All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Dunkel <harri@afaics.de>
To: linux-kernel@vger.kernel.org
Subject: sdcard autodetection enabled by running digikam somehow
Date: Wed, 12 Oct 2011 20:31:19 +0200	[thread overview]
Message-ID: <4E95DCF7.5070003@afaics.de> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi folks,

Maybe its a stupid question, but why do I have to run
digikam to make autodetection of sd cards work?

Before running digikam nothing happens if I insert a sd
card. After running digikam inserting and removing sd cards
is handled as expected, even if I logout and use root to
kill all jobs and agents that might be related to my
previous session (dbus, gconfd-2, gvfsd, etc).

This seems weird.

Of course I also checked lsmod: no additional modules have
been loaded by running digikam.


Kernel is 3.0.6. I am not running KDE or Gnome or any other
fancy desktop gui, only X and fvwm2. No hal, either. lsusb
of the card reader can be found below.


Any helpful comment would be highly appreciated.

Harri
- --------------------------------------------------------------
Bus 003 Device 006: ID 0424:2228 Standard Microsystems Corp. 9-in-2 Card Reader
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x0424 Standard Microsystems Corp.
  idProduct          0x2228 9-in-2 Card Reader
  bcdDevice            4.44
  iManufacturer           1
  iProduct                2
  iSerial                 3
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xc0
      Self Powered
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk (Zip)
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
        DEVICE CLASS:  07 21 07 e8 03 fe ff
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk6V3PEACgkQUTlbRTxpHjcwPgCgkvxiCL03+yppWQ3fXvi8L+Fe
fPUAoIaeXRnSJNBm67nr2hp0xQA7WAqK
=qR2g
-----END PGP SIGNATURE-----

                 reply	other threads:[~2011-10-12 18:31 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=4E95DCF7.5070003@afaics.de \
    --to=harri@afaics.de \
    --cc=linux-kernel@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.