No audio on Steam Deck after bazzite-deck:latest update
I updated my Steam Deck with the latest update but the update ended up breaking up my audio. And for some reason, sometimes it just doesn't let me boot into gamemode at all, leaving me stuck on a black screen. Rebooting it temporarily solves the issue but it still sometimes happens.
97 Replies
I had this issue too on
Bazzite-deck:testing but thought it was because I was on my OLED Deck. No audio output devices found at all. It also couldn’t find my network card but that’s probably an OLED-specific bug.
and about half of the time I’d get a black screen in the transition between boot and game mode or desktop to game modesame for me as well
really strange
but I'm LCD instead of OLED
this has been happening to me as well
made an issue for it https://github.com/ublue-os/bazzite/issues/591
GitHub
[Bug] No audio after latest update · Issue #591 · ublue-os/bazzite
There isn't any audio on the latest update and gamemode often won't load as well Someone on discord said this "I updated my Steam Deck with the latest update but the update ended up br...
It's the same for me no sound since I upload :/
But I haven't any network issue
Confirmed, they broke something in the latest pipewire changes
And it seems to also cause freezes here.
Probably related to the missing audio service.
I briefly encountered this issue on Bazzite 39 21-11-2023 when that was latest. It was sorted on next boot wituout me updating. I'm guessing this is a more permanent issue on the today's latest build?
Yes
No audio and it hardly boot as a result.
Would love to debug further but the doesn't boot part is in the way.
God bless the rollback, once you can press escape with an external keyboard at boot time to start the previous image XD
How did you rollback ?
I tried and it couldn't load the window manager so I did a Ctrl-Alt 2 to connect by the term and do a update
I hope I can roll back again but with the thing working
Escape at boot, select the previous booted image, then enter desktop mode and run rpm-ostree rollback.
It will select the correct image independently of the image booted.
I am so glad that we can have multiple rollbacks instead of one rollback in steamos or worse, no rollbacks like in traditional linux distros
Worst day to pick to do a clean install it seems. I can install do first boot but on any reboot I get stuck with black screen and since it is a clean install I have no prior grub options
I don't find it maybe it's because I have an encrypted divice ?
I had this happen to me too but not on a clean install. I rolled back, tried to update again, got black screened. eventually it just booted to the new version, but now I'm having this audio issue too
mine is unencrypted and I have the same issue
Are you talking about rollback ?
no, the latest build
I'm going to go ahead and rollback to my last working build from 20231120. good thing I pinned it while I was able to briefly gain access
When I press Esc on start i'm going on the steam deck boot options but I don't unterstand where I can find the rollback version
I got it to show up once after pressing continue, but it really only worked once. after re-updating to 1129, it did not come back up again
the rollbacks are in grub. try esc and if it doesn't work then try B
I also tried Esc, but it also didn't work after the first time
I don't see grub at any moment :/
It will not be stable
I managed to get to a display only once
yeah, I'm rolling back and not updating
You should see a set of boot options
They are ordered from newest to oldest
Just for record keeping, here are the rolled back packages in case it helps debug the issue: https://pastebin.com/xwRpRGT1
If you select the second one from the top, you should get the last one working in your system.
they're probably in the same situation I was in where I couldn't get grub to show up by holding B or Esc
I got the BIOS menu
Now press continue and spam esc again
You should get the grub menu
Something in here caused the issue if I have to guess.
Although the display problem is odd.
I'm not sure if gamescope depends on pipewire, but it might be.
I’m almost certain it does
But without being able to pull logs from the running system, it's a bit of a shot in the dark.
GitHub
gamescope/meson.build at 183e632631eb401f8cf9cc98b92f40e0dbe7326b ·...
SteamOS session compositing window manager. Contribute to ValveSoftware/gamescope development by creating an account on GitHub.
Yep.
It's just the broken pipewire then.
how could I forget about spamming presses? I only held 😓
New in breaking computers? Welcome /s
Yeah, it enters only on events, not on held 😛
hah, different device = forget everything
on my desktop, I spam because of how fast the BIOS screen goes away compared to the olden days
Geez this is a fun one, looking at it today
will I'm glad you're on it
how could you fix it since it is upstream?
Yeah clean install so no roll back will give it an hour or 2 from now if no solution the will have to install nobarra since I am going on holiday friday
there's probably a way to specify a past deployment, but that probably depends on existing access to the system (even may be ssh when gamescope is stalled)
You can rebase to a specific date
They're all tagged that way
what would the commands for that be? tbh i'd kinda like to get bazzite up and running, for the brief period i used it on my machine steam performed much better than on chimera os.
especailly on a fresh install in my case but i think they'd be the same
Sadly the 2 version are (I don't know why) the 29.11 version 😢
rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite:39-20231121
replace bazzite with the version you want
that's the previous buildnod, tyvm :) might give it another go, might also just wait for the fix since i just got chimera back and running. (ideally i want to figure out if i can have both use the same
$HOME/.steam/)Looking into this right now
Might be related to the overrides, I'm gonna rebuild gamescope as well just in case
Think it's related the faust2 and steamdeck DSP stuff?
possible, but those are just configs
That's true. Probably related to overrides in that case
No audio devices in gamescope or desktop mode
Not seeing the black screen bug being reported
I’m guessing the missing wifi is OLED only because of the new chip?
for me i got the black screen from a fresh install. i would go throught the bazzite portal on first boot, then reboot, plug in external montior to do the steam initial flow, during the install process it reboots with more time remaining, and then steam never restarts.
(device is lenovo legion go)
it stopped happening to me suddenly
If you open Steam in desktop mode before rebooting does it still do it?
steam was running but not logged in during those attempts.
steam already autostarts when in desktop mode
Missing firmware
That’s what I figured. Same issue exists on Nobara.
Thanks Valve to be quick as always for upstreaming stuff /s
should be fixed in kernel-fsync
Just putting them into place hasn’t been as simple as you’d expect. I gave up pretty quickly since it’s way out of my area of expertise
Yeah, it's all readonly.
Yes but better safe than sorry. I've bumped the archive that gets used as a fallback. Might help with this
It's random.
will the new build resolve the audio issue too?
But to me dodging it is almost impossible 😛
sometimes, it takes a few minutes for game mode to load
Mine is black from 15 min now.
So no, it's just a random chance that gamescope decides to not die on you without pipewire
I consider it to be completely stalled when the dpad + buttons provide keyboard inputs visible on the display
For example
anyone?
For questions like these I'd recommend looking at Bazzites commit history. Have no intention of leaving builds with broken audio and am currently testing a few things
It's steamdeck DSP. Rebased to testing, audio worked. Layered the DSP and lost audio @KyleGospo
New builds will have working audio for Jupiter. Should be out in 15 minutes
Interesting, it worked fine on unstable.
Odd.
Are you using Galileo or Jupiter?
Jupiter.
As the LCD one.
@EyeCantCU lack of DSP means we have to restore some files in system_files
I'll look into that soon
then debug DSP being silly
That's very strange. In testing, Kyle removed the Pipewire replacement workaround I implemented yesterday and steamdeck DSP. I rebased to testing and audio was fine then installed it and lost audio
Oh shoot. Hadn't noticed that
Last week when it got merged and kyle pinged me to test unstable I switched.
Audio was 10 times better.
No microstutters or anything.
Unstable hadn't been built with it iirc
Builds started failing 9 days ago
Oh, so just placebo.
That makes more sense now XD
Likely
Oh, pull stuff from main for the DSP
It's still quite in movement for bugs like these.
Might be worth to track the latest code from devs.
so excited
Thanks a lot it worked for me !
But at first I didn't notice but it's the basic version so to mension if you have the deck-gnome version to put for exemple : bazzite-deck-gnome:39-20231121
Maybe put a unvalide code this way people that are not always focus like me don't go to fast ^^
Like :
rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/YOURCHOICE:39-20231121
everything is working now
I can update ?
yes go ahead
audio works but there's still a really weird issue with the audio. if I leave the deck untouched for like 20 seconds and then I navigate through the steam menu, there's no audio for like 5 seconds and then it appears again
also whenever I try to boot into a game, the audio isn't available as well for like 5 seconds, afterwards it's fine
a bit annoying on my end, wondering if there's a fix for this issue.
Rebase to testing and see if that helps
I have to unplug and plug in headphones for the audio to work
are you on :testing
no
Try updating, if that doesn't fix it highly recommend you rebase to testing
Lot of improvements there and a fix for DRD
everything seems fine now. thanks guys once again!
If you're not already on :testing give it a try, audio gets even better