Infernal_pizza @ Infernal_pizza @lemmy.world

Posts

17

Comments

207

Joined

2 yr. ago

Does it run at a playable frame rate yet?

Edit: Oh it’s PlayStation, I thought EA play was PC only

You forgot about the few random settings that can only be changed with powershell for some reason!

Probably uses less power

Nah I don’t really need the latest kernel, I’m just worried the it’s kernel will eventually be updated and get the same problem

That makes sense, for the amount I use this laptop I won’t worry about it for now! It wasn’t noticeably dusty when I opened it yesterday, and the errors occur immediately after booting so I wouldn’t expect it to heat up that fast

In that case if it still works should I just ignore the error for now and replace the card if it causes any issues?

Thanks that’s sorted it! I must have not noticed the error before as I usually install btrfs-progs after chrooting and it looks like installing it triggers mkinitcpio to run again anyway

How?

By safe I guess I more meant should I be doing anything beforehand. I’m running snapper on btrfs so even if I do completely destroy everything it’s not too much of an issue but I’d rather avoid it if possible!

I found out how to check for orphaned packages with pacman thanks to another comment so I’ve removed them now

Wow I seem to have loads

I never knowingly installed these, the only packages I’ve intentionally installed from the AUR are heroic games launcher and 7-zip. And the only kde programs I’ve manually installed is the plasma-meta package, kde connect and ksnip. I think they were previously part of the plasma-meta package and have now been removed or replaced with the plasma 6 versions

That just means they deliberately made the game tedious with the goal of annoying people into paying

Any chance you can send it to me as well?

I just tried increasing it but the maximum I can set is 255 and that made no difference unfortunately. All the Windows VMs are also set at 8 and they don’t have any problems

Literally 1984

I hope its not a hardware issue, the 2 VMs were running on 2 separate hosts within the cluster so hopefully that's unlikely! Thanks for taking a look

I've just edited the main post with links for the journalctl output. The purpose was just to test some network config, I managed to do what I needed anyway but I'm just curious as to why I had issues with these VMs!

I just left it as default which is 1 display and 8mb video memory