All of lore.kernel.org
 help / color / mirror / Atom feed
From: "V.A." <miles123@gmx.de>
To: linux-hotplug@vger.kernel.org
Subject: Problem CompactFlash Card via PCMCIA Adapter
Date: Mon, 14 Feb 2005 14:51:34 +0000	[thread overview]
Message-ID: <4210BAF6.1000904@gmx.de> (raw)

Hello,

following Problem:
Whenever I insert a CompactFlash Card/Microdrive/SD Card
via an PCMCIA Card Adapter the system becomes very slow.
(I have tryed several PCMCIA Adapters and Card Types)

There is permanent logging in the /var/log/messages that looks
like follows:
.
.
.
Jan 20 10:51:48 DE111 /etc/dev.d/block/50-hwscan.dev[1087]: new block
device /block/hde
Jan 20 10:51:48 DE111 /etc/dev.d/block/51-subfs.dev[1099]: mount block
device /block/hde/hde1
Jan 20 10:51:48 DE111 /etc/dev.d/block/51-subfs.dev[1109]: mount block
device /block/hde
Jan 20 10:51:49 DE111 /etc/dev.d/block/51-subfs.dev[1194]: umount block
device /block/hde/hde1
.
.
.
Mounting the device manually fails, with the error message that
/dev/hde1 does not exists.

I am using SuSE 9.2 with 2.6.8-24.11-default kernel. I also tryed a vanilla
kernel from kernel.org (2.6.10) but it did not solve the problem.
udev version is udev-030-9

After some experiments I could  change this behaviour by
out-commenting
BUS="ide", PROGRAM="/sbin/udev.get_persistent_device_name.sh", NAME="%k" 
SYMLINK="%c{1+}"
in /etc/udev/rules.d/50-udev.rules. After that at least /dev/hde1 does 
not dissapear and there
aren't anymore errors logged in /var/log/messages. The device can be 
easily mounted manually.

The second alternative is by changing the /etc/dev.d/block/51-subfs.dev.
BUS="ide", PROGRAM="/sbin/udev.get_persistent_device_name.sh", NAME="%k" 
SYMLINK="%c{1+}"
has to be active (not out-commentet) in /etc/udev/rules.d/50-udev.rules
In /etc/sysconfig/hotplug
HOTPLUG_DO_MOUNT="yes"
and
HOTPLUG_MOUNT_TYPE="fstab"
(with other values it won't work)

I have put following block in the 51-subfs.dev

if [ -n "$dname" -a -z "$do_mount" ]; then
  pt_name=${DEVNAME##*/}
  path_name=$dname/block/$pt_name
  if [ -d $path_name ]; then
     do_mount=whynot
  fi
fi

before the final case
.
.
case $ACTION in
  add)
  mesg "mount block device $DEVPATH"
.
.

and after the block responsible for the USB devices.

Now the Flashcard get's also automatically mounted.

I consider both approaches as being a workaround.

What's here the problem ? I mean the CF Cards when used as with
PCMCIA adapter are handled as IDE devices, but somehow there
seems to be a problem with those. The same devices used
via an USB Card Reader work without any problem.

Thanky ou in advance!
Best Regards,
Vlad


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

                 reply	other threads:[~2005-02-14 14:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4210BAF6.1000904@gmx.de \
    --to=miles123@gmx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.