Debian - enable broadcom wireless controller












1














Ok, this is driving me crazy. I'm setting up an old Dell Precision M60 notebook, and I can't manage to enable support for its wireless device on debian squeeze.



What I tried:



lspci | grep -i wireless
02:03.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 02)


nice. I found this page on debianwiki: bcm43xx. First of all, let's check if the device is really supported.



lspci -vnn -d 14e4:
02:03.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 02)
Subsystem: Dell TrueMobile 1300 WLAN Mini-PCI Card [1028:0001]
Flags: bus master, fast devsel, latency 32, IRQ 5
Memory at fafec000 (32-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: b43-pci-bridge


so it's [14e4:4320] (rev 02). And yes, it's supported. Back to the debianwiki page



" For 802.11b-only devices (BCM4301) or 802.11b/g devices with the BCM4306 revision 2 chipset, install firmware-b43legacy-installer"



let's try:



sudo aptitude install firmware-b43legacy-installer 


..



 firmware-b43legacy-installer
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up firmware-b43legacy-installer (4.178.10.4-4) ...
Not supported card here (PCI id 14e4:165
14e4:4320)!
Use b43 firmware. This is just for the b43legacy driver.
Aborting.
dpkg: error processing firmware-b43legacy-installer (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
firmware-b43legacy-installer
Setting up firmware-b43legacy-installer (4.178.10.4-4) ...
Not supported card here (PCI id 14e4:165
14e4:4320)!
Use b43 firmware. This is just for the b43legacy driver.
Aborting.
dpkg: error processing firmware-b43legacy-installer (--configure):
subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
Errors were encountered while processing:
firmware-b43legacy-installer
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up firmware-b43legacy-installer (4.178.10.4-4) ...
Not supported card here (PCI id 14e4:165
14e4:4320)!
Use b43 firmware. This is just for the b43legacy driver.
Aborting.
dpkg: error processing firmware-b43legacy-installer (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
firmware-b43legacy-installer


What? Let's try with the firmware-b43-installer



aptitude install firmware-b43-installer


It works. But:



sudo iwconfig

wlan0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

sudo ifconfig wlan0 up
SIOCSIFFLAGS: No such file or directory


Again? I googled the error and it is related to the firmware, but i Installed it! I already checked in lib/firmware, there's a b43 folder with the .fw files



Any idea?










share|improve this question




















  • 1




    Did you remove the legacy installer explicitly? If you get the exact same error than it is caused by the legacy package not by firmware-b43-installer
    – Ulrich Dangel
    Feb 28 '13 at 14:03










  • @UlrichDangel I removed all the installers and did again firmware-b43-installer. This time it worked! But the SIOCSIFFLAGS error is always here. btw thanks for your contribution! I edited the question
    – randomUser
    Feb 28 '13 at 14:27










  • In my experience (initially Centrino, but several others over time), you can't use ifconfig reliably with WiFi, use the iw.... tools.
    – vonbrand
    Feb 28 '13 at 14:36










  • @randomUser after you did this you have to either reboot or reload (unload and load) the module for your wireless card
    – Ulrich Dangel
    Feb 28 '13 at 14:48










  • @UlrichDangel I rebooted, but unfortunatly nothing changed.
    – randomUser
    Feb 28 '13 at 15:32
















1














Ok, this is driving me crazy. I'm setting up an old Dell Precision M60 notebook, and I can't manage to enable support for its wireless device on debian squeeze.



What I tried:



lspci | grep -i wireless
02:03.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 02)


nice. I found this page on debianwiki: bcm43xx. First of all, let's check if the device is really supported.



lspci -vnn -d 14e4:
02:03.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 02)
Subsystem: Dell TrueMobile 1300 WLAN Mini-PCI Card [1028:0001]
Flags: bus master, fast devsel, latency 32, IRQ 5
Memory at fafec000 (32-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: b43-pci-bridge


so it's [14e4:4320] (rev 02). And yes, it's supported. Back to the debianwiki page



" For 802.11b-only devices (BCM4301) or 802.11b/g devices with the BCM4306 revision 2 chipset, install firmware-b43legacy-installer"



let's try:



sudo aptitude install firmware-b43legacy-installer 


..



 firmware-b43legacy-installer
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up firmware-b43legacy-installer (4.178.10.4-4) ...
Not supported card here (PCI id 14e4:165
14e4:4320)!
Use b43 firmware. This is just for the b43legacy driver.
Aborting.
dpkg: error processing firmware-b43legacy-installer (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
firmware-b43legacy-installer
Setting up firmware-b43legacy-installer (4.178.10.4-4) ...
Not supported card here (PCI id 14e4:165
14e4:4320)!
Use b43 firmware. This is just for the b43legacy driver.
Aborting.
dpkg: error processing firmware-b43legacy-installer (--configure):
subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
Errors were encountered while processing:
firmware-b43legacy-installer
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up firmware-b43legacy-installer (4.178.10.4-4) ...
Not supported card here (PCI id 14e4:165
14e4:4320)!
Use b43 firmware. This is just for the b43legacy driver.
Aborting.
dpkg: error processing firmware-b43legacy-installer (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
firmware-b43legacy-installer


What? Let's try with the firmware-b43-installer



aptitude install firmware-b43-installer


It works. But:



sudo iwconfig

wlan0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

sudo ifconfig wlan0 up
SIOCSIFFLAGS: No such file or directory


Again? I googled the error and it is related to the firmware, but i Installed it! I already checked in lib/firmware, there's a b43 folder with the .fw files



Any idea?










share|improve this question




















  • 1




    Did you remove the legacy installer explicitly? If you get the exact same error than it is caused by the legacy package not by firmware-b43-installer
    – Ulrich Dangel
    Feb 28 '13 at 14:03










  • @UlrichDangel I removed all the installers and did again firmware-b43-installer. This time it worked! But the SIOCSIFFLAGS error is always here. btw thanks for your contribution! I edited the question
    – randomUser
    Feb 28 '13 at 14:27










  • In my experience (initially Centrino, but several others over time), you can't use ifconfig reliably with WiFi, use the iw.... tools.
    – vonbrand
    Feb 28 '13 at 14:36










  • @randomUser after you did this you have to either reboot or reload (unload and load) the module for your wireless card
    – Ulrich Dangel
    Feb 28 '13 at 14:48










  • @UlrichDangel I rebooted, but unfortunatly nothing changed.
    – randomUser
    Feb 28 '13 at 15:32














1












1








1







Ok, this is driving me crazy. I'm setting up an old Dell Precision M60 notebook, and I can't manage to enable support for its wireless device on debian squeeze.



What I tried:



lspci | grep -i wireless
02:03.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 02)


nice. I found this page on debianwiki: bcm43xx. First of all, let's check if the device is really supported.



lspci -vnn -d 14e4:
02:03.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 02)
Subsystem: Dell TrueMobile 1300 WLAN Mini-PCI Card [1028:0001]
Flags: bus master, fast devsel, latency 32, IRQ 5
Memory at fafec000 (32-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: b43-pci-bridge


so it's [14e4:4320] (rev 02). And yes, it's supported. Back to the debianwiki page



" For 802.11b-only devices (BCM4301) or 802.11b/g devices with the BCM4306 revision 2 chipset, install firmware-b43legacy-installer"



let's try:



sudo aptitude install firmware-b43legacy-installer 


..



 firmware-b43legacy-installer
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up firmware-b43legacy-installer (4.178.10.4-4) ...
Not supported card here (PCI id 14e4:165
14e4:4320)!
Use b43 firmware. This is just for the b43legacy driver.
Aborting.
dpkg: error processing firmware-b43legacy-installer (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
firmware-b43legacy-installer
Setting up firmware-b43legacy-installer (4.178.10.4-4) ...
Not supported card here (PCI id 14e4:165
14e4:4320)!
Use b43 firmware. This is just for the b43legacy driver.
Aborting.
dpkg: error processing firmware-b43legacy-installer (--configure):
subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
Errors were encountered while processing:
firmware-b43legacy-installer
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up firmware-b43legacy-installer (4.178.10.4-4) ...
Not supported card here (PCI id 14e4:165
14e4:4320)!
Use b43 firmware. This is just for the b43legacy driver.
Aborting.
dpkg: error processing firmware-b43legacy-installer (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
firmware-b43legacy-installer


What? Let's try with the firmware-b43-installer



aptitude install firmware-b43-installer


It works. But:



sudo iwconfig

wlan0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

sudo ifconfig wlan0 up
SIOCSIFFLAGS: No such file or directory


Again? I googled the error and it is related to the firmware, but i Installed it! I already checked in lib/firmware, there's a b43 folder with the .fw files



Any idea?










share|improve this question















Ok, this is driving me crazy. I'm setting up an old Dell Precision M60 notebook, and I can't manage to enable support for its wireless device on debian squeeze.



What I tried:



lspci | grep -i wireless
02:03.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 02)


nice. I found this page on debianwiki: bcm43xx. First of all, let's check if the device is really supported.



lspci -vnn -d 14e4:
02:03.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 02)
Subsystem: Dell TrueMobile 1300 WLAN Mini-PCI Card [1028:0001]
Flags: bus master, fast devsel, latency 32, IRQ 5
Memory at fafec000 (32-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: b43-pci-bridge


so it's [14e4:4320] (rev 02). And yes, it's supported. Back to the debianwiki page



" For 802.11b-only devices (BCM4301) or 802.11b/g devices with the BCM4306 revision 2 chipset, install firmware-b43legacy-installer"



let's try:



sudo aptitude install firmware-b43legacy-installer 


..



 firmware-b43legacy-installer
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up firmware-b43legacy-installer (4.178.10.4-4) ...
Not supported card here (PCI id 14e4:165
14e4:4320)!
Use b43 firmware. This is just for the b43legacy driver.
Aborting.
dpkg: error processing firmware-b43legacy-installer (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
firmware-b43legacy-installer
Setting up firmware-b43legacy-installer (4.178.10.4-4) ...
Not supported card here (PCI id 14e4:165
14e4:4320)!
Use b43 firmware. This is just for the b43legacy driver.
Aborting.
dpkg: error processing firmware-b43legacy-installer (--configure):
subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
Errors were encountered while processing:
firmware-b43legacy-installer
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up firmware-b43legacy-installer (4.178.10.4-4) ...
Not supported card here (PCI id 14e4:165
14e4:4320)!
Use b43 firmware. This is just for the b43legacy driver.
Aborting.
dpkg: error processing firmware-b43legacy-installer (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
firmware-b43legacy-installer


What? Let's try with the firmware-b43-installer



aptitude install firmware-b43-installer


It works. But:



sudo iwconfig

wlan0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

sudo ifconfig wlan0 up
SIOCSIFFLAGS: No such file or directory


Again? I googled the error and it is related to the firmware, but i Installed it! I already checked in lib/firmware, there's a b43 folder with the .fw files



Any idea?







debian wifi firmware






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 28 '13 at 14:24

























asked Feb 28 '13 at 13:54









randomUser

613




613








  • 1




    Did you remove the legacy installer explicitly? If you get the exact same error than it is caused by the legacy package not by firmware-b43-installer
    – Ulrich Dangel
    Feb 28 '13 at 14:03










  • @UlrichDangel I removed all the installers and did again firmware-b43-installer. This time it worked! But the SIOCSIFFLAGS error is always here. btw thanks for your contribution! I edited the question
    – randomUser
    Feb 28 '13 at 14:27










  • In my experience (initially Centrino, but several others over time), you can't use ifconfig reliably with WiFi, use the iw.... tools.
    – vonbrand
    Feb 28 '13 at 14:36










  • @randomUser after you did this you have to either reboot or reload (unload and load) the module for your wireless card
    – Ulrich Dangel
    Feb 28 '13 at 14:48










  • @UlrichDangel I rebooted, but unfortunatly nothing changed.
    – randomUser
    Feb 28 '13 at 15:32














  • 1




    Did you remove the legacy installer explicitly? If you get the exact same error than it is caused by the legacy package not by firmware-b43-installer
    – Ulrich Dangel
    Feb 28 '13 at 14:03










  • @UlrichDangel I removed all the installers and did again firmware-b43-installer. This time it worked! But the SIOCSIFFLAGS error is always here. btw thanks for your contribution! I edited the question
    – randomUser
    Feb 28 '13 at 14:27










  • In my experience (initially Centrino, but several others over time), you can't use ifconfig reliably with WiFi, use the iw.... tools.
    – vonbrand
    Feb 28 '13 at 14:36










  • @randomUser after you did this you have to either reboot or reload (unload and load) the module for your wireless card
    – Ulrich Dangel
    Feb 28 '13 at 14:48










  • @UlrichDangel I rebooted, but unfortunatly nothing changed.
    – randomUser
    Feb 28 '13 at 15:32








1




1




Did you remove the legacy installer explicitly? If you get the exact same error than it is caused by the legacy package not by firmware-b43-installer
– Ulrich Dangel
Feb 28 '13 at 14:03




Did you remove the legacy installer explicitly? If you get the exact same error than it is caused by the legacy package not by firmware-b43-installer
– Ulrich Dangel
Feb 28 '13 at 14:03












@UlrichDangel I removed all the installers and did again firmware-b43-installer. This time it worked! But the SIOCSIFFLAGS error is always here. btw thanks for your contribution! I edited the question
– randomUser
Feb 28 '13 at 14:27




@UlrichDangel I removed all the installers and did again firmware-b43-installer. This time it worked! But the SIOCSIFFLAGS error is always here. btw thanks for your contribution! I edited the question
– randomUser
Feb 28 '13 at 14:27












In my experience (initially Centrino, but several others over time), you can't use ifconfig reliably with WiFi, use the iw.... tools.
– vonbrand
Feb 28 '13 at 14:36




In my experience (initially Centrino, but several others over time), you can't use ifconfig reliably with WiFi, use the iw.... tools.
– vonbrand
Feb 28 '13 at 14:36












@randomUser after you did this you have to either reboot or reload (unload and load) the module for your wireless card
– Ulrich Dangel
Feb 28 '13 at 14:48




@randomUser after you did this you have to either reboot or reload (unload and load) the module for your wireless card
– Ulrich Dangel
Feb 28 '13 at 14:48












@UlrichDangel I rebooted, but unfortunatly nothing changed.
– randomUser
Feb 28 '13 at 15:32




@UlrichDangel I rebooted, but unfortunatly nothing changed.
– randomUser
Feb 28 '13 at 15:32










2 Answers
2






active

oldest

votes


















0














I'm glad that you were able to resolve the installation problem of the driver... It's often just a simple matter of working out the dependencies and/or orphaned packages.



The reason for your error is that the interface does not exist, from the perspective of ifconfig.



If you look closely at the output of iwconfig, you will notice, in the second line of output, that the interface is not associated with an access point. In order for a wireless 802.11 interface (a/b/g/n) to be of any use in managed mode (which is standard for client operations), the interface must be associated with some other end-point. Once a wireless network is associated with the interface, the wlan0 interface will be able to be addresses via ifconfig, ip, or your other favorite network management tool.



The only way to assign an address to a wireless interface which is not associated with another endpoint is to use the interface in as a host interface, such as an ad-hoc network or using the system as an access point for a wireless network.






share|improve this answer

















  • 2




    jftr this is, based on my experience, wrong. Even though you aren't connected to a specifc AP you should see the wireless card in ifconfig and set it up even though it is not associated.
    – Ulrich Dangel
    Feb 28 '13 at 15:25



















0














The SIOCSIFFLAGS: No such file or directory can have many causes, including trying to change a network interface setting that is not supported by this particular device or driver. In this case it is very likely caused by the firmware not being loaded, but in general I'd like to check dmesg for more detailed error messages.



It looks like the firmware-b43legacy-installer package has some sort of a package scripting bug: when it's expecting just one PCI ID string, it's getting 14e4:165<enter>14e4:4320 instead. This is causing its configuration script to fail. You might send a bug report for that. (My first guess would be that the PCI ID of a wired Broadcom NIC could be causing some regular expression magic to go wrong.)



You can pretty easily do what the firmware-b43legacy-installer package does, manually:



wget --timeout=60 http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o
sudo b43-fwcutter -w /lib/firmware wl_apsta-3.130.20.0.o


After that, the /lib/firmware/b43legacy directory should exist and contain the necessary firmware files.






share|improve this answer





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "106"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f66403%2fdebian-enable-broadcom-wireless-controller%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    I'm glad that you were able to resolve the installation problem of the driver... It's often just a simple matter of working out the dependencies and/or orphaned packages.



    The reason for your error is that the interface does not exist, from the perspective of ifconfig.



    If you look closely at the output of iwconfig, you will notice, in the second line of output, that the interface is not associated with an access point. In order for a wireless 802.11 interface (a/b/g/n) to be of any use in managed mode (which is standard for client operations), the interface must be associated with some other end-point. Once a wireless network is associated with the interface, the wlan0 interface will be able to be addresses via ifconfig, ip, or your other favorite network management tool.



    The only way to assign an address to a wireless interface which is not associated with another endpoint is to use the interface in as a host interface, such as an ad-hoc network or using the system as an access point for a wireless network.






    share|improve this answer

















    • 2




      jftr this is, based on my experience, wrong. Even though you aren't connected to a specifc AP you should see the wireless card in ifconfig and set it up even though it is not associated.
      – Ulrich Dangel
      Feb 28 '13 at 15:25
















    0














    I'm glad that you were able to resolve the installation problem of the driver... It's often just a simple matter of working out the dependencies and/or orphaned packages.



    The reason for your error is that the interface does not exist, from the perspective of ifconfig.



    If you look closely at the output of iwconfig, you will notice, in the second line of output, that the interface is not associated with an access point. In order for a wireless 802.11 interface (a/b/g/n) to be of any use in managed mode (which is standard for client operations), the interface must be associated with some other end-point. Once a wireless network is associated with the interface, the wlan0 interface will be able to be addresses via ifconfig, ip, or your other favorite network management tool.



    The only way to assign an address to a wireless interface which is not associated with another endpoint is to use the interface in as a host interface, such as an ad-hoc network or using the system as an access point for a wireless network.






    share|improve this answer

















    • 2




      jftr this is, based on my experience, wrong. Even though you aren't connected to a specifc AP you should see the wireless card in ifconfig and set it up even though it is not associated.
      – Ulrich Dangel
      Feb 28 '13 at 15:25














    0












    0








    0






    I'm glad that you were able to resolve the installation problem of the driver... It's often just a simple matter of working out the dependencies and/or orphaned packages.



    The reason for your error is that the interface does not exist, from the perspective of ifconfig.



    If you look closely at the output of iwconfig, you will notice, in the second line of output, that the interface is not associated with an access point. In order for a wireless 802.11 interface (a/b/g/n) to be of any use in managed mode (which is standard for client operations), the interface must be associated with some other end-point. Once a wireless network is associated with the interface, the wlan0 interface will be able to be addresses via ifconfig, ip, or your other favorite network management tool.



    The only way to assign an address to a wireless interface which is not associated with another endpoint is to use the interface in as a host interface, such as an ad-hoc network or using the system as an access point for a wireless network.






    share|improve this answer












    I'm glad that you were able to resolve the installation problem of the driver... It's often just a simple matter of working out the dependencies and/or orphaned packages.



    The reason for your error is that the interface does not exist, from the perspective of ifconfig.



    If you look closely at the output of iwconfig, you will notice, in the second line of output, that the interface is not associated with an access point. In order for a wireless 802.11 interface (a/b/g/n) to be of any use in managed mode (which is standard for client operations), the interface must be associated with some other end-point. Once a wireless network is associated with the interface, the wlan0 interface will be able to be addresses via ifconfig, ip, or your other favorite network management tool.



    The only way to assign an address to a wireless interface which is not associated with another endpoint is to use the interface in as a host interface, such as an ad-hoc network or using the system as an access point for a wireless network.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Feb 28 '13 at 14:52









    Rob Gibson

    43626




    43626








    • 2




      jftr this is, based on my experience, wrong. Even though you aren't connected to a specifc AP you should see the wireless card in ifconfig and set it up even though it is not associated.
      – Ulrich Dangel
      Feb 28 '13 at 15:25














    • 2




      jftr this is, based on my experience, wrong. Even though you aren't connected to a specifc AP you should see the wireless card in ifconfig and set it up even though it is not associated.
      – Ulrich Dangel
      Feb 28 '13 at 15:25








    2




    2




    jftr this is, based on my experience, wrong. Even though you aren't connected to a specifc AP you should see the wireless card in ifconfig and set it up even though it is not associated.
    – Ulrich Dangel
    Feb 28 '13 at 15:25




    jftr this is, based on my experience, wrong. Even though you aren't connected to a specifc AP you should see the wireless card in ifconfig and set it up even though it is not associated.
    – Ulrich Dangel
    Feb 28 '13 at 15:25













    0














    The SIOCSIFFLAGS: No such file or directory can have many causes, including trying to change a network interface setting that is not supported by this particular device or driver. In this case it is very likely caused by the firmware not being loaded, but in general I'd like to check dmesg for more detailed error messages.



    It looks like the firmware-b43legacy-installer package has some sort of a package scripting bug: when it's expecting just one PCI ID string, it's getting 14e4:165<enter>14e4:4320 instead. This is causing its configuration script to fail. You might send a bug report for that. (My first guess would be that the PCI ID of a wired Broadcom NIC could be causing some regular expression magic to go wrong.)



    You can pretty easily do what the firmware-b43legacy-installer package does, manually:



    wget --timeout=60 http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o
    sudo b43-fwcutter -w /lib/firmware wl_apsta-3.130.20.0.o


    After that, the /lib/firmware/b43legacy directory should exist and contain the necessary firmware files.






    share|improve this answer


























      0














      The SIOCSIFFLAGS: No such file or directory can have many causes, including trying to change a network interface setting that is not supported by this particular device or driver. In this case it is very likely caused by the firmware not being loaded, but in general I'd like to check dmesg for more detailed error messages.



      It looks like the firmware-b43legacy-installer package has some sort of a package scripting bug: when it's expecting just one PCI ID string, it's getting 14e4:165<enter>14e4:4320 instead. This is causing its configuration script to fail. You might send a bug report for that. (My first guess would be that the PCI ID of a wired Broadcom NIC could be causing some regular expression magic to go wrong.)



      You can pretty easily do what the firmware-b43legacy-installer package does, manually:



      wget --timeout=60 http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o
      sudo b43-fwcutter -w /lib/firmware wl_apsta-3.130.20.0.o


      After that, the /lib/firmware/b43legacy directory should exist and contain the necessary firmware files.






      share|improve this answer
























        0












        0








        0






        The SIOCSIFFLAGS: No such file or directory can have many causes, including trying to change a network interface setting that is not supported by this particular device or driver. In this case it is very likely caused by the firmware not being loaded, but in general I'd like to check dmesg for more detailed error messages.



        It looks like the firmware-b43legacy-installer package has some sort of a package scripting bug: when it's expecting just one PCI ID string, it's getting 14e4:165<enter>14e4:4320 instead. This is causing its configuration script to fail. You might send a bug report for that. (My first guess would be that the PCI ID of a wired Broadcom NIC could be causing some regular expression magic to go wrong.)



        You can pretty easily do what the firmware-b43legacy-installer package does, manually:



        wget --timeout=60 http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o
        sudo b43-fwcutter -w /lib/firmware wl_apsta-3.130.20.0.o


        After that, the /lib/firmware/b43legacy directory should exist and contain the necessary firmware files.






        share|improve this answer












        The SIOCSIFFLAGS: No such file or directory can have many causes, including trying to change a network interface setting that is not supported by this particular device or driver. In this case it is very likely caused by the firmware not being loaded, but in general I'd like to check dmesg for more detailed error messages.



        It looks like the firmware-b43legacy-installer package has some sort of a package scripting bug: when it's expecting just one PCI ID string, it's getting 14e4:165<enter>14e4:4320 instead. This is causing its configuration script to fail. You might send a bug report for that. (My first guess would be that the PCI ID of a wired Broadcom NIC could be causing some regular expression magic to go wrong.)



        You can pretty easily do what the firmware-b43legacy-installer package does, manually:



        wget --timeout=60 http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o
        sudo b43-fwcutter -w /lib/firmware wl_apsta-3.130.20.0.o


        After that, the /lib/firmware/b43legacy directory should exist and contain the necessary firmware files.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 12 at 8:53









        telcoM

        15.8k12143




        15.8k12143






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f66403%2fdebian-enable-broadcom-wireless-controller%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Morgemoulin

            Scott Moir

            Souastre