Problem with 2.4.2 kernel and Realtek 8139 module loading
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
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: 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
If you are not using one of the graphic login managers, shift-pgup
will scroll back thru the boot messages. If you are, boot to the
non-graphical level and see above.
HTH,
Jeffrey
Quoting Paul W. Abrahams
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 don't do Windows and I don't come to work before nine. -- Johnny Paycheck
Jeffrey Taylor wrote:
If you are not using one of the graphic login managers, shift-pgup will scroll back thru the boot messages. If you are, boot to the non-graphical level and see above.
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?
Interesting discovery, Jeffrey. I knew about Shift-PgUp. But what I didn't know is that if you're using a graphical login manager, you can't get at them that way even though you can get at them with a text login manager. With KDM active I tried using Ctl-Alt-F1 to get to the bootup terminal, and indeed got there. But Shift-PgUp wouldn't take me back bfore the messages already visible. However, when I switched over to the textual login, Shift-PgUp showed me the messages. Of course, what they revealed is what I knew already: that the 8139too driver can't see the network card under the 2.4.2 kernel, at least without some (unknown) tweaking. Paul Abrahams
On Wed, 2 May 2001, Paul W. Abrahams wrote:
Jeffrey Taylor wrote:
If you are not using one of the graphic login managers, shift-pgup will scroll back thru the boot messages. If you are, boot to the non-graphical level and see above.
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?
Interesting discovery, Jeffrey. I knew about Shift-PgUp. But what I didn't know is that if you're using a graphical login manager, you can't get at them that way even though you can get at them with a text login manager. With KDM active I tried using Ctl-Alt-F1 to get to the bootup terminal, and indeed got there. But Shift-PgUp wouldn't take me back bfore the messages already visible. However, when I switched over to the textual login, Shift-PgUp showed me the messages.
The console buffer is being flushed when you switch to another console. If you want to have a look at the bootup messages, have a look at /var/log/boot.msg Bye, LenZ -- ------------------------------------------------------------------ Lenz Grimmer SuSE GmbH mailto:grimmer@suse.de Schanzaeckerstr. 10 http://www.suse.de/~grimmer/ 90443 Nuernberg, Germany One who is always in a stew generally goes to pot.
participants (3)
-
Jeffrey Taylor -
Lenz Grimmer -
Paul W. Abrahams