clavier azerty sous xfce

Le Tue, 25 May 2004 08:08:25 +0200, thierry a écrit :

je n'arrive pas a avoir un clavier 105 touches en azerty sous xfce,
windowsmaker, mais je l'ai sous kde.

j'ai recherche avec google et j'ai modifie ou controle certains fichier
(XF86Config, profile) mais ca ne marche pas.

Tu n'as pas le bon type de clavier dans XF86Config. KDE utilise son propre
réglage de clavier (ce qui est une grosse connerie, mais bon). Tu dois
avoir dans /etc/X11/XF86Config :

Option "XkbLayout" "fr"

Voilà...

--
Si non confectus non reficiat.

Le 25-05-2004, Emmanuel Florac écrivait:

Le Tue, 25 May 2004 08:08:25 +0200, thierry a écrit :

je n'arrive pas a avoir un clavier 105 touches en azerty sous xfce,
windowsmaker, mais je l'ai sous kde.

j'ai recherche avec google et j'ai modifie ou controle certains fichier
(XF86Config, profile) mais ca ne marche pas.

Tu n'as pas le bon type de clavier dans XF86Config. KDE utilise son propre
réglage de clavier (ce qui est une grosse connerie, mais bon). Tu dois
avoir dans /etc/X11/XF86Config :

Option "XkbLayout" "fr"

Rajouter éventuellement:

Option "XkbModel" "pc105"

--
apt-get --purge remove Bush

Le 25-05-2004, Emmanuel Florac écrivait:

je n'arrive pas a avoir un clavier 105 touches en azerty sous xfce,
windowsmaker, mais je l'ai sous kde.

j'ai recherche avec google et j'ai modifie ou controle certains fichier
(XF86Config, profile) mais ca ne marche pas.

Tu n'as pas le bon type de clavier dans XF86Config. KDE utilise son propre
réglage de clavier (ce qui est une grosse connerie, mais bon). Tu dois
avoir dans /etc/X11/XF86Config :

Option "XkbLayout" "fr"

Rajouter éventuellement:
Option "XkbModel" "pc105"

bonjour

voici mon XF86config a partir de la section < input devices>

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

Identifier "Keyboard"
Driver "Keyboard"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

# Option "Protocol" "Xqueue"

# Set the keyboard auto repeat parameters. Not all platforms implement
# this.

# Option "AutoRepeat" "500 5"

# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).

# Option "Xleds" "1 2 3"

# To disable the XKEYBOARD extension, uncomment XkbDisable.

# Option "XkbDisable"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a European
# keyboard, you will probably want to use one of:
#
# Option "XkbModel" "pc102"
# Option "XkbModel" "pc105"
#
# If you have a Microsoft Natural keyboard, you can use:
#
# Option "XkbModel" "microsoft"
#
# If you have a US "windows" keyboard you will want:
#
# Option "XkbModel" "pc104"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#
# Option "XkbLayout" "fr"
#
# or:
#
# Option "XkbLayout" "fr"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#
# Option "XkbOptions" "ctrl:swapcaps"


# These are the default XKB settings for XFree86
#
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "fr"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"

# On platforms where PnP mouse detection is supported the following
# protocol setting can be used when using a newer PnP mouse:

# Option "Protocol" "Auto"

# The available mouse protocols types that you can set below are:
# Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
# Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
# MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
# ThinkingMouse ThinkingMousePS/2 Xqueue
Option "Protocol" "IMPS/2"

# The mouse device. The device is normally set to /dev/mouse,
# which is usually a symbolic link to the real device.

Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
# Option "Device" "/dev/mouse"
# Option "Device" "/dev/psaux"
# Option "Device" "/dev/ttyS0"
# Option "Device" "/dev/ttyS1"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

# Option "Protocol" "Xqueue"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

# Option "BaudRate" "9600"
# Option "SampleRate" "150"

# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"

# ChordMiddle is an option for some 3-button Logitech mice

# Option "ChordMiddle"

EndSection

# Some examples of extended input devices

# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

Identifier "My Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

HorizSync 31.5-64.3

# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

VertRefresh 50-90

vendorname "Typical Monitors"
modelname "1280x1024, 60Hz"
ModeLine "1280x1024 60Hz" 110 1280 1328 1512 1712 1024 1025 1028 1054
ModeLine "1280x1024 60Hz" 110 1280 1328 1512 1712 1024 1025 1028 1054
EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

Section "Device"
Identifier "Nvidia"
Driver "nvidia"
#VideoRam 4096
# Insert Clocks lines here if appropriate
vendorname "nvidia"
boardname "geforce 4200"
EndSection

# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "Nvidia"
Monitor "My Monitor"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.

# DefaultDepth 8
# DefaultDepth 16
DefaultDepth 16
# DefaultDepth 32

# "1024x768" is also a conservative usable default resolution. If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)

Subsection "Display"
Depth 8
Modes "1280x1024" "800x600" "640x480"
Virtual 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "800x600" "640x480"
Virtual 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "800x600" "640x480"
Virtual 0 0
EndSubsection
Subsection "Display"
Depth 32
Modes "1280x1024" "800x600" "640x480"
Virtual 0 0
EndSubsection

EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
Identifier "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.

Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"

EndSection


Section "InputDevice"

Identifier "Keyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "fr"
Driver "keyboard"

EndSection


Section "InputDevice"

Identifier "Mouse"

Option "Protocol" ""
Option "Device" "/dev/mouse"
Driver "mouse"
Option "Emulate3Buttons"
Option "ZAxisMapping" "4 5"
EndSection

il me semble bizarre
ps : je n'ai pas non plus de clavier azerty au demarrage de KDM.

merci

Bonjour

Salut,

Je n'arrive pas a avoir un clavier 105 touches en azerty sous xfce,
windowsmaker, mais je l'ai sous kde.

J'ai recherche avec google et j'ai modifie ou controle certains fichier
(XF86Config, profile) mais ca ne marche pas.

Ok, alors comment est-ce que tu lances XFCE ? via KDM ?
Alors, je te propose d'essayer qq chose : tu demarres en init 3 (mode
console) et tu lances XFCE via ton .xinitrc
Voici ce que tu dois mettre dedans :
# Xfce
xfce-mcs-manager
xfwm4 --daemon
xftaskbar4 &
xfdesktop &
exec xfce4-panel

Dis-nous si après ça tu n'as tjs pas ton clavier en azerty.

Voici ma config
PIII 600 512 Ram
Slackware 9.1 noyau 2.6.3 (ca le fesait deja avant le changement du
noyau)

Yeah Slackware ;-)

Anthony

Bonjour

Salut,

Je n'arrive pas a avoir un clavier 105 touches en azerty sous xfce,
windowsmaker, mais je l'ai sous kde.

J'ai recherche avec google et j'ai modifie ou controle certains fichier
(XF86Config, profile) mais ca ne marche pas.

Ok, alors comment est-ce que tu lances XFCE ? via KDM ?
Alors, je te propose d'essayer qq chose : tu demarres en init 3 (mode
console) et tu lances XFCE via ton .xinitrc
Voici ce que tu dois mettre dedans :
# Xfce
xfce-mcs-manager
xfwm4 --daemon
xftaskbar4 &
xfdesktop &
exec xfce4-panel

Dis-nous si après ça tu n'as tjs pas ton clavier en azerty.

Voici ma config
PIII 600 512 Ram
Slackware 9.1 noyau 2.6.3 (ca le fesait deja avant le changement du
noyau)

Yeah Slackware ;-)

Anthony


salut et merci pour les reponses

ça marche , j'ai commente les lignes de la premiere section du clavier
et j'ai garde que les dernieres (voir les autres messages ou il y a le
XF86Config )et tout est rentre dans l'ordre.

Merci encore a tous pour les reponses
@+ thierry

Le Tue, 25 May 2004 13:38:28 +0200, thierry a écrit :

voici mon XF86config a partir de la section < input devices>

Toutes les lignes qui commencent par # sont commentées, c'est comme si
elles n'étaient pas là. Il faut que tu enlèves les # devant les lignes


# Option "XkbModel" "pc104"

# Option "XkbLayout" "fr"

Et que tu remplaces pc104 par pc105.

--
entia non sont multiplicanda praeter necessitatem.
Guillaume d'Ockham.