Bug 106871

Summary: Screen with blank cursor (raven ridge on MSI B350)
Product: DRI Reporter: Erik <keverik>
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED NOTOURBUG QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
xorg loggings with the problem none

Description Erik 2018-06-09 19:09:46 UTC 
Created attachment 140110 [details]
xorg loggings with the problem

After upgrading my debian stable with a (i assumed) a nice cpu with graphics AMD 2200G, it did not work, only in VESA mode.
I upgrade to unstable/sed and now have a non working system with default settings.

For me it is not clear, where the problem is (kernel or amdgpu), but maybe you can help me with steps to get it clear.

This are the warnings and errors:
[     9.874] (WW) AMDGPU(0): No outputs definitely connected, trying again...
[     9.874] (WW) AMDGPU(0): Unable to find connected outputs - setting 1024x768 initial framebuffer
[     9.874] (EE) AMDGPU(0): No modes.
[     9.874] (EE) Screen(s) found, but none have a usable configuration.

I have attached the following info:
* lshw -c video 
* dmesg 
* /var/log/Xorg.0.log 
* lsmod | grep amdgpu after boot.

I boot with kernel 4.16, to get a working VESA driver I use the "nomodeset" flag on the kernel arguments.

What I also don't understand is why the system doesn't fallback on the VESA driver?

Thanks already a lot!
Comment 1 Michel Dänzer 2018-06-11 10:03:15 UTC 
The Debian kernel packages don't enable CONFIG_DRM_AMD_DC_DCN1_0, so the amdgpu driver doesn't have display support for your GPU. Please report this in the Debian bug tracker.
Comment 2 Erik 2018-06-11 19:26:16 UTC 
Thank a lot!, i will forward the bug.

(Still interesting how you can figure this out from my logging.)
Comment 3 Michel Dänzer 2018-06-12 07:31:12 UTC 
(In reply to Erik from comment #2)
> (Still interesting how you can figure this out from my logging.)

In a nutshell: Because the dmesg output you attached doesn't contain the word "Display".

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.