Re: [b43] opensource firmware
2009/1/14 Lorenzo Nava navalor...@gmail.com: we completed the 1st version of initvals. They are available at http://www.ing.unibs.it/openfwwf . Currently only binary version is available: don't worry, we will publish source code as soon as possible!! This first version is a test version: please try it and let us know if everythink is ok... Today we have also tested a new firmware version that works with WPA2- personal (both TKIP and CCMP) and WPA2-enterprise (EAP-TTLS) (tested on 4306 and 4318 PCI device). If anybody was interested please try new firmware with encryption and let us know if it works correctly, thanks! Initvals and new firmware version can be found at http://www.ing.unibs.it/openfwwf I belive you still need testing? I used openfwwf-5.0.tar.gz and initvals.tar.gz for my bcm4318 card in Acer Aspire 5024 (qos=0). Scanning works fine, connecting to WPA Personal network also. I can't check speed performance as I don't have antenna connected to my card (notebook lid just gone... I belive Acer explains that situation to you?). As for stability it's great. I downloaded 100MB, left notebook for 24h and then downloaded another 50MB. So to sum up: I don't feel any difference between opensource and broardcom's firmware. -- Rafał Miłecki ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
Hello everyone, we just made available a new opensource firmware version, download at http://www.ing.unibs.it/openfwwf New features: - initvals source code added, initvals files are encoded by make process - firmware is now recognized as opensource, though still as version 351 (old format). Firmware's date switched to - watchdog implemented Tested with kernel 2.6.29-rc2-wl. Cheers, -FG ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
On Wednesday 21 January 2009 18:29:40 Francesco Gringoli wrote: Hello everyone, we just made available a new opensource firmware version, download at http://www.ing.unibs.it/openfwwf New features: - initvals source code added, initvals files are encoded by make process - firmware is now recognized as opensource, though still as version 351 (old format). Firmware's date switched to - watchdog implemented Note that the debug-IRQ feature is now also available to you. It enables you to panic, dump SHM, dump regs and print a marker message from within the firmware. See my openfw repository and handle_irq_ucode_debug() in b43 for details. Note that the debug-IRQ is synchronous, so it will disturb MAC functionality. But you only want to use it for debugging anyway. And for debugging it is _very_ convenient to be able to issue printks and memory dumps from within the firmware code. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
On Friday 16 January 2009 00:01:41 Francesco Gringoli wrote: On Jan 15, 2009, at 4:59 PM, Larry Finger wrote: Michael Buesch wrote: Yes, please introduce a feature-bitfield at some location in SHM that's unused by the proprietary firmware. This bitfields would contain a bit for QoS and a bit for hwcrypto. Also change your firmware so the driver detects it as open-source firmware. I think that's done by writing 0x to the date/time field in SHM. I don't quite remember, but it's something like that. Note that this might mean that the firmware watchdog in the driver will trigger, as that's enabled by the open-source-firmware-flag. We might want to temporarly disable the watchdog in the driver for the time being. I like the idea of encoding the capabilities in the firmware as it would be a self-documenting method as the firmware evolves. Is using the Broadcom names for the firmware the best course of action? What if the opensource firmware files were named something like os-ucode5.fw, etc. and b43 were coded to check for those files first? It would then fall back to the standard firmware if the opensource version is not found. Larry It could be interesting to also not separate the initvalues in two different files, everything could be coded in a single file. Never understood why original init values are split in two files. The normal initvalues have to be uploaded at init and the bandswitch init values have to be uploaded on bandswitch. That's a different thing. We currently implement bandswitch by re-initing, but that doesn't matter. We could easily change that in future. So don't put the initvals into one file. Michael: SHM(0x0014) (16bit) is not used by the open source firmware, Eh no. You need to find an offset that's not used by the PROPRIETARY firmware. A question: is the standard kernel aware that date set to indicates an opensource firmware Yes. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
On Friday 16 January 2009 00:17:43 Kyle McMartin wrote: On Thu, Jan 15, 2009 at 05:09:49PM +0100, Michael Buesch wrote: Already implemented here: http://bu3sch.de/patches/wireless-testing/20081227-1821/patches/008-b43-probe-open-fw.patch I just need to fix a leak in an error path before pushing that upstream. Groovy, I had cooked a similar patch for Fedora but haven't gotten around to packaging up the fw yet. Will sub in yours. I think we can actually push my patch upstream. The remaining FIXME is not relevant for the common case and it only matters in rare circumstances (I think A-PHY only, which isn't implemented anyway). So we can fix it later. The patch should work properly as-is for G/N/LP-PHY. It probably needs a rediff against a current b43, however. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
Pardon me, but those filenames are identical and contain no numbers. Did those get stripped off somewhere? I did a mistake. The correct name are b0g0bsinitvals5.fw and b0g0initvals5.fw for revision 5. Sorry Cheers Lorenzo ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
Lorenzo Nava wrote: Yes, you're right. Actually there are 2 ways to make firmware works: 1) Disable hw crypto with module parameter 2) Remove pcm5.fw from your /lib/firmware/b43 directory When I run the firmware I never include pcm5.fw file. The only initvals really necessary are b0g0bsinitvals.fw and b0g0bsinitvals.fw. Pardon me, but those filenames are identical and contain no numbers. Did those get stripped off somewhere? cheers Lorenzo Larry Finger had written: Great job. Larry Absolutely Ehud -- Legal Disclaimer that you are now contractually bound to under all laws with no recourse: http://attrition.org/security/rants/z/disclaimers.html ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
On Wednesday 14 January 2009 21:45:22 Johannes Berg wrote: Initvals and new firmware version can be found at http://www.ing.unibs.it/openfwwf I suggest that before this is packaged, we change it so b43 can recognise it and automatically disable qos and hwcrypto. Yes, please introduce a feature-bitfield at some location in SHM that's unused by the proprietary firmware. This bitfields would contain a bit for QoS and a bit for hwcrypto. Also change your firmware so the driver detects it as open-source firmware. I think that's done by writing 0x to the date/time field in SHM. I don't quite remember, but it's something like that. Note that this might mean that the firmware watchdog in the driver will trigger, as that's enabled by the open-source-firmware-flag. We might want to temporarly disable the watchdog in the driver for the time being. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
On Thursday 15 January 2009 16:37:57 Michael Buesch wrote: On Wednesday 14 January 2009 21:45:22 Johannes Berg wrote: Initvals and new firmware version can be found at http://www.ing.unibs.it/openfwwf I suggest that before this is packaged, we change it so b43 can recognise it and automatically disable qos and hwcrypto. Yes, please introduce a feature-bitfield at some location in SHM that's unused by the proprietary firmware. This bitfields would contain a bit for QoS and a bit for hwcrypto. Also change your firmware so the driver detects it as open-source firmware. I think that's done by writing 0x to the date/time field in SHM. I don't quite remember, but it's something like that. Note that this might mean that the firmware watchdog in the driver will trigger, as that's enabled by the open-source-firmware-flag. We might want to temporarly disable the watchdog in the driver for the time being. Ah and also note that hwcrypto is already automagically disabled, if the driver detects an opensource-firmware. To make the driver detect the firmware as opensource, write 0x to SHM_UCODEDATE You need to disable the watchdog in b43_periodic_every15sec(), if you don't implement the watchdog mechanism in your firmware. But it's pretty easy to implement. It just has to write 0 to some register in the MAC loop. Of course, the register has to be unused in the rest of the code. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
Michael Buesch wrote: Yes, please introduce a feature-bitfield at some location in SHM that's unused by the proprietary firmware. This bitfields would contain a bit for QoS and a bit for hwcrypto. Also change your firmware so the driver detects it as open-source firmware. I think that's done by writing 0x to the date/time field in SHM. I don't quite remember, but it's something like that. Note that this might mean that the firmware watchdog in the driver will trigger, as that's enabled by the open-source-firmware-flag. We might want to temporarly disable the watchdog in the driver for the time being. I like the idea of encoding the capabilities in the firmware as it would be a self-documenting method as the firmware evolves. Is using the Broadcom names for the firmware the best course of action? What if the opensource firmware files were named something like os-ucode5.fw, etc. and b43 were coded to check for those files first? It would then fall back to the standard firmware if the opensource version is not found. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
On Thursday 15 January 2009 16:59:11 Larry Finger wrote: Michael Buesch wrote: Yes, please introduce a feature-bitfield at some location in SHM that's unused by the proprietary firmware. This bitfields would contain a bit for QoS and a bit for hwcrypto. Also change your firmware so the driver detects it as open-source firmware. I think that's done by writing 0x to the date/time field in SHM. I don't quite remember, but it's something like that. Note that this might mean that the firmware watchdog in the driver will trigger, as that's enabled by the open-source-firmware-flag. We might want to temporarly disable the watchdog in the driver for the time being. I like the idea of encoding the capabilities in the firmware as it would be a self-documenting method as the firmware evolves. Is using the Broadcom names for the firmware the best course of action? What if the opensource firmware files were named something like os-ucode5.fw, etc. and b43 were coded to check for those files first? It would then fall back to the standard firmware if the opensource version is not found. Already implemented here: http://bu3sch.de/patches/wireless-testing/20081227-1821/patches/008-b43-probe-open-fw.patch I just need to fix a leak in an error path before pushing that upstream. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
On Jan 15, 2009, at 4:59 PM, Larry Finger wrote: Michael Buesch wrote: Yes, please introduce a feature-bitfield at some location in SHM that's unused by the proprietary firmware. This bitfields would contain a bit for QoS and a bit for hwcrypto. Also change your firmware so the driver detects it as open-source firmware. I think that's done by writing 0x to the date/time field in SHM. I don't quite remember, but it's something like that. Note that this might mean that the firmware watchdog in the driver will trigger, as that's enabled by the open-source-firmware-flag. We might want to temporarly disable the watchdog in the driver for the time being. I like the idea of encoding the capabilities in the firmware as it would be a self-documenting method as the firmware evolves. Is using the Broadcom names for the firmware the best course of action? What if the opensource firmware files were named something like os-ucode5.fw, etc. and b43 were coded to check for those files first? It would then fall back to the standard firmware if the opensource version is not found. Larry It could be interesting to also not separate the initvalues in two different files, everything could be coded in a single file. Never understood why original init values are split in two files. Michael: SHM(0x0014) (16bit) is not used by the open source firmware, I know the b43 reads core revision from SHM(0x0016). Normally SHM(0x0014) is set to zero. We can put fw capabilities here (0x0014), e.g.: - bit 0: [0 state that encryption should be handled by b43] - bit 1: [0 state that qos is not supported] We can prepare a firmware image with such feature + watchdog. Posting ASAP with new initvals (less values). A question: is the standard kernel aware that date set to indicates an opensource firmware or some define should be activated on compilation? Cheers, -FG ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
[b43] opensource firmware
Hello everybody, we completed the 1st version of initvals. They are available at http://www.ing.unibs.it/openfwwf . Currently only binary version is available: don't worry, we will publish source code as soon as possible!! This first version is a test version: please try it and let us know if everythink is ok... Today we have also tested a new firmware version that works with WPA2- personal (both TKIP and CCMP) and WPA2-enterprise (EAP-TTLS) (tested on 4306 and 4318 PCI device). If anybody was interested please try new firmware with encryption and let us know if it works correctly, thanks! Initvals and new firmware version can be found at http://www.ing.unibs.it/openfwwf Cheers Lorenzo Nava Francesco Gringoli ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
On Wed, Jan 14, 2009 at 04:30:47PM +0100, Lorenzo Nava wrote: Hello everybody, we completed the 1st version of initvals. They are available at http://www.ing.unibs.it/openfwwf . Currently only binary version is available: don't worry, we will publish source code as soon as possible!! This first version is a test version: please try it and let us know if everythink is ok... Today we have also tested a new firmware version that works with WPA2- personal (both TKIP and CCMP) and WPA2-enterprise (EAP-TTLS) (tested on 4306 and 4318 PCI device). If anybody was interested please try new firmware with encryption and let us know if it works correctly, thanks! Initvals and new firmware version can be found at http://www.ing.unibs.it/openfwwf Awesome...awesome...awesome!!! -- John W. LinvilleSomeday the world will need a hero, and you linvi...@tuxdriver.com might be all we have. Be ready. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
Great! Thank you very much for the help... qos=0 parameter was still needed, so it is correct. cheers Lorenzo Nava. On Jan 14, 2009, at 4:57 PM, Buran Ayuthia wrote: My 4311 rev 01 card still works with the new initvals and firmware using WPA2-personal (both TKIP and CCMP) and without encyrption. I am still loading the module using modprobe b43 qos=0. Buran Ayuthia On Wed, Jan 14, 2009 at 9:30 AM, Lorenzo Nava navalor...@gmail.com wrote: Hello everybody, we completed the 1st version of initvals. They are available at http://www.ing.unibs.it/openfwwf . Currently only binary version is available: don't worry, we will publish source code as soon as possible!! This first version is a test version: please try it and let us know if everythink is ok... Today we have also tested a new firmware version that works with WPA2- personal (both TKIP and CCMP) and WPA2-enterprise (EAP-TTLS) (tested on 4306 and 4318 PCI device). If anybody was interested please try new firmware with encryption and let us know if it works correctly, thanks! Initvals and new firmware version can be found at http://www.ing.unibs.it/openfwwf Cheers Lorenzo Nava Francesco Gringoli ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
Lorenzo Nava wrote: Today we have also tested a new firmware version that works with WPA2-personal (both TKIP and CCMP) and WPA2-enterprise (EAP-TTLS) (tested on 4306 and 4318 PCI device). If anybody was interested please try new firmware with encryption and let us know if it works correctly, thanks! On my BCM4318 (Linksys WPC54G, Ver 3) in a Cardbus format in a WPA2-personal encrypted network with AES algorithm, it nearly worked. With your firmware, it can scan and authenticate. It even gets an DHCP-supplied IP address; however, I get no data through the link. In addition, I see lots of PHY TRANSMISSION ERRORS. When I disable hardware encryption (nohwcrypt=1), then it works. Great job. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
On Wednesday 14 January 2009 18:43:27 Larry Finger wrote: Lorenzo Nava wrote: Today we have also tested a new firmware version that works with WPA2-personal (both TKIP and CCMP) and WPA2-enterprise (EAP-TTLS) (tested on 4306 and 4318 PCI device). If anybody was interested please try new firmware with encryption and let us know if it works correctly, thanks! On my BCM4318 (Linksys WPC54G, Ver 3) in a Cardbus format in a WPA2-personal encrypted network with AES algorithm, it nearly worked. With your firmware, it can scan and authenticate. It even gets an DHCP-supplied IP address; however, I get no data through the link. In addition, I see lots of PHY TRANSMISSION ERRORS. When I disable hardware encryption (nohwcrypt=1), then it works. Support for hardware crypto would require to reverse engineer the PCM firmware, first. So we can't support hw-crypto, except on new devices that don't have a PCM anymore. But these are not rev5 cores :) -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
Initvals and new firmware version can be found at http://www.ing.unibs.it/openfwwf I suggest that before this is packaged, we change it so b43 can recognise it and automatically disable qos and hwcrypto. johannes signature.asc Description: This is a digitally signed message part ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
On Wed, Jan 14, 2009 at 09:45:22PM +0100, Johannes Berg wrote: Initvals and new firmware version can be found at http://www.ing.unibs.it/openfwwf I suggest that before this is packaged, we change it so b43 can recognise it and automatically disable qos and hwcrypto. That's a good idea. Is that simply a driver patch? John -- John W. LinvilleSomeday the world will need a hero, and you linvi...@tuxdriver.com might be all we have. Be ready. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
On Wed, 2009-01-14 at 16:09 -0500, John W. Linville wrote: On Wed, Jan 14, 2009 at 09:45:22PM +0100, Johannes Berg wrote: Initvals and new firmware version can be found at http://www.ing.unibs.it/openfwwf I suggest that before this is packaged, we change it so b43 can recognise it and automatically disable qos and hwcrypto. That's a good idea. Is that simply a driver patch? Should be fairly simple, yeah. johannes signature.asc Description: This is a digitally signed message part ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
On Sat, Jan 10, 2009 at 06:37:43PM +0100, Lorenzo Nava wrote: Hello everybody, today I tried OpenFWWF with kernel 2.6.28 on a Siemens wifi device with Broadcom 4306 chipset: BCM94306 802.11g (rev 03) PHY: Analog 2, Type 2, Revision 2 Radio: Manuf 0x17F, Version 0x2050, Revision 2 I did some tests and everything seems to work fine. I remember, once again, that OpenFWWF needs v480 initvals to work properly, and was tested on 2.6.27-rc5 kernel. Any chance on getting a set of initvals packaged with the open source firmware? That would allow distros like Fedora to package this... John -- John W. LinvilleLinux should be at the core linvi...@tuxdriver.com of your literate lifestyle. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
On Monday 12 January 2009 16:39:49 John W. Linville wrote: On Sat, Jan 10, 2009 at 06:37:43PM +0100, Lorenzo Nava wrote: Hello everybody, today I tried OpenFWWF with kernel 2.6.28 on a Siemens wifi device with Broadcom 4306 chipset: BCM94306 802.11g (rev 03) PHY: Analog 2, Type 2, Revision 2 Radio: Manuf 0x17F, Version 0x2050, Revision 2 I did some tests and everything seems to work fine. I remember, once again, that OpenFWWF needs v480 initvals to work properly, and was tested on 2.6.27-rc5 kernel. Any chance on getting a set of initvals packaged with the open source firmware? That would allow distros like Fedora to package this... Did anybody try with the set of initvals from my git repository? It includes the major parts. It just misses parts like the default-beacon-template and stuff. But that's not really needed for now. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
On Jan 12, 2009, at 4:39 PM, John W. Linville wrote: On Sat, Jan 10, 2009 at 06:37:43PM +0100, Lorenzo Nava wrote: Hello everybody, today I tried OpenFWWF with kernel 2.6.28 on a Siemens wifi device with Broadcom 4306 chipset: BCM94306 802.11g (rev 03) PHY: Analog 2, Type 2, Revision 2 Radio: Manuf 0x17F, Version 0x2050, Revision 2 I did some tests and everything seems to work fine. I remember, once again, that OpenFWWF needs v480 initvals to work properly, and was tested on 2.6.27-rc5 kernel. Any chance on getting a set of initvals packaged with the open source firmware? That would allow distros like Fedora to package this... John -- John W. Linville Linux should be at the core linvi...@tuxdriver.comof your literate lifestyle. Yes, we have it now. Still testing as several values can be cut out. Posting ASAP. Cheers. -FG ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [b43] opensource firmware
Hello everybody, today I tried OpenFWWF with kernel 2.6.28 on a Siemens wifi device with Broadcom 4306 chipset: BCM94306 802.11g (rev 03) PHY: Analog 2, Type 2, Revision 2 Radio: Manuf 0x17F, Version 0x2050, Revision 2 I did some tests and everything seems to work fine. I remember, once again, that OpenFWWF needs v480 initvals to work properly, and was tested on 2.6.27-rc5 kernel. During firmware development we used these devices Belkin PCMCIA 4306 card, Siemens PCI 4306 card. Belkin PCI 4306 card. ASUSTeK PCI 4318 card. and firmware seems to work fine. Everyone that is interested in testing OpenFWWF is welcome: please let us know if the firmware works correctly, and, if it doesn't, please report which kind of problems you had. Michael please let us know which kind of problem you had with your device. cheers Lorenzo Nava. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 opensource firmware for monitor mode
On Mon, 2008-06-09 at 14:08 +0200, Michael Buesch wrote: You can try the latest firmware from git, btw. It should be (partially) fixed there. I've tried the today's version. It's working in monitor mode. Moreover, it scans in managed mode! The only problem is that it fails to associate, even to an AP with no security. But there are no hangs whatsoever. That's core rev5 (bcm4306). -- Regards, Pavel Roskin ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 opensource firmware for monitor mode
On Friday 13 June 2008 00:22:39 Pavel Roskin wrote: On Mon, 2008-06-09 at 14:08 +0200, Michael Buesch wrote: You can try the latest firmware from git, btw. It should be (partially) fixed there. I've tried the today's version. It's working in monitor mode. Moreover, it scans in managed mode! The only problem is that it fails to associate, even to an AP with no security. But there are no hangs whatsoever. That's core rev5 (bcm4306). Thanks for testing. TX is not implemented. No wonder it fails to assoc ;) -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 opensource firmware for monitor mode
On Fri, 2008-06-13 at 01:20 +0200, Michael Buesch wrote: On Friday 13 June 2008 00:22:39 Pavel Roskin wrote: On Mon, 2008-06-09 at 14:08 +0200, Michael Buesch wrote: You can try the latest firmware from git, btw. It should be (partially) fixed there. I've tried the today's version. It's working in monitor mode. Moreover, it scans in managed mode! The only problem is that it fails to associate, even to an AP with no security. But there are no hangs whatsoever. That's core rev5 (bcm4306). Thanks for testing. TX is not implemented. No wonder it fails to assoc ;) No wonder even the big 7 dBi antenna didn't help :) Anyway, it's great news. It turns out bcm4318 with rev9 code is working in monitor mode too! -- Regards, Pavel Roskin ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 opensource firmware for monitor mode
On Monday 09 June 2008 05:03:46 Pavel Roskin wrote: On Thu, 2008-06-05 at 15:35 +0200, Michael Buesch wrote: There shouldn't be a reason for a freeze. It might crash, yes, but it always prints out useful messages first for me. I tried different miniPCI-toPCI bridges, hoping that it's a hardware error, but the system freezes with all of them except RouterBoard RB-14. But if I use RB-14, I cannot get any scan results even with the normal firmware. I guess the rfkill pin is enabled in RB-14. I remember I used tape to cover one of the pins long ago to use some bridges. I guess freezing is triggered by receiving a packet. Before the system freezes, it prints messages like: b43-phy2 ERROR: DMA RX buffer too small (len: 47946, buffer: 2404, nr-dropped: 20) Expected. But that shouldn't happen for the original firmware. That's for rev9. Numbers are different for rev5. The screen capture is here: http://red-bean.com/proski/b43/rev9.jpg All expected. -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 opensource firmware for monitor mode
On Monday 09 June 2008 11:36:13 Michael Buesch wrote: On Monday 09 June 2008 05:03:46 Pavel Roskin wrote: On Thu, 2008-06-05 at 15:35 +0200, Michael Buesch wrote: There shouldn't be a reason for a freeze. It might crash, yes, but it always prints out useful messages first for me. I tried different miniPCI-toPCI bridges, hoping that it's a hardware error, but the system freezes with all of them except RouterBoard RB-14. But if I use RB-14, I cannot get any scan results even with the normal firmware. I guess the rfkill pin is enabled in RB-14. I remember I used tape to cover one of the pins long ago to use some bridges. I guess freezing is triggered by receiving a packet. Before the system freezes, it prints messages like: b43-phy2 ERROR: DMA RX buffer too small (len: 47946, buffer: 2404, nr-dropped: 20) Expected. But that shouldn't happen for the original firmware. That's for rev9. Numbers are different for rev5. The screen capture is here: http://red-bean.com/proski/b43/rev9.jpg All expected. You can try the latest firmware from git, btw. It should be (partially) fixed there. -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 opensource firmware for monitor mode
On Thursday 05 June 2008 04:46:28 Pavel Roskin wrote: On Wed, 2008-06-04 at 17:16 +0200, Michael Buesch wrote: Release early, release often. Here's the first testing release of the b43 opensource firmware. http://bu3sch.de/misc/b43-openfw-20080604.tar.bz2 Currently only the receive path is partially implemented. So that means we can only run it in monitor mode for now. This firmware is able to receive packets and push them without special handling (like decrypting) to the driver. There are lots of bugs, of course. Sometimes the PLCP header is corrupted. That will result in a kernel driver warning in xmit.c. This firmware does _only_ work on wireless core revisions 5, 6, 7, 8 or 10. That's great news! Having distributable firmware would simplify installation, placing b43 to the same league as Intel devices. But having free firmware would be unique to Broadcom card and extremely attractive for research in wireless communications and development of novel devices using non-standard protocol extensions. As a short term goal, maybe bcm4328 could be dumbed down to work with b43? I've tried it with bcm4318 first, and it hung hard on module load. Even Alt-SysRq would not work. It turns out it was revision 9 missing in your list. Then I tries a bcm4306 device with rev 5 core. The module loaded. I brought it up in managed mode first. Scanning didn't work. I brought the device down and set monitor mode. But the system hung when I tried to bring the interface back up. There shouldn't be a reason for a freeze. It might crash, yes, but it always prints out useful messages first for me. -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 opensource firmware for monitor mode
On Thursday 05 June 2008 16:37:18 Felipe Maya wrote: [EMAIL PROTECTED]:/# insmod b43.ko fwpostfix=-open Segmentation fault [EMAIL PROTECTED]:/# dmesg Unhandled kernel unaligned access[#1]: Ah well. The alignment is not completely implemented, yet ;) Working on that... -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 opensource firmware for monitor mode
[EMAIL PROTECTED]:/# insmod b43.ko fwpostfix=-open Segmentation fault [EMAIL PROTECTED]:/# dmesg Unhandled kernel unaligned access[#1]: Cpu 0 $ 0 : 1000b800 08124243 80203008 $ 4 : 80262570 80202f88 0021 801ffe3c $ 8 : 8028 8028 80279fa0 df809371 $12 : f3a5dbbc 00200200 32ee058e $16 : c018b008 80262570 c018b024 802bc6a4 $20 : c0161ef0 c0141000 c018c66c 80202f88 $24 : 0018 000186a0 $28 : 81e5a000 81e5bd40 0173 80152044 Hi: ffc5 Lo: 12af9c00 epc : c0174d64 Not tainted ra: 80152044 Status: 1000b803KERNEL EXL IE Cause : 0010 BadVA : 08124257 PrId : 00029029 Modules linked in: b43 option usbserial evdev ehci_hcd uhci_hcd ohci_hcd input_core nf_nat_tftp nf_conntrack_tftp nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp ipt_REDIRECT ipt_NETMAP ppp_async ppp_generic slhc crc_ccitt rt73usb rt2x00usb rt2x00lib usbcore mac80211 cfg80211 michael_mic arc4 aes deflate ecb cbc blkcipher crypto_hash cryptomgr crypto_algapi switch_robo switch_core diag Process insmod (pid: 702, threadinfo=81e5a000, task=8121c9d8) Stack : 0001 0001 0001 386d43e2 375027ff 81e3fafc 81e3fb64 81e5bd80 802bb448 800c4090 800c4080 802bc668 80203008 8039e500 c018b008 80262570 c018b024 802bc6a4 c0161ef0 c0141000 c018c66c c00f7a60 0173 80152044 80262570 81d4a05e 81df4a10 81d4a000 802bc6c0 802bc600 8013300c 80132fb0 802bc648 801f408c 81061600 06fa 802bc6c0 802bc600 ... Call Trace:[800c4090][800c4080][c00f7a60][80152044][8013300c][80132fb0][801f408c][801334a4][80131c6c][8010016c][8013332c][80131dd8][c00f7a60][801321f8][80054fa8][8006b2c8][c0130028][8004b1b0][8000c7b0] Code: afa30034 8fa40068 8c82000c 8c420014 104001b2 2403ffed 94430026 24024321 10620005 [EMAIL PROTECTED]:/# ls -l /lib/firmware/b43-open/ -rw-r--r--1 root root 28 Jun 4 2008 b0g0bsinitvals5.fw -rw-r--r--1 root root 224 Jun 4 2008 b0g0initvals5.fw -rw-r--r--1 root root 2856 Jun 4 2008 ucode5.fw [EMAIL PROTECTED]:/tmp# cat /proc/modules b43 125024 1 - Loading 0xc016e000 option 5440 0 - Live 0xc012d000 usbserial 24160 1 option, Live 0xc013a000 evdev 6880 0 - Live 0xc00b2000 ehci_hcd 30384 0 - Live 0xc00c7000 uhci_hcd 19920 0 - Live 0xc0127000 ohci_hcd 16720 0 - Live 0xc00d7000 input_core 20208 1 evdev, Live 0xc00d1000 nf_nat_tftp 480 0 - Live 0xc00c5000 nf_conntrack_tftp 2480 1 nf_nat_tftp, Live 0xc00c3000 nf_nat_irc 960 0 - Live 0xc00c1000 nf_conntrack_irc 2832 1 nf_nat_irc, Live 0xc00b5000 nf_nat_ftp 1472 0 - Live 0xc0086000 nf_conntrack_ftp 5152 1 nf_nat_ftp, Live 0xc00be000 ipt_REDIRECT 736 0 - Live 0xc00b ipt_NETMAP 736 0 - Live 0xc00ae000 ppp_async 9856 0 - Live 0xc00a7000 ppp_generic 20192 1 ppp_async, Live 0xc00b8000 slhc 5376 1 ppp_generic, Live 0xc00ab000 crc_ccitt 1024 1 ppp_async, Live 0xc00a5000 rt73usb 20832 0 - Live 0xc009 rt2x00usb 6048 1 rt73usb, Live 0xc0079000 rt2x00lib 15328 2 rt73usb,rt2x00usb, Live 0xc0098000 usbcore 106576 8 option,usbserial,ehci_hcd,uhci_hcd,ohci_hcd,rt73usb,rt2x00usb, Live 0xc010b000 mac80211 160800 3 b43,rt2x00usb,rt2x00lib, Live 0xc00e2000 cfg80211 27504 2 rt2x00lib,mac80211, Live 0xc009d000 michael_mic 1600 0 - Live 0xc0084000 arc4 864 2 - Live 0xc0082000 aes 28240 0 - Live 0xc0088000 deflate 1600 0 - Live 0xc008 ecb 1440 2 - Live 0xc007e000 cbc 2496 0 - Live 0xc007c000 blkcipher 3824 2 ecb,cbc, Live 0xc0075000 crypto_hash 1024 0 - Live 0xc0077000 cryptomgr 1472 0 - Live 0xc006a000 crypto_algapi 7040 7 michael_mic,arc4,aes,deflate,ecb,cbc,cryptomgr, Live 0xc006 switch_robo 4224 0 - Live 0xc0067000 switch_core 5088 1 switch_robo, Live 0xc0064000 diag 7184 0 - Live 0xc006c000 Note that the RT73 is installed using compat-wireless-2.6, seems work well. Mensagem Original From: Michael Buesch [EMAIL PROTECTED] To: Pavel Roskin [EMAIL PROTECTED] Sent: Qui, Junho 5, 2008 10:35 am Subject: Re: b43 opensource firmware for monitor mode On Thursday 05 June 2008 04:46:28 Pavel Roskin wrote: On Wed, 2008-06-04 at 17:16 +0200, Michael Buesch wrote: Release early, release often. Here's the first testing release of the b43 opensource firmware. http://bu3sch.de/misc/b43-openfw-20080604.tar.bz2 Currently only the receive path is partially implemented. So that means we can only run it in monitor mode for now. This firmware is able to receive packets and push them without special handling (like decrypting) to the driver. There are lots of bugs, of course. Sometimes the PLCP header is corrupted. That will result in a kernel driver warning in xmit.c. This firmware does _only_ work on wireless core revisions 5, 6, 7, 8 or 10. That's great news! Having distributable firmware would simplify installation, placing b43 to the same league as Intel devices. But having free firmware would be unique to Broadcom card and extremely attractive for research in wireless communications
b43 opensource firmware for monitor mode
Release early, release often. Here's the first testing release of the b43 opensource firmware. http://bu3sch.de/misc/b43-openfw-20080604.tar.bz2 Currently only the receive path is partially implemented. So that means we can only run it in monitor mode for now. This firmware is able to receive packets and push them without special handling (like decrypting) to the driver. There are lots of bugs, of course. Sometimes the PLCP header is corrupted. That will result in a kernel driver warning in xmit.c. This firmware does _only_ work on wireless core revisions 5, 6, 7, 8 or 10. You can see the core revision by turning on SSB debugging. It will print something like: ssb: Core X found: IEEE 802.11 (cc 0x812, rev 0x05, vendor 0x4243) As you can see there's the revision number in hex. If you want to test this, please get the tarball and extract it. The tarball contains the full sourcecode and a set of prebuilt binaries. (If you want to rebuild the stuff, you need to get the assembler toolchain from http://git.bu3sch.de/git/b43-tools.git). Simply get the *.fw files from bin/rev5/ in the tarball and copy them into /lib/firmware/b43-open. Then load b43 from latest wireless-testing.git with the module parameter fwpostfix=-open Setup monitor mode and see packets coming in. Or not... -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43 opensource firmware for monitor mode
On Wed, 2008-06-04 at 17:16 +0200, Michael Buesch wrote: Release early, release often. Here's the first testing release of the b43 opensource firmware. http://bu3sch.de/misc/b43-openfw-20080604.tar.bz2 Currently only the receive path is partially implemented. So that means we can only run it in monitor mode for now. This firmware is able to receive packets and push them without special handling (like decrypting) to the driver. There are lots of bugs, of course. Sometimes the PLCP header is corrupted. That will result in a kernel driver warning in xmit.c. This firmware does _only_ work on wireless core revisions 5, 6, 7, 8 or 10. That's great news! Having distributable firmware would simplify installation, placing b43 to the same league as Intel devices. But having free firmware would be unique to Broadcom card and extremely attractive for research in wireless communications and development of novel devices using non-standard protocol extensions. As a short term goal, maybe bcm4328 could be dumbed down to work with b43? I've tried it with bcm4318 first, and it hung hard on module load. Even Alt-SysRq would not work. It turns out it was revision 9 missing in your list. Then I tries a bcm4306 device with rev 5 core. The module loaded. I brought it up in managed mode first. Scanning didn't work. I brought the device down and set monitor mode. But the system hung when I tried to bring the interface back up. Anyway, I'm glad to see progress in that direction. -- Regards, Pavel Roskin ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
