Results 1 to 3 of 3
Thread: kernel upgrade woes
Enjoy an ad free experience by logging in. Not a member yet? Register.
- Join Date
- Jan 2010
[SOLVED] kernel upgrade woes
I used oldconfig with my current config, then:Code:
make V=1 bzImage make V=1 modules sudo make V=1 modules_install sudo cp arch/i386/boot/bzImage /boot/vmlinuz-188.8.131.52 sudo cp System.map /boot/System.map-184.108.40.206 sudo /sbin/mkinitrd -f -v /boot/initrd-220.127.116.11.img 18.104.22.168 # add to grub.conf: title Handrolled (22.214.171.124) root (hd0,0) kernel /boot/vmlinuz-126.96.36.199 ro root=LABEL=/ initrd /boot/initrd-188.8.131.52.imgCode:
Loading ata_piix.ko module ata_piix 0000:00:1f.2: MAP [ P0 P2 IDE IDE ] ACPI: PCI Interrupt 0000:00:1f.2[b] -> GSI 19 (level, low) -> IRQ 19 ata_piix 0000:00:1f.2: 0x1F0 IDE port busy ata_piix 0000:00:1f.2: 0x170 IDE port busy ata_piix 0000:00:1f.2: no available legacy port Trying to resume from LABEL=SWAP-sda2 No suspend signature on swap, not resuming. Creating root device. Mounting root filesystem. ext3: No journal on filesystem on hdd5 mount: error mounting /dev/root on /sysroot as ext3: Invalid argument Setting up other filesystems Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init!
Any suggestions of what to try next, or how to go about diagnosing the problem? I've scanned the config diffs (attached), and can't see an obvious culprit - they are all removals of presumably obsolete variables; I've also checked that the initrd contains the same entries as my current one, and the init script is identical.
Last edited by Hugo_vdS; 01-14-2010 at 03:06 PM. Reason: solved
you'd probably spend less time installing and configuring the latest fedora than you would trying to get a new kernel to work on an old distro
- Join Date
- Jan 2010
Got this working, finally, thanks to some great help from Greg at my old office.
Not sure exactly why, but with the new build the IDE driver gets to see the SATA disk before the SATA driver does: I should have searched for the first thing that looked like an error message ("no available legacy port") to find answers more quickly.
The solution is to tell the IDE driver not to attempt to detect drives on the first controller, by adding "ide0=noprobe" to the kernel command line.
That doesn't yet solve things for the 184.108.40.206 build, but now I have a reproducible baseline at 220.127.116.11 I should be able to take it forward.