FYI, I've switched my primary desktop to AMD64.

Adriaan de Groot adridg at cs.kun.nl
Sat Oct 18 05:13:08 PDT 2003


On Friday 17 October 2003 19:17, Peter Wemm wrote:
> I finally worked up the nerve to commit to eating my own dogfood.  :-)

Well that's excellent news! It seems the CPUs have also arrived here in .nl, 
and I'll be getting my devel box (K8V, amd64 3200+, matrox g450) shortly.

> I'm using an older nvidia geforce4 ti4200 for the video, so I had to fix
> a misconfiguration in the Xserver (I forgot to have it open /dev/io).  The
> previous cards I'd used were all matrox which were solely mmio driven and
> didn't run into this problem.

Good to know that X works with matrox properly already. If you need some other 
testing, I can borrow a radeon 9800 as well.


> I've been working on getting mozilla-firebird up and running but that is
> easier said than done because the core infrastructure (nspr, xpcom etc)
> haven't got official support for amd64 yet.  There are patches in the

My intention - KDE-FreeBSD core team - is to get KDE in its entirety working 
as well on amd64 as on x86. 

> real memory  = 1072955392 (1023 MB)
> avail memory = 1011191808 (964 MB)

There isn't anything out there that supports more than 4G memory, is there? 

> fxp0: <Intel 82559 Pro/100 Ethernet> port 0xdf00-0xdf3f mem
> 0xfc800000-0xfc8fffff,0xfc9fe000-0xfc9fefff irq 11 at device 5.0 on pci1
> fxp0: Ethernet address 00:d0:b7:21:31:94

I take it this means that the nforce3 integrated nvidia NIC is still not 
working? This was one of the reasons for me to go with a VIA chipset board.

> atapci1: <Promise PDC20378 SATA150 controller> port
> 0xdc00-0xdc7f,0xdf60-0xdf6f,0xde80-0xdebf mem
> 0xfc9a0000-0xfc9bffff,0xfc9fd000-0xfc9fdfff irq 11 at device 8.0 on pci1

I think the K8V also uses promise sata, so that ought to go well for me too.

> pcib2: <ACPI PCI-PCI bridge> at device 11.0 on pci0
> pcib2: could not get PCI interrupt routing table for \\_SB_.PCI0.P0P2 -
> AE_NOT_FOUND pci2: <ACPI PCI bus> on pcib2
> pci2: <display, VGA> at device 0.0 (no driver attached)

That's you matrox card?

> acpi_button0: <Power Button> on acpi0
>   uteval-0226: *** Error: Return object type is incorrect
> [\\_SB_.LATA._CRS] (Node 0xffffff0000a24730), AE_TYPE can't fetch resources
> for \\_SB_.LATA - AE_TYPE

Isn't that vaguely disconcerting, to have runtime type errors in ACPI code?

One last question, about the wifi on the K8V Deluxe. Do you have any idea what 
that is? Whether it's supported? I'll find out automatically, I guess :)




More information about the freebsd-amd64 mailing list