Re: QtMoko v31
Hi, I would like to use the new QtMoko v31 as my Dailly-Phone on NAND parallel to two other Distros and a big Documents-Partition on my SD-Card. Till v26 I could boot QtMoko over U-Boot 1.3.2-moko 12 (AUX + Power) and the other two over Qi (Power with or without AUX). With the new v31 this is no longer possible: When I try to boot v31 with U-Boot, I get the Message No kernel Image (or similar, the message shows only very short befor the U-Boot-Menu shows up again). From the Discussion around v28 I have learned, that I have to change the bootargs_base to use the new ubifs. I think, I have done this right (with the parameters from v28) but with no success. When I remove my SD-Card I can boot to v31 (with the new Qi). Please tell me the right parameters for U-Boot to use with v31 (and maybe the right way to set them, when I'm logged into U-Boot? - sorry for this NOOB-Question...), or what else could be wrong? Thanks in advance Sferic -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/QtMoko-v31-tp5881425p5898831.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: QtMoko v31
On Fri, 7 Jan 2011, sferic wrote: Hi, I would like to use the new QtMoko v31 as my Dailly-Phone on NAND parallel to two other Distros and a big Documents-Partition on my SD-Card. Till v26 I could boot QtMoko over U-Boot 1.3.2-moko 12 (AUX + Power) and the other two over Qi (Power with or without AUX). With the new v31 this is no longer possible: When I try to boot v31 with U-Boot, I get the Message No kernel Image (or similar, the message shows only very short befor the U-Boot-Menu shows up again). From the Discussion around v28 I have learned, that I have to change the bootargs_base to use the new ubifs. I think, I have done this right (with the parameters from v28) but with no success. When I remove my SD-Card I can boot to v31 (with the new Qi). Please tell me the right parameters for U-Boot to use with v31 (and maybe the right way to set them, when I'm logged into U-Boot? - sorry for this NOOB-Question...), or what else could be wrong? Thanks in advance Sferic I have exactly the same problem. But I even cannot boot into Qt without sdCard. Holding power longer prints some debug messages and the reason is, that the ubifs could not be mounted. The funny thing is, that it worked on another phone with the same set-up. The only difference I found is the 'pcb_rev=0x001' environment setting of u-boot... Alex. -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/QtMoko-v31-tp5881425p5898831.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: gestures (on SHR)
I can't seem to get past the initial make the gesture after selecting a model and pressing the train button. I've the same issue. Should the frontend still function as described in the wiki? I started looking into the underlying scripts, but haven't found the start or end yet. The library is still under heavy construction all the time... ??? The program for the gestures is named accelges and it's rather the contrary,and it seem that that program is not mained anymore. It would be nice to have it working again. Denis. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: gestures (on SHR)
The program for the gestures is named accelges and it's rather the contrary,and it seem that that program is not mained anymore. Oh. I was more thinking about fso-glib and so on, which has recently become broken because of so much tinkering.. It would be nice to have it working again. Dito Denis. lev 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: QtMoko v31
sferic wrote: I would like to use the new QtMoko v31 as my Dailly-Phone on NAND parallel to two other Distros and a big Documents-Partition on my SD-Card. Till v26 I could boot QtMoko over U-Boot 1.3.2-moko 12 (AUX + Power) and the other two over Qi (Power with or without AUX). With the new v31 this is no longer possible The problem is that qtmoko kernel image is now larger then 2MB uboot limit. And it is also recommended to not use uboot from NOR for booting the phone. I dont know the details, but NOR uboot loader was said to be bugged and you will also get worse performance then with qi from qtmoko download page (because of glamo 242 timings). I am afraid that nobody will try to solve problem with old uboot that cant be reflashed, this uboot is only good for dfu-util flashing. You can try new uboot that is maintained by Gennady, it should work good: http://wiki.openmoko.org/wiki/U-boot-gena2x or you can keep with qi and try switching partitions with AUX (which is quite tricky but works). Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31
В Птн, 07/01/2011 в 03:16 -0800, sferic пишет: Hi, I would like to use the new QtMoko v31 as my Dailly-Phone on NAND parallel to two other Distros and a big Documents-Partition on my SD-Card. Till v26 I could boot QtMoko over U-Boot 1.3.2-moko 12 (AUX + Power) and the other two over Qi (Power with or without AUX). With the new v31 this is no longer possible: When I try to boot v31 with U-Boot, I get the Message No kernel Image (or similar, the message shows only very short befor the U-Boot-Menu shows up again). From the Discussion around v28 I have learned, that I have to change the bootargs_base to use the new ubifs. I think, I have done this right (with the parameters from v28) but with no success. When I remove my SD-Card I can boot to v31 (with the new Qi). Please tell me the right parameters for U-Boot to use with v31 (and maybe the right way to set them, when I'm logged into U-Boot? - sorry for this NOOB-Question...), or what else could be wrong? Thanks in advance Sferic Hi, you should never use NOR u-boot for anything expect dfu-flashing. Reason: bootloader is important because it inits hw on boot and on resume. for example according to my measurements power consumption in suspend with nor-uboot is much higher. some things are really not controlled by kernel: bootloader inits something and kernel uses as it were init (many such things, any serial line is example). This may cause any kind of problems, which you'll never notice on first glance - power consumption, memory timings, anything else. If you really like u-boot, just flash it to nand and enjoy (i am maintaining working version http://wiki.openmoko.org/wiki/U-boot-gena2x ), it should work with all qtmokos or other distros. It is realatively easy to reflash nor u-boot btw. Gennady ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: bugs QtMoko v31
2011-01...@18:07 Radek Polak - I'm no longer able to connect to wifi and while I try I see console messages over the framebuffer graphic screen - gprs does not connect too No longer means that in v30 it worked? I dont see any messages and my wifi connects. Maybe we have different setup? Do you use qi or uboot? I have tested both gprs and wifi and it works, also it works for others. We have to find out what is wrong. Please give as much details as possible. sorry, with wifi I was out of the covered range due of interferences from a cordless phone near the antenna: in other words it's ok! btw I do see console messages through the framebuffer screen (like white terminal line over the graphic gui) every time I enable/disable the wifi connection. maybe it's related to the vt switch? about the gprs the problem is the multiplexer: when it's enabled it's not possible to use the gprs data connection. when you turn off the multiplexer it's ok but it's highly probable to loose sms or calls. - the long awaited rollback for the power profile when locked is still on the to-do list I was trying to look at it and at first sight i havent found what is wrong. I have to find the discussion we had last time to refresh my memory. the culprit is the on lock scenario because all the profiles (general, silent, meeting...etc) could support different power management properties each, but maybe the saved array does not take in account a third choice other than on cable and on battery and so begin the chaos both in the gui and in the actual values used in memory. by now it'd be safe to rollback to the original state and forget about the on lock buggy feature. we can achieve the same feature just configuring ad-hoc different profiles. the current implementation has too much negative side effects. - if you put qtmoko on uSD you cannot use the usb-storage because /opt/qtmoko/bin/usb-mass-storage-on.sh tries to use (and unmount) the whole uSD instead of a single partition and the root with qtmoko is on the same device Any ideas how to solve this? I sent to you an early suggested workaround: in the current on script you have to specify a single partition instead of the whole uSD eg: my current partition table is mmcblk0p1=/media/card (fat32 used as usb storage), p2=/ (qtmoko root), p3=swap (little extra memory). in the script I've specified to use only p1 and commented out / modified all the mount checks because they works only with a whole device in mind. I'm not saying this is a nice solution but at least it does not destroy your qtmoko/root filesystem! (-dangerous only if you have qtmoko on uSD too) kind regards and good year to all folks! -- ALFA21 IS PROVIDED AS IS AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Freerunner doesn't boot properly after upgrading to QtMoko v31
Hi, I've been running QtMoko v26 from my uSD card (Kingston) more or less successfully. I wanted to upgrade to v31, so I added the qtmoko repository as per the instructions on the wiki, did an apt-get update and apt-get dist-upgrade. When I rebooted the phone, I get only a terminal login prompt. My dmesg log is attached. I noticed some glamo errors: [21474538.175000] glamo-mci glamo-mci.0: Error after cmd: 0x8120 [21474538.175000] glamo-mci glamo-mci.0: Error after cmd: 0x120 [21474538.175000] glamo-mci glamo-mci.0: Error after cmd: 0x8120 [21474538.175000] glamo-mci glamo-mci.0: Error after cmd: 0x120 So I tried changing the settings in the max_sd_clk file, and also tried the qi-31.udfu bootloader from the QtMoko Downloads, but neither seemed to make any difference. I found one message suggesting that the errors indicate the SD card is not inserted properly, so I removed and reinstalled it a number of times. It seems to me that if it's not installed properly, I get a kernel panic almost immediately, with an error message about not being able to sync the rootfs or something. What else can I try to get QtMoko up and running again without doing a fresh install? Thanks, Bernie [0.00] Linux version 2.6.29-rc3-v26 (ra...@rp-skunk) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 Sat Aug 28 13:11:14 CEST 2010 [0.00] CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177 [0.00] CPU: VIVT data cache, VIVT instruction cache [0.00] Machine: GTA02 [0.00] Memory policy: ECC disabled, Data cache writeback [0.00] On node 0 totalpages: 32768 [0.00] free_area_init_node: node 0, pgdat c03b3dc4, node_mem_map c0413000 [0.00] Normal zone: 256 pages used for memmap [0.00] Normal zone: 0 pages reserved [0.00] Normal zone: 32512 pages, LIFO batch:7 [0.00] CPU S3C2442B (id 0x32440aab) [0.00] S3C24XX Clocks, (c) 2004 Simtec Electronics [0.00] S3C244X: core 400.000 MHz, memory 100.000 MHz, peripheral 50.000 MHz [0.00] CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 [0.00] Kernel command line: loglevel=4 console=tty0 console=ttySAC2,115200 init=/sbin/init ro mtdparts=physmap-flash:-(nor);neo1973-nand:0x0004(qi),0x0004(depr-ub-env),0x0080(kernel),0x000a(depr),0x0004(identity-ext2),0x0f6a(rootfs) g_ether.host_addr=00:1F:11:01:A1:E3 g_ether.dev_addr=00:1F:11:01:A1:E3 root=/dev/mmcblk0p1 rootdelay=1 console=tty0 loglevel=3 rootdelay=1 [0.00] Unknown boot option `g_ether.host_addr=00:1F:11:01:A1:E3': ignoring [0.00] Unknown boot option `g_ether.dev_addr=00:1F:11:01:A1:E3': ignoring [0.00] RCU-based detection of stalled CPUs is enabled. [0.00] irq: clearing pending ext status 000b12f0 [0.00] irq: clearing pending ext status 000902d0 [0.00] irq: clearing subpending status 0180 [0.00] irq: clearing subpending status 0080 [0.00] PID hash table entries: 512 (order: 9, 2048 bytes) [0.00] timer tcon=, tcnt a2c1, tcfg 0200,, usec 1eb8 [21474536.48] Console: colour dummy device 80x30 [21474536.48] console [tty0] enabled [21474536.48] console [ttySAC2] enabled [21474536.48] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [21474536.48] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) [21474536.495000] Memory: 128MB = 128MB total [21474536.495000] Memory: 125624KB available (3456K code, 533K data, 140K init) [21474536.495000] Calibrating delay loop... 199.47 BogoMIPS (lpj=498688) [21474536.595000] Mount-cache hash table entries: 512 [21474536.595000] CPU: Testing write buffer coherency: ok [21474536.60] net_namespace: 936 bytes [21474536.605000] regulator: core version 0.5 [21474536.605000] NET: Registered protocol family 16 [21474536.63] S3C Power Management, Copyright 2004 Simtec Electronics [21474536.63] modem wakeup interrupt [21474536.63] wake enabled for irq 17 [21474536.63] wake enabled for irq 49 [21474536.64] s3c24xx-adc s3c24xx-adc: attached adc driver [21474536.645000] S3C2442: Initialising architecture [21474536.645000] S3C24XX DMA Driver, (c) 2003-2004,2006 Simtec Electronics [21474536.645000] DMA channel 0 at c8808000, irq 33 [21474536.645000] DMA channel 1 at c8808040, irq 34 [21474536.645000] DMA channel 2 at c8808080, irq 35 [21474536.645000] DMA channel 3 at c88080c0, irq 36 [21474536.645000] S3C244X: Clock Support, DVS off [21474536.72] bio: create slab bio-0 at 0 [21474536.73] usbcore: registered new interface driver usbfs [21474536.73] usbcore: registered new interface driver hub [21474536.73] usbcore: registered new device driver usb [21474536.78] NET: Registered protocol family 2 [21474536.835000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes) [21474536.835000]
