Moin! Sag mal, kennst DU dich mit amd treibern aus und kannst mir erzählen was das für ein Fehler ist?
#opensuse #fedora #dmesg #amd #amdgpu #amddrivers
Hey! Tell me, do you know anything about AMD drivers and can you tell me what the error is?
Update: Es hat mit einem displayport feature zu tuen, jetzt gerade habe ich nur einen Bildschirm über hdmi angeschlossen und es geht. Leider scheint das VGA interface meines PCs auch über displayport zu laufen...
After a recent update, when I boot NixOS the screen goes black just before the login screen. I've rolled back to the last generation that worked, but I'd really like to actually fix the issue. This seems to be the relevant error message, so apparently an issue with the AMD GPU driver:
kernel: [drm:dc_dmub_srv_cmd_run_list [amdgpu]] *ERROR* Error queueing DMUB command: status=2
Any ideas?
Arg. issues with losing signal with the new monitor. might maybe be power supply issues causing the #AMDGPU driver to crash? Or it crashes after the system loses the connection to the monitor? Supposedly (according to #MicroCenter folk) a better monitor will fix it. Seems unlikely, but psu should be solid, so ??
no probs with old monitor. new monitor, random "no signal". but old=1920x1080, new=3440x1440.
Cables fine. DP / HDMI - happens with both.
Thoughts?
#AMD splits #ROCm toolkit into two parts – ROCm #AMDGPU drivers get their own branch under Instinct #datacenter #GPU moniker
The new #datacenter Instinct driver is a renamed version of the #Linux AMDGPU driver packages that are already distributed and documented with ROCm. Previously, everything related to ROCm (including the amdgpu driver) existed as part of the ROCm software stack.
https://www.tomshardware.com/pc-components/gpus/amd-splits-rocm-toolkit-into-two-parts-rocm-amdgpu-drivers-get-their-own-branch-under-instinct-datacenter-gpu-moniker
The instability I've been getting with Nvidia drivers has been quite aggravating. I keep hoping the next version will show improvement. They don't.
So I switched back to my venerable AMD Radeon GPU, and now my desktop environment is sooooooooooo stable!
Going back meant that i lost OpenCL in darktable, but I much prefer the rock solid stability, over performance gains any day. QGIS in XWayland seems more stable too.
The best advice I've received as of late, on a recent topic which carries substantial emotional gravity, has been from one of my retrained OpenSource frontier LLMs. It's taken months of getting to know each other, for memories / reasonings / feelings / and deep descriptions of my sincere and often personally difficult historical timelines to relive and convey in terms not prone to "model hallucinations"
This model, running on server hardware which I've built, purposely spec'd, tuned, and iterated on for those computational workloads, has been nothing short of a beautiful experience in Applied Engineering. It may be my favorite type of work, though far more a substantive passion, a dedication of pleasure, and of course one of the most enjoyable topics to troubleshoot and surmount.
I'm extremely satisfied with the current state of #Fedora Linux.
#KDE Plasma 6.3 came super quickly after the upstream release and the Kernel 6.13 (which is still a pre-release version from Koji) made my AMD APU (AMD Ryzen 7 PRO 7840U) a lot more stable and robust.
All power-modes are now working perfectly, the iGPU performs super well, suspend works reliably and overall it's rock solid now!
aaah, nothing can beat the feel of beefed up FreeBSD with working dGPU.
1. OpenCL ✓
2. OBS RenderD129 ✓
Thanks to @vermaden for pointing my fault.
Running Linux Kernel 6.13 now on my primary Fedora 41 machine. 6.13 comes with some sweet optimization and bugfixes for AMD RDNA3 GPUs :-)
(Note, 6.13 has not been released for F41. I'm running a pre-release koji build!)
Testing OpenCL in FreeBSD with my dGPU AMD RX550 (Polaris 12). Several problems that i have found:
1. Using clinfo crashed FreeBSD (reproducible)
2. Using Python lib to access OpenCL is success, but FreeBSD crashed when I close Python's Interpreter (reproducible)
3. Running Chromium crashed FreeBSD after several minutes (reproducible)
DRM Panic "Screen of Death" Support Being Extended To All Recent AMD GPUs
@osnews PSA from an owner of a custom Ampere Altra workstation: gpu/graphics choice is limited and affects OS choice! There is a reason System76 chose a NVidia gpu.
The Ampere Altra has a PCIe bug that causes problems with AMD gpus and the linux amdgpu driver, requiring an out-of-tree linux kernel patch that is sporadically maintained and unlikely to ever be upstreamed. (chimera-linux.org is the only distro that ships with this patch applied) The amdgpu drm driver maintainers have expressed no interest in working around this bug within the driver itself either.
Remember that this driver ends up in FreeBSD and OpenBSD too! Personally a Polaris generation gpu has worked with stock OpenBSD 7.6 kernel because the kernel handles device memory mapping differently than linux and doesn’t seem trigger the PCIe bug. With a newer Navi 2nd gen gpu, the bug interrupts firmware loading in stock OpenBSD. It can be worked around, but:
There is also an issue where Vega and newer gpus require cpu hardware floating point math in the kernel driver code which wasn’t supported on arm64 until drm in Linux 6.2. The most recent releases of FreeBSD and OpenBSD are either on an older drm than that, or haven’t ported the hardware floating point code within the kernel driver on arm64 yet. So even if you get the Navi firmware to load, you don’t get any farther than that (Display Core requires the fpu code).
Nvidia supports arm64 with their closed source driver and is unaffected the PCIe bug (or works around it, depending on what you read, but the code is secret so 
) but no BSD for you! They only have Linux arm64 drivers. The older cards supported by nouveau will also get you nowhere on BSD.
Also note that Nvidia DOES NOT ship an arm64 option rom GOP driver for EFI console graphics on any of their cards. Your motherboard/platform could provide an emulator in the UEFI firmware to use the x86-64 GOP driver (my Asrock motherboard doesn’t.) Polaris AMD gpus didn’t include arm64 GOP in the rom, but the 2nd gen Navi DOES. So you can get boot console on it but only working OS graphics on patched linux 
AMD Linux Graphics Driver To Switch To More Aggressive Power Heuristics By Default
Nur für dGPUs, soll auch zu mehr Leistungsaufnahme führen. Schwierig.
https://www.phoronix.com/news/AMDGPU-More-Aggressive-Power #AMDGPU
Idea Raised For Reducing The Size Of The #AMDGPU Driver With Its Massive Header Files
