USB 3.1 not working on Fatal1ty Z270 Gaming K6 |
Post Reply | Page 12> |
Author | |
transmitthis
Newbie Joined: 01 Jul 2017 Status: Offline Points: 1 |
Post Options
Thanks(0)
Posted: 01 Jul 2017 at 4:28am |
Same issue here.
Z87 Extreme4 MotherboardAnd a https://www.amazon.co.uk/gp/product/B016HL0W62/ref=oh_aui_detailpage_o02_s00?ie=UTF8&psc=1 Inateck USB 3.0 mSATA EncolsureWin 10 64 latest update, MB bios latest, no fastusb, no long cables, no hubs. Tried power setting options Tried all front back ports Change bios options for all USB features. Returned and replaced item, but it will just not connect in USB3 only USB2. Live linux, fails to mount it. Issue is constant connect/disconnect half a second apart, or no connection at all...stopping file explorer opening. No idea, just going to use msata to Pcie instead.
|
|
kicken
Newbie Joined: 30 Jun 2017 Status: Offline Points: 1 |
Post Options
Thanks(0)
|
I just had the same problem ... I just bought an Asrock Fatil1ty z270 Gaming K6, specifically as I had a USB 3.1 Type C connection I wanted to utilise.
After installing Windows 10 (v1703 Build 15063.413), I decided to get onto the Asrock website, update my BIOS (Z27GK62.10) and grab the latest (June 2017) drivers from Asrock and proceed to update. I've only just managed to connect my Drobo 5C via USB 3.1c and it would not detect it. It worked fine up on the rear USB 3.0 ports (using the Drobo supplied cable). So after reading this post, I decided to uninstall the 'updated' Asmedia USB 3.1 drivers v1.16.38.1 (dated 2016) I got from the Asmedia download page and leave the default Microsoft 1.1 (v10.0.15063.296 27th April 2017) driver installed. I reconnected the Drobo and presto ... worked straight away on the Microsoft 3.1 System Drivers. Actually this version of Windows 10 fresh on this motherboard is the first time I've seen Windows detect all non-intel devices and correctly configure all drivers without mismatch. Looks like I'll stick with the Microsoft drivers for USB 3.1, not the Asmedia ones for now. |
|
Rogerino
Newbie Joined: 27 Jan 2017 Status: Offline Points: 10 |
Post Options
Thanks(0)
|
parsec
Moderator Group Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
Post Options
Thanks(0)
|
Thanks for the update, that adapter works well, once you get one that actually works. Given my experience with other ASMedia drivers in the past, my guess seems to have been correct. Or the ASMedia 3.1 driver does not work well with this adapter, or in UASP mode. No example of the ASMedia driver performance? I'll take your word about the performance. Your test with "No drivers" is really with the Windows "inbox" driver. Could be titled "No ASMedia driver". |
|
Rogerino
Newbie Joined: 27 Jan 2017 Status: Offline Points: 10 |
Post Options
Thanks(0)
|
Rogerino
Newbie Joined: 27 Jan 2017 Status: Offline Points: 10 |
Post Options
Thanks(0)
|
I couldn't really test if under ubuntu the adapter was forking at full 3.1. speed.
I tried to replicate the test, but I don't have the old ubuntu installation usb key I used before (I did a format for the Win 10 clean install). Ubuntu 16.10 doesn't boot ("soft lockup - cpu stuck for 22s" error), ubuntu 16.04.1 LTS behaves as Windows 10 (so the usb 3.1 adapter is not working, USB 3.0 devices are fine). Unfortunately I can't change hdd power options as the hdd/adapter keep disconnecting every second (it just tries to install, in an endless loop). I ordered a replacement, I'll update the thread when it arrives. I tried to find an adapter with the jmicron chipset, but I had no luck.
|
|
parsec
Moderator Group Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
Post Options
Thanks(0)
|
A more accurate title for this thread would be, the ASMedia USB 3.1 port does not work with this Sabrent SATA adapter, and Windows 10. If it works fine with Ubuntu as you said, then there is a difference somewhere that causes it to fail with Windows 10. According to Sabrent's information about this adapter, Windows 10 is not supported by this product. That is on the Additional Information link on this page, which contradicts the main information page. So what is correct? https://www.sabrent.com/product/EC-SS31/usb-3-1-type-ssd-2-5-inch-sata-hard-drive-adapter/#additional_information I have a feeling it's the UASP transfer protocol that is causing problems with the ASMedia USB 3.1 port, and Windows 10. How long does it take for the USB 3.1 connection to be lost with Windows 10? You could try setting the Turn off hard disk after option in your Windows 10 Power Plan to Never as a test. |
|
Rogerino
Newbie Joined: 27 Jan 2017 Status: Offline Points: 10 |
Post Options
Thanks(0)
|
Yes, they work on the asmedia usb.
After the bios update they work (they weren't working before). Also hdds are working (with different usb 3.0 adapters). The linked 3.1 adapter works when connected to intel ports, doesn't work with the asmedia one (it keeps disconnecting). EDIT: under ubuntu, same adapter, same hdd, same asmedia port, works. It worked even with the first bios release. PS: Not using any extension cables or hubs.
Edited by Rogerino - 28 Jan 2017 at 2:50pm |
|
wardog
Moderator Group Joined: 15 Jul 2015 Status: Offline Points: 6447 |
Post Options
Thanks(0)
|
Rogerino
Newbie Joined: 27 Jan 2017 Status: Offline Points: 10 |
Post Options
Thanks(0)
|
Already tried those asmedia .38 drivers, on a fresh install on a new hdd too (I never installad the X-fast USB software).
I also tried the previous asmedia .36 drivers, no luck. I couldn't find anything newer than the .38 one. I was wondering, is it a motherboard firmware problem? Asmedia usb ports didn't work at all (literally, nothing worked when connected) with first bios release.
|
|
Post Reply | Page 12> |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |