You can find the M.2 SSD that work with this unit with no problem at:
At this point let me try that here, and I will let you know what will be the result.
I will appreciate your patience on this issue.
Thanks for the reply.
My m2 card is the Samsung xp941 which is on the tested list. It works fine with bios versions earlier than 0349/0350. Version 0249 etc all work fine but not the 03x bios builds.
bump. Any update?
Hi, I have a 5i5RYK with the same SSD. I also have a dual boot set up with Win7 and Linux. I haven't had problems with the mouse and kb choking on reboots, my mouse is USB and connected on the back port, my KB is PS/2 running through a PS/2 to USB converter, also connected on the back port. I'm using version 0246 of the bios for awhile now because I had a suspicion that later versions have some new bugs in them. Even though you are on 0247 I would suggest you drop down to 0246 as it is stable for me, it may resolve your devices issue. The only bug I've experienced with that one has been in Ubuntu 15.04 with that stupid plymouthd error. If you're not using that distro, you won't experience it.
Also, be careful with the dual boots and changing things. while Win7 is a legacy boot, GRUB2 wraps it in a UEFI wrapper. You may need to "refresh" what GRUB2 can see on the partitions when in a newer bios. If/when I tear out Linux, not only will I have to delete the partition, but I will also have to take grub2 out. Not sure if you will need to boot from a stick or if you can do all this work from within Linux to refresh the tables. I mention this because while the bios is also at fault here, there is also a software variable at play too because you don't have "only" a Win7 installation.
After I have been making some tests here, I did not find any problems, I was not able to use your Samsung xp941 because unfortunately I don’t have it here but I used the Intel 530 Series.
I tried with BIOS version 0350, 0348 and 0249 but I honestly did not see any problems.
I installed the operating system Windows 7 with UEFI and legacy boot enable as it should be and no problems.
Also, I installed the USB driver and I did not have any problems when I enable xHCI (auto, or enabled).
You can download the USB driver at:
I think you have missed the point. It is not a hardware boot capability issue (per se). TX has already installed Windows 7 onto his SSD in legacy mode. Without an ability to boot in legacy mode, he cannot boot from this install. Sure, he could spend whatever number of days are necessary to reinstall Windows 7 and all of his applications in UEFI mode, but he shouldn't have to do that.
Scott that is correct. He missed the point. I'm able to install UEFI operating systems on the later bios. But I am unable to install a legacy boot OS or boot a previous legacy OS after the bios upgrade. In my case I have two legacy OS installed and had to roll back bios to maintain operation. I really wanted him to disable UEFI and then try to boot a pic-e ssd not install an OS on UEFI as I already stated that works. Oh well. Thanks for stepping in with the correction. Hopefully he can re-test with proper scenario.
I’m sorry for the delay on this case.
I hope this time I have done it in the correct way, I have been doing several tests with the unit and from my end it is working perfectly fine, I was able to install Windows 7 in legacy mode with BIOS version 0247 and then upgraded the BIOS to version 0249, 0348 and 0350 and I did not see any problems. I rebooted the system several times to see any kind of behavior but I did not see any problems.
Also, I install the operating system in legacy mode enabled with BIOS versions 0348 and 0350 and from my end I did not see any problems. The USB 3.0 is working fine when xHCI is enabled but you will need to have the USB 3.0 drivers installed or disabled xHCI in order to use the mouse and keyboard without the driver installed.
I cannot boot from the m2 once the sata in installed. I have linux loaded in. Was hoping to use the sata for stoarge and the m2 for the system software. Any ideas?
The M.2 interface exposes SATA Port 1 while the SATA Connector exposes SATA Port 0. This means that, if a drive is present on the SATA Connector, it has placed ahead of the M.2 interface in the Boot Order by default. In order to boot from the M.2 drive, you need to go into BIOS Setup (Visual BIOS) and change the Boot Order to have the M.2 drive ahead of the SATA drive.
Hello Scoot and thank you!
That's just the problem. no matter what I do, it just wants to boot from the SATA, legacy order, etc. I have not tried to downgrade the bios to 247 yet, but apparently any newer bios will not let me boot from the m2 no matter what. I am running linux. Chroot'ed to change hard drives to DEV to UUID, everything possible. Cannot boot from m2!
Just use 246. I can boot fine from my m2.
Here's the result from my testing. My i5 RY is running BIOS 350. I disabled UEFI and installed Windows 8.1 in Legacy Mode onto my M.2 drive. I then installed a 500GB HDD into the SATA bay. When I powered it back up, I went into Visual BIOS and changed the Boot Order to place the M.2 ahead of the HDD. The system boots just fine.