[gentoo-user] Re: X broken; keyboard for sure, maybe dri

[walt]

On 07/04/2009 07:05 PM, felix@×××××××.com wrote:
> A reboot has lost X, in particular the keyboard confuses it.  Here is
> the beginning of the X log.  Unfortunately, I didn't save the previous
> working log.  This is ~amd64 under 2.6.30-gentoo-r1 and -r2.
>
> I learned a while back I could get by without an X config.  It swapped
> a couple of the menu / alt / menu keys, but I adapted.  Now X fills
> its log with these "expected keysym, got XF86*" messages, and I have
> no idea what causes them.  Without X, it's hard to search the forums
> and bugzilla to see how others have coped.
>
> I suspect I have emerged or unmerged something I shouldn't have, but I
> don't remember anything particular on this update / reboot cycle other
> than LVM and the kernel change (2.6.30-gentoo-r1 to -r2), and reboot
> with either -r1 or -r2 makes no difference that I can see.
>
> There are two other problems.  The "fb0" complaint has been there for
> a while; I have to "sudo rm /dev/fb0" for X to work.  The kernel has
> the framebuffer configured, but I haven't investigated much because I
> can get X working without /dev/fb0.
>
> The "dri" line seems new, but might not matter.  The display works.
> The mouse works.  It seems to be only the keyboard which is hosed.
> But if someone knows how to fix the "dri" complaint, thanks.
>
> =========== begin X log
> X.Org X Server 1.5.2
> Release Date: 10 October 2008
> X Protocol Version 11, Revision 0
> Build Operating System: Linux 2.6.27-gentoo-r7 x86_64
> Current Operating System: Linux crowfix 2.6.30-gentoo-r2 #1 SMP PREEMPT Sat Jul 4 14:07:08 PDT 2009 x86_64
> Build Date: 20 December 2008  04:18:31PM
>
> 	Before reporting problems, check http://wiki.x.org
> 	to make sure that you have the latest version.
> Module Loader present
> Markers: (--) probed, (**) from config file, (==) default setting,
> 	(++) from command line, (!!) notice, (II) informational,
> 	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/Xorg.0.log", Time: Sat Jul  4 17:47:02 2009
> (EE) Unable to locate/open config file
> New driver is "ati"
> (==) Using default built-in configuration (30 lines)
> (EE) Failed to load module "dri" (module does not exist, 0)
> (EE) open /dev/fb0: No such file or directory
> error setting MTRR (base = 0xfd000000, size = 0x00800000, type = 1) Invalid argument (22)
> expected keysym, got XF86Battery: line 59 of inet
> ============= end X log

I started getting the same 'expected keysym' messages recently but my
X continues to work okay anyway, so I think that's a red herring.

I'd say check the dates on everything in /usr/lib/xorg and re-emerge
anything that's not very recent, especially evdev (which I assume you
use if you got rid of xorg.conf?).

You should have a /usr/lib/xorg/modules/extensions/libdri.so -- that's the dri
module that your X can't find.  It's a symlink on my machine because I have
both the xorg and nvidia versions of opengl on my machine.  The 'eselect opengl'
function is what creates the symlink to the correct version of libdri.so.

Is the 'ati' driver correct for your video card?  Be sure to re-emerge that if
it is truly the right driver for you.