Software - Support > Installing Linux Lite
LL6.0 installs but after update get X.509 error @boot; LL6.6 install screws PC
stevef:
Reformating an unused partition should be trivial.
It seems that at post #2 you had a 'working' dual boot system but with something unusual going on before the grub menu and in the logs.
--- Quote ---I still get the X.509 error flashing up at boot before the grub menu. This is followed by "Error checking in progress". After about 10-15 seconds I get the Grub Menu
--- End quote ---
But, from the log posted in post #2
--- Quote ---feb 05 18:31:48 Lenovo-LL kernel: integrity: Loading X.509 certificate: UEFI:db
feb 05 18:31:48 Lenovo-LL kernel: integrity: Problem loading X.509 certificate -65
feb 05 18:31:48 Lenovo-LL kernel: fbcon: Taking over console
feb 05 18:31:48 Lenovo-LL kernel: integrity: Error adding keys to platform keyring UEFI:db
feb 05 18:31:48 Lenovo-LL kernel: integrity: Loading X.509 certificate: UEFI:db
--- End quote ---
The inference from posts #1 and #3 is that converting the ext4 data partition (or maybe updating kernel) triggers the system to fail to boot with a specific x509 error.
--- Quote ---Integrity Problem loading X.509 certificate -65
--- End quote ---
In your position, I'd be tempted to concentrate on getting the dual booting working properly by resolving or mitigating the x.509 -65 error before grub. The suspicion is that it is related to UEFI and secure boot and possibly kernel update post install.
Edit - addition
Can't find anything particularly concrete, but there are suggestions that the -65 error might be related to disk problems.
Alan_Wilts:
Well back to square 1.
I again booted to LL 6.6 desktop and reformatted my data partition to NTFS and restarted the laptop. Again I get the X.509 error followed by going into emergency mode whereas before the X.509 would be followed by a filesystem check and eventual desktop.
--- Code: ---[ 0.998701 ] Integrity Problem loading X.509 certificate -65
Your are in emergency mode. After logging in type "journalctl -xb" to view system logs.
"journalctl -reboot" to reboot. "journalctl -default" or "exit" to boot into default mode.
Press Enter for maintenance (or press Control-D to continue)
--- End code ---
Control-D doesn't ignore the problem and the PC is stuck.
I booted a USB stick into LL 6.6 Live and change the partition format back to ext4 but a reboot just repeats the above.
Looks like another install but without changing the shared data partition to NTFS, so no sharing with Windows.
Alan_Wilts:
I've solved my initial problem that the LL 6.6. update damaged the PC / Grub / EFI so I could no longer boot but it's not 100% fixed.
I tried a fresh installation again with a LL 6.6 Live stick and selected the 3 previous partitions for /, /home and my data but this time formatted all 3 to ext4 (last time my data was left at NTFS
I also change the BIOS Boot Mode to Legacy Support and Boot Priority to Legacy first
Installation completed and I rebooted and could boot to Windows and boot to LL.
I then did a LL update and rebooted and again could boot to Windows and boot to LL.
I still get the X.509 error flashing up at boot before the grub menu. This is followed by "Error checking in progress". After about 10-15 seconds I get the Grub menu.
Log extraction below
So I would like to solve this, if only to save 15 seconds on the boot, but mainly to be assured nothing more major is lurking to bite me later ;)
I still need to format my data partition to NTFS so it can be shared with Windows 11.
--- Code: ---feb 05 18:31:48 Lenovo-LL kernel: Loading compiled-in X.509 certificates
feb 05 18:31:48 Lenovo-LL kernel: Loaded X.509 cert 'Build time autogenerated kernel key: ec648241a1c40ddb590b5abe6c9f36ba54d989a2'
feb 05 18:31:48 Lenovo-LL kernel: Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969'
feb 05 18:31:48 Lenovo-LL kernel: Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19'
feb 05 18:31:48 Lenovo-LL kernel: blacklist: Loading compiled-in revocation X.509 certificates
feb 05 18:31:48 Lenovo-LL kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0'
feb 05 18:31:48 Lenovo-LL kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2017): 242ade75ac4a15e50d50c84b0d45ff3eae707a03'
feb 05 18:31:48 Lenovo-LL kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (ESM 2018): 365188c1d374d6b07c3c8f240f8ef722433d6a8b'
feb 05 18:31:48 Lenovo-LL kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2019): c0746fd6c5da3ae827864651ad66ae47fe24b3e8'
feb 05 18:31:48 Lenovo-LL kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v1): a8d54bbb3825cfb94fa13c9f8a594a195c107b8d'
feb 05 18:31:48 Lenovo-LL kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v2): 4cf046892d6fd3c9a5b03f98d845f90851dc6a8c'
feb 05 18:31:48 Lenovo-LL kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v3): 100437bb6de6e469b581e61cd66bce3ef4ed53af'
feb 05 18:31:48 Lenovo-LL kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (Ubuntu Core 2019): c1d57b8f6b743f23ee41f4f7ee292f06eecad>
feb 05 18:31:48 Lenovo-LL kernel: zswap: loaded using pool lzo/zbud
feb 05 18:31:48 Lenovo-LL kernel: Key type .fscrypt registered
feb 05 18:31:48 Lenovo-LL kernel: Key type fscrypt-provisioning registered
feb 05 18:31:48 Lenovo-LL kernel: Key type encrypted registered
feb 05 18:31:48 Lenovo-LL kernel: AppArmor: AppArmor sha1 policy hashing enabled
feb 05 18:31:48 Lenovo-LL kernel: integrity: Loading X.509 certificate: UEFI:db
feb 05 18:31:48 Lenovo-LL kernel: integrity: Problem loading X.509 certificate -65
feb 05 18:31:48 Lenovo-LL kernel: fbcon: Taking over console
feb 05 18:31:48 Lenovo-LL kernel: integrity: Error adding keys to platform keyring UEFI:db
feb 05 18:31:48 Lenovo-LL kernel: integrity: Loading X.509 certificate: UEFI:db
feb 05 18:31:48 Lenovo-LL kernel: Console: switching to colour frame buffer device 240x67
feb 05 18:31:48 Lenovo-LL kernel: integrity: Loaded X.509 cert 'E8S350141517ADA: d9ad0d486703a8bc46d842ed4ff82287'
feb 05 18:31:48 Lenovo-LL kernel: integrity: Loading X.509 certificate: UEFI:db
feb 05 18:31:48 Lenovo-LL kernel: integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
feb 05 18:31:48 Lenovo-LL kernel: integrity: Loading X.509 certificate: UEFI:db
feb 05 18:31:48 Lenovo-LL kernel: integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
feb 05 18:31:48 Lenovo-LL kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table)
feb 05 18:31:48 Lenovo-LL kernel: integrity: Loaded X.509 cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e34>
feb 05 18:31:48 Lenovo-LL kernel: ima: No TPM chip found, activating TPM-bypass!
feb 05 18:31:48 Lenovo-LL kernel: Loading compiled-in module X.509 certificates
feb 05 18:31:48 Lenovo-LL kernel: Loaded X.509 cert 'Build time autogenerated kernel key: ec648241a1c40ddb590b5abe6c9f36ba54d989a2'
feb 05 18:31:48 Lenovo-LL kernel: ima: Allocated hash algorithm: sha1
feb 05 18:31:48 Lenovo-LL kernel: ima: No architecture policies found
feb 05 18:31:48 Lenovo-LL kernel: evm: Initialising EVM extended attributes:
feb 05 18:31:48 Lenovo-LL kernel: evm: security.selinux
feb 05 18:31:48 Lenovo-LL kernel: evm: security.SMACK64
feb 05 18:31:48 Lenovo-LL kernel: evm: security.SMACK64EXEC
feb 05 18:31:48 Lenovo-LL kernel: evm: security.SMACK64TRANSMUTE
feb 05 18:31:48 Lenovo-LL kernel: evm: security.SMACK64MMAP
feb 05 18:31:48 Lenovo-LL kernel: evm: security.apparmor
feb 05 18:31:48 Lenovo-LL kernel: evm: security.ima
feb 05 18:31:48 Lenovo-LL kernel: evm: security.capability
feb 05 18:31:48 Lenovo-LL kernel: evm: HMAC attrs: 0x1
feb 05 18:31:48 Lenovo-LL kernel: PM: Magic number: 12:630:541
feb 05 18:31:48 Lenovo-LL kernel: acpi_cpufreq: overriding BIOS provided _PSD data
feb 05 18:31:48 Lenovo-LL kernel: RAS: Correctable Errors collector initialized.
feb 05 18:31:48 Lenovo-LL kernel: Unstable clock detected, switching default tracing clock to "global"
If you want to keep using the local clock, then add:
"trace_clock=local"
on the kernel command line
feb 05 18:31:48 Lenovo-LL kernel: Freeing unused decrypted memory: 2036K
feb 05 18:31:48 Lenovo-LL kernel: Freeing unused kernel image (initmem) memory: 3356K
feb 05 18:31:48 Lenovo-LL kernel: Write protecting the kernel read-only data: 30720k
feb 05 18:31:48 Lenovo-LL kernel: Freeing unused kernel image (text/rodata gap) memory: 2036K
feb 05 18:31:48 Lenovo-LL kernel: Freeing unused kernel image (rodata/data gap) memory: 1420K
feb 05 18:31:48 Lenovo-LL kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.
feb 05 18:31:48 Lenovo-LL kernel: Run /init as init process
feb 05 18:31:48 Lenovo-LL kernel: with arguments:
feb 05 18:31:48 Lenovo-LL kernel: /init
feb 05 18:31:48 Lenovo-LL kernel: splash
feb 05 18:31:48 Lenovo-LL kernel: with environment:
feb 05 18:31:48 Lenovo-LL kernel: HOME=/
feb 05 18:31:48 Lenovo-LL kernel: TERM=linux
feb 05 18:31:48 Lenovo-LL kernel: BOOT_IMAGE=/boot/vmlinuz-5.15.0-92-generic
feb 05 18:31:48 Lenovo-LL kernel: cryptd: max_cpu_qlen set to 1000
/
--- End code ---
Alan_Wilts:
Lenovo V15 ADA laptop with NMVe SSD and Windows 11 Home PC. Secure boot is off.
I shrunk the Win11 and then installed LL 6.0 no updates with /, /home & data partitions all ext4.
Booted OK into Windows and LL 6.0 via Grub.
Then I changed the data partition to NTFS, changed the desktop appearance and icon style and did a system update.
Then as requested I rebooted but it failed to boot with:
--- Code: ---[ 0.998701 ] Integrity Problem loading X.509 certificate -65Your are in emergency mode. After logging in type "journalctl -xb" to view system logs.
"journalctl -reboot" to reboot. "journalctl -default" or "exit" to boot into default mode.
Press Enter for maintenance (or press Control-D to continue)
--- End code ---
I pressed control-D and get:
--- Code: ---Failed to start default target: Transaction for graphical.target/start is destructive (emergency/target has 'start' job queued, but 'stop' is included in transaction).
--- End code ---
Forced a reboot and checked BIOS. All seems OK. Rebooted but get the X.509 error followed by 100s of errors re USB device descriptor errors. Had to power on & off.
Downloaded LL 6.6 to USB stick and booted Live to Desktop and clicked Install. After selecting the previous / and ./home partitions and clicking format the installation fails with:
--- Code: ---GNU GRUB Version 2.06 error: Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions.Anywhere else TAB lists possible device or file completions.
grub>
--- End code ---
So now I have a PC that does not boot into either LL or Windows :( Luckily I do have an image of the whole system with just Windows but don't want to go down that route until I have a solution.Suggestions please.Alan
PS been using LL for many years on an older laptop without problem and have recently installed LL6.6 onto a old desktop with SSD and Clover and that is working. But neither is dual boot with Windows and neither has secure boot.
[/code]
Navigation
[0] Message Index
[*] Previous page
Go to full version