Date: Mon, 12 Jul 2004 20:07:52 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Kenneth Christie <kenchristie@ntlworld.com> Cc: freebsd-questions@freebsd.org Subject: Re: Installation 4-10 Stable - Fatal Trap 12 Message-ID: <20040712190752.GB64570@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <000901c4683e$e53cbac0$13f889d9@GLAZHITBAS> References: <000901c4683e$e53cbac0$13f889d9@GLAZHITBAS>
next in thread | previous in thread | raw e-mail | index | archive | help
--FkmkrVfFsRoUs1wW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Jul 12, 2004 at 07:34:19PM +0100, Kenneth Christie wrote:
> I cannot get past the attached message when trying to install Free BSD 4.=
10 stable. Can you give me an indication as to what the problem might be ? =
(I am totally new to Unix, and was wanting to install Free BSD to learn abo=
ut it. I have searched the FAQs but without coming across a similar message=
, although one did suggest disabling ACPI during the installation. How woul=
d I do this if this is what I need to do ?).
Please enhance your karma by hitting the return key every 72 or so
characters.
Sorry -- you attachment was eaten by the attachment eater. Only
certain MIME types are permitted on the FreeBSD mailing lists.
However I can say confidently that trying to disable ACPI on a 4.10
install won't work. There isn't any ACPI support turned on by default
in 4.x: all of the advice about turning off ACPI applies to 5.x, and
in that case, the installation procedure is a bit different and gives
you that choice fairly early on.
Fatal Trap 12 means "non-existent system call invoked". Seeing it
while attempting to boot a kernel either means that the kernel is
broken, or that you have hardware problems. In the first instance,
you could have a corrupt kernel image on your installation media. If
you're trying to install from floppy disks, throw away any disks
you've been using and try again with some nice new fresh from the
manufacturer floppies. Otherwise, if you're using one of the .iso
images, try checking the md5 checksum to make sure everything came
down OK.
Knowing as little about Windows as I do, I have no reliable idea about
how to do that. However a little googling pulled up this page, which
looks like just the ticket:
http://www.fastsum.com/
If on the other hand, it's a hardware problem then you'll have to work
out if your system is faulty. That's something you tend to learn how
to deal with through experience and not something easily described in
a simple e-mail like this. Of course, it could be that you have
hardware which simply isn't supported under FreeBSD 4.10 -- most of
the time FreeBSD will simply igore kit it doesn't know how to drive,
but if it's something important like the disk controller all bets are
off. Try comparing your system against the lists of devices in the
4.10 Hardware Notes:
http://www.freebsd.org/releases/4.10R/hardware-i386.html
Also search the FreeBSD mailing lists for other mentions of your
particular brand of system (or of the motherboard in your system) --
some makes have specific settings that need to be in the BIOS before
they will work with FreeBSD. A good interface for searching FreeBSD
mailing lists is available at:
http://freebsd.rambler.ru/
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
--FkmkrVfFsRoUs1wW
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFA8uGIiD657aJF7eIRAh1ZAKCxEfeOieW95LQk25vyOTxTJddg5ACgtJkB
dr4MJnz5a9pE2O8ortKmF1g=
=tWpV
-----END PGP SIGNATURE-----
--FkmkrVfFsRoUs1wW--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040712190752.GB64570>