Kernal panic after installing more memory, won't boot
FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
After pulling the new memory module out, Fedora started normally.
There is a high probability that the new ram stick is bad. Boot off of any live cd that has memtest. I use System Rescue CD, but I think the Fedora install cd might have it on there. Check the F1-4 menu's when you boot off the cd and look for a memtest boot parameter.
Run memtest on each ram stick individually. I'd put money on you getting errors immediately after the test starts on the new stick.
For the record, what are your boot options? This is easy to see in an interactive GRUB session. Just highlight the selection you normally use (with arrow keys) and press the “e” key. There will be a line that says “kernel foo options” (where foo is the path to the kernel). If you don’t have an interactive GRUB, you’ll need some way of reading your grub.conf (perhaps a livecd).
An alternative method for determining the boot options is by reading the contents of /proc/cmdline. Obviously, you’ll need to be able to boot linux for this to work (so remove the likely-faulty ram before you try).
For the record, what are your boot options? There will be a line that says “kernel foo options” (where foo is the path to the kernel).
There's a line that just starts with 'Kernel', but doesn't say 'options'.
Here's what the line says:
Kernel /vmlinuz-2.6.23.1-49.fc8 ro root=/dev/VolGroup00/LogVol00 rhgb init /initrd-2.6.23.1-49.fc8.img
Note: after rhgb there is a small arrow ->, which I assume means that the line carries over to the next line. In other words there are two lines visible, which I have typed out as one line.
Quote:
Originally Posted by osor
An alternative method for determining the boot options is by reading the contents of /proc/cmdline.
proc/cmdline is completely empty. A blank file. (opened in Kate)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.