Description of problem: I've done several clean installs on M3. I cannot get the wireless to work --- at all. I've tried on several platforms and with RealTec 8192cu 801.11n and Atheros 5212/13. I've looked into the somewhat contradictory erratas and to no avail. How to reproduce: Steps to Reproduce: 1. Try to configure with MCC. 2. The link does NOT work. 3. Going back in the MCC the configurations drops back to openWEP despite my selection af WPA2 with private key. 4. Deleting the interface the MCC states the network card as a DRAM controller. It seem that it is not possible to connect to the AP. I have several Windozes, Androids and a wireless printer connected to the router, a ZyXel P-2601HN-F1. What on earth to do ? Reproducible: Steps to Reproduce:
CC: sysadmin-bugs => mageiaComponent: Release (media or process) => RPM PackagesSummary: Wirwless: Unable to connect to a WPA2 network with hidden SSID. => Wireless: Unable to connect to a WPA2 network with hidden SSID.
Are you using KDE or Gnome?
(In reply to Sander Lepik from comment #1) > Are you using KDE or Gnome? I use KDE 4.10.2 but NO applets from KDE and NO konfiguration via KDE. My kernel is 3.8.13-server-1.mga3
I would suggest you to try with NetworkManager. 1. Install this package: plasma-applet-networkmanagement. 2. Use MCC and configure your wireless device to be managed by NM. 3. Reboot your system. 4. After logging in right-click on the small icon that displays hidden tray icons and choose properties. From there enable network management and try to use it to configure your connection. Does this help or is the result the same?
(In reply to Sander Lepik from comment #3) > I would suggest you to try with NetworkManager. > > 1. Install this package: plasma-applet-networkmanagement. > 2. Use MCC and configure your wireless device to be managed by NM. > 3. Reboot your system. > 4. After logging in right-click on the small icon that displays hidden tray > icons and choose properties. From there enable network management and try to > use it to configure your connection. > > Does this help or is the result the same? OK - 1. Install this package: plasma-applet-networkmanagement. OK - 2. Use MCC and configure your wireless device to be managed by NM. OK - 3. Reboot your system. NOT OK - 4. After logging in right-click on the small icon that displays hidden tray icons and choose properties. From there enable network management and try to use it to configure your connection. Also if I just try to enable the wlan - the applet dies. Again the configuration does NOT keep the wanted WPA2 personal key config. So unfortunately this did not solve my problem.
Which applet dies? Plasma applet or net_applet? Which applet did you use to configure your network? Don't use the net_applet. I don't wanna believe that the NM applet can't remember the configuration. Never seen that before :/
(In reply to Sander Lepik from comment #5) > Which applet dies? Plasma applet or net_applet? Which applet did you use to > configure your network? Don't use the net_applet. I don't wanna believe that > the NM applet can't remember the configuration. Never seen that before :/ Well, maybe several things are in action here ? Pls look into bugs 8754, 8756 9541, 10013 and 10150. I cannot find any plasma-applet besides the network applet - that I activated via the KDE Start Menu - and which is the one that dies. As it seems I should NOT use this: Can you maybe guide to the right applet to use - I cannot find it using run og in the KDE menu. Spo how to strat the applet ?
(In reply to René Lagoni Neukirch from comment #4) > NOT OK - 4. After logging in right-click on the small icon that displays > hidden tray > icons and choose properties. From there enable network management and try to > use it to configure your connection. What was not OK with that? You didn't find how to do it or ... ?
(In reply to Sander Lepik from comment #7) > (In reply to René Lagoni Neukirch from comment #4) > > NOT OK - 4. After logging in right-click on the small icon that displays > > hidden tray > > icons and choose properties. From there enable network management and try to > > use it to configure your connection. > > What was not OK with that? You didn't find how to do it or ... ? I decided to reboot just in case .. Now I have enabled the applet, configured the wireless with WPA2 PSK. I now sees the network - PROGRESS ! - but it does not connect, unfortunately.
What's the output of this command: ps aux|grep wpa Also, what do you see in dmesg, anything interesting there?
To both 8 and 9: rln@rln ~]$ ps aux | grep wpa root 1044 0.0 0.0 45888 3312 ? Ss 13:46 0:00 /usr/sbin/wpa_supplicant -u -f /var/log/wpa_supplicant.log -c /etc/wpa_supplicant.conf -iwlan0 -P /run/wpa_supplicant.pid rln 5459 0.0 0.0 13832 660 pts/1 D+ 13:56 0:00 grep --color wpa Therefore - only one WPA supplicant is running. dmesg filter for 2 items, 8192 and link: [rln@rln ~]$ dmesg| grep 8192 [ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff88011dc00000 s83712 r8192 d22784 u524288 [ 0.000000] pcpu-alloc: s83712 r8192 d22784 u524288 alloc=1*2097152 [ 13.852191] rtl8192cu: Chip version 0x10 [ 13.935668] rtl8192cu: MAC address: 80:1f:02:81:88:19 [ 13.935674] rtl8192cu: Board Type 2 [ 13.935939] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw.bin [ 13.935975] usbcore: registered new interface driver rtl8192cu [ 28.937131] rtl8192cu: MAC auto ON okay! [ 28.969876] rtl8192cu: Tx queue select: 0x05 [ 152.286113] rtl8192cu: MAC auto ON okay! [ 152.318859] rtl8192cu: Tx queue select: 0x05 [ 343.982365] rtl8192cu: MAC auto ON okay! [ 344.015136] rtl8192cu: Tx queue select: 0x05 also - I stopped the eth connection before trying to connect via wifi: [rln@rln ~]$ dmesg| grep link [ 0.446314] audit: initializing netlink socket (disabled) [ 0.892016] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 1.241941] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 1.611848] ata5: SATA link down (SStatus 0 SControl 300) [ 1.961770] ata6: SATA link down (SStatus 0 SControl 300) [ 30.757578] r8169 0000:03:00.0 eth0: link down [ 30.757641] r8169 0000:03:00.0 eth0: link down [ 32.705519] r8169 0000:03:00.0 eth0: link up [ 62.689460] ctnetlink v0.93: registering with nfnetlink. [ 211.957886] r8169 0000:03:00.0 eth0: link down [ 211.957973] r8169 0000:03:00.0 eth0: link down [ 213.916606] r8169 0000:03:00.0 eth0: link up [ 288.881046] r8169 0000:03:00.0 eth0: link down [ 288.881113] r8169 0000:03:00.0 eth0: link down [ 290.969217] r8169 0000:03:00.0 eth0: link up [ 344.518869] r8169 0000:03:00.0 eth0: link down [ 344.518924] r8169 0000:03:00.0 eth0: link down [ 346.429299] r8169 0000:03:00.0 eth0: link up [ 407.085145] r8169 0000:03:00.0 eth0: link down [ 407.085195] r8169 0000:03:00.0 eth0: link down [ 408.986947] r8169 0000:03:00.0 eth0: link up [ 495.605835] r8169 0000:03:00.0 eth0: link down [ 495.605886] r8169 0000:03:00.0 eth0: link down [ 497.549479] r8169 0000:03:00.0 eth0: link up
One more observation: Even if the wif card is configured via the applet, when I try to enable it the applet asks for SSID, and the the applet asks for security and PSK ... hm strange.
Please attach the output of this command: systemctl status -n300 NetworkManager.service
FYI: I tried to make the SSID visible, I'v tried to hard-configure the connection with IP etc. And as of the requested command. Sure, here is the lot: [root@rln rln]# systemctl status -n300 NetworkManager.service NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled) Active: active (running) since Mon, 2013-06-24 14:21:39 CEST; 7min ago Main PID: 1046 (NetworkManager) CGroup: name=systemd:/system/NetworkManager.service â 1046 /usr/sbin/NetworkManager --no-daemon â 2905 /sbin/dhclient -d -sf /usr/libexec/nm-dhcp-client.action -pf /var/run/dhclient-eth0.pid -lf /var/lib/NetworkManager/dhc... Jun 24 14:21:37 rln systemd[1]: Starting Network Manager... Jun 24 14:21:37 rln NetworkManager[1046]: <info> NetworkManager (version 0.9.8.0) is starting... Jun 24 14:21:37 rln NetworkManager[1046]: <info> Read config file /etc/NetworkManager/NetworkManager.conf Jun 24 14:21:37 rln NetworkManager[1046]: <info> WEXT support is enabled Jun 24 14:21:39 rln NetworkManager[1046]: ifcfg-rh: Acquired D-Bus service com.redhat.ifcfgrh1 Jun 24 14:21:39 rln NetworkManager[1046]: <info> Loaded plugin ifcfg-rh: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the Netw...ng list. Jun 24 14:21:39 rln NetworkManager[1046]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the Netwo...ng list. Jun 24 14:21:39 rln NetworkManager[1046]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-wlan0 ... Jun 24 14:21:39 rln NetworkManager[1046]: <warn> failed to allocate link cache: (-10) Operation not supported Jun 24 14:21:39 rln NetworkManager[1046]: ifcfg-rh: error: Missing SSID Jun 24 14:21:39 rln NetworkManager[1046]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-SCBD52D8 ... Jun 24 14:21:39 rln NetworkManager[1046]: discover_mac_address: assertion `device != NULL' failed Jun 24 14:21:39 rln NetworkManager[1046]: ifcfg-rh: read connection 'SCBD52D8' Jun 24 14:21:39 rln NetworkManager[1046]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ... Jun 24 14:21:39 rln NetworkManager[1046]: ifcfg-rh: read connection 'System eth0' Jun 24 14:21:39 rln NetworkManager[1046]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-SCBD52D8-2 ... Jun 24 14:21:39 rln NetworkManager[1046]: discover_mac_address: assertion `device != NULL' failed Jun 24 14:21:39 rln NetworkManager[1046]: ifcfg-rh: read connection 'SCBD52D8' Jun 24 14:21:39 rln NetworkManager[1046]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ... Jun 24 14:21:39 rln NetworkManager[1046]: <info> monitoring kernel firmware directory '/lib/firmware'. Jun 24 14:21:39 rln NetworkManager[1046]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-...l8192cu) Jun 24 14:21:39 rln NetworkManager[1046]: <info> WiFi hardware radio set enabled Jun 24 14:21:39 rln systemd[1]: Started Network Manager. Jun 24 14:21:39 rln NetworkManager[1046]: <info> WiFi enabled by radio killswitch; enabled by state file Jun 24 14:21:39 rln NetworkManager[1046]: <info> WWAN enabled by radio killswitch; enabled by state file Jun 24 14:21:39 rln NetworkManager[1046]: <info> WiMAX enabled by radio killswitch; enabled by state file Jun 24 14:21:39 rln NetworkManager[1046]: <info> Networking is enabled by state file Jun 24 14:21:39 rln NetworkManager[1046]: <info> (wlan0): using nl80211 for WiFi device control Jun 24 14:21:39 rln NetworkManager[1046]: <info> (wlan0): driver supports Access Point (AP) mode Jun 24 14:21:39 rln NetworkManager[1046]: <info> (wlan0): new 802.11 WiFi device (driver: 'rtl8192cu' ifindex: 3) Jun 24 14:21:39 rln NetworkManager[1046]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/0 Jun 24 14:21:39 rln NetworkManager[1046]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Jun 24 14:21:39 rln NetworkManager[1046]: <info> (wlan0): preparing device. Jun 24 14:21:40 rln NetworkManager[1046]: <info> (wlan0): deactivating device (reason 'managed') [2] Jun 24 14:21:40 rln NetworkManager[1046]: <warn> failed to allocate link cache: (-10) Operation not supported Jun 24 14:21:40 rln NetworkManager[1046]: <info> (eth0): carrier is OFF Jun 24 14:21:40 rln NetworkManager[1046]: <info> (eth0): new Ethernet device (driver: 'r8169' ifindex: 2) Jun 24 14:21:40 rln NetworkManager[1046]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/1 Jun 24 14:21:40 rln NetworkManager[1046]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Jun 24 14:21:40 rln NetworkManager[1046]: <info> (eth0): bringing up device. Jun 24 14:21:40 rln NetworkManager[1046]: <info> (eth0): preparing device. Jun 24 14:21:40 rln NetworkManager[1046]: <info> (eth0): deactivating device (reason 'managed') [2] Jun 24 14:21:40 rln NetworkManager[1046]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring... Jun 24 14:21:40 rln NetworkManager[1046]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring... Jun 24 14:21:40 rln NetworkManager[1046]: <info> modem-manager is now available Jun 24 14:21:40 rln NetworkManager[1046]: <info> (wlan0) supports 1 scan SSIDs Jun 24 14:21:40 rln NetworkManager[1046]: <info> (wlan0): supplicant interface state: starting -> ready Jun 24 14:21:40 rln NetworkManager[1046]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42] Jun 24 14:21:40 rln NetworkManager[1046]: <warn> Trying to remove a non-existant call id. Jun 24 14:21:40 rln NetworkManager[1046]: <info> (wlan0): supplicant interface state: ready -> scanning Jun 24 14:21:40 rln NetworkManager[1046]: <info> (wlan0) supports 1 scan SSIDs Jun 24 14:21:40 rln NetworkManager[1046]: <warn> connection /org/freedesktop/NetworkManager/Settings/0 failed to activate: (2) Device not ...vailable Jun 24 14:21:42 rln NetworkManager[1046]: <info> (eth0): carrier now ON (device state 20) Jun 24 14:21:42 rln NetworkManager[1046]: <info> (eth0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40] Jun 24 14:21:42 rln NetworkManager[1046]: <info> Auto-activating connection 'System eth0'. Jun 24 14:21:42 rln NetworkManager[1046]: <info> Activation (eth0) starting connection 'System eth0' Jun 24 14:21:42 rln NetworkManager[1046]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Jun 24 14:21:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... Jun 24 14:21:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started... Jun 24 14:21:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... Jun 24 14:21:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete. Jun 24 14:21:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting... Jun 24 14:21:42 rln NetworkManager[1046]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0] Jun 24 14:21:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful. Jun 24 14:21:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. Jun 24 14:21:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete. Jun 24 14:21:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started... Jun 24 14:21:42 rln NetworkManager[1046]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0] Jun 24 14:21:42 rln NetworkManager[1046]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds) Jun 24 14:21:42 rln NetworkManager[1046]: <info> dhclient started with pid 1260 Jun 24 14:21:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Jun 24 14:21:42 rln dhclient[1260]: Internet Systems Consortium DHCP Client 4.2.5-P1 Jun 24 14:21:42 rln dhclient[1260]: Copyright 2004-2013 Internet Systems Consortium. Jun 24 14:21:42 rln dhclient[1260]: All rights reserved. Jun 24 14:21:42 rln dhclient[1260]: For info, please visit https://www.isc.org/software/dhcp/ Jun 24 14:21:42 rln dhclient[1260]: Jun 24 14:21:42 rln NetworkManager[1046]: <info> (eth0): DHCPv4 state changed nbi -> preinit Jun 24 14:21:42 rln dhclient[1260]: Listening on LPF/eth0/d4:3d:7e:2e:27:60 Jun 24 14:21:42 rln dhclient[1260]: Sending on LPF/eth0/d4:3d:7e:2e:27:60 Jun 24 14:21:42 rln dhclient[1260]: Sending on Socket/fallback Jun 24 14:21:42 rln dhclient[1260]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jun 24 14:21:42 rln dhclient[1260]: DHCPACK from 192.168.1.1 Jun 24 14:21:42 rln dhclient[1260]: bound to 192.168.1.52 -- renewal in 34833 seconds. Jun 24 14:21:42 rln NetworkManager[1046]: <info> (eth0): DHCPv4 state changed preinit -> reboot Jun 24 14:21:42 rln NetworkManager[1046]: <info> address 192.168.1.52 Jun 24 14:21:42 rln NetworkManager[1046]: <info> prefix 24 (255.255.255.0) Jun 24 14:21:42 rln NetworkManager[1046]: <info> gateway 192.168.1.1 Jun 24 14:21:42 rln NetworkManager[1046]: <info> hostname 'rln' Jun 24 14:21:42 rln NetworkManager[1046]: <info> nameserver '89.150.129.22' Jun 24 14:21:42 rln NetworkManager[1046]: <info> nameserver '89.150.129.10' Jun 24 14:21:42 rln NetworkManager[1046]: <info> domain name 'P-2601HNU-F1' Jun 24 14:21:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled... Jun 24 14:21:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) started... Jun 24 14:21:43 rln NetworkManager[1046]: <info> (eth0): device state change: ip-config -> secondaries (reason 'none') [70 90 0] Jun 24 14:21:43 rln NetworkManager[1046]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete. Jun 24 14:21:43 rln NetworkManager[1046]: <info> (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0] Jun 24 14:21:43 rln NetworkManager[1046]: <info> Policy set 'System eth0' (eth0) as default for IPv4 routing and DNS. Jun 24 14:21:43 rln NetworkManager[1046]: <info> Writing DNS information to /sbin/resolvconf Jun 24 14:21:43 rln NetworkManager[1046]: <info> Activation (eth0) successful, device activated. Jun 24 14:22:16 rln NetworkManager[1046]: <info> (eth0): device state change: activated -> disconnected (reason 'user-requested') [100 30 39] Jun 24 14:22:16 rln NetworkManager[1046]: <info> (eth0): deactivating device (reason 'user-requested') [39] Jun 24 14:22:16 rln NetworkManager[1046]: <info> (eth0): canceled DHCP transaction, DHCP client pid 1260 Jun 24 14:22:16 rln NetworkManager[1046]: <info> Removing DNS information from /sbin/resolvconf Jun 24 14:22:42 rln NetworkManager[1046]: <info> Activation (eth0) starting connection 'System eth0' Jun 24 14:22:42 rln NetworkManager[1046]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Jun 24 14:22:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... Jun 24 14:22:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started... Jun 24 14:22:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... Jun 24 14:22:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete. Jun 24 14:22:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting... Jun 24 14:22:42 rln NetworkManager[1046]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0] Jun 24 14:22:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful. Jun 24 14:22:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. Jun 24 14:22:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete. Jun 24 14:22:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started... Jun 24 14:22:42 rln NetworkManager[1046]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0] Jun 24 14:22:42 rln NetworkManager[1046]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds) Jun 24 14:22:42 rln NetworkManager[1046]: <info> dhclient started with pid 2905 Jun 24 14:22:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Jun 24 14:22:42 rln dhclient[2905]: Internet Systems Consortium DHCP Client 4.2.5-P1 Jun 24 14:22:42 rln dhclient[2905]: Copyright 2004-2013 Internet Systems Consortium. Jun 24 14:22:42 rln dhclient[2905]: All rights reserved. Jun 24 14:22:42 rln dhclient[2905]: For info, please visit https://www.isc.org/software/dhcp/ Jun 24 14:22:42 rln dhclient[2905]: Jun 24 14:22:42 rln NetworkManager[1046]: <info> (eth0): DHCPv4 state changed nbi -> preinit Jun 24 14:22:42 rln dhclient[2905]: Listening on LPF/eth0/d4:3d:7e:2e:27:60 Jun 24 14:22:42 rln dhclient[2905]: Sending on LPF/eth0/d4:3d:7e:2e:27:60 Jun 24 14:22:42 rln dhclient[2905]: Sending on Socket/fallback Jun 24 14:22:42 rln dhclient[2905]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jun 24 14:22:42 rln dhclient[2905]: DHCPACK from 192.168.1.1 Jun 24 14:22:42 rln dhclient[2905]: bound to 192.168.1.52 -- renewal in 34080 seconds. Jun 24 14:22:42 rln NetworkManager[1046]: <info> (eth0): DHCPv4 state changed preinit -> reboot Jun 24 14:22:42 rln NetworkManager[1046]: <info> address 192.168.1.52 Jun 24 14:22:42 rln NetworkManager[1046]: <info> prefix 24 (255.255.255.0) Jun 24 14:22:42 rln NetworkManager[1046]: <info> gateway 192.168.1.1 Jun 24 14:22:42 rln NetworkManager[1046]: <info> hostname 'rln' Jun 24 14:22:42 rln NetworkManager[1046]: <info> nameserver '89.150.129.22' Jun 24 14:22:42 rln NetworkManager[1046]: <info> nameserver '89.150.129.10' Jun 24 14:22:42 rln NetworkManager[1046]: <info> domain name 'P-2601HNU-F1' Jun 24 14:22:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled... Jun 24 14:22:42 rln NetworkManager[1046]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) started... Jun 24 14:22:43 rln NetworkManager[1046]: <info> (eth0): device state change: ip-config -> secondaries (reason 'none') [70 90 0] Jun 24 14:22:43 rln NetworkManager[1046]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete. Jun 24 14:22:43 rln NetworkManager[1046]: <info> (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0] Jun 24 14:22:43 rln NetworkManager[1046]: <info> Policy set 'System eth0' (eth0) as default for IPv4 routing and DNS. Jun 24 14:22:43 rln NetworkManager[1046]: <info> Writing DNS information to /sbin/resolvconf Jun 24 14:22:43 rln postfix[2990]: warning: inet_protocols: disabling IPv6 name/address support: Address family not supported by protocol Jun 24 14:22:43 rln postfix/master[2999]: warning: inet_protocols: disabling IPv6 name/address support: Address family not supported by protocol Jun 24 14:22:43 rln postfix/postlog[3004]: warning: inet_protocols: disabling IPv6 name/address support: Address family not supported by protocol Jun 24 14:22:43 rln postfix/postsuper[3007]: warning: inet_protocols: disabling IPv6 name/address support: Address family not supported by protocol Jun 24 14:22:43 rln NetworkManager[1046]: <info> Activation (eth0) successful, device activated. Jun 24 14:22:43 rln postfix/postsuper[3011]: warning: inet_protocols: disabling IPv6 name/address support: Address family not supported by protocol Jun 24 14:23:45 rln NetworkManager[1046]: <info> (wlan0): device state change: disconnected -> unavailable (reason 'none') [30 20 0] Jun 24 14:23:45 rln NetworkManager[1046]: <info> (wlan0): deactivating device (reason 'none') [0] Jun 24 14:23:45 rln NetworkManager[1046]: <info> (wlan0): taking down device. Jun 24 14:23:46 rln NetworkManager[1046]: <info> WiFi hardware radio set disabled Jun 24 14:23:46 rln NetworkManager[1046]: <info> WiFi now disabled by radio killswitch Jun 24 14:23:47 rln NetworkManager[1046]: <info> (wlan0): bringing up device. Jun 24 14:23:47 rln NetworkManager[1046]: <info> WiFi hardware radio set enabled Jun 24 14:23:47 rln NetworkManager[1046]: <info> WiFi now enabled by radio killswitch Jun 24 14:23:47 rln NetworkManager[1046]: <info> (wlan0): bringing up device. Jun 24 14:23:48 rln NetworkManager[1046]: <info> (wlan0) supports 4 scan SSIDs Jun 24 14:23:48 rln NetworkManager[1046]: <info> (wlan0): supplicant interface state: starting -> ready Jun 24 14:23:48 rln NetworkManager[1046]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42] Jun 24 14:23:48 rln NetworkManager[1046]: <warn> Trying to remove a non-existant call id. Jun 24 14:23:48 rln NetworkManager[1046]: <info> (wlan0): supplicant interface state: ready -> inactive Jun 24 14:23:48 rln NetworkManager[1046]: <info> (wlan0) supports 4 scan SSIDs
Check the end of /etc/wpa_supplicant.conf and delete any blocks that describe your SSID. Also, please _attach_ /var/log/wpa_supplicant.log
Created attachment 4163 [details] wpa_supplicant.log BEFORE deleting anything
(In reply to René Lagoni Neukirch from comment #15) > Created attachment 4163 [details] > wpa_supplicant.log BEFORE deleting anything Deleted 7 lines ... now then ? Do I try again via the applet ?
(In reply to René Lagoni Neukirch from comment #16) > (In reply to René Lagoni Neukirch from comment #15) > > Created attachment 4163 [details] > > wpa_supplicant.log BEFORE deleting anything > > Deleted 7 lines ... now then ? Do I try again via the applet ? Deleted the 7 lines from /etc/wpa_supplicant.conf (just to make sure :-)
Attachment 4163 mime type: text/x-log => text/plain
Reboot, after that try to connect and after that attach the output of this command: dmesg|tail -n 300
(In reply to Sander Lepik from comment #18) > Reboot, after that try to connect and after that attach the output of this > command: dmesg|tail -n 300 I tried just to start the connection. Entered the SSID, and then entered the PSK. Then both the hidden and 3 (three networks all named SCBD52D8) wre shown, but no connection. I deleted all and tried again - still no connection. The applet states a hidden network and still asks for SSID. Then (KDE) configuration is started and I have to select WPA2/PSK security and then enter the PSK - a new connection is created - thus the pre-configured configuration seems not to be used ??? And the output: [root@rln rln]# dmesg | tail -n 300 [ 7.603686] usb 3-1.1: Product: 802.11n WLAN Adapter [ 7.603688] usb 3-1.1: Manufacturer: Realtek [ 7.603690] usb 3-1.1: SerialNumber: 00e04c000001 [ 7.681782] usb 3-1.4: new high-speed USB device number 4 using ehci-pci [ 7.800646] usb 3-1.4: New USB device found, idVendor=0bda, idProduct=0184 [ 7.800651] usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 7.800654] usb 3-1.4: Product: USB2.0-CRW [ 7.800656] usb 3-1.4: Manufacturer: Generic [ 7.800658] usb 3-1.4: SerialNumber: 20100818841300000 [ 7.881740] usb 3-1.5: new low-speed USB device number 5 using ehci-pci [ 7.998212] usb 3-1.5: New USB device found, idVendor=046d, idProduct=c315 [ 7.998217] usb 3-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 7.998220] usb 3-1.5: Product: Logitech USB Keyboard [ 7.998222] usb 3-1.5: Manufacturer: Logitech [ 8.001685] input: Logitech Logitech USB Keyboard as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.5/3-1.5:1.0/input/input4 [ 8.001768] hid-generic 0003:046D:C315.0003: input,hidraw2: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on usb-0000:00:1a.0-1.5/input0 [ 8.041604] systemd[1]: systemd 195 running in system mode. (+PAM +LIBWRAP +AUDIT -SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ; mageia) [ 8.198225] systemd[1]: Inserted module 'autofs4' [ 8.203183] systemd[1]: Set hostname to <rln>. [ 8.773471] systemd[1]: Starting Replay Read-Ahead Data... [ 8.901447] systemd[1]: Starting Collect Read-Ahead Data... [ 8.906966] systemd-readahead[371]: Bumped block_nr parameter of 8:0 to 20480. This is a temporary hack and should be removed one day. [ 9.071409] systemd[1]: Starting RPC Port Mapper. [ 9.071433] systemd[1]: Reached target RPC Port Mapper. [ 9.071452] systemd[1]: Starting Forward Password Requests to Wall Directory Watch. [ 9.071501] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [ 9.071514] systemd[1]: Starting Login Prompts. [ 9.071530] systemd[1]: Reached target Login Prompts. [ 9.071538] systemd[1]: Starting Remote File Systems. [ 9.071551] systemd[1]: Reached target Remote File Systems. [ 9.071559] systemd[1]: Starting Delayed Shutdown Socket. [ 9.071592] systemd[1]: Listening on Delayed Shutdown Socket. [ 9.071598] systemd[1]: Starting /dev/initctl Compatibility Named Pipe. [ 9.071622] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. [ 9.071638] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point. [ 9.071721] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [ 9.071728] systemd[1]: Starting Encrypted Volumes. [ 9.071742] systemd[1]: Reached target Encrypted Volumes. [ 9.071749] systemd[1]: Expecting device dev-disk-by\x2duuid-503c8b04\x2da82b\x2d4f2f\x2dbb29\x2d774e7301bfda.device... [ 9.071803] systemd[1]: Starting udev Kernel Socket. [ 9.071826] systemd[1]: Listening on udev Kernel Socket. [ 9.071865] systemd[1]: Starting udev Control Socket. [ 9.071890] systemd[1]: Listening on udev Control Socket. [ 9.071898] systemd[1]: Expecting device dev-disk-by\x2duuid-dc95317d\x2d04c0\x2d4695\x2db1c1\x2df6cf16f89fc0.device... [ 9.071921] systemd[1]: Starting Journal Socket. [ 9.071958] systemd[1]: Listening on Journal Socket. [ 9.071976] systemd[1]: Starting Configure read-only root support... [ 9.281349] systemd[1]: Started Import network configuration from initramfs. [ 9.281365] systemd[1]: Mounting Debug File System... [ 9.381329] systemd[1]: Starting udev Kernel Device Manager... [ 9.551294] systemd[1]: Mounting POSIX Message Queue File System... [ 9.731236] systemd[1]: Mounting Huge Pages File System... [ 9.731297] systemd-udevd[375]: starting version 195 [ 9.841202] systemd[1]: Starting Set default kernel console loglevel... [ 10.101179] systemd[1]: Starting Journal Service... [ 10.231184] systemd[1]: Started Journal Service. [ 10.231443] systemd[1]: Starting udev Coldplug all Devices... [ 10.371471] systemd[1]: Started Replay Read-Ahead Data. [ 10.371565] systemd[1]: Started Collect Read-Ahead Data. [ 10.371639] systemd[1]: Started udev Kernel Device Manager. [ 10.421086] systemd[1]: Started Configure read-only root support. [ 10.421213] systemd[1]: Mounted Debug File System. [ 10.421297] systemd[1]: Mounted POSIX Message Queue File System. [ 10.421378] systemd[1]: Mounted Huge Pages File System. [ 10.471075] systemd[1]: Started Set default kernel console loglevel. [ 10.482362] systemd[1]: Starting Load legacy module configuration... [ 10.621102] systemd[1]: Started File System Check on Root Device. [ 10.621133] systemd[1]: Starting Remount Root and Kernel File Systems... [ 10.771609] systemd[1]: Started Set Up Additional Binary Formats. [ 10.788331] systemd[1]: Starting Load Kernel Modules... [ 10.891002] systemd[1]: Starting Setup Virtual Console... [ 11.022955] systemd[1]: Starting Apply Kernel Variables... [ 11.230578] EXT4-fs (sda1): re-mounted. Opts: acl [ 11.310895] systemd[1]: Started Load Kernel Modules. [ 11.370860] systemd[1]: Started Remount Root and Kernel File Systems. [ 11.430848] systemd[1]: Started udev Coldplug all Devices. [ 11.430949] systemd[1]: Starting udev Wait for Complete Device Initialization... [ 11.520849] systemd[1]: Starting Local File Systems (Pre). [ 11.520876] systemd[1]: Reached target Local File Systems (Pre). [ 11.520888] systemd[1]: Mounting /tmp... [ 11.730149] systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting anyway. (To see the over-mounted files, please manually mount the underlying file system to a secondary location.) [ 11.870760] systemd[1]: Starting Load Random Seed... [ 12.050786] systemd[1]: Mounted FUSE Control File System. [ 12.050805] systemd[1]: Mounted Configuration File System. [ 12.064027] ACPI: Requesting acpi_cpufreq [ 12.330669] ACPI: Fan [FAN0] (off) [ 12.330694] ACPI: Fan [FAN1] (off) [ 12.331063] ACPI: Fan [FAN2] (off) [ 12.331100] ACPI: Fan [FAN3] (off) [ 12.331119] ACPI: Fan [FAN4] (off) [ 12.340670] systemd[1]: Started Setup Virtual Console. [ 12.349180] fuse init (API version 7.20) [ 12.380933] thermal LNXTHERM:00: registered as thermal_zone0 [ 12.380935] ACPI: Thermal Zone [TZ00] (28 C) [ 12.381104] thermal LNXTHERM:01: registered as thermal_zone1 [ 12.381105] ACPI: Thermal Zone [TZ01] (30 C) [ 12.400651] systemd[1]: Started Apply Kernel Variables. [ 12.402083] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [ 12.402303] r8169 0000:03:00.0: irq 44 for MSI/MSI-X [ 12.402406] r8169 0000:03:00.0 eth0: RTL8168evl/8111evl at 0xffffc9000061c000, d4:3d:7e:2e:27:60, XID 0c900880 IRQ 44 [ 12.402408] r8169 0000:03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] [ 12.425293] microcode: CPU0 sig=0x306a9, pf=0x2, revision=0x16 [ 12.470631] systemd[1]: Started Load legacy module configuration. [ 12.470751] systemd[1]: Mounted /tmp. [ 12.497772] mei 0000:00:16.0: setting latency timer to 64 [ 12.497824] mei 0000:00:16.0: irq 45 for MSI/MSI-X [ 12.502850] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20121018/utaddress-251) [ 12.502854] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 12.502858] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251) [ 12.502860] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 12.502860] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251) [ 12.502862] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 12.502863] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 12.510048] ACPI Warning: 0x000000000000f000-0x000000000000f01f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20121018/utaddress-251) [ 12.510052] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 12.510632] systemd[1]: Started Load Random Seed. [ 12.518527] microcode: CPU1 sig=0x306a9, pf=0x2, revision=0x16 [ 12.518664] microcode: CPU2 sig=0x306a9, pf=0x2, revision=0x16 [ 12.518807] microcode: CPU3 sig=0x306a9, pf=0x2, revision=0x16 [ 12.518957] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba [ 12.610713] systemd[1]: Mounting FUSE Control File System... [ 12.771386] systemd[1]: Mounted FUSE Control File System. [ 13.106694] iTCO_vendor_support: vendor-support=0 [ 13.107475] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10 [ 13.107498] iTCO_wdt: Found a Panther Point TCO device (Version=2, TCOBASE=0x0460) [ 13.107557] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=1) [ 13.107836] nouveau E[ PGRAPH][0000:01:00.0] ROP0 ch 1 [0x000003fc92] 0x80000000 0x80000001 [ 13.107841] nouveau E[ PGRAPH][0000:01:00.0] ROP1 ch 1 [0x000003fc92] 0x80000000 0x80000001 [ 13.208290] Initializing USB Mass Storage driver... [ 13.208396] scsi6 : usb-storage 3-1.4:1.0 [ 13.208472] usbcore: registered new interface driver usb-storage [ 13.208473] USB Mass Storage support registered. [ 13.429429] cfg80211: Calling CRDA to update world regulatory domain [ 13.430764] cfg80211: World regulatory domain updated: [ 13.430766] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 13.430768] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 13.430769] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 13.430769] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 13.430770] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 13.430771] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 13.664315] systemd[1]: Found device ST2000DM001-9YN164. [ 13.664336] systemd[1]: Starting File System Check on /dev/disk/by-uuid/dc95317d-04c0-4695-b1c1-f6cf16f89fc0... [ 13.870972] rtl8192cu: Chip version 0x10 [ 13.954442] rtl8192cu: MAC address: 80:1f:02:81:88:19 [ 13.954448] rtl8192cu: Board Type 2 [ 13.954694] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1 [ 13.954717] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw.bin [ 13.954750] usbcore: registered new interface driver rtl8192cu [ 13.960957] snd_hda_intel 0000:00:1b.0: irq 46 for MSI/MSI-X [ 14.016139] ieee80211 phy0: Selected rate control algorithm 'rtl_rc' [ 14.016423] rtlwifi: wireless switch is on [ 14.027172] SKU: Nid=0x1d sku_cfg=0x4005c603 [ 14.027174] SKU: port_connectivity=0x1 [ 14.027174] SKU: enable_pcbeep=0x0 [ 14.027175] SKU: check_sum=0x00000005 [ 14.027176] SKU: customization=0x000000c6 [ 14.027176] SKU: external_amp=0x0 [ 14.027177] SKU: platform_type=0x0 [ 14.027178] SKU: swap=0x1 [ 14.027178] SKU: override=0x1 [ 14.027182] autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line [ 14.027183] speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 14.027184] hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) [ 14.027184] mono: mono_out=0x0 [ 14.027185] inputs: [ 14.027186] Front Mic=0x19 [ 14.027187] Rear Mic=0x18 [ 14.027187] Line=0x1a [ 14.029136] realtek: No valid SSID, checking pincfg 0x4005c603 for NID 0x1d [ 14.029137] realtek: Enabling init ASM_ID=0xc603 CODEC_ID=10ec0887 [ 14.034842] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input5 [ 14.034894] input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input6 [ 14.034933] input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7 [ 14.034964] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8 [ 14.034993] input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9 [ 14.035125] hda_intel: Disabling MSI [ 14.035130] hda-intel 0000:01:00.1: Handle VGA-switcheroo audio client [ 14.038496] hda-intel 0000:01:00.1: Enable delay in RIRB handling [ 14.071397] cfg80211: Calling CRDA for country: DK [ 14.072552] cfg80211: Regulatory domain changed to country: DK [ 14.072554] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 14.072555] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 14.072556] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 14.072557] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 14.072558] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm) [ 14.072559] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm) [ 14.120273] systemd[1]: Started File System Check on /dev/disk/by-uuid/dc95317d-04c0-4695-b1c1-f6cf16f89fc0. [ 14.120321] systemd[1]: Mounting /home... [ 14.212732] scsi 6:0:0:0: Direct-Access Generic- Compact Flash 1.00 PQ: 0 ANSI: 0 CCS [ 14.216947] scsi 6:0:0:1: Direct-Access Generic- SM/xD-Picture 1.00 PQ: 0 ANSI: 0 CCS [ 14.222822] scsi 6:0:0:2: Direct-Access Generic- SD/MMC/MS PRO 1.00 PQ: 0 ANSI: 0 CCS [ 14.265255] systemd[1]: Found device ST2000DM001-9YN164. [ 14.265274] systemd[1]: Activating swap /dev/disk/by-uuid/503c8b04-a82b-4f2f-bb29-774e7301bfda... [ 14.267755] sd 6:0:0:0: [sdb] Attached SCSI removable disk [ 14.269755] sd 6:0:0:1: [sdc] Attached SCSI removable disk [ 14.273552] sd 6:0:0:2: [sdd] Attached SCSI removable disk [ 14.531944] Adding 4087272k swap on /dev/sda5. Priority:-1 extents:1 across:4087272k [ 14.532528] systemd[1]: Activated swap /dev/disk/by-uuid/503c8b04-a82b-4f2f-bb29-774e7301bfda. [ 14.532582] systemd[1]: Starting Swap. [ 14.532598] systemd[1]: Reached target Swap. [ 14.892118] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: acl [ 14.892379] systemd[1]: Mounted /home. [ 15.110059] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input10 [ 15.110174] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input11 [ 15.110261] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input12 [ 15.120564] systemd[1]: Starting Sound Card. [ 15.120593] systemd[1]: Reached target Sound Card. [ 15.190041] systemd[1]: Started udev Wait for Complete Device Initialization. [ 15.190114] systemd[1]: Starting Wait for storage scan... [ 15.300044] systemd[1]: Started Show Plymouth Boot Screen. [ 15.300144] systemd[1]: Starting Forward Password Requests to Plymouth Directory Watch. [ 15.300177] systemd[1]: Started Forward Password Requests to Plymouth Directory Watch. [ 15.300187] systemd[1]: Started Dispatch Password Requests to Console Directory Watch. [ 15.579959] systemd[1]: Started Wait for storage scan. [ 15.580043] systemd[1]: Started Initialize storage subsystems (RAID, LVM, etc.). [ 15.580061] systemd[1]: Started Initialize storage subsystems (RAID, LVM, etc.). [ 15.580074] systemd[1]: Starting Local File Systems. [ 15.580089] systemd[1]: Reached target Local File Systems. [ 15.580096] systemd[1]: Starting LSB: Supports the direct execution of binary formats.... [ 15.709926] systemd[1]: Started Mark the need to relabel after reboot. [ 15.709967] systemd[1]: Starting Save boot dmesg content... [ 15.799952] systemd[1]: Started Reconfigure the system on administrator request. [ 15.799980] systemd[1]: Starting Reconfigure the system on administrator request... [ 15.899945] systemd[1]: Started Relabel all filesystems, if necessary. [ 15.899983] systemd[1]: Starting Setup links in /boot for running kernel... [ 16.021495] systemd[1]: Starting Recreate Volatile Files and Directories... [ 16.139950] systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... [ 16.249837] systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage... [ 16.429797] systemd[1]: Started Save boot dmesg content. [ 16.479764] systemd[1]: Started Setup links in /boot for running kernel. [ 16.559745] systemd[1]: Started Recreate Volatile Files and Directories. [ 16.639728] systemd[1]: Started Tell Plymouth To Write Out Runtime Data. [ 16.639776] systemd[1]: Starting System Initialization. [ 16.639792] systemd[1]: Reached target System Initialization. [ 16.639801] systemd[1]: Starting OSS (Open Sound System) Proxy Daemon... [ 16.759706] systemd[1]: Starting Daily Cleanup of Temporary Directories. [ 16.759729] systemd[1]: Started Daily Cleanup of Temporary Directories. [ 16.759741] systemd[1]: Starting Restore Sound Card State... [ 16.849749] systemd[1]: Starting CUPS Printer Service Spool. [ 16.880522] systemd[1]: Started CUPS Printer Service Spool. [ 16.880535] systemd[1]: Starting Avahi mDNS/DNS-SD Stack Activation Socket. [ 16.880582] systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket. [ 16.880589] systemd[1]: Starting CUPS Printing Service Sockets. [ 16.880611] systemd[1]: Listening on CUPS Printing Service Sockets. [ 16.880617] systemd[1]: Starting D-Bus System Message Bus Socket. [ 16.880643] systemd[1]: Listening on D-Bus System Message Bus Socket. [ 16.880652] systemd[1]: Starting Sockets. [ 16.880664] systemd[1]: Reached target Sockets. [ 16.880746] systemd[1]: Mounting Arbitrary Executable File Formats File System... [ 17.009927] systemd[1]: Started OSS (Open Sound System) Proxy Daemon. [ 17.059642] systemd[1]: Started Restore Sound Card State. [ 17.059781] systemd[1]: Mounted Arbitrary Executable File Formats File System. [ 17.109754] systemd-journald[387]: Received SIGUSR1 [ 17.169606] systemd[1]: Started LSB: Supports the direct execution of binary formats.. [ 17.219602] systemd[1]: Started Trigger Flushing of Journal to Persistent Storage. [ 22.431206] nouveau E[ PGRAPH][0000:01:00.0] ROP0 ch 1 [0x000003fc92] 0x80000000 0x80000001 [ 22.431214] nouveau E[ PGRAPH][0000:01:00.0] ROP1 ch 1 [0x000003fc92] 0x80000000 0x80000001 [ 27.761831] IPv6: Loaded, but administratively disabled, reboot required to enable [ 28.748433] microcode: Microcode Update Driver: v2.00 removed. [ 29.290147] systemd-logind[1047]: Watching system buttons on /dev/input/event1 (Power Button) [ 29.290232] systemd-logind[1047]: Watching system buttons on /dev/input/event0 (Power Button) [ 29.309073] rtl8192cu: MAC auto ON okay! [ 29.341818] rtl8192cu: Tx queue select: 0x05 [ 29.712302] NET: Registered protocol family 17 [ 30.367746] ata1.00: configured for UDMA/133 [ 30.367752] ata1: EH complete [ 30.719038] Bluetooth: Core ver 2.16 [ 30.719059] NET: Registered protocol family 31 [ 30.719060] Bluetooth: HCI device and connection manager initialized [ 30.719064] Bluetooth: HCI socket layer initialized [ 30.719066] Bluetooth: L2CAP socket layer initialized [ 30.719069] Bluetooth: SCO socket layer initialized [ 30.721462] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 30.721464] Bluetooth: BNEP filters: protocol multicast [ 30.721467] Bluetooth: BNEP socket layer initialized [ 30.784382] EXT4-fs (sda1): re-mounted. Opts: acl,commit=0 [ 30.788171] EXT4-fs (sda6): re-mounted. Opts: acl,commit=0 [ 30.878647] r8169 0000:03:00.0 eth0: link down [ 62.495056] ip_tables: (C) 2000-2006 Netfilter Core Team [ 62.615631] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 62.681468] Netfilter messages via NETLINK v0.30. [ 62.688558] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 62.738984] NF_TPROXY: Transparent proxy support initialized, version 4.1.0 [ 62.738986] NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd. [ 62.754768] ctnetlink v0.93: registering with nfnetlink. [ 62.793686] ip_set: protocol 6 [ 62.798758] ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully [ 62.827975] xt_time: kernel timezone is +0200 [ 63.088133] Bridge firewalling registered [ 63.201570] u32 classifier [ 63.201572] Actions configured [ 63.299623] netfilter PSD loaded - (c) astaro AG [ 63.300766] IFWLOG: register target [ 65.626943] lp: driver loaded but no devices found [ 65.629118] ppdev: user-space parallel port driver [ 313.200767] rtl8192cu: MAC auto ON okay! [ 313.233636] rtl8192cu: Tx queue select: 0x05 [ 405.256587] rtl8192cu: MAC auto ON okay! [ 405.289329] rtl8192cu: Tx queue select: 0x05 [ 477.125108] r8169 0000:03:00.0 eth0: link up
Thomas, do you have any ideas what else might be wrong? Would the kernel from updates_testing change something or not?
CC: (none) => tmb
yet some additional observations: I removed all I could of interfaces both via the MCC center and via KDE. Then I tried the applet again - it seems that trying to connect involves some network adapter configuration. I noted that only 802.11 b/g were flagged not ..n. The router should accept all 3, though. In the MCC, when I remov thee KDE created connections they are flagged as ethernet connections SCBD52D ... -1 ... -2 etc. This is different from the MCC configuration which configures a Wlan adapter (Realtek 802.11n) but flags it as a DRAM controller when removing it again.
(In reply to Sander Lepik from comment #20) > Thomas, do you have any ideas what else might be wrong? Would the kernel > from updates_testing change something or not? Well, this c o u l d be related to kernel versioning, I think. I had an older platform up and running M2, M3RC with wireless working just fine. I now try a clean install on that - and then I use ONLY the applet. Then I shall report back - Sander, thank you so much for your effort !!!
(In reply to René Lagoni Neukirch from comment #22) > (In reply to Sander Lepik from comment #20) > > Thomas, do you have any ideas what else might be wrong? Would the kernel > > from updates_testing change something or not? > > Well, this c o u l d be related to kernel versioning, I think. > I had an older platform up and running M2, M3RC with wireless working just > fine. > > I now try a clean install on that - and then I use ONLY the applet. > Then I shall report back - Sander, thank you so much for your effort !!! Ah, I forgot: This platform uses an Atheros 5212/13 - will that help ?
I now have the old platform running. I tried the plasma-applet both before and after updating via medias. Again some extra network entries are created flagged in MCC as Ethernet (SCBD52D8) and ... -1). The use of ath5 is flagged, and I se one other network now. But still, alas, no connection obtained to my network. This for what it's worth, as I only see the system as a user ...
Supplemental observation: On BOTH platforma (ie. on Atheros 5212/13 and 8291cu network adapters) the applet flags band til b/g and channel to -1 (MINUS one). On both then signal strength i 0% (ZERO percent) for my network (SCBD52D8).
Observation on /etc/wpa_supplicant.conf et al. If I by hand delete the section/block describing my SSID and try to connect via the plasma-applet, then signal strength is back - close to 100% in fact - otherwise it is 0 (zero). And again I just to be sure re-check that only one wp_supplicant is active. This has been no problem hitherto, though. Only one is running, every time I check. Then, there seems to be some negotiation going on, but only on b/g not n and via channel 0. The router has been locked to channel 10 now - the best one as of signal quality. The BSSID/mac addr. of the router is shown with all zeroes: 00:00:00:00:00:00 even if I hardcode it when entering the KDE configuration via the plasma-applet. Still the plasma-applet asks for a network EVERY time I try to connect, and an Ethernet (SCBD52D8) entry is added in MCC withe extensions ...D8-1) ...D8-2) ...D8-3) etc.. These connections are also seen in the KDE4 system configuration tool (networking) but they are NOT editable/deletable and are flagged never to have been connected. I then use MCC to delte each and every entry. So, as I understand it, the router can now be detected - but, maybe many other, things still go wrong and I cannot connect with wireless.
Created attachment 4170 [details] Error message from KDE. I left the system for a long time, due to a phonecall. When I got back, there were approx. 13 (thirteen) errormessages - pls see attached png.
VERY good news !!! I did a full "reburn" of my older platform with Atheros 5212/13. I updated everything and added the plasma-applet. I deleted the wlan0 entry via MCC. I stopped the wired etho connection, configured the wireless through the plasma applet - and EUREKA ! It nows works as I am using the wireless connection to write this message. I am just totally confused - either some updates did it or the change of network card did it ??? I did NOT wokr a couple of weeks ago though !! Now remain to get my platform with rtl8192cu running - still no success here. And again Sander - thanks for the guidance to this goal.
BACK TO SQUARE ONE ! I really don't get this at all. Today I tried to switch just to ejoy the victory of the "reburned" (old) platform with Atheros 5212/13, which worked the other day. It is now IMPOSSIBLE toget it to connect to the wireless. The configuration of the wireless adapter does not find the proper wireless channel it seems. AND nothing else has changed in my entire setup for the LAN. For my new platform it seems that my router falls back to 802.11 b/g provided just one unit is connected via these freqs. And in turn it seems that the rtl8192cu adapter cannot "downgrade" from 802.11 n to either b or g. BIG SIGH !
Have you tested with another channel on te router side? Is there any device in your network that is able to connect to that router?
Yes, I have various devices connected, eg. a Windoze XP, a Windoze 7 and a wireless HP printer. Also Androids do connect. My new platform with 8192cu won't connect wirelessly whatsoever. I just tried freezing on channel 10 on the router. Now it is possible AGAIN to connect wirelessly via the old platform with Atheros 5212/13. Does this help ? I am confused.
It might be something to do with your router or other devices connected to the router. At my parents home when any other device is connected to the router my dad's laptop won't connect and it's running XP not linux.
Sander, I'm afraid, that you are not quite right, that it is the router that fails. If I reboot the plasma-applet sometimes connects my old Linux/Atheros allright. If I then log out and in again it does not. If I in bothe cases configure yet another connection via the plasma-applet the very same machine connects again.
DEFINATELY the error lies within M3. For the record I have now tried 3 (three) different routers - ZyXel, Netgear and CISCO. The behaviour is CONSTANT across those 3 (which is in a sense comforting), namely, that the Atheros 5212/13 does connect with some help/handson. The 802.11n does NOT - whatsoever - (which is really bad). It always awaits some kind of recognition/acknowledgement after having found a chanel, the AP MAC etc. It seems, that no IP is allocated - I tried of course to set the IP in the config - but no succes either way. I really don't know what to do now or where to look. Any suggestions or help ???
Definitely ... Does someone have some idea on what to do. It's a rather annoying error. For my old platform I can work around by deleting older connections and establish a new one after each boot. This is with the old Atheros 5212/13 and the ath5 driver. For my new platform the Realtek does not connect - it awaits some kind of acknowledgement forever. Pls. advise ...
Helloooooooo, Is this thread abondoned ? As the problemto my opinion is severe - can someone guide to a work around or solution even ????
(In reply to René Lagoni Neukirch from comment #36) > Helloooooooo, > > Is this thread abondoned ? No, but we're all volunteers who work on this project in our free time. I think there are currently almost 3000 open bug reports. > As the problemto my opinion is severe - can someone guide to a work around > or solution even ???? For me it works if I uninstall networkmanager, then setup the connection with drakconnect http://doc.mageia.org/mcc/3/en/content/drakconnect.html and then reboot. I'll cc some more people who might know what else can be tried. For Mageia 4, we hope to have a better solution for the networkproblems https://wiki.mageia.org/en/Feature:NetworkDrakToolsImprovements If you happen to have some free time, please consider spending time on making Mageia a better contribution. Bugsquad, QA team and many other teams could really use your help. https://wiki.mageia.org/en/Contributing Kind regards, Marja
CC: (none) => mageia, marja11, pablo
(In reply to Marja van Waes from comment #37) > > For me it works if I uninstall networkmanager, then setup the connection > with drakconnect http://doc.mageia.org/mcc/3/en/content/drakconnect.html and > then reboot. > Ah, forgot to mention that I enable two options during set up: * Start the connection at boot * Allow access point roaming
Thx again Maja, I've tried your method - unfortunately without success. Do you use a Realtek 8192cu (802.11n) ?? I have several machines, and I can make it work, with some manual intervention after each boot on my machine (x64) with the ath5 driver. All my machines are clean (new) installs of M3 (x64) with all updates. I tried the drakconnect (again-again-again) and it did not connect. Then I tried to run drakconnect from a # prompt. Does the output below help ?? : ------------------------------------------------------------ [root@rln rln]# drakconnect Gtk-Message **: Failed to load module "canberra-gtk-module" at /usr/lib/libDrakX/mygtk2.pm line 20. Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 524. Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 524. Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 524. Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 524. Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 524. Selected interface 'wlan0' OK Kunne ikke oprette værtsnavnsopløser: Den forespurgte handling er ugyldig pÃ¥ grund af redundans [my translation: Could not resolve hostname: The action requested is invalid due to redundancy] run-parts: /etc/sysconfig/network-scripts/hostname.d/avahi exited with return code 1 Interface "wlan0" is already disabled. ioctl[SIOCSIWENCODEEXT]: Invalid argument ioctl[SIOCSIWENCODEEXT]: Invalid argument Selected interface 'wlan0' OK ------------------------------------------------- .... NO CONNECTION via WiFi - sigh ... I have the canberra-gtk 0.30 2.mga3 x86_64 installed, also the common module and 3 (three) lib64's (-gtk0, -gtk3_0 and 0). /René
Addendum - I double checked that there was NO RJ45 cable connected. I then tried to start drakconnect after a reboot (to "clean" the machine) - a little different reaction (see below re ifplugd): -------------------------------------------------------------------- [root@rln rln]# drakconnect Gtk-Message **: Failed to load module "canberra-gtk-module" at /usr/lib/libDrakX/mygtk2.pm line 20. Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 524. Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 524. Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 524. Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 524. Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 524. Selected interface 'wlan0' OK Kunne ikke oprette værtsnavnsopløser: Den forespurgte handling er ugyldig pÃ¥ grund af redundans run-parts: /etc/sysconfig/network-scripts/hostname.d/avahi exited with return code 1 Failed to kill daemon. (Timer expired) Interface "wlan0" is already disabled. ioctl[SIOCSIWENCODEEXT]: Invalid argument ioctl[SIOCSIWENCODEEXT]: Invalid argument Sorry, there is already an instance of ifplugd for wlan0 running. Selected interface 'wlan0' OK -------------------------------------------------------------------- but still no WiFi connection .... /René
(In reply to René Lagoni Neukirch from comment #39) > Thx again Maja, > > I've tried your method - unfortunately without success. > Do you use a Realtek 8192cu (802.11n) ?? > No, I have three other wlan adapters. The one I use at this moment on this system is a Ralink 802.11n Someone from QA team has a Realtek rtl8192se, which is probably more similar to yours. I'll cc him. Btw (sorry for not finding time to read all coments in this bug report), the summary is "Wireless: Unable to connect to a WPA2 network with hidden SSID" Am I correct to understand that you can connect without problems if the SSID is visible? @ Dick According to the QA hardware list, you have a rtl8192se, of which I hope it is similar. Do you maybe have a suggestion?
CC: (none) => dvgevers
(In reply to Marja van Waes from comment #41) > (In reply to René Lagoni Neukirch from comment #39) > > Thx again Maja, > > > > I've tried your method - unfortunately without success. > > Do you use a Realtek 8192cu (802.11n) ?? > > > > No, I have three other wlan adapters. The one I use at this moment on this > system is a Ralink 802.11n > > Someone from QA team has a Realtek rtl8192se, which is probably more similar > to yours. I'll cc him. > > Btw (sorry for not finding time to read all coments in this bug report), the > summary is "Wireless: Unable to connect to a WPA2 network with hidden SSID" > Am I correct to understand that you can connect without problems if the SSID > is visible? *** NO, unfortunately, Atheros 5212/13 and the ath5 driver works either way. The Realtek 8192cu works neither way :-( Maybe some of the problem is, that the WPA2 flag is lost. Sometimes when I look into the non-connecting adapter-config, it says e.g. OpenWEP or "nothing" ... > > @ Dick > According to the QA hardware list, you have a rtl8192se, of which I hope it > is similar. Do you maybe have a suggestion?
(In reply to René Lagoni Neukirch from comment #42) > (In reply to Marja van Waes from comment #41) > > > > Btw (sorry for not finding time to read all coments in this bug report), the > > summary is "Wireless: Unable to connect to a WPA2 network with hidden SSID" > > Am I correct to understand that you can connect without problems if the SSID > > is visible? > > *** NO, unfortunately, Atheros 5212/13 and the ath5 driver works either way. > The Realtek 8192cu works neither way :-( > Can you try with the latest driver from realtec, as described here https://forums.mageia.org/en/viewtopic.php?f=25&t=4242#p31035 ? @ leuhmanu bug 6031 and bug 8754 are related. Is it OK to close this one as a duplicate of the 8754 and set that one to Mageia 3 (MGA2TOO)?
as you want, too complex for me to read from the beginning
(In reply to Marja van Waes from comment #43) > (In reply to René Lagoni Neukirch from comment #42) > > (In reply to Marja van Waes from comment #41) > > > > > > > Btw (sorry for not finding time to read all coments in this bug report), the > > > summary is "Wireless: Unable to connect to a WPA2 network with hidden SSID" > > > Am I correct to understand that you can connect without problems if the SSID > > > is visible? > > > > *** NO, unfortunately, Atheros 5212/13 and the ath5 driver works either way. > > The Realtek 8192cu works neither way :-( > > > > Can you try with the latest driver from realtec, as described here > https://forums.mageia.org/en/viewtopic.php?f=25&t=4242#p31035 ? *** This seems rather complicated - at least for me. I'm not comfortable with manual edit of system related files and configs ... I do hope, that the solution is part of M4 (if not before). > > @ leuhmanu > > bug 6031 and bug 8754 are related. Is it OK to close this one as a duplicate > of the 8754 and set that one to Mageia 3 (MGA2TOO)?
(In reply to René Lagoni Neukirch from comment #42) > (In reply to Marja van Waes from comment #41) > > > > Btw (sorry for not finding time to read all coments in this bug report), the > > summary is "Wireless: Unable to connect to a WPA2 network with hidden SSID" > > Am I correct to understand that you can connect without problems if the SSID > > is visible? > > *** NO, unfortunately, Atheros 5212/13 and the ath5 driver works either way. > The Realtek 8192cu works neither way :-( > OK, since all that is left of this bug report is the 8192cu issue, closing this one as a duplicate of 8754 I hope an easier fix or workaround will be found than the one in the forum thread we talked about *** This bug has been marked as a duplicate of bug 8754 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE
sorry for not responding: was in hospital
(In reply to Dick Gevers from comment #47) > sorry for not responding: was in hospital Ouch! I hope you recovered (or will recover) well.