Re: Partitioning 4GB with the Debian Installer
but when I run './install all' I still get: Writing superblocks and filesystem accounting information: Warning, had trouble writing out superblocks.done doesn't sound good. if I try './install mount' I get: [errors] well, w/o superblocks mounting doesn't work Also, if I just end up partitioning this from my desktop machine, should I make a 8mb ext2 and the rest ext3? for the installer that's the default, i guess. if you change the layout you will have to mount manually before proceeding, since the installer (imo) would not know about separate partitions for usr, var, ... re the filesystems: the u-boot has an entry for fat+ext2 -- either you change taht/ add an entry for ext2+ext3 or you use fat+ext2. secondly, the installer assumes ext2 imo, since etx3 is not recommended for sd card. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Partitioning 4GB with the Debian Installer
arne anka wrote: secondly, the installer assumes ext2 imo, since etx3 is not recommended for sd card. That sounds interesting. I partitioned my 8gb sd-card to use ext3 for the rootfs and added an extra bootmenu entry for ext3. But why is ext3 not recommended for sd-card when compared to ext2? I played with debian on my sd card for over a week without any problems so far concerning the sd-card. I hope i must not backup my rootfs and reformat it to ext2. :) Ciao, Rainer ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Partitioning 4GB with the Debian Installer
But why is ext3 not recommended for sd-card when compared to ext2? i understood ist because of the additional wear caused by journalling. I played with debian on my sd card for over a week without any problems so far concerning the sd-card. I hope i must not backup my rootfs and reformat it to ext2. :) well, ext3 is ext2+journal. should be sufficient to mount as ext2, i think. not sure about u-boot, though. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Partitioning 4GB with the Debian Installer
arne anka wrote: But why is ext3 not recommended for sd-card when compared to ext2? i understood ist because of the additional wear caused by journalling. I played with debian on my sd card for over a week without any problems so far concerning the sd-card. I hope i must not backup my rootfs and reformat it to ext2. :) well, ext3 is ext2+journal. should be sufficient to mount as ext2, i think. not sure about u-boot, though. I know that ext2 issufficient but ext3 is the successor, so why stick with the older ext2? When ext3 makes much more accesses to the filesystem than ext2 you are right that it is not the best choice for the limited lifecycle that a flash medium has. Maybe i should google a bit about this to find a comparision table for ext2 against ext3 to make a better decision. :) Ciao, Rainer ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Partitioning 4GB with the Debian Installer
arne anka ha scritto: But why is ext3 not recommended for sd-card when compared to ext2? i understood ist because of the additional wear caused by journalling. Yes, in most cases ext3 is used improperly: ext3 is basically ext2+journal. This means that you are going to add some overhead to the data that you are writing (journal) producing more i/o gaining no new feature. You are using no such feature because improperly unmounting an ext2 or ex3 partition will sort the same effect, you will lose your data. Someone may say hey but you got the journal, yes you've got it but where is it written? in the same place of the fs? usually yes, this means that if you unplug the sd the data and the journal are unplugged at the same time so your data are still lost. Well you can do something better mounting the journal in a different support but unplugging the sd will still result in a data lost, the inode and filesystem structure could survive because of the journal but the real data will be lost. So after this explanation the advantages in using a journaled fs vs another one are so low that is not convenient. This is what i've understood reading around, may be something is wrong but the idea should be something like that. Pietro ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Partitioning 4GB with the Debian Installer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan Fröbe wrote: Depends on what you call straight-forward: you can search for glamo_mci.sd_max_clk , a description can for instance be found at http://docs.openmoko.org/trac/ticket/1743 : Basically you need to set this variable in the u-boot environment - I reduced it even down to 500 , but more might also work - ymmv. Whether setting this through /sys parameter works I do not know - does anyone know? Alright, I edited my uboot environment so that /proc/cmdline reads: glamo_mic.sd_max_clk=500 rootfstype=jffs2 root=/dev/mtdblock6 console=ttySAC2,115200 console=tty0 loglevel=4 regular_boot mtdparts=physmap-flash:-(nor);neo1973-nand:0x0004(u-boot),0x0004(u-boot_env),0x0080(kernel),0x000a(splash),0x0004(factory),0x0f6a(rootfs) but when I run './install all' I still get: Writing superblocks and filesystem accounting information: Warning, had trouble writing out superblocks.done if I try './install mount' I get: Running stage mount Mounting the newly created system mount: wrong fs type, bad option, bad superblock on /dev/mmcblk0p2, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so 'dmesg | tail' reads: end_request: I/O error, dev mmcblk0, sector 19752 end_request: I/O error, dev mmcblk0, sector 19760 end_request: I/O error, dev mmcblk0, sector 19768 end_request: I/O error, dev mmcblk0, sector 19776 end_request: I/O error, dev mmcblk0, sector 19784 glamo-mci glamo-mci.0: Error after cmd: 0x8020 mmcblk0: error -110 sending read/write command end_request: I/O error, dev mmcblk0, sector 15682 EXT2-fs: unable to read superblock Any ideas? Thanks for the help. Also, if I just end up partitioning this from my desktop machine, should I make a 8mb ext2 and the rest ext3? Thanks. - -Greg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFItccdR7UPrMLya90RArLNAKChTLp4dOM7zoJVVP+MdIoPh/ELYQCfV7qw db2Kd2wUpNTMCM1go1czJjU= =vZRC -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Partitioning 4GB with the Debian Installer
I found that lowering the glamo MMC clock by a factor of 1/2 repeatedly, until I found a stable clock speed, worked fine for me. I'm not sure how to do that. Is it pretty straight forward? Thanks. -Greg ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Partitioning 4GB with the Debian Installer
Hi, Am Donnerstag, den 21.08.2008, 15:48 -0500 schrieb Greg Bonett: Unfortunately I'm working with the 512mb SD card that came with my FR (install.sh had trouble partitioning my 4gb SDHC) so I haven't been able to install too many aps Actually, the install.sh should be able to handle that as well, at least theoretically. What problems did you have? Greetings, Joachim -- Joachim nomeata Breitner Debian Developer [EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeata signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Swap Space was Re: Partitioning 4GB with the Debian Installer
On Fri, Aug 22, 2008 at 5:02 AM, Joachim Breitner [EMAIL PROTECTED] wrote: Hi, Actually, the install.sh should be able to handle that as well, at least theoretically. What problems did you have? Greetings, Joachim When the installer partitions the disk, why does it not supply a swap partition? Is it needed or not needed by Debian? thanks clare ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Partitioning 4GB with the Debian Installer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joachim Breitner wrote: Hi, Am Donnerstag, den 21.08.2008, 15:48 -0500 schrieb Greg Bonett: Unfortunately I'm working with the 512mb SD card that came with my FR (install.sh had trouble partitioning my 4gb SDHC) so I haven't been able to install too many aps Actually, the install.sh should be able to handle that as well, at least theoretically. What problems did you have? Alright, here it is... When I run './install.sh all' it runs through the partition step (but does not continue) and gives this output before quiting: W: /dev/mmcblk0p1 is mounted, unmounting 1+0 records in 1+0 records out Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel Building a new DOS disklabel. Changes will remain in memory only, until you decide to write them. After that the previous content won't be recoverable. The number of cylinders for this disk is set to 125440. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Warning: invalid flag 0x00,0x00 of partition table 4 will be corrected by w(rite) Command (m for help): Command action e extended p primary partition (1-4) Partition number (1-4): First cylinder (1-125440, default 1): Using default value 1 Last cylinder or +size or +sizeM or +sizeK (1-125440, default 125440): Command (m for help): Command action e extended p primary partition (1-4) Partition number (1-4): First cylinder (246-125440, default 246): Using default value 246 Last cylinder or +size or +sizeM or +sizeK (246-125440, default 125440): Using default value 125440 Command (m for help): The partition table has been altered! Calling ioctl() to re-read partition table * Waiting for partitions to appear * Partition table created W: /dev/mmcblk0p1 is mounted, unmounting * Formatting the microSD card partitions mke2fs 1.38 (30-Jun-2005) Filesystem label= OS type: Linux Block size=1024 (log=0) Fragment size=1024 (log=0) 1960 inodes, 7832 blocks 391 blocks (4.99%) reserved for the super user First data block=1 1 block group 8192 blocks per group, 8192 fragments per group 1960 inodes per group Writing inode tables: done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 34 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. mke2fs 1.38 (30-Jun-2005) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 500960 inodes, 1001560 blocks 50078 blocks (5.00%) reserved for the super user First data block=0 31 block groups 32768 blocks per group, 32768 fragments per group 16160 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736 Writing inode tables: done Writing superblocks and filesystem accounting information: Warning, had trouble writing out superblocks.done This filesystem will be automatically checked every 33 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. If I try and run './install.sh mount' I get the following error: Running stage mount Mounting the newly created system mount: wrong fs type, bad option, bad superblock on /dev/mmcblk0p2, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so dmesg | tail gives: glamo-mci glamo-mci.0: Error after cmd: 0x20 mmcblk0: error -110 sending read/write command end_request: I/O error, dev mmcblk0, sector 0 glamo-mci glamo-mci.0: Error after cmd: 0x8020 mmcblk0: error -110 sending read/write command end_request: I/O error, dev mmcblk0, sector 0 glamo-mci glamo-mci.0: Error after cmd: 0x20 mmcblk0: error -110 sending read/write command end_request: I/O error, dev mmcblk0, sector 1568 EXT2-fs: unable to read superblock I'm pretty sure this has something to do with th e problem: Warning, had trouble writing out superblocks.done (from initial ./install.sh all output) Thanks for taking a look at this. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIrhIcR7UPrMLya90RAmk2AKDIRQRue11ukU3YV9N9ElgrnGfNswCfZsL0 ilTG+IGwiyOqYcr6fZbWzTU= =f4ES -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
