ChimeraOS now not capturing every CPU core
ChimeraOS now not capturing every CPU core
Hello, I own an HP EliteDesk 705 G5 SFF with these details: Ryzen 5 3400G 16GB DDR4 RAM, 1TB WD Green M.2 RX 6400 4GB. I've been testing ChimeraOS and it's functioning well so far. But yesterday during a session of Outer Worlds, the performance dropped significantly. I thought it was due to thermal throttling because I was running high settings. However, Gamescope showed the CPU at 100% utilization, only using one core while others stayed idle. After rebooting, the interface seemed unstable and the system settings displayed my hardware correctly but labeled my CPU as a single-core processor. The issue occurred during gameplay without causing a full crash. What could be causing this?
Entering the BIOS typically displays the processor details, including all cores if available. Booting a Linux live USB can show the system information and boot options presented by the OS.
I would attempt to reinstall the CPU and repaste the system to check for faulty pin connections.
I attempted to start from Windows because I didn't have a Linux USB available, and it worked fine. The CPU displayed properly with all its cores listed. I verified the BIOS settings as well, and everything looked correct. After resetting the BIOS, switching back to ChimeraOS still showed it running on just one core. I tried changing the beta channel in hopes it would fix the problem, but it didn't help. I'm considering a ChimeraOS issue rather than a hardware fault, though it feels unusual. I've attached some images for reference.
I faced a comparable problem on my older Intel i5 6600K with cores 1 and 3 disabled, which slowed down the system. It turned out I was launching into the "steam-plus" session. Switching to the default "steam" session resolved the issue, allowing all four cores to run and improving performance significantly. To achieve this, enter desktop mode and execute: chimera-session steam. I’m not entirely sure why steam-plus disables two cores, but it seems related to how it wraps Steam within an OpenGamePadUI environment. That setup has a bug where it assumes the CPU only has two cores, applying a profile that turns off the remaining two. I discovered this by switching to an OpenGamePadUI session, opening the QAM, and trying to adjust the core count—I could only set it to a maximum of two.