From: Christoph Spielmann <spielc@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Openmoko - Almost there...
Date: Fri, 06 Mar 2009 20:11:02 +0100 [thread overview]
Message-ID: <49B17546.6020405@gmail.com> (raw)
In-Reply-To: <9e0cf0bf0903051410k1f399db1qe7a44e3ed3e95f1e@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4117 bytes --]
Hi!
Alon Bar-Lev wrote:
> On Wed, Mar 4, 2009 at 10:57 PM, Christoph Spielmann<spielc@gmail.com> wrote:
>
>> Sure...
>> 1. I think dbus needs to start this, right? Anyway, I start it via the
>> settings/GSM
>>
>> Nope dbus starts gsm0710muxd (or should start). Ophonekitd has to be started
>> with a script. Or manually by calling ophonekitd. freesmartphone-framework
>> has to be started with the provided init-script. And if you have the correct
>> settings GSM-subsystem should be started automatically. Could you send me
>> the log of frameworkd too please?
>>
>
> Attached.
>
>
>> I think i've seen that one before but i can't remember what the problem was
>> and how it can be fixed.
>>
>
> Hmmm....
>
>
>> can you try the following (with pin disabled):
>>
>> 1. remove frameworkd and everything else connected to openmoko-specific
>> stuff (gsm0710muxd, gpsd or fso-gpsd) from default runlevel (if you've added
>> it)
>> 2. install mdbus (http://wiki.openmoko.org/wiki/OpenmokoFramework/mdbus)
>> 2. reboot
>> 3. log in again and check if gsm0710muxd is running
>>
>
> Not running. What should run it other than the init.d script?
>
You shouldn't start it with the initscript. dbus should start
gsm0710muxd automatically. If it's not started automatically something
is wrong.
>
>> 4. start frameworkd (you might have to wait a lil, because frameworkd takes
>> a bit to start up)
>>
>
> OK.
>
>
>> 5. execute the following commands and post the output:
>>
>> mdbus -s org.freesmartphone.frameworkd /org/freesmartphone/GSM/Device
>> org.freesmartphone.GSM.Device.GetInfo
>> mdbus -s org.freesmartphone.frameworkd /org/freesmartphone/GSM/Device
>> org.freesmartphone.GSM.SIM.GetSimInfo
>>
>
> # mdbus -s org.freesmartphone.frameworkd
> /org/freesmartphone/GSM/Device org.freesmartphone.GSM.Device.GetInfo
> /org/freesmartphone/GSM/Device: GetInfo failed:
> org.freesmartphone.Resource.NotEnabled
> # mdbus -s org.freesmartphone.frameworkd
> /org/freesmartphone/GSM/Device org.freesmartphone.GSM.SIM.GetSimInfo
> /org/freesmartphone/GSM/Device: GetSimInfo failed:
> org.freesmartphone.Resource.NotEnabled
>
> Even if i start gsm0710muxd it stays this way, also if I power_on the device.
>
That's the problem. Again gsm0710mux should get started automatically.
If it's not started automatically by dbus you can do what you want and
you won't get it to work. Believe me i had the same problem. Do you have
the following file installed:
/usr/armv4tl-softfloat-linux-gnueabi/usr/share/dbus-1/system-services/org.pyneo.muxer.service?
Usually this file should get installed by gsm0710muxd. I "solved" the
problem by completely removing ALL python-packages (including python
itself), deleting /usr/armv4tl-softfloat-linux-gnueabi/usr/lib/python2.5
and reinstall everything. After this procedure everything was working as
expected.
>
>> There is not much documentation for shr (or I could not find ones), does
>> anyone know a good resource?
>>
>>
>> I'm afraid there is no such thing as good documentation about shr... I made
>> things work by using trial and error, reading mailing list archives and look
>> through the tickets. In my case most things work now (phone, sms, suspend
>> and resume...) Things i know that are not working are pyphonelog which just
>> displays garbage here and shr-settings is umm very picky about what does and
>> what doesn't work.
>>
>
> Thanks for your help!!!
> What are me other alternatives? If SHR does not work, is there any other
> solution I can use, maybe something simpler? zhone does not work either,
> guess it needs ophonekitd too.
>
Nope zhone needs just freesmartphone-framework and as that's not working
correctly zhone can't work. There are other alternatives (e.g. the stuff
provided by hackable:1 sounds interesting) but we concentrate on
freesmartphone-framework at the moment but feel free to try other stuff.
I guess nobody would complain about having alternatives.
> Thanks!
>
No problem. After all we are one big gentoo-family, aren't we ;)
Christoph
> Alon.
>
[-- Attachment #2: Type: text/html, Size: 5557 bytes --]
next prev parent reply other threads:[~2009-03-06 19:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 22:49 [gentoo-embedded] Openmoko - Almost there Alon Bar-Lev
2009-03-04 6:45 ` Sven Rebhan
2009-03-04 7:44 ` Christoph Spielmann
2009-03-04 19:54 ` Alon Bar-Lev
2009-03-04 20:57 ` Christoph Spielmann
2009-03-05 22:10 ` Alon Bar-Lev
2009-03-06 19:11 ` Christoph Spielmann [this message]
2009-03-06 19:37 ` Alon Bar-Lev
2009-03-06 19:44 ` Ned Ludd
2009-03-07 13:11 ` Sven Rebhan
2009-03-10 0:26 ` Alon Bar-Lev
2009-03-10 8:52 ` Sven Rebhan
2009-03-04 21:08 ` Ned Ludd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49B17546.6020405@gmail.com \
--to=spielc@gmail.com \
--cc=gentoo-embedded@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox