Pinnacle PCTV 310i Remote: i2c 'ERROR: NO_DEVICE'

Pinnacle PCTV 310i Remote: i2c 'ERROR: NO_DEVICE'

[picciuX]

hi all.
Someone could explain to me what does 'saa7133[0]: i2c xfer: < 8f
ERROR: NO_DEVICE' mean? It appears in my logs exactly when I push a
button on my Pinnacle PCTV 310i remote... and obviously the remote
seems not to work.... this is why I enabled debug output.
Seems strange to me that I found tutorials on the net talking about
this board, and reporting experiences of happy users because the board
and the remote both *just work*. In my case, and some other I found
googling around, the remote simply doesn't work.
An user had two cards, buyed 6 months one after the other: the first
*just worked*, the second didn't.
Mine is new, and Pinnacle changed the name in "PCTV Hybrid Pro PCI",
but pci ids are the very same of PCTV 310i. Maybe did something change
on this cards?
I searched the net, with no luck.
Today i tried enabling saa7134 debug, loading the module like this:

modprobe saa7134 ir_debug=1 i2c_debug=1 gpio_tracking=1

My syslog started filling the screen with i2c xfer lines. When I
pushed a button on the remote, immediately appeared those "ERROR:
NO_DEVICE" lines, like this:

[ 1065.227063] saa7133[0]: i2c xfer: < 8f =ef =56 =40 =93 >
[ 1065.334805] saa7133[0]: i2c xfer: < 8f =6f =fd =d4 =4f >
[ 1065.443552] saa7133[0]: i2c xfer: < 8f =6a =5d =d3 =cd >
[ 1065.550300] saa7133[0]: i2c xfer: < 8f =b2 =6c =5e =28 >
[ 1065.658042] saa7133[0]: i2c xfer: < 8f =5c =02 =36 =f5 >
[ 1065.765786] saa7133[0]: i2c xfer: < 8f =07 =fc =dd =5b >
[ 1065.874533] saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
[ 1065.974329] saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
[ 1066.073096] saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
[ 1066.172860] saa7133[0]: i2c xfer: < 8f =ec =de =bd =fb >
[ 1066.280569] saa7133[0]: i2c xfer: < 8f =32 =d5 =13 =75 >
[ 1066.388315] saa7133[0]: i2c xfer: < 8f =af =6a =8f =01 >
[ 1066.496064] saa7133[0]: i2c xfer: < 8f =60 =20 =00 =10 >

I repeated the test more than once, just to be sure of the
relationship between remote button presses and the *ERROR* lines.

Kernel is stock ubuntu 8.04 (2.6.24-21). I tried also compiling and
using latest v4l-dvb from mercurial: but besides some problems with
saa7134_alsa (probably latest v4l-dvb needs a more recent kernel),
nothing changed with the remote.

Someone can shed some light on this?

I can post the entire dmesg output from module load to module unload,
if it could be useful.

Thanks a lot...
picciuX

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Pinnacle PCTV 310i Remote: i2c 'ERROR: NO_DEVICE'

[hermann pitton]

Hi,

Am Freitag, den 31.10.2008, 10:31 +0100 schrieb picciuX:
> hi all.
> Someone could explain to me what does 'saa7133[0]: i2c xfer: < 8f
> ERROR: NO_DEVICE' mean? It appears in my logs exactly when I push a
> button on my Pinnacle PCTV 310i remote... and obviously the remote
> seems not to work.... this is why I enabled debug output.
> Seems strange to me that I found tutorials on the net talking about
> this board, and reporting experiences of happy users because the board
> and the remote both *just work*. In my case, and some other I found
> googling around, the remote simply doesn't work.
> An user had two cards, buyed 6 months one after the other: the first
> *just worked*, the second didn't.
> Mine is new, and Pinnacle changed the name in "PCTV Hybrid Pro PCI",
> but pci ids are the very same of PCTV 310i. Maybe did something change
> on this cards?
> I searched the net, with no luck.
> Today i tried enabling saa7134 debug, loading the module like this:
> 
> modprobe saa7134 ir_debug=1 i2c_debug=1 gpio_tracking=1
> 
> My syslog started filling the screen with i2c xfer lines. When I
> pushed a button on the remote, immediately appeared those "ERROR:
> NO_DEVICE" lines, like this:
> 
> [ 1065.227063] saa7133[0]: i2c xfer: < 8f =ef =56 =40 =93 >
> [ 1065.334805] saa7133[0]: i2c xfer: < 8f =6f =fd =d4 =4f >
> [ 1065.443552] saa7133[0]: i2c xfer: < 8f =6a =5d =d3 =cd >
> [ 1065.550300] saa7133[0]: i2c xfer: < 8f =b2 =6c =5e =28 >
> [ 1065.658042] saa7133[0]: i2c xfer: < 8f =5c =02 =36 =f5 >
> [ 1065.765786] saa7133[0]: i2c xfer: < 8f =07 =fc =dd =5b >
> [ 1065.874533] saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
> [ 1065.974329] saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
> [ 1066.073096] saa7133[0]: i2c xfer: < 8f ERROR: NO_DEVICE
> [ 1066.172860] saa7133[0]: i2c xfer: < 8f =ec =de =bd =fb >
> [ 1066.280569] saa7133[0]: i2c xfer: < 8f =32 =d5 =13 =75 >
> [ 1066.388315] saa7133[0]: i2c xfer: < 8f =af =6a =8f =01 >
> [ 1066.496064] saa7133[0]: i2c xfer: < 8f =60 =20 =00 =10 >
> 
> I repeated the test more than once, just to be sure of the
> relationship between remote button presses and the *ERROR* lines.
> 
> Kernel is stock ubuntu 8.04 (2.6.24-21). I tried also compiling and
> using latest v4l-dvb from mercurial: but besides some problems with
> saa7134_alsa (probably latest v4l-dvb needs a more recent kernel),
> nothing changed with the remote.
> 
> Someone can shed some light on this?
> 
> I can post the entire dmesg output from module load to module unload,
> if it could be useful.
> 

don't have that remote, but also enable ir-kbd-i2c debug=1.

ir-kbd-i2c: probe 0x7a @ saa7133[0]: no
ir-kbd-i2c: probe 0x47 @ saa7133[0]: no
ir-kbd-i2c: probe 0x71 @ saa7133[0]: no
ir-kbd-i2c: probe 0x2d @ saa7133[0]: no
ir-kbd-i2c: probe 0x7a @ saa7133[1]: no
ir-kbd-i2c: probe 0x47 @ saa7133[1]: no
ir-kbd-i2c: probe 0x71 @ saa7133[1]: no
ir-kbd-i2c: probe 0x2d @ saa7133[1]: no

You should have the device found at 0x47.

Else something has changed or goes wrong.

Cheers,
Hermann


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Pinnacle PCTV 310i Remote: i2c 'ERROR: NO_DEVICE'

[picciuX]

2008/11/2 hermann pitton <hermann-pitton@arcor.de>:

> don't have that remote, but also enable ir-kbd-i2c debug=1.
>
> ir-kbd-i2c: probe 0x7a @ saa7133[0]: no
> ir-kbd-i2c: probe 0x47 @ saa7133[0]: no
> ir-kbd-i2c: probe 0x71 @ saa7133[0]: no
> ir-kbd-i2c: probe 0x2d @ saa7133[0]: no
> ir-kbd-i2c: probe 0x7a @ saa7133[1]: no
> ir-kbd-i2c: probe 0x47 @ saa7133[1]: no
> ir-kbd-i2c: probe 0x71 @ saa7133[1]: no
> ir-kbd-i2c: probe 0x2d @ saa7133[1]: no
>
> You should have the device found at 0x47.
>

In fact i see:

ir-kbd-i2c: probe 0x47 @ saa7133[0]: yes

So everything seemed to go well. But, same story for the rest: ERROR:
NO_DEVICE when i press buttons on the remote.
What seems strange to me is the fact that the driver *reacts* to
remote key presses, but reacts with an error.

Cheers
Matteo

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Pinnacle PCTV 310i Remote: i2c 'ERROR: NO_DEVICE'

[hermann pitton]

Hi Matteo,

Am Dienstag, den 04.11.2008, 15:09 +0100 schrieb picciuX:
> 2008/11/2 hermann pitton <hermann-pitton@arcor.de>:
> 
> > don't have that remote, but also enable ir-kbd-i2c debug=1.
> >
> > ir-kbd-i2c: probe 0x7a @ saa7133[0]: no
> > ir-kbd-i2c: probe 0x47 @ saa7133[0]: no
> > ir-kbd-i2c: probe 0x71 @ saa7133[0]: no
> > ir-kbd-i2c: probe 0x2d @ saa7133[0]: no
> > ir-kbd-i2c: probe 0x7a @ saa7133[1]: no
> > ir-kbd-i2c: probe 0x47 @ saa7133[1]: no
> > ir-kbd-i2c: probe 0x71 @ saa7133[1]: no
> > ir-kbd-i2c: probe 0x2d @ saa7133[1]: no
> >
> > You should have the device found at 0x47.
> >
> 
> In fact i see:
> 
> ir-kbd-i2c: probe 0x47 @ saa7133[0]: yes
> 
> So everything seemed to go well. But, same story for the rest: ERROR:
> NO_DEVICE when i press buttons on the remote.
> What seems strange to me is the fact that the driver *reacts* to
> remote key presses, but reacts with an error.
> 
> Cheers
> Matteo
> 

since you reported the trouble was already visible for you on earlier
kernels, we might try to get a second confirmation at first.

Anyone out there? I'm sending a copy to Ricardo too, who added the
support, not sure if he currently has time to read the list.

Cheers,
Hermann





--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Pinnacle PCTV 310i Remote: i2c 'ERROR: NO_DEVICE'

[Ricardo Cerqueira]

Hi all;

On Thu, 2008-11-06 at 01:09 +0100, hermann pitton wrote:
> Hi Matteo,
> 
> Am Dienstag, den 04.11.2008, 15:09 +0100 schrieb picciuX:
> > 2008/11/2 hermann pitton <hermann-pitton@arcor.de>:
> > 
> > > don't have that remote, but also enable ir-kbd-i2c debug=1.
> > >
> > > ir-kbd-i2c: probe 0x7a @ saa7133[0]: no
> > > ir-kbd-i2c: probe 0x47 @ saa7133[0]: no
> > > ir-kbd-i2c: probe 0x71 @ saa7133[0]: no
> > > ir-kbd-i2c: probe 0x2d @ saa7133[0]: no
> > > ir-kbd-i2c: probe 0x7a @ saa7133[1]: no
> > > ir-kbd-i2c: probe 0x47 @ saa7133[1]: no
> > > ir-kbd-i2c: probe 0x71 @ saa7133[1]: no
> > > ir-kbd-i2c: probe 0x2d @ saa7133[1]: no
> > >


Sorry, I missed the rest of the thread;

In any case, from the above paste, it looks as if you have 2 saa713x
boards in the system, right?

I suspect the bug is somehow related to that (ir-kbd-i2c is getting the
events, but sending them to the wrong board). Have you tried removing
one of them?

--
RC
> > > You should have the device found at 0x47.
> > >
> > 
> > In fact i see:
> > 
> > ir-kbd-i2c: probe 0x47 @ saa7133[0]: yes
> > 
> > So everything seemed to go well. But, same story for the rest: ERROR:
> > NO_DEVICE when i press buttons on the remote.
> > What seems strange to me is the fact that the driver *reacts* to
> > remote key presses, but reacts with an error.
> > 
> > Cheers
> > Matteo
> > 
> 
> since you reported the trouble was already visible for you on earlier
> kernels, we might try to get a second confirmation at first.
> 
> Anyone out there? I'm sending a copy to Ricardo too, who added the
> support, not sure if he currently has time to read the list.
> 
> Cheers,
> Hermann
> 
> 
> 
> 
> 


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Pinnacle PCTV 310i Remote: i2c 'ERROR: NO_DEVICE'

[hermann pitton]

Hi Ricardo,

Am Donnerstag, den 06.11.2008, 00:46 +0000 schrieb Ricardo Cerqueira:
> Hi all;
> 
> On Thu, 2008-11-06 at 01:09 +0100, hermann pitton wrote:
> > Hi Matteo,
> > 
> > Am Dienstag, den 04.11.2008, 15:09 +0100 schrieb picciuX:
> > > 2008/11/2 hermann pitton <hermann-pitton@arcor.de>:
> > > 
> > > > don't have that remote, but also enable ir-kbd-i2c debug=1.
> > > >
> > > > ir-kbd-i2c: probe 0x7a @ saa7133[0]: no
> > > > ir-kbd-i2c: probe 0x47 @ saa7133[0]: no
> > > > ir-kbd-i2c: probe 0x71 @ saa7133[0]: no
> > > > ir-kbd-i2c: probe 0x2d @ saa7133[0]: no
> > > > ir-kbd-i2c: probe 0x7a @ saa7133[1]: no
> > > > ir-kbd-i2c: probe 0x47 @ saa7133[1]: no
> > > > ir-kbd-i2c: probe 0x71 @ saa7133[1]: no
> > > > ir-kbd-i2c: probe 0x2d @ saa7133[1]: no
> > > >
> 
> 
> Sorry, I missed the rest of the thread;
> 
> In any case, from the above paste, it looks as if you have 2 saa713x
> boards in the system, right?

sorry, that was me to illustrate how the difference should look like.
Must be taken from the quadro md8800 machine.

I'm playing around with some other requests concerning remote behaviors,
but have to admit that getting some old PCs running on recent again is
not that much fun and I'm slow.

We have a case, where Asus stuff is not reliable on PCI subsystem IDs.
We can detect the different cards by a difference in the eeprom readout,
but this needs running i2c on saa7134 init2.

However, since input_init is on saa7134 init1, we fail here being too
late. Maybe we should have input init on saa7134 init2 in saa7134-core.
Roman with such a card mailed to me about that. At least I should be
close to be able to test it, but no i2c remote stuff is here.

> I suspect the bug is somehow related to that (ir-kbd-i2c is getting the
> events, but sending them to the wrong board). Have you tried removing
> one of them?

Maybe the card is even flaky in the PCI slot, that's why a second
confirmation would be nice.

Thanks,
Hermann

> --
> RC
> > > > You should have the device found at 0x47.
> > > >
> > > 
> > > In fact i see:
> > > 
> > > ir-kbd-i2c: probe 0x47 @ saa7133[0]: yes
> > > 
> > > So everything seemed to go well. But, same story for the rest: ERROR:
> > > NO_DEVICE when i press buttons on the remote.
> > > What seems strange to me is the fact that the driver *reacts* to
> > > remote key presses, but reacts with an error.
> > > 
> > > Cheers
> > > Matteo
> > > 
> > 
> > since you reported the trouble was already visible for you on earlier
> > kernels, we might try to get a second confirmation at first.
> > 
> > Anyone out there? I'm sending a copy to Ricardo too, who added the
> > support, not sure if he currently has time to read the list.
> > 
> > Cheers,
> > Hermann
> > 


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Pinnacle PCTV 310i Remote: i2c 'ERROR: NO_DEVICE'

[hermann pitton]

Hi,

Am Donnerstag, den 06.11.2008, 02:56 +0100 schrieb hermann pitton:
> Hi Ricardo,
> 
> Am Donnerstag, den 06.11.2008, 00:46 +0000 schrieb Ricardo Cerqueira:
> > Hi all;
> > 
> > On Thu, 2008-11-06 at 01:09 +0100, hermann pitton wrote:
> > > Hi Matteo,
> > > 
> > > Am Dienstag, den 04.11.2008, 15:09 +0100 schrieb picciuX:
> > > > 2008/11/2 hermann pitton <hermann-pitton@arcor.de>:
> > > > 
> > > > > don't have that remote, but also enable ir-kbd-i2c debug=1.
> > > > >
> > > > > ir-kbd-i2c: probe 0x7a @ saa7133[0]: no
> > > > > ir-kbd-i2c: probe 0x47 @ saa7133[0]: no
> > > > > ir-kbd-i2c: probe 0x71 @ saa7133[0]: no
> > > > > ir-kbd-i2c: probe 0x2d @ saa7133[0]: no
> > > > > ir-kbd-i2c: probe 0x7a @ saa7133[1]: no
> > > > > ir-kbd-i2c: probe 0x47 @ saa7133[1]: no
> > > > > ir-kbd-i2c: probe 0x71 @ saa7133[1]: no
> > > > > ir-kbd-i2c: probe 0x2d @ saa7133[1]: no
> > > > >
> > 
> > 
> > Sorry, I missed the rest of the thread;
> > 
> > In any case, from the above paste, it looks as if you have 2 saa713x
> > boards in the system, right?
> 
> sorry, that was me to illustrate how the difference should look like.
> Must be taken from the quadro md8800 machine.
> 
> I'm playing around with some other requests concerning remote behaviors,
> but have to admit that getting some old PCs running on recent again is
> not that much fun and I'm slow.
> 
> We have a case, where Asus stuff is not reliable on PCI subsystem IDs.
> We can detect the different cards by a difference in the eeprom readout,
> but this needs running i2c on saa7134 init2.
> 
> However, since input_init is on saa7134 init1, we fail here being too
> late. Maybe we should have input init on saa7134 init2 in saa7134-core.
> Roman with such a card mailed to me about that. At least I should be
> close to be able to test it, but no i2c remote stuff is here.

sorry, it is a little OT and only this P7131 Analog card is affected,
which needs to be eeprom detected to work around a duplicate PCI
subsystem for physically different cards.

The wrongly detected card has an USB remote by the way, so in case of
auto detection it will come up without working Asus PC-39 IRQ remote.
If the card number is forced, the remote will work too.

Roman seems to suggest a patch, which basically boils down to this.

diff -r b45ffc93fb82 linux/drivers/media/video/saa7134/saa7134-cards.c
--- a/linux/drivers/media/video/saa7134/saa7134-cards.c	Wed Nov 05 00:59:37 2008 +0000
+++ b/linux/drivers/media/video/saa7134/saa7134-cards.c	Mon Nov 03 16:52:17 2008 +0100
@@ -6307,6 +6307,7 @@ int saa7134_board_init2(struct saa7134_d
 		       printk(KERN_INFO "%s: P7131 analog only, using "
 						       "entry of %s\n",
 		       dev->name, saa7134_boards[dev->board].name);
+		       dev->has_remote = SAA7134_REMOTE_GPIO;
 	       }
 	       break;
 	case SAA7134_BOARD_HAUPPAUGE_HVR1110:
diff -r b45ffc93fb82 linux/drivers/media/video/saa7134/saa7134-core.c
--- a/linux/drivers/media/video/saa7134/saa7134-core.c	Wed Nov 05 00:59:37 2008 +0000
+++ b/linux/drivers/media/video/saa7134/saa7134-core.c	Mon Nov 03 16:44:54 2008 +0100
@@ -729,7 +729,6 @@ static int saa7134_hwinit1(struct saa713
 	saa7134_vbi_init1(dev);
 	if (card_has_mpeg(dev))
 		saa7134_ts_init1(dev);
-	saa7134_input_init1(dev);
 
 	saa7134_hw_enable1(dev);
 
@@ -775,6 +774,7 @@ static int saa7134_hwinit2(struct saa713
 
 	dprintk("hwinit2\n");
 
+	saa7134_input_init1(dev);
 	saa7134_video_init2(dev);
 	saa7134_tvaudio_init2(dev);
 
This seems to work for him and also no trouble on a normal gpio remote,
but I can't test on saa7134 i2c remotes.

Since this is only for that one card for now and the trouble seems to be
caused by the manufacturer, maybe to print use card=number to get also
the remote up would be sufficient, but I post it here just in case we'll
get more of this in the future.

Cheers,
Hermann

> > I suspect the bug is somehow related to that (ir-kbd-i2c is getting the
> > events, but sending them to the wrong board). Have you tried removing
> > one of them?
> 
> Maybe the card is even flaky in the PCI slot, that's why a second
> confirmation would be nice.
> 
> Thanks,
> Hermann
> 
> > --
> > RC
> > > > > You should have the device found at 0x47.
> > > > >
> > > > 
> > > > In fact i see:
> > > > 
> > > > ir-kbd-i2c: probe 0x47 @ saa7133[0]: yes
> > > > 
> > > > So everything seemed to go well. But, same story for the rest: ERROR:
> > > > NO_DEVICE when i press buttons on the remote.
> > > > What seems strange to me is the fact that the driver *reacts* to
> > > > remote key presses, but reacts with an error.
> > > > 
> > > > Cheers
> > > > Matteo
> > > > 
> > > 
> > > since you reported the trouble was already visible for you on earlier
> > > kernels, we might try to get a second confirmation at first.
> > > 
> > > Anyone out there? I'm sending a copy to Ricardo too, who added the
> > > support, not sure if he currently has time to read the list.
> > > 
> > > Cheers,
> > > Hermann
> > > 
> 


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Pinnacle PCTV 310i Remote: i2c 'ERROR: NO_DEVICE'

[picciuX]

I don't actually know how to test if mine is really different from any
previous PCTV310i Board with same IDs, because I have only this.
What makes me think about that is, as said, that I found (don't
remember where) a report af a user who buyed two cards at different
times (six month one after the other) and the first worked, while the
second didn't. Moreover, now the board is named "PCTV Hybrid Pro PCI",
but has same PCI IDs of PCTV310i. But, again, I have no way of
discovering differences, because I own only this board.
Anyway, I will do whichever test you want, if I'm able to. Just don't
ask me to test the remote on Windows...

And, for Ricardo, I have only ONE board in the system, and ir-kbd-i2c reports

ir-kbd-i2c: probe 0x7a @ saa7133[0]: no
ir-kbd-i2c: probe 0x47 @ saa7133[0]: yes

but the problem is still there.

Could be same of Asus? How can I test something more?

thank you very much.

matteo


2008/11/7 hermann pitton <hermann-pitton@arcor.de>:
> Hi,
>
> Am Donnerstag, den 06.11.2008, 02:56 +0100 schrieb hermann pitton:
>> Hi Ricardo,
>>
>> Am Donnerstag, den 06.11.2008, 00:46 +0000 schrieb Ricardo Cerqueira:
>> > Hi all;
>> >
>> > On Thu, 2008-11-06 at 01:09 +0100, hermann pitton wrote:
>> > > Hi Matteo,
>> > >
>> > > Am Dienstag, den 04.11.2008, 15:09 +0100 schrieb picciuX:
>> > > > 2008/11/2 hermann pitton <hermann-pitton@arcor.de>:
>> > > >
>> > > > > don't have that remote, but also enable ir-kbd-i2c debug=1.
>> > > > >
>> > > > > ir-kbd-i2c: probe 0x7a @ saa7133[0]: no
>> > > > > ir-kbd-i2c: probe 0x47 @ saa7133[0]: no
>> > > > > ir-kbd-i2c: probe 0x71 @ saa7133[0]: no
>> > > > > ir-kbd-i2c: probe 0x2d @ saa7133[0]: no
>> > > > > ir-kbd-i2c: probe 0x7a @ saa7133[1]: no
>> > > > > ir-kbd-i2c: probe 0x47 @ saa7133[1]: no
>> > > > > ir-kbd-i2c: probe 0x71 @ saa7133[1]: no
>> > > > > ir-kbd-i2c: probe 0x2d @ saa7133[1]: no
>> > > > >
>> >
>> >
>> > Sorry, I missed the rest of the thread;
>> >
>> > In any case, from the above paste, it looks as if you have 2 saa713x
>> > boards in the system, right?
>>
>> sorry, that was me to illustrate how the difference should look like.
>> Must be taken from the quadro md8800 machine.
>>
>> I'm playing around with some other requests concerning remote behaviors,
>> but have to admit that getting some old PCs running on recent again is
>> not that much fun and I'm slow.
>>
>> We have a case, where Asus stuff is not reliable on PCI subsystem IDs.
>> We can detect the different cards by a difference in the eeprom readout,
>> but this needs running i2c on saa7134 init2.
>>
>> However, since input_init is on saa7134 init1, we fail here being too
>> late. Maybe we should have input init on saa7134 init2 in saa7134-core.
>> Roman with such a card mailed to me about that. At least I should be
>> close to be able to test it, but no i2c remote stuff is here.
>
> sorry, it is a little OT and only this P7131 Analog card is affected,
> which needs to be eeprom detected to work around a duplicate PCI
> subsystem for physically different cards.
>
> The wrongly detected card has an USB remote by the way, so in case of
> auto detection it will come up without working Asus PC-39 IRQ remote.
> If the card number is forced, the remote will work too.
>
> Roman seems to suggest a patch, which basically boils down to this.
>
> diff -r b45ffc93fb82 linux/drivers/media/video/saa7134/saa7134-cards.c
> --- a/linux/drivers/media/video/saa7134/saa7134-cards.c Wed Nov 05 00:59:37 2008 +0000
> +++ b/linux/drivers/media/video/saa7134/saa7134-cards.c Mon Nov 03 16:52:17 2008 +0100
> @@ -6307,6 +6307,7 @@ int saa7134_board_init2(struct saa7134_d
>                       printk(KERN_INFO "%s: P7131 analog only, using "
>                                                       "entry of %s\n",
>                       dev->name, saa7134_boards[dev->board].name);
> +                      dev->has_remote = SAA7134_REMOTE_GPIO;
>               }
>               break;
>        case SAA7134_BOARD_HAUPPAUGE_HVR1110:
> diff -r b45ffc93fb82 linux/drivers/media/video/saa7134/saa7134-core.c
> --- a/linux/drivers/media/video/saa7134/saa7134-core.c  Wed Nov 05 00:59:37 2008 +0000
> +++ b/linux/drivers/media/video/saa7134/saa7134-core.c  Mon Nov 03 16:44:54 2008 +0100
> @@ -729,7 +729,6 @@ static int saa7134_hwinit1(struct saa713
>        saa7134_vbi_init1(dev);
>        if (card_has_mpeg(dev))
>                saa7134_ts_init1(dev);
> -       saa7134_input_init1(dev);
>
>        saa7134_hw_enable1(dev);
>
> @@ -775,6 +774,7 @@ static int saa7134_hwinit2(struct saa713
>
>        dprintk("hwinit2\n");
>
> +       saa7134_input_init1(dev);
>        saa7134_video_init2(dev);
>        saa7134_tvaudio_init2(dev);
>
> This seems to work for him and also no trouble on a normal gpio remote,
> but I can't test on saa7134 i2c remotes.
>
> Since this is only for that one card for now and the trouble seems to be
> caused by the manufacturer, maybe to print use card=number to get also
> the remote up would be sufficient, but I post it here just in case we'll
> get more of this in the future.
>
> Cheers,
> Hermann
>
>> > I suspect the bug is somehow related to that (ir-kbd-i2c is getting the
>> > events, but sending them to the wrong board). Have you tried removing
>> > one of them?
>>
>> Maybe the card is even flaky in the PCI slot, that's why a second
>> confirmation would be nice.
>>
>> Thanks,
>> Hermann
>>
>> > --
>> > RC
>> > > > > You should have the device found at 0x47.
>> > > > >
>> > > >
>> > > > In fact i see:
>> > > >
>> > > > ir-kbd-i2c: probe 0x47 @ saa7133[0]: yes
>> > > >
>> > > > So everything seemed to go well. But, same story for the rest: ERROR:
>> > > > NO_DEVICE when i press buttons on the remote.
>> > > > What seems strange to me is the fact that the driver *reacts* to
>> > > > remote key presses, but reacts with an error.
>> > > >
>> > > > Cheers
>> > > > Matteo
>> > > >
>> > >
>> > > since you reported the trouble was already visible for you on earlier
>> > > kernels, we might try to get a second confirmation at first.
>> > >
>> > > Anyone out there? I'm sending a copy to Ricardo too, who added the
>> > > support, not sure if he currently has time to read the list.
>> > >
>> > > Cheers,
>> > > Hermann
>> > >
>>
>
>
> --
> video4linux-list mailing list
> Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/video4linux-list
>

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Pinnacle PCTV 310i Remote: i2c 'ERROR: NO_DEVICE'

[picciuX]

For the records: have another machine with very same board (two
boards, in this case) with the same exact sympthoms regarding ir
remote. Here the remote is not needed at all, so it's not a problem,
but, at least, it's not my pc or my board malfunctioning.

Cheers
Matteo

2008/11/7 picciuX <matteo@picciux.it>:
> I don't actually know how to test if mine is really different from any
> previous PCTV310i Board with same IDs, because I have only this.
> What makes me think about that is, as said, that I found (don't
> remember where) a report af a user who buyed two cards at different
> times (six month one after the other) and the first worked, while the
> second didn't. Moreover, now the board is named "PCTV Hybrid Pro PCI",
> but has same PCI IDs of PCTV310i. But, again, I have no way of
> discovering differences, because I own only this board.
> Anyway, I will do whichever test you want, if I'm able to. Just don't
> ask me to test the remote on Windows...
>
> And, for Ricardo, I have only ONE board in the system, and ir-kbd-i2c reports
>
> ir-kbd-i2c: probe 0x7a @ saa7133[0]: no
> ir-kbd-i2c: probe 0x47 @ saa7133[0]: yes
>
> but the problem is still there.
>
> Could be same of Asus? How can I test something more?
>
> thank you very much.
>
> matteo
>
>
> 2008/11/7 hermann pitton <hermann-pitton@arcor.de>:
>> Hi,
>>
>> Am Donnerstag, den 06.11.2008, 02:56 +0100 schrieb hermann pitton:
>>> Hi Ricardo,
>>>
>>> Am Donnerstag, den 06.11.2008, 00:46 +0000 schrieb Ricardo Cerqueira:
>>> > Hi all;
>>> >
>>> > On Thu, 2008-11-06 at 01:09 +0100, hermann pitton wrote:
>>> > > Hi Matteo,
>>> > >
>>> > > Am Dienstag, den 04.11.2008, 15:09 +0100 schrieb picciuX:
>>> > > > 2008/11/2 hermann pitton <hermann-pitton@arcor.de>:
>>> > > >
>>> > > > > don't have that remote, but also enable ir-kbd-i2c debug=1.
>>> > > > >
>>> > > > > ir-kbd-i2c: probe 0x7a @ saa7133[0]: no
>>> > > > > ir-kbd-i2c: probe 0x47 @ saa7133[0]: no
>>> > > > > ir-kbd-i2c: probe 0x71 @ saa7133[0]: no
>>> > > > > ir-kbd-i2c: probe 0x2d @ saa7133[0]: no
>>> > > > > ir-kbd-i2c: probe 0x7a @ saa7133[1]: no
>>> > > > > ir-kbd-i2c: probe 0x47 @ saa7133[1]: no
>>> > > > > ir-kbd-i2c: probe 0x71 @ saa7133[1]: no
>>> > > > > ir-kbd-i2c: probe 0x2d @ saa7133[1]: no
>>> > > > >
>>> >
>>> >
>>> > Sorry, I missed the rest of the thread;
>>> >
>>> > In any case, from the above paste, it looks as if you have 2 saa713x
>>> > boards in the system, right?
>>>
>>> sorry, that was me to illustrate how the difference should look like.
>>> Must be taken from the quadro md8800 machine.
>>>
>>> I'm playing around with some other requests concerning remote behaviors,
>>> but have to admit that getting some old PCs running on recent again is
>>> not that much fun and I'm slow.
>>>
>>> We have a case, where Asus stuff is not reliable on PCI subsystem IDs.
>>> We can detect the different cards by a difference in the eeprom readout,
>>> but this needs running i2c on saa7134 init2.
>>>
>>> However, since input_init is on saa7134 init1, we fail here being too
>>> late. Maybe we should have input init on saa7134 init2 in saa7134-core.
>>> Roman with such a card mailed to me about that. At least I should be
>>> close to be able to test it, but no i2c remote stuff is here.
>>
>> sorry, it is a little OT and only this P7131 Analog card is affected,
>> which needs to be eeprom detected to work around a duplicate PCI
>> subsystem for physically different cards.
>>
>> The wrongly detected card has an USB remote by the way, so in case of
>> auto detection it will come up without working Asus PC-39 IRQ remote.
>> If the card number is forced, the remote will work too.
>>
>> Roman seems to suggest a patch, which basically boils down to this.
>>
>> diff -r b45ffc93fb82 linux/drivers/media/video/saa7134/saa7134-cards.c
>> --- a/linux/drivers/media/video/saa7134/saa7134-cards.c Wed Nov 05 00:59:37 2008 +0000
>> +++ b/linux/drivers/media/video/saa7134/saa7134-cards.c Mon Nov 03 16:52:17 2008 +0100
>> @@ -6307,6 +6307,7 @@ int saa7134_board_init2(struct saa7134_d
>>                       printk(KERN_INFO "%s: P7131 analog only, using "
>>                                                       "entry of %s\n",
>>                       dev->name, saa7134_boards[dev->board].name);
>> +                      dev->has_remote = SAA7134_REMOTE_GPIO;
>>               }
>>               break;
>>        case SAA7134_BOARD_HAUPPAUGE_HVR1110:
>> diff -r b45ffc93fb82 linux/drivers/media/video/saa7134/saa7134-core.c
>> --- a/linux/drivers/media/video/saa7134/saa7134-core.c  Wed Nov 05 00:59:37 2008 +0000
>> +++ b/linux/drivers/media/video/saa7134/saa7134-core.c  Mon Nov 03 16:44:54 2008 +0100
>> @@ -729,7 +729,6 @@ static int saa7134_hwinit1(struct saa713
>>        saa7134_vbi_init1(dev);
>>        if (card_has_mpeg(dev))
>>                saa7134_ts_init1(dev);
>> -       saa7134_input_init1(dev);
>>
>>        saa7134_hw_enable1(dev);
>>
>> @@ -775,6 +774,7 @@ static int saa7134_hwinit2(struct saa713
>>
>>        dprintk("hwinit2\n");
>>
>> +       saa7134_input_init1(dev);
>>        saa7134_video_init2(dev);
>>        saa7134_tvaudio_init2(dev);
>>
>> This seems to work for him and also no trouble on a normal gpio remote,
>> but I can't test on saa7134 i2c remotes.
>>
>> Since this is only for that one card for now and the trouble seems to be
>> caused by the manufacturer, maybe to print use card=number to get also
>> the remote up would be sufficient, but I post it here just in case we'll
>> get more of this in the future.
>>
>> Cheers,
>> Hermann
>>
>>> > I suspect the bug is somehow related to that (ir-kbd-i2c is getting the
>>> > events, but sending them to the wrong board). Have you tried removing
>>> > one of them?
>>>
>>> Maybe the card is even flaky in the PCI slot, that's why a second
>>> confirmation would be nice.
>>>
>>> Thanks,
>>> Hermann
>>>
>>> > --
>>> > RC
>>> > > > > You should have the device found at 0x47.
>>> > > > >
>>> > > >
>>> > > > In fact i see:
>>> > > >
>>> > > > ir-kbd-i2c: probe 0x47 @ saa7133[0]: yes
>>> > > >
>>> > > > So everything seemed to go well. But, same story for the rest: ERROR:
>>> > > > NO_DEVICE when i press buttons on the remote.
>>> > > > What seems strange to me is the fact that the driver *reacts* to
>>> > > > remote key presses, but reacts with an error.
>>> > > >
>>> > > > Cheers
>>> > > > Matteo
>>> > > >
>>> > >
>>> > > since you reported the trouble was already visible for you on earlier
>>> > > kernels, we might try to get a second confirmation at first.
>>> > >
>>> > > Anyone out there? I'm sending a copy to Ricardo too, who added the
>>> > > support, not sure if he currently has time to read the list.
>>> > >
>>> > > Cheers,
>>> > > Hermann
>>> > >
>>>
>>
>>
>> --
>> video4linux-list mailing list
>> Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
>> https://www.redhat.com/mailman/listinfo/video4linux-list
>>
>

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Re: Pinnacle PCTV 310i Remote: i2c 'ERROR: NO_DEVICE'

[hermann pitton]

Hi Matteo,

Am Montag, den 10.11.2008, 16:41 +0100 schrieb picciuX:
> For the records: have another machine with very same board (two
> boards, in this case) with the same exact sympthoms regarding ir
> remote. Here the remote is not needed at all, so it's not a problem,
> but, at least, it's not my pc or my board malfunctioning.
> 
> Cheers
> Matteo

can't be of much help here, since without such hardware.

We only have ("modinfo saa7134")
pinnacle_remote:Specify Pinnacle PCTV remote: 0=coloured, 1=grey (defaults to 0) (int)

Trying to find something indicating a new difference did not lead far.
http://www.pinnacle.at/fp_presse_bilder.htm

The new naming should not make any for the remote I guess.

Also can't tell, if the eeprom content could reveal anything on that.

Thanks for the report so far.

Cheers,
Hermann


> 2008/11/7 picciuX <matteo@picciux.it>:
> > I don't actually know how to test if mine is really different from any
> > previous PCTV310i Board with same IDs, because I have only this.
> > What makes me think about that is, as said, that I found (don't
> > remember where) a report af a user who buyed two cards at different
> > times (six month one after the other) and the first worked, while the
> > second didn't. Moreover, now the board is named "PCTV Hybrid Pro PCI",
> > but has same PCI IDs of PCTV310i. But, again, I have no way of
> > discovering differences, because I own only this board.
> > Anyway, I will do whichever test you want, if I'm able to. Just don't
> > ask me to test the remote on Windows...
> >
> > And, for Ricardo, I have only ONE board in the system, and ir-kbd-i2c reports
> >
> > ir-kbd-i2c: probe 0x7a @ saa7133[0]: no
> > ir-kbd-i2c: probe 0x47 @ saa7133[0]: yes
> >
> > but the problem is still there.
> >
> > Could be same of Asus? How can I test something more?
> >
> > thank you very much.
> >
> > matteo
> >
> >
> > 2008/11/7 hermann pitton <hermann-pitton@arcor.de>:
> >> Hi,
> >>
> >> Am Donnerstag, den 06.11.2008, 02:56 +0100 schrieb hermann pitton:
> >>> Hi Ricardo,
> >>>
> >>> Am Donnerstag, den 06.11.2008, 00:46 +0000 schrieb Ricardo Cerqueira:
> >>> > Hi all;
> >>> >
> >>> > On Thu, 2008-11-06 at 01:09 +0100, hermann pitton wrote:
> >>> > > Hi Matteo,
> >>> > >
> >>> > > Am Dienstag, den 04.11.2008, 15:09 +0100 schrieb picciuX:
> >>> > > > 2008/11/2 hermann pitton <hermann-pitton@arcor.de>:
> >>> > > >
> >>> > > > > don't have that remote, but also enable ir-kbd-i2c debug=1.
> >>> > > > >
> >>> > > > > ir-kbd-i2c: probe 0x7a @ saa7133[0]: no
> >>> > > > > ir-kbd-i2c: probe 0x47 @ saa7133[0]: no
> >>> > > > > ir-kbd-i2c: probe 0x71 @ saa7133[0]: no
> >>> > > > > ir-kbd-i2c: probe 0x2d @ saa7133[0]: no
> >>> > > > > ir-kbd-i2c: probe 0x7a @ saa7133[1]: no
> >>> > > > > ir-kbd-i2c: probe 0x47 @ saa7133[1]: no
> >>> > > > > ir-kbd-i2c: probe 0x71 @ saa7133[1]: no
> >>> > > > > ir-kbd-i2c: probe 0x2d @ saa7133[1]: no
> >>> > > > >
> >>> >
> >>> >
> >>> > Sorry, I missed the rest of the thread;
> >>> >
> >>> > In any case, from the above paste, it looks as if you have 2 saa713x
> >>> > boards in the system, right?
> >>>
> >>> sorry, that was me to illustrate how the difference should look like.
> >>> Must be taken from the quadro md8800 machine.
> >>>
> >>> I'm playing around with some other requests concerning remote behaviors,
> >>> but have to admit that getting some old PCs running on recent again is
> >>> not that much fun and I'm slow.
> >>>
> >>> We have a case, where Asus stuff is not reliable on PCI subsystem IDs.
> >>> We can detect the different cards by a difference in the eeprom readout,
> >>> but this needs running i2c on saa7134 init2.
> >>>
> >>> However, since input_init is on saa7134 init1, we fail here being too
> >>> late. Maybe we should have input init on saa7134 init2 in saa7134-core.
> >>> Roman with such a card mailed to me about that. At least I should be
> >>> close to be able to test it, but no i2c remote stuff is here.
> >>
> >> sorry, it is a little OT and only this P7131 Analog card is affected,
> >> which needs to be eeprom detected to work around a duplicate PCI
> >> subsystem for physically different cards.
> >>
> >> The wrongly detected card has an USB remote by the way, so in case of
> >> auto detection it will come up without working Asus PC-39 IRQ remote.
> >> If the card number is forced, the remote will work too.
> >>
> >> Roman seems to suggest a patch, which basically boils down to this.
> >>
> >> diff -r b45ffc93fb82 linux/drivers/media/video/saa7134/saa7134-cards.c
> >> --- a/linux/drivers/media/video/saa7134/saa7134-cards.c Wed Nov 05 00:59:37 2008 +0000
> >> +++ b/linux/drivers/media/video/saa7134/saa7134-cards.c Mon Nov 03 16:52:17 2008 +0100
> >> @@ -6307,6 +6307,7 @@ int saa7134_board_init2(struct saa7134_d
> >>                       printk(KERN_INFO "%s: P7131 analog only, using "
> >>                                                       "entry of %s\n",
> >>                       dev->name, saa7134_boards[dev->board].name);
> >> +                      dev->has_remote = SAA7134_REMOTE_GPIO;
> >>               }
> >>               break;
> >>        case SAA7134_BOARD_HAUPPAUGE_HVR1110:
> >> diff -r b45ffc93fb82 linux/drivers/media/video/saa7134/saa7134-core.c
> >> --- a/linux/drivers/media/video/saa7134/saa7134-core.c  Wed Nov 05 00:59:37 2008 +0000
> >> +++ b/linux/drivers/media/video/saa7134/saa7134-core.c  Mon Nov 03 16:44:54 2008 +0100
> >> @@ -729,7 +729,6 @@ static int saa7134_hwinit1(struct saa713
> >>        saa7134_vbi_init1(dev);
> >>        if (card_has_mpeg(dev))
> >>                saa7134_ts_init1(dev);
> >> -       saa7134_input_init1(dev);
> >>
> >>        saa7134_hw_enable1(dev);
> >>
> >> @@ -775,6 +774,7 @@ static int saa7134_hwinit2(struct saa713
> >>
> >>        dprintk("hwinit2\n");
> >>
> >> +       saa7134_input_init1(dev);
> >>        saa7134_video_init2(dev);
> >>        saa7134_tvaudio_init2(dev);
> >>
> >> This seems to work for him and also no trouble on a normal gpio remote,
> >> but I can't test on saa7134 i2c remotes.
> >>
> >> Since this is only for that one card for now and the trouble seems to be
> >> caused by the manufacturer, maybe to print use card=number to get also
> >> the remote up would be sufficient, but I post it here just in case we'll
> >> get more of this in the future.
> >>
> >> Cheers,
> >> Hermann
> >>
> >>> > I suspect the bug is somehow related to that (ir-kbd-i2c is getting the
> >>> > events, but sending them to the wrong board). Have you tried removing
> >>> > one of them?
> >>>
> >>> Maybe the card is even flaky in the PCI slot, that's why a second
> >>> confirmation would be nice.
> >>>
> >>> Thanks,
> >>> Hermann
> >>>
> >>> > --
> >>> > RC
> >>> > > > > You should have the device found at 0x47.
> >>> > > > >
> >>> > > >
> >>> > > > In fact i see:
> >>> > > >
> >>> > > > ir-kbd-i2c: probe 0x47 @ saa7133[0]: yes
> >>> > > >
> >>> > > > So everything seemed to go well. But, same story for the rest: ERROR:
> >>> > > > NO_DEVICE when i press buttons on the remote.
> >>> > > > What seems strange to me is the fact that the driver *reacts* to
> >>> > > > remote key presses, but reacts with an error.
> >>> > > >
> >>> > > > Cheers
> >>> > > > Matteo
> >>> > > >
> >>> > >
> >>> > > since you reported the trouble was already visible for you on earlier
> >>> > > kernels, we might try to get a second confirmation at first.
> >>> > >
> >>> > > Anyone out there? I'm sending a copy to Ricardo too, who added the
> >>> > > support, not sure if he currently has time to read the list.
> >>> > >
> >>> > > Cheers,
> >>> > > Hermann
> >>> > >
> >>>


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list