u/Jimmy-The-Perv

Usually, whenever I browse the Linux subreddits there is inevitably a question about GRUB out of memory errors on Live ISO's when trying to install a distro.

The answers are usually a very helpfully AI generated hallucination about updating BIOS, decrease dGPU available memory, enable various modes in BIOS, fully disable dGPU etc. However, the actual solution in 99% of cases is far simpler.

As this is linux4noobs, very basically when booting, the system available memory gets "probed" as it were, and very, very poor TPM firmware reports an incorrect amount of available memory, leading GRUB to think it has an incredibly small amount of memory to load the bootchain.

Anyway, to the solution! Basically, disable TPM during initial boot and you should, in 99% of cases, see the out of memory error miraculously disappear.

This can be achieved in a number of ways, as follows.

1. at the initial GRUB menu, when the boot choice is highlighted ("boot Fedora 44", "install OpenSUSE", " give Ubuntu a try" or whether it may say), press the 'e' key to edit the kernel parameters.

Find the line starting "linux" followed by, to a noob, complete gibberish. At the end of that line as eventually pointed out by my esteemed colleague below, I had a bit of a brain fart, on a new line above that add the words 'rmmod tpm', then press Ctrl+X to boot.

For some reason I know Fedora, which I very recently installed, doesn't like the above method, so if the above doesn't work, do the following.

2. When your boot choice is highlighted press 'c' to enter the interactive console.

In this console type 'rmmod tpm' and press enter.

Then type 'normal' and press enter.

Then proceed to boot.

Hopefully the above will alleviate a lot of the GRUB out of memory problems. Nothing any of the distros can do as its crappy manufacturer firmware causing it.

Quick question; I know the game is currently only built for windows and I'm running on Linux, so its not a whine about bugs etc (actually pretty happy with the game. Runs very well with no discernable bugs yet) but is it a thing for everyone or just a linux thing that my password isn't saved on the login screen?

I wouldn't mind, but I made a password in my password manager, not a chance I can remember it (or indeed even type it, with its high-ASCII characters), so its just a slight annoyance that i need to unlock my password manager and copy it over every time I fire up the game.

Thanks a lot.

Hello all,

Thought I'd better ask the question on here before I raise a bug report.

Basically, since the 6.7 update, vsync seems to hard-lock games to 30fps.

I sometimes plug my laptop into my TV via HDMI to play games, and when I plug into TV, I enable vsync. Games often start up at 60fps, then after 30 seconds or so, stutter and settle down to 30fps. No settings changed from how they used to be to give me 1080p60.

Games tested:

Persona 3 Reload

Witcher 3

Atomfall

Marvel Rivals

Has some settings somewhere been turned default on in the 6.7 update?

Specs:

Laptop.

i7 14650HX

RTX 4060 Mobile (595.80 Open driver)

32GB DDR5.

OpenSUSE Tumbleweed. I don't think its an OpenSUSE patch. Plasma 6.6 used to report the WM as Kwin (SUSE Linux) but this 6.7 update has the WM as simply Kwin (Wayland).

Thanks for any input

Edit: further tests I've just thought to conduct, all the above games when played on my laptop screen (eDP) with vsync on return 60-120fps.

I've seen several posts about linux controller users getting the popup saying along the lines of "can't update firmware, check cable is secure" and no firmware update happening. Happened to me.

Anyway, I've just had an update delivered (I'm in the beta channel, dunno if it's in the mainline client yet) and the firmware updated on both controller and puck, no issues. Fedora 44 KDE, incidentally.