2.4GHZ WI-FI NETWORK DOESN'T CONNECT TO UBUNTU 20.10

humberto99

New Member
Credits
73
This week I acquired a TP-Link Dual Band AC 1350 Archer C60 Wireless Router, configured the two networks (2.4GHz and 5GHz) and it's working correctly (in parts).

On my cell phone and all other cell phones here at home, both 2.4 and 5GHz networks normally work. I also connected my Echo Dot that I have here at home on the 2.4GHz network, and the internet access is working perfectly. My PC, which is connected via cable, is also working correctly.

The problem is restricted only here on this Dell Inspiron 15-3583 notebook. I have dual boot of windows 10 with Ubuntu 20.10 for approximately 5 months, and while using the company's router modem (until today before installing the TP-Link router) Ubuntu connected to the network normally.

I installed my TP-Link router just now and only the 5GHz network connects to this system (Ubuntu), while the 2.4GHz network doesn't establish a connection. I restarted the notebook and started on windows 10, and there both networks (2.4 and 5GHz) connect normally without any problems. Back to Ubuntu I can only use the 5GHz network.

I've already tried to reset the company's modem and the TP-Link router, tried to reset both devices, tried to restart the notebook several times.

I saw it in some forums and I noticed that in the file "/etc/NetworkManager/NetworkManager.conf" it already has this line: "wifi.scan-rand-mac-address = no"

I have no idea what to do because all devices here at home, including this notebook on Windows 10 connect to the 2.4GHz network but when I start Ubuntu it simply doesn't connect, being limited only to the 5GHz network that has a weaker signal , not even covering the entire house.
 


KGIII

Super Moderator
Staff member
Gold Supporter
Credits
26,277
I'd look to see if there's a better driver for your laptop's wireless card/adapter. If you have inxi installed, then 'inxi -v 5' should give you a ton of output, including the name and model of your wireless hardware. Then use that information to look up 'make model +linux drivers' to see what you find.
 

humberto99

New Member
Credits
73
What is output from

iw list

and

nmcli dev wifi list
output from iw list:

Bash:
$ iw list
Wiphy phy0
    wiphy index: 0
    max # scan SSIDs: 20
    max scan IEs length: 422 bytes
    max # sched scan SSIDs: 20
    max # match sets: 11
    max # scan plans: 2
    max scan plan interval: 65535
    max scan plan iterations: 254
    Retry short limit: 7
    Retry long limit: 4
    Coverage class: 0 (up to 0m)
    Device supports RSN-IBSS.
    Device supports AP-side u-APSD.
    Device supports T-DLS.
    Supported Ciphers:
        * WEP40 (00-0f-ac:1)
        * WEP104 (00-0f-ac:5)
        * TKIP (00-0f-ac:2)
        * CCMP-128 (00-0f-ac:4)
        * GCMP-128 (00-0f-ac:8)
        * GCMP-256 (00-0f-ac:9)
        * CMAC (00-0f-ac:6)
        * GMAC-128 (00-0f-ac:11)
        * GMAC-256 (00-0f-ac:12)
    Available Antennas: TX 0x1 RX 0x1
    Configured Antennas: TX 0x1 RX 0x1
    Supported interface modes:
         * IBSS
         * managed
         * AP
         * AP/VLAN
         * monitor
         * P2P-client
         * P2P-GO
         * P2P-device
    Band 1:
        Capabilities: 0x196f
            RX LDPC
            HT20/HT40
            SM Power Save disabled
            RX HT20 SGI
            RX HT40 SGI
            RX STBC 1-stream
            Max AMSDU length: 7935 bytes
            DSSS/CCK HT40
        Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
        Minimum RX AMPDU time spacing: 4 usec (0x05)
        HT Max RX data rate: 150 Mbps
        HT TX/RX MCS rate indexes supported: 0-7
        Bitrates (non-HT):
            * 1.0 Mbps
            * 2.0 Mbps (short preamble supported)
            * 5.5 Mbps (short preamble supported)
            * 11.0 Mbps (short preamble supported)
            * 6.0 Mbps
            * 9.0 Mbps
            * 12.0 Mbps
            * 18.0 Mbps
            * 24.0 Mbps
            * 36.0 Mbps
            * 48.0 Mbps
            * 54.0 Mbps
        Frequencies:
            * 2412 MHz [1] (22.0 dBm)
            * 2417 MHz [2] (22.0 dBm)
            * 2422 MHz [3] (22.0 dBm)
            * 2427 MHz [4] (22.0 dBm)
            * 2432 MHz [5] (22.0 dBm)
            * 2437 MHz [6] (22.0 dBm)
            * 2442 MHz [7] (22.0 dBm)
            * 2447 MHz [8] (22.0 dBm)
            * 2452 MHz [9] (22.0 dBm)
            * 2457 MHz [10] (22.0 dBm)
            * 2462 MHz [11] (22.0 dBm)
            * 2467 MHz [12] (22.0 dBm)
            * 2472 MHz [13] (22.0 dBm)
    Band 2:
        Capabilities: 0x196f
            RX LDPC
            HT20/HT40
            SM Power Save disabled
            RX HT20 SGI
            RX HT40 SGI
            RX STBC 1-stream
            Max AMSDU length: 7935 bytes
            DSSS/CCK HT40
        Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
        Minimum RX AMPDU time spacing: 4 usec (0x05)
        HT Max RX data rate: 150 Mbps
        HT TX/RX MCS rate indexes supported: 0-7
        VHT Capabilities (0x33907132):
            Max MPDU length: 11454
            Supported Channel Width: neither 160 nor 80+80
            RX LDPC
            short GI (80 MHz)
            SU Beamformee
            MU Beamformee
            RX antenna pattern consistency
            TX antenna pattern consistency
        VHT RX MCS set:
            1 streams: MCS 0-9
            2 streams: not supported
            3 streams: not supported
            4 streams: not supported
            5 streams: not supported
            6 streams: not supported
            7 streams: not supported
            8 streams: not supported
        VHT RX highest supported: 0 Mbps
        VHT TX MCS set:
            1 streams: MCS 0-9
            2 streams: not supported
            3 streams: not supported
            4 streams: not supported
            5 streams: not supported
            6 streams: not supported
            7 streams: not supported
            8 streams: not supported
        VHT TX highest supported: 0 Mbps
        Bitrates (non-HT):
            * 6.0 Mbps
            * 9.0 Mbps
            * 12.0 Mbps
            * 18.0 Mbps
            * 24.0 Mbps
            * 36.0 Mbps
            * 48.0 Mbps
            * 54.0 Mbps
        Frequencies:
            * 5180 MHz [36] (22.0 dBm) (no IR)
            * 5200 MHz [40] (22.0 dBm) (no IR)
            * 5220 MHz [44] (22.0 dBm) (no IR)
            * 5240 MHz [48] (22.0 dBm) (no IR)
            * 5260 MHz [52] (22.0 dBm) (no IR, radar detection)
            * 5280 MHz [56] (22.0 dBm) (no IR, radar detection)
            * 5300 MHz [60] (22.0 dBm) (no IR, radar detection)
            * 5320 MHz [64] (22.0 dBm) (no IR, radar detection)
            * 5500 MHz [100] (22.0 dBm) (no IR, radar detection)
            * 5520 MHz [104] (22.0 dBm) (no IR, radar detection)
            * 5540 MHz [108] (22.0 dBm) (no IR, radar detection)
            * 5560 MHz [112] (22.0 dBm) (no IR, radar detection)
            * 5580 MHz [116] (22.0 dBm) (no IR, radar detection)
            * 5600 MHz [120] (22.0 dBm) (no IR, radar detection)
            * 5620 MHz [124] (22.0 dBm) (no IR, radar detection)
            * 5640 MHz [128] (22.0 dBm) (no IR, radar detection)
            * 5660 MHz [132] (22.0 dBm) (no IR, radar detection)
            * 5680 MHz [136] (22.0 dBm) (no IR, radar detection)
            * 5700 MHz [140] (22.0 dBm) (no IR, radar detection)
            * 5720 MHz [144] (22.0 dBm) (no IR, radar detection)
            * 5745 MHz [149] (22.0 dBm)
            * 5765 MHz [153] (22.0 dBm)
            * 5785 MHz [157] (22.0 dBm)
            * 5805 MHz [161] (22.0 dBm)
            * 5825 MHz [165] (22.0 dBm)
    Supported commands:
         * new_interface
         * set_interface
         * new_key
         * start_ap
         * new_station
         * new_mpath
         * set_mesh_config
         * set_bss
         * authenticate
         * associate
         * deauthenticate
         * disassociate
         * join_ibss
         * join_mesh
         * remain_on_channel
         * set_tx_bitrate_mask
         * frame
         * frame_wait_cancel
         * set_wiphy_netns
         * set_channel
         * set_wds_peer
         * tdls_mgmt
         * tdls_oper
         * start_sched_scan
         * probe_client
         * set_noack_map
         * register_beacons
         * start_p2p_device
         * set_mcast_rate
         * connect
         * disconnect
         * channel_switch
         * set_qos_map
         * add_tx_ts
         * set_multicast_to_unicast
    Supported TX frame types:
         * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
         * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
    Supported RX frame types:
         * IBSS: 0x40 0xb0 0xc0 0xd0
         * managed: 0x40 0xb0 0xd0
         * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
         * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
         * mesh point: 0xb0 0xc0 0xd0
         * P2P-client: 0x40 0xd0
         * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
         * P2P-device: 0x40 0xd0
    WoWLAN support:
         * wake up on disconnect
         * wake up on magic packet
         * wake up on pattern match, up to 20 patterns of 16-128 bytes,
           maximum packet offset 0 bytes
         * can do GTK rekeying
         * wake up on GTK rekey failure
         * wake up on EAP identity request
         * wake up on 4-way handshake
         * wake up on rfkill release
         * wake up on network detection, up to 11 match sets
    software interface modes (can always be added):
         * AP/VLAN
         * monitor
    valid interface combinations:
         * #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1,
           total <= 3, #channels <= 2
    HT Capability overrides:
         * MCS: ff ff ff ff ff ff ff ff ff ff
         * maximum A-MSDU length
         * supported channel width
         * short GI for 40 MHz
         * max A-MPDU length exponent
         * min MPDU start spacing
    Device supports TX status socket option.
    Device supports HT-IBSS.
    Device supports SAE with AUTHENTICATE command
    Device supports low priority scan.
    Device supports scan flush.
    Device supports per-vif TX power setting
    P2P GO supports CT window setting
    P2P GO supports opportunistic powersave setting
    Driver supports full state transitions for AP/GO clients
    Driver supports a userspace MPM
    Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
    Device adds DS IE to probe requests
    Device can update TPC Report IE
    Device supports static SMPS
    Device supports dynamic SMPS
    Device supports WMM-AC admission (TSPECs)
    Device supports configuring vdev MAC-addr on create.
    Device supports randomizing MAC-addr in scans.
    Device supports randomizing MAC-addr in sched scans.
    Device supports randomizing MAC-addr in net-detect scans.
    Supported extended features:
        * [ VHT_IBSS ]: VHT-IBSS
        * [ RRM ]: RRM
        * [ MU_MIMO_AIR_SNIFFER ]: MU-MIMO sniffer
        * [ SCAN_START_TIME ]: scan start timestamp
        * [ BSS_PARENT_TSF ]: BSS last beacon/probe TSF
        * [ SET_SCAN_DWELL ]: scan dwell setting
        * [ FILS_STA ]: STA FILS (Fast Initial Link Setup)
        * [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
        * [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
        * [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support
        * [ DEL_IBSS_STA ]: deletion of IBSS station support
        * [ SCAN_FREQ_KHZ ]: scan on kHz frequency support
        * [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support
output from nmcli dev wifi list
note: Bat Signal 2.4GHz and Bat Signal 5GHz are my wifi networks

Bash:
$ nmcli dev wifi list
IN-USE  BSSID              SSID              MODE   CHAN  RATE        SIGNAL  BARS  SECURITY 
        28:EE:52:4F:83:50  Bat Signal 2.4GHz  Infra  10    195 Mbit/s  84      ▂▄▆█  WPA1 WPA2
        2E:EE:52:4F:83:50  --                 Infra  10    195 Mbit/s  77      ▂▄▆_  WPA2     
*       28:EE:52:4F:83:4F  Bat Signal 5GHz    Infra  149   270 Mbit/s  44      ▂▄__  WPA1 WPA2
        2E:EE:52:4F:83:4F  --                 Infra  149   270 Mbit/s  39      ▂▄__  WPA2
 

humberto99

New Member
Credits
73
I'd look to see if there's a better driver for your laptop's wireless card/adapter. If you have inxi installed, then 'inxi -v 5' should give you a ton of output, including the name and model of your wireless hardware. Then use that information to look up 'make model +linux drivers' to see what you find.
I am a recent Linux user, I've basic notions with the terminal. I've been researching what you said and I'll try to find more about drivers on the internet, thanks.
 

Lord Boltar

Well-Known Member
Credits
5,678
A possible solution, is to disable wpa_supplicant and replace it with iwd

Install iwd

sudo apt update
sudo apt install iwd

Create this file inside your NetworkManager configuration files directory

sudo gedit /etc/NetworkManager/conf.d/wifi_backend.conf

Copy and paste into this file the following content, then save the file:

[device]
wifi.backend=iwd

Stop and disable the wpa_supplicant service (note that disabling it is persistent after reboots)

systemctl stop wpa_supplicant.service
systemctl disable wpa_supplicant.service

Enable and start iwd service (note that enabling it is persistent after reboots)

sudo systemctl enable iwd.service
sudo systemctl start iwd.service

Restart NetworkManager service (this means you don't have to restart your computer for this to take effect--it just works immediately!)

systemctl restart network-manager.service

Now try to connect to the 2.4GHz wifi access point
 

dos2unix

Well-Known Member
Credits
4,425
output from iw list:

Bash:
$ iw list

            * 48.0 Mbps
            * 54.0 Mbps
        Frequencies:
            * 2412 MHz [1] (22.0 dBm)
            * 2417 MHz [2] (22.0 dBm)
            * 2422 MHz [3] (22.0 dBm)
            * 2427 MHz [4] (22.0 dBm)
            * 2432 MHz [5] (22.0 dBm)
            * 2437 MHz [6] (22.0 dBm)
            * 2442 MHz [7] (22.0 dBm)
            * 2447 MHz [8] (22.0 dBm)
            * 2452 MHz [9] (22.0 dBm)
            * 2457 MHz [10] (22.0 dBm)
            * 2462 MHz [11] (22.0 dBm)
            * 2467 MHz [12] (22.0 dBm)
            * 2472 MHz [13] (22.0 dBm)
    Band 2:

            * 54.0 Mbps
        Frequencies:
            * 5180 MHz [36] (22.0 dBm) (no IR)
            * 5200 MHz [40] (22.0 dBm) (no IR)
            * 5220 MHz [44] (22.0 dBm) (no IR)
            * 5240 MHz [48] (22.0 dBm) (no IR)
            * 5260 MHz [52] (22.0 dBm) (no IR, radar detection)
            * 5280 MHz [56] (22.0 dBm) (no IR, radar detection)
            * 5300 MHz [60] (22.0 dBm) (no IR, radar detection)
            * 5320 MHz [64] (22.0 dBm) (no IR, radar detection)
            * 5500 MHz [100] (22.0 dBm) (no IR, radar detection)
            * 5520 MHz [104] (22.0 dBm) (no IR, radar detection)
            * 5540 MHz [108] (22.0 dBm) (no IR, radar detection)
            * 5560 MHz [112] (22.0 dBm) (no IR, radar detection)
            * 5580 MHz [116] (22.0 dBm) (no IR, radar detection)
            * 5600 MHz [120] (22.0 dBm) (no IR, radar detection)
            * 5620 MHz [124] (22.0 dBm) (no IR, radar detection)
            * 5640 MHz [128] (22.0 dBm) (no IR, radar detection)
            * 5660 MHz [132] (22.0 dBm) (no IR, radar detection)
            * 5680 MHz [136] (22.0 dBm) (no IR, radar detection)
            * 5700 MHz [140] (22.0 dBm) (no IR, radar detection)
            * 5720 MHz [144] (22.0 dBm) (no IR, radar detection)
            * 5745 MHz [149] (22.0 dBm)
            * 5765 MHz [153] (22.0 dBm)
            * 5785 MHz [157] (22.0 dBm)
            * 5805 MHz [161] (22.0 dBm)
            * 5825 MHz [165] (22.0 dBm)
 
output from nmcli dev wifi list
note: Bat Signal 2.4GHz and Bat Signal 5GHz are my wifi networks

[CODE=bash]$ nmcli dev wifi list
IN-USE  BSSID              SSID              MODE   CHAN  RATE        SIGNAL  BARS  SECURITY
        28:EE:52:4F:83:50  Bat Signal 2.4GHz  Infra  10    195 Mbit/s  84      ▂▄▆█  WPA1 WPA2
        2E:EE:52:4F:83:50  --                 Infra  10    195 Mbit/s  77      ▂▄▆_  WPA2    
*       28:EE:52:4F:83:4F  Bat Signal 5GHz    Infra  149   270 Mbit/s  44      ▂▄__  WPA1 WPA2
        2E:EE:52:4F:83:4F  --                 Infra  149   270 Mbit/s  39      ▂▄__  WPA2
If you see this, then your drivers are defintely working.

What is output of

systemctl status -l wpa_supplicant
 

humberto99

New Member
Credits
73
If you share the salient output from the inxi command, someone may be able to help. I'll be stepping out for the afternoon, but if nobody else finds anything I can look when I get back.
That's the output when I run"inxi -v 5". Thanks
Bash:
$ inxi -v 5
System:    Host: humberto Kernel: 5.8.0-41-generic x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: N/A
           Distro: Ubuntu 20.10 (Groovy Gorilla)
Machine:   Type: Laptop System: Dell product: Inspiron 3583 v: N/A serial: <superuser/root required>
           Mobo: Dell model: 0TDN17 v: A01 serial: <superuser/root required> UEFI: Dell v: 1.8.0 date: 02/12/2020
Battery:   ID-1: BAT0 charge: 17.6 Wh condition: 38.6/42.0 Wh (92%) model: SMP DELL Y3F7Y6B status: Discharging
Memory:    RAM: total: 15.51 GiB used: 4.13 GiB (26.6%)
           RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU:       Info: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: C L2 cache: 6144 KiB
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800
           Speed: 800 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 799 2: 792 3: 800 4: 800 5: 800 6: 788 7: 800 8: 800
Graphics:  Device-1: Intel UHD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0
           Device-2: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo bus ID: 1-6:2
           Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz
           OpenGL: renderer: Mesa Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 20.2.6 direct render: Yes
Audio:     Device-1: Intel Cannon Point-LP High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:1f.3
           Sound Server: ALSA v: k5.8.0-41-generic
Network:   Device-1: Intel Cannon Point-LP CNVi [Wireless-AC] driver: iwlwifi v: kernel port: 4000 bus ID: 00:14.3
           IF: wlo1 state: up mac: 5c:cd:5b:0d:1b:64
           Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000
           bus ID: 01:00.0
           IF: enp1s0 state: down mac: 88:6f:d4:ff:2b:74
Drives:    Local Storage: total: 931.51 GiB used: 41.95 GiB (4.5%)
           ID-1: /dev/sda vendor: Toshiba model: MQ04ABF100 size: 931.51 GiB
           Message: No Optical or Floppy data was found.
Partition: ID-1: / size: 763.56 GiB used: 41.91 GiB (5.5%) fs: ext4 dev: /dev/sda6 label: N/A
           uuid: 8494e712-4ccb-4956-a143-2cf2e554f715
Swap:      ID-1: swap-1 type: partition size: 3.81 GiB used: 0 KiB (0.0%) dev: /dev/sda5 label: N/A
           uuid: 67816703-cd50-414c-9fc2-045a0ef18844
Sensors:   System Temperatures: cpu: 42.0 C mobo: N/A
           Fan Speeds (RPM): cpu: 0
Info:      Processes: 317 Uptime: 6m Init: systemd runlevel: 5 Compilers: gcc: 10.2.0 Packages: 2090 Shell: Bash v: 5.0.17
           inxi: 3.1.07
 

humberto99

New Member
Credits
73
If you see this, then your drivers are defintely working.

What is output of

systemctl status -l wpa_supplicant
That's the output when I run "systemctl status -l wpa_supplicant". Thanks
Bash:
$ systemctl status -l wpa_supplicant
● wpa_supplicant.service - WPA supplicant
     Loaded: loaded (/lib/systemd/system/wpa_supplicant.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2021-05-20 13:17:18 -03; 11min ago
   Main PID: 806 (wpa_supplicant)
      Tasks: 1 (limit: 18993)
     Memory: 6.6M
     CGroup: /system.slice/wpa_supplicant.service
             └─806 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant

mai 20 13:17:47 humberto wpa_supplicant[806]: wlo1: Associated with 28:ee:52:4f:83:4f
mai 20 13:17:47 humberto wpa_supplicant[806]: wlo1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
mai 20 13:17:47 humberto wpa_supplicant[806]: wlo1: WPA: Key negotiation completed with 28:ee:52:4f:83:4f [PTK=CCMP GTK=CCMP]
mai 20 13:17:47 humberto wpa_supplicant[806]: wlo1: CTRL-EVENT-CONNECTED - Connection to 28:ee:52:4f:83:4f completed [id=0 id_str=]
mai 20 13:17:48 humberto wpa_supplicant[806]: wlo1: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-72 noise=9999 txrate=292600
mai 20 13:18:00 humberto wpa_supplicant[806]: wlo1: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-73 noise=9999 txrate=260000
mai 20 13:23:58 humberto wpa_supplicant[806]: wlo1: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-68 noise=9999 txrate=195000
mai 20 13:24:42 humberto wpa_supplicant[806]: wlo1: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-74 noise=9999 txrate=97600
mai 20 13:25:08 humberto wpa_supplicant[806]: wlo1: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-76 noise=9999 txrate=29300
mai 20 13:27:22 humberto wpa_supplicant[806]: wlo1: Reject scan trigger since one is already pending
 

humberto99

New Member
Credits
73
I'm at the doctor's office and on mobile. I'd look to see if there were better drivers by using the device name and model. Copy that and add +Linux driver to your search terms.
I've been looking for "Intel Cannon Point-LP CNVi [Wireless-AC]" and found this drive on this site:

I ended up hitting a page on github but I have no idea what to do with it.
 

dos2unix

Well-Known Member
Credits
4,425
Almost certainly the intel iwlwifi drivers are what you are using. These are usually very good.
Intel is usually pretty good about keeping stuff in Linux up to date. They are a major contributor/supporter.

You might try this.

nmcli radio wifi on

then this.

sudo nmcli dev wifi connect 'Bat Signal 2.4GHz' password 'mypassword'

Change the password to whatever your password is.

If this doesn't work, it would be interesting to see the output from this. (Be careful not to post your password)
 

KGIII

Super Moderator
Staff member
Gold Supporter
Credits
26,277
Hmm... I see you have two wireless cards/adapters.

Like @dos2unix, I suspect you're using the Intel drivers. They're two radio signals - in close proximity. That could lead to problems.

First, why are there two wireless cards?
 

humberto99

New Member
Credits
73
Almost certainly the intel iwlwifi drivers are what you are using. These are usually very good.
Intel is usually pretty good about keeping stuff in Linux up to date. They are a major contributor/supporter.

You might try this.

nmcli radio wifi on

then this.

sudo nmcli dev wifi connect 'Bat Signal 2.4GHz' password 'mypassword'

Change the password to whatever your password is.

If this doesn't work, it would be interesting to see the output from this. (Be careful not to post your password)
I put my password and ran the command. The terminal was busy for a while and then this message returned:
Bash:
$ nmcli radio wifi on
$ sudo nmcli dev wifi connect 'Bat Signal 2.4GHz' password 'my_pass'
[sudo] password for humberto:
Error: Connection activation failed: (7) Secrets were required, but not provided.
 

humberto99

New Member
Credits
73
Hmm... I see you have two wireless cards/adapters.

Like @dos2unix, I suspect you're using the Intel drivers. They're two radio signals - in close proximity. That could lead to problems.

First, why are there two wireless cards?
I saw that there were two network cards but I thought it was because the laptop has a wired Ethernet port too.
I have no idea why there are two cards. my knowledge with linux is limited to that of an ordinary user. I just did the standard installation of Ubuntu.
 

KGIII

Super Moderator
Staff member
Gold Supporter
Credits
26,277
Interestingly, it looks like it has some issues with some variants (but, curiously, not all) of Linux.

As you scroll down on that page, you'll see it works in Mint 20.1. As a lark, and just to see, I'd download Mint 20.1 and see if it works in a live environment - just boot to it but don't install it.
 
$100 Digital Ocean Credit
Get a free VM to test out Linux!

Members online


Latest posts

Top