We help IT Professionals succeed at work.

Ethernet driver as kernel module problem

deeppurple
deeppurple asked
on
Medium Priority
285 Views
Last Modified: 2010-03-17
Hi all,

Not to long ago I got the idea to get right into modules with my kernel
(2.0.30).  Things worked fine (or so I thought) using kerneld and I was
happy.

After a while I noticed that there was a problem with my Ethernet card
(a WD8003E).  I could ping from my box, over the WD8003E, to another box
18 times after startup, then all traffic after that would fail.  :-(
(It had been a while since I used the Ethernet at home...)

This ONLY happened while I had the WD8003E installed as a module; when I
re-compiled the kernel again, with this in the kernel, the problem was
cleared.

When I was suffering with the problem, I saw that it looked that I could
send data OK, but anything I received was currupt or something.  This I
could see by doing a "ifconfig eth0" command and looking at the TX & RX
counts.  The "Error" count on the RX side of things would just keep on
incrementing.

I think I can remember reading something like this happening to someone
else before, but haven't been able to track down anything on the 'net.

Is any one able to help me with this.  It's _NOT_ urgent at all, as I
always start the Ethernet at startup, and the module would be loaded
anyway,
but it's got me a little curious.

Brian
Comment
Watch Question

I actually had the same thing happening to me, I could not seem to compile the kernel so My Network card would work, I mean, it worked, and configured, but then it had around about 912 bad packets after just having loaded.

I would have to say though the best thing for you to do is leave it in the kernel anyway, I have everything My Linux system uses in the kernel, and no modules at all, If you use the bzlilo or bzimage thing, you don't have to worry about the size of the kernel, unless you have a few hundred different peripherals haning out of you machine which require a different module each!
One other thing, loose the .01  in other words it would be a safer bet to go back to 2.0.29 since 2.0.30 has bugs as far as Networks go. I think that may have been where my errors where some time ago....

Also it may just be one little option you need to be disabling/enabling when you recompile the kernel and it will fix it, but since there are many Networking options...it takes a while.....Make a nice big cuppa....or twenty.  best of luck.


Nica...

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.