Date: Wed, 29 Mar 2023 00:25:05 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: maintainer-feedback requested: [Bug 270509] x11-servers/xorg-server: After update 21.1.6,1 -> 21.1.7,1, vesa fails Message-ID: <bug-270509-7141-GdUuIIfHtN@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-270509-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-270509-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 270509: x11-servers/xorg-server: After update 21.1.6,1 -> 21.1.7,1, vesa fails https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D270509 --- Description --- After today's update, vesa mode is no longer able to detect my graphics car= d: [ 31.110] (WW) Falling back to old probe method for scfb [ 31.110] scfb trace: probe start [ 31.111] scfb trace: probe done [ 31.111] vesa: Ignoring device with a bound kernel driver [ 31.111] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [ 31.111] (EE) Screen 0 deleted because of no matching config section. [ 31.111] (II) UnloadModule: "modesetting" [ 31.111] (EE) Screen 0 deleted because of no matching config section. [ 31.111] (II) UnloadModule: "vesa" The "device with a bound kernel driver" message rings a bell. Didn't somet= hing like this happen a few years ago? Anyway, nothing else changed today other than the xorg-server update, so I can't account for why this would happen.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-270509-7141-GdUuIIfHtN>