You are Here:
Linux Lite 7.0 RC1 Released - See Release Announcement Section



LL6.0 installs but after update get X.509 error @boot; LL6.6 install screws PC

Author (Read 2980 times)

0 Members and 4 Guests are viewing this topic.

 

Alan_Wilts

  • New to Forums
  • *
  • 17
    Posts
  • Reputation: 0
  • Linux Lite Member
    • View Profile

  • CPU: 1 VM under AMD Ryzen 7 3800X /2 Native AMD Ryzen 5 /3 Native A4 5300

  • MEMORY: 4Gb

  • VIDEO CARD: LLVMPIPE

  • Kernel: 6.x
Couple of notes:
1) Generally Windows can still be installed in legacy mode (dosMBR tables)

I bought a used laptop and Windows had been loaded ready to set up, so it was UEFI. When investigating my problem I read that legacy fixed it for some people. But it was a mistake for me to change it without further investigation.


3) I don't dual boot anymore anyway, nor do I advise others to. Virtualization is a better solution and Linux Lite runs quite nicely in hyper-v.

I've been using Virtual Box on my main Win10 PC for many years successfully. First to run some legacy 16bit Win XP software and 2nd to run LinuxLite for developing software for my Raspberry Pis. Here I  found a very useful Putty add-in called tkgpio that let's me simulate the GPIO pins and sensors as well as a small 4 line display.

On this laptop I didn't really want to wipe the Win 11 as it might be useful but I wanted to avoid running it connected to MS unless I spent a lot of time setting all the privacy settings etc. But I needed Linux to take the laptop to make full backups of my Pis from time to time.


I have recently added a SSD/PVIMe adapter to an old PC with LinuxLite installed first on the HDD and then copied the whole HDD to the SSD and then used Clover to boot into the SSD. I'm doing the same on another old Win10 PC but that is harder due to Windows Boot Manager. But both these are either LL/LL or Win10/Win10, not a mixture!


Overall, I think your comments are very sensible.

Alan in the UK
1: Using LL in VBox on a Win 10 Pro Ryzen 7 3800X  8GB ram and SSD PC to test code for implementing on various Rasp Pi from Zero to 4
2: LL 6.6 on an old AMD A88MX m/b with A4 5300 processor & 4GB ram and SSD/PCMIe adapter with Clover.
3: LL 6.6 on a Lenovo laptop with AMD Ryzen 5 processor and 8 GB of ram and SSD. Dual boot with Win11 Home.
 

 

Alan_Wilts

  • New to Forums
  • *
  • 17
    Posts
  • Reputation: 0
  • Linux Lite Member
    • View Profile

  • CPU: 1 VM under AMD Ryzen 7 3800X /2 Native AMD Ryzen 5 /3 Native A4 5300

  • MEMORY: 4Gb

  • VIDEO CARD: LLVMPIPE

  • Kernel: 6.x
Out of interest, does the log still report these after good Linux boots
"Problem loading X.509 certificate -65"
"Error adding keys to platform keyring UEFI:db"


Here are the X.509 Log Items from a fresh boot. Yes, still get an error adding keys:
Feb 06 18:12:52 Lenovo-LL kernel: Loading compiled-in X.509 certificates
Feb 06 18:12:52 Lenovo-LL kernel: Loaded X.509 cert 'Build time autogenerated kernel key: ec648241a1c40ddb590b5abe6c9f36ba54d989a2'
Feb 06 18:12:52 Lenovo-LL kernel: Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969'
Feb 06 18:12:52 Lenovo-LL kernel: Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19'
Feb 06 18:12:52 Lenovo-LL kernel: blacklist: Loading compiled-in revocation X.509 certificates
Feb 06 18:12:52 Lenovo-LL kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0'
Feb 06 18:12:52 Lenovo-LL kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2017): 242ade75ac4a15e50d50c84b0d45ff3eae707a03'
Feb 06 18:12:52 Lenovo-LL kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (ESM 2018): 365188c1d374d6b07c3c8f240f8ef722433d6a8b'
Feb 06 18:12:52 Lenovo-LL kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2019): c0746fd6c5da3ae827864651ad66ae47fe24b3e8'
Feb 06 18:12:52 Lenovo-LL kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v1): a8d54bbb3825cfb94fa13c9f8a594a195c107b8d'
Feb 06 18:12:52 Lenovo-LL kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v2): 4cf046892d6fd3c9a5b03f98d845f90851dc6a8c'
Feb 06 18:12:52 Lenovo-LL kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v3): 100437bb6de6e469b581e61cd66bce3ef4ed53af'
Feb 06 18:12:52 Lenovo-LL kernel: Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (Ubuntu Core 2019): c1d57b8f6b743f23ee41f4f7ee292f06eecadfb9'
Feb 06 18:12:52 Lenovo-LL kernel: zswap: loaded using pool lzo/zbud
Feb 06 18:12:52 Lenovo-LL kernel: Key type .fscrypt registered
Feb 06 18:12:52 Lenovo-LL kernel: Key type fscrypt-provisioning registered
Feb 06 18:12:52 Lenovo-LL kernel: Key type encrypted registered
Feb 06 18:12:52 Lenovo-LL kernel: AppArmor: AppArmor sha1 policy hashing enabled
Feb 06 18:12:52 Lenovo-LL kernel: integrity: Loading X.509 certificate: UEFI:db
Feb 06 18:12:52 Lenovo-LL kernel: integrity: Problem loading X.509 certificate -65
Feb 06 18:12:52 Lenovo-LL kernel: fbcon: Taking over console
Feb 06 18:12:52 Lenovo-LL kernel: integrity: Error adding keys to platform keyring UEFI:db
Feb 06 18:12:52 Lenovo-LL kernel: integrity: Loading X.509 certificate: UEFI:db
Feb 06 18:12:52 Lenovo-LL kernel: integrity: Loaded X.509 cert 'E8S350141517ADA: d9ad0d486703a8bc46d842ed4ff82287'
Feb 06 18:12:52 Lenovo-LL kernel: integrity: Loading X.509 certificate: UEFI:db
Feb 06 18:12:52 Lenovo-LL kernel: integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
Feb 06 18:12:52 Lenovo-LL kernel: integrity: Loading X.509 certificate: UEFI:db
Feb 06 18:12:52 Lenovo-LL kernel: integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
Feb 06 18:12:52 Lenovo-LL kernel: Console: switching to colour frame buffer device 240x67
Feb 06 18:12:52 Lenovo-LL kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table)
Feb 06 18:12:52 Lenovo-LL kernel: integrity: Loaded X.509 cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63'
Feb 06 18:12:52 Lenovo-LL kernel: ima: No TPM chip found, activating TPM-bypass!
Feb 06 18:12:52 Lenovo-LL kernel: Loading compiled-in module X.509 certificates
Feb 06 18:12:52 Lenovo-LL kernel: Loaded X.509 cert 'Build time autogenerated kernel key: ec648241a1c40ddb590b5abe6c9f36ba54d989a2'
Feb 06 18:12:52 Lenovo-LL kernel: ima: Allocated hash algorithm: sha1
Feb 06 18:12:52 Lenovo-LL kernel: ima: No architecture policies found
Feb 06 18:12:52 Lenovo-LL kernel: evm: Initialising EVM extended attributes:
Feb 06 18:12:52 Lenovo-LL kernel: evm: security.selinux
Feb 06 18:12:52 Lenovo-LL kernel: evm: security.SMACK64
Feb 06 18:12:52 Lenovo-LL kernel: evm: security.SMACK64EXEC
Feb 06 18:12:52 Lenovo-LL kernel: evm: security.SMACK64TRANSMUTE
Feb 06 18:12:52 Lenovo-LL kernel: evm: security.SMACK64MMAP
Feb 06 18:12:52 Lenovo-LL kernel: evm: security.apparmor
Feb 06 18:12:52 Lenovo-LL kernel: evm: security.ima
Feb 06 18:12:52 Lenovo-LL kernel: evm: security.capability
Feb 06 18:12:52 Lenovo-LL kernel: evm: HMAC attrs: 0x1
Feb 06 18:12:52 Lenovo-LL kernel: PM:   Magic number: 12:502:240
Feb 06 18:12:52 Lenovo-LL kernel: acpi_cpufreq: overriding BIOS provided _PSD data
Feb 06 18:12:52 Lenovo-LL kernel: RAS: Correctable Errors collector initialized.
Feb 06 18:12:52 Lenovo-LL kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7
Feb 06 18:12:52 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 06 18:12:52 Lenovo-LL kernel: Freeing unused decrypted memory: 2036K
................
Feb 06 18:12:52 Lenovo-LL kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
Feb 06 18:12:52 Lenovo-LL kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
........................
I also looked for "failed" and "error" and found:

Feb 06 18:12:54 Lenovo-LL systemd[1]: Starting GRUB failed boot detection...........Feb 06 18:12:54 Lenovo-LL systemd[1]: secureboot-db.service: Deactivated successfully.........Feb 06 18:12:54 Lenovo-LL systemd[1]: Finished Secure Boot updates for DB and DBX.Feb 06 18:12:54 Lenovo-LL systemd[1]: Finished GRUB failed boot detection.Feb 06 18:12:54 Lenovo-LL ModemManager[846]: <info>  ModemManager (version 1.20.0) starting in system bus...
Feb 06 18:12:54 Lenovo-LL bluetoothd[711]: Failed to set mode: Blocked through rfkill (0x12).......................
Then 100's of these:
Feb 06 18:13:06 Lenovo-LL ifup[878]: W: Tried to start delayed item http://security.ubuntu.com/ubuntu jammy-security InRelease, but failed

No other failed or errors that seemed relevant

Cheers
Alan
Alan in the UK
1: Using LL in VBox on a Win 10 Pro Ryzen 7 3800X  8GB ram and SSD PC to test code for implementing on various Rasp Pi from Zero to 4
2: LL 6.6 on an old AMD A88MX m/b with A4 5300 processor & 4GB ram and SSD/PCMIe adapter with Clover.
3: LL 6.6 on a Lenovo laptop with AMD Ryzen 5 processor and 8 GB of ram and SSD. Dual boot with Win11 Home.
 

 

trinidad

  • Platinum Level Poster
  • **********
  • 1484
    Posts
  • Reputation: 214
  • Linux Lite Member
    • View Profile
    • dbts-analytics.com

  • CPU: i7 4 cores 8 threads

  • MEMORY: 16Gb

  • VIDEO CARD: Intel HD graphics

  • Kernel: 5.x
Couple of notes:
1) Generally Windows can still be installed in legacy mode (dosMBR tables) however once installed you cannot switch to UEFI mode or vice versa just because the option is there in the BIOS. It's kind of you must pick one or the other and stick with it. If Windows was UEFI to begin with, then Linux should be installed for dual booting UEFI. This could be in part the cause of some of the boot problems you had.

2) Another culprit could be forgetting to shut Windows completely down before booting back into Linux. Hold down the shift key without releasing it and select shut down and don't release the shift key until Windows goes off, or use powershell to completely shut down. In your case I'd bet on a combination of these first two things I mention here.

3) I don't dual boot anymore anyway, nor do I advise others to. Virtualization is a better solution and Linux Lite runs quite nicely in hyper-v.

4) When I did dual boot and share a partition I used exFAT as it seemed quicker.

5) Anyway I hope your dual boot does what you need it to do.

best of luck
TC     
All opinions expressed and all advice given by Trinidad Cruz on this forum are his responsibility alone and do not necessarily reflect the views or methods of the developers of Linux Lite. He is a citizen of the United States where it is acceptable to occasionally be uninformed and inept as long as you pay your taxes.
 

 

stevef

  • Global Moderator
  • Gold Level Poster
  • *****
  • 840
    Posts
  • Reputation: 148
  • Linux Lite Member
    • View Profile

  • CPU: Intel Core i5-4460

  • MEMORY: 16Gb

  • Kernel: 5.x
Glad you got it sorted.

Quote
Looks like formatting the NTFS partition in LL is corrupting it and upsetting Grub/boot. Could the reformatting change/damage the GUID?
If the Windows doing the formatting has worked, then perhaps Windows is doing something different.
I've not had problems getting Linux to format NTFS drives in general, but it is sound thinking to get Windows to do the MS proprietary jobs when possible.

Out of interest, does the log still report these after good Linux boots
"Problem loading X.509 certificate -65"
"Error adding keys to platform keyring UEFI:db"
clueless
 

 

Alan_Wilts

  • New to Forums
  • *
  • 17
    Posts
  • Reputation: 0
  • Linux Lite Member
    • View Profile

  • CPU: 1 VM under AMD Ryzen 7 3800X /2 Native AMD Ryzen 5 /3 Native A4 5300

  • MEMORY: 4Gb

  • VIDEO CARD: LLVMPIPE

  • Kernel: 6.x
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.

Many thanks for looking at this Steve. I came to the same conclusion overnight and have just done the following:

1. Booted to LL 6.6 Live and deleted the shared partition
2. Installed LL 6.6 with using just the / and /home partitions reformatted ext4
3. Booted OK into LL and again into Win11
4. In Win11 formatted the shared partition as NTFS.
3. Booted OK into Win11 and again into LL.
4. In LL ran Install Updates
5. Booted into LL and mounted the shared partition on start and disabled mounting the Win11 System partition
6. Booted into Windows and hid the LL system partition (D:) and remapped the shared partition for E: to D:
7. In Bios changed back to UEFI boot - secure boot is still disabled.
8. Booted to Macrium Reflect Recovery / PE and made an image copy of the whole SSD

So far with many reboots it's been OK.

After Grub selection an error still flashed for half a second (I'm sure it is the X.509) but continues without a disk check. But I think this warning is different to the boot failure. Looks like formatting the NTFS partition in LL is corrupting it and upsetting Grub/boot. Could the reformatting change/damage the GUID?

So I think I will leave it for now and enjoy LL.
Alan in the UK
1: Using LL in VBox on a Win 10 Pro Ryzen 7 3800X  8GB ram and SSD PC to test code for implementing on various Rasp Pi from Zero to 4
2: LL 6.6 on an old AMD A88MX m/b with A4 5300 processor & 4GB ram and SSD/PCMIe adapter with Clover.
3: LL 6.6 on a Lenovo laptop with AMD Ryzen 5 processor and 8 GB of ram and SSD. Dual boot with Win11 Home.
 

 

stevef

  • Global Moderator
  • Gold Level Poster
  • *****
  • 840
    Posts
  • Reputation: 148
  • Linux Lite Member
    • View Profile

  • CPU: Intel Core i5-4460

  • MEMORY: 16Gb

  • Kernel: 5.x
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

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


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

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.
« Last Edit: February 06, 2024, 03:59:54 AM by stevef »
clueless
 

 

Alan_Wilts

  • New to Forums
  • *
  • 17
    Posts
  • Reputation: 0
  • Linux Lite Member
    • View Profile

  • CPU: 1 VM under AMD Ryzen 7 3800X /2 Native AMD Ryzen 5 /3 Native A4 5300

  • MEMORY: 4Gb

  • VIDEO CARD: LLVMPIPE

  • Kernel: 6.x
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: [Select]
[ 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)


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 in the UK
1: Using LL in VBox on a Win 10 Pro Ryzen 7 3800X  8GB ram and SSD PC to test code for implementing on various Rasp Pi from Zero to 4
2: LL 6.6 on an old AMD A88MX m/b with A4 5300 processor & 4GB ram and SSD/PCMIe adapter with Clover.
3: LL 6.6 on a Lenovo laptop with AMD Ryzen 5 processor and 8 GB of ram and SSD. Dual boot with Win11 Home.
 

Re: LL 6.6 installs but get X.509 error @ boot
« Reply #2 on: February 05, 2024, 12:43:14 PM »
 

Alan_Wilts

  • New to Forums
  • *
  • 17
    Posts
  • Reputation: 0
  • Linux Lite Member
    • View Profile

  • CPU: 1 VM under AMD Ryzen 7 3800X /2 Native AMD Ryzen 5 /3 Native A4 5300

  • MEMORY: 4Gb

  • VIDEO CARD: LLVMPIPE

  • Kernel: 6.x
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: [Select]
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
/
« Last Edit: February 05, 2024, 12:56:15 PM by Alan_Wilts »
Alan in the UK
1: Using LL in VBox on a Win 10 Pro Ryzen 7 3800X  8GB ram and SSD PC to test code for implementing on various Rasp Pi from Zero to 4
2: LL 6.6 on an old AMD A88MX m/b with A4 5300 processor & 4GB ram and SSD/PCMIe adapter with Clover.
3: LL 6.6 on a Lenovo laptop with AMD Ryzen 5 processor and 8 GB of ram and SSD. Dual boot with Win11 Home.
 

LL6.0 installs but after update get X.509 error @boot; LL6.6 install screws PC
« Reply #1 on: February 05, 2024, 11:45:25 AM »
 

Alan_Wilts

  • New to Forums
  • *
  • 17
    Posts
  • Reputation: 0
  • Linux Lite Member
    • View Profile

  • CPU: 1 VM under AMD Ryzen 7 3800X /2 Native AMD Ryzen 5 /3 Native A4 5300

  • MEMORY: 4Gb

  • VIDEO CARD: LLVMPIPE

  • Kernel: 6.x
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: [Select]
[ 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)

I pressed control-D and get:
Code: [Select]
Failed to start default target: Transaction for graphical.target/start is destructive (emergency/target has 'start' job queued, but 'stop' is included in transaction).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: [Select]
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>

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]
« Last Edit: February 06, 2024, 09:26:51 AM by stevef »
Alan in the UK
1: Using LL in VBox on a Win 10 Pro Ryzen 7 3800X  8GB ram and SSD PC to test code for implementing on various Rasp Pi from Zero to 4
2: LL 6.6 on an old AMD A88MX m/b with A4 5300 processor & 4GB ram and SSD/PCMIe adapter with Clover.
3: LL 6.6 on a Lenovo laptop with AMD Ryzen 5 processor and 8 GB of ram and SSD. Dual boot with Win11 Home.
 

 

-->
X Close Ad

Linux Lite 7.0 RC1 Released - See Release Announcement Section