Bug 61040
Summary: | FTP install: can't select network device driver | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Danny Trinh <danny_trinh> |
Component: | anaconda | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | afom_m, clay_cooper, dale_kaisner, danny_trinh, dean_oliver, gary_lerhaupt, john_hull, joshua_giles, matt_domsch, michael_e_brown, robert_hentosh, rogelio_noriega |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-03-26 16:51:42 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 61590 |
Description
Danny Trinh
2002-03-12 16:25:46 UTC
e1000 is on the driver disk and not bootnet, so you'd need 'noprobe dd' (expert is largely irrelevant). If you just do noprobe, you should get the dialog and be able to hit F2 to use the driver disk. This definitely appears to be working for me here, so if you could confirm that it's just that e1000 isn't on bootnet (which it won't be) or if there's something else going on, that would be great I just use e1000 as a sample. I don't see a list of NIC drivers, when I use "expert noprobe" mode. If I use broadcom NIC card, I still can't pick the driver, because there is no list of NIC drivers show up. Hrmm... this is working for me here on my test machine. I'll try to remember to do it as I'm doing some testing on other machines to see if I can reproduce the problems there There may be some confusion on this. Here are the exact steps/screens: 1. "expert noprobe" at boot prompt 2. No to driver disk, choose English, us keyboard 3. Choose FTP 4. Devices screen--> choose driver for NIC 5. connect to server in next 2 screens 6. You get a Devices screen that says that no special device drivers have been loaded. Choose "Add Device" 7. Choose "Network" to add a network device 8. Choose "No" for using a driver disk You are then kicked out to the SCSI/Network screen instead of being able to choose from a list of devices. Aha, with that information, I can reproduce it. Thanks, I'll look into it some more to try to see what's going on. not fixed in beta3 Since we froze last week, nope... it's on my list of things to fix, though. Just haven't gotten there due to things which require string/screen freezes needing to be done first. This behavior is actually as expected. There are only additional network drivers on the NFS install images and this is identical to the 7.2 behavior. Adding all of the network drivers to the FTP image would add over a meg to the ramdisk size and thus bump up the memory requirements similarly. To get network drivers other than the ones on bootnet.img with an FTP install, you have to use a driver disk. |