Re: no carrier detection after resume from swsusp (8139too)

2006-02-24 Thread Nikolaus Filus
Hi, On Wednesday 22 February 2006 16:19, Robert Love wrote: On Wed, 2006-02-22 at 16:12 +0100, Nikolaus Filus wrote: I didn't look enough on this issue before. After resume, I get invalid argument from /sys/class/net/eth1/carrier. Reloading the driver *OR* restarting networkmanager

Re: no carrier detection after resume from swsusp (8139too)

2006-02-24 Thread Robert Love
On Fri, 2006-02-24 at 13:42 +0100, Nikolaus Filus wrote: That's it! No real problem or bug in driver or kernel. An ifconfig eth1 after resume is enough to recognise the plug-in of netwwork cable. BTW: I added an ifconfig up into my resume script, but shouldn't it be done by

Re: no carrier detection after resume from swsusp (8139too)

2006-02-22 Thread Robert Love
On Wed, 2006-02-22 at 16:12 +0100, Nikolaus Filus wrote: I didn't look enough on this issue before. After resume, I get invalid argument from /sys/class/net/eth1/carrier. Reloading the driver *OR* restarting networkmanager solves the problem! Is it possible a process like nm blocks some