Package Base Details: linux-amd-znver2

Git Clone URL: https://aur.archlinux.org/linux-amd-znver2.git (read-only, click to copy)
Submitter: eggz
Maintainer: eggz (NhaMeh)
Last Packager: eggz
Votes: 16
Popularity: 0.95
First Submitted: 2020-10-26 18:04 (UTC)
Last Updated: 2024-04-13 17:47 (UTC)

Pinned Comments

eggz commented on 2020-10-26 18:15 (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 .. 3 4 5 6 7 8 9 10 11 12 13 .. 15 Next › Last »

dedguy21 commented on 2022-01-12 02:49 (UTC) (edited on 2022-01-12 03:06 (UTC) by dedguy21)

I'm sorry wasn't trying to be offensive, I really was just wondering.

But I think you are not understanding what I'm talking about.

Every kernel that is compiled has the possibility of excluding modules, this would be the first one where I just didn't see the option in the pkgbuild.

Modprobed-db provides this functionality for 99.9% of the custom kernels on arch to make that an easy process for the end user:

make LSMOD=$HOME/.config/modprobed.db localmodconfig ---remove all the modules not present in the modprobed.db database

Again, usually that option is available and I didn't see it in the pkgbuild, thought I was missing something.

You already provide a compiled package for download, I guess if it's no benefit to compiling that's just what I'll do.

But if you can't remove the excess modules during compile, why compile at all?

Again just wondering...

eggz commented on 2022-01-11 23:38 (UTC) (edited on 2022-01-11 23:39 (UTC) by eggz)

And where exactly do you want that "option" to be? I think I get the main idea of what you are trying to say but I'm not really sure. This kernel comes with a config and patches that I deem best for znver2, and its static. If you want to change the buildproces to something dynamic towards your system and preferences, I am unsure what you need this kernel for ... ?

dedguy21 commented on 2022-01-11 20:17 (UTC)

Hi, Just wondering

Am I missing where the option to build this with only ldconfig (only using the modules that are loaded with modprobed-db)?

There are a lot of modules I'm trying not to include in the build

PeerK commented on 2021-10-10 14:39 (UTC)

Thank you very much: As you see, I am not an expert ;) I changed makepkg.conf .

eggz commented on 2021-10-10 13:58 (UTC)

"Maybe the option "-j(Nr_of_cores-2)" as default might be a useful parameter?"

I dont control that variable, its provided by makepkg.conf, which is provided by core/pacman. I can only give you my experiences, and I had a situation where I had to do a "nr_of_cors+ 2+" -J flag.

I'm just glad you found your problem :-)

PeerK commented on 2021-10-10 13:16 (UTC) (edited on 2021-10-10 13:17 (UTC) by PeerK)

I have 8 cores, single threaded (4700U, laptop) and I tested the build process with -j4 and -j6, since I was still logged on.

Although I did not benchmark the processes precisely, -j6 built the kernel in a few minutes, while the default from the package was inacceptable long while the cores were sleeping ;-)

Maybe the option "-j(Nr_of_cores-2)" as default might be a useful parameter?

Thanks for the hint with -O3, I reset it to the default. Kind regards

eggz commented on 2021-10-10 10:35 (UTC)

how much cores you have and how many workers you pick? try adding 5 workers more than your threads and see what happens.

Be careful with choosing -O3, not all makefiles/packages support this and you might run into compatibility issues.

PeerK commented on 2021-10-10 10:26 (UTC)

For the last few kernel updates, the build process does not run on all availiable core.

Since this takes obviously much, much more time, I wondered if there is a technical reason, not to use on all the cores any more.

I am a noob, but I wonder, if "-j <no. of cores - 1>" in $MAKEFLAGS and "-O3" in $CFLAGS could speed up building the kernel.

Cheers,

s3rj1k commented on 2021-09-30 13:10 (UTC)

@eggz provides=linux description in wiki about reasons are quite full, but I wonder, what will happen if one would actually add this to a PKGBUILD, lets say separate one, specificaly tailored to replace existing default kernel, I mean like, would arch people take this AUR package down or it would just block a merge to community repo.

Would like to here a comment about that from Arch people.

eggz commented on 2021-09-30 04:39 (UTC)

sorry bkuri, I got told by arch linux staff not to do so. I find it annoying aswel.

https://aur.archlinux.org/pkgbase/linux-amd-znver2/?O=60&PP=10#comment-780129 https://aur.archlinux.org/pkgbase/linux-slim/?O=10&PP=10#comment-781913