Log in Register FAQ Memberlist Search pcHDTV Forum Index
pcHDTV Forum

pcHDTV Forum Index -> Installation/Setup -> Got to be a hardware problem
Post new topic  Reply to topic View previous topic :: View next topic 
Got to be a hardware problem
PostPosted: Thu Mar 15, 2007 11:53 am Reply with quote
batdog
 
Joined: 15 Mar 2007
Posts: 3




I bought a 5500 at end of Feb and have gotten exactly nothing from it. I've tried OTA and Cable/QAM. Using latest drivers from linuxtv.org and vanilla 2.6.20.1 kernel on amd64 system.




Code:

# ./atscscan -o 2 67                                                                                           
atscscan V2.0 Copyright (C) 2006 Trent Piepho <xyzzy@speakeasy.org>
With ignore signal stength hack for LGDT3303
Linux DVB based ATSC OTA/Cable channel scanning tool
Using DVB adapter #0
Using OTA US Broadcast frequencies w/ 8-VSB
LGDT330x Front-end detected, disabling signal strength checking
Tuning to channel 2 (57.0000 MHz): ###### Unable to tune channel
Tuning to channel 3 (63.0000 MHz): ###### Unable to tune channel
Tuning to channel 4 (69.0000 MHz): ###### Unable to tune channel
Tuning to channel 5 (79.0000 MHz): # LOCK Strength = 0.0%
Timeout waiting for data to arrive.
There is probably no station you can receive on this frequency.
Error getting table!
Unable to receive PAT, giving up on this channel
Tuning to channel 6 (85.0000 MHz): ###### Unable to tune channel
Tuning to channel 7 (177.0000 MHz): ###### Unable to tune channel
Tuning to channel 8 (183.0000 MHz): ###### Unable to tune channel
Tuning to channel 9 (189.0000 MHz): # LOCK Strength = 12.5%
 LOCK Strength = 11.8%
 LOCK Strength = 12.4%
 LOCK Strength = 11.1%
 LOCK Strength = 12.8%
 Unable to tune channel
Tuning to channel 10 (195.0000 MHz): ###### Unable to tune channel
Tuning to channel 11 (201.0000 MHz): ###### Unable to tune channel
Tuning to channel 12 (207.0000 MHz): ###### Unable to tune channel
Tuning to channel 13 (213.0000 MHz): ###### Unable to tune channel
Tuning to channel 14 (473.0000 MHz): ###### Unable to tune channel
Tuning to channel 15 (479.0000 MHz): ###### Unable to tune channel
Tuning to channel 16 (485.0000 MHz): ###### Unable to tune channel
Tuning to channel 17 (491.0000 MHz): ###### Unable to tune channel
Tuning to channel 18 (497.0000 MHz): ## LOCK Strength = 0.0%
Timeout waiting for data to arrive.
There is probably no station you can receive on this frequency.
Error getting table!
Unable to receive PAT, giving up on this channel
Tuning to channel 19 (503.0000 MHz): # LOCK Strength = 50.7%
Timeout waiting for data to arrive.
There is probably no station you can receive on this frequency.
Error getting table!
Unable to receive PAT, giving up on this channel
Tuning to channel 20 (509.0000 MHz): ###### Unable to tune channel
Tuning to channel 21 (515.0000 MHz): ###### Unable to tune channel
Tuning to channel 22 (521.0000 MHz): ###### Unable to tune channel
Tuning to channel 23 (527.0000 MHz): ###### Unable to tune channel
Tuning to channel 24 (533.0000 MHz): # LOCK Strength = 13.3%
 LOCK Strength = 13.5%
 LOCK Strength = 16.4%
Timeout waiting for data to arrive.
There is probably no station you can receive on this frequency.
Error getting table!
Unable to receive PAT, giving up on this channel
Tuning to channel 25 (539.0000 MHz): ###### Unable to tune channel
Tuning to channel 26 (545.0000 MHz): ###### Unable to tune channel
Tuning to channel 27 (551.0000 MHz): # LOCK Strength = 52.0%
Timeout waiting for data to arrive.
There is probably no station you can receive on this frequency.
Error getting table!
Unable to receive PAT, giving up on this channel
Tuning to channel 28 (557.0000 MHz): ###### Unable to tune channel
Tuning to channel 29 (563.0000 MHz): ###### Unable to tune channel
Tuning to channel 30 (569.0000 MHz): ###### Unable to tune channel
Tuning to channel 31 (575.0000 MHz): # LOCK Strength = 58.6%
Timeout waiting for data to arrive.
There is probably no station you can receive on this frequency.
Error getting table!
Unable to receive PAT, giving up on this channel
Tuning to channel 32 (581.0000 MHz): # LOCK Strength = 53.8%
Timeout waiting for data to arrive.
There is probably no station you can receive on this frequency.
Error getting table!
Unable to receive PAT, giving up on this channel
Tuning to channel 33 (587.0000 MHz): ###### Unable to tune channel
Tuning to channel 34 (593.0000 MHz): ###### Unable to tune channel
Tuning to channel 35 (599.0000 MHz): # LOCK Strength = 67.2%
Timeout waiting for data to arrive.
There is probably no station you can receive on this frequency.
Error getting table!
Unable to receive PAT, giving up on this channel
Tuning to channel 36 (605.0000 MHz): # LOCK Strength = 54.9%
Timeout waiting for data to arrive.
There is probably no station you can receive on this frequency.
Error getting table!
Unable to receive PAT, giving up on this channel
Tuning to channel 37 (611.0000 MHz): ###### Unable to tune channel
Tuning to channel 38 (617.0000 MHz): # LOCK Strength = 61.7%
Timeout waiting for data to arrive.
There is probably no station you can receive on this frequency.
Error getting table!
Unable to receive PAT, giving up on this channel
Tuning to channel 39 (623.0000 MHz): ###### Unable to tune channel
Tuning to channel 40 (629.0000 MHz): ###### Unable to tune channel
Tuning to channel 41 (635.0000 MHz): # LOCK Strength = 0.0%
Timeout waiting for data to arrive.
There is probably no station you can receive on this frequency.
Error getting table!
Unable to receive PAT, giving up on this channel
Tuning to channel 42 (641.0000 MHz): # LOCK Strength = 23.0%
Timeout waiting for data to arrive.
There is probably no station you can receive on this frequency.
Error getting table!
Unable to receive PAT, giving up on this channel
Tuning to channel 43 (647.0000 MHz): ###### Unable to tune channel
Tuning to channel 44 (653.0000 MHz): # LOCK Strength = 65.8%
Timeout waiting for data to arrive.
There is probably no station you can receive on this frequency.
Error getting table!
Unable to receive PAT, giving up on this channel
Tuning to channel 45 (659.0000 MHz): ###### Unable to tune channel
Tuning to channel 46 (665.0000 MHz): # LOCK Strength = 23.7%
Timeout waiting for data to arrive.
There is probably no station you can receive on this frequency.
Error getting table!
Unable to receive PAT, giving up on this channel
Tuning to channel 47 (671.0000 MHz): ###### Unable to tune channel
Tuning to channel 48 (677.0000 MHz): # LOCK Strength = 43.5%
Timeout waiting for data to arrive.
There is probably no station you can receive on this frequency.
Error getting table!
Unable to receive PAT, giving up on this channel
Tuning to channel 49 (683.0000 MHz): ###### Unable to tune channel
Tuning to channel 50 (689.0000 MHz): ###### Unable to tune channel
Tuning to channel 51 (695.0000 MHz): ## LOCK Strength = 0.0%
Timeout waiting for data to arrive.
There is probably no station you can receive on this frequency.
Error getting table!
Unable to receive PAT, giving up on this channel
Tuning to channel 52 (701.0000 MHz): # LOCK Strength = 0.0%
Timeout waiting for data to arrive.
There is probably no station you can receive on this frequency.
Error getting table!
Unable to receive PAT, giving up on this channel
Tuning to channel 53 (707.0000 MHz): ###### Unable to tune channel
Tuning to channel 54 (713.0000 MHz): ###### Unable to tune channel
Tuning to channel 55 (719.0000 MHz): ###### Unable to tune channel
Tuning to channel 56 (725.0000 MHz): ###### Unable to tune channel
Tuning to channel 57 (731.0000 MHz): ###### Unable to tune channel
Tuning to channel 58 (737.0000 MHz): ###### Unable to tune channel
Tuning to channel 59 (743.0000 MHz): ###### Unable to tune channel
Tuning to channel 60 (749.0000 MHz): ###### Unable to tune channel
Tuning to channel 61 (755.0000 MHz): ###### Unable to tune channel
Tuning to channel 62 (761.0000 MHz): ###### Unable to tune channel
Tuning to channel 63 (767.0000 MHz): ###### Unable to tune channel
Tuning to channel 64 (773.0000 MHz): ###### Unable to tune channel
Tuning to channel 65 (779.0000 MHz): ###### Unable to tune channel
Tuning to channel 66 (785.0000 MHz): # LOCK Strength = 0.0%
Timeout waiting for data to arrive.
There is probably no station you can receive on this frequency.
Error getting table!
Unable to receive PAT, giving up on this channel
Tuning to channel 67 (791.0000 MHz): ###### Unable to tune channel


It is able to lock on several frequencies (some with reasonably strong signals). Using dtvsignal, the strongest of these is 44:

Code:

# ./dtvsignal 44                                                                                               
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
tuning to 653000000 Hz
video pid 0x0021, audio pid 0x0024
dtvsignal ver 1.0.4 - by Jack Kelliher (c) 2002,2005,2006
channel = 44 freq = 653000000Hz
 30db       0%         25%         50%         75%        100%
Signal:     |     .     :     .     |     ._____:_____._____|
Signal: 081 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$


dmesg is full of cx8802_timeout messages. getatsc does nothing on any of the channels for which I get a signal. dtvscan and dvbscan have similar results. I think the modules are loaded correctly, as far as I can tell:

Code:

cx2388x alsa driver version 0.0.6 loaded
CORE cx88[0]: subsystem: 7063:5500, board: pcHDTV HD5500 HDTV [card=47,autodetected]
cx2388x cx88-mpeg Driver Manager version 0.0.6 loaded
cx2388x v4l2 driver version 0.0.6 loaded
cx88[0]/1: CX88x/0: ALSA support for cx2388x boards
cx88[0]/0: found at 0000:01:07.0, rev: 5, irq: 17, latency: 32, mmio: 0xf8000000
tuner 2-0043: chip found @ 0x86 (cx88[0])
tuner 2-0061: chip found @ 0xc2 (cx88[0])
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
cx88[0]/2: cx2388x 8802 Driver Manager
cx88[0]/2: found at 0000:01:07.2, rev: 5, irq: 17, latency: 32, mmio: 0xfa000000
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]).


I think maybe I just have a bad card? That's all I can think of at this point. It has been most frustrating. Any further advice would be greatly welcome.
View user's profile Send private message
PostPosted: Fri Mar 16, 2007 10:12 am Reply with quote
nybbler
 
Joined: 06 Jul 2006
Posts: 125




Have you confirmed that you can get any of these stations with another tuner? Also, check all the cables and splitters; a bad cable or splitter can ruin any chance of getting a good signal.
View user's profile Send private message
PostPosted: Fri Mar 16, 2007 7:20 pm Reply with quote
xyzzy
 
Joined: 12 Feb 2006
Posts: 225




Have you tried analog, and does that work?

Since the signal readings are ok for some channels, yet you get no data, it sounds like some kind of IRQ problem. Is the MPEG port assigned an interrupt in lspci -v? Does /proc/interrupts show activity on this interrupt when you try to use the dvb device? Try booting with the noapic option and/or acpi=noirq and see if that has any effect. Just worry about scanning the stations you get a good signal on, 35, 38, 44.
View user's profile Send private message
PostPosted: Sat Mar 17, 2007 6:12 pm Reply with quote
batdog
 
Joined: 15 Mar 2007
Posts: 3




xyzzy wrote:
Have you tried analog, and does that work?

Since the signal readings are ok for some channels, yet you get no data, it sounds like some kind of IRQ problem. Is the MPEG port assigned an interrupt in lspci -v? Does /proc/interrupts show activity on this interrupt when you try to use the dvb device? Try booting with the noapic option and/or acpi=noirq and see if that has any effect. Just worry about scanning the stations you get a good signal on, 35, 38, 44.


You're on to something. Relevant part of lspci -v gives this:

Code:

01:07.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05)
        Subsystem: pcHDTV Unknown device 5500
        Flags: bus master, medium devsel, latency 32, IRQ 17
        Memory at f8000000 (32-bit, non-prefetchable) [size=16M]
        Capabilities: [44] Vital Product Data
        Capabilities: [4c] Power Management version 2

01:07.1 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] (rev 05)
        Subsystem: pcHDTV Unknown device 5500
        Flags: bus master, medium devsel, latency 32, IRQ 17
        Memory at fb000000 (32-bit, non-prefetchable) [size=16M]
        Capabilities: [4c] Power Management version 2

01:07.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05)
        Subsystem: pcHDTV Unknown device 5500
        Flags: bus master, medium devsel, latency 32, IRQ 17
        Memory at fa000000 (32-bit, non-prefetchable) [size=16M]
        Capabilities: [4c] Power Management version 2

01:07.4 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [IR Port] (rev 05)
        Subsystem: pcHDTV Unknown device 5500
        Flags: bus master, medium devsel, latency 32, IRQ 11
        Memory at f9000000 (32-bit, non-prefetchable) [size=16M]
        Capabilities: [4c] Power Management version 2


So, it's IRQ 17. But /proc/interrupts reveals nothing shows up there:

Code:

# cat /proc/interrupts
           CPU0       CPU1
  0:      93391   23459582   IO-APIC-edge      timer
  1:          0          8   IO-APIC-edge      i8042
  6:          0          3   IO-APIC-edge      floppy
  8:          0          0   IO-APIC-edge      rtc
  9:          0          0   IO-APIC-fasteoi   acpi
 12:          0          4   IO-APIC-edge      i8042
 14:          0         37   IO-APIC-edge      ide0
 16:       8307    1939251   IO-APIC-fasteoi   ohci1394, EMU10K1
 17:          0          0   IO-APIC-fasteoi   cx88[0], cx88[0], cx88[0]
 18:      20278    5879886   IO-APIC-fasteoi   ohci1394, nvidia
 20:          0          0   IO-APIC-fasteoi   ehci_hcd:usb1
 21:          0          0   IO-APIC-fasteoi   libata
 22:       3299     498529   IO-APIC-fasteoi   libata, NVidia CK804
 23:      82748   41060054   IO-APIC-fasteoi   ohci_hcd:usb2, eth0
NMI:       9969       9294
LOC:   23554039   23554016
ERR:          0


I'll try booting with noapic and acpi=noirq as soon as my kids get off the mythtv...

Thanks,
Joel
View user's profile Send private message
noapic doesn't help
PostPosted: Sun Mar 18, 2007 6:13 pm Reply with quote
batdog
 
Joined: 15 Mar 2007
Posts: 3




Partial update: booting with noapic doesn't help. The assigned IRQ is 11 instead of 17 in this case, but interrupts are still not being picked up by the kernel. Next thing i will try is installing the card in another machine.
View user's profile Send private message
Got to be a hardware problem
  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