Installed steam os in an athlon dual core laptop from 2010 😲

I did not think it was possible but I pulled my old college dell latitude and realized hey this is amd... I wonder .. I simply put the USB stick in it and it fully installed steam os... I am so surprised, although this thing only has 8gb ram it came with 4 and I added another 4gb back then I thought it was bad ass back then...

Specs:

Processor: AMD Athlon II Dual-Core (e.g., M320, P320, N350) running between 2.1 GHz and 2.4 GHz.

Memory: 4GB of DDR3 RAM (a major jump from the DDR1 used in 2003).

Storage: 250GB SATA Hard Drive

Graphics: Integrated ATI Mobility Radeon HD 4200 or 5430 series, which allowed for 720p/1080p video playback and light gaming.

Everything seems to work, was able to run terraria no problem

So i want to build a PC and i think im gonna install SteamOS.

I like SteamOS more but im a keyboard and mouse gamer so should i use the big picture mode os thing or stick to the normal UI

Finally fixed Bluetooth audio on SteamOS + Echo Studio

My Echo Studio would connect to the Legion Go, but it never showed up as an audio output. It only appeared as a Bluetooth device.

I spent way too long messing with PipeWire/WirePlumber configs and codecs. The actual fix was:

BlueZ 5.83 → 5.87

After updating bluez, bluez-libs, bluez-utils and bluez-deprecated-tools to 5.87-2.4, the Echo started exposing the proper A2DP profiles.

Installing BlueZ 5.87 on SteamOS

⚠️ IMPORTANT: SteamOS is read-only by default.

If you try to run pacman -U while read-only mode is enabled, you'll get:

error: could not lock database
error: failed to lock database: Read-only file system

Temporarily disable read-only mode BEFORE installing the packages:

sudo steamos-readonly disable

Then install the downloaded packages:

sudo pacman -U ./*.pkg.tar.zst

After the installation finishes successfully, TURN READ-ONLY MODE BACK ON:

sudo steamos-readonly enable

Then restart Bluetooth/audio:

sudo systemctl restart bluetooth
systemctl --user restart wireplumber pipewire pipewire-pulse

Check the version:

bluetoothctl --version

You should get:

5.87

Then reconnect the Echo:

bluetoothctl connect 40:89:C6:C8:16:0F

The Echo then appeared as an A2DP sink. I set it as the default output with:

wpctl set-default 119

(119 was the sink ID on my system, so yours may be different.)

Before the update I was getting:

a2dp_select_capabilities() Unable to select SEP

After 5.87:

Legion Go → Bluetooth A2DP → Echo Studio ✅

So if your Bluetooth speaker connects but doesn't appear as an audio output on SteamOS, check your BlueZ version before going down the WirePlumber rabbit hole.

Hi. Is any of you successfully installed dual boot windows on drive which already contains steamos ? I’m not fancy wiping it off if there’s a way to avoid that

Also I had an idea to make 3rd partition for steam games to share between windows n steamos but still unsure if Its worth a hassle and even possible.

Ideally I would like to have windows as non steam app without having grub menu while switching my legion go 2 on an steamos in my default system of choice

Thanks

I just finished building and installing SteamOS on my PC, and the first thing I downloaded was L4D2. At first, the system let me in the game, but when I tried playing in Dead Center, it would just crash, and no matter how many times I did it, it would also crash. And then the next day, I downloaded Wuthering Waves, and after it finished downloading, WuWa would just crash or randomly abort when I tried to get in. Please help; this is a new system, and I don't want problems like this.

Ryzen 5 5600X
Rx6600
16 GB RAM

Hi everyone,

I'm trying to install the official SteamOS on a desktop PC with two NVMe SSDs.

Hardware:

- CPU: AMD Ryzen 7 5700X

- GPU: AMD Radeon RX 7600

- Windows 11 is installed on a separate SSD

- Target SSD: Great Wall GW3500 2TB NVMe

- The target SSD contains no important data

I want to install the official Valve SteamOS alongside Windows 11. Windows is on a completely separate SSD, and I'm installing SteamOS only to the GW3500 2TB SSD.

The installation consistently gets stuck at:

"Discarding device blocks"

After waiting, the installer fails and the Linux kernel reports errors such as:

- nvme timeout

- device not ready

- aborting reset

- Buffer I/O error on dev nvme0n1

- identify-ctrl: Input/output error

At one point, after the failure, `nvme list` could no longer see the SSD, although `lsblk` could still see `/dev/nvme0n1`.

After completely powering off the PC and turning it back on, the NVMe became visible again.

I also found that the SteamOS installer tries to run a controller firmware update script, `jupiter-controller-update`.

On my desktop PC, this step appeared to be problematic because the hardware is not a Steam Deck.

I modified/bypassed the controller firmware update part of the installation script so that the installer would continue without running the Jupiter controller firmware update.

After bypassing that step, the installer was able to proceed further, but it still failed later at:

"Discarding device blocks"

At that point, the kernel reported:

nvme timeout

device not ready

aborting reset

Buffer I/O error on dev nvme0n1p6

I also tried SteamOS 3.7.x instead of 3.8.14, and the same "Discarding device blocks" problem occurred.

So there seem to be two separate issues:

1. The `jupiter-controller-update` step may not be appropriate for my non-Steam-Deck PC.

2. The NVMe controller also times out when the installer performs discard.

I initially tried SteamOS 3.8.14, and then tried SteamOS 3.7.x. Both versions fail at the same "Discarding device blocks" stage.

Some additional information:

The SSD is still detected normally by the BIOS, and after a complete power cycle it becomes visible to `nvme list` again.

Has anyone experienced a similar issue with an NVMe SSD during SteamOS installation?

Could this be a firmware/compatibility issue between the GW3500 and Linux NVMe discard/TRIM?

Would adding `nodiscard` to the filesystem creation step be a reasonable workaround for the SteamOS installer?

I'm mainly looking for advice on how to diagnose this properly before trying to modify the SteamOS installation script.

Any suggestions or similar experiences would be greatly appreciated.

Youtube is laggy when in gamemode but when im on fullscreen watching videos is fine

I want to make a poll to check how many people use an eGPU in SteamOS. Also, to share anything useful. Like me, after reviewing logs and troubleshooting I found these very useful for my AMD RX 7600M XT connected through USB4:

- Changing to preview channel to change to SteamOS 3.9 and kernel 7.2.

-Use ewagner12's all-ways-egpu script.

- Using these kernel parameters:

thunderbolt.host_reset=0

pcie_port_pm=off

amdgpu.pcie_gen_cap=0x40000

amdgpu.cwsr_enable=0

It works perfectly now!

Hope you can answer the poll and share anything useful.

Hey! I’m currently using 9070xt, but I do really miss the 4xMFG with my old gpu 5080.. and I wonder if it is working stable om steamos game mode yet?? I have heard back and forth somewhere that you can use it on bazzite and it is working but losing abit performance.. how is it now and how is it working with steamos? Any performance issues? Any buggs? Micro stutters?
I would be very happy if anyone has or had experience trying it

Hi. Is any of you successfully installed dual boot windows on drive which already contains steamos ? I’m not fancy wiping it off if there’s a way to avoid that

Also I had an idea to make 3rd partition for steam games to share between windows n steamos but still unsure if Its worth a hassle and even possible. Thanks

I'm torn between the two. I want Windows, but people say Steam is better.

I'm looking for a more (free) (and convenient) system. For example, if I want to download a file from the internet, I'm afraid it will be limited to Windows because it's more commonly used.

However, it will be difficult to find a file specifically for the SteamOS system.

I've heard that SteamOS is better, but I'm wondering which one is easier to use and more versatile when it comes to editing and finding other options.