nfidump ...

K

kallquk

Registered
Messages
43
Hello to All!

I am trying to make an usb stick bootable with image, putting in work through bios of my dm800hdse, as some tutorial learns.
Is not working, I thought because nfidump is not executed completely:

root@dm800se:~# /usr/lib/enigma2/python/Plugins/Extensions/dFlash/bin/nfidump /tmp/OpenPLi-3.0-beta-dm800se-20121022.nfi /media/u1

************ nfidump 0.4.3 by gutemine <<<<<<

based on code from tmbinc, noggie and others

extracting dm800se nfi image ...
extracting boot.jffs2 from nfi ...
extracting boot from boot.jffs2 ...
** wrong data crc **
** wrong crc **
** INVALID ** - nodetype 3428
there were errors, but some valid stuff was detected. continuing.
extracting root.jffs2 from nfi ...
Error opening /media/u1/../root.jffs2

in bold is the command I give and /media/u1 is the folder where I mount the usb exactly as tutarials says, first partition is fat, others ext3. As you can see the proccess is interrupted, not all data is extracted so the boot from usb is not realized.


But if I create a directory in this partition of usb eg "1", then the nfidump is successed:

root@dm800se:~# /usr/lib/enigma2/python/Plugins/Extensions/dFlash/bin/nfidump /tmp/OpenPLi-3.0-beta-dm800se-20121022.nfi /media/u1/1

************ nfidump 0.4.3 by gutemine <<<<<<

based on code from tmbinc, noggie and others

extracting dm800se nfi image ...
extracting boot.jffs2 from nfi ...
extracting boot from boot.jffs2 ...
extracting root.jffs2 from nfi ...
extracting root from root.jffs2 ...

************ nfidump finished <<<<<<



where in bold is the command. even is successful, it is not usable, because it is needed swapped in root, isn't it ?

I am asking for help to execute this command succesfully, please help


thanks in advance
regards
 
C

cokesux

Registered
Messages
190
Yes, IIRC the image's filesystem needs to be in the root of it's USB partition, not a subdirectory. You could try:

cd /media/u1/1
mv * ..


to move all the files out of the subdir to the root.

It's been awhile since I played with it, but I don't recall seeing your error, not sure what could cause it as extracting to the subdir seems to work... Strange...

--
hemi
 
K

kallquk

Registered
Messages
43
Yes, mv command is executed but the boot fails

I downloaded the new version of dumbo but it requires new kernels and is not installed in flash where I have latest edg-nemesis


I thank you very much for the help

may be I going out of this thread, that I started for nfidump command, because I am posting the bootlog of usbserial port, during this failing boot:

Dreambox D

FIRST STAGE 1.0/400 {BO23456}


2ND STAGE OK, build #84 (2011-09-01)

0.000 - BCM board setup
0.000 - fp init
0.000 - ca init
0.513 - load config
0.540 - config loaded.
* press to enter setup
OLED found!
color oled reset
lcd: BOOT #84
P23 detected!
- read config file: /boot/secondstage.conf
Device: USB Disk unit 0
- Sectors: 15644912
- Size: 7639 MiB
P 01 63 22113 < 15644912

Device 0: Partition 1: Filesystem: FAT12 "NO NAME "
- failed to open /boot/secondstage.conf
- failed to open /cf/autorun.bat
lcd: /boot/autoexec_pli.dat
lcd: /boot/zImage.elf
detected jffs2 blocksize: 16kb
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
dreamupd initialized
Scanning JFFS2 FS: . | / - \ | / - \ |  done.

find_inode failed for name=zImage.elf

load: Failed to find inode

no valid boot source found. press any key to enter setup.
lcd: *** STOP ***
c


where autoexec_pli.bat is the file boot setuo, it is also in the first partition of usb stick.
 
A

androsat

Registered
Messages
5
Hello to all,
Dear hemispherical1, I made all of the steps as detailed, in your perfect manual, in the last step to make a autoexec.bat I stacked.
The image to extract based on O.E 2.0, and extract to the usb partition sdb2, in that partition was a folder /boot who include two (2) autoexec files, one was autoexec.bat and the second one autoexec_dmb00se.bat with the following data:
autoexec.bat
/boot/bootlogo-dm800se.elf.gz filename=/boot/bootlogo-dm800se.jpg
/boot/vmlinux-3.2-dm800se.gz root=/dev/mtdblock3 rootfstype=jffs2 rw console=ttyS0,115200 debug
autoexec_dm800se.bat
/boot/bootlogo-dm800se.elf.gz filename=/boot/bootlogo-dm800se.jpg
/boot/vmlinux-3.2-dm800se.gz root=/dev/sdb2 rootdelay=10 rw console=ttyS0,115200

Do you have any idea to who off them edit and copy in the boot partition sdb1 with the correct editing sequence to make a correct boot from USB??
androsat
 
C

cokesux

Registered
Messages
190
The /boot/autoexec file is used for booting from flash I believe, autoexec_dm800se.bat is the closer of the 2 for USB, but neither are correct for booting from USB.

I would think:

/boot/vmlinux-3.2-dm800se.gz root=/dev/sdb2 rootdelay=10 rw console=ttyS0,115200

would need to be changed to something like:

/usb/vmlinux-3.2-dm800se.gz root=/dev/sdb2 rootdelay=10 rootfstype=ext3 rw console=ttyS0,115200

... and copied to sdb1, assuming that vmlinux-3.2-dm800se.gz is the name of your kernel in sdb1(usb), sdb2 is the root (/) partition on USB, and you're using the ext3 filesystem, if not change to correct filesystem, ext4, reiserfs, etc...


... If that was what you were asking?

--
 
A

androsat

Registered
Messages
5
Thanks my friend,

I try to make the corrections and I post the result, after editing the above autoexec_dm800se.bat file, what happened with the other 2 autoexec files in sdb2/boot folder, I keep them without any action or editing?

androsat
 
C

cokesux

Registered
Messages
190
You should be able to leave them untouched, your box will be booting from the one on sdb1/vfat partition, not /boot...

--
hemi
 
A

androsat

Registered
Messages
5
My fied,
evrything is ok the autoexec edited file was correct and the system booting for the usb flash.

thanks for your help.

androsat
 
You must log in or register to reply here.
Top