Hi Ruben,
I will work through all your comments later...
3) Some general comments on compiling mods:
3a)
For the depmod modules the letux-400 sources compiles with 2.6.24.3-
xxxxxxxx-dirty.
Changing include/config/kernel.release and /include/linux/
utsrelease.h does not help.
I overruled it by changing below line in the Makefile:
KERNELRELEASE = $(shell cat include/config/kernel.release 2> /dev/
null)
to
KERNELRELEASE = 2.6.24.3
3b)
Mipsel gcc 4.3 and 4.4 give sometimes compiling errors on debian-
mipsel-lenny distro's.
So I modified below part to compile with 4.1.2
CC = $(CROSS_COMPILE)gcc -V 4.1
I am not sure how this is intended to work (and I have changed
nothing). The effect is that one gets kernel/module versions tagged by
git commit number. So, if you clone you will get a new git HEAD -
until you push. This means that this will change from time to time.
And 'dirty' appears to mean that there are uncommitted changes in the
local git clone (which appears if you change CONFIG).
My solution is that I copy uImage AND modules to the target machine
and run depmod -a once after booting.
5) If your nand distro is damaged easiest way is to restore via
regular recovery
Yes, I know all these descriptions and Recovery*.img files but it is
not the rootfs that is damaged but either the kernel or the recovery
procedure itself. Because of that I have learned some more how that
works (see my other mail).
The only thing I could not find yet is how the F3 key is recognized
and who displays the Boot splash.
BR,
Nikolaus
_______________________________________________
Mipsbook-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/mipsbook-devel
