Thanks for this!
Follow on question, which source(s) is best to use for CPU temp? I’ve got quite a few different ones that seem to qualify for the CPU in some way. Got a Ryzen 3800
Thanks for this!
Follow on question, which source(s) is best to use for CPU temp? I’ve got quite a few different ones that seem to qualify for the CPU in some way. Got a Ryzen 3800
My understanding …
Tdie is the temperature on the die, which is the one you want.
Tctl is the control temperature reported to the cooling system, with a 20C offset is to get it to trigger sooner … I think.
Would it be possible to leave the default zstd
in place and create or change a preset in /etc/mkinitcpio.d/
with gzip
for those kernels?
I don’t think you can have different compression settings for different kernel versions with mkinitcpio. If you configure gzip then all initramfs images will be gzip compressed.
Maybe you can with dracut, it is supposed to be much more configurable than mkinitcpio … but I don’t know dracut very well.
Funny thing is that my laptop boots into a black screen with the mainline kernel for ages.
And the same with the new LTS .
But, I downloaded the newest iso and booted fine with kernel 5.10.
Graphics:
Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx
Integrated Graphics
driver: i915 v: kernel
Device-2: Suyin Integrated_Webcam_HD type: USB driver: uvcvideo
Display: x11 server: X.Org 1.20.10 driver: loaded: intel
unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 400 (BSW) v: 4.6 Mesa 20.3.4e code here
A really good question. On some I go with Tdie, on others I go with Tccd1. When available, I find it tracks better (apparently) with what is shown in the BIOS - and doesn’t jump around as much. With less jumping, you can actually get an idea of what’s going on, without oversampling as much…
Strange times, indeed. An old laptop (Toshiba) was struggling with 5.10 mainline, so I went to LTS. However, the “NEW” LTS seemed to hang for a while, then booted up and runs fine (so far). No figuring it out without code guru status, I suspect…
Wow
That’s a fast moving LTS. Today only, two updates. I’m beginning to sweat…
I had the same issue on my 2 year-old Asus laptop with the initial 5.10.16-1
LTS kernel. It is one of those dreaded Optimus laptops and I use the Optimus-Switch solution. Running the set-nvidia.sh
script, thus copying over the needed configuration files for nVidia, fixed the issue. After updating to the 5.10.16-2
LTS kernel, there were no problems at all.
Which one are you talking about “When available”?
On my Ryzen 7 3700x, on an Asus Tuf Gaming X570, I have the choice:
┌12:59:58 WD= [~/Downloads]
└───freebird@nest ─▶$ sensors
nvme-pci-0300
Adapter: PCI adapter
Composite: +37.9°C (low = -60.1°C, high = +89.8°C)
(crit = +94.8°C)
amdgpu-pci-0800
Adapter: PCI adapter
vddgfx: 950.00 mV
fan1: 1209 RPM (min = 0 RPM, max = 4500 RPM)
edge: +44.0°C (crit = +94.0°C, hyst = -273.1°C)
power1: 39.24 W (cap = 135.00 W)
k10temp-pci-00c3
Adapter: PCI adapter
Tctl: +54.8°C
Tdie: +54.8°C
Tccd1: +35.5°C
On my Ryzen 5 2400G, however, these are my choices:
┌13:06:14 WD= [~]
└───freebird@aerie ─▶$ sensors
nvme-pci-0800
Adapter: PCI adapter
Composite: +29.9°C (low = -273.1°C, high = +84.8°C)
(crit = +84.8°C)
Sensor 1: +29.9°C (low = -273.1°C, high = +65261.8°C)
Sensor 2: +30.9°C (low = -273.1°C, high = +65261.8°C)
amdgpu-pci-0900
Adapter: PCI adapter
vddgfx: N/A
vddnb: N/A
edge: +37.0°C
k10temp-pci-00c3
Adapter: PCI adapter
Tctl: +37.1°C
Tdie: +37.1°C
More choices on newer chips, too…
Ah I see! Running sensors
a few times myself, it certainly appears that Tctl & Tdie don’t seem to report different temps. Tccd1 is usually lower by a few degrees for me as well.
AMD has two sensors for CPU’s. One is the die temp of the actual chip and fluctuates more the other is the socket temp which is usually a bit lower and more stable.
Tctl is not guaranteed to be a real temperature - it is generated some ‘other’ way for use as a control for setting fan speeds and boost parameters etc…
Yes. You could make a new file and call it mkinitcpio-gzip.conf
with the same content of the “normal” one and change and set the compression to gzip.
Then edit the relevant preset files for the kernel in questions (those you want to compress with gzip
) to point to this new file. You will have then different compressions for different kernels. One for those pointing to mkinitcpio.conf
and another for those pointing at mkinitcpio-gzip.conf
Example:
I have two kernel, linux-zen and linux-lts installed. Both using lz4 as compression algorithm. Now I want linux-lts to be compressed with gzip:
MODULES=“crc32c”
BINARIES=()
FILES=“”
HOOKS=“base udev autodetect modconf block keyboard keymap resume filesystems”
#COMPRESSION=“gzip”
#COMPRESSION=“bzip2”
#COMPRESSION=“lzma”
COMPRESSION=“xz”
#COMPRESSION=“lzop”
#COMPRESSION=“lz4”
#COMPRESSION_OPTIONS=()
ALL_config=“/etc/mkinitcpio-gzip.conf”
ALL_kver=“/boot/vmlinuz-linux-lts”
PRESETS=(‘default’ ‘fallback’)
#default_config=“/etc/mkinitcpio-gzip.conf”
default_image=“/boot/initramfs-linux-lts.img”
#default_options=“”
#fallback_config=“/etc/mkinitcpio-gzip.conf”
fallback_image=“/boot/initramfs-linux-lts-fallback.img”
fallback_options=“-S autodetect”
I leave mkinitcpio.conf
and linux-zen.preset
as before.
Now:
sudo mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: ‘default’
→ -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio-gzip.conf -g /boot/initramfs-linux-lts.img
==> Starting build: 5.10.17-1-lts
→ Running build hook: [base]
→ Running build hook: [udev]
→ Running build hook: [autodetect]
→ Running build hook: [modconf]
→ Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
→ Running build hook: [keyboard]
→ Running build hook: [keymap]
→ Running build hook: [resume]
→ Running build hook: [filesystems]
==> Generating module dependencies
==> Creating xz-compressed initcpio image: /boot/initramfs-linux-lts.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: ‘fallback’
→ -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio-gzip.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
==> Starting build: 5.10.17-1-lts
→ Running build hook: [base]
→ Running build hook: [udev]
→ Running build hook: [modconf]
→ Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: xhci_pci
→ Running build hook: [keyboard]
→ Running build hook: [keymap]
→ Running build hook: [resume]
→ Running build hook: [filesystems]
==> Generating module dependencies
==> Creating xz-compressed initcpio image: /boot/initramfs-linux-lts-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: ‘default’
→ -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen.img
==> Starting build: 5.11.0-zen1-1-zen
→ Running build hook: [base]
→ Running build hook: [udev]
→ Running build hook: [autodetect]
→ Running build hook: [modconf]
→ Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
→ Running build hook: [keyboard]
→ Running build hook: [keymap]
→ Running build hook: [resume]
→ Running build hook: [filesystems]
==> Generating module dependencies
==> Creating lz4-compressed initcpio image: /boot/initramfs-linux-zen.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: ‘fallback’
→ -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen-fallback.img -S autodetect
==> Starting build: 5.11.0-zen1-1-zen
→ Running build hook: [base]
→ Running build hook: [udev]
→ Running build hook: [modconf]
→ Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: xhci_pci
→ Running build hook: [keyboard]
→ Running build hook: [keymap]
→ Running build hook: [resume]
→ Running build hook: [filesystems]
==> Generating module dependencies
==> Creating lz4-compressed initcpio image: /boot/initramfs-linux-zen-fallback.img
==> Image generation successful
And I have completed my migration on all my Endeavour laptops from linux to linux-lts this morning.
And today I rebooted after a few days and the 5.4lts stopped booting.
The 5.10lts didn’t boot either, but suprise suprise kernel 5.11 booted.
That is weird because only the 5.4 booted since always.
I see this in my log though…
feb 24 09:27:30 richard-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hos>
feb 24 09:27:30 richard-pc kernel: kauditd_printk_skb: 6 callbacks suppressed
feb 24 09:27:30 richard-pc kernel: audit: type=1131 audit(1614155250.240:54): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/>
feb 24 09:27:30 richard-pc systemd[1]: NetworkManager-dispatcher.service: Succeeded.
feb 24 09:27:30 richard-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/s>
feb 24 09:27:30 richard-pc kernel: audit: type=1131 audit(1614155250.690:55): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="syst>
feb 24 09:27:33 richard-pc kernel: i915 0000:00:02.0: [drm] *ERROR* Panel status timeout: status 00000000 control abcd000b
feb 24 09:27:34 richard-pc kernel: ------------[ cut here ]------------
feb 24 09:27:34 richard-pc kernel: i915 0000:00:02.0: timed out waiting for [ENCODER:106:DP C] port ready: got 0xf0, expected 0xe0
feb 24 09:27:34 richard-pc kernel: WARNING: CPU: 1 PID: 412 at drivers/gpu/drm/i915/display/intel_display.c:1643 vlv_wait_port_ready+0xbe/0x100 [i915]
feb 24 09:27:34 richard-pc kernel: Modules linked in: ccm rtsx_usb_ms rtsx_usb_sdmmc memstick hid_logitech_hidpp uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_>
feb 24 09:27:34 richard-pc kernel: i2c_i801 pcspkr snd processor_thermal_device lpc_ich i2c_smbus intel_rapl_common mei_txe libarc4 int340x_thermal_zone mei i2c_algo_>
feb 24 09:27:34 richard-pc kernel: CPU: 1 PID: 412 Comm: Xorg Tainted: G OE 5.10.17-1-lts #1
feb 24 09:27:34 richard-pc kernel: [71B blob data]
feb 24 09:27:34 richard-pc kernel: RIP: 0010:vlv_wait_port_ready+0xbe/0x100 [i915]
feb 24 09:27:34 richard-pc kernel: Code: 50 4d 85 e4 75 03 4c 8b 27 e8 4e a1 75 e2 45 89 f1 4d 89 f8 44 89 e9 55 48 89 c6 4c 89 e2 48 c7 c7 b8 ed 01 c1 e8 bb 0e ad e2 >
feb 24 09:27:34 richard-pc kernel: RSP: 0018:ffffa725808cfa28 EFLAGS: 00010282
feb 24 09:27:34 richard-pc kernel: RAX: 0000000000000000 RBX: ffff91ff51480000 RCX: ffff91ffbbd18bb8
feb 24 09:27:34 richard-pc kernel: RDX: 00000000ffffffd8 RSI: 0000000000000027 RDI: ffff91ffbbd18bb0
feb 24 09:27:34 richard-pc kernel: RBP: 00000000000000e0 R08: 0000000000000000 R09: ffffa725808cf848
feb 24 09:27:34 richard-pc kernel: R10: ffffa725808cf840 R11: ffffffffa4acb1e8 R12: ffff91ff409f9b00
feb 24 09:27:34 richard-pc kernel: R13: 000000000000006a R14: 00000000000000f0 R15: ffff91ff4a8940a0
feb 24 09:27:34 richard-pc kernel: FS: 00007fc596971940(0000) GS:ffff91ffbbd00000(0000) knlGS:0000000000000000
feb 24 09:27:34 richard-pc kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
feb 24 09:27:34 richard-pc kernel: CR2: 00007f9fcc01d028 CR3: 00000001002ac000 CR4: 00000000001006e0
feb 24 09:27:34 richard-pc kernel: Call Trace:
feb 24 09:27:34 richard-pc kernel: intel_enable_dp.constprop.0+0x239/0x3f0 [i915]
feb 24 09:27:34 richard-pc kernel: chv_pre_enable_dp+0x2c/0x40 [i915]
feb 24 09:27:34 richard-pc kernel: intel_encoders_pre_enable+0x7e/0x90 [i915]
pc kernel: i915 0000:00:02.0: [drm] *ERROR* Panel status timeout: status 00000000 control abcd000b
New mkinitcpio default compression will not work with 5.4 LTS, that could be your issue.
Make sure when you update 5.4 LTS kernels than pacman hooks are configured correctly to trigger mkinitcpio and grub update.
What if I just uncomment gzip or xz in my mkinitcpio.conf?
Then all the images will be compressed with gzip. The question was if you could use different compression algorithms for different images.