public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "D. Stimits" <stimits@idcomm.com>
To: kernel-list <linux-kernel@vger.kernel.org>
Subject: Re: bzdisk broken in 2.4.5?
Date: Tue, 29 May 2001 01:36:06 -0600	[thread overview]
Message-ID: <3B135166.E061B01F@idcomm.com> (raw)
In-Reply-To: <3B12E8B4.238DCD11@idcomm.com>

"D. Stimits" wrote:
> 
> I've tried on two separate machines to test out 2.4.5 through the "make
> bzdisk" boot floppy, and it fails on both (the compile succeeds, but
> boot never gets to LILO, it simply gives "400" and a repeating list of
> AX, BX, CX, and DX registers). Both are scsi aic7xxx, but use different
> controllers, and have scsi directly compiled in. One machine is based on
> RH 7.1 beta, the other on RH 7.1. Both are x86 SMP, with motherboard and
> all hardware being different. Using the same kernel through a
> "mkbootdisk" works, only "make bzdisk" fails. Can anyone here verify
> that "make bzdisk" will create a bootable floppy (I did try an entire
> box of different floppies) on 2.4.5+? Especially, can anyone verify this
> for SMP and/or purely scsi machines? If scsi, do you use aic7xxx?
> 
> D. Stimits, stimits@idcomm.com

I found some references to bzdisk breaking in 2.3.28, followed by a fix.
Checking /usr/src/linux/arch/i386/boot/bootsect.S, the fix has remained
and has not been lost. See:
http://web.gnu.walfield.org/mail-archive/linux-kernel/1999-November/1818.html

However, something else must have changed since then to cause the image
size to go over its maximum. Has bzdisk being abandoned (or at least
ignored)?

D. Stimits, stimits@idcomm.com

      reply	other threads:[~2001-05-29  7:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-29  0:09 bzdisk broken in 2.4.5? D. Stimits
2001-05-29  7:36 ` D. Stimits [this message]

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=3B135166.E061B01F@idcomm.com \
    --to=stimits@idcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    /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