Created attachment 141298 [details] logs
This report is missing a description of the problem in prose.
When I boot ubuntu 18.10 with kernel 4.18rc1-4.18.6 or kernel 4.19rc1 , the result is black screen.
Does amdgpu.dc=0 on the kernel command line avoid the black screen? Does the screen go black when the amdgpu driver is loaded, or only when the login screen is supposed to start?
Created attachment 141335 [details] attachment-1742-0.html I tried to add amdgpu.dc=0 on the kernel command line, but this does not avoid the back screen. The screen go black when the amdgpu driver is loaded because I can catch to see nothing. I see bootloader only, I choose the kernel version for boot and then back screen. I don't know what to say but yesterday after I updated/upgraded all the packages , the screen go back if I boot also kernel 4.17.* I'll try to reinstall my desktop and I'll be back with my new details. I'm afraid I have an issue at my monitor (It's a TV). On Tuesday, August 28, 2018, 10:47:31 AM GMT+3, <bugzilla-daemon@freedesktop.org> wrote: Michel Dänzer changed bug 107698 | What | Removed | Added | | CC | | harry.wentland@amd.com, sunpeng.li@amd.com | Comment # 4 on bug 107698 from Michel Dänzer Does amdgpu.dc=0 on the kernel command line avoid the black screen? Does the screen go black when the amdgpu driver is loaded, or only when the login screen is supposed to start? You are receiving this mail because: - You are on the CC list for the bug. - You reported the bug.
Created attachment 141606 [details] attachment-25512-0.html I reinstalled my desktop but I have the same results. I triedamdgpu.dc=0 on the kernel command line but no results, I have black screen. It's working with kernel 4.17.* but not working with kernel 4.18.* or 4.19.* Wich new details you need for solving this issue ? Scuse me for delay but I had a two weeks holliday. I have installed in my desktop Ubuntu 18.10. Maybe it's usefull, you may see bellow: dpkg --list | grep mesa ii libegl-mesa0:amd64 18.1.5-1ubuntu1 amd64 free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:amd64 18.1.5-1ubuntu1 amd64 transitional dummy package ii libgl1-mesa-dri:amd64 18.1.5-1ubuntu1 amd64 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 18.1.5-1ubuntu1 amd64 transitional dummy package ii libglapi-mesa:amd64 18.1.5-1ubuntu1 amd64 free implementation of the GL API -- shared library ii libglu1-mesa:amd64 9.0.0-2.1build1 amd64 Mesa OpenGL utility library (GLU) ii libglx-mesa0:amd64 18.1.5-1ubuntu1 amd64 free implementation of the OpenGL API -- GLX vendor library ii mesa-utils 8.4.0-1 amd64 Miscellaneous Mesa GL utilities ii mesa-va-drivers:amd64 18.1.5-1ubuntu1 amd64 Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 18.1.5-1ubuntu1 amd64 Mesa VDPAU video acceleration drivers On Wednesday, August 29, 2018, 10:22:40 AM GMT+3, Felix Ezaru <efelixro@yahoo.com> wrote: I tried to add amdgpu.dc=0 on the kernel command line, but this does not avoid the back screen. The screen go black when the amdgpu driver is loaded because I can catch to see nothing. I see bootloader only, I choose the kernel version for boot and then back screen. I don't know what to say but yesterday after I updated/upgraded all the packages , the screen go back if I boot also kernel 4.17.* I'll try to reinstall my desktop and I'll be back with my new details. I'm afraid I have an issue at my monitor (It's a TV). On Tuesday, August 28, 2018, 10:47:31 AM GMT+3, <bugzilla-daemon@freedesktop.org> wrote: Michel Dänzer changed bug 107698 | What | Removed | Added | | CC | | harry.wentland@amd.com, sunpeng.li@amd.com | Comment # 4 on bug 107698 from Michel Dänzer Does amdgpu.dc=0 on the kernel command line avoid the black screen? Does the screen go black when the amdgpu driver is loaded, or only when the login screen is supposed to start? You are receiving this mail because: - You are on the CC list for the bug. - You reported the bug.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/884.
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.