From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 19 09: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 3732F16A4CE for ; Sun, 19 Dec 2004 09:55:16 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED97843D2F for ; Sun, 19 Dec 2004 09:55:15 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iBJ9tECi045707; Sun, 19 Dec 2004 01:55:15 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iBJ9tEL6045706; Sun, 19 Dec 2004 01:55:14 -0800 (PST) (envelope-from obrien) Date: Sun, 19 Dec 2004 01:55:14 -0800 From: "David O'Brien" To: Chris Dillon Message-ID: <20041219095514.GA7942@dragon.nuxi.com> References: <200412161403.46382.peter@wemm.org> <20041217122537.B85275@duey.wolves.k12.mo.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041217122537.B85275@duey.wolves.k12.mo.us> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: AW: FreeBSD 5.3; howto migrate from i386 to amd64 mode X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 09:55:16 -0000 On Fri, Dec 17, 2004 at 12:30:30PM -0600, Chris Dillon wrote: > On Thu, 16 Dec 2004, Peter Wemm wrote: > >The difficulty is working around the catch-22 situation where you > >need a new kernel first so you can install world, and you need a new > >world first before you can boot the new kernel. Cheating and using > >the swap partition for a temporary world is one way around it. It > >might even be necessary to do a new buildworld inside the temporary > >world if you can't reinstall the previous one. Some creativity will > >be needed. > > Isn't this where /usr/src/installworld_oldk could come in handy? > Apparently there was a similar chicken & egg problem updating > FreeBSD/sparc64 to 64BTT but installworld_oldk claims it can be used > for any situation where you need to install a majorly incompatible > old-kernel/new-world. This moving an installed 32-bit system to 64-bit has so much potential for food shooting, that I don't think we should come close to making it easy. There is reason that no other Unix supports such a thing on AMD64. People should back up their data and do a fresh install. Those that are true hard-core tinkers, a recipe has been posted. If they don't understand the steps and can't follow them; they probably shouldn't be trying this approach. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 19 10:09:25 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8689E16A4CE for ; Sun, 19 Dec 2004 10:09:25 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5888443D2D for ; Sun, 19 Dec 2004 10:09:25 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iBJA9Osh045986; Sun, 19 Dec 2004 02:09:24 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iBJA9K0B045985; Sun, 19 Dec 2004 02:09:20 -0800 (PST) (envelope-from obrien) Date: Sun, 19 Dec 2004 02:09:20 -0800 From: "David O'Brien" To: dev tree Message-ID: <20041219100920.GB7942@dragon.nuxi.com> References: <20041213152257.A3882@rc.tex-an.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041213152257.A3882@rc.tex-an.net> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: 5.3R cvsup failure, libm.so.2. COMPAT files missing? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 10:09:25 -0000 On Wed, Dec 15, 2004 at 05:38:09PM -0600, dev tree wrote: > > I did a fresh install of 5.3-R AMD64 from the disc1 dated > Nov 05 (I verified the md5 checksum), selecting "ALL" > under Distributions. I added package cvsup-16.1h, > did a buildworld and an SMP kernel, then attempted to do > a cvsup update along the RELENG5_3 line. > > I got the following error on a missing library file: > inoxidable[34]# uname -a > FreeBSD inoxidable.tex-an.net 5.3-RELEASE FreeBSD 5.3-RELEASE #0: > Wed Dec 15 13:31:38 UTC 2004 > root@inoxidable.tex-an.net:/usr/obj/usr/src/sys/SMP amd64 ... > >>> Running /usr/local/bin/cvsup > -------------------------------------------------------------- > /libexec/ld-elf.so.1: Shared object "libm.so.2" not found, required by > "cvsup" > *** Error code 1 This should be impossible. RCS file: /home/ncvs/ports/net/cvsup/Makefile,v RELEASE_5_3_0: 1.57 ---------------------------- revision 1.57 date: 2004/10/11 22:10:58; author: obrien; state: Exp; lines: +1 -0 Catching up with lib bumping, consume libm.so.3 on AMD64. ---------------------------- How did you install CVSup and what is the MD5 checksum of your distfile 'cvsup-without-gui.amd64.tar.bz2'? hammer$ ldd /usr/local/bin/cvsup | grep libm libm.so.3 => /lib/libm.so.3 (0x8007f2000) -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 19 18:41: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 2AEFC16A4CE for ; Sun, 19 Dec 2004 18:41:35 +0000 (GMT) Received: from smtp.orbitel.bg (smtp.orbitel.bg [195.24.32.22]) by mx1.FreeBSD.org (Postfix) with SMTP id 82FCE43D3F for ; Sun, 19 Dec 2004 18:41:33 +0000 (GMT) (envelope-from yngwiie@developer.bg) Received: (qmail 14235 invoked from network); 19 Dec 2004 18:41:31 -0000 Received: from unknown (HELO localhost) (10.0.0.4) by smtp.orbitel.bg with SMTP; 19 Dec 2004 18:41:31 -0000 Received: from smtp.orbitel.bg ([10.0.0.3]) by localhost (sof-rv2.orbitel.bg [10.0.0.4]) (amavisd-new, port 10024) with SMTP id 18568-52 for ; Sun, 19 Dec 2004 20:42:04 +0200 (EET) Received: (qmail 14229 invoked from network); 19 Dec 2004 18:41:31 -0000 Received: from unknown (HELO ?195.24.91.22?) (yngwiie%developer.bg@195.24.91.22) by smtp.orbitel.bg with SMTP; 19 Dec 2004 18:41:31 -0000 Message-ID: <41C5CB5E.7020409@developer.bg> Date: Sun, 19 Dec 2004 20:41:34 +0200 From: Ivan Georgiev User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at orbitel.bg Subject: nforce3 nic driver X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 18:41:35 -0000 Hello, I tried running the driver from ports on both platforms i386 and amd64, but it does not work on both. Under i386 when the module is loaded the kernel recognizes it as agp0 which is completely insane and under amd64 it doesn`t detect the nic at all. I`ve heard that David O`Brien has written a driver from scratch but hasn`t commited it yet. So please if you have any ideas on how to build this driver please help, and if you have David`s driver please post a link. Regards: Ivan Georgiev From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 19 21:54:50 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 B887416A4CE; Sun, 19 Dec 2004 21:54:50 +0000 (GMT) Received: from rc.tex-an.net (rc.tex-an.net [141.198.193.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5948E43D41; Sun, 19 Dec 2004 21:54:50 +0000 (GMT) (envelope-from wayside@rc.tex-an.net) Received: from rc.tex-an.net (localhost.capnet.state.tx.us [127.0.0.1]) by rc.tex-an.net (8.13.1/8.13.1) with ESMTP id iBJLsApL016849; Sun, 19 Dec 2004 15:54:10 -0600 (CST) (envelope-from wayside@rc.tex-an.net) Received: from localhost (wayside@localhost) by rc.tex-an.net (8.13.1/8.13.1/Submit) with ESMTP id iBJLsAA6016846; Sun, 19 Dec 2004 15:54:10 -0600 (CST) (envelope-from wayside@rc.tex-an.net) Date: Sun, 19 Dec 2004 15:54:10 -0600 (CST) From: dev tree To: "David O'Brien" In-Reply-To: <20041219100920.GB7942@dragon.nuxi.com> Message-ID: <20041219153005.T16666@rc.tex-an.net> References: <20041213152257.A3882@rc.tex-an.net> <20041219100920.GB7942@dragon.nuxi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-amd64@freebsd.org Subject: Re: 5.3R cvsup failure, libm.so.2. COMPAT files missing? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 21:54:51 -0000 On Sun, 19 Dec 2004, David O'Brien wrote: > On Wed, Dec 15, 2004 at 05:38:09PM -0600, dev tree wrote: >> >> I did a fresh install of 5.3-R AMD64 from the disc1 dated >> Nov 05 (I verified the md5 checksum), selecting "ALL" >> under Distributions. I added package cvsup-16.1h, >> did a buildworld and an SMP kernel, then attempted to do >> a cvsup update along the RELENG5_3 line. >> >> I got the following error on a missing library file: >> inoxidable[34]# uname -a >> FreeBSD inoxidable.tex-an.net 5.3-RELEASE FreeBSD 5.3-RELEASE #0: >> Wed Dec 15 13:31:38 UTC 2004 >> root@inoxidable.tex-an.net:/usr/obj/usr/src/sys/SMP amd64 > ... >> >>> Running /usr/local/bin/cvsup >> -------------------------------------------------------------- >> /libexec/ld-elf.so.1: Shared object "libm.so.2" not found, required by >> "cvsup" >> *** Error code 1 > This should be impossible. > RCS file: /home/ncvs/ports/net/cvsup/Makefile,v > RELEASE_5_3_0: 1.57 > ---------------------------- > revision 1.57 > date: 2004/10/11 22:10:58; author: obrien; state: Exp; lines: > +1 -0 > Catching up with lib bumping, consume libm.so.3 on AMD64. > ---------------------------- > > How did you install CVSup and what is the MD5 checksum of your distfile > 'cvsup-without-gui.amd64.tar.bz2'? > > hammer$ ldd /usr/local/bin/cvsup | grep libm > libm.so.3 => /lib/libm.so.3 (0x8007f2000) I used cvsup16.1h, and I think I took it off the Nov 05 5.3-R disc1 CD immediately after the system install. I had done it from the CD on another system, then removed that and tryed again from /stand/systinstall, prior to building inoxidable from scratch on Dec 14 to test it with a fresh installation. The package seems to have been from October 08. Here's whats in /var/db/pkg: inoxidable[34]# ll -d cvsup-16.1h drwxr-xr-x 2 root wheel 512 Dec 14 17:54 cvsup-16.1h/ inoxidable[35]# inoxidable[35]# ll cvsup-16.1h total 22 -rw-r--r-- 1 root wheel 73 Oct 8 09:38 +COMMENT -rw-r--r-- 1 root wheel 695 Dec 14 17:54 +CONTENTS -rw-r--r-- 1 root wheel 718 Oct 8 09:38 +DESC -r--r--r-- 1 root wheel 11209 Oct 8 09:38 +MTREE_DIRS drwxr-xr-x 2 root wheel 512 Dec 14 17:54 ./ drwxr-xr-x 30 root wheel 1024 Dec 18 00:21 ../ inoxidable[36]# uname -a FreeBSD inoxidable.tex-an.net 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 #0: Wed Dec 15 18:54:27 UTC 2004 root@inoxidable.tex-an.net:/usr/obj/usr/src/sys/INOXIDABLE amd64 inoxidable[37]# Here's whats in packages on ftp.freebsd.org right now: Script started on Sun Dec 19 15:42:01 2004 %ftp ftp.freebsd.org Trying 2001:4f8:0:2::e... ftp: connect to address 2001:4f8:0:2::e: No route to host Trying 204.152.184.73... Connected to ftp.freebsd.org. 220 Welcome to freebsd.isc.org. Name (ftp.freebsd.org:wayside): ftp 331 Please specify the password. Password: 230- 230-You have reached the freebsd.isc.org FTP server, serving the 230-full FreeBSD FTP archive over IPv4 (204.152.184.73) and IPv6 230-(2001:4f8:0:2::e) networks. This server is also known as: 230- 230- ftp.freebsd.org 230- ftp4.freebsd.org 230- ftp4.us.freebsd.org 230- [...] ftp> cd /pub/FreeBSD/ports/amd64/packages-5.3-release/All 250 Directory successfully changed. ftp> dir cvsup* 229 Entering Extended Passive Mode (|||40711|) 150 Here comes the directory listing. -rw-r--r-- 1 110 0 338553 Oct 08 09:38 cvsup-16.1h.tbz -rw-r--r-- 1 110 0 338498 Oct 08 09:38 cvsup-without-gui-16.1h.tbz 226 Directory send OK. ftp> exit 221 Goodbye. %exit exit Script done on Sun Dec 19 15:45:46 2004 Let me know if you need more information or if you want me to test anything for you. stu From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 19 21:59: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 2877F16A4CE for ; Sun, 19 Dec 2004 21:59:48 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2E0E43D54 for ; Sun, 19 Dec 2004 21:59:47 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iBJLxltQ049134; Sun, 19 Dec 2004 13:59:47 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iBJLxhZE049129; Sun, 19 Dec 2004 13:59:43 -0800 (PST) (envelope-from obrien) Date: Sun, 19 Dec 2004 13:59:43 -0800 From: "David O'Brien" To: dev tree Message-ID: <20041219215943.GA49045@dragon.nuxi.com> References: <20041213152257.A3882@rc.tex-an.net> <20041219100920.GB7942@dragon.nuxi.com> <20041219153005.T16666@rc.tex-an.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041219153005.T16666@rc.tex-an.net> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: 5.3R cvsup failure, libm.so.2. COMPAT files missing? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 21:59:48 -0000 On Sun, Dec 19, 2004 at 03:54:10PM -0600, dev tree wrote: > On Sun, 19 Dec 2004, David O'Brien wrote: > >On Wed, Dec 15, 2004 at 05:38:09PM -0600, dev tree wrote: > >> > >>I did a fresh install of 5.3-R AMD64 from the disc1 dated > >>Nov 05 (I verified the md5 checksum), selecting "ALL" > >>under Distributions. I added package cvsup-16.1h, > >>did a buildworld and an SMP kernel, then attempted to do > >>a cvsup update along the RELENG5_3 line. > >> > >>I got the following error on a missing library file: > >> inoxidable[34]# uname -a > >> FreeBSD inoxidable.tex-an.net 5.3-RELEASE FreeBSD 5.3-RELEASE #0: > >> Wed Dec 15 13:31:38 UTC 2004 > >> root@inoxidable.tex-an.net:/usr/obj/usr/src/sys/SMP amd64 > >... > >> >>> Running /usr/local/bin/cvsup > >> -------------------------------------------------------------- > >> /libexec/ld-elf.so.1: Shared object "libm.so.2" not found, required by > >> "cvsup" > >> *** Error code 1 > > >This should be impossible. > > RCS file: /home/ncvs/ports/net/cvsup/Makefile,v > > RELEASE_5_3_0: 1.57 > > ---------------------------- > > revision 1.57 > > date: 2004/10/11 22:10:58; author: obrien; state: Exp; lines: > > +1 -0 > > Catching up with lib bumping, consume libm.so.3 on AMD64. > > ---------------------------- > > > >How did you install CVSup and what is the MD5 checksum of your distfile > >'cvsup-without-gui.amd64.tar.bz2'? > > > >hammer$ ldd /usr/local/bin/cvsup | grep libm > > libm.so.3 => /lib/libm.so.3 (0x8007f2000) > > I used cvsup16.1h, and I think I took it off the Nov 05 5.3-R disc1 CD > immediately after the system install. I had done it from the CD > on another system, then removed that and tryed again from > /stand/systinstall, prior to building inoxidable from scratch > on Dec 14 to test it with a fresh installation. The package > seems to have been from October 08. Here's whats in /var/db/pkg: I can't follow this. On the system in which you have an AMD64 cvsup using libm.so.2; how did you install CVSup? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 19 23:03:05 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 4941B16A4CE; Sun, 19 Dec 2004 23:03:05 +0000 (GMT) Received: from rc.tex-an.net (rc.tex-an.net [141.198.193.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00F6543D2F; Sun, 19 Dec 2004 23:03:05 +0000 (GMT) (envelope-from wayside@rc.tex-an.net) Received: from rc.tex-an.net (localhost.capnet.state.tx.us [127.0.0.1]) by rc.tex-an.net (8.13.1/8.13.1) with ESMTP id iBJN2Ps7017054; Sun, 19 Dec 2004 17:02:25 -0600 (CST) (envelope-from wayside@rc.tex-an.net) Received: from localhost (wayside@localhost) by rc.tex-an.net (8.13.1/8.13.1/Submit) with ESMTP id iBJN2PwS017051; Sun, 19 Dec 2004 17:02:25 -0600 (CST) (envelope-from wayside@rc.tex-an.net) Date: Sun, 19 Dec 2004 17:02:25 -0600 (CST) From: dev tree To: "David O'Brien" In-Reply-To: <20041219215943.GA49045@dragon.nuxi.com> Message-ID: <20041219160935.V16824@rc.tex-an.net> References: <20041213152257.A3882@rc.tex-an.net> <20041219100920.GB7942@dragon.nuxi.com> <20041219215943.GA49045@dragon.nuxi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-amd64@freebsd.org Subject: Re: 5.3R cvsup failure, libm.so.2. COMPAT files missing? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 23:03:05 -0000 On Sun, 19 Dec 2004, David O'Brien wrote: >>>>>>> Running /usr/local/bin/cvsup >>>> -------------------------------------------------------------- >>>> /libexec/ld-elf.so.1: Shared object "libm.so.2" not found, required by >>>> "cvsup" >>>> *** Error code 1 >> >>> This should be impossible. >>> RCS file: /home/ncvs/ports/net/cvsup/Makefile,v >>> RELEASE_5_3_0: 1.57 >>> ---------------------------- >>> revision 1.57 >>> date: 2004/10/11 22:10:58; author: obrien; state: Exp; lines: >>> +1 -0 >>> Catching up with lib bumping, consume libm.so.3 on AMD64. >>> ---------------------------- >>> >>> How did you install CVSup and what is the MD5 checksum of your distfile >>> 'cvsup-without-gui.amd64.tar.bz2'? >>> >>> hammer$ ldd /usr/local/bin/cvsup | grep libm >>> libm.so.3 => /lib/libm.so.3 (0x8007f2000) >> I used cvsup16.1h, and I think I took it off the Nov 05 5.3-R disc1 CD >> immediately after the system install. I had done it from the CD >> on another system, then removed that and tryed again from >> /stand/systinstall, prior to building inoxidable from scratch >> on Dec 14 to test it with a fresh installation. The package >> seems to have been from October 08. Here's whats in /var/db/pkg: > I can't follow this. On the system in which you have an AMD64 cvsup > using libm.so.2; how did you install CVSup? I'm pretty sure I added it from the packages on the Nov 05 5.3R disc1 CD at the end of installing the system. I know it was the only package I installed, because I built that system specifically to test the problem I was having with cvsup. Here's the md5 from the disc1 CD: MD5 (cvsup-16.1h.tbz) = 59d01df0458d4849876426499e84282a From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 20 11:02: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 08B3316A4CE for ; Mon, 20 Dec 2004 11:02:07 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB68243D1F for ; Mon, 20 Dec 2004 11:02:06 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iBKB26HP047027 for ; Mon, 20 Dec 2004 11:02:06 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iBKB26ia047021 for freebsd-amd64@freebsd.org; Mon, 20 Dec 2004 11:02:06 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 20 Dec 2004 11:02:06 GMT Message-Id: <200412201102.iBKB26ia047021@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 11:02:07 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/10/27] amd64/73211 amd64 FAST_IPSEC broken on amd64 o [2004/12/18] amd64/75209 amd64 5.3-Release panics on attempted boot from 2 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59714 amd64 device timeout and ad0: WARNING - WRITE_D 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 o [2004/10/28] amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was see o [2004/10/30] amd64/73322 amd64 unarchiving /etc to msdos fs locks up amd o [2004/11/01] amd64/73369 amd64 on-board firewire unreliable with Asus K8 o [2004/11/07] amd64/73650 amd64 5.3-release panics on boot o [2004/11/10] amd64/73775 amd64 Kernel panic (trap 12) when booting with o [2004/11/16] amd64/74014 amd64 5.3-RELEASE-AMD64 freezes on boot during o [2004/12/05] amd64/74747 amd64 System panic on shutdown when process wil 11 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/15] amd64/71753 amd64 DRI loads but fails to render on Radeon 9 o [2004/12/02] amd64/74608 amd64 mpt hangs 5 minutes when booting o [2004/12/07] amd64/74811 amd64 df, nfs mount, negative Avail -> 32/64-bi 9 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 20 11:34:18 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13F5E16A4CE for ; Mon, 20 Dec 2004 11:34:18 +0000 (GMT) Received: from fidel.freesurf.fr (fidel.freesurf.fr [212.43.206.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id B766E43D49 for ; Mon, 20 Dec 2004 11:34:17 +0000 (GMT) (envelope-from developpez@freesurf.fr) Received: from freesurf.fr (arlette.freesurf.fr [212.43.206.12]) by fidel.freesurf.fr (Postfix) with SMTP id 75B582A4C12 for ; Mon, 20 Dec 2004 12:34:16 +0100 (CET) Received: from 134.214.201.98 (SquirrelMail authenticated user freebsd2) by arlette.freesurf.fr with HTTP; Mon, 20 Dec 2004 12:34:16 +0100 (CET) Message-ID: <17481.134.214.201.98.1103542456.squirrel@arlette.freesurf.fr> Date: Mon, 20 Dec 2004 12:34:16 +0100 (CET) From: "Guillaume R." To: X-Priority: 3 In-Reply-To: <20041211004257.GD50516@dragon.nuxi.com> References: <20041211004257.GD50516@dragon.nuxi.com> Importance: Normal X-MSMail-Priority: Normal X-Mailer: SquirrelMail (version 1.2.5) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: Kernel compilation problem X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: developpez@freesurf.fr List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 11:34:18 -0000 > On Tue, Dec 07, 2004 at 06:06:21PM +0100, Guillaume R. wrote: >> > On Monday 06 December 2004 05:50 am, freebsd2@freesurf.fr wrote: >> >> Hi all! >> >> I'm very new to FreeBSD (indeed I ran it since one week) and I need >> >> to compile my kernel so that some patches will apply correctly. So >> >> I made all the process I type make depends && make and I've got sth >> >> like this: >> >> ../../../i386/i386/genassym.c:216:error: storage size of BC32SELw0 >> >> isn't known >> >> I've got that for all BC32 and furthermore on line 214 for KSPEL :( >> >> So the compilation stops on an error code. >> >> Does anyone got a clue? >> >> Many thx :) >> > >> > It means you're in the wrong directory and as a result, trying to >> > build >> > an i386 kernel on an amd64 machine with an amd64 compiler. >> > >> > You probably want to do your thing in /usr/src/sys/amd64/conf >> > and /usr/src/sys/amd64/compile/... >> I am in those directories I try again and pay attention to this. Do u >> think it's a bug or sth like that? > > You can't be doing this in /usr/src/sys/amd64/conf otherwise you would > never try to compile i386/i386/genassym.c. Exactly what are the > commands and steps you are taking in trying to build a kernel? The problem is the makefile: it's the same as the one for i386; I was very astonished when I discover that. I will try to cvsup my tree to see if I could change sth by that way -- From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 20 14:12: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 6EC7416A4CE for ; Mon, 20 Dec 2004 14:12:14 +0000 (GMT) Received: from smtp-vbr13.xs4all.nl (smtp-vbr13.xs4all.nl [194.109.24.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1B5B43D31 for ; Mon, 20 Dec 2004 14:12:13 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr13.xs4all.nl (8.12.11/8.12.11) with ESMTP id iBKECC2f037231 for ; Mon, 20 Dec 2004 15:12:12 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id EFE246486; Mon, 20 Dec 2004 15:13:22 +0100 (CET) Date: Mon, 20 Dec 2004 15:13:22 +0100 From: Roland Smith To: freebsd-amd64@freebsd.org Message-ID: <20041220141322.GA8088@slackbox.xs4all.nl> Mail-Followup-To: freebsd-amd64@freebsd.org References: <200412201102.iBKB26ia047021@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bp/iNruPH9dso1Pn" Content-Disposition: inline In-Reply-To: <200412201102.iBKB26ia047021@freefall.freebsd.org> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 Organization: Me, organized? X-Virus-Scanned: by XS4ALL Virus Scanner Subject: Re: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 14:12:14 -0000 --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 20, 2004 at 11:02:06AM +0000, FreeBSD bugmaster wrote: > o [2004/07/28] amd64/69712 amd64 no DRI (hardware OpenGL) for > ATI Radeon 9200=20 > o [2004/09/15] amd64/71753 amd64 DRI loads but fails to render > on Radeon 9200 Aren't these solved? AFAIK a patch to drm_os_freebsd.h by Jung-uk Kim was applied to CVS on december 2nd. I've applied the same fix (changing fuword and suword to fuword32 and suword32) locally and DRI works fine on my Radeon 9250 now. The official patch makes another change, using the *fence instructions for the DRM_*MEMORYBARRIER() macros. I haven't changed that yet, and it seems to work fine without it. Is this a problem? Roland --=20 R.F. Smith /"\ ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ / No HTML/RTF in email http://www.xs4all.nl/~rsmith/ X No Word docs in email / \ Respect for open standards --bp/iNruPH9dso1Pn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBxt4CEnfvsMMhpyURAt/wAJ9TXZ79+774zLKIZs5MYo+7AsfmvACcCYZw PKZZaLgbX6BFQs80OWsYgu8= =TAEi -----END PGP SIGNATURE----- --bp/iNruPH9dso1Pn-- From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 20 15:27:09 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DE6716A4CE for ; Mon, 20 Dec 2004 15:27:09 +0000 (GMT) Received: from phoenix.gargantuan.com (phoenix.gargantuan.com [24.73.171.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id B138F43D4C for ; Mon, 20 Dec 2004 15:27:08 +0000 (GMT) (envelope-from michael@gargantuan.com) Received: from localhost (localhost.gargantuan.com [127.0.0.1]) by spamassassin-injector (Postfix) with SMTP id BDBDD245 for ; Mon, 20 Dec 2004 10:27:07 -0500 (EST) Received: by phoenix.gargantuan.com (Postfix, from userid 1001) id DAD16319; Mon, 20 Dec 2004 10:26:47 -0500 (EST) Date: Mon, 20 Dec 2004 10:26:47 -0500 From: "Michael W. Oliver" To: freebsd-amd64@freebsd.org Message-ID: <20041220152647.GA31796@gargantuan.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l" Content-Disposition: inline X-WWW-Site: http://michael.gargantuan.com X-PGP-Public-Key: $X-WWW-Site/gnupg/pubkey.asc X-PGP-Fingerprint: 2694 0179 AE3F BFAE 0916 0BF5 B16B FBAB C5FA A3C9 X-Home-Phone: +1-863-816-8091 X-Mobile-Phone: +1-863-738-2334 X-Home-Address0: 8008 Apache Lane X-Home-Address1: Lakeland, FL X-Home-Address2: 33810-2172 X-Home-Address3: United States of America X-Good-Question-Guide: http://www.catb.org/~esr/faqs/smart-questions.html X-Netiquette-Guidelines: http://www.ietf.org/rfc/rfc1855.txt User-Agent: Mutt/1.5.6i X-Spam-DCC: sgs_public_dcc_server: phoenix.gargantuan.com 1199; Body=1 Fuz1=1 Fuz2=1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on phoenix.gargantuan.com X-Spam-Level: X-Spam-Status: No, score=-105.6 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, USER_IN_WHITELIST autolearn=ham version=3.0.1 X-Spam-Pyzor: Subject: fwohci init on 5.3-RELEASE blowing up X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 15:27:09 -0000 --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Good morning folks, I am having trouble here and hope that you can help. I just got a new machine here, and it is giving me fits with FreeBSD 5.3-RELEASE (amd64 ISO). I am saying that this is a fwohci issue based on the following thread on the dfly list: http://marc.theaimsgroup.com/?t=3D109967176800001&r=3D1&w=3D2 also noted in this thread: http://lists.freebsd.org/pipermail/freebsd-current/2004-November/thread.htm= l#42637 My question: Is there a way to disable firewire at the loader prompt so that I can get FreeBSD installed and cvsup to a point where this is fixed? If not, perhaps my only choice is to find a amd64 snapshot since I cannot disable firewire in the BIOS. Other suggestions welcome, thanks. --=20 Michael W. Oliver [see complete headers for contact information] --XsQoSWH+UP9D9v3l Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBxu83sWv7q8X6o8kRAgz/AJ49JOHMz6EZi7pfceirOgzPu7SuJwCffe6B 1MJD8bZZfwJoEhqG7XtwmxQ= =2tOA -----END PGP SIGNATURE----- --XsQoSWH+UP9D9v3l-- From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 20 16:27:23 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 20F1E16A4CE; Mon, 20 Dec 2004 16:27:23 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE94C43D45; Mon, 20 Dec 2004 16:27:22 +0000 (GMT) (envelope-from obrien@FreeBSD.org) Received: from freefall.freebsd.org (obrien@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iBKGRMvb095479; Mon, 20 Dec 2004 16:27:22 GMT (envelope-from obrien@freefall.freebsd.org) Received: (from obrien@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iBKGRMsM095475; Mon, 20 Dec 2004 16:27:22 GMT (envelope-from obrien) Date: Mon, 20 Dec 2004 16:27:22 GMT From: "David E. O'Brien" Message-Id: <200412201627.iBKGRMsM095475@freefall.freebsd.org> To: morgothdbma@o2.pl, obrien@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: amd64/69712: no DRI (hardware OpenGL) for ATI Radeon 9200 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 16:27:23 -0000 Synopsis: no DRI (hardware OpenGL) for ATI Radeon 9200 State-Changed-From-To: open->closed State-Changed-By: obrien State-Changed-When: Mon Dec 20 16:27:03 GMT 2004 State-Changed-Why: fixed. Thanks for the report. http://www.freebsd.org/cgi/query-pr.cgi?pr=69712 From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 20 16:27:46 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 2BEC916A4CE; Mon, 20 Dec 2004 16:27:46 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06F9143D4C; Mon, 20 Dec 2004 16:27:46 +0000 (GMT) (envelope-from obrien@FreeBSD.org) Received: from freefall.freebsd.org (obrien@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iBKGRjSk095523; Mon, 20 Dec 2004 16:27:45 GMT (envelope-from obrien@freefall.freebsd.org) Received: (from obrien@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iBKGRjIh095519; Mon, 20 Dec 2004 16:27:45 GMT (envelope-from obrien) Date: Mon, 20 Dec 2004 16:27:45 GMT From: "David E. O'Brien" Message-Id: <200412201627.iBKGRjIh095519@freefall.freebsd.org> To: bsdunx@yahoo.com, obrien@FreeBSD.org, 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: Mon, 20 Dec 2004 16:27:46 -0000 Synopsis: DRI loads but fails to render on Radeon 9200se(RV280). State-Changed-From-To: open->closed State-Changed-By: obrien State-Changed-When: Mon Dec 20 16:27:31 GMT 2004 State-Changed-Why: Fixed in drm_os_freebsd.h commit. http://www.freebsd.org/cgi/query-pr.cgi?pr=71753 From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 21 00:46:31 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFF0C16A4CE for ; Tue, 21 Dec 2004 00:46:31 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id C644243D31 for ; Tue, 21 Dec 2004 00:46:31 +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 5D1F7F217B for ; Mon, 20 Dec 2004 16:46:31 -0800 (PST) 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 01319-01 for ; Mon, 20 Dec 2004 16:46:28 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 75405F2179 for ; Mon, 20 Dec 2004 16:46:28 -0800 (PST) From: Sean McNeil To: amd64@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-RShmuNEPgrJq+IaFUWGN" Date: Mon, 20 Dec 2004 16:46:27 -0800 Message-Id: <1103589988.1529.4.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com Subject: Help try to reproduce crash X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2004 00:46:32 -0000 --=-RShmuNEPgrJq+IaFUWGN Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Could anyone help to see if they can reproduce my crash? FreeBSD server.mcneil.com 6.0-CURRENT FreeBSD 6.0-CURRENT #31: Mon Dec 20 15:54:19 PST 2004 root@server.mcneil.com:/usr/obj/usr/src/sys/AMD64 amd64 totem-0.99.22 compiled with xine, not gstreamer. xine is the default. If I do the following, I will crash my computer without any debug information whatsoever: gdb `which totem` r I have done this with dcons going and it revealed nothing at the crash. It just goes straight to rebooting. I am very interested in whether this can be reproduced on another amd64 system or an i386 -current setup. Sean --=-RShmuNEPgrJq+IaFUWGN Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBx3JjyQsGN30uGE4RAmUtAJ9vSuWVkKiJKqRb8gz7EfevnzntmQCfXXFp Xot9vCwH6TASa6xJaK7IsnY= =IXyn -----END PGP SIGNATURE----- --=-RShmuNEPgrJq+IaFUWGN-- From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 21 01:13:50 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 CADC416A4CE for ; Tue, 21 Dec 2004 01:13:50 +0000 (GMT) Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 561F743D3F for ; Tue, 21 Dec 2004 01:13:50 +0000 (GMT) (envelope-from james@jrv.org) Received: from [192.168.3.156] (zippy.housenet.jrv [192.168.3.156]) (authenticated bits=0) by mail.jrv.org (8.12.11/8.12.10) with ESMTP id iBL1Dnmc076432 for ; Mon, 20 Dec 2004 19:13:49 -0600 (CST) (envelope-from james@jrv.org) Message-ID: <41C778CD.1080602@jrv.org> Date: Mon, 20 Dec 2004 19:13:49 -0600 From: "James R. Van Artsalen" User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: /usr/games/random bug? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2004 01:13:50 -0000 5-stable "/usr/games/random -e 99" seems to always return 0, which makes it very predictable. 5.2.1 does this too. But i386 4.x seems to work as expected (an exit value between 0 and 98 inclusive). The source code line in question is return (int)((denom * random()) / LONG_MAX); the assembler code is .p2align 3 .LC17: .long 0 .long 1006632960 call random cvtsi2sdq %rax, %xmm0 mulsd 24(%rsp), %xmm0 mulsd .LC17(%rip), %xmm0 cvttsd2si %xmm0, %eax jmp .L1 I'm not familiar enough with IEEE fp rules or amd64 fp coding to say why this doesn't work, nor if this source code is even reasonable. From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 21 01:27:52 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7811116A4CE; Tue, 21 Dec 2004 01:27:52 +0000 (GMT) Received: from lakermmtao04.cox.net (lakermmtao04.cox.net [68.230.240.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id D65BF43D41; Tue, 21 Dec 2004 01:27:51 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.30.50]) by lakermmtao04.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP <20041221012745.TXVJ22354.lakermmtao04.cox.net@dolphin.local.net>; Mon, 20 Dec 2004 20:27:45 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with ESMTP id iBL1RoRE025625; Mon, 20 Dec 2004 19:27:50 -0600 (CST) (envelope-from conrads@cox.net) Date: Mon, 20 Dec 2004 19:27:45 -0600 From: "Conrad J. Sabatier" To: freebsd-amd64@freebsd.org Message-ID: <20041220192745.0e941442@dolphin.local.net> In-Reply-To: <20041219100920.GB7942@dragon.nuxi.com> References: <20041213152257.A3882@rc.tex-an.net> <20041219100920.GB7942@dragon.nuxi.com> X-Mailer: Sylpheed-Claws 0.9.13 (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: 5.3R cvsup failure, libm.so.2. COMPAT files missing? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2004 01:27:52 -0000 On Sun, 19 Dec 2004 02:09:20 -0800, "David O'Brien" wrote: > > How did you install CVSup and what is the MD5 checksum of your > distfile'cvsup-without-gui.amd64.tar.bz2'? > > hammer$ ldd /usr/local/bin/cvsup | grep libm > libm.so.3 => /lib/libm.so.3 (0x8007f2000) If you do the same command without the grep: $ ldd /usr/local/bin/cvsup /usr/local/bin/cvsup: libz.so.2 => /lib/libz.so.2 (0x8006dd000) libm.so.3 => /lib/libm.so.3 (0x8007f0000) libc.so.5 => /lib/libc.so.5 (0x80090d000) Whereas CURRENT, of course, is up to libc.so.6 now. Fortunately, I was careful not to delete the older libc when the version bump occurred. Of course, /etc/libmap.conf can always be used as a workaround, but I try to avoid that as much as possible. MD5 (/usr/ports/distfiles/cvsup-without-gui.amd64.tar.bz2) = 5e83e6b68696058ebcc4e8666e8442a9 Perhaps it's time to update the cvsup port for amd64? -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 21 01:47:54 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 05C7516A4CE for ; Tue, 21 Dec 2004 01:47:54 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAB5843D1F for ; Tue, 21 Dec 2004 01:47:53 +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 iBL1lsib014404; Mon, 20 Dec 2004 17:47:54 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iBL1ls3V014403; Mon, 20 Dec 2004 17:47:54 -0800 Date: Mon, 20 Dec 2004 17:47:54 -0800 From: Brooks Davis To: "James R. Van Artsalen" Message-ID: <20041221014754.GA13070@odin.ac.hmc.edu> References: <41C778CD.1080602@jrv.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="opJtzjQTFsWo+cga" Content-Disposition: inline In-Reply-To: <41C778CD.1080602@jrv.org> 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: /usr/games/random bug? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2004 01:47:54 -0000 --opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 20, 2004 at 07:13:49PM -0600, James R. Van Artsalen wrote: > 5-stable "/usr/games/random -e 99" seems to always return 0, which makes= =20 > it very predictable. >=20 > 5.2.1 does this too. But i386 4.x seems to work as expected (an exit=20 > value between 0 and 98 inclusive). >=20 > The source code line in question is >=20 > return (int)((denom * random()) / LONG_MAX); >=20 > the assembler code is >=20 > .p2align 3 > .LC17: > .long 0 > .long 1006632960 >=20 > call random > cvtsi2sdq %rax, %xmm0 > mulsd 24(%rsp), %xmm0 > mulsd .LC17(%rip), %xmm0 > cvttsd2si %xmm0, %eax > jmp .L1 >=20 > I'm not familiar enough with IEEE fp rules or amd64 fp coding to say why= =20 > this doesn't work, nor if this source code is even reasonable. I believe the code is bogus. The code says, compute a long (denom*random) then divide it by the largest possiable value you can store in a long. Since integer math in C truncates, the value should always be 0 unless denom*random() happens to be LONG_MAX in which case it will be 1. It's intresting that this code ever worked. A quick check indicates that this doesn not work on alpha or sparc64. Apparently no one noticed that this code has been broken for over a decade (we got it from UCB). NetBSD switched from LONG_MAX to MAXRANDOM in 2000, but apparently didn't actually read the code since it also has the bug. -- 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 --opJtzjQTFsWo+cga Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBx4DJXY6L6fI4GtQRAiT5AKDH1hBsa6xruWC4p4a0I8qNq4/wtwCghcTW OV5XfgZym8U0dIVJ3B6zbLQ= =1ANS -----END PGP SIGNATURE----- --opJtzjQTFsWo+cga-- From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 21 02:17: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 BC0A816A4CE for ; Tue, 21 Dec 2004 02:17:07 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8669143D46 for ; Tue, 21 Dec 2004 02:17:07 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iBL2H3wo084819; Mon, 20 Dec 2004 18:17:03 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iBL2H3lj084818; Mon, 20 Dec 2004 18:17:03 -0800 (PST) (envelope-from obrien) Date: Mon, 20 Dec 2004 18:17:02 -0800 From: "David O'Brien" To: "Conrad J. Sabatier" Message-ID: <20041221021702.GB83892@dragon.nuxi.com> References: <20041213152257.A3882@rc.tex-an.net> <20041219100920.GB7942@dragon.nuxi.com> <20041220192745.0e941442@dolphin.local.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041220192745.0e941442@dolphin.local.net> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: 5.3R cvsup failure, libm.so.2. COMPAT files missing? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2004 02:17:07 -0000 On Mon, Dec 20, 2004 at 07:27:45PM -0600, Conrad J. Sabatier wrote: > On Sun, 19 Dec 2004 02:09:20 -0800, "David O'Brien" > wrote: > If you do the same command without the grep: > > $ ldd /usr/local/bin/cvsup > /usr/local/bin/cvsup: > libz.so.2 => /lib/libz.so.2 (0x8006dd000) > libm.so.3 => /lib/libm.so.3 (0x8007f0000) > libc.so.5 => /lib/libc.so.5 (0x80090d000) > > Whereas CURRENT, of course, is up to libc.so.6 now. Fortunately, I was > careful not to delete the older libc when the version bump occurred. Of > course, /etc/libmap.conf can always be used as a workaround, but I try > to avoid that as much as possible. > > MD5 (/usr/ports/distfiles/cvsup-without-gui.amd64.tar.bz2) = > 5e83e6b68696058ebcc4e8666e8442a9 > > Perhaps it's time to update the cvsup port for amd64? An update would render it unusable on 5.3. Right now one can use the compat5x port (once made). -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 21 02: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 9BAB816A4CE for ; Tue, 21 Dec 2004 02:20:39 +0000 (GMT) Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3067A43D4C for ; Tue, 21 Dec 2004 02:20:39 +0000 (GMT) (envelope-from james@jrv.org) Received: from [192.168.3.156] (zippy.housenet.jrv [192.168.3.156]) (authenticated bits=0) by mail.jrv.org (8.12.11/8.12.10) with ESMTP id iBL2Kb8M077889; Mon, 20 Dec 2004 20:20:37 -0600 (CST) (envelope-from james@jrv.org) Message-ID: <41C78875.1000100@jrv.org> Date: Mon, 20 Dec 2004 20:20:37 -0600 From: "James R. Van Artsalen" User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brooks Davis References: <41C778CD.1080602@jrv.org> <20041221014754.GA13070@odin.ac.hmc.edu> In-Reply-To: <20041221014754.GA13070@odin.ac.hmc.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: /usr/games/random bug? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2004 02:20:39 -0000 Brooks Davis wrote: >> .p2align 3 >>.LC17: >> .long 0 >> .long 1006632960 >> >> call random >> cvtsi2sdq %rax, %xmm0 >> mulsd 24(%rsp), %xmm0 >> mulsd .LC17(%rip), %xmm0 >> cvttsd2si %xmm0, %eax >> jmp .L1 >> >> >I believe the code is bogus. The code says, compute a long >(denom*random) then divide it by the largest possiable value you can >store in a long. > denom is a double. random() is converted to a double and the arithmetic is floating point. It does seem odd that it works on i386 FreeBSD-4 From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 21 08:08: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 7E29216A4CE for ; Tue, 21 Dec 2004 08:08:26 +0000 (GMT) Received: from host5-111.pool80117.interbusiness.it (host5-111.pool80117.interbusiness.it [80.117.111.5]) by mx1.FreeBSD.org (Postfix) with SMTP id 229FF43D39 for ; Tue, 21 Dec 2004 08:08:25 +0000 (GMT) (envelope-from sergio@softshark.org) Received: (qmail 35961 invoked from network); 21 Dec 2004 08:17:39 -0000 Received: from aidee.softshark.home (192.168.0.2) by host1-111.pool80117.interbusiness.it with SMTP; 21 Dec 2004 08:17:39 -0000 From: Sergio Mangialardi To: freebsd-amd64@freebsd.org Content-Type: text/plain Date: Tue, 21 Dec 2004 09:06:24 +0100 Message-Id: <1103616384.28929.81.camel@aidee.softshark.home> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Problems with a Acer Aspire X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2004 08:08:26 -0000 I've recently acquired a new laptop (Acer Aspire 1524) with Athlon 64 cpu in it, so I try to install FreeBSD for AMD64 (the 5.3 version) on it. The booting process stops when the screen for boot options, i.e. Boot FreeBSD, Boot FreeBSD with ACPI disabled, etc... appears. Whatever boot option I choose the system freezes immediately (only a slash in bottom left corner appears and nothing else) and I have to reboot it. Any idea? TIA Sergio. P.S. I've read some threads about a similar problem, and even if my problem is different, I've tried to apply a patch found in them, but nothing changes. From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 21 11:36:46 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 1997B16A4CE; Tue, 21 Dec 2004 11:36:46 +0000 (GMT) Received: from lakermmtao12.cox.net (lakermmtao12.cox.net [68.230.240.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A4DE43D4C; Tue, 21 Dec 2004 11:36:45 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.30.50]) by lakermmtao12.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20041221113640.WKM1659.lakermmtao12.cox.net@dolphin.local.net>; Tue, 21 Dec 2004 06:36:40 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with ESMTP id iBLBahP6082120; Tue, 21 Dec 2004 05:36:43 -0600 (CST) (envelope-from conrads@cox.net) Date: Tue, 21 Dec 2004 05:36:38 -0600 From: "Conrad J. Sabatier" To: obrien@freebsd.org Message-ID: <20041221053638.33947b3a@dolphin.local.net> In-Reply-To: <20041221021702.GB83892@dragon.nuxi.com> References: <20041213152257.A3882@rc.tex-an.net> <20041219100920.GB7942@dragon.nuxi.com> <20041220192745.0e941442@dolphin.local.net> <20041221021702.GB83892@dragon.nuxi.com> X-Mailer: Sylpheed-Claws 0.9.13 (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: 5.3R cvsup failure, libm.so.2. COMPAT files missing? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Dec 2004 11:36:46 -0000 On Mon, 20 Dec 2004 18:17:02 -0800, "David O'Brien" wrote: > On Mon, Dec 20, 2004 at 07:27:45PM -0600, Conrad J. Sabatier wrote: > > On Sun, 19 Dec 2004 02:09:20 -0800, "David O'Brien" > > wrote: > > If you do the same command without the grep: > > > > $ ldd /usr/local/bin/cvsup > > /usr/local/bin/cvsup: > > libz.so.2 => /lib/libz.so.2 (0x8006dd000) > > libm.so.3 => /lib/libm.so.3 (0x8007f0000) > > libc.so.5 => /lib/libc.so.5 (0x80090d000) > > > > Whereas CURRENT, of course, is up to libc.so.6 now. Fortunately, I > > was careful not to delete the older libc when the version bump > > occurred. Of course, /etc/libmap.conf can always be used as a > > workaround, but I try to avoid that as much as possible. > > > > MD5 (/usr/ports/distfiles/cvsup-without-gui.amd64.tar.bz2) = > > 5e83e6b68696058ebcc4e8666e8442a9 > > > > Perhaps it's time to update the cvsup port for amd64? > > An update would render it unusable on 5.3. Right now one can use the > compat5x port (once made). What about perhaps having a separate distfile for CURRENT, with a little .if __FreeBSD_version == ... magic in the port's Makefile? I would venture to say that the majority of amd64 users are, in fact, running CURRENT. -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 23 02:33: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 1FD4516A4CE for ; Thu, 23 Dec 2004 02:33:34 +0000 (GMT) Received: from lakermmtao01.cox.net (lakermmtao01.cox.net [68.230.240.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8277643D62 for ; Thu, 23 Dec 2004 02:33:33 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.30.50]) by lakermmtao01.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP <20041223022725.ZEKC27357.lakermmtao01.cox.net@dolphin.local.net>; Wed, 22 Dec 2004 21:27:25 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with ESMTP id iBN2RU9i089056; Wed, 22 Dec 2004 20:27:30 -0600 (CST) (envelope-from conrads@cox.net) Date: Wed, 22 Dec 2004 20:27:25 -0600 From: "Conrad J. Sabatier" To: Sergio Mangialardi Message-ID: <20041222202725.3eeed629@dolphin.local.net> In-Reply-To: <1103616384.28929.81.camel@aidee.softshark.home> References: <1103616384.28929.81.camel@aidee.softshark.home> X-Mailer: Sylpheed-Claws 0.9.13 (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Problems with a Acer Aspire 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, 23 Dec 2004 02:33:34 -0000 On Tue, 21 Dec 2004 09:06:24 +0100, Sergio Mangialardi wrote: > I've recently acquired a new laptop (Acer Aspire 1524) with Athlon 64 > cpu in it, so I try to install FreeBSD for AMD64 (the 5.3 version) on > it. > The booting process stops when the screen for boot options, i.e. Boot > FreeBSD, Boot FreeBSD with ACPI disabled, etc... appears. > Whatever boot option I choose the system freezes immediately (only a > slash in bottom left corner appears and nothing else) and I have to > reboot it. > Any idea? > > TIA > > Sergio. > > P.S. > I've read some threads about a similar problem, and even if my problem > is different, I've tried to apply a patch found in them, but nothing > changes. Try choosing option 6 at the beastie menu, and then do: set hw.apic.mixed_mode=1 boot I believe the GENERIC kernel is built with mixed mode off by default, which does cause problems on some systems (including my own). I suggested a while back that it would be safer to build GENERIC without the NO_MIXED_MODE option, but nothing ever came of it. Let us know if this helps or not. -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 23 03:20:06 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 F1B7916A4CE for ; Thu, 23 Dec 2004 03:20:06 +0000 (GMT) Received: from mailout07.sul.t-online.com (mailout07.sul.t-online.com [194.25.134.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id B714343D46 for ; Thu, 23 Dec 2004 03:20:06 +0000 (GMT) (envelope-from timo-schnitzler@t-online.de) Received: from fwd01.aul.t-online.de by mailout07.sul.t-online.com with smtp id 1ChJWH-0000t2-00; Thu, 23 Dec 2004 04:20:05 +0100 Received: from [217.226.15.94] (T5w82QZYredvrdDR8Y7lo5kNYkhnkt0Y4FVwpks9Hz-uXl5B+fH7cZ@[217.226.15.94]) by fwd01.sul.t-online.com with esmtp id 1ChJW5-1b1WxE0; Thu, 23 Dec 2004 04:19:53 +0100 Message-ID: <41CA3958.4020103@t-online.de> Date: Thu, 23 Dec 2004 04:19:52 +0100 From: timo-schnitzler@t-online.de (Timo Schnitzler) User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ID: T5w82QZYredvrdDR8Y7lo5kNYkhnkt0Y4FVwpks9Hz-uXl5B+fH7cZ X-TOI-MSGID: 59c312fc-c22c-4fcf-9e55-b5bf7ee8bfb4 Subject: 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, 23 Dec 2004 03:20:07 -0000 From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 23 05:30:26 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 BE41516A4CE for ; Thu, 23 Dec 2004 05:30:26 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BB8443D5D for ; Thu, 23 Dec 2004 05:30:26 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iBN5UQTO099221 for ; Thu, 23 Dec 2004 05:30:26 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iBN5UQdB099220; Thu, 23 Dec 2004 05:30:26 GMT (envelope-from gnats) Resent-Date: Thu, 23 Dec 2004 05:30:26 GMT Resent-Message-Id: <200412230530.iBN5UQdB099220@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, Jean-Michel Philippon-Nadeau Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A74216A4CE for ; Thu, 23 Dec 2004 05:28:15 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 407CC43D48 for ; Thu, 23 Dec 2004 05:28:15 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id iBN5SE1N062783 for ; Thu, 23 Dec 2004 05:28:14 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id iBN5SEGl062781; Thu, 23 Dec 2004 05:28:14 GMT (envelope-from nobody) Message-Id: <200412230528.iBN5SEGl062781@www.freebsd.org> Date: Thu, 23 Dec 2004 05:28:14 GMT From: Jean-Michel Philippon-Nadeau To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: amd64/75417: ACPI: SATA Hard-disk 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, 23 Dec 2004 05:30:26 -0000 >Number: 75417 >Category: amd64 >Synopsis: ACPI: SATA Hard-disk >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Dec 23 05:30:25 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Jean-Michel Philippon-Nadeau >Release: 5.3-rel >Organization: XEA Technologies >Environment: FreeBSD 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov 5 03:50:01 UTC 2004 root@fanboy.samsco.home:/usr/obj/usr/src/sys/GENERIC amd64 >Description: While trying to boot normally (with ACPI) everything freezes when the system is trying to detect the SATA hard-disk. But, when we boot without ACPI, we get the same freeze, but only for a short amount of time, then, the system boots up. >How-To-Repeat: Booting with ACPI on a ASUS SK8N with the Promise Controller and a SATA Hard-drive. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 23 07:25:36 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CDC416A4CE for ; Thu, 23 Dec 2004 07:25:36 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id F068043D5D for ; Thu, 23 Dec 2004 07:25:35 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id C3AD92A90B for ; Wed, 22 Dec 2004 23:25:35 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 331A8E2B3 for ; Wed, 22 Dec 2004 23:25:35 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.1/8.13.1) with ESMTP id iBN7PYoG037653; Wed, 22 Dec 2004 23:25:34 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id iBN7PYKD037652; Wed, 22 Dec 2004 23:25:34 -0800 (PST) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Wed, 22 Dec 2004 23:25:34 -0800 User-Agent: KMail/1.7.1 References: <41C778CD.1080602@jrv.org> In-Reply-To: <41C778CD.1080602@jrv.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412222325.34375.peter@wemm.org> cc: "James R. Van Artsalen" Subject: Re: /usr/games/random bug? 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, 23 Dec 2004 07:25:36 -0000 On Monday 20 December 2004 05:13 pm, James R. Van Artsalen wrote: > 5-stable "/usr/games/random -e 99" seems to always return 0, which > makes it very predictable. > > 5.2.1 does this too. But i386 4.x seems to work as expected (an exit > value between 0 and 98 inclusive). > > The source code line in question is > > return (int)((denom * random()) / LONG_MAX); > > the assembler code is > > .p2align 3 > .LC17: > .long 0 > .long 1006632960 > > call random > cvtsi2sdq %rax, %xmm0 > mulsd 24(%rsp), %xmm0 > mulsd .LC17(%rip), %xmm0 > cvttsd2si %xmm0, %eax > jmp .L1 > > I'm not familiar enough with IEEE fp rules or amd64 fp coding to say > why this doesn't work, nor if this source code is even reasonable. The problem is a code design error and/or invalid assumptions about the range of values that random() returns.. random() returns a long. However, random()'s range is limited to 31 bits. "DESCRIPTION The random() function uses a non-linear additive feedback random number generator employing a default table of size 31 long integers to return successive pseudo-random numbers in the range from 0 to (2**31)-1. The period of this random number generator is very large, approximately 16*((2**31)-1)." Now, We're taking a 2^31 bit number, and multiplying it by some integer value, eg: 99. Then dividing the result by LONG_MAX, which is 2^62. Now, the result of (large but not so large number) divided by (much larger number (a billion times larger!)) is always = 0. Try changing the LONG_MAX in that division to INT_MAX and it will behave the same as on i386. Then we have (n * (0 .. 2^31)) / (2 ^ 31) which makes much more sense. And it even works on both 32 and 64 bit systems. -- 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 Thu Dec 23 13:28:31 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B0D716A4CE for ; Thu, 23 Dec 2004 13:28:31 +0000 (GMT) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA0D043D5E for ; Thu, 23 Dec 2004 13:28:30 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87])iBNDSTHn004905; Fri, 24 Dec 2004 00:28:29 +1100 Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) iBNDSPX6006396; Fri, 24 Dec 2004 00:28:27 +1100 Date: Fri, 24 Dec 2004 00:28:26 +1100 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Peter Wemm In-Reply-To: <200412222325.34375.peter@wemm.org> Message-ID: <20041223230006.P73466@delplex.bde.org> References: <41C778CD.1080602@jrv.org> <200412222325.34375.peter@wemm.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "James R. Van Artsalen" cc: freebsd-amd64@FreeBSD.org Subject: Re: /usr/games/random bug? 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, 23 Dec 2004 13:28:31 -0000 On Wed, 22 Dec 2004, Peter Wemm wrote: > On Monday 20 December 2004 05:13 pm, James R. Van Artsalen wrote: > > 5-stable "/usr/games/random -e 99" seems to always return 0, which > > makes it very predictable. > > > > 5.2.1 does this too. But i386 4.x seems to work as expected (an exit > > value between 0 and 98 inclusive). > > > > The source code line in question is > > > > return (int)((denom * random()) / LONG_MAX); > > > > the assembler code is > > [floating point stuff] > The problem is a code design error and/or invalid assumptions about the > range of values that random() returns.. > > random() returns a long. > However, random()'s range is limited to 31 bits. > > "DESCRIPTION > The random() function uses a non-linear additive feedback random number > generator employing a default table of size 31 long integers to return > successive pseudo-random numbers in the range from 0 to (2**31)-1. The > period of this random number generator is very large, approximately > 16*((2**31)-1)." > > Now, We're taking a 2^31 bit number, and multiplying it by some integer > value, eg: 99. Erm, we're multiplying it by some double value, e.g., 99, to extend random()'s 31-bit range. > Then dividing the result by LONG_MAX, which is 2^62. Actually ((long)(2^63 - 1)). > > Now, the result of (large but not so large number) divided by (much > larger number (a billion times larger!)) is always = 0. The result of the division is double, so it is usually nonzero, but is always >= 0 and much less than 1.0, so rounding it always gives 0 (denom is limited to 255 (should be 127) so denom * random() can't exceed 2^39 which is much less than LONG_MAX on 64-bit machines). > Try changing the LONG_MAX in that division to INT_MAX and it will behave > the same as on i386. > > Then we have (n * (0 .. 2^31)) / (2 ^ 31) which makes much more sense. > And it even works on both 32 and 64 bit systems. INT_MAX would only work accidentally. The divisor (if this simple scaling algorithm is kept) should be (RANDOM_MAX + 1), except RANDOM_MAX doesn't exist. random() unimproves on rand() in not having a macro that gives its limits. This bug has a long history in jot/jot.c: 1.1: *y = (double) random() / INT_MAX; 1.3: *y = (double) random() / LONG_MAX; 1.9: *y = (double) arc4random() / ULONG_MAX; 1.16: *y = arc4random() / ULONG_MAX; 1.17: *y = arc4random() / (double)ULONG_MAX; 1.18: *y = arc4random() / (double)UINT_MAX; 1.19: *y = arc4random() / (double)UINT32_MAX; 1.25 and current: *y = arc4random() / ((double)UINT32_MAX + 1); I.e: - 1.1 assumes 32-bit ints, which was and remains a fairly safe but bad assumption. - 1.3 assumes 32-bit longs, which is an unsafe assumption. - 1.9 moved the problem and changed the limit. arc4random() unimporoves on even random() by not documenting its maximum value, but since arc4random() returns uint32_t and indirectly claims to represent all values up to RAND_MAX, it must have a maximum value between RAND_MAX and 2^32-1. It assumes that RAND_MAX <= 2^32-1. (The spec for RAND_MAX requires that it be between 32767 and INT_MAX, so it might exceed 2^32-1 on machines with >= 33-bit ints.) Rev.1.8 assumes that uint32_t == u_long. - 1.16 completely broke the range adjustment to "fix" a warning. - 1.17 essentially backed out 1.16. - 1.18 "fixed" the scaling on 64-bit machines by essentially backing out 1.1 It assumes that uint32_t == u_int instead of that uint32_t == u_long. - 1.19 removed the assumptions in 1.18. - 1.25 fixed an unrelated bug in the scaling. random(6) has the same bug that was fixed in jot.c 1.25 -- random -e 99 can exit with a status of 99 despite it being documented to exit with a status between 0 98. It seems to be missing the scaling/uniformity bug mentioned in the log message for jot.c 1.25 -- "jot -r -w %d 1 1 4" can never give 4; its range is from 1 to 3 despite its specified range being from 1 to 4. Bruce From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 23 16:39: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 CD46916A4CE; Thu, 23 Dec 2004 16:39:44 +0000 (GMT) Received: from phoenix.gargantuan.com (phoenix.gargantuan.com [24.73.171.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DA3543D45; Thu, 23 Dec 2004 16:39:44 +0000 (GMT) (envelope-from michael@gargantuan.com) Received: from localhost (localhost.gargantuan.com [127.0.0.1]) by spamassassin-injector (Postfix) with SMTP id 457063F9; Thu, 23 Dec 2004 11:39:43 -0500 (EST) Received: by phoenix.gargantuan.com (Postfix, from userid 1001) id 4D5A536A; Thu, 23 Dec 2004 11:39:29 -0500 (EST) Date: Thu, 23 Dec 2004 11:39:29 -0500 From: "Michael W. Oliver" To: freebsd-amd64@freebsd.org Message-ID: <20041223163929.GA52351@gargantuan.com> References: <20041220152647.GA31796@gargantuan.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="82I3+IH0IqGh5yIs" Content-Disposition: inline In-Reply-To: <20041220152647.GA31796@gargantuan.com> X-WWW-Site: http://michael.gargantuan.com X-PGP-Public-Key: $X-WWW-Site/gnupg/pubkey.asc X-PGP-Fingerprint: 2694 0179 AE3F BFAE 0916 0BF5 B16B FBAB C5FA A3C9 X-Home-Phone: +1-863-816-8091 X-Mobile-Phone: +1-863-738-2334 X-Home-Address0: 8008 Apache Lane X-Home-Address1: Lakeland, FL X-Home-Address2: 33810-2172 X-Home-Address3: United States of America X-Good-Question-Guide: http://www.catb.org/~esr/faqs/smart-questions.html X-Netiquette-Guidelines: http://www.ietf.org/rfc/rfc1855.txt User-Agent: Mutt/1.5.6i X-Spam-DCC: sonic.net: phoenix.gargantuan.com 1156; Body=1 Fuz1=1 Fuz2=1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on phoenix.gargantuan.com X-Spam-Level: X-Spam-Status: No, score=-105.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, USER_IN_WHITELIST autolearn=ham version=3.0.1 X-Spam-Pyzor: Reported 0 times. cc: simokawa@freebsd.org Subject: Re: fwohci init on 5.3-RELEASE blowing up 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, 23 Dec 2004 16:39:45 -0000 --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004-12-20T10:26:47-0500, Michael W. Oliver wrote: > Good morning folks, I am having trouble here and hope that you can help. > I just got a new machine here, and it is giving me fits with FreeBSD > 5.3-RELEASE (amd64 ISO). I am saying that this is a fwohci issue based > on the following thread on the dfly list: > http://marc.theaimsgroup.com/?t=3D109967176800001&r=3D1&w=3D2 > also noted in this thread: > http://lists.freebsd.org/pipermail/freebsd-current/2004-November/thread.h= tml#42637 > My question: Is there a way to disable firewire at the loader prompt so > that I can get FreeBSD installed and cvsup to a point where this is > fixed? If not, perhaps my only choice is to find a amd64 snapshot since > I cannot disable firewire in the BIOS. > Other suggestions welcome, thanks. Anyone want to take a stab at this? I would really like to get FreeBSD installed and running on this machine. I cannot find a snapshot site that has updated snapshots post-5.3-RELEASE, and just can't get my head around building a custom release (though, I will keep trying). Here is the exact output (hand-transcribed) from booting a 5.3-RELEASE amd64 ISO: -----------------8<---------------------------------------- [...] fwohci0: mem 0xd0000000-0xd0003fff,= 0xd0008000-0xd00087ff irq 17 at device 6.0 on pci0 fwohci0: Reserved 0x800 bytes for rid 0x10 type 3 at 0xd0008000 fwohci0: [MPSAFE] fwohci0: OHCI version 1.10 (ROM=3D1) NMI ISA b0, EISA ff RAM parity error, likely hardware failure. Fatal trap 19: non-maskable interrupt trap while in kernel mode instruction pointer =3D 0x8:0xffffffff8024db66 stack pointer =3D 0x10:0xffffffff80c99950 frame pointer =3D 0x10:0xffffffff80e39000 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, IOPL =3D 0 current process =3D 0 (swapper) trap number =3D 19 panic: non-maskable interrupt trap Uptime: 1s Shutting down ACPI Automatic reboot in 15 seconds - press a key on the console to abort -----------------8<---------------------------------------- I get the same message (though with slightly different pointers) when booting the 5.3-RELEASE amd64 ISO with ACPI disabled, as well as with the FreeSBIE 1.1 i386 ISO with and without ACPI. I went to http://www.freebsd.org/releases/snapshots.html and from there to ftp://current.freebsd.org/pub/FreeBSD/snapshots/amd64/ but couldn't find anything newer than late-October. I did just now download the latest snapshot of dragonflybsd, dated 2004-12-22 (dfly-20041222-stable.iso.gz), and it will boot up without panic on fwohci. Any help at all getting 64bit FreeBSD installed and running on this machine would be most appreciated. Thanks. --=20 Michael W. Oliver [see complete headers for contact information] --82I3+IH0IqGh5yIs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFByvTBsWv7q8X6o8kRAiu/AJ9+CXILnt9B6aT0wEKI3T5Z0TDVpACdHQqC WSh9fIcFvHTX1SdGAjGETdQ= =Cl+l -----END PGP SIGNATURE----- --82I3+IH0IqGh5yIs-- From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 23 18:54:57 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25ED516A4CE for ; Thu, 23 Dec 2004 18:54:57 +0000 (GMT) Received: from host5-111.pool80117.interbusiness.it (host5-111.pool80117.interbusiness.it [80.117.111.5]) by mx1.FreeBSD.org (Postfix) with SMTP id C3A8A43D31 for ; Thu, 23 Dec 2004 18:54:55 +0000 (GMT) (envelope-from sergio@softshark.org) Received: (qmail 3603 invoked from network); 23 Dec 2004 19:04:38 -0000 Received: from aidee.softshark.home (192.168.0.2) by host1-111.pool80117.interbusiness.it with SMTP; 23 Dec 2004 19:04:38 -0000 From: Sergio Mangialardi To: FreeBSD AMD64 In-Reply-To: <20041222202725.3eeed629@dolphin.local.net> References: <1103616384.28929.81.camel@aidee.softshark.home> <20041222202725.3eeed629@dolphin.local.net> Content-Type: text/plain Date: Thu, 23 Dec 2004 19:52:28 +0100 Message-Id: <1103827948.28929.94.camel@aidee.softshark.home> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Re: Problems with a Acer Aspire 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, 23 Dec 2004 18:54:57 -0000 Conrad J. Sabatier wrote: > Try choosing option 6 at the beastie menu, and then do: > > set hw.apic.mixed_mode=1 > boot > > I believe the GENERIC kernel is built with mixed mode off by default, > which does cause problems on some systems (including my own). I > suggested a while back that it would be safer to build GENERIC without > the NO_MIXED_MODE option, but nothing ever came of it. > > Let us know if this helps or not. Thanks for your help, but unfortunately nothing changes, the system still freezes in the same manner... If it can be of help, the laptop now has FreeBSD for i386 installed. Sergio From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 23 19:31:29 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6172616A4CE for ; Thu, 23 Dec 2004 19:31:29 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F9A643D58 for ; Thu, 23 Dec 2004 19:31:29 +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 E6F95F1C63 for ; Thu, 23 Dec 2004 11:31:28 -0800 (PST) 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 00749-02 for ; Thu, 23 Dec 2004 11:31:23 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 8B8A6F1C5F for ; Thu, 23 Dec 2004 11:31:23 -0800 (PST) From: Sean McNeil To: amd64@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-mSKrG9YxHr1qj7qSXapG" Date: Thu, 23 Dec 2004 11:31:23 -0800 Message-Id: <1103830283.53421.3.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com Subject: what is the proper asm spec for xchg 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, 23 Dec 2004 19:31:29 -0000 --=-mSKrG9YxHr1qj7qSXapG Content-Type: text/plain Content-Transfer-Encoding: quoted-printable I'm looking at why audio/sdl_mixer will not compile and I see that devel/sdl12 has an include with #elif defined(__GNUC__) && defined(__x86_64__) static __inline__ Uint16 SDL_Swap16(Uint16 x) { __asm__("xchgb %b0,%h0" : "=3Dq" (x) : "0" (x)); return x; } This appears to be incorrect as it is giving errors when compiled. Does anyone more conversant with asm directives for amd64 have an idea what this should be? Thanks, Sean --=-mSKrG9YxHr1qj7qSXapG Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBByx0LyQsGN30uGE4RAlB9AJ9ioAMpi7hPFrSt2LiNp5f+XCXD1wCgxVED QSimioBcab3D1zJvh7XlOww= =p3sd -----END PGP SIGNATURE----- --=-mSKrG9YxHr1qj7qSXapG-- From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 23 20:23:06 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 18DDA16A4CE for ; Thu, 23 Dec 2004 20:23:06 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7468B43D2D for ; Thu, 23 Dec 2004 20:23:05 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 32560 invoked from network); 23 Dec 2004 20:23:05 -0000 Received: from gate.funkthat.com (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail4.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 23 Dec 2004 20:23:04 -0000 Received: from hydrogen.funkthat.com (pcryty@localhost.funkthat.com [127.0.0.1])iBNKN3GH052669; Thu, 23 Dec 2004 12:23:03 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id iBNKN2po052668; Thu, 23 Dec 2004 12:23:02 -0800 (PST) Date: Thu, 23 Dec 2004 12:23:02 -0800 From: John-Mark Gurney To: Sean McNeil Message-ID: <20041223202302.GG19624@funkthat.com> Mail-Followup-To: Sean McNeil , amd64@freebsd.org References: <1103830283.53421.3.camel@server.mcneil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1103830283.53421.3.camel@server.mcneil.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html cc: amd64@freebsd.org Subject: Re: what is the proper asm spec for xchg X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Dec 2004 20:23:06 -0000 Sean McNeil wrote this message on Thu, Dec 23, 2004 at 11:31 -0800: > I'm looking at why audio/sdl_mixer will not compile and I see that > devel/sdl12 has an include with > > #elif defined(__GNUC__) && defined(__x86_64__) > static __inline__ Uint16 SDL_Swap16(Uint16 x) > { > __asm__("xchgb %b0,%h0" : "=q" (x) : "0" (x)); > return x; > } > > This appears to be incorrect as it is giving errors when compiled. Does > anyone more conversant with asm directives for amd64 have an idea what > this should be? well, from amd64/include/endian.h: #define __byte_swap_word_var(x) \ __extension__ ({ register __uint16_t __X = (x); \ __asm ("xchgb %h0, %b0" : "+Q" (__X)); \ __X; }) -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 23 21:14:06 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 AF6A516A4CE for ; Thu, 23 Dec 2004 21:14:06 +0000 (GMT) Received: from smtp-vbr11.xs4all.nl (smtp-vbr11.xs4all.nl [194.109.24.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id F039B43D53 for ; Thu, 23 Dec 2004 21:14:05 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr11.xs4all.nl (8.12.11/8.12.11) with ESMTP id iBNLE45f041556 for ; Thu, 23 Dec 2004 22:14:04 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 63DD86127; Thu, 23 Dec 2004 22:14:04 +0100 (CET) Date: Thu, 23 Dec 2004 22:14:04 +0100 From: Roland Smith To: freebsd-amd64@freebsd.org Message-ID: <20041223211404.GB1879@slackbox.xs4all.nl> Mail-Followup-To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TakKZr9L6Hm6aLOc" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 Organization: Me, organized? X-Virus-Scanned: by XS4ALL Virus Scanner Subject: Direct rendering doesn't work with Xorg 6.8.1 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, 23 Dec 2004 21:14:06 -0000 --TakKZr9L6Hm6aLOc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable After upgrading to 6.8.1, direct rendering stopped working. According to the X logfile, direct rendering is enabled: (relevant portion from the logfile) X Window System Version 6.8.1 Release Date: 17 September 2004 X Protocol Version 11, Revision 0, Release 6.8.1 Build Operating System: FreeBSD 5.3 amd64 [ELF]=20 Current Operating System: FreeBSD slackbox.xs4all.nl 5.3-RELEASE FreeBSD 5.= 3-REL EASE #3: Thu Dec 23 20:42:25 CET 2004 rsmith@slackbox.xs4all.nl:/usr/ob= j/usr /src/sys/RFS_1 amd64 Build Date: 23 December 2004 (II) LoadModule: "glx" (II) Loading /usr/X11R6/lib/modules/extensions/libglx.a (II) Module glx: vendor=3D"X.Org Foundation" compiled for 6.8.1, module version =3D 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading sub module "GLcore" (II) LoadModule: "GLcore" (II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a (II) Module GLcore: vendor=3D"X.Org Foundation" compiled for 6.8.1, module version =3D 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading extension GLX (II) LoadModule: "dri" (II) Loading /usr/X11R6/lib/modules/extensions/libdri.a (II) Module dri: vendor=3D"X.Org Foundation" compiled for 6.8.1, module version =3D 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading sub module "drm" (II) LoadModule: "drm" (II) Loading /usr/X11R6/lib/modules/freebsd/libdrm.a (II) Module drm: vendor=3D"X.Org Foundation" compiled for 6.8.1, module version =3D 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading extension XFree86-DRI (II) Loading /usr/X11R6/lib/modules/drivers/radeon_drv.o (II) Module radeon: vendor=3D"X.Org Foundation" compiled for 6.8.1, module version =3D 4.0.1 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 0.7 (II) LoadModule: "ati" (II) Loading /usr/X11R6/lib/modules/drivers/ati_drv.o (II) Module ati: vendor=3D"X.Org Foundation" compiled for 6.8.1, module version =3D 6.5.6 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 0.7 (--) Chipset ATI Radeon 9200PRO 5960 (AGP) found drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpenByBusid: Searching for BusID pci:0000:01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpenByBusid: drmOpenMinor returns 7 drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0 (II) RADEON(0): [drm] DRM interface version 1.2 (II) RADEON(0): [drm] created "radeon" driver at busid "pci:0000:01:00.0" (II) RADEON(0): [drm] added 8192 byte SAREA at 0xffffffff80c15000 (II) RADEON(0): [drm] mapped SAREA 0xffffffff80c15000 to 0x800739000 (II) RADEON(0): [drm] framebuffer handle =3D 0xc0000000 (II) RADEON(0): [drm] added 1 reserved context for kernel (II) RADEON(0): [agp] Mode 0x1f000a0f [AGP 0x0000/0x0000; Card 0x1002/0x596= 0] (II) RADEON(0): [agp] 8192 kB allocated with handle 0xffffff002e739d00 (II) RADEON(0): [agp] ring handle =3D 0xd0000000 (II) RADEON(0): [agp] Ring mapped at 0x809090000 (II) RADEON(0): [agp] ring read ptr handle =3D 0xd0101000 (II) RADEON(0): [agp] Ring read ptr mapped at 0x80073b000 (II) RADEON(0): [agp] vertex/indirect buffers handle =3D 0xd0102000 (II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0x809191000 (II) RADEON(0): [agp] GART texture map handle =3D 0xd0302000 (II) RADEON(0): [agp] GART Texture map mapped at 0x809391000 (II) RADEON(0): [drm] register handle =3D 0xcfef0000 (II) RADEON(0): [dri] Visual configs initialized (II) RADEON(0): CP in BM mode (II) RADEON(0): Using 8 MB GART aperture (II) RADEON(0): Using 1 MB for the ring buffer (II) RADEON(0): Using 2 MB for vertex/indirect buffers (II) RADEON(0): Using 5 MB for GART textures (II) RADEON(0): Memory manager initialized to (0,0) (1280,8191) (II) RADEON(0): Reserved area from (0,1024) to (1280,1026) (II) RADEON(0): Largest offscreen area available: 1280 x 7165 (II) RADEON(0): Will use back buffer at offset 0x1400000 (II) RADEON(0): Will use depth buffer at offset 0x1900000 (II) RADEON(0): Will use 100352 kb for textures at offset 0x1e00000 (II) RADEON(0): Render acceleration enabled (II) RADEON(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles 8x8 mono pattern filled rectangles Indirect CPU to Screen color expansion Solid Lines Scanline Image Writes Offscreen Pixmaps Setting up tile and stipple cache: 32 128x128 slots 32 256x256 slots 16 512x512 slots (II) RADEON(0): Acceleration enabled (=3D=3D) RADEON(0): Backing store disabled (=3D=3D) RADEON(0): Silken mouse enabled (II) RADEON(0): Using hardware cursor (scanline 1026) (II) RADEON(0): Largest offscreen area available: 1280 x 7161 (**) Option "dpms" "true" (**) RADEON(0): DPMS enabled (II) RADEON(0): X context handle =3D 0x00000001 (II) RADEON(0): [drm] installed DRM signal handler (II) RADEON(0): [DRI] installation complete (II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers (II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers (II) RADEON(0): [drm] dma control initialized, using IRQ 16 (II) RADEON(0): [drm] Initialized kernel GART heap manager, 5111808 (II) RADEON(0): Direct rendering enabled ^ | Note especially this last line. Nevertheless, when I run glxinfo, it returns: name of display: :0.0 display: :0 screen: 0 direct rendering: _No_ server glx vendor string: SGI server glx version string: 1.2 server glx extensions: GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating,=20 GLX_EXT_import_context, GLX_OML_swap_method, GLX_SGI_make_current_read,= =20 GLX_SGIS_multisample, GLX_SGIX_fbconfig client glx vendor string: SGI client glx version string: 1.4 client glx extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,= =20 GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory,= =20 GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method,= =20 GLX_OML_sync_control, GLX_SGI_make_current_read, GLX_SGI_swap_control,= =20 GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig,=20 GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group GLX extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,= =20 GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIS_multisample OpenGL vendor string: Mesa project: www.mesa3d.org OpenGL renderer string: _Mesa GLX Indirect_ OpenGL version string: 1.2 (1.5 Mesa 6.1) I did upgrade dri: pkg_info |grep dri- dri-6.2,2 OpenGL hardware acceleration drivers for the DRI Do I have to take some special steps to get direct rendering when upgrading? Note that the AGP and radeon_drm drivers are included in the kernel. dmesg says: agp0: mem 0xd0000000-0xd3ffffff at device 0.0 on p ci0 drm0: port 0xa800-0xa8ff mem 0xcfef0000-0xcfefffff,0xc00 00000-0xc7ffffff irq 16 at device 0.0 on pci1 info: [drm] AGP at 0xd0000000 64MB info: [drm] Initialized radeon 1.11.0 20020828 on minor 0 info: [drm] Loading R200 Microcode Roland --=20 R.F. Smith /"\ ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ / No HTML/RTF in email http://www.xs4all.nl/~rsmith/ X No Word docs in email --TakKZr9L6Hm6aLOc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFByzUcEnfvsMMhpyURAtwyAKCgAs0Y8J9hwmfmGj5zye1GcdKpcACfbGPg GBIXLragTm2azyUO1IpnB1E= =Dvw4 -----END PGP SIGNATURE----- --TakKZr9L6Hm6aLOc-- From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 23 21:31:30 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85B1716A4CE for ; Thu, 23 Dec 2004 21:31:30 +0000 (GMT) Received: from priv-edtnes56.telusplanet.net (outbound01.telus.net [199.185.220.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id D270343D1D for ; Thu, 23 Dec 2004 21:31:29 +0000 (GMT) (envelope-from james@icionline.ca) Received: from [199.126.32.70] by priv-edtnes56.telusplanet.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP <20041223213129.ZXTD29427.priv-edtnes56.telusplanet.net@[199.126.32.70]>; Thu, 23 Dec 2004 14:31:29 -0700 Message-ID: <41CB38F3.5050804@icionline.ca> Date: Thu, 23 Dec 2004 14:30:27 -0700 From: James Earl User-Agent: Mozilla Thunderbird 1.0 (X11/20041217) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Roland Smith References: <20041223211404.GB1879@slackbox.xs4all.nl> In-Reply-To: <20041223211404.GB1879@slackbox.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Direct rendering doesn't work with Xorg 6.8.1 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, 23 Dec 2004 21:31:30 -0000 Roland Smith wrote: > After upgrading to 6.8.1, direct rendering stopped working. According to > the X logfile, direct rendering is enabled: > > (relevant portion from the logfile) > > Roland Same here. I also had this problem with 6.7.0. http://lists.freebsd.org/pipermail/freebsd-amd64/2004-December/002811.html It does feels like DRI is still working (at least 2D)... I haven't tested any OpenGL apps though. James From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 23 22:04: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 DA4E516A4CE for ; Thu, 23 Dec 2004 22:04:20 +0000 (GMT) Received: from smtp812.mail.ukl.yahoo.com (smtp812.mail.ukl.yahoo.com [217.12.12.202]) by mx1.FreeBSD.org (Postfix) with SMTP id 2CEB743D1F for ; Thu, 23 Dec 2004 22:04:20 +0000 (GMT) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: from unknown (HELO w2fzz0vc01.aah-go-on.com) (thomas.sparrevohn@hg1.btinternet.com@81.157.164.165 with plain) by smtp812.mail.ukl.yahoo.com with SMTP; 23 Dec 2004 22:04:19 -0000 From: Thomas Sparrevohn To: freebsd-amd64@freebsd.org Date: Thu, 23 Dec 2004 22:04:04 +0000 User-Agent: KMail/1.7.2 References: <20041223211404.GB1879@slackbox.xs4all.nl> <41CB38F3.5050804@icionline.ca> In-Reply-To: <41CB38F3.5050804@icionline.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412232204.05090.Thomas.Sparrevohn@btinternet.com> Subject: Re: Direct rendering doesn't work with Xorg 6.8.1 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Thomas.Sparrevohn@btinternet.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Dec 2004 22:04:21 -0000 On Thursday 23 December 2004 21:30, James Earl wrote: > Roland Smith wrote: > > After upgrading to 6.8.1, direct rendering stopped working. According to > > the X logfile, direct rendering is enabled: > > > > (relevant portion from the logfile) > > > > Roland > > Same here. I also had this problem with 6.7.0. > > http://lists.freebsd.org/pipermail/freebsd-amd64/2004-December/002811.html > > It does feels like DRI is still working (at least 2D)... I haven't > tested any OpenGL apps though. > > JamesdrmOpenDevice: Open failed drmOpenDevice: minor is 2 drmOpenDevice: node name is /dev/dri/card2 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenDevice: minor is 3 drmOpenDevice: node name is /dev/dri/card3 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenDevice: minor is 4 drmOpenDevice: node name is /dev/dri/card4 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenDevice: minor is 5 drmOpenDevice: node name is /dev/dri/card5 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenDevice: minor is 6 drmOpenDevice: node name is /dev/dri/card6 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenDevice: minor is 7 drmOpenDevice: node name is /dev/dri/card7 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenDevice: minor is 8 drmOpenDevice: node name is /dev/dri/card8 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenDevice: minor is 9 drmOpenDevice: node name is /dev/dri/card9 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenDevice: minor is 10 drmOpenDevice: node name is /dev/dri/card10 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenDevice: minor is 11 up to card15 - I in the middle of upgrading and see how it goes (PS. I am running Current - cvsup'ed yeaterday late I have been having the same problem with 6.7.0 e.g. with a Radeon Mobility 7500 - It seems that the DRI driver does not load e.g. From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 23 23:19:09 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9963316A4CE for ; Thu, 23 Dec 2004 23:19:09 +0000 (GMT) Received: from smtp-vbr8.xs4all.nl (smtp-vbr8.xs4all.nl [194.109.24.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFBD143D31 for ; Thu, 23 Dec 2004 23:19:08 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr8.xs4all.nl (8.12.11/8.12.11) with ESMTP id iBNNJ7N4067560 for ; Fri, 24 Dec 2004 00:19:07 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 8BBE36259; Fri, 24 Dec 2004 00:19:07 +0100 (CET) Date: Fri, 24 Dec 2004 00:19:07 +0100 From: Roland Smith To: freebsd-amd64@freebsd.org Message-ID: <20041223231907.GA4623@slackbox.xs4all.nl> Mail-Followup-To: freebsd-amd64@freebsd.org References: <20041223211404.GB1879@slackbox.xs4all.nl> <41CB38F3.5050804@icionline.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sm4nu43k4a2Rpi4c" Content-Disposition: inline In-Reply-To: <41CB38F3.5050804@icionline.ca> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 Organization: Me, organized? X-Virus-Scanned: by XS4ALL Virus Scanner Subject: Re: Direct rendering doesn't work with Xorg 6.8.1 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, 23 Dec 2004 23:19:09 -0000 --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 23, 2004 at 02:30:27PM -0700, James Earl wrote: > Roland Smith wrote: > >After upgrading to 6.8.1, direct rendering stopped working. According to > >the X logfile, direct rendering is enabled: > > > >(relevant portion from the logfile) > > > >Roland >=20 > Same here. I also had this problem with 6.7.0. >=20 > http://lists.freebsd.org/pipermail/freebsd-amd64/2004-December/002811.html >=20 > It does feels like DRI is still working (at least 2D)... I haven't=20 > tested any OpenGL apps though. AFAIK, DRI is only concerned with 3D. It has little or nothing to do with the 2D drivers.=20 It used to work for me on 6.7.0, after fixing /usr/src/sys/dev/drm/drm_os_freebsd.h. I removed xorg 6.8.1 and dri, and installed the old 6.7.0 packages from the CD, but that didn't fix the problem. :-( Is there some other package I should have removed/replaced? Roland --=20 R.F. Smith /"\ ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ / No HTML/RTF in email http://www.xs4all.nl/~rsmith/ X No Word docs in email / \ Respect for open standards --sm4nu43k4a2Rpi4c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBy1JrEnfvsMMhpyURAhpcAJ93sAbUN60r/x3Qiel3jbvk0H+DlACfUyEx r9UwYN1s70C4qrpe9AJ2Pfo= =5S2F -----END PGP SIGNATURE----- --sm4nu43k4a2Rpi4c-- From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 24 00:11: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 4E61E16A4CE for ; Fri, 24 Dec 2004 00:11:33 +0000 (GMT) Received: from mxsf28.cluster1.charter.net (mxsf28.cluster1.charter.net [209.225.28.228]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC00143D46 for ; Fri, 24 Dec 2004 00:11:32 +0000 (GMT) (envelope-from tarkawebfoot@charter.net) Received: from mxip09.cluster1.charter.net (mxip09a.cluster1.charter.net [209.225.28.139])iBO0BTDq004141 for ; Thu, 23 Dec 2004 19:11:29 -0500 Received: from 66-169-225-54.or.charter.com (HELO [10.0.1.3]) (66.169.225.54) by mxip09.cluster1.charter.net with ESMTP; 23 Dec 2004 19:11:29 -0500 X-Ironport-AV: i="3.88,85,1102309200"; d="scan'208"; a="500735267:sNHT12772868" Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Message-Id: <5B1511FA-5540-11D9-AF1F-000A95B96642@charter.net> Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-amd64@freebsd.org From: Brian Myers Date: Thu, 23 Dec 2004 16:11:27 -0800 X-Mailer: Apple Mail (2.619) Subject: New board for a newbie X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Dec 2004 00:11:33 -0000 Hi all, I've decided to get my first dual processor system, and would like to do a dual Opteron. I've run FreeBSD before and had mixed results with it. Everything ran well for a long time; the only trouble I had was upgrading software. I am a competent developer, but not a Unix guru. Eventually the port upgrade process broke and I couldn't upgrade ports any more, and the problems were way too complicated for me to figure out. This is really bad since I have a production web site running on this machine. I was, however, really impressed by the fact that that box is so rock stable. The ports broke about 2 years ago and that box is still running strong today (FreeBSD 4.4). This year I purchased my first Mac and have been impressed in a big way with Mac OS/X. I've gotten almost all of the open source software I use installed on Darwin thru DarwinPorts which works much like FreeBSD ports. I also am stronger in my understanding of Unix, so I'm thinking about giving FreeBSD another try. I'm definitely going with a 64 bit OS, so it's either FreeBSD AMD-64, or Debian - AMD 64. So I have two questions for the list members here: 1) What do you see as the pros/cons of FreeBSD AMD-64 over Debian for a dual Opteron system? and 2) I've seen much conversation on which boards, memory, and SATA controllers were supported by FreeBSD. So much so that I have no idea what the current state of things is. So, if you were building a new dual Opteron from scratch, what would you get? For cost reasons, I'm going with 1.8 ghz processors and probably only 2GB of ram. I'll have two RAID 1 SATA hard drives, but should I use an onboard controller, or purchase a separate controller? Note that I may at some point upgrade to 4 RAID 0+1 disks. What about video cards? I don't need much so, are the onboard ones useable or not? Also, I, of course, would like the onboard LAN controller to be supported. Hope this generates some interesting conversation. Thanx to anyone who answers, Brian From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 24 02:03:04 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 ED84A16A4CE for ; Fri, 24 Dec 2004 02:03:04 +0000 (GMT) Received: from postman.riken.go.jp (postman.riken.go.jp [134.160.33.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8492743D45 for ; Fri, 24 Dec 2004 02:03:03 +0000 (GMT) (envelope-from sty@iki.fi) Received: (qmail 36907 invoked by uid 85); 24 Dec 2004 02:02:58 -0000 Received: from sty@iki.fi by postman-smtp1.riken.go.jp by uid 82 with qmail-scanner-1.12 (sweep: 2.10/3.60. . Clear:. Processed in 1.754778 secs); 24 Dec 2004 02:02:58 -0000 Received: from unknown (HELO ?172.16.112.232?) (134.160.173.1) by postman.riken.go.jp with AES256-SHA encrypted SMTP; 24 Dec 2004 02:02:57 -0000 Message-ID: <41CB78D0.4060101@iki.fi> Date: Fri, 24 Dec 2004 11:02:56 +0900 From: =?ISO-8859-1?Q?Tommi_L=E4tti?= User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brian Myers References: <5B1511FA-5540-11D9-AF1F-000A95B96642@charter.net> In-Reply-To: <5B1511FA-5540-11D9-AF1F-000A95B96642@charter.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: New board for a newbie X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Dec 2004 02:03:05 -0000 Brian Myers wrote: > 2) I've seen much conversation on which boards, memory, and SATA > controllers were supported by FreeBSD. So much so that I have no idea > what the current state of things is. So, if you were building a new dual > Opteron from scratch, what would you get? For cost reasons, I'm going > with 1.8 ghz processors and probably only 2GB of ram. I'll have two RAID > 1 SATA hard drives, but should I use an onboard controller, or purchase > a separate controller? Note that I may at some point upgrade to 4 RAID > 0+1 disks. What about video cards? I don't need much so, are the onboard > ones useable or not? Also, I, of course, would like the onboard LAN > controller to be supported. Well, I just went from dual p3 to dual opteron. The machine is in housing facility and has been rock solid since it's installation 2 months ago. For MB I used Tyan K8S Pro. Not the cheapest one around but I require stability and Tyan uses good components. Memory is 4x512M ECC Reg from Kingston. The memory modules were listed on AMD website (the same series was listed...). I also got 2x37G Barracudas (SATA) and used the boards SATA controller to attach them. I then used gmirror to build raid-1 out of them. Booting from that array works just nicely. As the machine is in housing, I really don't care about video controller, the integrated one serves just nicely as the console video. All three of the on-board NIC's are usable. Don't know about gigabit performance since I didn't need one. -- br, Sty From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 24 07:03:52 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E285E16A4CE; Fri, 24 Dec 2004 07:03:52 +0000 (GMT) Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F2C043D31; Fri, 24 Dec 2004 07:03:52 +0000 (GMT) (envelope-from james@jrv.org) Received: from [192.168.3.156] (zippy.housenet.jrv [192.168.3.156]) (authenticated bits=0) by mail.jrv.org (8.12.11/8.12.10) with ESMTP id iBO73m3Y074895; Fri, 24 Dec 2004 01:03:48 -0600 (CST) (envelope-from james@jrv.org) Message-ID: <41CBBF53.6020007@jrv.org> Date: Fri, 24 Dec 2004 01:03:47 -0600 From: "James R. Van Artsalen" User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: liettneff References: <1936407230.20041214120051@bk.ru> In-Reply-To: <1936407230.20041214120051@bk.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: archie@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: mpd@amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Dec 2004 07:03:53 -0000 Mike wrote: >Hello, freebsd-amd64. > >does mpd work on amd64? it crashes with message like >pid (some huge integer), (.. - as one char)@ > > I looked at this and it crashes starting up for me too. It crashes in vprintf, within the second call to LogPrintf (), apparently while logging ordinary startup messages. I don't see any obvious cause at that point unfortunately. From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 24 11:05:31 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD4DF16A4CE for ; Fri, 24 Dec 2004 11:05:31 +0000 (GMT) Received: from smtp-vbr11.xs4all.nl (smtp-vbr11.xs4all.nl [194.109.24.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CAC343D31 for ; Fri, 24 Dec 2004 11:05:31 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr11.xs4all.nl (8.12.11/8.12.11) with ESMTP id iBOB5THn030120 for ; Fri, 24 Dec 2004 12:05:30 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id AD56F626B; Fri, 24 Dec 2004 12:05:32 +0100 (CET) Date: Fri, 24 Dec 2004 12:05:32 +0100 From: Roland Smith To: freebsd-amd64@freebsd.org Message-ID: <20041224110532.GA9753@slackbox.xs4all.nl> Mail-Followup-To: freebsd-amd64@freebsd.org References: <20041223211404.GB1879@slackbox.xs4all.nl> <41CB38F3.5050804@icionline.ca> <20041223231907.GA4623@slackbox.xs4all.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0F1p//8PRICkK4MW" Content-Disposition: inline In-Reply-To: <20041223231907.GA4623@slackbox.xs4all.nl> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 Organization: Me, organized? X-Virus-Scanned: by XS4ALL Virus Scanner Subject: Re: Direct rendering doesn't work with Xorg 6.8.1 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Dec 2004 11:05:32 -0000 --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 24, 2004 at 12:19:07AM +0100, Roland Smith wrote: > On Thu, Dec 23, 2004 at 02:30:27PM -0700, James Earl wrote: > > Roland Smith wrote: > > >After upgrading to 6.8.1, direct rendering stopped working. According = to > > >the X logfile, direct rendering is enabled: > > > > > >(relevant portion from the logfile) > > > > > >Roland > >=20 > > Same here. I also had this problem with 6.7.0. > >=20 > > http://lists.freebsd.org/pipermail/freebsd-amd64/2004-December/002811.h= tml > >=20 > > It does feels like DRI is still working (at least 2D)... I haven't=20 > > tested any OpenGL apps though. >=20 > AFAIK, DRI is only concerned with 3D. It has little or nothing to do > with the 2D drivers.=20 >=20 > It used to work for me on 6.7.0, after fixing > /usr/src/sys/dev/drm/drm_os_freebsd.h. >=20 > I removed xorg 6.8.1 and dri, and installed the old 6.7.0 packages from > the CD, but that didn't fix the problem. :-( I just found out what happened. :-) The dri package that contains the accellerated drivers was registered as installed, but hadn't actually installed the drivers.=20 Forcebly removing the dri package, and adding it again solved the problem. I discovered this by doing a ktrace on glxinfo, and then looking through the tracefile with kdump. As soon as I saw that it failed to load r200_dri.so (for my radeon card) I knew there was something wrong. And indeed /usr/X11R6/lib/modules/dri/ was empty. So now I've got 6.7.0 working again. I'll try updating to 6.8.1 after xmas. Roland --=20 R.F. Smith /"\ ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ / No HTML/RTF in email http://www.xs4all.nl/~rsmith/ X No Word docs in email / \ Respect for open standards --0F1p//8PRICkK4MW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBy/f8EnfvsMMhpyURAgrVAKCJah0m6ZISHPu7Kv76bf01eu8UbgCgjyCo 67GBA2haFKO59pF55AizRWk= =SX/F -----END PGP SIGNATURE----- --0F1p//8PRICkK4MW-- From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 24 13:03:37 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C40F116A4CE for ; Fri, 24 Dec 2004 13:03:37 +0000 (GMT) Received: from priv-edtnes28.telusplanet.net (outbound04.telus.net [199.185.220.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BFA643D4C for ; Fri, 24 Dec 2004 13:03:37 +0000 (GMT) (envelope-from james@icionline.ca) Received: from [199.126.32.70] by priv-edtnes28.telusplanet.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP <20041224130336.ETDQ7943.priv-edtnes28.telusplanet.net@[199.126.32.70]>; Fri, 24 Dec 2004 06:03:36 -0700 Message-ID: <41CC1369.9010202@icionline.ca> Date: Fri, 24 Dec 2004 06:02:33 -0700 From: James Earl User-Agent: Mozilla Thunderbird 1.0 (X11/20041217) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Roland Smith , freebsd-amd64@freebsd.org References: <20041223211404.GB1879@slackbox.xs4all.nl> <41CB38F3.5050804@icionline.ca> <20041223231907.GA4623@slackbox.xs4all.nl> <20041224110532.GA9753@slackbox.xs4all.nl> In-Reply-To: <20041224110532.GA9753@slackbox.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Direct rendering doesn't work with Xorg 6.8.1 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Dec 2004 13:03:37 -0000 Roland Smith wrote: > On Fri, Dec 24, 2004 at 12:19:07AM +0100, Roland Smith wrote: > >>On Thu, Dec 23, 2004 at 02:30:27PM -0700, James Earl wrote: >> >>>Roland Smith wrote: >>> >>>>After upgrading to 6.8.1, direct rendering stopped working. According to >>>>the X logfile, direct rendering is enabled: >>>> >>>>(relevant portion from the logfile) >>>> >>>>Roland >>> >>>Same here. I also had this problem with 6.7.0. >>> >>>http://lists.freebsd.org/pipermail/freebsd-amd64/2004-December/002811.html >>> >>>It does feels like DRI is still working (at least 2D)... I haven't >>>tested any OpenGL apps though. >> >>AFAIK, DRI is only concerned with 3D. It has little or nothing to do >>with the 2D drivers. >> >>It used to work for me on 6.7.0, after fixing >>/usr/src/sys/dev/drm/drm_os_freebsd.h. >> >>I removed xorg 6.8.1 and dri, and installed the old 6.7.0 packages from >>the CD, but that didn't fix the problem. :-( > > > I just found out what happened. :-) The dri package that contains the > accellerated drivers was registered as installed, but hadn't actually > installed the drivers. > > Forcebly removing the dri package, and adding it again solved the problem. > > I discovered this by doing a ktrace on glxinfo, and then looking through > the tracefile with kdump. As soon as I saw that it failed to load > r200_dri.so (for my radeon card) I knew there was something wrong. And > indeed /usr/X11R6/lib/modules/dri/ was empty. > > So now I've got 6.7.0 working again. I'll try updating to 6.8.1 after > xmas. > > Roland Well, after installing graphics/dri (oops!) glxinfo still reports direct rendering: No. I am getting a warning though: (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found drm0@pci1:0:0: class=0x030000 card=0x7c13174b chip=0x59601002 rev=0x01 hdr=0x00 vendor = 'ATI Technologies Inc.' device = 'Radeon 9200 Pro (RV280)' class = display subclass = VGA none2@pci1:0:1: class=0x038000 card=0x7c12174b chip=0x59401002 rev=0x01 hdr=0x00 vendor = 'ATI Technologies Inc.' device = 'Radeon 9200 Pro (RV280) - Secondary' class = display What's this Secondary device for? James From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 24 13:26: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 A887F16A4CE for ; Fri, 24 Dec 2004 13:26:55 +0000 (GMT) Received: from smtp-vbr12.xs4all.nl (smtp-vbr12.xs4all.nl [194.109.24.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA1CE43D1D for ; Fri, 24 Dec 2004 13:26:54 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr12.xs4all.nl (8.12.11/8.12.11) with ESMTP id iBODQrFg000647 for ; Fri, 24 Dec 2004 14:26:54 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 2F945617A; Fri, 24 Dec 2004 14:26:57 +0100 (CET) Date: Fri, 24 Dec 2004 14:26:57 +0100 From: Roland Smith To: freebsd-amd64@freebsd.org Message-ID: <20041224132657.GA13792@slackbox.xs4all.nl> Mail-Followup-To: freebsd-amd64@freebsd.org References: <20041223211404.GB1879@slackbox.xs4all.nl> <41CB38F3.5050804@icionline.ca> <20041223231907.GA4623@slackbox.xs4all.nl> <20041224110532.GA9753@slackbox.xs4all.nl> <41CC1369.9010202@icionline.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1yeeQ81UyVL57Vl7" Content-Disposition: inline In-Reply-To: <41CC1369.9010202@icionline.ca> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 Organization: Me, organized? X-Virus-Scanned: by XS4ALL Virus Scanner Subject: Re: Direct rendering doesn't work with Xorg 6.8.1 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Dec 2004 13:26:55 -0000 --1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 24, 2004 at 06:02:33AM -0700, James Earl wrote: > >>I removed xorg 6.8.1 and dri, and installed the old 6.7.0 packages from > >>the CD, but that didn't fix the problem. :-( > > > > > >I just found out what happened. :-) The dri package that contains the > >accellerated drivers was registered as installed, but hadn't actually > >installed the drivers.=20 > > > >Forcebly removing the dri package, and adding it again solved the proble= m. > > > >I discovered this by doing a ktrace on glxinfo, and then looking through > >the tracefile with kdump. As soon as I saw that it failed to load > >r200_dri.so (for my radeon card) I knew there was something wrong. And > >indeed /usr/X11R6/lib/modules/dri/ was empty. > > > >So now I've got 6.7.0 working again. I'll try updating to 6.8.1 after > >xmas. > > > >Roland >=20 > Well, after installing graphics/dri (oops!) glxinfo still reports direct > rendering: No. I am getting a warning though: >=20 > (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) fo= und I get the same warning, but I don't think it matters very much, because the lines before say (in my case): (II) Primary Device is: PCI 01:00:0 (--) Assigning device section with no busID to primary device I'd guess that the warning just says, "you're not using the secondary device 1:0:1".=20 > drm0@pci1:0:0: class=3D0x030000 card=3D0x7c13174b chip=3D0x59601002 rev= =3D0x01 > hdr=3D0x00 > vendor =3D 'ATI Technologies Inc.' > device =3D 'Radeon 9200 Pro (RV280)' > class =3D display > subclass =3D VGA > none2@pci1:0:1: class=3D0x038000 card=3D0x7c12174b chip=3D0x59401002 rev= =3D0x01 > hdr=3D0x00 > vendor =3D 'ATI Technologies Inc.' > device =3D 'Radeon 9200 Pro (RV280) - Secondary' > class =3D display >=20 > What's this Secondary device for? I get more or less the same message, with a different card-id. My card has two connectors, a VGA connector and a DVI connector. I'm using the VGA connector. Maybe the second device has to do with the unused connector? Roland --=20 R.F. Smith /"\ ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ / No HTML/RTF in email http://www.xs4all.nl/~rsmith/ X No Word docs in email / \ Respect for open standards --1yeeQ81UyVL57Vl7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBzBkhEnfvsMMhpyURAoO3AKCWzyzfVv21dUj6ugnlk6i8LKSj5ACbBind mkVIlfaNb2Tnb0GvirVwBqc= =plLG -----END PGP SIGNATURE----- --1yeeQ81UyVL57Vl7-- From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 24 13:28:41 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B85316A4CE for ; Fri, 24 Dec 2004 13:28:41 +0000 (GMT) Received: from priv-edtnes84.telusplanet.net (defout.telus.net [199.185.220.240]) by mx1.FreeBSD.org (Postfix) with ESMTP id D52E243D3F for ; Fri, 24 Dec 2004 13:28:40 +0000 (GMT) (envelope-from james@icionline.ca) Received: from [199.126.32.70] by priv-edtnes84.telusplanet.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP <20041224132840.CAJB6547.priv-edtnes84.telusplanet.net@[199.126.32.70]> for ; Fri, 24 Dec 2004 06:28:40 -0700 Message-ID: <41CC194B.3040904@icionline.ca> Date: Fri, 24 Dec 2004 06:27:39 -0700 From: James Earl User-Agent: Mozilla Thunderbird 1.0 (X11/20041217) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20041223211404.GB1879@slackbox.xs4all.nl> <41CB38F3.5050804@icionline.ca> <20041223231907.GA4623@slackbox.xs4all.nl> <20041224110532.GA9753@slackbox.xs4all.nl> <41CC1369.9010202@icionline.ca> <20041224132657.GA13792@slackbox.xs4all.nl> In-Reply-To: <20041224132657.GA13792@slackbox.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Direct rendering doesn't work with Xorg 6.8.1 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Dec 2004 13:28:41 -0000 Roland Smith wrote: > On Fri, Dec 24, 2004 at 06:02:33AM -0700, James Earl wrote: > >>>>I removed xorg 6.8.1 and dri, and installed the old 6.7.0 packages from >>>>the CD, but that didn't fix the problem. :-( >>> >>> >>>I just found out what happened. :-) The dri package that contains the >>>accellerated drivers was registered as installed, but hadn't actually >>>installed the drivers. >>> >>>Forcebly removing the dri package, and adding it again solved the problem. >>> >>>I discovered this by doing a ktrace on glxinfo, and then looking through >>>the tracefile with kdump. As soon as I saw that it failed to load >>>r200_dri.so (for my radeon card) I knew there was something wrong. And >>>indeed /usr/X11R6/lib/modules/dri/ was empty. >>> >>>So now I've got 6.7.0 working again. I'll try updating to 6.8.1 after >>>xmas. >>> >>>Roland >> >>Well, after installing graphics/dri (oops!) glxinfo still reports direct >>rendering: No. I am getting a warning though: >> >>(WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found > > > I get the same warning, but I don't think it matters very much, because > the lines before say (in my case): > > (II) Primary Device is: PCI 01:00:0 > (--) Assigning device section with no busID to primary device > > I'd guess that the warning just says, "you're not using the secondary > device 1:0:1". > > >>drm0@pci1:0:0: class=0x030000 card=0x7c13174b chip=0x59601002 rev=0x01 >>hdr=0x00 >> vendor = 'ATI Technologies Inc.' >> device = 'Radeon 9200 Pro (RV280)' >> class = display >> subclass = VGA >>none2@pci1:0:1: class=0x038000 card=0x7c12174b chip=0x59401002 rev=0x01 >>hdr=0x00 >> vendor = 'ATI Technologies Inc.' >> device = 'Radeon 9200 Pro (RV280) - Secondary' >> class = display >> >>What's this Secondary device for? > > > I get more or less the same message, with a different card-id. My card > has two connectors, a VGA connector and a DVI connector. I'm using the > VGA connector. Maybe the second device has to do with the unused connector? > > Roland Hmm... I'm using the DVI connector. James From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 24 13:37:29 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0B2D16A4CE for ; Fri, 24 Dec 2004 13:37:29 +0000 (GMT) Received: from priv-edtnes57.telusplanet.net (outbound01.telus.net [199.185.220.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90D0443D39 for ; Fri, 24 Dec 2004 13:37:29 +0000 (GMT) (envelope-from james@icionline.ca) Received: from [199.126.32.70] by priv-edtnes57.telusplanet.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP <20041224133729.HIFK17601.priv-edtnes57.telusplanet.net@[199.126.32.70]> for ; Fri, 24 Dec 2004 06:37:29 -0700 Message-ID: <41CC1B59.5010705@icionline.ca> Date: Fri, 24 Dec 2004 06:36:25 -0700 From: James Earl User-Agent: Mozilla Thunderbird 1.0 (X11/20041217) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20041223211404.GB1879@slackbox.xs4all.nl> <41CB38F3.5050804@icionline.ca> <20041223231907.GA4623@slackbox.xs4all.nl> <20041224110532.GA9753@slackbox.xs4all.nl> <41CC1369.9010202@icionline.ca> <20041224132657.GA13792@slackbox.xs4all.nl> <41CC194B.3040904@icionline.ca> In-Reply-To: <41CC194B.3040904@icionline.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Direct rendering doesn't work with Xorg 6.8.1 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Dec 2004 13:37:30 -0000 James Earl wrote: > Roland Smith wrote: >> I get more or less the same message, with a different card-id. My card >> has two connectors, a VGA connector and a DVI connector. I'm using the >> VGA connector. Maybe the second device has to do with the unused >> connector? >> >> Roland > > > Hmm... I'm using the DVI connector. > > James The Secondary must just be whatever isn't being used. Anyway, as you already said it's normal... Maybe I'll have to give 6.7.0 another try now that I know to make sure I've got the dri port installed! :) (II) RADEON(0): Primary: Monitor -- TMDS Connector -- DVI-I DAC Type -- TVDAC/ExtDAC TMDS Type -- Internal DDC Type -- DVI_DDC (II) RADEON(0): Secondary: Monitor -- NONE Connector -- VGA DAC Type -- Primary TMDS Type -- NONE DDC Type -- VGA_DDC (II) RADEON(0): PLL parameters: rf=2700 rd=12 min=20000 max=40000; xclk=20000 (II) RADEON(0): DFP table revision: 4 (WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode disabled From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 24 15:43: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 922B716A4CE for ; Fri, 24 Dec 2004 15:43:53 +0000 (GMT) Received: from hal.btw23.de (reverse-213-146-119-155.dialin.kamp-dsl.de [213.146.119.155]) by mx1.FreeBSD.org (Postfix) with ESMTP id C83F143D46 for ; Fri, 24 Dec 2004 15:43:52 +0000 (GMT) (envelope-from flo@btw23.de) Received: by hal.btw23.de (Postfix, from userid 1004) id E6B6A256F0; Fri, 24 Dec 2004 16:48:00 +0100 (CET) Date: Fri, 24 Dec 2004 16:48:00 +0100 From: usenet04@rootofallevil.net To: freebsd-amd64@freebsd.org Message-ID: <20041224154800.GA14545@hal.btw23.de> Mail-Followup-To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: Linux 2.6.9 i586 X-Homepage: http://rootofallevil.net X-GPG-Key: FE3A7C44 X-Phone: +49-9231-702360 X-Phone2: +49-921-1612118 X-Mobile: +49-176-23534542 User-Agent: Mutt/1.5.6i Subject: Port: comms/obexapp X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Dec 2004 15:43:53 -0000 Hello, i just noticed, that the port comms/obexapp (for file transfers to mobiles via bluetooth) _does_ compile though it is marked as 'IGNORE' on AMD64. I just commented those Ignore lines out ;-) -- Florian Unglaub GnuPG Key ID: FE3A7C44 http://rootofallevil.net/files/flo.pub.asc No ePatents: From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 24 20:45: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 D516616A4CE; Fri, 24 Dec 2004 20:45:53 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F2C343D5D; Fri, 24 Dec 2004 20:45:53 +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 iBOKjqIG096549; Fri, 24 Dec 2004 15:45:52 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.1/8.13.1) with ESMTP id iBOKjq7k008577; Fri, 24 Dec 2004 15:45:52 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 2A5277306E; Fri, 24 Dec 2004 15:45:52 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041224204552.2A5277306E@freebsd-current.sentex.ca> Date: Fri, 24 Dec 2004 15:45:52 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/625/Fri Dec 10 12:41:57 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Scanned: ClamAV 0.80/640/Thu Dec 23 13:48:27 2004 clamav-milter version 0.80j on avscan2 X-Virus-Status: Clean X-Virus-Status: Clean 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: Fri, 24 Dec 2004 20:45:54 -0000 TB --- 2004-12-24 19:21:56 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-12-24 19:21:56 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-12-24 19:21:56 - checking out the source tree TB --- 2004-12-24 19:21:56 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2004-12-24 19:21:56 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-12-24 19:28:03 - building world (CFLAGS=-O2 -pipe) TB --- 2004-12-24 19:28:03 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-12-24 19:28:03 - /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 TB --- 2004-12-24 20:34:49 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-12-24 20:34:49 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-12-24 20:34:49 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Dec 24 20:34:50 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ipfilter/../../contrib/ipfilter/netinet/ip_fil.h:501:1: warning: "PFIL_HOOKS" redefined :6:1: warning: this is the location of the previous definition /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ipfilter/../../contrib/ipfilter/netinet/ip_fil.c: In function `fr_forgetifp': /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ipfilter/../../contrib/ipfilter/netinet/ip_fil.c:922: error: `ipf_mutex' undeclared (first use in this function) /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ipfilter/../../contrib/ipfilter/netinet/ip_fil.c:922: error: (Each undeclared identifier is reported only once /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ipfilter/../../contrib/ipfilter/netinet/ip_fil.c:922: error: for each function it appears in.) /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ipfilter/../../contrib/ipfilter/netinet/ip_fil.c: In function `ipfr_fastroute': /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ipfilter/../../contrib/ipfilter/netinet/ip_fil.c:1779: error: `ipf_rw' undeclared (first use in this function) *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys/modules/ipfilter. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys/modules. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-12-24 20:45:51 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-12-24 20:45:51 - ERROR: failed to build generic kernel TB --- 2004-12-24 20:45:51 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 24 21:30: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 E90E016A4CE; Fri, 24 Dec 2004 21:30:12 +0000 (GMT) Received: from mxsf27.cluster1.charter.net (mxsf27.cluster1.charter.net [209.225.28.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E61C43D31; Fri, 24 Dec 2004 21:30:12 +0000 (GMT) (envelope-from archie@dellroad.org) Received: from mxip13.cluster1.charter.net (mxip13a.cluster1.charter.net [209.225.28.143])iBOLUA3t014510; Fri, 24 Dec 2004 16:30:11 -0500 Received: from cable-68-113-94-164.mtv.al.charter.com (HELO InterJet.dellroad.org) (68.113.94.164) by mxip13.cluster1.charter.net with ESMTP; 24 Dec 2004 16:30:04 -0500 X-Ironport-AV: i="3.88,87,1102309200"; d="scan'208?atch'208"; a="671672043:sNHT16899320" Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.2.2.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id PAA17269; Fri, 24 Dec 2004 15:25:38 -0600 (CST) Received: from [127.0.0.1] (localhost [127.0.0.1])iBOLPaLo016830; Fri, 24 Dec 2004 15:25:37 -0600 (CST) (envelope-from archie@dellroad.org) Message-ID: <41CC8950.90803@dellroad.org> Date: Fri, 24 Dec 2004 15:25:36 -0600 From: Archie Cobbs User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041129 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "James R. Van Artsalen" References: <1936407230.20041214120051@bk.ru> <41CBBF53.6020007@jrv.org> In-Reply-To: <41CBBF53.6020007@jrv.org> Content-Type: multipart/mixed; boundary="------------050805020302010605020706" cc: archie@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: mpd@amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Dec 2004 21:30:13 -0000 This is a multi-part message in MIME format. --------------050805020302010605020706 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit James R. Van Artsalen wrote: >> Hello, freebsd-amd64. >> >> does mpd work on amd64? it crashes with message like >> pid (some huge integer), (.. - as one char)@ > > I looked at this and it crashes starting up for me too. It crashes in > vprintf, within the second call to LogPrintf (), apparently while > logging ordinary startup messages. I don't see any obvious cause at > that point unfortunately. Can you try the attached patch? Someone else on the mpd-users mailing list had a similar problem and this helped. -Archie __________________________________________________________________________ Archie Cobbs * CTO, Awarix * http://www.awarix.com --------------050805020302010605020706 Content-Type: text/plain; name="mpd.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="mpd.patch" Index: log.c =================================================================== RCS file: /cvsroot/mpd/mpd/src/log.c,v retrieving revision 1.4 retrieving revision 1.4.2.1 diff -u -r1.4 -r1.4.2.1 --- log.c 25 Nov 2002 23:51:41 -0000 1.4 +++ log.c 7 Oct 2004 22:43:31 -0000 1.4.2.1 @@ -265,17 +265,21 @@ { va_list args; - va_start(args, fmt); LogTimeStamp(logprintf); + va_start(args, fmt); vlogprintf(fmt, args); + va_end(args); + va_start(args, fmt); vlogprintf("\n", args); /* XXX args will be ignored */ + va_end(args); if (gLogOptions & LG_CONSOLE) { + va_start(args, fmt); vfprintf(stdout, fmt, args); + va_end(args); putc('\n', stdout); fflush(stdout); } - va_end(args); } /* @@ -315,12 +319,16 @@ /* Dump it */ - va_start(ap, fmt); - if (console) + if (console) { + va_start(ap, fmt); LogDoDumpBp(printf, vprintf, FALSE, bp, fmt, ap); - if (log) + va_end(ap); + } + if (log) { + va_start(ap, fmt); LogDoDumpBp(logprintf, vlogprintf, TRUE, bp, fmt, ap); - va_end(ap); + va_end(ap); + } } /* @@ -342,11 +350,16 @@ /* Dump it */ - va_start(ap, fmt); - if (console) + if (console) { + va_start(ap, fmt); LogDoDumpBuf(printf, vprintf, FALSE, buf, count, fmt, ap); - if (log) + va_end(ap); + } + if (log) { + va_start(ap, fmt); LogDoDumpBuf(logprintf, vlogprintf, TRUE, buf, count, fmt, ap); + va_end(ap); + } } /* --------------050805020302010605020706-- From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 25 08:19: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 A538A16A4CE; Sat, 25 Dec 2004 08:19:35 +0000 (GMT) Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 241EF43D31; Sat, 25 Dec 2004 08:19:35 +0000 (GMT) (envelope-from james@jrv.org) Received: from [192.168.3.156] (zippy.housenet.jrv [192.168.3.156]) (authenticated bits=0) by mail.jrv.org (8.12.11/8.12.10) with ESMTP id iBP8JSok006186; Sat, 25 Dec 2004 02:19:29 -0600 (CST) (envelope-from james@jrv.org) Message-ID: <41CD2290.7060001@jrv.org> Date: Sat, 25 Dec 2004 02:19:28 -0600 From: "James R. Van Artsalen" User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Archie Cobbs References: <1936407230.20041214120051@bk.ru> <41CBBF53.6020007@jrv.org> <41CC8950.90803@dellroad.org> In-Reply-To: <41CC8950.90803@dellroad.org> Content-Type: multipart/mixed; boundary="------------010805090104080808020407" cc: archie@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: mpd@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: Sat, 25 Dec 2004 08:19:35 -0000 This is a multi-part message in MIME format. --------------010805090104080808020407 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archie Cobbs wrote: > James R. Van Artsalen wrote: > >> I looked at this and it crashes starting up for me too. It crashes >> in vprintf, within the second call to LogPrintf (), apparently while >> logging ordinary startup messages. I don't see any obvious cause at >> that point unfortunately. > > > Can you try the attached patch? Someone else on the mpd-users mailing > list had a similar problem and this helped. Thanks, it works now. Attached is a slightly different patch. This is against the source currently in ports, and it fixes two additional questionable uses of va_start (). --------------010805090104080808020407 Content-Type: text/plain; name="pat.mpd" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="pat.mpd" --- custom.c.~1~ Tue May 4 11:12:28 2004 +++ custom.c Fri Dec 24 17:03:03 2004 @@ -141,16 +141,19 @@ if (!bund) return; - va_start(args, fmt); if (l == NULL) { for (k = 0; k < bund->n_links; k++) { - if (bund && bund->links[k]) + if (bund && bund->links[k]) { + va_start(args, fmt); RecordLinkUpDownReason2(bund->links[k], up, key, fmt, args); + va_end(args); + } } } else { + va_start(args, fmt); RecordLinkUpDownReason2(l, up, key, fmt, args); + va_end(args); } - va_end(args); } static void --- log.c.~1~ Tue May 4 11:12:28 2004 +++ log.c Fri Dec 24 16:42:52 2004 @@ -265,17 +265,21 @@ { va_list args; - va_start(args, fmt); LogTimeStamp(logprintf); + va_start(args, fmt); vlogprintf(fmt, args); + va_end(args); + va_start(args, fmt); vlogprintf("\n", args); /* XXX args will be ignored */ + va_end(args); if (gLogOptions & LG_CONSOLE) { + va_start(args, fmt); vfprintf(stdout, fmt, args); + va_end(args); putc('\n', stdout); fflush(stdout); } - va_end(args); } /* @@ -315,12 +319,16 @@ /* Dump it */ - va_start(ap, fmt); - if (console) + if (console) { + va_start(ap, fmt); LogDoDumpBp(printf, vprintf, FALSE, bp, fmt, ap); - if (log) + va_end(ap); + } + if (log) { + va_start(ap, fmt); LogDoDumpBp(logprintf, vlogprintf, TRUE, bp, fmt, ap); - va_end(ap); + va_end(ap); + } } /* @@ -342,11 +350,16 @@ /* Dump it */ - va_start(ap, fmt); - if (console) + if (console) { + va_start(ap, fmt); LogDoDumpBuf(printf, vprintf, FALSE, buf, count, fmt, ap); - if (log) + va_end(ap); + } + if (log) { + va_start(ap, fmt); LogDoDumpBuf(logprintf, vlogprintf, TRUE, buf, count, fmt, ap); + va_end(ap); + } } /* --- modem.c.~1~ Tue May 4 11:12:28 2004 +++ modem.c Fri Dec 24 17:08:54 2004 @@ -610,10 +610,12 @@ /* Concat prefix and message */ va_start(args, fmt); vsnprintf(buf, sizeof(buf), fmt, args); + va_end(args); if (*buf != ' ') snprintf(buf, sizeof(buf), "[%s] chat: ", lnk->name); else *buf = '\0'; + va_start(args, fmt); vsnprintf(buf + strlen(buf), sizeof(buf) - strlen(buf), fmt, args); va_end(args); --------------010805090104080808020407-- From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 25 10:20:02 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 B2D9916A4CE for ; Sat, 25 Dec 2004 10:20:02 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 863D943D58 for ; Sat, 25 Dec 2004 10:20:02 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iBPAK2YK016983 for ; Sat, 25 Dec 2004 10:20:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iBPAK2oY016982; Sat, 25 Dec 2004 10:20:02 GMT (envelope-from gnats) Resent-Date: Sat, 25 Dec 2004 10:20:02 GMT Resent-Message-Id: <200412251020.iBPAK2oY016982@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, Michael Lednev Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80F0216A4CE for ; Sat, 25 Dec 2004 10:17:15 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5909B43D48 for ; Sat, 25 Dec 2004 10:17:15 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id iBPAHFlt013720 for ; Sat, 25 Dec 2004 10:17:15 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id iBPAHEwV013719; Sat, 25 Dec 2004 10:17:15 GMT (envelope-from nobody) Message-Id: <200412251017.iBPAHEwV013719@www.freebsd.org> Date: Sat, 25 Dec 2004 10:17:15 GMT From: Michael Lednev To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: amd64/75488: ntfs_iconv not working 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: Sat, 25 Dec 2004 10:20:02 -0000 >Number: 75488 >Category: amd64 >Synopsis: ntfs_iconv not working on amd64 >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: Sat Dec 25 10:20:02 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Michael Lednev >Release: 5.3-STABLE >Organization: >Environment: FreeBSD comp-reaper.km.vibrators.ru 5.3-STABLE FreeBSD 5.3-STABLE #0: Sat Dec 18 16:55:36 MSK 2004 reaper@comp-reaper.km.vibrators.ru:/usr/obj/usr/src/sys/REAPER.pf amd64 >Description: when i mount ntfs partition with -C koi8-r option filesystem appears as garbage like =ppn@ab and >]`?hqo without -C option it appears normally exept russian letters are _ >How-To-Repeat: mount ntfs partition with -C koi8-r >Fix: i don't know >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 25 17:34: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 F2C9E16A4CE for ; Sat, 25 Dec 2004 17:34:33 +0000 (GMT) Received: from ns.yar.post.ru (ns.yar.post.ru [213.187.102.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEB6243D2D for ; Sat, 25 Dec 2004 17:34:32 +0000 (GMT) (envelope-from liettneff@bk.ru) Received: from gate-corbina.km.vibrators.ru (km.yar.post.ru [213.187.105.186]) by ns.yar.post.ru (8.12.9p2/8.12.9) with ESMTP id iBPHYUql017391 for ; Sat, 25 Dec 2004 20:34:31 +0300 (MSK) (envelope-from liettneff@bk.ru) Received: from 192.168.1.100 (reaper.1.168.192.in-addr.arpa [192.168.1.100] (may be forged))iBPHYNov002672 for ; Sat, 25 Dec 2004 20:34:24 +0300 (MSK) (envelope-from liettneff@bk.ru) Date: Sat, 25 Dec 2004 20:33:53 +0300 From: Michael Lednev X-Mailer: The Bat! (v2.01) Business Organization: none X-Priority: 3 (Normal) Message-ID: <9024919500.20041225203353@bk.ru> To: freebsd-amd64@freebsd.org In-Reply-To: <12524717718.20041225203032@bk.ru> References: <1936407230.20041214120051@bk.ru> <41CBBF53.6020007@jrv.org> <41CC8950.90803@dellroad.org> <12524717718.20041225203032@bk.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=Windows-1251 Content-Transfer-Encoding: 8bit Subject: Fwd: Re[2]: mpd@amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: liettneff List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Dec 2004 17:34:34 -0000 Hello, freebsd-amd64@freebsd.org. sorry, send this message only to Archie ---------- Forwarded Message ---------- From: Mike To: Archie Cobbs CC: Date: Sat, 25 Dec 2004 20:30:32 +0300 Subject: mpd@amd64 Attached: Hello, Archie. On 25 Dec 2004 ã., 0:25:36 you wrote: AC> Can you try the attached patch? Someone else on the mpd-users mailing AC> list had a similar problem and this helped. the patch help, thanks! maybe it should be committed to ports tree? -- Best regards, Mike mailto:liettneff@bk.ru ---------- End Forwarded Message ---------- -- Best regards, Michael mailto:liettneff@bk.ru From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 25 20:30: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 B57EC16A4CE for ; Sat, 25 Dec 2004 20:30:21 +0000 (GMT) Received: from mxsf34.cluster1.charter.net (mxsf34.cluster1.charter.net [209.225.28.159]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1032843D3F for ; Sat, 25 Dec 2004 20:30:21 +0000 (GMT) (envelope-from archie@dellroad.org) Received: from mxip19.cluster1.charter.net (mxip19a.cluster1.charter.net [209.225.28.149])iBPKUJlH004394 for ; Sat, 25 Dec 2004 15:30:19 -0500 Received: from cable-68-113-94-164.mtv.al.charter.com (HELO InterJet.dellroad.org) (68.113.94.164) by mxip19.cluster1.charter.net with ESMTP; 25 Dec 2004 15:30:12 -0500 X-Ironport-AV: i="3.88,87,1102309200"; d="scan'208"; a="647939786:sNHT12487914" Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.2.2.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id OAA29068; Sat, 25 Dec 2004 14:14:07 -0600 (CST) Received: from [127.0.0.1] (localhost [127.0.0.1])iBPKDvLo030184; Sat, 25 Dec 2004 14:14:03 -0600 (CST) (envelope-from archie@dellroad.org) Message-ID: <41CDCA05.3080308@dellroad.org> Date: Sat, 25 Dec 2004 14:13:57 -0600 From: Archie Cobbs User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041129 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "James R. Van Artsalen" References: <1936407230.20041214120051@bk.ru> <41CBBF53.6020007@jrv.org> <41CC8950.90803@dellroad.org> <41CD2290.7060001@jrv.org> In-Reply-To: <41CD2290.7060001@jrv.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: mpd@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: Sat, 25 Dec 2004 20:30:21 -0000 James R. Van Artsalen wrote: >>> I looked at this and it crashes starting up for me too. It crashes >>> in vprintf, within the second call to LogPrintf (), apparently while >>> logging ordinary startup messages. I don't see any obvious cause at >>> that point unfortunately. >> >> Can you try the attached patch? Someone else on the mpd-users mailing >> list had a similar problem and this helped. > > Thanks, it works now. > > Attached is a slightly different patch. This is against the source > currently in ports, and it fixes two additional questionable uses of > va_start (). Thanks.. I'll include those in the next release. -Archie __________________________________________________________________________ Archie Cobbs * CTO, Awarix * http://www.awarix.com