[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Ultra60, XF4.0.1pre2.RC3-1, woody


I'm pretty baffled by an issue I'm having /w a new Ultra running woody /w
XF4.0.1pre2.RC3-1 .. I've fidled with the input clause for the keyboard in
a seemingly endless series of variations, but I can't get the X server to
come up /w sane key mappings. The primary letter keys seem to function,
but the control and command keys are all twisted and mismatched. This is
the clause I'm using:

Section "InputDevice"
        Identifier  "Keyboard0"
        Driver      "keyboard"
        Option      "XkbRules"  "xfree86"
        Option      "XkbModel"  "sun5"
        Option      "XkbLayout" "us"

the keyboard is a sun type 5, recognized at boot:

su(mouse) at 0x1fff13062f8 (irq = 4,7ea) is a 16550A
Sun Mouse-Systems mouse driver version 1.00
su(kbd) at 0x1fff13083f8 (irq = 9,7e9) is a 16550A
Sun TYPE 5 keyboard detected without keyclick

On the console the key mappings are all fine. The machine is running a
custom kernel:

Linux wookiee 2.4.0-test12 #2 SMP Mon Dec 18 02:55:28 EST 2000 sparc64

which I installed to get the SMP support for the second CPU in the box. I
imagine I've done something completely boneheaded, but I'm not sure
what. =( This is the output from /var/log:

(==) ServerLayout "XFree86 Configured"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor0"
(**) |   |-->Device "Card0"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(WW) The directory "/usr/X11R6/lib/X11/fonts/CID/" does not exist.


(II) /dev/fb0: Detected FFB2+/vertical, Z-buffer, Double-buffered.
(II) /dev/fb0: BT498 (PAC2) ramdac detected
(II) /dev/fb0: Detected Creator/Creator3D
(0): [drm] created "ffb" driver at busid "SBUS:/dev/fb0"
(0): [drm] added 8192 byte SAREA at 0x1bd84000
(0): [drm] mapped SAREA 0x1bd84000 to 0x70028000
(0): [drm] framebuffer handle = 0x02000000
(0): [drm] added 1 reserved context for kernel
(II) SUNFFB(0): [drm] FBC Register handle = 0x00600000
(II) SUNFFB(0): [drm] DAC Register handle = 0x00400000
(II) SUNFFB(0): [drm] SFB8R handle = 0x04000000
(II) SUNFFB(0): [drm] SFB32 handle = 0x05000000
(II) SUNFFB(0): [drm] SFB64 handle = 0x06000000
(II) SUNFFB(0): [drm] Visual configs initialized
(II) /dev/fb0: DRM initialized
(==) SUNFFB(0): Backing store disabled
(==) SUNFFB(0): Silken mouse enabled
(II) /dev/fb0: Using acceleration
(II) /dev/fb0: DGA support initialized.
(0): X context handle = 0x00000001
(0): [DRI] installation complete
(II) /dev/fb0: DRM finish setup complete


(**) Option "Protocol" "Microsoft"
(**) Mouse0: Protocol: "Microsoft"
(**) Option "CorePointer"
(**) Mouse0: Core Pointer
(**) Option "Device" "/dev/gpmdata"
(==) Mouse0: Buttons: 3
(**) Option "BaudRate" "1200"
(**) Mouse0: BaudRate: 1200
(II) Keyboard "Keyboard0" handled by legacy driver
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
Couldn't load XKB keymap, falling back to pre-XKB keymap

this last line is obviously pointing at the culprit, but I'm unsure of how
to get the server to acknowledge the maps.. any help appreciated. 'cc me
off list as well pls. Cheers.


How often I found where I should be going only by setting out for
somewhere else..
                                       -- R. Buckminster Fuller

Reply to: