Does anyone know why OW2 may be crashing on Arch? I thought it was just me, but I went to protondb and saw more reports. The only solutions I found from historical crashing non-Arch related was for nVidia users, but I’m on AMD.
Any clue why it may be? And, more importantly, what the solution may be?
Can confirm, my WoW crashing problem is gone since doing so. At least, I changed two settings, not just the one mentioned (see below).
I had updated my BIOS version recently, and the ‘Above 4G Decoding’ and ‘Resizable BAR Support’ was turned off, instead of inheriting the previous BIOS version setting of them being turned on previously.
EDIT: As discussed above, turning on ‘Above 4G Decoding’ and ‘Resizable BAR Support’ settings in my BIOS fixed the problem.
I had updated my BIOS recently, and the ‘Above 4G Decoding’ and ‘Resizable BAR Support’ was turned off, instead of inheriting the previous BIOS version setting of them being turned on.
Does anyone know why OW2 may be crashing on Arch? I thought it was just me, but I went to protondb and saw more reports. The only solutions I found from historical crashing non-Arch related was for nVidia users, but I’m on AMD.
Any clue why it may be? And, more importantly, what the solution may be?
Not sure if its related, but throwing this reply your way, just in case.
WoW has been crashing for me too last couple of days, consistently. Launched via Battle.net launcher.
Its weird, but the only way I can get it to not crash is by letting the first WoW session crash on startup, NOT closing the exception error message dialog or the report the crash to Blizzard dialog, and then start up a second session of WoW. That second session plays fine.
I had played first session WoW normally for a week, then stopped to have lunch one day, and when I came back from lunch and started up WoW again, this crashing crap had just started.
I tried using Bottles (both native and flatpak), Lutris, and Steam. The ‘run twice’ trick is being done on Steam (native not flatpak) using experimental. Using Fedora/KDE spin.
Not sure where to report this ‘bug’ to on the Internet. Any ideas?
i had this same problem, turning on resizable BAR seems to have fixed it.
Can confirm, my WoW crashing problem is gone since doing so. At least, I changed two settings, not just the one mentioned (see below).
I had updated my BIOS version recently, and the ‘Above 4G Decoding’ and ‘Resizable BAR Support’ was turned off, instead of inheriting the previous BIOS version setting of them being turned on previously.
Anti Commercial-AI license (CC BY-NC-SA 4.0)
Can you please explain what you mean by that? ^ ^’
It’s a BIOS thing and it worked! Thank you! :3
It’s probably this recent bug in kernel/mesa. https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/47
You need to downgrade your kernel or wait for the fix…
Confirm that ‘Above 4G Decoding’ and ‘Resizable BAR Support’ is set to on in your BIOS first!
Anti Commercial-AI license (CC BY-NC-SA 4.0)
Thank you for the info!
EDIT: As discussed above, turning on ‘Above 4G Decoding’ and ‘Resizable BAR Support’ settings in my BIOS fixed the problem.
I had updated my BIOS recently, and the ‘Above 4G Decoding’ and ‘Resizable BAR Support’ was turned off, instead of inheriting the previous BIOS version setting of them being turned on.
Not sure if its related, but throwing this reply your way, just in case.
WoW has been crashing for me too last couple of days, consistently. Launched via Battle.net launcher.
Its weird, but the only way I can get it to not crash is by letting the first WoW session crash on startup, NOT closing the exception error message dialog or the report the crash to Blizzard dialog, and then start up a second session of WoW. That second session plays fine.
I had played first session WoW normally for a week, then stopped to have lunch one day, and when I came back from lunch and started up WoW again, this crashing crap had just started.
I tried using Bottles (both native and flatpak), Lutris, and Steam. The ‘run twice’ trick is being done on Steam (native not flatpak) using experimental. Using Fedora/KDE spin.
Not sure where to report this ‘bug’ to on the Internet. Any ideas?
Anti Commercial-AI license (CC BY-NC-SA 4.0)