GPU_KMS still not working for me since merge

[Kevin Oberman]

On Fri, Jun 22, 2012 at 2:34 PM, Konstantin Belousov
<kostikbel at 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

The log contains:
[    39.104] (II) LoadModule: "intel"
[    39.105] (II) Loading /usr/local/lib/xorg/modules/drivers/intel_drv.so
[    39.154] (II) Module intel: vendor="X.Org Foundation"
[    39.154]    compiled for 1.10.6, module version = 2.16.0
[    39.154]    Module class: X.Org Video Driver
[    39.154]    ABI class: X.Org Video Driver, version 10.0
[    39.154] (II) LoadModule: "vesa"
[    39.155] (II) Loading /usr/local/lib/xorg/modules/drivers/vesa_drv.so
[    39.160] (II) Module vesa: vendor="X.Org Foundation"
[    39.160]    compiled for 1.10.6, module version = 2.3.0
[    39.160]    Module class: X.Org Video Driver
[    39.160]    ABI class: X.Org Video Driver, version 10.0
[    39.160] (II) LoadModule: "fbdev"
[    39.160] (II) Loading /usr/local/lib/xorg/modules/drivers/fbdev_drv.so
[    39.166] (II) Module fbdev: vendor="X.Org Foundation"
[    39.166]    compiled for 1.10.6, module version = 0.4.2
[    39.166]    ABI class: X.Org Video Driver, version 10.0
[    39.166] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
        i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
        E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
        965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
        4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
        Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
        Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
        Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
        Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
        Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server

-- 
R. Kevin Oberman, Network Engineer
E-mail: kob6558 at gmail.com