Open GoogleCodeExporter opened 9 years ago
I'm sure that vtunerc is mounted on /dev/dvb/adaptor0/frontend0 since I can see
audio picture with szap + mplayer combination. It's just perfect for freeview
channels. Could't tried scrambled channels since I could not have audio/picture
on my OpenPLi. Did you have any chance to test XSHM ?
BTW, can I learn in PLi forum nick :)
Original comment by buyukb...@gmail.com
on 6 Feb 2012 at 10:13
Do you: git pull
and recompile the OpenpliPC osd branch because it is often updated, and first
version doesn't support OpenGL just XSHM but the latest version now support
also OpenGL.
Original comment by mebep...@gmail.com
on 6 Feb 2012 at 10:14
Yes, I created openpli OSD branch from scratch last night. I both tried OpenGL
and XSHM. OpenGL is not still working on VM, it's killed immediately This is
completely a VM related issue. But XSHM works, I got OSD, I saw a logical
signal value on the skin without audio or picture. Of course I can install and
use directly to my PC instead of VM, but this is not the target. I want to
prepare easily shareble VM images with working and ready to use OpenPLi
installed for people witout any linux and compile knowledge. I'm sure there is
something very small is overlooked since I got audio/picture with usb tuner
with XSHM? BTW, audio/video is not the only problem, as I said before, channel
scanning also cannot find no channels. I did nothing special:
1- compiled openPli from scracth.
2- started vtunerd and vtunerd.
3- I saw audio video with szap+mplayer
4- restarted vtunerd and vtunerd.
5- Copied my settings from VU+ to OpenPli.
6- Changed tuner setting to VTuner.
7- Changed xine.conf as XSHM
8- Started OpenPli
Is there any missing step or setting ?
Original comment by buyukb...@gmail.com
on 6 Feb 2012 at 11:10
Hi,
I think that the goal here is not to troubleshoot your OpenpliPC installation.
Please post your questions on Openpli forum where people can help you.
For me issue #13 on vtuner is now solved since I didn't change anything in the
source code, I just compile properly the vtunerc and vtunerd towards VU+
include files for you.
Mebepi.
Original comment by mebep...@gmail.com
on 6 Feb 2012 at 11:57
Yes you're right. At this point I'll try other dvb applications to be sure
about the vtuner since to verify channel scan and channel change. I just only
one channel in my szap config file (since manually adding channels to this file
is a bit difficult), then I'll try to make openpliPC work.
These are my last question, could you please kindly answer them as a final note
:
1- BTW, you changed no code? I previously tested vtunerd.mipsel files given in
this site, and you can find one in the above messages given by Honza. None of
them worked with szap. So I assume only gcc that you used made the difference
in my szap+mplayer tests? Right ? Is this the same for your XTrend ?
2- I think you used vtuner-dmm-3, not vtuner-dvb-3? So you did't changed make
config ?
3- Should I do anything special to compile vtunerc for DVB API 5? I'm using
ubuntu 11.10 and I assume that DVB API 5 exist on ubuntu 11.10. Isn't the one
that Honza provides the same ?
Thank you very much for all you helps and precious efforts !!!
Original comment by buyukb...@gmail.com
on 6 Feb 2012 at 12:23
Hi,
1-
What I did is:
- Create a full Openpli environment for Vuplus on my build PC.
- I have the crosscompiler installed on my build PC.
- I create a full new bunch of file to build vtunerc/vtunerd based on mipsel
one.
To do so I duplicate the ./build/mipsel into ./build/vuplus
Edit file: ./build/vuplus/Makefile and change:
CFLAGS=-fpic -DHAVE_DVB_API_VERSION=5 -DHAVE_DREAMBOX_HARDWARE
$(INCLUDE-$(ARCH)) $(INCLUDE2-$(ARCH)) $(DBGFLAGS)
Edit file: Make.config
# define the CC for target vuplus
CC-vuplus=/home/mebepi/vuplus/mipsel-unknown-linux-gnu/bin/mipsel-unknown-linux-
gnu-gcc
CXX-vuplus=/home/mebepi/vuplus/mipsel-unknown-linux-gnu/bin/mipsel-unknown-linux
-gnu-g++
INCLUDE2-vuplus=-I/home/mebepi/vuplus/build-vuduo/tmp/sysroots/vuduo-oe-linux/ke
rnel/include
INCLUDE-vuplus=-I/home/mebepi/vuplus/build-vuduo/tmp/sysroots/vuduo-oe-linux/ker
nel/arch/mips/include
The main point here is that I pickup the kernel include and arch/mips include
file form the folder where I compile an openpli image for Vuplus (I choose a
vuduo image).
This is the goal of INCLUDE and INCLUDE2 parameters.
After having compile towards those include file everything is working fine, so
yes I compile with vtuner-dmm-3 (answer to question 2), nothing is changed
compared to mipsel standard compilatione except the include files.
I do the same operation for xtrend and compared both compiled vtunerc and
vtunerd md5sum and they are the same, so the headers are the same both for VU+
Duo and Xtrend ET-9x00. I should check with VU+ Ultimo to see if the result is
the same.
But since I don't own VU+ hardware this is not really usefull for me.
3- On Unbuntu you need to change the include file location to:
Follow the tuto: http://wiki.nessiedvb.org/wiki/doku.php?id=install_vtunerc
But replace the KDIR command mentioned in the tuto with:
make KDIR=/usr/src/linux-headers-`uname -r`
I already provide to Honza all the informations to successfully build a version
for VU+ and Xtrend.
Mebepi
P.S.: if you don't know how to build a full openpli image please check this:
http://users.telenet.be/spstefansp/openpliubuntu.html
But be careful you need to use Makefile-2.1 and not Makefile-2.0 like in the
explanations.
The hardest part is to find all the required packages to successfully build the
image, since some mirrors are temporarily down or sometimes no longer available.
Original comment by mebep...@gmail.com
on 6 Feb 2012 at 1:23
Thank you very much again for the complete answer ! I have already openpli
compile environment, it seems as I just need to modify make and make config
files as you suggested. I'll try to compile vtuner this evening.
Regards...
Original comment by buyukb...@gmail.com
on 6 Feb 2012 at 2:05
Oh, few days I'm out and so nice progress. Good job Mebepi!
In day or two I should be back and then we can commit all necessary changes for
build system to get working binaries for VU+/ET boxes.
Honza
Original comment by jpetrous
on 6 Feb 2012 at 8:42
[deleted comment]
@Mebepi
I compiled vtunerd for VU this evening, with the suggested Make/ Make Config
modifications. My compiled binaries gives the same with the ones that you
attached above. Here are the results:
1- szap+mplayer gives audio + video with a manually created channels.conf.
2- w_scan finds no channel, so I could not create a channels.conf. It locks to
the frequencie,s but cannot find any channel.
3- I get No audio/video on PliPC with imported settings. EPG is OK. Signal is
OK. BER always shows numbers like 31 strangely.
4- PliPC cannot find any channels in channel scans. It locks to the
frequencies, but cannot find any channel.
5- Finally scan with the Mythtv cannot find any channels in channel scans. It
locks to the frequencies, but cannot find any channel.
@Honza,
You had suggested to me to use szap as the simplest test tool. What are the
differences of other DVB apps when compared to szap? Do you have any
explanation that my tests 2,3,4,5 fail while only 1 succeeds? Any suggestion
for the further test cases to prove vtunerd is working with no problem or not.
As I said before, I'm using a Virtual Machine (ubuntu 11.10) on my Windows 7.
Do you think this is cauesed by a VM usage? May be a second VU+ user should
check the results ??
Regards...
Original comment by buyukb...@gmail.com
on 7 Feb 2012 at 9:26
[deleted comment]
Still no progress here :( I think there is something wrong for vu+ here which
is not PLi specific.
I'm found following the error in PLiPC logs : "DMX_SET_SOURCE failed! - Invalid
argument"
I included problematic part raising the error when tunning to a channel below,
you can also find full logs attached.
---------------------------
OURSTATE: tuning
allocate Channel: res 0
[eDVBCIInterfaces] addPMTHandler 1:0:1:1:1:FFFF:1A42EBC:0:0:0:
allocate demux
DMX_SET_SOURCE failed! - Invalid argument
-----------------------------
Original comment by buyukb...@gmail.com
on 12 Feb 2012 at 12:52
Attachments:
Any comments?
Original comment by buyukb...@gmail.com
on 21 Feb 2012 at 1:13
Hey guys, first of all: what an awesome project. I'd just love to have
tvheadend use my dreambox as a dvb tuner!
It seems like my setup is almost working, but I get the "no scan results"
issue, apparently.
I have a: dm800se running OpenPLi that runs vtunerd.mipsel (20120104-r2) +
xbmc running on an arch linux machine (x64) running vtunerc.ko + vtunerc.x86_64
which i compiled myself using the kernel 3.3 quick-patch found in issue 18.
Communication seems ok, i have tried "vtunerc -f s" and "vtunerc -f s2" (others
(-f S or -f S2) do not connect successfully, as my tuner type = 9)
So the problem at this time is: i cannot scan for any channels (tried using
w_scan, passing -D1u, -D2u, ... for diseqc switching, don't know it this is
supported?).
I tried manually adding channels to channels.conf and tuning with szap, but
this does not seem to LOCK... (will try this again)
btw: is there a way to convert Enigma's channels to a channels.conf ?
Also, if there's know issues causing this behavior, on which I could help? I am
an embedded C programmer, so I might be able to help a little.
Original comment by maxime.v...@gmail.com
on 17 Apr 2012 at 6:52
Ok, I just read the line "Original Dreambox API is supported, but only up to
August's 2011 DVB drivers!". I suppose this explains my troubles. I someone
could point me out where I should look for improvements, to get it work on the
new Dreambox API? Is there any documentation about the dreambox-API?
Should I look in the vtunerd-part, in vtuner-dmm-3 ?
I know very little about linux-dvb, so I'll have to do some research first.
best regards
Original comment by maxime.v...@gmail.com
on 17 Apr 2012 at 10:32
Maxime, If you can test against some older kernel (non 3.3), please do it. As
you could notice, I did 3.3 kernel patch blindly, so it is more then possible
it consists of some bugs and this is a reason why it is not working for you.
Original comment by jpetrous
on 17 Apr 2012 at 7:38
jpetrous, everyone,
I have tried using a 3.0.x kernel, and scanning works now. (so using a recent
OpenPLi image on my dm800se. I still have to check which driver version this
image is using, exactly)
I will look into the new 3.3.x kernel dvb interface, and hopefully come up with
a fix.
Best regards
Original comment by maxime.v...@gmail.com
on 19 Apr 2012 at 12:01
I have also a lot of problems with getting vtunerd on my STB.
I'm using the stv090x driver. With the szap utility I got a lock but no tsdata.
Now I'm trying the openpliPC project.
On some channels in e2 I see a PID list and on a lot of channels I see nothing.
The ioctl(hw->demux_fd[j], DMX_SET_PES_FILTER, &flt); is failing also with
"invalid argument". If I set the PID hardcoded to 0 the ioctl succeeds.
The attached log shows what's going wrong. The DEMUX FAILED logging is custom
added.
Original comment by leonleij...@gmail.com
on 30 Apr 2012 at 12:09
Attachments:
Issue 34 has been merged into this issue.
Original comment by jpetrous
on 18 Feb 2014 at 7:22
Original issue reported on code.google.com by
buyukb...@gmail.com
on 13 Jan 2012 at 11:54