[linux-dvb] Hauppauge Nova-T PCI: cx8802_timeout

Sid Boyce sboyce at blueyonder.co.uk
Fri Sep 23 08:25:06 CEST 2005


Michael Krufky wrote:
> Mark Weaver wrote:
> 
>> I have recently acquired a hauppauge nova-t card which I'm trying to get
>> working, using current CVS + 2.6.12.  dmesg output on module load:
>>
>> cx2388x v4l2 driver version 0.0.5 loaded
>> ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 16
>> ACPI: PCI Interrupt 0000:02:08.0[A] -> Link [LNKC] -> GSI 16 (level,
>> low) -> IRQ 225
>> 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
>> cx88[0]: hauppauge eeprom: model=90002, tuner=76
>> cx88[0]: registered IR remote control
>> cx88[0]/0: found at 0000:02:08.0, rev: 5, irq: 225, latency: 32, mmio:
>> 0xfb000000
>> cx88[0]/0: registered device video1 [v4l2]
>> cx88[0]/0: registered device vbi1
>> cx2388x blackbird driver version 0.0.5 loaded
>> cx2388x dvb driver version 0.0.5 loaded
>> ACPI: PCI Interrupt 0000:02:08.2[A] -> Link [LNKC] -> GSI 16 (level,
>> low) -> IRQ 225
>> cx88[0]/2: found at 0000:02:08.2, rev: 5, irq: 225, latency: 32, mmio:
>> 0xfc000000
>> cx88[0]/2: cx2388x based dvb card
>> DVB: registering new adapter (cx88[0]).
>> DVB: registering frontend 1 (Conexant CX22702 DVB-T)...
>>
>> The card appears to tune fine with tzap, although I never get any data
>> from it:
> 
> 
> Are you doing tzap CHAN_XX -r  ?
> 
> -r is the key.
> 
>> cx88[0]/2: cx8802_timeout
>> cx88[0]/2: cx8802_stop_dma
>> cx88[0]/2: restarting queue
>> cx88[0]/2: cx8802_restart_queue
>> cx88[0]/2: cx8802_restart_queue: queue is empty
>> cx88[0]/2: queue is empty - first active
>> cx88[0]/2: cx8802_start_dma w: 0, h: 0, f: 2
>> cx88[0]/2: setting the interrupt mask
>> cx88[0]/2: [f653cdc0/0] cx8802_buf_queue - first active
>>
>> is repeated over and over in the logs.
>>
>> I've had a bit of a poke around, but I'm at a loss as to what to try 
>> next.
> 
> 
> I get the same messages with my cx88 boards.  They annoy me, but I never 
> really cared.  There's probably some verbosity default setting set too 
> high. Does anybody know if these messages are important enough to keep 
> visible by default?
> 

They just fill up my dmesg, overwriting other stuff that may be 
important. It would be better if they were scaled right back or 
verbosity could be turned on when troubleshooting.
Regards
Sid.
-- 
Sid Boyce ... Hamradio License G3VBV, licensed Private Pilot
Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support 
Specialist
Microsoft Windows Free Zone - Linux used for all Computing Tasks



More information about the linux-dvb mailing list