Bug 207581
| Summary: | [amdgpu] Framebuffer no image CARRIZO and STONEY | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Jan Burgmeier (Jan.Burgmeier) |
| Component: | Video(DRI - non Intel) | Assignee: | drivers_video-dri |
| Status: | NEW --- | ||
| Severity: | normal | CC: | alexdeucher |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 5.4.27 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
Path for 5.4.27 to fix framebuffer
lspci from lenovo 14w lspci from IGEL UD7 git bisect log possible fix possible fix |
||
Created attachment 288909 [details]
lspci from lenovo 14w
Created attachment 288911 [details]
lspci from IGEL UD7
Created attachment 288913 [details]
git bisect log
Created attachment 288915 [details]
possible fix
Reverting will break all systems with limited vram and large displays. Does this patch fix the issue?
Created attachment 288919 [details]
possible fix
This might be a better option.
|
Created attachment 288907 [details] Path for 5.4.27 to fix framebuffer Hi, we have some ancient software which uses DirectFB to draw to the framebuffer during installation. After upgrading from kernel 4.14.99 to 5.4.27 the framebuffer stall the GPU and only a black image was shown. This could be reprocuded on an Igel UD 7 (CARRIZO) and a Lenovo 14w (STONEY) lspci -vv is attached from both devices. We did some more investigation to find the breaking change please see attached git bisect log: 6c8d74caa2fa33908ecd07fb1cf1b7bc629b367a is the first bad commit After finding the bad commit we reverted the changes on the 5.4.27 and framebuffer started working again. Patch for reverting is also attached. Kind regards, Jan Burgmeier