* setting up a tevii s660
@ 2010-05-05 23:07 Tim Coote
2010-05-06 19:09 ` william
2010-05-09 18:46 ` Igor M. Liplianin
0 siblings, 2 replies; 12+ messages in thread
From: Tim Coote @ 2010-05-05 23:07 UTC (permalink / raw)
To: linux-media
Hullo
I've been struggling with this for a couple of days. I have checked
archives, but missed anything useful.
I've got a tevii s660 (dvbs2 via usb). It works with some limitations
on windows xp (I cannot get HD signals decoded, but think that's a
limitation of the software that comes on the CD).
I'm trying to get this working on Linux. I've tried VMs based on
fedora 12 and mythbuntu (VMWare Fusion on a MacBookPro, both based on
kernel 2.6.32), using the drivers from tevii's site (www.tevii.com/support.asp)
. these drivers are slightly modified versions of the v4l tip - but
don't appear to be modified where I've not yet managed to get the
drivers working :-(. Mythbuntu seems to be closest to working.
Goodness knows how tevii tested the code, but it doesn't seem to work
as far as I can see. My issues could just be down to using a VM.
I believe that I need to load up the modules ds3000 and dvb-usb-
dw2102, + add a rule to /etc/udev/rules.d and a script to /etc/udev/
scripts.
I think that I must be missing quite a lot of context, tho'. When I
look at the code in dw2102.c, which seems to support the s660, the bit
that downloads the firmware looks broken and if I add a default clause
to the switch that does the download, the s660's missed the download
process. This could be why when I do get anything out of the device
it looks like I'm just getting repeated bytes (the same value
repeated, different values at different times, sometimes nothing).
I'm finding it non-trivial working out the call sequences of the code
or devising repeatable tests.
Can anyone kick me off on getting this working? I'd like to at least
get to the point where scandvb can tune the device. It does look like
some folk have had success in the past, but probably with totally
different codebase (there are posts that refer to the teviis660
module, which I cannot find).
Any pointer gratefully accepted. I'll feed back any success if I can
be pointed at where to drop document it.
tia
Tim
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: setting up a tevii s660
2010-05-05 23:07 setting up a tevii s660 Tim Coote
@ 2010-05-06 19:09 ` william
2010-05-07 11:41 ` Tim Coote
2010-05-09 18:46 ` Igor M. Liplianin
1 sibling, 1 reply; 12+ messages in thread
From: william @ 2010-05-06 19:09 UTC (permalink / raw)
To: Tim Coote; +Cc: linux-media
Hello Tim,
i also have a tevii s660 which i cannot get to work properly.
i'm no programmer and nobody has given a reaction on my previous posts
(debugging my tevii...).
I get this in my log after getting the source from the linuxtv site with
the driver igor wrote:
[ 45.654362] dvb-usb: found a 'TeVii S660 USB' in cold state, will try
to load a firmware
[ 45.654379] usb 1-3: firmware: requesting dvb-usb-s630.fw
[ 45.717438] dvb-usb: downloading firmware from file 'dvb-usb-s630.fw'
[ 45.717450] dw2102: start downloading DW210X firmware
[ 45.824245] usb 1-3: USB disconnect, address 3
[ 45.930055] dvb-usb: found a 'TeVii S660 USB' in warm state.
[ 45.930167] dvb-usb: will pass the complete MPEG2 transport stream to
the software demuxer.
[ 45.930233] DVB: registering new adapter (TeVii S660 USB)
[ 56.182533] dvb-usb: MAC address: 00:00:00:00:00:00
[ 56.262532] mt312: R(126): 00
[ 56.262543] Only Zarlink VP310/MT312/ZL10313 are supported chips.
[ 56.607024] ds3000_attach
[ 56.642535] ds3000_readreg: read reg 0x00, value 0x00
[ 56.642542] Invalid probe, probably not a DS3000
[ 56.642816] dvb-usb: no frontend was attached by 'TeVii S660 USB'
[ 56.643037] input: IR-receiver inside an USB DVB receiver as
/devices/pci0000:00/0000:00:1d.7/usb1/1-3/input/input5
[ 56.643189] dvb-usb: schedule remote query interval to 150 msecs.
[ 56.643203] dvb-usb: TeVii S660 USB successfully initialized and
connected.
[ 56.643290] usbcore: registered new interface driver dw2102
[ 56.773230] dvb-usb: TeVii S660 USB successfully deinitialized and
disconnected.
[ 57.050043] usb 1-3: new high speed USB device using ehci_hcd and
address 5
in my previous post i got a message that an mt312 chip was found and now
it does not find anything.
so now i don't have a dvb device at all.
the firmware is from the drivers from tevii. I tried and the s630
firmware and later the s660 firmware renamed to s630 but none worked.
After installing the driver/changing the firmware, I shutdown the
computer removed the power from the tevii device and then replugged and
started my computer again.
======
modinfo dvb-usb-dw2102
filename:
/lib/modules/2.6.34-020634rc2-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb-dw2102.ko
license: GPL
version: 0.1
description: Driver for DVBWorld DVB-S 2101, 2102, DVB-S2 2104, DVB-C
3101 USB2.0, TeVii S600, S630, S650, S660 USB2.0, Prof 1100, 7500 USB2.0
devices
author: Igor M. Liplianin (c) liplianin@me.by
srcversion: FCBA4EFAEF1F6A88DC9F2DB
alias: usb:v3034p7500d*dc*dsc*dp*ic*isc*ip*
alias: usb:v9022pD660d*dc*dsc*dp*ic*isc*ip*
alias: usb:v3011pB012d*dc*dsc*dp*ic*isc*ip*
alias: usb:v9022pD630d*dc*dsc*dp*ic*isc*ip*
alias: usb:v04B4p3101d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0CCDp0064d*dc*dsc*dp*ic*isc*ip*
alias: usb:v9022pD650d*dc*dsc*dp*ic*isc*ip*
alias: usb:v04B4p2104d*dc*dsc*dp*ic*isc*ip*
alias: usb:v04B4p2101d*dc*dsc*dp*ic*isc*ip*
alias: usb:v04B4p2102d*dc*dsc*dp*ic*isc*ip*
depends: dvb-usb
vermagic: 2.6.34-020634rc2-generic SMP mod_unload modversions
parm: debug:set debugging level (1=info 2=xfer 4=rc(or-able)).
(int)
parm: keymap:set keymap 0=default 1=dvbworld 2=tevii 3=tbs
... (int)
parm: demod:demod to probe (1=cx24116 2=stv0903+stv6110
4=stv0903+stb6100(or-able)). (int)
parm: adapter_nr:DVB adapter numbers (array of short)
========
if you need help testing i would be glad to help.
The tevii drivers are working and also detect the mt312 chip.
This driver does not, but i'm not very pleased about the driver from
tevii because channel switch takes long and image quality is bad and my
system get's slow/freezes.
With kind regards
William van de Velde
On 05/06/2010 01:07 AM, Tim Coote wrote:
> Hullo
> I've been struggling with this for a couple of days. I have checked
> archives, but missed anything useful.
>
> I've got a tevii s660 (dvbs2 via usb). It works with some limitations
> on windows xp (I cannot get HD signals decoded, but think that's a
> limitation of the software that comes on the CD).
>
> I'm trying to get this working on Linux. I've tried VMs based on
> fedora 12 and mythbuntu (VMWare Fusion on a MacBookPro, both based on
> kernel 2.6.32), using the drivers from tevii's site
> (www.tevii.com/support.asp). these drivers are slightly modified
> versions of the v4l tip - but don't appear to be modified where I've
> not yet managed to get the drivers working :-(. Mythbuntu seems to be
> closest to working. Goodness knows how tevii tested the code, but it
> doesn't seem to work as far as I can see. My issues could just be
> down to using a VM.
>
> I believe that I need to load up the modules ds3000 and
> dvb-usb-dw2102, + add a rule to /etc/udev/rules.d and a script to
> /etc/udev/scripts.
>
> I think that I must be missing quite a lot of context, tho'. When I
> look at the code in dw2102.c, which seems to support the s660, the bit
> that downloads the firmware looks broken and if I add a default clause
> to the switch that does the download, the s660's missed the download
> process. This could be why when I do get anything out of the device
> it looks like I'm just getting repeated bytes (the same value
> repeated, different values at different times, sometimes nothing).
> I'm finding it non-trivial working out the call sequences of the code
> or devising repeatable tests.
>
> Can anyone kick me off on getting this working? I'd like to at least
> get to the point where scandvb can tune the device. It does look like
> some folk have had success in the past, but probably with totally
> different codebase (there are posts that refer to the teviis660
> module, which I cannot find).
>
> Any pointer gratefully accepted. I'll feed back any success if I can
> be pointed at where to drop document it.
>
> tia
>
> Tim
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: setting up a tevii s660
2010-05-06 19:09 ` william
@ 2010-05-07 11:41 ` Tim Coote
2010-05-07 11:46 ` Josu Lazkano
2010-05-07 12:31 ` william
0 siblings, 2 replies; 12+ messages in thread
From: Tim Coote @ 2010-05-07 11:41 UTC (permalink / raw)
To: william; +Cc: linux-media
William
did you load your modules with debug=1, or something else, somehow? I
thought that the code printing out ds3000_readreg required debug. or
have you got different source code from the tevii driver on www.tevii.com/Support.asp?
(unless I know what you're using, I cannot tell what's relevant.)
my log looks like this (VMWare fusion virtual hardware, MacBookPro
host, xubuntu 10.04, installed and updated, make and sudo make install
based on a .config that I understand works).
May 7 02:20:37 ubuntu kernel: [42761.520219] usb 1-1: new high speed
USB device using ehci_hcd and address 2
May 7 02:20:37 ubuntu kernel: [42761.708776] usb 1-1: configuration
#1 chosen from 1 choice
May 7 02:20:37 ubuntu kernel: [42762.229009] dvb-usb: found a 'TeVii
S660 USB' in cold state, will try to load a firmware
May 7 02:20:37 ubuntu kernel: [42762.229027] usb 1-1: firmware:
requesting dvb-usb-teviis660.fw
May 7 02:20:38 ubuntu kernel: [42762.307947] dvb-usb: downloading
firmware from file 'dvb-usb-teviis660.fw'
May 7 02:20:38 ubuntu kernel: [42762.307950] dw2102: start
downloading DW210X firmware
May 7 02:20:38 ubuntu kernel: [42762.508553] usb 1-1: USB disconnect,
address 2
May 7 02:20:38 ubuntu kernel: [42762.592094] dvb-usb: found a 'TeVii
S660 USB' in warm state.
May 7 02:20:38 ubuntu kernel: [42762.592253] dvb-usb: will pass the
complete MPEG2 transport stream to the software demuxer.
May 7 02:20:38 ubuntu kernel: [42762.592324] DVB: registering new
adapter (TeVii S660 USB)
May 7 02:20:42 ubuntu kernel: [42766.700222] dvb-usb: MAC address:
00:00:00:00:00:00
May 7 02:20:42 ubuntu kernel: [42766.778218] Only Zarlink VP310/MT312/
ZL10313 are supported chips.
May 7 02:20:42 ubuntu kernel: [42767.053874] input: IR-receiver
inside an USB DVB receiver as /devices/
pci0000:00/0000:00:11.0/0000:02:03.0/usb1/1-1/input/input5
May 7 02:20:42 ubuntu kernel: [42767.054053] dvb-usb: schedule remote
query interval to 150 msecs.
May 7 02:20:42 ubuntu kernel: [42767.054058] dvb-usb: TeVii S660 USB
successfully initialized and connected.
May 7 02:20:42 ubuntu kernel: [42767.054088] usbcore: registered new
interface driver dw2102
May 7 02:20:42 ubuntu kernel: [42767.054463] dvb-usb: TeVii S660 USB
successfully deinitialized and disconnected.
May 7 02:20:43 ubuntu kernel: [42767.340236] usb 1-1: new high speed
USB device using ehci_hcd and address 3
May 7 02:20:43 ubuntu kernel: [42767.824316] usb 1-1: config 1
interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 2
May 7 02:20:43 ubuntu kernel: [42767.828380] usb 1-1: configuration
#1 chosen from 1 choice
May 7 02:20:43 ubuntu kernel: [42768.068383] dvb-usb: found a 'TeVii
S660 USB' in cold state, will try to load a firmware
May 7 02:20:43 ubuntu kernel: [42768.068388] usb 1-1: firmware:
requesting dvb-usb-teviis660.fw
May 7 02:20:43 ubuntu kernel: [42768.087257] dvb-usb: downloading
firmware from file 'dvb-usb-teviis660.fw'
May 7 02:20:43 ubuntu kernel: [42768.087260] dw2102: start
downloading DW210X firmware
May 7 02:20:44 ubuntu kernel: [42768.360185] dvb-usb: found a 'TeVii
S660 USB' in warm state.
May 7 02:20:44 ubuntu kernel: [42768.361175] dvb-usb: will pass the
complete MPEG2 transport stream to the software demuxer.
May 7 02:20:44 ubuntu kernel: [42768.362197] DVB: registering new
adapter (TeVii S660 USB)
May 7 02:20:49 ubuntu kernel: [42773.580095] dvb-usb: MAC address:
70:70:70:70:70:70
May 7 02:20:49 ubuntu kernel: [42773.612787] Only Zarlink VP310/MT312/
ZL10313 are supported chips.
May 7 02:20:49 ubuntu kernel: [42773.875597] input: IR-receiver
inside an USB DVB receiver as /devices/
pci0000:00/0000:00:11.0/0000:02:03.0/usb1/1-1/input/input6
May 7 02:20:49 ubuntu kernel: [42773.875684] dvb-usb: schedule remote
query interval to 150 msecs.
May 7 02:20:49 ubuntu kernel: [42773.875687] dvb-usb: TeVii S660 USB
successfully initialized and connected.
May 7 02:20:49 ubuntu kernel: [42774.024247] dw2102: query RC enter
I'm not getting the 'probably not a ds3000' line, although that could
be a debugging level issue.
I see that you're using a different kernel and source file: here's my
modinfo for the module that I'm using:
filename: /lib/modules/2.6.32-22-generic/kernel/drivers/media/
dvb/dvb-usb/dvb-usb-dw2102.ko
license: GPL
version: 0.1
description: Driver for DVBWorld DVB-S 2101, 2102, DVB-S2 2104, DVB-
C 3101 USB2.0, TeVii S600, S630, S650, S660 USB2.0, Prof 1100, 7500
USB2.0 devices
author: Igor M. Liplianin (c) liplianin@me.by
srcversion: 5B4AEEBD8B92549304CF812
alias: usb:v3034p7500d*dc*dsc*dp*ic*isc*ip*
alias: usb:v9022pD660d*dc*dsc*dp*ic*isc*ip*
alias: usb:v3011pB012d*dc*dsc*dp*ic*isc*ip*
alias: usb:v9022pD630d*dc*dsc*dp*ic*isc*ip*
alias: usb:v04B4p3101d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0CCDp0064d*dc*dsc*dp*ic*isc*ip*
alias: usb:v9022pD650d*dc*dsc*dp*ic*isc*ip*
alias: usb:v04B4p2104d*dc*dsc*dp*ic*isc*ip*
alias: usb:v04B4p2101d*dc*dsc*dp*ic*isc*ip*
alias: usb:v04B4p2102d*dc*dsc*dp*ic*isc*ip*
depends: dvb-usb
vermagic: 2.6.32-22-generic SMP mod_unload modversions 586
parm: debug:set debugging level (1=info 2=xfer 4=rc(or-
able)). (int)
parm: keymap:set keymap 0=default 1=dvbworld 2=tevii
3=tbs ... (int)
parm: demod:demod to probe (1=cx24116 2=stv0903+stv6110
4=stv0903+stb6100(or-able)). (int)
parm: adapter_nr:DVB adapter numbers (array of short)
I'm not convinced that either of us is actually communicating with our
s660s. do you get a /dev/dvb/adapter0/frontend0? can you get any
output at all from the device? if so, with what?
There are too many variables here. I'd like to collect all of the
configurations of a known working system and work methodically from
there.
On 6 May 2010, at 20:09, william wrote:
> Hello Tim,
>
> i also have a tevii s660 which i cannot get to work properly.
>
> i'm no programmer and nobody has given a reaction on my previous
> posts (debugging my tevii...).
>
> I get this in my log after getting the source from the linuxtv site
> with the driver igor wrote:
>
>
> [ 45.654362] dvb-usb: found a 'TeVii S660 USB' in cold state, will
> try to load a firmware
> [ 45.654379] usb 1-3: firmware: requesting dvb-usb-s630.fw
> [ 45.717438] dvb-usb: downloading firmware from file 'dvb-usb-
> s630.fw'
> [ 45.717450] dw2102: start downloading DW210X firmware
> [ 45.824245] usb 1-3: USB disconnect, address 3
> [ 45.930055] dvb-usb: found a 'TeVii S660 USB' in warm state.
> [ 45.930167] dvb-usb: will pass the complete MPEG2 transport
> stream to the software demuxer.
> [ 45.930233] DVB: registering new adapter (TeVii S660 USB)
> [ 56.182533] dvb-usb: MAC address: 00:00:00:00:00:00
> [ 56.262532] mt312: R(126): 00
> [ 56.262543] Only Zarlink VP310/MT312/ZL10313 are supported chips.
> [ 56.607024] ds3000_attach
> [ 56.642535] ds3000_readreg: read reg 0x00, value 0x00
> [ 56.642542] Invalid probe, probably not a DS3000
> [ 56.642816] dvb-usb: no frontend was attached by 'TeVii S660 USB'
> [ 56.643037] input: IR-receiver inside an USB DVB receiver as /
> devices/pci0000:00/0000:00:1d.7/usb1/1-3/input/input5
> [ 56.643189] dvb-usb: schedule remote query interval to 150 msecs.
> [ 56.643203] dvb-usb: TeVii S660 USB successfully initialized and
> connected.
> [ 56.643290] usbcore: registered new interface driver dw2102
> [ 56.773230] dvb-usb: TeVii S660 USB successfully deinitialized
> and disconnected.
> [ 57.050043] usb 1-3: new high speed USB device using ehci_hcd and
> address 5
>
> in my previous post i got a message that an mt312 chip was found and
> now it does not find anything.
> so now i don't have a dvb device at all.
>
> the firmware is from the drivers from tevii. I tried and the s630
> firmware and later the s660 firmware renamed to s630 but none worked.
>
> After installing the driver/changing the firmware, I shutdown the
> computer removed the power from the tevii device and then replugged
> and started my computer again.
>
> ======
>
> modinfo dvb-usb-dw2102
> filename: /lib/modules/2.6.34-020634rc2-generic/kernel/drivers/
> media/dvb/dvb-usb/dvb-usb-dw2102.ko
> license: GPL
> version: 0.1
> description: Driver for DVBWorld DVB-S 2101, 2102, DVB-S2 2104,
> DVB-C 3101 USB2.0, TeVii S600, S630, S650, S660 USB2.0, Prof 1100,
> 7500 USB2.0 devices
> author: Igor M. Liplianin (c) liplianin@me.by
> srcversion: FCBA4EFAEF1F6A88DC9F2DB
> alias: usb:v3034p7500d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v9022pD660d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v3011pB012d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v9022pD630d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v04B4p3101d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v0CCDp0064d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v9022pD650d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v04B4p2104d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v04B4p2101d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v04B4p2102d*dc*dsc*dp*ic*isc*ip*
> depends: dvb-usb
> vermagic: 2.6.34-020634rc2-generic SMP mod_unload modversions
> parm: debug:set debugging level (1=info 2=xfer 4=rc(or-
> able)). (int)
> parm: keymap:set keymap 0=default 1=dvbworld 2=tevii
> 3=tbs ... (int)
> parm: demod:demod to probe (1=cx24116 2=stv0903+stv6110
> 4=stv0903+stb6100(or-able)). (int)
> parm: adapter_nr:DVB adapter numbers (array of short)
> ========
>
> if you need help testing i would be glad to help.
>
> The tevii drivers are working and also detect the mt312 chip.
> This driver does not, but i'm not very pleased about the driver from
> tevii because channel switch takes long and image quality is bad and
> my system get's slow/freezes.
>
> With kind regards
>
> William van de Velde
>
> On 05/06/2010 01:07 AM, Tim Coote wrote:
>> Hullo
>> I've been struggling with this for a couple of days. I have checked
>> archives, but missed anything useful.
>>
>> I've got a tevii s660 (dvbs2 via usb). It works with some
>> limitations on windows xp (I cannot get HD signals decoded, but
>> think that's a limitation of the software that comes on the CD).
>>
>> I'm trying to get this working on Linux. I've tried VMs based on
>> fedora 12 and mythbuntu (VMWare Fusion on a MacBookPro, both based
>> on kernel 2.6.32), using the drivers from tevii's site (www.tevii.com/support.asp)
>> . these drivers are slightly modified versions of the v4l tip - but
>> don't appear to be modified where I've not yet managed to get the
>> drivers working :-(. Mythbuntu seems to be closest to working.
>> Goodness knows how tevii tested the code, but it doesn't seem to
>> work as far as I can see. My issues could just be down to using a
>> VM.
>>
>> I believe that I need to load up the modules ds3000 and dvb-usb-
>> dw2102, + add a rule to /etc/udev/rules.d and a script to /etc/udev/
>> scripts.
>>
>> I think that I must be missing quite a lot of context, tho'. When I
>> look at the code in dw2102.c, which seems to support the s660, the
>> bit that downloads the firmware looks broken and if I add a default
>> clause to the switch that does the download, the s660's missed the
>> download process. This could be why when I do get anything out of
>> the device it looks like I'm just getting repeated bytes (the same
>> value repeated, different values at different times, sometimes
>> nothing). I'm finding it non-trivial working out the call
>> sequences of the code or devising repeatable tests.
>>
>> Can anyone kick me off on getting this working? I'd like to at
>> least get to the point where scandvb can tune the device. It does
>> look like some folk have had success in the past, but probably with
>> totally different codebase (there are posts that refer to the
>> teviis660 module, which I cannot find).
>>
>> Any pointer gratefully accepted. I'll feed back any success if I
>> can be pointed at where to drop document it.
>>
>> tia
>>
>> Tim
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-
>> media" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: setting up a tevii s660
2010-05-07 11:41 ` Tim Coote
@ 2010-05-07 11:46 ` Josu Lazkano
2010-05-07 12:31 ` william
1 sibling, 0 replies; 12+ messages in thread
From: Josu Lazkano @ 2010-05-07 11:46 UTC (permalink / raw)
To: Tim Coote; +Cc: william, linux-media
Hello, I don't have this card but you can try this:
http://www.linuxtv.org/wiki/index.php/TeVii_S470#Older_kernels
Is a script for Tevii S470, change the firmware path.
Good luck!
2010/5/7 Tim Coote <tim+vger.kernel.org@coote.org>:
> William
> did you load your modules with debug=1, or something else, somehow? I
> thought that the code printing out ds3000_readreg required debug. or have
> you got different source code from the tevii driver on
> www.tevii.com/Support.asp? (unless I know what you're using, I cannot tell
> what's relevant.)
>
> my log looks like this (VMWare fusion virtual hardware, MacBookPro host,
> xubuntu 10.04, installed and updated, make and sudo make install based on a
> .config that I understand works).
>
> May 7 02:20:37 ubuntu kernel: [42761.520219] usb 1-1: new high speed USB
> device using ehci_hcd and address 2
> May 7 02:20:37 ubuntu kernel: [42761.708776] usb 1-1: configuration #1
> chosen from 1 choice
> May 7 02:20:37 ubuntu kernel: [42762.229009] dvb-usb: found a 'TeVii S660
> USB' in cold state, will try to load a firmware
> May 7 02:20:37 ubuntu kernel: [42762.229027] usb 1-1: firmware: requesting
> dvb-usb-teviis660.fw
> May 7 02:20:38 ubuntu kernel: [42762.307947] dvb-usb: downloading firmware
> from file 'dvb-usb-teviis660.fw'
> May 7 02:20:38 ubuntu kernel: [42762.307950] dw2102: start downloading
> DW210X firmware
> May 7 02:20:38 ubuntu kernel: [42762.508553] usb 1-1: USB disconnect,
> address 2
> May 7 02:20:38 ubuntu kernel: [42762.592094] dvb-usb: found a 'TeVii S660
> USB' in warm state.
> May 7 02:20:38 ubuntu kernel: [42762.592253] dvb-usb: will pass the
> complete MPEG2 transport stream to the software demuxer.
> May 7 02:20:38 ubuntu kernel: [42762.592324] DVB: registering new adapter
> (TeVii S660 USB)
> May 7 02:20:42 ubuntu kernel: [42766.700222] dvb-usb: MAC address:
> 00:00:00:00:00:00
> May 7 02:20:42 ubuntu kernel: [42766.778218] Only Zarlink
> VP310/MT312/ZL10313 are supported chips.
> May 7 02:20:42 ubuntu kernel: [42767.053874] input: IR-receiver inside an
> USB DVB receiver as
> /devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb1/1-1/input/input5
> May 7 02:20:42 ubuntu kernel: [42767.054053] dvb-usb: schedule remote query
> interval to 150 msecs.
> May 7 02:20:42 ubuntu kernel: [42767.054058] dvb-usb: TeVii S660 USB
> successfully initialized and connected.
> May 7 02:20:42 ubuntu kernel: [42767.054088] usbcore: registered new
> interface driver dw2102
> May 7 02:20:42 ubuntu kernel: [42767.054463] dvb-usb: TeVii S660 USB
> successfully deinitialized and disconnected.
> May 7 02:20:43 ubuntu kernel: [42767.340236] usb 1-1: new high speed USB
> device using ehci_hcd and address 3
> May 7 02:20:43 ubuntu kernel: [42767.824316] usb 1-1: config 1 interface 0
> altsetting 0 bulk endpoint 0x81 has invalid maxpacket 2
> May 7 02:20:43 ubuntu kernel: [42767.828380] usb 1-1: configuration #1
> chosen from 1 choice
> May 7 02:20:43 ubuntu kernel: [42768.068383] dvb-usb: found a 'TeVii S660
> USB' in cold state, will try to load a firmware
> May 7 02:20:43 ubuntu kernel: [42768.068388] usb 1-1: firmware: requesting
> dvb-usb-teviis660.fw
> May 7 02:20:43 ubuntu kernel: [42768.087257] dvb-usb: downloading firmware
> from file 'dvb-usb-teviis660.fw'
> May 7 02:20:43 ubuntu kernel: [42768.087260] dw2102: start downloading
> DW210X firmware
> May 7 02:20:44 ubuntu kernel: [42768.360185] dvb-usb: found a 'TeVii S660
> USB' in warm state.
> May 7 02:20:44 ubuntu kernel: [42768.361175] dvb-usb: will pass the
> complete MPEG2 transport stream to the software demuxer.
> May 7 02:20:44 ubuntu kernel: [42768.362197] DVB: registering new adapter
> (TeVii S660 USB)
> May 7 02:20:49 ubuntu kernel: [42773.580095] dvb-usb: MAC address:
> 70:70:70:70:70:70
> May 7 02:20:49 ubuntu kernel: [42773.612787] Only Zarlink
> VP310/MT312/ZL10313 are supported chips.
> May 7 02:20:49 ubuntu kernel: [42773.875597] input: IR-receiver inside an
> USB DVB receiver as
> /devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb1/1-1/input/input6
> May 7 02:20:49 ubuntu kernel: [42773.875684] dvb-usb: schedule remote query
> interval to 150 msecs.
> May 7 02:20:49 ubuntu kernel: [42773.875687] dvb-usb: TeVii S660 USB
> successfully initialized and connected.
> May 7 02:20:49 ubuntu kernel: [42774.024247] dw2102: query RC enter
>
> I'm not getting the 'probably not a ds3000' line, although that could be a
> debugging level issue.
>
> I see that you're using a different kernel and source file: here's my
> modinfo for the module that I'm using:
>
> filename:
> /lib/modules/2.6.32-22-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb-dw2102.ko
> license: GPL
> version: 0.1
> description: Driver for DVBWorld DVB-S 2101, 2102, DVB-S2 2104, DVB-C
> 3101 USB2.0, TeVii S600, S630, S650, S660 USB2.0, Prof 1100, 7500 USB2.0
> devices
> author: Igor M. Liplianin (c) liplianin@me.by
> srcversion: 5B4AEEBD8B92549304CF812
> alias: usb:v3034p7500d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v9022pD660d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v3011pB012d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v9022pD630d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v04B4p3101d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v0CCDp0064d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v9022pD650d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v04B4p2104d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v04B4p2101d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v04B4p2102d*dc*dsc*dp*ic*isc*ip*
> depends: dvb-usb
> vermagic: 2.6.32-22-generic SMP mod_unload modversions 586
> parm: debug:set debugging level (1=info 2=xfer 4=rc(or-able)).
> (int)
> parm: keymap:set keymap 0=default 1=dvbworld 2=tevii 3=tbs ...
> (int)
> parm: demod:demod to probe (1=cx24116 2=stv0903+stv6110
> 4=stv0903+stb6100(or-able)). (int)
> parm: adapter_nr:DVB adapter numbers (array of short)
>
>
> I'm not convinced that either of us is actually communicating with our
> s660s. do you get a /dev/dvb/adapter0/frontend0? can you get any output at
> all from the device? if so, with what?
>
> There are too many variables here. I'd like to collect all of the
> configurations of a known working system and work methodically from there.
> On 6 May 2010, at 20:09, william wrote:
>
>> Hello Tim,
>>
>> i also have a tevii s660 which i cannot get to work properly.
>>
>> i'm no programmer and nobody has given a reaction on my previous posts
>> (debugging my tevii...).
>>
>> I get this in my log after getting the source from the linuxtv site with
>> the driver igor wrote:
>>
>>
>> [ 45.654362] dvb-usb: found a 'TeVii S660 USB' in cold state, will try
>> to load a firmware
>> [ 45.654379] usb 1-3: firmware: requesting dvb-usb-s630.fw
>> [ 45.717438] dvb-usb: downloading firmware from file 'dvb-usb-s630.fw'
>> [ 45.717450] dw2102: start downloading DW210X firmware
>> [ 45.824245] usb 1-3: USB disconnect, address 3
>> [ 45.930055] dvb-usb: found a 'TeVii S660 USB' in warm state.
>> [ 45.930167] dvb-usb: will pass the complete MPEG2 transport stream to
>> the software demuxer.
>> [ 45.930233] DVB: registering new adapter (TeVii S660 USB)
>> [ 56.182533] dvb-usb: MAC address: 00:00:00:00:00:00
>> [ 56.262532] mt312: R(126): 00
>> [ 56.262543] Only Zarlink VP310/MT312/ZL10313 are supported chips.
>> [ 56.607024] ds3000_attach
>> [ 56.642535] ds3000_readreg: read reg 0x00, value 0x00
>> [ 56.642542] Invalid probe, probably not a DS3000
>> [ 56.642816] dvb-usb: no frontend was attached by 'TeVii S660 USB'
>> [ 56.643037] input: IR-receiver inside an USB DVB receiver as
>> /devices/pci0000:00/0000:00:1d.7/usb1/1-3/input/input5
>> [ 56.643189] dvb-usb: schedule remote query interval to 150 msecs.
>> [ 56.643203] dvb-usb: TeVii S660 USB successfully initialized and
>> connected.
>> [ 56.643290] usbcore: registered new interface driver dw2102
>> [ 56.773230] dvb-usb: TeVii S660 USB successfully deinitialized and
>> disconnected.
>> [ 57.050043] usb 1-3: new high speed USB device using ehci_hcd and
>> address 5
>>
>> in my previous post i got a message that an mt312 chip was found and now
>> it does not find anything.
>> so now i don't have a dvb device at all.
>>
>> the firmware is from the drivers from tevii. I tried and the s630 firmware
>> and later the s660 firmware renamed to s630 but none worked.
>>
>> After installing the driver/changing the firmware, I shutdown the computer
>> removed the power from the tevii device and then replugged and started my
>> computer again.
>>
>> ======
>>
>> modinfo dvb-usb-dw2102
>> filename:
>> /lib/modules/2.6.34-020634rc2-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb-dw2102.ko
>> license: GPL
>> version: 0.1
>> description: Driver for DVBWorld DVB-S 2101, 2102, DVB-S2 2104, DVB-C
>> 3101 USB2.0, TeVii S600, S630, S650, S660 USB2.0, Prof 1100, 7500 USB2.0
>> devices
>> author: Igor M. Liplianin (c) liplianin@me.by
>> srcversion: FCBA4EFAEF1F6A88DC9F2DB
>> alias: usb:v3034p7500d*dc*dsc*dp*ic*isc*ip*
>> alias: usb:v9022pD660d*dc*dsc*dp*ic*isc*ip*
>> alias: usb:v3011pB012d*dc*dsc*dp*ic*isc*ip*
>> alias: usb:v9022pD630d*dc*dsc*dp*ic*isc*ip*
>> alias: usb:v04B4p3101d*dc*dsc*dp*ic*isc*ip*
>> alias: usb:v0CCDp0064d*dc*dsc*dp*ic*isc*ip*
>> alias: usb:v9022pD650d*dc*dsc*dp*ic*isc*ip*
>> alias: usb:v04B4p2104d*dc*dsc*dp*ic*isc*ip*
>> alias: usb:v04B4p2101d*dc*dsc*dp*ic*isc*ip*
>> alias: usb:v04B4p2102d*dc*dsc*dp*ic*isc*ip*
>> depends: dvb-usb
>> vermagic: 2.6.34-020634rc2-generic SMP mod_unload modversions
>> parm: debug:set debugging level (1=info 2=xfer 4=rc(or-able)).
>> (int)
>> parm: keymap:set keymap 0=default 1=dvbworld 2=tevii 3=tbs ...
>> (int)
>> parm: demod:demod to probe (1=cx24116 2=stv0903+stv6110
>> 4=stv0903+stb6100(or-able)). (int)
>> parm: adapter_nr:DVB adapter numbers (array of short)
>> ========
>>
>> if you need help testing i would be glad to help.
>>
>> The tevii drivers are working and also detect the mt312 chip.
>> This driver does not, but i'm not very pleased about the driver from tevii
>> because channel switch takes long and image quality is bad and my system
>> get's slow/freezes.
>>
>> With kind regards
>>
>> William van de Velde
>>
>> On 05/06/2010 01:07 AM, Tim Coote wrote:
>>>
>>> Hullo
>>> I've been struggling with this for a couple of days. I have checked
>>> archives, but missed anything useful.
>>>
>>> I've got a tevii s660 (dvbs2 via usb). It works with some limitations on
>>> windows xp (I cannot get HD signals decoded, but think that's a limitation
>>> of the software that comes on the CD).
>>>
>>> I'm trying to get this working on Linux. I've tried VMs based on fedora
>>> 12 and mythbuntu (VMWare Fusion on a MacBookPro, both based on kernel
>>> 2.6.32), using the drivers from tevii's site (www.tevii.com/support.asp).
>>> these drivers are slightly modified versions of the v4l tip - but don't
>>> appear to be modified where I've not yet managed to get the drivers working
>>> :-(. Mythbuntu seems to be closest to working. Goodness knows how tevii
>>> tested the code, but it doesn't seem to work as far as I can see. My issues
>>> could just be down to using a VM.
>>>
>>> I believe that I need to load up the modules ds3000 and dvb-usb-dw2102, +
>>> add a rule to /etc/udev/rules.d and a script to /etc/udev/scripts.
>>>
>>> I think that I must be missing quite a lot of context, tho'. When I look
>>> at the code in dw2102.c, which seems to support the s660, the bit that
>>> downloads the firmware looks broken and if I add a default clause to the
>>> switch that does the download, the s660's missed the download process. This
>>> could be why when I do get anything out of the device it looks like I'm just
>>> getting repeated bytes (the same value repeated, different values at
>>> different times, sometimes nothing). I'm finding it non-trivial working out
>>> the call sequences of the code or devising repeatable tests.
>>>
>>> Can anyone kick me off on getting this working? I'd like to at least get
>>> to the point where scandvb can tune the device. It does look like some folk
>>> have had success in the past, but probably with totally different codebase
>>> (there are posts that refer to the teviis660 module, which I cannot find).
>>>
>>> Any pointer gratefully accepted. I'll feed back any success if I can be
>>> pointed at where to drop document it.
>>>
>>> tia
>>>
>>> Tim
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-media" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Josu Lazkano
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: setting up a tevii s660
2010-05-07 11:41 ` Tim Coote
2010-05-07 11:46 ` Josu Lazkano
@ 2010-05-07 12:31 ` william
2010-05-07 14:33 ` Tim Coote
1 sibling, 1 reply; 12+ messages in thread
From: william @ 2010-05-07 12:31 UTC (permalink / raw)
To: Tim Coote; +Cc: linux-media
Hello Tim,
On 05/07/2010 01:41 PM, Tim Coote wrote:
> William
> did you load your modules with debug=1, or something else, somehow? I
> thought that the code printing out ds3000_readreg required debug. or
> have you got different source code from the tevii driver on
> www.tevii.com/Support.asp? (unless I know what you're using, I cannot
> tell what's relevant.)
i tried this so probably yes
/etc/modprobe.d/test.conf
##
options mt312 debug=1
options ds3000 debug=1
options dvb-usb-dw2102 debug=1
options dvb-usb disable_rc_polling=1
options dvb-usb-dw2102 keymap=2 demod=2
##
The tevii device should be supported by the linuxtv drivers:
############
hg clone http://linuxtv.org/hg/v4l-dvb
cd v4l-dvb
make menuconfig disable/enable what you need
make&& make install
poweroff
remove power/usb cables
replug the power to tevii device
then connect the usb
then poweron pc
Then i get this in my log:
modprobe dvb-usb-dw2102
[ 217.546580] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
[ 217.546595] usb 1-3: firmware: requesting dvb-usb-s630.fw
[ 217.630018] dvb-usb: downloading firmware from file 'dvb-usb-s630.fw'
[ 217.630030] dw2102: start downloading DW210X firmware
[ 217.748783] usb 1-3: USB disconnect, address 3
[ 217.850050] dvb-usb: found a 'TeVii S660 USB' in warm state.
[ 217.850161] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 217.850236] DVB: registering new adapter (TeVii S660 USB)
[ 228.090038] dvb-usb: MAC address: 00:00:00:00:00:00
[ 228.162540] mt312: R(126): 00
[ 228.162550] Only Zarlink VP310/MT312/ZL10313 are supported chips.
[ 228.507136] ds3000_attach
[ 228.542534] ds3000_readreg: read reg 0x00, value 0x00
[ 228.542541] Invalid probe, probably not a DS3000
[ 228.542808] dvb-usb: no frontend was attached by 'TeVii S660 USB'
[ 228.542861] dvb-usb: TeVii S660 USB successfully initialized and connected.
[ 228.543000] usbcore: registered new interface driver dw2102
[ 228.543454] dvb-usb: TeVii S660 USB successfully deinitialized and disconnected.
[ 228.820045] usb 1-3: new high speed USB device using ehci_hcd and address 5
########
using the tevii drivers i get this:
doing the same make ; make install ; poweroff ....
modprobe dvb-usb-dw2102
[ 80.354236] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
[ 80.354252] usb 1-3: firmware: requesting dvb-usb-teviis660.fw
[ 80.418598] dvb-usb: downloading firmware from file 'dvb-usb-teviis660.fw'
[ 80.418609] dw2102: start downloading DW210X firmware
[ 80.436136] usb 1-3: USB disconnect, address 3
[ 80.545656] dvb-usb: found a 'TeVii S660 USB' in warm state.
[ 80.545780] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 80.545840] DVB: registering new adapter (TeVii S660 USB)
[ 90.810041] dvb-usb: MAC address: 00:00:00:00:00:00
[ 90.921279] mt312: R(126): 00
[ 90.921289] Only Zarlink VP310/MT312/ZL10313 are supported chips.
[ 91.243014] ds3000_attach
[ 91.283778] ds3000_readreg: read reg 0x00, value 0x00
[ 91.283785] Invalid probe, probably not a DS3000
[ 91.284052] dvb-usb: no frontend was attached by 'TeVii S660 USB'
[ 91.284105] dvb-usb: TeVii S660 USB successfully initialized and connected.
[ 91.284209] usbcore: registered new interface driver dw2102
[ 91.284744] dvb-usb: TeVii S660 USB successfully deinitialized and disconnected.
[ 91.560036] usb 1-3: new high speed USB device using ehci_hcd and address 5
[ 91.710433] usb 1-3: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 2
[ 91.712260] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware
[ 91.712275] usb 1-3: firmware: requesting dvb-usb-teviis660.fw
[ 91.722989] dvb-usb: downloading firmware from file 'dvb-usb-teviis660.fw'
[ 91.723001] dw2102: start downloading DW210X firmware
[ 91.840045] dvb-usb: found a 'TeVii S660 USB' in warm state.
[ 91.840180] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 91.840339] DVB: registering new adapter (TeVii S660 USB)
[ 102.080030] dvb-usb: MAC address: 00:18:bd:5c:54:7f
[ 102.120028] mt312: R(126): ff
[ 102.120038] Only Zarlink VP310/MT312/ZL10313 are supported chips.
[ 102.390448] ds3000_attach
[ 102.430027] ds3000_readreg: read reg 0x00, value 0xe0
[ 102.470026] ds3000_readreg: read reg 0x01, value 0xc0
[ 102.510026] ds3000_readreg: read reg 0x02, value 0x00
[ 102.510033] DS3000 chip version: 0.192 attached.
[ 102.510039] dw2102: Attached ds3000+ds2020!
[ 102.510041]
[ 102.510274] DVB: registering adapter 1 frontend 0 (Montage Technology DS3000/TS2020)...
[ 102.510645] dvb-usb: TeVii S660 USB successfully initialized and connected.
#########
now i have:
root@backend:~# ls -al /dev/dvb/adapter1/
total 0
drwxr-xr-x 2 root root 120 2010-05-07 14:23 .
drwxr-xr-x 4 root root 80 2010-05-07 14:23 ..
crw-rw---- 1 root video 212, 4 2010-05-07 14:23 demux0
crw-rw---- 1 root video 212, 5 2010-05-07 14:23 dvr0
crw-rw---- 1 root video 212, 7 2010-05-07 14:23 frontend0
crw-rw---- 1 root video 212, 6 2010-05-07 14:23 net0
###
Now i can also make use off the device except that my system gets slow
and channel zapping takes ages.
i disabled the debug message for the remote with the option
disable_rc_polling for dvb-usb.
only then you cannot use the remote :)
With kind regards
William van de Velde
>
> my log looks like this (VMWare fusion virtual hardware, MacBookPro
> host, xubuntu 10.04, installed and updated, make and sudo make install
> based on a .config that I understand works).
>
> May 7 02:20:37 ubuntu kernel: [42761.520219] usb 1-1: new high speed
> USB device using ehci_hcd and address 2
> May 7 02:20:37 ubuntu kernel: [42761.708776] usb 1-1: configuration
> #1 chosen from 1 choice
> May 7 02:20:37 ubuntu kernel: [42762.229009] dvb-usb: found a 'TeVii
> S660 USB' in cold state, will try to load a firmware
> May 7 02:20:37 ubuntu kernel: [42762.229027] usb 1-1: firmware:
> requesting dvb-usb-teviis660.fw
> May 7 02:20:38 ubuntu kernel: [42762.307947] dvb-usb: downloading
> firmware from file 'dvb-usb-teviis660.fw'
> May 7 02:20:38 ubuntu kernel: [42762.307950] dw2102: start
> downloading DW210X firmware
> May 7 02:20:38 ubuntu kernel: [42762.508553] usb 1-1: USB disconnect,
> address 2
> May 7 02:20:38 ubuntu kernel: [42762.592094] dvb-usb: found a 'TeVii
> S660 USB' in warm state.
> May 7 02:20:38 ubuntu kernel: [42762.592253] dvb-usb: will pass the
> complete MPEG2 transport stream to the software demuxer.
> May 7 02:20:38 ubuntu kernel: [42762.592324] DVB: registering new
> adapter (TeVii S660 USB)
> May 7 02:20:42 ubuntu kernel: [42766.700222] dvb-usb: MAC address:
> 00:00:00:00:00:00
> May 7 02:20:42 ubuntu kernel: [42766.778218] Only Zarlink
> VP310/MT312/ZL10313 are supported chips.
> May 7 02:20:42 ubuntu kernel: [42767.053874] input: IR-receiver
> inside an USB DVB receiver as
> /devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb1/1-1/input/input5
> May 7 02:20:42 ubuntu kernel: [42767.054053] dvb-usb: schedule remote
> query interval to 150 msecs.
> May 7 02:20:42 ubuntu kernel: [42767.054058] dvb-usb: TeVii S660 USB
> successfully initialized and connected.
> May 7 02:20:42 ubuntu kernel: [42767.054088] usbcore: registered new
> interface driver dw2102
> May 7 02:20:42 ubuntu kernel: [42767.054463] dvb-usb: TeVii S660 USB
> successfully deinitialized and disconnected.
> May 7 02:20:43 ubuntu kernel: [42767.340236] usb 1-1: new high speed
> USB device using ehci_hcd and address 3
> May 7 02:20:43 ubuntu kernel: [42767.824316] usb 1-1: config 1
> interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 2
> May 7 02:20:43 ubuntu kernel: [42767.828380] usb 1-1: configuration
> #1 chosen from 1 choice
> May 7 02:20:43 ubuntu kernel: [42768.068383] dvb-usb: found a 'TeVii
> S660 USB' in cold state, will try to load a firmware
> May 7 02:20:43 ubuntu kernel: [42768.068388] usb 1-1: firmware:
> requesting dvb-usb-teviis660.fw
> May 7 02:20:43 ubuntu kernel: [42768.087257] dvb-usb: downloading
> firmware from file 'dvb-usb-teviis660.fw'
> May 7 02:20:43 ubuntu kernel: [42768.087260] dw2102: start
> downloading DW210X firmware
> May 7 02:20:44 ubuntu kernel: [42768.360185] dvb-usb: found a 'TeVii
> S660 USB' in warm state.
> May 7 02:20:44 ubuntu kernel: [42768.361175] dvb-usb: will pass the
> complete MPEG2 transport stream to the software demuxer.
> May 7 02:20:44 ubuntu kernel: [42768.362197] DVB: registering new
> adapter (TeVii S660 USB)
> May 7 02:20:49 ubuntu kernel: [42773.580095] dvb-usb: MAC address:
> 70:70:70:70:70:70
> May 7 02:20:49 ubuntu kernel: [42773.612787] Only Zarlink
> VP310/MT312/ZL10313 are supported chips.
> May 7 02:20:49 ubuntu kernel: [42773.875597] input: IR-receiver
> inside an USB DVB receiver as
> /devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb1/1-1/input/input6
> May 7 02:20:49 ubuntu kernel: [42773.875684] dvb-usb: schedule remote
> query interval to 150 msecs.
> May 7 02:20:49 ubuntu kernel: [42773.875687] dvb-usb: TeVii S660 USB
> successfully initialized and connected.
> May 7 02:20:49 ubuntu kernel: [42774.024247] dw2102: query RC enter
>
> I'm not getting the 'probably not a ds3000' line, although that could
> be a debugging level issue.
>
> I see that you're using a different kernel and source file: here's my
> modinfo for the module that I'm using:
>
> filename:
> /lib/modules/2.6.32-22-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb-dw2102.ko
>
> license: GPL
> version: 0.1
> description: Driver for DVBWorld DVB-S 2101, 2102, DVB-S2 2104,
> DVB-C 3101 USB2.0, TeVii S600, S630, S650, S660 USB2.0, Prof 1100,
> 7500 USB2.0 devices
> author: Igor M. Liplianin (c) liplianin@me.by
> srcversion: 5B4AEEBD8B92549304CF812
> alias: usb:v3034p7500d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v9022pD660d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v3011pB012d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v9022pD630d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v04B4p3101d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v0CCDp0064d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v9022pD650d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v04B4p2104d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v04B4p2101d*dc*dsc*dp*ic*isc*ip*
> alias: usb:v04B4p2102d*dc*dsc*dp*ic*isc*ip*
> depends: dvb-usb
> vermagic: 2.6.32-22-generic SMP mod_unload modversions 586
> parm: debug:set debugging level (1=info 2=xfer
> 4=rc(or-able)). (int)
> parm: keymap:set keymap 0=default 1=dvbworld 2=tevii 3=tbs
> ... (int)
> parm: demod:demod to probe (1=cx24116 2=stv0903+stv6110
> 4=stv0903+stb6100(or-able)). (int)
> parm: adapter_nr:DVB adapter numbers (array of short)
>
>
> I'm not convinced that either of us is actually communicating with our
> s660s. do you get a /dev/dvb/adapter0/frontend0? can you get any
> output at all from the device? if so, with what?
>
> There are too many variables here. I'd like to collect all of the
> configurations of a known working system and work methodically from
> there.
> On 6 May 2010, at 20:09, william wrote:
>
>> Hello Tim,
>>
>> i also have a tevii s660 which i cannot get to work properly.
>>
>> i'm no programmer and nobody has given a reaction on my previous
>> posts (debugging my tevii...).
>>
>> I get this in my log after getting the source from the linuxtv site
>> with the driver igor wrote:
>>
>>
>> [ 45.654362] dvb-usb: found a 'TeVii S660 USB' in cold state, will
>> try to load a firmware
>> [ 45.654379] usb 1-3: firmware: requesting dvb-usb-s630.fw
>> [ 45.717438] dvb-usb: downloading firmware from file 'dvb-usb-s630.fw'
>> [ 45.717450] dw2102: start downloading DW210X firmware
>> [ 45.824245] usb 1-3: USB disconnect, address 3
>> [ 45.930055] dvb-usb: found a 'TeVii S660 USB' in warm state.
>> [ 45.930167] dvb-usb: will pass the complete MPEG2 transport stream
>> to the software demuxer.
>> [ 45.930233] DVB: registering new adapter (TeVii S660 USB)
>> [ 56.182533] dvb-usb: MAC address: 00:00:00:00:00:00
>> [ 56.262532] mt312: R(126): 00
>> [ 56.262543] Only Zarlink VP310/MT312/ZL10313 are supported chips.
>> [ 56.607024] ds3000_attach
>> [ 56.642535] ds3000_readreg: read reg 0x00, value 0x00
>> [ 56.642542] Invalid probe, probably not a DS3000
>> [ 56.642816] dvb-usb: no frontend was attached by 'TeVii S660 USB'
>> [ 56.643037] input: IR-receiver inside an USB DVB receiver as
>> /devices/pci0000:00/0000:00:1d.7/usb1/1-3/input/input5
>> [ 56.643189] dvb-usb: schedule remote query interval to 150 msecs.
>> [ 56.643203] dvb-usb: TeVii S660 USB successfully initialized and
>> connected.
>> [ 56.643290] usbcore: registered new interface driver dw2102
>> [ 56.773230] dvb-usb: TeVii S660 USB successfully deinitialized and
>> disconnected.
>> [ 57.050043] usb 1-3: new high speed USB device using ehci_hcd and
>> address 5
>>
>> in my previous post i got a message that an mt312 chip was found and
>> now it does not find anything.
>> so now i don't have a dvb device at all.
>>
>> the firmware is from the drivers from tevii. I tried and the s630
>> firmware and later the s660 firmware renamed to s630 but none worked.
>>
>> After installing the driver/changing the firmware, I shutdown the
>> computer removed the power from the tevii device and then replugged
>> and started my computer again.
>>
>> ======
>>
>> modinfo dvb-usb-dw2102
>> filename:
>> /lib/modules/2.6.34-020634rc2-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb-dw2102.ko
>>
>> license: GPL
>> version: 0.1
>> description: Driver for DVBWorld DVB-S 2101, 2102, DVB-S2 2104,
>> DVB-C 3101 USB2.0, TeVii S600, S630, S650, S660 USB2.0, Prof 1100,
>> 7500 USB2.0 devices
>> author: Igor M. Liplianin (c) liplianin@me.by
>> srcversion: FCBA4EFAEF1F6A88DC9F2DB
>> alias: usb:v3034p7500d*dc*dsc*dp*ic*isc*ip*
>> alias: usb:v9022pD660d*dc*dsc*dp*ic*isc*ip*
>> alias: usb:v3011pB012d*dc*dsc*dp*ic*isc*ip*
>> alias: usb:v9022pD630d*dc*dsc*dp*ic*isc*ip*
>> alias: usb:v04B4p3101d*dc*dsc*dp*ic*isc*ip*
>> alias: usb:v0CCDp0064d*dc*dsc*dp*ic*isc*ip*
>> alias: usb:v9022pD650d*dc*dsc*dp*ic*isc*ip*
>> alias: usb:v04B4p2104d*dc*dsc*dp*ic*isc*ip*
>> alias: usb:v04B4p2101d*dc*dsc*dp*ic*isc*ip*
>> alias: usb:v04B4p2102d*dc*dsc*dp*ic*isc*ip*
>> depends: dvb-usb
>> vermagic: 2.6.34-020634rc2-generic SMP mod_unload modversions
>> parm: debug:set debugging level (1=info 2=xfer
>> 4=rc(or-able)). (int)
>> parm: keymap:set keymap 0=default 1=dvbworld 2=tevii 3=tbs
>> ... (int)
>> parm: demod:demod to probe (1=cx24116 2=stv0903+stv6110
>> 4=stv0903+stb6100(or-able)). (int)
>> parm: adapter_nr:DVB adapter numbers (array of short)
>> ========
>>
>> if you need help testing i would be glad to help.
>>
>> The tevii drivers are working and also detect the mt312 chip.
>> This driver does not, but i'm not very pleased about the driver from
>> tevii because channel switch takes long and image quality is bad and
>> my system get's slow/freezes.
>>
>> With kind regards
>>
>> William van de Velde
>>
>> On 05/06/2010 01:07 AM, Tim Coote wrote:
>>> Hullo
>>> I've been struggling with this for a couple of days. I have checked
>>> archives, but missed anything useful.
>>>
>>> I've got a tevii s660 (dvbs2 via usb). It works with some
>>> limitations on windows xp (I cannot get HD signals decoded, but
>>> think that's a limitation of the software that comes on the CD).
>>>
>>> I'm trying to get this working on Linux. I've tried VMs based on
>>> fedora 12 and mythbuntu (VMWare Fusion on a MacBookPro, both based
>>> on kernel 2.6.32), using the drivers from tevii's site
>>> (www.tevii.com/support.asp). these drivers are slightly modified
>>> versions of the v4l tip - but don't appear to be modified where I've
>>> not yet managed to get the drivers working :-(. Mythbuntu seems to
>>> be closest to working. Goodness knows how tevii tested the code, but
>>> it doesn't seem to work as far as I can see. My issues could just
>>> be down to using a VM.
>>>
>>> I believe that I need to load up the modules ds3000 and
>>> dvb-usb-dw2102, + add a rule to /etc/udev/rules.d and a script to
>>> /etc/udev/scripts.
>>>
>>> I think that I must be missing quite a lot of context, tho'. When I
>>> look at the code in dw2102.c, which seems to support the s660, the
>>> bit that downloads the firmware looks broken and if I add a default
>>> clause to the switch that does the download, the s660's missed the
>>> download process. This could be why when I do get anything out of
>>> the device it looks like I'm just getting repeated bytes (the same
>>> value repeated, different values at different times, sometimes
>>> nothing). I'm finding it non-trivial working out the call sequences
>>> of the code or devising repeatable tests.
>>>
>>> Can anyone kick me off on getting this working? I'd like to at least
>>> get to the point where scandvb can tune the device. It does look
>>> like some folk have had success in the past, but probably with
>>> totally different codebase (there are posts that refer to the
>>> teviis660 module, which I cannot find).
>>>
>>> Any pointer gratefully accepted. I'll feed back any success if I can
>>> be pointed at where to drop document it.
>>>
>>> tia
>>>
>>> Tim
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe
>>> linux-media" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>>
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: setting up a tevii s660
2010-05-07 12:31 ` william
@ 2010-05-07 14:33 ` Tim Coote
2010-05-07 16:41 ` william
0 siblings, 1 reply; 12+ messages in thread
From: Tim Coote @ 2010-05-07 14:33 UTC (permalink / raw)
To: william; +Cc: linux-media
Thanks, William. Really helpful.
I think that the issue is down to the mt312 or the ds3000_readreg.
Here's my /var/log/kern.log (I had some confusion over which log file
to look at due to
distro variations), from the tevii 100315_Beta_linux_tevii_ds3000.rar
code:
May 7 07:04:25 ubuntu kernel: [ 1888.738744] usb 1-1: USB disconnect,
address 5
May 7 07:04:25 ubuntu kernel: [ 1888.756834] dvb-usb: TeVii S660 USB
successfully deinitialized and disconnected.
May 7 07:04:30 ubuntu kernel: [ 1893.648175] usb 1-1: new high speed
USB device using ehci_hcd and address 6
May 7 07:04:30 ubuntu kernel: [ 1893.835482] usb 1-1: config 1
interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 2
May 7 07:04:31 ubuntu kernel: [ 1893.844725] usb 1-1: configuration
#1 chosen from 1 choice
May 7 07:04:31 ubuntu kernel: [ 1893.989017] dvb-usb: found a 'TeVii
S660 USB' in cold state, will try to load a firmware
May 7 07:04:31 ubuntu kernel: [ 1893.989030] usb 1-1: firmware:
requesting dvb-usb-teviis660.fw
May 7 07:04:31 ubuntu kernel: [ 1893.995703] dvb-usb: downloading
firmware from file 'dvb-usb-teviis660.fw'
May 7 07:04:31 ubuntu kernel: [ 1893.995706] dw2102: start
downloading DW210X firmware
May 7 07:04:31 ubuntu kernel: [ 1894.360084] dvb-usb: found a 'TeVii
S660 USB' in warm state.
May 7 07:04:31 ubuntu kernel: [ 1894.361316] dvb-usb: will pass the
complete MPEG2 transport stream to the software demuxer.
May 7 07:04:31 ubuntu kernel: [ 1894.362140] DVB: registering new
adapter (TeVii S660 USB)
May 7 07:04:36 ubuntu kernel: [ 1899.484223] dvb-usb: MAC address:
70:70:70:70:70:70
May 7 07:04:36 ubuntu kernel: [ 1899.612725] mt312: R(126): 00
May 7 07:04:36 ubuntu kernel: [ 1899.612729] Only Zarlink VP310/MT312/
ZL10313 are supported chips.
May 7 07:04:37 ubuntu kernel: [ 1899.844336] ds3000_attach
May 7 07:04:37 ubuntu kernel: [ 1899.864116] ds3000_readreg: read reg
0x00, value 0x70
May 7 07:04:37 ubuntu kernel: [ 1899.864119] Invalid probe, probably
not a DS3000
May 7 07:04:37 ubuntu kernel: [ 1899.864208] dvb-usb: no frontend was
attached by 'TeVii S660 USB'
May 7 07:04:37 ubuntu kernel: [ 1899.866721] dvb-usb: TeVii S660 USB
successfully initialized and connected.
Clearly, either I've still got the wrong code, my hardware's
different, or I've got some other config difference. your logfile
clearly shows that ds3000_readreg is getting the correct 0xe0
response, whereas mine's come back with 0x70 and therefore doesn't try
to attach the frontend...
here's the hashes taht I've got for the modules (from modinfo, I think
that this should show whether we're using hte same sources):
ds3000: srcversion: 8BBEA04D5B5CDF6343234E5
dw2102: srcversion: ADE91410D87CAB74AE3862C
mt312: srcversion: E4DBE51A55D359EB4157AA2
what did you do to get your mt312 correctly identified?
On my wintel box, channel switching takes a couple of seconds, does
yours take much longer?
what's the real problem with leaving the rc polling on ? I know that
you get log messages, but they're only messages. they can be turned
off by commenting out the info lines (info ("query RC... ) and then
make/sudo make install (just put // at the beginning of the lines in
dw2102.c)
On 7 May 2010, at 13:31, william wrote:
> Hello Tim,
>
> On 05/07/2010 01:41 PM, Tim Coote wrote:
>> William
>> did you load your modules with debug=1, or something else, somehow?
>> I thought that the code printing out ds3000_readreg required debug.
>> or have you got different source code from the tevii driver on www.tevii.com/Support.asp?
>> (unless I know what you're using, I cannot tell what's relevant.)
> i tried this so probably yes
> /etc/modprobe.d/test.conf
> ##
> options mt312 debug=1
> options ds3000 debug=1
> options dvb-usb-dw2102 debug=1
> options dvb-usb disable_rc_polling=1
> options dvb-usb-dw2102 keymap=2 demod=2
> ##
>
> The tevii device should be supported by the linuxtv drivers:
>
> ############
> hg clone http://linuxtv.org/hg/v4l-dvb
> cd v4l-dvb
> make menuconfig disable/enable what you need
> make&& make install
> poweroff
> remove power/usb cables
> replug the power to tevii device
> then connect the usb
> then poweron pc
>
> Then i get this in my log:
> modprobe dvb-usb-dw2102
> [ 217.546580] dvb-usb: found a 'TeVii S660 USB' in cold state, will
> try to load a firmware
> [ 217.546595] usb 1-3: firmware: requesting dvb-usb-s630.fw
> [ 217.630018] dvb-usb: downloading firmware from file 'dvb-usb-
> s630.fw'
> [ 217.630030] dw2102: start downloading DW210X firmware
> [ 217.748783] usb 1-3: USB disconnect, address 3
> [ 217.850050] dvb-usb: found a 'TeVii S660 USB' in warm state.
> [ 217.850161] dvb-usb: will pass the complete MPEG2 transport
> stream to the software demuxer.
> [ 217.850236] DVB: registering new adapter (TeVii S660 USB)
> [ 228.090038] dvb-usb: MAC address: 00:00:00:00:00:00
> [ 228.162540] mt312: R(126): 00
> [ 228.162550] Only Zarlink VP310/MT312/ZL10313 are supported chips.
> [ 228.507136] ds3000_attach
> [ 228.542534] ds3000_readreg: read reg 0x00, value 0x00
> [ 228.542541] Invalid probe, probably not a DS3000
> [ 228.542808] dvb-usb: no frontend was attached by 'TeVii S660 USB'
> [ 228.542861] dvb-usb: TeVii S660 USB successfully initialized and
> connected.
> [ 228.543000] usbcore: registered new interface driver dw2102
> [ 228.543454] dvb-usb: TeVii S660 USB successfully deinitialized
> and disconnected.
> [ 228.820045] usb 1-3: new high speed USB device using ehci_hcd and
> address 5
>
> ########
>
> using the tevii drivers i get this:
> doing the same make ; make install ; poweroff ....
> modprobe dvb-usb-dw2102
>
> [ 80.354236] dvb-usb: found a 'TeVii S660 USB' in cold state, will
> try to load a firmware
> [ 80.354252] usb 1-3: firmware: requesting dvb-usb-teviis660.fw
> [ 80.418598] dvb-usb: downloading firmware from file 'dvb-usb-
> teviis660.fw'
> [ 80.418609] dw2102: start downloading DW210X firmware
> [ 80.436136] usb 1-3: USB disconnect, address 3
> [ 80.545656] dvb-usb: found a 'TeVii S660 USB' in warm state.
> [ 80.545780] dvb-usb: will pass the complete MPEG2 transport
> stream to the software demuxer.
> [ 80.545840] DVB: registering new adapter (TeVii S660 USB)
> [ 90.810041] dvb-usb: MAC address: 00:00:00:00:00:00
> [ 90.921279] mt312: R(126): 00
> [ 90.921289] Only Zarlink VP310/MT312/ZL10313 are supported chips.
> [ 91.243014] ds3000_attach
> [ 91.283778] ds3000_readreg: read reg 0x00, value 0x00
> [ 91.283785] Invalid probe, probably not a DS3000
> [ 91.284052] dvb-usb: no frontend was attached by 'TeVii S660 USB'
> [ 91.284105] dvb-usb: TeVii S660 USB successfully initialized and
> connected.
> [ 91.284209] usbcore: registered new interface driver dw2102
> [ 91.284744] dvb-usb: TeVii S660 USB successfully deinitialized
> and disconnected.
> [ 91.560036] usb 1-3: new high speed USB device using ehci_hcd and
> address 5
> [ 91.710433] usb 1-3: config 1 interface 0 altsetting 0 bulk
> endpoint 0x81 has invalid maxpacket 2
> [ 91.712260] dvb-usb: found a 'TeVii S660 USB' in cold state, will
> try to load a firmware
> [ 91.712275] usb 1-3: firmware: requesting dvb-usb-teviis660.fw
> [ 91.722989] dvb-usb: downloading firmware from file 'dvb-usb-
> teviis660.fw'
> [ 91.723001] dw2102: start downloading DW210X firmware
> [ 91.840045] dvb-usb: found a 'TeVii S660 USB' in warm state.
> [ 91.840180] dvb-usb: will pass the complete MPEG2 transport
> stream to the software demuxer.
> [ 91.840339] DVB: registering new adapter (TeVii S660 USB)
> [ 102.080030] dvb-usb: MAC address: 00:18:bd:5c:54:7f
> [ 102.120028] mt312: R(126): ff
> [ 102.120038] Only Zarlink VP310/MT312/ZL10313 are supported chips.
> [ 102.390448] ds3000_attach
> [ 102.430027] ds3000_readreg: read reg 0x00, value 0xe0
> [ 102.470026] ds3000_readreg: read reg 0x01, value 0xc0
> [ 102.510026] ds3000_readreg: read reg 0x02, value 0x00
> [ 102.510033] DS3000 chip version: 0.192 attached.
> [ 102.510039] dw2102: Attached ds3000+ds2020!
> [ 102.510041]
> [ 102.510274] DVB: registering adapter 1 frontend 0 (Montage
> Technology DS3000/TS2020)...
> [ 102.510645] dvb-usb: TeVii S660 USB successfully initialized and
> connected.
>
> #########
>
> now i have:
>
> root@backend:~# ls -al /dev/dvb/adapter1/
> total 0
> drwxr-xr-x 2 root root 120 2010-05-07 14:23 .
> drwxr-xr-x 4 root root 80 2010-05-07 14:23 ..
> crw-rw---- 1 root video 212, 4 2010-05-07 14:23 demux0
> crw-rw---- 1 root video 212, 5 2010-05-07 14:23 dvr0
> crw-rw---- 1 root video 212, 7 2010-05-07 14:23 frontend0
> crw-rw---- 1 root video 212, 6 2010-05-07 14:23 net0
>
>
> ###
>
> Now i can also make use off the device except that my system gets
> slow and channel zapping takes ages.
> i disabled the debug message for the remote with the option
> disable_rc_polling for dvb-usb.
>
> only then you cannot use the remote :)
>
> With kind regards
>
> William van de Velde
>
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: setting up a tevii s660
2010-05-07 14:33 ` Tim Coote
@ 2010-05-07 16:41 ` william
2010-05-07 21:18 ` Tim Coote
0 siblings, 1 reply; 12+ messages in thread
From: william @ 2010-05-07 16:41 UTC (permalink / raw)
To: Tim Coote; +Cc: linux-media
On 05/07/2010 04:33 PM, Tim Coote wrote:
> Thanks, William. Really helpful.
>
> I think that the issue is down to the mt312 or the ds3000_readreg.
> Here's my /var/log/kern.log (I had some confusion over which log file
> to look at due to
> distro variations), from the tevii 100315_Beta_linux_tevii_ds3000.rar
> code:
>
> May 7 07:04:25 ubuntu kernel: [ 1888.738744] usb 1-1: USB disconnect,
> address 5
> May 7 07:04:25 ubuntu kernel: [ 1888.756834] dvb-usb: TeVii S660 USB
> successfully deinitialized and disconnected.
> May 7 07:04:30 ubuntu kernel: [ 1893.648175] usb 1-1: new high speed
> USB device using ehci_hcd and address 6
> May 7 07:04:30 ubuntu kernel: [ 1893.835482] usb 1-1: config 1
> interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 2
> May 7 07:04:31 ubuntu kernel: [ 1893.844725] usb 1-1: configuration
> #1 chosen from 1 choice
> May 7 07:04:31 ubuntu kernel: [ 1893.989017] dvb-usb: found a 'TeVii
> S660 USB' in cold state, will try to load a firmware
> May 7 07:04:31 ubuntu kernel: [ 1893.989030] usb 1-1: firmware:
> requesting dvb-usb-teviis660.fw
> May 7 07:04:31 ubuntu kernel: [ 1893.995703] dvb-usb: downloading
> firmware from file 'dvb-usb-teviis660.fw'
> May 7 07:04:31 ubuntu kernel: [ 1893.995706] dw2102: start
> downloading DW210X firmware
> May 7 07:04:31 ubuntu kernel: [ 1894.360084] dvb-usb: found a 'TeVii
> S660 USB' in warm state.
> May 7 07:04:31 ubuntu kernel: [ 1894.361316] dvb-usb: will pass the
> complete MPEG2 transport stream to the software demuxer.
> May 7 07:04:31 ubuntu kernel: [ 1894.362140] DVB: registering new
> adapter (TeVii S660 USB)
> May 7 07:04:36 ubuntu kernel: [ 1899.484223] dvb-usb: MAC address:
> 70:70:70:70:70:70
> May 7 07:04:36 ubuntu kernel: [ 1899.612725] mt312: R(126): 00
> May 7 07:04:36 ubuntu kernel: [ 1899.612729] Only Zarlink
> VP310/MT312/ZL10313 are supported chips.
> May 7 07:04:37 ubuntu kernel: [ 1899.844336] ds3000_attach
> May 7 07:04:37 ubuntu kernel: [ 1899.864116] ds3000_readreg: read reg
> 0x00, value 0x70
> May 7 07:04:37 ubuntu kernel: [ 1899.864119] Invalid probe, probably
> not a DS3000
> May 7 07:04:37 ubuntu kernel: [ 1899.864208] dvb-usb: no frontend was
> attached by 'TeVii S660 USB'
> May 7 07:04:37 ubuntu kernel: [ 1899.866721] dvb-usb: TeVii S660 USB
> successfully initialized and connected.
>
> Clearly, either I've still got the wrong code, my hardware's
> different, or I've got some other config difference. your logfile
> clearly shows that ds3000_readreg is getting the correct 0xe0
> response, whereas mine's come back with 0x70 and therefore doesn't try
> to attach the frontend...
> here's the hashes taht I've got for the modules (from modinfo, I think
> that this should show whether we're using hte same sources):
> ds3000: srcversion: 8BBEA04D5B5CDF6343234E5
> dw2102: srcversion: ADE91410D87CAB74AE3862C
> mt312: srcversion: E4DBE51A55D359EB4157AA2
mine are:
ds3000: srcversion: C7DB14F51712A761A96E6C0
dvb-usb-dw2102: srcversion: FCBA4EFAEF1F6A88DC9F2DB
mt312: srcversion: 01AA722165F2811847AD121
md5sums from tevii source:
ds3000.c fd28e654d57f0336640b6f13bed5102c
dw2102.c 019a275475fe2fbf9a255c65d80ee7be
mt312.c 222360df7838633b8b05e471b18678bd
With kind regards
William
>
> what did you do to get your mt312 correctly identified?
>
> On my wintel box, channel switching takes a couple of seconds, does
> yours take much longer?
>
> what's the real problem with leaving the rc polling on ? I know that
> you get log messages, but they're only messages. they can be turned
> off by commenting out the info lines (info ("query RC... ) and then
> make/sudo make install (just put // at the beginning of the lines in
> dw2102.c)
>
> On 7 May 2010, at 13:31, william wrote:
>
>> Hello Tim,
>>
>> On 05/07/2010 01:41 PM, Tim Coote wrote:
>>> William
>>> did you load your modules with debug=1, or something else, somehow?
>>> I thought that the code printing out ds3000_readreg required debug.
>>> or have you got different source code from the tevii driver on
>>> www.tevii.com/Support.asp? (unless I know what you're using, I
>>> cannot tell what's relevant.)
>> i tried this so probably yes
>> /etc/modprobe.d/test.conf
>> ##
>> options mt312 debug=1
>> options ds3000 debug=1
>> options dvb-usb-dw2102 debug=1
>> options dvb-usb disable_rc_polling=1
>> options dvb-usb-dw2102 keymap=2 demod=2
>> ##
>>
>> The tevii device should be supported by the linuxtv drivers:
>>
>> ############
>> hg clone http://linuxtv.org/hg/v4l-dvb
>> cd v4l-dvb
>> make menuconfig disable/enable what you need
>> make&& make install
>> poweroff
>> remove power/usb cables
>> replug the power to tevii device
>> then connect the usb
>> then poweron pc
>>
>> Then i get this in my log:
>> modprobe dvb-usb-dw2102
>> [ 217.546580] dvb-usb: found a 'TeVii S660 USB' in cold state, will
>> try to load a firmware
>> [ 217.546595] usb 1-3: firmware: requesting dvb-usb-s630.fw
>> [ 217.630018] dvb-usb: downloading firmware from file 'dvb-usb-s630.fw'
>> [ 217.630030] dw2102: start downloading DW210X firmware
>> [ 217.748783] usb 1-3: USB disconnect, address 3
>> [ 217.850050] dvb-usb: found a 'TeVii S660 USB' in warm state.
>> [ 217.850161] dvb-usb: will pass the complete MPEG2 transport stream
>> to the software demuxer.
>> [ 217.850236] DVB: registering new adapter (TeVii S660 USB)
>> [ 228.090038] dvb-usb: MAC address: 00:00:00:00:00:00
>> [ 228.162540] mt312: R(126): 00
>> [ 228.162550] Only Zarlink VP310/MT312/ZL10313 are supported chips.
>> [ 228.507136] ds3000_attach
>> [ 228.542534] ds3000_readreg: read reg 0x00, value 0x00
>> [ 228.542541] Invalid probe, probably not a DS3000
>> [ 228.542808] dvb-usb: no frontend was attached by 'TeVii S660 USB'
>> [ 228.542861] dvb-usb: TeVii S660 USB successfully initialized and
>> connected.
>> [ 228.543000] usbcore: registered new interface driver dw2102
>> [ 228.543454] dvb-usb: TeVii S660 USB successfully deinitialized and
>> disconnected.
>> [ 228.820045] usb 1-3: new high speed USB device using ehci_hcd and
>> address 5
>>
>> ########
>>
>> using the tevii drivers i get this:
>> doing the same make ; make install ; poweroff ....
>> modprobe dvb-usb-dw2102
>>
>> [ 80.354236] dvb-usb: found a 'TeVii S660 USB' in cold state, will
>> try to load a firmware
>> [ 80.354252] usb 1-3: firmware: requesting dvb-usb-teviis660.fw
>> [ 80.418598] dvb-usb: downloading firmware from file
>> 'dvb-usb-teviis660.fw'
>> [ 80.418609] dw2102: start downloading DW210X firmware
>> [ 80.436136] usb 1-3: USB disconnect, address 3
>> [ 80.545656] dvb-usb: found a 'TeVii S660 USB' in warm state.
>> [ 80.545780] dvb-usb: will pass the complete MPEG2 transport stream
>> to the software demuxer.
>> [ 80.545840] DVB: registering new adapter (TeVii S660 USB)
>> [ 90.810041] dvb-usb: MAC address: 00:00:00:00:00:00
>> [ 90.921279] mt312: R(126): 00
>> [ 90.921289] Only Zarlink VP310/MT312/ZL10313 are supported chips.
>> [ 91.243014] ds3000_attach
>> [ 91.283778] ds3000_readreg: read reg 0x00, value 0x00
>> [ 91.283785] Invalid probe, probably not a DS3000
>> [ 91.284052] dvb-usb: no frontend was attached by 'TeVii S660 USB'
>> [ 91.284105] dvb-usb: TeVii S660 USB successfully initialized and
>> connected.
>> [ 91.284209] usbcore: registered new interface driver dw2102
>> [ 91.284744] dvb-usb: TeVii S660 USB successfully deinitialized and
>> disconnected.
>> [ 91.560036] usb 1-3: new high speed USB device using ehci_hcd and
>> address 5
>> [ 91.710433] usb 1-3: config 1 interface 0 altsetting 0 bulk
>> endpoint 0x81 has invalid maxpacket 2
>> [ 91.712260] dvb-usb: found a 'TeVii S660 USB' in cold state, will
>> try to load a firmware
>> [ 91.712275] usb 1-3: firmware: requesting dvb-usb-teviis660.fw
>> [ 91.722989] dvb-usb: downloading firmware from file
>> 'dvb-usb-teviis660.fw'
>> [ 91.723001] dw2102: start downloading DW210X firmware
>> [ 91.840045] dvb-usb: found a 'TeVii S660 USB' in warm state.
>> [ 91.840180] dvb-usb: will pass the complete MPEG2 transport stream
>> to the software demuxer.
>> [ 91.840339] DVB: registering new adapter (TeVii S660 USB)
>> [ 102.080030] dvb-usb: MAC address: 00:18:bd:5c:54:7f
>> [ 102.120028] mt312: R(126): ff
>> [ 102.120038] Only Zarlink VP310/MT312/ZL10313 are supported chips.
>> [ 102.390448] ds3000_attach
>> [ 102.430027] ds3000_readreg: read reg 0x00, value 0xe0
>> [ 102.470026] ds3000_readreg: read reg 0x01, value 0xc0
>> [ 102.510026] ds3000_readreg: read reg 0x02, value 0x00
>> [ 102.510033] DS3000 chip version: 0.192 attached.
>> [ 102.510039] dw2102: Attached ds3000+ds2020!
>> [ 102.510041]
>> [ 102.510274] DVB: registering adapter 1 frontend 0 (Montage
>> Technology DS3000/TS2020)...
>> [ 102.510645] dvb-usb: TeVii S660 USB successfully initialized and
>> connected.
>>
>> #########
>>
>> now i have:
>>
>> root@backend:~# ls -al /dev/dvb/adapter1/
>> total 0
>> drwxr-xr-x 2 root root 120 2010-05-07 14:23 .
>> drwxr-xr-x 4 root root 80 2010-05-07 14:23 ..
>> crw-rw---- 1 root video 212, 4 2010-05-07 14:23 demux0
>> crw-rw---- 1 root video 212, 5 2010-05-07 14:23 dvr0
>> crw-rw---- 1 root video 212, 7 2010-05-07 14:23 frontend0
>> crw-rw---- 1 root video 212, 6 2010-05-07 14:23 net0
>>
>>
>> ###
>>
>> Now i can also make use off the device except that my system gets
>> slow and channel zapping takes ages.
>> i disabled the debug message for the remote with the option
>> disable_rc_polling for dvb-usb.
>>
>> only then you cannot use the remote :)
>>
>> 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 majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: setting up a tevii s660
2010-05-07 16:41 ` william
@ 2010-05-07 21:18 ` Tim Coote
0 siblings, 0 replies; 12+ messages in thread
From: Tim Coote @ 2010-05-07 21:18 UTC (permalink / raw)
To: william; +Cc: linux-media
fixed the initial problem: my hardware platform was broken. I
eventually created a windows VM and ran the tevii code on that - did
not work. So I pulled together a physical box, which worked.
Lesson: Fusion VM does not reliably work with the tevii. I don't know
what's broken, but I cannot see any obvious paramaters to twitch. This
is a shame as it is a powerful test technique to run up different
configs on VMs.
I'm sure I'll be back on the list before this device works as well as
it does on Windows.
I note that the box that the s660 came in had a linux logo, so
presumably there's some sort of agreed service level that would be
agreed to to allow such branding.... Otherwise linux will never be
well supported.
Tim
On 7 May 2010, at 17:41, william wrote:
> On 05/07/2010 04:33 PM, Tim Coote wrote:
>> Thanks, William. Really helpful.
>>
>> I think that the issue is down to the mt312 or the ds3000_readreg.
>> Here's my /var/log/kern.log (I had some confusion over which log
>> file to look at due to
>> distro variations), from the tevii
>> 100315_Beta_linux_tevii_ds3000.rar code:
>>
>> May 7 07:04:25 ubuntu kernel: [ 1888.738744] usb 1-1: USB
>> disconnect, address 5
>> May 7 07:04:25 ubuntu kernel: [ 1888.756834] dvb-usb: TeVii S660
>> USB successfully deinitialized and disconnected.
>> May 7 07:04:30 ubuntu kernel: [ 1893.648175] usb 1-1: new high
>> speed USB device using ehci_hcd and address 6
>> May 7 07:04:30 ubuntu kernel: [ 1893.835482] usb 1-1: config 1
>> interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 2
>> May 7 07:04:31 ubuntu kernel: [ 1893.844725] usb 1-1:
>> configuration #1 chosen from 1 choice
>> May 7 07:04:31 ubuntu kernel: [ 1893.989017] dvb-usb: found a
>> 'TeVii S660 USB' in cold state, will try to load a firmware
>> May 7 07:04:31 ubuntu kernel: [ 1893.989030] usb 1-1: firmware:
>> requesting dvb-usb-teviis660.fw
>> May 7 07:04:31 ubuntu kernel: [ 1893.995703] dvb-usb: downloading
>> firmware from file 'dvb-usb-teviis660.fw'
>> May 7 07:04:31 ubuntu kernel: [ 1893.995706] dw2102: start
>> downloading DW210X firmware
>> May 7 07:04:31 ubuntu kernel: [ 1894.360084] dvb-usb: found a
>> 'TeVii S660 USB' in warm state.
>> May 7 07:04:31 ubuntu kernel: [ 1894.361316] dvb-usb: will pass
>> the complete MPEG2 transport stream to the software demuxer.
>> May 7 07:04:31 ubuntu kernel: [ 1894.362140] DVB: registering new
>> adapter (TeVii S660 USB)
>> May 7 07:04:36 ubuntu kernel: [ 1899.484223] dvb-usb: MAC address:
>> 70:70:70:70:70:70
>> May 7 07:04:36 ubuntu kernel: [ 1899.612725] mt312: R(126): 00
>> May 7 07:04:36 ubuntu kernel: [ 1899.612729] Only Zarlink VP310/
>> MT312/ZL10313 are supported chips.
>> May 7 07:04:37 ubuntu kernel: [ 1899.844336] ds3000_attach
>> May 7 07:04:37 ubuntu kernel: [ 1899.864116] ds3000_readreg: read
>> reg 0x00, value 0x70
>> May 7 07:04:37 ubuntu kernel: [ 1899.864119] Invalid probe,
>> probably not a DS3000
>> May 7 07:04:37 ubuntu kernel: [ 1899.864208] dvb-usb: no frontend
>> was attached by 'TeVii S660 USB'
>> May 7 07:04:37 ubuntu kernel: [ 1899.866721] dvb-usb: TeVii S660
>> USB successfully initialized and connected.
>>
>> Clearly, either I've still got the wrong code, my hardware's
>> different, or I've got some other config difference. your logfile
>> clearly shows that ds3000_readreg is getting the correct 0xe0
>> response, whereas mine's come back with 0x70 and therefore doesn't
>> try to attach the frontend...
>> here's the hashes taht I've got for the modules (from modinfo, I
>> think that this should show whether we're using hte same sources):
>> ds3000: srcversion: 8BBEA04D5B5CDF6343234E5
>> dw2102: srcversion: ADE91410D87CAB74AE3862C
>> mt312: srcversion: E4DBE51A55D359EB4157AA2
>
> mine are:
> ds3000: srcversion: C7DB14F51712A761A96E6C0
> dvb-usb-dw2102: srcversion: FCBA4EFAEF1F6A88DC9F2DB
> mt312: srcversion: 01AA722165F2811847AD121
>
> md5sums from tevii source:
> ds3000.c fd28e654d57f0336640b6f13bed5102c
> dw2102.c 019a275475fe2fbf9a255c65d80ee7be
> mt312.c 222360df7838633b8b05e471b18678bd
>
>
> With kind regards
>
> William
>>
>> what did you do to get your mt312 correctly identified?
>>
>> On my wintel box, channel switching takes a couple of seconds, does
>> yours take much longer?
>>
>> what's the real problem with leaving the rc polling on ? I know
>> that you get log messages, but they're only messages. they can be
>> turned off by commenting out the info lines (info ("query RC... )
>> and then make/sudo make install (just put // at the beginning of
>> the lines in dw2102.c)
>>
>> On 7 May 2010, at 13:31, william wrote:
>>
>>> Hello Tim,
>>>
>>> On 05/07/2010 01:41 PM, Tim Coote wrote:
>>>> William
>>>> did you load your modules with debug=1, or something else,
>>>> somehow? I thought that the code printing out ds3000_readreg
>>>> required debug. or have you got different source code from the
>>>> tevii driver on www.tevii.com/Support.asp? (unless I know what
>>>> you're using, I cannot tell what's relevant.)
>>> i tried this so probably yes
>>> /etc/modprobe.d/test.conf
>>> ##
>>> options mt312 debug=1
>>> options ds3000 debug=1
>>> options dvb-usb-dw2102 debug=1
>>> options dvb-usb disable_rc_polling=1
>>> options dvb-usb-dw2102 keymap=2 demod=2
>>> ##
>>>
>>> The tevii device should be supported by the linuxtv drivers:
>>>
>>> ############
>>> hg clone http://linuxtv.org/hg/v4l-dvb
>>> cd v4l-dvb
>>> make menuconfig disable/enable what you need
>>> make&& make install
>>> poweroff
>>> remove power/usb cables
>>> replug the power to tevii device
>>> then connect the usb
>>> then poweron pc
>>>
>>> Then i get this in my log:
>>> modprobe dvb-usb-dw2102
>>> [ 217.546580] dvb-usb: found a 'TeVii S660 USB' in cold state,
>>> will try to load a firmware
>>> [ 217.546595] usb 1-3: firmware: requesting dvb-usb-s630.fw
>>> [ 217.630018] dvb-usb: downloading firmware from file 'dvb-usb-
>>> s630.fw'
>>> [ 217.630030] dw2102: start downloading DW210X firmware
>>> [ 217.748783] usb 1-3: USB disconnect, address 3
>>> [ 217.850050] dvb-usb: found a 'TeVii S660 USB' in warm state.
>>> [ 217.850161] dvb-usb: will pass the complete MPEG2 transport
>>> stream to the software demuxer.
>>> [ 217.850236] DVB: registering new adapter (TeVii S660 USB)
>>> [ 228.090038] dvb-usb: MAC address: 00:00:00:00:00:00
>>> [ 228.162540] mt312: R(126): 00
>>> [ 228.162550] Only Zarlink VP310/MT312/ZL10313 are supported chips.
>>> [ 228.507136] ds3000_attach
>>> [ 228.542534] ds3000_readreg: read reg 0x00, value 0x00
>>> [ 228.542541] Invalid probe, probably not a DS3000
>>> [ 228.542808] dvb-usb: no frontend was attached by 'TeVii S660 USB'
>>> [ 228.542861] dvb-usb: TeVii S660 USB successfully initialized
>>> and connected.
>>> [ 228.543000] usbcore: registered new interface driver dw2102
>>> [ 228.543454] dvb-usb: TeVii S660 USB successfully deinitialized
>>> and disconnected.
>>> [ 228.820045] usb 1-3: new high speed USB device using ehci_hcd
>>> and address 5
>>>
>>> ########
>>>
>>> using the tevii drivers i get this:
>>> doing the same make ; make install ; poweroff ....
>>> modprobe dvb-usb-dw2102
>>>
>>> [ 80.354236] dvb-usb: found a 'TeVii S660 USB' in cold state,
>>> will try to load a firmware
>>> [ 80.354252] usb 1-3: firmware: requesting dvb-usb-teviis660.fw
>>> [ 80.418598] dvb-usb: downloading firmware from file 'dvb-usb-
>>> teviis660.fw'
>>> [ 80.418609] dw2102: start downloading DW210X firmware
>>> [ 80.436136] usb 1-3: USB disconnect, address 3
>>> [ 80.545656] dvb-usb: found a 'TeVii S660 USB' in warm state.
>>> [ 80.545780] dvb-usb: will pass the complete MPEG2 transport
>>> stream to the software demuxer.
>>> [ 80.545840] DVB: registering new adapter (TeVii S660 USB)
>>> [ 90.810041] dvb-usb: MAC address: 00:00:00:00:00:00
>>> [ 90.921279] mt312: R(126): 00
>>> [ 90.921289] Only Zarlink VP310/MT312/ZL10313 are supported chips.
>>> [ 91.243014] ds3000_attach
>>> [ 91.283778] ds3000_readreg: read reg 0x00, value 0x00
>>> [ 91.283785] Invalid probe, probably not a DS3000
>>> [ 91.284052] dvb-usb: no frontend was attached by 'TeVii S660 USB'
>>> [ 91.284105] dvb-usb: TeVii S660 USB successfully initialized
>>> and connected.
>>> [ 91.284209] usbcore: registered new interface driver dw2102
>>> [ 91.284744] dvb-usb: TeVii S660 USB successfully deinitialized
>>> and disconnected.
>>> [ 91.560036] usb 1-3: new high speed USB device using ehci_hcd
>>> and address 5
>>> [ 91.710433] usb 1-3: config 1 interface 0 altsetting 0 bulk
>>> endpoint 0x81 has invalid maxpacket 2
>>> [ 91.712260] dvb-usb: found a 'TeVii S660 USB' in cold state,
>>> will try to load a firmware
>>> [ 91.712275] usb 1-3: firmware: requesting dvb-usb-teviis660.fw
>>> [ 91.722989] dvb-usb: downloading firmware from file 'dvb-usb-
>>> teviis660.fw'
>>> [ 91.723001] dw2102: start downloading DW210X firmware
>>> [ 91.840045] dvb-usb: found a 'TeVii S660 USB' in warm state.
>>> [ 91.840180] dvb-usb: will pass the complete MPEG2 transport
>>> stream to the software demuxer.
>>> [ 91.840339] DVB: registering new adapter (TeVii S660 USB)
>>> [ 102.080030] dvb-usb: MAC address: 00:18:bd:5c:54:7f
>>> [ 102.120028] mt312: R(126): ff
>>> [ 102.120038] Only Zarlink VP310/MT312/ZL10313 are supported chips.
>>> [ 102.390448] ds3000_attach
>>> [ 102.430027] ds3000_readreg: read reg 0x00, value 0xe0
>>> [ 102.470026] ds3000_readreg: read reg 0x01, value 0xc0
>>> [ 102.510026] ds3000_readreg: read reg 0x02, value 0x00
>>> [ 102.510033] DS3000 chip version: 0.192 attached.
>>> [ 102.510039] dw2102: Attached ds3000+ds2020!
>>> [ 102.510041]
>>> [ 102.510274] DVB: registering adapter 1 frontend 0 (Montage
>>> Technology DS3000/TS2020)...
>>> [ 102.510645] dvb-usb: TeVii S660 USB successfully initialized
>>> and connected.
>>>
>>> #########
>>>
>>> now i have:
>>>
>>> root@backend:~# ls -al /dev/dvb/adapter1/
>>> total 0
>>> drwxr-xr-x 2 root root 120 2010-05-07 14:23 .
>>> drwxr-xr-x 4 root root 80 2010-05-07 14:23 ..
>>> crw-rw---- 1 root video 212, 4 2010-05-07 14:23 demux0
>>> crw-rw---- 1 root video 212, 5 2010-05-07 14:23 dvr0
>>> crw-rw---- 1 root video 212, 7 2010-05-07 14:23 frontend0
>>> crw-rw---- 1 root video 212, 6 2010-05-07 14:23 net0
>>>
>>>
>>> ###
>>>
>>> Now i can also make use off the device except that my system gets
>>> slow and channel zapping takes ages.
>>> i disabled the debug message for the remote with the option
>>> disable_rc_polling for dvb-usb.
>>>
>>> only then you cannot use the remote :)
>>>
>>> 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 majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: setting up a tevii s660
2010-05-05 23:07 setting up a tevii s660 Tim Coote
2010-05-06 19:09 ` william
@ 2010-05-09 18:46 ` Igor M. Liplianin
2010-05-09 21:29 ` Tim Coote
1 sibling, 1 reply; 12+ messages in thread
From: Igor M. Liplianin @ 2010-05-09 18:46 UTC (permalink / raw)
To: Tim Coote; +Cc: linux-media
On 6 мая 2010 02:07:38 Tim Coote wrote:
> Hullo
> I've been struggling with this for a couple of days. I have checked
> archives, but missed anything useful.
>
> I've got a tevii s660 (dvbs2 via usb). It works with some limitations
> on windows xp (I cannot get HD signals decoded, but think that's a
> limitation of the software that comes on the CD).
>
> I'm trying to get this working on Linux. I've tried VMs based on
> fedora 12 and mythbuntu (VMWare Fusion on a MacBookPro, both based on
> kernel 2.6.32), using the drivers from tevii's site
> (www.tevii.com/support.asp) . these drivers are slightly modified versions
> of the v4l tip - but don't appear to be modified where I've not yet managed
> to get the
> drivers working :-(. Mythbuntu seems to be closest to working.
> Goodness knows how tevii tested the code, but it doesn't seem to work
> as far as I can see. My issues could just be down to using a VM.
>
> I believe that I need to load up the modules ds3000 and dvb-usb-
> dw2102, + add a rule to /etc/udev/rules.d and a script to /etc/udev/
> scripts.
>
> I think that I must be missing quite a lot of context, tho'. When I
> look at the code in dw2102.c, which seems to support the s660, the bit
> that downloads the firmware looks broken and if I add a default clause
> to the switch that does the download, the s660's missed the download
> process. This could be why when I do get anything out of the device
> it looks like I'm just getting repeated bytes (the same value
> repeated, different values at different times, sometimes nothing).
> I'm finding it non-trivial working out the call sequences of the code
> or devising repeatable tests.
>
> Can anyone kick me off on getting this working? I'd like to at least
> get to the point where scandvb can tune the device. It does look like
> some folk have had success in the past, but probably with totally
> different codebase (there are posts that refer to the teviis660
> module, which I cannot find).
>
> Any pointer gratefully accepted. I'll feed back any success if I can
> be pointed at where to drop document it.
>
> tia
>
> Tim
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi!
Read this:
http://forum.free-x.de/wbb/index.php?page=Thread&threadID=601&pageNo=6
Useful to translate from Russian:
http://babelfish.yahoo.com/translate_txt
Best regards
--
Igor M. Liplianin
Microsoft Windows Free Zone - Linux used for all Computing Tasks
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: setting up a tevii s660
2010-05-09 18:46 ` Igor M. Liplianin
@ 2010-05-09 21:29 ` Tim Coote
2010-05-10 10:56 ` Igor M. Liplianin
0 siblings, 1 reply; 12+ messages in thread
From: Tim Coote @ 2010-05-09 21:29 UTC (permalink / raw)
To: Igor M. Liplianin; +Cc: linux-media
Thanks, Igor. I was using that set of drivers (if I understood the
Babelfish translation.)
My issue was that my hardware was broken (I was using a VMWare VM that
didn't emulate usb properly). It's always hard to work out what's
broken when you load up some new package and it doesn't work. I'd
confirmed that the s660 worked from windows, but I had to build a
windows vm to demonstrate that it was VMWare that was broken.
Meanwhile, I kept stumbling across what seemed to be similar breakages
to what I was seeing.
I don't know how feasible it would be, but when I used to write device
drivers, I'd pull together simple programs to test that the hardware
was working as I'd expect as I spent so much time debugging changing
hardware designs :-(
I would say that the tevii drivers have both new code compared to the
tip of the driver that you manage, and also seem to be missing some
code.
thanks again for your help. Now all I've got to do is get mythtv to
work...
Tim
On 9 May 2010, at 19:46, Igor M. Liplianin wrote:
> On 6 мая 2010 02:07:38 Tim Coote wrote:
>> [snip]
> Hi!
> Read this:
> http://forum.free-x.de/wbb/index.php?page=Thread&threadID=601&pageNo=6
> Useful to translate from Russian:
> http://babelfish.yahoo.com/translate_txt
> Best regards
> --
> Igor M. Liplianin
> Microsoft Windows Free Zone - Linux used for all Computing Tasks
> --
> To unsubscribe from this list: send the line "unsubscribe linux-
> media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Tim Coote
tim@coote.org
+44 (0)7866 479 760
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: setting up a tevii s660
2010-05-09 21:29 ` Tim Coote
@ 2010-05-10 10:56 ` Igor M. Liplianin
0 siblings, 0 replies; 12+ messages in thread
From: Igor M. Liplianin @ 2010-05-10 10:56 UTC (permalink / raw)
To: Tim Coote; +Cc: linux-media
On 10 мая 2010 00:29:13 Tim Coote wrote:
> Thanks, Igor. I was using that set of drivers (if I understood the
> Babelfish translation.)
>
> My issue was that my hardware was broken (I was using a VMWare VM that
> didn't emulate usb properly). It's always hard to work out what's
> broken when you load up some new package and it doesn't work. I'd
> confirmed that the s660 worked from windows, but I had to build a
> windows vm to demonstrate that it was VMWare that was broken.
> Meanwhile, I kept stumbling across what seemed to be similar breakages
> to what I was seeing.
>
> I don't know how feasible it would be, but when I used to write device
> drivers, I'd pull together simple programs to test that the hardware
> was working as I'd expect as I spent so much time debugging changing
> hardware designs :-(
>
> I would say that the tevii drivers have both new code compared to the
> tip of the driver that you manage, and also seem to be missing some
> code.
So called "TeVii drivers" is simply a snapshot from linuxtv, so OK, they are useable.
>
> thanks again for your help. Now all I've got to do is get mythtv to
> work...
>
> Tim
>
> On 9 May 2010, at 19:46, Igor M. Liplianin wrote:
> > On 6 мая 2010 02:07:38 Tim Coote wrote:
> >> [snip]
> >
> > Hi!
> > Read this:
> > http://forum.free-x.de/wbb/index.php?page=Thread&threadID=601&pageNo=6
> > Useful to translate from Russian:
> > http://babelfish.yahoo.com/translate_txt
> > Best regards
> > --
> > Igor M. Liplianin
> > Microsoft Windows Free Zone - Linux used for all Computing Tasks
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-
> > media" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> Tim Coote
> tim@coote.org
> +44 (0)7866 479 760
--
Igor M. Liplianin
Microsoft Windows Free Zone - Linux used for all Computing Tasks
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: setting up a tevii s660
2010-05-06 19:14 Fwd: " Paul Shepherd
@ 2010-05-07 11:09 ` Tim Coote
0 siblings, 0 replies; 12+ messages in thread
From: Tim Coote @ 2010-05-07 11:09 UTC (permalink / raw)
To: Paul Shepherd; +Cc: linux-media
On 6 May 2010, at 20:14, Paul Shepherd wrote:
> [snip]
> I downloaded version from tevii.com and it worked for me on laptop
> running win 7. Had problems with HD on an XP machine but I assumed it
> was because the video card was old/slow.
that seems a fair test. you've got to know that the device itself's
working first
>
[snip]
>
> I tried on Ubuntu 9.10 but had problems which I documented here on 16
> april. Loading the firmware worked fine but there were problems with
> remote control messages being logged continually as well as stability
> problems. The card would tune (with scan) and worked with mythtv
> (for a
> day or so)
I get this output, too. I think that it's debugging code that's been
left in. I'd guess that the driver polls the device periodically and
spits out the results. If that's right, then you can remove the
messages from dmesg and /var/log/messages by commenting out the
relevant info lines in the source (should be lines 1131, 1137 and 1155
of ./linux=tevii-ds3000/linux/drivers/media/dev/dvb-usb/dw2102.c). I
think that line 84 implies that there was an intent for these messages
to be debug rather than info, but I'm not familiar with the coding
standards enough to fix that. I'd guess that the crash that you
experienced comes from something else, but goodness knows what or how
to debug it.
>
>> I believe that I need to load up the modules ds3000 and dvb-usb-
>> dw2102,
>> + add a rule to /etc/udev/rules.d and a script to /etc/udev/scripts.
>
> I didn't touch rules.d
Since my initial post, I've tried a vanilla xubuntu 10.04, (at the
suggestion of a member of the list who'd got it working with this
build) which still only populates /dev/dvb/adapter0/{demux0 drv0 net0}
and not frontend0. See below.
[snip]
>
>
> Had no problem with Ubuntu recognising the device and the correct .fw
> file being downloaded.
>
> There are various versions of dw2102.c from tevii, etc. I think I
> tried
> all of them. I did change the timeout on RC messages (dw2102.c?) which
> helped but did not cure the problem.
>
> Also tried the s2-liplianin library as well which seemed promising but
> also did not cure the problem.
>
I'm less sure now about my conclusions about downloading the .fw.
Certainly on xubuntu *something* is happening as I get a blue led
flash on plugging in the tevii.
>> [snip]
>> didn't have the knowledge (or time) to decide if the problem was in
> the firmware or the v4l drivers or perhaps some strange interaction
> with
> my dvb-t usb box.
>
> Exchanged some emails with tevii guys who had posted here however they
> appear to take the view that if it works under windows then the device
> is fine and offer no other solution.
>
> In the end I bought a Nova S2 PCI card which works fine but would be
> interested in trying to get the S660 working.
>
I don't have a pc that's big enough to take a pci card, and the
hardware clearly works. However, to debug what's going wrong, there
needs to be a repeatable test process, and a baseline system where the
different failure modes can be tied down. That's why I set up the
xubuntu system and used a .config file thats known to work. However,
there's still other stuff to load on a vanilla box, including:
build-essentials
linux-headers-2.6.32-22-generic
and possibly libncurses5-dev and a complete kernel source tree,
although I've avoided this by reusing the .config file.
I'm still assuming that 'working' means that I can use dvbscan (which
needs the frontend0 file, I think, although the reported error on
xubuntu is different from mythbuntu and it just says "Failed to open
frontend".
I'm afraid that in a situation like this, I don't know what I don't
know. And I don't know what I can rely on or what success is. Not a
great recipe for getting anything to do what you want.
I can understand tevii's point of view, but I need to get this working
on Linux. I don't think that Tevii wrote the code and it is slightly
modified from the mercurial code, so there needs to be some sort of
merge back if and when it is ever made to work.
> paul
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2010-05-10 10:56 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-05-05 23:07 setting up a tevii s660 Tim Coote
2010-05-06 19:09 ` william
2010-05-07 11:41 ` Tim Coote
2010-05-07 11:46 ` Josu Lazkano
2010-05-07 12:31 ` william
2010-05-07 14:33 ` Tim Coote
2010-05-07 16:41 ` william
2010-05-07 21:18 ` Tim Coote
2010-05-09 18:46 ` Igor M. Liplianin
2010-05-09 21:29 ` Tim Coote
2010-05-10 10:56 ` Igor M. Liplianin
2010-05-06 19:14 Fwd: " Paul Shepherd
2010-05-07 11:09 ` Tim Coote
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.