Bug 13094 - Installer fails to load any nic driver on driver disk!
Summary: Installer fails to load any nic driver on driver disk!
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Erik Troan
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-06-27 07:30 UTC by Pekka Pietikäinen
Modified: 2007-04-18 16:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-07-13 20:29:11 UTC
Embargoed:


Attachments (Terms of Use)

Description Pekka Pietikäinen 2000-06-27 07:30:25 UTC
I tried to do an NFS install with an alteon acenic board, so I made 
a driver disk from drivers.img, started up with linux dd, inserted the
driver disk and it kept on asking me for a supplemental driver disk.

Comment 1 Hans de Goede 2000-06-30 18:16:21 UTC
Same here for an 3c509 module, here's what I do exactly:
-insert bootnet.img disk
-press enter (or do linux dd)
-insert driver-disk (if linux dd weas choosen)
-choose us keyboard, english language
-choose nfs
-press F2 and insert driver disk (if not choosen linux dd)
-choose 3com etherlink III (3c509)
-floppy light lights, asks for driver disk
-insert driver disk
-floppy does nothing
-error
-redo from floppy light lights, asks for driver disk

I've tried replacing the driver disk with the bootdisk and then after the error
reinserting the driver disk, to see if it is a floppy exchnage problem, but no
go.


Comment 2 Hans de Goede 2000-07-10 22:10:09 UTC
This is still there in beta3, and this is a serious bug!!, without the driver
disk it is impossible todo installs on many machines. I just managed to also get
the same problem with a propietary cdrom controller (after buiding my own driver
disk, since that is still broken in beta3 too, see bug 12145)


Comment 3 Erik Troan 2000-07-13 20:29:09 UTC
This should be fixed for the next beta. I'll try to get a new bootdisk w/ this
fix available soon.


Note You need to log in before you can comment on or make changes to this bug.