| View previous topic :: View next topic |
| Author |
Message |
pomaranca
Tux's lil' helper
Joined: 26 Mar 2006
Posts: 87
Location: ljubljana
|
 Posted: Fri Aug 14, 2009 8:47 am Post subject: NIC stops working after suspend to ram |
 |
|
I have this strange NIC problem: My computer has two network interfaces, one is integrated and the other is in a PCI slot. When i normally start my computer both work just fine. But when i suspend it to RAM (which i do very often) and wake it up, my onboard nVidia NIC which is called eth1 stops working. I am thus unable to connect to my local network but eth0 works ok.
The output of ifconfig looks just fine:
| Code: |
~ # ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:11:6b:00:5b:03
inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.255.255 Mask:255.255.0.0
inet6 addr: fe80::211:6bff:fe00:5b03/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:45606 errors:0 dropped:0 overruns:0 frame:0
TX packets:36518 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:47726419 (45.5 MiB) TX bytes:5830181 (5.5 MiB)
Interrupt:18 Base address:0xac00
eth1 Link encap:Ethernet HWaddr 00:1d:60:f8:25:b6
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:23807 errors:1 dropped:0 overruns:0 frame:1
TX packets:28856 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1453013 (1.3 MiB) TX bytes:43054913 (41.0 MiB)
Interrupt:25 Base address:0xa000
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:25559 errors:0 dropped:0 overruns:0 frame:0
TX packets:25559 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1482069 (1.4 MiB) TX bytes:1482069 (1.4 MiB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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)
teql0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP 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:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
|
But ethtool tells me that there is no link, although the network cable is connected and the lights on the NIC socket are lit up:
| Code: |
~ # ethtool eth1
Settings for eth1:
Supported ports: [ MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: Unknown! (65535)
Duplex: Unknown! (255)
Port: MII
PHYAD: 1
Transceiver: external
Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Link detected: no
|
Speed and duplex are also not shown (at normal startup they are).
These are dmesg messages concerning eth1:
| Code: |
~ # dmesg | grep eth1
[ 4227.289510] eth1: no link during initialization.
[ 4227.290666] ADDRCONF(NETDEV_UP): eth1: link is not ready
|
|
|
| Back to top |
|
 |
VinzC
Watchman
Joined: 17 Apr 2004
Posts: 5098
Location: Dark side of the mood
|
| Posted: Fri Aug 14, 2009 9:56 am Post subject: |
|
|
Suspending and hibernating often lead to network troubles -- from what I've seen at least. You must unload the module before suspending and reload it afterwards.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739! |
|
| Back to top |
|
|
|
Networking & Security
