It's kinda funny that you release Broadwell-E compatibility before EVGA did.
 
Funny as in a sad way, for EVGA.

ValkyrieStar

Whag in particular is the problem with the raid controllers?
No boot support or not detecting at all?

I doubt id be able to do much in the way of this but i can look into it.
I have no raid controllers to test either

 
Problem with some Adaptec/PMC/Microsemi (why they can't stick to one name, darn corporations) controllers is that kernel does not initialize properly. To illustrate problem:




 
Top picture shows card which cannot initialize at all. It tries to load kernel 3 times and then hangs everything.
 
Bottom picture shows (semi-)properly initialized card. EVGA Classified detected my 71605 controller (16 ports) as 7805 (8 ports). Ignore the stuff below SAS WWN as it was just card alone without any drives connected to it (last thing I needed was to risk array damage with constant restarts). Now I know that this problem persist all across the X99 boards. 8 series works like a charm, but still 7 series 16 port card cost equivalent of about 1000$ (at least it did when I got it 2 years before first X99 hit the shelves). It's not PCI USB controller which cost 5$ and you can throw it away if it doesn't work. One thing straight. Controller works flawlessly in any board as long as it's not X99.
 
In odd way when controller is plugged (doesn't matter slot or bus generation as I've tested any mathematical possibility available) board emits long loud beep, long before POST beeps. From what I remember it happens at code 32 - can't afford now to run test again and I think there is some thread or post about it somewhere on the forum when precisely. Wasted many months last year on this without any results and sadly EVGA support never actually materialized any compatibility fix.
 

ypsylon

ValkyrieStar

Whag in particular is the problem with the raid controllers?
No boot support or not detecting at all?

I doubt id be able to do much in the way of this but i can look into it.
I have no raid controllers to test either

 
Problem with some Adaptec/PMC/Microsemi (why they can't stick to one name, darn corporations) controllers is that kernel does not initialize properly. To illustrate problem:




 
Top picture shows card which cannot initialize at all. It tries to load kernel 3 times and then hangs everything.
 
Bottom picture shows (semi-)properly initialized card. EVGA Classified detected my 71605 controller (16 ports) as 7805 (8 ports). Ignore the stuff below SAS WWN as it was just card alone without any drives connected to it (last thing I needed was to risk array damage with constant restarts). Now I know that this problem persist all across the X99 boards. 8 series works like a charm, but still 7 series 16 port card cost equivalent of about 1000$ (at least it did when I got it 2 years before first X99 hit the shelves). It's not PCI USB controller which cost 5$ and you can throw it away if it doesn't work. One thing straight. Controller works flawlessly in any board as long as it's not X99.
 
In odd way when controller is plugged (doesn't matter slot or bus generation as I've tested any mathematical possibility available) board emits long loud beep, long before POST beeps. From what I remember it happens at code 32 - can't afford now to run test again and I think there is some thread or post about it somewhere on the forum when precisely. Wasted many months last year on this without any results and sadly EVGA support never actually materialized any compatibility fix.
 

 
I just had a check on their site and a search found this;
http://ask.adaptec.com/app/answers/detail/a_id/15365/~/error-message%3A-controller-kernel-stopped-running
 
One of the causes can be motherboard incompatibility. And they recommend updating the firmware of the Controller itself.
I found some Firmware downloads for your model here; latest version is listed as a 11th May 2016 release date, 2 days ago! Perhaps that will help.
http://storage.microsemi.com/en-us/speed/raid/asr/fw_bios/71605_fw_b32106_zip.php
 
As always with firmware updates and such, back up everything you can. In case of any catastrophic failure.
 
Can you list everything you've tried doing to make it work?

ValkyrieStar

eckertt001
Appreciate the work put into this.  I though was unable to set my memory to 3200, still received blue screens.  This was using either M.2 compatibility on or off.
 
Are their other specific settings you used?

There was no other specific setting that i used.
I just flashed the bios, and put in all my normal config values, except this time i enabled xmp profile 1, which previously boot looped, and it worked.

What memory kit are you using? My kit is Corsair LPX 3200 C16 (4x8GB).

G.SKILL TridentZ 32GB DDR4 3200
 
I did the same thing (XMP Profile 1), but it blue screens on boot up.  I did not run into boot loops on prior firmware(s).  Voltage (1.35) and everything else adjusts accordingly, so that should be good.  I turned Compatibility both on and off.
 
But otherwise not a big deal, and I'll keep messing with it.
 
Again though thanks for putting the effort into this!

eckertt001

ValkyrieStar

eckertt001
Appreciate the work put into this.  I though was unable to set my memory to 3200, still received blue screens.  This was using either M.2 compatibility on or off.

Are their other specific settings you used?

There was no other specific setting that i used.
I just flashed the bios, and put in all my normal config values, except this time i enabled xmp profile 1, which previously boot looped, and it worked.

What memory kit are you using? My kit is Corsair LPX 3200 C16 (4x8GB).

G.SKILL TridentZ 32GB DDR4 3200
 
I did the same thing (XMP Profile 1), but it blue screens on boot up.  I did not run into boot loops on prior firmware(s).  Voltage (1.35) and everything else adjusts accordingly, so that should be good.  I turned Compatibility both on and off.
 
But otherwise not a big deal, and I'll keep messing with it.
 
Again though thanks for putting the effort into this!

Was your memory able to run on XMP #1 on the original bios?

Try bumping up the VCCIO voltage, its hidden away in Advanced -> HW Monitoring -> VCCIO voltage.

Its default value should be 1.05v, you can try up to 1.25v but more than that probably wont help much.

Oddly even though it doesnt show in the BIOS, XMP profiles also adjust the VCCSA offset on the main overclocking page. You can check the offset in HWMonitor from in windows. My XMP profile was bumping that to a +0.400v offset according to HWMonitor.

If you manage to get into windows and its showing a high offset like 500, then its getting close to the point where you might actually need to change Vin to 1.9v instead of the default 1.8v.

ValkyrieStar
 
I just had a check on their site and a search found this;
http://ask.adaptec.com/app/answers/detail/a_id/15365/~/error-message%3A-controller-kernel-stopped-running
 
One of the causes can be motherboard incompatibility. And they recommend updating the firmware of the Controller itself.
I found some Firmware downloads for your model here; latest version is listed as a 11th May 2016 release date, 2 days ago! Perhaps that will help.
http://storage.microsemi.com/en-us/speed/raid/asr/fw_bios/71605_fw_b32106_zip.php
 
As always with firmware updates and such, back up everything you can. In case of any catastrophic failure.
 
Can you list everything you've tried doing to make it work?

 
Uhh that's new. Last update was July last year. Anyway not holding my breath for that either. I went through every firmware revision. I got some experimental builds from Adaptec support to provide feedback and nothing changed.  Thanks for the heads up on that. Will test, but not expecting nothing spectacular. For now enjoying finally working main rig which was supposedly to be finished before 1st May, but with so much bad luck and obstacles I hit with this refit I think Friday 13th is lucky day actually.
 
List of things I've done:
 
- tested every firmware including experimental (either from EVGA or Adaptec),
- tested every slot configuration,
- tested every slot with server grade powered riser just in case card power delivery was incompatible with board,
- tested with full RAID expose RAW mode, hidden RAW, HBA, and Auto Volume
- tested with card BIOS disabled
- used 3 VGAs to remove conflict with VGA from equation (8800 GTS, GTX580 and 970)
- disabled unused slots with DIP switch
- tested with Turbo troubleshooter enabled
 
Out of couple hundreds of attempts to make it work, controller was detected properly once (! - the day when I recorded a movie for Jacob and tech guys to see, but after restart it was back in Dead mode), about 6-8 times as either 7805 & 7805E and hundreds without life at all. Classy UEFI detected controller (Advanced tab) only once (to use new HII function instead legacy Ctrl+A which is standard for last 30 years since first Adaptec SCSI controllers). If I set BIOS>StorageROM to UEFI I cannot boot the system - just blank screen at some stage - but I'm not fan of UEFI management anyway. With classic mode I can see if anything is wrong. With UEFI I cannot. Classy offers no POST verbose, just logo or black screen. It's fine for gamers not for workstations.
 
In the end I just obtained 8405 + expander and it works, but I will gladly trade 8405 for 71605 for additional 12 ports. 8 series use different kernel that 7 series. 

ypsylon

ValkyrieStar
 
I just had a check on their site and a search found this;
http://ask.adaptec.com/app/answers/detail/a_id/15365/~/error-message%3A-controller-kernel-stopped-running
 
One of the causes can be motherboard incompatibility. And they recommend updating the firmware of the Controller itself.
I found some Firmware downloads for your model here; latest version is listed as a 11th May 2016 release date, 2 days ago! Perhaps that will help.
http://storage.microsemi.com/en-us/speed/raid/asr/fw_bios/71605_fw_b32106_zip.php
 
As always with firmware updates and such, back up everything you can. In case of any catastrophic failure.
 
Can you list everything you've tried doing to make it work?

 
Uhh that's new. Last update was July last year. Anyway not holding my breath for that either. I went through every firmware revision. I got some experimental builds from Adaptec support to provide feedback and nothing changed.  Thanks for the heads up on that. Will test, but not expecting nothing spectacular. For now enjoying finally working main rig which was supposedly to be finished before 1st May, but with so much bad luck and obstacles I hit with this refit I think Friday 13th is lucky day actually.
 
List of things I've done:
 
- tested every firmware including experimental (either from EVGA or Adaptec),
- tested every slot configuration,
- tested every slot with server grade powered riser just in case card power delivery was incompatible with board,
- tested with full RAID expose RAW mode, hidden RAW, HBA, and Auto Volume
- tested with card BIOS disabled
- used 3 VGAs to remove conflict with VGA from equation (8800 GTS, GTX580 and 970)
- disabled unused slots with DIP switch
- tested with Turbo troubleshooter enabled
 
Out of couple hundreds of attempts to make it work, controller was detected properly once (! - the day when I recorded a movie for Jacob and tech guys to see, but after restart it was back in Dead mode), about 6-8 times as either 7805 & 7805E and hundreds without life at all. Classy UEFI detected controller (Advanced tab) only once (to use new HII function instead legacy Ctrl+A which is standard for last 30 years since first Adaptec SCSI controllers). If I set BIOS>StorageROM to UEFI I cannot boot the system - just blank screen at some stage - but I'm not fan of UEFI management anyway. With classic mode I can see if anything is wrong. With UEFI I cannot. Classy offers no POST verbose, just logo or black screen. It's fine for gamers not for workstations.
 
In the end I just obtained 8405 + expander and it works, but I will gladly trade 8405 for 71605 for additional 12 ports. 8 series use different kernel that 7 series. 

It's possible a few things could be wrong.
- Either just somehow the firmware is still not compatible with X99
- Missing/old out of date modules in CSM part of the bios.
- Combination of both.
 
I have no way to modify actual working code of the bios, I can only extract/replace and modify certain modules and even then sometimes it doesnt work.
I managed to get Intel ME Firmware updated, but upon testing, it seems that the actual working code needs to be modified, as BLCK changes no longer do anything, it just sits at its slightly odd 99.77 default no matter what I set. Even XTU refused to actually do anything with BLCK either.
 
If someone can provide me proper tools to look into the working code, please do.
 
 

ValkyrieStar
 
It's possible a few things could be wrong.
- Either just somehow the firmware is still not compatible with X99
- Missing/old out of date modules in CSM part of the bios.
- Combination of both.
 
I have no way to modify actual working code of the bios, I can only extract/replace and modify certain modules and even then sometimes it doesnt work.
I managed to get Intel ME Firmware updated, but upon testing, it seems that the actual working code needs to be modified, as BLCK changes no longer do anything, it just sits at its slightly odd 99.77 default no matter what I set. Even XTU refused to actually do anything with BLCK either.
 
If someone can provide me proper tools to look into the working code, please do.

 
Yeah, expected that it won't be easy for you. Still if you can do it yourself with proper tools, so should big corporation don't you think? With stacks of tech guys it's probably a week of work at most.
Thanks for the input anyway. 

ypsylon

ValkyrieStar
 
It's possible a few things could be wrong.
- Either just somehow the firmware is still not compatible with X99
- Missing/old out of date modules in CSM part of the bios.
- Combination of both.
 
I have no way to modify actual working code of the bios, I can only extract/replace and modify certain modules and even then sometimes it doesnt work.
I managed to get Intel ME Firmware updated, but upon testing, it seems that the actual working code needs to be modified, as BLCK changes no longer do anything, it just sits at its slightly odd 99.77 default no matter what I set. Even XTU refused to actually do anything with BLCK either.
 
If someone can provide me proper tools to look into the working code, please do.

 
Yeah, expected that it won't be easy for you. Still if you can do it yourself with proper tools, so should big corporation don't you think? With stacks of tech guys it's probably a week of work at most.
Thanks for the input anyway. 

Would you happen to know of any boards where this card does definitely work?
 
Edit; I've just read that the 7 series of cards, and likely below, is not compatible with X99 series. It's not known why, but simply the firmware on the card still does not support it.
 
I'll actually quote your post here;
http://www.overclock.net/...99-sata3#post_24923855
I'm interested as to whether the cards work with platforms like Z97 and maybe Z170.
Though the lack of PCIe 3.0 lanes will probably put most people off trying that on a Z97.
 
So those of you out there looking to buy a raid card for their X99 system, get an 8 series Adaptec card, as the previous generations of cards are not compatible.

Ypsilon and I were the folks verifying compatibility, or the lack thereof, for Adaptec cards Valkyriestar.