From nobody@FreeBSD.ORG  Tue Aug 22 01:12:38 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 4F67C37B424; Tue, 22 Aug 2000 01:12:38 -0700 (PDT)
Message-Id: <20000822081238.4F67C37B424@hub.freebsd.org>
Date: Tue, 22 Aug 2000 01:12:38 -0700 (PDT)
From: dragona@interaccess.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: Cannot boot the install floppy for version 4.1
X-Send-Pr-Version: www-1.0

>Number:         20776
>Category:       kern
>Synopsis:       Cannot boot the install floppy for version 4.1
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    rnordier
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Aug 22 01:20:00 PDT 2000
>Closed-Date:    Sun May 27 13:25:19 PDT 2001
>Last-Modified:  Sun May 27 13:29:33 PDT 2001
>Originator:     Derek Ragona
>Release:        4.1
>Organization:
Computing Innovations
>Environment:
I cannot boot to get this information
>Description:
When I try to boot the boot 4.1 floppy, the bootstrap loader cannot resolve which disk it is booting from.  Yet, I am loading the bootstrap from the floppy, which then the bootstrap cannot find to load the boot from.  Somehow the bootstrap is not finding the floppy drive from which it is loading itself.  This doesn't seem to make sense.

This is a VL-bus motherboard running a Pentium 60 CPU, 64 MB RAM, floppy controller on the motherboard, Adaptec 2840 SCSI card, 2 SCSI hard disks, 2 SCSI CD-ROM disks, 1 SCSI 4mm DAT tape drive.

Here is the entire messages that are displayed:
==============================================================
BTX Loader 1.00 BTX version is 1.01
Console: internal video/keyboard
BIOS drive C: is disk0
BIOS drive D: is disk1
BIOS 639KB/1070100KB available memory

FreeBSD/i386 bootstrap loader, Revision 0.8
(jkh@ref4.freebsd.org, Fri Jul 28 12:39:58 GMT 2000)
can't workout which disk we are booting from
Guessed BIOS device 0x0 not found by probes, defaulting to disk0
Hit [Enter] to boot immediately or any key for command prompt
Booting [Kernel] . . .
can't load 'kernel'
can't load 'kernel.old'

type '?' for a list of commands, 'help' for more detailed help
ok
===============================================================
>How-To-Repeat:
Simply put in the boot floppy and boot the PC.
>Fix:


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: sheldonh 
State-Changed-When: Tue Aug 22 07:38:06 PDT 2000 
State-Changed-Why:  
Smells like BIOS configuration.  Are you sure that the floppy 
is enabled in the BIOS, that the floppy isn't "swapped" by 
the BIOS and that the floppy is the first device probed 
by the BIOS in the boot order? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=20776 

From: Sheldon Hearn <sheldonh@uunet.co.za>
To: Derek Ragona <dragona@interaccess.com>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: kern/20776: Cannot boot the install floppy for version 4.1 
Date: Tue, 22 Aug 2000 17:53:52 +0200

 On Tue, 22 Aug 2000 10:40:09 EST, Derek Ragona wrote:
 
 > I experimented with the two floppies, mfsroot, and boot floppy.
 
 Experimented?  What were you using before, boot.flp?  Do you really have
 such a high capacity floppy drive?
 
 Also, what kind of floppy drive do you have?  Nothing special?
 
 Ciao,
 Sheldon.
 

From: Derek Ragona <dragona@interaccess.com>
To: Sheldon Hearn <sheldonh@uunet.co.za>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: kern/20776: Cannot boot the install floppy for version 4.1 
Date: Tue, 22 Aug 2000 11:37:45 -0500

 I have been using boot.flp and mfsroot.flp, both from the 4.1 CD.  These
 are "good" floppies, as I have used them to load another system.
 
 The floppy is a teac 1.44 MB standard drive.  
 
 	-Derek
 
 At 05:53 PM 8/22/00 +0200, Sheldon Hearn wrote:
 >
 >
 >On Tue, 22 Aug 2000 10:40:09 EST, Derek Ragona wrote:
 >
 >> I experimented with the two floppies, mfsroot, and boot floppy.
 >
 >Experimented?  What were you using before, boot.flp?  Do you really have
 >such a high capacity floppy drive?
 >
 >Also, what kind of floppy drive do you have?  Nothing special?
 >
 >Ciao,
 >Sheldon.
 >
 >
 

From: Derek Ragona <dragona@interaccess.com>
To: Sheldon Hearn <sheldonh@uunet.co.za>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: kern/20776: Cannot boot the install floppy for version 4.1 
Date: Tue, 22 Aug 2000 18:47:26 -0500

 Sheldon,
 
 I had a thought.  The system has an Adaptec 2840 SCSI adapter, and perhaps
 the bootstrap sees the SCSI adapter, and expects the floppies to be
 connected to it (which could be the case if a 2842 were used, and the
 floppy controller on it enabled) and doesn't probe further to the
 motherboard floppy controller.
 
 	-Derek
 
 At 05:53 PM 8/22/00 +0200, Sheldon Hearn wrote:
 >
 >
 >On Tue, 22 Aug 2000 10:40:09 EST, Derek Ragona wrote:
 >
 >> I experimented with the two floppies, mfsroot, and boot floppy.
 >
 >Experimented?  What were you using before, boot.flp?  Do you really have
 >such a high capacity floppy drive?
 >
 >Also, what kind of floppy drive do you have?  Nothing special?
 >
 >Ciao,
 >Sheldon.
 >
 >
 

From: Johan Karlsson <k@numeri.campus.luth.se>
To: Derek Ragona <dragona@interaccess.com>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: kern/20776: Cannot boot the install floppy for version 4.1 
Date: Wed, 23 Aug 2000 10:20:07 +0200

 At Tue, 22 Aug 2000 09:40:04 PDT, Derek Ragona wrote:
 > The following reply was made to PR kern/20776; it has been noted by GNATS.
 > 
 > From: Derek Ragona <dragona@interaccess.com>
 > To: Sheldon Hearn <sheldonh@uunet.co.za>
 > Cc: freebsd-gnats-submit@freebsd.org
 > Subject: Re: kern/20776: Cannot boot the install floppy for version 4.1 
 > Date: Tue, 22 Aug 2000 11:37:45 -0500
 > 
 >  I have been using boot.flp and mfsroot.flp, both from the 4.1 CD.  These
 >  are "good" floppies, as I have used them to load another system.
 >  
 >  The floppy is a teac 1.44 MB standard drive.  
 
 You should be using 'kern.flp' and 'mfsroot.flp' which are for 1.44MB drives.
 
 'boot.flp' is for 2.88MB drives.
 
 /Johan K 
 

From: Derek Ragona <dragona@interaccess.com>
To: Johan Karlsson <k@numeri.campus.luth.se>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: kern/20776: Cannot boot the install floppy for version 4.1 
Date: Wed, 23 Aug 2000 05:08:22 -0500

 Sorry, I typed the wrong image name.  I am using the two 1.44 images.
 
 	-Derek
 
 At 10:20 AM 8/23/00 +0200, Johan Karlsson wrote:
 >At Tue, 22 Aug 2000 09:40:04 PDT, Derek Ragona wrote:
 >> The following reply was made to PR kern/20776; it has been noted by GNATS.
 >> 
 >> From: Derek Ragona <dragona@interaccess.com>
 >> To: Sheldon Hearn <sheldonh@uunet.co.za>
 >> Cc: freebsd-gnats-submit@freebsd.org
 >> Subject: Re: kern/20776: Cannot boot the install floppy for version 4.1 
 >> Date: Tue, 22 Aug 2000 11:37:45 -0500
 >> 
 >>  I have been using boot.flp and mfsroot.flp, both from the 4.1 CD.  These
 >>  are "good" floppies, as I have used them to load another system.
 >>  
 >>  The floppy is a teac 1.44 MB standard drive.  
 >
 >You should be using 'kern.flp' and 'mfsroot.flp' which are for 1.44MB drives.
 >
 >'boot.flp' is for 2.88MB drives.
 >
 >/Johan K 
 >
 >
 

From: Sheldon Hearn <sheldonh@uunet.co.za>
To: Derek Ragona <dragona@interaccess.com>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: kern/20776: Cannot boot the install floppy for version 4.1 
Date: Wed, 23 Aug 2000 14:03:24 +0200

 On Wed, 23 Aug 2000 03:20:05 MST, Derek Ragona wrote:
 
 >  Sorry, I typed the wrong image name.  I am using the two 1.44 images.
 
 I'm not sure how to help you beyond this point.  This isn't something
 that a lot of people are complaining about.  I'm pretty sure that I've
 seen one other report like this, where the maintainer of the bootstrap
 code basically said that if the originator couldn't get his floppy
 probed, his BIOS was misbehaving and there wasn't much he could do with
 the floppy.
 
 Ciao,
 Sheldon.
 
Responsible-Changed-From-To: freebsd-bugs->rnordier 
Responsible-Changed-By: rnordier 
Responsible-Changed-When: Thu Aug 24 10:08:22 PDT 2000 
Responsible-Changed-Why:  
I'll handle this. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=20776 

From: "M. B. BUCHANAN" <buchanan@orbitworld.net>
To: freebsd-gnats-submit@FreeBSD.org, dragona@interaccess.com
Cc:  
Subject: Re: kern/20776: Cannot boot the install floppy for version 4.1
Date: Thu, 14 Dec 2000 21:51:52 -0600 (CST)

 I've had a similar problem with the 4.1 and 4.2 kern.flp images.  It must
 be something that's changed in the image between 3.4-R and 4.1-R, because
 3.4-R is the last version I've installed on my problem box.  Here's the
 relevant info:
 
 The CPU is a 486DX4-120.
 
 It's also a VL-bus, and I believe the floppy controller is on the 
 motherboard.
 
 Note that 'lsdev' can't read the disklabel on the floppy.
 
 ==============================================================
 BTX Loader 1.00 BTX version is 1.01
 Console: internal video/keyboard
 BIOS drive A: is disk0
 BIOS drive C: is disk1
 BIOS 639KB/31744kB available memory
 
 FreeBSD/i386 bootstrap loader, Revision 0.8
 (jkh@bento.FreeBSD.org, Mon Nov 20 11:41:23 GMT 2000)
 
 Hit [Enter] to boot immediately, or any other key for command prompt.
 Booting [kernel]...
 can't load 'kernel'
 can't load 'kernel.old'
 
 type '?' for a list of commands, 'help' for more detailed help
 ok ls
 open '/' failed: input/output error
 ok lsdev
 disk @ 0x10918
     disk0:   BIOS drive A:
     disk1:   BIOS drive C:
         disk1s1a: FFS  32MB (0 - 65536)
         disk1s2a: swap  73MB (65536 - 216640)
         disk1s1e: FFS  30MB (216640 - 278080)
         disk1s1f: FFS 3998MB (278080 - 8467200)
 pxe @ 0xef70
 ok
 ===============================================================
 
 Copyright (c) 1992-1999 FreeBSD Inc.
 Copyright (c) 1982, 1986, 1989, 1991, 1993
         The Regents of the University of California. All rights reserved.
 FreeBSD 3.4-RELEASE #0: Sat Jan 29 19:31:02 CST 2000
     buchanan@booger.mbb.org:/usr/src/sys/compile/V20000129
 Timecounter "i8254"  frequency 1193182 Hz
 CPU: AMD Enhanced Am486DX4 Write-Back (486-class CPU)
   Origin = "AuthenticAMD"  Id = 0x494  Stepping = 4
   Features=0x1<FPU>
 real memory  = 33554432 (32768K bytes)
 avail memory = 30294016 (29584K bytes)
 Preloaded elf kernel "kernel" at 0xc027c000.
 Probing for devices on the ISA bus:
 sc0 on isa
 sc0: VGA color <16 virtual consoles, flags=0x0>
 ed0 at 0x340-0x35f irq 15 on isa
 ed0: address 00:c0:f0:02:cb:44, type NE2000 (16 bit) 
 atkbdc0 at 0x60-0x6f on motherboard
 atkbd0 irq 1 on isa
 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
 sio0: type 16450
 sio1 at 0x2f8-0x2ff irq 3 on isa
 sio1: type 16450
 sio2 at 0x3e8-0x3ef irq 5 on isa
 sio2: type 16550A
 sio3 at 0x2e8-0x2ef irq 9 on isa
 sio3: type 16550A
 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
 fd0: 1.44MB 3.5in
 wdc0 at 0x1f0-0x1f7 irq 14 on isa
 wdc0: unit 0 (wd0): <QUANTUM BIGFOOT_CY4320A>
 wd0: 4134MB (8467200 sectors), 8960 cyls, 15 heads, 63 S/T, 512 B/S
 mcd0: type Mitsumi FX001D, version info: D 2
 mcd0 at 0x300-0x303 irq 10 on isa
 ppc0 at 0x378 irq 7 on isa
 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
 npx0 on motherboard
 npx0: INT 16 interface
 
 
State-Changed-From-To: feedback->closed 
State-Changed-By: rnordier 
State-Changed-When: Sun May 27 13:25:19 PDT 2001 
State-Changed-Why:  
Stale and unable to reproduce: if this is still an issue, please 
submit a fresh PR. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=20776 
>Unformatted:
