Re: Tangogps pre-cache?

[David Meder-Marouelli]

Hi Arne,

I just tried it and it looks like all data is cached.

Cheers, David

arne anka schrieb:
> btw: does anyone know if the tiles are persistently named, ie if i move  
> the clip slightly will _all_ tiles be downloaded again? or just the new  
> ones?
>
> ___
> 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: strange problem with Intenso 4GB SDHC card

[David Meder-Marouelli]

Hi Stefan,

maybe it turn out to be the same problem that I also have.

After the the card settles (see above in this thread), i can do the
following:

1) fdisk -l /dev/mmcblk0
Result: error
2) fdisk -l /dev/mmcblk0
Result: empty partition table!!!
3) fdisk -l /dev/mmcblk0
Result: correct full partition table!!!

[Note: nothing else changed in between]

To re-ead the partition table just start "fdisk /dev/mmcblk0", verify
that partition table is ok with "p", re-write unaltered partition table
with "w". After that it's re-read by the kernel and the Frerunner
recognises it.

Cheers,

David

Stefan Fröbe schrieb:
> Hi all,
>
> I can now reliably reproduce the issue, as dd'ing the mbr back to the
> card so far restores sane behaviour :
>
> If sd_drive is set to "0", then after a resume from "sync && apm -s"
> the MBR of my 4GB SanDisk is wiped - so far I haven't noticed any
> other errors, but have not looked very closely.
>
> To recover, I use the following commands:
> ---
> # re-write MBR
> dd if=mmcblk0_512_1.dump of=/dev/mmcblk0
> # recognize partitions again
> echo "1">/sys/module/glamo_mci/parameters/sd_drive
> apm -s
> 
>
> So it looks as if the sd_drive parameter does have a role in this -
> any suggestions on what else I should try, or what logs you guys need ?
>
> Unmounting the card before suspend should help, and I'll also gladly
> try another kernel and other partitions setup if I find the time.
>
> Btw, this all happens on a 4GB SanDisk with 4 primary partitions:
> 20M vfat + (196M +196M +3.2G ) ext2 and kernel om-gta02 2.6.24 Wed Jul
> 23 06:34:19
>
> Stefan
>
> PS: Can somebody please tell me how to re-initialize the card without
> going through another suspend/resume cycle ?
>
>
>
>
> On Thu, Jul 24, 2008 at 9:53 AM, arne anka <[EMAIL PROTECTED]
> > wrote:
>
> > Everybody, get a Micro-SD card and stick it in your Neo.  Put some
>
> should that apply to multiboot or to _every_ use of the sd card?
> i use suspend/resume more or less successfully for a week or 10
> days now
> and the files on my sd card (4gb, how do i determine the exact
> name from a
> running system?) still are unharmed.
> gta02, 2007.2, upgrade every or every second day.
>
> ___
> 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: strange problem with Intenso 4GB SDHC card

[David Meder-Marouelli]

Hi Andy,

thanks for the quick reply.

Andy Green schrieb:
> | mmc0: new high speed SDHC card at address b368
> | mmcblk0: mmc0:b368 SD3931136KiB
> |  mmcblk0:<6>glamo-mci glamo-mci.0: Error after cmd: 0x8310
> | mmcblk0: error -110 sending read/write command
>
> This first real error is ETIMEDOUT.  It can be a genuine timeout because
> your card is a bit slow, but it could also mean communication problems.
Not really good timing would probably be a good guess since "Intenso" is
a low cost brand around here (germany).

> | 2) I can trick it to work doing the following steps:
> |- re-set it to this (or possibly any other) value
> |  >[EMAIL PROTECTED]:~# echo 0 >
> /sys/module/glamo_mci/parameters/sd_drive
Thanks for your guidance. It's _not_ the sd_drive parameter.

It's actually just waiting for about 1-2min. After that the device is
readily accessible. (Need to force a re-read of the partition table to
mount though.)

Anyways I made sure that the data I wrote to the card yesterday is still
OK (md5sum) - although it's only around 1MB. I can do more tests tomorrow...

Cheers,

David



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

strange problem with Intenso 4GB SDHC card

[David Meder-Marouelli]

Hi,

I observed an interesting phenomenon with my newly bought Intenso 4GB
SDHC card.

While the 512MB card shipped with my Freerunner runs reliably and stable
the new card shows the following behaviour:

1) Errors during boot process:

[EMAIL PROTECTED]:~# dmesg |grep -E "glamo|mmc"
glamo3362 glamo3362.0: Detected Glamo core 3650 Revision 0002
(49119232Hz CPU / 81887232Hz Memory)
glamo3362 glamo3362.0: Glamo core now 49119232Hz CPU / 81887232Hz Memory)
glamo-spi-gpio glamo-spi-gpio.0: registering c0373838: jbt6k74
glamo-mci glamo-mci.0: glamo_mci driver (C)2007 Openmoko, Inc
glamo-mci glamo-mci.0: probe: mapped mci_base:c8864400 irq:0.
glamo-mci glamo-mci.0: glamo_mci_set_ios: power down.
glamo-mci glamo-mci.0: initialisation done.
mmc_set_power(power_mode=1, vdd=20
glamo-mci glamo-mci.0: powered (vdd = 20) clk: 0kHz div=255 (req: 0kHz).
Bus width=0
glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req:
195kHz). Bus width=0
glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req:
195kHz). Bus width=0
glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req:
195kHz). Bus width=0
glamo-mci glamo-mci.0: Error after cmd: 0x120
glamo-mci glamo-mci.0: Error after cmd: 0x8120
glamo-mci glamo-mci.0: Error after cmd: 0x120
glamo-mci glamo-mci.0: Error after cmd: 0x8120
glamo-mci glamo-mci.0: Error after cmd: 0x120
glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req:
195kHz). Bus width=0
glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req:
195kHz). Bus width=0
glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req:
195kHz). Bus width=0
glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req:
195kHz). Bus width=0
glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req:
195kHz). Bus width=0
glamo-mci glamo-mci.0: powered (vdd = 20) clk: 1kHz div=2 (req:
1kHz). Bus width=0
glamo-mci glamo-mci.0: powered (vdd = 20) clk: 1kHz div=2 (req:
1kHz). Bus width=2
mmc0: new high speed SDHC card at address b368
mmcblk0: mmc0:b368 SD3931136KiB
 mmcblk0:<6>glamo-mci glamo-mci.0: Error after cmd: 0x8310
mmcblk0: error -110 sending read/write command
end_request: I/O error, dev mmcblk0, sector 0
Buffer I/O error on device mmcblk0, logical block 0
glamo-mci glamo-mci.0: Error after cmd: 0x120
glamo-mci glamo-mci.0: Error after cmd: 0x122
mmcblk0: error -84 sending read/write command

[many more of the last few lines following]

2) I can trick it to work doing the following steps:
   - check sd_drive parameter (not required)
 >[EMAIL PROTECTED]:~# cat /sys/module/glamo_mci/parameters/sd_drive
 >0
   - re-set it to this (or possibly any other) value
 >[EMAIL PROTECTED]:~# echo 0 > /sys/module/glamo_mci/parameters/sd_drive
   - now the device works fine:
 >[EMAIL PROTECTED]:~# fdisk -l /dev/mmcblk0

Disk /dev/mmcblk0: 4025 MB, 4025483264 bytes
126 heads, 61 sectors/track, 1022 cylinders
Units = cylinders of 7686 * 512 = 3935232 bytes

Device Boot  Start End  Blocks  Id System
/dev/mmcblk0p1   11022 3927515+ 83 Linux
==

A suspend/resume cycle seems to do the trick as well.
I think that some parameter connected to sd_drive might be uninitialised
before sd_drive is explicitly rewritten.

Any ideas?

Cheers,

David



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