From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 12 03:08:07 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 6716916A4CE; Sun, 12 Sep 2004 03:08:07 +0000 (GMT) Received: from satie.private.org (YahooBB219196184005.bbtec.net [219.196.184.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E85F43D41; Sun, 12 Sep 2004 03:08:06 +0000 (GMT) (envelope-from chat95@mac.com) Received: from localhost (localhost [127.0.0.1]) by satie.private.org (8.12.10/8.12.10) with ESMTP id i8C383Cm001275; Sun, 12 Sep 2004 12:08:04 +0900 (JST) (envelope-from chat95@mac.com) Date: Sun, 12 Sep 2004 12:08:03 +0900 (JST) Message-Id: <20040912.120803.607953196.chat95@mac.com> To: freebsd-amd64@FreeBSD.org, developers@FreeBSD.org From: NAKATA Maho Organization: private X-Mailer: Mew version 3.3 on XEmacs 21.4.14 (Reasonable Discussion) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: KSE and SMP problem in FreeBSD/amd64 5.3BETA3, namely KSE dosen't make use of SMP. 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, 12 Sep 2004 03:08:07 -0000 Dear amd64 freaks, I noticed that there seems to be a bug in KSE with SMP configuration. Here, I describe my problem in detail. the math/atlas port utilize SMP by threading. namely, if you have 2 processors you can gain the nearly double performance so KSE is the key technology for SMP. However, for amd64, KSE doesn't utilize second CPU at all. My machine is: Tyan S2885 Opteron 1.6GHz x 2 2G bytes of memory I confirmed that: o FreeBSD/amd64 5.2.1-RELEASE with KSE doesn't work at all, dumps core or memory fault, while without KSE works well but without performance gain (using libmap.conf, and this is not shown here). o FreeBSD/amd64 5.3-BEAT3 with KSE works at least, however, doesn't utilize SMP. o FreeBSD/i386 5.2.1-RELEASE, and 5.3-BEAT3 works well. How to repreat: (it took huge hours to build math/atlas, so I put work dir at) CVSup your ports tree, please use: # $FreeBSD: ports/math/atlas/Makefile,v 1.27 2004/09/02 00:25:45 maho Exp $ 0a. prepare opteron SMP machine, and install FreeBSD/amd64 5.3-BETA3. 1a. cd /usr/ports/math/atlas 2a. make 3a. wait for long time 4a. cd /usr/ports/math/atlas/work/ATLAS/bin/THREADED 5a. make xdlutst (it took only seconds) 6a. make xdlutst_pt (it took only seconds) 7a. type ./xdlutst -N 1000 2000 200 (this doesn't utilize SMP and KSE) NREPS Major M N lda NPVTS TIME MFLOP RESID ===== ===== ===== ===== ===== ===== ======== ======== ======== 0 Col 1000 1000 1000 995 0.301 2210.755 3.821e-02 0 Col 1200 1200 1200 1194 0.504 2282.569 3.793e-02 0 Col 1400 1400 1400 1395 0.794 2303.707 2.843e-02 0 Col 1600 1600 1600 1595 1.156 2360.557 2.893e-02 0 Col 1800 1800 1800 1793 1.637 2374.130 2.803e-02 0 Col 2000 2000 2000 1990 2.192 2431.838 2.744e-02 6 cases ran, 6 cases passed 8a. type ./xdlutst_pt -N 2000 3000 200 ./xdlutst_pt -N 2000 3000 200 NREPS Major M N lda NPVTS TIME MFLOP RESID ===== ===== ===== ===== ===== ===== ======== ======== ======== 0 Col 2000 2000 2000 1990 2.286 2332.527 2.744e-02 0 Col 2200 2200 2200 2194 2.764 2567.795 2.639e-02 0 Col 2400 2400 2400 2394 3.766 2446.449 2.721e-02 0 Col 2600 2600 2600 2593 4.722 2480.761 2.472e-02 0 Col 2800 2800 2800 2795 5.855 2499.038 2.441e-02 0 Col 3000 3000 3000 2992 7.302 2464.553 2.442e-02 6 cases ran, 6 cases passed Please see the MFLOP column. This indicates the FLOPS of the calculation. Opteron 1.6G's performance is 2.4GFlops for LU decomposition. and as you can see no perfomance gain :( typical output of top is like that: PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 716 root 134 0 185M 179M CPU0 0 1:05 21.09% 21.09% xdlutst_pt 716 root 134 0 185M 179M RUN 0 1:05 19.53% 19.53% xdlutst_pt 716 root 20 0 185M 179M kserel 1 1:05 0.00% 0.00% xdlutst_pt 716 root 20 0 185M 179M ksesig 1 1:05 0.00% 0.00% xdlutst_pt 716 root 20 0 185M 179M kserel 0 1:05 0.00% 0.00% xdlutst_pt two threads of xdlutst_pt are always running on *ONLY CPU0 or CPU1* -------------------------------------------------------------------- Next, I have tried i386 version 0i. prepare opteron SMP machine same as above, and install FreeBSD/i386 5.3-BETA3. CVSup your ports tree. 1i. cd /usr/ports/math/atlas 2i. make 3i. wait for long time 4i. cd /usr/ports/math/atlas/work/ATLAS/bin/THREADED 5i. make xdlutst (it took only seconds) 6i. make xdlutst_pt (it took only seconds) 7i. type ./xdlutst -N 1000 2000 200 (this doesn't utilize SMP and KSE) ./xdlutst -N 1000 2000 200 NREPS Major M N lda NPVTS TIME MFLOP RESID ===== ===== ===== ===== ===== ===== ======== ======== ======== 0 Col 1000 1000 1000 995 0.307 2170.617 3.437e-02 0 Col 1200 1200 1200 1194 0.522 2204.335 3.482e-02 0 Col 1400 1400 1400 1395 0.799 2286.888 4.150e-02 0 Col 1600 1600 1600 1595 1.164 2345.104 3.598e-02 0 Col 1800 1800 1800 1793 1.616 2405.542 3.601e-02 0 Col 2000 2000 2000 1990 2.218 2403.157 3.436e-02 6 cases ran, 6 cases passed 8i. type ./xdlutst_pt -N 3000 4000 200 (this utilize KSE so that make full use of SMP) ./xdlutst_pt -N 3000 4000 200 NREPS Major M N lda NPVTS TIME MFLOP RESID ===== ===== ===== ===== ===== ===== ======== ======== ======== 0 Col 3000 3000 3000 2992 7.157 2514.351 3.650e-02 0 Col 3200 3200 3200 3186 5.127 4259.986 3.207e-02 0 Col 3400 3400 3400 3392 5.867 4465.006 3.528e-02 0 Col 3600 3600 3600 3589 6.791 4579.468 3.519e-02 0 Col 3800 3800 3800 3791 8.510 4297.730 3.285e-02 0 Col 4000 4000 4000 3995 9.207 4633.234 3.218e-02 6 cases ran, 6 cases passed yes, there are perfomance gain by utilizing SMP. typical output of top seems like PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 714 root 139 0 301M 300M CPU1 1 2:16 66.41% 66.41% xdlutst_pt 714 root 139 0 301M 300M RUN 0 2:16 66.41% 66.41% xdlutst_pt 714 root 20 0 301M 300M kserel 1 2:16 0.00% 0.00% xdlutst_pt 714 root 20 0 301M 300M kserel 0 2:16 0.00% 0.00% xdlutst_pt 714 root 20 0 301M 300M ksesig 0 2:16 0.00% 0.00% xdlutst_pt Summary: Difference between 8a and 8i are: o there are no perfomance gain in 8a whereas 8i gains nearly double. o the result of top indicates that by KSE of amd64, two threads are produced correctly, however scheduling is somwhat odd, so that two threads runs at the same processor, apparently threads are spread over different processors, though. You can try easily, work directory of these two ports are available: http://people.freebsd.org/~maho/atlas/atlas-work-opteron_dual-amd64.tar.bz http://people.freebsd.org/~maho/atlas/atlas-work-opteron_dual-i386.tar.bz MD5 (atlas-work-opteron_dual-amd64.tar.bz) = 9d9d7e8b00b34a783b7d2172bc404e23 MD5 (atlas-work-opteron_dual-i386.tar.bz) = 8076a753c7b3edaea7bd446c6473f120 Does anybody can fix it? Best regards, --nakata maho From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 12 04:09: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 7DF2516A4CF; Sun, 12 Sep 2004 04:09:48 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id E73E443D49; Sun, 12 Sep 2004 04:09:47 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id i8C49kmm003052; Sun, 12 Sep 2004 00:09:46 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.12.11/8.12.11) with ESMTP id i8C49k5d050971; Sun, 12 Sep 2004 00:09:46 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id D32CD7303F; Sun, 12 Sep 2004 00:09:45 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040912040945.D32CD7303F@freebsd-current.sentex.ca> Date: Sun, 12 Sep 2004 00:09:45 -0400 (EDT) Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Sep 2004 04:09:48 -0000 TB --- 2004-09-12 03:10:43 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-09-12 03:10:43 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-09-12 03:10:43 - checking out the source tree TB --- 2004-09-12 03:10:43 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2004-09-12 03:10:43 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-09-12 03:16:09 - building world (CFLAGS=-O2 -pipe) TB --- 2004-09-12 03:16:09 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-09-12 03:16:09 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -o mount mount.o mount_ufs.o getmntopts.o vfslist.o gzip -cn /tinderbox/CURRENT/amd64/amd64/src/sbin/mount/mount.8 > mount.8.gz ===> sbin/mount_autofs (all) cc -O2 -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /tinderbox/CURRENT/amd64/amd64/src/sbin/mount_autofs/mount_autofs.c /tinderbox/CURRENT/amd64/amd64/src/sbin/mount_autofs/mount_autofs.c: In function `ioset': /tinderbox/CURRENT/amd64/amd64/src/sbin/mount_autofs/mount_autofs.c:60: warning: implicit declaration of function `strlen' /tinderbox/CURRENT/amd64/amd64/src/sbin/mount_autofs/mount_autofs.c: In function `main': /tinderbox/CURRENT/amd64/amd64/src/sbin/mount_autofs/mount_autofs.c:80: warning: unused variable `i' *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sbin/mount_autofs. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sbin. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-09-12 04:09:45 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-09-12 04:09:45 - ERROR: failed to build world TB --- 2004-09-12 04:09:45 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 12 06:13:21 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 8F3DA16A4CE; Sun, 12 Sep 2004 06:13:21 +0000 (GMT) Received: from pimout2-ext.prodigy.net (pimout2-ext.prodigy.net [207.115.63.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7E8B43D31; Sun, 12 Sep 2004 06:13:20 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (adsl-68-123-121-27.dsl.snfc21.pacbell.net [68.123.121.27])i8C6DGvd225228; Sun, 12 Sep 2004 02:13:17 -0400 Message-ID: <4143E8FC.7000308@elischer.org> Date: Sat, 11 Sep 2004 23:13:16 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4b) Gecko/20030524 X-Accept-Language: en, hu MIME-Version: 1.0 To: NAKATA Maho References: <20040912.120803.607953196.chat95@mac.com> In-Reply-To: <20040912.120803.607953196.chat95@mac.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@FreeBSD.org cc: freebsd-amd64@FreeBSD.org Subject: Re: KSE and SMP problem in FreeBSD/amd64 5.3BETA3, namely KSEdosen't make use of SMP. 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, 12 Sep 2004 06:13:21 -0000 Firstly ,I am very happy to see your mail. We need all bug repors.. even bad ones :-) I have been working on trying to fix problems in this sort of thing in the last few weeks for 5.3 but will be able to examine your work more closely in a few days. I just want you to know that your email will be worked on, even if you do not hear anything immediatly. more notes below.. NAKATA Maho wrote: > Dear amd64 freaks, I noticed that there seems to be a bug > in KSE with SMP configuration. > > Here, I describe my problem in detail. > > the math/atlas port utilize SMP by threading. namely, > if you have 2 processors you can gain the nearly double performance > so KSE is the key technology for SMP. However, for amd64, KSE doesn't > utilize second CPU at all. > > My machine is: > Tyan S2885 > Opteron 1.6GHz x 2 > 2G bytes of memory > > I confirmed that: > o FreeBSD/amd64 5.2.1-RELEASE with KSE doesn't work at all, > dumps core or memory fault, while without KSE works well but > without performance gain (using libmap.conf, and this is not shown here). this is expected. > > o FreeBSD/amd64 5.3-BEAT3 with KSE works at least, however, > doesn't utilize SMP. I will try examine this together with Peter and Dan over the next few days.. Please show me the output in 5.3 of sysctl kern.threads and kern.sched also there will be improvements in beta4 I hope which scheduler? show ldd output for your program please. > o FreeBSD/i386 5.2.1-RELEASE, and 5.3-BEAT3 works well. > > How to repreat: > (it took huge hours to build math/atlas, so I put work dir at) at? > > CVSup your ports tree, please use: > # $FreeBSD: ports/math/atlas/Makefile,v 1.27 2004/09/02 00:25:45 maho Exp $ > > 0a. prepare opteron SMP machine, and install FreeBSD/amd64 5.3-BETA3. > 1a. cd /usr/ports/math/atlas > 2a. make > 3a. wait for long time > 4a. cd /usr/ports/math/atlas/work/ATLAS/bin/THREADED > 5a. make xdlutst (it took only seconds) > 6a. make xdlutst_pt (it took only seconds) > 7a. type ./xdlutst -N 1000 2000 200 (this doesn't utilize SMP and KSE) > NREPS Major M N lda NPVTS TIME MFLOP RESID > ===== ===== ===== ===== ===== ===== ======== ======== ======== > 0 Col 1000 1000 1000 995 0.301 2210.755 3.821e-02 > 0 Col 1200 1200 1200 1194 0.504 2282.569 3.793e-02 > 0 Col 1400 1400 1400 1395 0.794 2303.707 2.843e-02 > 0 Col 1600 1600 1600 1595 1.156 2360.557 2.893e-02 > 0 Col 1800 1800 1800 1793 1.637 2374.130 2.803e-02 > 0 Col 2000 2000 2000 1990 2.192 2431.838 2.744e-02 > > 6 cases ran, 6 cases passed > > > 8a. type ./xdlutst_pt -N 2000 3000 200 > ./xdlutst_pt -N 2000 3000 200 > NREPS Major M N lda NPVTS TIME MFLOP RESID > ===== ===== ===== ===== ===== ===== ======== ======== ======== > 0 Col 2000 2000 2000 1990 2.286 2332.527 2.744e-02 > 0 Col 2200 2200 2200 2194 2.764 2567.795 2.639e-02 > 0 Col 2400 2400 2400 2394 3.766 2446.449 2.721e-02 > 0 Col 2600 2600 2600 2593 4.722 2480.761 2.472e-02 > 0 Col 2800 2800 2800 2795 5.855 2499.038 2.441e-02 > 0 Col 3000 3000 3000 2992 7.302 2464.553 2.442e-02 > > 6 cases ran, 6 cases passed > > Please see the MFLOP column. This indicates the FLOPS of the calculation. > Opteron 1.6G's performance is 2.4GFlops for LU decomposition. > and as you can see no perfomance gain :( > > typical output of top is like that: > > PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND > 716 root 134 0 185M 179M CPU0 0 1:05 21.09% 21.09% xdlutst_pt > 716 root 134 0 185M 179M RUN 0 1:05 19.53% 19.53% xdlutst_pt > 716 root 20 0 185M 179M kserel 1 1:05 0.00% 0.00% xdlutst_pt > 716 root 20 0 185M 179M ksesig 1 1:05 0.00% 0.00% xdlutst_pt > 716 root 20 0 185M 179M kserel 0 1:05 0.00% 0.00% xdlutst_pt > > two threads of xdlutst_pt are always running on *ONLY CPU0 or CPU1* > -------------------------------------------------------------------- > Next, I have tried i386 version > > 0i. prepare opteron SMP machine same as above, and install FreeBSD/i386 > 5.3-BETA3. > CVSup your ports tree. > > 1i. cd /usr/ports/math/atlas > 2i. make > 3i. wait for long time > 4i. cd /usr/ports/math/atlas/work/ATLAS/bin/THREADED > 5i. make xdlutst (it took only seconds) > 6i. make xdlutst_pt (it took only seconds) > 7i. type ./xdlutst -N 1000 2000 200 (this doesn't utilize SMP and KSE) > ./xdlutst -N 1000 2000 200 > NREPS Major M N lda NPVTS TIME MFLOP RESID > ===== ===== ===== ===== ===== ===== ======== ======== ======== > 0 Col 1000 1000 1000 995 0.307 2170.617 3.437e-02 > 0 Col 1200 1200 1200 1194 0.522 2204.335 3.482e-02 > 0 Col 1400 1400 1400 1395 0.799 2286.888 4.150e-02 > 0 Col 1600 1600 1600 1595 1.164 2345.104 3.598e-02 > 0 Col 1800 1800 1800 1793 1.616 2405.542 3.601e-02 > 0 Col 2000 2000 2000 1990 2.218 2403.157 3.436e-02 > > 6 cases ran, 6 cases passed > > 8i. type ./xdlutst_pt -N 3000 4000 200 (this utilize KSE so that make > full use of SMP) > ./xdlutst_pt -N 3000 4000 200 > NREPS Major M N lda NPVTS TIME MFLOP RESID > ===== ===== ===== ===== ===== ===== ======== ======== ======== > 0 Col 3000 3000 3000 2992 7.157 2514.351 3.650e-02 > 0 Col 3200 3200 3200 3186 5.127 4259.986 3.207e-02 > 0 Col 3400 3400 3400 3392 5.867 4465.006 3.528e-02 > 0 Col 3600 3600 3600 3589 6.791 4579.468 3.519e-02 > 0 Col 3800 3800 3800 3791 8.510 4297.730 3.285e-02 > 0 Col 4000 4000 4000 3995 9.207 4633.234 3.218e-02 > > 6 cases ran, 6 cases passed > > yes, there are perfomance gain by utilizing SMP. > > typical output of top seems like > > PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND > 714 root 139 0 301M 300M CPU1 1 2:16 66.41% 66.41% xdlutst_pt > 714 root 139 0 301M 300M RUN 0 2:16 66.41% 66.41% xdlutst_pt > 714 root 20 0 301M 300M kserel 1 2:16 0.00% 0.00% xdlutst_pt > 714 root 20 0 301M 300M kserel 0 2:16 0.00% 0.00% xdlutst_pt > 714 root 20 0 301M 300M ksesig 0 2:16 0.00% 0.00% xdlutst_pt > > Summary: > Difference between 8a and 8i are: > o there are no perfomance gain in 8a whereas 8i gains nearly double. > o the result of top indicates that by KSE of amd64, two threads are produced > correctly, however scheduling is somwhat odd, so that two threads runs > at the same processor, apparently threads are spread over different > processors, though. > > You can try easily, work directory of these two ports are available: > http://people.freebsd.org/~maho/atlas/atlas-work-opteron_dual-amd64.tar.bz > http://people.freebsd.org/~maho/atlas/atlas-work-opteron_dual-i386.tar.bz > > MD5 (atlas-work-opteron_dual-amd64.tar.bz) = 9d9d7e8b00b34a783b7d2172bc404e23 > MD5 (atlas-work-opteron_dual-i386.tar.bz) = 8076a753c7b3edaea7bd446c6473f120 > > Does anybody can fix it? yes we will try. > > Best regards, > --nakata maho > From owner-freebsd-amd64@FreeBSD.ORG Sun Sep 12 17:40:29 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 5114A16A4DF for ; Sun, 12 Sep 2004 17:40:29 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 295AE43D2D for ; Sun, 12 Sep 2004 17:40:29 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i8CHeTaB009225 for ; Sun, 12 Sep 2004 17:40:29 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i8CHeT7A009224; Sun, 12 Sep 2004 17:40:29 GMT (envelope-from gnats) Resent-Date: Sun, 12 Sep 2004 17:40:29 GMT Resent-Message-Id: <200409121740.i8CHeT7A009224@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Pete French Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB6A916A4CE for ; Sun, 12 Sep 2004 17:39:03 +0000 (GMT) Received: from smtp-out1.blueyonder.co.uk (smtp-out1.blueyonder.co.uk [195.188.213.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDD1943D2D for ; Sun, 12 Sep 2004 17:39:02 +0000 (GMT) (envelope-from pete@twisted.org.uk) Received: from skerry.twisted.org.uk ([82.35.80.30]) by smtp-out1.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.6713); Sun, 12 Sep 2004 18:39:26 +0100 Received: from [192.168.4.2] (helo=frenic.drayhouse) by skerry.twisted.org.uk with esmtp (Exim 4.42 (FreeBSD)) id 1C6YJZ-000Juh-C6 for FreeBSD-gnats-submit@freebsd.org; Sun, 12 Sep 2004 18:39:01 +0100 Received: from pete by frenic.drayhouse with local (Exim 4.42 (FreeBSD)) id 1C6YJZ-0000H0-59 for FreeBSD-gnats-submit@freebsd.org; Sun, 12 Sep 2004 18:39:01 +0100 Message-Id: Date: Sun, 12 Sep 2004 18:39:01 +0100 From: Pete French To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: amd64/71674: static libraries cannot be linked when building shared libraries X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Pete French List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Sep 2004 17:40:29 -0000 >Number: 71674 >Category: amd64 >Synopsis: static libraries cannot be linked when building shared libraries >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Sep 12 17:40:28 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Pete French >Release: FreeBSD 5.3-BETA4 amd64 >Organization: >Environment: System: FreeBSD frenic.drayhouse 5.3-BETA4 FreeBSD 5.3-BETA4 #0: Sun Sep 12 18:04:01 BST 2004 pete@frenic.drayhouse:/usr/obj/usr/src/sys/FRENIC amd64 >Description: The supplied /usr/lib/libobjc.a has been compiled in such a way that trying to link when making a shared library gives the following error: /usr/bin/ld: /usr/lib/libobjc.a(Protocol.o): relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC /usr/lib/libobjc.a: could not read symbols: Bad value This did not happen on pre BETA versions. I am unsure as to whether the linker has changed or what. This may apply to all the static libraries in /usr/lib though! I have tried with libz.a and libufs.a with the same error. >How-To-Repeat: In this instance I was trying to build the GNUstep base libraries. But trying to make a very simple shared library, linking against static libraries in /usr/lib, will show it up. >Fix: Preseumably fix buildworld so that static libraries are compiled with -fPIC ? This also applies to static libraries built from ports. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 13 11:02:11 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 860BE16A4CE for ; Mon, 13 Sep 2004 11:02:11 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A81C43D1D for ; Mon, 13 Sep 2004 11:02:11 +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 i8DB2Bcr048724 for ; Mon, 13 Sep 2004 11:02:11 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i8DB2A4I048717 for freebsd-amd64@freebsd.org; Mon, 13 Sep 2004 11:02:10 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 13 Sep 2004 11:02:10 GMT Message-Id: <200409131102.i8DB2A4I048717@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Sep 2004 11:02:11 -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 7 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 13 11:55: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 F08D416A4CE for ; Mon, 13 Sep 2004 11:55:24 +0000 (GMT) Received: from ibhunu.nefkens.nu (gr-ztst-52e4.mxs.adsl.euronet.nl [212.129.210.228]) by mx1.FreeBSD.org (Postfix) with ESMTP id 951D543D53 for ; Mon, 13 Sep 2004 11:55:20 +0000 (GMT) (envelope-from pjnefkens@nefkensadvies.nl) Received: from localhost (localhost.intern.nefkens.net [127.0.0.1]) by ibhunu.nefkens.nu (Postfix) with ESMTP id E4E1D21 for ; Mon, 13 Sep 2004 14:04:59 +0200 (CEST) Received: from ibhunu.nefkens.nu ([127.0.0.1])port 10024) with ESMTP id 31952-07 for ; Mon, 13 Sep 2004 14:04:58 +0200 (CEST) Received: from [10.0.3.95] (gr-ztst-52e5.mxs.adsl.euronet.nl [212.129.210.229]) by ibhunu.nefkens.nu (Postfix) with ESMTP id C2FB214 for ; Mon, 13 Sep 2004 14:04:58 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-amd64@FreeBSD.org From: P-J Nefkens Date: Mon, 13 Sep 2004 13:55:21 +0200 X-Mailer: Apple Mail (2.619) Subject: Newbie question: 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: Mon, 13 Sep 2004 11:55:25 -0000 Hello, I've been working on getting my amd64 system ready to replace the current system. For some applications I need to recompile the kernel. If I do a complete upgrade with the standard-cvsup file, I end up with a 6.0 FreeBSD system. Is this system reasonably stable, or should I remain with the 5.2.1 release? Thanks in advance, Regards Pieter-Jan Nefkens From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 13 12:18:19 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 C80D916A4CE for ; Mon, 13 Sep 2004 12:18:19 +0000 (GMT) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30E4843D54 for ; Mon, 13 Sep 2004 12:18:19 +0000 (GMT) (envelope-from groot@kde.org) Received: from odin.cs.kun.nl [131.174.33.33] (helo=[127.0.0.1]) by pandora.cs.kun.nl (8.12.10/4.16) with ESMTP id i8DCIHdE012723; Mon, 13 Sep 2004 14:18:17 +0200 (MEST) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Mon, 13 Sep 2004 14:18:17 +0200 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200409131418.17212.groot@kde.org> Subject: Re: Newbie question: 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: Mon, 13 Sep 2004 12:18:19 -0000 On Monday 13 September 2004 13:55, P-J Nefkens wrote: > I've been working on getting my amd64 system ready to replace the > current system. For some applications I need to recompile the kernel. > If I do a complete upgrade with the standard-cvsup file, I end up with > a 6.0 FreeBSD system. Is this system reasonably stable, or should I > remain with the 5.2.1 release? 5.2.1 is pretty old by now, and there have been considerable improvements - modules, etc. - since. It's probably best to follow RELENG_5 right now, although there are rumors [1] that updating _right now_ might be a bad idea (something to do with the scheduler?). *default release=cvs tag=RELENG_5 is, I believe, the right supfile syntax. [1] Dammit, I know I ought to read -current as well, but there's only so many high-volume lists a guy can plow through. -- As of September 1st, 2004, the University of Nijmegen will _still_ be the University of Nijmegen, but with a different nonsensical adjective in front. Reach me at groot@kde.org instead. GPG FEA2 A3FE From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 14 03:39: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 D541516A4E9 for ; Tue, 14 Sep 2004 03:39:00 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD26D43D55 for ; Tue, 14 Sep 2004 03:39:00 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id AEB4B72DF4; Mon, 13 Sep 2004 20:39:00 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id ACF1872DF2; Mon, 13 Sep 2004 20:39:00 -0700 (PDT) Date: Mon, 13 Sep 2004 20:39:00 -0700 (PDT) From: Doug White To: NAKATA Maho In-Reply-To: <20040912.120803.607953196.chat95@mac.com> Message-ID: <20040913203823.R34536@carver.gumbysoft.com> References: <20040912.120803.607953196.chat95@mac.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@FreeBSD.org Subject: Re: KSE and SMP problem in FreeBSD/amd64 5.3BETA3, namely KSEdosen't make use of SMP. 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, 14 Sep 2004 03:39:02 -0000 (dropping off private list) On Sun, 12 Sep 2004, NAKATA Maho wrote: > Dear amd64 freaks, I noticed that there seems to be a bug > in KSE with SMP configuration. Were you using SCHED_4BSD or SCHED_ULE? -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 14 12:22:55 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 0B58216A4D1 for ; Tue, 14 Sep 2004 12:22:55 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id C7F8043D5C for ; Tue, 14 Sep 2004 12:22:53 +0000 (GMT) (envelope-from Gregor.Bittel@GMX.de) Received: (qmail 4763 invoked by uid 65534); 14 Sep 2004 12:22:52 -0000 Received: from pD9FA8EDF.dip.t-dialin.net (EHLO 2x_Xeon.BI) (217.250.142.223) by mail.gmx.net (mp005) with SMTP; 14 Sep 2004 14:22:52 +0200 X-Authenticated: #3119465 From: Gregor Bittel To: freebsd-smp@freebsd.org, freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Date: Tue, 14 Sep 2004 14:23:58 +0200 User-Agent: KMail/1.5 MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200409141409.12715.Gregor.Bittel@GMX.de> Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org cc: freebsd-ia64@freebsd.org Subject: Multiprocessing-mainboards. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2004 12:22:55 -0000 Hello. I'd like to remind you of my small project[1] -- a list[1] of SMP-boards running FreeBSD (in real SMP-mode with two or more physical processors - sorted by CPU-socket/slot). Everyone is invited to add his known-working FreeBSD-SMP-board to this list, especially the older ones - they are very hard to find (and I don't want to buy them all on online-auctions - my room and money are limited ;) Only real MP boards will be listed, that is, only boards with two or more physical processors installed -- running a FreeBSD SMP kernel -- and which can be identified by a specific name or number. For example, the "Tyan Tiger i7505 S2668AN" and the "Tyan Tiger i7505 S2668ANR" are different boards and will be listed as different, each with an own entry). To add a mainboard, please submit (in addition to the exact brand and label) the output of the dmesg(8) and mptable(1) commands, and optionally the "pciconf -l -v" output as well. The BIOS revision would be nice, too. Please take care to remove the host and/or domain name from the dmesg(8) output (only if you don't want it should be public). Any known caveats or remarks that may be helpful to other users are also most welcome! Currently 151 SMP-boards are listed, and my local list contains 633 different boards at the moment (including the 151 on the website). Some words about my person: I started my first FreeBSD-Installation in July 1999 (I ordered a CD-Set from a German Distributor), and since this time I am infected with the FreeBSD-Virus ;) And not to forget: I would like to say "Thank you" - for my favourite Operating System and for reading this mail. best regards, -Gregor. -- Gregor.Bittel@GMX.de [1]= http://www.bnv-bamberg.de/home/ba3294/smp/index.htm From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 14 15:04:14 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 C7DBA16A4CE for ; Tue, 14 Sep 2004 15:04:14 +0000 (GMT) Received: from ares.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88EF843D41 for ; Tue, 14 Sep 2004 15:04:13 +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 i8EF4BNf078637 for ; Tue, 14 Sep 2004 17:04:11 +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 i8EF4JKi007309 for ; Tue, 14 Sep 2004 17:04:19 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.1/8.13.1/Submit) id i8EF4JdP007308 for freebsd-amd64@freebsd.org; Tue, 14 Sep 2004 17:04:19 +0200 (CEST) (envelope-from ftigeot) Date: Tue, 14 Sep 2004 17:04:19 +0200 From: Francois Tigeot To: freebsd-amd64@freebsd.org Message-ID: <20040914150419.GA7191@aoi.wolfpond.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: 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, 14 Sep 2004 15:04:14 -0000 I'm running 5.3-BETA4 and I can't find even though bios(9) exists. It seems bios.h is only present on the i386 and alpha architectures. Is this normal on amd64 ? If yes, I would appreciate if someone could point me to an alternative to bios_sigsearch() -- Francois Tigeot From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 14 22:43: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 D958116A4CE for ; Tue, 14 Sep 2004 22:43:13 +0000 (GMT) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3DBD43D31 for ; Tue, 14 Sep 2004 22:43:13 +0000 (GMT) (envelope-from peter@yahoo-inc.com) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id 9C88D8803; Tue, 14 Sep 2004 15:43:13 -0700 (PDT) From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Tue, 14 Sep 2004 15:43:13 -0700 User-Agent: KMail/1.6.2 References: <20040914150419.GA7191@aoi.wolfpond.org> In-Reply-To: <20040914150419.GA7191@aoi.wolfpond.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200409141543.13318.peter@wemm.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, 14 Sep 2004 22:43:14 -0000 On Tuesday 14 September 2004 08:04 am, Francois Tigeot wrote: > I'm running 5.3-BETA4 and I can't find even > though bios(9) exists. > It seems bios.h is only present on the i386 and alpha architectures. > > Is this normal on amd64 ? If yes, I would appreciate if someone could > point me to an alternative to bios_sigsearch() We dont even have bios_sigsearch() - all the consumers in the kernel were related to vm86()/bios16()/bios32() calls, which are impossible in our kernel. What do you need it for? It might be ok to revive a subset of it, but it would be useful to know what that file is being used for first, so we know which subsets are needed. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Tue Sep 14 22:56: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 5127816A4CE for ; Tue, 14 Sep 2004 22:56:48 +0000 (GMT) Received: from web12821.mail.yahoo.com (web12821.mail.yahoo.com [216.136.174.202]) by mx1.FreeBSD.org (Postfix) with SMTP id 2577843D49 for ; Tue, 14 Sep 2004 22:56:48 +0000 (GMT) (envelope-from neshort@yahoo.com) Message-ID: <20040914225648.76987.qmail@web12821.mail.yahoo.com> Received: from [208.240.243.170] by web12821.mail.yahoo.com via HTTP; Tue, 14 Sep 2004 15:56:48 PDT Date: Tue, 14 Sep 2004 15:56:48 -0700 (PDT) From: Neil Short To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: RE: Current problem reports assigned to you - Re: boot fails on AMD Compaqs and HPs 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, 14 Sep 2004 22:56:48 -0000 I notice this issue has been moved from Critical status to Serious status. Since this issue is mostly associated with AMD laptops, I wonder if maybe the discussion ought to be moved back to the freebsd-mobile list. Opinions? This patch has been available since July but it seems the keyboard code doesn't get much attention these days. __________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 15 00:01:20 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 7AB7316A4CE for ; Wed, 15 Sep 2004 00:01:20 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46E8543D31 for ; Wed, 15 Sep 2004 00:01:20 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id i8F02G0o021601; Tue, 14 Sep 2004 17:02:16 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id i8F02Gql021600; Tue, 14 Sep 2004 17:02:16 -0700 Date: Tue, 14 Sep 2004 17:02:16 -0700 From: Brooks Davis To: Neil Short Message-ID: <20040915000216.GA20887@odin.ac.hmc.edu> References: <20040914225648.76987.qmail@web12821.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2fHTh5uZTiUOsy+g" Content-Disposition: inline In-Reply-To: <20040914225648.76987.qmail@web12821.mail.yahoo.com> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-amd64@freebsd.org Subject: Re: Current problem reports assigned to you - Re: boot fails on AMD Compaqs and HPs 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, 15 Sep 2004 00:01:20 -0000 --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 14, 2004 at 03:56:48PM -0700, Neil Short wrote: > I notice this issue has been moved from Critical > status to Serious status. >=20 > Since this issue is mostly associated with AMD > laptops, I wonder if maybe the discussion ought to be > moved back to the freebsd-mobile list. Opinions? >=20 > This patch has been available since July but it seems > the keyboard code doesn't get much attention these days. I assume you're talking about amd64/67745? I'd personally be rather nervous about removing a function call that has been in there since the commit in the 3.x days. We probably should have committed this a while back to allow for testing. We certaintly don't want to break hardware that would have worked otherwise. -- brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --2fHTh5uZTiUOsy+g Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBR4aIXY6L6fI4GtQRAg1HAJ9/WqkCVPAgq4t1Bxa2qUSiMRfY+gCg2p/g CDlEhcflBacIJZzEJF0AYMM= =zXqr -----END PGP SIGNATURE----- --2fHTh5uZTiUOsy+g-- From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 15 04:36: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 0AD5916A4CE for ; Wed, 15 Sep 2004 04:36:34 +0000 (GMT) Received: from aaryn.lunarpages.com (aaryn.lunarpages.com [216.193.217.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id C093C43D41 for ; Wed, 15 Sep 2004 04:36:33 +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 1C7RX4-0008Ic-Ry for amd64@freebsd.org; Tue, 14 Sep 2004 21:36:39 -0700 Date: Wed, 15 Sep 2004 00:39:15 -0500 From: John Wilson To: amd64@freebsd.org Message-Id: <20040915003915.2489d1b0.solita2@solitarylight.com> 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: 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, 15 Sep 2004 04:36:34 -0000 Hello all. I am currently in the process of spec'ing a new machine for myself and wish to go the AMD64 way. Unfortunately, trying to find good information on the myriad of mainboards that are available is giving me a serious headache. :) Please keep in mind, that up to this point, I've not strayed from the Intel world, and always used Intel mainboards. >From what I've been able to gather, the two best mainboards for the AMD64 platform come from either Asus or MSI. My original goal was to find a board with the minimum of additional features onboard, save for sound and a NIC. Firewire is useless to me. For what it's worth, I'm planning on getting a retail package AMD64 3000, which includes the AMD brand heatsink and fan. I've attempted browsing the AMD64 mailling list here for good info, but have come away scratching my head even more. Basically, my questions are as follows: - Which is the better chipset for FreeBSD, the Via offering or the NVidia one? - It seems that a lot of the MSI boards use Realtek audio and NIC's. Are these any good? Are they at all supported? My understanding was that Realtek was on the crappy side, but I've no personal experience with them. - It appears that Asus has problems with their onboard NIC as well; there were a few messages posted to the list in regard to this. Is this still a problem? Should I avoid Asus because of this? - If anyone could make a suggestion as to the best mainboard, in regard to FreeBSD compatibility, I'd be most appreciative. Thank you all very much for your time, John Wilson. From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 15 06:35:35 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 6DC5216A4CE for ; Wed, 15 Sep 2004 06:35:35 +0000 (GMT) Received: from ares.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4565443D64 for ; Wed, 15 Sep 2004 06:35:34 +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 i8F6ZTNf082668; Wed, 15 Sep 2004 08:35:29 +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 i8F6ZDGq010396; Wed, 15 Sep 2004 08:35:13 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.1/8.13.1/Submit) id i8F6ZCtx010395; Wed, 15 Sep 2004 08:35:12 +0200 (CEST) (envelope-from ftigeot) Date: Wed, 15 Sep 2004 08:35:12 +0200 From: Francois Tigeot To: Peter Wemm Message-ID: <20040915063512.GA10104@aoi.wolfpond.org> References: <20040914150419.GA7191@aoi.wolfpond.org> <200409141543.13318.peter@wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200409141543.13318.peter@wemm.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: Wed, 15 Sep 2004 06:35:35 -0000 On Tue, Sep 14, 2004 at 03:43:13PM -0700, Peter Wemm wrote: > On Tuesday 14 September 2004 08:04 am, Francois Tigeot wrote: > > I'm running 5.3-BETA4 and I can't find even > > though bios(9) exists. > > It seems bios.h is only present on the i386 and alpha architectures. > > > > Is this normal on amd64 ? If yes, I would appreciate if someone could > > point me to an alternative to bios_sigsearch() > > We dont even have bios_sigsearch() - all the consumers in the kernel > were related to vm86()/bios16()/bios32() calls, which are impossible in > our kernel. This puzzles me, as the functions seem to be present on alpha. > What do you need it for? It might be ok to revive a subset of it, but > it would be useful to know what that file is being used for first, so > we know which subsets are needed. I am experimenting with Bruno Ducrot's powernow_k7 and need to read some tables in BIOS memory area. I will try to see if there is a way to do the same thing via acpi instead... -- Francois Tigeot From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 15 06:54:35 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 AD03B16A4CE for ; Wed, 15 Sep 2004 06:54:35 +0000 (GMT) Received: from ares.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7CD943D1D for ; Wed, 15 Sep 2004 06:54:34 +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 i8F6sXNf082735; Wed, 15 Sep 2004 08:54:33 +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 i8F6sXs1010596; Wed, 15 Sep 2004 08:54:33 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.1/8.13.1/Submit) id i8F6sXD7010595; Wed, 15 Sep 2004 08:54:33 +0200 (CEST) (envelope-from ftigeot) Date: Wed, 15 Sep 2004 08:54:33 +0200 From: Francois Tigeot To: John Wilson Message-ID: <20040915065433.GB10104@aoi.wolfpond.org> References: <20040915003915.2489d1b0.solita2@solitarylight.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040915003915.2489d1b0.solita2@solitarylight.com> User-Agent: Mutt/1.4.2.1i cc: 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, 15 Sep 2004 06:54:35 -0000 On Wed, Sep 15, 2004 at 12:39:15AM -0500, John Wilson wrote: > > I am currently in the process of spec'ing a new machine for myself and wish > to go the AMD64 way. Unfortunately, trying to find good information on > the myriad of mainboards that are available is giving me a serious > headache. :) > > >From what I've been able to gather, the two best mainboards for the AMD64 > platform come from either Asus or MSI. My original goal was to find a board > with the minimum of additional features onboard, save for sound and a NIC. > Firewire is useless to me. > > I've attempted browsing the AMD64 mailling list here for good info, but have > come away scratching my head even more. Basically, my questions are as > follows: > > - Which is the better chipset for FreeBSD, the Via offering or the NVidia one? I believe NForce 3 chipsets have some teething problems. > - It seems that a lot of the MSI boards use Realtek audio and NIC's. Are these > any good? Are they at all supported? My understanding was that Realtek was > on the crappy side, but I've no personal experience with them. The Realtek NIC found on Athlon64 boards is not the crappy rl(4). It supports at least hardware checksum offloading... > - It appears that Asus has problems with their onboard NIC as well; there were > a few messages posted to the list in regard to this. Is this still a problem? > Should I avoid Asus because of this? > > - If anyone could make a suggestion as to the best mainboard, in regard to > FreeBSD compatibility, I'd be most appreciative. I use a MSI K8T Neo-FIS2R and everything works flawlessly including the onboard NIC and sound. -- Francois Tigeot From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 15 07:10:14 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 EF50016A4CE for ; Wed, 15 Sep 2004 07:10:13 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D60FB43D5A for ; Wed, 15 Sep 2004 07:10:13 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i8F7ADHC080097 for ; Wed, 15 Sep 2004 07:10:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i8F7ADLP080096; Wed, 15 Sep 2004 07:10:13 GMT (envelope-from gnats) Resent-Date: Wed, 15 Sep 2004 07:10:13 GMT Resent-Message-Id: <200409150710.i8F7ADLP080096@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Adam Gregoire Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B02116A4CE for ; Wed, 15 Sep 2004 07:03:45 +0000 (GMT) Received: from S01060080c83f4fb0.su.shawcable.net (S01060080c83f4fb0.su.shawcable.net [24.76.70.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4EBD43D49 for ; Wed, 15 Sep 2004 07:03:44 +0000 (GMT) (envelope-from ebola@S01060080c83f4fb0.su.shawcable.net) Received: from S01060080c83f4fb0.su.shawcable.net (ebola@localhost [127.0.0.1]) by S01060080c83f4fb0 (8.13.1/8.13.1) with ESMTP id i8ELrQ9q050496 for ; Tue, 14 Sep 2004 17:53:26 -0400 (EDT) (envelope-from ebola@S01060080c83f4fb0.su.shawcable.net) Received: (from ebola@localhost)i8ELrPXB050489; Tue, 14 Sep 2004 17:53:25 -0400 (EDT) (envelope-from ebola) Message-Id: <200409142153.i8ELrPXB050489@S01060080c83f4fb0.su.shawcable.net> Date: Tue, 14 Sep 2004 17:53:25 -0400 (EDT) From: Adam Gregoire To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: amd64/71753: DRI loads but fails to render on Radeon 9200se(RV280). X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Adam Gregoire List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Sep 2004 07:10:14 -0000 >Number: 71753 >Category: amd64 >Synopsis: DRI loads but fails to render on Radeon 9200se(RV280). >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Sep 15 07:10:13 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Adam Gregoire >Release: FreeBSD 5.3-BETA4 amd64 >Organization: N/A >Environment: System: FreeBSD S01060080c83f4fb0 5.3-BETA4 FreeBSD 5.3-BETA4 #3: Mon Sep 13 03:39:47 EDT 2004 root@S01060080c83f4fb0:/usr/obj/usr/src/sys/OPTMZD amd64 $ pkg_info | grep 'dri-' dri-5.0.2,1 OpenGL hardware acceleration drivers for the DRI $pkg_info | grep 'xorg-' xorg-clients-6.7.0_4 X client programs and related files from X.Org xorg-fonts-encodings-6.7.0 X.Org font encoding files xorg-fonts-miscbitmaps-6.7.0 X.Org miscellaneous bitmap fonts xorg-fonts-truetype-6.7.0 X.Org TrueType fonts xorg-libraries-6.7.0_1 X11 libraries and headers from X.Org xorg-server-6.7.0_7 X.Org X server and related programs >Description: $ dmesg | grep agp agp0: mem 0xf8000000-0xfbffffff at device 0.0 on pci0 $ dmesg | grep drm drm0: port 0xa000-0xa0ff mem 0xfd400000-0xfd40ffff,0xe8000000-0xefffffff irq 16 at device 0.0 on pci1 info: [drm] AGP at 0xf8000000 64MB info: [drm] Initialized radeon 1.11.0 20020828 on minor 0 info: [drm] Loading R200 Microcode $ glxinfo | grep rendering direct rendering: Yes $ glxgears drmCommandWrite: -22 drmRadeonCmdBuffer: -22 (exiting) and the following gets written to syslog: error: [drm:pid5296:radeon_cp_cmdbuf] *ERROR* bad cmd_type 0 at 0x561e10 >How-To-Repeat: Load DRI on amd64(others) on the radeon 9200se (RV280) chipset. Running glxgears produces: drmCommandWrite: -22 drmRadeonCmdBuffer: -22 (exiting) >Fix: N/A >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 15 09:07:27 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 190C116A4CE for ; Wed, 15 Sep 2004 09:07:27 +0000 (GMT) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BC3E43D2F for ; Wed, 15 Sep 2004 09:07:26 +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.17) with ESMTP id i8F97O51010468; Wed, 15 Sep 2004 11:07:24 +0200 (MEST) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Wed, 15 Sep 2004 11:07:18 +0200 User-Agent: KMail/1.7 References: <20040915003915.2489d1b0.solita2@solitarylight.com> In-Reply-To: <20040915003915.2489d1b0.solita2@solitarylight.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200409151107.19224.groot@kde.org> cc: John Wilson 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, 15 Sep 2004 09:07:27 -0000 On Wednesday 15 September 2004 07:39, John Wilson wrote: > I am currently in the process of spec'ing a new machine for myself and wish > to go the AMD64 way. Unfortunately, trying to find good information on > the myriad of mainboards that are available is giving me a serious > headache. :) There are really only two types: nvidia nforce 3 and via kt800 based boards. There are a few sub-variations in those chipsets, but in general if you look at the benchmarks on all them the differences within one family are marginal at best (like 3%). > platform come from either Asus or MSI. My original goal was to find a > board with the minimum of additional features onboard, save for sound and a > NIC. Firewire is useless to me. It's hard to get away from all the builtins; most boards that I'd trust (ie. not stuff from elitegroup) end up with all the bells and whistles. My firewire ports lie idle as well. > - Which is the better chipset for FreeBSD, the Via offering or the NVidia > one? nforce3 _had_ issues, that's for sure (oh, and I can't speak for any of the RAID support). > - It appears that Asus has problems with their onboard NIC as well; there > were a few messages posted to the list in regard to this. Is this still a > problem? Should I avoid Asus because of this? The asus k8v SE has an sk0 onboard that had been reported to be wonky. I had stability problems with it about a month ago, haven't recreated the problem recently (mostly for lack of trying). -- Don't worry, 't ain't no shame to be stupid - ol' mouse. GPG: FEA2 A3FE Adriaan de Groot From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 15 09:19:49 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 DF57C16A4CE for ; Wed, 15 Sep 2004 09:19:49 +0000 (GMT) Received: from fed1rmmtao11.cox.net (fed1rmmtao11.cox.net [68.230.241.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADD3143D45 for ; Wed, 15 Sep 2004 09:19:49 +0000 (GMT) (envelope-from xcas@cox.net) Received: from casper.bsd-unix.org ([68.2.128.106]) by fed1rmmtao11.cox.net SMTP <20040915091949.WWBU15429.fed1rmmtao11.cox.net@casper.bsd-unix.org> for ; Wed, 15 Sep 2004 05:19:49 -0400 Date: Wed, 15 Sep 2004 02:20:40 -0700 From: "Greg J." To: freebsd-amd64@freebsd.org Message-Id: <20040915022040.0a222384.xcas@cox.net> In-Reply-To: <200409151107.19224.groot@kde.org> References: <20040915003915.2489d1b0.solita2@solitarylight.com> <200409151107.19224.groot@kde.org> X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; amd64-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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: Wed, 15 Sep 2004 09:19:50 -0000 > On Wednesday 15 September 2004 07:39, John Wilson wrote: > > I am currently in the process of spec'ing a new machine for myself > > and wish to go the AMD64 way. Unfortunately, trying to find good > > information on the myriad of mainboards that are available is giving > > me a serious headache. :) Can't go wrong with a MSI K8T Neo-FIS2R mobo. I have one & it works great. It does have a Realtek NIC (device re).. but I haven't had issues with it. :) From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 15 14:02:22 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 B7A7D16A4CE for ; Wed, 15 Sep 2004 14:02:22 +0000 (GMT) Received: from max.af.czu.cz (max.af.czu.cz [193.84.41.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 130A743D49 for ; Wed, 15 Sep 2004 14:02:19 +0000 (GMT) (envelope-from lists@hosting50.cz) Received: (qmail 46859 invoked by uid 89); 15 Sep 2004 14:02:17 -0000 Received: from unknown (HELO ?193.84.40.30?) (ares@max.af.czu.cz@193.84.40.30) by max.af.czu.cz with AES256-SHA encrypted SMTP; 15 Sep 2004 14:02:17 -0000 From: Tomas Randa To: amd64@freebsd.org Content-Type: text/plain Message-Id: <1095256935.719.2.camel@ares.af.czu.cz> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 15 Sep 2004 16:02:16 +0200 Content-Transfer-Encoding: 7bit Subject: Problems compiling on AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Sep 2004 14:02:22 -0000 Hi, i have following problems with compiling p5-vpopmail port on AMD64: ===> Building for p5-vpopmail-0.08 rm -f blib/arch/auto/vpopmail/vpopmail.so LD_RUN_PATH="" cc -shared -L/usr/local/lib vpopmail.o -o blib/arch/auto/vpopmail/vpopmail.so -L/usr/local/vpopmail/lib-lvpopmail -lcrypt /usr/bin/ld: /usr/local/vpopmail/lib/libvpopmail.a(vpopmail.o): relocation R_X86_64_32S can not be used when making a shared object; recompile with -fPIC /usr/local/vpopmail/lib/libvpopmail.a: could not read symbols: Bad value *** Error code 1 Stop in /usr/ports/mail/p5-vpopmail/work/vpopmail-0.08. *** Error code 1 Stop in /usr/ports/mail/p5-vpopmail. I tried to add -fPIC to CPUFLAGS in /etc/make.conf with no effect. A searched the archives, but no answer found.. please help me anyone. Thanks TR From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 15 14:12:26 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 D9CC116A4CF for ; Wed, 15 Sep 2004 14:12:26 +0000 (GMT) Received: from max.af.czu.cz (max.af.czu.cz [193.84.41.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED36743D31 for ; Wed, 15 Sep 2004 14:12:25 +0000 (GMT) (envelope-from lists@hosting50.cz) Received: (qmail 47745 invoked by uid 89); 15 Sep 2004 14:12:25 -0000 Received: from unknown (HELO ?193.84.40.30?) (ares@max.af.czu.cz@193.84.40.30) by max.af.czu.cz with AES256-SHA encrypted SMTP; 15 Sep 2004 14:12:25 -0000 From: Tomas Randa To: freebsd-amd64@freebsd.org Message-Id: <1095257544.719.4.camel@ares.af.czu.cz> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 15 Sep 2004 16:12:24 +0200 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Problems compiling some ports on AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Sep 2004 14:12:27 -0000 Hi, i have following problems with compiling p5-vpopmail port on AMD64: ===> Building for p5-vpopmail-0.08 rm -f blib/arch/auto/vpopmail/vpopmail.so LD_RUN_PATH="" cc -shared -L/usr/local/lib vpopmail.o -o blib/arch/auto/vpopmail/vpopmail.so -L/usr/local/vpopmail/lib-lvpopmail -lcrypt /usr/bin/ld: /usr/local/vpopmail/lib/libvpopmail.a(vpopmail.o): relocation R_X86_64_32S can not be used when making a shared object; recompile with -fPIC /usr/local/vpopmail/lib/libvpopmail.a: could not read symbols: Bad value *** Error code 1 Stop in /usr/ports/mail/p5-vpopmail/work/vpopmail-0.08. *** Error code 1 Stop in /usr/ports/mail/p5-vpopmail. I tried to add -fPIC to CPUFLAGS in /etc/make.conf with no effect. A searched the archives, but no answer found.. please help me anyone. Thanks TR From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 15 16:19: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 477C416A4CE for ; Wed, 15 Sep 2004 16:19:15 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18C2943D48 for ; Wed, 15 Sep 2004 16:19:15 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id B8B93F19F8; Wed, 15 Sep 2004 09:19:14 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 52423-09; Wed, 15 Sep 2004 09:19:13 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id C2AFEF19C3; Wed, 15 Sep 2004 09:19:13 -0700 (PDT) From: Sean McNeil To: "Greg J." In-Reply-To: <20040915022040.0a222384.xcas@cox.net> References: <20040915003915.2489d1b0.solita2@solitarylight.com> <20040915022040.0a222384.xcas@cox.net> Content-Type: text/plain Message-Id: <1095265153.53126.2.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 15 Sep 2004 09:19:13 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com 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, 15 Sep 2004 16:19:15 -0000 On Wed, 2004-09-15 at 02:20, Greg J. wrote: > > On Wednesday 15 September 2004 07:39, John Wilson wrote: > > > I am currently in the process of spec'ing a new machine for myself > > > and wish to go the AMD64 way. Unfortunately, trying to find good > > > information on the myriad of mainboards that are available is giving > > > me a serious headache. :) > > Can't go wrong with a MSI K8T Neo-FIS2R mobo. I have one & it works > great. It does have a Realtek NIC (device re).. but I haven't had issues > with it. :) Only problem that I've had is that hardware tx checksums are broken. You have to turn them off or you'll see odd hangs when doing a lot of nfs over that nic. I'd suggest getting firewire as you can at some time possibly use it as a debug port. Sean From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 15 21:29:38 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 6183E16A4CF for ; Wed, 15 Sep 2004 21:29:38 +0000 (GMT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02C4D43D2F for ; Wed, 15 Sep 2004 21:29:38 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 28270 invoked from network); 15 Sep 2004 21:29:37 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 15 Sep 2004 21:29:37 -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 i8FLTXCP060045; Wed, 15 Sep 2004 17:29:33 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org, Adam Gregoire Date: Wed, 15 Sep 2004 17:24:09 -0400 User-Agent: KMail/1.6.2 References: <200409142153.i8ELrPXB050489@S01060080c83f4fb0.su.shawcable.net> In-Reply-To: <200409142153.i8ELrPXB050489@S01060080c83f4fb0.su.shawcable.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200409151724.09501.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: anholt@FreeBSD.org cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: amd64/71753: DRI loads but fails to render on Radeon 9200se(RV280). 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, 15 Sep 2004 21:29:38 -0000 On Tuesday 14 September 2004 05:53 pm, Adam Gregoire wrote: > >Number: 71753 > >Category: amd64 > >Synopsis: DRI loads but fails to render on Radeon 9200se(RV280). > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible: freebsd-amd64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Wed Sep 15 07:10:13 GMT 2004 > >Closed-Date: > >Last-Modified: > >Originator: Adam Gregoire > >Release: FreeBSD 5.3-BETA4 amd64 > >Organization: > > N/A > > >Environment: > > System: FreeBSD S01060080c83f4fb0 5.3-BETA4 FreeBSD 5.3-BETA4 #3: Mon Sep > 13 03:39:47 EDT 2004 root@S01060080c83f4fb0:/usr/obj/usr/src/sys/OPTMZD > amd64 > > $ pkg_info | grep 'dri-' > dri-5.0.2,1 OpenGL hardware acceleration drivers for the DRI > > $pkg_info | grep 'xorg-' > xorg-clients-6.7.0_4 X client programs and related files from X.Org > xorg-fonts-encodings-6.7.0 X.Org font encoding files > xorg-fonts-miscbitmaps-6.7.0 X.Org miscellaneous bitmap fonts > xorg-fonts-truetype-6.7.0 X.Org TrueType fonts > xorg-libraries-6.7.0_1 X11 libraries and headers from X.Org > xorg-server-6.7.0_7 X.Org X server and related programs > > >Description: > > $ dmesg | grep agp > agp0: mem 0xf8000000-0xfbffffff at device 0.0 > on pci0 > > $ dmesg | grep drm > drm0: port 0xa000-0xa0ff mem > 0xfd400000-0xfd40ffff,0xe8000000-0xefffffff irq 16 at device 0.0 on pci1 > info: [drm] AGP at 0xf8000000 64MB > info: [drm] Initialized radeon 1.11.0 20020828 on minor 0 > info: [drm] Loading R200 Microcode > > $ glxinfo | grep rendering > direct rendering: Yes > > $ glxgears > drmCommandWrite: -22 > drmRadeonCmdBuffer: -22 (exiting) > > and the following gets written to syslog: > error: [drm:pid5296:radeon_cp_cmdbuf] *ERROR* bad cmd_type 0 at 0x561e10 > > >How-To-Repeat: > > Load DRI on amd64(others) on the radeon 9200se (RV280) chipset. > > Running glxgears produces: > drmCommandWrite: -22 > drmRadeonCmdBuffer: -22 (exiting) > > >Fix: > > N/A > > >Release-Note: > >Audit-Trail: > >Unformatted: Do you have any errors in Xorg.0.log? Also, did you add an 'AGPSize' option to your Xorg config file to tell it you have a 64MB aperture? X seems to assume a default size of 8MB unless you explicitly tell it you have more. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Wed Sep 15 21:30:25 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 03B9716A4CE for ; Wed, 15 Sep 2004 21:30:25 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D08E043D2F for ; Wed, 15 Sep 2004 21:30:24 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i8FLUO4b083880 for ; Wed, 15 Sep 2004 21:30:24 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i8FLUOoD083874; Wed, 15 Sep 2004 21:30:24 GMT (envelope-from gnats) Date: Wed, 15 Sep 2004 21:30:24 GMT Message-Id: <200409152130.i8FLUOoD083874@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: John Baldwin Subject: Re: amd64/71753: DRI loads but fails to render on Radeon 9200se(RV280). X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John Baldwin List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Sep 2004 21:30:25 -0000 The following reply was made to PR amd64/71753; it has been noted by GNATS. From: John Baldwin To: freebsd-amd64@FreeBSD.org, Adam Gregoire Cc: FreeBSD-gnats-submit@FreeBSD.org, anholt@FreeBSD.org Subject: Re: amd64/71753: DRI loads but fails to render on Radeon 9200se(RV280). Date: Wed, 15 Sep 2004 17:24:09 -0400 On Tuesday 14 September 2004 05:53 pm, Adam Gregoire wrote: > >Number: 71753 > >Category: amd64 > >Synopsis: DRI loads but fails to render on Radeon 9200se(RV280). > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible: freebsd-amd64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Wed Sep 15 07:10:13 GMT 2004 > >Closed-Date: > >Last-Modified: > >Originator: Adam Gregoire > >Release: FreeBSD 5.3-BETA4 amd64 > >Organization: > > N/A > > >Environment: > > System: FreeBSD S01060080c83f4fb0 5.3-BETA4 FreeBSD 5.3-BETA4 #3: Mon Sep > 13 03:39:47 EDT 2004 root@S01060080c83f4fb0:/usr/obj/usr/src/sys/OPTMZD > amd64 > > $ pkg_info | grep 'dri-' > dri-5.0.2,1 OpenGL hardware acceleration drivers for the DRI > > $pkg_info | grep 'xorg-' > xorg-clients-6.7.0_4 X client programs and related files from X.Org > xorg-fonts-encodings-6.7.0 X.Org font encoding files > xorg-fonts-miscbitmaps-6.7.0 X.Org miscellaneous bitmap fonts > xorg-fonts-truetype-6.7.0 X.Org TrueType fonts > xorg-libraries-6.7.0_1 X11 libraries and headers from X.Org > xorg-server-6.7.0_7 X.Org X server and related programs > > >Description: > > $ dmesg | grep agp > agp0: mem 0xf8000000-0xfbffffff at device 0.0 > on pci0 > > $ dmesg | grep drm > drm0: port 0xa000-0xa0ff mem > 0xfd400000-0xfd40ffff,0xe8000000-0xefffffff irq 16 at device 0.0 on pci1 > info: [drm] AGP at 0xf8000000 64MB > info: [drm] Initialized radeon 1.11.0 20020828 on minor 0 > info: [drm] Loading R200 Microcode > > $ glxinfo | grep rendering > direct rendering: Yes > > $ glxgears > drmCommandWrite: -22 > drmRadeonCmdBuffer: -22 (exiting) > > and the following gets written to syslog: > error: [drm:pid5296:radeon_cp_cmdbuf] *ERROR* bad cmd_type 0 at 0x561e10 > > >How-To-Repeat: > > Load DRI on amd64(others) on the radeon 9200se (RV280) chipset. > > Running glxgears produces: > drmCommandWrite: -22 > drmRadeonCmdBuffer: -22 (exiting) > > >Fix: > > N/A > > >Release-Note: > >Audit-Trail: > >Unformatted: Do you have any errors in Xorg.0.log? Also, did you add an 'AGPSize' option to your Xorg config file to tell it you have a 64MB aperture? X seems to assume a default size of 8MB unless you explicitly tell it you have more. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 16 01:07: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 3DCDD16A4CE; Thu, 16 Sep 2004 01:07:53 +0000 (GMT) Received: from smtp.easystreet.com (smtp.easystreet.com [69.30.22.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2448743D45; Thu, 16 Sep 2004 01:07:53 +0000 (GMT) (envelope-from anholt@FreeBSD.org) Received: from [192.168.0.103] (69-30-77-85.dq1sn.easystreet.com [69.30.77.85]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.easystreet.com (Postfix) with ESMTP id 9FA68364004; Wed, 15 Sep 2004 18:07:52 -0700 (PDT) From: Eric Anholt To: John Baldwin In-Reply-To: <200409151724.09501.jhb@FreeBSD.org> References: <200409142153.i8ELrPXB050489@S01060080c83f4fb0.su.shawcable.net> <200409151724.09501.jhb@FreeBSD.org> Content-Type: text/plain Message-Id: <1095296871.864.13.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 15 Sep 2004 18:07:52 -0700 Content-Transfer-Encoding: 7bit cc: gnats cc: Adam Gregoire cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/71753: DRI loads but fails to render on Radeon 9200se(RV280). X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: eta@lclark.edu List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Sep 2004 01:07:53 -0000 On Wed, 2004-09-15 at 14:24, John Baldwin wrote: > Do you have any errors in Xorg.0.log? Also, did you add an 'AGPSize' option > to your Xorg config file to tell it you have a 64MB aperture? X seems to > assume a default size of 8MB unless you explicitly tell it you have more. The AGPSize is just to say how much of the aperture to allocate and bind for use. It turns out that 8MB is all that's really necessary, due to poor or nonexistent use of AGP textures, so that basically what gets used in AGP are the 3MB of vertex/indirect/ring buffers. I wasn't previously aware of any 64-bit issues in the Radeon/R200 DRI (and some have used these on 64-bit machines before), but to me that seems like the most likely reason to find bad command buffers. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 16 01:10:16 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 F1E9E16A4CE for ; Thu, 16 Sep 2004 01:10:16 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3C6743D31 for ; Thu, 16 Sep 2004 01:10:16 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i8G1AGtZ011333 for ; Thu, 16 Sep 2004 01:10:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i8G1AGjZ011332; Thu, 16 Sep 2004 01:10:16 GMT (envelope-from gnats) Date: Thu, 16 Sep 2004 01:10:16 GMT Message-Id: <200409160110.i8G1AGjZ011332@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Eric Anholt Subject: Re: amd64/71753: DRI loads but fails to render on Radeon 9200se(RV280). X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Eric Anholt List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Sep 2004 01:10:17 -0000 The following reply was made to PR amd64/71753; it has been noted by GNATS. From: Eric Anholt To: John Baldwin Cc: freebsd-amd64@FreeBSD.org, Adam Gregoire , gnats Subject: Re: amd64/71753: DRI loads but fails to render on Radeon 9200se(RV280). Date: Wed, 15 Sep 2004 18:07:52 -0700 On Wed, 2004-09-15 at 14:24, John Baldwin wrote: > Do you have any errors in Xorg.0.log? Also, did you add an 'AGPSize' option > to your Xorg config file to tell it you have a 64MB aperture? X seems to > assume a default size of 8MB unless you explicitly tell it you have more. The AGPSize is just to say how much of the aperture to allocate and bind for use. It turns out that 8MB is all that's really necessary, due to poor or nonexistent use of AGP textures, so that basically what gets used in AGP are the 3MB of vertex/indirect/ring buffers. I wasn't previously aware of any 64-bit issues in the Radeon/R200 DRI (and some have used these on 64-bit machines before), but to me that seems like the most likely reason to find bad command buffers. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 16 03:23:43 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 5078D16A4D0 for ; Thu, 16 Sep 2004 03:23:43 +0000 (GMT) Received: from web53903.mail.yahoo.com (web53903.mail.yahoo.com [206.190.36.126]) by mx1.FreeBSD.org (Postfix) with SMTP id CBBAF43D5A for ; Thu, 16 Sep 2004 03:23:42 +0000 (GMT) (envelope-from bsdunx@yahoo.com) Message-ID: <20040916032342.64931.qmail@web53903.mail.yahoo.com> Received: from [24.76.70.40] by web53903.mail.yahoo.com via HTTP; Wed, 15 Sep 2004 20:23:42 PDT Date: Wed, 15 Sep 2004 20:23:42 -0700 (PDT) From: unixgeek _ To: gnats In-Reply-To: <1095296871.864.13.camel@leguin> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: Adam Gregoire cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/71753: DRI loads but fails to render on Radeon 9200se(RV280). X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Sep 2004 03:23:43 -0000 > Do you have any errors in Xorg.0.log? Also, did you > add an 'AGPSize' option > to your Xorg config file to tell it you have a 64MB > aperture? X seems to > assume a default size of 8MB unless you explicitly > tell it you have more. $ grep EE /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (II) Loading extension MIT-SCREEN-SAVER Nothing unusual here. I also added the following to xorg.conf. Option "AGPSize" "64" DRI still loads, and rendering still fails with same error. Adam Gregoire __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail From owner-freebsd-amd64@FreeBSD.ORG Thu Sep 16 03:30: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 915AD16A4CF for ; Thu, 16 Sep 2004 03:30:28 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7800143D53 for ; Thu, 16 Sep 2004 03:30:28 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i8G3USkh024883 for ; Thu, 16 Sep 2004 03:30:28 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i8G3US8Z024876; Thu, 16 Sep 2004 03:30:28 GMT (envelope-from gnats) Date: Thu, 16 Sep 2004 03:30:28 GMT Message-Id: <200409160330.i8G3US8Z024876@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: unixgeek _ Subject: Re: amd64/71753: DRI loads but fails to render on Radeon 9200se(RV280). X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: unixgeek _ List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Sep 2004 03:30:28 -0000 The following reply was made to PR amd64/71753; it has been noted by GNATS. From: unixgeek _ To: gnats Cc: freebsd-amd64@FreeBSD.org, Adam Gregoire Subject: Re: amd64/71753: DRI loads but fails to render on Radeon 9200se(RV280). Date: Wed, 15 Sep 2004 20:23:42 -0700 (PDT) > Do you have any errors in Xorg.0.log? Also, did you > add an 'AGPSize' option > to your Xorg config file to tell it you have a 64MB > aperture? X seems to > assume a default size of 8MB unless you explicitly > tell it you have more. $ grep EE /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (II) Loading extension MIT-SCREEN-SAVER Nothing unusual here. I also added the following to xorg.conf. Option "AGPSize" "64" DRI still loads, and rendering still fails with same error. Adam Gregoire __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 17 16:07:26 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 38A5416A4CE for ; Fri, 17 Sep 2004 16:07:26 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id E050143D2D for ; Fri, 17 Sep 2004 16:07:19 +0000 (GMT) (envelope-from peter@evilpete.dyndns.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id C18D92A8D5 for ; Fri, 17 Sep 2004 09:07:19 -0700 (PDT) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 66099E2B3 for ; Fri, 17 Sep 2004 09:07:19 -0700 (PDT) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.12.11/8.12.11) with ESMTP id i8HG7Ixo097778; Fri, 17 Sep 2004 09:07:18 -0700 (PDT) (envelope-from peter@overcee.wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.12.11/8.12.11/Submit) id i8HG7Im8097777; Fri, 17 Sep 2004 09:07:18 -0700 (PDT) (envelope-from peter) From: Peter Wemm To: Francois Tigeot Date: Fri, 17 Sep 2004 09:07:18 -0700 User-Agent: KMail/1.6.1 References: <20040914150419.GA7191@aoi.wolfpond.org> <200409141543.13318.peter@wemm.org> <20040915063512.GA10104@aoi.wolfpond.org> In-Reply-To: <20040915063512.GA10104@aoi.wolfpond.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200409170907.18458.peter@wemm.org> 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: Fri, 17 Sep 2004 16:07:26 -0000 On Tuesday 14 September 2004 11:35 pm, Francois Tigeot wrote: > On Tue, Sep 14, 2004 at 03:43:13PM -0700, Peter Wemm wrote: > > On Tuesday 14 September 2004 08:04 am, Francois Tigeot wrote: > > > I'm running 5.3-BETA4 and I can't find even > > > though bios(9) exists. > > > It seems bios.h is only present on the i386 and alpha > > > architectures. > > > > > > Is this normal on amd64 ? If yes, I would appreciate if someone > > > could point me to an alternative to bios_sigsearch() > > > > We dont even have bios_sigsearch() - all the consumers in the > > kernel were related to vm86()/bios16()/bios32() calls, which are > > impossible in our kernel. > > This puzzles me, as the functions seem to be present on alpha. No, they are not.. The prototypes are there due to over-merging and lack of cleanup, but there are no implementations for the functions. > > What do you need it for? It might be ok to revive a subset of it, > > but it would be useful to know what that file is being used for > > first, so we know which subsets are needed. > > I am experimenting with Bruno Ducrot's powernow_k7 and need to read > some tables in BIOS memory area. Ahh - bios tables. That we can do. This is for a kernel component, right? > I will try to see if there is a way to do the same thing via acpi > instead... -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 17 16:20: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 9092916A4CE for ; Fri, 17 Sep 2004 16:20:39 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46FA643D4C for ; Fri, 17 Sep 2004 16:20:39 +0000 (GMT) (envelope-from peter@evilpete.dyndns.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 080342A8D5 for ; Fri, 17 Sep 2004 09:20:39 -0700 (PDT) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 9EAC4E2B3 for ; Fri, 17 Sep 2004 09:20:38 -0700 (PDT) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.12.11/8.12.11) with ESMTP id i8HGKbjV097933; Fri, 17 Sep 2004 09:20:38 -0700 (PDT) (envelope-from peter@overcee.wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.12.11/8.12.11/Submit) id i8HGKW7G097930; Fri, 17 Sep 2004 09:20:32 -0700 (PDT) (envelope-from peter) From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Fri, 17 Sep 2004 09:20:32 -0700 User-Agent: KMail/1.6.1 References: <20040915003915.2489d1b0.solita2@solitarylight.com> <200409151107.19224.groot@kde.org> In-Reply-To: <200409151107.19224.groot@kde.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200409170920.32739.peter@wemm.org> cc: John Wilson 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: Fri, 17 Sep 2004 16:20:39 -0000 On Wednesday 15 September 2004 02:07 am, Adriaan de Groot wrote: > On Wednesday 15 September 2004 07:39, John Wilson wrote: > > I am currently in the process of spec'ing a new machine for myself > > and wish to go the AMD64 way. Unfortunately, trying to find good > > information on the myriad of mainboards that are available is > > giving me a serious headache. :) > > There are really only two types: nvidia nforce 3 and via kt800 based > boards. There are a few sub-variations in those chipsets, but in > general if you look at the benchmarks on all them the differences > within one family are marginal at best (like 3%). There are also AMD-manufactured chipsets, but you're not likely to find them on taiwan motherboards. You'll have to look to the US manufacturers for those. (eg: tyan has them) > > platform come from either Asus or MSI. My original goal was to > > find a board with the minimum of additional features onboard, save > > for sound and a NIC. Firewire is useless to me. > > It's hard to get away from all the builtins; most boards that I'd > trust (ie. not stuff from elitegroup) end up with all the bells and > whistles. My firewire ports lie idle as well. > > > - Which is the better chipset for FreeBSD, the Via offering or the > > NVidia one? > > nforce3 _had_ issues, that's for sure (oh, and I can't speak for any > of the RAID support). The nforce3-pro 150 had a particularly poor set of reference bios builds supplied with it. We've had lots of trouble with the reliability of all of the boards with this for some reason or another. Be it mindblowing stupidity or outright errors in the acpi or mpspec tables (how the heck can you mix up irqs??), through to the vendor forgetting to include option roms every few builds and so on. And not to mention that we've had recurring trouble with the apic on some of the earlier rev nforce3-150 boards. I have not heard of anybody using nforce3-250. I guess that is a good sign. I've had lots of success with the via k8t800 boards under freebsd. The bioses are all pretty good and the boards mostly Just Work. The same goes for the AMD 8xxx chipset based boards - they Just Work too. > > - It appears that Asus has problems with their onboard NIC as well; > > there were a few messages posted to the list in regard to this. Is > > this still a problem? Should I avoid Asus because of this? > > The asus k8v SE has an sk0 onboard that had been reported to be > wonky. I had stability problems with it about a month ago, haven't > recreated the problem recently (mostly for lack of trying). I remember reading something about the serial eeprom on that board being misprogrammed during manufacturing. Some folks have no trouble, others have no end of trouble. I personally use asus k8v (not SE), and asus sk8v boards. Oh, there is one bios problem with the asus via based boards. If you use a usb keyboard, it works up to the point that you boot from the mbr. It seems that it has a list of mbr partition types encoded in the bios to decide whether to leave the usb keyboard enabled. And freebsd's mbr type isn't included. So what happens is the usb keyboard stops working the very second you get to the boot prompt. :-( The exact same bootblocks work with the usb keyboard from floppy, so it is the bios being braindead stupid. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 17 19:09: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 25F0616A4CE for ; Fri, 17 Sep 2004 19:09:03 +0000 (GMT) Received: from ares.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A04E43D1F for ; Fri, 17 Sep 2004 19:09:01 +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 i8HJ90Nf003406; Fri, 17 Sep 2004 21:09:00 +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 i8HJ8pHu089641; Fri, 17 Sep 2004 21:08:51 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.1/8.13.1/Submit) id i8HJ8o2V089640; Fri, 17 Sep 2004 21:08:50 +0200 (CEST) (envelope-from ftigeot) Date: Fri, 17 Sep 2004 21:08:50 +0200 From: Francois Tigeot To: Peter Wemm Message-ID: <20040917190850.GA69926@aoi.wolfpond.org> References: <20040914150419.GA7191@aoi.wolfpond.org> <200409141543.13318.peter@wemm.org> <20040915063512.GA10104@aoi.wolfpond.org> <200409170907.18458.peter@wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200409170907.18458.peter@wemm.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: Fri, 17 Sep 2004 19:09:03 -0000 On Fri, Sep 17, 2004 at 09:07:18AM -0700, Peter Wemm wrote: > On Tuesday 14 September 2004 11:35 pm, Francois Tigeot wrote: > > On Tue, Sep 14, 2004 at 03:43:13PM -0700, Peter Wemm wrote: > > > On Tuesday 14 September 2004 08:04 am, Francois Tigeot wrote: > > > > I'm running 5.3-BETA4 and I can't find even > > > > though bios(9) exists. > > > > > > We dont even have bios_sigsearch() - all the consumers in the > > > kernel were related to vm86()/bios16()/bios32() calls, which are > > > impossible in our kernel. > > > > This puzzles me, as the functions seem to be present on alpha. > > No, they are not.. The prototypes are there due to over-merging and > lack of cleanup, but there are no implementations for the functions. My bad, I did a quick grep in /usr/src. > > > What do you need it for? It might be ok to revive a subset of it, > > > but it would be useful to know what that file is being used for > > > first, so we know which subsets are needed. > > > > I am experimenting with Bruno Ducrot's powernow_k7 and need to read > > some tables in BIOS memory area. > > 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/ -- Francois Tigeot From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 17 22:34:47 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 BE0C816A55C for ; Fri, 17 Sep 2004 22:34:46 +0000 (GMT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D53443D53 for ; Fri, 17 Sep 2004 22:34:46 +0000 (GMT) (envelope-from bung-foo@comcast.net) Received: from 204.127.197.113 ([204.127.197.113]) by comcast.net (rwcrmhc12) with SMTP id <2004091722342601400fbphoe>; Fri, 17 Sep 2004 22:34:26 +0000 Received: from [128.208.94.53] by 204.127.197.113; Fri, 17 Sep 2004 22:34:26 +0000 From: bung-foo@comcast.net To: freebsd-amd64@freebsd.org Date: Fri, 17 Sep 2004 22:34:26 +0000 Message-Id: <091720042234.13357.414B6672000085F80000342D2200745672010100D309029A0D@comcast.net> X-Mailer: AT&T Message Center Version 1 (Jul 16 2004) X-Authenticated-Sender: YnVuZy1mb29AY29tY2FzdC5uZXQ= Subject: emu10k1 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: Fri, 17 Sep 2004 22:34:47 -0000 I'm running 5.3 beta 4 on my opteron system. Thanks for this great OS by the way. I added device sound device "emu10k1" to the kernel and rebuilt it and now I have working sound with my audigy card. My question is that it sounds like the card is set to output to 4 speakers or 5.1 rather than stereo. Is there a configuration file or something where I can change the output options? Thanks for your time and your knowledge folks. Abe From owner-freebsd-amd64@FreeBSD.ORG Fri Sep 17 23:40:25 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 2099C16A4CE for ; Fri, 17 Sep 2004 23:40:25 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15B3743D1F for ; Fri, 17 Sep 2004 23:40:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i8HNeOo3064611 for ; Fri, 17 Sep 2004 23:40:24 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i8HNeOo3064610; Fri, 17 Sep 2004 23:40:24 GMT (envelope-from gnats) Date: Fri, 17 Sep 2004 23:40:24 GMT Message-Id: <200409172340.i8HNeOo3064610@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Adam Gregoire Subject: Re: amd64/71753: DRI loads but fails to render on Radeon 9200se(RV280). X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Adam Gregoire List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Sep 2004 23:40:25 -0000 The following reply was made to PR amd64/71753; it has been noted by GNATS. From: Adam Gregoire To: freebsd-gnats-submit@FreeBSD.ORG Cc: Subject: Re: amd64/71753: DRI loads but fails to render on Radeon 9200se(RV280). Date: Fri, 17 Sep 2004 16:34:34 -0700 (PDT) Well, I have tried playing with all X Options for AGP, tried changing BIOS settings, to no effect. Today I borrowed an ATI Radeon QY RV100 7000/VE and have the same error from any program trying to use DRI: drmCommandWrite: -22 drmRadeonCmdBuffer: -22 (exiting) Now I really am starting to think that it is a 64-bit issue. Any suggestions? __________________________________ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 18 00:16: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 7AADF16A4CE for ; Sat, 18 Sep 2004 00:16:34 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BB7943D1F for ; Sat, 18 Sep 2004 00:16:34 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 023D5F1A06 for ; Fri, 17 Sep 2004 17:16:34 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18363-06 for ; Fri, 17 Sep 2004 17:16:33 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 02987F1A02 for ; Fri, 17 Sep 2004 17:16:32 -0700 (PDT) From: Sean McNeil To: freebsd-amd64@freebsd.org Content-Type: text/plain Message-Id: <1095466592.48494.11.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 17 Sep 2004 17:16:32 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com Subject: gdb problems with args to functions after a vararg routine 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, 18 Sep 2004 00:16:34 -0000 I've noticed this lately and have a clear-cut example where things look right but something is certainly off: seahorse crashes for me on amd64-current during initialization. The backtrace looks ok until I get to a vararg call and then it looks like arguments to funtion call further down the trace are hosed. For instance, this call actually has one parameter after it that is the vararg item: #3 0x0000000202f43382 in g_signal_new (signal_name=0x41adec "add", itype=5714304, signal_flags=G_SIGNAL_RUN_LAST, class_offset=160, accumulator=0, accu_data=0x0, c_marshaller=0x1, return_type=4, n_params=1) at gsignal.c:1130 then the next call looks sane and correct #2 0x0000000202f44b98 in g_signal_new_valist (signal_name=0x41adec "add", itype=5714304, signal_flags=G_SIGNAL_RUN_LAST, class_closure=0x56f980, accumulator=0, accu_data=0x0, c_marshaller=0x1, return_type=1, n_params=1, args=0x7fffffffe2e0) at gsignal.c:1370 but then it messes up with #1 0x0000000202f43faa in g_signal_newv (signal_name=0x0, itype=5714304, signal_flags=G_SIGNAL_RUN_LAST, class_closure=0x56f980, accumulator=0, accu_data=0x0, c_marshaller=0x1, return_type=4, n_params=1, param_types=0x569a00) at gsignal.c:1267 All that happens in between is that the varargs are scanned and put into an array 'param_types'. All the args look correct with the exception of the first one. Actlually looking at all calls to this function it would appear that gdb cannot understand the arguments at this point. All calls to this function have hosed arguments displayed. Sean From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 18 13:18:00 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 0CC0416A4CE; Sat, 18 Sep 2004 13:18:00 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9962743D46; Sat, 18 Sep 2004 13:17:59 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id i8IDHxLe078721; Sat, 18 Sep 2004 09:17:59 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.12.11/8.12.11) with ESMTP id i8IDHxNf095253; Sat, 18 Sep 2004 09:17:59 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id E5B727303F; Sat, 18 Sep 2004 09:17:58 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20040918131758.E5B727303F@freebsd-current.sentex.ca> Date: Sat, 18 Sep 2004 09:17:58 -0400 (EDT) Subject: [releng_5 tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Sep 2004 13:18:00 -0000 TB --- 2004-09-18 12:21:45 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-09-18 12:21:45 - starting RELENG_5 tinderbox run for amd64/amd64 TB --- 2004-09-18 12:21:45 - checking out the source tree TB --- 2004-09-18 12:21:45 - cd /home/tinderbox/RELENG_5/amd64/amd64 TB --- 2004-09-18 12:21:45 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_5 src TB --- 2004-09-18 12:29:46 - building world (CFLAGS=-O -pipe) TB --- 2004-09-18 12:29:46 - cd /home/tinderbox/RELENG_5/amd64/amd64/src TB --- 2004-09-18 12:29:46 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O -pipe -DHAVE_POLL_H -o faithd faithd.o tcp.o ftp.o prefix.o gzip -cn /tinderbox/RELENG_5/amd64/amd64/src/usr.sbin/faithd/faithd.8 > faithd.8.gz ===> usr.sbin/fdcontrol cc -O -pipe -I/tinderbox/RELENG_5/amd64/amd64/src/usr.sbin/fdcontrol/../fdread -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /tinderbox/RELENG_5/amd64/amd64/src/usr.sbin/fdcontrol/fdcontrol.c /tinderbox/RELENG_5/amd64/amd64/src/usr.sbin/fdcontrol/fdcontrol.c: In function `main': /tinderbox/RELENG_5/amd64/amd64/src/usr.sbin/fdcontrol/fdcontrol.c:212: error: `FD_DEBUG' undeclared (first use in this function) /tinderbox/RELENG_5/amd64/amd64/src/usr.sbin/fdcontrol/fdcontrol.c:212: error: (Each undeclared identifier is reported only once /tinderbox/RELENG_5/amd64/amd64/src/usr.sbin/fdcontrol/fdcontrol.c:212: error: for each function it appears in.) *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/src/usr.sbin/fdcontrol. *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/src/usr.sbin. *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/RELENG_5/amd64/amd64/src. TB --- 2004-09-18 13:17:58 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-09-18 13:17:58 - ERROR: failed to build world TB --- 2004-09-18 13:17:58 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 18 14:07: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 43D5616A4CE for ; Sat, 18 Sep 2004 14:07:33 +0000 (GMT) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FA1043D48 for ; Sat, 18 Sep 2004 14:07:31 +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 <20040918140730.TSJR1871.mxfep01.bredband.com@[192.168.245.231]> for ; Sat, 18 Sep 2004 16:07:30 +0200 Message-ID: <414C40CD.9090806@bredband.net> Date: Sat, 18 Sep 2004 16:06:05 +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: FBSD 5.3 AMD64-BETA4 X.ORG is not obeying XKB directives 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, 18 Sep 2004 14:07:33 -0000 Hi, Have started playing with Fbsd 5.3 Amd64 - beta4. I am unable to make X.org belive that I have a swedish keyboard . Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbLayout" "se" Option "XkbModel" "pc104" Even if there are no error msgs in /var/log/Xorg.0.log , and no error msgs on the console , keyboard layout in Gnome 2.6 is and stays "US" any ideas ? Regards //Lars From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 18 14:16: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 25DB716A4CE for ; Sat, 18 Sep 2004 14:16:39 +0000 (GMT) Received: from freenix.no (atreides.freenix.no [212.33.142.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9EC543D45 for ; Sat, 18 Sep 2004 14:16:37 +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 i8IEGZx9098498 for ; Sat, 18 Sep 2004 16:16:36 +0200 (CEST) (envelope-from shamz@atreides.freenix.no) Received: (from shamz@localhost) by atreides.freenix.no (8.12.11/8.12.11/Submit) id i8IEGUVq098497 for freebsd-amd64@freebsd.org; Sat, 18 Sep 2004 16:16:30 +0200 (CEST) (envelope-from shamz) Date: Sat, 18 Sep 2004 16:16:30 +0200 From: Shaun Jurrens To: freebsd-amd64@freebsd.org Message-ID: <20040918141630.GF90420@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, clamav-milter version 0.75 on atreides X-Virus-Status: Clean Subject: Re: FBSD 5.3 AMD64-BETA4 X.ORG is not obeying XKB directives 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, 18 Sep 2004 14:16:39 -0000 hey Lars, this seems to work for me on my .no kbd... YMMV Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc102" Option "XkbLayout" "no" EndSection -- Yours truly, Shaun D. Jurrens shaun@shamz.net From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 18 14:28: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 015AA16A4CE for ; Sat, 18 Sep 2004 14:28:58 +0000 (GMT) Received: from freenix.no (atreides.freenix.no [212.33.142.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30AE643D2D for ; Sat, 18 Sep 2004 14:28:57 +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 i8IEStKI098646 for ; Sat, 18 Sep 2004 16:28:56 +0200 (CEST) (envelope-from shamz@atreides.freenix.no) Received: (from shamz@localhost) by atreides.freenix.no (8.12.11/8.12.11/Submit) id i8IESofu098645 for freebsd-amd64@freebsd.org; Sat, 18 Sep 2004 16:28:50 +0200 (CEST) (envelope-from shamz) Date: Sat, 18 Sep 2004 16:28:50 +0200 From: Shaun Jurrens To: freebsd-amd64@freebsd.org Message-ID: <20040918142850.GG90420@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, clamav-milter version 0.75 on atreides X-Virus-Status: Clean Subject: snd_ modules disconnected from build in 5.3-BETA4 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, 18 Sep 2004 14:28:58 -0000 Hey... just installed from the 5.3-BETA4-amd64 iso and cvsup'd and upgraded, etc... There are just a few nits, I guess. The sound modules are/were not installed and could not be built with the sys/modules/Makefile in RELENG_5 . I grabbed $FreeBSD: /repoman/r/ncvs/src/sys/modules/Makefile,v 1.397 2004/08/30 03:37:36 scottl Exp $ and had to comment out the aac_ stuff (don't remember the error, but I may not even have the code to build that module anyway). The snd_via8233.ko then built with the other modules, loaded (manually, after boot), and seems to be working without problems. Is this an oversight from re@ ? I probably should comment that NOTES makes no mention at all of 'device sound' either, fwiw. I didn't see that in the i386 NOTES either, nor in GENERIC, but I can't remember if that supposed to be in GENERIC or not. The only other problem I ran into was that some freetype lib was missing from the xorg libs pkg (I installed X.org from via pkg, just to get things up and moving), so I rebuilt that via ports and things just worked. Good work, guys! I could really use the asr driver, btw, but the job looks a little hairy. I'll see what I can make out of what's left. FreeBSD dakota 5.3-BETA4 FreeBSD 5.3-BETA4 #1: Sat Sep 18 15:12:28 CEST 2004 root@dakota:/usr/obj/usr/src/sys/DAKOTA64 amd64 -- Yours truly, Shaun D. Jurrens shaun@shamz.net From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 18 15:05:49 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 E58CA16A4CE for ; Sat, 18 Sep 2004 15:05:49 +0000 (GMT) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CC8343D31 for ; Sat, 18 Sep 2004 15:05:49 +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 id <20040918150547.SDUR26974.mxfep02.bredband.com@[192.168.245.231]> for ; Sat, 18 Sep 2004 17:05:47 +0200 Message-ID: <414C4E77.70007@bredband.net> Date: Sat, 18 Sep 2004 17:04:23 +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: Re: FBSD 5.3 AMD64-BETA4 X.ORG is not obeying XKB directives 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, 18 Sep 2004 15:05:50 -0000 Shaun Jurrens wrote: > hey Lars, > > this seems to work for me on my .no kbd... YMMV > I edited it to this > Section "InputDevice" > Identifier "Keyboard0" > Driver "keyboard" > Option "XkbRules" "xfree86" > Option "XkbModel" "pc105" > Option "XkbLayout" "se" > EndSection > > 1) Yes does work but is against advice given by Marcus Clarke and others where they say that the line : Option "XkbRules" "xfree86" is to be replaced by Option "XkbRules" "xorg" or deleted. I noticed That /usr/X11R6/lib/X11/Xkb seems to be the old xfree86 directory and does not contain any references to Xorg. 2) With the above in /etc/x11/xorg.conf I get an error message from GNOME startup that says: ---------------- Error activating XKB configuration. Probably internal X server problem. X server version data: The X.Org Foundation 60700000 If you report this situation as a bug, please include: - The result of xprop -root | grep XKB - The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/xkb ---------------- capella# xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "xfree86", "pc105", "se", "", "" _XKB_RULES_NAMES(STRING) = "xfree86", "pc105", "se", "", "" capella# gconftool-2 -R /desktop/gnome/peripherals/keyboard/xkb layouts = [us] model = pc105 overrideSettings = false options = [] capella# //Regards //Lars From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 18 16:55: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 24A3116A4CF for ; Sat, 18 Sep 2004 16:55:16 +0000 (GMT) Received: from mailtest.sd73.bc.ca (mailtest.sd73.bc.ca [142.24.13.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1BB343D4C for ; Sat, 18 Sep 2004 16:55:15 +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 98B7D7A7A3 for ; Wed, 15 Sep 2004 08:30:33 -0700 (PDT) Received: from mailtest.sd73.bc.ca ([127.0.0.1]) by localhost (mailtest.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 68456-01-59 for ; Wed, 15 Sep 2004 08:30:32 -0700 (PDT) Received: from s166.sbo (s166.sbo [192.168.0.166]) by mailtest.sd73.bc.ca (Postfix) with ESMTP id C9F477A732 for ; Wed, 15 Sep 2004 08:30:32 -0700 (PDT) From: Freddie Cash Organization: School District 73 - Kamloops, BC To: freebsd-amd64@freebsd.org Date: Wed, 15 Sep 2004 08:29:09 -0400 User-Agent: KMail/1.7 References: <20040915003915.2489d1b0.solita2@solitarylight.com> In-Reply-To: <20040915003915.2489d1b0.solita2@solitarylight.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200409150829.10481.fcash-ml@sd73.bc.ca> X-Virus-Scanned: by amavisd-new at sd73.bc.ca 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: Sat, 18 Sep 2004 16:55:16 -0000 On September 15, 2004 01:39 am, John Wilson wrote: >From what I've been able to gather, the two best mainboards for the > AMD64 platform come from either Asus or MSI. My original goal was to > find a board with the minimum of additional features onboard, save for > sound and a NIC. Firewire is useless to me. 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). > - It seems that a lot of the MSI boards use Realtek audio and NIC's. > Are these any good? Are they at all supported? My understanding was > that Realtek was on the crappy side, but I've no personal experience > with them. The MSI boards we have don't use rl(4). The AthlonMP boards have fxp(4) NICs onboard, and the Opteron boards have bge(4) NICs. Don't know about the audio, though, as I disabled it in the BIOS before ever installing anything. -- 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 Sat Sep 18 22:00: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 E0C2216A4CE for ; Sat, 18 Sep 2004 22:00:51 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1724943D48 for ; Sat, 18 Sep 2004 22:00:51 +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 i8IM0nEg066310; Sun, 19 Sep 2004 00:00:49 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <414CB011.4030206@withagen.nl> Date: Sun, 19 Sep 2004 00:00:49 +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: Freddie Cash References: <20040915003915.2489d1b0.solita2@solitarylight.com> <200409150829.10481.fcash-ml@sd73.bc.ca> In-Reply-To: <200409150829.10481.fcash-ml@sd73.bc.ca> Content-Type: text/plain; charset=ISO-8859-1; 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: Sat, 18 Sep 2004 22:00:52 -0000 Freddie Cash wrote: >On September 15, 2004 01:39 am, John Wilson wrote: >>From what I've been able to gather, the two best mainboards for the > > >>AMD64 platform come from either Asus or MSI. My original goal was to >>find a board with the minimum of additional features onboard, save for >>sound and a NIC. Firewire is useless to me. >> >> > >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. --WjW From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 18 22:29:44 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 1DC4516A4CE for ; Sat, 18 Sep 2004 22:29:44 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53A5B43D31 for ; Sat, 18 Sep 2004 22:29:43 +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 i8IMTgEg067242; Sun, 19 Sep 2004 00:29:42 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <414CB6D6.4000407@withagen.nl> Date: Sun, 19 Sep 2004 00:29:42 +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: Nikolaos Korkakakis , "freebsd-amd64@freebsd.org" References: <20040915003915.2489d1b0.solita2@solitarylight.com> <200409150829.10481.fcash-ml@sd73.bc.ca> <414CB011.4030206@withagen.nl> <493526a2040918150826d1bbbd@mail.gmail.com> In-Reply-To: <493526a2040918150826d1bbbd@mail.gmail.com> 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: Sat, 18 Sep 2004 22:29:44 -0000 Nikolaos Korkakakis wrote: >I am using a gigabyte with VIA's k8t800 and AMD64 3000 with no probs. >But there are alo of stuff I guess you don't need [firewire gigabit >lan sound etc etc etc]. > > Are you using it in SMP mode??? because that is where the problems starts... Inter processor interrupts get lost, and other syncronisation is not handled correctly. And lots of panics become a way of life. Sorry if I forgot to mention that in a previous post, but I thought that that was the original precondition of the question. --WjW