You are not logged in.
I have some issues with restoring the wired ethernet connection when waking from sleep. Sometimes it takes 1 or 2 minutes before it comes back up and sometimes it won't work at all unless I restart (usually when it has been in sleep for hours).
The network is configured to a static IP address in rc.conf. Hardware is a Zotac Zbox AD04 (AMD Fusion E450 system) using the r8169 driver. I guess this is probably a driver issue, but I wondered if there's anything else which I could do to solve the issue. I've tried adding r8169 to SUSPEND_MODULES, but that seems to make no difference.
Another issue is that the network is "unreachable" for about 30s to a minute after booting.
Could it be a problem with my router?
Last edited by shaurz (2012-04-13 01:03:13)
Offline
Really sounds like a problem with your NIC. My AD10 (with Realtek NIC as well) works as expected - connection up shortly after boot, and suspends and resumes just fine.
You should check your logs first if you want some pointers (and if you want meaningful suggestions from other people
).
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
I haven't really found anything much in my logs. From the kernel message log:
[ 3.457080] r8169 0000:02:00.0: eth0: link down
[ 3.457146] r8169 0000:02:00.0: eth0: link down
[ 3.458714] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 7.573639] EXT4-fs (sda3): re-mounted. Opts: discard,commit=0
[ 88.121693] r8169 0000:02:00.0: eth0: link up
[ 88.123403] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 98.483350] eth0: no IPv6 routers presentIt seems it took 84 seconds after initial setup for the network to come up...
Something a bit odd in errors.log:
Apr 12 20:20:07 zedbox kernel: [ 2.030578] SP5100 TCO timer: mmio address 0xbafe00 already in useLast edited by shaurz (2012-04-12 21:51:05)
Offline
OK this is weird... the sound was working perfectly ever since I set the system up, and now ALSA doesn't detect it any more!
Edit: Back after a reboot. I guess the audio was taken out by the sleep that time... usually it's OK.
Last edited by shaurz (2012-04-12 22:33:14)
Offline
I found the solution:
Install r8168 driver from community and blacklist r8169. This fixed all my issues. (lspci listed it as r8168).
It still takes about 10s after waking for the network to come back up, but at least it is reliable now.
Last edited by shaurz (2012-04-13 01:02:27)
Offline