Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!netnews.upenn.edu!news.cc.swarthmore.edu!psuvax1!news.pop.psu.edu!news.cac.psu.edu!howland.reston.ans.net!cs.utexas.edu!utnut!helios.physics.utoronto.ca!jacques
From: jacques@helios.physics.utoronto.ca (Jacques Legare)
Subject: 1.1 won't boot on my 486 && slow access of pcfs volumes
Message-ID: <CsKz06.BD0@helios.physics.utoronto.ca>
Sender: news@helios.physics.utoronto.ca (News Administrator)
Organization: University of Toronto Physics/Astronomy/CITA
Date: Thu, 7 Jul 1994 17:24:05 GMT
Lines: 29
I have two things to report. BTW, all bugs refer to FreeBSD 1.1 (from the
CDROM).
1) I got the genericah boot disk (kcopy) from the CDROM release 1.1.
When I try to boot this disk on my 486 I only get as far as the
the message that says "text=<some hex addr> data=<another hex addr>"
After printing the data part of this message it simply reboots itself!
(Please, don't jump all over me if I got the message wrong in some
way since I haven't looked at it in a while and I don't want to
try right now.)
I imagine that if I left it alone the machine would reboot like this
forever.
Since the machine I am using was given to me I don't know much about
the board I have. Here is what I do know:
486 DX2/66 with 16M ram and a Phoenix Bios (barf sounds here)
The name on the front of the machine (which probably means nothing)
is BIT.
I am reasonably sure that none of the cards or peripherals is causing the
problem because I gutted the 486 and I am using all this stuff in
my 386 33 which boots FreeBSD just fine.
2) Anyone notice that accesses to a pcfs floppy are deathly slow.
Even worse a command like 'cp /mnt/drive-a/* /tmp' seems to be
uninteruptible and worse seems to prevent access to the target drive.