Today's update to Main/Beta broke controls completely

[Intoxicus]

Title.

I had use the touchscreen to do anything at all.

Going back to Steam Client Stable didn't fix it.

It doesn't register any controllers in Desktop mode in Steam's controller settings.

[Intoxicus]

It appears to only happen on the main channel. I went to beta/beta and it cleared up.

[Tsukiko]

Same, just happened to me, only touchscreen now works :O SD is now completely unusable.
Using TS to get to the settings-controllers shows no controllers detected.

Edit1: trying beta-beta channel as previous person said, will see if it works again

Edit2: Beta-beta does indeed fix it again (though it did stall during update and need a hard reset). I hope main-beta gets fixed soon :< between no controller and the blackscreens, it's gotten rather buggy the last week

[0x1D3A]

Same here. When put Deck to sleep, fixed itself.

[Intoxicus]

Originally posted by 0x1D3A:

Same here. When put Deck to sleep, fixed itself.

I went back to 3.5 and tried it out and it does work.

But overall at this point the pain in the ass of 3.5 outweights any benefits it has.

Until they get 3.5 in better shape I'm staying off main and sticking to preview.

[浅蘇芳]

// 30th July updated..

Found jupiter-hw-support-20230728.1-2-any.pkg.tar.zst zst package is updated and released!

The command line Fix method as below, and the details at #17

sudo steamos-readonly disable
curl -LO https://steamdeck-packages.steamos.cloud/archlinux-mirror/jupiter-main/os/x86_64/jupiter-hw-support-20230728.1-2-any.pkg.tar.zst
sudo pacman -U jupiter-hw-support-20230728.1-2-any.pkg.tar.zst
sudo jupiter-controller-update
sudo steamos-readonly enable

Looks like type 2 controller has this issue, type 3 is fine.

You could try to copy the files and update the controller again manually.

sudo steamos-readonly disable
cd /usr/share/jupiter_controller_fw_updater/
sudo cp D20_APP_REL_64C16821.bin D20_APP_REL_64C16820.bin
sudo cp D21_APP_REL_64C16820.bin D21_APP_REL_64C16821.bin
sudo jupiter-controller-update
sudo steamos-readonly enable

[Tsukiko]

Personally, I'd rather not mess around with that stuff myself, I'd rather wait a few days until the main-beta branch is fixed for all controller types. I can live without some of the main-branch features for a few days :<

[浅蘇芳]

Originally posted by Tsukiko:

Personally, I'd rather not mess around with that stuff myself, I'd rather wait a few days until the main-beta branch is fixed for all controller types. I can live without some of the main-branch features for a few days :<

ok, but basically.
the reason that you could see D20 and D21 files name are mistake in /usr/share/jupiter_controller_fw_updater/ folder.


The script is say:
64C16820 is required for D20
64C16821 is required for D21

cat  /usr/bin/jupiter-controller-update 

# Build Date 26-Jul-2023 (REL-20230726 tag)
CURRENT_D21_FW_TS=64C16821
CURRENT_D20_FW_TS=64C16820
CURRENT_RA4_FW_TS=64C16831

elif [[ $bootloader_type -eq 2 ]]; then

  if [[ $hybrid = "true" ]]; then
    info "Updating Hybrid SECONDARY of Type 2 System"
    run_firmware_tool program --secondary "$CURRENT_FW_FILE_D20"
  else
    info "Updating Homogeneous SECONDARY of Type 2 System"
    run_firmware_tool program --secondary "$CURRENT_FW_FILE_D21"
  fi

  info "Updating PRIMARY of Type 2 System"
  run_firmware_tool program --primary "$CURRENT_FW_FILE_D21"
 info "Firmware updated to $CURRENT_D21_FW_TS"

else
  info "Unknown System Type " + $bootloader_type
fi

// 28th July updated
looks like Type 1 also have the issue, because Type 1 also use D21.

if   [[ $bootloader_type -eq 1 ]]; then
  info "Updating Type 1 System"
  run_firmware_tool program "$CURRENT_FW_FILE_D21"
  info "Firmware updated to $CURRENT_D21_FW_TS"
elif   [[ $bootloader_type -eq 3 ]]; then
...omit...
elif [[ $bootloader_type -eq 2 ]]; then
...omit...

[Falkentyne]

100% working fix. (I have Type 1 apparently).
You can trust him fully.

[KS45]

I experienced the same issue today after upgrading the client. Steam support suggested I send it in for RMA.

[Tsukiko]

I trust the above procedure and can see what it will do, but i'm worried that I'd have to do that procedure each time I update on main-beta until valve fix it (might write a script for it and save on desktop to run each time if it happens again).
I might try the fix over the weekend once i get my dock and kb/mouse setup (since controller won't work).

[KS45]

I followed the above procedure and it fixed my deck and same here I'm afraid that I might have to repeat the same procedure for every single future update until there's an official fix.

[Intoxicus]

Glad to see there's a workaround.

For me personally 3.5 has become more trouble than it's worth.

And there's some odd quirks. Like yeah 3.5 has a vibrancy slider. But it break vibrant deck's ability to change gamma levels. They also need custom gamma settings.

Mango Peel doesn't work as well on 3.5. In general decky loader plugins don't work as reliably on 3.5.

Age of Calamity specifically is broken on Yuzu only on 3.5. I can actually play it now on Preview Channel(3.4.8)

There's the gamma and volume bugs. And the new volume limit is a hair much.

I get that main is the bleeding edge. And that sometimes tonfigure a problem out you need to break things more and see how it plays out.

For me personally 3.5/main channel isn't worth the benefits at this time. I'll come back when it improves.

[浅蘇芳]

Originally posted by Falkentyne:

100% working fix. (I have Type 1 apparently).
You can trust him fully.

Thanks for your comment.
You are right, looks like Type 1 also have the issue because Type 1 also use D21.

if   [[ $bootloader_type -eq 1 ]]; then
  info "Updating Type 1 System"
  run_firmware_tool program "$CURRENT_FW_FILE_D21"
  info "Firmware updated to $CURRENT_D21_FW_TS"
elif   [[ $bootloader_type -eq 3 ]]; then
...omit...
elif [[ $bootloader_type -eq 2 ]]; then
...omit...

My steamdeck Type 3 so I don't have any issue during the upgrade.
I heard my steam friend steamdeck controller was broken after upgrade,
so I recommend him to rename the files then upgrade the controller firmware manually.

[KS45]

where do you find the information about the type of steam deck, type 1, 2, or 3?

[浅蘇芳]

Originally posted by kevin_k4ever:

where do you find the information about the type of steam deck, type 1, 2, or 3?

Here is the controller firmware upgrad script, it will determine Type 1,2,3 from the hardware and serial number.

cat  /usr/bin/jupiter-controller-update

Also you may debug the script when you append set -x to the 2nd line.

set -x

Then run controller firmware upgraded script for watching the details.

sudo jupiter-controller-update