Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 5241 - kerneld configuration and /etc/conf.modules
Summary: kerneld configuration and /etc/conf.modules
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: control-panel
Version: 5.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-09-20 11:27 UTC by hartleys
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2000-02-16 13:52:41 UTC

Attachments (Terms of Use)

Description hartleys 1999-09-20 11:27:36 UTC
About a year ago, I installed Red Hat 5.1 on my generic
IDE disk-based PC without problem.  It did not have a
card at the time.  A few days ago I added a NE2000
network card set to a free IRQ, 5, and a free IO address
range, 0x300--0x31f.  The card works fine under Windows 95
(I hate mentioning that but it is critical information).
  I followed exactly the directions on page 132 of the Red
Hat 5.1 manual on kerneld configuration, entering eth0, ne,
io=0x300, and irq=5 into the dialog boxes.  My understanding
is that clicking on `kerneld restart' is supposed to enter
information into the file /etc/conf.modules, but it did not.
The file was unchanged and still zero length.  I was logged
in as root during all this.
  By reading and reading the modprobe man page, I stumbled
upon manually editing the following into /etc/conf.modules

  alias eth0 ne
  options eth0 io=0x300 irq=5

Now the card works fine.
  Do you know why the kerneld configuration tool does
not seem to work?

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