Gigabyte GA-Z68XP-UD3P - 20pin USB 3.0 Issue

Orias

Distinguished
Dec 30, 2013
11
0
18,510
Hi all,

Here's an interesting one that I can't seem to get to the bottom of! I have just installed an IcyBox IB-867 5.25" card reader/USB hub into my PC. I have hooked up all of the connectors required (1 x 20-pin internal USB 3.0 interface, 2 x USB internal connections, 1 x SATA and 1 x 4-pin power). All of the USB connectors work fine, so I know that part is connected properly and there is power.

The problem is with the actual card-reader slots. The power light doesn't come on, and no cards are recognised when I insert them. However, it DOES work if I pop the PC open whilst it's running, unplug the 20-pin USB 3.0 cable from the motherboard, and plug it back in again (whilst the PC is still running). At this point windows detects a new device, the card slot power-indicator turns on, and everything works fine. As soon as I turn the PC off and back on again, the card reader is no longer detected. Basically, if I want to use the card reader, I have to unplug and re-insert the internal USB 3.0 connector whilst the PC is running every time.

I am fairly sure that this must be either a BIOS or an Operating System issue, but I can't figure out what ... and why the reader isn't being recognised immediately on boot. Anyone got any ideas? Here are my PC specs:

Gigabyte GA-Z68XP-UD3P - Firmware Version F7
Intel i7-2600K @ 4.7ghz
ATI Radeon R9 290
16GB Crucial DDR3 RAM @ 1600mhz
Windows 7 64-bit (SP1 + all updates)
128BG SSD for OS
2 x 2tb 7400 HDD's

Thanks very much for any help!
 
Just a thought, I know that some Bios's (Asus in particular) have a setting where it will only initialize the keyboard and mouse. Not sure if this will solve your problem, but its worth a shot.

 
I've messed about with all of these settings now, and still it won't detect it on boot. It's frustrating as I know it's not a problem with the card reader, or the USB 3.0 port as they both work perfectly when I pull the internal cable and reconnect it. Somewhere there is a setting hiding from me!!
 
Hi there
I see you had this issue a while back.
I have exactly the same problem - I'm running Win 7 64bit with an ASUS Sabertooth mobo.
Did you ever resolve this problem? If so I'd really appreciate any tips you might have as its driving me nuts and I can't find anything elsewhere on the web.
regards
Alan
 


Hey there,

A good question! I did eventually get it sorted, but I can't remember exactly how! And even then, it was still a bit hit-and-miss. I would have to put the SD card in and out a few times before it finally decided to recognise it.

From what I remember, it was a BIOS setting that finally got it to almost work. I'm now using an Asus board, and it works fine 😀

 
I know this is an old thread but I had an identical issue and as this forum came high in the search list I thought I'd post my fix here, since it hadn't been fully answered here or elsewhere as far as I could find. I have a Lian-Li USB 3 / SD card reader combi front panel unit, with an Asus X99 Deluxe mother board. I had exactly the same problem with the SD card reader only working if the internal connector was removed and re-seated with power on, although there was no problem with the USB 3 socket. After reading around and doing a few of my own tests I came to the conclusion it wasn't an OS issue so I looked at BIOS settings. The thing that fixed it was changing EHCI legacy support from 'Enabled' (the default setting) to 'Auto'. In my BIOS this setting is under Advanced > USB Configuration. The only side effect this change seems to have had is that the computer takes about 10 seconds longer to boot if I start it with a card already in the reader, but not if there is no card present. I don't normally leave a card in it anyway so it's not an issue. I think EHCI has something to do with USB 2 support, but from the info given on the BIOS screen I don't think changing from Enabled to Auto should make any difference if you're using the USB 2 sockets on the mobo (I don't though). I hope this will help others with this baffling problem!