MAT: Boxtyp anfragen

[morly]

dachte ich, dann noch bitte ersten Teil meiner Frage beantworten

[intik]

Per Telnet ?
root@vusolo:~# /media/hdd/AT_MORLY/bin/ubiformat -v ubiformat: error!: MTD device name was not specified (use -h for help)
root@vusolo:~#

[morly]

ja genau, sehr gut, dann folgendes:

/media/hdd/AT_MORLY/bin/ofgwrite -v

[intik]

ofgwrite Utility v1.9.2
Author: Betacentauri
Based upon: mtd-utils-native-1.4.9
Use at your own risk! Make always a backup before use!
Don't use it if you use multiple ubi volumes in ubi layer!

/media/hdd/AT_MORLY/bin/ofgwrite: invalid option -- 'v'
Usage: ofgwrite <parameter> <image_directory>
Options:
-k --kernel flash kernel with automatic device recognition(default
-kmtdx --kernel=mtdx use mtdx device for kernel flashing
-r --rootfs flash rootfs with automatic device recognition(default
-rmtdy --rootfs=mtdy use mtdy device for rootfs flashing
-n --nowrite show only found image and mtd partitions (no write)
-q --quiet show less output
-h --help show help
root@vusolo:~#

[morly]

sehr gut, weiter gehts.
sicher stellen, dass e2 gekillt ist, dann:

ls -l /media/hdd/AT_MORLY
/media/hdd/AT_MORLY/bin/ofgwrite --rootfs=/dev/mtd0 /media/hdd/AT_MORLY/

[intik]

root@vusolo:~# ls -l /media/hdd/AT_MORLY
drwxr-xr-x 2 1000 1000 4096 Jul 31 14:11 bin
-rw-r--r-- 1 root root 4063232 Jan 1 1970 kernel_cfe_auto.bin
drwxr-xr-x 2 1000 1000 4096 Jul 31 14:11 lib
drwxr-xr-x 2 root root 4096 Sep 21 11:47 morly_tmp
-rw-r--r-- 1 root root 0 Jan 1 1970 root_cfe_auto.bin
root@vusolo:~# /media/hdd/AT_MORLY/bin/ofgwrite --rootfs=/dev/mtd0 /media/hdd/AT
_MORLY/


ofgwrite Utility v1.9.2
Author: Betacentauri
Based upon: mtd-utils-native-1.4.9
Use at your own risk! Make always a backup before use!
Don't use it if you use multiple ubi volumes in ubi layer!


Searching image files in /media/hdd/AT_MORLY/
Found rootfs file: /media/hdd/AT_MORLY/root_cfe_auto.bin
Found kernel file: /media/hdd/AT_MORLY/kernel_cfe_auto.bin


Found /proc/mtd entries:
Device: Size: Erasesize: Name: Image:
mtd0: 07400000 00020000 "rootfs" -> /media/hdd/AT_MORLY/root
_cfe_auto.bin
mtd1: 00400000 00020000 "kernel" -> /media/hdd/AT_MORLY/kern
el_cfe_auto.bin
mtd2: 00400000 00020000 "boot"
mtd3: 00100000 00020000 "cfe"
mtd4: 00080000 00020000 "mac"
mtd5: 00080000 00020000 "env"
mtd6: 00100000 00020000 "nvm"
Using kernel mtd device: /dev/mtd1
Using rootfs mtd device: /dev/mtd0


Found UBIFS


Switching to user mode 2
nmbd: no process found
smbd: no process found
rpc.mountd: no process found
rpc.statd: no process found
sh: /etc/init.d/softcam: not found
CCcam: no process found
hddtemp: no process found
transmission-daemon: no process found
Syncing filesystem
Remounting rootfs read-only
Found NAND flash
Flashing rootfs: ubiformat /dev/mtd0 -f /media/hdd/AT_MORLY/root_cfe_auto.bin
ubiformat: mtd0 (nand), size 121634816 bytes (116.0 MiB), 928 eraseblocks of 131
072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 927 -- 100 % complete
ubiformat: 926 eraseblocks have valid erase counter, mean value is 1
ubiformat: 2 bad eraseblocks found, numbers: 607, 782
Floating point exception
root@vusolo:~#

[morly]

mach bitte vorher:

init 2; killall nmbd; killall smbd; killall rpc.mountd; killall rpc.statd; sync

[intik]

root@vusolo:~# init 2; killall nmbd; killall smbd; killall rpc.mountd; killall r
pc.statd; sync
nmbd: no process found
smbd: no process found
rpc.mountd: no process found
rpc.statd: no process found
root@vusolo:~#

[morly]

wie lange dauerte der Befehl in #126?
war danach ein neues Image geflasht oder startete die Box nicht mehr? oder blieb das alte?

[intik]

am TV, sehe ich Flashing Rootfs balken, nur bis mitte, und dann geht es nicht mehr weiter, muss dann schalter von hinten einschalten.