NetworkManager without wlan

[guennov]

Problem: wlan can’t be activated in the NetworkManager icon of the task bar, the wlan checkbox is grey and untouchable. LAN is working fine.

Maybe there is a hint to a configuration issue in /etc/NetworkManager/NetworkManager.conf, because manually changing the content to “enabled=true” in the section for wireless doesn’t have any effect and has disappeared after reboot, whether or not I fire SuSEconfig. Hardware information doesn’t show any extraordinary content.

OS SLED11 SP4
Some output of some commands and some content of some files:

$ /sbin/lspci -nnk |grep -A3 Network
07:00.0 Network controller [0280]: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01)
Subsystem: Hewlett-Packard Company Device [103c:1461]
Kernel driver in use: ath9k
Kernel modules: ath9k

$ dmesg
…
[ 10.105745] ath9k 0000:07:00.0: PCI INT A → GSI 23 (level, low) → IRQ 23
[ 10.105938] ath9k 0000:07:00.0: setting latency timer to 64
[ 10.155391] ath: EEPROM regdomain: 0x60
[ 10.155395] ath: EEPROM indicates we should expect a direct regpair map
[ 10.155401] ath: Country alpha2 being used: 00
[ 10.155404] ath: Regpair used: 0x60
[ 10.198696] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci0000:00/0000
:00:01.1/sound/card0/input10
[ 10.199217] HDA Intel 0000:00:14.2: PCI INT A → GSI 16 (level, low) → IRQ 1
6
[ 10.199340] ALSA hda_intel.c:2952 Using LPIB position fix
[ 10.223893] ieee80211 phy0: Selected rate control algorithm ‘minstrel_ht’
[ 10.224463] Registered led device: ath9k-phy0
[ 10.224471] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xf8420000, irq=23
…

$ grep NETWORKMANAGER /etc/sysconfig/network/config
NETWORKMANAGER=yes

$ cat /etc/NetworkManager/NetworkManager.conf
[wireless]
enabled=false

[malcolmlewis]

Hi
It maybe softblocked, have you checked the BIOS to ensure it’s enabled? Or does the system have a wireless hardware switch/Fn key combo?

The SLE 11 version should work;
http://download.opensuse.org/repositories/hardware/SLE_11_SP3/x86_64/rfkill-0.5-13.1.x86_64.rpm

Then as root user run to verify;

rfkill list

[guennov]

Hi, you’re right, it’s softblocked

I successfully installed rfkill from the i586 repository and got this reply

0: hp-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: yes
1: hp-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: yes
2: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no

The led (function key) indicates that wlan should be working. Perhaps I made a configuration fault?

[malcolmlewis]

On Mon 28 Dec 2015 10:14:01 PM CST, guennov wrote:

Hi, you’re right, it’s softblocked

I successfully installed rfkill from the i586 repository and got this
reply

0: hp-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: yes
1: hp-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: yes
2: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no

The led (function key) indicates that wlan should be working. Perhaps I
made a configuration fault?

Hi
So what model HP, do you see any output from the following command?

lsmod |grep wmi

Hardblock means the Fn (Function key) + a key with the wireless icon on
it needs to be pressed a few times to cycle through bluetooth and
wireless enable/disable. Press the key combination and the run the
rfkill list command to see if any output changes.

Also try unblocking with;

rfkill unblock 0
rfkill unblock 1
rfkill unblock 2
rfkill unblock 3

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 | GNOME 3.10.1 | 3.12.51-52.31-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

[guennov]

Hi

[QUOTE]
So what model HP, do you see any output from the following command?[/QUOTE]

HP 635

lsmod |grep wmi

hp_wmi                 13652  0 
sparse_keymap          13658  1 hp_wmi
rfkill                 20926  4 cfg80211,bluetooth,hp_wmi
wmi                    18645  1 hp_wmi

[QUOTE]Hardblock means the Fn (Function key) + a key with the wireless icon on
it needs to be pressed a few times to cycle through bluetooth and
wireless enable/disable. Press the key combination and the run the
rfkill list command to see if any output changes.[/QUOTE]

The output doesn’t change. By the way, the led colour never changes, it always shows white. An extract from the hp manual

(4) Wireless light
● White: An integrated wireless device, such as a WLAN device and/or a Bluetooth device, is on.
● Amber: All wireless devices are off.

A contradiction?

Also try unblocking with;

rfkill unblock 0
rfkill unblock 1
rfkill unblock 2
rfkill unblock 3

After unblocking the response to “rfkill list” is

0: hp-wifi: Wireless LAN
	Soft blocked: yes
	Hard blocked: yes
1: hp-bluetooth: Bluetooth
	Soft blocked: yes
	Hard blocked: yes
2: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
3: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

Right-clicking on the NetworkManager icon shows that wireless still is unavailable and may not be activated.

[malcolmlewis]

On Tue 29 Dec 2015 10:14:01 AM CST, guennov wrote:

Hi
[color=blue]

So what model HP, do you see any output from the following command?[/color]

HP 635

Code:

lsmod |grep wmi

---

Code:

hp_wmi 13652 0
sparse_keymap 13658 1 hp_wmi
rfkill 20926 4 cfg80211,bluetooth,hp_wmi
wmi 18645 1 hp_wmi

---

[color=blue]

Hardblock means the Fn (Function key) + a key with the wireless icon
on it needs to be pressed a few times to cycle through bluetooth and
wireless enable/disable. Press the key combination and the run the
rfkill list command to see if any output changes.[/color]

The output doesn’t change. By the way, the led colour never changes, it
always shows white. An extract from the hp manual
[color=blue]

(4) Wireless light
● White: An integrated wireless device, such as a WLAN device
and/or a Bluetooth device, is on.
● Amber: All wireless devices are off.
[/color]

A contradiction?
[color=blue]

Also try unblocking with;[color=green]

[/color][/color]
Code:
--------------------[color=blue][color=green]
[/color]
rfkill unblock 0
rfkill unblock 1
rfkill unblock 2
rfkill unblock 3
[/color]
--------------------[color=blue][color=green]
[/color]
[/color]

After unblocking the response to “rfkill list” is

Code:

0: hp-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: yes
1: hp-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: yes
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

---

Right-clicking on the NetworkManager icon shows that wireless still is
unavailable and may not be activated.

Hi
So did the system originally come with SLED, or was it running windows?

HP have some special drivers for both wireless and bluetooth, not sure
if available for that model and SLE 12, you would need to contact HP
Support.

If you reboot and press F10 to go to the BIOS and disable both the
bluetooth and wireless save/exit and restart the system and let it boot
to SLED, is the light now amber, and what is the output from rfkill?

Then restart the computer, press F10 again and re-enable the wireless
and bluetooth and save/exit and let the computer start up, does it all
change?

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 | GNOME 3.10.1 | 3.12.51-52.31-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

[guennov]

Hi

sorry about the delay.

[QUOTE]
So did the system originally come with SLED, or was it running windows?[/QUOTE]

SLED11

[QUOTE]
If you reboot and press F10 to go to the BIOS and disable both the
bluetooth and wireless save/exit and restart the system and let it boot
to SLED, is the light now amber, and what is the output from rfkill?

Then restart the computer, press F10 again and re-enable the wireless
and bluetooth and save/exit and let the computer start up, does it all
change?[/QUOTE]

The BIOS main menue doesn’t allow to select the items for WLAN or Bluetooth and change their set-up. HP diagnostic log contains no errors.

[QUOTE]HP have some special drivers for both wireless and bluetooth, not sure
if available for that model and SLE 12, you would need to contact HP
Support.[/QUOTE]

I’m working with SLE11 SP4.

Today I tried to manually start wlan0, because I hoped to get more information what is going wrong. Therefore in YaST I changed network configuration from NetworkManager method to ifup, then rebooted.

hpc:~ # iwconfig wlan0 wlan0 IEEE 802.11bgn ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=off Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off

After reboot the reply was the same. I tried “ifstatus” and “ifup”:

[CODE]hpc:~ # ifstatus wlan0
wlan0 device: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
DHCP4 client NOT running
DHCP6 client (dhclient6) is running
. . . but is still waiting for data
wlan0 is down

hpc:~ # ifup wlan0
wlan0 device: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
wlan0 starting wpa_supplicant
Could not set interface wlan0 flags: Unknown error 132
Could not set interface ‘wlan0’ UP
Failed to initialize driver interface
ELOOP: remaining socket: sock=4 eloop_data=0x80f1970 user_data=0x80f1690 handler=0x80b7860
DHCP6 client is already running on wlan0
RTNETLINK answers: Unknown error 132
Starting DHCP4 client on wlan0. .
wlan0 DHCP4 client NOT running
wlan0 DHCP6 continues in background
RTNETLINK answers: Unknown error 132
Cannot enable interface wlan0.
interface wlan0 is not up[/CODE]

To check if there might be a driver problem I ran “wpa_supplicant -h”

Here are some lines of the reply

wpa_supplicant v0.7.1 Copyright (c) 2003-2010, Jouni Malinen <j@w1.fi> and contributors ... drivers: wext = Linux wireless extensions (generic) nl80211 = Linux nl80211/cfg80211 hostap = Host AP driver (Intersil Prism2/2.5/3) atmel = ATMEL AT76C5XXx (USB, PCMCIA) ndiswrapper = Linux ndiswrapper (deprecated; use wext) wired = Wired Ethernet driver ralink = Ralink Wireless Client driver options:

Shouldn’t there be a driver “ath9k” or should “wext” do the job? By the way, a configuration file “/etc/wpa_supplicant.conf” does not exist.

Thanks!

[malcolmlewis]

On Tue 05 Jan 2016 09:44:01 PM CST, guennov wrote:

Hi

sorry about the delay.
[color=blue]

So did the system originally come with SLED, or was it running
windows?[/color]

SLED11
[color=blue]

If you reboot and press F10 to go to the BIOS and disable both the
bluetooth and wireless save/exit and restart the system and let it
boot to SLED, is the light now amber, and what is the output from
rfkill?

Then restart the computer, press F10 again and re-enable the wireless
and bluetooth and save/exit and let the computer start up, does it all
change?[/color]

The BIOS main menue doesn’t allow to select the items for WLAN or
Bluetooth and change their set-up. HP diagnostic log contains no errors.

[color=blue]

HP have some special drivers for both wireless and bluetooth, not sure
if available for that model and SLE 12, you would need to contact HP
Support.[/color]

I’m working with SLE11 SP4.

Today I tried to manually start wlan0, because I hoped to get more
information what is going wrong. Therefore in YaST I changed network
configuration from NetworkManager method to ifup, then rebooted.

Code:

hpc:~ # iwconfig wlan0
wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=off
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off

After reboot the reply was the same. I tried “ifstatus” and “ifup”:

Code:

hpc:~ # ifstatus wlan0
wlan0 device: Qualcomm Atheros AR9285 Wireless Network Adapter
(PCI-Express) (rev 01) DHCP4 client NOT running
DHCP6 client (dhclient6) is running
. . . but is still waiting for data
wlan0 is down

hpc:~ # ifup wlan0
wlan0 device: Qualcomm Atheros AR9285 Wireless Network Adapter
(PCI-Express) (rev 01) wlan0 starting wpa_supplicant
Could not set interface wlan0 flags: Unknown error 132
Could not set interface ‘wlan0’ UP
Failed to initialize driver interface
ELOOP: remaining socket: sock=4 eloop_data=0x80f1970
user_data=0x80f1690 handler=0x80b7860 DHCP6 client is already running
on wlan0 RTNETLINK answers: Unknown error 132
Starting DHCP4 client on wlan0. .
wlan0 DHCP4 client NOT running
wlan0 DHCP6 continues in background
RTNETLINK answers: Unknown error 132
Cannot enable interface wlan0.
interface wlan0 is not up

To check if there might be a driver problem I ran “wpa_supplicant -h”

Here are some lines of the reply

Code:

wpa_supplicant v0.7.1
Copyright (c) 2003-2010, Jouni Malinen j@w1.fi and contributors
…
drivers:
wext = Linux wireless extensions (generic)
nl80211 = Linux nl80211/cfg80211
hostap = Host AP driver (Intersil Prism2/2.5/3)
atmel = ATMEL AT76C5XXx (USB, PCMCIA)
ndiswrapper = Linux ndiswrapper (deprecated; use wext)
wired = Wired Ethernet driver
ralink = Ralink Wireless Client driver
options:

Shouldn’t there be a driver “ath9k” or should “wext” do the job? By the
way, a configuration file “/etc/wpa_supplicant.conf” does not exist.

Thanks!

Hi
You should have some HP repositories then?

zypper lr -d

So your on a ipv6 network then?

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.2|3.12.51-60.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

[guennov]

Hi

[QUOTE]
You should have some HP repositories then?

zypper lr -d [/QUOTE]

No, none. Some time ago I had to install SLE from scratch and remove all repository connections.

So your on a ipv6 network then?

No. Boot messages show that DHCP4+DHCP6 client is started.

Setting up (remotefs) network interfaces: wlan0 device: Qualcomm Atheros AR9285 Wireless Network Adap wlan0 starting wpa_supplicant Could not set interface wlan0 flags: Unknown error 132 Could not set interface 'wlan0' UP Failed to initialize driver interface ELOOP: remaining socket: sock=4 eloop_data=0x80f1970 user_data=0x80f1690 handler=0x80b7860 RTNETLINK answers: Unknown error 132 wlan0 Starting DHCP4+DHCP6 client. . . . . . . . . . . . wlan0 DHCP4 client NOT running wlan0 DHCP6 continues in background RTNETLINK answers: Unknown error 132 Cannot enable interface wlan0. interface wlan0 is not up waiting Setting up service (remotefs) network . . . . . . . . . . done

[guennov]

Additional data from “modinfo ath9k”

filename: /lib/modules/3.0.101-68-pae/weak-updates/updates/drivers/net/wireless/ath/ath9k/ath9k.ko version: backported from Linux (v3.13-rc8-0-g7e22e91) using backports v3.13-rc8-1-0-gae71bd3 license: Dual BSD/GPL description: Support for Atheros 802.11n wireless LAN cards. author: Atheros Communications srcversion: 59B307FC5B392FD979BF9F4 alias: pci:v0000168Cd00000036sv*sd*bc*sc*i* alias: pci:v0000168Cd00000036sv0000185Fsd00003027bc*sc*i* alias: pci:v0000168Cd00000036sv00001B9Asd00002810bc*sc*i* alias: pci:v0000168Cd00000036sv0000144Fsd00007202bc*sc*i* alias: pci:v0000168Cd00000036sv00001A3Bsd00002130bc*sc*i* alias: pci:v0000168Cd00000036sv000011ADsd00000612bc*sc*i* alias: pci:v0000168Cd00000036sv000011ADsd00000652bc*sc*i* alias: pci:v0000168Cd00000036sv000011ADsd00000642bc*sc*i* alias: pci:v0000168Cd00000036sv0000168Csd0000302Cbc*sc*i* alias: pci:v0000168Cd00000036sv0000168Csd00003027bc*sc*i* alias: pci:v0000168Cd00000036sv0000144Dsd0000411Ebc*sc*i* alias: pci:v0000168Cd00000036sv0000144Dsd0000411Dbc*sc*i* alias: pci:v0000168Cd00000036sv0000144Dsd0000411Cbc*sc*i* alias: pci:v0000168Cd00000036sv0000144Dsd0000411Bbc*sc*i* alias: pci:v0000168Cd00000036sv0000144Dsd0000411Abc*sc*i* alias: pci:v0000168Cd00000036sv00001028sd0000020Ebc*sc*i* alias: pci:v0000168Cd00000036sv0000103Csd0000217Fbc*sc*i* alias: pci:v0000168Cd00000036sv0000103Csd000018E3bc*sc*i* alias: pci:v0000168Cd00000036sv000017AAsd00003026bc*sc*i* alias: pci:v0000168Cd00000036sv00001A3Bsd0000213Abc*sc*i* alias: pci:v0000168Cd00000036sv000011ADsd00000662bc*sc*i* alias: pci:v0000168Cd00000036sv000011ADsd00000672bc*sc*i* alias: pci:v0000168Cd00000036sv000011ADsd00000622bc*sc*i* alias: pci:v0000168Cd00000036sv0000185Fsd00003028bc*sc*i* alias: pci:v0000168Cd00000036sv0000105Bsd0000E069bc*sc*i* alias: pci:v0000168Cd00000036sv0000168Csd0000302Bbc*sc*i* alias: pci:v0000168Cd00000036sv0000168Csd00003026bc*sc*i* alias: pci:v0000168Cd00000036sv0000168Csd00003025bc*sc*i* alias: pci:v0000168Cd00000036sv00001B9Asd00002812bc*sc*i* alias: pci:v0000168Cd00000036sv00001B9Asd00002811bc*sc*i* alias: pci:v0000168Cd00000036sv000011ADsd00006671bc*sc*i* alias: pci:v0000168Cd00000036sv000011ADsd00000632bc*sc*i* alias: pci:v0000168Cd00000036sv0000185Fsd0000A119bc*sc*i* alias: pci:v0000168Cd00000036sv0000105Bsd0000E068bc*sc*i* alias: pci:v0000168Cd00000036sv00001A3Bsd00002176bc*sc*i* alias: pci:v0000168Cd00000036sv0000168Csd00003028bc*sc*i* alias: pci:v0000168Cd00000037sv*sd*bc*sc*i* alias: pci:v0000168Cd00000034sv*sd*bc*sc*i* alias: pci:v0000168Cd00000034sv000010CFsd00001783bc*sc*i* alias: pci:v0000168Cd00000034sv000014CDsd00000064bc*sc*i* alias: pci:v0000168Cd00000034sv000014CDsd00000063bc*sc*i* alias: pci:v0000168Cd00000034sv0000103Csd00001864bc*sc*i* alias: pci:v0000168Cd00000034sv000011ADsd00006641bc*sc*i* alias: pci:v0000168Cd00000034sv000011ADsd00006631bc*sc*i* alias: pci:v0000168Cd00000034sv00001043sd0000850Ebc*sc*i* alias: pci:v0000168Cd00000034sv00001A3Bsd00002110bc*sc*i* alias: pci:v0000168Cd00000034sv00001969sd00000091bc*sc*i* alias: pci:v0000168Cd00000034sv000017AAsd00003214bc*sc*i* alias: pci:v0000168Cd00000034sv0000168Csd00003117bc*sc*i* alias: pci:v0000168Cd00000034sv000011ADsd00006661bc*sc*i* alias: pci:v0000168Cd00000034sv00001A3Bsd00002116bc*sc*i* alias: pci:v0000168Cd00000033sv*sd*bc*sc*i* alias: pci:v0000168Cd00000032sv*sd*bc*sc*i* alias: pci:v0000168Cd00000032sv00001043sd0000850Dbc*sc*i* alias: pci:v0000168Cd00000032sv00001B9Asd00001C01bc*sc*i* alias: pci:v0000168Cd00000032sv00001B9Asd00001C00bc*sc*i* alias: pci:v0000168Cd00000032sv00001A3Bsd00001F95bc*sc*i* alias: pci:v0000168Cd00000032sv00001A3Bsd00001195bc*sc*i* alias: pci:v0000168Cd00000032sv00001A3Bsd00001F86bc*sc*i* alias: pci:v0000168Cd00000032sv00001A3Bsd00001186bc*sc*i* alias: pci:v0000168Cd00000032sv00001B9Asd00002001bc*sc*i* alias: pci:v0000168Cd00000032sv00001B9Asd00002000bc*sc*i* alias: pci:v0000168Cd00000032sv0000144Fsd00007197bc*sc*i* alias: pci:v0000168Cd00000032sv0000105Bsd0000E04Fbc*sc*i* alias: pci:v0000168Cd00000032sv0000105Bsd0000E04Ebc*sc*i* alias: pci:v0000168Cd00000032sv000011ADsd00006628bc*sc*i* alias: pci:v0000168Cd00000032sv000011ADsd00006627bc*sc*i* alias: pci:v0000168Cd00000032sv00001C56sd00004001bc*sc*i* alias: pci:v0000168Cd00000032sv00001A3Bsd00002100bc*sc*i* alias: pci:v0000168Cd00000032sv00001A3Bsd00002C97bc*sc*i* alias: pci:v0000168Cd00000032sv000017AAsd00003219bc*sc*i* alias: pci:v0000168Cd00000032sv000017AAsd00003218bc*sc*i* alias: pci:v0000168Cd00000032sv0000144Dsd0000C708bc*sc*i* alias: pci:v0000168Cd00000032sv0000144Dsd0000C680bc*sc*i* alias: pci:v0000168Cd00000032sv0000144Dsd0000C706bc*sc*i* alias: pci:v0000168Cd00000032sv0000144Dsd0000410Fbc*sc*i* alias: pci:v0000168Cd00000032sv0000144Dsd0000410Ebc*sc*i* alias: pci:v0000168Cd00000032sv0000144Dsd0000410Dbc*sc*i* alias: pci:v0000168Cd00000032sv0000144Dsd00004106bc*sc*i* alias: pci:v0000168Cd00000032sv0000144Dsd00004105bc*sc*i* alias: pci:v0000168Cd00000032sv0000185Fsd00003027bc*sc*i* alias: pci:v0000168Cd00000032sv0000185Fsd00003119bc*sc*i* alias: pci:v0000168Cd00000032sv0000168Csd00003122bc*sc*i* alias: pci:v0000168Cd00000032sv0000168Csd00003119bc*sc*i* alias: pci:v0000168Cd00000032sv0000105Bsd0000E075bc*sc*i* alias: pci:v0000168Cd00000032sv00001A3Bsd00002152bc*sc*i* alias: pci:v0000168Cd00000032sv00001A3Bsd0000126Abc*sc*i* alias: pci:v0000168Cd00000032sv00001A3Bsd00002126bc*sc*i* alias: pci:v0000168Cd00000032sv00001A3Bsd00001237bc*sc*i* alias: pci:v0000168Cd00000032sv00001A3Bsd00002086bc*sc*i* alias: pci:v0000168Cd00000030sv*sd*bc*sc*i* alias: pci:v0000168Cd0000002Esv*sd*bc*sc*i* alias: pci:v0000168Cd0000002Dsv*sd*bc*sc*i* alias: pci:v0000168Cd0000002Csv*sd*bc*sc*i* alias: pci:v0000168Cd0000002Bsv*sd*bc*sc*i* alias: pci:v0000168Cd0000002Bsv00001A3Bsd00002C37bc*sc*i* alias: pci:v0000168Cd0000002Asv000010CFsd00001536bc*sc*i* alias: pci:v0000168Cd0000002Asv000010CFsd0000147Dbc*sc*i* alias: pci:v0000168Cd0000002Asv000010CFsd0000147Cbc*sc*i* alias: pci:v0000168Cd0000002Asv0000185Fsd0000309Dbc*sc*i* alias: pci:v0000168Cd0000002Asv00001A32sd00000306bc*sc*i* alias: pci:v0000168Cd0000002Asv000011ADsd00006642bc*sc*i* alias: pci:v0000168Cd0000002Asv000011ADsd00006632bc*sc*i* alias: pci:v0000168Cd0000002Asv0000105Bsd0000E01Fbc*sc*i* alias: pci:v0000168Cd0000002Asv00001A3Bsd00001C71bc*sc*i* alias: pci:v0000168Cd0000002Asv*sd*bc*sc*i* alias: pci:v0000168Cd00000029sv*sd*bc*sc*i* alias: pci:v0000168Cd00000027sv*sd*bc*sc*i* alias: pci:v0000168Cd00000024sv*sd*bc*sc*i* alias: pci:v0000168Cd00000023sv*sd*bc*sc*i* depends: mac80211,ath9k_hw,ath9k_common,compat,ath,cfg80211 supported: external vermagic: 3.0.101-63-pae SMP mod_unload modversions 686 signer: SUSE Linux Enterprise Secure Boot Signkey sig_key: 3F:B0:77:B6:CE:BC:6F:F2:52:2E:1C:14:8C:57:C7:77:C7:88:E3:E7 sig_hashalgo: sha256 parm: debug:Debugging mask (uint) parm: nohwcrypt:Disable hardware encryption (int) parm: blink:Enable LED blink on activity (int) parm: btcoex_enable:Enable wifi-BT coexistence (int) parm: bt_ant_diversity:Enable WLAN/BT RX antenna diversity (int)

[malcolmlewis]

On Tue 05 Jan 2016 10:44:02 PM CST, guennov wrote:

Hi[color=blue]

You should have some HP repositories then?[color=green]

[/color][/color]
Code:
--------------------[color=blue][color=green]
[/color]
zypper lr -d
[/color]
--------------------[color=blue][color=green]
[/color][/color]

No, none. Some time ago I had to install SLE from scratch and remove all
repository connections.
[color=blue]

So your on a ipv6 network then?[/color]

No. Boot messages show that DHCP4+DHCP6 client is started.

Code:

Setting up (remotefs) network interfaces:
wlan0 device: Qualcomm Atheros AR9285 Wireless Network Adap
wlan0 starting wpa_supplicant
Could not set interface wlan0 flags: Unknown error 132
Could not set interface ‘wlan0’ UP
Failed to initialize driver interface
ELOOP: remaining socket: sock=4 eloop_data=0x80f1970
user_data=0x80f1690 handler=0x80b7860 RTNETLINK answers: Unknown error
132 wlan0 Starting DHCP4+DHCP6 client. . . . . . . . . . . .
wlan0 DHCP4 client NOT running
wlan0 DHCP6 continues in background
RTNETLINK answers: Unknown error 132
Cannot enable interface wlan0.
interface wlan0 is not
up
waiting Setting up service (remotefs)
network . . . . . . . . . .
done --------------------

Hi
I meant your using ipv6 not ipv4

So if you use the HP code, it should add those repositories onto your
system for bluetooth and wireless…

AFAIK these are needed to get it out from being softblocked as rfkill
showed.

You might want to post over in the HP support forum and someone there
may be able to provide a link to the HP drivers.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.2|3.12.51-60.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

[guennov]

Hi

[QUOTE]So if you use the HP code, it should add those repositories onto your
system for bluetooth and wireless…

AFAIK these are needed to get it out from being softblocked as rfkill
showed.[/QUOTE]

So the output of “modinfo ath9k” doesn’t mean that the driver is maintained by SuSE?

The status of the module looks like this

$ lsmod | sort | grep "ath" Module Size Used by ath 24377 3 ath9k,ath9k_common,ath9k_hw ath3k 13108 0 ath9k 99768 0 ath9k_common 13320 1 ath9k ath9k_hw 436007 2 ath9k,ath9k_common cfg80211 226039 3 ath9k,mac80211,ath compat 28330 8 bnep,ath9k,mac80211,btusb,bluetooth,ath9k_common,ath9k_hw,cfg80211 mac80211 587771 1 ath9k usbcore 200058 7 btusb,uvcvideo,ath3k,usbhid,ohci_hcd,ehci_hcd

Thank you.

[malcolmlewis]

On Wed 06 Jan 2016 11:24:01 AM CST, guennov wrote:

Hi[color=blue]

So if you use the HP code, it should add those repositories onto your
system for bluetooth and wireless…

AFAIK these are needed to get it out from being softblocked as rfkill
showed.[/color]

So the output of “modinfo ath9k” doesn’t mean that the driver is
maintained by SuSE?

The status of the module looks like this

Code:

$ lsmod | sort | grep “ath”
Module Size Used by
ath 24377 3 ath9k,ath9k_common,ath9k_hw
ath3k 13108 0
ath9k 99768 0
ath9k_common 13320 1 ath9k
ath9k_hw 436007 2 ath9k,ath9k_common
cfg80211 226039 3 ath9k,mac80211,ath
compat 28330 8
bnep,ath9k,mac80211,btusb,bluetooth,ath9k_common,ath9k_hw,cfg80211
mac80211 587771 1 ath9k usbcore 200058 7
btusb,uvcvideo,ath3k,usbhid,ohci_hcd,ehci_hcd --------------------

Thank you.

Hi
AFAIK can tell kernel modules are working fine, until you can remove
the softblock neither wireless or bluetooth will work (rfkill).

You still didn’t confirm whether your connection is ipv6 or ipv4?

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.2|3.12.51-60.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

[guennov]

Hi

[QUOTE]AFAIK can tell kernel modules are working fine, until you can remove
the softblock neither wireless or bluetooth will work (rfkill).

You still didn’t confirm whether your connection is ipv6 or ipv4?
[/QUOTE]

Oops, didn’t I? It is ipv4.
In YaST → Network Configuration → global options the option ipv6 is activated and, I suppose, does no harm. Deactivating it and rebooting led to a problem with the text console (strg-alt-f1), which started very slowly because of waiting for DHCP4 client. Now ipv6 is activated and NetworkManager is responsible.

[CODE]hpc:~ # netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

hpc:~ # ip route show
default via 192.168.2.1 dev eth0 proto static
127.0.0.0/8 dev lo scope link
192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.110 metric 1

hpc:~ # ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 2c:76:8a:e5:a2:e8 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 74:de:2b:72:52:c5 brd ff:ff:ff:ff:ff:ff[/CODE]

[malcolmlewis]

On Wed 06 Jan 2016 03:34:01 PM CST, guennov wrote:

Hi
[color=blue]

AFAIK can tell kernel modules are working fine, until you can remove
the softblock neither wireless or bluetooth will work (rfkill).

You still didn’t confirm whether your connection is ipv6 or ipv4?
[/color]

Oops, didn’t I? It is ipv4.
In YaST → Network Configuration → global options the option ipv6 is
activated and, I suppose, does no harm. Deactivating it and rebooting
led to a problem with the text console (strg-alt-f1), which started very
slowly because of waiting for DHCP4 client. Now ipv6 is activated and
NetworkManager is responsible.

Code:

hpc:~ # netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window
irtt Iface 0.0.0.0 192.168.2.1 0.0.0.0 UG 0
0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0
U 0 0 0 lo 192.168.2.0 0.0.0.0
255.255.255.0 U 0 0 0 eth0
hpc:~ # ip route show
default via 192.168.2.1 dev eth0 proto static
127.0.0.0/8 dev lo scope link
192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.110
metric 1
hpc:~ # ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP qlen 1000 link/ether 2c:76:8a:e5:a2:e8 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen
1000 link/ether 74:de:2b:72:52:c5 brd ff:ff:ff:ff:ff:ff

Hi
So you have the network cable in, if you unplug and run the same
commands?

I do suggest you pop over to the HP forums, there maybe some info on
unblocking those softblocks…

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.2|3.12.51-60.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

[guennov]

Hi

[QUOTE]So you have the network cable in, if you unplug and run the same
commands?[/QUOTE]

There is no surprise

[CODE]hpc:~ # ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
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 pfifo_fast state DOWN qlen 1000
link/ether 2c:76:8a:e5:a2:e8 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 74:de:2b:72:52:c5 brd ff:ff:ff:ff:ff:ff

hpc:~ # ip route show
127.0.0.0/8 dev lo scope link

hpc:~ # netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
[/CODE]

Let’s have a last try before switching to HP forums.
Some (edited) lines from /var/log/NetworkManager. Line 23 might be interesting. I still don’t understand why wireless is disabled by radio killswitch. Is there any configuration file which might be responsible?

Jan 6 15:26:05 hpc NetworkManager: <info> starting... Jan 6 15:26:05 hpc NetworkManager: <info> Trying to start the modem-manager... Jan 6 15:26:05 hpc NetworkManager: <WARN> nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add(): Sucess Jan 6 15:26:05 hpc NetworkManager: <info> Found radio killswitch /org/freedesktop/Hal/devices/platform_hp_wmi_rfkill_hp_wifi_wlan Jan 6 15:26:05 hpc NetworkManager: <info> Found radio killswitch /org/freedesktop/Hal/devices/pci_168c_2b_rfkill_phy0_wlan Jan 6 15:26:05 hpc NetworkManager: <info> Found new Ethernet device 'eth0' (driver: 'r8169'). Jan 6 15:26:05 hpc NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_2c_76_8a_e5_a2_e8 Jan 6 15:26:05 hpc NetworkManager: <info> (wlan0): driver supports SSID scans (scan_capa 0x01). Jan 6 15:26:05 hpc NetworkManager: <info> Found new 802.11 WiFi device 'wlan0' (driver: 'ath9k'). Jan 6 15:26:05 hpc NetworkManager: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_74_de_2b_72_52_c5 Jan 6 15:26:05 hpc NetworkManager: <info> Trying to start the supplicant... Jan 6 15:26:05 hpc NetworkManager: <info> modem-manager is now available Jan 6 15:26:05 hpc NetworkManager: <info> Trying to start the system settings daemon... Jan 6 15:26:05 hpc NetworkManager: <info> (eth0): device state change: 1 -> 2 (reason 2) Jan 6 15:26:05 hpc NetworkManager: <info> (eth0): bringing up device. Jan 6 15:26:05 hpc NetworkManager: <info> (eth0): preparing device. Jan 6 15:26:05 hpc NetworkManager: <info> (eth0): deactivating device (reason: 2). Jan 6 15:26:05 hpc NetworkManager: <info> Setting system hostname to 'localhost' (no default device) Jan 6 15:26:06 hpc NetworkManager: <info> (wlan0): device state change: 1 -> 2 (reason 2) Jan 6 15:26:06 hpc NetworkManager: <info> (wlan0): bringing up device. Jan 6 15:26:06 hpc NetworkManager: <info> (wlan0): deactivating device (reason: 2). Jan 6 15:26:06 hpc NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed Jan 6 15:26:06 hpc NetworkManager: <info> Wireless now disabled by radio killswitch Jan 6 15:26:06 hpc NetworkManager: <info> (wlan0): supplicant manager state: down -> idle Jan 6 15:26:06 hpc NetworkManager: <info> Setting system hostname to 'hpc' (from system configuration) Jan 6 15:26:07 hpc NetworkManager: <info> (eth0): carrier now ON (device state 2) Jan 6 15:26:07 hpc NetworkManager: <info> (eth0): device state change: 2 -> 3 (reason 40) Jan 6 15:26:07 hpc NetworkManager: <info> Activation (eth0) starting connection 'System eth0' Jan 6 15:26:07 hpc NetworkManager: <info> (eth0): device state change: 3 -> 4 (reason 0) Jan 6 15:26:07 hpc NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... Jan 6 15:26:07 hpc NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started... Jan 6 15:26:07 hpc NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... Jan 6 15:26:07 hpc NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete. Jan 6 15:26:07 hpc NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting... Jan 6 15:26:07 hpc NetworkManager: <info> (eth0): device state change: 4 -> 5 (reason 0) Jan 6 15:26:07 hpc NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful. Jan 6 15:26:07 hpc NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. Jan 6 15:26:07 hpc NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete. Jan 6 15:26:07 hpc NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started... Jan 6 15:26:07 hpc NetworkManager: <info> (eth0): device state change: 5 -> 7 (reason 0) Jan 6 15:26:07 hpc NetworkManager: <info> Activation (eth0) Beginning DHCP transaction. Jan 6 15:26:07 hpc NetworkManager: <info> dhclient started with pid 2461 Jan 6 15:26:07 hpc NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Jan 6 15:26:07 hpc NetworkManager: <info> DHCP: device eth0 state changed (null) -> preinit Jan 6 15:26:07 hpc NetworkManager: <info> DHCP: device eth0 state changed preinit -> reboot Jan 6 15:26:07 hpc NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled... Jan 6 15:26:07 hpc NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) started... Jan 6 15:26:07 hpc NetworkManager: <info> address 192.168.2.110 Jan 6 15:26:07 hpc NetworkManager: <info> prefix 24 (255.255.255.0) Jan 6 15:26:07 hpc NetworkManager: <info> gateway 192.168.2.1 Jan 6 15:26:07 hpc NetworkManager: <info> nameserver '192.168.2.1' Jan 6 15:26:07 hpc NetworkManager: <info> domain name 'intranet.ip' Jan 6 15:26:07 hpc NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... Jan 6 15:26:07 hpc NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) complete. Jan 6 15:26:07 hpc NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... Jan 6 15:26:08 hpc NetworkManager: <info> (eth0): device state change: 7 -> 8 (reason 0) Jan 6 15:26:08 hpc NetworkManager: <debug> [1452090368.702315] run_netconfig(): Spawning '/sbin/netconfig modify --service NetworkManager' Jan 6 15:26:08 hpc NetworkManager: <debug> [1452090368.705992] write_to_netconfig(): Writing to netconfig: DNSSEARCH='intranet.ip intranet.ip' Jan 6 15:26:08 hpc NetworkManager: <debug> [1452090368.706138] write_to_netconfig(): Writing to netconfig: DNSSERVERS='192.168.2.1' Jan 6 15:26:08 hpc NetworkManager: <info> Clearing nscd hosts cache. Jan 6 15:26:08 hpc NetworkManager: <info> Policy set 'System eth0' (eth0) as default for routing and DNS. Jan 6 15:26:08 hpc NetworkManager: <info> Activation (eth0) successful, device activated. Jan 6 15:26:08 hpc NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.

[QUOTE]I do suggest you pop over to the HP forums, there maybe some info on
unblocking those softblocks…[/QUOTE]

Thanks again for help, hints, and patience.

[malcolmlewis]

On Wed 06 Jan 2016 04:54:01 PM CST, guennov wrote:

<info>  Wireless now disabled by radio killswitch

Hi
No problems, we are here to help

AFAIK it’s a windows thing, as in you need to boot into windows and
enable, since you have Linux, hard to do. HP provide a driver to
complete this in Linux for the HP systems, which again AFAIK is
provided by there repositories that get added when you active the
system for updates.

You could try an acpi option, but not sure… Fire up YaST
System-> Bootloader, on the Kernel tab add this in on the Optional
Kernel Commands part before the last entry showopts;

acpi_osi=\"!Windows 2012\"

Reboot and see if the Fn+wireless keys starts to work, verify with
rfkill to see if key presses change it.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.2|3.12.51-60.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

[guennov]

Hi Malcolm

[QUOTE]You could try an acpi option, but not sure… Fire up YaST
System-> Bootloader, on the Kernel tab add this in on the Optional
Kernel Commands part before the last entry showopts;

acpi_osi=\"!Windows 2012\"

Reboot and see if the Fn+wireless keys starts to work, verify with
rfkill to see if key presses change it.
[/QUOTE]

Yes, now the wireless key starts to work. “rfkill list” now shows

0: hp-wifi: Wireless LAN Soft blocked: yes Hard blocked: no 1: hp-bluetooth: Bluetooth Soft blocked: yes Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no 3: hci0: Bluetooth Soft blocked: no Hard blocked: no
Pressing the key toggles hard blocking for hp-wifi and hp-bluetooth from ‘no’ to ‘yes’ and vice versa. Unfortunately both remain soft blocked.

Thank you!

[malcolmlewis]

On Wed 06 Jan 2016 08:44:02 PM CST, guennov wrote:

Hi Malcolm
[color=blue]

You could try an acpi option, but not sure… Fire up YaST
System-> Bootloader, on the Kernel tab add this in on the Optional
Kernel Commands part before the last entry showopts;
[color=green]

[/color][/color]
Code:
--------------------[color=blue][color=green]
[/color]
acpi_osi="!Windows 2012"
[/color]
--------------------[color=blue][color=green]
[/color]

Reboot and see if the Fn+wireless keys starts to work, verify with
rfkill to see if key presses change it.
[/color]

Yes, now the wireless key starts to work. “rfkill list” now shows

Code:

0: hp-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: no
1: hp-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

---

Pressing the key toggles hard blocking for hp-wifi and hp-bluetooth from
‘no’ to ‘yes’ and vice versa. Unfortunately both remain soft blocked.

Thank you!

Hi
Good news

Now you should be able to clear the other softblocks;

rfkill unblock 0
rfkill unblock 1
rfkill list

I had the same issue with my HP ProBook 455 G1 but with SLED 12 during
beta testing but had it fixed.

If you upgrade to SLED 12 SP1 it should be all good. Remember SLED 11
will go out of general support soon, so no more updates.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.2|3.12.51-60.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

[guennov]

Hi

[QUOTE]Now you should be able to clear the other softblocks;

rfkill unblock 0 rfkill unblock 1 rfkill list [/QUOTE]

No, those softblocks are not cleared.

[QUOTE]If you upgrade to SLED 12 SP1 it should be all good.[/QUOTE]Because of the i586 architecture unfortunately switching to SLE 12 is no option.

Cheers
guennov