Page 1 of 1

Ethernet Connections

Posted: Fri Jun 09, 2006 6:32 am
by romka
hi,

question - whenever i dont boot the computer with an ethernet cable connected - the device simply doesnt exist - i have to reboot with the ethernet plugged in, which as you can imagine is quite annoying.

any ideas as to the cause?

when i say it doesn't exist - that includes not only the Access Connections - but also the device manager.

thanks for any clues in advance

Posted: Fri Jun 09, 2006 4:19 pm
by kimx
Is this on battery, if so then it meant to be that way, and reaper when you incert the cable.

Posted: Fri Jun 09, 2006 4:54 pm
by Loof
My T60 (2007-4AU) does the same thing. However, the ethernet connection repairs itself within 30 seconds of plugging in the cable, all while running on battery.

Loof

Posted: Fri Jun 09, 2006 5:02 pm
by christopher_wolf
That is a new setting in the power management drivers. The ethernet port powers down when there is no cable plugged in. Plug it back in, no need to reboot, and it all comes back.

HTH :)

Posted: Fri Jun 09, 2006 5:40 pm
by astro
Ethernet port is supposed to power down when on battery. Just plug in the ethernet cable and it will wake up.

If it is really annoying, you can disable through the device manager I think. It is called "Deep Power Down" or something.

Posted: Fri Jun 09, 2006 11:52 pm
by romka
i find it very annoying actually so i might do that.

although - how long does it normally take for it to wake up from this deep state? as mine doesn't - from what i've noticed...

Posted: Sat Jun 10, 2006 6:14 pm
by Hamid
christopher_wolf wrote:That is a new setting in the power management drivers. The ethernet port powers down when there is no cable plugged in. Plug it back in, no need to reboot, and it all comes back.

HTH :)
So could this be the reason why some linux distros (like RHEL) don't detect the ethernet port while booting if the ethernet cable is not plugged in?

Posted: Tue Jun 13, 2006 6:08 am
by romka
just had the same thing - took the cable out for a few minutes.


then back in - and i let it stay in for 10 minutes - the ethernet interface NEVER woke up.

is this one faulty? as i had to restart to get it back up again.