sdxc reader is not recognized

English Hardware
#1

This is not an exfat issue. My SDXC card reader is not being enumerated.
It is seen:

[25201.046652] hub 9-0:1.0: Cannot enable port 4. Maybe the USB cable is bad?

but Linux won’t talk to it, with either 64GB or 8GB cards. Windows is all happy. It sees the reader and manipulates the card just fine.
Googling didn’t get me to any solution or any discussion of this problem. Maybe I used the wrong terms?
It is a “Flash Point All-in-one Card Reader” USB 2.0
Do I need to buy another?

#2

similar, but still outstanding: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784337

#3

Did I guess the wrong forum, or is there no answer?

#4

On Wed, 02 Sep 2015 20:16:02 +0000, bkorb wrote:

> Did I guess the wrong forum, or is there no answer?

There’s probably an answer, but nobody here who knows it has seen or
responded.

Have you tried it on another system to see if the device works?

Jim

–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

#5

Windows is all happy.
Yes, I tried it on the other OS.

#6

On Thu, 03 Sep 2015 15:06:01 +0000, bkorb wrote:

>> Windows is all happy. Yes, I tried it on the other OS.

Both on the same system?

OK, what’s the output of lsusb when the device is plugged in?

What messages are logged in dmesg when you plug it in?

Jim

–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

#7

I pasted it here: https://bugs.debian.org/cgi-bin/bugr…cgi?bug=784337
but a copy below:

Oh, PS: I did not reboot windows on the same platform.
I used the same device on my wife’s laptop and it was read successfully.
I used a different device on the same port under Linux and it was read successfully.
So the device works (on another machine) and the port works (with a different device)
but this device on any USB port under Linux fails.

> $ dmesg | grep -v DROP-DEFLT | tail -n 20
> ... boot stuff elided]
>  7231.954610] hub 9-0:1.0: Cannot enable port 4. Maybe the USB cable is bad?
>  7232.913815] hub 9-0:1.0: Cannot enable port 4. Maybe the USB cable is bad?
>  7233.873051] hub 9-0:1.0: Cannot enable port 4. Maybe the USB cable is bad?
>  7234.832363] hub 9-0:1.0: Cannot enable port 4. Maybe the USB cable is bad?
>  7234.832376] hub 9-0:1.0: unable to enumerate USB device on port 4
> $ ls -l ; lspci|fgrep USB ; lsusb
> total 0
> lrwxrwxrwx 1 root root 0 Sep 1 07:17 0000:00:12.2 -> ../../../../devices/pci0000:00/0000:00:12.2
> lrwxrwxrwx 1 root root 0 Sep 1 07:17 0000:00:13.2 -> ../../../../devices/pci0000:00/0000:00:13.2
> lrwxrwxrwx 1 root root 0 Sep 1 07:17 0000:00:16.2 -> ../../../../devices/pci0000:00/0000:00:16.2
> --w------- 1 root root 4096 Sep 1 07:17 bind
> --w------- 1 root root 4096 Sep 1 07:17 new_id
> --w------- 1 root root 4096 Sep 1 07:17 remove_id
> --w------- 1 root root 4096 Sep 1 07:15 uevent
> --w------- 1 root root 4096 Sep 1 07:17 unbind

> 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
> 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
> 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
> 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
> 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
> 00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
> 00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
> 02:00.0 USB controller: Etron Technology, Inc. EJ168 USB 3.0 Host Controller (rev 01)
> 06:00.0 USB controller: Etron Technology, Inc. EJ168 USB 3.0 Host Controller (rev 01)

> Bus 002 Device 003: ID 03f0:0e2a Hewlett-Packard
> Bus 009 Device 002: ID 046d:c068 Logitech, Inc. G500 Laser Mouse
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> ...]
> Bus 011 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

> $ uname -a
> Linux bach 3.11.10-29-desktop #1 SMP PREEMPT Thu Mar 5 16:24:00 UTC 2015 (338c513) x86_64 x86_64 x86_64 GNU/Linux
#8

On Thu, 03 Sep 2015 22:56:01 +0000, bkorb wrote:

> Oh, PS: I did not reboot windows on the same platform.
> I used the same device on my wife’s laptop and it was read successfully.
> I used a different device on the same port under Linux and it was read
> successfully.
> So the device works (on another machine) and the port works (with a
> different device)
> but this device on any USB port under Linux fails.

It would be useful, if you could, to test on the same hardware - it could
be a combination of hardware that’s causing the issue.

Another thing to try is a different port on your PC. I’ve seen some
situations where the arrangement of USB ports on the system results in
some unexpected internal bus layouts that result in some ports working
with some devices but not others (I think depending on power
requirements, but not entirely certain).

It has been a while since I’ve seen that, though.

Jim

–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

#9

It would be useful, if you could, to test on the same hardware…
Another thing to try is a different port on your PC.
I tried different cards (SDHC and SDXC both) and different USB ports (there are 4 readily available) and different readers (HC compatible readers work, the XC compatible one not) – all with the same result (though with different port numbers…)

I’ll try booting with a “live” boot CD to see what happens with a 13.2 live, but likely over the weekend some time.

#10

On Fri, 04 Sep 2015 20:46:02 +0000, bkorb wrote:

>> It would be useful, if you could, to test on the same hardware…
>> Another thing to try is a different port on your PC.I tried different
>> cards (SDHC and SDXC both) and different USB ports
> (there are 4 readily available) and different readers (HC compatible
> readers work, the XC compatible one not) – all with the same result
> (though with different port numbers…)
>
> I’ll try booting with a “live” boot CD to see what happens with a 13.2
> live, but likely over the weekend some time.

It could just be a compatibility issue or kernel bug for that specific
device. You might submit a bug to bugzilla if your testing doesn’t
provide any further insight.

Jim

–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

#11

OK, it’s the driver and likely it’s been fixed since openSuSE is many months long in the tooth now.
The device works perfectly on a Linux Mint 17.1 platform. I’ll try to upgrade to SuSE 13.2 and see
if there is still a problem. Thank you! Regards, Bruce

#12

Before doing so, you could try to boot from a 13.2 live image and see what happens.

#13

On Mon, 07 Sep 2015 10:46:02 +0000, Knurpht wrote:

> bkorb;2727213 Wrote:
>> OK, it’s the driver and likely it’s been fixed since openSuSE is many
>> months long in the tooth now.
>> The device works perfectly on a Linux Mint 17.1 platform. I’ll try to
>> upgrade to SuSE 13.2 and see if there is still a problem. Thank you!
>> Regards, Bruce
>
> Before doing so, you could try to boot from a 13.2 live image and see
> what happens.

+1 - excellent idea. :slight_smile:

Jim

–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C