Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #93087
| From | Dianne Skoll <dianne@skoll.ca> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.kernel, linux.debian.kernel |
| Subject | Bug#1139950: [resend] [regression] amdgpu carrizo: no display signal after modeset |
| Date | 2026-06-22 21:50 +0200 |
| Message-ID | <N8SOB-4F9-5@gated-at.bofh.it> (permalink) |
| References | (3 earlier) <N8SOB-4F9-7@gated-at.bofh.it> <N8SOB-4F9-9@gated-at.bofh.it> <N8SOB-4F9-11@gated-at.bofh.it> <N6YY9-dxko-5@gated-at.bofh.it> <N8SOB-4F9-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 3 groups.
On Mon, 22 Jun 2026 20:46:44 +0300
Jaak Ristioja <jaak@ristioja.ee> wrote:
> Reverting commit fee50077656 ("drm/amd/display: Bump the HDMI clock to
> 340MHz") on top of v7.1.1 appears to resolve the issue, as I am now able
> to get a picture.
Unfortunately, reverting that commit will *break* it for me with my Dasung
E-Ink monitor. :(
If it's not possible to detect what the maximum HDMI clock should be, perhaps
a module parameter specifying the HDMI version could be implemented? Or
a parameter to specify the maximum HDMI clock directly?
Regards,
Dianne.
Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#1139950: [regression] amdgpu carrizo: no display signal after modeset Salvatore Bonaccorso <carnil@debian.org> - 2026-06-20 22:20 +0200
Bug#1139950: [resend] [regression] amdgpu carrizo: no display signal after modeset Salvatore Bonaccorso <carnil@debian.org> - 2026-06-21 00:00 +0200
Bug#1139950: [resend] [regression] amdgpu carrizo: no display signal after modeset Dianne Skoll <dianne@skoll.ca> - 2026-06-22 21:50 +0200
Bug#1139950: [resend] [regression] amdgpu carrizo: no display signal after modeset Thorsten Leemhuis <regressions@leemhuis.info> - 2026-07-13 09:30 +0200
csiph-web