LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 07-17-2006, 12:16 AM   #1
kizersouzay
Member
 
Registered: Jul 2005
Location: Manchester, UK
Distribution: Slackware 14.2
Posts: 58

Rep: Reputation: 15
working with 2 similar network cards


By chance i have 2 network cards that are of similar type.One is built-in in the motherboard.While other is in the pci slot.Now i am having following problems.
1-I can't distinguish them in the OS i-e when is list them by using "lspci", both listed but i cant be sure which one in the list is refering to which physical card.
2-Kernel is installing the driver for only one card(as expected as it is mentioned in the Network administrators guide NAG).Now the problem is that some parameters are required to probe it by passing certain parameters(irq,base address,I/O address)where can i ger this information for my cards.I have intel eepro
 
Old 07-17-2006, 08:56 PM   #2
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,925
Blog Entries: 44

Rep: Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159
Quote:
Originally Posted by kizersouzay
By chance i have 2 network cards that are of similar type.One is built-in in the motherboard.While other is in the pci slot.Now i am having following problems.
1-I can't distinguish them in the OS i-e when is list them by using "lspci", both listed but i cant be sure which one in the list is refering to which physical card.
2-Kernel is installing the driver for only one card(as expected as it is mentioned in the Network administrators guide NAG).Now the problem is that some parameters are required to probe it by passing certain parameters(irq,base address,I/O address)where can i ger this information for my cards.I have intel eepro
Hi,

First, you state there are two nics in the machine. One is in the pci slot. Which slot? What card?

The on board is a intel, which chipset? What is the motherboard?

Machine manufacture?

Post the output from a terminal/cli (un-edited);

Code:
#dmesg |grep eth     #show the eth devices on boot
#lspci -vv          #you should be able to see irq and nic info
#lsmod              #modules
#ifconfig -a        #recognized

Last edited by onebuck; 07-18-2006 at 07:21 AM.
 
Old 07-18-2006, 06:42 AM   #3
archtoad6
Senior Member
 
Registered: Oct 2004
Location: Houston, TX (usa)
Distribution: MEPIS, Debian, Knoppix,
Posts: 4,727
Blog Entries: 15

Rep: Reputation: 234Reputation: 234Reputation: 234
I think you meant:
Code:
dmesg |grep eth
 
Old 07-18-2006, 07:22 AM   #4
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,925
Blog Entries: 44

Rep: Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159
Quote:
Originally Posted by archtoad6
I think you meant:
Code:
dmesg |grep eth
Hi,

Yes, just these big hands on a little laptop kybd.
 
Old 07-19-2006, 12:49 PM   #5
kizersouzay
Member
 
Registered: Jul 2005
Location: Manchester, UK
Distribution: Slackware 14.2
Posts: 58

Original Poster
Rep: Reputation: 15
ok,
that system was not mine but that of my friend
But on my system again there are two cards.Both in the pci slots.
here is the out put from the terminalKernel command line:

bash-3.00# dmesg | grep eth
Kernel command line: BOOT_IMAGE=Linux ro root=347 ether=0,0,eth0
e100: eth0: Intel(R) PRO/100 Network Connection

------------------------------
bash-3.00# lspci -vv
00:00.0 Host bridge: Intel Corp. 82815 815 Chipset Host Bridge and Memory Controller Hub (rev 02)
Subsystem: Intel Corp. D815EGEW Mainboard
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 0
Capabilities: [88] #09 [f104]

00:02.0 VGA compatible controller: Intel Corp. 82815 CGC [Chipset Graphics Controller] (rev 02) (prog-if 00 [VGA])
Subsystem: Intel Corp. D815EGEW Mainboard
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin A routed to IRQ 5
Region 0: Memory at f8000000 (32-bit, prefetchable) [disabled] [size=64M]
Region 1: Memory at feb80000 (32-bit, non-prefetchable) [disabled] [size=512K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB/ER Hub interface to PCI Bridge (rev 05) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: fc500000-fe9fffff
Prefetchable memory behind bridge: e4300000-f43fffff
BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B-

00:1f.0 ISA bridge: Intel Corp. 82801BA ISA Bridge (LPC) (rev 05)
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0

00:1f.1 IDE interface: Intel Corp. 82801BA IDE U100 (rev 05) (prog-if 80 [Master])
Subsystem: Intel Corp. D815EGEW Mainboard
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Region 4: I/O ports at ffa0 [size=16]

00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev 05) (prog-if 00 [UHCI])
Subsystem: Intel Corp. D815EGEW Mainboard
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin D routed to IRQ 10
Region 4: I/O ports at ef80 [size=32]

00:1f.3 SMBus: Intel Corp. 82801BA/BAM SMBus (rev 05)
Subsystem: Intel Corp. D815EGEW Mainboard
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin B routed to IRQ 9
Region 4: I/O ports at efa0 [size=16]

00:1f.5 Multimedia audio controller: Intel Corp. 82801BA/BAM AC'97 Audio (rev 05)
Subsystem: Intel Corp. D815EGEW Mainboard
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin B routed to IRQ 9
Region 0: I/O ports at e800 [size=256]
Region 1: I/O ports at ef00 [size=64]

01:09.0 Communication controller: Ambient Technologies Inc HaM controllerless modem (rev 02)
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 11
Region 0: Memory at fe9de000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at d800 [size=256]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

01:0a.0 VGA compatible controller: nVidia Corporation: Unknown device 0185 (rev c1) (prog-if 00 [VGA])
Subsystem: Unknown device 1682:201f
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (1250ns min, 250ns max)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at e8000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at fe9e0000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

01:0b.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 74)
Subsystem: 3Com Corporation 3C905C-TX Fast Etherlink for PC Management NIC
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (2500ns min, 2500ns max), cache line size 04
Interrupt: pin A routed to IRQ 3
Region 0: I/O ports at dc00 [size=128]
Region 1: Memory at fe9dfc00 (32-bit, non-prefetchable) [size=128]
Expansion ROM at fe9a0000 [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-

01:0c.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 05)
Subsystem: Compaq Computer Corporation NC3121 Fast Ethernet NIC (WOL)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (2000ns min, 14000ns max)
Interrupt: pin A routed to IRQ 9
Region 0: Memory at f43ff000 (32-bit, prefetchable) [size=4K]
Region 1: I/O ports at df80 [size=32]
Region 2: Memory at fe800000 (32-bit, non-prefetchable) [size=1M]
Expansion ROM at fe700000 [disabled] [size=1M]
Capabilities: [dc] Power Management version 1
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
----------------------------------
bash-3.00# lsmod
Module Size Used by Tainted: PF
ppp_deflate 3032 1 (autoclean)
zlib_deflate 18744 0 (autoclean) [ppp_deflate]
bsd_comp 4216 0 (autoclean)
ppp_async 6528 1 (autoclean)
ppp_generic 19364 3 (autoclean) [ppp_deflate bsd_comp ppp_async]
slhc 4592 1 (autoclean) [ppp_generic]
ham 14748 2
hamcore 511424 0 [ham]
snd-pcm-oss 36704 0 (unused)
snd-mixer-oss 12152 0 [snd-pcm-oss]
snd-intel8x0 18080 1
snd-ac97-codec 52472 0 [snd-intel8x0]
snd-pcm 54504 0 [snd-pcm-oss snd-intel8x0 snd-ac97-codec]
snd-timer 13412 0 [snd-pcm]
snd 31268 1 [snd-pcm-oss snd-mixer-oss snd-intel8x0 snd-ac97-codec snd-pcm snd-timer]
soundcore 3396 4 [snd]
snd-page-alloc 4712 0 [snd-mixer-oss snd-intel8x0 snd-pcm snd-timer snd]
3c59x 26544 0 (unused)
e100 47636 1
ide-scsi 9392 0
agpgart 45092 0 (unused)
bash-3.00#

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

bash-3.00# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:08:C7:73:BE:6E
inet addr:192.168.1.11 Bcast:192.168.1.255 Mask:255.255.255.0
UP 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:9 Base address:0xdf80 Memory:f43ff000-f43ff038

eth1 Link encap:Ethernet HWaddr 00:01:02:F7:68:59
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:3 Base address:0xdc00

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
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)

ppp0 Link encap:Point-to-Point Protocol
inet addr:203.148.67.124 P-t-P:203.148.64.3 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:6749 errors:0 dropped:0 overruns:0 frame:0
TX packets:7434 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:3236326 (3.0 Mb) TX bytes:1184571 (1.1 Mb)

bash-3.00#


I think the kernel is probing the driver for only one.How to get the other one working?
 
Old 07-20-2006, 07:20 AM   #6
archtoad6
Senior Member
 
Registered: Oct 2004
Location: Houston, TX (usa)
Distribution: MEPIS, Debian, Knoppix,
Posts: 4,727
Blog Entries: 15

Rep: Reputation: 234Reputation: 234Reputation: 234
I think your Q about your own system is very different from your friend's. To me, the output of ifconfig -a clearly shows that the kernel has found both cards, eth1 just hasn't been brought up yet.

With the card connected to a DHCP server, try each of the following (only one will work):
Code:
pump     eth1
dhcpcd   eth1
dhclient eth1

As for your friend's box, we probably need to see the actual output of the suggested commands. Try ifconfig -a 1st. If you see both NIC's, then he has the same problem you do & the other commands probably aren't necessary. If you do post the output from lspci -vv, consider removing the sections not related to the NIC's.
 
Old 07-27-2006, 06:39 AM   #7
kizersouzay
Member
 
Registered: Jul 2005
Location: Manchester, UK
Distribution: Slackware 14.2
Posts: 58

Original Poster
Rep: Reputation: 15
how can it be possible that both cards are "up"
when system boots.What settings are required
 
Old 07-27-2006, 12:52 PM   #8
archtoad6
Senior Member
 
Registered: Oct 2004
Location: Houston, TX (usa)
Distribution: MEPIS, Debian, Knoppix,
Posts: 4,727
Blog Entries: 15

Rep: Reputation: 234Reputation: 234Reputation: 234
What makes you think that a GNU/Linux box can't have 2 cards up at once?

How do you think a dedicated firewall appliance (like my SmoothWall Express) works?


As for the "required settings", the short answer is to find out where your system brings up the 1st card & add similar lines appropriate to the 2nd card. This will be somewhere in the init scripts. I can't be more helpful because I switched from RH8 to Debian (& later to MEPIS) about 3 years ago.

Last edited by archtoad6; 07-27-2006 at 12:53 PM. Reason: grammer
 
Old 07-27-2006, 04:18 PM   #9
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,925
Blog Entries: 44

Rep: Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159
Quote:
Originally Posted by kizersouzay
how can it be possible that both cards are "up"
when system boots.What settings are required
Hi,

The eth0 and eth1 devices were detected! You just have eth0 with a IP assignment.
Therefore both eth devices are not up! Just eth0.

You could look at this tutorial to get some guidelines.

If you would like to assign a IP to eth1 statically then as root from cli;
Code:
#ifconfig eth1 192.168.1.12       #incremented eth0 IP
#ifconfig -a                      #seee the assignment
#route -n                         #check routing table
You could edit the config file;

Code:
#vi /etc/sysconfig/network-scripts/ifcfg-eth0  #make changes and save
#vi /etc/sysconfig/network-scripts/ifcfg-eth1  #make changes and save
Or you could use the tui;

Code:
#/usr/sbin/system-config-network-tui
Of course you will have to init your network if you make changes. Once you make changes to the config files the assignments will be made.

This is all covered in the tutorial

A little google does wonders!

BTW, I agree that you should only post relevant information. Not the whole output of a command unless the output contains information about the problem at hand.

The command;
Code:
#lspci -vv                 #very verbose
A lot of what you posted for the lspci was not relevant to the problem.

Last edited by onebuck; 07-27-2006 at 04:25 PM.
 
Old 07-27-2006, 05:09 PM   #10
archtoad6
Senior Member
 
Registered: Oct 2004
Location: Houston, TX (usa)
Distribution: MEPIS, Debian, Knoppix,
Posts: 4,727
Blog Entries: 15

Rep: Reputation: 234Reputation: 234Reputation: 234
Nice answer, gwsandvik.

And thanks for reinforcing my suggestion about leaving out extraneous info. I almost didn't bother w/ this one because of it.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Network Cards not working FEDORA CORE 4 dssdave Linux - Wireless Networking 20 11-23-2005 01:22 PM
Two network cards, multihomed-public ips, not working? mikey3 Linux - Networking 5 11-04-2005 09:24 AM
Network cards - working under Linux RedHat 9.0 killer_bunny Linux - Networking 2 12-05-2003 09:44 AM
ip routing table. getting network cards working hamish Linux - Networking 2 11-30-2003 05:58 PM
What wireless network cards are working? raylpc Linux - General 7 08-12-2003 02:43 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 07:49 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration