Ubuntu-Certification

New Latitude E7450 running 14.04 wireless wont work

Asked by Troy Reed

I just pull this out of the box and installed 14.04 on it and the wireless wont come on. Tried the function key to toggle wireless but it wont turn on. Opened the case to make sure it was plugged in, it is. This was a certified unit to work with Ubuntu 14.04 so that’s why I purchased it. Any suggestions would be great.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu-Certification Edit question
Assignee:
No assignee Edit question
Solved by:
Troy Reed
Solved:
Last query:
Last reply:
Revision history for this message
Troy Reed (r-troy) said : 		#1

~~~
If I look for the interface nothing shows up.
iwconfig

lo no wireless extensions

eth2 no wireless extensions
~~~

Revision history for this message
Po-Hsu Lin (cypressyew) said : 		#2

Hi,
please paste the output of "lspci -nnk | grep 0280 -A2" here for diagnosis.

Revision history for this message
Po-Hsu Lin (cypressyew) said : 		#3

Also note that this system was certified pre-install for Ubuntu.
It's stated on the certification website [1] that "Standard images of Ubuntu may not work at all on the system or may not work well"
For more information, please refer to the FAQ here.

Cheers.

[1] http://www.ubuntu.com/certification/hardware/201408-15385/
FAQ #2219: “What's the difference between Certified (Pre-Installed) and Certified?”.

Revision history for this message
Troy Reed (r-troy) said : 		#4

Sorry for the late response, I had to go out of town. I have included the out put of your request.

$ lspci -nnk | grep 0280 -A2
02:00.0 Network controller [0280]: Broadcom Coorporation BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03)
subsystem: Dell Device [1028:0019]

Revision history for this message
Po-Hsu Lin (cypressyew) said : 		#5

OK Cool,
It's a Boardcom wireless chip, you might need to install the proprietary driver for it.

After connect to the Internet, bring up the dash with the Windows key, search for the "Additional Drivers" tool and you might be able to find it there.

Revision history for this message
Troy Reed (r-troy) said : 		#6

Thanks for the help, I installed the driver that came up and it is working now.