Posts by s3n0

2.1.200506

Minor changes in the source code.

Fixed a bug in the non-existent Python module "requests", when the plugin refused to load into the list in the Plugin-MENU:

- it's a remnant of a function from previous source code

- the "requests" module was used to test the alternate function

Design:

- the list of selected satellites in the configuration menu has changed to abbreviated text with the number of selected satellites together

- added unicode circle character (emptied / filled) in the selection of satellite positions, for their better visibility

Localization:

- added missing dot in one sentence, in translation files

- improved Russian language (by FRAP)

I've read yet, I don't know exactly where, about the guy which had this similar problem. Oscam did not work when launched with the system. The whole Oscam had to be restarted immediately after starting the whole system. Then it always worked fine :). I don't remember where I read it here.

The cause could be anything. For example, some drivers or libraries or access to an external drive - until they were booted up, Oscam didn't discover them and fooled around. It's hard to say what was going on there in this case of problems. Maybe the creation of the temporary system folder "/tmp" (usually as a "volatile" partition of RAM-disk) was delayed and maybe Oscam needed to work on it. It's really hard to say where the problem came from. Maybe the Oscam start should be moved via init.d sript to the last position ("/etc/rc3.d/S99softcam" instead of the example "/etc/rc3.d/S20softcam"). Or make a script that delays the launch of Oscam by one minute :).

ygurbuz:

So I need to see the debug-log file :-(. Stop Enigma via Shell, using "init 4" and then start debugging (in the case of OpenVisionE2 everything should work as in OpenPLi, but I don't know for sure) - i.e. run the plugin update. When the plugin will updated, send the resulting debug-log file ("/media/hdd/enigma2.log") to a private message - but before restarting Enigma - GUI !

init 4    # stop the Enigma2
ENIGMA_DEBUG_LVL=4 enigma2 | tee /media/hdd/enigma.log     # start the Enigma2 (+ make a debug-log file)

However, this is probably a forgotten "import requests" line again. Since in OpenVisionE2 this module is also not the default part of Enigma and must be installed from the feed. After installing the new version, a plugin error will be displayed and it will not be loaded. I fixed it in the new version 2.1.200506.

ygurbuz:

Which Enigma2 distribution do you use and which version ?

Which set-top box do you own ?

Do you mean when updating the plugin in the MENU ChocholousekPicons plugin? Or do you think when updating Enigma2 ?

Similar problems once existed in the case of .deb packages, but not in the case of .ipk.

ygurbuz:

Ciao. I'm sorry, but I don't understand you (even after translating your question from Italian). Please use Google Translator if you do not speak English well and describe your problem in more detail. Thanks.

I probably won't succeed, as you haven't written yet what you've done before, since it started to work correctly :).

Genaro75:

But still everything works correctly. This is not a mistake. It does not matter at all that the list of satellites is outside the dimensions of the configuration window.

antrabe:

These are just versions and there is no connection between them. It is always just a version, also consisting of a date. If the plugin has a different date than the current date, it does not mean that the plugin is old :). If the picons still have a different date than the plugin, it does not mean that the picons are old. This is just an informative build version. Picons are updated by Chocholousek - about once a week.

Genaro75 :

Hi. I know about this, but I never considered it a mistake, as I never assumed that anyone would need to check all satellites for updating :).

I can adjust this in future plugin versions so that only the number of selected satellites is displayed. Ie. that only the value of one number will be displayed - the number of selected satellites. After entering the satellite configuration, of course, this list of selected satellites will be displayed in 2-3 lines.

Each SKIN and Enigma can have different configuration widgets. So I can't influence it. Only if I programmed my own configuration widget or just some new elements to select in the configuration MENU, but that's also a lot more work :).

houba2007:

Since the debug-log file is not complete, the system probably crashed ? If so, then there should also be a crash-log file. I would also like to see him if possible. Thanks.

stephan94:

Yes, this "requests" Python module is unfortunately not included in all Enigma2. However, I do not use it. Unfortunately, I tested something and there remained "import requests" in the source code. So if this module does not exist in your Enigma2, then this error will pop up. Theoretically, it should be possible to install this module into Python in Enigma2 from the feed server:

opkg update
opkg install python-requests

In future versions, I will add a dependency to IPK control-scripts or delete "import requests" from the source code.

Hello. Um, maybe there's not enough free space on the flash drive ? A debug-log file and a crash-log file would help me. For OpenATV, both files should be in the folder "/home/root/logs". Send them to me in a private message (due to possible private data in LOGs). Thanks.

Hello.

Try, for example, the binary file Oscam, built by @juli13, from here: Oscam-EMU Mipsel & ARM (mipsoe20 or openpli40 or mips-emu-static-lib). Your set-top box contains a mips32el processor (so-called "mips" family), so use the binary for that processor.

(1) ps | grep -i "oscam" ...or... ps aux | grep -i "oscam" - as first, find the name and location of your current Oscam binary file

(2) /etc/init.d/softcam stop - stop current Oscam

(3) Now, download the new binary from the internet and replace the original binary file on your set-top box (before it, I recommend to backup original binary file, e.g. renaming to "/usr/bin/oscam-emu-backup").

(4) Copy the new binary to the original location (for example with the helping of FTP client in Total Commander).

(5) chmod a+x /usr/bin/file_name - set the execution rights attribute for sure again

(6) /etc/init.d/softcam start - start new Oscam

You can try setting the oscam process priority for the CPU, to "nice = -1": http://www.streamboard.tv/wiki…en/Config/oscam.conf#nice

You can also create a LOG file not only in TTY but in a file (logfile = /tmp/oscam.log "): http://www.streamboard.tv/wiki…Config/oscam.conf#logfile and then when crasnutí, look at the file to see if there will always be the same cause before Oscam freezes.

Also, you didn't show the configuration of your Oscam (of course, with the deletion of private data - login name, password, IP address, etc.), so it's hard to advise you.

Like I said ... I recommend starting a new topic with a new question. Your freeze is a device error (drivers, hardware, Oscam version, etc.).

What source does your Oscam come from ? You can try another Oscam build from the internet for your mips32el CPU architecture on your device.

I'm adding a shell-command to detect the active OscamWebif. If OscamWebif is not active, then Oscam restarts. However, in my opinion, this is not the solution to your problem ! You should find out why Oscam freezes in your receiver and solve the problem !

/usr/bin/wget -qO- "http://USER:PASS@127.0.0.1:8888" > /dev/null; [ $? == 0 ] || /usr/bin/sh /etc/init.d/softcam restart

...or :

if ! /usr/bin/wget -qO- "http://USER:PASS@127.0.0.1:8888" > /dev/null; then /usr/bin/sh /etc/init.d/softcam restart; fi

If you do not use a password for OscamWebif, delete the USER:PASS@ section.

Do you have a suitable Oscam for your set-top box ? Each Enigma, the Linux kernel including modules and libraries, each processor (architecture), may require a different Oscam.

What set top box do you have and which Enigma ? Do you have the latest Oscam ? If the Oscam process freezes, it is a hardware or system error.

In this case, it is not a freezing of the process. You probably have a problem with the Oscam configuration. The Oscam process itself works correctly.

The channel decoding on your card may have frozen for an unknown reason. However, this belongs to a separate forum thread with a LOG record attached (which happens in Oscam Webif > LiveLog).

If you really can't solve the problems with decoding channels under Oscam, then of course you can use some other methods to read the status of the reader in oscam-webif and based on the status of this reader it is also possible to restart this reader (using oscam-webif). You don't need to restart the whole Oscam process.

The "ps -C <process>" does not work on all Enigmas.

For example, OpenPLi includes "ps" as part of the BusyBox and cannot handle the "-C" argument. OpenATV contains a full-fledged tool "ps" with a functional argument "-C".

It depends on what exactly you want to test. Do you want to test whether the Oscam process is started? Or do you want to test if it's frozen? Or what exactly do you want to test?

Fo example, you can to use "pidof" instead:

if ! pidof oscam > /dev/null; then /bin/sh /etc/init.d/softcam restart; fi

I don't know all Skylink cards. I am not a satellite fitter or satellite dealer, and I am not interested in pirated card sharing. I know and can only advise on the card that I use myself (Irdeto) - as I have noted many times in my posts on the topic of Oscam.

I don't care if these are new or old cards - whether they are 1, 5 or 10 years old. M7 are new from the point of view that long ago there were no cards in the Czech / Slovak trade market called "M7" - as well as preferring the logo from the M7 operator instead of the Skylink logo, creating a new Skylink logo or the recent acquisition of FreeSat by Skylink.

Anyway ... thanks for the new information. I thought that the so-called "M7" cards only exist in the Viaccess version.

Um, I didn't know that there were new "M7" cards, still with supported Irdeto, which Skylink is gradually ceasing to support.

However, "M7" cards do not exist in Irdeto encoding. The so-called "M7" cards are new cards - in the Viaccess coding system. Or I am wrong ? I don't know much about Skylink provider marketing :).

Irdeto decoding cards, Skylink provider stopped selling. Only new cards are sold - the so-called "M7" (Viaccess encoding).