DVB-USB which version is installed?
I have just put a Nova-T 500 dual tuner into a newly installed mythdora 4 box. I also have a standard Nova-T in as well.
I wondered if I need to upgrade the dvb-usb drivers or if the current ones are the latest?
Here is the relevant output from dmesg, if that helps :-
cx2388x cx88-mpeg Driver Manager version 0.0.6 loaded
CORE cx88[0]: subsystem: 0070:9002, board: Hauppauge Nova-T DVB-T [card=18,autodetected]
TV tuner 4 at 0x1fe, Radio tuner -1 at 0x1fe
dib0700: loaded with support for 2 different device-types
dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state.
**WARNING** I2C adapter driver [Hauppauge Nova-T 500 Dual DVB-T] forgot to specify physical device; fix it!
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T).
tveeprom 1-0050: Hauppauge model 90002, rev C176, serial# 229140
tveeprom 1-0050: MAC address is 00-0D-FE-03-7F-14
tveeprom 1-0050: tuner model is Thompson DTT7592 (idx 76, type 4)
tveeprom 1-0050: TV standards ATSC/DVB Digital (eeprom 0x80)
tveeprom 1-0050: audio processor is None (idx 0)
tveeprom 1-0050: decoder processor is CX882 (idx 25)
tveeprom 1-0050: has no radio, has IR receiver, has no IR transmitter
cx88[0]: hauppauge eeprom: model=90002
input: cx88 IR (Hauppauge Nova-T DVB-T as /class/input/input3
cx88[0]/2: cx2388x 8802 Driver Manager
ACPI: PCI Interrupt 0000:00:09.2[A] -> GSI 17 (level, low) -> IRQ 21
cx88[0]/2: found at 0000:00:09.2, rev: 5, irq: 21, latency: 32, mmio: 0xdf000000
**WARNING** I2C adapter driver [DiBX000 tuner I2C bus] forgot to specify physical device; fix it!
DVB: registering frontend 0 (DiBcom 3000MC/P)...
cx2388x dvb driver version 0.0.6 loaded
cx8802_register_driver() ->registering driver type=dvb access=shared
CORE cx88[0]: subsystem: 0070:9002, board: Hauppauge Nova-T DVB-T [card=18]
cx88[0]/2: cx2388x based dvb card
ACPI: PCI Interrupt Link [ALKC] BIOS reported IRQ 0, using IRQ 22
ACPI: PCI Interrupt Link [ALKC] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:11.5[C] -> Link [ALKC] -> GSI 22 (level, low) -> IRQ 22
PCI: Setting latency timer of device 0000:00:11.5 to 64
DVB: registering new adapter (cx88[0]).
DVB: registering frontend 1 (Conexant CX22702 DVB-T)...
cx2388x v4l2 driver version 0.0.6 loaded
ACPI: PCI Interrupt 0000:00:09.0[A] -> GSI 17 (level, low) -> IRQ 21
cx88[0]/0: found at 0000:00:09.0, rev: 5, irq: 21, latency: 32, mmio: 0xde000000
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T).
**WARNING** I2C adapter driver [DiBX000 tuner I2C bus] forgot to specify physical device; fix it!
DVB: registering frontend 2 (DiBcom 3000MC/P)...
MT2060: successfully identified (IF1 = 1220)
dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_dib0700
I find it a bit odd that its used the 2 tuners from the Nova-T 500 as 0 and 2, and put the Nova-T as 1, but it all seems to be working. I had ready though that the older drivers were buggy, which is why I am wondering if I need to upgrade them?
Regards
Ben

The DVB drivers in MythDora
The DVB drivers in MythDora are as of 4/20/07 so they do have some age on them. You can certainly try using a later version but you will need to compile that rather then use the rpm's. I'm sure they have corrected some issues since then.
"Please ignore the man behind the curtain"
Dennis
"Please ignore the man behind the curtain"
Dennis
Hi Dennis,
Hi Dennis,
I have done the following (as root) (from a fresh mythdora 4 install) :-
wget http://www.wi-bw.tfh-wildau.de/~pboettch/home/linux-dvb-firmware/dvb-usb-dib0700-1.10.fw
cp dvb-usb-dib0700-1.10.fw /lib/firmware
yum install mercurial
hg clone http://linuxtv.org/hg/v4l-dvb
cd v4l-dvb
make
make install
Added options dvb-usb-dib0700 force_lna_activation=1 to /etc/modprobe.d/options
After a reboot, the it looks like it must be using the new drivers as I get
dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw'
in dmesg, which is the new version, so thats good I assume. Oh, and this time round the Nova-T is DVB 0 and the Nova-T 500 is 1 &2. Not sure if this is random, or based on some other criteria.
Anyway, the signal strength is very poor, and seems no be no different now I have added the dvb-usb-dib0700 force_lna_activation=1. Is there anyway I can tell that bit is working? Nothing gets added to the log files.
My Nova-T is showing 23% signal (which I think is inverted, as pulling the aerial lead out is 100%), so thats really 77%. The Nova-T 500 shows 49% and 51% on the different tuners, and the 49% can't get a lock.
Just for completeness sake,
Just for completeness sake, incase somebody else searches for the same problem, I found that If I plug the aerial directly into the Nova-T 500 The signal strength jumps upto about 65%, which is just about acceptable.
When it's connected via the aerial out on the Nova-T it drops to the 50% mark. Using a passive splitter before the 2 cards seems to be fine, and does not degrade the signal more than about 1%.
So I will purchase an amplified splitter, and I'm sure all will be fine.
I have no idea why the passive out from the original Nova-T is degrading the signal so much, it seemed to be able to drive a second nova-T that I used to have in the system just fine.