On Tue, Aug 24, 2010 at 8:22 AM, Andy Walls <[email protected]> wrote: > On Tue, 2010-08-17 at 02:58 -0400, Keith Richie wrote: >> I am not subscribed, if possible, please CC me on replies. >> >> PCI card was sold as " Asus Falcon2 FM+NTSC Tv Tuner PCI 5188-4214". >> Most likely an OEM model from an HP media center. >> I have 2 of these cards. They _did_ work just fine previously in a >> different motherboard. The PSU on my MythTV backend bit the dust, and >> I decided to just to a complete rebuild. It's been a while since I >> built the original machine, and do not recall needing to do anything >> _special_ in regards to the Falcon2 cards. >> >> [ 227.936651] Linux video capture interface: v2.00 >> [ 227.941234] ivtv: Start initialization, version 1.4.2 >> [ 227.941274] ivtv0: Initializing card 0 >> [ 227.941276] ivtv0: Unknown card: vendor/device: [4444:0016] > ^^^^^^^^^^^ > This is the right ID for the CX23416 chip -------------| > > >> [ 227.941277] ivtv0: subsystem vendor/device: [1043:0666] > ^^^^^^^^^^ > Has the Falcon always had this ID? -----------------------------| > > Because the ivtv driver only knows about these Asus PCI IDs: > > #define IVTV_PCI_ID_ASUSTEK 0x1043 > > static const struct ivtv_card_pci_info ivtv_pci_asus_falcon2[] = { > { PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_ASUSTEK, 0x4b66 }, > { PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_ASUSTEK, 0x462e }, > { PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_ASUSTEK, 0x4b2e }, > { 0, 0, 0 } > }; > > > Perhaps the PSU failure zapped the CX23416 internal PCI info EEPROM on > the cards. That of course begs the question: what else has been zapped? > > Anyway, you can use the "cardtype=22" module option to the ivtv driver > to force the card type to an Asus Falcon2. '/sbin/modinfo ivtv' gives a > full list of card types. > > Regards, > Andy > >> [ 227.941278] ivtv0: cx23416 based >> [ 227.941279] ivtv0: Defaulting to Hauppauge WinTV PVR-150 card >> [ 227.941281] ivtv0: Please mail the vendor/device and subsystem >> vendor/device IDs and what kind of >> [ 227.941282] ivtv0: card you have to the ivtv-devel mailinglist >> (www.ivtvdriver.org) >> [ 227.941283] ivtv0: Prefix your subject line with [UNKNOWN IVTV CARD]. >> >> 03:02.0 Multimedia video controller: Internext Compression Inc iTVC16 >> (CX23416) MPEG-2 Encoder (rev 01) >> Subsystem: ASUSTeK Computer Inc. Device 0666 >> 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 (32000ns min, 2000ns max), Cache Line Size: 32 bytes >> Interrupt: pin A routed to IRQ 17 >> Region 0: Memory at f0000000 (32-bit, prefetchable) [size=64M] >> Capabilities: [44] Power Management version 2 >> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA >> PME(D0-,D1-,D2-,D3hot-,D3cold-) >> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- >> Kernel driver in use: ivtv >> Kernel modules: ivtv >> >> >> Kernel 2.6.32.19, fresh tip of v4l-dvb-ab433502e041, make - make >> install - make unload. modprobe ivtv. > > >
Not sure if this card has always had _that_ ID. Everything's been running for 7 days now, and I have not experienced any recording nor tuning errors. Here's the dmesg after rmmod and modprobe ivtv cardtype=22 [647820.495580] tuner-simple 4-0060: destroying instance [647820.495675] ivtv 0000:03:02.0: PCI INT A disabled [647820.495677] ivtv: Removed Yuan PG600, Diamond PVR-550 [647855.635882] ivtv: Start initialization, version 1.4.2 [647855.635933] ivtv0: Initializing card 0 [647855.635934] ivtv0: User specified ASUS Falcon2 card (detected cx23416 based chip) [647855.635971] ivtv 0000:03:02.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [647855.659769] cx25840 4-0044: cx25843-24 found @ 0x88 (ivtv i2c driver #0) [647855.669234] tuner 4-0043: chip found @ 0x86 (ivtv i2c driver #0) [647855.669267] tda9887 4-0043: creating new instance [647855.669269] tda9887 4-0043: tda988[5/6/7] found [647855.683643] All bytes are equal. It is not a TEA5767 [647855.683675] tuner 4-0060: chip found @ 0xc0 (ivtv i2c driver #0) [647855.692693] m52790 4-0048: chip found @ 0x90 (ivtv i2c driver #0) [647855.738339] tuner-simple 4-0060: creating new instance [647855.738341] tuner-simple 4-0060: type set to 43 (Philips NTSC MK3 (FM1236MK3 or FM1236/F)) [647855.740435] IRQ 17/ivtv0: IRQF_DISABLED is not guaranteed on shared IRQs [647855.740707] ivtv0: Registered device video1 for encoder MPG (4096 kB) [647855.740848] ivtv0: Registered device video33 for encoder YUV (2048 kB) [647855.741012] ivtv0: Registered device vbi1 for encoder VBI (1024 kB) [647855.741112] ivtv0: Registered device video25 for encoder PCM (320 kB) [647855.741206] ivtv0: Registered device radio1 for encoder radio [647855.741207] ivtv0: Initialized card: ASUS Falcon2 [647855.741298] ivtv: End initialization [647856.378559] ivtv 0000:03:02.0: firmware: requesting v4l-cx2341x-enc.fw [647856.484228] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes) [647856.682018] ivtv0: Encoder revision: 0x02060039 [647856.699080] cx25840 4-0044: firmware: requesting v4l-cx25840.fw A quick channel scan, and tuning in a few channels with MythTV, things work as before. I did a little more digging though. And will have to chalk this to a problem outside of the IVTV driver. I'm going to assume it's a motherboard issue. I put my spare Falcon2 in a different motherboard. This Falcon2 had a PC_ID of 0x4b66. I then shutdown the Myth Backend, pulled that Falcon2 and placed the card in the same test motherboard - PC_ID 0x4b66. Placed both Falcon2s in the test motherboard booting from the same kernel as the mythbackend, this also resulted in each Falcon2 having a PC_ID of 0x4b66. Must be something with the IRQ assignments of the Biostar G31-M7 TE. As it is sharing an IRQ. I'll poke around in the BIOS for IRQ routing, and/or swap that lowend Biostar with a P45 I have. Worse comes to worse, I'll just continue using a custom ivtv.conf in /etc/modprobe.d/ Strange that this motherboard would show a different PC_ID. _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
