Re: Help requested: SHR Screenshots
Petr Vanek wrote: On Sun, 07 Jun 2009 10:38:41 +0100 Jon Levell openm...@coralbark.net (JL) wrote: Hi, I'm writing an article for LWN (http://www.lwn.net) saying that I think SHR is now suitable for your typical LWN.net reader). LWN would like some screenshots of a recent SHR (testing or unstable) that they could publish with the article. Unfortunately my FR is still in transit (buzz fixed by Dr. N et al) so could someone send some recent screenshots to: openm...@coralbark.net I'd especially like the dialler and the main illume launcher screen but I'd appreciate any that you thought were interesting and suitable for publication. Thanks in advance for any help. Jon. Hi, i am uploading it on http://scap.linuxtogo.org/ as we speak, please select what you like :) Nice selection, would it be possible to include a short description of what's visible in the images? Like: distro X, showing app Y and Z. TIA Bram ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[SHR-testing] Black Screen of Death?
Hi, Yesterday I encountered again what I'd call a Black Screen Of Death. For a - low quality - picture see http://users.telenet.be/bmertens/FreeRunner/FreeRunnerBSOD.jpg ). I've encountered this before but I'm never able to tell what exactly happened. Usually I leave the device for some time to find it like this when I return. Yesterday the device was on the seat next to me in the car doing nothing special (no GPS, no audio or anything). I had only booted it several minutes before after switching the SIM card to a card I use for testing and made one phone call. I'm using SHR-testing from 20090422 on an SD card: uImage-2.6.29-oe10+gitr81c61a7d1abb03aecd13f5395aba355e996a1641-r3.4-om-gta02.bin openmoko-shr-image-glibc-ipk--20090422-om-gta02.rootfs.tar.gz with U-Boot (u-boot-gta02v5-1.3.1+gitrb20cc520a22715fe7ff069b36b7dfdbb925a8e5a-r1.bin) When I get this black screen with a single white line the only way I've found to recover is to pull the battery, the device won't respond to screen touches or even holding the power button. I have never tried to ssh into the device. It usually feels warm but I can't tell if it is a result of this or a cause. What is normal operating temperature for the FreeRunner? Has anybody encountered this? I haven't been able to find references to anything similar, unless this too is a variation of the WSOD. Don't know if it is relevant but over the past couple of days the at daemon has regularly crashed causing ffalarms to fail. Other daemons have failed as well but less frequently. Thanks in advance Bram ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: little today app for shr
On Sat, May 2, 2009 at 1:04 AM, Pietro m0nt0 Montorfano mont...@gmail.com wrote: Hi, bored loosing some calls and always need to periodically check pyphenlog i wrote a really simple apps that warn me if one or more call are lost. Here is the link to opkg, any suggestion is welcome. http://www.opkg.org/package_213.html Clicking on 1 missed call it opens pyhoneloh and clicking on 1 unread message it opens opemoko-messages3, editing the script is simple so you can modify that apps. The app is insvisible, just sit there and wait for missed calls or incoming messages. The way it's autostarted is tricky, sleep 180 and then run it, just to be shure that illume and frameworkd are running. Bye! Pietro Another compliment, this really comes in handy! I do get the following warning (I started it using the init script from an ssh session after installing): r...@om-gta02 ~ $ /usr/lib/python2.6/site-packages/dbus/connection.py:242: DeprecationWarning: object.__init__() takes no parameters super(Connection, self).__init__(*args, **kwargs) r...@om-gta02 ~ $ Let's go on Kind regards Bram ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[SHR-testing] create contact from pyphonelog entries
Hi So far I've been unable to figure out how to access the list of contacts on my SIM so it looks like I'll need to enter them again or import them somehow. I already have a number of recieved/mised calls that I can access from pyphonelog. Is it possible to convert/export these somehow so I can create contacts out of this list? All phones I have owned/used/seen have a feature like this where you can use a number to create a contact, send an SMS message, etc. Going further being to do the same from number in SMS messages would be great too. Thanks in advance. Bram ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-testing] create contact from pyphonelog entries
Great, haven't seen that seen I've only subscribed to (only heard about it's exisitng) this week. Any idea when this would make it to testing? I seem to recall reading somewhere that SHR-testing is currently more recent than SHR-unstable. Is thta no longer true or is there another reason why this newer version of opimd is not in SHR-testing? Regards Bram On Tue, May 5, 2009 at 12:36 AM, Al Johnson openm...@mazikeen.demon.co.uk wrote: It can be done with elmphonelog, but requires new functionality from opimd that isn't in shr-testing. It works in shr-unstable though. This was announced on the shr-user list about a week ago. On Monday 04 May 2009, jeremy jozwik wrote: yes i would also like to know this one. the SHR phone log desperately needs this -- Forwarded message -- From: Bram Mertens mertensb.ma...@gmail.com Date: Mon, May 4, 2009 at 2:49 PM Subject: [SHR-testing] create contact from pyphonelog entries To: community@lists.openmoko.org Hi So far I've been unable to figure out how to access the list of contacts on my SIM so it looks like I'll need to enter them again or import them somehow. I already have a number of recieved/mised calls that I can access from pyphonelog. Is it possible to convert/export these somehow so I can create contacts out of this list? All phones I have owned/used/seen have a feature like this where you can use a number to create a contact, send an SMS message, etc. Going further being to do the same from number in SMS messages would be great too. Thanks in advance. Bram ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[SHR-testing] unable to return after suspend
Hi Last night I suspended my FreeRunner from SHR-testing, hoping that the alarm clock would work like it does on my Nokia. The alarm didn't work and when I tried to start it today the screen remained black. Sometimes when I press the power button I get the messages on screen as if it's waking up from suspend but then the screen goes black again. I tried shutting the device down, removing the battery for a while etc. But after the devices boots the screen goes black again. I do get the screen asking me to enter my PIN (the screen looks off a bit though and the text on the buttons is hardly readable) but after that the screen goes black again. When I boot FDOM from the device's main memory everything works but when I boot SHR-testing again I get the same symptoms. Any idea what might be wrong and how to fix it? Just now some more messages scrolled by on the screen, several minutes after my last key or screen presses. When I pressed the power button again again messages scrolled by, one of the last messages (not the last, the screen blacks out to soon to read that) was: restarting tasks: done Regards Bram ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-testing] save SMS messages to text file?
Cool, As soon as I can start SHR again (see my other post) I'll give this a try! @Arne: the second step of saving the messages is that the redirection of the output in David's script? Or did you mean a separate command? @Johnny: looking forward to those improvements! Regards Bram On Mon, Apr 27, 2009 at 2:31 AM, David Ford da...@blue-labs.org wrote: this is what i use to dump the messages from my sim card to a text file. then i delete the messages on the sim card so i have room for new messages. a limit of 30 messages is entirely impractical. that gets filled up before noon arrives unless i constantly delete messages. r...@nibbly-bits:~# cat backup_messages.sh #!/bin/sh d=$(date +%Y.%m.%d-%H%M) mdbus -s org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device org.freesmartphone.GSM.SIM.RetrieveMessagebook 'all' messages-$d.txt On 04/26/09 19:06, Daniel.Li wrote: I don't know about current status. But it seems impossible, if u are using openmoko-message, see below http://lists.openmoko.org/nabble.html#nabble-td2619250 On Sun, 2009-04-26 at 20:13 +0200, Bram Mertens wrote: Hi I've succesfully flashed my GSM firmware with the provided uSD image so now I'm able to use my FreeRunner as a phone. My old phone has several SMS messages stored in it's internal memory and allowed receiving messages to this memory even though the space on the SIM for storing SMS messages is full. Now off course only those messages on the SIM card are available on the FreeRunner and the messages application immediately complained that there is no space for new messages. Doesn't the FreeRunner allow storing SMS messages other than on the SIM? And in any case: is there a way to extract or backup SMS messages to a clear text file? I couldn't find anyhting on the wiki about this. Regards Bram ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
On Mon, Apr 27, 2009 at 10:43 AM, Robin Paulson robin.paul...@gmail.com wrote: 2009/4/27 Jose Luis Perez Diez perezd...@gmail.com: El Saturday, 25 de April de 2009 01:30:45 Robin Paulson va escriure: rebooted the phone and the laptop, and still nothing dmesg gives this, which looks like it can see the phone, but not figure out what it is [ 1448.937469] hub 1-0:1.0: unable to enumerate USB device on port 1 [ 1451.316831] usb 1-1: new full speed USB device using uhci_hcd and address 18 [ 1466.428058] usb 1-1: device descriptor read/64, error -110 . any ideas? I will try another usb cable or port no, there was nothing wrong with the port or cable - someone at shr hadn't run depmod before creating the tarball, and the modules for communicating over usb weren't being loaded. if you run depmod on your phone, it should clear it up It didn't when I tried this. I ended up flashing a newer version of SHR-testing (2009/04/22 if I remember corretly) and that one did work out of the box. That is untill I hit the suspend problem this morning... Regards Bram ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[SHR-testing] save SMS messages to text file?
Hi I've succesfully flashed my GSM firmware with the provided uSD image so now I'm able to use my FreeRunner as a phone. My old phone has several SMS messages stored in it's internal memory and allowed receiving messages to this memory even though the space on the SIM for storing SMS messages is full. Now off course only those messages on the SIM card are available on the FreeRunner and the messages application immediately complained that there is no space for new messages. Doesn't the FreeRunner allow storing SMS messages other than on the SIM? And in any case: is there a way to extract or backup SMS messages to a clear text file? I couldn't find anyhting on the wiki about this. Regards Bram ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
On Fri, Apr 24, 2009 at 4:08 PM, Thomas Otterbein th.otterb...@gmx.net wrote: On Friday 24 April 2009 15:16:38 Nelson Castillo wrote: On Fri, Apr 24, 2009 at 5:42 AM, Thomas Zimmermann zimmerm...@vdm-design.de wrote: Am Freitag 24 April 2009 12:20:00 schrieb Robin Paulson: 2009/4/24 Ben Thompson b...@york.ac.uk: ok, i'm confused now. why do i want to run this on my host? the problem's with the phone, isn't it? I don't know why, but the interface name on my host changed. For me it's now eth1. Check: http://lists.openmoko.org/pipermail/devel/2009-April/005384.html ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community On my Ubuntu 8.10 the shr-unstable behaves exactly as described in the link. The X depends on your number of network cards. I use a notebook which has a cable and a Wifi ethernet adapter named eth0 and eth1. However the Neo becomes eth3 as it connects. I collected the information from the Wiki about USB Networking in a script, which i use until I managed to integrate the Neo better into Ubuntu and it's various network configuration mechanisms. The script has a variable for the interface as the first line. Adapt it to your needs and run it after you have connected your Neo to the USB port. I use ifconfig to check out the known network cards and their configuration. On my Fedora 10 laptop nothing appears to happen anymore when I plug in the Neo. No messages in /var/log/messages, nothing in dmesg. [m8...@fedora10 ~]$ sudo /sbin/ip link show 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:1c:23:01:c4:a0 brd ff:ff:ff:ff:ff:ff 3: wmaster0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ieee802.11 00:1b:77:60:df:64 brd ff:ff:ff:ff:ff:ff 4: wlan0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:1b:77:60:df:64 brd ff:ff:ff:ff:ff:ff 5: pan0: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN link/ether 52:6d:38:6a:32:49 brd ff:ff:ff:ff:ff:ff I am booting from U-Boot (in NAND) though, the post referenced above mentions SHR-testing (the distro on the SD I'm booting from) behaving differently when booted from QI. I get the same result on my Xubuntu laptop so I fear that something else got broken with the opkg update, opkg upgrade I performed. So far I haven't found a description of what is needed on the side of the FreeRunner itself. When I check ifconfig -a on the FreeRunner I see an eth0 interface with no IP address, eth0:avah alias with IP 169.254.7.134 and the loopback device. ip link show shows the loopback device and the eth0 interface. When I check the /etc/network/interfaces it contains a comment right before the auto usb0 section saying: # Ethernet/RNDIS gadget (g_ether) # ... or on host side, usbnet and random hwaddr ifup usb0 retruns: ifup: interface usb0 already configured but ifconfig usb0 returns: ifconfig usb0: error fetching interface information: Device not found modprobe g_ether on the FreeRunner fails to locate the module so maybe some modules are missing? Or is this module no longer needed? loading the usbnet module on either the Fedora or the Xubuntu laptop does not help. One final note: the hardware is fine, when I start FDOM from the device's main memory it is still recognized. 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 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
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 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 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
backing up rootfs fails - after 40m FreeRunner continues booting
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 . However I'm unable to back up the rootfs as it takes more than 40 minutes and after 40minutes the FreeRunner continues to boot and I get: $ time sudo dfu-util -a rootfs -R -U 20090419-rootfs.jffs2 [sudo] password for m8ram: dfu-util - (C) 2007-2008 by OpenMoko Inc. This program is Free Software and has ABSOLUTELY NO WARRANTY Opening USB Device 0x:0x... 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=11, cfg=0, intf=0, alt=6, name=rootfs Claiming USB DFU Interface... Setting Alternate Setting ... Determining device status: state = dfuIDLE, status = 0 dfuIDLE, continuing Transfer Size = 0x1000 bytes_per_hash=4096 Starting upload: [### dfu_upload error -84 real40m5.588s user0m0.088s sys 0m1.357s 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... Thanks in advance Bram ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: $299 ESC San Jose limited time Special! ?
Joseph I too got a FR from kd85 and I'm impressed with the service. Regards Bram On Wed, Apr 1, 2009 at 4:58 PM, Joseph Reeves iknowjos...@gmail.com wrote: That would make sense... After a bit of googling for belgium openmoko (a perfectly normal search term, honest...) I found this reseller that I'd never seen before: https://kd85.com/openmoko.html Seems to have taken delivery of 180/200: http://openmoko.kd85.com/images/ and is selling them on at a very good price, has been doing so since November last year. Openmoko stock clearance? Cheers, Joseph 2009/4/1 Cédric Berger cedric.berge...@gmail.com: On Wed, Apr 1, 2009 at 16:00, Joseph Reeves iknowjos...@gmail.com wrote: Dear all, I've not seen any mention of this on the lists, but it all looks very cheap! http://us.direct.openmoko.com/products/neo-freerunner # GSM 850 ( Promotion, Extras: pouch and headset x 1) $299.00 USD # GSM 900-10 Pack $2,690.00 USD # GSM 850-10 Pack $2,690.00 USD Not an April Fools thing is it? This must be in-stock phones, and as next ones (GTA2 A7) should have some buzz fix already done at factory, these old ones will loose value I would say... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Fwd: Fwd: unable to get the boot menu
Apologies, again reply to sender instead of reply-to-list... -- Forwarded message -- From: Bram Mertens mertensb.ma...@gmail.com Date: Tue, Mar 3, 2009 at 10:20 AM Subject: Re: Fwd: unable to get the boot menu To: Joel Newkirk freerun...@newkirk.us On Tue, Mar 3, 2009 at 5:01 AM, Joel Newkirk freerun...@newkirk.us wrote: On Tue, 3 Mar 2009 00:31:54 +0100 Bram Mertens mertensb.ma...@gmail.com wrote: I've tried several times again. After removing the battery for several minutes the device automatically boots when the battery is replaced. By the time I've turned the device around after replacing the back cover the openmoko logo is already displayed. (The device was not connected to any computer.) So I've shut the device down again by pressing the power button for several seconds. Without removing the battery but waiting some 30 seconds: 1) press and hold AUX 2) press and hold power after about 4 seconds the AUX button lights up, about 2 seconds later the openmoko logo is displayed and after that the device boots I released both buttons as soon as the openmoko logo was displayed. Again power down the device 1) press and hold power 2) press (and hold) AUX approx 2 seconds after pressing power before the openmoko logo is displayed again the device boots without displaying any kind of boot menu Is it possible to reconfigure the wait time of the boot menu via the device? I can't find anything in the settings menu or any terminal application that would allow me to execute commands. Regards Bram Maybe someone else will have a brighter idea, but all I can suggest at this point is unplug, remove battery, then hold down AUX while inserting battery. If that doesn't work, but it just boots right up instead, then try to confirm that the AUX button is functional, as I'm starting to suspect a bum button. If that's the case I've no idea what solution is feasible. j Any idea how to test the AUX button? During one of my tests keeping the AUX button pressed longer than usual the screen was displayed rotated 90 degrees. So at least it had some effect. Unfortunately I haven't been able to find much documentation of the applications installed so I can't tell if any of them should react to the AUX button being pressed. I'll try keeping the AUX button pressed while inserting the battery later. Regards Bram ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
