From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] Booting Plan9 From: forsyth@vitanuova.com MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-unfrocejcxkwqpcqvqmalnxfyg" Message-Id: <20010327094451.8952E199DC@mail.cse.psu.edu> Date: Tue, 27 Mar 2001 09:52:25 +0100 Topicbox-Message-UUID: 74401762-eac9-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-unfrocejcxkwqpcqvqmalnxfyg Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit >>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. it's not so much the boot record as the config.sys and other files that aren't used in ME. it just occurred to me that the bootwinnt option (see /sys/lib/pcdist/inst/bootwinnt) updates a file boot.ini instead; perhaps that's usable on ME. i haven't got my ME machine with me to experiment. >> 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. panic: iunlock is there. is it really `kernel iunlock'? >> I have a 3COM PCMCIA 3C905C lan card. Would this cause a problem? The >>CPU is a 1.2 Gig Athlon. is it really PCMCIA? the only PCMCIA 3com cards supported (i believe) are 3c589, 3c562 and some minor variants. 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. --upas-unfrocejcxkwqpcqvqmalnxfyg Content-Type: message/rfc822 Content-Disposition: inline Return-Path: <9fans-admin@cse.psu.edu> Received: from punt-1.mail.demon.net by mailstore for forsyth@vitanuova.com id 985683024:10:14049:1; Tue, 27 Mar 2001 08:50:24 GMT Received: from psuvax1.cse.psu.edu ([130.203.4.6]) by punt-1.mail.demon.net id aa1013777; 27 Mar 2001 8:50 GMT Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.20.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 76F9B19A04; Tue, 27 Mar 2001 03:49:30 -0500 (EST) Received: from mercury.bath.ac.uk (mercury.bath.ac.uk [138.38.32.81]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 39983199DC for <9fans@cse.psu.edu>; Tue, 27 Mar 2001 03:48:46 -0500 (EST) Received: from news by mercury.bath.ac.uk with local (Exim 3.12 #1) id 14hooF-0004wx-00 for 9fans@cse.psu.edu; Tue, 27 Mar 2001 09:26:35 +0100 Received: from GATEWAY by bath.ac.uk with netnews for 9fans@cse.psu.edu (9fans@cse.psu.edu) To: cse.psu.edu!9fans Message-ID: <99o9i0$4oq@nntpa.cb.lucent.com> Organization: Lucent Technologies, Columbus, Ohio Subject: [9fans] Booting Plan9 Sender: cse.psu.edu!9fans-admin Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.1 Precedence: bulk Reply-To: cse.psu.edu!9fans List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Tue, 27 Mar 2001 08:25:42 GMT 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 --upas-unfrocejcxkwqpcqvqmalnxfyg--