You are not logged in.
Pages: 1
If I try to update my kernel to the latest version, I get crypto errors when trying to start the iwd service:
Jun 02 18:40:05 h iwd[642]: No HMAC(SHA1) support found
Jun 02 18:40:05 h iwd[642]: No HMAC(MD5) support found
Jun 02 18:40:05 h iwd[642]: No CMAC(AES) support found
Jun 02 18:40:05 h iwd[642]: No HMAC(SHA256) support not found
Jun 02 18:40:05 h iwd[642]: No HMAC(SHA512) support found, certain TLS connections might fail
Jun 02 18:40:05 h iwd[642]: DES support not found
Jun 02 18:40:05 h iwd[642]: AES support not found
Jun 02 18:40:05 h iwd[642]: No CBC(DES3_EDE) support found, certain TLS connections might fail
Jun 02 18:40:05 h iwd[642]: No CBC(AES) support found, WPS will not be available
Jun 02 18:40:05 h iwd[642]: The following options are missing in the kernel:
Jun 02 18:40:05 h iwd[642]: CONFIG_CRYPTO_USER_API_HASH
Jun 02 18:40:05 h iwd[642]: CONFIG_CRYPTO_USER_API_SKCIPHER
Jun 02 18:40:05 h iwd[642]: CONFIG_CRYPTO_ECB
Jun 02 18:40:05 h iwd[642]: CONFIG_CRYPTO_MD5
Jun 02 18:40:05 h iwd[642]: CONFIG_CRYPTO_CBC
Jun 02 18:40:05 h iwd[642]: CONFIG_CRYPTO_SHA256
Jun 02 18:40:05 h iwd[642]: CONFIG_CRYPTO_AES
Jun 02 18:40:05 h iwd[642]: CONFIG_CRYPTO_DES
Jun 02 18:40:05 h iwd[642]: CONFIG_CRYPTO_CMAC
Jun 02 18:40:05 h iwd[642]: CONFIG_CRYPTO_HMAC
Jun 02 18:40:05 h iwd[642]: CONFIG_CRYPTO_SHA512
Jun 02 18:40:05 h iwd[642]: CONFIG_CRYPTO_SHA1
Jun 02 18:40:05 h iwd[642]: The following optimized implementations might be available:
Jun 02 18:40:05 h iwd[642]: CONFIG_CRYPTO_SHA1_SSSE3
Jun 02 18:40:05 h iwd[642]: CONFIG_CRYPTO_AES_NI_INTEL
Jun 02 18:40:05 h iwd[642]: CONFIG_CRYPTO_SHA512_SSSE3
Jun 02 18:40:05 h iwd[642]: CONFIG_CRYPTO_AES_X86_64
Jun 02 18:40:05 h iwd[642]: CONFIG_CRYPTO_DES3_EDE_X86_64
Jun 02 18:40:05 h iwd[642]: CONFIG_CRYPTO_SHA256_SSSE3
Jun 02 18:40:05 h systemd[1]: iwd.service: Main process exited, code=exited, status=1/FAILURE
And so I am unable to connect to the internet with this new kernel. I downgraded the kernel, and it works again. Any ideas where the issue might come from ?
Last edited by dsudydfjsiuy (2025-06-05 05:51:33)
Offline
Can you give a full journal for a affected boot?
journalctl -b -1 | curl -F 'file=@-' 0x0.stuse -1 for the last boot, -2 for the one before that etc.
^ this expects that the drive is writeable. otherwise, you'll have to pipe it to a file on a usb drive or so while booting the new kernel, and then upload it:
journalctl -b 0 >/on-some-usb-drive/temp.txt
curl -F 'file=@-' 0x0.st < temp.txt #this one while on the old kernel/other PCI suspect you are somehow unable to load kernel modules, leading to a filesystem mount problem or such, which somehow doesn't make sense since the rest seems to be working properly.
Last edited by jl2 (2025-06-05 06:32:35)
Why I run Arch? To "BTW I run Arch" the guy one grade younger.
And to let my siblings and cousins laugh at Arsch Linux...
Offline
uname -a
pacman -Qs kernel
modinfo crypto-aesEdit: run that on the disfunctional kernel
Last edited by seth (2025-06-05 07:48:10)
Offline
uname -a pacman -Qs kernel
How could I forget that ![]()
Why I run Arch? To "BTW I run Arch" the guy one grade younger.
And to let my siblings and cousins laugh at Arsch Linux...
Offline
Pages: 1