Manually could I run while chrooted in for example:

dpkg -i /root/grub-coreboot.deb
grub-install /dev/sda
update-grub

Is that all it takes to do it manually? I believe grub-coreboot is just grub-pc but maybe just a few tweaks possibly maybe a few compatibility features. I am playing with a spare machine when I have time to work with everything at once.
In order to maybe implement grub-coreboot to automatically be used when coreboot is detected would take some some of check to verify the user is running coreboot bios. Which could require some creative check to see it. Might be simpler to just include the package in root directory. As grub-pc again works just fine to install. If there is an advantage to installing with grub-coreboot then manually might be quick enough anywho as it is very deliberate.

The required packages to have a encrypted snapshot? might be expected to work on a already encrypted system? Or specific packages needed for a live system to work? I don't know the specifics but I will play with it more when I get the chance.

I'll see how building an encrypted iso goes. I stumbled into it by accident in Ascii, My installer iso now is still on beowulf, but I did see the daedalus patch when I slowly try to upgrade. It takes time if I break something in upgrading to re-install of course.

Are you familiar with how the live ISO loads? As it's a hybrid iso with grub-efi and grub-pc installed. Does the bios decide which to boot than load grub essentially?
I am curious what modules the iso's grub might be loading by default if it differs on the live iso then the install or default devuan configuration. As libreboot will be removing several grub modules soon, I am curious what I would be looking to want loaded by default at a minimum from the normal devuan configuration file.
Apologies if it's a little off topic but I am curious how the live ISO sets up it's bootloader and if it's a typical grub config like a regular install? I noticed since chimaera os-prober is now disabled by default. Which is a good move.

Thanks again fsmithred

yeah. This is true. You also can't just remove it with a simple apt purge libreoffice.
Start with minimal iso maybe and build a snapshot.

Either way it takes some time.

Solved,
Was in fact a kernel module loading EC firmware

On both T400 and x200 running libreboot the EC portion of firmware would load and be default alsa device. This was corrected and is no longer visible in system.

acpi tables are complicated, I know they can be de-compiled and re-compiled. Could be custom setups that may yield more minimal setups. However, I have not experimented with custom setups yet.

Also, one way I just noticed to effect lid closure. Depending on your hardware and what kernel module you load. Is to blacklist your vendor specific kernel module for acpi table and just use generic kernel mode will be fallback. Might effect laptops radio kill switch.

run
lsmod

can use modprobe for testing. setting can be in /etc/modprobe.d/blacklist.conf
syntax is for each line
blacklist {module_name}

While you boot, from Live. Recovery style.

Depending what version of Devuan. how you had the snap shot Configured.

Upgrade path from Beowulf to Daedaleaus has been a little bit of a learning experience.

I started right at ascii / jessie. Upgrade path was a little bit to learn. Like $PATH bugs. but drivers were always solid.

Couple bugs... I should of reported. But now are now in time are bugs for Old Stable.I am realizing now.
If you had a good minimal install. Is best starting point sometimes. But, EFI installing will be harder. And, will just not work on some new hardware without some hacking with bios.Or I just need to learn the grub console better. I know how to rebuild efi entries. But working with MBR and legacy boot I have learned more about how hard drives are working. Some have firmware differences. I had installed, on Devuan repositories mind you. fwupdate, Never found any updates. But it could see my hard drive. I ran a few commands and it could of changed something on the HDD firmware side. Maybe it can be enabled to auto update as well. Depending on how you boot or if cron is scheduled or something.

dd is a pretty useful tool. Working with a new format it's basically the first thing you should grab. Nuke your drive.all memory area's you want to focus.Can write a couple times. Gutman wipe is 38 times. But that's way more then you'd ever need.

Now depending on hardware. It's good to keep EFI. as EFI enabled live USB. Can boot on almost all hardware.
So it's a lot more bloated. And up upgrade path you'd have to update grub after minimal install and then save efi built USB to get a more minimal upgrade route.

But I remember Ascii. and Jessie. pmount then it got phased out because it's just so much easier to just use regular mount. It can mount almost every file system XFS enabled is a good idea when you are building an ISO. Keep that in your tool kit. Because if you don't have in your live iso. You have to build it from the Live boot. And again, I have had much more minimal success with./

Also I ended up with an ISO that was encrypted at boot. Which was pretty cool.
refracta2usb. Don't just dd it onto the drive. Start from minimal.

Install refracta vintage that is solid place to start. And update into mainline devuan. Is simple and quick. It's got everything pretty much by default for most hardware.

Deviating too far from debian would indeed make maintenance of Devuan a tricky feat. The magic of Amprolla is much appreciated.

android has specific protocol to access its file system.
It has built in security for many devices not to be auto accessible when connected by USB.

If you enable developer settings in android you can auto enable to use it as file system. That is if it recognizes being plugged into your system.

However, the root directory and much of the system will not be mountable without rooting or mounting the device in a off state from what I understand.

Oh I'm sure there is some boot malware that can bypass secure boot implementations.

What I am interested in the possibility to buy separate TPM module from 3mdeb.com and harden the boot process.

I have had some boot issues that were questionable. Secure boot seems to have corrected it with efi stub. But if it wasn't a dell I probably wouldn't of had to use it.

I was working on a dark theme for clear looks for a bit.

It's a tricky one to do and have everything remain perfectly readable. Dusk was very easy to keep dark.
I'm sure it's possible, but will take some time. Just like matching between gtk3 and 2. Migration to gtk4 might be a future issue.

I still use the og obmenu.
I made a .deb package to make it easier to install as you can't grab it from the repos any more.

Now it's going to pretty much be pre-installed on and live iso I will make.

If it is of use. If I can learn how to I can maybe put the package to share save some people some time if they like the old gtk obmenu. Still works without a hitch. Just like you'd expect it to. There is really no reason for it to not work besides it not being maintained / depreciated. After all we still use slim.