Differences of the device running attached to a computer running a 64 bit kernel compared to the 32 bit version: - Volume control buttons "+" and "-" are not repeat buttons. - Some commands given from the remote control are recalled up to minutes after they've been issued and are then delivered to the application. This happens even if the device is dis-/reconnected. - With enabled debug output (cf. patch below) in cinergyT2-core.c the driver continuously outputs lines like these cinergyT2: key: ed 41 be 3 0 cinergyT2: key: 72 73 8c 6d 65 cinergyT2: key: 64 65 9a 63 6f cinergyT2: key: 75 64 9b 2f 63 at a rate of about 16 per second to the system log. --- linux/drivers/media/dvb/dvb-usb__/cinergyT2-core.c 2010-04-02 00:59:14.000000000 +0200 +++ linux/drivers/media/dvb/dvb-usb/cinergyT2-core.c 2010-05-31 19:18:35.000000000 +0200 @@ -29,6 +29,9 @@ #include "cinergyT2.h" +#undef deb_rc +#define deb_rc(a...) err(a) + /* debug */ int dvb_usb_cinergyt2_debug;
There were lots of changes at the RC code since 2.6.32 or even 2.6.35. You should test it with the Kernel 3.0 and see if the problems are still there. Also, some IR sensors are very sensible to infrared interferences. Be sure that the sensor is not receiving direct sunlight or direct light from a lamp.
(In reply to comment #1) > There were lots of changes at the RC code since 2.6.32 or even 2.6.35. You > should test it with the Kernel 3.0 and see if the problems are still there. Checked it with 3.0.1 and the problems are - slightly modified - still there: - Sometimes after switching channels "+"/"-" behave as repeat buttons for some time and then stop sometimes even while still being pressed. - Late delivery of RC commands still happens but I have not checked the disconnect/reconnect. - The lines are still printed to the system logs. > Also, some IR sensors are very sensible to infrared interferences. Be sure > that > the sensor is not receiving direct sunlight or direct light from a lamp. There is no direct light source shining on the sensor.
Since the latest 3.0.38 the phantom data
Since the latest 3.0.38 the phantom data problem is gone and the repeat buttons (e.g. volume) now work. In 3.0.35 was affected by all of the three problems, 3.0.37 had at least the repeat issue (did not check other issues).
The issue is back again in 3.0.43.
Can we close this as the kernel for your testing is obsolete. If you would like to test against a newer kernel and see if this bug is still valid. Cheers Nick
The bug is still valid. I have compiled the modules with CONFIG_DVB_USB_DEBUG=y. As soon as I enable rc debugging echo 32 > /sys/module/dvb_usb/parameters/debug echo 32 > /sys/module/dvb_usb_cinergyT2/parameters/debug the syslog fills with kernel: repeated key (non repeatable) and kernel: key: x x xx xx xx [x stands for a hex digit] messages.