Re: various rants about 7-currnet on AMD64

On 10/1/07, Astrodog <astrodog@xxxxxxxxx> wrote:
First, i386 arches do not properly support 4GB of memory without PAE.
The set of issues you will encounter without dealing with this first
is somewhat unpredictable... though performance issues, broken
hardware, etc is certainly possible.

I had tried PAE before the upgrade (see "what cpu type to use for a
intel duo e6850 (i386 or amd64)" in -questions for detail)... I had
also tried removing a DIMM... none resolved any issues.


The ports issue is known. You might be interested in lookup up 32-bit
compat on FreeBSD.

Since I am brand new to amd64 can give me a ptr to the right docs?


The CPUTYPE is amd64 because at the time the instruction set was
invented, and FreeBSD began supporting it, Intel had no plans to offer
support for it, it was an AMD-only offering. Intel decided to support
it, *after* the project did all of the fun work involved in supporting
it, including naming everything amd64.

That doesn't negate the confusion... perhaps just mentioning that it
works for all x86 and multi core x86 should suffice in hardware.txt
and prominently in some place that newbies will see it.


AMD64 as an arch isn't always suitable for systems. Its load specific.

I think since it is clear that at least on a p35 mobo it is the only
suitable one we may want to consider saying something.


In as far as nvidia.ko, and nv are concerned, I've run both of them
without problems, on a wide range of hardware. You do need to make
sure they're binding, instead of vesa, though. (Simply replace "vesa"
with "nv" or "nvidia" in your xorg.conf)


I assume this is under 32 bit compat?
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: 7.0 BETA4 unstable on MSI AM2 motherboard
    ... But I've now bought some new hardware for use as a fileserver and this new hardware doesn't work very well with 7.0. ... I've tested the 7.0 and 8.0 installations with both AMD64 and i386 installations and none work. ... Errors about wrong fileformat when loading shared libraries. ... I used a cheap Silicon Image 3114 32-bit PCI SATA controller while the HT1000 SATA problems were being worked out. ...
    (freebsd-current)
  • Re: AMD64 much slower than i386 on FreeBSD 5.4-pre
    ... Very slow for amd64 build. ... > various hardware, that might be useful. ... > wonder if the irq rates are changing, or irqs are ... > To unsubscribe, send any mail to ...
    (freebsd-questions)
  • Re: 7.0 BETA4 unstable on MSI AM2 motherboard
    ... But I've now bought some new hardware for use as a fileserver and this new hardware doesn't work very well with 7.0. ... These have all been AMD64 versions. ... Errors about wrong fileformat when loading shared libraries. ... I used a cheap Silicon Image 3114 32-bit PCI SATA controller while the HT1000 SATA problems were being worked out. ...
    (freebsd-current)
  • Re: [PATCH 0/6] MSI portability cleanups
    ... the problem of supporting the crazy hypervisor on the ppc RTAS, ... asks us to drive the hardware but does not give us access to the ... I see people pushing ridiculous interfaces like the RTAS hypervisor ... I don't mind supporting poorly designed hypervisor interfaces, ...
    (Linux-Kernel)
  • 7.0 BETA4 unstable on MSI AM2 motherboard
    ... I thought I would write here before I made a problem report. ... But I've now bought some new hardware for use as a fileserver and this new hardware doesn't work very well with 7.0. ... These have all been AMD64 versions. ... Errors about wrong fileformat when loading shared libraries. ...
    (freebsd-current)