Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've spent several hours now trying to get a Belkin F5D6001 card to work in a Slack 8 box running 2.4.21 and using the ADM8211 driver, with no success at all. The module keeps returning unresolved symbols when I run depmod -a, and I have no idea why. Others have reported getting the driver to work under Slack, but they've never detailed how exactly they did it, and the manufacturer seems to be pretty redhat-centric in their support. Anyone have any ideas?
I too got the unresolved symbols with this driver (I'm using it on a cardbus card), and yet it works and works well. I find that I don't even have to "force" it to load, there is a warning on load but that's it.
If you can grep 8211 /lib/modules/`uname -r`/modules.pcimap and find at least one entry for it, you should be fine, on my system there are 2 entries.
take a look at /etc/rc.d/rc.inet1 to configure it. Is this the only netcard in the machine?
Okay, at this point I've been able to get the driver in and the card working, but now the card seems to stop transmitting packets after a while. It looks like it'll still receive, but never send. The last time it happened it was after about 30mb of transmission and 7mb of receipt. I had to bring the interface down and back up before it would transmit again.
how far down did you have to take it? was it just ifconfig ethX down up? Also, any messages in the logs at about the time the card stops? they would be in /var/log/messages and/or /var/log/syslog and/or /var/log/kernel/errors, etc.
Initially I went all the way to the point of unloading the driver and then reloading it and bringing it back up, but then I realized that just bringing the interface down and up again was enough to fix the problem. So until I figure out what's going on, I've got a cron job to down and up the interface every five minutes. Crappy, but at least it works. I've heard that at one point something similar had to be done with an old version of the Tulip driver until a bug was ironed out.
As far as the logs, I had a look and didn't see anything I didn't recognize except for a bunch of these:
Yeah, I got those same MARK msgs w/slack8 and still do with slack9, must be a slack thing...the cron job sounds like an elegant solution to a not-so-elegant problem.
EDIT: deleted meaningless discussion of hotplug issues, forgot, card is pci.
At some point ADMtek will no doubt open all the source code, even what's in the ADM_prv.o binary.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.