firewire hangs system at boot
Béla Pátkai
bela.patkai at pp.inet.fi
Fri Mar 19 08:10:15 UTC 2004
In interactive mode the system hangs again after enabling the swap
space, so this doesn't work either. Unfortunately my BIOS can't turn
off the firewire controller.
Is there a kernel boot argument that prevents kudzu from starting? (I
haven't found any at
http://www.ibiblio.org/mdw/HOWTO/BootPrompt-HOWTO.html)
AD> Enter interactive mode when init starts by hitting "I" like it says and
AD> say no or "n" for kudzu when it asks you for the rest say yes. It should
AD> not go about detecting the hardware then.
>> Thanks, this "nofirewire" option works, the firewire initialization is
>> skipped, but at a later point of the bootup it starts to look for new
>> hardware and again the firewire hangs it... So, how could I skip the
>> search for new hardware? If only once I could boot I could change the
>> kernel.
>> AV> I believe, what you want to do, is enter edit mode on grub, by hitting
>> AV> e, and change your line, adding only "nofirewire" to the end. Then hit
>> AV> enter to save your change (for the current session), and b to boot.
On Thu, 2004-03-18 at 06:39, bela.patkai at pp.inet.fi wrote:
> I installed FC1 on a new HP nx9010 laptop without problems, but the
> system hangs at bootup when it reaches the initialization of the
> firewire controller (ohci1394). Nearly the same problem is posted on
> bugzilla, and I'm sure that the problem is the 2.4.22-1.2115 kernel,
> but I don't know how to change the kernel. Or is it possible to
> configure GRUB so that it skips the initialization of the controller?
> I tried something in GRUB that I found on the web, but it didn't work:
>
> kernel /vmlinuz-2.4.22-1.2115.nptl ro root=LABEL =/ hdc=ide-scsi alias
> ieee1394-controller off
>
> Please give me an idea how to follow.
>
> Bela
More information about the fedora-list
mailing list