netconfig in Slackware 12 does not recognize my active ethernet card
Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
netconfig in Slackware 12 does not recognize my active ethernet card
My computer contains two ethernet cards, one of which XP's Network Connections screen describes as "Network cable, unplugged, 3Com EtherLink XL 10/100 PCI TX NIC (3C905B-TX)", the other as "Connected, Firewalled, Intel(R) PRO/100 VE Network Connection"..
Fedora 3 and Ubuntu both recognize the connected card automatically.
Slackware 12's netconfig (with DHCP option) does not, and gives the message
No carrier detected on eth0
during boot. Is there a way via software, i.e., without removing one of the cards, to fix this?
eth0 Link encap:Ethernet HWaddr 00:10:4B:9E:1D:E3
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:18 Base address:0x4000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
which unfortunately tells me nothing.
P.S. Elizabethan English is hard enough.
This shows that you have only one eth device and that is 'eth0'. You do not have a 'IP'. 'Netconfig' only setups up the information for said device(s).
You can use the 'lspci -vv' to see all the devices.
If 'eth0' is the desired device then I would setup a static IP first, do as root from cli;
Code:
~#ifconfig -a #get recognized devices
~#ifconfig eth0 192.168.0.10 #set to a available IP
~#route add default gw 192.168.0.1 #set to your gateway
~#route -n #show the route table
~#ifconfig eth0 up #should be up already
~#ping 192.168.0.1 #ping your gateway
~#ping 208.69.32.130 #google.com IP
~#ping google.com #test DNS, if fail then
#check /etc/resolv.conf
You should have your '/etc/resolv.conf' setup with your 'ISP DNS' nameservers. After you find that the static works then use the information to edit or generate a new /etc/rc.d/rc.inet1.conf. You can restart init via the '/etc/rc.d/rc.inet1.conf restart' issue.
shows a module (driver) for the first one only (3c59x) -- "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI.
In your previous output from Windows, you show that NIC as not being used, and the Intel PRO/100 being used. Since a kernel module seems to be loaded, we have to wonder if there was something incorrectly setup with the "netconfig" command. If you know your gateway IP, the IP address of at least one DNS server, and think you can answer those questions, try using the "static IP" option while running "netconfig" again. Seems to me like at this point either (a) your router has no DHCP server running, or (b) something isn't correct with the module you have loaded.
If you would like to use Intel PRO/100 in Slackware instead of the 3Com card, this is what you should do. As root in a terminal issue "modprobe -r 3c59x" to remove that module. Then issue "modprobe e100" to insert the module for the Intel card. Next issue "/etc/rc.d/rc.inet1 restart" and then issue "ifconfig -a" to see if you have an address for the NIC.
EDIT: Just noticed something from your Windows output:
That's a pretty good reason that eth0 didn't get an IP address.
Rather than doing everything I have mentioned in the last two paragraphs, just move the cable from the other NIC (eth1) to that NIC (eth0), and then issue "/etc/rc.d/rc.inet1 restart"
Last edited by Bruce Hill; 03-06-2008 at 07:14 PM.
Reason: noticed the NIC is unplugged ...
I just happened across /etc/modeprobe.d/blacklist it appears the module for your intel card is blacklisted. You could comment out that line, issue "modprobe e100" and then issue "/etc/rc.d/rc.inet1 restart"
Or you could just switch the cables around as Bruce suggested.
mingdao@silas:~/kernel/linux-2.6.24.3$ less /etc/modprobe.d/blacklist
<snip>
# Alternate Intel EtherExpress Pro/100 support driver. List it
# here so it won't conflict with an already-loaded e100 module.
blacklist eepro100
<snip>
If so, there is no problem and he doesn't need to do anything there. Assuming his is the e100 -- the eepro100 and the e100 are different modules.
Actually he has two NICs ... see his first post and his closed thread. IMO it should have been merged, but at least we have the results to view.
<snip>
Thanks Bruce. I did not notice or see the previous thread. I would have advised differently with the added information. I agree that the posts should have been merged to assist in diagnosis.
Before you give up, try this. Okay I believe I have isolated the problem. login in as root. Then "nano /etc/modeprobe.d/blacklist". You will see this:
Code:
# Alternate Intel EtherExpress Pro/100 support driver. List it
# here so it won't conflict with an already-loaded eepro100 module.
blacklist e100
Change it to this:
Code:
# Alternate Intel EtherExpress Pro/100 support driver. List it
# here so it won't conflict with an already-loaded e100 module.
blacklist eepro100
blacklist 3c59x
Then reboot. This should block the module loading your 3com but allow your intel card which windows is using to connect to the internet. I don't believe you have edited any files so it should work. If you are unable to connect, rerun "netconfig". Good luck with all this and I hope it is not too confusing.
NB: The second and third commands will produces files named netconfigs and blacklist. You post those file contents here.
If for some reason your 3Com card won't work in Slackware, you can always change cables and use the Intel card. Then when you boot back into Windows, it will use the Intel card, also. There should be no problem with that setup.
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]="yes"
DHCP_HOSTNAME[0]=""
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]=""
DHCP_HOSTNAME[1]=""
IPADDR[2]=""
NETMASK[2]=""
USE_DHCP[2]=""
DHCP_HOSTNAME[2]=""
IPADDR[3]=""
NETMASK[3]=""
USE_DHCP[3]=""
DHCP_HOSTNAME[3]=""
GATEWAY=""
DEBUG_ETH_UP="no"
# the default 'eth4'
# 1360 when you use NAT'ed IPSec traffic.
# your default gateway
# server
# defined in rc.wireless.conf, by prepending
# 'WLAN_' to the parameter's name. Useful for
# those with multiple wireless interfaces.
# Some drivers require a private ioctl to be
# set through the iwpriv command. If more than
# one is required, you can place them in the
# IWPRIV parameter (space-separated, see the
# example).
You did not post the output of "ifconfig -a" and "route -a" and "lsmod".
However, if you have your ethernet cable plugged into the Intel PRO/100 NIC, and you have no module (driver) for it loaded, you will never get internet access. Your blacklist shows
Code:
blacklist e100
which is the module for the Intel PRO/100. This means your system is not loading the module (driver) for the NIC with the ethernet cable.
If you setup your system properly, then we can help you. If you continue to expect the NIC without a cable to work, we can't help you.
To summarize: if you want to use the Intel NIC, you must blacklist the 3Com NIC and then setup the Intel one as eth1. If you want to use the 3Com NIC, then you must plug the cable into it and setup eth0, and blacklist the Intel NIC.
So you post back which NIC you want to use, and I'll post the files with proper edits and commands to make it work.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.