On Mon, Mar 03, 2008 at 11:42:09AM +0100, Francesco Latino wrote:
Hello,
I suppose this is the right place for this kind of questions: if not, please
excuse me in advance.
I am really interested in understanding how GRUB works and growing my
experience in Assembly development (I just
Update of bug #22398 (project grub):
Status:None = Wont Fix
Open/Closed:Open = Closed
___
Follow-up Comment #1:
Sorry, but your BIOS
Follow-up Comment #2, bug #22398 (project grub):
You're right. It's better to just edit the source. But there are users out
there that have the same notebook and don't know how to edit/patch the source.
Maybe this could be documented somewhere (FAQ?, not that it really is
frequently asked
Follow-up Comment #3, bug #22398 (project grub):
So essentially what you want is GRUB to include documentation about a bug
that is in your BIOS?
___
Reply to this item at:
http://savannah.gnu.org/bugs/?22398
Follow-up Comment #4, bug #22398 (project grub):
Now that I think of it, I don't see why the initialisation in startup.S
should be playing with hard drives at all. Perhaps this should be moved to
biosdisk.mod, and this way you can avoid it entirely by not loading
biosdisk.mod (e.g. using
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.
