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 ressources, which are re-initialised by reloading the driver or
> restarting nm? Notice, that just stopping nm is not enough.
>
> Thanks in advance,
e100 or e1000?
`carrier' returns EINVAL if the device is not UP. It might be a bug in
NM if the device is not UP after a resume. What does `ifconfig eth1`
show before and after a resume?
Robert Love
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
