Did they try to reproduce with the exact same flash procedure as you? Do you have any other adapters in the system that they may not have had?
The thing I think most likely is that you ran out of option rom space. In x86 BIOS, it is a very limited area, and quite possibly switching the intel to raid bloated its footprint enough to leave insufficient space for your .rom. Have you tried make bin/10ec8168.mrom or does that not work with the device in question? That would be my next step. If there are more non-boot adapters that have option roms, I'd try disabling their option rom support in BIOS (at least IBM BIOS allows suppresion of slot option roms, I'm guessing most everyone does_. On Mon, Apr 15, 2013 at 7:47 AM, Joshua C. <[email protected]> wrote: > I have a strange problem with my bin/10ec8168.rom which I successfully > flashed in my bios. The orom loads and works normally when the intel-sata > controller is set to either AHCI/IDE/Disabled.When I set it to RAID-mode > then the orom doesn't load. > > I reported this to the MB-verdor (msi motherboard) and they replied they > cannot reproduced the problem. This was accompanied with a screenshot that > clearly supports their answer. > > So I'm puzzled as to what can cause the problem? Any ideas if some bios > calls/interrups (maybe resposible for loading the orom) can be hjacked by > the intel-orom when set to RAID-mode? How can I try to debug this? What can > it be? > > -- > --joshua > > _______________________________________________ > ipxe-devel mailing list > [email protected] > https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel > >
_______________________________________________ ipxe-devel mailing list [email protected] https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
