My guess about the WSOD
Hi, guys. I can attribute WS on boot and blank to changing version of compiler which builds kernel. Here, i have testing re: gcc_4.1.2gcc_4.4.6 2.6.34 kernel, configured for fb okWS on boot/unblank 2.6.32 shr kernel, configured for kms okWS on boot/unblank please, notice that something similar to unblank happens on rotation/mode change. but my kernels somehow lack of sound sound support (other kind of bug), all both shrs and .34, so they are unusable for daily usage (http://www.bsdmn.com/openmoko/glamo/242/shrkernel/) Gennady. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: My guess about the WSOD
On Friday, 23. July 2010 10:21:49 Helge Hafting wrote: > On 21. juli 2010 10:25, Petr Vanek wrote: > >> With the 2+4+2 qi, WSOD seems to happen more often. And curiously > >> enough, removing power (as in pulling the battery out), doesn't help. > >> It is then guaranteed to reboot into WSOD. Strange that the phone is > >> capable of keeping this state over poweroff - do qi and uboot write > >> state into flash? > >> > >> The solution is to boot into NOR flash, and then select "Poweroff" > >>from the menu. After that, I get a normal reboot without the WSOD. > >> Graphics indeed seems a bit faster with this qi. :-) I hope the WSOD > >> problems can be fixed in the kernel and/or the xserver. It happens > >> without this qi too - perhaps not as often. > > > > i can confirm exactly the same findings. as JaMa stated, perhaps this > > will help to find the cause of WS altogether... > > A WSOD was always a possibility. But in older images, it was rare. > I saw it occationally with duke nukem - Duke changes resolution and > orientation of the screen. > > The 2.6.32 kernel brought nice speedups. But WSODs happens now and then. > > The qi that changes glamo timing from 4+4+4 to 2+4+2 brings even more > speed, and much more WSOD trouble too. At least when combined with > 2.6.32, I haven't tried it with 2.6.29 or older kernels. > > It seems to me that the WSOD happen only when the display is turned on, > or the resolution and/or orientation is changed. > > So I guess the programming of resolution and/or orientation is > timing-sensitive. Existing code worked reasonably well with old kernels > and 4+4+4 timing. But speedups break it. > > Maybe someone with a compiler could try adding delays between hardware > operations in the modesetting code? (Preferably both the kernel > modesetting, and any screen-on operation the bootloader might do. And if > there is any modesetting left in Xorg these days.) Extra delays (or > longer delays) should compensate for unknown timing sensitivities in the > hardware. Maybe evn 1+4+2 timing can be used eventually. > > The video mode change is a rare operation - it won't matter much > if it gets slower. Not if graphics painting operations gets faster. :-) > > Helge Hafting I had tested qi with 2+4+2 and got heaps of WSOD on new SHR-U (2.6.32): about only every 3rd boot worked (screen was white from beginning otherwise) about every 2nd display lock caused WSOD With same qi I did not get any WSOD on my other installations on the same Freerunner (Android on SD and SHR-U old (2.6.29) in NAND). I switched back to "regular" qi and do not see "real" WSODs anymore, meaning that sometimes when dimming the screen turns white but comes back immediately. With 2+4+2 it sometimes came back after suspend (too bad if you have an app running requesting CPU and thus not being able to suspend). Christian ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
My guess about the WSOD
On 21. juli 2010 10:25, Petr Vanek wrote: >> With the 2+4+2 qi, WSOD seems to happen more often. And curiously >> enough, removing power (as in pulling the battery out), doesn't help. >> It is then guaranteed to reboot into WSOD. Strange that the phone is >> capable of keeping this state over poweroff - do qi and uboot write >> state into flash? >> >> The solution is to boot into NOR flash, and then select "Poweroff" >>from the menu. After that, I get a normal reboot without the WSOD. >> Graphics indeed seems a bit faster with this qi. :-) I hope the WSOD >> problems can be fixed in the kernel and/or the xserver. It happens >> without this qi too - perhaps not as often. > > i can confirm exactly the same findings. as JaMa stated, perhaps this > will help to find the cause of WS altogether... A WSOD was always a possibility. But in older images, it was rare. I saw it occationally with duke nukem - Duke changes resolution and orientation of the screen. The 2.6.32 kernel brought nice speedups. But WSODs happens now and then. The qi that changes glamo timing from 4+4+4 to 2+4+2 brings even more speed, and much more WSOD trouble too. At least when combined with 2.6.32, I haven't tried it with 2.6.29 or older kernels. It seems to me that the WSOD happen only when the display is turned on, or the resolution and/or orientation is changed. So I guess the programming of resolution and/or orientation is timing-sensitive. Existing code worked reasonably well with old kernels and 4+4+4 timing. But speedups break it. Maybe someone with a compiler could try adding delays between hardware operations in the modesetting code? (Preferably both the kernel modesetting, and any screen-on operation the bootloader might do. And if there is any modesetting left in Xorg these days.) Extra delays (or longer delays) should compensate for unknown timing sensitivities in the hardware. Maybe evn 1+4+2 timing can be used eventually. The video mode change is a rare operation - it won't matter much if it gets slower. Not if graphics painting operations gets faster. :-) Helge Hafting ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] QVGA and WSOD
Dne Čt 7. ledna 2010 20:34:04 Ole Kliemann napsal(a): > Thanks for the answer! > > At what point in the process do you start X? And how and when do you > tell X which resolution to use? QtMoko runs on framebuffer, so we dont start X. There is X compatibility layer, but IIRC nobody tried to run X in qvga there. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] QVGA and WSOD
On Wed, Jan 06, 2010 at 02:00:22PM +0100, Radek Polak wrote: > Ole Kliemann wrote: > > > with /etc/fb.modes as follows > > > > mode "240x320" > > geometry 240 320 240 320 16 > > timings 10 8 88 2 2 8 2 > > endmode > > > > Hi, i am using this setup together with: > > echo qvga-normal > /sys/bus/spi/devices/spi2.0/state > > mode "qvga" > geometry 480 640 480 1280 16 > timings 10 8 16 2 16 8 2 > rgba 5/11,6/5,5/0,0/0 > endmode > > Works for me quite good. I have this in my docs[1] > > [1] > http://github.com/radekp/qtmoko/blob/master/doc/txt/debian_rootfs_howto.txt Thanks for the answer! At what point in the process do you start X? And how and when do you tell X which resolution to use? pgpgTIwzkOTd7.pgp Description: PGP signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] QVGA and WSOD
On Sat, Jan 02, 2010 at 11:38:28PM +, Ole Kliemann wrote: > I figured it out this far: > > The problem is independent of X. If you stop the Xserver and do > > # echo "qvga-normal" > /sys/bus/spi/devices/spi2.0/state > # fbset 240x320 > > with /etc/fb.modes as follows > > mode "240x320" > geometry 240 320 240 320 16 > timings 10 8 88 2 2 8 2 > endmode > > then there is a high probability that the screen will fade to WSOD. This > is on latest shr-unstable. > > If I flash this kernel [1] from September, keeping the rootfs at latest > shr-unstable, the problem does not occur. > > You can then start X and have 240x320 resolution, suspend works without > problems. Just there are still some horizontal stripe like from bad > timings. What could be the right timings? > > I have so far encounter no problems from using the older kernel. > > [1] > http://buildhost.shr-project.org/shr-obsolete/images/om-gta02/uImage-2.6.29-oe11+gitr119844+a3587e4ed77974adfb057af261aaeea4022018e8-r3.5-om-gta02.bin > Problem remains with kernel-image-2.6.29-rc3_2.6.29-oe11+gitr119861+b90406de472c1aa5371ab593a2bb79136d5de658-r7.4_om-gta02.ipk from the unstable feed. Reflashing [1] fixes it again. pgpRxmnOTWr8i.pgp Description: PGP signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] QVGA and WSOD
I figured it out this far: The problem is independent of X. If you stop the Xserver and do # echo "qvga-normal" > /sys/bus/spi/devices/spi2.0/state # fbset 240x320 with /etc/fb.modes as follows mode "240x320" geometry 240 320 240 320 16 timings 10 8 88 2 2 8 2 endmode then there is a high probability that the screen will fade to WSOD. This is on latest shr-unstable. If I flash this kernel [1] from September, keeping the rootfs at latest shr-unstable, the problem does not occur. You can then start X and have 240x320 resolution, suspend works without problems. Just there are still some horizontal stripe like from bad timings. What could be the right timings? I have so far encounter no problems from using the older kernel. [1] http://buildhost.shr-project.org/shr-obsolete/images/om-gta02/uImage-2.6.29-oe11+gitr119844+a3587e4ed77974adfb057af261aaeea4022018e8-r3.5-om-gta02.bin pgp4BhiKbvEpK.pgp Description: PGP signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[SHR] QVGA and WSOD
Trying to switch resolution to 240x320 on shr-unstable or shr-testing I get the following problem. /etc/fb.modes is: mode "240x320" geometry 240 420 240 320 16 timings 10 8 88 2 2 8 2 accel false endmode With X running I do: # xrandr -s 240x320 # fbset 240x320 Now two things can happen. 1) the display works ok, just with some horizontal stripes. 2) the display fades to all white and stays like that. Case 2) can be easily produced by just calling # fbset 240x320 a second time, after the first call produced result 1). This almost always works. The screen can be all white after suspend/resume too. Sometime an all white screen can be fixed by suspend/resume. But the timings are back to previous state then and a call to fbset is inevitable. This mostly results in 2) again. When suspending/resuming sometimes there was the console visible before X got back. There was a repeated message, I think it was "glamofb cmd_queue never got empty" pgpg5Tp0LeWPv.pgp Description: PGP signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v9 and the WSOD
I only get it with Qi, never with u-boot. Using shr-u tho. BillK On Thu, 2009-09-17 at 21:05 +0200, Radek Polak wrote: > Pietro Montorfano wrote: > > > Hi, > > i gave a try to qtmoko v9, wow, impressive, very good work, it's fast > > and the others can hear me well when i call them but after a suspend > > there was a problem... the WSOD... > > a scream was heard near my home, that nightmare is back on my phone.. :D > > Well, pleas check the kernel, the patch is quite old and i think that > > the small number of people affected by that problem could enjoy that > > patch in your kernel. > > Hi Pietro, > for QtMoko i am using the latest andy-tracking kernel. Nothing better > currently exists as far as i know. You can try to use Qi. IIRC it does > not exhibit WSOD, while u-boot can. Someone correct me please if i am > wrong ;) > > Regards > > Radek > > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community -- William Kenworthy Home in Perth! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v9 and the WSOD
Pietro Montorfano wrote: > Hi, > i gave a try to qtmoko v9, wow, impressive, very good work, it's fast > and the others can hear me well when i call them but after a suspend > there was a problem... the WSOD... > a scream was heard near my home, that nightmare is back on my phone.. :D > Well, pleas check the kernel, the patch is quite old and i think that > the small number of people affected by that problem could enjoy that > patch in your kernel. Hi Pietro, for QtMoko i am using the latest andy-tracking kernel. Nothing better currently exists as far as i know. You can try to use Qi. IIRC it does not exhibit WSOD, while u-boot can. Someone correct me please if i am wrong ;) Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
QtMoko v9 and the WSOD
Hi, i gave a try to qtmoko v9, wow, impressive, very good work, it's fast and the others can hear me well when i call them but after a suspend there was a problem... the WSOD... a scream was heard near my home, that nightmare is back on my phone.. :D Well, pleas check the kernel, the patch is quite old and i think that the small number of people affected by that problem could enjoy that patch in your kernel. Thanks a lot Pietro ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Bug tracker (Was: WSOD)
On Tue, Sep 08, 2009 at 04:46:36PM +0200, Jens Seidel wrote: > If the latest andy-tracking kernel is no longer affected why > aren't both WSOD bug reports updated? I wasn't even aware until very > recently that the original WSOD bug was fixed as the initial report is still > open without activity since months. It is not generally possible to update bug reports in the OM bug tracker because the exact magic necessary to get permission to create bug reports or update existing ones isn't known. So you shouldn't put too much into seeing an open bug report with no activity for months. -- Rask Ingemann Lambertsen Danish law requires addresses in e-mail to be logged and stored for a year ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD (Was: Re: [SHR-Today] Accept call without unlocking)
On 9/8/09, Jens Seidel wrote: > On Tue, Sep 08, 2009 at 04:29:19PM +0200, Sebastian Krzyszkowiak wrote: >> On 9/8/09, Jens Seidel wrote: >> > Funny, it's opposite for me. I used until yesterday 2.6.29 together with >> > uboot but switched back to 2.6.28 and now the WSOD vanished. Great! >> > >> > With 2.6.29 WSOD happened very often (I would say in 50% of all cases). >> > Don't remember GSM status with 2.6.29 (works great with 2.6.28), used it >> > in the past mainly as PDA. >> >> BTW. Why are you playing with kernels instead of using ditribution >> one? > > A good question and I don't know the proper answer. I use SHR but have also > Debian installed. SHR is currently more stable and much fancier so I prefer > it. I often update the system via opkg update and opkg upgrade which > resulted > in kernel 2.6.29-rc3. > > Why should I keep it if it is unstable? And a very stupid question: I know > that 2.6.29-rc3 is installed in the file system (/boot) but is it used or > the kernel in /dev/mtdblock3? I didn't found the answer in the SHR manual > and wasted yesterday at least 3 hours because of it. I also checked the > uboot config, booted via USB serial connection started printenv, ... > That's not a easy way!!! I flashed finally directly into the "kernel" > partition which seems to work. So opkg doesn't affect the running kernel ... > > I know that Debian provided a script to customize the uboot configuration > and I know that the kernel in the filesystem is used and /dev/mtdblock3 > as fallback (or in reverse order, don't remember). But SHR? > > Digging into the Wiki and mailinglist postings is still the most time > consuming task and I'm always lost in it and not able to do any work with > my phone! > >> I understand playing with 2.6.31 RC kernels, but downgrading? > > I prefer a WSOD free kernel, you not? > >> SHR-unstable comes with latest andy-tracking. If something doesn't >> work in this kernel, then it has to be reported, debuged and fixed, >> instead of just switching back and being quiet about that! > > The problem in 2.6.29 is already known, there is no need to report it > so I tried to avoid it using 2.6.28 (which reports itself as > 2.6.29 :-)). If the latest andy-tracking kernel is no longer affected why > aren't both WSOD bug reports updated? I wasn't even aware until very > recently that the original WSOD bug was fixed as the initial report is still > open without activity since months. > > I now tried again at least ten minutes to find the SHR kernel download link > but failed, it's not on http://wiki.openmoko.org/wiki/Download, > http://wiki.openmoko.org/wiki/Flashing#Flashing_the_Kernel, > http://wiki.openmoko.org/wiki/SHR_User_Manual, wasn't able to find it via > Google, What a mess! At least I don't remember seeing anything andy-tracking > related (except the Wiki article about getting the source). > > Jens Kernel is in images and in repositiories. After opkg upgrade at /boot/uImage-GTA02 you should have latest kernel (even if it wasn't flashed by opkg) which you should use to flash if you want to test it. That kernel is supposed to be quite stable and usable. -- Sebastian Krzyszkowiak dos ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
WSOD (Was: Re: [SHR-Today] Accept call without unlocking)
On Tue, Sep 08, 2009 at 04:29:19PM +0200, Sebastian Krzyszkowiak wrote: > On 9/8/09, Jens Seidel wrote: > > Funny, it's opposite for me. I used until yesterday 2.6.29 together with > > uboot but switched back to 2.6.28 and now the WSOD vanished. Great! > > > > With 2.6.29 WSOD happened very often (I would say in 50% of all cases). > > Don't remember GSM status with 2.6.29 (works great with 2.6.28), used it > > in the past mainly as PDA. > > BTW. Why are you playing with kernels instead of using ditribution > one? A good question and I don't know the proper answer. I use SHR but have also Debian installed. SHR is currently more stable and much fancier so I prefer it. I often update the system via opkg update and opkg upgrade which resulted in kernel 2.6.29-rc3. Why should I keep it if it is unstable? And a very stupid question: I know that 2.6.29-rc3 is installed in the file system (/boot) but is it used or the kernel in /dev/mtdblock3? I didn't found the answer in the SHR manual and wasted yesterday at least 3 hours because of it. I also checked the uboot config, booted via USB serial connection started printenv, ... That's not a easy way!!! I flashed finally directly into the "kernel" partition which seems to work. So opkg doesn't affect the running kernel ... I know that Debian provided a script to customize the uboot configuration and I know that the kernel in the filesystem is used and /dev/mtdblock3 as fallback (or in reverse order, don't remember). But SHR? Digging into the Wiki and mailinglist postings is still the most time consuming task and I'm always lost in it and not able to do any work with my phone! > I understand playing with 2.6.31 RC kernels, but downgrading? I prefer a WSOD free kernel, you not? > SHR-unstable comes with latest andy-tracking. If something doesn't > work in this kernel, then it has to be reported, debuged and fixed, > instead of just switching back and being quiet about that! The problem in 2.6.29 is already known, there is no need to report it so I tried to avoid it using 2.6.28 (which reports itself as 2.6.29 :-)). If the latest andy-tracking kernel is no longer affected why aren't both WSOD bug reports updated? I wasn't even aware until very recently that the original WSOD bug was fixed as the initial report is still open without activity since months. I now tried again at least ten minutes to find the SHR kernel download link but failed, it's not on http://wiki.openmoko.org/wiki/Download, http://wiki.openmoko.org/wiki/Flashing#Flashing_the_Kernel, http://wiki.openmoko.org/wiki/SHR_User_Manual, wasn't able to find it via Google, What a mess! At least I don't remember seeing anything andy-tracking related (except the Wiki article about getting the source). Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Repair a dead Freerunner (was: Re: WSOD)
Hi! Just a thought I have bought a digital camera (Canon SX100IS) for 145 EUR, it fell off from a chair in a camera bag. The lcd screen broke. Repairing it (the warranty not cover such accident) would cost about 130EUR. So I bought a replacement LCD for 40USD on ebay. What I want to say with all this, that Freerunner got very cheap these days. You can have a brand new for 185EUR! Dunno where you are located, but I doubt if you can repair it under 100EUR (even if a tiny part is what only need to be replaced). FYI pulster.de offers LCD repair service. Best regards, Laszlo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Repair a dead Freerunner (was: Re: WSOD)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Does Openmoko or any other distribuitor offer a repair service? I mean, if the mainboard is dead, but the gps, the wifi, the screen and the case work, it might be cheaper to to get a new mainboard than to buy a new FR. I can send it anywhere if someone can tell for sure what is damaged, and offer a spare part to fix it. Kosa - - Un mundo mejor es posible - Philippe Lhardy escribió: >>> Well, it didn't work :( but I'm happy enough with the new one. If anyone >>> else knows if there's anything I can do with it, please let me know. >>> >>> Kosa >>> >>> - - Un mundo mejor es posible - >>> >>> >>> >> yes : >> - an ashtray >> - a mirror >> - a puck to play ShufflePuck Café with >> - ... >> > > If there is nothing to do to revive it, at lesat each sub piece can be > used to repair the other one > if something bad happens to it ... > I made repaired my openmoko and the new button i have come from a spare one... > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkqERqsACgkQmveDdjvKcqg+OwCgkP0h1ZH24kHQ6GbowLIzgBKl rv4AoIDAy7LmpBavrQsUdxwqleIfhz+Q =y2dz -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
>> >> Well, it didn't work :( but I'm happy enough with the new one. If anyone >> else knows if there's anything I can do with it, please let me know. >> >> Kosa >> >> - - Un mundo mejor es posible - >> >> >> > yes : > - an ashtray > - a mirror > - a puck to play ShufflePuck Café with > - ... > If there is nothing to do to revive it, at lesat each sub piece can be used to repair the other one if something bad happens to it ... I made repaired my openmoko and the new button i have come from a spare one... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
Kosa a écrit : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > >>>>>> Don't fear... It won't be damaged for only 1minute and in tap Water. >>>>>> Salted water (sea) can damage it. >>>>>> >>>>>> >>> Yes it can, My FR got dropped into the sea and it's dead. It still turns >>> on an I get a bright-white screen as the WSOD, and the wierd thing, it >>> still gets the charged, but I can't do nothing. I get no 'nor' nor nand. >>> >>> The good part, It happend two months ago and I just got a new one into >>> my office today, I'll picl it up tomorrow and I'll be happy again. >>> >> >>> A pretty stange thing... Yesterday evening I opened my moko to show to >>> some moko users the #1024 fix. I closed it, and WSOD ! It means : >>> no nand boot, no nor boot, only white screen but keep charging (red >>> power button) >>> I was a bit affraid of loosing my dear moko. I opened it agin, removing >>> Wifi module and >>> opening the GSM can (doing exactly what I did last night). Then I put >>> everything together, peacefully (I mean before my morning coffee), >>> blowing everywhere to remove some dust. (?) >>> Finally, I crossed my fingers, touch a rabbit leg, and pressed the power >>> button... Ta-da ! It booted again ... No more WSOD, a nice >>> BlackScreenWithConfusingWhiteText was rolling. >>> >>> If it can help someone. >>> >>> Thomas >>> > > Well, it didn't work :( but I'm happy enough with the new one. If anyone > else knows if there's anything I can do with it, please let me know. > > Kosa > > - - Un mundo mejor es posible - > > > yes : - an ashtray - a mirror - a puck to play ShufflePuck Café with - ... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >>>>> Don't fear... It won't be damaged for only 1minute and in tap Water. >>>>> Salted water (sea) can damage it. >>>>> >> Yes it can, My FR got dropped into the sea and it's dead. It still turns >> on an I get a bright-white screen as the WSOD, and the wierd thing, it >> still gets the charged, but I can't do nothing. I get no 'nor' nor nand. > >> The good part, It happend two months ago and I just got a new one into >> my office today, I'll picl it up tomorrow and I'll be happy again. > > >> A pretty stange thing... Yesterday evening I opened my moko to show to >> some moko users the #1024 fix. I closed it, and WSOD ! It means : >> no nand boot, no nor boot, only white screen but keep charging (red >> power button) >> I was a bit affraid of loosing my dear moko. I opened it agin, removing >> Wifi module and >> opening the GSM can (doing exactly what I did last night). Then I put >> everything together, peacefully (I mean before my morning coffee), >> blowing everywhere to remove some dust. (?) >> Finally, I crossed my fingers, touch a rabbit leg, and pressed the power >> button... Ta-da ! It booted again ... No more WSOD, a nice >> BlackScreenWithConfusingWhiteText was rolling. > >> If it can help someone. > >> Thomas > Well, it didn't work :( but I'm happy enough with the new one. If anyone else knows if there's anything I can do with it, please let me know. Kosa - - Un mundo mejor es posible - -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkqEKLEACgkQmveDdjvKcqh8QACfeVpGBqpx910IJYuScMVXn5W7 naAAoKhQNVKXCr7FZ9nA51em55cndkVr =hcLJ -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It might work... I'll try that tomorrow morining. I already have the new one right here on my desk, but I could use two of them to do lots of funny things :) I'll let you now :) Kosa - - Un mundo mejor es posible - Thomas HOCEDEZ escribió: > Kosa a écrit : > > >>>> Don't fear... It won't be damaged for only 1minute and in tap Water. >>>> Salted water (sea) can damage it. >>>> > Yes it can, My FR got dropped into the sea and it's dead. It still turns > on an I get a bright-white screen as the WSOD, and the wierd thing, it > still gets the charged, but I can't do nothing. I get no 'nor' nor nand. > > The good part, It happend two months ago and I just got a new one into > my office today, I'll picl it up tomorrow and I'll be happy again. > > > Kosa > > - Un mundo mejor es posible - >> ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community >> > A pretty stange thing... Yesterday evening I opened my moko to show to > some moko users the #1024 fix. I closed it, and WSOD ! It means : > no nand boot, no nor boot, only white screen but keep charging (red > power button) > I was a bit affraid of loosing my dear moko. I opened it agin, removing > Wifi module and > opening the GSM can (doing exactly what I did last night). Then I put > everything together, peacefully (I mean before my morning coffee), > blowing everywhere to remove some dust. (?) > Finally, I crossed my fingers, touch a rabbit leg, and pressed the power > button... Ta-da ! It booted again ... No more WSOD, a nice > BlackScreenWithConfusingWhiteText was rolling. > If it can help someone. > Thomas > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkqDpH8ACgkQmveDdjvKcqhxYQCeLsx0Vy9T1RHjaZWFB0SmwMZK lM8AnAt8VOJNMYXdAfarbNPithanTc9A =No8D -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
WSOD
Kosa a écrit : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > >> Don't fear... It won't be damaged for only 1minute and in tap Water. >> Salted water (sea) can damage it. >> > > Yes it can, My FR got dropped into the sea and it's dead. It still turns > on an I get a bright-white screen as the WSOD, and the wierd thing, it > still gets the charged, but I can't do nothing. I get no 'nor' nor nand. > > The good part, It happend two months ago and I just got a new one into > my office today, I'll picl it up tomorrow and I'll be happy again. > > > Kosa > > - - Un mundo mejor es posible - > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEARECAAYFAkqCA68ACgkQmveDdjvKcqh9awCfWds77+k1NQ/H0RvKDa86I1KI > LI0AnA+tyG4xu5IAE3PuFWplwDm34rLr > =TM/1 > -END PGP SIGNATURE- > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > > A pretty stange thing... Yesterday evening I opened my moko to show to some moko users the #1024 fix. I closed it, and WSOD ! It means : no nand boot, no nor boot, only white screen but keep charging (red power button) I was a bit affraid of loosing my dear moko. I opened it agin, removing Wifi module and opening the GSM can (doing exactly what I did last night). Then I put everything together, peacefully (I mean before my morning coffee), blowing everywhere to remove some dust. (?) Finally, I crossed my fingers, touch a rabbit leg, and pressed the power button... Ta-da ! It booted again ... No more WSOD, a nice BlackScreenWithConfusingWhiteText was rolling. If it can help someone. Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian 2.6.28|29 xserver-xorg-video-glamo] wsod when xserver stops
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 18.07.2009 um 15:22 schrieb Timo Jyrinki: > 2009/7/18 Christian Adams : >>> Indeed. I've run the latest GIT from >>> http://git.openmoko.org/?p=xf86-video-glamo.git;a=summary >> >> maybe a dumb question .. but could you give me some hints howto >> actually build it? > > Not a dumb question. I'm using Debian, so I have all the compilation > software directly on the phone, and also git. So, something like: > > apt-get install git-core build-essential gcc xserver-xorg-dev > git clone git://git.openmoko.org/git/xf86-video-glamo > cd xf86-video-glamo > > At this point you should run autotools, and I don't directly remember > what I ran. Probably something like: > > aclocal > libtoolize --automake > automake --add-missing > autoconf > > ...but I still had some problem so I simply ran autoreconf -vi also. > > then: > ./configure > make > > I installed the driver manually with: > > cp -a src/.libs/glamo_drv.so /usr/lib/xorg/modules/drivers/ > glamo_drv.so > > Hope this helps. > > -Timo thanks a lot timo, with these instructions it went flawlessly and playing with my freerunner is a lot more fun again :) cheers, christian (morlac) adams p.s. @arne anka: i'm not sure if i got that far if i didn't send my request to all IMHO relevant m/l .. - -- - -BEGIN CONTACT BLOCK- eMail: mor...@morlac.de Jabber: mor...@skavaer.homelinux.org - --END CONTACT BLOCK-- - -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS$/IT;d-;s:;a?;C++(+++)>;UL;P++(+++)>; L++(+++);E---;W++;N(+);o?;K?;!w;!O;!M+>;!V;PS(+);PE; Y+;PGP++;t+(++);5(+)>++;X(+);R*;tv->+;b++(+++);DI++; D++(+++)>;G(+)>++;e+>+++;h-()>++;r++;y++; - --END GEEK CODE BLOCK-- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFKYdmVr81gVylJyzERAiZiAKCijmR1crjFZkpQp1/IF8EFhs+z8QCeJVas JxvycPzWGKmv/r/d8ZHrIJs= =Jnbu -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian 2.6.28|29 xserver-xorg-video-glamo] wsod when xserver stops
2009/7/18 Christian Adams : >> Indeed. I've run the latest GIT from >> http://git.openmoko.org/?p=xf86-video-glamo.git;a=summary > > maybe a dumb question .. but could you give me some hints howto > actually build it? Not a dumb question. I'm using Debian, so I have all the compilation software directly on the phone, and also git. So, something like: apt-get install git-core build-essential gcc xserver-xorg-dev git clone git://git.openmoko.org/git/xf86-video-glamo cd xf86-video-glamo At this point you should run autotools, and I don't directly remember what I ran. Probably something like: aclocal libtoolize --automake automake --add-missing autoconf ...but I still had some problem so I simply ran autoreconf -vi also. then: ./configure make I installed the driver manually with: cp -a src/.libs/glamo_drv.so /usr/lib/xorg/modules/drivers/glamo_drv.so Hope this helps. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian 2.6.28|29 xserver-xorg-video-glamo] wsod when xserver stops
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 moinmoin, Am 17.07.2009 um 15:36 schrieb Timo Jyrinki: > 2009/7/16 Sebastian Krzyszkowiak : >>> since i installed 'xserver-xorg-video-glamo' instead 'xserver- >>> xglamo', every 2nd (or so) time >>> i try to shutdown/reboot i get a WSOD when x11 stops. >>> has someone an idea what i should do? >> >> Wait for upgrade. It's already fixed AFAIK. > > Indeed. I've run the latest GIT from > http://git.openmoko.org/?p=xf86-video-glamo.git;a=summary for over a > week now and haven't experienced the problem (nor the filling of > Xorg.0.log bug) anymore. > > -Timo maybe a dumb question .. but could you give me some hints howto actually build it? cheers, christian (morlac) adams - -- - -BEGIN CONTACT BLOCK- eMail: mor...@morlac.de Jabber: mor...@skavaer.homelinux.org - --END CONTACT BLOCK-- - -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS$/IT;d-;s:;a?;C++(+++)>;UL;P++(+++)>; L++(+++);E---;W++;N(+);o?;K?;!w;!O;!M+>;!V;PS(+);PE; Y+;PGP++;t+(++);5(+)>++;X(+);R*;tv->+;b++(+++);DI++; D++(+++)>;G(+)>++;e+>+++;h-()>++;r++;y++; - --END GEEK CODE BLOCK-- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD4DBQFKYcXHr81gVylJyzERAoS6AJ4kFf6cOPo/l24FXtnCg9ByLD5SgwCXW+V9 OpNB89AYSqjGpydbrlnPOQ== =kQjI -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian 2.6.28|29 xserver-xorg-video-glamo] wsod when xserver stops
2009/7/16 Sebastian Krzyszkowiak : >> since i installed 'xserver-xorg-video-glamo' instead 'xserver- >> xglamo', every 2nd (or so) time >> i try to shutdown/reboot i get a WSOD when x11 stops. >> has someone an idea what i should do? > > Wait for upgrade. It's already fixed AFAIK. Indeed. I've run the latest GIT from http://git.openmoko.org/?p=xf86-video-glamo.git;a=summary for over a week now and haven't experienced the problem (nor the filling of Xorg.0.log bug) anymore. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian 2.6.28|29 xserver-xorg-video-glamo] wsod when xserver stops
why did you send it to three lists at once? > since i installed 'xserver-xorg-video-glamo' instead 'xserver-xglamo', > every 2nd (or so) time > i try to shutdown/reboot i get a WSOD when x11 stops. > has someone an idea what i should do? i experience it, too. but i got the slight impression it is somehow related to nodm -- i started to see it, when nodm introduced that supervisor process (ie since there are _two_ instances of nodm running). ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian 2.6.28|29 xserver-xorg-video-glamo] wsod when xserver stops
On 7/16/09, Christian Adams wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > moinmoin, > > since i installed 'xserver-xorg-video-glamo' instead 'xserver- > xglamo', every 2nd (or so) time > i try to shutdown/reboot i get a WSOD when x11 stops. > has someone an idea what i should do? > > cheers, > christian (morlac) adams Wait for upgrade. It's already fixed AFAIK. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[debian 2.6.28|29 xserver-xorg-video-glamo] wsod when xserver stops
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 moinmoin, since i installed 'xserver-xorg-video-glamo' instead 'xserver- xglamo', every 2nd (or so) time i try to shutdown/reboot i get a WSOD when x11 stops. has someone an idea what i should do? cheers, christian (morlac) adams - -- - -BEGIN CONTACT BLOCK- eMail: mor...@morlac.de Jabber: mor...@skavaer.homelinux.org - --END CONTACT BLOCK-- - -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS$/IT;d-;s:;a?;C++(+++)>;UL;P++(+++)>; L++(+++);E---;W++;N(+);o?;K?;!w;!O;!M+>;!V;PS(+);PE; Y+;PGP++;t+(++);5(+)>++;X(+);R*;tv->+;b++(+++);DI++; D++(+++)>;G(+)>++;e+>+++;h-()>++;r++;y++; - --END GEEK CODE BLOCK-- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFKX2Vwr81gVylJyzERAt0eAJ98D9ggZM/Pyl60WtyfCz5d1Q3irgCdGJ1u iADYGpKn3C/h+d+n75p6ZV0= =AW4D -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-unstable] omgps wsod with full
no wdod for me, but the "enlightment crrashedd;..Recover ?" when I try the full screen in woosh, but not in tangogps., under the updated shr unstable 2009/6/29 jeremy jozwik > hey now! i made no mention of that lovable little keyboard. all i said > is that i switch illum to none. > > On Mon, Jun 29, 2009 at 12:10 PM, Michal Brzozowski > wrote: > > Same thing happens on Om2009 by the way. Illume or enlightenment bug. > Don't > > blame literki :-) > > > > 2009/6/29 jeremy jozwik > >> > >> i read some where else someone calling it the white screen of death > >> wsod, or "enlightement crashed, this is very bad..." > >> > >> On Mon, Jun 29, 2009 at 11:46 AM, Michal Brzozowski > >> wrote: > >> > By wsod do you mean the "enlightement crashed, this is very bad..." > >> > dialog? > >> > > >> > 2009/6/29 jeremy jozwik > >> >> > >> >> well... i think iv just narrowed it down. all my current applications > >> >> wsod on full screen because i, once again, set the illume keyboard to > >> >> none. > >> >> once i set it back to default everything calmed down. > >> >> > >> >> On Mon, Jun 29, 2009 at 11:30 AM, mqy wrote: > >> >> > > >> >> > hi jeremy, > >> >> > > >> >> > I encountered the WSOD two days ago with latest SHR-unstable, after > a > >> >> > upgrade without restart xserver or FR. > >> >> > Haven't seen that problem again after reboot. I suggest you try > other > >> >> > applications (eg. tangoGPS) with full/unfull buttons, and/or do a > >> >> > upgrade > >> >> > then test again. > >> >> > I will do a further check on omgps if this problem still exists > after > >> >> > your > >> >> > upgrade, but don't know where to start from for now :) > >> >> > > >> >> > > >> >> > jeremy jozwik wrote: > >> >> >> > >> >> >> running shr-unstable 20090624 with the latest version of omgps on > >> >> >> opkg.org. when i hit the "full" button i get a white screen of > >> >> >> death. > >> >> >> > >> >> >> no terminal errors to report. > >> >> >> > >> >> >> ___ > >> >> >> Openmoko community mailing list > >> >> >> community@lists.openmoko.org > >> >> >> http://lists.openmoko.org/mailman/listinfo/community > >> >> >> > >> >> >> > >> >> > > >> >> > -- > >> >> > View this message in context: > >> >> > > >> >> > > http://n2.nabble.com/-shr-unstable--omgps-wsod-with-full-tp3176059p3176211.html > >> >> > Sent from the Openmoko Community mailing list archive at > Nabble.com. > >> >> > > >> >> > > >> >> > ___ > >> >> > 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 > >> >> > >> > > >> > > >> > ___ > >> > 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 > >> > > > > > > ___ > > 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 > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-unstable] omgps wsod with full
hey now! i made no mention of that lovable little keyboard. all i said is that i switch illum to none. On Mon, Jun 29, 2009 at 12:10 PM, Michal Brzozowski wrote: > Same thing happens on Om2009 by the way. Illume or enlightenment bug. Don't > blame literki :-) > > 2009/6/29 jeremy jozwik >> >> i read some where else someone calling it the white screen of death >> wsod, or "enlightement crashed, this is very bad..." >> >> On Mon, Jun 29, 2009 at 11:46 AM, Michal Brzozowski >> wrote: >> > By wsod do you mean the "enlightement crashed, this is very bad..." >> > dialog? >> > >> > 2009/6/29 jeremy jozwik >> >> >> >> well... i think iv just narrowed it down. all my current applications >> >> wsod on full screen because i, once again, set the illume keyboard to >> >> none. >> >> once i set it back to default everything calmed down. >> >> >> >> On Mon, Jun 29, 2009 at 11:30 AM, mqy wrote: >> >> > >> >> > hi jeremy, >> >> > >> >> > I encountered the WSOD two days ago with latest SHR-unstable, after a >> >> > upgrade without restart xserver or FR. >> >> > Haven't seen that problem again after reboot. I suggest you try other >> >> > applications (eg. tangoGPS) with full/unfull buttons, and/or do a >> >> > upgrade >> >> > then test again. >> >> > I will do a further check on omgps if this problem still exists after >> >> > your >> >> > upgrade, but don't know where to start from for now :) >> >> > >> >> > >> >> > jeremy jozwik wrote: >> >> >> >> >> >> running shr-unstable 20090624 with the latest version of omgps on >> >> >> opkg.org. when i hit the "full" button i get a white screen of >> >> >> death. >> >> >> >> >> >> no terminal errors to report. >> >> >> >> >> >> ___ >> >> >> Openmoko community mailing list >> >> >> community@lists.openmoko.org >> >> >> http://lists.openmoko.org/mailman/listinfo/community >> >> >> >> >> >> >> >> > >> >> > -- >> >> > View this message in context: >> >> > >> >> > http://n2.nabble.com/-shr-unstable--omgps-wsod-with-full-tp3176059p3176211.html >> >> > Sent from the Openmoko Community mailing list archive at Nabble.com. >> >> > >> >> > >> >> > ___ >> >> > 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 >> >> >> > >> > >> > ___ >> > 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 >> > > > ___ > 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-unstable] omgps wsod with full
Same thing happens on Om2009 by the way. Illume or enlightenment bug. Don't blame literki :-) 2009/6/29 jeremy jozwik > i read some where else someone calling it the white screen of death > wsod, or "enlightement crashed, this is very bad..." > > On Mon, Jun 29, 2009 at 11:46 AM, Michal Brzozowski > wrote: > > By wsod do you mean the "enlightement crashed, this is very bad..." > dialog? > > > > 2009/6/29 jeremy jozwik > >> > >> well... i think iv just narrowed it down. all my current applications > >> wsod on full screen because i, once again, set the illume keyboard to > >> none. > >> once i set it back to default everything calmed down. > >> > >> On Mon, Jun 29, 2009 at 11:30 AM, mqy wrote: > >> > > >> > hi jeremy, > >> > > >> > I encountered the WSOD two days ago with latest SHR-unstable, after a > >> > upgrade without restart xserver or FR. > >> > Haven't seen that problem again after reboot. I suggest you try other > >> > applications (eg. tangoGPS) with full/unfull buttons, and/or do a > >> > upgrade > >> > then test again. > >> > I will do a further check on omgps if this problem still exists after > >> > your > >> > upgrade, but don't know where to start from for now :) > >> > > >> > > >> > jeremy jozwik wrote: > >> >> > >> >> running shr-unstable 20090624 with the latest version of omgps on > >> >> opkg.org. when i hit the "full" button i get a white screen of > death. > >> >> > >> >> no terminal errors to report. > >> >> > >> >> ___ > >> >> Openmoko community mailing list > >> >> community@lists.openmoko.org > >> >> http://lists.openmoko.org/mailman/listinfo/community > >> >> > >> >> > >> > > >> > -- > >> > View this message in context: > >> > > http://n2.nabble.com/-shr-unstable--omgps-wsod-with-full-tp3176059p3176211.html > >> > Sent from the Openmoko Community mailing list archive at Nabble.com. > >> > > >> > > >> > ___ > >> > 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 > >> > > > > > > ___ > > 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 > > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-unstable] omgps wsod with full
On Mon, 29 Jun 2009 11:50:07 -0700 jeremy jozwik (JJ) wrote: >i read some where else someone calling it the white screen of death >wsod, or "enlightement crashed, this is very bad..." watch out, wsod is different, no recovery except reboot. en crashing is another story... Petr ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-unstable] omgps wsod with full
i read some where else someone calling it the white screen of death wsod, or "enlightement crashed, this is very bad..." On Mon, Jun 29, 2009 at 11:46 AM, Michal Brzozowski wrote: > By wsod do you mean the "enlightement crashed, this is very bad..." dialog? > > 2009/6/29 jeremy jozwik >> >> well... i think iv just narrowed it down. all my current applications >> wsod on full screen because i, once again, set the illume keyboard to >> none. >> once i set it back to default everything calmed down. >> >> On Mon, Jun 29, 2009 at 11:30 AM, mqy wrote: >> > >> > hi jeremy, >> > >> > I encountered the WSOD two days ago with latest SHR-unstable, after a >> > upgrade without restart xserver or FR. >> > Haven't seen that problem again after reboot. I suggest you try other >> > applications (eg. tangoGPS) with full/unfull buttons, and/or do a >> > upgrade >> > then test again. >> > I will do a further check on omgps if this problem still exists after >> > your >> > upgrade, but don't know where to start from for now :) >> > >> > >> > jeremy jozwik wrote: >> >> >> >> running shr-unstable 20090624 with the latest version of omgps on >> >> opkg.org. when i hit the "full" button i get a white screen of death. >> >> >> >> no terminal errors to report. >> >> >> >> ___ >> >> Openmoko community mailing list >> >> community@lists.openmoko.org >> >> http://lists.openmoko.org/mailman/listinfo/community >> >> >> >> >> > >> > -- >> > View this message in context: >> > http://n2.nabble.com/-shr-unstable--omgps-wsod-with-full-tp3176059p3176211.html >> > Sent from the Openmoko Community mailing list archive at Nabble.com. >> > >> > >> > ___ >> > 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 >> > > > ___ > 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-unstable] omgps wsod with full
By wsod do you mean the "enlightement crashed, this is very bad..." dialog? 2009/6/29 jeremy jozwik > well... i think iv just narrowed it down. all my current applications > wsod on full screen because i, once again, set the illume keyboard to > none. > once i set it back to default everything calmed down. > > On Mon, Jun 29, 2009 at 11:30 AM, mqy wrote: > > > > hi jeremy, > > > > I encountered the WSOD two days ago with latest SHR-unstable, after a > > upgrade without restart xserver or FR. > > Haven't seen that problem again after reboot. I suggest you try other > > applications (eg. tangoGPS) with full/unfull buttons, and/or do a upgrade > > then test again. > > I will do a further check on omgps if this problem still exists after > your > > upgrade, but don't know where to start from for now :) > > > > > > jeremy jozwik wrote: > >> > >> running shr-unstable 20090624 with the latest version of omgps on > >> opkg.org. when i hit the "full" button i get a white screen of death. > >> > >> no terminal errors to report. > >> > >> ___ > >> Openmoko community mailing list > >> community@lists.openmoko.org > >> http://lists.openmoko.org/mailman/listinfo/community > >> > >> > > > > -- > > View this message in context: > http://n2.nabble.com/-shr-unstable--omgps-wsod-with-full-tp3176059p3176211.html > > Sent from the Openmoko Community mailing list archive at Nabble.com. > > > > > > ___ > > 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 > > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-unstable] omgps wsod with full
well... i think iv just narrowed it down. all my current applications wsod on full screen because i, once again, set the illume keyboard to none. once i set it back to default everything calmed down. On Mon, Jun 29, 2009 at 11:30 AM, mqy wrote: > > hi jeremy, > > I encountered the WSOD two days ago with latest SHR-unstable, after a > upgrade without restart xserver or FR. > Haven't seen that problem again after reboot. I suggest you try other > applications (eg. tangoGPS) with full/unfull buttons, and/or do a upgrade > then test again. > I will do a further check on omgps if this problem still exists after your > upgrade, but don't know where to start from for now :) > > > jeremy jozwik wrote: >> >> running shr-unstable 20090624 with the latest version of omgps on >> opkg.org. when i hit the "full" button i get a white screen of death. >> >> no terminal errors to report. >> >> ___ >> Openmoko community mailing list >> community@lists.openmoko.org >> http://lists.openmoko.org/mailman/listinfo/community >> >> > > -- > View this message in context: > http://n2.nabble.com/-shr-unstable--omgps-wsod-with-full-tp3176059p3176211.html > Sent from the Openmoko Community mailing list archive at Nabble.com. > > > ___ > 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-unstable] omgps wsod with full
hi jeremy, I encountered the WSOD two days ago with latest SHR-unstable, after a upgrade without restart xserver or FR. Haven't seen that problem again after reboot. I suggest you try other applications (eg. tangoGPS) with full/unfull buttons, and/or do a upgrade then test again. I will do a further check on omgps if this problem still exists after your upgrade, but don't know where to start from for now :) jeremy jozwik wrote: > > running shr-unstable 20090624 with the latest version of omgps on > opkg.org. when i hit the "full" button i get a white screen of death. > > no terminal errors to report. > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > > -- View this message in context: http://n2.nabble.com/-shr-unstable--omgps-wsod-with-full-tp3176059p3176211.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-unstable] omgps wsod with full
also seems to be happening with ffalarms... On Mon, Jun 29, 2009 at 11:02 AM, jeremy jozwik wrote: > running shr-unstable 20090624 with the latest version of omgps on > opkg.org. when i hit the "full" button i get a white screen of death. > > no terminal errors to report. > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[shr-unstable] omgps wsod with full
running shr-unstable 20090624 with the latest version of omgps on opkg.org. when i hit the "full" button i get a white screen of death. no terminal errors to report. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: shr - messages + wsod
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
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
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
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 - Latest unstable] WSOD?
could also confirm this, i hadn't testing it with u-boot, but since 4-6 days i hadn't a wsod.. :D On Mittwoch, 29. April 2009 18.00:09 Nelson Castillo wrote: > On Wed, Apr 29, 2009 at 4:28 AM, Tony Berth wrote: > > Dear List, > > > > before trying out the latest unstable image, can anyone confirm if WSOD > > was corrected? > > It has been confirmed that the WSOD will not happen with Qi. It will > happen with u-boot. > I'm testing this now. > > ___ > 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 - Latest unstable] WSOD?
On Wed, Apr 29, 2009 at 4:28 AM, Tony Berth wrote: > Dear List, > > before trying out the latest unstable image, can anyone confirm if WSOD was > corrected? It has been confirmed that the WSOD will not happen with Qi. It will happen with u-boot. I'm testing this now. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR - Latest unstable] WSOD?
On Wednesday 29 April 2009, Tony Berth wrote: > Dear List, > > before trying out the latest unstable image, can anyone confirm if WSOD was > corrected? I haven't seen it with: openmoko-shr-image-glibc-ipk--20090427-om-gta02.rootfs.tar.gz Then again I've never seen WSOD, and from what I remember it can depend on hardware tolerances, so perhaps I'm just lucky. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[SHR - Latest unstable] WSOD?
Dear List, before trying out the latest unstable image, can anyone confirm if WSOD was corrected? Thanks Tony ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: shr - messages + wsod
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
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
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
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
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
>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
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
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
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
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
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
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
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
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
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
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
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
Re: [SHR] latest unstabl;e WSOD!
ah, ok ! w, bad news 2009/4/5 Tony Berth > On Sun, Apr 5, 2009 at 1:33 PM, kimaidou wrote: > >> Sorry not to know, but what is WSOD please ? >> Thx >> >> 2009/4/5 Tony Berth >> >>> Dear Group, >>> >>> WSOD is back! Using the latest SHR unstable and after selecting >>> 'suspend', WSOD shows up! >>> >>> Thanks >>> >>> Tony >>> >>> > > White Screen Of Death! > > 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] latest unstabl;e WSOD!
On Sun, Apr 5, 2009 at 1:33 PM, kimaidou wrote: > Sorry not to know, but what is WSOD please ? > Thx > > 2009/4/5 Tony Berth > >> Dear Group, >> >> WSOD is back! Using the latest SHR unstable and after selecting 'suspend', >> WSOD shows up! >> >> Thanks >> >> Tony >> >> White Screen Of Death! Thanks Tony ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] latest unstabl;e WSOD!
Sorry not to know, but what is WSOD please ? Thx 2009/4/5 Tony Berth > Dear Group, > > WSOD is back! Using the latest SHR unstable and after selecting 'suspend', > WSOD shows up! > > 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
[SHR] latest unstabl;e WSOD!
Dear Group, WSOD is back! Using the latest SHR unstable and after selecting 'suspend', WSOD shows up! Thanks Tony ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR Unstable + Qi]: WSOD
2009/2/23 Jeffrey Ratcliffe > 2009/2/23 Nacho Seijo : > > I will flash uboot this afternoon, to try if I also get the annoying WSOD > > with it. > > This did it for me - with uBoot, no WSOD. I can also confirm it, with uBoot there's no WSOD, it resumes as expected. > > > Regards > > Jeff > > ___ > 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 Unstable + Qi]: WSOD
2009/2/23 Nacho Seijo : > I will flash uboot this afternoon, to try if I also get the annoying WSOD > with it. This did it for me - with uBoot, no WSOD. Regards Jeff ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR Unstable + Qi]: WSOD
2009/2/23 Andy Green > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > | I have just flashed my freerunner with the latest SHR unstable images: > | > > http://build.shr-project.org/shr-unstable/images/om-gta02/shr-image-om-gta02.jffs2 > | > > http://build.shr-project.org/shr-unstable/images/om-gta02/uImage-om-gta02-latest.bin > | and the latest Qi: > | > > http://people.openmoko.org/andy/qi-s3c2442-master-hist_1665e43677c005a8.udfu > | > | Once I booted it and it suspend for the first time, I get a WSOD. > | This issue hadn't be solved in 2.6.28 kernels? Has this something to do > | with Qi? > > Can you tell the result of > > cat /proc/version > > on that kernel? "gta02-latest" is so opaque it could mean anything, but > probably doesn't mean what it actually says. r...@om-gta02 ~ $ cat /proc/version Linux version 2.6.28-rc4 (s...@opmbuild) (gcc version 4.1.2) #1 PREEMPT Sun Feb 8 19:53:16 CET 2009 This is the result. > > > WSOD actual problem belongs in the LCM, the kernel though is the main > thing that will make it happen or not. I guess Qi can impact it but > it's not obvious how. I have also tried this other kernel: http://downloads.openmoko.org/distro/unstable/NeoFreerunner/uImage-2.6.28-oe1+gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r3-om-gta02.bin All this morning (in Spain) with the same results. I have just changed the kernel to shr unstable latest, that I downloaded yesterday. And I'm getting the same WSOD. I will flash uboot this afternoon, to try if I also get the annoying WSOD with it. > > > - -Andy > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org > > iEYEARECAAYFAkmiAgYACgkQOjLpvpq7dMraGwCfZwyVfuKls1ZIHqp5soJ0rqg8 > 3fsAn0Rb6FSdDVnGOgc9MJqQBQOIAwm3 > =i5kk > -END PGP SIGNATURE- > > ___ > 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 Unstable + Qi]: WSOD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | I have just flashed my freerunner with the latest SHR unstable images: | http://build.shr-project.org/shr-unstable/images/om-gta02/shr-image-om-gta02.jffs2 | http://build.shr-project.org/shr-unstable/images/om-gta02/uImage-om-gta02-latest.bin | and the latest Qi: | http://people.openmoko.org/andy/qi-s3c2442-master-hist_1665e43677c005a8.udfu | | Once I booted it and it suspend for the first time, I get a WSOD. | This issue hadn't be solved in 2.6.28 kernels? Has this something to do | with Qi? Can you tell the result of cat /proc/version on that kernel? "gta02-latest" is so opaque it could mean anything, but probably doesn't mean what it actually says. WSOD actual problem belongs in the LCM, the kernel though is the main thing that will make it happen or not. I guess Qi can impact it but it's not obvious how. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmiAgYACgkQOjLpvpq7dMraGwCfZwyVfuKls1ZIHqp5soJ0rqg8 3fsAn0Rb6FSdDVnGOgc9MJqQBQOIAwm3 =i5kk -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[SHR Unstable + Qi]: WSOD
I have just flashed my freerunner with the latest SHR unstable images: http://build.shr-project.org/shr-unstable/images/om-gta02/shr-image-om-gta02.jffs2 http://build.shr-project.org/shr-unstable/images/om-gta02/uImage-om-gta02-latest.bin and the latest Qi: http://people.openmoko.org/andy/qi-s3c2442-master-hist_1665e43677c005a8.udfu Once I booted it and it suspend for the first time, I get a WSOD. This issue hadn't be solved in 2.6.28 kernels? Has this something to do with Qi? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
On Thu, Dec 18, 2008 at 5:02 PM, Peter Abplanalp wrote: > On Thu, Dec 18, 2008 at 4:40 PM, Andy Green wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Somebody in the thread at some point said: >> >> | kernel - 2.6.24+r10.1+gitrf5b973489beb1a1239dfad53e3ad6e36ff7ee958-r10.1 >> | >> | /proc/version is: >> | >> | Linux version 2.6.24 (s...@builder) (gcc version 4.1.2) #1 PREEMPT Fri >> | Oct 17 17:20:36 UTC 2008 >> >> Yow it's from Oct 17... it has Harald's patches but not Nicolas' >> fixes... ancient kernel alert. Kernel from that vintage is expected to >> WSOD all over the place. > > can i change one of the opkg conf files to get a newer kernel to test with? i edited the om-gta02-feed.conf file to point to http://downloads.openmoko.org/repository/testing/om-gta02/ and the did an update/upgrade. this got me a new kernel, to wit: Upgrading kernel on root from 2.6.24+r10.1+gitrf5b973489beb1a1239dfad53e3ad6e36ff7ee958-r10.1 to 3:2.6.24+gitr76014+fb42ce6724576fc173faf8abfb04aa2c36d213b7-r2.01... and also a number of kernel modules and other stuff. i then rebooted the unit and ran my tests again. with this kernel, i no longer get the wsod on screen blank but i still get it when i suspend/resume. also, letting the unit blank/unblank after a wsod no longer clears up the wsod. something is not entirely kosher though as my usb networking went away. there may be other brokenness as well. -- Peter Abplanalp ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
On Thu, Dec 18, 2008 at 5:18 PM, Andy Green wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > | On Thu, Dec 18, 2008 at 4:40 PM, Andy Green wrote: > |> -BEGIN PGP SIGNED MESSAGE- > |> Hash: SHA1 > |> > |> Somebody in the thread at some point said: > |> > |> | kernel - > 2.6.24+r10.1+gitrf5b973489beb1a1239dfad53e3ad6e36ff7ee958-r10.1 > |> | > |> | /proc/version is: > |> | > |> | Linux version 2.6.24 (s...@builder) (gcc version 4.1.2) #1 PREEMPT Fri > |> | Oct 17 17:20:36 UTC 2008 > |> > |> Yow it's from Oct 17... it has Harald's patches but not Nicolas' > |> fixes... ancient kernel alert. Kernel from that vintage is expected to > |> WSOD all over the place. > | > | can i change one of the opkg conf files to get a newer kernel to test > with? > | > | after more testing i found that i can only get the wsod to clear up if > | i bring the unit back from blanking quickly on the second blank. if i > | wait longer than a couple minutes or so, i get the wsod again. is any > | of this information useful or should i try everything again with a > | newer kernel? > > I think it's just suffering for you at this point. > > I updated the http://people.openmoko.org/andy with current > andy-tracking, you can give that a try. should i just flash the andy-tracking kernel and try it with my existing fso rootfs and see what happens? i'm not sure how to "try andy-tracking". thanks, -peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | On Thu, Dec 18, 2008 at 4:40 PM, Andy Green wrote: |> -BEGIN PGP SIGNED MESSAGE- |> Hash: SHA1 |> |> Somebody in the thread at some point said: |> |> | kernel - 2.6.24+r10.1+gitrf5b973489beb1a1239dfad53e3ad6e36ff7ee958-r10.1 |> | |> | /proc/version is: |> | |> | Linux version 2.6.24 (s...@builder) (gcc version 4.1.2) #1 PREEMPT Fri |> | Oct 17 17:20:36 UTC 2008 |> |> Yow it's from Oct 17... it has Harald's patches but not Nicolas' |> fixes... ancient kernel alert. Kernel from that vintage is expected to |> WSOD all over the place. | | can i change one of the opkg conf files to get a newer kernel to test with? | | after more testing i found that i can only get the wsod to clear up if | i bring the unit back from blanking quickly on the second blank. if i | wait longer than a couple minutes or so, i get the wsod again. is any | of this information useful or should i try everything again with a | newer kernel? I think it's just suffering for you at this point. I updated the http://people.openmoko.org/andy with current andy-tracking, you can give that a try. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklK6HAACgkQOjLpvpq7dMrcDACgicsUP5XJmpad3LYIOb7bDiPj gBUAn1aHOmojlmG4QDF/9wVz2QFmUHHg =bNGt -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
On Thu, Dec 18, 2008 at 4:40 PM, Andy Green wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > > | kernel - 2.6.24+r10.1+gitrf5b973489beb1a1239dfad53e3ad6e36ff7ee958-r10.1 > | > | /proc/version is: > | > | Linux version 2.6.24 (s...@builder) (gcc version 4.1.2) #1 PREEMPT Fri > | Oct 17 17:20:36 UTC 2008 > > Yow it's from Oct 17... it has Harald's patches but not Nicolas' > fixes... ancient kernel alert. Kernel from that vintage is expected to > WSOD all over the place. can i change one of the opkg conf files to get a newer kernel to test with? after more testing i found that i can only get the wsod to clear up if i bring the unit back from blanking quickly on the second blank. if i wait longer than a couple minutes or so, i get the wsod again. is any of this information useful or should i try everything again with a newer kernel? -peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | kernel - 2.6.24+r10.1+gitrf5b973489beb1a1239dfad53e3ad6e36ff7ee958-r10.1 | | /proc/version is: | | Linux version 2.6.24 (s...@builder) (gcc version 4.1.2) #1 PREEMPT Fri | Oct 17 17:20:36 UTC 2008 Yow it's from Oct 17... it has Harald's patches but not Nicolas' fixes... ancient kernel alert. Kernel from that vintage is expected to WSOD all over the place. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklK33gACgkQOjLpvpq7dMrO3gCgkpKnBjK5MxXdrKp0T/Q8veX5 i1EAoICZuvH1lgm3pSGj8nZZm/El6um6 =N8xl -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
On Thu, Dec 18, 2008 at 7:16 AM, Peter Abplanalp wrote: > On Thu, Dec 18, 2008 at 3:18 AM, Andy Green wrote: >> Second, WSOD from resume is a bit ambiguous since it can be a more >> generic resume failure on 2.6.24. If you disable resume and just let it >> do framebuffer blanking for a while, do you ever see the WSOD just from >> that? > > i'm not sure how to turn on framebuffer blanking but i will do some > research and use that for a bit and report back; however, i have used > other distros where frameblanking was the norm and never had wsod. i > only get wsod after a resume. ok. i installed the latest fso from [1] and then did an opkg update/upgrade from these repos [2]. the kernel i end up with is: kernel - 2.6.24+r10.1+gitrf5b973489beb1a1239dfad53e3ad6e36ff7ee958-r10.1 /proc/version is: Linux version 2.6.24 (s...@builder) (gcc version 4.1.2) #1 PREEMPT Fri Oct 17 17:20:36 UTC 2008 what i've noticed is that i do, indeed, get a wsod on screen blanking when the unit is cold; however, if i let it blank again, the wsod goes away when i touch the screen again. i also get a wsod when i suspend the unit using a quick press of the power button, let the unit cool off on a window ledge and then resume with another quick press on the power button. the interesting thing is that, so far, i've been able to get rid of the wsod by letting the unit blank again and then touching the screen again. so it looks like something that this version of fso is doing upon unblanking the screen gets rid of the wsod. i will continue testing for the next couple days. if there is any other information that would be helpful, please let me know. -peter 1: http://downloads.freesmartphone.org/fso-stable/milestone4.1/ 2: all-feed.conf:src/gz remote-all http://downloads.freesmartphone.org/fso-testing/feeds//all armv4-feed.conf:src/gz remote-armv4 http://downloads.freesmartphone.org/fso-testing/feeds//armv4 armv4t-feed.conf:src/gz remote-armv4t http://downloads.freesmartphone.org/fso-testing/feeds//armv4t fic-gta02-feed.conf:src/gz remote-fic-gta02 http://downloads.freesmartphone.org/fso-testing/feeds//fic-gta02 neo1973-feed.conf:src/gz remote-neo1973 http://downloads.freesmartphone.org/fso-testing/feeds//neo1973 om-gta02-feed.conf:src/gz remote-om-gta02 http://downloads.freesmartphone.org/fso-testing/feeds//om-gta02 -- Peter Abplanalp ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
Hi, "Peter Abplanalp" writes: > can you also please point me to somewhere that tells me about > how to use andy-tracking instead of stock and what things might be > broken due to the /sys filesystem changes. Basically you can try to use andy-tracking with FSO ms4 with a quick-and-dirty patch from http://trac.freesmartphone.org/ticket/293 . The proper support is coming in MS5 (probably will be backported to stabilization/milestone4). It doesn't seem that any other distro is ready. What will be broken depends mostly on the distro's way of dealing with /sys. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
On Thu, Dec 18, 2008 at 8:17 AM, Andy Green wrote > Somebody in the thread at some point said: > > | i'm not sure how to turn on framebuffer blanking but i will do some > | research and use that for a bit and report back; however, i have used > | other distros where frameblanking was the norm and never had wsod. i > | only get wsod after a resume. > > I guess it is another Glamo / suspend related misery. > > On andy-tracking I changed the Glamo resume to hard reset the Glamo and > reload it every time. This works around a variety of WSOD caused by > accidental actuation of Glamo's reset signal during suspend via a dodgy > resistor divider. > > Later today I'll update the testing binaries in > http://people.openmoko.org/andy and I think that will impact this > problem for you. thanks a lot andy. please let me know when this happens so i can update. can you also please point me to somewhere that tells me about how to use andy-tracking instead of stock and what things might be broken due to the /sys filesystem changes. thanks, -peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | i'm not sure how to turn on framebuffer blanking but i will do some | research and use that for a bit and report back; however, i have used | other distros where frameblanking was the norm and never had wsod. i | only get wsod after a resume. I guess it is another Glamo / suspend related misery. On andy-tracking I changed the Glamo resume to hard reset the Glamo and reload it every time. This works around a variety of WSOD caused by accidental actuation of Glamo's reset signal during suspend via a dodgy resistor divider. Later today I'll update the testing binaries in http://people.openmoko.org/andy and I think that will impact this problem for you. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklKaYUACgkQOjLpvpq7dMolRwCdGnVieQx0k7qpF4xzwxVAmGNc BOkAn0rkZDGfl63vPUY3IYValwgigPv+ =Cu9d -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
thanks for the help, andy. On Thu, Dec 18, 2008 at 3:18 AM, Andy Green wrote: > Well, first confirm with cat /proc/version that you're running what you > think you're running. r...@om-gta02:~# cat /proc/version Linux version 2.6.24 (bu...@barbie) (gcc version 4.1.2) #1 PREEMPT Tue Dec 16 09:01:00 CST 2008 'opkg list_installed | grep kernel' gives a lot of packages. most have the version: 3:2.6.24+gitr76014+fb42ce6724576fc173faf8abfb04aa2c36d213b7-r2.01 however, there is one that is different, and that would be: kernel-module-usbhid - 3:2.6.24+gitr75986+f5b973489beb1a1239dfad53e3ad6e36ff7ee958-r2 i have 3 packages that look like actual kernel packages. i think a couple of them might be meta packages but they are: kernel - 3:2.6.24+gitr76014+fb42ce6724576fc173faf8abfb04aa2c36d213b7-r2.01 kernel-2.6.24 - 3:2.6.24+gitr76014+fb42ce6724576fc173faf8abfb04aa2c36d213b7-r2.01 kernel-image-2.6.24 - 3:2.6.24+gitr76014+fb42ce6724576fc173faf8abfb04aa2c36d213b7-r2.01 they all look the same to me as far as version is concerned. i hope that helps. > Second, WSOD from resume is a bit ambiguous since it can be a more > generic resume failure on 2.6.24. If you disable resume and just let it > do framebuffer blanking for a while, do you ever see the WSOD just from > that? i'm not sure how to turn on framebuffer blanking but i will do some research and use that for a bit and report back; however, i have used other distros where frameblanking was the norm and never had wsod. i only get wsod after a resume. -peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: |> ok, so i flashed the images above and then did a wget for the kernel |> opk and then did a opkg install |> kernel-2.6.24_2.6.24+gitr76014+fb42ce6724576fc173faf8abfb04aa2c36d213b7-r2.01_om-gta02.opk. |> |> again after 5-10 suspend/resume cycles, i got the wsod again. does |> this mean i did something wrong or that you are mistaken or that i was |> unlucky enough to get bad hardware? Well, first confirm with cat /proc/version that you're running what you think you're running. Second, WSOD from resume is a bit ambiguous since it can be a more generic resume failure on 2.6.24. If you disable resume and just let it do framebuffer blanking for a while, do you ever see the WSOD just from that? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklKI2AACgkQOjLpvpq7dMp+ZwCfcc08rVov6HwcjRzlUVV1eFtG iVgAmwfV4YDHAWuoNB3tXw4fOjriSbth =VPSs -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
On Wed, Dec 17, 2008 at 07:57:17PM +, Andy Green wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > > | > http://downloads.openmoko.org/daily/testing/openmoko-testing-om-gta02.rootfs.jffs2 > | > http://downloads.openmoko.org/daily/testing/testing-om-gta02-20081216.uImage.bin > | > | booted it up and within 5-10 suspend/resume cycles i got the wsod > | again. should these images have the fix? if not, can someone point > | me to a kernel/rootfs that doesn't wsod? > > I can't tell from the filename if they should have it or not. But, I > can tell from the filename of this package that it should have it. > > http://downloads.openmoko.org/repository/testing/om-gta02/kernel-2.6.24_2.6.24+gitr76014+fb42ce6724576fc173faf8abfb04aa2c36d213b7-r2.01_om-gta02.opk > > John, maybe you can clarify the situation with the other path (and maybe > change it to have a git hash). The filenames under daily/testing is as it is now because Sean specifically requested these to be 'simplified' many times in the past. Not sure if Ray wants to change it again. The versions of the kernel packages in the system could be obtained by opkg list_installed | grep kernel I think it would help to clarify the situation. - John > - -Andy > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org > > iEYEARECAAYFAklJWZ0ACgkQOjLpvpq7dMp0VQCfVxId2dAzx9XxgQfd7GnapaHW > h0cAn1YOwxA34xbNLDgWNnwmpBBD9mdW > =vqJO > -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
additional note. the wsod is definitely temperature related. when in my cold basement, i get the wsod every time on suspend/resume. i'd like to know what my options are from here on out. i'd be happy to ship my freerunner to someone who can help debug this or perform any testing that i can to help. -peter On Wed, Dec 17, 2008 at 6:56 PM, Peter Abplanalp wrote: > On Wed, Dec 17, 2008 at 5:41 PM, Peter Abplanalp > wrote: >> On Wed, Dec 17, 2008 at 12:57 PM, Andy Green wrote: >>> Somebody in the thread at some point said: >>> >>> | >>> http://downloads.openmoko.org/daily/testing/openmoko-testing-om-gta02.rootfs.jffs2 >>> | >>> | >>> http://downloads.openmoko.org/daily/testing/testing-om-gta02-20081216.uImage.bin >>> | >>> | booted it up and within 5-10 suspend/resume cycles i got the wsod >>> | again. should these images have the fix? if not, can someone point >>> | me to a kernel/rootfs that doesn't wsod? >>> >>> I can't tell from the filename if they should have it or not. But, I >>> can tell from the filename of this package that it should have it. >>> >>> http://downloads.openmoko.org/repository/testing/om-gta02/kernel-2.6.24_2.6.24+gitr76014+fb42ce6724576fc173faf8abfb04aa2c36d213b7-r2.01_om-gta02.opk >> >> after having installed the packages above, can i just opkg install >> this kernel you mention? > > ok, so i flashed the images above and then did a wget for the kernel > opk and then did a opkg install > kernel-2.6.24_2.6.24+gitr76014+fb42ce6724576fc173faf8abfb04aa2c36d213b7-r2.01_om-gta02.opk. > > again after 5-10 suspend/resume cycles, i got the wsod again. does > this mean i did something wrong or that you are mistaken or that i was > unlucky enough to get bad hardware? > > if the first, please tell me what i did wrong. if the second, could > you point me to a kernel that has the fix? if the third, can i get a > warranty replacement? if so, how do i go about doing that? i bought > my phone from the web shop. > > thanks, > > -peter > -- Peter Abplanalp ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
On Wed, Dec 17, 2008 at 5:41 PM, Peter Abplanalp wrote: > On Wed, Dec 17, 2008 at 12:57 PM, Andy Green wrote: >> Somebody in the thread at some point said: >> >> | >> http://downloads.openmoko.org/daily/testing/openmoko-testing-om-gta02.rootfs.jffs2 >> | >> | >> http://downloads.openmoko.org/daily/testing/testing-om-gta02-20081216.uImage.bin >> | >> | booted it up and within 5-10 suspend/resume cycles i got the wsod >> | again. should these images have the fix? if not, can someone point >> | me to a kernel/rootfs that doesn't wsod? >> >> I can't tell from the filename if they should have it or not. But, I >> can tell from the filename of this package that it should have it. >> >> http://downloads.openmoko.org/repository/testing/om-gta02/kernel-2.6.24_2.6.24+gitr76014+fb42ce6724576fc173faf8abfb04aa2c36d213b7-r2.01_om-gta02.opk > > after having installed the packages above, can i just opkg install > this kernel you mention? ok, so i flashed the images above and then did a wget for the kernel opk and then did a opkg install kernel-2.6.24_2.6.24+gitr76014+fb42ce6724576fc173faf8abfb04aa2c36d213b7-r2.01_om-gta02.opk. again after 5-10 suspend/resume cycles, i got the wsod again. does this mean i did something wrong or that you are mistaken or that i was unlucky enough to get bad hardware? if the first, please tell me what i did wrong. if the second, could you point me to a kernel that has the fix? if the third, can i get a warranty replacement? if so, how do i go about doing that? i bought my phone from the web shop. thanks, -peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
On Wed, Dec 17, 2008 at 12:57 PM, Andy Green wrote: > Somebody in the thread at some point said: > > | > http://downloads.openmoko.org/daily/testing/openmoko-testing-om-gta02.rootfs.jffs2 > | > | > http://downloads.openmoko.org/daily/testing/testing-om-gta02-20081216.uImage.bin > | > | booted it up and within 5-10 suspend/resume cycles i got the wsod > | again. should these images have the fix? if not, can someone point > | me to a kernel/rootfs that doesn't wsod? > > I can't tell from the filename if they should have it or not. But, I > can tell from the filename of this package that it should have it. > > http://downloads.openmoko.org/repository/testing/om-gta02/kernel-2.6.24_2.6.24+gitr76014+fb42ce6724576fc173faf8abfb04aa2c36d213b7-r2.01_om-gta02.opk after having installed the packages above, can i just opkg install this kernel you mention? thanks, -peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | http://downloads.openmoko.org/daily/testing/openmoko-testing-om-gta02.rootfs.jffs2 | http://downloads.openmoko.org/daily/testing/testing-om-gta02-20081216.uImage.bin | | booted it up and within 5-10 suspend/resume cycles i got the wsod | again. should these images have the fix? if not, can someone point | me to a kernel/rootfs that doesn't wsod? I can't tell from the filename if they should have it or not. But, I can tell from the filename of this package that it should have it. http://downloads.openmoko.org/repository/testing/om-gta02/kernel-2.6.24_2.6.24+gitr76014+fb42ce6724576fc173faf8abfb04aa2c36d213b7-r2.01_om-gta02.opk John, maybe you can clarify the situation with the other path (and maybe change it to have a git hash). - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklJWZ0ACgkQOjLpvpq7dMp0VQCfVxId2dAzx9XxgQfd7GnapaHW h0cAn1YOwxA34xbNLDgWNnwmpBBD9mdW =vqJO -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
after my last email, i went looking around the wiki and found this section: http://wiki.openmoko.org/wiki/Latest_Images#The_bleeding_edge:_Om_.22base_.2F_empty.22_images which talks about "testing" images and so i downloaded and flashed the following: http://downloads.openmoko.org/daily/testing/openmoko-testing-om-gta02.rootfs.jffs2 http://downloads.openmoko.org/daily/testing/testing-om-gta02-20081216.uImage.bin booted it up and within 5-10 suspend/resume cycles i got the wsod again. should these images have the fix? if not, can someone point me to a kernel/rootfs that doesn't wsod? thanks, -peter On Wed, Dec 17, 2008 at 9:43 AM, Peter Abplanalp wrote: > let me preface this with thanking andy, all the devs and om for all > the hard work. i'm really excited about om and their "free your > phone" ideas. i am happy to support this effort by buying a phone > that isn't 100%. that said, there are some things that irritate me... > > On Wed, Dec 17, 2008 at 9:23 AM, Andy Green wrote: >> Somebody in the thread at some point said: >> >> | i have been reading about this fix for a couple weeks now and how it >> | is in andy-tracking and testing and how it was supposed to be in >> | stable "soon." reading your email, andy, i assume that it is now in >> >> Nicolas' patches went in to our stable kernel 12 days ago, but when the >> various distros update to that, or if they want to use some different >> kernel tree is up to them. > > do any of them document this? i can't for the life of me figure out > which kernel each distro is using. why can't i just install what i > want and then opkg upgrade to the latest? how dependent are the > distros on the kernel? can i install a kernel from "here" and a > rootfs (distro) from "there"? if so, where are the "blessed" kernels? > >> | so, my question is: what is the easiest way to get the wsod fix. >> | which distro, which uimage, etc. my choice would be to use andy >> | tracking since that seems to be the future but i understand that most >> | of the distros will have some broken bits due to some changes. >> | >> | this is really the last annoyance for me in using the phone on a >> | regular basis. >> >> The kernel packages in testing repository have the workaround: >> >> http://downloads.openmoko.org/repository/testing/om-gta02/ > > ok, thanks for the link but that is a list of packages. how do i get > a phone with that on it? if i install om2008.9, does that get me > there? do i need to opkg update/upgrade? do i need to modify my opk > config first? if so, how? > > as i said above, i'm content to own a "brick" due to the fact that i > want to support this effort but i'd still rather have a working phone; > however, i just can't seem to get there. things are just too > splintered. i can't figure out what bits to put together in order to > get a working phone with my particular annoyance fixed. > > thanks, > > -peter > -- Peter Abplanalp ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
let me preface this with thanking andy, all the devs and om for all the hard work. i'm really excited about om and their "free your phone" ideas. i am happy to support this effort by buying a phone that isn't 100%. that said, there are some things that irritate me... On Wed, Dec 17, 2008 at 9:23 AM, Andy Green wrote: > Somebody in the thread at some point said: > > | i have been reading about this fix for a couple weeks now and how it > | is in andy-tracking and testing and how it was supposed to be in > | stable "soon." reading your email, andy, i assume that it is now in > > Nicolas' patches went in to our stable kernel 12 days ago, but when the > various distros update to that, or if they want to use some different > kernel tree is up to them. do any of them document this? i can't for the life of me figure out which kernel each distro is using. why can't i just install what i want and then opkg upgrade to the latest? how dependent are the distros on the kernel? can i install a kernel from "here" and a rootfs (distro) from "there"? if so, where are the "blessed" kernels? > | so, my question is: what is the easiest way to get the wsod fix. > | which distro, which uimage, etc. my choice would be to use andy > | tracking since that seems to be the future but i understand that most > | of the distros will have some broken bits due to some changes. > | > | this is really the last annoyance for me in using the phone on a > | regular basis. > > The kernel packages in testing repository have the workaround: > > http://downloads.openmoko.org/repository/testing/om-gta02/ ok, thanks for the link but that is a list of packages. how do i get a phone with that on it? if i install om2008.9, does that get me there? do i need to opkg update/upgrade? do i need to modify my opk config first? if so, how? as i said above, i'm content to own a "brick" due to the fact that i want to support this effort but i'd still rather have a working phone; however, i just can't seem to get there. things are just too splintered. i can't figure out what bits to put together in order to get a working phone with my particular annoyance fixed. thanks, -peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | i have been reading about this fix for a couple weeks now and how it | is in andy-tracking and testing and how it was supposed to be in | stable "soon." reading your email, andy, i assume that it is now in Nicolas' patches went in to our stable kernel 12 days ago, but when the various distros update to that, or if they want to use some different kernel tree is up to them. | so, my question is: what is the easiest way to get the wsod fix. | which distro, which uimage, etc. my choice would be to use andy | tracking since that seems to be the future but i understand that most | of the distros will have some broken bits due to some changes. | | this is really the last annoyance for me in using the phone on a regular basis. The kernel packages in testing repository have the workaround: http://downloads.openmoko.org/repository/testing/om-gta02/ The ones in the unstable repo lack it (?) Anyway the ones in the unstable repo should shortly become andy-tracking based, but not, evidently, yet. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklJJ3oACgkQOjLpvpq7dMqSFgCdFzRvlrOGT1Rl2aTjFisD+DPP f94An1Dr5+UTPY4r0sPmILBVkRqXEo+q =TQhf -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
On Wed, Dec 17, 2008 at 4:05 AM, Andy Green wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > > | For the WSOD, I recommand you to use the SHR distribution. > | > | I had the same problem for a few month, killing any usuability of the > | phone, but since SHR have resolved it, it's far more enjoyable to use > | the phone. > > Nicolas Dufresne resolved it with a couple of patches that are in our > current stable and andy-tracking kernels now. So the solution is > independent of the distro used. i have been reading about this fix for a couple weeks now and how it is in andy-tracking and testing and how it was supposed to be in stable "soon." reading your email, andy, i assume that it is now in stable. so i excitedly installed the shr distro since someone else in the thread mentioned it as a good wsod avoidance choice. i installed a rootfs dated 12/16 and a uimage dated 12/14. well, much to my dismay, i just got a wsod again. so, my question is: what is the easiest way to get the wsod fix. which distro, which uimage, etc. my choice would be to use andy tracking since that seems to be the future but i understand that most of the distros will have some broken bits due to some changes. this is really the last annoyance for me in using the phone on a regular basis. thanks, -peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | For the WSOD, I recommand you to use the SHR distribution. | | I had the same problem for a few month, killing any usuability of the | phone, but since SHR have resolved it, it's far more enjoyable to use | the phone. Nicolas Dufresne resolved it with a couple of patches that are in our current stable and andy-tracking kernels now. So the solution is independent of the distro used. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklI3PYACgkQOjLpvpq7dMq3vACdGs+2DsC4F5nAFg4wwaiLAtPV VwsAn05XxOiVxvf7KQ2Du+d3Up1F4YVa =ZbPM -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WSOD
Hi Ole, For the WSOD, I recommand you to use the SHR distribution. I had the same problem for a few month, killing any usuability of the phone, but since SHR have resolved it, it's far more enjoyable to use the phone. You can download it here: http://shr.bearstech.com/shr-testing/images/neo1973/ shr-image-om-gta02.jffs2 at the end of the list. Alex On 17/12/2008, at 13:10, Ole Kliemann wrote: > Hi everyone! > > I have not been reading the lists lately, so I don't know if this is > an > old one. > > I have been suffering badly from WSOD. This means, often when I > resumed > from suspend the screen showed all white while other things still > worked. Sometimes it recovered after some minutes and screen worked > again, sometimes I waited for maybe 10 minutes then switched off the > device. I had this problem since I got the device in July and I always > thought this was a kernel problem. I tried about every kernel > version so > far but it was always the same. > > Now, GPS was not working on my device, so last week I finally returned > it to my distributor and he sent me a new one. > > I am using the exact same kernel and distribution[1] that was giving > my > WSOD all the time on the old device (just like every kernel and > distribution was given WSOD). But suspend/resume is now working > flawlessly. No white screen ever! > > So this bug is highly hardware related after all? Replacing the > hardware > fixed it for me. > > Ole > > [1] http://qtextended.org/modules/mydownloads/visit.php?lid=98 > ___ > 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
WSOD
Hi everyone! I have not been reading the lists lately, so I don't know if this is an old one. I have been suffering badly from WSOD. This means, often when I resumed from suspend the screen showed all white while other things still worked. Sometimes it recovered after some minutes and screen worked again, sometimes I waited for maybe 10 minutes then switched off the device. I had this problem since I got the device in July and I always thought this was a kernel problem. I tried about every kernel version so far but it was always the same. Now, GPS was not working on my device, so last week I finally returned it to my distributor and he sent me a new one. I am using the exact same kernel and distribution[1] that was giving my WSOD all the time on the old device (just like every kernel and distribution was given WSOD). But suspend/resume is now working flawlessly. No white screen ever! So this bug is highly hardware related after all? Replacing the hardware fixed it for me. Ole [1] http://qtextended.org/modules/mydownloads/visit.php?lid=98 pgp3fTH3NgAAK.pgp Description: PGP signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [testing] WSOD gone
Evgeny Karyakin wrote: > 2008/12/7 Andreas Cyberfrag Fischer <[EMAIL PROTECTED]>: >> This is on the testing branch. Flash OM2008.9, switch to testing as >> described here: >> http://n2.nabble.com/Optimization-team-update-%2811-23-%7E-11-29%29-td1595015.html#a1600801 >> and do a full update (opkg update && opkg upgrade). > >Will it bump all the software to the latest? I mean, will the phone > end up with all software from 2008.x official release (kernel + > graphics + qtopia dialer + gps + ...), but latest versions of them? I > guess so. >For a couple of weeks I just take > http://downloads.openmoko.org/daily/testing/ images to play with, and > constantly being ridicued by colleagues like "what have you bought, a > black screen with white letters?" :-) . I must say in this textual > state Neo performs very well. Not sure what you mean by that. I have (and always had) a fully functional Illume-desktop. And yes, the 2008.9 software was simply updated to newer versions (git revisions). BTW: Show your colleagues a round of DukeNukem and see if they still ridicule you :D Regards, Andreas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [testing] WSOD gone
2008/12/7 Andreas Cyberfrag Fischer <[EMAIL PROTECTED]>: > This is on the testing branch. Flash OM2008.9, switch to testing as > described here: > http://n2.nabble.com/Optimization-team-update-%2811-23-%7E-11-29%29-td1595015.html#a1600801 > and do a full update (opkg update && opkg upgrade). Will it bump all the software to the latest? I mean, will the phone end up with all software from 2008.x official release (kernel + graphics + qtopia dialer + gps + ...), but latest versions of them? I guess so. For a couple of weeks I just take http://downloads.openmoko.org/daily/testing/ images to play with, and constantly being ridicued by colleagues like "what have you bought, a black screen with white letters?" :-) . I must say in this textual state Neo performs very well. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [testing] WSOD gone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 07.12.2008 10:05, ivvmm schrieb: > Andreas "Cyberfrag" Fischer wrote: >> Hi All, >> >> Wohoo, after today's kernel upgrade the infamous WSOD seems to be gone >> for me. I rebooted the phone and am now running for several hours >> without encoutering WSOD. The phone seems to reliably wake up from >> suspend at incoming calls (tested only once, though) and performs quite >> fine after manual resume. I didn't test incoming SMS, yet. >> >> Anyway - good job guys. Now I only need a fix for the annoying echo to >> have a (in my point of view) fully functional phone. >> >> Regards, >> Andreas > > You said you updated with opkg update && opkg upgrade > > But is kernel being upgraded if you are updating this way? I just wonder. Yes, the kernel was definitely updated from one git revision to another (same major/minor number though). There was a section during the upgrade where the kernel was explicitely written to its flash partition (messages about "XYZ bytes written" - or somewhat like that - flushed by). Regards, Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkk7nSEACgkQ5Fl7TYZQYwFdVQCfaJluNiZZwdclGjsiAeEIpe/I fSkAoK7rO8+HDtx692k+oHZvEfRSj2oX =TszB -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [testing] WSOD gone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 07.12.2008 03:43, John Lee schrieb: > On Sat, Dec 06, 2008 at 11:00:24PM +0100, Andreas Cyberfrag Fischer wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Am 06.12.2008 20:33, Alexandre Girard schrieb: >>> Hi Andreas, >>> >>> That's a great news I was looking for :) >>> >>> Where to get and download this image? >> Hi Alex, >> >> This is on the testing branch. Flash OM2008.9, switch to testing as >> described here: >> http://n2.nabble.com/Optimization-team-update-%2811-23-%7E-11-29%29-td1595015.html#a1600801 >> and do a full update (opkg update && opkg upgrade). >> >> If you want to stay on the safe side however, I'd recommend to wait for >> the upcoming stable release 200?.??. >> >> Regards, >> Andreas > > Or flashing the testing image directly... > > http://downloads.openmoko.org/daily/testing/ Ah - ok. I wasn't aware of that. Regards, Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkk7nIoACgkQ5Fl7TYZQYwGfJACfWOdvcZ5nYR40v5XXcMSVaQYz fCgAn1cGaOJ+2/A/VpT9G7lULTS/iGN5 =oUSC -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [testing] WSOD gone
Andreas "Cyberfrag" Fischer wrote: > Hi All, > > Wohoo, after today's kernel upgrade the infamous WSOD seems to be gone > for me. I rebooted the phone and am now running for several hours > without encoutering WSOD. The phone seems to reliably wake up from > suspend at incoming calls (tested only once, though) and performs quite > fine after manual resume. I didn't test incoming SMS, yet. > > Anyway - good job guys. Now I only need a fix for the annoying echo to > have a (in my point of view) fully functional phone. > > Regards, > Andreas You said you updated with opkg update && opkg upgrade But is kernel being upgraded if you are updating this way? I just wonder. signature.asc Description: OpenPGP digital signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
