Announcement

**tomcloyd** · Apr 24, 2014, 08:14 AM

Originally posted by Mal__3 View Post

tomcloyd;
I couldnt agree more - I am an experienced PC user - with only a little linux experince.
I had exactly this issue too - and it totally baffled me. Surely Linux should detect wireless hardware easily and set it up.

Anyway - after much searching i found a simpe way of working.
Connect the ethernet so the computer is connected to the net:
Use 'System Settings' and then look towards the bottom of the panel for 'Driver Manager' and click it.
It then searches for the drivers and the one for my HP G61 appeared 'Broadcomm' I think it was, and the system started downloadeing and installed the driver.
The click on to WiFi symbol ( the dot and arcs pointing up ) - and you should see your routers wifi ID listed, eneter the WPA password and you are done.
Hope that works for you
Mal

The problem, as has been pointed out elsewhere, is that the driver for my chipset is not available through this method.

But beyond that, you say "you should see your routers wifi ID listed" - and I do - then "enter the WPA password and you are done". It isn't asked for. Clicking the wrench I get the "Connection editor" modal window. What's supposed to happen next isn't exactly obvious. Clicking "help > connection editor handbook" yields a page titled "documentation not found".

Clicking "About" on the same dropdown, I see that I'm running Connection Editor 0.9.3.3. I go to the KDE website. It doesn't even have a search function. After browsing for a while, I give up. No mention there of "Connection Editor". Apparently only The Chosen are given the Secret Knowledge.

**tomcloyd** · Apr 24, 2014, 08:15 AM

Originally posted by sithlord48 View Post

there is a new tool that does it even better . fixing the nightmare laptop i had last night i can confirm that at least for broadcom-kernel-source supported devices. i was able to enable the driver and use the wifi directly from the live disc.

Lovely. Care to tell us what it is and where it may be gotten?

**GreyGeek** · Apr 24, 2014, 08:22 AM

http://wireless.kernel.org/en/users/Drivers/b43

b43 and b43legacy

b43 and b43legacy are drivers for the 802.11b/g/n family of wireless chips that Broadcom produces.
Note: Broadcom USB devices are handled by the brcmfmac driver.

b43legacy: supports BCM4306 Rev 2 and cards that have only 802.11b capability
b43: supports all other models

Kernel automatically loads correct driver for the present hardware (it checks for revision of the 802.11 core).

...

Caveats

The b43/b43legacy drivers require proprietary firmware to be loaded onto the wireless chip before it can operate, see below.
If you have an Broadcom USB device, please use the rndis_wlan driver. The b43/b43legacy driver is not meant to support this device.
It is possible to use only one driver at a moment, they are conflicting each other. See Switching between drivers for howto on choosing driver.

Known issues

LP-PHY devices: DMA errors on some machines with kernel 2.6. Problem was fixed in 3.0. Using PIO (module param) can be used as workaround for 2.6.
BCM4318 chipset: AP mode does not work because of packet loss in high transmission rates. Hard to debug & fix.
BCM4321: some cards do not work in DMA mode with kernel 3.1 and older. Problem was fixed in 3.2. A workaround for older kernel is to use PIO mode (b43.pio=1 module param).

...

Supported devices

To find out whether a PCI device is supported by the b43 or b43legacy drivers, issue this lspci command:
lspci -vnn -d 14e4:
The command will output a string similar to this example:
0001:01:01.0 Network controller [0280]: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller [14e4:4318] (rev 02)Ignore everything, except the last part inside of the [ ]. Find that phrase in the below table to determine support.

Code:

[TABLE="class: devtable"]
[TR]
[TD][B]PCI-ID[/B] [/TD]
[TD][B]Supported?[/B] [/TD]
[TD][B]Chip ID[/B] [/TD]
[TD][B]Modes[/B] [/TD]
[TD][B]PHY version[/B] [/TD]
[TD][B]Alternative[/B] [/TD]
[/TR]
[TR]
[TD]14e4:0576 [/TD]
[TD="bgcolor: #ffff00"]not tested [/TD]
[TD]BCM43224 [/TD]
[TD]? [/TD]
[TD]? [/TD]
[TD]wl/[URL="http://wireless.kernel.org/en/users/Drivers/brcm80211"]brcm80211[/URL] [/TD]
[/TR]
[TR]
[TD]14e4:4301 [/TD]
[TD="bgcolor: #90ff90"]yes (b43legacy) [/TD]
[TD]BCM4301 [/TD]
[TD]b [/TD]
[TD]B [/TD]
[TD][/TD]
[/TR]
[TR]
[TD][B]14e4:4306 [/B][/TD]
[TD="bgcolor: #90ff90"][B]yes (b43legacy) [/B][/TD]
[TD][B]BCM4306/2 [/B][/TD]
[TD][B]b/g [/B][/TD]
[TD][B]G [/B][/TD]
[TD][/TD]
[/TR]
[TR]
[TD][B]14e4:4307 [/B][/TD]
[TD="bgcolor: #90ff90"][B]yes [/B][/TD]
[TD][B]BCM4306/3 [/B][/TD]
[TD][B]b/g [/B][/TD]
[TD][B]G [/B][/TD]
[TD][/TD]
[/TR]
[TR]
[TD]14e4:4311 [/TD]
[TD="bgcolor: #90ff90"]yes [/TD]
[TD]BCM4311 [/TD]
[TD]b/g [/TD]
[TD]G [/TD]
[TD]wl 
[/TD]
[/TR]
[TR]
[TD]14e4:4312 [/TD]
[TD="bgcolor: #90ff90"]yes [/TD]
[TD]BCM4311 [/TD]
[TD]a/b/g [/TD]
[TD]G (r8) [/TD]
[TD]wl [/TD]
[/TR]
[TR]
[TD="align: center"]14e4:4313 [/TD]
[TD="bgcolor: #ffff00"]not tested [/TD]
[TD]BCM4311 [/TD]
[TD]a [/TD]
[TD]? [/TD]
[TD]wl [/TD]
[/TR]
[TR]
[TD="bgcolor: #ff9090"]no (WIP) [/TD]
[TD]BCM4313 [/TD]
[TD]b/g/n [/TD]
[TD]LCN (r1) [/TD]
[TD]wl/[URL="http://wireless.kernel.org/en/users/Drivers/brcm80211"]brcm80211[/URL] [/TD]
[/TR]
[TR]
[TD]14e4:4315 [/TD]
[TD="bgcolor: #90ff90"]yes (2.6.33+) [/TD]
[TD]BCM4312 [/TD]
[TD]b/g [/TD]
[TD]LP (r1) [/TD]
[TD]wl [/TD]
[/TR]
[TR]
[TD]14e4:4318 [/TD]
[TD="bgcolor: #90ff90"]yes [/TD]
[TD]BCM4318 [/TD]
[TD]b/g [/TD]
[TD]G (r7) [/TD]
[TD][/TD]
[/TR]
[TR]
[TD]14e4:4319 [/TD]
[TD="bgcolor: #90ff90"]yes [/TD]
[TD]BCM4318 [/TD]
[TD]a/b/g [/TD]
[TD]G [/TD]
[TD][/TD]
[/TR]
[TR]
[TD="align: center"]14e4:4320 [/TD]
[TD="bgcolor: #90ff90"]yes (b43legacy) [/TD]
[TD]BCM4306/2 [/TD]
[TD]b/g [/TD]
[TD]G (r1) [/TD]
[TD][/TD]
[/TR]
[TR]
[TD="bgcolor: #90ff90"]yes [/TD]
[TD]BCM4306/3 [/TD]
[TD]? [/TD]
[TD]G (r2) [/TD]
[TD][/TD]
[/TR]
[TR]
[TD]14e4:4320 (USB) [/TD]
[TD="bgcolor: #ffff00"]no (USB device) [/TD]
[TD]BCM4320 [/TD]
[TD]a/g [/TD]
[TD]? [/TD]
[TD][URL="http://wireless.kernel.org/en/users/Drivers/rndis_wlan"]rndis_wlan[/URL] [/TD]
[/TR]
[TR]
[TD]14e4:4321 [/TD]
[TD="bgcolor: #ffff00"]partially in 2.6.39+ [/TD]
[TD]BCM4321 [/TD]
[TD]? [/TD]
[TD]N (r2) [/TD]
[TD][/TD]
[/TR]
[TR]
[TD]14e4:4322 [/TD]
[TD="bgcolor: #ff9090"]no [/TD]
[TD]BCM4322 [/TD]
[TD]b/g/n [/TD]
[TD]N (r4) [/TD]
[TD][/TD]
[/TR]
[TR]
[TD]14e4:4323 (USB) [/TD]
[TD="bgcolor: #ffff00"]no (USB device) [/TD]
[TD]BCM4323 [/TD]
[TD]a/b/g/n [/TD]
[TD]? [/TD]
[TD]ndiswrapper [/TD]
[/TR]
[TR]
[TD="align: center"]14e4:4324 [/TD]
[TD="bgcolor: #90ff90"]yes (b43legacy) [/TD]
[TD]BCM4309 [/TD]
[TD]a/b/g [/TD]
[TD]G (r1) [/TD]
[TD][/TD]
[/TR]
[TR]
[TD="bgcolor: #90ff90"]yes [/TD]
[TD]BCM4309 [/TD]
[TD]a/b/g [/TD]
[TD]G (r5) [/TD]
[TD][/TD]
[/TR]
[TR]
[TD]14e4:4325 [/TD]
[TD="bgcolor: #90ff90"]yes (b43legacy) [/TD]
[TD]BCM4306/2 [/TD]
[TD]b/g [/TD]
[TD]G (r1) [/TD]
[TD][/TD]
[/TR]
[TR]
[TD]14e4:4328 [/TD]
[TD="bgcolor: #ffff00"]partially in 2.6.39+ [/TD]
[TD]BCM4321 [/TD]
[TD]b/g/n [/TD]
[TD]N (r2) [/TD]
[TD]wl [/TD]
[/TR]
[TR]
[TD]14e4:4329 [/TD]
[TD="bgcolor: #ffff00"]partially in 2.6.39+ [/TD]
[TD]BCM4321 [/TD]
[TD]b/g/n [/TD]
[TD]N (r1) [/TD]
[TD]wl [/TD]
[/TR]
[TR]
[TD]14e4:432a [/TD]
[TD="bgcolor: #ffff00"]not tested [/TD]
[TD]BCM4321 [/TD]
[TD]a/n [/TD]
[TD]N [/TD]
[TD]wl [/TD]
[/TR]
[TR]
[TD]14e4:432b [/TD]
[TD="bgcolor: #90ff90"]partially in 2.6.39+ [/TD]
[TD]BCM4322 [/TD]
[TD]a/b/g/n [/TD]
[TD]N (r4) [/TD]
[TD]wl [/TD]
[/TR]
[TR]
[TD]14e4:432c [/TD]
[TD="bgcolor: #90ff90"]yes [/TD]
[TD]BCM4322 [/TD]
[TD]b/g/n [/TD]
[TD]N [/TD]
[TD]wl [/TD]
[/TR]
[TR]
[TD]14e4:432d [/TD]
[TD="bgcolor: #ffff00"]not tested [/TD]
[TD]BCM4322 [/TD]
[TD]a/n [/TD]
[TD]N [/TD]
[TD]wl [/TD]
[/TR]
[TR]
[TD]14e4:4331 [/TD]
[TD="bgcolor: #90ff90"]yes (3.2-rc3+) [/TD]
[TD]BCM4331 [/TD]
[TD]b/g [/TD]
[TD]HT (r1) [/TD]
[TD]wl [/TD]
[/TR]
[TR]
[TD]14e4:4350 [/TD]
[TD="bgcolor: #90ff90"]yes [/TD]
[TD]BCM43222 [/TD]
[TD]? [/TD]
[TD]N (r6) [/TD]
[TD][/TD]
[/TR]
[TR]
[TD]14e4:4353 [/TD]
[TD="bgcolor: #90ff90"]yes (3.1+) [/TD]
[TD]BCM43224 [/TD]
[TD]a/b/g/n [/TD]
[TD]N (r6) [/TD]
[TD]wl/[URL="http://wireless.kernel.org/en/users/Drivers/brcm80211"]brcm80211[/URL] [/TD]
[/TR]
[TR]
[TD]14e4:4357 [/TD]
[TD="bgcolor: #90ff90"]yes (3.1+) [/TD]
[TD]BCM43225 [/TD]
[TD]b/g/n [/TD]
[TD]N (r6) [/TD]
[TD]wl/[URL="http://wireless.kernel.org/en/users/Drivers/brcm80211"]brcm80211[/URL] [/TD]
[/TR]
[TR]
[TD]14e4:4358 [/TD]
[TD="bgcolor: #ff9090"]no ([URL="http://lists.infradead.org/pipermail/b43-dev/2012-August/002746.html"]WIP[/URL]) [/TD]
[TD]BCM43227 [/TD]
[TD]b/g/n [/TD]
[TD]LCNXN (r0) [/TD]
[TD]wl [/TD]
[/TR]
[TR]
[TD]14e4:4359 [/TD]
[TD="bgcolor: #ff9090"]no [/TD]
[TD]BCM43228 [/TD]
[TD]a/b/g/n [/TD]
[TD]LCNXN (r0) [/TD]
[TD]wl [/TD]
[/TR]
[TR]
[TD]14e4:435a [/TD]
[TD="bgcolor: #ff9090"]no [/TD]
[TD]BCM43228 [/TD]
[TD]? [/TD]
[TD]? [/TD]
[TD]wl [/TD]
[/TR]
[TR]
[TD]14e4:4360 [/TD]
[TD="bgcolor: #ff9090"]no [/TD]
[TD]BCM4360 [/TD]
[TD]? [/TD]
[TD]AC? [/TD]
[TD][/TD]
[/TR]
[TR]
[TD]14e4:4365 [/TD]
[TD="bgcolor: #ff9090"]no [/TD]
[TD]BCM43142 [/TD]
[TD]? [/TD]
[TD]LCN40 (r3) [/TD]
[TD]wl [/TD]
[/TR]
[TR]
[TD]14e4:43a0 [/TD]
[TD="bgcolor: #ff9090"]no [/TD]
[TD]BCM4360 [/TD]
[TD]? [/TD]
[TD]AC? [/TD]
[TD][/TD]
[/TR]
[TR]
[TD]14e4:43a2 [/TD]
[TD="bgcolor: #ff9090"]no [/TD]
[TD]BCM4360 [/TD]
[TD]? [/TD]
[TD]AC (r0) [/TD]
[TD][/TD]
[/TR]
[TR]
[TD]14e4:43b1 [/TD]
[TD="bgcolor: #ff9090"]no [/TD]
[TD]BCM4352 [/TD]
[TD]? [/TD]
[TD]AC? [/TD]
[TD][/TD]
[/TR]
[TR]
[TD]14e4:4727 [/TD]
[TD="bgcolor: #ff9090"]no (WIP) [/TD]
[TD]BCM4313 [/TD]
[TD]b/g/n [/TD]
[TD]LCN (r1) [/TD]
[TD]wl/[URL="http://wireless.kernel.org/en/users/Drivers/brcm80211"]brcm80211[/URL] [/TD]
[/TR]
[TR]
[TD]14e4:a8d6 [/TD]
[TD="bgcolor: #ffff00"]not tested [/TD]
[TD]BCM43222 [/TD]
[TD]? [/TD]
[TD]N (6) [/TD]
[TD][/TD]
[/TR]
[TR]
[TD="align: center"]14e4:a8d8 [/TD]
[TD="bgcolor: #90ff90"]yes (3.6+) [/TD]
[TD]BCM43224 [/TD]
[TD]a/b/g/n [/TD]
[TD]N (r6) [/TD]
[TD][URL="http://wireless.kernel.org/en/users/Drivers/brcm80211"]brcm80211[/URL] [/TD]
[/TR]
[TR]
[TD="bgcolor: #90ff90"]yes (3.6+) [/TD]
[TD]BCM43225 [/TD]
[TD]? [/TD]
[TD]N (r6) [/TD]
[TD][URL="http://wireless.kernel.org/en/users/Drivers/brcm80211"]brcm80211[/URL] [/TD]
[/TR]
[TR]
[TD]14e4:a99d [/TD]
[TD="bgcolor: #ffff00"]not tested [/TD]
[TD]BCM43421? [/TD]
[TD]? [/TD]
[TD]? [/TD]
[TD]wl [/TD]
[/TR]
[/TABLE]

In recent versions of Ubuntu and Debian, installing the firmware-b43-installer package will handle everything for you: 
[B]sudo apt-get install firmware-b43-installer
[/B]

Or, you can follow the advice given here:
https://help.ubuntu.com/community/Wi...ernet%20access

**tomcloyd** · Apr 24, 2014, 08:28 AM

Originally posted by kc1di View Post

b43 may work But I have the same card and bcmwl-kernel-source is the one that works best for me. That is the WL/STA driver.

I wish I had ANY idea what you're talking about. Can you explain. I'm eager to learn, but I just can't devote 3 days to it.

also this page may be of help to you:
https://help.ubuntu.com/community/BroadcomSTA(Wireless)

THAT page is scary! It Is full of information, however. I also think I'm past that point, as I appear to a working driver, now.

I might add the the problem is not Kubuntu's or Ubuntu's because the manufacturer's do not release their drivers as open source so the devs can not modify them to work with linux. The situation is getting better and more manufacturer's are releasing or at least building and releasing drivers for their cards. But the reason they can't be loaded at install is due to copy write and license problems. Which if you have one of their cards makes it a pain, but that is life as it is today. So if you want to complain to anyone it should be to the card manufacturers. Though Broadcom has gotten better over the years.

Well, OK. But my original post didn't complain about lack of access to the driver. It appears that the "Additional drivers" function available in the default launch menu on a fresh install had found the drivers and I had loaded them. MY problem was with what happens next. Having now apparently obtained the drivers, I'm back where I started.

In the Connection Editor, I have made new entry for wireless, and attempted to fill in the data. But I really mostly have NO idea what in blazes I'm doing. And, as I noted here, I can find no documentation anywhere for the Connection Editor. So, I'm faced with a bunch of alphabet soup there, and a mostly different alphabet soup on my router status page.

So again I ask, who does Canonical think uses this stuff? Just the CS major at Carnegie Mellon? What I need is instructions for what to do with the Connection Editor, which may as well be in Russian for all sense I can make of it.

**tomcloyd** · Apr 24, 2014, 08:36 AM

GG - thanks! that a lot of detailed information, which could well be helpful.

But I think I may well be past the point of needing a driver. It appears to me that what I have loaded is working. Here's what I'm seeing:

You agree?

If so, then I just need a clue with what to do with the Connection Editor, as I've stated elsewhere.

**sithlord48** · Apr 24, 2014, 08:37 AM

the new tool is included with 14.04. its called the driver manager. according to shadeslayer its also availble for 13.10 more on his blog.

http://kshadeslayer.wordpress.com/20...r-for-kubuntu/

**tomcloyd** · Apr 24, 2014, 08:53 AM

Here's what I dealing with - what I cannot make sense of:

This just shows that I have a wireless connection set up.

I understand maybe 1/3 of this page.
"Automatically connect to VPN..." Huh?

We are now leaving the human zone.
"SSID" I can guess from my router status page.
"Cloned MAC address" I'm taking a blind leap at.
The rest? I have no idea whatsoever what it even means.

I think, but do not know, that I have chosen the right security protocol.
The password IS correct.

The "IPv..." stuff? Huh?

I really have tried to make sense of this, but since I couldn't find anything even approximating documentation for the software, I'm simply unable to get any further. So...any and all help would be much appreciated!

**tomcloyd** · Apr 24, 2014, 09:01 AM

Originally posted by sithlord48 View Post

the new tool is included with 14.04. its called the driver manager. according to shadeslayer its also availble for 13.10 more on his blog.

http://kshadeslayer.wordpress.com/20...r-for-kubuntu/

Ah. Very nice. This looks like a major advance. I didn't see this in System Settings, when I searched it for anything having to do with networking.

I just went there, and upon accessing the Driver Manager page, I was confronted with "Gathering information about your system" message, and little "busy" whirly thingie.

Then all that went away and I was confronted with a totally blank page, except for a button which said "Refresh driver list". I clicked it, and got a rerun.

Strike the "major advance" remark. What programmer in their right mind would have a process outcome logic branch that results in a blank page? Amazing.Also not ready for prime time, I'd say.

**GreyGeek** · Apr 24, 2014, 02:41 PM

Originally posted by tomcloyd View Post

GG - thanks! that a lot of detailed information, which could well be helpful.

But I think I may well be past the point of needing a driver. It appears to me that what I have loaded is working. Here's what I'm seeing:

[ATTACH=CONFIG]4859[/ATTACH]

You agree?

If so, then I just need a clue with what to do with the Connection Editor, as I've stated elsewhere.

You certainly have a connection, but it is a "wired" connection, made with an ethernet cable connected to your wireless router. The network manager lists several wireless access points so your wireless connection is working. What you have to do if you want a wireless connection is to locate your access point among those listed, click on it, and then click on its connect button. Supply your password and your wireless should connect. IF the network manager refuses to connect then you might be missing parts of your network manager. That happened to me on the last major update. Using Snowhog's "sudo apt-get update" followed by "sudo apt-get dist-upgrade" should pull in any missing components.

**tomcloyd** · Apr 24, 2014, 04:00 PM

Originally posted by GreyGeek View Post

You certainly have a connection, but it is a "wired" connection, made with an ethernet cable connected to your wireless router.

Quite true, of course.

...Locate your access point among those listed, click on it, and then click on its connect button. Supply your password and your wireless should connect. IF the network manager refuses to connect then you might be missing parts of your network manager. That happened to me on the last major update. Using Snowhog's "sudo apt-get update" followed by "sudo apt-get dist-upgrade" should pull in any missing components.

I've done several "...dist-upgrade"s since the clean OS install which started this problem. Just now did another (Chrome is now updating, but nothing else.) So if I'm missing something it isn't showing up, regrettably.

Since I don't understand most of the stuff in the Connection editor I'm simply flying blind. I did try this: On the Wireless tab, I changed Mode from Infrastructure to Access point, then tried again to connect. THIS time it asked for the password (which I'd already supplied on the Wireless security tab). I re-entered it in the field provided, then clicked connect again. No response. I refreshed the display by clicking the green arrow. My named access point just disappeared. I rebooted. The access point is back, but now I'm not getting asked for the password. The connection attempt fails, and the access point disappears. What am I supposed to do - reboot again to get it back?

**tomcloyd** · Apr 24, 2014, 11:46 PM

UPDATE: I downloaded WICD and removed NewworkManager, carefully following the procedure outlined here. WICD allows a somewhat different set of security options, such that I had to change security from WPA-PSK [TKIP] + WPA2-PSK [AES] to WEP.

I can definitely connect using an ethernet cord. When I try to connect wirelessly, though, I just keep getting "bad password" messages. But the password is NOT bad. I was getting this same message before I changed the security protocol. I discovered the protocol problem when looking for why I might be getting the message. It appears that I have not found the reason.

Here's a shot of my screen. My router is Quietmind, and the WICD edit box is also displayed. I hope someone can suggest what I'm doing wrong.

**GreyGeek** · Apr 25, 2014, 09:45 AM

I don't think WICD, which I used to use, is keeping up with the changes. The "bad password" message is a common problem when parts of NetworkManager are not removed.

Your best course of action is to PURGE WICD and re-install NetworkManager.

What appears to be happening is that your connection is repeatedly connecting and disconnecting without every allowing you to log in. If that is the case then you should see "authenticaing ..." followed a couple lines later by "deauthenticating ..." in the SystemLogs.

deauthenticating from by local choice (reason=3)

There are several possible causes for this:
One is that the wireless router may be set for N band only but the wireless chip in your laptop cannot do N band connections, only a or b& g. Check your wireless router and set it to the b&g band to see if that allows it to connect. I installed Kubuntu 14.04 on a 10 year old gateway with a BCM4306 wireless chip and ran into that problem. Also, when my son came over he found that his iPad could not connect to my N band setting. So, last night, I switched it to "NG Mixed", which allows either an N or G connection. (N connections on my wireless router can reach 300Mb/s, but G's maximum is 54Mb/s.)

Another is that your router security setting is wrong. TKIP settings do not connect well. You may have to log into your router and change from TKIP to WPA2-PSK [AES]

Another is the nohwcrypt=0 setting, a parameter of some wireless drivers. It should be set to nohwcrypt=1. However, since your wireless is a BCM4306 (IIRC), this option isn't your problem because the b43legacy driver does not have a nohwcrypt parameter.

And yet another, which is a problem which plagued me in 12.04, is that when the kernel upgraded the new ath9k driver could not drive my Atheros 9642 chip properly. Switching to a 3.9 and later 3.11 kernel solved it. In some cases downgrading the kernel, especially for older machines, may be the solution.

Anyway, to help you with your problem Ubuntu (Kubuntu) has a set of commands that gives information that can be used to resolve your problem.
https://help.ubuntu.com/community/Wi...otingProcedure

**tomcloyd** · Apr 25, 2014, 11:15 AM

GG - thanks for all those potentially productive ideas. I need options, right now, and you've given me a bunch. We both know that if I can keep fiddling with this long enough it will likely work, and in the process my knowledge will also increase (play does this!). So, I have to think that we're closing in on a solution. Won't be able to work on this until later today, but I do much appreciate having a bunch of things to try, when I CAN get to it.

Thanks!

t.

**tomcloyd** · Apr 25, 2014, 07:35 PM

GG: OK, here's my current status on this:

1. WICD is purged; NetworkManager is reinstalled. Wireless connect just fine. Wireless is non-existent.

2. My wireless router was set to automatic, but is not set to b & g band.

3. Router security is now set back to WPA-PSK [TKIP] + WPA2-PSK [AES].

4. kernal issues: I had no problem with wireless and 13.10. My Netbook is an HP Mini-110, with 2 Intel Atom CPU N270 @ 1.60GHz, and 992.3 MiB of RAM. I bought it new several years ago, but I wouldn't think it could be classified as an "older" box. Would you think it advisable to downgrade the kernal? If so, can you suggest where I could learn how to do this?

5. UPDATE: I've worked through the troubleshooting steps at the link you gave me and am awaiting a response. Thanks!

**GreyGeek** · Apr 25, 2014, 09:06 PM

I would complete the wireless trouble shooting guide and see if it resolves your problem before reverting to a prior kernel. If it doesn't help then you can use wget command to download the appropriate 3.11 kernel from the 26-Feb-2014 release of Saucy. It was the last kernel released before Trusty Tahr came out.

Code:

wget [URL]http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.10.5-saucy/linux-headers-3.11.10-03111005-generic_3.11.10-03111005.201402260544_amd64.deb[/URL]
wget [URL]http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.10.5-saucy/linux-image-3.11.10-03111005-generic_3.11.10-03111005.201402260544_amd64.deb[/URL]

or

Code:

wget [URL]http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.10.5-saucy/linux-headers-3.11.10-03111005-generic_3.11.10-03111005.201402260544_i386.deb[/URL]
wget [URL]http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.10.5-saucy/linux-image-3.11.10-03111005-generic_3.11.10-03111005.201402260544_i386.deb[/URL]

And, regardless of which of the two above you choose, you will need to install

Code:

[URL]http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.10.5-saucy/linux-headers-3.11.10-03111005_3.11.10-03111005.201402260544_all.deb[/URL]

(Note that just selecting and copying the above links will not get you the complete URL. You should right mouse on them and chose "copy link location" and past that infront of "wget ".)

But, be warned this is not a totally safe procedure and you might have problems afterwards, even system failures. On the other hand, you might get better performance from your system.

I am curious ... did you do a clean install of Trusty Tahr from an ISO burned onto a CD or USB, or did you do a distribution upgrade?
If you did the upgrade instead of a fresh install I'd download the desktop ISO of Trusty, burn it, and then run it as a LiveCD or LiveUSB and see if it allows a wireless connections.

Announcement

Wireless networking in 14.04 completely baffling to me

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment