qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Martin <jmartin@notamusica.com>
To: qemu-devel@nongnu.org
Subject: OS/2 net & graphics (was: [Qemu-devel] Network problems - any news?)
Date: Tue, 3 Aug 2004 12:24:18 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.56.0408031218040.2272@halef.NotaMusica.com> (raw)
In-Reply-To: <1091510246.56584.4.camel@pcgem.rdg.cyberkinetica.com>

On Tue, 3 Aug 2004, Antony T Curtis wrote:
> > a few weeks ago, some people reported on their network connection being
> > flaky in a Win98 guest. I experience similar problems with a OS/2 guest.
> > Most of the time, it won't even receive a DHCP response.
> >
> > Has anybody been able to track down the source of these problems yet? Are
> > they independent of the emulated NIC, or may I have better results using
> > one of the alternative NIC emulators?
>
> I have only had 100% success with my AMD PCNet NIC emulation when using
> OS/2 guest. It was what partly what prompted me to write that emulation.

I tried your patch. It applies cleanly to the latest CVS and an earlier
version pretty close to 0.6.0, but qemu crashes after OS/2 has loaded the
PCNet driver and waits for a dhcp response (segmentation fault).

Running OS/2 Warp 4 with Fixpack 15 and DDFP 2.

How would I go about finding out where qemu crashes? When I attach gdb to
qemu it only tells me that the debuggee has gone away once it's crashed
and I still don't see where it happened. Is there a way to produce a core
dump?

BTW, I got SVGA support to work in OS/2 with the 'new' GENGRADD drivers
available at the OS/2 device driver pack online. Use -std-vga and the
generic Vesa-driver of GENGRADD.

	Johannes

      reply	other threads:[~2004-08-03 10:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-02 21:55 [Qemu-devel] Network problems - any news? Johannes Martin
2004-08-03  5:17 ` Antony T Curtis
2004-08-03 10:24   ` Johannes Martin [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=Pine.LNX.4.56.0408031218040.2272@halef.NotaMusica.com \
    --to=jmartin@notamusica.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).