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 know that there is a known problem with the Netgear FA311 and Redhat/Linux after reading various sources across the net I have been unable to find a cure for my problem.
A little bit of background information for you, I am a complete newbie to Linux, but I am trying to run a Celeron 533 machine that I have put together with 'Left over' parts as a Router for my DSL, Once this is done I will also be building a p3 833 into a file server.
When I boot, as soon as it fires up ethX (Where X = 0 or 1) I get this error
ethX: PCI error 0x800000
It just repeats over and over and I cant see anything. I can still login by just typing login and password then typing service network stop, eventually it stops.
If I do a ifconfig ethx, everything looks alright, but the overruns are like huge, like > 3mil but different on both cards.
Some interesting information, though I don't know if this has anything to do with it, the network config shows the drivers to be natsemi DP83815 yet the chip on the card is DP83816. Also the card has stamped on it FA311 Rev-D2 (checked this after reading that some came out with the wrong EPROM).
I have tried to install new drivers from the Netgear site, and from www scyld com [cant post a url yet ?!] (I don't know if I installed these properly as there wasent much instruction), and after reading on another forum I also tried some other drivers (netdrivers.tgz) from the same site that had a 'Make/Make Install' file attached (For newbs like me). The netgear drivers made no difference, while the scyld drivers changed the error message to 'Something Wicked Happened!' but thats all.
If i startx and enable the cards there (one as static ip one as PPPoE for DSL) they seem to work, I can ping internal machines and also connect to the net, but my processor is sitting at 100% and it takes about 5 mins to do anything. If I then <ctrl><alt><F1> I see the error filling the screen and the only way back is <ctrl><alt><F7> as I cannot type any commands.
I have been waiting on a response back from Netgear with help (As I have purchased these cards for 14 machines as well as a 16port switch from them) for five days now, and as I hope to have this all running for start of business on Monday coming I am getting desperate.
Side note, ctrl+alt+f2, or f3 up til most likely f6, will get you a login prompt and let you type commands f1 is where startx is launched from, so you can't login there as it's still running.
Check dmesg for any odd/error messages, try the card in a different slot, etc (sounds like a bus-mastering problem to me, maybe you can turn that off). Most likely you've done all these things and more. perhaps lspci will show something amiss on the pci bus, modinfo <modulenameforthecard> may reveal possible parameters for the module you can set at load-time with an "options modulename var=val..." line in /etc/modules.conf.
Yeah if i do f2-6 I get the same error spam etc...
I have tried other slots, with both cards, I have also tried just running one card, same problem.
Out of interest, I stuck an old SMC network card in to see if the PCI slot was buggered, and it worked fine, worked a treat. No errors etc. If only I didnt buy so many of the fn things.... (It said on the Netgear site that they are supported in RedHat)....
What would the lspci command show me ? ( ) ! Is there something specific that I should be looking for ? Also, the command for modinfo would then be - modinfo natsemi dp83815 ?! or like it shows in the config ... natsemi|dp83815
Aslo, do you think that the info on the chip is pointing me to a possible problem with the driver ? (eg written on the card is dp83816, driver running is dp83815).
There should only be one module associated with the netcard, so the modinfo command would be "modinfo modulename" where the "modulename" is most likely what comes after "alias eth0.." in your /etc/modules.conf, if you've got more than one "alias eth0..." lines there with differing modules on them, then one or the other is wrong. You should see the same module name turn up when you do "lsmod", which shows a list of all currently loaded modules.
You've configured these cards with different ip addresses? ie: /etc/sysconfig/network-scripts/ifcfg-eth0 & ifcfg-eth1 are defined correctly?
out of curiosity what does the output of "route" show you?
lspci, would show everything on the pci bus as linux sees it, "lspci -v" shows better info and should be used instead. You'd be looking for weirdness in irq's and/or io and memory addresses that linux thinks the devices are using. Look for "unknown device" lines also, but don't get too excited if you see them where they wouldn't affect the network controller.
If you type "dmesg | less" and using the arrow keys scroll down looking for "no known interrupt for pin X of device X", those are not good.
no other ideas as of yet, (of course I'll be passed out in a few hours, different timezones...) although I'll probably see the same docs you found I'll try a search on this device myself tomorrow.
I have just been told by a work mate that these cards just simply wont work with linux . I just dont understand why... I thought it was simply drivers because they work just uber slow with the errors.
Thanks for your help Bevis, it looks like this is a no brainer and i'll have to go and get all new network cards....
Any suggestions for cards that work well with RH9 ?
O/S Compatibility
All major operating systems are supported: Microsoft Windows, Microsoft NT, Novell NetWare, RedHat Linux, and SCO OpenServer Unix.
I bought this whole setup (Network Cards/Switch) because the rep said it was tried and tested, worked easy first go. Their tech support is hopeless, I still havent heard squat from them. It's great for the 24/7 support that comes with the product(s).
Wow, that is incredibly annoying, and you say that the card is listed as supported in linux on the netgear site? How can they say that?
Actually, and sadly, I didn't really help you at all, and getting stubborn hardware working in linux is my main pet project, to me, it's the one main obstacle linux needs to get over to gain wide acceptance. Windows (understandably) and Mac(can't figure out why) users invariably get a driver on the cd that comes in the box with the device, linux users have to come here, compile,install, and hopefully between all of us we can get them going.
You know what? send all those linux-rejects back, if the cards are that unfriendly to an OS that is so network-centric, then netgear doesn't deserve the revenue.
As for what to get, I'm partial to SMC cards, and/or no-name cards with a realtek chipset. The trick is to find out what chips are on the card *before* purchasing, which is difficult to do.
It's not so much about the brand-name, or lack thereof, it's mostly about the chipset on the card. To me, realtek works and works best, for the money.
oops, didn't answer the "full-duplex" question...I bought a lot of realtek-based pci netcards (made in taiwan) for $5 each (US dollars) which go full-duplex no problem with stock linux realtek modules. As a result, I really like realtek chips.
From reading thru the above plus a few more, I think that I need to use the natsemi driver from this page http://www.scyld.com/network/natsemi.html the natsemi.c file.
Few problems. First is I dont know if this driver is for RH9, second, I have no idea how to put this into the kernel and 'recompile' etc.
Can you help me out with this (last attempt before buying new network cards) driver ??
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.