From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC PATCH] Re: Native CD test results
Date: Sun, 30 Mar 2008 00:59:02 -0400 [thread overview]
Message-ID: <1206853142.8818.35.camel@dv> (raw)
In-Reply-To: <20080327023715.kzdy15h4pwkg4ggw@webmail.spamcop.net>
On Thu, 2008-03-27 at 02:37 -0400, Pavel Roskin wrote:
> Even though int 13 returns in the original code (I can see it by
> modifying video memory from the real mode), something get corrupted,
> and GRUB fails to return to the protected mode.
As it turns out, BIOS writes 0 to one byte at 0x8403, which is in the
code of prot_to_real. That happens if the pointer for
grub_biosdisk_get_cdinfo_int13_extensions() is presented in %ds:%si as
0x6000:0x8000. If I put 0x6001:0x7ff0 there, 0x83f3 is corrupted.
Generally, 0x0000:(%si + 0x0403) is replaced with 0.
If we use the form with minimal offset, 0x6800:0x0000, then 0x0403 would
be corrupted, but this is in the BIOS area, so it's probably what BIOS
really was meant to do.
I've seen in on two machines, both with AMD processors in Socket A, VIA
chipset and AWARD BIOS.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-03-30 4:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 2:09 Native CD test results Pavel Roskin
2008-03-27 6:37 ` [RFC PATCH] " Pavel Roskin
2008-03-30 4:59 ` Pavel Roskin [this message]
2008-03-27 8:24 ` Bean
2008-03-27 15:30 ` Pavel Roskin
2008-03-27 20:25 ` Bean
2008-03-27 20:48 ` Pavel Roskin
2008-03-27 21:46 ` Pavel Roskin
2008-03-27 21:55 ` Vesa Jääskeläinen
2008-03-27 22:08 ` Pavel Roskin
2008-03-28 17:40 ` Pavel Roskin
2008-03-29 11:13 ` Vesa Jääskeläinen
2008-03-30 4:08 ` Pavel Roskin
2008-04-13 11:08 ` Robert Millan
2008-04-14 1:09 ` Pavel Roskin
2008-04-14 12:08 ` Robert Millan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1206853142.8818.35.camel@dv \
--to=proski@gnu.org \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.