On Wednesday 01 September 2010, Joachim Ott wrote: > On 31 August 2010 19:15, Jakob <[email protected]> wrote: > > On 8/4/10, Joachim Ott <[email protected]> wrote: > >> On 3 August 2010 20:58, <[email protected]> wrote: > >>> 03.08.2010 14:57, David Garabana Barro пишет: > >>>> It was related to uboot. > >>>> I flashed qi, and now I get a fix after suspending with no problem. > >>> > >>> This is weird. > >>> What u-boot have to do with gps or any other subsystem for that matter? > >>> Are you sure about this? > >> > >> One difference between uboot and qi is that qi doesn't initialize the > >> display. The problem with gps and suspending also occurs on my older > >> image from June 28, with upgrades until today and 2.6.32.16. > >> _______________________________________________ > >> Shr-User mailing list > >> [email protected] > >> http://lists.shr-project.org/mailman/listinfo/shr-user > > > > Has anyone looked into this problem? > > Still no gps after a suspend with uboot. Or is everyone using qi these > > days? > > We must be the only two using u-boot.
I have both (2 FRs), but u-boot is usually starting an old shr-u that's been unable to update since it lost its package list, but is otherwise surprisingly good. I don't have any unusual gps problems with it. I'll try sticking a current shr-u on a partition to see if the gps behaves any differently. > I suspend very seldom, maybe > once in a month and therefore the gps failure doesn't appear on my FR > (and I don't use gps very much currently). But it still occurs with > 2.6.32.21. I'm trying to find out again. I can't really believe that > the bootloader make such a difference. I don't expect the bootloader to make a difference either. I have had occasions with current shr-u and qi where I have failed to get a fix quickly, given up and closed the app, removed the agps data and restarted the app, and got a fix quickly. It usually happens when I'm out walking somewhere with a poorish sky view somewhere unsuitable for debugging... > Can someone with Qi show me the > value of his /proc/cmdline? With my u-boot it is this: > > rootfstype=jffs2 root=/dev/mtdblock6 console=ttySAC2,115200 > console=tty0 loglevel=4 regular_boot > mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(u-boot),0x00040000(u- > boot_env),0x00800000(kernel),0x000a0000(splash),0x00040000(factory),0x0f6a0 > 000(rootfs) r...@om-gta02 ~ # cat /proc/cmdline loglevel=4 console=tty0 console=ttySAC2,115200 init=/sbin/init ro mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(qi),0x00040000(depr-ub- env),0x00800000(kernel),0x000a0000(depr),0x00040000(identity- ext2),0x0f6a0000(rootfs) root=/dev/mmcblk0p1 rootdelay=1 loglevel=1 quiet splash r...@om-gta02 ~ # cat /boot/append-GTA02 loglevel=1 quiet splash _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
