[opensuse-amd64] Trouble with Kernel of the Day
I am running 64-bit SuSE 10 on a Presario R3240 laptop (AMD64-based). I installed the rpm for the the latest _x64 kernel of the day (KOD), 2.6.18.2, dated Nov. 25. (The rpm saved me some manual labor from redirecting the link to '/usr/src/linux'.) During boot, the system crashes. Here is part of the messages I am getting, ending with the crash: . . . fsck succeeded. Mounting root device read-write. Mounting root /dev/hda6. kjournald starting. Commit interval 5 seconds. EXT3 FS on hda6, internal journal. EXT3-fs: mounted filesystem with ordered data mode. /bin/run-init: opening console: No such file or directory Kernel panic - not syncing: Attempted to kill init! And then the system just hangs. Here is the part of the /boot/grub/menu.lst which is pertinent to this: title Linux-2.6.18.2-20061125183539-preemptible root (hd0,5) kernel /boot/vmlinuz-2.6.18.2-20061125183539-preemptible root=/dev/hda6 vga= 0x317 selinux=0 resume=/dev/hda7 splash=silent showopts idebus=66 initrd /boot/initrd-2.6.18.2-20061125183539-preemptible This section of /boot/grub/menu.lst was created using 'INSTALL_PATH=/boot make install', which is SuSE's well-thought shortcut to the drudgery of copying system map files manually. I enabled full preemption. I had no problems with full preemption with 2.6.16. Could anybody shed some light on what I may be doing wrong? TIA for your time. -- Running 64-bit Linux on AMD64 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
On Monday 27 November 2006 08:24, Constantine 'Gus' Fantanas wrote:
I am running 64-bit SuSE 10 on a Presario R3240 laptop (AMD64-based). I installed the rpm for the the latest _x64 kernel of the day (KOD), 2.6.18.2, dated Nov. 25.
That's a 10.2 kernel running on 10.0 -- that unfortunately requires some other changes like updating udev or mkinitrd.
This section of /boot/grub/menu.lst was created using 'INSTALL_PATH=/boot make install', which is SuSE's well-thought shortcut to the drudgery of copying system map files manually. I enabled full preemption. I had no problems with full preemption with 2.6.16.
What do you mean with full preemption? Did you recompile your kernel.
Could anybody shed some light on what I may be doing wrong?
It's normally safest to use matching user land for the kernel rpms -- if you use a 10.2 kernel use 10.2 userland etc. Self compiled kernels can be more independent and work on older user land, but the rpms have more dependencies -Andi --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
Andi Kleen wrote:
On Monday 27 November 2006 08:24, Constantine 'Gus' Fantanas wrote:
I am running 64-bit SuSE 10 on a Presario R3240 laptop (AMD64-based). I installed the rpm for the the latest _x64 kernel of the day (KOD), 2.6.18.2, dated Nov. 25.
That's a 10.2 kernel running on 10.0 -- that unfortunately requires some other changes like updating udev or mkinitrd.
--I think --but I am not 100% positive-- mkinitrd works alright, but as for udev I cannot be sure because, starting with 9.3, udev seems to have been undergoing rapid changes. I guess it's time to bite the bullet and update to 10.2.
This section of /boot/grub/menu.lst was created using 'INSTALL_PATH=/boot make install', which is SuSE's well-thought shortcut to the drudgery of copying system map files manually. I enabled full preemption. I had no problems with full preemption with 2.6.16.
What do you mean with full preemption? Did you recompile your kernel.
--Yes, of course, I did recompile my kernel. The rpm was for the kernel sources installation only, or at least that was my understanding. The rpm for the "default" kernel could not install, complaining that my perl-Bootloader module was out of date. I wanted to compile the kernel anyway, so I can fine tune it.
Could anybody shed some light on what I may be doing wrong?
It's normally safest to use matching user land for the kernel rpms -- if you use a 10.2 kernel use 10.2 userland etc. Self compiled kernels can be more independent and work on older user land, but the rpms have more dependencies
--Alright. Thank you for your time, Andi.
-Andi
-- Running 64-bit Linux on AMD64 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-amd64+help@opensuse.org
participants (2)
-
Andi Kleen -
Constantine 'Gus' Fantanas