Date: Mon, 12 Apr 2021 10:28:17 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: maintainer-feedback requested: [Bug 255000] graphics/drm-fbsd12.0-kmod: fails to display anything on 12.0 Message-ID: <bug-255000-7141-aJt8pXQpL9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255000-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-255000-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
Bugzilla Automation <bugzilla@FreeBSD.org> has asked freebsd-x11 (Nobody) <x11@FreeBSD.org> for maintainer-feedback: Bug 255000: graphics/drm-fbsd12.0-kmod: fails to display anything on 12.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255000 --- Description --- After I updated the drm-kmod stuff from source Xorg nolonger starts properl= y. Previously it worked just fine. Now my flat screen only tells me =E2=80=9Do= ut of range=E2=80=9D on a little blue box on otherwise completely black screen. I assume this might be related to the fact that the package message says =E2=80=9Damdgpu and radeonkms are known to fail with EFI boot.=E2=80=9D The previous drn versions had no such problems. So, this is plain madness. What is the point in updating the package in the ports tree, if it does not operate at least as well as the preceeding versions? For the last 10 years it has been quite common for tower case systems to bo= ot using EFI + GPT.=20 Publishing a kms version which suddenly no longer supports Radeon cards on systems using EFI boot is bound to hurt quite a lot of people. Many such systems ha= ve been installed first time years ago assuming they can safely use EFI.=20 Since the drm stuff has previously worked on system using EFI it probably should not be impossible now either.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255000-7141-aJt8pXQpL9>