From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 22 Nov 2007 16:39:58 +0100 To: 9fans@cse.psu.edu Subject: Re: [9fans] panic Message-ID: <20071122153958.GB12286@lisa.galaxy> References: <20071121162925.GA14392@lisa.galaxy> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071121162925.GA14392@lisa.galaxy> From: frank@inua.be (Frank Lenaerts) Topicbox-Message-UUID: 08461926-ead3-11e9-9d60-3106f5b1d025 On Wed, Nov 21, 2007 at 05:29:26PM +0100, Frank Lenaerts wrote: Hi, Apart from the original problem (the panic), where should I put the plan9.ini style file when booting via PXE from a non-Plan 9 (e.g. Linux) box. Would 9pxeload look for the file in /cfg/pxe under the tftp root directory (e.g. /tftpboot)? > As this machine does not have a floppy drive and I do not want to burn > a new CD just to modify plan9.ini, I tried to boot the system using > PXE (from a Linux machine running a dhcp and tftp server). The > intention was to get 9pxeload to load a plan9.ini file from the Linux > machine and to then continue booting from the CD (i.e. trying to pass > the *noe820scan to the kernel). > > To do this, I did the following: > > - configured the dhcp server (MAC, filename...) > - put 9pxeload in place > - modified plan9.ini so that it contains *noe820scan and renamed it to > the MAC address of the NIC > > Booting the PC using PXE loads 9pxeload but the plan9.ini file is not > found: > > --- begin --- > initial probe, to find plan9.ini...pcirouting: ... > > Boot devices: fd0 > boot from: > --- end --- > > The 9load manpage says that the file should be put in /cfg/pxe (which > I then created under /tftpboot on the Linux box). I thought that > 9pxeload would request /cfg/pxe/ using TFTP but even that does > not seem to be the case i.e. it seems as if 9pxeload doesn't request > any file using TFTP... Could somebody explain me how it is supposed to > work? -- Frank Lenaerts ---------------------------------------- frank@inua.be