You are not logged in.
Pages: 1
I don't know when the problem started, but lately whenever I reboot my computer (for example to use CentOS that's on the other partition), I'm not only losing the network - the LAN-indicators on modem and back side of the computer where the line is plugged in go off - but I cannot bring it back unless I turn the computer off and pull out the power cable and put it back again. Only then does the LAN - indicator lamp turn on!
Isn't that weird?
I noticed the LAN-indicator lamp goes off when Arch is shutting down the daemons such as the network.
Any ideas?
Last edited by new2arch (2009-04-16 19:20:32)
Offline
Try a different port and/or cable. Sounds like a bad wire or loose crystal (thats the jack thingy on the cable).
Offline
Try a different port and/or cable. Sounds like a bad wire or loose crystal (thats the jack thingy on the cable).
I've tried that with no success. Same problems.
It seems when the network shuts off, the hardware is affected somehow but I don't see why and how that could be.
Offline
I know some OSes can put the network card into 'sleep' mode or something similar.. Perhaps this is what's happening?
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
I know some OSes can put the network card into 'sleep' mode or something similar.. Perhaps this is what's happening?
If it were so, doesn't one need to configure this manually in a conf.file somewhere in order to benefit from that function?
Offline
If it were so, doesn't one need to configure this manually in a conf.file somewhere in order to benefit from that function?
Not sure... That would make sense, but I haven't had the 'pleasure' of having to deal with a NIC like this..
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
I've seen such a problem with dual boot with windows and in the case of realtek cards. The card would be detected in linux but no way to make it work.
The solution is to boot into windows, go to the device manager, driver properties and change something I can't recall exactly but had to do with wakeup from lan or something like that, by default the option is not to wakeup, if you change that then all works well.
I've seen reports (but never tested it) that going into the bios and changing the option "boot from lan" to on would also solve the problem.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Windows is known for incorrectly terminating DHCP leases. This problem can happen with e.g. rebooting into Linux after you booted into Windows before.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
Pages: 1