Posts by joeuser

Is it connected to the internet? Did you change the default passwords?
Are there some timers set?
Check your HDMI settings and disable ability to control TV. Not sure where on openvix, otherwise I would give more detailed directions...

Maybe this helps: http://linuxsat-support.com/showthread.php?t=26955

This link explains ca certs with curl: http://curl.haxx.se/docs/sslcerts.html

Are you sure there is email on the server?

Did you try just pop3 instead of pop3s? Some servers want normal connection first, then negotiate ssl.

- - - Updated - - -

You can also try the "-k" (insecure) option to rule out certificate errors...

Did you try without any spaces between "pop3s:" and "//pop...." ?
Did you try with -v option instead of --silent to see what it says?

You can try one of Fano or CaptainBlast's "repacked" images.
http://linuxsat-support.com/showthread.php?t=78344&p=279532&viewfull=1#post279532
http://linuxsat-support.com/showthread.php?t=84654&p=278166&viewfull=1#post278166

Quote from sleepy

Tried 3 times m8, even downloaded again in case the file was corrupt and tried a different usb stick.
Strange this one m8!:67:

- - - Updated - - -

Hiya m8, just tried another twice with different sticks in the front and rear usb ports, still no joy.
I'm guessing but i bet your back up doesn't like dual tuner boxes, time to try something different i think.
Cheers sleepy.

I know it is a little late, but here is a repacked version which should install better.

I was just coming online to ask you what you used for backups. :)
It should be possible to boot into spark and run the commands from my script to create a packed backup image to start with. I will try it when I have time. I already tested that it can be done when booting from USB or NFS. Although it is possible to do from the running system, it is usually a bad idea to backup a mounted/running root filesystem...

I posted some scripts here: Some scripts for extracting and re-packing e2jffs2.img files. The second one is for repacking backup images.

Since I usually run my images from my NFS server instead of from flash, I found myself quite often having to extract e2jffs2.img files. So, I found a script which did most of what I wanted and made some mods. I don't remember where I found the original script (was a couple of years ago...) otherwise, I would give the original author credit.

The first script mounts the e2jffs2.img file using a loop device and copies the filesystem to a local directory. Then copies the uImage file to the boot directory in the extracted filesystem. (My NFS boot scripts automatically look for the kernel there...)

Usage: ./extract_jffs2.sh e2jffs2.img Destination_Dir
(Full or relative paths can be used)

Example: Assuming you have unzipped/untarred the image to /home/user/download/image_x/ and you want to extract it to /data/alien/images/new_image:

./extract_jffs2.sh  /home/user/download/image_x/enigma2/e2jffs2.img  /data/alien/images/new_image

#!/bin/bash




## Script to extract e2jffs2.img filesystem using mtd kernel modules.




if [[ $# -lt 1 ]]
then
    echo "Usage: $0 e2jffs2.img Destination_Dir"
    echo "(Full or relative paths can be used)"
    exit 1
fi




if [ '$(whoami)' != 'root' ]
then
    echo "$0 must be run as root!"
    exit 1
fi




if [[ ! -e $1 ]]
then
    echo "$1 does not exist"
    exit 1
fi




if [[ -d $2 ]]
then
    echo "$2 already exists!!"
    exit 1
else
    mkdir $2
fi




if [[ ! -d $2 ]]
then
    echo "$2 is not a valid extract directory"
    exit 1
fi




# cleanup if necessary
umount /tmp/e2jffs2 &>/dev/null
umount /tmp/mtdblock0 &>/dev/null
modprobe -r jffs2 &>/dev/null
modprobe -r block2mtd &>/dev/null
modprobe -r mtdblock &>/dev/null
sleep 0.25
losetup -d /dev/loop1 &>/dev/null
sleep 0.25




modprobe loop || exit 1
losetup /dev/loop1 "$1" || exit 1
modprobe block2mtd || exit 1
modprobe jffs2 || exit 1
if [[ ! -e /tmp/mtdblock0 ]]
then
    mknod /tmp/mtdblock0 b 31 0 || exit 1
fi




echo "/dev/loop1,128KiB" > /sys/module/block2mtd/parameters/block2mtd




if [[ ! -e /tmp/e2jffs2 ]]
then
    mkdir /tmp/e2jffs2
fi




mount -t jffs2 -o ro /tmp/mtdblock0 /tmp/e2jffs2 || exit 1




(cd /tmp/e2jffs2; tar cf - .) | (cd "$2" ; tar xpf -) || exit 1







# cleanup if necessary
#umount /tmp/jffs2 &>/dev/null
#umount /tmp/mtdblock0 &>/dev/null
#modprobe -r jffs2 &>/dev/null
#modprobe -r block2mtd &>/dev/null
#modprobe -r mtdblock &>/dev/null
umount /tmp/e2jffs2
#umount /tmp/mtdblock0
modprobe -r jffs2
modprobe -r block2mtd
modprobe -r mtdblock
sleep 0.25
#losetup -d /dev/loop1 &>/dev/null
losetup -d /dev/loop1
sleep 0.25




rmdir /tmp/e2jffs2
rm /tmp/mtdblock0




cp $(dirname $1)/uImage $2/boot/




echo "Successfully extracted $1 to $2"
exit 0

Second script is for re-packing backup images. It mounts the backup e2jffs2.img file using a loop device and then uses mkfs.jffs2 to create a new image file.

Usage: ./repack_e2jffs2.sh e2jffs2.img
(Full or relative paths can be used)

Example: Assuming you have unzipped/untarred the backup image to /home/user/download/image_x/

./repack_e2jffs2.sh  /home/user/download/image_x/enigma2/e2jffs2.img

It will rename the original e2jffs2.img file to e2jffs2.orig and create a new repacked e2jffs2.img file.

#!/bin/bash




## Script to repack e2jffs2.img filesystem using mtd kernel modules.




if [[ $# -lt 1 ]]
then
    echo "Usage: $0 e2jffs2.img"
    echo "(Full or relative paths can be used)"
    exit 1
fi




if [ '$(whoami)' != 'root' ]
then
    echo "$0 must be run as root!"
    exit 1
fi




if [[ ! -e $1 ]]
then
    echo "$1 does not exist"
    exit 1
fi




# cleanup if necessary
umount /tmp/e2jffs2 &>/dev/null
umount /tmp/mtdblock0 &>/dev/null
modprobe -r jffs2 &>/dev/null
modprobe -r block2mtd &>/dev/null
modprobe -r mtdblock &>/dev/null
sleep 0.25
losetup -d /dev/loop1 &>/dev/null
sleep 0.25




modprobe loop || exit 1
losetup /dev/loop1 "$1" || exit 1
modprobe block2mtd || exit 1
modprobe jffs2 || exit 1
if [[ ! -e /tmp/mtdblock0 ]]
then
    mknod /tmp/mtdblock0 b 31 0 || exit 1
fi




echo "/dev/loop1,128KiB" > /sys/module/block2mtd/parameters/block2mtd




if [[ ! -e /tmp/e2jffs2 ]]
then
    mkdir /tmp/e2jffs2
fi




mount -t jffs2 -o ro /tmp/mtdblock0 /tmp/e2jffs2 || exit 1




mkfs.jffs2 --root=/tmp/e2jffs2/ --output=/tmp/mtd_root.bin --eraseblock=128KiB --pad --no-cleanmarkers || exit 1
sumtool  --pad --eraseblock=128KiB --input=/tmp/mtd_root.bin --output=$(dirname $1)/mtd_root.sum.bin || exit 1







# cleanup if necessary
#umount /tmp/jffs2 &>/dev/null
#umount /tmp/mtdblock0 &>/dev/null
#modprobe -r jffs2 &>/dev/null
#modprobe -r block2mtd &>/dev/null
#modprobe -r mtdblock &>/dev/null
umount /tmp/e2jffs2
#umount /tmp/mtdblock0
modprobe -r jffs2
modprobe -r block2mtd
modprobe -r mtdblock
sleep 0.25
#losetup -d /dev/loop1 &>/dev/null
losetup -d /dev/loop1
sleep 0.25




rmdir /tmp/e2jffs2
rm /tmp/mtdblock0
rm /tmp/mtd_root.bin




mv $1 $1.orig && mv $(dirname $1)/mtd_root.sum.bin $1 || exit 1




echo "Successfully repacked $1"
exit 0

I use Debian and already had all tools installed, so I am not sure exactly which packages you will need. I know for sure mtd-utils is necessary. Of course it depends on which Linux distribution you are using.

You can try running the scripts with:

bash -x extract_e2jffs2.sh  /home/user/download/image_x/enigma2/e2jffs2.img /data/alien/images/new_image

to see what is going on if there is a problem.

The scripts are not fool-proof and not much error checking is done, so take care with what you are doing...

For people having trouble flashing this image you can try this re-packed version.

When I get some time, I will post the script I use to repack backup images so they are more like the original developer's e2jffs.img files.

Did you try changing boxtype to "ipbox"?

It has been awhile since I used Spark or Hyperion, but I think you need to change the boxtype. You can try 'boxtype = ipbox' or 'boxtype = duckbox' in oscam.conf.

That is why I posted the repacked image. It is only as big as needed for the actual files, so more like the original developers images...

Sent from my A/S10 using Forum Fiend OSP v1.3.3.

Or try this - it has a smaller, re-packed e2jffs2.img which may install better on some machines.

"Sticks on the boot screen," meaning the hdmu boot logo on the TV or a blank TV screen and the VFD showing just "BOOT" ?
If the first case, does it respond to pings? Can you ftp/telnet to the box?
Do you have any flash drives or external hard drives connected?

I usually use a cheap satfinder I picked up for less than £10 to get it close then use my phone/tablet with Vu+ Player app to fine tune. Some sats can be found with just using the app, but with the slight delay, it can be a slow tedious process. Using the inline satfinder is much quicker and easier.

try dishpointer.com

Sent from my A/S10 using Forum Fiend OSP v1.3.3.

Maybe try Dreambox edit???

See this post: http://linuxsat-support.com/showthread.php?t=84654&p=276143&viewfull=1#post276143

The commands did not get entered ok. Try again cutting and pasting just 2-3 lines at a time starting with

setenv board 'pdk7105'

Make sure each time you get the whole line including both single quote marks ( ' ) and after each time you should get the

PDK7105>

command prompt back. If you get just

>

then it means you did not paste both single quote marks ( ' ). In that case, type another single quote ( ' ) by itself and return and try again.

Every command should read

setenv ....

If it does not start with that, then there was something wrong with the input.

Also at the end, you entered

'printenv

instead of just

printenv

So the command did not work, nor did any commands afterwards.

BTW - when posting the output back here, it is best to use the "#" option and paste the output between the "[ CODE ]" and " [ /CODE ]". Then it will be put in a scrollable box like in my posts...