Is it possible to make an image of a neutrino...?

[DM900]

Then you should try flash via restore mode (Browser). May this can repair the partitions.

I have also updated (online update) - no problems here. Strange, that you have such problems.

Already try browser mode too but still this problem arises

[zozman]

Then flash the original E2 from dreamboxupdate.com. This will also make a clean flash (complete new partitions). If this also not work then you may have a flash memory problem. But the log was normal for this...

[DM900]

Then flash the original E2 from dreamboxupdate.com. This will also make a clean flash (complete new partitions). If this also not work then you may have a flash memory problem. But the log was normal for this...

Ok I will try thank you so much for helping
Original image is working fine without any issue

[DM900]

When I flash through browser this image I have this error
Mounting '/dev/mmcblk0p2' to '/mnt'
[*] Extracting '/tmp/nbbSlI' to '/mnt'
Warning: Unknown package manager, can't run postinst scripts
[*] Unmounting '/mnt'
[*] Finished successfully. You may reboot now.
I think this is actual problem
If I flash official dream image I don't get this error

Screenshot_2024-06-23-10-40-32-789_com.android.chrome-edit.jpg

[zozman]

No, this is not the problem, because Neutrino don't have a package manager. You should better read the first 8 lines. They show you the problems.

1. The rescue loader is too old. WARNING: Don't flash rescue loader if you are in rescue mode!
2. The data partition not valid and can't be mounted.

At rescue mode:

To repair partitions:
umount /dev/mmcblk0p3
this can be give a error if not mountet - it's OK

now make a ext4 filesytem:
mkfs.ext4 /dev/mmcblk0p3 -L data

if this not working, try a ext3 filesystem:
mkfs.ext3 /dev/mmcblk0p3 -L data

Now reboot again to rescue loader. Just type reboot and hold the power button at the box. If you are in rescue again, try flashing the original E2 via browser. Then should the error for the data partition gone. Start now the original E2. Skip all except the network settings, we don't need a picture. If network set, update the rescue loader with:

update-rescue

This make take some time, wait for response. If done, then you can try again flashing neutrino via rescue mode. After that the original kernel will be used, but it should work. The kernel can be updatet with ofgwrite.

cp /boot/zImage /tmp/kernel.bin
ofgwrite -k /tmp

After a reboot now the right kernel used.

[DM900]

No, this is not the problem, because Neutrino don't have a package manager. You should better read the first 8 lines. They show you the problems.

1. The rescue loader is too old. WARNING: Don't flash rescue loader if you are in rescue mode!
2. The data partition not valid and can't be mounted.

At rescue mode:

To repair partitions:
umount /dev/mmcblk0p3
this can be give a error if not mountet - it's OK

now make a ext4 filesytem:
mkfs.ext4 /dev/mmcblk0p3 -L data

if this not working, try a ext3 filesystem:
mkfs.ext3 /dev/mmcblk0p3 -L data

Now reboot again to rescue loader. Just type reboot and hold the power button at the box. If you are in rescue again, try flashing the original E2 via browser. Then should the error for the data partition gone. Start now the original E2. Skip all except the network settings, we don't need a picture. If network set, update the rescue loader with:

update-rescue

This make take some time, wait for response. If done, then you can try again flashing neutrino via rescue mode. After that the original kernel will be used, but it should work. The kernel can be updatet with ofgwrite.

cp /boot/zImage /tmp/kernel.bin
ofgwrite -k /tmp

After a reboot now the right kernel used.

All above step done and successful
But while flash kernel it give error

kernel.txt

[zozman]

No, there is no error. The FBIO messages can be ignored.

Code: Alles auswählen

Flashing kernel ...
done

[DM900]

No, there is no error. The FBIO messages can be ignored.

Code: Alles auswählen

Flashing kernel ...
done

All step done but my bad luck same error and remote not responds thank for your support and help I will leave it now thank you so much again

[DM900]

Very strange. I have the image testet without any problems. I have also for a test repart all partitions (*) with own script, testing image and back to default partition sizes - all without any problems. Of course all with actual rescue loader.

(*) Testet on DM820/DM7080/DM900/DM920

[DM900]

Very strange. I have the image testet without any problems. I have also for a test repart all partitions (*) with own script, testing image and back to default partition sizes - all without any problems. Of course all with actual rescue loader.

(*) Testet on DM820/DM7080/DM900/DM920

(Rescue loader also update successfully)
I don't know sir I done every step which u said but still that fatal zapit error
And if I use multiboot then it works but there are other problems

[zozman]

...but still that fatal zapit error

This is, because the root partition maybe is still r/o. Can you see with mount in telnet.

And if I use multiboot then it works but there are other problems

What for problems - and does the multiboot use the right kernel?

[DM900]

...but still that fatal zapit error

This is, because the root partition maybe is still r/o. Can you see with mount in telnet.

U mean with above telnet commands

And if I use multiboot then it works but there are other problems

What for problems - and does the multiboot use the right kernel?

Problem some transponders scan some not
No kernel I think is wrong one I try manually through extra menu but no success it still shows dream kernel

[zozman]

Yes, type "mount" in Telnet then you see the ro flag. But I don't know why this on your box is, because this is fixed at booting before the modules are loading.

Multiboot: You should find out, where the kernel come from so that you can it change/replace.

[DM900]

Yes, type "mount" in Telnet then you see the ro flag. But I don't know why this on your box is, because this is fixed at booting before the modules are loading.

Multiboot: You should find out, where the kernel come from so that you can it change/replace.

Please check this mount text

mount.txt

[zozman]

Seems to be the mount command with BA, not with flash image, because all is r/w.