Re: driver problem: cx231xx error -71 with Hauppauge USB live2 on Ubuntu 11.04, netbook edition

2011-07-26 Thread Doychin Dokov
I'm having the same problem, on Ubuntu Server 11.04 x64, kernel 
2.6.38-10. I've also tried Debian with the same results. Here's the 
debug log from the Ubuntu installation:

[416830.888124] cx231xx #0: cx231xx #0/0: registered device video3 [v4l2]
[416830.888243] cx231xx #0: cx231xx #0/0: registered device vbi3
[416830.888251] cx231xx #0: V4L2 device registered as video3 and vbi3
[416830.888260] cx231xx #0: cx231xx-audio.c: probing for cx231xx non 
standard usbaudio

[416830.888684] cx231xx #0: EndPoint Addr 0x83, Alternate settings: 3
[416830.888695] cx231xx #0: Alternate setting 0, max size= 512
[416830.888703] cx231xx #0: Alternate setting 1, max size= 28
[416830.888710] cx231xx #0: Alternate setting 2, max size= 52
[416830.888720] cx231xx #0: EndPoint Addr 0x84, Alternate settings: 5
[416830.888728] cx231xx #0: Alternate setting 0, max size= 512
[416830.888735] cx231xx #0: Alternate setting 1, max size= 184
[416830.888742] cx231xx #0: Alternate setting 2, max size= 728
[416830.888749] cx231xx #0: Alternate setting 3, max size= 2892
[416830.888756] cx231xx #0: Alternate setting 4, max size= 1800
[416830.888763] cx231xx #0: EndPoint Addr 0x85, Alternate settings: 2
[416830.888771] cx231xx #0: Alternate setting 0, max size= 512
[416830.888778] cx231xx #0: Alternate setting 1, max size= 512
[416830.888786] cx231xx #0: EndPoint Addr 0x86, Alternate settings: 2
[416830.888794] cx231xx #0: Alternate setting 0, max size= 512
[416830.01] cx231xx #0: Alternate setting 1, max size= 576
[416830.890957] cx231xx #0 cx231xx_v4l2_open :open dev=video3 
type=vid-cap users

[416830.890975] cx231xx #0:  setPowerMode::mode = 48, No Change req.
[416830.890986] cx231xx #0 cx231xx_set_video_alternate 
:dev-video_mode.alt= 3
[416830.890996] cx231xx #0 cx231xx_set_video_alternate :minimum isoc 
packet size
[416830.891007] cx231xx #0 cx231xx_set_video_alternate :setting 
alternate 3 with

[416830.903131] cx231xx #0: cannot change alt number to 3 (error=-71)
[416830.906687] cx231xx #0: (pipe 0x80001280): IN:  c0 04 29 88 21 04 01 
00 FAIL
[416830.914736] cx231xx #0: UsbInterface::sendCommand, failed with 
status --71
[416830.914752] cx231xx #0: (pipe 0x80001200): OUT:  40 00 21 88 00 00 
03 00 
[416830.922983] cx231xx #0: UsbInterface::sendCommand, failed with 
status --71

[416830.923028] cx231xx #0 video: VIDIOC_QUERYCAP
[416830.923060] cx231xx #0 cx231xx_v4l2_open :open dev=vbi3 type=vbi-cap 
users=1

[416830.923089] cx231xx #0 vbi: VIDIOC_QUERYCAP
[416830.923123] cx231xx #0 cx231xx_v4l2_close :users=2
[416830.923128] cx231xx #0 cx231xx_v4l2_close :users=2
[416830.923181] cx231xx #0 cx231xx_v4l2_close :users=1
[416830.923188] cx231xx #0 cx231xx_v4l2_close :users=1
[416830.923199] cx231xx #0 cx231xx_uninit_isoc :cx231xx: called 
cx231xx_uninit_i

[416830.923208] cx231xx #0: cx231xx_stop_stream():: ep_mask = 8
[416830.923220] cx231xx #0: (pipe 0x80001280): IN:  c0 0d 0f 00 18 00 04 
00 FAIL
[416830.931259] cx231xx #0 cx231xx_set_alt_setting :setting alternate 0 
with wMa

[416830.939483] cx231xx #0: can't change interface 3 alt no. to 0 (err=-71)

This is with the stock kernel, no media_build tree installed (I'm 
currently compiling it).




На 20.1.2011 г. 14:11 ч., Gerard Toonstra написа:

Hello,

I'm using a Hauppauge USB live2 video capture stick with Ubuntu 11.04,
netbook edition.
On Ubuntu 10.04, I pulled v4l from a development mercurial branch,
where cx231xx drivers were provided. That worked ok.

Ubuntu since then was upgraded to 10.10 with kernel 2.6.35, which is
where I couldn't use that branch anymore. Since the driver was
upstreamed,
I decided to give the media_build branch a go. I ran into problems
trying to compile media_build on 10.10, because that uses kernel
2.6.35,
and decided to upgrade to Ubuntu alpha 11.04, which uses kernel
2.6.37, so that the v4l would be better supported.

After deactivating two modules in .config that created some problems
in media_build, I was able to get a successful build and 'make
install'
them. After a reboot and sticking in the capture stick, tvtime, xawtv
or other applications do start, but only a black screen is the result.
The standard camera from the netbook itself does give output, so it's
not likely an overall video or X issue. I tried to remove the stick,
replug it back in,
replug it into different ports, start up with the stick already in,
but nothing worked. The output @ dmesg is always the same and repeats
itself infinitely.

dmesg and lsusb information is attached.

Further details:
- hardware: Siemens N210 netbook  (has another built-in camera @ /dev/video0)
- Ubuntu 11.04 netbook edition
- Linux 2.6.37-12-generic 32-bit i686 GNU/Linux  (stock kernel that
comes with Ubuntu 11.04)
- Code pulled from media_build.git, cloned yesterday
- Hauppauge USB Live2 video capture card, using cx231xx driver.


Are there any workarounds or quick patches available, or is the best
bet to revert to 10.04 for now?

Rgds,

--
Gerard Toonstra



--
To unsubscribe from this list: send 

Re: driver problem: cx231xx error -71 with Hauppauge USB live2 on Ubuntu 11.04, netbook edition

2011-07-26 Thread Doychin Dokov

На 26.7.2011 г. 15:17 ч., Devin Heitmueller написа:

On Tue, Jul 26, 2011 at 7:53 AM, Doychin Dokovr...@net1.cc  wrote:

[416830.939483] cx231xx #0: can't change interface 3 alt no. to 0 (err=-71)

This is with the stock kernel, no media_build tree installed (I'm currently
compiling it).


Patches for this issue were submitted over the weekend.  Check the
mailing list for posts from Saturday or wait a few days for the
patches to be merged into the linux_media tree.



I find only the Sunday fix for the power ramp issue, which states it's 
for a problem caused by the config hz being different of 100. Is this 
the patch you point me to, and do you think it's the solution in my case?


# cat /boot/config-2.6.38-10-server | grep CONFIG_HZ
CONFIG_HZ_100=y
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=100

Kind regards,
Doychin

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


Re: [PATCH] Fix regression introduced which broke the Hauppauge USBLive 2

2011-07-26 Thread Doychin Dokov

На 24.7.2011 г. 04:17 ч., Devin Heitmueller написа:

The following patch addresses the regression introduced in the cx231xx
driver which stopped the Hauppauge USBLive2 from working.

Confirmed working by both myself and the user who reported the issue
on the KernelLabs blog (Robert DeLuca).



I can also confirm this patch works fine for me.

[  839.052752] cx231xx: Cx231xx Audio Extension initialized
[  850.221325] cx231xx #0: cx231xx_start_stream():: ep_mask = 4
[  850.224774] cx231xx #0: cx231xx_init_audio_isoc: Starting ISO AUDIO 
transfers

[  851.150358] cx231xx #0: cx231xx_stop_stream():: ep_mask = 4

It was not possible to capture audio from the device before that.

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


Re: [PATCH] Add support for PCTV452E.

2011-06-12 Thread Doychin Dokov

The same thing happens when the devices are on different USB buses:
Bus 002 Device 004: ID 0b48:300a TechnoTrend AG TT-connect S2-3650 CI
Bus 001 Device 007: ID 0b48:3006 TechnoTrend AG TT-connect S-2400 DVB-S
Bus 001 Device 004: ID 734c:5980 TBS Technologies China

When the S2-3650 CI scans, the stream output from the TBS is gone. When 
it's done scanning / locking, the TBS continues to work fine. The S-2400 
is not affected in any way, nor it affects the other receivers.


It seems the issue is not relative to the devices being on the same USB 
bus, nor the kernel used. I've tried Debian's 2.6.32.5 and 2.6.38-bpo2 
on a Debian Squeeze system.


На 11.6.2011 г. 19:38 ч., Doychin Dokov написа:

i've been using the patches in the latest media_tree for some hours -
the S2-3650 CI seems to work. There's one thing that disturbs me, though
- when it scans / locks on a frequency, another device on the same PC,
using the same stb6100, gets stuck for a moment. Any ideas what might be
the cause for that? The two devices do not share common RF input signal,
but are on the same USB bus:
Bus 001 Device 004: ID 734c:5980 TBS Technologies China
Bus 001 Device 003: ID 0b48:300a TechnoTrend AG TT-connect S2-3650 CI

The TBS device is a QBOX2 SI, which works with their official driver
from their web-site.

There's also a third DVB device in the system - a TT S-2400 (which is on
the other USB bus, though), which does not exhibit any problems related
with the first two devices, nor causes them to get stuck when it's
scanning.

I'll try to switch devices around and see if anything changes.



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


Re: [PATCH] Add support for PCTV452E.

2011-06-12 Thread Doychin Dokov

On 2.6.32.5 with s2-liplianin tree this is not observed, i.e. everything
works as expected - the S2-3650 does not cause the TBS device to stutter.

На 12.6.2011 г. 23:27 ч., Doychin Dokov написа:

The same thing happens when the devices are on different USB buses:
Bus 002 Device 004: ID 0b48:300a TechnoTrend AG TT-connect S2-3650 CI
Bus 001 Device 007: ID 0b48:3006 TechnoTrend AG TT-connect S-2400 DVB-S
Bus 001 Device 004: ID 734c:5980 TBS Technologies China

When the S2-3650 CI scans, the stream output from the TBS is gone. When
it's done scanning / locking, the TBS continues to work fine. The S-2400
is not affected in any way, nor it affects the other receivers.

It seems the issue is not relative to the devices being on the same USB
bus, nor the kernel used. I've tried Debian's 2.6.32.5 and 2.6.38-bpo2
on a Debian Squeeze system.

На 11.6.2011 г. 19:38 ч., Doychin Dokov написа:

i've been using the patches in the latest media_tree for some hours -
the S2-3650 CI seems to work. There's one thing that disturbs me, though
- when it scans / locks on a frequency, another device on the same PC,
using the same stb6100, gets stuck for a moment. Any ideas what might be
the cause for that? The two devices do not share common RF input signal,
but are on the same USB bus:
Bus 001 Device 004: ID 734c:5980 TBS Technologies China
Bus 001 Device 003: ID 0b48:300a TechnoTrend AG TT-connect S2-3650 CI

The TBS device is a QBOX2 SI, which works with their official driver
from their web-site.

There's also a third DVB device in the system - a TT S-2400 (which is on
the other USB bus, though), which does not exhibit any problems related
with the first two devices, nor causes them to get stuck when it's
scanning.

I'll try to switch devices around and see if anything changes.





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


Re: [PATCH] Add support for PCTV452E.

2011-06-12 Thread Doychin Dokov
I also confirmed it works with s2-liplianin on Debian's 2.6.38-bpo2 
kernel without such problems.


Another thing I've tested is to compile the media_tree with the stb6100, 
but the problem persist, so it seems it's not related to the component 
that both devices share.


Any ideas what might be the reason for that, or at least where I should 
focus at searching?


На 13.6.2011 г. 00:38 ч., Doychin Dokov написа:

On 2.6.32.5 with s2-liplianin tree this is not observed, i.e. everything
works as expected - the S2-3650 does not cause the TBS device to stutter.

На 12.6.2011 г. 23:27 ч., Doychin Dokov написа:

The same thing happens when the devices are on different USB buses:
Bus 002 Device 004: ID 0b48:300a TechnoTrend AG TT-connect S2-3650 CI
Bus 001 Device 007: ID 0b48:3006 TechnoTrend AG TT-connect S-2400 DVB-S
Bus 001 Device 004: ID 734c:5980 TBS Technologies China

When the S2-3650 CI scans, the stream output from the TBS is gone. When
it's done scanning / locking, the TBS continues to work fine. The S-2400
is not affected in any way, nor it affects the other receivers.

It seems the issue is not relative to the devices being on the same USB
bus, nor the kernel used. I've tried Debian's 2.6.32.5 and 2.6.38-bpo2
on a Debian Squeeze system.

На 11.6.2011 г. 19:38 ч., Doychin Dokov написа:

i've been using the patches in the latest media_tree for some hours -
the S2-3650 CI seems to work. There's one thing that disturbs me, though
- when it scans / locks on a frequency, another device on the same PC,
using the same stb6100, gets stuck for a moment. Any ideas what might be
the cause for that? The two devices do not share common RF input signal,
but are on the same USB bus:
Bus 001 Device 004: ID 734c:5980 TBS Technologies China
Bus 001 Device 003: ID 0b48:300a TechnoTrend AG TT-connect S2-3650 CI

The TBS device is a QBOX2 SI, which works with their official driver
from their web-site.

There's also a third DVB device in the system - a TT S-2400 (which is on
the other USB bus, though), which does not exhibit any problems related
with the first two devices, nor causes them to get stuck when it's
scanning.

I'll try to switch devices around and see if anything changes.







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


Re: [PATCH] Add support for PCTV452E.

2011-06-11 Thread Doychin Dokov
i've been using the patches in the latest media_tree for some hours - 
the S2-3650 CI seems to work. There's one thing that disturbs me, though 
- when it scans / locks on a frequency, another device on the same PC, 
using the same stb6100, gets stuck for a moment. Any ideas what might be 
the cause for that? The two devices do not share common RF input signal, 
but are on the same USB bus:

Bus 001 Device 004: ID 734c:5980 TBS Technologies China
Bus 001 Device 003: ID 0b48:300a TechnoTrend AG TT-connect S2-3650 CI

The TBS device is a QBOX2 SI, which works with their official driver 
from their web-site.


There's also a third DVB device in the system - a TT S-2400 (which is on 
the other USB bus, though), which does not exhibit any problems related 
with the first two devices, nor causes them to get stuck when it's scanning.


I'll try to switch devices around and see if anything changes.

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


Re: [PATCH] Add support for PCTV452E.

2011-06-10 Thread Doychin Dokov

I think you've missed this line at the end of ttpci-eeprom.c :

EXPORT_SYMBOL(ttpci_eeprom_decode_mac);

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


Re: TT S2-3650CI problems with high-SR DVB-S2 transponders

2011-05-11 Thread Doychin Dokov
I've just tried with the 2.6.38 kernel from the backports, and the lock 
fix only - result is the same, unusable output from device - too many 
discontinuities.


Noone using the S2-3600 / 3650 on high-rate transponders?

Any other Linux-supported USB DVB-S2 device with CI and high SR support?



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


TT S2-3650CI problems with high-SR DVB-S2 transponders

2011-05-10 Thread Doychin Dokov
I've been trying to get TechnoTrend S2-3650CI running with DVB-S2 
transponder with SR of 3. I'm using stock Debian 6 kernel 
2.6.32-5-amd64 and s2-liplianin tree.


Initially, the device couldn't lock the 30K transponders at all. After 
applying patch [1], it locks without any problems, and does so very fast:
sat 0, frequency 11632 MHz V, symbolrate 3000, coderate auto, 
rolloff 0.35

vpid 0x1fff, apid 0x1fff, sid 0x
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
status 00 | signal  | snr 0004 | ber  | unc fffe |
status 1b | signal 05aa | snr 0023 | ber 00516155 | unc fffe | 
FE_HAS_LOCK
This happens each and every time I try. So far, so good, but when I'm 
trying to stream a PID with dvblast, I get lots of TS discontinuities. 
It does read the NIT and PAT fine, but nothing else is nearly-usable.


I've then tried the STB6100 patch [2], but it does not seem to do any 
help in this case.


Any ideas?

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


Re: TT S2-3650CI problems with high-SR DVB-S2 transponders

2011-05-10 Thread Doychin Dokov

На 11.5.2011 г. 02:24 ч., Doychin Dokov написа:

I've been trying to get TechnoTrend S2-3650CI running with DVB-S2
transponder with SR of 3. I'm using stock Debian 6 kernel
2.6.32-5-amd64 and s2-liplianin tree.

Initially, the device couldn't lock the 30K transponders at all. After
applying patch [1], it locks without any problems, and does so very fast:
sat 0, frequency 11632 MHz V, symbolrate 3000, coderate auto,
rolloff 0.35
vpid 0x1fff, apid 0x1fff, sid 0x
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
status 00 | signal  | snr 0004 | ber  | unc fffe |
status 1b | signal 05aa | snr 0023 | ber 00516155 | unc fffe |
FE_HAS_LOCK
This happens each and every time I try. So far, so good, but when I'm
trying to stream a PID with dvblast, I get lots of TS discontinuities.
It does read the NIT and PAT fine, but nothing else is nearly-usable.

I've then tried the STB6100 patch [2], but it does not seem to do any
help in this case.

Any ideas?



Sorry, missed some info:
[1] http://dev.net1.cc/dvb-s23650/patch-01-lock-fix.diff
[2] http://dev.net1.cc/dvb-s23650/patch-02-noise-filter.diff

Also, the same device on the same machine, but under Windows OS, works 
fine and decodes the very same transponder with no artefacts at all.
The firmware of the device is updated with the latest one from the TT 
web site.


Thanks very much for any help!


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