Sean Tilley
Former Diaspora core team member, I work on various fediverse projects, and also spend my time making music and indie adventure games!
- 7 Posts
- 6 Comments
Joined 6 years ago
Cake day: November 29th, 2019
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
2·2 years agoHey, final update here - I managed to get the game working again! I think a patch came through somewhere that broke something - maybe it was ProtonGE, maybe it was Valve patching Proton Experimental, maybe it was Bethesda putting out something weird in a patch. Regardless, I got a tip that you can upgrade your Linux kernel to 6.5.x, and upgrade to the latest Mesa git drivers. The game is now running smoothly again without any issues on Wayland!
Alright, bit of an update: after investigating my hardware, doing a fresh OS install, and trying just about everything that everybody’s suggested to me so far, I have logs. Definitely amdgpu related, but not 100% sure what is going on yet. This was on Wayland, searches for similar error messages suggest a possible driver bug, maybe issues with particular kernel versions? Still investigating.
amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32785, for process Starfield.exe pid 71830 thread vkd3d_queue pid 71960) Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000800131efe000 from client 0x1b (UTCL2) Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00201031 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32785, for process Starfield.exe pid 71830 thread vkd3d_queue pid 71960) Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000800131efe000 from client 0x1b (UTCL2) Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00201031 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32785, for process Starfield.exe pid 71830 thread vkd3d_queue pid 71960) Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000800131efe000 from client 0x1b (UTCL2) Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00201031 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32785, for process Starfield.exe pid 71830 thread vkd3d_queue pid 71960) Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000800131eff000 from client 0x1b (UTCL2) Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32785, for process Starfield.exe pid 71830 thread vkd3d_queue pid 71960) Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000800131eff000 from client 0x1b (UTCL2) Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32785, for process Starfield.exe pid 71830 thread vkd3d_queue pid 71960) Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000800131efe000 from client 0x1b (UTCL2) Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 Sep 24 02:29:50 Asmodeus kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x0 Sep 24 02:30:00 Asmodeus kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered
Yeah, I’ve tried several, of both the GE and Experimental varieties. The problem persists, sadly.
It feels as though the game is suddenly only capable of loading interior spaces, despite the game running great as recently as two days ago.
Unfortunately, I’m not sure as to how to find them, or enable them if they’re not already working. I agree that logs would definitely help here.
Yeah, it’s possible. I’m curious, though, as to why it affected my other saves retroactively? Like, I can run around within TMD / the old Red Devils facility just fine, but the game craps out when I set foot on Mars.
While I think shareholders can be a driving factor, I see it way more often with VC-funded companies. The “2.5x year over year” growth mantra that places like YCombinator stipulate have disastrous effects on small tech companies. Often, these startups have an incentive to keep taking additional funding rounds, which appears to tighten the grip the VC has over them.
Try growing the next Microsoft or Google or Amazon out of that model. I’m not convinced that it’s possible. At least if you bootstrap your own company, you don’t have the same binding obligations…even if it takes way longer to get to a place that’s self-sustaining.