SD Memory Card Problems

[phil1349]

I have recently upgraded from 14.04LTS to 16.04.1LTS on my Lenovo Z580 laptop The upgrade (live from the net) went OK, the desktop is a bit unstable and occasionally crashes but not too much of a problem.

The problem is with SD memory cards which I use in cameras. With 14.04 there was no problem but with 16.04 most function as expected, 1 is recognised but any attempt to read it gives an error message "cannot read superblock" and 1 does not register at all, it is completely ignored. It is not a hardware problem as if I boot into windoze all can be read as normal. The only pattern is that the card which is totally ignored is 32GB, the card which gives the error message is 8Gb but the other 8Gb card reads OK. All cards are formatted by the cameras.

Any ideas ?

[vinnywright]

what are they formated to/as ?

VINNY

[phil1349]

All the cards are formatted to FAT32.

I think it may be a conflict between the Lenovo card reader and the version 4 kernel. I live booted another computer, an Acer, with 16.04 and the cards read OK. Also with the 4 kernel running the Lenovo does not recognise the camera when plugged in via usb, this may indicate a usb problem as the card reader connects via the usb bus.

But how to fix it I don't know.

[jglen490]

I have recently upgraded from 14.04LTS to 16.04.1LTS on my Lenovo Z580 laptop The upgrade (live from the net) went OK, the desktop is a bit unstable and occasionally crashes but not too much of a problem.

The problem is with SD memory cards which I use in cameras. With 14.04 there was no problem but with 16.04 most function as expected, 1 is recognised but any attempt to read it gives an error message "cannot read superblock" and 1 does not register at all, it is completely ignored. It is not a hardware problem as if I boot into windoze all can be read as normal. The only pattern is that the card which is totally ignored is 32GB, the card which gives the error message is 8Gb but the other 8Gb card reads OK. All cards are formatted by the cameras.

Any ideas ?

It may not matter, but what cameras are involved (i.e., make, model)? The size of the SD card shouldn't matter, Linux handles 8GB and 32GB equally well. When you plug one of the SD cards into your card reader, go into konsole and enter

 dmesg

, and then

 lsusb.

[phil1349]

The cameras are a Panasonic TZ60 and a Nikon D5100, the camera connection problem seems to have partially resolved itself.

The TZ60 has the 32Gb card, if I plug the camera in to usb it is recognised and I can access the pics, copy them to the HD etc. dmesg and lsusb messages are normal. If I put the card in the reader it is not recognised by the file manager and dmesg gives the following :-

[ 8133.406629] usb 1-1.3: new high-speed USB device number 16 using ehci-pci
[ 8133.499514] usb 1-1.3: New USB device found, idVendor=0bda, idProduct=0139
[ 8133.499522] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8133.499527] usb 1-1.3: Product: USB2.0-CRW
[ 8133.499530] usb 1-1.3: Manufacturer: Generic
[ 8133.499533] usb 1-1.3: SerialNumber: 20100201396000000
[ 8133.888522] mmc0: tuning execution failed
[ 8133.888536] mmc0: error -22 whilst initialising SD card
[ 8135.008027] mmc0: tuning execution failed
[ 8135.008044] mmc0: error -22 whilst initialising SD card

When I plug the Nikon in with the 8Gb card, sometimes it appears in file manager, sometimes it doesn't. Dmesg output is normal. When it is recognised, I can see the file structure but the individual files cannot be copied or opened. If I plug the card in, it is not recognised and gives the following in dmesg :-

[10387.259419] usb 1-1.3: New USB device found, idVendor=0bda, idProduct=0139
[10387.259426] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[10387.259430] usb 1-1.3: Product: USB2.0-CRW
[10387.259432] usb 1-1.3: Manufacturer: Generic
[10387.259435] usb 1-1.3: SerialNumber: 20100201396000000
[10387.523744] mmc0: new ultra high speed SDR50 SDHC card at address 0007
[10387.524056] mmcblk0: mmc0:0007 SD8GB 7.21 GiB
[10387.525658] mmcblk0: p1
[10388.987616] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x900

I am now totally confused !

[jglen490]

When you insert an SD into the card reader, is that a built-in card reader within your laptop, or is it one that is connected to the laptop via USB?

[phil1349]

It is a built-in card reader but seems to be connected internally via the usb bus as shown by the following output from lsusb :-

Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 012: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 020: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 003 Device 003: ID 0c45:6455 Microdia
Bus 003 Device 002: ID 3938:1031
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

As previously posted, everything is OK when a version 3 kernel is booted, the problem is the version 4 kernel.

[jglen490]

Did you upgrade from 14.04 to 16.04, or did you do a clean install of 16.04?

I can't say for sure in this case, but there have been some issues with upgrading to 16.04 versus a clean install. Since a version 3 kernel works correctly, but a version 4 kernel doesn't, a correct module may not have been installed during the upgrade. But like I say, I don't know for sure.

[phil1349]

I did do a live upgrade & I have had issues in the past with live upgrades which were only resolved with a clean install. I might well try a clean install, why not ? nothing to lose. The only trouble is I have just tried booting off a live DVD and get exactly the same problem giving exactly the same dmesg output so it is not looking good. It looks like a conflict between the kernel modules and this model of card reader. I shall keep trying.

[jglen490]

Hopefully, a clean install will be better but it is possible that there is a fundamental issue with a specific kernel module. If you do a clean install, and it still doesn't work right, then you can file a bug with all the info that you have gathered.

[phil1349]

I will try a clean install over the weekend although as previously posted, I am not that confident. I agree that it is probably a bug in a specific kernel module but which ? I have tried lsmod which gives a full list which is comprehensive, I can guess what a lot are but some entries are a bit cryptic. If anyone can indicate what to look for I would be grateful.

Where and how would I file a formal bug report ?

[GreyGeek]

I wouldn't be so quick to indict the kernel. My own experience with upgrades vs clean installs is that clean installs are much better. One doesn't have old or mangled config files laying around, among other things. New files can't be installed because a directory can't be deleted because it is not empty, etc.

However, ALWAYS make sure the ISO checksum matches what is posted, AND that the burned ISO checksum matches as well. One option on a LiveDVD/USB is to check the burn.

[jglen490]

I will try a clean install over the weekend although as previously posted, I am not that confident. I agree that it is probably a bug in a specific kernel module but which ? I have tried lsmod which gives a full list which is comprehensive, I can guess what a lot are but some entries are a bit cryptic. If anyone can indicate what to look for I would be grateful.

Where and how would I file a formal bug report ?

GreyGeek is correct (as always!), don't be too quick to file a bug. Do the clean install first, and once you are satisfied and have all your applications back, then try the problem. If the problem still exists, then go to https://launchpad.net/ubuntu which is the home for Ubuntu bugs. On the right side of the page is a link to where you can login and file the bug report.

Before you do the clean install, make sure you have a backup of your /home first.

[phil1349]

My thanks to GreyGeek and jglen490 for their advice, I will give it a try. I backed up /home before the live upgrade.

[phil1349]

This is not good. Just completed clean install and exactly the same problem, no change. Seriously considering going back to 14.04LTS.