[SOLVED] Lenovo Z580 wireless problem

ososid · 10-22-2014, 06:40 PM

Hi guys, time for a new thread hopping you can help me.

Just bought myself a Lenovo Z580 as a "Slacktop" (running Slack 14.1) , so far everything is working fine (half the stuff out of the box...) but I'm getting trouble with my wireless connection.

After forgetting to setup my network during install and editing a couple of stuff I got NetworkMananger working fine with a wired connection, the problem is the wireless. I can find the wireless connection, insert pwd, etc, but the problem is, it never connects? Keeps asking the pwd, I insert, and over and over again...

Any pointers on what I'm doing wrong?

Thanks to anyone who can help.

P.S: now it always says not connected (WLAN Interface)

allend · 10-22-2014, 11:12 PM

Check the output of 'lspci' and if you see a line like

Quote:

04:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)

then you will need to install a suitable driver.
http://www.linuxquestions.org/questi...-a-4175491970/
http://www.linuxquestions.org/questi...rd-4175487183/

Ilgar · 10-23-2014, 02:12 AM

I'm writing this message from a Lenovo Z580 through a wireless connection. This computer never had issues about wireless. I am using wicd, by the way. If your computer still has Windows installed, can you make sure that the wireless hardware works OK under windows?

@allend: My chipset is Atheros:

Code:

04:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01)

ososid · 10-23-2014, 03:34 AM

Quote:

00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 05)
03:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)

No Windows install, full Slack.

Drakeo · 10-23-2014, 03:48 AM

The b43/b43legacy drivers require proprietary firmware to be loaded onto the wireless chip before it can operate.
Did you click the links that was given to you on the first reply. This has been a solved issue that always comes up for years now. years.
this is your eth0

Quote:

Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 05))

this will be your eth1 or visa versa.

Quote:

Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)

Two drivers one is open source one isn't.
For the BCM43 we have
you will need the cutter. http://slackbuilds.org/repository/14.../b43-fwcutter/
then you will need the firmware.http://slackbuilds.org/repository/14.../b43-firmware/

the question should be why do we have such problems with the open source driver and the latest kernel.
the firm ware is needed for the radio functions. the firmware cutter is a proprietary tool that can be down loaded but not distributed.
if using the proprietary one then the open source driver must be blacklisted.
The real problem is it isnt finding the firmware. and probably because it is looking in /lib/firmware/your firmware. but you will notice it is in the /lib/firmware/brcm folder And that is for the USB driver.. because for years the broadcom-driver driver firmware was in /lib/firmware/bcm43 or b43 or just in /lib/firmware.

For other distro's it had other places like hotplug. As you know slackware used the vanilla kernel and the firmware comes with the kernel. I used the slackbuild way after a few years of doing it this way.http://wireless.kernel.org/en/users/Drivers/b43
This explains it all. google is cool stuff

Ilgar · 10-23-2014, 04:50 AM

b43-firmware and b43-fwcutter are also available at slackbuilds.org (or just use sbopkg).

ososid · 10-23-2014, 05:23 AM

Hi, I followed Drakeo instructions and also this SlackBuild and everything is working now.

Thanks for all the replies!

allend · 10-23-2014, 06:58 AM

Quote:

This computer never had issues about wireless.
...
@allend: My chipset is Atheros

Which is what made me think it was likely the OP had a BCM4313.

Quote:

This has been a solved issue that always comes up for years now

I wish someone who actually has one of these devices would write a SlackDocs page.
It would save people like Drakeo having to write the details of the solution time and again.