[arch-general] Boot sequence stops at modules (rc.sysinit)
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 The only reference I found to a similar problem is in the forum: http://bbs.archlinux.org/viewtopic.php?pid=323775 where it was suggested to try the fallback image and removing modules from the rc.conf. I've tried both, but hasn't helped (as expected: the kernel loads properly, so not an ramdisk problem, and the modules also load as I get [DONE] status...). Before this problem, I knew nothing at all about the boot sequence in linux so I read this: http://wiki.freegeek.org/index.php/The_Linux_Boot_Sequence Please correct me if I've misunderstood: after loading the kernel, the boot sequence gets to the init stage, and rc.sysinit is executed -- which, according to my '/etc/rc.sysinit' ends with loading of modules... but what happens next? I've looked at /etc/inittab but I don't understand how the sequence of events (and scripts) is specified. I tried booting into different run levels (adding 1 or 3 to the kernel line of grub), but it makes no difference. Because I don't get to a login prompt, I resorted to using a live CD to mount my root partition and tinker with /etc/rc.sysinit ... although I admit I don't know what I'm doing. I thought that maybe the initscripts package should have been upgraded at the same time as the kernel. In summary, what I've tried: - used a live CD to edit rc.conf (disable modules), and checked there was nothing in rc.local -- made no difference - tried booting with fallback image -- made no difference (didn't think it would as the kernel loads properly) -- made no difference - used a live CD to tinker with /etc/rc.sysinit but don't know what I'm doing, and it seems to complete successfully anyway, as all modules are loaded (status says [DONE]) - tried entering run level 1 by appending 1 to my Grub kernel line -- made no difference Is there a way to bypass what comes between the end of rc.sysinit (i.e. loading the modules) and the login prompt, so that I can at least log in and then try to fix the problem? In other words, how do I find out what happens after rc.sysinit and disable it? Thanks, Steve 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.
2008/2/29, Stephen Wilkinson <sw8511@gmail.com>:
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 (Роман Кирилич)
On Fri, Feb 29, 2008 at 3:41 PM, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
2008/2/29, Stephen Wilkinson <sw8511@gmail.com>:
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.
Woah - sounds like this machine hadn't been touched in like 6 months to a year.
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@gmail.com> wrote:
2008/2/29, Stephen Wilkinson <sw8511@gmail.com>:
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 (Роман Кирилич)
2008/3/2, Stephen Wilkinson <sw8511@gmail.com>:
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.
I highly recommend you to upgrade *at least* initscripts and udev. -- Roman Kyrylych (Роман Кирилич)
Thank you all for your replies. I may have found the problem, although I'm not sure because I ended up re-installing: tired of using live CDs and rebooting to see if my changes had any effect on the problem, I decided to do an ftp re-installation... but when I created my network connection, I kept getting transmission errors (code 0x90 reported in one of the virtual consoles, lots of TX overruns reported by ifconfig and in /proc/net/dev). That seemed odd as the hardware was working perfectly during the last upgrade... in the end I had to switch off my router and computer for those errors to disappear and to get a connection working. So I wonder if after the modules loaded, the network connection could not be brought up and caused everything else to fail. I'll never know as I wasn't able to test it... Thanks again for your helpful suggestions. Steve On 02/03/2008, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
2008/3/2, Stephen Wilkinson <sw8511@gmail.com>:
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.
I highly recommend you to upgrade *at least* initscripts and udev.
-- Roman Kyrylych (Роман Кирилич)
Stephen Wilkinson schrieb:
I tried booting into different run levels (adding 1 or 3 to the kernel line of grub), but it makes no difference. I'm no dev - but as far as I know the bsd-style initscripts gave ArchLinux no runlevels like you find them in SysV-style systems like Debian or SUSE. Running is running...
-- Gruß, Johannes Täglich http://blog.hehejo.de und du fühlst dich gut. http://cryptocd.eduforge.org/online_version
Stephen Wilkinson schrieb:
I tried booting into different run levels (adding 1 or 3 to the kernel line of grub), but it makes no difference. I'm no dev - but as far as I know the bsd-style initscripts gave ArchLinux no runlevels like you find them in SysV-style systems like Debian or SUSE. Running is running...
-- Gruß, Johannes Täglich http://blog.hehejo.de und du fühlst dich gut.
Um, yes there ARE run levels and a look at BOTH inittab and the scripts that are called from the levels being used will indicate that as well. For instance the difference between level three and level five is part of inittab itself. <- I use the difference between levels 3 and 5 during new system installs. YMMV of course. Very best regards; Bob Finch Liviu Librescu - În veci pomenirea lui. (May his memory be eternal.)
Stephen Wilkinson wrote:
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
The only reference I found to a similar problem is in the forum: http://bbs.archlinux.org/viewtopic.php?pid=323775 where it was suggested to try the fallback image and removing modules from the rc.conf. I've tried both, but hasn't helped (as expected: the kernel loads properly, so not an ramdisk problem, and the modules also load as I get [DONE] status...).
Before this problem, I knew nothing at all about the boot sequence in linux so I read this: http://wiki.freegeek.org/index.php/The_Linux_Boot_Sequence
The next step after Loading modules is loading standard ACPI modules. Try adding these to the module blacklist in rc.conf: ac battery button fan processor thermal Glenn
participants (6)
-
Aaron Griffin
-
Johannes Held
-
RedShift
-
Roman Kyrylych
-
Stephen Wilkinson
-
w9ya＠qrparci.net