Craig White wrote:
On Fri, 2005-08-26 at 16:47 -0600, Philip Prindeville wrote:
Craig White wrote:
On Fri, 2005-08-26 at 12:19 -0600, Philip Prindeville wrote:
I'm getting the message "No driver found" during an attempted
install of FC3.i386 on an AMD NX1500S DB (mini-ITX) mainboard.
It uses the SiS5513 chipset (962/963) south and northbridge chipsets.
The problem is, I can't tell which device it's missing the driver for.
Sure would help if it gave a slot number, or PCI ID, device category
(video, disk controller, etc).
Any ideas?
----
try switching to virtual console 4 and see what the print is on screen..
<Alt><Control><F4)
Craig
Well, vty3 tells me that "54 keymaps are available" and vty4 gives me
the probing/autoconfiguration information for eth0...
Otherwise, nothing looks suspicious other than the fact that it fails to
find a floppy controller (I tried to boot with "nousb nofloppy" because
it hangs at "running /sbin/loader" if I don't give the "nousb" argument...
no idea why)...
----
try some of the boot options listed in item 6 of fedorafaq (for FC-3)
http://www.fedorafaq.org/fc3/
Q: I have strange installation problems.
A: If your installation doesn't work, or you have problems during or
after installation, first read the README
<http://download.fedora.redhat.com/pub/fedora/linux/core/3/i386/os/README-en.html>
and the Release Notes.
<http://download.fedora.redhat.com/pub/fedora/linux/core/3/i386/os/RELEASE-NOTES-en.html>
If the README and Release Notes don't have a solution for your problem,
try booting the installer with one of the following commands:
linux ide=nodma
linux acpi=off
linux i8042.nomux
linux acpi=off apm=off
The "i8042.nomux" is especially helpful if you have keyboard or mouse
problems.
If any of those commands fixes your problem, please file a bug in Red
Hat's Bugzilla.
(Thanks to Alan Cox for all this information.)
Craig
Tried all of those options, but it made no difference. When I go
to vty3 or vty4, doing shft-page-up doesn't work... so I can't scroll
through all of the output. Sigh.
I'll try "noprobe" next.
Sure would help if I could tell if the missing driver was for the
graphics card or the disk controller or... whatever.
-Philip
