clean install hangs system
Jim Cornette
jim-cornette at insight.rr.com
Mon Dec 1 02:49:12 UTC 2003
Remco wrote:
> Hello,
>
> After installing Core 1 and booting for the first time I get stuck with the
> login screen which doesn't respond to the keyboard (I didn't install X so
> this is a console login).
USB legacy support caused me to have no keyboard in a terminal. I think
that ACPI not being enabled also had something to do with my keyboard
loss. Try adding acpi=on to your kernel line. If you have USB legacy
support set in your BIOS, try disabling that feature.
>
> After a while this error appears:
>
> eth0: Host error, FIFO diagnostic register 2000.
> eth0: PCI bus error, bus status 00a00029
>
> This error appears whenever I ping the machine from another box or when I just
> wait a while.
>
> When I shutdown, remove the nic (a 3Com PCI 3c905 Boomerang) and reboot the
> same login freezes but I don't get the eth0 error.
This card is pretty common. I'm going to try this card again shortly. I
think that there is a newer version of ethtool out. I hope something is
changed in the program to get these cards working properly again.
>
> Also, at boot-up, no error messages are generated and all services start-up
> cleanly (all green OKs).
>
> I understand that the eth0 error is caused by the system failing somewhere
> else, however I get little feedback otherwise (no other errors). Moreover, I
> tried running the install cd in rescue mode but it crashed spitting out a
> nasty run-time error (some libs couldn't be found) so I have to figure out a
> way to get at the logs.
If I'm thinking about the same logs. They might be in your /root
directory. Without a keyboard, I don't know how you would get to the
logs though.
Jim
>
> Does anyone have a suggestion? I'll be going through my cds looking for
> something to use as a rescue kit ;-)
>
> regards,
>
> Remco
> -----
> AI student
> Open Source fundamentalist
--
You may get an opportunity for advancement today. Watch it!
More information about the fedora-list
mailing list