[Gta04-owner] [QtMoko] Problem booting on GTA02

"Benedikt Bär | Relamp.tk" beniwtv at relamp.tk
Tue Oct 16 11:49:32 CEST 2012


On 10/16/2012 11:33 AM, "Benedikt Bär | Relamp.tk" wrote:
> Hi,
>
> This is the output:
>
> NeoKbdDriverPlugin:create()
> Before call NeoKbdHandler()
> 56223 0
> QDBusObjectPath: invalid path ""
> Method call  "/->DefaultAdapter()"  failed: 
> QDBusError("org.bluez.Error.NoSuchAdapter", "No such adapter")
> QDBusObjectPath: invalid path ""
> Method call  "/->DefaultAdapter()"  failed: 
> QDBusError("org.bluez.Error.NoSuchAdapter", "No such adapter")
> QDBusObjectPath: invalid path ""
> Method call  "/->DefaultAdapter()"  failed: 
> QDBusError("org.bluez.Error.NoSuchAdapter", "No such adapter")
> QDBusObjectPath: invalid path ""
> Method call  "/->DefaultAdapter()"  failed: 
> QDBusError("org.bluez.Error.NoSuchAdapter", "No such adapter")
> QDBusObjectPath: invalid path ""
> Method call  "/->DefaultAdapter()"  failed: 
> QDBusError("org.bluez.Error.NoSuchAdapter", "No such adapter")
> QDBusObjectPath: invalid path ""
> Method call  "/->DefaultAdapter()"  failed: 
> QDBusError("org.bluez.Error.NoSuchAdapter", "No such adapter")
> QDBusObjectPath: invalid path ""
> Method call  "/->DefaultAdapter()"  failed: 
> QDBusError("org.bluez.Error.NoSuchAdapter", "No such adapter")
> 0
> QDBusObjectPath: invalid path ""
> Method call  "/->DefaultAdapter()"  failed: 
> QDBusError("org.bluez.Error.NoSuchAdapter", "No such adapter")
> Segmentation fault
>
> Then the same repeats over and over again...
> Seems it is segfaulting somewhere.
>
> Thanks,
> Ben
>
> On 10/16/2012 11:20 AM, Gilles Filippini wrote:
>> Hi,
>>
>> ----- Mail original -----
>>> De: "Benedikt Bär | Relamp.tk" <beniwtv at relamp.tk>
>>>
>>> I recently installed QtMoko v48 on my Freerunner (in NAND), but it
>>> does
>>> not seem to boot.
>>>
>>> The first time I booted it went OK, there was a calibration and time
>>> settings screen. When I finished, it seemed to restart QtExtended and
>>> there the problems began.
>>>
>>> I now get to a screen with the white clock displaying, but then it
>>> appears to crash and the blinking cursor appears again. Then the
>>> white
>>> clock appears again and the same process starts over.
>>>
>>> I have left it a few minutes doing this, but it does not boot.
>>>
>>> Any ideas on how to debug this?
>>  From what I understand the Freerunner does boot but QtMoko fails to 
>> launch. You can try to SSH into the FreeRunner, and from there :
>> 1- stop the qtmoko service
>> # invoke-rc.d qtmoko-neo stop
>>
>> 2- launch it by hand
>> # . /opt/qtmoko/qpe.env
>> # /opt/qtmoko/qpe.sh
>>
>> 3- Watch the messages in the console.
>>
>> Thanks,
>>
>> _g.

Hi again,

So I did a /etc/init.d/bluetooth stop and now QtMoko starts...

I tried enabling the bluetooth chip manually, (via 
http://wiki.openmoko.org/wiki/Manually_using_Bluetooth), but it seems 
the chip doesn't power up.

Investigating that now...

Ben

>> _______________________________________________
>> Gta04-owner mailing list
>> Gta04-owner at goldelico.com
>> http://lists.goldelico.com/mailman/listinfo/gta04-owner
>
> _______________________________________________
> Gta04-owner mailing list
> Gta04-owner at goldelico.com
> http://lists.goldelico.com/mailman/listinfo/gta04-owner



More information about the Gta04-owner mailing list