Re: backing up rootfs fails - after 40m FreeRunner continues booting
Am Mo 20. April 2009 schrieb Cameron Frazier: On Mon, Apr 20, 2009 at 2:03 PM, Bram Mertens mertensb.ma...@gmail.com wrote: snip Have you tried using NeoTool [1]? It's always worked quite well for me, and the backing up process avoids dfu-util. [1] http://wiki.openmoko.org/wiki/NeoTool Huh, neotool avoids dfu-util? less +/dfu-util `which NeoTool` /j signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: backing up rootfs fails - after 40m FreeRunner continues booting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joerg Reisenweber wrote: Huh, neotool avoids dfu-util? less +/dfu-util `which NeoTool` /j neotool's *rootfs backup* avoids dfu-util. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFJ8ziWFbVnQRV3OEYRAr1hAJ9DeIsEqCQGHUpgKbKZG4TzT8aX+gCfSR7F drlCo8fKJI6jogLP6hlsON8= =qe7K -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: backing up rootfs fails - after 40m FreeRunner continues booting
Bram Mertens mertensb.ma...@gmail.com writes: On Tue, Apr 21, 2009 at 9:21 AM, Paul Fertser fercer...@gmail.com wrote: Any particular reason you omitted the list from Cc? Feel free to bring conversation back there, so everybody benefits. No reason, just hit reply like I did with all other posts. Only this time Gmail didn't address the list but you personally. Could have something to do with the fact that you wrote your reply to me and CC'd the list... That's how the mailing lists are supposed to work. Whenever you mean to send an answer to the mailing list, you're supposed to press Reply All (it can be called differently but the meaning is the same). That way you avoid accidentally sending a private e-mail to list btw. Moreover please take into account that the person you're writing a reply to may not be necessarily subscribed to the list (and everyone should be free to send mails to any list he desires to), so in case you reply to the list directly, the person you address might never receive it. Backing up the rootfs took about 10 minutes compared to +40 minutes with dfu-util and the complete image is merely 83M in size, whereas the file created by dfu-util is 247M when the backup is terminated due to the timeout! Does this mean that dfu-util backs up the entire disk (which according to the output below is approx the size of the resulting jffs2 image) and NeoTool only backs up the data that has been written? However even then 83M is less than what's reported in use. Or does NeoTool compress the data somehow? Yes, dfu-util doesn't care about filesystem, files etc, works on the whole NAND partition. And i guess with NeoTool you're using ssh actually. Perhaps (well actually likely) I'm missing something but as far as I understand you need a working distribution before you would be able to restore files via SSH. If your distro works at least somehow, you'll get ssh over usb access. If not, you can get a uSD image that works. Thanks again for the help, I'll play around some more tomorrow and will update the wiki based on your suggestions. Thank you, our wiki really needs to be more accurate. :) HTH -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: backing up rootfs fails - after 40m FreeRunner continues booting
Bram Mertens mertensb.ma...@gmail.com writes: So it looks like NAND U-Boot was updated but NOR hasn't. However http://wiki.openmoko.org/wiki/Backup#Backing-up_flash_images specifically states that you need to be in NOR U-Boot before flashing/backing up. Then the wiki is wrong. There's absolutely zero sense in backing up u-boot itself and other partitions are perfectly readable when you boot to NAND. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: backing up rootfs fails - after 40m FreeRunner continues booting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, To backup your rootfs with NeoTool: * Make sure you have a working image on your Neo. By 'Working', I mean it should boot into the GUI, and networking should work - you should be able to ssh into your neo. NeoTool is supposed to be pretty much idiot proof, so it should tell you if this isn't the case. * Boot your Neo all the way into the gui. (NeoTool's rootfs backup needs to use SSH, so your Neo should be completely booted, not at the boot menu) * Run NeoTool, choose backup, select 'Root Filesystem' when it prompts for what to backup, and choose 'Go!'. * you may be told that you don't have mkfs-jffs2 installed. If this happens, ssh into your neo and opkg install mkfs-jffs2 * the backup will take a while (maybe 20-30mins?). If you chose the default backup method (jffs2), the file it produces will be flashable using dfu-util or NeoTool. HTH, - -Dale Bram Mertens wrote: On Mon, Apr 20, 2009 at 9:39 PM, Cameron Frazier frazier.came...@gmail.com wrote: On Mon, Apr 20, 2009 at 2:51 PM, Bram Mertens mertensb.ma...@gmail.com wrote: On Mon, Apr 20, 2009 at 8:12 PM, Cameron Frazier frazier.came...@gmail.com wrote: On Mon, Apr 20, 2009 at 2:03 PM, Bram Mertens mertensb.ma...@gmail.com wrote: snip Have you tried using NeoTool [1]? It's always worked quite well for me, and the backing up process avoids dfu-util. [1] http://wiki.openmoko.org/wiki/NeoTool I have tried to use it before when I initially went to pick up the device but never succeeded, probably because we were using the wrong files. And the instructions seemed clear enough to use the command line utility. The current problems/questions would have arisen with NeoTool anyway, looks like I made a mistake when rebooting the device. So when you have flashed the U-Boot with NeoTool, how do you proceed? Unplug it first, power down, then boot again or use the boot menu to reboot? And did you boot the device normally or immediately into NOR or NAND? The display still shows the openmoko logo, guess I'll have to hard reset it though I hope that won't break anything... I've always just: - flashed - powered down, which the FR seems to do on it's own once u-boot times out - unplug the usb, as I've found that leaving it in will cause hangs similar to what your seeing (oddly I don't have this issue with the AC adapter) - turn on pre normal procedure (power button for 8-10 sec) I use NeoTool most times since I like the backup method (having had numerous problems with dfu-util backups) and it helps to ensure I'm not throwing improper commands when I flash. I have little faith in the user on my end. Thanks, I pulled the battery and booted into NOR, it still shows: U-Boot 1.3.2-moko12 (May 09 2008 - 10:28:48) select reboot from menu - FDOM boots. Shut down device to NAND boot menu. NAND boot menu shows: pr 19 2009 - 19:10:05)520a22715fe7ff069b36b7dfdbb925a8e5a (A So it looks like NAND U-Boot was updated but NOR hasn't. However http://wiki.openmoko.org/wiki/Backup#Backing-up_flash_images specifically states that you need to be in NOR U-Boot before flashing/backing up. After reading http://wiki.openmoko.org/wiki/Flashing_NOR I get the impression that flashing NOR is not really recommended compared to flashing NAND. I'll try with NeoTool since even with the new U-Boot a backup fails after 38minutes (while booted to NAND). Regards Bram ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFJ7YWDFbVnQRV3OEYRAhkjAKCbv651TqaoSJ9Jzy0z8T+hG8azqwCeO/P7 2M1cwNT9rbkdSqn2JZ46xY0= =20rP -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: backing up rootfs fails - after 40m FreeRunner continues booting
The display still shows the openmoko logo, guess I'll have to hard reset it though I hope that won't break anything... the logo is completely unrelated to u-boot or qi or whatever. it lives in its own partition and needs to be flashed on its own, if you wnat to change it. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: backing up rootfs fails - after 40m FreeRunner continues booting
On Tue, Apr 21, 2009 at 9:21 AM, Paul Fertser fercer...@gmail.com wrote: Hi, Any particular reason you omitted the list from Cc? Feel free to bring conversation back there, so everybody benefits. No reason, just hit reply like I did with all other posts. Only this time Gmail didn't address the list but you personally. Could have something to do with the fact that you wrote your reply to me and CC'd the list... On Tue, Apr 21, 2009 at 09:05:50AM +0200, Bram Mertens wrote: On Tue, Apr 21, 2009 at 8:33 AM, Paul Fertser fercer...@gmail.com wrote: Bram Mertens mertensb.ma...@gmail.com writes: So it looks like NAND U-Boot was updated but NOR hasn't. However http://wiki.openmoko.org/wiki/Backup#Backing-up_flash_images specifically states that you need to be in NOR U-Boot before flashing/backing up. Then the wiki is wrong. There's absolutely zero sense in backing up u-boot itself and other partitions are perfectly readable when you boot to NAND. OK, is there any reason why one would want to be in U-Boot in the NOR Flash for backing up instead of NAND flash? I guess no. For backing up you need a fixed u-boot anyway. And you can only update NAND u-boot. And NAND u-boot is loaded from NAND to RAM on start, so it can access any NAND partition for reading. It's recommended to use NOR u-boot to flash u-boot partition and also only NOR u-boot is available when one uses Qi. That said, i see no reason to use u-boot's backup facility at all, because if you can boot the device, you can scp or nc from it anyway. And if you can't boot from NAND for whatever reason, you can boot using any SD image and backup anything you need. Perhaps you can update the wiki page? If not I'll rephrase it to: As when flashing, you will need to be in [http://wiki.openmoko.org/wiki/Booting_the_Neo_FreeRunner#Log_into_U-Boot_in_the_NAND_Flash U-Boot in the NAND Flash]. I guess it's ok, go ahead. From what I understand the Booting_the_Neo_FreeRunner page could use an update as well. It only metions the possibility of flashing the device in the U-Boot in the NOR Flash section not in the NAND section. Yes, please update it. Nor does it metion backing up the device. It's not very useful anyway, see above. However the NOR section does have a comment that seems to be interesting: When flashing the device via USB connection, you must choose Set console to USB by pressing the AUX key until it is highlighted and then press the power button to select it. I flashed Qi many times from NOR u-boot, never did anything special (so i suspect this suggestion is wrong). Would this help prevent the timeout I get? No, NOR u-boot times out in 30 seconds anyway. You need to prepare everything beforehand and then start NOR to avoid hitting the timeout. On another note: Backing up using NeoTool failed last night becuase Reason I was unable to connect via SSH is that I included the MAC address in NetworkManager's configuration and the usb0 device received (or generated?) a new one. So this time I was able to create a backup of the kernel, the U-Boot and the rootfs using NeoTool (Thanks to Dale as well for a very clear step-by-step). Backing up the rootfs took about 10 minutes compared to +40 minutes with dfu-util and the complete image is merely 83M in size, whereas the file created by dfu-util is 247M when the backup is terminated due to the timeout! Does this mean that dfu-util backs up the entire disk (which according to the output below is approx the size of the resulting jffs2 image) and NeoTool only backs up the data that has been written? However even then 83M is less than what's reported in use. Or does NeoTool compress the data somehow? r...@om-gta02:~# df -h FilesystemSize Used Available Use% Mounted on rootfs 246.6M 92.9M153.7M 38% / /dev/root 246.6M 92.9M153.7M 38% / tmpfs40.0k 0 40.0k 0% /mnt/.exquisite udev 2.0M 12.0k 2.0M 1% /dev shmfs61.6M 12.0k 61.6M 0% /dev/shm /dev/mmcblk0p18.7M 3.8M 4.9M 44% /media/card volatile 61.6M368.0k 61.3M 1% /var/volatile I never understood why anything special can be needed if we already have ssh/scp. Therefore never used NeoTool. Perhaps (well actually likely) I'm missing something but as far as I understand you need a working distribution before you would be able to restore files via SSH. The point of this exercise for me is to back up the only distro that works for me so far - which is the distro that came with the device - before attempting to install anything else. My earlier attempts to install a distro to the SD card have not been very successful: the one distro that boots apparantely has a non-working dbus implementation or something meaning that few if any applications are actually useful. I was also unable to SSH into
Re: backing up rootfs fails - after 40m FreeRunner continues booting
On Mon, Apr 20, 2009 at 4:06 AM, Rask Ingemann Lambertsen r...@sygehus.dk wrote: On Mon, Apr 20, 2009 at 12:07:55AM +0200, Bram Mertens wrote: Hi, I'm about ready to flash a new distro onto the FreRuuner main memory but since it'll be the first time I wanted to try backing up the existing distro first. So I followed the steps on http://wiki.openmoko.org/wiki/Backup . Which version of U-Boot are you using? DFU Upload was broken at least until 2008-10-17. 2008-10-07 Harald Welte u-boot: Fix DFU upload in u-boot http://git.openmoko.org/?p=u-boot.git;a=commitdiff;h=414367bf5b65942947dd5d569c27d2a8e8e5e562 I wrote it down because I intended to include it... I'll check when I get back home but this date looks familiar. As for reducing the backup: I'm trying to create a backup of the initial image that came with the device so I'd like to avoid throwing stuff away. So the recommendation would be to update the U-Boot with: 1) backup exsitng U-Boot (http://wiki.openmoko.org/wiki/Backup): Boot NOR boto menu sudo ./dfu-util -a u-boot -R -U good-u-boot.bin sudo ./dfu-util -a u-boot_env -R -U good-u-boot_env.bin 2) flash U-Boot (http://wiki.openmoko.org/wiki/Flashing_the_Neo_FreeRunner#Flashing_the_boot_loader_to_the_NAND): dfu-util -a u-boot -R -D uboot.bin Reboot the device to use the new U-Boot but the following reminder is not very clear to me: Reminder: You should have boot from NOR first, in order to flash the boot-loader in NAND. After flashing succesfully, make sure you reboot from NAND's newly flashed boot loader, to benefit from the updates. Does this mean I simply have to reboot the FreeRunner to the NOR boot menu again, or do I have to boot to the NAND boot menu as well/instead? And from which boot menu should I continue backing up the device? From the NOR menu? Which u-boot.bin should I use? And where should I get it? Thanks in advance. Bram ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: backing up rootfs fails - after 40m FreeRunner continues booting
On Mon, Apr 20, 2009 at 11:17 AM, Bram Mertens mertensb.ma...@gmail.com wrote: On Mon, Apr 20, 2009 at 4:06 AM, Rask Ingemann Lambertsen r...@sygehus.dk wrote: On Mon, Apr 20, 2009 at 12:07:55AM +0200, Bram Mertens wrote: Hi, I'm about ready to flash a new distro onto the FreRuuner main memory but since it'll be the first time I wanted to try backing up the existing distro first. So I followed the steps on http://wiki.openmoko.org/wiki/Backup . Which version of U-Boot are you using? DFU Upload was broken at least until 2008-10-17. 2008-10-07 Harald Welte u-boot: Fix DFU upload in u-boot http://git.openmoko.org/?p=u-boot.git;a=commitdiff;h=414367bf5b65942947dd5d569c27d2a8e8e5e562 I wrote it down because I intended to include it... I'll check when I get back home but this date looks familiar. As for reducing the backup: I'm trying to create a backup of the initial image that came with the device so I'd like to avoid throwing stuff away. So the recommendation would be to update the U-Boot with: 1) backup exsitng U-Boot (http://wiki.openmoko.org/wiki/Backup): Boot NOR boto menu sudo ./dfu-util -a u-boot -R -U good-u-boot.bin sudo ./dfu-util -a u-boot_env -R -U good-u-boot_env.bin 2) flash U-Boot (http://wiki.openmoko.org/wiki/Flashing_the_Neo_FreeRunner#Flashing_the_boot_loader_to_the_NAND): dfu-util -a u-boot -R -D uboot.bin Reboot the device to use the new U-Boot but the following reminder is not very clear to me: Reminder: You should have boot from NOR first, in order to flash the boot-loader in NAND. After flashing succesfully, make sure you reboot from NAND's newly flashed boot loader, to benefit from the updates. Does this mean I simply have to reboot the FreeRunner to the NOR boot menu again, or do I have to boot to the NAND boot menu as well/instead? And from which boot menu should I continue backing up the device? From the NOR menu? Which u-boot.bin should I use? And where should I get it? Thanks in advance. Bram NOR boot menu shows: U-Boot 1.3.2-moko12 (May 9 2008 - 10:28:48) NAND boot menu shows: U-Boot 1.3.2-moko12 (Oct 7 2008 - 21:03:06) so I guess I need to update According to http://wiki.openmoko.org/wiki/U-boot the latest bootloader binary builds can be found under http://downloads.openmoko.org/distro/unstable/daily/ . Are these considered stable despite being in the unstable branch? Which version is recommended at this stage? The latest daily build (http://downloads.openmoko.org/distro/unstable/daily/om-gta02/20090420/) does not contain a uboot image. The one from 20090419 does. Regards Bram Mertens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: backing up rootfs fails - after 40m FreeRunner continues booting
On Mon, Apr 20, 2009 at 7:32 PM, Bram Mertens mertensb.ma...@gmail.com wrote: On Mon, Apr 20, 2009 at 11:17 AM, Bram Mertens mertensb.ma...@gmail.com wrote: On Mon, Apr 20, 2009 at 4:06 AM, Rask Ingemann Lambertsen r...@sygehus.dk wrote: On Mon, Apr 20, 2009 at 12:07:55AM +0200, Bram Mertens wrote: Hi, I'm about ready to flash a new distro onto the FreRuuner main memory but since it'll be the first time I wanted to try backing up the existing distro first. So I followed the steps on http://wiki.openmoko.org/wiki/Backup . Which version of U-Boot are you using? DFU Upload was broken at least until 2008-10-17. 2008-10-07 Harald Welte u-boot: Fix DFU upload in u-boot http://git.openmoko.org/?p=u-boot.git;a=commitdiff;h=414367bf5b65942947dd5d569c27d2a8e8e5e562 I wrote it down because I intended to include it... I'll check when I get back home but this date looks familiar. As for reducing the backup: I'm trying to create a backup of the initial image that came with the device so I'd like to avoid throwing stuff away. So the recommendation would be to update the U-Boot with: 1) backup exsitng U-Boot (http://wiki.openmoko.org/wiki/Backup): Boot NOR boto menu sudo ./dfu-util -a u-boot -R -U good-u-boot.bin sudo ./dfu-util -a u-boot_env -R -U good-u-boot_env.bin 2) flash U-Boot (http://wiki.openmoko.org/wiki/Flashing_the_Neo_FreeRunner#Flashing_the_boot_loader_to_the_NAND): dfu-util -a u-boot -R -D uboot.bin Reboot the device to use the new U-Boot but the following reminder is not very clear to me: Reminder: You should have boot from NOR first, in order to flash the boot-loader in NAND. After flashing succesfully, make sure you reboot from NAND's newly flashed boot loader, to benefit from the updates. Does this mean I simply have to reboot the FreeRunner to the NOR boot menu again, or do I have to boot to the NAND boot menu as well/instead? And from which boot menu should I continue backing up the device? From the NOR menu? Which u-boot.bin should I use? And where should I get it? Thanks in advance. Bram NOR boot menu shows: U-Boot 1.3.2-moko12 (May 9 2008 - 10:28:48) NAND boot menu shows: U-Boot 1.3.2-moko12 (Oct 7 2008 - 21:03:06) so I guess I need to update According to http://wiki.openmoko.org/wiki/U-boot the latest bootloader binary builds can be found under http://downloads.openmoko.org/distro/unstable/daily/ . Are these considered stable despite being in the unstable branch? Which version is recommended at this stage? The latest daily build (http://downloads.openmoko.org/distro/unstable/daily/om-gta02/20090420/) does not contain a uboot image. The one from 20090419 does. Regards Bram Mertens I tried using the u-boot-gta02v5-1.3.1+gitrb20cc520a22715fe7ff069b36b7dfdbb925a8e5a-r1.bin from http://downloads.openmoko.org/distro/unstable/daily/om-gta02/20090419/: $ sudo dfu-util -a u-boot -R -D uboot.bin dfu-util - (C) 2007-2008 by OpenMoko Inc. This program is Free Software and has ABSOLUTELY NO WARRANTY Opening USB Device 0x:0x... Found Runtime: [0x1d50:0x5119] devnum=14, cfg=0, intf=0, alt=1, name=u-boot Claiming USB DFU Interface... Setting Alternate Setting ... Determining device status: state = dfuERROR, status = 14 dfuERROR, clearing status Determining device status: state = dfuIDLE, status = 0 dfuIDLE, continuing Transfer Size = 0x1000 bytes_per_hash=4338 Starting download: [##] finished! state(2) = dfuIDLE, status(0) = No error condition is present Done! Resetting USB to switch back to runtime mode While device was connected, I selected reboot option from the U-Boot menu. Device powers down briefly, then displays the openmoko logo. It sat there doing nothing for a while so I unplugged the device. However the openmoko logo remains on screen... Is it supposed to take several minutes, it's been more than 15minutes already... Should I reset the device? Boot immediately to the NOR or NAND menu? Thanks in advance. Bram ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: backing up rootfs fails - after 40m FreeRunner continues booting
On Mon, Apr 20, 2009 at 2:03 PM, Bram Mertens mertensb.ma...@gmail.com wrote: snip Have you tried using NeoTool [1]? It's always worked quite well for me, and the backing up process avoids dfu-util. [1] http://wiki.openmoko.org/wiki/NeoTool ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: backing up rootfs fails - after 40m FreeRunner continues booting
On Mon, Apr 20, 2009 at 8:12 PM, Cameron Frazier frazier.came...@gmail.com wrote: On Mon, Apr 20, 2009 at 2:03 PM, Bram Mertens mertensb.ma...@gmail.com wrote: snip Have you tried using NeoTool [1]? It's always worked quite well for me, and the backing up process avoids dfu-util. [1] http://wiki.openmoko.org/wiki/NeoTool I have tried to use it before when I initially went to pick up the device but never succeeded, probably because we were using the wrong files. And the instructions seemed clear enough to use the command line utility. The current problems/questions would have arisen with NeoTool anyway, looks like I made a mistake when rebooting the device. So when you have flashed the U-Boot with NeoTool, how do you proceed? Unplug it first, power down, then boot again or use the boot menu to reboot? And did you boot the device normally or immediately into NOR or NAND? The display still shows the openmoko logo, guess I'll have to hard reset it though I hope that won't break anything... Regards Bram ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: backing up rootfs fails - after 40m FreeRunner continues booting
On Mon, Apr 20, 2009 at 2:51 PM, Bram Mertens mertensb.ma...@gmail.com wrote: On Mon, Apr 20, 2009 at 8:12 PM, Cameron Frazier frazier.came...@gmail.com wrote: On Mon, Apr 20, 2009 at 2:03 PM, Bram Mertens mertensb.ma...@gmail.com wrote: snip Have you tried using NeoTool [1]? It's always worked quite well for me, and the backing up process avoids dfu-util. [1] http://wiki.openmoko.org/wiki/NeoTool I have tried to use it before when I initially went to pick up the device but never succeeded, probably because we were using the wrong files. And the instructions seemed clear enough to use the command line utility. The current problems/questions would have arisen with NeoTool anyway, looks like I made a mistake when rebooting the device. So when you have flashed the U-Boot with NeoTool, how do you proceed? Unplug it first, power down, then boot again or use the boot menu to reboot? And did you boot the device normally or immediately into NOR or NAND? The display still shows the openmoko logo, guess I'll have to hard reset it though I hope that won't break anything... I've always just: - flashed - powered down, which the FR seems to do on it's own once u-boot times out - unplug the usb, as I've found that leaving it in will cause hangs similar to what your seeing (oddly I don't have this issue with the AC adapter) - turn on pre normal procedure (power button for 8-10 sec) I use NeoTool most times since I like the backup method (having had numerous problems with dfu-util backups) and it helps to ensure I'm not throwing improper commands when I flash. I have little faith in the user on my end. Hope that helps. Cameron ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: backing up rootfs fails - after 40m FreeRunner continues booting
On Mon, Apr 20, 2009 at 9:39 PM, Cameron Frazier frazier.came...@gmail.com wrote: On Mon, Apr 20, 2009 at 2:51 PM, Bram Mertens mertensb.ma...@gmail.com wrote: On Mon, Apr 20, 2009 at 8:12 PM, Cameron Frazier frazier.came...@gmail.com wrote: On Mon, Apr 20, 2009 at 2:03 PM, Bram Mertens mertensb.ma...@gmail.com wrote: snip Have you tried using NeoTool [1]? It's always worked quite well for me, and the backing up process avoids dfu-util. [1] http://wiki.openmoko.org/wiki/NeoTool I have tried to use it before when I initially went to pick up the device but never succeeded, probably because we were using the wrong files. And the instructions seemed clear enough to use the command line utility. The current problems/questions would have arisen with NeoTool anyway, looks like I made a mistake when rebooting the device. So when you have flashed the U-Boot with NeoTool, how do you proceed? Unplug it first, power down, then boot again or use the boot menu to reboot? And did you boot the device normally or immediately into NOR or NAND? The display still shows the openmoko logo, guess I'll have to hard reset it though I hope that won't break anything... I've always just: - flashed - powered down, which the FR seems to do on it's own once u-boot times out - unplug the usb, as I've found that leaving it in will cause hangs similar to what your seeing (oddly I don't have this issue with the AC adapter) - turn on pre normal procedure (power button for 8-10 sec) I use NeoTool most times since I like the backup method (having had numerous problems with dfu-util backups) and it helps to ensure I'm not throwing improper commands when I flash. I have little faith in the user on my end. Thanks, I pulled the battery and booted into NOR, it still shows: U-Boot 1.3.2-moko12 (May 09 2008 - 10:28:48) select reboot from menu - FDOM boots. Shut down device to NAND boot menu. NAND boot menu shows: pr 19 2009 - 19:10:05)520a22715fe7ff069b36b7dfdbb925a8e5a (A So it looks like NAND U-Boot was updated but NOR hasn't. However http://wiki.openmoko.org/wiki/Backup#Backing-up_flash_images specifically states that you need to be in NOR U-Boot before flashing/backing up. After reading http://wiki.openmoko.org/wiki/Flashing_NOR I get the impression that flashing NOR is not really recommended compared to flashing NAND. I'll try with NeoTool since even with the new U-Boot a backup fails after 38minutes (while booted to NAND). Regards Bram ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: backing up rootfs fails - after 40m FreeRunner continues booting
I pulled the battery and booted into NOR, it still shows: U-Boot 1.3.2-moko12 (May 09 2008 - 10:28:48) select reboot from menu - FDOM boots. Shut down device to NAND boot menu. NAND boot menu shows: pr 19 2009 - 19:10:05)520a22715fe7ff069b36b7dfdbb925a8e5a (A So it looks like NAND U-Boot was updated but NOR hasn't. However http://wiki.openmoko.org/wiki/Backup#Backing-up_flash_images specifically states that you need to be in NOR U-Boot before flashing/backing up. After reading http://wiki.openmoko.org/wiki/Flashing_NOR I get the impression that flashing NOR is not really recommended compared to flashing NAND. The NOR is not flashable on the Freerunner (sans debug board, or special versions). It's your failsafe should you break your NAND bootloader in some spectacular fashion. This is why you go into NOR for flashing, since it is invariable over all the changes you can do to the system. I still recommend using NeoTool for at least backing up, as it uses an ssh connection and mkfs-jffs2 to create an image of the rootfs, rather then fiddling with dfu-util. Hope that helps in some fashion. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: backing up rootfs fails - after 40m FreeRunner continues booting
2009/4/20 Bram Mertens mertensb.ma...@gmail.com: Is there a way to prevent this or to speed up the backup? Or have it continue where it left off? The backup is already 247M... the obvious (to me, anyway), would be: how much of the stuff on there do you need? i'm sure you can delete/copy over ssh some of the bigger files, or uninstall some software. personally i have lots of software installed that i got to test, and then never used again. or are there any temp/cache/log files you can clean out? that might be enough to bring it under 40 minutes it should really allow you to back up the lot, but then there are lots of things the software doesn't do yet ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: backing up rootfs fails - after 40m FreeRunner continues booting
On Mon, Apr 20, 2009 at 12:07:55AM +0200, Bram Mertens wrote: Hi, I'm about ready to flash a new distro onto the FreRuuner main memory but since it'll be the first time I wanted to try backing up the existing distro first. So I followed the steps on http://wiki.openmoko.org/wiki/Backup . Which version of U-Boot are you using? DFU Upload was broken at least until 2008-10-17. 2008-10-07 Harald Welteu-boot: Fix DFU upload in u-boot http://git.openmoko.org/?p=u-boot.git;a=commitdiff;h=414367bf5b65942947dd5d569c27d2a8e8e5e562 -- Rask Ingemann Lambertsen Danish law requires addresses in e-mail to be logged and stored for a year ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
