36 replies to this topic

[dog05]

I installed the latest image for dm7025 and if I load plugins cc * 221, mgca sca * 3.6 * 1.35 and the dreambox to reboot hangs.
I would like to ask you a few things for a workaround:
1. - If I copy the firmware to a CF, plugins and settings when you go to install flash or CF?
2. - If this is not possible, you can remove "something" to reduce the burden?
3. - How do you see the free space of the flash and CF?
We thank in advance those who will help me.
Greetings

[dog05]

Sorry there is a type, I wrote 8075 instead of 7025.

[JanH]

Flash memory is small and enough for image only (7025) if you try to install plugins, system failed because flash full and not possible to write to.
CF card is usable for swap, some config files etc. Plugins are installed to flash memory.
There are two programs available as plugins to extend flash memory:
- CFboot, which should copy whole system to CF card and boot from it.
- CFexpander which make directory "Delta..." on CF card and mount it over /usr directory on flash memory.
You should install this plugin as first one on clean image.
It is possible to delete some plugins and restore system from linux prompt or FTP. Plugins are in directory
/usr/bin/enigma2/python/.... I do not know if it is exact :-)
Let me know how you resolve the problem, I have 7025 too and my installation is a bit crazy now.

[dog05]

JanH,So if I understand correctly, after you copy the flash cf everything will be that I will install on flash, right? but so the flash will always be full. can clarify this?.
I also wanted to know how to see the space available in cf and flash, if there is a command or instruction.
Hello

[JanH]

It doas not matter where you copy file for installation. It still be installed to flash. Usually we use /tmp directory because it will be deleted after reboot.
It is only way to use new image or delete something from the flash to rescue box.
Plugins for CF boot or expand you should install to clean image becouse space needed for it too.
I do not know now what exactly you will see on linux prompt but try for example "df" command.
I have 4 GB CF card then I am free to use it.
If you use plugin for CF card, flash remain stil same as it was before CF plugin installation. After card removing box is booting from flash again without later changes.

[MiLo]

If you use cf-boot, best way to set up is to do a minimal configuration in internal flash (i.e. your dish settings and a softcam). That gives you a nice backup point - you can always go back to this state quickly.
Then activate the plugin and have it copy everything to the CF card. The CF card must have an ext2/3 filesystem for this to work (format it via the menu if it isn't).
Activate booting from CF card via the plugin, and reboot.

The system will now completely run from CF card. The internal flash is only used for storing the linux kernel. The "rootfs" portion of the flash is no longer even being mounted (shortens boot time considerably), it won't be written. "df" will no longer report anything for the internal flash.

The "/media/cf" directory is present (and just points to the CF card's root which is also the system root) to remain compatible with e.g. timeshift and picons and plugins. Everything is stored on the CF card, so it does not matter where you put things.

[dog05]

Milo,when I leave the formatting (it does), I get this message, it means?
--------
initialing storage device...
errore: mke2fs 1.42 (29-nov-2011)
warning:unable to get device geometry for /dev/hdc1
/dev/hdc1: no such file or directory while settng up superblock
-----------
then if you do the copy command in flash cf, I get this error message:
-----
Cannot continue, you did not format or mount the CF correcly
-------
Can you help to eliminate these errors?
Thanks
Greetings

[MiLo]

Milo,when I leave the formatting (it does), I get this message, it means?

It means it failed to format, I've never seen this particular error before. You could try manually via telnet/ssh, it might give better feedback as well.

To format the CF card, first unmount it, check /proc/mounts and do "umount /dev/hdc*"

Format with "mkfs.ext3 -m0 -O dir_index /dev/hdc".

[dog05]

Milo, telnel do not know well, you may please guide me step by step. Using the program dcc296 generally to stp but c'èanche telnet
Thanks
Greetings

[dog05]

Milo, I write because it is a strange thing happened. After uploading an image several times that I made the copy on the flash cf. I have not run any commands, only the instructions in the menu. At this point I press "Activate CF boot" but the message "In / boot / bin / init file exits" and boot from cf is not executed. What can I do to boot?.
Hello

[dog05]

Milo, I was able to format the CF, I copied the flash in CF, but when I go to "activate CF boot" from the following error message: "ln: / boot / bin / init file exists". What does this mean? How to fix it
Thanks again for the help.
Greetings

[dog05]

JanH, I was able, with the help of Milo, format and copy the flash CF. Unfortunately, when I click on "active boot from CF" (via ppnal) I get the following error massage: "ln: / boot / bin / init file exists" and I do not know if the system boots from flash or cf. I have also seen that if I install plugins like setting, they are installed on the flash. As you can see I'm a little messed up and I want some good soul enlighten me.
Hello

[MiLo]

Can you use telnet or ssh? Do you know how to enter commands? do you know how to copy the output and paste it on the forum?

[dog05]

Milo, first thank you for answering and then tell you that, use telnet, the copy of the screen I've ever made but if you say how do you post it in the forum.

Edited by dog05, 26 January 2013 - 19:43.

[MiLo]

Can you post the output of the following telnet commands:

mount

ls -al /boot/

[dog05]

root@dm7025:~# mount
rootfs on / type rootfs (rw)
/dev/root on /boot type jffs2 (ro,noatime)
/dev/mtdblock3 on /boot/mnt/flash type jffs2 (rw,noatime)
/dev/loop0 on /boot/mnt/squashfs type squashfs (ro)
none on / type unionfs (rw,dirs=/boot/mnt/flash/delta=rw:/boot/mnt/squashfs=ro,d
ebug=0,delete=whiteout,copyup=preserve)

proc on /proc type proc (rw,nodiratime)
sysfs on /sys type sysfs (rw)
tmpfs on /media type tmpfs (rw)
tmpfs on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw)
/dev/hda1 on /media/hdd type ext3 (rw)
/dev/hdc1 on /media/cf type ext3 (rw)
usbfs on /proc/bus/usb type usbfs (rw)
tmpfs on /var/volatile type tmpfs (rw)
---------------------------

root@dm7025:~# ls -al /boot/
drwxr-xr-x 7 root root 0 Apr 26 2012 .
drwxr-xr-x 19 root root 0 Jan 1 00:00 ..
-rw-r--r-- 1 root root 38 Jan 1 1970 autoexec.bat
lrwxrwxrwx 1 root root 18 Jan 1 1970 backdrop.mvi -> /boot/b
ootlogo.mvi

drwxr-xr-x 2 root root 0 Jan 1 00:05 bin
-rwxr-xr-x 1 root root 9310 Jan 1 1970 bootlogo.elf
-rwxr-xr-x 1 root root 457522 Jan 1 1970 bootlogo.jpg
lrwxrwxrwx 1 root root 23 Jan 1 1970 bootlogo.mvi -> /usr/sh
are/bootlogo.mvi
lrwxrwxrwx 1 root root 18 Jan 1 1970 bootlogo_wait.mvi -> /b
oot/bootlogo.mvi

drwxr-xr-x 2 root root 0 Jan 1 00:05 dev
drwxr-xr-x 3 root root 0 Jan 1 1970 lib
drwxr-xr-x 5 root root 0 Jan 1 1970 mnt
lrwxrwxrwx 1 root root 16 Jan 1 1970 vmlinux -> vmlinux-2.6.
12.6
-rwxr-xr-x 1 root root 2303819 Jan 1 1970 vmlinux.gz

[MiLo]

"/dev/root on /boot type jffs2 (ro,noatime)" Means you're running from internal flash.

What's the output of:

ls -al /boot/bin/

[dog05]

root@dm7025:~# ls al/boot/bin/
ls: al/boot/bin/: No such file or directory

[dog05]

pardon

root@dm7025:~# ls -al /boot/bin/
drwxr-xr-x 2 root root 0 Jan 1 00:05 .
drwxr-xr-x 7 root root 0 Apr 26 2012 ..
-rwxr-xr-x 2 root root 19540 Jan 1 1970 init
-rwxr-xr-x 1 root root 14836 Apr 26 2012 initcf
-rwxr-xr-x 2 root root 19540 Jan 1 1970 initflash

[dog05]

Milo, soon as you can, we can continue the discussion of the CF.
Hello