From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 13 Sep 2001 15:59:02 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 13 Sep 2001 15:58:52 -0400 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:10756 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Thu, 13 Sep 2001 15:58:44 -0400 Message-ID: <3BA10FFA.1050204@zytor.com> Date: Thu, 13 Sep 2001 12:58:50 -0700 From: "H. Peter Anvin" Organization: Zytor Communications User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3+) Gecko/20010905 X-Accept-Language: en, sv MIME-Version: 1.0 To: Pavel Machek CC: Edgar Toernig , linux-kernel@vger.kernel.org, vojtech@ucw.cz, Hamera Erik Subject: Re: Booting linux using Novell NetWare Remote Program Loader In-Reply-To: <20010909220921.A19145@bug.ucw.cz> <20010909170206.A3245@redhat.com> <20010909230920.A23392@atrey.karlin.mff.cuni.cz> <9nh5p0$3qt$1@cesium.transmeta.com> <20010911005318.C822@bug.ucw.cz> <3BA04514.D65EDF98@gmx.de> <20010913120706.C25204@atrey.karlin.mff.cuni.cz> <3BA0D2BA.8B972B51@gmx.de> <20010913215617.E6820@atrey.karlin.mff.cuni.cz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Pavel Machek wrote: > Hi! > >>>>I removed the autoprobing from bootsect.S and fixed it to 1.44MB format >>>>et voila, it worked perfectly. >>>> >>>Do you have patch to do that? >>> >>I have a patch for 2.0.x only. But it should be enough to change the >>disksizes table at the end of bootsect.S to: >> >>disksizes: .byte 18,18,18,18 >> > > Yep, tried that. No more crc errors when decompressing. Instead, > sudden reboot when it finishes loading. OOps. > > This is 486sx/25 booting from network. Kernel is 2.4.9, compiled with > math emu, and processor=386. Any ideas what is wrong? > Pavel Am I guessing correctly that this RPL thing is a floppy image emulator? Then it probably becomes a matter of where that image lives (in memory, if so where; or on the network and downloaded sector by sector.) You may want to try to make a SYSLINUX image and see if it works. -hpa