[MythDora] Autoloading modules in 2.6.20

[gchris at bellsouth.net]

> 
> From: gchris <gchris at bellsouth.net>
> Date: 2007/03/21 Wed PM 08:36:32 EDT
> To: Discussion about MythDora <mythdora at atrpms.net>
> Subject: Re: [MythDora] Autoloading modules in 2.6.20
> 
> New problem with the HD3000 cards?
> I completed basic system installation with the 2.6.20 kernel. 
.    .     .
> All the /dev ports then looked perfectly normal so I started 
> mythtvsetup.  All looked perfectly normal through the first three steps 
> but when I went to do a channel scan on the first dvb card, I wasn't 
> seeing anything on at all on the signal strength meter or the signal to 
> noise meter and no channels were found.  Those meters have always in the 
> past showed some amount of residual noise so something is very wrong.  I 
> canceled out of Mythtvsetup and saw that the terminal window contained 
> these warnings:
> 2007-03-21 19:38:24.579 DiSEqCDevTree, Warning: No device tree for cardid 1
> 2007-03-21 19:38:24.631 DiSEqCDevTree, Warning: No device tree for cardid 2
> 2007-03-21 19:38:44.873 DVBSignalMonitor(0)::constructor(-1,Warning, can 
> not measure Signal Strength): Remote I/O error
> 2007-03-21 19:38:44.998 DVBSignalMonitor(0)::constructor(-1,Warning, can 
> not measure S/N): Remote I/O error
> 
I'm currently thinking that the DiSEqC warnings are probably meanless because these cards don't support that function and so no information is placed in the database for that function.
DVBSignalMonitor *may* be telling the truth in reporting that Mythtv is having difficulty communicating with the card.

Since I wasn't able to find an error in my entries in Mythsetup, I installed an old friend, azap which is a dvb card testing utility.  Azap, working with a channels.conf file lets you select any available station and then it repeatly tries to tune and access the station using the standard /dev/dvb/adapter ports and reports signal strength, SNR and signal lock.  Azap worked normally with both HD3000s.  It was able to tune, lock and report normal signal strength and SNR.

These findings tend to argue for a Mythtv/2.6.20 compatibility issue rather than a driver problem and it would be very helpful if Jarod could confirm this problem independently with his HD3000. 

Chris