Package Details: linux-amd 6.8.v.8-2

Git Clone URL: https://aur.archlinux.org/linux-amd.git (read-only, click to copy)
Package Base: linux-amd
Description: Linux kernel aimed at the ZNVER4/MZEN4 AMD Ryzen CPU based hardware
Upstream URL: https://www.kernel.org/
Licenses: GPL2
Submitter: None
Maintainer: archdevlab
Last Packager: None
Votes: 30
Popularity: 0.92
First Submitted: 2019-11-10 15:20 (UTC)
Last Updated: 2024-04-29 09:32 (UTC)

Pinned Comments

<deleted-account> commented on 2023-05-04 16:38 (UTC)

GCC13.1 is mainlined in arch, so this means znver4 support can kick off on this kernel. The graysky compile patches have been updated too.

This kernel now natively supports the znver4 arch, but this kernel will most likely keep working on all AMD ryzen hardware. It's better to be able to address certain small perks or issues per architecture now and in the future.

If you use znver3 based hardware, please use linux-amd-znver3
If you use znver2 based hardware, please use linux-amd-znver2
If you use raven based hardware, please use linux-amd-raven

<deleted-account> commented on 2020-10-26 18:15 (UTC)

GCC11.1 is mainlined in arch, so this means znver3 support can kick off on this kernel. The graysky compile patches have been updated too.

This kernel now natively supports the znver3 arch, but this kernel will most likely keep working on all AMD ryzen hardware. It's better to be able to address certain small perks or issues per architecture now and in the future.

If you use znver2 based hardware, please use linux-amd-znver2
If you use raven based hardware, please use linux-amd-raven

<deleted-account> commented on 2019-11-10 15:23 (UTC)

Tired of compiling? Use this binary repo instead! Add this at the end of /etc/pacman.conf :

[linuxkernels]
Server = http://nhameh.ovh/$repo/$arch
SigLevel = Optional TrustAll

Latest Comments

« First ‹ Previous 1 .. 29 30 31 32 33 34 35 36 Next › Last »

usuariopolivalen commented on 2020-03-20 11:17 (UTC)

@eggz thanks for mantain that patch I am not sure if my girlfriend is the only person who uses it.. but much thanks.

<deleted-account> commented on 2020-02-26 12:16 (UTC)

If I had the time, I'd flood that asuswmi module with printing debug info so I'd get to know the kernel ACPI modules and all that, but for now, I'm glad the experts are taking a look at it in my place :)

usuariopolivalen commented on 2020-02-26 11:48 (UTC)

@eggz luck with your pc, wish you can fix it

<deleted-account> commented on 2020-02-25 07:28 (UTC)

I'm not sure what you mean, the suggested patch in that code is the exact same thing as the current patch I offer. theres just a linebreak right in the middle, maybe the coder was using a windows with a small putty screen? xD. And I will say the same as I always do when during workhours: If I did this stuff just for the credit, Man, I would have dried and burned out a long time ago. It is not needed, I'm just glad I could help. Also most of it was about your suggestion, so you actually found it :-)

usuariopolivalen commented on 2020-02-24 21:51 (UTC)

@eggz https://www.spinics.net/lists/platform-driver-x86/msg20929.html the patch is sent. Can you build your kernel with thaat patch for testing? It is suppose to be your patch anyways :)

PD: thanks in advance, thanks anyway, and much thnanks for all :) wanna credit for this? I think I can try to do it if you want

usuariopolivalen commented on 2020-02-22 12:51 (UTC)

It should be accepting at least the limits on the charge. Try in Windows if you can please if not. Pls give info in that link. https://gist.github.com/klausenbusk/643f15320ae8997427155c38be13e445

<deleted-account> commented on 2020-02-22 10:30 (UTC)

@agm yeah about being busy, I know the feeling :) Im working on it now.

I have a GL702ZC, it was the first ryzen laptop for ASUS, So I think they gave it a B treatment back then. (it shipped with a broken BIOS, and they updated it later...)

usuariopolivalen commented on 2020-02-22 01:08 (UTC)

@eggz both of them were working good :) sorry for the late response i have been very busy these days. I am now having the file that control the charges and the limits are working with the backwards compability. What asus are you using? it is something weird that your asus wmi doesn't control the battery

<deleted-account> commented on 2020-02-20 20:27 (UTC)

Can you say if it was the dirty BATT override (-3 http://nhameh.ovh/linuxkernels_archive/linux-amd-5.5.v.4-3-x86_64.pkg.tar.xz, http://nhameh.ovh/linuxkernels_archive/linux-amd-headers-5.5.v.4-3-x86_64.pkg.tar.xz) or the backwards compatibility one (-2 http://nhameh.ovh/linuxkernels_archive/linux-amd-5.5.v.4-2-x86_64.pkg.tar.xz, http://nhameh.ovh/linuxkernels_archive/linux-amd-headers-5.5.v.4-2-x86_64.pkg.tar.xz) that worked? I really liked my way better...

I never had the file so asuswmi is not working for my hardware at all. But I can patch it for other people like you.

usuariopolivalen commented on 2020-02-20 18:58 (UTC)

@eggz sorry. Put the patch of Asus again with you backwards compability please. The limits of the battery were working good. But only 80, 60 and 100 percent values are accepted, with other values the laptop just ignore them. Try to edit that file. You will get limits on your battery charge.