more.
You can enable/disable smi_l in the bios. I'm going to check that today. If smi_l is disabled, your OS will never know that the BUD asserted an interruptt when you tried to write the BIOS>
The remaining question, of course, is what you're supposed to do with that interrupt, but that's next.
it's rather amazing, but intel is shipping a server motherboard that REQUIRES DOS to be upgraded. You have to wonder sometimes, what are people thinking? The only exisiting SMI_L interrupt handler is in the BIOS!
ron
- To unsubscribe: send mail to majordomo@freiburg.linux.de with 'unsubscribe openbios' in the body of the message
Well if thats the case, lets hope to god that freedos will do the trick! :)
edwin ----- Original Message ----- From: Ronald G. Minnich rminnich@lanl.gov To: openbios@elvis.informatik.uni-freiburg.de Sent: Monday, February 07, 2000 10:39 AM Subject: [OpenBIOS] l440gx+ nvram writing ...
more.
You can enable/disable smi_l in the bios. I'm going to check that today. If smi_l is disabled, your OS will never know that the BUD asserted an interruptt when you tried to write the BIOS>
The remaining question, of course, is what you're supposed to do with that interrupt, but that's next.
it's rather amazing, but intel is shipping a server motherboard that REQUIRES DOS to be upgraded. You have to wonder sometimes, what are people thinking? The only exisiting SMI_L interrupt handler is in the BIOS!
ron
To unsubscribe: send mail to majordomo@freiburg.linux.de with 'unsubscribe openbios' in the body of the message
- To unsubscribe: send mail to majordomo@freiburg.linux.de with 'unsubscribe openbios' in the body of the message
On Mon, 7 Feb 2000, Edwin Rhodes wrote:
Well if thats the case, lets hope to god that freedos will do the trick! :)
not that simple. You'll still have to solve the problem for freedos of unlocking the key.
Go to intel and get doc # 245141-001 of 3/1999. Check page 19, para 2.3.2 We need to see how that is handled. I've got requests in to Intel and VALinux now. We'll see how it goes.
ron
- To unsubscribe: send mail to majordomo@freiburg.linux.de with 'unsubscribe openbios' in the body of the message
Ron,
In case you're not aware, the SMI is the System Management Interrupt. When an SMI is asserted, the CPU will enter SMM, System Management Mode. It is a special mode of the CPU that was originally designed to make it easier for the BIOS to perform power management functions. The SMI is completely transparent to the OS and cannot be masked. The code that is executed in SMM is stored in a special memory area called SMRAM (generally mapped at A0000h-BFFFFh) and cannot be accessed unless operating in SMM (there is usually a lock bit in Intel chipsets that is set and cannot be cleared without resetting the system, this is to protect the SMI handler from being modified). The only way to modify the code in the SMI handler is to write your own BIOS. If you have a good hardware ICE then you could step through the SMI handler and find out where the FMUP signature, or you could try reverse engineering the FMUP utility. In either case you have a good deal of work ahead of you.
Dave
-----Original Message----- From: owner-openbios@elvis.informatik.uni-freiburg.de [mailto:owner-openbios@elvis.informatik.uni-freiburg.de]On Behalf Of Ronald G. Minnich Sent: Monday, February 07, 2000 10:40 AM To: openbios@elvis.informatik.uni-freiburg.de Subject: [OpenBIOS] l440gx+ nvram writing ...
more.
You can enable/disable smi_l in the bios. I'm going to check that today. If smi_l is disabled, your OS will never know that the BUD asserted an interruptt when you tried to write the BIOS>
The remaining question, of course, is what you're supposed to do with that interrupt, but that's next.
it's rather amazing, but intel is shipping a server motherboard that REQUIRES DOS to be upgraded. You have to wonder sometimes, what are people thinking? The only exisiting SMI_L interrupt handler is in the BIOS!
ron
- To unsubscribe: send mail to majordomo@freiburg.linux.de with 'unsubscribe openbios' in the body of the message
- To unsubscribe: send mail to majordomo@freiburg.linux.de with 'unsubscribe openbios' in the body of the message
On Mon, 7 Feb 2000, David Christensen wrote:
In case you're not aware, the SMI is the System Management Interrupt. When an SMI is asserted, the CPU will enter SMM, System Management Mode.
Yes, I've finally begun to realize this.
It is a special mode of the CPU that was originally designed to make it easier for the BIOS to perform power management functions. The SMI is completely transparent to the OS and cannot be masked. The code that is executed in SMM is stored in a special memory area called SMRAM (generally mapped at A0000h-BFFFFh) and cannot be accessed unless operating in SMM (there is usually a lock bit in Intel chipsets that is set and cannot be cleared without resetting the system, this is to protect the SMI handler from being modified). The only way to modify the code in the SMI handler is to write your own BIOS.
openbios to the rescue, I suppose.
geez, this is awful stuff. I'll let you know where I get today.
ron
- To unsubscribe: send mail to majordomo@freiburg.linux.de with 'unsubscribe openbios' in the body of the message
-
David Christensen -
Edwin Rhodes -
Ronald G. Minnich