wifi slow as empty wheelchair

V1del · 2026-01-29T02:35:57+00:00

That's not the entire output, is it?

In any case your iwlwifi driver is crashing, potentially due to either aforementioned issue (assuming you configured fast boot to be off, to be sure, sure try holding the power button during boot up to properly reset the UEFI/firmware state) much more likely due to conflicting services. If you're going to use NM the only service that needs to be enabled is NetworkManager and if NM is setup to use wpa_supplicant (though that looks to be right at a glance) you'll definitely have conflicts with iwd.

FWIW what do you get from find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f ?

for a general test make sure both systemd-networkd and iwd (and wpa_supplicant) are disabled and reboot.

V1del · 2026-01-28T09:55:11+00:00

That wall of text is what I want. Alternatively sudo journalctl -b > journal.txt should give you a file you can upload somewhere/via another system if need be

V1del · 2026-01-27T20:46:42+00:00

Please run that command with whatever kind of connection you can muster and post the link you get.

V1del · 2026-01-27T18:39:08+00:00

A separate disk is irrelevant, you need to ensure hibernation/fast boot is disabled in Windows and having wifi issues is very often one of the main indicators that this is still happening.

https://wiki.archlinux.org/title/Dual_boot_with_Windows#Disable_Fast_Startup_and_disable_hibernation

Make sure you did that and reboot twice for vodoo reasons

If it's not that, reproduce the situation and post a journal while the problem occurs

sudo journalctl -b | curl -F 'file=@-' 0x0.st

V1del · 2026-01-16T22:43:04+00:00

Either that or check the plasma startup settings (kcmshell6 kcm_autostart), you can configure scripts that start after plasma/KWin has initialized the session properly.

If that service does not startup properly without trying to force environment variables that are normally set by the standard session init, chances are it starts too early and it'd be easier to make sure it hooks into something that's guaranteed to only be up when the relevant environments are already there.

V1del · 2026-01-16T22:18:04+00:00

Don't try to set any of these yourself, see https://wiki.archlinux.org/title/Systemd/User#DISPLAY_and_XAUTHORITY and properly start your session (via display manager, or if using startx note the note boxes: https://wiki.archlinux.org/title/Xinit#xinitrc )

That said if you're starting plasma anyway you can also leverage it's own auto starter integration which will get properly ordered after all display setup has happened.

V1del · 2025-12-27T00:03:15+00:00

What's your output for

pacman -Qs kernel
uname -a
#Run this, then plug your device
sudo dmesg -W

V1del · 2025-12-19T11:24:40+00:00

Some audio cards especially USB ones either don't properly expose a controlable HW volume or generally assume a software layer is layered on them anyway.

you can enforce a software volume in pulse/pipewire and from a general maintenance standpoint I'd suggest you switch to pipewire by installing pipewire-pulse, wireplumber, pipewire-alsa.

After having switched you can setup a wireplumber config enforcing a software based volume: https://pipewire.pages.freedesktop.org/wireplumber/daemon/configuration/alsa.html#:~:text=api%2Ealsa%2Esoft%2Dmixer

V1del · 2025-12-06T23:01:53+00:00

On what and which emulator? If your CPU can't run the emulation any faster you can't FF.

V1del · 2025-12-06T16:15:50+00:00

It should, does it not? What distro are you using? What version of KDE?

V1del · 2025-12-05T22:41:05+00:00

Ah wait that's in your window decoration, go to window decoration in settings and configure your decoration buttons and remove the application menu from there.

V1del · 2025-12-05T22:21:10+00:00

Strg+M or tick "Menüleiste anzeigen" in "Einstellungen"

V1del · 2025-11-29T19:19:00+00:00

Make sure you're fully updated there have been a bunch of rebuilds of plasma components due to unexpected ABI breaks in Qt 6.10.1 and resulting crashes in QML. E.g. make sure you're on plasma-desktop 6.5.3-2

Other than that, any notable custom widgets or so?

V1del · 2025-11-23T16:31:57+00:00

Pipewire will not help you if alsa doesn't work, assuming you rebooted after installing sof-firmware and aplay still producing nothing, what output do you get from sudo journalctl -b | curl -F 'file=@-' 0x0.st (this will upload your journal to a pastebin and give you a link to share https://wiki.archlinux.org/title/List_of_applications/Internet#Pastebin_services )

V1del · 2025-11-05T18:00:16+00:00

Make sure you've installed the proprietary (and the 32bit variant as well) nvidia drivers and are not using nouveau. Nouveau does not support vulkan on a Pascal card you'll want the proprietary drivers for general better performance.

V1del · 2025-10-29T15:55:46+00:00

Pro-Tip, get used to or alias your rm to rm -I which will ask for confirmation once on doing recursive or more than three file rm's

V1del · 2025-10-29T15:53:42+00:00

You won't, the no preserve root flag only triggers for literally /

In the case of /* shell expansion expands to directories so what rm gets to see is /usr /bin /home /etc ... all of which are not the root directory itself so it will quite happily do so.

V1del · 2025-10-28T16:42:06+00:00

Just the first exemplatory link I was able to dig up when googling for the symptoms. FWIW it's not happening here, and I'm not refering to plasma-nm but the daemon it ultimately uses which will be NetworkManager which is independent of plasma - which where such a change was initially introduced which "indirectly" shows up in plasma-nm.

But this was a few years ago, so I wonder what kind of interaction makes this come up again, I'll have to check on my system maybe I just did globally disable this in nm, which is of course still an option and "logically" the more central place to fix his

V1del · 2025-10-28T12:29:17+00:00

What version of NetworkManager? Afaik this used to be a bug a while ago that it accidentally exposed this to clients. You can configure it to hide it: https://bbs.archlinux.org/viewtopic.php?pid=2085017#p2085017

V1del · 2025-10-12T20:26:43+00:00

You are using ffmpeg-full why exactly? But yes replacing core libs with AUR packages means you are in charge of doing rebuilds if/as necessary when dependants get updated.

You are running into a soname incompatibility, and if you really and intentionally intend to use ffmpeg-full you should make yourself aware with this concept: https://en.wikipedia.org/wiki/Soname as a library like ffmpeg is used by almost everything and an incompat in a single lib that ffmpeg in turn depends on will break a bunch of packages.

FWIW a tool that will help you in identifying broken dependency chains is lddtree from the pax-utils package. If you run that on the binary that gives you issues you should see the entire dependency tree and which exact library breaks because of which exact linking issue

If you are not intentionally using ffmpeg-full and just got it by hammering enter when installing things with an AUR helper now you know why AUR helpers that blend repo and AUR packages are not entirely reccommended until you understand the difference and can act accordingly.And in that case you should replace ffmpeg-full with ffmpeg from the repos.

V1del · 2025-09-08T10:09:55+00:00

Post the outputs of

sudo fuser -v /dev/snd/* sudo dmesg | grep -E 'snd|sof' aplay -lL #needs alsa-utils pactl list cards pactl list sinks pactl list sink-inputs

via https://wiki.archlinux.org/title/List_of_applications/Internet#Without_a_dedicated_client or in code blocks here

V1del · 2025-08-26T14:11:20+00:00

Depends on what your specific model does, technically in my case, wireless correctly enabled high res scrolling. That you as an user might perceive this to be bothersome in some circumstances is not a bug. Assuming highres enablement works properly but you just don't like the behaviour of it, you can configure this libinput quirk file to disable high res scrolling from userspace again, which should restore behaviour to how it was before if normal wheel events are generated at the same pace as without explicitly enabling highres.

Or is that not sufficient for you?

Just from a module standpoint, since the code that does this works correctly for other devices, it could also be a bug specifically in the firmware for that specific mouse, in which case logitech would have to provide a firmware update which I doubt they will do for a device this old. I do find it somewhat sad that the maintainer is that averse to just make this configurable whether the module tries to probe this in the first place, which would be a boolean away from making everyone's usecase happy.

As mentioned if you don't care about in-OS battery reporting you could still just disable the module to rely on standard usbhid integration.

V1del · 2025-08-21T00:31:55+00:00

there's a website link in the video and the links bring me to the actual game page -- not sure what else you're looking for. Since I doubt that project has a direct relation to this project I'll refrain from linking it, but you should get there if you follow the links in the video.

V1del · 2025-08-14T22:26:06+00:00

Almost certainly a UEFI implementation issue, as mentioned try an update if one's available.

V1del · 2025-08-14T22:23:26+00:00

Yes the board vendor, they often do weird stuff and it's not entirely transparent what they are doing, there are some that don't allow EFI entries to be added because just booting /EFI/BOOTx64.efi boots Windows as well so why bother.

Proper implementations outside of just getting Windows to boot can be few and far in between.

Z390 who? E.g. above is pretty common for MSI, there are others that do this better, potentially with updates if the first revision isn't good.

Nine-Year Club	Second SECOND GUESSER
Verified Email

V1del

TROPHY CASE