Great news - thanks to the ViX team for working with what you have and presenting it to us.
http://linuxsat-support.com/vu…openvix-3-0-540-beta.html
Uploaded here for the benefit of our members who are not members of the 'you all know where' forum, and for those who don't know where!
Happy xmas - please post an introduction, you are more likely to get help if you are not a stranger:linuxsat5:
sounds to me like you are just getting now and next and need to get the CrossEPG plugin - download this from the BH plugin downloads, and then you need to set it up - you should set it to save on usb or hdd rather than internal flash, you can set it to download rytec updates, or opentv 28.2e updates
you could always download the backup images for the solo here
several have been done by our resident Ten Below - that will have some of the stuff already installed.
BlackHole has its own UK epg service built in, but I found CrossEPG to give better coverage.
give me an hour and i will see if i can compile it.
http://linuxsat-support.com/os…sion-oscam.html#post89796
7982 is the latest - you want the arm-coolstream one - not sure if it is compiled with the support for pcsc or smargo but worth a go - not tried it myself I have the one I posted working fine for 2 weeks 100% stable.
not sure what the problem is cause i only compiled mine a couple of weeks ago and I followed this guide to make sure it is sending people down the right track, unless something has changed with the image, packages or sources etc - you could always try the binaries I created, pick up the guide from after the compile part, create the folders as stated, and move these into the folders and change attribs as stated.
the requirement to install these packages was already stated as part of the guide, under the heading "First, you need to get your packages" Have you missed anything else out?
all should work if all instructions are followed completely - did you note this?
Compile Oscam (note the two dots after the 5th line are there because they need to be).
I'm planning on getting one of these today and tranfering my setup from pc tower to this, I run 2 instances of oscam now on the pc one for cache only and one for shares, may need some help in getting 2 instances running?
Shouldn't be a problem especially as the new models have double the RAM - consider it is pretty much the same as having oscam running on a debian server, not tried it but sure it is possible. If you can't manage then consider the Raspberry Pi is so cheap you might want to just get 2 Raspbery Pi's!
Great tutorial.
I think that I have setup the Pi correctly to run oscam. I only have oscam.config and oscam.server in usr/local/etc. Is this correct.
Thanks in advance.
There are a number of config files you could have in usr/local/etc
oscam.conf is the most important because with this you can activate the webinterface by adding the following;
[webif]
httpport = 8888
httprefresh = 5
httpallowed = 127.0.0.1,192.168.0.0-255.255.255.255that way you can either access the oscam webinterface from a web browser either on the raspberry pi gui http://127.0.0.1:8888 or from a browser on a remote PC in your lan http://192.168.x.x:8888
with the webinterface you can then add readers, users, edit configs etc.
oscam.conf, oscam.user and oscam.server are probably the 3 most important, but you also put the srvid, services, provid, cert, ac and one or two others in here.
Can anyone tell me why 1 cline would be more stable than another. Both from the same peer. ECM time are higher on one and the other cline ECM times are lower and more stable.
Thanks in advance
If your peer gives you 2 clines it may be the case that they are running 2 servers, and if that is the case then each request might be going to a different card for each cline. One of the servers could also be working differently as well (cache exchange for example) If you have 2 clients and you have one of the clines on each client then it might be that the issue is the way your client or cam is handling the requests. It may also be the case that the origin of each cline is different. A lot of people are experimenting with vps as well, so maybe one of the lines comes from a different geo location.
If you have a look at the CCcam or OSCam web interface for each line, you will get an idea of what is on the server.
If both clines were from exactly the same server with the same settings, and are both in the same client, then there would be no point of being given 2 clines.
read back thats exactly what i wanted
not people slinging mud
I don't see any mud being slung, think I stand by my last posts on here that this thread has been an account of people's high ecm's on sly UK without any real disclosure from those with the problem as to what may be causing it, so without the information about the setups, amount of peers, configs, etc then it will remain an account of people's high ecm's rather than a solution to the problem.
sWeRvEr - not sure if it is fair to say that people who are not affected shouldn't take part. Clearly not everyone is affected so as axegrinder and dbxxx have stated, maybe it would be useful to find out why those who are affected are. This is not being unhelpful, they are suggesting that more is disclosed about the way the servers are set up, so then maybe something in common can be found, which could lead to a reason being found as to why this is happening.
Maybe using Oscam could be a better option if he wanted more control over what services he gives and receives. You can set rules in oscam.services, name the rule and apply it with the 'services =' flag for readers and users.
I have always had issues every now and again with EPG updates keeping the receiver awake. I think using OpenTV you are more likely to see this, you could try using rytec providers instead, because I think this does the update while the receiver is in standby and for some reason the OpenTV can wake the receiver up, not all the time, but never found a 100% reason why it happens.
I prefer to use OpenTV - so I have used various ways to put it back in to standby. The method I use at the moment is menu - setup - system - AutoShutDown settings, and I keep AutoShutDown disabled, but enable action after activity - set this at 120 minutes, and for it to go in to standby. This will put the receiver in to standby after a 20 second warning if you haven't pressed anything on the remote for that length of time, can get a bit annoying if you don't channel hop much but it is ok for me.
There is also a plugin called Buyukbang from the ViX feeds - with this you can run a daily scheduler that returns the receiver to standby at any given time each day, or you can schedule it to reboot after an EPG update with the same tool and return it to standby - not fully tested this plugin but it is worth giving it a go.
I am a newbi. The only way to learn is to ask. But thank you anyway.
No problem at all matey that is what we are here for, just that a lot of your questions have already been asked by others, and the answers are already here on the forum, so although we have no problems answering questions, it can help you a lot if you have a look through the forum first, and the search tool is a really good way to startbeer10
You have a lot of questions! How about using the search tool at the top right hand...
Anyway if you are worried about memory you might want create a swap file, which will be utilised if your physical memory gets full to free up some RAM.
This can be done from the setup menu which differs from image to image - but if you have TSpanel installed you can do it from TSpanel Tools-2 - swap manager.
If you have any plugins installed you don't need, then remove them, and a daily reboot can also help.
http://linuxsat-support.com/vu…-duo-backup-musogeek.html
another backup to try - just install it and put your line in CCcam.cfg and should be good to go.
Thankyou for in advance for agreeing to the forum rules and posting here Introductions before taking further part in the forum.
you need to install CCcam so from the plugins menu, select TSpanel, then select 'Addons' then select 'Linuxsat_support_addons' then find cams-blackhole, then select CCcam 2.2.1 or 2.1.3 or 2.3.0 depending what is there and what you want (better choose 2.1.3 or above). This will install your cam.
you then need to activate it, think you do this by pressing the blue button I think, and left and right to get to the default cam (the one you downloaded) and press ok.
To add clines, again use FTP, navigate to /etc/CCcam.cfg, and in an editor, add your line/s to this file, and save.
