From: Nick Craig-Wood <ncw1@axis.demon.co.uk>
To: Patrick Beard <patrick@scotcomms.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Smartmedia 2.6.0-test9 problem.
Date: Tue, 18 Nov 2003 17:48:28 +0000 [thread overview]
Message-ID: <20031118174828.GA26450@axis.demon.co.uk> (raw)
In-Reply-To: <bpcumv$v22$1@sea.gmane.org>
On Tue, Nov 18, 2003 at 11:11:26AM -0000, Patrick Beard wrote:
> I have two smartmedia cards 16mb and 64mb. I have recently compiled
> the Debian source for Kernel 2.6.0-test9. I normally only use my
> 64mb card together with a usb reader. The problem I have led me to
> the wrong conclusion which I reported to this group. For this I
> apologise.
I wonder if you are seeing the same thing I see...
I have several different sized memory cards which I use using a usb
adaptor. The kernel (I've only tried 2.4 not 2.6) recognises the
first one fine, but refuses to update its internal knowledge of the
size of the card so if I insert a different sized one it doesn't mount
properly.
The work-around I use is to "rmmod usb-storage ; modprobe usb-storage"
whenever I change memory card - this kicks the kernel into re-reading
the size of the media (or maybe the partition table) and it all works
fine after that.
This obviously isn't ideal but I haven't found a better solution.
--
Nick Craig-Wood
ncw1@axis.demon.co.uk
next prev parent reply other threads:[~2003-11-18 17:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-18 11:11 Smartmedia 2.6.0-test9 problem Patrick Beard
2003-11-18 11:31 ` Patrick Beard
2003-11-18 17:48 ` Nick Craig-Wood [this message]
2003-11-18 21:51 ` Parick Beard
2003-11-20 22:52 ` Andries Brouwer
2003-11-21 10:59 ` Parick Beard
2003-11-18 22:17 ` Eli Carter
2003-11-18 23:08 ` Eli Carter
2003-11-20 22:56 ` Andries Brouwer
2003-11-19 11:42 ` Patrick Beard
-- strict thread matches above, loose matches on Subject: below --
2003-11-19 8:29 Vid Strpic
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=20031118174828.GA26450@axis.demon.co.uk \
--to=ncw1@axis.demon.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@scotcomms.co.uk \
/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