solus-enroll not recognized as valid certificate

marcvg

Hi,

Trying to install Solus 4.4 on brand new Asus Zephyrus m16 with secure boot enabled (supported as of 4.4)
When I get to the MOK screen, I able to select 'solus-enroll' from Live-USB, but I get following message:

"Unsupported cert format. Only .CER, .DER and .CRT are supported"

How to solve?

Kind regards,
M.

tflovik

I would suggest that you turn off secure boot.

marcvg

tflovik err.. no. New PC, new Solus with secure boot support. I want to try it.

pomon

Are you doing according to this guide?

marcvg

pomon Exactly like that.

It says: "it should normally be located in the SOLUSESP directory".. but when selecting usb-live disk it shows right in the list (there is no SOLUSESP dir) but without file extension (.cer, .der, ..)

Br,
Marc.

Staudey

marcvg It says: "it should normally be located in the SOLUSESP directory".. but when selecting usb-live disk it shows right in the list (there is no SOLUSESP dir) but without file extension (.cer, .der, ..)

Depending on your system it might show up as SOLUSESP might just show up as efi.img

The solus-enroll file you mention is not the correct certificate (I assume you used Rufus in ISO-mode or similar, which is not supported and creates its own enroll file). As the documentation says the correct file is called solus-enroll-me.cer

marcvg

Staudey you might be right. I'll create the live-usb again.

Staudey

marcvg Be sure to follow the Preparing to Install docs for best results

marcvg

Using latest Rufus to create live-usb:

Rufus x64 v4.3.2090 (Portable)
Windows version: Windows 11 Home x64 (Build 22621.2428)
Syslinux versions: 4.07/2013-07-25, 6.04/pre1
Grub versions: 0.4.6a, 2.06
System locale ID: 0x0809 (en-GB)
Will use default UI locale 0x0809
SetLGP: Successfully set NoDriveTypeAutorun policy to 0x0000009E
Localization set to 'en-US'
Found 517 officially revoked UEFI bootloaders from embedded list
Found 2351 additional revoked UEFI bootloaders from this system's SKUSiPolicy.p7b
Found USB 2.0 device 'SanDisk Cruzer Edge USB Device' (0781:556B)
1 device found
Disk type: Removable, Disk size: 8 GB, Sector size: 512 bytes
Cylinders: 973, Tracks per cylinder: 255, Sectors per track: 63
Partition type: GPT, NB Partitions: 2
Disk GUID: {5F4A0E77-95C2-4142-A43E-4BCF8AEE4088}
Max parts: 128, Start Offset: 17408, Usable = 8004270592 bytes
Partition 1:
  Type: Microsoft Basic Data Partition
  Name: 'Main Data Partition'
  Detected File System: FAT32
  ID: {D5E3E4DA-B91B-4941-AE9D-B3596C382A0B}
  Size: 6.5 GB (6929489920 bytes)
  Start Sector: 2048, Attributes: 0x0000000000000000
Partition 2:
  Type: Linux Data Partition
  Name: 'Linux Persistence'
  Detected File System: ext3
  ID: {DBE7356C-E472-4884-9070-07C7A3C0E30E}
  Size: 1024.0 MB (1073737728 bytes)
  Start Sector: 13536208, Attributes: 0x0000000000000000
Scanning image...
ISO analysis:
  Image is an ISO9660 image
  Will use '/isolinux/isolinux.cfg' for Syslinux
  Detected Syslinux version: 6.03 (from '/isolinux/isolinux.bin')
  Detected EFI bootloader(s) (from '/efi.img'):
  ● 'bootx64.efi'
Disk image analysis:
  Image has an unknown Master Boot Record
  Image is a bootable disk image
ISO label: 'SolusLiveBudgie'
  Size: 2.3 GB (Projected)
  Uses: Syslinux/Isolinux v6.03
  Uses: EFI
Using image: Solus-4.4-Budgie.iso (2.3 GB)
Checking for Rufus updates...
Checking release channel...
No new release version found.
Timeout while retrieving conflicting process list

Format operation started
Requesting disk access...
Will use 'D:' as volume mountpoint
Opened \\.\PhysicalDrive2 for shared write access
Analyzing existing boot records...
Drive has a Zeroed Master Boot Record
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Initializing disk...
Partitioning (GPT)...
● Creating Main Data Partition (offset: 1048576, size: 6.5 GB)
● Creating Linux Persistence Partition (offset: 6930538496, size: 1024.0 MB)
Waiting for logical drive to reappear...
Using Debian-like method to enable persistence
Notice: Using physical device to access partition data
Formatting (ext3)...
65535 possible inodes out of 262143 blocks (block size = 4096)
13107 blocks (5.0%) reserved for the super user
Creating 8 inode sets: [1 marker = 1.0 set(s)]
++++++++
Creating 2048 journal blocks: [1 marker = 25.6 block(s)]
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Created 'persistence.conf' file
Formatting to FAT32 (using IFS)
Using cluster size: 4096 bytes
Quick format was selected
Creating file system...
Format completed.
Opened \\.\PhysicalDrive2 for shared write access
Writing Master Boot Record...
Using Rufus protective MBR
Writing protective message SBR
Found volume \\?\Volume{1e83e6f3-1a95-48e1-9942-3e20214bfd79}\
Successfully remounted \\?\Volume{1e83e6f3-1a95-48e1-9942-3e20214bfd79}\ as D:
Extracting files...
Image is an ISO9660 image
This image will be extracted using Joliet extensions (if present)
Extracting: D:\boot\initrd.img (42.4 MB)
Extracting: D:\boot\kernel (9.9 MB)
Extracting: D:\efi.img (150 MB)
Extracting: D:\isolinux\boot.cat (2 KB)
Extracting: D:\isolinux\isohdpfx.bin (432 bytes)
Extracting: D:\isolinux\isolinux.bin (38 KB)
Extracting: D:\isolinux\isolinux.cfg (1.5 KB)
  Patched D:\isolinux\isolinux.cfg: 'SolusLiveBudgie' ➔ 'SOLUSLIVEBU'
Extracting: D:\isolinux\ldlinux.c32 (112.9 KB)
Extracting: D:\isolinux\libcom32.c32 (176.4 KB)
Extracting: D:\isolinux\libutil.c32 (22.2 KB)
Extracting: D:\isolinux\splash.png (9.2 KB)
Extracting: D:\isolinux\vesa.c32 (3 KB)
Extracting: D:\isolinux\vesamenu.c32 (26.1 KB)
Extracting: D:\LiveOS\squashfs.img (2.1 GB)
Extracting: D:\EFI\Boot\grubx64.efi (from '/efi.img', 110.5 KB)
Extracting: D:\EFI\Boot\BOOTx64.EFI (from '/efi.img', 924.5 KB)
Extracting: D:\EFI\Boot\mmx64.efi (from '/efi.img', 837.2 KB)
Extracting: D:\solus-enroll (from '/efi.img', 1.3 KB)
Extracting: D:\kernel (from '/efi.img', 9.9 MB)
Extracting: D:\initrd (from '/efi.img', 42.4 MB)
Extracting: D:\loader\loader.conf (from '/efi.img', 24 bytes)
Extracting: D:\loader\entries\solus.conf (from '/efi.img', 157 bytes)
  Patched D:\loader\entries\solus.conf: 'SolusLiveBudgie' ➔ 'SOLUSLIVEBU'
Extracting: D:\loader\entries\solus-nomode (from '/efi.img', 208 bytes)
Extracting: D:\loader\entries\solus-debug. (from '/efi.img', 216 bytes)
Created: D:\syslinux.cfg → /isolinux/isolinux.cfg
Finalizing, please wait...
Created: D:autorun.inf
Created: D:autorun.ico

Found USB 2.0 device 'SanDisk Cruzer Edge USB Device' (0781:556B)
Using 'autorun.inf' label for drive D: 'SolusLiveBudgie'
1 device found
Disk type: Removable, Disk size: 8 GB, Sector size: 512 bytes
Cylinders: 973, Tracks per cylinder: 255, Sectors per track: 63
Partition type: GPT, NB Partitions: 2
Disk GUID: {80B8F8A3-6843-4A7C-A137-F7DD0D463141}
Max parts: 128, Start Offset: 17408, Usable = 8004270592 bytes
Partition 1:
  Type: Microsoft Basic Data Partition
  Name: 'Main Data Partition'
  Detected File System: FAT32
  ID: {1E83E6F3-1A95-48E1-9942-3E20214BFD79}
  Size: 6.5 GB (6929489920 bytes)
  Start Sector: 2048, Attributes: 0x0000000000000000
Partition 2:
  Type: Linux Data Partition
  Name: 'Linux Persistence'
  Detected File System: ext3
  ID: {C90411A8-2C4D-464A-85A3-BC9BA282FB11}
  Size: 1024.0 MB (1073737728 bytes)
  Start Sector: 13536208, Attributes: 0x0000000000000000

Notice how it extracted 'solus-enroll' from /efi.img

I'll try with an older version of Rufus as per instructions

Staudey

marcvg I'll try with an older version of Rufus as per instructions

The instructions happen show a screenshot of an older Rufus version, but this doesn't mean you have to use an older version. Or do newer Rufus versions no longer offer the "DD Image" mode? (in which case we'll have to update the instructions). If they do offer it, just use "DD Image" with the new Rufus version.

Staudey

marcvg Notice how it extracted 'solus-enroll' from /efi.img

Yeah, not sure what Rufus is doing exactly, but it obviously doesn't work quite right, now does it? 😀

marcvg

Rufus 2.5 showing this message when trying to write DD img (as per preparation instructions):

marcvg

Staudey I know.. just wanted to try the "according to documentation"-way to see if that worked.

The DD option on the latest Rufus is weird, it will ask you once wether to use ISO of DD mode, following times it won't ask anymore as if it 'remembers' the iso used. Not sure how to trigger the pop-up.

Anyway, I'll try once more with latest Rufus & DD, if that fails : I'm switching back to ye olde and trusted (but slightly degrading) Dell workstation (a beast that's been running Solus since first image, or pretty darn close to it) to create the live-usb in the terminal!

alfisya

Or maybe use etcher. Its recommeded on macOS guide, but etcher also work the same on Windows.

marcvg

Linux FTW!

Live-USB correctly created in Solus. The Rufus approach in Windows was not working for me.

Managed to install with Secure Boot enabled on an 2nd empty SSD. Copied over the /EFI/Microsoft files to linux boot to enable multiboot.

Thanks all!