Hi all,<br><br>I'm struggling to 'get my head round' this and I'm hoping that someone here may be able to suggest what might be happening, though I admit that the problem is probably not MythTV's "fault" ...<br>
<br>For a long time now my backend system has been stable and working well. It has two Hauppauge WinTV Nova DVB-S2 PCI cards, Mythbuntu 10.04LTS and MythTV 0.24/fixes.<br><br>Sometime recently (I can't say exactly when) something has changed and it now fails to start correctly from a reboot.<br>
<br>Whereas previously the firmware on both DVB cards has been loaded at boot time and MythTV has started correctly, what happens now is that no firmware is loaded and Myth starts up with no adaptors visible.<br><br>To get the 2 cards to load their firmware I have to manually go into backend setup and select each of the cards. There is then a delay of around a second before the screen showing the card setup is displayed. All I need to do is select "Finish" on each card, then exit setup, and from then on everything behaves normally.<br>
<br>The last time this happened we had a mains power loss at 04:00 and it was 07:40 when I manually intervened to get the backend up & running again<br><br>Here are the relevant bits of the syslog from boot time:<br><br>
May 2 04:02:08 mythbuntu kernel: [ 20.324959] cx88[0]: subsystem: 0070:6906, board: Hauppauge WinTV-HVR4000(Lite) DVB-S/S2 [card=69,autodetected], frontend(s): 1<br>May 2 04:02:08 mythbuntu kernel: [ 22.227646] tveeprom 0-0050: TV standards ATSC/DVB Digital (eeprom 0x80)<br>
May 2 04:02:08 mythbuntu kernel: [ 22.320569] cx88[1]: subsystem: 0070:6906, board: Hauppauge WinTV-HVR4000(Lite) DVB-S/S2 [card=69,autodetected], frontend(s): 1<br>May 2 04:02:08 mythbuntu kernel: [ 22.618110] tveeprom 2-0050: TV standards ATSC/DVB Digital (eeprom 0x80)<br>
May 2 04:02:08 mythbuntu kernel: [ 22.872801] cx88[0]/2: subsystem: 0070:6906, board: Hauppauge WinTV-HVR4000(Lite) DVB-S/S2 [card=69]<br>May 2 04:02:08 mythbuntu kernel: [ 22.872806] cx88[0]/2: cx2388x based DVB/ATSC card<br>
May 2 04:02:08 mythbuntu kernel: [ 22.988739] DVB: registering new adapter (cx88[0])<br>May 2 04:02:08 mythbuntu kernel: [ 22.988749] DVB: registering adapter 0 frontend 0 (Conexant CX24116/CX24118)...<br>May 2 04:02:08 mythbuntu kernel: [ 22.989335] cx88[1]/2: subsystem: 0070:6906, board: Hauppauge WinTV-HVR4000(Lite) DVB-S/S2 [card=69]<br>
May 2 04:02:08 mythbuntu kernel: [ 22.989341] cx88[1]/2: cx2388x based DVB/ATSC card<br>May 2 04:02:08 mythbuntu kernel: [ 22.991132] DVB: registering new adapter (cx88[1])<br>May 2 04:02:08 mythbuntu kernel: [ 22.991137] DVB: registering adapter 1 frontend 0 (Conexant CX24116/CX24118)...<br>
<br><br>And here is the firmware correctly loading in response to the 'kick' from my manually running backend setup and selecting each card...<br><br>May 2 07:40:25 mythbuntu kernel: [13086.206814] cx24116_firmware_ondemand: Waiting for firmware upload (dvb-fe-cx24116.fw)...<br>
May 2 07:40:25 mythbuntu kernel: [13086.206834] cx88-mpeg driver manager 0000:00:08.2: firmware: requesting dvb-fe-cx24116.fw<br>May 2 07:40:25 mythbuntu kernel: [13086.211934] cx24116_firmware_ondemand: Waiting for firmware upload(2)...<br>
May 2 07:40:30 mythbuntu kernel: [13091.071865] cx24116_load_firmware: FW version 1.20.79.0<br>May 2 07:40:30 mythbuntu kernel: [13091.071900] cx24116_firmware_ondemand: Firmware upload complete<br>May 2 07:40:44 mythbuntu kernel: [13104.419726] cx24116_firmware_ondemand: Waiting for firmware upload (dvb-fe-cx24116.fw)...<br>
May 2 07:40:44 mythbuntu kernel: [13104.425725] cx88-mpeg driver manager 0000:00:09.2: firmware: requesting dvb-fe-cx24116.fw<br>May 2 07:40:44 mythbuntu kernel: [13104.435178] cx24116_firmware_ondemand: Waiting for firmware upload(2)...<br>
May 2 07:40:50 mythbuntu kernel: [13110.897500] cx24116_load_firmware: FW version 1.20.79.0<br>May 2 07:40:50 mythbuntu kernel: [13110.897538] cx24116_firmware_ondemand: Firmware upload complete<br><br>Prior to this I can't see anything suggesting that the firmware is being requested.<br>
<br>Once it's up and running again the system runs 100% reliably, and I can't afford the time (or the loss of WAF) right now to even contemplate a rebuild or upgrade.<br>Any clues anyone??<br><br>Thanks!<br>George<br>
<br><br>