<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AMD on maxgio's notes</title><link>https://notes.maxgio.me/tags/amd/</link><description>Recent content in AMD on maxgio's notes</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 30 Aug 2026 13:14:00 +0200</lastBuildDate><atom:link href="https://notes.maxgio.me/tags/amd/index.xml" rel="self" type="application/rss+xml"/><item><title>From a frozen Telegram photo to the Linux graphics stack</title><link>https://notes.maxgio.me/notes/from-telegram-freeze-to-linux-graphics-stack/</link><pubDate>Sun, 30 Aug 2026 13:14:00 +0200</pubDate><guid>https://notes.maxgio.me/notes/from-telegram-freeze-to-linux-graphics-stack/</guid><description>1. The fullscreen photo that froze a laptop I opened a photo from Telegram Web in Brave and switched it to fullscreen. The display froze. After failed attempts to recover it, I forced the Framework Laptop to restart.
A TTY later showed Vulkan selecting my AMD Radeon 780M. Two warnings about dynamic-buffer limits followed. They looked relevant, but appeared more than ten minutes after the next boot began.
The previous boot told a different story.</description></item></channel></rss>