![]() But it proved the connection drops were cause by the firmware.Once I was done testing JMS539FwUpdateToolv010.zip, I re-installed the 37K JMS539PM255.BIN ARECA had originally sent me to correct the 'Device Failed to Load Code(10)' error in Windows 7 between the JMS539 bridging chip and the Intel XHCI USB 3.0 embedded controller. This fixed my usb 3.0 drop issue and I had good speed but created a new issue.I now had only one volume vise seven in my Raid Stack. Meanwhile, the downstream port of the JMS583 is compatible with storage device with PCIe interface, such as SSD. The USB 3.1 Gen 2 interface offers data transfer speed up to 10Gbps, doubling the USB 3.1 Gen 1 data rate. They sent me JMS539FwUpdateToolv010.zip (unzipped: JMS539FwUpdateToolv010.exe) (ie: Firmware 255.00.03.00.11) the lastest firmware for the end user. The JMS583 is a USB 3.1 Gen 2 to PCIe Gen3 x 2 bridge controllerbetween USB host and PCIe storage device. ARECA's bin didn't update the whole Firmware area.I bet there was stuff unchange in the NVRAM area on the update.I finally got though to JMICRON in Taiwan. The Whole firmware area is 60K + 4K of NVRAM = 64K. It was all Jmicron JMS539 firmware And I now have the solutuion.My Areca ARC-5040 Raid Box is now working in full USB 3.0 with all 7 Volumes and Have an idea as to why the first JMS539 firmware update created the drop out issue in the first place with multiple volumes.See ARECA sent me FwUpdateToolv11600T2.exe and JMS539PM255.BINHowever, their bin was 37K in size like all others on the web. Issue has been fixed the Asus G75VW USB 3.0 is not junk.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |