Comment 16 for bug 226941

Revision history for this message
Khunphil (khunphil) wrote :

Hi,

Same symptoms here with Gutsy / 2.6.24.3 / AR5006EG / ndiswrapper 1.53./ XP driver

It sometimes cannot connect at boot. It seems that after a while (10mn), the link becomes ready. Sometimes, I try to connect with Wifi-radar during this time. I am not sure this helps. I think that there is a timeout somewhere in the process and after, the links becomes ready.

No hard freeze / just lost of time waiting for wifi waking-up.

/var/log/message
=========
Aug 6 09:41:18 IT kernel: [ 602.107150] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Aug 6 09:42:43 IT dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason
Aug 6 09:42:47 IT kernel: [ 649.233207] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Aug 6 09:42:50 IT dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.host_name
Aug 6 09:42:50 IT dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.domain_name
Aug 6 09:42:50 IT dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_domain
Aug 6 09:42:50 IT dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_servers
=========

My card : Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)

I did not try in Hardy by the way.

Philippe