Follow-up Comment #5, bug #22398 (project grub):
> So essentially what you want is GRUB to include documentation about a bug
that is in your BIOS?
Well, essentially, yes. But is this such a weird idea? When people find GRUB
not working the first place they will/should check is the documentation.
Aren't there any other BIOSes that have at least some problems with GRUB? If
not, then I can understand you do not want to include it in the
documentation.
About the patch:
Does biosdisk.mod already reset the disk system with `int 0x13'? If so,
startup.S should just stop calling `int 0x13'.
And also, what're these mod things? Where can I read what file belongs to
what module?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?22398>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-grub mailing list
Bug-grub@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-grub
