From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 11 14:19:03 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D6AF16A41F for ; Sun, 11 Dec 2005 14:19:03 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id A230943D5F for ; Sun, 11 Dec 2005 14:19:01 +0000 (GMT) (envelope-from lars.tunkrans@bredband.net) Received: from [192.168.245.40] ([213.112.167.135] [213.112.167.135]) by mxfep01.bredband.com with ESMTP id <20051211141900.BPXU676.mxfep01.bredband.com@[192.168.245.40]> for ; Sun, 11 Dec 2005 15:19:00 +0100 Message-ID: <439C3555.2090909@bredband.net> Date: Sun, 11 Dec 2005 15:19:01 +0100 From: Lars Tunkrans User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.12) Gecko/20051118 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@FreeBSD.org References: <200512082032.jB8KWbQP089454@freefall.freebsd.org> In-Reply-To: <200512082032.jB8KWbQP089454@freefall.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Anyone running R 6.0 on Shuttle SN25P X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2005 14:19:03 -0000 Hi; Does anyone have experience of FreeBSD 6.0 Running on the Shuttle SN25P. I am looking for a ( silent) platform for hosting 3 large disks ( 3 * 300-500 GB SATA RAID ) for a NFS server with Gigabit Ethernet. This box does have PCI Express, is that stable enough at this point ? Graphics ( probably some low-end PCI-E Nvidia board of my choise ) attached to a PCI-Express X16 slot ( will this work ? ) CPU socket 939 ( probably AMD Athlon 64 3800+, As I have one spare ) NorthBridge/SouthBridge - nForce 4 Ultra MCP SATA - nForce 4 Ultra MCP Audio - VIA Envy24 unimportant for a server LAN/Ethernet - Marvel 88E1111 Firewire - VIA VT6307 USB - nForce 4 Ultra MCP http://www.shuttle.com/share/product_data/spec/SN25P_DM.pdf //Lars From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 11 17:00:28 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01C0A16A41F for ; Sun, 11 Dec 2005 17:00:28 +0000 (GMT) (envelope-from work@ashleymoran.me.uk) Received: from mail.dc-servers.com (mail.dc-servers.com [83.243.101.206]) by mx1.FreeBSD.org (Postfix) with SMTP id A21C343D5E for ; Sun, 11 Dec 2005 17:00:26 +0000 (GMT) (envelope-from work@ashleymoran.me.uk) Received: (qmail 13123 invoked by uid 399); 11 Dec 2005 17:02:14 -0000 Received: from unknown (HELO alfie.jigsawhq.com) (work@ashleymoran.me.uk@213.106.224.113) by mail.dc-servers.com with SMTP; 11 Dec 2005 17:02:14 -0000 From: Ashley Moran Organization: Codeweavers Ltd To: freebsd-amd64@freebsd.org Date: Sun, 11 Dec 2005 16:59:19 +0000 User-Agent: KMail/1.8.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512111659.20182.work@ashleymoran.me.uk> Subject: Problem with FreeBSD-6.0-amd64 on MSI Neo2 Platinum X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2005 17:00:28 -0000 A few weeks back I had to replace the motherboard in a server, and the only motherboard with ATA RAID I could get locally was an MSI Neo2 Platinum (nForce 3 chipset). I initially just swapped the board out and booted back into i386 mode, but I just tried to reinstall with 6.0-REL-amd64. I get a corrupt boot loader screen and the following information when I hit enter a few times: int=0000000d err=00000000 efl=00030002 eip=0000ffff eax=000500b2 ebx=000503d6 ecx=00059214 edx=00050000 esi=00059194 edi=0005999c ebp=00091cb0 esp=0000c3dc cs=d000 ds=d6cf es=9b8a fs=0033 gs=0033 ss=d6cf syms=[0x8+0x8c268+0x8+0x7 (i think this bit is from the corrupt boot process) cs: eip=ff ff ff ff ff ff ff ff-ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff-ff ff ff ff ff ff ff ff ss: esp=ff ff ff ff ff ff ff ff-ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff-ff ff ff ff ff ff ff ff BTX halted I've tried disabling as much as I can in the BIOS but I still get the same error. Is there anything else I could look into that might cause the issue or is it a motherboard fault? I'm new to amd64 and I had expected the install to go as sweetly as i386 (wish I'd booted the install CD before running pkg_deinstall -a!). Oh well :( Ashley PS if there is no way round this, can anyone recommend a good FreeBSD compatible amd64 board that comes with ATA RAID? From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 11 19:37:54 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25F1B16A41F for ; Sun, 11 Dec 2005 19:37:54 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id A075C43D49 for ; Sun, 11 Dec 2005 19:37:52 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IRC0054FMQEEB10@osl1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Sun, 11 Dec 2005 20:42:14 +0100 (CET) Received: from kg-work.kg4.no ([80.203.92.30]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0IRC00C0OMNOQ4Q0@osl1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Sun, 11 Dec 2005 20:40:36 +0100 (CET) Date: Sun, 11 Dec 2005 20:37:47 +0100 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH To: freebsd-amd64@freebsd.org Message-id: <20051211203747.474fb5a6.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd5.4) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: FreeBSD/amd64: is Linux 32-bit or 64-bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2005 19:37:54 -0000 No, really, this is NOT a trick question. I run FreeBSD/amd64 on one of my machines. As usual, I have installed the linuxulator and the linux_base-8 port. While doing some crazy tricks in my neverending quest to get a working Java browser plugin for my amd64 machine, I thought about the linuxulator and the linux_base-8 port. Since the platform OS is 64-bit, I assumed that the Linuxulator and the linux_base-8 port also was 64-bit. However, I'm not so sure anymore: root@kg-quiet# uname -a FreeBSD kg-quiet.kg4.no 6.0-STABLE FreeBSD 6.0-STABLE #0: Thu Dec 8 00:56:05 CET 2005 root@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET amd64 root@kg-quiet# /compat/linux/bin/uname -a Linux kg-quiet.kg4.no 2.4.2 FreeBSD 6.0-STABLE #0: Thu Dec 8 00:56:05 CET 2005 i686 i686 i386 GNU/Linux This last part seems to say that linux on this machine is 32-bit? What is the correct answer? -- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 11 19:59:24 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D2A3016A41F for ; Sun, 11 Dec 2005 19:59:24 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.178.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9825343D5F for ; Sun, 11 Dec 2005 19:59:21 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [217.185.96.166] (manz-d9b960a6.pool.mediaWays.net [217.185.96.166]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate2.zdv.Uni-Mainz.DE (Postfix) with ESMTP id CB45C3000F05; Sun, 11 Dec 2005 20:59:18 +0100 (CET) Message-ID: <439C8512.2090602@mail.uni-mainz.de> Date: Sun, 11 Dec 2005 20:59:14 +0100 From: "O. Hartmann" User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Torfinn Ingolfsen References: <20051211203747.474fb5a6.torfinn.ingolfsen@broadpark.no> In-Reply-To: <20051211203747.474fb5a6.torfinn.ingolfsen@broadpark.no> Content-Type: multipart/mixed; boundary="------------090101060101030804000603" X-Virus-Scanned: by amavisd-new at uni-mainz.de X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD/amd64: is Linux 32-bit or 64-bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2005 19:59:24 -0000 This is a multi-part message in MIME format. --------------090101060101030804000603 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Torfinn Ingolfsen wrote: >No, really, this is NOT a trick question. > >I run FreeBSD/amd64 on one of my machines. As usual, I have installed >the linuxulator and the linux_base-8 port. >While doing some crazy tricks in my neverending quest to get a >working Java browser plugin for my amd64 machine, I thought about the >linuxulator and the linux_base-8 port. > >Since the platform OS is 64-bit, I assumed that the Linuxulator and the >linux_base-8 port also was 64-bit. > >However, I'm not so sure anymore: >root@kg-quiet# uname -a >FreeBSD kg-quiet.kg4.no 6.0-STABLE FreeBSD 6.0-STABLE #0: Thu Dec 8 >00:56:05 CET 2005 root@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET >amd64 > >root@kg-quiet# /compat/linux/bin/uname -a >Linux kg-quiet.kg4.no 2.4.2 FreeBSD 6.0-STABLE #0: Thu Dec 8 00:56:05 >CET 2005 i686 i686 i386 GNU/Linux > >This last part seems to say that linux on this machine is 32-bit? > >What is the correct answer? > > Dear Torfinn. Since summer this year I try compiling a working 64-bit capable JAVA environment! I had never luck with FBSD 6.0-RELEASE, but with one of the following 6.0-STABLEs. No clue why. These days I did a portupgrade and my jdk15 died again, impossible to compile it again. Installing Linuxulator and linux-jdk14 for bootstrapping purposes works fine, but jdk15 dies: some java vm errors occur. No chance. JAVA is very important these days and the lack of a working java environment is harsh. Can you offer us your errors and failures? Oliver --------------090101060101030804000603-- From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 11 20:19:00 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A45216A41F for ; Sun, 11 Dec 2005 20:19:00 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id C73A343D66 for ; Sun, 11 Dec 2005 20:18:59 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (ap6.matik.com.br [200.152.83.36]) by msrv.matik.com.br (8.13.4/8.13.1) with ESMTP id jBBKIxEd055880 for ; Sun, 11 Dec 2005 18:19:00 -0200 (BRST) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-amd64@freebsd.org Date: Sun, 11 Dec 2005 18:19:00 -0200 User-Agent: KMail/1.8.3 References: <20051211203747.474fb5a6.torfinn.ingolfsen@broadpark.no> <439C8512.2090602@mail.uni-mainz.de> In-Reply-To: <439C8512.2090602@mail.uni-mainz.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512111819.01138.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on msrv.matik.com.br X-Virus-Status: Clean Subject: Re: FreeBSD/amd64: is Linux 32-bit or 64-bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2005 20:19:00 -0000 On Sunday 11 December 2005 17:59, O. Hartmann wrote: > Since summer this year I try compiling a working 64-bit capable JAVA > environment! I had never luck with FBSD 6.0-RELEASE, but with one of the > following 6.0-STABLEs. No clue why. These days I did a portupgrade and > my jdk15 died again, impossible to compile it again. Installing > Linuxulator and linux-jdk14 for bootstrapping purposes works fine, but > jdk15 dies: some java vm errors occur. No chance. > > JAVA is very important these days and the lack of a working java > environment is harsh. > Hi there even if java1.4 and 1.5 of any kind (jdk, linux-jdk ...) installs smooth it= is=20 not working properly on i386 as plugin, does not matter if on 4.11, 5.4, 6= =2E0=20 R and Stable, does not matter if Gnome or Kde and Konqueror, Firefox or any= =20 other Mozilla. I compiled and configured my PCs to death ... no chance. Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 11 20:35:01 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 093F916A41F for ; Sun, 11 Dec 2005 20:35:01 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.178.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id B68BF43D49 for ; Sun, 11 Dec 2005 20:34:55 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [217.185.96.166] (manz-d9b960a6.pool.mediaWays.net [217.185.96.166]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate2.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 584053000F11; Sun, 11 Dec 2005 21:34:45 +0100 (CET) Message-ID: <439C8D64.6090300@mail.uni-mainz.de> Date: Sun, 11 Dec 2005 21:34:44 +0100 From: "O. Hartmann" User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: JoaoBR References: <20051211203747.474fb5a6.torfinn.ingolfsen@broadpark.no> <439C8512.2090602@mail.uni-mainz.de> <200512111819.01138.joao@matik.com.br> In-Reply-To: <200512111819.01138.joao@matik.com.br> Content-Type: multipart/mixed; boundary="------------030805020008050204070604" X-Virus-Scanned: by amavisd-new at uni-mainz.de X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD/amd64: is Linux 32-bit or 64-bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2005 20:35:01 -0000 This is a multi-part message in MIME format. --------------030805020008050204070604 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit JoaoBR wrote: >On Sunday 11 December 2005 17:59, O. Hartmann wrote: > > >>Since summer this year I try compiling a working 64-bit capable JAVA >>environment! I had never luck with FBSD 6.0-RELEASE, but with one of the >>following 6.0-STABLEs. No clue why. These days I did a portupgrade and >>my jdk15 died again, impossible to compile it again. Installing >>Linuxulator and linux-jdk14 for bootstrapping purposes works fine, but >>jdk15 dies: some java vm errors occur. No chance. >> >>JAVA is very important these days and the lack of a working java >>environment is harsh. >> >> >> > >Hi there >even if java1.4 and 1.5 of any kind (jdk, linux-jdk ...) installs smooth it is >not working properly on i386 as plugin, does not matter if on 4.11, 5.4, 6.0 >R and Stable, does not matter if Gnome or Kde and Konqueror, Firefox or any >other Mozilla. I compiled and configured my PCs to death ... no chance. > >Joćo > > > > > > > >A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. >Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br >_______________________________________________ >freebsd-amd64@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 >To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > > I had same problems with my i386 box at my lab. I took many attempts before jdk15 compiled correct. No chance with 6.0-RELEASE, but then with 6.0-STABLE. I it very strange. On this i386 platform, jdk15 works fine, I also installed/compiled ECLIPSE successfully and have a FireFox 1.0.X-plugin! On AMD64, ther's noc chance obtaining a working jdk15 environment! --------------030805020008050204070604-- From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 11 21:13:40 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9115516A41F for ; Sun, 11 Dec 2005 21:13:40 +0000 (GMT) (envelope-from hartzell@satchel.alerce.com) Received: from merlin.alerce.com (w094.z064001164.sjc-ca.dsl.cnc.net [64.1.164.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id D05E443D49 for ; Sun, 11 Dec 2005 21:13:39 +0000 (GMT) (envelope-from hartzell@satchel.alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id ABA4C2174; Sun, 11 Dec 2005 13:13:36 -0800 (PST) Received: from satchel.alerce.com (w092.z064001164.sjc-ca.dsl.cnc.net [64.1.164.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by merlin.alerce.com (Postfix) with ESMTP id 6F5BE215B; Sun, 11 Dec 2005 13:13:36 -0800 (PST) Received: from satchel.alerce.com (localhost [127.0.0.1]) by satchel.alerce.com (8.13.4/8.13.4) with ESMTP id jBBLDcls027576; Sun, 11 Dec 2005 13:13:38 -0800 (PST) (envelope-from hartzell@satchel.alerce.com) Received: (from hartzell@localhost) by satchel.alerce.com (8.13.4/8.13.4/Submit) id jBBLDbME027567; Sun, 11 Dec 2005 13:13:37 -0800 (PST) (envelope-from hartzell) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17308.38528.862259.201313@satchel.alerce.com> Date: Sun, 11 Dec 2005 13:13:36 -0800 To: Lars Tunkrans In-Reply-To: <439C3555.2090909@bredband.net> References: <200512082032.jB8KWbQP089454@freefall.freebsd.org> <439C3555.2090909@bredband.net> X-Mailer: VM 7.17 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-amd64@freebsd.org Subject: Re: Anyone running R 6.0 on Shuttle SN25P X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hartzell@alerce.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2005 21:13:40 -0000 Lars Tunkrans writes: > > Hi; > > Does anyone have experience of FreeBSD 6.0 Running on > the Shuttle SN25P. > I am looking for a ( silent) platform for hosting 3 large disks > ( 3 * 300-500 GB SATA RAID ) for a NFS server with Gigabit > Ethernet. > This box does have PCI Express, is that stable enough at this point ? > [...] There was some discussion a while back about a related Shuttle, the SN95G5V3. Here's a pointer to some comments by Matthew Dillon: http://leaf.dragonflybsd.org/mailarchive/users/2005-11/msg00027.html and you can search back around Nov 18 in the freebsd-current archives for a thread discussion it w/ Shuttle XPC in the subject. g. From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 11 21:30:10 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C479616A41F for ; Sun, 11 Dec 2005 21:30:10 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id E786D43D60 for ; Sun, 11 Dec 2005 21:30:09 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (ap6.matik.com.br [200.152.83.36]) by msrv.matik.com.br (8.13.4/8.13.1) with ESMTP id jBBLU9Dh058459; Sun, 11 Dec 2005 19:30:10 -0200 (BRST) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: "O. Hartmann" Date: Sun, 11 Dec 2005 19:30:11 -0200 User-Agent: KMail/1.8.3 References: <20051211203747.474fb5a6.torfinn.ingolfsen@broadpark.no> <200512111819.01138.joao@matik.com.br> <439C8D64.6090300@mail.uni-mainz.de> In-Reply-To: <439C8D64.6090300@mail.uni-mainz.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512111930.12508.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on msrv.matik.com.br X-Virus-Status: Clean Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD/amd64: is Linux 32-bit or 64-bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2005 21:30:10 -0000 On Sunday 11 December 2005 18:34, you wrote: > > On this i386 platform, jdk15 works fine, I also installed/compiled > ECLIPSE successfully and have a FireFox 1.0.X-plugin! > hehe, you say so ;) the secret is not installing it, running it is the question go here and crash your ilusion: https://office.bancobrasil.com.br/office/portal/installPLUGIN.html chose your install path, there appears c:/ but you can change it to whateve= r=20 you want so the install runs fine with konqueror and firefox , but then go to the=20 installation dir and try to run index.html (probably you got an icon on you= r=20 desktop) unless you installed the aplication dir directly in / the freebsd=20 whatever-java-jdk-or-jsk creates strange directory trees beside the app dir example you install it in ~/BB after first run of index,html it creates ~/usr/home/username/BB/...... and the second run it does not run anymore when you install it in / it tries to update the first run and stops somewhe= re=20 and gives some java applet errors this only one example, almost all https java apps do not run under FreeBSD = but=20 run fine with the same java version and same kde-version under any=20 redhat-distro so my guess this is a freebsd-java problem and not KDE but I= =20 may be wrong but for sure I believe freebsd java do not know sym-links and = do=20 not know the current dir either ... but this also is only a guess, I do not= =20 know anything about java besides that it bothers me :S Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 11 21:45:23 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1722B16A41F for ; Sun, 11 Dec 2005 21:45:23 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id D58BF43D6A for ; Sun, 11 Dec 2005 21:45:21 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IRC00597SMVDW50@osl1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Sun, 11 Dec 2005 22:49:43 +0100 (CET) Received: from kg-work.kg4.no ([80.203.92.30]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0IRC00CXRSK4Q8N1@osl1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Sun, 11 Dec 2005 22:48:05 +0100 (CET) Date: Sun, 11 Dec 2005 22:43:28 +0100 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH In-reply-to: <439C8D64.6090300@mail.uni-mainz.de> To: freebsd-amd64@freebsd.org Message-id: <20051211224328.32e3b6ef.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd5.4) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT References: <20051211203747.474fb5a6.torfinn.ingolfsen@broadpark.no> <439C8512.2090602@mail.uni-mainz.de> <200512111819.01138.joao@matik.com.br> <439C8D64.6090300@mail.uni-mainz.de> Subject: Re: FreeBSD/amd64: is Linux 32-bit or 64-bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2005 21:45:23 -0000 On Sun, 11 Dec 2005 21:34:44 +0100 "O. Hartmann" wrote: > On AMD64, ther's noc chance obtaining a working jdk15 environment! Installing Java on FreeBSD 6.0-stable / amd64 works. The problem is that the jdk15 port does not install the browser plugin. I'm currently busy doing a portupgrade of jdk15, I'll let you know how it went. -- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 11 22:50:07 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9AA3916A41F for ; Sun, 11 Dec 2005 22:50:07 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 492A943D72 for ; Sun, 11 Dec 2005 22:50:04 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IRC005AFVMPEC70@osl1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Sun, 11 Dec 2005 23:54:25 +0100 (CET) Received: from kg-work.kg4.no ([80.203.92.30]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0IRC00F11VJZIG90@osl1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Sun, 11 Dec 2005 23:52:47 +0100 (CET) Date: Sun, 11 Dec 2005 23:50:02 +0100 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH In-reply-to: <20051211224328.32e3b6ef.torfinn.ingolfsen@broadpark.no> To: freebsd-amd64@freebsd.org Message-id: <20051211235002.487f762f.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd5.4) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT References: <20051211203747.474fb5a6.torfinn.ingolfsen@broadpark.no> <439C8512.2090602@mail.uni-mainz.de> <200512111819.01138.joao@matik.com.br> <439C8D64.6090300@mail.uni-mainz.de> <20051211224328.32e3b6ef.torfinn.ingolfsen@broadpark.no> Subject: Re: FreeBSD/amd64: is Linux 32-bit or 64-bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2005 22:50:07 -0000 On Sun, 11 Dec 2005 22:43:28 +0100 Torfinn Ingolfsen wrote: > I'm currently busy doing a portupgrade of jdk15, I'll let you know > how it went. It completed without problems. Results: root@kg-quiet# uname -a FreeBSD kg-quiet.kg4.no 6.0-STABLE FreeBSD 6.0-STABLE #0: Thu Dec 8 00:56:05 CET 2005 root@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET amd64 root@kg-quiet# portversion -v | grep jdk jdk-1.5.0p2_3 = up-to-date with port linux-blackdown-jdk-1.4.2_3 = up-to-date with port linux-sun-jdk-1.4.2.10 = up-to-date with port (Don't worry about the linux-blackdown-jdk, I just installed that for testing purposes) -- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 11 22:58:41 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F88216A420 for ; Sun, 11 Dec 2005 22:58:41 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.178.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 521FA43D64 for ; Sun, 11 Dec 2005 22:58:40 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [87.193.16.115] (unknown [87.193.16.115]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate2.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 5AFFA30001DF; Sun, 11 Dec 2005 23:58:37 +0100 (CET) Message-ID: <439CAF18.3040305@mail.uni-mainz.de> Date: Sun, 11 Dec 2005 23:58:32 +0100 From: "O. Hartmann" User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Torfinn Ingolfsen References: <20051211203747.474fb5a6.torfinn.ingolfsen@broadpark.no> <439C8512.2090602@mail.uni-mainz.de> <200512111819.01138.joao@matik.com.br> <439C8D64.6090300@mail.uni-mainz.de> <20051211224328.32e3b6ef.torfinn.ingolfsen@broadpark.no> <20051211235002.487f762f.torfinn.ingolfsen@broadpark.no> In-Reply-To: <20051211235002.487f762f.torfinn.ingolfsen@broadpark.no> Content-Type: multipart/mixed; boundary="------------000605050506090801090909" X-Virus-Scanned: by amavisd-new at uni-mainz.de X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD/amd64: is Linux 32-bit or 64-bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2005 22:58:41 -0000 This is a multi-part message in MIME format. --------------000605050506090801090909 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Torfinn Ingolfsen wrote: >On Sun, 11 Dec 2005 22:43:28 +0100 >Torfinn Ingolfsen wrote: > > > >>I'm currently busy doing a portupgrade of jdk15, I'll let you know >>how it went. >> >> > >It completed without problems. Results: >root@kg-quiet# uname -a >FreeBSD kg-quiet.kg4.no 6.0-STABLE FreeBSD 6.0-STABLE #0: Thu Dec 8 >00:56:05 CET 2005 root@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET >amd64 root@kg-quiet# portversion -v | grep jdk >jdk-1.5.0p2_3 = up-to-date with port >linux-blackdown-jdk-1.4.2_3 = up-to-date with port >linux-sun-jdk-1.4.2.10 = up-to-date with port > >(Don't worry about the linux-blackdown-jdk, I just installed that for >testing purposes) > > > Ok. Tomorrow I'll try installing JDK15 again and I will report the mysterious error I alway get. As often as I try the run, I never succeed! There was only one run that succeded last month. --------------000605050506090801090909-- From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 11 23:00:07 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FC2F16A41F for ; Sun, 11 Dec 2005 23:00:07 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.178.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBD1343D69 for ; Sun, 11 Dec 2005 22:59:51 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [87.193.16.115] (unknown [87.193.16.115]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate2.zdv.Uni-Mainz.DE (Postfix) with ESMTP id B72B93000A94; Sun, 11 Dec 2005 23:59:48 +0100 (CET) Message-ID: <439CAF61.4070006@mail.uni-mainz.de> Date: Sun, 11 Dec 2005 23:59:45 +0100 From: "O. Hartmann" User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: JoaoBR References: <20051211203747.474fb5a6.torfinn.ingolfsen@broadpark.no> <200512111819.01138.joao@matik.com.br> <439C8D64.6090300@mail.uni-mainz.de> <200512111930.12508.joao@matik.com.br> In-Reply-To: <200512111930.12508.joao@matik.com.br> Content-Type: multipart/mixed; boundary="------------010707010306060903020606" X-Virus-Scanned: by amavisd-new at uni-mainz.de X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD/amd64: is Linux 32-bit or 64-bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2005 23:00:07 -0000 This is a multi-part message in MIME format. --------------010707010306060903020606 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit JoaoBR wrote: >On Sunday 11 December 2005 18:34, you wrote: > > > > > >>On this i386 platform, jdk15 works fine, I also installed/compiled >>ECLIPSE successfully and have a FireFox 1.0.X-plugin! >> >> >> > >hehe, you say so ;) >the secret is not installing it, running it is the question > >go here and crash your ilusion: > >https://office.bancobrasil.com.br/office/portal/installPLUGIN.html > >chose your install path, there appears c:/ but you can change it to whatever >you want > >so the install runs fine with konqueror and firefox , but then go to the >installation dir and try to run index.html (probably you got an icon on your >desktop) > >unless you installed the aplication dir directly in / the freebsd >whatever-java-jdk-or-jsk creates strange directory trees beside the app dir > >example >you install it in ~/BB >after first run of index,html it creates ~/usr/home/username/BB/...... >and the second run it does not run anymore > >when you install it in / it tries to update the first run and stops somewhere >and gives some java applet errors > >this only one example, almost all https java apps do not run under FreeBSD but >run fine with the same java version and same kde-version under any >redhat-distro so my guess this is a freebsd-java problem and not KDE but I >may be wrong but for sure I believe freebsd java do not know sym-links and do >not know the current dir either ... but this also is only a guess, I do not >know anything about java besides that it bothers me :S > >Joćo > > > > > > > >A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. >Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br > > I will try this tomorrow when I'm back in my lab. --------------010707010306060903020606-- From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 12 02:42:03 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62BB416A41F for ; Mon, 12 Dec 2005 02:42:03 +0000 (GMT) (envelope-from bezpieczenstwo@limeart.pl) Received: from limeart.pl (limeart.pl [195.116.22.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id E595543D4C for ; Mon, 12 Dec 2005 02:42:02 +0000 (GMT) (envelope-from bezpieczenstwo@limeart.pl) Received: from ARTUR (artur [192.168.0.3]) by limeart.pl (Postfix) with ESMTP id AE15AB242D for ; Mon, 12 Dec 2005 03:42:01 +0100 (CET) Date: Mon, 12 Dec 2005 03:41:59 +0100 From: Artur Kozak X-Mailer: The Bat! (v3.0) Professional Organization: Limeart X-Priority: 3 (Normal) Message-ID: <1475832559.20051212034159@limeart.pl> To: freebsd-amd64@freebsd.org In-Reply-To: <439875CF.5020006@jetnet.co.uk> References: <439875CF.5020006@jetnet.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: how to get more info X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Artur Kozak List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 02:42:03 -0000 Hi 8-12-2005 (19:05:03) David Reid wrote: > I'm running -STABLE and at present I'm being lucky to get more than 6 > hours uptime! The problem (and reason for this email) is to ask if there > is anything I can do to try and get more info on th crashes to help > debug and correct them. When the system goes it just reboots, no panic > or information written to any logs. It's been doing it for a while but > the last few days have seen it happening more often. > I'm running a GENERIC kernel with WITNESS enabled. I'm more than willing > to try and help find/fix the problem, but the lack of information is > stopping me from doing much! Did you set 'dumpdir' and dumpdev in /etc/rc.conf ? What NIC do you have ? I've got similiar problem on 5.4 stable because one of the NIC was realtek. I replace it with intel and now it's stable. -- Pozdrowienia, Artur Kozak From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 12 04:20:07 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 793EB16A41F for ; Mon, 12 Dec 2005 04:20:07 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9643B43D6D for ; Mon, 12 Dec 2005 04:20:05 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBC4K5G5036034 for ; Mon, 12 Dec 2005 04:20:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBC4K48J036033; Mon, 12 Dec 2005 04:20:05 GMT (envelope-from gnats) Resent-Date: Mon, 12 Dec 2005 04:20:05 GMT Resent-Message-Id: <200512120420.jBC4K48J036033@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, Roger Marquis Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7269A16A41F for ; Mon, 12 Dec 2005 04:14:00 +0000 (GMT) (envelope-from marquis@roble.com) Received: from mx5.roble.com (mx5.roble.com [206.40.34.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 368FF43D60 for ; Mon, 12 Dec 2005 04:14:00 +0000 (GMT) (envelope-from marquis@roble.com) Message-Id: <20051212041358.B73E127EC66@mx7.roble.com> Date: Sun, 11 Dec 2005 20:13:58 -0800 (PST) From: Roger Marquis To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: amd64/90267: nmap fails under amd64 5.4-REL X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Roger Marquis List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 04:20:07 -0000 >Number: 90267 >Category: amd64 >Synopsis: nmap fails under amd64 5.4-REL >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Dec 12 04:20:04 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Roger Marquis >Release: FreeBSD 5.4-RELEASE-p4 amd64 >Organization: Roble Systems (http://www.roble.com/) >Environment: FreeBSD 5.4-RELEASE-p4 amd64 tcsh IBM e325 >Description: nmap-3.93 returns the following error: Starting nmap 3.93 ( http://www.insecure.org/nmap/ ) at 2005-12-11 20:09 PST getinterfaces: Failed to open ethernet interface (bge0) QUITTING! >How-To-Repeat: nmap >Fix: revert to previous version >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 12 08:31:20 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8DE016A41F for ; Mon, 12 Dec 2005 08:31:20 +0000 (GMT) (envelope-from valery@vslash.com) Received: from mail.vslash.com (bgl93-1-82-67-185-6.fbx.proxad.net [82.67.185.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DEBE43D5F for ; Mon, 12 Dec 2005 08:31:19 +0000 (GMT) (envelope-from valery@vslash.com) Received: from [192.168.0.22] (oxe.intranet.vslash.com [192.168.0.22]) by mail.vslash.com (Postfix) with ESMTP id 7C1FC8444D for ; Mon, 12 Dec 2005 09:31:58 +0100 (CET) Message-ID: <439D354D.1000007@vslash.com> Date: Mon, 12 Dec 2005 09:31:09 +0100 From: Valery User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.7) Gecko/20050420 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Supported Hardwre : Sun X2100 ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 08:31:21 -0000 Dear all, a simple question, is the recent Sun X2100 Servers family (AMD Opteron 148,152,175 / SATA) planned to be supported, or simply, does FreeBSD 6.x run whithout trouble on this kind of system ? Thanks for your attention, v/ From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 12 11:02:03 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2A0C16A420 for ; Mon, 12 Dec 2005 11:02:02 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E5E543D6A for ; Mon, 12 Dec 2005 11:01:57 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBCB1uwC064540 for ; Mon, 12 Dec 2005 11:01:56 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBCB1tl2064534 for freebsd-amd64@freebsd.org; Mon, 12 Dec 2005 11:01:55 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 12 Dec 2005 11:01:55 GMT Message-Id: <200512121101.jBCB1tl2064534@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 11:02:03 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2005/08/09] amd64/84693 amd64 Keyboard not recognized during first step o [2005/11/17] amd64/89202 amd64 [ufs] [panic] Kernel crash when accessing 2 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59714 amd64 device timeout and ad0: WARNING - WRITE_D o [2004/07/28] amd64/69704 amd64 ext2/ext3 unstable in amd64 o [2004/07/28] amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o [2004/09/07] amd64/71471 amd64 Can not install 5.3beta3/amd64 on IBM eSe o [2004/09/12] amd64/71644 amd64 [panic] amd64 5.3-BETA4 crash when heavy o [2004/10/28] amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was see o [2004/10/30] amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdo o [2004/11/01] amd64/73369 amd64 on-board firewire unreliable with Asus K8 o [2004/11/07] amd64/73650 amd64 5.3-release panics on boot o [2004/11/10] amd64/73775 amd64 Kernel panic (trap 12) when booting with o [2004/11/16] amd64/74014 amd64 5.3-RELEASE-AMD64 freezes on boot during o [2004/12/05] amd64/74747 amd64 System panic on shutdown when process wil o [2004/12/18] amd64/75209 amd64 5.3-Release panics on attempted boot from o [2004/12/23] amd64/75417 amd64 ACPI: SATA Hard-disk o [2005/01/12] amd64/76136 amd64 system halts before reboot o [2005/01/17] amd64/76336 amd64 racoon/setkey -D cases instant "Fatal Tra o [2005/02/02] amd64/77011 amd64 consisten 5.3-p5 make crash on installwor o [2005/02/23] amd64/77949 amd64 Pb boot FreeBSD 64 o [2005/03/04] amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/p o [2005/03/07] amd64/78558 amd64 installation o [2005/03/14] amd64/78848 amd64 [sis] sis driver on FreeBSD 5.x does not o [2005/04/12] amd64/79813 amd64 Will not install/run on amd64 nForce 4 pl o [2005/04/19] amd64/80114 amd64 kldload snd_ich causes interrupt storm wh o [2005/05/06] amd64/80691 amd64 amd64 kernel hangs on load o [2005/05/14] amd64/81037 amd64 SATA problem o [2005/05/28] amd64/81602 amd64 SATA crashes with parallel pcm access o [2005/06/09] amd64/82071 amd64 incorrect -march's parameter to build 32b o [2005/06/19] amd64/82425 amd64 [fxp] fxp0: device timeout, fxp interface o [2005/06/23] amd64/82555 amd64 Kernel Panic - after i connect to my "amd o [2005/07/05] amd64/83005 amd64 Memory Occupied during installation of th o [2005/08/12] amd64/84832 amd64 Installation crashes just at boot AMD64/ o [2005/08/14] amd64/84930 amd64 [msdosfs] something wrong with msdosfs on o [2005/08/29] amd64/85431 amd64 AMD64 has short but temporary freezes (ha o [2005/08/29] amd64/85451 amd64 [hang] 6.0-BETA3 lockups on AMD64 (PREEMP o [2005/09/13] amd64/86080 amd64 [radeon] [hang] radeon DRI causes system o [2005/09/23] amd64/86503 amd64 [atapicam] [panic] k3b crash the system l o [2005/10/09] amd64/87156 amd64 First Installation: Kernel crashes o [2005/10/11] amd64/87258 amd64 [smp] [boot] cannot boot with SMP and Are o [2005/10/12] amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powe o [2005/10/12] amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD a [2005/10/12] amd64/87328 amd64 [boot] BTX halted error o [2005/10/12] amd64/87348 amd64 amd64+smp+startkde always crashing o [2005/10/15] amd64/87472 amd64 I downloaded 5.4 and went to install it, o [2005/10/16] amd64/87514 amd64 6.0-CURRENT freezes machine using >4GB on o [2005/10/19] amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron o [2005/10/20] amd64/87748 amd64 can't initialize X o [2005/10/25] amd64/87977 amd64 [busdma] [panic] amd64 busdma dflt_lock c o [2005/10/31] amd64/88299 amd64 swapcontext fails with errno 0 o [2005/11/06] amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not b f [2005/11/09] amd64/88746 amd64 Buffer problem with SSH2 under amd64 arch o [2005/11/10] amd64/88790 amd64 kernel panic on first boot (after the Fre o [2005/11/24] amd64/89501 amd64 System crashes on install using ftp on lo o [2005/11/24] amd64/89503 amd64 Cant Boot Installation Disk o [2005/11/25] amd64/89546 amd64 [geom] GEOM error o [2005/11/25] amd64/89549 amd64 [amd64] nve timeouts on 6.0-release o [2005/11/25] amd64/89550 amd64 [amd64] sym0: VTOBUS failed (6.0 Release) o [2005/12/05] amd64/89968 amd64 [ata] Asus A8N-E MediaShield RAID problem 57 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/01/11] amd64/61209 amd64 ppc0: cannot reserve I/O port range o [2004/02/21] amd64/63188 amd64 [ti] ti(4) broken on amd64 o [2004/07/28] amd64/69705 amd64 IPC problem (msq_queues) o [2004/12/02] amd64/74608 amd64 [mpt] [hang] mpt hangs 5 minutes when boo o [2004/12/07] amd64/74811 amd64 [nfs] df, nfs mount, negative Avail -> 32 o [2004/12/13] ports/75015 amd64 cvsup on amd64 coredumps with either runs o [2005/03/17] amd64/78954 amd64 kerberos 5 failed to build o [2005/05/16] amd64/81089 amd64 [bge] [patch] FreeBSD 5.4 released versio o [2005/06/18] amd64/82399 amd64 MSI K8N Neo4 Platinium is not supported o [2005/08/07] amd64/84652 amd64 kbdmap -r dumps core o [2005/08/20] amd64/85144 amd64 Asus K8S-MX mobo, integ LAN not recognize o [2005/09/06] amd64/85812 amd64 "Rebooting..." on serial console appears o [2005/09/07] amd64/85820 amd64 1.5 times slower performance with SCHED_U o [2005/10/23] amd64/87882 amd64 emu10k1 and APCI on amd64 is just noisy o [2005/11/09] amd64/88730 amd64 kernel panics during booting from the ins o [2005/12/12] amd64/90267 amd64 nmap fails under amd64 5.4-REL 16 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 12 12:54:38 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 722F816A41F for ; Mon, 12 Dec 2005 12:54:38 +0000 (GMT) (envelope-from arnuld.fraser@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00C4B43D5E for ; Mon, 12 Dec 2005 12:54:37 +0000 (GMT) (envelope-from arnuld.fraser@gmail.com) Received: by xproxy.gmail.com with SMTP id t15so959807wxc for ; Mon, 12 Dec 2005 04:54:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=cnQ0PtFDKd0/c8JJWeLpg75e2Yif0W2IIrr8KxvbjHo0bfsQ46hOORGS3E6F2l4sIGwwA5wTP9QMTURPAqF3Y+jvpfqQgFqieNsoZwe744/9qFV/wbQH5KRkWmspu2i+37XsGhLs0GvY77eUpNo1gCfJpRdqL35ZTTeDoys7vIo= Received: by 10.70.65.17 with SMTP id n17mr9420670wxa; Mon, 12 Dec 2005 04:54:36 -0800 (PST) Received: by 10.70.72.19 with HTTP; Mon, 12 Dec 2005 04:54:36 -0800 (PST) Message-ID: <449a85a0512120454l50c19a85h8b07473d8cc72a25@mail.gmail.com> Date: Mon, 12 Dec 2005 18:24:36 +0530 From: arnuld To: FreeBSD_amd64_ml MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: is my hardware supporteded? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 12:54:38 -0000 aGksCgogICAgICBJIGhhdmUgcHJvYmxlbXMgY29uZmlndXJpbmcgWC13aW5kb3cgc3lzdGVtLiBJ IG9ubHkgd2FudCB0byBrbm93CndoZXRoZXIgbXkgaGFyZHdhcmUgaXMKICAgICAgc3VwcG9ydGVk IG9yIG5vdAoKCkkgaGF2ZSBGcmVlQlNEIDUuNCBDRHMgZm9yIHg4Ni4KMS4pIGhlcmUgaXMgbXkg YXJjaGl0ZWN0dXJlOgoKICAgICAgICAgICAgICAgICBpLikgICAgICBBTUQ2NCAtPiBwcm9jZXNz b3IKCiAgICAgICAgICAgICAgICAgaWkuKSAgICAgQVNVUyBLOFYtTVggLT4gbW90aGVyYm9hcmQK CiAgICAgICAgICAgICAgICAgICAgICAgICAgY2hpcHNldDogICAgICAgICAgVklBSzhNODAwCiAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFZJQSBWVDgyMzdS CgogICAgICAgICAgICAgICAgIGlpaS4pICAgIExHIDE3JycgU3R1ZGlvd29ya3MgNzc1TiAtPiBt b25pdG9yCiAgICAgICAgICAgICAgICAgICAgICAgICBIb3JpelN5bnMgPSAzMC03MCBrSHoKICAg ICAgICAgICAgICAgICAgICAgICAgIFZlcnRzeW5jICA9IDUwLTE2MCBIegogICAgICAgICAgICAg ICAgICAgICAgICAgUmVzb2x1dGlvbiBNYXguID0gMTI4MHgxMDI0IEAgNjAgSHoKCnRoYW5rcwoK LS0KInRoZSBncmVhdCBpbnRlbGxlY3R1YWxzIgo= From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 12 14:22:48 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E21616A41F for ; Mon, 12 Dec 2005 14:22:48 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr12.xs4all.nl (smtp-vbr12.xs4all.nl [194.109.24.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CBD543D68 for ; Mon, 12 Dec 2005 14:22:46 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr12.xs4all.nl (8.13.3/8.13.3) with ESMTP id jBCEMibw076107; Mon, 12 Dec 2005 15:22:44 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 55D45B820; Mon, 12 Dec 2005 15:22:44 +0100 (CET) Date: Mon, 12 Dec 2005 15:22:44 +0100 From: Roland Smith To: arnuld Message-ID: <20051212142244.GA71789@slackbox.xs4all.nl> Mail-Followup-To: arnuld , freebsd-amd64@freebsd.org References: <449a85a0512120454l50c19a85h8b07473d8cc72a25@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WIyZ46R2i8wDzkSu" Content-Disposition: inline In-Reply-To: <449a85a0512120454l50c19a85h8b07473d8cc72a25@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-amd64@freebsd.org Subject: Re: is my hardware supporteded? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 14:22:48 -0000 --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 12, 2005 at 06:24:36PM +0530, arnuld wrote: > I have FreeBSD 5.4 CDs for x86. > 1.) here is my architecture: >=20 > i.) AMD64 -> processor No problem, you can run both amd64 and x86 on this. > ii.) ASUS K8V-MX -> motherboard >=20 > chipset: VIAK8M800 > VIA VT8237R I'm not sure if the onboard ethernet chip is supported. The onboard video should be supported by the via driver, _but that's only on x86, not amd64!_ > iii.) LG 17'' Studioworks 775N -> monitor > HorizSyns =3D 30-70 kHz > Vertsync =3D 50-160 Hz > Resolution Max. =3D 1280x1024 @ 60 Hz Any recent monitor should work. You haven't told us if you have a seperate graphics card..=20 Roland --=20 R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt --WIyZ46R2i8wDzkSu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDnYe0EnfvsMMhpyURApeLAJwKVi2PBrCe8MUPDNAwWy1XPR+FxQCfbZ/C 103gglMte3pfC4ANDZvUA8c= =gL7I -----END PGP SIGNATURE----- --WIyZ46R2i8wDzkSu-- From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 12 17:00:32 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CC9D16A420 for ; Mon, 12 Dec 2005 17:00:32 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.178.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7564843D5A for ; Mon, 12 Dec 2005 17:00:17 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [134.93.180.218] (edda.Physik.Uni-Mainz.DE [134.93.180.218]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate2.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 5CC83300041E for ; Mon, 12 Dec 2005 18:00:14 +0100 (CET) Message-ID: <439DAC66.3020104@mail.uni-mainz.de> Date: Mon, 12 Dec 2005 17:59:18 +0100 From: "O. Hartmann" Organization: Institut =?UTF-8?B?ZsO8ciBHZW9waHlzaWs=?= User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de Subject: PCIe-8x usage on ASUS SLI boards X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 17:00:32 -0000 Hello. My question may be a little bit cranky, but having low cost server in mind it may be of relevance. Is it possible to use the second 8x SLI slot on ASUS A8n-SLI Deluxe/Premium as a normal PCIe-8x slot with SLI enabled? Server systems do not utilize high graphics throughput, so I can live with a PEG card in 8x mode. But it would be fine if I could use a 8x-lane SATA-II or SCSI RAID card in the second PEG slot with 8x-lane support. Thanks in advance, Oliver From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 12 17:59:32 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E782016A420 for ; Mon, 12 Dec 2005 17:59:32 +0000 (GMT) (envelope-from martin@gneto.com) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7900743D90 for ; Mon, 12 Dec 2005 17:59:09 +0000 (GMT) (envelope-from martin@gneto.com) Received: from ironport.bredband.com ([195.54.107.82] [195.54.107.82]) by mxfep01.bredband.com with ESMTP id <20051212175907.XISG676.mxfep01.bredband.com@ironport.bredband.com> for ; Mon, 12 Dec 2005 18:59:07 +0100 Received: from ua-83-227-181-30.cust.bredbandsbolaget.se ([83.227.181.30]) by ironport.bredband.com with ESMTP; 12 Dec 2005 18:59:30 +0100 X-BrightmailFiltered: true X-IronPort-AV: i="3.99,244,1131318000"; d="scan'208"; a="17590765:sNHT35099010" Received: from [192.168.10.11] (euklides.gneto.com [192.168.10.11]) by ua-83-227-181-30.cust.bredbandsbolaget.se (Postfix) with ESMTP id 3B715678DC; Mon, 12 Dec 2005 18:59:07 +0100 (CET) Message-ID: <439DBA6A.6070804@gneto.com> Date: Mon, 12 Dec 2005 18:59:06 +0100 From: Martin Nilsson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "O. Hartmann" References: <439DAC66.3020104@mail.uni-mainz.de> In-Reply-To: <439DAC66.3020104@mail.uni-mainz.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: PCIe-8x usage on ASUS SLI boards X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 17:59:33 -0000 O. Hartmann wrote: > Hello. > My question may be a little bit cranky, but having low cost server in > mind it may be of relevance. > > Is it possible to use the second 8x SLI slot on ASUS A8n-SLI > Deluxe/Premium as a normal PCIe-8x slot with SLI enabled? I don't know about the SLI but on the A8N-E it is possible to use the PCI-e16x slot for RAID and the PCI-e2x stot for graphics. In the end I choose a PCI graphics card instead as it produces less heat and I have no use for graphics at all. /Martin From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 12 18:01:14 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2604416A41F for ; Mon, 12 Dec 2005 18:01:14 +0000 (GMT) (envelope-from dev@unixdaemon.org) Received: from whisk.dreamhost.com (whisk.dreamhost.com [205.196.208.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id E00C743D6D for ; Mon, 12 Dec 2005 18:01:13 +0000 (GMT) (envelope-from dev@unixdaemon.org) Received: from dracula (cpe-24-24-83-9.stny.res.rr.com [24.24.83.9]) by whisk.dreamhost.com (Postfix) with ESMTP id 0B6217F01E for ; Mon, 12 Dec 2005 10:01:10 -0800 (PST) From: Dev Tugnait To: freebsd-amd64@freebsd.org Content-Type: text/plain Date: Mon, 12 Dec 2005 13:01:08 -0500 Message-Id: <1134410468.12592.6.camel@dracula> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: MotherBoard Chipset Woes X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dev@unixdaemon.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 18:01:14 -0000 I am still deciding on what mobo to get for my Athlon X2. I have seen the supported motherboards list, my question being I was looking into the DFI LANPARTY UT nF4 Ultra-D ATX AMD Motherboard. The problem is Onboard LAN LAN Chipset Vitesse VSC8201 Second LAN Chipset Marvell 88E8001 I see neither in the supported hardware list. So is this supported? Problem is most newer boards use Marvell, if its not supported is it perhaps in current or will be in future releases? I have also seen an ATI Express 200 Chipset Mobo but I have heard stay away from ati due to unsupported hardware. Either via or nf4 chipset. If I go nf4 the DFI board seems cheap and in my budget. Any experience with these boards? Thanks -- Dev Tugnait From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 12 18:06:04 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9AE716A41F for ; Mon, 12 Dec 2005 18:06:04 +0000 (GMT) (envelope-from martin@mullet.se) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CFDB43D73 for ; Mon, 12 Dec 2005 18:05:54 +0000 (GMT) (envelope-from martin@mullet.se) Received: from ua-83-227-181-30.cust.bredbandsbolaget.se ([83.227.181.30] [83.227.181.30]) by mxfep01.bredband.com with ESMTP id <20051212180549.XLKW676.mxfep01.bredband.com@ua-83-227-181-30.cust.bredbandsbolaget.se>; Mon, 12 Dec 2005 19:05:49 +0100 Received: from [192.168.10.11] (euklides.gneto.com [192.168.10.11]) by ua-83-227-181-30.cust.bredbandsbolaget.se (Postfix) with ESMTP id E7521678DC; Mon, 12 Dec 2005 19:05:48 +0100 (CET) Message-ID: <439DBBFC.90303@mullet.se> Date: Mon, 12 Dec 2005 19:05:48 +0100 From: Martin Nilsson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tomas Randa , freebsd-amd64@freebsd.org References: <43760926.3090604@hosting50.cz> In-Reply-To: <43760926.3090604@hosting50.cz> Content-Type: multipart/mixed; boundary="------------090701070400070803010308" Cc: Subject: Re: ServerWorks HT1000 experience? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 18:06:05 -0000 This is a multi-part message in MIME format. --------------090701070400070803010308 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Tomas Randa wrote: > Hello! > > I would buy new SuperMicro motherboard H8SSL-i / > http://www.supermicro.com/Aplus/motherboard/Opteron/HT1000/H8SSL-i.cfm / > based on ServerWorks HT1000 Chipset. Is anybody here who tested these > new chipsets HT1000 / HT2000 with FreeBSD ? > Thanks for your answers. I have just installed 6.0/amd64 on a H8SSL-i and it seems to work. Dmesg is attached. The SATA controller is usable in emulation mode, don't be fooled by the 33MB/s message, it is bogus - the drive operates at full speed. /Martin -- Martin Nilsson, CTO & Founder, Mullet Scandinavia AB, Malmö, SWEDEN E-mail: martin@mullet.se, Phone: +46-(0)708-606170, Web: www.mullet.se Our business is well engineered servers optimised for FreeBSD & Linux --------------090701070400070803010308 Content-Type: text/plain; name="H8SSLi-FreeBSD-6.0.dmesg" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="H8SSLi-FreeBSD-6.0.dmesg" Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-RELEASE #0: Wed Nov 2 19:07:38 UTC 2005 root@rat.samsco.home:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3200+ (1995.01-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20ff0 Stepping = 0 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800,LM,3DNow+,3DNow> real memory = 1073676288 (1023 MB) avail memory = 1021038592 (973 MB) acpi0: on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) pci_link0: irq 0 on acpi0 pci_link1: irq 0 on acpi0 pci_link2: irq 0 on acpi0 pci_link3: irq 10 on acpi0 pci_link4: irq 0 on acpi0 pci_link5: irq 0 on acpi0 pci_link6: irq 0 on acpi0 pci_link7: irq 0 on acpi0 pci_link8: irq 5 on acpi0 pci_link9: irq 9 on acpi0 pci_link10: irq 0 on acpi0 pci_link11: irq 0 on acpi0 pci_link12: irq 0 on acpi0 pci_link13: irq 0 on acpi0 pci_link14: irq 0 on acpi0 pci_link15: irq 0 on acpi0 pci_link16: irq 0 on acpi0 pci_link17: irq 0 on acpi0 pci_link18: irq 0 on acpi0 pci_link19: irq 0 on acpi0 pci_link20: irq 0 on acpi0 pci_link21: irq 0 on acpi0 pci_link22: irq 0 on acpi0 pci_link23: irq 0 on acpi0 pci_link24: irq 0 on acpi0 pci_link25: irq 0 on acpi0 pci_link26: irq 0 on acpi0 pci_link27: irq 0 on acpi0 pci_link28: irq 0 on acpi0 pci_link29: irq 0 on acpi0 pci_link30: irq 0 on acpi0 pci_link31: irq 10 on acpi0 pci_link32: irq 11 on acpi0 acpi0: reservation of 540, 20 (4) failed acpi0: reservation of 500, 20 (4) failed acpi0: reservation of 560, 20 (4) failed Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: at device 13.0 on pci1 pci2: on pcib2 bge0: mem 0xfc9d0000-0xfc9dffff irq 5 at device 3.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:30:48:57:13:80 bge1: mem 0xfc9e0000-0xfc9effff irq 9 at device 3.1 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:30:48:57:13:81 atapci0: port 0xb080-0xb087,0xb000-0xb003,0xac00-0xac07,0xa880-0xa883,0xa800-0xa80f mem 0xfcafe000-0xfcafffff irq 11 at device 14.0 on pci1 ata2: on atapci0 ata3: on atapci0 atapci1: port 0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb807,0xb480-0xb483,0xb400-0xb40f irq 11 at device 14.1 on pci1 ata4: on atapci1 ata5: on atapci1 atapci2: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 2.1 on pci0 ata0: on atapci2 ata1: on atapci2 isab0: at device 2.2 on pci0 isa0: on isab0 pci0: at device 2.4 (no driver attached) pci0: at device 2.5 (no driver attached) pci0: at device 2.6 (no driver attached) ohci0: port 0xd400-0xd4ff mem 0xfebf8000-0xfebf8fff irq 10 at device 3.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ohci1: port 0xd800-0xd8ff mem 0xfebf9000-0xfebf9fff irq 10 at device 3.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ehci0: port 0xe800-0xe8ff mem 0xfebfa000-0xfebfafff irq 10 at device 3.2 on pci0 ehci0: [GIANT-LOCKED] usb2: EHCI version 1.0 usb2: companion controllers, 2 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: (0x1166) EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 4 ports with 4 removable, self powered pci0: at device 5.0 (no driver attached) acpi_button0: on acpi0 acpi_button1: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: No FDOUT register! device_attach: fdc0 attach returned 6 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: No FDOUT register! device_attach: fdc0 attach returned 6 orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xc9fff,0xca000-0xcb7ff,0xcb800-0xccfff,0xcd000-0xcdfff on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1995011331 Hz quality 800 Timecounters tick every 1.000 msec md0: Preloaded image 4194304 bytes at 0xffffffff80970f68 acd0: CDRW at ata0-master UDMA33 ad4: 157066MB at ata2-master UDMA33 Trying to mount root from ufs:/dev/md0 Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...3 1 0 0 done All buffers synced. Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-RELEASE #0: Wed Nov 2 19:07:38 UTC 2005 root@rat.samsco.home:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3200+ (1995.02-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20ff0 Stepping = 0 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800,LM,3DNow+,3DNow> real memory = 1073676288 (1023 MB) avail memory = 1025220608 (977 MB) acpi0: on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) pci_link0: irq 0 on acpi0 pci_link1: irq 0 on acpi0 pci_link2: irq 0 on acpi0 pci_link3: irq 10 on acpi0 pci_link4: irq 0 on acpi0 pci_link5: irq 0 on acpi0 pci_link6: irq 0 on acpi0 pci_link7: irq 0 on acpi0 pci_link8: irq 5 on acpi0 pci_link9: irq 9 on acpi0 pci_link10: irq 0 on acpi0 pci_link11: irq 0 on acpi0 pci_link12: irq 0 on acpi0 pci_link13: irq 0 on acpi0 pci_link14: irq 0 on acpi0 pci_link15: irq 0 on acpi0 pci_link16: irq 0 on acpi0 pci_link17: irq 0 on acpi0 pci_link18: irq 0 on acpi0 pci_link19: irq 0 on acpi0 pci_link20: irq 0 on acpi0 pci_link21: irq 0 on acpi0 pci_link22: irq 0 on acpi0 pci_link23: irq 0 on acpi0 pci_link24: irq 0 on acpi0 pci_link25: irq 0 on acpi0 pci_link26: irq 0 on acpi0 pci_link27: irq 0 on acpi0 pci_link28: irq 0 on acpi0 pci_link29: irq 0 on acpi0 pci_link30: irq 0 on acpi0 pci_link31: irq 10 on acpi0 pci_link32: irq 11 on acpi0 acpi0: reservation of 540, 20 (4) failed acpi0: reservation of 500, 20 (4) failed acpi0: reservation of 560, 20 (4) failed Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: at device 13.0 on pci1 pci2: on pcib2 bge0: mem 0xfc9d0000-0xfc9dffff irq 5 at device 3.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:30:48:57:13:80 bge1: mem 0xfc9e0000-0xfc9effff irq 9 at device 3.1 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:30:48:57:13:81 atapci0: port 0xb080-0xb087,0xb000-0xb003,0xac00-0xac07,0xa880-0xa883,0xa800-0xa80f mem 0xfcafe000-0xfcafffff irq 11 at device 14.0 on pci1 ata2: on atapci0 ata3: on atapci0 atapci1: port 0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb807,0xb480-0xb483,0xb400-0xb40f irq 11 at device 14.1 on pci1 ata4: on atapci1 ata5: on atapci1 atapci2: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 2.1 on pci0 ata0: on atapci2 ata1: on atapci2 isab0: at device 2.2 on pci0 isa0: on isab0 pci0: at device 2.4 (no driver attached) pci0: at device 2.5 (no driver attached) pci0: at device 2.6 (no driver attached) ohci0: port 0xd400-0xd4ff mem 0xfebf8000-0xfebf8fff irq 10 at device 3.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ohci1: port 0xd800-0xd8ff mem 0xfebf9000-0xfebf9fff irq 10 at device 3.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ehci0: port 0xe800-0xe8ff mem 0xfebfa000-0xfebfafff irq 10 at device 3.2 on pci0 ehci0: [GIANT-LOCKED] usb2: EHCI version 1.0 usb2: companion controllers, 2 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: (0x1166) EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 4 ports with 4 removable, self powered pci0: at device 5.0 (no driver attached) acpi_button0: on acpi0 acpi_button1: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: No FDOUT register! device_attach: fdc0 attach returned 6 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: No FDOUT register! device_attach: fdc0 attach returned 6 orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xc9fff,0xca000-0xcb7ff,0xcb800-0xccfff,0xcd000-0xcdfff on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1995017931 Hz quality 800 Timecounters tick every 1.000 msec acd0: CDRW at ata0-master UDMA33 ad4: 157066MB at ata2-master UDMA33 Trying to mount root from ufs:/dev/ad4s1a stray irq7 stray irq7 stray irq7 too many stray irq 7's: not logging anymore --------------090701070400070803010308-- From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 12 19:28:51 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 30F8F16A423 for ; Mon, 12 Dec 2005 19:28:51 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66E0A43D67 for ; Mon, 12 Dec 2005 19:28:48 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3660102 for multiple; Mon, 12 Dec 2005 14:30:54 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jBCJSTM5012946; Mon, 12 Dec 2005 14:28:37 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Mon, 12 Dec 2005 13:57:44 -0500 User-Agent: KMail/1.8.2 References: <20051211203747.474fb5a6.torfinn.ingolfsen@broadpark.no> In-Reply-To: <20051211203747.474fb5a6.torfinn.ingolfsen@broadpark.no> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512121357.45468.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Subject: Re: FreeBSD/amd64: is Linux 32-bit or 64-bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 19:28:51 -0000 On Sunday 11 December 2005 02:37 pm, Torfinn Ingolfsen wrote: > This last part seems to say that linux on this machine is 32-bit? > > What is the correct answer? It runs Linux/i386 (i.e. 32-bit) binaries only currently. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 12 19:28:56 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1177C16A424; Mon, 12 Dec 2005 19:28:56 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82E8143D60; Mon, 12 Dec 2005 19:28:51 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3660106 for multiple; Mon, 12 Dec 2005 14:30:56 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jBCJSTM6012946; Mon, 12 Dec 2005 14:28:40 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org, Roger Marquis Date: Mon, 12 Dec 2005 13:58:22 -0500 User-Agent: KMail/1.8.2 References: <20051212041358.B73E127EC66@mx7.roble.com> In-Reply-To: <20051212041358.B73E127EC66@mx7.roble.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512121358.24042.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: amd64/90267: nmap fails under amd64 5.4-REL X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 19:28:56 -0000 On Sunday 11 December 2005 11:13 pm, Roger Marquis wrote: > >Number: 90267 > >Category: amd64 > >Synopsis: nmap fails under amd64 5.4-REL > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible: freebsd-amd64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Mon Dec 12 04:20:04 GMT 2005 > >Closed-Date: > >Last-Modified: > >Originator: Roger Marquis > >Release: FreeBSD 5.4-RELEASE-p4 amd64 > >Organization: > > Roble Systems (http://www.roble.com/) > > >Environment: > > FreeBSD 5.4-RELEASE-p4 amd64 tcsh IBM e325 > > >Description: > > nmap-3.93 returns the following error: > Starting nmap 3.93 ( http://www.insecure.org/nmap/ ) at 2005-12-11 20:09 > PST getinterfaces: Failed to open ethernet interface (bge0) > QUITTING! > > >How-To-Repeat: > > nmap Are you running it as root? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 12 19:30:12 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 162F316A439 for ; Mon, 12 Dec 2005 19:30:12 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5430743D69 for ; Mon, 12 Dec 2005 19:30:10 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBCJUAKN004318 for ; Mon, 12 Dec 2005 19:30:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBCJUAtf004315; Mon, 12 Dec 2005 19:30:10 GMT (envelope-from gnats) Resent-Date: Mon, 12 Dec 2005 19:30:10 GMT Resent-Message-Id: <200512121930.jBCJUAtf004315@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, Max Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA74D16A423 for ; Mon, 12 Dec 2005 19:28:54 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D5B743D5A for ; Mon, 12 Dec 2005 19:28:52 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id jBCJSoPd038671 for ; Mon, 12 Dec 2005 19:28:50 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id jBCJSoKL038670; Mon, 12 Dec 2005 19:28:50 GMT (envelope-from nobody) Message-Id: <200512121928.jBCJSoKL038670@www.freebsd.org> Date: Mon, 12 Dec 2005 19:28:50 GMT From: Max To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/90303: Marvell 88E8111 Gigabit LAN PHY driver X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 19:30:12 -0000 >Number: 90303 >Category: amd64 >Synopsis: Marvell 88E8111 Gigabit LAN PHY driver >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Mon Dec 12 19:30:09 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Max >Release: 5.4 Amd 64 >Organization: Entrend >Environment: >Description: Device is not supported by if_sk driver >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 12 19:30:14 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0AF5E16A43A for ; Mon, 12 Dec 2005 19:30:14 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B4B943D53 for ; Mon, 12 Dec 2005 19:30:13 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBCJUDsq004369 for ; Mon, 12 Dec 2005 19:30:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBCJUDvf004368; Mon, 12 Dec 2005 19:30:13 GMT (envelope-from gnats) Date: Mon, 12 Dec 2005 19:30:13 GMT Message-Id: <200512121930.jBCJUDvf004368@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: John Baldwin Cc: Subject: Re: amd64/90267: nmap fails under amd64 5.4-REL X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Baldwin List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 19:30:14 -0000 The following reply was made to PR amd64/90267; it has been noted by GNATS. From: John Baldwin To: freebsd-amd64@freebsd.org, Roger Marquis Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: amd64/90267: nmap fails under amd64 5.4-REL Date: Mon, 12 Dec 2005 13:58:22 -0500 On Sunday 11 December 2005 11:13 pm, Roger Marquis wrote: > >Number: 90267 > >Category: amd64 > >Synopsis: nmap fails under amd64 5.4-REL > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible: freebsd-amd64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Mon Dec 12 04:20:04 GMT 2005 > >Closed-Date: > >Last-Modified: > >Originator: Roger Marquis > >Release: FreeBSD 5.4-RELEASE-p4 amd64 > >Organization: > > Roble Systems (http://www.roble.com/) > > >Environment: > > FreeBSD 5.4-RELEASE-p4 amd64 tcsh IBM e325 > > >Description: > > nmap-3.93 returns the following error: > Starting nmap 3.93 ( http://www.insecure.org/nmap/ ) at 2005-12-11 20:09 > PST getinterfaces: Failed to open ethernet interface (bge0) > QUITTING! > > >How-To-Repeat: > > nmap Are you running it as root? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 12 21:24:16 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC72F16A41F for ; Mon, 12 Dec 2005 21:24:16 +0000 (GMT) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3915843D82 for ; Mon, 12 Dec 2005 21:24:10 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id 45810B814 for ; Mon, 12 Dec 2005 16:24:07 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <439D354D.1000007@vslash.com> References: <439D354D.1000007@vslash.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <7396D2F5-A7AE-4D57-A05B-11743F2F1FAD@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Mon, 12 Dec 2005 16:24:06 -0500 To: freebsd-amd64 List X-Mailer: Apple Mail (2.746.2) Subject: Re: Supported Hardwre : Sun X2100 ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 21:24:16 -0000 On Dec 12, 2005, at 3:31 AM, Valery wrote: > Dear all, > a simple question, is the recent Sun X2100 Servers > family (AMD Opteron 148,152,175 / SATA) planned to be > supported, or simply, does FreeBSD 6.x run whithout > trouble on this kind of system ? There are reports it boots on NetBSD and OpenBSD. I'm awaiting an appointment at the local Sun "lab" to test it out with FreeBSD. By the looks of the dmesg output from Net/Open BSD it *should* work with FreeBSD although one of the ethernet interfaces is nvidia which may not be 100% optimal/stable. I'm planning to plug in an extra intel NIC to make up for that since I need 2 NICs. From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 12 21:48:28 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24C3516A41F for ; Mon, 12 Dec 2005 21:48:28 +0000 (GMT) (envelope-from lists@nabble.com) Received: from talk.nabble.com (www.nabble.com [72.21.53.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id E12A143D7E for ; Mon, 12 Dec 2005 21:48:25 +0000 (GMT) (envelope-from lists@nabble.com) Received: from localhost ([127.0.0.1] helo=talk.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1ElvWz-0007Fv-1u for freebsd-amd64@freebsd.org; Mon, 12 Dec 2005 13:48:25 -0800 Message-ID: <1913673.post@talk.nabble.com> Date: Mon, 12 Dec 2005 13:48:25 -0800 (PST) From: "bsdrio (sent by Nabble.com)" To: freebsd-amd64@freebsd.org In-Reply-To: <436C5F54.7020300@rsmba.biz> MIME-Version: 1.0 X-Nabble-Sender: Nabble Forums X-Nabble-From: bsdrio References: <436BF442.9020708@rsmba.biz> <20051105054130.GL63539@ip.net.ua> <436C5F54.7020300@rsmba.biz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: buildworld failing on amd64 with RELENG_6 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bsdrio List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 21:48:28 -0000 Did you ever resolve this problem ? I have been unable to get past it myself. I have tried make cleanworld, as well as cd'ing to the directory and doing "make clean" followed by a "make", which as you reported built all the files, but then returning to /usr/src and running a make buildworld it still fails at the same point. Thanks for your time, I would appreciate any tips you may have for getting past this error, in particular the steps you took in resolving it in your case. Cheers, bsdrio Post Scriptum: I am using RELENG_6_0, amd64, upgrade from 5.4. -- Sent from the freebsd-amd64 forum at Nabble.com: http://www.nabble.com/buildworld-failing-on-amd64-with-RELENG_6-t494383.html#a1913673 From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 12 23:12:53 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B97016A41F; Mon, 12 Dec 2005 23:12:53 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9086C43D79; Mon, 12 Dec 2005 23:12:17 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.4/8.13.4) with ESMTP id jBCNCCjv034903; Mon, 12 Dec 2005 18:12:13 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id jBCNCCvp064379; Mon, 12 Dec 2005 18:12:12 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 989087302F; Mon, 12 Dec 2005 18:12:12 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051212231212.989087302F@freebsd-current.sentex.ca> Date: Mon, 12 Dec 2005 18:12:12 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 23:12:53 -0000 TB --- 2005-12-12 21:32:22 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-12-12 21:32:22 - starting HEAD tinderbox run for amd64/amd64 TB --- 2005-12-12 21:32:22 - cleaning the object tree TB --- 2005-12-12 21:33:02 - checking out the source tree TB --- 2005-12-12 21:33:02 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2005-12-12 21:33:02 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-12-12 21:39:02 - building world (CFLAGS=-O2 -pipe) TB --- 2005-12-12 21:39:02 - cd /src TB --- 2005-12-12 21:39:02 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries TB --- 2005-12-12 23:10:15 - generating LINT kernel config TB --- 2005-12-12 23:10:15 - cd /src/sys/amd64/conf TB --- 2005-12-12 23:10:15 - /usr/bin/make -B LINT TB --- 2005-12-12 23:10:15 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-12-12 23:10:15 - cd /src TB --- 2005-12-12 23:10:15 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Dec 12 23:10:15 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] /src/sys/gnu/fs/xfs/FreeBSD/xfs_freebsd.h:130:5: #error Wrong BLKDEV_IOSIZE In file included from /src/sys/gnu/fs/xfs/xfs.h:36, from /src/sys/gnu/fs/xfs/xfs_iomap.c:33: /src/sys/gnu/fs/xfs/FreeBSD/xfs_freebsd.h:130:5: #error Wrong BLKDEV_IOSIZE In file included from /src/sys/gnu/fs/xfs/xfs.h:36, from /src/sys/gnu/fs/xfs/xfs_behavior.c:33: /src/sys/gnu/fs/xfs/FreeBSD/xfs_freebsd.h:130:5: #error Wrong BLKDEV_IOSIZE mkdep: compile failed *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-12-12 23:12:12 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-12-12 23:12:12 - ERROR: failed to build lint kernel TB --- 2005-12-12 23:12:12 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 12 23:32:23 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F20016A420 for ; Mon, 12 Dec 2005 23:32:23 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1C7D43D69 for ; Mon, 12 Dec 2005 23:32:21 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IRE004O1S98MUA0@osl1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Tue, 13 Dec 2005 00:36:44 +0100 (CET) Received: from kg-work.kg4.no ([80.203.92.30]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0IRE008P4S6FSLB0@osl1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Tue, 13 Dec 2005 00:35:04 +0100 (CET) Date: Tue, 13 Dec 2005 00:32:19 +0100 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH In-reply-to: <200512121357.45468.jhb@freebsd.org> To: freebsd-amd64@freebsd.org Message-id: <20051213003219.0c292056.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd5.4) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT References: <20051211203747.474fb5a6.torfinn.ingolfsen@broadpark.no> <200512121357.45468.jhb@freebsd.org> Subject: Re: FreeBSD/amd64: is Linux 32-bit or 64-bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2005 23:32:23 -0000 On Mon, 12 Dec 2005 13:57:44 -0500 John Baldwin wrote: > On Sunday 11 December 2005 02:37 pm, Torfinn Ingolfsen wrote: > > This last part seems to say that linux on this machine is 32-bit? > > > > What is the correct answer? > > It runs Linux/i386 (i.e. 32-bit) binaries only currently. Ok. So 8in theory at least) a Linux/i386 web browser plugin for Java should work with a Linux/i386 webbrowser. Will it work with a native web browser as well? -- Regards, Torfinn Ingolfsen From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 13 00:31:32 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9079616A41F for ; Tue, 13 Dec 2005 00:31:32 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31D1743D68 for ; Tue, 13 Dec 2005 00:31:31 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IRE004G8UZUMWC0@osl1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Tue, 13 Dec 2005 01:35:54 +0100 (CET) Received: from kg-work.kg4.no ([80.203.92.30]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0IRE008QSUX2SO61@osl1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Tue, 13 Dec 2005 01:34:14 +0100 (CET) Date: Tue, 13 Dec 2005 01:31:29 +0100 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH To: freebsd-amd64@freebsd.org Message-id: <20051213013129.2f0b5568.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd5.4) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Running Opera (for Linux) on amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 00:31:32 -0000 Hello, Shouldn't it be possible to run linux-opera on FreeBSD 6.0-stable / amd64? Here is what I get: root@kg-quiet# uname -a FreeBSD kg-quiet.kg4.no 6.0-STABLE FreeBSD 6.0-STABLE #0: Thu Dec 8 00:56:05 CET 2005 root@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET amd64 root@kg-quiet# portversion -v | grep opera linux-opera-8.51.20051114 = up-to-date with port root@kg-quiet# ll /usr/X11R6/share/linux-opera/bin/opera -rwxr-xr-x 1 root wheel 12059892 Dec 13 00:35 /usr/X11R6/share/linux-opera/bin/opera* root@kg-quiet# file /usr/X11R6/share/linux-opera/bin/opera /usr/X11R6/share/linux-opera/bin/opera: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.0.0, dynamically linked (uses shared libs), stripped When I try to run opera (as my normal user), I get: tingo@kg-quiet$ /usr/X11R6/share/linux-opera/bin/opera opera: Preference initialization failure. File not found or could not be opened (-7) Why doesn't it find the prerefence file? And which preference file? I note that the native opera for FreeBSD/i386 installs a wrapper script, but linux-opera doesn't seem to do this. -- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 13 01:20:05 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45B7216A457 for ; Tue, 13 Dec 2005 01:20:05 +0000 (GMT) (envelope-from lists@nabble.com) Received: from talk.nabble.com (www.nabble.com [72.21.53.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id C835943D60 for ; Tue, 13 Dec 2005 01:20:04 +0000 (GMT) (envelope-from lists@nabble.com) Received: from localhost ([127.0.0.1] helo=talk.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1Elypo-0001Is-0d for freebsd-amd64@freebsd.org; Mon, 12 Dec 2005 17:20:04 -0800 Message-ID: <1916335.post@talk.nabble.com> Date: Mon, 12 Dec 2005 17:20:03 -0800 (PST) From: "bsdrio (sent by Nabble.com)" To: freebsd-amd64@freebsd.org In-Reply-To: <7.0.0.16.0.20051207104632.01c92628@micom.mng.net> MIME-Version: 1.0 X-Nabble-Sender: Nabble Forums X-Nabble-From: bsdrio References: <7.0.0.16.0.20051207093744.01c92628@micom.mng.net> <4396433C.3050701@samsco.org> <7.0.0.16.0.20051207104632.01c92628@micom.mng.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: 6.0 Buildworld on AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bsdrio List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 01:20:06 -0000 I have the same concern as Ganbold. I also had an "abrupt" end to buildworld with exactly the same ending as Ganbold. I second his question of "Is it safe to continue the upgrade?". This is on a production server so I wish to be as cautious as possible. Any and all suggestions are welcome, bsdrio -- Sent from the freebsd-amd64 forum at Nabble.com: http://www.nabble.com/6.0-Buildworld-on-AMD64-t691634.html#a1916335 From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 13 01:26:16 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92FFB16A41F for ; Tue, 13 Dec 2005 01:26:16 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1993943D46 for ; Tue, 13 Dec 2005 01:26:16 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id CC43B1A3C1E; Mon, 12 Dec 2005 17:26:15 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 1F4A351432; Mon, 12 Dec 2005 20:26:15 -0500 (EST) Date: Mon, 12 Dec 2005 20:26:15 -0500 From: Kris Kennaway To: bsdrio Message-ID: <20051213012614.GA39654@xor.obsecurity.org> References: <7.0.0.16.0.20051207093744.01c92628@micom.mng.net> <4396433C.3050701@samsco.org> <7.0.0.16.0.20051207104632.01c92628@micom.mng.net> <1916335.post@talk.nabble.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Kj7319i9nmIyA2yE" Content-Disposition: inline In-Reply-To: <1916335.post@talk.nabble.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: 6.0 Buildworld on AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 01:26:16 -0000 --Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 12, 2005 at 05:20:03PM -0800, bsdrio (sent by Nabble.com) wrote: >=20 > I have the same concern as Ganbold. > I also had an "abrupt" end to buildworld with exactly the same ending as = Ganbold. I second his question of "Is it safe to continue the upgrade?". Th= is is on a production server so I wish to be as cautious as possible. >=20 > Any and all suggestions are welcome, buildworld does not touch any of your installed files, so if it halts unexpectedly it still did not touch any of your files. You can correct the problem and retry. Kris --Kj7319i9nmIyA2yE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDniM2Wry0BWjoQKURArPIAKDx0biGQBxUerF9Amdf06HcJZqsVgCcCUrS Q01IyLaZlmPOI9S4osYUcsI= =EiJg -----END PGP SIGNATURE----- --Kj7319i9nmIyA2yE-- From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 13 01:49:22 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BC1916A41F for ; Tue, 13 Dec 2005 01:49:22 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4613943D45 for ; Tue, 13 Dec 2005 01:49:20 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.53 (FreeBSD)) id 1ElzOI-000BlP-7E; Tue, 13 Dec 2005 09:55:42 +0800 Message-Id: <7.0.0.16.2.20051213094628.04230870@micom.mng.net> X-Mailer: QUALCOMM Windows Eudora Version 7.0.0.16 Date: Tue, 13 Dec 2005 09:49:09 +0800 To: bsdrio From: Ganbold In-Reply-To: <1916335.post@talk.nabble.com> References: <7.0.0.16.0.20051207093744.01c92628@micom.mng.net> <4396433C.3050701@samsco.org> <7.0.0.16.0.20051207104632.01c92628@micom.mng.net> <1916335.post@talk.nabble.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: freebsd-amd64@freebsd.org Subject: Re: 6.0 Buildworld on AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 01:49:22 -0000 At 09:20 AM 12/13/2005, you wrote: >I have the same concern as Ganbold. >I also had an "abrupt" end to buildworld with exactly the same >ending as Ganbold. I second his question of "Is it safe to continue >the upgrade?". This is on a production server so I wish to be as >cautious as possible. Without waiting for an answer from mailing list I continued the upgrade and it seems like upgrade went through. This is my production server. publica# uname -an FreeBSD publica.ub.mng.net 6.0-STABLE FreeBSD 6.0-STABLE #1: Thu Dec 8 11:48:36 ULAT 2005 tsgan@publica.ub.mng.net:/usr/obj/usr/src/sys/AMD amd64 hth, Ganbold >Any and all suggestions are welcome, > >bsdrio >-- >Sent from the freebsd-amd64 forum at Nabble.com: >http://www.nabble.com/6.0-Buildworld-on-AMD64-t691634.html#a1916335 >_______________________________________________ >freebsd-amd64@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 >To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 13 04:20:59 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 605F016A41F for ; Tue, 13 Dec 2005 04:20:59 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC3BB43D5A for ; Tue, 13 Dec 2005 04:20:58 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id jBD4Kvh4009405; Mon, 12 Dec 2005 20:20:57 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id jBD4Kv7v009404; Mon, 12 Dec 2005 20:20:57 -0800 Date: Mon, 12 Dec 2005 20:20:57 -0800 From: Brooks Davis To: bsdrio Message-ID: <20051213042057.GA13113@odin.ac.hmc.edu> References: <436BF442.9020708@rsmba.biz> <20051105054130.GL63539@ip.net.ua> <436C5F54.7020300@rsmba.biz> <1913673.post@talk.nabble.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0OAP2g/MAC+5xKAE" Content-Disposition: inline In-Reply-To: <1913673.post@talk.nabble.com> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: freebsd-amd64@freebsd.org Subject: Re: buildworld failing on amd64 with RELENG_6 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 04:20:59 -0000 --0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 12, 2005 at 01:48:25PM -0800, bsdrio (sent by Nabble.com) wrote: >=20 > Did you ever resolve this problem ? I have been unable to get past > it myself. I have tried make cleanworld, as well as cd'ing to the > directory and doing "make clean" followed by a "make", which as you > reported built all the files, but then returning to /usr/src and > running a make buildworld it still fails at the same point. > > Thanks for your time, I would appreciate any tips you may have for > getting past this error, in particular the steps you took in resolving > it in your case. Check your system clock. This did fix it for me. -- 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 --0OAP2g/MAC+5xKAE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDnkwpXY6L6fI4GtQRAi4cAJ97AjcpCNhbyvfsShxruIruRYig3QCfYqCY 46nWJyjtmSLbKcBc8IUlqfU= =Xck5 -----END PGP SIGNATURE----- --0OAP2g/MAC+5xKAE-- From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 13 04:41:08 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 600AC16A41F for ; Tue, 13 Dec 2005 04:41:08 +0000 (GMT) (envelope-from steve.tell@crashmail.de) Received: from hydra.crashmail.de (hydra.crashmail.de [217.146.142.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9926243D67 for ; Tue, 13 Dec 2005 04:41:06 +0000 (GMT) (envelope-from steve.tell@crashmail.de) Received: from localhost (localhost.crashmail.de [127.0.0.1]) by hydra.crashmail.de (Postfix) with ESMTP id A70A162F67 for ; Tue, 13 Dec 2005 05:41:12 +0100 (CET) Received: from hydra.crashmail.de ([127.0.0.1]) by localhost (hydra.crashmail.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 04032-05 for ; Tue, 13 Dec 2005 05:41:05 +0100 (CET) Received: from nexxus.crashmail.de (dslb-082-083-080-134.pools.arcor-ip.net [82.83.80.134]) by hydra.crashmail.de (Postfix) with ESMTP id C24D26209C for ; Tue, 13 Dec 2005 05:41:04 +0100 (CET) From: Stefan 'Steve' Tell To: freebsd-amd64@freebsd.org In-Reply-To: <20051213013129.2f0b5568.torfinn.ingolfsen@broadpark.no> (Torfinn Ingolfsen's message of "Tue, 13 Dec 2005 01:31:29 +0100") Organization: The Third Place References: <20051213013129.2f0b5568.torfinn.ingolfsen@broadpark.no> X-Face: .KSo,m`RE@]&5>cJ8vw<`1x?R(?,Q]b@qeq; P\.fK\}i>U^v9f; /~+rKfXKOJ$jD@Foy7MtnIpnk+6]/](%q@*/|+M<4.q@SO3+)u X-PGP-Key: 0x9B6C7E15 X-PGP-Fingerprint: 0A21 6C88 552E 54AE 3FB5 4732 25EE 6ABE 9B6C 7E15 X-BSD-Version: FreeBSD nexxus.crashmail.de 6.0-STABLE FreeBSD 6.0-STABLE #8: Mon Dec 12 18:46:47 CET 2005 stell@nexxus.crashmail.de:/usr/obj/usr/src/sys/NEXXUS amd64 Date: Tue, 13 Dec 2005 05:40:55 +0100 Message-ID: <87lkypy5go.fsf@zeus.crashmail.de> User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new-20030616-p10 at crashmail.de Subject: Re: Running Opera (for Linux) on amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 04:41:08 -0000 * Torfinn Ingolfsen wrote: > Shouldn't it be possible to run linux-opera on FreeBSD 6.0-stable / > amd64? I run linux-opera on FreeBSD/amd64 6.0-stable for some weeks. Since yesterday, 'linux-opera' just says ,---- | [stell @ nexxus:~]% linux-opera | FATAL: kernel too old `---- Hum? I don't now what change to my system causes this error. -- By(t)e, Steve /\ http://www.crashmail.de GnuPG/PGP: 0X9B6C7E15, encrypted mail prefered, see header From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 13 04:44:17 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43AB616A41F for ; Tue, 13 Dec 2005 04:44:17 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9934B43D5D for ; Tue, 13 Dec 2005 04:44:16 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3688201 for multiple; Mon, 12 Dec 2005 23:46:30 -0500 Received: from [192.168.0.15] (osx.baldwin.cx [192.168.0.15]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jBD4iCA9016732; Mon, 12 Dec 2005 23:44:12 -0500 (EST) (envelope-from jhb@FreeBSD.org) In-Reply-To: <20051213003219.0c292056.torfinn.ingolfsen@broadpark.no> References: <20051211203747.474fb5a6.torfinn.ingolfsen@broadpark.no> <200512121357.45468.jhb@freebsd.org> <20051213003219.0c292056.torfinn.ingolfsen@broadpark.no> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <91BDEEAB-DD25-4E5F-ACE9-FD357DB6B50F@FreeBSD.org> Content-Transfer-Encoding: 7bit From: John Baldwin Date: Mon, 12 Dec 2005 23:43:51 -0500 To: Torfinn Ingolfsen X-Mailer: Apple Mail (2.746.2) X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-amd64@FreeBSD.org Subject: Re: FreeBSD/amd64: is Linux 32-bit or 64-bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 04:44:17 -0000 On Dec 12, 2005, at 6:32 PM, Torfinn Ingolfsen wrote: > On Mon, 12 Dec 2005 13:57:44 -0500 > John Baldwin wrote: > >> On Sunday 11 December 2005 02:37 pm, Torfinn Ingolfsen wrote: >>> This last part seems to say that linux on this machine is 32-bit? >>> >>> What is the correct answer? >> >> It runs Linux/i386 (i.e. 32-bit) binaries only currently. > > Ok. So 8in theory at least) a Linux/i386 web browser plugin for Java > should work with a Linux/i386 webbrowser. > Will it work with a native web browser as well? Well, it might work with a FreeBSD/i386 webbrowser if you use something like the pluginwrapper port, although I'm not sure how ld- elf32.so.1 interacts with libmap (does it use /etc/libmap.conf or a separate /etc/libmap32.conf?). I'm fairly certain you can't use Linux/i386 plugins with a FreeBSD/amd64 browser however. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 13 16:53:34 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7C8616A422 for ; Tue, 13 Dec 2005 16:53:34 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5819043E2F for ; Tue, 13 Dec 2005 16:51:42 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.4/8.13.4) with ESMTP id jBDGpQmF059963; Tue, 13 Dec 2005 08:51:27 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.4/8.13.1/Submit) id jBDGpPbM059962; Tue, 13 Dec 2005 08:51:25 -0800 (PST) (envelope-from obrien) Date: Tue, 13 Dec 2005 08:51:25 -0800 From: "David O'Brien" To: Dev Tugnait Message-ID: <20051213165125.GA59683@dragon.NUXI.org> References: <1134410468.12592.6.camel@dracula> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1134410468.12592.6.camel@dracula> X-Operating-System: FreeBSD 7.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.11 Cc: freebsd-amd64@freebsd.org Subject: Re: MotherBoard Chipset Woes X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 16:53:34 -0000 On Mon, Dec 12, 2005 at 01:01:08PM -0500, Dev Tugnait wrote: > I have also seen an ATI Express 200 Chipset Mobo but I have heard stay > away from ati due to unsupported hardware. What unsupported hardware? I'm running an MSI ATI-based motherboard. -- -- David (obrien@FreeBSD.org) Q: Because it reverses the logical flow of conversation. A: Why is top-posting (putting a reply at the top of the message) frowned upon? From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 13 17:04:29 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5123616A41F; Tue, 13 Dec 2005 17:04:29 +0000 (GMT) (envelope-from rondzierwa@comcast.net) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75FD243D7B; Tue, 13 Dec 2005 17:04:26 +0000 (GMT) (envelope-from rondzierwa@comcast.net) Received: from comcast.net (pcp0010489854pcs.essex01.md.comcast.net[69.143.77.148]) by comcast.net (sccrmhc11) with SMTP id <20051213170425011005jf67e>; Tue, 13 Dec 2005 17:04:25 +0000 Message-ID: <439EFF19.958D6326@comcast.net> Date: Tue, 13 Dec 2005 12:04:25 -0500 From: Ron Dzierwa X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: glewis@freebsd.org, freebsd-amd64@FreeBSD.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: jdk15 on 6.0-RELEASE amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 17:04:29 -0000 I am trying to install the native jdk15 on a new installation of 6.0-RELEASE-amd64 i got the three packages: jdk-1_5_0-bin-scsl.zip jdk-1_5_0-src-scsl.zip bsd-jdk15-patches-2.tar.bz2 put them in distfiles, then did make in /usr/ports/java/jdk15. it runs along for a while, then: ===> Applying FreeBSD patches for jdk-1.5.0p2_3 Ignoring previously applied (or reversed) patch. 1 out of 1 hunks ignored--saving rejects to ../../hotspot/src/os/bsd/vm/os_bsd.inline.hpp.rej => Patch patch-hotspot-vm-os_bsd.inline.hpp failed to apply cleanly. => Patch(es) patch-control::common::Defs-bsd.gmk patch-deploy::common::Defs-bsd.gmk patch-dep loy::common::DeployRules-solaris.gmk patch-deploy::native::msgString.c patch-deploy::native:: system_md.c patch-deploy::native::system_md.h patch-deploy::ns7-adapter::Makefile applied cle anly. *** Error code 1 Stop in /usr/ports/java/jdk15. the contents of ./work/hotspot/src/os/bsd/vm/os_bsd.inline.hpp.rej is: *************** *** 29,38 **** inline bool os::allocate_stack_guard_pages() { assert(uses_stack_guard_pages(), "sanity check"); - // XXXBSD: ?? - // return thr_main(); - // return pthread_main_np(); - return true; } --- 29,37 ---- inline bool os::allocate_stack_guard_pages() { assert(uses_stack_guard_pages(), "sanity check"); + // Since FreeBSD 4 uses malloc() for allocating the thread stack + // there is no need to do anything extra to allocate the guard pages + return false; } any ideas? any help installing any 1.4 or 1.5 (preferably) jdk would be appreciated. thanks, ron. From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 13 17:18:14 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0EC116A41F for ; Tue, 13 Dec 2005 17:18:14 +0000 (GMT) (envelope-from ewinter@west.bsn.com) Received: from lobo.ewinter.org (host-62-245-151-69.customer.m-online.net [62.245.151.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA82C43D53 for ; Tue, 13 Dec 2005 17:18:13 +0000 (GMT) (envelope-from ewinter@west.bsn.com) Received: from lobo.ewinter.org (localhost [127.0.0.1]) by lobo.ewinter.org (8.13.4/8.13.4) with ESMTP id jBDHEGPV035759; Tue, 13 Dec 2005 18:14:16 +0100 (CET) (envelope-from ewinter@west.bsn.com) Received: (from ewinter@localhost) by lobo.ewinter.org (8.13.4/8.13.4/Submit) id jBDHEFf5035758; Tue, 13 Dec 2005 18:14:15 +0100 (CET) (envelope-from ewinter) Date: Tue, 13 Dec 2005 18:14:15 +0100 From: "Ernst W. Winter" To: Ron Dzierwa Message-ID: <20051213171415.GA35686@lobo.ewinter.org> References: <439EFF19.958D6326@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <439EFF19.958D6326@comcast.net> X-Phone: + 49-89-3075-6800 Organization: FreeBSD Evangelist X-Operating-System: FreeBSD lobo.ewinter.org 6.0-STABLE FreeBSD 6.0-STABLE User-Agent: mutt-ng/devel (FreeBSD) Cc: freebsd-amd64@freebsd.org Subject: Re: jdk15 on 6.0-RELEASE amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Ernst W. Winter" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 17:18:14 -0000 On Tue, 13 Dec 2005, Ron Dzierwa wrote: > I am trying to install the native jdk15 on a new installation of > 6.0-RELEASE-amd64 > > i got the three packages: > jdk-1_5_0-bin-scsl.zip > jdk-1_5_0-src-scsl.zip > bsd-jdk15-patches-2.tar.bz2 > > put them in distfiles, then did make in /usr/ports/java/jdk15. it > runs along for a while, then: > > ===> Applying FreeBSD patches for jdk-1.5.0p2_3 > Ignoring previously applied (or reversed) patch. > 1 out of 1 hunks ignored--saving rejects to > ../../hotspot/src/os/bsd/vm/os_bsd.inline.hpp.rej => Patch > patch-hotspot-vm-os_bsd.inline.hpp failed to apply cleanly. > => Patch(es) patch-control::common::Defs-bsd.gmk > patch-deploy::common::Defs-bsd.gmk patch-dep > loy::common::DeployRules-solaris.gmk > patch-deploy::native::msgString.c patch-deploy::native:: > system_md.c patch-deploy::native::system_md.h > patch-deploy::ns7-adapter::Makefile applied cle > anly. > *** Error code 1 > > Stop in /usr/ports/java/jdk15. > > the contents of ./work/hotspot/src/os/bsd/vm/os_bsd.inline.hpp.rej > is: > > *************** > *** 29,38 **** > > inline bool os::allocate_stack_guard_pages() { > assert(uses_stack_guard_pages(), "sanity check"); > - // XXXBSD: ?? > - // return thr_main(); > - // return pthread_main_np(); > - return true; > } > > > --- 29,37 ---- > > inline bool os::allocate_stack_guard_pages() { > assert(uses_stack_guard_pages(), "sanity check"); > + // Since FreeBSD 4 uses malloc() for allocating the thread stack > + // there is no need to do anything extra to allocate the guard pages > + return false; > } > > > any ideas? > well I would say to update it with cvsup and then do a "makeworld - kernel installation and then reboot and compile it. I have done a update yesterday and there where no problems it all went smooth. Here output: lobo root 502-->uname -a FreeBSD lobo.ewinter.org 6.0-STABLE FreeBSD 6.0-STABLE #5: Tue Dec 6 21:20:19 CET 2005 ewinter@lobo.ewinter.org:/usr/obj/usr/src/sys/lobo amd64 /home/ewinter lobo root 503--> > any help installing any 1.4 or 1.5 (preferably) jdk would be > appreciated. > that is all I can say to it. It was a bit wonky in the beginning when 6.0pre came out, but so far I would say if you updated it with cvsup I would say it will compile and install. Mond you I don't use it, jst to see that it is installable for customers. Ernst From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 13 18:19:55 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B0ED16A427; Tue, 13 Dec 2005 18:19:55 +0000 (GMT) (envelope-from dev@unixdaemon.org) Received: from ladle.dreamhost.com (ladle.dreamhost.com [205.196.219.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id A185643D9D; Tue, 13 Dec 2005 18:19:21 +0000 (GMT) (envelope-from dev@unixdaemon.org) Received: from dracula (cpe-24-24-83-9.stny.res.rr.com [24.24.83.9]) by ladle.dreamhost.com (Postfix) with ESMTP id 13D7F129A85; Tue, 13 Dec 2005 10:19:08 -0800 (PST) From: Dev Tugnait To: obrien@freebsd.org In-Reply-To: <20051213165125.GA59683@dragon.NUXI.org> References: <1134410468.12592.6.camel@dracula> <20051213165125.GA59683@dragon.NUXI.org> Content-Type: text/plain Date: Tue, 13 Dec 2005 13:18:49 -0500 Message-Id: <1134497929.12592.9.camel@dracula> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: MotherBoard Chipset Woes X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dev@unixdaemon.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 18:19:56 -0000 On Tue, 2005-12-13 at 08:51 -0800, David O'Brien wrote: > On Mon, Dec 12, 2005 at 01:01:08PM -0500, Dev Tugnait wrote: > > I have also seen an ATI Express 200 Chipset Mobo but I have heard stay > > away from ati due to unsupported hardware. > > What unsupported hardware? I'm running an MSI ATI-based motherboard. > I saw it in the Motherboards list later, thought it wasn't mentioned seemed to be getting negative feedback on that chipset from wrong sources. Thanks, I'll go with the Sapphire board then. -- Dev Tugnait From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 13 22:23:43 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7BB316A41F for ; Tue, 13 Dec 2005 22:23:43 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEAE343D4C for ; Tue, 13 Dec 2005 22:23:42 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IRG00L6QJQUJ490@osl1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Tue, 13 Dec 2005 23:28:06 +0100 (CET) Received: from kg-work.kg4.no ([80.203.92.30]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0IRG00M6KJO1PD90@osl1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Tue, 13 Dec 2005 23:26:25 +0100 (CET) Date: Tue, 13 Dec 2005 20:21:49 +0100 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH In-reply-to: <20051213165125.GA59683@dragon.NUXI.org> To: freebsd-amd64@freebsd.org Message-id: <20051213202149.260c77be.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd5.4) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT References: <1134410468.12592.6.camel@dracula> <20051213165125.GA59683@dragon.NUXI.org> Subject: Re: MotherBoard Chipset Woes X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 22:23:43 -0000 On Tue, 13 Dec 2005 08:51:25 -0800 David O'Brien wrote: > What unsupported hardware? I'm running an MSI ATI-based motherboard. Not unsupported per se, just flaky. Note: this _might_ be related to the specific manufacturer and / or model of motherboard that I'm using; I don't know. And all this might be history now, for all I know. Earlier on, the Xorg support (xorg 6.99.5) for ATI Radeon Xpress 200 gfx chipset was unstable, as described here: https://bugs.freedesktop.org/show_bug.cgi?id=3242 https://bugs.freedesktop.org/show_bug.cgi?id=3296 because the card was unusable at the time, I switched to a external card - the nVidia GeForce 6200 TurboCache. This has worked for me, so I haven't tested the Xpress 200 onboard gfx after that. -- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 14 00:02:17 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB75716A41F for ; Wed, 14 Dec 2005 00:02:17 +0000 (GMT) (envelope-from mv@roq.com) Received: from vault.mel.jumbuck.com (ppp166-27.static.internode.on.net [150.101.166.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0252B43D62 for ; Wed, 14 Dec 2005 00:02:16 +0000 (GMT) (envelope-from mv@roq.com) Received: from vault.mel.jumbuck.com (localhost [127.0.0.1]) by vault.mel.jumbuck.com (Postfix) with ESMTP id 771FC8A027; Wed, 14 Dec 2005 11:02:15 +1100 (EST) Received: from [192.168.46.52] (unknown [192.168.46.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by vault.mel.jumbuck.com (Postfix) with ESMTP id 5B6838A01F; Wed, 14 Dec 2005 11:02:15 +1100 (EST) Message-ID: <439F6108.9050601@roq.com> Date: Wed, 14 Dec 2005 11:02:16 +1100 From: Michael Vince User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.12) Gecko/20051208 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ron Dzierwa References: <439EFF19.958D6326@comcast.net> In-Reply-To: <439EFF19.958D6326@comcast.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-amd64@FreeBSD.org Subject: Re: jdk15 on 6.0-RELEASE amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 00:02:18 -0000 I have had problems compiling it, it does appear to be different problems for different people but for me I nuked the current linux packages setup and put 'OVERRIDE_LINUX_BASE_PORT=suse-9.2' into /etc/make.conf And I also upgraded to 6-stable for some reason it worked after going stable. Mike Ron Dzierwa wrote: >I am trying to install the native jdk15 on a new installation of 6.0-RELEASE-amd64 > >i got the three packages: > jdk-1_5_0-bin-scsl.zip > jdk-1_5_0-src-scsl.zip > bsd-jdk15-patches-2.tar.bz2 > >put them in distfiles, then did make in /usr/ports/java/jdk15. it runs along for a while, then: > >===> Applying FreeBSD patches for jdk-1.5.0p2_3 >Ignoring previously applied (or reversed) patch. >1 out of 1 hunks ignored--saving rejects to ../../hotspot/src/os/bsd/vm/os_bsd.inline.hpp.rej >=> Patch patch-hotspot-vm-os_bsd.inline.hpp failed to apply cleanly. >=> Patch(es) patch-control::common::Defs-bsd.gmk patch-deploy::common::Defs-bsd.gmk patch-dep >loy::common::DeployRules-solaris.gmk patch-deploy::native::msgString.c patch-deploy::native:: >system_md.c patch-deploy::native::system_md.h patch-deploy::ns7-adapter::Makefile applied cle >anly. >*** Error code 1 > >Stop in /usr/ports/java/jdk15. > >the contents of ./work/hotspot/src/os/bsd/vm/os_bsd.inline.hpp.rej is: > >*************** >*** 29,38 **** > > inline bool os::allocate_stack_guard_pages() { > assert(uses_stack_guard_pages(), "sanity check"); >- // XXXBSD: ?? >- // return thr_main(); >- // return pthread_main_np(); >- return true; > } > > >--- 29,37 ---- > > inline bool os::allocate_stack_guard_pages() { > assert(uses_stack_guard_pages(), "sanity check"); >+ // Since FreeBSD 4 uses malloc() for allocating the thread stack >+ // there is no need to do anything extra to allocate the guard pages >+ return false; > } > > >any ideas? > >any help installing any 1.4 or 1.5 (preferably) jdk would be appreciated. > >thanks, >ron. > > >_______________________________________________ >freebsd-amd64@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 >To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > > From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 14 02:11:24 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9060D16A41F for ; Wed, 14 Dec 2005 02:11:24 +0000 (GMT) (envelope-from dev@unixdaemon.org) Received: from ladle.dreamhost.com (ladle.dreamhost.com [205.196.219.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95DDE43D86 for ; Wed, 14 Dec 2005 02:11:07 +0000 (GMT) (envelope-from dev@unixdaemon.org) Received: from dracula (cpe-24-24-83-9.stny.res.rr.com [24.24.83.9]) by ladle.dreamhost.com (Postfix) with ESMTP id A63B5129A85; Tue, 13 Dec 2005 18:11:04 -0800 (PST) From: Dev Tugnait To: Torfinn Ingolfsen In-Reply-To: <20051213202149.260c77be.torfinn.ingolfsen@broadpark.no> References: <1134410468.12592.6.camel@dracula> <20051213165125.GA59683@dragon.NUXI.org> <20051213202149.260c77be.torfinn.ingolfsen@broadpark.no> Content-Type: text/plain Date: Tue, 13 Dec 2005 21:10:59 -0500 Message-Id: <1134526259.12592.12.camel@dracula> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: MotherBoard Chipset Woes X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dev@unixdaemon.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 02:11:24 -0000 The board I have bought does not have onboard video hehe go figure. I plan on using nvidia anyway but since their aren't any drivers out as yet I might be forced to run x86 for awhile. I am just worried about the Marvell Lan chipset. On Tue, 2005-12-13 at 20:21 +0100, Torfinn Ingolfsen wrote: > On Tue, 13 Dec 2005 08:51:25 -0800 > David O'Brien wrote: > > > What unsupported hardware? I'm running an MSI ATI-based motherboard. > > Not unsupported per se, just flaky. Note: this _might_ be related to the > specific manufacturer and / or model of motherboard that I'm using; I > don't know. And all this might be history now, for all I know. > > Earlier on, the Xorg support (xorg 6.99.5) for ATI Radeon Xpress 200 gfx > chipset was unstable, as described here: > https://bugs.freedesktop.org/show_bug.cgi?id=3242 > https://bugs.freedesktop.org/show_bug.cgi?id=3296 > > because the card was unusable at the time, I switched to a external > card - the nVidia GeForce 6200 TurboCache. This has worked for me, so I > haven't tested the Xpress 200 onboard gfx after that. -- Dev Tugnait From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 14 08:28:00 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8493516A41F for ; Wed, 14 Dec 2005 08:28:00 +0000 (GMT) (envelope-from fbsd-am64@bzerk.org) Received: from ei.bzerk.org (ei.xs4all.nl [213.84.67.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id C839143D55 for ; Wed, 14 Dec 2005 08:27:59 +0000 (GMT) (envelope-from fbsd-am64@bzerk.org) Received: from ei.bzerk.org (BOFH@localhost [127.0.0.1]) by ei.bzerk.org (8.13.3/8.13.3) with ESMTP id jBE8Wg7q005454; Wed, 14 Dec 2005 09:32:45 +0100 (CET) (envelope-from fbsd-am64@bzerk.org) Received: (from bulk@localhost) by ei.bzerk.org (8.13.3/8.13.3/Submit) id jBE8WglA005453; Wed, 14 Dec 2005 09:32:42 +0100 (CET) (envelope-from fbsd-am64@bzerk.org) Date: Wed, 14 Dec 2005 09:32:42 +0100 From: Ruben de Groot To: "O. Hartmann" Message-ID: <20051214083242.GA5351@ei.bzerk.org> References: <20051211203747.474fb5a6.torfinn.ingolfsen@broadpark.no> <439C8512.2090602@mail.uni-mainz.de> <200512111819.01138.joao@matik.com.br> <439C8D64.6090300@mail.uni-mainz.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <439C8D64.6090300@mail.uni-mainz.de> User-Agent: Mutt/1.4.2.1i X-Spam-Status: No, score=-0.8 required=5.0 tests=ALL_TRUSTED, J_CHICKENPOX_93 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on ei.bzerk.org X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (ei.bzerk.org [127.0.0.1]); Wed, 14 Dec 2005 09:32:48 +0100 (CET) Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD/amd64: is Linux 32-bit or 64-bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 08:28:00 -0000 On Sun, Dec 11, 2005 at 09:34:44PM +0100, O. Hartmann typed: > > On AMD64, ther's noc chance obtaining a working jdk15 environment! It's working fine here: > uname -a FreeBSD malenfant.lan 6.0-STABLE FreeBSD 6.0-STABLE #3: Tue Dec 13 22:53:04 CET 2005 root@malenfant.lan:/usr/obj/usr/src/sys/MALENFANT amd64 > java -version java version "1.5.0-p2" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-p2-root_12_nov_2005_17_05) Java HotSpot(TM) 64-Bit Server VM (build 1.5.0-p2-root_12_nov_2005_17_05, mixed mode) From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 14 14:30:32 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5344116A41F for ; Wed, 14 Dec 2005 14:30:32 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.178.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB60243D95 for ; Wed, 14 Dec 2005 14:30:17 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [134.93.180.218] (edda.Physik.Uni-Mainz.DE [134.93.180.218]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate1.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 99DF430012E9; Wed, 14 Dec 2005 15:30:13 +0100 (CET) Message-ID: <43A02C3F.7040104@mail.uni-mainz.de> Date: Wed, 14 Dec 2005 15:29:19 +0100 From: "O. Hartmann" Organization: Institut =?ISO-8859-1?Q?f=FCr_Geophysik?= User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ruben de Groot References: <20051211203747.474fb5a6.torfinn.ingolfsen@broadpark.no> <439C8512.2090602@mail.uni-mainz.de> <200512111819.01138.joao@matik.com.br> <439C8D64.6090300@mail.uni-mainz.de> <20051214083242.GA5351@ei.bzerk.org> In-Reply-To: <20051214083242.GA5351@ei.bzerk.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD/amd64: is Linux 32-bit or 64-bit? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 14:30:32 -0000 Ruben de Groot wrote: > On Sun, Dec 11, 2005 at 09:34:44PM +0100, O. Hartmann typed: > >>On AMD64, ther's noc chance obtaining a working jdk15 environment! > > > It's working fine here: > > >>uname -a > > FreeBSD malenfant.lan 6.0-STABLE FreeBSD 6.0-STABLE #3: Tue Dec 13 22:53:04 CET 2005 root@malenfant.lan:/usr/obj/usr/src/sys/MALENFANT amd64 > > >>java -version > > java version "1.5.0-p2" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-p2-root_12_nov_2005_17_05) > Java HotSpot(TM) 64-Bit Server VM (build 1.5.0-p2-root_12_nov_2005_17_05, mixed mode) Java HotSpot 64-Bit Server VM crashes on my box when compiling a new jdk15 (patchlevel 3). I will provide you with more detailed information when I try compiling next time. From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 14 16:10:10 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FC9316A41F for ; Wed, 14 Dec 2005 16:10:10 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B89B943D95 for ; Wed, 14 Dec 2005 16:10:07 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBEGA6Kw073658 for ; Wed, 14 Dec 2005 16:10:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBEGA6QA073657; Wed, 14 Dec 2005 16:10:06 GMT (envelope-from gnats) Date: Wed, 14 Dec 2005 16:10:06 GMT Message-Id: <200512141610.jBEGA6QA073657@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Roger Marquis Cc: Subject: Re: amd64/90267: nmap fails under amd64 5.4-REL X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Roger Marquis List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 16:10:10 -0000 The following reply was made to PR amd64/90267; it has been noted by GNATS. From: Roger Marquis To: John Baldwin Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: amd64/90267: nmap fails under amd64 5.4-REL Date: Wed, 14 Dec 2005 08:05:34 -0800 (PST) John Baldwin wrote: >>>Are you running it as root? >> Yes >> Does nmap work under FreeBSD/i386 on the same hardware? > Yes >> ... This bug is fixed in nmap-3.95. Thanks John! -- Roger Marquis Roble Systems Consulting http://www.roble.com/ From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 14 16:12:43 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D68016A41F for ; Wed, 14 Dec 2005 16:12:43 +0000 (GMT) (envelope-from dev@unixdaemon.org) Received: from knife.dreamhost.com (knife.dreamhost.com [66.33.219.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07DE343D5C for ; Wed, 14 Dec 2005 16:12:42 +0000 (GMT) (envelope-from dev@unixdaemon.org) Received: from dracula (cpe-24-24-83-9.stny.res.rr.com [24.24.83.9]) by knife.dreamhost.com (Postfix) with ESMTP id AA2C1FB621; Wed, 14 Dec 2005 08:12:32 -0800 (PST) From: Dev Tugnait To: Torfinn Ingolfsen In-Reply-To: <20051213202149.260c77be.torfinn.ingolfsen@broadpark.no> References: <1134410468.12592.6.camel@dracula> <20051213165125.GA59683@dragon.NUXI.org> <20051213202149.260c77be.torfinn.ingolfsen@broadpark.no> Content-Type: text/plain Date: Tue, 13 Dec 2005 21:10:59 -0500 Message-Id: <1134526259.12592.12.camel@dracula> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: MotherBoard Chipset Woes X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dev@unixdaemon.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 16:12:43 -0000 The board I have bought does not have onboard video hehe go figure. I plan on using nvidia anyway but since their aren't any drivers out as yet I might be forced to run x86 for awhile. I am just worried about the Marvell Lan chipset. On Tue, 2005-12-13 at 20:21 +0100, Torfinn Ingolfsen wrote: > On Tue, 13 Dec 2005 08:51:25 -0800 > David O'Brien wrote: > > > What unsupported hardware? I'm running an MSI ATI-based motherboard. > > Not unsupported per se, just flaky. Note: this _might_ be related to the > specific manufacturer and / or model of motherboard that I'm using; I > don't know. And all this might be history now, for all I know. > > Earlier on, the Xorg support (xorg 6.99.5) for ATI Radeon Xpress 200 gfx > chipset was unstable, as described here: > https://bugs.freedesktop.org/show_bug.cgi?id=3242 > https://bugs.freedesktop.org/show_bug.cgi?id=3296 > > because the card was unusable at the time, I switched to a external > card - the nVidia GeForce 6200 TurboCache. This has worked for me, so I > haven't tested the Xpress 200 onboard gfx after that. -- Dev Tugnait From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 14 17:23:26 2005 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55E6616A420; Wed, 14 Dec 2005 17:23:26 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E977743D5A; Wed, 14 Dec 2005 17:23:25 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from freefall.freebsd.org (jhb@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBEHNPCe078839; Wed, 14 Dec 2005 17:23:25 GMT (envelope-from jhb@freefall.freebsd.org) Received: (from jhb@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBEHNPBm078835; Wed, 14 Dec 2005 17:23:25 GMT (envelope-from jhb) Date: Wed, 14 Dec 2005 17:23:25 GMT From: John Baldwin Message-Id: <200512141723.jBEHNPBm078835@freefall.freebsd.org> To: marquis@roble.com, jhb@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/90267: nmap fails under amd64 5.4-REL X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 17:23:26 -0000 Synopsis: nmap fails under amd64 5.4-REL State-Changed-From-To: open->closed State-Changed-By: jhb State-Changed-When: Wed Dec 14 17:22:57 UTC 2005 State-Changed-Why: Appears to be a bug in nmap. Submitter reports that it was fixed in nmap-3.95. http://www.freebsd.org/cgi/query-pr.cgi?pr=90267 From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 14 18:11:53 2005 Return-Path: X-Original-To: amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F286B16A41F; Wed, 14 Dec 2005 18:11:52 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6895F43D79; Wed, 14 Dec 2005 18:11:39 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jBEIBaEN075786; Wed, 14 Dec 2005 20:11:37 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 41721-02-9; Wed, 14 Dec 2005 20:11:35 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jBEI9lgF075642 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Dec 2005 20:09:47 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.4/8.13.4) id jBEI9sMb052830; Wed, 14 Dec 2005 20:09:54 +0200 (EET) (envelope-from ru) Date: Wed, 14 Dec 2005 20:09:54 +0200 From: Ruslan Ermilov To: Kirill Ponomarew , Kris Kennaway Message-ID: <20051214180954.GD51686@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PmA2V3Z32TCmWXqI" Content-Disposition: inline User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua Cc: amd64@FreeBSD.org Subject: [patch] mixed i386/amd64 ports semi-broken X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 18:11:53 -0000 --PmA2V3Z32TCmWXqI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi there, I hit this problem attempting to install print/acroread7 on amd64. It depends on emulators/linux_base-8, which rewrites ${ARCH} from "amd64" to "i386". Unfortunately, when linux_base-8 is processed in a submake, e.g., when I run "make fetch-recursive" in print/acroread7, no rewrite of ${ARCH} actually happens because bsd.port.mk mistakenly thinks that ${ARCH} can never change, so it's getting passed ARCH already set to "amd64", and as a highest priority command-line type make(1) variable. This results in ${MD5_FILE} improperly set to distinfo.amd64 which doesn't exist. Here's a fix: %%% Index: bsd.port.mk =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/ports/Mk/bsd.port.mk,v retrieving revision 1.518 diff -u -p -r1.518 bsd.port.mk --- bsd.port.mk 8 Nov 2005 09:02:51 -0000 1.518 +++ bsd.port.mk 14 Dec 2005 17:54:40 -0000 @@ -5071,7 +5071,6 @@ __softMAKEFLAGS+=3D '${softvar}+=3D${${ .if !defined(NOPRECIOUSMAKEVARS) # These won't change, so we can pass them through the environment .MAKEFLAGS: \ - ARCH=3D"${ARCH:S/"/"'"'"/g:S/\$/\$\$/g:S/\\/\\\\/g}" \ OPSYS=3D"${OPSYS:S/"/"'"'"/g:S/\$/\$\$/g:S/\\/\\\\/g}" \ OSREL=3D"${OSREL:S/"/"'"'"/g:S/\$/\$\$/g:S/\\/\\\\/g}" \ OSVERSION=3D"${OSVERSION:S/"/"'"'"/g:S/\$/\$\$/g:S/\\/\\\\/g}" \ %%% Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --PmA2V3Z32TCmWXqI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDoF/yqRfpzJluFF4RAtxmAJ9zbC6Y53nNK069xEzvQHsGMKcS2QCeNYxK Xolp57KHlMr7nAMccMybEwA= =E2o5 -----END PGP SIGNATURE----- --PmA2V3Z32TCmWXqI-- From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 14 18:52:11 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B70416A420 for ; Wed, 14 Dec 2005 18:52:11 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 462A243D88 for ; Wed, 14 Dec 2005 18:51:56 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3806130 for multiple; Wed, 14 Dec 2005 13:49:53 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jBEIppq3058500; Wed, 14 Dec 2005 13:51:51 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org, Roger Marquis Date: Wed, 14 Dec 2005 12:23:09 -0500 User-Agent: KMail/1.8.2 References: <200512141610.jBEGA6QA073657@freefall.freebsd.org> In-Reply-To: <200512141610.jBEGA6QA073657@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512141223.10738.jhb@freebsd.org> X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Subject: Re: amd64/90267: nmap fails under amd64 5.4-REL X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 18:52:11 -0000 On Wednesday 14 December 2005 11:10 am, Roger Marquis wrote: > The following reply was made to PR amd64/90267; it has been noted by GNATS. > > From: Roger Marquis > To: John Baldwin > Cc: FreeBSD-gnats-submit@freebsd.org > Subject: Re: amd64/90267: nmap fails under amd64 5.4-REL > Date: Wed, 14 Dec 2005 08:05:34 -0800 (PST) > > John Baldwin wrote: > >>>Are you running it as root? > >> > >> Yes > >> Does nmap work under FreeBSD/i386 on the same hardware? > > > > Yes > > > >> ... > > This bug is fixed in nmap-3.95. Thanks John! Ah, great news then. Thanks. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 14 23:27:31 2005 Return-Path: X-Original-To: amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5625916A41F for ; Wed, 14 Dec 2005 23:27:31 +0000 (GMT) (envelope-from plehner2000@yahoo.com) Received: from web81801.mail.mud.yahoo.com (web81801.mail.mud.yahoo.com [68.142.207.166]) by mx1.FreeBSD.org (Postfix) with SMTP id DE89B43D5A for ; Wed, 14 Dec 2005 23:27:30 +0000 (GMT) (envelope-from plehner2000@yahoo.com) Received: (qmail 61210 invoked by uid 60001); 14 Dec 2005 23:27:29 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=f2vzpJBYxSykof2UMKtHH0v4lhvLPiFfBgYmDXAaCuAbRdIfzR1DhIBtMNFWU9ASRNR6EVvUGrmci+suqOTJeDVa0UHzakhPjIym8ciINcW3uNObDe0xTvseQKxAjdGYFnh6M6LVhi6ishiiiC6xSADMwAS6NAoh50p1bTxx0T4= ; Message-ID: <20051214232729.61207.qmail@web81801.mail.mud.yahoo.com> Received: from [64.56.206.254] by web81801.mail.mud.yahoo.com via HTTP; Wed, 14 Dec 2005 15:27:29 PST Date: Wed, 14 Dec 2005 15:27:29 -0800 (PST) From: Patrick Lehner To: amd64@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Did anyone get the native quake3 port sucessfully built on 5.4? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 23:27:31 -0000 I am getting the following error output: Install release-x86-FreeBSD-/Q3/q3_ui/q3_ui/ui.qvm as install/baseq3/vm/ui.qvm cc -pipe -fsigned-char -I/usr/local/include -L/usr/local/lib -I/usr/X11R6/include -L/usr/X11R6/lib -DNDEBUG -O6 -fomit-frame-pointer -ffast-math -falign-loops=2 -falign-jumps=2 -falign-functions=2 -fno-strict-aliasing -fstrength-reduce -DDEDICATED -DC_ONLY -c release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c -o release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.o release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:79: error: initializer element is not constant release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:83: error: initializer element is not constant release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c: In function `VM_Compile': release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:455: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:465: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:475: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:491: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:506: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:521: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:561: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:566: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:594: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:597: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:602: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:607: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:624: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:629: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:635: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:640: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:654: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:660: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:666: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:672: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:683: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:692: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:701: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:713: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:723: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:733: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:743: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:753: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:763: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:773: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:783: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:793: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:803: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:815: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:827: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:839: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:851: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:863: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:875: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:1029: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:1045: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:1065: warning: cast from pointer to integer of different size release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c: In function `VM_CallCompiled': release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:1163: warning: matching constraint does not allow a register release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:1163: warning: matching constraint does not allow a register release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:1163: warning: matching constraint does not allow a register release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.c:1163: warning: matching constraint does not allow a register cons: *** [release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.o] Error 1 cons: errors constructing release-x86-FreeBSD-/core/dedicated/qcommon/vm_x86.o *** Error code 22 Stop in /usr/ports/games/quake3. Thanks you very much From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 15 07:36:15 2005 Return-Path: X-Original-To: amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E32B016A41F for ; Thu, 15 Dec 2005 07:36:15 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: from blue-ld-038.synserver.de (blue-ld-038.synserver.de [217.119.50.239]) by mx1.FreeBSD.org (Postfix) with SMTP id D73D843D69 for ; Thu, 15 Dec 2005 07:36:14 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: (qmail 2844 invoked by uid 0); 15 Dec 2005 07:36:12 -0000 X-SynServer-RemoteDnsName: port-212-202-34-162.dynamic.qsc.de X-SynServer-AuthUser: markus@trippelsdorf.de Received: from port-212-202-34-162.dynamic.qsc.de (HELO bsd.trippelsdorf.de) (212.202.34.162) by mx-06.synserver.de with SMTP; 15 Dec 2005 07:36:12 -0000 Date: Thu, 15 Dec 2005 08:36:11 +0100 From: Markus Trippelsdorf To: Patrick Lehner Message-ID: <20051215073611.GA927@bsd.trippelsdorf.de> References: <20051214232729.61207.qmail@web81801.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051214232729.61207.qmail@web81801.mail.mud.yahoo.com> Cc: amd64@FreeBSD.org Subject: Re: Did anyone get the native quake3 port sucessfully built on 5.4? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 07:36:16 -0000 On Wed, Dec 14, 2005 at 03:27:29PM -0800, Patrick Lehner wrote: > I am getting the following error output: >... The quake port is for i386 only and should be marked as such. But there are efforts underway to port it to amd64, see: http://g-rave.nl/quake3.xht -- Markus From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 15 09:41:23 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A31D16A41F; Thu, 15 Dec 2005 09:41:23 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.178.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA9FF43D45; Thu, 15 Dec 2005 09:41:21 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [217.185.96.176] (manz-d9b960b0.pool.mediaWays.net [217.185.96.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate2.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 4AD803001174; Thu, 15 Dec 2005 10:41:15 +0100 (CET) Message-ID: <43A13A36.8030304@mail.uni-mainz.de> Date: Thu, 15 Dec 2005 10:41:10 +0100 From: "O. Hartmann" User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ron Dzierwa References: <439EFF19.958D6326@comcast.net> In-Reply-To: <439EFF19.958D6326@comcast.net> Content-Type: multipart/mixed; boundary="------------070206000304090603090709" X-Virus-Scanned: by amavisd-new at uni-mainz.de X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: glewis@freebsd.org, freebsd-amd64@FreeBSD.org Subject: Re: jdk15 on 6.0-RELEASE amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 09:41:23 -0000 This is a multi-part message in MIME format. --------------070206000304090603090709 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Ron Dzierwa wrote: >I am trying to install the native jdk15 on a new installation of 6.0-RELEASE-amd64 > >i got the three packages: > jdk-1_5_0-bin-scsl.zip > jdk-1_5_0-src-scsl.zip > bsd-jdk15-patches-2.tar.bz2 > >put them in distfiles, then did make in /usr/ports/java/jdk15. it runs along for a while, then: > >===> Applying FreeBSD patches for jdk-1.5.0p2_3 >Ignoring previously applied (or reversed) patch. >1 out of 1 hunks ignored--saving rejects to ../../hotspot/src/os/bsd/vm/os_bsd.inline.hpp.rej >=> Patch patch-hotspot-vm-os_bsd.inline.hpp failed to apply cleanly. >=> Patch(es) patch-control::common::Defs-bsd.gmk patch-deploy::common::Defs-bsd.gmk patch-dep >loy::common::DeployRules-solaris.gmk patch-deploy::native::msgString.c patch-deploy::native:: >system_md.c patch-deploy::native::system_md.h patch-deploy::ns7-adapter::Makefile applied cle >anly. >*** Error code 1 > >Stop in /usr/ports/java/jdk15. > >the contents of ./work/hotspot/src/os/bsd/vm/os_bsd.inline.hpp.rej is: > >*************** >*** 29,38 **** > > inline bool os::allocate_stack_guard_pages() { > assert(uses_stack_guard_pages(), "sanity check"); >- // XXXBSD: ?? >- // return thr_main(); >- // return pthread_main_np(); >- return true; > } > > >--- 29,37 ---- > > inline bool os::allocate_stack_guard_pages() { > assert(uses_stack_guard_pages(), "sanity check"); >+ // Since FreeBSD 4 uses malloc() for allocating the thread stack >+ // there is no need to do anything extra to allocate the guard pages >+ return false; > } > > >any ideas? > >any help installing any 1.4 or 1.5 (preferably) jdk would be appreciated. > >thanks, >ron. > > >_______________________________________________ >freebsd-amd64@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 >To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > > Tried installing JDK15 again. Fresh install of the supported Linux_base-8, the necessary linux-sun-jdk14. Then compiling jdk15, most recent ports tree update (I do this nearly every day or once a week). This is what I receive. The mentioned error file is attached: ../../../../../src/share/classes/java/io/ObjectStreamClass.java:1006: warning: non-varargs call of varargs method with inexact argument type for last parameter; cast to java.lang.Object for a varargs call cast to java.lang.Object[] for a non-varargs call and to suppress this warning return readResolveMethod.invoke(obj, null); ^ # # An unexpected error has been detected by HotSpot Virtual Machine: # # Internal Error (4E4D4554484F440E435050051B), pid=54296, tid=0x513000 # # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0-p2-root_14_dec_2005_18_55 mixed mode) # An error report file with more information is saved as hs_err_pid54296.log # # If you would like to submit a bug report, please write # a letter to freebsd-java@FreeBSD.org mailing list # Abort trap gmake[7]: *** [.compile.classlist] Error 134 gmake[7]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/sun/javac/recompile/library' gmake[6]: *** [optimized] Error 2 gmake[6]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/sun/javac/recompile/library' gmake[5]: *** [all] Error 1 gmake[5]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/sun/javac/recompile' gmake[4]: *** [all] Error 1 gmake[4]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/sun/javac' gmake[3]: *** [all] Error 2 gmake[3]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/java/javac' gmake[2]: *** [all] Error 1 gmake[2]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/java' gmake[1]: *** [all] Error 1 gmake[1]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make' gmake: *** [j2se-build] Error 2 *** Error code 2 Stop in /usr/ports/java/jdk15. --------------070206000304090603090709 Content-Type: text/plain; name="hs_err_pid54296.log" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline; filename="hs_err_pid54296.log" # # An unexpected error has been detected by HotSpot Virtual Machine: # # Internal Error (4E4D4554484F440E435050051B), pid=3D54296, tid=3D0x5130= 00 # # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0-p2-root_14_dec_2005_1= 8_55 mixed mode) --------------- T H R E A D --------------- Current thread (0x000000000052f400): JavaThread "main" [_thread_in_Java,= id=3D5320704] Stack: [0x00007fffffc00000,0x0000800000000000), sp=3D0x00007fffffff40c0,= free space=3D4048k Native frames: (J=3Dcompiled Java code, j=3Dinterpreted, Vv=3DVM code, C=3D= native code) V [libjvm.so+0x79063e] V [libjvm.so+0x465c56] V [libjvm.so+0x698eab] V [libjvm.so+0x70aa78] V [libjvm.so+0x6ac3e4] V [libjvm.so+0x6aae1e] --------------- P R O C E S S --------------- Java Threads: ( =3D> current thread ) 0x000000000060d800 JavaThread "Low Memory Detector" daemon [_thread_blo= cked, id=3D6331392] 0x000000000060bc00 JavaThread "CompilerThread1" daemon [_thread_in_nati= ve, id=3D6330368] 0x000000000060b000 JavaThread "CompilerThread0" daemon [_thread_in_nati= ve, id=3D6329344] 0x00000000005f7400 JavaThread "AdapterThread" daemon [_thread_blocked, = id=3D6229504] 0x00000000005ee800 JavaThread "Signal Dispatcher" daemon [_thread_block= ed, id=3D6228992] 0x00000000005ee000 JavaThread "Finalizer" daemon [_thread_blocked, id=3D= 6208512] 0x00000000005adc00 JavaThread "Reference Handler" daemon [_thread_block= ed, id=3D6208000] =3D>0x000000000052f400 JavaThread "main" [_thread_in_Java, id=3D5320704] Other Threads: 0x00000000005e1800 VMThread [id=3D6167040] 0x0000000000532800 WatcherThread [id=3D6331904] VM state:synchronizing (normal execution) VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event]) [0x000000000052c580/0x000000000052c600] Safepoint_lock - owner thread: 0x= 00000000005e1800 [0x000000000052c700/0x000000000052c780] Threads_lock - owner thread: 0x00= 000000005e1800 Heap def new generation total 38656K, used 23746K [0x0000000842b00000, 0x00= 000008454f0000, 0x0000000848050000) eden space 34368K, 61% used [0x0000000842b00000, 0x0000000843f9ff68, 0= x0000000844c90000) from space 4288K, 61% used [0x00000008450c0000, 0x0000000845350a40, 0x= 00000008454f0000) to space 4288K, 0% used [0x0000000844c90000, 0x0000000844c90000, 0x= 00000008450c0000) tenured generation total 85876K, used 66357K [0x0000000848050000, 0x00= 0000084d42d000, 0x0000000852b00000) the space 85876K, 77% used [0x0000000848050000, 0x000000084c11d6b0, 0= x000000084c11d800, 0x000000084d42d000) compacting perm gen total 21248K, used 5080K [0x0000000852b00000, 0x000= 0000853fc0000, 0x0000000857d00000) the space 21248K, 23% used [0x0000000852b00000, 0x0000000852ff6018, 0= x0000000852ff6200, 0x0000000853fc0000) No shared spaces configured. Dynamic libraries: 0x0000000000400000 /usr/ports/java/jdk15/work/control/build/bsd-amd64/bi= n/javac 0x0000000800639000 /usr/lib/libthr.so.2 0x0000000800750000 /lib/libc.so.6 0x000000080094d000 /usr/ports/java/jdk15/work/control/build/bsd-amd64/li= b/amd64/server/libjvm.so 0x0000000801386000 /usr/lib/libstdc++.so.5 0x000000080157d000 /lib/libm.so.4 0x0000000801699000 /usr/ports/java/jdk15/work/control/build/bsd-amd64/li= b/amd64/native_threads/libhpi.so 0x00000008017a5000 /usr/ports/java/jdk15/work/control/build/bsd-amd64/li= b/amd64/libverify.so 0x00000008018b4000 /usr/ports/java/jdk15/work/control/build/bsd-amd64/li= b/amd64/libjava.so 0x00000008019dc000 /usr/ports/java/jdk15/work/control/build/bsd-amd64/li= b/amd64/libzip.so 0x000000080050f000 /libexec/ld-elf.so.1 VM Arguments: jvm_args: -Denv.class.path=3D -Dapplication.home=3D/usr/ports/java/jdk15/= work/control/build/bsd-amd64 -Xms8m -Xss4m -ea:com.sun.tools... -XX:Threa= dStackSize=3D1536 -Xms64m -Xmx256m java_command: com.sun.tools.javac.Main -classpath /usr/ports/java/jdk15/w= ork/control/build/bsd-amd64/tmp/java/java.lang/library/newclasses:../../.= =2E/../../src/share/classes -bootclasspath /usr/ports/java/jdk15/work/con= trol/build/bsd-amd64/lib/jce.jar:/usr/ports/java/jdk15/work/control/build= /bsd-amd64/lib/jsse.jar -sourcepath /usr/ports/java/jdk15/work/control/bu= ild/bsd-amd64/gensrc:../../../../../src/solaris/classes:../../../../../sr= c/share/classes -d /usr/ports/java/jdk15/work/control/build/bsd-amd64/tmp= /java/java.lang/library/newclasses -encoding ascii -source 1.5 ../../../.= =2E/../src/share/classes/java/lang/Object.java ../../../../../src/share/c= lasses/java/lang/Class.java ../../../../../src/share/classes/java/lang/Th= read.java ../../../../../src/share/classes/java/lang/Character.java ../..= /../../../src/share/classes/sun/misc/ASCIICaseInsensitiveComparator.java = =2E./../../../../src/share/classes/sun/misc/VM.java ../../../../../src/sh= are/classes/sun/misc/Signal.java ../../../../../src/share/classes/sun/mis= c/NativeSignalHandler.java ../../../../../src/share/classes/java/lang/Thr= eadGroup.java ../../../../../src/share/classes/java/lang/ThreadLocal.java= ../../../../../src/share/classes/java/lang/InheritableThreadLocal.java .= =2E/../../../../src/share/classes/java/lang/String.java ../../../../../sr= c/share/classes/java/lang/ConditionalSpecialCasing.java ../../../../../sr= c/share/classes/java/lang/StringCoding.java ../../../../../src/share/clas= ses/java/lang/StringBuffer.java ../../../../../src/share/classes/java/lan= g/StringBuilder.java ../../../../../src/share/classes/java/lang/SuppressW= arnings.java ../../../../../src/share/classes/java/lang/AbstractStringBui= lder.java ../../../../../src/share/classes/java/lang/ClassLoader.java ../= =2E./../../../src/share/classes/java/lang/AssertionStatusDirectives.java = =2E./../../../../src/share/classes/java/lang/Enum.java ../../../../../src= /share/classes/java/lang/StrictMath.java ../../../../../src/share/classes= /java/lang/Math.java ../../../../../src Environment Variables: JAVA_HOME=3D CLASSPATH=3D PATH=3D/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/loca= l/bin:/usr/X11R6/bin:/usr/local/samba/bin:/usr/local/mysql/bin:/root/bin:= /usr/local/scripts/admin:/usr/local/scripts/public:usr/local/gmt/bin LD_LIBRARY_PATH=3D/usr/ports/java/jdk15/work/control/build/bsd-amd64/lib/= amd64/server:/usr/ports/java/jdk15/work/control/build/bsd-amd64/lib/amd64= :/usr/ports/java/jdk15/work/control/build/bsd-amd64/../lib/amd64: SHELL=3D/bin/sh HOSTTYPE=3DFreeBSD OSTYPE=3DFreeBSD ARCH=3Damd64 MACHTYPE=3Dunknown --------------- S Y S T E M --------------- OS:FreeBSD uname:FreeBSD 6.0-STABLE FreeBSD 6.0-STABLE #158: Mon Dec 12 22:29:27 CET= 2005 root@thor.schanze.de:/usr/obj/usr/src/sys/THOR amd64 rlimit: STACK 524288k, CORE infinity, NOFILE 11095 CPU:total 1=20 Memory: 4k page, physical 262144k vm_info: Java HotSpot(TM) 64-Bit Server VM (1.5.0-p2-root_14_dec_2005_18_= 55) for freebsd-amd64, built on Dec 14 2005 19:38:30 by root with gcc 3.4= =2E4 [FreeBSD] 20050518 --------------070206000304090603090709-- From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 15 09:46:33 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDBC416A425; Thu, 15 Dec 2005 09:46:33 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.178.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 267D043D9C; Thu, 15 Dec 2005 09:45:52 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [217.185.96.176] (manz-d9b960b0.pool.mediaWays.net [217.185.96.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate2.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 7EE88300171D; Thu, 15 Dec 2005 10:45:37 +0100 (CET) Message-ID: <43A13B40.3000601@mail.uni-mainz.de> Date: Thu, 15 Dec 2005 10:45:36 +0100 From: "O. Hartmann" User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "O. Hartmann" References: <439EFF19.958D6326@comcast.net> <43A13A36.8030304@mail.uni-mainz.de> In-Reply-To: <43A13A36.8030304@mail.uni-mainz.de> Content-Type: multipart/mixed; boundary="------------090408060107030003060301" X-Virus-Scanned: by amavisd-new at uni-mainz.de X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: glewis@freebsd.org, freebsd-amd64@FreeBSD.org, Ron Dzierwa Subject: Re: jdk15 on 6.0-RELEASE amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 09:46:34 -0000 This is a multi-part message in MIME format. --------------090408060107030003060301 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable O. Hartmann wrote: >Ron Dzierwa wrote: > > =20 > >>I am trying to install the native jdk15 on a new installation of 6.0-RE= LEASE-amd64 >> >>i got the three packages: >> jdk-1_5_0-bin-scsl.zip >> jdk-1_5_0-src-scsl.zip >> bsd-jdk15-patches-2.tar.bz2 >> >>put them in distfiles, then did make in /usr/ports/java/jdk15. it runs = along for a while, then: >> >>=3D=3D=3D> Applying FreeBSD patches for jdk-1.5.0p2_3 >>Ignoring previously applied (or reversed) patch. >>1 out of 1 hunks ignored--saving rejects to ../../hotspot/src/os/bsd/vm= /os_bsd.inline.hpp.rej >>=3D> Patch patch-hotspot-vm-os_bsd.inline.hpp failed to apply cleanly. >>=3D> Patch(es) patch-control::common::Defs-bsd.gmk patch-deploy::common= ::Defs-bsd.gmk patch-dep >>loy::common::DeployRules-solaris.gmk patch-deploy::native::msgString.c = patch-deploy::native:: >>system_md.c patch-deploy::native::system_md.h patch-deploy::ns7-adapter= ::Makefile applied cle >>anly. >>*** Error code 1 >> >>Stop in /usr/ports/java/jdk15. >> >>the contents of ./work/hotspot/src/os/bsd/vm/os_bsd.inline.hpp.rej is: >> >>*************** >>*** 29,38 **** >> >> inline bool os::allocate_stack_guard_pages() { >> assert(uses_stack_guard_pages(), "sanity check"); >>- // XXXBSD: ?? >>- // return thr_main(); >>- // return pthread_main_np(); >>- return true; >> } >> >> >>--- 29,37 ---- >> >> inline bool os::allocate_stack_guard_pages() { >> assert(uses_stack_guard_pages(), "sanity check"); >>+ // Since FreeBSD 4 uses malloc() for allocating the thread stack >>+ // there is no need to do anything extra to allocate the guard page= s >>+ return false; >> } >> >> >>any ideas? >> >>any help installing any 1.4 or 1.5 (preferably) jdk would be appreciat= ed. >> >>thanks, >>ron. >> >> >>_______________________________________________ >>freebsd-amd64@freebsd.org mailing list >>http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 >>To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org= " >>=20 >> >> =20 >> >Tried installing JDK15 again. Fresh install of the supported >Linux_base-8, the necessary linux-sun-jdk14. Then compiling jdk15, most >recent ports tree update (I do this nearly every day or once a week). >This is what I receive. The mentioned error file is attached: >../../../../../src/share/classes/java/io/ObjectStreamClass.java:1006: >warning: >non-varargs call of varargs method with inexact argument type for last >parameter; >cast to java.lang.Object for a varargs call >cast to java.lang.Object[] for a non-varargs call and to suppress this >warning > return readResolveMethod.invoke(obj, null); > ^ ># ># An unexpected error has been detected by HotSpot Virtual Machine: ># ># Internal Error (4E4D4554484F440E435050051B), pid=3D54296, tid=3D0x513= 000 ># ># Java VM: Java HotSpot(TM) 64-Bit Server VM >(1.5.0-p2-root_14_dec_2005_18_55 >mixed mode) ># An error report file with more information is saved as hs_err_pid54296= =2Elog ># ># If you would like to submit a bug report, please write ># a letter to freebsd-java@FreeBSD.org mailing list ># >Abort trap >gmake[7]: *** [.compile.classlist] Error 134 >gmake[7]: Leaving directory >`/usr/ports/java/jdk15/work/j2se/make/sun/javac/recompile/library' >gmake[6]: *** [optimized] Error 2 >gmake[6]: Leaving directory >`/usr/ports/java/jdk15/work/j2se/make/sun/javac/recompile/library' >gmake[5]: *** [all] Error 1 >gmake[5]: Leaving directory >`/usr/ports/java/jdk15/work/j2se/make/sun/javac/recompile' >gmake[4]: *** [all] Error 1 >gmake[4]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/sun/ja= vac' >gmake[3]: *** [all] Error 2 >gmake[3]: Leaving directory >`/usr/ports/java/jdk15/work/j2se/make/java/javac' >gmake[2]: *** [all] Error 1 >gmake[2]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/java' >gmake[1]: *** [all] Error 1 >gmake[1]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make' >gmake: *** [j2se-build] Error 2 >*** Error code 2 > >Stop in /usr/ports/java/jdk15. > > > > > =20 > >------------------------------------------------------------------------= > ># ># An unexpected error has been detected by HotSpot Virtual Machine: ># ># Internal Error (4E4D4554484F440E435050051B), pid=3D54296, tid=3D0x513= 000 ># ># Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0-p2-root_14_dec_2005_= 18_55 mixed mode) > >--------------- T H R E A D --------------- > >Current thread (0x000000000052f400): JavaThread "main" [_thread_in_Java= , id=3D5320704] > >Stack: [0x00007fffffc00000,0x0000800000000000), sp=3D0x00007fffffff40c0= , free space=3D4048k >Native frames: (J=3Dcompiled Java code, j=3Dinterpreted, Vv=3DVM code, C= =3Dnative code) >V [libjvm.so+0x79063e] >V [libjvm.so+0x465c56] >V [libjvm.so+0x698eab] >V [libjvm.so+0x70aa78] >V [libjvm.so+0x6ac3e4] >V [libjvm.so+0x6aae1e] > > >--------------- P R O C E S S --------------- > >Java Threads: ( =3D> current thread ) > 0x000000000060d800 JavaThread "Low Memory Detector" daemon [_thread_bl= ocked, id=3D6331392] > 0x000000000060bc00 JavaThread "CompilerThread1" daemon [_thread_in_nat= ive, id=3D6330368] > 0x000000000060b000 JavaThread "CompilerThread0" daemon [_thread_in_nat= ive, id=3D6329344] > 0x00000000005f7400 JavaThread "AdapterThread" daemon [_thread_blocked,= id=3D6229504] > 0x00000000005ee800 JavaThread "Signal Dispatcher" daemon [_thread_bloc= ked, id=3D6228992] > 0x00000000005ee000 JavaThread "Finalizer" daemon [_thread_blocked, id=3D= 6208512] > 0x00000000005adc00 JavaThread "Reference Handler" daemon [_thread_bloc= ked, id=3D6208000] >=3D>0x000000000052f400 JavaThread "main" [_thread_in_Java, id=3D5320704]= > >Other Threads: > 0x00000000005e1800 VMThread [id=3D6167040] > 0x0000000000532800 WatcherThread [id=3D6331904] > >VM state:synchronizing (normal execution) > >VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event]) >[0x000000000052c580/0x000000000052c600] Safepoint_lock - owner thread: 0= x00000000005e1800 >[0x000000000052c700/0x000000000052c780] Threads_lock - owner thread: 0x0= 0000000005e1800 > >Heap > def new generation total 38656K, used 23746K [0x0000000842b00000, 0x0= 0000008454f0000, 0x0000000848050000) > eden space 34368K, 61% used [0x0000000842b00000, 0x0000000843f9ff68, = 0x0000000844c90000) > from space 4288K, 61% used [0x00000008450c0000, 0x0000000845350a40, 0= x00000008454f0000) > to space 4288K, 0% used [0x0000000844c90000, 0x0000000844c90000, 0= x00000008450c0000) > tenured generation total 85876K, used 66357K [0x0000000848050000, 0x0= 00000084d42d000, 0x0000000852b00000) > the space 85876K, 77% used [0x0000000848050000, 0x000000084c11d6b0, = 0x000000084c11d800, 0x000000084d42d000) > compacting perm gen total 21248K, used 5080K [0x0000000852b00000, 0x00= 00000853fc0000, 0x0000000857d00000) > the space 21248K, 23% used [0x0000000852b00000, 0x0000000852ff6018, = 0x0000000852ff6200, 0x0000000853fc0000) >No shared spaces configured. > >Dynamic libraries: >0x0000000000400000 /usr/ports/java/jdk15/work/control/build/bsd-amd64/b= in/javac >0x0000000800639000 /usr/lib/libthr.so.2 >0x0000000800750000 /lib/libc.so.6 >0x000000080094d000 /usr/ports/java/jdk15/work/control/build/bsd-amd64/l= ib/amd64/server/libjvm.so >0x0000000801386000 /usr/lib/libstdc++.so.5 >0x000000080157d000 /lib/libm.so.4 >0x0000000801699000 /usr/ports/java/jdk15/work/control/build/bsd-amd64/l= ib/amd64/native_threads/libhpi.so >0x00000008017a5000 /usr/ports/java/jdk15/work/control/build/bsd-amd64/l= ib/amd64/libverify.so >0x00000008018b4000 /usr/ports/java/jdk15/work/control/build/bsd-amd64/l= ib/amd64/libjava.so >0x00000008019dc000 /usr/ports/java/jdk15/work/control/build/bsd-amd64/l= ib/amd64/libzip.so >0x000000080050f000 /libexec/ld-elf.so.1 > >VM Arguments: >jvm_args: -Denv.class.path=3D -Dapplication.home=3D/usr/ports/java/jdk15= /work/control/build/bsd-amd64 -Xms8m -Xss4m -ea:com.sun.tools... -XX:Thre= adStackSize=3D1536 -Xms64m -Xmx256m >java_command: com.sun.tools.javac.Main -classpath /usr/ports/java/jdk15/= work/control/build/bsd-amd64/tmp/java/java.lang/library/newclasses:../../= =2E./../../src/share/classes -bootclasspath /usr/ports/java/jdk15/work/co= ntrol/build/bsd-amd64/lib/jce.jar:/usr/ports/java/jdk15/work/control/buil= d/bsd-amd64/lib/jsse.jar -sourcepath /usr/ports/java/jdk15/work/control/b= uild/bsd-amd64/gensrc:../../../../../src/solaris/classes:../../../../../s= rc/share/classes -d /usr/ports/java/jdk15/work/control/build/bsd-amd64/tm= p/java/java.lang/library/newclasses -encoding ascii -source 1.5 ../../../= =2E./../src/share/classes/java/lang/Object.java ../../../../../src/share/= classes/java/lang/Class.java ../../../../../src/share/classes/java/lang/T= hread.java ../../../../../src/share/classes/java/lang/Character.java ../.= =2E/../../../src/share/classes/sun/misc/ASCIICaseInsensitiveComparator.ja= va ../../../../../src/share/classes/sun/misc/VM.java ../../../../../src/s= hare/classes/sun/misc/Signal.java ../../../../../src/share/classes/sun/mi= sc/NativeSignalHandler.java ../../../../../src/share/classes/java/lang/Th= readGroup.java ../../../../../src/share/classes/java/lang/ThreadLocal.jav= a ../../../../../src/share/classes/java/lang/InheritableThreadLocal.java = =2E./../../../../src/share/classes/java/lang/String.java ../../../../../s= rc/share/classes/java/lang/ConditionalSpecialCasing.java ../../../../../s= rc/share/classes/java/lang/StringCoding.java ../../../../../src/share/cla= sses/java/lang/StringBuffer.java ../../../../../src/share/classes/java/la= ng/StringBuilder.java ../../../../../src/share/classes/java/lang/Suppress= Warnings.java ../../../../../src/share/classes/java/lang/AbstractStringBu= ilder.java ../../../../../src/share/classes/java/lang/ClassLoader.java ..= /../../../../src/share/classes/java/lang/AssertionStatusDirectives.java .= =2E/../../../../src/share/classes/java/lang/Enum.java ../../../../../src/= share/classes/java/lang/StrictMath.java ../../../../../src/share/classes/= java/lang/Math.java ../../../../../src > >Environment Variables: >JAVA_HOME=3D >CLASSPATH=3D >PATH=3D/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/loc= al/bin:/usr/X11R6/bin:/usr/local/samba/bin:/usr/local/mysql/bin:/root/bin= :/usr/local/scripts/admin:/usr/local/scripts/public:usr/local/gmt/bin >LD_LIBRARY_PATH=3D/usr/ports/java/jdk15/work/control/build/bsd-amd64/lib= /amd64/server:/usr/ports/java/jdk15/work/control/build/bsd-amd64/lib/amd6= 4:/usr/ports/java/jdk15/work/control/build/bsd-amd64/../lib/amd64: >SHELL=3D/bin/sh >HOSTTYPE=3DFreeBSD >OSTYPE=3DFreeBSD >ARCH=3Damd64 >MACHTYPE=3Dunknown > > >--------------- S Y S T E M --------------- > >OS:FreeBSD >uname:FreeBSD 6.0-STABLE FreeBSD 6.0-STABLE #158: Mon Dec 12 22:29:27 CE= T 2005 root@thor.schanze.de:/usr/obj/usr/src/sys/THOR amd64 >rlimit: STACK 524288k, CORE infinity, NOFILE 11095 >CPU:total 1=20 > >Memory: 4k page, physical 262144k > >vm_info: Java HotSpot(TM) 64-Bit Server VM (1.5.0-p2-root_14_dec_2005_18= _55) for freebsd-amd64, built on Dec 14 2005 19:38:30 by root with gcc 3.= 4.4 [FreeBSD] 20050518 > > =20 > >------------------------------------------------------------------------= > >_______________________________________________ >freebsd-amd64@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 >To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org"= > =20 > Forgot to say I'm using FreeBSD 6.0-STABLE as most recent cvsupdated and compiled. --------------090408060107030003060301-- From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 15 12:37:52 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 344EF16A41F for ; Thu, 15 Dec 2005 12:37:52 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.178.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFEF243D55 for ; Thu, 15 Dec 2005 12:37:51 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [134.93.180.123] (ipamzra.Physik.Uni-Mainz.DE [134.93.180.123]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate2.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 617F0300098C for ; Thu, 15 Dec 2005 13:37:50 +0100 (CET) Message-ID: <43A1636A.6030108@mail.uni-mainz.de> Date: Thu, 15 Dec 2005 13:36:58 +0100 From: "O. Hartmann" User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de Subject: device drm with PCIe? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 12:37:52 -0000 Normally 'device drm' is only useable in conjunction with 'device agp'. A lot of amd64 based boxes now use PEG slots for their graphics accelerators. Is it possible to utilize 'drm' with PCIe devices? Does device agp has any effect on PCIe graphics accelerators? Thanks, Oliver From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 15 17:54:10 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E94116A41F for ; Thu, 15 Dec 2005 17:54:10 +0000 (GMT) (envelope-from tcumming123@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02A7843D55 for ; Thu, 15 Dec 2005 17:54:08 +0000 (GMT) (envelope-from tcumming123@gmail.com) Received: by nproxy.gmail.com with SMTP id l37so157444nfc for ; Thu, 15 Dec 2005 09:54:06 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Q/7f5Ragh6HqsIHR52BqyEBmNjx6x7Oa/EPt4/EM/Xjop9ymGRNkwovryLI7D/3OOme2pQDBDsvYIDi7hmIQtIQKEDj6nnyN/Ez04CykaV1+UkaE3BTQkDmBtdVIMKZLo7tlNuU7v5rlArpmltqgz5/3nuH6gzvo/Q8r9wbYVkg= Received: by 10.48.235.1 with SMTP id i1mr102361nfh; Thu, 15 Dec 2005 09:54:06 -0800 (PST) Received: by 10.48.162.4 with HTTP; Thu, 15 Dec 2005 09:54:06 -0800 (PST) Message-ID: Date: Thu, 15 Dec 2005 09:54:06 -0800 From: Tom Cumming To: Henry Vogt In-Reply-To: MIME-Version: 1.0 References: <43927A1D.9090003@cox.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD 6.0-Release AMD64 3DM2 3ware 7506-8 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 17:54:10 -0000 > Webinterface shows the following version info:Last updated Fri, Dec 09, > 2005 09:57.33AM > *3DM 2 version 2.04.00.011 (64 bit)* > I'll be damn. I thought that didn't work. I am curious though, is it running secure (i.e., https://localhost)? tom.c From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 15 18:35:54 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A9FE16A41F for ; Thu, 15 Dec 2005 18:35:54 +0000 (GMT) (envelope-from hv@tuebingen.mpg.de) Received: from tuebingen.mpg.de (smtp-out.tuebingen.mpg.de [192.124.26.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD33343D8B for ; Thu, 15 Dec 2005 18:35:37 +0000 (GMT) (envelope-from hv@tuebingen.mpg.de) Received: from [10.3.7.24] ([10.3.7.24] verified) by tuebingen.mpg.de (CommuniGate Pro SMTP 4.1.8) with ESMTP id 16344405; Thu, 15 Dec 2005 19:35:33 +0100 In-Reply-To: References: <43927A1D.9090003@cox.net> Mime-Version: 1.0 (Apple Message framework v746.2) Message-Id: <6C3C0031-788A-4F97-B1BD-5A1CE869E9DD@tuebingen.mpg.de> From: Henry Vogt Date: Thu, 15 Dec 2005 19:35:32 +0100 To: Tom Cumming X-Mailer: Apple Mail (2.746.2) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD 6.0-Release AMD64 3DM2 3ware 7506-8 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 18:35:54 -0000 Am 15.12.2005 um 18:54 schrieb Tom Cumming: > > Webinterface shows the following version info: > Last updated Fri, Dec 09, 2005 09:57.33AM > 3DM 2 version 2.04.00.011 (64 bit) > > I'll be damn. I thought that didn't work. > > I am curious though, is it running secure (i.e., https://=20 > localhost)? Althoug the same port, the i386 (32bit) version, always uses ssl - =20 the 64bit version doesn't seem to use ssl at all. Not sure, but i believe to have read this somewhere (on the 3ware =20 website?) that ssl is not (yet?) supported in the 64bit version. Hope that helps. --=20 Henry Vogt (Phone: ++49-7071-601-511) Network- and Systemadminstration Campus Max-Planck-Institutes, Spemannstr. 32-39, T=FCbingen, Germany From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 15 18:53:14 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8265216A420 for ; Thu, 15 Dec 2005 18:53:14 +0000 (GMT) (envelope-from RonDzierwa@comcast.net) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [63.240.77.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7599043D69 for ; Thu, 15 Dec 2005 18:53:05 +0000 (GMT) (envelope-from RonDzierwa@comcast.net) Received: from comcast.net (pcp0010489854pcs.essex01.md.comcast.net[69.143.77.148]) by comcast.net (sccrmhc12) with SMTP id <20051215184720012007kgcse>; Thu, 15 Dec 2005 18:47:20 +0000 Message-ID: <43A1BA56.1FCB8C40@comcast.net> Date: Thu, 15 Dec 2005 13:47:50 -0500 From: Ron Dzierwa X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "O. Hartmann" References: <439EFF19.958D6326@comcast.net> <43A13A36.8030304@mail.uni-mainz.de> <43A13B40.3000601@mail.uni-mainz.de> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-amd64@FreeBSD.org Subject: Re: jdk15 on 6.0-RELEASE amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 18:53:14 -0000 yeah, i eventually got it to work. my ports directory was trashed, and w= hen i updated it from ports.tar.gz, i simply untar'ed the new over the old, so the trash s= till existed. I needed to remove the directory and all its contents, then restore the new one. = Next was the build of the linux environment (linux_base-8). It doesn't build properly when = invoked as a dependency from the jdk15 build, you have to build it by itself before yo= u start the jdk15 build. After loading the linux 1.4 package into distfiles, it built succ= essfully, albeit with lots of warnings. I didn't get the vm internal error though... one thing i am still wrestling with is the firefox/mozilla plugin build. = The normal build didn't create it, i was wondering if you, or anybody else has got it to b= uild. I went to work/deploy/make and did a "gmake plugin-all" but it got compile errors. = it looks like it is not setting up the include directories correctly. any body have an= y ideas? thanks, ron. "O. Hartmann" wrote: > O. Hartmann wrote: > > >Ron Dzierwa wrote: > > > > > > > >>I am trying to install the native jdk15 on a new installation of 6.0-= RELEASE-amd64 > >> > >>i got the three packages: > >> jdk-1_5_0-bin-scsl.zip > >> jdk-1_5_0-src-scsl.zip > >> bsd-jdk15-patches-2.tar.bz2 > >> > >>put them in distfiles, then did make in /usr/ports/java/jdk15. it run= s along for a while, then: > >> > >>=3D=3D=3D> Applying FreeBSD patches for jdk-1.5.0p2_3 > >>Ignoring previously applied (or reversed) patch. > >>1 out of 1 hunks ignored--saving rejects to ../../hotspot/src/os/bsd/= vm/os_bsd.inline.hpp.rej > >>=3D> Patch patch-hotspot-vm-os_bsd.inline.hpp failed to apply cleanly= =2E > >>=3D> Patch(es) patch-control::common::Defs-bsd.gmk patch-deploy::comm= on::Defs-bsd.gmk patch-dep > >>loy::common::DeployRules-solaris.gmk patch-deploy::native::msgString.= c patch-deploy::native:: > >>system_md.c patch-deploy::native::system_md.h patch-deploy::ns7-adapt= er::Makefile applied cle > >>anly. > >>*** Error code 1 > >> > >>Stop in /usr/ports/java/jdk15. > >> > >>the contents of ./work/hotspot/src/os/bsd/vm/os_bsd.inline.hpp.rej is= : > >> > >>*************** > >>*** 29,38 **** > >> > >> inline bool os::allocate_stack_guard_pages() { > >> assert(uses_stack_guard_pages(), "sanity check"); > >>- // XXXBSD: ?? > >>- // return thr_main(); > >>- // return pthread_main_np(); > >>- return true; > >> } > >> > >> > >>--- 29,37 ---- > >> > >> inline bool os::allocate_stack_guard_pages() { > >> assert(uses_stack_guard_pages(), "sanity check"); > >>+ // Since FreeBSD 4 uses malloc() for allocating the thread stack > >>+ // there is no need to do anything extra to allocate the guard pa= ges > >>+ return false; > >> } > >> > >> > >>any ideas? > >> > >>any help installing any 1.4 or 1.5 (preferably) jdk would be appreci= ated. > >> > >>thanks, > >>ron. > >> > >> > >>_______________________________________________ > >>freebsd-amd64@freebsd.org mailing list > >>http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > >>To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.o= rg" > >> > >> > >> > >> > >Tried installing JDK15 again. Fresh install of the supported > >Linux_base-8, the necessary linux-sun-jdk14. Then compiling jdk15, mos= t > >recent ports tree update (I do this nearly every day or once a week). > >This is what I receive. The mentioned error file is attached: > >../../../../../src/share/classes/java/io/ObjectStreamClass.java:1006: > >warning: > >non-varargs call of varargs method with inexact argument type for last= > >parameter; > >cast to java.lang.Object for a varargs call > >cast to java.lang.Object[] for a non-varargs call and to suppress this= > >warning > > return readResolveMethod.invoke(obj, null); > > ^ > ># > ># An unexpected error has been detected by HotSpot Virtual Machine: > ># > ># Internal Error (4E4D4554484F440E435050051B), pid=3D54296, tid=3D0x5= 13000 > ># > ># Java VM: Java HotSpot(TM) 64-Bit Server VM > >(1.5.0-p2-root_14_dec_2005_18_55 > >mixed mode) > ># An error report file with more information is saved as hs_err_pid542= 96.log > ># > ># If you would like to submit a bug report, please write > ># a letter to freebsd-java@FreeBSD.org mailing list > ># > >Abort trap > >gmake[7]: *** [.compile.classlist] Error 134 > >gmake[7]: Leaving directory > >`/usr/ports/java/jdk15/work/j2se/make/sun/javac/recompile/library' > >gmake[6]: *** [optimized] Error 2 > >gmake[6]: Leaving directory > >`/usr/ports/java/jdk15/work/j2se/make/sun/javac/recompile/library' > >gmake[5]: *** [all] Error 1 > >gmake[5]: Leaving directory > >`/usr/ports/java/jdk15/work/j2se/make/sun/javac/recompile' > >gmake[4]: *** [all] Error 1 > >gmake[4]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/sun/= javac' > >gmake[3]: *** [all] Error 2 > >gmake[3]: Leaving directory > >`/usr/ports/java/jdk15/work/j2se/make/java/javac' > >gmake[2]: *** [all] Error 1 > >gmake[2]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/java= ' > >gmake[1]: *** [all] Error 1 > >gmake[1]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make' > >gmake: *** [j2se-build] Error 2 > >*** Error code 2 > > > >Stop in /usr/ports/java/jdk15. > > > > > > > > > > > > > >----------------------------------------------------------------------= -- > > > ># > ># An unexpected error has been detected by HotSpot Virtual Machine: > ># > ># Internal Error (4E4D4554484F440E435050051B), pid=3D54296, tid=3D0x5= 13000 > ># > ># Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0-p2-root_14_dec_200= 5_18_55 mixed mode) > > > >--------------- T H R E A D --------------- > > > >Current thread (0x000000000052f400): JavaThread "main" [_thread_in_Ja= va, id=3D5320704] > > > >Stack: [0x00007fffffc00000,0x0000800000000000), sp=3D0x00007fffffff40= c0, free space=3D4048k > >Native frames: (J=3Dcompiled Java code, j=3Dinterpreted, Vv=3DVM code,= C=3Dnative code) > >V [libjvm.so+0x79063e] > >V [libjvm.so+0x465c56] > >V [libjvm.so+0x698eab] > >V [libjvm.so+0x70aa78] > >V [libjvm.so+0x6ac3e4] > >V [libjvm.so+0x6aae1e] > > > > > >--------------- P R O C E S S --------------- > > > >Java Threads: ( =3D> current thread ) > > 0x000000000060d800 JavaThread "Low Memory Detector" daemon [_thread_= blocked, id=3D6331392] > > 0x000000000060bc00 JavaThread "CompilerThread1" daemon [_thread_in_n= ative, id=3D6330368] > > 0x000000000060b000 JavaThread "CompilerThread0" daemon [_thread_in_n= ative, id=3D6329344] > > 0x00000000005f7400 JavaThread "AdapterThread" daemon [_thread_blocke= d, id=3D6229504] > > 0x00000000005ee800 JavaThread "Signal Dispatcher" daemon [_thread_bl= ocked, id=3D6228992] > > 0x00000000005ee000 JavaThread "Finalizer" daemon [_thread_blocked, i= d=3D6208512] > > 0x00000000005adc00 JavaThread "Reference Handler" daemon [_thread_bl= ocked, id=3D6208000] > >=3D>0x000000000052f400 JavaThread "main" [_thread_in_Java, id=3D532070= 4] > > > >Other Threads: > > 0x00000000005e1800 VMThread [id=3D6167040] > > 0x0000000000532800 WatcherThread [id=3D6331904] > > > >VM state:synchronizing (normal execution) > > > >VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event]) > >[0x000000000052c580/0x000000000052c600] Safepoint_lock - owner thread:= 0x00000000005e1800 > >[0x000000000052c700/0x000000000052c780] Threads_lock - owner thread: 0= x00000000005e1800 > > > >Heap > > def new generation total 38656K, used 23746K [0x0000000842b00000, 0= x00000008454f0000, 0x0000000848050000) > > eden space 34368K, 61% used [0x0000000842b00000, 0x0000000843f9ff68= , 0x0000000844c90000) > > from space 4288K, 61% used [0x00000008450c0000, 0x0000000845350a40,= 0x00000008454f0000) > > to space 4288K, 0% used [0x0000000844c90000, 0x0000000844c90000,= 0x00000008450c0000) > > tenured generation total 85876K, used 66357K [0x0000000848050000, 0= x000000084d42d000, 0x0000000852b00000) > > the space 85876K, 77% used [0x0000000848050000, 0x000000084c11d6b0= , 0x000000084c11d800, 0x000000084d42d000) > > compacting perm gen total 21248K, used 5080K [0x0000000852b00000, 0x= 0000000853fc0000, 0x0000000857d00000) > > the space 21248K, 23% used [0x0000000852b00000, 0x0000000852ff6018= , 0x0000000852ff6200, 0x0000000853fc0000) > >No shared spaces configured. > > > >Dynamic libraries: > >0x0000000000400000 /usr/ports/java/jdk15/work/control/build/bsd-am= d64/bin/javac > >0x0000000800639000 /usr/lib/libthr.so.2 > >0x0000000800750000 /lib/libc.so.6 > >0x000000080094d000 /usr/ports/java/jdk15/work/control/build/bsd-am= d64/lib/amd64/server/libjvm.so > >0x0000000801386000 /usr/lib/libstdc++.so.5 > >0x000000080157d000 /lib/libm.so.4 > >0x0000000801699000 /usr/ports/java/jdk15/work/control/build/bsd-am= d64/lib/amd64/native_threads/libhpi.so > >0x00000008017a5000 /usr/ports/java/jdk15/work/control/build/bsd-am= d64/lib/amd64/libverify.so > >0x00000008018b4000 /usr/ports/java/jdk15/work/control/build/bsd-am= d64/lib/amd64/libjava.so > >0x00000008019dc000 /usr/ports/java/jdk15/work/control/build/bsd-am= d64/lib/amd64/libzip.so > >0x000000080050f000 /libexec/ld-elf.so.1 > > > >VM Arguments: > >jvm_args: -Denv.class.path=3D -Dapplication.home=3D/usr/ports/java/jdk= 15/work/control/build/bsd-amd64 -Xms8m -Xss4m -ea:com.sun.tools... -XX:Th= readStackSize=3D1536 -Xms64m -Xmx256m > >java_command: com.sun.tools.javac.Main -classpath /usr/ports/java/jdk1= 5/work/control/build/bsd-amd64/tmp/java/java.lang/library/newclasses:../.= =2E/../../../src/share/classes -bootclasspath /usr/ports/java/jdk15/work/= control/build/bsd-amd64/lib/jce.jar:/usr/ports/java/jdk15/work/control/bu= ild/bsd-amd64/lib/jsse.jar -sourcepath /usr/ports/java/jdk15/work/control= /build/bsd-amd64/gensrc:../../../../../src/solaris/classes:../../../../..= /src/share/classes -d /usr/ports/java/jdk15/work/control/build/bsd-amd64/= tmp/java/java.lang/library/newclasses -encoding ascii -source 1.5 ../../.= =2E/../../src/share/classes/java/lang/Object.java ../../../../../src/shar= e/classes/java/lang/Class.java ../../../../../src/share/classes/java/lang= /Thread.java ../../../../../src/share/classes/java/lang/Character.java ..= /../../../../src/share/classes/sun/misc/ASCIICaseInsensitiveComparator.ja= va ../../../../../src/share/classes/sun/misc/VM.java ../../../../../src/s= hare/classes/sun/misc/Signal.java > ../../../../../src/share/classes/sun/misc/NativeSignalHandler.java ../.= =2E/../../../src/share/classes/java/lang/ThreadGroup.java ../../../../../= src/share/classes/java/lang/ThreadLocal.java ../../../../../src/share/cla= sses/java/lang/InheritableThreadLocal.java ../../../../../src/share/class= es/java/lang/String.java ../../../../../src/share/classes/java/lang/Condi= tionalSpecialCasing.java ../../../../../src/share/classes/java/lang/Strin= gCoding.java ../../../../../src/share/classes/java/lang/StringBuffer.java= ../../../../../src/share/classes/java/lang/StringBuilder.java ../../../.= =2E/../src/share/classes/java/lang/SuppressWarnings.java ../../../../../s= rc/share/classes/java/lang/AbstractStringBuilder.java ../../../../../src/= share/classes/java/lang/ClassLoader.java ../../../../../src/share/classes= /java/lang/AssertionStatusDirectives.java ../../../../../src/share/classe= s/java/lang/Enum.java ../../../../../src/share/classes/java/lang/StrictMa= th.java > ../../../../../src/share/classes/java/lang/Math.java ../../../../../src= > > > >Environment Variables: > >JAVA_HOME=3D > >CLASSPATH=3D > >PATH=3D/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/l= ocal/bin:/usr/X11R6/bin:/usr/local/samba/bin:/usr/local/mysql/bin:/root/b= in:/usr/local/scripts/admin:/usr/local/scripts/public:usr/local/gmt/bin > >LD_LIBRARY_PATH=3D/usr/ports/java/jdk15/work/control/build/bsd-amd64/l= ib/amd64/server:/usr/ports/java/jdk15/work/control/build/bsd-amd64/lib/am= d64:/usr/ports/java/jdk15/work/control/build/bsd-amd64/../lib/amd64: > >SHELL=3D/bin/sh > >HOSTTYPE=3DFreeBSD > >OSTYPE=3DFreeBSD > >ARCH=3Damd64 > >MACHTYPE=3Dunknown > > > > > >--------------- S Y S T E M --------------- > > > >OS:FreeBSD > >uname:FreeBSD 6.0-STABLE FreeBSD 6.0-STABLE #158: Mon Dec 12 22:29:27 = CET 2005 root@thor.schanze.de:/usr/obj/usr/src/sys/THOR amd64 > >rlimit: STACK 524288k, CORE infinity, NOFILE 11095 > >CPU:total 1 > > > >Memory: 4k page, physical 262144k > > > >vm_info: Java HotSpot(TM) 64-Bit Server VM (1.5.0-p2-root_14_dec_2005_= 18_55) for freebsd-amd64, built on Dec 14 2005 19:38:30 by root with gcc = 3.4.4 [FreeBSD] 20050518 > > > > > > > >----------------------------------------------------------------------= -- > > > >_______________________________________________ > >freebsd-amd64@freebsd.org mailing list > >http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > >To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.or= g" > > > > > > Forgot to say I'm using FreeBSD 6.0-STABLE as most recent cvsupdated an= d > compiled. From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 15 20:33:08 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F0F116A41F for ; Thu, 15 Dec 2005 20:33:08 +0000 (GMT) (envelope-from lists@nabble.com) Received: from talk.nabble.com (www.nabble.com [72.21.53.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F8D743D58 for ; Thu, 15 Dec 2005 20:33:06 +0000 (GMT) (envelope-from lists@nabble.com) Received: from localhost ([127.0.0.1] helo=talk.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1Emzmj-00035n-Ge for freebsd-amd64@freebsd.org; Thu, 15 Dec 2005 12:33:05 -0800 Message-ID: <1964166.post@talk.nabble.com> Date: Thu, 15 Dec 2005 12:33:05 -0800 (PST) From: "bsdrio (sent by Nabble.com)" To: freebsd-amd64@freebsd.org In-Reply-To: <7.0.0.16.2.20051213094628.04230870@micom.mng.net> MIME-Version: 1.0 X-Nabble-Sender: Nabble Forums X-Nabble-From: bsdrio References: <7.0.0.16.0.20051207093744.01c92628@micom.mng.net> <4396433C.3050701@samsco.org> <7.0.0.16.0.20051207104632.01c92628@micom.mng.net> <1916335.post@talk.nabble.com> <7.0.0.16.2.20051213094628.04230870@micom.mng.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: 6.0 Buildworld on AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bsdrio List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 20:33:08 -0000 Thank you, that worked for us as well. Happily running 6.0 now. bsdrio -- Sent from the freebsd-amd64 forum at Nabble.com: http://www.nabble.com/6.0-Buildworld-on-AMD64-t691634.html#a1964166 From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 15 20:36:10 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A97816A41F for ; Thu, 15 Dec 2005 20:36:10 +0000 (GMT) (envelope-from lists@nabble.com) Received: from talk.nabble.com (www.nabble.com [72.21.53.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id C921B43D6A for ; Thu, 15 Dec 2005 20:36:06 +0000 (GMT) (envelope-from lists@nabble.com) Received: from localhost ([127.0.0.1] helo=talk.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1Emzpd-0003C2-T6 for freebsd-amd64@freebsd.org; Thu, 15 Dec 2005 12:36:05 -0800 Message-ID: <1964210.post@talk.nabble.com> Date: Thu, 15 Dec 2005 12:36:05 -0800 (PST) From: "bsdrio (sent by Nabble.com)" To: freebsd-amd64@freebsd.org In-Reply-To: <20051213042057.GA13113@odin.ac.hmc.edu> MIME-Version: 1.0 X-Nabble-Sender: Nabble Forums X-Nabble-From: bsdrio References: <436BF442.9020708@rsmba.biz> <20051105054130.GL63539@ip.net.ua> <436C5F54.7020300@rsmba.biz> <1913673.post@talk.nabble.com> <20051213042057.GA13113@odin.ac.hmc.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: buildworld failing on amd64 with RELENG_6 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bsdrio List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2005 20:36:10 -0000 The system clock is within a few seconds at most of what it should be so I ruled that out as the problem. I found however that the makefile was pointing to source in a much different directory, yet during the buildworld it was looking for the source in the libalias directory which only had the makefile in it. Symlinking all the libalias source files to the libalias directory resolved this problem for me. Thank -- Sent from the freebsd-amd64 forum at Nabble.com: http://www.nabble.com/buildworld-failing-on-amd64-with-RELENG_6-t494383.html#a1964210 From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 16 01:05:53 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5F3916A41F; Fri, 16 Dec 2005 01:05:53 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4883943D62; Fri, 16 Dec 2005 01:05:53 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id jBG15pj2090863; Thu, 15 Dec 2005 20:05:51 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id jBG15ptF093067; Thu, 15 Dec 2005 20:05:51 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 7C5307302F; Thu, 15 Dec 2005 20:05:51 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051216010551.7C5307302F@freebsd-current.sentex.ca> Date: Thu, 15 Dec 2005 20:05:51 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 01:05:54 -0000 TB --- 2005-12-15 23:23:45 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-12-15 23:23:45 - starting HEAD tinderbox run for amd64/amd64 TB --- 2005-12-15 23:23:45 - cleaning the object tree TB --- 2005-12-15 23:24:21 - checking out the source tree TB --- 2005-12-15 23:24:21 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2005-12-15 23:24:21 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-12-15 23:30:19 - building world (CFLAGS=-O2 -pipe) TB --- 2005-12-15 23:30:19 - cd /src TB --- 2005-12-15 23:30:19 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries TB --- 2005-12-16 01:00:32 - generating LINT kernel config TB --- 2005-12-16 01:00:32 - cd /src/sys/amd64/conf TB --- 2005-12-16 01:00:32 - /usr/bin/make -B LINT TB --- 2005-12-16 01:00:32 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-12-16 01:00:32 - cd /src TB --- 2005-12-16 01:00:32 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Dec 16 01:00:32 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -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 -finstrument-functions -Wno-inline /src/sys/dev/ata/ata-dma.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -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 -finstrument-functions -Wno-inline /src/sys/dev/ata/ata-isa.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -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 -finstrument-functions -Wno-inline /src/sys/dev/ata/ata-lowlevel.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -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 -finstrument-functions -Wno-inline /src/sys/dev/ata/ata-pci.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -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 -finstrument-functions -Wno-inline /src/sys/dev/ata/ata-queue.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -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 -finstrument-functions -Wno-inline /src/sys/dev/ata/ata-raid.c /src/sys/dev/ata/ata-raid.c: In function `ata_raid_via_write_meta': /src/sys/dev/ata/ata-raid.c:3622: warning: cast from pointer to integer of different size *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-12-16 01:05:51 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-12-16 01:05:51 - ERROR: failed to build lint kernel TB --- 2005-12-16 01:05:51 - tinderbox aborted TB --- 1.21 user 6.77 system 6126.03 real From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 16 17:31:25 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7046C16A41F for ; Fri, 16 Dec 2005 17:31:25 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08B5F43D8A for ; Fri, 16 Dec 2005 17:31:13 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id jBGHgxKQ077359; Fri, 16 Dec 2005 12:42:59 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-amd64@FreeBSD.org Date: Fri, 16 Dec 2005 12:30:39 -0500 User-Agent: KMail/1.6.2 References: <43A1636A.6030108@mail.uni-mainz.de> In-Reply-To: <43A1636A.6030108@mail.uni-mainz.de> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Message-Id: <200512161230.41499.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV devel-20050919/1210/Thu Dec 15 10:23:22 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: "O. Hartmann" Subject: Re: device drm with PCIe? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 17:31:25 -0000 On Thursday 15 December 2005 07:36 am, O. Hartmann wrote: > Normally 'device drm' is only useable in conjunction with 'device > agp'. A lot of amd64 based boxes now use PEG slots for their > graphics accelerators. Is it possible to utilize 'drm' with PCIe > devices? Yes. It should work, at least in theory. ;-) > Does device agp has any effect on PCIe graphics accelerators? No. You don't need it for PCI-Express controller. Jung-uk Kim > Thanks, > Oliver From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 16 18:27:50 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C840516A422; Fri, 16 Dec 2005 18:27:50 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from leguin.anholt.net (69-30-77-85.dq1sn.easystreet.com [69.30.77.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0160C43D66; Fri, 16 Dec 2005 18:27:46 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from leguin.anholt.net (localhost [127.0.0.1]) by leguin.anholt.net (8.13.4/8.13.1) with ESMTP id jBGIRi7C050162; Fri, 16 Dec 2005 10:27:44 -0800 (PST) (envelope-from eta@lclark.edu) Received: (from anholt@localhost) by leguin.anholt.net (8.13.4/8.13.1/Submit) id jBGIRhtA050161; Fri, 16 Dec 2005 10:27:43 -0800 (PST) (envelope-from eta@lclark.edu) X-Authentication-Warning: leguin.anholt.net: anholt set sender to eta@lclark.edu using -f From: Eric Anholt To: Jung-uk Kim In-Reply-To: <200512161230.41499.jkim@FreeBSD.org> References: <43A1636A.6030108@mail.uni-mainz.de> <200512161230.41499.jkim@FreeBSD.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Aj8XgXBe7Tf25jSn/5QH" Date: Fri, 16 Dec 2005 10:27:42 -0800 Message-Id: <1134757662.1404.81.camel@leguin> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2 FreeBSD GNOME Team Port Cc: "O. Hartmann" , freebsd-amd64@freebsd.org Subject: Re: device drm with PCIe? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 18:27:51 -0000 --=-Aj8XgXBe7Tf25jSn/5QH Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2005-12-16 at 12:30 -0500, Jung-uk Kim wrote: > On Thursday 15 December 2005 07:36 am, O. Hartmann wrote: > > Normally 'device drm' is only useable in conjunction with 'device > > agp'. A lot of amd64 based boxes now use PEG slots for their > > graphics accelerators. Is it possible to utilize 'drm' with PCIe > > devices? >=20 > Yes. It should work, at least in theory. ;-) >=20 > > Does device agp has any effect on PCIe graphics accelerators? >=20 > No. You don't need it for PCI-Express controller. Now, this is stuff I don't 100% understand, but what I've figured out so far is that for graphics, you're going to need a GART somewhere. For their PCIE cards, ATI deals with this by doing essentially the old PCIGART method but tweaked, in lieu of AGP. Intel's PCIE graphics, on the other hand, has a GART on their chips that is basically the same thing as their previous AGP GARTs, at least in terms of programming. So we expose their gart through the agp device still, even though the chipset may be PCIE. --=20 Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org --=-Aj8XgXBe7Tf25jSn/5QH Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDowceHUdvYGzw6vcRAn0VAKCVyjHsB4ucJhOLntSy2BZzcHgIoQCfSnkR DO4G1Nxni8XFvEbtkcPOtbU= =/FKQ -----END PGP SIGNATURE----- --=-Aj8XgXBe7Tf25jSn/5QH-- From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 16 18:49:45 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E25416A41F; Fri, 16 Dec 2005 18:49:45 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.178.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9AB543D62; Fri, 16 Dec 2005 18:49:41 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [134.93.180.123] (ipamzra.Physik.Uni-Mainz.DE [134.93.180.123]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate1.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 3222E30003A0; Fri, 16 Dec 2005 19:45:46 +0100 (CET) Message-ID: <43A30B25.3030102@mail.uni-mainz.de> Date: Fri, 16 Dec 2005 19:44:53 +0100 From: "O. Hartmann" User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Jung-uk Kim References: <43A1636A.6030108@mail.uni-mainz.de> <200512161230.41499.jkim@FreeBSD.org> In-Reply-To: <200512161230.41499.jkim@FreeBSD.org> Content-Type: text/plain; charset=EUC-KR Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de Cc: freebsd-amd64@FreeBSD.org Subject: Re: device drm with PCIe? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 18:49:45 -0000 Jung-uk Kim schrieb: > On Thursday 15 December 2005 07:36 am, O. Hartmann wrote: > >>Normally 'device drm' is only useable in conjunction with 'device >>agp'. A lot of amd64 based boxes now use PEG slots for their >>graphics accelerators. Is it possible to utilize 'drm' with PCIe >>devices? > > > Yes. It should work, at least in theory. ;-) > > >>Does device agp has any effect on PCIe graphics accelerators? > > > No. You don't need it for PCI-Express controller. Ok, but without AGP (device agp) in my kernel config file, I get a lot of errors while linking the kernel of missing agp_xxxxx routines (FreeBSD 6.0-STABLE/amd64). So, device drm alone seems to be useless (although in conjunction with device pci). > > Jung-uk Kim > > >>Thanks, >>Oliver From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 16 18:59:08 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 236A716A41F for ; Fri, 16 Dec 2005 18:59:08 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3578143D5F for ; Fri, 16 Dec 2005 18:59:06 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id jBGJArS1080626; Fri, 16 Dec 2005 14:10:53 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: Eric Anholt Date: Fri, 16 Dec 2005 13:58:32 -0500 User-Agent: KMail/1.6.2 References: <43A1636A.6030108@mail.uni-mainz.de> <200512161230.41499.jkim@FreeBSD.org> <1134757662.1404.81.camel@leguin> In-Reply-To: <1134757662.1404.81.camel@leguin> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Message-Id: <200512161358.34963.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV devel-20050919/1210/Thu Dec 15 10:23:22 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: "O. Hartmann" , freebsd-amd64@FreeBSD.org Subject: Re: device drm with PCIe? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 18:59:08 -0000 On Friday 16 December 2005 01:27 pm, Eric Anholt wrote: > On Fri, 2005-12-16 at 12:30 -0500, Jung-uk Kim wrote: > > On Thursday 15 December 2005 07:36 am, O. Hartmann wrote: > > > Normally 'device drm' is only useable in conjunction with > > > 'device agp'. A lot of amd64 based boxes now use PEG slots for > > > their graphics accelerators. Is it possible to utilize 'drm' > > > with PCIe devices? > > > > Yes. It should work, at least in theory. ;-) > > > > > Does device agp has any effect on PCIe graphics accelerators? > > > > No. You don't need it for PCI-Express controller. > > Now, this is stuff I don't 100% understand, but what I've figured > out so far is that for graphics, you're going to need a GART > somewhere. For their PCIE cards, ATI deals with this by doing > essentially the old PCIGART method but tweaked, in lieu of AGP. > Intel's PCIE graphics, on the other hand, has a GART on their chips > that is basically the same thing as their previous AGP GARTs, at > least in terms of programming. So we expose their gart through the > agp device still, even though the chipset may be PCIE. Ah, Eric is correct about the Intel part. But it was amd64 thread, so I just assumed... :-( Jung-uk Kim From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 16 19:23:30 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8942716A44B for ; Fri, 16 Dec 2005 19:23:29 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 549BA43DEF for ; Fri, 16 Dec 2005 19:22:52 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id jBGJYRdg081440; Fri, 16 Dec 2005 14:34:27 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: "O. Hartmann" Date: Fri, 16 Dec 2005 14:21:58 -0500 User-Agent: KMail/1.6.2 References: <43A1636A.6030108@mail.uni-mainz.de> <200512161230.41499.jkim@FreeBSD.org> <43A30B25.3030102@mail.uni-mainz.de> In-Reply-To: <43A30B25.3030102@mail.uni-mainz.de> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Message-Id: <200512161422.00688.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV devel-20050919/1210/Thu Dec 15 10:23:22 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-amd64@FreeBSD.org Subject: Re: device drm with PCIe? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 19:23:30 -0000 On Friday 16 December 2005 01:44 pm, O. Hartmann wrote: > Jung-uk Kim schrieb: > > On Thursday 15 December 2005 07:36 am, O. Hartmann wrote: > >>Normally 'device drm' is only useable in conjunction with 'device > >>agp'. A lot of amd64 based boxes now use PEG slots for their > >>graphics accelerators. Is it possible to utilize 'drm' with PCIe > >>devices? > > > > Yes. It should work, at least in theory. ;-) > > > >>Does device agp has any effect on PCIe graphics accelerators? > > > > No. You don't need it for PCI-Express controller. > > Ok, but without AGP (device agp) in my kernel config file, I get a > lot of errors while linking the kernel of missing agp_xxxxx > routines (FreeBSD 6.0-STABLE/amd64). So, device drm alone seems to > be useless (although in conjunction with device pci). Did you try 'make clean; make cleandepend; make depend; make'? Jung-uk Kim > > Jung-uk Kim > > > >>Thanks, > >>Oliver From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 16 19:23:41 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1474816A422; Fri, 16 Dec 2005 19:23:41 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from leguin.anholt.net (69-30-77-85.dq1sn.easystreet.com [69.30.77.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C38E43D45; Fri, 16 Dec 2005 19:23:22 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from leguin.anholt.net (localhost [127.0.0.1]) by leguin.anholt.net (8.13.4/8.13.1) with ESMTP id jBGJNGrW080307; Fri, 16 Dec 2005 11:23:16 -0800 (PST) (envelope-from eta@lclark.edu) Received: (from anholt@localhost) by leguin.anholt.net (8.13.4/8.13.1/Submit) id jBGJNGRm080306; Fri, 16 Dec 2005 11:23:16 -0800 (PST) (envelope-from eta@lclark.edu) X-Authentication-Warning: leguin.anholt.net: anholt set sender to eta@lclark.edu using -f From: Eric Anholt To: Jung-uk Kim In-Reply-To: <200512161358.34963.jkim@FreeBSD.org> References: <43A1636A.6030108@mail.uni-mainz.de> <200512161230.41499.jkim@FreeBSD.org> <1134757662.1404.81.camel@leguin> <200512161358.34963.jkim@FreeBSD.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-y4DRANeubVxmHxzZrmbC" Date: Fri, 16 Dec 2005 11:23:15 -0800 Message-Id: <1134760995.1404.88.camel@leguin> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2 FreeBSD GNOME Team Port Cc: "O. Hartmann" , freebsd-amd64@FreeBSD.org Subject: Re: device drm with PCIe? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 19:23:41 -0000 --=-y4DRANeubVxmHxzZrmbC Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2005-12-16 at 13:58 -0500, Jung-uk Kim wrote: > On Friday 16 December 2005 01:27 pm, Eric Anholt wrote: > > On Fri, 2005-12-16 at 12:30 -0500, Jung-uk Kim wrote: > > > On Thursday 15 December 2005 07:36 am, O. Hartmann wrote: > > > > Normally 'device drm' is only useable in conjunction with > > > > 'device agp'. A lot of amd64 based boxes now use PEG slots for > > > > their graphics accelerators. Is it possible to utilize 'drm' > > > > with PCIe devices? > > > > > > Yes. It should work, at least in theory. ;-) > > > > > > > Does device agp has any effect on PCIe graphics accelerators? > > > > > > No. You don't need it for PCI-Express controller. > > > > Now, this is stuff I don't 100% understand, but what I've figured > > out so far is that for graphics, you're going to need a GART > > somewhere. For their PCIE cards, ATI deals with this by doing > > essentially the old PCIGART method but tweaked, in lieu of AGP.=20 > > Intel's PCIE graphics, on the other hand, has a GART on their chips > > that is basically the same thing as their previous AGP GARTs, at > > least in terms of programming. So we expose their gart through the > > agp device still, even though the chipset may be PCIE. >=20 > Ah, Eric is correct about the Intel part. But it was amd64 thread, so=20 > I just assumed... :-( And now, for extra complication, we've got EM64Ts on i915 motherboards :) It also seems to me like we ought to be able to use the internal GART on real amd64s to avoid the card's PCIGART-ish method for PCIE radeons, right? --=20 Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org --=-y4DRANeubVxmHxzZrmbC Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDoxQjHUdvYGzw6vcRArH2AJ0UhuuCaANTGgdz/ftkQKLI9m44UACeONar yZPKYk7m0bUkArPgETfo4O0= =0BiB -----END PGP SIGNATURE----- --=-y4DRANeubVxmHxzZrmbC-- From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 16 19:27:57 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD27A16A423; Fri, 16 Dec 2005 19:27:57 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56AB843D8D; Fri, 16 Dec 2005 19:27:24 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jBGJRHS7019951; Fri, 16 Dec 2005 12:27:17 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43A31515.6050602@samsco.org> Date: Fri, 16 Dec 2005 12:27:17 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anholt References: <43A1636A.6030108@mail.uni-mainz.de> <200512161230.41499.jkim@FreeBSD.org> <1134757662.1404.81.camel@leguin> <200512161358.34963.jkim@FreeBSD.org> <1134760995.1404.88.camel@leguin> In-Reply-To: <1134760995.1404.88.camel@leguin> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: "O. Hartmann" , freebsd-amd64@freebsd.org, Jung-uk Kim Subject: Re: device drm with PCIe? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 19:27:58 -0000 Eric Anholt wrote: > On Fri, 2005-12-16 at 13:58 -0500, Jung-uk Kim wrote: > >>On Friday 16 December 2005 01:27 pm, Eric Anholt wrote: >> >>>On Fri, 2005-12-16 at 12:30 -0500, Jung-uk Kim wrote: >>> >>>>On Thursday 15 December 2005 07:36 am, O. Hartmann wrote: >>>> >>>>>Normally 'device drm' is only useable in conjunction with >>>>>'device agp'. A lot of amd64 based boxes now use PEG slots for >>>>>their graphics accelerators. Is it possible to utilize 'drm' >>>>>with PCIe devices? >>>> >>>>Yes. It should work, at least in theory. ;-) >>>> >>>> >>>>>Does device agp has any effect on PCIe graphics accelerators? >>>> >>>>No. You don't need it for PCI-Express controller. >>> >>>Now, this is stuff I don't 100% understand, but what I've figured >>>out so far is that for graphics, you're going to need a GART >>>somewhere. For their PCIE cards, ATI deals with this by doing >>>essentially the old PCIGART method but tweaked, in lieu of AGP. >>>Intel's PCIE graphics, on the other hand, has a GART on their chips >>>that is basically the same thing as their previous AGP GARTs, at >>>least in terms of programming. So we expose their gart through the >>>agp device still, even though the chipset may be PCIE. >> >>Ah, Eric is correct about the Intel part. But it was amd64 thread, so >>I just assumed... :-( > > > And now, for extra complication, we've got EM64Ts on i915 > motherboards :) > > It also seems to me like we ought to be able to use the internal GART on > real amd64s to avoid the card's PCIGART-ish method for PCIE radeons, > right? > Apparently there is a bit of magic with true AMD athlon64 and Opteron systems regarding the different ways that GART functionality is exposed. Probably the best bet is to get with David O'brien and figure out those details. For Intel systems, it depends on whether the AGP GART has a link to the PCIe root complex. I can't imagine it not having this, but again it's something to check the docs for. Scott From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 16 20:30:08 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 075E816A426 for ; Fri, 16 Dec 2005 20:30:07 +0000 (GMT) (envelope-from seanmwelch@yahoo.com) Received: from smtp102.mail.sc5.yahoo.com (smtp102.mail.sc5.yahoo.com [216.136.174.140]) by mx1.FreeBSD.org (Postfix) with SMTP id 4D08F43D7F for ; Fri, 16 Dec 2005 20:30:05 +0000 (GMT) (envelope-from seanmwelch@yahoo.com) Received: (qmail 70193 invoked from network); 16 Dec 2005 20:30:04 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:Received:Received:Date:From:To:Cc:Subject:Message-ID:Reply-To:Mime-Version:Content-Type:Content-Disposition:User-Agent; b=2lyqQ42j6psDZrT+J3t8yWujdQTKnwVwoRlZFKSqRUvV+deEJwS+jPHhfuwEYfIuLCADX/UlbDVjatLNBRnFEF1Rxw8LJaTnVZpzuaml9v6Jnjt83Xi4Q18nGF+WVc1AlMiszHogNuT5LWXhbnAnfLnvyUhV1Fn3fGJQdhyXWYQ= ; Received: from unknown (HELO NitroPhys.welchsmnet.net) (seanmwelch@66.41.102.215 with plain) by smtp102.mail.sc5.yahoo.com with SMTP; 16 Dec 2005 20:30:03 -0000 Received: from NitroPhys.welchsmnet.net (localhost [127.0.0.1]) by NitroPhys.welchsmnet.net (8.13.1/8.12.10) with ESMTP id jBGKTSGV063099; Fri, 16 Dec 2005 14:29:29 -0600 (CST) (envelope-from seanmwelch@yahoo.com) Received: (from welchsm@localhost) by NitroPhys.welchsmnet.net (8.13.1/8.13.1/Submit) id jBGKTRwa063098; Fri, 16 Dec 2005 14:29:27 -0600 (CST) (envelope-from seanmwelch@yahoo.com) Date: Fri, 16 Dec 2005 14:29:27 -0600 From: Sean Welch To: eta@lclark.edu Message-ID: <20051216202927.GA63068@NitroPhys.welchsmnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i Cc: ohartman@mail.uni-mainz.de, jkim@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: device drm with PCIe X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: seanmwelch@yahoo.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 20:30:08 -0000 So I take it I'm not going to be able to get my brand new Ferrari 4005WLMi to do DRI just yet? (With the exceptions of resume from suspend and a nasty freezing bug when dynamic frequency scaling is enabled this is a SWEET machine for i386 FreeBSD -- haven't tried 64bit yet) Yes, I've finally moved on from my I8k to something a bit newer, faster, thinner, lighter, etc... Is there anything I could help test out in this area? Sean >> It also seems to me like we ought to be able to use the internal GART on >> real amd64s to avoid the card's PCIGART-ish method for PCIE radeons, >> right? >> > > Apparently there is a bit of magic with true AMD athlon64 and Opteron > systems regarding the different ways that GART functionality is exposed. > Probably the best bet is to get with David O'brien and figure out those > details. For Intel systems, it depends on whether the AGP GART has a > link to the PCIe root complex. I can't imagine it not having this, but > again it's something to check the docs for. > > Scott From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 16 22:25:29 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D714716A422 for ; Fri, 16 Dec 2005 22:25:29 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4E6443D64 for ; Fri, 16 Dec 2005 22:25:22 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper [212.12.50.230]) by schlepper.zs64.net (8.13.3/8.12.9) with ESMTP id jBGMPIvv031964; Fri, 16 Dec 2005 23:25:18 +0100 (CET) (envelope-from cracauer@schlepper.zs64.net) Received: (from cracauer@localhost) by schlepper.zs64.net (8.13.3/8.12.9/Submit) id jBGMPINt031963; Fri, 16 Dec 2005 17:25:18 -0500 (EST) (envelope-from cracauer) Date: Fri, 16 Dec 2005 17:25:18 -0500 From: Martin Cracauer To: "O. Hartmann" Message-ID: <20051216172518.A31803@cons.org> References: <439DAC66.3020104@mail.uni-mainz.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <439DAC66.3020104@mail.uni-mainz.de>; from ohartman@mail.uni-mainz.de on Mon, Dec 12, 2005 at 05:59:18PM +0100 Cc: freebsd-amd64@freebsd.org Subject: Re: PCIe-8x usage on ASUS SLI boards X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 22:25:30 -0000 O. Hartmann wrote on Mon, Dec 12, 2005 at 05:59:18PM +0100: > Hello. > My question may be a little bit cranky, but having low cost server in > mind it may be of relevance. > > Is it possible to use the second 8x SLI slot on ASUS A8n-SLI > Deluxe/Premium as a normal PCIe-8x slot with SLI enabled? > > Server systems do not utilize high graphics throughput, so I can live > with a PEG card in 8x mode. But it would be fine if I could use a > 8x-lane SATA-II or SCSI RAID card in the second PEG slot with 8x-lane > support. In practice that should usually be possible. In theory, a x16 slot is only required to serve x16 and x1 cards, a x8 slots most serve x8 and x1 but nothing in between is required. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 16 22:52:52 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E754F16A422; Fri, 16 Dec 2005 22:52:52 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.178.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id C05E643D97; Fri, 16 Dec 2005 22:52:27 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [83.242.62.175] (175-62-242-83.dip.h-tel.de [83.242.62.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate2.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 0CE6E30020CF; Fri, 16 Dec 2005 23:52:23 +0100 (CET) Message-ID: <43A34520.9060001@mail.uni-mainz.de> Date: Fri, 16 Dec 2005 23:52:16 +0100 From: "O. Hartmann" User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jung-uk Kim References: <43A1636A.6030108@mail.uni-mainz.de> <200512161230.41499.jkim@FreeBSD.org> <43A30B25.3030102@mail.uni-mainz.de> <200512161422.00688.jkim@FreeBSD.org> In-Reply-To: <200512161422.00688.jkim@FreeBSD.org> Content-Type: multipart/mixed; boundary="------------080405000207010406010908" X-Virus-Scanned: by amavisd-new at uni-mainz.de X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-amd64@FreeBSD.org Subject: Re: device drm with PCIe? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 22:52:53 -0000 This is a multi-part message in MIME format. --------------080405000207010406010908 Content-Type: text/plain; charset=EUC-KR Content-Transfer-Encoding: 7bit Jung-uk Kim wrote: >On Friday 16 December 2005 01:44 pm, O. Hartmann wrote: > > >>Jung-uk Kim schrieb: >> >> >>>On Thursday 15 December 2005 07:36 am, O. Hartmann wrote: >>> >>> >>>>Normally 'device drm' is only useable in conjunction with 'device >>>>agp'. A lot of amd64 based boxes now use PEG slots for their >>>>graphics accelerators. Is it possible to utilize 'drm' with PCIe >>>>devices? >>>> >>>> >>>Yes. It should work, at least in theory. ;-) >>> >>> >>> >>>>Does device agp has any effect on PCIe graphics accelerators? >>>> >>>> >>>No. You don't need it for PCI-Express controller. >>> >>> >>Ok, but without AGP (device agp) in my kernel config file, I get a >>lot of errors while linking the kernel of missing agp_xxxxx >>routines (FreeBSD 6.0-STABLE/amd64). So, device drm alone seems to >>be useless (although in conjunction with device pci). >> >> > >Did you try 'make clean; make cleandepend; make depend; make'? > > I used always 'make kernel' from /usr/usr. Doing it the old-stylish way no error occurs on FBSD6.0-STABLE/amd64 with device drm enabled, device agp disabled using your recommended command sentence. This is a little bit confusing ... Though 'make kernel' does all the stuff ... >Jung-uk Kim > > > >>>Jung-uk Kim >>> >>> >>> >>>>Thanks, >>>>Oliver >>>> >>>> --------------080405000207010406010908-- From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 16 22:57:17 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9831716A420; Fri, 16 Dec 2005 22:57:17 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.178.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78D0F43D45; Fri, 16 Dec 2005 22:57:16 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [83.242.62.175] (175-62-242-83.dip.h-tel.de [83.242.62.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate1.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 9FCEF30018F5; Fri, 16 Dec 2005 23:57:13 +0100 (CET) Message-ID: <43A34647.1030404@mail.uni-mainz.de> Date: Fri, 16 Dec 2005 23:57:11 +0100 From: "O. Hartmann" User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jung-uk Kim References: <43A1636A.6030108@mail.uni-mainz.de> <200512161230.41499.jkim@FreeBSD.org> <43A30B25.3030102@mail.uni-mainz.de> <200512161422.00688.jkim@FreeBSD.org> In-Reply-To: <200512161422.00688.jkim@FreeBSD.org> Content-Type: multipart/mixed; boundary="------------000605030806080300050400" X-Virus-Scanned: by amavisd-new at uni-mainz.de X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-amd64@FreeBSD.org Subject: Re: device drm with PCIe? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 22:57:17 -0000 This is a multi-part message in MIME format. --------------000605030806080300050400 Content-Type: text/plain; charset=EUC-KR Content-Transfer-Encoding: 7bit Jung-uk Kim wrote: >On Friday 16 December 2005 01:44 pm, O. Hartmann wrote: > > >>Jung-uk Kim schrieb: >> >> >>>On Thursday 15 December 2005 07:36 am, O. Hartmann wrote: >>> >>> >>>>Normally 'device drm' is only useable in conjunction with 'device >>>>agp'. A lot of amd64 based boxes now use PEG slots for their >>>>graphics accelerators. Is it possible to utilize 'drm' with PCIe >>>>devices? >>>> >>>> >>>Yes. It should work, at least in theory. ;-) >>> >>> >>> >>>>Does device agp has any effect on PCIe graphics accelerators? >>>> >>>> >>>No. You don't need it for PCI-Express controller. >>> >>> >>Ok, but without AGP (device agp) in my kernel config file, I get a >>lot of errors while linking the kernel of missing agp_xxxxx >>routines (FreeBSD 6.0-STABLE/amd64). So, device drm alone seems to >>be useless (although in conjunction with device pci). >> >> > >Did you try 'make clean; make cleandepend; make depend; make'? > > Doesn't work without device agp in kernel config file! linking kernel drm_agpsupport.o(.text+0x22c): In function `drm_agp_info': : undefined reference to `agp_get_info' drm_agpsupport.o(.text+0x324): In function `drm_agp_acquire': : undefined reference to `agp_acquire' drm_agpsupport.o(.text+0x374): In function `drm_agp_release': : undefined reference to `agp_release' drm_agpsupport.o(.text+0x3cf): In function `drm_agp_enable': : undefined reference to `agp_enable' drm_agpsupport.o(.text+0x45b): In function `drm_agp_init': : undefined reference to `agp_find_device' drm_agpsupport.o(.text+0x4ed): In function `drm_agp_init': : undefined reference to `agp_get_info' drm_agpsupport.o(.text+0x534): In function `drm_agp_allocate_memory': . . . . drm_agpsupport.o(.text+0xb66): In function `drm_agp_unbind_memory': : undefined reference to `agp_unbind_memory' *** Error code 1 Stop in /usr/obj/usr/src/sys/THOR. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. >Jung-uk Kim > > > >>>Jung-uk Kim >>> >>> >>> >>>>Thanks, >>>>Oliver >>>> >>>> --------------000605030806080300050400-- From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 16 23:09:09 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 23EC916A41F for ; Fri, 16 Dec 2005 23:09:09 +0000 (GMT) (envelope-from fcash@ocis.net) Received: from smtp.sd73.bc.ca (mailtest.sd73.bc.ca [142.24.13.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDFE143D5D for ; Fri, 16 Dec 2005 23:09:08 +0000 (GMT) (envelope-from fcash@ocis.net) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id B70258A0161 for ; Fri, 16 Dec 2005 15:08:55 -0800 (PST) Received: from smtp.sd73.bc.ca ([127.0.0.1]) by localhost (smtp.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 77945-01-26 for ; Fri, 16 Dec 2005 15:08:54 -0800 (PST) Received: from s157.sbo (unknown [192.168.0.157]) by smtp.sd73.bc.ca (Postfix) with ESMTP id 247CA8A016D for ; Fri, 16 Dec 2005 15:08:54 -0800 (PST) From: Freddie Cash To: freebsd-amd64@freebsd.org Date: Fri, 16 Dec 2005 15:08:59 -0800 User-Agent: KMail/1.8.3 References: <43A1636A.6030108@mail.uni-mainz.de> <200512161422.00688.jkim@FreeBSD.org> <43A34520.9060001@mail.uni-mainz.de> In-Reply-To: <43A34520.9060001@mail.uni-mainz.de> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512161509.00780.fcash@ocis.net> X-Virus-Scanned: by amavisd-new using ClamAV at sd73.bc.ca Subject: Re: device drm with PCIe? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 23:09:09 -0000 On December 16, 2005 02:52 pm, O. Hartmann wrote: > Jung-uk Kim wrote: > >On Friday 16 December 2005 01:44 pm, O. Hartmann wrote: > >>Ok, but without AGP (device agp) in my kernel config file, I get a > >>lot of errors while linking the kernel of missing agp_xxxxx > >>routines (FreeBSD 6.0-STABLE/amd64). So, device drm alone seems to > >>be useless (although in conjunction with device pci). > >Did you try 'make clean; make cleandepend; make depend; make'? > I used always 'make kernel' from /usr/usr. > Doing it the old-stylish way no error occurs on FBSD6.0-STABLE/amd64 > with device drm enabled, device agp disabled using your recommended > command sentence. This is a little bit confusing ... Though 'make > kernel' does all the stuff ... I bet if you do a "make cleanworld" or "make clean" or "make cleankernel" (if that's a valid target) before doing the "make kernel", you'll get the same results as the command sequence Jung-uk Kim posted. :) AFAIK, "make kernel" doesn't do a clean beforehand, which means you pick up the old depends files and objects. -- Freddie Cash fcash@ocis.net From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 16 23:25:28 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 032B716A434 for ; Fri, 16 Dec 2005 23:25:28 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5EA643D5A for ; Fri, 16 Dec 2005 23:25:26 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id jBGNb9eq088859; Fri, 16 Dec 2005 18:37:09 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-amd64@FreeBSD.org Date: Fri, 16 Dec 2005 18:24:46 -0500 User-Agent: KMail/1.6.2 References: <43A1636A.6030108@mail.uni-mainz.de> <200512161422.00688.jkim@FreeBSD.org> <43A34647.1030404@mail.uni-mainz.de> In-Reply-To: <43A34647.1030404@mail.uni-mainz.de> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Message-Id: <200512161824.50323.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV devel-20050919/1210/Thu Dec 15 10:23:22 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: "O. Hartmann" Subject: Re: device drm with PCIe? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 23:25:28 -0000 On Friday 16 December 2005 05:57 pm, O. Hartmann wrote: > Doesn't work without device agp in kernel config file! [SNIP!!!] Ouch, sorry about that. It seems drm(4) actually depends on agp(4) now. Well, it's not documented nor in conf/files though. :-( BTW, you don't need drm in kernel config, i. e., it will be kldload'ed by Xorg server. Jung-uk Kim From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 17 00:13:59 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DBC916A420; Sat, 17 Dec 2005 00:13:59 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from leguin.anholt.net (69-30-77-85.dq1sn.easystreet.com [69.30.77.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8080043D64; Sat, 17 Dec 2005 00:13:58 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from leguin.anholt.net (localhost [127.0.0.1]) by leguin.anholt.net (8.13.4/8.13.1) with ESMTP id jBH0DvrR010062; Fri, 16 Dec 2005 16:13:57 -0800 (PST) (envelope-from eta@lclark.edu) Received: (from anholt@localhost) by leguin.anholt.net (8.13.4/8.13.1/Submit) id jBH0DvcN010061; Fri, 16 Dec 2005 16:13:57 -0800 (PST) (envelope-from eta@lclark.edu) X-Authentication-Warning: leguin.anholt.net: anholt set sender to eta@lclark.edu using -f From: Eric Anholt To: "O. Hartmann" In-Reply-To: <43A34647.1030404@mail.uni-mainz.de> References: <43A1636A.6030108@mail.uni-mainz.de> <200512161230.41499.jkim@FreeBSD.org> <43A30B25.3030102@mail.uni-mainz.de> <200512161422.00688.jkim@FreeBSD.org> <43A34647.1030404@mail.uni-mainz.de> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-dAZX90k87VIdAZ0i8ARB" Date: Fri, 16 Dec 2005 16:13:55 -0800 Message-Id: <1134778435.1404.100.camel@leguin> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2 FreeBSD GNOME Team Port Cc: freebsd-amd64@freebsd.org, Jung-uk Kim Subject: Re: device drm with PCIe? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 00:13:59 -0000 --=-dAZX90k87VIdAZ0i8ARB Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2005-12-16 at 23:57 +0100, O. Hartmann wrote: > Jung-uk Kim wrote: >=20 > >On Friday 16 December 2005 01:44 pm, O. Hartmann wrote: > > =20 > > > >>Jung-uk Kim schrieb: > >> =20 > >> > >>>On Thursday 15 December 2005 07:36 am, O. Hartmann wrote: > >>> =20 > >>> > >>>>Normally 'device drm' is only useable in conjunction with 'device > >>>>agp'. A lot of amd64 based boxes now use PEG slots for their > >>>>graphics accelerators. Is it possible to utilize 'drm' with PCIe > >>>>devices? > >>>> =20 > >>>> > >>>Yes. It should work, at least in theory. ;-) > >>> > >>> =20 > >>> > >>>>Does device agp has any effect on PCIe graphics accelerators? > >>>> =20 > >>>> > >>>No. You don't need it for PCI-Express controller. > >>> =20 > >>> > >>Ok, but without AGP (device agp) in my kernel config file, I get a > >>lot of errors while linking the kernel of missing agp_xxxxx > >>routines (FreeBSD 6.0-STABLE/amd64). So, device drm alone seems to > >>be useless (although in conjunction with device pci). > >> =20 > >> > > > >Did you try 'make clean; make cleandepend; make depend; make'? > > =20 > > >=20 > Doesn't work without device agp in kernel config file! >=20 > linking kernel > drm_agpsupport.o(.text+0x22c): In function `drm_agp_info': > : undefined reference to `agp_get_info' > drm_agpsupport.o(.text+0x324): In function `drm_agp_acquire': > : undefined reference to `agp_acquire' > drm_agpsupport.o(.text+0x374): In function `drm_agp_release': > : undefined reference to `agp_release' > drm_agpsupport.o(.text+0x3cf): In function `drm_agp_enable': > : undefined reference to `agp_enable' > drm_agpsupport.o(.text+0x45b): In function `drm_agp_init': > : undefined reference to `agp_find_device' > drm_agpsupport.o(.text+0x4ed): In function `drm_agp_init': > : undefined reference to `agp_get_info' > drm_agpsupport.o(.text+0x534): In function `drm_agp_allocate_memory': Correct, the DRM module requires AGP. --=20 Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org --=-dAZX90k87VIdAZ0i8ARB Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDo1hDHUdvYGzw6vcRAso0AJ9p0a7UVCg+bDLHL8syDvylY6dnpQCeLh62 TOLjaKWWC5KbQqoCw6Fc4YQ= =wNQd -----END PGP SIGNATURE----- --=-dAZX90k87VIdAZ0i8ARB-- From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 17 10:45:08 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A25AB16A41F; Sat, 17 Dec 2005 10:45:08 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.178.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BDA043D81; Sat, 17 Dec 2005 10:44:53 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [217.185.96.27] (manz-d9b9601b.pool.mediaWays.net [217.185.96.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate2.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 2984E300228E; Sat, 17 Dec 2005 11:44:50 +0100 (CET) Message-ID: <43A3EC1A.5050209@mail.uni-mainz.de> Date: Sat, 17 Dec 2005 11:44:42 +0100 From: "O. Hartmann" User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anholt References: <43A1636A.6030108@mail.uni-mainz.de> <200512161230.41499.jkim@FreeBSD.org> <43A30B25.3030102@mail.uni-mainz.de> <200512161422.00688.jkim@FreeBSD.org> <43A34647.1030404@mail.uni-mainz.de> <1134778435.1404.100.camel@leguin> In-Reply-To: <1134778435.1404.100.camel@leguin> Content-Type: multipart/mixed; boundary="------------040106030302010808080402" X-Virus-Scanned: by amavisd-new at uni-mainz.de X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-amd64@freebsd.org, Jung-uk Kim Subject: Re: device drm with PCIe? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 10:45:08 -0000 This is a multi-part message in MIME format. --------------040106030302010808080402 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Eric Anholt wrote: >On Fri, 2005-12-16 at 23:57 +0100, O. Hartmann wrote: > > >>Jung-uk Kim wrote: >> >> >> >>>On Friday 16 December 2005 01:44 pm, O. Hartmann wrote: >>> >>> >>> >>> >>>>Jung-uk Kim schrieb: >>>> >>>> >>>> >>>> >>>>>On Thursday 15 December 2005 07:36 am, O. Hartmann wrote: >>>>> >>>>> >>>>> >>>>> >>>>>>Normally 'device drm' is only useable in conjunction with 'device >>>>>>agp'. A lot of amd64 based boxes now use PEG slots for their >>>>>>graphics accelerators. Is it possible to utilize 'drm' with PCIe >>>>>>devices? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>Yes. It should work, at least in theory. ;-) >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>>Does device agp has any effect on PCIe graphics accelerators? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>No. You don't need it for PCI-Express controller. >>>>> >>>>> >>>>> >>>>> >>>>Ok, but without AGP (device agp) in my kernel config file, I get a >>>>lot of errors while linking the kernel of missing agp_xxxxx >>>>routines (FreeBSD 6.0-STABLE/amd64). So, device drm alone seems to >>>>be useless (although in conjunction with device pci). >>>> >>>> >>>> >>>> >>>Did you try 'make clean; make cleandepend; make depend; make'? >>> >>> >>> >>> >>Doesn't work without device agp in kernel config file! >> >>linking kernel >>drm_agpsupport.o(.text+0x22c): In function `drm_agp_info': >>: undefined reference to `agp_get_info' >>drm_agpsupport.o(.text+0x324): In function `drm_agp_acquire': >>: undefined reference to `agp_acquire' >>drm_agpsupport.o(.text+0x374): In function `drm_agp_release': >>: undefined reference to `agp_release' >>drm_agpsupport.o(.text+0x3cf): In function `drm_agp_enable': >>: undefined reference to `agp_enable' >>drm_agpsupport.o(.text+0x45b): In function `drm_agp_init': >>: undefined reference to `agp_find_device' >>drm_agpsupport.o(.text+0x4ed): In function `drm_agp_init': >>: undefined reference to `agp_get_info' >>drm_agpsupport.o(.text+0x534): In function `drm_agp_allocate_memory': >> >> > >Correct, the DRM module requires AGP. > > > So, due to this limitation, drm on any PCIe-based AMD64 platform is useless so far? --------------040106030302010808080402-- From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 17 17:23:25 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0906516A41F; Sat, 17 Dec 2005 17:23:25 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from leguin.anholt.net (69-30-77-85.dq1sn.easystreet.com [69.30.77.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20E9F43D5A; Sat, 17 Dec 2005 17:23:24 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from leguin.anholt.net (localhost [127.0.0.1]) by leguin.anholt.net (8.13.4/8.13.1) with ESMTP id jBHHNM17025267; Sat, 17 Dec 2005 09:23:23 -0800 (PST) (envelope-from eta@lclark.edu) Received: (from anholt@localhost) by leguin.anholt.net (8.13.4/8.13.1/Submit) id jBHHNMQ4025266; Sat, 17 Dec 2005 09:23:22 -0800 (PST) (envelope-from eta@lclark.edu) X-Authentication-Warning: leguin.anholt.net: anholt set sender to eta@lclark.edu using -f From: Eric Anholt To: "O. Hartmann" In-Reply-To: <43A3EC1A.5050209@mail.uni-mainz.de> References: <43A1636A.6030108@mail.uni-mainz.de> <200512161230.41499.jkim@FreeBSD.org> <43A30B25.3030102@mail.uni-mainz.de> <200512161422.00688.jkim@FreeBSD.org> <43A34647.1030404@mail.uni-mainz.de> <1134778435.1404.100.camel@leguin> <43A3EC1A.5050209@mail.uni-mainz.de> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-T1co2wTx0R0GkeKy/6Ug" Date: Sat, 17 Dec 2005 09:23:21 -0800 Message-Id: <1134840201.1404.109.camel@leguin> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2 FreeBSD GNOME Team Port Cc: freebsd-amd64@freebsd.org, Jung-uk Kim Subject: Re: device drm with PCIe? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 17:23:25 -0000 --=-T1co2wTx0R0GkeKy/6Ug Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2005-12-17 at 11:44 +0100, O. Hartmann wrote: > >>>>Ok, but without AGP (device agp) in my kernel config file, I get a > >>>>lot of errors while linking the kernel of missing agp_xxxxx > >>>>routines (FreeBSD 6.0-STABLE/amd64). So, device drm alone seems to > >>>>be useless (although in conjunction with device pci). > >>>> =20 > >>>> > >>>> =20 > >>>> > >>>Did you try 'make clean; make cleandepend; make depend; make'? > >>>=20 > >>> > >>> =20 > >>> > >>Doesn't work without device agp in kernel config file! > >> > >>linking kernel > >>drm_agpsupport.o(.text+0x22c): In function `drm_agp_info': > >>: undefined reference to `agp_get_info' > >>drm_agpsupport.o(.text+0x324): In function `drm_agp_acquire': > >>: undefined reference to `agp_acquire' > >>drm_agpsupport.o(.text+0x374): In function `drm_agp_release': > >>: undefined reference to `agp_release' > >>drm_agpsupport.o(.text+0x3cf): In function `drm_agp_enable': > >>: undefined reference to `agp_enable' > >>drm_agpsupport.o(.text+0x45b): In function `drm_agp_init': > >>: undefined reference to `agp_find_device' > >>drm_agpsupport.o(.text+0x4ed): In function `drm_agp_init': > >>: undefined reference to `agp_get_info' > >>drm_agpsupport.o(.text+0x534): In function `drm_agp_allocate_memory': > >> =20 > >> > > > >Correct, the DRM module requires AGP. > > > > =20 > > >=20 > So, due to this limitation, drm on any PCIe-based AMD64 platform is > useless so far? No, you simply need the agp device compiled into the kernel. It doesn't mean it will actually be used with your specific card at runtime. And anyways, you never need to build drm and your device-specific drm built into the kernel. X loads it for you so you don't have to worry. --=20 Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org --=-T1co2wTx0R0GkeKy/6Ug Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDpEmJHUdvYGzw6vcRAu0nAJ9qXg9L2ur3o5R/bbUypT9oC00XsgCfTDJx uEqsFmLj8n8p7uehsdG825M= =wBAJ -----END PGP SIGNATURE----- --=-T1co2wTx0R0GkeKy/6Ug-- From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 17 17:58:23 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B5A416A41F; Sat, 17 Dec 2005 17:58:23 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9E1243D7D; Sat, 17 Dec 2005 17:58:07 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jBHHw6TG028026; Sat, 17 Dec 2005 10:58:06 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43A451AE.9080601@samsco.org> Date: Sat, 17 Dec 2005 10:58:06 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anholt References: <43A1636A.6030108@mail.uni-mainz.de> <200512161230.41499.jkim@FreeBSD.org> <43A30B25.3030102@mail.uni-mainz.de> <200512161422.00688.jkim@FreeBSD.org> <43A34647.1030404@mail.uni-mainz.de> <1134778435.1404.100.camel@leguin> <43A3EC1A.5050209@mail.uni-mainz.de> <1134840201.1404.109.camel@leguin> In-Reply-To: <1134840201.1404.109.camel@leguin> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: "O. Hartmann" , Jung-uk Kim , freebsd-amd64@freebsd.org Subject: Re: device drm with PCIe? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2005 17:58:23 -0000 Eric Anholt wrote: > On Sat, 2005-12-17 at 11:44 +0100, O. Hartmann wrote: > >>>>>>Ok, but without AGP (device agp) in my kernel config file, I get a >>>>>>lot of errors while linking the kernel of missing agp_xxxxx >>>>>>routines (FreeBSD 6.0-STABLE/amd64). So, device drm alone seems to >>>>>>be useless (although in conjunction with device pci). >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>>Did you try 'make clean; make cleandepend; make depend; make'? >>>>> >>>>> >>>>> >>>>> >>>> >>>>Doesn't work without device agp in kernel config file! >>>> >>>>linking kernel >>>>drm_agpsupport.o(.text+0x22c): In function `drm_agp_info': >>>>: undefined reference to `agp_get_info' >>>>drm_agpsupport.o(.text+0x324): In function `drm_agp_acquire': >>>>: undefined reference to `agp_acquire' >>>>drm_agpsupport.o(.text+0x374): In function `drm_agp_release': >>>>: undefined reference to `agp_release' >>>>drm_agpsupport.o(.text+0x3cf): In function `drm_agp_enable': >>>>: undefined reference to `agp_enable' >>>>drm_agpsupport.o(.text+0x45b): In function `drm_agp_init': >>>>: undefined reference to `agp_find_device' >>>>drm_agpsupport.o(.text+0x4ed): In function `drm_agp_init': >>>>: undefined reference to `agp_get_info' >>>>drm_agpsupport.o(.text+0x534): In function `drm_agp_allocate_memory': >>>> >>>> >>> >>>Correct, the DRM module requires AGP. >>> >>> >>> >> >>So, due to this limitation, drm on any PCIe-based AMD64 platform is >>useless so far? > > > No, you simply need the agp device compiled into the kernel. It doesn't > mean it will actually be used with your specific card at runtime. > > And anyways, you never need to build drm and your device-specific drm > built into the kernel. X loads it for you so you don't have to worry. > Maybe it's time for an agp kobj interface? Scott