Keyboard Layout Problems with OS X Mavericks on MacBook

My brother and I have a Early 2009 MacBook that received succesive updates on OS X over the past four years: it went from Leopard to Snow Leopard to Lion to Mountain Lion. But this year, we decided to upgrade it from a clean install of Mavericks.
It went fine, but... the keyboard is acting in a terrible way. The layout is bugged! The left shift key enters the "Y" letter, while return enters the "/" key... I've just tried everything to fix this resetting NVRAM and SMC, but nothing has worked.
Somebody else is having this problem? Could a software update fix it?

See if a Safe Mode boot helps...
Startup your Mac in Safe Mode
A Safe Mode boot takes much longer than a normal boot so be patient.
Once you are in Safe Mode, click Restart from the Apple () menu.

Similar Messages

Non-US keyboard layout problem with VNC

Hi everyone,
I've got an arch box at work running tigervnc through an ssh tunnel so that I can work from home when I need to.
Everything is great, as long as I'm using and ASCII keyboard layout.
When I switch layouts, the keystrokes just don't get through to the server.
Here's what I use to switch layouts:
setxkbmap -layout us,ru -option 'grp:alt_shift_toggle'
So I need to type in russian, and I hit alt-shift, as usual, and start typing, but nothing is echoed back to me. I can tell that the keystrokes are just not getting to the destination because if I'm at a terminal and I'm switched to the ru layout and I type something and hit enter, I just get a newline, as if there was nothing typed at all.
Any ideas?

Hi,
Why are the characters mixed up in the session?
This issue can occur if the keyboard language has been switched on the remote PC while running a remote desktop session. In the case you would like to switch to a different keyboard
language follow these instructions.
Important:
The remote PC selects the system language of the device running the remote desktop client and not the keyboard language. When switching the keyboard language on your device,
you need to manually switch the keyboard language on the remote PC.
1. Open settings on your device.
2. Tap General and then tap International.
3. Tap Language and select the language running on the remote PC.
4. Open the RD Client and connect to the remote PC and check if the Windows keyboard language matches the language that you selected.
Quote from
Remote Desktop Client on Mac: FAQ
Thanks.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Problem with Maps in Mavericks on Macbook pro

I just installed OS X 10.9 Mavericks on my Macbook pro 2010 mid model. Install processes were good with no problem.
After Install, I opend Maps application. I found my Map is not load whole map image. like this picture.
Can any one help me from this terrible situation?
Spec :
2010-Mid MBP 15''
2.66 GHz Intel Core i7
8GB RAM
500GB 5400RPM HDD

Fixed, for me.
Just changed the language order in preferences language & region.
Seems like maps has bad behaivor with some languages.
Maps was not ready for the world.

Problem with replies in Maverick's mail. Originating emails send fine. When replying to an email (various addresses) the reply is hung up and can not be sent. Option becomes put in draft, delete, etc. Any suggestions would be helpful

Problem with replies in Maverick's mail. Originating emails send fine. When replying to an email (various addresses) the reply is hung up and can not be sent. Option becomes put in draft, delete, etc. Any suggestions would be helpful. Mid 2013 iMac.

I don't know how rare this is. I went a week or so without a problem, and now it's starting to recur. Also, in some instances, an email will look unsent (remain in the outbox on the Treo), but it has been sent, and recipients are replying while I'm trying to figure out what is going on. Further, it will send the same email over and over during this madness.
This is a show stopper. If there isn't a software fix soon, I may chuck this phone in the garbage.
Post relates to: Treo 800w (Sprint)
UPDATE: The problem comes and goes. The next day, no changes to the treo, everything workeds. Now i'm suspecting the sprint server, and how it/the phone responds from failing to send while roaming. I've since turned off roaming, and haven't had a problem for several days.
Message Edited by slrichardson on 12-22-2008 01:12 PM

Anyone having a problem with iMovie in Mavericks v 10.9.3 ? when previewing the a slideshow the colors all disappear after the first image.

Anyone having a problem with iDVD in Mavericks 10.9.3? When previewing a slideshow all color is lost after the first image.

Is your problem with iMovie as the title suggests or with iDVD?

Problem with maps in Mavericks on iMac

I have a problem with my Maps on Mavericks.
I can open it just fine, no crash or whatever but the map itself just won't load, whatever mode it is on. Here is the screenshot of my Maps:
As you can see, it just stays blank all the time.
I'm also running Parallels 9 and don't know if that has something to do with problem.

Spent days trying various fixes, but this is the one that did it for me. Thanks!
livetowin
Re: Problem with maps in Mavericks on iMac
Dec 8, 2013 7:14 PM (in response to robin1943)
Try this
Since my date and time were incorrect and imessage was not working as well, I tried this
1. Go to system preferences and click date and time
2. Select date and time tab
3. Uncheck "set date and time automatically" and manually enter the correct time
4. Go to time zone tab and uncheck the box there too
5. Go back to date and time tab and now check the box "set date and time automatically"
6. Then check the box in time zone as well
Now open maps and see if it works!

Is Apple doing anything to fix the problem with displaylink in Mavericks?

I have been doing the Beta track for several years. Apple has been fairly good about ironing out the bugs before a release (as compared to Microsuck and other OS alternatives). But this problem with DisplayLink and Mavericks is about to kill me. I've been running multiple displays for several years and never had problems with prior OSX versions. My work computer (Macbook Pro) is still running Lion and works perfectly with DisplayLink and two 27" Samsung HD monitors. I would really love to get back to using the monitor setup with my Dev environment, however I can't even get a 2013 model Mavericks Macbook Pro to recognize that the DisplayLink device (IBM USB3.0 dock) is connected.
Once or twice I've gotten one monitor to show up after using the computer for a random amount of time. On that occasion, suddenly the main screen blinked and the second monitor came to life. I was reading webmail with Safari at the time and no other apps were running or had been started when it happened. This sort of thing isn't what I would classify as release-ready.
Every seed announcement I keep hoping for a fix, but after 3 since the Mav release, I'm beginning to lose hope. Anyone have info on how this might be made to work?
Thanks
David

DisplayLink also points fingers at Apple, which may be completely valid, but expecting Apple to put much effort into problems that only affect third-party hardware using an unsupported interface seems a bit of wishful thinking.
However, rumor sites indicate a focus on graphics in the next update : http://www.macrumors.com/2014/03/06/apple-seeds-first-os-x-10-9-3-build-to-devel opers/

Problems with OS X Mavericks?

Has anyone else had problems with OS X Mavericks? Since updating the system, my MacBook Pro has crashed (for the first time ever!) and I have continued problems with Finder and Mail (e.g. i cannot close down and have to force quit).

No issues so far on my 2012 Mac Mini but after using this new system for 2 days I find no improvement or features that I would use from ML version. Probably more trouble updating than it was worth.

I have a brand new hp officejet 6700 premium e-all-in-one printer but my macbook pro is not detecting the printer to even install it or make a print can some one tell me if it is a problem with the printer or the macbook pro?

can some one help me with the question ..

no not at all..it was just tested if it was being detected on a windows os..it did..i am doubting either it is a problem with the router or the macbook pro....but earlier it did connect well to a hp officejet pro 8600 e-all-in-one printer over a different network(at someone else's house)...

I have a problem with my Imessage at my macbook pro ,its says it can contact the server and i cant use it ,please solve me this problem

i have a problem with my Imessage at my macbook pro ,its says it can contact the server and i cant use it ,please solve me this problem

I am having the exact same problem with the iMessage on both my MacBook pro and my iphone4. It either says the username/password is incorrect or it can not contact the server. Facetime and iCloud works just fine with the same apple id and password. Somebody please help, I am beyond frustrated!

I have problems with my FacebookVideoCalling in my MacBook Air

I have problems with my FacebookVideoCalling in my MacBook Air.

Please see this already existing thread: Is anyone having trouble streaming music videos from iCloud? (Updated)

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)

[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)

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.)

Keyboard Layout Problems with OS X Mavericks on MacBook

Similar Messages

Maybe you are looking for