1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

[PC-BSD] Broadcom wireless on Dell doesn't turn on.

Discussion in 'Mobile Computing' started by nemirst, Dec 7, 2010.

  1. nemirst

    nemirst New Member

    Messages:
    7
    Likes Received:
    0
    Hi folks,

    Just started using Unix-type OS few days ago and now I have one problem. I can't get wireless device turning on (led is switched off) even though it's working on Windows. OS installed is PCBSD 8.1 so there should be no difference compared to FreeBSD. I have some kind of Dell mini wireless card (it must be Broadcom). Please tell me how to get more accurate information in terminal and I'll provide you with it if you need. For reference I used some parts of FreeBSD handbook.

    Here's what I tried:
    * Added if_bwn_load="YES" to /boot/loader.conf.
    * Did "make install clean" inside /usr/ports/net/bwn-firmware-kmod directory
    * reboot
    * ifconfig wlan0 create wlandev bwn0
    * ifconfig wlan0 up scan

    Tried also bwi instead of bwn with no success.

    What should I do to make my wireless work?
     
  2. richardpl

    richardpl New Member

    Messages:
    841
    Likes Received:
    0
    Add bwn firmware to loader.conf
     
  3. DutchDaemon

    DutchDaemon Administrator Staff Member Administrator Moderator

    Messages:
    10,651
    Likes Received:
    20
    That's a risky misconception, so beware of advice.
     
  4. nemirst

    nemirst New Member

    Messages:
    7
    Likes Received:
    0
    I did it now I guess. Added
    Code:
    bwn_v4_ucode_load="YES"
    to /boot/loader.conf.
    Tried also manual load of module after reboot kldload bwn_v4_ucode and got message:
    Code:
    kldload: can't load bwn_v4_ucode: File exists
    
    Which should mean that module is really loaded. Wifi is still not working, led turned off.
     
  5. richardpl

    richardpl New Member

    Messages:
    841
    Likes Received:
    0
    Is there hardware switch somewhere?

    Anythin displayed in dmesg(8)
     
  6. joag

    joag New Member

    Messages:
    39
    Likes Received:
    0
  7. richardpl

    richardpl New Member

    Messages:
    841
    Likes Received:
    0
    There, fixed it for ya.
     
  8. joag

    joag New Member

    Messages:
    39
    Likes Received:
    0
    :D exactly, that was the idea :p
     
  9. nemirst

    nemirst New Member

    Messages:
    7
    Likes Received:
    0
    Thanks for mentioning this useful command. I see some interesting lines now:
    Code:
    need multicast update callback
    need multicast update callback
    bwn_v4_lp_ucode15: could not load firmware image, error 2
    bwn-open_v4_lp_ucode15: could not load firmware image, error 2
    
    But there is also line in /boot/loader.conf which should load these firmware images:
    Code:
    if_bwn_load="YES"
    bwn_v4_ucode_load="YES"
    I will try http://forums.freebsd.org/showpost.php?p=113500&postcount=227 solution but it seems like a silly workaround.

    Yes, thanks I already read first sections which are more firmware/driver related.


    By the way, I switched to FreeBSD 8.1 x86.
     
  10. nemirst

    nemirst New Member

    Messages:
    7
    Likes Received:
    0
    I now switched to Ndisulator and configured system using this guide: http://www.freebsd.org/doc/handbook/config-network-setup.html.
    When I load wireless module manually all works fine but when it's started automatically at boot adding line
    Code:
    bcmwl5_sys_load="YES"
    to /boot/loader.conf system crashes showing page fault and offers only to restart. I had to use FreeBSD installation disk to fix system modifying loader.conf. Is there any way to start module automatically?
    Also wireless hardware led is disabled but [CMD="dhclient"]wlan0[/CMD] works just fine when loading module manually.
     
  11. richardpl

    richardpl New Member

    Messages:
    841
    Likes Received:
    0
    Why are you trying to load module via loader.conf?

    Just stop doing that.

    You do not need to use install cd to unload module from loader prompt.

    For more info about NDISulator follow this thread:
    http://forums.freebsd.org/showthread.php?t=9204
     
  12. nemirst

    nemirst New Member

    Messages:
    7
    Likes Received:
    0
    I'm loading module via loader.conf because I want it to load automatically at startup and that's what is said if you follow that link I posted before:
    Why shouldn't I follow handbook? Could be I understood incorrectly what was written in it...

    How do I unload module otherwise? I couldn't access commandline before that restart. Was there any secret key combination?
     
  13. richardpl

    richardpl New Member

    Messages:
    841
    Likes Received:
    0
    Information in handbook was never correct. You was very lucky if you ever got ndis modules to not crash during boot.

    Nothing is really secret. From loader prompt/bootloader menu you type unload, this will unload all modules
    now you just type boot command and/or load modules you really want via load command.
    This and the others is explained in various manual pages.

    You can load modules after boot via rc.local and many other options...
     
  14. nemirst

    nemirst New Member

    Messages:
    7
    Likes Received:
    0
    Tried older Broadcom driver and it loaded successfully at startup. One more thing is left. Interface is not getting ip by DHCP automatically at startup. I have to type manually:[CMD="dhclient"]wlan0[/CMD]
    That's only command necessary and wireless is working.
    Wireless entries in /etc/rc.conf:
    Code:
    wlans_ndis0="wlan0"
    ifconfig_wlan0="WPA DHCP"
    
     
  15. richardpl

    richardpl New Member

    Messages:
    841
    Likes Received:
    0
    Use SYNCDHCP.
     
  16. nemirst

    nemirst New Member

    Messages:
    7
    Likes Received:
    0