Bug 12141 - Linuxconf doesn't configure smc-ultra.o correctly
Linuxconf doesn't configure smc-ultra.o correctly
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: linuxconf (Show other bugs)
6.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-06-12 14:29 EDT by dcjanes
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:47:41 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description dcjanes 2000-06-12 14:29:38 EDT
I just set a box up to be a firewall using two old SMC Ultra ISA NICs. I 
set the interrupts and everything, started the network and my system hung 
(cold re-start, fsck needed).

The problem appears to be that the smc-ultra driver requires another 
module to be preloaded before it is loaded.  Adding a line like

pre-install smc-ultra modprobe -a 8390

to /etc/conf.modules fixed the problem, but shouldn't linuxconf take care 
of these dependencies?  The install program did, since this machine lacks 
a CD-ROM and was installed using http.
Comment 1 Nalin Dahyabhai 2000-06-15 16:02:51 EDT
What does "grep smc-ultra /lib/modules/`uname -r`/modules.dep" on the affected
machine show?
Comment 2 dcjanes 2000-06-15 21:27:05 EDT
/lib/modules/2.2.14-5.0/net/smc-ultra.o:	
/lib/modules/2.2.14-5.0/net/8390.o
/lib/modules/2.2.14-5.0/net/smc-ultra32.o:	
/lib/modules/2.2.14-5.0/net/8390.o

Looks right to me. I'm still using the stock kernel from 6.2, as the machine is 
not really connected yet. I plan to roll a custom kernel this weekend, probably 
from the virgin 2.2.16 sources.
Comment 3 Brent Fox 2002-06-05 12:24:02 EDT
Closing because we don't ship linuxconf anymore
Comment 4 Red Hat Bugzilla 2006-02-21 13:47:41 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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