Posts by musogeek

The default skin on an image is usually a good skin to stick with - this would explain why it is being used as the default skin in the first place, because it is popular and works well. I often experiment with skins, but tend to switch back to the one that I started with!

I used to be into CB when I was young - had a 1/4 wave aerial on a scaffold and had a nice set of boosters and high mid and low channels- AM, FM - etc - was great fun!

my mrs calls the motor dish - 'the ugly bit of metal attached to the wall!'

I think you need to look at the ip address of the http port - it is default at 80, not sure about the openmips but if it is something different in the webinterface you need to change that setting accordingly in the dbedit configs.

on the dbedit configs - you can go to the ftp part of the options and set more options for resetting the box- just a case of experimenting - I haven't used dbedit with openmips, but worth messing around!

sounds like you are doing it right - next thing would be your right boot! - I would maybe look at factory reset - or deleting everything in /var/tuxbox - then try again.. keep trying - from what I have seen in your posts s1m0nw if anyone would get it sorted it is yourself!

do an init 4 command, then delete the existing files, then replace with the settings you are trying to load, then do an init 3 command. I usually delete the lamedb and files ending with .tv and .radio in the /etc/enigma2 folder, and then paste the ones from the downloaded settings in their place - the satellites.xml file in /etc/tuxbox would be replaced with the one in the settings list too - then do an init 3 command - try rebooting the receiver as well

just type them in!

in a telnet session - log in to receiver - when you are messing with changing files you can do an 'init 4' command, which will allow you to edit stuff while the receiver is suspended, and when you are done, do an 'init 3' command which should reset it allowing you to use the new configuration.

Not tried this on the openmips but it is quite generic.

I know you sorted it, but EaseUS Partition Master 9.1 is what I use for this - It is a great Windows tool, and I have used it many times to solve the problem you had.

http://www.partition-tool.com/download.htm

Just because you are having problems with this receiver, it doesn't mean that the GigaBlue is a bad receiver. It is either faulty, or more likely you are not setting it up or installing the firmware properly. These are good receivers, and are well supported.

When these boxes are sold, they are sold as being suitable for those who have some linux/telnet/ftp and networking knowledge. If you haven't then you need to do a little bit of reading. If you are not willing to slow down a bit and get your foundation knowledge boxed off, then you will get frustrated. If you try to exercise before warming up, then you will injure yourself...

Once you are there with this box, then you will like it alot - I have a gigablue - never had an issue with it really.

If you don't want to spend the time learning then you might be better going back to the closed source receivers.

So does the law require ISPs to block out VPN access as well? I bet the VPN providers will be laughing all the way to the bank. Unless they have found a way to detect traffic passing throuh - and I have found this article to address this question

http://www.bbc.co.uk/news/technology-17922214

will it ever end - this cat and mouse game!!??

can't see much wrong with your post to be honest! - just boxkey and ip and passwords which i blocked out. We appreciate your account on what you did to get this working as it may help others. To answer the question about the card deactivating, with an MTV Unlimited card, the entitlements will last for the period of your subscription, so you won't need to worry about enabling EMMs in your configs (you can disable them if you like) until you renew your card.

Not familiar with tvdheadend - I can see you are using it to connect to Oscam - I see you have enabled newcamd and CCcam protocol in Oscam, what protocol is it using to connect with Oscam? Also I can't see that dvbapi in Oscam will have any use in updating your entitlements as this is really only if your card is being read in a receiver using Oscam - I think in your setup it would be about how tvheadend and Oscam are speaking to each other that dictates how successful it is in updating entitlements.

I managed to update entitlements on an MTV Unlimited card being read in Oscam connected to CCcam client, and seemed to have better success with CCcam protocol rather than newcamd, although I had only sent the renewal code to the MTV website about half hour before it updated in Oscam with CCcam protocol, If I had stuck with the newcamd and been a bit more patient, it might have worked, but I won't know that until the next time.

In my Oscam setup for the MTV card, I didn't use an ecm whitelist, also I kept it on VH-1 Classics and it updated on this channel.

Looks good - looks like they can run Ubuntu - although I only had a quick butchers - first one to put a server on it wins....:dribble:

edit - raspberry pi can run linux but don't think the alternatives do - running Android 4.0 - still - only a matter of time!

All posts on the forum should be preceded by an intro post here;
Introduce yourself here...

Or in all likelyhood, they would get overlooked. As my folks always said - never speak to strangers.:cold:

try using drfox's configs but change part of the oscam.server back to how you had if before, as your card seemed to be regognised in oscam ok with that

Protocol = smartreader
Detect = cd
Device = 003:002
mhz = 375
cardmhz = 375

put the above back in your oscam.server card entry, replacing the equivalent existing entries from drfox's configs.

You have a PC server running Ubuntu Oscam and Digitalalb card that is showing entitlements and when you go to a channel on your receiver, it is showing that the ecm reqest is ok, but you are getting a blank screen, I am guessing that the card is being read in a card reader attached to your PC (this is a guess because you haven't said it is the case), and you are using newcamd or newcamd protocol somewhere along the lines.

What I have worked out is detective work, because you are not being that clear. You get the best support in this forum, but only if you can be more clear about what is happening. So far we don't know how your server is connected to your PC, we have no idea of your existing Oscam config files, we don't know if you are Using CCcam, we don't know what receiver or image you have because you haven't put any information in your profile.

We like to help in this forum, but we need your help so we can have a better understanding of your problem.

We might be able to help if you told us what your problem actually is. What aspect of your setup isn't working? You need to tell us what your problem is.

http://linuxsat-support.com/os…at-how-do-i-maintain.html

have a read of this - hope it helps.

never used oscam.whitelist - but some info on the Oscam wiki

OSCam/en/Config/oscam.whitelist