From owner-freebsd-amd64@FreeBSD.ORG Sun Aug 14 09:32:00 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 4CA0016A41F for ; Sun, 14 Aug 2005 09:32:00 +0000 (GMT) (envelope-from flynn@energyhq.es.eu.org) Received: from mindfields.energyhq.es.eu.org (73.Red-213-97-200.pooles.rima-tde.net [213.97.200.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BDE643D45 for ; Sun, 14 Aug 2005 09:31:55 +0000 (GMT) (envelope-from flynn@energyhq.es.eu.org) Received: from scienide.energyhq.es.eu.org (scienide.energyhq.es.eu.org [192.168.100.1]) by mindfields.energyhq.es.eu.org (Postfix) with SMTP id A6AEF123F3D for ; Sun, 14 Aug 2005 11:31:50 +0200 (CEST) Date: Sun, 14 Aug 2005 11:31:27 +0200 From: Miguel Mendez To: freebsd-amd64@freebsd.org Message-Id: <20050814113127.7d69af2b.flynn@energyhq.es.eu.org> X-Mailer: Sylpheed version 2.0.0 (GTK+ 2.6.9; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Sun__14_Aug_2005_11_31_27_+0200_9cRzp5a1M2gn2v0L" Subject: 32bit Linux dri apps on FreeBSD/amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Aug 2005 09:32:00 -0000 --Signature=_Sun__14_Aug_2005_11_31_27_+0200_9cRzp5a1M2gn2v0L Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I'm trying to run linux-enemyterritory which, incidentally is marked as 386 only, although I don't see any reason why amd64 couldn't be added to the supported arches. I've installed said port and linux_dri, linux-base-8 and linux-XFree86-libs. When trying to run et it fails when opening /dev/dri/card0. Can anybody shed some light on what's going on? I remember playing et on i386 before. Is this an AMD64-only issue? This is the relevant portion from ktrace: 66553 et.x86 NAMI "/compat/linux/dev/dri" 66553 et.x86 NAMI "/dev/dri" 66553 et.x86 RET setrlimit 0 66553 et.x86 CALL setrlimit(0xffffc890,0xffffc790,0x4c) 66553 et.x86 NAMI "/compat/linux/dev/dri/card0" 66553 et.x86 NAMI "/dev/dri/card0" 66553 et.x86 RET setrlimit 0 66553 et.x86 CALL open(0xffffc890,0x2,0) 66553 et.x86 NAMI "/compat/linux/dev/dri/card0" 66553 et.x86 NAMI "/dev/dri/card0" 66553 et.x86 RET open 8 66553 et.x86 CALL ioctl(0x8,0xc0086401 ,0xffffc990) 66553 et.x86 RET ioctl -1 errno -22 Unknown error: -22 66553 et.x86 CALL close(0x8) 66553 et.x86 RET close 0 Cheers, --=20 Miguel Mendez http://www.energyhq.es.eu.org PGP Key: 0xDC8514F1 --Signature=_Sun__14_Aug_2005_11_31_27_+0200_9cRzp5a1M2gn2v0L Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFC/w9ynLctrNyFFPERAnXbAJ9DUkFKyTfXnXwOVDrqXR2hbOhQswCfenJ7 2wFq+7nprD775SBcjqGv+kQ= =1O4F -----END PGP SIGNATURE----- --Signature=_Sun__14_Aug_2005_11_31_27_+0200_9cRzp5a1M2gn2v0L-- From owner-freebsd-amd64@FreeBSD.ORG Sun Aug 14 09:59:22 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 C097816A41F for ; Sun, 14 Aug 2005 09:59:22 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: from falcon.loomes.de (smtp.loomes.de [212.40.161.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A70643D45 for ; Sun, 14 Aug 2005 09:59:22 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: from port-212-202-34-162.dynamic.qsc.de ([212.202.34.162] helo=bsd.trippelsdorf.de) by falcon.loomes.de with asmtp (Exim 4.30) id 1E4FGr-0005Ov-Td; Sun, 14 Aug 2005 11:59:13 +0200 Date: Sun, 14 Aug 2005 11:59:12 +0200 From: Markus Trippelsdorf To: Miguel Mendez Message-ID: <20050814095912.GA651@bsd.trippelsdorf.de> References: <20050814113127.7d69af2b.flynn@energyhq.es.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050814113127.7d69af2b.flynn@energyhq.es.eu.org> User-Agent: Mutt/1.5.9i Cc: freebsd-amd64@freebsd.org Subject: Re: 32bit Linux dri apps on FreeBSD/amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Aug 2005 09:59:22 -0000 On Sun, Aug 14, 2005 at 11:31:27AM +0200, Miguel Mendez wrote: > Hi, > > I'm trying to run linux-enemyterritory which, incidentally is marked as > 386 only, although I don't see any reason why amd64 couldn't be added > to the supported arches. > > I've installed said port and linux_dri, linux-base-8 and > linux-XFree86-libs. When trying to run et it fails when > opening /dev/dri/card0. Can anybody shed some light on what's going on? > I remember playing et on i386 before. Is this an AMD64-only issue? > Yes, the 64 bit X Server and the 32 bit client use different handle sizes. The DRI people are working on this issue, see: http://dri.freedesktop.org/wiki/DrmMapHandling and https://bugs.freedesktop.org/show_bug.cgi?id=943 for further information. -- Markus From owner-freebsd-amd64@FreeBSD.ORG Sun Aug 14 11:49:00 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 4D6E216A41F for ; Sun, 14 Aug 2005 11:49:00 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr3.xs4all.nl (smtp-vbr3.xs4all.nl [194.109.24.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id C99AE43D46 for ; Sun, 14 Aug 2005 11:48:59 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr3.xs4all.nl (8.13.3/8.13.3) with ESMTP id j7EBmiFm003668; Sun, 14 Aug 2005 13:48:44 +0200 (CEST) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 5F87961BD; Sun, 14 Aug 2005 13:48:44 +0200 (CEST) Date: Sun, 14 Aug 2005 13:48:44 +0200 From: Roland Smith To: Miguel Mendez Message-ID: <20050814114844.GA58288@slackbox.xs4all.nl> Mail-Followup-To: Miguel Mendez , freebsd-amd64@freebsd.org References: <20050814113127.7d69af2b.flynn@energyhq.es.eu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FCuugMFkClbJLl1L" Content-Disposition: inline In-Reply-To: <20050814113127.7d69af2b.flynn@energyhq.es.eu.org> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-amd64@freebsd.org Subject: Re: 32bit Linux dri apps on FreeBSD/amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Aug 2005 11:49:00 -0000 --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 14, 2005 at 11:31:27AM +0200, Miguel Mendez wrote: > I've installed said port and linux_dri, linux-base-8 and > linux-XFree86-libs. When trying to run et it fails when > opening /dev/dri/card0. Can anybody shed some light on what's going on? > 66553 et.x86 CALL open(0xffffc890,0x2,0) > 66553 et.x86 NAMI "/compat/linux/dev/dri/card0" > 66553 et.x86 NAMI "/dev/dri/card0" > 66553 et.x86 RET open 8 > 66553 et.x86 CALL ioctl(0x8,0xc0086401 ,0xffffc990) > 66553 et.x86 RET ioctl -1 errno -22 Unknown error: -22 > 66553 et.x86 CALL close(0x8) > 66553 et.x86 RET close 0 It doesn't fail by opening the file, it's the ioctl call that fails. Errno 22 is EINVAL (invalid argument). The number of the ioctl can be broken down as follows (see /usr/src/sys/sys/ioccom.h, /usr/src/sys/dev/drm/drm.h and /usr/src/sys/dev/drm/drm_drv.h): 0xc0000000 =3D copy parameters in and out 0x00080000 =3D argument length <<16=20 0x00006400 =3D ioctl group <<8 0x00000001 =3D ioctl number 0x01 =3D DRM_IOCTL_GET_UNIQUE The definition of getunique is: int DRM(getunique)( DRM_IOCTL_ARGS ) { DRM_DEVICE; drm_unique_t u; DRM_COPY_FROM_USER_IOCTL( u, (drm_unique_t *)data, sizeof(u) ); if (u.unique_len >=3D dev->unique_len) { if (DRM_COPY_TO_USER(u.unique, dev->unique, dev->unique_len= )) return DRM_ERR(EFAULT); } u.unique_len =3D dev->unique_len; DRM_COPY_TO_USER_IOCTL( (drm_unique_t *)data, u, sizeof(u) ); return 0; } The DRM_IOCTL_ARGS are:=20 struct cdev *kdev, u_long cmd, caddr_t data, int flags,=20 DRM_STRUCTPROC *p, DRMFILE filp As you can see below, DRM_COPY_FROM_USER_IOCTL can return EINVAL: #define DRM_COPY_FROM_USER_IOCTL(kern, user, size) \ if ( IOCPARM_LEN(cmd) !=3D size) \ return EINVAL; \ kern =3D *user; IOCPARM_LEN(cmd) is cmd>>16 & 0x1fff, which in this case gives 8 bytes. And here is the error, I think. Because drm_unique_t is defined as: typedef struct drm_unique { size_t unique_len; /**< Length of unique */ char *unique; /**< Unique name for driver instantiation= */ } drm_unique_t; On amd64, both size_t and char* are 8 bytes. So sizeof(drm_unique_t) is 16 bytes on amd64. To fix this, the drm driver would have to know if ioctls were being made by a 32-bit program, and adjust the parameter size tests accordingly. I do not know if that is possible. Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --FCuugMFkClbJLl1L Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC/y+cEnfvsMMhpyURAthZAKCezLuXSGTyVzGds0iBgONmyTrQOwCfVCzh HdgWMAOGrMcgBmsXfV5gJNk= =hj42 -----END PGP SIGNATURE----- --FCuugMFkClbJLl1L-- From owner-freebsd-amd64@FreeBSD.ORG Sun Aug 14 16:04:49 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 329D416A41F for ; Sun, 14 Aug 2005 16:04:49 +0000 (GMT) (envelope-from adm@celeritystorm.com) Received: from mail.celeritystorm.com (mail.celeritystorm.com [213.247.62.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id C88F143D45 for ; Sun, 14 Aug 2005 16:04:48 +0000 (GMT) (envelope-from adm@celeritystorm.com) Received: by mail.celeritystorm.com (Postfix, from userid 106) id E05EB3D7BC4; Sun, 14 Aug 2005 18:15:20 +0200 (CEST) Received: from [192.168.0.1] (unknown [81.84.174.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.celeritystorm.com (Postfix) with ESMTP id AA9743D7BC2 for ; Sun, 14 Aug 2005 18:15:17 +0200 (CEST) Message-ID: <42FF6B9E.5000903@celeritystorm.com> Date: Sun, 14 Aug 2005 17:04:46 +0100 From: Hugo Silva User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040724) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20050814113127.7d69af2b.flynn@energyhq.es.eu.org> <20050814095912.GA651@bsd.trippelsdorf.de> In-Reply-To: <20050814095912.GA651@bsd.trippelsdorf.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: 32bit Linux dri apps on FreeBSD/amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Aug 2005 16:04:49 -0000 This is not related to AMD64, but will enemy territory run fine with dri ?? I have an ATI Mobility Radeon 9700 on my laptop (5.4-RELEASE) and I'd like to play there since it is a lot better than the card on my workstation, but I've been unable to, because I don't know any good opengl driver for ati/freebsd .. I've not researched about this issue for some time now, would I be able to play with decent FPS using dri? Markus Trippelsdorf wrote: >On Sun, Aug 14, 2005 at 11:31:27AM +0200, Miguel Mendez wrote: > > >>Hi, >> >>I'm trying to run linux-enemyterritory which, incidentally is marked as >>386 only, although I don't see any reason why amd64 couldn't be added >>to the supported arches. >> >>I've installed said port and linux_dri, linux-base-8 and >>linux-XFree86-libs. When trying to run et it fails when >>opening /dev/dri/card0. Can anybody shed some light on what's going on? >>I remember playing et on i386 before. Is this an AMD64-only issue? >> >> >> >Yes, the 64 bit X Server and the 32 bit client use different handle >sizes. >The DRI people are working on this issue, see: >http://dri.freedesktop.org/wiki/DrmMapHandling and >https://bugs.freedesktop.org/show_bug.cgi?id=943 >for further information. > > From owner-freebsd-amd64@FreeBSD.ORG Sun Aug 14 17:01:02 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 A092316A41F for ; Sun, 14 Aug 2005 17:01:02 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr1.xs4all.nl (smtp-vbr1.xs4all.nl [194.109.24.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 054C943D46 for ; Sun, 14 Aug 2005 17:01:01 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr1.xs4all.nl (8.13.3/8.13.3) with ESMTP id j7EH0qan024059; Sun, 14 Aug 2005 19:00:52 +0200 (CEST) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 77CCB61B9; Sun, 14 Aug 2005 19:00:52 +0200 (CEST) Date: Sun, 14 Aug 2005 19:00:52 +0200 From: Roland Smith To: Hugo Silva Message-ID: <20050814170052.GA60227@slackbox.xs4all.nl> Mail-Followup-To: Hugo Silva , freebsd-amd64@freebsd.org References: <20050814113127.7d69af2b.flynn@energyhq.es.eu.org> <20050814095912.GA651@bsd.trippelsdorf.de> <42FF6B9E.5000903@celeritystorm.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k+w/mQv8wyuph6w0" Content-Disposition: inline In-Reply-To: <42FF6B9E.5000903@celeritystorm.com> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-amd64@freebsd.org Subject: Re: 32bit Linux dri apps on FreeBSD/amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Aug 2005 17:01:02 -0000 --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 14, 2005 at 05:04:46PM +0100, Hugo Silva wrote: > This is not related to AMD64, but will enemy territory run fine with dri= =20 > ?? I have an ATI Mobility Radeon 9700 on my laptop (5.4-RELEASE) and I'd= =20 > like to play there since it is a lot better than the card on my=20 > workstation, but I've been unable to, because I don't know any good=20 > opengl driver for ati/freebsd .. I've not researched about this issue=20 > for some time now, would I be able to play with decent FPS using dri? The latest Radeon chip to be supported by open source drivers in Xorg is the 9250. There is a binary-only i386 driver for later models available from NVidia. Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --k+w/mQv8wyuph6w0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC/3jEEnfvsMMhpyURAnATAJ9jmi+AwEMcahA64rn5wG7nlj6YKgCbBa1y PRiPzOpqdsLNjHyEfgNl5Es= =AbUc -----END PGP SIGNATURE----- --k+w/mQv8wyuph6w0-- From owner-freebsd-amd64@FreeBSD.ORG Sun Aug 14 20:02:32 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org 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 A9EA016A41F; Sun, 14 Aug 2005 20:02:32 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6888543D46; Sun, 14 Aug 2005 20:02:32 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7EK2Wk7089537; Sun, 14 Aug 2005 20:02:32 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7EK2WsC089533; Sun, 14 Aug 2005 20:02:32 GMT (envelope-from linimon) Date: Sun, 14 Aug 2005 20:02:32 GMT From: Mark Linimon Message-Id: <200508142002.j7EK2WsC089533@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/84930: [msdosfs] something wrong with msdosfs on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Aug 2005 20:02:32 -0000 Old Synopsis: something wrong with msdosfs on amd64 New Synopsis: [msdosfs] something wrong with msdosfs on amd64 Responsible-Changed-From-To: freebsd-bugs->freebsd-amd64 Responsible-Changed-By: linimon Responsible-Changed-When: Sun Aug 14 20:01:59 GMT 2005 Responsible-Changed-Why: Sounds amd64-specific (or at least 64-bit specific). http://www.freebsd.org/cgi/query-pr.cgi?pr=84930 From owner-freebsd-amd64@FreeBSD.ORG Sun Aug 14 20:20:21 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org 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 7BC8416A41F for ; Sun, 14 Aug 2005 20:20:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47F5A43D48 for ; Sun, 14 Aug 2005 20:20:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7EKKLMb094929 for ; Sun, 14 Aug 2005 20:20:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7EKKLWF094928; Sun, 14 Aug 2005 20:20:21 GMT (envelope-from gnats) Date: Sun, 14 Aug 2005 20:20:21 GMT Message-Id: <200508142020.j7EKKLWF094928@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Andy Fawcett Cc: Subject: Re: kern/84930: something wrong with msdosfs on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andy Fawcett List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Aug 2005 20:20:21 -0000 The following reply was made to PR amd64/84930; it has been noted by GNATS. From: Andy Fawcett To: bug-followup@freebsd.org, mi@aldan.algebra.com Cc: Subject: Re: kern/84930: something wrong with msdosfs on amd64 Date: Sun, 14 Aug 2005 23:14:37 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508142314.38088.andy@athame.co.uk> At least here on 6.0-BETA2/amd64 it is working fine umass0: USB Mass storage, rev 2.00/2.00, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: 250MB (512000 512 byte sectors: 64H 32S/T 250C) [tap@ping Done]$ sudo mount -t msdosfs /dev/da0s1 /cdrom [tap@ping Done]$ ls -l /cdrom/ total 43820 [tap@ping Done]$ sudo touch /cdrom/test [tap@ping Done]$ ls -l /cdrom/ total 43820 -rwxr-xr-x 1 root wheel 0 Aug 14 23:08 test From owner-freebsd-amd64@FreeBSD.ORG Sun Aug 14 20:30:26 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 0886116A41F for ; Sun, 14 Aug 2005 20:30:26 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.178.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D03143D46 for ; Sun, 14 Aug 2005 20:30:24 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [217.185.89.14] (manz-d9b9590e.pool.mediaWays.net [217.185.89.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate1.zdv.Uni-Mainz.DE (Postfix) with ESMTP id F329E30005B0 for ; Sun, 14 Aug 2005 22:30:22 +0200 (CEST) Message-ID: <42FFA9D8.7010504@mail.uni-mainz.de> Date: Sun, 14 Aug 2005 22:30:16 +0200 From: "O. Hartmann" Organization: Institut =?ISO-8859-1?Q?f=FCr_Geophysik?= User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050724) 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 uni-mainz.de Subject: gcc compiler option -m64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Aug 2005 20:30:26 -0000 Hello. To make ist short: On my box (Athlon64 based machine) I run a FBSD 6.0Beta2 with no 32Bit support and I hope (but do not exactly know) the machine is 64Bit only that way without any 32Bit compatibilty. I see in some compiler hints this undocumented '-m32' or '-m64' option of gcc(1) (undocumented that way as I can not find it in the man pages) . On SPARC64 systems, the system's default gcc compiler implies '-m64'. Is this also true for AMD64 FreeBSD 6.X? My intention is to avoid compiling in some 32Bit libs by accident when compiling some C code for my scientific studies. thanks, Oliver From owner-freebsd-amd64@FreeBSD.ORG Sun Aug 14 20:54:20 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 9792216A41F for ; Sun, 14 Aug 2005 20:54:20 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr2.xs4all.nl (smtp-vbr2.xs4all.nl [194.109.24.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC85243D45 for ; Sun, 14 Aug 2005 20:54:19 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr2.xs4all.nl (8.13.3/8.13.3) with ESMTP id j7EKsIj6074488; Sun, 14 Aug 2005 22:54:19 +0200 (CEST) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id BFC9761B9; Sun, 14 Aug 2005 22:54:18 +0200 (CEST) Date: Sun, 14 Aug 2005 22:54:18 +0200 From: Roland Smith To: "O. Hartmann" Message-ID: <20050814205418.GB60825@slackbox.xs4all.nl> Mail-Followup-To: "O. Hartmann" , freebsd-amd64@freebsd.org References: <42FFA9D8.7010504@mail.uni-mainz.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EuxKj2iCbKjpUGkD" Content-Disposition: inline In-Reply-To: <42FFA9D8.7010504@mail.uni-mainz.de> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-amd64@freebsd.org Subject: Re: gcc compiler option -m64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Aug 2005 20:54:20 -0000 --EuxKj2iCbKjpUGkD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 14, 2005 at 10:30:16PM +0200, O. Hartmann wrote: > Hello. > To make ist short: On my box (Athlon64 based machine) I run a FBSD=20 > 6.0Beta2 with no 32Bit support and I hope (but do not exactly know) the= =20 > machine is 64Bit only that way without any 32Bit compatibilty. I think the install CD doesn't come with 32bit stuff. If you want to be absolutely sure, add NO_LIB32=3Dtrue to /etc/make.conf and rebuild the system. You can check the state of binaries with the file command: $ file /bin/dd /bin/dd: ELF 64-bit LSB executable, AMD x86-64, version 1 (FreeBSD),=20 for FreeBSD 5.4-CURRENT (rev 2), dynamically linked (uses shared libs),=20 stripped To find all 32-bit binaries on your system: find / -perm -100 -type f|xargs file|grep 32-bit|more > I see in some compiler hints this undocumented '-m32' or '-m64' option=20 > of gcc(1) (undocumented that way as I can not find it in the man pages)= =20 It is documented in the gcc info files. The GNU people in general don't like manpages. > . On SPARC64 systems, the system's default gcc compiler implies '-m64'.= =20 > Is this also true for AMD64 FreeBSD 6.X? Yes. --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --EuxKj2iCbKjpUGkD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC/696EnfvsMMhpyURAi+9AJ9x9sR6wkgxeP9K2ziKdmQ0ipHHLQCeNfOm 0mcXiebh/HzHbwL/J4CF43o= =qaJ6 -----END PGP SIGNATURE----- --EuxKj2iCbKjpUGkD-- From owner-freebsd-amd64@FreeBSD.ORG Sun Aug 14 21:00:37 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org 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 D1EC016A41F for ; Sun, 14 Aug 2005 21:00:37 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 826BF43D45 for ; Sun, 14 Aug 2005 21:00:37 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7EL0bQc096857 for ; Sun, 14 Aug 2005 21:00:37 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7EL0b7a096840; Sun, 14 Aug 2005 21:00:37 GMT (envelope-from gnats) Date: Sun, 14 Aug 2005 21:00:37 GMT Message-Id: <200508142100.j7EL0b7a096840@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Roland Smith Cc: Subject: [rsmith@xs4all.nl: Re: amd64/84930: [msdosfs] something wrong with msdosfs on amd64] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Roland Smith List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Aug 2005 21:00:37 -0000 The following reply was made to PR amd64/84930; it has been noted by GNATS. From: Roland Smith To: bug-followup@FreeBSD.org Cc: Subject: [rsmith@xs4all.nl: Re: amd64/84930: [msdosfs] something wrong with msdosfs on amd64] Date: Sun, 14 Aug 2005 22:56:40 +0200 --8NvZYKFJsRX2Djef Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable No problem here with msdosfs on amd64. My system: FreeBSD slackbox.xs4all.nl 5.4-STABLE FreeBSD 5.4-STABLE #0:=20 Wed Aug 10 20:25:45 CEST 2005=20 rsmith@slackbox.xs4all.nl:/usr/obj/usr/src/sys/RFS amd64 I tried a USB keydrive first: umass0: vendor 0x1005 USB Flash Drive, rev 2.00/1.00, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device=20 da0: 1.000MB/s transfers da0: 61MB (126973 512 byte sectors: 64H 32S/T 61C) Mounted OK. Deleting and adding files OK. Files checked with md5. Next I tried a compactflash card, in a SanDisk SDDR-31 reader: umass0: SanDisk Corporation ImageMate CompactFlash USB, rev 1.10/0.09, addr= 2 umass0: Get Max Lun not supported (STALLED) da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device=20 da0: 1.000MB/s transfers da0: 61MB (125441 512 byte sectors: 64H 32S/T 61C) I got some errors here: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 0 1 ea 0 0 0 1 0=20 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): MEDIUM ERROR asc:0,0 (da0:umass-sim0:0:0:0): No additional sense information This error was repeated a couple of times. But I could still mount the drive. Deleting and adding files OK. Files also checked with md5. Contact me if you need more info. Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --8NvZYKFJsRX2Djef Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC/7AIEnfvsMMhpyURApZ3AJ97wu85S/49BIpDb3mfoUt0TaZ2wACdHBj1 7SyTh9jpOpuDsIpcl/7UiLY= =tDvJ -----END PGP SIGNATURE----- --8NvZYKFJsRX2Djef-- From owner-freebsd-amd64@FreeBSD.ORG Sun Aug 14 21:00:41 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org 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 8591D16A421 for ; Sun, 14 Aug 2005 21:00:41 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BA2B43D45 for ; Sun, 14 Aug 2005 21:00:41 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7EL0fHb096867 for ; Sun, 14 Aug 2005 21:00:41 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7EL0fH2096866; Sun, 14 Aug 2005 21:00:41 GMT (envelope-from gnats) Date: Sun, 14 Aug 2005 21:00:41 GMT Message-Id: <200508142100.j7EL0fH2096866@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Mikhail Teterin Cc: Subject: Re: amd64/84930: [msdosfs] something wrong with msdosfs on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mikhail Teterin List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Aug 2005 21:00:41 -0000 The following reply was made to PR amd64/84930; it has been noted by GNATS. From: Mikhail Teterin To: bug-followup@freebsd.org Cc: rsmith@xs4all.nl, andy@athame.co.uk Subject: Re: amd64/84930: [msdosfs] something wrong with msdosfs on amd64 Date: Sun, 14 Aug 2005 16:59:08 -0400 Maybe, something is "wrong" about this particular filesystem? It was created by IRiver -- I never reformatted it. It is 40Gb, but I can extract some headers or whatever would be useful to debug this... Or, maybe, it is related to its size? Two people have responded so far with their _working_ examples, but theirs are 61Mb and 250Mb. -mi From owner-freebsd-amd64@FreeBSD.ORG Sun Aug 14 21:30:23 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org 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 CB79016A41F for ; Sun, 14 Aug 2005 21:30:23 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF73E43D5A for ; Sun, 14 Aug 2005 21:30:22 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7ELUMm8002281 for ; Sun, 14 Aug 2005 21:30:22 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7ELUMSe002280; Sun, 14 Aug 2005 21:30:22 GMT (envelope-from gnats) Date: Sun, 14 Aug 2005 21:30:22 GMT Message-Id: <200508142130.j7ELUMSe002280@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Roland Smith Cc: Subject: Re: amd64/84930: [msdosfs] something wrong with msdosfs on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Roland Smith List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Aug 2005 21:30:23 -0000 The following reply was made to PR amd64/84930; it has been noted by GNATS. From: Roland Smith To: Mikhail Teterin Cc: bug-followup@freebsd.org, andy@athame.co.uk Subject: Re: amd64/84930: [msdosfs] something wrong with msdosfs on amd64 Date: Sun, 14 Aug 2005 23:20:49 +0200 --1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 14, 2005 at 04:59:08PM -0400, Mikhail Teterin wrote: > Maybe, something is "wrong" about this particular filesystem? >=20 > It was created by IRiver -- I never reformatted it. It is 40Gb, > but I can extract some headers or whatever would be useful to > debug this... Did you get any unusual messages in the system logfiles? > Or, maybe, it is related to its size? Two people have responded so far > with their _working_ examples, but theirs are 61Mb and 250Mb. Could be, but I don't think so. IIRC, you have to have the "options MSDOSFS_LARGE" in your kernel for drives >128GB. Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --1yeeQ81UyVL57Vl7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC/7WxEnfvsMMhpyURAm8oAJ9A2khb/uidD+JvQ7wh/ouENf8FFQCgkNJM ODeOh55O0cRJoeTw7ohyjg0= =P/dM -----END PGP SIGNATURE----- --1yeeQ81UyVL57Vl7-- From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 06:18:07 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 10B5916A41F for ; Mon, 15 Aug 2005 06:18:07 +0000 (GMT) (envelope-from will+freebsd-amd64@will.iki.fi) Received: from will.iki.fi (will.iki.fi [217.169.64.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95A4E43D45 for ; Mon, 15 Aug 2005 06:18:06 +0000 (GMT) (envelope-from will+freebsd-amd64@will.iki.fi) Received: from [10.0.20.56] (fa-3-0-0.fw.exomi.com [217.169.64.99]) by will.iki.fi (Postfix) with ESMTP id DF2FC123; Mon, 15 Aug 2005 09:18:04 +0300 (EEST) Message-ID: <43003399.4040901@will.iki.fi> Date: Mon, 15 Aug 2005 09:18:01 +0300 From: Ville-Pertti Keinonen User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050721) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Roland Smith References: <20050814113127.7d69af2b.flynn@energyhq.es.eu.org> <20050814095912.GA651@bsd.trippelsdorf.de> <42FF6B9E.5000903@celeritystorm.com> <20050814170052.GA60227@slackbox.xs4all.nl> In-Reply-To: <20050814170052.GA60227@slackbox.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: 32bit Linux dri apps on FreeBSD/amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 06:18:07 -0000 Roland Smith wrote: > On Sun, Aug 14, 2005 at 05:04:46PM +0100, Hugo Silva wrote: > >>This is not related to AMD64, but will enemy territory run fine with dri >>?? I have an ATI Mobility Radeon 9700 on my laptop (5.4-RELEASE) and I'd >>like to play there since it is a lot better than the card on my >>workstation, but I've been unable to, because I don't know any good >>opengl driver for ati/freebsd .. I've not researched about this issue >>for some time now, would I be able to play with decent FPS using dri? > > > The latest Radeon chip to be supported by open source drivers in Xorg is > the 9250. There is a binary-only i386 driver for later models available There is some (incomplete) support for cards based on R300-series chips (including the Mobility 9700 aka. M10). There's some info on r300.sourceforge.net, and a FreeBSD version that seems to work is available by installing the following ports: graphics/dri-devel x11-server/xorg-server-snap It also requires -current or RELENG_6 for the kernel-side support, although backporting to 5.4 might be as simple as copying the sys/dev/drm directory. Lacking a linux_dri-devel, it won't work with Linux binaries, and the driver might not be complete enough for some games yet. Relevant to this list, it does work on FreeBSD/amd64. > from NVidia. Which obviously doesn't support later model Radeons, although it does support NVidia cards of comparable generations. But you can't usually switch graphics chipsets on a laptop... From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 08:16:54 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 B425D16A41F for ; Mon, 15 Aug 2005 08:16:54 +0000 (GMT) (envelope-from googl3meister@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EEEF43D5A for ; Mon, 15 Aug 2005 08:16:53 +0000 (GMT) (envelope-from googl3meister@gmail.com) Received: by wproxy.gmail.com with SMTP id 70so1024762wra for ; Mon, 15 Aug 2005 01:16:53 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=s/uBDU3l+X0rEMvdD7KPbZwoewhjl799VhGIwvIqOvFOkQKQ3i7pzcgY2gePsrWTp4EvW4PcsNFaUU0mg6cqI19Bz+I5W8rvlIJLN3En+bzP4+iL7pRVQ3IMzOKUZxKs7YeXAwSi1c3l6BnYYwzay0Uahb+4dNnqCRVKJy4f3Pw= Received: by 10.54.23.8 with SMTP id 8mr3453763wrw; Mon, 15 Aug 2005 01:16:52 -0700 (PDT) Received: by 10.54.31.35 with HTTP; Mon, 15 Aug 2005 01:16:52 -0700 (PDT) Message-ID: <8f554029050815011672ec4a5a@mail.gmail.com> Date: Mon, 15 Aug 2005 18:16:52 +1000 From: =?WINDOWS-1252?B?lSCV?= To: Juergen Lock In-Reply-To: <20050812205356.GA15463@saturn.kn-bremen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050812085823.645f5b39.kgunders@teamcool.net> <20050812205356.GA15463@saturn.kn-bremen.de> Cc: freebsd-amd64@freebsd.org Subject: Re: workstation mobo X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 08:16:54 -0000 On 8/13/05, Juergen Lock wrote: > On Fri, Aug 12, 2005 at 08:58:23AM -0600, Ken Gunderson wrote: > > Greets All: > > > > I'm liking these amd opteron servers so much that I am considering > > building an amd based workstationn. Assumed it would be Athalon based > > but in searching archives I note that some folks seem to prefer the > > opterons for workstation use. Perhaps to some degree in reaction > > to the "chipset mess". I'm not averse to spending a bit more for the > > opteron system but it seems to me the Opteron's CPU heatsink/fan might > > be a bit noisy for workstation use. And I have buddies shouting in my > > ear to "stick w/ Intel" for workstation. But then I also know others > > who run AMD for their desktop machines. Any recommends based on curren= t > > state of affairs in the ADM hardware world? >=20 > I just got a new box with an Asus A8V Deluxe board (VIA K8T800 Pro, > Socket 939), and so far everything seems to be working. The only > unusual thing i had to do for FreeBSD (5.4-R) was adding a patch > to the sk nic driver (see other thread.) >=20 Update on ASUS A8V Deluxe for archives I installed 5.4-RELEASE about April (2005) and track 5-Stable on that hardware straight from CVS - never had a prob with sk0 yet, it's worked since day one with no boot time errors. -- cheers gm From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 08:48:16 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 45F7616A420; Mon, 15 Aug 2005 08:48:16 +0000 (GMT) (envelope-from fabrice@bellard.org) Received: from sMtp.neuf.fr (sp604002mt.neufgp.fr [84.96.92.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCA6143D55; Mon, 15 Aug 2005 08:48:15 +0000 (GMT) (envelope-from fabrice@bellard.org) Received: from [84.99.204.171] by sp604002mt.gpm.neuf.ld (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTP id <0IL9005GS9SD2Z20@sp604002mt.gpm.neuf.ld>; Mon, 15 Aug 2005 10:48:13 +0200 (CEST) Date: Mon, 15 Aug 2005 10:48:56 +0200 From: Fabrice Bellard In-reply-to: <20050811193840.GA13133@saturn.kn-bremen.de> To: qemu-devel@nongnu.org Message-id: <430056F8.3010803@bellard.org> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <20050811193840.GA13133@saturn.kn-bremen.de> User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913 Cc: freebsd-emulation@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: [Qemu-devel] qemu-system-x86_64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 08:48:16 -0000 Juergen Lock wrote: > After further installing my new amd64 box (yes, if_sk works now :) > I just tried a few guests with qemu-system-x86_64: > > [...] > > Hope this is helpful to some... Thank you for the info. I am trying to fix the issues you have seen. Fabrice. From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 11:01:44 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 84A9A16A41F for ; Mon, 15 Aug 2005 11:01:44 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46BE343D49 for ; Mon, 15 Aug 2005 11:01:44 +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.3/8.13.3) with ESMTP id j7FB1iEP007430 for ; Mon, 15 Aug 2005 11:01:44 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7FB1hkZ007424 for freebsd-amd64@freebsd.org; Mon, 15 Aug 2005 11:01:43 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 15 Aug 2005 11:01:43 GMT Message-Id: <200508151101.j7FB1hkZ007424@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 Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 11:01:44 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/10/27] amd64/73211 amd64 FAST_IPSEC broken on amd64 1 problem 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 o [2004/12/18] amd64/75209 amd64 5.3-Release panics on attempted boot from o [2004/12/23] amd64/75417 amd64 ACPI: SATA Hard-disk o [2005/01/12] amd64/76136 amd64 system halts before reboot o [2005/01/17] amd64/76336 amd64 racoon/setkey -D cases instant "Fatal Tra o [2005/02/02] amd64/77011 amd64 consisten 5.3-p5 make crash on installwor o [2005/02/04] amd64/77101 amd64 Please include ULi M1689 LAN, SATA, and A o [2005/02/17] amd64/77629 amd64 aMule hardlocks AMD64 system o [2005/02/23] amd64/77949 amd64 Pb boot FreeBSD 64 o [2005/03/04] amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/p o [2005/03/07] amd64/78558 amd64 installation o [2005/03/14] amd64/78848 amd64 sis driver on FreeBSD 5.x does not work o o [2005/04/12] amd64/79813 amd64 Will not install/run on amd64 nForce 4 pl o [2005/04/19] amd64/80114 amd64 kldload snd_ich causes interrupt storm wh o [2005/05/06] amd64/80691 amd64 amd64 kernel hangs on load o [2005/05/14] amd64/81037 amd64 SATA problem o [2005/05/19] amd64/81272 amd64 JDK 1.5 port doesn't build. o [2005/05/20] amd64/81325 amd64 KLD if_ath.ko: depends on ath_hal - not a o [2005/05/28] amd64/81602 amd64 SATA crashes with parallel pcm access o [2005/06/09] amd64/82071 amd64 incorrect -march's parameter to build 32b o [2005/06/19] amd64/82425 amd64 fxp0: device timeout, fxp interface dies o [2005/06/23] amd64/82555 amd64 Kernel Panic - after i connect to my "amd o [2005/07/05] amd64/83005 amd64 Memory Occupied during installation of th o [2005/07/25] amd64/84027 amd64 if_nve gets stuck o [2005/08/12] amd64/84832 amd64 Installation crashes just at boot AMD64/ o [2005/08/14] amd64/84930 amd64 [msdosfs] something wrong with msdosfs on 36 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/08/15] amd64/70500 amd64 bge driver for 3Com 3C996B on amd64 preve 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 o [2004/12/13] ports/75015 amd64 cvsup on amd64 with runsocks (socks5) cor o [2005/03/17] amd64/78954 amd64 kerberos 5 failed to build o [2005/05/16] amd64/81089 amd64 FreeBSD 5.4 released version can not use o [2005/06/12] amd64/82178 amd64 missing 32bit subsystem o [2005/06/18] amd64/82380 amd64 buildworld error in libc o [2005/06/18] amd64/82399 amd64 MSI K8N Neo4 Platinium is not supported o [2005/06/24] amd64/82599 amd64 ports/misc/mtx wont compile on amd64 o [2005/07/20] amd64/83806 amd64 Can not comple /usr/src/lib/msun/amd64/fe o [2005/08/07] amd64/84652 amd64 kbdmap -r dumps core 16 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 11:20:17 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org 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 478EE16A428 for ; Mon, 15 Aug 2005 11:20:17 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16F1043D46 for ; Mon, 15 Aug 2005 11:20:17 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7FBKGl2014802 for ; Mon, 15 Aug 2005 11:20:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7FBKGjS014801; Mon, 15 Aug 2005 11:20:16 GMT (envelope-from gnats) Date: Mon, 15 Aug 2005 11:20:16 GMT Message-Id: <200508151120.j7FBKGjS014801@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Mikhail Teterin Cc: Subject: Re: amd64/84930: [msdosfs] something wrong with msdosfs on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mikhail Teterin List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Aug 2005 11:20:17 -0000 The following reply was made to PR amd64/84930; it has been noted by GNATS. From: Mikhail Teterin To: rsmith@xs4all.nl (Roland Smith) Cc: bug-followup@freebsd.org, andy@athame.co.uk Subject: Re: amd64/84930: [msdosfs] something wrong with msdosfs on amd64 Date: Mon, 15 Aug 2005 07:14:33 -0400 (EDT) > Did you get any unusual messages in the system logfiles? No, I checked. > > Or, maybe, it is related to its size? Two people have responded so far > > with their _working_ examples, but theirs are 61Mb and 250Mb. > > Could be, but I don't think so. IIRC, you have to have the "options > MSDOSFS_LARGE" in your kernel for drives >128GB. The disk is 40Gb... It is above 2Gb (and 4Gb), which may explain why the behavior is different from the working examples. But it is well below the size requiring special treatment -- and, indeed, works fine with my i386 systems. -mi From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 14:01:24 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 1B4E716A41F for ; Mon, 15 Aug 2005 14:01:24 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3B1643D46 for ; Mon, 15 Aug 2005 14:01:23 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 53A9511EB9 for ; Mon, 15 Aug 2005 08:01:18 -0600 (MDT) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 1BA6511EB8 for ; Mon, 15 Aug 2005 08:01:18 -0600 (MDT) Date: Mon, 15 Aug 2005 08:01:16 -0600 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20050815080116.0382d538.kgunders@teamcool.net> In-Reply-To: <8f554029050815011672ec4a5a@mail.gmail.com> References: <20050812085823.645f5b39.kgunders@teamcool.net> <20050812205356.GA15463@saturn.kn-bremen.de> <8f554029050815011672ec4a5a@mail.gmail.com> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: workstation mobo X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 14:01:24 -0000 On Mon, 15 Aug 2005 18:16:52 +1000 • • wrote: > On 8/13/05, Juergen Lock wrote: > > On Fri, Aug 12, 2005 at 08:58:23AM -0600, Ken Gunderson wrote: > > > Greets All: > > > > > > I'm liking these amd opteron servers so much that I am considering > > > building an amd based workstationn. Assumed it would be Athalon based > > > but in searching archives I note that some folks seem to prefer the > > > opterons for workstation use. Perhaps to some degree in reaction > > > to the "chipset mess". I'm not averse to spending a bit more for the > > > opteron system but it seems to me the Opteron's CPU heatsink/fan might > > > be a bit noisy for workstation use. And I have buddies shouting in my > > > ear to "stick w/ Intel" for workstation. But then I also know others > > > who run AMD for their desktop machines. Any recommends based on current > > > state of affairs in the ADM hardware world? > > > > I just got a new box with an Asus A8V Deluxe board (VIA K8T800 Pro, > > Socket 939), and so far everything seems to be working. The only > > unusual thing i had to do for FreeBSD (5.4-R) was adding a patch > > to the sk nic driver (see other thread.) > > > > Update on ASUS A8V Deluxe for archives > > I installed 5.4-RELEASE about April (2005) and track 5-Stable on that > hardware straight from CVS - never had a prob with sk0 yet, it's > worked since day one with no boot time errors. Thanks for the input. My short list is two VIA KT890 based boards: - Abit AX8v2.0 - Asus A8-E SE I've had good history w/both of these mobo makers but the Asus gets a an extra plus in the support department since I can usually find bios updates etc. on their site w/a bit less digging...;-) -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 14:30:00 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 4E67816A41F for ; Mon, 15 Aug 2005 14:30:00 +0000 (GMT) (envelope-from david@jetnet.co.uk) Received: from kosh.jetnet.co.uk (kosh.jetnet.co.uk [80.87.128.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE69143D45 for ; Mon, 15 Aug 2005 14:29:59 +0000 (GMT) (envelope-from david@jetnet.co.uk) Received: from localhost (localhost [127.0.0.1]) by kosh.jetnet.co.uk (Postfix) with ESMTP id 53ED325F3B; Mon, 15 Aug 2005 14:29:59 +0000 (GMT) Received: from kosh.jetnet.co.uk ([127.0.0.1]) by localhost (mail.jetnet.co.uk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 89306-06; Mon, 15 Aug 2005 14:29:57 +0000 (GMT) Received: from [192.168.0.100] (82-69-108-39.dsl.in-addr.zen.co.uk [82.69.108.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by kosh.jetnet.co.uk (Postfix) with ESMTP id 9D71A20A5A; Mon, 15 Aug 2005 14:29:57 +0000 (GMT) Message-ID: <4300A6E4.4030103@jetnet.co.uk> Date: Mon, 15 Aug 2005 15:29:56 +0100 From: David Reid User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050808) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ken Gunderson References: <20050812085823.645f5b39.kgunders@teamcool.net> <20050812205356.GA15463@saturn.kn-bremen.de> <8f554029050815011672ec4a5a@mail.gmail.com> <20050815080116.0382d538.kgunders@teamcool.net> In-Reply-To: <20050815080116.0382d538.kgunders@teamcool.net> X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at jetnet.co.uk Cc: freebsd-amd64@freebsd.org Subject: Re: workstation mobo X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 14:30:00 -0000 Ken Gunderson wrote: > On Mon, 15 Aug 2005 18:16:52 +1000 > • • wrote: > > >>On 8/13/05, Juergen Lock wrote: >> >>>On Fri, Aug 12, 2005 at 08:58:23AM -0600, Ken Gunderson wrote: >>> >>>>Greets All: >>>> >>>>I'm liking these amd opteron servers so much that I am considering >>>>building an amd based workstationn. Assumed it would be Athalon based >>>>but in searching archives I note that some folks seem to prefer the >>>>opterons for workstation use. Perhaps to some degree in reaction >>>>to the "chipset mess". I'm not averse to spending a bit more for the >>>>opteron system but it seems to me the Opteron's CPU heatsink/fan might >>>>be a bit noisy for workstation use. And I have buddies shouting in my >>>>ear to "stick w/ Intel" for workstation. But then I also know others >>>>who run AMD for their desktop machines. Any recommends based on current >>>>state of affairs in the ADM hardware world? >>> >>>I just got a new box with an Asus A8V Deluxe board (VIA K8T800 Pro, >>>Socket 939), and so far everything seems to be working. The only >>>unusual thing i had to do for FreeBSD (5.4-R) was adding a patch >>>to the sk nic driver (see other thread.) >>> >> >>Update on ASUS A8V Deluxe for archives >> >>I installed 5.4-RELEASE about April (2005) and track 5-Stable on that >>hardware straight from CVS - never had a prob with sk0 yet, it's >>worked since day one with no boot time errors. > > > Thanks for the input. My short list is two VIA KT890 based boards: > > - Abit AX8v2.0 > - Asus A8-E SE > > I've had good history w/both of these mobo makers but the Asus gets a > an extra plus in the support department since I can usually find bios > updates etc. on their site w/a bit less digging...;-) when I updated I went for an ABit An-8 Ultra, based on the nVidia chipset, but while the board *almost* works correctly, it seems to have some issues. Also given nVidias approach to drivers I'd suggest avoiding them - I would have if I'd known how bad they were! david From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 14:42:31 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 46A2F16A41F for ; Mon, 15 Aug 2005 14:42:31 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5C5743D45 for ; Mon, 15 Aug 2005 14:42:30 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 38A5711EB9; Mon, 15 Aug 2005 08:42:30 -0600 (MDT) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id D9BD211EA4; Mon, 15 Aug 2005 08:42:29 -0600 (MDT) Date: Mon, 15 Aug 2005 08:42:28 -0600 From: Ken Gunderson To: David Reid Message-Id: <20050815084228.2828df8a.kgunders@teamcool.net> In-Reply-To: <4300A6E4.4030103@jetnet.co.uk> References: <20050812085823.645f5b39.kgunders@teamcool.net> <20050812205356.GA15463@saturn.kn-bremen.de> <8f554029050815011672ec4a5a@mail.gmail.com> <20050815080116.0382d538.kgunders@teamcool.net> <4300A6E4.4030103@jetnet.co.uk> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-amd64@freebsd.org Subject: Re: workstation mobo X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 14:42:31 -0000 On Mon, 15 Aug 2005 15:29:56 +0100 David Reid wrote: > Ken Gunderson wrote: > > On Mon, 15 Aug 2005 18:16:52 +1000 > > • • wrote: > > > > > >>On 8/13/05, Juergen Lock wrote: > >> > >>>On Fri, Aug 12, 2005 at 08:58:23AM -0600, Ken Gunderson wrote: > >>> > >>>>Greets All: > >>>> > >>>>I'm liking these amd opteron servers so much that I am considering > >>>>building an amd based workstationn. Assumed it would be Athalon based > >>>>but in searching archives I note that some folks seem to prefer the > >>>>opterons for workstation use. Perhaps to some degree in reaction > >>>>to the "chipset mess". I'm not averse to spending a bit more for the > >>>>opteron system but it seems to me the Opteron's CPU heatsink/fan might > >>>>be a bit noisy for workstation use. And I have buddies shouting in my > >>>>ear to "stick w/ Intel" for workstation. But then I also know others > >>>>who run AMD for their desktop machines. Any recommends based on current > >>>>state of affairs in the ADM hardware world? > >>> > >>>I just got a new box with an Asus A8V Deluxe board (VIA K8T800 Pro, > >>>Socket 939), and so far everything seems to be working. The only > >>>unusual thing i had to do for FreeBSD (5.4-R) was adding a patch > >>>to the sk nic driver (see other thread.) > >>> > >> > >>Update on ASUS A8V Deluxe for archives > >> > >>I installed 5.4-RELEASE about April (2005) and track 5-Stable on that > >>hardware straight from CVS - never had a prob with sk0 yet, it's > >>worked since day one with no boot time errors. > > > > > > Thanks for the input. My short list is two VIA KT890 based boards: > > > > - Abit AX8v2.0 > > - Asus A8-E SE > > > > I've had good history w/both of these mobo makers but the Asus gets a > > an extra plus in the support department since I can usually find bios > > updates etc. on their site w/a bit less digging...;-) > > when I updated I went for an ABit An-8 Ultra, based on the nVidia > chipset, but while the board *almost* works correctly, it seems to have > some issues. Also given nVidias approach to drivers I'd suggest avoiding > them - I would have if I'd known how bad they were! Which is why I'm looking at VIA based boards. Moreover, given nVidia's unwillingness to play nicely with others you can rest assured I'll also be purchasing an ATI based VPU...... nVidia probably doesn't give a damn one way or the other since they make plenty profit off the mainstream Winblows gamers. But I can do my part and boycott their stuff to the extent possible... I've talked with Tyan about the nVidia issues and encouraged them to continue making boards based on AMD chipset but Tyan USA representative informed me that AMD was getting out of the chipset business now that nVidia is making "good ones". Maybe somebody w/contacts at AMD could clue them into the nVidia mess. -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 15:24:37 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 12D3716A41F for ; Mon, 15 Aug 2005 15:24:37 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB08343D45 for ; Mon, 15 Aug 2005 15:24:36 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id E27BB11EB9 for ; Mon, 15 Aug 2005 09:24:35 -0600 (MDT) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 95D3411EA4 for ; Mon, 15 Aug 2005 09:24:35 -0600 (MDT) Date: Mon, 15 Aug 2005 09:24:34 -0600 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20050815092434.282c53f5.kgunders@teamcool.net> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: rc init path question X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 15:24:37 -0000 Greets: Not strictly amd64 related but I'm not subsribed to questions so here goes.... Why is PATH set so restrictively (e.g. PATH=/sbin:/bin:/usr/sbin:/usr/ bin) by rc init? Startup scripts in rc.d inherit this and seem to have difficulties finding things upon boot whereas running the script manually works fine since .cshrc has come into play by then. Or am I totally missing something here.?? TIA -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 15:42:57 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 852D416A41F for ; Mon, 15 Aug 2005 15:42:57 +0000 (GMT) (envelope-from david@jetnet.co.uk) Received: from kosh.jetnet.co.uk (kosh.jetnet.co.uk [80.87.128.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0972443D55 for ; Mon, 15 Aug 2005 15:42:57 +0000 (GMT) (envelope-from david@jetnet.co.uk) Received: from localhost (localhost [127.0.0.1]) by kosh.jetnet.co.uk (Postfix) with ESMTP id 9BA652AC77; Mon, 15 Aug 2005 15:42:56 +0000 (GMT) Received: from kosh.jetnet.co.uk ([127.0.0.1]) by localhost (mail.jetnet.co.uk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 90102-03-2; Mon, 15 Aug 2005 15:42:47 +0000 (GMT) Received: from [192.168.0.100] (82-69-108-39.dsl.in-addr.zen.co.uk [82.69.108.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by kosh.jetnet.co.uk (Postfix) with ESMTP id 8FFD62A9F3; Mon, 15 Aug 2005 15:42:47 +0000 (GMT) Message-ID: <4300B7F7.2000702@jetnet.co.uk> Date: Mon, 15 Aug 2005 16:42:47 +0100 From: David Reid User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050808) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ken Gunderson References: <20050812085823.645f5b39.kgunders@teamcool.net> <20050812205356.GA15463@saturn.kn-bremen.de> <8f554029050815011672ec4a5a@mail.gmail.com> <20050815080116.0382d538.kgunders@teamcool.net> <4300A6E4.4030103@jetnet.co.uk> <20050815084228.2828df8a.kgunders@teamcool.net> In-Reply-To: <20050815084228.2828df8a.kgunders@teamcool.net> X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at jetnet.co.uk Cc: freebsd-amd64@freebsd.org Subject: Re: workstation mobo X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 15:42:57 -0000 Ken Gunderson wrote: > On Mon, 15 Aug 2005 15:29:56 +0100 > David Reid wrote: > > >>Ken Gunderson wrote: >> >>>On Mon, 15 Aug 2005 18:16:52 +1000 >>>• • wrote: >>> >>> >>> >>>>On 8/13/05, Juergen Lock wrote: >>>> >>>> >>>>>On Fri, Aug 12, 2005 at 08:58:23AM -0600, Ken Gunderson wrote: >>>>> >>>>> >>>>>>Greets All: >>>>>> >>>>>>I'm liking these amd opteron servers so much that I am considering >>>>>>building an amd based workstationn. Assumed it would be Athalon based >>>>>>but in searching archives I note that some folks seem to prefer the >>>>>>opterons for workstation use. Perhaps to some degree in reaction >>>>>>to the "chipset mess". I'm not averse to spending a bit more for the >>>>>>opteron system but it seems to me the Opteron's CPU heatsink/fan might >>>>>>be a bit noisy for workstation use. And I have buddies shouting in my >>>>>>ear to "stick w/ Intel" for workstation. But then I also know others >>>>>>who run AMD for their desktop machines. Any recommends based on current >>>>>>state of affairs in the ADM hardware world? >>>>> >>>>>I just got a new box with an Asus A8V Deluxe board (VIA K8T800 Pro, >>>>>Socket 939), and so far everything seems to be working. The only >>>>>unusual thing i had to do for FreeBSD (5.4-R) was adding a patch >>>>>to the sk nic driver (see other thread.) >>>>> >>>> >>>>Update on ASUS A8V Deluxe for archives >>>> >>>>I installed 5.4-RELEASE about April (2005) and track 5-Stable on that >>>>hardware straight from CVS - never had a prob with sk0 yet, it's >>>>worked since day one with no boot time errors. >>> >>> >>>Thanks for the input. My short list is two VIA KT890 based boards: >>> >>>- Abit AX8v2.0 >>>- Asus A8-E SE >>> >>>I've had good history w/both of these mobo makers but the Asus gets a >>>an extra plus in the support department since I can usually find bios >>>updates etc. on their site w/a bit less digging...;-) >> >>when I updated I went for an ABit An-8 Ultra, based on the nVidia >>chipset, but while the board *almost* works correctly, it seems to have >>some issues. Also given nVidias approach to drivers I'd suggest avoiding >>them - I would have if I'd known how bad they were! > > > Which is why I'm looking at VIA based boards. Moreover, given nVidia's > unwillingness to play nicely with others you can rest assured I'll also > be purchasing an ATI based VPU...... nVidia probably doesn't give a > damn one way or the other since they make plenty profit off the > mainstream Winblows gamers. But I can do my part and boycott their > stuff to the extent possible... Boycotting manufacturers is the only way to go. Sadly, as you say, it'll take a lot of people to make them sit up and take notice. A long time ago I tried to organise a site that allowed people to register their boycott, but I never really got to a point of getting it all working and ran out of time/enthusiasm. I ended up with an nVidia VPU, but that was before I realised that I needed the nvidia driver (which doesn't work on amd64) for dual head. If anyone knows of an ATI card that does dual head and DVI output then I'd be more than happy to hear :-) I will probably swap at some point soonish... david From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 16:54:36 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 6539916A41F for ; Mon, 15 Aug 2005 16:54:36 +0000 (GMT) (envelope-from flynn@energyhq.es.eu.org) Received: from mindfields.energyhq.es.eu.org (73.Red-213-97-200.pooles.rima-tde.net [213.97.200.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB9F443D53 for ; Mon, 15 Aug 2005 16:54:30 +0000 (GMT) (envelope-from flynn@energyhq.es.eu.org) Received: from scienide.energyhq.es.eu.org (scienide.energyhq.es.eu.org [192.168.100.1]) by mindfields.energyhq.es.eu.org (Postfix) with SMTP id 5AD1F123FCA; Mon, 15 Aug 2005 18:54:28 +0200 (CEST) Date: Mon, 15 Aug 2005 18:54:25 +0200 From: Miguel Mendez To: Roland Smith Message-Id: <20050815185425.5740ac11.flynn@energyhq.es.eu.org> In-Reply-To: <20050814114844.GA58288@slackbox.xs4all.nl> References: <20050814113127.7d69af2b.flynn@energyhq.es.eu.org> <20050814114844.GA58288@slackbox.xs4all.nl> X-Mailer: Sylpheed version 2.0.0 (GTK+ 2.6.9; 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: 32bit Linux dri apps on FreeBSD/amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 16:54:36 -0000 On Sun, 14 Aug 2005 13:48:44 +0200 Roland Smith wrote: Thanks Markus and Roland for the interesting info. I wanted to rule out the 'pilot error' case before starting to read code. I'm going to keep running the amd64 version of the operating system but nevertheless this problem is pretty interesting. > 0xc0000000 = copy parameters in and out > 0x00080000 = argument length <<16 > 0x00006400 = ioctl group <<8 > 0x00000001 = ioctl number 0x01 = DRM_IOCTL_GET_UNIQUE > > The definition of getunique is: > > int DRM(getunique)( DRM_IOCTL_ARGS ) > { [...] code snippet > } drm_unique_t; > On amd64, both size_t and char* are 8 bytes. So sizeof(drm_unique_t) is > 16 bytes on amd64. > To fix this, the drm driver would have to know if ioctls were being made > by a 32-bit program, and adjust the parameter size tests accordingly. I > do not know if that is possible. Besides the work the DRI people are doing I wonder if it could be possible to write some sort of 'proxy' that would sit between linux_dri and the kernel's drm module, doing the necessary translations. Considering that Linux apps try to open /compat/linux/dev first it might actually be doable. I'll have to investigate that. In the meantime I'll play bzflag and crack-attack, both excellent games btw :) Cheers, -- Miguel Mendez http://www.energyhq.es.eu.org PGP Key: 0xDC8514F1 From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 16:56:59 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 6EE4716A41F for ; Mon, 15 Aug 2005 16:56:59 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAFA043D48 for ; Mon, 15 Aug 2005 16:56:58 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper [212.12.50.230]) by schlepper.zs64.net (8.13.1/8.12.9) with ESMTP id j7FGuvwG092586 for ; Mon, 15 Aug 2005 18:56:57 +0200 (CEST) (envelope-from cracauer@schlepper.zs64.net) Received: (from cracauer@localhost) by schlepper.zs64.net (8.13.1/8.12.9/Submit) id j7FGuvZ5092585 for freebsd-amd64@freebsd.org; Mon, 15 Aug 2005 12:56:57 -0400 (EDT) (envelope-from cracauer) Date: Mon, 15 Aug 2005 12:56:57 -0400 From: Martin Cracauer To: freebsd-amd64@freebsd.org Message-ID: <20050815125657.A92343@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Subject: 4 GB RAM showing up as 3, BIOS memory hole and all that X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 16:56:59 -0000 Somebody here must know this: I have a Dual Opteron board with 4x 1 GB RAM. The memory count in the BIOS goes up to 640 KB + 3072 MB, and FreeBSD says it sees 3 GB. I know/assume/heared this has to do with the I/O space placed in the upper GB and that you can re-map the top GB to avoid the problem. The BIOS has the options to have a memory hole which I set to 1 GB, thinking it would put the 3G-4G memory at 4G-5G instead. It seems I am wrong about this, I am stuck with 3 GB. Obviously I don't understand how that top GB for I/O works, how can that work when the machine has less than 3 GB? Any way to get my GB back? I know the hardware is OK by cross-checking all modules individually. And I can see that the memory bandwidth is that of dual-channel, so it is not a case of one stick not being recognized. Specs: - Armima Rioworks HDAMB, 2x Opteron 246, 4x 1 GB PC2100 - FreeBSD-7.0-current/AMD64, SMP kernel - dmesg, pciconf etc on http://www.cons.org/cracauer/machines/wings/ Thanks! Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ No warranty. This email is probably produced by one of my cats stepping on the keys. No, I don't have an infinite number of cats. From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 17:19:58 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 05C5B16A41F for ; Mon, 15 Aug 2005 17:19:58 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id A280D43D45 for ; Mon, 15 Aug 2005 17:19:57 +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 j7FHJvri016679; Mon, 15 Aug 2005 10:19:57 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j7FHJv8o016678; Mon, 15 Aug 2005 10:19:57 -0700 Date: Mon, 15 Aug 2005 10:19:57 -0700 From: Brooks Davis To: Ken Gunderson Message-ID: <20050815171957.GC8859@odin.ac.hmc.edu> References: <20050815092434.282c53f5.kgunders@teamcool.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="aT9PWwzfKXlsBJM1" Content-Disposition: inline In-Reply-To: <20050815092434.282c53f5.kgunders@teamcool.net> 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: rc init path question X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 17:19:58 -0000 --aT9PWwzfKXlsBJM1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 15, 2005 at 09:24:34AM -0600, Ken Gunderson wrote: > Greets: >=20 > Not strictly amd64 related but I'm not subsribed to questions so here > goes.... >=20 > Why is PATH set so restrictively (e.g. PATH=3D/sbin:/bin:/usr/sbin:/usr/ > bin) by rc init? Startup scripts in rc.d inherit this and seem to have > difficulties finding things upon boot whereas running the script > manually works fine since .cshrc has come into play by then. Or am I > totally missing something here.?? Predictability. Those directories should in general contain only system programs who's behavior should be what we expect. Adding other directories such as /usr/local/bin would complicate matters. This means you have to test slightly more carefully, but using full paths to commands is good practice in general, particularly for system startup scripts. -- 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 --aT9PWwzfKXlsBJM1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDAM68XY6L6fI4GtQRAjCGAJ9c1r7CZl17hMDuoUkXcLkCQk/+/ACgn6L4 A1CZ4jeahlm0p3cItYGtP+8= =fKm1 -----END PGP SIGNATURE----- --aT9PWwzfKXlsBJM1-- From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 17:22:52 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 D46EC16A42F for ; Mon, 15 Aug 2005 17:22:52 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75C9343D48 for ; Mon, 15 Aug 2005 17:22:52 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.13.4/8.13.4) with ESMTP id j7FHMoQF032845; Mon, 15 Aug 2005 10:22:50 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.4/8.13.1/Submit) id j7FHMo1b032844; Mon, 15 Aug 2005 10:22:50 -0700 (PDT) (envelope-from sgk) Date: Mon, 15 Aug 2005 10:22:50 -0700 From: Steve Kargl To: Martin Cracauer Message-ID: <20050815172250.GA32804@troutmask.apl.washington.edu> References: <20050815125657.A92343@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050815125657.A92343@cons.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: 4 GB RAM showing up as 3, BIOS memory hole and all that X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 17:22:53 -0000 On Mon, Aug 15, 2005 at 12:56:57PM -0400, Martin Cracauer wrote: > > I have a Dual Opteron board with 4x 1 GB RAM. The memory count in the > BIOS goes up to 640 KB + 3072 MB, and FreeBSD says it sees 3 GB. (snip) > Any way to get my GB back? This should be a FAQ. No, you can't get it back. David O'brien has explained this more than once in the freebsd-amd64 list. Unfortunately, I don't have a handy URL for you to read. I suggest scanning the list for posts by David in the Feb to May timeframe. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 17:26:19 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 84E8516A41F for ; Mon, 15 Aug 2005 17:26:19 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A7C843D45 for ; Mon, 15 Aug 2005 17:26:18 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 65BC811EB9; Mon, 15 Aug 2005 11:26:18 -0600 (MDT) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 2BA8B11EB8; Mon, 15 Aug 2005 11:26:18 -0600 (MDT) Date: Mon, 15 Aug 2005 11:26:17 -0600 From: Ken Gunderson To: Brooks Davis Message-Id: <20050815112617.5a6e80f3.kgunders@teamcool.net> In-Reply-To: <20050815171957.GC8859@odin.ac.hmc.edu> References: <20050815092434.282c53f5.kgunders@teamcool.net> <20050815171957.GC8859@odin.ac.hmc.edu> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-amd64@freebsd.org Subject: Re: rc init path question X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 17:26:19 -0000 On Mon, 15 Aug 2005 10:19:57 -0700 Brooks Davis wrote: > On Mon, Aug 15, 2005 at 09:24:34AM -0600, Ken Gunderson wrote: > > Greets: > > > > Not strictly amd64 related but I'm not subsribed to questions so here > > goes.... > > > > Why is PATH set so restrictively (e.g. PATH=/sbin:/bin:/usr/sbin:/usr/ > > bin) by rc init? Startup scripts in rc.d inherit this and seem to have > > difficulties finding things upon boot whereas running the script > > manually works fine since .cshrc has come into play by then. Or am I > > totally missing something here.?? > > Predictability. Those directories should in general contain only system > programs who's behavior should be what we expect. Adding other > directories such as /usr/local/bin would complicate matters. This means > you have to test slightly more carefully, but using full paths to > commands is good practice in general, particularly for system startup > scripts. Yes indeed, but for example, in the case of something like Zope it needs to know where to look for things like lnyx, etc. wh/get stashed in /usr/local/bin. Adding a path statement to rc.d/zope.sh solves the problem but it took me a while to figure out why manual starts worked but not reboots...;-P Or maybe I should be specifying PATH in zope.conf in this case. in any event, I've subsequently also noticed this in a couple other rc.d scripts. Thanks for your input. -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 17:33:57 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 6A56216A420 for ; Mon, 15 Aug 2005 17:33:57 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr2.xs4all.nl (smtp-vbr2.xs4all.nl [194.109.24.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D87743D48 for ; Mon, 15 Aug 2005 17:33:56 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr2.xs4all.nl (8.13.3/8.13.3) with ESMTP id j7FHXZ8f018777; Mon, 15 Aug 2005 19:33:39 +0200 (CEST) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id BC55961B9; Mon, 15 Aug 2005 19:33:35 +0200 (CEST) Date: Mon, 15 Aug 2005 19:33:35 +0200 From: Roland Smith To: Miguel Mendez Message-ID: <20050815173335.GA69184@slackbox.xs4all.nl> Mail-Followup-To: Miguel Mendez , freebsd-amd64@freebsd.org References: <20050814113127.7d69af2b.flynn@energyhq.es.eu.org> <20050814114844.GA58288@slackbox.xs4all.nl> <20050815185425.5740ac11.flynn@energyhq.es.eu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uAKRQypu60I7Lcqm" Content-Disposition: inline In-Reply-To: <20050815185425.5740ac11.flynn@energyhq.es.eu.org> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-amd64@freebsd.org Subject: Re: 32bit Linux dri apps on FreeBSD/amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 17:33:57 -0000 --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 15, 2005 at 06:54:25PM +0200, Miguel Mendez wrote: > > To fix this, the drm driver would have to know if ioctls were being made > > by a 32-bit program, and adjust the parameter size tests accordingly. I > > do not know if that is possible. >=20 > Besides the work the DRI people are doing I wonder if it could be > possible to write some sort of 'proxy' that would sit between linux_dri a= nd > the kernel's drm module, doing the necessary translations. Considering > that Linux apps try to open /compat/linux/dev first it might actually > be doable. I'll have to investigate that. It certainly looks doable. But it might be too much overhead. Every bit of data passed between the user process and the kernel would have to be converted if necessary. One way of doing that would be to add this code to the relevant macros in drm_os_freebsd.h, but it give an unacceptable drop in performance. IMHO a pseudo-driver linked to /compat/linux/dev is a better idea. That way, only the processes that need it have to accept the translation overhead. Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFDANHvEnfvsMMhpyURAtyDAJ9ueQkCGdr7zLGS0GQzMcjDyoYDngCdFbll Qe2qqJYKNfd6wGWFs6m5Cho= =Gtm5 -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm-- From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 18:21:48 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 DBD2D16A41F for ; Mon, 15 Aug 2005 18:21:48 +0000 (GMT) (envelope-from Say@funlabs.com) Received: from funlabs.com (dpg231.neoplus.adsl.tpnet.pl [83.24.140.231]) by mx1.FreeBSD.org (Postfix) with SMTP id C9A0543D49 for ; Mon, 15 Aug 2005 18:21:43 +0000 (GMT) (envelope-from Say@funlabs.com) From: "Dipali Saylor" To: "Juni Schreiber" Message-ID: <001901c5a1c6$24a02a00$698aa8c0@flying> Date: Mon, 15 Aug 2005 13:21:24 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: =?iso-8859-1?q?McDonald=27s_bomber_j=C4iled?= X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 18:21:49 -0000 Hello, some acquaintance will see me and then theyll tell my husband I was = = outKoroviev - hes the devil!has been sitting on this platform and = sleeping, but when the full moonthree pm come. Berlioz.sounds - over = him. But before then he wont rise.will not see Yeshua, you will never = leave your refuge. Hundreds of arms were raised, the spectators = held the bills up to theabout the world and about power. Well, so, = if its more comforting, consider me that, Woland replied `He casts = no shadow! Rimsky cried out desperately in his mind. Heeven moaned, = began talking to himself, got up. The storm raged more andshe had = received from Azazello, and Margarita did not take her eyes from itsthe = same company. Here the girls story was interrupted - the valerian = had not done muchscored by deep wrinkles running parallel to the sharp = eyebrows. The skin ofparchment and was horrified. I said decidedly = nothing of whats written From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 18:35:11 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 9E66616A41F for ; Mon, 15 Aug 2005 18:35:11 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4823443D45 for ; Mon, 15 Aug 2005 18:35:11 +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 j7FIZAG2024003; Mon, 15 Aug 2005 11:35:10 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j7FIZAkL024002; Mon, 15 Aug 2005 11:35:10 -0700 Date: Mon, 15 Aug 2005 11:35:10 -0700 From: Brooks Davis To: Ken Gunderson Message-ID: <20050815183510.GE8859@odin.ac.hmc.edu> References: <20050815092434.282c53f5.kgunders@teamcool.net> <20050815171957.GC8859@odin.ac.hmc.edu> <20050815112617.5a6e80f3.kgunders@teamcool.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="phCU5ROyZO6kBE05" Content-Disposition: inline In-Reply-To: <20050815112617.5a6e80f3.kgunders@teamcool.net> 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: rc init path question X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 18:35:11 -0000 --phCU5ROyZO6kBE05 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 15, 2005 at 11:26:17AM -0600, Ken Gunderson wrote: > On Mon, 15 Aug 2005 10:19:57 -0700 > Brooks Davis wrote: >=20 > > On Mon, Aug 15, 2005 at 09:24:34AM -0600, Ken Gunderson wrote: > > > Greets: > > >=20 > > > Not strictly amd64 related but I'm not subsribed to questions so here > > > goes.... > > >=20 > > > Why is PATH set so restrictively (e.g. PATH=3D/sbin:/bin:/usr/sbin:/u= sr/ > > > bin) by rc init? Startup scripts in rc.d inherit this and seem to ha= ve > > > difficulties finding things upon boot whereas running the script > > > manually works fine since .cshrc has come into play by then. Or am I > > > totally missing something here.?? > >=20 > > Predictability. Those directories should in general contain only system > > programs who's behavior should be what we expect. Adding other > > directories such as /usr/local/bin would complicate matters. This means > > you have to test slightly more carefully, but using full paths to > > commands is good practice in general, particularly for system startup > > scripts. >=20 > Yes indeed, but for example, in the case of something like Zope it needs > to know where to look for things like lnyx, etc. wh/get stashed > in /usr/local/bin. Adding a path statement to rc.d/zope.sh solves the > problem but it took me a while to figure out why manual starts worked > but not reboots...;-P Or maybe I should be specifying PATH in > zope.conf in this case. in any event, I've subsequently also noticed > this in a couple other rc.d scripts. The script should use /usr/local/bin/lnyx in that case. Actually, it should use %%LOCALBASE%%/bin/lnyx and have LOCALBASE be set by the port installation porcess. -- 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 --phCU5ROyZO6kBE05 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDAOBdXY6L6fI4GtQRAj4MAKDXhB24ELSM7i5MUwhWdpTJwWBrIQCeM5CF CrpKLcBMoQ9OdBG6TrhfPXQ= =V5JG -----END PGP SIGNATURE----- --phCU5ROyZO6kBE05-- From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 18:58:24 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 01BB916A41F for ; Mon, 15 Aug 2005 18:58:24 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from deadcafe.de (deadcafe.de [81.169.162.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53C8743D45 for ; Mon, 15 Aug 2005 18:58:23 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from dialin.t-online.de (p54A5CD81.dip.t-dialin.net [84.165.205.129]) by deadcafe.de (8.13.4/8.13.4/Rock) with ESMTP id j7FIwGF5011737 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 15 Aug 2005 20:58:18 +0200 (CEST) X-Envelope-To: Received: from [172.23.7.254] (doom.rock.net [172.23.7.254]) by dialin.t-online.de (8.13.4/8.13.4/Rock) with ESMTP id j7FIw95C098688 for ; Mon, 15 Aug 2005 20:58:09 +0200 (CEST) Message-ID: <4300E5C1.4030808@deadcafe.de> Date: Mon, 15 Aug 2005 20:58:09 +0200 From: Daniel Rock User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050323) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20050815125657.A92343@cons.org> <20050815172250.GA32804@troutmask.apl.washington.edu> In-Reply-To: <20050815172250.GA32804@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.1 required=5.5 tests=FORGED_RCVD_HELO autolearn=disabled version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on deadcafe.de Subject: Re: 4 GB RAM showing up as 3, BIOS memory hole and all that X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 18:58:24 -0000 Steve Kargl wrote: > On Mon, Aug 15, 2005 at 12:56:57PM -0400, Martin Cracauer wrote: >>Any way to get my GB back? > > > This should be a FAQ. No, you can't get it back. > David O'brien has explained this more than once in > the freebsd-amd64 list. Unfortunately, I don't > have a handy URL for you to read. I suggest scanning > the list for posts by David in the Feb to May timeframe. > Hmm, on my board I could get the missing hole back. BIOS has three settings for memory hole remapping: Disabled/Hardware/Software (Hardware remapping should only work on stepping E-Opterons). With each of these settings I get different results: Hardware: real memory = 5637144576 (5376 MB) Physical memory chunk(s): 0x0000000000001000 - 0x0000000000090fff, 589824 bytes (144 pages) 0x0000000000985000 - 0x00000000a616ffff, 2776543232 bytes (677867 pages) 0x0000000100000000 - 0x000000014ffdffff, 1342046208 bytes (327648 pages) avail memory = 4109500416 (3919 MB) Software: real memory = 6442450944 (6144 MB) Physical memory chunk(s): 0x0000000000001000 - 0x0000000000090fff, 589824 bytes (144 pages) 0x0000000000985000 - 0x000000007ff1ffff, 2136584192 bytes (521627 pages) 0x0000000100000000 - 0x0000000174baffff, 1958412288 bytes (478128 pages) avail memory = 4085907456 (3896 MB) Disabled: real memory = 2951872512 (2815 MB) Physical memory chunk(s): 0x0000000000001000 - 0x0000000000090fff, 589824 bytes (144 pages) 0x0000000000983000 - 0x00000000aac56fff, 2855092224 bytes (697044 pages) avail memory = 2846003200 (2714 MB) Unfortunately, only if I cut memory below 4GB, my nve network adapter does work at all (ehm, mostly) - but that is another story... Daniel From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 19:15:32 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 DF10016A41F for ; Mon, 15 Aug 2005 19:15:32 +0000 (GMT) (envelope-from nox@saturn.kn-bremen.de) Received: from gwyn.kn-bremen.de (gwyn.kn-bremen.de [212.63.36.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABB5A43D48 for ; Mon, 15 Aug 2005 19:15:29 +0000 (GMT) (envelope-from nox@saturn.kn-bremen.de) Received: from gwyn.kn-bremen.de (gwyn [127.0.0.1]) by gwyn.kn-bremen.de (8.13.4/8.13.4/Debian-3) with ESMTP id j7FJFPuS020726; Mon, 15 Aug 2005 21:15:25 +0200 Received: from saturn.kn-bremen.de (uucp@localhost) by gwyn.kn-bremen.de (8.13.4/8.13.4/Submit) with UUCP id j7FJFPFZ020724; Mon, 15 Aug 2005 21:15:25 +0200 Received: from saturn.kn-bremen.de (localhost [127.0.0.1]) by saturn.kn-bremen.de (8.13.1/8.13.1) with ESMTP id j7FJDJQh062760; Mon, 15 Aug 2005 21:13:19 +0200 (CEST) (envelope-from nox@saturn.kn-bremen.de) Received: (from nox@localhost) by saturn.kn-bremen.de (8.13.1/8.13.1/Submit) id j7FJDIxn062759; Mon, 15 Aug 2005 21:13:18 +0200 (CEST) (envelope-from nox) From: Juergen Lock Date: Mon, 15 Aug 2005 21:13:18 +0200 To: ? ? Message-ID: <20050815191318.GA62590@saturn.kn-bremen.de> References: <20050812085823.645f5b39.kgunders@teamcool.net> <20050812205356.GA15463@saturn.kn-bremen.de> <8f554029050815011672ec4a5a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8f554029050815011672ec4a5a@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: workstation mobo X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 19:15:33 -0000 On Mon, Aug 15, 2005 at 06:16:52PM +1000, ? ? wrote: > On 8/13/05, I wrote: >[...] > > I just got a new box with an Asus A8V Deluxe board (VIA K8T800 Pro, > > Socket 939), and so far everything seems to be working. The only > > unusual thing i had to do for FreeBSD (5.4-R) was adding a patch > > to the sk nic driver (see other thread.) > > > > Update on ASUS A8V Deluxe for archives > > I installed 5.4-RELEASE about April (2005) and track 5-Stable on that > hardware straight from CVS - never had a prob with sk0 yet, it's > worked since day one with no boot time errors. Yeah I was surprised too that my network didnt work out-of-the-box, as i had read of other ppl having no problems at all with this board. Apparently there are boards with different revisions of the sk chip (skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) here, see other thread for the full dmesg.) Juergen From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 19:45:54 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 DF6FC16A41F; Mon, 15 Aug 2005 19:45:54 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1385243D45; Mon, 15 Aug 2005 19:45:53 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper [212.12.50.230]) by schlepper.zs64.net (8.13.1/8.12.9) with ESMTP id j7FJjqNU095775; Mon, 15 Aug 2005 21:45:52 +0200 (CEST) (envelope-from cracauer@schlepper.zs64.net) Received: (from cracauer@localhost) by schlepper.zs64.net (8.13.1/8.12.9/Submit) id j7FJjqlP095774; Mon, 15 Aug 2005 15:45:52 -0400 (EDT) (envelope-from cracauer) Date: Mon, 15 Aug 2005 15:45:52 -0400 From: Martin Cracauer To: freebsd-amd64@freebsd.org Message-ID: <20050815154552.A95576@cons.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="PEIAKu/WMn1b1Hv9" Content-Disposition: inline User-Agent: Mutt/1.2.5i Cc: freebsd-doc@freebsd.org Subject: Update for www/amd64/motherboards.sgml - please review X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 19:45:55 -0000 --PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Can somebody who has the SGML system running and is a native speaker of English please review the appended diff? It contains entries for the 4 mainboards that I tried with FreeBSD/AMD64 recently. Thanks Martin --PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=diff Content-Transfer-Encoding: quoted-printable Index: motherboards.sgml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/dcvs/www/en/platforms/amd64/motherboards.sgml,v retrieving revision 1.36 diff -u -r1.36 motherboards.sgml --- motherboards.sgml 20 Jul 2005 21:39:52 -0000 1.36 +++ motherboards.sgml 15 Aug 2005 19:40:26 -0000 @@ -46,6 +46,42 @@ Integrated NIC does not work, otherwise fully functional. + Abit + + KV8-Pro + VIA K8T800 / Socket 754 + Martin Cracauer + 6-betas, 7-current + On-board ethernet controller (vge(4)) does not work unless stati= cally compiled into kernel. Temperature and fans monitors are connected to = a custom chip, not the Winbond chip they have for voltage. They don't give = out documentation on this custom "uGuru" chip, so no Linux or FreeBSD monit= oring. Sound works just fine. No ECC memory support. I replaced it with an = Asus K8V-X which has working monitoring and ECC support. I would recommend = not giving money to people who needlessly invent cute chips and tell Linux = and FreeBSD to go stuff themself when they want to support these chips. Con= trary to common believe this is also not a very good overclocker. You need = a non-public custom BIOS to even get a working AGP/PCI lock, although the w= hole point of the K8T800-pro chipset is the ability to have that lock. + + + AccelerTech + + ATO2082 + AMD 8111/8131 chipset, dual socket 940 + Martin Cracauer + 6-betas, 7-current + Different name for the Armima Rioworks HDAMB board, see my comme= nts there. + + + Arima + + Rioworks HDAMB + AMD 8111/8131 chipset, dual socket 940 + Martin Cracauer + 6-betas, 7-current on August 2005 + Also sold under the name "AccelerTech ATO2082". Works fine. Soun= d works out of box, as do USB, firewire and SATA. Ethernet only works if co= mpiled statically into the kernel, not as a module. Memory seems slow, I ha= ve PC2100 but it is even slower than it should be with that. Temperature mo= nitoring seems broken. Suspend-to-RAM does not work. This is one of the few= normal-size ATX dual Opteron boards so that you can use a normal case. Can= be had for $120 or so on ebay. Revisions up to C0 or so do not support DDR= 400 memory (PC3200), only DDR333 (PC2700). No dual-core support. Most likel= y no support for E stepping Opterons. Note just in case: like all socket 94= 0 bords it needs registered memory. Nothing fancy or fast but a nice board = if you want it small, don't need PCI-X or PCIe and want full FreeBSD suppor= t. + + + Asus + + KVN-Deluxe + NVidia NForce 3 250 GB / Socket 754 + Martin Cracauer + 6-betas, 7-current + Don't buy this. Ethernet needs the reimplementation of a reverse= engineered Linux driver and didn't do 1000mps for me. Sound would not work= . Under Windows, the AGP port has hangs/stutter with NVidia 6x00 video card= s, in case you plan on dual-purpose with gaming. Lots of issues with Windoz= e drivers, too. Sometimes crashes hard after using PCI TV card, requiring p= ysical (PSU) powercycle. Not very fast for compilation, my Via boards are f= aster (see other entries). However, this board has the Ethernet not on the = PCI bus and under Linux (where the driver works) you can get insane speeds = of ethernet and disk, at the same time. Has ECC support, too. Still, FreeBS= D was no joy on this board. + + Asus A8N-SLI Deluxe @@ -101,6 +137,13 @@ 5.4-STABLE On-board audio untested. The on-board sk0 ethernet controller h= ad issues with 5.3-RELEASE. + Asus + + K8V-X + VIA K8T800 / Socket 754 + Martin Cracauer + 6-betas, 7-current + On-board audio works fine. The on-board sk0 ethernet works but = is slow at about 33 MB/sec. Linux does 70 MB/sec reading, 48 MB writing on = the same card so it's no hardware issue. ECC support. Drives your DDR400 me= mory in DDR333 if you have more than one module and corrupts memory if you = force it into DDR400. Only two fan connectors. I like it better than the A= bit KV8-Pro and that Asus K8N-E deluxe disgrace I had. WARNING: in the defa= ult BIOS shipped switching back and forth between forcing DDR400 and autode= tection, it would not reliably autodetect. If you go from forced memory spe= cs to autodetection load the whole BIOS-wide factory defaults first. This i= s a memory corruption issue so don't ignore this warning. Or don't play wit= h the RAM settings to start from, there was nothing to be gained here. The = board doesn't do DDR400 with two modules and it doesn't have a AGP/PCI lock= so both overclocking and RAM tuning are out. Just plug it in and leave it = alone works best here. Overall, while I list my nitpicks, this is probably = the best socket 754 board for reliable operations and complete FreeBSD supp= ort, with ECC, temperature monitoring etc. Celestica A2210-SCSI --PEIAKu/WMn1b1Hv9-- From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 20:04:10 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 17AB316A41F for ; Mon, 15 Aug 2005 20:04:10 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from peedub.jennejohn.org (Jba3f.j.pppool.de [85.74.186.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4440143D48 for ; Mon, 15 Aug 2005 20:04:09 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.4/8.11.6) with ESMTP id j7FK45LW027551; Mon, 15 Aug 2005 22:04:06 +0200 (CEST) (envelope-from garyj@jennejohn.org) Message-Id: <200508152004.j7FK45LW027551@peedub.jennejohn.org> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 To: Juergen Lock In-Reply-To: Message from Juergen Lock of "Mon, 15 Aug 2005 21:13:18 +0200." <20050815191318.GA62590@saturn.kn-bremen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Aug 2005 22:04:05 +0200 From: Gary Jennejohn Cc: freebsd-amd64@freebsd.org Subject: Re: workstation mobo X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 20:04:10 -0000 Juergen Lock writes: > On Mon, Aug 15, 2005 at 06:16:52PM +1000, ? ? wrote: > > On 8/13/05, I wrote: > >[...] > > > > I just got a new box with an Asus A8V Deluxe board (VIA K8T800 Pro, > > > Socket 939), and so far everything seems to be working. The only > > > unusual thing i had to do for FreeBSD (5.4-R) was adding a patch > > > to the sk nic driver (see other thread.) > > > > > > > Update on ASUS A8V Deluxe for archives > > > > I installed 5.4-RELEASE about April (2005) and track 5-Stable on that > > hardware straight from CVS - never had a prob with sk0 yet, it's > > worked since day one with no boot time errors. > > Yeah I was surprised too that my network didnt work out-of-the-box, > as i had read of other ppl having no problems at all with this board. > Apparently there are boards with different revisions of the sk chip > (skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) here, see other > thread for the full dmesg.) > Looks like it. I have an A8V Deluxe with skc0: Marvell Yukon Lite Gigabit Ethernet rev. A3(0x7) and never had any problems. --- Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTde From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 20:24:01 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 C077F16A41F for ; Mon, 15 Aug 2005 20:24:01 +0000 (GMT) (envelope-from ewinter@lobo.homeunix.org) Received: from lobo.homeunix.org (reverse-82-141-58-133.dialin.kamp-dsl.de [82.141.58.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE6C643D46 for ; Mon, 15 Aug 2005 20:24:00 +0000 (GMT) (envelope-from ewinter@lobo.homeunix.org) Received: from lobo.homeunix.org (localhost.homeunix.org [127.0.0.1]) by lobo.homeunix.org (8.13.3/8.13.1) with ESMTP id j7FKIMCe001207; Mon, 15 Aug 2005 22:18:22 +0200 (CEST) (envelope-from ewinter@lobo.homeunix.org) Received: (from ewinter@localhost) by lobo.homeunix.org (8.13.3/8.13.1/Submit) id j7FKIMsb001206; Mon, 15 Aug 2005 22:18:22 +0200 (CEST) (envelope-from ewinter) Date: Mon, 15 Aug 2005 22:18:22 +0200 From: "Ernst W. Winter" To: Gary Jennejohn Message-ID: <20050815201822.GB1156@lobo.homeunix.org> References: <20050815191318.GA62590@saturn.kn-bremen.de> <200508152004.j7FK45LW027551@peedub.jennejohn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200508152004.j7FK45LW027551@peedub.jennejohn.org> X-Phone: + 49-89-3075-6800 Organization: FreeBSD Evangelist X-Operating-System: FreeBSD lobo.homeunix.org 5.4-STABLE FreeBSD 5.4-STABLE User-Agent: mutt-ng/devel (FreeBSD) Cc: freebsd-amd64@freebsd.org Subject: Re: workstation mobo X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Ernst W. Winter" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Aug 2005 20:24:01 -0000 On Mon, 15 Aug 2005, Gary Jennejohn wrote: > > Juergen Lock writes: > > On Mon, Aug 15, 2005 at 06:16:52PM +1000, ? ? wrote: > > > On 8/13/05, I wrote: > > >[...] > > > > > > I just got a new box with an Asus A8V Deluxe board (VIA K8T800 Pro, > > > > Socket 939), and so far everything seems to be working. The only > > > > unusual thing i had to do for FreeBSD (5.4-R) was adding a patch > > > > to the sk nic driver (see other thread.) > > > > > > > > > > Update on ASUS A8V Deluxe for archives > > > > > > I installed 5.4-RELEASE about April (2005) and track 5-Stable on that > > > hardware straight from CVS - never had a prob with sk0 yet, it's > > > worked since day one with no boot time errors. > > > > Yeah I was surprised too that my network didnt work out-of-the-box, > > as i had read of other ppl having no problems at all with this board. > > Apparently there are boards with different revisions of the sk chip > > (skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) here, see other > > thread for the full dmesg.) > > > > Looks like it. I have an A8V Deluxe with > skc0: Marvell Yukon Lite Gigabit Ethernet rev. A3(0x7) > and never had any problems. > same here and I can't complain. It had a couple hickups with 5.4-RELEASE but was then fixed and if you update with cvsup it will be fixed. Ernst From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 20:33:25 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 1F33E16A41F for ; Mon, 15 Aug 2005 20:33:25 +0000 (GMT) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (glewis.dsl.xmission.com [166.70.56.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDEB443D49 for ; Mon, 15 Aug 2005 20:33:23 +0000 (GMT) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (localhost.eyesbeyond.com [127.0.0.1]) by misty.eyesbeyond.com (8.13.3/8.13.3) with ESMTP id j7FKXKkG008010; Mon, 15 Aug 2005 14:33:21 -0600 (MDT) (envelope-from glewis@eyesbeyond.com) Received: (from glewis@localhost) by misty.eyesbeyond.com (8.13.3/8.13.3/Submit) id j7FKXIL6008007; Mon, 15 Aug 2005 14:33:18 -0600 (MDT) (envelope-from glewis@eyesbeyond.com) X-Authentication-Warning: misty.eyesbeyond.com: glewis set sender to glewis@eyesbeyond.com using -f Date: Mon, 15 Aug 2005 14:33:18 -0600 From: Greg Lewis To: Gary Jennejohn Message-ID: <20050815203318.GA7959@misty.eyesbeyond.com> References: <20050815191318.GA62590@saturn.kn-bremen.de> <200508152004.j7FK45LW027551@peedub.jennejohn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200508152004.j7FK45LW027551@peedub.jennejohn.org> User-Agent: Mutt/1.4.2.1i Cc: Juergen Lock , freebsd-amd64@freebsd.org Subject: Re: workstation mobo X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 20:33:25 -0000 On Mon, Aug 15, 2005 at 10:04:05PM +0200, Gary Jennejohn wrote: > Juergen Lock writes: > > On Mon, Aug 15, 2005 at 06:16:52PM +1000, ? ? wrote: > > > On 8/13/05, I wrote: > > >[...] > > > > > > I just got a new box with an Asus A8V Deluxe board (VIA K8T800 Pro, > > > > Socket 939), and so far everything seems to be working. The only > > > > unusual thing i had to do for FreeBSD (5.4-R) was adding a patch > > > > to the sk nic driver (see other thread.) > > > > > > > > > > Update on ASUS A8V Deluxe for archives > > > > > > I installed 5.4-RELEASE about April (2005) and track 5-Stable on that > > > hardware straight from CVS - never had a prob with sk0 yet, it's > > > worked since day one with no boot time errors. > > > > Yeah I was surprised too that my network didnt work out-of-the-box, > > as i had read of other ppl having no problems at all with this board. > > Apparently there are boards with different revisions of the sk chip > > (skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) here, see other > > thread for the full dmesg.) > > > > Looks like it. I have an A8V Deluxe with > skc0: Marvell Yukon Lite Gigabit Ethernet rev. A3(0x7) > and never had any problems. Hmm. I have skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) and its running fine for the most part with the occasional watchdog timeout. However, this is a different motherboard (Gigabyte K8NS Ultra-939). -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 20:53:16 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 35F6016A41F; Mon, 15 Aug 2005 20:53:16 +0000 (GMT) (envelope-from ghelmer@palisadesys.com) Received: from magellan.palisadesys.com (magellan.palisadesys.com [192.188.162.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84F1343D46; Mon, 15 Aug 2005 20:53:15 +0000 (GMT) (envelope-from ghelmer@palisadesys.com) Received: from [172.16.1.108] (cetus.palisadesys.com [192.188.162.7]) (authenticated bits=0) by magellan.palisadesys.com (8.12.11/8.12.11) with ESMTP id j7FKqVNe021259; Mon, 15 Aug 2005 15:52:35 -0500 (CDT) (envelope-from ghelmer@palisadesys.com) Message-ID: <4301008F.5050604@palisadesys.com> Date: Mon, 15 Aug 2005 15:52:31 -0500 From: Guy Helmer User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Martin Cracauer References: <20050815154552.A95576@cons.org> In-Reply-To: <20050815154552.A95576@cons.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Palisade-MailScanner-Information: Please contact the ISP for more information X-Palisade-MailScanner: Found to be clean X-MailScanner-From: ghelmer@palisadesys.com Cc: freebsd-doc@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: Update for www/amd64/motherboards.sgml - please review X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 20:53:16 -0000 Martin Cracauer wrote: >Can somebody who has the SGML system running and is a native speaker >of English please review the appended diff? > >It contains entries for the 4 mainboards that I tried with >FreeBSD/AMD64 recently. > > Watch out for '&' characters in the URLs, like this one below. I managed to break the www build recently by not converting them to '&' sequences. >+ >+ KV8-Pro > > Guy -- Guy Helmer, Ph.D. Principal System Architect Palisade Systems, Inc. From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 21:08:28 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 06B1816A41F for ; Mon, 15 Aug 2005 21:08:28 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF47C43D53 for ; Mon, 15 Aug 2005 21:08:27 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 0FAA611EB9 for ; Mon, 15 Aug 2005 15:08:27 -0600 (MDT) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id B54EB11EB8 for ; Mon, 15 Aug 2005 15:08:26 -0600 (MDT) Date: Mon, 15 Aug 2005 15:08:25 -0600 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20050815150825.79226025.kgunders@teamcool.net> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: to dual core or not to dual core... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 21:08:28 -0000 ah, that is the question... It seems to me that for most normal workstation use one might well be better off w/investing in faster single core cpu than in dual core. Anybody running the dual core on desktop fbsd workstation can report? TIA -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 21:16:48 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 8B7F416A41F for ; Mon, 15 Aug 2005 21:16:48 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3529643D48 for ; Mon, 15 Aug 2005 21:16:48 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id CBF5811EB9 for ; Mon, 15 Aug 2005 15:16:47 -0600 (MDT) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 7ED6C11EB8 for ; Mon, 15 Aug 2005 15:16:47 -0600 (MDT) Date: Mon, 15 Aug 2005 15:16:46 -0600 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20050815151646.2cc3a735.kgunders@teamcool.net> In-Reply-To: <20050815150825.79226025.kgunders@teamcool.net> References: <20050815150825.79226025.kgunders@teamcool.net> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: to dual core or not to dual core... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 21:16:48 -0000 On Mon, 15 Aug 2005 15:08:25 -0600 Ken Gunderson wrote: > ah, that is the question... > > It seems to me that for most normal workstation use one might well be > better off w/investing in faster single core cpu than in dual core. > Anybody running the dual core on desktop fbsd workstation can report? Sorry to follow up on my own but I forgot to add "faster single core w/ 1MB L2 cache".... -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 21:36:21 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 B5B6A16A41F for ; Mon, 15 Aug 2005 21:36:21 +0000 (GMT) (envelope-from fcash@ocis.net) Received: from smtp.sd73.bc.ca (mailtest.sd73.bc.ca [142.24.13.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F84943D6A for ; Mon, 15 Aug 2005 21:36:20 +0000 (GMT) (envelope-from fcash@ocis.net) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id 64A0E8A0094 for ; Mon, 15 Aug 2005 14:36:20 -0700 (PDT) Received: from smtp.sd73.bc.ca ([127.0.0.1]) by localhost (mailtest.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 87823-02-13 for ; Mon, 15 Aug 2005 14:36:19 -0700 (PDT) Received: from ember.sd73.bc.ca (unknown [192.168.0.9]) by smtp.sd73.bc.ca (Postfix) with ESMTP id 5CBBD8A0084 for ; Mon, 15 Aug 2005 14:36:19 -0700 (PDT) From: Freddie Cash To: freebsd-amd64@freebsd.org Date: Mon, 15 Aug 2005 14:36:14 -0700 User-Agent: KMail/1.8.1 References: <20050815150825.79226025.kgunders@teamcool.net> In-Reply-To: <20050815150825.79226025.kgunders@teamcool.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508151436.14837.fcash@ocis.net> X-Virus-Scanned: by amavisd-new using ClamAV at sd73.bc.ca Subject: Re: to dual core or not to dual core... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 21:36:21 -0000 On August 15, 2005 02:08 pm, Ken Gunderson wrote: > ah, that is the question... > It seems to me that for most normal workstation use one might well be > better off w/investing in faster single core cpu than in dual core. > Anybody running the dual core on desktop fbsd workstation can report? Considering 95% of all Socket 939 motherboards will accept dual-core processors with nothing more than a BIOS update, get a single-code system now, and upgrade to dual-core when the prices drop. The nice thing about AMD systems is you can do that. :) Intel dual-core requires an entire new chipset/motherboard, RAM, etc. -- Freddie Cash fcash@ocis.net From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 21:54:36 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 4936D16A41F for ; Mon, 15 Aug 2005 21:54:36 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6B8C43D53 for ; Mon, 15 Aug 2005 21:54:35 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 5B4C511EB9; Mon, 15 Aug 2005 15:54:35 -0600 (MDT) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 1F5BD11EB8; Mon, 15 Aug 2005 15:54:35 -0600 (MDT) Date: Mon, 15 Aug 2005 15:54:34 -0600 From: Ken Gunderson To: Freddie Cash Message-Id: <20050815155434.08ac079e.kgunders@teamcool.net> In-Reply-To: <200508151436.14837.fcash@ocis.net> References: <20050815150825.79226025.kgunders@teamcool.net> <200508151436.14837.fcash@ocis.net> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-amd64@freebsd.org Subject: Re: to dual core or not to dual core... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 21:54:36 -0000 On Mon, 15 Aug 2005 14:36:14 -0700 Freddie Cash wrote: > On August 15, 2005 02:08 pm, Ken Gunderson wrote: > > ah, that is the question... > > > It seems to me that for most normal workstation use one might well be > > better off w/investing in faster single core cpu than in dual core. > > Anybody running the dual core on desktop fbsd workstation can report? > > Considering 95% of all Socket 939 motherboards will accept dual-core > processors with nothing more than a BIOS update, get a single-code > system now, and upgrade to dual-core when the prices drop. > > The nice thing about AMD systems is you can do that. :) Intel > dual-core requires an entire new chipset/motherboard, RAM, etc. Right on AMD being mroe better than Intel... But what I was getting at was, all other things being equal, i.e. same ballpark budget, would one be better off sacrificing cpu a few hundred MHz to go w/dual core (e.g. 2.0 GHz) or better off "investing" in single core w/more Mhz and a 1MB L2 cache (e.g. 2.4 GHz). Given that these puppies are w/in $20 of each other, I'm inclined to opt for the later. -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 21:56:03 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 1120B16A41F for ; Mon, 15 Aug 2005 21:56:03 +0000 (GMT) (envelope-from nox@saturn.kn-bremen.de) Received: from gwyn.kn-bremen.de (gwyn.kn-bremen.de [212.63.36.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10F1043D49 for ; Mon, 15 Aug 2005 21:56:01 +0000 (GMT) (envelope-from nox@saturn.kn-bremen.de) Received: from gwyn.kn-bremen.de (gwyn [127.0.0.1]) by gwyn.kn-bremen.de (8.13.4/8.13.4/Debian-3) with ESMTP id j7FLtO0p003776; Mon, 15 Aug 2005 23:55:24 +0200 Received: from saturn.kn-bremen.de (uucp@localhost) by gwyn.kn-bremen.de (8.13.4/8.13.4/Submit) with UUCP id j7FLtOSN003774; Mon, 15 Aug 2005 23:55:24 +0200 Received: from saturn.kn-bremen.de (localhost [127.0.0.1]) by saturn.kn-bremen.de (8.13.1/8.13.1) with ESMTP id j7FLra2J066242; Mon, 15 Aug 2005 23:53:36 +0200 (CEST) (envelope-from nox@saturn.kn-bremen.de) Received: (from nox@localhost) by saturn.kn-bremen.de (8.13.1/8.13.1/Submit) id j7FLrZjZ066241; Mon, 15 Aug 2005 23:53:35 +0200 (CEST) (envelope-from nox) From: Juergen Lock Date: Mon, 15 Aug 2005 23:53:34 +0200 To: Greg Lewis Message-ID: <20050815215334.GB65728@saturn.kn-bremen.de> Mail-Followup-To: Greg Lewis , Gary Jennejohn , freebsd-amd64@freebsd.org References: <20050815191318.GA62590@saturn.kn-bremen.de> <200508152004.j7FK45LW027551@peedub.jennejohn.org> <20050815203318.GA7959@misty.eyesbeyond.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050815203318.GA7959@misty.eyesbeyond.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: workstation mobo X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 21:56:03 -0000 On Mon, Aug 15, 2005 at 02:33:18PM -0600, Greg Lewis wrote: > On Mon, Aug 15, 2005 at 10:04:05PM +0200, Gary Jennejohn wrote: > > Juergen Lock writes: > > > On Mon, Aug 15, 2005 at 06:16:52PM +1000, ? ? wrote: > > > > On 8/13/05, I wrote: > > > >[...] > > > > > > > > I just got a new box with an Asus A8V Deluxe board (VIA K8T800 Pro, > > > > > Socket 939), and so far everything seems to be working. The only > > > > > unusual thing i had to do for FreeBSD (5.4-R) was adding a patch > > > > > to the sk nic driver (see other thread.) > > > > > > > > > > > > > Update on ASUS A8V Deluxe for archives > > > > > > > > I installed 5.4-RELEASE about April (2005) and track 5-Stable on that > > > > hardware straight from CVS - never had a prob with sk0 yet, it's > > > > worked since day one with no boot time errors. > > > > > > Yeah I was surprised too that my network didnt work out-of-the-box, > > > as i had read of other ppl having no problems at all with this board. > > > Apparently there are boards with different revisions of the sk chip > > > (skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) here, see other > > > thread for the full dmesg.) > > > > > > > Looks like it. I have an A8V Deluxe with > > skc0: Marvell Yukon Lite Gigabit Ethernet rev. A3(0x7) > > and never had any problems. > > Hmm. I have > > skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) > > and its running fine for the most part with the occasional watchdog timeout. > Hmm. Maybe it also has something to do with to what it is connected, is yours on a gig switch too? > However, this is a different motherboard (Gigabyte K8NS Ultra-939). Well or something on the board is different. Juergen From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 22:03:34 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org 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 0957016A41F for ; Mon, 15 Aug 2005 22:03:34 +0000 (GMT) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (glewis.dsl.xmission.com [166.70.56.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id C860643D46 for ; Mon, 15 Aug 2005 22:03:32 +0000 (GMT) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (localhost.eyesbeyond.com [127.0.0.1]) by misty.eyesbeyond.com (8.13.3/8.13.3) with ESMTP id j7FM3UbW009058; Mon, 15 Aug 2005 16:03:30 -0600 (MDT) (envelope-from glewis@eyesbeyond.com) Received: (from glewis@localhost) by misty.eyesbeyond.com (8.13.3/8.13.3/Submit) id j7FM3TFj009057; Mon, 15 Aug 2005 16:03:29 -0600 (MDT) (envelope-from glewis@eyesbeyond.com) X-Authentication-Warning: misty.eyesbeyond.com: glewis set sender to glewis@eyesbeyond.com using -f Date: Mon, 15 Aug 2005 16:03:29 -0600 From: Greg Lewis To: Juergen Lock Message-ID: <20050815220329.GB8917@misty.eyesbeyond.com> References: <20050815191318.GA62590@saturn.kn-bremen.de> <200508152004.j7FK45LW027551@peedub.jennejohn.org> <20050815203318.GA7959@misty.eyesbeyond.com> <20050815215334.GB65728@saturn.kn-bremen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050815215334.GB65728@saturn.kn-bremen.de> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@FreeBSD.org Subject: Re: workstation mobo X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 22:03:34 -0000 On Mon, Aug 15, 2005 at 11:53:34PM +0200, Juergen Lock wrote: > On Mon, Aug 15, 2005 at 02:33:18PM -0600, Greg Lewis wrote: > > Hmm. I have > > > > skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) > > > > and its running fine for the most part with the occasional watchdog timeout. > > > Hmm. Maybe it also has something to do with to what it is connected, > is yours on a gig switch too? Now that you mention it, its actually connected to a 10/100 switch. I can't readily get a GigE switch to test it against at the moment. > > However, this is a different motherboard (Gigabyte K8NS Ultra-939). > > Well or something on the board is different. Could be. -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org > On Mon, Aug 15, 2005 at 02:33:18PM -0600, Greg Lewis wrote: > > On Mon, Aug 15, 2005 at 10:04:05PM +0200, Gary Jennejohn wrote: > > > Juergen Lock writes: > > > > On Mon, Aug 15, 2005 at 06:16:52PM +1000, ? ? wrote: > > > > > On 8/13/05, I wrote: > > > > >[...] > > > > > > > > > > I just got a new box with an Asus A8V Deluxe board (VIA K8T800 Pro, > > > > > > Socket 939), and so far everything seems to be working. The only > > > > > > unusual thing i had to do for FreeBSD (5.4-R) was adding a patch > > > > > > to the sk nic driver (see other thread.) > > > > > > > > > > > > > > > > Update on ASUS A8V Deluxe for archives > > > > > > > > > > I installed 5.4-RELEASE about April (2005) and track 5-Stable on that > > > > > hardware straight from CVS - never had a prob with sk0 yet, it's > > > > > worked since day one with no boot time errors. > > > > > > > > Yeah I was surprised too that my network didnt work out-of-the-box, > > > > as i had read of other ppl having no problems at all with this board. > > > > Apparently there are boards with different revisions of the sk chip > > > > (skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) here, see other > > > > thread for the full dmesg.) > > > > > > > > > > Looks like it. I have an A8V Deluxe with > > > skc0: Marvell Yukon Lite Gigabit Ethernet rev. A3(0x7) > > > and never had any problems. > > > > Hmm. I have > > > > skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) > > > > and its running fine for the most part with the occasional watchdog timeout. > > > Hmm. Maybe it also has something to do with to what it is connected, > is yours on a gig switch too? > > > However, this is a different motherboard (Gigabyte K8NS Ultra-939). > > Well or something on the board is different. > > Juergen -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 22:07:19 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 EEC1C16A41F for ; Mon, 15 Aug 2005 22:07:19 +0000 (GMT) (envelope-from fcash@ocis.net) Received: from smtp.sd73.bc.ca (smtp.sd73.bc.ca [142.24.13.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A5DE43D45 for ; Mon, 15 Aug 2005 22:07:19 +0000 (GMT) (envelope-from fcash@ocis.net) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id DD53E8A009C for ; Mon, 15 Aug 2005 15:07:19 -0700 (PDT) Received: from smtp.sd73.bc.ca ([127.0.0.1]) by localhost (mailtest.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 89927-01-25 for ; Mon, 15 Aug 2005 15:07:17 -0700 (PDT) Received: from ember.sd73.bc.ca (unknown [192.168.0.9]) by smtp.sd73.bc.ca (Postfix) with ESMTP id 5EBBC8A0094 for ; Mon, 15 Aug 2005 15:07:17 -0700 (PDT) From: Freddie Cash To: freebsd-amd64@freebsd.org Date: Mon, 15 Aug 2005 15:07:12 -0700 User-Agent: KMail/1.8.1 References: <20050815150825.79226025.kgunders@teamcool.net> <200508151436.14837.fcash@ocis.net> <20050815155434.08ac079e.kgunders@teamcool.net> In-Reply-To: <20050815155434.08ac079e.kgunders@teamcool.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508151507.12738.fcash@ocis.net> X-Virus-Scanned: by amavisd-new using ClamAV at sd73.bc.ca Subject: Re: to dual core or not to dual core... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 22:07:20 -0000 On August 15, 2005 02:54 pm, you wrote: > On Mon, 15 Aug 2005 14:36:14 -0700 > > Freddie Cash wrote: > > On August 15, 2005 02:08 pm, Ken Gunderson wrote: > > > ah, that is the question... > > > > > > It seems to me that for most normal workstation use one might > > > well be better off w/investing in faster single core cpu than in > > > dual core. Anybody running the dual core on desktop fbsd > > > workstation can report? > > > > Considering 95% of all Socket 939 motherboards will accept > > dual-core processors with nothing more than a BIOS update, get a > > single-code system now, and upgrade to dual-core when the prices > > drop. > > > > The nice thing about AMD systems is you can do that. :) Intel > > dual-core requires an entire new chipset/motherboard, RAM, etc. > > Right on AMD being mroe better than Intel... But what I was getting > at was, all other things being equal, i.e. same ballpark budget, > would one be better off sacrificing cpu a few hundred MHz to go > w/dual core (e.g. 2.0 GHz) or better off "investing" in single core > w/more Mhz and a 1MB L2 cache (e.g. 2.4 GHz). Given that these > puppies are w/in $20 of each other, I'm inclined to opt for the > later. Depends on your workload. :) If you tend to run only 1 or 2 large programs at a time, with nothing running in the background, and if those apps are single-threaded, then you may be better off with a faster single-code CPU. Especially if you are into gaming, as the vast majority of those are still primarily single-threaded, and the Athlon64 FX is still the premier gaming CPU. However, if you tend to have a thousand different apps loaded, and they are all chugging away in the background doing various things, and you like to multitask (write docs, compile code, listen to music, rip CDs, etc), then a dual-core system will be a better fit. One thing to watch for with the dual-core Athlon64 X2s is the amount of cache. The only difference between some of the models is the amount of L2; the actual processor speed is the same. -- Freddie Cash fcash@ocis.net From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 22:13:47 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 CAEE516A41F for ; Mon, 15 Aug 2005 22:13:47 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from peedub.jennejohn.org (Ja3e3.j.pppool.de [85.74.163.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17E6543D45 for ; Mon, 15 Aug 2005 22:13:46 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.4/8.11.6) with ESMTP id j7FMDdbE029303; Tue, 16 Aug 2005 00:13:44 +0200 (CEST) (envelope-from garyj@jennejohn.org) Message-Id: <200508152213.j7FMDdbE029303@peedub.jennejohn.org> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 To: Ken Gunderson In-Reply-To: Message from Ken Gunderson of "Mon, 15 Aug 2005 15:54:34 MDT." <20050815155434.08ac079e.kgunders@teamcool.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 Aug 2005 00:13:39 +0200 From: Gary Jennejohn Cc: freebsd-amd64@freebsd.org Subject: Re: to dual core or not to dual core... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 22:13:47 -0000 Ken Gunderson writes: > On Mon, 15 Aug 2005 14:36:14 -0700 > Freddie Cash wrote: > > > On August 15, 2005 02:08 pm, Ken Gunderson wrote: > > > ah, that is the question... > > > > > It seems to me that for most normal workstation use one might well be > > > better off w/investing in faster single core cpu than in dual core. > > > Anybody running the dual core on desktop fbsd workstation can report? > > > > Considering 95% of all Socket 939 motherboards will accept dual-core > > processors with nothing more than a BIOS update, get a single-code > > system now, and upgrade to dual-core when the prices drop. > > > > The nice thing about AMD systems is you can do that. :) Intel > > dual-core requires an entire new chipset/motherboard, RAM, etc. > Right on AMD being mroe better than Intel... But what I was getting at > was, all other things being equal, i.e. same ballpark budget, would one > be better off sacrificing cpu a few hundred MHz to go w/dual core (e.g. > 2.0 GHz) or better off "investing" in single core w/more Mhz and a 1MB > L2 cache (e.g. 2.4 GHz). Given that these puppies are w/in $20 of > each other, I'm inclined to opt for the later. > I used to have a single core 3200+ (2200 MHz and 512 kB cache) in my ASUS A8V Deluxe. I then put a low-end X2 into it (also 2200 Mhz and with 512 kB cache) and my build worlds are now twice as fast! :-) SMP does have its benefits. The only drawback was that I had to replace my RADEON card with an NVIDIA due to stability problems in SMP mode. Since I run mostly in 32-bit mode the nvidia-driver port works OK for me. However, that would not be an option in 64-bit mode! --- Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTde From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 22:28:22 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 304C616A41F for ; Mon, 15 Aug 2005 22:28:22 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7F4643D45 for ; Mon, 15 Aug 2005 22:28:21 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id F07CA11EB9; Mon, 15 Aug 2005 16:28:20 -0600 (MDT) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id B273211EB8; Mon, 15 Aug 2005 16:28:20 -0600 (MDT) Date: Mon, 15 Aug 2005 16:28:19 -0600 From: Ken Gunderson To: Freddie Cash Message-Id: <20050815162819.4ea85f42.kgunders@teamcool.net> In-Reply-To: <200508151507.12738.fcash@ocis.net> References: <20050815150825.79226025.kgunders@teamcool.net> <200508151436.14837.fcash@ocis.net> <20050815155434.08ac079e.kgunders@teamcool.net> <200508151507.12738.fcash@ocis.net> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-amd64@freebsd.org Subject: Re: to dual core or not to dual core... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 22:28:22 -0000 On Mon, 15 Aug 2005 15:07:12 -0700 Freddie Cash wrote: > On August 15, 2005 02:54 pm, you wrote: > > On Mon, 15 Aug 2005 14:36:14 -0700 > > > > Freddie Cash wrote: > > > On August 15, 2005 02:08 pm, Ken Gunderson wrote: > > > > ah, that is the question... [snippage] > Depends on your workload. :) > > If you tend to run only 1 or 2 large programs at a time, with nothing > running in the background, and if those apps are single-threaded, then > you may be better off with a faster single-code CPU. Especially if you > are into gaming, as the vast majority of those are still primarily > single-threaded, and the Athlon64 FX is still the premier gaming CPU. > > However, if you tend to have a thousand different apps loaded, and they > are all chugging away in the background doing various things, and you > like to multitask (write docs, compile code, listen to music, rip CDs, > etc), then a dual-core system will be a better fit. > > One thing to watch for with the dual-core Athlon64 X2s is the amount of > cache. The only difference between some of the models is the amount of > L2; the actual processor speed is the same. So I've noticed;-) The only benches I've seen are for Winblows and seem to be about 20-30 % increase for high multitasking. I DO tend to have a lot of apps open and doing several things at once but, as you point out, it also depends on how those apps are coded. For example, I don't notice my old dual PIII 450 taking advantage of the 2nd cpu much under X... Anyhow, thanks for your input. Was hoping that maybe someone w/a dual core rig could perhaps share some real world fbsd experience... -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Mon Aug 15 22:38:52 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 989EE16A41F for ; Mon, 15 Aug 2005 22:38:52 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC56E43D60 for ; Mon, 15 Aug 2005 22:38:48 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper [212.12.50.230]) by schlepper.zs64.net (8.13.1/8.12.9) with ESMTP id j7FMclbb099249; Tue, 16 Aug 2005 00:38:47 +0200 (CEST) (envelope-from cracauer@schlepper.zs64.net) Received: (from cracauer@localhost) by schlepper.zs64.net (8.13.1/8.12.9/Submit) id j7FMckKC099248; Mon, 15 Aug 2005 18:38:46 -0400 (EDT) (envelope-from cracauer) Date: Mon, 15 Aug 2005 18:38:46 -0400 From: Martin Cracauer To: Steve Kargl Message-ID: <20050815183846.A99145@cons.org> References: <20050815125657.A92343@cons.org> <20050815172250.GA32804@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20050815172250.GA32804@troutmask.apl.washington.edu>; from sgk@troutmask.apl.washington.edu on Mon, Aug 15, 2005 at 10:22:50AM -0700 Cc: Martin Cracauer , freebsd-amd64@freebsd.org Subject: Re: 4 GB RAM showing up as 3, BIOS memory hole and all that X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Aug 2005 22:38:52 -0000 Steve Kargl wrote on Mon, Aug 15, 2005 at 10:22:50AM -0700: > On Mon, Aug 15, 2005 at 12:56:57PM -0400, Martin Cracauer wrote: > > > > I have a Dual Opteron board with 4x 1 GB RAM. The memory count in the > > BIOS goes up to 640 KB + 3072 MB, and FreeBSD says it sees 3 GB. > > (snip) > > > Any way to get my GB back? > > This should be a FAQ. No, you can't get it back. > David O'brien has explained this more than once in > the freebsd-amd64 list. Unfortunately, I don't > have a handy URL for you to read. I suggest scanning > the list for posts by David in the Feb to May timeframe. Sorry, I just read every message David posted to amd64@ since January 2004 and I have only seen a reference that it has been explained too often :-) He also said that you only lose the space from 3.5-4 GB, not the full GB, and that the board can re-map that physical memory to > 4 GB. http://groups-beta.google.com/group/fa.freebsd.stable/browse_frm/thread/9dc99b2be7f23d4/2d6de607055b020d?lnk=st&q=freebsd-amd64+david+%224+gb%22&rnum=7&hl=en#2d6de607055b020d Any further hints what to look for? I am sure I did a decent scan of the archive (both local and on google groups). Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ No warranty. This email is probably produced by one of my cats stepping on the keys. No, I don't have an infinite number of cats. From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 16 00:55:20 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org 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 D182916A41F; Tue, 16 Aug 2005 00:55:20 +0000 (GMT) (envelope-from marcel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EDEF43D46; Tue, 16 Aug 2005 00:55:20 +0000 (GMT) (envelope-from marcel@FreeBSD.org) Received: from freefall.freebsd.org (marcel@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7G0tKhq019040; Tue, 16 Aug 2005 00:55:20 GMT (envelope-from marcel@freefall.freebsd.org) Received: (from marcel@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7G0tKZG019036; Tue, 16 Aug 2005 00:55:20 GMT (envelope-from marcel) Date: Tue, 16 Aug 2005 00:55:20 GMT From: Marcel Moolenaar Message-Id: <200508160055.j7G0tKZG019036@freefall.freebsd.org> To: marcel@FreeBSD.org, freebsd-ia64@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/84693: Keyboard not recognized during first step of install (Elite model ECS 755-A/A2) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Aug 2005 00:55:21 -0000 Synopsis: Keyboard not recognized during first step of install (Elite model ECS 755-A/A2) Responsible-Changed-From-To: freebsd-ia64->freebsd-amd64 Responsible-Changed-By: marcel Responsible-Changed-When: Tue Aug 16 00:54:52 GMT 2005 Responsible-Changed-Why: Misfiled PR. http://www.freebsd.org/cgi/query-pr.cgi?pr=84693 From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 16 05:04:38 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 714CC16A41F for ; Tue, 16 Aug 2005 05:04:38 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBB1043D46 for ; Tue, 16 Aug 2005 05:04:35 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [172.20.101.145] ([12.167.156.2]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j7G5FdAq043075; Mon, 15 Aug 2005 23:15:40 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <430173BE.4080802@samsco.org> Date: Mon, 15 Aug 2005 23:03:58 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Martin Cracauer References: <20050815125657.A92343@cons.org> <20050815172250.GA32804@troutmask.apl.washington.edu> <20050815183846.A99145@cons.org> In-Reply-To: <20050815183846.A99145@cons.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: freebsd-amd64@freebsd.org Subject: Re: 4 GB RAM showing up as 3, BIOS memory hole and all that X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Aug 2005 05:04:38 -0000 Martin Cracauer wrote: > Steve Kargl wrote on Mon, Aug 15, 2005 at 10:22:50AM -0700: > >>On Mon, Aug 15, 2005 at 12:56:57PM -0400, Martin Cracauer wrote: >> >>>I have a Dual Opteron board with 4x 1 GB RAM. The memory count in the >>>BIOS goes up to 640 KB + 3072 MB, and FreeBSD says it sees 3 GB. >> >>(snip) >> >> >>>Any way to get my GB back? >> >>This should be a FAQ. No, you can't get it back. >>David O'brien has explained this more than once in >>the freebsd-amd64 list. Unfortunately, I don't >>have a handy URL for you to read. I suggest scanning >>the list for posts by David in the Feb to May timeframe. > > > Sorry, I just read every message David posted to amd64@ since January > 2004 and I have only seen a reference that it has been explained too > often :-) He also said that you only lose the space from 3.5-4 GB, not > the full GB, and that the board can re-map that physical memory to > 4 > GB. > > http://groups-beta.google.com/group/fa.freebsd.stable/browse_frm/thread/9dc99b2be7f23d4/2d6de607055b020d?lnk=st&q=freebsd-amd64+david+%224+gb%22&rnum=7&hl=en#2d6de607055b020d > > Any further hints what to look for? I am sure I did a decent scan of > the archive (both local and on google groups). > > Martin You are definitely going to loose the address space from 3.75GB to 4GB to normal PCI and APIC overhead. If you have PCI Express then you'll likely also loose the space from 3.5 to 3.75GB. Any other space lost beyond that would be possible but usual. And no, most AMD systems do *NOT* remap the lost space. If you want a detailed analysis then please send a verbose boot message along with a pointer to the specs on your motherboard. That will give enough to information to say if FreeBSD is at fault or if your motherboard is simply sub-standard. Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 16 08:14:06 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 8F99516A41F for ; Tue, 16 Aug 2005 08:14:06 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from peedub.jennejohn.org (Jaf1e.j.pppool.de [85.74.175.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6D1943D45 for ; Tue, 16 Aug 2005 08:14:05 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.4/8.11.6) with ESMTP id j7G8DxIt004943; Tue, 16 Aug 2005 10:13:59 +0200 (CEST) (envelope-from garyj@jennejohn.org) Message-Id: <200508160813.j7G8DxIt004943@peedub.jennejohn.org> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 To: freebsd-amd64@freebsd.org From: Gary Jennejohn Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 Aug 2005 10:13:59 +0200 Sender: garyj@jennejohn.org Cc: Subject: Re: to dual core or not to dual core... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Aug 2005 08:14:06 -0000 Ken Gunderson writes > Anyhow, thanks for your input. Was hoping that maybe someone w/a dual > core rig could perhaps share some real world fbsd experience... Here are some things which I've noticed a) building ports in parallel is a much more pleasant experience. b) transcoding movies with dvdrip is much faster if one uses two passes because the first pass uses both cores and takes only about 1/3 as long. The second pass only seems to use one core, but that leaves the second core free to do other things. c) buildworld takes only half the time with -j2. I've tried higher -jX values but > 2 showed no real benefit. I have seen in top that the X server seems to run on one core while other things, e.g. a terminal, run on a different core. That can be good if the terminal is displaying lots of trace, for example. -- Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTde From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 16 10:00:38 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org 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 9430A16A41F for ; Tue, 16 Aug 2005 10:00:38 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 611DE43D46 for ; Tue, 16 Aug 2005 10:00:38 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7GA0cZe096483 for ; Tue, 16 Aug 2005 10:00:38 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7GA0cxT096482; Tue, 16 Aug 2005 10:00:38 GMT (envelope-from gnats) Date: Tue, 16 Aug 2005 10:00:38 GMT Message-Id: <200508161000.j7GA0cxT096482@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Giorgos Keramidas Cc: Subject: Re: kern/84930: something wrong with msdosfs on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Giorgos Keramidas List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Aug 2005 10:00:38 -0000 The following reply was made to PR amd64/84930; it has been noted by GNATS. From: Giorgos Keramidas To: "Mikhail T." Cc: bug-followup@freebsd.org Subject: Re: kern/84930: something wrong with msdosfs on amd64 Date: Tue, 16 Aug 2005 02:43:15 +0300 On 2005-08-14 15:14, "Mikhail T." wrote: > I just tried to move some songs over to the IRiver MP3-player. > USB code recognized the device: > > da1 at umass-sim0 bus 0 target 0 lun 0 > da1: Fixed Direct Access SCSI-0 device > da1: 1.000MB/s transfers > da1: 38147MB (78126048 512 byte sectors: 255H 63S/T 4863C) > > and I was able to mount it: > > % mount -t msdosfs /dev/da1s1 /iriver > > The drive on it is just over half-full and df confirms it: > > /dev/da1s1 39052512 19902080 19150432 51% /iriver > > Yet, when I tried to list the contents of the drive, I saw nothing: > > % ls -l /iriver > total 0 > > Another system -- i386 running 5.4-stable from April 23 -- had no > problems and is busy copying the files as I type this. > > >How-To-Repeat: > > Try to write to an msdosfs on amd64. This may be unrelated, but I'm successfully using a JetFlash USB stick to move small amounts of data between my i386 7.0-CURRENT workstation and my amd64 laptop. So far things seem to work fine, so it may be a bug that is not related to msdosfs. Another thought is that I had similar problems with msdosfs and cd9660 filesystems when I tried to read their contents from a root shell (which doesn't have any LC_XXX or LANG environment vars), especially when the filesystem contained Greek filenames. Setting up the correct locale fixed everything. I'm not saying that nothing is wrong with msdosfs on amd64. Just adding what I've seen so far, in case it helps track down the cause of your problems. Regards, Giorgos From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 16 12:17:02 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 EEFFA16A41F for ; Tue, 16 Aug 2005 12:17:02 +0000 (GMT) (envelope-from franklinux392@yahoo.com) Received: from web54306.mail.yahoo.com (web54306.mail.yahoo.com [206.190.49.116]) by mx1.FreeBSD.org (Postfix) with SMTP id 4CE6243D46 for ; Tue, 16 Aug 2005 12:17:02 +0000 (GMT) (envelope-from franklinux392@yahoo.com) Received: (qmail 74818 invoked by uid 60001); 16 Aug 2005 12:17:01 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=fUAsn/+DHp4DXAC/crxI3lSMYhktja/jt/Rc7vFJ9KjzF4Z+DuAAwMJoDWKTv3JIETrBpF7e7oNxjg0Sz0NDH7ugJffeKieyNERd5fAyd2qJxgVcakaaC4cWNrA9qipP3Pg7CukYl2QQ0PjX+2bFDAfXRUkULCijA6EqkNxeEA8= ; Message-ID: <20050816121701.74816.qmail@web54306.mail.yahoo.com> Received: from [64.136.49.225] by web54306.mail.yahoo.com via HTTP; Tue, 16 Aug 2005 05:17:01 PDT Date: Tue, 16 Aug 2005 05:17:01 -0700 (PDT) From: "Frank S." To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Hi X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Aug 2005 12:17:03 -0000 Hi I want to start using freebsd, and i'm not sure if it will work on my system, I have a asus A8V-E Deluxe motherboard and Ati pci expres video card X700 Pro. thank you Frank --------------------------------- Start your day with Yahoo! - make it your home page From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 16 13:01:51 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 2E57616A41F for ; Tue, 16 Aug 2005 13:01:51 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id A602A43D46 for ; Tue, 16 Aug 2005 13:01:50 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [172.20.101.145] ([12.167.156.2]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j7GDCuK2045273; Tue, 16 Aug 2005 07:12:57 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4301E39F.1050500@samsco.org> Date: Tue, 16 Aug 2005 07:01:19 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Frank S." References: <20050816121701.74816.qmail@web54306.mail.yahoo.com> In-Reply-To: <20050816121701.74816.qmail@web54306.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: freebsd-amd64@freebsd.org Subject: Re: Hi X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Aug 2005 13:01:51 -0000 Frank S. wrote: > Hi > I want to start using freebsd, and i'm not sure if it will work on my system, I have a asus A8V-E Deluxe motherboard and Ati pci expres video card X700 Pro. > thank you > > Frank > > I have almost the same system, but with an X600 card. It works fine with the exception of the on-board network controllers. As long as you're willing to drop in an alternate network card, it's a very good board. Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 16 15:14:33 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 D0A4116A41F for ; Tue, 16 Aug 2005 15:14:33 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 384A843D45 for ; Tue, 16 Aug 2005 15:14:32 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper [212.12.50.230]) by schlepper.zs64.net (8.13.1/8.12.9) with ESMTP id j7GFEV10024526; Tue, 16 Aug 2005 17:14:31 +0200 (CEST) (envelope-from cracauer@schlepper.zs64.net) Received: (from cracauer@localhost) by schlepper.zs64.net (8.13.1/8.12.9/Submit) id j7GFES4Z024525; Tue, 16 Aug 2005 11:14:28 -0400 (EDT) (envelope-from cracauer) Date: Tue, 16 Aug 2005 11:14:28 -0400 From: Martin Cracauer To: Scott Long Message-ID: <20050816111428.A24284@cons.org> References: <20050815125657.A92343@cons.org> <20050815172250.GA32804@troutmask.apl.washington.edu> <20050815183846.A99145@cons.org> <430173BE.4080802@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <430173BE.4080802@samsco.org>; from scottl@samsco.org on Mon, Aug 15, 2005 at 11:03:58PM -0600 Cc: Martin Cracauer , freebsd-amd64@freebsd.org Subject: Re: 4 GB RAM showing up as 3, BIOS memory hole and all that X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Aug 2005 15:14:33 -0000 > You are definitely going to loose the address space from 3.75GB to 4GB > to normal PCI and APIC overhead. If you have PCI Express then you'll > likely also loose the space from 3.5 to 3.75GB. Any other space lost > beyond that would be possible but usual. And no, most AMD systems do > *NOT* remap the lost space. > > If you want a detailed analysis then please send a verbose boot message > along with a pointer to the specs on your motherboard. That will give > enough to information to say if FreeBSD is at fault or if your > motherboard is simply sub-standard. If you have time for explanations I would rather be interested to know how the above situation works in the case that you *don't* have 4 GB of RAM. Correct me if I'm wrong but: - the above 3.5 to 4.0 GB addresses are physical, not virtual - if you have less than 3.5 GB there is no physical memory at these addresses that PCI and APIC need - but if you have 4 GB there is physical memory at these addresses I don't understand how this can transparently work with and without physical RAM at 3.5-4.0 GB. I am not worrying too much about my particular board, and in any case I just fatfingered a BIOS update and it won't POST :-) It's a Arima Rioworks HDAMB http://www.rioworks.com/HDAMB.htm If people are interested I can send the boot -v afer I recover. Thanks Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ No warranty. This email is probably produced by one of my cats stepping on the keys. No, I don't have an infinite number of cats. From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 16 15:21:21 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 27A6316A420 for ; Tue, 16 Aug 2005 15:21:21 +0000 (GMT) (envelope-from ethemind@gmail.com) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DCF743D49 for ; Tue, 16 Aug 2005 15:21:19 +0000 (GMT) (envelope-from ethemind@gmail.com) Received: by rproxy.gmail.com with SMTP id r35so1031517rna for ; Tue, 16 Aug 2005 08:21:18 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:disposition-notification-to:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=G52a3aO4zMVJ/GYt/nmbeKmL2o00UY5WPHK4r3Dxlc84zNA87tsnBT17sMjnNLtU7t8atM0+EeffR5CPrinMwsFDU7XR6x8ktdy7AAvfD3Pl8hBRzgWUrFq0Tr2aJiBp3yhKDx2nigFXZ+C6FL13qktfKdyVyIcVH4nAFf1Ab4g= Received: by 10.38.151.24 with SMTP id y24mr1881479rnd; Tue, 16 Aug 2005 08:21:18 -0700 (PDT) Received: from ?194.186.247.88? ([194.186.247.88]) by mx.gmail.com with ESMTP id 79sm1108845rnc.2005.08.16.08.21.16; Tue, 16 Aug 2005 08:21:18 -0700 (PDT) Message-ID: <4302047F.4020401@gmail.com> Date: Tue, 16 Aug 2005 19:21:35 +0400 From: Ethereal mind User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: ru-ru, ru MIME-Version: 1.0 To: Scott Long , freebsd-amd64@freebsd.org References: <20050816121701.74816.qmail@web54306.mail.yahoo.com> <4301E39F.1050500@samsco.org> In-Reply-To: <4301E39F.1050500@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Hi X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Aug 2005 15:21:21 -0000 Frank S. wrote: >> Hi I want to start using freebsd, and i'm not sure if it will work on >> my system, I have a asus A8V-E Deluxe motherboard and Ati pci expres >> video card X700 Pro. >> thank you >> Frank >> >> > > > I have almost the same system, but with an X600 card. It works fine > with the exception of the on-board network controllers. As long as > you're willing to drop in an alternate network card, it's a very > good board. > > Scott > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > Do you have your video card working? I mean graphic acceleration. From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 16 15:24:03 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 6EECC16A41F for ; Tue, 16 Aug 2005 15:24:03 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACDFE43D48 for ; Tue, 16 Aug 2005 15:23:58 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [157.185.81.167] ([158.69.81.167]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j7GFZ2WZ045909; Tue, 16 Aug 2005 09:35:02 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <43020508.4090407@samsco.org> Date: Tue, 16 Aug 2005 11:23:52 -0400 From: Scott Long User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ethereal mind References: <20050816121701.74816.qmail@web54306.mail.yahoo.com> <4301E39F.1050500@samsco.org> <4302047F.4020401@gmail.com> In-Reply-To: <4302047F.4020401@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: freebsd-amd64@freebsd.org Subject: Re: Hi X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Aug 2005 15:24:03 -0000 Ethereal mind wrote: > Frank S. wrote: > >>> Hi I want to start using freebsd, and i'm not sure if it will work on >>> my system, I have a asus A8V-E Deluxe motherboard and Ati pci expres >>> video card X700 Pro. >>> thank you Frank >>> >>> >> >> >> >> I have almost the same system, but with an X600 card. It works fine >> with the exception of the on-board network controllers. As long as >> you're willing to drop in an alternate network card, it's a very >> good board. >> >> Scott >> _______________________________________________ >> freebsd-amd64@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 >> To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" >> > Do you have your video card working? I mean graphic acceleration. > No. Apparently the latest X11 DRI/DRM code will work with an AGP R3xx card, but not a PCI-E R3xx card. I don't know the status beyond that. Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 16 15:46:43 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 5EC1816A41F for ; Tue, 16 Aug 2005 15:46:43 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05AB943D45 for ; Tue, 16 Aug 2005 15:46:42 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 77EA011EB9; Tue, 16 Aug 2005 09:46:37 -0600 (MDT) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 370C011EB8; Tue, 16 Aug 2005 09:46:37 -0600 (MDT) Date: Tue, 16 Aug 2005 09:46:36 -0600 From: Ken Gunderson To: Scott Long Message-Id: <20050816094636.17ce5e3e.kgunders@teamcool.net> In-Reply-To: <43020508.4090407@samsco.org> References: <20050816121701.74816.qmail@web54306.mail.yahoo.com> <4301E39F.1050500@samsco.org> <4302047F.4020401@gmail.com> <43020508.4090407@samsco.org> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-amd64@freebsd.org Subject: Re: Hi X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Aug 2005 15:46:43 -0000 On Tue, 16 Aug 2005 11:23:52 -0400 Scott Long wrote: > Ethereal mind wrote: > > Frank S. wrote: > > > >>> Hi I want to start using freebsd, and i'm not sure if it will work on > >>> my system, I have a asus A8V-E Deluxe motherboard and Ati pci expres > >>> video card X700 Pro. > >>> thank you Frank > >>> > >>> > >> > >> > >> > >> I have almost the same system, but with an X600 card. It works fine > >> with the exception of the on-board network controllers. As long as > >> you're willing to drop in an alternate network card, it's a very > >> good board. > >> > >> Scott > >> _______________________________________________ > >> freebsd-amd64@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > >> To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > >> > > Do you have your video card working? I mean graphic acceleration. > > > > No. Apparently the latest X11 DRI/DRM code will work with an AGP R3xx > card, but not a PCI-E R3xx card. I don't know the status beyond that. Good toknow. Per the radeon manpage pcie falls back to pci: PCIE -- PCI Express (falls back to PCI at present) (used only when DRI is enabled) So I took that to mean that DRI worked.... -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 16 16:01:11 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org 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 692F516A41F for ; Tue, 16 Aug 2005 16:01:11 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0838943D48 for ; Tue, 16 Aug 2005 16:01:10 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id j7GG4nMX003558; Tue, 16 Aug 2005 12:04:50 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-amd64@FreeBSD.org Date: Tue, 16 Aug 2005 12:00:51 -0400 User-Agent: KMail/1.6.2 References: <20050816121701.74816.qmail@web54306.mail.yahoo.com> <43020508.4090407@samsco.org> <20050816094636.17ce5e3e.kgunders@teamcool.net> In-Reply-To: <20050816094636.17ce5e3e.kgunders@teamcool.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200508161200.54824.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.85.1/1023/Mon Aug 15 16:15:08 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Subject: Re: Hi X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Aug 2005 16:01:11 -0000 On Tuesday 16 August 2005 11:46 am, Ken Gunderson wrote: > On Tue, 16 Aug 2005 11:23:52 -0400 > > Scott Long wrote: > > No. Apparently the latest X11 DRI/DRM code will work with an AGP > > R3xx card, but not a PCI-E R3xx card. I don't know the status > > beyond that. > > Good toknow. Per the radeon manpage > pcie falls back to > pci: > > PCIE -- PCI Express (falls back to PCI at present) > (used only when DRI is enabled) > > So I took that to mean that DRI worked.... Not exactly. PCI fall-back doesn't seem to work well and there are other issues. I am willing to spend more time on this issue but I don't have hardware to test. :-( However, you can try the latest (but experimental) DRM and Xorg. DRM patch: http://people.freebsd.org/~jkim/drm_vs_fbsd-20050815.diff ports/x11-servers/xorg-server-snap patch: http://people.freebsd.org/~jkim/xorg-server-snap.diff Jung-uk Kim From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 16 16:06:45 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 C191816A41F for ; Tue, 16 Aug 2005 16:06:45 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6379643D62 for ; Tue, 16 Aug 2005 16:06:41 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [157.185.81.167] ([158.69.81.167]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j7GGHffr046366; Tue, 16 Aug 2005 10:17:42 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <43020F08.6070108@samsco.org> Date: Tue, 16 Aug 2005 12:06:32 -0400 From: Scott Long User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Martin Cracauer References: <20050815125657.A92343@cons.org> <20050815172250.GA32804@troutmask.apl.washington.edu> <20050815183846.A99145@cons.org> <430173BE.4080802@samsco.org> <20050816111428.A24284@cons.org> In-Reply-To: <20050816111428.A24284@cons.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: freebsd-amd64@freebsd.org Subject: Re: 4 GB RAM showing up as 3, BIOS memory hole and all that X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Aug 2005 16:06:45 -0000 Martin Cracauer wrote: >>You are definitely going to loose the address space from 3.75GB to 4GB >>to normal PCI and APIC overhead. If you have PCI Express then you'll >>likely also loose the space from 3.5 to 3.75GB. Any other space lost >>beyond that would be possible but usual. And no, most AMD systems do >>*NOT* remap the lost space. >> >>If you want a detailed analysis then please send a verbose boot message >>along with a pointer to the specs on your motherboard. That will give >>enough to information to say if FreeBSD is at fault or if your >>motherboard is simply sub-standard. > > > If you have time for explanations I would rather be interested to know > how the above situation works in the case that you *don't* have 4 GB > of RAM. > > Correct me if I'm wrong but: > - the above 3.5 to 4.0 GB addresses are physical, not virtual > - if you have less than 3.5 GB there is no physical memory at these > addresses that PCI and APIC need > - but if you have 4 GB there is physical memory at these addresses > > I don't understand how this can transparently work with and without > physical RAM at 3.5-4.0 GB. > > > I am not worrying too much about my particular board, and in any case > I just fatfingered a BIOS update and it won't POST :-) > It's a Arima Rioworks HDAMB http://www.rioworks.com/HDAMB.htm If > people are interested I can send the boot -v afer I recover. > > Thanks > Martin First thing to keep in mind is that I'm talking about physical addresses, not OS-specific virtual addresses. Second thing to keep in mind is that I'm talking about *address space*, not *RAM*. There is a big different here. An address represents a location where data can be stored or retrieved. That location does _not_ have to be RAM. It could be a register on a APIC chip, or a memory array on a PCI card, or a location in a local RAM chip. PCI (AGP is really just like PCI from this perspective) specifically allows the CPU to access registers and memory arrays on the cards as if they were local addresses, that's the point of the MEMIO registers and Base Address Registers. When the CPU does a load or store of an address that falls into these address ranges, the request doesn't go to RAM, it goes to the PCI bus and is serviced by the appropriate card there. Local RAM doesn't get involved at all. PCI doesn't actually care much which addresses are used, but by convention the PC platform puts them at the top of the 32-bit address space. But, what happens when you have so much RAM that the RAM could service those very high addresses? For many years that wasn't an issue because it wasn't possible or practical to put that much RAM into a PC. But now it is, so it's up to the memory controller and host bridge to figure out what to do. Many systems cause that high RAM to simply be ignored, resulting in the loss of effective RAM (as you saw in your case). More complex systems will take the RAM that would occupy that 3.5-4GB address space and re-map it into the 4.0-4.5 address space. The RAM doesn't care because it's just an array of storage cells, it's up to the memory controller to associate addresses with those storage cells. Of course, that only works if you're using a 64-bit (or 32bit PAE enabled) OS that can deal with physical addresses larger than 32 bits. Intel Xeon systems typically do the remapping trick, so when you boot FreeBSD i386+PAE or amd64 on them, they might show 4.5GB of RAM when there reall is only 4GB (this is a limitation of how we compute RAM and is purely cosmetic, but should be fixed). Many AMD Opteron systems do not do the remapping and result in you loosing effective RAM. The difference between Intel and AMD is because AMD puts the memory controller into the CPU instead of in the PCI host bridge, so it's much harder to have the two work together to do the remapping. I believe that there are some Opteron systems that can do this, though. A junior doc writer task would be for someone to collect all of the email responses that I give on this topic (I seem to get at least one query a month) and turn it into an FAQ for the FreeBSD doc set. Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 16 18:29:42 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 D9A7D16A41F for ; Tue, 16 Aug 2005 18:29:42 +0000 (GMT) (envelope-from skreetch_fr@yahoo.fr) Received: from postfix3-2.free.fr (postfix3-2.free.fr [213.228.0.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7254043D45 for ; Tue, 16 Aug 2005 18:29:42 +0000 (GMT) (envelope-from skreetch_fr@yahoo.fr) Received: from eliminator.no-ip.org (blm93-2-82-229-62-88.fbx.proxad.net [82.229.62.88]) by postfix3-2.free.fr (Postfix) with ESMTP id B20BFC006 for ; Tue, 16 Aug 2005 20:29:38 +0200 (CEST) Received: from [127.0.0.1] (localhost.no-ip.org [127.0.0.1]) by eliminator.no-ip.org (8.13.4/8.13.1) with ESMTP id j7GITSOL001464 for ; Tue, 16 Aug 2005 20:29:29 +0200 (CEST) (envelope-from skreetch_fr@yahoo.fr) Message-ID: <43023088.90500@yahoo.fr> Date: Tue, 16 Aug 2005 20:29:28 +0200 From: Skreetch User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050722) X-Accept-Language: fr, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on eliminator.no-ip.org X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on eliminator.no-ip.org X-Virus-Status: Clean Subject: Openoffice 1.1 with gcc-ooo X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Aug 2005 18:29:43 -0000 Hello, I'd like to install OpenOffice 1.1 using the ports collection (editors/openoffice-1.1) on FreeBSD 5.4 / AMD64 release. My ports collection, my "world" and my kernel are up to date. It's trying to install the lang/gcc32 application. I installed lang/gcc-ooo but it's the same result: ===> fr-openoffice-1.1.5.rc2.1 depends on executable: gcc32 - not found ===> Verifying install for gcc32 in /usr/ports/lang/gcc32 ===> gcc-3.2.3_3 does not run on amd64, and you are running amd64. *** Error code 1 Stop in /usr/ports/lang/gcc32. *** Error code 1 Stop in /usr/ports/editors/openoffice-1.1. How can I do it ? Thanks for your help. Skreetch From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 16 20:01:26 2005 Return-Path: X-Original-To: amd64@freebsd.org 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 6B2F916A41F; Tue, 16 Aug 2005 20:01:26 +0000 (GMT) (envelope-from gabor.kovesdan@t-hosting.hu) Received: from server.t-hosting.hu (server.t-hosting.hu [217.20.133.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7D5B43D49; Tue, 16 Aug 2005 20:01:25 +0000 (GMT) (envelope-from gabor.kovesdan@t-hosting.hu) Received: from localhost (localhost [127.0.0.1]) by server.t-hosting.hu (Postfix) with ESMTP id DD30E997632; Tue, 16 Aug 2005 22:01:23 +0200 (CEST) Received: from server.t-hosting.hu ([127.0.0.1]) by localhost (server.t-hosting.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 94079-01; Tue, 16 Aug 2005 22:01:17 +0200 (CEST) Received: from [80.98.156.20] (catv-50629c14.catv.broadband.hu [80.98.156.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by server.t-hosting.hu (Postfix) with ESMTP id C2FFC9975E3; Tue, 16 Aug 2005 22:01:17 +0200 (CEST) Message-ID: <43024608.5040606@t-hosting.hu> Date: Tue, 16 Aug 2005 22:01:12 +0200 From: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: amd64@freebsd.org, questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at t-hosting.hu Cc: Subject: i386 compatibility under amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Aug 2005 20:01:26 -0000 Hello, If I try to run an i386 binary uner amd64 I get this: ELF interpreter /libexec/ld-elf32.so.1 not found Abort trap I have options COMPAT_IA32 in my kernel config file but I don't know what should I do besides this. Cheers, Gabor Kovesdan From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 16 20:19:55 2005 Return-Path: X-Original-To: amd64@freebsd.org 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 D857016A41F for ; Tue, 16 Aug 2005 20:19:55 +0000 (GMT) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BE2743D46 for ; Tue, 16 Aug 2005 20:19:53 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id 49DA5B812 for ; Tue, 16 Aug 2005 16:19:52 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v733) In-Reply-To: <43024608.5040606@t-hosting.hu> References: <43024608.5040606@t-hosting.hu> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <21246C71-387C-4966-B999-5696D50E90A3@khera.org> Content-Transfer-Encoding: quoted-printable From: Vivek Khera Date: Tue, 16 Aug 2005 16:19:51 -0400 To: amd64@freebsd.org X-Mailer: Apple Mail (2.733) Cc: Subject: Re: i386 compatibility under amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Aug 2005 20:19:56 -0000 On Aug 16, 2005, at 4:01 PM, K=F6vesd=E1n G=E1bor wrote: > Hello, > > If I try to run an i386 binary uner amd64 I get this: > > ELF interpreter /libexec/ld-elf32.so.1 not found > Abort trap > > I have options COMPAT_IA32 in my kernel config file but I don't =20 > know what should I do besides this. The CD install doens't inclide that file. You need to install via =20 source build to get it. From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 16 20:22:52 2005 Return-Path: X-Original-To: amd64@freebsd.org 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 08F7B16A41F for ; Tue, 16 Aug 2005 20:22:52 +0000 (GMT) (envelope-from gabor.kovesdan@t-hosting.hu) Received: from server.t-hosting.hu (server.t-hosting.hu [217.20.133.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87FA743D46 for ; Tue, 16 Aug 2005 20:22:51 +0000 (GMT) (envelope-from gabor.kovesdan@t-hosting.hu) Received: from localhost (localhost [127.0.0.1]) by server.t-hosting.hu (Postfix) with ESMTP id 5C25C997632; Tue, 16 Aug 2005 22:22:50 +0200 (CEST) Received: from server.t-hosting.hu ([127.0.0.1]) by localhost (server.t-hosting.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 93635-03; Tue, 16 Aug 2005 22:22:46 +0200 (CEST) Received: from [80.98.156.20] (catv-50629c14.catv.broadband.hu [80.98.156.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by server.t-hosting.hu (Postfix) with ESMTP id C138F997607; Tue, 16 Aug 2005 22:22:46 +0200 (CEST) Message-ID: <43024B15.1030402@t-hosting.hu> Date: Tue, 16 Aug 2005 22:22:45 +0200 From: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vivek Khera References: <43024608.5040606@t-hosting.hu> <21246C71-387C-4966-B999-5696D50E90A3@khera.org> In-Reply-To: <21246C71-387C-4966-B999-5696D50E90A3@khera.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at t-hosting.hu Cc: amd64@freebsd.org Subject: Re: i386 compatibility under amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Aug 2005 20:22:52 -0000 Vivek Khera wrote: > The CD install doens't inclide that file. You need to install via > source build to get it. > I should just make buildworld and make installworld and it will work? From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 16 21:46:27 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 003B216A41F for ; Tue, 16 Aug 2005 21:46:26 +0000 (GMT) (envelope-from ghelmer@palisadesys.com) Received: from magellan.palisadesys.com (magellan.palisadesys.com [192.188.162.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 975C243D48 for ; Tue, 16 Aug 2005 21:46:26 +0000 (GMT) (envelope-from ghelmer@palisadesys.com) Received: from [172.16.1.108] (cetus.palisadesys.com [192.188.162.7]) (authenticated bits=0) by magellan.palisadesys.com (8.12.11/8.12.11) with ESMTP id j7GLkJ1L056442; Tue, 16 Aug 2005 16:46:23 -0500 (CDT) (envelope-from ghelmer@palisadesys.com) Message-ID: <43025EAB.6030201@palisadesys.com> Date: Tue, 16 Aug 2005 16:46:19 -0500 From: Guy Helmer User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <20050815125657.A92343@cons.org> <20050815172250.GA32804@troutmask.apl.washington.edu> <20050815183846.A99145@cons.org> <430173BE.4080802@samsco.org> <20050816111428.A24284@cons.org> <43020F08.6070108@samsco.org> In-Reply-To: <43020F08.6070108@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Palisade-MailScanner-Information: Please contact the ISP for more information X-Palisade-MailScanner: Found to be clean X-MailScanner-From: ghelmer@palisadesys.com Cc: freebsd-amd64@freebsd.org Subject: Re: 4 GB RAM showing up as 3, BIOS memory hole and all that X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Aug 2005 21:46:27 -0000 Scott Long wrote: > Intel Xeon systems typically do the remapping trick, so when you boot > FreeBSD i386+PAE or amd64 on them, they might show 4.5GB of RAM when > there reall is only 4GB (this is a limitation of how we compute RAM and > is purely cosmetic, but should be fixed). Many AMD Opteron systems do > not do the remapping and result in you loosing effective RAM. The > difference between Intel and AMD is because AMD puts the memory > controller into the CPU instead of in the PCI host bridge, so it's > much harder to have the two work together to do the remapping. I > believe that there are some Opteron systems that can do this, though. Ahh, that helps explain something. I got excited yesterday when I noticed a Supermicro H8DAR-8 that I thought had 8MB of RAM reported 10GB of physical memory instead. Guy -- Guy Helmer, Ph.D. Principal System Architect Palisade Systems, Inc. From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 16 22:05:46 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 1608B16A41F for ; Tue, 16 Aug 2005 22:05:46 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fileserver.fields.utoronto.ca (fileserver.fields.utoronto.ca [128.100.216.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DC1243D45 for ; Tue, 16 Aug 2005 22:05:45 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fields.fields.utoronto.ca (fields.localdomain [192.168.216.11]) by fileserver.fields.utoronto.ca (8.12.8/8.12.8/Fields 6.0) with ESMTP id j7GM5ivf002523 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Aug 2005 18:05:44 -0400 Received: from obsecurity.dyndns.org (localhost.localdomain [127.0.0.1]) by fields.fields.utoronto.ca (8.12.8/8.12.8/Fields WS 6.0) with ESMTP id j7GM5i6P030293; Tue, 16 Aug 2005 18:05:44 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id AE0E25137D; Tue, 16 Aug 2005 18:05:43 -0400 (EDT) Date: Tue, 16 Aug 2005 18:05:43 -0400 From: Kris Kennaway To: Skreetch Message-ID: <20050816220543.GA97063@xor.obsecurity.org> References: <43023088.90500@yahoo.fr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WIyZ46R2i8wDzkSu" Content-Disposition: inline In-Reply-To: <43023088.90500@yahoo.fr> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: Openoffice 1.1 with gcc-ooo X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Aug 2005 22:05:46 -0000 --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 16, 2005 at 08:29:28PM +0200, Skreetch wrote: > Hello, >=20 > I'd like to install OpenOffice 1.1 using the ports collection > (editors/openoffice-1.1) on FreeBSD 5.4 / AMD64 release. My ports > collection, my "world" and my kernel are up to date. It's trying to > install the lang/gcc32 application. I installed lang/gcc-ooo but it's > the same result: > =3D=3D=3D> fr-openoffice-1.1.5.rc2.1 depends on executable: gcc32 - not= found > =3D=3D=3D> Verifying install for gcc32 in /usr/ports/lang/gcc32 > =3D=3D=3D> gcc-3.2.3_3 does not run on amd64, and you are running amd64. > *** Error code 1 >=20 > Stop in /usr/ports/lang/gcc32. > *** Error code 1 >=20 > Stop in /usr/ports/editors/openoffice-1.1. >=20 > How can I do it ? You cannot, see the mailing list archives. Kris --WIyZ46R2i8wDzkSu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFDAmM2Wry0BWjoQKURAjBdAKDq6xuMjnsam/OTadZRceMYqyXTdACg+cHS H9WMjVnF/tKhkLdCWIkB/ms= =dbWJ -----END PGP SIGNATURE----- --WIyZ46R2i8wDzkSu-- From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 16 22:56:04 2005 Return-Path: X-Original-To: amd64@freebsd.org 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 0B42E16A41F for ; Tue, 16 Aug 2005 22:56:04 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from mail27.sea5.speakeasy.net (mail27.sea5.speakeasy.net [69.17.117.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 050D043D66 for ; Tue, 16 Aug 2005 22:55:19 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: (qmail 22428 invoked from network); 16 Aug 2005 22:55:19 -0000 Received: from aldan.algebra.com ([216.254.65.224]) (envelope-sender ) by mail27.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 16 Aug 2005 22:55:17 -0000 Received: from corbulon.video-collage.com (static-151-204-231-237.bos.east.verizon.net [151.204.231.237]) by aldan.algebra.com (8.13.1/8.13.1) with ESMTP id j7GMtE3t007736 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 16 Aug 2005 18:55:15 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from mteterin.us.murex.com (195-11.customer.cloud9.net [168.100.195.11]) by corbulon.video-collage.com (8.13.4/8.13.1) with ESMTP id j7GMt6K3034302 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Aug 2005 18:55:07 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from mteterin.us.murex.com (mteterin@localhost [127.0.0.1]) by mteterin.us.murex.com (8.13.3/8.13.3) with ESMTP id j7GMt1MJ027346; Tue, 16 Aug 2005 18:55:01 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by mteterin.us.murex.com (8.13.3/8.13.3/Submit) id j7GMsxRF027328; Tue, 16 Aug 2005 18:54:59 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) X-Authentication-Warning: mteterin.us.murex.com: mteterin set sender to mi+mx@aldan.algebra.com using -f From: Mikhail Teterin Organization: Virtual Estates, Inc. To: Q , net@freebsd.org, amd64@freebsd.org Date: Tue, 16 Aug 2005 18:54:59 -0400 User-Agent: KMail/1.8.2 References: <200504220128.17540@aldan> <3597b10b1fe23e85f87632829a3e9d2c@onthenet.com.au> In-Reply-To: <3597b10b1fe23e85f87632829a3e9d2c@onthenet.com.au> MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_D7mADdPvPDVPD/Z" Message-Id: <200508161854.59560.mi+mx@aldan.algebra.com> X-Virus-Scanned: ClamAV devel-20050525/1023/Mon Aug 15 16:15:08 2005 on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 Cc: Subject: Re: nvnet does not see NVidia's adapter on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Aug 2005 22:56:04 -0000 --Boundary-00=_D7mADdPvPDVPD/Z Content-Type: text/plain; charset="koi8-u" Content-Transfer-Encoding: 8bit Content-Disposition: inline Hi, Quinton! Friday, April 22, 2005 01:34, Q wrote: > Err yes it is. šMy firewall/router at home has an uptime of 28 days and > has 0 errrors. Looks like a duplex problem, which will explain your > poor performance. Why it's happening is another story. Have you tried > this motherboard using linux or windows with these switches to ensure > that they function correctly and it's not a hardware issue. I have a > switch at home that will not sync with one of my motherboards unless > you use a crossover into the uplink port for some reason. Ok, in the 4 months since our last exchange on this matter, we did try WindowsXP/64 on the machine. There were no problems using the interface (after I added NVidia's drivers, that is). I'm now trying to net-install 6.0-BETA2 and am seeing the same symptoms however. The interface works (very) intermittently. For example, during install, it was unable to obtain the DHCP information. But, when we entered the info by hand, it was able to resolve the name 'ftp3.freebsd.org'. But then it was again unable to login to the ftp-server. While the install was struggling with that, I looked at the debug screen -- Alt-F2. It kept showing "Interface nve0 UP" and "Interface nve0 DOWN". Have you made any updates to the driver/port recently, that may not be in 6.0? Is the net/nvnet port newer -- we can try to install 5.4 and add this port... Thanks! -mi P.S. The machine has no OS on it right now -- I'm attaching the dmesg and the pciconf output from April 13. --Boundary-00=_D7mADdPvPDVPD/Z Content-Type: text/plain; charset="koi8-u"; name="dmesg.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="dmesg.txt" ata3-slave: stat=0x7f err=0xff lsb=0xff msb=0xff ata3: reset tp2 stat0=ff stat1=ff devices=0x0 ata3: [MPSAFE] pcib1: at device 11.0 on pci0 pcib1: secondary bus 2 pcib1: subordinate bus 2 pcib1: I/O decode 0x9000-0x9fff pcib1: memory decode 0xff100000-0xff1fffff pcib1: prefetched decode 0xe6900000-0xee8fffff pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.P0P2 - AE_NOT_FOUND pci2: on pcib1 pci2: physical bus=2 map[10]: type 3, range 32, base e8000000, size 26, enabled pcib1: device (null) requested decoded memory range 0xe8000000-0xebffffff map[14]: type 4, range 32, base 00009800, size 8, enabled pcib1: device (null) requested decoded I/O range 0x9800-0x98ff map[18]: type 1, range 32, base ff1fc000, size 14, enabled pcib1: device (null) requested decoded memory range 0xff1fc000-0xff1fffff pcib0: matched entry for 0.11.INTA (src \\_SB_.LNKE) pcib0: possible interrupts: 16 17 18 19 ACPI PCI link arbitrated settings: \\_SB_.LNKB (references 3, priority 840): interrupts: 19 18 17 16 penalty: 280 280 280 280 \\_SB_.LKSM (references 1, priority 706): interrupts: 20 22 21 penalty: 640 740 740 \\_SB_.LKMO (references 1, priority 706): interrupts: 20 22 21 penalty: 640 740 740 \\_SB_.LTIE (references 1, priority 706): interrupts: 20 22 21 penalty: 640 740 740 \\_SB_.LNKE (references 1, priority 280): interrupts: 19 18 17 16 penalty: 280 280 280 280 pcib0: slot 11 INTA routed to irq 19 via \\_SB_.LNKE pcib1: slot 0 INTA is routed to irq 19 found-> vendor=0x1002, dev=0x5446, revid=0x00 bus=2, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0087, statreg=0x02b0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) intpin=a, irq=19 powerspec 2 supports D0 D1 D3 current D0 pci2: at device 0.0 (no driver attached) pcib2: at device 14.0 on pci0 pcib2: secondary bus 1 pcib2: subordinate bus 1 pcib2: I/O decode 0xf000-0xfff pcib2: memory decode 0xff000000-0xff0fffff pcib2: prefetched decode 0xfff00000-0xfffff ACPI link \\_SB_.LNKD has invalid initial irq 10, ignoring ACPI link \\_SB_.LNKC has invalid initial irq 10, ignoring ACPI PCI link initial configuration: \\_SB_.LNKD irq 0: [16 17 18 19] 0+ low,level,sharable 1.7.0 \\_SB_.LNKA irq 0: [16 17 18 19] 0+ low,level,sharable 1.7.1 \\_SB_.LNKB irq 0: [16 17 18 19] 0+ low,level,sharable 1.7.2 \\_SB_.LNKC irq 0: [16 17 18 19] 0+ low,level,sharable 1.7.3 \\_SB_.LNKC irq 0: [16 17 18 19] 0+ low,level,sharable 1.6.0 \\_SB_.LNKD irq 0: [16 17 18 19] 0+ low,level,sharable 1.6.1 \\_SB_.LNKA irq 0: [16 17 18 19] 0+ low,level,sharable 1.6.2 \\_SB_.LNKB irq 0: [16 17 18 19] 0+ low,level,sharable 1.6.3 pci1: on pcib2 pci1: physical bus=1 map[10]: type 1, range 32, base ff0ff800, size 11, enabled pcib2: device (null) requested decoded memory range 0xff0ff800-0xff0fffff map[14]: type 1, range 32, base ff0f8000, size 14, enabled pcib2: device (null) requested decoded memory range 0xff0f8000-0xff0fbfff pcib2: matched entry for 1.6.INTA (src \\_SB_.LNKC) pcib2: possible interrupts: 16 17 18 19 ACPI PCI link arbitrated settings: \\_SB_.LNKB (references 5, priority 2212): interrupts: 18 17 16 19 penalty: 440 440 440 450 \\_SB_.LNKD (references 2, priority 885): interrupts: 18 17 16 19 penalty: 440 440 440 450 \\_SB_.LNKA (references 2, priority 885): interrupts: 18 17 16 19 penalty: 440 440 440 450 \\_SB_.LNKC (references 2, priority 885): interrupts: 18 17 16 19 penalty: 440 440 440 450 \\_SB_.LKSM (references 1, priority 706): interrupts: 20 21 22 penalty: 640 740 740 \\_SB_.LKMO (references 1, priority 706): interrupts: 20 21 22 penalty: 640 740 740 \\_SB_.LTIE (references 1, priority 706): interrupts: 20 21 22 penalty: 640 740 740 pcib2: slot 6 INTA routed to irq 18 via \\_SB_.LNKC found-> vendor=0x104c, dev=0x8023, revid=0x00 bus=1, slot=6, func=0 class=0c-00-10, hdrtype=0x00, mfdev=0 cmdreg=0x0116, statreg=0x0210, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x02 (500 ns), maxlat=0x04 (1000 ns) intpin=a, irq=18 powerspec 2 supports D0 D1 D2 D3 current D0 fwohci0: mem 0xff0f8000-0xff0fbfff,0xff0ff800-0xff0fffff irq 18 at device 6.0 on pci1 fwohci0: Reserved 0x800 bytes for rid 0x10 type 3 at 0xff0ff800 fwohci0: [MPSAFE] fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:00:00:00:00:01:46:87 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:00:00:01:46:87 fwe0: bpf attached fwe0: Ethernet address: 02:00:00:01:46:87 fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) pcib3: on acpi0 pcib3: could not get PCI interrupt routing table for \\_SB_.PCIB - AE_NOT_FOUND pci3: on pcib3 pci3: physical bus=3 found-> vendor=0x1022, dev=0x7450, revid=0x12 bus=3, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0117, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x07 (1750 ns), maxlat=0x04 (1000 ns) map[10]: type 1, range 64, base ff6fe000, size 12, enabled found-> vendor=0x1022, dev=0x7451, revid=0x01 bus=3, slot=1, func=1 class=08-00-10, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x7450, revid=0x12 bus=3, slot=2, func=0 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0116, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x07 (1750 ns), maxlat=0x00 (0 ns) map[10]: type 1, range 64, base ff6ff000, size 12, enabled found-> vendor=0x1022, dev=0x7451, revid=0x01 bus=3, slot=2, func=1 class=08-00-10, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) pcib4: at device 1.0 on pci3 pcib4: secondary bus 5 pcib4: subordinate bus 5 pcib4: I/O decode 0xd000-0xefff pcib4: memory decode 0xff400000-0xff5fffff pcib4: prefetched decode 0xfff00000-0xfffff ACPI PCI link initial configuration: pci5: on pcib4 pci5: physical bus=5 map[10]: type 4, range 32, base 0000ec00, size 3, enabled pcib4: device (null) requested decoded I/O range 0xec00-0xec07 map[14]: type 4, range 32, base 0000e800, size 2, enabled pcib4: device (null) requested decoded I/O range 0xe800-0xe803 map[18]: type 4, range 32, base 0000e400, size 3, enabled pcib4: device (null) requested decoded I/O range 0xe400-0xe407 map[1c]: type 4, range 32, base 0000e000, size 2, enabled pcib4: device (null) requested decoded I/O range 0xe000-0xe003 map[20]: type 4, range 32, base 0000dc00, size 4, enabled pcib4: device (null) requested decoded I/O range 0xdc00-0xdc0f map[24]: type 1, range 32, base ff5ffc00, size 10, enabled pcib4: device (null) requested decoded memory range 0xff5ffc00-0xff5fffff pcib4: matched entry for 5.3.INTA pcib4: slot 3 INTA hardwired to IRQ 27 found-> vendor=0x1095, dev=0x3114, revid=0x02 bus=5, slot=3, func=0 class=01-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0107, statreg=0x02b0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=27 powerspec 2 supports D0 D1 D2 D3 current D0 atapci2: port 0xdc00-0xdc0f,0xe000-0xe003,0xe400-0xe407,0xe800-0xe803,0xec00-0xec07 mem 0xff5ffc00-0xff5fffff irq 27 at device 3.0 on pci5 atapci2: Reserved 0x10 bytes for rid 0x20 type 4 at 0xdc00 atapci2: [MPSAFE] atapci2: Reserved 0x400 bytes for rid 0x24 type 3 at 0xff5ffc00 ata4: channel #0 on atapci2 ata4: reset tp1 mask=01 ostat0=50 ostat1=50 ata4-master: stat=0xd0 err=0xd0 lsb=0xd0 msb=0xd0 ata4-master: stat=0xd0 err=0xd0 lsb=0xd0 msb=0xd0 ata4-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata4: reset tp2 stat0=50 stat1=00 devices=0x1 ata4: [MPSAFE] ata5: channel #1 on atapci2 ata5: reset tp1 mask=01 ostat0=50 ostat1=50 ata5-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata5: reset tp2 stat0=50 stat1=00 devices=0x1 ata5: [MPSAFE] ata6: channel #2 on atapci2 ata6: reset tp1 mask=01 ostat0=7f ostat1=7f ata6-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata6-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata6-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata6-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata6-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata6-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata6-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata6: reset tp2 stat0=ff stat1=00 devices=0x0 ata6: [MPSAFE] ata7: channel #3 on atapci2 ata7: reset tp1 mask=01 ostat0=7f ostat1=7f ata7-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata7-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata7-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata7-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata7-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata7-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata7-master: stat=0x7f err=0x00 lsb=0x00 msb=0x00 ata7: reset tp2 stat0=ff stat1=00 devices=0x0 ata7: [MPSAFE] pci3: at device 1.1 (no driver attached) pcib5: at device 2.0 on pci3 pcib5: secondary bus 4 pcib5: subordinate bus 4 pcib5: I/O decode 0x0-0x0 pcib5: memory decode 0xff300000-0xff3fffff pcib5: prefetched decode 0xfea00000-0xfeafffff ACPI PCI link initial configuration: pci4: on pcib5 pci4: physical bus=4 map[10]: type 3, range 32, base feaf0000, size 16, enabled pcib5: device (null) requested decoded memory range 0xfeaf0000-0xfeafffff pcib5: matched entry for 4.1.INTA pcib5: slot 1 INTA hardwired to IRQ 29 found-> vendor=0x1000, dev=0x1960, revid=0x01 bus=4, slot=1, func=0 class=01-04-00, hdrtype=0x00, mfdev=0 cmdreg=0x0116, statreg=0x04b0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=29 powerspec 2 supports D0 D3 current D0 amr0: mem 0xfeaf0000-0xfeafffff irq 29 at device 1.0 on pci4 amr0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xfeaf0000 amr0: [MPSAFE] amr0: Firmware 712T, BIOS G116, 64MB RAM pci3: at device 2.1 (no driver attached) acpi_button0: on acpi0 unknown: not probed (disabled) sio0: irq maps: 0xa3 0xb3 0xa3 0xa3 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: irq maps: 0xa3 0xab 0xa3 0xa3 sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: ic_type 90 part_id 80 fdc0: [MPSAFE] fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000 atkbd0: [GIANT-LOCKED] psm0: unable to allocate IRQ unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) ahc_isa_probe 10: ioport 0xac00 alloc failed ahc_isa_probe 11: ioport 0xbc00 alloc failed ahc_isa_probe 12: ioport 0xcc00 alloc failed ahc_isa_probe 13: ioport 0xdc00 alloc failed ahc_isa_probe 14: ioport 0xec00 alloc failed ex_isa_identify() atkbdc: atkbdc0 already exists; skipping it fdc: fdc0 already exists; skipping it sio: sio0 already exists; skipping it sio: sio1 already exists; skipping it Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: at iomem 0xc8800-0xccfff,0xc0000-0xc7fff on isa0 ppc0: cannot reserve I/O port range ppc0: failed to probe at irq 7 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio2: not probed (disabled) sio3: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xffffffff800b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 EGA/VGA parameters to be used for mode 24 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff isa_probe_children: probing PnP devices Device configuration finished. Reducing kern.maxvnodes 132744 -> 100000 procfs registered linprocfs registered Timecounter "TSC" frequency 1800005863 Hz quality 800 Timecounters tick every 1.000 msec Linux ELF exec handler installed lo0: bpf attached ata1-master: pio=0x0c wdma=0x22 udma=0xffffffff cable=40pin ata1-master: setting PIO4 on nVidia nForce3 Pro chip acd0: CDROM drive at ata1 as master acd0: read 5512KB/s (5512KB/s), 256KB buffer, PIO4 acd0: Reads: CDR, CDRW, CDDA, packet acd0: Writes: acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc ata4-master: pio=0x0c wdma=0x22 udma=0x46 cable=40pin ad8: ATA-6 disk at ata4-master ad8: 190782MB (390721968 sectors), 387621 C, 16 H, 63 S, 512 B ad8: 16 secs/int, 1 depth queue, SATA150 ar: LSI check1 failed ata5-master: FAILURE - ATA_IDENTIFY status=51 error=4 LBA=0 GEOM: new disk ad8 [0] f:00 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:16771797 [1] f:80 typ:165 s(CHS):1023/255/63 e(CHS):1023/254/63 s:16771860 l:4192965 [2] f:00 typ:165 s(CHS):1023/255/63 e(CHS):1023/254/63 s:20964825 l:16771860 [3] f:00 typ:165 s(CHS):1023/255/63 e(CHS):1023/254/63 s:37736685 l:352980180 GEOM: Configure ad8s1, start 32256 length 8587160064 end 8587192319 GEOM: Configure ad8s2, start 8587192320 length 2146798080 end 10733990399 GEOM: Configure ad8s3, start 10733990400 length 8587192320 end 19321182719 GEOM: Configure ad8s4, start 19321182720 length 180725852160 end 200047034879 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 GEOM: Configure ad8s1b, start 0 length 8587160064 end 8587160063 GEOM: Configure ad8s1c, start 0 length 8587160064 end 8587160063 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 GEOM: Configure ad8s2a, start 0 length 2146798080 end 2146798079 GEOM: Configure ad8s2c, start 0 length 2146798080 end 2146798079 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 GEOM: Configure ad8s3c, start 0 length 8587192320 end 8587192319 GEOM: Configure ad8s3d, start 0 length 8587192320 end 8587192319 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 GEOM: Configure ad8s4c, start 0 length 180725852160 end 180725852159 GEOM: Configure ad8s4d, start 0 length 180725852160 end 180725852159 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 ata5: reiniting channel .. ata5: reset tp1 mask=01 ostat0=50 ostat1=50 ata5-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata5: reset tp2 stat0=50 stat1=00 devices=0x1 ata5: resetting done .. ata5-master: FAILURE - ATA_IDENTIFY status=51 error=4 LBA=0 ata5: reiniting channel .. ata5-master: FAILURE - ATA_IDENTIFY timed out ata5: device config done .. ata5-master: FAILURE - ATA_IDENTIFY timed out amrd0: on amr0 amrd0: 953885MB (1953556480 sectors) RAID 5 (optimal) GEOM: new disk amrd0 (probe21:amr0:0:15:0): error 22 (probe21:amr0:0:15:0): Unretryable Error (probe13:amr0:0:6:0): error 22 (probe13:amr0:0:6:0): Unretryable Error (probe14:amr0:0:8:0): error 22 (probe14:amr0:0:8:0): Unretryable Error (probe15:amr0:0:9:0): error 22 (probe15:amr0:0:9:0): Unretryable Error (probe16:amr0:0:10:0): error 22 (probe16:amr0:0:10:0): Unretryable Error (probe17:amr0:0:11:0): error 22 (probe17:amr0:0:11:0): Unretryable Error (probe18:amr0:0:12:0): error 22 (probe18:amr0:0:12:0): Unretryable Error (probe19:amr0:0:13:0): error 22 (probe19:amr0:0:13:0): Unretryable Error (probe20:amr0:0:14:0): error 22 (probe20:amr0:0:14:0): Unretryable Error (probe12:amr0:0:5:0): error 22 (probe12:amr0:0:5:0): Unretryable Error (probe11:amr0:0:4:0): error 22 (probe11:amr0:0:4:0): Unretryable Error (probe9:amr0:0:2:0): error 22 (probe9:amr0:0:2:0): Unretryable Error (probe7:amr0:0:0:0): error 22 (probe7:amr0:0:0:0): Unretryable Error (probe8:amr0:0:1:0): error 22 (probe8:amr0:0:1:0): Unretryable Error (probe10:amr0:0:3:0): error 22 (probe10:amr0:0:3:0): Unretryable Error (probe3:sbp0:0:3:0): error 22 (probe3:sbp0:0:3:0): Unretryable Error (probe0:sbp0:0:0:0): error 22 (probe0:sbp0:0:0:0): Unretryable Error (probe1:sbp0:0:1:0): error 22 (probe1:sbp0:0:1:0): Unretryable Error (probe2:sbp0:0:2:0): error 22 (probe2:sbp0:0:2:0): Unretryable Error (probe4:sbp0:0:4:0): error 22 (probe4:sbp0:0:4:0): Unretryable Error (probe5:sbp0:0:5:0): error 22 (probe5:sbp0:0:5:0): Unretryable Error (probe6:sbp0:0:6:0): error 22 (probe6:sbp0:0:6:0): Unretryable Error ioapic0: routing intpin 1 (ISA IRQ 1) to cluster 0 ioapic0: routing intpin 3 (ISA IRQ 3) to cluster 0 ioapic0: routing intpin 4 (ISA IRQ 4) to cluster 0 ioapic0: routing intpin 6 (ISA IRQ 6) to cluster 0 ioapic0: routing intpin 8 (ISA IRQ 8) to cluster 0 ioapic0: routing intpin 9 (ISA IRQ 9) to cluster 0 ioapic0: routing intpin 14 (ISA IRQ 14) to cluster 0 ioapic0: routing intpin 15 (ISA IRQ 15) to cluster 0 ioapic0: routing intpin 18 (PCI IRQ 18) to cluster 0 ioapic0: routing intpin 21 (PCI IRQ 21) to cluster 0 ioapic0: routing intpin 22 (PCI IRQ 22) to cluster 0 ioapic1: routing intpin 3 (PCI IRQ 27) to cluster 0 ioapic2: routing intpin 1 (PCI IRQ 29) to cluster 0 Mounting root from ufs:/dev/ad8s2a start_init: trying /sbin/init [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 [0] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:80 typ:165 s(CHS):0/0/1 e(CHS):1023/254/63 s:0 l:50000 Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...3 2 2 1 0 0 done No buffers busy after final sync Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-RC2 #0: Sun Apr 10 04:02:23 UTC 2005 root@portnoy.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 244 (1800.01-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 Features=0x78bfbff AMD Features=0xe0500800 real memory = 2146697216 (2047 MB) avail memory = 2060873728 (1965 MB) ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 pcib0: port 0xcf8-0xcff on acpi0 ACPI link \\_SB_.LUS0 has invalid initial irq 10, ignoring ACPI link \\_SB_.LKLN has invalid initial irq 5, ignoring ACPI link \\_SB_.LUS1 has invalid initial irq 11, ignoring ACPI link \\_SB_.LUS2 has invalid initial irq 7, ignoring ACPI link \\_SB_.LNKE has invalid initial irq 11, ignoring ACPI link \\_SB_.LNKB has invalid initial irq 10, ignoring ACPI link \\_SB_.LTIE has invalid initial irq 10, ignoring pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xff2fb000-0xff2fbfff irq 22 at device 2.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ohci1: mem 0xff2fc000-0xff2fcfff irq 21 at device 2.1 on pci0 usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered pci0: at device 2.2 (no driver attached) pci0: at device 5.0 (no driver attached) pci0: at device 6.0 (no driver attached) atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 8.0 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 atapci1: port 0xbc00-0xbc0f,0xc000-0xc003,0xc400-0xc407,0xc800-0xc803,0xcc00-0xcc07 irq 21 at device 10.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 pcib1: at device 11.0 on pci0 pci2: on pcib1 pci2: at device 0.0 (no driver attached) pcib2: at device 14.0 on pci0 ACPI link \\_SB_.LNKD has invalid initial irq 10, ignoring ACPI link \\_SB_.LNKC has invalid initial irq 10, ignoring pci1: on pcib2 fwohci0: mem 0xff0f8000-0xff0fbfff,0xff0ff800-0xff0fffff irq 18 at device 6.0 on pci1 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:00:00:00:00:01:46:87 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:00:00:01:46:87 fwe0: Ethernet address: 02:00:00:01:46:87 fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) pcib3: on acpi0 pci3: on pcib3 pcib4: at device 1.0 on pci3 pci5: on pcib4 atapci2: port 0xdc00-0xdc0f,0xe000-0xe003,0xe400-0xe407,0xe800-0xe803,0xec00-0xec07 mem 0xff5ffc00-0xff5fffff irq 27 at device 3.0 on pci5 ata4: channel #0 on atapci2 ata5: channel #1 on atapci2 ata6: channel #2 on atapci2 ata7: channel #3 on atapci2 pci3: at device 1.1 (no driver attached) pcib5: at device 2.0 on pci3 pci4: on pcib5 amr0: mem 0xfeaf0000-0xfeafffff irq 29 at device 1.0 on pci4 amr0: Firmware 712T, BIOS G116, 64MB RAM pci3: at device 2.1 (no driver attached) acpi_button0: on acpi0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 orm0: at iomem 0xc8800-0xccfff,0xc0000-0xc7fff on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1800006073 Hz quality 800 Timecounters tick every 1.000 msec acd0: CDROM at ata1-master PIO4 ad8: 190782MB [387621/16/63] at ata4-master SATA150 ata5-master: FAILURE - ATA_IDENTIFY status=51 error=4 LBA=0 ata5-master: FAILURE - ATA_IDENTIFY status=51 error=4 LBA=0 ata5-master: FAILURE - ATA_IDENTIFY timed out ata5-master: FAILURE - ATA_IDENTIFY timed out amrd0: on amr0 amrd0: 953885MB (1953556480 sectors) RAID 5 (optimal) Mounting root from ufs:/dev/ad8s2a --Boundary-00=_D7mADdPvPDVPD/Z Content-Type: text/plain; charset="koi8-u"; name="pciconf.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="pciconf.txt" hostb0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x00e110de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' class = bridge subclass = HOST-PCI isab0@pci0:1:0: class=0x060100 card=0x004415d4 chip=0x00e010de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' class = bridge subclass = PCI-ISA none0@pci0:1:1: class=0x0c0500 card=0x004415d4 chip=0x00e410de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce PCI System Management' class = serial bus subclass = SMBus ohci0@pci0:2:0: class=0x0c0310 card=0x004415d4 chip=0x00e710de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' class = serial bus subclass = USB ohci1@pci0:2:1: class=0x0c0310 card=0x004415d4 chip=0x00e710de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' class = serial bus subclass = USB none1@pci0:2:2: class=0x0c0320 card=0x004415d4 chip=0x00e810de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' class = serial bus subclass = USB none2@pci0:5:0: class=0x068000 card=0x004415d4 chip=0x00df10de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'Network Bus Enumerator' class = bridge none3@pci0:6:0: class=0x040100 card=0x004415d4 chip=0x00ea10de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' class = multimedia subclass = audio atapci0@pci0:8:0: class=0x01018a card=0x004415d4 chip=0x00e510de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'CK8S Parallel ATA Controller' class = mass storage subclass = ATA atapci1@pci0:10:0: class=0x010185 card=0x00000000 chip=0x00e310de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'CK8S Serial ATA Controller' class = mass storage subclass = ATA pcib1@pci0:11:0: class=0x060400 card=0x00000000 chip=0x00e210de rev=0xa2 hdr=0x01 vendor = 'NVIDIA Corporation' device = 'nForce3 250 AGP Host to PCI Bridge' class = bridge subclass = PCI-PCI pcib2@pci0:14:0: class=0x060400 card=0x00000000 chip=0x00ed10de rev=0xa2 hdr=0x01 vendor = 'NVIDIA Corporation' class = bridge subclass = PCI-PCI hostb1@pci0:24:0: class=0x060000 card=0x00000000 chip=0x11001022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron HyperTransport Technology Configuration' class = bridge subclass = HOST-PCI hostb2@pci0:24:1: class=0x060000 card=0x00000000 chip=0x11011022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron Address Map' class = bridge subclass = HOST-PCI hostb3@pci0:24:2: class=0x060000 card=0x00000000 chip=0x11021022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron DRAM Controller' class = bridge subclass = HOST-PCI hostb4@pci0:24:3: class=0x060000 card=0x00000000 chip=0x11031022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron Miscellaneous Control' class = bridge subclass = HOST-PCI none4@pci2:0:0: class=0x030000 card=0x04081002 chip=0x54461002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc.' device = 'Rage 128 PRO ULTRA Video Controller (VGA Compatible)' class = display subclass = VGA fwohci0@pci1:6:0: class=0x0c0010 card=0x8023104c chip=0x8023104c rev=0x00 hdr=0x00 vendor = 'Texas Instruments (TI)' device = 'TSB43AB22/A IEEE1394a-2000 OHCI PHY/Link-Layer Ctrlr' class = serial bus subclass = FireWire pcib4@pci3:1:0: class=0x060400 card=0x000000a0 chip=0x74501022 rev=0x12 hdr=0x01 vendor = 'Advanced Micro Devices (AMD)' device = 'AMD-8131 PCI-X Bridge' class = bridge subclass = PCI-PCI none5@pci3:1:1: class=0x080010 card=0x36c01022 chip=0x74511022 rev=0x01 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'AMD-8131 PCI-X IOAPIC' class = base peripheral subclass = interrupt controller pcib5@pci3:2:0: class=0x060400 card=0x000000a0 chip=0x74501022 rev=0x12 hdr=0x01 vendor = 'Advanced Micro Devices (AMD)' device = 'AMD-8131 PCI-X Bridge' class = bridge subclass = PCI-PCI none6@pci3:2:1: class=0x080010 card=0x36c01022 chip=0x74511022 rev=0x01 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'AMD-8131 PCI-X IOAPIC' class = base peripheral subclass = interrupt controller atapci2@pci5:3:0: class=0x018000 card=0x31141095 chip=0x31141095 rev=0x02 hdr=0x00 vendor = 'Silicon Image Inc (Was: CMD Technology Inc)' device = 'Sil 3114 SATALink/SATARaid Controller' class = mass storage amr0@pci4:1:0: class=0x010400 card=0x05231000 chip=0x19601000 rev=0x01 hdr=0x00 vendor = 'LSI Logic (Was: Symbios Logic, NCR)' class = mass storage subclass = RAID --Boundary-00=_D7mADdPvPDVPD/Z-- From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 16 23:42:29 2005 Return-Path: X-Original-To: amd64@freebsd.org 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 24D8B16A41F; Tue, 16 Aug 2005 23:42:29 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB65143D48; Tue, 16 Aug 2005 23:42:28 +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.3/8.13.3) with ESMTP id j7GNgREQ014495; Tue, 16 Aug 2005 19:42:27 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id j7GNgR9X055112; Tue, 16 Aug 2005 19:42:27 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 21E9A7304D; Tue, 16 Aug 2005 19:42:27 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050816234227.21E9A7304D@freebsd-current.sentex.ca> Date: Tue, 16 Aug 2005 19:42:27 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner5 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Aug 2005 23:42:29 -0000 TB --- 2005-08-16 22:45:41 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-08-16 22:45:41 - starting HEAD tinderbox run for amd64/amd64 TB --- 2005-08-16 22:45:41 - cleaning the object tree TB --- 2005-08-16 22:46:16 - checking out the source tree TB --- 2005-08-16 22:46:16 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2005-08-16 22:46:16 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-08-16 22:52:28 - building world (CFLAGS=-O2 -pipe) TB --- 2005-08-16 22:52:28 - cd /src TB --- 2005-08-16 22:52:28 - /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 [...] mkdep -f .depend -a -I/src/sbin/gbde/../../sys -DRESCUE /src/sbin/gbde/gbde.c template.c /src/sbin/gbde/../../sys/crypto/rijndael/rijndael-alg-fst.c /src/sbin/gbde/../../sys/crypto/rijndael/rijndael-api-fst.c /src/sbin/gbde/../../sys/crypto/sha2/sha2.c /src/sbin/gbde/../../sys/geom/bde/g_bde_lock.c echo gbde: /obj/amd64/src/tmp/usr/lib/libc.a /obj/amd64/src/tmp/usr/lib/libmd.a /obj/amd64/src/tmp/usr/lib/libutil.a /obj/amd64/src/tmp/usr/lib/libgeom.a >> .depend cc -O2 -pipe -I/src/sbin/gbde/../../sys -DRESCUE -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /src/sbin/gbde/gbde.c cc -O2 -pipe -I/src/sbin/gbde/../../sys -DRESCUE -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c template.c cc -O2 -pipe -I/src/sbin/gbde/../../sys -DRESCUE -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /src/sbin/gbde/../../sys/crypto/rijndael/rijndael-alg-fst.c /src/sbin/gbde/../../sys/crypto/rijndael/rijndael-alg-fst.c: In function `rijndaelKeySetupEnc': /src/sbin/gbde/../../sys/crypto/rijndael/rijndael-alg-fst.c:737: warning: implicit declaration of function `KASSERT' /src/sbin/gbde/../../sys/crypto/rijndael/rijndael-alg-fst.c:738: warning: left-hand operand of comma expression has no effect *** Error code 1 Stop in /src/sbin/gbde. *** Error code 1 Stop in /obj/amd64/src/rescue/rescue. *** Error code 1 Stop in /src/rescue/rescue. *** Error code 1 Stop in /src/rescue. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-08-16 23:42:26 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-08-16 23:42:26 - ERROR: failed to build world TB --- 2005-08-16 23:42:26 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 16 23:58:42 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 5C46116A41F for ; Tue, 16 Aug 2005 23:58:42 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from deadcafe.de (deadcafe.de [81.169.162.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9120243D58 for ; Tue, 16 Aug 2005 23:58:41 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from dialin.t-online.de (p54A5D7C8.dip.t-dialin.net [84.165.215.200]) by deadcafe.de (8.13.4/8.13.4/Rock) with ESMTP id j7GNwaoV013223 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 17 Aug 2005 01:58:39 +0200 (CEST) X-Envelope-To: Received: from [172.23.7.254] (doom.rock.net [172.23.7.254]) by dialin.t-online.de (8.13.4/8.13.4/Rock) with ESMTP id j7GNwKcc097040 for ; Wed, 17 Aug 2005 01:58:20 +0200 (CEST) Message-ID: <43027D9E.7000602@deadcafe.de> Date: Wed, 17 Aug 2005 01:58:22 +0200 From: Daniel Rock User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20050815125657.A92343@cons.org> <20050815172250.GA32804@troutmask.apl.washington.edu> <20050815183846.A99145@cons.org> <430173BE.4080802@samsco.org> <20050816111428.A24284@cons.org> <43020F08.6070108@samsco.org> In-Reply-To: <43020F08.6070108@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.1 required=5.5 tests=FORGED_RCVD_HELO autolearn=disabled version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on deadcafe.de Subject: Re: 4 GB RAM showing up as 3, BIOS memory hole and all that X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Aug 2005 23:58:42 -0000 Scott Long schrieb: > AMD puts the memory controller into the CPU instead of in the > PCI host bridge, so it's much harder to have the two work together > to do the remapping. I believe that there are some Opteron > systems that can do this, though. The gory details are described in AMD's Technical Documentation #26094 (BIOS and Kernel Developer's Guide) http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/26094.PDF in section 3.5.8. Daniel From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 17 00:09:34 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 A596316A41F for ; Wed, 17 Aug 2005 00:09:34 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from deadcafe.de (deadcafe.de [81.169.162.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BBA943D64 for ; Wed, 17 Aug 2005 00:09:33 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from dialin.t-online.de (p54A5D7C8.dip.t-dialin.net [84.165.215.200]) by deadcafe.de (8.13.4/8.13.4/Rock) with ESMTP id j7H09Thj013251 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 17 Aug 2005 02:09:32 +0200 (CEST) X-Envelope-To: Received: from [172.23.7.254] (doom.rock.net [172.23.7.254]) by dialin.t-online.de (8.13.4/8.13.4/Rock) with ESMTP id j7H09NRC097328 for ; Wed, 17 Aug 2005 02:09:23 +0200 (CEST) Message-ID: <43028035.5000807@deadcafe.de> Date: Wed, 17 Aug 2005 02:09:25 +0200 From: Daniel Rock User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.1 required=5.5 tests=FORGED_RCVD_HELO autolearn=disabled version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on deadcafe.de Subject: Workaround for AMD64 Errata X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2005 00:09:34 -0000 Hi, have any of the AMD64 Errata with possible workarounds in software been addressed by FreeBSD? Errata List: http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/25759.pdf I'm just curious. I studied the OpenSolaris source code a little bit and found a huge list of OS workarounds for different errata mostly in the following file: usr/src/uts/i86pc/os/mp_startup.c Daniel From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 17 01:08:06 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 4F31816A41F for ; Wed, 17 Aug 2005 01:08:06 +0000 (GMT) (envelope-from googl3meister@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7532843D48 for ; Wed, 17 Aug 2005 01:08:05 +0000 (GMT) (envelope-from googl3meister@gmail.com) Received: by wproxy.gmail.com with SMTP id i22so63556wra for ; Tue, 16 Aug 2005 18:08:04 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=QmkWWy26yRs3rnpBU7LPuisCWVmpyNZC1ROudn5l85VZ2Nx9l6F2dqsVwf3F0/bXJ+MQrl1jyXSB5su8vP+s6ZTnaiWr08ZkohFOaUiWm8Vs5nt9GzFHM+4P+KB2yMFtzAOGMUyVjOo1Pi/U0MSTIPLkVUQ7ecmWiqRpRaudYaE= Received: by 10.54.15.11 with SMTP id 11mr67676wro; Tue, 16 Aug 2005 18:08:04 -0700 (PDT) Received: by 10.54.31.35 with HTTP; Tue, 16 Aug 2005 18:08:04 -0700 (PDT) Message-ID: <8f554029050816180853f0bef9@mail.gmail.com> Date: Wed, 17 Aug 2005 11:08:04 +1000 From: =?WINDOWS-1252?B?lSCV?= To: dR In-Reply-To: <20050803124814.17890.qmail@web52306.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050803124814.17890.qmail@web52306.mail.yahoo.com> Cc: freebsd-amd64@freebsd.org, freebsd-java@freebsd.org Subject: Re: Building JDK15 for AMD64 -- status of the "long-command" error? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2005 01:08:06 -0000 On 8/3/05, dR wrote: > A few weeks ago, someone on the AMD64 list was going > to try to find a solution to the "long-command" error > that one sees when trying to build JDK15 for AMD64. >=20 > One theory is that this problem is caused by a bug in > the Linux Java binary that is needed to seed the > FreeBSD build. >=20 > While sifting through the mail archive yesterday, I > saw a comment by someone saying that the JDK15 problem > does not exist in 5.4 CURRENT. (I am using 5.4 > STABLE.) >=20 > Would someone please confirm whether the bug exists in > 5.4 CURRENT or 6.0? >=20 > Marko > Ottawa, Canada >=20 For the archives - when I first installed it, I had the 'long command' issue and naively didn't write it down expecting it to come up again when the next portupgrade happened along... Ever since then it builds successfully... and I won't be in a position to completely remove and reinstall to locate this error for some time. Someone provided some scripts to check the command line length problem, but they ran for >24 hours on my box without erroring out - I changed the 'jump size' to 6 levels and re-ran it with same results, albeit for a much shorter time (about an hour). 5.4-STABLE on AMD-64/3000+/2GB/Asus A8V Deluxe > java -version java version "1.5.0-p1" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-p1-gm_13_aug_2005_14_37) Java HotSpot(TM) 64-Bit Server VM (build 1.5.0-p1-gm_13_aug_2005_14_37, mixed mode) 1 thing to note - the build will 'appear' to hang at the end, but it just takes ages to do it's thing (compiling the javadocs from memory)... -- g'luck gm From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 17 02:22:00 2005 Return-Path: X-Original-To: amd64@freebsd.org 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 0128D16A420 for ; Wed, 17 Aug 2005 02:22:00 +0000 (GMT) (envelope-from mi+kde@aldan.algebra.com) Received: from mail27.sea5.speakeasy.net (mail27.sea5.speakeasy.net [69.17.117.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2994343D48 for ; Wed, 17 Aug 2005 02:21:59 +0000 (GMT) (envelope-from mi+kde@aldan.algebra.com) Received: (qmail 1600 invoked from network); 17 Aug 2005 02:21:58 -0000 Received: from aldan.algebra.com (HELO blue.virtual-estates.net) ([216.254.65.224]) (envelope-sender ) by mail27.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 17 Aug 2005 02:21:58 -0000 Received: from blue.virtual-estates.net (blue [127.0.0.1]) by blue.virtual-estates.net (8.13.3/8.13.3) with ESMTP id j7H2Lvmq030475; Tue, 16 Aug 2005 22:21:57 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by blue.virtual-estates.net (8.13.3/8.13.3/Submit) id j7H2LvAb030474; Tue, 16 Aug 2005 22:21:57 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) X-Authentication-Warning: blue.virtual-estates.net: mi set sender to mi+kde@aldan.algebra.com using -f From: Mikhail Teterin To: voisine@gmail.com Date: Tue, 16 Aug 2005 22:21:56 -0400 User-Agent: KMail/1.8.1 X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7whJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Cc: amd64@freebsd.org, gnome@freebsd.org Subject: using linux-firefox on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2005 02:22:00 -0000 Hi! I found, that the only way to use the linux-firefox (a 32-bit Linux binary) on amd64 is by removing the ~/.fonts.cache-1 prior to starting it -- the process gets SIGILL on startup otherwise. Is that because the file is architecture specific, or because the versions of whatever library maintains it (freetype?) differ too much between FreeBSD's native and what's installed by linux compatability ports (linux_base-8 in my case)? -mi From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 17 02:42:36 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 5D1AA16A41F for ; Wed, 17 Aug 2005 02:42:36 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 099AA43D49 for ; Wed, 17 Aug 2005 02:42:31 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 35A0611EB9 for ; Tue, 16 Aug 2005 20:42:31 -0600 (MDT) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 11A6F11EB8 for ; Tue, 16 Aug 2005 20:42:31 -0600 (MDT) Date: Tue, 16 Aug 2005 20:42:29 -0600 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20050816204229.758827a5.kgunders@teamcool.net> In-Reply-To: <4301E39F.1050500@samsco.org> References: <20050816121701.74816.qmail@web54306.mail.yahoo.com> <4301E39F.1050500@samsco.org> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Asus A8V-E Deluxe discontinued (was Re: Hi) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2005 02:42:36 -0000 On Tue, 16 Aug 2005 07:01:19 -0600 Scott Long wrote: > Frank S. wrote: > > Hi > > I want to start using freebsd, and i'm not sure if it will work on my system, I have a asus A8V-E Deluxe motherboard and Ati pci expres video card X700 Pro. > > thank you > > > > Frank > > > > > > I have almost the same system, but with an X600 card. It works fine > with the exception of the on-board network controllers. As long as > you're willing to drop in an alternate network card, it's a very > good board. I just noticed that Asus is discontinuing this mainboard so if you've been wanting one it's a good time to get one while you can. Might look for them to be priced for clearance as well... -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 17 03:10:56 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 DD68E16A41F for ; Wed, 17 Aug 2005 03:10:56 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 712C343D45 for ; Wed, 17 Aug 2005 03:10:51 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [172.20.101.145] ([12.167.156.2]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j7H3LoAq056205; Tue, 16 Aug 2005 21:21:51 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4302AA97.8030002@samsco.org> Date: Tue, 16 Aug 2005 21:10:15 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ken Gunderson References: <20050816121701.74816.qmail@web54306.mail.yahoo.com> <4301E39F.1050500@samsco.org> <20050816204229.758827a5.kgunders@teamcool.net> In-Reply-To: <20050816204229.758827a5.kgunders@teamcool.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: freebsd-amd64@freebsd.org Subject: Re: Asus A8V-E Deluxe discontinued (was Re: Hi) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2005 03:10:57 -0000 Ken Gunderson wrote: > On Tue, 16 Aug 2005 07:01:19 -0600 > Scott Long wrote: > > >>Frank S. wrote: >> >>>Hi >>>I want to start using freebsd, and i'm not sure if it will work on my system, I have a asus A8V-E Deluxe motherboard and Ati pci expres video card X700 Pro. >>>thank you >>> >>>Frank >>> >>> >> >>I have almost the same system, but with an X600 card. It works fine >>with the exception of the on-board network controllers. As long as >>you're willing to drop in an alternate network card, it's a very >>good board. > > > I just noticed that Asus is discontinuing this mainboard so if you've > been wanting one it's a good time to get one while you can. Might look > for them to be priced for clearance as well... > I forgot to mention that this board doesn't support dual core chips. That's probably why it's being discontinued. Scott From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 17 04:27:12 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 76CEC16A41F; Wed, 17 Aug 2005 04:27:12 +0000 (GMT) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (glewis.dsl.xmission.com [166.70.56.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5C2E43D45; Wed, 17 Aug 2005 04:27:11 +0000 (GMT) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (localhost.eyesbeyond.com [127.0.0.1]) by misty.eyesbeyond.com (8.13.3/8.13.3) with ESMTP id j7H4RAJ3024309; Tue, 16 Aug 2005 22:27:10 -0600 (MDT) (envelope-from glewis@eyesbeyond.com) Received: (from glewis@localhost) by misty.eyesbeyond.com (8.13.3/8.13.3/Submit) id j7H4R9eY024308; Tue, 16 Aug 2005 22:27:09 -0600 (MDT) (envelope-from glewis@eyesbeyond.com) X-Authentication-Warning: misty.eyesbeyond.com: glewis set sender to glewis@eyesbeyond.com using -f Date: Tue, 16 Aug 2005 22:27:08 -0600 From: Greg Lewis To: ? ? Message-ID: <20050817042708.GA24252@misty.eyesbeyond.com> References: <20050803124814.17890.qmail@web52306.mail.yahoo.com> <8f554029050816180853f0bef9@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8f554029050816180853f0bef9@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: dR , freebsd-amd64@freebsd.org, freebsd-java@freebsd.org Subject: Re: Building JDK15 for AMD64 -- status of the "long-command" error? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2005 04:27:12 -0000 On Wed, Aug 17, 2005 at 11:08:04AM +1000, ? ? wrote: > For the archives - when I first installed it, I had the 'long command' > issue and naively didn't write it down expecting it to come up again > when the next portupgrade happened along... Ever since then it builds > successfully... and I won't be in a position to completely remove and > reinstall to locate this error for some time. Thats because the successive portupgrades will use the installed native JDK to bootstrap the build rather than reverting to using the Linux JDK it had to use originally. This problem is only seen with the Linux JDK, it isn't seen with a native JDK. > Someone provided some scripts to check the command line length > problem, but they ran for >24 hours on my box without erroring out - I > changed the 'jump size' to 6 levels and re-ran it with same results, > albeit for a much shorter time (about an hour). > > 5.4-STABLE on AMD-64/3000+/2GB/Asus A8V Deluxe > > java -version > java version "1.5.0-p1" > Java(TM) 2 Runtime Environment, Standard Edition (build > 1.5.0-p1-gm_13_aug_2005_14_37) > Java HotSpot(TM) 64-Bit Server VM (build > 1.5.0-p1-gm_13_aug_2005_14_37, mixed mode) Same problem - this is the native JDK, it won't show the issue. -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 17 05:53:04 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 F14F616A41F for ; Wed, 17 Aug 2005 05:53:04 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (koyukuk.teamcool.net [209.161.34.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 966A343D46 for ; Wed, 17 Aug 2005 05:53:02 +0000 (GMT) (envelope-from kgunders@teamcool.net) Received: from koyukuk.teamcool.net (localhost [127.0.0.1]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id A704A11EB9 for ; Tue, 16 Aug 2005 23:53:01 -0600 (MDT) Received: from cochise.teamcool.net (unknown [192.168.1.57]) by koyukuk.teamcool.net (TeamCool Rocks) with ESMTP id 70A8F11EB8 for ; Tue, 16 Aug 2005 23:53:01 -0600 (MDT) Date: Tue, 16 Aug 2005 23:53:00 -0600 From: Ken Gunderson To: freebsd-amd64@freebsd.org Message-Id: <20050816235300.4dc8924e.kgunders@teamcool.net> In-Reply-To: <4302AA97.8030002@samsco.org> References: <20050816121701.74816.qmail@web54306.mail.yahoo.com> <4301E39F.1050500@samsco.org> <20050816204229.758827a5.kgunders@teamcool.net> <4302AA97.8030002@samsco.org> Organization: Teamcool Networks X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: Asus A8V-E Deluxe discontinued (was Re: Hi) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2005 05:53:05 -0000 On Tue, 16 Aug 2005 21:10:15 -0600 Scott Long wrote: > Ken Gunderson wrote: > > On Tue, 16 Aug 2005 07:01:19 -0600 > > Scott Long wrote: > > > > > >>Frank S. wrote: > >> > >>>Hi > >>>I want to start using freebsd, and i'm not sure if it will work on my system, I have a asus A8V-E Deluxe motherboard and Ati pci expres video card X700 Pro. > >>>thank you > >>> > >>>Frank > >>> > >>> > >> > >>I have almost the same system, but with an X600 card. It works fine > >>with the exception of the on-board network controllers. As long as > >>you're willing to drop in an alternate network card, it's a very > >>good board. > > > > > > I just noticed that Asus is discontinuing this mainboard so if you've > > been wanting one it's a good time to get one while you can. Might look > > for them to be priced for clearance as well... > > > > I forgot to mention that this board doesn't support dual core chips. > That's probably why it's being discontinued. Which seems a bit incongruous at first blush since per Asus website the A8V-E SE does support dual core and both boards use the same VIA K8T890 chipset but I guess there's some other stumbling block. Been a busy boy as of late building systems for others. Now it's my turn and I've got a couple of the A8V-E SE's on order;-) Can't wait! Might be a mistake but I decided to forgo the dual core for now in favor of a 3700+ -- Best regards, Ken Gunderson Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 17 14:36:25 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 6D8D116A41F for ; Wed, 17 Aug 2005 14:36:25 +0000 (GMT) (envelope-from dystopianrebel@yahoo.com) Received: from web52305.mail.yahoo.com (web52305.mail.yahoo.com [206.190.48.148]) by mx1.FreeBSD.org (Postfix) with SMTP id E1EDF43D45 for ; Wed, 17 Aug 2005 14:36:24 +0000 (GMT) (envelope-from dystopianrebel@yahoo.com) Received: (qmail 61752 invoked by uid 60001); 17 Aug 2005 14:36:24 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=W/DePD7I0yKvw3YCckRqeuGobZxvw5ZDfdWwniJvjq406OPyaZ+Bp7oE8Oda5rvjc5dbQb1rjIHxgTuiiClnnCh0aCkWV6DTW8SvWMSdIV+d72ugmy4N/7gFbef4aGJaSfPWDBlaDCZ0/8yeNbn9Axc1Yx1mcSC+yGUy/ILGmLM= ; Message-ID: <20050817143624.61750.qmail@web52305.mail.yahoo.com> Received: from [205.210.232.62] by web52305.mail.yahoo.com via HTTP; Wed, 17 Aug 2005 07:36:24 PDT Date: Wed, 17 Aug 2005 07:36:24 -0700 (PDT) From: dR To: freebsd-amd64@freebsd.org, skreetch_fr@yahoo.fr MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Openoffice 1.1 with gcc-ooo X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2005 14:36:25 -0000 Bonjour d'Ottawa, Canada! You can't build OO 1.1 on AMD64. But you can run an i386 build of OO 1.1 on AMD64 if you have the compatibility set in the kernel. (C'est presqu'une certitude si vous utilisez une version récente de FreeBSD pour AMD64.) Alors, il vous faut trouver quelqu'un qui possède l'archive d'installation («package») d' OO 1.1. Moi, je l'ai en anglais si cela vous intéresse. m! ------------------------------ Message: 9 Date: Tue, 16 Aug 2005 20:29:28 +0200 From: Skreetch Subject: Openoffice 1.1 with gcc-ooo To: freebsd-amd64@freebsd.org Message-ID: <43023088.90500@yahoo.fr> Content-Type: text/plain; charset=ISO-8859-1 Hello, I'd like to install OpenOffice 1.1 using the ports collection (editors/openoffice-1.1) on FreeBSD 5.4 / AMD64 release. My ports collection, my "world" and my kernel are up to date. It's trying to install the lang/gcc32 application. I installed lang/gcc-ooo but it's the same result: ===> fr-openoffice-1.1.5.rc2.1 depends on executable: gcc32 - not found ===> Verifying install for gcc32 in /usr/ports/lang/gcc32 ===> gcc-3.2.3_3 does not run on amd64, and you are running amd64. *** Error code 1 Stop in /usr/ports/lang/gcc32. *** Error code 1 Stop in /usr/ports/editors/openoffice-1.1. How can I do it ? Thanks for your help. Skreetch ------------ __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 17 14:37:03 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 50CC816A41F for ; Wed, 17 Aug 2005 14:37:03 +0000 (GMT) (envelope-from martin@gneto.com) Received: from av12-1-sn2.hy.skanova.net (av12-1-sn2.hy.skanova.net [81.228.8.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id D25BA43D45 for ; Wed, 17 Aug 2005 14:37:02 +0000 (GMT) (envelope-from martin@gneto.com) Received: by av12-1-sn2.hy.skanova.net (Postfix, from userid 502) id 8D0EB37F0C; Wed, 17 Aug 2005 16:37:01 +0200 (CEST) Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net [81.228.8.92]) by av12-1-sn2.hy.skanova.net (Postfix) with ESMTP id 3B8E437F02; Wed, 17 Aug 2005 16:37:01 +0200 (CEST) Received: from [192.168.2.30] (h99n2fls34o985.telia.com [213.66.202.99]) by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id D704237E44; Wed, 17 Aug 2005 16:36:55 +0200 (CEST) Message-ID: <43034B86.9080900@gneto.com> Date: Wed, 17 Aug 2005 16:36:54 +0200 From: Martin Nilsson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: sv, en-us, en MIME-Version: 1.0 To: Scott Long References: <20050815125657.A92343@cons.org> <20050815172250.GA32804@troutmask.apl.washington.edu> <20050815183846.A99145@cons.org> <430173BE.4080802@samsco.org> <20050816111428.A24284@cons.org> <43020F08.6070108@samsco.org> In-Reply-To: <43020F08.6070108@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Martin Cracauer , freebsd-amd64@freebsd.org Subject: Re: 4 GB RAM showing up as 3, BIOS memory hole and all that X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2005 14:37:03 -0000 Scott Long wrote: > not do the remapping and result in you loosing effective RAM. The > difference between Intel and AMD is because AMD puts the memory > controller into the CPU instead of in the PCI host bridge, so it's much > harder to have the two work together to do the remapping. I believe > that there are some Opteron systems that can do this, though. The E stepping Opteron can remap memory. The earlier versions can't. The 252 and above is only avalable as rev. E, the slower models are being replaced in the near future. In order to use the remap feature your motherboard BIOS must know about it and have settings for memory remap. /Martin From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 17 16:47:10 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 13A0F16A41F for ; Wed, 17 Aug 2005 16:47:10 +0000 (GMT) (envelope-from ghelmer@palisadesys.com) Received: from magellan.palisadesys.com (magellan.palisadesys.com [192.188.162.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DBDD43D64 for ; Wed, 17 Aug 2005 16:47:04 +0000 (GMT) (envelope-from ghelmer@palisadesys.com) Received: from [172.16.1.108] (cetus.palisadesys.com [192.188.162.7]) (authenticated bits=0) by magellan.palisadesys.com (8.12.11/8.12.11) with ESMTP id j7HGl1fC081084; Wed, 17 Aug 2005 11:47:02 -0500 (CDT) (envelope-from ghelmer@palisadesys.com) Message-ID: <43036A03.2030708@palisadesys.com> Date: Wed, 17 Aug 2005 11:46:59 -0500 From: Guy Helmer User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Martin Nilsson References: <42D66D84.9010701@palisadesys.com> <42D68EDA.7050808@mullet.se> In-Reply-To: <42D68EDA.7050808@mullet.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Palisade-MailScanner-Information: Please contact the ISP for more information X-Palisade-MailScanner: Found to be clean X-MailScanner-From: ghelmer@palisadesys.com Cc: freebsd-amd64@freebsd.org Subject: Re: Supermicro H8DAR-8 motherboard X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2005 16:47:10 -0000 Martin Nilsson wrote: > Guy Helmer wrote: > >> Has anyone on the list tried the new Supermicro H8DAR-8 or related >> motherboards for Opterons? If so, any issues? > > > I have a H8DAE running in a test-box before we start selling them. > > So far I have ony found one problem: > It is impossible to boot FreeBSD/i386 with the 1U IPMI card, the > kernel panics when loading the keyboard driver. This does not happen > with FreeBSD/amd64. I haven't tested how well the IPMI card works in > FreeBSD, there may be problems with the bge driver. > > Other than that I really like the board. If you have any more > questions I'll be happy to answer them. > We received the H8DAR-8 unit a little over a week ago with dual Opteron 275s and it has been running well since. I didn't have any problem installing FreeBSD 6.0-BETA1, and I ran "make -j12 buildworld" continuously on it over a weekend. It finally crashed on an sbfree call, but I'd chalk that up to BETA1. It's been solid under a lighter load since. I like the board and I'm glad Supermicro was able to cram it into a 1U case :-) Guy -- Guy Helmer, Ph.D. Principal System Architect Palisade Systems, Inc. From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 17 20:25:35 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 31AA716A421 for ; Wed, 17 Aug 2005 20:25:35 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F76D43D5A for ; Wed, 17 Aug 2005 20:25:34 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [127.0.0.1] (pooker.samsco.org [168.103.85.57]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j7HKaO4G060879; Wed, 17 Aug 2005 14:36:25 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <43039D1E.8070209@samsco.org> Date: Wed, 17 Aug 2005 14:25:02 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Guy Helmer References: <42D66D84.9010701@palisadesys.com> <42D68EDA.7050808@mullet.se> <43036A03.2030708@palisadesys.com> In-Reply-To: <43036A03.2030708@palisadesys.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: Martin Nilsson , freebsd-amd64@freebsd.org Subject: Re: Supermicro H8DAR-8 motherboard X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2005 20:25:35 -0000 Guy Helmer wrote: > Martin Nilsson wrote: > >> Guy Helmer wrote: >> >>> Has anyone on the list tried the new Supermicro H8DAR-8 or related >>> motherboards for Opterons? If so, any issues? >> >> >> >> I have a H8DAE running in a test-box before we start selling them. >> >> So far I have ony found one problem: >> It is impossible to boot FreeBSD/i386 with the 1U IPMI card, the >> kernel panics when loading the keyboard driver. This does not happen >> with FreeBSD/amd64. I haven't tested how well the IPMI card works in >> FreeBSD, there may be problems with the bge driver. >> >> Other than that I really like the board. If you have any more >> questions I'll be happy to answer them. >> > We received the H8DAR-8 unit a little over a week ago with dual Opteron > 275s and it has been running well since. I didn't have any problem > installing FreeBSD 6.0-BETA1, and I ran "make -j12 buildworld" > continuously on it over a weekend. It finally crashed on an sbfree > call, but I'd chalk that up to BETA1. It's been solid under a lighter > load since. I like the board and I'm glad Supermicro was able to cram > it into a 1U case :-) > > Guy > Do you have any crash data on the panic? Unfortunately, we haven't perfected the 'self fixing beta release', so we rely on good reports to get bugs fixed manually =-) Scott From owner-freebsd-amd64@FreeBSD.ORG Wed Aug 17 21:11:26 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 6662516A41F for ; Wed, 17 Aug 2005 21:11:26 +0000 (GMT) (envelope-from ghelmer@palisadesys.com) Received: from magellan.palisadesys.com (magellan.palisadesys.com [192.188.162.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07A5443D46 for ; Wed, 17 Aug 2005 21:11:25 +0000 (GMT) (envelope-from ghelmer@palisadesys.com) Received: from [172.16.1.108] (cetus.palisadesys.com [192.188.162.7]) (authenticated bits=0) by magellan.palisadesys.com (8.12.11/8.12.11) with ESMTP id j7HLBJiA098426; Wed, 17 Aug 2005 16:11:22 -0500 (CDT) (envelope-from ghelmer@palisadesys.com) Message-ID: <4303A7F7.5050408@palisadesys.com> Date: Wed, 17 Aug 2005 16:11:19 -0500 From: Guy Helmer User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <42D66D84.9010701@palisadesys.com> <42D68EDA.7050808@mullet.se> <43036A03.2030708@palisadesys.com> <43039D1E.8070209@samsco.org> In-Reply-To: <43039D1E.8070209@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Palisade-MailScanner-Information: Please contact the ISP for more information X-Palisade-MailScanner: Found to be clean X-MailScanner-From: ghelmer@palisadesys.com Cc: Martin Nilsson , freebsd-amd64@freebsd.org Subject: Re: Supermicro H8DAR-8 motherboard X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2005 21:11:26 -0000 Scott Long wrote: > Guy Helmer wrote: > >> Martin Nilsson wrote: >> >>> Guy Helmer wrote: >>> >>>> Has anyone on the list tried the new Supermicro H8DAR-8 or related >>>> motherboards for Opterons? If so, any issues? >>> >>> >>> >>> >>> I have a H8DAE running in a test-box before we start selling them. >>> >>> So far I have ony found one problem: >>> It is impossible to boot FreeBSD/i386 with the 1U IPMI card, the >>> kernel panics when loading the keyboard driver. This does not happen >>> with FreeBSD/amd64. I haven't tested how well the IPMI card works in >>> FreeBSD, there may be problems with the bge driver. >>> >>> Other than that I really like the board. If you have any more >>> questions I'll be happy to answer them. >>> >> We received the H8DAR-8 unit a little over a week ago with dual >> Opteron 275s and it has been running well since. I didn't have any >> problem installing FreeBSD 6.0-BETA1, and I ran "make -j12 >> buildworld" continuously on it over a weekend. It finally crashed on >> an sbfree call, but I'd chalk that up to BETA1. It's been solid >> under a lighter load since. I like the board and I'm glad Supermicro >> was able to cram it into a 1U case :-) >> >> Guy >> > > Do you have any crash data on the panic? Unfortunately, we haven't > perfected the 'self fixing beta release', so we rely on good reports > to get bugs fixed manually =-) > > Scott I'll have to build a kernel with the debugging features to get a useful backtrace (if I can make it happen again with the current BETA-2 sources). I'll try to get it started tomorrow. Guy -- Guy Helmer, Ph.D. Principal System Architect Palisade Systems, Inc. From owner-freebsd-amd64@FreeBSD.ORG Thu Aug 18 03:32:08 2005 Return-Path: X-Original-To: amd64@freebsd.org 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 CA65D16A420 for ; Thu, 18 Aug 2005 03:32:08 +0000 (GMT) (envelope-from mi+kde@aldan.algebra.com) Received: from mail22.sea5.speakeasy.net (mail22.sea5.speakeasy.net [69.17.117.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1246E43D45 for ; Thu, 18 Aug 2005 03:32:07 +0000 (GMT) (envelope-from mi+kde@aldan.algebra.com) Received: (qmail 7216 invoked from network); 18 Aug 2005 03:32:07 -0000 Received: from aldan.algebra.com (HELO blue.virtual-estates.net) ([216.254.65.224]) (envelope-sender ) by mail22.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 18 Aug 2005 03:32:07 -0000 Received: from blue.virtual-estates.net (blue [127.0.0.1]) by blue.virtual-estates.net (8.13.3/8.13.3) with ESMTP id j7I3W6P0043105; Wed, 17 Aug 2005 23:32:06 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by blue.virtual-estates.net (8.13.3/8.13.3/Submit) id j7I3W5Gs043104; Wed, 17 Aug 2005 23:32:05 -0400 (EDT) (envelope-from mi+kde@aldan.algebra.com) X-Authentication-Warning: blue.virtual-estates.net: mi set sender to mi+kde@aldan.algebra.com using -f From: Mikhail Teterin To: Q Date: Wed, 17 Aug 2005 23:32:05 -0400 User-Agent: KMail/1.8.1 References: <200508171230.j7HCU2pl052524@corbulon.video-collage.com> In-Reply-To: X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7whJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Cc: amd64@freebsd.org, current@freebsd.org Subject: Re: nvnet does not see NVidia's adapter on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Aug 2005 03:32:08 -0000 On Wednesday 17 August 2005 07:41 pm, Q wrote: = = Incidentally. Does 6.0 support the Marvell PHY you have on that = motherboard or is it still defaulting to the ukphy driver? I have not the slightest idea... Maybe, someone on these two mailing lists can answer? -mi From owner-freebsd-amd64@FreeBSD.ORG Thu Aug 18 10:20:19 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org 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 9FB1016A41F for ; Thu, 18 Aug 2005 10:20:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18B1C43D64 for ; Thu, 18 Aug 2005 10:20:16 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7IAKF6M087843 for ; Thu, 18 Aug 2005 10:20:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7IAKFQX087842; Thu, 18 Aug 2005 10:20:15 GMT (envelope-from gnats) Resent-Date: Thu, 18 Aug 2005 10:20:15 GMT Resent-Message-Id: <200508181020.j7IAKFQX087842@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, Pika Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D0EE16A41F for ; Thu, 18 Aug 2005 10:17:58 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B1FD43D53 for ; Thu, 18 Aug 2005 10:17:58 +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 j7IAHvuN018647 for ; Thu, 18 Aug 2005 10:17:57 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id j7IAHvQ4018646; Thu, 18 Aug 2005 10:17:57 GMT (envelope-from nobody) Message-Id: <200508181017.j7IAHvQ4018646@www.freebsd.org> Date: Thu, 18 Aug 2005 10:17:57 GMT From: Pika To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/85081: TeamSpeak X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Aug 2005 10:20:19 -0000 >Number: 85081 >Category: amd64 >Synopsis: TeamSpeak >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Aug 18 10:20:15 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Pika >Release: >Organization: >Environment: FreeBSD NewGameServer 5.4-RELEASE-p6 FreeBSD 5.4-RELEASE-p6 #1: Sun Aug 7 21:53:39 MSD 2005 pika@NewGameServer:/usr/obj/usr/src/sys/PIKA amd64 >Description: root@NewGameServer# ./teamspeak_server.sh.sample start Runtime error 230 at 0805975D su: line 1: 4102 Segmentation fault (core dumped) ./server_linux >/dev/null >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Thu Aug 18 15:12:59 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 277BE16A41F for ; Thu, 18 Aug 2005 15:12:59 +0000 (GMT) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0B3F43D46 for ; Thu, 18 Aug 2005 15:12:56 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.150] (host-150.int.kcilink.com [192.168.7.150]) by yertle.kcilink.com (Postfix) with ESMTP id 3747CB816 for ; Thu, 18 Aug 2005 11:12:55 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v733) In-Reply-To: <43034B86.9080900@gneto.com> References: <20050815125657.A92343@cons.org> <20050815172250.GA32804@troutmask.apl.washington.edu> <20050815183846.A99145@cons.org> <430173BE.4080802@samsco.org> <20050816111428.A24284@cons.org> <43020F08.6070108@samsco.org> <43034B86.9080900@gneto.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <16572053-1E41-4156-8CA9-362832D1CD60@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Thu, 18 Aug 2005 11:12:53 -0400 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.733) Subject: Re: 4 GB RAM showing up as 3, BIOS memory hole and all that X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Aug 2005 15:12:59 -0000 On Aug 17, 2005, at 10:36 AM, Martin Nilsson wrote: > The E stepping Opteron can remap memory. The earlier versions can't. > How does one tell the stepping is E? My dmesg.boot says "Id = 0xf5a Stepping = 10" on my 246 CPUs. Vivek Khera, Ph.D. +1-301-869-4449 x806 From owner-freebsd-amd64@FreeBSD.ORG Thu Aug 18 17:50:32 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 83BBF16A41F for ; Thu, 18 Aug 2005 17:50:32 +0000 (GMT) (envelope-from eh-lists-freebsd@critical.ch) Received: from smtp.hispeed.ch (mxout.hispeed.ch [62.2.95.247]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACC4143D45 for ; Thu, 18 Aug 2005 17:50:31 +0000 (GMT) (envelope-from eh-lists-freebsd@critical.ch) Received: from beaver (217-162-251-247.dclient.hispeed.ch [217.162.251.247]) by smtp.hispeed.ch (8.12.6/8.12.6/tornado-1.0) with SMTP id j7IHoTNN019410 for ; Thu, 18 Aug 2005 19:50:29 +0200 Date: Thu, 18 Aug 2005 19:50:29 +0200 From: Emanuel Haupt To: freebsd-amd64@freebsd.org Message-Id: <20050818195029.770270cf.eh-lists-freebsd@critical.ch> X-Mailer: Sylpheed version 1.0.5 (GTK+ 1.2.10; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on smtp-05.tornado.cablecom.ch X-Virus-Status: Clean X-DCC-spamcheck-02.tornado.cablecom.ch-Metrics: smtp-05.tornado.cablecom.ch 32701; Body=1 Fuz1=1 Fuz2=1 Subject: need help testing a port on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Aug 2005 17:50:32 -0000 Hi, I made a new port (audio/xmms-nsf) and I am not sure if it needs to be built with -fPIC on amd64 archs. Could someone with an amd64 arch build the port and send me the output of the build? Without -fPIC http://critical.ch/xmms-nsf.shar With -fPIC http://critical.ch/xmms-nsf.with-fPIC.shar Thanks in advance for any volunteers. - emanuel From owner-freebsd-amd64@FreeBSD.ORG Thu Aug 18 18:41:41 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 E127016A41F for ; Thu, 18 Aug 2005 18:41:41 +0000 (GMT) (envelope-from flynn@energyhq.es.eu.org) Received: from mindfields.energyhq.es.eu.org (73.Red-213-97-200.pooles.rima-tde.net [213.97.200.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3351D43D46 for ; Thu, 18 Aug 2005 18:41:37 +0000 (GMT) (envelope-from flynn@energyhq.es.eu.org) Received: from scienide.energyhq.es.eu.org (scienide.energyhq.es.eu.org [192.168.100.1]) by mindfields.energyhq.es.eu.org (Postfix) with SMTP id 6C7A1123FCD; Thu, 18 Aug 2005 20:41:34 +0200 (CEST) Date: Thu, 18 Aug 2005 20:41:23 +0200 From: Miguel Mendez To: Emanuel Haupt Message-Id: <20050818204123.29ce61db.flynn@energyhq.es.eu.org> In-Reply-To: <20050818195029.770270cf.eh-lists-freebsd@critical.ch> References: <20050818195029.770270cf.eh-lists-freebsd@critical.ch> X-Mailer: Sylpheed version 2.0.0 (GTK+ 2.6.9; 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: need help testing a port on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Aug 2005 18:41:42 -0000 On Thu, 18 Aug 2005 19:50:29 +0200 Emanuel Haupt wrote: > Hi, > > I made a new port (audio/xmms-nsf) and I am not sure if it needs to be > built with -fPIC on amd64 archs. > > Could someone with an amd64 arch build the port and send me the output > of the build? > > Without -fPIC > http://critical.ch/xmms-nsf.shar This one fails during the last link stage. /usr/bin/ld: ../../src/nes/.libs/libnez.a(handler.o): relocation R_X86_64_32S can not be used when making a shared object; recompile with -fPIC ../../src/nes/.libs/libnez.a(handler.o): could not read symbols: Bad value *** Error code 1 > With -fPIC > http://critical.ch/xmms-nsf.with-fPIC.shar Works fine on 6.0-BETA2. Cheers, -- Miguel Mendez http://www.energyhq.es.eu.org PGP Key: 0xDC8514F1 From owner-freebsd-amd64@FreeBSD.ORG Thu Aug 18 20:12:27 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 E285C16A41F for ; Thu, 18 Aug 2005 20:12:27 +0000 (GMT) (envelope-from martin@gneto.com) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04C7743D46 for ; Thu, 18 Aug 2005 20:12:25 +0000 (GMT) (envelope-from martin@gneto.com) Received: from as6-1-5.kr.m.bonet.se ([83.227.181.30] [83.227.181.30]) by mxfep02.bredband.com with ESMTP id <20050818201225.LPNL17509.mxfep02.bredband.com@as6-1-5.kr.m.bonet.se>; Thu, 18 Aug 2005 22:12:25 +0200 Received: from [192.168.10.11] (euklides.gneto.com [192.168.10.11]) by as6-1-5.kr.m.bonet.se (Postfix) with ESMTP id 5EFE7678B9; Thu, 18 Aug 2005 22:12:15 +0200 (CEST) Message-ID: <4304EB9F.1090403@gneto.com> Date: Thu, 18 Aug 2005 22:12:15 +0200 From: Martin Nilsson User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050724) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vivek Khera References: <20050815125657.A92343@cons.org> <20050815172250.GA32804@troutmask.apl.washington.edu> <20050815183846.A99145@cons.org> <430173BE.4080802@samsco.org> <20050816111428.A24284@cons.org> <43020F08.6070108@samsco.org> <43034B86.9080900@gneto.com> <16572053-1E41-4156-8CA9-362832D1CD60@khera.org> In-Reply-To: <16572053-1E41-4156-8CA9-362832D1CD60@khera.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: 4 GB RAM showing up as 3, BIOS memory hole and all that X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Aug 2005 20:12:28 -0000 Vivek Khera wrote: > > On Aug 17, 2005, at 10:36 AM, Martin Nilsson wrote: > >> The E stepping Opteron can remap memory. The earlier versions can't. >> > > How does one tell the stepping is E? My dmesg.boot says "Id = 0xf5a > Stepping = 10" on my 246 CPUs. The document here: http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/25759.pdf Says that it is stepping CG, the one before E4. This one is common in shops right now. You can get the meaning of the ordernumber (number on top of the CPU) at this page: http://www.amdcompare.com/us%2Den/opteron/Default.aspx I have not been able to get E4 stepping 246:es yet in Sweden, they are simply not available yet. Regards, Martin Nilsson From owner-freebsd-amd64@FreeBSD.ORG Fri Aug 19 09:27:55 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 168CC16A41F for ; Fri, 19 Aug 2005 09:27:55 +0000 (GMT) (envelope-from vasim@human-capital.ru) Received: from wolf.resume-bank.ru (mail.resume-bank.ru [62.118.252.60]) by mx1.FreeBSD.org (Postfix) with SMTP id 25FF043D53 for ; Fri, 19 Aug 2005 09:27:53 +0000 (GMT) (envelope-from vasim@human-capital.ru) Received: (qmail 34346 invoked by uid 0); 19 Aug 2005 09:30:02 -0000 Received: from unknown (HELO vasimwork) (213.33.147.104) by mail.resume-bank.ru with SMTP; 19 Aug 2005 09:30:02 -0000 Message-ID: <00d601c5a88e$1cb8c260$2107a8c0@vasimwork> From: "Vasim Valejev" To: Date: Wed, 24 Aug 2005 13:27:56 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Subject: Slow PCI-X controller perfomance (adaptec 2130SLP) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2005 09:27:55 -0000 Hi ! I've tried to set up FreeBSD-current on Dual opteron box with Adaptec 2130SLP PCI-X RAID controller (256MB memory). My tests did show that maximum transfer rate from controller to OS was about 132MB/s. That is very strange since PCI-X maximum speed should be about 1GB/s. Why the controller was so slow? Because poor driver or my method of the test? To test transfer rate, i just did run command "dd if=/dev/aacd1 of=/dev/null bs=8k count=4k" many times (may be i'm wrong but the controller shall cache this request in its memory). Change of hw.aac.iosize_max to 98k did a very little effect. My system config: Tyan K8SD Pro (S2882-D) motherboard (onboard SATA controller was turned off) 2xOpteron 244 2GB memory (2x512MB RAM stick for each CPU) Adaptec 2130SLP RAID controller with 256MB memory and backup battery (tried every PCI-X slot on the MB with same results) Six Maxtor Atlas 15K2 36GB drives (8E036J0) on the SCSI channel (but only four was used for /dev/aacd1, RAID5 with 64K stripe) FreeBSD7.0-CURRENT/amd64 (Tested with 5.4-RELEASE/amd64 and 6.0-BETA2/386 but no difference). Vasim V. From owner-freebsd-amd64@FreeBSD.ORG Fri Aug 19 10:48:36 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 1CAE416A41F for ; Fri, 19 Aug 2005 10:48:36 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from efacilitas.de (smtp.efacilitas.de [85.10.196.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADA0E43D55 for ; Fri, 19 Aug 2005 10:48:35 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from eurystheus.local (port-212-202-37-251.dynamic.qsc.de [212.202.37.251]) by efacilitas.de (Postfix) with ESMTP id 0902E4AFA9; Fri, 19 Aug 2005 12:54:37 +0200 (CEST) Received: from [192.168.1.67] (eurystheus.local [192.168.1.67]) by eurystheus.local (Postfix) with ESMTP id 1717F19345F; Fri, 19 Aug 2005 12:48:20 +0200 (CEST) Message-ID: <4305B8F3.7080904@cs.tu-berlin.de> Date: Fri, 19 Aug 2005 12:48:19 +0200 From: =?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050517 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vasim Valejev References: <00d601c5a88e$1cb8c260$2107a8c0@vasimwork> In-Reply-To: <00d601c5a88e$1cb8c260$2107a8c0@vasimwork> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-amd64@freebsd.org Subject: Re: Slow PCI-X controller perfomance (adaptec 2130SLP) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2005 10:48:36 -0000 Vasim Valejev wrote: > I've tried to set up FreeBSD-current on Dual opteron box with Adaptec 2130SLP > PCI-X RAID controller (256MB memory). My tests did show that maximum transfer > rate from controller to OS was about 132MB/s. That is very strange since PCI-X > maximum speed should be about 1GB/s. Why the controller was so slow? [...] 132 MB/s is a very good transfer rate. Keep in mind that 1 GB/s is the theoretical limit of the PCI-X bus which means that single devices do not necessarily accomplish this transfer rate. As far as I can remember the maximum read transfer rate of a RAID 5 is n - 1, i.e. if one drive has a maximum transfer rate of 80 MB/s then three of them in a RAID 5 array can't have more than 160 MB/s. Björn From owner-freebsd-amd64@FreeBSD.ORG Fri Aug 19 10:50:43 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 9EA9616A41F for ; Fri, 19 Aug 2005 10:50:43 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from efacilitas.de (smtp.efacilitas.de [85.10.196.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id 076D043D49 for ; Fri, 19 Aug 2005 10:50:43 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from eurystheus.local (port-212-202-37-251.dynamic.qsc.de [212.202.37.251]) by efacilitas.de (Postfix) with ESMTP id A9C274AFC9; Fri, 19 Aug 2005 12:56:45 +0200 (CEST) Received: from [192.168.1.67] (eurystheus.local [192.168.1.67]) by eurystheus.local (Postfix) with ESMTP id 11A9C19345F; Fri, 19 Aug 2005 12:50:28 +0200 (CEST) Message-ID: <4305B974.5050706@cs.tu-berlin.de> Date: Fri, 19 Aug 2005 12:50:28 +0200 From: =?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050517 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vasim Valejev References: <00d601c5a88e$1cb8c260$2107a8c0@vasimwork> In-Reply-To: <00d601c5a88e$1cb8c260$2107a8c0@vasimwork> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-amd64@freebsd.org Subject: Re: Slow PCI-X controller perfomance (adaptec 2130SLP) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2005 10:50:43 -0000 Vasim Valejev wrote: > Six Maxtor Atlas 15K2 36GB drives (8E036J0) on the SCSI channel (but only four > was used for /dev/aacd1, RAID5 with 64K stripe) Oh, I just saw that you talk about six drives. I didn't read careful enough. Please ignore my last mail. I have no experience with large RAID 5 arrays. Björn From owner-freebsd-amd64@FreeBSD.ORG Fri Aug 19 11:02:25 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 0593A16A421 for ; Fri, 19 Aug 2005 11:02:25 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (www1.multiplay.co.uk [212.42.16.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6675C43D45 for ; Fri, 19 Aug 2005 11:02:24 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from stevenp4 ([193.123.241.40]) by multiplay.co.uk (multiplay.co.uk [212.42.16.7]) (MDaemon.PRO.v8.1.0.R) with ESMTP id md50001808575.msg for ; Fri, 19 Aug 2005 11:55:16 +0100 Message-ID: <0b0a01c5a4ad$63e42240$7f06000a@int.mediasurface.com> From: "Steven Hartland" To: "Vasim Valejev" , References: <00d601c5a88e$1cb8c260$2107a8c0@vasimwork> Date: Fri, 19 Aug 2005 12:01:45 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="koi8-r"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-Spam-Processed: multiplay.co.uk, Fri, 19 Aug 2005 11:55:16 +0100 (not processed: message from valid local sender) X-MDRemoteIP: 193.123.241.40 X-Return-Path: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-amd64@freebsd.org X-MDAV-Processed: multiplay.co.uk, Fri, 19 Aug 2005 11:55:19 +0100 Cc: Subject: Re: Slow PCI-X controller perfomance (adaptec 2130SLP) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2005 11:02:25 -0000 Sounds harsh but its Adaptec I wouldn't expect good performance they have gone way down in my estimates recently with bad support bad drivers, in general poor products. There was a thread about SATA Highpoint RAID 5 controllers a few months back however which may well have some useful things in you may want to try to increase performance. >From memory key things where: * vfs.read_max * RAID strip size * kernel variable tweak ( cant remember the exact details ) Steve / K ----- Original Message ----- From: "Vasim Valejev" To: Sent: 24 August 2005 10:27 Subject: Slow PCI-X controller perfomance (adaptec 2130SLP) > Hi ! > > I've tried to set up FreeBSD-current on Dual opteron box with Adaptec 2130SLP > PCI-X RAID controller (256MB memory). My tests did show that maximum transfer > rate from controller to OS was about 132MB/s. That is very strange since PCI-X > maximum speed should be about 1GB/s. Why the controller was so slow? Because > poor driver or my method of the test? > > To test transfer rate, i just did run command "dd if=/dev/aacd1 of=/dev/null > bs=8k count=4k" many times (may be i'm wrong but the controller shall cache this > request in its memory). Change of hw.aac.iosize_max to 98k did a very little > effect. > > My system config: > > Tyan K8SD Pro (S2882-D) motherboard (onboard SATA controller was turned off) > 2xOpteron 244 > 2GB memory (2x512MB RAM stick for each CPU) > Adaptec 2130SLP RAID controller with 256MB memory and backup battery (tried > every PCI-X slot on the MB with same results) > Six Maxtor Atlas 15K2 36GB drives (8E036J0) on the SCSI channel (but only four > was used for /dev/aacd1, RAID5 with 64K stripe) > > FreeBSD7.0-CURRENT/amd64 (Tested with 5.4-RELEASE/amd64 and 6.0-BETA2/386 but no > difference). > > Vasim V. > > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > > ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-amd64@FreeBSD.ORG Fri Aug 19 14:09:33 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 1190116A41F for ; Fri, 19 Aug 2005 14:09:33 +0000 (GMT) (envelope-from simon.dick@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 817C343D46 for ; Fri, 19 Aug 2005 14:09:32 +0000 (GMT) (envelope-from simon.dick@gmail.com) Received: by nproxy.gmail.com with SMTP id c2so112542nfe for ; Fri, 19 Aug 2005 07:09:30 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=AwTofiH+8212e33iWJoMaAP55Vpv+rOPheDE8NPhKX+TZw32wePNDFG2s9yAYzqnmjhCRCp1sQpUKhdXGLLQhjT99JMMLnbfBQ4qjycC2LYTNNbnBcDKno1hXX5IIylu4/00RTY2vx6qoq1MaYQzZHyVaalJZ7Nwpgh+NJ80oco= Received: by 10.48.43.14 with SMTP id q14mr67106nfq; Fri, 19 Aug 2005 07:09:30 -0700 (PDT) Received: by 10.48.43.5 with HTTP; Fri, 19 Aug 2005 07:09:30 -0700 (PDT) Message-ID: <2355215605081907095a2dd533@mail.gmail.com> Date: Fri, 19 Aug 2005 15:09:30 +0100 From: Simon Dick To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: amd64 Sempron compatibility X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2005 14:09:33 -0000 Having just bought one of the new 64 bit capable Semprons (2800+), I just thought it was worth asking if anyone's testing freebsd on it yet? I'd assume it'd work even if the cpu isn't recognised, but I have no idea yet! Thanks! --=20 Simon Dick From owner-freebsd-amd64@FreeBSD.ORG Fri Aug 19 14:12:30 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 D97E016A41F for ; Fri, 19 Aug 2005 14:12:30 +0000 (GMT) (envelope-from gabor.kovesdan@t-hosting.hu) Received: from server.t-hosting.hu (server.t-hosting.hu [217.20.133.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E41043D45 for ; Fri, 19 Aug 2005 14:12:30 +0000 (GMT) (envelope-from gabor.kovesdan@t-hosting.hu) Received: from localhost (localhost [127.0.0.1]) by server.t-hosting.hu (Postfix) with ESMTP id BE2269974BB; Fri, 19 Aug 2005 16:12:28 +0200 (CEST) Received: from server.t-hosting.hu ([127.0.0.1]) by localhost (server.t-hosting.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 51164-01-2; Fri, 19 Aug 2005 16:12:25 +0200 (CEST) Received: from [80.98.156.20] (catv-50629c14.catv.broadband.hu [80.98.156.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by server.t-hosting.hu (Postfix) with ESMTP id 524C3997A70; Fri, 19 Aug 2005 16:12:22 +0200 (CEST) Message-ID: <4305E8C3.1090004@t-hosting.hu> Date: Fri, 19 Aug 2005 16:12:19 +0200 From: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Simon Dick References: <2355215605081907095a2dd533@mail.gmail.com> In-Reply-To: <2355215605081907095a2dd533@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at t-hosting.hu Cc: freebsd-amd64@freebsd.org Subject: Re: amd64 Sempron compatibility X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2005 14:12:31 -0000 Simon Dick wrote: >Having just bought one of the new 64 bit capable Semprons (2800+), I >just thought it was worth asking if anyone's testing freebsd on it >yet? I'd assume it'd work even if the cpu isn't recognised, but I have >no idea yet! > >Thanks! > > > Afaik, Sempron isn't 64 bit capable or am I wrong? Sempron is a low-end processor. It is the same category that Duron used to be. You can install the i386 version on that machine. It must do fine. Cheers, Gabor Kovesdan From owner-freebsd-amd64@FreeBSD.ORG Fri Aug 19 14:31:28 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 BAA7116A42D for ; Fri, 19 Aug 2005 14:31:28 +0000 (GMT) (envelope-from dfeustel@verizon.net) Received: from vms042pub.verizon.net (vms042pub.verizon.net [206.46.252.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7932843D46 for ; Fri, 19 Aug 2005 14:31:28 +0000 (GMT) (envelope-from dfeustel@verizon.net) Received: from [71.97.178.169] by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2 HotFix 0.04 (built Dec 24 2004)) with ESMTPA id <0ILH009KS4BCCWV5@vms042.mailsrvcs.net> for freebsd-amd64@freebsd.org; Fri, 19 Aug 2005 09:30:49 -0500 (CDT) Date: Fri, 19 Aug 2005 09:30:47 -0500 From: Dave Feustel In-reply-to: <4305E8C3.1090004@t-hosting.hu> To: freebsd-amd64@freebsd.org Message-id: <200508190930.47785.dfeustel@verizon.net> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable Content-disposition: inline References: <2355215605081907095a2dd533@mail.gmail.com> <4305E8C3.1090004@t-hosting.hu> User-Agent: KMail/1.7.2 Cc: =?iso-8859-1?q?K=F6vesd=E1n_G=E1bor?= Subject: Re: amd64 Sempron compatibility X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfeustel@mindspring.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Aug 2005 14:31:28 -0000 On Friday 19 August 2005 09:12, K=F6vesd=E1n G=E1bor wrote: > Afaik, Sempron isn't 64 bit capable New semprons are 64-bit capable and support SSE-3. =2D-=20 Tired of having to defend against Malware? (You know: trojans, viruses, spyware, worms and popups)=20 Then Switch to OpenBSD with a KDE desktop!!! From owner-freebsd-amd64@FreeBSD.ORG Fri Aug 19 14:38:56 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 AA85016A420 for ; Fri, 19 Aug 2005 14:38:56 +0000 (GMT) (envelope-from ddumont@gmail.com) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id B04BB43D45 for ; Fri, 19 Aug 2005 14:38:54 +0000 (GMT) (envelope-from ddumont@gmail.com) Received: by rproxy.gmail.com with SMTP id i8so511247rne for ; Fri, 19 Aug 2005 07:38:54 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=r563s7U2NmhlXbwx9c1WeqaS8lAsIxUvCf70SJmQPfqu+NYbzkiToGuX2xhKk6SuJ4XxQP5n7Rdymhjc2k1FajaXOhqkcuc3AYUs9jJf/PbEwBcme3AHaOcFXI6iHdRkOWRpR4n8DN39nUoF+aFOSW7SRAvhdst24OyNHm8dsI4= Received: by 10.39.2.68 with SMTP id e68mr156614rni; Fri, 19 Aug 2005 07:38:54 -0700 (PDT) Received: by 10.38.101.26 with HTTP; Fri, 19 Aug 2005 07:38:54 -0700 (PDT) Message-ID: Date: Fri, 19 Aug 2005 10:38:54 -0400 From: Dan Dumont To: freebsd-amd64@freebsd.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <2355215605081907095a2dd533@mail.gmail.com> <4305E8C3.1090004@t-hosting.hu> Subject: Re: amd64 Sempron compatibility X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2005 14:38:56 -0000 It depends on what model Sempron. http://techreport.com/reviews/2004q3/sempron/index.x?pg=3D1 It looks to me like the 2800 is a 32 bit proc. If your chip is Socket A, then it's 32 bit. On 8/19/05, K=F6vesd=E1n G=E1bor wrote: > Simon Dick wrote: > > >Having just bought one of the new 64 bit capable Semprons (2800+), I > >just thought it was worth asking if anyone's testing freebsd on it > >yet? I'd assume it'd work even if the cpu isn't recognised, but I have > >no idea yet! > > > >Thanks! > > > > > > > Afaik, Sempron isn't 64 bit capable or am I wrong? Sempron is a low-end > processor. It is the > same category that Duron used to be. > You can install the i386 version on that machine. It must do fine. > > Cheers, > > Gabor Kovesdan > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > -- Dan Dumont - ddumont@gmail.com 50 gmail invites up for grabs. --=20 Dan Dumont - ddumont@gmail.com 50 gmail invites up for grabs. From owner-freebsd-amd64@FreeBSD.ORG Fri Aug 19 15:01:17 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 ADC6616A41F for ; Fri, 19 Aug 2005 15:01:17 +0000 (GMT) (envelope-from simon.dick@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19DAC43D45 for ; Fri, 19 Aug 2005 15:01:16 +0000 (GMT) (envelope-from simon.dick@gmail.com) Received: by nproxy.gmail.com with SMTP id c2so114907nfe for ; Fri, 19 Aug 2005 08:01:15 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=fHdPwEg1ofD0xKcGAK4Eo/t1Cuew/GhMflTvl4c1+R8nVIF/0Z4OrQsANxwgfUCN/l2yH761eAjnae+6U8X7VlpBkT4S81u6zb+KicTtOdUlnS6iQQsuVyPfgi7LLud5zmtRgvPQ5kCFu9fbAw0DPxmTFXL503384j070+FZfqo= Received: by 10.48.43.20 with SMTP id q20mr80449nfq; Fri, 19 Aug 2005 08:01:15 -0700 (PDT) Received: by 10.48.43.5 with HTTP; Fri, 19 Aug 2005 08:01:15 -0700 (PDT) Message-ID: <2355215605081908017bd3070e@mail.gmail.com> Date: Fri, 19 Aug 2005 16:01:15 +0100 From: Simon Dick To: Dan Dumont In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <2355215605081907095a2dd533@mail.gmail.com> <4305E8C3.1090004@t-hosting.hu> Cc: freebsd-amd64@freebsd.org Subject: Re: amd64 Sempron compatibility X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2005 15:01:17 -0000 On 19/08/05, Dan Dumont wrote: > It depends on what model Sempron. >=20 > http://techreport.com/reviews/2004q3/sempron/index.x?pg=3D1 >=20 > It looks to me like the 2800 is a 32 bit proc. If your chip is Socket > A, then it's 32 bit. There's a socket a 2800+, a s754 32 bit 2800+ and a 64 bit 2800+, nice and simple ;) http://www.theregister.co.uk/2005/07/07/amd_64bit_sempron/ lists which model semprons have 64 bit versions, basically the 2600+, 2800+, 3000+, 3100+ and 3300+. So expect lots more people asking stuff like this ones they start getting them with or without realising! BTW, the 64 bit versions have an AMD64 sticker on the retail box while the 32 bit versions don't, or that was the case of my 2600+ 32 bit ver and 2800+ 64 bit cpu. --=20 Simon Dick From owner-freebsd-amd64@FreeBSD.ORG Fri Aug 19 15:06:51 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 E203B16A41F for ; Fri, 19 Aug 2005 15:06:50 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E1B343D48 for ; Fri, 19 Aug 2005 15:06:49 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j7JFHMw8074258; Fri, 19 Aug 2005 09:17:23 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4305F56C.8090405@samsco.org> Date: Fri, 19 Aug 2005 09:06:20 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vasim Valejev References: <00d601c5a88e$1cb8c260$2107a8c0@vasimwork> In-Reply-To: <00d601c5a88e$1cb8c260$2107a8c0@vasimwork> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: freebsd-amd64@freebsd.org Subject: Re: Slow PCI-X controller perfomance (adaptec 2130SLP) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2005 15:06:51 -0000 Vasim Valejev wrote: > Hi ! > > I've tried to set up FreeBSD-current on Dual opteron box with Adaptec 2130SLP > PCI-X RAID controller (256MB memory). My tests did show that maximum transfer > rate from controller to OS was about 132MB/s. That is very strange since PCI-X > maximum speed should be about 1GB/s. Why the controller was so slow? Because > poor driver or my method of the test? > > To test transfer rate, i just did run command "dd if=/dev/aacd1 of=/dev/null > bs=8k count=4k" many times (may be i'm wrong but the controller shall cache this > request in its memory). Change of hw.aac.iosize_max to 98k did a very little > effect. > > My system config: > > Tyan K8SD Pro (S2882-D) motherboard (onboard SATA controller was turned off) > 2xOpteron 244 > 2GB memory (2x512MB RAM stick for each CPU) > Adaptec 2130SLP RAID controller with 256MB memory and backup battery (tried > every PCI-X slot on the MB with same results) > Six Maxtor Atlas 15K2 36GB drives (8E036J0) on the SCSI channel (but only four > was used for /dev/aacd1, RAID5 with 64K stripe) > > FreeBSD7.0-CURRENT/amd64 (Tested with 5.4-RELEASE/amd64 and 6.0-BETA2/386 but no > difference). > > Vasim V. > Whenever people complain about slow performance with AAC products and try to point the finger at the driver, I ask them do repeat their benchmark under linux and see how it compares. Then they realize just how good they have it with FreeBSD. I've worked very hard over the years to make the FreeBSD driver be the fastest driver available for AAC cards. Your particular test is testing the following things: 1) disk transfer speed 2) controller firmware efficiency 3) cache memory bandwidth on the controller 4) stripe alignment of the requests 5) PCI-X bandwidth Your disk transfer speed is going to be about 70MB/s per disk. Given that you are doing RAID-5 on 4 disks, you'll ideally get 3x70MB/s = 210MB/s. The reason that you multiply by 3 and not 4 is that for a given stripe, you only have 3 disks that contain data, with the 4th disk containing parity information. Also note that you are dealing with Ultra320. Adding more disks than what you have will start to saturate the bandwidth of the bus (which is probabl between 260-300MB/s depending on a lot of factors) The controller firmware efficiency part is hard to quantify. Is the firmware doing a good job of servicing requets from the OS in a timely fashion and also servicing completions from the disks? There have been significant observable problems with this in the past. Also, maybe the disk is reading and recomputing parity with each operation. This is a feature of high-reliability disk systems and is not typically a feature of Adaptec controllers, but it's a possibility. Try running your test with RAID0 instead. Cache memory bandwidth is very important. Usually when you create an array on an Adaptec card, it defaults to having the array read cache turned on. I cannot stress enough how incredibly useless this feature is. What it means is that data coming off the drive must travel across the controller's internal bus to the cache, then travel back across the same bus to the PCI bridge to the host. Since the data has to make two trips across the same medium, latency and contention is introduced. Read caches on raid controllers are completely worthless in all but the most specific tests. Turn it off and make sure that the write cache is turned on (which will significantly help write performance, just make sure that you have a battery attached to the card when doing RAID-5 or else you'll risk data corruption). Having the read cache on is likely a very significant factor in your test. Stripe alignment matters because most RAID firmware is optimized to work in terms of reading and writing full stripes of data across all disks at the same time. If a request is sent down that isn't aligned with the stripe boundary, then two stripe reads/writes will have to be issued, impacting performance. Since you are reading from the raw aacd0 device, this probably isn't an issue, but you might try playing with different offsets to 'dd' to see if it changes anything. Scott From owner-freebsd-amd64@FreeBSD.ORG Fri Aug 19 19:33:32 2005 Return-Path: X-Original-To: amd64@freebsd.org 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 1AA7716A41F; Fri, 19 Aug 2005 19:33:32 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1DBE43D46; Fri, 19 Aug 2005 19:33:31 +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.3/8.13.3) with ESMTP id j7JJXTf7048729; Fri, 19 Aug 2005 15:33:29 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id j7JJXUNa080475; Fri, 19 Aug 2005 15:33:30 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 553E87304D; Fri, 19 Aug 2005 15:33:30 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050819193330.553E87304D@freebsd-current.sentex.ca> Date: Fri, 19 Aug 2005 15:33:30 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner5 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Aug 2005 19:33:32 -0000 TB --- 2005-08-19 17:50:54 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-08-19 17:50:54 - starting HEAD tinderbox run for amd64/amd64 TB --- 2005-08-19 17:50:54 - cleaning the object tree TB --- 2005-08-19 17:51:27 - checking out the source tree TB --- 2005-08-19 17:51:27 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2005-08-19 17:51:27 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-08-19 17:57:42 - building world (CFLAGS=-O2 -pipe) TB --- 2005-08-19 17:57:42 - cd /src TB --- 2005-08-19 17:57:42 - /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 >>> stage 5.1: building 32 bit shim libraries TB --- 2005-08-19 19:27:52 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-08-19 19:27:52 - cd /src TB --- 2005-08-19 19:27:52 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Aug 19 19:27:52 UTC 2005 >>> 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 [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/dev/acpica -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /src/sys/kern/kern_exit.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/dev/acpica -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /src/sys/kern/kern_fork.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/dev/acpica -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /src/sys/kern/kern_idle.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/dev/acpica -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /src/sys/kern/kern_intr.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/dev/acpica -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /src/sys/kern/kern_jail.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/dev/acpica -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /src/sys/kern/kern_kse.c /src/sys/kern/kern_kse.c: In function `thread_continued': /src/sys/kern/kern_kse.c:1444: error: syntax error before string constant *** Error code 1 Stop in /obj/amd64/src/sys/GENERIC. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-08-19 19:33:30 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-08-19 19:33:30 - ERROR: failed to build generic kernel TB --- 2005-08-19 19:33:30 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Fri Aug 19 22:17:21 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 21E6E16A41F for ; Fri, 19 Aug 2005 22:17:21 +0000 (GMT) (envelope-from miha@ghuug.org) Received: from sonic.ux6.net (sonic.ux6.net [64.62.252.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80C6D43D45 for ; Fri, 19 Aug 2005 22:17:20 +0000 (GMT) (envelope-from miha@ghuug.org) Received: from [64.62.253.84] (helo=m) by sonic.ux6.net with esmtpa (Exim 4.52 (FreeBSD)) id 1E6FAs-000Ktv-7z for freebsd-amd64@freebsd.org; Fri, 19 Aug 2005 15:17:20 -0700 From: "Mikhail P." To: freebsd-amd64@freebsd.org Date: Fri, 19 Aug 2005 22:17:06 +0000 User-Agent: KMail/1.8.1 References: <20050815125657.A92343@cons.org> <20050816111428.A24284@cons.org> <43020F08.6070108@samsco.org> In-Reply-To: <43020F08.6070108@samsco.org> Organization: Ghana Unix Users Group MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200508192217.06403.miha@ghuug.org> X-Spam-Score: -5.9 (-----) X-Spam-Report: Spam detection software, running on the system "sonic.ux6.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: On Tuesday 16 August 2005 16:06, Scott Long wrote: > Intel Xeon systems typically do the remapping trick, so when you boot > FreeBSD i386+PAE or amd64 on them, they might show 4.5GB of RAM when > there reall is only 4GB (this is a limitation of how we compute RAM and > is purely cosmetic, but should be fixed). Many AMD Opteron systems do > not do the remapping and result in you loosing effective RAM. The > difference between Intel and AMD is because AMD puts the memory > controller into the CPU instead of in the PCI host bridge, so it's much > harder to have the two work together to do the remapping. I believe > that there are some Opteron systems that can do this, though. > > A junior doc writer task would be for someone to collect all of the > email responses that I give on this topic (I seem to get at least one > query a month) and turn it into an FAQ for the FreeBSD doc set. > > Scott [...] Content analysis details: (-5.9 points, 6.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -3.3 ALL_TRUSTED Did not pass through any untrusted hosts -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Subject: Re: 4 GB RAM showing up as 3, BIOS memory hole and all that X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: miha@ghuug.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Aug 2005 22:17:21 -0000 On Tuesday 16 August 2005 16:06, Scott Long wrote: > Intel Xeon systems typically do the remapping trick, so when you boot > FreeBSD i386+PAE or amd64 on them, they might show 4.5GB of RAM when > there reall is only 4GB (this is a limitation of how we compute RAM and > is purely cosmetic, but should be fixed). Many AMD Opteron systems do > not do the remapping and result in you loosing effective RAM. The > difference between Intel and AMD is because AMD puts the memory > controller into the CPU instead of in the PCI host bridge, so it's much > harder to have the two work together to do the remapping. I believe > that there are some Opteron systems that can do this, though. > > A junior doc writer task would be for someone to collect all of the > email responses that I give on this topic (I seem to get at least one > query a month) and turn it into an FAQ for the FreeBSD doc set. > > Scott Here's a dual opteron system we've got recently. Currently it runs=20 =46reeBSD-4.11 GENERIC kernel (just fresh installed). It has 4GB of actual RAM, and OS sees it: CPU: AMD Opteron(tm) Processor 246 (1992.77-MHz 686-class CPU) =A0 Origin =3D "AuthenticAMD" =A0Id =3D 0xf5a =A0Stepping =3D 10 =A0=20 =46eatures=3D0x78bfbff =A0 AMD Features=3D0xe0500000<,AMIE,,DSP,3DNow!> real memory =A0=3D 4227792896 (4128704K bytes) avail memory =3D 4117520384 (4021016K bytes) I'm not sure what BIOS settings it uses (system is overseas), but it is bui= lt=20 on identical Celestia barebone: http://www.monarchcomputer.com/Merchant2/merchant.mv?Screen=3DPROD&Store_Co= de=3DM&Product_Code=3D100944&Category_Code=3D1U M. From owner-freebsd-amd64@FreeBSD.ORG Sat Aug 20 06:15:56 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org 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 CF3CB16A41F for ; Sat, 20 Aug 2005 06:15:56 +0000 (GMT) (envelope-from simon.dick@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BA3E43D72 for ; Sat, 20 Aug 2005 06:15:50 +0000 (GMT) (envelope-from simon.dick@gmail.com) Received: by nproxy.gmail.com with SMTP id c2so127815nfe for ; Fri, 19 Aug 2005 23:15:49 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Y09E5Oz3+Ax106onH1QLsQ7FDkHWtm8Xz2i//1jVAMOcbc8lpru3jp5efQ0Tr3BSQX/5yj1aHREbJrXanK3wqDvVyrIDje96+wDXUb7szWWuWx7Tz3mjJI6JMEOwwoRSWOJgWDkxHN2cFub1xnbD3hLXhyTt9mCDzfoUgnJrQec= Received: by 10.48.43.14 with SMTP id q14mr78275nfq; Fri, 19 Aug 2005 23:15:49 -0700 (PDT) Received: by 10.48.43.5 with HTTP; Fri, 19 Aug 2005 23:15:49 -0700 (PDT) Message-ID: <23552156050819231564e10d36@mail.gmail.com> Date: Sat, 20 Aug 2005 07:15:49 +0100 From: Simon Dick To: Dan Dumont In-Reply-To: <2355215605081908017bd3070e@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <2355215605081907095a2dd533@mail.gmail.com> <4305E8C3.1090004@t-hosting.hu> <2355215605081908017bd3070e@mail.gmail.com> Cc: freebsd-amd64@freebsd.org Subject: Re: amd64 Sempron compatibility X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2005 06:15:56 -0000 Just a quick note but I had a quick boot of the 6.0-beta2 amd64 cd and it booted fine recognising the speed if not the model, once I get a chance to install properly I can tell you the cpu id if it's not on amds site --=20 Simon Dick