Hi all,
Am 26.04.2010 um 19:12 schrieb Dr. H. Nikolaus Schaller:
Hi Ruben,
Am 25.04.2010 um 14:38 schrieb Dr. H. Nikolaus Schaller:
Am 25.04.2010 um 11:29 schrieb Dr. H. Nikolaus Schaller:
Ha - it works!
It was indeed a typo. And, I have reverted the change of
root_device_name in do_mounts.c because that appeared to be a
duplicate when the boot args are overwritten.
On ext3 I have tried a debian etch rootfs and I can login! Great!
Now I have to find out how to connect ethernet/wlan to install
more packages and get Debian to run a Xserver...
And, of course - upgrade to a Debian Lenny rootfs first.
I have now installed a debian lenny, but I could not yet log in. I
think I am missing some important pre-configuratiion after building
the debootstrap. It just gives a short warning: unable to open an
initial console.
I have found that I had produced the lenny bootstrap image with
debootstrap --foreign which requires to finalize the bootstrap on
the target machine. But since I can't log in yet, I can' complete :)
There appears to be a trick to manually predefine some important
files (/etc/inittab, /etc/fstab, /etc/network/interfaces). Has
somebody already done such a cross-bootstrap?
That did not work unfortunately. The second-stage of debootstrap
appears to do more than just creating some config files. So I am
halfway stuck.
Therefore I tried what is described everywhere: take a machine with
the right architecture and chroot into the new image and run
debootstrap --second-stage.
Unfortunately this does not work on our mipsbooks. The reason is that
it runs a 2.4 kernel (which isn't upgraded by chroot :). And the
debian lenny chroot is a 2.6 system. Therefore some libraries are not
compatible and the error message is simply: FATAL: kernel too old.
So does anyone have a working debian lenny rootfs for mipsel
available? Or is there a trick to bootstrap from 2.4 to 2.6 systems?
BTW: something went wrong with my experiments and I can only start
the new kernel from SD by pressing fn+shift+ctrl. But I can't boot
the original system any more. What is worse, even the recovery
installation does no longer work when pressing F3 (the screen blinks
and blurs out). The only effect I can achieve is by pressing FN and
some other key. This makes the two green led on the right side blink
until I release the buttons. Any ideas on that?
I was not yet able to find a fix for this yet. So only one mipsbook is
working (with the old Skytone system) while the other one can just
boot the new kernel.
BR,
Nikolaus
_______________________________________________
Mipsbook-devel mailing list
Mipsbook-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/mipsbook-devel
