On 01/08/2013 11:02 PM, Cédric Girard wrote:
Hi, Since a few weeks, I am unable to use my TerraTec Cinergy T PCIe dual card anymore. On the kernel and drivers side, everything seems to be working as expected but I get no signal from any channel. It used to work and I have done too many updates recently to be able to pinpoint to from which point it stopped to work. Plugging the same cable to my TV tuner I get perfect reception so no change in signal quality. I am running Arch Linux with linux 3.7.1 on an x86_64 architecture. Following are some logs. Kernel logs when loading cx23885 module: ### [93752.708088] cx23885 driver version 0.0.3 loaded [93752.708954] CORE cx23885[0]: subsystem: 153b:117e, board: TerraTec Cinergy T PCIe Dual [card=34,autodetected] [93752.847421] cx25840 12-0044: cx23885 A/V decoder found @ 0x88 (cx23885[0]) [93753.502291] cx25840 12-0044: loaded v4l-cx23885-avcore-01.fw firmware (16382 bytes) [93753.518236] cx23885_dvb_register() allocating 1 frontend(s) [93753.518242] cx23885[0]: cx23885 based dvb card [93753.533378] drxk: status = 0x639160d9 [93753.533383] drxk: detected a drx-3916k, spin A3, xtal 20.250 MHz [93753.606391] DRXK driver version 0.9.4300 [93753.630635] drxk: frontend initialized. [93753.667152] mt2063_attach: Attaching MT2063 [93753.667156] DVB: registering new adapter (cx23885[0]) [93753.667161] cx23885 0000:03:00.0: DVB: registering adapter 0 frontend 0 (DRXK DVB-T)... [93753.670728] cx23885_dvb_register() allocating 1 frontend(s) [93753.670732] cx23885[0]: cx23885 based dvb card [93753.686602] drxk: status = 0x639130d9 [93753.686605] drxk: detected a drx-3913k, spin A3, xtal 20.250 MHz [93753.759577] DRXK driver version 0.9.4300 [93753.783845] drxk: frontend initialized. [93753.783852] mt2063_attach: Attaching MT2063 [93753.783854] DVB: registering new adapter (cx23885[0]) [93753.783858] cx23885 0000:03:00.0: DVB: registering adapter 1 frontend 0 (DRXK DVB-C DVB-T)... [93753.784284] cx23885_dev_checkrevision() Hardware revision = 0xa5 [93753.784290] cx23885[0]/0: found at 0000:03:00.0, rev: 4, irq: 18, latency: 0, mmio: 0xfb800000 ### Kernel logs when scanning ### [93853.705675] mt2063: detected a mt2063 B3 ### "femon -H -a0" output: ### FE: DRXK DVB-T (DVBT) Problem retrieving frontend information: Resource temporarily unavailable status SCV | signal 49% | snr 0% | ber 2014507767 | unc 1 | ### Meaningful bits of an strace of the same command ### ioctl(3, FE_READ_STATUS, 0x7fff69172ef0) = 0 ioctl(3, FE_READ_BER, 0x7fff69173018) = -1 EAGAIN (Resource temporarily unavailable) ioctl(3, FE_READ_SIGNAL_STRENGTH, 0x7fff6917301c) = -1 EAGAIN (Resource temporarily unavailable) ioctl(3, FE_READ_SNR, 0x7fff6917301e) = -1 EAGAIN (Resource temporarily unavailable) ioctl(3, FE_READ_UNCORRECTED_BLOCKS, 0x7fff69173020) = -1 EAGAIN (Resource temporarily unavailable) ###
I could guess these errors are coming because you query statistics but device is sleeping and statistics cannot be offered. -EAGAIN == device is sleeping, -ENOTTY device does not support given statistic at all.
Could you ensure that? Use some app, like w_scan, tzap, czap, etc. to tune and recheck if it shows these or not. femon could not tune, it queries only statistics. You will need to leave tuning on and then use other terminal for femon.
w_scan give "no signal" result. dvbscan give "Unable to query frontend status"
hmm, that dvbscan results sounds crazy. I am not sure about these scanning apps as there is scan, dvbscan, scandvb. Maybe some of those, or even all, are just same app but renamed as "scan" is too general. My Fedora 17 has scandvb. I just tested against one DRX-K device and it worked fine.
Any hint to where I should look would be welcome!
Try to downgrade Kernels until you find working one. regards Antti -- http://palosaari.fi/ -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
