ThePiGrepper

I noticed that GPD Win Max 2 2025 comes with two different CPUs, the newer AI 9 HX 370, but also the same Ryzen™ 7 8840U that came in the 2024 model. So, are these two the same, or does the 2025 release comes with any other difference. I cant find refurbished or used ones from 2024 at much lower prices so I'll probably but a new 2025 one from Droix if the newer version comes with many advantages. do you know any?

I try to update my system after a couple of weeks and now I need 52 new packages between lib32-* packages and others, just because newest Steam needs lib32-libappindicator-gtk2...

Using latest linux and systemd package. Already tried downgrading to previous systemd package and nothing improved. Any suggestions?

Thanks for being in my life Arch.

DISCLAIMER: This is an issue happening on my netbook using Arch32, so I dont know if I can post this here. I'd like your opinion anyway, so any comment saying that I need to change my hardware, although it's true that I cant avoid it, if possible I'd like to focus on the issue at hand instead(I have several other x64 systems using Arch, so I'll have future posts regarding those for certain XD)

After upgrading my system from xorg-server 1.19.x to 1.20.x, my system (an HP Mini 210-4000 with a Atom n2800 CPU and GMA 3600 iGPU(not supported by intel driver, but some support available with xorg-server itself). After upgrading it, the system no longer started X, when the display manager greeter s

After upgrading my system from xorg-server 1.19.x to 1.20.x, my system (an HP Mini 210-4000 with a Atom n2800 CPU and GMA 3600 iGPU(not supported by intel driver, but some support available with xorg-server itself). After upgrading it, the system no longer started X, when the display manager greeter should appear, instead a black screen appears with only a single blinking dash at the top. I know for a fact that this package is the one causing the issue, because my system works perfectly fine without any other xf86-video-* package, and after downgrading this package back to 1.19.*, it works fine again. My main concern is that some big change occurred upstream in between those two version th

I was confused for a min, I think the theme changed as well. I'm not quite sure what changed but it feels different somehow. Where's Thunar 1.7 btw???

When I rebooted the kernel starts, but instead of loading the lightdm greeter, I find a blinking screen with the following message: nm-dispatcher: req:1 'hostname' : new request (0 scripts) nm-dispatcher: req:1 'hostname' : completed: no scripts

What does it mean? Besides knowing that it probsbly has to do with networkManager package breaking something, now I think chrooting to the Void from my Arch partition and uninstalling for now networkmanager or at least disabling nm with runit can be the way to go. What do you think? Did you experience something similar?

I compiled kernel v4.17-rc1 a couple days ago. For the first time since I have this machine, some ACPI errors appeared. Normally I'd not take it too seriously, but today I happened to witness the first related bug(probably). I open guvcview and my laptop totally froze. The caps lock key led started blinking, and everything else stopped working. This isnt happening with any other kernel version with similar config. I'm almost sure that it is related to the ACPI errors during boot. Here's the log: https://pastebin.com/C3diiqAs Anyone who has knowledge of ACPI, or maybe has encountered something similar on their machines. please help me.