Andy Walls wrote: > On Fri, 2008-08-29 at 16:44 -0400, Josh Becigneul wrote: > >> Hi Andy, >> >> This is what I get on my working box. Hope it helps. >> >> otherbox vsnine # lspci -tvv >> -[0000:00]-+-00.0 VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host >> Bridge >> +-00.1 VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host >> Bridge >> +-00.2 VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host >> Bridge >> +-00.3 VIA Technologies, Inc. PT890 Host Bridge >> +-00.4 VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host >> Bridge >> +-00.7 VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host >> Bridge >> +-01.0-[0000:01]--+-00.0 ATI Technologies Inc RV410 [Radeon >> X700 Pro (PCIE)] >> | \-00.1 ATI Technologies Inc RV410 [Radeon >> X700 Pro (PCIE)] (Secondary) >> +-09.0 D-Link System Inc DGE-530T Gigabit Ethernet Adapter >> (rev 11) >> +-0a.0 Conexant Unknown device 5b7a >> +-0f.0 VIA Technologies, Inc. VIA VT6420 SATA RAID Controller >> +-0f.1 VIA Technologies, Inc. >> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE >> +-10.0 VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller >> +-10.1 VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller >> +-10.2 VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller >> +-10.3 VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller >> +-10.4 VIA Technologies, Inc. USB 2.0 >> +-11.0 VIA Technologies, Inc. VT8237 ISA bridge >> [KT600/K8T800/K8T890 South] >> +-11.5 VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio >> Controller >> \-12.0 VIA Technologies, Inc. VT6102 [Rhine-II] >> >> >> otherbox vsnine # lspci -s 0:0a.0 -vv -x >> 00:0a.0 Multimedia video controller: Conexant Unknown device 5b7a >> Subsystem: Hauppauge computer works Inc. Unknown device 7404 >> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- >> ParErr- Stepping- SERR- FastB2B- DisINTx- >> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- >> <TAbort- <MAbort- >SERR- <PERR- INTx- >> Latency: 64 (500ns min, 50000ns max), Cache Line Size: 32 bytes >> Interrupt: pin A routed to IRQ 18 >> Region 0: Memory at f8000000 (32-bit, non-prefetchable) [size=64M] >> Capabilities: [44] Vital Product Data <?> >> Capabilities: [4c] Power Management version 2 >> Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA >> PME(D0-,D1-,D2-,D3hot-,D3cold-) >> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >> Kernel driver in use: cx18 >> Kernel modules: cx18 >> 00: f1 14 7a 5b 06 00 90 02 00 00 00 04 08 40 00 00 >> 10: 00 00 00 f8 00 00 00 00 00 00 00 00 00 00 00 00 >> 20: 00 00 00 00 00 00 00 00 00 00 00 00 70 00 04 74 >> 30: 00 00 00 00 44 00 00 00 00 00 00 00 05 01 02 c8 >> >> I'm on an older version of the driver, however. I'll update and see if >> there is any difference. >> > > OK. Your card appears to be right on the main segment behind the host > CPU bridge. > > Does the card and cx18 driver work for you in this configuration? > > Regards, > Andy > >
Yeah, aside from not having a decent antenna, the channels I can pick up usually come in well. Currently the analog is connected to the RF out of our satellite unit, and I use MythTV to watch. When I updated my kernel and the drivers from the repo, I also got an invalid firmware error. So I untarred them again and replaced the existing ones, and then did a modprobe cx18. I'm not sure if replacing the firmware or reloading the module did the trick. Unsuccessful load: [ 336.950151] Linux video capture interface: v2.00 [ 336.963637] cx18: Start initialization, version 1.0.0 [ 336.963979] cx18-0: Initializing card #0 [ 336.963984] cx18-0: Autodetected Hauppauge card [ 336.964012] ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 18 (level, low) -> IRQ 18 [ 336.964025] cx18-0: Unreasonably low latency timer, setting to 64 (was 32) [ 336.968300] cx18-0: cx23418 revision 01010000 (B) [ 337.048796] i2c-adapter i2c-1: NAK from device addr 0x50 msg #0 [ 337.049313] tveeprom 1-0050: Huh, no eeprom present (err=-121)? [ 337.049317] tveeprom 1-0050: Encountered bad packet header [00]. Corrupt or not a Hauppauge eeprom. [ 337.049320] cx18-0: Invalid EEPROM [ 337.049322] cx18-0: VBI is not yet supported [ 337.245795] tuner 2-0043: chip found @ 0x86 (cx18 i2c driver #0-1) [ 337.251265] tda9887 2-0043: creating new instance [ 337.251271] tda9887 2-0043: tda988[5/6/7] found [ 337.356994] tuner 2-0061: chip found @ 0xc2 (cx18 i2c driver #0-1) [ 337.357227] cs5345 1-004c: chip found @ 0x98 (cx18 i2c driver #0-0) [ 337.388422] i2c-adapter i2c-1: NAK from device addr 0x4c msg #0 [ 337.411420] i2c-adapter i2c-1: NAK from device addr 0x4c msg #0 [ 337.433414] i2c-adapter i2c-1: NAK from device addr 0x4c msg #0 [ 337.434159] cx18-0: Disabled encoder IDX device [ 337.437122] cx18-0: Registered device video0 for encoder MPEG (2 MB) [ 337.437310] DVB: registering new adapter (cx18) [ 337.475073] i2c-adapter i2c-1: NAK from device addr 0x19 msg #0 [ 337.475591] s5h1409_readreg: readreg error (ret == -121) [ 337.475749] cx18-0: frontend initialization failed [ 337.476595] cx18-0: DVB failed to register [ 337.478795] cx18-0: Registered device video32 for encoder YUV (2 MB) [ 337.479013] cx18-0: Registered device video24 for encoder PCM audio (1 MB) [ 337.479102] cx18-0: Registered device radio0 for encoder radio [ 337.479351] cx18-0: Error -12 registering devices [ 337.479886] tda9887 2-0043: destroying instance [ 337.480083] cx18-0: Error -12 on initialization [ 337.480196] cx18: probe of 0000:00:0a.0 failed with error -12 [ 337.480287] cx18: End initialization Sucessful Load: [ 342.823968] Linux video capture interface: v2.00 [ 342.830634] cx18: Start initialization, version 1.0.0 [ 342.830879] cx18-0: Initializing card #0 [ 342.830884] cx18-0: Autodetected Hauppauge card [ 342.833532] cx18-0: cx23418 revision 01010000 (B) [ 342.927966] tveeprom 1-0050: Hauppauge model 74021, rev C1B2, serial# 876046 [ 342.927973] tveeprom 1-0050: MAC address is 00-0D-FE-0D-5E-0E [ 342.927976] tveeprom 1-0050: tuner model is TCL M2523_5N_E (idx 112, type 50) [ 342.927979] tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08) [ 342.927982] tveeprom 1-0050: audio processor is CX23418 (idx 38) [ 342.927984] tveeprom 1-0050: decoder processor is CX23418 (idx 31) [ 342.927986] tveeprom 1-0050: has no radio, has IR receiver, has IR transmitter [ 342.927989] cx18-0: Autodetected Hauppauge HVR-1600 [ 342.927992] cx18-0: VBI is not yet supported [ 342.949073] i2c-adapter i2c-2: NAK from device addr 0x43 msg #0 [ 342.949528] tuner 2-0061: chip found @ 0xc2 (cx18 i2c driver #0-1) [ 342.949625] cs5345 1-004c: chip found @ 0x98 (cx18 i2c driver #0-0) [ 342.957416] tuner-simple 2-0061: creating new instance [ 342.957422] tuner-simple 2-0061: type set to 50 (TCL 2002N) [ 342.958678] cx18-0: Disabled encoder IDX device [ 342.958836] cx18-0: Registered device video0 for encoder MPEG (2 MB) [ 342.958926] DVB: registering new adapter (cx18) [ 343.029108] MXL5005S: Attached at address 0x63 [ 343.029314] DVB: registering frontend 0 (Samsung S5H1409 QAM/8VSB Frontend)... [ 343.029457] cx18-0: DVB Frontend registered [ 343.029562] cx18-0: Registered device video32 for encoder YUV (2 MB) [ 343.029648] cx18-0: Registered device video24 for encoder PCM audio (1 MB) [ 343.029652] cx18-0: Initialized card #0: Hauppauge HVR-1600 [ 343.029825] cx18: End initialization [ 343.958452] cx18-0: loaded v4l-cx23418-apu.fw firmware V00120000 (141200 bytes) [ 344.032847] cx18-0: loaded v4l-cx23418-cpu.fw firmware (158332 bytes) [ 344.035730] cx18-0: FW version: 0.0.74.0 (Release 2007/03/12) [ 344.359173] cx18-0: loaded v4l-cx23418-dig.fw firmware (16382 bytes) I'm still seeing those i2c errors, but I'm not sure if they are causing any harm. I haven't actually sat and watched a stream for some time, the FTA satellite has been down for a couple of weeks now. Regards, Josh Becigneul >> Andy Walls wrote: >> >>> Hi all, >>> >>> I have a question. >>> >>> For users of HVR-1600 and other CX23418 based cards that basically work: >>> is your card behind a PCI-PCI bridge chip that is set for "subtractive >>> decode"? >>> >>> For users of HVR-1600 and other CX23418 based cards that basically don't >>> work: Is your card behind a not behind a PCI-PCI bridge chip that is set >>> for "subtractive decode" (i.e. directly behind a host bridge, or behind >>> a PCI-PCI bridge set for positive decode)? >>> >>> >>> Here's an example, run as root, showing how to see if you have the >>> CX23418 behind a PCI-PCI bridge set for subtractive decode: >>> >>> # lspci -tvv >>> -[0000:00]-+-00.0 ATI Technologies Inc Unknown device 7911 >>> +-01.0-[0000:01]----05.0 ATI Technologies Inc Radeon 2100 >>> [...] >>> +-14.4-[0000:03]--+-02.0 Internext Compression Inc iTVC16 >>> (CX23416) MPEG-2 Encoder >>> | \-03.0 Conexant CX23418 Single-Chip MPEG-2 >>> Encoder with Integrated Analog Video/Broadcast Audio Decoder >>> [...] >>> >>> >From the tree view above, we see the CX23418 is behind the bridge at >>> 00:14.4. >>> >>> # lspci -s 0:14.4 -vv -x >>> 00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge (prog-if >>> 01 [Subtractive decode]) >>> >>> ^^^^^^^^^^^^^^^^^^^^^^^ >>> [...] >>> 00: 02 10 84 43 07 01 a0 02 00 01 04 06 00 40 81 00 >>> ^^^^^^^^ >>> || >>> Subtractive Decode PCI-PCI ----++ >>> [...] >>> >>> Here we see in the first text line for the bridge, lspci has shown us >>> its a PCI-PCI bridge in subtractive decode. This could also be read off >>> of bytes 09x-0xb of the configuration space. The byte at 0x9 being 1 >>> indicate subtractive decode vs positive decode. >>> >>> >>> >>> Thanks in advance for your responses. >>> >>> Regards, >>> Andy >>> >>> >>> >>> >>> >>> _______________________________________________ >>> ivtv-devel mailing list >>> [email protected] >>> http://ivtvdriver.org/mailman/listinfo/ivtv-devel >>> >>> >> _______________________________________________ >> ivtv-devel mailing list >> [email protected] >> http://ivtvdriver.org/mailman/listinfo/ivtv-devel >> >> > > > _______________________________________________ > ivtv-devel mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-devel > _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
