From: Kevin O'Connor <kevin@koconnor.net>
To: "Alain Ribière" <alain_ribiere@yahoo.com>
Cc: seabios@seabios.org, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Regression: more 0.12 regression (SeaBIOS related?)
Date: Wed, 7 Mar 2012 08:38:30 -0500 [thread overview]
Message-ID: <20120307133830.GA6806@morn.localdomain> (raw)
In-Reply-To: <1331053255.66064.YahooMailNeo@web130102.mail.mud.yahoo.com>
On Tue, Mar 06, 2012 at 09:00:55AM -0800, Alain Ribière wrote:
> Hello,
>
> I'm reacting a bit later but I have a trouble with an old DOS OS from Digital Research called Concurrent DOS.
> It worked fine till Qemu v0.11.1.
> I tried it with a lot of versions from 0.12.0 to 1.0.1 and it boot correctly. But after a key pressed, I can't use the keyboard any more. The system is not freezed (there is a clock in the bottom side of the screen which is running) but I can't use the keyboard any more.
> It worked also with 0.12.0-rc1 and the PC-BIOS. It seems that with Seabios it doesn't work any more but PC-BIOS is no longer supported by QEMU (from v0.12.0).
>
> Do you know what can I do ?
You can help debug the issue so it can be fixed in SeaBIOS. Start
with producing a log from SeaBIOS by adding (on a recent qemu) the
following to the command-line:
-chardev stdio,id=seabios -device isa-debugcon,iobase=0x402,chardev=seabios
Also, if there is an image available for download, other developers
can take a look at it as well.
-Kevin
next prev parent reply other threads:[~2012-03-07 13:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 17:00 [Qemu-devel] Regression: more 0.12 regression (SeaBIOS related?) Alain Ribière
2012-03-07 13:38 ` Kevin O'Connor [this message]
2012-03-07 14:31 ` [Qemu-devel] Re : " Alain Ribière
2012-03-08 13:56 ` Luiz Capitulino
2012-03-08 14:01 ` Kevin O'Connor
2012-03-08 14:09 ` Daniel P. Berrange
2012-03-08 14:28 ` Luiz Capitulino
2012-03-08 14:36 ` [Qemu-devel] [SeaBIOS] " Peter Stuge
2012-03-08 14:37 ` [Qemu-devel] " Daniel P. Berrange
2012-03-08 14:45 ` Luiz Capitulino
2012-03-08 17:04 ` [Qemu-devel] Re : " Alain Ribière
2012-03-12 0:52 ` [Qemu-devel] " Kevin O'Connor
2012-03-12 10:38 ` [Qemu-devel] Re : " Alain Ribière
[not found] <998502.27470.qm@web15103.mail.cnb.yahoo.com>
[not found] ` <473191351003071956g48c3944fyd3adc3ae6012493c@mail.gmail.com>
2010-03-08 3:57 ` [Qemu-devel] " Roy Tam
-- strict thread matches above, loose matches on Subject: below --
2010-03-08 2:04 Roy Tam
2010-03-08 10:05 ` Jamie Lokier
2010-03-08 11:08 ` Roy Tam
2010-03-08 13:48 ` Roy Tam
2010-03-10 4:48 ` Roy Tam
2010-03-09 15:41 ` Natalia Portillo
2010-03-09 16:09 ` Natalia Portillo
2010-03-10 2:12 ` Kevin O'Connor
2010-03-10 3:49 ` Roy Tam
2010-03-10 4:59 ` Kevin O'Connor
2010-03-10 5:05 ` Roy Tam
2010-03-10 5:55 ` Kevin O'Connor
2010-03-10 5:24 ` Roy Tam
2010-03-11 3:07 ` Kevin O'Connor
2010-03-11 7:42 ` Roy Tam
2010-03-11 8:10 ` Natalia Portillo
2010-03-12 0:57 ` Kevin O'Connor
2010-03-12 1:17 ` Roy Tam
2010-03-12 16:13 ` Roy Tam
2010-03-13 15:35 ` Kevin O'Connor
2010-03-13 16:00 ` Roy Tam
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=20120307133830.GA6806@morn.localdomain \
--to=kevin@koconnor.net \
--cc=alain_ribiere@yahoo.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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).