toad.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server operated by David Troy, a tech pioneer and investigative journalist addressing threats to democracy. Thoughtful participation and discussion welcome.

Administered by:

Server stats:

387
active users

#uefi

3 posts3 participants0 posts today

In the adventures of Bob's "Perfect" #Slackware install, I've been struggling to get Secure Boot working on my #Thinkpad x280.

Something seems to be preventing me from loading a custom Platform Key, while none appears loaded, and everything seems 'right' -- #SecureBoot is in Custom / Setup mode.

The unfortunate thing is ... using Secure Boot and signing kernel images and efi executables is not a common practice, and the documentation seems lacking explanations for people with my particular issue; method 1 of using `efi-updatevar` returns an error "Cannot write to PK, wrong filesystem permissions", method 2 -- updating from the #UEFI 'bios' -- is not an option on an x280, and method 3, using KeyTool.efi returns the error "Failed to update variable: (26) Security Violation".

I am wondering if there are some further setup settings that need to be adjusted to allow this operation, if perhaps my pk.auth file is incorrect in some way, if my machine was, from the factory, unable to allow custom Platform Keys, or if someone has modified it since then.

Rabbit holes are a pain in the dick, and now I'm in a position where I'm kinda 'forced' to learn a bit more about the mechanics of Secure Boot, under the hood.

Anyone got some good tips for where to start solving this puzzle?

I have been referencing:

- wiki.gentoo.org/wiki/User:Saka
- wiki.linuxquestions.org/wiki/H

wiki.gentoo.orgUser:Sakaki/Sakaki's EFI Install Guide/Configuring Secure Boot under OpenRC - Gentoo wiki

this older #dell #xps 13 is absolutely stumping me

can boot to #uefi USB devices and install operating systems to disk no problem

cannot get it to ever boot from said disk, secure boot on or off, legacy boot on or off, nada. just endless "no bootable devices found." frustration grr.

Die Upgrade-Falle von Windows 11: Wie man alle Sicherheitsupdates bekommt

Microsoft hängt einige PCs mit Windows 11 schon jetzt von Updates ab, sogar mit Windows 11 gekaufte. Im Podcast klären wir Hintergründe und zeigen Auswege auf.

heise.de/news/Die-Upgrade-Fall

heise online · Die Upgrade-Falle von Windows 11: Wie man alle Sicherheitsupdates bekommtBy Jörg Wirtgen
#ct#ctuplink#UEFI

🦎 Bad News for Older Computers! openSUSE Considers dropping Legacy BIOS Support
@itsfoss

「 One of the main arguments behind this planned move is said to be the x86-64-v2 architecture requirement on the upcoming SLES and Leap releases that act as a “compatibility filter”, where devices supporting x86-64-v2 or later are assumed to support UEFI 」

news.itsfoss.com/opensuse-drop

It's FOSS News · Bad News for Older Computers! openSUSE Considers dropping Legacy BIOS SupportShould users of older hardware be worried?
Replied in thread

This is the massive list of GRUB sub commands that I have to wade through

I have taken a Higher Grade Android to make this photograph and luckily this camera system knows how to capture the Light of the IPS LED panel in Total Darkness.

Compliments of Open Camera Android version

#bash#csh#ksh
Replied in thread

I'm going to include another photograph to give you an indication of how complex GRUB is in comparison to Legacy Lilo

When I press tab twice in Rapid Succession, the whole screen is filled with commands that I can execute within the GRUB sh {command environment}

I literally have to read all the man pages of those GRUB sub commands which give me an indication that they can do what I want, just so I can pass the parameters to the kernel

GRUB has made the distance between the command prompt and the kernel much bigger!

#bash#csh#ksh