No dead keys in Xorg, strange dead keys in virtual consoles

Without touching my configs I'm having issues with the dead keys on my german keyboard:
In applications under Xorg they are simply inactive (as if choosing a nodeadkeys-layout). In virtual consoles there is no character displayed when I double-tap a dead key (e.g. '~'), but it is indeed displayed if I press some other key afterwards. Strange thing here is that it is not combined with the second one like in the deadkeys-layout (e.g. à for pressing ` and then 'a').
I do my Xorg layout via /etc/X11/xorg.conf.d/25-evdev.conf:
Section "InputClass"
Identifier "Logitech Illuminated Keyboard"
MatchProduct "Logitech Illuminated Keyboard"
Driver "evdev"
Option "XkbLayout" "de"
Option "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection
According to /var/log/Xorg.0.log the layout seems to be set correctly:
[ 39.725] (**) evdev: Logitech Logitech Illuminated Keyboard: Device: "/dev/input/event2"
[ 39.725] (--) evdev: Logitech Logitech Illuminated Keyboard: Vendor 0x46d Product 0xc318
[ 39.725] (--) evdev: Logitech Logitech Illuminated Keyboard: Found keys
[ 39.725] (II) evdev: Logitech Logitech Illuminated Keyboard: Configuring as keyboard
[ 39.725] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.3/4-1.3:1.0/input/input2/event2"
[ 39.725] (II) XINPUT: Adding extended input device "Logitech Logitech Illuminated Keyboard" (type: KEYBOARD, id 10)
[ 39.725] (**) Option "xkb_rules" "evdev"
[ 39.725] (**) Option "xkb_model" "evdev"
[ 39.725] (**) Option "xkb_layout" "de"
[ 39.725] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
I'm using an up-to-date pure-systemd install.
Any suggestions how to trace down the issue?
Thanks in advance,
lynix
Last edited by lynix (2012-10-10 21:21:26)

I’ve the same behavior as you in virtual console, and I really don’t know why.
For Xorg, check your .XCompose (recently I’ve a problem with a line only recognized by Xorg months later after I add it) or the Compose file of your locale in
/usr/share/X11/locale/$your_locale.UTF-8/Compose
However it seems en_US.UTF-8/Compose is used for many western languages (at least that seems to be the case for french).

Similar Messages

Key Generation in console

Hi Folks,
I have defined key generation in console .I need some information in key generation such as ,if i define None ,range and Qualifed Range.
Where it effect and what are significance of it.
Secondaly., We create clone in Import manager and then we do mapping to remote key to the clone of the main table. I am looking for the business significance and techanical signifiance of it.
Thanks in advance,
Rohit

Hi Rohit,
If you choose
NONE: - Then remote key will not be generated automatically and has to be applied explicitly either using import manager or in data manager.
RANGE: - Here we can specify a range using TO and FROM. This generates the key automatically for that client between that range.
Qualified range: - Here we specify a range for a qualified table for key generation.
Keys are generated on a per value basis i.e. MDM automatically generates keys for the specified single-valued lookup field based on values you specify
using the Range property. You can specify Qualified Range values by selecting the
single-valued lookup field from the drop-down list and specifying From
and To values for each lookup table value.
Let me know if this helped your cause.
BR,
Siddharth

Sending Keys through VM Console incorrect Ascii mapping (openSUSE)?

Hi All,
I'm using a Hyper-V environment, and using Powershell to send keys via the console to the SUSE VM for setup
scripting. This all works fine with CentOS, Debian, Fedora and Ubuntu.
However, with SUSE 13 when I sent keys from powershell using the following commands:
$VMConsole = Connect-VMConsole
$KB = $VMConsole.VSMKB
$KB.TypeText("root")
It does not work. On further investigation I found that using TypeKey or TypeText it sends the keystrokes using
standard ascii table as found at:http://www.bluesock.org/~willg/dev/ascii.html
However, SUSE interprets using a different ascii table, found at: http://msdn.microsoft.com/en-us/library/windows/desktop/dd375731(v=vs.85).aspx
I can provide this by sending:
$KB.TypeKey(0x6B)
This produces the character + on the console.
Whereas, it should produce the character: k
This only seems to happen on OpenSUSE (at least it doesn’t happen on CentOS, Ubuntu, Debian or Fedora).
Have you got any ideas? I’ve tried resetting the keyboard to US layout on the SUSE VM, and I’ve also tried
using loadkeys us.
Cheers
Will

Hi Will,
Sorry that mistake .
You are using deploylinuxVM powershell , right?
In its fuctions I found this class " Msvm_Keyboard " , it has methods "
TypeText " and " TypeKey "
TypeText method of the Msvm_Keyboard class
"Simulates a series of typed ASCII characters. This routine may not be used to simulate the input of non-ASCII characters."
Parameters
asciiText [in]
Type: string
The series of ASCII text characters to type.
TypeKey method of the Msvm_Keyboard class
“Simulates a press-release key sequence."
Parameters
keyCode [in]
Type: uint32
The virtual key code of the key to press. For the list for virtual-key codes, see
Virtual-Key Codes.
As you mentioned :
"$KB.TypeKey(0x6B)
This produces the character + on the console."
It seems Method Typekey invoked the Virtual-Key Codes
not Ascii .
Hope this helps
Best Regards
Elton Ji
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.

Display lost when switching virtual consoles (xorg 1.12.1-1)

Hi all,
About a week ago I noticed that I will sometimes be left with a black screen when I switch between virtual consoles using Ctrl+Alt+F8, etc. The system is still running, and can be communicated with over the network, but, short of rebooting via ssh or killing X, there seems to be nothing I can do to get the screen working again. It seems especially common when switching between F7 and F8 (both graphical) but sometimes occurs when switching from a graphical to a text based console (F1-F6).
I have downgraded from recent versions of xorg-server, xorg-server-common and the nvidia drivers to see if the problem would go away, but without success.
Thanks for your thoughts!
Last edited by conn-fused (2012-04-22 05:22:28)

Well, many 20-nvidia-conf files later, the problem persists.
Not only that, but the number of jumps between virtual consoles before failure seems to be perfectly consistent. I login as one user (a GUI session on tty7), then switch user to open a new GUI session on tty8. Now, (using Ctrl+Alt+F7 or F8, as appropriate), I switch back to the first user (enter a password because opening the new session locks the first one), switch back to the second user, back to the first, and then try switch back to the second ... and all is lost. The fifth switch fails: every ... single ... time.
I'd appreciate it if someone else using an Nvidia card and the proprietary drivers would try this procedure and see if they too face the black screen after the fifth switch. If you do, it's not something I've misconfigured on my own, but an issue with a package (probably nvidia's) that I suppose I'll just have to wait for a fix for.
Thanks!

Dead keys on virtual keyboard

My virtual keypad no long allows the use of the "0" key and the "P" key. Both are on the right side of my I-Touch. This prevents me from entering my password for my WI-FI, and any E-mail. All the other key work fine. This morning I downloaded the new I-touch/phone 2.0 firmware today and 2 new apps. I don't know if this is the cause or it the key have been dead for a while, as I have not used the keypad in several months. I have tried doing a total re-set of all setting bring everything back to factory specs. I still have the two dead keys.
Any idea what happened? or should I just go to Apple repair directly?

hi,
i have a NEW ipod touch, still with 1.x version software, and having the same problem. Also the backspace key doesn't function. Should I take this thing back, or can I somehow calibrate the screen?
greetz,

[SOLVED] Xorg Strangeness- Running startx runs xorg for a split second

As in the subject, I am trying to run startx on my Arch (x86_64) machine for the first time since installation, however X only runs for a split second before quitting.. I've checked the log, but there aren't any errors that pop up to tell me what's going on. What I've been doing that I think may affect the answer:
Installed proprietary nvidia drivers that I downloaded off of nvidia's website (though I removed it by running sudo ./driver.run -uninstall)
Installed nvidia drivers from the repository (sudo pacman -S nvidia nvidia-utils)
shut off nouveau drivers (blacklisted nouveau in /etc/modprobe.d)
Ran nvidia-xconfig to generate new xorg.conf file
/var/log/Xorg.0.log shows nothing with (EE), so I assume that everything is going smoothly, however still can't get X to work. Any help would be appreciated. Google's let me down so far.
Perhaps some fresh eyes could help me
(contents of /var/log/Xorg.0.log)
[ 22.116]
X.Org X Server 1.12.2
Release Date: 2012-05-29
[ 22.116] X Protocol Version 11, Revision 0
[ 22.116] Build Operating System: Linux 3.0.32-1-lts x86_64
[ 22.116] Current Operating System: Linux Ponyville 3.3.7-1-ARCH #1 SMP PREEMPT Tue May 22 00:26:26 CEST 2012 x86_64
[ 22.117] Kernel command line: root=/dev/sda4 ro
[ 22.117] Build Date: 30 May 2012 07:24:13PM
[ 22.117]
[ 22.117] Current version of pixman: 0.26.0
[ 22.117] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 22.117] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 22.119] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jun 7 08:50:45 2012
[ 22.148] (==) Using config file: "/etc/X11/xorg.conf"
[ 22.148] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 22.166] (==) ServerLayout "Layout0"
[ 22.166] (**) |-->Screen "Screen0" (0)
[ 22.166] (**) | |-->Monitor "Monitor0"
[ 22.166] (**) | |-->Device "Device0"
[ 22.166] (**) |-->Input Device "Keyboard0"
[ 22.166] (**) |-->Input Device "Mouse0"
[ 22.166] (==) Automatically adding devices
[ 22.166] (==) Automatically enabling devices
[ 22.196] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[ 22.196] Entry deleted from font path.
[ 22.196] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 22.196] Entry deleted from font path.
[ 22.196] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 22.196] Entry deleted from font path.
[ 22.213] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 22.213] Entry deleted from font path.
[ 22.213] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 22.213] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/100dpi/
[ 22.213] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 22.213] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 22.213] (WW) Disabling Keyboard0
[ 22.213] (WW) Disabling Mouse0
[ 22.213] (II) Loader magic: 0x7c58e0
[ 22.213] (II) Module ABI versions:
[ 22.213] X.Org ANSI C Emulation: 0.4
[ 22.213] X.Org Video Driver: 12.0
[ 22.213] X.Org XInput driver : 16.0
[ 22.213] X.Org Server Extension : 6.0
[ 22.214] (--) PCI:*(0:1:0:0) 10de:0dc4:196e:085a rev 161, Mem @ 0xf8000000/16777216, 0xe8000000/134217728, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 22.214] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 22.214] (II) LoadModule: "extmod"
[ 22.257] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 22.264] (II) Module extmod: vendor="X.Org Foundation"
[ 22.264] compiled for 1.12.2, module version = 1.0.0
[ 22.264] Module class: X.Org Server Extension
[ 22.264] ABI class: X.Org Server Extension, version 6.0
[ 22.265] (II) Loading extension MIT-SCREEN-SAVER
[ 22.265] (II) Loading extension XFree86-VidModeExtension
[ 22.265] (II) Loading extension XFree86-DGA
[ 22.265] (II) Loading extension DPMS
[ 22.265] (II) Loading extension XVideo
[ 22.265] (II) Loading extension XVideo-MotionCompensation
[ 22.265] (II) Loading extension X-Resource
[ 22.265] (II) LoadModule: "dbe"
[ 22.265] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 22.265] (II) Module dbe: vendor="X.Org Foundation"
[ 22.265] compiled for 1.12.2, module version = 1.0.0
[ 22.265] Module class: X.Org Server Extension
[ 22.265] ABI class: X.Org Server Extension, version 6.0
[ 22.265] (II) Loading extension DOUBLE-BUFFER
[ 22.265] (II) LoadModule: "glx"
[ 22.266] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 22.799] (II) Module glx: vendor="NVIDIA Corporation"
[ 22.799] compiled for 4.0.2, module version = 1.0.0
[ 22.799] Module class: X.Org Server Extension
[ 22.799] (II) NVIDIA GLX Module 295.53 Fri May 11 23:49:08 PDT 2012
[ 22.799] (II) Loading extension GLX
[ 22.799] (II) LoadModule: "record"
[ 22.799] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 22.885] (II) Module record: vendor="X.Org Foundation"
[ 22.885] compiled for 1.12.2, module version = 1.13.0
[ 22.885] Module class: X.Org Server Extension
[ 22.885] ABI class: X.Org Server Extension, version 6.0
[ 22.885] (II) Loading extension RECORD
[ 22.885] (II) LoadModule: "dri"
[ 22.885] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 22.911] (II) Module dri: vendor="X.Org Foundation"
[ 22.911] compiled for 1.12.2, module version = 1.0.0
[ 22.911] ABI class: X.Org Server Extension, version 6.0
[ 22.911] (II) Loading extension XFree86-DRI
[ 22.911] (II) LoadModule: "dri2"
[ 22.911] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 22.911] (II) Module dri2: vendor="X.Org Foundation"
[ 22.911] compiled for 1.12.2, module version = 1.2.0
[ 22.911] ABI class: X.Org Server Extension, version 6.0
[ 22.911] (II) Loading extension DRI2
[ 22.911] (II) LoadModule: "nvidia"
[ 22.912] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 22.993] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 22.993] compiled for 4.0.2, module version = 1.0.0
[ 22.994] Module class: X.Org Video Driver
[ 23.021] (II) NVIDIA dlloader X Driver 295.53 Fri May 11 23:29:56 PDT 2012
[ 23.021] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 23.021] (--) using VT number 7
[ 23.024] (II) Loading sub module "fb"
[ 23.024] (II) LoadModule: "fb"
[ 23.024] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 23.032] (II) Module fb: vendor="X.Org Foundation"
[ 23.032] compiled for 1.12.2, module version = 1.0.0
[ 23.032] ABI class: X.Org ANSI C Emulation, version 0.4
[ 23.032] (II) Loading sub module "wfb"
[ 23.032] (II) LoadModule: "wfb"
[ 23.032] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 23.038] (II) Module wfb: vendor="X.Org Foundation"
[ 23.038] compiled for 1.12.2, module version = 1.0.0
[ 23.038] ABI class: X.Org ANSI C Emulation, version 0.4
[ 23.038] (II) Loading sub module "ramdac"
[ 23.038] (II) LoadModule: "ramdac"
[ 23.038] (II) Module "ramdac" already built-in
[ 23.047] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 23.047] (==) NVIDIA(0): RGB weight 888
[ 23.047] (==) NVIDIA(0): Default visual is TrueColor
[ 23.047] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 23.047] (**) NVIDIA(0): Enabling 2D acceleration
[ 23.817] (II) NVIDIA(GPU-0): Display (ViewSonic VA1916wSERIES (CRT-1)) does not support
[ 23.817] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
[ 23.831] (II) NVIDIA(0): NVIDIA GPU GeForce GTS 450 (GF106) at PCI:1:0:0 (GPU-0)
[ 23.831] (--) NVIDIA(0): Memory: 1048576 kBytes
[ 23.831] (--) NVIDIA(0): VideoBIOS: 70.06.13.00.51
[ 23.831] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 23.831] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 23.833] (--) NVIDIA(0): Connected display device(s) on GeForce GTS 450 at PCI:1:0:0
[ 23.833] (--) NVIDIA(0): ViewSonic VA1916wSERIES (CRT-1)
[ 23.833] (--) NVIDIA(0): ViewSonic VA1916wSERIES (CRT-1): 400.0 MHz maximum pixel
[ 23.833] (--) NVIDIA(0): clock
[ 23.868] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 23.868] (**) NVIDIA(0): device ViewSonic VA1916wSERIES (CRT-1) (Using EDID
[ 23.868] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
[ 23.874] (II) NVIDIA(0): Assigned Display Device: CRT-1
[ 23.874] (==) NVIDIA(0):
[ 23.874] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 23.874] (==) NVIDIA(0): will be used as the requested mode.
[ 23.874] (==) NVIDIA(0):
[ 23.874] (II) NVIDIA(0): Validated modes:
[ 23.874] (II) NVIDIA(0): "nvidia-auto-select"
[ 23.874] (II) NVIDIA(0): Virtual screen size determined to be 1440 x 900
[ 23.903] (--) NVIDIA(0): DPI set to (89, 87); computed from "UseEdidDpi" X config
[ 23.903] (--) NVIDIA(0): option
[ 23.903] (--) Depth 24 pixmap format is 32 bpp
[ 23.903] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 23.903] (II) NVIDIA: access.
[ 23.906] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 23.906] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 23.906] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 23.906] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 23.906] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 23.906] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 23.906] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 23.906] (II) NVIDIA(0): Config Options in the README.
[ 23.908] (II) NVIDIA(0): Setting mode "nvidia-auto-select"
[ 23.952] (II) Loading extension NV-GLX
[ 24.017] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 24.017] (==) NVIDIA(0): Backing store disabled
[ 24.017] (==) NVIDIA(0): Silken mouse enabled
[ 24.017] (**) NVIDIA(0): DPMS enabled
[ 24.017] (II) Loading extension NV-CONTROL
[ 24.017] (II) Loading extension XINERAMA
[ 24.017] (II) Loading sub module "dri2"
[ 24.017] (II) LoadModule: "dri2"
[ 24.017] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 24.017] (II) Module dri2: vendor="X.Org Foundation"
[ 24.017] compiled for 1.12.2, module version = 1.2.0
[ 24.017] ABI class: X.Org Server Extension, version 6.0
[ 24.017] (II) NVIDIA(0): [DRI2] Setup complete
[ 24.017] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 24.017] (==) RandR enabled
[ 24.017] (II) Initializing built-in extension Generic Event Extension
[ 24.017] (II) Initializing built-in extension SHAPE
[ 24.017] (II) Initializing built-in extension MIT-SHM
[ 24.017] (II) Initializing built-in extension XInputExtension
[ 24.017] (II) Initializing built-in extension XTEST
[ 24.017] (II) Initializing built-in extension BIG-REQUESTS
[ 24.017] (II) Initializing built-in extension SYNC
[ 24.017] (II) Initializing built-in extension XKEYBOARD
[ 24.017] (II) Initializing built-in extension XC-MISC
[ 24.017] (II) Initializing built-in extension SECURITY
[ 24.017] (II) Initializing built-in extension XINERAMA
[ 24.017] (II) Initializing built-in extension XFIXES
[ 24.017] (II) Initializing built-in extension RENDER
[ 24.017] (II) Initializing built-in extension RANDR
[ 24.017] (II) Initializing built-in extension COMPOSITE
[ 24.017] (II) Initializing built-in extension DAMAGE
[ 24.018] (II) Initializing extension GLX
[ 24.296] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 24.296] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 24.296] (II) LoadModule: "evdev"
[ 24.296] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 24.304] (II) Module evdev: vendor="X.Org Foundation"
[ 24.304] compiled for 1.12.0, module version = 2.7.0
[ 24.304] Module class: X.Org XInput Driver
[ 24.304] ABI class: X.Org XInput driver, version 16.0
[ 24.304] (II) Using input driver 'evdev' for 'Power Button'
[ 24.304] (**) Power Button: always reports core events
[ 24.304] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 24.304] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 24.304] (--) evdev: Power Button: Found keys
[ 24.304] (II) evdev: Power Button: Configuring as keyboard
[ 24.304] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[ 24.304] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 24.304] (**) Option "xkb_rules" "evdev"
[ 24.304] (**) Option "xkb_model" "evdev"
[ 24.304] (**) Option "xkb_layout" "us"
[ 24.317] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[ 24.317] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 24.317] (II) Using input driver 'evdev' for 'Power Button'
[ 24.317] (**) Power Button: always reports core events
[ 24.317] (**) evdev: Power Button: Device: "/dev/input/event0"
[ 24.317] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 24.317] (--) evdev: Power Button: Found keys
[ 24.317] (II) evdev: Power Button: Configuring as keyboard
[ 24.317] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0/event0"
[ 24.317] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 24.317] (**) Option "xkb_rules" "evdev"
[ 24.317] (**) Option "xkb_model" "evdev"
[ 24.317] (**) Option "xkb_layout" "us"
[ 24.318] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event14)
[ 24.318] (II) No input driver specified, ignoring this device.
[ 24.318] (II) This device may have been added with another device file.
[ 24.318] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event15)
[ 24.318] (II) No input driver specified, ignoring this device.
[ 24.318] (II) This device may have been added with another device file.
[ 24.318] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event16)
[ 24.318] (II) No input driver specified, ignoring this device.
[ 24.318] (II) This device may have been added with another device file.
[ 24.318] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event17)
[ 24.318] (II) No input driver specified, ignoring this device.
[ 24.318] (II) This device may have been added with another device file.
[ 24.318] (II) config/udev: Adding input device HDA Intel PCH Line Out Side (/dev/input/event10)
[ 24.318] (II) No input driver specified, ignoring this device.
[ 24.318] (II) This device may have been added with another device file.
[ 24.318] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event11)
[ 24.318] (II) No input driver specified, ignoring this device.
[ 24.318] (II) This device may have been added with another device file.
[ 24.318] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event12)
[ 24.318] (II) No input driver specified, ignoring this device.
[ 24.318] (II) This device may have been added with another device file.
[ 24.319] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event13)
[ 24.319] (II) No input driver specified, ignoring this device.
[ 24.319] (II) This device may have been added with another device file.
[ 24.319] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event6)
[ 24.319] (II) No input driver specified, ignoring this device.
[ 24.319] (II) This device may have been added with another device file.
[ 24.319] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event7)
[ 24.319] (II) No input driver specified, ignoring this device.
[ 24.319] (II) This device may have been added with another device file.
[ 24.319] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event8)
[ 24.319] (II) No input driver specified, ignoring this device.
[ 24.319] (II) This device may have been added with another device file.
[ 24.319] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event9)
[ 24.319] (II) No input driver specified, ignoring this device.
[ 24.319] (II) This device may have been added with another device file.
[ 24.319] (II) config/udev: Adding input device UVC Camera (046d:09a1) (/dev/input/event5)
[ 24.319] (**) UVC Camera (046d:09a1): Applying InputClass "evdev keyboard catchall"
[ 24.319] (II) Using input driver 'evdev' for 'UVC Camera (046d:09a1)'
[ 24.319] (**) UVC Camera (046d:09a1): always reports core events
[ 24.319] (**) evdev: UVC Camera (046d:09a1): Device: "/dev/input/event5"
[ 24.319] (--) evdev: UVC Camera (046d:09a1): Vendor 0x46d Product 0x9a1
[ 24.319] (--) evdev: UVC Camera (046d:09a1): Found keys
[ 24.319] (II) evdev: UVC Camera (046d:09a1): Configuring as keyboard
[ 24.319] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1.3/6-1.3:1.0/input/input5/event5"
[ 24.319] (II) XINPUT: Adding extended input device "UVC Camera (046d:09a1)" (type: KEYBOARD, id 8)
[ 24.319] (**) Option "xkb_rules" "evdev"
[ 24.319] (**) Option "xkb_model" "evdev"
[ 24.319] (**) Option "xkb_layout" "us"
[ 24.320] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event3)
[ 24.320] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[ 24.320] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[ 24.320] (**) Logitech USB Receiver: always reports core events
[ 24.320] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event3"
[ 24.320] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc517
[ 24.320] (--) evdev: Logitech USB Receiver: Found keys
[ 24.320] (II) evdev: Logitech USB Receiver: Configuring as keyboard
[ 24.320] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1.8/6-1.8:1.0/input/input3/event3"
[ 24.320] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 9)
[ 24.320] (**) Option "xkb_rules" "evdev"
[ 24.320] (**) Option "xkb_model" "evdev"
[ 24.320] (**) Option "xkb_layout" "us"
[ 24.320] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event4)
[ 24.320] (**) Logitech USB Receiver: Applying InputClass "evdev pointer catchall"
[ 24.320] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[ 24.320] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[ 24.320] (**) Logitech USB Receiver: always reports core events
[ 24.320] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event4"
[ 24.320] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc517
[ 24.320] (--) evdev: Logitech USB Receiver: Found 12 mouse buttons
[ 24.320] (--) evdev: Logitech USB Receiver: Found scroll wheel(s)
[ 24.320] (--) evdev: Logitech USB Receiver: Found relative axes
[ 24.320] (--) evdev: Logitech USB Receiver: Found x and y relative axes
[ 24.320] (--) evdev: Logitech USB Receiver: Found absolute axes
[ 24.320] (II) evdev: Logitech USB Receiver: Forcing absolute x/y axes to exist.
[ 24.320] (--) evdev: Logitech USB Receiver: Found keys
[ 24.320] (II) evdev: Logitech USB Receiver: Configuring as mouse
[ 24.320] (II) evdev: Logitech USB Receiver: Configuring as keyboard
[ 24.320] (II) evdev: Logitech USB Receiver: Adding scrollwheel support
[ 24.320] (**) evdev: Logitech USB Receiver: YAxisMapping: buttons 4 and 5
[ 24.320] (**) evdev: Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 24.320] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1.8/6-1.8:1.1/input/input4/event4"
[ 24.320] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 10)
[ 24.320] (**) Option "xkb_rules" "evdev"
[ 24.320] (**) Option "xkb_model" "evdev"
[ 24.320] (**) Option "xkb_layout" "us"
[ 24.320] (II) evdev: Logitech USB Receiver: initialized for relative axes.
[ 24.320] (WW) evdev: Logitech USB Receiver: ignoring absolute axes.
[ 24.320] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
[ 24.320] (**) Logitech USB Receiver: (accel) acceleration profile 0
[ 24.320] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[ 24.320] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[ 24.320] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/mouse0)
[ 24.320] (II) No input driver specified, ignoring this device.
[ 24.320] (II) This device may have been added with another device file.
[ 24.321] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event2)
[ 24.321] (**) Eee PC WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[ 24.321] (II) Using input driver 'evdev' for 'Eee PC WMI hotkeys'
[ 24.321] (**) Eee PC WMI hotkeys: always reports core events
[ 24.321] (**) evdev: Eee PC WMI hotkeys: Device: "/dev/input/event2"
[ 24.321] (--) evdev: Eee PC WMI hotkeys: Vendor 0 Product 0
[ 24.321] (--) evdev: Eee PC WMI hotkeys: Found keys
[ 24.321] (II) evdev: Eee PC WMI hotkeys: Configuring as keyboard
[ 24.321] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input2/event2"
[ 24.321] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 11)
[ 24.321] (**) Option "xkb_rules" "evdev"
[ 24.321] (**) Option "xkb_model" "evdev"
[ 24.321] (**) Option "xkb_layout" "us"
[ 24.497] (II) evdev: Power Button: Close
[ 24.497] (II) UnloadModule: "evdev"
[ 24.497] (II) evdev: Power Button: Close
[ 24.497] (II) UnloadModule: "evdev"
[ 24.497] (II) evdev: UVC Camera (046d:09a1): Close
[ 24.497] (II) UnloadModule: "evdev"
[ 24.497] (II) evdev: Logitech USB Receiver: Close
[ 24.497] (II) UnloadModule: "evdev"
[ 24.497] (II) evdev: Logitech USB Receiver: Close
[ 24.497] (II) UnloadModule: "evdev"
[ 24.497] (II) evdev: Eee PC WMI hotkeys: Close
[ 24.497] (II) UnloadModule: "evdev"
[ 24.680] Server terminated successfully (0). Closing log file.
Contents of Xorg.conf:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 295.53 ([email protected]) Sat May 12 00:34:20 PDT 2012
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
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"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection
Last edited by Glupoi652 (2012-06-07 20:51:53)

windscape wrote:
wgetfree wrote:It may be a stupid question but do you have all the Xorg dependencies?
It may even be simpler than that. If this is a new installation, a desktop environment or window manager may not be installed. In that case, the Xorg server has nothing to do. Install a desktop environment or window manager and see if Xorg continues running once it has something to do.
Listen to this man. What I meant by Xorg dependencies is that people usually install xterm, xclock, etc so they have a very basic WM set up so they can see that Xorg is in fact working. Try setting up a .xinitrc with the following in it:
exec startxfce4 --with-ck-launch
Or even try to launch it manually with:
$ startxfce4

How can I configure a VM to boot from USB key in Virtual PC of Windows 7?

Hi all,
I want to boot up with a USB key to install a new VM on Windows 7. I heared that Microsoft Virtual PC begins to support USB device on Windows 7. How can i configure it? I don't find any virtual USB device in VM settings on my Windows 7 box.
Thanks for any help.
Scorprio
TechNet Software Assurance Managed Newsgroup MCTS: Windows Vista | Exchange Server 2007 MCITP: Enterprise Support Technician | Server & Enterprise Admin

Hi all,
I want to boot up with a USB key to install a new VM on Windows 7. I heared that Microsoft Virtual PC begins to support USB device on Windows 7. How can i configure it? I don't find any virtual USB device in VM settings on my Windows 7 box.
Thanks for any help.
Scorprio
TechNet Software Assurance Managed Newsgroup MCTS: Windows Vista | Exchange Server 2007 MCITP: Enterprise Support Technician | Server & Enterprise Admin
Virtual PC does not support USB. Windows 7 XP Mode Virtual Machine supports the use of USB devices. Virtual PC and Windows 7 XP Mode VM are not the same thing!

MBAM Clients not able to recover key from MBAM Console

For the first time I am installing MBAM with SCCM intergration. Everything has successfully installed, but having problem getting clients to respond to the MBAM administration console. I keep getting "Please enter correct Machine Information"(for
Manage TPM) or "Recovery keys not found" (Drive Recovery).
When I checked SCCM reports, it shows the one computer i'm working on at 100% compliant. Also the the recovery key is showing in AD.
Somewhere i think i'm not connected to the database. Please help?

It sounds like you might not have configured the 'Configure MBAM Services' policy, or you have conflicting policies between the default BitLocker policies and the MBAM policies. Please see the article 'Planning
for MBAM 2.0 Group Policy Requirements', where it states:
If you do not configure or if you disable this policy setting, the Key recovery information will not be saved, and status report and key recovery activity will not be reported to server. When this setting is set to
Recovery Password and key package, the recovery password and key package will be automatically and silently backed up to the configured key recovery server location.
Hope this helps,
David
MDOP on the Springboard Series on TechNet

[Xorg] strange scrolling

I recently updated Xorg and when I restarted X everything worked just fine. But when I opened Firefox and scrolled up and down (with mouse or scroll bar) the current page scrolled very slow and painful. First I though is was a Firefox only problem, but when I opened Rox and Opera they had the same problem. I did some search on Google, and ArchLinux but I could not find a solution.
Pleas can someone help me with my problem?
<_abe>

I have installed and configured the ati-drive on my computer and now I don't have any problems anymore with the scrolling or anything else. So I advice you to install the official ati or nvidia drives if you have a ati or nvidia cart. I also advice you to read the following pages:http://wiki.archlinux.org/index.php/Xorg and especially: http://wiki.archlinux.org/index.php/Xorg7
I hope this informations is as helpful to you as it was to me.
<_abe>

Xorg strange issue

hello, this is sort of an oddball issue. i did a system update the other day and ever since my Xorg server is acting weird. whenever I start up my machine i am greeted with the sLiM login screen. I log in and then nothing. just a blank black screen. I switch over to tty1 and do sudo killall X. X then restarts itself somehow and i finally get my desktop. magic? maybe try to reconfigure xorg?
Also on an unrelated note. sometimes when i boot my system complains about edd? i have to add edd=off to the kernel line to get it to boot. any ideas?
here is the error.
thanks for the help

You probably have "respawn" in /etc/inittab next to x:5:. That makes slim restart every time a session ends, which may be after logging out or after killing X. That's why X restarts when you kill it.
Your problem seems to be that your DE has some problem that prevents from starting correctly the first time, but not the second. Perhaps there is some kind of race condition, but I'm lost at this point.

Are there any left and right cursor key on virtual keyboard?

I am a apple new iPad user, first use ipad. I agree the virtual keyboard used idea, but I am not use to keyboard without left/right cursor,
Especially point words with my bigger finger.
Who can teach me to solve this problem? Thank you.

WenshuTw wrote:
Don't you think so?
No, I don't think so.
Submit your feedback directly to Apple requesting this feature using the appropriate link on the Feedback page:
http://www.apple.com/feedback

Strange Entries in System and Console Logs

I have some strange entries in my system and console logs. In the system log, I regularly see these entries:
Feb 24 21:07:29 joseph-youngs-computer /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: Error: owner of process not logged in on console - exiting.
Feb 24 21:20:32 joseph-youngs-computer kernel[0]: (82: coreservicesd)tfp: failed on 0:
In my console log, I regularly find these entries:
2006-02-25 09:23:24 -0600
2006-02-24 21:07:30.530 loginwindow[803] FSResolveAliasWithMountFlags returned err = -43
On occasion, I find something like this in my console log:
Assert failed: /Users/dave/dev/flash/player/FlashPlayer/platform/mac/plugins/../../../core/spl ay.cpp:7105
I admit to being something of a novice with the Mac, so I am not sure what to make of these entries, though I never noticed anything like this on my eMac, or on my prior iMac. Also, on the entry above, there are no users named dave on my Mac.
Has anyone else noticed this, and can anyone shed any light on what these messages mean?

Resolved with a clean install.

Need an xorg.conf to use inside virtual box

Hi,
Just setup virtualbox on my work windows 7 thinkpad, installed Arch but its been so long since I have done a fresh install!
I have installed X and hal, but everytime I start X I still cant use the keyboard and mouse!!!
Is anyone able to supply me with a basic xorg.conf file and hal .fdi files that I can use just so I can get the display working?
Thanks.

wonder wrote:did you actually started hal daemon before starting X?
/facepalm
Thanks

[SOLVED] Dead keys on console in UTF-8 locale

Hello,
I want to share something interesting I found out about dead keys support on the Linux console (i.e., without X).
I live in Canada and use the "Canadian French" keyboard, which uses dead keys for several diacritical marks (e.g., to type ê I push and release the ^ key, then type the e key). It works perfectly under X, but I was unable to type any character using dead keys on the console. On the other hand, non-ASCII characters like "é" that do not use dead keys worked perfectly.
After some googling, I found many posts claiming the kernel did not support dead keys when the console was in Unicode mode. So I changed the locale to a non-UTF-8 setting in /etc/rc.conf, and indeed dead keys started working. But this was not useful to me, since editing UTF-8 files resulted in gibberish, and I did not want to regress back to Latin1 encoding or have to support both encodings. I tried many combinations of settings, but none worked. For a few days, I thought there was no way to have dead keys and Unicode working on the Console.
But then I started to install Arch Linux on another computer and noticed that when I set the keyboard to Canadian French with the "km" utility before installing (the keymap is called "cf"), dead keys worked, even though the locale was Unicode! So there was a way to do it.
I started digging and trying new things, and found out that after the following incantations, I was able to enable dead keys for Unicode on the console:
kbd_mode -a
sudo loadkeys cf
kbd_mode -u
This sets the console to ASCII mode, loads the "cf" keymap, and sets the console back to Unicode. I found it by trial and error, and I have no idea why it works or whether it breaks anything. I'm posting here to ask if there are easier ways to have a functional Canadian French keyboard on the console, and to document what I did in case someone has a similar problem.
Last edited by pguertin (2010-01-23 21:44:33)

I have the exact same issue.
The weird thing for me is that before I was using gentoo and never had a problem with dead keys and unicode. Also, I confirm that dead keys is working when booting from the archlinux installation cd. Either run 'loadkeys cf' rigth after login or pass 'keymap=cf' as a boot parameter to the kernel line by editing it in grub before booting.
Your solution is interesting, however the cf.map.gz file is the same on the installation cd (and on my gentoo system) so it should works without editing it.
In my quest to solve this issue, I found something interesting. I added the 'keymap' hook in /etc/mkinitcpio.conf and regenerated the image by issuing
mkinitcpio -g /boot/kernel26.img
This alone didn't solved the issue, but then I REMOVED the keymap assignation in /etc/rc.conf (i.e. leaving it as
KEYMAP=
), rebooted... and voilà, it now works.
Furthermore, now if I run
sudo loadkeys cf
after login it stops working (well of course because it's the same as defining KEYMAP="cf" in /etc/rc.conf). Issuing the 3 commands of your first post make it works again. OK so I did one more test: boot from the archlinux installation cd by adding the 'keymap=cf' boot parameter to the kernel line and then run 'loadkeys cf' after login to see if it breaks dead keys. But no, it still works.
So is this issue comes from a newer version of the kernel/loadkeys/mkinitcpio/...? How different is the kernel and initramfs images of the installation cd compared to the installed system ?

[SOLVED] xorg 1.5 + keyboard key

Certain of the keyboard keys do not work after the upgrade to xorg 1.5 These include the arrow keys and the page up and page down keys (possibly more but I didn't do a thorough check). They work fine in the virtual consoles 1-6, however.
i'm using the "keyboard" driver in the xorg.conf, btw.
Last edited by vik (2008-11-30 19:03:14)

mutlu_inek wrote:
You don't need to put the driver into xorg.conf. It has been deprecated. You should read the news and the wiki page.
If you are using KDE, see here:
http://bbs.archlinux.org/viewtopic.php? … 36#p456436
I'm using gnome. I understand that it was shifted to evdev, I've already read both the wiki and news.

No dead keys in Xorg, strange dead keys in virtual consoles

Similar Messages

Maybe you are looking for