Linux doesn't boot up - Firewire issue

Martin Stone martin.stone at
Wed Apr 14 13:21:09 UTC 2004

So are you saying that the 1394 modules fail to load, or that your computer 
freezes when they attempt to load at boot time?

If your computer is freezing when it attempts to load the 1394 modules, it's a 
little more involved to get them out, since they are typically loaded from the 
initial ramdisk, rather than as part of the regular boot process.

I always did something like this:

gzip -dc /boot/initrd-xxxxx.img >/tmp/initrd.img
... (substitute the xxxxx for whatever your kernel's real initrd is, as listed 
in /boot/grub/grub.conf) ...

mkdir /tmp/1
mount -o loop /tmp/initrd.img /tmp/1
vi /tmp/1/linuxrc

... take out those entries in linuxrc that load the 1394 modules ...

umount /tmp/1
gzip -c /tmp/initrd.img >/boot/initrd-xxxxx.img

And reboot.  Later on you can fool around with the 1394 modules on your own and 
see just what the problem is, but at least that would get you booting.

Nancy Demers wrote:
> I found the REAL issue.  IEEE 1394 Firewire.
> Linux doesn't like this.  
> Does anyone have a clue how to get Linux to recognize
> a firewire controller?
> Thanks
> Nancy
> ----------------------
> There was a spelling error in my email (the GRUB
> command is correct - kernel)
> Thanks for the suggestion on init 3.  The error is in
> the firewall.  I attempted to add nofirewall as a
> kernel parameter... but didn't work.  Aside from
> reinstalling without a firewall, is there any way to
> bypass this initialization?
> Thanks again 
> Nancy
> At the grub menu screen hit e before it starts
> booting.
> Use move down to the line kernel
> /boot/vmlinuz-2.4.22-1.22115.ntpl ro
> root=LABEL=/ hdc=ide-scsi rhgb
> remove rhgb 
> Adding init 3 will put you in command mode (not X).
> Then you will hopefully see what is hanging.

More information about the users mailing list