Keyboard problems on Gnome login screen

I just installed my system, and im going through a strange problem: My keyboard is spanish, and i set everything so the spanish locales are used: I configured gnome to use spanish keyboard and so on.... but, when i am in the gnome login prompt, i dont have the spanish keyboard enabled..... how can i change this?
Thanks
Last edited by Xi0N (2009-08-09 22:12:26)

Vivo en Barakaldo, donde es la Euskal Encounter, llevo un par de años sin ir: No será por falta de ganas....
I think is the way gdm is handled: Before, i could set the language to spanish via the xorg configuration file, but now, since i am using the free ati drivers, and by default, it does not use any xorg.conf file, i cannot use this solution i found some time ago:
http://bbs.archlinux.org/viewtopic.php? … 02#p532202
Maybe it's useful for you..........
Any more ideas?

Similar Messages

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

Installed Xfce but get Gnome login screen

I installed Xfce (only) but when booting up I get a Gnome login screen. Why? Is there a way to make it a Xfce login screen?

..because you have installed GDM.
See this link to learn about other alternatives.

Keyboard locked at the login screen

Hey all,
i have a problem with my macbook pro (late 2010), since updated from Maverick to Yosemite 10.10 and few days later to 10.10.1
i while using "normally" surfing, emailing has crashed my MAIL and few moments later the SAFARI. Thinking a restart always can
help i did it. But after the restart at the login screen the keyboard is (b)locked (i can moving the mouse cursor) but i can't type in any
in the password field. (by the way, i can't not open the screen keyboard)
If i go to the guest account, there i haven't password (because never used this account) there is working the keyboard. But i haven't
any rights to change something at the system. Please, anyone can help me, and sorry for my bad english. Any solution without lost
all my documents.
Thank you very much.
Daniel

Then you are not at the initial login screen - you are waking up the mac from having put the computer or display to sleep due to inactivity.
You are already logged in. are you certain you're entering the correct password?
Do you have another computer on the same network that you could try and login to your Mac via "ssh" from this other computer. If you do, login from the other computer in a terminal type window and "ssh username@IP_Address_of_Mac" and see if that helps (substitute username and ip address of the mac for the user and IP address of the mac). You can then do a "sudo restart" and try the safe boot and reboot. This assumes you had "Remote Logins" enabled in the Sharing System Preferences though so it may not work depending on how that is set now.
So you don't see any dots appear in the password field as you type - do you? Are you sure the Caps-Lock key is not active (your password is case sensitive so if the CapsLock is on accidentally then you will never be able to login this way until you turn it off). If the CapsLock LED is not working you have no way of knowing if it's on or off, so if one attempt at loggging in does not work (and you see dots appear in the password field as you type) then press the CapsLock key once and try again.
If you don't see any "dots" appear in the password box
Good luck...
ps - in any event you can always press and hold down the power button for about 5 seconds to force a shutdown but this can cause problems and not recommended except as a last resort.

[SOLVED] GNOME login screen freezes after 3 seconds

Hello,
today I installed Arch-Linux the first time. I had some issues during the installation (following https://wiki.archlinux.de/title/Anleitu … Einsteiger (its the german version, seems to differ a little from the english version)), but everything went good until I installed GNOME. Now the login screen freezes everytime after quite exactly 3 seconds, unless I press [strg]+[alt]+[f2] fast enough to switch in tty2. Then the screen will only freeze when I switch back to tty1. Once the screen is frozen, I can't switch to tty2 anymore.
I think the problem has something to do with my nvidia hybrid graphic system. During the installation I installed the packages bumblebee, bbswitch and primus, but uninstalled them because I thought they could be the problem. But although I uninstalled the packages, the "Stamina-Mode" status led is turned on after the system has started and the "Speed-Mode" status led not. I think that's a little bit strange, because I can't imagine which process is controlling these leds.
So I ran just
pacman -S xorg-drivers
and I had to create the xinitrc-file (because I could not find this file in /etc/skel). Now the default GUI appeared after I ran
startx
(I saw some windows and a clock). After that I installed gnome, changed the xinitrc-file in my userhome and got the freeze after a reboot.
I don't know if it has anything to do with my problem, but I get the following error-messages everytime I boot:
[drm:ibx_irq_handler] *ERROR* PCH transcoder A FIFO underrun
[drm:intel_dp_start_link_train] *ERROR* too many full retries, give up
[drm:ilk_display_irq_handler] *ERROR* Pipe A FIFO underrun
interl ips 0000:00:1f.6: thermal reporting for required devices not enabled, aborting
Hoeman
P.S.: Because I'm a total beginner at linux I probably missed the most important informations, but I can give you more if you tell me how
Last edited by Homan42 (2014-10-18 19:43:17)

Ok, I could solve the problem myself by installing the latest nvidia driver. Now I guess the intel grahic card is not used anymore, but I don't really know...

Macbook pro does not respond to bluetooth keyboard and mouse at login screen

i've seen this question floating around and i don't think i've found one that has been resolved. i'm hoping someone may have an answer by now.
i do not have this issue when i boot into windows 7 (bootcamp) the macbook pro responds to keyboard input and mouse input immediately on the windows 7 login screen. when i boot into mac, there is no response from either. i've seen suggestions of waiting for 30 secods. i still get nothing after waiting for over a minute.
what i do right now is use the built-in touch pad and keyboard of the macbook pro to get past the login screen. once i'm logged in, i can see that the bluetooth devices are not yet connected (the three dots that go across the bluetooth symbol at the top right of the screen are not yet there). then after a while, maybe about half a minute, the bluetooth keyboard and mouse are connected and i can use them normally.
it is not a big deal but it is very annoying.
i am using a logitech bluetooth mouse (v740) and an adesso bluetooth keyboard (wkb-4000bm). i also tried an azio bluetooth keyboard and had the same issue. all these keyboards are made for mac.
thannks in advance.

just a correction, the keyboard and mouse don't always automatically reconnect once i'm logged in. most of the time i have to go click the bluetooth icon at the top right of my screen, select the mouse and then select "connect". i have to do the same to the keyboard.

Keyboard lighting at the login screen?

Hi,
I have a mid 2011 MBA with 10.7.4. Lion used to have the feature where the keyboard light had its own setting for the login screen. This way I could set it so that the light was on at the login screen and went off right after logging in.
After installing ML today it seems that this is not the case anymore. If I switch off the light in my account, the light is off also at the login screen. Is it supposed to be like that? I guess, there's no setting for this in ML?

Could someone please test this? Resetting SMC and PRAM didn't change the situation.

I have problem at desktop login screen startup

Hi guys...
I install Solaris 10 1/06 and every thing is ok...
When the Solaris startup is appear some text and its loading lines
like:
checking ufs filesystems
/dev/rdsk/c1d0s4: is logging.
/dev/rdsk/c1d0s3: is logging.
/dev/rdsk/c1d0s7: is logging.
unknown console login: syslogd: line 24: warnin: loghost could not be resolvedthen it is appear the following lines:
* Starting Desktop Login Screen on display :0...
* Wait for the Desktop Login screen before logging in.
************************************************************then it is reboot my computer.
I don't know what happened and I need your help.
============= Some Information about My computer =============
processor: AMD Athlon 64Processor 3000+
RAM : 2 GB
HD : 250 GB Sata
I have already install windows on this computer, When I startup my computer the GNU GRUB is appear choosing window any OS will be running.
I Solaris 10 on the same HD that have been windows, and every one of those OS have 100 GB from HD
=========================================================
I am sorry for my English writing, I don't know English very well. :)
Message was edited by:
Mohd

I have the exact same problem.
my system hangs after solaris wants to start the "desktop login screen".
during the installation i had a problem that X or something couldnt start either. i had to use the console based installation (number 4.), with the standard interactive installation my system would hang after "discovering additional network devices".
i can use the failsafe option. i guess its something with X and my network card?

Problems with XP login screen

I recently installed a G-force4 MX440-T8X and while installing the software, it disabled my fast switch login screen in win XP and it will not allow me to change it back. I have tried uninstalling all of the software as well as that piece of hardware and nothing works. It seems to have installed some third party software that controls my display properties with no way to uninstall it. Does anyone know the solution to this problem?
thanks

What version of drivers and where did you get them?

USB Keyboard Not Working At Login Screen

After waking my brand new Mac Pro (OS X 10.7.4) from sleep, my usb keyboard sometimes becomes unresponsive. So, at the login, I am unable to type my password in order to restore my session.
Is there a reason for usb devices to not work after waking the mac up? I tried all of the usb ports on the mac, as well as all the ports on both monitors. Thankfully, I have a bluetooth mouse and that works. But no idea why the usb devices stop working all together...
My software is completely up to date. And since this computer is less than a month out of the box, I'm puzzled as to why there would be any issues with it. Please let me know if there is a setting that affects this and what I need to do to fix it.
Thanks!

Maybe it needs to be plugged into the Mac before it goes to sleep...
Because when it wasn't letting me type anything I tried every USB port on the Mac itself, as well as the monitors, and even using an extender. Nothing worked.
However, I did eventually leave the keyboard plugged into the Mac and it woke up without a problem this morning. So, I'm hoping your solution did the trick!
Thanks

Keyboard problems in gnome

When I log to gnome the keyboard starts to behave very bad, when I enter my password everything is fine but when I log in my keys work as the Fn key was always on but if I don't log in to gnome it works fine (but it if I kill gnome it doesn't return to work fine) What do I have to do get my keyboard working again?

Vicfred wrote:When I log to gnome the keyboard starts to behave very bad, when I enter my password everything is fine but when I log in my keys work as the Fn key was always on but if I don't log in to gnome it works fine (but it if I kill gnome it doesn't return to work fine) What do I have to do get my keyboard working again?
I had the same symptoms in two different laptops. It was like if the Fn key was stuck.
I am not really using the gnome DE, I just use a window manager, in this case icewm. But I did start
gnome-settings-daemon on icewm startup file.
Commenting out gnome-settings-daemon stopped the weird keyboard behavior.
So I started gconf-editor (is in extra) and did quite blindly untick anything related to keys or function keys.
So f.e. in apps -> gnome-settings-daemon -> plugins -> a11y-keyboard and unticked "active".
This takes a while, and is quite a dumb solution since at the end I don't know what solved the problem,
but it was solved.
Mektub

Keyboard not working (On login screen!)

Hi there,
I have a customer with a brand new PC with 8.1
It was running fine for a few days - then they called me to say they could not login...
I logged in remotely and saw that the on-screen keyboard was on the screen at the login stage.
I was able to login remotely as I was not using the physical keyboard.
I Googled the issue and found a fair few similar issues.
I found that if the user, a) turned off the on-screen keyboard & b) clicked the Accessibility icon and then turned off the options in there (Sticky Keys, Toggle Keys and Filter Keys) the physical keyboard then started working...
So that seemed to fix it.
The other discussions I read seemed to suggest the fix for the issue is to go into Control panel >> Ease of Access & turning these things of permanently...
So I did that, but on reboot, they revert back and the user cannot login back in & is forced to follow my instructions on closing the on-screen keyboard, turning off the Accessibility options, so they can then login each time they turn their computer on
- most inconvenient!.
It is very frustrating and would very much appreciate if anyone has a solution...
Thanks, Dave

Hi,
Have you made changes on All Control Panel Items\Ease of Access Center\Change sign-in settings?
And have the customer made any changes recently which might cause this issue?
Yolanda Zhu
TechNet Community Support

Keyboard problem with Mac os 10.7 + FileVault to + login screen

I have a problem with the login screen, the keyboard is recognized as a English keyboard but I have a french keyboard. The menu to change keyboard language is not displayed on login screen since 10.7.2.
During the session the keyboard is French, it's only for the login screen.
How can I fix this and switch my keyboard layout to French in login screen ?
Thank you.

How did you find out the keyboard layout changed to English? I had a similar problem with my first login after enabling FileVault, and now I think this might be a cause? I have a Spanish keyboard.
See this thread also:
https://discussions.apple.com/message/16293028#16293028
Rolando

Gnome Black Screen with Mouse Cursor after Login

I am using Archlinux 64bit with a Gnome Desktop Environment. Everything was running normally uptill today. When i ran "sudo fc-cache", my system froze. I couldnt open any other app but i was able to access terminal. I restarted using "reboot" command. After that I was unable to log in to my desktop.
The Gnome login screen comes and after entering the correct username and password, all I can see is a black screen with mouse cursor. I then started gnome manually with "startx" and it worked. But still I am unable to use normally (that is the graphical login). I reinstalled gdm but it didnt work. Please help me out.

there are a lot of processess running... dunno killing which process will not cause a problem
here is the xorg log ( sorry i dont have much knowlegde to analyse it )
[ 2957.489]
X.Org X Server 1.16.1
Release Date: 2014-09-21
[ 2957.493] X Protocol Version 11, Revision 0
[ 2957.494] Build Operating System: Linux 3.16.1-1-ARCH x86_64
[ 2957.495] Current Operating System: Linux defo-arch 3.17.1-1-ARCH #1 SMP PREEMPT Wed Oct 15 15:04:35 CEST 2014 x86_64
[ 2957.495] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=3c376af4-e330-4277-8bfa-388dabfced9e rw quiet
[ 2957.497] Build Date: 21 September 2014 10:53:13AM
[ 2957.498]
[ 2957.499] Current version of pixman: 0.32.6
[ 2957.501] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 2957.501] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 2957.506] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Oct 26 01:36:27 2014
[ 2957.507] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 2957.507] (==) No Layout section. Using the first Screen section.
[ 2957.507] (==) No screen section available. Using defaults.
[ 2957.507] (**) |-->Screen "Default Screen Section" (0)
[ 2957.507] (**) | |-->Monitor "<default monitor>"
[ 2957.507] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 2957.507] (==) Automatically adding devices
[ 2957.507] (==) Automatically enabling devices
[ 2957.507] (==) Automatically adding GPU devices
[ 2957.507] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[ 2957.507] Entry deleted from font path.
[ 2957.507] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 2957.507] Entry deleted from font path.
[ 2957.507] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 2957.507] Entry deleted from font path.
[ 2957.507] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 2957.507] Entry deleted from font path.
[ 2957.507] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 2957.507] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 2957.507] Entry deleted from font path.
[ 2957.507] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 2957.507] (==) FontPath set to:
/usr/share/fonts/misc/
[ 2957.507] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 2957.507] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 2957.507] (II) Loader magic: 0x818d80
[ 2957.507] (II) Module ABI versions:
[ 2957.507] X.Org ANSI C Emulation: 0.4
[ 2957.507] X.Org Video Driver: 18.0
[ 2957.507] X.Org XInput driver : 21.0
[ 2957.507] X.Org Server Extension : 8.0
[ 2957.509] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
[ 2957.509] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 2957.510] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0
[ 2957.512] (--) PCI:*(0:0:2:0) 8086:2a02:1028:022f rev 12, Mem @ 0xfea00000/1048576, 0xe0000000/268435456, I/O @ 0x0000eff8/8
[ 2957.512] (--) PCI: (0:0:2:1) 8086:2a03:1028:022f rev 12, Mem @ 0xfeb00000/1048576
[ 2957.512] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 2957.512] (II) LoadModule: "glx"
[ 2957.512] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 2957.514] (II) Module glx: vendor="X.Org Foundation"
[ 2957.514] compiled for 1.16.1, module version = 1.0.0
[ 2957.514] ABI class: X.Org Server Extension, version 8.0
[ 2957.514] (==) AIGLX enabled
[ 2957.514] (==) Matched intel as autoconfigured driver 0
[ 2957.514] (==) Matched intel as autoconfigured driver 1
[ 2957.514] (==) Matched modesetting as autoconfigured driver 2
[ 2957.514] (==) Matched fbdev as autoconfigured driver 3
[ 2957.514] (==) Matched vesa as autoconfigured driver 4
[ 2957.514] (==) Assigned the driver to the xf86ConfigLayout
[ 2957.514] (II) LoadModule: "intel"
[ 2957.514] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 2957.515] (II) Module intel: vendor="X.Org Foundation"
[ 2957.515] compiled for 1.16.1, module version = 2.99.916
[ 2957.515] Module class: X.Org Video Driver
[ 2957.515] ABI class: X.Org Video Driver, version 18.0
[ 2957.515] (II) LoadModule: "modesetting"
[ 2957.515] (WW) Warning, couldn't open module modesetting
[ 2957.515] (II) UnloadModule: "modesetting"
[ 2957.515] (II) Unloading modesetting
[ 2957.515] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 2957.515] (II) LoadModule: "fbdev"
[ 2957.515] (WW) Warning, couldn't open module fbdev
[ 2957.515] (II) UnloadModule: "fbdev"
[ 2957.515] (II) Unloading fbdev
[ 2957.515] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 2957.515] (II) LoadModule: "vesa"
[ 2957.515] (WW) Warning, couldn't open module vesa
[ 2957.515] (II) UnloadModule: "vesa"
[ 2957.515] (II) Unloading vesa
[ 2957.515] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 2957.515] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[ 2957.516] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[ 2957.516] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[ 2957.516] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300
[ 2957.516] (++) using VT number 1
[ 2957.516] (--) controlling tty is VT number 1, auto-enabling KeepTty
[ 2957.516] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20140725
[ 2957.516] (--) intel(0): Integrated Graphics Chipset: Intel(R) 965GM
[ 2957.517] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1
[ 2957.517] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 2957.517] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 2957.517] (==) intel(0): RGB weight 888
[ 2957.517] (==) intel(0): Default visual is TrueColor
[ 2957.517] (II) intel(0): Output LVDS1 has no monitor section
[ 2957.517] (--) intel(0): Found backlight control interface acpi_video0 (type 'firmware') for output LVDS1
[ 2957.517] (II) intel(0): Enabled output LVDS1
[ 2957.517] (II) intel(0): Output VGA1 has no monitor section
[ 2957.517] (II) intel(0): Enabled output VGA1
[ 2957.517] (II) intel(0): Output HDMI1 has no monitor section
[ 2957.517] (II) intel(0): Enabled output HDMI1
[ 2957.517] (II) intel(0): Output TV1 has no monitor section
[ 2957.517] (II) intel(0): Enabled output TV1
[ 2957.517] (--) intel(0): Using a maximum size of 256x256 for hardware cursors
[ 2957.517] (II) intel(0): Output VIRTUAL1 has no monitor section
[ 2957.517] (II) intel(0): Enabled output VIRTUAL1
[ 2957.517] (--) intel(0): Output LVDS1 using initial mode 1280x800 on pipe 1
[ 2957.517] (==) intel(0): TearFree disabled
[ 2957.517] (==) intel(0): DPI set to (96, 96)
[ 2957.517] (II) Loading sub module "dri2"
[ 2957.517] (II) LoadModule: "dri2"
[ 2957.517] (II) Module "dri2" already built-in
[ 2957.517] (II) Loading sub module "present"
[ 2957.517] (II) LoadModule: "present"
[ 2957.517] (II) Module "present" already built-in
[ 2957.517] (==) Depth 24 pixmap format is 32 bpp
[ 2957.518] (II) intel(0): SNA initialized with Broadwater (gen4) backend
[ 2957.518] (==) intel(0): Backing store enabled
[ 2957.518] (==) intel(0): Silken mouse enabled
[ 2957.518] (II) intel(0): HW Cursor enabled
[ 2957.518] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 2957.518] (==) intel(0): DPMS enabled
[ 2957.518] (II) intel(0): [XvMC] i965_xvmc driver initialized.
[ 2957.518] (II) intel(0): [DRI2] Setup complete
[ 2957.518] (II) intel(0): [DRI2] DRI driver: i965
[ 2957.518] (II) intel(0): [DRI2] VDPAU driver: i965
[ 2957.518] (II) intel(0): direct rendering: DRI2 enabled
[ 2957.518] (II) intel(0): hardware support for Present enabled
[ 2957.518] (==) intel(0): display hotplug detection enabled
[ 2957.518] (--) RandR disabled
[ 2957.569] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 2957.569] (II) AIGLX: enabled GLX_ARB_create_context
[ 2957.569] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 2957.569] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 2957.569] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 2957.569] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 2957.569] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 2957.569] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 2957.569] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 2957.569] (II) AIGLX: Loaded and initialized i965
[ 2957.569] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 2957.576] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 1, position (0, 0), rotation normal, reflection none
[ 2957.583] (II) intel(0): Setting screen physical size to 338 x 211
[ 2957.636] (II) config/udev: Adding input device Video Bus (/dev/input/event12)
[ 2957.636] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 2957.636] (II) LoadModule: "evdev"
[ 2957.636] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 2957.637] (II) Module evdev: vendor="X.Org Foundation"
[ 2957.637] compiled for 1.16.0, module version = 2.9.0
[ 2957.637] Module class: X.Org XInput Driver
[ 2957.637] ABI class: X.Org XInput driver, version 21.0
[ 2957.637] (II) systemd-logind: got fd for /dev/input/event12 13:76 fd 15 paused 0
[ 2957.637] (II) Using input driver 'evdev' for 'Video Bus'
[ 2957.638] (**) Video Bus: always reports core events
[ 2957.638] (**) evdev: Video Bus: Device: "/dev/input/event12"
[ 2957.638] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 2957.638] (--) evdev: Video Bus: Found keys
[ 2957.638] (II) evdev: Video Bus: Configuring as keyboard
[ 2957.638] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input19/event12"
[ 2957.638] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 6)
[ 2957.638] (**) Option "xkb_rules" "evdev"
[ 2957.638] (**) Option "xkb_model" "pc104"
[ 2957.638] (**) Option "xkb_layout" "us"
[ 2957.669] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 2957.670] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2957.670] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 16 paused 0
[ 2957.670] (II) Using input driver 'evdev' for 'Power Button'
[ 2957.670] (**) Power Button: always reports core events
[ 2957.670] (**) evdev: Power Button: Device: "/dev/input/event2"
[ 2957.670] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 2957.670] (--) evdev: Power Button: Found keys
[ 2957.670] (II) evdev: Power Button: Configuring as keyboard
[ 2957.670] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input6/event2"
[ 2957.670] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 2957.670] (**) Option "xkb_rules" "evdev"
[ 2957.670] (**) Option "xkb_model" "pc104"
[ 2957.670] (**) Option "xkb_layout" "us"
[ 2957.671] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
[ 2957.671] (II) No input driver specified, ignoring this device.
[ 2957.671] (II) This device may have been added with another device file.
[ 2957.671] (II) config/udev: Adding input device Sleep Button (/dev/input/event3)
[ 2957.671] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 2957.672] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 17 paused 0
[ 2957.672] (II) Using input driver 'evdev' for 'Sleep Button'
[ 2957.672] (**) Sleep Button: always reports core events
[ 2957.672] (**) evdev: Sleep Button: Device: "/dev/input/event3"
[ 2957.672] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 2957.672] (--) evdev: Sleep Button: Found keys
[ 2957.672] (II) evdev: Sleep Button: Configuring as keyboard
[ 2957.672] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input7/event3"
[ 2957.672] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[ 2957.672] (**) Option "xkb_rules" "evdev"
[ 2957.672] (**) Option "xkb_model" "pc104"
[ 2957.672] (**) Option "xkb_layout" "us"
[ 2957.673] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event6)
[ 2957.673] (II) No input driver specified, ignoring this device.
[ 2957.673] (II) This device may have been added with another device file.
[ 2957.673] (II) config/udev: Adding input device HDA Intel HDMI/DP,pcm=3 (/dev/input/event7)
[ 2957.673] (II) No input driver specified, ignoring this device.
[ 2957.673] (II) This device may have been added with another device file.
[ 2957.673] (II) config/udev: Adding input device HDA Intel Front Headphone Front (/dev/input/event8)
[ 2957.673] (II) No input driver specified, ignoring this device.
[ 2957.673] (II) This device may have been added with another device file.
[ 2957.674] (II) config/udev: Adding input device HDA Intel Front Headphone Surround (/dev/input/event9)
[ 2957.674] (II) No input driver specified, ignoring this device.
[ 2957.674] (II) This device may have been added with another device file.
[ 2957.674] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 2957.674] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 2957.675] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 18 paused 0
[ 2957.675] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 2957.675] (**) AT Translated Set 2 keyboard: always reports core events
[ 2957.675] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 2957.675] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 2957.675] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 2957.675] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 2957.675] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 2957.675] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
[ 2957.675] (**) Option "xkb_rules" "evdev"
[ 2957.675] (**) Option "xkb_model" "pc104"
[ 2957.675] (**) Option "xkb_layout" "us"
[ 2957.675] (II) config/udev: Adding input device AlpsPS/2 ALPS GlidePoint (/dev/input/event11)
[ 2957.675] (**) AlpsPS/2 ALPS GlidePoint: Applying InputClass "evdev touchpad catchall"
[ 2957.675] (**) AlpsPS/2 ALPS GlidePoint: Applying InputClass "touchpad catchall"
[ 2957.675] (**) AlpsPS/2 ALPS GlidePoint: Applying InputClass "Default clickpad buttons"
[ 2957.675] (II) LoadModule: "synaptics"
[ 2957.676] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 2957.676] (II) Module synaptics: vendor="X.Org Foundation"
[ 2957.676] compiled for 1.16.0, module version = 1.8.1
[ 2957.676] Module class: X.Org XInput Driver
[ 2957.676] ABI class: X.Org XInput driver, version 21.0
[ 2957.676] (II) systemd-logind: got fd for /dev/input/event11 13:75 fd 19 paused 0
[ 2957.676] (II) Using input driver 'synaptics' for 'AlpsPS/2 ALPS GlidePoint'
[ 2957.676] (**) AlpsPS/2 ALPS GlidePoint: always reports core events
[ 2957.676] (**) Option "Device" "/dev/input/event11"
[ 2957.710] (--) synaptics: AlpsPS/2 ALPS GlidePoint: x-axis range 0 - 1023 (res 0)
[ 2957.710] (--) synaptics: AlpsPS/2 ALPS GlidePoint: y-axis range 0 - 767 (res 0)
[ 2957.710] (--) synaptics: AlpsPS/2 ALPS GlidePoint: pressure range 0 - 127
[ 2957.710] (II) synaptics: AlpsPS/2 ALPS GlidePoint: device does not report finger width.
[ 2957.710] (--) synaptics: AlpsPS/2 ALPS GlidePoint: buttons: left right middle
[ 2957.710] (--) synaptics: AlpsPS/2 ALPS GlidePoint: Vendor 0x2 Product 0x8
[ 2957.710] (--) synaptics: AlpsPS/2 ALPS GlidePoint: invalid finger width range. defaulting to 0 - 15
[ 2957.710] (**) Option "TapButton1" "1"
[ 2957.710] (**) Option "TapButton2" "2"
[ 2957.710] (**) Option "TapButton3" "3"
[ 2957.710] (--) synaptics: AlpsPS/2 ALPS GlidePoint: touchpad found
[ 2957.710] (**) AlpsPS/2 ALPS GlidePoint: always reports core events
[ 2957.710] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio2/input/input10/event11"
[ 2957.710] (II) XINPUT: Adding extended input device "AlpsPS/2 ALPS GlidePoint" (type: TOUCHPAD, id 10)
[ 2957.710] (**) synaptics: AlpsPS/2 ALPS GlidePoint: (accel) MinSpeed is now constant deceleration 2.5
[ 2957.710] (**) synaptics: AlpsPS/2 ALPS GlidePoint: (accel) MaxSpeed is now 1.75
[ 2957.710] (**) synaptics: AlpsPS/2 ALPS GlidePoint: (accel) AccelFactor is now 0.156
[ 2957.710] (**) AlpsPS/2 ALPS GlidePoint: (accel) keeping acceleration scheme 1
[ 2957.710] (**) AlpsPS/2 ALPS GlidePoint: (accel) acceleration profile 1
[ 2957.710] (**) AlpsPS/2 ALPS GlidePoint: (accel) acceleration factor: 2.000
[ 2957.710] (**) AlpsPS/2 ALPS GlidePoint: (accel) acceleration threshold: 4
[ 2957.710] (--) synaptics: AlpsPS/2 ALPS GlidePoint: touchpad found
[ 2957.711] (II) config/udev: Adding input device AlpsPS/2 ALPS GlidePoint (/dev/input/mouse1)
[ 2957.711] (**) AlpsPS/2 ALPS GlidePoint: Ignoring device from InputClass "touchpad ignore duplicates"
[ 2957.711] (II) config/udev: Adding input device ALPS PS/2 Device (/dev/input/event10)
[ 2957.711] (**) ALPS PS/2 Device: Applying InputClass "evdev pointer catchall"
[ 2957.712] (II) systemd-logind: got fd for /dev/input/event10 13:74 fd 20 paused 0
[ 2957.712] (II) Using input driver 'evdev' for 'ALPS PS/2 Device'
[ 2957.712] (**) ALPS PS/2 Device: always reports core events
[ 2957.712] (**) evdev: ALPS PS/2 Device: Device: "/dev/input/event10"
[ 2957.712] (--) evdev: ALPS PS/2 Device: Vendor 0x2 Product 0x8
[ 2957.712] (--) evdev: ALPS PS/2 Device: Found 3 mouse buttons
[ 2957.712] (--) evdev: ALPS PS/2 Device: Found relative axes
[ 2957.712] (--) evdev: ALPS PS/2 Device: Found x and y relative axes
[ 2957.712] (II) evdev: ALPS PS/2 Device: Configuring as mouse
[ 2957.712] (**) evdev: ALPS PS/2 Device: YAxisMapping: buttons 4 and 5
[ 2957.712] (**) evdev: ALPS PS/2 Device: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2957.712] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio2/input/input12/event10"
[ 2957.712] (II) XINPUT: Adding extended input device "ALPS PS/2 Device" (type: MOUSE, id 11)
[ 2957.712] (II) evdev: ALPS PS/2 Device: initialized for relative axes.
[ 2957.712] (**) ALPS PS/2 Device: (accel) keeping acceleration scheme 1
[ 2957.712] (**) ALPS PS/2 Device: (accel) acceleration profile 0
[ 2957.712] (**) ALPS PS/2 Device: (accel) acceleration factor: 2.000
[ 2957.712] (**) ALPS PS/2 Device: (accel) acceleration threshold: 4
[ 2957.713] (II) config/udev: Adding input device ALPS PS/2 Device (/dev/input/mouse0)
[ 2957.713] (II) No input driver specified, ignoring this device.
[ 2957.713] (II) This device may have been added with another device file.
[ 2957.713] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
[ 2957.713] (II) No input driver specified, ignoring this device.
[ 2957.713] (II) This device may have been added with another device file.
[ 2957.714] (II) config/udev: Adding input device Dell WMI hotkeys (/dev/input/event5)
[ 2957.714] (**) Dell WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[ 2957.714] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 21 paused 0
[ 2957.714] (II) Using input driver 'evdev' for 'Dell WMI hotkeys'
[ 2957.714] (**) Dell WMI hotkeys: always reports core events
[ 2957.714] (**) evdev: Dell WMI hotkeys: Device: "/dev/input/event5"
[ 2957.714] (--) evdev: Dell WMI hotkeys: Vendor 0 Product 0
[ 2957.714] (--) evdev: Dell WMI hotkeys: Found keys
[ 2957.714] (II) evdev: Dell WMI hotkeys: Configuring as keyboard
[ 2957.714] (**) Option "config_info" "udev:/sys/devices/virtual/input/input11/event5"
[ 2957.714] (II) XINPUT: Adding extended input device "Dell WMI hotkeys" (type: KEYBOARD, id 12)
[ 2957.714] (**) Option "xkb_rules" "evdev"
[ 2957.714] (**) Option "xkb_model" "pc104"
[ 2957.714] (**) Option "xkb_layout" "us"
[ 2963.887] (II) evdev: Dell WMI hotkeys: Close
[ 2963.887] (II) UnloadModule: "evdev"
[ 2963.887] (II) systemd-logind: releasing fd for 13:69
[ 2963.949] (II) evdev: ALPS PS/2 Device: Close
[ 2963.950] (II) UnloadModule: "evdev"
[ 2963.950] (II) systemd-logind: releasing fd for 13:74
[ 2964.016] (II) UnloadModule: "synaptics"
[ 2964.016] (II) systemd-logind: releasing fd for 13:75
[ 2964.069] (II) evdev: AT Translated Set 2 keyboard: Close
[ 2964.070] (II) UnloadModule: "evdev"
[ 2964.070] (II) systemd-logind: releasing fd for 13:64
[ 2964.123] (II) evdev: Sleep Button: Close
[ 2964.123] (II) UnloadModule: "evdev"
[ 2964.123] (II) systemd-logind: releasing fd for 13:67
[ 2964.156] (II) evdev: Power Button: Close
[ 2964.156] (II) UnloadModule: "evdev"
[ 2964.156] (II) systemd-logind: releasing fd for 13:66
[ 2964.183] (II) evdev: Video Bus: Close
[ 2964.183] (II) UnloadModule: "evdev"
[ 2964.183] (II) systemd-logind: releasing fd for 13:76
[ 2964.271] (EE) Server terminated successfully (0). Closing log file.

Help! bootcamped window pro 7 ok BUT driver / setup flash drive seemed to correctly install drivers, nvidia etc etc BUT on windows login screen i have no mouse or keyboard , have plugged in logitech usb mouse and keyboard still no good please help

Please can somebody help me with this.
i cannot get any mouse or keyboard input on my login screen after bootcamping windows 7 pro.
i used a correctly formatted drive for the driver downloads, they seemed to install but now i have no input method to login to wondows7.
all is fine in osx apple wireless mouse keyboard magicpad ok
windows cant login due to no input devices.
have connected logitech mouse keyboard still nothing.
please help!
thanks in advance

1. I have tried copying the Keyboard/Trackpad/Mouse drivers to the $WinPEDriver$ directory with mixed success on a 2012 MBP.
2. My experience is based on a 2013 rMBP. You may be able to use an Apple USB Keypad/Mouse to better success.
3. See http://www.macworld.com/article/2460820/macbook-pro-mid-2014-review-minor-update -offers-slightly-better-cpu-performance.html for HW differences between the two machines.
4. If you have access to a 2013 rMBP, I can suggest trying to build the USB on that and working with the USB to see if you can make it install Windows. the rMBP 2014 and rMBP 2013 have the same HW, except some CPU changes. You can also try building the USB at the nearest Apple store, if possible.
5. There is a section in AutoUnattend.xml, which is supposed to install all drivers in $WinPEDriver$ (see this http://support.microsoft.com/kb/2686316 )
<component name="Microsoft-Windows-PnpCustomizationsWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <DriverPaths>
                <PathAndCredentials wcm:keyValue="1" wcm:action="add">
                    <Path>$WinPEDriver$</Path>
                </PathAndCredentials>
            </DriverPaths>
        </component>

Keyboard problems on Gnome login screen

Similar Messages

Maybe you are looking for