32 Replies
the lights should flash on sleep right?
Correct, its staying lit here
yay suspend broke
Going to run this ‘bazzite-rollback-helper rebase 40-20240427’
whats your current ver
20240510
Still happening here
actually fans are also on
hold the power button to reset the EC
Trying now, 40 secs
no different
sounds sort of similar to https://discord.com/channels/1072614816579063828/1239366893639307305
does suspend work when you do it through steam's power menu?
same behavior, fans are still running
I reset the bios settings, this is on the 0427 ally image
I checked for multiple HHD and only one is active and running
when i press the sleep button, it will shut off the screen, terminate my SSH session, but the fans remain on
The activity light is also constant, where when sleeping it should be blinking
theres no point on fixing this from my part until bazzite works correctly under f40
I risk breaking stuff
‘asus_wmi: ASUS WMI generic driver loaded
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: Setting up ROG USB in>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: Setting up ROG Ally i>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally not ready, r>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally not ready, r>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally not ready, r>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally never respon>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally not ready, r>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally not ready, r>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally not ready, r>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally never respon>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally not ready, r>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally not ready, r>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally not ready, r>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally never respon>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally not ready, r>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally not ready, r>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally not ready, r>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally never respon>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally not ready, r>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally not ready, r>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally not ready, r>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally never respon>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally not ready, r>
May 13 12:56:31 fedora kernel: asus 0003:0B05:1ABE.0001: ROG Ally not ready, r>’
the system should not shutdown if the powerbutton daemon is nto active
this is a new bug under f40
of course
check if extreme power saving is on
maybe that broke it
Is that a bios thing?
actually fixing the pwoer saving bug may have broken it @Kyle Gospo
no fluke decided that extreme mode should be a thing now
even though its still broken
so whereas before it was force disabled its not anymore
so the bazzite setup script will disable it
where’s this at? rog control app?
Oh, so on the Ally it's due to the extreme power mode? I think I saw some discussion about this on a different discord server
@Aru @antheas if one of you two came in here one day and told me
"a recent Ally firmware update causes water to be flammable"
I'd probably just accept it
i remember mentioning that both the kernel driver and the ally are garbage
and force setting that param every boot might cause issues
was that in the log you sent?
this was a different one let me send it
no its there too
that happens before the update script fixes it
so thats not it
maybe
thats just the kernel driver logging a lot of stuff
no idea what to try now 😔
Going back to :stable
maybe an earlier image would fix things?
I'm not sure when the extreme power mode change was introduced
Went back to 0427 still the same 😕
maybe something earlier then? 04/06?
then again, i'm not seeing other ally users reporting this issue 🤔
Yeah I wonder what their setups look like
Maybe a combination of rebasing to 04/27 from 05/10 and back
Flashed latest KDE ally image, worked until it upgraded then the suspend issue is back
this was on a fresh install
Went back to Windows installed latest MCU update, same issue. Will try to clean install again -deck image KDE this evening
I can happily report that downgrading my bios from 337 to 331 fixed my issue
what did asus break now....
No idea, It wasn’t Bazzite. I tried Nobara, Bazzite, CachyOS, Windows. For some reason it would never sleep
flashed back an older bios using the EzFlash tool from bios
Bazzite sleep works as intended 😭
😢
glad you figured it out
only took me 3 days of headaches
Sleep broke again fml
Wanted to give this closure, I ended up RMA’ing my device. New one has no issues and can’t reproduce the issue even on the same NVME drive. The SD card reader was bad but not sure if this could have been a factor, or just a MCU bug