Date: Wed, 10 Jul 2019 00:19:52 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 239065] devel/libpciaccess-0.14 breaks x11-drivers/xf86-video-vesa-2.4.0_2 Message-ID: <bug-239065-7788-0ConuWmpSA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-239065-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-239065-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239065 Andreas Schwarz <bugs.freebsd.asc@schwarzes.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugs.freebsd.asc@schwarzes. | |net --- Comment #1 from Andreas Schwarz <bugs.freebsd.asc@schwarzes.net> --- Same here. After upgrading my desktop system today, the vesa driver want lo= ad anymore. [ 845.322] vesa: Ignoring device with a bound kernel driver [ 845.322] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [ 845.322] (EE) Screen 0 deleted because of no matching config section. [ 845.322] (II) UnloadModule: "vesa" root@fbsddesk:~ # uname -a FreeBSD fbsddesk.schwarzes.net 12.0-RELEASE-p7 FreeBSD 12.0-RELEASE-p7 GENE= RIC=20 amd64 I'm using a AMD Ryzen 5 2400G a APU containing a VEGA 11 GPU, which is still not supported. So I'm using the vesa driver which was working fine before. Fortunately, the scfb video driver still works, so it was possible to use s= cfb as a workaround. FreeBSD was upgraded by freebsd-update and the packages via pkg system. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-239065-7788-0ConuWmpSA>