How stupid I was to choose vfat for /boot. Now I can't change it to ext2, despite: http://wiki.debian.org/DebianOnFreeRunner http://pkg-fso.alioth.debian.org/freerunner/install.sh http://wiki.openmoko.org/wiki/Flashing_the_Neo_FreeRunner http://pkg-fso.alioth.debian.org/freerunner/configure-uboot.sh http://paste.ubuntuusers.de/raw/391456/
One thinks: I'll move the files out of the vfat /boot, run mkfs.ext2, put them back there, run the scripts above, and reboot. Sorry. You'll just end up, if you're lucky, running mkfs.vfat from the Openmoko Corp. kernel to hope and put your Debian world back into bootable state. Adventure #1, http://pkg-fso.alioth.debian.org/freerunner/configure-uboot.sh http://paste.ubuntuusers.de/raw/391456/ etc. Dumping current uboot environment dfu-util - (C) 2007 by OpenMoko Inc. This program is Free Software and has ABSOLUTELY NO WARRANTY Opening USB Device 0x0000:0x0000... Claiming USB DFU Runtime Interface... Determining device status: state = appIDLE, status = 0 Device really in Runtime Mode, send DFU detach request... Resetting USB... Opening USB Device... Found Runtime: [0x1d50:0x5119] devnum=9, cfg=0, intf=0, alt=2, name="u-boot_env" Claiming USB DFU Interface... Setting Alternate Setting ... Determining device status: state = dfuIDLE, status = 0 dfuIDLE, continuing Transfer Size = 0x1000 Merging debian menu entries into uboot environment Writing back uboot environment dfu-util - (C) 2007 by OpenMoko Inc. This program is Free Software and has ABSOLUTELY NO WARRANTY Opening USB Device 0x0000:0x0000... Found Runtime: [0x1d50:0x5119] devnum=9, cfg=0, intf=0, alt=2, name="u-boot_env" Claiming USB DFU Interface... Setting Alternate Setting ... Determining device status: state = dfuERROR, status = 14 dfuERROR, clearing status <-----Gosh, an ERROR?! Determining device status: state = dfuIDLE, status = 0 dfuIDLE, continuing Transfer Size = 0x1000 bytes_per_hash=5242 Starting download: [###################################################] finished! state(2) = dfuIDLE, status(0) = No error condition is present<-----Gosh, No error afterall, maybe Done! Done modifying uboot environment Restart and enjoy Enjoy not being able to boot into Debian. Adventure #2, now booted into the only kernel left, the OpenMoko Inc. kernel, # ./install.sh mount uboot Running stage mount Mounting the newly created system I: microSD card partitions mounted I: Done with stage mount Running stage uboot Modifying U-Boot bootloader menu * Checking for a sane MTD configuration * Mounting /dev inside the chroot at /mnt/debian * Dumping current U-Boot environment ECC failed: 0 ECC corrected: 0 Number of bad blocks: 0 Number of bbt blocks: 0 Block size 131072, page size 2048, OOB size 64 Dumping data starting at 0x00000000 and ending at 0x00040000... * Merging Debian menu entries into U-Boot environment (can take up to 70s) * Writing back U-Boot environment Erasing 128 Kibyte @ 20000 -- 50 % complete. Writing data to block 0 Writing data to block 20000 * Unmounting /dev I: U-Boot environment modified I: Done with stage uboot Anyway, in both Adventures, the boot menu still says "vfat+ext2", so (dear user,) you had better restore your vfat+ext2 former set up if booting is important to you. _______________________________________________ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
