From: Raph <gibboris@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: smartcard not detected
Date: Sun, 11 Apr 2010 21:54:35 +0000 [thread overview]
Message-ID: <20100411215434.GA2145@deeebian> (raw)
In-Reply-To: <20100410130905.GA6362@deeebian>
On Sun, Apr 11, 2010 at 07:07:00PM +0200, Kay Sievers wrote:
> On Sat, Apr 10, 2010 at 15:09, Raph <gibboris@gmail.com> wrote:
> > I'm using an eeepc 701 and just bought a SDHC card which
> > doesn't get detected unless :
> > - it's plugged at boot time
> > - I use udevadm trigger
> > - it has been detected once before (with either the first or
> > second method above)
> > If it's not an expected behavior below are some infos.
>
> Something on system is supposed to poll the device, otherwise media
> changes are not detected. So either HAL or DeviceKit-disks or udisks
> usually run and do that. I guess running "touch /dev/sdX" will make
> the device appear too. That's what a polling process would do, by
> opening the device every couple of seconds.
>
> Oh, and a SDHC card has not much to do with a smartcard like mentioned
> in the Subject:. :)
right, memory card is the word.
I must correct my previous email: the device does not shows up ...
in less than 15 seconds, that may be considered as normal but that's
more than other devices I plugged in until now.
But, from my last tests, the real problem seems to be that the device
doesn't get removed from /dev and /sys/block after a physical removal.
That's what wrongly brought me to my 3rd diagnostic in my previous email.
I guess that's related to the card reader driver, so... excuse me for the noise.
prev parent reply other threads:[~2010-04-11 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-10 13:09 smartcard not detected Raph
2010-04-11 17:07 ` Kay Sievers
2010-04-11 21:54 ` Raph [this message]
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=20100411215434.GA2145@deeebian \
--to=gibboris@gmail.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).