public inbox for linux-kernel@vger.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 07:33:08 +0200	[thread overview]
Message-ID: <3BA04514.D65EDF98@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>

Pavel Machek wrote:
> 
> I found out I can boot it after little games with mars netware
> emulator. However I have problems booting anything else than
> freedos. Trying to boot zImage directly results in crc errors or in
> errors in compressed data. Too much failures and too repeatable
> (althrough ram seems flakey) for me to believe its hw.

I bet that's the same problem I had booting a zImage directly from an
El-Torito CD.  The problem was the autoprobing for the floppy type
performed by the boot loader.  It detected a 2.88 drive and issued
corresponding read requests (track x, 36 blocks; track x+1, 36 blocks;
...).  The bios performs these request, but it emulates a 1.44 disk so
the last 18 blocks of track x are actually the blocks from track x+1.
In my case I did not even got a crc error but an immediate reboot.

I removed the autoprobing from bootsect.S and fixed it to 1.44MB format
et voila, it worked perfectly.

Ciao, ET.

PS: Maybe that's the same problem lilo has on some systems with the
linear option...

  reply	other threads:[~2001-09-13  5:42 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 [this message]
2001-09-13 10:07           ` Pavel Machek
2001-09-13 10:13             ` H. Peter Anvin
2001-09-13 15:37             ` Edgar Toernig
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=3BA04514.D65EDF98@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox