pinnacle pctv 110i remote does not work in feisty

[pleban]

feisty with all recent updates.
TV card pinnacle 110i (saa7134 module, card=77)
remote detected by kernel

dmesg:
   41.065255] saa7130/34: v4l2 driver version 0.2.14 loaded
[ 41.065844] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
[ 41.065856] ACPI: PCI Interrupt 0000:04:08.0[A] -> Link [APC1] -> GSI 16 (level, low) -> IRQ 21
[ 41.065864] saa7133[0]: found at 0000:04:08.0, rev: 209, irq: 21, latency: 32, mmio: 0xfdbfe000
[ 41.065870] saa7133[0]: subsystem: 11bd:002e, board: Pinnacle PCTV 40i/50i/110i (saa7133) [card=77,insmod option]
[ 41.065880] saa7133[0]: board init: gpio is 200e000
  41.178669] input: Pinnacle PCTV as /class/input/input6
[ 41.178700] ir-kbd-i2c: Pinnacle PCTV detected at i2c-2/2-0047/ir0 [saa7133[0]]
[ 41.218532] saa7133[0]: i2c eeprom 00: bd 11 2e 00 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
[ 41.218540] saa7133[0]: i2c eeprom 10: ff e0 60 02 ff 20 ff ff ff ff ff ff ff ff ff ff
[ 41.218546] saa7133[0]: i2c eeprom 20: 01 2c 01 23 23 01 04 30 98 ff 00 e2 ff 22 00 c2
[ 41.218553] saa7133[0]: i2c eeprom 30: 96 ff 03 30 15 01 ff 15 0e 6c a3 ea 03 c4 6e 26
[ 41.218559] saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 41.218565] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 41.218571] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 41.218577] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 41.390591] tuner 2-004b: chip found @ 0x96 (saa7133[0])
[ 41.442578] tuner 2-004b: setting tuner address to 61
[ 41.482584] tuner 2-004b: type set to tda8290+75a
[ 41.765592] input: ImPS/2 Generic Wheel Mouse as /class/input/input7
[ 42.946887] tuner 2-004b: setting tuner address to 61
[ 42.994895] tuner 2-004b: type set to tda8290+75a
[ 44.341590] saa7133[0]: registered device video0 [v4l2]
[ 44.341701] saa7133[0]: registered device vbi0
[ 44.341813] saa7133[0]: registered device radio0
[ 44.427788] ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 22
[ 44.427793] ACPI: PCI Interrupt 0000:00:10.1[B] -> Link [AAZA] -> GSI 22 (level, low) -> IRQ 17
[ 44.427816] PCI: Setting latency timer of device 0000:00:10.1 to 64
[ 44.452443] saa7134 ALSA driver for DMA sound loaded
[ 44.452470] saa7133[0]/alsa: saa7133[0] at 0xfdbfe000 irq 21 registered as card -2

lsinput:
/dev/input/event4
   bustype : BUS_I2C
   vendor : 0x0
   product : 0x0
   version : 0
   name : "Pinnacle PCTV"
   phys : "i2c-2/2-0047/ir0"
   bits ev : EV_SYN EV_KEY EV_REP

mar@myszka:~$ uname -a
Linux myszka 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux

no events are generated from the remote

[pleban (marek-zebrowski-gmail)]

It does not work in gutsy either

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Sebastian Cardello (guindous)]

I have the same problem with Intrepid Ibex 8.10 Ubuntu/Mythbuntu version. When I load the the saa7134 module with the ir_debug option (sudo modprobe saa7134 ir_debug=1), the syslog (/var/log/syslog) says:

Jan 21 07:12:35 nena kernel: [ 1180.224162] Pinnacle PCTV/ir: read error
Jan 21 07:12:35 nena kernel: [ 1180.324163] Pinnacle PCTV/ir: read error
Jan 21 07:12:35 nena kernel: [ 1180.424162] Pinnacle PCTV/ir: read error
Jan 21 07:12:37 nena kernel: [ 1183.116153] Pinnacle PCTV/ir: read error

Could anyone confirm the same problem and the same logs?

[Leann Ogasawara (leannogasawara)]

Hi guindous,

Could you also capture and attach your dmesg output after you load the module. Just curious what additional error messages may get logged. Thanks.

[Sebastian Cardello (guindous)]

Hi Leaan

First, thanks for answer to my problems. You are the only one that has answered something so far. :(

I attach all the dmesg info. The saa7134 and ir-kbd-i2c modules are loaded at [ 10.697919] mark. IMHO, there is no others error messages.

I've done a lot of research during this “fight” with this remote. I've tried with different distros (openSUSE 11.1, Knopmyth R5 and Mythdora 10.21) with no success, and the same logs!. Furthermore I've also tested the remote with Windows XP and it worked, so it's not a hardware malfunction either.

Also I've reported this “bug” (I think) to the v4l2 mail list, and nobody has answered (https://www.redhat.com/mailman/private/video4linux-list/2009-January/msg00456.html). I suggest you read that post. There is even more information.

If I can help with any other info, just ask me. I need some orientation with this problem because I think that I've tried everything that I could do.

Thanks again.

--
guindous
(el Seba)

[Leann Ogasawara (leannogasawara)]

Thanks guindous,

Can you do one extra test, can you try the latest pre-release of Jaunty (currently Alpha4) and confirm the issue remains - http://cdimage.ubuntu.com/releases/jaunty/ . You should be able to test using a LiveCD. Jaunty contains a newer 2.6.28 based kernel. Please let us know your results. Thanks.

[Sebastian Cardello (guindous)]

I've done the test with the alpha-5 jaunty livecd and I can confirm the issue with the new 2.6.28 kernel. I'm pretty sure that is a v4l2 saa7134 driver bug, but no one in the v4l-list is interested in it.

[Taka Suphler (suphler)]

Do you try to load lirc_i2c kernel module?

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]