-<li>If you find an app that does not start up at all, please don’t report it as a bug. Lots of apps won’t work because they require a newer GL version than what we support. Please set the <code>LIBGL_ALWAYS_SOFTWARE=1</code> environment variable for those apps to fall back to software rendering. If it is a popular app that is part of the Arch Linux ARM repository, you can make a comment on <a href=https://github.com/AsahiLinux/linux/issues/73>this issue</a> instead, so we can add Mesa quirks to workaround.</li><li>If you run into issues caused by <code>linux-asahi-edge</code> unrelated to the GPU, please add a comment to <a href=https://github.com/AsahiLinux/linux/issues/70>this issue</a>. This includes display output issues! (Resolutions, backlight control, display power control, etc.)</li><li>If the GPU locks up and all GPU apps stop working, run <code>asahi-diagnose</code> (for example, from an SSH session), open a new bug on <a href=https://github.com/AsahiLinux/linux>AsahiLinux/linux</a>, attach the file generated by that command, and tell us what you were doing that caused the lockup.</li><li>For other GPU issues (rendering glitches, apps that crash after starting up correctly, and things like that), run <code>asahi-diagnose</code> and make a comment on <a href=https://github.com/AsahiLinux/linux/issues/72>this issue</a>, attaching the file generated by that command. Don’t forget to tell us about your environment!</li><li>In the future, if a driver update causes a regression (rendering problems or crashes for apps that previously worked properly), you can open a bug <a href=https://gitlab.freedesktop.org/asahi/mesa/-/issues>directly in the Mesa tracker</a>.</li></ul><p>We hope you enjoy our driver! Remember, things are still moving quickly, so make sure to update your packages regularly to get updates and bug fixes!</p><div class=post-bottom>Alyssa Rosenzweig & Asahi Lina · <span class=publishdate>2022-12-07</span></div></div></div></section><style>.hnsucks{position:fixed;left:0;top:0;width:100%;height:100%;background-color:#fff;display:block;z-index:10000000000;pointer-events:none;mix-blend-mode:multiply;text-align:center}.hnsucks:visited{background-color:#000}.hnsucks2{padding:20px;height:auto;color:#000;background-color:#000;mix-blend-mode:lighten}.hnsucks2:visited{color:#fff}.hnsucks2 code{color:inherit}</style><script>fetch&&CSS.supports("mix-blend-mode","multiply")&&fetch("https://cdn.asahilinux.org/.h",{method:"GET"}).then(e=>e.json()).then(e=>{let t=document.getElementById("post-section");e.forEach(e=>{let n=document.createElement("a");n.ariaHidden=!0,n.tabIndex=-1,n.classList.add("hnsucks"),n.rel="nofollow",n.href=e;let s=n.cloneNode();s.classList.add("hnsucks2"),s.innerHTML="Hi! It looks like you might have come from Hacker News. We've consistently found large numbers of comments containing blatant harassment, abuse, and bigotry directed at multiple Asahi Linux developers in HN comment sections, which go unmoderated for long periods of time or indefinitely. These abusive comments rank highly in search results for our project and the names of our developers, and continue to do so to this day.<br><br>In addition, we find that only a tiny fraction of HN comments (often less than 1%) actually engage with the substance of our articles, with the majority being off-topic, misinformative, repetitive, or otherwise of low quality, making the overall value of HN exposure overwhelmingly negative for our project.<br><br>We have tried to raise the issue of rampant abuse and low-quality discussion with HN mods, but instead of replying they added <code>rel="noreferrer"</code> to links to our site (specifically), to make it harder for us to block HN traffic. We sent a further email and explicitly pointed out a thread with multiple severe instances of directed, explicit harassment at one of our developers (including multiple allegations of mental illness, direct insults, misgendering, and transphobic dog whistles, all unmoderated and publicly visible and indexed). Some of these were removed weeks later (after being up for months), but they stopped responding after we pointed out even more instances of abuse.<br><br>At this point, we are forced to conclude that Y Combinator and Daniel Gackle are actively choosing to platform hate and harassment against open source developers, and further are actively working to evade blocking of this harassment by those targeted. For this reason, we are not interested in traffic or commentary from HN. Please move on to the next story.<br><br>To Dang: Do better.",t.after(n),n.after(s),t=s})})</script>
0 commit comments