Mailinglist Archive: opensuse (3637 mails)
| < Previous | Next > |
Problem with 2.4.2 kernel and Realtek 8139 module loading
- From: "Paul W. Abrahams" <abrahams@xxxxxxx>
- Date: Wed, 02 May 2001 12:20:44 -0400
- Message-id: <3AF033DC.351A8DC@xxxxxxx>
I've just switched over to the 2.4.2 kernel (from SuSE), and
I can't get my networking card to work, even though it
worked fine under the older 2.4.0 kernel. I haven't
changed /etc/modules.conf, which specifies loading the
8139too driver. As far as I can tell from the bootup
messages that flash by, insmod is rejecting the module at
boot time. I also tried running insmod explicitly later on,
and got the message:
> insmod 8139too
Using /lib/modules/2.4.2-4GB/kernel/drivers/net/8139too.o
/lib/modules/2.4.2-4GB/kernel/drivers/net/8139too.o:
init_module: No such device
Hint: insmod errors can be caused by incorrect module
parameters including invalid IO or IRQ parameters
There's a note on the SuSE website explaining that the 2.4
kernel series requires using the 8139too driver for the
RealTek 8139 networking chip, but of course that's what I'm
doing. I don't think the module parameters (which I never
specified anyway) are incorrect since the module worked
under kernel 2.4.0.
The only way I can get this message out to the world is to
send it from a different computer.
A side comment: the error messages that zipped by on the
screen appear neither in the dmesg output nor in
/var/log/messages. Is there some way I can look at them
for more than a second or two?
Paul Abrahams
I can't get my networking card to work, even though it
worked fine under the older 2.4.0 kernel. I haven't
changed /etc/modules.conf, which specifies loading the
8139too driver. As far as I can tell from the bootup
messages that flash by, insmod is rejecting the module at
boot time. I also tried running insmod explicitly later on,
and got the message:
> insmod 8139too
Using /lib/modules/2.4.2-4GB/kernel/drivers/net/8139too.o
/lib/modules/2.4.2-4GB/kernel/drivers/net/8139too.o:
init_module: No such device
Hint: insmod errors can be caused by incorrect module
parameters including invalid IO or IRQ parameters
There's a note on the SuSE website explaining that the 2.4
kernel series requires using the 8139too driver for the
RealTek 8139 networking chip, but of course that's what I'm
doing. I don't think the module parameters (which I never
specified anyway) are incorrect since the module worked
under kernel 2.4.0.
The only way I can get this message out to the world is to
send it from a different computer.
A side comment: the error messages that zipped by on the
screen appear neither in the dmesg output nor in
/var/log/messages. Is there some way I can look at them
for more than a second or two?
Paul Abrahams
| < Previous | Next > |