Quantcast
Channel: Intel Communities : Discussion List - Chipsets
Viewing all articles
Browse latest Browse all 3841

Intel C236 chipset has severe issues with RST(e) driver

$
0
0

Hello,

 

I have an ASRockRack C236 WSI mainboard running with an Intel Xeon E3-1245 v5 processor. It has eight SATA ports provided by the C236 chipset, however there seems to be some severe issues with the RST(e) driver. It looks like that:

 

Windows 10 integrated driver:
With storage controller set to AHCI, all ports (0-7) are working. With storage controller set to RAID, SATA ports 6+7 are not recognized!

Shutting system down or putting to sleep works as expected in both modes.

 

Intel RST v14.10.0.1610 driver:
With storage controller set to AHCI, SATA ports 6+7 are not recognized! With storage controller set to RAID, this driver cannot be installed (says the system would not meet the minimum requirements)!
Shutting system down or putting to sleep works as expected.

 

Intel RSTe v4.3.0.1223 driver:
Works with storage controller set to AHCI and RAID, all drives are working!
But shutting system down or putting it to sleep works NOT as expected. Drives are spinned down and power LED blinks, but system does not go off, but spins all drives incl. ODD up again, then spins them down a 2nd time and then finally goes off.

 

Intel RSTe v4.5.0.2123 driver:

Cannot be installed at all!

 

As you can see the behaviour is really strange, especially two facts:

- Why are ports 6+7 recognized in AHCI mode with the Win 10 driver, but not with the 14.10 RST driver?
- Why are ports 6+7 NOT recognized in RAID mode with the Win 10 driver, and 14.10 RST driver cannot be installed at all in RAID mode?

 

I already double checked with another board of same type which shows the same issues, so it's not a broken board or sth. like that. Please assist in solving this issue!

 

Best regards

 

Stefan


Viewing all articles
Browse latest Browse all 3841

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>