HAhaunter·Sep 17, 2025Submission
AMD Open Source Driver for Vulkan project is discontinued
154 points · Open discussionGPUOpen-Drivers
AMDVLK
OPEN SOURCE2017–2025
GPUOpen-Drivers / AMDVLK
AMDVLK
AMD Open Source Driver For Vulkan
6Distinct people
7Mentions
0Explicit recommenders
2KGitHub stars
What to know before exploring
What it is
AMD Open Source Driver For Vulkan
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year7 dated mentions
Observed mentions: 2017-12-26 02:01:02 UTC to 2025-09-17 00:31:04 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 2 | 1 | 1 |
What Hacker News says
7 sourcesThose who have had or perceived issues tend to be the loudest.
I have had a good experience with Nvidia and when there is an issue, I report it and Nvidia fixes it within months. The only time I have seen a better turn around was Intel graphics, where they fixed things within 24 hours after I pointed out a bug in their kernel driver. AMD graphics on the other hand seems unresponsive to community reports or outright refuses to handle issues.
For example, they refused to implement VK_EXT_fragment_shader_interlock in AMDVLK despite implementing the equivalent for D3D12 on Windows:
https://github.com/GPUOpen-Drivers/AMDVLK/issues/108
The damage in that case is limited to Windows, as the community driver for Linux implemented it, but it made cross platform support in emulators more difficult. If it were not for Valve working on the community d
Read the rest
river, the Linux experience on AMD graphics would be no where near how good it is on Nvidia graphics.
I have been using the Nvidia driver for many years, had minimal problems and had great responses from Nvidia when I did report issues.
As for opening a bug on GitHub, there is a difference between them responding and them fixing things. I have seen many people report bugs without them fixing the issues. There is one prominent issue for parity between direct3d q2 and vulkan that was needed by emulators that they outright refused to fix:
https://github.com/GPUOpen-Drivers/AMDVLK/issues/108
With Intel, the last time I opened a bug with them, they fixed the issue I reported within 24 hours.
In Intel announces Arc B-series "Battlemage" discrete graphics with Linux supportWhat drivers are you using?
I'm running Chrome 72 at 4K on a 50" monitor via KDE Plasma and Fedora 29 on Kernel 4.20, using only an AMD Ryzen 5 2400g ASIC, and it runs just fine (so it does work on the desktop in at least that configuration). I did however manually build the latest ROCm [1] and Vulkan [2]. I would check your flags and check your settings to make sure you have the right optimizations.
chrome://flags chrome://chrome-urls
BTW: For whatever reason, in certain builds under some combination of settings, the times I've experienced Chrome running at a crawl, it's usually been an issue with GPU rasterization. These are the settings I have disabled (everything else is set to hardware accelerated or enabled)...
chrome://gpu
Out-of-process Rasterization: Disabled
Hardware Protected Video Decode: Hardware accelerated
Ras
Read the rest
terization: Software only. Hardware acceleration disabled
Skia Deferred Display List: Disabled
Skia Renderer: Disabled
Surface Control: Disabled
Here's my full Command Line:
/usr/bin/google-chrome-stable --disable-gpu-driver-bug-workarounds --enable-native-gpu-memory-buffers --force-device-scale-factor=1 --enable-accelerated-video --enable-accelerated-mjpeg-decode --flag-switches-begin --enable-audio-focus --enable-experimental-web-platform-features --enable-google-branded-context-menu --enable-oop-rasterization --enable-quic --enable-zero-copy --ignore-gpu-blacklist --enable-lcd-text --load-media-router-component-extension=1 --enable-hardware-overlays=single-fullscreen,single-on-top,underlay --enable-features=DrawOcclusion,ExperimentalProductivityFeatures,FontCacheScaling,InfiniteSessionRestore,LayeredAPI,NetworkService,OverlayScrollbar,OverlayScrollbarFlashAfterAnyScrollUpdate,OverlayScrollbarFlashWhenMouseEnter,PageAlmostIdle,ProactiveTabFreezeAndDiscard,SharedArrayBuffer,SiteCharacteristicsDatabase,UseSurfaceLayerForVideo,V8Orinoco,V8VmFuture,VizDisplayCompositor,VizHitTestDrawQuad,WebAssemblyBaseline,WebAssemblyThreads,WebRTC-H264WithOpenH264FFmpeg,enable-pixel-canvas-recording --flag-switches-end
[1] https://github.com/RadeonOpenCompute/ROCm
[2] https://github.com/GPUOpen-Drivers/AMDVLK
AMD Open Source Driver for Vulkan
505 points · Open discussion> Also AMD is working on providing open source GPU Vulkan drivers.
They have already provided them:
https://github.com/GPUOpen-Drivers/AMDVLK
https://www.phoronix.com/scan.php?page=article&item=amdvlk-r...
In Microsoft disables Spectre mitigations as Intel’s patches cause instabilityAMD Open Source Driver for Vulkan
4 points · Open discussion