This does not prevent the kernel being used on other releases, though it is most likely to work correctly on the release it is build for, or earlier ones. The further away from your base kernel release you are the more likely that there will be an incompatible userspace interaction which will prevent them working for you.
There are a number of changes to underlying systems like the boot process which have changed with Oneric, and simply upgrading the kernel on Natty does not work smoothly for me on my Natty machine. I've found that 2. Create a free Team What is Teams? Learn more. Where to download Linux Kernel source code of a specific version? Ask Question. Asked 9 years, 2 months ago. Active 1 year, 7 months ago.
Viewed 79k times. Improve this question. Mateusz Piotrowski 4, 5 5 gold badges 28 28 silver badges 59 59 bronze badges. RaoulDuke RaoulDuke 1 1 gold badge 3 3 silver badges 3 3 bronze badges. The link in this question seems to be broken. Add a comment. If you don't, you won't be able to boot the new kernel image. See the LILO docs for more information. After reinstalling LILO, you should be all set. Shutdown the system, reboot, and enjoy! If you ever need to change the default root device, video mode, ramdisk size, etc.
No need to recompile the kernel to change these parameters. If there isn't anyone listed there, then the second best thing is to mail them to me torvalds linux-foundation. If the problem is new, tell me so, and if the problem is old, please try to tell me when you first noticed it. The dump may look incomprehensible to you, but it does contain information that may help debugging the problem.
The text above the dump is also important: it tells something about why the kernel dumped code in the above example it's due to a bad kernel pointer. Alternately you can do the dump lookup by hand: - In debugging dumps like the above, it helps enormously if you can look up what the EIP value means. The hex value as such doesn't help me or anybody else very much: it will depend on your particular kernel setup. What you should do is take the hex value from the EIP line ignore the "" , and look it up in the kernel namelist to see which kernel function contains the offending address.
To find out the kernel function name, you'll need to find the system binary associated with the kernel that exhibited the symptom.
To extract the namelist and match it against the EIP from the kernel crash, do: nm vmlinux sort less This will give you a list of kernel addresses sorted in ascending order, from which it is simple to find the function that contains the offending address.
Note that the address given by the kernel debugging messages will not necessarily match exactly with the function addresses in fact, that is very unlikely , so you can't just 'grep' the list: the list will, however, give you the starting point of each kernel function, so by looking for the function that has a starting address lower than the one you are searching for but is followed by a function with a higher address you will find the one you want. In fact, it may be a good idea to include a bit of "context" in your problem report, giving a few lines around the interesting one.
If you for some reason cannot do the above you have a pre-compiled kernel image or similar , telling me as much about your setup as possible will help. You can now use all the usual gdb commands. When I logged in, a whole list of errors I got. Fortunately I was able to login with the old kernel. Then you need to remove the latest kernel which you installed, by logging with the old kernel. Some of your Hardware might not be supported, to install the latest kernel try compiling the kernel source and install it.
Also, is this pretty safe to do?
0コメント