Bug#649951: xD card fails to mount

Hi Jonathan,

Kindly find attached the full output of lspci and dmseg, just after booting and inserting the xD card. As apparent from the last two lines, the kernel successfully identified the inserted card. However, I can't find it anywhere in /dev. Only /dev/mtd0 and /dev/mtd0ro are added after the insertion of the xD card and when trying to mount them I get an error that they are not block devices. So the problem seems to be with binding the xD card to a correct block device (something like sdb, sdc ... ) which in turns causes the failure of gnome to recognize it.

This behavior appears for me on kernel 3.0.0-1-amd64 (working on wheezy, installed from testing repos) and I didn't try the xD card on any previous kernel (Same card and slot works on Windows, this is how I made sure the hardware is working in the first place).

Please let me know if you need any further information from me or you need me to try anything.

Thanks,

On Fri, Nov 25, 2011 at 2:01 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:

reassign 649951 src:linux-2.6 3.1.1-1
severity 649951 normal
quit

Hi,

Bichoy wrote:

> Package: linux-image-3.1.0-1-amd64
> Version: linux-image
> Severity: important
>
> xD card when inserted into a "Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro" fails
> to mount at all and doesn't appear in /dev.
[...]
> r852: detected xD writeable card in slot
> NAND device: Manufacturer ID: 0x98, Chip ID: 0xd5 (Toshiba xD 2GiB 3,3V)

For the future, please use "reportbug linux-image-$(uname -r)". It
provides more information about your hardware (which is not too
important in this case, but generally can be very useful).

For this case, please provide:

- full output of "dmesg" immediately after booting and reproducing the
bug, as an attachment
- output of "lspci -nnvv", also as an attachment.
- which kernels you have tried in the past. Is this a regression, or is
it the first time you've tried this? If it's the first time you've
tried this, please also try the kernel from squeeze-proposed-updates
(it should install on wheezy/sid without trouble) to see if it's
affected, too.

Thanks and hope that helps,
Jonathan