Am 23.08.2010 um 17:00 schrieb Dr. H. Nikolaus Schaller: > > Am 22.08.2010 um 00:54 schrieb Andy Valencia: > >> -------- >> Ok... I can boot from that SD card, but not, apparently, any other way any >> more. But I typed fast and killed the init script before it shot down the >> system, so now I appear to have a 2.6 kernel running on what is apparently >> the 2.4 filesystem. >> >> The instructions say to bring up eth0 (done, works) and run "./postinst". >> There's no such file. Is there something subtly wrong, which is why I've >> booted up with the new kernel and an old root filesystem? > > Hi Andy, > did you install our Debian Lenny rootfs including the config.tgz > on the second partition? The latter provides the postinst file. > > Then, the 2.6 kernel and Debian should log in as root and > change the home directory to /root. There should be the postinst > file that completes the Lenny bootstrapping. > > In the meantime, I have tried to pull the original files from > /dev/mtd* on another machine - and now it can't start the > old 2.4 system. > > Therefore: we have a problem in our 2.6-kernel that appears > to (slightly?) damage the NAND flash contents even if the > mtd devices are NOT mounted. > > I hope that I can build the JTAG adapter next week so that we > will have progress with direct access to the flash and console. > > Nikolaus
Once again I have damaged one of the Mipsbooks by booting the 2.6 kernel from SD card. The device *did* boot into the Skytone system before I inserted the SD card, powered down, and powered on while pressing Shift+Fn+Ctrl. After that, the 2.6 kernel booted fine into Debian and I copied the /dev/mtd partitions (without mounting). After that, I did shut down, unplug the SD card with Debian and rebooted back to Skytone from internal NAND. Well, tried to reboot but it did not boot at all. Fortunately, this unit has a RS232 connector in the battery compartment so I could now trace the U-Boot messages: NAND SPL Starting U-Boot ... U-Boot 1.1.6 (Jun 24 2008 - 18:57:34) Board: Ingenic PMP Ver 1.x (CPU Speed 335 MHz) DRAM: 64 MB Flash: 0 kB NAND:1024 MiB *** Warning - bad CRC or NAND, using default environment In: serial Out: serial Err: serial Net: JZ ETHERNET ### main_loop: bootcmd="nboot 0x80600000 0 0x100000;bootm" Hit any key to stop autoboot: 0 Loading from NAND 1GiB 3,3V 8-bit, offset 0x100000 Image Name: Linux-2.6.24.3-g4f2821eb-dirty Image Type: MIPS Linux Kernel Image (gzip compressed) Data Size: 2225876 Bytes = 2.1 MB Load Address: 80010000 Entry Point: 803c1960 ## Booting image at 80600000 ... Image Name: Linux-2.6.24.3-g4f2821eb-dirty Image Type: MIPS Linux Kernel Image (gzip compressed) Data Size: 2225876 Bytes = 2.1 MB Load Address: 80010000 Entry Point: 803c1960 Verifying Checksum ... Bad Data CRC ### boot the second kernel in nand flash offset 0x200000 ...... Loading from NAND 1GiB 3,3V 8-bit, offset 0x280000 ** Bad Magic Number 0xffffffff ** ## Booting image at 80600000 ... Bad Magic Number ### boot the second kernel in nand flash offset 0x200000 ...... Loading from NAND 1GiB 3,3V 8-bit, offset 0x280000 The interesting thing is that it reports to find a Linux-2.6.24.3 image!!! Maybe, we have either a bug in our descriptions or did not correctly understand the U-Boot code for handling the modifier keys? It appears that booting with Fn+Ctrl+Shift installs the new kernel in NAND as a side-effect. Nikolaus _______________________________________________ Mipsbook-devel mailing list Mipsbook-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/mipsbook-devel
