Ethernet driver as kernel module problem

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
deeppurpleAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

nicademusCommented:
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...
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux Networking

From novice to tech pro — start learning today.