# \[RESOLVED\] White Screen & Flicker w/ Proton Experimental

**URL:** <https://community.frame.work/t/resolved-white-screen-flicker-w-proton-experimental/46791>\
**Category:** Linux\
**Created:** [March 10, 2024, 10:41pm UTC](https://community.frame.work/t/resolved-white-screen-flicker-w-proton-experimental/46791 "2024-03-10T22:41:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tyler\_Duzan](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/tyler_duzan/32/17965_2.png) [@Tyler\_Duzan](https://community.frame.work/u/Tyler_Duzan)\
**Post date:** [March 10, 2024, 10:41pm UTC](https://community.frame.work/t/resolved-white-screen-flicker-w-proton-experimental/46791/1 "2024-03-10T22:41:04Z")

</div>

I am having some odd behavior w/ my Framework 13 AMD. This is repeatable by launching Last Epoch from Steam using Proton Experimental. I am running Arch Linux and I am fully up to date, using KDE/Plasma 6 on Wayland.

Here’s what I get in dmesg when this happens:

```auto
[259.011521] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2bc44000 flags=0x0000]
[259.011535] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2bc45000 flags=0x0000]
[259.011550] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2bc46000 flags=0x0000]
[259.011564] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2bc47000 flags=0x0000]
[259.011579] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2bc00000 flags=0x0000]
[259.011593] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2bc4c000 flags=0x0000]
[264.014052] amd_iommu_report_page_fault: 20758 callbacks suppressed
[264.014060] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2be40000 flags=0x0000]
[264.014081] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2be41000 flags=0x0000]
[264.014097] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2be42000 flags=0x0000]
[264.014112] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2be43000 flags=0x0000]
[264.014127] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2be44000 flags=0x0000]
[264.014141] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2be45000 flags=0x0000]
[264.014156] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2be46000 flags=0x0000]
[264.014171] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2be47000 flags=0x0000]
[264.014180] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2be48000 flags=0x0000]
[264.014187] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2be54000 flags=0x0000]
[269.016838] amd_iommu_report_page_fault: 19973 callbacks suppressed
[269.016846] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2bbc0000 flags=0x0000]
[269.016860] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2bbc1000 flags=0x0000]
[269.016871] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2bbc2000 flags=0x0000]
[269.016881] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2bbc3000 flags=0x0000]
[269.016890] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2bbc4000 flags=0x0000]
[269.016900] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2bbc5000 flags=0x0000]
[269.016910] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2bbc6000 flags=0x0000]
[269.016920] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2bbc7000 flags=0x0000]
[269.016930] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2bbc8000 flags=0x0000]
[269.016939] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2bbd4000 flags=0x0000]
[274.041074] amd_iommu_report_page_fault: 39750 callbacks suppressed
[274.041083] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2c430000 flags=0x0000]
[274.041109] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2c431000 flags=0x0000]
[274.041125] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2c432000 flags=0x0000]
[274.041140] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2c433000 flags=0x0000]
[274.041155] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2c434000 flags=0x0000]
[274.041170] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2c435000 flags=0x0000]
[274.041184] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2c436000 flags=0x0000]
[274.041199] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2c437000 flags=0x0000]
[274.041213] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2c450000 flags=0x0000]
[274.041228] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2c43c000 flags=0x0000]
[279.043505] amd_iommu_report_page_fault: 22773 callbacks suppressed
[279.043508] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2c2c0000 flags=0x0000]
[279.043515] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2c2c1000 flags=0x0000]
[279.043519] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2c2c2000 flags=0x0000]
[279.043523] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2c2c3000 flags=0x0000]
[279.043527] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2c2c4000 flags=0x0000]
[279.043531] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2c2c5000 flags=0x0000]
[279.043535] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2c2c6000 flags=0x0000]
[279.043539] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2c2c7000 flags=0x0000]
[279.043543] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2c2c8000 flags=0x0000]
[279.043547] amdgpu 0000:c1:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xfff2c2d4000 flags=0x0000]

```

Based on this, I think it’s an amdgpu related issue in the kernel. I am on 6.7.9 which is the latest release available currently for Arch.

```auto
Linux fw13amd 6.7.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 08 Mar 2024 01:59:01 +0000 x86_64 GNU/Linux

```

I’m curious if anyone else has seen similar behavior, if there’s some kernel/driver tuning that might resolve this?

---

<div class="post-metadata">

**Author:** ![Tyler\_Duzan](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/tyler_duzan/32/17965_2.png) [@Tyler\_Duzan](https://community.frame.work/u/Tyler_Duzan)\
**Post date:** [March 11, 2024, 2:22am UTC](https://community.frame.work/t/resolved-white-screen-flicker-w-proton-experimental/46791/2 "2024-03-11T02:22:39Z")

</div>

I’ve resolved this by adding `amdgpu.sg_display=0` to my kernel configuration and recompiling my unified kernel. After a reboot, I confirmed this issue doesn’t re-occur.

---

<div class="post-metadata">

**Author:** ![Matt\_Hartley](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/matt_hartley/32/13623_2.png) [@Matt\_Hartley](https://community.frame.work/u/Matt_Hartley)\
**Post date:** [March 11, 2024, 6:58pm UTC](https://community.frame.work/t/resolved-white-screen-flicker-w-proton-experimental/46791/3 "2024-03-11T18:58:00Z")

</div>

> [@Tyler\_Duzan](#):
>
> I’ve resolved this by adding `amdgpu.sg_display=0` to my kernel configuration and recompiling my unified kernel. After a reboot, I confirmed this issue doesn’t re-occur.

Glad to hear amdgpu.sg\_display=0 resolved this for you. We also [point folks towards this](https://knowledgebase.frame.work/en_us/allocate-additional-ram-to-igpu-framework-laptop-13-amd-ryzen-7040-series-BkpPUPQa) as well should it crop up again.

---

<div class="post-metadata">

**Author:** ![ralp](https://avatars.discourse-cdn.com/v4/letter/r/74df32/32.png) [@ralp](https://community.frame.work/u/ralp)\
**Post date:** [March 17, 2024, 7:03am UTC](https://community.frame.work/t/resolved-white-screen-flicker-w-proton-experimental/46791/4 "2024-03-17T07:03:31Z")

</div>

Just as an FYI, I also experience this issue when doing modest tasks like watching a youtube video on fullscreen. I also have seen these messages come up after suspend and the laptop not coming up (not sure if this is the culprit) and I wonder if my previous GPU problem also arose from this: [Be aware with Framework 13, AMD and Fedora/Linux - #2 by mikeymop](http://community.frame.work/t/be-aware-with-framework-13-amd-and-fedora-linux/46746/2)

I will try to assign more RAM.
