Log in Register FAQ Memberlist Search pcHDTV Forum Index
pcHDTV Forum

pcHDTV Forum Index -> HD-2000/3000 drivers -> HD2000 and FC5 Goto page 1, 2, 3  Next
Post new topic  This topic is locked: you cannot edit posts or make replies. View previous topic :: View next topic 
HD2000 and FC5
PostPosted: Mon Jun 05, 2006 11:54 am Reply with quote
KenA
 
Joined: 15 Mar 2004
Posts: 30
Location: LI, NY




I bought the HD2000 over a year ago and I couldn't get it working with FC3, so I set it aside. Well, I've bought some new hardware, so I decided to dust it off and give it another shot. This time, I'm running FC5. I tried installing FC4, but my hardware didn't seem to like it. Intel dual core - BTW. I figured it would make a great back-end.

Anyway, I can't seem to get the DVB drivers working for the HD2000. I've gone through a ton of threads over the past couple of weeks and I think I've tried everything, including dvb_bt8xx and cx88-dvb.

With the dvb_bt8xx driver, I get signal strength of 7% across the board, even for channels I know don't exist.
Code:
root@mythtv ~# dtvsignal -dvb 0 45
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
tuning to 659000000 Hz
video pid 0x0021, audio pid 0x0024
dtvsignal ver 1.0.3 - by Jack Kelliher (c) 2002,2005,2006
channel = 45 freq = 659000000Hz
 30db       0%         25%         50%         75%        100%
Signal:     |     .     :     .     |     ._____:_____._____|
Signal: 007 ---


With the cx88-dvb driver, I get the following error:
Code:
root@mythtv ~# dtvsignal -dvb 0 45
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
ERROR: failed opening '/dev/dvb/adapter0/frontend0' (No such file or directory)


Oddly enough, if I take out the -dvb 0 option:
Code:
root@mythtv modprobe.d# dtvsignal 45
[root@mythtv ~]# dtvsignal 45
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
ERROR: failed opening '/dev/dvb/adapter0/frontend0' (No such file or directory)
dtvsignal ver 1.0.3 - by Jack Kelliher (c) 2002,2005,2006
channel = 45 freq = 659000000Hz
 30db       0%         25%         50%         75%        100%
Signal:     |     .     :     .     |     ._____:_____._____|
Signal: 094 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

I have no idea what device it is using, so I can't really capture or even view the signal. It can't be the HD2000 card.

Here is the dmesg output when loading the cx88-dvb driver:
Code:
Linux video capture interface: v1.00
cx2388x dvb driver version 0.0.5 loaded

Nothing else. Here is the dmesg output when loading the dvb_bt8xx driver:
Code:
Linux video capture interface: v1.00
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:02:01.0[A] -> GSI 21 (level, low) -> IRQ 21
bttv0: Bt878 (rev 17) at 0000:02:01.0, irq: 21, latency: 64, mmio: 0xdfeff000
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=000000ff [init]
tuner 0-0061: chip found @ 0xc2 (bt878 #0 [sw])
bttv0: using tuner=42
tuner 0-0061: type set to 42 (Philips 1236D ATSC/NTSC dual 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 video0
bttv0: registered device vbi0
bttv0: add subdevice "dvb0"
bt878: AUDIO driver version 0.0.0 loaded
bt878: Bt878 AUDIO function found (0).
ACPI: PCI Interrupt 0000:02:01.1[A] -> GSI 21 (level, low) -> IRQ 21
bt878_probe: card id=[0x20007063],[ pcHDTV HD-2000 TV ] has DVB functions.
bt878(0): Bt878 (rev 17) at 02:01.1, irq: 21, latency: 64, memory: 0xdfefe000
DVB: registering new adapter (bttv0).
DVB: registering frontend 0 (Oren OR51211 VSB Frontend)...


The RG6 cable is hooked directly to my roof-top antenna and I know there are channels coming in because I have a DirectTV HD receiver with the antenna that I've swapped out on the same antenna and a MyHD card on a WinXP box that also gets a signal when hooked to the antenna.

Any help?

ken

_________________
»ken«
View user's profile Send private message
PostPosted: Thu Jun 15, 2006 7:47 pm Reply with quote
pcHDTV_tech
 
Joined: 16 Dec 2004
Posts: 295




Are you using the drivers from the kernel? or did you compile from separate set of drivers?

without the -dvb option dtvscan will try DVB device 0 first then try /dev/dtv which is a device setup by the old V4L2 API driver cx88-atsc. Do an /sbin/lsmod and post the output here.

Rusty
View user's profile Send private message Visit poster's website
PostPosted: Mon Jul 17, 2006 7:25 am Reply with quote
KenA
 
Joined: 15 Mar 2004
Posts: 30
Location: LI, NY




pcHDTV_tech wrote:
Are you using the drivers from the kernel? or did you compile from separate set of drivers?

without the -dvb option dtvscan will try DVB device 0 first then try /dev/dtv which is a device setup by the old V4L2 API driver cx88-atsc. Do an /sbin/lsmod and post the output here.

Rusty

I'm using kernel drivers, but I've tried recompiling with the same results. I used to think I knew what I was doing with Linux (been working with it for 10 years), but this is driving me crazy. I appreciate all the help I can get. I'm also more than willing to rebuild the server.
Code:

[root@mythtv ~]# /sbin/lsmod
Module                  Size  Used by
dvb_bt8xx              18885  0
nxt6000                10693  1 dvb_bt8xx
mt352                   9925  1 dvb_bt8xx
dvb_pll                15301  1 dvb_bt8xx
sp887x                 10693  1 dvb_bt8xx
dst_ca                 15809  1 dvb_bt8xx
dst                    24389  2 dvb_bt8xx,dst_ca
bt878                  15193  2 dvb_bt8xx,dst
dvb_core               78825  2 dvb_bt8xx,dst_ca
cx24110                11461  1 dvb_bt8xx
or51211                12997  1 dvb_bt8xx
lgdt330x               11229  1 dvb_bt8xx
fglrx                 389548  8
ipv6                  246561  18
autofs4                22980  1
hidp                   24001  2
nfs                   198061  2
lockd                  59465  2 nfs
nfs_acl                 7744  1 nfs
rfcomm                 42709  0
l2cap                  31681  10 hidp,rfcomm
bluetooth              52901  5 hidp,rfcomm,l2cap
sunrpc                140925  4 nfs,lockd,nfs_acl
dm_mirror              24081  0
dm_mod                 55129  1 dm_mirror
video                  18885  0
button                 10577  0
battery                13253  0
ac                      8901  0
lp                     16265  0
parport_pc             29413  1
parport                38281  2 lp,parport_pc
floppy                 61829  0
nvram                  12617  0
snd_atiixp             20116  0
snd_ac97_codec         85536  1 snd_atiixp
snd_ac97_bus            6016  1 snd_ac97_codec
snd_seq_dummy           7044  0
snd_seq_oss            32384  0
snd_seq_midi_event     10368  1 snd_seq_oss
snd_seq                48720  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device         11148  3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss            37920  0
snd_mixer_oss          19200  1 snd_pcm_oss
tuner                  50425  0
snd_pcm                76164  3 snd_atiixp,snd_ac97_codec,snd_pcm_oss
bttv                  171381  2 dvb_bt8xx,bt878
video_buf              25413  1 bttv
compat_ioctl32          5441  1 bttv
i2c_algo_bit           12361  1 bttv
v4l2_common            11713  2 tuner,bttv
btcx_risc               8777  1 bttv
ir_common              13381  1 bttv
tveeprom               17873  1 bttv
8139too                29761  0
8139cp                 25793  0
mii                     9281  2 8139too,8139cp
snd_timer              22660  2 snd_seq,snd_pcm
snd                    49124  10 snd_atiixp,snd_ac97_codec,snd_seq_dummy,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
i2c_core               24769  12 dvb_bt8xx,nxt6000,mt352,sp887x,dst,cx24110,or51211,lgdt330x,tuner,bttv,i2c_algo_bit,tveeprom
videodev               13505  1 bttv
ehci_hcd               33229  0
soundcore              13345  1 snd
snd_page_alloc         11528  2 snd_atiixp,snd_pcm
ohci_hcd               23901  0
ext3                  121417  2
jbd                    56917  1 ext3
sata_sil               13641  0
libata                 58065  1 sata_sil
sd_mod                 20417  0
scsi_mod              129001  2 libata,sd_mod

_________________
»ken«
View user's profile Send private message
PostPosted: Mon Jul 17, 2006 7:32 am Reply with quote
KenA
 
Joined: 15 Mar 2004
Posts: 30
Location: LI, NY




BTW, I get an error when trying to scan /dev/dtv:
Code:
[root@mythtv ~]# dtvsignal /dev/dtv 45
failed opening /dev/dtv

_________________
»ken«
View user's profile Send private message
PostPosted: Mon Jul 17, 2006 7:51 am Reply with quote
pcHDTV_tech
 
Joined: 16 Dec 2004
Posts: 295




What does dmesg show? I don't think the confusion is linux, but the DVB issue. It looks like things are loading for you just fine. Try using dtvscan -dvb 0

Rusty
View user's profile Send private message Visit poster's website
PostPosted: Mon Jul 17, 2006 8:55 am Reply with quote
KenA
 
Joined: 15 Mar 2004
Posts: 30
Location: LI, NY




pcHDTV_tech wrote:
What does dmesg show? I don't think the confusion is linux, but the DVB issue. It looks like things are loading for you just fine. Try using dtvscan -dvb 0

Rusty

Here is the output from dmesg:
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:02:01.0[A] -> GSI 21 (level, low) -> IRQ 21
bttv0: Bt878 (rev 17) at 0000:02:01.0, irq: 21, latency: 64, mmio: 0xdfeff000
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]
bttv0: using tuner=42
bttv0: i2c: checking for MSP34xx @ 0x80... not found
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
tuner 0-0061: chip found @ 0xc2 (bt878 #0 [sw])
tuner 0-0061: type set to 42 (Philips 1236D ATSC/NTSC dual in)
bttv0: registered device video0
bttv0: registered device vbi0
bttv0: add subdevice "dvb0"

...snip...

bt878: AUDIO driver version 0.0.0 loaded
bt878: Bt878 AUDIO function found (0).
ACPI: PCI Interrupt 0000:02:01.1[A] -> GSI 21 (level, low) -> IRQ 21
bt878_probe: card id=[0x20007063],[ pcHDTV HD-2000 TV ] has DVB functions.
bt878(0): Bt878 (rev 17) at 02:01.1, irq: 21, latency: 64, memory: 0xdfefe000
DVB: registering new adapter (bttv0).
DVB: registering frontend 0 (Oren OR51211 VSB Frontend)...

dtvscan:
Code:

[root@mythtv ~]# dtvscan -dvb 0
dtvscan ver 1.0.3 - by Jack Kelliher (c) 2002,2005,2006
channel = 2
channel = 3
channel = 4
channel = 5
channel = 6
channel = 7
channel = 8
..snip..
channel = 98
channel = 99
channel = 100
channel = 101
channel = 102
channel = 103
channel = 104
channel = 105
channel = 106
channel = 107
channel = 108
channel = 109


dtvsignal:
Code:

[root@mythtv ~]# dtvsignal -dvb 0 45
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
tuning to 659000000 Hz
video pid 0x0021, audio pid 0x0024
dtvsignal ver 1.0.3 - by Jack Kelliher (c) 2002,2005,2006
channel = 45 freq = 659000000Hz
 30db       0%         25%         50%         75%        100%
Signal:     |     .     :     .     |     ._____:_____._____|
Signal: 007 ---

_________________
»ken«
View user's profile Send private message
PostPosted: Mon Jul 17, 2006 1:39 pm Reply with quote
mikek
 
Joined: 01 Jul 2006
Posts: 16




So I'm in nearly the same boat, except using Debian rather than FC5, and I'm getting no (0) signal with dtsignal.

Code:

videodrome:/usr/src/dvb-atsc-tools-1.0.3# ./dtvsignal -dvb 0 48
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
tuning to 677000000 Hz
video pid 0x0021, audio pid 0x0024
dtvsignal ver 1.0.3 - by Jack Kelliher (c) 2002,2005,2006
channel = 48 freq = 677000000Hz
 30db       0%         25%         50%         75%        100%
Signal:     |     .     :     .     |     ._____:_____._____|
Signal: 000 .


I turned on or51211 debugging as suggested by Rusty in this thread:
http://www.pchdtv.com/forum/viewtopic.php?t=1558&start=0&postdays=0&postorder=asc&highlight=


And that gave me this repeated many times in dmesg:
Code:

or51211: read_signal_strength 8585
or51211: read_snr 203
or51211: read_status 20 3


I really don't know how to interprate this. I'm assuming snr is at an error value, unless its some kind of fixed decimal type, and I have no idea what the status values mean. However, it would be interesting to see what you get if you did this, since you seem to be having the same problem.

My suspicion is that my tuner is shot.
View user's profile Send private message
PostPosted: Mon Jul 17, 2006 2:05 pm Reply with quote
KenA
 
Joined: 15 Mar 2004
Posts: 30
Location: LI, NY




I added the debug option to my modprobe.conf and I get something very similar:
Code:

bt878: AUDIO driver version 0.0.0 loaded
bt878: Bt878 AUDIO function found (0).
ACPI: PCI Interrupt 0000:02:01.1[A] -> GSI 21 (level, low) -> IRQ 21
bt878_probe: card id=[0x20007063],[ pcHDTV HD-2000 TV ] has DVB functions.
bt878(0): Bt878 (rev 17) at 02:01.1, irq: 21, latency: 64, memory: 0xdfefe000
DVB: registering new adapter (bttv0).
DVB: registering frontend 0 (Oren OR51211 VSB Frontend)...
or51211: Waiting for firmware upload (dvb-fe-or51211.fw)...
or51211:Got Hotplug firmware
or51211: Firmware is 8518 bytes
or51211: Done.
or51211: Firmware upload complete.
bttv0: IRQ lockup, clearing GPINT from int mask [bits: OFLOW GPINT*]
or51211: read_fwbits 6 1 ff 2 2 3 66 4 66 5
or51211: ver TUff0266 VSB mode 06 Status 62
or51211: read_signal_strength 8585
or51211: set_parameters frequency = 659000000 (tunerfreq = 11248)
or51211: set_parameters UHF range
or51211: set_parameters tuner bytes: 0x2b 0xf0 0x8e 0x30or51211: 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: setmode rec status 20 03
or51211: read_snr 203
or51211: read_status 20 3
...repeating..

The IRQ lockup, clearing GPINT from int mask message kind of sticks out.

_________________
»ken«
View user's profile Send private message
PostPosted: Mon Jul 17, 2006 4:29 pm Reply with quote
mikek
 
Joined: 01 Jul 2006
Posts: 16




KenA wrote:

The IRQ lockup, clearing GPINT from int mask message kind of sticks out.


I got the same thing, see:
http://pchdtv.com/forum/viewtopic.php?p=8113#8113

I wrote if off - I've seen that in other posts from people whose cards were working. Something tells me that is part of the normal driver/card/firmware initialization... though I could be wrong.

The pcHDTV Tech replied to that post and didn't mention that "IRQ lockup", so I'm sort of thinking it isn't a problem. I wish someone who knows what those status codes mean would chime in.
View user's profile Send private message
PostPosted: Mon Jul 17, 2006 6:09 pm Reply with quote
waterhead
 
Joined: 24 Apr 2005
Posts: 299




I think SNR is referring to signal to noise ratio. When you google read_snr, you get alot of hits about a dvb patch.

I don't have a solution to your problems, though.

Paul

_________________
Mythbuntu 8.04
Intel D875PBZ main board
Pentium4 3.06Ghz
1024GB RAM
nVidia 6600GT
pcHDTV HD-3000
Air2PC PCI
MythTV 0.21
View user's profile Send private message
PostPosted: Mon Jul 17, 2006 6:16 pm Reply with quote
mikek
 
Joined: 01 Jul 2006
Posts: 16




waterhead wrote:
I think SNR is referring to signal to noise ratio.


Do you know an integer representation of a fixed point decimal, an error value, or is it reporting my SNR at 203?
View user's profile Send private message
PostPosted: Mon Jul 17, 2006 6:43 pm Reply with quote
waterhead
 
Joined: 24 Apr 2005
Posts: 299




mikek wrote:

Do you know an integer representation of a fixed point decimal, an error value, or is it reporting my SNR at 203?


I'm not going to even pretend to know anything about this, sorry.

_________________
Mythbuntu 8.04
Intel D875PBZ main board
Pentium4 3.06Ghz
1024GB RAM
nVidia 6600GT
pcHDTV HD-3000
Air2PC PCI
MythTV 0.21
View user's profile Send private message
PostPosted: Mon Jul 17, 2006 7:03 pm Reply with quote
KenA
 
Joined: 15 Mar 2004
Posts: 30
Location: LI, NY




What are the chances that we both have the same SNR? Unless Mike lives next door and has the same antenna and cable length, I would imagine they are pretty high. We have to be missing something and I'm hoping that Rusty will get a chance to chime in on it.

ken

Rusty, if you're listening - I can give you temp ssh access to my mythtv box if it will help. PM me.
View user's profile Send private message
PostPosted: Mon Jul 17, 2006 9:24 pm Reply with quote
xyzzy
 
Joined: 12 Feb 2006
Posts: 225




The HD-2000 has two input coax connectors, right? Have you tried connecting you antenna to both? One is supposed to be for analog and one for digital, but I'm not sure the driver is getting it correct. It might be using the analog connector.

The debug information tells me you are trying to tune to OTA channel 45, and it appers to be sending the correct bytes to the tuner to make it do this.

The snr value is just something that is read from some register in the demodulator. I don't have a or51211 datasheet so I can't tell what it means. You're right that is supposed to be signal to noise ratio.

The read_status 20 3 line means it read the bytes 0x20 0x03 from the demodulator's receiver status register. Again, without the datasheet there is little I can say about that. But, the source code for the driver tells me that bit 0 of the first byte indicates a lock. It is not set in that status message, so the demodulator is telling you that you don't have a lock.

Maybe there is nothing on channel 45 where you live? Maybe your antenna isn't good enough to get reception? Maybe you have it connected to the wrong port? Maybe the HD-2000 is just very fussy?

Try my atscscan program to scan some other frequencies (use -o to scan OTA channels). It should be better at telling you what is going on.
View user's profile Send private message
PostPosted: Mon Jul 17, 2006 11:11 pm Reply with quote
mikek
 
Joined: 01 Jul 2006
Posts: 16




xyzzy wrote:
Maybe there is nothing on channel 45 where you live? Maybe your antenna isn't good enough to get reception? Maybe you have it connected to the wrong port? Maybe the HD-2000 is just very fussy?


'Mad'

I'm another one of those 10 year users that thought they knew something about linux, but I guess since you wrote a software program, you're free to speculate...

Here's the latest on recetption of channel 45:

Last weekend, I had a friend bring by his HDTV reciver, connected it to my antenna, and 45 came in sharp, about what you'd expect with the transmitter LOS and 3mi away! I don't think it's the antenna, I don't think its station 45.

As for the rest:

Either of the coax ports can be used for ATSC or NTSC reception, the driver selects one. The documentation for which one doesn't exist. However, I don't think its an issue of me connecting to the wrong port since I've tried both several times.

I've already gone to driver source code and figured the reciever had no lock (check my previous post). Sure I can get the data sheet and go through every register on the or51211 and become one of the "select few" with detailed technical knowledge of this hunk-o-poo, or I could just write it off as $200.00 (those are 2004 dollars) poorly spent.


Here's my $200.00 worth of speculation: Maybe the problem is pcHDTV's support? Maybe pcHDTV is ripping people off under the guise of being part of the "Linux Community"? Maybe pcHDTV is no more part of the "Linux community" than Hauppauge, ATI, Avermedia, Pinnacle or any other "for profit" companies that have provided enough information to the "Linux Community" to get a driver written? Maybe the HD-2000 doesn't even work with the DVB drivers? Or maybe my HD-2000 is just hosed?


If pcHDTB isn't going to provide drivers for 2.6.13+, the very least they could have done was provide a How-To on using thier card with the DVB drivers since they advertise it as working. Instead, they abandoned it, and use volunteers that don't have the time, patience, skills, or hardware platforms to support this.

I don't feel like becoming a driver developer/debugger for someone who sold me a $200.00 peice of hardware advertised as working, and I really don't want to become an expert on the obsolete. On top of that, my patience has worn thin with these quixotic diversions: pcHDTV's random collection of speculations, dead ends, spam, and trolls they call "support".

The lesson learned here is never expect a product whose only source of support is a public forum to be that useful once it breaks. If the card had been $45 or cheaper, that would have been one thing - I would have had fun figuring it out. But to pay a premium retail price and have this much hassel is an insult.

Evil or Very Mad
View user's profile Send private message
HD2000 and FC5
  pcHDTV Forum Index -> HD-2000/3000 drivers
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 3  
Goto page 1, 2, 3  Next
  
  
 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