debugging my Tevii S660 usb 2.0 dvb-s2 device

[kc]

Hello all,

I have bought a new tevii s660 device in december 3 months later
(backorder) when i received my device i was having issues when loading the
driver from the tevii website.
First loading went ok but then i got hundreds of debug messages in dmesg.
Later this device really died so i sent it back for rma.

Now i have received a new device but still have the same issues.
I got the old drivers from Artem: Re: [vdr] System unresponsive and
picture breakup with VDR 1.7.10  and Tevii S660 (USB) (thanks for helping
out)

But still  i have system freezes.
and a channel scan freaks out my system and device.

Does someone have time/ideas how to make this device work and how can i
deliver the right info to make it happen.
I'm no developer so programming is a problem but i'm happy to try patches
if someone can help me out.

So what info would be needed beside a dmesg/uname -a and how can i get the
right information
e.g. lsusb -vvv

With kind regards

William van de Velde



--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

tevii s660 system slow/freeze

[kc]

Dear mailinglist/Tevii,

i have received a new tevii s660 yesterday.
I have tried to use the device with scan but then my system freezes/slows
down and i don't get any channels. Also when i create a channel list with
my nova 2 hd and check if that works with vdr, then i removed the drivers
from the nova card and plugged in the s660 and started vdr. But then still
no picture only system freeze/slow down. I get nothing in the logs so it
seems a driver issue.

i have tried the drivers from the tevii site and also tried the 2.6.34rc1
kernel from ubuntu. I also tried it on 3 different systems but to no
avail.

in dmesg i get:
[16735.496800] usbcore: deregistering interface driver dw2102
[16735.562114] dvb-usb: TeVii S660 USB successfully deinitialized and
disconnected.
[16737.219577] dvb-usb: found a 'TeVii S660 USB' in cold state, will try
to load a firmware
[16737.219593] usb 1-1: firmware: requesting dvb-usb-teviis660.fw
[16737.229441] dvb-usb: downloading firmware from file 'dvb-usb-teviis660.fw'
[16737.229453] dw2102: start downloading DW210X firmware
[16737.350052] dvb-usb: found a 'TeVii S660 USB' in warm state.
[16737.350171] dvb-usb: will pass the complete MPEG2 transport stream to
the software demuxer.
[16737.350414] DVB: registering new adapter (TeVii S660 USB)
[16747.590032] dvb-usb: MAC address: 00:18:bd:5c:55:bb
[16747.650033] Only Zarlink VP310/MT312/ZL10313 are supported chips.
[16748.074008] DS3000 chip version: 0.192 attached.
[16748.074015] dw2102: Attached ds3000+ds2020!
[16748.074017]
[16748.074189] DVB: registering adapter 0 frontend 0 (Montage Technology
DS3000/TS2020)...
[16748.076014] input: IR-receiver inside an USB DVB receiver as
/devices/pci:00/:00:1d.7/usb1/1-1/input/input11
[16748.076312] dvb-usb: schedule remote query interval to 150 msecs.
[16748.076327] dvb-usb: TeVii S660 USB successfully initialized and
connected.
[16748.076596] usbcore: registered new interface driver dw2102


and after that i only see:
[16748.224312] dw2102: query RC enter
[16748.224320] dw2102: query RC start
[16748.246317] dw2102: query RC end
[16748.396311] dw2102: query RC enter
[16748.396320] dw2102: query RC start
[16748.415313] dw2102: query RC end
[16748.561641] dw2102: query RC enter
[16748.561650] dw2102: query RC start
[16748.585317] dw2102: query RC end


over and over just filling the logs. i saw that it was from/for the remote
but it looks like debug messages.

I have tried 3 different kernels 2.6.32/3/4rc1 but they all have the same
issue with the driver from 15 march.

What can be wrong?
Any suggestions how i can troubleshoot this?

With kind regards
William van de Velde


new tevii S660 system slow/freeze no channels linux

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html