| Summary: | X fails to start with Raven Ridge APU and 1440p monitor on DVI | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Öyvind Saether <oyvinds> | ||||||
| Component: | Driver/AMDgpu | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||||
| Status: | RESOLVED WONTFIX | QA Contact: | Xorg Project Team <xorg-team> | ||||||
| Severity: | normal | ||||||||
| Priority: | medium | ||||||||
| Version: | unspecified | ||||||||
| Hardware: | x86-64 (AMD64) | ||||||||
| OS: | Linux (All) | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
Created attachment 138949 [details]
xorg log of xorg failure to start
It appears this is not a bug but a new motherboard with outdated ancient garbage single link DVI made for resolution-lets with 1080p monitors. https://www.asus.com/us/Motherboards/TUF-B350M-PLUS-GAMING/specifications/ - Supports HDMI 1.4b with max. resolution 4096 x 2160 @ 24 Hz / 2560 x 1600 @ 60 Hz - Supports DVI-D with max. resolution 1920 x 1200 @ 60 Hz - Supports RGB with max. resolution 1920 x 1200 @ 60 Hz Maximum shared memory of 2048 MB (for iGPU exclusively) put simply, the HDMI port is the only barely usable port on this motherboard. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 138948 [details] kernel dmesg with lots of drm / amdgpu error Xorg will not start, boot log stops at lightdm starting and it does not start with a 1440p monitor connected via DVI. Ryzen 2400G APU: 06:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c6) dmesg shows a red line saying: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 1us * 100 tries - tgn10_lock line:566 and a ton of other errors, attached. xorg error log ends with [ 128.160] (EE) modeset(0): failed to set mode: Invalid argument Kernel is 4.15.17. Mesa version is 17.3.6. A workaround for this error is to use a HDMI cable. That does work. I can provide more information on this total scandal bug if someone tells me what to provide and how.