--- title: OpenBSD 8.0 ships with Clang 22 everywhere, Linux 6.18... description: OpenBSD 8.0, the 61st release of the project, lands with its drm graphics stack now tracking Linux 6.18.y, adding initial Intel Arc A-Series (Alchemist) GPU... canonical: https://daily.dev/posts/openbsd-8-0-ships-with-clang-22-everywhere-linux-6-18-graphics-drivers-and-intel-arc-support-zsbu52hid copyright: © 2026 Daily Dev Ltd. terms: https://daily.dev/tos/ twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: OpenBSD 8.0 ships with Clang 22 everywhere, Linux 6.18 graphics drivers and Intel Arc support | daily.dev og:description: OpenBSD 8.0, the 61st release of the project, lands with its drm graphics stack now tracking Linux 6.18.y, adding initial Intel Arc A-Series (Alchemist) GPU... og:url: https://daily.dev/posts/openbsd-8-0-ships-with-clang-22-everywhere-linux-6-18-graphics-drivers-and-intel-arc-support-zsbu52hid og:image: https://api.daily.dev/og/posts/ZSbU52hId.png og:image:alt: OpenBSD 8.0 ships with Clang 22 everywhere, Linux 6.18 graphics drivers and Intel Arc support og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # OpenBSD 8.0 ships with Clang 22 everywhere, Linux 6.18 graphics drivers and Intel Arc support **[Collections](https://daily.dev/sources/collections)** · 2 min read · 0 upvotes · 0 comments ## Summary OpenBSD 8.0, the 61st release of the project, lands with its drm graphics stack now tracking Linux 6.18.y, adding initial Intel Arc A-Series (Alchemist) GPU support and expanding the amd64 kernel virtual address space from 4G to 512G for larger VRAM mappings. Clang/LLVM 22 is now the base compiler on every architecture that uses Clang, including sparc64, which switched last; Loongson support was dropped due to incompatibility with Clang 22. vmm/vmd now supports SMP guests with up to 64 VCPUs, and swap encryption is faster via CPU AES instructions. Other additions include ARM64 hibernate support, RISC-V 'V' vector extension support, a new Qualcomm WCN7850 WiFi driver (qwz), a Samsung Galaxy Book4 Edge battery driver (sambat), and httpd(8) custom response headers and header-based filtering. Bundled software includes GCC 16.1, GNOME 49, KDE Plasma 6.7.5, Python 3.14.7, Rust 1.98.1, Wayland 1.26 and Xfce 4.20. ## Content OpenBSD 8.0, the 61st release of the BSD operating system, is out. Here is what changed. ## Toolchain Clang/LLVM 22 is now the base compiler on every architecture that uses Clang. sparc64 was the last platform to switch, which leaves OpenBSD as the only OS with a modern toolchain on sparc64. The price is Loongson support, which was dropped because the port is incompatible with Clang 22. ## Graphics and kernel The drm stack (inteldrm, radeondrm, amdgpu) now tracks Linux 6.18.y. That brings initial support for Intel Arc A-Series (Alchemist) GPUs. The amd64 kernel's virtual address space grows from 4G to 512G, which makes larger VRAM mappings possible. vmm/vmd can now run SMP guests with up to 64 VCPUs. ## Hardware and platforms - arm64 gains hibernate support. - RISC-V adds the 'V' vector extension. - A new qwz driver covers the Qualcomm WCN7850 WiFi chip, and the qwx driver for Qualcomm WiFi 6 devices gets quite a few improvements. - A new sambat driver handles the battery on the Samsung Galaxy Book4 Edge. - Swap encryption is faster because it now uses the CPU's AES instructions. - Some arm64 and riscv64 boards get heartbeat LEDs. ## Userland httpd(8) can now set custom response headers and filter on headers. Someone on the release thread also reported making their first OpenSSH commit this cycle. ## Bundled software The release ships GCC 16.1, GNOME 49, KDE Plasma 6.7.5, LLVM/Clang 22, Python 3.14.7, Rust 1.98.1, Wayland 1.26 and Xfce 4.20. ## Getting it Install images are available for amd64, i386, arm64, armv7, hppa, loongson, luna88k, macppc, octeon, powerpc64, riscv64 and sparc64. The release page covers installation and how to extract the source, kernel and ports trees. It also links the full changelog and an upgrade guide for people coming from 7.9, and explains how to keep the ports tree current through AnonCVS. ## Questions this post answers ### Does OpenBSD 8.0 support Intel Arc GPUs? Yes, OpenBSD 8.0 adds initial support for Intel Arc A-Series (Alchemist) GPUs because its drm graphics stack (inteldrm, radeondrm, amdgpu) now tracks Linux 6.18.y. On amd64 the kernel virtual address space was also expanded from 4G to 512G to allow larger VRAM mappings needed by modern GPUs. _Track BSD graphics driver progress on daily.dev before picking hardware for your next OpenBSD build._ ### What compiler does OpenBSD 8.0 use by default OpenBSD 8.0 uses Clang/LLVM 22 as the base compiler on every architecture that supports Clang, with sparc64 being the last platform to switch over. This makes OpenBSD the only operating system running a modern toolchain on sparc64. Loongson architecture support was dropped entirely because it is incompatible with Clang 22. _Follow daily.dev for toolchain shifts like this before they break a legacy architecture build._ ### How many VCPUs can an OpenBSD vmm/vmd guest have in OpenBSD 8.0 OpenBSD 8.0's vmm/vmd hypervisor can run SMP guests with up to 64 VCPUs. The release also speeds up swap encryption by using the CPU's AES instructions. _Check daily.dev for virtualization updates when planning OpenBSD guest capacity._ ## Community take How the wider developer community reacted, aggregated from 2 discussions and 123 comments across hackernews (as of 2026-10-20). **TL;DR:** OpenBSD 8.0: Much of the discussion fixates on the satirical, AI-themed release artwork and its Simpsons references, while a separate thread praises OpenBSD's famously simple upgrade process and long-term stability, with some pushback on whether that's really unique anymore and on OpenBSD's filesystem and ecosystem tradeoffs. OpenBSD 8.0 release will have inteldrm/radeondrm/amdgpu drivers from Linux 6.18: Most discussion centers on technical curiosity about how GPL-adjacent Linux driver code can legally be ported into OpenBSD, plus a side debate on OpenBSD's versioning scheme and whether chasing Linux feature parity is still worthwhile. **Sentiment:** 41% positive · 38% mixed · 21% skeptical **The case for** - The sysupgrade/syspatch workflow is praised as simple and reliable across many releases. - The licensing works because the drm/Mesa/Xorg driver code in question is actually MIT/X-licensed, not GPL, even though it lives alongside GPL code in the Linux tree. - Long-time users report OpenBSD running stably for years on old hardware with minimal breakage between upgrades. - Firmware blobs are fetched post-install via fw_update rather than bundled, similar to how some Linux distros handle nonfree codecs. - Release notes and changelog are seen as clearer and better organized than some Linux release notes. **The pushback** - Some find the AI-styled release graphic genuinely off-putting regardless of satirical intent, with one calling it part of a broader 'slop' trend. - Some pushed back that importing code doesn't let you relicense it, and address-space/linking questions around GPL 'taint' remain genuinely unsettled. - OpenBSD's non-journaled filesystem and fixed sub-partition sizing are flagged as practical drawbacks versus Linux/FreeBSD with ZFS. - A recurring skeptical question: if OpenBSD mostly imports Linux drivers and chases feature parity, what's the point versus just using Linux or forking if Linux ever goes astray. - The package manager and overall system are described as feeling slower than Linux or FreeBSD. **By community** - hackernews (mixed): A long sub-thread debates whether the AI-styled release art is clever satire or genuinely bad, while another praises the upgrade process and stability, with some critical voices on filesystem choices, performance, and project culture. **Hottest debate:** OpenBSD 8.0: Whether the AI-generated-looking release artwork and song are a deliberate, funny satire of AI slop or just an unwelcome embrace of it. **Open questions** - Is it possible to get a modern journaled filesystem on OpenBSD, or does it remain limited in that area? - Is there a settled legal consensus on whether code embedded in a GPL-licensed project (like the Linux kernel) retains its original permissive license when extracted and reused elsewhere? - Can OpenBSD run smoothly on a modern 2025 laptop with suspend, graphics, and browser support without extra effort? - Given how much effort goes into porting Linux hardware support, is maintaining OpenBSD as a distinct system still worth it long-term? - Why does the upgrade sometimes require a monitor plugged in to avoid rebooting into the old version? **Highlights** > > I am not on board with the graphic, whatever the heck it is. They are purposefully iconoclast with whatever aesthetics are "socially acceptable" for mainstream nerds. For example, their use of comic-sans in official presentations. Here they use ridiculous slop in front of an audience of conservative unix hackers. You can find it funny with the right mindset. The upgrade mechanism from 7.9 to 8.0 is still gloriously simple, and exactly the same as it was at least 5 years ago [0]: ssh myopenbsdbox # log-in to your machine doas sysupgrade # will log you out, go drink some coffee ssh myopenbsdbox # log-in to the upgraded machine doas sysmerge # (optional) solve merge conflicts of your cfg files doas pkg_add -u # (optional) upgrade local packages [0] https://news.ycombinator.com/item?id=31109046 > — [enriquto on hackernews · 2 comments](https://news.ycombinator.com/item?id=50162029) > And so it begins. SlopenBSD. Disappointing OpenBSD is and all of software is descending into slop. Don't care if it is satire or not. > — [colesantiago on hackernews](https://news.ycombinator.com/item?id=50161355) > Huh; I would have thought that importing MIT code into a GPL codebase (like the Linux kernel) essentially “beats out” the original MIT-licensing and instead creates an GPL-licensed fork of said code; thus making such forked code ineligible for re-import into an MIT/BSD-licensed project like the OpenBSD kernel (unless that project wants to be infected by the component’s licensing and become GPL-licensed in turn.) Are you saying instead that the DRM drivers in the Linux kernel (the in-tree parts, I mean, not the firmware blobs) exist as an island of MIT-licensed code inside the otherwise GPL-licensed codebase? Or are these parts of the Linux kernel not even technically in-tree, but rather developed in a separate canonical repo and frequently synchronized into the kernel as a vendored dependency? That’s the only way I can see this working; but it’s unclear to me why this state of things would have been maintained for any length of time when the Linux kernel was the only consumer… > — [derefr on hackernews · 3 comments](https://news.ycombinator.com/item?id=50160649) > I got your point about the monoculture, and I agree with you. Being different is not something bad. My question was more nuanced though. It seems to me that in the past 10 years or so, openbsd didn’t invent very much. Of course that I agree that there are some punctual things where openbsd was first but that’s not the case lately. So it’s mostly a catchup game with linux features and compatibility needs for running linux software. If you open now the HN front page you will see one story about openbsd importing linux drivers and another story on openbsd struggles to support wine - and basically how wine developers don’t care too much about that. Hence my question, if most of the effort is put to catch up with linux features, is it even worth anymore? If I want to use linux from 5 years ago, I could just do that. Putting so much effort and time into developing a linux feature clone just in case linux becomes evil, also doesn’t make sense, because you can fork when you see this. Licensing wise even less, I think there’s now a mixture on both sides. So please take it as a genuine question, not as criticism or anything. > — [asmnzxklopqw on hackernews](https://news.ycombinator.com/item?id=50163738) > I've used OpenBSD the last year or so (as a bastion/jump host for a few systems) after using *BSD systems very little for probably the past decade, and... good lord I love it so much. Say what you want about the benefits of systemd or the usefulness of other parts of what is now unavoidable with Linux, and I won't argue with many of them, but OpenBSD just feels like a nix system is supposed to. `ps aux` is like 10 entries at first. `pf` makes so much sense. `man` pages are consistently incredible. Then the security/cryptography focus, managing services... so many things about it is just chef's kiss*. It's not a daily driver for me and it may not fit your use case for anything, but I highly recommend playing with it. > — [ctolsen on hackernews](https://news.ycombinator.com/item?id=50163511) **Source threads** - [hackernews](https://news.ycombinator.com/item?id=50160494) · 272 points · 87 comments - [hackernews](https://news.ycombinator.com/item?id=50158138) · 155 points · 36 comments ## Similar posts on daily.dev - [FreeBSD 14.5 Released With Hardware Support Improvements, Many Bug & Security Fixes](https://daily.dev/posts/freebsd-14-5-released-with-hardware-support-improvements-many-bug-security-fixes-dvq3z5eyl) · Phoronix · 1 upvotes · 0 comments --- Tags: [#infrastructure](https://daily.dev/tags/infrastructure), [#gpu](https://daily.dev/tags/gpu), [#openbsd](https://daily.dev/tags/openbsd) [View this post on daily.dev](https://daily.dev/posts/openbsd-8-0-ships-with-clang-22-everywhere-linux-6-18-graphics-drivers-and-intel-arc-support-zsbu52hid) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"OpenBSD 8.0 ships with Clang 22 everywhere, Linux 6.18 graphics drivers and Intel Arc support","url":"https://daily.dev/posts/openbsd-8-0-ships-with-clang-22-everywhere-linux-6-18-graphics-drivers-and-intel-arc-support-zsbu52hid","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/openbsd-8-0-ships-with-clang-22-everywhere-linux-6-18-graphics-drivers-and-intel-arc-support-zsbu52hid"},"datePublished":"2026-10-20T09:57:20.428Z","dateModified":"2026-10-20T13:09:34.577Z","description":"OpenBSD 8.0, the 61st release of the project, lands with its drm graphics stack now tracking Linux 6.18.y, adding initial Intel Arc A-Series (Alchemist) GPU...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/eeb3679e2406fa56f36dcdafe1ac0a03?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/eeb3679e2406fa56f36dcdafe1ac0a03?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Collections","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collections","logo":"https://media.daily.dev/image/upload/s--fk_6ycEi--/f_auto,q_auto/v1780996001/logos/collections?_a=BAMAMiWQ0","url":"https://daily.dev/sources/collections"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/openbsd-8-0-ships-with-clang-22-everywhere-linux-6-18-graphics-drivers-and-intel-arc-support-zsbu52hid","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"infrastructure,gpu,openbsd","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collections","item":"https://daily.dev/sources/collections"},{"@type":"ListItem","position":3,"name":"OpenBSD 8.0 ships with Clang 22 everywhere, Linux 6.18 graphics drivers and Intel Arc support"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/openbsd-8-0-ships-with-clang-22-everywhere-linux-6-18-graphics-drivers-and-intel-arc-support-zsbu52hid#faq","mainEntity":[{"@type":"Question","name":"Does OpenBSD 8.0 support Intel Arc GPUs?","acceptedAnswer":{"@type":"Answer","text":"Yes, OpenBSD 8.0 adds initial support for Intel Arc A-Series (Alchemist) GPUs because its drm graphics stack (inteldrm, radeondrm, amdgpu) now tracks Linux 6.18.y. On amd64 the kernel virtual address space was also expanded from 4G to 512G to allow larger VRAM mappings needed by modern GPUs. Track BSD graphics driver progress on daily.dev before picking hardware for your next OpenBSD build."}},{"@type":"Question","name":"What compiler does OpenBSD 8.0 use by default","acceptedAnswer":{"@type":"Answer","text":"OpenBSD 8.0 uses Clang/LLVM 22 as the base compiler on every architecture that supports Clang, with sparc64 being the last platform to switch over. This makes OpenBSD the only operating system running a modern toolchain on sparc64. Loongson architecture support was dropped entirely because it is incompatible with Clang 22. Follow daily.dev for toolchain shifts like this before they break a legacy architecture build."}},{"@type":"Question","name":"How many VCPUs can an OpenBSD vmm/vmd guest have in OpenBSD 8.0","acceptedAnswer":{"@type":"Answer","text":"OpenBSD 8.0's vmm/vmd hypervisor can run SMP guests with up to 64 VCPUs. The release also speeds up swap encryption by using the CPU's AES instructions. Check daily.dev for virtualization updates when planning OpenBSD guest capacity."}}]} ```