li20034

There is a previous topic on this from 2020, but it's closed and not much action was taken except discussing workarounds. I'd like to continue this. Looking at the kernel configs in this repo, many of them have CONFIG_RT_GROUP_SCHED=y. This does not play nicely with modern systemd (cgroups v2), breaking things like rtkit-daemon. See https://bugs.gentoo.org/569546 and https://bugzilla.redhat.com/show_bug.cgi?id=655321. rtkit is an important part of making pulseaudio and pipewire work smoothly, as well as for many other low-latency applications. There are a few currently available workarounds, but none are ideal: 1. Linux 6.16 or later has boot time param rt_group_sched=0 to override it, but there is still some runtime overhead. No exact alternative for earlier kernels. 2. kernel.sched_rt_runtime_us=-1 in sysctl.conf -- potentially dangerous as it removes the 95% CPU time safeguard for RT processes, leading to lockups when badly behaving processes exist. 3. disable cpu and cpuset cgroup controllers in systemd configs -- has a lot of other side effects, like preventing systemd's CPU limits for services Since the last post on this (linked above), forcefully assigning an rt time time slice won't even work anymore, since cgroup v2 doesn't even have that ability anymore. So this kernel config option is somewhat useless now.

Mint packages its own Chromium as a deb package, whereas Ubuntu's Chromium is a snap (even `apt install` just installs a snap by default). So, all x64 packages work (and I confirmed by testing xtradeb PPA's x64 package, which works). However, it's also not ARM64 related, as the Chromium ARM64 Snap from Ubuntu 24.04 (I just tested that too) works perfectly fine. It's just the ARM64 deb package from xtradeb that seems broken, which is bizarre.

I've seen this same issue with Discord, since March/April this year. Just going to https://discord.com/app (no login necessary) is enough to trigger it. From what I gather, this seems to be some sort of problem with the Chromium build Armbian uses (it appears to be the same build from the xtradeb ppa). This seems to happen on: 1. Raspberry Pi 4 on Armbian Ubuntu Noble 2. Some random Ubuntu VM ARM64 on Apple Silicon using Chromium from xtradeb/apps PPA 3. Dragon Q6A w/ Armbian Ubuntu Noble No workarounds seem to work. Turning off GPU acceleration, disabling sandboxing, etc. all make no difference. But it does not occur on: 1. Google Chrome 2. Chromium 145 or earlier ARM64 from Armbian or Xtradeb PPA, on all devices. Only 146 or later is affected for some reason 3. Linux Mint's Chromium x64 build 4. x64 Chromium snap package on Ubuntu I have not tested xtradeb PPA (or Armbian)'s x64 build of Chromium. Based on the above, I do not think this is an Armbian specific issue. Anyone have any ideas on where to report this?

@Darkseider I'm not sure if you are replying to OP or me, but if you look above at my comment, you will notice that I did run that command, and included the failing output. tldr; Armbian's latest kernel is built with a newer version of gcc (14) than what Ubuntu 24.04 defaults to (13), and dkms does not like that. So it requires some fixes (not sure what exactly) to actually work. This also doesn't just affect me, but in theory at least, should affect anyone using the Ubuntu images (Debian images default to gcc 14 so they should work)

There is supposed to be a package that automatically handles building a (presumably patched) version of the kernel module for this wifi/bt chip, called `aic8800-usb-dkms`, but for some reason, a kernel upgrade doesn't auto-trigger it. During the last kernel upgrade, I was able to get it working by manually doing `sudo dpkg-reconfigure aic8800-usb-dkms`, but that also does not work since 26.5.1, as it gives Deleting module aic8800-usb-4.0+git20250410.b99ca8b6-3 completely from the DKMS tree. Loading new aic8800-usb-4.0+git20250410.b99ca8b6-3 DKMS files... Building for 6.18.2-current-qcs6490 Building initial module for 6.18.2-current-qcs6490 Error! Bad return status for module build on kernel: 6.18.2-current-qcs6490 (aarch64) Consult /var/lib/dkms/aic8800-usb/4.0+git20250410.b99ca8b6-3/build/make.log for more information. And that file basically says (a bunch is redacted for brevity): DKMS make.log for aic8800-usb-4.0+git20250410.b99ca8b6-3 for kernel 6.18.2-current-qcs6490 (aarch64) Sat Jun 20 06:36:14 PM PDT 2026 make: Entering directory '/usr/src/linux-headers-6.18.2-current-qcs6490' make[1]: Entering directory '/var/lib/dkms/aic8800-usb/4.0+git20250410.b99ca8b6-3/build/USB/driver_fw/drivers/aic8800' warning: the compiler differs from the one used to build the kernel The kernel was built by: aarch64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0 You are using: gcc (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0 ... gcc: error: unrecognized command-line option ‘-fmin-function-alignment=8’; did you mean ‘-flimit-function-alignment’? gcc: error: unrecognized command-line option ‘-fmin-function-alignment=8’; did you mean ‘-flimit-function-alignment’? make[4]: *** [/usr/src/linux-headers-6.18.2-current-qcs6490/scripts/Makefile.build:287: aic_load_fw/aic_txrxif.o] Error 1 ... Apparently, the kernel is now built with gcc 14 (which matches the default in Debian Trixie images but not Ubuntu Noble images which have gcc 13). Not sure how to resolve that inconsistency. 1. Install & replace gcc 13 with gcc 14 (just installing won't work as this dkms module build doesn't respect CC env vars); not sure if this will break other things in Ubuntu 24.04 2. Rebuild the kernel with gcc 13; same issue will re-occur on the next kernel upgrade 3. Or something else Just out of curiosity, did you have to mess around with gcc versions to get it to compile (or are you using Debian Trixie images)?