Bug 24211 - Symbios/NCR 53C8xx driver not on list if "dd" specified
Summary: Symbios/NCR 53C8xx driver not on list if "dd" specified
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
Target Milestone: ---
Assignee: Erik Troan
QA Contact: Brock Organ
Whiteboard: Florence Beta-3
Depends On:
TreeView+ depends on / blocked
Reported: 2001-01-17 14:51 UTC by Brent Nordquist
Modified: 2007-04-18 16:30 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-01-17 18:20:10 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Brent Nordquist 2001-01-17 14:51:58 UTC
When doing "LILO: expert text dd" from bootnet.img, when you get to the
expert screen for adding drivers and choose SCSI, my card's driver
"Symbios/NCR 53C8xx" doesn't appear on the list.  Pressing F2 to re-read
the driver disk doesn't help.

Strangely enough, if you omit the dd ("LILO: expert text") and say "No" to
the "Do you have a driver disk?" question, the driver appears on the
subsequent list.  Shouldn't "dd" always make the driver list longer (not
drop any drivers)?

This system also has the 3Com Etherlink III ISA, so that device driver gets
added manually first; it also requires specified module parameters

[Florence beta-2]

Comment 1 Brent Nordquist 2001-01-17 16:19:36 UTC
Second aspect of the problem:  The "LILO: expert text" boot from bootnet.img
does allow you to choose "Symbios/NCR 53C8xx" from the list; however, the driver
fails to load.  But if you omit expert mode altogether, and just boot "LILO:
text", it figures out it needs the "Symbios/NCR 53C8xx" driver all on its own,
and it loads fine!

Comment 2 Glen Foster 2001-01-17 18:17:11 UTC
This defect is considered MUST-FIX for Florence Beta-3

Comment 3 Erik Troan 2001-01-17 20:42:46 UTC
This seems to work fine here. We've tested this with NIC's, and it works fine.

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