LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > SUSE / openSUSE
User Name
Password
SUSE / openSUSE This Forum is for the discussion of Suse Linux.

Notices


Reply
  Search this Thread
Old 06-23-2016, 04:40 PM   #1
wagscat123
Member
 
Registered: Jan 2009
Location: Maryland-Pennsylvania border, USA
Distribution: openSUSE 15.2/15.3, Tumbleweed, Kubuntu 18.04/21.04, macOS 10.15, antiX 19, and Linux Mint 19.3
Posts: 860
Blog Entries: 45

Rep: Reputation: 120Reputation: 120
USB Wi-Fi Adapter Won't Activate on Plugin or Start


Hi all,

I'm on Tumbleweed, and for the last month or so my USB Belkin Realtek Wi-Fi adapter won't work on startup or plugin. Before in Tubmeweed, and in Leap and most other popular distros it'll instantly work on plugin or startup, but in this Tumbleweed install it doesn't.

To get it running I have to, after every startup, go into YaST and temporarily switch the Network Manager to wicked, then go back in and set it to NetworkManager.

What can I do so it just works on startup?

Thanks!
 
Old 06-23-2016, 05:56 PM   #2
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,781

Rep: Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139
When you first plug the device in,confirm that the wireless network interface is present
Code:
/sbin/ifconfig
then check its status from NM point of view...
Code:
nmcli g
[/CODE]nmcli d[/CODE]
More questions may follow.
 
Old 06-23-2016, 05:56 PM   #3
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,781

Rep: Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139
Sorry, duplicate posted...<removed>

Last edited by ferrari; 06-23-2016 at 05:57 PM.
 
Old 06-23-2016, 07:25 PM   #4
wagscat123
Member
 
Registered: Jan 2009
Location: Maryland-Pennsylvania border, USA
Distribution: openSUSE 15.2/15.3, Tumbleweed, Kubuntu 18.04/21.04, macOS 10.15, antiX 19, and Linux Mint 19.3
Posts: 860

Original Poster
Blog Entries: 45

Rep: Reputation: 120Reputation: 120
When ran these, I didn't see "wlan1" listed, which is the one that the KDE Network Manager applet connects me to once I do my convoluted trick and then connect. Here's the output:

Code:
linux-rnpk:/home/jared # /sbin/ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:280 (280.0 b)  TX bytes:280 (280.0 b)

p3p2      Link encap:Ethernet  HWaddr D0:67:E5:1C:C6:AA  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wlan0     Link encap:Ethernet  HWaddr 38:59:F9:C4:04:EC  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

linux-rnpk:/home/jared # nmcli g
STATE         CONNECTIVITY  WIFI-HW  WIFI     WWAN-HW  WWAN    
disconnected  none          enabled  enabled  enabled  enabled 
linux-rnpk:/home/jared # nmcli d
DEVICE  TYPE      STATE         CONNECTION 
wlan0   wifi      disconnected  --         
p3p2    ethernet  unavailable   --         
lo      loopback  unmanaged     --         
linux-rnpk:/home/jared #
 
Old 06-23-2016, 09:11 PM   #5
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,781

Rep: Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139
Quote:
When ran these, I didn't see "wlan1" listed, which is the one that the KDE Network Manager applet connects me to once I do my convoluted trick and then connect
That's what I was kind of hoping to see - I wanted a 'snapshot' of the situation when the device is first plugged in, before your switching to wikced and back. So, the wlano0 interface is not present (active) initially? BTW, I wonder if restarting network.service would do the same as your switching trick?
Code:
sudo systemctl restart network
Anyway, for more detail it might be useful to open a terminal and run
Code:
dmesg --follow
or
Code:
sudo journalctl -f
Plug the USB dongle in again, and observe/capture the kernel output resulting.
 
Old 06-24-2016, 08:32 PM   #6
wagscat123
Member
 
Registered: Jan 2009
Location: Maryland-Pennsylvania border, USA
Distribution: openSUSE 15.2/15.3, Tumbleweed, Kubuntu 18.04/21.04, macOS 10.15, antiX 19, and Linux Mint 19.3
Posts: 860

Original Poster
Blog Entries: 45

Rep: Reputation: 120Reputation: 120
Interestingly, the systemctl restart of network services didn't work. I do have, however, the network log of when I first switch (using YaST) to wicked from Network Manager, then back to Network Manager when it starts working. Oddly it lights up after I switch it to wicked (207-209), but doesn't connect (can't ping router or Google) until I switch it back to Network Manager (265 and later).

Code:
[  207.108905] No iBFT detected.
[  207.822260] r8712u 2-1.3:1.0 wlan1: 1 RCR=0x153f00e
[  207.823116] r8712u 2-1.3:1.0 wlan1: 2 RCR=0x553f00e
[  209.130042] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[  265.463473] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  265.480925] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  265.482383] IPv6: ADDRCONF(NETDEV_UP): p3p2: link is not ready
[  265.588344] r8169 0000:03:00.0 p3p2: link down
[  265.588399] IPv6: ADDRCONF(NETDEV_UP): p3p2: link is not ready
[  265.589974] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[  266.894600] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[  266.958863] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  266.969484] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[  266.976041] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[  276.970446] r8712u 2-1.3:1.0 wlan1: r8712u: wpa_set_encryption: crypt.alg = WEP
[  277.309420] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
I can post what it looks like when I initially plug it in, if it's still relevant after this. I rebooted and forgot to save it
 
Old 06-24-2016, 10:09 PM   #7
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,781

Rep: Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139
Yes, post back with the kernel output occurring when device is first plugged in..
 
Old 06-24-2016, 10:16 PM   #8
wagscat123
Member
 
Registered: Jan 2009
Location: Maryland-Pennsylvania border, USA
Distribution: openSUSE 15.2/15.3, Tumbleweed, Kubuntu 18.04/21.04, macOS 10.15, antiX 19, and Linux Mint 19.3
Posts: 860

Original Poster
Blog Entries: 45

Rep: Reputation: 120Reputation: 120
Got it again here

Code:
[   77.589770] usb 2-1.3: new high-speed USB device number 6 using ehci-pci
[   77.684817] usb 2-1.3: New USB device found, idVendor=050d, idProduct=845a
[   77.684824] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   77.684826] usb 2-1.3: Product: Belkin USB Wireless Adaptor
[   77.684829] usb 2-1.3: Manufacturer: Manufacturer Realtek 
[   77.684831] usb 2-1.3: SerialNumber: 00e04c000001
[   77.685504] r8712u: register rtl8712_netdev_ops to netdev_ops
[   77.685510] usb 2-1.3: r8712u: USB_SPEED_HIGH with 4 endpoints
[   77.686149] usb 2-1.3: r8712u: Boot from EFUSE: Autoload OK
[   78.091129] usb 2-1.3: r8712u: CustomerID = 0x0000
[   78.091136] usb 2-1.3: r8712u: MAC Address from efuse = 94:10:3e:b0:9c:dd
[   78.091139] usb 2-1.3: r8712u: Loading firmware from "rtlwifi/rtl8712u.bin"
Thanks!
 
Old 06-25-2016, 12:35 AM   #9
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,781

Rep: Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139
Nothing reported a little after that?

For example, I get
Code:
[   95.994222] usb 3-1: new high-speed USB device number 3 using xhci_hcd
[   96.160075] usb 3-1: New USB device found, idVendor=0bda, idProduct=8176
[   96.160082] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   96.160086] usb 3-1: Product: 802.11n WLAN Adapter
[   96.160089] usb 3-1: Manufacturer: Realtek
[   96.160091] usb 3-1: SerialNumber: 00e04c000001
[   97.338580] rtl8192cu: Chip version 0x10
[   97.370081] rtl8192cu: MAC address: a0:f3:c1:22:27:e5
[   97.370089] rtl8192cu: Board Type 0
[   97.370157] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
[   97.370193] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[   97.370391] usbcore: registered new interface driver rtl8192cu
[   97.377929] ieee80211 phy1: Selected rate control algorithm 'rtl_rc'
[   97.378562] rtlwifi: wireless switch is on
[   97.399236] rtl8192cu: MAC auto ON okay!
[   97.411602] rtl8192cu: Tx queue select: 0x05
[   97.770357] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
and /sbin/ifconfig reports the new network device node
Code:
wlp0s20u1 Link encap:Ethernet  HWaddr A0:F3:C1:22:27:E5  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
 
Old 06-25-2016, 10:02 AM   #10
wagscat123
Member
 
Registered: Jan 2009
Location: Maryland-Pennsylvania border, USA
Distribution: openSUSE 15.2/15.3, Tumbleweed, Kubuntu 18.04/21.04, macOS 10.15, antiX 19, and Linux Mint 19.3
Posts: 860

Original Poster
Blog Entries: 45

Rep: Reputation: 120Reputation: 120
I tried it again and got this:

Code:
[  136.697454] usb 2-1.3: new high-speed USB device number 5 using ehci-pci
[  136.792552] usb 2-1.3: New USB device found, idVendor=050d, idProduct=845a
[  136.792558] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  136.792561] usb 2-1.3: Product: Belkin USB Wireless Adaptor
[  136.792563] usb 2-1.3: Manufacturer: Manufacturer Realtek 
[  136.792565] usb 2-1.3: SerialNumber: 00e04c000001
[  137.870392] r8712u: module is from the staging directory, the quality is unknown, you have been warned.
[  137.871791] r8712u: register rtl8712_netdev_ops to netdev_ops
[  137.871796] usb 2-1.3: r8712u: USB_SPEED_HIGH with 4 endpoints
[  137.872315] usb 2-1.3: r8712u: Boot from EFUSE: Autoload OK
[  138.261923] usb 2-1.3: r8712u: CustomerID = 0x0000
[  138.261929] usb 2-1.3: r8712u: MAC Address from efuse = 94:10:3e:b0:9c:dd
[  138.261932] usb 2-1.3: r8712u: Loading firmware from "rtlwifi/rtl8712u.bin"
I then ran ifconfig and got

Code:
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:1140 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1140 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:93032 (90.8 Kb)  TX bytes:93032 (90.8 Kb)

p3p2      Link encap:Ethernet  HWaddr D0:67:E5:1C:C6:AA  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wlan0     Link encap:Ethernet  HWaddr 38:59:F9:C4:04:EC  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

linux-rnpk:/home/jared #
 
Old 06-25-2016, 04:52 PM   #11
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,781

Rep: Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139
Okay, so the wlan0 network interface is present as expected. So it should be possible to get NetworkManager to connect. The output from NM can be monitored using
Code:
sudo journalctl -fu NetworkManager
Then attempt to connect manually and observe the output. Ctrl+C to terminate Copy/paste the output here if there are any issues.
 
Old 06-27-2016, 01:36 PM   #12
wagscat123
Member
 
Registered: Jan 2009
Location: Maryland-Pennsylvania border, USA
Distribution: openSUSE 15.2/15.3, Tumbleweed, Kubuntu 18.04/21.04, macOS 10.15, antiX 19, and Linux Mint 19.3
Posts: 860

Original Poster
Blog Entries: 45

Rep: Reputation: 120Reputation: 120
I should have specified that I have a non-functional (due to completely hardware related issues) Wi-Fi card that shows up as wlan0, and the USB dongle I want is wlan0. I'll still try that though and get back about it
 
Old 06-29-2016, 08:29 PM   #13
wagscat123
Member
 
Registered: Jan 2009
Location: Maryland-Pennsylvania border, USA
Distribution: openSUSE 15.2/15.3, Tumbleweed, Kubuntu 18.04/21.04, macOS 10.15, antiX 19, and Linux Mint 19.3
Posts: 860

Original Poster
Blog Entries: 45

Rep: Reputation: 120Reputation: 120
Sorry about the slow reply - I thought my last post went up.

Here's the output of that:

Code:
Jun 29 21:23:54 linux-rnpk systemd[1]: Starting Network Manager...
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  NetworkManager (version 1.0.12) is starting...
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  Read config: /etc/NetworkManager/NetworkManager.conf
Jun 29 21:23:54 linux-rnpk systemd[1]: Started Network Manager.
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  Loaded settings plugin ifcfg-suse: (C) 2008 Novell, Inc.  To report bugs please use the NetworkManager mailing list. (/usr/lib64/NetworkManager/libnm-settings-plugin-ifcfg-suse.so)
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  Loaded settings plugin keyfile: (c) 2007 - 2015 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  keyfile: new connection /etc/NetworkManager/system-connections/Sharp403-909f2ddf-eaae-455c-9c0a-7a649eb3d4ff (909f2ddf-eaae-455c-9c0a-7a649eb3d4ff,"Sharp403")
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  keyfile: new connection /etc/NetworkManager/system-connections/Sharp403-da7d929f-a9fc-4290-a083-f2abee7d5b6e (da7d929f-a9fc-4290-a083-f2abee7d5b6e,"Sharp403")
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  keyfile: new connection /etc/NetworkManager/system-connections/Sharp403 (b6b4b208-066e-414e-84b6-498f157f4226,"Sharp403")
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  VPN: loaded org.freedesktop.NetworkManager.vpnc
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  VPN: loaded org.freedesktop.NetworkManager.pptp
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  VPN: loaded org.freedesktop.NetworkManager.openvpn
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  monitoring kernel firmware directory '/lib/firmware'.
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.3/0000:02:00.0/ieee80211/phy0/rfkill0) (driver ath9k)
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  WiFi hardware radio set enabled
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  WWAN hardware radio set enabled
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  Loaded device plugin: NMVxlanFactory (internal)
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  Loaded device plugin: NMVlanFactory (internal)
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  Loaded device plugin: NMVethFactory (internal)
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  Loaded device plugin: NMTunFactory (internal)
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  Loaded device plugin: NMMacvlanFactory (internal)
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  Loaded device plugin: NMInfinibandFactory (internal)
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  Loaded device plugin: NMGreFactory (internal)
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  Loaded device plugin: NMEthernetFactory (internal)
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  Loaded device plugin: NMBridgeFactory (internal)
Jun 29 21:23:54 linux-rnpk NetworkManager[2787]: <info>  Loaded device plugin: NMBondFactory (internal)
Jun 29 21:23:55 linux-rnpk NetworkManager[2787]: <info>  Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so)
Jun 29 21:23:55 linux-rnpk NetworkManager[2787]: <info>  Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/libnm-device-plugin-wifi.so)
Jun 29 21:23:55 linux-rnpk NetworkManager[2787]: <info>  Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/libnm-device-plugin-team.so)
Jun 29 21:23:55 linux-rnpk NetworkManager[2787]: <info>  Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/libnm-device-plugin-wwan.so)
Jun 29 21:23:55 linux-rnpk NetworkManager[2787]: <info>  Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/libnm-device-plugin-adsl.so)
Jun 29 21:23:55 linux-rnpk NetworkManager[2787]: <info>  WiFi enabled by radio killswitch; enabled by state file
Jun 29 21:23:55 linux-rnpk NetworkManager[2787]: <info>  WWAN enabled by radio killswitch; enabled by state file
Jun 29 21:23:55 linux-rnpk NetworkManager[2787]: <info>  WiMAX enabled by radio killswitch; enabled by state file
Jun 29 21:23:55 linux-rnpk NetworkManager[2787]: <info>  Networking is enabled by state file
Jun 29 21:23:55 linux-rnpk NetworkManager[2787]: <info>  (wlan0): using nl80211 for WiFi device control
Jun 29 21:23:55 linux-rnpk NetworkManager[2787]: <info>  (wlan0): driver supports Access Point (AP) mode
Jun 29 21:23:55 linux-rnpk NetworkManager[2787]: <info>  (wlan0): new 802.11 WiFi device (carrier: UNKNOWN, driver: 'ath9k', ifindex: 3)
Jun 29 21:23:55 linux-rnpk NetworkManager[2787]: <info>  (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jun 29 21:23:55 linux-rnpk NetworkManager[2787]: <info>  (p3p2): new Ethernet device (carrier: OFF, driver: 'r8169', ifindex: 2)
Jun 29 21:23:55 linux-rnpk NetworkManager[2787]: <info>  (p3p2): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jun 29 21:23:55 linux-rnpk NetworkManager[2787]: <info>  keyfile: add connection in-memory (6f26e3b0-7fad-465d-967f-9423ef81902e,"Wired connection 1")
Jun 29 21:23:55 linux-rnpk NetworkManager[2787]: <info>  (p3p2): created default wired connection 'Wired connection 1'
Jun 29 21:23:55 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): driver does not support SSID scans (scan_capa 0x00).
Jun 29 21:23:55 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): using WEXT for WiFi device control
Jun 29 21:23:55 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): new 802.11 WiFi device (carrier: UNKNOWN, driver: 'r8712u', ifindex: 4)
Jun 29 21:23:55 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (lo): link connected
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (lo): new Generic device (carrier: ON, driver: 'unknown', ifindex: 1)
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  ModemManager available in the bus
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  wpa_supplicant running
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): supplicant interface state: init -> starting
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (wlan0): supplicant interface state: init -> starting
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (wlan0) supports 4 scan SSIDs
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3) supports 1 scan SSIDs
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (wlan0): supplicant interface state: starting -> ready
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): supplicant interface state: starting -> ready
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  Auto-activating connection 'Sharp403'.
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): Activation: starting connection 'Sharp403' (da7d929f-a9fc-4290-a083-f2abee7d5b6e)
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  NetworkManager state is now CONNECTING
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): device state change: prepare -> config (reason 'none') [40 50 0]
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): Activation: (wifi) access point 'Sharp403' has security, but secrets are required.
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): device state change: config -> need-auth (reason 'none') [50 60 0]
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <warn>  (wlp0s29u1u3): No agents were available for this request.
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  NetworkManager state is now DISCONNECTED
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <warn>  (wlp0s29u1u3): Activation: failed for connection 'Sharp403'
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): device state change: failed -> disconnected (reason 'none') [120 30 0]
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  Auto-activating connection 'Sharp403'.
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): Activation: starting connection 'Sharp403' (da7d929f-a9fc-4290-a083-f2abee7d5b6e)
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  NetworkManager state is now CONNECTING
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): device state change: prepare -> config (reason 'none') [40 50 0]
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): Activation: (wifi) access point 'Sharp403' has security, but secrets are required.
Jun 29 21:23:56 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): device state change: config -> need-auth (reason 'none') [50 60 0]
Jun 29 21:23:57 linux-rnpk NetworkManager[2787]: <info>  (wlan0): supplicant interface state: ready -> inactive
Jun 29 21:24:01 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Jun 29 21:24:01 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): device state change: prepare -> config (reason 'none') [40 50 0]
Jun 29 21:24:01 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): Activation: (wifi) connection 'Sharp403' has security, and secrets exist.  No new secrets needed.
Jun 29 21:24:01 linux-rnpk NetworkManager[2787]: <info>  Config: added 'ssid' value 'Sharp403'
Jun 29 21:24:01 linux-rnpk NetworkManager[2787]: <info>  Config: added 'scan_ssid' value '1'
Jun 29 21:24:01 linux-rnpk NetworkManager[2787]: <info>  Config: added 'key_mgmt' value 'NONE'
Jun 29 21:24:01 linux-rnpk NetworkManager[2787]: <info>  Config: added 'wep_key0' value '<omitted>'
Jun 29 21:24:01 linux-rnpk NetworkManager[2787]: <info>  Config: added 'wep_tx_keyidx' value '0'
Jun 29 21:24:01 linux-rnpk NetworkManager[2787]: <info>  Config: set interface ap_scan to 1
Jun 29 21:24:06 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): supplicant interface state: ready -> associating
Jun 29 21:24:07 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): supplicant interface state: associating -> completed
Jun 29 21:24:07 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Sharp403'.
Jun 29 21:24:07 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): device state change: config -> ip-config (reason 'none') [50 70 0]
Jun 29 21:24:07 linux-rnpk NetworkManager[2787]: <info>  Activation (wlp0s29u1u3) Beginning DHCPv4 transaction (timeout in 45 seconds)
Jun 29 21:24:07 linux-rnpk NetworkManager[2787]: <info>  dhclient started with pid 3036
Jun 29 21:24:12 linux-rnpk NetworkManager[2787]: <info>    address 192.168.1.34
Jun 29 21:24:12 linux-rnpk NetworkManager[2787]: <info>    plen 24 (255.255.255.0)
Jun 29 21:24:12 linux-rnpk NetworkManager[2787]: <info>    gateway 192.168.1.1
Jun 29 21:24:12 linux-rnpk NetworkManager[2787]: <info>    server identifier 192.168.1.1
Jun 29 21:24:12 linux-rnpk NetworkManager[2787]: <info>    lease time 86400
Jun 29 21:24:12 linux-rnpk NetworkManager[2787]: <info>    nameserver '192.168.1.1'
Jun 29 21:24:12 linux-rnpk NetworkManager[2787]: <info>    domain name 'westell.com'
Jun 29 21:24:12 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): DHCPv4 state changed unknown -> bound
Jun 29 21:24:12 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Jun 29 21:24:12 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Jun 29 21:24:12 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): device state change: secondaries -> activated (reason 'none') [90 100 0]
Jun 29 21:24:12 linux-rnpk NetworkManager[2787]: <info>  NetworkManager state is now CONNECTED_LOCAL
Jun 29 21:24:12 linux-rnpk NetworkManager[2787]: <info>  NetworkManager state is now CONNECTED_SITE
Jun 29 21:24:12 linux-rnpk NetworkManager[2787]: <info>  Policy set 'Sharp403' (wlp0s29u1u3) as default for IPv4 routing and DNS.
Jun 29 21:24:12 linux-rnpk NetworkManager[2787]: <13>Jun 29 21:24:12 dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
Jun 29 21:24:12 linux-rnpk NetworkManager[2787]: <13>Jun 29 21:24:12 dns-resolver: You can find my version in /etc/resolv.conf.netconfig
Jun 29 21:24:12 linux-rnpk NetworkManager[2787]: ATTENTION: You have modified /etc/resolv.conf.  Leaving it untouched...
Jun 29 21:24:12 linux-rnpk NetworkManager[2787]: You can find my version in /etc/resolv.conf.netconfig ...
Jun 29 21:24:12 linux-rnpk NetworkManager[2787]: <info>  (wlp0s29u1u3): Activation: successful, device activated.
Jun 29 21:24:12 linux-rnpk NetworkManager[2787]: <info>  startup complete
Jun 29 21:24:12 linux-rnpk NetworkManager[2787]: <info>  NetworkManager state is now CONNECTED_GLOBAL
At 9:23 I switched to wicked, and at 9:24 I switched to Network Manager
 
Old 06-29-2016, 11:13 PM   #14
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,781

Rep: Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139
Okay, from that I see the device is actually wlp0s29u1u3 (with wlan0 being your on-board device). It does connect, but it's not clear to me why NM doesn't handle it as soon as it becomes available. I'm wondering if perhaps you just need to recreate the NM connection and restrict it to the particular wireless device (wlp0s29u1u3) when configuring.
 
Old 06-29-2016, 11:21 PM   #15
ferrari
LQ Guru
 
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 5,781

Rep: Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139Reputation: 1139
Perhaps it just needs more time to initialise when first plugged in? Or does it only become available after switching to wicked first? A bug report may be required if so.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] mouse on PS/2 to USB adapter won't initialize nathank0 Linux - Hardware 3 08-17-2010 01:23 PM
Receiving wlan0 device not found when trying to activate usb adapter with ndiswrapper rtoney5 Linux - Laptop and Netbook 3 03-30-2008 03:37 PM
linksys USB Network Adapter, Fedora Core 1 - How do I activate it? edu2 Linux - Networking 3 07-06-2004 08:14 PM
ethernet adapter won't start at boot time darkpark Linux - Networking 1 01-06-2004 11:27 AM
ethernet adapter won't start at bootup. darkpark Linux - Hardware 1 01-06-2004 11:01 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > SUSE / openSUSE

All times are GMT -5. The time now is 08:49 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration