Ask Your Question
2

Xorg Logs show misdetection of my DVB USB tuner device as a Keyboard - How to Resolve ?

asked 2014-01-30 18:39:24 -0600

dmm gravatar image

updated 2014-01-30 20:17:01 -0600

FranciscoD_ gravatar image

Fedora 20 / Gnome Destop / 64 bit / Kworld 395U DVB-T Tuner

While searching the Xorg logs for a problem to do with Fedora front screen not responding to keyboard after PC being unattended for an hour - mouse moved OK but keyboard (ESC) will not respond to take me to password entrry screen …… and whiule browsing logs to debug it I found a more concerning 2nd problem - so one problem at a time …….

Background : I have been having erratic behaviour with my USB - DVB-T device - it would sometimes become unrecognised by the system after a period of say couple hours ie failed to initialize errors in dmesg | grep DVB and so on

While browsing the Xorg Logs i found this below - Should I be concerned with the fact that the DVB tuner it reports as a keyboard in the logs - I reckon i should be ?? see below

$ cat Xorg.0.log | grep 395
[    33.464] (II) config/udev: Adding input device KWorld USB DVB-T TV Stick II (VS-DVB-T 395U) (/dev/input/event5)
[    33.464] (**) KWorld USB DVB-T TV Stick II (VS-DVB-T 395U): Applying InputClass "evdev keyboard catchall"
[    33.464] (**) KWorld USB DVB-T TV Stick II (VS-DVB-T 395U): Applying InputClass "system-keyboard"
[    33.464] (II) Using input driver 'evdev' for 'KWorld USB DVB-T TV Stick II (VS-DVB-T 395U)'
[    33.464] (**) KWorld USB DVB-T TV Stick II (VS-DVB-T 395U): always reports core events
[    33.464] (**) evdev: KWorld USB DVB-T TV Stick II (VS-DVB-T 395U): Device: "/dev/input/event5"
[    33.464] (--) evdev: KWorld USB DVB-T TV Stick II (VS-DVB-T 395U): Vendor 0x1b80 Product 0xe39b
[    33.464] (--) evdev: KWorld USB DVB-T TV Stick II (VS-DVB-T 395U): Found keys
[    33.464] (II) evdev: KWorld USB DVB-T TV Stick II (VS-DVB-T 395U): Configuring as keyboard
[    33.464] (II) XINPUT: Adding extended input device "KWorld USB DVB-T TV Stick II (VS-DVB-T 395U)" **(type: KEYBOARD, id 10)**

by the way tuner still works mostly - but it can uninstall detach itself from the system occasionally (not physically ) but from an OS / driver point of view

What can i do to fix this mis detection of my device ? thank you all Don

edit retag flag offensive close merge delete

2 Answers

Sort by » oldest newest most voted
1

answered 2014-02-22 21:32:22 -0600

QuLogic gravatar image

I do not think it is a problem that the tuner device is detected as a keyboard. A lot of devices show up that way, even though they have no visible way to input anything. For example, the power button shows up as a keyboard, even though it's really just one button. On my laptop, the lid switch is a keyboard. Even the integrated webcam shows up as a keyboard (though there's no switch or any physical input related to it).

But anyway, the KWorld product page says it optionally comes with a remote control. The device could treat input from that as a "keyboard". It is fairly likely that they use the same hardware whether you have a remote or not, so it will always report itself as a keyboard even if you haven't got the remote..

edit flag offensive delete link more
0

answered 2014-03-29 08:53:19 -0600

dmm gravatar image

thank you for your answer QuLogic

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2014-01-30 18:39:24 -0600

Seen: 371 times

Last updated: Mar 29 '14