From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <40E95601.50900@place.org>
Date: Mon,  5 Jul 2004 06:22:09 -0700
From: Stephen Wynne <stevemw@place.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7) Gecko/20040616
MIME-Version: 1.0
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Virtual PC + Toshiba Tecra 8100 (SavageMX) vgadb entry
	and	vgainfo.txt
References: <40E6E4F3.8030306@place.org>
In-Reply-To: <40E6E4F3.8030306@place.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: b50a5efc-eacd-11e9-9e20-41e7f4b1d025

Interesting quandry: if I attach the plan9.iso to a Virtual PC
instance, it can boot it up and run the installer. That kernel
can see the NIC, which is evidently emulating a 2114x, but
then can't find disk/kfs* commands.

I rebuilt 9pcflop.gz from a fresh install on a normal PC but
while it can see the NIC when it boots, it can't deal with
my VGA controller, which I had hacked around by recognizing
VIDEO B, etc... The vgainfo.txt is a lot less informative.

Shouldn't 9pcflop.gz be very similar to what I get when I
download?

I guess I'm building different kernels, but I'm not sure what
to do next.

I'm curious what will happen once I finally get serious
about talking to the outside world with this NIC. I
see:

    #l0: 21140: 0Mbps port 0xEC00 irq 11: 0003FF9A5B41

at boot. I've tried a couple of quick "experiments" (like batting
in the dark to you scientists) with the ip/ping command. I've
tried NAT and direct connection to the network. It looks like
I'll have to have /lib/ndb/local fixed up first.