<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.6.6">
</HEAD>
<BODY>
<BR>
<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!] <BR>
<BR>
<BR>
<BR>
Hi Curtis!<BR>
<BR>
<PRE>
<B><FONT COLOR="#737373">> One thing I remembered while typing up there someplace is in MCC both</FONT></B>
<B><FONT COLOR="#737373">> cards aren't listed. Comes up fine _within_ #2 Capture Cards, but at</FONT></B>
<B><FONT COLOR="#737373">> the screen which appears after selecting #2 Capture Cards I see:</FONT></B>
<B><FONT COLOR="#737373">> Capture Cards</FONT></B>
<B><FONT COLOR="#737373">> (New capture card)</FONT></B>
<B><FONT COLOR="#737373">> (Delete all capture cards on MythFE1) [which is the name of the</FONT></B>
<B><FONT COLOR="#737373">> Frontend portion, not the Backend portion]</FONT></B>
<B><FONT COLOR="#737373">> (Delete all capture cards)</FONT></B>
<B><FONT COLOR="#737373">> [DVB:/dev/dvb/adapter1/frontend0] </FONT></B>
<B><FONT COLOR="#737373">> Is that right or significant of something?? Not seeing the HVR1600</FONT></B>
<B><FONT COLOR="#737373">> (adapter0/frontend0) listed seems odd, or (probably!) the first half of</FONT></B>
<B><FONT COLOR="#737373">> the HVR-2250 (1,0) listed (in brackets, not parenthesis) might be trying</FONT></B>
<B><FONT COLOR="#737373">> to tell me something. (The second half hasn't been started.) </FONT></B>
<B>I agree that something seems miss.</B>
<B>Since you mentioned that the HVR1600 is correctly set up and working</B>
<B>then the HVR1600 should be listed as well (adapter0/frontend0).</B>
Correct
<B>Unless.... perhaps the listed adapter1/frontend0 is actually your</B>
<B>HVR1600 card? Or perhaps adapter1/frontend0 is actually the first half</B>
<B>of the HVR2250?</B>
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.
<B>For reference my PVR with two HVR2250's shows:</B>
<B> Capture cards</B>
<B> (New capture card)</B>
<B> (Delete all capture cards on mythpvr)</B>
<B> (Delete all capture cards)</B>
<B> [DVB:/dev/dvb/adapter0/frontend0]</B>
<B> [DVB:/dev/dvb/adapter1/frontend0]</B>
<B> [DVB:/dev/dvb/adapter2/frontend0]</B>
<B> [DVB:/dev/dvb/adapter3/frontend0]</B>
OK - weird my working HVR-1600 (adapter0/frontend0) doesn't appear.
<B>It might be worth trying to add the second half of the HVR2250 so see</B>
<B>what happens.</B>
May as well! Won't have time until tomorrow.
<FONT COLOR="#737373">> #4 Video Sources lists the HVR1600 and HVR2250a (again, the second half</FONT>
<FONT COLOR="#737373">> hasn't been started).</FONT>
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 <A HREF="http://localhost/mythweb/status">http://localhost/mythweb/status</A> ==>
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!!)
<B><FONT COLOR="#737373">> #5 Input Connections lists </FONT></B>
<B><FONT COLOR="#737373">> Input Connections</FONT></B>
<B><FONT COLOR="#737373">> [DVB:/dev/dvb/adapter1/frontend0] (DVBInput -> HVR2250a</FONT></B>
<B><FONT COLOR="#737373">> </FONT></B>
<B><FONT COLOR="#737373">> (The Channel Editor lists the stations found during the earlier scan</FONT></B>
<B><FONT COLOR="#737373">> step.)</FONT></B>
<B><FONT COLOR="#737373">> </FONT></B>
<B>Input connections is where the tuner card is paired with a TV listings</B>
<B>source.</B>
<B>For reference my PVR shows:</B>
<B> Input connections</B>
<B> [DVB:/dev/dvb/adapter0/frontend0](DVBInput) -> HD Antenna</B>
<B> [DVB:/dev/dvb/adapter1/frontend0](DVBInput) -> HD Antenna</B>
<B> [DVB:/dev/dvb/adapter2/frontend0](DVBInput) -> HD Antenna</B>
<B> [DVB:/dev/dvb/adapter3/frontend0](DVBInput) -> HD Antenna</B>
So I don't need separate listings for the two different cards?
<B>You can check to see if the HVR2250 firmware is being properly loaded</B>
<B>with a command such as the following:</B>
<B> dmesg | egrep 'saa7164|firmware'</B>
('egrep'? That's a new command!)
<B>On my PVR with two HVR2250s (both cards need the firmware loaded) I see</B>
<B>the following:</B>
<B>$ dmesg | egrep 'saa7164|firmware'</B>
<B>[ 2.932469] saa7164 driver loaded</B>
<B>[ 2.935922] CORE saa7164[0]: subsystem: 0070:8891, board: Hauppauge</B>
<B>WinTV-HVR2250 [card=7,autodetected]</B>
<B>[ 2.935927] saa7164[0]/0: found at 0000:02:00.0, rev: 129, irq: 16,</B>
<B>latency: 0, mmio: 0xfb800000</B>
<B>[ 3.101634] saa7164_downloadfirmware() no first image</B>
<B>[ 3.101646] saa7164_downloadfirmware() Waiting for firmware upload</B>
<B>(NXP7164-2010-03-10.1.fw)</B>
<B>[ 3.127246] saa7164_downloadfirmware() firmware read 4019072 bytes.</B>
<B>[ 3.127248] saa7164_downloadfirmware() firmware loaded.</B>
<B>[ 3.127252] saa7164_downloadfirmware() SecBootLoader.FileSize = 4019072</B>
<B>[ 3.127258] saa7164_downloadfirmware() FirmwareSize = 0x1fd6</B>
<B>[ 3.127259] saa7164_downloadfirmware() BSLSize = 0x0</B>
<B>[ 3.127260] saa7164_downloadfirmware() Reserved = 0x0</B>
<B>[ 3.127260] saa7164_downloadfirmware() Version = 0x1661c00</B>
<B>[ 9.875557] saa7164_downloadimage() Image downloaded, booting...</B>
<B>[ 9.979533] saa7164_downloadimage() Image booted successfully.</B>
<B>[ 9.979551] starting firmware download(2)</B>
<B>[ 12.706768] saa7164_downloadimage() Image downloaded, booting...</B>
<B>[ 14.370325] saa7164_downloadimage() Image booted successfully.</B>
<B>[ 14.370343] firmware download complete.</B>
<B>[ 14.415064] saa7164[0]: Hauppauge eeprom: model=88061</B>
<B>[ 14.997526] DVB: registering new adapter (saa7164)</B>
<B>[ 14.997532] saa7164 0000:02:00.0: DVB: registering adapter 0 frontend</B>
<B>0 (Samsung S5H1411 QAM/8VSB Frontend)...</B>
<B>[ 17.886570] DVB: registering new adapter (saa7164)</B>
<B>[ 17.886582] saa7164 0000:02:00.0: DVB: registering adapter 1 frontend</B>
<B>0 (Samsung S5H1411 QAM/8VSB Frontend)...</B>
<B>[ 17.887035] saa7164[0]: registered device video0 [mpeg]</B>
<B>[ 18.117697] saa7164[0]: registered device video1 [mpeg]</B>
<B>[ 18.328747] saa7164[0]: registered device vbi0 [vbi]</B>
<B>[ 18.328874] saa7164[0]: registered device vbi1 [vbi]</B>
<B>[ 18.331519] CORE saa7164[1]: subsystem: 0070:8851, board: Hauppauge</B>
<B>WinTV-HVR2250 [card=7,autodetected]</B>
<B>[ 18.331523] saa7164[1]/0: found at 0000:03:00.0, rev: 129, irq: 17,</B>
<B>latency: 0, mmio: 0xfb000000</B>
<B>[ 18.489180] saa7164_downloadfirmware() no first image</B>
<B>[ 18.489191] saa7164_downloadfirmware() Waiting for firmware upload</B>
<B>(NXP7164-2010-03-10.1.fw)</B>
<B>[ 18.490482] saa7164_downloadfirmware() firmware read 4019072 bytes.</B>
<B>[ 18.490484] saa7164_downloadfirmware() firmware loaded.</B>
<B>[ 18.490488] saa7164_downloadfirmware() SecBootLoader.FileSize = 4019072</B>
<B>[ 18.490494] saa7164_downloadfirmware() FirmwareSize = 0x1fd6</B>
<B>[ 18.490495] saa7164_downloadfirmware() BSLSize = 0x0</B>
<B>[ 18.490495] saa7164_downloadfirmware() Reserved = 0x0</B>
<B>[ 18.490496] saa7164_downloadfirmware() Version = 0x1661c00</B>
<B>[ 25.237392] saa7164_downloadimage() Image downloaded, booting...</B>
<B>[ 25.341317] saa7164_downloadimage() Image booted successfully.</B>
<B>[ 25.341335] starting firmware download(2)</B>
<B>[ 28.067196] saa7164_downloadimage() Image downloaded, booting...</B>
<B>[ 30.041708] saa7164_downloadimage() Image booted successfully.</B>
<B>[ 30.041727] firmware download complete.</B>
<B>[ 30.086296] saa7164[1]: Hauppauge eeprom: model=88061</B>
<B>[ 30.668850] DVB: registering new adapter (saa7164)</B>
<B>[ 30.668858] saa7164 0000:03:00.0: DVB: registering adapter 2 frontend</B>
<B>0 (Samsung S5H1411 QAM/8VSB Frontend)...</B>
<B>[ 33.559588] DVB: registering new adapter (saa7164)</B>
<B>[ 33.559593] saa7164 0000:03:00.0: DVB: registering adapter 3 frontend</B>
<B>0 (Samsung S5H1411 QAM/8VSB Frontend)...</B>
<B>[ 33.560243] saa7164[1]: registered device video2 [mpeg]</B>
<B>[ 33.790607] saa7164[1]: registered device video3 [mpeg]</B>
<B>[ 34.001664] saa7164[1]: registered device vbi2 [vbi]</B>
<B>[ 34.001812] saa7164[1]: registered device vbi3 [vbi]</B>
<B>$</B>
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!
</PRE>
<BR>
</BODY>
</HTML>