Can X coexist with the Framebuffer console? (kbdrate woes)

[John Magolske <listmail@b79.net>]

Why does the X Window System reset kbdrate? I've set keyboard delay
and repeat for the framebuffer console with "kbdrate -r 30 -d 250 -s",
but starting up X will reset these values to slower settings.

Switching from X to another VT and issuing "kbdrate -r 30 -d 250 -s"
does nothing. Keyboard delay & repeat remain at slower setting so long
as X is running. These values can only be re-set after closing X.

In ~/.xinitrc "xset m 2 5 r rate 250 30" sets the delay & repeat rate
for everything in X. But switching to another VT finds the console
stuck at slower settings, effectively rendering the framebuffer
console useless to me. A half solution is to start X with this script:

    #!/bin/sh
    startx
    # startx seems to mess with kbdrate...set it back to what I like
    sudo kbdrate -r 30 -d 250 -s

Upon closing X, this resets the delay & repeat rate to what it was.
But kbdrate remains at a slower setting so long as X is running.

I find it is not possible to have X running in one VT and still be
able to use a framebuffer console in another VT.

Is there some way to avoid how X resets kbdrate?

TIA for any suggestions,

John


-- 
John Magolske
http://B79.net/contact