8139D NIC not working in mepis6.5
I have a GA7ZXR mobo, Athlon 1200 with an ebuyer NC100TX, 8139D-chip network card.
I installed mepis6.5 and it reports eth0 does not exist, and indeed there is no network access. I have also tried knoppix with the same result. ifconfig reports only the lo interface. I can't find an entry in dmesg relating to the NIC. lspci -v 0000:00:09.0 Ethernet controller: Hangzhou Silan Microelectronics Co RTL8139D [Realtek] ethernet adaptor... (no mention of an eth port) So I think mepis is detecting the card, why is it not working as eth0? TIA Kipper |
NIC as something else
Some Linux and Unix distros use other ids for the network card. Solaris for example uses pcn0, and FreeBSD uses fxp0, but then I have never seen a linux distro use anything other than eth0 except for wireless which would be wlan0. I would suggest to use the "ifconfig -a" switch so that it can tell you all NIC even if they do not have an IP address. You can also try "ifconfig eth0 up".
|
thanks for the reply,
ifconfig -a reports only the lo device, no eth* listed. and ifconfig eth0 up says "no such device" !! |
I say no drivers
I would say that your NIC is not setup then. I have never had that NIC before, but a quick little google shows me that some have had issues. I would research for linux drivers for your chipset. My quick little google make me think that you may just need to run "modprobe rtl8139" as the root user. At least the output may show you something.
|
modprobe rtl8139
FATAL... so I tried... modprobe 8139too which gave no output, does that mean it has done something? but still no eth0 showing, and I restarted the network. |
whats do these commands tell you?
lspci | grep -i ethernet dmesg | grep eth What does each tell you. Also you can try the following. modprobe 8139too and then to find out the outcome. dmesg | tail |
Fixed
Thanks for the replies, but I swapped the NIC for a lucent one and all's well...
kipper |
All times are GMT -5. The time now is 12:33 AM. |