Hi Nikolaus,
Subject: Re: [Mipsbook-devel] Recovery image/procedure for the Letux 400
From: h...@goldelico.com
Date: Thu, 26 Aug 2010 10:25:43 +0200
CC: wolfg...@peerworld.at; mipsbook-devel@linuxtogo.org
To: r_vi...@hotmail.com
Hi,
Am 25.08.2010 um 22:58 schrieb Ruben Viets:
Hi,
On the trendtac the /dev/mtd3 can be automatic overwritten during startup
(minifs.img on SD card +left fn , left shift + right shift. this will give
blank screen and copies minifs to /dev/mtd3) The old minifs.img works correctly
for kernel 2.4.20.
It should be the same for the Letux 400 - at least with my tests. But there may
be some subtle differences.
The problem is that there are at least two different hardware revisions of the
same
motherboard (different in RTC, power management PIC). One of my sample devices
even has a LED on the left side of the LCD that appears to indicate WiFi status.
Manual steps for /dev/mtd3 recovery. [only 5MB size, even less when having bad
blocks]
When it is mounted as yaffs you get 100% use, and it corrupts jffs2 data..
Yes, the minifs is a jffs2 so you can't mount it as yaffs and it gets damaged.
You must specify the -t jffs2 parameter explicitly.
What is worse: the automounter can't distinguish and falls back to yaffs2.
If that happened. erase it with ./flash_eraseall /dev/mtd3
Afterwards you can mount -t jffs2 /dev/mtdblock3 /mnt/mtd3
This will give you the possibility to write your own files to /mnt/mtd3.
It is much better to write the raw disk image than files. I.e. you can#t write
the minifs.img
to /mnt/mtd3.
What you should do is *not mount* and:
cp minifs.img /dev/mtd0
You mean /dev/mtd3 right. This fails in my case because of the bad blocks.
There could be the problem that because of bad blocks there is not enough size
to write minifs, then dd will not work. (I have only 1664 bytes available ;-( )
To get it working then I should reduce the minifs.img to < 1.6MB.
Ah, that could be a hint why it does not yet work for Wolfgang. There may be a
bad block
in the minifs partition. And I think the flashing algorithm of U-Boot
(Fn+Shift+Shift) is
not intelligent enough to handle that.
I think we cannot fix the bad blocks, nandflash is nok.
For kernel 2.6.24.3 need some additional fixes.
- need update minifs.img file to work on new kernel (add the correct /dev/
parts from our new kernel, change startup /etc/init.d/modules)
And, it needs much more work. All the binaries and libs have to be updated.
old binaries will work on new kernel. Only /dev/ and some mount scripts have to
be updated.
What I have near the ./postinst script is a ./minifs script which copies the
most important binaries
from Debian to a directory from which we could make a new minifs.
But it is not working and is missing all scripts to do something useful. It
simply should open
a shell on the console.
Yes linuxrc linked to /bin/busybox + /etc + correct /dev + /lib +
/etc/init.d/start script should be enough.
- Update kernel startup key's to be changed to boot /dev/mtd3 as jffs2 when
pressing F3. (instead of yaffs, this will corrupt jffs2)
That is a good idea. But I don't know if the kernel rootfs startup code is
capable of handling a given
file system type or if it is automounting.
Should be possible.
I think just add fs_names_setup("jffs2") to F3 key mount.
(arch/mips/jz4730/board-minipc.c)
- Additional we could use the second nand /dev/mtd5 as recovery and boot it
with F5.
Grt Ruben.
To: h...@goldelico.com; wolfg...@peerworld.at
Date: Wed, 25 Aug 2010 15:49:48 +0000
From: wolfg...@peerworld.at
CC: mipsbook-devel@linuxtogo.org
Subject: Re: [Mipsbook-devel] Recovery image/procedure for the Letux 400
Hi Nikolaus ,
i tried the steps again, using my SD which cotains uImage and minifs.img.
But still no F3 Recovery menu :-(
do you think, using 'dd' to copy the minifs.img to /dev/mtd3 from my SD -
debian (lenny) ?
Yes, please try.
What you could also do is xxd /dev/mtd3 | more
This should show some file system structure (bin, lib, bash etc.). If not,
flashing wasn't successful.
I mounted the /dev/mtdblock3 and checked the content. But ls -la shows only
lost+found and "df -k" show 100% usage .
But maybe this device is not readable using normal mount (who knows)
You should mount as -t jffs2 or a new (empty) yaffs2 will be installed. But df
shows that it is full. So something is broken (or
yaffs2 doesn't report file system sizes correctly).
BR,
Nikolaus _______________________________________________
Mipsbook-devel mailing list
Mipsbook-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/mipsbook-devel
