Re: need a new u-boot_env
Arne Zachlod [EMAIL PROTECTED] writes: Hello there! i had destroyed my u-boot_env and can't get a new one because of this bug in envedit.pl: :~/Desktop/devirginator$ ./envedit.pl -D GTA02 -s 262144 -i env.in -f environment.in -o env.out CRC error: expected 0x27a5eefd, got 0x20230a23 so, is there anyone who could send me a proper u-boot-env? first bootdevice should be flash and the rest is unimportant, but you can put there as much as you like. my device is a GTA02v05 thanks a lot, greetings, zachso Shouldn't such information be in the wiki for reference ? I have tweaked mine unfortunately, so I'm not sure it's worth reusing. My 2 cents, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
microSD partition table and proper heads/sectors/cylinders # ?
Hi. I noticed that initially, my 2GB microSD card was displaying : # fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 2032 MB, 2032664576 bytes 64 heads, 63 sectors/track, 984 cylinders Units = cylinders of 4032 * 512 = 2064384 bytes Device Boot Start End Blocks Id System /dev/mmcblk0p1 1 984 1983619+ 6 FAT16 After Debian installer's partitioning step, it becomes : # fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 2032 MB, 2032664576 bytes 4 heads, 16 sectors/track, 62032 cylinders Units = cylinders of 64 * 512 = 32768 bytes Device Boot Start End Blocks Id System /dev/mmcblk0p1 1 2457832 83 Linux /dev/mmcblk0p2 246 62032 1977184 83 Linux Is there any rationale for the heads/sectors/cylinders difference ? I'm not sure this is something that matters as I never really tried and figure how the microSD memory to disk mapping is done. Thanks in advance for any hints. Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: SD Card Issues On GTA02
Marzak [EMAIL PROTECTED] writes: Hello, I read the information about slowing down the clock speed to allow for slower cards. This is the original SD card, but I gave it a try anyway. I created another boot menu entry with the added argument to max the speed at 1000. I tried the debian installer again and had the same error. You're talking of http://docs.openmoko.org/trac/ticket/1743 ? The glamo_mci.sd_max_clk workaround seems to not apply in my case, although I'm not completely sure. I checked over the list of supported SD cards and tried a 2GB scandisk thinking that maybe my SD card had an issue. Same results. Is there anything that I missed or did not consider? Anything else I can try? Could I have a bad SD controller? Same here I think although my card wasn't listed initially in http://wiki.openmoko.org/wiki/Supported_microSD_cards I suspect there's something nasty around, as this is the 3rd thread about the same subject in 3 days (both on community and support lists). I guess all should try and review the ticket above and add reference info in the wiki, to try and identify the problem more precisely. Hope this helps. -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
2008.8 updated today and illume as default profile brings classical enlightenment
Hi. I updated to today's stable packages (after noticing quite a lot of merges from testing), and lost the illume/raster keyboard. I tried to apply the hacks described at http://wiki.openmoko.org/wiki/Keyboard_Debate#How_to_install_the_illume_.28Raster.27s.29_keyboard_.3F (more or less), and noticed that now, only the 'asu' default profile seems to bring the 2008.8 theme, and setting it as 'illum' (echo 'E_PROFILE=-profile illume' /etc/enlightenment/default_profile) will switch to classical enlightenment desktop like theme, menus, etc. I think the http://wiki.openmoko.org/wiki/Keyboard_Debate should be updated, but I'm not so sure something ain't broken in the current stable updates :-/ I'm back with the ASU keyboard (and no config wrench) for the time being. Thanks for any comments. Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: 2008.8 updated today and illume as default profile brings classical enlightenment
Thomas B. [EMAIL PROTECTED] writes: On Thu, Sep 04, 2008 at 08:53:46AM +0200, Olivier Berger wrote: Hi. I updated to today's stable packages (after noticing quite a lot of merges from testing), and lost the illume/raster keyboard. I tried to apply the hacks described at http://wiki.openmoko.org/wiki/Keyboard_Debate#How_to_install_the_illume_.28Raster.27s.29_keyboard_.3F (more or less), and noticed that now, only the 'asu' default profile seems to bring the 2008.8 theme, and setting it as 'illum' (echo 'E_PROFILE=-profile illume' /etc/enlightenment/default_profile) will switch to classical enlightenment desktop like theme, menus, etc. I also had this issue when I upgraded today. I think the http://wiki.openmoko.org/wiki/Keyboard_Debate should be updated, but I'm not so sure something ain't broken in the current stable updates :-/ Yes, I think there is actually something broken. When I did opkg files illume-config-illume after the upgrade, it showed that this package was actually empty, just like several of the other illume packages (illume-keyboard-*). Indeed : illume-config-illume Package illume-config-illume (0.0+svnr35727-r13) is installed on root and has the following files: [NOTHING] illume-keyboards-default Package illume-keyboards-default (0.0+svnr35727-r13) is installed on root and has the following files: [NOTHING] illume-keyboards-numbers Package illume-keyboards-numbers (0.0+svnr35727-r13) is installed on root and has the following files: [NOTHING] illume-keyboards-terminal Package illume-keyboards-terminal (0.0+svnr35727-r13) is installed on root and has the following files: [NOTHING] Doing an opkg install with the URL of the packages in the testing feed didn't seem to work either, I had to download the ipk's from the testing feed, put their md5sums into the packages list in /var/lib/opkg/daily-all and opkg install *.ipk. That did it for me. I did manual install of : # opkg install http://downloads.openmoko.org/repository/Om2008.8/all/illume-config-illume_0.0+svnr35727-r13_all.opk # opkg install http://downloads.openmoko.org/repository/Om2008.8/all/illume-keyboards-default_0.0+svnr35727-r13_all.opk # opkg install http://downloads.openmoko.org/repository/Om2008.8/all/illume-keyboards-numbers_0.0+svnr35727-r13_all.opk # opkg install http://downloads.openmoko.org/repository/Om2008.8/all/illume-keyboards-terminal_0.0+svnr35727-r13_all.opk And that reinstalled them properly... Hope this helps, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
USB networking deconnected... interference with avahi-daemon on host ?
Hi. I experienced issues with intermitent USB networking deconnections (I mean, the IP level, since underlying USB was still there). That was on initial ASU/2008.8. I think it used to be worse when avahi-daemon was running on my host. Now I have shut it down, it's better, although not perfect. Would anyone have similar experience, or hints ? Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Reference screenshots of various keyboards ? - Was: Re: Illume keyboard Disappeared
Armin ranjbar [EMAIL PROTECTED] writes: after running a few while , maybe after suspends , Illume keyboard does not appear and standard om2008 keyboard appear , any one has any idea ? There are lots of flames/discussions over the keyboard (including in bugtracker), and it's sometimes very difficult to follow the reasoning... and adding more noise to noisy discussions is not what's preferable.. still it's really hard to keep up on these issues, I think. What is om2008 keyboard (which om 2088 : 08/08 or 08/26 ?).. what's Illume keyboard, etc. Maybe if we had a set of pictures to name them and avoid confusion (pictures like what's in http://wiki.openmoko.org/wiki/Om2008.8_Keyboard) would help alot to get a clearer idea of the various options. Is this possible (taking snapshots of the keybords displayed) ? Thanks in advance for your comments. Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Latest Image works great
phillip tribble [EMAIL PROTECTED] writes: Hello everyone, I highly recommend the 2008-08-11 image because it has been a lot more stable for me. It is way better than 2008-08-08. The addres is: http://buildhost.openmoko.org/daily/freerunner/200808/20080811/ Is this supposed to be an official update for 2008.8, or something built from another unsupported branch not for end-users ? Are there any update fees for 2008.8 in sync with these images ? Thanks in advance. -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Pulling flash image off device
Craig Woodward [EMAIL PROTECTED] writes: This may seem trivial, but I can't seem to find anything on how to do this directly. Is there an easy way to pull my existing fs flash image OFF my phone so I can save the current config? I want to have a backup so if I add a package or do an upgrade later that toasts my phone I don't have to start from square one again. ;) I could probably remount the root as ro, and DD it out via ssh or to the mmc. But is there anything I have to do otherwise to make it valid in dft-uilts eyes? You may have a look at http://wiki.openmoko.org/wiki/Moving_current_system_from_flash_to_SD which explains a way to backup from which you could, in principle, dual boot in any case. Hope this helps. Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: USB Networking troubles
michael cole [EMAIL PROTECTED] writes: Perhaps someone with editing rights to the networking page can add a couple of lines to make clear the need for distinct networks in specifying the setup. Why not change that yourself... it's a wiki. You too can get these edit rights (unless registration gets broken) ;-) Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Todays 2008.08 Bug list
Craig Woodward [EMAIL PROTECTED] writes: Ok, so here are just a few things I've found working with the current image today: Ever heard of a bug tracker ? https://docs.openmoko.org/trac/report then, maybe https://docs.openmoko.org/trac/login and then only : https://docs.openmoko.org/trac/newticket Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: distro-feed-configs_1.0-r0_om-gta02.ipk
arne anka [EMAIL PROTECTED] writes: why does distro-feed-configs_1.0-r0_om-gta02.ipk attempt to overwrite all feeds' url with http://my-distribution.org/remote-feed/ ? this will ultimately kill any further update until replaced with meaningful url! Hi. This time the problem seems that there's a new set of files in distro-feed-configs_1.0-r0.01_om-gta02.ipk which try and change the feeds config : Downloading http://buildhost.openmoko.org/daily-feed/om-gta02/distro-feed-configs_1.0-r0.01_om-gta02.ipk Multiple packages (distro-feed-configs and distro-feed-configs) providing same name marked HOLD or PREFER. Using latest. Multiple packages (distro-feed-configs and distro-feed-configs) providing same name marked HOLD or PREFER. Using latest. Installing distro-feed-configs (1.0-r0.01) to root... Configuration file '/etc/opkg/all-feed.conf' == File on system created by you or by a script. == File also in package provided by package maintainer. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions (if diff is installed) The default action is to keep your current version. *** all-feed.conf (Y/I/N/O/D) [default=N] ?d --- /etc/opkg/all-feed.conf-opkg.backup Sat Aug 2 01:05:27 2008 +++ /etc/opkg/all-feed.conf Thu Aug 7 02:11:33 2008 @@ -1 +1 @@ -src/gz daily-all http://buildhost.openmoko.org/daily-feed/all +src/gz om-dev-all http://buildhost.openmoko.org/daily-feed/all The only result I can see, if installing the new ones is that now there's two sets of feeds saved in /var/lib/opkg/ : the old ones : daily-alldaily-armv4t daily-neo1973daily-om-gta02 and the new ones : om-dev-all om-dev-armv4tom-dev-om-gta02 Is this related to 2008.08 image release ? Any comments ? Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Led light stay on after boot
Feydreva [EMAIL PROTECTED] writes: yeah, it turns off at one point... but it s not consistent... Well, it may be consistent to the fact that the phone eventually drops charging at one time even though the charger may be plugged-in (which is another bug) ? I'd bet for conjunction of several bugs ;) and do not seems related to any event... it stays on at least for 15 minutes after the cable is disconnected On Tue, Aug 5, 2008 at 10:15 PM, Dale Maggee [EMAIL PROTECTED]wrote: using yesterday's kernel (5th). For me, it does seem like it's indicating that the battery is charging, but it doesn't turn off if I unplug the USB cable (bug?). If I leave it connected for a while, eventually the red led turns off. -Dale -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: distro-feed-configs_1.0-r0_om-gta02.ipk
Dale Maggee [EMAIL PROTECTED] writes: agh, I was foolish enough to hit 'Y'... can somebody give me the correct contents of the files i've overwritten? Here's a (partial) log of the session here, which exhibits the differences : Installing distro-feed-configs (1.0-r0) to root... Downloading http://buildhost.openmoko.org/daily-feed/om-gta02/distro-feed-configs_1.0-r0_om-gta02.ipk Configuration file '/etc/opkg/all-feed.conf' --- /etc/opkg/all-feed.conf-opkg.backup Thu Jan 1 01:00:00 1970 +++ /etc/opkg/all-feed.conf Tue Aug 5 05:02:09 2008 @@ -1 +1 @@ -src/gz daily-all http://buildhost.openmoko.org/daily-feed/all +src/gz remote-all http://my-distribution.org/remote-feed//all Configuration file '/etc/opkg/armv4t-feed.conf' --- /etc/opkg/armv4t-feed.conf-opkg.backup Thu Jan 1 01:00:00 1970 +++ /etc/opkg/armv4t-feed.conf Tue Aug 5 05:02:09 2008 @@ -1 +1 @@ -src/gz daily-armv4t http://buildhost.openmoko.org/daily-feed/armv4t +src/gz remote-armv4t http://my-distribution.org/remote-feed//armv4t Configuration file '/etc/opkg/neo1973-feed.conf' --- /etc/opkg/neo1973-feed.conf-opkg.backup Thu Jan 1 01:00:00 1970 +++ /etc/opkg/neo1973-feed.conf Tue Aug 5 05:02:09 2008 @@ -1 +1 @@ -src/gz daily-neo1973 http://buildhost.openmoko.org/daily-feed/neo1973 +src/gz remote-neo1973 http://my-distribution.org/remote-feed//neo1973 Configuration file '/etc/opkg/om-gta02-feed.conf' --- /etc/opkg/om-gta02-feed.conf-opkg.backupThu Jan 1 01:00:00 1970 +++ /etc/opkg/om-gta02-feed.confTue Aug 5 05:02:09 2008 @@ -1 +1 @@ -src/gz daily-om-gta02 http://buildhost.openmoko.org/daily-feed/om-gta02 +src/gz remote-om-gta02 http://my-distribution.org/remote-feed//om-gta02 Hope this helps. Now, what's the difference between daily and remote here (considering the hostname is wrong, that's the other change). And what's the point of having something like neo1973 in addition to om-gta02 when I'm running a FR ? Thanks in advance, Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: distro-feed-configs_1.0-r0_om-gta02.ipk
atweb [EMAIL PROTECTED] writes: Hi, Ovverwrite it manually with the new Version: opkg install http://buildhost.openmoko.org/daily-feed/om-gta02/distro-feed-configs_1.0-r0_om-gta02.ipk; This installs direct the file via http without searching in the Paket-Database. I don't get the point here... isn't it the same version as the one in the subject of that thread ? I would expect it not to repair the URLS in the opkg sources, then ? Dale Maggee schrieb: agh, I was foolish enough to hit 'Y'... can somebody give me the correct contents of the files i've overwritten? didn't even notice the 'D' option, to be honest. I'll be using it next time! Thanks. Regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Upgrading u-boot needed ?
Mikael Berthe [EMAIL PROTECTED] writes: * Torfinn Ingolfsen [EMAIL PROTECTED] [2008-08-04 23:55 +0200]: FWIW, I learned (from the community list I believe) som time ago that you can use 'grep Bootloader /dev/mtdblock0' from a shell on the FreeRunner (and possibly the 1973 as well) to get the u-boot version. Like this: [EMAIL PROTECTED]:~# grep Bootloader /dev/mtdblock0 Neo1973 Bootloader U-Boot 1.3.2-moko12 That's NOR u-boot version, and you can get NAND's with mtdblock1: [EMAIL PROTECTED]:~# grep Bootloader /dev/mtdblock1 Neo1973 Bootloader U-Boot 1.3.2+gitr18+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb ...which can be useful to check after an upgrade. HTH too :) Regards, Well... but all that doesn't give any hint on which one the FR was booted under :( (it actually tells you it's under one of these two, which is already a start ;), as in my case, if you pressed aux and power together when booting it, in the wrong order. My 2 cents, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: USB networking in Ubuntu
Joerg Reisenweber [EMAIL PROTECTED] writes: Am So 3. August 2008 schrieb sparky mat: Flushed '-t filter'. Added MASQUERADE-ing as per the wiki. It worked. Finally, my TangoGPS can download maps :P On Sat, Aug 2, 2008 at 11:50 PM, sparky mat [EMAIL PROTECTED] wrote: On Sat, Aug 2, 2008 at 11:45 PM, sparky mat [EMAIL PROTECTED] wrote: I am not sure what I did (though it seems like ifconfig usb0 192.168.0.200 followed by ifconfig usb0 192.168.0.202) but it works now!! I can ssh in :D .. Ok.. now for some MASQUERADE-ing Stopped working. It's something to do with my iptables. Figuring it out. Please note there's an issue with uboot breaking usb for 50% of the boots. so if it doesn't work, a simple reboot of FR might change it. Refer to Andy's postings of last 48h on this issue. Thanks for that information. However, a proper link would have been useful :-( Maybe : http://lists.openmoko.org/pipermail/support/2008-August/000912.html ? Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Upgrading u-boot needed ? - Was: Re: opkg upgrade breaks USB networking: g_ether module missing
Andy Green [EMAIL PROTECTED] writes: | Which uboot is safe? I'm not sure. I suspect older U-Boot had lower probability of making the same problem since we had no idea this was happening until now, and some of the fixes I added would have been needed on older versions too. ~ best bet is to update to tomorrow's U-Boot and we'll try to remove the remaining chance of the problem in the meanwhile. Could someone point to these valid u-boot*.bin files please ? I'd like to upgrade it but it's not clear at all which versions I need. I used to have v. 1.3.2-moko12 of May 9 2008 10:28:48 I downloaded : http://buildhost.openmoko.org/daily/freerunner/200808/20080804/uboot-gta02v5-latest.bin and got a message displayed advertising some april version (which I unfortunately didn't write down)... so I'm puzzled :( How could I check which version I'm using on my FR and if it's up-to-date or not ? Thanks in advance. P.S.: the wiki pages are not clear at all so as to finding appropriate version of u-boot, IMHO, but would gladly improve the situation of course ;) -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Upgrading u-boot needed ? - Was: Re: opkg upgrade breaks USB networking: g_ether module missing
Andy Green [EMAIL PROTECTED] writes: Somebody in the thread at some point said: | Could someone point to these valid u-boot*.bin files please ? | http://buildhost.openmoko.org/daily/freerunner/200808/20080804/uboot-gta02v5-latest.bin Alright, it's the one I had picked. | and got a message displayed advertising some april version (which I | unfortunately didn't write down)... so I'm puzzled :( Are you sure that it is not 4th Aug -- looks like 8th April in some countries? I doubt the latest symlink is broken for so many months. Might be that... No way to start over :( | How could I check which version I'm using on my FR and if it's | up-to-date or not ? At the moment we don't stamp the image with the git head of the sources it came from, we should move to that. I guess so. There's a build date on the menu Well... should it read U-Boot 1.3.2-moko12 (May 9 2008 - 10:28:48) on first line, then ? ... I'd expect something closer from now :-/ and coming out of the serial console as you saw. Same hopefully ;) : GTA02v5 # version U-Boot 1.3.2-moko12 (May 9 2008 - 10:28:48) At the moment this one is up to date for today and has the USB Insane Spam Mode fixes. http://buildhost.openmoko.org/daily/freerunner/200808/20080804/u-boot-gta02v5-1.3.1+gitr18+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb-r0.bin Tried it and get the same versions (means the link are OK on the download site). I thought about trying something : # ./dfu-util -a u-boot -R -U current-uboot.bin # strings current-uboot.bin | grep git U-Boot 1.3.2+gitr18+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb (Aug 4 2008 - 02:33:52) Neo1973 Bootloader U-Boot 1.3.2+gitr18+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb So obviously, the version on u-boot's prompt is not meanlingful, then... :( Should I file a bug report ? Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Upgrading u-boot needed ? - Was: Re: opkg upgrade breaks USB networking: g_ether module missing
Konstantin [EMAIL PROTECTED] writes: Hi there! There's a build date on the menu Well... should it read U-Boot 1.3.2-moko12 (May 9 2008 - 10:28:48) on first line, then ? ... I'd expect something closer from now :-/ Not sure if that applies to you, but I had the same problem, until I realized I was booting to NOR (which you can't update w/o the debug board) instead of NAND all the time. Should that be the case for you, too, try booting with pressing+holding Power first and then pressing and holding AUX while still holding the power button until your freerunner comes to life. Thanks alot. I was indeed booting from NOR (which was indicated in the boot menu, by the way, but I didn't notice). I booted from NAND (following http://wiki.openmoko.org/wiki/Booting#Log_into_U-Boot_in_the_NAND_Flash), and this time, it's OK, displaying (Aug 4 2008 - 02:33:52)0cab8055084ae25ea4e73b66dd03cc1a0cb at top of screen ! :-) And connecting through USB console, I get : GTA02v5 # version U-Boot 1.3.2+gitr18+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb (Aug 4 2008 - 02:33:52) Great, I know now in which order to press buttons on the FR ;-) Thanks alot again. -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Upgrading u-boot needed ? - Was: Re: opkg upgrade breaks USB networking: g_ether module missing
Andy Green [EMAIL PROTECTED] writes: Somebody in the thread at some point said: | So obviously, the version on u-boot's prompt is not meaningful, | then... :( | | Should I file a bug report ? Yes, it's telling you about the upstream git version / date I guess, but we don't intend to update U-Boot from upstream at all if we can get away with it. So only our build info is interesting. Anyway it is the right build :-) As you may have seen from my previous message, there's no bug there, only the fact that I wasn't booting from NAND, but still from the factory version in NOR. I updated http://wiki.openmoko.org/wiki/Flashing_the_Neo_FreeRunner in order to provide more detailed instructions for others that may face the same situation. Thanks for your time. Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Worrisome output from opkg -test update in 2007.2
Dale Schumacher [EMAIL PROTECTED] writes: On Sun, Aug 3, 2008 at 6:35 AM, Jeffrey Ratcliffe [EMAIL PROTECTED] wrote: 2008/8/2 Olivier Berger [EMAIL PROTECTED]: Doing an opkg remove gtk+-fastscaling and opkg upgrade gtk+ solved the issue, I think. YMMV though. I needed opkg remove -force-depends gtk+-fastscaling but otherwise this sorted out the error messages. Thank you. I really appreciate the work-around for gtk+. However I think this represents an example of a deeper issue. How many -force-depends, -nodeps or remove foo / install bar are we expecting new users to navigate when trying to upgrade from their factory configurations? Is it not possible to get the package dependencies properly defined so that opkg will just work? I suppose you'd like to check https://docs.openmoko.org/trac/ticket/1650 which seems to explain where the issue comes from, AFAICT... maybe this will enlighten you a bit more ? Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Worrisome output from opkg -test update in 2007.2
Dale Schumacher [EMAIL PROTECTED] writes: Finally we have these messages: Collected errors: * Package gtk+ wants to install file /usr/lib/libgtk-x11-2.0.so.0 But that file is already provided by package * gtk+-fastscaling * Package gtk+ wants to install file /usr/lib/libgdk_pixbuf_xlib-2.0.so.0 SNIP You may have a look at https://docs.openmoko.org/trac/ticket/1650 which relates, I think to this issue. Doing an opkg remove gtk+-fastscaling and opkg upgrade gtk+ solved the issue, I think. YMMV though. Regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Battery discharging after long time connected to the power charger ?
Joerg Reisenweber [EMAIL PROTECTED] writes: Please note: 1) Openmoko does NOT recommend to do this, nor is it usually necessary when using the OM-charger or a standard powered host at PC. It's a hack for non-OM wallchargers only. I assume it would also be valid for car chargers like http://wiki.openmoko.org/wiki/USB_charger#sold_as_.22Essentiel_b_.28Boulanger.29.22_Chargeur_allume-cigares.2FUSB ... as I did it ;) My 2 cents. Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Battery discharging after long time connected to the power charger ?
Hi. I've just noticed something strange. If 'm not mistaken, the battry was reported discharging (whith 'apm') while the FR was connected to the power charger (provided with the FR). I had left the FR plugged to the power charger during all night, and thismorning, after waking up (maybe not enough), I checked the battery status with the command-line apm command, and was surprised to see the battery reported at 85%, off-line, battery status high 85% ... What's happening at night that would stop the charging (either software-side or charger-side ?) ? Thanks in advance for your comments. Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: SSH into Freerunner
shawn sullivan [EMAIL PROTECTED] writes: Thanks Steven. I've actually tried both variations with the same results. I thought maybe my system was getting confused w/ the 192.168.0.200. Looks like you may need to learn basic TCP/IP networking. If your freerunner is configured to known itself as 192.168.0.202, then your should talk to it on that address (and not 192.168.1.202). And you should do it from your other host which should be 192.168.0.200 too)... Then of course if your already had a network interface with routing using 192.168.0.x it would be confusing for your host. Unless you're doing bridging, but that shouldn't usually be the case. Hope this helps anyway. Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: opkg upgrade = endless IRQ messages
Brian C [EMAIL PROTECTED] writes: That doesn't seem like a great way for the opkg upgrade process to terminate, and it leaves me wondering which packages upgraded and which didn't. Is anyone else experiencing this? Have you tried and upgrade from inside X ? You should to the upgrade from a ssh session IMHO... But this would lead to another problem. My suggestion : 1. connect into the terminal app in the GUI 2. there type/tap opkg update 3. also there type/tap opkg upgrade dropbear 4. connect via SSH 5. inside the SSH shell, do opkg upgrade This was the only way I found to upgrade (almost) everything. Hope this helps. Best regards, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
