Mailinglist Archive: opensuse (2441 mails)
| < Previous | Next > |
Re: [SLE] 9.3: Keyboard keymaps and xorg
- From: AmigaPhil@xxxxxxx
- Date: 15 Jun 2005 15:12:17 +0100
- Message-id: <6671.27T878T9122335AmigaPhil@xxxxxxx>
ken (gebser@xxxxxxxxxxxxx) wrote something I wish to comment :
(news:<42AFFA2D.5070200@xxxxxxxxxxxxx> posted on 15-juin-05 10:51:41)
>>Sounded good to me. That line was
>>
>> Option "XkbLayout" "be"
>>
>>and I change it to:
>>
>> Option "XkbLayout" "be-latin1"
>>
>>then reboot the computer... No change :-(
>>
>>I did perform the same change to /etc/X11/xorg.conf-Linux1 (where
>>"Linux1" is the name of my machine) and reboot. No change either.
>>
>
> Strange crap! Do you have /etc/X11/xorg.conf or just the
> xorg.conf-Linux1 file? If there's no xorg.conf, copy the
> xorg.conf-Linux1 to xorg.conf. Then just do Ctrl-Alt-Backspace; you
> don't need to reboot.
xorg.conf was there, already same content as in as xorg.conf-Linux1
> I forgot to mention in my previous post that the keyboard can be
> configured in the file /etc/sysconfig/keyboard (also). Near the top of
> that file you'll find a variable called KEYTABLE; set that to
> "be-latin1.map.gz".
It is already.
> You might want to check through /etc/sysconfig/language also, to make
> sure the settings are correct there too.
Not sure.
The first entry is a long string which looks like a list of language
file. Something like:
string(POSIX,ca_ES.ISO-8859-1, ... ,zh_CN.UTF-8)
Don't know if it has any importance, but there is nothing related to
Belgium. For the French language, there is fr_FR@euro,fr_FR.ISO-8859-1,
fr_FR.UTF-8, but there is no fr_BE<something>.
Next on the file, the RC_LANG is set to "fr_FR.UTF-8"
Other entries which are set to something are:
ROOT_USES_LANG="ctype"
AUTO_DETECT_UTF8="no"
INSTALLED_LANGUAGES="en_GB,en_US,fr_FR"
> If it still doesn't work after these changes, check the date/time on
> your /var/log/Xorg.0.log. If the date/time corresponds to the last time
> you loaded X or after, cut-n-paste that into your next reply so we can
> have a look at it.
Good idea !
Hmm, the file is 41Kb, so i'll paste here only the lines that seems
relevant to me (and related to the keyboard):
(**) Option "CoreKeyboard"
(**) Keyboard[0]: Core Keyboard
(**) Option "Protocol" "Standard"
(**) Keyboard[0]: Protocol: Standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xfree86"
(**) Keyboard[0]: XkbRules: "xfree86"
(**) Option "XkbModel" "pc105"
(**) Keyboard[0]: XkbModel: "pc105"
(**) Option "XkbLayout" "be"
(**) Keyboard[0]: XkbLayout: "be"
(**) Option "CustomKeycodes" "off"
(**) Keyboard[0]: CustomKeycodes disabled
(**) Option "Protocol" "explorerps/2"
(**) Mouse[1]: Device: "/dev/input/mice"
(**) Mouse[1]: Protocol: "explorerps/2"
(**) Option "CorePointer"
(**) Mouse[1]: Core Pointer
(**) Option "Device" "/dev/input/mice"
(==) Mouse[1]: Emulate3Buttons, Emulate3Timeout: 50
(==) Mouse[1]: Buttons: 3
(II) XINPUT: Adding extended input device "Mouse[1]" (type: MOUSE)
(II) XINPUT: Adding extended input device "Keyboard[0]" (type: KEYBOARD)
(EE) Couldn't load XKB keymap, falling back to pre-XKB keymap
I saw there is also a file SaX.log there. I find it very informative
as to the trouble I have encountered while trying to configure the
keyboard with SaX2. Here are some lines I find interesting
(between "<" and ">" are comments I've added):
13-Jun 23:23:57 <X> Logging File contents: /tmp/sax2-8841/xorg.conf [
<content of xorg.conf here>
]
sh: -c: line 0: unexpected EOF while looking for matching `''
sh: -c: line 1: syntax error: unexpected end of file
13-Jun 23:24:10 <X> Logging File contents: /var/log/xlog [
< ... >
(**) Option "CoreKeyboard"
(**) Keyboard[0]: Core Keyboard
(**) Option "Protocol" "Standard"
(**) Keyboard[0]: Protocol: Standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xfree86"
(**) Keyboard[0]: XkbRules: "xfree86"
(**) Option "XkbModel" "pc104"
(**) Keyboard[0]: XkbModel: "pc104"
(**) Option "XkbLayout" "be"
(**) Keyboard[0]: XkbLayout: "be"
(**) Option "CustomKeycodes" "off"
(**) Keyboard[0]: CustomKeycodes disabled
(**) Option "Protocol" "explorerps/2"
(**) Mouse[1]: Device: "/dev/input/mice"
(**) Mouse[1]: Protocol: "explorerps/2"
(**) Option "CorePointer"
(**) Mouse[1]: Core Pointer
(**) Option "Device" "/dev/input/mice"
(==) Mouse[1]: Emulate3Buttons, Emulate3Timeout: 50
(==) Mouse[1]: Buttons: 3
(II) XINPUT: Adding extended input device "Mouse[1]" (type: MOUSE)
(II) XINPUT: Adding extended input device "Keyboard[0]" (type: KEYBOARD)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error: Can't find file "pc" for geometry include
> Exiting
> Abandoning geometry file "default"
Errors from xkbcomp are not fatal to the X server
(EE) Couldn't load XKB keymap, falling back to pre-XKB keymap
< ... >
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error: Can't find file "unknown" for geometry include
> Exiting
> Abandoning geometry file "default"
Errors from xkbcomp are not fatal to the X server
< those last 5 lines are reproduced 4 more time >
]
>>In another reply on this list, Carlos E. R. suggested that the
>>keyboard problem might be due to a bug in KDE (someone else on the
>>Spanish list reporteing about the same problem).
>>
> That's possible. I doubt, though, with all the people around the world
> using Linux, including developers, that there's a major bug in non-US
> keyboard configuration. Of course, since I don't use that, I can't
> really make first-hand comments.
I finally don't think it's a bug in KDE as the keyboard problem also
happen when I log in a FVWM session.
>> Well, I tried to re-install xorg from runlevel 3 using yast in text
>> mode, with the same result (failed).
>>
>
> Why?
I thought I should try the installation without the X server running
(and possibly "locking" some files in use (???) )
> Well, we still don't have it working for you. So, the next time I'm
> Belgium you can loan me your non-working car.
:-)
AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1
-----BEGIN ECHELON TEASER-----
The following garbage may or may not contain crypted message.
At least you now know I'm an advocate for the respect of privacy.
abpOFtWx1zaptVq5xVytHHyHvIzHrDkEFYEIEHntSlzVFFMpG53FRVzS2OaIqtVMlqRVRDOH
UMFScDJpn0vyEBHlIFvtztvJIxUALnOzEGAPFFp3KFTMVFtTOHOMlOtDRyItVHIytdWcElSd
aRWSVotICJtVMIx0MvypptjyFlVKUILyDbLRRyzAVMp1pFjqvGvU5vLl1nJ6vOVz6ARHITOO
I5JlDJvhfRHBOVvEPnN5WvvOHuhqtt
-----END ECHELON TEASER-----
(news:<42AFFA2D.5070200@xxxxxxxxxxxxx> posted on 15-juin-05 10:51:41)
>>Sounded good to me. That line was
>>
>> Option "XkbLayout" "be"
>>
>>and I change it to:
>>
>> Option "XkbLayout" "be-latin1"
>>
>>then reboot the computer... No change :-(
>>
>>I did perform the same change to /etc/X11/xorg.conf-Linux1 (where
>>"Linux1" is the name of my machine) and reboot. No change either.
>>
>
> Strange crap! Do you have /etc/X11/xorg.conf or just the
> xorg.conf-Linux1 file? If there's no xorg.conf, copy the
> xorg.conf-Linux1 to xorg.conf. Then just do Ctrl-Alt-Backspace; you
> don't need to reboot.
xorg.conf was there, already same content as in as xorg.conf-Linux1
> I forgot to mention in my previous post that the keyboard can be
> configured in the file /etc/sysconfig/keyboard (also). Near the top of
> that file you'll find a variable called KEYTABLE; set that to
> "be-latin1.map.gz".
It is already.
> You might want to check through /etc/sysconfig/language also, to make
> sure the settings are correct there too.
Not sure.
The first entry is a long string which looks like a list of language
file. Something like:
string(POSIX,ca_ES.ISO-8859-1, ... ,zh_CN.UTF-8)
Don't know if it has any importance, but there is nothing related to
Belgium. For the French language, there is fr_FR@euro,fr_FR.ISO-8859-1,
fr_FR.UTF-8, but there is no fr_BE<something>.
Next on the file, the RC_LANG is set to "fr_FR.UTF-8"
Other entries which are set to something are:
ROOT_USES_LANG="ctype"
AUTO_DETECT_UTF8="no"
INSTALLED_LANGUAGES="en_GB,en_US,fr_FR"
> If it still doesn't work after these changes, check the date/time on
> your /var/log/Xorg.0.log. If the date/time corresponds to the last time
> you loaded X or after, cut-n-paste that into your next reply so we can
> have a look at it.
Good idea !
Hmm, the file is 41Kb, so i'll paste here only the lines that seems
relevant to me (and related to the keyboard):
(**) Option "CoreKeyboard"
(**) Keyboard[0]: Core Keyboard
(**) Option "Protocol" "Standard"
(**) Keyboard[0]: Protocol: Standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xfree86"
(**) Keyboard[0]: XkbRules: "xfree86"
(**) Option "XkbModel" "pc105"
(**) Keyboard[0]: XkbModel: "pc105"
(**) Option "XkbLayout" "be"
(**) Keyboard[0]: XkbLayout: "be"
(**) Option "CustomKeycodes" "off"
(**) Keyboard[0]: CustomKeycodes disabled
(**) Option "Protocol" "explorerps/2"
(**) Mouse[1]: Device: "/dev/input/mice"
(**) Mouse[1]: Protocol: "explorerps/2"
(**) Option "CorePointer"
(**) Mouse[1]: Core Pointer
(**) Option "Device" "/dev/input/mice"
(==) Mouse[1]: Emulate3Buttons, Emulate3Timeout: 50
(==) Mouse[1]: Buttons: 3
(II) XINPUT: Adding extended input device "Mouse[1]" (type: MOUSE)
(II) XINPUT: Adding extended input device "Keyboard[0]" (type: KEYBOARD)
(EE) Couldn't load XKB keymap, falling back to pre-XKB keymap
I saw there is also a file SaX.log there. I find it very informative
as to the trouble I have encountered while trying to configure the
keyboard with SaX2. Here are some lines I find interesting
(between "<" and ">" are comments I've added):
13-Jun 23:23:57 <X> Logging File contents: /tmp/sax2-8841/xorg.conf [
<content of xorg.conf here>
]
sh: -c: line 0: unexpected EOF while looking for matching `''
sh: -c: line 1: syntax error: unexpected end of file
13-Jun 23:24:10 <X> Logging File contents: /var/log/xlog [
< ... >
(**) Option "CoreKeyboard"
(**) Keyboard[0]: Core Keyboard
(**) Option "Protocol" "Standard"
(**) Keyboard[0]: Protocol: Standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xfree86"
(**) Keyboard[0]: XkbRules: "xfree86"
(**) Option "XkbModel" "pc104"
(**) Keyboard[0]: XkbModel: "pc104"
(**) Option "XkbLayout" "be"
(**) Keyboard[0]: XkbLayout: "be"
(**) Option "CustomKeycodes" "off"
(**) Keyboard[0]: CustomKeycodes disabled
(**) Option "Protocol" "explorerps/2"
(**) Mouse[1]: Device: "/dev/input/mice"
(**) Mouse[1]: Protocol: "explorerps/2"
(**) Option "CorePointer"
(**) Mouse[1]: Core Pointer
(**) Option "Device" "/dev/input/mice"
(==) Mouse[1]: Emulate3Buttons, Emulate3Timeout: 50
(==) Mouse[1]: Buttons: 3
(II) XINPUT: Adding extended input device "Mouse[1]" (type: MOUSE)
(II) XINPUT: Adding extended input device "Keyboard[0]" (type: KEYBOARD)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error: Can't find file "pc" for geometry include
> Exiting
> Abandoning geometry file "default"
Errors from xkbcomp are not fatal to the X server
(EE) Couldn't load XKB keymap, falling back to pre-XKB keymap
< ... >
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error: Can't find file "unknown" for geometry include
> Exiting
> Abandoning geometry file "default"
Errors from xkbcomp are not fatal to the X server
< those last 5 lines are reproduced 4 more time >
]
>>In another reply on this list, Carlos E. R. suggested that the
>>keyboard problem might be due to a bug in KDE (someone else on the
>>Spanish list reporteing about the same problem).
>>
> That's possible. I doubt, though, with all the people around the world
> using Linux, including developers, that there's a major bug in non-US
> keyboard configuration. Of course, since I don't use that, I can't
> really make first-hand comments.
I finally don't think it's a bug in KDE as the keyboard problem also
happen when I log in a FVWM session.
>> Well, I tried to re-install xorg from runlevel 3 using yast in text
>> mode, with the same result (failed).
>>
>
> Why?
I thought I should try the installation without the X server running
(and possibly "locking" some files in use (???) )
> Well, we still don't have it working for you. So, the next time I'm
> Belgium you can loan me your non-working car.
:-)
AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1
-----BEGIN ECHELON TEASER-----
The following garbage may or may not contain crypted message.
At least you now know I'm an advocate for the respect of privacy.
abpOFtWx1zaptVq5xVytHHyHvIzHrDkEFYEIEHntSlzVFFMpG53FRVzS2OaIqtVMlqRVRDOH
UMFScDJpn0vyEBHlIFvtztvJIxUALnOzEGAPFFp3KFTMVFtTOHOMlOtDRyItVHIytdWcElSd
aRWSVotICJtVMIx0MvypptjyFlVKUILyDbLRRyzAVMp1pFjqvGvU5vLl1nJ6vOVz6ARHITOO
I5JlDJvhfRHBOVvEPnN5WvvOHuhqtt
-----END ECHELON TEASER-----
| < Previous | Next > |