9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Virtual PC 6 PCI device probe failure
Date: Wed, 25 Jun 2003 11:06:39 -0400	[thread overview]
Message-ID: <e305c715ab1abec77c4789469f7be51d@plan9.bell-labs.com> (raw)
In-Reply-To: <BC4932FA-A6BF-11D7-8B4F-000393D34A62@orthanc.ab.ca>

On Tue Jun 24 23:48:27 EDT 2003, lyndon@orthanc.ab.ca wrote:
> I've done some more fiddling with the VPC 6 install. Video is working
> fine, but the kernel does not see any PCI (or PNP) devices during the
> bus scan. This explains why the virtual 21140 ethernet isn't getting
> configured.
>
> Was there any magic required to get the kernel to work under vmware?
>
> Meanwhile I'm going to install a FreeBSD and see what it thinks about
> PCI devices.
>
> --lyndon

This came up a year or so ago, so maybe things have changed, but at that time
the VirtualPC docs claimed it emulated an Intel Triton chipset, but it was discovered
it didn't emulate the PCI config registers in that chipset. This matters on Plan9
because it does raw accesses to probe the PCI space whereas other operating systems
do BIOS calls to obtain that information.



  reply	other threads:[~2003-06-25 15:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-25  3:47 Lyndon Nerenberg
2003-06-25 15:06 ` jmk [this message]
2003-06-25 19:09   ` Lyndon Nerenberg
2003-06-25 19:55   ` Lyndon Nerenberg
2003-06-25 20:10     ` David Presotto
2003-06-25 20:20       ` andrey mirtchovski
2003-06-25 20:35         ` jmk
2003-06-25 20:32       ` Lyndon Nerenberg
2003-06-25 20:32     ` ron minnich
2003-06-25 20:39       ` Lyndon Nerenberg
2003-06-25 20:42         ` Christopher Nielsen
2003-06-25 20:49         ` boyd, rounin
2003-06-25 21:04         ` ron minnich
2003-06-26  0:08           ` Lyndon Nerenberg
2003-06-25 20:41 jmk
2003-06-25 20:44 ` Lyndon Nerenberg

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=e305c715ab1abec77c4789469f7be51d@plan9.bell-labs.com \
    --to=jmk@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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).