Disclaimer

This coding guide and any accompanying scripts are provided by Damian123123 / Kr4k3nPL on an "as is" basis, without warranties or conditions of any kind, either expressed or implied. You are free to use, modify, copy, and distribute the content in this guide for personal or commercial purposes. However, Damian123123 / Kr4k3nPL will not be held liable for any damages, losses, or issues resulting from its use.

By using or contributing to these scripts, you acknowledge that you do so at your own risk and agree to hold Damian123123 / Kr4k3nPL harmless from any responsibility regarding the reliability, performance, or maintenance of your projects. Furthermore, any contributions or modifications you make are equally shared under these same terms, ensuring that future users benefit from the same open collaboration principles.

Below are the step‐by‐step instructions to install the new OSCam package on your Dreambox One (Enigma2, OpenBH firmware). Make sure you have SSH access to your Dreambox before proceeding.

Transfer & Verify the Tarball

Make sure the file oscam_new.tar.gz is placed in:

/var/volatile/tmp/

_{Check by running:}

ls -l /var/volatile/tmp/oscam_new.tar.gz

You should see something like:

-rw-r--r-- 1 root root <size> <date> /var/volatile/tmp/oscam_new.tar.gz

Extract the Archive

Change to the tmp directory and extract:

cd /var/volatile/tmp
tar -zxvf oscam_new.tar.gz

Create a Directory for OSCam

On many Enigma2 systems, custom OSCam files are placed in /etc/tuxbox/config/. Create a new directory to hold your OSCam binary and any config files:

mkdir /etc/tuxbox/config/oscam_new

(If you get “File exists,” remove or rename any existing file with the same name.)

Move & Rename the Binary

If your extract gave you a single binary (for example, oscam-gitXXXX-something), move and rename it to oscam inside the new directory:

mv /var/volatile/tmp/oscam-gitXXXX-something /etc/tuxbox/config/oscam_new/oscam

If it created a folder instead (for example, oscam-Dark-Grey-V2/), move that folder’s contents (especially the oscam file) into /etc/tuxbox/config/oscam_new. Adjust the move command accordingly.

Make the Binary Executable

chmod 755 /etc/tuxbox/config/oscam_new/oscam

(Optional) Put Configuration Files in Place

If you have OSCam config files (e.g., oscam.conf, oscam.server, oscam.user), place them in the same folder or wherever your image expects them, for example:

cp oscam.conf /etc/tuxbox/config/oscam_new/

Run OSCam

Change to the OSCam directory:

cd /etc/tuxbox/config/oscam_new

Start OSCam in debug mode:

./oscam -b -d

You should see debug output in your terminal indicating if OSCam starts successfully. Once it’s running, you can check with:

ps | grep oscam

By following these steps, you’ll have OSCam extracted from oscam_new.tar.gz, installed in /etc/tuxbox/config/oscam_new/, and running on your Dreambox One with OpenBH. Make sure to tailor your config files (cards, servers, etc.) for your specific setup.

=============================================================================

How to make OSCam start automatically in the background whenever your Dreambox One (Enigma2, OpenBH) reboots.

Method 1:Create an init.d Startup Script

1. Create a Shell Script in /etc/init.d/oscam

Use a text editor (like nano or vi) to create a file named /etc/init.d/oscam:

nano /etc/init.d/oscam

Paste the following script (adjusting the path to your OSCam binary if needed):

#!/bin/sh
### BEGIN INIT INFO
# Provides:          oscam
# Required-Start:    $network
# Required-Stop:
# Default-Start:     2 3 4 5
# Default-Stop:
# Short-Description: Start OSCam
### END INIT INFO


OSCAM_BIN="/etc/tuxbox/config/oscam_new/oscam"
OSCAM_ARGS="-b -d 1"


case "$1" in
start)
echo "Starting OSCam..."
# -b runs in background; -d 1 sets a basic debug level
$OSCAM_BIN $OSCAM_ARGS >/dev/null 2>&1 &
;;
stop)
echo "Stopping OSCam..."
killall oscam
;;
restart)
$0 stop
sleep 1
$0 start
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
;;
esac


exit 0

Make the Script Executable

chmod 755 /etc/init.d/oscam

Add It to Startup (SysV Style)

update-rc.d oscam defaults

(If your image uses BusyBox’s simpler rc system, it should still respect /etc/init.d/oscam automatically at boot. If not, you may need to create symbolic links in /etc/rc3.d/ or /etc/rcS.d/, etc.)

Method 2: Use OpenBH’s Built‐in Softcam Panel (if available)

Some Enigma2 images (including OpenBH) have a Softcam Manager or Softcam Panel that lets you manage which softcam starts at boot. The approach typically looks like this:

1. Place the OSCam binary (e.g. /etc/tuxbox/config/oscam_new/oscam) where the panel expects it, often /usr/bin/, /usr/softcams/, or a designated location for emulators.
2. Add or edit a Softcam script in /usr/camscript/ or /usr/script/ with lines to start/stop your OSCam.
3. In the Softcam Panel menu, select your new OSCam script as the default softcam and enable autostart on reboot.

Depending on your image version, the specifics may vary, but this is often the most seamless approach if your firmware provides a dedicated panel for managing softcams.

Method 3: Append to rc.local (If Present)

Some older or more minimal Enigma2 setups still have an /etc/rc.local file that runs at the end of the boot process. You can add:

/etc/tuxbox/config/oscam_new/oscam -b -d 1 &

to /etc/rc.local before the final exit 0. However, many modern images either don’t have rc.local or ignore it, so the init.d or Softcam Manager methods are more reliable.

Summary

1. Make sure your OSCam binary is in a consistent location (e.g. /etc/tuxbox/config/oscam_new/oscam) with the correct permissions (chmod 755).
2. Pick an autostart method:
   • Init Script: Create /etc/init.d/oscam, make it executable, run update-rc.d oscam defaults.
   • Softcam Panel: If your image supports it, place the binary and create a startup script recognized by the panel.
   • rc.local: If your image still uses rc.local, add your OSCam start command there.

Any of these approaches ensures OSCam will start automatically in the background whenever you reboot your Dreambox One on OpenBH.