Hello everyone.
I've been using my D-Link DWA-160 network adapter for around two years without any issue for a couple of years. Some weeks ago however, it
started misbehaving.
After I use it as usual for a seemingly random amount of time (but see below), spanning from a few minutes to several hours, I suddenly get disconnected from wifi. After that, if I try to connect again with nmcli
my computer freezes and I can only force it off. However, if I unplug
the adapter, plug it in again and then reconnect with nmcli everything
works fine - until I get disconnected again.
At first I didn't bother to even look for a solution, since this
happened only once in a few days. However, now it happens several times
a day, and most often when I reach high download speeds. Anything around
2 MiB/s for more than a handful of seconds seems to be a granted
trigger.
I couldn't find any useful information online and I know nothing about
wifi hardware or software. Can anyone help troubleshooting this?
--
Ceppo
https://wiki.debian.org/Ceppo
Please, encrypt our messages with the key at the link above and send me yours.
Is there anything you have changed to the system lately?
Is there another adapter you can use and try and recreate the issue?-
At first I didn't bother to even look for a solution, since this
happened only once in a few days. However, now it happens several times
a day, and most often when I reach high download speeds. Anything around
2 MiB/s for more than a handful of seconds seems to be a granted
trigger.
On 2/5/25 10:16, Ceppo wrote:
At first I didn't bother to even look for a solution, since this
happened only once in a few days. However, now it happens several
times a day, and most often when I reach high download speeds.
Anything around 2 MiB/s for more than a handful of seconds seems to
be a granted trigger.
If you unplug-replug faster does it crash sooner?
Conversely, if you stick it in the freezer does it last longer before crashing?
Also, is this USB or a card? If USB, does it have a case you can
remove?
My hypothesis is that some component is overheating based on its
failures being related to throughput.
On Wed, Feb 05, 2025 at 12:17:40PM -0500, eben@gmx.us wrote:
On 2/5/25 10:16, Ceppo wrote:
Also, is this USB or a card? If USB, does it have a case you can
remove?
It's USB, and I think I can't remove the outer plastic case without
breaking it. See this [image].
My hypothesis is that some component is overheating based on its
failures being related to throughput.
This is an interesting idea, but if this was the reason I couldn't
imagine why the issue only arised after ~2 years of use without any significant change in my network activity habits. E.g. I use to download
huge and higly available files throught bittorent very often, so 2 MiB/s
or more is not an unusual throughput.
Thermal compound (if there is any) dried out?
If you can trigger a failure by heating the device with say a hair
dryer, that's supporting evidence. But yeah, it might be some
software. Or some component aging and changing its behavior slightly
out of spec.
On Thu, Feb 06, 2025 at 09:36:28AM -0500, eben@gmx.us wrote:
Thermal compound (if there is any) dried out?
There's none. At least not visible, or replaceable.
If you can trigger a failure by heating the device with say a hair
dryer, that's supporting evidence. But yeah, it might be some
software. Or some component aging and changing its behavior slightly
out of spec.
I performed the hair dryer test, but couldn't trigger the disconnection.
I kept the adapter warm, to a temperature higher than what I get during regular use, for around 15 mins. Under heavy load this is long enough
for 2-4 disconnections.
Welp, there goes my theory. Thanks for checking. Ah well.
Something might change outside your machine: you installed another
router, more devices have been added to your wifi network, including
ones actively using multicast (IPTV), some of your neighbors installed
new access point working with higher power on the same channel...
I have seen various recipes, but I have not tried them, so unsure
concerning real effect: explicitly disable 802.11a and 802.11b low
bitrate modes, try fixed frequency instead of autoselect, disable dual frequency channel mode on 2.4GHz band.
I assume, you have tried backports kernel and latest firmware.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (0 / 16) |
Uptime: | 161:58:13 |
Calls: | 10,385 |
Calls today: | 2 |
Files: | 14,057 |
Messages: | 6,416,500 |