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'm still a newbie, but I have to echo what everyone here will probably agree with... "Linux kicks ass!!!!" ...only one problem though.
I have two Network cards in my machine, one is an asound 10/100 which uses an 8139 chip and the drivers that I got with it are fealnx.c and fealnx.o respectively. The other card is an NE2000 compatible. Linux has 8139too.o or so Linuxconf tells me when I try to set up the cards, I also have 8139.o which is all fine and great but I can't get either of these cards to work!!!
I have tried to everthing (except recompiling the kernel) and looked everywhere, but no luck!
And I know that both cards work on my Win2K drive! I can't ping myself (i.e. not my loopback address but the address I assigned to eth0 and eth1)
Does anyone have any idea why this is happening? Any info would be great...
Thanks...
PS when I try to assign a driver to either card from Linuxconfig ne displays as ne(install) or something to that effect... what does that mean anyway?
1) NEVER use linuxconf, it has a very wobbly history, screwing things up all over the place.
for the 8139 chipset use the 8139too driver, just make sure yo have a line saying "alias eth0 8129too" in your /etc/modules.conf and netconfig or any similar program should be fine with just that.
AFAIK all you should actually need to do is use netconfgi to create a /etc/sysconfig/network-scripts/ifcfg-eth0 file that reads approximately like...
Yeah we all make typos but I managed to figure out which one you meant though so all is cool... But I think I MAY (and I stress that I'm most likely wrong) have figured out what the problem is with my network cards is... still haven't found a solution though.
I assume that Linux just really does not like my choice of cards.
I've just removed the one to see if there was some sort of conflict between the two cards, but no luck!! :-(
I've just started reinstalling Linux, and from what I've gathered if my card is detected I would be given the option to set up the Network info from the installation but I don't get that...
I kept my NE2000 in which according to the Redhat HCL is compatible.
Hopefully someone out there knows what's going on, 'cause I sure as hell don't.
I went home yesterday with a Realtek 8029 and set that card up on my home system with no problem...
Kudzu popped up the minute Linux booted up which is great 'cause now I'll just get an 8029 card from one of the machines at work and use that on my Linux machine. Hopefully that will end my problems!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.