Hi!
I have tried several months to use display managers (DM) in sid, but every time the program tries to start a DM (supposedly the X-server) the keyboard is disconnected. I have tried every DM in my installation with the same result. Its utterly irritating because only method to escape the situation is to disconnect the PC from electricity. I have updated the kernel every time a new is released in debian sid. For me it is newertheless no catastroph because i use also debian Jessie. Could someone give me a hint how I can continue to resolv the problem.
jarvini.

A few questions come to mind:

1) What happens when you launch X with startx? Does the keyboard work then?
2) Does your mouse work when the keyboard doesn't? If not, it's a problem with evdev or udev.
3) Have you looked at /var/log/Xorg.0.log? In particular, can you see the keyboard being recognised? For example, I have:
My instinct is to think it's a udev rule problem. Is there a significant difference in the udev input rules files (for example evdev-rules) between Jessie and Sid?

1 members found this post helpful.

Thank you for responding.
to answer your questions.
1) Launching with startx behaves exactly the same way as with trying with DM:s
2) Mouse stops working at the same time. I also suspected udev. In fact the issue appeared after a update.
3) /var/log/xorg.0.log does not tell me anything. Here are the trailing messages:
[ 3315.843] (**) AT Translated Set 2 keyboard: always reports core events
[ 3315.843] (**) Option "Device" "/dev/input/event1"
[ 3315.843] (**) Option "_source" "server/udev"
[ 3315.844] (II) event1 - (II) AT Translated Set 2 keyboard: (II) is tagged by udev as: Keyboard
[ 3315.844] (II) event1 - (II) AT Translated Set 2 keyboard: (II) device is a keyboard
[ 3315.844] (II) event1 - (II) AT Translated Set 2 keyboard: (II) device removed
[ 3315.853] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event1"
[ 3315.853] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
[ 3315.853] (**) Option "xkb_model" "pc105"
[ 3315.853] (**) Option "xkb_layout" "fi"
[ 3315.853] (**) Option "xkb_options" "compose:rwin,terminate:ctrl_alt_bksp"
[ 3315.854] (II) event1 - (II) AT Translated Set 2 keyboard: (II) is tagged by udev as: Keyboard
[ 3315.854] (II) event1 - (II) AT Translated Set 2 keyboard: (II) device is a keyboard
[ 3315.855] (II) config/udev: Adding input device PC Speaker (/dev/input/event0)
[ 3315.855] (II) No input driver specified, ignoring this device.
[ 3315.855] (II) This device may have been added with another device file.
[ 3315.862] (**) MOSART Semi. Wireless Keyboard & Mouse: Applying InputClass "evdev pointer catchall"
[ 3315.862] (**) MOSART Semi. Wireless Keyboard & Mouse: Applying InputClass "evdev keyboard catchall"
[ 3315.862] (**) MOSART Semi. Wireless Keyboard & Mouse: Applying InputClass "libinput pointer catchall"
[ 3315.862] (**) MOSART Semi. Wireless Keyboard & Mouse: Applying InputClass "libinput keyboard catchall"
[ 3315.862] (II) Using input driver 'libinput' for 'MOSART Semi. Wireless Keyboard & Mouse'
[ 3315.862] (**) MOSART Semi. Wireless Keyboard & Mouse: always reports core events
[ 3315.862] (**) Option "Device" "/dev/input/event6"
[ 3315.862] (**) Option "_source" "_driver/libinput"
[ 3315.863] (II) libinput: MOSART Semi. Wireless Keyboard & Mouse: is a virtual subdevice
[ 3315.863] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.1/0003:062A:0102.0002/input/input8/event6"
[ 3315.863] (II) XINPUT: Adding extended input device "MOSART Semi. Wireless Keyboard & Mouse" (type: KEYBOARD, id 12)
[ 3315.863] (**) Option "xkb_model" "pc105"
[ 3315.863] (**) Option "xkb_layout" "fi"
[ 3315.863] (**) Option "xkb_options" "compose:rwin,terminate:ctrl_alt_bksp"
[ 3323.953] (WW) RADEON(0): flip queue failed: Invalid argument
[ 3323.953] (WW) RADEON(0): Page flip failed: Invalid argument
[ 3323.954] (WW) RADEON(0): flip queue failed: Invalid argument
[ 3323.954] (WW) RADEON(0): Page flip failed: Invalid argument

There are so many udev-rules so I cant know whitch to compare, can you help?

jarvini

Certainly the evdev rules, anything with input in the title and the default rules. I notice that your keyboard uses libinput and Debian has a udev file for that too. And I've noticed an xorg-xkb.rules file. Doing a diff on the /lib/udev/rules.d directories for sid and jessie might be an idea too, since you say jessie works.

1 members found this post helpful.

i recently saw a very similar thread and in the end the fault was with a custom script that disabled a device identified via libinput (xinput) ids, only the id had changed meanwhile...
anyhow, is there anything non-standard in your system that you should tell us about?

Thank you for the suggestions.
I will compare the files. Doing a diff on the /lib/udev/rules.d directories could scarsely be to any help it generates 378KB with differences.

jarvini

Yes, I use a non-standard kernel because I do not want to use a initramfile. I compile every kernel myself but that cant be the fault because I often use the same kernel in both OS:s

jarvini

ok, maybe i was off with my suggestion but this just shows how much often goes unsaid in the initial post.
what custom kernel? could it have something ot do with the issue? show us some output.

long-pressing the power button usually does the same.

The latest kernel I use is from linux-source-4.13.10-1 compiled by me but as I said it can't be this that is causing the problem. What kind of "output" are you thinking about.

jarvini

I have now compared every rulesfile in the rules.d directory including your suggestions. diff didn't found any differences whatsoever in non of the rulefiles. This is little astonishing Jesse and sid uses exact the same rules?? The other files in the udev directory differ much. Do you have more suggestions?

jarvini