All of lore.kernel.org
 help / color / mirror / Atom feed
From: picciuX <matteo@picciux.it>
To: video4linux-list@redhat.com
Subject: Pinnacle PCTV 310i Remote: i2c 'ERROR: NO_DEVICE'
Date: Fri, 31 Oct 2008 10:31:47 +0100	[thread overview]
Message-ID: <c41ce8440810310231gdb614bcred3f4386de883abb@mail.gmail.com> (raw)

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

             reply	other threads:[~2008-10-31  9:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31  9:31 picciuX [this message]
2008-11-02  0:42 ` Pinnacle PCTV 310i Remote: i2c 'ERROR: NO_DEVICE' hermann pitton
2008-11-04 14:09   ` picciuX
2008-11-06  0:09     ` hermann pitton
2008-11-06  0:46       ` Ricardo Cerqueira
2008-11-06  1:56         ` hermann pitton
2008-11-07  0:07           ` hermann pitton
2008-11-07 13:46             ` picciuX
2008-11-10 15:41               ` picciuX
2008-11-11  2:09                 ` hermann pitton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c41ce8440810310231gdb614bcred3f4386de883abb@mail.gmail.com \
    --to=matteo@picciux.it \
    --cc=video4linux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.