From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 13 07:29:22 2003 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4757816A4B3 for ; Mon, 13 Oct 2003 07:29:21 -0700 (PDT) Received: from faui10.informatik.uni-erlangen.de (faui10.informatik.uni-erlangen.de [131.188.31.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1DF843FCB for ; Mon, 13 Oct 2003 07:29:19 -0700 (PDT) (envelope-from bauerm@faui10.informatik.uni-erlangen.de) Received: from faui1d.informatik.uni-erlangen.de (faui1d [131.188.31.34]) id QAA03129 for ; Mon, 13 Oct 2003 16:29:18 +0200 (CEST) Received: (from bauerm@localhost) by faui1d.informatik.uni-erlangen.de (8.9.3p2/8.1.6-FAU) id QAA19140 for freebsd-amd64@freebsd.org; Mon, 13 Oct 2003 16:29:18 +0200 (CEST) Date: Mon, 13 Oct 2003 16:29:18 +0200 From: Matthias Bauer To: freebsd-amd64@freebsd.org Message-ID: <20031013142918.GA19096@faui1d.informatik.uni-erlangen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.25i Subject: Summary of experience with amd64 mainboards? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Oct 2003 14:29:22 -0000 Hi, since quite a variety of mainboards for the amd64 are available now, it would be very useful if members of this mailing list would announce on which chipsets/mainboards they got the amd64 port to run (and what devices on the boards are not working as yet). It would also be nice to put the result on the project page. Best regards, Matthias From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 13 09:06:54 2003 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7840C16A4B3 for ; Mon, 13 Oct 2003 09:06:54 -0700 (PDT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id E71BC43F75 for ; Mon, 13 Oct 2003 09:06:53 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id D41BB2A8E3; Mon, 13 Oct 2003 09:06:53 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Matthias Bauer In-Reply-To: <20031013142918.GA19096@faui1d.informatik.uni-erlangen.de> Date: Mon, 13 Oct 2003 09:06:53 -0700 From: Peter Wemm Message-Id: <20031013160653.D41BB2A8E3@canning.wemm.org> cc: freebsd-amd64@freebsd.org Subject: Re: Summary of experience with amd64 mainboards? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Oct 2003 16:06:54 -0000 Matthias Bauer wrote: > Hi, > since quite a variety of mainboards for the amd64 are > available now, it would be very useful if members of this > mailing list would announce on which chipsets/mainboards > they got the amd64 port to run (and what devices on the > boards are not working as yet). It would also be nice to > put the result on the project page. The ones I have personal experience with are: 940 pin: Asus SK8N: works (nForce3 chipset, no driver for onboard nVidia nic, onboard promise 378 raid+SATA) Rioworks HDAMA: works (AMD chipset, 2 cpu, onboard if_bge gigabit, in use on the freebsd.org cluster as sledge.freebsd.org and at work) 754 pin: Asus K8V: works (VIA K8T800 chipset, onboard ide not recognized without patch which has integrated SATA support, decent onboard 3com/syskonnect gigabit nic (if_sk), onboard promise 378 raid+SATA) Gigabyte K8NPro: works (nForce3, lousy tiny bios interface, realtek 8110 gigabit nic (if_re) - supposedly not bad. onboard nVidia ethernet isn't connected (but we dont have a driver anyway)). AMD Solo4, Solo5 and Solo7 (developer reference boards) I really like both of the ASUS boards for personal use and the Rioworks for servers. I have not seen any of the MSI boards so I can't vouch for them. The MSI 2xCPU board only has 2 dimm slots on one of the cpus so I'm not that interested in their server board. Their consumer board appears to have similar specs to the asus K8V but I haven't tried it. All of these boards work with ACPI, minus some quirks with ordering the serial ports. Some of them list the COM2 port first in the tables which means we assign 'sio0' to it. Thats only a minor annoyance though. The onboard nVidia ethernet is annoying because they only give out a binary driver blob that you write an OS shim to use. This works for i386, but obviously isn't going to work too well for an amd64 kernel. The only board affected by this is the Asus SK8N, but ethernet cards are not a big deal. I really really dislike the bios on the Gigabyte, and really like the ones on the ASUS boards. The Gigabyte bios interface is almost worthless and gives you very little control over anything. If it had to be named, I'd call it a 'BIOS for dummies'. On the other hand, the ASUS bios' give you more than enough rope. For example, Gigabyte have 'PNP OS: Yes' by default and dont give you the ability to turn it off. ASUS do let you turn it off. Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 13 10:35:46 2003 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC8C016A4B3; Mon, 13 Oct 2003 10:35:46 -0700 (PDT) Received: from cueball.rtp.FreeBSD.org (cueball.rtp.FreeBSD.org [192.58.184.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB23843FCB; Mon, 13 Oct 2003 10:35:45 -0700 (PDT) (envelope-from des+tinderbox@freebsd.org) Received: from cueball.rtp.FreeBSD.org (localhost [127.0.0.1]) h9DHZinE055314; Mon, 13 Oct 2003 13:35:44 -0400 (EDT) (envelope-from des+tinderbox@freebsd.org) Received: (from des@localhost) by cueball.rtp.FreeBSD.org (8.12.9/8.12.9/Submit) id h9DHZiNh055313; Mon, 13 Oct 2003 13:35:44 -0400 (EDT) (envelope-from des+tinderbox@freebsd.org) Date: Mon, 13 Oct 2003 13:35:44 -0400 (EDT) Message-Id: <200310131735.h9DHZiNh055313@cueball.rtp.FreeBSD.org> X-Authentication-Warning: cueball.rtp.FreeBSD.org: des set sender to Tinderbox using -f Sender: Tinderbox From: Tinderbox To: current@freebsd.org, amd64@freebsd.org Precedence: bulk Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Oct 2003 17:35:46 -0000 From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 13 11:01:44 2003 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76CD516A4BF for ; Mon, 13 Oct 2003 11:01:44 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C44F943FBF for ; Mon, 13 Oct 2003 11:01:34 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h9DI1YFY044315 for ; Mon, 13 Oct 2003 11:01:34 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h9DI1XNP044309 for freebsd-amd64@freebsd.org; Mon, 13 Oct 2003 11:01:33 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 13 Oct 2003 11:01:33 -0700 (PDT) Message-Id: <200310131801.h9DI1XNP044309@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Oct 2003 18:01:44 -0000 Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/09/26] amd64/57250 amd64 Broken PTRACE_GETFPREGS and PTRACE_SETFPR 1 problem total. From owner-freebsd-amd64@FreeBSD.ORG Mon Oct 13 22:33:22 2003 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 063A116A4BF; Mon, 13 Oct 2003 22:33:22 -0700 (PDT) Received: from cueball.rtp.FreeBSD.org (cueball.rtp.FreeBSD.org [192.58.184.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 230F243FAF; Mon, 13 Oct 2003 22:33:21 -0700 (PDT) (envelope-from des+tinderbox@freebsd.org) Received: from cueball.rtp.FreeBSD.org (localhost [127.0.0.1]) h9E5XKnE096090; Tue, 14 Oct 2003 01:33:20 -0400 (EDT) (envelope-from des+tinderbox@freebsd.org) Received: (from des@localhost) by cueball.rtp.FreeBSD.org (8.12.9/8.12.9/Submit) id h9E5XKvY096089; Tue, 14 Oct 2003 01:33:20 -0400 (EDT) (envelope-from des+tinderbox@freebsd.org) Date: Tue, 14 Oct 2003 01:33:20 -0400 (EDT) Message-Id: <200310140533.h9E5XKvY096089@cueball.rtp.FreeBSD.org> X-Authentication-Warning: cueball.rtp.FreeBSD.org: des set sender to Tinderbox using -f Sender: Tinderbox From: Tinderbox To: current@freebsd.org, amd64@freebsd.org Precedence: bulk Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Oct 2003 05:33:22 -0000 From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 14 10:33:31 2003 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9815F16A4BF; Tue, 14 Oct 2003 10:33:31 -0700 (PDT) Received: from cueball.rtp.FreeBSD.org (cueball.rtp.FreeBSD.org [192.58.184.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id F41D543F75; Tue, 14 Oct 2003 10:33:29 -0700 (PDT) (envelope-from des+tinderbox@freebsd.org) Received: from cueball.rtp.FreeBSD.org (localhost [127.0.0.1]) h9EHXSnE037179; Tue, 14 Oct 2003 13:33:28 -0400 (EDT) (envelope-from des+tinderbox@freebsd.org) Received: (from des@localhost) by cueball.rtp.FreeBSD.org (8.12.9/8.12.9/Submit) id h9EHXSIJ037178; Tue, 14 Oct 2003 13:33:28 -0400 (EDT) (envelope-from des+tinderbox@freebsd.org) Date: Tue, 14 Oct 2003 13:33:28 -0400 (EDT) Message-Id: <200310141733.h9EHXSIJ037178@cueball.rtp.FreeBSD.org> X-Authentication-Warning: cueball.rtp.FreeBSD.org: des set sender to Tinderbox using -f Sender: Tinderbox From: Tinderbox To: current@freebsd.org, amd64@freebsd.org Precedence: bulk Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Oct 2003 17:33:31 -0000 From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 15 18:56:54 2003 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8B0516A4B3 for ; Wed, 15 Oct 2003 18:56:54 -0700 (PDT) Received: from bigtex.jrv.org (rrcs-sw-24-73-246-106.biz.rr.com [24.73.246.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8D9043FD7 for ; Wed, 15 Oct 2003 18:56:53 -0700 (PDT) (envelope-from james@bigtex.jrv.org) Received: from bigtex.jrv.org (localhost [127.0.0.1]) by bigtex.jrv.org (8.12.1/8.12.1) with ESMTP id h9G1uqo8058086 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 15 Oct 2003 20:56:52 -0500 (CDT) Received: (from james@localhost) by bigtex.jrv.org (8.12.1/8.12.1/Submit) id h9G1uqkc058083; Wed, 15 Oct 2003 20:56:52 -0500 (CDT) Date: Wed, 15 Oct 2003 20:56:52 -0500 (CDT) Message-Id: <200310160156.h9G1uqkc058083@bigtex.jrv.org> From: James Van Artsdalen To: freebsd-amd64@freebsd.org Subject: I/O cards, bounce-buffer free? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2003 01:56:54 -0000 Is there a list of disk and network adapters that 1. Work well under FreeBSD/amd64? 2. Can directly address the entire AMD64 address space, i.e. 64 bit addresses, without the need for bounce buffers or such? From owner-freebsd-amd64@FreeBSD.ORG Fri Oct 17 10:17:50 2003 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C017D16A4B3; Fri, 17 Oct 2003 10:17:50 -0700 (PDT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79FDE43FA3; Fri, 17 Oct 2003 10:17:47 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by canning.wemm.org (Postfix) with ESMTP id 655BE2A7EA; Fri, 17 Oct 2003 10:17:47 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: current@freebsd.org Date: Fri, 17 Oct 2003 10:17:47 -0700 From: Peter Wemm Message-Id: <20031017171747.655BE2A7EA@canning.wemm.org> cc: amd64@freebsd.org Subject: FYI, I've switched my primary desktop to AMD64. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2003 17:17:50 -0000 I finally worked up the nerve to commit to eating my own dogfood. :-) I've actually been doing my primary development on amd64 boxes for a while, and now that the consumer products have been officially launched, I figured it was about time. Most of the key components are in place. I've upgraded my home machine to an Asus SK8N + Athlon64 FX-51 (niiice!). My i386 box is in pieces, there is no going back now. For some strange reason I've had to pay attention to some of the sharp edges I'd been putting off for a while. 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. 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 bugzilla database though. If all else fails, I'll use remote X from my laptop or something evil like that. Or finish off the 32 bit i386 binary support (I need to do that anyway - I haven't even tried to see if a FreeBSD/i386 binary of mozilla works, it might already work) Anyway, the 24 hours later status is: Thumbs up! And now to do the same thing to my work desktop. I'm planning to use an Asus K8V + Athlon64 3200+ there. Anyway, in case anybody is interested, the dmesg of my home box looks like this: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #3: Thu Oct 16 11:37:26 PDT 2003 root@overcee.wemm.org:/home/src/sys/amd64/compile/OVERCEE Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff806ef000. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 FX-51 Processor (2200.01-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 Features=0x78bfbff AMD Features=0xe0500000 real memory = 1072955392 (1023 MB) avail memory = 1011191808 (964 MB) Pentium Pro MTRR support enabled acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_cpu0: port 0x530-0x537 on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xfebfd000-0xfebfdfff irq 11 at device 2.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x10de) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfebfe000-0xfebfefff irq 5 at device 2.1 on pci0 usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: (0x10de) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ehci0: mem 0xfebffc00-0xfebffcff irq 10 at device 2.2 on pci0 ehci_pci_attach: companion usb0 ehci_pci_attach: companion usb1 usb2: EHCI version 1.0 usb2: companion controllers, 4 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: (0x10de) EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 6 ports with 6 removable, self powered pcm0: port 0xec00-0xec7f,0xe800-0xe8ff mem 0xfebfb000-0xfebfbfff irq 11 at device 6.0 on pci0 pcm0: atapci0: port 0xffa0-0xffaf at device 8.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pcib1: at device 10.0 on pci0 pci1: on pcib1 ahc0: port 0xd800-0xd8ff mem 0xfc9ff000-0xfc9fffff irq 5 at device 4.0 on pci1 aic7870: Single Channel A, SCSI Id=7, 16/253 SCBs fxp0: 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 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto puc0: port 0xdfe0-0xdfe7,0xdff0-0xdff7,0xdf80-0xdf9f irq 11 at device 6.0 on pci1 sio4: on puc0 sio4: type 16550A sio4: unable to activate interrupt in fast mode - using normal mode sio5: on puc0 sio5: type 16550A sio5: unable to activate interrupt in fast mode - using normal mode puc1: port 0xdfa0-0xdfa7,0xdfa8-0xdfaf,0xdf40-0xdf5f irq 5 at device 7.0 on pci1 sio6: on puc1 sio6: type 16550A sio6: unable to activate interrupt in fast mode - using normal mode sio7: on puc1 sio7: type 16550A sio7: unable to activate interrupt in fast mode - using normal mode atapci1: port 0xdc00-0xdc7f,0xdf60-0xdf6f,0xde80-0xdebf mem 0xfc9a0000-0xfc9bffff,0xfc9fd000-0xfc9fdfff irq 11 at device 8.0 on pci1 atapci1: [MPSAFE] ata2: at 0xfc9fd000 on atapci1 ata2: [MPSAFE] ata3: at 0xfc9fd000 on atapci1 ata3: [MPSAFE] ata4: at 0xfc9fd000 on atapci1 ata4: [MPSAFE] fwohci0: mem 0xfc9f8000-0xfc9fbfff,0xfc9fc800-0xfc9fcfff irq 11 at device 9.0 on pci1 fwohci0: [MPSAFE] fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 00:e0:18:00:00:2e:05:8c fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 if_fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:e0:18:2e:05:8c sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) pcib2: at device 11.0 on pci0 pcib2: could not get PCI interrupt routing table for \\_SB_.PCI0.P0P2 - AE_NOT_FOUND pci2: on pcib2 pci2: at device 0.0 (no driver attached) fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 ppc0 port 0x778-0x77f,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse Explorer, device ID 4 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A acpi_button0: 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 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 npx0: on motherboard npx0: INT 16 interface orm0: