2008-11-21 00:39:19

by Cyril Hrubis

[permalink] [raw]
Subject: zd1211rw breaks s2ram

Hi,
on my asus eee 1000h notebook, an Usb wifi with driver zd1211rw breaks
s2ram. Notebook hangs before suspending (with console on the screen)
and doesn't react to anyting but the power button. The dongle is
identified as:

idVendor 0x0ace ZyDAS
idProduct 0x1215 WLA-54L WiFi
bcdDevice 48.10
iManufacturer 16 ZyDAS
iProduct 32 USB2.0 WLAN

I'm using firmware version 4725 (that's default one in Gentoo), kernel
is vanilla 2.6.28-rc5.

When i run "ifconfig wlan0 up", I get 'ADDRCONF(NETDEV_UP): wlan0: link
is not ready' in dmesg, however scanning seems works fine.

--
metan


2008-11-21 05:54:28

by Rami Rosen

[permalink] [raw]
Subject: Re: zd1211rw breaks s2ram

Hello,

>When i run "ifconfig wlan0 up", I get 'ADDRCONF(NETDEV_UP): wlan0: link
>is not ready' in dmesg,

This message comes from IPv6; I suggest you ignore it. I also have this message
when using zd1211rw and it works fine. Disabling IPv6 on your machine,
if possible, will avoid this error.

To be more specific, this message is from addrconf_notify()
in net/ipv6/addrconf.c; this method is called when there is event of changing
flags of an interface.

Regards,
Rami Rosen




On Fri, Nov 21, 2008 at 2:39 AM, Cyril Hrubis <[email protected]> wrote:
> Hi,
> on my asus eee 1000h notebook, an Usb wifi with driver zd1211rw breaks
> s2ram. Notebook hangs before suspending (with console on the screen)
> and doesn't react to anyting but the power button. The dongle is
> identified as:
>
> idVendor 0x0ace ZyDAS
> idProduct 0x1215 WLA-54L WiFi
> bcdDevice 48.10
> iManufacturer 16 ZyDAS
> iProduct 32 USB2.0 WLAN
>
> I'm using firmware version 4725 (that's default one in Gentoo), kernel
> is vanilla 2.6.28-rc5.
>
> When i run "ifconfig wlan0 up", I get 'ADDRCONF(NETDEV_UP): wlan0: link
> is not ready' in dmesg, however scanning seems works fine.
>
> --
> metan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>