Re: Broadcom BCM4310 USB Controller (Wifi)
On 11/22/10, Alberto Villa avi...@freebsd.org wrote: On Wednesday 17 November 2010 10:57:34 Paul B Mahol wrote: Please use ndis5 branch. master branch is in heavy development. CURRENT branch just blindly (and badly) track code on FreeBSD CURRENT. ok. unfortunately in this test i made an error and just saw that... `-- git status # On branch ndis5 # Your branch is ahead of 'origin/ndis5' by 13 commits. i hope it's ok for this time Git status should be empty. Just pull again. Or clone repo again, or do not use git and fetch tar.gz from site. I did some changes with forced rebase so that happened. When you say what you did be more specific, like are you are using i386 or amd64, and so on. FreeBSD echo.hoth 9.0-CURRENT FreeBSD 9.0-CURRENT #2 r215448M: Thu Nov 18 08:34:00 CET 2010 r...@echo.hoth:/usr/obj/usr/src/sys/HPDV6 amd64 my kernel configuration file is a GENERIC trimmed down to the minimum (so that everything possible is loaded as a module) amd64, I see. And another broadcom card on CURRENT and on amd64 just panics, but this is another driver. Can you post link to your driver? For using code in branch master and ndis5, you will need to reinstall ndisgen and ndiscvt from git repo and do not use one from FreeBSD world. This also means you will need to regenerate miniport module with new ndiscvt ndisgen because interface have changed slightly. i did it, and here you are the results: http://pastebin.ca/1998450 http://pastebin.ca/1998454 Why it picked MAC first time without problems, otherwise ndis0 would never attach, and second time it reports error? For a moment disable wpa_supplicant in your rc.conf. And try to get scan results via ifconfig(8). like this: # ifconfig wlan0 destroy # ifconfig wlan create wlandev ndis0 # ifconfig wlan0 up # ifconfig wlan0 list scan And upload relevant dmesg output (ndis/NDIS lines) somewhere. And/or contact me off-list. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
On 11/22/10, Paul B Mahol one...@gmail.com wrote: On 11/22/10, Alberto Villa avi...@freebsd.org wrote: On Wednesday 17 November 2010 10:57:34 Paul B Mahol wrote: Please use ndis5 branch. master branch is in heavy development. CURRENT branch just blindly (and badly) track code on FreeBSD CURRENT. ok. unfortunately in this test i made an error and just saw that... `-- git status # On branch ndis5 # Your branch is ahead of 'origin/ndis5' by 13 commits. i hope it's ok for this time Git status should be empty. Just pull again. Or clone repo again, or do not use git and fetch tar.gz from site. I did some changes with forced rebase so that happened. When you say what you did be more specific, like are you are using i386 or amd64, and so on. FreeBSD echo.hoth 9.0-CURRENT FreeBSD 9.0-CURRENT #2 r215448M: Thu Nov 18 08:34:00 CET 2010 r...@echo.hoth:/usr/obj/usr/src/sys/HPDV6 amd64 my kernel configuration file is a GENERIC trimmed down to the minimum (so that everything possible is loaded as a module) amd64, I see. And another broadcom card on CURRENT and on amd64 just panics, but this is another driver. Can you post link to your driver? For using code in branch master and ndis5, you will need to reinstall ndisgen and ndiscvt from git repo and do not use one from FreeBSD world. This also means you will need to regenerate miniport module with new ndiscvt ndisgen because interface have changed slightly. i did it, and here you are the results: http://pastebin.ca/1998450 http://pastebin.ca/1998454 Why it picked MAC first time without problems, otherwise ndis0 would never attach, and second time it reports error? For a moment disable wpa_supplicant in your rc.conf. And try to get scan results via ifconfig(8). like this: # ifconfig wlan0 destroy # ifconfig wlan create wlandev ndis0 # ifconfig wlan0 up # ifconfig wlan0 list scan And upload relevant dmesg output (ndis/NDIS lines) somewhere. And/or contact me off-list. I managed to fix panic on amd64 for driver I'm using. So try the latest version. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
On Wednesday 17 November 2010 10:57:34 Paul B Mahol wrote: Please use ndis5 branch. master branch is in heavy development. CURRENT branch just blindly (and badly) track code on FreeBSD CURRENT. ok. unfortunately in this test i made an error and just saw that... `-- git status # On branch ndis5 # Your branch is ahead of 'origin/ndis5' by 13 commits. i hope it's ok for this time When you say what you did be more specific, like are you are using i386 or amd64, and so on. FreeBSD echo.hoth 9.0-CURRENT FreeBSD 9.0-CURRENT #2 r215448M: Thu Nov 18 08:34:00 CET 2010 r...@echo.hoth:/usr/obj/usr/src/sys/HPDV6 amd64 my kernel configuration file is a GENERIC trimmed down to the minimum (so that everything possible is loaded as a module) For using code in branch master and ndis5, you will need to reinstall ndisgen and ndiscvt from git repo and do not use one from FreeBSD world. This also means you will need to regenerate miniport module with new ndiscvt ndisgen because interface have changed slightly. i did it, and here you are the results: http://pastebin.ca/1998450 http://pastebin.ca/1998454 thanks -- Alberto Villa, FreeBSD committer avi...@freebsd.org http://people.FreeBSD.org/~avilla Flying saucers on occasion Show themselves to human eyes. Aliens fume, put off invasion While they brand these tales as lies. signature.asc Description: This is a digitally signed message part.
Re: Broadcom BCM4310 USB Controller (Wifi)
On Mon, Nov 15, 2010 at 2:41 PM, Paul B Mahol one...@gmail.com wrote: Feel free to test code at: gitorious.org/NDISulator github.com/richardpl/NDISulator The code is developed on CURRENT. But with small changes it can be compiled on STABLE too. thanks! i've applied a checkout of last night to current. i can load the module after boot, but the panic is still there when i unload or load on boot, and wpa_supplicant fails to work (see attached log) Just now I have only one tester (and that is without counting me). consider me as the third one :) -- Alberto Villa, FreeBSD committer avi...@freebsd.org http://people.FreeBSD.org/~avilla ndis.log Description: Binary data ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
On 11/17/10, Alberto Villa avi...@freebsd.org wrote: On Mon, Nov 15, 2010 at 2:41 PM, Paul B Mahol one...@gmail.com wrote: Feel free to test code at: gitorious.org/NDISulator github.com/richardpl/NDISulator The code is developed on CURRENT. But with small changes it can be compiled on STABLE too. thanks! i've applied a checkout of last night to current. i can load the module after boot, but the panic is still there when i unload or load on boot, and wpa_supplicant fails to work (see attached log) Just now I have only one tester (and that is without counting me). consider me as the third one :) Please use ndis5 branch. master branch is in heavy development. CURRENT branch just blindly (and badly) track code on FreeBSD CURRENT. When you say what you did be more specific, like are you are using i386 or amd64, and so on. When testing, enable debug.bootverbose, and debug.ndis sysctl before loading miniport module. [miniport module is module you created with ndisgen(8)] Do not load miniport module(s) during boot(from loader), if it ever worked it was big luck. [Even on Windows, drivers are loaded after boot.] Actually drivers can be loaded but we must be extra carefull what to call during boot and what to call after boot. For using code in branch master and ndis5, you will need to reinstall ndisgen and ndiscvt from git repo and do not use one from FreeBSD world. This also means you will need to regenerate miniport module with new ndiscvt ndisgen because interface have changed slightly. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
On Wed, Oct 27, 2010 at 3:36 PM, Paul B Mahol one...@gmail.com wrote: Currently amd64 is broken with some/most drivers. Drivers appears to use fpu registers. I dunno how it ever worked, probably original developer(s) never encountered drivers which use fpu registers. I will probably fix amd64 support in this year. so, i've tried the ndis driver with amd64 and it paniced, as you said. do you have any idea on when you're gonna fix this? i need to know if i can keep amd64 and wait for a fix (in short time) or if i have to install i386 temporarily... thanks -- Alberto Villa, FreeBSD committer avi...@freebsd.org http://people.FreeBSD.org/~avilla ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
On 11/15/10, Alberto Villa avi...@freebsd.org wrote: On Wed, Oct 27, 2010 at 3:36 PM, Paul B Mahol one...@gmail.com wrote: Currently amd64 is broken with some/most drivers. Drivers appears to use fpu registers. I dunno how it ever worked, probably original developer(s) never encountered drivers which use fpu registers. I will probably fix amd64 support in this year. so, i've tried the ndis driver with amd64 and it paniced, as you said. do you have any idea on when you're gonna fix this? i need to know if i can keep amd64 and wait for a fix (in short time) or if i have to install i386 temporarily... Feel free to test code at: gitorious.org/NDISulator github.com/richardpl/NDISulator The code is developed on CURRENT. But with small changes it can be compiled on STABLE too. Just now I have only one tester (and that is without counting me). ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
El día Thursday, October 28, 2010 a las 12:07:10PM +, Paul B Mahol escribió: # ifconfig ndis0 192.168.2.200 All this is with a 8-CURRENT kernel/system as of May 2009. I will now build a USB key from HEAD and will continue testing. On 9/8 CURRENT you create wlanX with ifconfig(8) and operate on them. But note that such old CURRENT have few bugs in NDISulator. For example scan results are incomplete and scanning can trigger panic in some situations. If you use wpa_supplicant -Dndis you will never encounter such problems. I booted the 8-CURRENT this morning, loaded the module with kldload(8) and wlan0 came up by its own (I did not realized this yesterday). I have in rc.conf: wlans_ndis0=wlan0 ifconfig_wlan0=WPA DHCP wpa_supplicant(8) started after kldload, and associated the interface with my AP; had to do the DHCP by hand, don't know why? For the moment all seems to be fine. Thanks for guiding me through this to all. matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
On Fri, Oct 29, 2010 at 12:59 AM, Matthias Apitz g...@unixarea.de wrote: I booted the 8-CURRENT this morning, loaded the module with kldload(8) and wlan0 came up by its own (I did not realized this yesterday). I have in rc.conf: wlans_ndis0=wlan0 ifconfig_wlan0=WPA DHCP wpa_supplicant(8) started after kldload, and associated the interface with my AP; had to do the DHCP by hand, don't know why? The problem is that the Broadcom NDIS driver is generating connection events, but nothing is relaying that information to the wpa_supplicant daemon. Since the wpa_supplicant daemon doesn't see a connection event, it retries connecting I had created a patch in PR 113915 which solves this problem: http://www.freebsd.org/cgi/query-pr.cgi?pr=113915 Give it a try, if it solves your problem submit a followup to the PR. Scot ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
On Fri, Oct 29, 2010 at 6:34 AM, Scot Hetzel swhet...@gmail.com wrote: On Fri, Oct 29, 2010 at 12:59 AM, Matthias Apitz g...@unixarea.de wrote: I booted the 8-CURRENT this morning, loaded the module with kldload(8) and wlan0 came up by its own (I did not realized this yesterday). I have in rc.conf: wlans_ndis0=wlan0 ifconfig_wlan0=WPA DHCP wpa_supplicant(8) started after kldload, and associated the interface with my AP; had to do the DHCP by hand, don't know why? The problem is that the Broadcom NDIS driver is generating connection events, but nothing is relaying that information to the wpa_supplicant daemon. Since the wpa_supplicant daemon doesn't see a connection event, it retries connecting I had created a patch in PR 113915 which solves this problem: http://www.freebsd.org/cgi/query-pr.cgi?pr=113915 Give it a try, if it solves your problem submit a followup to the PR. Hmm, ndis_events are required if you use -Dndis and wpa/rsn and need to get event of PMKIDs. For other uses it is of no use. Try -Dbsd driver for wpa_supplicant with code from here: Try http://gitorious.org/ndisulator ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
El día Friday, October 29, 2010 a las 07:07:18AM +, Paul B Mahol escribió: On Fri, Oct 29, 2010 at 6:34 AM, Scot Hetzel swhet...@gmail.com wrote: On Fri, Oct 29, 2010 at 12:59 AM, Matthias Apitz g...@unixarea.de wrote: I booted the 8-CURRENT this morning, loaded the module with kldload(8) and wlan0 came up by its own (I did not realized this yesterday). I have in rc.conf: wlans_ndis0=wlan0 ifconfig_wlan0=WPA DHCP wpa_supplicant(8) started after kldload, and associated the interface with my AP; had to do the DHCP by hand, don't know why? The problem is that the Broadcom NDIS driver is generating connection events, but nothing is relaying that information to the wpa_supplicant daemon. Since the wpa_supplicant daemon doesn't see a connection event, it retries connecting I had created a patch in PR 113915 which solves this problem: http://www.freebsd.org/cgi/query-pr.cgi?pr=113915 Give it a try, if it solves your problem submit a followup to the PR. Hmm, ndis_events are required if you use -Dndis and wpa/rsn and need to get event of PMKIDs. For other uses it is of no use. The wpa_supplicant(8) which comes up after loading the NDIS kmod with kldload(8) is launched with -Dndis; I checked this this morning; will try the patch proposed by Scott; matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
El día Wednesday, October 27, 2010 a las 12:12:09PM -0500, Scot Hetzel escribió: Where did you get your bcmwl5 driver? If you downloaded it from Acer, it should work. If you downloaded it from anywhere else then this might be why it didn't work for you. Just noticed that you didn't specify your computer manufacture. The above would only work for Matthias Apitz. You just need to download the driver from the manufacture of your computer. Why is this? Isn't it just the Wifi chip which matters? Could you sheet a bit light on this? Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
El día Wednesday, October 27, 2010 a las 12:07:51PM -0500, Scot Hetzel escribió: On Wed, Oct 27, 2010 at 8:58 AM, Alberto Villa avi...@freebsd.org wrote: On Wed, Oct 27, 2010 at 1:36 PM, Paul B Mahol one...@gmail.com wrote: NDISulator does not support 6.X NDIS API. You will need to find bcmwl5 driver. Note 5 vs 6 in driver name. Editing inf files will give you nothing. i've tried that driver, but apparently it doesn't support my card... loading the .ko doesn't show anything... Where did you get your bcmwl5 driver? If you downloaded it from Acer, it should work. If you downloaded it from anywhere else then this might be why it didn't work for you. Following Scot's hint (thanks for this) I downloaded today morning the WinXP x86 driver zip archive from www.Acer.com and built the bcmwl5_sys.ko with ndisgen(8). The system panics on early boot stages when the kmod was pulled in via loader.conf. If the system is up, you can kldload the module fine and the interface ndis0 appears and even the card gets associated with the AP (i.e. wpa_supplicant(8) must work fine). The ifconfig(8) shows the interface as: ndis0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 90:4c:e5:00:06:ce media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated and the Wifi indicator light of the laptop is green. But: # dhclient ndis0 ifconfig: ioctl (SIOCAIFADDR): Invalid argument ndis0: not found and the same is with # ifconfig ndis0 192.168.2.200 All this is with a 8-CURRENT kernel/system as of May 2009. I will now build a USB key from HEAD and will continue testing. Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
On 10/28/10, Matthias Apitz g...@unixarea.de wrote: El dia Wednesday, October 27, 2010 a las 12:07:51PM -0500, Scot Hetzel escribio: On Wed, Oct 27, 2010 at 8:58 AM, Alberto Villa avi...@freebsd.org wrote: On Wed, Oct 27, 2010 at 1:36 PM, Paul B Mahol one...@gmail.com wrote: NDISulator does not support 6.X NDIS API. You will need to find bcmwl5 driver. Note 5 vs 6 in driver name. Editing inf files will give you nothing. i've tried that driver, but apparently it doesn't support my card... loading the .ko doesn't show anything... Where did you get your bcmwl5 driver? If you downloaded it from Acer, it should work. If you downloaded it from anywhere else then this might be why it didn't work for you. Following Scot's hint (thanks for this) I downloaded today morning the WinXP x86 driver zip archive from www.Acer.com and built the bcmwl5_sys.ko with ndisgen(8). The system panics on early boot stages when the kmod was pulled in via loader.conf. Newer drivers do that, I don't have solution. If the system is up, you can kldload the module fine and the interface ndis0 appears and even the card gets associated with the AP (i.e. wpa_supplicant(8) must work fine). The ifconfig(8) shows the interface as: ndis0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 90:4c:e5:00:06:ce media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated and the Wifi indicator light of the laptop is green. But: # dhclient ndis0 ifconfig: ioctl (SIOCAIFADDR): Invalid argument ndis0: not found and the same is with # ifconfig ndis0 192.168.2.200 All this is with a 8-CURRENT kernel/system as of May 2009. I will now build a USB key from HEAD and will continue testing. On 9/8 CURRENT you create wlanX with ifconfig(8) and operate on them. But note that such old CURRENT have few bugs in NDISulator. For example scan results are incomplete and scanning can trigger panic in some situations. If you use wpa_supplicant -Dndis you will never encounter such problems. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
El día Thursday, October 28, 2010 a las 12:07:10PM +, Paul B Mahol escribió: # dhclient ndis0 ifconfig: ioctl (SIOCAIFADDR): Invalid argument ndis0: not found and the same is with # ifconfig ndis0 192.168.2.200 All this is with a 8-CURRENT kernel/system as of May 2009. I will now build a USB key from HEAD and will continue testing. On 9/8 CURRENT you create wlanX with ifconfig(8) and operate on them. Stupid I am. Of course. I forgot this in the happyness that ndis0 came up :-( But note that such old CURRENT have few bugs in NDISulator. For example scan results are incomplete and scanning can trigger panic in some situations. If you use wpa_supplicant -Dndis you will never encounter such problems. I've checked my old man page and the one of HEAD ... -D is not explained in the man page of wpa_supplicant(8), but in its help: # /usr/sbin/wpa_supplicant --help | fgrep -- -D wpa_supplicant: illegal option -- - -iifname -cconfig file [-Cctrl] [-Ddriver] [-pdriver_param] \ [-N -iifname -cconf [-Cctrl] [-Ddriver] \ -D = driver name wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf Thanks for the hint matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
On Thu, Oct 28, 2010 at 1:06 AM, Matthias Apitz g...@unixarea.de wrote: El día Wednesday, October 27, 2010 a las 12:12:09PM -0500, Scot Hetzel escribió: Where did you get your bcmwl5 driver? If you downloaded it from Acer, it should work. If you downloaded it from anywhere else then this might be why it didn't work for you. Just noticed that you didn't specify your computer manufacture. The above would only work for Matthias Apitz. You just need to download the driver from the manufacture of your computer. Why is this? Isn't it just the Wifi chip which matters? Could you sheet a bit light on this? Thanks When you get the Windows NDIS driver from the computer manufacture, you are ensured that your card is supported by that version of the driver. If you download the Windows NDIS driver from another source, that driver may not include support for your card as it might be an older version. Also, some versions of the Windows NDIS driver may use functions that are not currently implemented in the FreeBSD NDIS emulator. Scot ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
On Wed, Oct 27, 2010 at 5:12 PM, Scot Hetzel swhet...@gmail.com wrote: You just need to download the driver from the manufacture of your computer. i downloaded some from acer and dell, until i found one from hp (actually, more than one - http://h10025.www1.hp.com/ewfrf/wc/searchResults?tmp_qt=broadcom+wirelesslc=endlc=encc=us, for reference) which is working! some panics yet, but i have other versions to try, and anyway it only requires some manual setting... thank you very much for your help! -- Alberto Villa, FreeBSD committer avi...@freebsd.org http://people.FreeBSD.org/~avilla ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
On Thu, Oct 28, 2010 at 4:37 PM, Scot Hetzel swhet...@gmail.com wrote: When you get the Windows NDIS driver from the computer manufacture, you are ensured that your card is supported by that version of the driver. If you download the Windows NDIS driver from another source, that driver may not include support for your card as it might be an older version. checking the .inf file should be enough to know if it's supported or not (as far as i've seen)... -- Alberto Villa, FreeBSD committer avi...@freebsd.org http://people.FreeBSD.org/~avilla ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
On Tue, Oct 26, 2010 at 2:09 PM, Paul B Mahol one...@gmail.com wrote: i've tried ndis without success... Sharing you experience would help (if you are not on amd64). i'm on i386 at the moment, but i'll switch to amd64 as soon as i decide what to do (keep freebsd natively or virtualize it under windows... it depends on the wireless driver). would that change anything? here's my experience. also, as a reference, here's what i get if i add the device id to siba_bwn: # kldload if_bwn siba_bwn0: Broadcom BCM43225 802.11b/g/n Wireless mem 0xda10-0xda103fff irq 16 at device 0.0 on pci2 siba_bwn0: cannot map register space device_attach: siba_bwn0 attach returned 6 and here is the new open source driver: http://wireless.kernel.org/en/users/Drivers/brcm80211 and now, ndis. the driver is bcmwl6 (http://people.freebsd.org/~avilla/bcmwl6.inf and http://people.freebsd.org/~avilla/bcmwl6.sys , apparently no need for firmware files, but i'm not sure), which is said not to work with ndis on linux forums (maybe they removed the support for winxp) matthias: you should try bcmwl5, that could work for you using the unmodified files i've attached (they default to winvista and win7) i get this: # kldload ./bcmwl6_sys.ko module ndis already present! no match for NdisMIndicateReceiveNetBufferLists no match for NdisFreeNetBufferListPool no match for NdisMRegisterScatterGatherDma no match for NdisMAllocatePort no match for NdisQueueIoWorkItem no match for NdisMFreePort no match for NdisMOidRequestComplete no match for NdisMNetPnPEvent no match for NdisAllocateIoWorkItem no match for NdisFreeIoWorkItem no match for NdisGetVersion no match for NdisMSetMiniportAttributes no match for NdisMDeregisterMiniportDriver no match for NdisAllocateTimerObject no match for NdisMPauseComplete no match for NdisOpenConfigurationEx no match for NdisFreeTimerObject no match for NdisCancelTimerObject no match for NdisSetTimerObject no match for NdisMSynchronizeWithInterruptEx no match for NdisMDeregisterInterruptEx no match for NdisMRegisterInterruptEx no match for NdisMIndicateStatusEx no match for NdisFreeNetBufferList no match for NdisGetSystemUpTimeEx no match for NdisAllocateMdl no match for NdisAllocateNetBufferAndNetBufferList no match for NdisFreeMdl no match for NdisMResetComplete no match for NdisMSendNetBufferListsComplete no match for NdisAllocateNetBufferListPool no match for NdisMRegisterMiniportDriver no match for NdisMDeregisterScatterGatherDma no match for NdisAllocateMemoryWithTagPriority no match for NdisMGetBusData no match for NdisMSetBusData no match for ZwQueryInformationFile no match for ZwReadFile no match for ZwCreateFile no match for ExFreePoolWithTag no match for IoRegisterPlugPlayNotification no match for IoUnregisterPlugPlayNotification NDIS dummy called... NDIS dummy called... which should mean that the driver doesn't support xp. so i tried changing (in the .inf) %V_BCM% = BROADCOM, NTx86.6.0, NTamd64.6.0, NTx86.6.1, NTamd64.6.1 to %V_BCM% = BROADCOM, NTx86, NTamd64 and then i only get module ndis already present!, but no interface shows up i also tried removing NTx86, making it %V_BCM% = BROADCOM, NTamd64 (it should be correct), and with this modification i get the same error messages of the first attempt anyway i don't have any experience with ndis... should i test anything else? -- Alberto Villa, FreeBSD committer avi...@freebsd.org http://people.FreeBSD.org/~avilla ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
On 10/27/10, Alberto Villa avi...@freebsd.org wrote: On Tue, Oct 26, 2010 at 2:09 PM, Paul B Mahol one...@gmail.com wrote: i've tried ndis without success... Sharing you experience would help (if you are not on amd64). i'm on i386 at the moment, but i'll switch to amd64 as soon as i decide what to do (keep freebsd natively or virtualize it under windows... it depends on the wireless driver). would that change anything? Currently amd64 is broken with some/most drivers. Drivers appears to use fpu registers. I dunno how it ever worked, probably original developer(s) never encountered drivers which use fpu registers. I will probably fix amd64 support in this year. here's my experience. also, as a reference, here's what i get if i add the device id to siba_bwn: # kldload if_bwn siba_bwn0: Broadcom BCM43225 802.11b/g/n Wireless mem 0xda10-0xda103fff irq 16 at device 0.0 on pci2 siba_bwn0: cannot map register space device_attach: siba_bwn0 attach returned 6 and here is the new open source driver: http://wireless.kernel.org/en/users/Drivers/brcm80211 and now, ndis. the driver is bcmwl6 (http://people.freebsd.org/~avilla/bcmwl6.inf and http://people.freebsd.org/~avilla/bcmwl6.sys , apparently no need for firmware files, but i'm not sure), which is said not to work with ndis on linux forums (maybe they removed the support for winxp) matthias: you should try bcmwl5, that could work for you using the unmodified files i've attached (they default to winvista and win7) i get this: # kldload ./bcmwl6_sys.ko module ndis already present! no match for NdisMIndicateReceiveNetBufferLists no match for NdisFreeNetBufferListPool no match for NdisMRegisterScatterGatherDma no match for NdisMAllocatePort no match for NdisQueueIoWorkItem no match for NdisMFreePort no match for NdisMOidRequestComplete no match for NdisMNetPnPEvent no match for NdisAllocateIoWorkItem no match for NdisFreeIoWorkItem no match for NdisGetVersion no match for NdisMSetMiniportAttributes no match for NdisMDeregisterMiniportDriver no match for NdisAllocateTimerObject no match for NdisMPauseComplete no match for NdisOpenConfigurationEx no match for NdisFreeTimerObject no match for NdisCancelTimerObject no match for NdisSetTimerObject no match for NdisMSynchronizeWithInterruptEx no match for NdisMDeregisterInterruptEx no match for NdisMRegisterInterruptEx no match for NdisMIndicateStatusEx no match for NdisFreeNetBufferList no match for NdisGetSystemUpTimeEx no match for NdisAllocateMdl no match for NdisAllocateNetBufferAndNetBufferList no match for NdisFreeMdl no match for NdisMResetComplete no match for NdisMSendNetBufferListsComplete no match for NdisAllocateNetBufferListPool no match for NdisMRegisterMiniportDriver no match for NdisMDeregisterScatterGatherDma no match for NdisAllocateMemoryWithTagPriority no match for NdisMGetBusData no match for NdisMSetBusData no match for ZwQueryInformationFile no match for ZwReadFile no match for ZwCreateFile no match for ExFreePoolWithTag no match for IoRegisterPlugPlayNotification no match for IoUnregisterPlugPlayNotification NDIS dummy called... NDIS dummy called... which should mean that the driver doesn't support xp. so i tried changing (in the .inf) %V_BCM% = BROADCOM, NTx86.6.0, NTamd64.6.0, NTx86.6.1, NTamd64.6.1 Now when you mention this I may send patch for ndisgen(8) so it will deny creating modules for 6.X API drivers. to %V_BCM% = BROADCOM, NTx86, NTamd64 and then i only get module ndis already present!, but no interface shows up i also tried removing NTx86, making it %V_BCM% = BROADCOM, NTamd64 (it should be correct), and with this modification i get the same error messages of the first attempt anyway i don't have any experience with ndis... should i test anything else? NDISulator does not support 6.X NDIS API. You will need to find bcmwl5 driver. Note 5 vs 6 in driver name. Editing inf files will give you nothing. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
On Wed, Oct 27, 2010 at 12:07 PM, Scot Hetzel swhet...@gmail.com wrote: On Wed, Oct 27, 2010 at 8:58 AM, Alberto Villa avi...@freebsd.org wrote: On Wed, Oct 27, 2010 at 1:36 PM, Paul B Mahol one...@gmail.com wrote: NDISulator does not support 6.X NDIS API. You will need to find bcmwl5 driver. Note 5 vs 6 in driver name. Editing inf files will give you nothing. i've tried that driver, but apparently it doesn't support my card... loading the .ko doesn't show anything... Where did you get your bcmwl5 driver? If you downloaded it from Acer, it should work. If you downloaded it from anywhere else then this might be why it didn't work for you. Just noticed that you didn't specify your computer manufacture. The above would only work for Matthias Apitz. You just need to download the driver from the manufacture of your computer. Scot ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
On Wed, Oct 27, 2010 at 8:58 AM, Alberto Villa avi...@freebsd.org wrote: On Wed, Oct 27, 2010 at 1:36 PM, Paul B Mahol one...@gmail.com wrote: NDISulator does not support 6.X NDIS API. You will need to find bcmwl5 driver. Note 5 vs 6 in driver name. Editing inf files will give you nothing. i've tried that driver, but apparently it doesn't support my card... loading the .ko doesn't show anything... Where did you get your bcmwl5 driver? If you downloaded it from Acer, it should work. If you downloaded it from anywhere else then this might be why it didn't work for you. Scot ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
El día Wednesday, October 27, 2010 a las 05:10:32PM +, Alberto Villa escribió: On Wed, Oct 27, 2010 at 5:07 PM, Scot Hetzel swhet...@gmail.com wrote: Where did you get your bcmwl5 driver? If you downloaded it from Acer, it should work. If you downloaded it from anywhere else then this might be why it didn't work for you. i don't remember, actually. anyway i thought the 5 was the driver version, i've just understood that it's the windows version :P i'll try the acer one, thanks for the suggestion! I could no get any bcmwl5 driver from Acer, only bcmwl6 version (which is also installed in Win7 in my laptop). I have even asked Broadcom, but they pointed me back to my dealer, to the reseller of the Acer laptop. And asking them, they pointed to Acer. If someone has an bcmwl5 from Acer, please contact me off-list. matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
On Mon, Oct 25, 2010 at 1:07 AM, Matthias Apitz g...@unixarea.de wrote: I have a new laptop Acer Aspire One D250 and pulled out HEAD from SVN today morning. As far as I can see in sys/dev/bwi and sys/dev/bwn the above chip is still not supported. I am wrong? i have the same problem with a BCM43225. there is a linux driver: is anyone going to port it in the near future? would a donation help the process? Any other idea how to get Wifi working on this mini laptop? i've tried ndis without success... -- Alberto Villa, FreeBSD committer avi...@freebsd.org http://people.FreeBSD.org/~avilla ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Broadcom BCM4310 USB Controller (Wifi)
On 10/26/10, Alberto Villa avi...@freebsd.org wrote: On Mon, Oct 25, 2010 at 1:07 AM, Matthias Apitz g...@unixarea.de wrote: I have a new laptop Acer Aspire One D250 and pulled out HEAD from SVN today morning. As far as I can see in sys/dev/bwi and sys/dev/bwn the above chip is still not supported. I am wrong? i have the same problem with a BCM43225. there is a linux driver: is anyone going to port it in the near future? would a donation help the process? Any other idea how to get Wifi working on this mini laptop? i've tried ndis without success... Sharing you experience would help (if you are not on amd64). ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
