Hi, new here
Until half a year ago I hadn't used debian for over 20 years. I was using
Kubuntu in the mean time. Then I installed Trixie, and today I upgraded to
testing to get a newer KDE Plasma.
It took a couple of hours on my old laptop.
The system seems to be running fine, but the wifi connection is *very* flaky.
It connects and disconnects constantly.
I know next to nothing about networking, so I have no idea how to find out
what's why.
How do I find relevant info to debug this?
This is the only have:
lspci | grep -i network
07:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network
Adapter (rev 01)
Both 'firmware-atheros' and 'firmware-misc-nonfree' are installed.
And:
When the connection is down:
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp8s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state
DOWN group default qlen 1000
link/ether 20:25:64:c3:4c:10 brd ff:ff:ff:ff:ff:ff
altname enx202564c34c10
3: wlp7s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state
DOWN group default qlen 1000
link/ether a2:31:a2:ff:20:7c brd ff:ff:ff:ff:ff:ff permaddr
28:e3:47:f1:f1:e0
altname wlx28e347f1f1e0
This when it's up:
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp8s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state
DOWN group default qlen 1000
link/ether 20:25:64:c3:4c:10 brd ff:ff:ff:ff:ff:ff
altname enx202564c34c10
3: wlp7s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
group default qlen 1000
link/ether 28:e3:47:f1:f1:e0 brd ff:ff:ff:ff:ff:ff
altname wlx28e347f1f1e0
inet 192.168.161.20/24 brd 192.168.161.255 scope global dynamic
noprefixroute wlp7s0
valid_lft 3596sec preferred_lft 3596sec
inet6 fe80::efb5:5c99:7773:59f/64 scope link noprefixroute
valid_lft forever preferred_lft forever
sudo systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled;
preset: enabled)
Active: active (running) since Sun 2026-10-04 14:55:44 CEST; 1h 22min ago
Invocation: b225c6ab95a04f0d92064651d731eadf
Docs: man:NetworkManager(8)
Main PID: 849 (NetworkManager)
Tasks: 4 (limit: 9206)
Memory: 10.3M (peak: 11M)
CPU: 24.034s
CGroup: /system.slice/NetworkManager.service
└─849 /usr/sbin/NetworkManager --no-daemon
Oct 04 16:17:47 akd-laptop NetworkManager[849]: <info> [1791123467.9661] dhcp4
(wlp7s0): activation: beginning tr>
Oct 04 16:17:47 akd-laptop NetworkManager[849]: <info> [1791123467.9914] dhcp4
(wlp7s0): state changed new lease,>
Oct 04 16:17:48 akd-laptop NetworkManager[849]: <info> [1791123468.1403] dhcp4
(wlp7s0): state changed new lease,>
Oct 04 16:17:48 akd-laptop NetworkManager[849]: <info> [1791123468.1421]
policy: set 'Tanghus mobil' (wlp7s0) as >
Oct 04 16:17:48 akd-laptop NetworkManager[849]: <info> [1791123468.2935]
device (wlp7s0): state change: ip-config>
Oct 04 16:17:48 akd-laptop NetworkManager[849]: <info> [1791123468.3317]
device (wlp7s0): state change: ip-check >
Oct 04 16:17:48 akd-laptop NetworkManager[849]: <info> [1791123468.3325]
device (wlp7s0): state change: secondari>
Oct 04 16:17:48 akd-laptop NetworkManager[849]: <info> [1791123468.3336]
manager: NetworkManager state is now CON>
Oct 04 16:17:48 akd-laptop NetworkManager[849]: <info> [1791123468.3341]
device (wlp7s0): Activation: successful,>
Oct 04 16:17:48 akd-laptop NetworkManager[849]: <info> [1791123468.3349]
manager: NetworkManager state is now CON>
I'm away from home so I use my phone as hotspot. It didn't give me any problems
before I updated.
Best regards
Thomas Tanghus
Best Regards
Thomas Tanghus
---
Please consider the environmental impact before using so-called "AI"
functionality to reply to this email.
Plus it's super annoying.
