From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: ATAPI Driver problems
Date: Sat, 1 Nov 2008 13:54:55 +0100 [thread overview]
Message-ID: <20081101125455.GE14721@thorin> (raw)
In-Reply-To: <20081009102325.GA856@helfmeier.de>
On Thu, Oct 09, 2008 at 12:23:25PM +0200, Clemens Helfmeier wrote:
> Hi everybody,
>
> I am trying to access the qemu cdrom drive (atapi) with grub2. Unfortunately,
> qemu crashes with "triple faults". A bit of google revealed that this would also
> reboot a real machine, so qemu has reasons for it.
>
> This always happens at the same location of code (0xb3a0 in my case) but the
> output bofore the crash is not always the same. I don't know if output is
> delayed either in qemu or in grub, does anyone know that?
>
> I also wonder why the qemu cdrom drive is not detected as removable nor as cdrom
> drive:
>
> grub> ls (ata2)/
> ../disk/ata.c:798: opened device ata0 successfully.
> ../disk/ata.c:803: using block size 0x200 for device ata0.
> ../disk/ata.c:816: closed device ata0,1.
> ../disk/ata.c:920: opening ATAPI dev `ata2'
> ../disk/scsi.c:261: dev opened
> ../disk/scsi.c:270: inquiry: devtype=0x00 removable=0
> qemu: fatal: triple fault
This code is known to work on qemu AFAIK. Is that pristine SVN, or your patched
version?
> How can i debug the running grub2 in the qemu machine? Is there an easy way with
> gdb? Did someone already get the ATAPI code working somehow? Where can i find
> information on how to access atapi/ata drives?
The wiki has some info on that IIRC
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
prev parent reply other threads:[~2008-11-01 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 10:23 ATAPI Driver problems Clemens Helfmeier
2008-11-01 12:54 ` Robert Millan [this message]
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=20081101125455.GE14721@thorin \
--to=rmh@aybabtu.com \
--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.