Re: OM2008.12 - basic usage instructions?
William Kenworthy wrote: Then the wiki needs to do something for people NOW. They buy a freerunner, see that the next version in the progression is 2008.12 and flash accordingly with the resulting questions here, and a really bad user experience - they are at where we were months ago - ready to throw the FR at a wall - HARD! I have to heartily second all your email. Based on my personal experience, when I got my FR, this is clearly the most crucial aspect to be fixed. At that time I considered to do some changes in the Wiki but I was deterred by: 1- the fact that someone had locked (with a banner msg) the page for editing 2- there were a lot of changes to be done, beyond my little free time, 3- I was not yet confident on my understanding of FR/Om2008.* 4- OM2008.12 was still too annoying to be able to do something effective/useful just by writing on the Wiki. Regards, Fernando Disclaimer: I haven't went back to check if the startup page(s) have improved since I'm using an older SHR unstable release. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] FSO unfunded?
Craig Woodward wrote: Thanks for taking the time and effort to find/post these threads. When most of this was happening I was unable to keep up with the lists and killed threads at a time. Slashdoted was not an attention getting subject for me. :( no problem So basically what I'm getting from that is half the staff are gone (or going), FR work is still back burner, and plan B is the new focus? Awesome. At least now I know where things are... In my understanding, FR work is still back burner, is misleading: a) FR-GTA02 will be improved with minor releases, I think both at hardware and om2009 distro, by OM; OM has stopped funding of FSO which is not to say FSO has stopped itself; b) FR-GTA03 is back burner by OM, but there is a new mailing list to to open development of GTA03 by the community, with support by Steve Mosher (but I'm not sure that means support from OM). Fernando ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [SHR-testing] where to get the 'nice' binary
2009/4/8 Konstantin chaosspaw...@gmx.net: Hi there, I hope someone can help me with that. I'd love to raise the nice-value of apps I start (for example mplayer), but I can't find the nice binary on SHR testing. Any hints as to where to get it? In Ubuntu/Debian, it's in the package coreutils, if that helps, but I didn't find a similar package in the SHR repositories... Start the mplayer thru a shellscript, like this: #!/bin/sh renice -20 $$ exec mplayer ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [SHR-testing] where to get the 'nice' binary
Joachim Ott wrote: 2009/4/8 Konstantin chaosspaw...@gmx.net: Hi there, I hope someone can help me with that. I'd love to raise the nice-value of apps I start (for example mplayer), but I can't find the nice binary on SHR testing. Any hints as to where to get it? In Ubuntu/Debian, it's in the package coreutils, if that helps, but I didn't find a similar package in the SHR repositories... Start the mplayer thru a shellscript, like this: #!/bin/sh renice -20 $$ exec mplayer Great, just what I was looking for! Thanks a lot! :) P.S.: I've put $1 after exec mplayer, because that way I can give a file to play as an argument. Works like a charm :D Regards, Konstantin ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [SHR-testing] where to get the 'nice' binary
Konstantin a écrit : P.S.: I've put $1 after exec mplayer, because that way I can give a file to play as an argument. Works like a charm :D Give $@ instead of $1 so you can have file(s) and argument(s) ! -- Christophe Badoit ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: No GSM. Suspect dead Calypso. What to do?
danek dan...@digsoc.com writes: - A couple of weeks later I contacted the list for suggestions. Someone suggested looking at the output of logread, which showed a +CME ERROR: 100 when trying to talk to the So do I understand it right, calypso answers to AT commands and is thus not completely dead? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: No GSM. Suspect dead Calypso. What to do?
Yes, I should clarify that... Calypso seems to be present, but will not register the GSM network no matter what. Calypso is dead for certain values of dead. I should add that when I tried to use GSM manually it would hang when trying to connect to the modem. (Logdump does show quite a bit of ATChat, so I admit I may not have been connecting to the modem properly, but I did try following a couple of different guides on the subject.) If you can make more sense of ATChat logs than I can (my knowledge of AT is small, and is limited to having dialed ISPs on POTS modems many years ago; I have no knowledge of GSM) please have a look at my trac ticket http://docs.openmoko.org/trac/ticket/2229 where I have attached a few different logs. Another possibility is that something is wrong with the antenna, but again, I don't know how to read AT well enough to tell if registration fails because of a problem with the modem (which I suspect, because it really did just die suddenly out of the blue -- it was sitting on a table doing nothing between the last time I used it and the first time I couldn't use it anymore) or because of lack of signal. -- View this message in context: http://n2.nabble.com/No-GSM.-Suspect-dead-Calypso.-What-to-do--tp2614421p2616000.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: No GSM. Suspect dead Calypso. What to do?
danek dan...@digsoc.com writes: Another possibility is that something is wrong with the antenna, but again, I don't know how to read AT well enough to tell if Dec 19 22:53:09 om-gta02 user.notice root: AtChat : W : %CSQ: 16, 99, 1 shows that the signal gsm signal is there so it is not an antenna problem. Please try to register to network manually with socat. First stop all processes that access ttySAC0 and then echo 0 /sys/devices/platform/neo1973-pm-gsm.0/power_on echo 1 /sys/devices/platform/neo1973-pm-gsm.0/power_on socat - file:/dev/ttySAC0,crtscts,crnl,b115200 and then type (mind your own pin instead of ) ATE1 AT+CFUN=1 AT+CPIN= AT+CPIN? AT+COPS AT+COPS? and tell us the output. Note that you might want to send those commands multiple times since calypso will go to sleep very fast and when it wakes up it won't handle the first command it receives. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: No GSM. Suspect dead Calypso. What to do?
Timo, Thanks for the tip. I just got home and tried this, and it worked much better than the methods I had tried before for talking to Calypso manually (cu would hang and not accept any AT commands IIRC), but unfortunately I was still unable to register. Of course I was using 2007.2 (or 2008.4, depending on what you call it) because the instructions I found were ancient. I did as you said: 1. Stop anything using the /dev/TTYSAC0 -- I was using Om2008.12, so as far as I knew, this was just qpe. I did killall qpe, then when the error popped up on the Neo screen I told it not to relaunch. Then, for good measure, I stopped xserver-nodm too. 2. Power cycle the GSM modem. 3. socat ... this was not installed by default. I managed to find the package at opkg.org, but it depended on libssl 0.9.8 and libcrypto 0.9.8. I couldn't find packages for either. Opkg update; opkg upgrade did nothing. I noticed that I had version 0.9.7 of both, and figured that talking to the Calypso shouldn't involve any kind of encryption anyway, so I decided to do an ugly hack and symlink the 0.9.7 SOs to 0.9.8 so I could install socat. I just now realized that I probably didn't have / couldn't get 0.9.8 because I installed stable, and should probably switch to testing or something else, so that I can try this again as intended. I'll do that after I send this message and report back (not expecting much to happen). 4. Since it took a while to get socat sorted, and I wasn't sure what you meant when you said Calypso goes to sleep very fast (goes to sleep after being powered on? in between commands? didn't know.) I figured it would be a good idea to power cycle the modem again. 5. OK, now we run socat with the parameters you gave: Neo: AT-Command Interpreter ready Me: ATE1 Neo: //nothing ... Me: ATE1 Neo: ATE1 OK Me: AT+CFUN=1 Neo: AT+CFUN=1 // pause for a couple of seconds ERROR // at this point, i don't know what has gone wrong, so I keep giving commands anyway... Me: AT+CPIN=4747 // i don't normally use a SIM pin, but i do like the number 47, so I set this SIM pin on my dumbphone. When I enter it when QPE asks me, it's happy. When I enter something else, it's not. So I'm assuming the Neo is working correctly with the PIN. Neo: AT+CPIN=4747 OK Me: AT+CPIN? Neo: AT+CPIN? +CPIN: READY OK Me: AT+COPS Neo: AT+COPS OK AT-Command Interpreter ready //It looks like it reset itself. I try dialing anyway... Me: ATD+1XXXYYY // this is a US telephone number, phone sitting next to me Neo: //hang... //hang... //hang... i try ATH anyway Me: ATH Neo: ATH OK //phone doesn't ring Since it gave me an error at AT+CFUN=1 before, I tried again, just pasting AT+CFUN=1 over and over again, but it kept saying ERROR, whatever that error is. I didn't know what AT+CFUN=1 did, so I looked up Hardware:AT_Commands in the wiki and saw that AT+CFUN=1 sets the modem to phone mode. I saw that AT+CFUN? could be used to query what mode the modem was operating in, so I initialized the modem again and did AT?CFUN? and got +CFUN: 0 So if I understand what is happening correctly (and I might not, because this is my first time talking directly to a GSM device) it seems that the modem never goes into phone mode. Is there anything else you would try at this point? Thanks again, Daniel -- View this message in context: http://n2.nabble.com/No-GSM.-Suspect-dead-Calypso.-What-to-do--tp2614421p2619428.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: No GSM. Suspect dead Calypso. What to do?
OK, I just flashed the latest daily image from unstable so that I could test again, using socat with the correct versions of libssl and libcrypto. First let me say I'm very impressed with the great work being done with the software since I last used the phone... Anyway, an interesting thing happened when I tried to use socat. I booted the phone, made sure zhone wasn't running, power cycled the modem, installed and ran socat... what started happening is that the modem kept repeatedly saying OK OK OK... etc ad infinitum. Then I realized I hadn't installed the modules when I flashed the kernel and rootfs. I did this and repeated the procedure, and got the same results as I did when I was running Om2008.12 with socat linked with the wrong versions of libssl and libcrypto, which was more or less what I expected. -- View this message in context: http://n2.nabble.com/No-GSM.-Suspect-dead-Calypso.-What-to-do--tp2614421p2619601.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
