Mailing List Archive: Gentoo: User

Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'

Index | Next | Previous | View Threaded

w41ter at gmail

Dec 12, 2009, 4:20 PM

Post #1 of 5 (268 views)
Permalink

Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'

On 12/12/2009 03:14 PM, Mick wrote:

> ...
> I have had mouse, keyboard and synaptics along with evdev in my
> INPUT_DEVICES and have emerged relative drivers. I am now going to
> remove them and see what gives.

I know nothing about the synaptics driver, so be careful about deleting
it. Maybe rename it instead of deleting it?

>
> I am not clear which /etc/hal/fdi/policy/* files I should have in
> there ... any ideas?

That depends on what hardware you have -- a lot of the stuff that once
went into xorg.conf can be put in an fdi file now.

Here is an example: I have an unusual mouse with four buttons and no
wheel, and I use one extra button to simulate a mouse wheel:

$cat /etc/hal/fdi/policy/10-x11-logitech.fdi
<?xml version="1.0" encoding="ISO-8859-1"?>
<deviceinfo version="0.2">
<device>
<match key="info.product" contains="ImExPS/2">
<merge key="input.x11_options.EmulateWheel" type="string">true</merge>
<merge key="input.x11_options.EmulateWheelButton" type="string">8</merge>
</match>
</device>
</deviceinfo>

The two lines with "input.x11_options" used to be in my xorg.conf in the
Input section. Those lines do the same thing now that I've moved them into
an fdi file.

michaelkintzios at gmail

Dec 12, 2009, 4:20 PM

Post #2 of 5 (254 views)
Permalink

Re: Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap' [In reply to]

On 12/12/2009, walt <w41ter [at] gmail> wrote:
> On 12/12/2009 03:14 PM, Mick wrote:
>
>> ...
>> I have had mouse, keyboard and synaptics along with evdev in my
>> INPUT_DEVICES and have emerged relative drivers. I am now going to
>> remove them and see what gives.
>
> I know nothing about the synaptics driver, so be careful about deleting
> it. Maybe rename it instead of deleting it?

Nope, unmerged it and deleted it from make.conf, then when I emerged
xf86-video-ati and evdev all other drivers (mouse, keyboard,
synaptics) were brought in as well.

>>
>> I am not clear which /etc/hal/fdi/policy/* files I should have in
>> there ... any ideas?
>
> That depends on what hardware you have -- a lot of the stuff that once
> went into xorg.conf can be put in an fdi file now.
>
> Here is an example:

Thanks for that.

I tried the startx trick. I recall that this would launch my WM
(fluxbox), but now all I get is an X session with twm! Has something
changed with /etc/rc.conf? Where should I specify fluxbox?

No /var/log/xdm.log or other errors were there this time. Trying to
start xdm and I keep getting the same old errors:

XIO: fatal IO error 11 (Resource temporarily unavailable) on X server (:0.0)

and

(EE) XKB: No components provided for device Virtual core keyboard.

I am running out of things to try now. I don't have a recent enough
back up otherwise I would roll back this bad experience.
--
Regards,
Mick

rdalek1967 at gmail

Dec 12, 2009, 6:17 PM

Post #3 of 5 (256 views)
Permalink

Re: Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap' [In reply to]

walt wrote:
>
> I have these lines in my xorg.conf but I can't remember when or why I
> put them there. I believe it had something to do with evdev, though.
>
> Section "ServerFlags"
> Option "AllowEmptyInput" "true"
> Option "AutoAddDevices" "true"
> EndSection
>

If I recall correctly, that disables evdev. I think the first Option
disables it. I'm not real sure about the second one. I remember
because I did that when I couldn't get evdev to work.

Dale

:-) :-)

w41ter at gmail

Dec 12, 2009, 6:20 PM

Post #4 of 5 (256 views)
Permalink

Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap' [In reply to]

On 12/12/2009 04:20 PM, Mick wrote:
> ...
> I tried the startx trick. I recall that this would launch my WM
> (fluxbox), but now all I get is an X session with twm! Has something
> changed with /etc/rc.conf? Where should I specify fluxbox?

That twm session is the default (see end of /etc/X11/xinit/xinitrc)
if you don't specify what you really want. The xdm display manager
checks in ~/.xsession for the stuff you want to run (i.e. fluxbox),
but startx uses the file ~/.xinitrc for the same purpose. You could
probably just copy .xsession to .xinitrc for starters.

>
> No /var/log/xdm.log or other errors were there this time. Trying to
> start xdm and I keep getting the same old errors:
>
> XIO: fatal IO error 11 (Resource temporarily unavailable) on X server (:0.0)
>
> and
>
> (EE) XKB: No components provided for device Virtual core keyboard.
>
> I am running out of things to try now. I don't have a recent enough
> back up otherwise I would roll back this bad experience.

I have these lines in my xorg.conf but I can't remember when or why I
put them there. I believe it had something to do with evdev, though.

Section "ServerFlags"
Option "AllowEmptyInput" "true"
Option "AutoAddDevices" "true"
EndSection

michaelkintzios at gmail

Dec 13, 2009, 2:04 AM

Post #5 of 5 (260 views)
Permalink

Re: Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap' [In reply to]

2009/12/13 walt <w41ter [at] gmail>:
> On 12/12/2009 04:20 PM, Mick wrote:
>>
>> ...
>> I tried the startx trick. �I recall that this would launch my WM
>> (fluxbox), but now all I get is an X session with twm! �Has something
>> changed with /etc/rc.conf? �Where should I specify fluxbox?
>
> That twm session is the default (see end of /etc/X11/xinit/xinitrc)
> if you don't specify what you really want. �The xdm display manager
> checks in ~/.xsession for the stuff you want to run (i.e. fluxbox),
> but startx uses the file ~/.xinitrc for the same purpose. �You could
> probably just copy .xsession to .xinitrc for starters.

OK, but I never had set up ~/.xsession or ~/.xinitrc files. This is a
single user machine. As far as I can recall I had only set up in
/etc/rc.conf the parameter XSESSION="fluxbox", which looked in
/etc/X11/Sessions/ and ran the fluxbox configuration file that I had
in there.

Looking at /etc/conf.d/xdm I see this:
=========================================
# What display manager do you use ? [. xdm | gdm | kdm | kdm-4.3 | gpe
| entrance ]
# NOTE: If this is set in /etc/rc.conf, that setting will override this one.
=========================================
In that file I have specified DISPLAYMANAGER="xdm". Again as far as I
recall this is how I had set things up, so I am not sure what has
changed recently.

Setting a ~/.xinitrc file with 'exec startfluxbox' in it starts
fluxbox nicely if I run startx from the console - but this is not the
same session that I would get which would also include xconsole. I
found these messages now, but no significant errors:
=========================================
Setting CPU scaling governor "performance" for CPU 1...
could not open file
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor for writing!
failed setting 'performance' CPUfreq governor!
Failed to read: session.screen0.maxIgnoreIncrement
Setting default value
Failed to read: session.screen0.maxDisableMove
Setting default value
Failed to read: session.screen0.maxDisableResize
Setting default value
Failed to read: session.screen0.noFocusWhileTypingDelay
Setting default value
Failed to read: session.screen0.tooltipDelay
Setting default value
Failed to read: session.screen0.clientMenu.usePixmap
Setting default value
Failed to read: session.screen0.maxIgnoreIncrement
Setting default value
Failed to read: session.screen0.maxDisableMove
Setting default value
Failed to read: session.screen0.maxDisableResize
Setting default value
Failed to read: session.screen0.noFocusWhileTypingDelay
Setting default value
Failed to read: session.screen0.tooltipDelay
Setting default value
Failed to read: session.screen0.clientMenu.usePixmap
Setting default value
Failed to read: session.screen0.maxIgnoreIncrement
Setting default value
Failed to read: session.screen0.maxDisableMove
Setting default value
Failed to read: session.screen0.maxDisableResize
Setting default value
Failed to read: session.screen0.noFocusWhileTypingDelay
Setting default value
Failed to read: session.screen0.tooltipDelay
Setting default value
Failed to read: session.screen0.clientMenu.usePixmap
Setting default value
Failed to read: session.screen0.slit.acceptKdeDockapps
Setting default value
=========================================

So, what would be the way to start xdm and have xdm starting fluxbox?
--
Regards,
Mick

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads