Date: Wed, 02 Jan 2019 20:58:15 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 233034] graphics/mesa-dri: update to 18.3.1 Message-ID: <bug-233034-7141-VIM7FpuX1o@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-233034-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-233034-7141@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=3D233034 --- Comment #9 from rkoberman@gmail.com --- (In reply to Greg V from comment #8) I'm sure that I should know what triggers the selection of modesetting vs.xf86-intel. In my log I see all possible drivers loaded and then the following: [ 90.970] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20171222 [ 90.971] (WW) Falling back to old probe method for modesetting [ 90.971] (WW) Falling back to old probe method for scfb [ 90.971] scfb trace: probe start [ 90.971] scfb trace: probe done [ 90.971] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [ 90.972] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphi= cs 3000 [ 90.973] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx; using a maximum of 2 threads [ 90.973] (II) intel(0): Creating default Display subsection in Screen section "Screen0" for depth/fbbpp 24/32 [ 90.973] (**) intel(0): Depth 24, (--) framebuffer bpp 32 [ 90.973] (=3D=3D) intel(0): RGB weight 888 [ 90.973] (=3D=3D) intel(0): Default visual is TrueColor [ 91.004] (II) intel(0): Output LVDS1 has no monitor section [ 91.004] (II) intel(0): Enabled output LVDS1 [ 91.004] (II) intel(0): Output VGA1 has no monitor section [ 91.004] (II) intel(0): Enabled output VGA1 [ 91.004] (II) intel(0): Output HDMI1 has no monitor section [ 91.004] (II) intel(0): Enabled output HDMI1 [ 91.005] (II) intel(0): Output DP1 has no monitor section [ 91.005] (II) intel(0): Enabled output DP1 [ 91.005] (II) intel(0): Output HDMI2 has no monitor section [ 91.005] (II) intel(0): Enabled output HDMI2 [ 91.005] (II) intel(0): Output HDMI3 has no monitor section [ 91.005] (II) intel(0): Enabled output HDMI3 [ 91.005] (II) intel(0): Output DP2 has no monitor section [ 91.005] (II) intel(0): Enabled output DP2 [ 91.005] (II) intel(0): Output DP3 has no monitor section [ 91.005] (II) intel(0): Enabled output DP3 [ 91.005] (--) intel(0): Using a maximum size of 256x256 for hardware cursors [ 91.005] (II) intel(0): Output VIRTUAL1 has no monitor section [ 91.005] (II) intel(0): Enabled output VIRTUAL1 [ 91.005] (--) intel(0): Output LVDS1 using initial mode 1600x900 on pip= e 0 [ 91.006] (=3D=3D) intel(0): TearFree disabled [ 91.006] (=3D=3D) intel(0): DPI set to (96, 96) [ 91.006] (II) Loading sub module "dri3" [ 91.006] (II) LoadModule: "dri3" [ 91.006] (II) Module "dri3" already built-in [ 91.006] (II) Loading sub module "dri2" [ 91.006] (II) LoadModule: "dri2" [ 91.006] (II) Module "dri2" already built-in [ 91.006] (II) Loading sub module "present" [ 91.006] (II) LoadModule: "present" [ 91.006] (II) Module "present" already built-in [ 91.006] (II) Module "present" already built-in [ 91.006] (II) UnloadModule: "modesetting" [ 91.006] (II) Unloading modesetting [ 91.006] (II) UnloadModule: "scfb" [ 91.006] (II) Unloading scfb [ 91.006] (II) UnloadModule: "vesa" [ 91.006] (II) Unloading vesa [ 91.006] (II) UnloadModule: "modesetting" [ 91.006] (II) Unloading modesetting [ 91.006] (II) UnloadModule: "scfb" [ 91.006] (II) Unloading scfb [ 91.006] (II) UnloadModule: "vesa" [ 91.006] (II) Unloading vesa and that leaves the xf86-intel-driver. Do I need to put something in the co= nf file to cause modesetting to be selected? I see nothing to indicate a probl= em (except that one warning) to cause modesetting to be rejected, so I assume = that X thinks that the xf86-intel-deriver should be preferred. Probably unrelated, 32 seconds after Xorg starts, I get the following: [ 125.009] (EE) intel(0): Failed to submit rendering commands (Bad addres= s), disabling acceleration. I can confirm that VAAPI is no longer working, but it was not working witho= ut HYBRID and with mesa-18.1.9. I suspect that it has worked since I upgraded = to 12.0. But that is probably for another ticket. --=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-233034-7141-VIM7FpuX1o>