From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 19 00:05:34 2004 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 12BDA16A4CE for ; Sun, 19 Sep 2004 00:05:34 +0000 (GMT) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D14943D1D for ; Sun, 19 Sep 2004 00:05:28 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from [192.168.245.231] ([213.112.167.129] [213.112.167.129]) by mxfep01.bredband.com with ESMTP id <20040919000527.XVNL1871.mxfep01.bredband.com@[192.168.245.231]> for ; Sun, 19 Sep 2004 02:05:27 +0200 Message-ID: <414CCCF2.20208@bredband.net> Date: Sun, 19 Sep 2004 02:04:02 +0200 From: Lars Tunkrans Organization: None User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20040618 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20040915003915.2489d1b0.solita2@solitarylight.com> <200409150829.10481.fcash-ml@sd73.bc.ca> <414CB011.4030206@withagen.nl> In-Reply-To: <414CB011.4030206@withagen.nl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Mainboard suggestions? 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: Sun, 19 Sep 2004 00:05:34 -0000 Willem Jan Withagen wrote: > Well I'd have to argue about that. I had to replace a MSI K8T > Master2-FAR board with 2 opteron 242 processors because it was causing > crashes to no end during high load. As soon as the load went over 10 for > a longer period the board crashed. After long discussions with people > doing the amd64 port I bought a new board (Tyan Tiger), and that has > proven rock solid with all the same components. Supposedly it is because > of "things" with the VIA chipset, but the finer details never became > clear. > And looking at others thru google, there are a lot of people not very > happy with that board. Hello, I installed the "MSI K8T Neo2 FIR" and an AMD64 3800+ in my old chassie this thursday. It is a socket 939 board with Via KT800Pro chipset. Today I have installed Fbsd 5.3 AMD64 Beta4 with some success. It is a single CPU board with Realtek gigabit Eth , Firewire and ATA/SATA Raid. ( Promise chipset) I Have disabled the RAID in Bios an use the "trusted" old ATA UDMA100. Otherwise the Ethernet and firewire interfaces runs from the beginning with the BETA4 CDROM. I did choose this board because there was too many reported problems with NFORCE 3 boards. specifically the "sk0 - driver " problems that seems plauge all newer ASUS boards. Also I wanted the socket 939 128-bit ram-bus with non-ecc memory for cost and speed reasons. I paid about $1200 for the MOBO + AMD64 3800 + 1 GB RAM. If I was buying an Opteron SMP workstation, and money was not an issue... I would go for the "SUN Microsystems W2100z" , its built around the AMD8000 series chipset. Regards //Lars From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 19 02:17:57 2004 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 6AE3A16A4D0; Sun, 19 Sep 2004 02:17:57 +0000 (GMT) Received: from mail.broadpark.no (mail.broadpark.no [217.13.4.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00F0743D49; Sun, 19 Sep 2004 02:17:57 +0000 (GMT) (envelope-from des@des.no) Received: from dwp.des.no (37.80-203-228.nextgentel.com [80.203.228.37]) by mail.broadpark.no (Postfix) with ESMTP id 78DE338C5; Sun, 19 Sep 2004 04:18:36 +0200 (MEST) Received: by dwp.des.no (Postfix, from userid 2602) id D0A4FB85E; Sun, 19 Sep 2004 04:17:55 +0200 (CEST) To: amd64@freebsd.org, re@freebsd.org From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Sun, 19 Sep 2004 04:17:55 +0200 Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Subject: NO_MIXED_MODE 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: Sun, 19 Sep 2004 02:17:57 -0000 I just got an ASUS SK8N motherboard that has the problematic nForce 3 chipset. It runs 5.3 BETA4 fine, except you have to boot it in safe mode because the APIC only works properly in mixed mode, and GENERIC has the NO_MIXED_MODE option. Took me quite a while to figure that out... Should we consider removing that option for 5.3-RELEASE? DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 19 18:52:40 2004 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 5643A16A4CE; Sun, 19 Sep 2004 18:52:40 +0000 (GMT) Received: from lakermmtao08.cox.net (lakermmtao08.cox.net [68.230.240.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9A3343D39; Sun, 19 Sep 2004 18:52:39 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao08.cox.net ESMTP <20040919185239.IPSE27491.lakermmtao08.cox.net@dolphin.local.net>; Sun, 19 Sep 2004 14:52:39 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with SMTP id i8JIqcYw051751; Sun, 19 Sep 2004 13:52:38 -0500 (CDT) (envelope-from conrads@cox.net) Date: Sun, 19 Sep 2004 13:52:33 -0500 From: "Conrad J. Sabatier" To: des@des.no (Dag-Erling =?ISO-8859-1?Q?Sm=F8rgrav?=) Message-ID: <20040919135233.4997ea78@dolphin.local.net> In-Reply-To: References: X-Mailer: Sylpheed-Claws 0.9.12a (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable cc: amd64@freebsd.org cc: re@freebsd.org Subject: Re: NO_MIXED_MODE 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: Sun, 19 Sep 2004 18:52:40 -0000 On Sun, 19 Sep 2004 04:17:55 +0200, des@des.no (Dag-Erling Sm=F8rgrav) wrote: > I just got an ASUS SK8N motherboard that has the problematic nForce 3 > chipset. It runs 5.3 BETA4 fine, except you have to boot it in safe > mode because the APIC only works properly in mixed mode, and GENERIC > has the NO_MIXED_MODE option. Took me quite a while to figure that > out... >=20 > Should we consider removing that option for 5.3-RELEASE? I'll second that motion. I have the same chipset, and the same problem with NO_MIXED_MODE. I think we should err on the side of caution with this one. --=20 Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 19 20:41:30 2004 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 9A01316A4CE; Sun, 19 Sep 2004 20:41:30 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E778243D1F; Sun, 19 Sep 2004 20:41:25 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.4.0.76] ([65.220.109.67]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i8JKf3xr021633; Sun, 19 Sep 2004 14:41:04 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <414DEE9B.3020800@samsco.org> Date: Sun, 19 Sep 2004 14:39:55 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040831 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Conrad J. Sabatier" References: <20040919135233.4997ea78@dolphin.local.net> In-Reply-To: <20040919135233.4997ea78@dolphin.local.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: amd64@freebsd.org cc: re@freebsd.org Subject: Re: NO_MIXED_MODE 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: Sun, 19 Sep 2004 20:41:31 -0000 Conrad J. Sabatier wrote: > On Sun, 19 Sep 2004 04:17:55 +0200, des@des.no (Dag-Erling Smørgrav) > wrote: > > >>I just got an ASUS SK8N motherboard that has the problematic nForce 3 >>chipset. It runs 5.3 BETA4 fine, except you have to boot it in safe >>mode because the APIC only works properly in mixed mode, and GENERIC >>has the NO_MIXED_MODE option. Took me quite a while to figure that >>out... >> >>Should we consider removing that option for 5.3-RELEASE? > > > I'll second that motion. I have the same chipset, and the same problem > with NO_MIXED_MODE. I think we should err on the side of caution with > this one. > Let's see what Peter, David, and John say about this. My understanding is that mixed mode has a measurable performance impact, so we don't want to turn it on universally unless neccessary. Maybe David knows of a BIOS upgrade that would help your motherboards. Scott From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 20 11:02:09 2004 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 CA8CF16A4CE for ; Mon, 20 Sep 2004 11:02:09 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C06F843D2D for ; Mon, 20 Sep 2004 11:02:09 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i8KB29xQ001382 for ; Mon, 20 Sep 2004 11:02:09 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i8KB28jJ001376 for freebsd-amd64@freebsd.org; Mon, 20 Sep 2004 11:02:08 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 20 Sep 2004 11:02:08 GMT Message-Id: <200409201102.i8KB28jJ001376@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, 20 Sep 2004 11:02:09 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59714 amd64 device timeout and ad0: WARNING - WRITE_D o [2004/06/09] amd64/67745 amd64 boot fails on compaq presario r3000z o [2004/07/28] amd64/69704 amd64 ext2/ext3 unstable in amd64 o [2004/07/28] amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o [2004/09/07] amd64/71471 amd64 Can not install 5.3beta3/amd64 on IBM eSe 5 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/01/11] amd64/61209 amd64 ppc0: cannot reserve I/O port range o [2004/02/21] amd64/63188 amd64 ti(4) broken on amd64 o [2004/07/28] amd64/69705 amd64 IPC problem (msq_queues) o [2004/07/28] amd64/69709 amd64 ACPI enabled then floppy don't work (5.2. o [2004/07/28] amd64/69712 amd64 no DRI (hardware OpenGL) for ATI Radeon 9 o [2004/08/15] amd64/70500 amd64 bge driver for 3Com 3C996B on amd64 preve o [2004/09/12] amd64/71674 amd64 static libraries cannot be linked when bu o [2004/09/15] amd64/71753 amd64 DRI loads but fails to render on Radeon 9 8 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 20 13:49:01 2004 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 BE44A16A4CE for ; Mon, 20 Sep 2004 13:49:01 +0000 (GMT) Received: from s1.vhost.cz (s1.vhost.cz [82.208.27.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8703A43D3F for ; Mon, 20 Sep 2004 13:49:00 +0000 (GMT) (envelope-from konfer@mikulas.com) Received: (qmail 58030 invoked by uid 89); 20 Sep 2004 15:48:59 +0200 Received: from unknown (HELO localhost) (127.0.0.1) by localhost with SMTP; 20 Sep 2004 15:48:59 +0200 Received: from QMQPqq client ([127.0.0.1]) by localhost (s1.vhost.cz [127.0.0.1]) (amavisd-new, port 10628) with QMQPqq id 57849-03; Mon, 20 Sep 2004 15:48:58 +0200 (CEST) Received: from unknown (HELO mikulas.com) (jiri@mikulas.com@195.122.204.153) by s1.vhost.cz with AES256-SHA encrypted SMTP; 20 Sep 2004 15:48:58 +0200 Message-ID: <414EDFC7.2020104@mikulas.com> Date: Mon, 20 Sep 2004 15:48:55 +0200 From: Jiri Mikulas User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040407 X-Accept-Language: cs, en, en-us MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at s1.vhost.cz cc: amd64@freebsd.org Subject: Sil 3114 SATA RAID 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, 20 Sep 2004 13:49:01 -0000 Hello I have Epox *EP-8HDA3+* motherboard AMD64 processor, runing on i386 kernel and userland FreeBSD kelt64.mikulas.com 5.3-BETA5 FreeBSD 5.3-BETA5 #0: Mon Sep 20 11:49:48 UTC 2004 root@kelt64.mikulas.com:/usr/obj/usr/src/sys/KELT i386 I am booting from standalone SATA disk ad12 atapci1: port 0xcc00-0xccff,0xc800-0xc80f,0xc400-0xc403,0xc000-0xc007,0xbc00-0xbc03,0xb800-0xb807 irq 11 at device 15.0 on pci0 ad12: 152627MB [310101/16/63] at ata6-master SATA150 I have: atapci0: port 0xb400-0xb40f,0xb000-0xb003,0xac00-0xac07,0xa800-0xa803,0xa400-0xa407 mem 0xeb004000-0xeb0043ff irq 10 at device 14.0 on pci0 ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 ata4: channel #2 on atapci0 ata5: channel #3 on atapci0 --------- atapci0@pci0:14:0: class=0x010400 card=0x90181695 chip=0x31141095 rev=0x02 hdr=0x00 vendor = 'Silicon Image Inc (Was: CMD Technology Inc)' device = 'Sil 3114 SATALink/SATARaid Controller' class = mass storage subclass = RAID --------- and two disks ad4: 190782MB [387621/16/63] at ata2-master SATA150 ad6: 190782MB [387621/16/63] at ata3-master SATA150 if I create any RAID(0,1) with Sil 3114 controller BIOS boot hangs on ~~~cut~~~ Timecounter "TSC" frequency 2009947112 Hz quality 800 Timecounters tick every 10.000 msec ata2-master: FAILURE - ATA_IDENTIFY status=51 error=4 LBA=0 ~~~cut~~~ if I setup disks in "standalone" mode - with controller BIOS as ad4 and ad6, after boot I can create RAID with atacontrol without problems kelt64# atacontrol create RAID1 ad4 ad6 ar0 created dmesg: ar0: 190780MB [24321/255/63] status: READY subdisks: disk0 READY on ad4 at ata2-master disk1 READY on ad6 at ata3-master kelt64# atacontrol status 0 ar0: ATA RAID1 subdisks: ad4 ad6 status: READY Is it known bug, or anything else (my fault)? I also used amd64 FBSD 5.3-BETA4 and had the same problem sorry for my english thanks for reply ;) Jiri From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 20 17:00:18 2004 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 687C716A4CF for ; Mon, 20 Sep 2004 17:00:18 +0000 (GMT) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 091F843D39 for ; Mon, 20 Sep 2004 17:00:18 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1C9RWP-0004rm-00; Mon, 20 Sep 2004 19:00:13 +0200 Date: Mon, 20 Sep 2004 19:00:13 +0200 To: Francois Tigeot Message-ID: <20040920170013.GQ16132@poupinou.org> References: <20040914150419.GA7191@aoi.wolfpond.org> <200409141543.13318.peter@wemm.org> <20040915063512.GA10104@aoi.wolfpond.org> <200409170907.18458.peter@wemm.org> <20040917190850.GA69926@aoi.wolfpond.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040917190850.GA69926@aoi.wolfpond.org> User-Agent: Mutt/1.5.5.1+cvs20040105i From: Bruno Ducrot cc: freebsd-amd64@freebsd.org Subject: Re: bios.h question 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, 20 Sep 2004 17:00:18 -0000 On Fri, Sep 17, 2004 at 09:08:50PM +0200, Francois Tigeot wrote: > > > > Ahh - bios tables. That we can do. This is for a kernel component, > > right? > > Right. The table is providing CPU frequency and voltage information > corresponding to different power states. > A kernel module could use it to scale system speed according to the > average load... > > At least, it seems this is what this code does on i386: > http://www.poupinou.org/cpufreq/bsd/powernow_k7/ > I'm working on a powernow_k8 driver anyway since I need one. -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 20 18:11:48 2004 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 45C6816A4CE for ; Mon, 20 Sep 2004 18:11:48 +0000 (GMT) Received: from ares.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE89C43D55 for ; Mon, 20 Sep 2004 18:11:46 +0000 (GMT) (envelope-from ftigeot@wolfpond.org) Received: from aoi.wolfpond.org (aoi.wolfpond.org [IPv6:2001:7a8:24db:1:20c:76ff:feb4:27e1]) by ares.wolfpond.org (8.12.10/8.12.10) with ESMTP id i8KIBjui002574; Mon, 20 Sep 2004 20:11:45 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.1/8.13.1) with ESMTP id i8KIBbSP001160; Mon, 20 Sep 2004 20:11:37 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.1/8.13.1/Submit) id i8KIBb9u001159; Mon, 20 Sep 2004 20:11:37 +0200 (CEST) (envelope-from ftigeot) Date: Mon, 20 Sep 2004 20:11:37 +0200 From: Francois Tigeot To: Bruno Ducrot Message-ID: <20040920181137.GA1004@aoi.wolfpond.org> References: <20040914150419.GA7191@aoi.wolfpond.org> <200409141543.13318.peter@wemm.org> <20040915063512.GA10104@aoi.wolfpond.org> <200409170907.18458.peter@wemm.org> <20040917190850.GA69926@aoi.wolfpond.org> <20040920170013.GQ16132@poupinou.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040920170013.GQ16132@poupinou.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: bios.h question 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, 20 Sep 2004 18:11:48 -0000 On Mon, Sep 20, 2004 at 07:00:13PM +0200, Bruno Ducrot wrote: > On Fri, Sep 17, 2004 at 09:08:50PM +0200, Francois Tigeot wrote: > > > > > > Ahh - bios tables. That we can do. This is for a kernel component, > > > right? > > > > Right. The table is providing CPU frequency and voltage information > > corresponding to different power states. > > A kernel module could use it to scale system speed according to the > > average load... > > > > At least, it seems this is what this code does on i386: > > http://www.poupinou.org/cpufreq/bsd/powernow_k7/ > > I'm working on a powernow_k8 driver anyway since I need one. Nice to hear that. I'm curious: did you find any recent documentation ? All documents on Powernow! I could gather on AMD site were for the K6 family. -- Francois Tigeot From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 20 18:41:52 2004 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 1243716A542 for ; Mon, 20 Sep 2004 18:41:49 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 923E743D49 for ; Mon, 20 Sep 2004 18:41:48 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 464 invoked from network); 20 Sep 2004 18:41:48 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 20 Sep 2004 18:41:47 -0000 Received: from [10.50.40.210] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i8KIfXOB024733; Mon, 20 Sep 2004 14:41:45 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org Date: Mon, 20 Sep 2004 14:30:39 -0400 User-Agent: KMail/1.6.2 References: <20040919135233.4997ea78@dolphin.local.net> <414DEE9B.3020800@samsco.org> In-Reply-To: <414DEE9B.3020800@samsco.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200409201430.39304.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: amd64@FreeBSD.org cc: Scott Long cc: re@FreeBSD.org Subject: Re: NO_MIXED_MODE 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, 20 Sep 2004 18:41:52 -0000 On Sunday 19 September 2004 04:39 pm, Scott Long wrote: > Conrad J. Sabatier wrote: > > On Sun, 19 Sep 2004 04:17:55 +0200, des@des.no (Dag-Erling Sm=F8rgrav) > > > > wrote: > >>I just got an ASUS SK8N motherboard that has the problematic nForce 3 > >>chipset. It runs 5.3 BETA4 fine, except you have to boot it in safe > >>mode because the APIC only works properly in mixed mode, and GENERIC > >>has the NO_MIXED_MODE option. Took me quite a while to figure that > >>out... > >> > >>Should we consider removing that option for 5.3-RELEASE? > > > > I'll second that motion. I have the same chipset, and the same problem > > with NO_MIXED_MODE. I think we should err on the side of caution with > > this one. > > Let's see what Peter, David, and John say about this. My understanding > is that mixed mode has a measurable performance impact, so we don't want > to turn it on universally unless neccessary. Maybe David knows of a > BIOS upgrade that would help your motherboards. You can toggle mixed mode via a loader tunable. I'd add a note to the=20 hardware notes suggesting that people with the specific motherboard break=20 into the loader during install and do: set hw.apic.mixed_mode=3D1 and then add an appropriate line to /boot/loader.conf after install. =2D-=20 John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 20 18:41:52 2004 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 A9F3016A519 for ; Mon, 20 Sep 2004 18:41:48 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90E9943D1F for ; Mon, 20 Sep 2004 18:41:48 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 464 invoked from network); 20 Sep 2004 18:41:48 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 20 Sep 2004 18:41:47 -0000 Received: from [10.50.40.210] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i8KIfXOB024733; Mon, 20 Sep 2004 14:41:45 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org Date: Mon, 20 Sep 2004 14:30:39 -0400 User-Agent: KMail/1.6.2 References: <20040919135233.4997ea78@dolphin.local.net> <414DEE9B.3020800@samsco.org> In-Reply-To: <414DEE9B.3020800@samsco.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200409201430.39304.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: amd64@FreeBSD.org cc: Scott Long cc: re@FreeBSD.org Subject: Re: NO_MIXED_MODE 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, 20 Sep 2004 18:41:52 -0000 On Sunday 19 September 2004 04:39 pm, Scott Long wrote: > Conrad J. Sabatier wrote: > > On Sun, 19 Sep 2004 04:17:55 +0200, des@des.no (Dag-Erling Sm=F8rgrav) > > > > wrote: > >>I just got an ASUS SK8N motherboard that has the problematic nForce 3 > >>chipset. It runs 5.3 BETA4 fine, except you have to boot it in safe > >>mode because the APIC only works properly in mixed mode, and GENERIC > >>has the NO_MIXED_MODE option. Took me quite a while to figure that > >>out... > >> > >>Should we consider removing that option for 5.3-RELEASE? > > > > I'll second that motion. I have the same chipset, and the same problem > > with NO_MIXED_MODE. I think we should err on the side of caution with > > this one. > > Let's see what Peter, David, and John say about this. My understanding > is that mixed mode has a measurable performance impact, so we don't want > to turn it on universally unless neccessary. Maybe David knows of a > BIOS upgrade that would help your motherboards. You can toggle mixed mode via a loader tunable. I'd add a note to the=20 hardware notes suggesting that people with the specific motherboard break=20 into the loader during install and do: set hw.apic.mixed_mode=3D1 and then add an appropriate line to /boot/loader.conf after install. =2D-=20 John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 20 19:02:03 2004 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 8365516A4CE; Mon, 20 Sep 2004 19:02:03 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45C0E43D81; Mon, 20 Sep 2004 19:02:03 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id i8KJ1xDw009368; Mon, 20 Sep 2004 12:01:59 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i8KJ1w3j009367; Mon, 20 Sep 2004 12:01:58 -0700 (PDT) (envelope-from obrien) Date: Mon, 20 Sep 2004 12:01:57 -0700 From: "David O'Brien" To: Dag-Erling Sm?rgrav Message-ID: <20040920190157.GB9191@dragon.nuxi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: amd64@freebsd.org cc: re@freebsd.org Subject: Re: NO_MIXED_MODE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2004 19:02:03 -0000 On Sun, Sep 19, 2004 at 04:17:55AM +0200, Dag-Erling Sm?rgrav wrote: > I just got an ASUS SK8N motherboard that has the problematic nForce 3 Eeek. You got one of the worst mobos you could get for non-mswin OS's. See if you can return it to the store and get an SK8V. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 20 19:06:53 2004 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 8FD0516A4CE; Mon, 20 Sep 2004 19:06:53 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C6FF43D2D; Mon, 20 Sep 2004 19:06:53 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id i8KJ6iaS009444; Mon, 20 Sep 2004 12:06:45 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i8KJ6iq4009443; Mon, 20 Sep 2004 12:06:44 -0700 (PDT) (envelope-from obrien) Date: Mon, 20 Sep 2004 12:06:43 -0700 From: "David O'Brien" To: Scott Long Message-ID: <20040920190643.GC9191@dragon.nuxi.com> References: <20040919135233.4997ea78@dolphin.local.net> <414DEE9B.3020800@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <414DEE9B.3020800@samsco.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: amd64@freebsd.org cc: re@freebsd.org Subject: Re: NO_MIXED_MODE X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2004 19:06:53 -0000 On Sun, Sep 19, 2004 at 02:39:55PM -0600, Scott Long wrote: > >I'll second that motion. I have the same chipset, and the same problem > >with NO_MIXED_MODE. I think we should err on the side of caution with > >this one. > > Let's see what Peter, David, and John say about this. My understanding > is that mixed mode has a measurable performance impact, so we don't want > to turn it on universally unless necessary. Correct. > Maybe David knows of a BIOS upgrade that would help your motherboards. I've never been able to get a sufficiently accurate detailed explanation of the problem FreeBSD has on this mobo that I could get the BIOS vendor to fix it; (read, there isn't a fix I know of; but you should be using the latest '1007' for other reasons). I've avoided nForce3-150 mobos like the plague and don't have one for looking into this. If anyone can dive deeper into this issue, I'd appreciate it and will work to have the vendor fix it. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 20 21:07:42 2004 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 E6A2A16A4CE for ; Mon, 20 Sep 2004 21:07:42 +0000 (GMT) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BD4343D2F for ; Mon, 20 Sep 2004 21:07:41 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from [192.168.245.231] ([213.112.167.129] [213.112.167.129]) by mxfep01.bredband.com with ESMTP id <20040920210738.RDGU1871.mxfep01.bredband.com@[192.168.245.231]> for ; Mon, 20 Sep 2004 23:07:38 +0200 Message-ID: <414F4641.8080201@bredband.net> Date: Mon, 20 Sep 2004 23:06:09 +0200 From: Lars Tunkrans Organization: None User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20040618 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Install of Mozilla 1.7.2 ( after build ) hangs with regxpcom 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, 20 Sep 2004 21:07:43 -0000 I have tried to build x11/gnome2 metaport in both AMD64 Beta4 and Beta5 . The build of mozilla 1.7.2 succeds but fails in the install phase. While Building the Chrome registry : "regxpcom" gets stuck somehow consumeing 100% CPU while registering the webcal protocol handler. //Lars From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 20 21:23:57 2004 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 2AAC716A4CE; Mon, 20 Sep 2004 21:23:57 +0000 (GMT) Received: from mail.broadpark.no (mail.broadpark.no [217.13.4.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A695243D46; Mon, 20 Sep 2004 21:23:56 +0000 (GMT) (envelope-from des@des.no) Received: from dwp.des.no (37.80-203-228.nextgentel.com [80.203.228.37]) by mail.broadpark.no (Postfix) with ESMTP id C7987505D; Mon, 20 Sep 2004 23:24:36 +0200 (MEST) Received: by dwp.des.no (Postfix, from userid 2602) id AC8D1B85E; Mon, 20 Sep 2004 23:23:55 +0200 (CEST) To: obrien@freebsd.org References: <20040920190157.GB9191@dragon.nuxi.com> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Mon, 20 Sep 2004 23:23:55 +0200 In-Reply-To: <20040920190157.GB9191@dragon.nuxi.com> (David O'Brien's message of "Mon, 20 Sep 2004 12:01:57 -0700") Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable cc: amd64@freebsd.org cc: re@freebsd.org Subject: Re: NO_MIXED_MODE 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, 20 Sep 2004 21:23:57 -0000 "David O'Brien" writes: > On Sun, Sep 19, 2004 at 04:17:55AM +0200, Dag-Erling Sm?rgrav wrote: > > I just got an ASUS SK8N motherboard that has the problematic nForce 3 > Eeek. You got one of the worst mobos you could get for non-mswin OS's. > See if you can return it to the store and get an SK8V. It was a donation, as I already told you in a separate email where I asked for a copy of your uncommitted nve(4) driver. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 20 23:16:09 2004 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 0DEAB16A4CE for ; Mon, 20 Sep 2004 23:16:09 +0000 (GMT) Received: from slyna.neosaint.org (slyna.neosaint.org [207.3.94.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DD8043D3F for ; Mon, 20 Sep 2004 23:16:08 +0000 (GMT) (envelope-from rich@neosaint.org) Received: from [10.1.101.133] (nat-vlan200.sat.rackspace.com [64.39.1.10]) (authenticated bits=0)i8KNFf1S026198 for ; Mon, 20 Sep 2004 18:15:47 -0500 From: "RIchard N. Fogle" To: freebsd-amd64@freebsd.org Content-Type: text/plain Message-Id: <1095722150.33796.38.camel@rfogle.rackspace.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 20 Sep 2004 18:15:50 -0500 Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on slyna.neosaint.org Subject: 64-bit HAL for ath_hal module X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: rich@neosaint.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2004 23:16:09 -0000 Greetings, There is a 64-bit HAL for the Atheros chipset in the CVS version of madwiki.. Any chance that will be included in the ath_hal device for AMD64 FreeBSD? I made an attempt at getting this to work myself by dropping in the 64-bit, but received a missing symbol of "ath_hal_memcpy" when loading the driver. I then defined "ath_hal_memcpy" as "bcopy((_src), (_dst), (_size))" as required in ah_osdep.h, and with a version change, the module loded successfully with the device found. Unfortunately, when I try to manipulate it after an "ifconfig ath0 up" I get a kernel panic. Honestly didn't think it would be that easy, but I thought I'd try. I have a copy of the 64-bit HAL if anyone needs it.. Something changed somewhere but I'm not all that experienced in this sort of thing. Until then I'm running i386/FreeBSD 5.3BETA3 on my dual Opteron. Tried Fedora but it gave me fits. I'm probably in the minority, but wireless is the only method I have for connecting to the interenet. Regards, Rich From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 21 08:32:13 2004 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 6EB6216A4CE for ; Tue, 21 Sep 2004 08:32:13 +0000 (GMT) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2526443D1D for ; Tue, 21 Sep 2004 08:32:13 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1C9g4I-0005ni-00; Tue, 21 Sep 2004 10:32:10 +0200 Date: Tue, 21 Sep 2004 10:32:10 +0200 To: Francois Tigeot Message-ID: <20040921083210.GS16132@poupinou.org> References: <20040914150419.GA7191@aoi.wolfpond.org> <200409141543.13318.peter@wemm.org> <20040915063512.GA10104@aoi.wolfpond.org> <200409170907.18458.peter@wemm.org> <20040917190850.GA69926@aoi.wolfpond.org> <20040920170013.GQ16132@poupinou.org> <20040920181137.GA1004@aoi.wolfpond.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040920181137.GA1004@aoi.wolfpond.org> User-Agent: Mutt/1.5.5.1+cvs20040105i From: Bruno Ducrot cc: freebsd-amd64@freebsd.org Subject: Re: bios.h question 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: Tue, 21 Sep 2004 08:32:13 -0000 Hi, On Mon, Sep 20, 2004 at 08:11:37PM +0200, Francois Tigeot wrote: > I'm curious: did you find any recent documentation ? All documents on > Powernow! I could gather on AMD site were for the K6 family. Actually it is well documented (for the k7 one, it's another story though). http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_739_7203,00.html Especially: "BIOS and Kernel Developer's Guide for AMD Athlon 64 and AMD Opteron Processors", #26094 look especially at 9.5.5.2 which describe how to make a transition for example. "AMD Athlon 64 Processor Power and Thermal Data Sheet", #30430 which contains (amongst other things) all the processors supporting frequency and voltage scalings. and of course you have to look at the errata doc. Cheers, -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 21 12:41:33 2004 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 1AB1916A4CE for ; Tue, 21 Sep 2004 12:41:33 +0000 (GMT) Received: from maxwell.syr.edu (maxwell.syr.edu [128.230.129.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8744843D1D for ; Tue, 21 Sep 2004 12:41:32 +0000 (GMT) (envelope-from jracine@maxwell.syr.edu) Received: from [128.230.130.10] (jracine.maxwell.syr.edu [128.230.130.10]) by maxwell.syr.edu (8.12.10/8.9.1) with ESMTP id i8LCfUBf056311 for ; Tue, 21 Sep 2004 08:41:31 -0400 (EDT) From: Jeffrey Racine To: freebsd-amd64@freebsd.org Content-Type: text/plain Organization: Syracuse University Date: Tue, 21 Sep 2004 08:41:30 -0400 Message-Id: <1095770490.592.4.camel@jracine.maxwell.syr.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.0.0FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Date problems (ntpd) & current... 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: Tue, 21 Sep 2004 12:41:33 -0000 Hi. I have had this problem for quite some time now. Time related functions are not functioning. Upon boot I receive the message ntpd[378]: bind() fd 7, family 28, port 123, addr fe80:2::202:b3ff:feed:b12, in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address Setting the time via rdate yields rdate -s clock.psu.edu rdate: Could not read data: Unknown error: 0 Finally, attempting to set the time via the time/date tool in gnome 2.8 crashes (as it did in 2.6). System is running current... here is relevant info, and thanks for your help. uname -a FreeBSD jracine.maxwell.syr.edu 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Wed Sep 15 14:16:34 EDT 2004 root@jracine.maxwell.syr.edu:/usr/obj/usr/src/sys/OPTERON amd64 dmesg Copyright (c) 1992-2004 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 6.0-CURRENT #0: Wed Sep 15 14:16:34 EDT 2004 root@jracine.maxwell.syr.edu:/usr/obj/usr/src/sys/OPTERON ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 248 (2205.01-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 Features=0x78bfbff AMD Features=0xe0500800 real memory = 3674144768 (3503 MB) avail memory = 3543638016 (3379 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 cpu0: on acpi0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pcib2: at device 6.0 on pci0 pci2: on pcib2 ohci0: mem 0xfd7fe000-0xfd7fefff irq 19 at device 0.0 on pci2 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfd7ff000-0xfd7fffff irq 19 at device 0.1 on pci2 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered fwohci0: mem 0xfd7f8000-0xfd7fbfff,0xfd7fd800-0xfd7fdfff irq 18 at device 6.0 on pci2 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:00:00:00:00:01:0e:f8 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:00:00:01:0e:f8 fwe0: Ethernet address: 02:00:00:01:0e:f8 fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) ohci2: mem 0xfd7f7000-0xfd7f7fff irq 19 at device 7.0 on pci2 ohci2: [GIANT-LOCKED] usb2: OHCI version 1.0 usb2: on ohci2 usb2: USB revision 1.0 uhub2: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 3 ports with 3 removable, self powered ohci3: mem 0xfd7fc000-0xfd7fcfff irq 16 at device 7.1 on pci2 ohci3: [GIANT-LOCKED] usb3: OHCI version 1.0 usb3: on ohci3 usb3: USB revision 1.0 uhub3: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pci2: at device 7.2 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 7.3 (no driver attached) pcm0: port 0xcc00-0xcc3f,0xc800-0xc8ff irq 17 at device 7.5 on pci0 pcm0: [GIANT-LOCKED] pcm0: pcib3: at device 10.0 on pci0 pci3: on pcib3 em0: port 0xac00-0xac1f mem 0xfd9c0000-0xfd9dffff,0xfd9e0000-0xfd9fffff irq 17 at device 1.0 on pci3 em0: Ethernet address: 00:02:b3:ed:0b:12 em0: Speed:N/A Duplex:N/A skc0: port 0xa800-0xa8ff mem 0xfd99c000-0xfd99ffff irq 19 at device 3.0 on pci3 skc0: Yukon Gigabit Ethernet 10/100/1000Base-T Adapter sk0: on skc0 sk0: Ethernet address: 00:d0:68:03:d4:99 miibus0: on sk0 e1000phy0: on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX- FDX, autopci0: at device 10.1 (no driver attached) pcib4: at device 11.0 on pci0 pci4: on pcib4 twe0: <3ware Storage Controller. Driver version 1.50.01.002> port 0xbc00-0xbc0f mem 0xfe000000-0xfe7fffff irq 17 at device 1.0 on pci4 twe0: [GIANT-LOCKED] twe0: 4 ports, Firmware FE8S 1.05.00.068, BIOS BE7X 1.08.00.048 pci0: at device 11.1 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0 port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: at iomem 0xcf800-0xd07ff,0xc0000-0xcf7ff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 0.976 msec acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% ATAPI_RESET time = 70us acd0: CDRW at ata1-master UDMA33 twed0: on twe0 twed0: 70910MB (145224064 sectors) em0: Link is up 100 Mbps Full Duplex SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/twed0s1a em0: Link is up 100 Mbps Full Duplex From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 21 14:36:09 2004 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 7969716A4CE for ; Tue, 21 Sep 2004 14:36:09 +0000 (GMT) Received: from ares.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD2FA43D5D for ; Tue, 21 Sep 2004 14:36:07 +0000 (GMT) (envelope-from ftigeot@wolfpond.org) Received: from aoi.wolfpond.org (aoi.wolfpond.org [IPv6:2001:7a8:24db:1:20c:76ff:feb4:27e1]) by ares.wolfpond.org (8.13.1/8.13.1) with ESMTP id i8LEa5Ob021719; Tue, 21 Sep 2004 16:36:05 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.1/8.13.1) with ESMTP id i8LEa8Xd004776; Tue, 21 Sep 2004 16:36:08 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.1/8.13.1/Submit) id i8LEa8Q7004775; Tue, 21 Sep 2004 16:36:08 +0200 (CEST) (envelope-from ftigeot) Date: Tue, 21 Sep 2004 16:36:08 +0200 From: Francois Tigeot To: Bruno Ducrot Message-ID: <20040921143608.GA4487@aoi.wolfpond.org> References: <20040914150419.GA7191@aoi.wolfpond.org> <200409141543.13318.peter@wemm.org> <20040915063512.GA10104@aoi.wolfpond.org> <200409170907.18458.peter@wemm.org> <20040917190850.GA69926@aoi.wolfpond.org> <20040920170013.GQ16132@poupinou.org> <20040920181137.GA1004@aoi.wolfpond.org> <20040921083210.GS16132@poupinou.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040921083210.GS16132@poupinou.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: bios.h question 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: Tue, 21 Sep 2004 14:36:09 -0000 On Tue, Sep 21, 2004 at 10:32:10AM +0200, Bruno Ducrot wrote: > Hi, > > On Mon, Sep 20, 2004 at 08:11:37PM +0200, Francois Tigeot wrote: > > I'm curious: did you find any recent documentation ? All documents on > > Powernow! I could gather on AMD site were for the K6 family. > > Actually it is well documented (for the k7 one, it's another story > though). > > http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_739_7203,00.html > > Especially: > > "BIOS and Kernel Developer's Guide for AMD Athlon 64 and AMD Opteron > Processors", #26094 > look especially at 9.5.5.2 which describe how to make a transition > for example. > > "AMD Athlon 64 Processor Power and Thermal Data Sheet", #30430 > which contains (amongst other things) all the processors supporting > frequency and voltage scalings. > > and of course you have to look at the errata doc. Thanks, I was looking for a separate guide, which was not a good idea :) -- Francois Tigeot From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 21 21:36:40 2004 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 7100D16A4CE for ; Tue, 21 Sep 2004 21:36:40 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id B267743D39 for ; Tue, 21 Sep 2004 21:36:37 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) i8LLZsAq098237; Tue, 21 Sep 2004 17:35:55 -0400 (EDT) (envelope-from jkim@niksun.com) X-RAV-AntiVirus: This e-mail has been scanned for viruses. From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org, rich@neosaint.org Date: Tue, 21 Sep 2004 17:35:51 -0400 User-Agent: KMail/1.6.2 References: <1095722150.33796.38.camel@rfogle.rackspace.com> In-Reply-To: <1095722150.33796.38.camel@rfogle.rackspace.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Message-Id: <200409211735.51574.jkim@niksun.com> Subject: Re: 64-bit HAL for ath_hal module 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: Tue, 21 Sep 2004 21:36:40 -0000 On Monday 20 September 2004 07:15 pm, RIchard N. Fogle wrote: > Greetings, > > There is a 64-bit HAL for the Atheros chipset in the CVS version > of madwiki.. Any chance that will be included in the ath_hal > device for AMD64 FreeBSD? I made an attempt at getting this to > work myself by dropping in the 64-bit, but received a missing > symbol of > "ath_hal_memcpy" when loading the driver. > I then defined "ath_hal_memcpy" as "bcopy((_src), (_dst), > (_size))" as required in ah_osdep.h, and with a version change, the > module loded successfully with the device found. Unfortunately, > when I try to manipulate it after an "ifconfig ath0 up" I get a > kernel panic. Honestly didn't think it would be that easy, but I > thought I'd try. I have a copy of the 64-bit HAL if anyone needs > it.. Something changed somewhere but I'm not all that experienced > in this sort of thing. Until then I'm running i386/FreeBSD > 5.3BETA3 on my dual Opteron. Tried Fedora but it gave me fits. > I'm probably in the minority, but wireless is the only method I > have for connecting to the interenet. Have you tried this? http://docs.freebsd.org/cgi/mid.cgi?200408201412.15438.sam I haven't tried it myself but it seems to have the ath_hal_memcpy() and so on. Just my 2 cents... Jung-uk Kim > Regards, > > Rich From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 21 23:04:51 2004 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 9947816A4CE for ; Tue, 21 Sep 2004 23:04:51 +0000 (GMT) Received: from mailtest.sd73.bc.ca (mailtest.sd73.bc.ca [142.24.13.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64D4443D53 for ; Tue, 21 Sep 2004 23:04:49 +0000 (GMT) (envelope-from fcash-ml@sd73.bc.ca) Received: from localhost (localhost [127.0.0.1]) by mailtest.sd73.bc.ca (Postfix) with ESMTP id 2ED247AA1F; Sun, 19 Sep 2004 14:53:49 -0700 (PDT) Received: by mailtest.sd73.bc.ca (Postfix, from userid 80) id 278167A904; Sun, 19 Sep 2004 14:53:48 -0700 (PDT) Received: from 24.71.131.186 (SquirrelMail authenticated user fcash); by mailtest.sd73.bc.ca with HTTP; Sun, 19 Sep 2004 14:53:48 -0700 (PDT) Message-ID: <61033.24.71.131.186.1095630828.squirrel@24.71.131.186> In-Reply-To: <414CB011.4030206@withagen.nl> References: <20040915003915.2489d1b0.solita2@solitarylight.com> <200409150829.10481.fcash-ml@sd73.bc.ca> <414CB011.4030206@withagen.nl> Date: Sun, 19 Sep 2004 14:53:48 -0700 (PDT) From: "Freddie Cash" To: "Willem Jan Withagen" User-Agent: SquirrelMail/1.5.0 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at sd73.bc.ca cc: freebsd-amd64@freebsd.org Subject: Re: Mainboard suggestions? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: fcash-ml@sd73.bc.ca List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2004 23:04:51 -0000 >> The MSI Master series of mobos work very nicely with FreeBSD, both >> in 32-bit and 64-bit mode. We have a handful of the Master >> dual-AthlonMP boards, and a pair of the Master dual-Opteron boards. >> All deveices on the mobo as detected and usuable under FreeBSD >> 5.2.1 and 5.3. The VIA K8T800 chipset is very stable in our >> testing, and the SATA support is decent (didn't stress it much, but >> never had any problems with it). > Well I'd have to argue about that. I had to replace a MSI K8T > Master2-FAR board with 2 opteron 242 processors because it was causing > crashes to no end during high load. As soon as the load went over 10 > for > a longer period the board crashed. After long discussions with people > doing the amd64 port I bought a new board (Tyan Tiger), and that has > proven rock solid with all the same components. Supposedly it is > because > of "things" with the VIA chipset, but the finer details never became > clear. > And looking at others thru google, there are a lot of people not very > happy with that board. Hmmm, strange. We didn't do much in the way of stress testing, beyond loading 5.2.1, and running buildworld a bunch of times a week to bring it up to 5.3-BETA1. At that point, it was recommissioned as a Fedora Core 2 box running in 32-bit mode, for a Linux-only app. While it was runing 64-bit FreeBSD, though,we never had any problems. It was never super-loaded, though. -- Freddie Cash, CCNT CCLP Helpdesk / Network Support Tech. School District 73 (250) 377-HELP [377-4357] fcash-ml@sd73.bc.ca From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 22 01:57:02 2004 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 386A216A4CE for ; Wed, 22 Sep 2004 01:57:02 +0000 (GMT) Received: from aaryn.lunarpages.com (aaryn.lunarpages.com [216.193.217.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 142AE43D53 for ; Wed, 22 Sep 2004 01:57:02 +0000 (GMT) (envelope-from solita2@solitarylight.com) Received: from 68-173-147-104.nyc.rr.com ([68.173.147.104] helo=bsd.nyc.rr.com) by aaryn.lunarpages.com with smtp (Exim 4.42) id 1C9wNi-0006f9-7p for freebsd-amd64@freebsd.org; Tue, 21 Sep 2004 18:57:18 -0700 Date: Tue, 21 Sep 2004 21:50:06 -0500 From: John Wilson To: freebsd-amd64@freebsd.org Message-Id: <20040921215006.02385d26.solita2@solitarylight.com> In-Reply-To: <200409170920.32739.peter@wemm.org> References: <20040915003915.2489d1b0.solita2@solitarylight.com> <200409151107.19224.groot@kde.org> <200409170920.32739.peter@wemm.org> X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - aaryn.lunarpages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - solitarylight.com X-Source: X-Source-Args: X-Source-Dir: Subject: Re: Mainboard suggestions? 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: Wed, 22 Sep 2004 01:57:02 -0000 Hello all, First off, I would just like to thank everyone who replied to my initial inquery both here on the list as well as via e-mail. Trying to choose an AMD64 mainboard has, literally, been a virtual nightmare. All of my previous home built machines have always centered on Intel CPU's and Intel brand mainboards. For whatever reasons, I've always been wary of other manufacturers. At any rate, I think I've stabilized my choice on the ABit KV8 Pro mainboard. Many of the reviews that I've read seem to value this board quite well, and from what I've been able to gather from various other sources, it is well supported in FreeBSD. In regard to the ALC850 audio, it does appear to be supported via generic ac97. Grep'ing /usr/src/sys/dev/sound/pcm/ac97.h shows this. Based on a quick google search, it appears to be one of the better onboard implementations to boot, which is nice. The VT6122 GB Ethernet also appears to be supported by the 'vge' driver. The rest of the board is rather standard stuff. All of this is truly wonderful, but my hesitation remains in a few other key areas. ABit doesn't seem to have the following as say, Asus or MSI. I do understand that this really means nothing in itself, and based on the reviews that I've read it does seem like a nice board. However, I've not been able to find that much information on -personal- experiences with this board in semi-long term... terms. Is anyone here running this mainboard? If so, what are your impressions of it? Good, bad? Anything anyone else can add would be most appreciated. : ) Thank you, John Wilson. From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 22 01:57:25 2004 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 98EE116A4CE for ; Wed, 22 Sep 2004 01:57:25 +0000 (GMT) Received: from mxsf25.cluster1.charter.net (mxsf25.cluster1.charter.net [209.225.28.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09ED543D1D for ; Wed, 22 Sep 2004 01:57:25 +0000 (GMT) (envelope-from jwest@classiccmp.org) Received: from mxip17.cluster1.charter.net (mxip17a.cluster1.charter.net [209.225.28.147])i8M1vNsf001946 for ; Tue, 21 Sep 2004 21:57:23 -0400 Received: from overland10k.mo24.107.24.220.charter-stl.com (HELO HPLAPTOP) (24.107.24.220) by mxip17.cluster1.charter.net with SMTP; 21 Sep 2004 21:57:24 -0400 X-Ironport-AV: i="3.84,170,1091419200"; d="scan'217,208"; a="329020984:sNHT19348972" Message-ID: <000601c4a047$8243f370$6400a8c0@HPLAPTOP> From: "Jay West" To: Date: Tue, 21 Sep 2004 20:57:25 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Dual AMD64, APCI woes, 5.2.1-Rel, Help! 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: Wed, 22 Sep 2004 01:57:25 -0000 I'm trying to get another FreeBSD system up at our office for a mission = critical app. Unfortunately if I can't figure this problem out, FreeBSD = will be tossed and Linux used instead and I really don't want that. = We've always been a FreeBSD/i386 house, this is our first foray into = Opteron. Here's the particulars.... Rhapsody HDAMA-F mainboard Dual bge 10/100/1000 nics 8gb ram dual Opteron 2.0ghz cpus LSI megaraid amr 320-2X raid controller w/128mb cache Four ultra-320 15Krpm scsi drives, 35gb each The drives are set up raid 10. A striped set of 70gb, then a 70gb = mirror. I'm using the amd64 ISO for 5.2.1-Release My problem seems to center around APCI. If I disable APCI in the bios = and boot off the install CD and select the boot without APCI, the system = comes up and installs just fine. However, it seems to only recognize one = cpu. At least, the sysctl variables I looked at appeared to indicate = just one cpu and the top display didn't have a cpu column. If I leave APCI enabled, the system boots off the cd fine but when the = installed starts to probe the devices, it gets stuck just after the line = for the CD drive (acd0). I am pretty certain that that is exactly the = point where it's probing the scsi drives, because if APCI is turned off = - right after the acd0 probe is where geom starts and the disk is = recognized. The lsi controller is definitely recognized ok further up in = the probe display. I'd just disable APCI to get around this, but if FreeBSD will only use = one cpu.... management will switch to Suse (which purportedly runs this = configuration perfectly) and I'd really like to stay FreeBSD. Normally = I'd just love to dive into the new and unknown (to me) opteron/5.X/APCI = stuff. But I'm completely out of time on this project to get the machine = up. Could anyone possibly offer me some quick pointers or help on this? = I've googled lots and so far not come up with anything concrete, other = than "disable APCI" which seems to leave me with just one cpu. Please cc replies to jwest@classiccmp.org as I'm not on this list. Regards, Jay West From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 22 02:24:41 2004 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 DEB9216A4CE for ; Wed, 22 Sep 2004 02:24:41 +0000 (GMT) Received: from salvador.pacific.net.sg (salvador.pacific.net.sg [203.120.90.219]) by mx1.FreeBSD.org (Postfix) with SMTP id ABE9943D55 for ; Wed, 22 Sep 2004 02:24:40 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: (qmail 19279 invoked from network); 22 Sep 2004 02:24:39 -0000 Received: from unknown (HELO maxwell6.pacific.net.sg) (203.120.90.212) by salvador with SMTP; 22 Sep 2004 02:24:39 -0000 Received: from [192.168.0.107] ([210.24.202.141]) by maxwell6.pacific.net.sg with ESMTP <20040922022438.FEEZ17051.maxwell6.pacific.net.sg@[192.168.0.107]>; Wed, 22 Sep 2004 10:24:38 +0800 Message-ID: <4150E25F.90600@pacific.net.sg> Date: Wed, 22 Sep 2004 10:24:31 +0800 From: Erich Dollansky User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Wilson References: <20040915003915.2489d1b0.solita2@solitarylight.com> <200409151107.19224.groot@kde.org> <200409170920.32739.peter@wemm.org> <20040921215006.02385d26.solita2@solitarylight.com> In-Reply-To: <20040921215006.02385d26.solita2@solitarylight.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Mainboard suggestions? 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: Wed, 22 Sep 2004 02:24:42 -0000 Hi, John Wilson wrote: > > Trying to choose an AMD64 mainboard has, literally, been a virtual > nightmare. All of my previous home built machines have always centered > on Intel CPU's and Intel brand mainboards. For whatever reasons, I've > always been wary of other manufacturers. > My last Intel CPU was a Pentium 166. You will face a very simple problem. The Non-Intel people use once in a while a different lingo to express things. There are no real technical issues with the other CPUs. Just minor things which also happen with Intel CPUs. Sometimes you will notice that the defaults are in favour of Intel. Have fun with your new board. Erich From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 22 03:20:19 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 373E716A4CE for ; Wed, 22 Sep 2004 03:20:19 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 131EB43D41 for ; Wed, 22 Sep 2004 03:20:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i8M3KIuE072277 for ; Wed, 22 Sep 2004 03:20:18 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i8M3KI4e072276; Wed, 22 Sep 2004 03:20:18 GMT (envelope-from gnats) Date: Wed, 22 Sep 2004 03:20:18 GMT Message-Id: <200409220320.i8M3KI4e072276@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Nicolas Blais Subject: Re: amd64/67745: boot fails on compaq presario r3000z X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Nicolas Blais List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2004 03:20:19 -0000 The following reply was made to PR amd64/67745; it has been noted by GNATS. From: Nicolas Blais To: freebsd-gnats-submit@freebsd.org, newntrbr@ucla.edu Cc: Subject: Re: amd64/67745: boot fails on compaq presario r3000z Date: Tue, 21 Sep 2004 23:10:57 -0400 Hi, I have a Compaq Presario R3000 too (A64-3200) and I can't boot 5.3-BETA5 or any other iso. Will any work around make it to 5.3-RELEASE? Thanks, Nicolas. From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 22 07:39:59 2004 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 E4D6316A4CE for ; Wed, 22 Sep 2004 07:39:59 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6055A43D4C for ; Wed, 22 Sep 2004 07:39:58 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from [212.61.27.71] (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with ESMTP id i8M7dpEg018315; Wed, 22 Sep 2004 09:39:52 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <41512C49.9070107@withagen.nl> Date: Wed, 22 Sep 2004 09:39:53 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jay West References: <000601c4a047$8243f370$6400a8c0@HPLAPTOP> In-Reply-To: <000601c4a047$8243f370$6400a8c0@HPLAPTOP> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Dual AMD64, APCI woes, 5.2.1-Rel, Help! 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: Wed, 22 Sep 2004 07:40:00 -0000 5.2.1 is rather old.... I'd give the 5.3-BETA's a try, if only to see if the problem is solved in the nearby future... Either upgrade by cvsup, make build{world,kernel} Or grab the ISO's --WjW Jay West wrote: >I'm trying to get another FreeBSD system up at our office for a mission critical app. Unfortunately if I can't figure this problem out, FreeBSD will be tossed and Linux used instead and I really don't want that. We've always been a FreeBSD/i386 house, this is our first foray into Opteron. Here's the particulars.... > >Rhapsody HDAMA-F mainboard >Dual bge 10/100/1000 nics >8gb ram >dual Opteron 2.0ghz cpus >LSI megaraid amr 320-2X raid controller w/128mb cache >Four ultra-320 15Krpm scsi drives, 35gb each > >The drives are set up raid 10. A striped set of 70gb, then a 70gb mirror. > >I'm using the amd64 ISO for 5.2.1-Release > >My problem seems to center around APCI. If I disable APCI in the bios and boot off the install CD and select the boot without APCI, the system comes up and installs just fine. However, it seems to only recognize one cpu. At least, the sysctl variables I looked at appeared to indicate just one cpu and the top display didn't have a cpu column. > >If I leave APCI enabled, the system boots off the cd fine but when the installed starts to probe the devices, it gets stuck just after the line for the CD drive (acd0). I am pretty certain that that is exactly the point where it's probing the scsi drives, because if APCI is turned off - right after the acd0 probe is where geom starts and the disk is recognized. The lsi controller is definitely recognized ok further up in the probe display. > >I'd just disable APCI to get around this, but if FreeBSD will only use one cpu.... management will switch to Suse (which purportedly runs this configuration perfectly) and I'd really like to stay FreeBSD. Normally I'd just love to dive into the new and unknown (to me) opteron/5.X/APCI stuff. But I'm completely out of time on this project to get the machine up. Could anyone possibly offer me some quick pointers or help on this? I've googled lots and so far not come up with anything concrete, other than "disable APCI" which seems to leave me with just one cpu. > >Please cc replies to jwest@classiccmp.org as I'm not on this list. > >Regards, > >Jay West > >_______________________________________________ >freebsd-amd64@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 >To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > > > From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 22 12:36:51 2004 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 635B816A4CE for ; Wed, 22 Sep 2004 12:36:51 +0000 (GMT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 456EF43D1D for ; Wed, 22 Sep 2004 12:36:51 +0000 (GMT) (envelope-from rob2@pythonemproject.com) Received: from [192.168.1.102] (c-67-169-203-186.client.comcast.net[67.169.203.186]) by comcast.net (rwcrmhc13) with ESMTP id <2004092212365001500eg5gge> (Authid: europax); Wed, 22 Sep 2004 12:36:50 +0000 Message-ID: <41517226.9040201@pythonemproject.com> Date: Wed, 22 Sep 2004 05:37:58 -0700 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040816 X-Accept-Language: en-us, en MIME-Version: 1.0 To: amd-list Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: new to AMD 64 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: Wed, 22 Sep 2004 12:36:51 -0000 So far I have an MSI K8TNeo mobo, AMD 64 3700, Adaptec 29160 with 2 10K/s SCSI 160 drives, 450W power, Plextor 44-28-44CDRW, Soundblaster, and several nics. Hopefully I haven't forgot anything, oh and I have the iso from the 5.3 betas. Wish me luck, today is judgement day. Sincerely, Rob From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 23 06:18:17 2004 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 8706316A4CE for ; Thu, 23 Sep 2004 06:18:17 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DBB743D5C for ; Thu, 23 Sep 2004 06:18:17 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id i8N6I6pW063945; Wed, 22 Sep 2004 23:18:07 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i8N6I6gW063944; Wed, 22 Sep 2004 23:18:06 -0700 (PDT) (envelope-from obrien) Date: Wed, 22 Sep 2004 23:18:06 -0700 From: "David O'Brien" To: Jay West Message-ID: <20040923061806.GA63633@dragon.nuxi.com> References: <000601c4a047$8243f370$6400a8c0@HPLAPTOP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000601c4a047$8243f370$6400a8c0@HPLAPTOP> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: Dual AMD64, APCI woes, 5.2.1-Rel, Help! X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2004 06:18:17 -0000 On Tue, Sep 21, 2004 at 08:57:25PM -0500, Jay West wrote: > I'm trying to get another FreeBSD system up at our office for a mission > critical app. Unfortunately if I can't figure this problem out, FreeBSD > will be tossed and Linux used instead and I really don't want that. > We've always been a FreeBSD/i386 house, this is our first foray into > Opteron. Here's the particulars.... > > Rhapsody HDAMA-F mainboard .. > My problem seems to center around APCI. What BIOS version are you using? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 23 19:50:28 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE1C116A4CE for ; Thu, 23 Sep 2004 19:50:28 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8874E43D31 for ; Thu, 23 Sep 2004 19:50:28 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i8NJoSIm051335 for ; Thu, 23 Sep 2004 19:50:28 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i8NJoSEl051334; Thu, 23 Sep 2004 19:50:28 GMT (envelope-from gnats) Date: Thu, 23 Sep 2004 19:50:28 GMT Message-Id: <200409231950.i8NJoSEl051334@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: =?ISO-8859-2?Q?Toma=BE_Bor=B9tnar?= Subject: Re: amd64/71471: Can not install 5.3beta3/amd64 on IBM eServer 325 with ServeRAID-6M X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: =?ISO-8859-2?Q?Toma=BE_Bor=B9tnar?= List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2004 19:50:28 -0000 The following reply was made to PR amd64/71471; it has been noted by GNATS. From: =?ISO-8859-2?Q?Toma=BE_Bor=B9tnar?= To: freebsd-gnats-submit@FreeBSD.org, tomaz.borstnar@over.net Cc: Subject: Re: amd64/71471: Can not install 5.3beta3/amd64 on IBM eServer 325 with ServeRAID-6M Date: Thu, 23 Sep 2004 21:45:17 +0200 Things are getting worse. Now it does not even boot into sysinstall! It hangs after printing out lines for bge0. From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 23 20:20:33 2004 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 C189216A4CE for ; Thu, 23 Sep 2004 20:20:33 +0000 (GMT) Received: from slyna.neosaint.org (slyna.neosaint.org [207.3.94.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05A6943D41 for ; Thu, 23 Sep 2004 20:20:33 +0000 (GMT) (envelope-from rich@neosaint.org) Received: from [10.1.101.133] (nat-vlan200.sat.rackspace.com [64.39.1.10]) (authenticated bits=0)i8NKKKkI002550; Thu, 23 Sep 2004 15:20:26 -0500 From: "RIchard N. Fogle" To: =?iso-8859-2?Q?Toma=BE_Bor=B9tnar?= In-Reply-To: <200409231950.i8NJoSEl051334@freefall.freebsd.org> References: <200409231950.i8NJoSEl051334@freefall.freebsd.org> Content-Type: text/plain; charset=iso-8859-2 Message-Id: <1095970833.740.24.camel@rfogle.rackspace.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 23 Sep 2004 15:20:33 -0500 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed version=3.0.0 X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on slyna.neosaint.org cc: freebsd-amd64@freebsd.org Subject: Re: amd64/71471: Can not install 5.3beta3/amd64 on IBM eServer 325 with ServeRAID-6M X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: rich@neosaint.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2004 20:20:33 -0000 Strange enough, I had similiar errors on my Tyan Tiger KSW dual proc.. I went into the bios and changed "PCI SCAN ORDER" to "DESCENT" instead of "ASCENT", then it worked. The kernel would hang on the network card, then the SATA RAID card afterwards, etc.. Hope it helps. Rich On Thu, 2004-09-23 at 14:50, Toma¾ Bor¹tnar wrote: > The following reply was made to PR amd64/71471; it has been noted by GNATS. > > From: =?ISO-8859-2?Q?Toma=BE_Bor=B9tnar?= > To: freebsd-gnats-submit@FreeBSD.org, tomaz.borstnar@over.net > Cc: > Subject: Re: amd64/71471: Can not install 5.3beta3/amd64 on IBM eServer 325 > with ServeRAID-6M > Date: Thu, 23 Sep 2004 21:45:17 +0200 > > Things are getting worse. Now it does not even boot into sysinstall! It hangs after printing out lines for bge0. > > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 24 13:38:33 2004 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 D040C16A4CE for ; Fri, 24 Sep 2004 13:38:33 +0000 (GMT) Received: from web14103.mail.yahoo.com (web14103.mail.yahoo.com [216.136.172.133]) by mx1.FreeBSD.org (Postfix) with SMTP id A79B443D49 for ; Fri, 24 Sep 2004 13:38:33 +0000 (GMT) (envelope-from cguttesen@yahoo.dk) Message-ID: <20040924133833.80707.qmail@web14103.mail.yahoo.com> Received: from [194.248.174.58] by web14103.mail.yahoo.com via HTTP; Fri, 24 Sep 2004 15:38:33 CEST Date: Fri, 24 Sep 2004 15:38:33 +0200 (CEST) From: Claus Guttesen To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: unable to install beta5 (amd64) on a Dell 2850 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, 24 Sep 2004 13:38:33 -0000 Hi. I'm trying to install beta5 (amd64) on a Dell 2850 with dual Nocona CPU @ 3.2 GHz and 4 GB RAM; Perc 4e/Di RAID-controller. It stops when it's probing the IDE-CD (Teac). I did manage to install beta5 (amd64) on a Dell 1850 without any problems. This has an LSI-card (mpt-driver). The amd64 port seems slightly faster than it's i386-counterpart, so I'd like to install amd64 on the 2850'er as well. I'm able to boot beta4 and -5 (i386) without any problems. regards Claus From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 24 13:54:24 2004 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 17F4616A4CE for ; Fri, 24 Sep 2004 13:54:24 +0000 (GMT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id F090A43D4C for ; Fri, 24 Sep 2004 13:54:23 +0000 (GMT) (envelope-from rob2@pythonemproject.com) Received: from pythonemproject.com (c-67-169-203-186.client.comcast.net[67.169.203.186]) by comcast.net (rwcrmhc13) with ESMTP id <20040924135423015003m27be> (Authid: europax); Fri, 24 Sep 2004 13:54:23 +0000 Message-ID: <41542753.30409@pythonemproject.com> Date: Fri, 24 Sep 2004 06:55:31 -0700 From: Rob User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: square power socket on AMD 64 boards X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: rob2@pythonemproject.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2004 13:54:24 -0000 Is it mandatory to use this square socket or just an option? If its mandatory, another trip to computer store today. Rob. From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 24 16:47:58 2004 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 0F67616A4CF for ; Fri, 24 Sep 2004 16:47:58 +0000 (GMT) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DAC243D1D for ; Fri, 24 Sep 2004 16:47:56 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from [192.168.245.231] ([213.112.167.129] [213.112.167.129]) by mxfep01.bredband.com with ESMTP <20040924164755.BHSC19800.mxfep01.bredband.com@[192.168.245.231]>; Fri, 24 Sep 2004 18:47:55 +0200 Message-ID: <41544F5B.4080509@bredband.net> Date: Fri, 24 Sep 2004 18:46:19 +0200 From: Lars Tunkrans Organization: None User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20040618 X-Accept-Language: en-us, en MIME-Version: 1.0 To: rob2@pythonemproject.com References: <41542753.30409@pythonemproject.com> In-Reply-To: <41542753.30409@pythonemproject.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: square power socket on AMD 64 boards 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, 24 Sep 2004 16:47:58 -0000 Rob wrote: > Is it mandatory to use this square socket or just an option? IT IS Mandatory !!! If its > mandatory, another trip to computer store today. Rob. > See: http://www.compute-aid.com/atxspec.html //Lars From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 24 18:05:34 2004 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 2A99216A4D2 for ; Fri, 24 Sep 2004 18:05:34 +0000 (GMT) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6628743D1D for ; Fri, 24 Sep 2004 18:05:10 +0000 (GMT) (envelope-from rob2@pythonemproject.com) Received: from pythonemproject.com (c-67-169-203-186.client.comcast.net[67.169.203.186]) by comcast.net (sccrmhc11) with ESMTP id <20040924180507011008n74be> (Authid: europax); Fri, 24 Sep 2004 18:05:07 +0000 Message-ID: <41546216.3020408@pythonemproject.com> Date: Fri, 24 Sep 2004 11:06:14 -0700 From: Rob User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lars Tunkrans , freebsd-amd64@freebsd.org References: <41542753.30409@pythonemproject.com> <41544F5B.4080509@bredband.net> In-Reply-To: <41544F5B.4080509@bredband.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: square power socket on AMD 64 boards X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: rob2@pythonemproject.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2004 18:05:34 -0000 Lars Tunkrans wrote: > Rob wrote: > >> Is it mandatory to use this square socket or just an option? > > > IT IS Mandatory !!! > > If its > >> mandatory, another trip to computer store today. Rob. >> > > See: > > http://www.compute-aid.com/atxspec.html > > //Lars > Thank you!! Sincerely, Rob. From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 24 21:11:39 2004 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 1EC4116A4CE for ; Fri, 24 Sep 2004 21:11:39 +0000 (GMT) Received: from smtp.unsam.edu.ar (smtp.unsam.edu.ar [170.210.48.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F84643D31 for ; Fri, 24 Sep 2004 21:11:28 +0000 (GMT) (envelope-from fernan@iib.unsam.edu.ar) Received: from pi.iib.unsam.edu.ar (pi.iib.unsam.edu.ar [192.168.10.11]) by smtp.unsam.edu.ar (8.12.6/8.12.6) with ESMTP id i8OLMlOx031792 for ; Fri, 24 Sep 2004 18:22:50 -0300 (ART) (envelope-from fernan@iib.unsam.edu.ar) Received: from pi.iib.unsam.edu.ar (localhost.iib.unsam.edu.ar [127.0.0.1]) by pi.iib.unsam.edu.ar (8.12.11/8.12.9) with ESMTP id i8OL9n5R007524 for ; Fri, 24 Sep 2004 18:09:51 -0300 (ART) (envelope-from fernan@iib.unsam.edu.ar) Received: (from fernan@localhost) by pi.iib.unsam.edu.ar (8.12.11/8.12.11/Submit) id i8OL9l5K007523 for freebsd-amd64@freebsd.org; Fri, 24 Sep 2004 18:09:47 -0300 (ART) (envelope-from fernan@iib.unsam.edu.ar) X-Authentication-Warning: pi.iib.unsam.edu.ar: fernan set sender to fernan@iib.unsam.edu.ar using -f Date: Fri, 24 Sep 2004 18:09:47 -0300 From: Fernan Aguero To: freebsd-amd64@freebsd.org Message-ID: <20040924210947.GC6597@iib.unsam.edu.ar> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: freebsd i386 on amd64 hardware? 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, 24 Sep 2004 21:11:39 -0000 Hi! I'm planning to buy a new box, and would like to move to amd64 hardware. Now, I'm running FreeBSD-4.10 on i386 right now (Pentium III) and I guess that the switch to both a different architecture and a different branch could be too much (I don't know for sure, but since it is possible I need to take it into account). My question would thus be: is it possible to run 32-bit FreeBSD (4.x) on amd64 hardware? If the answer is yes, perhaps I could go for a dual bootable box (32 bit 4.10 / 64bit 5.3) for a while, until I see how it all goes. Thanks in advance, Fernan PS: I've been reading the list for recommended motherboards and chipsets and probably will be sticking to an MSI with a Via K8T800 chipset. If you have other suggestions I'll be more than glad to hear them. Thanks! -- Fernan Aguero - fernan at iib.unsam.edu.ar Phone: +54 11 4580-7255/7 ext 310, Fax: +54 11 4752-9639 Check http://genoma.unsam.edu.ar/~fernan for more info. From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 24 21:15:29 2004 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 993DB16A4CE for ; Fri, 24 Sep 2004 21:15:29 +0000 (GMT) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0165C43D1D for ; Fri, 24 Sep 2004 21:15:29 +0000 (GMT) (envelope-from groot@kde.org) Received: from odin.cs.kun.nl [131.174.33.33] (helo=localhost) by pandora.cs.kun.nl (8.12.10/4.18) with ESMTP id i8OLFQSd024997; Fri, 24 Sep 2004 23:15:26 +0200 (MEST) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Fri, 24 Sep 2004 23:15:02 +0200 User-Agent: KMail/1.7.50 References: <20040924210947.GC6597@iib.unsam.edu.ar> In-Reply-To: <20040924210947.GC6597@iib.unsam.edu.ar> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200409242315.02959.groot@kde.org> cc: Fernan Aguero Subject: Re: freebsd i386 on amd64 hardware? 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, 24 Sep 2004 21:15:29 -0000 On Friday 24 September 2004 23:09, Fernan Aguero wrote: > is it possible to run 32-bit FreeBSD (4.x) on amd64 > hardware? Yes. The amd64 runs like a nice fast x86 machine if you run a 32-bit OS like FreeBSD x86 4.10 on it. > If the answer is yes, perhaps I could go for a dual bootable > box (32 bit 4.10 / 64bit 5.3) for a while, until I > see how it all goes. A good idea - you never know when 5-UNSTABLE is going to fall over, it seems. From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 24 21:19:16 2004 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 A52BC16A4CE for ; Fri, 24 Sep 2004 21:19:16 +0000 (GMT) Received: from web14125.mail.yahoo.com (web14125.mail.yahoo.com [66.163.171.116]) by mx1.FreeBSD.org (Postfix) with SMTP id 7843543D2F for ; Fri, 24 Sep 2004 21:19:16 +0000 (GMT) (envelope-from cguttesen@yahoo.dk) Message-ID: <20040924211916.58977.qmail@web14125.mail.yahoo.com> Received: from [194.248.174.58] by web14125.mail.yahoo.com via HTTP; Fri, 24 Sep 2004 23:19:16 CEST Date: Fri, 24 Sep 2004 23:19:16 +0200 (CEST) From: Claus Guttesen To: Fernan Aguero , freebsd-amd64@freebsd.org In-Reply-To: <20040924210947.GC6597@iib.unsam.edu.ar> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: freebsd i386 on amd64 hardware? 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, 24 Sep 2004 21:19:16 -0000 > is it possible to run 32-bit FreeBSD (4.x) on amd64 > hardware? Last year I purchased a dual opteron @ 1.6 GHz, and couldn't compile php4 with mcrypt properly using the amd64-port and had also problems with acpi, so I installed the i386-port (FreeBSD 5.x) instead. 4.10 should the same way as well. Works like a charm, the cpu performs better than their intel-counterparts. Good luck Claus From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 24 21:23:31 2004 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 AA5FE16A4CE for ; Fri, 24 Sep 2004 21:23:31 +0000 (GMT) Received: from web14125.mail.yahoo.com (web14125.mail.yahoo.com [66.163.171.116]) by mx1.FreeBSD.org (Postfix) with SMTP id 9686643D2F for ; Fri, 24 Sep 2004 21:23:31 +0000 (GMT) (envelope-from cguttesen@yahoo.dk) Message-ID: <20040924212331.59439.qmail@web14125.mail.yahoo.com> Received: from [194.248.174.58] by web14125.mail.yahoo.com via HTTP; Fri, 24 Sep 2004 23:23:31 CEST Date: Fri, 24 Sep 2004 23:23:31 +0200 (CEST) From: Claus Guttesen To: Adriaan de Groot , freebsd-amd64@freebsd.org In-Reply-To: <200409242315.02959.groot@kde.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: Fernan Aguero Subject: Re: freebsd i386 on amd64 hardware? 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, 24 Sep 2004 21:23:31 -0000 > A good idea - you never know when 5-UNSTABLE is > going to fall over, it seems. Well, I don't agree. I've been running 5.x for more than one year now. My nfs-server has current from February this year, was up for 118 days before I took it down for maintenance. Have many webservers as well on 5.x. All in production. Claus From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 24 21:23:56 2004 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 8301816A4CE for ; Fri, 24 Sep 2004 21:23:56 +0000 (GMT) Received: from slyna.neosaint.org (slyna.neosaint.org [207.3.94.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id D73D743D31 for ; Fri, 24 Sep 2004 21:23:55 +0000 (GMT) (envelope-from rich@neosaint.org) Received: from [10.1.101.133] (nat-vlan200.sat.rackspace.com [64.39.1.10]) (authenticated bits=0)i8OLNiA7017673; Fri, 24 Sep 2004 16:23:49 -0500 From: "RIchard N. Fogle" To: Claus Guttesen In-Reply-To: <20040924211916.58977.qmail@web14125.mail.yahoo.com> References: <20040924211916.58977.qmail@web14125.mail.yahoo.com> Content-Type: text/plain Message-Id: <1096061032.636.4.camel@rfogle.rackspace.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 24 Sep 2004 16:23:52 -0500 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed version=3.0.0 X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on slyna.neosaint.org cc: Fernan Aguero cc: freebsd-amd64@freebsd.org Subject: Re: freebsd i386 on amd64 hardware? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: rich@neosaint.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2004 21:23:56 -0000 The i386 distribution works great on my dual Opteron.. I can't use the AMD64 version until I figure out how to get the Atheros wireless driver working with the new 64-bit HAL :) The speed is amazing. R On Fri, 2004-09-24 at 16:19, Claus Guttesen wrote: > > is it possible to run 32-bit FreeBSD (4.x) on amd64 > > hardware? > > Last year I purchased a dual opteron @ 1.6 GHz, and > couldn't compile php4 with mcrypt properly using the > amd64-port and had also problems with acpi, so I > installed the i386-port (FreeBSD 5.x) instead. 4.10 > should the same way as well. Works like a charm, the > cpu performs better than their intel-counterparts. > > Good luck > > Claus > > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 24 21:34:09 2004 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 6725016A4CF for ; Fri, 24 Sep 2004 21:34:09 +0000 (GMT) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDF2743D39 for ; Fri, 24 Sep 2004 21:34:07 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from [192.168.245.231] ([213.112.167.129] [213.112.167.129]) by mxfep02.bredband.com with ESMTP <20040924213406.HDYU19503.mxfep02.bredband.com@[192.168.245.231]>; Fri, 24 Sep 2004 23:34:06 +0200 Message-ID: <4154926E.7020407@bredband.net> Date: Fri, 24 Sep 2004 23:32:30 +0200 From: Lars Tunkrans Organization: None User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20040618 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Fernan Aguero References: <20040924210947.GC6597@iib.unsam.edu.ar> In-Reply-To: <20040924210947.GC6597@iib.unsam.edu.ar> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: freebsd i386 on amd64 hardware? 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, 24 Sep 2004 21:34:09 -0000 Fernan Aguero wrote: > Hi! > > I'm planning to buy a new box, and would like to move to > amd64 hardware. > My question would thus be: > > is it possible to run 32-bit FreeBSD (4.x) on amd64 > hardware? > I switched from an Athlon-XP 2100+ (1733 Mhz) to the Athlon64 3800+ (2400 Mhz) on the MSI K8T Neo2 Fir socket939 board 10 days ago. When running 5.2.1-Release (i386) I find the the time to complete a seti@home workunit has dropped from 5+ hours to 2 hours 55 minutes !!! //Lars From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 25 01:24:15 2004 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 7A8F416A4CE for ; Sat, 25 Sep 2004 01:24:15 +0000 (GMT) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FBC043D39 for ; Sat, 25 Sep 2004 01:24:15 +0000 (GMT) (envelope-from rob2@pythonemproject.com) Received: from pythonemproject.com (c-67-169-203-186.client.comcast.net[67.169.203.186]) by comcast.net (sccrmhc11) with ESMTP id <200409250124140110070nmqe> (Authid: europax); Sat, 25 Sep 2004 01:24:14 +0000 Message-ID: <4154C903.1050504@pythonemproject.com> Date: Fri, 24 Sep 2004 18:25:23 -0700 From: Rob User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Failure X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: rob2@pythonemproject.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Sep 2004 01:24:15 -0000 Not even able to get any text out of the bios on my system. AMD 64 3800. Abit AV8 mobo, 3 banksof 512k 400Mhz memory, Adaptek 29160 with 2 SCSI 160 drives. uP was OEM so using Zalman fan and heat sink. Video is old Abit board, model now unknown, but worked well for 3 os's and a few years. When I power up I get the whirring fans and a bright red led. Nothing seems to get abnormally hot. Maybe I need new video card. Rob. From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 25 06:55:18 2004 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 C070E16A4CE for ; Sat, 25 Sep 2004 06:55:18 +0000 (GMT) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41CA543D69 for ; Sat, 25 Sep 2004 06:55:17 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from [192.168.245.231] ([213.112.167.129] [213.112.167.129]) by mxfep01.bredband.com with ESMTP <20040925065515.FTGR19800.mxfep01.bredband.com@[192.168.245.231]>; Sat, 25 Sep 2004 08:55:15 +0200 Message-ID: <415515F2.3060907@bredband.net> Date: Sat, 25 Sep 2004 08:53:38 +0200 From: Lars Tunkrans Organization: None User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20040618 X-Accept-Language: en-us, en MIME-Version: 1.0 To: rob2@pythonemproject.com, freebsd-amd64@freebsd.org References: <4154C903.1050504@pythonemproject.com> In-Reply-To: <4154C903.1050504@pythonemproject.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Failure 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: Sat, 25 Sep 2004 06:55:18 -0000 Rob wrote: > Not even able to get any text out of the bios on my system. AMD 64 > 3800. Abit AV8 mobo, 3 banksof 512k 400Mhz memory, Adaptek 29160 with > 2 SCSI 160 drives. uP was OEM so using Zalman fan and heat sink. Video > is old Abit board, model now unknown, but worked well for 3 os's and a > few years. > When I power up I get the whirring fans and a bright red led. Nothing > seems to get abnormally hot. Maybe I need new video card. Its more likely that you need to change your memory configuration, The socket 939 3800+ is using a 128 bit memory bus. www.abit.com.tw states that the AV8 board is socket 939. I would use 2 or 4 non-ecc memory Dimms from the approved list: http://www.abit.com.tw/test_report/AV8_Series/memory.php Using 3 Dimms is not going to work ! You need to place equal number of Dimms in both memory-banks, One in a blue slot and one in purple slot according to the image on Abits website. Its probably better to continue this discussion here: http://lists.freebsd.org/mailman/listinfo/freebsd-hardware or here: http://www.freebsdforums.org/forums/forumdisplay.php?s=&forumid=5 This mailinglist is supposed to address software issues in the Freebsd AMD64 port. Regards //Lars From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 25 11:47:37 2004 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 6E90E16A4CE for ; Sat, 25 Sep 2004 11:47:37 +0000 (GMT) Received: from freenix.no (atreides.freenix.no [212.33.142.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B60443D3F for ; Sat, 25 Sep 2004 11:47:35 +0000 (GMT) (envelope-from shamz@atreides.freenix.no) Received: from atreides.freenix.no (localhost [127.0.0.1]) by freenix.no (8.12.11/8.12.11) with ESMTP id i8PBlTbv031967 for ; Sat, 25 Sep 2004 13:47:33 +0200 (CEST) (envelope-from shamz@atreides.freenix.no) Received: (from shamz@localhost) by atreides.freenix.no (8.12.11/8.12.11/Submit) id i8PBlOrr031966 for freebsd-amd64@freebsd.org; Sat, 25 Sep 2004 13:47:24 +0200 (CEST) (envelope-from shamz) Date: Sat, 25 Sep 2004 13:47:24 +0200 From: Shaun Jurrens To: freebsd-amd64@freebsd.org Message-ID: <20040925114724.GH90420@atreides.freenix.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.10-RELEASE-p2 X-Philosophy: If you can read this, you're too close. X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on atreides X-Virus-Status: Clean Subject: A number of show-stopper bugs... 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: Sat, 25 Sep 2004 11:47:37 -0000 Hei guys, This is just an informal heads up at the moment, perhaps just to either get a few hits with the clue bat or to inform about some nasty kernel bugs. I have run across a number of things that produce unbootable or unstable kernels: 1) Loading the sound and snd_via8233 modules after boot crashed my machine within 30 minutes. I first received a ca. 50Hz white noise sound before freezing the box and subsequent reboot. I was using mpg123 with a 1024kb buffer, downloading via scp and running Mozilla. No crashdump available yet... With both compiled in the kernel, things seem to be stable. 2) Adding NETGRAPH modules to the kernel config produces unbootable kernels in almost any configuration (trying to get the bluetooth stuff working). Using the kernel modules produced no working results. No crashdump yet... With any luck I'll get far enough here to give more concrete results with dumps. dmesg, fwiw (input munged from cut-n-paste): Copyright (c) 1992-2004 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.3-BETA5 #2: Sun Sep 19 22:38:28 CEST 2004 root@dakota:/usr/obj/usr/src/sys/DAKOTA64 WARNING: WITNESS option enabled, expect reduced performance. ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3200+ (2002.57-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf48 Stepping = 8 Features=0x78bfbff AMD Features=0xe0500800 real memory = 1072889856 (1023 MB) avail memory = 1026969600 (979 MB) ioapic0: Changing APIC ID to 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xf0000000-0xf7ffffff at device 0.0 on p ci0 pcib1: at device 1.0 on pci0 pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.P0P1 - AE_NOT_F OUND pci2: on pcib1 drm0: mem 0xfc800000-0xfcffffff,0xfd000000-0xfd003fff,0 xec000000-0xedffffff irq 16 at device 0.0 on pci2 info: [drm] AGP at 0xf0000000 128MB info: [drm] Initialized mga 3.1.0 20021029 on minor 0 fwohci0: port 0xcc00-0xcc7f mem 0xfd900000-0xfd9007ff irq 16 at device 7.0 on pci0 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:e0:18:00:00:35:11:d2 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) atapci0: port 0xdc00-0xdc7f,0xec00-0xec0f, 0xb000-0xb03f mem 0xfda00000-0xfda1ffff,0xfdb00000-0xfdb00fff irq 18 at device 8 .0 on pci0 atapci0: failed: rid 0x20 is memory, requested 4 ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 ata4: channel #2 on atapci0 pci0: at device 9.0 (no driver attached) pci0: at device 9.1 (no driver attached) skc0: <3Com 3C940 Gigabit Ethernet> port 0xb400-0xb4ff mem 0xfdc00000-0xfdc03fff irq 17 at device 10.0 on pci0 skc0: 3Com Gigabit LOM (3C940) sk0: on skc0 sk0: Ethernet address: 00:0c:6e:bd:c3:e5 miibus0: on sk0 e1000phy0: on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto ahc0: port 0xb800-0xb8ff mem 0xfde00000-0x fde00fff irq 17 at device 12.0 on pci0 ahc0: [GIANT-LOCKED] aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs pcib2: at device 14.0 on pci0 pci1: on pcib2 pci1: at device 3.0 (no driver attached) pci1: at device 4.0 (no driver attached) atapci1: port 0xd000-0xd0ff,0xd400-0xd40f,0xd800-0 xd803,0xe000-0xe007,0xe400-0xe403,0xe800-0xe807 irq 20 at device 15.0 on pci0 ata5: channel #0 on atapci1 ata6: channel #1 on atapci1 atapci2: port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f 6,0x1f0-0x1f7 at device 15.1 on pci0 ata0: channel #0 on atapci2 ata1: channel #1 on atapci2 uhci0: port 0xc000-0xc01f irq 21 at device 16.0 on p ci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ugen0: Micro Star International product 0x697a, rev 1.10/5.25, addr 2 umass0: SanDisk ImageMate 8 in 1, rev 2.00/91.39, addr 3 uhci1: port 0xc400-0xc41f irq 21 at device 16.1 on p ci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: at device 16.4 (no driver attached) isab0: at device 17.0 on pci0 isa0: on isab0 pcm0: port 0xc800-0xc8ff irq 22 at device 17.5 on pci0 pcm0: [GIANT-LOCKED] pcm0: acpi_button0: on acpi0 acpi_button1: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi 0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 ppi0: on ppbus0 sio0: configured irq 3 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 port 0x2f8-0x2ff irq 3 on acpi0 sio0: type 16550A sio1: configured irq 4 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1 port 0x3f8-0x3ff irq 4 on acpi0 sio1: type 16550A orm0: at iomem 0xce800-0xcf7ff,0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 2002571040 Hz quality 800 Timecounters tick every 0.976 msec Waiting 5 seconds for SCSI devices to settle cd0 at ahc0 bus 0 target 2 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present da1 at ahc0 bus 0 target 3 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) cd1 at ahc0 bus 0 target 6 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 20.000MB/s transfers (20.000MHz, offset 8) cd1: Attempt to query device size failed: NOT READY, Medium not present - tray c losed da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C) da3 at ahc0 bus 0 target 10 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.000MB/s transfers (20.000MHz, offset 127, 16bit), Tagged Queueing Enable d da3: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) da4 at umass-sim0 bus 0 target 0 lun 0 da4: Removable Direct Access SCSI-0 device da4: 1.000MB/s transfers da4: 122MB (250368 512 byte sectors: 64H 32S/T 122C) da5 at umass-sim0 bus 0 target 0 lun 1 da5: Removable Direct Access SCSI-0 device da5: 1.000MB/s transfers da5: Attempt to query device size failed: NOT READY, Medium not present da2 at ahc0 bus 0 target 4 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da2: 4303MB (8813870 512 byte sectors: 255H 63S/T 548C) da6 at umass-sim0 bus 0 target 0 lun 2 da6: Removable Direct Access SCSI-0 device da6: 1.000MB/s transfers da6: Attempt to query device size failed: NOT READY, Medium not present da7 at umass-sim0 bus 0 target 0 lun 3 da7: Removable Direct Access SCSI-0 device da7: 1.000MB/s transfers da7: Attempt to query device size failed: NOT READY, Medium not present (da5:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 (da5:umass-sim0:0:0:1): CAM Status: SCSI Status Error (da5:umass-sim0:0:0:1): SCSI Status: Check Condition (da5:umass-sim0:0:0:1): NOT READY asc:3a,0 (da5:umass-sim0:0:0:1): Medium not present (da5:umass-sim0:0:0:1): Unretryable error Opened disk da5 -> 6 (da5:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 (da5:umass-sim0:0:0:1): CAM Status: SCSI Status Error (da5:umass-sim0:0:0:1): SCSI Status: Check Condition (da5:umass-sim0:0:0:1): NOT READY asc:3a,0 (da5:umass-sim0:0:0:1): Medium not present (da5:umass-sim0:0:0:1): Unretryable error Opened disk da5 -> 6 (da5:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 (da5:umass-sim0:0:0:1): CAM Status: SCSI Status Error (da5:umass-sim0:0:0:1): SCSI Status: Check Condition (da5:umass-sim0:0:0:1): NOT READY asc:3a,0 (da5:umass-sim0:0:0:1): Medium not present (da5:umass-sim0:0:0:1): Unretryable error Opened disk da5 -> 6 (da6:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 (da6:umass-sim0:0:0:2): CAM Status: SCSI Status Error (da6:umass-sim0:0:0:2): SCSI Status: Check Condition (da6:umass-sim0:0:0:2): NOT READY asc:3a,0 (da6:umass-sim0:0:0:2): Medium not present (da6:umass-sim0:0:0:2): Unretryable error Opened disk da6 -> 6 (da6:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 (da6:umass-sim0:0:0:2): CAM Status: SCSI Status Error (da6:umass-sim0:0:0:2): SCSI Status: Check Condition (da6:umass-sim0:0:0:2): NOT READY asc:3a,0 (da6:umass-sim0:0:0:2): Medium not present (da6:umass-sim0:0:0:2): Unretryable error Opened disk da6 -> 6 (da6:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 (da6:umass-sim0:0:0:2): CAM Status: SCSI Status Error (da6:umass-sim0:0:0:2): SCSI Status: Check Condition (da6:umass-sim0:0:0:2): NOT READY asc:3a,0 (da6:umass-sim0:0:0:2): Medium not present (da6:umass-sim0:0:0:2): Unretryable error Opened disk da6 -> 6 (da7:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0 (da7:umass-sim0:0:0:3): CAM Status: SCSI Status Error (da7:umass-sim0:0:0:3): SCSI Status: Check Condition (da7:umass-sim0:0:0:3): NOT READY asc:3a,0 (da7:umass-sim0:0:0:3): Medium not present (da7:umass-sim0:0:0:3): Unretryable error Opened disk da7 -> 6 (da7:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0 (da7:umass-sim0:0:0:3): CAM Status: SCSI Status Error (da7:umass-sim0:0:0:3): SCSI Status: Check Condition (da7:umass-sim0:0:0:3): NOT READY asc:3a,0 (da7:umass-sim0:0:0:3): Medium not present (da7:umass-sim0:0:0:3): Unretryable error Opened disk da7 -> 6 (da7:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0 (da7:umass-sim0:0:0:3): CAM Status: SCSI Status Error (da7:umass-sim0:0:0:3): SCSI Status: Check Condition (da7:umass-sim0:0:0:3): NOT READY asc:3a,0 (da7:umass-sim0:0:0:3): Medium not present (da7:umass-sim0:0:0:3): Unretryable error Opened disk da7 -> 6 (yeah, the umass stuff is a bit broken, but there's a patch I just haven't tested yet). -- Yours truly, Shaun D. Jurrens shaun@shamz.net From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 25 18:12:36 2004 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 353D816A4CE for ; Sat, 25 Sep 2004 18:12:36 +0000 (GMT) Received: from sophia3.e-shell.net (sophia3.e-shell.net [64.246.46.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 097C043D39 for ; Sat, 25 Sep 2004 18:12:36 +0000 (GMT) (envelope-from loox@e-shell.net) Received: from customer-201-133-104-82.prod-infinitum.com.mx (unknown [201.133.104.82]) by sophia3.e-shell.net (Postfix) with ESMTP id 161CE656803 for ; Sat, 25 Sep 2004 13:12:26 -0500 (CDT) From: Axel Gonzalez Organization: e-shell.net Inc To: freebsd-amd64@freebsd.org Date: Sat, 25 Sep 2004 13:12:38 -0500 User-Agent: KMail/1.7 References: <20040925114724.GH90420@atreides.freenix.no> In-Reply-To: <20040925114724.GH90420@atreides.freenix.no> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200409251312.38515.loox@e-shell.net> Subject: Re: A number of show-stopper bugs... 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: Sat, 25 Sep 2004 18:12:36 -0000 I'm running -CURRENT, so not sure if this applies to 5.3 I noticed some problems with snd_via8233 with prior kernels (~ < 17 sep, last I built with problems was around 10 sep) Under heavy disk activity (cvsup, buildworld) esdplay almost completly crashed the system.. x was dead (mouse didn't move), most services were dead (ssh ftp natd), but it replied to pings. With no disk activy, I was able to listen to a stream for hours + kde sounds + edsplay with no problems . With last kernel I built (17 sep) system seems to be ok, and haven't been able to reproduce the problem again. I think there is some other minor problem with esdplay, but haven't been able to trace it, or even confirm it. Building a new kernel now, and try to find the problem (or see if it even exists). I' m also using NETGRAPH modules (dinamically loaded) for pppoe with no problems whatsoever for almost a month now. Im using: FreeBSD moonlight.e-shell.net 6.0-CURRENT FreeBSD 6.0-CURRENT #1: Fri Sep 17 23:38:49 CDT 2004 root@moonlight.e-shell.net:/usr/obj/usr/src/sys/LXAMD64 amd64 ng modules: 6 4 0xffffffff96343000 d5c2 netgraph.ko 7 2 0xffffffff96351000 1add ng_ether.ko 8 1 0xffffffff96353000 43f9 ng_pppoe.ko 9 1 0xffffffff96358000 24ed ng_socket.ko On Saturday 25 September 2004 06:47, Shaun Jurrens wrote: > Hei guys, > > This is just an informal heads up at the moment, perhaps just to either get > a few hits with the clue bat or to inform about some nasty kernel bugs. > > I have run across a number of things that produce unbootable or unstable > kernels: > > 1) Loading the sound and snd_via8233 modules after boot crashed my > machine within 30 minutes. I first received a ca. 50Hz white noise sound > before freezing the box and subsequent reboot. I was using mpg123 with > a 1024kb buffer, downloading via scp and running Mozilla. No crashdump > available yet... With both compiled in the kernel, things seem to be > stable. > > 2) Adding NETGRAPH modules to the kernel config produces unbootable kernels > in almost any configuration (trying to get the bluetooth stuff working). > Using the kernel modules produced no working results. No crashdump yet... >