It happens that I wanted to install the Hardened kernel and it does not start session itself, then I checked in AKM and it is not listed as stable at least, like Zen …
Thank you as always!
Where did you download that, I’m not seeing it on my fresh install of KDE Plasma. Thanks.
Nope, not installed. 
$ sudo pacman -S akm
[sudo] password for soloyo:
advertencia: akm-2.5.3-2 está actualizado -- reinstalándolo
resolviendo dependencias...
buscando conflictos entre paquetes...
Paquetes (1) akm-2.5.3-2
Tamaño total de la instalación: 0,01 MiB
Tamaño neto tras actualizar: 0,00 MiB
:: ¿Continuar con la instalación? [S/n]
2 Likes
Thanks! 
2 Likes
Could someone please tell me why the Zen and Hardened kernels are missing from Akm?
They’re not, look at Stable column…
Just tick 
desired Kenrel + headers and choose it on reboot
1 Like
Thank you for your response.
It’s the same thing I did by hand and it doesn’t work, it installs just like Akm does, but it doesn’t start up and jams before the start session …
That’s weird maybe some modules not released for that Kernel yet (sometimes it could happen to zen / hardened), like for example you have to wait for older Nvidia proprietary drivers from AUR if you have one…
What does journal say when you startup, you still can get to TTY to check them, i assume?
Perhaps @anon31687413 could help you better, he’s Kernel Jesus 
2 Likes
Very likely, although in reality you should already be loaded.
I’ve just tested on VM with EndeavourOS and KDE with zen Kernel - works and loads fine, so it must be something specific on your system that prevents it…
Please post:
inxi -Fxxxz
so those who come would have a better idea on your situation 
Resumen
System: Kernel: 5.9.8-arch1-1 x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: KDE Plasma 5.20.3 tk: Qt 5.15.1 wm: kwin_x11
dm: SDDM Distro: EndeavourOS
Machine: Type: Desktop Mobo: Gigabyte model: B365M DS3H v: x.x serial: UEFI: American Megatrends v: F5
date: 08/13/2019
CPU: Info: 6-Core model: Intel Core i5-9400 bits: 64 type: MCP arch: Kaby Lake rev: D L2 cache: 9216 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 34814
Speed: 800 MHz min/max: 800/4100 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800
Graphics: Device-1: NVIDIA TU117 [GeForce GTX 1650] vendor: Gigabyte driver: nvidia v: 455.38 bus ID: 01:00.0
chip ID: 10de:1f82
Display: x11 server: X.org 1.20.9 compositor: kwin_x11 driver: nvidia unloaded: fbdev,modesetting,vesa
alternate: nouveau,nv resolution: <missing: xdpyinfo>
Message: Unable to show advanced data. Required tool glxinfo missing.
Audio: Device-1: Intel 200 Series PCH HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 00:1f.3
chip ID: 8086:a2f0
Device-2: NVIDIA vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:10fa
Sound Server: ALSA v: k5.9.8-arch1-1
Network: Device-1: Realtek RTL8188EE Wireless Network Adapter driver: rtl8188ee v: kernel port: d000 bus ID: 04:00.0
chip ID: 10ec:8179
IF: wlan0 state: down mac:
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8168 v: 8.048.03-NAPI
port: c000 bus ID: 07:00.0 chip ID: 10ec:8168
IF: enp7s0 state: down mac:
Device-3: 802.11g Adapter [Linksys WUSB54GC v3] WUSB54GC v3 802.11g Adapter [Ralink RT2070L] type: USB
driver: rt2800usb bus ID: 1-1:2 chip ID: 1737:0077 serial:
IF: wlan1 state: up mac:
Drives: Local Storage: total: 1.09 TiB used: 46.59 GiB (4.2%)
ID-1: /dev/sda vendor: Western Digital model: WDS480G2G0A-00JH30 size: 447.13 GiB speed: 6.0 Gb/s serial:
rev: 0400 scheme: GPT
ID-2: /dev/sdb vendor: Western Digital model: WDS480G2G0A-00JH30 size: 447.13 GiB speed: 6.0 Gb/s serial:
rev: 0400 scheme: GPT
ID-3: /dev/sdc type: USB model: Mass Storage Device size: 223.57 GiB serial: scheme: GPT
Partition: ID-1: / size: 438.82 GiB used: 46.59 GiB (10.6%) fs: ext4 dev: /dev/sdb2
Swap: Alert: No Swap data was found.
Sensors: System Temperatures: cpu: 27.8 C mobo: 16.8 C gpu: nvidia temp: 32 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 56%
Info: Processes: 200 Uptime: 28m wakeups: 0 Memory: 15.58 GiB used: 1.93 GiB (12.4%) Init: systemd v: 246 Compilers:
gcc: 10.2.0 Packages: pacman: 1059 Shell: Bash v: 5.0.18 running in: konsole inxi: 3.1.09
journalctl -p 4 -xb
-- Logs begin at Wed 2020-11-11 14:35:16 -03, end at Tue 2020-11-17 08:16:56 -03. --
nov 17 07:42:24 siempresolo kernel: ACPI: Invalid passive threshold
nov 17 07:42:24 siempresolo kernel: resource sanity check: requesting [mem 0xfdffe800-0xfe0007ff], which spans more than pnp 00:08 [mem 0xfdb00000-0xfdffffff]
nov 17 07:42:24 siempresolo kernel: caller pmc_core_probe+0x85/0x380 mapping multiple BARs
nov 17 07:42:24 siempresolo kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT2._GTF.DSSP], AE_NOT_FOUND (20200717/psargs-330)
nov 17 07:42:24 siempresolo kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT2._GTF due to previous error (AE_NOT_FOUND) (20200717/psparse-529)
nov 17 07:42:24 siempresolo kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT3._GTF.DSSP], AE_NOT_FOUND (20200717/psargs-330)
nov 17 07:42:24 siempresolo kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT3._GTF due to previous error (AE_NOT_FOUND) (20200717/psparse-529)
nov 17 07:42:24 siempresolo kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT3._GTF.DSSP], AE_NOT_FOUND (20200717/psargs-330)
nov 17 07:42:24 siempresolo kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT3._GTF due to previous error (AE_NOT_FOUND) (20200717/psparse-529)
nov 17 07:42:24 siempresolo kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT2._GTF.DSSP], AE_NOT_FOUND (20200717/psargs-330)
nov 17 07:42:24 siempresolo kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT2._GTF due to previous error (AE_NOT_FOUND) (20200717/psparse-529)
nov 17 07:42:24 siempresolo systemd-modules-load[243]: Failed to find module 'platform-integrity'
nov 17 07:42:25 siempresolo kernel: r8168: loading out-of-tree module taints kernel.
nov 17 07:42:25 siempresolo kernel: r8168 Copyright (C) 2020 Realtek NIC software team <nicfae@realtek.com>
This program comes with ABSOLUTELY NO WARRANTY; for details, please see <http://www.gnu.org/licenses/>.
This is free software, and you are welcome to redistribute it under certain conditions; see <http://www.gnu.org/licenses/>.
nov 17 07:42:25 siempresolo systemd-udevd[269]: controlC0: Process '/usr/bin/alsactl restore 0' failed with exit code 99.
nov 17 07:42:25 siempresolo kernel: nvidia: module license 'NVIDIA' taints kernel.
nov 17 07:42:25 siempresolo kernel: Disabling lock debugging due to kernel taint
nov 17 07:42:25 siempresolo kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 455.38 Thu Oct 22 06:06:59 UTC 2020
nov 17 07:42:26 siempresolo kernel: usbhid 1-7:1.1: couldn't find an input interrupt endpoint
nov 17 07:42:26 siempresolo systemd-udevd[268]: controlC1: Process '/usr/bin/alsactl restore 1' failed with exit code 99.
nov 17 07:42:27 siempresolo kernel: sd 6:0:0:0: [sdc] No Caching mode page found
nov 17 07:42:27 siempresolo kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write through
1 Like
kernel: nvidia: module license ‘NVIDIA’ taints kernel. 
1 Like
That’s not error, normal message rather for nvidia (basically it means that Nvidia is proprietary module, but it will still work)…
journalctl -p3 -xb
should give only errors
1 Like
journalctl -p3 -xb
-- Logs begin at Wed 2020-11-11 14:35:16 -03, end at Tue 2020-11-17 08:39:40 -03. --
nov 17 08:35:22 siempresolo kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT2._GTF.DSSP], AE_NOT_FOUND (20200717/psargs-330)
nov 17 08:35:22 siempresolo kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT2._GTF due to previous error (AE_NOT_FOUND) (20200717/psparse-529)
nov 17 08:35:22 siempresolo kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT3._GTF.DSSP], AE_NOT_FOUND (20200717/psargs-330)
nov 17 08:35:22 siempresolo kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT3._GTF due to previous error (AE_NOT_FOUND) (20200717/psparse-529)
nov 17 08:35:22 siempresolo kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT2._GTF.DSSP], AE_NOT_FOUND (20200717/psargs-330)
nov 17 08:35:22 siempresolo kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT2._GTF due to previous error (AE_NOT_FOUND) (20200717/psparse-529)
nov 17 08:35:22 siempresolo kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT3._GTF.DSSP], AE_NOT_FOUND (20200717/psargs-330)
nov 17 08:35:22 siempresolo kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT3._GTF due to previous error (AE_NOT_FOUND) (20200717/psparse-529)
nov 17 08:35:22 siempresolo systemd-modules-load[251]: Failed to find module 'platform-integrity'
nov 17 08:35:24 siempresolo kernel: usbhid 1-7:1.1: couldn't find an input interrupt endpoint
nov 17 08:35:25 siempresolo kernel: sd 6:0:0:0: [sdc] No Caching mode page found
nov 17 08:35:25 siempresolo kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write through
1 Like
Well…I don’t see anything too out there for that log that could prevent booting normally, assuming that it’s log from attempt of loading with zen / hardened
-
kernel: usbhid 1-7:1.1: couldn’t find an input interrupt endpoint no idea really, but usbhid should be something like mouse / keyboard, it stands for usb Human interface device
-
ACPI errors is usual stuff (although mostly for laptops, and you seem to use normal PC, make sure you turned off Secure boot / Fast boot in UEFI/BIOS)
-
systemd-modules-load[251]: Failed to find module ‘platform-integrity’ this is also more like warning, can be ignored, as it should be removed in next Kernels to come
-
sdc also looks more like warnings for your usb drive, shouldn’t prevent boot, but you can unplug it to test if it may be a reason, just in case
2 Likes
You might be on to something there…I did a fresh install of KDE yesterday to try and help someone and I had two USB devices plugged in on initial boot. A USB wifi adapter and the install media. It hung on boot. I removed both USB devices and it booted normally.
2 Likes
All points are to be ignored, although UEFI could be the case here, but neither is an obstacle to normal boot, we will see in the next Hardened update what can happen …
Thank you equally for your time, much appreciated!
2 Likes
Inside the PC I have 2 disks, in one of which is EOS, I just removed the usb disk and Hardened doesn’t work.
Thanks for the contribution!
1 Like