Re: Uboot
Am Mi 6. August 2008 schrieb Andy Green: > Somebody in the thread at some point said: > |> I had this problem when I put obexftp into the startup for my bluez. > Turns out it doesn't auto-background, so it was hanging there just > after the startup. Happily, I was able to ssh in, fix it, and kill the > obexftp to let it start up normal. Can you ssh in via USB still? If so > look at the last started process before your shell and see if it's hung. > |> > |> > | > | The process '/bin/ash /etc/rc5.d/S98qpe start' is constantly in the > | process list, so it looks like that's where it's hanging. If I kill this > | and restart it, it hangs again at the command-line as well until I ^C > | it. What is it about the most recent updates that could have caused this? > > IIRC qpe is the thing that likes to sit there going through your SD card > contents after boot, making things slugglish. Maybe that's why it is > "hung"? SD-card IO-error? /jOERG signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Uboot
> > IIRC qpe is the thing that likes to sit there going through your SD card > contents after boot, making things slugglish. Maybe that's why it is > "hung"? > > - -Andy > I thought qpe was 'Qtopia Palmtop Environment'... or perhaps you were just being facetious ;) . Although I must admit, the only reason I assumed it was 'hanging' was because nothing comes up on the screen. I started another thread last night called 'Qtopia post-mortem' with output from logread, and there's a whole lot of stuff about 'undefined symbols' which appears to be related to Qtopia itself. I just don't see how an upgrade would affect the Qtopia binaries in that way... Aaron ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Led light stay on after boot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | 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 ;) It's not pretty in there. I guess this is today's topic for debug action. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiZSTEACgkQOjLpvpq7dMrCMQCeNpp5qDv6BYVO6ywWEy57u5GY qxEAniyuLYwFeezKMTC++msXm4y1tSm8 =9kDU -END PGP SIGNATURE- ___ 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: Uboot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: |> I had this problem when I put obexftp into the startup for my bluez. Turns out it doesn't auto-background, so it was hanging there just after the startup. Happily, I was able to ssh in, fix it, and kill the obexftp to let it start up normal. Can you ssh in via USB still? If so look at the last started process before your shell and see if it's hung. |> |> | | The process '/bin/ash /etc/rc5.d/S98qpe start' is constantly in the | process list, so it looks like that's where it's hanging. If I kill this | and restart it, it hangs again at the command-line as well until I ^C | it. What is it about the most recent updates that could have caused this? IIRC qpe is the thing that likes to sit there going through your SD card contents after boot, making things slugglish. Maybe that's why it is "hung"? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiZRSoACgkQOjLpvpq7dMpxXwCfbIGJXr8JhqOwR56NgtkOZLif XzwAoJEzkoKd/LTGY3E/8W91IjuI/k5u =FZFk -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Uboot
> I had this problem when I put obexftp into the startup for my bluez. Turns > out it doesn't auto-background, so it was hanging there just after the > startup. Happily, I was able to ssh in, fix it, and kill the obexftp to let > it start up normal. Can you ssh in via USB still? If so look at the last > started process before your shell and see if it's hung. > > The process '/bin/ash /etc/rc5.d/S98qpe start' is constantly in the process list, so it looks like that's where it's hanging. If I kill this and restart it, it hangs again at the command-line as well until I ^C it. What is it about the most recent updates that could have caused this? Aaron ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: distro-feed-configs_1.0-r0_om-gta02.ipk
Thanks, but /etc/opkg/*.conf still point to my-distribution.org, even though i overwrote the files...? has this not been fixed yet? atweb wrote: > 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. > > > cu > Markus > > > > 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. >> >> -Dale >> >> arne anka wrote: >> yeah, I saw that yesterday... I had to change manually the file again after the upgrade... >>> i was sure someone would run into this -- opkg asks you if you would >>> like to replace those files with then package maintainer's ones. >>> since i use debian i am familiar with this and almost automatically >>> hit D for diff'ing the old and the new file before deciding. >>> thus i could avoid overwriting. >>> >>> I do not know from where this adress comes from... >>> it's obviously the result of some testing with the package building >>> process that should never have made it into the feeds ... >>> >>> ___ >>> 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 >> > > > > ___ > 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: Date + NTP
Update the /etc/localtime symlink to point to your timezone: # ls -l /etc/localtime lrwxrwxrwx 1 root root 27 Jul 10 23:05 /etc/localtime -> /usr/share/zoneinfo/PST8PDT # ln -s /usr/share/zoneinfo/CST6CDT /etc/localtime Feydreva wrote: > Hello, > > i installed th NTP packet.. I set the date as the wiki says > so.. now > > date -u > Wed Aug 6 04:25:55 UTC 2008 > > date > Wed Aug 6 04:26:09 UTC 2008 > > > I did export TZ="CDT" > > > but it seems after, the FR change the TZ again to UTC > where can I choose my Timezone , and make sure the FR display the "good" > time ? > > regards > philippe > > > > > > ___ > 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: Led light stay on after boot
yeah, it turns off at one point... but it s not consistent... 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 > > W.Kenworthy wrote: > > Seems more to indicate the phone is active - doesnt seem to be tied to > > charging at all. Only stays off when phone is dead/suspended/off. Even > > on when screen saver is in effect, but not suspended. Charger on/off > > has no effect. > > > > Kernel of Aug 4th > > > > BillK > > > > > > On Tue, 2008-08-05 at 15:58 +0100, Andy Green wrote: > > > >> -BEGIN PGP SIGNED MESSAGE- > >> Hash: SHA1 > >> > >> Somebody in the thread at some point said: > >> > >> | "Yeah it indicates charging activity now." > >> | I have to try the kernel of August 5th... But on the one of August > 4th, > >> | the LED stays on even after disconnecting the power cable. > >> > >> That's not good :-/ > >> > >> - -Andy > >> -BEGIN PGP SIGNATURE- > >> Version: GnuPG v1.4.9 (GNU/Linux) > >> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org > >> > >> iEYEARECAAYFAkiYaq4ACgkQOjLpvpq7dMqqlwCeMCJ6BrSXT7qyEKDGLderu2Ze > >> gR0An3OCIw0weQFi0s+xGcAb1rDHf3Qn > >> =nUPi > >> -END PGP SIGNATURE- > >> > >> ___ > >> 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 > > > > > > > ___ > 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: distro-feed-configs_1.0-r0_om-gta02.ipk
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. cu Markus 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. -Dale arne anka wrote: yeah, I saw that yesterday... I had to change manually the file again after the upgrade... i was sure someone would run into this -- opkg asks you if you would like to replace those files with then package maintainer's ones. since i use debian i am familiar with this and almost automatically hit D for diff'ing the old and the new file before deciding. thus i could avoid overwriting. I do not know from where this adress comes from... it's obviously the result of some testing with the package building process that should never have made it into the feeds ... ___ 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 ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Date + NTP
Hello, i installed th NTP packet.. I set the date as the wiki says so.. now date -u Wed Aug 6 04:25:55 UTC 2008 date Wed Aug 6 04:26:09 UTC 2008 I did export TZ="CDT" but it seems after, the FR change the TZ again to UTC where can I choose my Timezone , and make sure the FR display the "good" time ? regards philippe ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: GPRS Problems w/ 2008.1
Craig Woodward <[EMAIL PROTECTED]> writes: > Receive serial link is not 8-bit clean: > Problem: all had bit 7 set to 0 Just curious, what does sudo stty -F /dev/ttySAC0 -a print? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
GPRS Problems w/ 2008.1
Ok, I'm getting something pretty odd now with GRPS setup. I'm trying this with 2008.1, which is probably a mistake, but... I'm getting a connection, and have used cu to tip in and see I'm getting what looks to me to be valid ppp setup packets spit back at me when I enter the commands manually. When I run it through ppp I'm getting the following (via logs). I've never seen this particular error, and am a little confused. I can see that the data coming across starts with ~y} after a manual connect, so I know it's trying to link. What's going on that manually it seems to be working but with pppd it's going 7-bit? Any ideas? =PPP LOG STARTS HERE= Serial connection established. using channel 1 Using interface ppp0 Connect: ppp0 <--> /dev/ttySAC0 sent [LCP ConfReq id=0x1] sent [LCP ConfReq id=0x1] sent [LCP ConfReq id=0x1] sent [LCP ConfReq id=0x1] sent [LCP ConfReq id=0x1] sent [LCP ConfReq id=0x1] sent [LCP ConfReq id=0x1] sent [LCP ConfReq id=0x1] sent [LCP ConfReq id=0x1] sent [LCP ConfReq id=0x1] LCP: timeout sending Config-Requests Connection terminated. Receive serial link is not 8-bit clean: Problem: all had bit 7 set to 0 Serial connection established. using channel 2 Using interface ppp0 Connect: ppp0 <--> /dev/ttySAC0 disconnect script failed sent [LCP ConfReq id=0x2] sent [LCP ConfReq id=0x2] sent [LCP ConfReq id=0x2] sent [LCP ConfReq id=0x2] sent [LCP ConfReq id=0x2] sent [LCP ConfReq id=0x2] sent [LCP ConfReq id=0x2] sent [LCP ConfReq id=0x2] sent [LCP ConfReq id=0x2] sent [LCP ConfReq id=0x2] LCP: timeout sending Config-Requests Connection terminated. Receive serial link is not 8-bit clean: Problem: all had bit 7 set to 0 tcflush failed: Bad file descriptor Connect script failed Modem hangup =PPP LOG ENDS= ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Buzzing sound
moved thread to [hardware]-ml, please continue there. This thread closed and discontinued. thanks jOERG signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Led light stay on after boot
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 W.Kenworthy wrote: > Seems more to indicate the phone is active - doesnt seem to be tied to > charging at all. Only stays off when phone is dead/suspended/off. Even > on when screen saver is in effect, but not suspended. Charger on/off > has no effect. > > Kernel of Aug 4th > > BillK > > > On Tue, 2008-08-05 at 15:58 +0100, Andy Green wrote: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Somebody in the thread at some point said: >> >> | "Yeah it indicates charging activity now." >> | I have to try the kernel of August 5th... But on the one of August 4th, >> | the LED stays on even after disconnecting the power cable. >> >> That's not good :-/ >> >> - -Andy >> -BEGIN PGP SIGNATURE- >> Version: GnuPG v1.4.9 (GNU/Linux) >> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org >> >> iEYEARECAAYFAkiYaq4ACgkQOjLpvpq7dMqqlwCeMCJ6BrSXT7qyEKDGLderu2Ze >> gR0An3OCIw0weQFi0s+xGcAb1rDHf3Qn >> =nUPi >> -END PGP SIGNATURE- >> >> ___ >> 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 > > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: distro-feed-configs_1.0-r0_om-gta02.ipk
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. -Dale arne anka wrote: >> yeah, I saw that yesterday... I had to change manually the file again >> after >> the upgrade... >> > > i was sure someone would run into this -- opkg asks you if you would like > to replace those files with then package maintainer's ones. > since i use debian i am familiar with this and almost automatically hit D > for diff'ing the old and the new file before deciding. > thus i could avoid overwriting. > > >> I do not know from where this adress comes from... >> > > it's obviously the result of some testing with the package building > process that should never have made it into the feeds ... > > ___ > 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: Uboot
I had this problem when I put obexftp into the startup for my bluez. Turns out it doesn't auto-background, so it was hanging there just after the startup. Happily, I was able to ssh in, fix it, and kill the obexftp to let it start up normal. Can you ssh in via USB still? If so look at the last started process before your shell and see if it's hung. Aaron Sowry <[EMAIL PROTECTED]> wrote: = >> There are 3 versions for the gta02v5 - what is the >> difference? >> > > apparently the creation date. > > Naw... they're the same creation date, the only difference seems to be the `1.3.1+gitr`[22|26|30] part of the filename. I've just flashed the 'latest' one anyway - Andy Green mentioned it could be related to the build problems lately. Side note - the reason I'm flashing is because after doing an opkg update/upgrade on the Qtopia distro, it will no longer boot. It gets to the point where it looks like it should be loading up the GUI (tiny blinking cursor in the top left, nothing else on the screen) and hangs there. Anyone else had this problem? Aaron p.s. doesn't look like flashing u-boot helped either :( ___ 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: Led light stay on after boot
Seems more to indicate the phone is active - doesnt seem to be tied to charging at all. Only stays off when phone is dead/suspended/off. Even on when screen saver is in effect, but not suspended. Charger on/off has no effect. Kernel of Aug 4th BillK On Tue, 2008-08-05 at 15:58 +0100, Andy Green wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > > | "Yeah it indicates charging activity now." > | I have to try the kernel of August 5th... But on the one of August 4th, > | the LED stays on even after disconnecting the power cable. > > That's not good :-/ > > - -Andy > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org > > iEYEARECAAYFAkiYaq4ACgkQOjLpvpq7dMqqlwCeMCJ6BrSXT7qyEKDGLderu2Ze > gR0An3OCIw0weQFi0s+xGcAb1rDHf3Qn > =nUPi > -END PGP SIGNATURE- > > ___ > 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: Uboot
Neng-Yu Tu (Tony Tu) wrote: > Aaron Sowry ??: >> I've found the daily u-boot images at >> http://buildhost.openmoko.org/daily/freerunner/200808/20080805/ >> >> Which one do I use? There are 3 versions for the gta02v5 - what is the >> difference? It's even four ! r22, r26, r30, and r34. Besides having different git "depths" and different build times, all these "gta02v5" versions are bitwise identical. So I pass this question to our daily builders: why so many if just one would do nicely ? ;-) - Werner ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: distro-feed-configs_1.0-r0_om-gta02.ipk
> yeah, I saw that yesterday... I had to change manually the file again > after > the upgrade... i was sure someone would run into this -- opkg asks you if you would like to replace those files with then package maintainer's ones. since i use debian i am familiar with this and almost automatically hit D for diff'ing the old and the new file before deciding. thus i could avoid overwriting. > I do not know from where this adress comes from... it's obviously the result of some testing with the package building process that should never have made it into the feeds ... ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: distro-feed-configs_1.0-r0_om-gta02.ipk
yeah, I saw that yesterday... I had to change manually the file again after the upgrade... http://my-distribution.org/remote-feed/ was also the adresse when you image with FSO I do not know from where this adress comes from... On Tue, Aug 5, 2008 at 1:55 PM, arne anka <[EMAIL PROTECTED]> wrote: > 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! > > ___ > 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
distro-feed-configs_1.0-r0_om-gta02.ipk
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! ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: ASU repository location and package for this
from http://wiki.openmoko.org/wiki/ASU "It launched on August 08, 2008." So I guess we will not have the images nor the feed before this date.. On Tue, Aug 5, 2008 at 2:14 PM, Christoph Anton Mitterer < [EMAIL PROTECTED]> wrote: > Hi. > > Can someone please provide me the current main location for the > ASU/2008.8 image? Is it on buildhost or downloads? > > Would be best if you could post the whole /etc/opkg/ stuff. > > And please create a package for this > > Thanks, > Chris. > > ___ > 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: Buzzing sound
Am Mi 6. August 2008 schrieb Andy Green: > I didn't really get to believe it is specifically radiated RF coupling > yet, it can still be RF conducted via PSU. Just something to bear in mind. Ok, we can not exclude this. Actually it's quite possible. Anyway we need a decent test under controlled environment (analyze exact level of noise in dB, at a known PCL), then we easily could tell. There are reports that connecting an external antenna stopped the noise completely, which would give a cue in direction radiated RF coupling. Alas nobody approached the external antenna to the GTA02 to test whether noise starts with this procedure. Also the absence of noise with ext ant could be a result of better antenna gain leading to BS leveling down PCL. You see there are a lot of tests, some of them rather simple, most of them not even clear wrt their setup, that all need to be done until I leave next week. cheers jOERG signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia image at /media/card directory
Alex Kavanagh wrote: > Hi > > I've been running the qtopia image for a few days and I'd like to dual > boot it with the ASU or FSO image just to keep an eye on what is > happening with them. > > Thus I have the qtopia in the main flash, and I'd like to put the ASU or > FSO image into the SD card. > > However, I ran into a problem. the SD card is mounted at /meda/card > (it's the original card that came with the phone), and there is a > qtopia_db.sqlite file on it. > > And sure enough the qpe process has open file handles on it and so is > clearly using it. > > Does anyone know where the config option is for moving this file off > /media/card? I can't find it anywhere after grepping the whole device > for /media/card, card, /media, etc. Look in ~/Settings/Trolltech/Storage.conf (or /opt/Qtopia/etc/default/Trolltech.Storage.conf) In the [MountPoint0] section, change ContentDatabase = 1 to ContentDatabase = 0 Does this help? > > The other option is just to take /media/card out of fstab so it ends up > on the main flash - but then I don't know whether qpe (and friends) are > finding the card through other means (e.g. the block device or MTD, etc.). > > Anyone know? > > Cheers > Alex. > > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > -- Lorn 'ljp' Potter Software Engineer, Systems Group, Trolltech, a Nokia company ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
ASU repository location and package for this
Hi. Can someone please provide me the current main location for the ASU/2008.8 image? Is it on buildhost or downloads? Would be best if you could post the whole /etc/opkg/ stuff. And please create a package for this Thanks, Chris. smime.p7s Description: S/MIME cryptographic signature ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Buzzing sound
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Am Mi 6. August 2008 schrieb Andy Green: |> Somebody in the thread at some point said: |> |> |> Just a note, on the "skelephone" that I use I replaced the GSM antenna |> |> with a short length of patch wire, it still works (and some guy was |> |> complaining normal GTA02 is for hardcore hackers). I guess if I |> |> shortened it further, it can force base station to tell me to use max |> |> power all the time. RF performance seems fine with $WIRE like 5cm long. |> |> ... |> |> | the device can emit. So maybe this could be one of the possible fixes for |> | this issue (a very nasty one, that probably even won't yield the desired |> | results) to reduce gain by crippling the built-in antenna. |> |> Gah no not a suggested fix, just to remove one of the variables about |> provoking the problem in as consistently bad a form as possible :-)) | | Yup, but as I elaborated in my last posting, the resulting RF field will stay | at same level (to the point where MaxTXPower of amp limits further | adjustment), so probably will the noise. :-/ I didn't really get to believe it is specifically radiated RF coupling yet, it can still be RF conducted via PSU. Just something to bear in mind. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiYl3sACgkQOjLpvpq7dMoSrQCfVPLV7pC07/+A7JHGxttLNq3p //MAnjWcATY6UIV5cnIylInbdx6X5UP/ =U+ND -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Buzzing sound
On Tue, 2008-08-05 at 18:56 +0800, Joerg Reisenweber wrote: > Local has never been a related issue. It's always far end that "get's the > buzz". Quite basic and important to understand. We have *two* distinct > audio-transfers with opposite directions. Buzz is on > FR->(mixer,GSM)->far_end only. > If you hear local buzz, your mixer/gsm-sidetone settings are somewhat > incorrect. > > I'd appreciate such a wikipage and the reports there very much. > Additional needed info: GSM-band (we don't know all providers!), signal-level > GSM > In fact that's what I did in Germany, collect reports from users about noise. > I even had them call my answering machine so I actually collected some real > audio samples as *.wav. Result: in Germany it's virtually only E+ that's > causing the noise. > > Anyway still this makes no database for a guess on percentage of users that > suffer from complaints of their callees about buzz-noise. Just to add to the E+ 900 vs. 1800: Orange France uses 900/1800 and my phones all suffer from the buzz but not always and not reproducibly. Except with the headphones, they can make it so loud the communication becomes impossible. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Qtopia post-mortem
Hi, I have just now flashed my Freerunner with today's uboot and the latest Qtopia uImage and rootfs available from their website. After flashing it boots up fine, and I run 'opkg update' followed by 'opkg upgrade' which results in a lengthy process but seems to complete successfully. After the upgrade the applications seem to launch fine but the settings result in the following error (shown by logread while trying to launch the 'appearance' setting): Aug 5 16:38:36 om-gta02 user.notice Qtopia: /opt/Qtopia/bin/appearance: /usr/lib/libstdc++.so.6: no version information available (required by /opt/Qtopia/lib/libQtSvg.so.4) ...[there are a huge number of these with only the 'required by' file changing]... Aug 5 16:38:36 om-gta02 user.notice Qtopia: /opt/Qtopia/bin/appearance: symbol lookup error: /opt/Qtopia/lib/libqtopia.so.4: undefined symbol: _ZN17QAbstractItemView14dragEnterEventEP15QDragEnterEvent After a reboot, everything seems to go fine right up until the point which the Qtopia GUI tries to load. There it gets stuck with a totally blank screen except for a blinking cursor in the upper left-hand corner, red LED on (stays on when USB cable is removed). The screen seems to dim if left alone for a while, and I can still SSH into the Freerunner in this state. From the logs: Aug 5 16:47:11 om-gta02 user.notice Qtopia: qpe: /usr/lib/libstdc++.so.6: no version information available (required by /opt/Qtopia/lib/libQtGui.so.4) Aug 5 16:47:11 om-gta02 user.notice Qtopia: qpe: /usr/lib/libstdc++.so.6: no version information available (required by /opt/Qtopia/lib/libQtNetwork.so.4) ...[etc]... Aug 5 16:47:12 om-gta02 user.notice Qtopia: qpe: symbol lookup error: /opt/Qtopia/lib/libqtopiapim.so.4: undefined symbol: _ZN11QListWidget9dropEventEP10QDropEvent Most of these messages repeat themselves ad nauseum - I've seen the 'no version information' messages before with no apparent side effects, but the 'undefined symbol' one is new to me. Anyone have any ideas how I should be troubleshooting this? Aaron ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Uboot
Aaron Sowry ??: > I've found the daily u-boot images at > http://buildhost.openmoko.org/daily/freerunner/200808/20080805/ > > Which one do I use? There are 3 versions for the gta02v5 - what is the > difference? > > Aaron > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support Only v5 is production sale version, after all after v5 u-boot should could auto detect hardware version and pass correct ATAG to kernel. Tony Tu ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Led light stay on after boot
On Tue, Aug 5, 2008 at 8:28 PM, Andy Green <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > > | "Yeah it indicates charging activity now." > | I have to try the kernel of August 5th... But on the one of August 4th, > | the LED stays on even after disconnecting the power cable. > > That's not good :-/ No its not. :-) . Yeah, it happens with the 5th august one as well. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Buzzing sound
Am Mi 6. August 2008 schrieb Andy Green: > Somebody in the thread at some point said: > > |> Just a note, on the "skelephone" that I use I replaced the GSM antenna > |> with a short length of patch wire, it still works (and some guy was > |> complaining normal GTA02 is for hardcore hackers). I guess if I > |> shortened it further, it can force base station to tell me to use max > |> power all the time. RF performance seems fine with $WIRE like 5cm long. > > ... > > | the device can emit. So maybe this could be one of the possible fixes for > | this issue (a very nasty one, that probably even won't yield the desired > | results) to reduce gain by crippling the built-in antenna. > > Gah no not a suggested fix, just to remove one of the variables about > provoking the problem in as consistently bad a form as possible :-)) Yup, but as I elaborated in my last posting, the resulting RF field will stay at same level (to the point where MaxTXPower of amp limits further adjustment), so probably will the noise. :-/ /j signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Buzzing sound
Joerg Reisenweber wrote: > BS decides on this depending on signal-quality of MS as BS sees it. > It would be *very* helpful to confirm this, by using some RF-meter (e.g. > microwave leakage tester?), and/or reading the battery current, while > observing the noise come and go- I tested this a while ago with my Neo1973, and the noise did get quieter as the RF level went down. I can't quantify this - it was just subjective observations. The test was a cheap Radio Shack microwave leakage tester and the phone sitting next to each other on my desk (not moved during the test). I covered both of them with a metal mixing bowl to block some of the RF signal. After I removed the bowl, the RF level stepped down a few times (a couple of seconds between steps) and the buzzing got quieter at each step. I didn't look at the battery current. The Neo was transmitting audio throughout this test. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Buzzing sound
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: |> Just a note, on the "skelephone" that I use I replaced the GSM antenna |> with a short length of patch wire, it still works (and some guy was |> complaining normal GTA02 is for hardcore hackers). I guess if I |> shortened it further, it can force base station to tell me to use max |> power all the time. RF performance seems fine with $WIRE like 5cm long. ... | the device can emit. So maybe this could be one of the possible fixes for | this issue (a very nasty one, that probably even won't yield the desired | results) to reduce gain by crippling the built-in antenna. Gah no not a suggested fix, just to remove one of the variables about provoking the problem in as consistently bad a form as possible :-)) - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiYfmIACgkQOjLpvpq7dMohLACggbn5tKAPbdzBeelvEtQQ8tbf YUsAoIm3rNels44Xn6vLDJB2GQHioXMZ =dvKl -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Buzzing sound
Am Di 5. August 2008 schrieb Andy Green: > Somebody in the thread at some point said: > > |> So it comes and goes in discrete steps and it lags behind the change of > |> position. > | > | That's exactly the behaviour we would expect when noise is related to > | MS-TXPower controlled by a PCL command from BS. BS isn't responding to > any > | momentary change in signal-strength of inbound MS-signal, instead BS does > > Sounds good. > > Just a note, on the "skelephone" that I use I replaced the GSM antenna > with a short length of patch wire, it still works (and some guy was > complaining normal GTA02 is for hardcore hackers). I guess if I > shortened it further, it can force base station to tell me to use max > power all the time. RF performance seems fine with $WIRE like 5cm long. When shorting the wire, we reduce antenna gain. This basically means we need more power from battery, to have the same RF signal strength. So yes, probably BS would level up the PCF, but only to the point where we have same local RF field around GTA02. As noise is supposed to be introduced to GTA02 by own (and externally applied) RF, and not by battery current LF/DC, the only effect would be a reduced battery life time. In fact it's the SWR [http://en.wikipedia.org/wiki/Standing_wave_ratio] that gets worse when creating a impedance missmatch by shortening antenna, so a part of the RF-power is reflected at antenna rot point and fed back to amplifier and dissipated producing heat. Depending on power and design of last amplifier stage this can even burn out the amplifier. Of course reducing the antenna gain is a little bit like flashing another power class to the firmware, in that it limits the maximum effective RF power the device can emit. So maybe this could be one of the possible fixes for this issue (a very nasty one, that probably even won't yield the desired results) to reduce gain by crippling the built-in antenna. cheers jOERG signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
qtopia image at /media/card directory
Hi I've been running the qtopia image for a few days and I'd like to dual boot it with the ASU or FSO image just to keep an eye on what is happening with them. Thus I have the qtopia in the main flash, and I'd like to put the ASU or FSO image into the SD card. However, I ran into a problem. the SD card is mounted at /meda/card (it's the original card that came with the phone), and there is a qtopia_db.sqlite file on it. And sure enough the qpe process has open file handles on it and so is clearly using it. Does anyone know where the config option is for moving this file off /media/card? I can't find it anywhere after grepping the whole device for /media/card, card, /media, etc. The other option is just to take /media/card out of fstab so it ends up on the main flash - but then I don't know whether qpe (and friends) are finding the card through other means (e.g. the block device or MTD, etc.). Anyone know? Cheers Alex. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Uboot
>>> There are 3 versions for the gta02v5 - what is the >>> difference? >> apparently the creation date. > Naw... they're the same creation date, the only difference seems to be > the `1.3.1+gitr`[22|26|30] part of the filename. well, in my browser the "last modified" column has thre different times: 4:18, 13:24, 16:05. uboot-gta02v5-latest.bin has 16:05. > Side note - the reason I'm flashing is because after doing an opkg > update/upgrade on the Qtopia distro, it will no longer boot. It gets to > the point where it looks like it should be loading up the GUI (tiny > blinking cursor in the top left, nothing else on the screen) and hangs > there. Anyone else had this problem? > > Aaron > > p.s. doesn't look like flashing u-boot helped either :( can you log in via usb? if so, have a look at the log with logread. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Uboot
>> There are 3 versions for the gta02v5 - what is the >> difference? >> > > apparently the creation date. > > Naw... they're the same creation date, the only difference seems to be the `1.3.1+gitr`[22|26|30] part of the filename. I've just flashed the 'latest' one anyway - Andy Green mentioned it could be related to the build problems lately. Side note - the reason I'm flashing is because after doing an opkg update/upgrade on the Qtopia distro, it will no longer boot. It gets to the point where it looks like it should be loading up the GUI (tiny blinking cursor in the top left, nothing else on the screen) and hangs there. Anyone else had this problem? Aaron p.s. doesn't look like flashing u-boot helped either :( ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Uboot
> Which one do I use? uboot-gta02v5-latest.bin > There are 3 versions for the gta02v5 - what is the > difference? apparently the creation date. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Uboot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | I've found the daily u-boot images at | http://buildhost.openmoko.org/daily/freerunner/200808/20080805/ | | Which one do I use? There are 3 versions for the gta02v5 - what is the | difference? I guess this is an outcome of the buildhost issues that are happening at the moment. They're all the same git hash and same size, I guess they are all identical. Normally there'd be just the one a day. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiYdgcACgkQOjLpvpq7dMrohwCfaqoW9TXs0eHRB2NSQjP+SdjN t9AAn0sqeCS3BvCRl7n72Kp3Dim149or =s3pA -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Uboot
I've found the daily u-boot images at http://buildhost.openmoko.org/daily/freerunner/200808/20080805/ Which one do I use? There are 3 versions for the gta02v5 - what is the difference? Aaron ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qtopia Questions/Bugs/Suggestions
Ole Kliemann wrote: > > But a new problem has appeared. When resuming after long suspend I only > get a white screen. It can sometimes be fixed by pressing something. > Maybe something that forces full redraw? > > This problem was not when using the kernel that came with the Qtopia > image form 20080724. I have the same problem, plus one. I've compiled /opt/Qtopia from source (20080804) and substituted the whole directory as described in another thread, now sometimes the screen blanks and yesterday after wake up I could not hear the speaker on the other side, neither the ringtone when I was dialing. He could hear me, on the other side. Is there a butrack for Qtopia on freerunner? ciao, leonardo. -- http://leonardo.lilik.it Key fingerprint = 2C20 A587 05AC 42E5 1292 D0D4 3EED CFB5 52FD AD1E ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Is a 12 MB/s microSD overkill for what the glamo driver does?
I used dd(1) to read 100M from each the stock SD card and one that is supposedly rated at 12MB/sec and there was not any noticeable difference is rate of transfer. The rate was about 3 megabytes per second - same as what Andy Green said he saw. I had already ordered that SD before I learned from Tim S. that the bus is at 7MB/s. So I'm returning the 4GB card to get one (from newegg) that is 8GB and not concerning myself with it's speed. On Thu, Jul 31, 2008 at 12:23 PM, Tim Schmidt <[EMAIL PROTECTED]> wrote: > On Thu, Jul 31, 2008 at 4:11 PM, Esben Stien <[EMAIL PROTECTED]> > wrote: > > "Jim Colton" <[EMAIL PROTECTED]> writes: > > > >> in M bytes per second > > > > Please use new SI convention, Mi (Mebi), Gi (Gibi), Ti (Tebi). > > > > It's also a nice convention to use octects, o, instead of bytes, as > > bytes are not always 8 bits. > > > > So, to be perfectly clear, 1Mio (Mebiotctet), 1Gio (Gibioctet), 1Gib > > (Gibibit). > > No, thank you. > > 50+ years of computer science has already resulted in perfectly usable > standard units. > > --tim > > ___ > 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: gta02, 2007.2: state of upgrades
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | On Sat, 2008-08-02 at 14:00 +0100, Andy Green wrote: |> Tomorrow's U-Boot is recommended. Current U-Boot has 50% chance per |> boot of breaking USB device for the session (including in Linux). | Which one is this exactly? | http://buildhost.openmoko.org/daily/freerunner/200808/20080805/u-boot-gta02v5-1.3.1+gitr30+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb-r0.bin ? Looks good. | Does this still have any serious bugs? What can I say... probably. Nothing springs to mind though. | Should I only upgrade the uboot in NAND (by first booting into NOR uboot | and then doing a | dfu-util -a u-boot -R -D u-boot-gta02v5-1.3.1+gitr30 | +64eb10cab8055084ae25ea4e73b66dd03cc1a0cb-r0.bin)? Looks reasonable. | Or also that one in NOR? No best to leave the NOR guy alone. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiYclMACgkQOjLpvpq7dMq/CgCfb3+L5VI22Eg2csJu8AhzFJ0e Q14An3awZtjXcq1AXd7P12yZ/kAujCZX =aYNX -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: gta02, 2007.2: state of upgrades
On Sat, 2008-08-02 at 14:00 +0100, Andy Green wrote: > Tomorrow's U-Boot is recommended. Current U-Boot has 50% chance per > boot of breaking USB device for the session (including in Linux). Which one is this exactly? http://buildhost.openmoko.org/daily/freerunner/200808/20080805/u-boot-gta02v5-1.3.1+gitr30+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb-r0.bin ? Does this still have any serious bugs? Should I only upgrade the uboot in NAND (by first booting into NOR uboot and then doing a dfu-util -a u-boot -R -D u-boot-gta02v5-1.3.1+gitr30 +64eb10cab8055084ae25ea4e73b66dd03cc1a0cb-r0.bin)? Or also that one in NOR? Thanks, Chris. smime.p7s Description: S/MIME cryptographic signature ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Led light stay on after boot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | "Yeah it indicates charging activity now." | I have to try the kernel of August 5th... But on the one of August 4th, | the LED stays on even after disconnecting the power cable. That's not good :-/ - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiYaq4ACgkQOjLpvpq7dMqqlwCeMCJ6BrSXT7qyEKDGLderu2Ze gR0An3OCIw0weQFi0s+xGcAb1rDHf3Qn =nUPi -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Led light stay on after boot
"Yeah it indicates charging activity now." I have to try the kernel of August 5th... But on the one of August 4th, the LED stays on even after disconnecting the power cable. On Tue, Aug 5, 2008 at 3:15 AM, Andy Green <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > | Ever since I flashed the latest firmware from > | http://buildhost.openmoko.org/daily/freerunner/200808/20080805/ , the > | led light stays light after boot. > | > | The files I used are : > | > > http://buildhost.openmoko.org/daily/freerunner/200808/20080805/openmoko-openmoko-devel-image-glibc-ipk--20080805-om-gta02.rootfs.jffs2 > | > > http://buildhost.openmoko.org/daily/freerunner/200808/20080805/uImage-2.6.24+git27+1a95efdc23966343a3b432ceef2f6c24dc0e2052-r2-om-gta02.bin > | > | I have never updated my u-boot since I got the phone. Does this have > | something to do with that? > > Yeah it indicates charging activity now. > > - -Andy > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org > > iEYEARECAAYFAkiX/gcACgkQOjLpvpq7dMocyQCfU3lQ936OXKUgJQn9HCmHstYX > cGkAn0ROh1rBAn3ht6DI+zE7F2+jAe/o > =dWnK > -END PGP SIGNATURE- > > ___ > 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: Buzzing sound
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: |> So it comes and goes in discrete steps and it lags behind the change of |> position. | | That's exactly the behaviour we would expect when noise is related to | MS-TXPower controlled by a PCL command from BS. BS isn't responding to any | momentary change in signal-strength of inbound MS-signal, instead BS does Sounds good. Just a note, on the "skelephone" that I use I replaced the GSM antenna with a short length of patch wire, it still works (and some guy was complaining normal GTA02 is for hardcore hackers). I guess if I shortened it further, it can force base station to tell me to use max power all the time. RF performance seems fine with $WIRE like 5cm long. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiYV8YACgkQOjLpvpq7dMpTUgCeIyqCmaFIWQT5UgnVkXE1ogK2 O1IAnRbaQQ0wYQSrIr5v+xJntJixMwlb =PNOQ -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Buzzing sound
Am Di 5. August 2008 schrieb Ole Kliemann: > On Tue, Aug 05, 2008 at 07:49:51PM +0800, Joerg Reisenweber wrote: > > Am Di 5. August 2008 schrieb Jeffrey Ratcliffe: > > > 2008/8/5 Andy Green <[EMAIL PROTECTED]>: > > > > Like Ole says when I started looking at it, by calling a landline in the > > > > same room and listening to its receiver lying on the desk, it varied > > > > tremendously and not in a repeatable way. Eg, it appeared to vary by > > > > orientation of the phone, but when I traced the path backwards, the buzz > > > > did not return. > > > > > > OK. Confirming this - the buzzing seems to come and go in waves of > > > varying frequency. Even without touching the phone, the buzzing just > > > comes and goes. > > > > I noticed the buzz come and go in discrete steps. I guess that's basestation > > sending PCL commands to mobile, to level up/down the TX-power. > > BS decides on this depending on signal-quality of MS as BS sees it. > > It would be *very* helpful to confirm this, by using some RF-meter (e.g. > > microwave leakage tester?), and/or reading the battery current, while > > observing the noise come and go- > > I can only observe: I did this test some weeks ago at my home. The FR > has signaficantly better signal when held out of the window. > > When holding out of the window during a call, it takes a short moment > then buzzing disappears quite suddenly. Going back into the room again > after a moment the buzzing returns suddenly. > > So it comes and goes in discrete steps and it lags behind the change of > position. That's exactly the behaviour we would expect when noise is related to MS-TXPower controlled by a PCL command from BS. BS isn't responding to any momentary change in signal-strength of inbound MS-signal, instead BS does some averaging on signal-quality and then decides to send a PCL to MS eventually. There are a maximum of 32 PCL steps, actually not all of them are valid for type of FR GSM-chipset. Remark: FR immediately tore down the connection, when I sent a PCL command to level up to an (invalid?) high powerlevel (PCL0. On "CMU200 universal radio communication tester", kind of a test-BS). But aside from that we still try to reproduce the noise under controlled test environment. Strange enough, so far there seems to be no noise when on CMU200. Anyway tests are not completed yet. So it's very important to get as much detail as possible on situations where noise actually is seen. Such as battery current, GSM-signal level, frequency etc. Quotes from R&S CMU200 manual: >> Power control level (PCL) Dynamic power control is used in GSM networks to reduce the output power of the mobile station as far as possible. In practice the base station sets the mobile power on a dimen- sionless scale of power control levels (PCL) ranging from 0 to 31. In GSM900, PCL 0 corresponds to the largest nominal output power (39 dBm), power control levels between 16 and 31 can be set for phase II mobiles only. In contrast to the PCL the power class characterizes the nominal maximum output power of the mobile. Depending on the power class of the mobile the range of possible PCL set- tings may be restricted. <<< GSM mobile phones are divided into different power classes according to their maximum output power: Power classNominal maximum output power in dBm GSM400GSM1800 GSM1900 GSM GT800 GSM850 GSM900 1 – 30 30 2 3924 24 3 3736 33 4 33 5 29 Besides, a dimensionless scale of power control levels (PCL) is determined for dynamic control of the mobile power: GSM Power control levels (PCL) Power control level, PCLNominal output power in dBm GSM400/ GSM1800GSM1900 GSM GT800 GSM850/ GSM900 0 39 3030 1 39 2828 2 39 2626 3 37 2424 4 35 2222 5 33 2020 6 31 1818 7 29 1616 8 27 1414 9 25 1212 10
Re: Buzzing sound
On Tue, Aug 05, 2008 at 07:49:51PM +0800, Joerg Reisenweber wrote: > Am Di 5. August 2008 schrieb Jeffrey Ratcliffe: > > 2008/8/5 Andy Green <[EMAIL PROTECTED]>: > > > Like Ole says when I started looking at it, by calling a landline in the > > > same room and listening to its receiver lying on the desk, it varied > > > tremendously and not in a repeatable way. Eg, it appeared to vary by > > > orientation of the phone, but when I traced the path backwards, the buzz > > > did not return. > > > > OK. Confirming this - the buzzing seems to come and go in waves of > > varying frequency. Even without touching the phone, the buzzing just > > comes and goes. > > I noticed the buzz come and go in discrete steps. I guess that's basestation > sending PCF commands to mobile, to level up/down the TX-power. > BS decides on this depending on signal-quality of MS as BS sees it. > It would be *very* helpful to confirm this, by using some RF-meter (e.g. > microwave leakage tester?), and/or reading the battery current, while > observing the noise come and go- I can only observe: I did this test some weeks ago at my home. The FR has signaficantly better signal when held out of the window. When holding out of the window during a call, it takes a short moment then buzzing disappears quite suddenly. Going back into the room again after a moment the buzzing returns suddenly. So it comes and goes in discrete steps and it lags behind the change of position. BTW: Not that I would know anything about these things. But would it be possible to lower the TX-power of the FR to see how far down you can go without loosing connection? I have active speakers in my room that catch GSM signals. I noticed several times that the noise in the speakers when the phone is registering is louder with the FR than with a Motorola V3x with the same SIM. pgpzcz4peRhUl.pgp Description: PGP signature ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Buzzing sound
Am Di 5. August 2008 schrieb Jeffrey Ratcliffe: > 2008/8/5 Andy Green <[EMAIL PROTECTED]>: > > Like Ole says when I started looking at it, by calling a landline in the > > same room and listening to its receiver lying on the desk, it varied > > tremendously and not in a repeatable way. Eg, it appeared to vary by > > orientation of the phone, but when I traced the path backwards, the buzz > > did not return. > > OK. Confirming this - the buzzing seems to come and go in waves of > varying frequency. Even without touching the phone, the buzzing just > comes and goes. I noticed the buzz come and go in discrete steps. I guess that's basestation sending PCF commands to mobile, to level up/down the TX-power. BS decides on this depending on signal-quality of MS as BS sees it. It would be *very* helpful to confirm this, by using some RF-meter (e.g. microwave leakage tester?), and/or reading the battery current, while observing the noise come and go- > > > Also, I had to keep whistling during this to provoke transmission > > actions that seem to be the start of the issue. > > You obviously need a signal generator for repeatability - unless you > have perfect pitch... Nah, that's just to give some data to GSM-chip it has to transmit. Otherwise it will enter dicontinuous transmission mode, means simply stopping to transmit as there's nothing but silence we had to send to the other end. So the actual pitch is irrelevant. Any kind of noise will do, as long as it's loud enough. cheers jOERG signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Buzzing sound
2008/8/5 Andy Green <[EMAIL PROTECTED]>: > Like Ole says when I started looking at it, by calling a landline in the > same room and listening to its receiver lying on the desk, it varied > tremendously and not in a repeatable way. Eg, it appeared to vary by > orientation of the phone, but when I traced the path backwards, the buzz > did not return. OK. Confirming this - the buzzing seems to come and go in waves of varying frequency. Even without touching the phone, the buzzing just comes and goes. > Also, I had to keep whistling during this to provoke transmission > actions that seem to be the start of the issue. You obviously need a signal generator for repeatability - unless you have perfect pitch... Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Buzzing sound
Am Di 5. August 2008 schrieb Jeffrey Ratcliffe: > 2008/8/5 Joerg Reisenweber <[EMAIL PROTECTED]>: > > Only thing you may try for now is changing GSM-provider, as it seems to be > > very clear the issue is to be found on some GSM-networks, and not (or less) > > on some others. Generally the 1800/1900 networks seem to be more likely to > > cause this problem than the 850/900 networks. For Germany I got reports f > > noise only for E+ network (and resellers) > > My experience on Blau (E+) is that I hear the caller excellently - but > the caller complains that buzzing is very bad. > > > Hard to tell. We don't get sufficient number of reports, and due to nature of > > reports nearly all are problem-reports, people without problems usually don't > > post a report. > > I suggest, therefore, a wiki page where users are encouraged to > document the line quality at both ends (good or bad) against their > provider. Local has never been a related issue. It's always far end that "get's the buzz". Quite basic and important to understand. We have *two* distinct audio-transfers with opposite directions. Buzz is on FR->(mixer,GSM)->far_end only. If you hear local buzz, your mixer/gsm-sidetone settings are somewhat incorrect. I'd appreciate such a wikipage and the reports there very much. Additional needed info: GSM-band (we don't know all providers!), signal-level GSM In fact that's what I did in Germany, collect reports from users about noise. I even had them call my answering machine so I actually collected some real audio samples as *.wav. Result: in Germany it's virtually only E+ that's causing the noise. Anyway still this makes no database for a guess on percentage of users that suffer from complaints of their callees about buzz-noise. cheers jOERG signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Buzzing sound
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | 2008/8/5 Andy Green <[EMAIL PROTECTED]>: |> Do they say the buzzing is consistent, or it comes and goes? | | I've not asked in any detail. What frequency of coming and going has | been reported? Are we talking seconds or minutes? Like Ole says when I started looking at it, by calling a landline in the same room and listening to its receiver lying on the desk, it varied tremendously and not in a repeatable way. Eg, it appeared to vary by orientation of the phone, but when I traced the path backwards, the buzz did not return. Also, I had to keep whistling during this to provoke transmission actions that seem to be the start of the issue. Next I am gonna try rubbing my tummy at the same time :-O Maybe a bag of frozen peas on my head :-O - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiYMV4ACgkQOjLpvpq7dMpyxwCdFiK1KB3faqXMokVh0rCH6MK4 A1EAn0cTwP2ZEifuLIdMpRPrBZ55lZGP =Nar7 -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Buzzing sound
2008/8/5 Andy Green <[EMAIL PROTECTED]>: > Do they say the buzzing is consistent, or it comes and goes? I've not asked in any detail. What frequency of coming and going has been reported? Are we talking seconds or minutes? Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Buzzing sound
On Tue, Aug 05, 2008 at 11:25:56AM +0100, Andy Green wrote: > Somebody in the thread at some point said: > | 2008/8/5 Joerg Reisenweber <[EMAIL PROTECTED]>: > |> Only thing you may try for now is changing GSM-provider, as it seems > to be > |> very clear the issue is to be found on some GSM-networks, and not (or > less) > |> on some others. Generally the 1800/1900 networks seem to be more > likely to > |> cause this problem than the 850/900 networks. For Germany I got reports f > |> noise only for E+ network (and resellers) > | > | My experience on Blau (E+) is that I hear the caller excellently - but > | the caller complains that buzzing is very bad. > > Do they say the buzzing is consistent, or it comes and goes? For me using Simyo (E+) the far-end buzzing is consistent as long as the phone lies still. It varies depending on: - where you touch the phone - in which orientation you hold it - whether you move around with the phone BTW: Near-end buzzing I think is dependent on alsamixer. At least I had images with only far-end buzzing. pgp4aTcc6w22w.pgp Description: PGP signature ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Buzzing sound
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | 2008/8/5 Joerg Reisenweber <[EMAIL PROTECTED]>: |> Only thing you may try for now is changing GSM-provider, as it seems to be |> very clear the issue is to be found on some GSM-networks, and not (or less) |> on some others. Generally the 1800/1900 networks seem to be more likely to |> cause this problem than the 850/900 networks. For Germany I got reports f |> noise only for E+ network (and resellers) | | My experience on Blau (E+) is that I hear the caller excellently - but | the caller complains that buzzing is very bad. Do they say the buzzing is consistent, or it comes and goes? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiYKrQACgkQOjLpvpq7dMogwACfWP2yWOynrTBXpFmzK0q4cYES zCYAn0TCfUURl2/GpHwGTFMkANSzo2FI =1KrK -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Buzzing sound
2008/8/5 Joerg Reisenweber <[EMAIL PROTECTED]>: > Only thing you may try for now is changing GSM-provider, as it seems to be > very clear the issue is to be found on some GSM-networks, and not (or less) > on some others. Generally the 1800/1900 networks seem to be more likely to > cause this problem than the 850/900 networks. For Germany I got reports f > noise only for E+ network (and resellers) My experience on Blau (E+) is that I hear the caller excellently - but the caller complains that buzzing is very bad. > Hard to tell. We don't get sufficient number of reports, and due to nature of > reports nearly all are problem-reports, people without problems usually don't > post a report. I suggest, therefore, a wiki page where users are encouraged to document the line quality at both ends (good or bad) against their provider. Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Buzzing sound
Am Di 5. August 2008 schrieb Sebastien Nanchen: > > Hello, > > I played with my Freerunner for some days now. I am part of the users who > have the "buzzing sound" problem. I modified the sound configuration as described > in the wiki and was able to eradicate the echo (caller-side) and to make the low-level > voice volume (called-side) acceptable. Fine! :-) > But the buzzing sound stays and make the FR > unusable as a phone (I tried both OM 2007.2 and the latest image of Qtopia). The "GSM-buzz-noise" issue isn't related to image used. At least that's what we think of it at the moment. It's a hw-issue. (Please note we fixed other hw-issues by sw-patch - compare sd-card/GPS). Anyway there's no *bug* in any of the sw-stacks/images that causes this issue, so changing image won't help, until we eventually might find a sw-fix for the hw-issue. > > I know this was much discussed in the ML, and I'm sorry to come with this topic again, > but I haven't found any answer yet. There isn't any yet. My regret :.( > I would know if y missed some important information > about a tweak solving this issue? Only thing you may try for now is changing GSM-provider, as it seems to be very clear the issue is to be found on some GSM-networks, and not (or less) on some others. Generally the 1800/1900 networks seem to be more likely to cause this problem than the 850/900 networks. For Germany I got reports f noise only for E+ network (and resellers) > > If not, does somebody have an idea about how many users are experiencing the same > problem (10%, 30%, more?) Hard to tell. We don't get sufficient number of reports, and due to nature of reports nearly all are problem-reports, people without problems usually don't post a report. > > Is there any hope we can use our freed phone as a phone in a foreseeable future? See above... Investigation on issue continues. cheers jOERG signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Unable to install gpsd
sparky mat ??: > I am using today's build of 2007.2. > > When I do 'opkg install gpsd', I get the following error: > > Downloading > http://buildhost.automated.it/OM2007.2/packages/armv4t/gpsd_2.34-r9_armv4t.ipk > Collected errors: > * Packages were found, but none compatible with the architectures > configured > * Packages were found, but none compatible with the architectures > configured > * Packages were found, but none compatible with the architectures > configured > * Packages were found, but none compatible with the architectures > configured > * ERROR: Cannot satisfy the following dependencies for gpsd: > * gpsd-conf * > > > Any ideas? > http://buildhost.automated.it/ is not openmoko server , should be in openmoko/deploy/glibc/ipk/om-gta02/gpsd-conf_2.34-r9_om-gta02.ipk Tony Tu ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Opkg progress bar
sparky mat wrote: > Out of curiosity, what happened to the progress bar for each task in > opkg? I assume it must've been removed for good reason, just wondering > what that was. I believe the reason was that it used to use wget for downloading, which has itself a progress bar. But it uses libcurl now, which does not (out of the box). curl is of course the better choice. *g* -- Drucken Sie diese Mail bitte nur auf Recyclingpapier aus. Please print this mail only on recycled paper. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: USB networking in Ubuntu
Am Mo 4. August 2008 schrieb Olivier Berger: > 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, Maybe just adding the link by yourself would have been enough :-( My job is to fix your hw and create new one, not to supply links. C'mon encourage me to give such information in the future, when I come along. Best regards jOERG signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
ASU daily builds
Are ASU daily builds no longer available? None of the folders (at http://buildhost.openmoko.org/daily/freerunner/200808/ ) have any ASU jffs2 files. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Unable to install gpsd
I am using today's build of 2007.2. When I do 'opkg install gpsd', I get the following error: Downloading http://buildhost.automated.it/OM2007.2/packages/armv4t/gpsd_2.34-r9_armv4t.ipk Collected errors: * Packages were found, but none compatible with the architectures configured * Packages were found, but none compatible with the architectures configured * Packages were found, but none compatible with the architectures configured * Packages were found, but none compatible with the architectures configured * ERROR: Cannot satisfy the following dependencies for gpsd: * gpsd-conf * Any ideas? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Led light stay on after boot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Gta02v5 is the mass-production version. Yes that one is good for A6 too when they come. A6 is same as A5 except for very minor changes in components. | I took the plunge and flashed the 'fore mentioned u-boot. Boot seems | faster. And USB networking works now!! :-) Great. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiYAxwACgkQOjLpvpq7dMplrwCffdIpjQJI4VpmeANWA0oJhE7k PC4An1GQa7MvdMHY5AWyt5BBCNpG75j5 =wQHT -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Opkg progress bar
Out of curiosity, what happened to the progress bar for each task in opkg? I assume it must've been removed for good reason, just wondering what that was. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Led light stay on after boot
On Tue, Aug 5, 2008 at 12:52 PM, sparky mat <[EMAIL PROTECTED]> wrote: > On Tue, Aug 5, 2008 at 12:45 PM, sparky mat <[EMAIL PROTECTED]> wrote: > >> On Tue, Aug 5, 2008 at 12:38 PM, sparky mat <[EMAIL PROTECTED]> wrote: >> >>> Ever since I flashed the latest firmware from >>> http://buildhost.openmoko.org/daily/freerunner/200808/20080805/ , the >>> led light stays light after boot. >>> >>> The files I used are : >>> >>> http://buildhost.openmoko.org/daily/freerunner/200808/20080805/openmoko-openmoko-devel-image-glibc-ipk--20080805-om-gta02.rootfs.jffs2 >>> >>> http://buildhost.openmoko.org/daily/freerunner/200808/20080805/uImage-2.6.24+git27+1a95efdc23966343a3b432ceef2f6c24dc0e2052-r2-om-gta02.bin >>> >>> I have never updated my u-boot since I got the phone. Does this have >>> something to do with that? >>> >>> - sparkymat >>> >> >> Ok. Now USB networking is not working. Is flashing >> 'u-boot-gta02v5-1.3.1+gitr22+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb-r0.bin' >> gonna help? >> > > Why is there a gta02v2, v4 and a v5? How do I know which one I need? > Gta02v5 is the mass-production version. I took the plunge and flashed the 'fore mentioned u-boot. Boot seems faster. And USB networking works now!! :-) ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Buzzing sound
Hello, I played with my Freerunner for some days now. I am part of the users who have the "buzzing sound" problem. I modified the sound configuration as described in the wiki and was able to eradicate the echo (caller-side) and to make the low-level voice volume (called-side) acceptable. But the buzzing sound stays and make the FR unusable as a phone (I tried both OM 2007.2 and the latest image of Qtopia). I know this was much discussed in the ML, and I'm sorry to come with this topic again, but I haven't found any answer yet. I would know if y missed some important information about a tweak solving this issue? If not, does somebody have an idea about how many users are experiencing the same problem (10%, 30%, more?) Is there any hope we can use our freed phone as a phone in a foreseeable future? Thanks to anybody who can lessen my anguish ! Sébastien _ Windows Live Spaces – Votre vie, votre espace. Cliquez ici pour en savoir plus. http://get.live.com/spaces/overview___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Led light stay on after boot
On Tue, Aug 5, 2008 at 12:45 PM, sparky mat <[EMAIL PROTECTED]> wrote: > On Tue, Aug 5, 2008 at 12:38 PM, sparky mat <[EMAIL PROTECTED]> wrote: > >> Ever since I flashed the latest firmware from >> http://buildhost.openmoko.org/daily/freerunner/200808/20080805/ , the led >> light stays light after boot. >> >> The files I used are : >> >> http://buildhost.openmoko.org/daily/freerunner/200808/20080805/openmoko-openmoko-devel-image-glibc-ipk--20080805-om-gta02.rootfs.jffs2 >> >> http://buildhost.openmoko.org/daily/freerunner/200808/20080805/uImage-2.6.24+git27+1a95efdc23966343a3b432ceef2f6c24dc0e2052-r2-om-gta02.bin >> >> I have never updated my u-boot since I got the phone. Does this have >> something to do with that? >> >> - sparkymat >> > > Ok. Now USB networking is not working. Is flashing > 'u-boot-gta02v5-1.3.1+gitr22+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb-r0.bin' > gonna help? > Why is there a gta02v2, v4 and a v5? How do I know which one I need? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Led light stay on after boot
And what about USB networking? Do I need to do something to get it to work? Is it an optional module now that I have to install manually? (Thought I read something like that on the mailing list) On Tue, Aug 5, 2008 at 12:45 PM, Andy Green <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > | Ever since I flashed the latest firmware from > | http://buildhost.openmoko.org/daily/freerunner/200808/20080805/ , the > | led light stays light after boot. > | > | The files I used are : > | > > http://buildhost.openmoko.org/daily/freerunner/200808/20080805/openmoko-openmoko-devel-image-glibc-ipk--20080805-om-gta02.rootfs.jffs2 > | > > http://buildhost.openmoko.org/daily/freerunner/200808/20080805/uImage-2.6.24+git27+1a95efdc23966343a3b432ceef2f6c24dc0e2052-r2-om-gta02.bin > | > | I have never updated my u-boot since I got the phone. Does this have > | something to do with that? > > Yeah it indicates charging activity now. > > - -Andy > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org > > iEYEARECAAYFAkiX/gcACgkQOjLpvpq7dMocyQCfU3lQ936OXKUgJQn9HCmHstYX > cGkAn0ROh1rBAn3ht6DI+zE7F2+jAe/o > =dWnK > -END PGP SIGNATURE- > > ___ > 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: Led light stay on after boot
On Tue, Aug 5, 2008 at 12:38 PM, sparky mat <[EMAIL PROTECTED]> wrote: > Ever since I flashed the latest firmware from > http://buildhost.openmoko.org/daily/freerunner/200808/20080805/ , the led > light stays light after boot. > > The files I used are : > > http://buildhost.openmoko.org/daily/freerunner/200808/20080805/openmoko-openmoko-devel-image-glibc-ipk--20080805-om-gta02.rootfs.jffs2 > > http://buildhost.openmoko.org/daily/freerunner/200808/20080805/uImage-2.6.24+git27+1a95efdc23966343a3b432ceef2f6c24dc0e2052-r2-om-gta02.bin > > I have never updated my u-boot since I got the phone. Does this have > something to do with that? > > - sparkymat > Ok. Now USB networking is not working. Is flashing 'u-boot-gta02v5-1.3.1+gitr22+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb-r0.bin' gonna help? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Led light stay on after boot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Ever since I flashed the latest firmware from | http://buildhost.openmoko.org/daily/freerunner/200808/20080805/ , the | led light stays light after boot. | | The files I used are : | http://buildhost.openmoko.org/daily/freerunner/200808/20080805/openmoko-openmoko-devel-image-glibc-ipk--20080805-om-gta02.rootfs.jffs2 | http://buildhost.openmoko.org/daily/freerunner/200808/20080805/uImage-2.6.24+git27+1a95efdc23966343a3b432ceef2f6c24dc0e2052-r2-om-gta02.bin | | I have never updated my u-boot since I got the phone. Does this have | something to do with that? Yeah it indicates charging activity now. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiX/gcACgkQOjLpvpq7dMocyQCfU3lQ936OXKUgJQn9HCmHstYX cGkAn0ROh1rBAn3ht6DI+zE7F2+jAe/o =dWnK -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Led light stay on after boot
Ever since I flashed the latest firmware from http://buildhost.openmoko.org/daily/freerunner/200808/20080805/ , the led light stays light after boot. The files I used are : http://buildhost.openmoko.org/daily/freerunner/200808/20080805/openmoko-openmoko-devel-image-glibc-ipk--20080805-om-gta02.rootfs.jffs2 http://buildhost.openmoko.org/daily/freerunner/200808/20080805/uImage-2.6.24+git27+1a95efdc23966343a3b432ceef2f6c24dc0e2052-r2-om-gta02.bin I have never updated my u-boot since I got the phone. Does this have something to do with that? - sparkymat ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
