If you run Linux on AMD hardware, you have probably spent the last month either rebooting into Windows to dim your screen, or running a custom kernel with a patch you grabbed off a forum thread. The August batch from AerynOS ends that detour by shipping the upstream fix for the AMDGPU brightness regression that landed in Linux 7.1.6 and 7.1.7. That is the headline. Everything else in the update is the kind of background housekeeping you do not notice until you need it.
AerynOS is the atomic-update Linux distribution that splits its tooling from the wider systemd world and rebuilds its base system every day from a manifest. That sounds like a recipe for chaos, but it is actually the point. When something breaks in mainline, AerynOS can either ship around it or absorb the patch on its own schedule without dragging the whole distro into a version freeze. The August update is a clean example of that pipeline doing what it is supposed to do.
What is actually fixed in Linux 7.1.8
The AMDGPU brightness regression was a small but loud bug. After 7.1.6 shipped in late June, a chunk of AMD Radeon users found that their laptop backlight controller stopped responding to the standard ACPI (Advanced Configuration and Power Interface, the firmware layer that handles brightness keys and power state) brightness keys. The panel either pinned at full brightness or pegged at minimum, and neither state survived a suspend cycle. There was no console error and no obvious journal entry. The fix went into mainline 7.1.8 and rolled forward into the stable kernel tree. AerynOS picked it up the same week, which is what atomic distros are supposed to be good at.
What you actually get when you update today:
- Linux 7.1.8 on the stable kernel track, with the AMDGPU fix included
- Linux 7.1.8 also on the gaming kernel track, so Nvidia and AMD users land on the same version for once
- Linux 6.18.44 on the LTS (long-term support) kernel for people who would rather wait six months and skip GPU churn
- Updated Intel and AMD microcode packages, picked up automatically by the loader
If you only care about the brightness fix, the upgrade is a five-minute job and a reboot. If you care about everything else in the update, give yourself a weekend.
GNOME 50.4 and KDE Plasma 6.7.4 ship together
AerynOS treats its desktop layer as a single stack that can run either GNOME or Plasma on top of the same base system, and the August update pushes both desktops forward in lockstep. GNOME 50.4 brings the usual pile of small refinements to the shell, the calendar, the screenshot tool, and the settings app. KDE Plasma 6.7.4 brings a similar pile to the KDE side, and KDE Frameworks 6.29 lands underneath both. The interesting detail is that you can flip between sessions and find the same system tray behavior, the same font rendering, the same notification panel underneath both desktops. That is not a small thing. Most distros pick a side and let the other desktop rot.
The catch is that AerynOS still treats its Unstable stream as the rapid-iteration channel. If you want GNOME 50.4 and Plasma 6.7.4 today, you take the bumpy ride that comes with daily rebuilds and the occasional broken package. The Stable stream cuts once a quarter, and the cut that follows this August batch is where these desktops will land in a quieter form.
Practical notes for anyone running AerynOS today:
- Mesa 26.1.7 graphics drivers are in, which gives a measurable boost on AMD RDNA3 and on Intel Arc hardware
- GStreamer 1.28.6 is in, which fixes a long-standing bug with certain webcam pipelines
- The PipeWire (the audio and video routing daemon that replaced PulseAudio) stack picked up a small but real latency improvement for Bluetooth headsets
- Firefox and Chromium both got bumped to their current stable releases
If you are not an AerynOS user yet, none of this matters to you directly. If you are running Fedora, openSUSE, or Arch, you will get most of the same versions on your own schedule.
kmscon becomes the default virtual terminal
This is the change I did not expect, and probably the one that will cause the most complaints in the forums. AerynOS has switched its default virtual terminal from the Linux kernel’s built-in VT (a text-mode screen driver that runs before X or Wayland starts) to kmscon, which is a userspace terminal that talks to the display via DRM (Direct Rendering Manager, the Linux kernel subsystem that lets programs draw to the screen) instead of going through the kernel console layer. The visible difference is that kmscon handles UTF-8 properly, renders fonts without aliasing, and does not lose its mind when you switch back from a Wayland session.
Practical reasons you might care:
- Resizing a tty (teletypewriter, the text-mode virtual terminal you get with Ctrl+Alt+F2) does not leave a smear of old characters on the screen anymore
- Asian and Cyrillic characters render correctly in the console without dropping back to ASCII boxes
- Copy and paste work between the terminal and Wayland without the kernel buffer getting in the way
- Boot messages look cleaner because kmscon starts before Plymouth hands off
The downside is that if you depend on the kernel’s built-in console for crash dumps or for serial-over-LAN debugging, kmscon sits on top of the same framebuffer and may obscure the early-boot output you used to rely on. If you do real kernel work, keep a USB stick with a fallback image that boots with the old VT.
Broadcom STA wireless finally shows up
This is the kind of entry that only matters if you have been waiting for it. Broadcom’s proprietary wireless driver, the one that supports a long list of older laptops and a stubborn handful of current ones, has been missing from AerynOS for about six months. It landed in the August update. If your laptop’s Wi-Fi was working under Ubuntu but not under AerynOS, that is probably why, and the fix is now in the Unstable stream and will land in the next Stable cut.
- bcmwl-kernel-source-equivalent package now ships in the standard repo (the driver source)
- Firmware blobs (binary files the hardware needs to operate) are pre-installed on first boot for supported chipsets
- A dkms (Dynamic Kernel Module Support, a system that rebuilds kernel modules automatically when the kernel updates) hook keeps the module working across kernel updates, which was the second half of the bug
If you bought a Dell, HP, or Lenovo laptop in the last ten years and have never been able to get Wi-Fi working under AerynOS, this is the month to try again.
Trade-offs
Picking the Unstable stream means living with breakage. Pick Stable and you wait until the next quarterly cut for GNOME 50.4 and Plasma 6.7.4. Picking the LTS kernel means waiting six more months for any GPU fix, including this one. The atomic update model is real, and it works, but it punishes anyone who wants the new desktop today and the old stability guarantee yesterday. You cannot have both at once.
Specific costs worth naming:
- The kmscon switch will break serial console workflows on any machine where the kernel console is your only window into boot
- The LTS kernel track still sits at 6.18.44, which means LTS users do not get the AMDGPU fix at all on that branch
- The Broadcom STA driver is proprietary, and AerynOS users who want a fully free system will have to opt out of the package
- Daily rebuilds in the Unstable stream sometimes pull a bad package for six to twelve hours before the rollback lands
Bottom line
If you have an AMD laptop and have been dodging the brightness bug for two months, update today. If you have been waiting for Broadcom wireless to show up on your AerynOS install, same answer. If you just want GNOME 50.4 and Plasma 6.7.4 on a stable base, wait for the next Stable cut and stop refreshing the Unstable announcement thread. Pick the stream that matches your patience, not the one that matches your hype tolerance.