Page 1 of 3 123 LastLast
Results 1 to 10 of 23

Thread: NetworkManager without wlan

  1. #1

    NetworkManager without wlan

    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

  2. Re: NetworkManager without wlan

    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/reposit...3.1.x86_64.rpm

    Then as root user run to verify;
    Code:
    rfkill list
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  3. #3

    Re: NetworkManager without wlan

    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?

  4. Re: NetworkManager without wlan

    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?

    Code:
    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;
    Code:
    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!


  5. #5

    Re: NetworkManager without wlan

    Hi

    So what model HP, do you see any output from the following command?
    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
    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.
    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;
    Code:
    rfkill unblock 0
    rfkill unblock 1
    rfkill unblock 2
    rfkill unblock 3
    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.

  6. Re: NetworkManager without wlan

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

    Hi

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


    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

    --------------------


    > 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.


    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;
    > >

    Code:
    --------------------
    > >

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

    --------------------
    > >

    >


    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!


  7. #7

    Re: NetworkManager without wlan

    Hi

    sorry about the delay.

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

    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?
    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.

    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.
    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!

  8. Re: NetworkManager without wlan

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

    Hi

    sorry about the delay.

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


    SLED11

    >
    > 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?


    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.


    > 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.


    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 ESSIDff/any
    Mode:Managed Access Point: Not-Associated Tx-Power=off
    Retry long limit:7 RTS thrff Fragment thrff
    Encryption keyff
    Power Managementff
    --------------------


    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?
    Code:
    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!


  9. #9

    Re: NetworkManager without wlan

    Hi
    You should have some HP repositories then?
    Code:
    zypper lr -d
    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.

    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

  10. #10

    Re: NetworkManager without wlan

    Additional data from "modinfo ath9k"

    Code:
    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)
    Last edited by guennov; 06-Jan-2016 at 00:53. Reason: syntax error

Page 1 of 3 123 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •