Hi there! I am sorry for the delay, real life issues...
On Wed, 24 Jun 2009 05:09:28 +0200, Michael 'Mickey' Lauer wrote: > On Wednesday 24 June 2009 02:49:23 Luca Capello wrote: >> What a boot loader has to do with GSM firmware? > > GPIO setup of GSM is not done in the kernel, but the bootloader. If you miss > the proper GPIO setup, you can't talk to the modem. There were some versions > of U-Boot/Qi/Kernel that didn't take this into account, recent versions > should > not make a difference though. Thank you for the information, I think I would need to study a bit more computer science to better understand what you reported. The fact that this information is not present anywhere still stands. BTW, I forgot to say that with the FSO-milestone5.1 installed on NAND Zhone does not have any problem. And I boot that one with the NOR U-Boot, which is even older (i.e. never updated since I received the phone back in July 2008) than the one in NAND. So the problem seems to be specific to Debian... >> I remember that once GSM worked, but then it stopped again for whatever >> reason. Now I am back to my GTA02 and while I do not get anymore the >> error above it seems I experience D-Bus timeout errors: [...] >> debian-gta02:~# DISPLAY=:0.0 mdbus >> >> :1.0 >> :1.3 >> >> org.enlightenment.wm.service >> org.freedesktop.DBus > > Don't forget to submit -s to mdbus, if you want to inspect the session > bus. Silly me, thanks for the reminder. I tried with the new installation and everything was the same. However, `mdbus -s` shows all the fso tree, thus the problem should be somewhere else, since Zhone still fails to register to network. Soon after boot, Zhone cannot connect to the GSM and fails with the following error: ===== gsm ok: <Interface <ProxyObject wrapping <dbus._dbus.SystemBus (system) at 0x40355120> \ :1.12 /org/freesmartphone/GSM/Device at 0x4035b0d0> implementing \ 'org.freesmartphone.GSM.Network' at 0x4035b1f0> [....] failcount = 0 dbus_objectInitOK! Requesting resource list Requesting resource GSM INFO:root:entering init for buttons INFO:root:entering init for UsageInterface for gsm INFO:root:entering init for gsm INFO:root:entering init for wifi IDLE STATE = idle_dim error while requesting resource GSM (DBusException org.freedesktop.DBus.Error.NoReply: \ Did not receive a reply. Possible causes include: the remote application did not send \ a reply, the message bus security policy blocked the reply, the reply timeout expired, \ or the network connection was broken.) Requested resource GSM with error INFO:root:entering init for UsageInterface for gps INFO:root:entering init for brightness INFO:root:entering init for UsageInterface for bluetooth IDLE STATE = idle_prelock IDLE STATE = lock checking for unsent messages did not receive any unsent messages: org.freesmartphone.Resource.NotEnabled: Resource \ Device is not enabled, current status is 'enabling' IDLE STATE = suspend ===== If I kill that Zhone process and start a new one, however, everything works as expected. The solution I found is to add a `sleep 10` before Zhone is started by the ~/.xsession script, something similar to what I reported for openmoko-panel-plugin back in November 2008: http://lists.linuxtogo.org/pipermail/smartphones-userland/2008-November/000551.html I firstly tried with `sleep 5` with no success and I have no time to try to reduce the working value. Is this in any way related to the following comment, i.e. Zhone is fired up too quickly and frameworkd is not fully operational yet? http://trac.freesmartphone.org/ticket/383#comment:7 FWIW, the very same solution above does not work on my old Debian: if Zhone is started by ~/.xsession, it cannot register to network and it gets the D-Bus timeout error above, no matter how many seconds it is delayed :-( Thx, bye, Gismo / Luca
pgpsnjyoDVLKq.pgp
Description: PGP signature
_______________________________________________ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
