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
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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 | 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. | 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. There's a build date on the menu and coming out of the serial console as you saw. 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 About the patchlevel, the git hash in the filename lets you check here http://git.openmoko.org/?p=u-boot.git;a=shortlog;h=stable and find out what patches are in and out. In the stable trees (although this isn't true for stable-2.6.26 yet) we only add patches, so if you hover on each patch near the top (and look at the URL in your browser status bar) you can find the matching git hash for the patch that was at the top when the package was made. Right now the topmost patch in git is 64eb10cab80... mentioned in the package, so you know you have all the patches in there. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEUEARECAAYFAkiWtDAACgkQOjLpvpq7dMoTdwCfXJ/SCs9i8NtyKknmE0tmUZj7 V5wAl1FBvODJVndD3Uo13ALcLcNu9lY= =up7h -END PGP SIGNATURE- ___ 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
2008/8/4 Olivier Berger [EMAIL PROTECTED]: 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 :-/ No, I have Aug 4 now that I flashed u-boot. But are you looking at the NOR u-boot (unchanged) or NAND (flashed)? ___ 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
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. HTH, Konstantin ___ 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
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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 :-) - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiW3DUACgkQOjLpvpq7dMouwACfQ5xddtJeF3suz/bBoVVaoz5a YkcAn0b5cPZyWeS5JqPXxcCVzt6nVOyX =fdh3 -END PGP SIGNATURE- ___ 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: Upgrading u-boot needed ? - Was: Re: opkg upgrade breaks USB networking: g_ether module missing
On Mon, 2008-08-04 at 14:09 +0200, Olivier Berger wrote: 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, hmm, I assume the default boot is nand? (that is just pressing the power button) Is it possible to tell on a running FR what it booted from? BillK -- William Kenworthy [EMAIL PROTECTED] Home in Perth! ___ 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
Normal boot (just pressing the power button) uses the NAND. more info at http://wiki.openmoko.org/wiki/Boot On Mon, Aug 4, 2008 at 9:02 AM, William Kenworthy [EMAIL PROTECTED]wrote: On Mon, 2008-08-04 at 14:09 +0200, Olivier Berger wrote: 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, hmm, I assume the default boot is nand? (that is just pressing the power button) Is it possible to tell on a running FR what it booted from? BillK -- William Kenworthy [EMAIL PROTECTED] Home in Perth! ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ 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
Olivier Berger wrote: 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 ? I would consider it a bug that the version on u-boot's prompt is not meaningful, although I know in some cases that comes out of the source control package automatically and is not easily fixed. Is that the case in our case, or is this an error that can be fixed? ___ 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
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | # 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 ? | | | I would consider it a bug that the version on u-boot's prompt is not | meaningful, although I know in some cases that comes out of the source | control package automatically and is not easily fixed. Is that the case | in our case, or is this an error that can be fixed? It turned out the guy was booting his NOR U-Boot and reporting the version data from that. He said his NAND U-Boot version string when he did see it was good (ie, had the correct date and git hash). - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiXQwMACgkQOjLpvpq7dMqHTQCfcnweBXMKAk2zAZabxZKUzhAE +6UAn0rYPJe19mG9E53jcjgpWZxrWGQB =DA6m -END PGP SIGNATURE- ___ 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 wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | # 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 ? | | | I would consider it a bug that the version on u-boot's prompt is not | meaningful, although I know in some cases that comes out of the source | control package automatically and is not easily fixed. Is that the case | in our case, or is this an error that can be fixed? It turned out the guy was booting his NOR U-Boot and reporting the version data from that. He said his NAND U-Boot version string when he did see it was good (ie, had the correct date and git hash). Ah. Then all is well. M ___ 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
On Mon, Aug 4, 2008 at 7:57 PM, Andy Green [EMAIL PROTECTED] wrote: It turned out the guy was booting his NOR U-Boot and reporting the version data from that. He said his NAND U-Boot version string when he did see it was good (ie, had the correct date and git hash). 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 [EMAIL PROTECTED]:~# HTH -- Regards, Torfinn Ingolfsen ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
