On Fri, 2006-02-24 at 09:31 -0500, Robert Love wrote:
> 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 ifconf
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 Networkm
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
> > networ
On Wednesday 22 February 2006 16:19, Robert Love wrote:
> e100 or e1000?
8139cp here. Seems to have picked up this behaviour since SL10.1beta2 or so,
still in beta4.
See https://bugzilla.novell.com/show_bug.cgi?id=151892
> `carrier' returns EINVAL if the device is not UP. It might be a bug in
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
>
Cc: networkamanger-list, as it seems now to be related to nm
On Wednesday 22 February 2006 00:49, Francois Romieu wrote:
> (owner of http://bugzilla.kernel.org/show_bug.cgi?id=5681 Cc:ed)
>
> Nikolaus Filus <[EMAIL PROTECTED]> :
> [...]
>
> > I'm using linux 2.6.14.3 with swsusp2 2.2rc14 (not the
