no Wifi

Trmpt8va · July 15, 2019, 12:30am

I had wifi with 15.0 then with 15.1 no wifi. Wifi is still working with Windows.
During install wifi networks are discovered but not able to connect.

linux-71oy:/home/home # ping 8.8.8.8
connect: Network is unreachable

please advise on what commands I should run to help me discover the error.

Thanks
Les

dcurtisfra · July 15, 2019, 3:03pm

Which graphical user interface are you using? – KDE? GNOME? Something else?
Which network manager are you using? – NetworkManager? Wicked? Something else?
Are you certain that, the Wireless Interface hardware has the correct Linux Kernel module installed?
Is the Wireless Interface activated?
With Leap 15.0, and therefore Leap 15.1 also, SuSEfirewall2 has been replaced by “firewalld” – are you certain that, the Firewall settings for the Wireless Interface are relaxed enough to allow access to the Wireless Network?
Are you certain that, you have the correct key value for the Wireless Network’s SSID?
Are you using a Password Wallet to store the Key values needed to access any given Wireless Network SSID?

Trmpt8va · July 15, 2019, 10:43pm

GNOME
Wicked and Network manager…no luck. default is Wicked
Yes. I set it up and the name and PW are used for other connectors and all is well.
No Wallet is used.

Now with 3. How can I tell what kernel module I need?
4. I can not say for sure?
5. I am not sure

Please advise on what to use to check these settings.

Thanks so much,
Les

dcurtisfra · July 16, 2019, 10:55am

@Trmpt8va:

If GNOME with a WLAN device conforming to the WiFi standard then, consider using Network Manager and the GNOME Keyring to store the WiFi/WLAN Network Key needed to access each SSID you need to use. The Leap 15.1 documentation for GNOME is here: <https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.nm.html#sec.nm.configure> and here: <https://doc.opensuse.org/documentation/leap/gnomeuser/html/book.gnomeuser/cha.gnomeuser.use.html#sec.gnomeuser.use.connections>. The GNOME documentation for Keyring is here: <https://doc.opensuse.org/documentation/leap/gnomeuser/html/book.gnomeuser/cha.gnome.crypto.html#cha.gnome.crypto.prefs.keyrings>.

I’m inspecting the equivalent KDE Plasma code dealing with Network Manager and WiFi/WLAN Network Key values (AKA secrets) and, my current conclusion – which hasn’t changed the view I had before – is that, not using a Password Wallet such as the GNOME Keyring or the KDE Plasma KWallet is not a good idea – it may work but, the Key values are stored in plain text in a system file, which isn’t a good thing, and, the code dealing with this situation can be viewed as being “very simple and not at all friendly” …

Bottom line – at least from my point of view:

If you wish to have a simple, reliable, easy to use, access to WLAN SSIDs, use a Password Wallet – the supporting code is complete and, it offers an easy, understandable, Graphical User Interface.

dcurtisfra · July 16, 2019, 12:15pm

With the user “root”, the command “lspci” will list the devices on the PCI bus – one of them should be the WLAN (WiFi standard) device.
You can also use, with the user “root”, the command “hwinfo --short” for a complete list of the devices and “hwinfo --wlan” for detailed information about the WLAN/WiFi devices on your system.

With a normal user, you can perform a quick check on the network interfaces with “ip link show”.

There should be should be an entry for the wireless device – usually “wlan0”.

You can also use “cat /proc/net/wireless” and “iw dev” to gather information about the interface.
You can also inspect the devices listed in “/sys/class/net/” for the one which has a sub-directory named “wireless”.

Then, with the user “root” you can search “journalctl --this-boot” for the device name – you should find entries which indicate which Kernel module being used for the device.
The command “lsmod” will confirm that, that module is in fact installed into the Kernel.

With that information you can then inspect the openSUSE Hardware information for details about your wireless device: <https://en.opensuse.org/HCL:Network_(Wireless)>.

<https://en.opensuse.org/Portal:Hardware> – currently the external links aren’t very helpful …

You may need to ensure that, a firmware package for the WLAN/WiFi device has been installed on your system.

Trmpt8va · July 16, 2019, 5:34pm

Thank you everyone for your time.

Kernel Settings/
PCI ID Setup
Nothing is listed?
When I try to add from list the Qualcom network adapter
There are two empty boxes,
Driver and SysFS Directory

Lspci
00:00.0 Host bridge: Intel Corporation Device 5914 (rev 08)
00:02.0 VGA compatible controller: Intel Corporation Device 5917 (rev 07)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
00:15.2 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #2 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Device 9d4e (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce MX130] (rev a2)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01)
03:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a808

hwinfo --short
network:
wlan0 Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
network interface:
lo Loopback network interface
wlan0 WLAN network interface

ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 98:22:ef:d5:e2:bd brd ff:ff:ff:ff:ff:ff

journalctl --this-boot
– Logs begin at Tue 2019-07-16 08:00:05 PDT, end at Tue 2019-07-16 08:05:36 PDT. –
Jul 16 08:00:05 linux-71oy kernel: microcode: microcode updated early to revision 0x9e, date = 2018-10-18
Jul 16 08:00:05 linux-71oy kernel: Linux version 4.12.14-lp151.26-default (geeko@buildhost) (gcc version 7.4.0 (SUSE Linux) ) #1 SMP Fri May 3 05:18:47 UTC 2019 (0e0777>
Jul 16 08:00:05 linux-71oy kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.12.14-lp151.26-default root=UUID=15eaef8f-3c3d-4c22-8c6d-a0f3b41c9da6 splash=silent resume=/>
Jul 16 08:00:05 linux-71oy kernel: x86/fpu: Supporting XSAVE feature 0x001: ‘x87 floating point registers’
Jul 16 08:00:05 linux-71oy kernel: x86/fpu: Supporting XSAVE feature 0x002: ‘SSE registers’
Jul 16 08:00:05 linux-71oy kernel: x86/fpu: Supporting XSAVE feature 0x004: ‘AVX registers’
Jul 16 08:00:05 linux-71oy kernel: x86/fpu: Supporting XSAVE feature 0x008: ‘MPX bounds registers’
Jul 16 08:00:05 linux-71oy kernel: x86/fpu: Supporting XSAVE feature 0x010: ‘MPX CSR’
Jul 16 08:00:05 linux-71oy kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Jul 16 08:00:05 linux-71oy kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
Jul 16 08:00:05 linux-71oy kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
Jul 16 08:00:05 linux-71oy kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using ‘compacted’ format.
Jul 16 08:00:05 linux-71oy kernel: e820: BIOS-provided physical RAM map:
Jul 16 08:00:05 linux-71oy kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
Jul 16 08:00:05 linux-71oy kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
Jul 16 08:00:05 linux-71oy kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable
Jul 16 08:00:05 linux-71oy kernel: BIOS-e820: [mem 0x000000000009e000-0x00000000000fffff] reserved
Jul 16 08:00:05 linux-71oy kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000060a3afff] usable
Jul 16 08:00:05 linux-71oy kernel: BIOS-e820: [mem 0x0000000060a3b000-0x0000000060a3bfff] ACPI NVS
Jul 16 08:00:05 linux-71oy kernel: BIOS-e820: [mem 0x0000000060a3c000-0x0000000060a3cfff] reserved
Jul 16 08:00:05 linux-71oy kernel: BIOS-e820: [mem 0x0000000060a3d000-0x00000000628b2fff] usable
Jul 16 08:00:05 linux-71oy kernel: BIOS-e820: [mem 0x00000000628b3000-0x00000000631b2fff] reserved
Jul 16 08:00:05 linux-71oy kernel: BIOS-e820: [mem 0x00000000631b3000-0x00000000793c8fff] usable
Jul 16 08:00:05 linux-71oy kernel: BIOS-e820: [mem 0x00000000793c9000-0x0000000079f58fff] reserved
Jul 16 08:00:05 linux-71oy kernel: BIOS-e820: [mem 0x0000000079f59000-0x000000007af58fff] ACPI NVS
Jul 16 08:00:05 linux-71oy kernel: BIOS-e820: [mem 0x000000007af59000-0x000000007affefff] ACPI data
Jul 16 08:00:05 linux-71oy kernel: BIOS-e820: [mem 0x000000007afff000-0x000000007affffff] usable
Jul 16 08:00:05 linux-71oy kernel: BIOS-e820: [mem 0x000000007b000000-0x000000007fffffff] reserved
Jul 16 08:00:05 linux-71oy kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
lines 1-30

Thanks

john_hudson · July 16, 2019, 10:48pm

Notwithstanding the Leap 15.1 installation summary saying that it will install Network Manager, I have twice found wicked installed instead. Going to YaST Network services, selecting Network Manager (and deleting /etc/resolv.conf for good measure) and rebooting has solved the problem.

Trmpt8va · July 17, 2019, 1:15am

“Going to YaST Network services, selecting Network Manager (and deleting /etc/resolv.conf for good measure) and rebooting has solved the problem.:”

This did not work.

Thank you

dcurtisfra · July 18, 2019, 11:53am

Aha!!! You have a Qualcomm Atheros QCA6174 WLAN/WiFi device!!!
Let’s take the Leap 15.1 case:


> l /lib/firmware/ath10k/QCA6174/
total 16
drwxr-xr-x  4 root root 4096 Mar 12 13:12 ./
drwxr-xr-x 10 root root 4096 Mar 12 13:12 ../
drwxr-xr-x  2 root root 4096 Jul  2 18:38 hw2.1/
drwxr-xr-x  2 root root 4096 Jul  2 18:38 hw3.0/
 >

So, yes, Leap 15.1 has the firmware for Qualcomm Atheros QCA6174 WLAN/WiFi devices …
But, which firmware is being loaded to your device? – “hw2.1” or “hw3.0” ?

“Which firmware is being used?” can only be answered by searching the systemd Journal for “wlan0
” entries and, from there, to the driver which should be loaded as a Kernel module … - You can check which driver is being used for your WLAN device as follows:


# lspci -nnkv -s **03:00.0**

At the bottom of the list output by “lspci” you should find:


        Kernel driver in use: …
        Kernel modules: …

I suspect that the driver should be “ath10k” which you can check with “lsmod” and also for entries in the systemd Journal, which should then point to which firmware has been loaded for your WLAN device …

dcurtisfra · July 19, 2019, 7:54pm

@Trmpt8va:

Just a thought:

I can also provoke the following by entering the following CLI command with a “normal” user “nmcli radio wifi off
”:


 > ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 20:1a:06:2e:c5:c2 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state **DOWN** mode DEFAULT group default qlen 1000
    link/ether a6:36:1e:6c:5b:ec brd ff:ff:ff:ff:ff:ff
 >

The following CLI commands give more detail:


 > nmcli general status 
STATE            CONNECTIVITY  WIFI-HW    WIFI         WWAN-HW    WWAN        
disconnected     none          enabled    disabled     enabled    disabled 
 > 
 > **nmcli radio wifi on**
 > 
 > nmcli general status 
STATE      CONNECTIVITY  WIFI-HW  WIFI     WWAN-HW  WWAN     
connected  full          enabled  enabled  enabled  disabled 
 >

dcurtisfra · July 20, 2019, 5:36pm

@Trmpt8va:

Yet another thought: please check “rfkill” …


 # rfkill 
ID TYPE      DEVICE                 SOFT      HARD
 0 wlan      ideapad_wlan      unblocked unblocked
 1 bluetooth ideapad_bluetooth unblocked unblocked
 2 wlan      phy0              unblocked unblocked
 3 bluetooth hci0                blocked unblocked
 # systemctl list-unit-files | grep -i 'kill'
systemd-rfkill.service                                                 static   
systemd-rfkill.socket                                                  static   
 # systemctl status systemd-rfkill.service  systemd-rfkill.socket
● systemd-rfkill.service - Load/Save RF Kill Switch Status
   Loaded: loaded (/usr/lib/systemd/system/systemd-rfkill.service; static; vendor preset: disabled)
   Active: inactive (dead) since Sat 2019-07-20 17:06:53 CEST; 19min ago
     Docs: man:systemd-rfkill.service(8)
  Process: 1815 ExecStart=/usr/lib/systemd/systemd-rfkill (code=exited, status=0/SUCCESS)
 Main PID: 1815 (code=exited, status=0/SUCCESS)

Jul 20 17:06:48 eck005 systemd[1]: Starting Load/Save RF Kill Switch Status...
Jul 20 17:06:48 eck005 systemd[1]: Started Load/Save RF Kill Switch Status.

● systemd-rfkill.socket - Load/Save RF Kill Switch Status /dev/rfkill Watch
   Loaded: loaded (/usr/lib/systemd/system/systemd-rfkill.socket; static; vendor preset: disabled)
   Active: active (listening) since Sat 2019-07-20 17:06:37 CEST; 19min ago
     Docs: man:systemd-rfkill.socket(8)
   Listen: /dev/rfkill (Special)

Jul 20 17:06:37 eck005 systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
 #

You may have to use “rfkill unblock wlan” to get your WLAN/WiFi device up and running …