bazzite
bazzite copied to clipboard
ublue-os
USB keyboard and mouse don't work on Steam deck
Just after the installation of bazzite 39 my keyboard and my mouse don't work
Can confirm..deck will lockup/freeze after a short period of pressing keys on any usb keyboard connected so not brand specific keyboards cause it all seem to.
I've encountered this as well. An update was installed this morning, and I I found myself unable to use a keyboard to enter my drive encryption password. I reformatted the device and the USB and Ethernet from the dock work during that process, but once I boot into the desktop for the first time, the Ethernet connection is no longer available and USB no longer works. I've tested this with multiple docks and adapters, and encounter the same issue on all.
Same situation. After fresh install of bazzite 39, my mouse and keyboard not working also usb via dock station.
Yep same here. Docked experience is now broken for whatever reason.
Edit: Switching to unstable fixed these issues for me.
Can confirm same issue here. Using a Logitech USB mouse and keyboard combo wireless. Everything is fine until I press a key, then the system locks up in both game mode and desktop mode
Yep same here. Docked experience is now broken for whatever reason.
Edit: Switching to unstable fixed these issues for me.
Unstable version of what?
Yep same here. Docked experience is now broken for whatever reason. Edit: Switching to unstable fixed these issues for me.
Unstable version of what?
The unstable branch of Bazzite:
rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:unstable (or ...bazzite-deck:unstable for deck version or whatever image you're using.)
Unstable is exactly what it sounds like though, it's unstable. The good news is that most likely the fix is already there, but it's not in the ":latest" (stable) channel yet.
This should be fixed as of the latest update, thank you all for the reports.
This should be fixed as of the latest update, thank you all for the reports.
Okay well this is still a problem except its now on both latest and unstable in my experience.
Just tested my deck with the Dell dock I have at work that was working on Friday, keyboard and mouse are dead. So it was an update I received towards the end of the week. Also my Logitech keyboard and mouse are still dead as well.
I will add, I am using Logitech devices at work as well. My keyboard at work at the moment will light up when the Deck is plugged in, but the numlock doesn't transition the light on the keyboard. Nor does caps lock. I have a razor keyboard I can test tonight to see if it works. But as of right now, wired and wireless Logitech devices do nothing on my Deck.
I just use a generic usb keyboard its acer branded but theres nothing special about it or anything doesn't require drivers. And it didn't work either.
I've tested with both a Razer and Logitech keyboard, an Anker dock as well as the official Steam one, and a simple USB A-to-C adapter, and none of them are registered in the OS.
I have same issue. I tried resetting the usb PD via pushing ... and - and that did not work. I have unplugged and pluged in many variation to no avail
Works with USB XHCI mode
Confirmed, was just able to enter encryption key, and Ethernet is working on desktop.
Works with USB XHCI mode
That explains the discrepancy in testing, DRD also prevents booting from USB drives.
Works with USB XHCI mode
That explains the discrepancy in testing, DRD also prevents booting from USB drives.
Is DRD the default setting in bios? As i never touched mine and i always have been able to boot from USB.
It is. I hadn't heard of DRD before, but it appears to be an option to allow the Deck to be connected to another computer as a mass storage device. Since that's not a default behavior of the Deck I'm not terribly worried about changing it, though I would be interested in hearing if there's additional use cases for the setting.
Switching to XHCI mode has fixed my dock at work 👍🏼
Now just to test my stuff at home
Works with USB XHCI mode
That explains the discrepancy in testing, DRD also prevents booting from USB drives.
Is DRD the default setting in bios? As i never touched mine and i always have been able to boot from USB.
XHCI is the default, most people would have DRD on due to previous use of the DeckMTP decky plugin requiring it.
Works with USB XHCI mode
That explains the discrepancy in testing, DRD also prevents booting from USB drives.
Is DRD the default setting in bios? As i never touched mine and i always have been able to boot from USB.
XHCI is the default, most people would have DRD on due to previous use of the DeckMTP decky plugin requiring it.
Yup I now remember enabling this a long time ago. That's why I forgot about it. Well I guess the issue is kinda fixed then. Minus the fact that the DRD is now broken?
Works with USB XHCI mode
That explains the discrepancy in testing, DRD also prevents booting from USB drives.
Is DRD the default setting in bios? As i never touched mine and i always have been able to boot from USB.
XHCI is the default, most people would have DRD on due to previous use of the DeckMTP decky plugin requiring it.
Yup I now remember enabling this a long time ago. That's why I forgot about it. Well I guess the issue is kinda fixed then. Minus the fact that the DRD is now broken?
Yep, I'll look into that next.
Works with USB XHCI mode
That explains the discrepancy in testing, DRD also prevents booting from USB drives.
Is DRD the default setting in bios? As i never touched mine and i always have been able to boot from USB.
XHCI is the default, most people would have DRD on due to previous use of the DeckMTP decky plugin requiring it.
Very interesting. I never enabled DeckMTP or adjusted this setting, but had DRD on. Could it possibly have been a default setting on an earlier version of the hardware or BIOS?
Works with USB XHCI mode
That explains the discrepancy in testing, DRD also prevents booting from USB drives.
Is DRD the default setting in bios? As i never touched mine and i always have been able to boot from USB.
XHCI is the default, most people would have DRD on due to previous use of the DeckMTP decky plugin requiring it.
Very interesting. I never enabled DeckMTP or adjusted this setting, but had DRD on. Could it possibly have been a default setting on an earlier version of the hardware or BIOS?
Same here and i know mine is DRD but i never used deckmtp or had any reason to change it..🤔
Yeah, found this issue the hard way, one part of the driver is missing from Fedora, see here. It should be fixed shortly, and I can confirm that XHCI is quirky on the latest kernel since a commit from Valve impeded the XHCI stack to load by default on it. As soon as @KyleGospo complete the akmod to include dwc3 in it's entirety this should be gone for good.
New fc39 kernel build with the dwc3 driver is available: https://bodhi.fedoraproject.org/updates/FEDORA-2023-9d54a271e2
Latest builds on :testing should fix this, we'll eventually roll this out to latest but it has secure boot implications we'll need to telegraph.