The Linux Thread - The Autist's OS of Choice

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
Despite everybody recommending amd on linux amd is terrible. I regret buying my amd gpu. I have a lot of gpu driver issues, on both x11 and wayland (similar to what you posted). I unironically had far less issues with nvidia. My computer is unusable unless I enabled software cursor, otherwise the cursor will randomly lag. This is also related to dynamic power. Amd drivers are terrible.
I was thinking about finally buying a dedicated GPU for my computer. Reading this, it's gonna be harder than I thought. NVIDIA has an issue with not working with system RAM properly which was discussed earlier in the thread and all the budget cards it offers have, comparatively, very little VRAM. Seems like it's suffering no matter what you pick, unless you shell out the big bucks for something top-of-the-line (not ideal).
 
I was thinking about finally buying a dedicated GPU for my computer. Reading this, it's gonna be harder than I thought. NVIDIA has an issue with not working with system RAM properly which was discussed earlier in the thread and all the budget cards it offers have, comparatively, very little VRAM. Seems like it's suffering no matter what you pick, unless you shell out the big bucks for something top-of-the-line (not ideal).
This is anecdotal of course and I know it is a real problem, but you don't really tend to hit that ceiling ever in my experience on NVIDIA. I have used both a GTX 1660 SUPER and a RTX 4070 on Linux, I only use Linux to do all my computing tasks and I use it for hours at a time. I perform heavy tasks on it like gaming and cuda rendering, I also play music and videos on a browser while doing these things. The only time was when I was trying to run an AI model that was too demanding and that was on the GTX 1660 SUPER, and even then it just told me "hey idiot, your VRAM is too low for this" and then exited cleanly. I say try it but go with NVIDIA, you can get a cheapish modern card from a 70 line one and most likely still be fine. - If you run into problems still you might get some luck with doing something like offloading tasks to the iGPU which I guess would serve to "share" your VRAM by performing some tasks reserved for it over the dGPU. I have never had to do this personally, but again that is anecdotal. Some have had worse luck with this tbf however it's not really super widespread, I only learned of this NVIDIA flaw from that post in this thread, and that was months of using NVIDIA being none the wiser.

Unrelated, but the first version of this flag has to be one of the best ones I have ever seen:

1757827211350.webp

fromsbctl(src)
 
I agree with this in general, dedicated AMDGPUs are awfully made. I oddly have had better luck with the integrated AMD graphics on laptops. My laptop with an old Radeon card (that is able to use the amdgpu driver) has none of those problems, which is both interesting and kind of funny.
AMD is treated as the budget brand (which in GPUs isn’t entirely inaccurate), so the OEMs cut every corner they can.
 
I was thinking about finally buying a dedicated GPU for my computer. Reading this, it's gonna be harder than I thought. NVIDIA has an issue with not working with system RAM properly which was discussed earlier in the thread and all the budget cards it offers have, comparatively, very little VRAM. Seems like it's suffering no matter what you pick, unless you shell out the big bucks for something top-of-the-line (not ideal).
I think you can probably be fine going amd too, just do research on the specific gpu you are buying, and the drivers you will be using with it. I feel like you could run into issues with either brand potentially.
 
AMD is treated as the budget brand (which in GPUs isn’t entirely inaccurate), so the OEMs cut every corner they can.
I've never really used premium brand NVIDIA cards though, it's both a card I got used like all my NVIDIA cards and a "mid tier" (according to the pundits) one. We know NVIDIA does some corner cutting on their less premium cards, at the very least they nerf the VRAM, yet I've never felt any problems from whatever they do to make more profits. Why? I have no idea. Maybe NVIDIA just have better build practices for their entire line up or perhaps they have better people working on them? I am not even going to pretend to know the differences between AMDGPU and NVIDIA's architectures, so I have no clue personally. The issues @dec05eba and others around the web are describing with AMDGPU on both Linux and esp Windows sounds like a nightmare to deal with and I can honestly say I've never had any issues like that at all w/ NVIDIA on any system. And some of the people with issues have like the top of the line cards too. The budget option might have been tempting, but you can get used NVIDIA for cheaper than a lot of AMD stuff in my area and/or work. Either I scavenge off a work colleague's* comp if I can or I get one from a gamer who is feeling FOMO for a new generation. And I don't need to change them for a long time either, my last card I used for well over 5 years, it was a mid tier too but it still chugs along just fine.

But tbf I could be wrong, it's been years since I tried AMDGPUs and it was on Windows, however I don't think I will try until they get something equivalent (both as a function and in functionality) to cuda which IIRC they still don't have. But to balance it out a bit, it also isn't all sunshine and rainbows with NVIDIA on Linux ofc. Suspend and hibernation seems to still be a coin toss but I wouldn't know for sure since I don't use either of those things. I just shut off my computer instead, SSDs are so fast now and boot times were the only reason I personally ever suspended or hibernated in the past. However if you need either of them then that is a consistent issue I see. There's also some fighting of the driver at times, like having to add some stuff to prevent nouveau and simpledrm from loading. Signing for SecureBoot is also irksome for non supported distros like Arch where you either have to import a signed shim if you don't want to compile a kernel every update, and there's still one minor problem with GSP on Wayland, but that's Wayland. None of these things are dealbreakers though, just slight annoyances.
 
Last edited:
Does anyone know why sometimes when I launch a video game the framerate locks to the 10-15 no matter if it is in fullscreen or not? The only solution I've found is to go in the display settings on KDE or Gnome to change the frequency from 200 to 120 then back to 200.
I'm on Arch with a AMD CPU and GPU, and this happens on both KDE and Gnome.
 
I was thinking about finally buying a dedicated GPU for my computer. Reading this, it's gonna be harder than I thought. NVIDIA has an issue with not working with system RAM properly which was discussed earlier in the thread and all the budget cards it offers have, comparatively, very little VRAM. Seems like it's suffering no matter what you pick, unless you shell out the big bucks for something top-of-the-line (not ideal).
For what it's worth, I've never had any serious problems with AMD on Linux. The only thing I've encountered is that Xorg will crash eventually if the monitor's off for more than a few hours.
 
yo im rocking lxqt right now and the config resets every time i update the kernel (i use arch btw) or install/uninstall things like tlp

but it only resets the kb/mouse config, so i just have to reset the kb layout and set up the touchpad settings again

so what do i do in order to not need to do that?
 
yo im rocking lxqt right now and the config resets every time i update the kernel (i use arch btw) or install/uninstall things like tlp

but it only resets the kb/mouse config, so i just have to reset the kb layout and set up the touchpad settings again

so what do i do in order to not need to do that?
Make a config.d/ file?
 
yo im rocking lxqt right now and the config resets every time i update the kernel (i use arch btw) or install/uninstall things like tlp

but it only resets the kb/mouse config, so i just have to reset the kb layout and set up the touchpad settings again

so what do i do in order to not need to do that?
Is this a config for xorg? Or something else. If it's xorg, like they suggested above me. But put it in. /etc/X11/xorg.conf.d/


Lunduke is doing more Kirk posting.
 
Last edited:
Make a config.d/ file?
Is this a config for xorg? Or something else. If it's xorg, like they suggested above me. But put it in. /etc/X11/xorg.conf.d/
thats the thing
i dont know where to put this in, i dont know what the files are, i dont know what settings these are, i cant find anything on google, ive checked out the code for the lxqt input settings and i still dont know anythign

i use the lxqt-config-input binary to change those settings and i cant find anything related to lxqt in /etc/
 
thats the thing
i dont know where to put this in, i dont know what the files are, i dont know what settings these are, i cant find anything on google, ive checked out the code for the lxqt input settings and i still dont know anythign

i use the lxqt-config-input binary to change those settings and i cant find anything related to lxqt in /etc/
Ok. Assuming you are running it on xorg. Maybe check to see if there are files being created or changed in the /etc/x11 directory when you change settings.

If not it might be something in .config which shouldn't be effected on updates. But idk really. It would make sense if the lxqt is editing some xorg config file that is getting overwritten on updates, or might even be competing with some other program.
 
Ok. Assuming you are running it on xorg. Maybe check to see if there are files being created or changed in the /etc/x11 directory when you change settings.

If not it might be something in .config which shouldn't be effected on updates. But idk really. It would make sense if the lxqt is editing some xorg config file that is getting overwritten on updates, or might even be competing with some other program.
okay...
on debian wiki it says shit should be in /etc/xdg/lxqt.conf i dont have that file

but shit is in ~/.config/lxqt/
for some reason these settings are set in session.conf and not lxqt.conf or lxqt-config-input.conf

so just in case i copypasted shit from session.conf to these files, and we will have to wait until something updates
 
okay...
on debian wiki it says shit should be in /etc/xdg/lxqt.conf i dont have that file

but shit is in ~/.config/lxqt/
for some reason these settings are set in session.conf and not lxqt.conf or lxqt-config-input.conf

so just in case i copypasted shit from session.conf to these files, and we will have to wait until something updates
Ok. Yeah I guess just wait and see.

Something I would try. Is maybe move that other file out of that directory. And see if the settings still stay with the new session.conf file. Obviously restart the session, see if things are still working properly, and move the old file back if you need to. Or maybe delete it, if things are working still
 
Ok. Yeah I guess just wait and see.

Something I would try. Is maybe move that other file out of that directory. And see if the settings still stay with the new session.conf file. Obviously restart the session, see if things are still working properly, and move the old file back if you need to. Or maybe delete it, if things are working still
okay, ive reinstalled tlp, because i know this triggers the config reload

i noticed that it doesn't wipe the contents of session.conf, but the settings dont actually take effect, the tap to click doesn't work, the kb is set to us, and lxqt-config-input reflects that
but it starts working again after a restart
i dunno whats going on
 
Does anyone know why sometimes when I launch a video game the framerate locks to the 10-15 no matter if it is in fullscreen or not? The only solution I've found is to go in the display settings on KDE or Gnome to change the frequency from 200 to 120 then back to 200.
I'm on Arch with a AMD CPU and GPU, and this happens on both KDE and Gnome.
You could try "echo 1 | sudo tee /sys/class/drm/card0/device/pp_power_profile_mode"
If you're running on UEFI you could try to enable Resizable BAR in EFI. I always get framerate problems without this. You could verify with "sudo dmesg | grep BAR", it should say something like "[drm] Detected VRAM RAM=8176M, BAR=8192M". If it's not enabled, you'll see BAR=256MB.
 
okay...
on debian wiki it says shit should be in /etc/xdg/lxqt.conf i dont have that file

but shit is in ~/.config/lxqt/
for some reason these settings are set in session.conf and not lxqt.conf or lxqt-config-input.conf

so just in case i copypasted shit from session.conf to these files, and we will have to wait until something updates
If the config settings are written to session.config, they probably are supposed to be written to session.config, not those other files.

Arch wiki suggests that the system wide session.config will be at: /usr/share/lxqt/session.conf

You could try seeing if there are settings that seem like they could be related to the input settings that exist in /usr/share/lxqt/session.conf but not in ~/.config/lxqt/session.config , and adding them manually to the latter- as it may simply be that LXQT is not handling the 'merging' of those settings files properly.

If you were on a Debian-based distribution that would explicitly prompt you to merge/keep/drop any manual changes to system config files when running an update that would replace them, I would suggest that you push your user-level changes into the system config file to see if that worked... but as I understand Arch doesn't do this and leaves you to manually merge in any changes to an updated system config file, it would be better to avoid that if at all possible.
 
If the config settings are written to session.config, they probably are supposed to be written to session.config, not those other files.

Arch wiki suggests that the system wide session.config will be at: /usr/share/lxqt/session.conf

You could try seeing if there are settings that seem like they could be related to the input settings that exist in /usr/share/lxqt/session.conf but not in ~/.config/lxqt/session.config , and adding them manually to the latter- as it may simply be that LXQT is not handling the 'merging' of those settings files properly.

If you were on a Debian-based distribution that would explicitly prompt you to merge/keep/drop any manual changes to system config files when running an update that would replace them, I would suggest that you push your user-level changes into the system config file to see if that worked... but as I understand Arch doesn't do this and leaves you to manually merge in any changes to an updated system config file, it would be better to avoid that if at all possible.
session.conf isnt overwritten
just in case i tried copypasting the relevant settings to the systemwide session.conf, and there they aren't overwritten either, the settings are just defaulted in RAM
also this might be a hint idk
1757884849636.webp
 
Is there like a diff detect program that scans your entire computer and tells you all files that are different after each scan? It would be a slow process though
 
Back
Top Bottom