| View previous topic :: View next topic |
| Author |
Message |
one_1
n00b
Joined: 19 Sep 2006
Posts: 7
|
 Posted: Tue Oct 03, 2006 10:25 am Post subject: missing network card [SOLVED] |
 |
|
I have a machine with 3 network devices on it, 1 on board and 2 pci cards. When I first installed gentoo (kernel 2.4.32-gentoo-r3) all 3 seemed to be detected as per
| Code: | Apr 18 13:06:48 cerberus via-rhine.c:v1.10-LK1.1.19 July-12-2003 Written by Donald Becker
Apr 18 13:06:48 cerberus http://www.scyld.com/network/via-rhine.html
Apr 18 13:06:48 cerberus eth0: VIA VT6102 Rhine-II at 0xec00, 00:0c:76:5f:e1:26, IRQ 11.
Apr 18 13:06:48 cerberus eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1.
Apr 18 13:06:48 cerberus PPP generic driver version 2.4.2
Apr 18 13:06:48 cerberus 8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
Apr 18 13:06:48 cerberus 8139cp: pci dev 00:06.0 (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
Apr 18 13:06:48 cerberus 8139cp: Try the "8139too" driver instead.
Apr 18 13:06:48 cerberus 8139cp: pci dev 00:07.0 (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
Apr 18 13:06:48 cerberus 8139cp: Try the "8139too" driver instead.
Apr 18 13:06:48 cerberus 8139too Fast Ethernet driver 0.9.26
Apr 18 13:06:48 cerberus eth1: RealTek RTL8139 at 0xde808000, 00:e0:4c:02:da:7c, IRQ 10
Apr 18 13:06:48 cerberus eth1: Identified 8139 chip type 'RTL-8100B/8139D'
Apr 18 13:06:48 cerberus eth2: RealTek RTL8139 at 0xde80a000, 00:e0:4d:06:b0:47, IRQ 11
Apr 18 13:06:48 cerberus eth2: Identified 8139 chip type 'RTL-8100B/8139D' |
I have not actually been using the eth2 network card and now want to use it, however it does'nt seem to pick up the eth2 network card anymore.
| Code: | Sep 29 15:04:06 cerberus via-rhine.c:v1.10-LK1.1.19 July-12-2003 Written by Donald Becker
Sep 29 15:04:06 cerberus http://www.scyld.com/network/via-rhine.html
Sep 29 15:04:06 cerberus eth0: VIA VT6102 Rhine-II at 0xec00, 00:0c:76:5f:e1:26, IRQ 11.
Sep 29 15:04:06 cerberus eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1.
Sep 29 15:04:06 cerberus PPP generic driver version 2.4.2
Sep 29 15:04:06 cerberus PPP Deflate Compression module registered
Sep 29 15:04:06 cerberus PPP BSD Compression module registered
Sep 29 15:04:06 cerberus 8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
Sep 29 15:04:06 cerberus 8139cp: pci dev 00:07.0 (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
Sep 29 15:04:06 cerberus 8139cp: Try the "8139too" driver instead.
Sep 29 15:04:06 cerberus 8139too Fast Ethernet driver 0.9.26
Sep 29 15:04:06 cerberus eth1: RealTek RTL8139 at 0xde808200, 00:e0:4d:06:b0:47, IRQ 11
Sep 29 15:04:06 cerberus eth1: Identified 8139 chip type 'RTL-8100B/8139D' |
this is the output from lspci
| Code: | 00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
00:05.0 System peripheral: Conexant ADSL AccessRunner PCI Arbitration Device (rev 01)
00:05.1 ATM network controller: Conexant AccessRunner PCI ADSL Interface Device (rev 01)
00:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Unknown device 9139 (rev 10)
00:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video (rev 01) |
ifconfig output:
| Code: | ifconfig | grep eth
eth0 Link encap:Ethernet HWaddr 00:0C:76:5F:E1:26
eth1 Link encap:Ethernet HWaddr 00:E0:4D:06:B0:47 |
Looks like it can see the card, but I'm unsure as to why its not working. I don't think I've changed anything that would stop it working - Would anyone be able to point me in the right direction as to how to solve this problem.
This is the first problem I have'nt been able to solve by searching the the forums/net etc, so I'm a bit stumped.
Thanks in advance.
Last edited by one_1 on Wed Oct 04, 2006 9:37 pm; edited 1 time in total |
|
| Back to top |
|
 |
fearofcarpet
Tux's lil' helper
Joined: 02 Apr 2005
Posts: 89
Location: Cambridge, MA
|
| Posted: Tue Oct 03, 2006 10:55 am Post subject: |
|
|
I had a similar problem in which my PCI NIC just stopped being seen. A kernell upgrade/recompile fixed it - I also had to add the driver to /etc/modules.autoload.d/ (until I decided to just compile it into the kernel). I have no explanation for this, but it was a VIA chipset... You might also walk through the Gentoo installation handbook section on installing your NICs (but from your installed OS rather than LiveCD) just for kicks.
Come to think of it, I had the same problem with an integrated Yukon gigabit NIC and fixed it the same way, but in that case I think it was a problem with the particular version of the driver (which was in its infancy at the time). Similar problem though in that lspci saw it, but when I loaded the driver I saw nothing in the dmesg output. |
|
| Back to top |
|
|
one_1
n00b
Joined: 19 Sep 2006
Posts: 7
|
| Posted: Tue Oct 03, 2006 11:23 am Post subject: |
|
|
| Will try recompiling the kernel and see if it works then. Mine is already compiled into the kernel. Thanks |
|
| Back to top |
|
|
one_1
n00b
Joined: 19 Sep 2006
Posts: 7
|
| Posted: Wed Oct 04, 2006 6:31 am Post subject: |
|
|
Ok, I've tried it and it did'nt make any difference  |
|
| Back to top |
|
|
fearofcarpet
Tux's lil' helper
Joined: 02 Apr 2005
Posts: 89
Location: Cambridge, MA
|
| Posted: Wed Oct 04, 2006 10:45 am Post subject: |
|
|
| You could try re-emerging baselayout (or system) - maybe a script got munched somewhere along the way...? If you haven't synced portage/updated in a while you should see just about everything get replaced/updated. |
|
| Back to top |
|
|
someone19
n00b
Joined: 26 Sep 2006
Posts: 51
|
| Posted: Wed Oct 04, 2006 2:19 pm Post subject: |
|
|
| Quote: | this is the output from lspci
Code:
<snip>
00:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Unknown device 9139 (rev 10)
00:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) |
It appears as though one of the network cards is either a different chipset or the hardware has become corrupted. Are the two network cards identical. Its possible the old module may have identified the other nic incorrectly, or as I said, the hardware has been corrupted and is now reporting the wrong model number.
A quick google search implies the existance of a realtek 9139 chipset, however, a search on the realtek website returns nothing for 9139.
Me thinks u got a paperweight. |
|
| Back to top |
|
|
one_1
n00b
Joined: 19 Sep 2006
Posts: 7
|
| Posted: Wed Oct 04, 2006 9:36 pm Post subject: |
|
|
Sure enough, replaced the network with another one of the same model and it worked lspci now contains the correct information:
| Code: |
00:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
|
Thanks for your help! |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
