arne anka wrote:
> within normal operation (runlevel) phonefsod does not work predicatble.
> small changes in the phonefsod.conf made it stop entirely (w/o any useful
> info in the log despite DEBUG) and small changes in eg fsodeviced seemed
> to fix that ...
>
> what looks far more confusing
> note, that nothing else is printed when shutting down by doing init 2 --
> looks, like phonefsod freezes somehow?
it doesn't freeze -- it dies.
most recent log of phonefsod (last lines):
2010.01.23 14:07:40.886422 [phonefsod] DEBUG: _request_resource_callback()
2010.01.23 14:07:42.854920 [pho
> frameworkd and phonefsod are updated. So your next report would be
> based on git head ;)
ah, thanks!
however, it does not change the problem, below the output of a normal
startup (init 3).
note, that nothing else is printed when shutting down by doing init 2 --
looks, like phonefsod freeze
Hi,
frameworkd and phonefsod are updated. So your next report would be
based on git head ;)
-- Sebastian
signature.asc
Description: Digital signature
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/li
On Fri, Jan 22, 2010 at 10:55:38PM +0100, arne anka wrote:
> > only changed in opimd and a small fix for ogpsd since then.
> a link to the changelog?
http://git.freesmartphone.org/?p=framework.git;a=shortlog
-- Sebastian
signature.asc
Description: Digital signature
> only changed in opimd and a small fix for ogpsd since then.
a link to the changelog?
> This will most probably not fix your problem!
that's quite possible, i added the remark only i case the issue was
related to differences in frameworkd between the one debian uses and the
shr one (since s
On Fri, Jan 22, 2010 at 10:03:07PM +0100, arne anka wrote:
> > hmm, strange thing. This is exactly what we intend to do... retry to
> > access FSO until it appears on the scene... and then list the resources
> > and register GSM if it is there... if not, wait for the signal that the
> > GSM r
> hmm, strange thing. This is exactly what we intend to do... retry to
> access FSO until it appears on the scene... and then list the resources
> and register GSM if it is there... if not, wait for the signal that the
> GSM resource
> appeared.
well, that's what i thought.
i've seen two dif
Am Freitag 22 Januar 2010 18:52:58 schrieb arne anka:
> within normal operation (runlevel) phonefsod does not work predicatble.
> small changes in the phonefsod.conf made it stop entirely (w/o any useful
> info in the log despite DEBUG) and small changes in eg fsodeviced seemed
> to fix that ...
>
9 matches
Mail list logo
