On 2011-05-04 19:32, Julien Cristau wrote:
Both, really.
Well, my sound device stopped working after an upgrade. I can see my
device listed as usual in
/proc/asound/cards:
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xf0600000 irq 47
1 [default ]: USB-Audio - Microsoft Digital Sound System
Microsoft Microsoft Digital Sound System at
usb-0000:00:1a.7-2.4, full speed
2 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xf0210000 irq 48
But it is not available to use, as it doesn't show up in kde control
panel. When I was looking for error information, I've checked into my
/etc/var/Xorg.0.log and found the following:
42.829] (II) config/udev: Adding input device Microsoft Microsoft
Digital Sound System 80 (/dev/input/event3)
[ 42.829] (**) Microsoft Microsoft Digital Sound System 80: Applying
InputClass "evdev keyboard catchall"
[ 42.829] (II) Using input driver 'evdev' for 'Microsoft Microsoft
Digital Sound System 80'
[ 42.829] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 42.829] (**) Microsoft Microsoft Digital Sound System 80: always
reports core events
[ 42.829] (**) Microsoft Microsoft Digital Sound System 80: Device:
"/dev/input/event3"
[ 42.829] (--) Microsoft Microsoft Digital Sound System 80: Found keys
[ 42.829] (II) Microsoft Microsoft Digital Sound System 80:
Configuring as keyboard
[ 42.829] (**) Option "config_info"
"udev:/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2.4/1-2.4:1.2/input/inpu$
[ 42.829] (II) XINPUT: Adding extended input device "Microsoft
Microsoft Digital Sound System 80" (type: KEYBOARD)
[ 42.829] (**) Option "xkb_rules" "evdev"
[ 42.829] (**) Option "xkb_model" "pc105"
[ 42.829] (**) Option "xkb_layout" "pt"
Being no expert, I assumed that this would be an incorrect behavior.
Off course, I'm not saying that the problem is definitely xinput
related, but I had no other info on what package to "blame".
As for its severity, I thought that since it has a major effect on the
usability of a package (in this case, I cannot use my sound device), it
should be considered normal.
Now, do you think this bug report does not belong to xinput, or isn't
important, or both?
Any hints:
Cheers:
Pedro
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]