Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[Solved] WiFi channels visible but connection impossible on Debian 12 MATE and XFCE

Ask for help with issues regarding the Installations of the Debian O/S.
Post Reply
Message
Author
JohnWasRight
Posts: 8
Joined: 2024-01-20 13:07

[Solved] WiFi channels visible but connection impossible on Debian 12 MATE and XFCE

#1 Post by JohnWasRight »

I'm traditionally a Debian MATE user - I write these lines from my main computer, running Debian 12 MATE. Whenever I want to try Linux on a "new old" computer, I try Debian MATE first.

I have tried to do the same on a Lenovo mini laptop currently running "the other OS". It's a bit underpowered (1.3Ghz 64-bit processor, 2GB RAM) but within the specs. Live USB is a bit slow to boot but gets there eventually. However, there is a very peculiar problem: I can see the available WiFi channels (my own among them), but when trying to connect, after supplying my password (double- and triple-checking with "show password" that is correct), there is a short attempt to connect and then I am shown the password prompt again. Meanwhile, the WiFi icon on the taskbar shows the "trying to connect" animation. If I try to resubmit the password, nothing happens. After a while the "disconnect" icon is shown on the taskbar, and clicking (left- or right-click) on it is no longer responsive. That is, I can't even display the channel list anymore.

This has happened both with Debian 12 MATE and Debian 12 XFCE (parenthetically, I've also tried LXDE which has all sorts of other WiFi issues; can't even start the network manager)

For reference, I have tried Puppy Bookworm and Bodhi on this device and WiFi works fine out of the box. I would really prefer to use Debian though. Any ideas? Thanks!
Last edited by JohnWasRight on 2024-01-22 14:02, edited 1 time in total.

User avatar
bbbhltz
Posts: 168
Joined: 2024-01-10 14:53
Location: Normandy
XMMP/Jabber: bbbhltz@mailbox.org
Has thanked: 52 times
Been thanked: 34 times

Re: WiFi channels visible but connection impossible on Debian 12 MATE and XFCE

#2 Post by bbbhltz »

JohnWasRight wrote: 2024-01-20 13:17 I have tried to do the same on a Lenovo mini laptop...
Which model? It might need a non-free firmware for the WiFi to work.
bbbhltz
longtime desktop Linux user; eternal newbie

User avatar
FreewheelinFrank
Global Moderator
Global Moderator
Posts: 2140
Joined: 2010-06-07 16:59
Has thanked: 38 times
Been thanked: 233 times

Re: WiFi channels visible but connection impossible on Debian 12 MATE and XFCE

#3 Post by FreewheelinFrank »

In a terminal with root prompt enter

Code: Select all

# journalctl -f
and try connecting.

Any error messages?

JohnWasRight
Posts: 8
Joined: 2024-01-20 13:07

Re: WiFi channels visible but connection impossible on Debian 12 MATE and XFCE

#4 Post by JohnWasRight »

The model is Miix 300-10IBY Tablet (ideapad) - Type 80NR

I was under the impression Debian 12 included non free drivers in the live USB. Or was I mistaken?

After running

Code: Select all

 # journalctl -f
and trying to connect I basically get the same behavior and info in more verbose form. There's a warning at some point about secrets being required but nor provided (I get the same message in GUI). I don't think there's anything informative there, but if you'd still like to see the output, I can provide it, but it might take me some days – I'd need to find another USB stick, I don't have any other way of exporting the info.

User avatar
bbbhltz
Posts: 168
Joined: 2024-01-10 14:53
Location: Normandy
XMMP/Jabber: bbbhltz@mailbox.org
Has thanked: 52 times
Been thanked: 34 times

Re: WiFi channels visible but connection impossible on Debian 12 MATE and XFCE

#5 Post by bbbhltz »

Yes, the firmware is probably there. Do you have the firmware-realtek package installed? (link) Check with

Code: Select all

$ apt policy firmware-realtek
If you run this next command as root, is there any mention of missing firmware?

Code: Select all

# dmesg | grep -i firmware
If nothing is missing, sorry to have wasted your time. You could also try forcing a new IP address with

Code: Select all

dhclient -r wlan0 && dhclient wlan0
bbbhltz
longtime desktop Linux user; eternal newbie

User avatar
FreewheelinFrank
Global Moderator
Global Moderator
Posts: 2140
Joined: 2010-06-07 16:59
Has thanked: 38 times
Been thanked: 233 times

Re: WiFi channels visible but connection impossible on Debian 12 MATE and XFCE

#6 Post by FreewheelinFrank »

JohnWasRight wrote: 2024-01-20 16:10 There's a warning at some point about secrets being required but nor provided (I get the same message in GUI).
warnings about "secrets" usually means the keyring service is the issue. Can you manually enter the password?

Right click on the nm-applet, "Edit connections", find your network and enter the password under "Wi-Fi" security.

In output of the following command, does gnome-keyring-daemon.service appear?

Code: Select all

$ systemctl status --user

User avatar
FreewheelinFrank
Global Moderator
Global Moderator
Posts: 2140
Joined: 2010-06-07 16:59
Has thanked: 38 times
Been thanked: 233 times

Re: WiFi channels visible but connection impossible on Debian 12 MATE and XFCE

#7 Post by FreewheelinFrank »

JohnWasRight wrote: 2024-01-20 16:10 The model is Miix 300-10IBY Tablet (ideapad) - Type 80NR
This model seems to use the rtl8723bs driver. For some setups with an internal usb connection it may not work:

viewtopic.php?p=787180#p787180

Check

Code: Select all

$ lsusb
for device 0bda:b720.

JohnWasRight
Posts: 8
Joined: 2024-01-20 13:07

Re: WiFi channels visible but connection impossible on Debian 12 MATE and XFCE

#8 Post by JohnWasRight »

I was able to find an old USB stick in a box, so I'm able to provide outputs.

Code: Select all

$ apt policy firmware-realtek
firmware-realtek:
  Installed: 20230210-5
  Candidate: 20230210-5
  Version table:
 *** 20230210-5 500
        500 http://deb.debian.org/debian bookworm/non-free-firmware amd64 Packages
        100 /var/lib/dpkg/status

Code: Select all

root@debian:/home/user# dmesg | grep -i firmware
[    0.081547] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    0.178098] [Firmware Info]: PCI: MMCONFIG at [mem 0xe0000000-0xe3ffffff] not reserved in ACPI motherboard resources
[    0.214533] byt_gpio INT33FC:00: [Firmware Bug]: pin 92: direct_irq_en set but no IRQ assigned, clearing
[    0.214553] byt_gpio INT33FC:00: [Firmware Bug]: pin 93: direct_irq_en set but no IRQ assigned, clearing
[    3.144662] ACPI: thermal: [Firmware Bug]: No valid trip found
[   16.966659] intel_sst_acpi 80860F28:00: firmware: direct-loading firmware intel/fw_sst_0f28.bin
[   17.878555] platform regulatory.0: firmware: direct-loading firmware regulatory.db
[   17.969975] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s
[   18.793811] bluetooth hci0: firmware: direct-loading firmware rtl_bt/rtl8723bs_fw.bin
[   18.794154] bluetooth hci0: firmware: direct-loading firmware rtl_bt/rtl8723bs_config-OBDA8723.bin
[   51.445919] rtl8723bs mmc0:0001:1: firmware: direct-loading firmware rtlwifi/rtl8723bs_nic.bin
This one generated a "command not found":

Code: Select all

dhclient -r wlan0 && dhclient wlan0

Code: Select all

root@debian:/home/user# journalctl -f
Jan 21 08:07:55 debian kernel: sd 1:0:0:0: [sdb] Attached SCSI removable disk
Jan 21 08:08:00 debian udisksd[1590]: Mounted /dev/sdb1 at /media/user/USB_STICK on behalf of uid 1000
Jan 21 08:08:33 debian kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Jan 21 08:09:54 debian sudo[2685]:     user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/su
Jan 21 08:09:54 debian sudo[2685]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Jan 21 08:09:54 debian su[2687]: (to root) root on pts/1
Jan 21 08:09:54 debian su[2687]: pam_unix(su:session): session opened for user root(uid=0) by user(uid=0)
Jan 21 08:10:42 debian systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
Jan 21 08:10:42 debian systemd[1]: sysstat-collect.service: Deactivated successfully.
Jan 21 08:10:42 debian systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
Jan 21 08:11:57 debian NetworkManager[1609]: <warn>  [1705824717.0529] device (wlan0): set-hw-addr: new MAC address 6A:F3:A2:E7:1A:B2 not successfully set (scanning)
Jan 21 08:11:57 debian NetworkManager[1609]: <info>  [1705824717.0540] device (wlan0): supplicant interface state: disconnected -> interface_disabled
Jan 21 08:11:57 debian NetworkManager[1609]: <info>  [1705824717.1281] device (wlan0): supplicant interface state: interface_disabled -> inactive
Jan 21 08:12:06 debian NetworkManager[1609]: <info>  [1705824726.7443] device (wlan0): Activation: starting connection 'Wastewlan' (b79f0c0e-9e33-4801-9315-761ceb9197f7)
Jan 21 08:12:06 debian NetworkManager[1609]: <info>  [1705824726.7448] audit: op="connection-add-activate" uuid="b79f0c0e-9e33-4801-9315-761ceb9197f7" name="Wastewlan" pid=2234 uid=1000 result="success"
Jan 21 08:12:06 debian NetworkManager[1609]: <info>  [1705824726.7457] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 21 08:12:06 debian NetworkManager[1609]: <info>  [1705824726.7471] manager: NetworkManager state is now CONNECTING
Jan 21 08:12:06 debian NetworkManager[1609]: <info>  [1705824726.7478] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 21 08:12:06 debian NetworkManager[1609]: <info>  [1705824726.7488] device (wlan0): Activation: (wifi) access point 'Wastewlan' has security, but secrets are required.
Jan 21 08:12:06 debian NetworkManager[1609]: <info>  [1705824726.7489] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jan 21 08:12:07 debian dbus-daemon[1578]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.40' (uid=1000 pid=2234 comm="nm-applet")
Jan 21 08:12:07 debian systemd[1]: Starting systemd-hostnamed.service - Hostname Service...
Jan 21 08:12:08 debian dbus-daemon[1578]: [system] Successfully activated service 'org.freedesktop.hostname1'
Jan 21 08:12:08 debian systemd[1]: Started systemd-hostnamed.service - Hostname Service.
Jan 21 08:12:20 debian NetworkManager[1609]: <info>  [1705824740.9039] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 21 08:12:20 debian NetworkManager[1609]: <info>  [1705824740.9064] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 21 08:12:20 debian NetworkManager[1609]: <info>  [1705824740.9084] device (wlan0): Activation: (wifi) connection 'Wastewlan' has security, and secrets exist.  No new secrets needed.
Jan 21 08:12:20 debian NetworkManager[1609]: <info>  [1705824740.9095] Config: added 'ssid' value 'Wastewlan'
Jan 21 08:12:20 debian NetworkManager[1609]: <info>  [1705824740.9103] Config: added 'scan_ssid' value '1'
Jan 21 08:12:20 debian NetworkManager[1609]: <info>  [1705824740.9111] Config: added 'bgscan' value 'simple:30:-70:86400'
Jan 21 08:12:20 debian NetworkManager[1609]: <info>  [1705824740.9121] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Jan 21 08:12:20 debian NetworkManager[1609]: <info>  [1705824740.9130] Config: added 'auth_alg' value 'OPEN'
Jan 21 08:12:20 debian NetworkManager[1609]: <info>  [1705824740.9138] Config: added 'psk' value '<hidden>'
Jan 21 08:12:21 debian NetworkManager[1609]: <info>  [1705824741.5795] device (wlan0): supplicant interface state: inactive -> scanning
Jan 21 08:12:23 debian wpa_supplicant[1614]: wlan0: Trying to associate with b0:95:75:41:05:c8 (SSID='Wastewlan' freq=2452 MHz)
Jan 21 08:12:23 debian NetworkManager[1609]: <info>  [1705824743.5638] device (wlan0): supplicant interface state: scanning -> associating
Jan 21 08:12:29 debian wpa_supplicant[1614]: wlan0: CTRL-EVENT-ASSOC-REJECT status_code=1
Jan 21 08:12:29 debian wpa_supplicant[1614]: wlan0: CTRL-EVENT-ASSOC-REJECT status_code=1
Jan 21 08:12:29 debian NetworkManager[1609]: <info>  [1705824749.7349] device (wlan0): supplicant interface state: associating -> disconnected
Jan 21 08:12:29 debian NetworkManager[1609]: <info>  [1705824749.8401] device (wlan0): supplicant interface state: disconnected -> scanning
Jan 21 08:12:31 debian wpa_supplicant[1614]: wlan0: Trying to associate with b0:95:75:41:05:c8 (SSID='Wastewlan' freq=2452 MHz)
Jan 21 08:12:31 debian NetworkManager[1609]: <info>  [1705824751.3370] device (wlan0): supplicant interface state: scanning -> associating
Jan 21 08:12:31 debian wpa_supplicant[1614]: wlan0: Associated with b0:95:75:41:05:c8
Jan 21 08:12:31 debian wpa_supplicant[1614]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan 21 08:12:31 debian NetworkManager[1609]: <info>  [1705824751.3505] device (wlan0): supplicant interface state: associating -> associated
Jan 21 08:12:31 debian wpa_supplicant[1614]: wlan0: WPA: Key negotiation completed with b0:95:75:41:05:c8 [PTK=CCMP GTK=CCMP]
Jan 21 08:12:31 debian wpa_supplicant[1614]: wlan0: CTRL-EVENT-CONNECTED - Connection to b0:95:75:41:05:c8 completed [id=0 id_str=]
Jan 21 08:12:31 debian NetworkManager[1609]: <info>  [1705824751.4520] device (wlan0): supplicant interface state: associated -> 4way_handshake
Jan 21 08:12:31 debian kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jan 21 08:12:31 debian wpa_supplicant[1614]: bgscan simple: Failed to enable signal strength monitoring
Jan 21 08:12:38 debian systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Jan 21 08:12:46 debian NetworkManager[1609]: <warn>  [1705824766.2382] device (wlan0): Activation: (wifi) association took too long
Jan 21 08:12:46 debian NetworkManager[1609]: <info>  [1705824766.2384] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jan 21 08:12:46 debian NetworkManager[1609]: <warn>  [1705824766.2416] device (wlan0): Activation: (wifi) asking for new secrets
Jan 21 08:12:46 debian dbus-daemon[1578]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.40' (uid=1000 pid=2234 comm="nm-applet")
Jan 21 08:12:46 debian systemd[1]: Starting systemd-hostnamed.service - Hostname Service...
Jan 21 08:12:47 debian dbus-daemon[1578]: [system] Successfully activated service 'org.freedesktop.hostname1'
Jan 21 08:12:47 debian systemd[1]: Started systemd-hostnamed.service - Hostname Service.
Jan 21 08:12:52 debian NetworkManager[1609]: <info>  [1705824772.0518] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 21 08:12:52 debian NetworkManager[1609]: <info>  [1705824772.0543] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 21 08:12:52 debian NetworkManager[1609]: <info>  [1705824772.0563] device (wlan0): Activation: (wifi) connection 'Wastewlan' has security, and secrets exist.  No new secrets needed.
Jan 21 08:12:52 debian NetworkManager[1609]: <info>  [1705824772.0569] Config: added 'ssid' value 'Wastewlan'
Jan 21 08:12:52 debian NetworkManager[1609]: <info>  [1705824772.0573] Config: added 'scan_ssid' value '1'
Jan 21 08:12:52 debian NetworkManager[1609]: <info>  [1705824772.0576] Config: added 'bgscan' value 'simple:30:-70:86400'
Jan 21 08:12:52 debian NetworkManager[1609]: <info>  [1705824772.0580] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Jan 21 08:12:52 debian NetworkManager[1609]: <info>  [1705824772.0584] Config: added 'auth_alg' value 'OPEN'
Jan 21 08:12:52 debian NetworkManager[1609]: <info>  [1705824772.0587] Config: added 'psk' value '<hidden>'
Jan 21 08:13:06 debian NetworkManager[1609]: <warn>  [1705824786.2420] sup-iface[6b17d7448aff48e7,0,wlan0]: call-disconnect: failed with Timeout was reached
Jan 21 08:13:06 debian NetworkManager[1609]: <warn>  [1705824786.2423] sup-iface[6b17d7448aff48e7,0,wlan0]: call-remove-network: failed with Timeout was reached
Jan 21 08:13:06 debian NetworkManager[1609]: <warn>  [1705824786.2426] sup-iface[6b17d7448aff48e7,0,wlan0]: call-disconnect: failed with Timeout was reached
Jan 21 08:13:12 debian NetworkManager[1609]: <warn>  [1705824792.0637] sup-iface[6b17d7448aff48e7,0,wlan0]: set bridge (null) result: Timeout was reached
Jan 21 08:13:12 debian NetworkManager[1609]: <warn>  [1705824792.0641] sup-iface[6b17d7448aff48e7,0,wlan0]: call-disconnect: failed with Timeout was reached
Jan 21 08:13:12 debian NetworkManager[1609]: <warn>  [1705824792.0643] sup-iface[6b17d7448aff48e7,0,wlan0]: assoc[6c96293a9890d034]: failure to set AP scan mode: Timeout was reached
Jan 21 08:13:12 debian NetworkManager[1609]: <info>  [1705824792.0656] device (wlan0): state change: config -> failed (reason 'supplicant-failed', sys-iface-state: 'managed')
Jan 21 08:13:12 debian NetworkManager[1609]: <info>  [1705824792.0707] manager: NetworkManager state is now DISCONNECTED
Jan 21 08:13:17 debian systemd[1]: systemd-hostnamed.service: Deactivated successfully.
I was able to enter the password manually, no change in behavior.

Code: Select all

user@debian:~$ systemctl status --user
● debian
    State: running
    Units: 154 loaded (incl. loaded aliases)
     Jobs: 0 queued
   Failed: 0 units
    Since: Sun 2024-01-21 08:20:46 UTC; 3min 57s ago
  systemd: 252.19-1~deb12u1
   CGroup: /user.slice/user-1000.slice/user@1000.service
           ├─app.slice
           │ ├─dconf.service
           │ │ └─2315 /usr/libexec/dconf-service
           │ ├─gnome-keyring-daemon.service
           │ │ └─2532 /usr/bin/gnome-keyring-daemon --foreground --components=p>
           │ ├─gpg-agent.service
           │ │ └─2204 /usr/bin/gpg-agent --supervised
           │ ├─tumblerd.service
           │ │ └─2281 /usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd
           │ └─xdg-desktop-portal-gtk.service
           │   └─2224 /usr/libexec/xdg-desktop-portal-gtk
           ├─init.scope
           │ ├─2002 /lib/systemd/systemd --user
           │ └─2003 "(sd-pam)"
           └─session.slice
             ├─at-spi-dbus-bus.service
             │ ├─2165 /usr/libexec/at-spi-bus-launcher
             │ ├─2174 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at>
             │ └─2187 /usr/libexec/at-spi2-registryd --use-gnome-session
             ├─dbus.service
             │ ├─2029 /usr/bin/dbus-daemon --session --address=systemd: --nofor>
             │ ├─2163 /usr/libexec/ibus-portal
             │ ├─2181 /usr/lib/x86_64-linux-gnu/xfce4/xfconf/xfconfd
             │ └─2530 /usr/bin/gnome-keyring-daemon --start --foreground --comp>
             ├─gvfs-daemon.service
             │ ├─2146 /usr/libexec/gvfsd
             │ └─2488 /usr/libexec/gvfsd-trash --spawner :1.10 /org/gtk/gvfs/ex>
             ├─gvfs-metadata.service
             │ └─2487 /usr/libexec/gvfsd-metadata
             ├─gvfs-udisks2-volume-monitor.service
             │ └─2473 /usr/libexec/gvfs-udisks2-volume-monitor
             ├─pulseaudio.service
             │ └─2018 /usr/bin/pulseaudio --daemonize=no --log-target=journal
             ├─xdg-desktop-portal.service
             │ └─2192 /usr/libexec/xdg-desktop-portal
             ├─xdg-document-portal.service
             │ ├─2209 /usr/libexec/xdg-document-portal
             │ └─2221 fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_unmount>
             └─xdg-permission-store.service
               └─2213 /usr/libexec/xdg-permission-store

Code: Select all

user@debian:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 13fe:3600 Phison Electronics Corp. flash drive (4GB, EMTEC)
Bus 001 Device 003: ID 258a:1015 SINO WEALTH USB Composite Device
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Many thanks for the help so far, by the way!
Last edited by JohnWasRight on 2024-01-21 07:01, edited 1 time in total.

User avatar
FreewheelinFrank
Global Moderator
Global Moderator
Posts: 2140
Joined: 2010-06-07 16:59
Has thanked: 38 times
Been thanked: 233 times

Re: WiFi channels visible but connection impossible on Debian 12 MATE and XFCE

#9 Post by FreewheelinFrank »

You can try deleting the connection profile and creating a new one:

You can also try disabling MAC address randomization:
https://wiki.archlinux.org/title/Networ ... t_provided

User avatar
bbbhltz
Posts: 168
Joined: 2024-01-10 14:53
Location: Normandy
XMMP/Jabber: bbbhltz@mailbox.org
Has thanked: 52 times
Been thanked: 34 times

Re: WiFi channels visible but connection impossible on Debian 12 MATE and XFCE

#10 Post by bbbhltz »

JohnWasRight wrote: 2024-01-21 06:40
This one generated a "command not found":

Code: Select all

dhclient -r wlan0 && dhclient wlan0
it needs to be run as root. But I don't think it would help. I like the solution linked by @FreewheelinFrank. Looks just like your problem.
bbbhltz
longtime desktop Linux user; eternal newbie

JohnWasRight
Posts: 8
Joined: 2024-01-20 13:07

Re: WiFi channels visible but connection impossible on Debian 12 MATE and XFCE

#11 Post by JohnWasRight »

Sadly neither of these (deleting/recreating the profile and disabling MAC randomization) helped

User avatar
bbbhltz
Posts: 168
Joined: 2024-01-10 14:53
Location: Normandy
XMMP/Jabber: bbbhltz@mailbox.org
Has thanked: 52 times
Been thanked: 34 times

Re: WiFi channels visible but connection impossible on Debian 12 MATE and XFCE

#12 Post by bbbhltz »

Are you restarting the computer or NetworkManager after these attempts?

Last thing I have which is similar to the other suggestions:

1. Restart NetworkManager

Code: Select all

$ sudo systemctl restart NetworkManager
2. Delete the connection

Code: Select all

$ nmcli con delete Wastewlan
3. Add a new connection

Code: Select all

$ nmcli dev wifi connect Wastewlan password <password>
4. Restart again
bbbhltz
longtime desktop Linux user; eternal newbie

JohnWasRight
Posts: 8
Joined: 2024-01-20 13:07

Re: WiFi channels visible but connection impossible on Debian 12 MATE and XFCE

#13 Post by JohnWasRight »

I will try these too and then I'll probably have to give up (for now). I also attempted to connect to a network with no security, but it didn't work either.

Thanks again for the effort. I'll come back with any info if I happen to find a solution.

Aki
Global Moderator
Global Moderator
Posts: 3086
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 76 times
Been thanked: 418 times

Re: WiFi channels visible but connection impossible on Debian 12 MATE and XFCE

#14 Post by Aki »

You might check the configuration of the regional setting for your wireless device to match the ones of the hotspot.
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

JohnWasRight
Posts: 8
Joined: 2024-01-20 13:07

Re: WiFi channels visible but connection impossible on Debian 12 MATE and XFCE

#15 Post by JohnWasRight »

The earlier suggestions didn't work either. I have a question though: I thought of tethering my phone through USB and it successfully shared connectivity, showing up as ethernet. Is there anything I can do, having internet access, to further troubleshoot the wifi issue? Any different network manager, driver, or something of the sort?

User avatar
FreewheelinFrank
Global Moderator
Global Moderator
Posts: 2140
Joined: 2010-06-07 16:59
Has thanked: 38 times
Been thanked: 233 times

Re: WiFi channels visible but connection impossible on Debian 12 MATE and XFCE

#16 Post by FreewheelinFrank »

Output of the following might be useful, as it will show driver and firmware in use (you may need to install package lshw).

Code: Select all

# lshw -C network
Also check

Code: Select all

# lsmod | grep <driver name>
If you could do that on a working live image too (you mentioned Puppy Bookworm and Bodhi) and something is different, that might give us a clue.

JohnWasRight
Posts: 8
Joined: 2024-01-20 13:07

Re: WiFi channels visible but connection impossible on Debian 12 MATE and XFCE

#17 Post by JohnWasRight »

Here are the outputs. First, the connection using the USB tethering (IP redacted). Notice how lsmod returns empty. Note that trying on Bodhi had the exact same output (including an empty lsmod) but it worked fine:

Code: Select all

user@debian:~$ sudo lshw -C network
  *-network:0               
       description: Wireless interface
       physical id: 12
       bus info: mmc@0:0001:1
       logical name: wlan0
       serial: 34:c3:d2:6e:80:53
       capabilities: ethernet physical wireless
       configuration: broadcast=yes driver=rtl8723bs driverversion=6.1.0-15-amd64 multicast=yes wireless=IEEE 802.11
  *-network:1
       description: Ethernet interface
       physical id: 13
       bus info: usb@1:2.1
       logical name: enxfae57f76cc21
       serial: fa:e5:7f:76:cc:21
       capabilities: ethernet physical
       configuration: autonegotiation=off broadcast=yes driver=rndis_host driverversion=6.1.0-15-amd64 duplex=half firmware=RNDIS device ip=XX.XX.XXX.XX link=yes multicast=yes port=twisted pair
user@debian:~$ lsmod | grep rtl8723bs
user@debian:~$ 
At this point I had another idea: I remembered a USB WiFi dongle I have - it's ancient - which I plugged and, lo and behold, it worked:

Code: Select all

user@debian:~$ sudo lshw -C network
  *-network:0               
       description: Wireless interface
       physical id: 12
       bus info: mmc@0:0001:1
       logical name: wlan0
       serial: 34:c3:d2:6e:80:53
       capabilities: ethernet physical wireless
       configuration: broadcast=yes driver=rtl8723bs driverversion=6.1.0-15-amd64 multicast=yes wireless=IEEE 802.11
  *-network:1
       description: Wireless interface
       physical id: 13
       bus info: usb@1:2.1
       logical name: wlx00b08c415466
       serial: 00:b0:8c:41:54:66
       capabilities: ethernet physical wireless
       configuration: broadcast=yes driver=rt2800usb driverversion=6.1.0-15-amd64 firmware=0.36 ip=XX.XX.XX.XXX link=yes multicast=yes wireless=IEEE 802.11
user@debian:~$ sudo lsmod | grep rt2800usb
rt2800usb              28672  0
rt2x00usb              28672  1 rt2800usb
rt2800lib             176128  1 rt2800usb
rt2x00lib              77824  3 rt2800usb,rt2x00usb,rt2800lib
usbcore               348160  10 xhci_hcd,rt2800usb,usbnet,usbhid,usb_storage,rndis_host,xhci_pci,cdc_ether,uas,rt2x00usb
user@debian:~$ 

User avatar
fabien
Forum Helper
Forum Helper
Posts: 741
Joined: 2019-12-03 12:51
Location: Anarres (Toulouse, France actually)
Has thanked: 67 times
Been thanked: 173 times

Re: WiFi channels visible but connection impossible on Debian 12 MATE and XFCE

#18 Post by fabien »

JohnWasRight wrote: 2024-01-22 06:31

Code: Select all

       configuration: broadcast=yes driver=rtl8723bs driverversion=6.1.0-15-amd64 multicast=yes wireless=IEEE 802.11
You are using the 6.1.0-15 kernel which is known to have a WIFI bug. This kernel is the one in the stable installer, so if you install without the network enabled this is the one in use.
You should try the 6.1.0-17 from bookworm-security. Add something like this to your sources.list if it's not already the case:

Code: Select all

deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
ImageShare your Debian SCRIPTS
There will be neither barrier nor walls, neither official nor guard, there will be no more desert and the entire world will become a garden. — Anacharsis Cloots

JohnWasRight
Posts: 8
Joined: 2024-01-20 13:07

Re: WiFi channels visible but connection impossible on Debian 12 MATE and XFCE

#19 Post by JohnWasRight »

OK, my plan was to try a live USB before installing it. To the best of my understanding, it's not possible to install a different kernel to a live USB system (since it requires rebooting), so there's no way for me to test this. I'll mark this as resolved so we can get closure, and I'll have to let this go for now. Thanks to everyone for the help

Post Reply