[arch-general] Boot sequence stops at modules (rc.sysinit)

[Stephen Wilkinson]

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 at gmail.com> wrote:
>
> 2008/3/2, Stephen Wilkinson <sw8511 at 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 (Роман Кирилич)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://archlinux.org/pipermail/arch-general/attachments/20080304/2d71433a/attachment.htm>