Package Details: linux-mainline-headers 6.15rc1-1

Git Clone URL: https://aur.archlinux.org/linux-mainline.git (read-only, click to copy)
Package Base: linux-mainline
Description: Headers and scripts for building modules for the Linux Mainline kernel
Upstream URL: https://kernel.org/
Licenses: GPL-2.0-only
Submitter: miffe
Maintainer: miffe
Last Packager: miffe
Votes: 290
Popularity: 1.86
First Submitted: 2011-07-22 06:50 (UTC)
Last Updated: 2025-04-06 22:33 (UTC)

Pinned Comments

miffe commented on 2020-01-30 21:44 (UTC)

Repository here

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 93 Next › Last »

sigxcpu commented on 2024-12-22 16:19 (UTC)

efi_pstore.pstore_disable=0 should not be related to login. It just allows the kernel to store the dmesg output outside of the system main disk when crashing, so you can recover some dumps after rebooting.

xuwd1 commented on 2024-12-22 15:24 (UTC) (edited on 2024-12-22 15:27 (UTC) by xuwd1)

I do have a suggestion for the guys having the freeze problem: check your bios version and consider update it to the latest versions like 312and 315. I noticed that it seems that dear T1c’s laptop has been using the 312 bios version. There are quite a few discussions I saw on Reddit saying that the newer bios version enhanced the system stability, though the majority of people are using Windows. However do note that it seems that bios version >=309 lowered the power limit thus performance drop should be expected. But also I think the 315 bios fixed the core2core latency problem so it’s still worth considering.

podulator commented on 2024-12-22 14:11 (UTC)

Also have to report the gpu freeze. Tried the efi_pstore.pstore_disable=0 grub option, but that prevented login after crash (kde + wayland), so reverted. Tried with 0x600 and 0x612, still happens.

That1Calculator commented on 2024-12-21 17:05 (UTC)

@sigxcpu can't reproduce the first or third issues, but for the second, use asus-um5606-fan-state instead

sigxcpu commented on 2024-12-21 16:17 (UTC)

This laptop is mostly stable for me, with the following caveats:

  • sometimes (~1/8) the touchpad acts in a very weird way - random jumps and/or clicks
  • sometimes (~1/10) the CPU is stuck in low power mode (2GHz), regardless of the cpu profile selected with asusctl
  • sometimes (~1/20) the amdgpu 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.

fallingcats commented on 2024-12-21 12:38 (UTC)

@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.

VanKurt commented on 2024-12-21 12:22 (UTC)

@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?

sigxcpu commented on 2024-12-21 07:57 (UTC) (edited on 2024-12-21 07:57 (UTC) by sigxcpu)

@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)

VanKurt commented on 2024-12-21 06:33 (UTC)

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...

zkurdi commented on 2024-12-19 05:22 (UTC)

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

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 93 Next › Last »