Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I tried the battery storage mode thing, reinstalled Steam OS, turned on/off the power management for wifi. Non of them worked. Did looked into desktop mode and typed "lsmod | grep 88" DID NOT see RT88 or any network interface.
This is what I mean, though......where did you type that command? What does it do?
Everywhere I look, there's an entirely different command/code string just to get Linux to even *look* for a device depending what version you have. There's a different one for Ubuntu, for Fedora, whatever the heck "Mint Cinnamon" is......
I just want to know if my bluetooth is busted.....
In your terminal application, which in KDE is called Konsole.
lsmod lists (ls is the command to list the contents of a directory) the kernel modules that are in use. The pipe | takes the output of one command and feeds it into the input of another. grep searches through text for a text string that you've given it, and returns lines that contain that string.
Just to add to the discussion, on your Linux system (SteamOS) a lot of things are managed with systemd.
If you want some information quickly on your system you can, for example, run the command
If you want more information on a specific element of this list, you can then run the command
I'm not an expert in Linux, but I hope that with these additional pieces of information you will be able to find a solution to your problem.
One last thing, systemctl is a big thing that offers a lot of commands, some of them can have an impact / modify your system, so be sure to know what you are doing before running them. The commands I listed above will not change anything and will just return some information.
In the intervening months, following some more system updates, the issue seems to have cleared up on its own and the Steam Deck can see and use its bluetooth adapter again.
Not entirely sure what the cause of the issue was, but it seems it was likely something in one of the prior updates that broke it, so luckily, it seems that it took other subsequent updates to the system to unbreak it and get it working again.
Rebooting didn't help me, but the following worked:
1) Turn on airplane mode;
2) Turn off (not restart) the Steam Deck;
2.1) Clap your hands;
3) Turn on the Steam Deck and turn off airplane mode.
1) Open file explorer
2) On the left pane under devices click on "rootfs"
3) Click into the folder "etc"
4) Click into the "bluetooth" folder
5) From there we need to open the "main.conf" file and make a change.
6) From here scroll down until you're between lines 114 to 116 and here you will find a setting that says "D-Bus Experimental" and it looks like this.
# Enables D-Bus Experimental interfaces
# possible values: true or false
#Experimental = false
7) Change the experimental line to "true" (leave the quotes out). Save your changes then reboot and you should see that Bluetooth is back.