On Tuesday 15 March 2011 01:29:19 John Watlington wrote:
On Mar 14, 2011, at 3:18 PM, Arnd Bergmann wrote:
Another effect is that the page size has increased by a factor of 8,
from 2 or 4 KB to 16 or 32 KB. Writing data that as smaller than
a page is more likely to get you into the worst
On Sunday 13 March 2011, Mikus Grinbergs wrote:
The tests have also helped expose other issues with things like sudden
power off. In one case a SPO during a write would corrupt the card so
badly it became useless. You could only recover them via a super secret
tool from the
On 03/13/2011 06:34 PM, Mikus Grinbergs wrote:
The tests have also helped expose other issues with things like sudden
power off. In one case a SPO during a write would corrupt the card so
badly it became useless. You could only recover them via a super secret
tool from the manufacturer.
Is
On Sunday 13 March 2011, Richard A. Smith wrote:
On 03/13/2011 01:21 PM, Arnd Bergmann wrote:
There's a 2nd round of test(s) that runs during the manufacturing and
burn-in phases. One is a simple firmware test to see if you can talk the
card at all and then one runs at burn in. It doesn't
On Mar 13, 2011, at 6:34 PM, Mikus Grinbergs wrote:
The tests have also helped expose other issues with things like sudden
power off. In one case a SPO during a write would corrupt the card so
badly it became useless. You could only recover them via a super secret
tool from the
On Monday 14 March 2011 19:50:27 John Watlington wrote:
Cards that are in the state you describe are most likely dead due to
running out of spare blocks. There is nothing that can be done to
rehabilitate them, even using the manufacturer's secret code.
In a disturbing trend, most of the
On Mar 14, 2011, at 3:18 PM, Arnd Bergmann wrote:
On Monday 14 March 2011 19:50:27 John Watlington wrote:
Cards that are in the state you describe are most likely dead due to
running out of spare blocks. There is nothing that can be done to
rehabilitate them, even using the manufacturer's
On Sun, Mar 13, 2011 at 8:57 AM, Andrei Warkentin andr...@motorola.com wrote:
Sorry to butt in, I think I'm missing most of the context
herenevertheless... I'm curious, ignoring outer packaging and
product names, if you look at cards with the same CID (i.e. same
manfid/oemid/date/firmware
On Sun, Mar 13, 2011 at 1:00 PM, C. Scott Ananian csc...@laptop.org wrote:
On Sun, Mar 13, 2011 at 8:57 AM, Andrei Warkentin andr...@motorola.com
wrote:
Sorry to butt in, I think I'm missing most of the context
herenevertheless... I'm curious, ignoring outer packaging and
product names,
On Sunday 13 March 2011 02:01:22 C. Scott Ananian wrote:
On Sat, Mar 12, 2011 at 5:51 PM, Arnd Bergmann a...@arndb.de wrote:
I've had four cards with a Sandisk label that had unusual characteristics
and manufacturer/OEM IDs that refer to other companies, three Samsung (SM)
and one unknown
On Sat, Mar 12, 2011 at 7:01 PM, C. Scott Ananian csc...@laptop.org wrote:
On Sat, Mar 12, 2011 at 5:51 PM, Arnd Bergmann a...@arndb.de wrote:
I've had four cards with a Sandisk label that had unusual characteristics
and manufacturer/OEM IDs that refer to other companies, three Samsung (SM)
On 03/13/2011 01:21 PM, Arnd Bergmann wrote:
Do you have test results somewhere publically available? We are currently
discussing adding some tweaks to the linux mmc drivers to detect cards
with certain features, and to do some optimizations in the block layer
for common ones.
The tests have also helped expose other issues with things like sudden
power off. In one case a SPO during a write would corrupt the card so
badly it became useless. You could only recover them via a super secret
tool from the manufacturer.
Is there any sledgehammer process available to
On Mar 11, 2011, at 5:35 AM, Arnd Bergmann wrote:
I've tested around a dozen media from them, and while you are true
that they use rather different algorithms and NAND chips inside, all
of them can write to at least 5 erase blocks before getting into
garbage collection, which is really
Canonical related blog post: http://www.bunniestudios.com/blog/?p=918
Mandatory reading for anyone who has to deal with flash memory.
--scott
--
( http://cscott.net/ )
___
Devel mailing list
Devel@lists.laptop.org
On Friday 11 March 2011 18:28:49 John Watlington wrote:
On Mar 11, 2011, at 5:35 AM, Arnd Bergmann wrote:
I've tested around a dozen media from them, and while you are true
that they use rather different algorithms and NAND chips inside, all
of them can write to at least 5 erase blocks
On Sat, Mar 12, 2011 at 5:51 PM, Arnd Bergmann a...@arndb.de wrote:
I've had four cards with a Sandisk label that had unusual characteristics
and manufacturer/OEM IDs that refer to other companies, three Samsung (SM)
and one unknown (BE, possibly lexar). In all cases, the Sandisk support
has
On Friday 11 March 2011, John Watlington wrote:
On Mar 9, 2011, at 2:23 PM, Arnd Bergmann wrote:
On Wednesday 09 March 2011 17:31:24 Kevin Gordon wrote:
go, no-go, spend the extra pennies and get a Class 4/6/8/10
Note that Class 8 does not exist (except fakes) and class 10 is
usually
On 10 March 2011 05:51, Paul Fox p...@laptop.org wrote:
kevin wrote:
and having my anti-static wrist guard properly attached - advice please:
go,
no-go, spend the extra pennies and get a Class 4/6/8/10. All I know for
sure is the 2GiB card in there has to be replaced. There are
On Mar 9, 2011, at 2:23 PM, Arnd Bergmann wrote:
On Wednesday 09 March 2011 17:31:24 Kevin Gordon wrote:
go, no-go, spend the extra pennies and get a Class 4/6/8/10
Note that Class 8 does not exist (except fakes) and class 10 is
usually not faster than class 6 if you run ext3 on it.
Mikus and James and the gang:
OK, the little 8GiB microSD card inserted into an SD adapter, inserted into
the external SD slot, passed the dir test that James said to perform at
OFW. Didnt complain. However, it is a Class 2 Sandisk card, so it might
not really be the right way to go. Before I
advice please: go, no-go,
spend the extra pennies and get a Class 4/6/8/10
Go.
I was interested in having a higher-performing XO-1.5 -- so the card I
bought back then was a class 6. It is likely the micro-SD card you have
now is a class 2 -- so your new card (Sandisk has good reputation for
kevin wrote:
Mikus and James and the gang:
OK, the little 8GiB microSD card inserted into an SD adapter, inserted into
the external SD slot, passed the dir test that James said to perform at
OFW. Didnt complain. However, it is a Class 2 Sandisk card, so it might
not really be the
On Wednesday 09 March 2011 17:31:24 Kevin Gordon wrote:
go, no-go, spend the extra pennies and get a Class 4/6/8/10
Note that Class 8 does not exist (except fakes) and class 10 is
usually not faster than class 6 if you run ext3 on it.
Also, a Sandisk card is usually faster than a card from
most
Also make sure that the partition
is aligned to 4 MB, otherwise you waste half the performance
and expected life.
I do this for every SD card onto which I myself write the partition table.
But I think the .zd files re-write the WHOLE SD card (including its
partition table). If that is true,
On Wed, Mar 09, 2011 at 03:15:12PM -0600, Mikus Grinbergs wrote:
But I think the .zd files re-write the WHOLE SD card (including its
partition table). If that is true, then the person replacing the SD
card has no control over where the partitions get placed -- only the
person who created the
On Wed, Mar 09, 2011 at 11:31:24AM -0500, Kevin Gordon wrote:
OK, the little 8GiB microSD card inserted into an SD adapter, inserted
into the external SD slot, passed the dir test that James said to
perform at OFW. Didnt complain.
Good. You must test again if you change cards, by the way.
Hi,
On Sun, Mar 06 2011, Kevin Gordon wrote:
Might someone be able to point me to the place where one can get
instructions on how to upgrade the SD card from an old XO 1.5 currently
with 2GiB, to a fresh new 8GiB micro-SD card?
Just:
wget
how to upgrade the SD card ?
All you have to do is stick the new card in, then perform the
'fs-update' (with an appropriate-sized .zd image). The ENTIRE
SD-card-content will be written-over-anew, including the partition table.
The catch is that the micro-SD card is beneath the heat
29 matches
Mail list logo
