clavier qwerty en azerty sous slack Fermé

Question

bonjour voila j ai teste ca

xorgconf -textmode et jai teste les differentes langues
french alternative etc ...

en fait sous x c en qwerty et avant de lancer X c est en azerty

quelqu un peut m aider ?
merci

MX · Answer

man xf86config

gl · Answer

bash-2.05b# man xf86configNo manual entry for xf86configbash-2.05b#Je precise que je suis sous slack 10.0merci

philtrain · Answer

Bonjour,il faut éditer le fichier /etc/X11/XF86Config (ou si c'est xorg, /etc/X11/xorg.conf)Localiser la section InputDevice et changer l'option XkbLayout de "us" en "fr" ou "be" (selon que tu veux un clavier français ou belge)par ex:Section "InputDevice"  Driver       "Keyboard"  Identifier   "Keyboard[0]"  Option       "Protocol" "Standard"  Option       "XkbLayout" "us"     <------ changer en fr  Option       "XkbModel" "pc104"  Option       "XkbRules" "xfree86"EndSectiondevient :Section "InputDevice"  Driver       "Keyboard"  Identifier   "Keyboard[0]"  Option       "Protocol" "Standard"  Option       "XkbLayout" "be"      Option       "XkbModel" "pc104"  Option       "XkbRules" "xfree86"EndSectiona+

gl · Answer

Ah merci !

gl · Answer

ben en fait ca marche pas.J'ai remplacé en "be" et en "fr", ca ne change pas (et c'est xorg).Personne ne saurait ?

philtrain · Answer

Ne pas oublier le cas échéant de - décommenter les lignes (enlever le #)- redémarrer le serveura+

gl · Answer

bonsoir,le reel probleme est que la plupart des informations contenues dans  xorg.conf contient des #, meme les sections importantes, est ce normal ?je pourrai peut etre faire un copie coller de mon xorg et voir ce qui ne va pas avec vous.merci.

Utilisateur anonyme · Answer

oui fais ça.surtout mets-le entre balise < code >ce n'est pas un ragondin

gl · Answer

Voici comme convenu le xorg.conf de ma slack 10.0 : # File generated by xf86config. # # Copyright (c) 1999 by The XFree86 Project, Inc. # # Permission is hereby granted, free of charge, to any person obtaining a # copy of this software and associated documentation files (the "Software"), # to deal in the Software without restriction, including without limitation # the rights to use, copy, modify, merge, publish, distribute, sublicense, # and/or sell copies of the Software, and to permit persons to whom the # Software is furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in # all copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL # THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. # # Except as contained in this notice, the name of the XFree86 Project shall # not be used in advertising or otherwise to promote the sale, use or other # dealings in this Software without prior written authorization from the # XFree86 Project. # # ********************************************************************** # Refer to the XF86Config(4/5) man page for details about the format of # this file. # ********************************************************************** # NOTE: This is a NEW IMPROVED version of XF86Config-fbdev that uses the vesa # driver instead of the fbdev driver. Thanks to Kenneth Fanyo who pointed # this out to me. :) # This XF86Config file is designed for use with the VESA framebuffer. # This generic interface should work with nearly all video cards # (although not every card will support every resolution). # With the new driver, it should no longer be required to have frame buffer # support in the kernel, or to run it on the console. # # Enjoy! :) # -- volkerdi@slackware.com # # ********************************************************************** # Module section -- this section is used to specify # which dynamically loadable modules to load. # ********************************************************************** # Section "Module" # This loads the DBE extension module. Load "dbe" # Double buffer extension # This loads the miscellaneous extensions module, and disables # initialisation of the XFree86-DGA extension within that module. SubSection "extmod" Option "omit xfree86-dga" # don't initialise the DGA extension EndSubSection # This loads the font modules Load "type1" Load "freetype" Load "speedo" # This loads the GLX module Load "glx" EndSection # ********************************************************************** # Files section. This allows default font and rgb paths to be set # ********************************************************************** Section "Files" # The location of the RGB database. Note, this is the name of the # file minus the extension (like ".txt" or ".db"). There is normally # no need to change the default. RgbPath "/usr/X11R6/lib/X11/rgb" # Multiple FontPath entries are allowed (which are concatenated together), # as well as specifying multiple comma-separated entries in one FontPath # command (or a combination of both methods) # # If you don't have a floating point coprocessor and emacs, Mosaic or other # programs take long to start up, try moving the Type1 and Speedo directory # to the end of this list (or comment them out). # FontPath "/usr/X11R6/lib/X11/fonts/local/" FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/CID/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/" # ModulePath can be used to set a search path for the X server modules. # The default path is shown here. # ModulePath "/usr/X11R6/lib/modules" EndSection # ********************************************************************** # Server flags section. # ********************************************************************** Section "ServerFlags" # Uncomment this to cause a core dump at the spot where a signal is # received. This may leave the console in an unusable state, but may # provide a better stack trace in the core dump to aid in debugging # Option "NoTrapSignals" # Uncomment this to disable the VT switch sequence # (where n is 1 through 12). This allows clients to receive these key # events. # Option "DontVTSwitch" # Uncomment this to disable the server abort sequence # This allows clients to receive this key event. # Option "DontZap" # Uncomment this to disable the / mode switching # sequences. This allows clients to receive these key events. # Option "DontZoom" # Uncomment this to disable tuning with the xvidtune client. With # it the client can still run and fetch card and monitor attributes, # but it will not be allowed to change them. If it tries it will # receive a protocol error. # Option "DisableVidModeExtension" # Uncomment this to enable the use of a non-local xvidtune client. # Option "AllowNonLocalXvidtune" # Uncomment this to disable dynamically modifying the input device # (mouse and keyboard) settings. # Option "DisableModInDev" # Uncomment this to enable the use of a non-local client to # change the keyboard or mouse settings (currently only xset). # Option "AllowNonLocalModInDev" # Set the basic blanking screen saver timeout. # Option "blank time" "10" # 10 minutes # Set the DPMS timeouts. These are set here because they are global # rather than screen-specific. These settings alone don't enable DPMS. # It is enabled per-screen (or per-monitor), and even then only when # the driver supports it. # Option "standby time" "20" # Option "suspend time" "30" # Option "off time" "60" # On some platform the server needs to estimate the sizes of PCI # memory and pio ranges. This is done by assuming that PCI ranges # don't overlap. Some broken BIOSes tend to set ranges of inactive # devices wrong. Here one can adjust how aggressive the assumptions # should be. Default is 0. # Option "EstimateSizesAggresively" "0" EndSection # ********************************************************************** # Input devices # ********************************************************************** # ********************************************************************** # Core keyboard's InputDevice section # ********************************************************************** Section "InputDevice" Identifier "Keyboard1" 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" "de" # # or: # # Option "XkbLayout" "de" # 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 X.Org # # Option "XkbRules" "xorg" # Option "XkbModel" "pc101" # Option "XkbLayout" "us" # 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" "PS/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/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 - 50.0 # 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 40-90 EndSection # ********************************************************************** # Graphics device section # ********************************************************************** # Any number of graphics device sections may be present Section "Device" Identifier "VESA Framebuffer" Driver "vesa" #VideoRam 4096 # Insert Clocks lines here if appropriate 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 "VESA Framebuffer" 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 24 # 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 "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 16 Modes "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 24 Modes "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 32 Modes "1024x768" "800x600" "640x480" 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 Voyez vous un problemes ?

Utilisateur anonyme · Answer

ceci étant, tu devrais t'en tirer avec    Option "XkbRules"   "xorg"    Option "XkbModel"   "pc105"    Option "XkbLayout"  "fr-latin9"ce n'est pas un ragondin

gl · Answer

merci pour cela, mais pour tout dire, ca ne fonctionne pas.j'ai bien sur decommente ce qui donne :[...]#    Option     "XkbOptions"    "ctrl:swapcaps"# These are the default XKB settings for X.Org#    Option     "XkbRules"      "xorg"    Option     "XkbModel"      "pc101"    Option     "XkbLayout"     "fr-latin9"#    Option     "XkbVariant"    ""#    Option     "XkbOptions"    ""EndSection[...]C est cela ?Ou alors, je decommente tout mon xorg.conf qui commence avec des Option. etc...Le xorg.conf la haut est par defaut, installe sur mon laptop.merci bien.

gl · Answer

j'ai aussi teste avec pc105et en decommentant les lignes presentes dans mon precedent poste.

gl · Answer

noon ! j'ai pas tout decommente qd meme je suis pas totalement dingue.j'ai juste decommente 5 lignes, celles cite plus haut. je peux tenter de les ajouter, mais techniquement le resultat sera le meme.bon, je reregarde ca cette apres - midi, merci pour ces informations.

gl · Answer

une idée quelqu'un ?

philtrain · Answer

On trouve dans le fichier de configuration que tu as posté les lignes suivantes:# These are the default XKB settings for X.Org##    Option     "XkbRules"      "xorg"#    Option     "XkbModel"      "pc101"#    Option     "XkbLayout"     "us"#    Option     "XkbVariant"    ""#    Option     "XkbOptions"    ""Or tu devrais avoir quelque chose comme ceci:# These are the default XKB settings for X.Org#     Option "XkbRules" "xorg"      Option "XkbModel" "pc101"      Option "XkbLayout" "fr-latin9" # Option "XkbVariant" "" # Option "XkbOptions" "" Avec la bonne valeur pour l'option XkbModel selon ton type de clavier.L'option XkbLayout prend la valeur "fr" ou "fr-latin9".Une fois les changements effectués, il faut redémarrer le serveur pour que les changemenst soient pris en compte.a+

gl · Answer

c'est effectivement ce que j'ai teste hier.et pourtant....peut etre que le probleme est au niveau du Model, comment puis je savoir ?

philtrain · Answer

re,Pour un laptop, c'est souvent 101Le fichier xorg.conf que tu as posté n'est pas bon. Les lignes proposées par Hector et par moi-même doivent être décommentées. Ou alors , a vérifier, n'y aurait-il pas un autre fichier de configuration de X dans /etc/X11 ?On trouve parfois XF86Config, XF86Config-4, ...Chez moi xorg.conf est un lien symbolique qui pointe sur XF86Config !a+

gl · Answer

je vais verifier ça.

gl · Answer

oui un full.

gl · Answer

pour la reinstallation, c'est la 4eme lolet toujours le meme cas.

Utilisateur anonyme · Answer

tu as essayé de créer ton fichier avec xorgconf ? ça a donné quoi?ce n'est pas un ragondin

gl · Answer

J'ai tester Reiser. c'était ce qui était selectioné par defaut et on m'a dit que c'était bon.
sinon on m'a dit ext2, je testerai peut etre.

Sinon, c'est slackware 10.0 que j'ai acheté a 10 € avec le manuel contenant les 4 cd.

pour le xorg tu as raison je vais me lancer.
dès demain je formate et j'installe tout bien.

Je choisis ext2 ?
Je redemanderai de l'aide dans un autre topic, merci pour tout.
sur ce, a très bientot

et bonne soirée.

gl · Answer

Rajout :Mais trouvez-vous normal que le xorg.conf soit bourré de # ?Meme les sections qui paraissent plutot importantes sont commentés, y compris le clavier au tout début.

abdelhak · Answer

salut

si tu es sous X11 alors....
#emacs /etc/profile.d/lang.sh

tu auras au debut tout un baratin avec des ' # ',bref, des comments, jusque là, pas de suprises!
ensuite, tu modifies en rentrant ces lignes;

LC_CTYPE=ISO-8859-15
LANGUAGE=fr
LC_MESSAGES=fr
LC_ALL=fr_FR
LANG=fr
LESSCHARSET=latin9
#pour le ', ' en '.' du pavé numérique
LC_NUMERICS=C
export LC_CTYPE LANGUAGE LC_MESSAGES LC_ALL LANG LESSCHARSET LC_NUMERICS

Une fois que ton file est modifié, alors et seulement alors:

#localedef -i fr_FR -f ISO-8859-15 fr_FR

Voilà, tu tapes cela ma couille et tout doit bien se passer parce que si tu faits le truc standard genre rajouter l'OPTION "XkbLayout" dans /etc/X11/XF86Config etc etc

rikikus · Answer

Ca marche MERCIIIIIIIIIIIIIIIIIIIIIIII Beaucoup :) Avec Nano

Config : Soho Vector Linux 5.8

1. Terminal
2. su
3. Votre mot de passe
4. nano /etc/X11/xorg.conf
5. modifier le "us" en "fr" ou "be" selon ce que vous voulez
6. Controle + O, regardez bien quand même qu'il saggit bien du chemin /etc/X11/xorg.conf
7. Entrée
8. Reboot

A partir de celà, vous pouvez modifier pas mal de petites choses, mais des petites connaissances sont indispensables

Merci encore, je croyais que le package Fr n'existait pas sur ce Nux là !
:)

Clavier qwerty en azerty sous slack

25 réponses

Discussions similaires

Newsletters