Lingolol

Csepp 🌢Hrmm, should I install my Vega series AMD card in my work PC after all? I looked up the NixOS page on AMDGPU and immediately remembered one of the major reasons I stopped using that device: <a href="https://merveilles.town/tags/AMDGPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#AMDGPU</a> is a buggy piece of crap. Several years later and they still haven't fixed the kernel bugs that cause the entire GPU to crash. At least now there are workarounds, although of dubious quality. Maybe I should just put it back in my old PC and use it with Windows with no internet access. Or more likely: just finally sell it.

FellSay about Linux what you will, but getting this much detail about what your graphics card is doing is pretty cool.🐧`amdgpu_top --gui`<a href="https://ma.fellr.net/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://ma.fellr.net/tags/LinuxGaming" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxGaming</a> <a href="https://ma.fellr.net/tags/GamingOnLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#GamingOnLinux</a> <a href="https://ma.fellr.net/tags/AMD" class="mention hashtag" rel="nofollow noopener" target="_blank">#AMD</a> <a href="https://ma.fellr.net/tags/GPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPU</a> <a href="https://ma.fellr.net/tags/amdgpu" class="mention hashtag" rel="nofollow noopener" target="_blank">#amdgpu</a> <a href="https://ma.fellr.net/tags/amdgpu_top" class="mention hashtag" rel="nofollow noopener" target="_blank">#amdgpu_top</a>

Eduardo Medina 🇪🇸¿<a href="https://mastodon.social/tags/HDMI" class="mention hashtag" rel="nofollow noopener" target="_blank">#HDMI</a> o <a href="https://mastodon.social/tags/DisplayPort" class="mention hashtag" rel="nofollow noopener" target="_blank">#DisplayPort</a> en <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>? Sin lugar a dudas, DisplayPort, ya que HDMI Forum ha vetado la implementación de la versión 2.1 de su especificación en <a href="https://mastodon.social/tags/AMDGPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#AMDGPU</a>.DisplayPort, por su parte, es una interfaz abierta desarrollada por <a href="https://mastodon.social/tags/VESA" class="mention hashtag" rel="nofollow noopener" target="_blank">#VESA</a>, por lo que su implementación es totalmente libre, como en USB.La pena es que apenas existen capturadoras que se apoyen en DisplayPort en lugar de HDMI. <a href="https://www.phoronix.com/news/HDMI-2.1-OSS-Rejected" rel="nofollow noopener" translate="no" target="_blank">https://www.phoronix.com/news/HDMI-2.1-OSS-Rejected</a><a href="https://mastodon.social/tags/AMD" class="mention hashtag" rel="nofollow noopener" target="_blank">#AMD</a> <a href="https://mastodon.social/tags/Radeon" class="mention hashtag" rel="nofollow noopener" target="_blank">#Radeon</a>

S.T. VejeAfter 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=2Any ideas?<a href="https://mstdn.social/tags/NixOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#NixOS</a> <a href="https://mstdn.social/tags/Nix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nix</a> <a href="https://mstdn.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://mstdn.social/tags/AMDGPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#AMDGPU</a> <a href="https://mstdn.social/tags/DMUB" class="mention hashtag" rel="nofollow noopener" target="_blank">#DMUB</a>

thedæmonOk, I'm seriously tired of this hard lock on FreeBSD due to my amdgpu / drivers. How can I get logs on this as it completely locks up my system and turns off my monitor. I cannot ssh into it, I have to hard reset it. It happens in console, x11, wayland. It's random afaik, it will do it randomly is how I feel. I am using 14.2 and a amd 6750XT, probably the only FreeBSD user with one. Do I need to swap GPUs or do something else? Please help, I am so frustrated with this 1 issue. <a href="https://snac.9front.club?t=freebsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> <a href="https://snac.9front.club?t=amdgpu" class="mention hashtag" rel="nofollow noopener" target="_blank">#amdgpu</a> <a href="https://snac.9front.club?t=amd" class="mention hashtag" rel="nofollow noopener" target="_blank">#amd</a> <a href="https://snac.9front.club?t=drmkmod" class="mention hashtag" rel="nofollow noopener" target="_blank">#drmkmod</a>

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

Eva WinterschönThe 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" target="_blank">#gpu</a> <a href="https://mastodon.bsd.cafe/tags/compute" class="mention hashtag" rel="nofollow noopener" target="_blank">#compute</a> <a href="https://mastodon.bsd.cafe/tags/aiml" class="mention hashtag" rel="nofollow noopener" target="_blank">#aiml</a> <a href="https://mastodon.bsd.cafe/tags/nvidia" class="mention hashtag" rel="nofollow noopener" target="_blank">#nvidia</a> <a href="https://mastodon.bsd.cafe/tags/turingTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#turingTest</a> <a href="https://mastodon.bsd.cafe/tags/amdgpu" class="mention hashtag" rel="nofollow noopener" target="_blank">#amdgpu</a> <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> <a href="https://mastodon.bsd.cafe/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mastodon.bsd.cafe/tags/neverUbuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#neverUbuntu</a> <a href="https://mastodon.bsd.cafe/tags/LLMs" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLMs</a> <a href="https://mastodon.bsd.cafe/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://mastodon.bsd.cafe/tags/cognition" class="mention hashtag" rel="nofollow noopener" target="_blank">#cognition</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" target="_blank">@vermaden</a> for pointing my fault.<a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> <a href="https://mastodon.bsd.cafe/tags/amdgpu" class="mention hashtag" rel="nofollow noopener" target="_blank">#amdgpu</a> <a href="https://mastodon.bsd.cafe/tags/opencl" class="mention hashtag" rel="nofollow noopener" target="_blank">#opencl</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" target="_blank">#FreeBSD</a> <a href="https://mastodon.bsd.cafe/tags/dGPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#dGPU</a> <a href="https://mastodon.bsd.cafe/tags/AMDGPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#AMDGPU</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" target="_blank">#linux</a> <a href="https://social.linux.pizza/tags/amdgpu" class="mention hashtag" rel="nofollow noopener" target="_blank">#amdgpu</a> <a href="https://social.linux.pizza/tags/amd" class="mention hashtag" rel="nofollow noopener" target="_blank">#amd</a>

Denzil FerreiraIf you have a laptop with an AMD powered iGPU or eGPU, and you are on Linux, make sure to install LACT: <a href="https://github.com/ilya-zlobintsev/LACT" rel="nofollow noopener" translate="no" target="_blank">https://github.com/ilya-zlobintsev/LACT</a>I was able to lower the clocks of my iGPU Picasso Vega 8, so I can enjoy more battery life on my laptop on the go.<a href="https://techhub.social/tags/amdgpu" class="mention hashtag" rel="nofollow noopener" target="_blank">#amdgpu</a> <a href="https://techhub.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://techhub.social/tags/batteryLife" class="mention hashtag" rel="nofollow noopener" target="_blank">#batteryLife</a>

Zeroday Podcast (stefan)<a href="https://mastodon.social/@nixCraft" class="u-url mention" rel="nofollow noopener" target="_blank">@nixCraft</a> <a href="https://podcasts.social/tags/gaming" class="mention hashtag" rel="nofollow noopener" target="_blank">#gaming</a> on <a href="https://podcasts.social/tags/linux" class="mention hashtag" rel="nofollow noopener" 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" target="_blank">#linux</a>, and now from <a href="https://podcasts.social/tags/nvidia" class="mention hashtag" rel="nofollow noopener" target="_blank">#nvidia</a> to <a href="https://podcasts.social/tags/amd" class="mention hashtag" rel="nofollow noopener" target="_blank">#amd</a> <a href="https://podcasts.social/tags/amdgpu" class="mention hashtag" rel="nofollow noopener" target="_blank">#amdgpu</a>.

🔗 David Sommerseth<a href="https://mastodon.social/@nixCraft" class="u-url mention" rel="nofollow noopener" 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" 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" target="_blank">#nvidia</a> deserves to be completely ignored by <a href="https://infosec.exchange/tags/Linux" class="mention hashtag" rel="nofollow noopener" 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" 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.

ralf tauscher :FreiburgSocial:how to fix a <a href="https://freiburg.social/tags/amdgpu" class="mention hashtag" rel="nofollow noopener" target="_blank">#amdgpu</a> <a href="https://freiburg.social/tags/wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#wayland</a> bug? just use linux 6.6.6 ;)

HimmelssohnCan please someone explain to me, how to get the <a href="https://social.adlerhorst.net/tags/amdgpu" class="mention hashtag" rel="nofollow noopener" target="_blank">#amdgpu</a> driver running with <a href="https://social.adlerhorst.net/tags/Manjaro" class="mention hashtag" rel="nofollow noopener" target="_blank">#Manjaro</a>? Any more recent version than from 2018? I was told, Radeon drivers integrate well with linux.

Csepp 🌢pissed at computer

Recent searches

Search options

Administered by:

Server stats:

#amdgpu