On Sunday 07 September 2008 02:32:56 Larry Finger wrote: > Chr wrote: > > On Sunday 07 September 2008 01:33:29 Larry Finger wrote: > >> Chr wrote: > >>> But, for newer firmwares you'll need "p54: better firmware support" > >>> (cc4b0cbf4ab) as well. This changes were merged about 25-26 hours ago > >>> into wireless-testing, the only thing that isn't in yet is 802.11a > >>> support.... > >>> > >>> the LM87 firmware is this one: > >>> http://daemonizer.de/prism54/prism54-fw/fw-usb/2.13.1.0.arm.1 > >>> > >>> This link can be found on the driver's site too: > >>> http://linuxwireless.org/en/users/Drivers/p54 > >> > >> Thanks. That one fixed the ping problem. I had the latest > >> wireless-testing, and have added the patches you posted earlier today. > > > > Well, since you already do some testing here. Want more? ;-) > > > > I will be off for about 4-5 weeks and it would be very nice if someone > > with lots of broadcom hardware can test if the p54 works ADHOC & AP mode > > with them. > > > > i've already (successfully) tested Intel's 2915 & 4965, several atheros > > chipsets and another prism54 on different operating systems. > > > > But there could be problems with some broadcom chips. > > I'll see what I can do. > > After loading the new firmware, p54usb crapped out after the following > message was logged: > > phy9: not handling 0x02 type control frame > > After this, I had to unload and reload the driver. I have not yet had > time to check on it. > Do you have a big-endian machine by accident? Anyway control flags with 0x02 is some sort of scanning trap... These packages can be produces easily by setting chan->flags = 2 (or 4,6?) and setting the dwell timers as well in p54_set_freq. Since we don't do this, is there any chance you can hexdump the unknown/corrupted frames? and as a last shot: try another firmware, maybe this one works better for you. Regards, Chr
Attachment:
2.13.3.lm87.arm
Description: Binary data
