[mythtv-users] All my DVB Cards have broken!!!

[David Whyte]

Hi all,

Yesterday whilst I was watching a recording on my remote FE and my BE
was coming to the end of capturing another recording it crashed hard
resulting in me doing a reboot using the power button.

When I looked at the syslogs I saw that the end of the recording
produced a while heap of...

Oct  9 19:10:32 localhost kernel: [17264062.172000]
mt352_read_register: readreg error (reg=15, ret==-5)

...but I assumed a reboot would have fixed it.  Tonight I come to look
at my recorded programs and everything that should have recorded
overnight results in Zero byte recordings and my syslog is full of the
above messages.

I fiddled with the antenna connection to no avail so gave the BE box
another reboot.  Now, none of the DVB cards are initialising correctly
and I get the following in the BE logs...

Starting up as the master server.
2006-10-09 19:25:23.897 New DB connection, total: 2
2006-10-09 19:25:23.901 Connected to database 'mythconverg' at host: localhost
2006-10-09 19:25:23.905 mythbackend: MythBackend started as master server
2006-10-09 19:25:23.915 New DB connection, total: 3
2006-10-09 19:25:23.925 Connected to database 'mythconverg' at host: localhost
2006-10-09 19:25:23.933 DVB#0 ERROR - Opening DVB frontend device failed.
          (2) No such file or directory
2006-10-09 19:25:23.936 Failed to locate input DVBInput
2006-10-09 19:25:23.939 DVB#0 ERROR - SetChannelByString(7): not open
2006-10-09 19:25:24.058 DVB#1 ERROR - Opening DVB frontend device failed.
          (2) No such file or directory
2006-10-09 19:25:24.060 Failed to locate input DVBInput
2006-10-09 19:25:24.063 DVB#1 ERROR - SetChannelByString(10): not open
2006-10-09 19:25:24.076 TVRec(4) Error: Start channel from DB is
empty, setting to '13' instead.
2006-10-09 19:25:24.090 DVB#2 ERROR - Opening DVB frontend device failed.
          (2) No such file or directory
2006-10-09 19:25:24.091 Failed to locate input DVBInput
2006-10-09 19:25:24.096 DVB#2 ERROR - SetChannelByString(13): not open

...and mythtv-setup shows similar results.  If I try and start a
recording, I also get similar results.

These are Avermedia DVB-T 771's and nothing has changed with them and
my BE has been flawless for many, many months.

dmesg indicates that it finds the cards all OK...

djwhyte at myth:/dev/dvb/adapter0$ dmesg | grep DVB
[17179589.600000] bttv0: detected: AVermedia AverTV DVB-T 771
[card=123], PCI subsystem ID is 1461:0771
[17179589.600000] bttv0: using: AVerMedia AVerTV DVB-T 771
[card=123,autodetected]
[17179589.652000] bttv1: detected: AVermedia AverTV DVB-T 771
[card=123], PCI subsystem ID is 1461:0771
[17179589.652000] bttv1: using: AVerMedia AVerTV DVB-T 771
[card=123,autodetected]
[17179589.692000] bttv2: detected: AVermedia AverTV DVB-T 771
[card=123], PCI subsystem ID is 1461:0771
[17179589.692000] bttv2: using: AVerMedia AVerTV DVB-T 771
[card=123,autodetected]
[17179593.488000] DVB: registering new adapter (bttv0).
[17179593.492000] DVB: registering new adapter (bttv1).
[17179593.496000] DVB: registering new adapter (bttv2).
djwhyte at myth:/dev/dvb/adapter0$


The only updates that have been made to my Ubuntu Dapper box are
official Dapper updates, which I did on Saturday night as follows....

Commit Log for Sat Oct  7 11:48:02 2006


Upgraded the following packages:
cpio (2.6-10) to 2.6-10ubuntu0.2
libavcodec-dev (3:0.cvs20050918-5ubuntu1) to 3:0.cvs20050918-5ubuntu1.1
libssl0.9.7 (0.9.7g-5ubuntu1) to 0.9.7g-5ubuntu1.1
libssl0.9.8 (0.9.8a-7ubuntu0.2) to 0.9.8a-7ubuntu0.3
libxine-main1 (1.1.1+ubuntu2-7.2) to 1.1.1+ubuntu2-7.3
openssl (0.9.8a-7ubuntu0.2) to 0.9.8a-7ubuntu0.3
python2.4 (2.4.3-0ubuntu4) to 2.4.3-0ubuntu6
python2.4-examples (2.4.3-0ubuntu4) to 2.4.3-0ubuntu6
python2.4-gdbm (2.4.3-0ubuntu4) to 2.4.3-0ubuntu6
python2.4-minimal (2.4.3-0ubuntu4) to 2.4.3-0ubuntu6
python2.4-tk (2.4.3-0ubuntu4) to 2.4.3-0ubuntu6

...but I don't see anything that would effect the DVB cards.

When I do a ls -al /dev/dvb I get the following...

djwhyte at myth:/dev/dvb/adapter0$ ls -al /dev/dvb/
total 0
drwxr-xr-x  5 root root   100 2006-10-09 19:13 .
drwxr-xr-x 16 root root 15240 2006-10-09 19:13 ..
drwxr-xr-x  2 root root   100 2006-10-09 19:13 adapter0
drwxr-xr-x  2 root root   100 2006-10-09 19:13 adapter1
drwxr-xr-x  2 root root   100 2006-10-09 19:13 adapter2

Does anyone have any idea what could have caused this issue?  I can't
imagine it being an antenna thing since the cards appear broke.  I
also imagine the cards are fairly OK since my BE is sat behind a UPS
device so should not be affected by surges unless something came down
the antenna itself, but our TVs are OK.

Any help is greatly appreciated,
Whytey