From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 106871] Screen with blank cursor (raven ridge on MSI B350) Date: Sat, 09 Jun 2018 19:09:46 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0379116270==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 6989B6E1A1 for ; Sat, 9 Jun 2018 19:09:47 +0000 (UTC) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0379116270== Content-Type: multipart/alternative; boundary="15285713870.c8f4bF.17572" Content-Transfer-Encoding: 7bit --15285713870.c8f4bF.17572 Date: Sat, 9 Jun 2018 19:09:47 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D106871 Bug ID: 106871 Summary: Screen with blank cursor (raven ridge on MSI B350) Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: keverik@gmail.com Created attachment 140110 --> https://bugs.freedesktop.org/attachment.cgi?id=3D140110&action=3Dedit 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=20 * dmesg=20 * /var/log/Xorg.0.log=20 * 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! --=20 You are receiving this mail because: You are the assignee for the bug.= --15285713870.c8f4bF.17572 Date: Sat, 9 Jun 2018 19:09:47 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated
Bug ID 106871
Summary Screen with blank cursor (raven ridge on MSI B350)
Product DRI
Version unspecified
Hardware x86-64 (AMD64)
OS Linux (All)
Status NEW
Severity normal
Priority medium
Component DRM/AMDgpu
Assignee dri-devel@lists.freedesktop.org
Reporter keverik@gmail.com 

Created attachmen=
t 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=20
* dmesg=20
* /var/log/Xorg.0.log=20
* lsmod | grep amdgpu after boot.

I boot with kernel 4.16, to get a working VESA driver I use the "nomod=
eset"
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!

You are receiving this mail because:
  • You are the assignee for the bug.
= --15285713870.c8f4bF.17572-- --===============0379116270== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0379116270==--