Bug 16901

Summary: cannot boot 3.4 floppies
Product: Base System Reporter: dragona <dragona>
Component: miscAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description dragona 2000-02-22 06:20:01 UTC
I have a ISA/VL bus motherboard, with an Adaptec 284X SCSI adapter, 2 SCSI harddisks, no IDE drives.  The kern floppy does not recognize the floppy drive, and won't boot from it.  Yet, it is the same drive I made the floppies on.

How-To-Repeat: Try to boot the floppies.
Comment 1 jmd526 2000-02-23 23:02:49 UTC
I have the same sort of problem.

When I boot from the kern floppy my system hangs after the following is
printed to the screen:
===============================================
/boot.config: -P
Keyboard: no
-
BTX loader 1.00   BTX version is 1.01
===============================================
My system is an Acer Aspire PIII 450, 128MB RAM, 8GB HD with the following
hardware:
   Human Interface Devices (HID) USB mouse and keyboard
         (*NOTE* only USB keyboard - no PS/2 or AT-style ports)

   Intel 82443BX Pentium II Processor to PCI bridge
   Intel 82443BX Pentium II Process to AGP Controller

   Intel 82371AB/EB PCI to USB Universal Host Controller
   Intel 82371EB PCI to ISA bridge (ISA mode)
   Intel 82371AB/EB PCI Bus Master IDE Controller
   Intel 82371AB/EB Power Management Controller
(the Intel 82371AB/EB architecture is specifically supported according to
the hardward notes at freeBSD.org)

   ATI XPERT 98 Display adapter
   Mitsubishi Diamond Plus 70 Monitor

   ESS Solo-1 Soundblaster sound card

   Advanced Configuration and Power Interface (ACPI) BIOS

   Acer 56K DataFax PCI Modem

   3com FastEtherlink XL 10/100MB TX Ethernet NIC (3C905B-TX)

   Hitachi DVD-ROM GD-2500

   Generic IDE Harddisk and Floppy disk

First: It's my understanding that USB is supported so I don't understand why
I get the message "Keyboard: no."  Second: Everything seems to go well for
2-3 minutes: the drive is humming, I get messages on the screen, etc but
then the baton stops turning, the floopy stops (I guess it has finished
reading) and nothing happens.

NOTE  I have the second floppy disk: mfsroot and I have tried putting it
into the drive after a couple of minutes of inactivity (despite not being
prompted to do so) but nothing happens (even after hitting return a few
times).

What is the correct behavior?  Shouldn't there be a prompt for the second
disk?

FYI: I am a "newbie," and have done extensive reading about FreeBSD over teh
last few days.  I am very excited about getting freeBSD but I never thought
I would have problems this early in the install process.  I have used
VAX/VMS and Win95/98/NT for many years.  I was going to use Redhat but,
Linux doesn't support USB.  This appears to be a lucky coincidence, however,
since FreeBSD seems to be *much* better (more stable, more central and
coherent development, easier (PORTS), possibly a better license for
developers, etc.)  FreeBSD seems to be the best-kept secret in "free"
operating systems!

John

John
Comment 2 jmd526 2000-02-29 14:29:51 UTC
I have the same sort of problem.

When I boot from the kern floppy my system hangs after the following is
printed to the screen:
===============================================
/boot.config: -P
Keyboard: no
-
BTX loader 1.00   BTX version is 1.01
===============================================
My system is an Acer Aspire PIII 450, 128MB RAM, 8GB HD with the following
hardware:
   Human Interface Devices (HID) USB mouse and keyboard
         (*NOTE* only USB keyboard - no PS/2 or AT-style ports)

   Intel 82443BX Pentium II Processor to PCI bridge
   Intel 82443BX Pentium II Process to AGP Controller

   Intel 82371AB/EB PCI to USB Universal Host Controller
   Intel 82371EB PCI to ISA bridge (ISA mode)
   Intel 82371AB/EB PCI Bus Master IDE Controller
   Intel 82371AB/EB Power Management Controller
(the Intel 82371AB/EB architecture is specifically supported according to
the hardward notes at freeBSD.org)

   ATI XPERT 98 Display adapter
   Mitsubishi Diamond Plus 70 Monitor

   ESS Solo-1 Soundblaster sound card

   Advanced Configuration and Power Interface (ACPI) BIOS

   Acer 56K DataFax PCI Modem

   3com FastEtherlink XL 10/100MB TX Ethernet NIC (3C905B-TX)

   Hitachi DVD-ROM GD-2500

   Generic IDE Harddisk and Floppy disk

First: It's my understanding that USB is supported so I don't understand why
I get the message "Keyboard: no."  Second: Everything seems to go well for
2-3 minutes: the drive is humming, I get messages on the screen, etc but
then the baton stops turning, the floopy stops (I guess it has finished
reading) and nothing happens.

NOTE  I have the second floppy disk: mfsroot and I have tried putting it
into the drive after a couple of minutes of inactivity (despite not being
prompted to do so) but nothing happens (even after hitting return a few
times).

What is the correct behavior?  Shouldn't there be a prompt for the second
disk?

FYI: I am a "newbie," and have done extensive reading about FreeBSD over teh
last few days.  I am very excited about getting freeBSD but I never thought
I would have problems this early in the install process.  I have used
VAX/VMS and Win95/98/NT for many years.  I was going to use Redhat but,
Linux doesn't support USB.  This appears to be a lucky coincidence, however,
since FreeBSD seems to be *much* better (more stable, more central and
coherent development, easier (PORTS), possibly a better license for
developers, etc.)  FreeBSD seems to be the best-kept secret in "free"
operating systems!

John

John
Comment 3 Alfred Perlstein freebsd_committer freebsd_triage 2000-06-06 10:23:50 UTC
State Changed
From-To: open->feedback

Needs more input from user, can you please provide more information 
such as motherboard type and floppy drive type?  Can you boot any 
other type of boot disks? 

How far does the boot get before failing?
Comment 4 nbm freebsd_committer freebsd_triage 2000-08-06 20:36:42 UTC
State Changed
From-To: feedback->closed

Feedback timeout - submission didn't give enough information to 
diagnose.