Posts by Numerio

Quote from toysoft

Forget about the log, just boot the box and it will work. The building of an open image is not same as the strucutre of the DMM image.

So just flash, and boot box, it will work fine.

Then... naturally flash it to the right box, if the image is dreamone, flash to dreamone, If the image is dreamtwo, flash to dreamtwo... and DON'T USE the nasty Multiboot that rejects open images... that's crap. You need to flash directly the image to flash.

TS

Display More

Thanks indeed, my box booted regularly once moved it from pc desk to the tv.

Actually, the screen monitor I use on my desk doesn't show up (synch) on PLI sturtup as it happens with DMM images (not really an issue).

NP

Hello Toysof,

I got stuck trying to flash "openpli-enigma2-8xstar-dreamtwo.rootfs.tar.gz" to my DreamboxTwo.

Any hint is welcome

------------------------- Log ------------------------

[*] Remounting '/dev/dreambox-data' to '/data'

[*] Creating ext4 filesystem 'dreambox-rootfs' on /dev/dreambox-rootfs

mke2fs 1.43.4 (31-Jan-2017)

Discarding device blocks: 4096/1048576 528384/1048576 done

Creating filesystem with 1048576 4k blocks and 262144 inodes

Filesystem UUID: 4cd73435-7f10-4c0f-9180-40ed8d55afd0

Superblock backups stored on blocks:

32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables: 0/32 done

Writing inode tables: 0/32 done

Creating journal (16384 blocks): done

Writing superblocks and filesystem accounting information: 0/32 done

[*] Mounting '/dev/dreambox-rootfs' to '/mnt'

[*] Extracting '/tmp/KEf0J2' to '/mnt'

[*] Mounting '/dev' to '/mnt/dev'

[*] Mounting '/proc' to '/mnt/proc'

[*] Mounting '/run' to '/mnt/run'

[*] Mounting '/sys' to '/mnt/sys'

[*] Creating directory '/mnt/tmp'

[*] Mounting '/tmp' to '/mnt/tmp'

Fatal: Unsupported machine!

Fatal: Failed to run kernel-image.postinst

[*] Unmounting '/mnt/tmp'

[*] Unmounting '/mnt/sys'

[*] Unmounting '/mnt/run'

[*] Unmounting '/mnt/proc'

[*] Unmounting '/mnt/dev'

[*] Unmounting '/mnt'

Ciao

No-pla

I am glad to hear that finally you manage and control both of them.:thumbup:

cheers

I suggest you enable the log production inside /usr/local/etc/oscam.conf (the one releted to oscammips)

make sure it contains:

[global]

disablelog = 0

logfile = /tmp/oscammips.log <<< path/file of your preference

hopefully we get some info

cheers

Hi G++,

I don't know 'oscammips'. I assume it is an oscam variant that we want to run in parallel.

For what I see, 'oscammips' has been started with PID 226 but the socket hadn't

>> Root @ DM900: ~ # SystemCTL status new-supcam.socket

>> ● New-Supcam.Socket

>> Loaded: Loaded (/Lib/systemd/system/new-supcam.socket; Disabled; Vendor taken

>>>>>>>>>>>>> Active: Inactive (dead) <<<<<<<<<<<<<<<<<<

add 'new-supcam.socket' into new-supcam.service as follow:

Requires=new-supcam.socket dev-dvb-adapter0-ca0.device dev-dvb-adapter0-demux0.device dev-sci0.device

please also consider that with this script configuration, 'oscammips' get started before 'oscam-11682',

maybe you need the other way around (still I don't know what oscammips does/requires)

ciao

P.S.: did you try to manually debug your first script via systemctl/journalctl in telnet ?

May be you find an easy way to fix the problem. We still don't know what went wrong with your initial script.

Well, I don't know what Supcam does. My first suggestion was to run/debug the scrip manually, then I asked "would it be feasible to create second script ?"

Hi,

I've created a test enviroment on my Dream-Two: Both executables seem to start one after the other.

Here is what I have done:

1. Create new script (NewSupcam.service)

-------------------------------------------------

[Unit]

Description=Supcam

Requires=dev-dvb-adapter0-ca0.device dev-dvb-adapter0-demux0.device dev-sci0.device

After=dev-dvb-adapter0-ca0.device

After=dev-dvb-adapter0-demux0.device

After=dev-sci0.device

[Service]

Type=forking

ExecStart=/usr/bin/oscam-emu-00 -b -B -r 2 -w 1 -c /etc/tuxbox/Test & << Change this

Restart=on-failure

NonBlocking=true

NotifyAccess=main

[Install]

WantedBy=multi-user.target

Also=NewSupcam.socket

-------------------------------------------------

you need to replace the ExecStart with yours -> /usr/local/etc/oscammips -b -B -r 2 -w 1 -c /usr/local/etc &

2.) create (NewSupcam.socket)

-------------------------------------------------

[Unit]

[Socket]

ListenStream=/var/run/osccam.pid

Backlog=8

[Install]

WantedBy=sockets.target

--------------------------------------------

3) Link NewSupcam.service into your original script

This is my script (emu-osca.Test.service)

--------------------------------------------

[Unit]

Description=Test

Requires=emu-oscam.Test.socket dev-dvb-adapter0-ca0.device dev-dvb-adapter0-demux0.device dev-sci0.device NewSupcam.service <<<<<< Link here

After=dev-dvb-adapter0-ca0.device

After=dev-dvb-adapter0-demux0.device

After=dev-sci0.device

After=NewSupcam.service <<<<<< Link here

[Service]

Type=forking

ExecStart=/usr/bin/oscam-emu-11.689 -b -B -r 2 -w 1 -c /etc/tuxbox/Test &

Restart=on-failure

NonBlocking=true

NotifyAccess=main

[Install]

WantedBy=multi-user.target

Also=emu-oscam.Test.socket

--------------------------------------------

4) I went through the Telnet running (systemctl start emu-oscam.Test.service)

5) check service status (systemctl status emu-oscam.Test.service or journalctl -u emu-oscam.Test.service)

● emu-oscam.Test.service - Test

Loaded: loaded (/lib/systemd/system/emu-oscam.Test.service; disabled; vendor preset: enabled)

Active: active (running) since Wed 2021-03-24 01:00:50 CET; 9min ago

Process: 650 ExecStart=/usr/bin/oscam-emu-11.689 -b -B -r 2 -w 1 -c /etc/tuxbox/Test & (code=exited, status=0/SUCCESS)

Main PID: 651 (oscam-emu-11.68)

CGroup: /system.slice/emu-oscam.Test.service

├─651 /usr/bin/oscam-emu-11.689 -b -B -r 2 -w 1 -c /etc/tuxbox/Test &

└─652 /usr/bin/oscam-emu-11.689 -b -B -r 2 -w 1 -c /etc/tuxbox/Test &

Mar 24 01:00:50 dreambox systemd[1]: Starting Test...

Mar 24 01:00:50 dreambox systemd[1]: Started Test.

5) check service status (systemctl status NewSupcam.service)

● NewSupcam.service - Supcam

Loaded: loaded (/lib/systemd/system/NewSupcam.service; disabled; vendor preset: enabled)

Active: active (running) since Wed 2021-03-24 01:00:50 CET; 10min ago

Process: 635 ExecStart=/usr/bin/oscam-emu-00 -b -B -r 2 -w 1 -c /etc/tuxbox/Test & (code=exited, status=0/SUCCESS)

Main PID: 636 (oscam-emu-00)

CGroup: /system.slice/NewSupcam.service

├─636 /usr/bin/oscam-emu-00 -b -B -r 2 -w 1 -c /etc/tuxbox/Test &

└─637 /usr/bin/oscam-emu-00 -b -B -r 2 -w 1 -c /etc/tuxbox/Test &

Mar 24 01:00:50 dreambox systemd[1]: Starting Supcam...

Mar 24 01:00:50 dreambox systemd[1]: Started Supcam.

-----------------

604 ? 00:00:00 kworker/1:1H

615 ? 00:00:00 telnetd

616 pts/0 00:00:00 bash

621 ? 00:00:00 vsftpd

623 ? 00:00:00 vsftpd

636 ? 00:00:00 oscam-emu-00 <<<

637 ? 00:00:01 oscam-emu-00 <<<

651 ? 00:00:00 oscam-emu-11.68 <<<

652 ? 00:00:01 oscam-emu-11.68 <<<

676 ? 00:00:00 irq/27-ff642000

677 ? 00:00:00 irq/28-ff642000

2065 ? 00:00:00 tb_detect

2066 ? 00:00:00 ppmgr

2167 pts/0 00:00:00 ps

Cheers

Hi,

try to start the script manually in a Telnet terminal via

systemctl start <scriptname>

you might get info about the reason of failure (I see a potential problem with the socket file name).

As an alternative, would it be feasible to create second script NewSupCam.service ?

[Unit]

Description=Supcam

Requires =Supcam.socket

[Service]

ExecStart=/usr/local/etc/oscammips -b -B -r 2 -w 1 -c /usr/local/etc &

[Install]

WantedBy=multi-user.target

Also=Supcam.socket

then add NewSupCam.service inside the [Unit] section of your script

..

Requires ... NewSupCam.service

..

After=dev-sci0.device

After = NewSupCam.service

ExecStart must be updated accordingly.

Cheers