@techhelpkb

TL;DR: #GRUB assumes that the file system is valid, and might execute arbitrary code if it isn't.

That is a perfectly valid assumption…or it would be if #Microsoft wasn't still trying to ice-skate uphill by pushing #SecureBoot.

News flash, Microsoft: Secure Boot is only secure if the #BIOS is secure, and I'm sorry to break it to you but that is absolutely hopeless.

@tofugolem
Don't You hate it that there's no standard way to access the #BIOS?
It's always a matter of endless restarting to find the right key.

@Eeyore_Syndrome

I downloaded the #gnome-iso from the #Bazzite website. There were no significant problems during the installation. However, when the PC started for the first time after the installation, an error occurred due to the #secure #boot. I then deactivated the Secure Boot, restarted the computer and lo and behold, everything worked perfectly. Then I read through the documentation and took a closer look at the mistake, which is very well explained there.

https://docs.bazzite.gg/general/installation_guide/secure_boot/

After the changes in the #BIOS regarding the Secure Boot, I started again and everything was fine.

Steam was already pre -installed and I just had to register and then download my games again. After several attempts, I found that the mouse was not recognized in some games. When researching further, I found that it may be a problem with Gnome.

#gaming
#Linux
#immutable

@Eeyore_Syndrome

Ich habe das #GNOME-ISO von der #Bazzite-Website heruntergeladen. Während der Installation gab es keine nennenswerten Probleme. Allerdings trat beim ersten Start des PCs nach der Installation ein Fehler aufgrund des #Secure #Boot auf. Ich habe daraufhin den Secure Boot deaktiviert, den Computer neu gestartet und siehe da, alles funktionierte einwandfrei. Anschließend habe ich die Dokumentation durchgelesen und mir den Fehler genauer angesehen, der dort sehr gut erklärt wird.

https://docs.bazzite.gg/General/Installation_Guide/secure_boot/

Nach den Änderungen im #BIOS bezüglich des Secure Boot habe ich erneut gestartet, und alles war in Ordnung.

Steam war bereits vorinstalliert, und ich musste mich lediglich anmelden, um anschließend meine Spiele erneut herunterzuladen. Nach mehreren Versuchen stellte ich fest, dass bei einigen Spielen die Maus nicht erkannt wurde. Bei weiterer Recherche fand ich heraus, dass es sich möglicherweise um ein Problem mit Gnome handelt.

Since the people who know about kernel parameter parsing via GRUB, did not see my post and because I forgot to use the AksFediverse hash, I hunted for an answer and am reading this one...

https://linuxconfig.org/how-to-set-kernel-boot-parameters-on-linux

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