Bug 64565 - driver disk does not work
Summary: driver disk does not work
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-05-08 00:26 UTC by Robert Jameson
Modified: 2007-04-18 16:42 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-05-28 13:59:50 UTC
Embargoed:


Attachments (Terms of Use)

Description Robert Jameson 2002-05-08 00:26:16 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 
1.0.3705)

Description of problem:
When booting off the bootnet.img for RH 7.3, and then going to devices and 
trying to load the driver disk by pressing F2, and then inserting the driver 
disk from 7.3 named drvnet.img, the installer says the disk are incorrect for 
this version of Redhat.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.boot from the bootnet.img from rh 7.3
2.when asked for the driver to use, press f2
3.insert the drvnet floppy.


Actual Results:  It said that the drivers were not for this release of redhat

Expected Results:  should of allowed me to load the drivers off the disk.

Additional info:

Comment 1 Michael Fulbright 2002-05-09 18:41:54 UTC
Have you tried writing the driver disk onto a different disk to check if its a
media problem?

Comment 2 Brent Nordquist 2002-05-20 19:01:20 UTC
I hit exactly the same issue/same error message, and I tried a second disk, and
it worked fine; I think your theory is right.

Comment 3 Michael Fulbright 2002-05-23 19:44:22 UTC
Any luck with a different disk?

Comment 4 Paul Murphy 2002-05-28 13:59:45 UTC
I booted from boot.net, hit f2 and loaded drvnet fine.  I selected etherlink III
(3c509) and then tried to set the IRQ to 7.  At that point the process went into
a loop continually querying for a device, unless I didn't try to set the IRQ.
The default IRQ doesn't work because of a conflict.  Setting it to 7 works fine
in 7.2 /etc/modules.conf


Comment 5 Michael Fulbright 2002-06-12 16:50:05 UTC
Good to hear its working.


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