Fedora 10: Trouble installing libdrm (2.4.4) for latest Intel driver (2.6)

[Dan Nicholson]

On Wed, Jan 21, 2009 at 1:57 PM, Joe Smith <stopads at yahoo.com> wrote:
>
>> I tried starting X
>> > anyway, but the keyboard and mouse where unresponsive.
>>
>> For the keyboard/mouse issues, you'd probably have to
>> attach an
>> Xorg.log. Did you build the evdev input driver against the
>> new
>> xserver?
>>
>> --
>> Dan
>
> PART 1:
>
> Thanks, the evdev driver was the problem.  I built 2.1.1 against the new xserver.  I noticed in the log that fbdev and vesa weren't found either, so I built 0.4.0 and 2.1.0, respectively.
>
> That cleaned it up for the most part, but I'm still getting some errors that I don't think are normal (here's one example):
>
> ....
> (EE) XKB: Couldn't open rules file /opt/gfx-test/share/X11/xkb/rules/evdev
> (EE) XKB: No components provided for device Video Bus
> ....
>
> I've attached my log file.  Am I supposed to have a "rules file" for evdev?

Unfortunately, the script you followed doesn't seem to tell you about
handling the XKB data. You can either install xkeyboard-config or
follow the instructions for "Making the keyboard work" here:

http://wiki.x.org/wiki/Development/git

Or, as a quick and dirty method:
ln -sn /usr/share/xkb /opt/gfx-test/share/X11/xkb
ln -s /usr/bin/xkbcomp /opt/gfx-test/bin

> ---------
> PART 2:
>
> I installed system-config-display to generate a xorg.conf.  I added the UXA option for DRI2 (my xorg.conf is attached).  Then I tried out glxinfo (and glxgears).  They don't work:
>
> [root at xyz ~]# glxinfo
> name of display: :0.0
> X Error of failed request:  BadLength (poly request too large or internal Xlib length error)
>  Major opcode of failed request:  135 (DRI2)
>  Minor opcode of failed request:  1 ()
>  Serial number of failed request:  16
>  Current serial number in output stream:  16
>
> In case the new glxinfo is different, I called it directly, like this: /opt/gfx-test/bin/glxinfo.  Same result.
>
> Am I doing something wrong?  Thanks for the help so far.

I don't know why that's happening since the log seems to indicate the
DRI2 is loaded. Maybe you want to try LIBGL_DEBUG=verbose glxinfo.

--
Dan