Re: Qi
2009/1/31 Andy Green a...@openmoko.com: So need to remove what you have in partition 1, and add a kernel named /boot/uImage-GTA02.bin into partition 2 (since that's your rootfs), which should be ext2 or better ext3. Thanks. The Debian installer had put the kernel in the root of /dev/mmcblk0p1, not in a boot subdirectory. I added a boot subdirectory with symlinks to the kernel and now it's all working. Why is the journalling of ext3 better? Would the kernel also be better off in an ext3 fs? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qi
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | 2009/1/31 Andy Green a...@openmoko.com: | So need to remove what you have in partition 1, and add a kernel named | /boot/uImage-GTA02.bin into partition 2 (since that's your rootfs), | which should be ext2 or better ext3. | | Thanks. The Debian installer had put the kernel in the root of | /dev/mmcblk0p1, not in a boot subdirectory. I added a boot | subdirectory with symlinks to the kernel and now it's all working. | | Why is the journalling of ext3 better? Would the kernel also be better Ext3 is better IMO because it can soak up a lot of casual damage that ext2 can't. With my usage pattern I am randomly powering things off all the time I appreciate how ext3 never makes any difficulty for me about that. Whereas after a day of it ext2 is on its knees. | off in an ext3 fs? Splitting the kernel off in its own private partition is an aberration we introduced because ext2 parser in U-Boot was broken for a while. So we had to make do with a VFAT partition first that U-Boot could parse, then an ext2 one after that contained the rootfs. But it makes trouble for updating the kernel in the case you have multiple rootfs, and makes it possible to get your kernel and modules out of sync. It's an ugly kludge. So the optimum situation is that the kernel is coming out of the same filesystem that is the root filesystem, the package update for it is simply to put in it /boot on current root filesystem which is easiest for the package system. It also readily allows different kernels in different rootfs if you are making an SD with multiple rootfs. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmErpcACgkQOjLpvpq7dMqjgQCdEstuzymmhmo8rMts3BB9cCa6 rAQAmwQI6bnr2ceW952zE8el5zL0dDC+ =mdqv -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: GTA01 Battery loader problem
Matthias Barmeier escreveu: Chris Syntichakis schrieb: Hi, How long do you have this battery? Maybe its lost the capacity... I think you could dis-charge it completely (maybe using an external battery dis-charger) and then recharge again (on the openmoko, a bit tricky , eh?) I will try. Don't. Discharging the battery completely will make its protection circuit cut off, making it much harder to restore (LiIon batteries are not supposed to be discharged too much, it damages them). In fact, that is probably precisely what happened: the GTA01 did not switch to the correct charging mode (because it needs to be able to power on to do so), and discharged the battery too much. The way to recover from it on GTA01 is to jump-start the battery (since the GTA01 cannot boot only on USB power, which would allow enabling the charger), which is not a recommended thing to do (and might in fact be dangerous). -- Cesar Eduardo Barros ces...@cesarb.net cesar.bar...@gmail.com ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qi
2009/1/31 Andy Green a...@openmoko.com: Ext3 is better IMO because it can soak up a lot of casual damage that ext2 can't. With my usage pattern I am randomly powering things off all the time I appreciate how ext3 never makes any difficulty for me about that. Whereas after a day of it ext2 is on its knees. OK. You've convinced me. Is there a way of backing up /dev/mmcblk0p2, repartitioning the uSD with one partition, formatting it to ext3, and restoring the backup? Or is it quicker to wipe, repartition, format and install from scratch? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qi
2009/2/1 Jeffrey Ratcliffe jeffrey.ratcli...@gmail.com 2009/1/31 Andy Green a...@openmoko.com: Ext3 is better IMO because it can soak up a lot of casual damage that ext2 can't. With my usage pattern I am randomly powering things off all the time I appreciate how ext3 never makes any difficulty for me about that. Whereas after a day of it ext2 is on its knees. OK. You've convinced me. Is there a way of backing up /dev/mmcblk0p2, repartitioning the uSD with one partition, formatting it to ext3, and restoring the backup? Or is it quicker to wipe, repartition, format and install from scratch? You can convert an ext2-fs to an ext3-fs rather easy. There are several examples on the web, like this: http://www.troubleshooters.com/linux/ext2toext3.htm (boot the nand-system and convert it from there). And while you're on the converting trip: convert your obsolete mmcblk0p1 into a swap partition: mkswap /dev/mmcblk0p1 swapon /dev/mmcblk0p1 For easiness, put it into your /etc/fstab on both nand and sd-card system: /dev/mmcblk0p1 swapswapauto,pri=1 0 0 ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
micro sh
I bought a 4gb SDHC card, and it is not recognized. I thought I read on this list that it is supported. Is there something I need to do before fdisk? output below. Thanks Seth r...@om-gta02:~# fdisk /dev/mmcblk0 fdisk: cannot read from /dev/mmcblk0 r...@om-gta02:~# r...@om-gta02:~# uname -a Linux om-gta02 2.6.24 #1 PREEMPT Thu Nov 6 02:57:37 CST 2008 armv4tl unknown r...@om-gta02:~# dmesg | grep mmcbl (duplicate lines trimmed) [ 38.775000] mmcblk0: error -110 sending read/write command [ 38.78] end_request: I/O error, dev mmcblk0, sector 0 [ 38.78] Buffer I/O error on device mmcblk0, logical block 0 [ 38.845000] mmcblk0: error -84 sending read/write command [ 38.85] end_request: I/O error, dev mmcblk0, sector 0 [ 38.85] Buffer I/O error on device mmcblk0, logical block 0 [ 2702.90] mmcblk0: error -110 sending read/write command [ 2702.905000] end_request: I/O error, dev mmcblk0, sector 0 [ 2702.905000] Buffer I/O error on device mmcblk0, logical block 0 r...@om-gta02:~# r...@om-gta02:~# modprobe s3cmci modprobe: module s3cmci not found modprobe: failed to load module s3cmci This has been fixed in commits 2831 (for 2.6.21.x) and 2832 (for 2.6.22.x). ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
