Beiträge von liviurosioara

Hi everyone!

It is not a magical patch for usbtuner.c, it's just the rmie's revised usbtuner where I increased the buffers in order to have it working. I am affraid I've lost the virtual machine partition which I've used to compile the binary. I will try to look for a backup this weekend.

Hi there!

As I said earlier on pages 20-22, now cinergy t2 dvb-t usb really works on e2, including scan and also watching tv. Pay atention to the patches for DVB-T and specially for Cinergy T2

Zitat

Originally posted by rmie

Nearly no time left in the last few days, and no hope that it'll be much better the days coming.

If it's that easy to fool enigma, fine
Did you use vtunerc/vtunerd running on the same box, or did you use the usbtuner binary?

Well, I had also to tweak the values from the usb buffer, otherwise only the SD channels were working or the environment became unstable. Both vtunerd/vtunerct and usbtuner are working. But I found a small mistake in the version you updated and posted (adapter0 instead of 1 and demux=2).

I still have a small problem and I can't figure why it's happening. The image on one single HD channel is flickering. This is visible where the tv station logo is displayed (moving upwars few pixels in 1-2 seconds interval) and also the OSD (enigma2 bar or menu) is doing the same, like jumping upwards few pixels and then normal, at 1-2 seconds. Sometimes when I switch between channels or zap from a black screen, the display works normal.

Any idea for this?

Back again!

I have got the Cinergy T2 USB DVB-T working directly on my DM800. I will explain you how:

- first, I had edited the driver CinergyT2.c from kernel and modified the following:

#ifdef CONFIG_DVB_CINERGYT2_TUNING
#define STREAM_URB_COUNT (CONFIG_DVB_CINERGYT2_STREAM_URB_COUNT)
#define STREAM_BUF_SIZE (CONFIG_DVB_CINERGYT2_STREAM_BUF_SIZE)
#define QUERY_INTERVAL (CONFIG_DVB_CINERGYT2_QUERY_INTERVAL)
#ifdef CONFIG_DVB_CINERGYT2_ENABLE_RC_INPUT_DEVICE
#define RC_QUERY_INTERVAL (CONFIG_DVB_CINERGYT2_RC_QUERY_INTERVAL)
#define ENABLE_RC (1)
#endif
#else
#define STREAM_URB_COUNT (5)
#define STREAM_BUF_SIZE (512*100) /* bytes */
#define ENABLE_RC (0)
#define RC_QUERY_INTERVAL (100) /* milliseconds */
#define QUERY_INTERVAL (50) /* milliseconds */
#endif

and ...

case FE_GET_FRONTEND:
/**
* trivial to implement (see struct dvbt_get_status_msg).
* equivalent to FE_READ ioctls, but needs
* TPS -> linux-dvb parameter set conversion. Feel free
* to implement this and send us a patch if you need this
* functionality.
*/
return 0;

Then, I compiled vtunerd.mipsel with dvb3 instead of dmm3. Now it works

Zitat

Originally posted by rmie

This should work (as usual, totaly untested

Code

147a148
> 			struct dvb_frontend_parameters fe_params;
158a160
> 				memcpy(&fe_params, &msg.body.dvb_frontend_parameters, sizeof(fe_params));
161c163,166
< 				require(ioctl(fe, FE_GET_FRONTEND, &msg.body.dvb_frontend_parameters) == 0, "FE_GET_FRONTEND");
---
> 				if(ioctl(fe, FE_GET_FRONTEND, &msg.body.dvb_frontend_parameters)) {
> 					// workaround for broken CinergyT2 driver
> 					memcpy(&msg.body.dvb_frontend_parameters, &fe_params, sizeof(msg.body.dvb_frontend_parameters));
> 				}

Alles anzeigen

Roland

Alles anzeigen

rmie,

All the tests I have performed were with vtunerd-dvb3.mipsel you have provided to me. I will need this patch applied to vtunerd.c and vtuner-dvb3.c instead.

Just to remind you the part of the error log:

[1081 vtuner-dvb-3.c:91] warn: FE_GET_FRONTEND failed
[1081 vtunerd.c:290] debug: MSG_GET_FRONTEND
[1081 vtunerd.c:347] warn: vtuner call failed, type:-1 reason:-1 - Invalid argument

Maybe you can take a look also at 'vtuner call failed'.

Zitat

Originally posted by rmie

I'm not sure, but the suggested work around is easy. So it's worth trying.

Hi,

I got the toolchain working. But my knowledge in programming is still limited Could you indicate the steps needed, please?

I didn't manage to build the env. I will try again in the evening.

But do you think that the warning 'FE_GET_FRONTEND failed' is the cause for not having the stream displayed?

Now, I can tell you why it's failing... It has nothing but a comment in the source file in the section where FE_GET_FRONTEND should be defined... So the driver is the problem.

rmie

Thank you for helping me with the vtunerd-dvb3 version.
When tuning a dvb-t channel on dm800, the blue led of the usb tuner lights up, this is a good sign. After that, the dm800 displays the snr/agc/ber info, after some seconds i got the 'no data on the transponder - timeout reading PAT' and then the led of the usb tuner goes off again.

I captured the logs of both vtunerd-dvb3 and vtunerct running in the same time, maybe you can figure what's happening

What I saw it was wrong:

[1081 vtuner-dvb-3.c:91] warn: FE_GET_FRONTEND failed
[1081 vtunerd.c:290] debug: MSG_GET_FRONTEND
[1081 vtunerd.c:347] warn: vtuner call failed, type:-1 reason:-1 - Invalid argument

Sounds great I'll test right now!

Later edit: it doesn't work. After restarting e2, there is an error message FE_SET_VOLTAGE failed - Invalid argument. And no tuning at all.

I have read the thread about usbtuner some weeks ago and already tested the binary. Unfortunatelly, it works only for dvb-s tuners.

I'm pretty sure that compiling the vtunerd for dm800 in the way it doesn't have the integrated tuner will allow me to make use of the usb device.

If you can't compile this, at least is it possible to guide me how to make the mipsel-linux-gcc for dm800 or to have access to files from folder /stuff/dm800?

I have tested usbtuner before, it's not working with dvb-t for the moment.

Because I don't have the toolchain to cross-compile vtunerd for dm800, I would need your help to build the vtunerd from 26.08 with dvb-api instead of dmm tuner. Then I will test it and provide with the details.

rmie, thanks again, you were right, the version from 26.08 works fine, I use vtunerd on popcornhour nmt with attached usb dvb-t cinergy t2 and vtunerc on dm800.

What I would like to try next is to connect directly the usb tuner to dm800, and to run both vtunerd and vtunerc on the same dm800. But this would require a vtunerd version compiled for dvb tuner and dm800, like I said in the previous post. I suppose compile.sh should look like:

CC=/stuff/dm800/build/tmp/cross/bin/mipsel-linux-gcc
ARCH=mipsel
CFLAGS="-DHAVE_DVB_API_VERSION=3 "$DBGFLAGS
LDFLAGS="-lpthread -lrt"
$CC $CFLAGS -c -o vtuner-network.$ARCH.o vtuner-network.c
$CC $CFLAGS -c -o vtuner-dvb-3.$ARCH.o vtuner-dvb-3.c
$CC $CFLAGS $LDFLAGS -o vtunerd.$ARCH vtuner-network.$ARCH.o vtuner-dvb-3.$ARCH.o vtunerd.c
$CC $CFLAGS $LDFLAGS -o vtunerc-test.$ARCH vtuner-network.$ARCH.o vtuner-dvb-3.$ARCH.o vtunerc-test.c

Zitat

Originally posted by rmie

Hi, find below the patched version

Roland

Roland, thank you very much!

But now I know what the problem is... hope I'm not saying stupid things here...

When you compile the vtunerd.mipsel for dm800 you do it with 'have_dmm_tuner' (vtuner-dmm-3.c)... but what i want to share is the second tuner, that is usb dvb-t (vtuner-dvb-3.c) attached to dm800. Could you build the vtunerd.mipsel in this way?

Zitat

Originally posted by SrbastianM
sorry.. offtopic, but what do you want to do with your popcorn hour?
It does not have a tuner, does it?

Edit: just saw your link... nice

ciao

Basti

Alles anzeigen

The popcornhour doesn't have a tuner but you can use one if you can compile drivers for 2.6.15 kernel. I would like to use vtunerd on popcorn, but as you see, I encounter some difficulties.

I downloaded the version from 14.09 and I compiled vtunerd for Popcornhour A110 (nmt with linux). Everything was okay in loading the driver and I launched vtunerd 1 0 0 0 0 & on nmt.

the output is like this:

/opt/sybhttpd/localhost.drives/HARD_DISK/Apps # ./vtunerd.mips 1 0 0 0 0 &
[6546 vtunerd.c:38] debug: try to init 1 tuner(s)
[6546 vtunerd.c:44] debug: init hardware adapter 0, frontend 0, demux 0, dvr 0
/opt/sybhttpd/localhost.drives/HARD_DISK/Apps # [6546 vtuner-dvb-3.c:44] info: F
E_GET_INFO dvb-type:2 vtuner-type:4
[6549 vtunerd-service.c:88] info: anon stream socket prepared 40
[6549 vtunerd-service.c:240] info: control socket bound to 35890
[6549 vtunerd-service.c:88] info: anon stream socket prepared 41
[6549 vtunerd-service.c:255] info: waiting for connect control:35890 data:41940
listen:40
[6550 vtunerd-service.c:21] info: autodiscver thread started.
[6550 vtunerd-service.c:33] info: waiting for autodiscover packet ...
[6551 vtunerd-service.c:154] debug: tsdata_worker thread started.
[6550 vtunerd-service.c:37] info: received discover request
[6550 vtunerd-service.c:40] debug: Session 0 device type 4 is idle
[6550 vtunerd-service.c:52] info: Answered discover request with session 0
[6550 vtunerd-service.c:55] info: waiting for autodiscover packet ...
[6549 vtunerd-service.c:103] debug: setsockopt TCP_NODELAY 1 successful
[6549 vtunerd-service.c:109] debug: setsockopt SO_KEEPALIVE 1 successful
[6549 vtunerd-service.c:116] debug: setsockopt TCP_KEEPIDLE 15 successful
[6549 vtunerd-service.c:123] debug: setsockopt TCP_KEEPCNT 2 successful
[6549 vtunerd-service.c:130] debug: setsockopt TCP_KEEPINTVL 2 successful
[6551 vtunerd-service.c:103] debug: setsockopt TCP_NODELAY 1 successful
[6551 vtunerd-service.c:109] debug: setsockopt SO_KEEPALIVE 1 successful
[6551 vtunerd-service.c:116] debug: setsockopt TCP_KEEPIDLE 15 successful
[6551 vtunerd-service.c:123] debug: setsockopt TCP_KEEPCNT 2 successful
[6551 vtunerd-service.c:130] debug: setsockopt TCP_KEEPINTVL 2 successful
[6549 vtunerd-service.c:330] debug: MSG_SET_VOLTAGE: 0x2
[6549 vtunerd-service.c:330] debug: MSG_SET_VOLTAGE: 0x2
[6549 vtunerd-service.c:330] debug: MSG_SET_VOLTAGE: 0x2
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1
[6549 vtunerd-service.c:310] debug: MSG_READ_BER: 0
[6549 vtunerd-service.c:318] debug: MSG_READ_SNR: 0
[6549 vtunerd-service.c:318] debug: MSG_READ_SNR: 0
[6549 vtunerd-service.c:314] debug: MSG_READ_SIGNAL_STRENGTH: 45879
[6549 vtunerd-service.c:330] debug: MSG_SET_VOLTAGE: 0x2
[6549 vtunerd-service.c:297] debug: MSG_SET_FRONTEND
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtunerd-service.c:310] debug: MSG_READ_BER: 0
[6549 vtunerd-service.c:318] debug: MSG_READ_SNR: 43433
[6549 vtunerd-service.c:318] debug: MSG_READ_SNR: 43433
[6549 vtunerd-service.c:314] debug: MSG_READ_SIGNAL_STRENGTH: 33591
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtunerd-service.c:310] debug: MSG_READ_BER: 0
[6549 vtunerd-service.c:318] debug: MSG_READ_SNR: 43433
[6549 vtunerd-service.c:318] debug: MSG_READ_SNR: 43690
[6549 vtunerd-service.c:314] debug: MSG_READ_SIGNAL_STRENGTH: 17207
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtunerd-service.c:302] debug: MSG_GET_FRONTEND
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor:
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211 561
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211 561
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211 561
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211 561
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211 561
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211 561
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211 561
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211 561
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211 561
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211 561
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211 561
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211 561
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211 561 57
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211 561 57
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211 561 57
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211 561 57
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211 561 57
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtunerd-service.c:310] debug: MSG_READ_BER: 0
[6549 vtunerd-service.c:318] debug: MSG_READ_SNR: 43690
[6549 vtunerd-service.c:318] debug: MSG_READ_SNR: 43947
[6549 vtunerd-service.c:314] debug: MSG_READ_SIGNAL_STRENGTH: 823
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211 561 57
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211 561 57
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211 561 57
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211 561 57
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211 561 57 17
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211 561 57 17
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtunerd-service.c:297] debug: MSG_SET_FRONTEND
[6549 vtunerd-service.c:330] debug: MSG_SET_VOLTAGE: 0x2
[6549 vtunerd-service.c:297] debug: MSG_SET_FRONTEND
[6549 vtunerd-service.c:302] debug: MSG_GET_FRONTEND
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211 561 57 17
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211 561 57 17
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211 561 57 17
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211 561 57 17
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 18 0 211 561 57 17
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 18 0 211 561 57 17
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 18 0 211 561 57 17
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 0 211 561 57 17
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 0 211 561 57 17
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 0 211 561 57 17
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 0 211 561 17
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 0 211 561 17
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 0 211 561 17
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 0 561 17
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 0 561 17
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 0 561 17
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 0 17
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 0 17
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 0 17
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20 17
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20 17
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20 17
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent: 20
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after: 20
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtuner-dvb-3.c:143] debug: hw_pidlist befor: 20
[6549 vtuner-dvb-3.c:146] debug: hw_pidlist sent:
[6549 vtuner-dvb-3.c:183] debug: hw_pidlist after:
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtunerd-service.c:306] debug: MSG_READ_STATUS: 0x1f
[6549 vtunerd-service.c:310] debug: MSG_READ_BER: 0
[6549 vtunerd-service.c:318] debug: MSG_READ_SNR: 43690
[6549 vtunerd-service.c:318] debug: MSG_READ_SNR: 43947
[6549 vtunerd-service.c:314] debug: MSG_READ_SIGNAL_STRENGTH: 21304

When I try to tune a dvb-t channel, the usb tuner led lights up (like tuning) but I have no image on dm800 and time to time I get the 'no data on transponder. timeout reading PAT' error message.

In lamedb I manually added correctly the frequency and parameters for the transponder and also the channel.

eDVB services /3/
transponders
eeee0000:012f:0003
t 738000000:0:1:1:2:1:1:0:2:0
/

0001:eeee0000:012f:0003:1:0
TVR1
p:TVR

Do you have any idea why I have no image on dm800? (on nmt, the tuner works perfect, see http://www.networkedmediatank.com/showthread.php?tid=26368 )

Zitat

Original von rmie

yes I can, but can last a few days

It would be great indeed! Thanks a lot!

rmie,

I don't have the tools to compile vtunerd, could you please help me with this?

Hi Tweek,

I'm trying the same with Cinergy T2 usb dvb-t, but I have some problems, as described before. Could you please share the steps you've done in order to have the dvb-t usable?

When trying vtunerd.mipsel 1 1 0 0 0 & I receive the following:

root@dm800:/tmp/vtuner# ./vtunerd.mipsel 1 1 0 0 0 &
root@dm800:/tmp/vtuner# [1078 vtunerd.c:397] debug: try to init 1 tuner(s)
[1078 vtunerd.c:403] debug: init hardware adapter 1, frontend 0, demux 0, dvr 0
[1078 vtuner-dmm-3.c:53] info: FE_GET_INFO type:2
[1078 vtuner-dmm-3.c:64] error: DMX_SET_SOURCE failed for /dev/dvb/adapter1/demux0 - Invalid argument
[1078 vtunerd.c:405] error: failed to init hardware (adapter 1, frontend 0, demux 0, dvr 0)

Do you have any sugestions?