Andy Green wrote:
[...]
Hey don't lose hope. There are two issues. First is just some big
cards are too slow to respond at default 16MHz clock with Glamo 16-bit
clock count timeout counter. See this
https://docs.openmoko.org/trac/ticket/1743
Suspend / resume (partition overwrite is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| i played with it a bit and came to the conclusion that it eats exactly
| 1024byte from the beginning of the 'physical' blockdevice. atleast when
| i backup these to nand, write them back via dd after
Alle 01:16, sabato 26 luglio 2008, Thomas B. ha scritto:
On Fri, Jul 25, 2008 at 11:44:37PM +0200, AVee wrote:
On Friday 25 July 2008 10:54, arne anka wrote:
i got a 4 gig card too (can't say if from intenso, have to check the
wrapping).
my card's boot sector is not erased but -- after
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andrew Burgess said (on the OLPC bug tracker):
|
| ...For me the SD card corruption is 100% fixed now. I run a swap to the
| first sd card partition and I could guarantee partition wipe by turning
| off
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| With all ext2 partitions, I get this in dmesg
|
| FAT: bogus number of reserved sectors
| VFS: Can't find a valid FAT filesystem on dev mmcblk0.
| FAT: bogus number of reserved sectors
| VFS: Can't find a
Joerg Reisenweber wrote:
snip
As I think this seems to be quite a good clue to what's really happening here,
quote from the OLPC ticket #6532:
snip
Yes, anybody working on this issue really ought to read that ticket in
its entirety:
http://dev.laptop.org/ticket/6532
(keeping in mind that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| As I think this seems to be quite a good clue to what's really
happening here,
| quote from the OLPC ticket #6532:
| (HTH)
| cc dilinger added
| I've spend some time digging deep into the bowels of the
i had the same problem here, with sandisk 8gb sdhc class 4 using ext2
partition. partition table was completley deleted :(
hope this gets fixed soon.
--
View this message in context:
http://n2.nabble.com/strange-problem-with-Intenso-4GB-SDHC-card-tp579169p584908.html
Sent from the Openmoko
David Meder-Marouelli [EMAIL PROTECTED] writes:
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
thewtex [EMAIL PROTECTED] writes:
David Meder-Marouelli [EMAIL PROTECTED] writes:
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
i got a 4 gig card too (can't say if from intenso, have to check the
wrapping).
my card's boot sector is not erased but -- after a resume the card is
mounted wrongly!
fstab says as mountpoint /media/card and after booting that's where the
card is.
after suspend/resume the card (often) is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| i got a 4 gig card too (can't say if from intenso, have to check the
| wrapping).
| my card's boot sector is not erased but -- after a resume the card is
| mounted wrongly!
|
| fstab says as mountpoint
This is definitely the signature of the old MMC resume problems, not
anything else.
oh, ok. thought it to be related to the wiped out boot sector and thus
maybe helpful.
I am deep down that mine at the minute, this is getting intensely looked
at.
is there a workaround for the time
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| This is definitely the signature of the old MMC resume problems, not
| anything else.
|
| oh, ok. thought it to be related to the wiped out boot sector and thus
| maybe helpful.
It can be related, I expect
btw: just checked and the default _device_ ist mmcblk0p1, after resume it
disappears and instead there is mmcblk1p1.
dunno if it is news to you ...
___
Openmoko community mailing list
community@lists.openmoko.org
well, the card is a kingston 4gb class 4.
yesterday i downloaded a map with tangogps and meanwhile the fr went to
suspend. afterwards a few directories were misisng.
trying
ls /media/card/Maps/om/adirectorynotthere/
gives errors (something w/ read access i think)
so i decided to delete the
On Friday 25 July 2008 10:54, arne anka wrote:
i got a 4 gig card too (can't say if from intenso, have to check the
wrapping).
my card's boot sector is not erased but -- after a resume the card is
mounted wrongly!
fstab says as mountpoint /media/card and after booting that's where the
card
On Fri, Jul 25, 2008 at 11:44:37PM +0200, AVee wrote:
On Friday 25 July 2008 10:54, arne anka wrote:
i got a 4 gig card too (can't say if from intenso, have to check the
wrapping).
my card's boot sector is not erased but -- after a resume the card is
mounted wrongly!
fstab says as
Am Do 24. Juli 2008 schrieb Andy Green:
Somebody in the thread at some point said:
| 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
Mikael Berthe wrote:
* Doug Jones [EMAIL PROTECTED] [2008-07-24 01:21 +0200]:
There have been some indications that partition type may have some
effect on this problem on the OLPC.
I doubt it.
So, shrink the default vfat partition that came on the card and put
an ext3 on there too. If
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
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| 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
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:
Hi David,
After the the card settles (see above in this thread), i can do the
following:
1) fdisk -l /dev/mmcblk0
Result: error
...
No matter how often I call this, it never changes as the MBR is
completely zeroed out.
To re-ead the partition table just start fdisk /dev/mmcblk0, verify
Hi Andy,
sd_drive setting isn't actually used until next time we access the card,
so provoking an access will do it, eg, touch /something ; sync.
Good point, but now it is getting really strange (all with sd_drive=0
prior to suspend):
Adding a touch /media/mmcblk0p4/suspending and it works,
I experienced the same issue with my card (also the A-Data 8GB) after
flashing the kernel and rootfs builds from the 22nd. My partition
table seems to have been deleted. I'm pretty sure it happened after a
suspend/resume cycle (what happens when you have power management set
to dim first, then
Does anyone know an equivalent tool for Linux?
fdisk just says unable to open. So, I can't even re-write the data
to the card. It's just dead!
-Steven
On Wed, Jul 23, 2008 at 4:15 PM, Stefan Fröbe [EMAIL PROTECTED] wrote:
Hi,
just a quick observation from my side that could possibly be
Nevermind. Gparted could read it.
-Steven
On Thu, Jul 24, 2008 at 6:37 PM, Steven ** [EMAIL PROTECTED] wrote:
Does anyone know an equivalent tool for Linux?
fdisk just says unable to open. So, I can't even re-write the data
to the card. It's just dead!
-Steven
On Wed, Jul 23, 2008 at
On Thursday 24 July 2008 08:39, Doug Jones wrote:
Mikael Berthe wrote:
* Doug Jones [EMAIL PROTECTED] [2008-07-24 01:21 +0200]:
There have been some indications that partition type may have some
effect on this problem on the OLPC.
I doubt it.
So, shrink the default vfat partition
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| 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
Hi Andy,
thanks for the quick reply.
Andy Green schrieb:
| mmc0: new high speed SDHC card at address b368
| mmcblk0: mmc0:b368 SD3931136KiB
| mmcblk0:6glamo-mci glamo-mci.0: Error after cmd: 0x8310
| mmcblk0: error -110 sending read/write command
This first real error is ETIMEDOUT.
Hi,
just a quick observation from my side that could possibly be related:
Until yesterday, my 4GB SanDisk card worked fine with a recent (e.g.
2008-07-22 or 21) kernel - after an opkg upgrade this morning that got me a
new kernel I was surprised to see the card not beeing recognized anymore -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi,
|
| just a quick observation from my side that could possibly be related:
| Until yesterday, my 4GB SanDisk card worked fine with a recent (e.g.
| 2008-07-22 or 21) kernel - after an opkg upgrade this
Stefan Fröbe wrote:
Hi,
just a quick observation from my side that could possibly be related:
Until yesterday, my 4GB SanDisk card worked fine with a recent (e.g.
2008-07-22 or 21) kernel - after an opkg upgrade this morning that got
me a new kernel I was surprised to see the card not
Andy Green wrote:
There's a race of some kind in suspend / resume that can do this, the
signature effect of it is on resume your device comes back as mmcblk1
and the logical filesystem in memory is corrupted. We didn't see this
for a long time though. Maybe keep an eye out for such
Thanks for the link, seems to be quite valuable to me as it explains the
background quite well!
Something similar has been happening with SD cards on the OLPC laptop
(another example of hardware specifically designed for the FOSS world)
for at least the last six months. Last time I checked,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Thanks for the link, seems to be quite valuable to me as it explains the
| background quite well!
|
| Something similar has been happening with SD cards on the OLPC laptop
| (another example of
Stefan Fröbe wrote:
Thanks for the link, seems to be quite valuable to me as it explains the
background quite well!
Something similar has been happening with SD cards on the OLPC laptop
(another example of hardware specifically designed for the FOSS world)
for at least the last
* Doug Jones [EMAIL PROTECTED] [2008-07-24 01:21 +0200]:
There have been some indications that partition type may have some
effect on this problem on the OLPC.
I doubt it.
So, shrink the default vfat partition that came on the card and put
an ext3 on there too. If you want to be
41 matches
Mail list logo
