Log in Register FAQ Memberlist Search pcHDTV Forum Index
pcHDTV Forum

pcHDTV Forum Index -> Installation/Setup -> Problems with hd5500 station detection
Post new topic  Reply to topic View previous topic :: View next topic 
Problems with hd5500 station detection
PostPosted: Sat Mar 31, 2007 10:33 am Reply with quote
gramila
 
Joined: 31 Mar 2007
Posts: 6




Greetings,
I wrote the following somewhat long winded note to support on wednesday, but have yet to hear anything back. I am hoping that someone here might be able to give me a pointer for something to try to see if I can get this bear to function....
I should probably add to the info at the start -- I have two functioning pv250's from happauge in the box as well. Those two and the HD5500 used to "play well" together.

I am pleased to have purchased an hd5500 from your company, but
I am having an absolutely aweful time getting it to function. I am
currently running fedora core 6 on a dual processor 64 bit athlon cpu,
using the 2.6.20-1.2933.fc6 x86_64 kernel as provided by fedora updates.
If there's an easy way to get things to work, please let me know,
otherwise please read on to learn of the things I have tried and the
symptoms I experience.

A central difficulty is the inability to detect hd stations
either with "dtvscan -q" or inside mythtvsetup. I am using a cable
signal that provides 10 or 15 unencrypted HD channels using qcam, as
confirmed by my ability to see them on my hd capable TV (NO cable
card!!) and for a brief time on my older mythtv box, which was a 32 bit
athlon also running fc6. I abandoned that computer because of problems
with smooth playback of the HD stream, but cannot get the hd5500 to work
the same way it did in finding channels.

I have tried three different kernels and a number of different
configurations. Let me describe my attempts with the 2.6.19-1.6.5.2911
kernel, which matches (other than being 64 bit) what I ran on the old
box. After a clean install of the OS with just an update of the system
and to that kernel, it takes two boots for the dvb driver to be loaded.
the appropriate section from the boot messages are: (I have stripped the
time and date info)


: CORE cx88[0]: subsystem: 7063:5500, board: pcHDTV HD5500 HDTV [card=47,autodetected]
: TV tuner 64 at 0x1fe, Radio tuner -1 at 0x1fe
: i2c_adapter i2c-2: nForce2 SMBus adapter at 0x4c00
: i2c_adapter i2c-3: nForce2 SMBus adapter at 0x4c40
: tuner 4-0043: chip found @ 0x86 (cx88[0])
: tda9887 4-0043: tda988[5/6/7] found @ 0x43 (tuner)
: tuner 4-0061: chip found @ 0xc2 (cx88[0])
: tuner 4-0061: type set to 64 (LG TDVS-H06xF)
: tuner 4-0061: type set to 64 (LG TDVS-H06xF)
: cx88[0]/0: found at 0000:01:09.0, rev: 5, irq: 17, latency: 32, mmio: 0xfd000000
: cx88[0]/0: registered device video2 [v4l2]
: cx88[0]/0: registered device vbi2
: ACPI: PCI Interrupt Link [APCH] enabled at IRQ 23
: ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [APCH] -> GSI 23 (level, low) -> IRQ 23
: forcedeth: using HIGHDMA
: eth0: forcedeth.c: subsystem: 01565:2501 bound to 0000:00:0a.0
: ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 22
: ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [APCJ] -> GSI 22 (level, low) -> IRQ 22
: intel8x0_measure_ac97_clock: measured 50781 usecs
: intel8x0: clocking to 46875
: EDAC MC0: Giving out device to k8_edac Athlon64/Opteron: DEV 0000:00:18.2
: ACPI: PCI Interrupt 0000:01:09.1[A] -> Link [APC2] -> GSI 17 (level, low) -> IRQ 17
: cx88[0]/1: CX88x/0: ALSA support for cx2388x boards
: cx88[0]/2: cx2388x 8802 Driver Manager
: ACPI: PCI Interrupt 0000:01:09.2[A] -> Link [APC2] -> GSI 17 (level, low) -> IRQ 17
: cx88[0]/2: found at 0000:01:09.2, rev: 5, irq: 17, latency: 32, mmio: 0xfb000000
: ACPI: PCI Interrupt 0000:05:00.0[A] -> Link [APC3] -> GSI 18 (level, low) -> IRQ 18
: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 1.0-9755 Mon Feb 26 23:16:31 PST 2007
: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
: cx2388x dvb driver version 0.0.6 loaded
: cx8802_register_driver() ->registering driver type=dvb access=shared
: CORE cx88[0]: subsystem: 7063:5500, board: pcHDTV HD5500 HDTV [card=47]
: cx88[0]/2: cx2388x based dvb card
: DVB: registering new adapter (cx88[0]).
: DVB: registering frontend 0 (LG Electronics LGDT3303 VSB/QAM Frontend)..

The dvb device seems to be succesfully loaded.

If I run "dtvscan -q -c 78" (using qcam, and starting at the first
previously available digital channel) I get a confusing result: on the
channels that I believe are available it gets packets but declares that
the channel info is unavailable. the error is the same as I spoted on
the forums for a problem 64 versus 32 bits, but this was reported for
much older kernels. I can reproduce the actual error statement if
desired, but i am not right now running this kernel. I have tried both
versions of the tools available on your web page (dvb-atsc-tools 1.0.4
and ker-2.6.28 ), without improvement.

If I run mythtvsetup, it is somewhat more succesful -- it detects two
stations with a couple of subchannels on one of them. This is well
below the number of available channels. There is no signel information.

I have tried compiling the v4l/dvb driver from your web page,
(v4l-dvb-HD-5500-driver.tar.gz) but it does not compile. I have also
downloaded and compiled the latest drivers from linuxtv.org (v4l-dvb)
which DO compile, but which cause an error when the module is loaded.
It reports:

lgdt330x: lgdt330x_set_parameters: Modulation type(0) UNSUPPORTED
KERN_WARNING lgdt330x: lgdt3303_read_status: Modulation set to unsupported value

and it repeats this warning over and over.

this is after:

: CORE cx88[0]: subsystem: 7063:5500, board: pcHDTV HD5500 HDTV [card=47,autodetected]
: TV tuner 64 at 0x1fe, Radio tuner -1 at 0x1fe
: i2c_adapter i2c-2: nForce2 SMBus adapter at 0x4c00
: i2c_adapter i2c-3: nForce2 SMBus adapter at 0x4c40
: tuner 4-0043: chip found @ 0x86 (cx88[0])
: tda9887 4-0043: tda988[5/6/7] found @ 0x43 (tuner)
: tuner 4-0061: chip found @ 0xc2 (cx88[0])
: tuner 4-0061: type set to 64 (LG TDVS-H06xF)
: tuner 4-0061: type set to 64 (LG TDVS-H06xF)
: cx88[0]/0: found at 0000:01:09.0, rev: 5, irq: 17, latency: 32, mmio: 0xfd000000
: cx88[0]/0: registered device video2 [v4l2]
: cx88[0]/0: registered device vbi2
: ACPI: PCI Interrupt Link [APCH] enabled at IRQ 23
: ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [APCH] -> GSI 23 (level, low) -> IRQ 23
: forcedeth: using HIGHDMA
: eth0: forcedeth.c: subsystem: 01565:2501 bound to 0000:00:0a.0
: ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 22
: ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [APCJ] -> GSI 22 (level, low) -> IRQ 22
: intel8x0_measure_ac97_clock: measured 50781 usecs
: intel8x0: clocking to 46875
: EDAC MC0: Giving out device to k8_edac Athlon64/Opteron: DEV 0000:00:18.2
: ACPI: PCI Interrupt 0000:01:09.1[A] -> Link [APC2] -> GSI 17 (level, low) -> IRQ 17
: cx88[0]/1: CX88x/0: ALSA support for cx2388x boards
: cx88[0]/2: cx2388x 8802 Driver Manager
: ACPI: PCI Interrupt 0000:01:09.2[A] -> Link [APC2] -> GSI 17 (level, low) -> IRQ 17
: cx88[0]/2: found at 0000:01:09.2, rev: 5, irq: 17, latency: 32, mmio: 0xfb000000
: ACPI: PCI Interrupt 0000:05:00.0[A] -> Link [APC3] -> GSI 18 (level, low) -> IRQ 18
: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 1.0-9755 Mon Feb 26 23:16:31 PST 2007
: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
: cx2388x dvb driver version 0.0.6 loaded
: cx8802_register_driver() ->registering driver type=dvb access=shared
: CORE cx88[0]: subsystem: 7063:5500, board: pcHDTV HD5500 HDTV [card=47]
: cx88[0]/2: cx2388x based dvb card
: DVB: registering new adapter (cx88[0]).
: DVB: registering frontend 0 (LG Electronics LGDT3303 VSB/QAM Frontend)...

but nothing can then be accessed at all.

I updated to 2.6.20-1.2933.fc6 x86_64 and the dvb related module is no
longer automatically loaded. I can load it by hand "modprobe cx88-dvb"
but it then gives the same message over and over,

lgdt330x: lgdt330x_set_parameters: Modulation type(0) UNSUPPORTED
KERN_WARNING lgdt330x: lgdt3303_read_status: Modulation set to unsupported value

, with no access to channels either with dtvscan or mythtvsetup.

this is after:

: cx2388x dvb driver version 0.0.6 loaded
: cx8802_register_driver() ->registering driver type=dvb access=shared
: CORE cx88[0]: subsystem: 7063:5500, board: pcHDTV HD5500 HDTV [card=47]
: cx88[0]/2: cx2388x based dvb card
: DVB: registering new adapter (cx88[0]).
: DVB: registering frontend 0 (LG Electronics LGDT3303 VSB/QAM Frontend)...

which appears to indicate some success.

I have not yet tried compiling the linuxtv.org drivers for this kernel,
but they did not work for the 2925 vesion of the 2.6.20 kernel.

Please let me know which direction I should go in attempting to get this
thing working. I could really use your help!!

_________________
Tom G.
View user's profile Send private message
PostPosted: Sat Mar 31, 2007 3:39 pm Reply with quote
nybbler
 
Joined: 06 Jul 2006
Posts: 125




The reason you don't get channel information is most likely that it isn't there... the cable company is likely stripping it out. Annoying and illegal but I know they do it. My ultimate answer to that was an antenna.
View user's profile Send private message
PostPosted: Sat Mar 31, 2007 9:46 pm Reply with quote
gramila
 
Joined: 31 Mar 2007
Posts: 6




The channel info was there when the card was in my older 32 bit machine running nearly the same stuff. And in addition, my TV, which has an HD tuner, can currently display the channel call name instantly. So unless the cable company has really changed something, and changed it on the day I transferred the cards, it would appear, at least to me, to be a problem with the drivers or scanning code.

I do appreciate your suggestion, and may have to face giving the over the air route a try. I will certainly report if the problem persists, though
I am hoping that there might be other suggestions before giving up on cable hdtv. The disappointing part is that it worked well in the 32 bit machine, even with the two analog tuners in there.... Ugghhh.

_________________
Tom G.
View user's profile Send private message
PostPosted: Sun Apr 01, 2007 12:00 am Reply with quote
gramila
 
Joined: 31 Mar 2007
Posts: 6




Well I took your suggestion to heart and tried the over the air route. I am using a winegard square array antenna which works fine with my TV. But no better luck with the hd5500.

I had been able to lock and revieve packets from only two channels at best (still no channel info) with all my tinkering around using the cable as the source, with my best luck trying an old approach from a thread mentioned on these forums which I fouind in my digging. That was to uninstall a bunch of modules and then re-load the cx88-dvb:

modprobe -r cx88-dvb
modprobe -r cx8800
modprobe -r cx88-blackbird
modprobe symbol:lgdt330x_attach
modprobe cx88-dvb

It locked on two channels but could not get the channel info.

Switching over to over-the-air I tried dtvscan again and got about the same:
]# dtvscan
dtvscan ver 1.0.4 - by Jack Kelliher (c) 2002,2005,2006
Attempting to open /dev/dtv
Opened FE:/dev/dvb/adapter0/frontend0 3
Opened DMX:/dev/dvb/adapter0/demux0 4
Opened DVR:/dev/dvb/adapter0/dvr0 5
channel = 2 VSB_8
channel = 3 VSB_8

and so on, with only the following info on just two channels.:
channel = 36 VSB_8
Signal: 33
Signal: 33
Signal: 33
Signal: 33
channel = 37 VSB_8
channel = 38 VSB_8
Signal: 27
Signal: 27
Signal: 27

dtvscan for kernel 2.6.18 does no better and just gets nothing for all channels.

So.... Looks like my problems persist even with over-the-air signals.
I agree that this was worth a try.

Maybe you or someone else may have another suggestion???
Thanks.....

_________________
Tom G.
View user's profile Send private message
PostPosted: Sun Apr 01, 2007 9:20 am Reply with quote
nybbler
 
Joined: 06 Jul 2006
Posts: 125




The fact that you are getting a signal at all indicates that the software is probably working. If the card hadn't worked before I'd suspect a bad card.
If you haven't already, you might want to check your cables, and the push-on connector for the card, that sort of thing. You might also try a different PCI slot; if the slot it is in is very close to a noise source it could create the low signal levels you are seeing.

I'm not sure what's going on with your "modulation type unsupported" issue; I'm using the latest v4l-dvb drivers (pulled as of 3/30/2007) on a 2.6.20 kernel and I don't get that.
View user's profile Send private message
PostPosted: Sun Apr 01, 2007 5:46 pm Reply with quote
gramila
 
Joined: 31 Mar 2007
Posts: 6




Well I've got a small bit of progress to report. I decided, in desperation, to abandon the 64 bit distribution and to reinstall fedora core 6 based on the 32 bit disks. -- did that, updated to all the latest rpms, and compiled the most recent drivers from linuvtv.org. Still not alot of luck with dtvscan, my analog signal gives a couple of channels and does not always repeat, while my cable signal sees packets, but can not get channel information.

I came across another approach to scanning for channels, and BINGO! I can see all the channels that I could see before. its scandvb (alias scan or dvbscan) from dvb-apps (alias dvb-utils). the line that gets me there is:

scandvb -A 2 /usr/share/dvb-apps/atsc/us-Cable-Standard-center-frequencies-QAM256

which looks at ALL the US cable hd channels, and uses qcam.
it finds all the channels that I had been able to see earlier.
dtvscan from pcHDTV still fails to get anything. It continues to proclaim:
Unable to recieve valid packets
did find pat
`ERROR vct item ptr null couldn't get channel info

Now if I can figure out how to get this info into mythtv (after I reinstall all of mythtv...) then I can be happy.....

Thanks for the suggestions -- please comment if anyone has more to try!

_________________
Tom G.
View user's profile Send private message
PostPosted: Mon Apr 09, 2007 9:02 am Reply with quote
daver
 
Joined: 08 Apr 2007
Posts: 5




gramila,

I think I'm seeing exactly the same thing that you did. (See my posts at http://www.pchdtv.com/forum/viewtopic.php?t=3663.) I'm also using a newly upgraded 2.6.20-1.2933.fc6 kernel on an Athlon 64, and the upgrade seems to have broken my system.

I am able to scan channels using the "scandvb" command line that you provided but get all the same error messages you see when scanning with dtvscan. I also get timeouts when scanning for digital channels within mythtv-setup and seem to get the same lgdt330x errors you do (although I think mine may say that modulation type "6" is unsupported).

Just like you, I had previously been receiving about 15 unencrypted QAM256 signals off a Comcast cable input. I have also had success previously receiving OTA signals but have not tried that again since having the problems with the cable signal. I have also downloaded, compiled, and installed the latest v4l-dvb drivers from linuxtv.org, but that didn't fix the problem for me either.

Did you ever solve your problem?

Dave
View user's profile Send private message
PostPosted: Mon Apr 09, 2007 5:47 pm Reply with quote
rhumbliner
 
Joined: 08 Apr 2007
Posts: 1
Location: Park City || Las Vegas




gramila,

i'm a newbie with mythtv but i'm also seeing the same results on my gentoo system with a 2.6.20-r5 kernel running on an athlon-64. i see no channels, but my tv does, and my log is full of these messages:

lgdt330x: lgdt3303_read_snr: Modulation set to unsupported value
lgdt330x: lgdt330x_set_parameters: Modulation type(6) UNSUPPORTED
KERN_WARNING lgdt330x: lgdt3303_read_status: Modulation set to unsupported value

i have no idea what to try next.
View user's profile Send private message
PostPosted: Mon Apr 09, 2007 6:34 pm Reply with quote
daver
 
Joined: 08 Apr 2007
Posts: 5




This appears to be a problem on more than just pcHDTV cards. Go over to http://www.gossamer-threads.com/lists/mythtv/users/ and do a search on "cx88-dvb". There was a thread on March 25 talking about how scanning for channels is broken on the 2.6.20 kernel but there seems to be a disagreement about what is causing the problem and whether or not it is really a kernel issue.

Anyone have any ideas or solutions???
View user's profile Send private message
PostPosted: Tue Apr 10, 2007 1:37 pm Reply with quote
electronikjunkie
 
Joined: 11 Dec 2006
Posts: 15




I've been having similar issues, but have not found a solution. See: http://mythtv.org/pipermail/mythtv-users/2007-April/176370.html

When I get home I'm going to try the suggestions here: http://www.mythtv.org/wiki/index.php/Adding_QAM_Channels_For_HDTV_Tuner_Cards

It says to make sure your Zap2It account has a digital lineup for your digital card and an analog lineup for your analog card. I only had an analog lineup before. I also havn't tried scanning with anything, but mythtv. All though I have had success scanning before, but everything is screwed up now...
View user's profile Send private message
PostPosted: Tue Apr 10, 2007 1:48 pm Reply with quote
xyzzy
 
Joined: 12 Feb 2006
Posts: 225




rhumbliner wrote:

lgdt330x: lgdt3303_read_snr: Modulation set to unsupported value
lgdt330x: lgdt330x_set_parameters: Modulation type(6) UNSUPPORTED


Modulation type 6 is qam-auto and the pchd-5500 doesn't support qam-auto. You need to get myth to somehow use qam-256 or qam-64.
View user's profile Send private message
PostPosted: Tue Apr 10, 2007 1:55 pm Reply with quote
electronikjunkie
 
Joined: 11 Dec 2006
Posts: 15




xyzzy wrote:
rhumbliner wrote:

lgdt330x: lgdt3303_read_snr: Modulation set to unsupported value
lgdt330x: lgdt330x_set_parameters: Modulation type(6) UNSUPPORTED


Modulation type 6 is qam-auto and the pchd-5500 doesn't support qam-auto. You need to get myth to somehow use qam-256 or qam-64.


Really. I selected QAM-256 when scanning. Huh? I'll have to try 128 or 64. Thank you.

***edit***
Whoops. My errors don't suggest type(6). They just say this:

Code:
[  696.002456] KERN_WARNING lgdt330x: lgdt3303_read_status: Modulation set
to unsupported value


I'm going to try mythtv .19 and see if that helps. I'll let you know my results...
View user's profile Send private message
PostPosted: Tue Apr 10, 2007 2:52 pm Reply with quote
daver
 
Joined: 08 Apr 2007
Posts: 5




xyzzy wrote:
Modulation type 6 is qam-auto and the pchd-5500 doesn't support qam-auto. You need to get myth to somehow use qam-256 or qam-64.


This is helpful to know. Looks like I may just have to generate a channels.conf file using:

scandvb -A 2 /usr/share/dvb-apps/atsc/us-Cable-Standard-center-frequencies-QAM256

and then import that file into mythtv instead of running the scan within mythtv-setup. (Must be a problem with the modulation type setting in the updated mythtv-suite from atrpms.) I'll try it tonight when I get home and report back.

Thanks.
View user's profile Send private message
PostPosted: Wed Apr 11, 2007 7:54 am Reply with quote
gramila
 
Joined: 31 Mar 2007
Posts: 6




Daver,
That command is what I used to generate a channel.conf, and have succesfully imported it, after editing out the encrypted channels, into mythtv. (Sorry I missed your earlier request, though the discussion on gossamer threads is new to me-- thanks!)

Importing like this It leaves one without programming information, so while you can watch live TV, recording by program selection is broken. The only way I could find to fix this was to edit, by hand, the station information, adding the station identifier. I did this by watching live TV, hitting e for edit, and pasting in the station identification number that you can get from zap2it by looking at the HTML page source for your listings. After doing this, mythfilldatabase worked and I could see entries in the myth tv listings and when watching live tv.

Its a clumsy process, but seems to function. The thing that really tripped me up was that BOTH dtvscan from pchdtv and the mythtv channel scanning were broken. I had assumed that something was wrong with the drivers.

Good Luck!!

_________________
Tom G.
View user's profile Send private message
PostPosted: Wed Apr 11, 2007 8:03 am Reply with quote
gramila
 
Joined: 31 Mar 2007
Posts: 6




rhumbliner,
I was able to fix that part by downloading and compiling the latest v4l-dvb drivers from linuxtv.org. Following their instructions, than rebooting twice made the errors you mention go away...
Good Luck!!

~~~~~~~~~~~~~~~~
i'm a newbie with mythtv but i'm also seeing the same results on my gentoo system with a 2.6.20-r5 kernel running on an athlon-64. i see no channels, but my tv does, and my log is full of these messages:

lgdt330x: lgdt3303_read_snr: Modulation set to unsupported value
lgdt330x: lgdt330x_set_parameters: Modulation type(6) UNSUPPORTED
KERN_WARNING lgdt330x: lgdt3303_read_status: Modulation set to unsupported value

i have no idea what to try next.[/quote]

_________________
Tom G.
View user's profile Send private message
Problems with hd5500 station detection
  pcHDTV Forum Index -> Installation/Setup
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  Reply to topic  


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