Results 1 to 3 of 3

Thread: Wireless Adator not starting automatically

  1. #1

    Default Wireless Adator not starting automatically

    Hi folks
    I have been dual-booting one of my laptops with Windows 10 and OpenSuse Leap 15.1 for months without any real problems. I booted OpenSuse up the other day and found I had not got an Internet connection. (Last time I had used it, there had been no problem with the Internet, or connecting to other computers on my home network [I have 3 - a desktop and two laptops])
    I opened Yast > System > Network Settings to find that the adaptor was showing as 'Not Connected'. 'ip a' in a terminal showed that Wlan0 was down. I could bring it up by typing 'ifup Wlan0', and then everything worked fine - which means that all the settings are OK. I use a fixed ip, but I tried using DHCP to see if it made any difference, but it was the same. Rebooting with the interface up resulted in 'not connected' and the interface down again when the system came back up.
    I have done a complete new install of the whole system. Same result - 'Not connected'. Can still manually bring the interface up.
    So, the wireless adaptor is not connecting automatically.
    System is as follows:
    Acer Aspire E5-571-304M
    Motherboard EX50-HB
    Intel Corei3-4005U
    12GB ram
    Qualcomm QCA9565/AR9565 wireless adaptor
    SSD: CT240BX500SSD1 (system)
    HDD: WD10JPVX-22J (for data only)

    Output of 'lspci' contains the line:
    02:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01)

    Output of 'dmesg | less' contains the line:
    [ 11.116711] ieee80211 phy0: Atheros AR9565 Rev:1 mem=0xffffc90002c00000, irq=19

    'iwconfig' gives:
    eth0 no wireless extensions.

    lo no wireless extensions.

    wlan0 IEEE 802.11 ESSIDff/any
    Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
    Retry short limit:7 RTS thrff Fragment thrff
    Encryption keyff
    Power Managementff

    but if I bring the interface up manually, it gives:
    eth0 no wireless extensions.

    lo no wireless extensions.

    wlan0 IEEE 802.11 ESSID:"PLUSNET-FHMR"
    Mode:Managed Frequency:2.437 GHz Access Point: F8:1A:67:AA:9C:6C
    Bit Rate=120 Mb/s Tx-Power=16 dBm
    Retry short limit:7 RTS thrff Fragment thrff
    Encryption keyff
    Power Managementff
    Link Quality=66/70 Signal level=-44 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:32 Missed beacon:0

    'wlist scan' gives the following on boot up:
    eth0 Interface doesn't support scanning.

    lo Interface doesn't support scanning.

    wlan0 Interface doesn't support scanning : Network is down

    but if I bring up the interface manually, it contains the details of all the routers it can reach (about 6 in nearby houses), including my own:
    Cell 02 - Address: F8:1A:67:AA:9C:6C
    Channel:6
    Frequency:2.437 GHz (Channel 6)
    Quality=69/70 Signal level=-41 dBm
    Encryption keyn
    ESSID:"PLUSNET-FHMR"
    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
    9 Mb/s; 12 Mb/s; 18 Mb/s
    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
    Mode:Master
    Extra:tsf=0000000085f1dea6
    Extra: Last beacon: 20ms ago
    IE: Unknown: 000C504C55534E45542D46484D52
    IE: Unknown: 010882848B960C121824
    IE: Unknown: 030106
    IE: Unknown: 0706474220010D14
    IE: Unknown: 2A0100
    IE: Unknown: 32043048606C
    IE: Unknown: 2D1AEF1103FFFF000000000000000000008000000000000000000000
    IE: Unknown: 331AEF1103FFFF000000000000000000008000000000000000000000
    IE: Unknown: 3D16060F0400000000000000000000000000000000000000
    IE: Unknown: 3416060F0400000000000000000000000000000000000000
    IE: Unknown: DD180050F20201018C0003A4000027A4000042435E0062322F00
    IE: Unknown: DD0900037F01010000FF7F
    IE: IEEE 802.11i/WPA2 Version 1
    Group Cipher : TKIP
    Pairwise Ciphers (2) : CCMP TKIP
    Authentication Suites (1) : PSK
    IE: WPA Version 1
    Group Cipher : TKIP
    Pairwise Ciphers (2) : CCMP TKIP
    Authentication Suites (1) : PSK

    I can't find any command which will bring the interface up automatically. Can anyone help?
    Many thanks in advance!

  2. #2
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    4,384

    Default AW: Wireless Adator not starting automatically

    When your network is configured with Yast (wicked) you are running in a bug of wpa_supplicant.
    https://bugzilla.suse.com/show_bug.cgi?id=1166933


    With Lan cable:
    Install the old one:
    Code:
    zypper in -f wpa_supplicant-2.6-lp151.4.4
    Lock the package from updating:
    Code:
    zypper al wpa_supplicant
    Last edited by Sauerland; 05-Apr-2020 at 08:59.

  3. #3

    Default Re: Wireless Adaptor not starting automatically

    Hi Sauerland
    Great result! Yes, that worked. Thanks very much for your help.

Posting Permissions

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