Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Greets all.
Just did an install of Slackware 13 on this Acer.
It's got the Broadcom wireless, b43 card.
I've tried executing steps from a couple different sites, one installed ndiswrapper, the other extracted firmware to /lib/firmware.
Neither method i've come across works, and when I execute iwconfig, wlan0 doesn't even show up now. I'm wondering if all this experimenting has screwed my chances of getting this badboy working beyond repair.
If anyone has a quick and effective howto, i'd love to hear it. I'm not too opposed to wiping the disk clean and reinstalling a fresh copy of Slack 13 either, considering i've not attempted a kernel rebuild or anything yet.
I guess the word is...."help "
I've read a good many sites and tried different methods outlined there and am having no luck whatsoever. Just want you fellas to know I tried like hell before giving in and posting another vile Broadcom thread.
I wish I knew. I've since wiped it and am reinstalling a fresh copy at present, but most of the info it threw up regarding wlan0 was blank or zeros. I have a wireless router right in front of me, iwlist scan kept throwing up an error too, can't remember what it was. First i'm going to complete this reinstall. So far, this has been a nightmare, I miss Slack 12
I have to use a usb mouse because the synaptics touchpad mouse won't work in linux (works in my MS-Dos partition?), and when I recompiled my kernel I lost sound, still no mouse, and still couldn't configure wireless.
Unfortunately, Slackware does not include hwinfo. Hardware detection has to be done with standard system tools like lspci.
Though it appears that he already knows which driver supports his card, I am not sure that it is really necessary anymore. Looks like the issue is with installing said driver.
Hi! May I join in?!?
I have the same problem usr robotics MaxG wirless card ... broadcom chipset (BCM4318). I get the following error when I run 'iwconfig wlan0 up':
SIOCISFFLAGS: No such file or directory.
I have a couple machines with the BCM4318 chipset. I've found fwcutter to be the easiest method for me. This will allow the stock B43 kernel driver to do it's thing. I'd recommend researching fwcutter.
and I also tried installing the official broadcom drivers from here: http://www.broadcom.com/support/802.11/linux_sta.php
(although with this method, it asks me to disable a module called ssb which is in use by another called b44 which drives my built in ethernet, so I can't disable it.)
Both from a stock Slack 13 install, and having installed the firmware as defined in step 1, i'm still getting a missing essid. My output from iwconfig looks like so:
Quote:
sh-3.1# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11bg ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry min limit:7 RTS thrff Fragment thr=2352 B
Encryption keyff
Power Managementff
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
which in turn leaves me with:
Quote:
sh-3.1# iwlist wlan0 scan
wlan0 Interface doesn't support scanning : Network is down
Using the information from the first method above, i've determined that I have a supported chipset. lspci reports:
Quote:
sh-3.1# lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
06:01.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
06:02.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
06:04.0 CardBus bridge: ENE Technology Inc CB-712/4 Cardbus Controller (rev 10)
06:04.1 FLASH memory: ENE Technology Inc ENE PCI Memory Stick Card Reader Controller (rev 01)
06:04.2 SD Host controller: ENE Technology Inc ENE PCI Secure Digital Card Reader Controller (rev 01)
06:04.3 FLASH memory: ENE Technology Inc FLASH memory: ENE Technology Inc: (rev 01)
06:04.4 FLASH memory: ENE Technology Inc SD/MMC Card Reader Controller (rev 01)
Any ideas how I might proceed? I'm hoping that I didn't screw up anything in the first method. It put a bunch of files in /lib/firmware. I don't know that anything else is happening, unless that stuff is used by something automagically.
--Q
Last edited by crasslogic; 11-18-2009 at 12:17 PM.
I personally use "wicd" for connecting my wireless. It works well and it's user friendly. You might try this to see if you card is actually working though.
Code:
iwlist wlan0 scan
This should scan for any signals in the area and display relevant info. If it sees your essid, then the next step is to connect to it, either manually or with something like "wicd" or "network manager".
The way I got this wireless NIC working was with ndiswrapper on an Acer with Ubuntu installed. There's a thread here on LQ that gives step by step instructions.
Update!
I half got this badboy working.
If you look, I did the stuff listed in the top of this thread (went to those two sites).
I need help getting this setup right though. Check this out;
I had to blacklist modules ssb, b43, and b44. Now when I start up, I have no network interfaces of any sort.
When i'm logged in, I have to go the directory where the driver (or is it module?) I downloaded from Broadcom was extracted. and do (as per Broadcom's readme)
modprobe lib80211
insmod wl.ko
Once that's done, I can modprobe b43 and b44, so I have my wired and wireless back. I'm perfectly content with using ifconfig and dhcpcd to bring up my wired interface, and using the necessary console tools to connect with my wireless,
so my question now, is there any way to automate the process I just ran down? Where should the stuff from the broadcom folder (the wl.ko for example) go, and what config do I need to edit so that lib80211 is modprobed at boot and wl.ko is inserted BEFORE the b43 and b44 modules are? I'd read somewhere that if b43 or b44 are loaded before the wl module, that they will then require ssb and will, despite being blacklisted, load that module first anyway, which in turn kills the wireless driver.
Thanks for the patience folks.
--Q
Last edited by crasslogic; 11-19-2009 at 07:20 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.