Package Details: linux-amd-znver3-headers 6.13.v.2-1

Git Clone URL: https://aur.archlinux.org/linux-amd-znver3.git (read-only, click to copy)
Package Base: linux-amd-znver3
Description: Header files and scripts for building modules for the linux-amd-znver3 kernel
Upstream URL: https://www.kernel.org/
Licenses: GPL2
Submitter: None
Maintainer: None
Last Packager: bebna
Votes: 10
Popularity: 0.012806
First Submitted: 2023-05-04 15:47 (UTC)
Last Updated: 2025-02-16 11:21 (UTC)

Dependencies (9)

Required by (0)

Sources (2)

Latest Comments

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

<deleted-account> commented on 2023-12-08 09:28 (UTC)

Hello, please refer to https://wiki.archlinux.org/title/Pacman/Pacnew_and_Pacsave and https://wiki.archlinux.org/title/mkinitcpio. I do not manage these packages or package managers or their behaviour, which practicly and effectively means I cannot make any diffrence whatsoever on the way they work and do things. Thanks.

deemon commented on 2023-12-08 09:08 (UTC) (edited on 2023-12-08 09:43 (UTC) by deemon)

for some reason this package (alone) always generates new /etc/mkinitcpio.d/linux-amd-znver3.preset.pacsave, which is identical to the previous /etc/mkinitcpio.d/linux-amd-znver3.preset.

(5/5) Checking for .pacnew and .pacsave files...
.pac* files found:
/etc/mkinitcpio.d/linux-amd-znver3.preset.pacsave
Please check and merge: sudo DIFFPROG=meld pacdiff
$ md5sum /etc/mkinitcpio.d/linux-amd-znver3.preset /etc/mkinitcpio.d/linux-amd-znver3.preset.pacsave
00fc0e0152f0b7319e292a0477d41975  /etc/mkinitcpio.d/linux-amd-znver3.preset
00fc0e0152f0b7319e292a0477d41975  /etc/mkinitcpio.d/linux-amd-znver3.preset.pacsave
$ sudo DIFFPROG=meld pacdiff
==> pacsave file found for /etc/mkinitcpio.d/linux-amd-znver3.preset
  -> Files are identical, removing...
removed '/etc/mkinitcpio.d/linux-amd-znver3.preset.pacsave'

can this .pacsave generation be turned off for it, when nothing changed? or the forceful /etc/mkinitcpio.d/linux-amd-znver3.preset overwrite every time, that triggers pacsave generation?

deemon commented on 2023-11-12 16:06 (UTC) (edited on 2023-11-13 16:33 (UTC) by deemon)

Something is rather weird about this latest iteration of this kernel. UI becomes ocasionally unresponsive for second or 2 making the entire experience rather laggy feeling. And then got this weird message in dmesg: [P nov 12 17:34:47 2023] sched: RT throttling activated. Is this the new scheduler crap introduced in Linux 6.6 that's causing this? Started to look into the laggy programs problem and discovered that they had several processes with nice 19 set. after renice'ing them back to 0 the lag disappeared from those. ... sooo .... this required manual intervention is rather unpleasant and counterproductive when this nice:19 thing indeed done by the new scheduler :-(

<deleted-account> commented on 2023-10-29 11:26 (UTC)

No idea. Maybe your CPU RNG timings were having a cold.

Anarconda commented on 2023-10-29 08:27 (UTC)

Hi, I'm really confused about the jitterentropy message. I mean, the message is gone:

┌─[09:23:34]─[amarcord@Gaia-A]
└──> ~ $ >> uname -a
Linux Gaia-A 6.5.9-AMD-znver3 #1 SMP PREEMPT_DYNAMIC Thu Oct 26 08:53:45 CEST 2023 x86_64 GNU/Linux
┌─[09:23:37]─[amarcord@Gaia-A]
└──> ~ $ >> dmesg | grep jitterentropy
┌─[✗]─[09:23:42]─[amarcord@Gaia-A]
└──> ~ $ >>

Isn't a kernel related message, then?

<deleted-account> commented on 2023-10-28 14:08 (UTC)

@iseja ty for the heads up!! rebuilds coming up.

Iseja commented on 2023-10-28 12:42 (UTC)

Please enable CONFIG_UNICODE, casefolding on ext4 needs that.

<deleted-account> commented on 2023-10-25 16:45 (UTC)

Okay well I'll commit that change regardless. I think this is a really random thing (like a race timing condition like mentioned) and its not worth losing your mind over...

Anarconda commented on 2023-10-25 16:39 (UTC)

@eggz 1. It seems I was wrong because linux-cachyos-lto 6.5.9 shows the same message. 2. ArchLinux Zen 6.5.8 doesn't 3. Your kernel whith CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE=n shows the message.

<deleted-account> commented on 2023-10-25 15:23 (UTC)

On second thought I think it might be CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE that does it. Let me fire up a build for you. (because I am going to disable it regardless)

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