Will it easier just run konsole after fresh install and set the gamescope
Will it easier just run konsole after fresh install and set the gamescope
Aerr, not sure if it will fix the problem on fresh install, but you can try. why not try hitting the
return to game mode icon on fresh boot?
MAnother fresh install, the boot up doesn't have
Allow me to ctl alt f2
Allow me to ctl alt f2
SI want to customize the Bazzite Portal app, is the app open source?
M
Awhy are you running it while already in desktop mode?
Athat command opens desktop mode 
Aonce in desktop mode, just click the
return to game mode icon on the desktopAyou need to load desktop mode, and then return to game mode from desktop mode.
MI can't get ctl alt f2 to work during boot
Aon the blank screen?
MYes
Ait should be when you boot, and see the blank screen
A
Athen how did you get into desktop mode in the first place?
Athe command is only necessary for to get you into desktop mode
Athen from desktop, return to game mode
Aan alternative solution is to connect an external monitor at least once while you see the blank screen on boot.
MOk gamemode is working, installing updates
M
MI think there is something mess in the installation
MAfter installation it boot into desktop mode it after when try to boot into gamemode I get black screen
Aupdates can take a while, try waiting a bit
VInstalling bazzite when I get home 
RDoes MTPDeck work yet by chance? I guess I have to back up everything on my Deck after all
Hback buttons work but has to be configured in windows using the 8bitdo application or through android/ios using 8bitdo ultimate software (the controller does not have to be paired with the controller)
gyro works only in switch mode (with dongle beta firmware) or bluetooth mode (which is locked to switch mode)
gyro works only in switch mode (with dongle beta firmware) or bluetooth mode (which is locked to switch mode)
Hand if you need the beta firmware i have it archived somewhere
TI can confirm that is my experience with the 8bitdo Ultimate BT as well
Tspecifically, the back buttons are not separately bindable in Steam
Hyeah this is because steam input offer no way to bind them, valve focuses only on the 1st party controllers with extended functionality (or its just that there is no "proper" way to remap the back buttons on other controllers without reverse engineering every single one of them, which valve wont do)
RJust to add on to this, if MTPDeck doesn't work yet, how do you guys usually back up your things from the Deck?
Hits called yafti and yes it is
TGitHub
This application is responsible for installing Flatpaks on first boot after a user finishes installation. It is intended as a replacement for custom zenity dialogs. - GitHub - ublue-os/yafti: This ...
KNot yet, I use a USB drive
KMight work next update on testing branch
RIs there an ETA on that?
ROr is it a while out? Just seeing if I should wait or not.
TDoes anyone know how to set Bluetooth to turn on automatically after switching to desktop mode from boot
VIs the bazzite loading screen supposed to be sideways?
Aif your device's display is a portrait one it will be
Ais Miraclecast (open source Miracast) installed on Bazzite out of the box?
VI thought that'd be changed for Deck
Ahm, i'm not sure what orientation the actual deck's display is. i never ran anything but steamos when i had it
VIt's a vertical display rotated in software
Vso i wanted to install bazzite on my desktop but when i try to boot from my usb (made with fedora media writer) it gives an error saying "image unsupported" and boots right back to windows
Aanyone see really slow network transfer speeds? everything says i'm connecting at 1Gbps+ wifi-wise, but i'm getting transfer speeds around 1Mbps, even to the lan (i'm on a lenovo legion go)
KNope, should be normal for you at least once everything is configured. Possible it's DeckHD related
VThat's what I was thinking
KCan always use a stock sb/Kinoite installer and then rebase
Hgo into the USB root and navigate to
that should fix the
EFI/fedora/ and copy grubx64.efi and paste it into the EFI/BOOT/, then rename BOOTX64.EFI to something else and now rename grubx64.efi in the BOOT folder to BOOTX64.EFIthat should fix the
image not supported issue and odd bioses refusing to boot the usbH@KyleGospo ^ thats also some workaround for you to add to your list of tricks too, as if they get that error, stock atomic fedora might also get the same issue
