@otherdog Unfortunately ridiculous seems like the new norm.
I was really hoping with Intel entering the GPU Market that they would be more competition and pricing adjustments, but that doesn't seem to be happening.
Having said that, if you can wait, not purchase right away, and if everyone does that, then the market will adjust down, because at some point they need to actually sell the hardware.
Der neueste #Treiber für die #GeForce-#Grafikkarten von #Nvidia macht ernste Probleme. So wird durch einen #Bug die #Temperatur der #GPU nicht korrekt erfasst, was potenziell gefährliche Folgen haben könnte. https://winfuture.de/news,150430.html?utm_source=Mastodon&utm_medium=ManualStatus&utm_campaign=SocialMedia
TIL #AMD has #GPU (s) that have no hardware encoding capabilities whatsoever, i.e. their #RX6400. Yikes? Be careful when buying GPUs from AMD, I suppose.
It's one thing when people compare AMD GPUs with #NVIDIA's saying AMD's encoding prowess is inferior vs something like #NVENC, but to literally be unable to hardware transcode H264, HEVC, etc. as a modern GPU is insanely hilarious seeing that it's something even ancient GPUs and even iGPUs are capable of.
AMD CPUs? Solid, my last #Intel CPU was literally 7th gen - have gone through at least ~5 CPU upgrades since then. AMD GPUs? Stayed away from them and will continue to do so, even as a #Linux user. NVIDIA GPUs have been perfectly fine for me on #X11 before, and is perfectly usable (+ continually improving) on #Wayland now - Intel Arc GPUs are also affordable and perfect for my #homelab/servers.
https://github.com/GPUOpen-LibrariesAndSDKs/AMF/wiki/GPU-and-APU-HW-Features-and-Support#amd-gpu-multimedia-hardware-features
Quick HomeLab Update
As a follow up to this morning's iGPU 512M GART debugging (re: drm-61-kmod memory leak on amdgpu.ko), here are some pics. Reluctantly, the "ok fine" method for testing the memory leak allocation aspects involves using a non-integrated GPU which requires the same driver, for which this low-TDP single-slot AMD W7500 was acquired. Sometime tomorrow it will be installed in my workstation, which is the third chassis from the bottom (4U) situated above the two 5U chassis (HCI private cloud for GPU compute VMs).
More to follow...
Shader Programmers:
Are vector ops more efficient than scalar (ie if I add two float4s is that the same cost as adding two floats) or did that stop being a thing 15 years ago?
I just uploaded the 5000th #OpenCL hardware report to @sascha's gpuinfo.org database! 
And guess what #GPU I reserved the spot for: #Intel Arc B580 #Battlemage 
https://opencl.gpuinfo.org/displayreport.php?id=5000
I have contributed 4.2% (211) of all entries. 
Dynamic Register Allocation on AMD's RDNA 4 GPU Architecture
https://chipsandcheese.com/p/dynamic-register-allocation-on-amds
Panic most recently used by lkpikmalloc ...
Well, that was fast... didn't even get a mouse cursor of a full MATE Desktop menu system load. Was yet to connect kgdb to COM1 (need to swap from minicom to do so)... makes me want a PCIe RS232 card (for "comconsole_pcidev") so that I have a few more COMs to play with on redirects. Gotta love these iGPU tash-bins eh? "It's better than not having a GPU right?" ... not really.''
Closed bug report from the drm-515-kmod, discussing amdgpu memory leak. so, maybe a new one in drm-61-kmod, would not be surprised.
- https://github.com/freebsd/drm-kmod/issues/258
Short term revision of approach:
----
1. Today via post arrives, an AMD Radeon Pro W7500 (single slot 8GB, Navi-whatever gen)
2. I'll block off the iGPU during loader.conf sequence, using a "pptdev" blackhole (not for VM pt, but maybe an experiment for a 14.1 VM with the known-good amdgpu version).
3. Known as: throw money at the problem?
Some hardware notes:
----
1. This is not a Nvidia GPU situation; there are several generations of cards in the room which have been cycled through the workstation during "hardware isolation" and "process of elimination" sequences. I know those are stable, and which gen cards require which nvidia driver versions for stability purposes.
2. This is not a FreeBSD kernel issue, nor a Xorg "Plain Jane FrameBuffer" situation. The kernel (14.0, 14.1, 14.2) is stable and fine, and the basic vt driver for non-4K display-port functionality works fine. I can work all day in a series of tmux windows with some fifty or so panes, but that's not quite the optimal experience.
3. The AMD iGPU (Raphael) maxes out default to 512MB GART VRAM, and it can handle 240Hz @ 4K all day with no issues as long as that 512M doesn't get used up... that is until the latest amdgpu kmod drm, which crashes whenever it feels like it.
Michael... yes yes, I do have a lot of hardware, but this issue has surpassed the Sunk Cost Fallacy and has become a consumate knowledge-requirement process. I must know where this is failing so horrendously, otherwise the operating rule of "if it doesn't fulfill its hardware destiny, it will get the hammer and flames"... and the hardware is too nice for that - plus I could involve Supermicro support since it's still in warranty, but a replacement motherboard or CPU for the iGPU isn't going to solve a kernel module issue.
In the interim, laptop life and tablet meetings are getting me by, mostly decently.
Debug items of interest:
----
intsmb0: <AMD FCH SMBus Controller> at device 20.0 on pci0
intsmb0: Could not allocate I/O space
device_attach: intsmb0 attach returned 6
drmn0: Fetched VBIOS from VFCT
amdgpu: ATOM BIOS: 102-RAPHAEL-008
drmn0: Trusted Memory Zone (TMZ) feature not supported
drmn0: PCIE atomic ops is not supported
drmn0: VRAM: 512M 0x000000F400000000 - 0x000000F41FFFFFFF (512M used)
[drm ERROR :amdgpu_bo_init] Unable to set WC memtype for the aperture base
Loader items of usage:
----
# Multi-Console Output
# boot output primary: TTY, standard monitor via UEFI
# boot output secondary: COM1 RS232 Redirect (physical)
# boot output tertiary: COM2 RS232 Redirect (BMC SoL)
ipmi_load="YES"
boot_mute="NO"
boot_verbose="YES"
verbose_loading="YES"
boot_multicons="YES"
boot_serial="YES"
console="efi,comconsole,comconsole"
comconsole_port1="0x3F8"
comconsole_speed1="115200"
comconsole_port2="0x2F8"
comconsole_speed2="115200"
hw.uart.console="io:0x3f8,br:115200 io:0x2f8,br:115200"
ok ive to go now but the plan once i return ~2 hrs later is to dig thru my pendrives and use 1 to backup my current bios settings, use another to load up the latest stable bios version, take pics of my current bios settings, upgrade to the latest bios version, and then lastly to re-configure bios as close as possible to my current settings.
fingers crossed, my #Proxmox node would still be fine and hopefully, the ReBAR option would show up on my BIOS, cos rn on BIOS v4.6 (2020), it's not (even with CSM disabled, above 4G decoding enabled). My server hardware: #AMD Ryzen 7 1700, #ASRock B450M Pro4 #motherboard, and #Intel #ArcA380 #GPU.
A second test release of my texture viewer is available, now:
Array textures (2D and cubemaps) are supported
- Integer textures are displayed in a (more) useful way
- Color channels can be easily swizzled by the user
- … if that's not enough, the fragment shader source can be edited in the program
#nvidia used $1,000,000 of the hard earned money you spent on their #gpu #videocard to pay tribute to a #republican in order to be excluded from the #tariff #torture. #defundcorruption
New GPU meta just dropped!
Nvidia announces RTX 5060 Ti and 5060 mainstream graphics cards - but VRAM counts are concerning
Nvidia has announced a $500 billion AI infrastructure plan for Texas, just as the US government has basically banned H20 chip exports to China.
#Nvidia #AI #Semiconductors #USChinaTrade #ExportControls #Tariffs #H20 #Blackwell #GPU #Geopolitics
https://winbuzzer.com/2025/04/16/nvidia-pledges-500b-for-texas-ai-supercomputer-hub-xcxwbn/
#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 fact that a #GPU is subjected to #ITAR #controls and #restrictions is fucking insane. (I didn't read the article but I'm assuming it's ITAR.)
I hope #Nvidia pulls out of the #US over this shit.
RE: https://mstdn.social/users/TechCrunch/statuses/114344335481626839
Does anyone have a collection of .dds (and maybe also .ktx and/or .ktx2) textures I could use to test my texture viewer (https://github.com/DanielGibson/texview)?
For DDS I only found test textures from GLI and unfortunately many of them are invalid/broken :-/
For KTX(2) I have the ones from libktx (and the broken ones from GLI).
Thanks in advance! :)
Playing around with local #llm and wanted to evaluate the performance of my #gpu so I wrote this little #ollama benchmarking tool: https://github.com/stefanthoss/ollama-server-benchmark Impressive - my small #nvidia Tesla T4 generates prompt responses roughly 4 times as fast as my 64 core server CPU can.
⏚
Hacker News 
