SD card does not mount Dell Inspiron 9300

Hi Saivann,

Can you tell me which version of Gutsy the SD card was known to work with?

Thanks

My SD card reader did work without problems in a fresh Gutsy Release Candidate installation. It also worked with gutsy and all updates. It also worked on Feisty before. I don't know if this bug can be reproduced on first Hardy alpha releases, but it always happens with the alpha 6.

I've looked at the driver code and the error -123 indicates that the driver believes that the SD card is no longer present - which is clearly not the case.

Do you have any other SD cards to test this with? This way we may be able to see if the problem occurs with the just SD card or the SD reader.

I suspect it's some kind of timing issue, causing the current driver not to work with your particular hardware. There are quite a few differences between the Hardy driver and the Gutsy version, so there are many possible reasons it may not work correctly.

Also, as per the kernel team's bug policy, can you please attach the following information:

* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* sudo lspci -vvnn > lspci-vvnn.log

Thanks again and we appreciate your help and feedback.

Thanks for your work on this. I looked deeper around this problem and found that the I/O errors are just errors because I remove the card without umounting correctly, we should ignore these errors. This bug finally does not appear to be a linux bug since the device seems properly detected and handled by linux kernel according to dmesg, and the SD card can always be mounted manually. Only automatic mount often stop working during more than 5 consecutive times, and suddenly it starts to work every time.

I changed description and I set the package to "ubuntu" since I don't know which package causes this bug. If you know which package causes this bug, can you change it to the right package? Also if you still suspect that there's a bug in linux kernel and that I might be wrong, please tell me and I will provide needed files and informations. I also appreciate your help on this, thanks!

I'm seeing the same behavior on a Dell Inspiron E1405. The relevant info from lspci:

02:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19)
02:01.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 0a)
02:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 05)
02:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff)

And from dmseg:
# card inserted:
[79098.904397] mmc0: new high speed SD card at address e543
[79098.904622] mmcblk0: mmc0:e543 SD01G 1006080KiB
[79098.904674] mmcblk0: p1
# card removed:
[79111.790021] mmc0: card e543 removed

SD cards automount the first time they're inserted after a reboot. After that, automount does not work, but "mount /dev/mmcblk0p1 /mnt" does.

(I forgot to mention that automount for this exact hardware worked perfectly under Gutsy.)

Same situtation as with Malicious Monkey. Under Hardy Beta the internal card reader on my e1405 works on the first insert of an SD card. But will only recognize the card again If I manually mount or reboot the laptop. The automount feature worked correctly in Gutsy.

My laptop (asus pro57Sn) is doing the same.
I am testing hardy64 and asus internal multireader is mounting the inserted SDcard only at the first time after the boot. but the card is unreadable (I can perfectly read the content of that card under gutsy and Xp)
If i phisically remove the SDcard and reinsert it volume will not be re-mounted

take care

ciao

Could you read https://wiki.ubuntu.com/DebuggingRemovableDevices and get the informations not concerning gnome-volume-manager requested there?

also there is no need to specify the ubuntu version in the title, that only creates extra work to update the title and confusion, if the bug is not closed that's because that's still an issue in the current ubuntu version

Sebastian Bacher : I tried to follow these instructions but noticed that gnome-volume-manager does not work anymore in Hardy :

root@zxz-laptop:~# gnome-volume-manager -n 2>&1 | tee gvm.log
bash: gnome-volume-manager: command not found

the gnome-volume-manager package is installed, but no binary exist in that package with the name of gnome-volume-manager. What should I do here? Should I use existing gnome-volume-manager-gthumb instead?

Thanks!

did you read my comment? the informations about gnome-volume-manager are not to get on hardy

Sorry, I did not read your comment correctly. Here's the required files.

I am also having problems on my Laptop DELLM1330 M with the internal and 3rd party USB SD-Reader and desktop with an internal USB reader. None of my SD-cards (20 in total can be read). The reader is recognized.

I use the following kernel

Ubuntu 2.6.24-16.30-generic

could you run lshal --monitor, plug the card and copy the log to a comment?

Here is what I get on the internal reader:

Start monitoring devicelist:
-------------------------------------------------
11:24:53.976: pci_1180_822_mmc_host_mmc_card_rca43356 added
11:24:54.175: storage_serial_0x208919aa added

Yay! The external reader has started to work after the latest round of updates! For your reference this is the output from the external:
Start monitoring devicelist:
-------------------------------------------------
Start monitoring devicelist:
-------------------------------------------------
11:31:11.017: storage_serial_Radius_SD_card_MMC_SD_ABCD12345683_0_2 property storage.removable.media_available = true
11:31:11.044: storage_serial_Radius_SD_card_MMC_SD_ABCD12345683_0_2 property storage.partitioning_scheme = 'mbr'
11:31:11.105: volume_uuid_6161_3931 added
11:31:11.263: volume_uuid_6161_3931 property volume.mount_point = '/media/SD-01'
11:31:11.264: volume_uuid_6161_3931 property volume.is_mounted = true

I really do not know what changed in the updates to make this work.
However the internal reader still fails ti mount the SD card :(

This bug seems fixed for my internal SD card reader since the recent updates. I was not able to reproduce it today.

Start monitoring devicelist:
-------------------------------------------------
23:59:13.595: pci_1180_822_mmc_host_mmc_card_rca32768 added
23:59:13.692: storage_serial_0x507d5815 added
23:59:13.733: volume_uuid_5804_F6FC added
23:59:13.881: volume_uuid_5804_F6FC property volume.mount_point = '/media/USB'
23:59:13.884: volume_uuid_5804_F6FC property volume.is_mounted = true

After rebooting my laptop the SD-card reader now works. So I guess the last
round of updates contained the fix.

On Sun, Apr 20, 2008 at 1:28 PM, Saïvann Carignan <email address hidden> wrote:

> This bug seems fixed for my internal SD card reader since the recent
> updates. I was not able to reproduce it today.
>
> Start monitoring devicelist:
> -------------------------------------------------
> 23:59:13.595: pci_1180_822_mmc_host_mmc_card_rca32768 added
> 23:59:13.692: storage_serial_0x507d5815 added
> 23:59:13.733: volume_uuid_5804_F6FC added
> 23:59:13.881: volume_uuid_5804_F6FC property volume.mount_point =
> '/media/USB'
> 23:59:13.884: volume_uuid_5804_F6FC property volume.is_mounted = true
>
> --
> SD card does not mount Dell Inspiron 9300
> https://bugs.launchpad.net/bugs/199215
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Source Package "gnome-mount" in Ubuntu: New
> Status in Source Package "gvfs" in Ubuntu: Confirmed
>
> Bug description:
> I have a SD card reader inside my laptop that work correctly with Windows
> XP. With Linux ubuntu Gutsy, it also worked correctly. Now with Hardy
> 2.6.24-11 kernel, The SD card reader automatically mount just half of the
> time, if I remove the SD card and put it back, often does not mount again. I
> can mount it manually myself in /media using /dev/mmcblk0 and it works,
> however no icon appears on the desktop or in "My Computer" to show that this
> device is mounted. Here's dmesg outputs :
>
> ** At this point, the system just booted, SD card is mounted and appears
> on the Desktop
> [ 128.239949] mmc0: card 3542 removed
> ** I just removed the SD card
> [ 128.381328] mmc0: new SD card at address 3542
> [ 128.382127] mmcblk0: mmc0:3542 SD01G 1006080KiB
> [ 128.382178] mmcblk0: p1
> ** I just put back the SD card, but the card did not mount (also not
> mounted in /media)
> [ 129.682923] mmc0: card 3542 removed
> ** I just removed the SD card
> [ 130.109594] mmc0: new SD card at address 3542
> [ 130.110054] mmcblk0: mmc0:3542 SD01G 1006080KiB
> [ 130.110106] mmcblk0: p1
> ** I just put back the SD card, which automatically mounted on /media and
> appears on the Desktop
>
> 03:01.2 SD Host controller [0805]: Ricoh Co Ltd R5C822
> SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 17) (prog-if 01)
> Subsystem: Dell Unknown device [1028:0189]
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> Latency: 64
> Interrupt: pin C routed to IRQ 18
> Region 0: Memory at dfcfc700 (32-bit, non-prefetchable) [size=256]
> Capabilities: <access denied>
>
> Linux zxz-laptop 2.6.24-10-generic #1 SMP Fri Feb 22 19:08:18 UTC 2008
> i686 GNU/Linux
>

Unless this bug can be reproduced again, I set the status to Fix Released, thanks!

Hello,
I can reproduce this bug with the newest updates from pre-released updates on IBM x40 and internal sd card reader, here are few comments:
$ dmesg
[ 463.553884] mmc0: new SD card at address 0002
[ 463.554305] mmcblk0: mmc0:0002 SD512 503296KiB
[ 463.554361] mmcblk0: p1

I can mount it by hand:
mount -t vfat /dev/mmcblk0p1 /mnt

Output from hal:
$ lshal --monitor

Start monitoring devicelist:
-------------------------------------------------
18:05:45.713: pci_1180_822_mmc_host_mmc_card_rca2 added
18:05:45.784: storage_serial_0x21e007ac added
18:05:45.883: volume_part1_size_515342848 added

That is all what I get, unfortunatelly sd is not working automatically.

Even if you can mount the media, do *not* trust the I/O until you have tested and verified that you do not see Bug 211668 on your hardware.

See also: Bug 88992.

can you mount the partition using gnome-mount?

Hello,
I have tested and I/O works fine, so I am not hitting the bug 211668.
Also I don't have /usr/share/hal/fdi/policy/gparted-disable-automount.fdi file, so bug 88992 is not a problem in my case.

I can still mount by hand the SD with mount(8) , but gnome-mount(1) doesn't work for me:

$ gnome-mount -v --extra-mount-options remount,exec -d /dev/mmcblk0p1
gnome-mount 0.8

$ gnome-mount --display-settings -v --extra-mount-options remount,exec -d /dev/mmcblk0p1
gnome-mount 0.8
Displaying settings for volume (overrides drive settings)
hal udi: /org/freedesktop/Hal/devices/volume_part1_size_1030193664
** (gnome-mount:26134): DEBUG: Reading from gconf directory /system/storage/volumes/_org_freedesktop_Hal_devices_volume_part1_size_1030193664
There are no settings; you can use --write-settings

I can see that there is no such gconf directory /system/storage/volumes
$ gconftool -R /system/storage
 /system/storage/default_options:
  /system/storage/default_options/ntfs:
   fstype_override = ntfs-3g
   mount_options = [umask=222,utf8,exec]
  /system/storage/default_options/vfat:
   mount_options = [shortname=mixed,uid=,utf8,umask=077,exec,flush]
  /system/storage/default_options/ntfs-3g:
   mount_options = [locale=,exec]
  /system/storage/default_options/iso9660:
   mount_options = [uid=,utf8,exec]
  /system/storage/default_options/udf:
   mount_options = [uid=,exec]
  /system/storage/default_options/hfs:
   mount_options = [uid=,]

could you try gnome-mount -v -b -d devince?

$ gnome-mount -v -b -d /dev/mmcblk0p1
gnome-mount 0.8
** (gnome-mount:6385): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_part1_size_1030193664
GConf Error: Bad key or directory name: "/system/storage/default_options/(null)/fstype_override": `(' is an invalid character in key/directory names
** (gnome-mount:6385): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_part1_size_1030193664 with mount_point='', fstype='', num_options=0
** Message: Mount failed for /org/freedesktop/Hal/devices/volume_part1_size_1030193664
org.freedesktop.DBus.Error.UnknownMethod : Method "Mount" with signature "ssas" on interface "org.freedesktop.Hal.Device.Volume" doesn't exist

$ gnome-mount -f vfat -v -b -d /dev/mmcblk0p1
gnome-mount 0.8
** (gnome-mount:6131): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_part1_size_1030193664
** (gnome-mount:6131): DEBUG: read default option 'shortname=mixed' from gconf strlist key /system/storage/default_options/vfat/mount_options
** (gnome-mount:6131): DEBUG: read default option 'uid=' from gconf strlist key /system/storage/default_options/vfat/mount_options
** (gnome-mount:6131): DEBUG: read default option 'utf8' from gconf strlist key /system/storage/default_options/vfat/mount_options
** (gnome-mount:6131): DEBUG: read default option 'umask=077' from gconf strlist key /system/storage/default_options/vfat/mount_options
** (gnome-mount:6131): DEBUG: read default option 'exec' from gconf strlist key /system/storage/default_options/vfat/mount_options
** (gnome-mount:6131): DEBUG: read default option 'flush' from gconf strlist key /system/storage/default_options/vfat/mount_options
** (gnome-mount:6131): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_part1_size_1030193664 with mount_point='', fstype='vfat', num_options=6
** (gnome-mount:6131): DEBUG: option='shortname=mixed'
** (gnome-mount:6131): DEBUG: option='uid=1000'
** (gnome-mount:6131): DEBUG: option='utf8'
** (gnome-mount:6131): DEBUG: option='umask=077'
** (gnome-mount:6131): DEBUG: option='exec'
** (gnome-mount:6131): DEBUG: option='flush'
** Message: Mount failed for /org/freedesktop/Hal/devices/volume_part1_size_1030193664
org.freedesktop.DBus.Error.UnknownMethod : Method "Mount" with signature "ssas" on interface "org.freedesktop.Hal.Device.Volume" doesn't exist

what filesystem is used on the card? it seems that it doesn't success to detect it correctly. that's not a gvfs issue

It's fat16.
I have been trying on two cards, one formatted using camera (Ixus 40) and second formatted by Palm LifeDrive.

After plugging in the card, can you please do

  lshal > /tmp/hal.txt

and attach /tmp/hal.txt here? Thanks!

Might be related to the gconf error, though. I'll have a look at this.

I have exactly the same issue. SD card do not automount in 8.04 while it worked fine in 7.10. I can mount by hand using 'mount' command.

dmesg:
[18059.497955] mmc0: problem reading switch capabilities, performance might suffer.
[18059.499051] mmc0: new SD card at address 795f
[18059.499885] mmcblk0: mmc0:795f SD01G 1006080KiB
[18059.499951] mmcblk0: p1
$ gnome-mount -v -b -d /dev/mmcblk0p1
gnome-mount 0.8
** Message: Given device '/dev/mmcblk0p1' is not a volume or a drive.

Output from lshal attached.

I have HP nx7010 notebook.

I too am having a very similar problem. It is occurring on a Gateway M320 laptop. Automounting of SD cards worked in 7.10 and earlier releases (at least back to 6.06, I believe), but is not working with 8.04.1 (fully updated), and I don't believe it has worked in 8.04 at any point. The reader is internal, which came with this laptop. I'm posting the files and outputs recommended by the "DebuggingRemovableDevices" page in the wiki. Hope this helps.

id yields:
uid=1000(toni) gid=1000(toni) groups=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),107(fuse),109(lpadmin),115(admin),125(vboxusers),1000(toni)

id hal:
id: hal: No such user

id haldaemon:
uid=111(haldaemon) gid=123(haldaemon) groups=123(haldaemon)

uname -a:
Linux toni-lappy 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux

Same on Intrepid (kernel 2.6.27-8-generic) with a USB micro SD card reader.

~$ gnome-mount -v -b -f vfat -d /dev/sdb1
gnome-mount 0.8
** (gnome-mount:12387): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_part1_size_2031226368
** (gnome-mount:12387): DEBUG: read default option 'shortname=mixed' from gconf strlist key /system/storage/default_options/vfat/mount_options
** (gnome-mount:12387): DEBUG: read default option 'uid=' from gconf strlist key /system/storage/default_options/vfat/mount_options
** (gnome-mount:12387): DEBUG: read default option 'utf8' from gconf strlist key /system/storage/default_options/vfat/mount_options
** (gnome-mount:12387): DEBUG: read default option 'umask=077' from gconf strlist key /system/storage/default_options/vfat/mount_options
** (gnome-mount:12387): DEBUG: read default option 'exec' from gconf strlist key /system/storage/default_options/vfat/mount_options
** (gnome-mount:12387): DEBUG: read default option 'flush' from gconf strlist key /system/storage/default_options/vfat/mount_options
** (gnome-mount:12387): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_part1_size_2031226368 with mount_point='', fstype='vfat', num_options=6
** (gnome-mount:12387): DEBUG: option='shortname=mixed'
** (gnome-mount:12387): DEBUG: option='uid=1000'
** (gnome-mount:12387): DEBUG: option='utf8'
** (gnome-mount:12387): DEBUG: option='umask=077'
** (gnome-mount:12387): DEBUG: option='exec'
** (gnome-mount:12387): DEBUG: option='flush'
** Message: Mount failed for /org/freedesktop/Hal/devices/volume_part1_size_2031226368
org.freedesktop.DBus.Error.UnknownMethod : Method "Mount" with signature "ssas" on interface "org.freedesktop.Hal.Device.Volume" doesn't exist

This report now has various reporters with differerent issues. I am going to use this for the original report from Saïvann Carignan. His hal debug output shows

14:15:47.054 [I] blockdev.c:970: Ignoring hotplug event - no parent
14:15:47.054 [W] blockdev.c:1481: Not adding device object

which seems to point to an inconsistency with the /sys tree/udev/hal. Saïvann, do you still have this issue in 8.10?

Martin Pitt : As per my latest comment, I cannot reproduce this bug anymore with latest updates. I tried again today with jaunty alpha 3 and the SD card mount correctly each time, whatever I do. According to this, I'm changing status again to fix released. Unless there are sufficient clues to think that other reporters are getting the exact same bug, other issues should be reported as separate bugs. Thanks!

Is this going to be fixed for the stable 8.0.4 release? I have the same problem on 780G chipset mobo
 2.6.24-23-generic #1 SMP Wed Apr 1 21:43:24 UTC 2009 x86_64 GNU/Linux

The cardreader is built-in on the Dell 2408WFP. lsusb simply hangs.

Is upgrade to unstable release compulsory for stable release users to get their bugs fixed?

TIA

> Is upgrade to unstable release compulsory for stable release users to get their bugs fixed?

no but there is thousand of bugs fixed every cycles and the team doesn't have the ressources to backport all that to stable, also copying all the unstable code change to stable would mean it would become unstable, that bug could be fixed if somebody identify a small change doing the job

Alrity. Thanks for explainng why. That makes me feel much better :)

Thanks & Regards

Alrity. Thanks for explaining why. That makes me feel much better :)

Thanks & Regards

I suddenly have doubts about your choice of words -

>>> there is thousand of bugs fixed every cycles and the team doesn't have the resources to backport all that to stable, also copying all the unstable code change to stable would mean it would become unstable..
<<<

Why is a bug-fix being confused with feature backports? The new features would be the unstable bit that don't need to get back into the stable release. I do appreciate the argument about the resource crunch, but I do feel the Ubuntu team is skipping on its commitment to fix bugs in LTS releases.

Please clarify.

Regards

There is no confusion but in this case there is no clear bugfix change and lot of code has been rewritten so it's not a matter to just copying the change but it could be doing work from scratch. The LTS version get security support for 3 years on the desktop but nowhere it's written than every single bug fix will be applied to the lts version, we just do the best we can with the available ressources

 I understand. Thank you for clarifying that.

Regards