Closed franchise2099 closed 1 month ago
Mostly the same issue.
Same version of HoloISO.
Tested with and Xbox Elite Series 2 and a Switch Pro Controller. The Xbox controller isn't seen at all by the OS and the Switch controller suffers from constant disconnects.
It worked before on non-immutable versions of HoloISO.
Specs:
Mobo: Aorus B550i Pro AX CPU: AMD Ryzen 7 5800x CPU: AMD 6950xt Wireless: Intel WiFi 6 802.11ax 2T2R & BT5
Looks like it's a known bluez 5.69 issue. https://bbs.archlinux.org/viewtopic.php?id=288754 and https://bbs.archlinux.org/viewtopic.php?id=288390 regression to 5.68 fixes it. maybe also 5.72 could work, haven't tried. all the best and great work
Interesting about Bluez seeming to be the root cause of these issues. How would I go about downgrading to 5.68? Windows power user for years, relatively new to Linux after I fell in love with SteamOS on my Deck.
Is this still happening?
It was as of two weeks ago. (Not sure if there was an update since then) I switched to bazzite. I would be more than happy to reinstall and give a report on the Asus motherboard I am using.
On Thu, Mar 28, 2024, 12:42 PM Adam Jafarov @.***> wrote:
Is this still happening?
— Reply to this email directly, view it on GitHub https://github.com/HoloISO/issuetracker/issues/7#issuecomment-2025659084, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJXWJYSX6ARYLOYBX446BDDY2RB6TAVCNFSM6AAAAABCV54PZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRVGY2TSMBYGQ . You are receiving this because you authored the thread.Message ID: @.***>
Closing issue due to inactivity
Your Issue:
Bluetooth Connection On Dual Sense, Dualsense Edge & Xbox One (bluetooth model) won't hold a connection but are recognized.
type your problem here Bluetooth can see a ALL bluetooth discoverable but cannot hold connection for controllers. (audio devices seem to work)
Your device's full specs
CPU: AMD Ryzen 7 5700X GPU: AMD RX 6700XT Mobo: Asus X570 Wifi: Intel [wifi 6 AX200]
OS version (/etc/holoiso-release):
(Only for SteamOS Session loading issues) Have you tried launching
gamescope-session
from terminal? If yes, provide a log.Did it work before?