From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: "Mukund JB." <mukundjb@esntechnologies.co.in>
Cc: hirofumi@mail.parknet.co.jp,
linux-kernel-Mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: The Linux FAT issue on SD Cards.. maintainer support please
Date: Thu, 11 Aug 2005 11:33:35 -0400 [thread overview]
Message-ID: <20050811153335.GI31019@csclub.uwaterloo.ca> (raw)
In-Reply-To: <C349E772C72290419567CFD84C26E01709FFF9@mail.esn.co.in>
On Thu, Aug 11, 2005 at 10:57:14AM +0530, Mukund JB. wrote:
> I am Linux driver programmer.
>
> I have a FAT12 issue on my SD cards. I have got these addresses from the
> fs-lists as the maintainer support mail IDs for FAT-FS.
>
> I am using the 2.6.10 kernel, X86 like systems.
>
> I am NOT able to mount the Camera formatted FAT12 filesystem on my linux
> BOX. SD card is of size 16MB. At the same time I am able to mount the SD
> cards formatted in windows & linux.
>
> I have identified fat_fill_super() in fs/fat/inode.c file as the
> function that reads the super block of as MS-DOS FS.
>
> To debug, I have rebuilt my kernel 2.6.10 inserting some debug messages
> in the FS sub-system to know what data is coming into "struct
> fat_boot_sector *b" structure in fs/fat/inode.c file after sb_bread()
> call.
>
> I believe that this data in the "struct fat_boot_sector *b" should be
> FAT12 information.
>
> On the camera formatted SD that is NOT mounting I have found this
> structure to be all '0' till total_sectors variable (relevant till here
> on - FAT12).
>
> Will you please verify if there & tell me if the problem is in the FAT
> sub-system.
A few things I would try:
Stick the SD card in a generic cheap USB media reader, and see what the
kernel thinks of the cards then. Do both work?
If the answer is still no, then it really seems the card is formated
incorrectly, or linux has a bug in the fat driver.
If both work fine that way, then there is a problem in the driver for
the sd reader you are using that needs to be resolved.
Using a known to work for people in general driver (usb-storage) with
a standard usb card reader sure does seem like a good start until you
know if the card is formated properly or not.
You could also use that do dd the first few blocks from the card to see
what the partition table and fat tables look like, in case your SD
driver is somehow messing that part up. By having a copy you can
compare more easily.
Len Sorensen
next prev parent reply other threads:[~2005-08-11 15:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 5:27 Mukund JB.
2005-08-11 5:56 ` Marc Singer
2005-08-11 15:33 ` Lennart Sorensen [this message]
2005-08-12 14:22 Mukund JB.
2005-08-12 14:48 ` Lennart Sorensen
2005-08-12 14:31 Mukund JB.
2005-08-12 15:46 Mukund JB.
2005-08-12 16:00 ` Lennart Sorensen
2005-08-16 13:24 Mukund JB.
2005-08-16 16:08 ` Lennart Sorensen
2005-08-16 13:34 Mukund JB.
2005-08-16 13:59 ` Olivier Galibert
2005-08-16 16:09 ` Lennart Sorensen
2005-08-17 17:02 Mukund JB`.
2005-08-17 18:50 ` Lennart Sorensen
2005-08-18 12:51 Mukund JB`.
2005-08-18 17:26 ` Lennart Sorensen
2005-08-18 12:56 Mukund JB`.
2005-08-19 11:39 Mukund JB`.
2005-08-19 12:59 ` Lennart Sorensen
2005-08-24 8:33 Mukund JB.
2005-08-24 13:13 ` Lennart Sorensen
2005-08-24 13:18 Mukund JB.
2005-08-24 13:28 ` Lennart Sorensen
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=20050811153335.GI31019@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=mukundjb@esntechnologies.co.in \
/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
all inboxes | Powered by JetHome®