Re: shr - messages + wsod

2009-05-06 Thread Tony Berth
On Wed, May 6, 2009 at 12:38 PM, Nelson Castillo
wrote:

> On Wed, May 6, 2009 at 4:19 AM, Tony Berth 
> wrote:
> (cut)
> >> It seems that I've found the way to avoid WSOD. If is somehow connected
> >> with the backlight of the display. If you live it at 100% the WSOD will
> >> not happen.
> >>
> >
> > just did a test with the latest builds but WSOD is still an issue :(
>
> It has been reported it will not happen with Qi.
>
>
I did install Qi prior to that!

Thanks

Tony
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: shr - messages + wsod

2009-05-06 Thread Nelson Castillo
On Wed, May 6, 2009 at 4:19 AM, Tony Berth  wrote:
(cut)
>> It seems that I've found the way to avoid WSOD. If is somehow connected
>> with the backlight of the display. If you live it at 100% the WSOD will
>> not happen.
>>
>
> just did a test with the latest builds but WSOD is still an issue :(

It has been reported it will not happen with Qi.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: shr - messages + wsod

2009-05-06 Thread Tony Berth
On Tue, May 5, 2009 at 9:03 PM, ivvmm  wrote:

> ivvmm wrote:
> > Pietro "m0nt0" Montorfano wrote:
> >> Il giorno mar, 21/04/2009 alle 22.30 +0400, ivvmm ha scritto:
> >>> Pietro Montorfano wrote:
>  just get back to the old 2.6.29-r2 kernel and then wsod
>  will go away.
> >>> How can this be achieved? The WSOD is really getting on my nerves.
> >> Quite simple but "dirty":
> >> 1) download a tar.gz version of shr which was running and the uImage,
> >> let's say the one built on 10th of april, before the big upgrade.
> >> 2) get the /lib/modules/2.6.29-r2 dir out of the tar.gz
> >> 3) copy it to your FR with scp, obviously it should be in /lib/modules
> >> 4) run "depmod -ae" from your FR
> >> 5a) if you are using the flash, use dfu-util to flash the kernel
> >> 5b) if you are using the uSD, copy the uImage in the right place
> >>
> >> There are other ways like using opkg or something similar but, hey, this
> >> is simple and it's working :D
> >>
> >> Bye!
> >>
> >> Pietro
> >>
> >>
> >
> > Thank you for the solution. But why just SHR developers do not revert
> > the kernel packages in testing and leave newer in unstable?
> >
> >
>
> It seems that I've found the way to avoid WSOD. If is somehow connected
> with the backlight of the display. If you live it at 100% the WSOD will
> not happen.
>
>
just did a test with the latest builds but WSOD is still an issue :(

Thanks

Tony
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: shr - messages + wsod

2009-05-05 Thread ivvmm
ivvmm wrote:
> Pietro "m0nt0" Montorfano wrote:
>> Il giorno mar, 21/04/2009 alle 22.30 +0400, ivvmm ha scritto:
>>> Pietro Montorfano wrote:
 just get back to the old 2.6.29-r2 kernel and then wsod
 will go away.
>>> How can this be achieved? The WSOD is really getting on my nerves.
>> Quite simple but "dirty":
>> 1) download a tar.gz version of shr which was running and the uImage,
>> let's say the one built on 10th of april, before the big upgrade.
>> 2) get the /lib/modules/2.6.29-r2 dir out of the tar.gz
>> 3) copy it to your FR with scp, obviously it should be in /lib/modules
>> 4) run "depmod -ae" from your FR
>> 5a) if you are using the flash, use dfu-util to flash the kernel
>> 5b) if you are using the uSD, copy the uImage in the right place
>>
>> There are other ways like using opkg or something similar but, hey, this
>> is simple and it's working :D
>>
>> Bye!
>>
>> Pietro
>>
>>
> 
> Thank you for the solution. But why just SHR developers do not revert
> the kernel packages in testing and leave newer in unstable?
> 
> 

It seems that I've found the way to avoid WSOD. If is somehow connected
with the backlight of the display. If you live it at 100% the WSOD will
not happen.



signature.asc
Description: OpenPGP digital signature
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: shr - messages + wsod

2009-04-22 Thread ivvmm
Pietro "m0nt0" Montorfano wrote:
> Il giorno mar, 21/04/2009 alle 22.30 +0400, ivvmm ha scritto:
>> Pietro Montorfano wrote:
>>> just get back to the old 2.6.29-r2 kernel and then wsod
>>> will go away.
>> How can this be achieved? The WSOD is really getting on my nerves.
> 
> Quite simple but "dirty":
> 1) download a tar.gz version of shr which was running and the uImage,
> let's say the one built on 10th of april, before the big upgrade.
> 2) get the /lib/modules/2.6.29-r2 dir out of the tar.gz
> 3) copy it to your FR with scp, obviously it should be in /lib/modules
> 4) run "depmod -ae" from your FR
> 5a) if you are using the flash, use dfu-util to flash the kernel
> 5b) if you are using the uSD, copy the uImage in the right place
> 
> There are other ways like using opkg or something similar but, hey, this
> is simple and it's working :D
> 
> Bye!
> 
> Pietro
> 
> 

Thank you for the solution. But why just SHR developers do not revert
the kernel packages in testing and leave newer in unstable?




signature.asc
Description: OpenPGP digital signature
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: shr - messages + wsod

2009-04-22 Thread Tony Berth
On Tue, Apr 21, 2009 at 11:27 PM, Pietro "m0nt0" Montorfano <
mont...@gmail.com> wrote:

> Il giorno mar, 21/04/2009 alle 22.30 +0400, ivvmm ha scritto:
> > Pietro Montorfano wrote:
> > > just get back to the old 2.6.29-r2 kernel and then wsod
> > > will go away.
> >
> > How can this be achieved? The WSOD is really getting on my nerves.
>
> Quite simple but "dirty":
> 1) download a tar.gz version of shr which was running and the uImage,
> let's say the one built on 10th of april, before the big upgrade.
> 2) get the /lib/modules/2.6.29-r2 dir out of the tar.gz
> 3) copy it to your FR with scp, obviously it should be in /lib/modules
> 4) run "depmod -ae" from your FR
> 5a) if you are using the flash, use dfu-util to flash the kernel
> 5b) if you are using the uSD, copy the uImage in the right place
>
> There are other ways like using opkg or something similar but, hey, this
> is simple and it's working :D
>
> Bye!
>
> Pietro
>


I don't know if the 'new' kernel (from the 21/4) was supposed to fix WSOD
but it didn't!

Thanks

Tony
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: shr - messages + wsod

2009-04-21 Thread Pietro "m0nt0" Montorfano
Il giorno mar, 21/04/2009 alle 22.30 +0400, ivvmm ha scritto:
> Pietro Montorfano wrote:
> > just get back to the old 2.6.29-r2 kernel and then wsod
> > will go away.
> 
> How can this be achieved? The WSOD is really getting on my nerves.

Quite simple but "dirty":
1) download a tar.gz version of shr which was running and the uImage,
let's say the one built on 10th of april, before the big upgrade.
2) get the /lib/modules/2.6.29-r2 dir out of the tar.gz
3) copy it to your FR with scp, obviously it should be in /lib/modules
4) run "depmod -ae" from your FR
5a) if you are using the flash, use dfu-util to flash the kernel
5b) if you are using the uSD, copy the uImage in the right place

There are other ways like using opkg or something similar but, hey, this
is simple and it's working :D

Bye!

Pietro


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: shr - messages + wsod

2009-04-21 Thread ivvmm
Pietro Montorfano wrote:
> just get back to the old 2.6.29-r2 kernel and then wsod
> will go away.

How can this be achieved? The WSOD is really getting on my nerves.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: shr - messages + wsod

2009-04-21 Thread Pietro Montorfano
Il giorno mar, 21/04/2009 alle 13.46 +0200, Petr Vanek ha scritto:
> >wsod is still there with the latest (19/04!) SHR unstable! It doesn't
> >happen immediately when you suspend. You have to wait a while :(
> 
> unfortunately i can confirm this... just not sure whether i have booted
> by NOR or Qi (i needed usb networking and this is not working with Qi on
> this image)
> 
> Petr

Yeah, wsod is back, Nicolas Dufresne is remaking the kernel module wich
handles the LCM sleep state, so, if someone is getting a better battery
life, someone (only if you are lucky like you and me :D) is still stuck
with the good old WSOD (i was missing it :D). It's not a problem, at
least for now, just get back to the old 2.6.29-r2 kernel and then wsod
will go away.
I think that Nicolas is doing a good job, let's hope that he could solve
the wsod problem with the new driver.

Bye!

Pietro


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: shr - messages + wsod

2009-04-21 Thread Petr Vanek
>wsod is still there with the latest (19/04!) SHR unstable! It doesn't
>happen immediately when you suspend. You have to wait a while :(

unfortunately i can confirm this... just not sure whether i have booted
by NOR or Qi (i needed usb networking and this is not working with Qi on
this image)

Petr


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: shr - messages + wsod

2009-04-21 Thread Yorick Moko
On Tue, Apr 21, 2009 at 11:22 AM, Tony Berth  wrote:
> On Fri, Apr 17, 2009 at 6:41 PM, Nelson Castillo 
> wrote:
>>
>> On Fri, Apr 17, 2009 at 7:51 AM, Tony Berth 
>> wrote:
>> > it is back :( I just tried with the latest image and kernel and WSOD is
>> > there!
> Also the 'key-lock' button doesn't work any more!

you have to bind the key manually
click on the wrench and take a look around

> Thanks
>
> Tony
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>
>

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: shr - messages + wsod

2009-04-21 Thread Tony Berth
On Fri, Apr 17, 2009 at 6:41 PM, Nelson Castillo
wrote:

> On Fri, Apr 17, 2009 at 7:51 AM, Tony Berth 
> wrote:
> > it is back :( I just tried with the latest image and kernel and WSOD is
> > there!
>
> I see. WSOD could be device specific. Could you try this kernel?
>
>
> http://wiki.emqbit.com/tmp/uImage-moredrivers-GTA02_andy-tracking-9c4451ff31b937a4.bin
>
> It doesn't include a recent patch that touches relevant timings.
>
>
> http://git.openmoko.org/?p=kernel.git;a=commit;h=bd4b7e8e84ab43a13a4620b001d52d373c2122b3
>
> Please let us know how it works for you.
>


wsod is still there with the latest (19/04!) SHR unstable! It doesn't happen
immediately when you suspend. You have to wait a while :(

Also the 'key-lock' button doesn't work any more!

Thanks

Tony
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: shr - messages + wsod

2009-04-19 Thread Vinzenz Hersche
how i said, the sms-app also crashed in newer versions if i want to read some 
sms. in the old testing-version, it was working.

i had now the trackback, hope, it help, to do something (i ha d no iea, but 
also no expirience in moko- & python-code)

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-
packages/framework/subsystems/ogsmd/gsm/channel.py", line 414, in 
handleResponseToRequest
ok_cb( reqstring.strip(), response )
  File "/usr/lib/python2.6/site-
packages/framework/subsystems/ogsmd/modems/abstract/mediator.py", line 999, in 
responseFromChannel
result.append( ( index, status, str(sms.addr), sms.ud, sms.properties ) )
  File "/usr/lib/python2.6/site-
packages/framework/subsystems/ogsmd/gsm/sms.py", line 471, in _getProperties
map.update( self._get_udh() )
  File "/usr/lib/python2.6/site-
packages/framework/subsystems/ogsmd/gsm/sms.py", line 326, in _get_udh
map["csm_id"] = self.udh[0][0]*256 + self.udh[0][1]
KeyError: 0

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: shr - messages + wsod

2009-04-18 Thread Johny Tenfinger
On Sat, Apr 18, 2009 at 18:07, Nelson Castillo
 wrote:
> In my attempts to reproduce the bug I missed the "let it cool down a
> little bit" step.

But it's the most important step I think ;)

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: shr - messages + wsod

2009-04-18 Thread Nelson Castillo
On Sat, Apr 18, 2009 at 11:02 AM, ivvmm  wrote:
> Nelson Castillo wrote:
>> On Fri, Apr 17, 2009 at 7:51 AM, Tony Berth  wrote:
>>> it is back :( I just tried with the latest image and kernel and WSOD is
>>> there!
>>
>> I see. WSOD could be device specific. Could you try this kernel?
>>
>> http://wiki.emqbit.com/tmp/uImage-moredrivers-GTA02_andy-tracking-9c4451ff31b937a4.bin
>>
>> It doesn't include a recent patch that touches relevant timings.
>>
>> http://git.openmoko.org/?p=kernel.git;a=commit;h=bd4b7e8e84ab43a13a4620b001d52d373c2122b3
>>
>> Please let us know how it works for you.
>>
>
> I assume it is not hardware related as I get it too.

Thanks a lot for the report.  The bug is now in trac:

https://docs.openmoko.org/trac/ticket/2274

In my attempts to reproduce the bug I missed the "let it cool down a
little bit" step.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: shr - messages + wsod

2009-04-18 Thread ivvmm
Nelson Castillo wrote:
> On Fri, Apr 17, 2009 at 7:51 AM, Tony Berth  wrote:
>> it is back :( I just tried with the latest image and kernel and WSOD is
>> there!
> 
> I see. WSOD could be device specific. Could you try this kernel?
> 
> http://wiki.emqbit.com/tmp/uImage-moredrivers-GTA02_andy-tracking-9c4451ff31b937a4.bin
> 
> It doesn't include a recent patch that touches relevant timings.
> 
> http://git.openmoko.org/?p=kernel.git;a=commit;h=bd4b7e8e84ab43a13a4620b001d52d373c2122b3
> 
> Please let us know how it works for you.
> 

I assume it is not hardware related as I get it too.

Also may provide additional information about it: it only blanks the
screen with white colour but the device is still responcible --- you can
still push buttons if your know where they are or just shutdown the
device in a normal way by holding the power button.

And it is very annoying.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: shr - messages + wsod

2009-04-17 Thread Nelson Castillo
On Fri, Apr 17, 2009 at 7:51 AM, Tony Berth  wrote:
> it is back :( I just tried with the latest image and kernel and WSOD is
> there!

I see. WSOD could be device specific. Could you try this kernel?

http://wiki.emqbit.com/tmp/uImage-moredrivers-GTA02_andy-tracking-9c4451ff31b937a4.bin

It doesn't include a recent patch that touches relevant timings.

http://git.openmoko.org/?p=kernel.git;a=commit;h=bd4b7e8e84ab43a13a4620b001d52d373c2122b3

Please let us know how it works for you.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: shr - messages + wsod

2009-04-17 Thread Tony Berth
it is back :( I just tried with the latest image and kernel and WSOD is
there!

Thanks

Tony


On Thu, Apr 16, 2009 at 11:15 PM, Vinzenz Hersche  wrote:

> hey nelson,
>
> yes, i'm shure.. it's not a lot, but sometimes it appears.. :/
> there was also a mail in the mailing list, called "wsod is back" with the
> same
> expiriences.. think, it was before 2 weeks..
>
> hope, in the stable release, wsod is dead forever :)
>
> greets
>
> On Donnerstag 16 April 2009 17:58:44 Nelson Castillo wrote:
> > Hello Vinzenz. Are you sure about the WSOD?
> >
> > I just tested the latest GTA02 kernel with SHR unstable and
> > suspend/resume worked as expected.
> >
> > openmoko-shr-lite-image-glibc-ipk--20090414-om-gta02.rootfs.jffs2
> >
> > Nelson.-
> >
>
>
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: shr - messages + wsod

2009-04-16 Thread Vinzenz Hersche
hey nelson,

yes, i'm shure.. it's not a lot, but sometimes it appears.. :/
there was also a mail in the mailing list, called "wsod is back" with the same 
expiriences.. think, it was before 2 weeks..

hope, in the stable release, wsod is dead forever :)

greets

On Donnerstag 16 April 2009 17:58:44 Nelson Castillo wrote:
> Hello Vinzenz. Are you sure about the WSOD?
>
> I just tested the latest GTA02 kernel with SHR unstable and
> suspend/resume worked as expected.
>
> openmoko-shr-lite-image-glibc-ipk--20090414-om-gta02.rootfs.jffs2
>
> Nelson.-
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: shr - messages + wsod

2009-04-16 Thread Nelson Castillo
On Thu, Apr 16, 2009 at 4:51 AM, Vinzenz Hersche  wrote:
> hello there,
> i saw, the shr-team isn't work fast in the last weeks.. :s (most commits are 3
> weeks or older)
> i'm now interested, when the first stable-version would be released. now, 
> there
> is also the wsod back and the sms-application crashes when it should loading(
> the sms (works in testing but not in unstable)..

Hello Vinzenz. Are you sure about the WSOD?

I just tested the latest GTA02 kernel with SHR unstable and
suspend/resume worked as expected.

openmoko-shr-lite-image-glibc-ipk--20090414-om-gta02.rootfs.jffs2

Nelson.-

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


shr - messages + wsod

2009-04-16 Thread Vinzenz Hersche
hello there,
i saw, the shr-team isn't work fast in the last weeks.. :s (most commits are 3 
weeks or older)
i'm now interested, when the first stable-version would be released. now, there 
is also the wsod back and the sms-application crashes when it should loading 
the sms (works in testing but not in unstable)..

so, is there a long way to make it stable or are problems like this fixed fast?

hope, we could work in near time with shr :)

greets


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community