Helvede

1 post1 participant1 post today

Benjamin Carr, Ph.D. 👨🏻‍💻🧬<a href="https://hachyderm.io/tags/AMD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AMD</a> splits <a href="https://hachyderm.io/tags/ROCm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ROCm</a> toolkit into two parts – ROCm <a href="https://hachyderm.io/tags/AMDGPU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AMDGPU</a> drivers get their own branch under Instinct <a href="https://hachyderm.io/tags/datacenter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#datacenter</a> <a href="https://hachyderm.io/tags/GPU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPU</a> moniker The new <a href="https://hachyderm.io/tags/datacenter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#datacenter</a> Instinct driver is a renamed version of the <a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> 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. <a href="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" rel="nofollow noopener noreferrer" translate="no" target="_blank">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</a>

thedæmonI stayed up until 4:00 am setting up my FreeBSD system. I had to rise at 6:30 am to get ready for work today. The issue I haven't figured out yet why dpms gives my X11 a heart attack. The work around I've had to come up with is to ctrl+alt+f1, ctrl+alt+f8 then kill my cwm session with custom hotkey and startx again. I'm hoping to have it solved by the end of the day. <a href="https://hj.9fs.net?t=freebsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a> <a href="https://hj.9fs.net?t=dpms" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dpms</a> <a href="https://hj.9fs.net?t=amdgpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amdgpu</a> <a href="https://hj.9fs.net?t=navi22" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#navi22</a>

♡ Eva Winterschön ♡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 notified 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.<a href="https://mastodon.bsd.cafe/tags/gpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gpu</a> <a href="https://mastodon.bsd.cafe/tags/compute" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#compute</a> <a href="https://mastodon.bsd.cafe/tags/aiml" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aiml</a> <a href="https://mastodon.bsd.cafe/tags/nvidia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nvidia</a> <a href="https://mastodon.bsd.cafe/tags/turingTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#turingTest</a> <a href="https://mastodon.bsd.cafe/tags/amdgpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amdgpu</a> <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a> <a href="https://mastodon.bsd.cafe/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://mastodon.bsd.cafe/tags/neverUbuntu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#neverUbuntu</a> <a href="https://mastodon.bsd.cafe/tags/LLMs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLMs</a> <a href="https://mastodon.bsd.cafe/tags/python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#python</a> <a href="https://mastodon.bsd.cafe/tags/cognition" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cognition</a>

orva<a href="https://mastodon.social/@mntmn" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mntmn</a> libera has <a href="https://fosstodon.org/tags/amdgpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amdgpu</a> but.. "There are 8 users on channel <a href="https://fosstodon.org/tags/amdgpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amdgpu</a>"

Larvitz :fedora: :redhat:I'm extremely satisfied with the current state of <a href="https://burningboard.net/tags/Fedora" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fedora</a> Linux.<a href="https://burningboard.net/tags/KDE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KDE</a> 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!<a href="https://burningboard.net/tags/fedora" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fedora</a> <a href="https://burningboard.net/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://burningboard.net/tags/amdgpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amdgpu</a> <a href="https://burningboard.net/tags/ryzen" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ryzen</a> <a href="https://burningboard.net/tags/thinkpad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#thinkpad</a>

Alauddin Maulana Hirzan 💻aaah, nothing can beat the feel of beefed up FreeBSD with working dGPU. 1. OpenCL ✓ 2. OBS RenderD129 ✓ Thanks to <a href="https://mastodon.bsd.cafe/@vermaden" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@vermaden</a> for pointing my fault.<a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a> <a href="https://mastodon.bsd.cafe/tags/amdgpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amdgpu</a> <a href="https://mastodon.bsd.cafe/tags/opencl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opencl</a>

Larvitz :fedora: :redhat: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!) :linux: :fedora: <a href="https://burningboard.net/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://burningboard.net/tags/fedora" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fedora</a> <a href="https://burningboard.net/tags/amdgpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amdgpu</a> <a href="https://burningboard.net/tags/kernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kernel</a>

Alauddin Maulana Hirzan 💻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)What should I do to fix this? <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a> <a href="https://mastodon.bsd.cafe/tags/dGPU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dGPU</a> <a href="https://mastodon.bsd.cafe/tags/AMDGPU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AMDGPU</a>

Gilberto FicaraPublished another article about <a href="https://mastodon.art/tags/Darktable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Darktable</a> with <a href="https://mastodon.art/tags/OpenCL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenCL</a> for <a href="https://mastodon.art/tags/AMD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AMD</a> <a href="https://mastodon.art/tags/ROCm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ROCm</a> on <a href="https://mastodon.art/tags/Debian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Debian</a> (SID)... I finally got it working (again) :)<a href="https://www.stranatesta.eu/tech/darktable-opencl-debian-sid-december-2024/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.stranatesta.eu/tech/darktable-opencl-debian-sid-december-2024/</a><a href="https://mastodon.art/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://mastodon.art/tags/amdgpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amdgpu</a> <a href="https://mastodon.art/tags/gpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gpu</a> <a href="https://mastodon.art/tags/photography" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#photography</a>

methoxyf<a href="https://mstdn.social/@osnews" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@osnews</a> 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 🫠<a href="https://social.treehouse.systems/tags/bsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bsd</a> <a href="https://social.treehouse.systems/tags/openbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openbsd</a> <a href="https://social.treehouse.systems/tags/amdgpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amdgpu</a> <a href="https://social.treehouse.systems/tags/amdgraphics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amdgraphics</a> <a href="https://social.treehouse.systems/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://social.treehouse.systems/tags/arm64" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#arm64</a> <a href="https://social.treehouse.systems/tags/armlinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#armlinux</a> <a href="https://social.treehouse.systems/tags/nvidia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nvidia</a> <a href="https://social.treehouse.systems/tags/nvidiagpudisplaydriver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nvidiagpudisplaydriver</a> <a href="https://social.treehouse.systems/tags/ChimeraLinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ChimeraLinux</a> <a href="https://social.treehouse.systems/tags/amperecomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amperecomputing</a> <a href="https://social.treehouse.systems/tags/amperealtra" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amperealtra</a>

Wintermute_BBSso the <a href="https://oldbytes.space/tags/amdgpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amdgpu</a> driver included in drm-515-kmod has the disturbing habit of coredumping itself. which is why I downgraded to drm-510-kmod as it does not annoy me with such things.aside from that, I now have <a href="https://oldbytes.space/tags/xfce4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#xfce4</a> localized and up and running. next stop: testing suspend mode ...<a href="https://oldbytes.space/tags/freebsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freebsd</a>

Jason WeatherlyYay, it seems that locking my desktop is making the GPU very, very angry. Not quite sure what's going on, but this is *definitely* an issue as I'm losing half of a monitor with a large white box. This is with an AMD Radeon 7900XT. <a href="https://social.linux.pizza/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://social.linux.pizza/tags/amdgpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amdgpu</a> <a href="https://social.linux.pizza/tags/amd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amd</a>

Major Hayden 🤠My new AMD GPU was missing from btop after building a new PC and installing Fedora 40. Solving it involved installing the "rocm-smi" package:<a href="https://major.io/p/amd-gpu-missing-btop/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://major.io/p/amd-gpu-missing-btop/</a><a href="https://social.lol/tags/AMD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AMD</a> <a href="https://social.lol/tags/amdgpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amdgpu</a> <a href="https://social.lol/tags/fedora" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fedora</a> <a href="https://social.lol/tags/btop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#btop</a> <a href="https://social.lol/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a>

in ♥️ with PDA (and 🐧)Sorry ... stupid question. Everythink works fine when I set my display to 60hz. No artefacts or lags. The image quality should be the same? 120 hz are mainly good in games (I don't play on my laptops) <a href="https://chaos.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://chaos.social/tags/amdgpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amdgpu</a>

in ♥️ with PDA (and 🐧)Someone else has this problem? AMD Ryzen 7 7840HS w/ Radeon 780M Graphics with 120hz I have glitches for a blink and when moving windows. Not always. switching to 96hz seems to help... <a href="https://chaos.social/tags/amdgpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amdgpu</a> <a href="https://chaos.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a>

Zeroday Podcast (stefan)<a href="https://mastodon.social/@nixCraft" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@nixCraft</a> <a href="https://podcasts.social/tags/gaming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gaming</a> on <a href="https://podcasts.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> is possible and practical. I am proof of that since I switch first from windough to <a href="https://podcasts.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a>, and now from <a href="https://podcasts.social/tags/nvidia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nvidia</a> to <a href="https://podcasts.social/tags/amd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amd</a> <a href="https://podcasts.social/tags/amdgpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amdgpu</a>.

🔗 David Sommerseth<a href="https://mastodon.social/@nixCraft" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@nixCraft</a> I can be pragmatic in many cases, use stuff which works - prefer FOSS when there are real alternatives.But nvidia ... They deliberately try to get a free pass in <a href="https://infosec.exchange/tags/foss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#foss</a> with their proprietary driver. The "open source" Linux kernel driver you get from them is essentially just a firmware loader ... Which tries to circumvent the limitations internal GPL export restricted functions have, inside that binary blob.And that, dear friends, is one of the reasons this driver can make your system end up in crashes ... When it tries to access restricted functions using an expected interface, where an internal kernel interface may have changed sufficiently with a kernel update to break unexpected users of it.Drivers doing the right thing, typically don't end up in this mess ... Because they use properly public exposed APIs which has a different guarantee to stability. So if that driver is a proper GPL licenced driver, it has access to all the GPL tagged functions in the kernel directly and doesn't need to do this wonky stuff.And that's why <a href="https://infosec.exchange/tags/nvidia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nvidia</a> deserves to be completely ignored by <a href="https://infosec.exchange/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> users. They deliberately try to access kernel functionality in particularly restricted from their driver - because it's not a proper GPL driver.<a href="https://infosec.exchange/tags/amdgpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amdgpu</a>'s might not be equally good compared to what nvidia can do. But at least, there are real open sourced, GPL based drivers for them.

in ♥️ with PDA (and 🐧)Does someone have the same problems with <a href="https://chaos.social/tags/amdgpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amdgpu</a> and 120 hz monitor. My <a href="https://linuxrocks.online/@tuxedocomputers" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@tuxedocomputers</a> laptop shows pink artefacts when switching transparent windows. setting the screen to 96 hz fixes the problem. running <a href="https://chaos.social/tags/fedora" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fedora</a>

JP LehrWe just released <a href="https://mast.hpc.social/tags/AOMP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AOMP</a> 18.0-0 -- our <a href="https://mast.hpc.social/tags/LLVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLVM</a> based <a href="https://mast.hpc.social/tags/OpenMP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenMP</a> compiler for <a href="https://mast.hpc.social/tags/AMDGPU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AMDGPU</a>. Go get your copy at <a href="https://github.com/ROCm-Developer-Tools/aomp/releases/tag/rel_18.0-0" rel="nofollow noopener noreferrer" target="_blank">https://github.com/ROCm-Developer-Tools/aomp/releases/tag/rel_18.0-0</a><a href="https://mast.hpc.social/tags/HPC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HPC</a> <a href="https://mast.hpc.social/tags/GPU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPU</a>

flywheelIt seems that <a href="https://mastodon.social/tags/AMD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AMD</a> <a href="https://mastodon.social/tags/AMDGPU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AMDGPU</a> DC display support for <a href="https://mastodon.social/tags/RISC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RISC</a>-V is arriving in <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> 6.6.That Pioneer Box seems more and more attractive looking.<a href="https://www.phoronix.com/news/AMD-FSPR-Linux-6.6" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.phoronix.com/news/AMD-FSPR-Linux-6.6</a> <a href="https://milkv.io/pioneer" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://milkv.io/pioneer</a>

Recent searches

Search options

Administered by:

Server stats:

#amdgpu