sd-card mounting problem

Hi,

I have a build-in card-reader in my notebook.
When I insert a sd-card the card is mounted but as soon as i start copying the files to the harddrive, the sd-card
will unmount and than mount again.
Every time i start copying I have the unmount followed by a new mount.
I tried with different sd-cards and I have the same problem.

Card reader works fine on windows. But now I don´ t have windows anymore on this notebook so I need to use the card-reader on opensuse.

How can I solve this problem?

Thanks

Hi,

I have a build-in card-reader in my notebook.
When I insert a sd-card the card is mounted but as soon as i start copying the files to the harddrive, the sd-card
will unmount and than mount again.
Every time i start copying I have the unmount followed by a new mount.
I tried with different sd-cards and I have the same problem.

Card reader works fine on windows. But now I don´ t have windows anymore on this notebook so I need to use the card-reader on opensuse.

How can I solve this problem?

Thanks

Welcome to the openSUSE forums paperazzo. I am sorry to hear about your problems. So I just test a SD on my rig and it seems to work OK. I guess I need to ask a few questions. For instance, I am using openSUSE 11.4 64 bit & KDE 4.6 which is fully up to date using YaST. My home made PC rig has a LGA1155 ASUS motherboard, Intel i7 CPU with lots of memory and disk space. What can you tell us about your software & hardware setup?

Thank You,

Hi jdmcdaniel3,

thank you for your reply.

Here some information about my setup:

Hardware:
Toshiba Satellite A100-646
2 gb ram
2x1.66 GHz

Software:
Opensuse 11.4 Celadon 32 bit
Kernel: 2.6.37.6-0.7-default
Gnome: 2.32.1

Everything works fine, except for the sd-card reader. :frowning:

Could it be a Gnome problem?
Or the Kernel? What about updating the Kernel? Don´t know if this
2.6.37.6-0.7-default is the newest one.
Any suggestions?

Thanks

paperazzo

So, I do not use Gnome, but you could always load KDE if you wanted to give it a try.

Open YaST / Software / Software Management - Select the View Button on the top left and pick Patterns. Now, you will see several Patterns listed and you want to select:

Graphical Environment
  
[X] KDE4 Desktop Environment
[X] KDE4 Base System

Then Press the Accept button on the bottom right and allow these applications to install.

You need to restart openSUSE. To actually switch to KDE, select the sessions option on the bottom right and select the KDE Plasma session I think it is called (there is more than one KDE entry). To update your kernel, here is a blog I have on the subject:

S.A.K.C. - SUSE Automated Kernel Compiler - Version 2.50 - Blogs - openSUSE Forums

Thank You,

Hi
What size it the SD Card? From other posts it’s usually the kernel
driver for the device.

Can you see the card reader in the output from the command lsusb eg;


lsusb

Bus 001 Device 003: ID 058f:6335 Alcor Micro Corp. SD/MMC Card Reader


Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.4 (x86_64) Kernel 2.6.37.6-0.7-desktop
up 8:39, 4 users, load average: 0.19, 0.20, 0.15
GPU GeForce 8600 GTS Silent - Driver Version: 280.13

Hi
Installing an alternative desktop may not help, either installing a
later kernel as this may cause additional issues.

Better to identify the device and see what’s up first IMHO (It may not
even be supported yet).

@OP, if you don’t see the device in Linux, when in windows can you
check under hardware devices and you can pick up the Vendor and PCI ID
string.


Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.4 (x86_64) Kernel 2.6.37.6-0.7-desktop
up 8:46, 4 users, load average: 0.16, 0.17, 0.14
GPU GeForce 8600 GTS Silent - Driver Version: 280.13

And for what it might be worth, here is that portion of the lsusb output that relates to my SD reader.

Bus 001 Device 003: ID 054c:01bd Sony Corp. MRW62E Multi-Card Reader/Writer

Here is what it says with the lsusb -v command (Be aware this produces a long list which you may want to use** sudo lsusb -v | less **to view).

Bus 001 Device 003: ID 054c:01bd Sony Corp. MRW62E Multi-Card Reader/Writer
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x054c Sony Corp.
  idProduct          0x01bd MRW62E Multi-Card Reader/Writer
  bcdDevice           51.95
  iManufacturer           1 Sony
  iProduct                2 USB 2.0 MultiCard R/W
  iSerial                 3 2B209000037B
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          4 CARD READER
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk (Zip)
      iInterface              5 Bulk-In, Bulk-Out, Interface
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      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 Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)

I have been loading the most recent stable kernel, now up to 3.0.1, but not sure that has any effect on the SD card reader.

Thank You,

Hi
If the OP is using the wbsd (seems to be the common Toshiba one) module,
then adding the option nopnp=1 to /etc/modprobe.d/99-local.conf may
help.


options wbsd nopnp=1

/sbin/modinfo wbsd
filename:       /lib/modules/2.6.37.6-0.7-desktop/kernel/drivers/mmc/host/wbsd.ko
description:    Winbond W83L51xD SD/MMC card interface driver
author:         Pierre Ossman <pierre@ossman.eu>
license:        GPL
srcversion:     308F0EFB8945F3DE30EE2E0
alias:          acpi*:WEC0518:*
alias:          pnp:dWEC0518*
alias:          acpi*:WEC0517:*
alias:          pnp:dWEC0517*
depends:        mmc_core
vermagic:       2.6.37.6-0.7-desktop SMP preempt mod_unload modversions
parm:           nopnp:Scan for device instead of relying on PNP.
(default 0) (uint) parm:           io:I/O base to allocate. Must be 8
byte aligned. (default 0x248) (uint) parm:           irq:IRQ to
allocate. (default 6) (uint) parm:           dma:DMA channel to
allocate. -1 for no DMA. (default 2) (int)


Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.4 (x86_64) Kernel 2.6.37.6-0.7-desktop
up 0:02, 3 users, load average: 0.35, 0.33, 0.14
GPU GeForce 8600 GTS Silent - Driver Version: 280.13

Hi to all,

“lsusb” doesn´t give any information because my reader is not a usb, but it is build in. so I tried the command “hwinfo” and I got:

31: PCI 706.2: 0180 Storage controller
  [Created at pci.318]
  Unique ID: meMN.rzmSbP_danE
  Parent ID: 6NW+.yzvLCdtS8F7
  SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:07:06.2
  SysFS BusID: 0000:07:06.2
  Hardware Class: storage
  Model: "Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD)"
  Vendor: pci 0x104c "Texas Instruments"
  Device: pci 0x803b "5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD)"
  SubVendor: pci 0x1179 "Toshiba America Info Systems"
  SubDevice: pci 0xff10 
  Driver: "tifm_7xx1"
  Driver Modules: "tifm_7xx1"
  Memory Range: 0xf0904000-0xf0904fff (rw,non-prefetchable)
  IRQ: 18 (28618 events)
  Module Alias: "pci:v0000104Cd0000803Bsv00001179sd0000FF10bc01sc80i00"
  Driver Info #0:
    Driver Status: tifm_7xx1 is active
    Driver Activation Cmd: "modprobe tifm_7xx1"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #23 (PCI bridge)

If the OP is using the wbsd (seems to be the common Toshiba one) module,
then adding the option nopnp=1 to /etc/modprobe.d/99-local.conf may
help.

I tried, but still have the problem.

In the file:

“/var/log/message”

the following lines are written as soon as I insert the card in the reader:

Aug 14 09:17:21 jordan kernel:   928.116165] tifm_core: MMC/SD card detected in socket 0:1
Aug 14 09:17:21 jordan kernel:   928.396356] mmc1: new SD card at address 0007
Aug 14 09:17:21 jordan kernel:   928.396766] mmcblk0: mmc1:0007 SD2GB 1.89 GiB 
Aug 14 09:17:21 jordan kernel:   928.398686]  mmcblk0: p1

When I start copying files from the sd-card to the harddrive, some files are copied but than it stops copying and the following lines are added to “/var/log/message”:


Aug 14 09:18:07 jordan kernel:   974.620097] tifm_sd0:1 : card failed to respond for a long period of time (12, 5)
Aug 14 09:18:07 jordan kernel:   974.620120] tifm0 : demand removing card from socket 0:1
Aug 14 09:18:07 jordan kernel:   974.620185] mmc1: card 0007 removed
Aug 14 09:18:07 jordan kernel:   974.620280] mmcblk0: retrying using single block read
Aug 14 09:18:07 jordan kernel:   974.620293] mmcblk0: error -123 sending status comand
Aug 14 09:18:07 jordan kernel:   974.620298] mmcblk0: error -123 sending read/write command, response 0x0, card status 0x0
Aug 14 09:18:07 jordan kernel:   974.620305] end_request: I/O error, dev mmcblk0, sector 49728
Aug 14 09:18:07 jordan kernel:   974.620314] mmcblk0: error -123 sending status comand
Aug 14 09:18:07 jordan kernel:   974.620319] mmcblk0: error -123 sending read/write command, response 0x0, card status 0x0
Aug 14 09:18:07 jordan kernel:   974.620324] end_request: I/O error, dev mmcblk0, sector 49729
Aug 14 09:18:07 jordan kernel:   974.620332] mmcblk0: error -123 sending status comand
Aug 14 09:18:07 jordan kernel:   974.620336] mmcblk0: error -123 sending read/write command, response 0x0, card status 0x0
Aug 14 09:18:07 jordan kernel:   974.620341] end_request: I/O error, dev mmcblk0, sector 49730
.
.
.
.
.
.
.
Aug 14 09:18:07 jordan kernel:   974.655458] mmcblk0: error -123 sending read/write command, response 0x0, card status 0x0
Aug 14 09:18:07 jordan kernel:   974.655460] end_request: I/O error, dev mmcblk0, sector 61818
Aug 14 09:18:07 jordan kernel:   974.655464] mmcblk0: error -123 sending status comand
Aug 14 09:18:07 jordan kernel:   974.655466] mmcblk0: error -123 sending read/write command, response 0x0, card status 0x0
Aug 14 09:18:07 jordan kernel:   974.655469] end_request: I/O error, dev mmcblk0, sector 61819
Aug 14 09:18:07 jordan kernel:   974.655473] mmcblk0: error -123 sending status comand
Aug 14 09:18:07 jordan kernel:   974.655475] mmcblk0: error -123 sending read/write command, response 0x0, card status 0x0
Aug 14 09:18:07 jordan kernel:   974.655478] end_request: I/O error, dev mmcblk0, sector 61820
Aug 14 09:18:07 jordan kernel:   974.655481] mmcblk0: error -123 sending status comand
Aug 14 09:18:07 jordan kernel:   974.655484] mmcblk0: error -123 sending read/write command, response 0x0, card status 0x0
Aug 14 09:18:07 jordan kernel:   974.655487] end_request: I/O error, dev mmcblk0, sector 61821
Aug 14 09:18:07 jordan kernel:   974.655490] mmcblk0: error -123 sending status comand
Aug 14 09:18:07 jordan kernel:   974.655493] mmcblk0: error -123 sending read/write command, response 0x0, card status 0x0
Aug 14 09:18:07 jordan kernel:   974.655495] end_request: I/O error, dev mmcblk0, sector 61822
Aug 14 09:18:07 jordan kernel:   974.655499] mmcblk0: error -123 sending status comand
Aug 14 09:18:07 jordan kernel:   974.655501] mmcblk0: error -123 sending read/write command, response 0x0, card status 0x0
Aug 14 09:18:07 jordan kernel:   974.655504] end_request: I/O error, dev mmcblk0, sector 61823
Aug 14 09:18:07 jordan kernel:   974.704037] tifm_core: MMC/SD card detected in socket 0:1
Aug 14 09:18:07 jordan kernel:   974.987294] mmc1: new SD card at address 0007
Aug 14 09:18:07 jordan kernel:   974.990891] mmcblk1: mmc1:0007 SD2GB 1.89 GiB 
Aug 14 09:18:07 jordan kernel:   974.992422]  mmcblk1: p1

Could be a kernel issue.
May trie to update the kernel. But to which one?

Regards

paperazzo

I have found a different command option that can produce a shorter listing and shows the kernel module being loaded:


/sbin/lspci -k

It appears that your SD reader is using kernel module TIFM_7XX1 as described here:

Linux Kernel Driver DataBase: CONFIG_TIFM_7XX1: TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)

I have installed kernel 3.0.1 and here is the module description:

/sbin/modinfo tifm_7xx1
filename:       /lib/modules/3.0.1-0.5-desktop/kernel/drivers/misc/tifm_7xx1.ko
version:        0.8
license:        GPL
description:    TI FlashMedia host driver
author:         Alex Dubov
srcversion:     F59C57F43407595F2202461
alias:          pci:v0000104Cd0000AC8Fsv*sd*bc*sc*i*
alias:          pci:v0000104Cd0000803Bsv*sd*bc*sc*i*
alias:          pci:v0000104Cd00008033sv*sd*bc*sc*i*
depends:        tifm_core
vermagic:       3.0.1-0.5-desktop SMP preempt mod_unload modversions

It was described as experimental at first, but not sure of that now. If we can assume there is nothing wrong with the SD device and that it is not filled with dust and the SD disks are good, the best you could do is to update your kernel, OR try a different openSUSE version. Even using a LiveCD from openSUSE or any other distro might tell you if the problem is solved in something newer. I would add that the sakc script makes a painless kernel update and does not remove your old kernel. But I just can’t say if it will help you out in any way. Anyone loading in a external wireless or video driver must reload that driver when changing their kernel version. If you did not have to do this at first, then you will not need to do it later on the same computer.

Thank You,

Hi
You need to report it as a bug, http://en.opensuse.org/Bugs

Add the storage info and log file bits as information.

When you do, post back the bug number :wink:


Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.4 (x86_64) Kernel 2.6.37.6-0.7-desktop
up 15:45, 4 users, load average: 0.14, 0.10, 0.13
GPU GeForce 8600 GTS Silent - Driver Version: 280.13