[mythtv-users] HVR-2250 Tuner Not Available

Barry Martin Barry_Martin_3 at Q.COM
Tue Apr 19 22:57:33 UTC 2016


<Gaa! Did it again!  The message I sent last night was bounced back but
the one I just sent to the same address seems fine! ...There are times I
miss my DEC Rainbow 100! [jk!]   



Hi Curtis!


> One thing I remembered while typing up there someplace is in MCC both
> cards aren't listed.  Comes up fine _within_ #2 Capture Cards, but at
> the screen which appears after selecting #2 Capture Cards I see:
>     Capture Cards
>     (New capture card)
>     (Delete all capture cards on MythFE1)  [which is the name of the
> Frontend portion, not the Backend portion]
>     (Delete all capture cards)
>     [DVB:/dev/dvb/adapter1/frontend0] 
> Is that right or significant of something??  Not seeing the HVR1600
> (adapter0/frontend0) listed seems odd, or (probably!) the first half of
> the HVR-2250 (1,0) listed (in brackets, not parenthesis) might be trying
> to tell me something.  (The second half hasn't been started.) 
I agree that something seems miss.
Since you mentioned that the HVR1600 is correctly set up and working
then the HVR1600 should be listed as well (adapter0/frontend0).

Correct


Unless.... perhaps the listed adapter1/frontend0 is actually your
HVR1600 card?  Or perhaps adapter1/frontend0 is actually the first half
of the HVR2250?

AFAIK no: at "#2 Capture Cards option", when I'm on the DVD Device option I can left_arrow and changes
to /dev/dev/adapter0/frontend0 plus the Frontend ID line changes to Samsung S5H1409.  Right_arrow to
adapter1/frontend0 changes to Samsung S5H1411.  Same for adapter2/frontend0.  



For reference my PVR with two HVR2250's shows:
 Capture cards
  (New capture card)
  (Delete all capture cards on mythpvr)
  (Delete all capture cards)
  [DVB:/dev/dvb/adapter0/frontend0]
  [DVB:/dev/dvb/adapter1/frontend0]
  [DVB:/dev/dvb/adapter2/frontend0]
  [DVB:/dev/dvb/adapter3/frontend0]

OK - weird my working HVR-1600 (adapter0/frontend0) doesn't appear.


It might be worth trying to add the second half of the HVR2250 so see
what happens.

May as well!  Won't have time until tomorrow.



> #4 Video Sources lists the HVR1600 and HVR2250a (again, the second half
> hasn't been started).
Video sources contains where the TV listings come from.  This is only
tied to the tuner card if your are using an Over-The-Air antenna with
EIT listings information.
Do you retrieve the TV listings using an OTA EIT with antenna, or from a
service like Schedules Direct?
For reference my PVR lists my Schedules Direct entry (named HD Antenna)
for my OTA Antenna:

 Video Sources
  (New video source)
  (Delete all video sources)
  HD Antenna

SchedulesDirect.  (Also found if in some other config screen if set for 
EIT the HVR-1600 would be listed as 'busy' on the Frontend.)

Did find something in the Video Sources config: HVR1600 set for "Default"
and the HVR2250a for 'us-bcast'.   Well, that didn't fix anything.  (And 
yes, ran mythfilldatabase.)


And sort of along those lines, I spent some of the day trying to find a 
solution on-line (not that I don't appreciate your assistance -- I greatly 
do!).  Did find something which may (or may not) be tryingt o tell us what 
is wrong:

   Open in browser http://localhost/mythweb/status ==>
   Opens MythTV Status:
      Encoder 1 [DVB:/dev/dvb/adapter0/frontend0] is local on MythBE1 and is not recording.
      Encoder 5 [DVB:/dev/dvb/adapter1/frontend0] is remote on MythFE1 (currently not connected).

1 is the HVR-1600 and 5 is the HVR-2250.  BE1 is the backend I'm working on 
with FE1 it's frontend.  (Eventually a second backend -- I'll keep the 
instruction!!)






> #5 Input Connections lists 
>     Input Connections
>     [DVB:/dev/dvb/adapter1/frontend0] (DVBInput -> HVR2250a
> 
> (The Channel Editor lists the stations found during the earlier scan
> step.)
> 

Input connections is where the tuner card is paired with a TV listings
source.

For reference my PVR shows:

 Input connections
  [DVB:/dev/dvb/adapter0/frontend0](DVBInput) -> HD Antenna
  [DVB:/dev/dvb/adapter1/frontend0](DVBInput) -> HD Antenna
  [DVB:/dev/dvb/adapter2/frontend0](DVBInput) -> HD Antenna
  [DVB:/dev/dvb/adapter3/frontend0](DVBInput) -> HD Antenna

So I don't need separate listings for the two different cards?




You can check to see if the HVR2250 firmware is being properly loaded
with a command such as the following:
  dmesg | egrep 'saa7164|firmware'

('egrep'? That's a new command!)



On my PVR with two HVR2250s (both cards need the firmware loaded) I see
the following:

$ dmesg | egrep 'saa7164|firmware'
[    2.932469] saa7164 driver loaded
[    2.935922] CORE saa7164[0]: subsystem: 0070:8891, board: Hauppauge
WinTV-HVR2250 [card=7,autodetected]
[    2.935927] saa7164[0]/0: found at 0000:02:00.0, rev: 129, irq: 16,
latency: 0, mmio: 0xfb800000
[    3.101634] saa7164_downloadfirmware() no first image
[    3.101646] saa7164_downloadfirmware() Waiting for firmware upload
(NXP7164-2010-03-10.1.fw)
[    3.127246] saa7164_downloadfirmware() firmware read 4019072 bytes.
[    3.127248] saa7164_downloadfirmware() firmware loaded.
[    3.127252] saa7164_downloadfirmware() SecBootLoader.FileSize = 4019072
[    3.127258] saa7164_downloadfirmware() FirmwareSize = 0x1fd6
[    3.127259] saa7164_downloadfirmware() BSLSize = 0x0
[    3.127260] saa7164_downloadfirmware() Reserved = 0x0
[    3.127260] saa7164_downloadfirmware() Version = 0x1661c00
[    9.875557] saa7164_downloadimage() Image downloaded, booting...
[    9.979533] saa7164_downloadimage() Image booted successfully.
[    9.979551] starting firmware download(2)
[   12.706768] saa7164_downloadimage() Image downloaded, booting...
[   14.370325] saa7164_downloadimage() Image booted successfully.
[   14.370343] firmware download complete.
[   14.415064] saa7164[0]: Hauppauge eeprom: model=88061
[   14.997526] DVB: registering new adapter (saa7164)
[   14.997532] saa7164 0000:02:00.0: DVB: registering adapter 0 frontend
0 (Samsung S5H1411 QAM/8VSB Frontend)...
[   17.886570] DVB: registering new adapter (saa7164)
[   17.886582] saa7164 0000:02:00.0: DVB: registering adapter 1 frontend
0 (Samsung S5H1411 QAM/8VSB Frontend)...
[   17.887035] saa7164[0]: registered device video0 [mpeg]
[   18.117697] saa7164[0]: registered device video1 [mpeg]
[   18.328747] saa7164[0]: registered device vbi0 [vbi]
[   18.328874] saa7164[0]: registered device vbi1 [vbi]
[   18.331519] CORE saa7164[1]: subsystem: 0070:8851, board: Hauppauge
WinTV-HVR2250 [card=7,autodetected]
[   18.331523] saa7164[1]/0: found at 0000:03:00.0, rev: 129, irq: 17,
latency: 0, mmio: 0xfb000000
[   18.489180] saa7164_downloadfirmware() no first image
[   18.489191] saa7164_downloadfirmware() Waiting for firmware upload
(NXP7164-2010-03-10.1.fw)
[   18.490482] saa7164_downloadfirmware() firmware read 4019072 bytes.
[   18.490484] saa7164_downloadfirmware() firmware loaded.
[   18.490488] saa7164_downloadfirmware() SecBootLoader.FileSize = 4019072
[   18.490494] saa7164_downloadfirmware() FirmwareSize = 0x1fd6
[   18.490495] saa7164_downloadfirmware() BSLSize = 0x0
[   18.490495] saa7164_downloadfirmware() Reserved = 0x0
[   18.490496] saa7164_downloadfirmware() Version = 0x1661c00
[   25.237392] saa7164_downloadimage() Image downloaded, booting...
[   25.341317] saa7164_downloadimage() Image booted successfully.
[   25.341335] starting firmware download(2)
[   28.067196] saa7164_downloadimage() Image downloaded, booting...
[   30.041708] saa7164_downloadimage() Image booted successfully.
[   30.041727] firmware download complete.
[   30.086296] saa7164[1]: Hauppauge eeprom: model=88061
[   30.668850] DVB: registering new adapter (saa7164)
[   30.668858] saa7164 0000:03:00.0: DVB: registering adapter 2 frontend
0 (Samsung S5H1411 QAM/8VSB Frontend)...
[   33.559588] DVB: registering new adapter (saa7164)
[   33.559593] saa7164 0000:03:00.0: DVB: registering adapter 3 frontend
0 (Samsung S5H1411 QAM/8VSB Frontend)...
[   33.560243] saa7164[1]: registered device video2 [mpeg]
[   33.790607] saa7164[1]: registered device video3 [mpeg]
[   34.001664] saa7164[1]: registered device vbi2 [vbi]
[   34.001812] saa7164[1]: registered device vbi3 [vbi]
$

I do see essentially that.  Hauppauge model is 88021.   BTW, I did check: 
subsystem 0070:88a1 -- according to Kernel Labs' Cardlist it is a 2250.
(Know about the 2255 thing.)


I see there's a second message from you but I'm being called.  ...Thanks again!


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20160419/c5d284d8/attachment.html>


More information about the mythtv-users mailing list