-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 loosin
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
Perhaps this will help until Andy gets the new kernel ready.
I had vanishing partition table problems on my OLPC XO (fixed now in
kernel 2.6.25). I found that I could avoid data loss by doing two
things:
1) create a swap partition as the first partition.
2) when the table vanishes, recreate it EXA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| yes i am loosing my partition table every couple of day. very annoying! i
| cant trust anymore my data beeing secure on the openmoko.
|
| i have a sandisk 8gb class4 sdhc card with one ext3 partition.
|
| i
yes i am loosing my partition table every couple of day. very annoying! i
cant trust anymore my data beeing secure on the openmoko.
i have a sandisk 8gb class4 sdhc card with one ext3 partition.
i hope there will be a fix soon, but i'm loosing hope :(
--
View this message in context:
http:/
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 b
-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 v
-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 pow
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
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
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 Comm
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 power or shutting down with swap on. I could work around it 100% by
running swapoff before power do
-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 VFS
Joerg Reisenweber wrote:
> As I think this seems to be quite a good clue to what's really happening here,
> quote from the OLPC ticket #6532:
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 some o
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
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
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
>
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 entire
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
http://lists.openmoko.org/mailman/listi
-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 expec
> 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 be
-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 /medi
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 mou
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 defaul
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,
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 b
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 l
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,
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",
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: corre
-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
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
> 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 syst
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 th
* 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 ad
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
-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 hardw
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, t
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 shenan
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 no
-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 mo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| 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 aft
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 -
furt
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 ETIMED
-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 gl
45 matches
Mail list logo
