On 12 August 2011 09:47, Bee Hock Goh wrote:
> I am trying to script out creating of android partitions on different
> size of sdcard. While going through android-media-create scripts, I
> found the following:
>
> return '%s,%s,%s,*\n%s,%s,L\n%s,%s,L\n%s,-,E\n%s,%s,L\n%s,,,-' % (
>
Hi,
I am trying to script out creating of android partitions on different
size of sdcard. While going through android-media-create scripts, I
found the following:
return '%s,%s,%s,*\n%s,%s,L\n%s,%s,L\n%s,-,E\n%s,%s,L\n%s,,,-' % (
boot_start, boot_len, partition_type, system_st
On 30 June 2011 04:10, AJ ONeal wrote:
> The cards are from the same manufacturer, and exactly the same size.
> I've tried dd and not only does it take closer to 2.5 hours instead of 10
> minutes, it yields the same results.
> dd if=/dev/sde of=/dev/sdf bs=8M
This bs=8M doesn't seem the best/us
Some more points:
On Friday 08 July 2011 00:37:35 AJ ONeal wrote:
> On Wed, Jun 29, 2011 at 11:48 AM, AJ ONeal wrote:
> I have a few inter-related issues:
> Why would one kernel boot a card that another kernel can't?
Possibly the controller is set up in a slightly different way, resulting
in ba
On Friday 08 July 2011 00:37:35 AJ ONeal wrote:
> Confirmed: the combination of a linaro-2.6.39 kernel with a transcend 8gb
> card results in flakey boots.
> linaro-2.6.39 kernel is affected
> transcend cards are affected
> oe-2.6.36 kernel is not affected
> sandisk 8gb cards are not affected (67
Confirmed: the combination of a linaro-2.6.39 kernel with a transcend 8gb
card results in flakey boots.
- linaro-2.6.39 kernel is affected
- transcend cards are affected
- oe-2.6.36 kernel is *not* affected
- sandisk 8gb cards are *not* affected (67 megabytes smaller)
I zero'd a card,
On 29 June 2011 23:40, AJ ONeal wrote:
> The cards are from the same manufacturer, and exactly the same size.
Is the ID of the card as reported by
/sys/class/mmc_host/mmc0/mmc0:0001/manfid and oemid
(adjust path to your SD card interface) the same for the cards that
work and the cards that don't?
The cards are from the same manufacturer, and exactly the same size.
I've tried dd and not only does it take closer to 2.5 hours instead of 10
minutes, it yields the same results.
dd if=/dev/sde of=/dev/sdf bs=8M
The only difference between a card that boots and a card that fails with `[
1.00
If you want to avoid l-m-c which is the image creation route we
support, once you've created the first master and have it booting and
setup the way you want, and presuming all your SD cards are exactly
the same, I suspect you'd fine more success to dd from master to
create an image file and then dd
>
> Were you using Linaro-media-create to put things onto the SD card or
> some other route?
>
>
Yes.
created the master card using `linaro-media-create`
booted it once and added some secret sauce to it.
duplicated that card to 20 cards using `sfdisk` and `partimage`.
(Half of those cards did no
I have a few inter-related issues:
- Why would one kernel boot a card that another kernel can't?
- Why would a card's disk geometry matter for boot?
- Who is a good manufacturer for getting hardware-identical cards in
bulk?
- How can I probe the actual "disk geometry" of an sd card?
11 matches
Mail list logo
