Log in Register FAQ Memberlist Search pcHDTV Forum Index
pcHDTV Forum

pcHDTV Forum Index -> General pcHDTV topics -> Dtsignal Shows 0% Across the Board, is My HD-2000 Broken?
Post new topic  This topic is locked: you cannot edit posts or make replies. View previous topic :: View next topic 
Dtsignal Shows 0% Across the Board, is My HD-2000 Broken?
PostPosted: Mon Jul 03, 2006 9:00 pm Reply with quote
mikek
 
Joined: 01 Jul 2006
Posts: 16




I've got an HD-2000 that I'm just finally getting around to using, after years in the box...

I can't seem to get any reception. dtsignal show 0% for all channels. Using the same antenna (a Radio Shlock indoor/outdoor HDTV antenna), I can recieve NTSC UHF signals on my VCR tuner from the same tower, which is relatively close (3.5 mi).

I'm not sure how dtsignal works, should it show signal strength (even noise) in a paticular channel, or does it require a coherent ATSC signal before it reports?

Any ideas?
View user's profile Send private message
PostPosted: Tue Jul 04, 2006 1:24 pm Reply with quote
pcHDTV_tech
 
Joined: 16 Dec 2004
Posts: 295




First things first.
What system (kernel version, ditribution. etc) did you put the card into?
Are you using the drivers that came on the CD, or have you downloaded the latest from pcHDTV?
Are there any pertinent messages when you run dmesg?

Rusty
View user's profile Send private message Visit poster's website
PostPosted: Tue Jul 04, 2006 5:08 pm Reply with quote
mikek
 
Joined: 01 Jul 2006
Posts: 16




2.6.15, Debian. Custom built kernel, using dvb drivers.

lspci:
Code:

0000:00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1)
0000:00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1)
0000:00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1)
0000:00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1)
0000:00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1)
0000:00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1)
0000:00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
0000:00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
0000:00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
0000:00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
0000:00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
0000:00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet Controller (rev a1)
0000:00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1)
0000:00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3)
0000:00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
0000:00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
0000:01:04.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
0000:01:04.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
0000:01:06.0 Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2 Encoder (rev 01)
0000:01:08.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 08)
0000:01:08.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 08)
0000:01:09.0 FireWire (IEEE 1394): NEC Corporation IEEE 1394 [OrangeLink] Host Controller (rev 03)
0000:02:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G550 AGP (rev 01)


This is what happens when I load the driver:
Code:

videodrome:/usr/src/dvb-atsc-tools-1.0.3# modprobe -v dvb_bt8xx
insmod /lib/modules/2.6.15/kernel/drivers/media/dvb/frontends/lgdt330x.ko
insmod /lib/modules/2.6.15/kernel/drivers/media/dvb/frontends/or51211.ko
insmod /lib/modules/2.6.15/kernel/drivers/media/dvb/frontends/cx24110.ko
insmod /lib/modules/2.6.15/kernel/drivers/media/dvb/dvb-core/dvb-core.ko
insmod /lib/modules/2.6.15/kernel/drivers/media/video/tveeprom.ko
insmod /lib/modules/2.6.15/kernel/drivers/media/video/btcx-risc.ko
insmod /lib/modules/2.6.15/kernel/drivers/media/video/v4l2-common.ko
insmod /lib/modules/2.6.15/kernel/drivers/media/video/video-buf.ko
insmod /lib/modules/2.6.15/kernel/drivers/media/video/bttv.ko
insmod /lib/modules/2.6.15/kernel/drivers/media/dvb/bt8xx/bt878.ko
insmod /lib/modules/2.6.15/kernel/drivers/media/dvb/bt8xx/dst.ko
insmod /lib/modules/2.6.15/kernel/drivers/media/dvb/bt8xx/dst_ca.ko
insmod /lib/modules/2.6.15/kernel/drivers/media/dvb/frontends/sp887x.ko
insmod /lib/modules/2.6.15/kernel/drivers/media/dvb/frontends/dvb-pll.ko
insmod /lib/modules/2.6.15/kernel/drivers/media/dvb/frontends/mt352.ko
insmod /lib/modules/2.6.15/kernel/drivers/media/dvb/frontends/nxt6000.ko
insmod /lib/modules/2.6.15/kernel/drivers/media/dvb/bt8xx/dvb-bt8xx.ko


dmesg gives me this:
Code:

bttv: driver version 0.9.16 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
ACPI: PCI Interrupt 0000:01:04.0[A] -> Link [APC1] -> GSI 16 (level, high) -> IRQ 209
bttv0: Bt878 (rev 17) at 0000:01:04.0, irq: 209, latency: 32, mmio: 0xdc001000
bttv0: detected: pcHDTV HD-2000 TV [card=112], PCI subsystem ID is 7063:2000
bttv0: using: pcHDTV HD-2000 TV [card=112,autodetected]
bttv0: gpio: en=00000000, out=00000000 in=0000007f [init]
tuner 3-0061: chip found @ 0xc2 (bt878 #0 [sw])
bttv0: using tuner=42
tuner 3-0061: type set to 42 (Philips 1236D ATSC/NTSC daul in)
bttv0: i2c: checking for MSP34xx @ 0x80... not found
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
bttv0: registered device video1
bttv0: registered device vbi1
bttv0: add subdevice "dvb0"
bt878: AUDIO driver version 0.0.0 loaded
bt878: Bt878 AUDIO function found (0).
ACPI: PCI Interrupt 0000:01:04.1[A] -> Link [APC1] -> GSI 16 (level, high) -> IRQ 209
bt878(0): Bt878 (rev 17) at 01:04.1, irq: 209, latency: 32, memory: 0xdc000000
DVB: registering new adapter (bttv0).
DVB: registering frontend 0 (Oren OR51211 VSB Frontend)...


When I run dtvsignal for the first time after loading the driver, dmesg shows this:
Code:

or51211: Waiting for firmware upload (dvb-fe-or51211.fw)...
or51211:Got Hotplug firmware
or51211: Done.
or51211: Firmware upload complete.
bttv0: IRQ lockup, clearing GPINT from int mask [bits: OFLOW GPINT*]
or51211: ver TU256266 VSB mode 06 Status 62


And this is the output from dtvsignal:
Code:

videodrome:/usr/src/dvb-atsc-tools-1.0.3# ./dtvsignal -dvb 0 39
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
tuning to 623000000 Hz
video pid 0x0021, audio pid 0x0024
dtvsignal ver 1.0.3 - by Jack Kelliher (c) 2002,2005,2006
channel = 39 freq = 623000000Hz
 30db       0%         25%         50%         75%        100%
Signal:     |     .     :     .     |     ._____:_____._____|
Signal: 000 .
View user's profile Send private message
PostPosted: Thu Jul 06, 2006 6:54 pm Reply with quote
pcHDTV_tech
 
Joined: 16 Dec 2004
Posts: 295




Try adding the following line to /etc/modprobe.conf
Code:
options or51211 debug=1


Then look at the output of dmesg when you run dtvsignal.

Rusty

p.s. You may also want to try
Code:
> /sbin/modprobe -vr bt878 dvb-bt8xx
> /sbin/modprobe -v dvb-bt8xx
View user's profile Send private message Visit poster's website
PostPosted: Fri Jul 07, 2006 10:38 am Reply with quote
mikek
 
Joined: 01 Jul 2006
Posts: 16




That gave me some more information, but I'm not sure what it means, beyond not having a valid signal - which I already knew:

Code:

or51211: set_parameters frequency = 563000000 (tunerfreq = 9712)
or51211: set_parameters UHF range
or51211: set_parameters tuner bytes: 0x25 0xf0 0x8e 0x30
or51211: setmode rec status 20 03
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3
or51211: read_signal_strength 8585
or51211: read_status 20 3
or51211: read_status 20 3
or51211: read_status 20 3
or51211: read_status 20 3
or51211: read_status 20 3
or51211: read_status 20 3


Unfortunatly, I think I'm at the edge of my abilities when it comes to interprating this. I was sort of hoping it might give me a more user friendly readback.

Really, I'll just go back to my question - if, from the same transmitter, I can recieve NTSC UHF stations clearly, should I be able to at least see *some* noise using dtvsignal.
View user's profile Send private message
Dtsignal Shows 0% Across the Board, is My HD-2000 Broken?
  pcHDTV Forum Index -> General pcHDTV topics
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
All times are GMT - 7 Hours  
Page 1 of 1  

  
  
 Post new topic  This topic is locked: you cannot edit posts or make replies.  


Powered by phpBB © 2001-2003 phpBB Group
Theme created by Vjacheslav Trushkin