Not able to get my Realtek 8139 to work in Debian 3.1
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Not able to get my Realtek 8139 to work in Debian 3.1
Hi, I am very new to the linux system and have recently installed Debian 3.1. During the installation i had trouble getting a network connection to be established via dhcp. because of this i tried installing another ethernet card in a pci slot only to have that not be able to connect with dhcp as well. So i installed it through the cd's. I have a Realtek RTL8139/810x Family fast ethernet NIC #2 and this is located on my motherboard which is a Soyo P4X400 DRAGON Ultra Platinum Edition. I have been trying to figure this thing out and it has been a real pain in the neck. Any help will be greatly appreciated.
My advice? Don't DHCP. DHCP just doesn't seem to work nearly as well as it should in the dozen or so distros I tried before settling on the one I use now. None of them really liked DHCP, and worked constantly, so in every case I was forced to hardset IP address, and DNS servers. That could be my routing equiptment not playing well with linux, or maybe it is just how some version work, I don't really know. Also in linux the DHCP and DNS, when they worked right, still seemed to take far longer than in Windows, so it never seemed worth it to me. Again, could just be my experience, but, that is my recommendation.
I have the same RealTek 8139 card as you, and am using Debian Sarge as well. Eveything installed well for me using DHCP. I am, however, using a router, which means the IP address doesn't change every time I reboot the system. Not sure how you would get around NOT using DHCP unless you have one, since most ISPs don't give you a static IP.
Maybe there is a hardware conflict. I know some PCI cards do not share resources with others. The simplest way to isolate the problem is to remove cards until it works. Hope this helps,
Last edited by harrygraham; 10-23-2005 at 11:25 PM.
You should post the file /etc/network/interfaces and the output of '/sbin/ifconfig'. Also check what drivers are loaded using 'lsmod' command. The 8139 driver is probably called '8139too'. If it is not loaded try loading it manually with 'modprobe 8139too' and check /sbin/ifconfig again.
Also check the output of dmesg for possible network/DHCP/driver errors (and of course make sure the cables are properly pushed home).
To give the add-on NIC its best chance you should probably also disable the on-board NIC in the BIOS.
Not sure what driver the on-board NIC needs. You could run 'lspci -v' and check the output for details (need to have the NIC enabled for this I expect).
The hardware and configuration looks OK to me. From the lspci lisiting the onboard NIC most likely uses the same 8139too driver as the card NIC. Since the card did not fix the problem it seems likely the onboard NIC is OK and the problem elsewhere.
You are not using DHCP. You have a static address at 192.168.1.100.
How do you know the network is not working? What have you tried to do? Are there any other machines or a router on your LAN?
Your system expects to find a router of some sort at 192.168.1.1. Do you have a router configured at that address? If you think you are using DHCP and you are not that could certainly give some problems.
I've had the same problem. Not only with Debian 3.1, but also Slackware 10.1, SuSe 10 and Mandrake 2005 edition. I get the same outputs as thread-starter, except that I've tried with both DHCP and Static.
Setting DNS in resolv.conf won't help either, since a ping to the router yields nothing more than "Destination host unreachable".
My box is configured as 192.168.0.101, Subnet 255.255.255.0, GW/DNS 192.168.0.1. I've tried using mii-tool to force Half Duplex, but it's of no use.
If anyone has any idea what could be wrong, It'd be appreciated. According to symptoms/outputs written earler in the thread, I think it's the exact same problem we're talking about here.
I've used several different NICs with 8139too driver and all worked fine (except once when the cable plug was not fully clicked in, giving similar problems). If network config is correct and driver loads without problems, it's hard to know what to suggest.
Someone fixed something similar on LQ a while ago:
In my experience, trouble getting dhcp working in Debian at install
comes from the fact that your network hasn't got a proper driver
in the list debian use when configuring the network.
I had to wait almost a year to get my Broadcom card supported,
you know why ? Because I didn't even think of burning a newer
netinstall cd, which are updated WEEKLY.
My advice, burn a newer one, chances are that your card is supported
Try that, you never know..
Ok let me help narrow it down a bit. The network i am sure is working cause this computer double boots win xp and debian 3.1. I have no problems with both cards in Win Xp. I also am connecting to a router. The other computer on it works fine as well. The onboard is the realtek 8139. The install cds are brand new i burned them the day of the first post. I really have no idea what to do. This is so frustrating. Everytime i want to try something i have to reboot into debian and then when it doesnt work i have to come back here cause i have no internet hehe hopefully i can get this thing up and running. The only thing i really did was install 8139too thats about all i tried.
So have you tried turning off APIC as suggested in the old LQ link above?
gives many reports of similar problems, and including success with turning off APIC.
The same site also contains some suggestions that Windows XP security patches were messing with the EEPROM on some network cards, making them stop working with linux. Not sure what became of that rumour.