Pondering a bit about the bug I thought about using the linux real mode
interrupt (lrmi) interface (that vbetool already uses) to figure the bios driver
order. The interessting bit here is int 13h/ah=48h
(http://www.ctyme.com/intr/rb-0715.htm) to get drive information. I wrote some
testcode (based on vbetool) at http://people.ubuntu.com/~mvo/hacks/hddhack-0.0.tar.gz. Calling the interrupts
works pretty well but I seem to be unable to get the drive information into a
real-mode buffer :/
Another idea would be to use the partition label or uuid to figure the
boot-partition but that would involve a lot more work than the rather simple
approach above.
Pondering a bit about the bug I thought about using the linux real mode www.ctyme. com/intr/ rb-0715. htm) to get drive information. I wrote some people. ubuntu. com/~mvo/ hacks/hddhack- 0.0.tar. gz. Calling the interrupts
interrupt (lrmi) interface (that vbetool already uses) to figure the bios driver
order. The interessting bit here is int 13h/ah=48h
(http://
testcode (based on vbetool) at
http://
works pretty well but I seem to be unable to get the drive information into a
real-mode buffer :/
Another idea would be to use the partition label or uuid to figure the
boot-partition but that would involve a lot more work than the rather simple
approach above.