| Git Clone URL: | https://aur.archlinux.org/linux-mainline.git (read-only, click to copy) |
|---|---|
| Package Base: | linux-mainline |
| Description: | The Linux Mainline kernel and modules |
| Upstream URL: | https://kernel.org/ |
| Licenses: | GPL-2.0-only |
| Provides: | KSMBD-MODULE, NTSYNC-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE |
| Replaces: | virtualbox-guest-modules-arch, wireguard-arch |
| Submitter: | miffe |
| Maintainer: | miffe |
| Last Packager: | miffe |
| Votes: | 298 |
| Popularity: | 1.47 |
| First Submitted: | 2011-07-22 06:50 (UTC) |
| Last Updated: | 2026-07-21 04:45 (UTC) |
This laptop is mostly stable for me, with the following caveats:
asusctlamdgpu driver crashes (with logs in pstore)The above numbers are pulled more or less out of a hat and the denominator shows the cycles of suspend/resume. Everything works fine after a reboot.
@sigxcpu @VanKurt Neither 0x612 nor the pstore work for me. I'm mainly getting crashes that completely kill the kernel dead (screen frozen, no caps blinking, no sysrq reboot anymore)
Those mostly happen while streaming video from a nas over nfs over wifi to mpv.
@sigxcpu Thanks for the hint. I tried that, but the folder is empty. Had two crashes so far, but none seems to have produced any data. Does 0x612 give you better (stable) results?
@VanKurt: to find crashlogs, add this to your kernel command line: efi_pstore.pstore_disable=0
After a freeze, reboot and go to /sys/fs/pstore and there you will find bits of dmesg.
Btw, I am also running this with amdgpu.dcdebugmask=0x612 (0x600 and 0x12, from two suggestions: phoronix I guess and the arch install page for this laptop)
After testing for several days now, I still have random freezes, no matter what I do: in VS Code, in Nautilus or while streaming a video. I installed the latest BIOS from Asus, updated linux-firmware-git and use the 13rc3 version of this kernel. -> Is there a way to find out where the freezes come from? (stack traces, logs, dump files etc.) I would really like to get to the bottom of this and make the machine work reliably...
brothers I can't seem to control the brightness My system: -S16 ryzen ai 370 -this kernel@latest -kde plasma 6.2 w/ wayland
the problem:
I can't seem to change the brightness by any method
-> I first tried with the slider: no change and cat /sys/class/backlight/amdgpu_bl1/actual_brightness is showing no change.
-> Then I tried brightnessctl which changes the cat output but doesn't change the screen
also I have noticed that if I run journalctl -f I see the following
Dec 18 21:18:20 s16 google-chrome-stable[1897]: [1218/211820.262463:ERROR:file_io.cc(103)] ReadExactly: expected 32, observed 0
Dec 18 21:21:15 s16 plasmashell[1439]: The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce.
Dec 18 21:21:15 s16 plasmashell[1439]: ignoring brightness change, it's coming from the applet itself
Dec 18 21:21:15 s16 systemd[1]: Started dbus-:1.3-org.kde.powerdevil.backlighthelper@3.service.
Dec 18 21:21:16 s16 plasmashell[1439]: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce.
Dec 18 21:21:16 s16 plasmashell[1439]: kf.windowsystem.wayland: Failed to recreate shadow for PlasmaQuick::AppletPopup(0x55bdd57c2720, name="popupWindow")
Dec 18 21:21:16 s16 plasmashell[1439]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0
Dec 18 21:21:25 s16 systemd[1]: dbus-:1.3-org.kde.powerdevil.backlighthelper@3.service: Deactivated successfully.
anyone have any idea what is going on. thank you Mister maintainer for your hard work
Is there a reason why the linux-mainline-um5606-headers isn't marked as: provides linux-headers?
@That1Calculator have you noticed this new warning when running mkinitcpio with the new 6.13-rc2 kernel?
==> WARNING: No module containing the symbol 'drm_privacy_screen_register' found in: 'drivers/platform'
It looks like there was change on module compress config:
$ grep CONFIG_MODULE_COMPRESS src/linux-mainline/.config
> # CONFIG_MODULE_COMPRESS is not set
If you perform the same grep on src/linux-mainline/.config.old you get:
$ grep CONFIG_MODULE_COMPRESS src/linux-mainline/.config.old
> # CONFIG_MODULE_COMPRESS_NONE is not set
> # CONFIG_MODULE_COMPRESS_GZIP is not set
> # CONFIG_MODULE_COMPRESS_XZ is not set
> CONFIG_MODULE_COMPRESS_ZSTD=y
Pinned Comments
miffe commented on 2020-01-30 21:44 (UTC)
Repository here