Zitat

I'm having problems with my Dreambox 7025. I've had it for about 4 months and since 2 months ago the following started to happen - after i've put it in deep standby, it wouldn't finish booting after i started it for the first time and i had to switch it off and on again on the button at the back of it (cause no front buttons would react) it and it booted fine.

This is a known problem (that hopefully will get fixed)

If you can read German, the situation is discussed in full here,
with a temporary solution: link

When the 7025 hangs, it can still be reached via the network, so you can telnet the box from you PC and ask it to reboot ("init 0") after which it works fine.

In the German text linked above it's explained how to add a safety net to the boot sequence. An additional batch job is started which checks if the 7025 has booted up correctly. (The version to get is the post from HeiRos (18.09.2006 15:00)). If there's a hang in the bootup, this job will notice it and issue a restart command once. My box had the hanging problem all the time. With this script, it starts perfectly every time - even if it sometimes needs two attempts. I just add 5 minutes to each timer begin to give it enough time to do two starts.

Zitat

So, i suspect there's something wrong with the power supply. Am i right or is there something else i can try?

I don't know if the constant hard resets have damaged your image.
Reflashing might help - but that's only a guess.

For the benefit of other English language readers here's the script:

The script is

#!/bin/sh


DATEI=/media/hdd/bootbroblem.log
NAME=BOOTTEST_V_0.1: 
WARTEZEIT=60s


echo $NAME Aufruf von Skript $0 mit Parameter $1
case "$1" in
 start)
  echo $NAME Restart von $0 im Hintergrund
  $0 teste &
  ;;
 stop)
  echo $NAME Nichts zu tun
  ;;
 restart)
  echo $NAME Nichts zu tun
  ;;
 teste)
  echo $NAME Warte $WARTEZEIT auf Start der Enigma2-Prozesse 
  sleep $WARTEZEIT
  if [ `ps -ax | grep enigma2 | wc -l` -lt 4 ]; then
    echo $NAME Zu wenige Enigma2-Prozesse
    if [ ! -f $DATEI ]; then
      echo $NAME $DATEI existiert nicht, Box wird neu gestartet
      ps -ax >$DATEI
      reboot
      exit 0
     else
      echo $NAME $DATEI existiert, kein Reboot
    fi
   else 
    echo $NAME Start scheinbar normal
    if [ -f $DATEI ]; then 
      echo $NAME Loesche $DATEI
      rm $DATEI
    fi  
  fi
  echo $NAME Boottest beendet
  exit 0  
  ;;
 *)
  echo $NAME Aufruf unklar
  ;;
esac

I saved it as bootprobleme.sh and copied it into
"/etc/init.d/bootprobleme.sh". This is not the best
place to put it - you can also put it anywhere on your
hdd - just make sure it is linked correctly (see below).

I then used telnet to connect to the box,
when into "/etc/init.d" and typed
dos2unix bootprobleme.sh
and
chmod 777 bootprobleme.sh

Then I went into "/etc/rc3.d/"
Here I linked the file.
ln -sf /etc/init.d/bootprobleme.sh S9abootprobleme

Now you're done.

If you want to test it:

Type init 2 (to stop Enigma) and
then sh bootprobleme.sh start
The script should wait for 60 seconds and then
reboot the system (as Enigma is not running)

Hope this helps.

Zitat

errrrm, how do you get into /etc?

i don't suppose it's the same as in DOS - cd etc?

Give it a try , the "cd" command is the same.
You will have to go up some levels ("cd ..") before
you reach the etc directory.

(And instead of dir, you use "ls")

Zitat

ls outputs nothing

This is probably because the telnet session starts in your home directory.
This should be empty - so no output.

Try "cd .." repeatedly until the ls command displays the etc directory.

Zitat

thanx, it works, but unfortunately after doing it i noticed in rc3.d there already is a S99 process - S99mnologin. did i mess up something?

No, this was in there before.

Just to be on the safe side,
you could rename the link S99bootprobleme to
S9abootprobleme using your FTP client.
This way it would be started as the last process
and not the second last...

As far as I understand it the number only determines the
order in which the processes get run. (I'm not a Linux
expert)

This is my last post for now - if you still have problems I'll look in here again this evening...

Zitat

enigma stops, but then when i try to start it, dm reports it can't find the script.

note that bootprobleme.sh is in "/etc/init.d",
so to start it you have to navigate back into this directory fiirst.

Another hint: "init 2" stops Enigma. You can restart it by
typing "init 3". Both commands work in any directory.

Zitat

are there any visible signs of this scrpt? i mean, how do i know it works?

you could telnet your machine and type ps to see the running processes.

But if your machine hangs as often as mine you'll notice the second successful boot attempt soon

Zitat

i did that, but still i can't start it

Hmm, if you're in the /etc/init.d directory and
can see the file (by typing ls) but not
start it, then I'm stumped...