Re: [gta02] cannot boot from NAND
On Monday, December 16, 2013 10:12:08 PM Ben Wong wrote: There must be some timing problem. It can be quite tricky to debug it, because with logging it works and with debugging enabled it works too. Timing with the AT communications? Would that be the chat script? No idea, i guess it will be a lot of debug prints and recompiling to find this out. That would be a nice one to fix. If I don't notice that I've received a text message or call, I'll sometimes find later that the phone is very warm and the battery nearly dead even though I haven't been using it. It seems i understand the problem and have a workaround that works on v58. The problem seems to be in QtMoko power management handling. You can set intervals for dim, screen off and suspend. There are intervals between them and it always goes like: dim-screen off-suspend If you dont specify interval between screen off-suspend QtMoko automatically places 100ms there. But this is probably not enough and suspend never happens. The workaround: go to Settings-Power management-select On battery and fill in good intevals - e.g. Dim=off, Display off=30s, Suspend=40s and it will auto suspend ok. The trick is that Display off must be filled and must be more then 10s less then suspend. 4/ maybe fix the wifi dialog It would be nice if it was sane. But even just ditching it and having something simple, even trivial like OpenWRT's ewoc-cli script, would be an improvement. You can use standard debian networking (/etc/network/interfaces) even for wpa2 connections. There are some docs on internet how to do it. BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [gta02] cannot boot from NAND
There must be some timing problem. It can be quite tricky to debug it, because with logging it works and with debugging enabled it works too. Timing with the AT communications? Would that be the chat script? 3/ implement better screen locking. Now if you lock screen and receive phone call the screen unlocks and never locks again. I'd like to have it locked once the call ends. That would be a nice one to fix. If I don't notice that I've received a text message or call, I'll sometimes find later that the phone is very warm and the battery nearly dead even though I haven't been using it. 4/ maybe fix the wifi dialog It would be nice if it was sane. But even just ditching it and having something simple, even trivial like OpenWRT's ewoc-cli script, would be an improvement. —B P.S. I've got my phone working again with v58. Apparently my kernel hadn't flashed correctly. And like everyone else, I had to enable logging to get past the number pad screen. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [gta02] cannot boot from NAND
Me too, jffs works but had to enable modem logging to get trough the pin screen. Jorge On 14/12/13 13:41, Francesco De Vita wrote: Thank you Radek, the jffs2 image works on NAND! But, as happened for the uSD version, the system stops at the PIN screen. However, as you suggested, enabling the modem logging solves the problem. Regards Joif ___ 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: [gta02] cannot boot from NAND
On Monday, December 16, 2013 04:11:20 AM Jorge wrote: Me too, jffs works but had to enable modem logging to get trough the pin screen. There must be some timing problem. It can be quite tricky to debug it, because with logging it works and with debugging enabled it works too. But with logging it seems to work well. I am now using GTA02 again as my phone. My plan for v59 is: 1/ fix this problem 2/ autosuspend issue (the phone dims screen but instead of suspend it wakes again). 3/ implement better screen locking. Now if you lock screen and receive phone call the screen unlocks and never locks again. I'd like to have it locked once the call ends. 4/ maybe fix the wifi dialog The last points are optional, we'll se how easy will they be. BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [gta02] cannot boot from NAND
On Friday, December 13, 2013 04:18:13 PM Francesco De Vita wrote: Is the tarball ok at least? Tested on the uSD and it is ok ...apart that I'm stuck at the PIN entry screen (that one with just the notice Please wait...) no matter how many times I restart. But from ssh all seems to work well. Hi, can you try enable modem logging? Long press AUX, from Favourites screen context menu use Add, select Logging. Then answer twice Yes, from context menu select Modem AT communication. After restart QtMoko should work as expected. This is most likely some bad timing bug, because in NAND it works ok. BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [gta02] cannot boot from NAND
On Friday, December 13, 2013 04:18:13 PM Francesco De Vita wrote: Is the tarball ok at least? Tested on the uSD and it is ok ...apart that I'm stuck at the PIN entry screen (that one with just the notice Please wait...) no matter how many times I restart. But from ssh all seems to work well. Btw i have now uploaded even jffs2 image. You'll need qi-jffs-v58.udfu - both can be downloaded from here: http://sourceforge.net/projects/qtmoko/files/GTA02/ Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [gta02] cannot boot from NAND
Thank you Radek, the jffs2 image works on NAND! But, as happened for the uSD version, the system stops at the PIN screen. However, as you suggested, enabling the modem logging solves the problem. Regards Joif ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [gta02] cannot boot from NAND
Weirdly, I'm getting a panic on boot with the JFFS2 images for rootfs and u-boot. I'll try resending with dfu-util again. —B P.S. When I mentioned using 'dd' before to write directly, I meant to say 'nandwrite'. On Sat, Dec 14, 2013 at 7:41 AM, Francesco De Vita francesco.dev...@mailoo.org wrote: Thank you Radek, the jffs2 image works on NAND! But, as happened for the uSD version, the system stops at the PIN screen. However, as you suggested, enabling the modem logging solves the problem. Regards Joif ___ 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: [gta02] cannot boot from NAND
882cc204627226ffefda4e446fae3862 qtmoko-debian-gta02-v58.tar.gz a76072c1c9dce4eb2b07235f7cc307fe qtmoko-debian-gta02-v58.ubi 50baec96657802b5a053fa0ef6b777a2 uImage.bin-2.6.39-qtmoko-v58 checksum ok This is strange - it works for me. Are you booting with qi-v58.udfu? Yep, I also reflashed qi-v56 but the problem persists Is the tarball ok at least? I'll try it soon Regards Joif ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [gta02] cannot boot from NAND
On Thu, Dec 12, 2013 at 11:10 PM, Radek Polak pson...@seznam.cz wrote: On Friday, December 13, 2013 02:59:01 AM Ben Wong wrote: What's the checksum supposed to be for the QTMoko files? a76072c1c9dce4eb2b07235f7cc307fe qtmoko-debian-gta02-v58.ubi 50baec96657802b5a053fa0ef6b777a2 uImage.bin-2.6.39-qtmoko-v58 Yup, that's what I'm getting. This is strange - it works for me. Are you using dfu-util or dd to write to the NAND? Are you booting with qi-v58.udfu? Is the tarball ok at least? I tried qi-v58 first then qi-v56 as a test. Neither worked. Haven't tried the tarball; I don't have an SD card handy and (correct me if I'm wrong) there's no way to unpack the tarball onto the NAND unless you've already booted from SD. I notice that v58's .ubi file is 101MiB. This is probably a red-herring, but is there any known problem with crossing the 100MiB threshold? [Oh wait, ignore that, I just checked and v54's .ubi was 142MiB.] —B ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [gta02] cannot boot from NAND
On Fri 13 December 2013 13:25:47 Ben Wong wrote: Are you using dfu-util or dd to write to the NAND? dd to write to NAND? :-o Don't do that! That's prone to fail, since dd can't handle bad blocks, and NAND per definitionem doesn't. That's why you got things like jffs2/ubifs /j -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments (alas the above page got scrapped due to resignation(!!), so here some supplementary links:) http://www.georgedillon.com/web/html_email_is_evil.shtml http://www.nonhtmlmail.org/campaign.html http://www.georgedillon.com/web/html_email_is_evil_still.shtml http://www.gerstbach.at/2004/ascii/ (German) signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [gta02] cannot boot from NAND
On Friday, December 13, 2013 01:25:47 PM Ben Wong wrote: I tried qi-v58 first then qi-v56 as a test. Neither worked. Haven't tried the tarball; I don't have an SD card handy and (correct me if I'm wrong) there's no way to unpack the tarball onto the NAND unless you've already booted from SD. I notice that v58's .ubi file is 101MiB. This is probably a red-herring, but is there any known problem with crossing the 100MiB threshold? [Oh wait, ignore that, I just checked and v54's .ubi was 142MiB.] The size should be ok. NAND is IIRC 256MB. Would you be interested to try jffs2? I can do it and upload quite easily. BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [gta02] cannot boot from NAND
The size should be ok. NAND is IIRC 256MB. Would you be interested to try jffs2? I can do it and upload quite easily. Sure, I'd give that a shot if it's easy for you to do. I seem to have more corruption problems from ubifs than jffs2, so wouldn't mind going back. —B ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [gta02] cannot boot from NAND
Is the tarball ok at least? Tested on the uSD and it is ok ...apart that I'm stuck at the PIN entry screen (that one with just the notice Please wait...) no matter how many times I restart. But from ssh all seems to work well. Joif ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[gta02] cannot boot from NAND
Hello Flashing QtMoko v58 I discovered that I'm not able to boot any more from NAND. This is what I receive after pressing the power button: UBI error: process_eb: bad image sequence number 1588845893 in PEB 1971, epxected 1933142073 slab error in kmem_cache_destroy(): cache `ubi_scan_slab': Can't free all objects UBI error: ubi_init: cannot attach mtd6 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [c002b0f0] (unwind_backtrace+0x0/0xf0) from [c02aba94] (panic+0x58/0x174) [c02aba94] (panic+0x58/0x174) from [c0008cc0] (mount_block_root+0x1d4/0x294) [c0008cc0] (mount_block_root+0x1d4/0x294) from [c0008f6c] (prepare_namespace+0x8c/0x1c8) [c0008f6c] (prepare_namespace+0x8c/0x1c8) from [c00089b4] (kernel_init+0xfc/0x130) [c00089b4] (kernel_init+0xfc/0x130) from [c0027730] (kernel_thread_exit+0x0/0x8) With v55 it seems to boot correctly but the process stops after the first configuration, and rebooting gives just a black screen. With v56 I have similar errors like above. Any hints on what's going on? I'm so sad... Joif ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [gta02] cannot boot from NAND
Hey Joif, You're not alone. I get the same message with v58 in NAND; haven't tried on SD yet. I thought it might be DFU transferring the file system incorrectly, but seeing that you have the same problem, I think perhaps the image on sourceforge is corrupted. What's the checksum supposed to be for the QTMoko files? —B On Thu, Dec 12, 2013 at 1:31 PM, Francesco De Vita francesco.dev...@mailoo.org wrote: Hello Flashing QtMoko v58 I discovered that I'm not able to boot any more from NAND. This is what I receive after pressing the power button: UBI error: process_eb: bad image sequence number 1588845893 in PEB 1971, epxected 1933142073 slab error in kmem_cache_destroy(): cache `ubi_scan_slab': Can't free all objects UBI error: ubi_init: cannot attach mtd6 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [c002b0f0] (unwind_backtrace+0x0/0xf0) from [c02aba94] (panic+0x58/0x174) [c02aba94] (panic+0x58/0x174) from [c0008cc0] (mount_block_root+0x1d4/0x294) [c0008cc0] (mount_block_root+0x1d4/0x294) from [c0008f6c] (prepare_namespace+0x8c/0x1c8) [c0008f6c] (prepare_namespace+0x8c/0x1c8) from [c00089b4] (kernel_init+0xfc/0x130) [c00089b4] (kernel_init+0xfc/0x130) from [c0027730] (kernel_thread_exit+0x0/0x8) With v55 it seems to boot correctly but the process stops after the first configuration, and rebooting gives just a black screen. With v56 I have similar errors like above. Any hints on what's going on? I'm so sad... Joif ___ 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: [gta02] cannot boot from NAND
Yup, same here. No booting from NAND. On 12/12/13 23:59, Ben Wong wrote: Hey Joif, You're not alone. I get the same message with v58 in NAND; haven't tried on SD yet. I thought it might be DFU transferring the file system incorrectly, but seeing that you have the same problem, I think perhaps the image on sourceforge is corrupted. What's the checksum supposed to be for the QTMoko files? —B On Thu, Dec 12, 2013 at 1:31 PM, Francesco De Vita francesco.dev...@mailoo.org wrote: Hello Flashing QtMoko v58 I discovered that I'm not able to boot any more from NAND. This is what I receive after pressing the power button: UBI error: process_eb: bad image sequence number 1588845893 in PEB 1971, epxected 1933142073 slab error in kmem_cache_destroy(): cache `ubi_scan_slab': Can't free all objects UBI error: ubi_init: cannot attach mtd6 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [c002b0f0] (unwind_backtrace+0x0/0xf0) from [c02aba94] (panic+0x58/0x174) [c02aba94] (panic+0x58/0x174) from [c0008cc0] (mount_block_root+0x1d4/0x294) [c0008cc0] (mount_block_root+0x1d4/0x294) from [c0008f6c] (prepare_namespace+0x8c/0x1c8) [c0008f6c] (prepare_namespace+0x8c/0x1c8) from [c00089b4] (kernel_init+0xfc/0x130) [c00089b4] (kernel_init+0xfc/0x130) from [c0027730] (kernel_thread_exit+0x0/0x8) With v55 it seems to boot correctly but the process stops after the first configuration, and rebooting gives just a black screen. With v56 I have similar errors like above. Any hints on what's going on? I'm so sad... Joif ___ 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: [gta02] cannot boot from NAND
This is my main phone, so I've reverted to v55 (the latest one I could find on sourceforge) and it seems to be working. —B On Thu, Dec 12, 2013 at 6:29 PM, Jorge xxo...@gmail.com wrote: Yup, same here. No booting from NAND. On 12/12/13 23:59, Ben Wong wrote: Hey Joif, You're not alone. I get the same message with v58 in NAND; haven't tried on SD yet. I thought it might be DFU transferring the file system incorrectly, but seeing that you have the same problem, I think perhaps the image on sourceforge is corrupted. What's the checksum supposed to be for the QTMoko files? —B On Thu, Dec 12, 2013 at 1:31 PM, Francesco De Vita francesco.dev...@mailoo.org wrote: Hello Flashing QtMoko v58 I discovered that I'm not able to boot any more from NAND. This is what I receive after pressing the power button: UBI error: process_eb: bad image sequence number 1588845893 in PEB 1971, epxected 1933142073 slab error in kmem_cache_destroy(): cache `ubi_scan_slab': Can't free all objects UBI error: ubi_init: cannot attach mtd6 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [c002b0f0] (unwind_backtrace+0x0/0xf0) from [c02aba94] (panic+0x58/0x174) [c02aba94] (panic+0x58/0x174) from [c0008cc0] (mount_block_root+0x1d4/0x294) [c0008cc0] (mount_block_root+0x1d4/0x294) from [c0008f6c] (prepare_namespace+0x8c/0x1c8) [c0008f6c] (prepare_namespace+0x8c/0x1c8) from [c00089b4] (kernel_init+0xfc/0x130) [c00089b4] (kernel_init+0xfc/0x130) from [c0027730] (kernel_thread_exit+0x0/0x8) With v55 it seems to boot correctly but the process stops after the first configuration, and rebooting gives just a black screen. With v56 I have similar errors like above. Any hints on what's going on? I'm so sad... Joif ___ 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: [gta02] cannot boot from NAND
On Friday, December 13, 2013 02:59:01 AM Ben Wong wrote: Hey Joif, You're not alone. I get the same message with v58 in NAND; haven't tried on SD yet. I thought it might be DFU transferring the file system incorrectly, but seeing that you have the same problem, I think perhaps the image on sourceforge is corrupted. What's the checksum supposed to be for the QTMoko files? 882cc204627226ffefda4e446fae3862 qtmoko-debian-gta02-v58.tar.gz a76072c1c9dce4eb2b07235f7cc307fe qtmoko-debian-gta02-v58.ubi 50baec96657802b5a053fa0ef6b777a2 uImage.bin-2.6.39-qtmoko-v58 The checksums look ok on SF. This is strange - it works for me. Are you booting with qi-v58.udfu? Is the tarball ok at least? Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
