by support »
Hello,
"PC booting sometimes" is something I've heard from some people, mostly those using relatively old PC hardware. For my own curiosity, what is the motherboard model you tried it on?
I would initially suggest to try it on another computer. It's not a solution to the problem, but it will at least let you see that the board is talking with you.
What the BIOS does at boot time is pretty much up to the BIOS version. There is a certain sequence defined in the specification, but there is much room for implementation-specific variations.
And yes, I would suggest playing around with the Vendor ID, Product ID, and the class data. I've had someone telling me that changing the base class did matter.
As for MSI-only settings, this is the way the Xillybus IP core is configured (no legacy interrupts) and it works well. Some old motherboard chips have cranky support of MSI, so the operating system may not cooperate. But I haven't had any indication that choosing MSI only would be a reason for a no-boot.
Regarding the rest of your questions, I'm afraid I can't help much.
If you manage to solve your issue without changing the computer, I will be most curious knowing what you did.
Eli
Hello,
"PC booting sometimes" is something I've heard from some people, mostly those using relatively old PC hardware. For my own curiosity, what is the motherboard model you tried it on?
I would initially suggest to try it on another computer. It's not a solution to the problem, but it will at least let you see that the board is talking with you.
What the BIOS does at boot time is pretty much up to the BIOS version. There is a certain sequence defined in the specification, but there is much room for implementation-specific variations.
And yes, I would suggest playing around with the Vendor ID, Product ID, and the class data. I've had someone telling me that changing the base class did matter.
As for MSI-only settings, this is the way the Xillybus IP core is configured (no legacy interrupts) and it works well. Some old motherboard chips have cranky support of MSI, so the operating system may not cooperate. But I haven't had any indication that choosing MSI only would be a reason for a no-boot.
Regarding the rest of your questions, I'm afraid I can't help much.
If you manage to solve your issue without changing the computer, I will be most curious knowing what you did.
Eli