Hi, Sorry to answer so late, but I had few time to do tests recently. Actually it seemed to work. The conditions of success are somewhat strange: sometimes I've to reboot and re-t!y so that the dhclient works, but... well. Well, so it worked, until today. I get this today: wl0: wlc_wme_setparams : no-clock On kernel 2.6.32, when I do iwlist scan then, the computer freezes fully. Really fully. The hardware crashes (RAM, CPU, etc.). On a 3.2.0 kernel, it doesn't, but wlan0 says that no scan possible as network not available. My laptop is a HP ProBook 6560b (LG652ET) Do you know such problem and any solution? Do you think it can be a hardware problem? I don't understand why my wifi would be locked, as I haven't done anything for that and I don't know how to achieve this. But I can try some unlock if you tell me the shortcut. Finally, a Debian Dev suggested me, a long time ago, a software to check locking and control locking of bluetooth/wifi hardware, but I don't remember it. Thanks for your help and I'm now more available to test and tweak if needed. Regards, Jean-Philippe MENGUAL Le mercredi 21 mars 2012 à 09:21 +0100, Arend van Spriel a écrit : > On 03/20/2012 06:52 PM, Jean-Philippe MENGUAL wrote: > > Hi, > > > > I use the 2.6.32 kernel on a Debian system. I use the module > > mac80211 for my Wifi card. But in more and more numerous cases, > > I cannot get an IP with dhclient. It fails. While it searches > > for one, I get: > > wl0: wlc_d11hdrs_mac80211: AC_BE txop exceeded phylen 366/186 > > > > Is it a bug in the module? I found some info but not about some > > patch or fix. Is there a fix in the recent kernel? What release > > should I use? If no patch, is there some workaround? > > > > Thanks, > > > > Sincerely, > > > > Jean-Philippe MENGUAL > > > > The message itself means that according to the driver we get a transmit > packet that exceeds the WMM txop. This message itself does not prevent > the packet from being transmitted. I have not seen the message lately in > recent driver versions. > > You can either try compat-wireless (see [1]), which should support > 2.6.32. Or you can try the latest 3.3 kernel. > > btw. 9 out of 10 times not getting an IP with dhclient means a problem > with security credentials/handshake/etc. So if the option above do not > solve your problems, we have to dive into that. > > Gr. AvS > > [1] http://linuxwireless.org/en/users/Download >
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
