Update: It’s fixed! Spoiler tag for anyone who wants to think about what it could be before send the solution.

spoiler

I don’t know why exactly this fixed it, but Max_P suggested deleting the pipewire and wireplumber folders and restarting. This has solved my issues!

Original post:

Hi there.

I swapped the drive because my old steam deck is the “good” one, the first one we bought. My wife has been using it so much lately, we decided to get a second one. She doesn’t need a 2TB drive, so I swapped it with the 512GB one that came with the “new” deck.

Why not just give her the new deck? It’s screen is cracked, and it has other issues I’m going to fix. I want her to have the nice one.

The issue is software related, the headphones work fine with the old nvme. Likewise, I slapped a 256GB 2280 drive in there, did a fresh steam install, and it works fine.

Things I’ve tried:

Searching online, nobody else seems to have this exact issue.

Restarting with headphones plugged in.

Rapidly changing between outputs in the settings.

Going into desktop mode and manually fiddling with the headphones in the audio settings.

Bluetooth headphones work fine.

So far nothing makes the wired headphones work.

I don’t want to factory reset my Deck, but I will if I have to. My next step is to do a system repair using the install media, to see if it finds and fixes anything. But it gives a warning about potential data loss if it fails. So first, I am running rescuzilla and backing up the entire drive. I don’t have a spare nvme big enough to test that backup, so it’s not really a backup, but, that’s where I’m at.

Does anyone else have any suggestions?

Thanks

Edit: added to the things I’ve tried

  • rotopenguin@infosec.pubEnglish
    9·
    11 days ago

    👆 this sounds like the most probable fix. I suspect OP buried a very critical factoid - moving the drive between OLED and LCD models. The systems have some significant hardware differences (as evidenced by the Windows drivers changing so much that Valve took a long time to update em). Somewhere, Pipewire has squirreled away details about routing or preferred devices from the old system.

    Heck, there might be journalctl log entries being generated you plug into the headphone jack. Pipewire could already be trying to tell you exactly what’s wrong.

    • beastlykings@sh.itjust.worksOP
      4·
      11 days ago

      This was the solution, deleting the pipewire and wireplumber folders and restarting was the solution.

      To be clear though, I definitely swapped from one LCD model to another, so I’m still not sure why it was failing 🤷‍♂️

      Glad it’s fixed though!

      • tinchs@lemmy.world
        3·
        11 days ago

        Disregard, I found it. Looks like it also worked!

        ~~Sorry, could you please give more context on what you deleted and where?

        I tried looking for that ~/.local/ folder but can’t seem to find it :/ I’m still new to Linux/Steam OS~~

      • rotopenguin@infosec.pubEnglish
        2·
        11 days ago

        Huh. Mmmaybe the LCD model has board revisions that are still different enough to trip things up? It’s definitely a bug to have wireplumber not “do the right thing no matter what hardware it booted up on today”, it would probably take a Valve engineer to chase that down and submit a patch.

        • beastlykings@sh.itjust.worksOP
          1·
          11 days ago

          That makes sense, definitely weirdness. Funny it didn’t bother it the other way around, the other deck is fine 🤔

          At any rate, I’m done worrying about it haha