From: Sid Boyce <sboyce@blueyonder.co.uk>
To: gregoire@alwaysinnovating.com
Cc: Beagle Board <beagleboard@googlegroups.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Beagleboard -XM and 32GB microSD card oddities
Date: Thu, 30 Jun 2011 16:49:14 +0100 [thread overview]
Message-ID: <4E0C9AFA.60603@blueyonder.co.uk> (raw)
In-Reply-To: <1309445038.308.10.camel@gregoire-laptop>
It's marked Sandisk microSD HC 32GB. The only view and description of
how it's put together is at
http://www.androidcentral.com/finger-32gb-sandisk-microsd-card where one
reply reckons it's Class 2.
http://www.jigsaw24.com/product-details/x946axa/sandisk-32gb-micro-sd-card
for a much clear photo.
I only have a Beagleboard -XM, no access to a Pandaboard.
Regards
Sid.
On 30/06/11 15:43, Gregoire Gentil wrote:
> Is your card labeled SDHC or SDXC? Can you give the specs of your card?
> Have you tried on Pandaboard?
>
> Grégoire
>
> On Thu, 2011-06-30 at 10:50 +0100, Sid Boyce wrote:
>> I'm not really looking for a solution, just supplying some information
>> in case anyone is contemplating a>16GB card.
>>
>> Using Ubuntu 11.04 ARM or x86_64, I cannot create an ext4 partition that
>> will mount. Doing fsck.ext4 appears to fix the filesystem, but rerunning
>> fsck.ext4 a second time gives the same errors.
>>
>> Only BTRFS works.
>>
>> A BTRFS partition can be created without a problem. I then use rsync to
>> copy across all the data from the 16GB (ext4) partition and it mounts
>> without errors. After the rsync I create the excluded directories proc,
>> sys, tmp, media.
>>
>> I get a kernel oops (2.6.39-x1) on boot up of the 32GB card.
>> I'm still trying to figure why I'm getting the oops that I don't have on
>> the original 16GB card.
>> Regards
>> Sid.
>
>
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-06-30 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 9:50 Beagleboard -XM and 32GB microSD card oddities Sid Boyce
2011-06-30 14:43 ` Gregoire Gentil
2011-06-30 15:49 ` Sid Boyce [this message]
2011-06-30 15:52 ` Sid Boyce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E0C9AFA.60603@blueyonder.co.uk \
--to=sboyce@blueyonder.co.uk \
--cc=beagleboard@googlegroups.com \
--cc=gregoire@alwaysinnovating.com \
--cc=linux-omap@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox