I been having issues with the cheap hp gaming laptop with Linux, One CPU core runs at 100% no matter that do i tried masking and disabling stuff, changing the Network card, adding Ram, and some desktops like Gnome forks had issues as well, KDE, and Mate work fine but it looks like it maybe has a Firmware, Driver or a Kernel issue, so far i tested it with Fedora, Fedora rawhide, Ubuntu and Mint, I’m going to test Debian next.

The laptop i had issues with Windows 11 works fine. https://www.walmart.com/ip/HP-Victus-15-6-inch-FHD-144Hz-Gaming-Laptop-AMD-Ryzen-5-8645HS-NVIDIA-GeForce-RTX-4050-8GB-DDR4-512GB-SSD-Mica-Silver-2024/5395277312

Edit Only Gnome 3 forks have issues with the Nvidia Drivers i will retest it at a later date with a new install and one CPU thread runs at 100% with all DE’s and OSes but Windows 11.

Edit 2 I think i found the issue AMD APUs on some systems with Nvidia GPUs will spam the system the bug report i found said to disable the iGPU. also Gnome forks work fine i think it was my fault for not disabling secure boot.

  • @[email protected]OP
    1•3 months ago

    A big issue i have it does not show any process running at 100% and i tested Kernel 6.8 to 6.11.Rc.x Nvidia Release, Beta etc I used performance and the default’s on Ubuntu and Fedora, i even tried to disable USB power saving mode that is a common issue with Linux on laptops, you think something like amd_pstate=guided etc will fix it? I seen many types of hardware, driver and firmware bugs over the years but i have not seen one like this in maybe 6-10 years and the last was a Intel atom CPU? and maybe a few Realtek Driver issue’s, i’m going to try Debian unstable etc soon, but i need to buy a USB SSD but my LMDE laptop with a backport Kernel works fine on my other laptop without a Nvidia GPU, and i think Debian’s Kernels has AMD-TEE support as of Kernel 6.9.7?, i have not had to debug hardware in a long time and i have a lot going on for the next few month’s so if up stream does not fix it i can start debugging I’m going to do a little bit like disabling hardware to see if it is the nic or a usb port etc.

    • UnfortunateShort
      2•3 months ago

      You should almost always use amd_pstate=guided/active on anything newer than Zen 2, although Arch Wiki says active is the default since kernel 6.5. Even if it doesn’t seem to fix the problem, it’s the preferred way to run those CPUs (if it works). guided + conservative scaling governor might help. Maybe it’s just a reporting bug tho, wouldn’t be a first for AMD.