Package Details: linux-mainline-um5606 1:6.12rc7-2

Git Clone URL: https://aur.archlinux.org/linux-mainline-um5606.git (read-only, click to copy)
Package Base: linux-mainline-um5606
Description: The Linux Mainline with patches for the Asus UM5606(WA) laptop kernel and modules
Upstream URL: https://kernel.org/
Keywords: asus
Licenses: GPL-2.0-only
Provides: KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Replaces: virtualbox-guest-modules-arch, wireguard-arch
Submitter: That1Calculator
Maintainer: That1Calculator
Last Packager: That1Calculator
Votes: 3
Popularity: 2.19
First Submitted: 2024-08-07 22:07 (UTC)
Last Updated: 2024-11-16 17:21 (UTC)

Dependencies (16)

Sources (4)

Pinned Comments

That1Calculator commented on 2024-11-14 13:12 (UTC)

A reminder to please take discussions about these patches on other distros to an appropriate channel :)

That1Calculator commented on 2024-10-07 15:57 (UTC) (edited on 2024-10-21 21:10 (UTC) by That1Calculator)

Updated to 6.12rc2, most of the old patches (keyboard, bluetooth, zsc etc) are now in upstream! This package is now only useful for the heterogeneous CPU patch (performance & efficiency increases) and the NPU patch (currently no practical use case)

Latest Comments

1 2 3 4 Next › Last »

travisghansen commented on 2024-11-17 14:29 (UTC)

I will give rc7 a try. To be clear, all of my testing has been on arch.

That1Calculator commented on 2024-11-14 13:12 (UTC)

A reminder to please take discussions about these patches on other distros to an appropriate channel :)

That1Calculator commented on 2024-11-14 13:12 (UTC)

While rc6 was stable for some and unstable for others, rc7 seems to be stable for everyone!

travisghansen commented on 2024-11-11 01:59 (UTC)

It's funny this got rolled back, rc6 is only build that has been stable for me. Running with the stock drive, I haven't tried to swap that out yet with rc6 but I have it running for 4 days straight with no crashes and looping through videos in youtube the whole time. I've suspended/resumed several times and that seems to work (still have a delay on resume). Hopefully the freshly released rc7 proves a happy build as well.

bob418 commented on 2024-10-28 05:41 (UTC)

It's 24.10.

travisghansen commented on 2024-10-28 00:40 (UTC)

Hi sorry for the delay, I have the 990 pro. I assume you mean ubuntu 24.10? If so I will give that a try on the stock ssd.

I find it really odd that the ssd would cause issues, I have never seen that be an issue before so does this machine have a new controller or something?

bob418 commented on 2024-10-25 03:45 (UTC)

@travisghansen, which Samsung NVME do you use? I previously used a 2TB 980 Pro and got more issues. Later I switched to Crucial T500 2TB Gen4 and the system seemd to have much less issues. Now I mainly use EndeavourOS KDE (with this kernel) and Ubuntu 22.10 (kernel 6.11.0.9). EndeavourOS still freezes occationally after waking up if I leave with Firefox tab playing Youtube with hardware accelaration. Ubuntu is rock-solid but bluetooth doesn't work yet. Ubuntu also wakes up immediately while EndeavourOS needs to wait about 10 seconds.

travisghansen commented on 2024-10-24 17:48 (UTC)

Yeah, rc4 is still entirely unusable for me. I am starting to wonder if there is some incompatibility with my samsung nvme, the desktop crashes and ultimately leaves me at the tty showing io errors on the fs (systemd/journald trying to rotate logs seemingly).

travisghansen commented on 2024-10-23 21:45 (UTC)

I will try what @bob418 suggested. In general the laptop has been entirely unusable for me with all the different kernel variants and even with the mask settings.

I generally get a symptom of disk issues (I put my own nvme that I swap out of my daily driver in there) so not sure if that has some incompatibility or if it really is just the symptom. If anyone has tips on how to get useful debugs/traces when lockups occur happy to share what those are.

bob418 commented on 2024-10-23 01:57 (UTC)

Installed this kernel (linux-mainline-um5606 6.12rc4-1) on EndeavourOS KDE and got 2 freezes very quickly. Still need to set "amdgpu.dcdebugmask". After some tests I use "amdgpu.dcdebugmask=0x10 amdgpu.sg_display=0" right now and it seems very stable.

1 2 3 4 Next › Last »