Intel Support

[snoweuph]

Like Stated in the Readme, Intel is not supported, is it Planned for the future, or is it a thing that will never be supported?
I got an Intel Nuc of the 6. Gen, which is not working right with holoiso, so I was hoping to use this on it, but sadly Intel is not supoprted. Would love to see this run on Intel in the future

[nicknamenamenick]

Intel should be supported at the very least with the regular desktop image. If you want the Steam Deck image, it might work. Your mileage will vary since Valve's Game Mode favors AMD GPUs over any other vendor right now.

[tfranken90]

I am also on Intel hardware as well but I've been running Chimera just fine. I wasn't really expecting to run into any issues since bazzite's gamescope-session is taken from Chimera. Are there any major changes that may be causing gamescope-session to crash?

[nicknamenamenick]

There are small additions added, a newer Mesa version, and a newer Gamescope version. I would try upgrading Bazzite by opening a terminal and entering: rpm-ostree update waiting for it complete and rebooting. if you cannot do this, or it does not fix the image I would suggest using an online ISO, just make sure you connect to the internet in the installer, and using the latest online ISO as opposed to the offline one to get the latest updates: https://github.com/ublue-os/bazzite/releases/tag/v1.0.1

nevermind, read KyleGospo's response.

[KyleGospo]

We're using the same gamescope session with very minor changes, our Mesa and Gamescope is newer which may be causing these issues. Last Intel user we looked at this in depth with it was gamescope crashing due to missing/unsupported Vulkan features, and the patch to fix it upstream was seemingly abandoned for breaking other Intel GPUs that work.

[tfranken90]

That makes sense. The main issue I have run into with intel and gamescope is the INTEL_DEBUG=norbc environmental, but that seems to be taken care of in the gamescope-session-script. I am able to run steam inside gamescope while in desktop mode, other than some sluggishness from the additional overhead, it seems to work fine. I don't know if that indicates that there might be something wrong with the gamescope-session. The only other major issue I've noticed is that steam is not remembering my credentials when it autostarts.

[tfranken90]

So I ran gamescope -e -- steam -gamepadui -steamos3 -steampal -steamdeck inside desktop mode. It prompted a system update and rebooted my system. It still booted me into desktop mode, but when I ran it again I was able to get the steam deck ui experience although fsr, custom resolution, and steam input (mouse emulation) had issues. However, Return to Gaming Mode still just sends me back to desktop mode. I tried to run the same command from tty2 and it just aborted.