From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 8 03:40:07 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F40B516A4CF for ; Sun, 8 Feb 2004 03:40:06 -0800 (PST) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EA0043D1D for ; Sun, 8 Feb 2004 03:40:06 -0800 (PST) (envelope-from adridg@cs.kun.nl) Received: from odin.cs.kun.nl [131.174.33.33] (helo=localhost) by pandora.cs.kun.nl (8.12.10/3.61) with ESMTP id i18Be2Rv016196 for ; Sun, 8 Feb 2004 12:40:02 +0100 (MET) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Sun, 8 Feb 2004 12:40:02 +0100 User-Agent: KMail/1.6.50 References: <200402050740.i157e4Rv028605@pandora.cs.kun.nl> In-Reply-To: <200402050740.i157e4Rv028605@pandora.cs.kun.nl> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Multipart/Mixed; boundary="Boundary-00=_SAiJAULbfN3M4Z3" Message-Id: <200402081240.02765.adridg@cs.kun.nl> Subject: Redux: KDE 3.2.0 packages X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Feb 2004 11:40:07 -0000 --Boundary-00=_SAiJAULbfN3M4Z3 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 05 February 2004 00:25, Adriaan de Groot wrote: > For the crowd using amd64 boxes as desktop machines, I thought that KDE > 3.2.0 packages might be useful. The set isn't complete yet - after all, it New packages, suitable for -current from after feb. 5th, have been uploaded= to=20 http://www.fruitsalad.org/people/adridg/ (I suppose you could even set=20 PACKAGESITE to that). These are non-debug builds, and include all the=20 dependencies for KDE, right down to XFree86-libraries-4.3.0_6.tgz.=20 =2D --=20 pub 1024D/FEA2A3FE 2002-06-18 Adriaan de Groot The users that I support would double-click on a landmine to see what it di= d. =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAJiASdqzuAf6io/4RAhvqAJ93AUCzMH5xtzb9ZlsZ8ccu6jWnfACfai1l 5eaKB0cp80uUeEucO53kumQ=3D =3Dp5FW =2D----END PGP SIGNATURE----- --Boundary-00=_SAiJAULbfN3M4Z3 Content-Type: text/plain; charset="iso-8859-1"; name="md5s" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="md5s" MD5 (WordNet-1.7.1.tgz) = 2a882bfbd6f299663d760b9da2e179d3 MD5 (XFree86-fontEncodings-4.3.0.tgz) = d710a0dde6997d0f5762202edcc0eda2 MD5 (XFree86-fontScalable-4.3.0.tgz) = 2d052346a49ee7371add023aba462b58 MD5 (XFree86-libraries-4.3.0_6.tgz) = c594644f53b2069bf0ba8d326a43b169 MD5 (Xft-2.1.2_1.tgz) = 7f32b6120b01ff8171d41bd517f7f581 MD5 (aalib-1.4.r5_1.tgz) = fb0248ddfc9c037fe6c72c7e06bfe581 MD5 (arts-1.1.4_2,1.tgz) = 024e0cf0e72bb6ab96e0c1307b83c746 MD5 (aspell-0.50.4.1_1.tgz) = d0355eb2315b3728bc391ea12aca27c2 MD5 (cdparanoia-3.9.8_7.tgz) = 0f151e0f186c6c8efd121aa47034c884 MD5 (cups-base-1.1.20.0.tgz) = d235920c63226090b50fa2a30ec08f72 MD5 (db41-4.1.25_1.tgz) = 8aa8c8e87f971bf4524b541c119d101b MD5 (esound-0.2.32_1.tgz) = 822c68129aa8abede12da7b36f356855 MD5 (expat-1.95.6_1.tgz) = 15b01388d321e3da78e25c2fefcf6d87 MD5 (fam-2.6.9_4.tgz) = 3755460a50fb0df80e8db45074d10e43 MD5 (flac-1.1.0_3.tgz) = 661a21a0cf3cbc1a9f8f7e06a07c75c7 MD5 (fontconfig-2.2.90_4.tgz) = d386b685ef7186724cf2e6a1b80305ec MD5 (freetype2-2.1.5_2.tgz) = 24c5bb4e5b7c45bc16c5c07f6be7ed57 MD5 (gettext-0.13.1.tgz) = beb3f52fbd4a316c0101723487702da1 MD5 (gmake-3.80_2.tgz) = 00e8d53645f4331c0f01a6116671c444 MD5 (gnupg-1.2.4_1.tgz) = 422c9580cf3fbf479f0fda4b95991792 MD5 (imake-4.3.0_2.tgz) = c355da732a1c47a628fa5a1836069d13 MD5 (jasper-1.700.5.tgz) = cf41909f690fafb8cb872c50c9144d7c MD5 (jpeg-6b_1.tgz) = 14b54fe63a3b81b4f7d018db086ccc6e MD5 (kdeaddons-3.2.0.tgz) = 975c26458f34edb4d551439b3da8101c MD5 (kdeadmin-3.2.0.tgz) = 179f6ea6ea8431b010df4713ee28b482 MD5 (kdeartwork-3.2.0.tgz) = 485a1414e06c1bac5cf14cdb4ed84de3 MD5 (kdebase-3.2.0.tgz) = d1776601fc4e89cbb03031d93472bcb7 MD5 (kdeedu-3.2.0.tgz) = 771f97c26568c3075268ccb8d5a40f3d MD5 (kdegames-3.2.0.tgz) = 8190afc25bdcd78b8beb08004d620192 MD5 (kdegraphics-3.2.0.tgz) = 857825132692d0012e35d1de7062931e MD5 (kdelibs-3.2.0.tgz) = 6d7a19aebb5983e85e077a97f0eee255 MD5 (kdemultimedia-3.2.0.tgz) = 93da416365db0f7092110efaf12db975 MD5 (kdenetwork-3.2.0.tgz) = 7f9cb0bc0b2042b00789d7089e0ae63e MD5 (kdepim-3.2.0_1.tgz) = de4a42aae1c03594c389d5221ffe4917 MD5 (kdesdk-3.2.0.tgz) = 36847eadca0ff04a84f7740ebb0fa9f9 MD5 (kdetoys-3.2.0.tgz) = 7367510a4f34620a6ae0f0732788be79 MD5 (kdeutils-3.2.0_1.tgz) = b472607d51b32ef9f0132408cc579be6 MD5 (kdevelop-3.0.0.tgz) = 7cb5b0d70eb7aa2c670993b51fc33554 MD5 (koffice-1.3,1.tgz) = 3c36f57507b61f21f5e8434728acd994 MD5 (lame-3.95.1_1.tgz) = 90c71f0e887f3f05f9d50e780da9e9b5 MD5 (lcms-1.09,1.tgz) = 8309dd2d85d5b48f9334aaf25adc51e3 MD5 (libart_lgpl2-2.3.16.tgz) = 9fb6e4a6f49411f25d3b9ad05e609791 MD5 (libaudiofile-0.2.5.tgz) = fbaab2e6ade1b78ede54050a41db3252 MD5 (libglut-5.0.2.tgz) = 57c0f4923f22bda2750388f5810f5d72 MD5 (libiconv-1.9.1_3.tgz) = c085d4e76ec4f976717a1ddf8e5f30e4 MD5 (libmng-1.0.5_1.tgz) = 220388f9e841d095bcfc95412de9bbff MD5 (libogg-1.1,3.tgz) = da466e29a5765a2ad814c5f03dba9f4b MD5 (libpaper-1.1.13.tgz) = 43528873e88ae7ca714448576a37b30c MD5 (libvorbis-1.0.1,3.tgz) = 76b90c150f7794009115e3cb10daada2 MD5 (libxml2-2.6.5_1.tgz) = f4020501aa59743ba67b5971ba659da3 MD5 (libxslt-1.1.2_3.tgz) = 34b165b77d79deecb5c195141e8e84fe MD5 (open-motif-2.2.2_2.tgz) = 8b941e6b7e87fff0b9aec552bb9db991 MD5 (openldap-client-2.1.26.tgz) = 000dd034180e0205b6ac4c2696910094 MD5 (pcre-4.5.tgz) = 771a23c02faafb0f5c76550e069868cf MD5 (perl-5.6.1_15.tgz) = 4d6b5e79ef96aa6b38a1052662760734 MD5 (pkgconfig-0.15.0_1.tgz) = a76d7d7a87f4c771748a5656350caa51 MD5 (png-1.2.5_3.tgz) = ae136c5a09121e2ed2e6c9041a066c31 MD5 (python-2.3.3.tgz) = ba3caeb445f978a31bdd6eb96406414c MD5 (qmake-3.2.3_1.tgz) = 179dcb986b6d3950f1052c62218b8aec MD5 (qt-3.2.3.tgz) = 9e080be62c910a0e0b83927869d73bf2 MD5 (quanta-3.2.0,2.tgz) = 5a0326928693790ee70d2c5f5cfbf03f MD5 (samba-libsmbclient-3.0.1.tgz) = ad9c1f08f330257d34b242b07a804f20 MD5 (sdl-1.2.5_3,1.tgz) = d473a3ae7bef6faceb1f7200a65d33ed MD5 (taglib-1.0_1.tgz) = ed8c33763e53d1c842189288ec267f16 MD5 (tcl-8.3.5_2.tgz) = 9284416f1c439de76f2a4184ea99325c MD5 (tiff-3.6.1.tgz) = 5ebd29ce53719215e3fa66e7858b1e53 MD5 (tk-8.3.5_2.tgz) = 9eb90ee1bce803425016b89650b82583 --Boundary-00=_SAiJAULbfN3M4Z3-- From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 8 10:46:11 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8654916A4CE; Sun, 8 Feb 2004 10:46:11 -0800 (PST) Received: from bigtex.jrv.org (rrcs-sw-24-73-246-106.biz.rr.com [24.73.246.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A29F43D1D; Sun, 8 Feb 2004 10:46:11 -0800 (PST) (envelope-from james@bigtex.jrv.org) Received: from bigtex.jrv.org (localhost [127.0.0.1]) by bigtex.jrv.org (8.12.1/8.12.1) with ESMTP id i18IkAo8000262 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 8 Feb 2004 12:46:10 -0600 (CST) Received: (from james@localhost) by bigtex.jrv.org (8.12.1/8.12.1/Submit) id i18IkA81000259; Sun, 8 Feb 2004 12:46:10 -0600 (CST) Date: Sun, 8 Feb 2004 12:46:10 -0600 (CST) Message-Id: <200402081846.i18IkA81000259@bigtex.jrv.org> From: James Van Artsdalen To: obrien@freebsd.org In-reply-to: <20040202095652.GA25017@dragon.nuxi.com> (obrien@freebsd.org) References: <20040202095652.GA25017@dragon.nuxi.com> cc: freebsd-amd64@freebsd.org Subject: Re: SiImg 3114 was: (FWD) FreeBSD 5.2.1-RC available X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Feb 2004 18:46:11 -0000 > Date: Mon, 2 Feb 2004 01:56:52 -0800 > From: "David O'Brien" > > Note 5.2.1 also adds the Silicon Image 3114 SATA support needed to > install on a SATA drive in many Opteron systems. Is anyone else having trouble with this? The 3114 is found no problem but the drive is not seen. The culprit may be this code in ata_reset(). It does not recognize any drive unless (err & 0x7f) == ATA_E_ILI is true immediately after BUSY is deasserted, which isn't the case for me (and definitely isn't true for older ATA disks; could this be a typo of some kind?). stat0 = ATA_IDX_INB(ch, ATA_STATUS); if (bootverbose) ata_printf(ch, ATA_MASTER, "stat=0x%02x err=0x%02x lsb=0x%02x msb=0x%02x\n", stat0, err, lsb, msb); if (!(stat0 & ATA_S_BUSY)) { if ((err & 0x7f) == ATA_E_ILI) { if (lsb == ATAPI_MAGIC_LSB && msb == ATAPI_MAGIC_MSB) { ch->devices |= ATA_ATAPI_MASTER; } else if (stat0 & ATA_S_READY) { ch->devices |= ATA_ATA_MASTER; } } else if ((stat0 & 0x4f) && err == lsb && err == msb) { stat0 |= ATA_S_BUSY; } From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 8 17:17:21 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A0EA16A4CE; Sun, 8 Feb 2004 17:17:21 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 061ED43D1F; Sun, 8 Feb 2004 17:17:21 -0800 (PST) (envelope-from peter@evilpete.dyndns.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id C712D2A8EB; Sun, 8 Feb 2004 17:17:20 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 9B2B72C1AF; Sun, 8 Feb 2004 17:17:20 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.12.10/8.12.10) with ESMTP id i191H6Vu083761; Sun, 8 Feb 2004 17:17:06 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.12.10/8.12.10/Submit) id i191H6Bm083760; Sun, 8 Feb 2004 17:17:06 -0800 (PST) (envelope-from peter) From: Peter Wemm To: Ruslan Ermilov , Dag-Erling Sm?rgrav Date: Sun, 8 Feb 2004 17:17:06 -0800 User-Agent: KMail/1.5.4 References: <20040206222812.818607303A@freebsd-current.sentex.ca> <20040207111719.GB46350@FreeBSD.org.ua> In-Reply-To: <20040207111719.GB46350@FreeBSD.org.ua> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402081717.06587.peter@wemm.org> cc: amd64@freebsd.org Subject: Re: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2004 01:17:21 -0000 On Saturday 07 February 2004 03:17 am, Ruslan Ermilov wrote: > On Sat, Feb 07, 2004 at 12:08:22PM +0100, Dag-Erling Sm?rgrav wrote: > > Kris Kennaway writes: > > > On Fri, Feb 06, 2004 at 05:28:12PM -0500, Tinderbox wrote: > > >> ===> accf_http > > > > > > AFAIK modules are not yet supported on amd64..the tinderbox > > > shouldn't try building them. > > > > They usually build fine. If the tinderbox isn't supposed to build > > them, GENERIC and NOTES should have 'makeoptions > > MODULES_OVERRIDE=""' > > NO_MODULES is better. Yes, I forgot to add it when the lint stuff went in. It was in GENERIC the whole time. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 8 18:21:15 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDB3316A4CE for ; Sun, 8 Feb 2004 18:21:15 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7FFD43D1F for ; Sun, 8 Feb 2004 18:21:15 -0800 (PST) (envelope-from peter@evilpete.dyndns.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 5759B2A8EC for ; Sun, 8 Feb 2004 18:21:15 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 0A1DB2C1AF for ; Sun, 8 Feb 2004 18:21:15 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.12.10/8.12.10) with ESMTP id i192L1Vu084994; Sun, 8 Feb 2004 18:21:01 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.12.10/8.12.10/Submit) id i192L0TP084993; Sun, 8 Feb 2004 18:21:00 -0800 (PST) (envelope-from peter) From: Peter Wemm To: "" , "Greg J." Date: Sun, 8 Feb 2004 18:21:00 -0800 User-Agent: KMail/1.5.4 References: <1074066811.4004f57b5adb0@webmail.thejemreport.com> <40053D06.5030808@cox.net> <1074121024.4005c940ac817@webmail.thejemreport.com> In-Reply-To: <1074121024.4005c940ac817@webmail.thejemreport.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402081821.00599.peter@wemm.org> cc: freebsd-amd64@freebsd.org Subject: Re: VESA driver in X X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2004 02:21:15 -0000 On Wednesday 14 January 2004 02:57 pm, wrote: > Quoting "Greg J." : > > techsupport@thejemreport.com wrote: > > > Anyone know why there is no VESA driver in XFree86, or when one > > > will be available? That's the only one that I can get working > > > with my Radeon 9800 > > > > (in > > > > > the i386 build). The VGA driver is not usable. > > > > > > -Jem > > > > My 9800Pro works fine on my FreeBSD/amd64 machine with XFree86 > > 4.3.0's vesa driver. I'm not quite sure what you're asking. > > > > Section "Device" > > Identifier "Card0" > > Driver "vesa" > > VendorName "ATI" > > BoardName "Radeon 9800 Pro" > > BusID "PCI:1:0:0" > > EndSection > > I solved it -- the XFree86 package somehow doesn't include some of > the video driver modules. Removing the package and installing from > ports gave me the ability to use the VESA driver. I know this is a bit late, but this was my mistake. I missed a #ifdef in the early porting that caused the int10 interpreter to be left out. At the time you ran into trouble, the package was still old, but the port has been fixed. The next time the packages are built (if not already), they'll get the int10 module. BTW; I think I ran into this because I used a matrox g450, which was a pure MMIO native driver. It didn't even catch the fact that I forgot to enable inb/outb access via /dev/io. mga was probably the only driver that would work at that point. :-) -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 8 18:47:31 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45DF016A4CE for ; Sun, 8 Feb 2004 18:47:31 -0800 (PST) Received: from pillage.dreamhost.com (pillage.dreamhost.com [66.33.213.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D29543D1D for ; Sun, 8 Feb 2004 18:47:31 -0800 (PST) (envelope-from absinthe@pobox.com) Received: from redstone.retrovertigo.com (ool-182dd6f2.dyn.optonline.net [24.45.214.242]) by pillage.dreamhost.com (Postfix) with ESMTP id E82D714968B for ; Sun, 8 Feb 2004 18:47:30 -0800 (PST) From: Dylan Carlson To: freebsd-amd64@freebsd.org Date: Sun, 8 Feb 2004 21:47:29 -0500 User-Agent: KMail/1.6 References: <1074066811.4004f57b5adb0@webmail.thejemreport.com> <1074121024.4005c940ac817@webmail.thejemreport.com> <200402081821.00599.peter@wemm.org> In-Reply-To: <200402081821.00599.peter@wemm.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200402082147.29563.absinthe@pobox.com> Subject: Re: VESA driver in X X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: absinthe@pobox.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2004 02:47:31 -0000 On Sunday 08 February 2004 21:21, Peter Wemm wrote: > > I solved it -- the XFree86 package somehow doesn't include some of > > the video driver modules. Removing the package and installing from > > ports gave me the ability to use the VESA driver. > In regards to ATI Radeon support... it's worth noting that if you build 4.3.99.x (by hand or otherwise) the "radeon" driver will work... which is much better than using the vesa driver. Cheers, Dylan Carlson [absinthe@pobox.com] Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3F3F5A7 Key fingerprint = FF76 7CAF 1B76 0C74 B84F 96C3 DEC7 6EC2 E3F3 F5A7 From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 8 20:40:22 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B240E16A4CE; Sun, 8 Feb 2004 20:40:22 -0800 (PST) Received: from tor-adm1.nbc.attcanada.ca (tor-adm1.business.allstream.net [207.181.89.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 601DF43D1D; Sun, 8 Feb 2004 20:40:22 -0800 (PST) (envelope-from taob@risc.org) Received: from tor-adm1.nbc.attcanada.ca (localhost [127.0.0.1]) i194eLwH027931; Sun, 8 Feb 2004 23:40:21 -0500 (EST) Received: from localhost (ncc0070@localhost)i194eLxB027928; Sun, 8 Feb 2004 23:40:21 -0500 (EST) X-Authentication-Warning: tor-adm1.nbc.attcanada.ca: ncc0070 owned process doing -bs Date: Sun, 8 Feb 2004 23:40:20 -0500 (EST) From: Brian Tao X-Sender: ncc0070@tor-adm1.nbc.attcanada.ca To: James Van Artsdalen In-Reply-To: <200402081846.i18IkA81000259@bigtex.jrv.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org Subject: Re: SiImg 3114 was: (FWD) FreeBSD 5.2.1-RC available X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2004 04:40:22 -0000 On Sun, 8 Feb 2004, James Van Artsdalen wrote: > > Is anyone else having trouble with this? > > The 3114 is found no problem but the drive is not seen. > The culprit may be this code in ata_reset(). I haven't had much time to look into this yet, but the i386 port of 5.2.1-RC2 panics when it attempts to probe the S-ATA devices on my motherboard (Tyan Tiger K8W S2875). I haven't tried the amd64 port yet. -- Brian Tao (BT300, taob@risc.org) "Though this be madness, yet there is method in't" From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 9 00:40:31 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9584B16A4CE for ; Mon, 9 Feb 2004 00:40:31 -0800 (PST) Received: from smtp1.su.se (smtp1.su.se [130.237.162.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3051F43D1F for ; Mon, 9 Feb 2004 00:40:31 -0800 (PST) (envelope-from jj@it.su.se) Received: from localhost (smtp1.su.se [127.0.0.1]) by smtp1.su.se (Postfix) with ESMTP id 8D8BA391F0 for ; Mon, 9 Feb 2004 09:40:29 +0100 (CET) Received: from smtp1.su.se ([127.0.0.1]) by localhost (smtp1.su.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31226-05 for ; Mon, 9 Feb 2004 09:40:29 +0100 (CET) Received: from it.su.se (jj.it.su.se [130.237.95.193]) by smtp1.su.se (Postfix) with ESMTP id 75D403877A for ; Mon, 9 Feb 2004 09:40:29 +0100 (CET) Message-ID: <40274772.9080902@it.su.se> Date: Mon, 09 Feb 2004 09:40:18 +0100 From: Janne Johansson Organization: Stockholms Universitet User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040123 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <4020B672.9080304@it.su.se> <200402041251.50129.adridg@cs.kun.nl> <200402041207.i14C7JGW008982@bigtex.jrv.org> <200402042130.i14LUBwd029592@bigtex.jrv.org> In-Reply-To: <200402042130.i14LUBwd029592@bigtex.jrv.org> X-Enigmail-Version: 0.82.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at su.se Subject: Re: shaky support or my system? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2004 08:40:31 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 |>>>in either fbsd5.2 nor the recent 5.2.1RC. One of the things that makes |>>>it crash for sure is the /usr/ports/benchmarks/ubench program. It does |>> |>>Don't run that, it'll just tell you that the system is only marginally faster |>>than the athlon XP it replaces. |> |>I've reproduced Janne's panic with ubench twice. Both show similar |>outputs from the panic. Panic #3 is proving more elusive: I'm running |>ubench for the fourth time in a row now waiting for crash #3. | | Unfortunately it appears my case was a false alarm. | My Tyan K8W S2885 is not stable unless ECC is turned off in ROM setup. I switched my memory chips around and found that one seems to cause more instability, and removing it made me be able to run that stupid app "ubench". ;-) Now I can build several ports in a row without hanging, but I do still get the odd freeze sometimes. Since memtest86 wont work (on my) A64, is there something else I can do to stress my memory chips? Which bench/whatever for FBSD would you recommend to me so I know when/if I have a stable setup? I got more or less all available kernel errors, I started listing them on a postit, from a "GPF" to "freeing membuf twice" but when I had some 10 or so different error messages, I realised it couldn't be the code or so and went to my hardware. Thanks for you help though. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAJ0dyKWyDo3z7ubcRAklyAJ9TQUkUzuQmcZeqxVVVvq+xLtdEfACff5mm Qy1nshfEFqwfojPYvRTyS4g= =scS5 -----END PGP SIGNATURE----- From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 9 02:03:18 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4109416A4CE for ; Mon, 9 Feb 2004 02:03:18 -0800 (PST) Received: from curacao.n2it.nl (62-177-157-186.bbeyond.nl [62.177.157.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BDC643D1D for ; Mon, 9 Feb 2004 02:03:18 -0800 (PST) (envelope-from billsf@curacao.n2it.nl) Received: by curacao.n2it.nl (Postfix, from userid 1000) id 8AAA42058; Mon, 9 Feb 2004 11:03:16 +0100 (CET) Date: Mon, 9 Feb 2004 11:03:16 +0100 From: Bill Squire To: freebsd-amd64@freebsd.org Message-ID: <20040209100316.GA49862@curacao.n2it.nl> References: <4020B672.9080304@it.su.se> <200402041251.50129.adridg@cs.kun.nl> <200402041207.i14C7JGW008982@bigtex.jrv.org> <200402042130.i14LUBwd029592@bigtex.jrv.org> <40274772.9080902@it.su.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40274772.9080902@it.su.se> User-Agent: Mutt/1.4.1i Subject: Re: shaky support or my system? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2004 10:03:18 -0000 On Mon, Feb 09, 2004 at 09:40:18AM +0100, Janne Johansson wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > |>>>in either fbsd5.2 nor the recent 5.2.1RC. One of the things that makes > |>>>it crash for sure is the /usr/ports/benchmarks/ubench program. It does > |>> > |>>Don't run that, it'll just tell you that the system is only > marginally faster > |>>than the athlon XP it replaces. > |> > |>I've reproduced Janne's panic with ubench twice. Both show similar > |>outputs from the panic. Panic #3 is proving more elusive: I'm running > |>ubench for the fourth time in a row now waiting for crash #3. > | > | Unfortunately it appears my case was a false alarm. > | My Tyan K8W S2885 is not stable unless ECC is turned off in ROM setup. > > I switched my memory chips around and found that one seems to cause more > instability, and removing it made me be able to run that stupid app > "ubench". ;-) > > Now I can build several ports in a row without hanging, but I do still > get the odd freeze sometimes. Since memtest86 wont work (on my) A64, is > there something else I can do to stress my memory chips? Which > bench/whatever for FBSD would you recommend to me so I know when/if I > have a stable setup? > > I got more or less all available kernel errors, I started listing them > on a postit, from a "GPF" to "freeing membuf twice" but when I had some > 10 or so different error messages, I realised it couldn't be the code or > so and went to my hardware. Thanks for you help though. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.4 (FreeBSD) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFAJ0dyKWyDo3z7ubcRAklyAJ9TQUkUzuQmcZeqxVVVvq+xLtdEfACff5mm > Qy1nshfEFqwfojPYvRTyS4g= > =scS5 > -----END PGP SIGNATURE----- Run 'memtest' which is a small standalone program to test your memory in patterns you choose. I used it from a Gentoo install CD but it does fit on a floppy if anyone uses the things anymore. (Maybe the 64bit version is different, but i don't why it would be.) If you can produce any errors, either replace the offending module or reduce the memory clock speed slightly. Adjust the voltage to the memory slightly, up or down by about a tenth of a volt each run and see if you can produce a repeatable no-error condition. Experiment with reducing the memory clock speed and increasing the processor clock speed. This can be tweaked to achieve complete stability. You will probably find the optimum operating points are __not__ the defaults. The amd64 is completely stable and should not crash randomly. Keep in mind that each run can take several hours so start with the default test first which takes a reasonable time to run and make it more complex if you cannot get errors with the default settings. Ofcourse, make sure your hardware is solid and the voltages are stable. If you are on the same power with fridges, vacuum cleaners, wash machines, etc. try cleaner mains power! Strong RF energy can crash a computer. A friend put his GSM mobile phone on my keyboard, it happened to ring and the machine crashed. This is a well known problem. Good luck, Bill From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 9 10:20:53 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38A9016A4CE for ; Mon, 9 Feb 2004 10:20:53 -0800 (PST) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id B945143D31 for ; Mon, 9 Feb 2004 10:20:52 -0800 (PST) (envelope-from adridg@cs.kun.nl) Received: from odin.cs.kun.nl [131.174.33.33] (helo=localhost) by pandora.cs.kun.nl (8.12.10/3.61) with ESMTP id i19IKpiF004700 for ; Mon, 9 Feb 2004 19:20:51 +0100 (MET) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Mon, 9 Feb 2004 19:20:51 +0100 User-Agent: KMail/1.6.50 MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-Id: <200402091920.51316.adridg@cs.kun.nl> Subject: ogg123 crashing again X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2004 18:20:53 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Remember way back when, when the stack wasn't 16-aligned and ogg123, which= =20 does neat-o threading stuff, didn't work? And how Peter fixed it? Well, wit= h=20 =2D -CURRENT from =46reeBSD beans.ebn.kun.nl 5.2-CURRENT FreeBSD 5.2-CURRENT #19: Thu Feb 5= =20 23:16:29 CET 2004 =20 root@beans.ebn.kun.nl:/usr/obj/mnt/sys/CURRENT/src/sys/BEANS amd64 I'm getting crashes again. My libmap.conf maps c_r to pthread right now - a= nd=20 ogg123 crashes occasionally. If I map to kse, then ogg123 hangs immediately= ,=20 doesn't eat CPU though, and it remains kill -9'able. I've cleaned and rebui= lt=20 (the old version was built in december or so, before many changes), and tha= t=20 has changed the pattern of crashes a little, but it still crashes. Once I can produce a reliable bt I'll reply to myself. =2D --=20 pub 1024D/FEA2A3FE 2002-06-18 Adriaan de Groot The users that I support would double-click on a landmine to see what it di= d. =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAJ8+DdqzuAf6io/4RAutsAKChE2vAxhRUkMk4HOaN2fB2dQL70ACfSa21 HtWQE7ibKOiptjRph4aj4sU=3D =3DJ8vU =2D----END PGP SIGNATURE----- From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 9 11:01:34 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5002016A4E0 for ; Mon, 9 Feb 2004 11:01:34 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DA3A43D1D for ; Mon, 9 Feb 2004 11:01:34 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.10/8.12.10) with ESMTP id i19J1Ybv083060 for ; Mon, 9 Feb 2004 11:01:34 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i19J1XUH083052 for freebsd-amd64@freebsd.org; Mon, 9 Feb 2004 11:01:33 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 9 Feb 2004 11:01:33 -0800 (PST) Message-Id: <200402091901.i19J1XUH083052@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2004 19:01:34 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59713 amd64 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 CCEEF16A4CE for ; Tue, 10 Feb 2004 10:29:28 -0800 (PST) Received: from ms3.surfglobal.net (ms3.surfglobal.net [64.30.60.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id A762C43D39 for ; Tue, 10 Feb 2004 10:29:28 -0800 (PST) (envelope-from mike@surfglobal.net) Received: from ms3.surfglobal.net (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 366CC2A2A7 for ; Tue, 10 Feb 2004 13:29:31 -0500 (EST) Received: from VAL3 (unknown [64.30.60.20]) by ms3.surfglobal.net (Postfix) with SMTP id F3DFA2A286 for ; Tue, 10 Feb 2004 13:29:30 -0500 (EST) Message-ID: <000801c3f003$ca7e9f90$4502a8c0@VAL3> From: "Mike Thompson" To: Date: Tue, 10 Feb 2004 13:29:16 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: cvsup X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2004 18:29:29 -0000 How to I get the cvsup to work on amd64. I am currently running 5.2.1. Thanks Mike From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 10 10:36:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8A8516A4E6 for ; Tue, 10 Feb 2004 10:36:56 -0800 (PST) Received: from 21322530218.direct.eti.at (21322530218.direct.eti.at [213.225.30.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id E181B43D1F for ; Tue, 10 Feb 2004 10:36:55 -0800 (PST) (envelope-from tilman@arved.de) Received: from huckfinn-wi0.arved.de (localhost [127.0.0.1]) i1AIaoH6062567; Tue, 10 Feb 2004 19:36:51 +0100 (CET) (envelope-from tilman@arved.de) Received: (from tilman@localhost) by huckfinn-wi0.arved.de (8.12.11/8.12.6/Submit) id i1AIaoTw062566; Tue, 10 Feb 2004 19:36:50 +0100 (CET) X-Authentication-Warning: huckfinn-wi0.arved.de: tilman set sender to tilman@arved.de using -f Date: Tue, 10 Feb 2004 19:36:49 +0100 From: Tilman Linneweh To: Mike Thompson Message-ID: <20040210183649.GF86779@huckfinn.arved.de> References: <000801c3f003$ca7e9f90$4502a8c0@VAL3> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8w3uRX/HFJGApMzv" Content-Disposition: inline In-Reply-To: <000801c3f003$ca7e9f90$4502a8c0@VAL3> User-Agent: Mutt/1.4.1i cc: freebsd-amd64@freebsd.org Subject: Re: cvsup X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2004 18:36:56 -0000 --8w3uRX/HFJGApMzv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline * Mike Thompson [Tue, Feb 10, 2004 at 01:29:16PM -0500]: > How to I get the cvsup to work on amd64. I am currently running 5.2.1. * pkg_add http://people.freebsd.org/~peter/cvsup-without-gui-16.1h.tbz * Disable compression in the supfile Time for a FAQ? regards tilman --8w3uRX/HFJGApMzv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAKSTAfCLDn4B6xToRApsCAJ9nw7BsJEB0Uw5O4n/KDxSM54MKygCfdriv l/JCDiqhabxgUGNyHAqZpYI= =Y6P8 -----END PGP SIGNATURE----- --8w3uRX/HFJGApMzv-- From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 10 14:06:21 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B41FC16A4CE for ; Tue, 10 Feb 2004 14:06:21 -0800 (PST) Received: from curacao.n2it.nl (62-177-157-186.bbeyond.nl [62.177.157.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 881A743D1D for ; Tue, 10 Feb 2004 14:06:21 -0800 (PST) (envelope-from billsf@curacao.n2it.nl) Received: by curacao.n2it.nl (Postfix, from userid 1000) id 4837A2058; Tue, 10 Feb 2004 23:06:20 +0100 (CET) Date: Tue, 10 Feb 2004 23:06:20 +0100 From: Bill Squire To: Tilman Linneweh Message-ID: <20040210220620.GA56300@curacao.n2it.nl> References: <000801c3f003$ca7e9f90$4502a8c0@VAL3> <20040210183649.GF86779@huckfinn.arved.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040210183649.GF86779@huckfinn.arved.de> User-Agent: Mutt/1.4.1i cc: Mike Thompson cc: freebsd-amd64@freebsd.org Subject: Re: cvsup X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2004 22:06:21 -0000 On Tue, Feb 10, 2004 at 07:36:49PM +0100, Tilman Linneweh wrote: > > Time for a FAQ? > > regards > tilman Indeed. Almost every mailing list or news group publishes a FAQ containing common problems and solutions known to work and updates it when needed. This saves allot of unnecessary posts, particularly from new members. Bill From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 11 01:01:15 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EBD5416A4CE for ; Wed, 11 Feb 2004 01:01:15 -0800 (PST) Received: from alogis.com (firewall.solit-ag.de [212.184.102.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 037ED43D1F for ; Wed, 11 Feb 2004 01:01:15 -0800 (PST) (envelope-from Holger.Kipp@alogis.com) Received: from intserv.int1.b.intern (localhost [127.0.0.1]) by alogis.com (8.11.1/8.9.3) with SMTP id i1B91CY23063 for ; Wed, 11 Feb 2004 10:01:12 +0100 (CET) (envelope-from hk@alogis.com) Message-Id: <200402110901.i1B91CY23063@alogis.com> Date: Wed, 11 Feb 2004 09:01:07 +0000 From: Holger Kipp To: freebsd-amd64@freebsd.org X-Mailer: phpGroupWare (http://www.phpgroupware.org) MIME-version: 1.0 Content-type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-description: Mail message body Subject: State of linux emulation under AMD64 (eg Opteron)? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Holger.Kipp@alogis.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2004 09:01:16 -0000 Hello, is it planned to have either 32-bit and/or 64-bit Linux Emulation available for AMD64 in the near future or to offer a general 32-bit 'Emulation' to run binaries compiled for 32-bit x86? And if so, what is the current status? As a side note, if or when can one use cvsup on 5.2 for AMD64 (eg via "pkg_add" or "make package)? Please cc me as I am not (yet) subscribed to this list. Regards, Holger Kipp From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 11 01:02:35 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DEBF16A4CE; Wed, 11 Feb 2004 01:02:35 -0800 (PST) Received: from rms04.rommon.net (rms04.rommon.net [212.54.2.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF5DC43D1D; Wed, 11 Feb 2004 01:02:34 -0800 (PST) (envelope-from pete@he.iki.fi) Received: from he.iki.fi (h81.vuokselantie10.fi [193.64.42.129]) by rms04.rommon.net (8.12.9p1/8.12.9) with ESMTP id i1B92TcM067577; Wed, 11 Feb 2004 11:02:32 +0200 (EET) (envelope-from pete@he.iki.fi) Message-ID: <4029EF67.9020703@he.iki.fi> Date: Wed, 11 Feb 2004 11:01:27 +0200 From: Petri Helenius User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: obrien@freebsd.org, peter@wemm.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: kld support X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2004 09:02:35 -0000 Since the kld support for amd64 is pending, is there a way to compile netgraph modules statically into the kernel to get for example ng_ether support? I would also be happy to try out early code if such thing exists. (to enable KLD) For the time being, I have a spare opteron box. Pete From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 11 02:06:02 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4B5316A4CE; Wed, 11 Feb 2004 02:06:02 -0800 (PST) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91CFD43D1D; Wed, 11 Feb 2004 02:06:02 -0800 (PST) (envelope-from des+tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 1E54D7303A; Wed, 11 Feb 2004 05:06:02 -0500 (EST) Sender: Tinderbox From: Tinderbox To: current@freebsd.org, amd64@freebsd.org Precedence: bulk Message-Id: <20040211100602.1E54D7303A@freebsd-current.sentex.ca> Date: Wed, 11 Feb 2004 05:06:02 -0500 (EST) Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2004 10:06:03 -0000 TB --- 2004-02-11 09:10:08 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-02-11 09:10:08 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-02-11 09:10:08 - checking out the source tree TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-02-11 09:14:23 - building world TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything.. TB --- 2004-02-11 10:01:33 - building generic kernel TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Wed Feb 11 10:01:33 GMT 2004 [...] cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/other/tinderbox/CURRENT/amd64/amd64/src/sys -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 -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 /other/tinderbox/CURRENT/amd64/amd64/src/sys/netinet/ip_input.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/other/tinderbox/CURRENT/amd64/amd64/src/sys -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 -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 /other/tinderbox/CURRENT/amd64/amd64/src/sys/netinet/ip_output.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/other/tinderbox/CURRENT/amd64/amd64/src/sys -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 -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 /other/tinderbox/CURRENT/amd64/amd64/src/sys/netinet/raw_ip.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/other/tinderbox/CURRENT/amd64/amd64/src/sys -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 -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 /other/tinderbox/CURRENT/amd64/amd64/src/sys/netinet/tcp_hostcache.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/other/tinderbox/CURRENT/amd64/amd64/src/sys -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 -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 /other/tinderbox/CURRENT/amd64/amd64/src/sys/netinet/tcp_input.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/other/tinderbox/CURRENT/amd64/amd64/src/sys -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/other/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 -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 /other/tinderbox/CURRENT/amd64/amd64/src/sys/netinet/tcp_output.c /other/tinderbox/CURRENT/amd64/amd64/src/sys/netinet/tcp_output.c: In function `tcp_output': /other/tinderbox/CURRENT/amd64/amd64/src/sys/netinet/tcp_output.c:119: warning: unused variable `sigoff' *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-02-11 10:06:01 - TB --- /usr/bin/make returned exit code 1 TB --- 2004-02-11 10:06:01 - TB --- ERROR: failed to build generic kernel TB --- 2004-02-11 10:06:01 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 11 02:39:10 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2218516A4CE for ; Wed, 11 Feb 2004 02:39:10 -0800 (PST) Received: from wn1.sci.kun.nl (wn1.sci.kun.nl [131.174.8.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FDA743D1D for ; Wed, 11 Feb 2004 02:39:09 -0800 (PST) (envelope-from adridg@sci.kun.nl) Received: from wn4.sci.kun.nl [131.174.8.3] (helo=wn4.sci.kun.nl) by wn1.sci.kun.nl (8.12.10/3.61) with ESMTP id i1BAYq6v007347; Wed, 11 Feb 2004 11:34:52 +0100 (MET) Date: Wed, 11 Feb 2004 11:34:52 +0100 (MET) From: Adriaan de Groot To: Holger Kipp In-Reply-To: <200402110901.i1B91CY23063@alogis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org Subject: Re: State of linux emulation under AMD64 (eg Opteron)? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: adridg@cs.kun.nl List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2004 10:39:10 -0000 On Wed, 11 Feb 2004, Holger Kipp wrote: > is it planned to have either 32-bit and/or 64-bit Linux Emulation > available for AMD64 in the near future or to offer a general 32-bit > 'Emulation' to run binaries compiled for 32-bit x86? Near future is apparently "once Peter &| David have the time." First on the list of priorities is getting 32-bit FreeBSD binaries to work. This is apparently close, but no cigar (and I might add that even 64-bit with threading is now very rough again). Getting Linux stuff to work is still much farther off. > As a side note, if or when can one use cvsup on 5.2 for AMD64 > (eg via "pkg_add" or "make package)? > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 Fetch cvsup from Peter's page (I think it is) .. it was mentioned a few days ago. Take a look at the list archives at that URL above. Then you will know (and have a cvsup-with-no-gui and no compression). -- Adriaan de Groot adridg@cs.kun.nl Kamer A6020 024-3652272 GPG Key Fingerprint 934E 31AA 80A7 723F 54F9 50ED 76AC EE01 FEA2 A3FE http://www.cs.kun.nl/~adridg/research/ From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 11 09:28:18 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD7E516A4CF for ; Wed, 11 Feb 2004 09:28:18 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 916CF43D1F for ; Wed, 11 Feb 2004 09:28:18 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.10/8.12.3) with ESMTP id i1BHOO2h030424; Wed, 11 Feb 2004 09:24:24 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i1BHONoP030418; Wed, 11 Feb 2004 09:24:23 -0800 Date: Wed, 11 Feb 2004 09:24:22 -0800 From: Brooks Davis To: adridg@cs.kun.nl Message-ID: <20040211172422.GA17038@Odin.AC.HMC.Edu> References: <200402110901.i1B91CY23063@alogis.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xHFwDpU9dbj6ez1V" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: Holger Kipp cc: freebsd-amd64@freebsd.org Subject: Re: State of linux emulation under AMD64 (eg Opteron)? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2004 17:28:18 -0000 --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 11, 2004 at 11:34:52AM +0100, Adriaan de Groot wrote: > On Wed, 11 Feb 2004, Holger Kipp wrote: > > is it planned to have either 32-bit and/or 64-bit Linux Emulation > > available for AMD64 in the near future or to offer a general 32-bit > > 'Emulation' to run binaries compiled for 32-bit x86? >=20 > Near future is apparently "once Peter &| David have the time." First on > the list of priorities is getting 32-bit FreeBSD binaries to work. This is > apparently close, but no cigar (and I might add that even 64-bit with > threading is now very rough again). Getting Linux stuff to work is still > much farther off. Some 32-bit binaries do run, just not all of them. I've been using the i386 p4 binary as my primary update mechanism on my amd64 test box. -- 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 --xHFwDpU9dbj6ez1V Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAKmVFXY6L6fI4GtQRAvmBAKDg8MXZ6hO7Evj2BPr2XIqsGqY55wCg10nn yNkuEX1/RPr0omY6yzz7U5A= =f+8Y -----END PGP SIGNATURE----- --xHFwDpU9dbj6ez1V-- From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 11 12:39:54 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6309D16A4CE; Wed, 11 Feb 2004 12:39:54 -0800 (PST) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D59043D1D; Wed, 11 Feb 2004 12:39:54 -0800 (PST) (envelope-from peter@evilpete.dyndns.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id C1FEE2A8E7; Wed, 11 Feb 2004 12:39:53 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 839DB2C1AC; Wed, 11 Feb 2004 12:39:53 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.12.10/8.12.10) with ESMTP id i1BKdpTd021128; Wed, 11 Feb 2004 12:39:51 -0800 (PST) (envelope-from peter@overcee.wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.12.10/8.12.10/Submit) id i1BKdoaG021127; Wed, 11 Feb 2004 12:39:50 -0800 (PST) (envelope-from peter) From: Peter Wemm To: Petri Helenius , obrien@freebsd.org Date: Wed, 11 Feb 2004 12:39:50 -0800 User-Agent: KMail/1.5.4 References: <4029EF67.9020703@he.iki.fi> In-Reply-To: <4029EF67.9020703@he.iki.fi> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402111239.50639.peter@wemm.org> cc: freebsd-amd64@freebsd.org Subject: Re: kld support X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2004 20:39:54 -0000 On Wednesday 11 February 2004 01:01 am, Petri Helenius wrote: > Since the kld support for amd64 is pending, is there a way to compile > netgraph modules statically into the kernel to get for example > ng_ether support? > > I would also be happy to try out early code if such thing exists. (to > enable KLD) For the time being, I have a spare opteron box. I have bad news and some good news on this front. I thought we might be able to get away with a quick hack to binutils to get it to work. Indeed, I've been able to produce .ko files that can be loaded and almost even work. But thats the problem... almost. Check out these lines in sys/conf/NOTES: options NETGRAPH #netgraph(4) system options NETGRAPH_ASYNC options NETGRAPH_BPF options NETGRAPH_BRIDGE options NETGRAPH_CISCO options NETGRAPH_ECHO options NETGRAPH_ETHER options NETGRAPH_FRAME_RELAY options NETGRAPH_GIF .....[lots more].... Thats how you chose what you want to compile in. Anyway, the problem with binutils is subtle but massive. There is a sanity check that prevents you producing shared libs without -fpic mode. Because *everybody* knows that ld.so cannot guarantee that it can load the library within the first 2GB of address space on linux, so binutils enforces this policy. The problem though is that all the wold is not linux. And there are legitimate reasons for doing this. One of which is our kernel modules where we can provide those guarantees. Anyway, removing the sanity check lets you produce them. BUT... because those code paths have never been tested on linux, binutils neglects to support the rest of the relocation types that would be needed, and none of the linux folks have noticed. Binutils is a freaking nightmare to try and work in, and it has me totally beaten on this one. So, I thought.. since I can do something about the in-kernel linker, perhaps I can add PIC mode support? The problem with that though is that gcc says "-fPIC mode not implemented in kernel mode" and errors out. There's no way in hell that I'm going to try and implement that in gcc either, so plan B is a bust. The good news though is that Plan C is possible. Plan C is to stop using -shared for kernel modules and use a simple .o file, like linux does. I think I can write code for the kld subsystem without too much pain. And because linux does the same thing already, we dont have to worry about treading on landmines in binutils/gcc, because that path should be well trodden already. We already produce these files in kmod.mk. If you have a look at the obj dirs, we have: ld -d -warn-common -r -d -o if_sl.kld if_sl.o slcompress.o touch /home/src/sys/modules/if_sl/obj/export_syms awk -f /home/src/sys/modules/if_sl/../../conf/kmod_syms.awk if_sl.kld /home/src/sys/modules/if_sl/obj/export_syms | xargs -J% objcopy % if_sl.kld ld -Bshareable -d -warn-common -o if_sl.ko if_sl.kld ld: if_sl.kld: relocation R_X86_64_32S can not be used when making a shared object; recompile with -fPIC .... ls obj/ -rw-r--r-- 1 root src 19608 Feb 11 12:32 if_sl.kld That file was the immediate step prior to conversion to a .ko file, and thats what we can load. On another machine with the hacks to produce a .ko anyway, we have: peter@hammer[12:37pm]/home/obj/home/src/sys/modules/if_sl-105> ls -l if_sl.* -rw-r--r-- 1 root wheel 19608 Feb 6 14:46 if_sl.kld -rwxr-xr-x 1 root wheel 23179 Feb 6 14:46 if_sl.ko* -rw-r--r-- 1 root wheel 15760 Feb 6 14:46 if_sl.o -rw-r--r-- 1 root wheel 24668 Feb 6 14:46 if_sl.s Also of note is that the .kld file is smaller than the .ko file. So yes, there is light at the end of the tunnel. I think its time to give up on binutils/gcc hacking and take the path of least resistence and write some code that we control. The original reasons for having -shared kernel object files are mostly obsolete these days. We dont use the DT_NEEDED tags for dependency tracking anymore, for example. I think we can actually get a superior system as a result. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 11 19:13:52 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67C9A16A4CE; Wed, 11 Feb 2004 19:13:52 -0800 (PST) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4983943D1F; Wed, 11 Feb 2004 19:13:52 -0800 (PST) (envelope-from marcel@xcllnt.net) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by ns1.xcllnt.net (8.12.10/8.12.10) with ESMTP id i1C3DqOE087766; Wed, 11 Feb 2004 19:13:52 -0800 (PST) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp01.pn.xcllnt.net (localhost [127.0.0.1]) i1C3DpuP099132; Wed, 11 Feb 2004 19:13:51 -0800 (PST) (envelope-from marcel@dhcp01.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.12.10/8.12.10/Submit) id i1C3Dp1h099131; Wed, 11 Feb 2004 19:13:51 -0800 (PST) (envelope-from marcel) Date: Wed, 11 Feb 2004 19:13:51 -0800 From: Marcel Moolenaar To: Peter Wemm Message-ID: <20040212031351.GA97767@dhcp01.pn.xcllnt.net> References: <4029EF67.9020703@he.iki.fi> <200402111239.50639.peter@wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200402111239.50639.peter@wemm.org> User-Agent: Mutt/1.4.1i cc: freebsd-amd64@freebsd.org cc: Petri Helenius Subject: Re: kld support X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2004 03:13:52 -0000 On Wed, Feb 11, 2004 at 12:39:50PM -0800, Peter Wemm wrote: > > So, I thought.. since I can do something about the in-kernel linker, > perhaps I can add PIC mode support? The problem with that though is > that gcc says "-fPIC mode not implemented in kernel mode" and errors > out. After looking at the gcc source code, it appears to me that the conflict is created by using -mcmodel as well as -fpic, right? If so, is there any harm in building the modules in the small model (for whatever that implies)? I think they'll still be 64-bit, right? -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 12 13:40:17 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB21416A4CE for ; Thu, 12 Feb 2004 13:40:17 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD7EF43D39 for ; Thu, 12 Feb 2004 13:40:17 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i1CLeHbv016891 for ; Thu, 12 Feb 2004 13:40:17 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i1CLeHwP016890; Thu, 12 Feb 2004 13:40:17 -0800 (PST) (envelope-from gnats) Resent-Date: Thu, 12 Feb 2004 13:40:17 -0800 (PST) Resent-Message-Id: <200402122140.i1CLeHwP016890@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, Mikhail Teterin Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B04816A4CE for ; Thu, 12 Feb 2004 13:31:21 -0800 (PST) Received: from harik.murex.com (mail.murex.com [194.98.239.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7AA943D2F for ; Thu, 12 Feb 2004 13:31:20 -0800 (PST) (envelope-from mteterin@pollux.us.murex.com) Received: from interscan.murex.fr (interscan.murex.fr [172.21.17.206]) by harik.murex.com with ESMTP id i1CLQJaw016974 for ; Thu, 12 Feb 2004 22:26:19 +0100 (CET) Received: from bilbo.murex.com (interscan.murex.fr [127.0.0.1]) by interscan.murex.fr (8.11.6/8.11.6) with ESMTP id i1CLRjQ02471 for ; Thu, 12 Feb 2004 22:27:45 +0100 Received: from pollux.us.murex.com ([172.21.130.56]) by bilbo.murex.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 12 Feb 2004 22:30:41 +0100 Received: (from mteterin@localhost) by pollux.us.murex.com (8.12.10/8.12.10/Submit) id i1CLUssk000835; Thu, 12 Feb 2004 16:30:54 -0500 (EST) (envelope-from mteterin) Message-Id: <200402122130.i1CLUssk000835@pollux.us.murex.com> Date: Thu, 12 Feb 2004 16:30:54 -0500 (EST) From: Mikhail Teterin To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: amd64/62753: txp(4) panics on amd4 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 12 Feb 2004 21:40:18 -0000 >Number: 62753 >Category: amd64 >Synopsis: txp(4) panics on amd4 >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Feb 12 13:40:17 PST 2004 >Closed-Date: >Last-Modified: >Originator: Mikhail Teterin >Release: FreeBSD 5.2.1-RC amd64 >Organization: Virtual Estates, Inc. >Environment: System: FreeBSD pollux 5.2.1-RC FreeBSD 5.2.1-RC #0: Sat Jan 31 12:38:34 GMT 2004 root@ngoc.NUXI.com:/usr/obj/usr/src/sys/GENERIC amd64 >Description: Although the txp0 is found and reported at boot time, an attempt to ifconfig it causes kernel page fault with txp0 being the "current process". Manual ifconfig or through dhclient -- does not matter. I first observed it while installing the RC and then (after installing over a different NIC) confirmed on a functional system. Here it is: dmesg: txp0: <3Com 3cR990-TX-95 Etherlink with 3XP Processor> port 0x8080-0x80ff mem 0xff380000-0xff3bffff irq 16 at device 10.0 on pci3 txp0: Ethernet address 00:01:02:68:53:e7 ifconfig: txp0: flags=8802 mtu 1500 options=13 ether 00:01:02:68:53:e7 media: Ethernet autoselect (100baseTX ) status: active The card, of course, worked perfectly in a i386 box for years. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 12 18:46:41 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A09016A4CE for ; Thu, 12 Feb 2004 18:46:41 -0800 (PST) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 530E243D1F for ; Thu, 12 Feb 2004 18:46:41 -0800 (PST) (envelope-from rodrigc@crodrigues.org) Received: from h00609772adf0.ne.client2.attbi.com ([66.31.45.197]) by comcast.net (sccrmhc11) with ESMTP id <2004021302464001100hv3gee>; Fri, 13 Feb 2004 02:46:40 +0000 Received: from h00609772adf0.ne.client2.attbi.com (localhost.crodrigues.org [127.0.0.1])i1D2kqhd075971 for ; Thu, 12 Feb 2004 21:46:53 -0500 (EST) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: (from rodrigc@localhost)i1D2kqel075970 for freebsd-amd64@freebsd.org; Thu, 12 Feb 2004 21:46:52 -0500 (EST) (envelope-from rodrigc) Date: Thu, 12 Feb 2004 21:46:52 -0500 From: Craig Rodrigues To: freebsd-amd64@freebsd.org Message-ID: <20040213024652.GA75957@crodrigues.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: Test building devel/apr port X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 02:46:41 -0000 Hi, Kris reported this failure to me: http://bento.freebsd.org/errorlogs/amd64-5-latest/apr-nothr-db4-0.9.4_8.log A fix to the apr port has just been committed. I don't have access to the amd64 platform. Can someone cvsup the devel/apr port and build it under amd64 and report the results to me? Thanks. -- Craig Rodrigues http://crodrigues.org rodrigc@crodrigues.org From owner-freebsd-amd64@FreeBSD.ORG Thu Feb 12 21:09:03 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FF0516A4CE for ; Thu, 12 Feb 2004 21:09:03 -0800 (PST) Received: from nu.binary.net (nu.binary.net [216.229.0.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB28743D1D for ; Thu, 12 Feb 2004 21:09:02 -0800 (PST) (envelope-from yura@binary.net) Received: from matrix.binary.net (matrix.binary.net [216.229.0.2]) by nu.binary.net (Postfix) with ESMTP id 5B5AC1586C; Thu, 12 Feb 2004 23:09:02 -0600 (CST) Received: by matrix.binary.net (Postfix, from userid 100) id F2868102935; Thu, 12 Feb 2004 23:09:01 -0600 (CST) Date: Thu, 12 Feb 2004 23:09:01 -0600 From: Yura Socolov To: Craig Rodrigues Message-ID: <20040213050901.GA79822@binary.net> References: <20040213024652.GA75957@crodrigues.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040213024652.GA75957@crodrigues.org> User-Agent: Mutt/1.4.2i cc: freebsd-amd64@freebsd.org Subject: Re: Test building devel/apr port X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 05:09:03 -0000 On Thu, Feb 12, 2004 at 09:46:52PM -0500, Craig Rodrigues wrote: > Kris reported this failure to me: > http://bento.freebsd.org/errorlogs/amd64-5-latest/apr-nothr-db4-0.9.4_8.log > > A fix to the apr port has just been committed. I don't > have access to the amd64 platform. Can someone > cvsup the devel/apr port and build it under amd64 and report > the results to me? It compiled and included tests say everything is ok: [0:02] [kussi:/usr/ports/devel/apr/work/apr-0.9.4/test] ./testall All APR Tests: Strings: ....... Time: ............ Versioning: .. IP subnets: ..... MMAP: ........ User Data: .... Table: ......... Hash: .............. Sleep: . Pools: ...... Formats: ....... File I/O: ..................... File Info: ..... Pipes: ...... File duplication: .... Directory: .............. Random: . DSO: ......... Other Child: . Socket Creation: ...... Socket Options: ...... Process control: ... Cross-Process Mutexes: . Poll: ...................... Thread Locks: .... Threads: ..... Getopt: ...... Path names: ........... Users: ... Path lists: .... Environment: ... 210 tests run: 210 passed, 0 failed, 0 not implemented. If you care for a make log, it can be found at: http://www.binary.net/yura/apr-make-log.txt uname -a: FreeBSD kussi.31337.net 5.2.1-RC FreeBSD 5.2.1-RC #2: Wed Feb 4 21:10:18 EST 2004 yura@kussi.31337.net:/usr/obj/usr/src/sys/GENERIC amd64 -- Yura Socolov FP: A7192ABD96E15F5 19AB21E60C34109 -- http://users.binary.net/yura/ -- -- Opinions and views in this message are my own and my own only. -- -- "Two wrongs don't make a right... and three rights make a left." -- TRACON From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 13 02:50:09 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DA0E16A4CE for ; Fri, 13 Feb 2004 02:50:09 -0800 (PST) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id A49D843D1F for ; Fri, 13 Feb 2004 02:50:08 -0800 (PST) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.9) with SMTP id i1DAnUeL012807 for ; Fri, 13 Feb 2004 11:49:31 +0100 (CET) (envelope-from wjw@withagen.nl) Message-ID: <0b6801c3f21f$1fd470b0$471b3dd4@dual> From: "Willem Jan Withagen" To: Date: Fri, 13 Feb 2004 11:49:58 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: System advice requested X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 10:50:09 -0000 Hi, If I were to get a dual opteron board/system what things would be to watch out for, or would be required. Hardware wise that is. In the beginning I would like to use is as: 1) FreeBSD/windows/linux desktop and lateron it would turn into my 2) Home NFS/Samba-server running FBSD In case 2) I'd remove any fancy user-interface stuff... All suggestions welcomed, Thanx, --WjW From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 13 03:02:09 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8C7E16A4CE for ; Fri, 13 Feb 2004 03:02:09 -0800 (PST) Received: from wn1.sci.kun.nl (wn1.sci.kun.nl [131.174.8.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20F5443D39 for ; Fri, 13 Feb 2004 03:02:09 -0800 (PST) (envelope-from adridg@sci.kun.nl) Received: from wn4.sci.kun.nl [131.174.8.3] (helo=wn4.sci.kun.nl) by wn1.sci.kun.nl (8.12.10/3.61) with ESMTP id i1DB276v028612; Fri, 13 Feb 2004 12:02:07 +0100 (MET) Date: Fri, 13 Feb 2004 12:02:07 +0100 (MET) From: Adriaan de Groot To: Willem Jan Withagen In-Reply-To: <0b6801c3f21f$1fd470b0$471b3dd4@dual> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org Subject: Re: System advice requested X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: adridg@cs.kun.nl List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 11:02:09 -0000 On Fri, 13 Feb 2004, Willem Jan Withagen wrote: > If I were to get a dual opteron board/system what things would be > to watch out for, or would be required. Hardware wise that is. > > In the beginning I would like to use is as: > 1) FreeBSD/windows/linux desktop > and lateron it would turn into my > 2) Home NFS/Samba-server running FBSD For all of that, dual opteron sounds massively overdone. Unless you can write off the system for tax purposes, or desperately want to play with dually stuff, there's no performance benefit over, say, an athlon XP 1600+. Performance in the sense of "snappy desktop use". Put another way - the reason for having a dual board is massive compute power and/or massive memory. I don't see much point in having 8G of memory in a home NFS server (unless you want to cache _everything_), and for desktop use, again, a single is really all you need. Unless your house needs heating, of course. There are several hardware-issues related threads in the archives at http://lists.freebsd.org/pipermail/freebsd-amd64/ -- it looks like some SATA stuff is to be avoided, depending on your FBSD install image the GigE may give you some trouble and require a different NIC for fetching newer sources, 4+2 DIMM configurations are crap. From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 13 03:16:57 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 23F5B16A4CE for ; Fri, 13 Feb 2004 03:16:57 -0800 (PST) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 746D043D1D for ; Fri, 13 Feb 2004 03:16:56 -0800 (PST) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.9) with SMTP id i1DBEleL015946; Fri, 13 Feb 2004 12:14:47 +0100 (CET) (envelope-from wjw@withagen.nl) Message-ID: <0b8201c3f222$a7d3eec0$471b3dd4@dual> From: "Willem Jan Withagen" To: References: Date: Fri, 13 Feb 2004 12:15:15 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: freebsd-amd64@freebsd.org Subject: Re: System advice requested X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 11:16:57 -0000 Like you suggest: I've also got some taxes to burn But also: I'd like to play And to be honest: In my new house 8Gb isn't going to cover all. It needs to: stream audio CD's and DVD's capture secure cams function as a database server for the domotica system central store and backup for all other PC's 4*W2K 5*FBSD ....... I was thinking of adding at least 1T of diskspace and see if either vinum, ccd, GEOM or something that is to come would be able to do the job. I knew about the SATA stuff from current@, but I would expect that carefull choices can prevent some of the major pittfalls. I'll have a go at the archive. Since your .nl too, any price indications and/or shop-advices??? --WjW ----- Original Message ----- From: "Adriaan de Groot" To: "Willem Jan Withagen" Cc: Sent: Friday, February 13, 2004 12:02 PM Subject: Re: System advice requested > On Fri, 13 Feb 2004, Willem Jan Withagen wrote: > > If I were to get a dual opteron board/system what things would be > > to watch out for, or would be required. Hardware wise that is. > > > > In the beginning I would like to use is as: > > 1) FreeBSD/windows/linux desktop > > and lateron it would turn into my > > 2) Home NFS/Samba-server running FBSD > > For all of that, dual opteron sounds massively overdone. Unless you can > write off the system for tax purposes, or desperately want to play with > dually stuff, there's no performance benefit over, say, an athlon XP > 1600+. Performance in the sense of "snappy desktop use". > > Put another way - the reason for having a dual board is massive compute > power and/or massive memory. I don't see much point in having 8G of memory > in a home NFS server (unless you want to cache _everything_), and for > desktop use, again, a single is really all you need. Unless your house > needs heating, of course. > > There are several hardware-issues related threads in the archives at > http://lists.freebsd.org/pipermail/freebsd-amd64/ -- it looks like some > SATA stuff is to be avoided, depending on your FBSD install image the GigE > may give you some trouble and require a different NIC for fetching newer > sources, 4+2 DIMM configurations are crap. > > > From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 13 03:32:05 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70F0516A4CF for ; Fri, 13 Feb 2004 03:32:05 -0800 (PST) Received: from sarajevo.pacific.net.sg (sarajevo.pacific.net.sg [203.120.90.134]) by mx1.FreeBSD.org (Postfix) with SMTP id 91E9743D2F for ; Fri, 13 Feb 2004 03:32:04 -0800 (PST) (envelope-from oceanare@pacific.net.sg) Received: (qmail 27085 invoked from network); 13 Feb 2004 11:32:02 -0000 Received: from unknown (HELO maxwell6.pacific.net.sg) (203.120.90.212) by sarajevo with SMTP; 13 Feb 2004 11:32:02 -0000 Received: from pacific.net.sg ([210.24.202.170]) by maxwell6.pacific.net.sg with ESMTP id <20040213113202.UGHX9972.maxwell6.pacific.net.sg@pacific.net.sg>; Fri, 13 Feb 2004 19:32:02 +0800 Message-ID: <402CB5B1.4070505@pacific.net.sg> Date: Fri, 13 Feb 2004 19:32:01 +0800 From: Erich Dollansky Organization: oceanare pte ltd User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en, en-us, de MIME-Version: 1.0 To: Willem Jan Withagen References: <0b8201c3f222$a7d3eec0$471b3dd4@dual> In-Reply-To: <0b8201c3f222$a7d3eec0$471b3dd4@dual> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: adridg@cs.kun.nl cc: freebsd-amd64@freebsd.org Subject: Re: System advice requested X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 11:32:05 -0000 Hi, Willem Jan Withagen wrote: > Like you suggest: > I've also got some taxes to burn It looks like this is the reason for many of the big machines. > I knew about the SATA stuff from current@, but I would expect that > carefull choices can prevent some of the major pittfalls. > I'll have a go at the archive. > If you are already at burning money, take SCSI. Those boards are available with two SCSI U320 channels. It also gives you a real speed gain. I have a dual Athlon box. It has had for a while an additional IDE drive. It is real slow compared to SCSI and give a pretty high CPU load compared to SCSI. >>For all of that, dual opteron sounds massively overdone. Unless you can >>write off the system for tax purposes, or desperately want to play with >>dually stuff, there's no performance benefit over, say, an athlon XP >>1600+. Performance in the sense of "snappy desktop use". >> A dual machine has even under load an extremely snappy desktop. The general speed gain is really not worth to mention, but the responsivnes of an SMP machine is real good. I use since some years for serious machines Tyan motherboards. But I have not touched an Opteron board yet. Erich From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 13 03:55:30 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E70416A4CE for ; Fri, 13 Feb 2004 03:55:30 -0800 (PST) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0768343D1F for ; Fri, 13 Feb 2004 03:55:30 -0800 (PST) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.9) with SMTP id i1DBrFeL016867; Fri, 13 Feb 2004 12:53:16 +0100 (CET) (envelope-from wjw@withagen.nl) Message-ID: <0b9001c3f228$083f84e0$471b3dd4@dual> From: "Willem Jan Withagen" To: "Erich Dollansky" References: <0b8201c3f222$a7d3eec0$471b3dd4@dual> <402CB5B1.4070505@pacific.net.sg> Date: Fri, 13 Feb 2004 12:53:43 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: adridg@cs.kun.nl cc: freebsd-amd64@freebsd.org Subject: Re: System advice requested X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 11:55:30 -0000 From: "Erich Dollansky" > > I knew about the SATA stuff from current@, but I would expect that > > carefull choices can prevent some of the major pittfalls. > > I'll have a go at the archive. > > > If you are already at burning money, take SCSI. Those boards are > available with two SCSI U320 channels. It also gives you a real > speed gain. I have a dual Athlon box. It has had for a while an > additional IDE drive. It is real slow compared to SCSI and give a > pretty high CPU load compared to SCSI. Though I have cash to spare, building a 1T array with SCSI would make it rather big and expensive. Since SCSI only goes to 144G. So I'd end up with 8 disks at least. Then I'd put in on a RAID controller and fiber. But that is way too professional. I'd do that for data-centres etc... SCSI disk have a better MBTF, but MBTF/$$ is something different. No, I'm more looking at 5*ATA 250 Gb at RAID-5, with a few spare disks on the shelf get a good ventilated case. it would be just manageble. --WjW From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 13 04:44:25 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11A6816A505 for ; Fri, 13 Feb 2004 04:44:24 -0800 (PST) Received: from lurza.secnetix.de (lurza.secnetix.de [195.143.231.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AB9743D1D for ; Fri, 13 Feb 2004 04:44:23 -0800 (PST) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (zyrozo@localhost [127.0.0.1]) by lurza.secnetix.de (8.12.9p2/8.12.9) with ESMTP id i1DCiLb0061872 for ; Fri, 13 Feb 2004 13:44:21 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.12.9p2/8.12.9/Submit) id i1DCiL7q061871; Fri, 13 Feb 2004 13:44:21 +0100 (CET) (envelope-from olli) Date: Fri, 13 Feb 2004 13:44:21 +0100 (CET) Message-Id: <200402131244.i1DCiL7q061871@lurza.secnetix.de> From: Oliver Fromme To: freebsd-amd64@FreeBSD.ORG X-Newsgroups: list.freebsd-amd64 User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.9-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Freebsd/amd64 on Sun Fire V20z? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@FreeBSD.ORG List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 12:44:25 -0000 Hi, The subject says it all ... Does ayone happen to have an idea whether FreeBSD/amd64 will run on a Sun Fire V20z? If it doesn't, I assume that FreeBSD/i386 will do for the moment, right? http://www.sun.com/servers/entry/v20z/ In the smallest configuration it's available for ~ $2800 which seems pretty cheap, taking the data into account (1U form factor, up to two processors, two U320 SCSI drive bays, two gigabit ethernet ports, 8 DIMM slots for up to 16 Gb RAM), _and_ the fact that it carries a cool Sun logo. ;-) I mean, for comparison, an x86-based HP Proliant DL360-G3 is just about the same price (or even a bit more), while having roughly the same data (1U, 2 x U320, 2 x gigabit), but only 32bit intel Xeon, not 64bit AMD Opteron. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "Clear perl code is better than unclear awk code; but NOTHING comes close to unclear perl code" (taken from comp.lang.awk FAQ) From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 13 05:02:31 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85D3F16A4CE for ; Fri, 13 Feb 2004 05:02:31 -0800 (PST) Received: from wn1.sci.kun.nl (wn1.sci.kun.nl [131.174.8.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 120A643D1F for ; Fri, 13 Feb 2004 05:02:31 -0800 (PST) (envelope-from adridg@sci.kun.nl) Received: from wn4.sci.kun.nl [131.174.8.3] (helo=wn4.sci.kun.nl) by wn1.sci.kun.nl (8.12.10/3.61) with ESMTP id i1DD2T6v017213; Fri, 13 Feb 2004 14:02:29 +0100 (MET) Date: Fri, 13 Feb 2004 14:02:29 +0100 (MET) From: Adriaan de Groot To: Willem Jan Withagen In-Reply-To: <0b8201c3f222$a7d3eec0$471b3dd4@dual> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org Subject: Re: System advice requested X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: adridg@cs.kun.nl List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 13:02:31 -0000 On Fri, 13 Feb 2004, Willem Jan Withagen wrote: > And to be honest: > In my new house 8Gb isn't going to cover all. None of that sounds particularly memory-intensive, but hey. > Since your .nl too, any price indications and/or shop-advices??? No, since I don't have money to burn (but did want to play) so I'm in consumer-grade space (k8v, 1G, amd64 3200+). For that, comptechworld.nl is my "huisleverancier", although they are more expensive than the rock-bottom stuff you can get now (computerland.nl sells a msi neo + cpu for E350). switch.nl will sell you just about anything if you ask :) They got a collegue of mine an sk8n w/ 4G (of which the BIOS apparently only sees 3.5 G - very odd). That was around E2000 for the full system. For big dually boxes, I really don't know whether post-order parts stores (even if they will assemble for you) will cut it. CTW was willing to custom-build a dual athlon MP w/4G back in the day that that was da bong, though. -- Adriaan de Groot adridg@cs.kun.nl Kamer A6020 024-3652272 GPG Key Fingerprint 934E 31AA 80A7 723F 54F9 50ED 76AC EE01 FEA2 A3FE http://www.cs.kun.nl/~adridg/research/ From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 13 05:17:25 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C948216A4D0 for ; Fri, 13 Feb 2004 05:17:25 -0800 (PST) Received: from bigtex.jrv.org (rrcs-sw-24-73-246-106.biz.rr.com [24.73.246.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id E031E43D1F for ; Fri, 13 Feb 2004 05:17:24 -0800 (PST) (envelope-from james@bigtex.jrv.org) Received: from bigtex.jrv.org (localhost [127.0.0.1]) by bigtex.jrv.org (8.12.1/8.12.1) with ESMTP id i1DDHNo8021340 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 13 Feb 2004 07:17:23 -0600 (CST) Received: (from james@localhost) by bigtex.jrv.org (8.12.1/8.12.1/Submit) id i1DDHNku021337; Fri, 13 Feb 2004 07:17:23 -0600 (CST) Date: Fri, 13 Feb 2004 07:17:23 -0600 (CST) Message-Id: <200402131317.i1DDHNku021337@bigtex.jrv.org> From: James Van Artsdalen To: Oliver Fromme In-reply-to: <200402131244.i1DCiL7q061871@lurza.secnetix.de> (message from Oliver Fromme on Fri, 13 Feb 2004 13:44:21 +0100 (CET)) References: <200402131244.i1DCiL7q061871@lurza.secnetix.de> cc: freebsd-amd64@freebsd.org Subject: Re: Freebsd/amd64 on Sun Fire V20z? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 13:17:25 -0000 > Date: Fri, 13 Feb 2004 13:44:21 +0100 (CET) > From: Oliver Fromme > > Does ayone happen to have an idea whether FreeBSD/amd64 will run on > a Sun Fire V20z? If it doesn't, I assume that FreeBSD/i386 will do > for the moment, right? > > http://www.sun.com/servers/entry/v20z/ Since it can use "customer provided" Windows and SUSE linux the boot environment is probably normal enough for FreeBSD/amd64 to boot. The main thing to check is to make sure the onboard NIC and SCSI controllers are supported. The other thing of course is to make sure there's no critical app you need that isn't amd64 ported yet. From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 13 05:17:43 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 475A616A4CE for ; Fri, 13 Feb 2004 05:17:43 -0800 (PST) Received: from bragi.housing.ufl.edu (bragi.housing.ufl.edu [128.227.47.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 030F243D1D for ; Fri, 13 Feb 2004 05:17:43 -0800 (PST) (envelope-from WillS@housing.ufl.edu) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Fri, 13 Feb 2004 08:17:39 -0500 Message-ID: <0E972CEE334BFE4291CD07E056C76ED8DB37F5@bragi.housing.ufl.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: System advice requested Thread-Index: AcPyINt0zVK7PlFERtG4O/2J7wO5KgAEqO3A From: "Will Saxon" To: , "Willem Jan Withagen" cc: freebsd-amd64@freebsd.org Subject: RE: System advice requested X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 13:17:43 -0000 >=20 > There are several hardware-issues related threads in the archives at > http://lists.freebsd.org/pipermail/freebsd-amd64/ -- it looks=20 > like some > SATA stuff is to be avoided, depending on your FBSD install=20 > image the GigE > may give you some trouble and require a different NIC for=20 > fetching newer > sources, 4+2 DIMM configurations are crap. At least with my board (an 'awful' 4+0 MSI K8T Master2-FAR board) the = onboard broadcom NIC does not work correctly with bge. It does work with = ndis though. Also for whatever reason -current as of last weekend would = lock the machine up hard after ~ 30 minutes. Haven't had time to work on = why. -Will From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 13 06:45:07 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A69116A4CE for ; Fri, 13 Feb 2004 06:45:07 -0800 (PST) Received: from web14102.mail.yahoo.com (web14102.mail.yahoo.com [216.136.172.132]) by mx1.FreeBSD.org (Postfix) with SMTP id 7128843D1F for ; Fri, 13 Feb 2004 06:45:07 -0800 (PST) (envelope-from cguttesen@yahoo.dk) Message-ID: <20040213144507.11985.qmail@web14102.mail.yahoo.com> Received: from [194.248.174.58] by web14102.mail.yahoo.com via HTTP; Fri, 13 Feb 2004 15:45:07 CET Date: Fri, 13 Feb 2004 15:45:07 +0100 (CET) From: =?iso-8859-1?q?Claus=20Guttesen?= To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: cguttesen@yahoo.dk Subject: re: trouble with K8T Master2-FAR (dual Opteron) (solved) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 14:45:07 -0000 > I'm trying to install FreeBSD/amd64 to dual Opteron > machine. > M/B: MSI K8T Master2-FAR > CPU: AMD Opteron 240 x 2 > Mem: 512MB x 2 ( in Slot 1 and 3, Single channel) >I had some trouble with this installation. Hi. Acquired the same board Opteron 242. Experienced the same panic using acpi with 5.2 and 5.2.1 RC. I went into the BIOS, then 'Advanced BIOS Features' and changed 'MPS Version Control for OS' _from_ 1.4 to 1.1. This enabled the second CPU. Using the stock 5.2 install-CD will make the board panic if it's soft-rebooted (like shutdown -r now). So I had to swicth it completely off and on again. I have just cvsup'ed to current as of Feb. 13'th 2004 approx. 13.00 GMT, and the above mentioned hard reboot apperantly is _not_ necessary. I'm using BIOS ver. 1.1. I tried to subscibe to the amd64-list, but did not yet receive any verification. Hope this helps. This was purely trial-and-error, so I was very pleased with the fact that I didn't have to use the i386-port. regards Claus Yahoo! Mail (http://dk.mail.yahoo.com) - Gratis: 6 MB lagerplads, spamfilter og virusscan From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 13 07:54:00 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF25B16A4E6 for ; Fri, 13 Feb 2004 07:54:00 -0800 (PST) Received: from sack.dreamhost.com (sack.dreamhost.com [66.33.213.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAA7843D2F for ; Fri, 13 Feb 2004 07:54:00 -0800 (PST) (envelope-from absinthe@pobox.com) Received: from redstone.retrovertigo.com (ool-182dd6f2.dyn.optonline.net [24.45.214.242]) by sack.dreamhost.com (Postfix) with ESMTP id 74DC35681E for ; Fri, 13 Feb 2004 07:54:00 -0800 (PST) From: Dylan Carlson To: freebsd-amd64@freebsd.org Date: Fri, 13 Feb 2004 10:52:12 -0500 User-Agent: KMail/1.6 References: <0b8201c3f222$a7d3eec0$471b3dd4@dual> <402CB5B1.4070505@pacific.net.sg> In-Reply-To: <402CB5B1.4070505@pacific.net.sg> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200402131052.12590.absinthe@pobox.com> Subject: Re: System advice requested X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: absinthe@pobox.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 15:54:00 -0000 On Friday 13 February 2004 06:32, Erich Dollansky wrote: > > I use since some years for serious machines Tyan motherboards. But > I have not touched an Opteron board yet. > Tyan K8W here with dual 242's. Love it. Cheers, Dylan Carlson [absinthe@pobox.com] From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 13 08:45:27 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C97DE16A4CE for ; Fri, 13 Feb 2004 08:45:27 -0800 (PST) Received: from malkavian.ghostar.ath.cx (rrcs-sw-24-153-201-7.biz.rr.com [24.153.201.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CD0143D1D for ; Fri, 13 Feb 2004 08:45:27 -0800 (PST) (envelope-from hcoyote@malkavian.ghostar.ath.cx) Received: from malkavian.ghostar.ath.cx (hcoyote@localhost.ghostar.ath.cx [127.0.0.1])i1DGjQKe048216 for ; Fri, 13 Feb 2004 10:45:26 -0600 (CST) (envelope-from hcoyote@malkavian.ghostar.ath.cx) Received: (from hcoyote@localhost) by malkavian.ghostar.ath.cx (8.12.9/8.12.8/Submit) id i1DGjQQp048215 for freebsd-amd64@freebsd.org; Fri, 13 Feb 2004 10:45:26 -0600 (CST) Date: Fri, 13 Feb 2004 10:45:26 -0600 From: HCoyote To: freebsd-amd64@freebsd.org Message-ID: <20040213164526.GA48076@malkavian.ghostar.ath.cx> Mail-Followup-To: freebsd-amd64@freebsd.org References: <200402131244.i1DCiL7q061871@lurza.secnetix.de> <200402131317.i1DDHNku021337@bigtex.jrv.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200402131317.i1DDHNku021337@bigtex.jrv.org> User-Agent: Mutt/1.5.5.1i X-Scanned-By: MIMEDefang 2.39 Subject: Re: Freebsd/amd64 on Sun Fire V20z? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 16:45:27 -0000 On Fri, Feb 13, 2004 at 07:17:23AM -0600, James Van Artsdalen wrote: > Since it can use "customer provided" Windows and SUSE linux the boot > environment is probably normal enough for FreeBSD/amd64 to boot. > > The main thing to check is to make sure the onboard NIC and SCSI > controllers are supported. The V20Z is using the following: Broadcom 5703 rev2 LSI Logic 53c1030 Fusion-MPT The broadcom is supported by bge(4). The 53c1030 is supported by mpt(4). I'll see if I can get 5.2R loaded on the one we have if its not being used. Travis From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 13 11:36:42 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7FA316A4CE for ; Fri, 13 Feb 2004 11:36:42 -0800 (PST) Received: from mail.atl.us.wormulon.net (unknown [63.223.8.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D7BE43D1F for ; Fri, 13 Feb 2004 11:36:42 -0800 (PST) (envelope-from hscholz@beach.wormulon.net) Received: from localhost (unknown [63.223.8.130]) by mail.atl.us.wormulon.net (Postfix) with ESMTP id 317E45D9A1 for ; Fri, 13 Feb 2004 14:37:06 -0500 (EST) Received: from mail.atl.us.wormulon.net ([63.223.8.130]) by localhost (plant.wormulon.net [63.223.8.130]) (amavisd-new, port 10024) with ESMTP id 33727-07 for ; Fri, 13 Feb 2004 14:37:05 -0500 (EST) Received: from beach.wormulon.net (unknown [63.223.8.131]) by mail.atl.us.wormulon.net (Postfix) with ESMTP id 122075D99F for ; Fri, 13 Feb 2004 14:37:05 -0500 (EST) Received: by beach.wormulon.net (Postfix, from userid 8001) id E30B4C3924; Fri, 13 Feb 2004 14:37:04 -0500 (EST) Date: Fri, 13 Feb 2004 14:37:04 -0500 From: Hendrik Scholz To: freebsd-amd64@freebsd.org Message-ID: <20040213193704.GA78028@beach.wormulon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Virus-Scanned: turning SPAM into Slurm since 2003 (wormulon.net) Subject: gdb support? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 19:36:42 -0000 Hi! I've just installed two Dual Opteron machines (works nice :)) but ran into a third party program related bug that I'd like to solve. Is there any gdb like program available? (I've got a core dump to analyze :)) Btw: Are there any known issues with the ti driver? From time to time it seems to send broken packages. Since they make it to the receiver IP and TCP layers seem to be fine but ssh connections drop every few minutes. ti0: mem 0xfc8bc000-0xfc8bffff irq 28 at device 1.0 on pci1 Thanks, Hendrik -- Hendrik Scholz - - http://raisdorf.net/ drag me, drop me - treat me like an object From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 13 11:42:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2A1516A4CE for ; Fri, 13 Feb 2004 11:42:56 -0800 (PST) Received: from wn1.sci.kun.nl (wn1.sci.kun.nl [131.174.8.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23FF843D1D for ; Fri, 13 Feb 2004 11:42:56 -0800 (PST) (envelope-from adridg@sci.kun.nl) Received: from wn4.sci.kun.nl [131.174.8.3] (helo=wn4.sci.kun.nl) by wn1.sci.kun.nl (8.12.10/3.61) with ESMTP id i1DJgt6v023398; Fri, 13 Feb 2004 20:42:55 +0100 (MET) Date: Fri, 13 Feb 2004 20:42:54 +0100 (MET) From: Adriaan de Groot To: Hendrik Scholz In-Reply-To: <20040213193704.GA78028@beach.wormulon.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org Subject: Re: gdb support? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: adridg@cs.kun.nl List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 19:42:56 -0000 On Fri, 13 Feb 2004, Hendrik Scholz wrote: > I've just installed two Dual Opteron machines (works nice :)) but ran > into a third party program related bug that I'd like to solve. So tell us what they are, since there are people asking for tips on good dual machines for FBSD. > Is there any gdb like program available? > (I've got a core dump to analyze :)) Yes, gdb from the GNU ftp area - you will want a CVS snapshot version. I picked up a package gdb+dejagnu-20031116 back in november (when I got my first core dump) and it works quite well. From owner-freebsd-amd64@FreeBSD.ORG Fri Feb 13 14:05:50 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19BA716A4CF; Fri, 13 Feb 2004 14:05:50 -0800 (PST) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0071443D1D; Fri, 13 Feb 2004 14:05:50 -0800 (PST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 4A39B7303A; Fri, 13 Feb 2004 17:05:49 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: freebsd tinderbox , current@freebsd.org, amd64@freebsd.org Precedence: bulk Message-Id: <20040213220549.4A39B7303A@freebsd-current.sentex.ca> Date: Fri, 13 Feb 2004 17:05:49 -0500 (EST) Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 22:05:50 -0000 TB --- 2004-02-13 21:22:44 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-02-13 21:22:44 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-02-13 21:22:44 - checking out the source tree TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-02-13 21:27:04 - building world TB --- cd /home/tinderbox/sandbox/CURRENT/amd64/amd64/src TB --- /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.. [...] ===> sbin/ipfw cc -O -pipe -c /other/tinderbox/CURRENT/amd64/amd64/src/sbin/ipfw/ipfw2.c In file included from /other/tinderbox/CURRENT/amd64/amd64/src/sbin/ipfw/ipfw2.c:53: /home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/include/netinet/ip_dummynet.h: In function `ip_dn_find_rule': /home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/include/netinet/ip_dummynet.h:362: error: `PACKET_TAG_DUMMYNET' undeclared (first use in this function) /home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/include/netinet/ip_dummynet.h:362: error: (Each undeclared identifier is reported only once /home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/include/netinet/ip_dummynet.h:362: error: for each function it appears in.) /home/tinderbox/sandbox/CURRENT/amd64/amd64/obj/amd64/other/tinderbox/CURRENT/amd64/amd64/src/i386/usr/include/netinet/ip_dummynet.h:363: error: dereferencing pointer to incomplete type *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src/sbin/ipfw. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src/sbin. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /other/tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-02-13 22:05:49 - TB --- /usr/bin/make returned exit code 1 TB --- 2004-02-13 22:05:49 - TB --- ERROR: failed to build world TB --- 2004-02-13 22:05:49 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 14 07:52:25 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DDB916A4CE for ; Sat, 14 Feb 2004 07:52:25 -0800 (PST) Received: from mail.massarenti.com (host238-109.pool8017.interbusiness.it [80.17.109.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9530A43D1F for ; Sat, 14 Feb 2004 07:52:24 -0800 (PST) (envelope-from massarenti@massarenti.com) Received: by mail.massarenti.com (Postfix, from userid 527) id EAB266F7B4; Sat, 14 Feb 2004 16:38:07 +0100 (CET) Received: from ts (ts.massarenti.com [192.168.1.201]) by mail.massarenti.com (Postfix) with SMTP id 85D376F679 for ; Sat, 14 Feb 2004 16:38:07 +0100 (CET) Message-ID: <002c01c3f312$947a26a0$c901a8c0@ts> From: "Luca Massarenti" To: Date: Sat, 14 Feb 2004 16:52:42 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.3790.0 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0 Subject: which motherboard and which chipset? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Feb 2004 15:52:25 -0000 Hi I 'am italian RHCE even if I like freebsd very much. I want to start installing freebsd on amd based server and in particular using opteron cpu. I want to install an application server which run a java application for about 80 clients Which chipset is best and is best tested? Which mainboard is considered the best? What about dual processors? Generally I like asus MB and nvidia chipset very much but I have never installed unix-like operating system on amd processors. I have the possibility to choose between via and nvidia and between asus and MSI. Please suggest me the best choice for this porpouse. Thanks Luca From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 14 13:03:17 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1459D16A4CE for ; Sat, 14 Feb 2004 13:03:17 -0800 (PST) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 48D2043D1D for ; Sat, 14 Feb 2004 13:03:16 -0800 (PST) (envelope-from Gregor.Bittel@GMX.de) Received: (qmail 3550 invoked by uid 65534); 14 Feb 2004 21:03:12 -0000 Received: from pC19F2EDE.dip.t-dialin.net (EHLO 2x_Xeon.BI) (193.159.46.222) by mail.gmx.net (mp023) with SMTP; 14 Feb 2004 22:03:12 +0100 X-Authenticated: #3119465 From: Gregor Bittel To: freebsd-amd64@freebsd.org Date: Sat, 14 Feb 2004 22:04:37 +0100 User-Agent: KMail/1.5 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200402142204.37739.Gregor.Bittel@GMX.de> Subject: SMP-Boards for Opteron and other processors (was: Re: gdb support?) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Feb 2004 21:03:17 -0000 Hi, On Freitag, 13. Februar 2004 20:42 Adriaan de Groot wrote: > On Fri, 13 Feb 2004, Hendrik Scholz wrote: > > I've just installed two Dual Opteron machines (works nice :)) but > > ran into a third party program related bug that I'd like to > > solve. > > So tell us what they are, since there are people asking for tips on > good dual machines for FBSD. At this point I will make some "propaganda" for my project, which I started some years ago - a list[1] of SMP-Boards running with FreeBSD (in real SMP-mode with two or more physical processors - sorted by the used CPU-Socket/Slot). There is only one Opteron-Board on it, but I hope I will have someday every running type of SMP-Board on it. I'm only a normal FreeBSD-User and reading this mailinglist since a few weeks "in background" - but I can't do any tests of amd64-systems, because I haven't such a system at home. Everyone is invited to add his good running (SMP)-Board to this list - I know there are people outside in the world who are searching for this ones. The "rules": I'm adding only boards with real SMP-Mode (with 2 or more physical processors installed) who can be identified with a specific name or number (example: the "Tyan Thunder K8S Pro S2882G3NR" and the "Tyan Thunder K8S Pro S2882UG3NR" are different boards and will be listed as different, each with an own entry). If it is possible, I will get a dmesg, mptable and "pciconf -lv"-output to add these outputs (it should be possible to build the same system IMHO). -Gregor. -- Gregor.Bittel@GMX.de [1]= http://www.bnv-bamberg.de/home/ba3294/smp/index.htm From owner-freebsd-amd64@FreeBSD.ORG Sat Feb 14 14:26:09 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3157A16A4CE for ; Sat, 14 Feb 2004 14:26:09 -0800 (PST) Received: from wn1.sci.kun.nl (wn1.sci.kun.nl [131.174.8.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFE8D43D1F for ; Sat, 14 Feb 2004 14:26:08 -0800 (PST) (envelope-from adridg@sci.kun.nl) Received: from wn4.sci.kun.nl [131.174.8.3] (helo=wn4.sci.kun.nl) by wn1.sci.kun.nl (8.12.10/3.61) with ESMTP id i1EMQ66v006026; Sat, 14 Feb 2004 23:26:06 +0100 (MET) Date: Sat, 14 Feb 2004 23:26:06 +0100 (MET) From: Adriaan de Groot To: Luca Massarenti In-Reply-To: <002c01c3f312$947a26a0$c901a8c0@ts> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org Subject: Re: which motherboard and which chipset? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: adridg@cs.kun.nl List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Feb 2004 22:26:09 -0000 Ciao, Luca, On Sat, 14 Feb 2004, Luca Massarenti wrote: > I want to start installing freebsd on amd based server and in particular > using opteron cpu. > > I want to install an application server which run a java application for > about 80 clients > > Which chipset is best and is best tested? Before you ask that question you should probably ask: does Java run at all under FreeBSD on amd64? Also remember that there is a native FreeBSD JSK version 1.3 - no 1.4 or 1.5. Running Linux binaries is, as yet, not possible. So first check if the platform can support what you need. > Which mainboard is considered the best? > What about dual processors? Take a look at the archives of this list (via http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 ), there's lot of hardware mentioned. I think a lot depends on how much memory you need to support your users: Athlon64 boards (single CPU) tend to top out at 4G theoretical and 3G practical (like my Asus k8v, with 3 slots so I could stick 3G of DDR266 in it) ; Opteron boards for single CPU with 4 slots top out at 8G theoretical (4x2G Registered), but I hear tales of an sk8n supporting only 3.5G. Dual boards run up to 8 slots, for 16G of memory. > I have the possibility to choose between via and nvidia and between asus and > MSI. That sounds very much like you're limiting yourself to single CPU systems (although MSI makes the k8t master2, with 2 CPUs and 4 memory slots, and the k8dm, which looks like the kind of 4+2 dimm solution that is said to be dodgy). You state you want to use an opteron processor, that's socket 940, and limiting your choices to those two manufacturers and chipsets. Hm. That throws out the MSI k8d, since that's an amd chipset. That leaves the k8t master (not the neo, since it's socket 754) and asus sk8n (nvidia) or sk8v (via). Maybe you already knew all that. I don't recall any of those systems being mentioned here on the list - but again, check the archives. I'll tell you that my own asus k8v w/ 1G and using SATA drives works just fine - for one user, at least.