netconfig in Slackware 12 does not recognize my active ethernet card

arejay · 03-05-2008, 11:47 AM

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?

symatic · 03-05-2008, 10:21 PM

run "ifconfig -a" this will tell you where your cards are. Edit /etc/rc.d/rc.inet1.conf to set them up. www.slackbook.org should help.

arejay · 03-06-2008, 07:20 AM

Running

ipxconfig -a

produced

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.

onebuck · 03-06-2008, 11:17 AM

Hi,

Quote:

Originally Posted by arejay

Running

ipxconfig -a

produced

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.

Bruce Hill · 03-06-2008, 07:08 PM

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.

Quote:

Originally posted by arejay

1) lspci | grep -i ethernet replied with

Code:

06:02.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 24)
06:08.0 Ethernet controller: Intel Corporation 82562ET/EZ/GT/GZ - PRO/100 VE (LOM) Ethernet Controller (rev 01)

So you have two NICs -- eth0 and eth1.

However, the output of lsmod:

Code:

2) ls mod replied with

Module Size Used by
snd_seq_dummy 6788 0
snd_seq_oss 32896 0
snd_seq_midi_event 10112 1 snd_seq_oss
snd_seq 50640 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 10508 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 42784 0
snd_mixer_oss 18048 1 snd_pcm_oss
ipv6 254496 12
pcmcia 34988 0
pcmcia_core 36500 1 pcmcia
capability 7304 0
commoncap 9344 1 capability
lp 13736 0
parport_pc 27812 1
parport 34760 2 lp,parport_pc
pcspkr 6528 0
psmouse 39048 0
iTCO_wdt 12964 0
iTCO_vendor_support 7172 1 iTCO_wdt
3c59x 43176 0
mii 8576 1 3c59x
serio_raw 9220 0
sg 30364 0
snd_hda_intel 20248 0
snd_hda_codec 209152 1 snd_hda_intel
snd_pcm 72068 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
snd_timer 22532 2 snd_seq,snd_pcm
snd 47204 9 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_hda_codec,snd_pcm,snd _timer
soundcore 9824 1 snd
snd_page_alloc 11528 2 snd_hda_intel,snd_pcm
intel_agp 25116 1
agpgart 31432 1 intel_agp
shpchp 33172 0
i2c_i801 11408 0
evdev 11904 1
ata_generic 9220 0

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:

Quote:

Network cable, unplugged, 3Com EtherLink XL 10/100 PCI TX NIC (3C905B-TX)

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"

symatic · 03-06-2008, 10:41 PM

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.

Bruce Hill · 03-06-2008, 11:02 PM

symatic,

Is this what you're talking about:

Code:

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.

symatic · 03-07-2008, 01:05 AM

Bruce,

here is my /etc/modeprobe.d/blacklist

Code:

# Alternate Intel EtherExpress Pro/100 support driver.  List it
# here so it won't conflict with an already-loaded eepro100 module.
blacklist e100

Mine appears different then yours. If his is like mine then I believe this to be the problem.

onebuck · 03-07-2008, 07:44 AM

Hi,

Quote:

Originally Posted by Bruce Hill

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.

arejay · 03-07-2008, 11:35 AM

I appreciate all the suggested software solutions, but none has solved the problem, so I'll have to look at the cards and cables next.

Can anyone tell me if making such hardware changes will mess up my XP networking setup, and if so how to repair this?

symatic · 03-07-2008, 02:20 PM

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.

arejay · 03-07-2008, 04:47 PM

sorry, no cigar

Bruce Hill · 03-07-2008, 04:55 PM

Reboot the box then issue and post the output of:

Code:

ifconfig -a
egrep -v "(^#|^ *$)" /etc/rc.d/rc.inet1.conf > netconfigs
egrep -v "(^#|^ *$)" /etc/modprobe.d/blacklist > blacklist
route -n
lsmod

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.

arejay · 03-07-2008, 05:46 PM

NETCONFIGS:

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).

------------

BLACKLIST:

blacklist psmouse
blacklist pcspkr
blacklist de4x5
blacklist dmfe
blacklist evbug
blacklist e100
blacklist 8139cp
blacklist hostap_cs
blacklist hostap_pci
blacklist hostap_plx
blacklist hostap
blacklist eth1394
blacklist i8xx_tco
blacklist hw_random
blacklist via-ircc
blacklist snd-atiixp-modem
blacklist snd-intel8x0m
blacklist snd-via82xx-modem
blacklist ac97
blacklist ac97_codec
blacklist aci
blacklist ad1816
blacklist ad1848
blacklist ad1889
blacklist adlib_card
blacklist aedsp16
blacklist ali5455
blacklist awe_wave
blacklist btaudio
blacklist cmpci
blacklist cs4232
blacklist cs4281
blacklist cs46xx
blacklist emu10k1
blacklist es1370
blacklist es1371
blacklist esssolo1
blacklist forte
blacklist gus
blacklist i810_audio
blacklist kahlua
blacklist mad16
blacklist maestro
blacklist maestro3
blacklist maui
blacklist mpu401
blacklist msnd
blacklist msnd_classic
blacklist msnd_pinnacle
blacklist nm256_audio
blacklist opl3
blacklist opl3sa
blacklist opl3sa2
blacklist pas2
blacklist pss
blacklist rme96xx
blacklist sb
blacklist sb_lib
blacklist sgalaxy
blacklist sonicvibes
blacklist sound
blacklist sscape
blacklist trident
blacklist trix
blacklist uart401
blacklist uart6850
blacklist v_midi
blacklist via82cxxx_audio
blacklist wavefront
blacklist ymfpci
blacklist arcfb
blacklist aty128fb
blacklist atyfb
blacklist cirrusfb
blacklist clgenfb
blacklist cyber2000fb
blacklist fbcon-cfb2
blacklist fbcon-cfb4
blacklist fbcon-hga
blacklist fbcon-mfb
blacklist fbcon-vga-planes
blacklist fbgen
blacklist hgafb
blacklist i2c-matroxfb
blacklist i810fb
blacklist intelfb
blacklist kyrofb
blacklist matroxfb_DAC1064
blacklist matroxfb_Ti3026
blacklist matroxfb_accel
blacklist matroxfb_base
blacklist matroxfb_crtc2
blacklist matroxfb_g450
blacklist matroxfb_maven
blacklist matroxfb_misc
blacklist neofb
blacklist nvidiafb
blacklist pm2fb
blacklist pm3fb
blacklist radeonfb
blacklist rivafb
blacklist savagefb
blacklist sisfb
blacklist sstfb
blacklist tdfxfb
blacklist tridentfb
blacklist vga16fb
blacklist 3w-xxxx
blacklist 53c7,8xx
blacklist AM53C974
blacklist BusLogic
blacklist NCR53c406a
blacklist a100u2w
blacklist advansys
blacklist aha152x
blacklist aha1542
blacklist aha1740
blacklist aic79xx
blacklist aic7xxx
blacklist aic7xxx_old
blacklist ata_piix
blacklist atp870u
blacklist cpqfc
blacklist dc395x
blacklist dmx3191d
blacklist dpt_i2o
blacklist dtc
blacklist eata
blacklist eata_dma
blacklist eata_pio
blacklist fdomain
blacklist g_NCR5380
blacklist g_NCR5380_mmio
blacklist gdth
blacklist ide-scsi
blacklist imm
blacklist in2000
blacklist initio
blacklist ipr
blacklist ips
blacklist libata
blacklist megaraid
blacklist ncr53c8xx
blacklist nsp32
blacklist osst
blacklist pas16
blacklist pci2000
blacklist pci2220i
blacklist ppa
blacklist psi240i
blacklist qla1280
blacklist qla2100
blacklist qla2200
blacklist qla2300
blacklist qla2322
blacklist qla2xxx
blacklist qla6312
blacklist qla6322
blacklist qlogicfas
blacklist qlogicfas408
blacklist qlogicfc
blacklist qlogicisp
blacklist seagate
blacklist sim710
blacklist sata_promise
blacklist sata_sil
blacklist sata_sis
blacklist sata_svw
blacklist sata_sx4
blacklist sata_via
blacklist sata_vsc
blacklist scsi_debug
blacklist scsi_transport_fc
blacklist scsi_transport_spi
blacklist sym53c416
blacklist sym53c8xx
blacklist sym53c8xx
blacklist t128
blacklist tmscsim
blacklist u14-34f

Bruce Hill · 03-07-2008, 06:07 PM

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.