All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edgar Toernig <froese@gmx.de>
To: Pavel Machek <pavel@suse.cz>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org, vojtech@ucw.cz,
	Hamera Erik <HAMERAE@cs.felk.cvut.cz>
Subject: Re: Booting linux using Novell NetWare Remote Program Loader
Date: Thu, 13 Sep 2001 17:37:30 +0200	[thread overview]
Message-ID: <3BA0D2BA.8B972B51@gmx.de> (raw)
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>

[-- Attachment #1: Type: text/plain, Size: 325 bytes --]

Pavel Machek wrote:
> 
> > 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

Ciao, ET.

[-- Attachment #2: boot-diff --]
[-- Type: text/plain, Size: 1016 bytes --]

--- /usr/src/2.0.36/arch/i386/boot/bootsect.S	Sat Mar  9 12:31:42 1996
+++ /tmp/q/bootsect.S	Thu Aug 23 21:42:20 2001
@@ -102,6 +102,7 @@
 
 ! cx contains 0 from rep movsw above
 
+#if 0 /* ET: let the DPT alone */
 	mov	fs,cx
 	mov	bx,#0x78		! fs:bx is parameter table address
 	push	ds
@@ -124,6 +125,7 @@
 	mov	(bx),di
 	seg fs
 	mov	2(bx),es
+#endif
 
 ! load the setup-sectors directly after the bootblock.
 ! Note that 'es' is already set up.
@@ -170,6 +172,7 @@
 ! 36 sectors if sector 36 can be read, 18 sectors if sector 18 can be read,
 ! 15 if sector 15 can be read.  Otherwise guess 9.
 
+#if 0 /* ET: no autoprobing.  asume 1.44mb disk */
 	mov	si,#disksizes		! table of sizes to try
 
 probe_loop:
@@ -187,6 +190,7 @@
 	mov	ax,#0x0201		! service 2, 1 sector
 	int	0x13
 	jc	probe_loop		! try next value
+#endif
 
 #endif
 
@@ -438,10 +442,12 @@
 	ret
 
 sectors:
-	.word 0
+	.word 18
 
+#if 0 /* ET: no autoprobing.  fixed at 18 sectors */
 disksizes:
 	.byte 36,18,15,9
+#endif
 
 msg1:
 	.byte 13,10

  parent reply	other threads:[~2001-09-13 15:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-09 20:09 Booting linux using Novell NetWare Remote Program Loader Pavel Machek
2001-09-09 21:02 ` Benjamin LaHaise
2001-09-09 21:09   ` Pavel Machek
2001-09-10  1:41     ` H. Peter Anvin
2001-09-10 22:53       ` Pavel Machek
2001-09-13  5:33         ` Edgar Toernig
2001-09-13 10:07           ` Pavel Machek
2001-09-13 10:13             ` H. Peter Anvin
2001-09-13 15:37             ` Edgar Toernig [this message]
2001-09-13 19:56               ` Pavel Machek
2001-09-13 19:58                 ` H. Peter Anvin
2001-09-13 20:03                   ` Pavel Machek
2001-09-13 20:08                     ` H. Peter Anvin
2001-09-13 20:50                       ` Pavel Machek
2001-09-17 19:29                 ` ACPI and SCSI SirVer
2001-09-09 21:10   ` Booting linux using Novell NetWare Remote Program Loader Eric Lammerts
2001-09-13 15:13     ` Kai Henningsen
2001-09-13 22:46       ` Eric Lammerts
2001-09-10 13:20 ` Ross Vandegrift
2001-09-10 14:35   ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3BA0D2BA.8B972B51@gmx.de \
    --to=froese@gmx.de \
    --cc=HAMERAE@cs.felk.cvut.cz \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=vojtech@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.