[linux-dvb] m920x tests

fago nuppla at zites.net
Tue Apr 17 17:52:43 CEST 2007


I've just tried the latest m920x driver and had some problems...
I'm running the latest code from http://linuxtv.org/hg/~mkrufky/m920x
Installation went fine. 

My dvb-t usb-stick was actually quite cheap and I don't know much about its
modell as I found not much information about it on the net. It's a SEG
DTR 61-USB. But lsusb said something from Uli m9206 so I tested it with
this driver. 

Then it tried to load the firmware dvb-usb-dposh-01.fw, so I downloaded
that. So far so fine.

That are the success messages when I plug the usb "stick" on:

[ 4985.973394] usbcore: registered new interface driver dvb_usb_m920x
[ 5088.679511] usb 3-6: USB disconnect, address 3
[ 5093.989570] usb 3-6: new high speed USB device using ehci_hcd and
address 4
[ 5094.131172] usb 3-6: configuration #1 chosen from 1 choice
[ 5094.131372] dvb-usb: found a 'Dposh DVB-T USB2.0' in cold state, will
try to load a firmware
[ 5094.170723] dvb-usb: downloading firmware from file
'dvb-usb-dposh-01.fw'
[ 5094.809012] dvb_usb_m920x: probe of 3-6:1.0 failed with error 64
[ 5095.004532] usb 3-6: USB disconnect, address 4
[ 5095.244169] usb 3-6: new high speed USB device using ehci_hcd and
address 5
[ 5095.385960] usb 3-6: configuration #1 chosen from 1 choice
[ 5095.386163] dvb-usb: found a 'Dposh DVB-T USB2.0' in warm state.
[ 5095.386200] dvb-usb: will pass the complete MPEG2 transport stream to
the software demuxer.
[ 5095.386258] DVB: registering new adapter (Dposh DVB-T USB2.0).
[ 5095.406482] DVB: registering frontend 0 (Zarlink MT352 DVB-T)...
[ 5095.426073] Quantek QT1010 successfully identified.
[ 5095.426081] dvb-usb: Dposh DVB-T USB2.0 successfully initialized and
connected.



But when I try to scan for channels, I get this:

scan Scanlist.txt > channels.conf
scanning Scanlist.txt
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 794000000 1 2 9 1 1 3 0
initial transponder 794000000 1 3 9 1 1 3 0
initial transponder 794000000 0 2 9 1 1 3 0
initial transponder 794000000 0 3 9 1 1 3 0
>>> tune to:
794000000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_AUTO:QAM_16:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE
__tune_to_transponder:1491: ERROR: FE_READ_STATUS failed: 121 Remote I/O
error
>>> tune to:
794000000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_AUTO:QAM_16:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE
__tune_to_transponder:1491: ERROR: FE_READ_STATUS failed: 121 Remote I/O
error
>>> tune to:
794000000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_AUTO:QAM_16:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_4:HIERARCHY_NONE
__tune_to_transponder:1491: ERROR: FE_RE
....

Scanning generates these errors messages on dmesg:

[ 7312.152821] qt1010 I2C write failed
[ 7314.138687] mt352_write() to reg 51 failed (err = -110)!
[ 7316.120432] mt352_write() to reg 5e failed (err = -110)!
[ 7318.110165] qt1010 I2C write failed
[ 7320.096031] mt352_write() to reg 51 failed (err = -110)!
[ 7322.085766] mt352_write() to reg 5e failed (err = -110)!
[ 7324.075501] mt352_read_register: readreg error (reg=0, ret==-110)
[ 7326.049382] mt352_read_register: readreg error (reg=0, ret==-110)
[ 7328.035119] qt1010 I2C write failed
[ 7330.012872] mt352_write() to reg 51 failed (err = -110)!
[ 7331.990746] mt352_write() to reg 5e failed (err = -110)!
[ 7333.984475] qt1010 I2C write failed
[ 7335.974211] mt352_write() to reg 51 failed (err = -110)!
[ 7337.964071] mt352_write() to reg 5e failed (err = -110)!
[ 7339.960049] mt352_read_register: readreg error (reg=0, ret==-110)
[ 7341.931557] mt352_read_register: readreg error (reg=0, ret==-110)
[ 7343.921416] qt1010 I2C write failed
...

And I can't find any channels, but I do if I scan with windows.

So I thought this might be a problem with the driver?
Or is it possible that I'm just using the wrong driver or firmware?

If you need any further input or a driver tester, I'd be happy to help
out.

regards,
fago




More information about the linux-dvb mailing list