From: Christian MICHON <christian.michon@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Can you commit the pcnet patch ?
Date: Thu, 21 Jul 2005 15:49:34 +0200 [thread overview]
Message-ID: <46d6db66050721064935c22f61@mail.gmail.com> (raw)
In-Reply-To: <200507211419.51421.paul@codesourcery.com>
I tried using pxe (at least the probe) to get more diagnostics
regarding this pcnet failure.
Based on the windows host patches I posted earlier on, I get
this message:
=============================================
Probing pci nic...
[lancepci]pcnet32.c: Found lancepci, Vendor=0x1022 Device=0x2000
lancepci: 52:54:00:12:34:56 at ioaddr C020, No MII tranceiver found!
=============================================
This apparently tells the hw emulation is incomplete. When using
realtek, I do not get this tranceiver message.
If I try to boot win95 guest with "-nic-pcnet -nics 2", I finally get an IP
thru the DHCP, but the network does not work.
The patch needs badly some update/improvement on the windows side.
Any specialist around? I'm puzzled, not being an expert in this field.
Christian
next prev parent reply other threads:[~2005-07-21 14:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 10:32 [Qemu-devel] Can you commit the pcnet patch ? Ludovic Drolez
2005-07-20 12:37 ` Paul Brook
2005-07-20 12:48 ` Christian MICHON
2005-07-21 15:32 ` Ludovic Drolez
2005-07-20 12:56 ` Ludovic Drolez
2005-07-20 14:26 ` Christian MICHON
2005-07-20 14:45 ` Christian MICHON
2005-07-20 15:19 ` Christian MICHON
2005-07-20 15:29 ` Paul Brook
2005-07-20 15:37 ` Filip Navara
2005-07-21 11:33 ` Christian MICHON
2005-07-21 16:43 ` Filip Navara
2005-07-21 20:21 ` Filip Navara
2005-07-21 20:54 ` Christian MICHON
2005-07-21 7:29 ` Lars Munch
2005-07-21 13:19 ` Paul Brook
2005-07-21 13:49 ` Christian MICHON [this message]
2005-07-21 19:10 ` Antony T Curtis
2005-07-21 21:14 ` Fabrice Bellard
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=46d6db66050721064935c22f61@mail.gmail.com \
--to=christian.michon@gmail.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 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.