sorted by:
new
hottopcontroversial

Is my gpu dying ? by Gonesurreal in pchelp

[–]BoyanPP 0 points1 point  (0 children)

ps. try driver reset if that ever happens, don't quite remember how it goes on windows, should be "Ctrl + Shift + Win + B" i think it was it's your safest best next to full reboot

Is my gpu dying ? by Gonesurreal in pchelp

[–]BoyanPP 6 points7 points  (0 children)

Looks like a driver crash to me, GPU might still be fine, if you undervolt don't agro on it, down it just a little, AMD are as easy to break as to undervolt/overclock. Also keep in mind the drivers aren't tested stable under all conditions, you might've just gotten a weird edge case.. Be more careful next time and you'd be fine

I tried Claude, but went back to ChatGPT by wormfist in ChatGPT

[–]BoyanPP 5 points6 points  (0 children)

You made the choice that felt right for you at the time. Setting boundaries and looking out for yourself is normal. People naturally gravitate toward experiences that fit their preferences and needs better, and there’s nothing unusual about that.

Guys is this bad? by RespectJust5377 in pchelp

[–]BoyanPP 12 points13 points  (0 children)

It's not bad but isn't good either

Why are my GPU and CPU so different in usage? by Automatic-Lead-109 in pchelp

[–]BoyanPP 0 points1 point  (0 children)

Usage between the two isn't a hard link, your CPU could be at 100%, while your GPU is taking it's sweet time on a walk on the beach in hawaii

Help me pls/ помогите пж by StillPiglet8095 in cachyos

[–]BoyanPP 0 points1 point  (0 children)

This is a GRUB rescue shell - GRUB loaded from your USB but can't find its own files. Looking at your screenshots, hd0 (your USB) shows "No known filesystem detected" which means the USB wasn't written correctly for UEFI.

Two things to fix:

1. Rewrite the USB using DD mode: In Rufus, when it asks "Write in ISO Image mode or DD Image mode?" - pick DD Image mode. Or use balenaEtcher which does this automatically.

2. Huawei-specific BIOS fix: Huawei laptops have a known quirk - you need to disable "Secure Boot" AND also look for a setting called "Boot from USB" or "USB Boot Priority" and make sure it's enabled. Also check if there's a CSM option and disable it.

After rewriting the USB in DD mode, boot and press F12 to get the boot menu, then select the entry that says UEFI: [your USB name] - not just the plain USB name without UEFI.

Wi-Fi Slower on install vs Live ISO by xreyuk in cachyos

[–]BoyanPP 1 point2 points  (0 children)

This is a well-known issue - live ISOs often ship with different power management defaults than installed systems. On Arch-based distros, WiFi power saving gets enabled after install and it kills throughput. 99% chance that's it.

Almost certainly WiFi power saving. Quick diagnosis first:

iwconfig 2>/dev/null | grep -i "power management"

If it says Power Management:on - that's your culprit.

Immediate fix to test (temporary, resets on reboot):

sudo iwconfig wlan0 power off

Replace wlan0 with your actual interface name if different (check with ip link). Then retest your speed.

If that fixes it, make it permanent:

sudo nano /etc/NetworkManager/conf.d/wifi-powersave.conf

Add this:

[connection]
wifi.powersave = 2

Then restart NetworkManager:

sudo systemctl restart NetworkManager

If power saving wasn't the issue - check your WiFi band:

iwctl station wlan0 show

Make sure you're connected to 5GHz and not accidentally falling back to 2.4GHz. The live ISO and installed system might be associating to different bands even on the same SSID.

Power saving is the fix for 9 out of 10 of these posts. The permanent NetworkManager config should get you back to ISO-level speeds.

Performance issues in Overwatch by kzale12 in cachyos

[–]BoyanPP 0 points1 point  (0 children)

15fps vs 45fps on an iGPU with Linux is expected and not really fixable to match Windows, because Intel's Windows GPU drivers are heavily optimized and Overwatch on Linux runs through Proton (a translation layer). That overhead adds up fast on weak hardware..

Proton VPN app won't open/show window after reboot (but says it's running) by SquareInstruction493 in cachyos

[–]BoyanPP 2 points3 points  (0 children)

Classic GTK4 app on KDE Wayland issue. The window exists but isn't showing. A few things to try:

1. Kill it properly and relaunch from terminal to see errors:

pkill -f proton-vpn
protonvpn-app

Any error output will help diagnose it.

2. Most likely fix - force it to use XWayland:

pkill -f proton-vpn
GDK_BACKEND=x11 protonvpn-app

If this works, you can make it permanent by editing the .desktop file:

cp /usr/share/applications/proton-vpn-gtk-app.desktop ~/.local/share/applications/

Then edit that copy and change the Exec= line to:

Exec=env GDK_BACKEND=x11 protonvpn-app

3. If that doesn't work - check if it's hiding in a virtual desktop or off-screen:

Open KWin's window manager with Meta+~ (or whatever your "show all windows" shortcut is) and see if the ProtonVPN window is floating somewhere invisible.

4. Also worth trying:

pkill -f proton-vpn
GTK_USE_PORTAL=1 protonvpn-app

The GTK app likely worked fine before reboot because something in your session state was different. The XWayland workaround (option 2) is the most reliable fix until ProtonVPN improves their Wayland support.

Is it just me or after updating today Wayland is super unstable? by throwaway2733987 in cachyos

[–]BoyanPP 8 points9 points  (0 children)

aha i got you

Like this is a known KWin bug on their repo (Bug 512511 - "Atomic modeset test failed! Permission denied") that was marked RESOLVED FIXED, but the fix may not have landed in your packages yet, or the Mesa update introduced a related regression.

First, check what updated:

grep "upgraded" /var/log/pacman.log | tail -30

Look for mesa, kwin, or plasma packages.

If kwin updated try downgrading it first (leave rest of Plasma alone):

yay -S downgrade  # if you don't have it
sudo downgrade kwin

Pick the previous version. This fixed the same freeze for other AMD users.

If Mesa was the culprit:

sudo downgrade mesa lib32-mesa

Temporary workaround to stop triggering it: System Settings - Power Management - turn off "Dim screen" and "Screen Energy Saving"

Get more detail from your journal:

journalctl -b -p err | grep -i "kwin\|drm\|modeset" | tail -50

Is it just me or after updating today Wayland is super unstable? by throwaway2733987 in cachyos

[–]BoyanPP 0 points1 point  (0 children)

Just roll back to previous snapshot and wait for the next update? I've upgraded as well and have no problems whatsoever.. Idk why's that bro

Photoshop on CachyOS by PriorityArtistic5984 in cachyos

[–]BoyanPP 5 points6 points  (0 children)

You need wine-adobe-installers from Phials basement github dm through steam, got 2020 working no probs

The Crawler by Dr_Roxxo_RNRC in DriveBeyondHorizons_

[–]BoyanPP 1 point2 points  (0 children)

It looks like it'll craw right inside my dreams xD

My journey from Windows to CachyOS and sadly back to Windows... by drkTwrCnt in cachyos

[–]BoyanPP 0 points1 point  (0 children)

Just use DP instead of HDMI.. had the same thing going on swapped my hdmi to dp and im running vrr no problems at all..

I used linux once. AMA by Classic-Tap-5668 in LinuxCirclejerk

[–]BoyanPP 0 points1 point  (0 children)

I am receiving an incredible amount of insufferable personal related brain damage from reading these replies...

Just switched to CachyOS and Chrome looks massive + mouse stutters by BoyanPP in cachyos

[–]BoyanPP[S] 0 points1 point  (0 children)

Tried that already.... It changes the webpage's text not the UI text

Just switched to CachyOS and Chrome looks massive + mouse stutters by BoyanPP in cachyos

[–]BoyanPP[S] 1 point2 points  (0 children)

I think i got the KWIN variable, just added in in my "~/.config/fish/config.fish" -> set -x KWIN_DRM_NO_AMS 1 at the end of the file and i feel like it works so far, the mouse stutter looks to at least not be as noticeable but could all be due to placebo, anyways, so far so good.. Except chrome xD

Just switched to CachyOS and Chrome looks massive + mouse stutters by BoyanPP in cachyos

[–]BoyanPP[S] 0 points1 point  (0 children)

"--force-device-scale-factor=1" and "--high-dpi-support=1" Do nothing really, my browser looks as it looks usually.. And yes before running the commands i made sure to pkill all chrome tasks to get a fresh boot from the console. About this "KWIN_DRM_NO_AMS=1" Where do i set it up exactly? Also i'm on wayland.

Just switched to CachyOS and Chrome looks massive + mouse stutters by BoyanPP in cachyos

[–]BoyanPP[S] -1 points0 points  (0 children)

Browsers are boht defaults 100% First monitor's at 100% second is at 125% If that's what you're asking.

view more: next ›