@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...

@cas @wolf480pl granted, the distain is mutual, given almost all #SBC & #SoC vendors refuse to do basic #documentation on how their shit works and barely release some dodgy images with custom kernel modules.

• @olimex and #RaspberryPi being an exception of the norm, but #Rockchip, #Allwinner and other SOCs are a real pain in the ass to support unless they are #ARMv8 with #UEFI to boot.

#Apple's Hardware does have @AsahiLinux as project to care for and is popular enough to be worth the hassle for them, as it brings decent performance and battery runtime to the table...

@eloy @merlin #UEFI and #AppStore are what's wrong with the whole concept of #EFI...

• it's #bloated & messy shite!

@simonzerafa I mean obviously #reuse / #UseLonger is better and if your options are "corporate surplus" or nothing then I'd never judge.

To me it's just that #ThinkPad as a brand has really died as every single Device is a #downgrade in #repairability & #upgradeability compared to my #X230Tablet:

• They have #SolderedDownRAM even on P-Series #Workstation machines, not just cheap cheap #Lenovo consoomer devices.

• Batteries ain't toolfree-swappable anymore!

• #WWAN modules are worse (i.e. #Fibocom #850GL aka. #Intel #XMM7360)

• #Linux support gets worse and neither Lenovo nor @ubuntu feel responsible on a "#Ubuntu-certified Workstation" (i.e. #P15v)

• Less & Worse #Docking options.

• Most machines don't offer Linux or to eveb to opt-out of #Govware noone should pay their overcharged premium for (in fact #Microsoft pays Lenovo $25 for every #Windows #preinstall so they don't ship Linux, they don't even pay the $10 for an #OEM-#UEFI-Key, much less the $135+ of a #SystemBuilder version they charge for!)

• ...

Personally, I wish I had €.€€€.€€€ so I could just develop the #NUCbook and be done with the #Enshittification of #Laptops / #Notebooks!

For the HP Prodesk G4 (and other HP models) if the Keyboard or Mouse isn't working in the UEFI Firmware or Grub menus the workaround in the JetKVM is to go to:

Hardware -> Settings -> USB Devices

and select Keyboard Only in Classes.

There is something wonky with HP devices USB HID support at Boot that means it won't detect JetKVM USB HID devices if the Classes option is set to more than one item in the Classes list.

Weird

@georgetakei

Maybe a 4 day poweroff will make it wake up and boot properly.

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

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!

The camera of the Android is utterly failing to focus on the dimly lit IPS Led flat panel screen, but I have still captured a photograph of the command shell of GRUB

I have found the way to add parameters to the kernel at both time from GRUB
I'll make a photograph in a number of minutes

Now I read about gub

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

I dived into the disappearance of Lilo on all distro's. It turns out that Lilo was only usuable on BIOS, it did not evolve to UEFI systems.

I wanted to easily pass commands to the kernel pre-boot. Before I dive into the workings of grub, can anyone tell me where i Need to go to parse pre boot parameters through grub to the kernel?

https://en.wikipedia.org/wiki/LILO_(bootloader)