Package Details: linux-g14-headers 6.15.4.arch1-1

Git Clone URL: https://aur.archlinux.org/linux-g14.git (read-only, click to copy)
Package Base: linux-g14
Description: Headers and scripts for building modules for the Linux-g14 kernel
Upstream URL: https://gitlab.com/dragonn/linux-g14.git
Keywords: ASUS G14 ROG Zephyrus
Licenses: GPL-2.0-only
Provides: linux-rog-headers
Submitter: dragonn
Maintainer: Taijian
Last Packager: Taijian
Votes: 10
Popularity: 0.043112
First Submitted: 2020-06-06 15:43 (UTC)
Last Updated: 2025-07-02 13:04 (UTC)

Latest Comments

1 2 3 4 5 6 .. 11 Next › Last »

archiso7 commented on 2025-07-02 11:56 (UTC)

@Taijian, sha246 checks now pass, but applying the 0000-asus-patch-series.patch fails. patching file drivers/hid/hid-asus.c Hunk #1 FAILED at 624. Hunk #2 FAILED at 1381. Hunk #3 succeeded at 1327 (offset -103 lines). 2 out of 3 hunks FAILED -- saving rejects to file drivers/hid/hid-asus.c.rej

I would also send the contents of drivers/hid/hid-asus.c.rej but I cannot find the file.

archiso7 commented on 2025-07-01 22:44 (UTC)

@Taijian, 0000-asus-patch-series.patch is failing the sha256 check again. I've checked the PKGBUILD file directly on the AUR and the sha256sum is different from the 0000-asus-patch-series.patch file.

sha256sum 0000-asus-patch-series.patch 3a283bfb37070f31418c5d36530734f83306a1c831d33b2f36950e86cf59642e 0000-asus-patch-series.patch

pashax commented on 2025-03-24 13:25 (UTC)

@Taijian, I'm usually just deleting files that don't pass the sha256 check. In this case it was just "0000-asus-patch-series.patch". And I'm running "makepkg -sicC" which suppose to do all other clean up for me. But yeah, I see that issue that my PKGBUILD wasn't updated with a new hash for some reason. And that's supper odd, since any time I'm doing git pull, git complains on my custom uncommitted changes in PKGBUILD (I'm updating all microarchitecture values), so I have to run "git reset --hard" to restore repo state. Anyway, works now. Thank you!

Taijian commented on 2025-03-24 12:55 (UTC)

@pashax:2baff989b4ab826897f7da8c6fa3b25dea542ffedc9581eb45063a34a869cb6b is the exact sha256sum that is in the PKGBUILD for that file.

Have you tried cleaning up your build directory before building this package, so that all external patches can get re-downloaded with the correct version?

pashax commented on 2025-03-24 12:19 (UTC)

Hey @Taijian, I'm still having issues with 0000-asus-patch-series.patch.

0000-asus-patch-series.patch ... FAILED

$ sha256sum 0000-asus-patch-series.patch 2baff989b4ab826897f7da8c6fa3b25dea542ffedc9581eb45063a34a869cb6b 0000-asus-patch-series.patch

Taijian commented on 2025-03-21 22:04 (UTC)

@drpars: It could certainly be done, especially with the ability to go back through the commit history of both this package and the fedora patch set - however this would be a bit of an effort, because the patches would have to be adapted to the different code base and some patches would have to be revived, that are already in this kernel, but not in the lts one.

So why don´t I patch the lts kernel? Too much work for something I would not personally be using.

drpars commented on 2025-03-21 17:25 (UTC)

Why don't you patch the "linux-lts" kernel as well? Or can you?

Taijian commented on 2025-03-17 11:31 (UTC)

@katalysatorn: Oooops! Fixed now!

katalysatorn commented on 2025-03-17 03:47 (UTC)

linux-6.13.7.tar.xz linux-v6.13.7-arch1.patch.zst config 0000-asus-patch-series.patch

Above packages have incorrect sha256sums for latest release

JimMoen commented on 2025-02-06 06:31 (UTC)

file 0000-asus-patch-series.patch has changed. plz bump new sha256sum of the file.

1 2 3 4 5 6 .. 11 Next › Last »