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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
If I go into System Settings -> (General tab) -> Network Settings -> Network Connections -> Administrator Mode -> wlan0 "Disabled Wireless Network Device"... and I right-click on that line and "Enable Interface" It simply doesn't work!
If I go into "Administrator mode" and change settings (DHCP automatic, activate when computers starts, etc...) and save changes, the next time I go in there, nothing is set as I previously set it (at least when I reboot the computer)!
When I try to change the settings and then activate the wlan0, I get the following message:
"Could not parse the XML output from the network configuration backend."
"Please wait while saving the network settings..." continues to be displayed in a window in the background during this time.
Does anybody have any ideas on what I can do to get my wireless card working?
# ... iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:""
Mode:Managed Channel:0 Access Point: Not-Associated
Tx-Power=0 dBm
Retry min limit:7 RTS thr: off Fragment thr=2346 B
Encryption key: off
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
Many thanks.
P.S. My Wireless card: "Broadcom 54g MaxPerforance 802.11g"
Last edited by geeeeky.girl; 06-19-2008 at 06:54 PM.
Hmm... how about searching for the other X thousand times people have asked? I must have answered that at least twice in 2 days; I'm too lazy to repeat it a third time. Basically, don't use the graphical tools - they're probably still all defective. Set up your /etc/network/interfaces file correctly instead. If you use WPA-PSK (which you should), you also need to install 'wpasupplicant'.
Hmm... how about searching for the other X thousand times people have asked? I must have answered that at least twice in 2 days;
You being familiar with the problem doesn't mean it's common knowledge. I've looked and searched and haven't been able to find a solution, that is why I've posted here.
Quote:
I'm too lazy to repeat it a third time.
They say good programmers are lazy and that less is more. How about omitting your insulting discourse and simply pasting three or four links? If there are some thousand of them, this shouldn't pose any problem.
Quote:
Basically, don't use the graphical tools - they're probably still all defective.
I'm not a Linux wizard. If it's not graphical, I'm not all that confident that I won't mess everything up even more!
Quote:
Set up your /etc/network/interfaces file correctly instead.
How?!
Quote:
If you use WPA-PSK (which you should), you also need to install 'wpasupplicant'.
Keep in mind that I don't have an Internet connection when I'm on Kubuntu. I have to go back and forth from Linux to Windows to search... What the h*** is WPA-PSK and wpasupplicant?
If anybody out there is interested in helping me out, please do so, I'd certainly appreciate it. If your only objective is to express "I'm better than you!", please refrain from replying.
Last edited by geeeeky.girl; 06-20-2008 at 03:40 PM.
Reason: I don't like being insulted by fellow members, I was much too polite in my initial reply.
"I'm not a Linux wizard. If it's not graphical, I'm not all that confident that I won't mess everything up even more!"
Well, stop being unconfident and play around. If you're not sure, just make a habit of:
1. copy the untouched config file - for example: cp interfaces interfaces.orig
You probably also want to prevent yourself from making changes to the original without being prompted: chmod a-w interfaces.orig
2. play with the config file
3. if it works, leave it (optionally, delete the old one) and if it doesn't work, just copy the original back over:
cp interfaces.orig interfaces
And if you changed the 'write' permissions:
chmod u+w interfaces
There's no point in using a GUI if it's defective - that's virtually guaranteed to screw up your configuration and you're forced to edit the files with pico/nano/vi/emacs/jove/whatever.
Well, WPA-PSK is WiFi Protected Access - Public Shared Key - a data encryption protocol used on wireless networks. The much older "Wireless Encryption Protocol" (WEP) was a scam and did not protect your information at all.
"wpasupplicant" works with the network device to negotiate the keys etc used by WPA-PSK. For Debian-based systems like Kubuntu you can search for software in the listed archives:
apt-cache search somekeyword
You can check if wpasupplicant is already installed:
dpkg -s wpasupplicant
If it's not installed, you can install it (if it's listed in your archives and it is a 'local' list):
apt-get install wpasupplicant
Your archive list would be the file /etc/apt/sources.list
There should be a 'CDROM' entry for your install disk; if there isn't, then you can add your install disk:
apt-cdrom add
Then put in your Kubuntu installer disk when it asks for a disk.
Could someone please help me by doing the following? ...
- Not include any English, prose, or discourse whatsoever. Please, no explanations...
- Cut and paste a complete, typical example of an /etc/network/interfaces file right here that works both with a wired connection and a wireless connection
- Do not write anything else
Many thanks.
P.S. - We'll talk about it later, once my network connections are working...
Last edited by geeeeky.girl; 06-21-2008 at 02:12 PM.
P.S. My Wireless card: "Broadcom 54g MaxPerforance 802.11g"
OK, we're gonna need a bit more info because Broadcom are morons and don't support Linux. That makes getting their garbage going a bit tougher than average. What we need to know are two things:
1) The chipset that the card is using. If you don't know this, open a console and (as root) run lspci. If you want to save the output to a text file run lspci > lspci.txt. That will save the output in a file called lspci.txt and you can open that in any text editor.
2) The driver that Ubuntu is trying to use. Again in a console, type
Quote:
lsmod
(the lsmod > lsmod.txt trick will work here as well). This one you'll probably want to post the whole thing.
The third thing to do (OK, I lied about two things) is look in /lib/firmware and see if there are any files there that have b43, bcm43xx or broadcom in their name.
That is your card and you've got a 4306 chipset. Fortunately, that is one of the less infuriating ones Broadcom makes.
This is from your lsmod:
Quote:
b43 115104 0
So Ubuntu is trying to use the b43 driver, which is the native linux driver for most Broadcom cards.
Quote:
jc@jeje:/lib/firmware$ ls
2.6.24-16-generic
jc@jeje:/lib/firmware$
That looks very much like you haven't install the firmware for the card, which isn't surprising. To use a Broadcom card, you have to have both a driver (b43 in your case) and firmware for that driver. Unfortunately due to Broadcom's licensing, most distros won't distribute the firmware files. However, it looks from this that there are Ubuntu packages of the firmware available. You have an option here:
1) Install the firmware package (probably the easiest)
2) Create your own firmware files. To do this you need to install a program called fwcutter and have a Windows driver available. You can find both of those here.
Once you've got the firmware installed, do a reboot and then your card will likely behave.
In the interest of full disclosure, you've got another option as well, namely ndiswrapper. The b43 driver was built by reverse engineering (i.e. Broadcom had nothing to do with it) and can be a bit flaky. If it doesn't work, you can use ndiswrapper, which is a way to use a Windows driver in Linux. To use ndiswrapper, you have to blacklist b43 (which isn't hard) to prevent the two drivers from conflicting. In the past, ndiswrapper has given better performance on some Broadcom chipsets, but the 4306 is one of the better supported by b43.
Thank you so much for your response. What you've said leads me to believe that it's not all that easy to solve this problem after all, that simply changing the /etc/network/interfaces file won't do the trick!
Based on what you've said, it seems that the ndiswrapper solution is best. I've had a look on the Net and done the following, although, I don't know if what I've done was a good idea:
I now have a thing in my menu, "Settings", with "Windows Wireless Drivers", but I haven't the foggiest idea how to use it! Don't know where anything is! (You're supposed to choose a file to install, I think).
Where do I go from here? Or am I headed in the wrong direction?
Many thanks for your response. I'm eager to get my wifi working so that I can actually use my Kubuntu laptop!
Based on what you've said, it seems that the ndiswrapper solution is best. I've had a look on the Net and done the following, although, I don't know if what I've done was a good idea:
That looks OK to me (although I don't use *buntu, so I may be wrong about this). However, what you appear to have done is installed the nidswrapper binary, which doesn't go far enough. Have a look at the ndiswrapper wiki install instructions starting with the Install Windows Driver section. I'm assuming that the packages you've installed mean that you don't have to compile ndiswrapper.
That doc you linked to seems to be very good, so following that is probably a good idea. Especially be sure to blacklist the Linux drivers since if you don't there will be problems.
Quote:
I now have a thing in my menu, "Settings", with "Windows Wireless Drivers", but I haven't the foggiest idea how to use it! Don't know where anything is! (You're supposed to choose a file to install, I think).
Again, since I don't use *buntu, I might not be the best person to give advice here. If you could give a description of what you're seeing, that might help or you might want to ask on the Ubuntu forum. It also might be helpful if you could tell me what steps you've gotten through on the doc you linked to.
Quote:
Where do I go from here? Or am I headed in the wrong direction?
I don't think you're heading in the wrong direction, but I'm completely unfamiliar with all the GUI monstrosities that *buntu uses. One thing to check is your lsmod output again. If this is heading in the right direction you should see ndiswrapper and NOT see b43. If you see both we've got trouble. You also might have a look at the output of iwconfig and see if it sees a wireless card.
Sorry it's taken me so long to get back to you, I only have a wired Internet connection at the weekend.
I'm having trouble doing what's mentioned here in the link you sent me:
Quote:
If you already have your device working in Windows you can try that driver. Open the device manager and find the name of the .sys driver file listed for the device. You need the .sys file and the .inf file. To find the .inf file search in the \Windows\inf\ directory for a file containing the name of the .sys file. You will need to do an advanced search to search for text within the files.
What do I include in the advanced search and what exactly am I looking for here? I noticed there are tons of .inf files in WINDOWS\INF.
A lot of this is Greek to me, but here's what happens when I run the following command in a shell:
What do I include in the advanced search and what exactly am I looking for here? I noticed there are tons of .inf files in WINDOWS\INF.
Sorry, I probably wasn't real clear. Broadcom drivers in Windows is usually named something like bcmwl5 and there are two files you need, bcmwl5.inf and bcmwl5.sys (You can also get them from Broadcom or from whoever makes your wireless card). Anyway, the .sys file is the actual driver and the .inf has some required information so you need to find, or get, both. Once you've got those two files copied somewhere Linux can see them, you need to use ndiswrapper to install them. By the way, both the .inf and .sys files need to be in the same location.
Once that is done, you should be able to load the ndiswrapper module (modprobe ndiswrapper) and that should give you a wireless interface you can configure.
As for the lspci, we needed that to find out what chipset you have, and since we know that (4306) we don't have to worry about it anymore.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.