This content has been marked as final. Show 5 replies
Hi there, I have similar socket 1155 supermicro boards and ran into the same issue. I managed to get the system to boot by disabling Intel-AES in the BIOS. If that doesn't work, try disabling VT-D and IOMMU. Hopefully you aren't using this as a Virtualbox host because the VT-D and IOMMU really help to accelerate that.
Thanks Tom, your suggestion worked! I also re-flashed the motherboard with the latest 2.0a firmware. Intel-AES was disabled by default, but I disabled Intel VT-D from the following menu and the system now boots fine.
-> Intergrated IO Configuration
-> IIO Revision L1/P0/E1/NO
-> Intel VT-D [Disabled]
I am running Solaris on bare metal, no virtualBox hosts planned, so this should not be an inconvenience for me.
Many thanks for helping me out.
All the best
Glad to hear!
I am unsure if this is a supermicro bios issue or on Oracle's side.. I'll probably end up opening a ticket in both locations. I love the super-micro boards so and their barebone systems are used for most of my system builds. However I did not notice this behavior with the AMD boards I used in VM Hosts even though they are also supermicro. So maybe its a Solaris VT-D implementation issue.
Are you seeing a message from Solaris at boot that says "Bios miss-represents the presence of IOMMU"? I get that on some of the systems that exhibit this issue, yet there there is no doubt that they DO have IOMMU capabilities.
Interestingly I have found a similar issue on two additional systems. In both cases I had to disable Intel Trusted Execution Technology (TXT) in the BIOS. The Solaris 11 LiveCD boots fine with this enabled, but the installed OS will only boot if TXT is disabled.
Both are using an Ivy Bridge CPU, but with two different chipsets (both Intel) on motherboards from different manufacturers (one genuine intel).