Gentoo Archives: gentoo-embedded

From: Christoph Spielmann <spielc@×××××.com>
To: gentoo-embedded@l.g.o
Subject: Re: [gentoo-embedded] Openmoko - Almost there...
Date: Wed, 04 Mar 2009 20:58:23
Message-Id: 49AEEB3C.4090609@gmail.com
In Reply to: Re: [gentoo-embedded] Openmoko - Almost there... by Alon Bar-Lev
1 Hi!
2
3 Alon Bar-Lev wrote:
4 > On Wed, Mar 4, 2009 at 9:44 AM, Christoph Spielmann<spielc@×××××.com> wrote:
5 >
6 >> Sorry but in order to help you solve this problem i need more info. How do
7 >> you start ophonekitd? What version of frameworkd are you using? Is
8 >> frameworkd running? Is dbus running? And I need the exact output you get
9 >> from ophonekitd of course! Another thing you could try: What happens if you
10 >> disable pin? In my case i had problems with pin enabled but as soon as i
11 >> removed pin-lock everything worked like a charm. I know this is not a
12 >> solution for the problem but maybe your problem is connected to this
13 >>
14 >
15 > Sure...
16 > 1. I think dbus needs to start this, right? Anyway, I start it via the
17 > settings/GSM
18 >
19 Nope dbus starts gsm0710muxd (or should start). Ophonekitd has to be
20 started with a script. Or manually by calling ophonekitd.
21 freesmartphone-framework has to be started with the provided
22 init-script. And if you have the correct settings GSM-subsystem should
23 be started automatically. Could you send me the log of frameworkd too
24 please?
25 > menu. Is there a better way?
26 > 2. dbus is running.
27 > 3. versions:
28 > frameworkd-phonegui-20090127
29 > frameworkd-phonegui-efl-20090127
30 > freesmartphone-framework-0.4
31 > gsm0710muxd-0.9.2.2
32 > libframeworkd-glib-20090125
33 > openmoko-contacts3-20090125
34 > openmoko-dialer3-20090125
35 > openmoko-messages3-20090125
36 > ophonekitd-20090127
37 > pyphonelog-20090214
38 > shr-settings-20090214
39 >
40 Looks okey
41 > 4. Output of stdout:
42 > ---
43 > from pythonwifi.iwlibs import Wireless, getNICnames import error - not present
44 > displayModulesWin 1
45 > displayModulesWin 2
46 > loading<class 'shr_settings_modules.shr_gsm.Gsm'>
47 > GSM view [info] can't connect to dbus
48 > Unknown HZ value! (93) Assume 100.
49 > loading<class 'shr_settings_modules.shr_sim.Sim'>
50 > SimMstateContener can connect to dbus
51 > 3
52 > sim dbus1
53 > 4
54 > 5
55 > module<class 'shr_settings_modules.shr_sim.Sim'> can't be loaded!
56 > displayModulesWin 3
57 > ---
58 > 5. ophonekitd.log
59 > ---
60 > ** (process:1894): DEBUG: Entering ecore loop
61 > ** (process:1894): DEBUG: Phonegui initiated
62 > ** (process:1894): DEBUG: Phonelog database initiated
63 > ** (process:1894): DEBUG: Entering glib main loop
64 > ** (process:1894): DEBUG: /org/shr/ophonekitd/Usage
65 > ** (process:1894): DEBUG: Trying to get the system bus
66 > ** (process:1894): DEBUG: Adding signals.
67 > ** (process:1894): DEBUG: Added sim AuthStatus.
68 > ** (process:1894): DEBUG: Added sim IncomingStoredMessage.
69 > ** (process:1894): DEBUG: Added call CallStatus.
70 > ** (process:1894): DEBUG: Added device Idle Notifier State.
71 > ** (process:1894): DEBUG: Added network IncomingUssd.
72 > ** (process:1894): DEBUG: Connected to the buses
73 > ** (process:1894): DEBUG: list_resources()
74 > ** (process:1894): DEBUG: list_resources_callback()
75 > ** (process:1894): DEBUG: Resource Bluetooth available
76 > ** (process:1894): DEBUG: Resource GSM available
77 > ** (process:1894): DEBUG: Request GSM resource
78 > ** (process:1894): DEBUG: Initiated elementary
79 > ** (process:1894): DEBUG: Initiated etk
80 > ** (process:1894): DEBUG: idle notifier state handler called, id 1
81 > ** (process:1894): DEBUG: idle notifier state handler called, id 2
82 > ** (process:1894): DEBUG: request_resource_callback()
83 > ** (process:1894): DEBUG: dbus not available, try again in 5s
84 > ** (process:1894): DEBUG: list_resources()
85 > ** (process:1894): DEBUG: list_resources_callback()
86 > ** (process:1894): DEBUG: Resource Bluetooth available
87 > ** (process:1894): DEBUG: Resource GSM available
88 > ** (process:1894): DEBUG: Request GSM resource
89 > ** (process:1894): DEBUG: request_resource_callback()
90 > ** (process:1894): DEBUG: request resource error, try again in 5s
91 >
92 > ** ERROR **: error: TODO org.freesmartphone.Usage.UserExists
93 > org.freesmartphone.Usage -6
94 > aborting...
95 > ---
96 > 6. If I disable PIN it behaves the same.
97 >
98 I think i've seen that one before but i can't remember what the problem
99 was and how it can be fixed.
100
101 can you try the following (with pin disabled):
102
103 1. remove frameworkd and everything else connected to openmoko-specific
104 stuff (gsm0710muxd, gpsd or fso-gpsd) from default runlevel (if you've
105 added it)
106 2. install mdbus (http://wiki.openmoko.org/wiki/OpenmokoFramework/mdbus)
107 2. reboot
108 3. log in again and check if gsm0710muxd is running
109 4. start frameworkd (you might have to wait a lil, because frameworkd
110 takes a bit to start up)
111 5. execute the following commands and post the output:
112
113 mdbus -s org.freesmartphone.frameworkd /org/freesmartphone/GSM/Device
114 org.freesmartphone.GSM.Device.GetInfo
115 mdbus -s org.freesmartphone.frameworkd /org/freesmartphone/GSM/Device
116 org.freesmartphone.GSM.SIM.GetSimInfo
117 > There is not much documentation for shr (or I could not find ones), does
118 > anyone know a good resource?
119 >
120 I'm afraid there is no such thing as good documentation about shr... I
121 made things work by using trial and error, reading mailing list archives
122 and look through the tickets. In my case most things work now (phone,
123 sms, suspend and resume...) Things i know that are not working are
124 pyphonelog which just displays garbage here and shr-settings is umm very
125 picky about what does and what doesn't work.
126
127 I hope i could enlighten you a lil!
128
129 Christoph
130 > Thank you for your help!
131 > Alon.
132 >
133 >
134 >

Replies

Subject Author
Re: [gentoo-embedded] Openmoko - Almost there... Alon Bar-Lev <alon.barlev@×××××.com>