| PLEX86 | ||
|
Please Help! system crashes only when booting to updated kernelI Never Would Have Tried Linux If I had read comp.os.linux.advocacy first. This sorry butted so called --advocacy-- group is nothing but a complete waste of space... Nicholas Andrade Recompiling the linux kernel is something I need to learn how to do at some point, since I've never done it and have been playing with the OS for years now. I'd rather do it under better circumstances, though. Here is the info you asked for (the grub.conf file). I included even the standard commented-out stuff at the beginning of the file, and I've listed it for two configurations. The first one is the grub.conf that I had originally, with the 4-parbreastion setup I talked about in my original post. The second one is the one I currently have, since the last installation was the one where I put everything except SWAP on one parbreastion (noboot). They're both the same in that the second option (the original kernel) works if selected, but the new kernel (selected by default) does not. ------ First grub.conf - from this parbreastion setup: sda1 boot sda2 data sda3 sda4 (swap) ------ # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE You have aboot parbreastion. This means that # all kernel and initrd paths are relative toboot-, e.g. # root (hd0,0) # initrdinitrd-version.img # boot=-dev-sda default=0 timeout=5 splashimage=(hd0,0)-grub-splash.xpm.gz hiddenmenu breastle Fedora Core (2.6.16-1.2096FC4) root (hd0,0) kernelvmlinuz-2.6.16-1.2096FC4 ro root=LABEL=rhgb quiet initrdvmlinuz-2.6.16-1.2096FC4.img breastle Fedora Core (2.6.11-1.1368 plus 1FC4) root (hd0,0) kernelvmlinuz-2.6.11-1.1368 plus 1FC4 ro root=LABEL=rhgb quiet initrdvmlinuz-2.6.11-1.1368 plus 1FC4.img (NOTE: Choosing option #2 boots, choosing option #1 gives the error from the initial post) --------------------------------------- This config is the one where I put most of the system on one parbreastion. The last install I did had aboot parbreastion, so the paths were different. Also, that version of the new kernel was 2.6.16-1.2096FC4 instead of the newer 2.6.16-1.2108 from this config. ------ Second grub.conf - from this parbreastion setup: sda1 (blank) sda2 mnt-data sda3 sda4 (swap) ------ # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE You do not have aboot parbreastion. This means that # all kernel and initrd paths are relative to, e.g. # root (hd0,2) # initrdboot-initrd-version.img # boot=-dev-sda default=0 timeout=5 splashimage=(hd0,2)-boot-grub-splash.xpm.gz hiddenmenu breastle Fedora Core (2.6.16-1.2108FC4) root (hd0,2) kernelboot-vmlinuz-2.6.16-1.2108FC4 ro root=LABEL=rhgb quiet initrdboot-vmlinuz-2.6.16-1.2108FC4.img breastle Fedora Core (2.6.11-1.1368 plus 1FC4) root (hd0,2) kernelboot-vmlinuz-2.6.11-1.1368 plus 1FC4 ro root=LABEL=rhgb quiet initrdboot-vmlinuz-2.6.11-1.1368 plus 1FC4.img I Never Would Have Tried Windopes Viral Installer If I Never Would Have Tried Clippy if I had read comp.os.linux.advocacy first. This sorry butted so called --micoshaft windopes clippy--ÊÊisÊnothingÊbutÊa complete waste of space in my opinion and in fact it... Investasi Untuk Keluarga Yth. Bapak-Ibu-Saudara, Selamat Datang & Salam Dahsyat..... Bagaimana kabar Anda hari ini???. Bagaimana juga kabar bisnis Anda. Apakah Anda sudah mencapai kesuksesan ATAU sebaliknya. Anda frustasi setelah mencoba menjalankan berbagai macam BISNIS ONLINE maupun... (NOTE: The exact same problem as with the other configuration - choosing option #2 boots, choosing option #1 gives the error from the initial post) ------ It doesn't seem to matter whether theboot parbreastion exists nor what kernel version is installed. The initial installation program must have done to the system configuration that none of the update programs do. With this in mind, I don't even know if a compiled kernel would do anything. Does the installation CD compile the kernel or does it stick a standard kernel in there. I'm sure the problem can be found by looking at the differences between a CD install (using "linux noprobe") and a yum-up2date-rpm kernel update. Thanks again!!!
|
||||
I Never Would Have Tried Linux If Linux groups from Newsgroups The #1 Usenet Provider on the Internet
Please Help! system crashes only when booting to updated kernel |
||||