Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
livellosegreto.it is one of the many independent Mastodon servers you can use to participate in the fediverse.
Livello Segreto è il social etico che ha rispetto di te e del tuo tempo.

Administered by:

Server stats:

1.2K
active users

livellosegreto.it: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#gpu

10 posts10 participants1 post today
Public
♡ Eva Winterschön ♡

💾 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...

#gpu #amd #ai #homelab #freebsd #linux #

Continued thread
Public
♡ Eva Winterschön ♡

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.
- github.com/freebsd/drm-kmod/is

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"

#amd#gpu#drm616kmod
Public
Benjamin Carr, Ph.D. 👨🏻‍💻🧬

#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.
tomshardware.com/pc-components

Tom's Hardware · AMD splits ROCm toolkit into two parts – ROCm AMDGPU drivers get their own branch under Instinct datacenter GPU monikerBy Aaron Klotz
Public
Daniel Gibson

Does anyone have a collection of .dds (and maybe also .ktx and/or .ktx2) textures I could use to test my texture viewer (github.com/DanielGibson/texvie)?

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! :)

crossplatform texture viewer. Contribute to DanielGibson/texview development by creating an account on GitHub.
GitHubGitHub - DanielGibson/texview at devcrossplatform texture viewer. Contribute to DanielGibson/texview development by creating an account on GitHub.
#gamedev#graphics#gpu
Public
Brian Benz

Had fun at #CosmosDBConf showcasing “Accelerating Real-Time Analytics with Cosmos DB and #NVIDIA GPU-Enhanced Serverless Apache Spark!” We used separate CPU/GPU builds in our Maven POM via profiles, Dockerfiles for container apps, and GPU-accelerated Spark to handle streaming data at warp speed. ⚡🚀

Missed it? Catch the recording: youtu.be/x-0-S0MS5ko?si=wr6pKX
Sample code here: aka.ms/sparkrapidsgpudemo

YouTubeAccelerating Real-Time Analytics with Cosmos DB and GPU-Enhanced Serverless Apache SparkBy Azure Cosmos DB
#Azure#GPU#Analytics
Public
GripNews

🌘 Shadertoys 移植至 Rust GPU
➤ 使用 Rust 開發 GPU 程式：以 Shadertoy 移植為例
✤ rust-gpu.github.io/blog/2025/0
這篇文章介紹了將流行的 Shadertoy 著色器移植到 Rust GPU 的過程。Rust GPU 允許使用 Rust 程式語言編寫 GPU 程式，並將其編譯成 SPIR-V 格式，使其與 Vulkan 兼容。移植過程相對順暢，並展示了 Rust 在 CPU 和 GPU 之間共享程式碼的優勢，以及對 traits、泛型和宏的支持。此外，作者也回饋了 wgpu 和 naga 專案，修復了幾個問題，並鼓勵更多人參與 Rust GPU 的開發。
+ 哇，Rust 竟然也能開發 GPU 程式！這感覺很酷，以後可以嘗試用 Rust 寫一些圖形效果。
+ 聽起來 Rust GPU 解決了 CPU 和 GPU 之間資料共享的痛點，這真的很棒！期待未來能看到更多 Rust GPU 的應用。
#程式開發 #Rust #GPU #Shadertoys

rust-gpu.github.io · Shadertoys ported to Rust GPU | Rust GPUWe ported a few popular Shadertoy shaders over to Rust
Public *
Jaycosm🔆

I stumbled upon an interesting blog today while searching for an image of the Silicon Graphics 3D cube logo. Named "Abort Retry Fail" by Bradford Morgan White, the blog's articles document computer history. I eventually wound up reading three of them.

#1 "The Rise and Fall of Silicon Graphics"

abortretry.fail/p/the-rise-and

Abort Retry Fail · The Rise and Fall of Silicon GraphicsBy Bradford Morgan White
#AbortRetryFail#Blog#RetroComputing
Public
GripNews

🌗 Shadertoys 移植至 Rust GPU
➤ 使用 Rust 開發 GPU 程式，為圖形渲染帶來新可能。
✤ rust-gpu.github.io/blog/2025/0
Rust GPU 專案成功將數個熱門的 Shadertoy shader 程式碼移植至 Rust 語言。此過程證明瞭使用 Rust 進行 GPU 程式設計的潛力，並展現了 Rust GPU 在整合 Rust 程式碼到 Vulkan 工作流程中的優勢。Rust GPU 允許開發者使用 Rust 撰寫 GPU 程式，並將其編譯成 SPIR-V 格式，同時也支援 CPU 和 GPU 之間的程式碼共享、traits、泛型和巨集等功能，並可利用標準的 Rust 工具進行開發和測試。此外，移植過程中也回饋了 wgpu 和 naga 專案，修復了多個問題，提升了整個 Rust 圖形生態系統。
+ 「這實在太棒了！Rust 的安全性和效能，加上 GPU 的平行處理能力，簡直是完美的結合。」
+ 「期待 Rust GPU 的生態系統能更完善
#程式開發 #GPU #Rust

rust-gpu.github.io · Shadertoys ported to Rust GPU | Rust GPUWe ported a few popular Shadertoy shaders over to Rust
SearchLive feeds
About