Hello All, Thank you for your replies. To answer a few questions: * versions before and after ugrade (I'm can see I've probably attempted a combination which won't work...) - kernel: 2.6.15-2 ---> 2.6.22 - udev: 079-1 - initscripts: 0.7.1-17 - mkinitrd 1.01-25 -> mkinitcpio 0.5.15-2 When I upgraded the kernel it only asked to upgrade mkinitrd to mkinitcpio... so the other two didn't change. * tried blacklisting these modules: ac battery button fan processor thermal but still stuck after modules have loaded. I have a look at the rc.single file which ends with "exec /sbin/init -t1 S" so I tried to put that at the end of rc.sysinit to try and get a login prompt, but that didn't work. Is there a way of going from rc.sysinit to prompting for a shell (bypassing any intermediary steps)? Thanks, Steve On 29/02/2008, Roman Kyrylych <roman.kyrylych@xxxxxxxxx> wrote: > 2008/2/29, Stephen Wilkinson <sw8511@xxxxxxxxx>: > > > Hello everyone, > > > > After upgrading the kernel alone (and after fixing some kernel panics > > -- see postscript) the boot sequence now stops at loading the modules > > ([DONE]) and goes no further: the cursor blinks and I can type > > characters, but I never get a shell prompt. It seems the boot sequence > > doesn't go beyond rc.sysinit > > > . . . > > > > P.S: in case it's relevant, here is a summary of the kernel panics I > > got after upgrading the kernel and rebooting: > > > > After kernel upgrade I got kernel panics because I hadn't changed > > initrd26.img to kernel26.img and /dev/hda5 to /dev/sda5 in Grub's > > menu.lst (as you can see I hadn't upgraded for a long time, and didn't > > pay enough attention to the upgrade messages). Having done that, I > > then had to correct /etc/fstab for the same /dev/hda5 mistake. Finally > > the kernel booted properly, but the sequence stops at loading modules. > > > please indicate current and previous versions of kernel, udev, > initscripts, mkinitcpio. > > > -- > Roman Kyrylych (Роман Кирилич) >
