Just got this MB and got build done.
I have one slight problem.
build:
i7-6700k
win10 x64 pro
the samsung drive max speed is only 10gb/s--->should be more like 25gb/s
More details:
Bios is updated and samsung drive is plugged into m.2 ultra under the m/b
bios updated to latest version 2.00
WIN10 latest intel ME install from intel website
I see an option in the UEFI to alter the link speed of the mini pcie1 slot but not the m.2 ultra slot.
The 10gb/s that i am getting is likely gen2 x2 speeds that its falling back to .
The INTEL ME version in the bios 2.00 update is not the latest thats on intel website and what i installed via WIN10.
I dont know of a way to update the bios version without the manufacturer updating bios firmware.
I think this may be the problem. I could test this theory by pulling the m.2 drive and putting it in the mini pcie1 slot on the top of the MB and removing the wifi module in that slot. However, that would require me to completely disassemble the build and start over. Not really looking forward to that.
I am guessing this is a bug or perhaps i over looked something fundamental.
Thoughts?
I have one slight problem.
build:
i7-6700k
win10 x64 pro
the samsung drive max speed is only 10gb/s--->should be more like 25gb/s
More details:
Bios is updated and samsung drive is plugged into m.2 ultra under the m/b
bios updated to latest version 2.00
WIN10 latest intel ME install from intel website
I see an option in the UEFI to alter the link speed of the mini pcie1 slot but not the m.2 ultra slot.
The 10gb/s that i am getting is likely gen2 x2 speeds that its falling back to .
The INTEL ME version in the bios 2.00 update is not the latest thats on intel website and what i installed via WIN10.
I dont know of a way to update the bios version without the manufacturer updating bios firmware.
I think this may be the problem. I could test this theory by pulling the m.2 drive and putting it in the mini pcie1 slot on the top of the MB and removing the wifi module in that slot. However, that would require me to completely disassemble the build and start over. Not really looking forward to that.
I am guessing this is a bug or perhaps i over looked something fundamental.
Thoughts?