<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>amd on Maxgio&#39;s blog</title>
    <link>https://blog.maxgio.me/tags/amd/</link>
    <description>Recent content in amd on Maxgio&#39;s blog</description>
    <image>
      <url>https://blog.maxgio.me/papermod-cover.png</url>
      <link>https://blog.maxgio.me/papermod-cover.png</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Sun, 30 Aug 2026 13:14:00 +0200</lastBuildDate><atom:link href="https://blog.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://blog.maxgio.me/posts/from-telegram-freeze-to-linux-graphics-stack/</link>
      <pubDate>Sun, 30 Aug 2026 13:14:00 +0200</pubDate>
      
      <guid>https://blog.maxgio.me/posts/from-telegram-freeze-to-linux-graphics-stack/</guid>
      <description>1. The fullscreen photo that froze a laptop It was Sunday morning, I had a fever, and my plans extended no further than tea and feeling sorry for myself; troubleshooting a GPU failure was not on the list.
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, followed by two warnings about dynamic-buffer limits whose timestamp placed them more than ten minutes after the next boot began.</description>
    </item>
    
  </channel>
</rss>
