All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: Hauppage HVR-2250 Tuning problems
@ 2009-10-30 19:55 Ross J. Reedstrom
  2009-10-30 19:58 ` Steven Toth
  0 siblings, 1 reply; 17+ messages in thread
From: Ross J. Reedstrom @ 2009-10-30 19:55 UTC (permalink / raw)
  To: Steven Toth; +Cc: linux-media


Steven -
Thanks for all the driver work. Do you want bug reports for the -stable
branch on the list, or both to you and the list? (looked around a bit,
couldn't find a community "how to report a bug")

I've recently installed an HVR-2250 (to replace an HVR-1800 that had
some surface mount component blow a crater out, right near the bus
connector!) in a Mythbuntu box, running mythtv
0.21.0+fixes18207-0ubuntu4~hardy1, kernel 2.6.24-24.61

And have the digital tuning working w/ your stable driver (cloned from
kernellabs on 10/16: I don't know hg well enough to how to report a
specific source set)

It's been working well, until one evening my wife reported that two
shows stopped recording simultaneously. Checking the logs, I see the
occasional pair of i2c errors ( ~ 1 every 12-24 hours):

Oct 23 22:48:04 MediaPC kernel: [679597.153063] saa7164_api_i2c_read() error, ret(2) = 0x13
Oct 23 22:48:04 MediaPC kernel: [679597.153072] tda18271_read_regs: ERROR: i2c_transfer returned: -5

Until about 20 min before it locked up, these show up:
Oct 27 20:22:45 MediaPC kernel: [1015942.952099] Event timed out
Oct 27 20:22:45 MediaPC kernel: [1015942.952107] saa7164_api_i2c_read() error, ret(1) = 0x32
Oct 27 20:22:45 MediaPC kernel: [1015942.952110] s5h1411_readreg: readreg error (ret == -5)

and the occasional:

Oct 27 20:23:06 MediaPC kernel: [1015963.906731] Event timed out
Oct 27 20:23:06 MediaPC kernel: [1015963.906741] saa7164_api_i2c_write() error, ret(1) = 0x32
Oct 27 20:23:06 MediaPC kernel: [1015963.906744] s5h1411_writereg: writereg error 0x19 0xf7 0x0000, ret == -5)

in blocks, one set a second for a few seconds, then a few second gap. 
Note at this point, it's still recording both shows.

There are many, many more read than write errors: 232644 read errors
between 20:22:45 and 20:44:10, 168 write errors.

Finally, this changes to:
Oct 27 20:44:10 MediaPC kernel: [1017225.901272] Event timed out
Oct 27 20:44:10 MediaPC kernel: [1017225.901282] saa7164_api_i2c_read() error, ret(1) = 0x32
Oct 27 20:44:10 MediaPC kernel: [1017225.901286] s5h1411_readreg: readreg error (ret == -5)
Oct 27 20:44:10 MediaPC kernel: [1017225.901301] saa7164_cmd_send() No free sequences
Oct 27 20:44:10 MediaPC kernel: [1017225.901303] saa7164_api_i2c_write() error, ret(1) = 0xc
Oct 27 20:44:10 MediaPC kernel: [1017225.901306] s5h1411_writereg: writereg error 0x19 0xf7 0x0000, ret == -5)

And both recordings lock up.

I rebooted to clear the error,and I'm back to the occasional read error
(~1 a day) Not sure if it's been pushed that hard since (recording off
both tuners simultaneously)

Is this useful info? I've got the whole log, and haven't updated the
code yet. I'm willing to do tests, compile other changesets, etc.

Ross
-- 
Ross Reedstrom, Ph.D.                                 reedstrm@rice.edu
Systems Engineer & Admin, Research Scientist        phone: 713-348-6166
The Connexions Project      http://cnx.org            fax: 713-348-3665
Rice University MS-375, Houston, TX 77005
GPG Key fingerprint = F023 82C8 9B0E 2CC6 0D8E  F888 D3AE 810E 88F0 BEDE

^ permalink raw reply	[flat|nested] 17+ messages in thread
* Hauppage HVR-2250 Tuning problems
@ 2009-10-26 22:44 dan
  2009-10-26 23:23 ` Another Sillyname
  0 siblings, 1 reply; 17+ messages in thread
From: dan @ 2009-10-26 22:44 UTC (permalink / raw)
  To: linux-media

I can't seem to get my HVR-2250 (rev. 88061) card to tune any
channels.  I have Comcast digital cable, and my VIZIO VL370M
television is able to tune all of the QAM channels, so I know that the
signal is present and is usable (in theory).  I have tried scanning
for channels in Mythbuntu 9.10 RC (2.6.31 kernel), with MythTV, scan,
dvbscan and scte65scan, without finding any channels.  I have tried
installing the saa7164 drivers from the kernellabs repository and also
the linuxtv repository, with the same results.

The channel scanner in MythTV has two bars at the top of the screen to
indicate signal strength and signal-to-noise ratio, and they both stay
at 0% during the channel scan.  The scanner will say "locked" for a
particular channel, but then it will show a message saying that it
timed and without finding any channels.  I have already set the
timeout to the maximum allowed by the software.

scte65 scan get the closest to giving some kind of output.  I run it
with this command:

$ ./scte65scan -f1 -n1 ./us-Cable-Standard-center-frequencies-QAM256 >
channels.conf

At some point it  gives the following output:

tuning 741000000hz..locked...PID 0x1ffc found
Collecting data (may take up to 2 minutes)

but then it basically just hangs indefinitely until I kill it, and
channels.conf is always empty afterward.

I do have a couple of errors show up in dmesg, but I'm not sure if
they're relevant.  Just in case it's helpful, here is the output from
dmesg.

[   14.266956] saa7164 driver loaded
[   14.267518] saa7164 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   14.267621] CORE saa7164[0]: subsystem: 0070:8891, board: Hauppauge
WinTV-HVR2250 [card=7,autodetected]
[   14.267627] saa7164[0]/0: found at 0000:01:00.0, rev: 129, irq: 16,
latency: 0, mmio: 0xe4000000
[   14.267633] saa7164 0000:01:00.0: setting latency timer to 64
[   14.267637] IRQ 16/saa7164[0]: IRQF_DISABLED is not guaranteed on shared IRQs
[   14.460016] saa7164_downloadfirmware() no first image
[   14.460029] saa7164_downloadfirmware() Waiting for firmware upload
(v4l-saa7164-1.0.3.fw)
[   14.460035] saa7164 0000:01:00.0: firmware: requesting v4l-saa7164-1.0.3.fw
[   16.075415] saa7164_downloadfirmware() firmware read 3978608 bytes.
[   16.075417] saa7164_downloadfirmware() firmware loaded.
[   16.075425] saa7164_downloadfirmware() SecBootLoader.FileSize = 3978608
[   16.075431] saa7164_downloadfirmware() FirmwareSize = 0x1fd6
[   16.075433] saa7164_downloadfirmware() BSLSize = 0x0
[   16.075434] saa7164_downloadfirmware() Reserved = 0x0
[   16.075435] saa7164_downloadfirmware() Version = 0x51cc1
[   23.351830] saa7164_downloadimage() Image downloaded, booting...
[   23.460015] saa7164_downloadimage() Image booted successfully.
[   25.840015] saa7164_downloadimage() Image downloaded, booting...
[   27.260019] saa7164_downloadimage() Image booted successfully.
[   27.302513] saa7164[0]: Hauppauge eeprom: model=88061
[   28.539398] saa7164_api_i2c_read() error, ret(2) = 0x13
[   28.542913] saa7164_api_i2c_read() error, ret(2) = 0x13
[   28.543201] DVB: registering new adapter (saa7164)
[   32.148177] DVB: registering new adapter (saa7164)

I have done some searching online, and that's what led me to scan,
dvbscan and scte65scan, but none of the suggestions I've found so far
seem to help.  Does anyone have any suggestions as to where I can go
from here?  Could there be something wrong with the card itself?  Are
there any diagnostics I could run?

Thanks in advance for any help that anyone can offer.

--dan

^ permalink raw reply	[flat|nested] 17+ messages in thread
end of thread, other threads:[~2009-10-30 20:33 UTC | newest]

Thread overview: 17+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-10-30 19:55 Hauppage HVR-2250 Tuning problems Ross J. Reedstrom
2009-10-30 19:58 ` Steven Toth
2009-10-30 20:09   ` Ross J. Reedstrom
2009-10-30 20:21     ` Ross J. Reedstrom
  -- strict thread matches above, loose matches on Subject: below --
2009-10-26 22:44 dan
2009-10-26 23:23 ` Another Sillyname
2009-10-27 14:17   ` Steven Toth
2009-10-27 14:55     ` dan
2009-10-27 16:20       ` Steven Toth
2009-10-28  5:44         ` dan
2009-10-28 14:08           ` Steven Toth
2009-10-28 14:12             ` Steven Toth
2009-10-30 17:43               ` dan
2009-10-30 18:09                 ` Steven Toth
2009-10-30 18:19                   ` dan
2009-10-30 18:49                     ` Steven Toth
2009-10-27 14:17   ` Steven Toth

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.