From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
From: "Michael H. Collins" <mhtexcollins@austin.rr.com>
Message-ID: <3AC298A1.1080001@austin.rr.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
References: <20010327094451.8952E199DC@mail.cse.psu.edu>
Subject: Re: [9fans] Booting Plan9
Date: Thu, 29 Mar 2001 08:26:37 +0000
Topicbox-Message-UUID: 769f113e-eac9-11e9-9e20-41e7f4b1d025

I have sucessfully used many 3c905c cards.  The work no p.  Don't even 
have to spec the io and irq.

forsyth@vitanuova.com wrote:

>>

 normally 3C905 is a PCI card.  i'll see if i can find a 905C
> card here that's not in use, to test it.
> 
> 
> ------------------------------------------------------------------------
> 
> Subject:
> 
> [9fans] Booting Plan9
> Date:
> 
> Tue, 27 Mar 2001 08:25:42 GMT
> To:
> 
> cse.psu.edu!9fans
> 
> 
> Hi
>     I'm trying to install Plan9 on a new PC. I've got 3 partitions. Windows
> ME hogs the first two and I'm trying to install Plan 9 on the third
> partition (its about 30 GB).
>     The installation of Plan 9 goes through quite successfully. I have no
> problems with the VGA (ATI Xpert 98) and unpack proceeds well.
>     Finally at bootsetup I created a boot floppy and I also opted to boot
> from the disk. This does not work at all because the Windows ME idea of a
> boot record may be different from Windows 98 or NT.
>     However when I try to boot from the boot floppy it hangs after it says
> its booting the image from sdC0. The message I get is panic: kernel iunlock.
> I've looked at the code in code in /sys/src/boot/pc and I cannot find this
> message though there seem to be iunlocks associated with ethernet drivers.
>    I have a 3COM PCMCIA 3C905C lan card. Would this cause a problem?  The
> CPU is a 1.2 Gig Athlon.
> 
> S
> Part 1.1
> 
> Content-Type:
> 
> text/plain
> Content-Encoding:
> 
> 7bit
> 
> 
> ------------------------------------------------------------------------
> Part 1.2.1
> 
> 
> ------------------------------------------------------------------------
> Part 1.2
> 
> Content-Type:
> 
> message/rfc822