qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Ben Dailey" <bdailey@bhmsd.k12.in.us>
To: eswierk@arastra.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Bios Bug?
Date: Fri, 28 Apr 2006 16:19:50 -0500	[thread overview]
Message-ID: <s45240b6.051@mail.bhmsd.k12.in.us> (raw)

Ed,

You should also note that I have not been able to use the new
-kernel-kqemu option with the old bios. The bios in cvs was specifically
patched for the new kqemu support from my understanding so that is
expected. Just a quick heads.

Thanks,
Ben

>>> eswierk@arastra.com 04/28/06 4:05 PM >>>
On 4/28/06, Ben Dailey <bdailey@bhmsd.k12.in.us> wrote:
> After much searching I believe I have found a problem with the bochs
> bios in cvs. I found that I was not able to boot the fedora core 5 or
4
> or 3 rescue cds or the Fedora 4 image from free.oszoo.org. Fedora core
2
> booted correctly as well as Windows 2000 and Windows XP. I tried the
> build with and without kqemu support and changed from gcc3.2 to gcc3.4
> to no change. I then copied the bios from 0.8.0 and now all boots
> correctly. My host system is Fedora 4 on X86_64. Is/has anyone else
seen
> this problem?

Yes, I just ran into the same problem with the bios.bin from the
2006-04-27_23 CVS snapshot. Thanks for tracking it down--you probably
saved me hours!

I was able to boot after reverting to the bios.bin from the
2006-03-27_23 snapshot. So the problem must have been introduced
within the past month.

--Ed

             reply	other threads:[~2006-04-28 21:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-28 21:19 Ben Dailey [this message]
2006-04-28 22:38 ` [Qemu-devel] Bios Bug? Fabrice Bellard
2006-04-28 22:56   ` Ed Swierk
  -- strict thread matches above, loose matches on Subject: below --
2006-04-28 18:58 Ben Dailey
2006-04-28 21:05 ` Ed Swierk

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=s45240b6.051@mail.bhmsd.k12.in.us \
    --to=bdailey@bhmsd.k12.in.us \
    --cc=eswierk@arastra.com \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).