hm you shouldnt be able to see the nintendo controller unless i pushed an update i shouldnt have
hm you shouldnt be able to see the nintendo controller unless i pushed an update i shouldnt have
Aunfortunately if you disabled rgb on windows they wont work
Aand i dont have a device to dechipher why that is
Atry the rog gui that is part of the image to see if that can turn them on, after that they will work
RSorry! I was mistaken. I don't have Nintendo controller option. Just XBox, DualShock, and DualShock Edge. I checked again.
Ayeah youll need windows for that one
RBut what is ROG GUI? asusctl?
Ayeah
ROh... Crap. I don't want to install Windows 11 on it just for the LEDs.
Ayou dont need to the leds work
Ayou only need to enable them
Aone time thing
RAnd then I have to install Bazzite, configure essential plugins, configurations, and most importantly downloading all games again. Just because of the LEDs.
Asomeone else here will have a workaround for sure
Ai think you can use windows to go or something similar
Ayou dont need to reinstall
RSorry, I don't get it. Do you mean I can use another drive to boot into Windows on the Ally?
ROr running a Win11 VM?
RHonestly, I'm considering to take out the 2TB M.2 2230 drive from my Steam Deck, and put it into Ally with Bazzite.
R@antheas Thanks! I got the idea now. I'm downloading a Hiren's BootCD PE to boot my Ally. Hopefully it could install the ROG software and to let me switch the LEDs back on.
R@Kyle Gospo did you already update the dsp to fix the "slightly" conf. mishap from Valve here? : https://gitlab.com/evlaV/valve-hardware-audio-processing/-/commit/86bc77b945cad1e766610c1faaf2ce92d1e26148
Cptyxis my beloved
Cbest of luck
Ci had so many issues w my ally in general (not bazzite related really) that im just buying a steam deck oled
Kwhat sort of issues, if you don't mind my asking?
Chorrible battery life, worse performance than the deck unless i went to 18+ watts but that reduces the battery even more
Calso on windows in particular it erased my gpu driver lol
Cin the end it just wasnt the device for me, i dont really play AAA or games like COD
P^ live windows yeeting driver 
Cfr
Cwindows is painful on a handheld pc
YWindows is painful in general
CWindows is pain
YAnyone know if bazzite nvidia is using Wayland or xorg?
BIt has both and I believe it defaults to X11 because Wayland is very janky.
TIs steam filling /run/user/1000 with a ton of sdl-shared* files for anyone else? It's saturating that directory which prevents any new apps from opening up on the system.
Cyeah
Cbut its extremely more painful on a handheld pc
KBoth, but we recommend xorg until Nvidia gets their shit together
KNow this sounds like a fun one
KI'll see if I can reproduce
TYeah it's weird, took me a minute to realize what's happening. Trying to run a flatpak gave me an error about no space available. Dug into it a bit and found all those files clogging up /run/user/1000.
Tclosing steam and deleting those files fixes things. not sure if there are other conditions to recreate besides running steam. I played games last night for a while, closed laptop, issue presented this morning so dunno if suspend is part of it, if running games or a specific game is part of it. I'll let you know if I figure out more.
TAs I run a game with gamescope, it's just slowly creating those files
Phmm... not sure if anyone have noticed but adding nonsteam games is pretty... darn slow on bazzite I'll check later if there are some useful logs
TSo my normal launch options under which the bug is occurring are "MANGOHUD_CONFIGFILE=~/mango.conf MESA_VK_WSI_PRESENT_MODE=immediate vk_xwayland_wait_ready=false gamescope --cursor-scale-height 192 --sdr-gamut-wideness 0.8 -F fsr --sharpness 0 -e -W 3840 -H 2160 -w 1920 -h 1080 -r 120 -o 120 -- mangohud %command%".
If I remove these, no sdl-shared-* files are created. So something wacky going on here
If I remove these, no sdl-shared-* files are created. So something wacky going on here
Tyeah it's gamescope, just adding a bare gamescope -- %command% starts piling up the sdl-shared-* files.
TI'm on 3.14.2-1.fc40.x86_64 so it might be different/fixed on 3..14.13-1.bazzite.x86_64.rpm
RI have another observation on my Bazzite Ally. I have configured the battery charging limit to 80% using the ROG Control Center under desktop mode. I rebooted. And I played Cyberpunk a bit to spend some battery. It dropped down to 95%. And then I plugged it to power for better performance. My device got charged to 100%!!
Cdid you have the issue where hhd dies continuously?
