Date: Sat, 23 Jun 2012 11:58:12 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Kevin Oberman <kob6558@gmail.com> Cc: freebsd-x11@freebsd.org Subject: Re: GPU_KMS still not working for me since merge Message-ID: <20120623085812.GN2337@deviant.kiev.zoral.com.ua> In-Reply-To: <CAN6yY1v0=OjKPHJtCG7v0rZnN=56bd43AC_AToOZ6kRsyo=DDg@mail.gmail.com> References: <CAN6yY1vqYyqV9r-nFJFgdsdJ=amGfVniNGCritb3tfp2y81wYg@mail.gmail.com> <20120622213442.GL2337@deviant.kiev.zoral.com.ua> <CAN6yY1v0=OjKPHJtCG7v0rZnN=56bd43AC_AToOZ6kRsyo=DDg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Fri, Jun 22, 2012 at 04:18:13PM -0700, Kevin Oberman wrote: > On Fri, Jun 22, 2012 at 2:34 PM, Konstantin Belousov > <kostikbel@gmail.com> wrote: > > On Fri, Jun 22, 2012 at 02:20:59PM -0700, Kevin Oberman wrote: > >> I am still missing something needed to get the KMS support for my > >> Sandybridge to work.It has been working fine until the KMS code was > >> merged into RELENG-9. > >> > >> I updated my sources and built a new kernel this morning. I already > >> had WITH_KMS=YES and WITH_NEW_XORG=YES in my make.conf from building > >> prior to the patch. šI can confirm that i915kms.ko is built and in > >> /boot/kernel/ > >> > >> When I tried starting X, the screen never left vty mode. The keyboard > >> would no longer work, but I could do a clean shutdown via a network > >> connection. I examined the log and things went awry at: > >> [ š 330.411] drmOpenByBusid: Searching for BusID pci:0000:00:02.0 > >> [ š 330.411] drmOpenDevice: node name is /dev/dri/card0 > >> [ š 330.411] Failed to change owner or group for file /dev/dri! 2: No > >> such file or directory > >> [ š 330.411] Failed to change owner or group for file /dev/dri/card0! > >> 2: No such file or directory > >> [ š 330.411] drmOpenDevice: open result is -1, (No such file or directory) > >> [ š 330.411] Failed to change owner or group for file /dev/dri/card0! > >> 2: No such file or directory > >> [ š 330.411] drmOpenDevice: open result is -1, (No such file or directory) > >> [ š 330.411] drmOpenDevice: Open failed > >> [ š 330.411] drmOpenByBusid: drmOpenMinor returns -2 > >> where my old log showed: > >> [ š 300.134] drmOpenByBusid: Searching for BusID pci:0000:00:02.0 > >> [ š 300.134] drmOpenDevice: node name is /dev/dri/card0 > >> [ š 300.134] drmOpenDevice: open result is 10, (OK) > >> [ š 300.134] drmOpenByBusid: drmOpenMinor returns 10 > >> [ š 300.134] drmOpenByBusid: Interface 1.4 failed, trying 1.1 > >> [ š 300.134] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0 > >> [ š 300.134] (II) intel(0): Creating default Display subsection in > >> Screen section > >> š š š "Builtin Default intel Screen 0" for depth/fbbpp 24/32 > >> [ š 300.134] (==) intel(0): Depth 24, (--) framebuffer bpp 32 > >> [ š 300.134] (==) intel(0): RGB weight 888 > >> [ š 300.134] (==) intel(0): Default visual is TrueColor > >> [ š 300.135] (II) intel(0): Integrated Graphics Chipset: Intel(R) > >> Sandybridge Mobile (GT2+) > >> [ š 300.135] (--) intel(0): Chipset: "Sandybridge Mobile (GT2+)" > >> > >> What am I missing? > > Show the verbose dmesg during the load of i915kms. > > Hmm. I don't see exactly how to get that. I booted verbose, but I see > no console message about the module loading, either to the console or > to /var/run/dmesg.boot. I do see: > DRM_IOCTL_I915_GEM_APERTURE failed: Bad file descriptor > Assuming 131072kB available aperture size. > May lead to reduced performance or incorrect rendering. > get chip id failed: -1 [9] > param: 4, val: 0 > Assertion failed: (0), function drm_intel_bufmgr_gem_init, file intel_bufmgr_gem > .c, line 2332. > xinit: giving up > xinit: unable to connect to X server: Connection refused > xinit: server error Show the _dmesg(8)_ output. Verify that i915kms is loaded. If it is not, investigate why. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAk/lhSMACgkQC3+MBN1Mb4i+KgCgljf5Xn9FJ1xIcUT/DQ20qreo sbsAn3PNNPnpq6nhVs3pB0OxiGZpWCJt =ZN/n -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120623085812.GN2337>