search

ValveSoftware / SteamOS

SteamOS community tracker
1.54k stars 69 forks source link

Steam Deck crashes and reboots to "verifying installation" screen in games after update to v 3.5.5 or higher. #1257

Closed murphyjohn closed 7 months ago

murphyjohn commented 9 months ago

Your system information

Since updating to SteamOS versions 3.5.5 and higher on Steam Deck, games crash after a few minutes of gameplay and the console reboots with a "verifying installation" screen upon restart. This occurs throughout all games (both steam and non-steam) and there are also noticeable graphical glitches in games while running.

It appears that this issue is somehow related to VRAM usage as when the UMA Frame Buffer Size is changed from 1GB (default) to 4GB the issue seems to be mitigated somewhat. (EDIT: This is no longer the case. Even with the UMA at 4GB, games now crash and the deck reboots, rendering the deck as an expensive brick).

However this means that there is less VRAM available for CPU usage and it means that games are unplayable on SteamOS on the steam deck without changing this setting in the BIOS for those who are effected.

This is a widespread issue that is reported among numerous other users on Steam deck forums and discussions.

Steps for reproducing this issue:

  1. Update to version 3.5.5 or 3.5.7
  2. Play a 3D game, e.g. Spider-Man: Miles Morales
  3. Game has graphical glitches and console crashes within 2 minutes of play.
  4. Steam Deck reboots itself and verifies installation each time.
Statesidemonk commented 8 months ago

Disregard the post about disabling some of the display settings. The problem returned after I powered back on from shutdown.

arisqotle commented 8 months ago

This issue has been mentioned by many people in the steam community. My SD is 512 GB, bought two mouths ago. The crash problem has often occurred in version 3.4.11. It also occurs after updating to version 3.5.5. The frequency of occurrence is very random. Sometimes when the battery power is lower than 40%, crashes occur easily. After trying battery storage mode, freezing issues appear to have been alleviated. Tried reinstalling the system, but it didn't solve the problem. Many people think it is a problem with the SD itself, and many people contact customer service RMA, some have solved the problem, and some will still crash after RMA. I think it cannot be ruled out that it is a problem with the SD itself. Different SD have different constitutions. What needs to be determined now is whether anyone has encountered a crash problem in the new oled version of SD.

lutzgooren commented 8 months ago

What needs to be determined now is whether anyone has encountered a crash problem in the new oled version of SD.

I have an 1TB OLED and it's the same for me + sometimes some cool artifacts on screen when switching from Desktop to Game Mode: ojcFdhJ This can be "fixed" by putting the Deck to sleep and wake it up again and it will display the game library just fine afterwards. @lostgoat if you want to take a closer look at my logs: https://steamcommunity.com/profiles/76561198041949835/

murphyjohn commented 8 months ago

  • Do you have an OLED deck or LCD?

  • LCD (256GB)

  • How long have you had your deck?

  • over a year. Since July/August of 2022.

  • When did the problems start happening? (Please answer with a time measurement, e.g. 1 week ago, 3 weeks ago, 6 months ago, etc).

  • 2 weeks ago. (after updating to 3.5.5. Issue persists on 3.5.7.)

AlexNes-SDUser commented 8 months ago

Hi all,

found this topic in the steamcommunity. I have the same Problem with my Deck

Ordered September 2023 64GB Version Upgraded to Sabrent 1tb SSD

I had little problems from the beginnig with Diablo 4 (Battle.net Version) It crashed randomly, but after a few reinstallations I could play it a few days without any Crashes. Then Patch 1.2 comes out and it started crashing again. I then tested SteamOS 3.5 from the preview Channel and it installed a never BIOS version I think.. 3.5 doesn't helped me with Diablo so I did a re-image, formated the SSD and installed a fresh SteamOS 3.4. But I think the BIOS version remains the same.. I then played Grim Dawn and Fallout 4 from time to time and have no freezes. Then the "stable" SteamOS Update 3.5 was installed, on the same Day I brought Batman Arkham Collection on the Steam Sale and I couldn't play any of the games.. Grim Dawn and Fallout starts crashing and now my Deck isn't really usable anymore.

I have an open ticket at support at the momtan, but deactivating Fan Control, or battery mode doesn't help.. It's getting better, but I couldn't play longer than ~1 hour without freeze - crash - restarting

https://steamcommunity.com/profiles/76561198111060402/

Menahen commented 8 months ago

you

exactly, for me it only worked when I did both things in sequence, the factory reset and the gpu reset, I don't remember now if it was a driver or cache reset, but when I just did the factory reset it didn't work, I continue crashing no matter what I did, after the factory reset I still ended up updating to 3.5.7 and the problem continued. So I did a new factory reset and then the gpu reset, using the volume down + ... and holding the power button, when I felt the second vibration I removed my finger from the power button, but it continues according to the volume down and the..., until the steam logo came up, at least that's how I did it, and now everything is normal, I believe that maybe in my case it was something in the 3.5 update regarding the drivers, in 3.4.11 it was normal. But even after downgrading to 3.4.11 again, after a while I started having crashes again, but they took 1-2 hours to occur, after 3.5.7 they occurred every 5 minutes, I had already thought that my deck was already , because I live in a country that doesn't have support, but I luckily did this procedure and it worked.

rvreqTheSheepo commented 8 months ago

Same problem for me when trying to play Fall Guys, it crashes in 5-10 minutes after launching, no matter if it's low or ultra settings.

Latest updates, LCD model with original 64GB drive, never tinkered, running only emulators from the Discover store and some Decky plugins. Game running from SanDisk SD card.

Steam client version: 1701289036 SteamOS version: 3.6 (Main, because someone recommended to try it instead, same result on Stable) Opted into Steam client beta?: No Opted into SteamOS beta?: No Have you checked for updates in Settings > System?: Yes

Sent report to Steam support from profile https://steamcommunity.com/id/rvreqTheSheepo (no Steam ticket made yet)

Statesidemonk commented 8 months ago

Ok. I tried yet another clean reinstall of SteamOS.

I used a brand new Samsung USB Type-C flash drive. I installed it in Linux Mint using Balena Etcher. It did not solve the crashing.

Doing the BIOS reset has also proven to have been just a coincidence.

ScottCarammell commented 8 months ago

Yeeep, this has been an issue for me for probably two weeks or more and has rendered the vast majority of the games in my library completely unplayable. tried contacting steam support, they took way too long to respond every time and at the end just told me to send my deck in with a minimum $120 repair fee - which is completely ridiculous for an issue THEY caused.

If anyone has a suggestion for a specific game+proton combination that causes this to problem to reproduce semi consistently and quickly it would help speed up testing.

I have more than a few examples. I've tried several Proton versions with most of these games, so I'll just be naming my most recent version. Just know I've mostly tested with 8.0, 7.0, Experimental, Hotfix and sometimes Glorious Eggroll.

Some of these crash more often than others, but I can't find any consistency with what does and doesn't crash often, regardless of game engine, Proton version, Linux native-ness or compatibility rating. Hopefully this helps test.

AleSank commented 8 months ago

Guys, one big question: which mesa drivers were present in 3.4.X? also because I'm reading on the internet that 23.1.3 (those of 3.5.7) have given many problems to several Linux users... ah, and above all that version is from 2023-06-22...

LEVIMITSU commented 8 months ago

Has anyone in here had a definitive answer from steam yet as to what the problem is? they are replying to me very slowly!

@lostgoat do you work for valve / steam? thank you for your work in this btw!

AlexNes-SDUser commented 8 months ago

@LEVIMITSU Not really.. "Please try this" "please try that" .. todays Question was : "Have tried to Update?" yes.. I wrote that I am on the stable 3.5.7 and have tried 3.5.8 ... but at least I get an reaction

I send them the systemlog in the topic now.. I hope that this will help

LEVIMITSU commented 8 months ago

Guys, one big question: which mesa drivers were present in 3.4.X? also because I'm reading on the internet that 23.1.3 (those of 3.5.7) have given many problems to several Linux users... ah, and above all that version is from 2023-06-22...

I've just had an update come through for mesa & mesa extra version 23.2.1 wonder if this is a fix of some kind??

LEVIMITSU commented 8 months ago

@LEVIMITSU Not really.. "Please try this" "please try that" .. todays Question was : "Have tried to Update?" yes.. I wrote that I am on the stable 3.5.7 and have tried 3.5.8 ... but at least I get an reaction

I send them the systemlog in the topic now.. I hope that this will help

fingers crossed

AleSank commented 8 months ago

Guys, one big question: which mesa drivers were present in 3.4.X? also because I'm reading on the internet that 23.1.3 (those of 3.5.7) have given many problems to several Linux users... ah, and above all that version is from 2023-06-22...

I've just had an update come through for mesa & mesa extra version 23.2.1 wonder if this is a fix of some kind??

Mmm maybe not, is different, because for steam os in handled by the SO ( in this case 3.5.7 for example), for desktop mode is different

redqrogh commented 8 months ago

I was having similar issue where on steamOS 3.5.7:

  1. Game is ran [e.g., Kingdom's of Amalur: Re-Reckoning (severe), Heaven]
  2. Game plays fine for a bit [1min-30min]
  3. Game freeze, then the deck freezes.
  4. Soft reboot occurs next with the "Verifying installation" following shortly

In Kingdom's of Amalur, I was able to recreate the crash in a certain save file by going to certain areas in the map. Although depending of the order of operations crash could be avoid. Frame time would start spiking before crash occurred. All my games have manual TDP/FPS/GPU Clock limit set to 5W/42FPS/600Mhz, so I do not think this was 200/1040 issue (though I was not observing frequencies)

I tried many version of Proton (normal, GE, experimental) and the best I could do was have the game crash instead of soft reboot but even that was not repeatable.

I got fed up with the frequent and unpredictable crashes, I decided to reinstall steamOS from scratch and attempt to downgrade to 3.4.x where issues were not as noticeable. Unfortunately, it seems there no way for Deck users to manually select the version of the OS they want to downgrade to directly (3.5.5 -> 3.5.7 upgrade removed the older 3.4.x in bios bootup options). My Deck (purchased in Sept sale this year) was 64GB which I had upgraded to 1TB Corsair MP600 mini. I hadn't reformatted my 64GB drive, so I cloned this drive to SD card and cloned it back again to Corsair drive inside SD. Process thankfully worked fine after expanding the main partition to account for new 1TB size.

Now I do have issues in 3.4.10 but they are not as noticeable or cause soft reboot. The game crashes partly or at least the rendering stop but the game is still running. Like I can access in-game menu (noticeable via sound) and even save my game via SD back button. Just that game is stuck with gfx not updating. I can quit the game from steamOS menu and come back into the game.

Statesidemonk commented 8 months ago

3.5.9 from the preview build channel sadly has not fixed this issue. Games are still crashing. It did fix the 200/1040 and frame rate capping bugs, so progress is being made.

I submitted another system crash report directly after the latest crash. Hopefully this can further assist.

https://steamcommunity.com/profiles/76561198076474768/

*edit

I just wanted to add that while preview build 3.5.9 is not perfect, it’s still a great step in the right direction, and I want to thank the devs on here that worked (and are still working) on this issue.

Igor-devc commented 8 months ago

Good afternoon, everyone. Has anyone tried installing windows 11 instead of steam os? The problem is solved with the launch of games in windows or the problem remains, try someone and please give an answer.

ScottCarammell commented 8 months ago

Good afternoon, everyone. Has anyone tried installing windows 11 instead of steam os? The problem is solved with the launch of games in windows or the problem remains, try someone and please give an answer.

I imagine that'd work, though having to go through partitioning drives and installing Windows to play games that are supposed to work out-of-the-box with likely worse performance is definitely more of a nuclear option than a temporary workaround.

AleSank commented 8 months ago

Good afternoon, everyone. Has anyone tried installing windows 11 instead of steam os? The problem is solved with the launch of games in windows or the problem remains, try someone and please give an answer.

For me no, because the drivers are differents.

Igor-devc commented 8 months ago

I want to understand if this is a software problem or a hardware one, if you install windows 11 and there is no such problem, the game will work well and the console will not turn off, then the problem is in steam os. If it is exactly the same on Windows, then the problem is in hardware, a hardware problem. By installing WIndows, you can determine where the problem really is.

AleSank commented 8 months ago

Is software, at 100%! I've been played until latest 3.4.x release, so isn't possibile an hardware problem 😎

Igor-devc commented 8 months ago

image

Such a window pops up on the steam deck 5-10 minutes after the game and the console restarts, I want to understand is this a software problem of steam os or a problem in the hardware?

Igor-devc commented 8 months ago

device removed reason dxgi_error_device_reset: badly formed command, code sent an invalid draw command. Please verify that the latest graphics device are installed

This is the inscription that comes out after 5-10 minutes during the game

murphyjohn commented 8 months ago

device removed reason dxgi_error_device_reset: badly formed command, code sent an invalid draw command. Please verify that the latest graphics device are installed

This is the inscription that comes out after 5-10 minutes during the game

This is a different issue. If it is occurring with multiple games and googling the error does not help you, I suggest you contact Steam support.

If you believe it is an issue with SteamOS I suggest you create another issue, since it is distinct and separate from this one.

Igor-devc commented 8 months ago

I can't figure out if this is a steam os software problem or a hardware problem. I haven't seen a solution to this problem anywhere.

DeadlyDownie commented 8 months ago

I can't figure out if this is a steam os software problem or a hardware problem. I haven't seen a solution to this problem anywhere.

I can confirm this is a Steam OS software issue.

I have been watching this feed for over a week now as I have been having the same problems but didn’t have an account sorted to comment.

I have had a 512GB LCD for about a year and a half now and I have only encountered this issue recently.

At first I thought it was just Lethal Company being new, but then I realised it was happening on my Fallout 3 play through and Starfield. That’s when I knew it must be something to do with a recent software update that must have slipped through the cracks of preview and beta testing.

I previously had the preview mode for 3.5 to get the extra juice to play Starfield when it first came out, then switched back to stable when it was coming out with the OLED model.

I haven’t raised a ticket yet as I thought Valve would be on top of this by now and aware of the issue but it is starting to seem like it’s a sporadic subset of users it has affected.

This bug literally renders the whole device useless, which regardless of how small the number of people affected by it is, it should not be it ignored by Valve.

Paulthe1 commented 8 months ago

Another new Deck user with gaming issues.

Unboxed my steam deck this week, it started updating immediately so I have never played a game with the older firmware.

Most game time until now is 5 minutes before it restarts with verifying. But most attempts crash within seconds of being in-game. Game menu's are working fine. I was assuming Valve was on top of this so was just waiting for a few days for the new firmware to come out.

Only had 1 game crash with an actual error message after trying to go to the beta channel (if that helps) Assertion Failed :

File /src-wine/dlls/winepulse.drv/mmdevdrv.c" Line 226 Expression "!status"

AlexNes-SDUser commented 8 months ago

Hi all,

Valve will send me RMA instructions in the next hours. So my Deck will go on a trip back to them. It will be nice for me if I get a functional device back ... but it will not help to clarify whats wrong.. And when most new produced decks have this issue, it is exciting what I get back...

AlexNes-SDUser commented 8 months ago

I don't get it... I have played Arkham City and Hogwarts Legacy now for a while.. With no crashes... Normally Arkham City crashed every time I entered a door in the game.. now it is working.. I try to provoking a crash for a new system report without "success".

What have I done the last days...?

  1. I was on preview 3.5.8 and switched back to the stable channel and 3.5.7 was installed again

  2. For the latest Battle.net error I have changed Proton Experimental to Bleeding edge (To use Proton Bleeding Edge, you need to right-click on Proton Experimental and select Properties -> Betas -> select the bleeding-edge option) But Arkham or Hogwarts are on default compatibility.. Is the Deck using Proton Experimental as default? Don't know..

  3. I have reset the BIOS -> hold down both the volume - button and the "..." button, then press the power button once. Then you can release all the buttons. You will hear a chime and then the white LED light will begin to blink (it may take 5 or more seconds before the blinking begins), which confirms this process is working. And I have reset it in the bios itself because I don't know if the stepps abpove worked, I get no chime..

After my last steps I have only tested Arkham City.. So maybe my last crash was another error only for the game.. At the moment (!!) I can play everything I tested without crash. I will play more in the evening and let you know. Maybe one of you can test my steps so far

LEVIMITSU commented 8 months ago

Replying to https://github.com/ValveSoftware/SteamOS/issues/1257#issuecomment-1845199261

did you update the mesa drivers in desktop mode?

or i'm wondering if steam / valve have stealth a patch, my games are crashing less but i've made no changes, also giving it a proper run tonight will report back

also steam and valve are not acknowledging the problem they keep sending me computer / automated trouble shooting response...

AlexNes-SDUser commented 8 months ago

No I didn't Update the drivers.. But every other Update that was shown.. I don't want to update Mesa at the moment if I'm honest.. I will test a bit more first... Never touch a running system... :)

Menahen commented 8 months ago

No I didn't Update the drivers.. But every other Update that was shown.. I don't want to update Mesa at the moment if I'm honest.. I will test a bit more first... Never touch a running system... :)

You solved the problem in a very similar way to me. In my case I did a factory reset and then a gpu reset, but before that I updated to 3.5.7, so far everything is normal, no crashes, I even disabled the wifi so as not to update anything until they find out what this is. , but in my opinion, I believe there is something to do with a corrupt update, which somehow also influences the bios, this would explain the solution of doing a successful update followed by a bios reset, solving some of these cases, including this DXGI_ERROR problem , and soon after it evolved into the issue problem (freezes, blinks twice and goes to the checking screen)

lostgoat commented 8 months ago

Hey Everyone,

Please make sure to read all the warnings in this message before proceeding.

We'd like to test if these problems were introduced by a software change in SteamOS 3.5. In order to verify this, we'd like you to downgrade to SteamOS 3.4. After downgrading, run the same games that were having issues and let us know if the problem goes away.

WARNING: DO NOT PROCEED UNLESS YOU HAVE A STEAMOS RECOVERY USB READY

If the OS becomes unbootable after the update, you can hold the '...' button and press the power button to boot into the recovery menu. This will let you boot into the your previous SteamOS install. If this mechanism fails, you'll need a recovery USB to re-install SteamOS on your SteamDeck.

Recovery USB instructions: https://help.steampowered.com/en/faqs/view/1B71-EDF2-EB6D-2BB3

Also please note that old versions of the OS are untested, and you may run into unexpected bugs. These may include performance issues, TDP/performance management features working incorrectly, failure to start the steam client, etc. If you run into any issues please update to a supported version of SteamOS or reflash your system with the recovery USB.

WARNING: DO NOT DOWNGRADE OLED DECK, IT WILL NOT BOOT

SteamOS 3.4 is not compatible with OLED decks. Installing this version of the OS on your OLED deck will result in irrecoverable errors.

Run the following command to re-install 3.4.11:

# Don't run this in an OLED deck
sudo steamos-atomupd-client --update-from-url https://steamdeck-images.steamos.cloud/steamdeck/20231005.1/steamdeck-20231005.1-snapshot.raucb

:warning: WARNING: ONE MORE TIME: DO NOT DOWNGRADE OLED DECK, IT WILL NOT BOOT WITH 3.4 :warning:

If you need instructions on how to run this command, you should probably not downgrade your deck. Please allow someone else to run the tests on instead.

lostgoat commented 8 months ago

One more note: there is an important behaviour difference between 3.4 and 3.5. On 3.4 a game causing a GPU hang will just crash the game. On 3.5 the same GPU hang will also cause gamescope and steam to crash, which will result in the "Verifying Installation" screen to be shown. This is something we need to fix in SteamOS 3.5.

So when you test on SteamOS 3.4 please watch for game crashes instead of "Verifying Installation" crashes.

ScottCarammell commented 8 months ago

I'll try downgrading, but fyi the new Stable release (I think from today?) seems to have mostly fixed the issue. Mostly. I still got crashes on The Witcher 3 and if it's anything like it was before it'll probably slowly get worse and crash more often as time goes on, but at least with BIT.TRIP RERUNNER, Duke Nukem Forever and RE:Revelations I've yet to experience a crash after this release. Regardless, I'll give it a try and report back!

Edit: also because I'm sure you saw it and I feel bad now I do wanna apologize for sounding angry in my original post. I'm sure you and your team are doing all that you can to fix the issue. In my defense, I think anyone would be irritable if you were locked off from your games for three weeks for what felt like no reason. Anyway, thanks for the help

ScottCarammell commented 8 months ago

Update: it...still has GPU hangs? For me at least. As you described, it doesn't crash the whole system, just locks it for a few seconds before letting you exit. Still, this definitely didn't happen prior to the aforementioned update.

I've actually had a problem exactly like this early on this year (with the GPU hangs, not with system resets; I think Q1 - early Q2? I can't remember), though that got fixed after a month or so. Maybe they're related? I didn't really look for discussions on that bug at the time, so I can't recall a thread being made about it.

Paulthe1 commented 8 months ago

I can confirm the same 3.4.11 has the same results after the downgrade only without the verify steps after crashing a game (tested 3 random titles, all crash within seconds to max 2 minutes).

This is my new deck, so no previous version experience.

lostgoat commented 8 months ago

@ScottCarammell One more thing to try, lets fully reset the system by:

If that doesn't work, I'd recommend contacting steam support and describing everything you've tried.

ScottCarammell commented 8 months ago

@ScottCarammell One more thing to try, lets fully reset the system by:

  • Power down the deck
  • Hold vol- and '...' buttons
  • Tap the power button (keep holding the other two buttons)
  • You can let go of the buttons once you see the power led blinking
  • The system will take longer than normal to fully boot, let it take its time without powering off.

If that doesn't work, I'd recommend contacting steam support and describing everything you've tried.

Sadly, I've already tried both. BIOS resetting didn't really do anything, and spending $120 minimum for a repair definitely isn't in the cards for me. Sadly checking in on this thread is really the only hope I have for getting this fixed at the moment.

lostgoat commented 8 months ago

@ScottCarammell can you submit a system report after the crash happens and link me your steam account profile?

Paulthe1 commented 8 months ago

@ScottCarammell One more thing to try, lets fully reset the system by:

  • Power down the deck
  • Hold vol- and '...' buttons
  • Tap the power button (keep holding the other two buttons)
  • You can let go of the buttons once you see the power led blinking
  • The system will take longer than normal to fully boot, let it take its time without powering off.

If that doesn't work, I'd recommend contacting steam support and describing everything you've tried.

This worked for me, after the downgrade to 3.4.11 executing these steps made all the difference. Will test some more games tomorrow for an extended period.

rvreqTheSheepo commented 8 months ago

@ScottCarammell can you submit a system report after the crash happens and link me your steam account profile?

I also have same issue, I just downloaded latest 'Main' branch update and now my games crash even faster, just in 30 seconds, leaving a lit black screen and having a autorestart after some time.

The "vol-+ ..." method did nothing for me.

I'm afraid of downgrading, because I don't want to lose things on the Deck, so hopefully the fix comes out anyway. I sent the crash log, profile: http://steamcommunity.com/id/rvreqTheSheepo

emcy849 commented 8 months ago

Like i said in my post, gamescope crashing was literally the first brand new thing i experienced after updating to 3.5.5 stable, from 3.4.11. Directly after updating. Many others in here report this also. I dont see how it can be in doubt that something about the 3.5.5 update has caused this?

The bios update to 119 was deployed at the same time as 3.5.5 i believe. it is possible it has something to do with that too, or instead?

Also, i gave you a method for 100% reliable and instant reproduction of this bug (at least for me), did you see it?

emcy849 commented 8 months ago

Replying to https://github.com/ValveSoftware/SteamOS/issues/1257#issuecomment-1845939496

OK @lostgoat i ran the command, and i now have 3.4.11 on the A partition, and 3.5.10 on the B partition, BIOS is the same 119 between both. A few pictures to confirm my setup:

https://files.catbox.moe/xc7o7x.jpg https://files.catbox.moe/gu8lj7.jpg https://files.catbox.moe/33x3z2.jpg

Result: When booted into 3.4.11, Halo Infinite campaign mode loads and works fine (along with a non steam game which i know is also guaranteed to crash 3.5, Sonic CD Restored. Works fine in 3.4.11)

When booted into 3.5.10, H I Campaign mode fails (as does Sonic CD). Gamescope crashes and steam restarts. I have again uploaded the most recent system report to valve servers related to this.

Conclusion: for me this absolutely without a shadow of a doubt pins the issue down to Gamescope as shipped with the 3.5.x line of steamOS. I have now even eliminated the effect of BIOS 119, since 3.4.11 with BIOS 119 worked.

For now im going to mark active and make default the partition containing 3.4, since that seems like its going to be the only way to actually play the games i want to until this nasty bug is fixed.

emcy849 commented 8 months ago

@emcy849 How did you install 3.4.11? I want to try this on my steam deck too. Thank you for your efforts thus far.

I did what lostgoat instructed in https://github.com/ValveSoftware/SteamOS/issues/1257#issuecomment-1845939496

Read his whole post and the warnings thouroughly and make sure you understand whats youre getting into, and how the steam decks RAUC A and B partition setup works conceptually. Its not hard to do but if you dont actually understand what its doing, you can get lost.

And if you have an OLED deck DO NOT try and install 3.4.11, it has no idea how to run on an OLED deck, it it will just brick it.

Kind of a perverse situation right now where people with new OLED models have no option to use it without running into this bug, but people who bought the original model ages ago do.

HotRunes commented 8 months ago

I've returned my Steam Deck for a refund in the end. I can't see the point in owning a piece of hardware that doesn't do the job (consistently and reliably) that you've paid for it to do. We're closing in on two weeks since this thread was created, and probably three or four weeks since I started experiencing this problem with the Steam Deck, and it's still no closer to being solved and fixed. At the moment, the device/software is way too unreliable for it to prove a good investment.

Igor-devc commented 8 months ago

Всем добрый день. Кто-нибудь пробовал устанавливать Windows 11 вместо steam os? Проблема решается с запуском игр в Windows или проблема остается, попробуйте кого-нибудь и, пожалуйста, дайте ответ.

I imagine that'd work, though having to go through partitioning drives and installing Windows to play games that are supposed to work out-of-the-box with likely worse performance is definitely more of a nuclear option than a temporary workaround.

If everything works on windows 11, you can play games, the console works, no problem, I think this solution is better than having a non-working brick on steam os. which will be covered with dust on the shelf without it being possible to play on it!

Igor-devc commented 8 months ago

On windows 11, all games are free, you don't have to buy, there are no compatibility problems. What doesn't work will launch on steam os. It runs easily on windows 11. All games run. And control is applied to all games via the xbox 360 emulator. I set myself a 512gb ssd drive. I installed windows 11. I played for free without problems in GTA 5. Days Gone. Cyberpunk 2077. death stranding. simcity 5. Factorio. red dead redemption 2. Fifa 2023. Many other games were going great. there was no drop in productivity. It's better on windows than on steam os!

Igor-devc commented 8 months ago

Stick your finger in your anus, you fool.