Most of this is invisible, and it's the release where the kernel stopped quietly lacking things people assume are there: systemd's memory limits did nothing, a laptop's USB-C DisplayPort wasn't there, some laptops had silent speakers, and crash dumps were thrown away on purpose.
PengyOS builds its kernel as x86_64_defconfig plus three fragments, which means anything nobody
thought to add was off, silently. A diff against Ubuntu 26.04's config found 7,514 options it enables
and we don't. Nearly all are drivers for specific hardware. About 150 infrastructure options were worth
checking, and these were missing:
- cgroup v2 memory control and BPF (
MEMCG,BPF_SYSCALL,CGROUP_BPF). systemd'sMemoryMax=,DeviceAllow=andIPAddressDeny=were set in units and did nothing. - The BPF JIT, PSI, and
intel_idle. Intel CPUs had been using onlyacpi_idle's C-states. - Native PCIe hotplug, plus AER and DPC. NVMe bays and USB4 tunnels need hotplug, and without AER a PCIe link error hangs instead of being logged and recovered.
- pstore in EFI variables, so a kernel panic's log survives the reboot.
- Transparent huge pages (madvise) and the multi-generational LRU. zswap stays off because swap is zram.
- Server: SR-IOV and the SMB/CIFS client.
- Desktop, mostly laptops: USB-C through UCSI with DisplayPort alt mode;
platform_profilefor Lenovo GameZone and AMD PMF, without which power-profiles-daemon had nothing to switch; Intel DPTF;serial-multi-instantiate, without which Cirrus CS35L41-class speaker amps never bind and a lot of HP, Lenovo and ASUS laptops have silent speakers; and HDA codec power save on by default, worth about 6 W on battery on one laptop.
Kconfig drops a fragment line whose dependencies aren't met without saying anything. The core post-build
now runs the fragment check with --built against the kernel's resolved .config and fails the build on
a dropped line, and a new kernel-required.txt lists the options every edition relies on only the base
defconfig provides, so a kernel bump can't take one away unnoticed.
Fixes a person can see. Every edition had enabled a login on ttyS0 whether or not the machine had a
serial port, and the kernel always creates ttyS0, so on a laptop with no UART agetty failed and
restarted every 10 seconds, forever, two journal lines each time. The getty port is tty1 now, and
systemd's getty generator still starts a serial login when GRUB found a real UART. switcherooctl
started with the build host's Python and failed; its shebang is the image's.
Battery: the discrete GPU never left D0, at about 23 W on battery even with nothing holding
/dev/nvidia*. CONFIG_VGA_SWITCHEROO was unset, so snd_hda_intel never enabled runtime PM for the
GPU's own HDMI audio function, and the kernel's GPU/audio device link kept the GPU awake. Then the slot
still wouldn't lose power, because its root port is a hotplug port and without CONFIG_HOTPLUG_PCI_PCIE
the kernel refuses D3 for those. With both on, the GPU and its root port reach D3cold within seconds of
boot; a CUDA and Vulkan job wakes it in 1.8 s and it's back in D3cold within 25 s. A udev rule that was
supposed to handle AMD runtime PM was deleted: its card[0-9]* match fired on every DRM connector, its
delay write failed on the real card, and it produced about 12 udev errors per boot while doing nothing.
Two quality-of-diagnosis things. Every edition ships systemd-coredump now: before, kernel.core_pattern
was |/bin/false, so a crash left one kernel line and nothing else. Now a crash logs a stack trace and
coredumpctl list / info show what died. Storage is capped, because a browser or Steam dump alone can be
gigabytes: the store never exceeds 1 GB, never leaves less than 10 GB free, and a process over 2 GB keeps
only its journal backtrace. And every binary the toolchain links carries a GNU build-id, 36 bytes each,
which is what matches a dump to the unstripped binary in the build tree.
The agent in the images went 1.11.5 → 1.12.3. The pin had been pinned 1.11.5 since 26.10.24 and stopped moving while upstream released four versions.