You are not logged in.
- Topics: Active | Unanswered
#1 2011-12-03 18:42:30
- Moo-Crumpus
- Member
- From: Hessen / Germany
- Registered: 2003-12-01
- Posts: 1,489
[reopened] WPA2 authentication fails on Lenovo Y560 Broadcom BCM 43225
05:00.0 Network controller [0280]: Broadcom Corporation BCM43225 802.11b/g/n [14e4:4357] (rev 01)
Subsystem: Broadcom Corporation Device [14e4:04da]
09:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM57780 Gigabit Ethernet PCIe [14e4:1692] (rev 01)I run current archlinux 64, using the modules brcmcmac, tg3 in this order, and have linux-firmware installed. Following the wiki, everything should be fine. The wireless card is up, it finds my SSID, but fails to authenticate. I tried wicd, networkmanager. I even tried linux mint, ubuntu: they all fail.
Here is wpa_supplicant talking:
Dec 3 09:57:44 localhost NetworkManager[890]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Dec 3 09:58:08 localhost NetworkManager[890]: <warn> Activation (wlan0/wireless): association took too long.
Dec 3 09:58:08 localhost NetworkManager[890]: <info> (wlan0): device state change: config -> failed (reason 'no-secrets') [50 120 7]
Dec 3 09:58:08 localhost NetworkManager[890]: <warn> Activation (wlan0) failed for access point (ZITRUSGARTEN)
Dec 3 09:58:08 localhost NetworkManager[890]: <info> Marking connection 'ZITRUSGARTEN (automatisch)' invalid.
Dec 3 09:58:08 localhost NetworkManager[890]: <warn> Activation (wlan0) failed.
Dec 3 09:58:08 localhost NetworkManager[890]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Dec 3 09:58:08 localhost NetworkManager[890]: <info> (wlan0): deactivating device (reason 'none') [0]
Dec 3 09:58:08 localhost NetworkManager[890]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Dec 3 09:58:08 localhost NetworkManager[890]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Dec 3 09:58:46 localhost NetworkManager[890]: <info> Activation (wlan0) starting connection 'ZITRUSGARTEN (automatisch)'
Dec 3 09:58:46 localhost NetworkManager[890]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Dec 3 09:58:46 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Dec 3 09:58:46 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Dec 3 09:58:46 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Dec 3 09:58:46 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Dec 3 09:58:46 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Dec 3 09:58:46 localhost NetworkManager[890]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Dec 3 09:58:46 localhost NetworkManager[890]: <info> Activation (wlan0/wireless): access point 'ZITRUSGARTEN (automatisch)' has security, but secrets are required.
Dec 3 09:58:46 localhost NetworkManager[890]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Dec 3 09:58:46 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Dec 3 09:58:46 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Dec 3 09:58:46 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Dec 3 09:58:46 localhost NetworkManager[890]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Dec 3 09:58:46 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Dec 3 09:58:46 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Dec 3 09:58:46 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Dec 3 09:58:46 localhost NetworkManager[890]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Dec 3 09:58:46 localhost NetworkManager[890]: <info> Activation (wlan0/wireless): connection 'ZITRUSGARTEN (automatisch)' has security, and secrets exist. No new secrets needed.
Dec 3 09:58:46 localhost NetworkManager[890]: <info> Config: added 'ssid' value 'ZITRUSGARTEN'
Dec 3 09:58:46 localhost NetworkManager[890]: <info> Config: added 'scan_ssid' value '1'
Dec 3 09:58:46 localhost NetworkManager[890]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Dec 3 09:58:46 localhost NetworkManager[890]: <info> Config: added 'psk' value '<omitted>'
Dec 3 09:58:46 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Dec 3 09:58:46 localhost NetworkManager[890]: <info> Config: set interface ap_scan to 1
Dec 3 09:58:47 localhost NetworkManager[890]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Dec 3 09:58:47 localhost NetworkManager[890]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Dec 3 09:59:11 localhost NetworkManager[890]: <warn> Activation (wlan0/wireless): association took too long.
Dec 3 09:59:11 localhost NetworkManager[890]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Dec 3 09:59:11 localhost NetworkManager[890]: <warn> Activation (wlan0/wireless): asking for new secrets
Dec 3 09:59:11 localhost NetworkManager[890]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Dec 3 09:59:11 localhost NetworkManager[890]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Dec 3 10:00:13 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Dec 3 10:00:13 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Dec 3 10:00:13 localhost NetworkManager[890]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Dec 3 10:00:13 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Dec 3 10:00:13 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Dec 3 10:00:13 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Dec 3 10:00:13 localhost NetworkManager[890]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Dec 3 10:00:13 localhost NetworkManager[890]: <info> Activation (wlan0/wireless): connection 'ZITRUSGARTEN (automatisch)' has security, and secrets exist. No new secrets needed.
Dec 3 10:00:13 localhost NetworkManager[890]: <info> Config: added 'ssid' value 'ZITRUSGARTEN'
Dec 3 10:00:13 localhost NetworkManager[890]: <info> Config: added 'scan_ssid' value '1'
Dec 3 10:00:13 localhost NetworkManager[890]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Dec 3 10:00:13 localhost NetworkManager[890]: <info> Config: added 'psk' value '<omitted>'
Dec 3 10:00:13 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Dec 3 10:00:13 localhost NetworkManager[890]: <info> Config: set interface ap_scan to 1
Dec 3 10:00:13 localhost NetworkManager[890]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Dec 3 10:00:14 localhost NetworkManager[890]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Dec 3 10:00:38 localhost NetworkManager[890]: <warn> Activation (wlan0/wireless): association took too long.
Dec 3 10:00:38 localhost NetworkManager[890]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Dec 3 10:00:38 localhost NetworkManager[890]: <warn> Activation (wlan0/wireless): asking for new secrets
Dec 3 10:00:38 localhost NetworkManager[890]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Dec 3 10:00:38 localhost NetworkManager[890]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Dec 3 10:01:41 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Dec 3 10:01:41 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Dec 3 10:01:41 localhost NetworkManager[890]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Dec 3 10:01:41 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Dec 3 10:01:41 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Dec 3 10:01:41 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Dec 3 10:01:41 localhost NetworkManager[890]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Dec 3 10:01:41 localhost NetworkManager[890]: <info> Activation (wlan0/wireless): connection 'ZITRUSGARTEN (automatisch)' has security, and secrets exist. No new secrets needed.
Dec 3 10:01:41 localhost NetworkManager[890]: <info> Config: added 'ssid' value 'ZITRUSGARTEN'
Dec 3 10:01:41 localhost NetworkManager[890]: <info> Config: added 'scan_ssid' value '1'
Dec 3 10:01:41 localhost NetworkManager[890]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Dec 3 10:01:41 localhost NetworkManager[890]: <info> Config: added 'psk' value '<omitted>'
Dec 3 10:01:41 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Dec 3 10:01:41 localhost NetworkManager[890]: <info> Config: set interface ap_scan to 1
Dec 3 10:01:41 localhost NetworkManager[890]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Dec 3 10:01:42 localhost NetworkManager[890]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Dec 3 10:02:06 localhost NetworkManager[890]: <warn> Activation (wlan0/wireless): association took too long.
Dec 3 10:02:06 localhost NetworkManager[890]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Dec 3 10:02:06 localhost NetworkManager[890]: <warn> Activation (wlan0/wireless): asking for new secrets
Dec 3 10:02:06 localhost NetworkManager[890]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Dec 3 10:02:06 localhost NetworkManager[890]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Dec 3 10:02:08 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Dec 3 10:02:08 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Dec 3 10:02:08 localhost NetworkManager[890]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Dec 3 10:02:08 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Dec 3 10:02:08 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Dec 3 10:02:08 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Dec 3 10:02:08 localhost NetworkManager[890]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Dec 3 10:02:08 localhost NetworkManager[890]: <info> Activation (wlan0/wireless): connection 'ZITRUSGARTEN (automatisch)' has security, and secrets exist. No new secrets needed.
Dec 3 10:02:08 localhost NetworkManager[890]: <info> Config: added 'ssid' value 'ZITRUSGARTEN'
Dec 3 10:02:08 localhost NetworkManager[890]: <info> Config: added 'scan_ssid' value '1'
Dec 3 10:02:08 localhost NetworkManager[890]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Dec 3 10:02:08 localhost NetworkManager[890]: <info> Config: added 'psk' value '<omitted>'
Dec 3 10:02:08 localhost NetworkManager[890]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Dec 3 10:02:08 localhost NetworkManager[890]: <info> Config: set interface ap_scan to 1
Dec 3 10:02:08 localhost NetworkManager[890]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Dec 3 10:02:09 localhost NetworkManager[890]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Dec 3 10:02:33 localhost NetworkManager[890]: <warn> Activation (wlan0/wireless): association took too long.
Dec 3 10:02:33 localhost NetworkManager[890]: <info> (wlan0): device state change: config -> failed (reason 'no-secrets') [50 120 7]
Dec 3 10:02:33 localhost NetworkManager[890]: <warn> Activation (wlan0) failed for access point (ZITRUSGARTEN)
Dec 3 10:02:33 localhost NetworkManager[890]: <info> Marking connection 'ZITRUSGARTEN (automatisch)' invalid.
Dec 3 10:02:33 localhost NetworkManager[890]: <warn> Activation (wlan0) failed.
Dec 3 10:02:33 localhost NetworkManager[890]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Dec 3 10:02:33 localhost NetworkManager[890]: <info> (wlan0): deactivating device (reason 'none') [0]
Dec 3 10:02:33 localhost NetworkManager[890]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Dec 3 10:02:33 localhost NetworkManager[890]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.Last edited by Moo-Crumpus (2011-12-27 13:34:09)
Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]
Offline
#2 2011-12-04 09:41:00
- Strike0
- Member
- From: Germany
- Registered: 2011-09-05
- Posts: 1,491
Re: [reopened] WPA2 authentication fails on Lenovo Y560 Broadcom BCM 43225
For encryption there is always two hands which can fail to handshake, i.e. also the router may be the problem. Don't use WPA/WPA2 mixed mode on the router, but one of them. You may also want to try if WPA works.
Did you have to load a firmware for the card in connection with the driver?
Also it looks like you have alternatives to the driver if the problem persists This lists it also for b43 since the new kernel.
http://linuxwireless.org/en/users/Drivers/b43
Offline
#3 2011-12-05 16:19:11
- Moo-Crumpus
- Member
- From: Hessen / Germany
- Registered: 2003-12-01
- Posts: 1,489
Re: [reopened] WPA2 authentication fails on Lenovo Y560 Broadcom BCM 43225
b43 and the firmware do not match. The firmware is newer, and it complains to need a kernel >= 3.2. Unfortunately, I have no idea which firmware will work with the stock archlinux kernel.
Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]
Offline
#4 2011-12-05 16:29:23
- Gusar
- Member
- Registered: 2009-08-25
- Posts: 3,607
Re: [reopened] WPA2 authentication fails on Lenovo Y560 Broadcom BCM 43225
You said you're using brcmsmac, but now you're mentioning b43. These are two separate things. So which driver are you using?
For brcmsmac: have linux-firmware installed and blacklist bcma
For b43: do not blacklist bcma, blacklist brcmsmac, install b43-firmware from AUR
Offline
#5 2011-12-05 16:42:49
- Moo-Crumpus
- Member
- From: Hessen / Germany
- Registered: 2003-12-01
- Posts: 1,489
Re: [reopened] WPA2 authentication fails on Lenovo Y560 Broadcom BCM 43225
https://bbs.archlinux.org/viewtopic.php?id=127723
The firmware version that I tried was wrong. Using b43 module with bwcutter and firmware version 5.10.56.27.3 is running well.
Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]
Offline
#6 2011-12-05 16:44:39
- Moo-Crumpus
- Member
- From: Hessen / Germany
- Registered: 2003-12-01
- Posts: 1,489
Re: [reopened] WPA2 authentication fails on Lenovo Y560 Broadcom BCM 43225
solved!
Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]
Offline
#7 2011-12-05 19:09:09
- Strike0
- Member
- From: Germany
- Registered: 2011-09-05
- Posts: 1,491
Re: [reopened] WPA2 authentication fails on Lenovo Y560 Broadcom BCM 43225
Great, put that [solved] into the headline sometime. Thats for bbs statistics I hear.
Offline
#8 2011-12-27 13:40:12
- Moo-Crumpus
- Member
- From: Hessen / Germany
- Registered: 2003-12-01
- Posts: 1,489
Re: [reopened] WPA2 authentication fails on Lenovo Y560 Broadcom BCM 43225
Still, I hab a solution that worked for days. Later, the connection was dropped short after connections, and now, no authentication is possible. I run brcmsmac and linux-firmware, bcma blacklistet. Authentication still fails.
Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]
Offline
#9 2011-12-27 14:24:07
- Strike0
- Member
- From: Germany
- Registered: 2011-09-05
- Posts: 1,491
Re: [reopened] WPA2 authentication fails on Lenovo Y560 Broadcom BCM 43225
Check if those line drops/errors occured after updating kernel to 3.1-5.
Besides: when you marked this as solved, you were using b43 and now again the mac driver .. not sure how to read that.
Offline
#10 2011-12-27 15:37:31
- Moo-Crumpus
- Member
- From: Hessen / Germany
- Registered: 2003-12-01
- Posts: 1,489
Re: [reopened] WPA2 authentication fails on Lenovo Y560 Broadcom BCM 43225
b43 was unstable as hell, so I read wireless kernel org's receipts again, and my chip is documented to work fine with brcmsmac. I tried b43, broadcom-wl - none really worked. Any driver that rocks the audience is welcome.
Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]
Offline
#11 2011-12-27 16:07:14
- Strike0
- Member
- From: Germany
- Registered: 2011-09-05
- Posts: 1,491
Re: [reopened] WPA2 authentication fails on Lenovo Y560 Broadcom BCM 43225
Ok, that's bad then, long route of troubles. Can you rule out the router as cause for the wpa troubles?
Offline
#12 2011-12-27 16:14:18
- Gusar
- Member
- Registered: 2009-08-25
- Posts: 3,607
Re: [reopened] WPA2 authentication fails on Lenovo Y560 Broadcom BCM 43225
There's been lots of work done on these cards as recently as last week, in both b43 and brcmsmac. So one thing to try would be compat-wireless. If you go that route, note that the latest brcmsmac driver now uses bcma, so the old wisdom of blacklisting bcma is not valid anymore. You'll also need newer firmware for b43 (b43-firmware-latest instead of b43-firmware).
Last edited by Gusar (2011-12-27 16:15:05)
Offline
#13 2011-12-27 16:40:31
- Moo-Crumpus
- Member
- From: Hessen / Germany
- Registered: 2003-12-01
- Posts: 1,489
Re: [reopened] WPA2 authentication fails on Lenovo Y560 Broadcom BCM 43225
does not work: removed bcma from blacklist, compiling compat-wireless failes.
Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]
Offline
#14 2011-12-29 06:57:20
- Moo-Crumpus
- Member
- From: Hessen / Germany
- Registered: 2003-12-01
- Posts: 1,489
Re: [reopened] WPA2 authentication fails on Lenovo Y560 Broadcom BCM 43225
So here is the current setup:
Modules in /etc/rc.conf
MODULES=(fuse b43 intel-agp drm i915 tg3)
Blacklisted modules
blacklist bcma
This is the only setup I found that does work somehow. It looses connectivity quite often.
Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]
Offline
#15 2011-12-29 07:55:50
- Moo-Crumpus
- Member
- From: Hessen / Germany
- Registered: 2003-12-01
- Posts: 1,489
Re: [reopened] WPA2 authentication fails on Lenovo Y560 Broadcom BCM 43225
Hahaha, it worked for half an hour, and since then it can't authenticate ... again ... this sucks.
Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]
Offline
#16 2011-12-29 08:43:45
- Strike0
- Member
- From: Germany
- Registered: 2011-09-05
- Posts: 1,491
Re: [reopened] WPA2 authentication fails on Lenovo Y560 Broadcom BCM 43225
it would be the router also. Maybe you try something other than WPA2. I have wrangled with a realtek card that had consistent problems with AES, but worked with TKIP fairly reasonable.
Offline
#17 2012-02-19 09:51:15
- Moo-Crumpus
- Member
- From: Hessen / Germany
- Registered: 2003-12-01
- Posts: 1,489
Re: [reopened] WPA2 authentication fails on Lenovo Y560 Broadcom BCM 43225
Ah, no, there are five machines using the router, all are doing fine, the lenovo one does not. The machines are running either win7 or archlinux up to date.
Meanwhile, I have
- brcmsmac is detected and loaded (but udev fails to laod the firmware, workaround using modprobe in rc.local works)
- networkmanager loads wlan0 and finds wireless acess points, including my own
- gnome asks permission for changing network settings (how to stop this?)
- networkmanager asks for authentication, and fails while
-- wireshark sniffs zero packages listening on wlan0 and
-- rfkill reports wlan0 to be not blocked
I have no idea.
Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]
Offline
#18 2012-02-19 12:34:16
- Strike0
- Member
- From: Germany
- Registered: 2011-09-05
- Posts: 1,491
Re: [reopened] WPA2 authentication fails on Lenovo Y560 Broadcom BCM 43225
The encryption problem might of course a driver specific one, so imho the router working with other PCs only means it can do it generally.
Anyway, the permission issue for gnome is described in the wireless wiki. Have a look there first, though that does not really bug once it would connect automatically.
Next ideas: How about turning off wifi-N on the card or try the fresh LTS kernel.
Offline
#19 2012-02-29 10:50:00
- admiralspark
- Member
- From: Alaska, USA
- Registered: 2011-01-07
- Posts: 87
Re: [reopened] WPA2 authentication fails on Lenovo Y560 Broadcom BCM 43225
Ah, no, there are five machines using the router, all are doing fine, the lenovo one does not. The machines are running either win7 or archlinux up to date.
Meanwhile, I have
- brcmsmac is detected and loaded (but udev fails to laod the firmware, workaround using modprobe in rc.local works)
- networkmanager loads wlan0 and finds wireless acess points, including my own
- gnome asks permission for changing network settings (how to stop this?)
- networkmanager asks for authentication, and fails while
-- wireshark sniffs zero packages listening on wlan0 and
-- rfkill reports wlan0 to be not blocked
I have no idea.
Hello,
I also have a Y560, and had some wireless issues in the beginning. I have them fixed now, and can perform EAP-TLS authentication with no issues (yes, also wpa/wpa2/wep/open/etc).
Here's my setup, copy as you will:
in /etc/rc.conf:
MODULES=(broadcom tg3 ...)I do not have any modules blacklisted at this time.
The modules just list iwlwifi and broadcom as being modprobed. So, try without?
I literally just verified my working setup, I use netcfg with a profile since none of the gui's work with my specific authentication method.
Team Ignition Kernel Developer
linux-ideapad developer/maintainer
Flame Kernel developer for Galaxy Nexus and Galaxy S3
Want a cheap, reliable VPS with AWESOME customer service?
Offline