It was something like this:

A: Everybody shut the fuck up I got accepted into NASA

B: mind your language

A: fuck you

B: denys A the scholarship

It's not like the STD vanishes after jumping being pushed.

Fastboot was never enabled to begin with :-/

Ok, I foxed it! I looked around in the log of which I mostly understood nothing, but then I came acress the section where the kernel/shstemd mounts the drives and the error it spits out. Googling it gave me an arch forum post with the identical problem. Windows didn't shutdown correvtly the last time I used it and did something to the partition table. I'll update my post wiy the solution.

Tnx. I will report back tonight when I get around checking.

I'll check the BIOS stuff tonight.

As for the sata port, the new drive was connected to a different one so it can't be it. I did a drive health check and all seemed well and good.

I touhgt the same, but connecting a new drive and getting the same "read-only file system" error is really strange. I used the other drive for qbittorrent and it worked flawlessly before the update. I haven't come around to try any of the suggestions yet. I'll report back tonight.

I checked fstab and it's the same from day one. I tired adding stuff to it and shuffeling parameters around (like phtting rw,exec last), but it did nothing.

I'll give ut a shot first before the other suggestions. Tnx

Where would I start? Any commands I should try or just see if the livecd let's me take control?

Tnx for the suggestions. I have asked on the discord server, but no response as of now. I will take a look at those commands and see if anything fixes it.

If 13th or 14th gen, only if you get lucky and update to the microcode hotfix. GL

I tried reducing the font size to no avail. Seems it's the fonts fault.

The KDE system settings have no such option :-/ All my google results for line spacing are regarding the terminal, non for my case. I guess there is some config file somewhere that I can edit, but sine I am still nee to Linux, I jave no idea where to start.

As long as he doesn't touch my blinker fluid, all is well.

Ich habe meinen Anwalt bereits in Kenntnis gesetzt

There are a few video on YT from reputable creators highlighting malpratices Apple does on a yearly basis to rip you off in every way imaginable. Louis Rossmann and Hugh Jeffreys have done some "compilation" videos on that topic. To point you to a quick one, search for "Astonishing Anti Repair Pratcices by Apple in the last 15 years" by Hugh. If you value yourself, don't buy Apple products.

As a newbie in this space, I had interactions with a few distros over the years and lately switched (hopefully) permanently.

My first experience was with Mint 10 years ago. Installing it would cause some GPU driver defect (AMD card) and would turn the whole login screen into an epileptic checkerboard pattern with no way of doing anything. It took me a few reinstalls and a ungodly amount of googling to find a solution which involved opening the terminal at boot process. You can only imagine how frustating that can be for a newcomer.

Later in time I had Ubuntu on my laptop which had a bug that wouldn't spin up the CPU fan and it would simply overheat and shutdown. I had to take it to a technician to find out what was causing the random shutdowns.

A year ago I decided to try Debian on my desktop PC as many have praized it for it's rock-wolid stability. It didn't want to work on my PC. No internet connection and some weird bugs. Took me two-three days to get ti to work and I still don't know what exactly fixed it as I have applied every possible solition I came across.

Much later, aka now, I decided to go with Bazzite on my desktop as many have claimed excelent support. I wanted to install the mimalloc because I play Factorio a lot and a few reddit posts claimed 20% UPS improvement over the stock scheduler. After downloading the source code and following the 4 very easy steps, cmake would throw some random eerors at me claiming some critical files were missing, although they were right there in the usr directory. Turns us Bazzite some some issue and Fedora 40 compiled the code in seconds without any issues.

Conclusion: Linux users, which are very tech savvy or work in that space, know what to do when things don't work out, while the rest of us keeps googling and crying over error messages for things that seem trivial. You never seem to know if it's you, the system or your hardware.