Problems on keyboard layout

Hello, I'm a newbie in Mac world, and unfortunately I'm having some problems with the keyboard for brazilian layout. It just works like the american one, and I can't type the brazilian characters on the text. If I choose the portuguese, it works, but portuguese layout isn't so easy to use like the brazilian one. Can anybody help me??

ME TOO!!!!!!!
I called support and two other people with apple tried it on panther and tiger the board is wrong they suspect.........
I can't make many of the symbols I need currently--and some tyes look swedish!!!!
PLEASE PATCH THIS APPLE!!! I PURCHASED THE COMPUTER BECAUSE IT COULD DO BRAZILIAN!!! before OSX I was able to program my own keyboard and assign any key. Put this function back in if nothing else. THANKS!!

Similar Messages

Problems with keyboard layout after 10.7.1

Hi,
After install the 10.7.1, the computer do not recognize the keyboard layout in startup process (when ask for the password in order to open the encrypted volume), and I have to use the US Keyboard Layout to introduce the password.
The main problem is my keboard is in a Spanish ISO layout, so, I have to remember where the symbols are defined...
How can I change the keybard layout for the boot process???
Thanks in advance.
H.
P.S: After login, the keyboard layout is well defined...

Hi @ all,
same problem here. On my MacBook Air the keyboard layout at the login-screen (FileVault 2) changed to US after the Update to 10.7.1. After I tried to change this back to the German one, my MacBook does net accept any way to enter my password any more.
It seems that I have to reset my password with the key stored by Apple.
Do you know how to set the keyboard layout for FileVault 2, so that this doesn't happen again?
Thank you!
Greez,
Stefan

Safari changes my keyboard layout when on password field

Hi,
after upgrade to Safari 5, I got really strange problem.
I have two keyboard layout configured, U.S., which I use regulary, and Czech, to which I switch on rare occasions when I need to write something in my native language. I have configured keyboard shortcut Shift-Cmd-Space for switching between those layouts.
Now, the problem is that whenever I enter a password field on a web page form in Safari, it immediately switches to the Czech layout and disables the U.S. one, so I even can not switch back! The keyboard shortcut does not work and the "U.S." item in the keyboard indicator menu is grey.
This is extremely annoying. Does anyone have an idea what is causing it and how can I fix it?
Also, I think (but I'm not sure) that I have sometimes seen this before. But now (probably after Safari 5 installation) it happens on all the passwords fields I tried (even on pages I never visited before).
regards,
Bob
mid-2008 15" MacBook Pro, Snow Leopard, Safari 5, all available updates. In the Language & Text section of the preferences, I have following settings:
Language: First English, then Czech, then the rest.
Formats: Region: Custom (mostly czech with some tweaks)
Input Sources: Keyboard & Character Viewer checked, Czech-QWERTY checked, English checked. Selected "Use the same one in all documents", checked Show input menu in menu bar.

Problem solved! I have installed Keywurl some time ago (I really missed Firefox's bookmark keywords). After I upgraded to Safari 5, Keywurl said "Ooops, I'm not tested with Safari 5, disabling myself", so I did not suspected it. But out of deseperation, I tried to remove the plugin completely from the disk. And it worked! No more problems with keyboard layout in password field. Strange, but at least it works.
Bob

VNC into Mac and keyboard layout

Hi,
I'm trying to get keyboard layout mapping to work between the mac mini which is the VNC server and any remote VNC clients (linux, windows, mac). Tried ultravnc, tightvnc, realvnc clients. And 10.5.x built-in as well as Vine VNC servers. The mini has an Alphagrip keyboard with US+Finnish layouts. The client PCs have Finnish layout typically, also US or German.
Problem is that any pipe, tilde, @ etc "special" characters typed through the clients end up as umlauts or other characters in the VNC.
Any suggestions how I could make VNC work so that the VNC keyboard layout is always the client layout?
Thanks,
- Jan

Thanks for pointers!
Setting "US" in OSXvnc did not work with any local client-side layout, oddly not even EN/US local + EN/US remote with OSXvnc use either "US" or "Current Layout".
But the following nearly works. Client Finnish keyboard, server Mac Mini Finnish keyboard, for the ultraVNC client change Finnish/FI to US winxp locale (using XP's/Vista's Language Bar), in OSXvnc choose "Current Layout" and set global Mac layout to Finnish.
I.e. have same keyboard at both ends but set the "wrong" US locale in WinXP for the ultraVNC client.
Now nearly everything works (with this laptop and server) - all umlauts and special characters. The only and unfortunately also critical problem is that the key "|" does not "work", it outputs "'*" instead. On the Mac the key is on the left of spacebar, on the client on the right. I don't see how this alone could change the scancodes. But apparently it does. Because it does not work.
Is there not some UTF / Unicode version of VNC for all OS X, Windows, Linux?
Or some VNC that would handle keyboard layouts smartly, transparent to the user?
Another option, IME with RDP (MS Terminal Services, rdesktop) there is no problem with keyboard layouts. Perhaps you guys know some RDP server for OS X?

[SOLVED] Keyboard layout switching

Hello,
I have a problem with keyboard layout switching key.
Just notice it not working anymore...
here is my key setting in xorg.conf
Section "InputDevice"
Identifier "Keyboard"
Driver "kbd"
Option "XkbLayout" "us,th"
Option "XkbOptions" "grp:alt_shift_toggle"
EndSectionp
Last edited by xcession (2008-11-05 13:23:57)

bender02 wrote:
xcession wrote:EndSectionp
extra p?
Seriously though, it looks fine to me. There's a wiki article http://wiki.archlinux.org/index.php/Con … youts_in_X
I'd try adding
Option "XkbRules" "xorg"
although that could be automatic.
Oops! it's my typo when posting that post...
Added Option "XkbRules" "xorg"
but still doesn't work...:(

Problem with Mail and customized keyboard layout

I have created a customized keyboard layout in XML, it loads and works perfectly with all applications except Apple Mail. I noticed on a googlegroup that somebody has the same problem. How can I submit this Mail bug to Apple?

download and run Find Any File to search for "Antidote".
FAF can search areas that Spotlight can't like invisible folders, system folders and packages. Any file you find will be in the search results window and can be dragged to the Desktop and then to the Trash bin.
OT

Keyboard layout problems in Gnome

I'm not sure if it was a recent upgrade that did it or not, but in gnome my keyboard layout is only half right. I checked the keyboard manager in the gnome menu and it was set to Generic 105 key (INTEL).
In xorg.conf the keyboard is listed as pc105. In KDE the keyboard works normally.

bgodea wrote:I changed the Gnome keyboard layout to "104 key PC" and also tried changing my xorg.conf, but I still have the same problem. In non-graphical and KDE it works fine
You also have to setup a valid layout for this kind of keyboard. That is done in the same dialog field. Then, what do you mean with "tried"? First off, if Gnome and X disagree about keyboard layout, Gnome complains loudly. Thus KDE is unilaterally setting the layout to something it likes. Check your Kconfig to find out what it is. Then find the section named InputDevice in /etc/X11/xorg.conf that looks something like this:
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "us"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
EndSection
Change it to resemble this example, if it doesn't. Check if your ServerLayout actually uses this InputDevice. Finally, is there anything else we should know about your keyboard? Do you run XGL/AIGLX?
Last edited by Captain Spaulding (2007-04-03 16:50:46)

Dwm and non-english keyboard layouts problem

Hi all,
I am using dwm 5.5. I'm Greek so I change between keyboard layouts all the time,
see the relevant xorg.conf section:
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us,gr"
Option "XkbVariant" ","
Option "XkbOptions" "grp:alt_shift_toggle,grp_led:scroll"
EndSection
Now the thing is that whenever I switch to Greek (by pressing Alt+Shift) the
dwm tags (1,2,...,9) are not clickable (keyboard shortcuts do work
though, so it's not a very big problem).
Do you have any ideas about how to fix that behavior? I'd go to the dwm irc
channel and ask them, but I'll be a "newbie asking stupid questions" so I
preferred to ask here
Thanks in advance
Last edited by geo909 (2010-01-08 17:23:29)

thayer wrote:Your best bet would be to post your problem to the dwm mailing list:
[email protected]
Will do...
Thanks!

[E17] lock and keyboard layout problems when suspend

Hello,
I just installed E17 on my Dell Vostro laptop. The main problem I have is related to the suspend mode.
In settings > screen > screen lock, I enabled the option "lock on suspend" and the keyboard layout is selected to "be (default, basic)" (I have a belgian keyboard).
When I use the menu system > suspend, the screen is locked. But when I suspend my laptop by closing the lid (I see the power light indicator blinking on the side, so it's suspended) the screen is not locked when I open it.
Also related to the suspend mode. The layout is set to belgian (in the screen config as explained above but also in vconsole.conf and in /etc/X11/xorg.conf.d/10-keyboard.conf). When I put the luks decryption key or when E17 starts at boot, I have the right layout. However when I resume the laptop after being suspended, the layout is switched to qwerty (en_us I guess).
Any idea why ?
Thank you
PS: this problem is maybe more related to E17 than to Archlinux but I haven't found any forum about enlightenment. If you think I have better chances somewhere else, let me know.

I was having problems with E17 after a fresh install (mixer problem, key bindings, etc), and I fixed it by deleting the configuration files at
~/.e
as the wiki says.

[SOLVED] Keyboard layout problems

Hi community,
I fresh installed arch linux and I rly like it. After playing a little around and installing the awesome wm I can't set the croatian keyboard layout.
My xorg.config file:
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "logicd"
Option "XkbLayout" "hr"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Arnos Instruments F-417"
HorizSync 24.0 - 80.0
VertRefresh 49.0 - 75.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 6600 GT"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "1"
Option "TwinViewXineramaInfoOrder" "DFP-0"
Option "metamodes" "CRT: nvidia-auto-select +1920+0, DFP: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
My Xorg.0.log file:
[ 2186.778]
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[ 2186.778]
X.Org X Server 1.8.1.902 (1.8.2 RC 2)
Release Date: 2010-06-21
[ 2186.778] X Protocol Version 11, Revision 0
[ 2186.778] Build Operating System: Linux 2.6.34-ARCH x86_64
[ 2186.778] Current Operating System: Linux arch 2.6.34-ARCH #1 SMP PREEMPT Mon Jul 5 22:12:11 CEST 2010 x86_64
[ 2186.778] Kernel command line: root=/dev/sda5 ro
[ 2186.778] Build Date: 21 June 2010 12:01:49PM
[ 2186.778]
[ 2186.779] Current version of pixman: 0.18.2
[ 2186.779] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 2186.779] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 2186.779] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jul 22 13:23:50 2010
[ 2186.779] (==) Using config file: "/etc/X11/xorg.conf"
[ 2186.779] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 2186.779] (==) ServerLayout "Layout0"
[ 2186.779] (**) |-->Screen "Screen0" (0)
[ 2186.779] (**) | |-->Monitor "Monitor0"
[ 2186.779] (**) | |-->Device "Device0"
[ 2186.779] (**) |-->Input Device "Keyboard0"
[ 2186.779] (**) |-->Input Device "Mouse0"
[ 2186.780] (**) Option "Xinerama" "0"
[ 2186.780] (==) Automatically adding devices
[ 2186.780] (==) Automatically enabling devices
[ 2186.780] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 2186.780] Entry deleted from font path.
[ 2186.780] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 2186.780] Entry deleted from font path.
[ 2186.780] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 2186.780] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 2186.780] (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 2186.780] (WW) Disabling Keyboard0
[ 2186.780] (WW) Disabling Mouse0
[ 2186.780] (II) Loader magic: 0x7ce880
[ 2186.780] (II) Module ABI versions:
[ 2186.780] X.Org ANSI C Emulation: 0.4
[ 2186.780] X.Org Video Driver: 7.0
[ 2186.780] X.Org XInput driver : 9.0
[ 2186.780] X.Org Server Extension : 3.0
[ 2186.786] (--) PCI:*(0:1:0:0) 10de:00f1:0000:0000 nVidia Corporation NV43 [GeForce 6600 GT] rev 162, Mem @ 0xf8000000/16777216, 0xe0000000/268435456, 0xf9000000/16777216, BIOS @ 0x????????/131072
[ 2186.787] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 2186.787] (II) LoadModule: "extmod"
[ 2186.787] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 2186.787] (II) Module extmod: vendor="X.Org Foundation"
[ 2186.787] compiled for 1.8.1.902, module version = 1.0.0
[ 2186.787] Module class: X.Org Server Extension
[ 2186.787] ABI class: X.Org Server Extension, version 3.0
[ 2186.787] (II) Loading extension MIT-SCREEN-SAVER
[ 2186.787] (II) Loading extension XFree86-VidModeExtension
[ 2186.787] (II) Loading extension XFree86-DGA
[ 2186.787] (II) Loading extension DPMS
[ 2186.787] (II) Loading extension XVideo
[ 2186.787] (II) Loading extension XVideo-MotionCompensation
[ 2186.787] (II) Loading extension X-Resource
[ 2186.787] (II) LoadModule: "dbe"
[ 2186.787] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 2186.787] (II) Module dbe: vendor="X.Org Foundation"
[ 2186.787] compiled for 1.8.1.902, module version = 1.0.0
[ 2186.788] Module class: X.Org Server Extension
[ 2186.788] ABI class: X.Org Server Extension, version 3.0
[ 2186.788] (II) Loading extension DOUBLE-BUFFER
[ 2186.788] (II) LoadModule: "glx"
[ 2186.788] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 2186.813] (II) Module glx: vendor="NVIDIA Corporation"
[ 2186.813] compiled for 4.0.2, module version = 1.0.0
[ 2186.813] Module class: X.Org Server Extension
[ 2186.813] (II) NVIDIA GLX Module 256.35 Wed Jun 16 19:10:31 PDT 2010
[ 2186.813] (II) Loading extension GLX
[ 2186.813] (II) LoadModule: "record"
[ 2186.814] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 2186.814] (II) Module record: vendor="X.Org Foundation"
[ 2186.814] compiled for 1.8.1.902, module version = 1.13.0
[ 2186.814] Module class: X.Org Server Extension
[ 2186.814] ABI class: X.Org Server Extension, version 3.0
[ 2186.814] (II) Loading extension RECORD
[ 2186.814] (II) LoadModule: "dri"
[ 2186.814] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 2186.814] (II) Module dri: vendor="X.Org Foundation"
[ 2186.814] compiled for 1.8.1.902, module version = 1.0.0
[ 2186.814] ABI class: X.Org Server Extension, version 3.0
[ 2186.814] (II) Loading extension XFree86-DRI
[ 2186.814] (II) LoadModule: "dri2"
[ 2186.814] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 2186.814] (II) Module dri2: vendor="X.Org Foundation"
[ 2186.814] compiled for 1.8.1.902, module version = 1.2.0
[ 2186.815] ABI class: X.Org Server Extension, version 3.0
[ 2186.815] (II) Loading extension DRI2
[ 2186.815] (II) LoadModule: "nvidia"
[ 2186.815] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 2186.816] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 2186.816] compiled for 4.0.2, module version = 1.0.0
[ 2186.816] Module class: X.Org Video Driver
[ 2186.816] (II) NVIDIA dlloader X Driver 256.35 Wed Jun 16 18:45:02 PDT 2010
[ 2186.816] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 2186.816] (++) using VT number 7
[ 2186.820] (II) Primary Device is: PCI 01@00:00:0
[ 2186.820] (II) Loading sub module "fb"
[ 2186.820] (II) LoadModule: "fb"
[ 2186.820] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 2186.821] (II) Module fb: vendor="X.Org Foundation"
[ 2186.821] compiled for 1.8.1.902, module version = 1.0.0
[ 2186.821] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2186.821] (II) Loading sub module "wfb"
[ 2186.821] (II) LoadModule: "wfb"
[ 2186.821] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 2186.821] (II) Module wfb: vendor="X.Org Foundation"
[ 2186.821] compiled for 1.8.1.902, module version = 1.0.0
[ 2186.821] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2186.821] (II) Loading sub module "ramdac"
[ 2186.821] (II) LoadModule: "ramdac"
[ 2186.821] (II) Module "ramdac" already built-in
[ 2186.821] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 2186.821] (==) NVIDIA(0): RGB weight 888
[ 2186.821] (==) NVIDIA(0): Default visual is TrueColor
[ 2186.821] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 2186.821] (**) NVIDIA(0): Option "TwinView" "1"
[ 2186.822] (**) NVIDIA(0): Option "MetaModes" "CRT: nvidia-auto-select +1920+0, DFP: nvidia-auto-select +0+0"
[ 2186.822] (**) NVIDIA(0): Option "TwinViewXineramaInfoOrder" "DFP-0"
[ 2186.822] (**) NVIDIA(0): Enabling RENDER acceleration
[ 2186.822] (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
[ 2186.822] (II) NVIDIA(0): enabled.
[ 2188.363] (II) NVIDIA(0): NVIDIA GPU GeForce 6600 GT (NV43) at PCI:1:0:0 (GPU-0)
[ 2188.363] (--) NVIDIA(0): Memory: 131072 kBytes
[ 2188.363] (--) NVIDIA(0): VideoBIOS: 05.43.02.39.00
[ 2188.363] (II) NVIDIA(0): Detected AGP rate: 8X
[ 2188.363] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 2188.363] (--) NVIDIA(0): Connected display device(s) on GeForce 6600 GT at PCI:1:0:0:
[ 2188.363] (--) NVIDIA(0): Arnos Instruments F-417 (CRT-0)
[ 2188.363] (--) NVIDIA(0): ViewSonic VX2433wm (DFP-0)
[ 2188.363] (--) NVIDIA(0): Arnos Instruments F-417 (CRT-0): 400.0 MHz maximum pixel
[ 2188.363] (--) NVIDIA(0): clock
[ 2188.363] (--) NVIDIA(0): ViewSonic VX2433wm (DFP-0): 155.0 MHz maximum pixel clock
[ 2188.363] (--) NVIDIA(0): ViewSonic VX2433wm (DFP-0): Internal Single Link TMDS
[ 2188.363] (**) NVIDIA(0): TwinView enabled
[ 2188.363] (II) NVIDIA(0): Display Devices found referenced in MetaMode: CRT-0, DFP-0
[ 2188.364] (II) NVIDIA(0): Assigned Display Devices: CRT-0, DFP-0
[ 2188.364] (II) NVIDIA(0): Validated modes:
[ 2188.364] (II) NVIDIA(0):
[ 2188.364] (II) NVIDIA(0): "CRT:nvidia-auto-select+1920+0,DFP:nvidia-auto-select+0+0"
[ 2188.364] (II) NVIDIA(0): Virtual screen size determined to be 3200 x 1080
[ 2188.364] (--) NVIDIA(0): DPI set to (95, 96); computed from "UseEdidDpi" X config
[ 2188.364] (--) NVIDIA(0): option
[ 2188.364] (==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
[ 2188.364] (--) Depth 24 pixmap format is 32 bpp
[ 2188.365] (II) NVIDIA(0): Initialized AGP GART.
[ 2188.373] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 2188.373] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 2188.373] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 2188.373] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 2188.373] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 2188.373] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 2188.373] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 2188.373] (II) NVIDIA(0): Config Options in the README.
[ 2188.373] (II) NVIDIA(0): Setting mode
[ 2188.373] (II) NVIDIA(0): "CRT:nvidia-auto-select+1920+0,DFP:nvidia-auto-select+0+0"
[ 2188.613] (II) Loading extension NV-GLX
[ 2188.657] (II) NVIDIA(0): Initialized OpenGL Acceleration
[ 2188.659] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 2188.659] (II) NVIDIA(0): Initialized X Rendering Acceleration
[ 2188.659] (==) NVIDIA(0): Backing store disabled
[ 2188.659] (==) NVIDIA(0): Silken mouse enabled
[ 2188.660] (**) NVIDIA(0): DPMS enabled
[ 2188.660] (II) Loading extension NV-CONTROL
[ 2188.661] (II) Loading extension XINERAMA
[ 2188.661] (II) Loading sub module "dri2"
[ 2188.661] (II) LoadModule: "dri2"
[ 2188.661] (II) Reloading /usr/lib/xorg/modules/extensions/libdri2.so
[ 2188.661] (II) NVIDIA(0): [DRI2] Setup complete
[ 2188.661] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 2188.661] (==) RandR enabled
[ 2188.661] (II) Initializing built-in extension Generic Event Extension
[ 2188.661] (II) Initializing built-in extension SHAPE
[ 2188.661] (II) Initializing built-in extension MIT-SHM
[ 2188.661] (II) Initializing built-in extension XInputExtension
[ 2188.661] (II) Initializing built-in extension XTEST
[ 2188.661] (II) Initializing built-in extension BIG-REQUESTS
[ 2188.661] (II) Initializing built-in extension SYNC
[ 2188.661] (II) Initializing built-in extension XKEYBOARD
[ 2188.661] (II) Initializing built-in extension XC-MISC
[ 2188.661] (II) Initializing built-in extension SECURITY
[ 2188.661] (II) Initializing built-in extension XINERAMA
[ 2188.661] (II) Initializing built-in extension XFIXES
[ 2188.661] (II) Initializing built-in extension RENDER
[ 2188.661] (II) Initializing built-in extension RANDR
[ 2188.661] (II) Initializing built-in extension COMPOSITE
[ 2188.661] (II) Initializing built-in extension DAMAGE
[ 2188.664] (II) Initializing extension GLX
[ 2188.842] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 2188.842] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2188.842] (II) LoadModule: "evdev"
[ 2188.842] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 2188.842] (II) Module evdev: vendor="X.Org Foundation"
[ 2188.842] compiled for 1.8.0, module version = 2.4.0
[ 2188.842] Module class: X.Org XInput Driver
[ 2188.842] ABI class: X.Org XInput driver, version 9.0
[ 2188.842] (**) Power Button: always reports core events
[ 2188.842] (**) Power Button: Device: "/dev/input/event2"
[ 2188.842] (II) Power Button: Found keys
[ 2188.842] (II) Power Button: Configuring as keyboard
[ 2188.842] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 2188.842] (**) Option "xkb_rules" "evdev"
[ 2188.843] (**) Option "xkb_model" "evdev"
[ 2188.843] (**) Option "xkb_layout" "us"
[ 2188.883] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 2188.883] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2188.883] (**) Power Button: always reports core events
[ 2188.883] (**) Power Button: Device: "/dev/input/event1"
[ 2188.883] (II) Power Button: Found keys
[ 2188.883] (II) Power Button: Configuring as keyboard
[ 2188.883] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 2188.883] (**) Option "xkb_rules" "evdev"
[ 2188.883] (**) Option "xkb_model" "evdev"
[ 2188.883] (**) Option "xkb_layout" "us"
[ 2188.887] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/event3)
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "evdev pointer catchall"
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: always reports core events
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: Device: "/dev/input/event3"
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Found 3 mouse buttons
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Found scroll wheel(s)
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Found relative axes
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Found x and y relative axes
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Configuring as mouse
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: YAxisMapping: buttons 4 and 5
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2188.887] (II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical Mouse" (type: MOUSE)
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: (accel) keeping acceleration scheme 1
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration profile 0
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration factor: 2.000
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration threshold: 4
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: initialized for relative axes.
[ 2188.887] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/mouse0)
[ 2188.887] (II) No input driver/identifier specified (ignoring)
[ 2188.888] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event4)
[ 2188.888] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2188.888] (**) Logitech USB Multimedia Keyboard: always reports core events
[ 2188.888] (**) Logitech USB Multimedia Keyboard: Device: "/dev/input/event4"
[ 2188.888] (II) Logitech USB Multimedia Keyboard: Found keys
[ 2188.888] (II) Logitech USB Multimedia Keyboard: Configuring as keyboard
[ 2188.888] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD)
[ 2188.888] (**) Option "xkb_rules" "evdev"
[ 2188.888] (**) Option "xkb_model" "evdev"
[ 2188.888] (**) Option "xkb_layout" "us"
[ 2188.888] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event5)
[ 2188.889] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2188.889] (**) Logitech USB Multimedia Keyboard: always reports core events
[ 2188.889] (**) Logitech USB Multimedia Keyboard: Device: "/dev/input/event5"
[ 2188.889] (II) Logitech USB Multimedia Keyboard: Found keys
[ 2188.889] (II) Logitech USB Multimedia Keyboard: Configuring as keyboard
[ 2188.889] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD)
[ 2188.889] (**) Option "xkb_rules" "evdev"
[ 2188.889] (**) Option "xkb_model" "evdev"
[ 2188.889] (**) Option "xkb_layout" "us"
[ 2188.891] (II) config/udev: Adding input device PC Speaker (/dev/input/event0)
[ 2188.891] (II) No input driver/identifier specified (ignoring)
Xorg.0.log important (I think):
[ 2188.888] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event4)
[ 2188.888] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2188.888] (**) Logitech USB Multimedia Keyboard: always reports core events
[ 2188.888] (**) Logitech USB Multimedia Keyboard: Device: "/dev/input/event4"
[ 2188.888] (II) Logitech USB Multimedia Keyboard: Found keys
[ 2188.888] (II) Logitech USB Multimedia Keyboard: Configuring as keyboard
[ 2188.888] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD)
[ 2188.888] (**) Option "xkb_rules" "evdev"
[ 2188.888] (**) Option "xkb_model" "evdev"
[ 2188.888] (**) Option "xkb_layout" "us"
[ 2188.888] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event5)
[ 2188.889] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2188.889] (**) Logitech USB Multimedia Keyboard: always reports core events
[ 2188.889] (**) Logitech USB Multimedia Keyboard: Device: "/dev/input/event5"
[ 2188.889] (II) Logitech USB Multimedia Keyboard: Found keys
[ 2188.889] (II) Logitech USB Multimedia Keyboard: Configuring as keyboard
[ 2188.889] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD)
[ 2188.889] (**) Option "xkb_rules" "evdev"
[ 2188.889] (**) Option "xkb_model" "evdev"
[ 2188.889] (**) Option "xkb_layout" "us"
Why is he adding the keyboard 2 times, and why "xkb_layout" "us"? I need hr (croatian).
My first post Sorry, for the bad english.
Last edited by b3no (2010-07-22 23:45:29)

[ 2186.780] (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
Add this
Section "ServerFlags"
Option "AllowEmptyInput" "no"
EndSection
EditL If the above didn't help, read this http://wiki.archlinux.org/index.php/Xor … d_settings
Last edited by karol (2010-07-22 12:06:04)

Two problems with setting up arch. Keyboard layout and wifi card.

Hi guys.
I have installed arch on my old laptop (LG le express) and I have two problems.
1. I wasn't able to create a Hebrew keyboard layout.
2. I don't know how to install my wifi card. (Ralink 2500).
as for one, I changed my xorg.conf to this:
section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "Xkbmodel" "pc105"
Option "XkbLayout" "us,il"
Option "KkbOption" "grep:switch,grp:alt_shift_toggel,grp_led:caps"
EndSection
but it didn't work.
As for 2, I have found this:
https://wiki.archlinux.org/index.php/Us … eta_driver
But I can't find how to install rt2x00
Thanks

If you edit the first post you can change the title, prepend it with [solved] (once all issues are actually solved). Also if you can post your working solution then it will be useful for others having similar difficulties. Please read the following links.
Mark threads as [solved]
Forum etiquette
As for your wireless issue, which tool are you using? A quick google around seems to suggest that netcfg in combination with wpa supplicant can connect to LEAP encrypted networks, eg this thread. Are you also aware that there are graphical tools to do this for you that you may find easier, such as wicd?
Last edited by quigybo (2010-11-12 01:56:01)

Keyboard layout problem at the login screen

Hi there!
I'm having a huge problem at the login screen just after installing OS X Lion 10.7. It seems like the keyboard layout has changed, and I need to enter some numbers in my password. I can't find the digit 9, and I really don't know if the other numbers are in the right place either. Maybe it's changed to a us layout.. What to do?

stoneheart,
the numbers are in the same position on a US English keyboard as they are on a Norwegian keyboard.
If you select the Users & Groups pane of System Preferences, and select its Login Options, do you have the “Show Input menu in login window” checkbox checked? (That’s where the checkbox’s location is in Mavericks; I don’t have Lion, so I don’t know if it’s in the same location there.)

E70 Keyboard layout problems

I have a brand-new E70 bought from Expansys a week ago. I have the same problem reported by other here regarding incorrect keyboard layout (e.g. "(" key produces ")" and "/" produces ","). I have not upgraded the firmware, this is the way the phone was shipped.
I haven't found any solution in this forum or on the web yet. Any advice is appreciated. Thanks,
-- Terrence

bgodea wrote:I changed the Gnome keyboard layout to "104 key PC" and also tried changing my xorg.conf, but I still have the same problem. In non-graphical and KDE it works fine
You also have to setup a valid layout for this kind of keyboard. That is done in the same dialog field. Then, what do you mean with "tried"? First off, if Gnome and X disagree about keyboard layout, Gnome complains loudly. Thus KDE is unilaterally setting the layout to something it likes. Check your Kconfig to find out what it is. Then find the section named InputDevice in /etc/X11/xorg.conf that looks something like this:
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "us"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
EndSection
Change it to resemble this example, if it doesn't. Check if your ServerLayout actually uses this InputDevice. Finally, is there anything else we should know about your keyboard? Do you run XGL/AIGLX?
Last edited by Captain Spaulding (2007-04-03 16:50:46)

Hotplugging Keyboard Layout Switching Problem

With a recent update, my keyboard configuration got a bit hosed. The super key stopped working, I couldn't use shifts to swap keyboard layouts, and ctrl/caps swap reverted back. Instead of troubleshooting that, I decided to give hotplugging a try. I disabled the keyboard configuration in xong.conf and enabled hotplugging.
Everything is working fine with one exception. If I list more than one keyboard layout in the .fdi, the keyboard reverts back to 'us'. As far as I can tell (and other posts have verified this) this is pretty close to copy/paste from xorg.conf. If I use just a single layout, that layout works.
Any advice?
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="info.capabilities" contains="input.keymap">
<append key="info.callouts.add" type="strlist">hal-setup-keymap</append>
</match>
<match key="info.capabilities" contains="input.keys">
<merge key="input.xkb.rules" type="string">base</merge>

<merge key="input.xkb.model" type="string">keyboard</merge>
<match key="/org/freedesktop/Hal/devices/computer:system.kernel.name"
string="Linux">
<merge key="input.xkb.model" type="string">evdev</merge>
</match>
<merge key="input.xkb.layout" type="string">dvorak,us</merge>
<merge key="input.xkb.variant" type="string" />
<merge key="input.xkb.options" type="string">grp:shifts_toggle,ctrl:swapcaps</merge>
</match>
</device>
</deviceinfo>
Last edited by elegua (2009-02-14 15:20:28)

elegua wrote:
Of course I get it figured out a little bit after asking.
It seems that the update killed the ability to use dvorak layout with anything else in setxkbmap. The following works for me now.
<merge key="input.xkb.layout" type="string">us,us</merge>
<merge key="input.xkb.variant" type="string">dvorak,basic</merge>
elegua, where did you ask your questions? I've got a very similar problem, tried this (pure guesswork):
<merge key="input.xkb.layout" type="string">us,ru</merge>
<merge key="input.xkb.variant" type="string">basic,winkeys</merge>
But it won't wash ...

Keyboard layout problem

My wife has an old iBook running Mac OS X Tiger and it's been working just fine. Never any trouble at all with this sturdy old thing but today, for some odd reason, the keyboard layout got messed up out of nowhere. We're Swedish and need the Swedish layout ( åäö ) but it suddenly stopped working. The layout has changed and the @-character is now accessible while pressing Shift+2 instead of Alt+2. I have no idea why this happened and I have no clue as to how to change/restore the default layout. I've looked around in the International preference pane but nothing I did there changed a thing. Anyone else bumped into this particular problem?

Forget this question, I found out what was wrong. My father-in-law ( who isn't too good at computers ) changed the layout by mistake by clicking the little flag and so switched the layout from Swedish Pro to US English. Problem solved.

Problems on keyboard layout

Similar Messages

Maybe you are looking for