public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eli Carter <eli.carter@inet.com>
To: Eli Carter <eli.carter@inet.com>
Cc: Nick Craig-Wood <ncw1@axis.demon.co.uk>,
	Patrick Beard <patrick@scotcomms.co.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: Smartmedia 2.6.0-test9 problem.
Date: Tue, 18 Nov 2003 17:08:07 -0600	[thread overview]
Message-ID: <3FBAA657.8070406@inet.com> (raw)
In-Reply-To: 3FBA9A6B.1040404@inet.com

Eli Carter wrote:
> Nick Craig-Wood wrote:
> 
>> 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.
>>
> 
> I've had this problem with 2.4 kernels as well, and use "unplug the 
> reader, rmmod, plug in the reader".  I reported this a long time ago, 
> and didn't get any response IIRC.

Oh, I just realized... I should mention that I was having this problem 
with CompactFlash cards of differing sizes/partitioning.

Eli
--------------------. "If it ain't broke now,
Eli Carter           \                  it will be soon." -- crypto-gram
eli.carter(a)inet.com `-------------------------------------------------


  reply	other threads:[~2003-11-18 23:08 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
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 [this message]
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=3FBAA657.8070406@inet.com \
    --to=eli.carter@inet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncw1@axis.demon.co.uk \
    --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