Did I do it right Erik?

Here lies the issue most likely. You have a Broadcom wireless card. The Linux kernel does not ship with the broadcom drivers. I think there is a package you can install for the broadcom that includes the firmware. I have no experience with installing this package on ubuntu, though. You may hit up Google search for "Installing broadcom drivers on Ubuntu". Now that I think about it, I think theres a sticky on this forum somewhere about it. Do a search on the site.

https://www.google.com/search?q=broa...utf-8&oe=utf-8

Here is the linux driver directly from Broadcom. You may have to build it though. Not sure how to do that, though. I'm sure someone here will post further instruction.
https://www.broadcom.com/support/802.11

My coworker had a Dell laptop that had a Broadcom card in it that wouldnt work out of the box either. I had a spare Intel wireless card that I gave her and we replaced the broadcom. Intel (for the most part) just works.


Good Luck.

So if I go and buy an intel based USB wifi adaptor then this will work?

Thanks for the info too btw Erik! Top man! Chris you too mate!

Intel generally always works but I find it more fun to make things work that shouldn't just to give those companies the fickle finger.

1 members found this post helpful.

Soooo. you're not going to believe this.......... I have an old desktop here that requires a usb wifi adaptor......... I just turned off my linux 16.04 laptop, plugged in the usb adaptor robbed from the old desktop pc and hey presto I am online via wifi!!!!! Thanks sooo much for your patience guys. As Chris knows I have been at this all day and it was that bloody simple ha!

Now can I ask for help with the old turning off problem. Basically the 16.04 won't shut down. I can crash it out by holding down the power button during a failed shutdown. But I'd rather have a the drop down menu shut down option work.

And for that we need logs

It may be as simple as something longer to shut down that you're giving it or you don't have permission to shut down but without those logs we don't know

Hi...

What you could do instead is take out the USB adapter, plug in your ethernet cable and then navigate to "Additional Drivers" and install the STA driver for your internal Broadcom adapter. At that point it should work after you reboot it.

Regards...

Dude, that was the first solution I tried this morning as per other forum posts and youtube videos. In 16.04 only one option comes up under additional drivers and it's not the STA driver. I will check and try that again in defference to your superior knowledge! Will let you know the result!

I will post the log asap. I am just reinstalling 16.04 again to undo all the drivel I have put into the Terminal trying to solve my wifi problem

Check back tomorrow for the log, we will work on the not shutting down thing then. Go grab a beer, you deserve it for helping a noob like me! I appreciate the advice and time you put in mate!

Mate the only additional driver that shows is- "using processor microcode firmware for Intel CPUs from Intel microcode (open source)"

This laptop is for my mother so she can have Open Office, a browser and Kodi. The laptop is hers and it was an old Vista junk machine that no longer ran. She'll be fine with the USB wifi adaptor Thanks though mate!

'pal' (thus b/w quotation marks) ...

use the TAG >>> to put outputs

Odd that your adapter doesn't show but you're welcome, hope she enjoys Ubuntu!

Regards...

This might be the wrong place for this comment as I realize the post is how to get bluetooth to work, but I've searched far and wide on how to disable bluetooth and get rid of these nuisance errors in journalctl:
as I don't have or use bluetooth and it being part of a bloated gnome package is impossible to uninstall the package due to other things gnome i use that break (Gnome pita). I read about blacklisting but nothing that I could understand on how to blacklist bluez. I stopped and disabled the service which is what produces the above nagging messages in the journal, it will constantly repeat itself. So next I commented out the lines in:
/usr/share/dbus-1/system-services/org.bluez.service and rebooted once and no error messages related to bluez.
So will have to find out if this truly works after more than one reboot.