this post was submitted on 16 Dec 2024
76 points (90.4% liked)
Linux
49059 readers
1015 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Same here. I'm using CorrCTRL for my 6800XT and the VRAM OC is not working properly, will give LACT a try
Chances are that it doesn't work there either. What actually does the OC is the kernel; the GUIs merely write the desired values into the correct files in
/sys
.I've just got to try it and you're right. VRAM OC is also broken with LACT though at first it seemed like it worked and I even managed one full bebchmark run in CP2077 but my PC started heavily artifacting and crashed on 2nd run.
Well then it sounds like it works just fine but your chosen value isn't stable.
I can do 2150MHz fast timings on Windows (2000MHz is default). But on Linux even +1MHz is unstable with CoreCTRL and anything above +2MHz is unstable with LACT
There cannot be differences between CoreCTRL and LACT; they use the exact same kernel interfaces.
Your issue is therefore also not connected to any of these GUIs but how the kernel applies your policies.
I'd recommend you try to reproduce the issue using just the raw kernel files and report the issue upstream: https://gitlab.freedesktop.org/drm/amd/-/issues/