From owner-freebsd-x11@freebsd.org Mon Apr 12 10:28:17 2021 Return-Path: Delivered-To: freebsd-x11@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7FBB55CA37D for ; Mon, 12 Apr 2021 10:28:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4FJlLn329Wz3pZl for ; Mon, 12 Apr 2021 10:28:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 665035CA379; Mon, 12 Apr 2021 10:28:17 +0000 (UTC) Delivered-To: x11@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 661955CA7B2 for ; Mon, 12 Apr 2021 10:28:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FJlLn2NRRz3pXk for ; Mon, 12 Apr 2021 10:28:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 44E8015D10 for ; Mon, 12 Apr 2021 10:28:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 13CASHUq069073 for ; Mon, 12 Apr 2021 10:28:17 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 13CASH4g069072 for x11@FreeBSD.org; Mon, 12 Apr 2021 10:28:17 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" 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 Date: Mon, 12 Apr 2021 10:28:17 +0000 X-Bugzilla-Type: request X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: x11@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? Message-ID: In-Reply-To: References: X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Apr 2021 10:28:17 -0000 Bugzilla Automation has asked freebsd-x11 (Nobody) 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.