Re: fso-abyss docs anywhere? (Was: GSM errors after 1024 fix)
Hi, Michael 'Mickey' Lauer-2 wrote: > > Do you have anything else installed that > could compete with fso-abyss over the GSM resource? > Like what? I'm not all that clear about the multiplexing process. As far as I know I have only the latest version of shr-u installed with all the upgrades (and waiting for more :) I do have gsm0710muxd installed - but from what I see - only fso-abyss is started up in the log. I have attached the log where the phone registers to this mail. Will post the log where the modem doesn't register in a few hours - when I can use another phone instead. Thanks. [working] http://n2.nabble.com/file/n3857557/frameworkd.log frameworkd.log [not working] -- View this message in context: http://n2.nabble.com/GSM-errors-after-1024-fix-tp3827146p3857557.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fso-abyss docs anywhere? (Was: GSM errors after 1024 fix)
Framework not being able to open a new channel means fso-abyss is not able to register a channel with the multiplexer. That it only works 4 out of 5 times sounds like a race condition. Do you have anything else installed that could compete with fso-abyss over the GSM resource? :M: ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fso-abyss docs anywhere? (Was: GSM errors after 1024 fix)
Hi, Well, I got mr FR rechecked and it seems that the fix was applied fine. But - I still have this problem. About 4 out of 5 times my FR fails to register with the messages like 2009.10.15 07:29:57.870 ogsmd.modem.abstract ERRORcould not open channel MISC, retrying in 2 seconds 2009.10.15 07:29:57.880 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:30:11.55 ogsmd.modem.abstract ERRORcould not open channel UNSOL, retrying in 2 seconds 2009.10.15 07:30:11.65 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:30:24.375 ogsmd.modem.abstract ERRORcould not open channel CALL, retrying in 2 seconds 2009.10.15 07:30:24.502 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' and this continues with no registration. I need to restart and sometimes it registers fine. 1. Can someone tell me what this means? 2. I tried android's latest release and surprisingly, the modem registered fine immediately! Is this a new bug? :( I'm on roaming - if that makes any diff - but I'm surprised how fast the newer version of android boots up and registers (with a small r to indicate the roaming status)!! shr-u on the other hand takes 4 tries or so to register successfully. Seems to be a software prob in my opinion now - but I can't confirm that without more help. Mickey - can you shed some light on the error messages? -- View this message in context: http://n2.nabble.com/GSM-errors-after-1024-fix-tp3827146p3856574.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fso-abyss docs anywhere? (Was: GSM errors after 1024 fix)
On Mon, 19 Oct 2009 17:15:18 +0200 Michael 'Mickey' Lauer (M'L) wrote: >Am Montag, den 19.10.2009, 12:46 +0200 schrieb Petr Vanek: >> On Mon, 19 Oct 2009 01:50:51 -0400 >> David Ford (DF) wrote: >> >> >actually i was vague/misleading in what i wrote. what i would like >> >to see is for the end user to be notified in a friendly fashion. >> >like injecting a service message into opimd/sms buffer >> >> sounds like a good communication method for the future :), if the >> devs like it :)) > >I'm open for it. I find sending a dbus signal somewhat less intrusive >though... as everything, it would have to be configurable and well thought through :) is there a difference between a SMS message and another type of message? Also, could "a message" contain an attachment? i.e. bluetooth received file? or how about a link to the file... this would then be dependent on the ability of the viewer i guess... Petr ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fso-abyss docs anywhere? (Was: GSM errors after 1024 fix)
Am Montag, den 19.10.2009, 12:46 +0200 schrieb Petr Vanek: > On Mon, 19 Oct 2009 01:50:51 -0400 > David Ford (DF) wrote: > > >actually i was vague/misleading in what i wrote. what i would like to > >see is for the end user to be notified in a friendly fashion. like > >injecting a service message into opimd/sms buffer > > sounds like a good communication method for the future :), if the devs > like it :)) I'm open for it. I find sending a dbus signal somewhat less intrusive though... :M: ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fso-abyss docs anywhere? (Was: GSM errors after 1024 fix)
On Mon, 19 Oct 2009 01:50:51 -0400 David Ford (DF) wrote: >actually i was vague/misleading in what i wrote. what i would like to >see is for the end user to be notified in a friendly fashion. like >injecting a service message into opimd/sms buffer sounds like a good communication method for the future :), if the devs like it :)) Petr ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fso-abyss docs anywhere? (Was: GSM errors after 1024 fix)
actually i was vague/misleading in what i wrote. what i would like to see is for the end user to be notified in a friendly fashion. like injecting a service message into opimd/sms buffer Petr Vanek wrote: > It exists already. > > ...another way is to use frameworkd with ti_calypso_sleep_mode = > 'adaptive' and inspect the logs. Frameworkd will tell you, when a real > recamping exists. > > http://wiki.openmoko.org/wiki/1024#Bug_detection > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fso-abyss docs anywhere? (Was: GSM errors after 1024 fix)
On Mon, 19 Oct 2009 00:32:28 -0400 David Ford (DF) wrote: >can't we build in detection for that? > >Michael 'Mickey' Lauer wrote: >> (NB: This compact debug output form is not optimal for recognizing >> #1024 anyways, you should rather watch for CSQ and CREG messages. If >> CSQ suddenly drops to 99 and you get thrown out of the cell, then >> it's 100% clear you have #1024). >> It exists already. ...another way is to use frameworkd with ti_calypso_sleep_mode = 'adaptive' and inspect the logs. Frameworkd will tell you, when a real recamping exists. http://wiki.openmoko.org/wiki/1024#Bug_detection -- Petr ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fso-abyss docs anywhere? (Was: GSM errors after 1024 fix)
can't we build in detection for that? Michael 'Mickey' Lauer wrote: > (NB: This compact debug output form is not optimal for recognizing #1024 > anyways, you should rather watch for CSQ and CREG messages. If CSQ suddenly > drops to 99 and you get thrown out of the cell, then it's 100% clear you have > #1024). > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fso-abyss docs anywhere? (Was: GSM errors after 1024 fix)
>How did you ever get it to work in the first place? I noticed the > Debian > package appearing and installed it, but never found all of the required > documentation to actually use it: i don't remember exactly, but i think the only change was setting the muxer to fso-abyss in frameworkd.conf. > [snip] >> after several frameworkd restarts and two reboots i decided to revert to >> gsmwhtsitsnamemuxer, which seems to work far better > >Where 'far better' means crashes at the slightest provocation (such as > (trying to) ping across a GPRS connection). well, yeah. once a month i get a call -- and it happened, when using gsmwhatsitsnamemuxer. fr rang but i couldn't pick up :-( switched back to fso-abyss, which loses connection on resume -- no calls at all. for the time being i switched to shr-u, which i flashed last time my debian/fso broke. at least telephony is working so far. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fso-abyss docs anywhere? (Was: GSM errors after 1024 fix)
>Yes, just use frameworkd with ti_calypso_sleep_mode = 'adaptive' and >inspect the logs. Frameworkd will tell you, when a real recamping >exists. makes sense, thank you Petr ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fso-abyss docs anywhere? (Was: GSM errors after 1024 fix)
>How about this output: >[2009-10-18 13:37:02.701925] Signal : cid=9E4A, lac=17A2 >[2009-10-18 13:37:26.813505] Signal : cid=7149, lac=17A2 >[2009-10-18 13:41:22.576405] Signal : cid=9E4A, lac=17A2 >[2009-10-18 13:45:48.512750] Signal : cid=7149, lac=17A2 >[2009-10-18 13:49:10.453532] Signal : cid=9E4A, lac=17A2 No recamping either, just handovers. If there is a better way - script of determining whether the 1024 has been dealt with correctly, it would be helpful... Yes, just use frameworkd with ti_calypso_sleep_mode = 'adaptive' and inspect the logs. Frameworkd will tell you, when a real recamping exists. :M: ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fso-abyss docs anywhere? (Was: GSM errors after 1024 fix)
On 10/18/09, Petr Vanek wrote: >>> I get messages like >>>[2009-10-18 07:51:27.107655] Signal : cid=4E91, lac=006A >>>[2009-10-18 07:52:45.145288] Signal : cid=4E7B, lac=006A >>>[2009-10-18 07:53:18.218122] Signal : cid=4E91, lac=006A >>>... >>> So I guess my #1024 is not fixed :-( >> >>The three lines you quoted are not showing #1024. Again, frequent cell >>_handovers_ are perfectly normal. #1024 is about dropping out of a >>cell, then recamping into it, e.g. it looks like that: >> >>[2009-10-18 07:51:27.107655] Signal : cid=4E91, lac=006A >>[2009-10-18 07:52:45.145288] Signal : cid=4E91, lac=006A >>[2009-10-18 07:53:18.218122] Signal : cid=4E91, lac=006A >> >>(NB: This compact debug output form is not optimal for recognizing >>#1024 anyways, you should rather watch for CSQ and CREG messages. If >>CSQ suddenly drops to 99 and you get thrown out of the cell, then it's >>100% clear you have #1024). > > How about this output: > > [2009-10-18 13:37:02.701925] Signal : cid=9E4A, lac=17A2 > [2009-10-18 13:37:26.813505] Signal : cid=7149, lac=17A2 > [2009-10-18 13:41:22.576405] Signal : cid=9E4A, lac=17A2 > [2009-10-18 13:45:48.512750] Signal : cid=7149, lac=17A2 > [2009-10-18 13:49:10.453532] Signal : cid=9E4A, lac=17A2 > > If there is a better way - script of determining whether the 1024 has > been dealt with correctly, it would be helpful... > > thank you > > Petr Looks normally, not like #1024. -- Sebastian Krzyszkowiak dos ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fso-abyss docs anywhere? (Was: GSM errors after 1024 fix)
>> I get messages like >>[2009-10-18 07:51:27.107655] Signal : cid=4E91, lac=006A >>[2009-10-18 07:52:45.145288] Signal : cid=4E7B, lac=006A >>[2009-10-18 07:53:18.218122] Signal : cid=4E91, lac=006A >>... >> So I guess my #1024 is not fixed :-( > >The three lines you quoted are not showing #1024. Again, frequent cell >_handovers_ are perfectly normal. #1024 is about dropping out of a >cell, then recamping into it, e.g. it looks like that: > >[2009-10-18 07:51:27.107655] Signal : cid=4E91, lac=006A >[2009-10-18 07:52:45.145288] Signal : cid=4E91, lac=006A >[2009-10-18 07:53:18.218122] Signal : cid=4E91, lac=006A > >(NB: This compact debug output form is not optimal for recognizing >#1024 anyways, you should rather watch for CSQ and CREG messages. If >CSQ suddenly drops to 99 and you get thrown out of the cell, then it's >100% clear you have #1024). How about this output: [2009-10-18 13:37:02.701925] Signal : cid=9E4A, lac=17A2 [2009-10-18 13:37:26.813505] Signal : cid=7149, lac=17A2 [2009-10-18 13:41:22.576405] Signal : cid=9E4A, lac=17A2 [2009-10-18 13:45:48.512750] Signal : cid=7149, lac=17A2 [2009-10-18 13:49:10.453532] Signal : cid=9E4A, lac=17A2 If there is a better way - script of determining whether the 1024 has been dealt with correctly, it would be helpful... thank you Petr ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fso-abyss docs anywhere? (Was: GSM errors after 1024 fix)
>Hi, > I get messages like >[2009-10-18 07:51:27.107655] Signal : cid=4E91, lac=006A >[2009-10-18 07:52:45.145288] Signal : cid=4E7B, lac=006A >[2009-10-18 07:53:18.218122] Signal : cid=4E91, lac=006A >... > So I guess my #1024 is not fixed :-( The three lines you quoted are not showing #1024. Again, frequent cell _handovers_ are perfectly normal. #1024 is about dropping out of a cell, then recamping into it, e.g. it looks like that: [2009-10-18 07:51:27.107655] Signal : cid=4E91, lac=006A [2009-10-18 07:52:45.145288] Signal : cid=4E91, lac=006A [2009-10-18 07:53:18.218122] Signal : cid=4E91, lac=006A (NB: This compact debug output form is not optimal for recognizing #1024 anyways, you should rather watch for CSQ and CREG messages. If CSQ suddenly drops to 99 and you get thrown out of the cell, then it's 100% clear you have #1024). :M: ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fso-abyss docs anywhere? (Was: GSM errors after 1024 fix)
Hi, I get messages like [2009-10-18 07:51:27.107655] Signal : cid=4E91, lac=006A [2009-10-18 07:52:45.145288] Signal : cid=4E7B, lac=006A [2009-10-18 07:53:18.218122] Signal : cid=4E91, lac=006A ... So I guess my #1024 is not fixed :-( -- View this message in context: http://n2.nabble.com/GSM-errors-after-1024-fix-tp3827146p3842955.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fso-abyss docs anywhere? (Was: GSM errors after 1024 fix)
http://www.freesmartphone.org/index.php/Implementations/fso-abyss. :M: ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
fso-abyss docs anywhere? (Was: GSM errors after 1024 fix)
On Thu, Oct 15, 2009 at 12:48:50PM +0200, arne anka wrote: > try the other muxer, gsmwhatsitsname, instead. > to me it seems, fso-abyss has detoriated into almost unusability over the > last months. How did you ever get it to work in the first place? I noticed the Debian package appearing and installed it, but never found all of the required documentation to actually use it: 1) D-bus path. 2) D-bus destination. 3) D-bus this-third-thing-dbus-send-etc-needs-to-know. 4) The interface specification. [snip] > after several frameworkd restarts and two reboots i decided to revert to > gsmwhtsitsnamemuxer, which seems to work far better Where 'far better' means crashes at the slightest provocation (such as (trying to) ping across a GPRS connection). My only motivation for installing fso-abyss in the first place was to get multiplexed GPRS working (again - I think it did work back in December or January). :-( -- Rask Ingemann Lambertsen Danish law requires addresses in e-mail to be logged and stored for a year ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM errors after 1024 fix
Hi, Well, mine is working for now. I managed to reboot it to show android to a friend - and it registered both in android and in shr-u - after I 'thumped' it a few times ;-) It might be because of some loose connection - I intend getting it checked soon - just need some time from pending stuff. Definitely a hardware problem - unless 'organic' software starts responding to thumping too ;-) BTW - I did switch the modem to 'always' and there haven't been any updates to shr-u for a long time now - so the software is the same as before the buzz fix. Somehow, I can't seem to notice any significant increase in the battery standby time either. How do I check for the modem recamping? -- View this message in context: http://n2.nabble.com/GSM-errors-after-1024-fix-tp3827146p3833238.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM errors after 1024 fix
> Wow, that'd be quite an achiement considering that I didn't do any > development on it. Note that it still works flawlessly here. Perhaps > software these days starts to rot, just as organic material ;) well, debian's release cycle is somewhat detached from upstream. i don't know when you "did any development on it" last. i am perfectly open to any suggestion how to make it work again, but so far i am stuck -- and since the fr is my sole phone it has to work most of the day. tried two different frameworkd.conf, mine, so far working, and one posted on the list (smartphone-userland, iirc) said to be working well as well. the issues with fso-abyss remained regardless. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM errors after 1024 fix
Am Donnerstag, den 15.10.2009, 12:48 +0200 schrieb arne anka: > try the other muxer, gsmwhatsitsname, instead. > to me it seems, fso-abyss has detoriated into almost unusability over the > last months. Wow, that'd be quite an achiement considering that I didn't do any development on it. Note that it still works flawlessly here. Perhaps software these days starts to rot, just as organic material ;) :M: ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM errors after 1024 fix
have you changed the deep sleep mode setting? or have you done an opkg update after the fix? if yes can you revert back and check. also check if recamping has stopped after the fix - just to be sure the fix was ok. On 10/15/09, c_c wrote: > > > > rakshat wrote: >> >> Did u manage to register at all after the fix? Or the error started later? >> > Seems like I can register once in every 4/5 reboots. I'm registered now > after 5 reboots. > -- > View this message in context: > http://n2.nabble.com/GSM-errors-after-1024-fix-tp3827146p3827502.html > Sent from the Openmoko Community mailing list archive at Nabble.com. > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > -- -- Please use Firefox as your web browser. Its protects you from spyware and is also a very feature rich browser. www.firefox.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM errors after 1024 fix
try the other muxer, gsmwhatsitsname, instead. to me it seems, fso-abyss has detoriated into almost unusability over the last months. when is started with it, month ago, it worked flawlessly, after doing an update to a more recent version of fso in july/august, zhone had issues requesting the gsm once in a while. i updated to the latest fso packages of debian tuesday and zhone would not connect to fso at all -- something about not being able to enable gsm, gsm being in state enabling or to that effect. before, i could restart frameworkd and it worked, last resort was reboot. after several frameworkd restarts and two reboots i decided to revert to gsmwhtsitsnamemuxer, which seems to work far better (though with some minor flaws. connection to network is sometimes lost and i need to call twice to actually call). ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM errors after 1024 fix
rakshat wrote: > > Did u manage to register at all after the fix? Or the error started later? > Seems like I can register once in every 4/5 reboots. I'm registered now after 5 reboots. -- View this message in context: http://n2.nabble.com/GSM-errors-after-1024-fix-tp3827146p3827502.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM errors after 1024 fix
Did u manage to register at all after the fix? Or the error started later? On 10/15/09, c_c wrote: > > Hi, >Thought I'll start a new thread. > I got the buzz and 1024 fixes done at Delhi yesterday (thanks Zoheb and > Rakshat). But after a few restarts I'm facing this new problem - my modem > doesn't register and I get errors like :- > > 2009.10.15 07:29:37.114 frameworkd.resource INFO setting resource > status for GSM from enabled to disabling > 2009.10.15 07:29:38.235 frameworkd.resource INFO setting resource > status for GSM from disabling to disabled > 2009.10.15 07:29:38.395 ophoned.protocol INFO removing protocol GSM > 2009.10.15 07:29:43.927 frameworkd.resource INFO setting resource > status for GSM from disabled to enabling > 2009.10.15 07:29:43.948 ogsmd.channelINFO unknown>: Creating channel with timeout = 3600 seconds > 2009.10.15 07:29:43.996 ogsmd.channelINFO > : Creating channel with timeout = > 300 seconds > 2009.10.15 07:29:44.99 ogsmd.channelINFO unknown>: Creating channel with timeout = 300 seconds > 2009.10.15 07:29:44.149 ogsmd.modems.ti_calypso INFO Requesting new > channel from 'fso-abyss' > 2009.10.15 07:29:57.870 ogsmd.modem.abstract ERRORcould not open channel > MISC, retrying in 2 seconds > 2009.10.15 07:29:57.880 ogsmd.modems.ti_calypso INFO Requesting new > channel from 'fso-abyss' > 2009.10.15 07:30:11.55 ogsmd.modem.abstract ERRORcould not open channel > UNSOL, retrying in 2 seconds > 2009.10.15 07:30:11.65 ogsmd.modems.ti_calypso INFO Requesting new > channel from 'fso-abyss' > 2009.10.15 07:30:24.375 ogsmd.modem.abstract ERRORcould not open channel > CALL, retrying in 2 seconds > 2009.10.15 07:30:24.502 ogsmd.modems.ti_calypso INFO Requesting new > channel from 'fso-abyss' > 2009.10.15 07:30:37.700 ogsmd.modem.abstract ERRORcould not open channel > MISC, retrying in 2 seconds > 2009.10.15 07:30:37.710 ogsmd.modems.ti_calypso INFO Requesting new > channel from 'fso-abyss' > 2009.10.15 07:30:50.900 ogsmd.modem.abstract ERRORcould not open channel > UNSOL, retrying in 2 seconds > 2009.10.15 07:30:50.910 ogsmd.modems.ti_calypso INFO Requesting new > channel from 'fso-abyss' > 2009.10.15 07:31:04.100 ogsmd.modem.abstract ERRORcould not open channel > CALL, retrying in 2 seconds > 2009.10.15 07:31:04.109 ogsmd.modems.ti_calypso INFO Requesting new > channel from 'fso-abyss' > 2009.10.15 07:31:17.300 ogsmd.modem.abstract ERRORcould not open channel > MISC, retrying in 2 seconds > 2009.10.15 07:31:17.310 ogsmd.modems.ti_calypso INFO Requesting new > channel from 'fso-abyss' > 2009.10.15 07:31:30.485 ogsmd.modem.abstract ERRORcould not open channel > UNSOL, retrying in 2 seconds > 2009.10.15 07:31:30.495 ogsmd.modems.ti_calypso INFO Requesting new > channel from 'fso-abyss' > 2009.10.15 07:31:43.675 ogsmd.modem.abstract ERRORcould not open channel > CALL, retrying in 2 seconds > 2009.10.15 07:31:43.805 ogsmd.modems.ti_calypso INFO Requesting new > channel from 'fso-abyss' > 2009.10.15 07:31:56.985 ogsmd.modem.abstract ERRORcould not open channel > MISC, retrying in 2 seconds > 2009.10.15 07:31:56.997 ogsmd.modems.ti_calypso INFO Requesting new > channel from 'fso-abyss' > 2009.10.15 07:32:10.355 ogsmd.modem.abstract ERRORcould not open channel > UNSOL, retrying in 2 seconds > 2009.10.15 07:32:10.365 ogsmd.modems.ti_calypso INFO Requesting new > channel from 'fso-abyss' > 2009.10.15 07:32:23.540 ogsmd.modem.abstract ERROR could not open channel > CALL, retrying in 2 seconds > 2009.10.15 07:32:23.550 ogsmd.modems.ti_calypso INFO Requesting new > channel from 'fso-abyss' > > and so on > > Any ideas what the problem could be? What do MISC, UNSOL and CALL mean? > Thanks. > -- > View this message in context: > http://n2.nabble.com/GSM-errors-after-1024-fix-tp3827146p3827146.html > Sent from the Openmoko Community mailing list archive at Nabble.com. > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > -- -- Please use Firefox as your web browser. Its protects you from spyware and is also a very feature rich browser. www.firefox.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
GSM errors after 1024 fix
Hi, Thought I'll start a new thread. I got the buzz and 1024 fixes done at Delhi yesterday (thanks Zoheb and Rakshat). But after a few restarts I'm facing this new problem - my modem doesn't register and I get errors like :- 2009.10.15 07:29:37.114 frameworkd.resource INFO setting resource status for GSM from enabled to disabling 2009.10.15 07:29:38.235 frameworkd.resource INFO setting resource status for GSM from disabling to disabled 2009.10.15 07:29:38.395 ophoned.protocol INFO removing protocol GSM 2009.10.15 07:29:43.927 frameworkd.resource INFO setting resource status for GSM from disabled to enabling 2009.10.15 07:29:43.948 ogsmd.channelINFO : Creating channel with timeout = 3600 seconds 2009.10.15 07:29:43.996 ogsmd.channelINFO : Creating channel with timeout = 300 seconds 2009.10.15 07:29:44.99 ogsmd.channelINFO : Creating channel with timeout = 300 seconds 2009.10.15 07:29:44.149 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:29:57.870 ogsmd.modem.abstract ERRORcould not open channel MISC, retrying in 2 seconds 2009.10.15 07:29:57.880 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:30:11.55 ogsmd.modem.abstract ERRORcould not open channel UNSOL, retrying in 2 seconds 2009.10.15 07:30:11.65 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:30:24.375 ogsmd.modem.abstract ERRORcould not open channel CALL, retrying in 2 seconds 2009.10.15 07:30:24.502 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:30:37.700 ogsmd.modem.abstract ERRORcould not open channel MISC, retrying in 2 seconds 2009.10.15 07:30:37.710 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:30:50.900 ogsmd.modem.abstract ERRORcould not open channel UNSOL, retrying in 2 seconds 2009.10.15 07:30:50.910 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:31:04.100 ogsmd.modem.abstract ERRORcould not open channel CALL, retrying in 2 seconds 2009.10.15 07:31:04.109 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:31:17.300 ogsmd.modem.abstract ERRORcould not open channel MISC, retrying in 2 seconds 2009.10.15 07:31:17.310 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:31:30.485 ogsmd.modem.abstract ERRORcould not open channel UNSOL, retrying in 2 seconds 2009.10.15 07:31:30.495 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:31:43.675 ogsmd.modem.abstract ERRORcould not open channel CALL, retrying in 2 seconds 2009.10.15 07:31:43.805 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:31:56.985 ogsmd.modem.abstract ERRORcould not open channel MISC, retrying in 2 seconds 2009.10.15 07:31:56.997 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:32:10.355 ogsmd.modem.abstract ERRORcould not open channel UNSOL, retrying in 2 seconds 2009.10.15 07:32:10.365 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.10.15 07:32:23.540 ogsmd.modem.abstract ERRORcould not open channel CALL, retrying in 2 seconds 2009.10.15 07:32:23.550 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' and so on.... Any ideas what the problem could be? What do MISC, UNSOL and CALL mean? Thanks. -- View this message in context: http://n2.nabble.com/GSM-errors-after-1024-fix-tp3827146p3827146.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
