Aunque todavía no he podido repararlo creo que ya tengo identificado el error de grub.

Estaba convencido de que había algún problema con lo que se estaba cargando y yo quería tratar de ver si había algún reporte de error en las variables EFI punto no lo encontré, pero escribiendo ls_env para tratar de ver el entorno, grub me dijo que no existía el archivo /efi/ubuntu/grubenv.

¿Por qué no existía?

Porque grub-install y grub-update me instalan grub en /efi/max (que es lo que *estoy* arrancando).

Ahora solo necesito
1) copiar /efi/max a /efi/ubuntu,

2) Averiguar por qué ni la reparación de arranque del modo de reparación de Ubuntu ni boot-repair han sido capaces de detectar el problema.

3) averiguar qué hay que cambiar para que max busque su arranque en el sitio adecuado.

#linux #grub #linuxboot

@whitequark What's not wrong with vendors?

• None of them do #LinuxBoot proper, or even #ARM64+#UEFI!

I managed to get the HEADS firmware to boot my existing fedora install, but only after I reinstalled GRUB2 on that. GRUB2 has nothing to do with the boot process (HEADS uses kexec to directly run a kernel), but apparently HEADS requires its configuration to be present on /boot. Even if I manually set up the kexec_*.txt files on there, it claims that no bootable configuration could be found. Very odd. #linuxboot #firmware

@OhMyGod @bsi @BNetzA @BMWK @EUCommission @digitalcourage ja, weil under #ARM64-Mobilgeräten kein standarditisierter Hartdwaretree vorliegt und alle #Integratoren und #SoC-Vendoren irgendwelche shice zusammenkoksen!

• Mit #AMD64 ist das Hardwareproblem gelöst und #ARM könnte es auch wenn,#UEFI oder zumindest #LinuxBoot genutzt würde und brauchbare #Treiber vorhanden wären!

Ich bin ja für #RightToRepair, #RightToAPI, Verbot.von #Digitalzwang und #Supportpflicht für Hersteller samt Zwangs-#OpenSource-Lizensierung nach #Supportende!

• Gerade die Masse an 100% vermeidbaren #Elektroschrott infolge von #AntiRepairDesign ist absolut inakzeptabel!

@OhMyGod Ja, das ist aber seitens #Google so gewollt denn die wollen es zu #iOS enshittifyen mit Zwangs-#Doxxing aller Entwickler!

• Leider verpennen @bsi, @BNetzA, @BMWK & @EUCommission genau das!

Wenns nach mir ginge wäre #ARM64-#UEFI (oder besser #LinuxBoot auf allen Plattformen) bei #Smartphones vorgeschrieben um diese #Elektroschrott-Produktion zu stoppen!

• Leider gibts auch kaum brauchbare #Aftermarket-Firmware abseits von #LineageOS und ich nutze #Waydroid für #Android-#Apps!

#Enshittification

@adingbatponder yes as in the #remite part of it is offline so no #AMT functionality.

• But the general #microcode is still there.

This is called a "#neutered #ManagmentEngine" and "permanently disable" is also an option on commercial #UEFI|s like #ThinkPad.

• Personally I want #LinuxBoot instead of UEFI!

@LunaDragofelis @dborch Ja, und ich bin der Ansicht dass dies durch #Standardisierung gefixt werden kann.

• IMHO sollten Regulierer wie @EUCommission daher #UEFI bzw. #LinuxBoot nee. "NERF" - Unterstützung vorschreiben damit "generische" #ROMs entwickel- und baubar sind.

#ARM - insbesondere #ARM64 - unterstützt das und es wäre daher trivial entsprechend dies zu verlangen.

• Das würde weitaus mehr für die #Umwelt leisten als #USBc als gesetzlicher Standard wenn es darum geht #Elektroschrott zu vermeiden!

My proposal "#LinuxBoot for the #Community" was rejected by @nlnet.
Quite unfortunate, but I got a job again anyway, so I don't depend on it and would have had to pass it on.

If anyone is interested in the idea, please do reach out to me though - there is always another chance to apply, plus @sovtechfund and possibly others.

Het tuig aanpakken!

I just did a full #LinuxBoot from our graphical menu. :D

https://www.youtube.com/watch?v=gpOJrqOjBHI

I just successfully did a `kexec` on the TP-Link M7350 v3 router via `cpu`, using kexec-tools:

cpu-tpl $KEXEC -cf arch/arm/boot/zImage

I.e., we can now #LinuxBoot!
Well, we still need to gain NAND flash support and get the kernel to boot without lk2nd directly, but the PoC is done. :)

cpu-tpl is my script wrapping cpu to set up a namespace and use the fixed IP address. $KEXEC is just the full path to my Arm 32 build of kexec.

If I get any of the grants I applied for, I will do #live streams again for the #development. ✨👩‍💻✨

Thus far, I asked:
- NLnet to fund #LinuxBoot integration with U-Boot XPL
- OSFF to fund further development of #Intel ME tooling

The former will be much more work.
And the latter would be integrated in https://fiedka.app and @coreboot.

Today, we met with a small group of people working on #LinuxBoot and #Racklet. Starting at Hackerbrücke, we went by the Google Arnulfpost campus that is still being worked on, then got some lunch nearby.
https://realestate.withgoogle.com/arnulfpost/

We continued walking around in the sunshine ☀️ and made up some bogus historical non-facts, chatting around and passing by Lenbachhaus where we stopped for a while to enjoy its garden. Finally, we went toward Marienplatz where we split again to get back home. A fun day! 🥳

@tauon #Microsoft did!

• That's why they pushed for #CensirBoot!

IMHO #USEFI is an irredeemabke #Bloatware and needs to be replaced with #LinuxBoot aka. #NERF!

https://en.wikipedia.org/wiki/LinuxBoot

Currently debugging #BashCoreLX: it boots into CLI on TTY1 as intended, but startx errors pop up due to .Xauthority issues, hostname not found, or X server already running.

Switching to TTY2 and running sudo startx works, LXDE starts fine.

Goal: make TTY1 stay clean CLI-only, no automatic X attempts, no startup errors. Working on suppressing X server noise and managing session permissions.

#Linux #Debian #MinimalLinux #LXDE #TTY #Startx #Xorg #BashCore #LinuxBoot #Debugging

@wolf480pl @cas I just assume they don't want to have to deal with a gazillion of undocumented SBCs that may only get 1 person to once push code that gets accepted, but then "orphaned" and break over time as they may not be willing to build & test every new kernel before release just to enshure it ain't broken!

• Espechally since #ARM doesn't have just a bootcode.bin and #UEFI to boot from, but half a dozen different mechanisms ranging from fixed sector location and -sizes for the initramfs to #uBOOT & #LinuxBoot, #Coreboot and potentially even #OpenFirmware-style #bootcode...
  

It's absolute chaos and one of the reasons I didn't even try to build @OS1337 for the #Pi0W as of today...

Oh nice, the kexec patches for RISC-V in https://github.com/horms/kexec-tools have just been merged 2 weeks ago! 🥳

that added support for loading Image files and kexec_file_load

yay #LinuxBoot!

Here is one:
https://book.linuxboot.org/use-cases.html

The #LinuxBoot book keeps growing. :)

"Since bootloaders run before operating systems run, they mostly have UEFI-provided services as APIs to rely on. Therefore, bootloaders do not benefit from modern operating system security features"

https://www.microsoft.com/en-us/security/blog/2025/03/31/analyzing-open-source-bootloaders-finding-vulnerabilities-faster-with-ai/

#linuxboot

Would be cool to see #linuxboot or #coreboot on the @frameworkcomputer #framework12 being worked on when it releases. Wish my eyes didn't haze over when looking at code, otherwise I'd help get it running.

@novacustom

Grateful to NovaCustom for their generous financial contribution and collaboration to integrate Heads firmware into their hardware offerings.

This partnership highlights the growing adoption of Heads as a trusted solution for secure boot verification and tamper detection.

Looking to adapt Heads to your specific needs? Explore our consultation services: https://osresearch.net/Consultation-Services/

Want hardware preflashed with Heads? Check out our trusted vendors: https://osresearch.net/Vendors/

#OpenSource #FirmwareSecurity #Heads #linuxboot #firmware #cybersecurity #qubesos #linux #security #coreboot