New AMD64 owner

[Adriaan de Groot]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 29 January 2004 14:13, Brian Tao wrote:
> installed to do some burn-in testing, presumably).  If this is the
> case, why am I seeing references to broken ia32 compatibility?
> Shouldn't that "just work"?  Or is this a kernel/loader issue with a
> 64-bit aware install?

It's a kernel/loader issue, mostly. The stack layout is very different in 64
bit mode than in 32 bit mode (or so I gather from messages from DAvid &
James). This means that when running 32 bit apps, the stack needs to be
treated differently, and the kernel doesn't do that right (yet).

>     Related to the previous question:  should I be able to install
> either freebsd-i386 or freebsd-amd64, and both will work?  Obviously

Well, i386 will work. amd64 YMMV.

> the i386 install will run in 32-bit mode, but at least it will run
> (and act as a really fast Intel box, I'm hoping).  Or is there

It's been said several times on this list that running an amd64 as an i386
works quite well and _is_ really fast. I can't confirm that, though.

>     The Tyan motherboard has an onboard Silicon Image 3114 S-ATA
> adapter.  I have two WD Raptor drives attached.  The aforementioned

SATA seems to be the primary source of woe on this list right now. Check the
archives a little. For me, with a consumer-grade asus k8v, everything just
worked.

- --
pub  1024D/FEA2A3FE 2002-06-18 Adriaan de Groot <groot at kde.org>
            If the door is ajar, can we fill it with door-jamb?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFAGQlTdqzuAf6io/4RAnAqAJ0cE6YtQ99gbh1wfDxnN0kjaJ1lhwCfTzbh
saxmorQNUDjbEFNFY2eSMNc=
=dED6
-----END PGP SIGNATURE-----