From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 1 03:05:52 2006 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 D550616A41F; Sun, 1 Jan 2006 03:05:52 +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 29DC543D48; Sun, 1 Jan 2006 03:05:52 +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 k0135pnx016879; Sat, 31 Dec 2005 22: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 k0135odM054984; Sat, 31 Dec 2005 22:05:50 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id BA2D87302F; Sat, 31 Dec 2005 22:05:50 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20060101030550.BA2D87302F@freebsd-current.sentex.ca> Date: Sat, 31 Dec 2005 22:05:50 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner4 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: Sun, 01 Jan 2006 03:05:53 -0000 TB --- 2006-01-01 01:37:56 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-01-01 01:37:56 - starting HEAD tinderbox run for amd64/amd64 TB --- 2006-01-01 01:37:56 - cleaning the object tree TB --- 2006-01-01 01:38:18 - checking out the source tree TB --- 2006-01-01 01:38:18 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2006-01-01 01:38:18 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-01-01 01:44:23 - building world (CFLAGS=-O2 -pipe) TB --- 2006-01-01 01:44:23 - cd /src TB --- 2006-01-01 01:44:23 - /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 [...] /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:385: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:395: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:415: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:431: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:432: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:434: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:435: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:437: error: dereferencing pointer to incomplete type *** Error code 1 Stop in /src/kerberos5/lib/libgssapi. *** Error code 1 Stop in /src/kerberos5/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-01-01 03:05:50 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-01-01 03:05:50 - ERROR: failed to build world TB --- 2006-01-01 03:05:50 - tinderbox aborted TB --- 0.99 user 4.14 system 5274.26 real From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 1 10:30:10 2006 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 D0E3B16A420 for ; Sun, 1 Jan 2006 10:30: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 7473E43D5A for ; Sun, 1 Jan 2006 10:30:09 +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 k01AU9a1054823 for ; Sun, 1 Jan 2006 10:30:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k01AU9AJ054822; Sun, 1 Jan 2006 10:30:09 GMT (envelope-from gnats) Resent-Date: Sun, 1 Jan 2006 10:30:09 GMT Resent-Message-Id: <200601011030.k01AU9AJ054822@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Michael Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96F7B16A41F for ; Sun, 1 Jan 2006 10:23:22 +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 2EFA443D46 for ; Sun, 1 Jan 2006 10:23:22 +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 k01ANLgP055345 for ; Sun, 1 Jan 2006 10:23:22 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id k01ANL6t055344; Sun, 1 Jan 2006 10:23:21 GMT (envelope-from nobody) Message-Id: <200601011023.k01ANL6t055344@www.freebsd.org> Date: Sun, 1 Jan 2006 10:23:21 GMT From: Michael To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/91159: pango fails to compile 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, 01 Jan 2006 10:30:11 -0000 >Number: 91159 >Category: amd64 >Synopsis: pango fails to compile >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Jan 01 10:30:08 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Michael >Release: amd64 6-STABLE >Organization: >Environment: FreeBSD newbox 6.0-STABLE FreeBSD 6.0-STABLE #1: Fri Dec 30 12:04:24 PST 2005 root@newbox:/usr/obj/usr/src/sys/NEWBOX amd64 >Description: creating pango-xftview if cc -DHAVE_CONFIG_H -I. -I. -I.. -DG_DISABLE_DEPRECATED -DPANGO_DISABLE_DEPRECATED -DG_DISABLE_CAST_CHECKS -I.. -I/usr/local/include/cairo -D_REENTRANT -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/X11R6/include -I/usr/X11R6/include -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/X11R6/include -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include -I/usr/X11R6/include -O2 -fno-strict-aliasing -pipe -march=opteron -Wall -MT cairoview.o -MD -MP -MF ".deps/cairoview.Tpo" \ -c -o cairoview.o `test -f 'cairoview.c' || echo './'`cairoview.c; \ then mv -f ".deps/cairoview.Tpo" ".deps/cairoview.Po"; \ else rm -f ".deps/cairoview.Tpo"; exit 1; \ fi cairoview.c:35:24: cairo-xlib.h: No such file or directory cairoview.c: In function `update': cairoview.c:145: warning: implicit declaration of function `cairo_xlib_surface_create' cairoview.c:147: warning: assignment makes pointer from integer without a cast gmake[2]: *** [cairoview.o] Error 1 gmake[2]: Leaving directory `/usr/ports/x11-toolkits/pango/work/pango-1.10.2/examples' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/x11-toolkits/pango/work/pango-1.10.2' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/x11-toolkits/pango. >How-To-Repeat: cd /usr/ports/x11-toolkits/pango && make clean && make install or portinstall pango >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 1 18:24:00 2006 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 8344B16A420; Sun, 1 Jan 2006 18:24:00 +0000 (GMT) (envelope-from pav@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BC8043D5D; Sun, 1 Jan 2006 18:23:59 +0000 (GMT) (envelope-from pav@FreeBSD.org) Received: from freefall.freebsd.org (pav@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k01INxeD083175; Sun, 1 Jan 2006 18:23:59 GMT (envelope-from pav@freefall.freebsd.org) Received: (from pav@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k01INxLN083171; Sun, 1 Jan 2006 18:23:59 GMT (envelope-from pav) Date: Sun, 1 Jan 2006 18:23:59 GMT From: Pav Lucistnik Message-Id: <200601011823.k01INxLN083171@freefall.freebsd.org> To: elshar@cheekan.org, pav@FreeBSD.org, freebsd-amd64@FreeBSD.org, gnome@FreeBSD.org Cc: Subject: Re: ports/91159: pango fails to compile 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, 01 Jan 2006 18:24:00 -0000 Synopsis: pango fails to compile State-Changed-From-To: open->feedback State-Changed-By: pav State-Changed-When: Sun Jan 1 18:22:42 UTC 2006 State-Changed-Why: What is the version of your cairo? Responsible-Changed-From-To: freebsd-amd64->gnome Responsible-Changed-By: pav Responsible-Changed-When: Sun Jan 1 18:22:42 UTC 2006 Responsible-Changed-Why: Refile to ports; over to maintainers http://www.freebsd.org/cgi/query-pr.cgi?pr=91159 From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 2 02:20:02 2006 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 AB40416A420; Mon, 2 Jan 2006 02:20:02 +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 6970E43D67; Mon, 2 Jan 2006 02:19:57 +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 k022JtZS074027; Sun, 1 Jan 2006 21:19:55 -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 k022JtEd022584; Sun, 1 Jan 2006 21:19:55 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 5393F7302F; Sun, 1 Jan 2006 21:19:55 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20060102021955.5393F7302F@freebsd-current.sentex.ca> Date: Sun, 1 Jan 2006 21:19:55 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner4 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, 02 Jan 2006 02:20:03 -0000 TB --- 2006-01-02 00:51:42 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-01-02 00:51:42 - starting HEAD tinderbox run for amd64/amd64 TB --- 2006-01-02 00:51:42 - cleaning the object tree TB --- 2006-01-02 00:52:03 - checking out the source tree TB --- 2006-01-02 00:52:03 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2006-01-02 00:52:03 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-01-02 00:58:02 - building world (CFLAGS=-O2 -pipe) TB --- 2006-01-02 00:58:02 - cd /src TB --- 2006-01-02 00:58: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 [...] /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:385: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:395: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:415: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:431: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:432: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:434: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:435: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:437: error: dereferencing pointer to incomplete type *** Error code 1 Stop in /src/kerberos5/lib/libgssapi. *** Error code 1 Stop in /src/kerberos5/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-01-02 02:19:55 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-01-02 02:19:55 - ERROR: failed to build world TB --- 2006-01-02 02:19:55 - tinderbox aborted TB --- 0.87 user 4.27 system 5292.46 real From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 2 02:35:00 2006 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 06C9F16A41F for ; Mon, 2 Jan 2006 02:35:00 +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 4CD4043D45 for ; Mon, 2 Jan 2006 02:34:59 +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 k022Yw4h096510 for ; Mon, 2 Jan 2006 03:34:58 +0100 (CET) (envelope-from cracauer@schlepper.zs64.net) Received: (from cracauer@localhost) by schlepper.zs64.net (8.13.3/8.12.9/Submit) id k022YvOe096509 for freebsd-amd64@freebsd.org; Sun, 1 Jan 2006 21:34:58 -0500 (EST) (envelope-from cracauer) Date: Sun, 1 Jan 2006 21:34:57 -0500 From: Martin Cracauer To: freebsd-amd64@freebsd.org Message-ID: <20060101213457.A95942@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Subject: ohci_add_done panic on a board with 4 GB RAM and remapping (AMD64) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 02:35:00 -0000 When using 4 GB RAM and remapping of the device memory space to above 4 GB I get: ohci_adddone: addr 0x000d1bf0 not found That applies when I turn on software remapping, hardware remapping or both (CPU is E revision, see below). The board is an Asus A8N-E Premium (NForce4 chipset). I tried both new newest BIOS 1009 and the newest beta BIOS 1011-001, no change. CPU is a dual-core Opteron 170. FreeBSD is a few days old 7-current, SMP kernel, AMD64. I also noticed that device probing becomes much slower with 4 GB and remapping as opposed to running 2 GB or 4 GB with no remapping. The probe of the nve GbE in particular takes long, about 20 seconds. Linux on the same board with 4GB+remapping panics with PCI-DMA: high address but no IOMMU In Linux you can work around it with boot option iommu=soft Is this just the usual "Asus has BIOS siesta again" situation or can I do anything about it? I like the board otherwise, without remapping it works best of what I tested for my new server so far. dmesg, pciconf etc are on http://www.cons.org/cracauer/machines/wings-a8ne-premium/ 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 Mon Jan 2 04:30:13 2006 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 941CA16A420 for ; Mon, 2 Jan 2006 04:30:13 +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 8A8FD43D4C for ; Mon, 2 Jan 2006 04:30:09 +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 k024U9gk016808 for ; Mon, 2 Jan 2006 04:30:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k024U9td016807; Mon, 2 Jan 2006 04:30:09 GMT (envelope-from gnats) Resent-Date: Mon, 2 Jan 2006 04:30:09 GMT Resent-Message-Id: <200601020430.k024U9td016807@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, Heeroy Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CCD8C16A41F for ; Mon, 2 Jan 2006 04:24:20 +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 9163E43D45 for ; Mon, 2 Jan 2006 04:24:20 +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 k024OK62028345 for ; Mon, 2 Jan 2006 04:24:20 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id k024OKUY028343; Mon, 2 Jan 2006 04:24:20 GMT (envelope-from nobody) Message-Id: <200601020424.k024OKUY028343@www.freebsd.org> Date: Mon, 2 Jan 2006 04:24:20 GMT From: Heeroy To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/91195: FreeBSD 6.0(amd64) and Asus A8R-MVP 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, 02 Jan 2006 04:30:13 -0000 >Number: 91195 >Category: amd64 >Synopsis: FreeBSD 6.0(amd64) and Asus A8R-MVP >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 Jan 02 04:30:08 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Heeroy >Release: FreeBSD 6.0 release >Organization: student >Environment: CPU: Amd Athelon 64 3000+ (socket 939) Motherboard: Asus A8R-MVP >Description: FreeBSD 6.0 does not full support ULI chipset M1575 in my new Motherboard: Asus A8R-MVP. When I change my BIOS setting: On Board SATA Boot Rom to enable, my WD SATA 2 HD can not be found by FreeBSD When I change the setting to disable: and 1. Change SATA mode selection to AHCI, FreeBSD can not detect my disk, too. 2. Change SATA mode selection to PATA, FreeBSD can detect my disk, but the transfer mode is DMA 33 >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 2 11:02:35 2006 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 4B80D16A420 for ; Mon, 2 Jan 2006 11:02:35 +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 71C0543D7D for ; Mon, 2 Jan 2006 11:02:32 +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 k02B2Txf037442 for ; Mon, 2 Jan 2006 11:02:29 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k02B2SDb037436 for freebsd-amd64@freebsd.org; Mon, 2 Jan 2006 11:02:28 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 2 Jan 2006 11:02:28 GMT Message-Id: <200601021102.k02B2SDb037436@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, 02 Jan 2006 11:02:35 -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 o [2005/12/12] amd64/90303 amd64 Marvell 88E8111 Gigabit LAN PHY driver o [2005/12/22] amd64/90798 amd64 asking if motherboard is compatible 59 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 [2006/01/02] amd64/91195 amd64 FreeBSD 6.0(amd64) and Asus A8R-MVP 16 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 2 13:00:13 2006 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 94EDD16A41F for ; Mon, 2 Jan 2006 13:00:13 +0000 (GMT) (envelope-from jiashiun@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADCB443D5E for ; Mon, 2 Jan 2006 13:00:12 +0000 (GMT) (envelope-from jiashiun@gmail.com) Received: by wproxy.gmail.com with SMTP id i14so2035999wra for ; Mon, 02 Jan 2006 05:00:11 -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:content-transfer-encoding:content-disposition:references; b=PPqtHGYWCEHH/gBBdRV7GSfeY6zsSXmOQQrnJ57/KvMLP8udfu5z8RG4O2gNT3SFEEkX3oZ0eNhMOKE06KURGohD7cx1Uz0ieqmmT9wWvr8Z5uXSBJfkOlyMiyIhrm9RKcfH5xgtlHy/fLomaa4XQYyUHbCQ4nt8AkIiC6CBxiA= Received: by 10.54.132.10 with SMTP id f10mr266693wrd; Mon, 02 Jan 2006 05:00:11 -0800 (PST) Received: by 10.54.131.9 with HTTP; Mon, 2 Jan 2006 05:00:11 -0800 (PST) Message-ID: <1d6d20bc0601020500p41a6101ao@mail.gmail.com> Date: Mon, 2 Jan 2006 21:00:11 +0800 From: Jia-Shiun Li To: vd@datamax.bg In-Reply-To: <20051220145023.GA48817@qlovarnika.bg.datamax> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051201182200.29630.qmail@web32911.mail.mud.yahoo.com> <20051205174356.GA76476@dragon.NUXI.org> <1d6d20bc0512190232v5591adabw@mail.gmail.com> <20051220145023.GA48817@qlovarnika.bg.datamax> Cc: pfgshield-freebsd@yahoo.com, freebsd-amd64@freebsd.org Subject: Re: options VESA --> where is it ? 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, 02 Jan 2006 13:00:13 -0000 2005/12/20, Vasil Dimov : > On Mon, Dec 19, 2005 at 06:32:11PM +0800, Jia-Shiun Li wrote: > > If you mean VESA framebuffer driver, the comment in > > linux/drivers/video/vesafb.c > > says that it enters graphics mode at boot time while still in real mode= . > > > Some time ago I pondered switching the video mode at early boot time and > wondered if it would be less work to do... If I understood the source correctly, freebsd/amd64 switches to long mode in loader stage before the kernel is run. Jia-Shiun. From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 2 21:34:54 2006 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 1885516A422 for ; Mon, 2 Jan 2006 21:34:54 +0000 (GMT) (envelope-from surija@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E33543D46 for ; Mon, 2 Jan 2006 21:34:53 +0000 (GMT) (envelope-from surija@gmail.com) Received: by uproxy.gmail.com with SMTP id o2so25719uge for ; Mon, 02 Jan 2006 13:34:52 -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=GxmfHare9nTIsHbfc1rwRcRCmNLuSM8nHPG77ryBUWitl0NjFONyZkV6eeoz0uTSiJ/1/qBrC36ncEXQD3efu5gGW27mJEsETo/z7qVHPsJHaMyjQMYbJlIHHNY4OeY+Eyk2x1IkCNm3QZlJIC3YFy9DcVVNzdAXd7+Roz5TIMY= Received: by 10.66.255.18 with SMTP id c18mr4583915ugi; Mon, 02 Jan 2006 13:34:51 -0800 (PST) Received: by 10.66.241.13 with HTTP; Mon, 2 Jan 2006 13:34:51 -0800 (PST) Message-ID: <21bc91010601021334k69288c9ao8ccaab51da1095c3@mail.gmail.com> Date: Mon, 2 Jan 2006 16:34:51 -0500 From: Ranko Sredojevic To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: gnome & dual head problems 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, 02 Jan 2006 21:34:54 -0000 Hi all, I'm running RELENG_6 on amd64. Recently I installed new gnome port, recompiled Xorg... No problems encountered. In configuration with one monitor, everything is running fine. However, in dual head configuration, I experienced two problems: (1) After screen-saver locks the screen, I cannot unlock (no password dialogue is popping up on keyboard/mouse activity) (2) When Gnome is just started (after reboot, for example) in place of desktop picture I see random contents of memory ... parts of previously opened windows and such... It goes away after "refreshing" the screen by moving a window around... Second problem is not a big issue, since I don't reboot very often. However= , first one is much more annoying... :) Any ideas on this? In case it helps: it is Radeon 9250 using radeon driver. Trying not to run Xinerama, to keep DRI working, so I set up MergedFB with Virtual twice the size of on= e monitor. One monitor is on DVI and the other on Analog output. Both using 1280x1024... Pseudo-Xinerama provided by the driver is enabled. tnx, rasha From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 2 22:14:26 2006 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 9795016A41F for ; Mon, 2 Jan 2006 22:14:26 +0000 (GMT) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6282343D48 for ; Mon, 2 Jan 2006 22:14:24 +0000 (GMT) (envelope-from arno@heho.snv.jussieu.fr) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.13.5/jtpda-5.4) with ESMTP id k02MEIcf056687 ; Mon, 2 Jan 2006 23:14:21 +0100 (CET) X-Ids: 168 Received: from heho.labo (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.13.3/jtpda-5.2) with ESMTP id k02MEH6m032551 ; Mon, 2 Jan 2006 23:14:17 +0100 (MET) Received: (from arno@localhost) by heho.labo (8.13.3/8.13.1/Submit) id k02MEBkT032546; Mon, 2 Jan 2006 23:14:11 +0100 (MET) (envelope-from arno) Sender: arno@heho.snv.jussieu.fr To: Fernando Schapachnik References: <20051231122034.599bbf8c.torfinn.ingolfsen@broadpark.no> <20051231125158.GA830@funes.schapachnik.com.ar> From: "Arno J. Klaassen" Date: 02 Jan 2006 23:14:10 +0100 In-Reply-To: <20051231125158.GA830@funes.schapachnik.com.ar> Message-ID: Lines: 35 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.7.2 (shiva.jussieu.fr [134.157.0.168]); Mon, 02 Jan 2006 23:14:22 +0100 (CET) X-Antivirus: scanned by sophie at shiva.jussieu.fr X-Miltered: at shiva.jussieu.fr with ID 43B9A5BA.002 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Cc: freebsd-amd64@freebsd.org Subject: Re: Skype on FreeBSD / amd64 - what's the trick? 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, 02 Jan 2006 22:14:26 -0000 Fernando Schapachnik writes: > En un mensaje anterior, Torfinn Ingolfsen escribió: > > Hi, > > > > I tried to install Skype on my amd64 machine, running FreeBSD > > 6.0-stable: > > root@kg-quiet# uname -a > > FreeBSD kg-quiet.kg4.no 6.0-STABLE FreeBSD 6.0-STABLE #1: Thu Dec 22 > > 06:29:24 CET 2005 root@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET > > amd64 > > > > Looking at the makefile, I could see that the port was supposed to work > > on both i386 and amd64, adn thought the install would go smoothly. > > Boy, was I wrong. > > > > It seems that the port net/skype depends on graphics/linux_dri, but the > > latter (linux_dri) is i386 only. > > So, what's the trick to get Skype installed on amd64? > > If you have a 32-bit linux environment in place, just comment the > i386 only line of the linux_dri Makefile. It worked for me and skype > works fine. there seem to be serious problems on many configurations with linux_dri on amd64; I just made a symlink libGL.so.1 -> libX11.so.6 in /compat/linux/usr/X11R6/lib; this make Skype happy (which does not seem to need reel GL functionality, just a valid libGL.so.1 to start-up) and prevents my linux-apps which really use GL to bomb. My $0.02 Arno From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 3 04:00:51 2006 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 71AC316A41F; Tue, 3 Jan 2006 04:00:51 +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 EC0EB43D5F; Tue, 3 Jan 2006 04:00:50 +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 k0340oIj054965; Mon, 2 Jan 2006 20:00:50 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.4/8.13.1/Submit) id k0340oHW054964; Mon, 2 Jan 2006 20:00:50 -0800 (PST) (envelope-from obrien) Date: Mon, 2 Jan 2006 20:00:49 -0800 From: "David O'Brien" To: John Baldwin Message-ID: <20060103040049.GA54882@dragon.NUXI.org> References: <200512301245.57820.andrea@brancatelli.it> <20051230130529.GK52756@ip.net.ua> <200512300834.51959.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200512300834.51959.jhb@freebsd.org> 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: AMD64 boot floppies X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 04:00:51 -0000 On Fri, Dec 30, 2005 at 08:34:50AM -0500, John Baldwin wrote: > On Friday 30 December 2005 08:05 am, Ruslan Ermilov wrote: > > On Fri, Dec 30, 2005 at 12:45:57PM +0100, Andrea Brancatelli wrote: > > > For i386 we have > > > ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/6.0-RELEASE/floppies/ > > > but for Amd64 there's no > > > ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/6.0-RELEASE/floppies/ > > > > > > How can I get installation floppies for 6.0 / amd64? > > > > http://www.freebsd.org/releases/6.0R/installation-amd64.html#FLOPPIES > > FYI, it would be trivial to support with the splitfs stuff now. You'd > basically just need to copy over the variables from i386 to set the > sizes, etc. please, Please, PLEASE no... why add the pain of floppies to the release mix when no one in their right mind as an AMD64 machine that has a floppy drive AND doesn't have a CDROM (or DVD) drive. -- -- 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 Jan 3 04:02:11 2006 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 4BC5816A41F for ; Tue, 3 Jan 2006 04:02:11 +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 DD3E343D48 for ; Tue, 3 Jan 2006 04:02:10 +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 k0342AZ1055002; Mon, 2 Jan 2006 20:02:10 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.4/8.13.1/Submit) id k03427LF055001; Mon, 2 Jan 2006 20:02:07 -0800 (PST) (envelope-from obrien) Date: Mon, 2 Jan 2006 20:02:07 -0800 From: "David O'Brien" To: "Arno J. Klaassen" Message-ID: <20060103040207.GB54882@dragon.NUXI.org> References: <20051231122034.599bbf8c.torfinn.ingolfsen@broadpark.no> <20051231125158.GA830@funes.schapachnik.com.ar> Mime-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: 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: Fernando Schapachnik , freebsd-amd64@freebsd.org Subject: Re: Skype on FreeBSD / amd64 - what's the trick? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 04:02:11 -0000 On Mon, Jan 02, 2006 at 11:14:10PM +0100, Arno J. Klaassen wrote: > Fernando Schapachnik writes: > > En un mensaje anterior, Torfinn Ingolfsen escribió: > > > I tried to install Skype on my amd64 machine, running FreeBSD > > > 6.0-stable: ... > > > It seems that the port net/skype depends on graphics/linux_dri, but the > > > latter (linux_dri) is i386 only. > > > So, what's the trick to get Skype installed on amd64? > > > > If you have a 32-bit linux environment in place, just comment the > > i386 only line of the linux_dri Makefile. It worked for me and skype > > works fine. > > there seem to be serious problems on many configurations with linux_dri > on amd64; > I just made a symlink libGL.so.1 -> libX11.so.6 > in /compat/linux/usr/X11R6/lib; this make Skype happy (which > does not seem to need reel GL functionality, just a valid libGL.so.1 > to start-up) and prevents my linux-apps which really use GL to bomb. > My $0.02 Patch to /usr/ports anyone? :-) -- -- 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 Jan 3 04:08:36 2006 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 516CE16A41F for ; Tue, 3 Jan 2006 04:08:36 +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 713BD43D76 for ; Tue, 3 Jan 2006 04:08:29 +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 k0348Pkg055093; Mon, 2 Jan 2006 20:08:25 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.4/8.13.1/Submit) id k0348Oj8055092; Mon, 2 Jan 2006 20:08:24 -0800 (PST) (envelope-from obrien) Date: Mon, 2 Jan 2006 20:08:24 -0800 From: "David O'Brien" To: Adriaan de Groot Message-ID: <20060103040824.GD54882@dragon.NUXI.org> References: <562e6673484764a98de5ffb5241d1b76@prodigy.net> <200512271020.58471.groot@kde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200512271020.58471.groot@kde.org> 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: version 6.0 and AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 04:08:36 -0000 On Tue, Dec 27, 2005 at 10:20:57AM +0100, Adriaan de Groot wrote: > On Monday 26 December 2005 21:35, je killen wrote: > > I purchased Version 6.0 from FreeBSD Mall and am now concerned that the > > packaged system will work on AMD64 which I have, The processor I have > > and want to use is socket 754, if it makes a difference. > > Socket 754 is an amd64 socket, so that'll be fine (unless there are > socket 754 Semprons without 64-bit? There definately are 32-bit only K8 core Sempron's. -- -- 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 Jan 3 04:10:16 2006 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 639F516A41F for ; Tue, 3 Jan 2006 04:10:16 +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 115F543D53 for ; Tue, 3 Jan 2006 04:10:16 +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 k034AF6a055125; Mon, 2 Jan 2006 20:10:15 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.4/8.13.1/Submit) id k034AFRA055124; Mon, 2 Jan 2006 20:10:15 -0800 (PST) (envelope-from obrien) Date: Mon, 2 Jan 2006 20:10:15 -0800 From: "David O'Brien" To: chuck remes Message-ID: <20060103041015.GE54882@dragon.NUXI.org> References: <19DE779F-3568-4399-8963-D6B7F3E654FD@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <19DE779F-3568-4399-8963-D6B7F3E654FD@mac.com> 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: Advice on server configuration X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 04:10:16 -0000 On Mon, Dec 26, 2005 at 03:11:49PM -0600, chuck remes wrote: > I need some advice on building a server to run 6.0-RELEASE. .. > 1. Tyan Thunder K8S Pro S2882G3NR > http://www.serversdirect.com/product.asp?pf_id=MBS802 > 2. Single Opteron 265 dual-core > http://www.serversdirect.com/product.asp?pf_id=Opteron%5F265 This will limit you to only being able to use 4 of the 8 DIMM slots on the motherboard. If you're going to do that - you might consider the Tyan s2866 1P motherboard and use PCI-express I/O cards. -- -- 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 Jan 3 09:42:45 2006 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 74D0916A41F for ; Tue, 3 Jan 2006 09:42:45 +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 8255343D46 for ; Tue, 3 Jan 2006 09:42:44 +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 <0ISI007QAGJEFGD0@osl1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Tue, 03 Jan 2006 10:47:38 +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 <0ISI00AQ8GFL1J10@osl1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Tue, 03 Jan 2006 10:45:22 +0100 (CET) Date: Tue, 03 Jan 2006 10:42:43 +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: <20060103040207.GB54882@dragon.NUXI.org> To: freebsd-amd64@freebsd.org Message-id: <20060103104243.777a42f1.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: <20051231122034.599bbf8c.torfinn.ingolfsen@broadpark.no> <20051231125158.GA830@funes.schapachnik.com.ar> <20060103040207.GB54882@dragon.NUXI.org> Subject: Re: Skype on FreeBSD / amd64 - what's the trick? 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, 03 Jan 2006 09:42:45 -0000 On Mon, 02 Jan 2006 20:02:07 -0800 David O'Brien wrote: > Patch to /usr/ports anyone? :-) I guess this is not what you are asking for: --- /usr/ports/graphics/linux_dri/Makefile_org Sun Nov 6 19:50:50 2005 +++ /usr/ports/graphics/linux_dri/Makefile Tue Jan 3 10:11:30 2006 @@ -25,7 +25,7 @@ USE_LINUX_PREFIX= yes USE_XLIB= yes -ONLY_FOR_ARCHS= i386 +ONLY_FOR_ARCHS= i386 amd64 MODULELIST= gamma_dri.so i810_dri.so i830_dri.so mga_dri.so r128_dri.so \ r200_dri.so radeon_dri.so sis_dri.so tdfx_dri.so (beware of linewraps) Anyway, that made my linux_dri port install, which made skype install. It looks like Skype works, but I haven't tested chat or call yet. -- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 3 13:03:24 2006 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 CCB6716A41F for ; Tue, 3 Jan 2006 13:03:24 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: from blue-ld-041.synserver.de (blue-ld-041.synserver.de [217.119.50.242]) by mx1.FreeBSD.org (Postfix) with SMTP id 7E45C43D46 for ; Tue, 3 Jan 2006 13:03:22 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: (qmail 14013 invoked by uid 0); 3 Jan 2006 13:03:18 -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-07.synserver.de with SMTP; 3 Jan 2006 13:03:18 -0000 Date: Tue, 3 Jan 2006 14:03:20 +0100 From: Markus Trippelsdorf To: freebsd-amd64@freebsd.org Message-ID: <20060103130320.GA691@bsd.trippelsdorf.de> References: <200512301245.57820.andrea@brancatelli.it> <20051230130529.GK52756@ip.net.ua> <200512300834.51959.jhb@freebsd.org> <20060103040049.GA54882@dragon.NUXI.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060103040049.GA54882@dragon.NUXI.org> Cc: Subject: Re: AMD64 boot floppies 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, 03 Jan 2006 13:03:24 -0000 On Mon, Jan 02, 2006 at 08:00:49PM -0800, David O'Brien wrote: > On Fri, Dec 30, 2005 at 08:34:50AM -0500, John Baldwin wrote: > > On Friday 30 December 2005 08:05 am, Ruslan Ermilov wrote: > > > On Fri, Dec 30, 2005 at 12:45:57PM +0100, Andrea Brancatelli wrote: > > > > For i386 we have > > > > ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/6.0-RELEASE/floppies/ > > > > but for Amd64 there's no > > > > ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/6.0-RELEASE/floppies/ > > > > > > > > How can I get installation floppies for 6.0 / amd64? > > > > > > http://www.freebsd.org/releases/6.0R/installation-amd64.html#FLOPPIES > > > > FYI, it would be trivial to support with the splitfs stuff now. You'd > > basically just need to copy over the variables from i386 to set the > > sizes, etc. > > please, Please, PLEASE no... why add the pain of floppies to the release > mix when no one in their right mind as an AMD64 machine that has a floppy > drive AND doesn't have a CDROM (or DVD) drive. But I guess, the are many AMD64 machines that don't have a CDROM- or DVD- burner build in. For these machines a few floppy images to start a network installation would be helpful. -- Markus From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 3 13:24:33 2006 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 E6FF316A41F for ; Tue, 3 Jan 2006 13:24:33 +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 3827543D45 for ; Tue, 3 Jan 2006 13:24:32 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.4/8.13.1) with ESMTP id k03DOWCq027893 for ; Tue, 3 Jan 2006 11:24:32 -0200 (BRST) (envelope-from joao@matik.com.br) From: JoaoBR To: freebsd-amd64@freebsd.org Date: Tue, 3 Jan 2006 11:24:26 -0200 User-Agent: KMail/1.8.3 References: <200512301245.57820.andrea@brancatelli.it> <20060103040049.GA54882@dragon.NUXI.org> <20060103130320.GA691@bsd.trippelsdorf.de> In-Reply-To: <20060103130320.GA691@bsd.trippelsdorf.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200601031124.26176.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: AMD64 boot floppies 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, 03 Jan 2006 13:24:34 -0000 On Tuesday 03 January 2006 11:03, Markus Trippelsdorf wrote: > > please, Please, PLEASE no... why add the pain of floppies to the release :) historical and sentimental reasons? > > But I guess, the are many AMD64 machines that don't have a CDROM- or > DVD- burner build in. For these machines a few floppy images to start a > network installation would be helpful. you may like something like this: http://www.tnpi.biz/computing/freebsd/pxe-netboot.shtml 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 Tue Jan 3 15:54:56 2006 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 99EB416A41F for ; Tue, 3 Jan 2006 15:54:56 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DD9143D8B for ; Tue, 3 Jan 2006 15:54:45 +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 k03Fsd8w073650; Tue, 3 Jan 2006 08:54:40 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43BA9E3F.50505@samsco.org> Date: Tue, 03 Jan 2006 08:54:39 -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: Markus Trippelsdorf References: <200512301245.57820.andrea@brancatelli.it> <20051230130529.GK52756@ip.net.ua> <200512300834.51959.jhb@freebsd.org> <20060103040049.GA54882@dragon.NUXI.org> <20060103130320.GA691@bsd.trippelsdorf.de> In-Reply-To: <20060103130320.GA691@bsd.trippelsdorf.de> 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: freebsd-amd64@freebsd.org Subject: Re: AMD64 boot floppies 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, 03 Jan 2006 15:54:56 -0000 Markus Trippelsdorf wrote: > On Mon, Jan 02, 2006 at 08:00:49PM -0800, David O'Brien wrote: > >>On Fri, Dec 30, 2005 at 08:34:50AM -0500, John Baldwin wrote: >> >>>On Friday 30 December 2005 08:05 am, Ruslan Ermilov wrote: >>> >>>>On Fri, Dec 30, 2005 at 12:45:57PM +0100, Andrea Brancatelli wrote: >>>> >>>>>For i386 we have >>>>>ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/6.0-RELEASE/floppies/ >>>>>but for Amd64 there's no >>>>>ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/6.0-RELEASE/floppies/ >>>>> >>>>>How can I get installation floppies for 6.0 / amd64? >>>> >>>>http://www.freebsd.org/releases/6.0R/installation-amd64.html#FLOPPIES >>> >>>FYI, it would be trivial to support with the splitfs stuff now. You'd >>>basically just need to copy over the variables from i386 to set the >>>sizes, etc. >> >>please, Please, PLEASE no... why add the pain of floppies to the release >>mix when no one in their right mind as an AMD64 machine that has a floppy >>drive AND doesn't have a CDROM (or DVD) drive. > > > But I guess, the are many AMD64 machines that don't have a CDROM- or > DVD- burner build in. For these machines a few floppy images to start a > network installation would be helpful. > My impression was the floppy drives are disappearing from servers faster than CDROM drives are. It's certainly possible to start generating floppies for amd64, but that has not been done in a very long time, so it could turn into a big mess of unknown bugs. Also, we will eventually move to a new installer, one that cannot easily fit onto floppies. That day might not happen today or tomorrow, but it will happen sometime. Most server systems these days do support PXE booting, and that can actually be more convenient than floppies if handled correctly. Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 3 15:55:37 2006 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 B576416A420 for ; Tue, 3 Jan 2006 15:55:37 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F4DD43D86 for ; Tue, 3 Jan 2006 15:55:20 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1EtoVB-0007J3-00; Tue, 03 Jan 2006 16:55:09 +0100 Date: Tue, 3 Jan 2006 16:55:09 +0100 To: Francisco Reyes Message-ID: <20060103155509.GE13887@poupinou.org> References: <63675.24.71.129.36.1135718125.squirrel@imap.sd73.bc.ca> <200512291412.19476.peter@wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: freebsd-amd64@freebsd.org Subject: Re: No APM yet for AMD? 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, 03 Jan 2006 15:55:37 -0000 On Sat, Dec 31, 2005 at 01:09:18PM -0500, Francisco Reyes wrote: > Peter Wemm writes: > > >sysctl hw.acpi.battery.life (percentage) > >sysctl hw.acpi.battery.time (time remaining) > > With a 6.0 Release I could not even boot with ACPI. I had to put in > /boot/loader.conf > hint.acpi.0.disabled=0 > hint.apic.0.disabled=1 > > At that point sysctl variables for acpi showed > > hw.acpi.battery.life: -1 > hw.acpi.battery.time: -1 > hw.acpi.battery.state: 7 > hw.acpi.battery.units: 1 > hw.acpi.battery.info_expire: 5 > > > Upgraded to stable today. > I am now able to boot without having to disable acpi or apic. > However, the sysctl variables still show the same values. > What happens if you plug/unplug the AC adapter? Could you please put a link of an output from 'acpidump -d -t' somewhere? -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 3 17:12:59 2006 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 DBCFC16A41F for ; Tue, 3 Jan 2006 17:12:59 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A74B43D4C for ; Tue, 3 Jan 2006 17:12:47 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (zoraida.natserv.net [66.114.65.147]) by zoraida.natserv.net (Postfix) with ESMTP id 237237DF2; Tue, 3 Jan 2006 12:12:46 -0500 (EST) References: <63675.24.71.129.36.1135718125.squirrel@imap.sd73.bc.ca> <200512291412.19476.peter@wemm.org> <20060103155509.GE13887@poupinou.org> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: Bruno Ducrot Date: Tue, 03 Jan 2006 12:12:45 -0500 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: No APM yet for AMD? 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, 03 Jan 2006 17:13:00 -0000 Bruno Ducrot writes: >> hw.acpi.battery.life: -1 >> hw.acpi.battery.time: -1 >> hw.acpi.battery.state: 7 >> hw.acpi.battery.units: 1 >> hw.acpi.battery.info_expire: 5 > What happens if you plug/unplug the AC adapter? Variables remain exactly the same. > Could you please put a link of an output from 'acpidump -d -t' somewhere? http://public.natserv.net/acpidump.txt Thanks for taking a look. Put the machine info on the top of the file. The one "feature" I like is that if I close the machine it keeps on going. :-) Thinks I can do with that "feature".. * Put the machine away quickly when I reach my subway stop and then halt the machine at work/home. * Leave the maching building world or a long running port.. while I take it to work. From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 3 17:15:10 2006 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 CA89416A41F for ; Tue, 3 Jan 2006 17:15:10 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: from blue-ld-041.synserver.de (blue-ld-041.synserver.de [217.119.50.242]) by mx1.FreeBSD.org (Postfix) with SMTP id BB74243D86 for ; Tue, 3 Jan 2006 17:15:01 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: (qmail 11934 invoked by uid 0); 3 Jan 2006 17:14:55 -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-07.synserver.de with SMTP; 3 Jan 2006 17:14:54 -0000 Date: Tue, 3 Jan 2006 18:14:58 +0100 From: Markus Trippelsdorf To: Scott Long Message-ID: <20060103171458.GA688@bsd.trippelsdorf.de> References: <200512301245.57820.andrea@brancatelli.it> <20051230130529.GK52756@ip.net.ua> <200512300834.51959.jhb@freebsd.org> <20060103040049.GA54882@dragon.NUXI.org> <20060103130320.GA691@bsd.trippelsdorf.de> <43BA9E3F.50505@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43BA9E3F.50505@samsco.org> Cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 boot floppies 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, 03 Jan 2006 17:15:10 -0000 On Tue, Jan 03, 2006 at 08:54:39AM -0700, Scott Long wrote: > Markus Trippelsdorf wrote: > > >On Mon, Jan 02, 2006 at 08:00:49PM -0800, David O'Brien wrote: > > > >>On Fri, Dec 30, 2005 at 08:34:50AM -0500, John Baldwin wrote: > >> > >>>On Friday 30 December 2005 08:05 am, Ruslan Ermilov wrote: > >>> > >>>>On Fri, Dec 30, 2005 at 12:45:57PM +0100, Andrea Brancatelli wrote: > >>>> > >>>>>For i386 we have > >>>>>ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/6.0-RELEASE/floppies/ > >>>>>but for Amd64 there's no > >>>>>ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/6.0-RELEASE/floppies/ > >>>>> > >>>>>How can I get installation floppies for 6.0 / amd64? > >>>> > >>>>http://www.freebsd.org/releases/6.0R/installation-amd64.html#FLOPPIES > >>> > >>>FYI, it would be trivial to support with the splitfs stuff now. You'd > >>>basically just need to copy over the variables from i386 to set the > >>>sizes, etc. > >> > >>please, Please, PLEASE no... why add the pain of floppies to the release > >>mix when no one in their right mind as an AMD64 machine that has a floppy > >>drive AND doesn't have a CDROM (or DVD) drive. > > > > > >But I guess, the are many AMD64 machines that don't have a CDROM- or > >DVD- burner build in. For these machines a few floppy images to start a > >network installation would be helpful. > > > > My impression was the floppy drives are disappearing from servers faster > than CDROM drives are. It's certainly possible to start generating > floppies for amd64, but that has not been done in a very long time, so > it could turn into a big mess of unknown bugs. Also, we will eventually > move to a new installer, one that cannot easily fit onto floppies. That > day might not happen today or tomorrow, but it will happen sometime. > Most server systems these days do support PXE booting, and that can > actually be more convenient than floppies if handled correctly. Just an example: When I upgraded my old Celeron box a year ago, I had to buy a CDROM burner, so that I could burn the install CD for my new machine. Since than it is sitting idle in its slot. Had a floppy image been available at that time, it would have saved me the ~30 Euro for the burner. BTW, all other main BSD variants offer floppy images for the AMD64 architecture. -- Markus From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 3 17:20:19 2006 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 737BC16A41F for ; Tue, 3 Jan 2006 17:20:19 +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 E29BC43D9F for ; Tue, 3 Jan 2006 17:19:53 +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 k03HJpcd074050; Tue, 3 Jan 2006 10:19:51 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43BAB237.8020002@samsco.org> Date: Tue, 03 Jan 2006 10:19:51 -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: Markus Trippelsdorf References: <200512301245.57820.andrea@brancatelli.it> <20051230130529.GK52756@ip.net.ua> <200512300834.51959.jhb@freebsd.org> <20060103040049.GA54882@dragon.NUXI.org> <20060103130320.GA691@bsd.trippelsdorf.de> <43BA9E3F.50505@samsco.org> <20060103171458.GA688@bsd.trippelsdorf.de> In-Reply-To: <20060103171458.GA688@bsd.trippelsdorf.de> 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: freebsd-amd64@freebsd.org Subject: Re: AMD64 boot floppies 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, 03 Jan 2006 17:20:19 -0000 Markus Trippelsdorf wrote: > On Tue, Jan 03, 2006 at 08:54:39AM -0700, Scott Long wrote: > >>Markus Trippelsdorf wrote: >> >> >>>On Mon, Jan 02, 2006 at 08:00:49PM -0800, David O'Brien wrote: >>> >>> >>>>On Fri, Dec 30, 2005 at 08:34:50AM -0500, John Baldwin wrote: >>>> >>>> >>>>>On Friday 30 December 2005 08:05 am, Ruslan Ermilov wrote: >>>>> >>>>> >>>>>>On Fri, Dec 30, 2005 at 12:45:57PM +0100, Andrea Brancatelli wrote: >>>>>> >>>>>> >>>>>>>For i386 we have >>>>>>>ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/6.0-RELEASE/floppies/ >>>>>>>but for Amd64 there's no >>>>>>>ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/6.0-RELEASE/floppies/ >>>>>>> >>>>>>>How can I get installation floppies for 6.0 / amd64? >>>>>> >>>>>>http://www.freebsd.org/releases/6.0R/installation-amd64.html#FLOPPIES >>>>> >>>>>FYI, it would be trivial to support with the splitfs stuff now. You'd >>>>>basically just need to copy over the variables from i386 to set the >>>>>sizes, etc. >>>> >>>>please, Please, PLEASE no... why add the pain of floppies to the release >>>>mix when no one in their right mind as an AMD64 machine that has a floppy >>>>drive AND doesn't have a CDROM (or DVD) drive. >>> >>> >>>But I guess, the are many AMD64 machines that don't have a CDROM- or >>>DVD- burner build in. For these machines a few floppy images to start a >>>network installation would be helpful. >>> >> >>My impression was the floppy drives are disappearing from servers faster >>than CDROM drives are. It's certainly possible to start generating >>floppies for amd64, but that has not been done in a very long time, so >>it could turn into a big mess of unknown bugs. Also, we will eventually >>move to a new installer, one that cannot easily fit onto floppies. That >>day might not happen today or tomorrow, but it will happen sometime. >>Most server systems these days do support PXE booting, and that can >>actually be more convenient than floppies if handled correctly. > > > Just an example: > When I upgraded my old Celeron box a year ago, I had to buy a CDROM > burner, so that I could burn the install CD for my new machine. Since > than it is sitting idle in its slot. Had a floppy image been available > at that time, it would have saved me the ~30 Euro for the burner. > BTW, all other main BSD variants offer floppy images for the AMD64 > architecture. I'll happily accept patches from anyone who is interested in turning floppy support back on for amd64. I'm not rejecting the idea, I'm just saying that it might have some risks, and the overall long-term future is murky. Scott From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 3 18:06:17 2006 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 4744816A420 for ; Tue, 3 Jan 2006 18:06: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 228A143D67 for ; Tue, 3 Jan 2006 18:06:02 +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 5182140 for multiple; Tue, 03 Jan 2006 13:03:51 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k03I5bO4094388; Tue, 3 Jan 2006 13:05:40 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Tue, 3 Jan 2006 13:06:24 -0500 User-Agent: KMail/1.8.2 References: <200512301245.57820.andrea@brancatelli.it> <20060103171458.GA688@bsd.trippelsdorf.de> <43BAB237.8020002@samsco.org> In-Reply-To: <43BAB237.8020002@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601031306.25611.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1225/Mon Jan 2 12:54:07 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Markus Trippelsdorf Subject: Re: AMD64 boot floppies 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, 03 Jan 2006 18:06:17 -0000 On Tuesday 03 January 2006 12:19 pm, Scott Long wrote: > Markus Trippelsdorf wrote: > > On Tue, Jan 03, 2006 at 08:54:39AM -0700, Scott Long wrote: > >>Markus Trippelsdorf wrote: > >>>On Mon, Jan 02, 2006 at 08:00:49PM -0800, David O'Brien wrote: > >>>>On Fri, Dec 30, 2005 at 08:34:50AM -0500, John Baldwin wrote: > >>>>>On Friday 30 December 2005 08:05 am, Ruslan Ermilov wrote: > >>>>>>On Fri, Dec 30, 2005 at 12:45:57PM +0100, Andrea Brancatelli wrote: > >>>>>>>For i386 we have > >>>>>>>ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/6.0-RELEASE/floppies > >>>>>>>/ but for Amd64 there's no > >>>>>>>ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/6.0-RELEASE/floppie > >>>>>>>s/ > >>>>>>> > >>>>>>>How can I get installation floppies for 6.0 / amd64? > >>>>>> > >>>>>>http://www.freebsd.org/releases/6.0R/installation-amd64.html#FLOPPIES > >>>>> > >>>>>FYI, it would be trivial to support with the splitfs stuff now. You'd > >>>>>basically just need to copy over the variables from i386 to set the > >>>>>sizes, etc. > >>>> > >>>>please, Please, PLEASE no... why add the pain of floppies to the > >>>> release mix when no one in their right mind as an AMD64 machine that > >>>> has a floppy drive AND doesn't have a CDROM (or DVD) drive. > >>> > >>>But I guess, the are many AMD64 machines that don't have a CDROM- or > >>>DVD- burner build in. For these machines a few floppy images to start a > >>>network installation would be helpful. > >> > >>My impression was the floppy drives are disappearing from servers faster > >>than CDROM drives are. It's certainly possible to start generating > >>floppies for amd64, but that has not been done in a very long time, so > >>it could turn into a big mess of unknown bugs. Also, we will eventually > >>move to a new installer, one that cannot easily fit onto floppies. That > >>day might not happen today or tomorrow, but it will happen sometime. > >>Most server systems these days do support PXE booting, and that can > >>actually be more convenient than floppies if handled correctly. > > > > Just an example: > > When I upgraded my old Celeron box a year ago, I had to buy a CDROM > > burner, so that I could burn the install CD for my new machine. Since > > than it is sitting idle in its slot. Had a floppy image been available > > at that time, it would have saved me the ~30 Euro for the burner. > > BTW, all other main BSD variants offer floppy images for the AMD64 > > architecture. > > I'll happily accept patches from anyone who is interested in turning > floppy support back on for amd64. I'm not rejecting the idea, I'm just > saying that it might have some risks, and the overall long-term future > is murky. Should be pretty simple actually (untested): Index: Makefile =================================================================== RCS file: /usr/cvs/src/release/Makefile,v retrieving revision 1.895 diff -u -r1.895 Makefile --- Makefile 2 Jan 2006 13:29:58 -0000 1.895 +++ Makefile 3 Jan 2006 18:05:12 -0000 @@ -219,6 +219,12 @@ MFSLABEL= auto SEPARATE_LIVEFS= .elif ${TARGET_ARCH} == "amd64" +MAKE_FLOPPIES= true +FLOPPYSIZE= 1440 +FLOPPYSPLITSIZE= 1392 +FLOPPYINODE= 40000 +FLOPPYLABEL= fd1440 +BOOTINODE= 80000 MFSSIZE= 4096 MFSINODE= 8192 MFSLABEL= auto -- 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 Jan 3 18:35:55 2006 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 C9B9316A41F for ; Tue, 3 Jan 2006 18:35:55 +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 A2C0843D5A for ; Tue, 3 Jan 2006 18:35:54 +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 5184162 for ; Tue, 03 Jan 2006 13:34:04 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k03IZouU094652 for ; Tue, 3 Jan 2006 13:35:52 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Tue, 3 Jan 2006 13:36:40 -0500 User-Agent: KMail/1.8.2 References: <200512301245.57820.andrea@brancatelli.it> <200512300834.51959.jhb@freebsd.org> <20060103040049.GA54882@dragon.NUXI.org> In-Reply-To: <20060103040049.GA54882@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601031336.41132.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1226/Tue Jan 3 11:51:16 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Subject: Re: AMD64 boot floppies 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, 03 Jan 2006 18:35:55 -0000 On Monday 02 January 2006 11:00 pm, David O'Brien wrote: > On Fri, Dec 30, 2005 at 08:34:50AM -0500, John Baldwin wrote: > > On Friday 30 December 2005 08:05 am, Ruslan Ermilov wrote: > > > On Fri, Dec 30, 2005 at 12:45:57PM +0100, Andrea Brancatelli wrote: > > > > For i386 we have > > > > ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/6.0-RELEASE/floppies/ > > > > but for Amd64 there's no > > > > ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/6.0-RELEASE/floppies > > > >/ > > > > > > > > How can I get installation floppies for 6.0 / amd64? > > > > > > http://www.freebsd.org/releases/6.0R/installation-amd64.html#FLOPPIES > > > > FYI, it would be trivial to support with the splitfs stuff now. You'd > > basically just need to copy over the variables from i386 to set the > > sizes, etc. > > please, Please, PLEASE no... why add the pain of floppies to the release > mix when no one in their right mind as an AMD64 machine that has a floppy > drive AND doesn't have a CDROM (or DVD) drive. What pain? We no longer use custom kernels for floppy images. I think I've successfully removed the pain from floppies now. See the simple 5 or 6-line patch I posted in a reply to Scott. The makefiles now take care of splitting a GENERIC kernel up into however many floppies are needed, etc. The only possible change is that if the entire mfsroot doesn't fit on boot.flp you have to add 1 more line to define SPLIT_MFSROOT as on Alpha and then you are done. -- 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 Jan 3 18:51:07 2006 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 2EE5C16A41F for ; Tue, 3 Jan 2006 18:51:07 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id D403443D53 for ; Tue, 3 Jan 2006 18:50:55 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1EtrF9-0008Cx-00; Tue, 03 Jan 2006 19:50:47 +0100 Date: Tue, 3 Jan 2006 19:50:47 +0100 To: Francisco Reyes Message-ID: <20060103185047.GH13887@poupinou.org> References: <63675.24.71.129.36.1135718125.squirrel@imap.sd73.bc.ca> <200512291412.19476.peter@wemm.org> <20060103155509.GE13887@poupinou.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: freebsd-amd64@freebsd.org Subject: Re: No APM yet for AMD? 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, 03 Jan 2006 18:51:07 -0000 On Tue, Jan 03, 2006 at 12:12:45PM -0500, Francisco Reyes wrote: > Bruno Ducrot writes: > > >>hw.acpi.battery.life: -1 > >>hw.acpi.battery.time: -1 > >>hw.acpi.battery.state: 7 > >>hw.acpi.battery.units: 1 > >>hw.acpi.battery.info_expire: 5 > > >What happens if you plug/unplug the AC adapter? > > Variables remain exactly the same. > > >Could you please put a link of an output from 'acpidump -d -t' somewhere? > > http://public.natserv.net/acpidump.txt Well could you try to add this to your /boot/loader.conf: hw.acpi.osname="Microsoft Windows NT" It's because I want to check what happens if the following ASL is triggered: If (LEqual (SizeOf (\_OS), 0x14)) { BPOL (0x3C) } That's look like a workaround for Windows NT and that seems to be related to batteries and AC adapter. > > Thanks for taking a look. > Put the machine info on the top of the file. > > The one "feature" I like is that if I close the machine it keeps on going. > :-) > > Thinks I can do with that "feature".. > * Put the machine away quickly when I reach my subway stop and then halt > the machine at work/home. > * Leave the maching building world or a long running port.. while I take it > to work. -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 3 20:58:58 2006 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 383FC16A41F for ; Tue, 3 Jan 2006 20:58:58 +0000 (GMT) (envelope-from david@jetnet.co.uk) Received: from kosh.jetnet.co.uk (kosh.jetnet.co.uk [80.87.128.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA35543D66 for ; Tue, 3 Jan 2006 20:58:56 +0000 (GMT) (envelope-from david@jetnet.co.uk) Received: from localhost (localhost [127.0.0.1]) by kosh.jetnet.co.uk (Postfix) with ESMTP id 7A5E421D75; Tue, 3 Jan 2006 20:58:55 +0000 (GMT) Received: from kosh.jetnet.co.uk ([127.0.0.1]) by localhost (mail.jetnet.co.uk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 71098-05; Tue, 3 Jan 2006 20:58:44 +0000 (GMT) Received: from [192.168.0.90] (82-69-108-39.dsl.in-addr.zen.co.uk [82.69.108.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by kosh.jetnet.co.uk (Postfix) with ESMTP id 3A46520AE5; Tue, 3 Jan 2006 20:58:44 +0000 (GMT) Message-ID: <43BAE584.9080307@jetnet.co.uk> Date: Tue, 03 Jan 2006 20:58:44 +0000 From: David Reid User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051216) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Arno J. Klaassen" References: <20051231122034.599bbf8c.torfinn.ingolfsen@broadpark.no> <20051231125158.GA830@funes.schapachnik.com.ar> In-Reply-To: X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at jetnet.co.uk Cc: Fernando Schapachnik , freebsd-amd64@freebsd.org Subject: Re: Skype on FreeBSD / amd64 - what's the trick? 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, 03 Jan 2006 20:58:58 -0000 Arno J. Klaassen wrote: > Fernando Schapachnik writes: > > >>En un mensaje anterior, Torfinn Ingolfsen escribió: >> >>>Hi, >>> >>>I tried to install Skype on my amd64 machine, running FreeBSD >>>6.0-stable: >>>root@kg-quiet# uname -a >>>FreeBSD kg-quiet.kg4.no 6.0-STABLE FreeBSD 6.0-STABLE #1: Thu Dec 22 >>>06:29:24 CET 2005 root@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET >>>amd64 >>> >>>Looking at the makefile, I could see that the port was supposed to work >>>on both i386 and amd64, adn thought the install would go smoothly. >>>Boy, was I wrong. >>> >>>It seems that the port net/skype depends on graphics/linux_dri, but the >>>latter (linux_dri) is i386 only. >>>So, what's the trick to get Skype installed on amd64? >> >>If you have a 32-bit linux environment in place, just comment the >>i386 only line of the linux_dri Makefile. It worked for me and skype >>works fine. > > > there seem to be serious problems on many configurations with linux_dri > on amd64; > I just made a symlink libGL.so.1 -> libX11.so.6 > in /compat/linux/usr/X11R6/lib; this make Skype happy (which > does not seem to need reel GL functionality, just a valid libGL.so.1 > to start-up) and prevents my linux-apps which really use GL to bomb. I tried this and it worked! Now, if I can just figure out why my microphone doesn't work with it I'll have a working skype setup. Microphone doesn't seem to work under i386 either, so must be some setting I'm not getting right I guess... Thanks for the tip! david From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 3 22:27:23 2006 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 9574E16A420 for ; Tue, 3 Jan 2006 22:27:23 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: from blue-ld-032.synserver.de (blue-ld-032.synserver.de [217.119.50.235]) by mx1.FreeBSD.org (Postfix) with SMTP id 73A8643D5E for ; Tue, 3 Jan 2006 22:27:21 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: (qmail 20457 invoked by uid 0); 3 Jan 2006 22:27:18 -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-04.synserver.de with SMTP; 3 Jan 2006 22:27:17 -0000 Date: Tue, 3 Jan 2006 23:27:17 +0100 From: Markus Trippelsdorf To: John Baldwin Message-ID: <20060103222717.GA688@bsd.trippelsdorf.de> References: <200512301245.57820.andrea@brancatelli.it> <20060103171458.GA688@bsd.trippelsdorf.de> <43BAB237.8020002@samsco.org> <200601031306.25611.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200601031306.25611.jhb@freebsd.org> Cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 boot floppies 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, 03 Jan 2006 22:27:23 -0000 On Tue, Jan 03, 2006 at 01:06:24PM -0500, John Baldwin wrote: > On Tuesday 03 January 2006 12:19 pm, Scott Long wrote: > > Markus Trippelsdorf wrote: > > > On Tue, Jan 03, 2006 at 08:54:39AM -0700, Scott Long wrote: > > >>Markus Trippelsdorf wrote: > > >>>On Mon, Jan 02, 2006 at 08:00:49PM -0800, David O'Brien wrote: > > >>>>On Fri, Dec 30, 2005 at 08:34:50AM -0500, John Baldwin wrote: > > >>>>>On Friday 30 December 2005 08:05 am, Ruslan Ermilov wrote: > > >>>>>>On Fri, Dec 30, 2005 at 12:45:57PM +0100, Andrea Brancatelli wrote: > > >>>>>>>For i386 we have > > >>>>>>>ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/6.0-RELEASE/floppies > > >>>>>>>/ but for Amd64 there's no > > >>>>>>>ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/6.0-RELEASE/floppie > > >>>>>>>s/ > > >>>>>>> > > >>>>>>>How can I get installation floppies for 6.0 / amd64? > > >>>>>> > > >>>>>>http://www.freebsd.org/releases/6.0R/installation-amd64.html#FLOPPIES > > >>>>> > > >>>>>FYI, it would be trivial to support with the splitfs stuff now. You'd > > >>>>>basically just need to copy over the variables from i386 to set the > > >>>>>sizes, etc. > > >>>> > > >>>>please, Please, PLEASE no... why add the pain of floppies to the > > >>>> release mix when no one in their right mind as an AMD64 machine that > > >>>> has a floppy drive AND doesn't have a CDROM (or DVD) drive. > > >>> > > >>>But I guess, the are many AMD64 machines that don't have a CDROM- or > > >>>DVD- burner build in. For these machines a few floppy images to start a > > >>>network installation would be helpful. > > >> > > >>My impression was the floppy drives are disappearing from servers faster > > >>than CDROM drives are. It's certainly possible to start generating > > >>floppies for amd64, but that has not been done in a very long time, so > > >>it could turn into a big mess of unknown bugs. Also, we will eventually > > >>move to a new installer, one that cannot easily fit onto floppies. That > > >>day might not happen today or tomorrow, but it will happen sometime. > > >>Most server systems these days do support PXE booting, and that can > > >>actually be more convenient than floppies if handled correctly. > > > > > > Just an example: > > > When I upgraded my old Celeron box a year ago, I had to buy a CDROM > > > burner, so that I could burn the install CD for my new machine. Since > > > than it is sitting idle in its slot. Had a floppy image been available > > > at that time, it would have saved me the ~30 Euro for the burner. > > > BTW, all other main BSD variants offer floppy images for the AMD64 > > > architecture. > > > > I'll happily accept patches from anyone who is interested in turning > > floppy support back on for amd64. I'm not rejecting the idea, I'm just > > saying that it might have some risks, and the overall long-term future > > is murky. > > Should be pretty simple actually (untested): > > Index: Makefile > =================================================================== > RCS file: /usr/cvs/src/release/Makefile,v > retrieving revision 1.895 > diff -u -r1.895 Makefile > --- Makefile 2 Jan 2006 13:29:58 -0000 1.895 > +++ Makefile 3 Jan 2006 18:05:12 -0000 > @@ -219,6 +219,12 @@ > MFSLABEL= auto > SEPARATE_LIVEFS= > .elif ${TARGET_ARCH} == "amd64" > +MAKE_FLOPPIES= true > +FLOPPYSIZE= 1440 > +FLOPPYSPLITSIZE= 1392 > +FLOPPYINODE= 40000 > +FLOPPYLABEL= fd1440 > +BOOTINODE= 80000 > MFSSIZE= 4096 > MFSINODE= 8192 > MFSLABEL= auto > ... Making the kernel boot floppies... sh /usr/src/release/scripts/split-file.sh /R/stage/kernels/kernel.gz /R/stage/floppyset/kern "Kernel" + FILE=/R/stage/kernels/kernel.gz + shift + DEST=/R/stage/floppyset/kern + shift + CHUNK_SIZE=Kernel + shift + DESCR= + shift shift: can't shift that many *** Error code 2 Stop in /usr/src/release. *** Error code 1 -- Markus From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 3 22:29:00 2006 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 28D3616A41F for ; Tue, 3 Jan 2006 22:29:00 +0000 (GMT) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 249FB43D48 for ; Tue, 3 Jan 2006 22:28:58 +0000 (GMT) (envelope-from arno@heho.snv.jussieu.fr) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.13.5/jtpda-5.4) with ESMTP id k03MSvRs062121 for ; Tue, 3 Jan 2006 23:28:57 +0100 (CET) X-Ids: 166 Received: from heho.labo (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.13.3/jtpda-5.2) with ESMTP id k03MSuPY037417 for ; Tue, 3 Jan 2006 23:28:56 +0100 (MET) Received: (from arno@localhost) by heho.labo (8.13.3/8.13.1/Submit) id k03MSp3L037413; Tue, 3 Jan 2006 23:28:51 +0100 (MET) (envelope-from arno) Sender: arno@heho.snv.jussieu.fr To: freebsd-amd64@freebsd.org Cc: freebsd-amd64@freebsd.org References: <20051231122034.599bbf8c.torfinn.ingolfsen@broadpark.no> <20051231125158.GA830@funes.schapachnik.com.ar> <20060103040207.GB54882@dragon.NUXI.org> From: "Arno J. Klaassen" Date: 03 Jan 2006 23:28:51 +0100 In-Reply-To: <20060103040207.GB54882@dragon.NUXI.org> Message-ID: Lines: 40 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.7.2 (shiva.jussieu.fr [134.157.0.166]); Tue, 03 Jan 2006 23:28:57 +0100 (CET) X-Antivirus: scanned by sophie at shiva.jussieu.fr X-Miltered: at shiva.jussieu.fr with ID 43BAFAA9.001 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Subject: Re: Skype on FreeBSD / amd64 - what's the trick? 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, 03 Jan 2006 22:29:00 -0000 "David O'Brien" writes: > On Mon, Jan 02, 2006 at 11:14:10PM +0100, Arno J. Klaassen wrote: > > Fernando Schapachnik writes: > > > En un mensaje anterior, Torfinn Ingolfsen escribió: > > > > I tried to install Skype on my amd64 machine, running FreeBSD > > > > 6.0-stable: > ... > > > > It seems that the port net/skype depends on graphics/linux_dri, but the > > > > latter (linux_dri) is i386 only. > > > > So, what's the trick to get Skype installed on amd64? > > > > > > If you have a 32-bit linux environment in place, just comment the > > > i386 only line of the linux_dri Makefile. It worked for me and skype > > > works fine. > > > > there seem to be serious problems on many configurations with linux_dri > > on amd64; > > I just made a symlink libGL.so.1 -> libX11.so.6 > > in /compat/linux/usr/X11R6/lib; this make Skype happy (which > > does not seem to need reel GL functionality, just a valid libGL.so.1 > > to start-up) and prevents my linux-apps which really use GL to bomb. > > My $0.02 > > Patch to /usr/ports anyone? :-) Installing a fake libGL.so.1 in /usr/X11R6/share/skype and use LD_LIBRARY_PATH AND ENOENT /compat/linux/usr/X11R6/lib/libGL.so.1 will probably infer less with futur development on linux_dri, no? Arno -- Arno J. Klaassen SCITO S.A. 8 rue des Haies F-75020 Paris, France http://scito.com From owner-freebsd-amd64@FreeBSD.ORG Tue Jan 3 23:32:16 2006 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 1304616A41F for ; Tue, 3 Jan 2006 23:32:16 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: from blue-ld-041.synserver.de (blue-ld-041.synserver.de [217.119.50.242]) by mx1.FreeBSD.org (Postfix) with SMTP id 7C21C43D48 for ; Tue, 3 Jan 2006 23:32:14 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: (qmail 14557 invoked by uid 0); 3 Jan 2006 23:32:04 -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-07.synserver.de with SMTP; 3 Jan 2006 23:32:04 -0000 Date: Wed, 4 Jan 2006 00:32:10 +0100 From: Markus Trippelsdorf To: John Baldwin Message-ID: <20060103233210.GB688@bsd.trippelsdorf.de> References: <200512301245.57820.andrea@brancatelli.it> <20060103171458.GA688@bsd.trippelsdorf.de> <43BAB237.8020002@samsco.org> <200601031306.25611.jhb@freebsd.org> <20060103222717.GA688@bsd.trippelsdorf.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060103222717.GA688@bsd.trippelsdorf.de> Cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 boot floppies 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, 03 Jan 2006 23:32:16 -0000 On Tue, Jan 03, 2006 at 11:27:17PM +0100, Markus Trippelsdorf wrote: ... > > > > Should be pretty simple actually (untested): > > > > Index: Makefile > > =================================================================== > > RCS file: /usr/cvs/src/release/Makefile,v > > retrieving revision 1.895 > > diff -u -r1.895 Makefile > > --- Makefile 2 Jan 2006 13:29:58 -0000 1.895 > > +++ Makefile 3 Jan 2006 18:05:12 -0000 > > @@ -219,6 +219,12 @@ > > MFSLABEL= auto > > SEPARATE_LIVEFS= > > .elif ${TARGET_ARCH} == "amd64" > > +MAKE_FLOPPIES= true > > +FLOPPYSIZE= 1440 > > +FLOPPYSPLITSIZE= 1392 > > +FLOPPYINODE= 40000 > > +FLOPPYLABEL= fd1440 > > +BOOTINODE= 80000 > > MFSSIZE= 4096 > > MFSINODE= 8192 > > MFSLABEL= auto > > > ... > Making the kernel boot floppies... > sh /usr/src/release/scripts/split-file.sh /R/stage/kernels/kernel.gz > /R/stage/floppyset/kern "Kernel" > + FILE=/R/stage/kernels/kernel.gz > + shift > + DEST=/R/stage/floppyset/kern > + shift > + CHUNK_SIZE=Kernel > + shift > + DESCR= > + shift > shift: can't shift that many > *** Error code 2 It's actually working. I had to copy the patched Makefile to the chrootdir by hand. Then I did a "make floppies.1" and now have four floppy images in the /R/stage/floppies directory. Sorry for the noise; I will test the images tomorrow. -- Markus From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 4 03:40:58 2006 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 6367116A41F for ; Wed, 4 Jan 2006 03:40:58 +0000 (GMT) (envelope-from recompile2@yahoo.com) Received: from web54315.mail.yahoo.com (web54315.mail.yahoo.com [206.190.49.125]) by mx1.FreeBSD.org (Postfix) with SMTP id 94C1743D5A for ; Wed, 4 Jan 2006 03:40:57 +0000 (GMT) (envelope-from recompile2@yahoo.com) Received: (qmail 45907 invoked by uid 60001); 4 Jan 2006 03:40:56 -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=tXGFmbPNg9LV22qsDBnnDon+dkZxHYt0zJSDrQCMiSIZiYpNtRSm2BpAaHzpNnxgObtaTDrMX2blvVOgcNHwLIw0zFMwH6sc+dkVI34FYfLY+5Woz+EjYCv2JCmnTurpirR9X65a0zVoJxjmHIpIIRl6lby4XUv2VUQUJmG1Qxc= ; Message-ID: <20060104034056.45903.qmail@web54315.mail.yahoo.com> Received: from [64.77.192.148] by web54315.mail.yahoo.com via HTTP; Tue, 03 Jan 2006 19:40:56 PST Date: Tue, 3 Jan 2006 19:40:56 -0800 (PST) From: Mikey Galum To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: recom for newegg amd64 box? 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, 04 Jan 2006 03:40:58 -0000 If I study http://www.freebsd.org/platforms/amd64/motherboards.html, pick a motherboard that appears to be supported and then try to locate a manufacturer that has a prebuilt system with that mobo, or a motherboard bundle, I run into problems. Newegg doesn't have this or that exact motherboard, bla bla bla, mwave stopped stocking that the other week, blablabla. Can someone recommend a simple reliable amd64 motherboard that's readily available as a bundle or even a prebuilt system? I would have hoped something like an asus A8N32-sli dlx with athlon 64x2 3800+ 2x512MB RAM, etc would be nice but I haven't been able to learn if this is supported. __________________________________________ Yahoo! DSL – Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 4 10:58:21 2006 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 0ABCF16A41F for ; Wed, 4 Jan 2006 10:58:21 +0000 (GMT) (envelope-from groot@kde.org) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60ACA43D5C for ; Wed, 4 Jan 2006 10:58:20 +0000 (GMT) (envelope-from groot@kde.org) Received: from odin.cs.kun.nl [131.174.33.33] (helo=localhost.englishbreakfastnetwork.org) by pandora.cs.kun.nl (8.13.5/5.7) with ESMTP id k04AwHZM008144; Wed, 4 Jan 2006 11:58:17 +0100 (MET) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Wed, 4 Jan 2006 11:58:11 +0100 User-Agent: KMail/1.9.1 References: <20060104034056.45903.qmail@web54315.mail.yahoo.com> In-Reply-To: <20060104034056.45903.qmail@web54315.mail.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1251287.yoUbo9BDxk"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200601041158.16634.groot@kde.org> X-Spam-Score: 1.833 (*) BAYES_50,FORGED_RCVD_HELO X-Scanned-By: MIMEDefang 2.48 on 131.174.33.4 Cc: Mikey Galum Subject: Re: recom for newegg amd64 box? 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, 04 Jan 2006 10:58:21 -0000 --nextPart1251287.yoUbo9BDxk Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 04 January 2006 04:40, Mikey Galum wrote: > Can someone recommend a simple reliable amd64 > motherboard that's > readily available as a bundle or even a prebuilt > system? Straightforward, simple, reliable, has worked since 5.1-R? Via KT800 based= =20 boards, or KT890. How to find those boards? Look for a V in the name :) A8V= ,=20 K8V, that kind of thing. And they're getting harder to find (and come to=20 think of it, might be socket 754 which you don't want). =46eatureful, can be a total bitch to set up, working nicely in 6.0-R? nFor= ce4=20 based boards will do, and they're _everywhere_. But do some searching first= -=20 the Asus A8N-VM and variants will have you hex-editing BIOS code before it= =20 will boot anything but Windows in a useful way. > I would have hoped something like an asus A8N32-sli > dlx with > athlon 64x2 3800+ 2x512MB RAM, etc would be nice but I > haven't > been able to learn if this is supported. Half the battle is getting reports for those boards that _do_ work. Not=20 everybody bothers to report them. =2D-=20 These are your friends - Adem GPG: FEA2 A3FE Adriaan de Groot --nextPart1251287.yoUbo9BDxk Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBDu6pIdqzuAf6io/4RArOuAKChdpCmmlgficGUAVivr39N5hIcSACfd5IT 55akoqOChsjIcSq8MGdO8so= =WgkX -----END PGP SIGNATURE----- --nextPart1251287.yoUbo9BDxk-- From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 4 15:14:15 2006 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 7275D16A41F for ; Wed, 4 Jan 2006 15:14:15 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EF0843D55 for ; Wed, 4 Jan 2006 15:14:14 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (zoraida.natserv.net [66.114.65.147]) by zoraida.natserv.net (Postfix) with ESMTP id 5711F7E9D; Wed, 4 Jan 2006 10:14:13 -0500 (EST) References: <63675.24.71.129.36.1135718125.squirrel@imap.sd73.bc.ca> <200512291412.19476.peter@wemm.org> <20060103155509.GE13887@poupinou.org> <20060103185047.GH13887@poupinou.org> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: Bruno Ducrot Date: Wed, 04 Jan 2006 10:14:13 -0500 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: No APM yet for AMD? 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, 04 Jan 2006 15:14:15 -0000 Bruno Ducrot writes: >> http://public.natserv.net/acpidump.txt > > Well could you try to add this to your /boot/loader.conf: > hw.acpi.osname="Microsoft Windows NT" Done > It's because I want to check what happens if the following ASL is > triggered: > > If (LEqual (SizeOf (\_OS), 0x14)) > { > BPOL (0x3C) > } Second dump on the same location... different name http://public.natserv.net/acpidump2.txt > That's look like a workaround for Windows NT and that seems to > be related to batteries and AC adapter. Not sure what was supposed to happen after trying the change in loader.conf, but I tried "sysctl -a |grep acpi.bat" and the results are the same as before. hw.acpi.battery.life: -1 hw.acpi.battery.time: -1 hw.acpi.battery.state: 7 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 4 15:59:09 2006 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 185B616A41F for ; Wed, 4 Jan 2006 15:59:09 +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 E474843D77 for ; Wed, 4 Jan 2006 15:59:08 +0000 (GMT) (envelope-from marquis@roble.com) Date: Wed, 4 Jan 2006 07:59:08 -0800 (PST) From: Roger Marquis To: freebsd-amd64@freebsd.org In-Reply-To: <20060104120024.2556B16A420@hub.freebsd.org> Message-ID: <20060104075019.W36259@roble.com> References: <20060104120024.2556B16A420@hub.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: AMD64 boot floppies 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, 04 Jan 2006 15:59:09 -0000 Markus Trippelsdorf wrote: > When I upgraded my old Celeron box a year ago, I had to buy a CDROM > burner, so that I could burn the install CD for my new machine. Since > than it is sitting idle in its slot. You could also have purchased a USB-CD-RW or USB-DVD-RW. The problem with floppies is their A) tendency to develop bad sectors, and B) increasing rarity. The lines of code needed for a boot floppy would be much better spent on other bootable media, Flash, DVD, etc, all of which would have larger and more appreciative audiences. -- Roger Marquis Roble Systems Consulting http://www.roble.com/ From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 4 16:14:19 2006 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 4E55116A41F for ; Wed, 4 Jan 2006 16:14:19 +0000 (GMT) (envelope-from david@jetnet.co.uk) Received: from kosh.jetnet.co.uk (kosh.jetnet.co.uk [80.87.128.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id B122943D53 for ; Wed, 4 Jan 2006 16:14:18 +0000 (GMT) (envelope-from david@jetnet.co.uk) Received: from localhost (localhost [127.0.0.1]) by kosh.jetnet.co.uk (Postfix) with ESMTP id 36B0D220FF for ; Wed, 4 Jan 2006 16:14:18 +0000 (GMT) Received: from kosh.jetnet.co.uk ([127.0.0.1]) by localhost (mail.jetnet.co.uk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 82153-02-25 for ; Wed, 4 Jan 2006 16:14:09 +0000 (GMT) Received: from [192.168.0.90] (82-69-108-39.dsl.in-addr.zen.co.uk [82.69.108.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by kosh.jetnet.co.uk (Postfix) with ESMTP id 185ED20A2A for ; Wed, 4 Jan 2006 16:14:09 +0000 (GMT) Message-ID: <43BBF457.3030506@jetnet.co.uk> Date: Wed, 04 Jan 2006 16:14:15 +0000 From: David Reid User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051216) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@freebsd.org X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at jetnet.co.uk Subject: acpi on nVidia 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, 04 Jan 2006 16:14:19 -0000 In my boot sequence I see these lines... ACPI APIC Table: ... acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR ACPI seems to be working so I'm assuming this isn't something to worry about? Who's the best person to follow this up with? Ta david From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 4 16:18:47 2006 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 EA05F16A41F; Wed, 4 Jan 2006 16:18:47 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CF2A43D55; Wed, 4 Jan 2006 16:18:46 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1EuBLW-0001Jf-00; Wed, 04 Jan 2006 17:18:42 +0100 Date: Wed, 4 Jan 2006 17:18:42 +0100 To: Francisco Reyes Message-ID: <20060104161842.GK13887@poupinou.org> References: <63675.24.71.129.36.1135718125.squirrel@imap.sd73.bc.ca> <200512291412.19476.peter@wemm.org> <20060103155509.GE13887@poupinou.org> <20060103185047.GH13887@poupinou.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: freebsd-acpi@FreeBSD.org, freebsd-amd64@freebsd.org Subject: Re: No APM yet for AMD? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-acpi@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 16:18:48 -0000 On Wed, Jan 04, 2006 at 10:14:13AM -0500, Francisco Reyes wrote: > Bruno Ducrot writes: > > >>http://public.natserv.net/acpidump.txt > > > >Well could you try to add this to your /boot/loader.conf: > >hw.acpi.osname="Microsoft Windows NT" > > Done > > > >It's because I want to check what happens if the following ASL is > >triggered: > > > >If (LEqual (SizeOf (\_OS), 0x14)) > >{ > > BPOL (0x3C) > >} > > Second dump on the same location... different name > http://public.natserv.net/acpidump2.txt > > >That's look like a workaround for Windows NT and that seems to > >be related to batteries and AC adapter. > > Not sure what was supposed to happen after trying the change in > loader.conf, but I tried "sysctl -a |grep acpi.bat" and the results are the > same as before. > > hw.acpi.battery.life: -1 > hw.acpi.battery.time: -1 > hw.acpi.battery.state: 7 > hw.acpi.battery.units: 1 > hw.acpi.battery.info_expire: 5 It was a stupid idea, sorry. I will look a little bit more. I think I begin to understand what's wrong, but I need to look a little bit further. I also CC to freebsd-acpi@ with a reply-to accordingly. Cheers, -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 4 16:23:06 2006 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 1D11416A41F for ; Wed, 4 Jan 2006 16:23:06 +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 9C6F543D58 for ; Wed, 4 Jan 2006 16:23:01 +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 5270584 for multiple; Wed, 04 Jan 2006 11:24:18 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k04GMpYu003698; Wed, 4 Jan 2006 11:22:52 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Wed, 4 Jan 2006 11:23:41 -0500 User-Agent: KMail/1.8.2 References: <20060104120024.2556B16A420@hub.freebsd.org> <20060104075019.W36259@roble.com> In-Reply-To: <20060104075019.W36259@roble.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601041123.42453.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1229/Wed Jan 4 10:08:11 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Roger Marquis Subject: Re: AMD64 boot floppies 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, 04 Jan 2006 16:23:06 -0000 On Wednesday 04 January 2006 10:59 am, Roger Marquis wrote: > Markus Trippelsdorf wrote: > > When I upgraded my old Celeron box a year ago, I had to buy a CDROM > > burner, so that I could burn the install CD for my new machine. Since > > than it is sitting idle in its slot. > > You could also have purchased a USB-CD-RW or USB-DVD-RW. > > The problem with floppies is their A) tendency to develop bad > sectors, and B) increasing rarity. The lines of code needed for a > boot floppy would be much better spent on other bootable media, > Flash, DVD, etc, all of which would have larger and more > appreciative audiences. There isn't any code needed 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 Wed Jan 4 16:24:09 2006 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 0513916A41F for ; Wed, 4 Jan 2006 16:24:09 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: from blue-ld-032.synserver.de (blue-ld-032.synserver.de [217.119.50.235]) by mx1.FreeBSD.org (Postfix) with SMTP id 2A47E43D5C for ; Wed, 4 Jan 2006 16:24:05 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: (qmail 4203 invoked by uid 0); 4 Jan 2006 16:23:57 -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-04.synserver.de with SMTP; 4 Jan 2006 16:23:56 -0000 Date: Wed, 4 Jan 2006 17:23:56 +0100 From: Markus Trippelsdorf To: Roger Marquis Message-ID: <20060104162356.GA691@bsd.trippelsdorf.de> References: <20060104120024.2556B16A420@hub.freebsd.org> <20060104075019.W36259@roble.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060104075019.W36259@roble.com> Cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 boot floppies 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, 04 Jan 2006 16:24:09 -0000 On Wed, Jan 04, 2006 at 07:59:08AM -0800, Roger Marquis wrote: > Markus Trippelsdorf wrote: > >When I upgraded my old Celeron box a year ago, I had to buy a CDROM > >burner, so that I could burn the install CD for my new machine. Since > >than it is sitting idle in its slot. > > You could also have purchased a USB-CD-RW or USB-DVD-RW. Sure, but the point is that I don't need any kind of burner. > The problem with floppies is their A) tendency to develop bad > sectors, and B) increasing rarity. The lines of code needed for a > boot floppy would be much better spent on other bootable media, > Flash, DVD, etc, all of which would have larger and more > appreciative audiences. The infrastructure to automatically produce the boot floppies is already there. All that is needed, is the short patch from John to turn it on. BTW I tested the floppies today and everything is working without any problem. -- Markus From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 4 16:54:53 2006 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 BD21B16A420; Wed, 4 Jan 2006 16:54:53 +0000 (GMT) (envelope-from ariff@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40A7243D53; Wed, 4 Jan 2006 16:54:53 +0000 (GMT) (envelope-from ariff@FreeBSD.org) Received: from misaki (root@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with SMTP id k04GsoEo027860; Wed, 4 Jan 2006 16:54:51 GMT (envelope-from ariff@FreeBSD.org) Date: Thu, 5 Jan 2006 00:54:41 +0800 From: Ariff Abdullah To: freebsd-acpi@FreeBSD.org Message-Id: <20060105005441.029835c1.ariff@FreeBSD.org> In-Reply-To: <20060104161842.GK13887@poupinou.org> References: <63675.24.71.129.36.1135718125.squirrel@imap.sd73.bc.ca> <200512291412.19476.peter@wemm.org> <20060103155509.GE13887@poupinou.org> <20060103185047.GH13887@poupinou.org> <20060104161842.GK13887@poupinou.org> Organization: FreeBSD X-Mailer: /usr/local/lib/ruby/1.8/net/smtp.rb Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Thu__5_Jan_2006_00_54_41_+0800_x7.9sabrhOeUmjCa" Cc: freebsd-amd64@FreeBSD.org Subject: Re: No APM yet for AMD? 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, 04 Jan 2006 16:54:54 -0000 --Signature=_Thu__5_Jan_2006_00_54_41_+0800_x7.9sabrhOeUmjCa Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, 4 Jan 2006 17:18:42 +0100 Bruno Ducrot wrote: > On Wed, Jan 04, 2006 at 10:14:13AM -0500, Francisco Reyes wrote: > > Bruno Ducrot writes: > >=20 > > >>http://public.natserv.net/acpidump.txt > > > > > >Well could you try to add this to your /boot/loader.conf: > > >hw.acpi.osname=3D"Microsoft Windows NT" > >=20 > > Done > >=20 > >=20 > > >It's because I want to check what happens if the following ASL is > > >triggered: > > > > > >If (LEqual (SizeOf (\_OS), 0x14)) > > >{ > > > BPOL (0x3C) > > >} > >=20 > > Second dump on the same location... different name > > http://public.natserv.net/acpidump2.txt > >=20 > > >That's look like a workaround for Windows NT and that seems to > > >be related to batteries and AC adapter. > >=20 > > Not sure what was supposed to happen after trying the change in=20 > > loader.conf, but I tried "sysctl -a |grep acpi.bat" and the > > results are the same as before. > >=20 > > hw.acpi.battery.life: -1=20 > > hw.acpi.battery.time: -1 > > hw.acpi.battery.state: 7 > > hw.acpi.battery.units: 1 > > hw.acpi.battery.info_expire: 5 >=20 > It was a stupid idea, sorry. I will look a little bit more. I > think I begin to understand what's wrong, but I need to look a > little bit further. >=20 > I also CC to freebsd-acpi@ with a reply-to accordingly. >=20 Few acpi BIOSes does not support _BST (battery status) method, causing that type of weird sysctl output (since it depends solely on _BST). Your hope is to use acpiconf(8) i.e acpiconf -i . Unfortunately, acpiconf itself does not display all possible values. Try this patch against usr.sbin/acpi/acpiconf/acpiconf.c http://people.freebsd.org/~ariff/acpi/acpiconf.c.diff Hopefully you will have the proper output in terms of percentage. You won't have advance battery status such as remaining time and few others. This is a limitation for BIOSes without _BST. I believe Nate Lawson is the right person to comment on this. -- Ariff Abdullah FreeBSD --Signature=_Thu__5_Jan_2006_00_54_41_+0800_x7.9sabrhOeUmjCa Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDu/3Ulr+deMUwTNoRAvt6AKCw1i6PO/2XDUFG+H7ThfP+Y4wMfwCg0yTz n+ZsS3t+xbZlSm8K/Ps0slg= =KiTK -----END PGP SIGNATURE----- --Signature=_Thu__5_Jan_2006_00_54_41_+0800_x7.9sabrhOeUmjCa-- From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 4 17:12:49 2006 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 9A87416A426 for ; Wed, 4 Jan 2006 17:12:49 +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 1AD6343D6D for ; Wed, 4 Jan 2006 17:12:47 +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 k04HCkpY080916; Wed, 4 Jan 2006 10:12:47 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43BC020E.4000606@samsco.org> Date: Wed, 04 Jan 2006 10:12:46 -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: Markus Trippelsdorf References: <20060104120024.2556B16A420@hub.freebsd.org> <20060104075019.W36259@roble.com> <20060104162356.GA691@bsd.trippelsdorf.de> In-Reply-To: <20060104162356.GA691@bsd.trippelsdorf.de> 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: Roger Marquis , freebsd-amd64@freebsd.org Subject: Re: AMD64 boot floppies 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, 04 Jan 2006 17:12:49 -0000 Markus Trippelsdorf wrote: > On Wed, Jan 04, 2006 at 07:59:08AM -0800, Roger Marquis wrote: > >>Markus Trippelsdorf wrote: >> >>>When I upgraded my old Celeron box a year ago, I had to buy a CDROM >>>burner, so that I could burn the install CD for my new machine. Since >>>than it is sitting idle in its slot. >> >>You could also have purchased a USB-CD-RW or USB-DVD-RW. > > > Sure, but the point is that I don't need any kind of burner. > > >>The problem with floppies is their A) tendency to develop bad >>sectors, and B) increasing rarity. The lines of code needed for a >>boot floppy would be much better spent on other bootable media, >>Flash, DVD, etc, all of which would have larger and more >>appreciative audiences. > > > The infrastructure to automatically produce the boot floppies is > already there. All that is needed, is the short patch from John to > turn it on. > BTW I tested the floppies today and everything is working without any > problem. > Ah, so you built a release with John's patch, and the result works? If so, we might as well commit it. How many floppies were generated? Scott From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 4 17:24:43 2006 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 8D73B16A41F for ; Wed, 4 Jan 2006 17:24:43 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: from blue-ld-032.synserver.de (blue-ld-032.synserver.de [217.119.50.235]) by mx1.FreeBSD.org (Postfix) with SMTP id 8456F43D8A for ; Wed, 4 Jan 2006 17:24:39 +0000 (GMT) (envelope-from markus@trippelsdorf.de) Received: (qmail 17244 invoked by uid 0); 4 Jan 2006 17:24:33 -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-04.synserver.de with SMTP; 4 Jan 2006 17:24:32 -0000 Date: Wed, 4 Jan 2006 18:24:32 +0100 From: Markus Trippelsdorf To: Scott Long Message-ID: <20060104172432.GB691@bsd.trippelsdorf.de> References: <20060104120024.2556B16A420@hub.freebsd.org> <20060104075019.W36259@roble.com> <20060104162356.GA691@bsd.trippelsdorf.de> <43BC020E.4000606@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43BC020E.4000606@samsco.org> Cc: Roger Marquis , freebsd-amd64@freebsd.org Subject: Re: AMD64 boot floppies 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, 04 Jan 2006 17:24:43 -0000 On Wed, Jan 04, 2006 at 10:12:46AM -0700, Scott Long wrote: > Markus Trippelsdorf wrote: > > >On Wed, Jan 04, 2006 at 07:59:08AM -0800, Roger Marquis wrote: > > > >>Markus Trippelsdorf wrote: > >> > >>>When I upgraded my old Celeron box a year ago, I had to buy a CDROM > >>>burner, so that I could burn the install CD for my new machine. Since > >>>than it is sitting idle in its slot. > >> > >>You could also have purchased a USB-CD-RW or USB-DVD-RW. > > > > > >Sure, but the point is that I don't need any kind of burner. > > > > > >>The problem with floppies is their A) tendency to develop bad > >>sectors, and B) increasing rarity. The lines of code needed for a > >>boot floppy would be much better spent on other bootable media, > >>Flash, DVD, etc, all of which would have larger and more > >>appreciative audiences. > > > > > >The infrastructure to automatically produce the boot floppies is > >already there. All that is needed, is the short patch from John to > >turn it on. > >BTW I tested the floppies today and everything is working without any > >problem. > > > > Ah, so you built a release with John's patch, and the result works? Yes. > If so, we might as well commit it. How many floppies were generated? Four floppies: boot and kern1-3. (I used RELEASETAG=RELENG_6 for the build) -- Markus From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 4 17:57:54 2006 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 0B02616A41F; Wed, 4 Jan 2006 17:57:54 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE54243D45; Wed, 4 Jan 2006 17:57:52 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1EuCtS-0001UC-00; Wed, 04 Jan 2006 18:57:50 +0100 Date: Wed, 4 Jan 2006 18:57:50 +0100 To: Ariff Abdullah Message-ID: <20060104175750.GM13887@poupinou.org> References: <63675.24.71.129.36.1135718125.squirrel@imap.sd73.bc.ca> <200512291412.19476.peter@wemm.org> <20060103155509.GE13887@poupinou.org> <20060103185047.GH13887@poupinou.org> <20060104161842.GK13887@poupinou.org> <20060105005441.029835c1.ariff@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060105005441.029835c1.ariff@FreeBSD.org> User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: freebsd-acpi@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: No APM yet for AMD? 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, 04 Jan 2006 17:57:54 -0000 On Thu, Jan 05, 2006 at 12:54:41AM +0800, Ariff Abdullah wrote: > On Wed, 4 Jan 2006 17:18:42 +0100 > Bruno Ducrot wrote: > > On Wed, Jan 04, 2006 at 10:14:13AM -0500, Francisco Reyes wrote: > > > Bruno Ducrot writes: > > > > > > >>http://public.natserv.net/acpidump.txt > > > > > > > >Well could you try to add this to your /boot/loader.conf: > > > >hw.acpi.osname="Microsoft Windows NT" > > > > > > Done > > > > > > > > > >It's because I want to check what happens if the following ASL is > > > >triggered: > > > > > > > >If (LEqual (SizeOf (\_OS), 0x14)) > > > >{ > > > > BPOL (0x3C) > > > >} > > > > > > Second dump on the same location... different name > > > http://public.natserv.net/acpidump2.txt > > > > > > >That's look like a workaround for Windows NT and that seems to > > > >be related to batteries and AC adapter. > > > > > > Not sure what was supposed to happen after trying the change in > > > loader.conf, but I tried "sysctl -a |grep acpi.bat" and the > > > results are the same as before. > > > > > > hw.acpi.battery.life: -1 > > > hw.acpi.battery.time: -1 > > > hw.acpi.battery.state: 7 > > > hw.acpi.battery.units: 1 > > > hw.acpi.battery.info_expire: 5 > > > > It was a stupid idea, sorry. I will look a little bit more. I > > think I begin to understand what's wrong, but I need to look a > > little bit further. > > > > I also CC to freebsd-acpi@ with a reply-to accordingly. > > > Few acpi BIOSes does not support _BST (battery status) method, causing > that type of weird sysctl output (since it depends solely on _BST). > Your hope is to use acpiconf(8) i.e acpiconf -i . > Unfortunately, acpiconf itself does not display all possible > values. > > Try this patch against usr.sbin/acpi/acpiconf/acpiconf.c > > http://people.freebsd.org/~ariff/acpi/acpiconf.c.diff > > Hopefully you will have the proper output in terms of percentage. > You won't have advance battery status such as remaining time and few > others. This is a limitation for BIOSes without _BST. There is a broken _BST in that AML. I think I can fix it directly onto the DSDT, or maybe I will use a little workaround which will use a SM Bus to access the battery. In fact I'm wondering if Windows use such smart battery stuff instead even though the SMBus is not visible from the AML (or I really don't see how it can work under that OS. Really). > I believe Nate Lawson is the right person to comment on this. Indeed. -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 4 18:15:04 2006 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 DB1FA16A41F for ; Wed, 4 Jan 2006 18:15:04 +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 B19DC43D58 for ; Wed, 4 Jan 2006 18:15:00 +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 5277747 for multiple; Wed, 04 Jan 2006 13:16:16 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k04IEnt9004383; Wed, 4 Jan 2006 13:14:49 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Wed, 4 Jan 2006 11:24:05 -0500 User-Agent: KMail/1.8.2 References: <43BBF457.3030506@jetnet.co.uk> In-Reply-To: <43BBF457.3030506@jetnet.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601041124.06427.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1229/Wed Jan 4 10:08:11 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Subject: Re: acpi on nVidia 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, 04 Jan 2006 18:15:05 -0000 On Wednesday 04 January 2006 11:14 am, David Reid wrote: > In my boot sequence I see these lines... > ACPI APIC Table: > ... > acpi0: on motherboard > acpi_bus_number: can't get _ADR > acpi_bus_number: can't get _ADR > acpi0: Power Button (fixed) > acpi_bus_number: can't get _ADR > acpi_bus_number: can't get _ADR > > ACPI seems to be working so I'm assuming this isn't something to worry > about? Who's the best person to follow this up with? If it's working you can just ignore those messages. -- 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 Jan 4 19:03:49 2006 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 5AFB416A41F for ; Wed, 4 Jan 2006 19:03:49 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9CD943D53 for ; Wed, 4 Jan 2006 19:03:48 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A6E04.dip.t-dialin.net [84.154.110.4]) (authenticated bits=128) by tower.berklix.org (8.12.9p2/8.12.9) with ESMTP id k04J3jos041147; Wed, 4 Jan 2006 20:03:46 +0100 (CET) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id k04J3hg0022796; Wed, 4 Jan 2006 20:03:44 +0100 (CET) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost.jhs.private [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id k04Gv3wq007451; Wed, 4 Jan 2006 17:57:03 +0100 (CET) (envelope-from jhs@fire.jhs.private) Message-Id: <200601041657.k04Gv3wq007451@fire.jhs.private> To: Roger Marquis In-Reply-To: Message from Roger Marquis of "Wed, 04 Jan 2006 07:59:08 PST." <20060104075019.W36259@roble.com> Date: Wed, 04 Jan 2006 17:57:03 +0100 From: "Julian H. Stacey" Cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 boot floppies 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, 04 Jan 2006 19:03:49 -0000 Roger Marquis wrote: > Markus Trippelsdorf wrote: > > When I upgraded my old Celeron box a year ago, I had to buy a CDROM > > burner, so that I could burn the install CD for my new machine. Since > > than it is sitting idle in its slot. > > You could also have purchased a USB-CD-RW or USB-DVD-RW. > > The problem with floppies is their A) tendency to develop bad > sectors, and B) increasing rarity. The lines of code needed for a > boot floppy would be much better spent on other bootable media, > Flash, DVD, etc, all of which would have larger and more > appreciative audiences. A) Yes. B) No. Not `larger audience' unless one only counts developers & installers buying / using latest mboards, & excludes vast user base of running kit, eg very few if any of my ~20+ varied i386 arch. systems of all ages have BIOS support for USB boot. -- Julian Stacey. Consultant Unix Net & Sys. Eng., Munich. http://berklix.com Mail in Ascii, HTML=spam. Ihr Rauch = meine allergischen Kopfschmerzen. From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 4 23:15:37 2006 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 5B42316A41F for ; Wed, 4 Jan 2006 23:15:37 +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 7F4A443D62 for ; Wed, 4 Jan 2006 23:15:36 +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 <0ISL009SSCU7MUB0@osl1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Thu, 05 Jan 2006 00:20:31 +0100 (CET) Received: from kg-work.kg4.no ([80.203.66.1]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0ISL00BF8CQCZC90@osl1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Thu, 05 Jan 2006 00:18:12 +0100 (CET) Date: Thu, 05 Jan 2006 00:15:35 +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: <20060104075019.W36259@roble.com> To: freebsd-amd64@freebsd.org Message-id: <20060105001535.7d881d0a.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: <20060104120024.2556B16A420@hub.freebsd.org> <20060104075019.W36259@roble.com> Subject: Re: AMD64 boot floppies 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, 04 Jan 2006 23:15:37 -0000 On Wed, 04 Jan 2006 07:59:08 -0800 (PST) Roger Marquis wrote: > The problem with floppies is their A) tendency to develop bad > sectors, and B) increasing rarity. The lines of code needed for a A) Yes, but easily countered by fresh for,atting floppies everytime you use them. Not a problem. B) No, USB floppy drives are everywhere. Floppies themselves can be had in almost any store (here in Norway at least). There is another reason why you need a floppy drive around; most motherboards only supports BIOS updates from either - windows or - a floppy Heck, my newest mainboard even has a built-in bios update mechanism, but it wants to load files from the internal floppy, no way to choose device in that program. Luckily, it also supports update from dos floppy, which worked nicely with a usb floppy drive. -- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 5 19:50:37 2006 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 C9D0916A41F for ; Thu, 5 Jan 2006 19:50:37 +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 A4EB943D5A for ; Thu, 5 Jan 2006 19:50:31 +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 k05JoS7A012845; Thu, 5 Jan 2006 20:50:28 +0100 (CET) (envelope-from cracauer@schlepper.zs64.net) Received: (from cracauer@localhost) by schlepper.zs64.net (8.13.3/8.12.9/Submit) id k05JoSiM012844; Thu, 5 Jan 2006 14:50:28 -0500 (EST) (envelope-from cracauer) Date: Thu, 5 Jan 2006 14:50:28 -0500 From: Martin Cracauer To: Mikey Galum Message-ID: <20060105145028.A12446@cons.org> References: <20060104034056.45903.qmail@web54315.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20060104034056.45903.qmail@web54315.mail.yahoo.com>; from recompile2@yahoo.com on Tue, Jan 03, 2006 at 07:40:56PM -0800 Cc: freebsd-amd64@freebsd.org Subject: Re: recom for newegg amd64 box? 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, 05 Jan 2006 19:50:38 -0000 Mikey Galum wrote on Tue, Jan 03, 2006 at 07:40:56PM -0800: > If I study > http://www.freebsd.org/platforms/amd64/motherboards.html, > pick a motherboard that appears to be supported and > then try to > locate a manufacturer that has a prebuilt system with > that mobo, > or a motherboard bundle, I run into problems. Newegg > doesn't have > this or that exact motherboard, bla bla bla, mwave > stopped stocking > that the other week, blablabla. For 754 and 939 boards I have Asus K8V-X, Abit KV8-Pro, Asus A8N-E Premium, DFI SLI Infinity, Asus A8V-E SE and DFI SLI-DR. Hm, I need to ebay off some stuff. Anyway... The only board doing everything perfect is the K8V-X, but it has weaknesses with RAM. Everything means all devices work in FreeBSD-6.0 including temperature monitoring, and also does ECC RAM. However, not only does it lack dual-channel RAM support (being socket 754), it also seems to like to keep RAM frequency at or below 200 MHz, with two sticks defaulting to 166 MHz. Still nice, with a Newcastle 3400+ you can build a very nice system very cheap if you don't want to overclock. Obviously, it doesn't do dual-core. The board I like best is the DFI SLI-DR, the right board for a control freak. It doesn't do ECC RAM, though, and the slots arrangement is stupid, the PCIe x4 is blocked by most oversized CPU HSFs and it only has 2 PCI slots. The A8V-E SE is nice but challenged in the I/O department. Of the above it is the only board that does 4 GB RAM with ECC support and correct remapping of the I/O space to above 4 GB. The SLI Infinity has the best potential being cheap, having many slots, supports ECC (well, in theory) and decent control options. Right now it is BIOS-challenged, though. Not sure whether I want to wait for DFI to come around, since it's not their top board I doubt they polish up the BIOS to a sufficient level. > Can someone recommend a simple reliable amd64 > motherboard that's > readily available as a bundle or even a prebuilt > system? Monarchcomputers is doing pre-tested mainboard/CPU/RAM/hsf combos. > I would have hoped something like an asus A8N32-sli > dlx with Why in the world would you dump the money not only on a SLI board but on the N32? Even under Windows games that is useless. My A8N-E premium does not correctly remap the I/O space above 3 GB. So not a good choice for 4 GB RAM. Nice board otherwise, but lacks BIOS control. > athlon 64x2 3800+ 2x512MB RAM, etc would be nice but I > haven't > been able to learn if this is supported. Of course it is. I would get 2 GB of RAM, though, the G.Skill HZ kit is nice and cheap. I would recommend a dual-core socket 939 Opteron instead of the X2, though. If you ever want to overclock (don't send us bug reports while doing it, though) it'll likely do much better. The bigger cache is almost useless, though. I have a huge bunch of random notes from my board testing and unfinished writeups, I guess I could dump them somewhere. Let me know if you want that. 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 Thu Jan 5 19:59:31 2006 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 1CA5316A420 for ; Thu, 5 Jan 2006 19:59:31 +0000 (GMT) (envelope-from pfgshield-freebsd@yahoo.com) Received: from web32909.mail.mud.yahoo.com (web32909.mail.mud.yahoo.com [68.142.206.56]) by mx1.FreeBSD.org (Postfix) with SMTP id 6F3C343D75 for ; Thu, 5 Jan 2006 19:58:49 +0000 (GMT) (envelope-from pfgshield-freebsd@yahoo.com) Received: (qmail 88206 invoked by uid 60001); 5 Jan 2006 19:58:42 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=t/vPilhGwqrJFW5wALINve+Z+FWkZEOqv7rKSdhS1CBezdgwpYpLyx0oYJTXW7m8O7/QoqMcjsU33mDZyn7oTM0ph3CtWOzFby3WAzuNfzdD3I42oeMS0luO8U513Jz+HPjBMs+ObYN4rWmOw4aXcj2OqThfr4aDI1JTYG9p6aU= ; Message-ID: <20060105195842.88204.qmail@web32909.mail.mud.yahoo.com> Received: from [69.79.142.173] by web32909.mail.mud.yahoo.com via HTTP; Thu, 05 Jan 2006 20:58:42 CET Date: Thu, 5 Jan 2006 20:58:42 +0100 (CET) From: To: freebsd-amd64@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Cc: Subject: Splash screen / SVR4 emulation?? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pfgshield-freebsd@yahoo.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 19:59:31 -0000 Hi; I've been happily running FreeBSD-amd64, and while some stuff from the ports tree still need work and not even OSS supports my sound harware, in general, it's really nice to use. While it has been discussed here that VESA doesn't work, it would still be nice to be able to load simple VGA splash screens, I tried but the module didn't load (in fact there is no module). Maybe I had something wrong, has anyone done it? BTW, for those interested in KGI, it doesn't build yet due to 64bit issues :(. Another thing is that I've been trying to do some updates and testing with the SVR4 compat module but it looks like it's never been considered for amd64. With a couple OpenSolaris live filesystem distributions out there now available it would be a nice thing to have. cheers, Pedro. Chiacchiera con i tuoi amici in tempo reale! http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 6 07:02:11 2006 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 51CF216A41F for ; Fri, 6 Jan 2006 07:02:11 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8A7843D46 for ; Fri, 6 Jan 2006 07:02:10 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (unknown [200.46.204.144]) by hub.org (Postfix) with ESMTP id D5D1E62C8AA for ; Fri, 6 Jan 2006 03:02:09 -0400 (AST) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 41428-01 for ; Fri, 6 Jan 2006 03:02:09 -0400 (AST) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id 700A862C862 for ; Fri, 6 Jan 2006 03:02:09 -0400 (AST) Received: by ganymede.hub.org (Postfix, from userid 1000) id 532A33A929; Fri, 6 Jan 2006 03:02:08 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 0A90C39D6F for ; Fri, 6 Jan 2006 03:02:08 -0400 (AST) Date: Fri, 6 Jan 2006 03:02:07 -0400 (AST) From: "Marc G. Fournier" To: freebsd-amd64@freebsd.org Message-ID: <20060106025853.L1088@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Subject: Migrating from FreeBSD 4/i386 to FreeBSD 6/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: Fri, 06 Jan 2006 07:02:11 -0000 I just picked up our first 64Bit server ... HP DL360 ... planning on running FreeBSD 6.x on it, overdue to move away from FreeBSD 4 ... The question is ... will a jail environment from a FreeBSD 4.x i386 machine work on this new box, or will I have to rebuild each one that I wish to move over? I realize that running it this way wouldn't be optimal, and it would be purely a temporary thing, but will/should it work? Thanks ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 6 17:20:04 2006 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 0311516A41F for ; Fri, 6 Jan 2006 17:20:04 +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 5BC4B43D48 for ; Fri, 6 Jan 2006 17:20:03 +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 k06HK3D1006234 for ; Fri, 6 Jan 2006 17:20:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k06HK3Q4006233; Fri, 6 Jan 2006 17:20:03 GMT (envelope-from gnats) Resent-Date: Fri, 6 Jan 2006 17:20:03 GMT Resent-Message-Id: <200601061720.k06HK3Q4006233@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, Don Brearley Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31DD116A41F for ; Fri, 6 Jan 2006 17:12:16 +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 E606A43D45 for ; Fri, 6 Jan 2006 17:12:15 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id k06HCFBY088972 for ; Fri, 6 Jan 2006 17:12:15 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id k06HCF88088971; Fri, 6 Jan 2006 17:12:15 GMT (envelope-from nobody) Message-Id: <200601061712.k06HCF88088971@www.freebsd.org> Date: Fri, 6 Jan 2006 17:12:15 GMT From: Don Brearley To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/91405: Kernel panic caused by asr on 6.0-amd64 box 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, 06 Jan 2006 17:20:04 -0000 >Number: 91405 >Category: amd64 >Synopsis: Kernel panic caused by asr on 6.0-amd64 box >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jan 06 17:20:02 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Don Brearley >Release: 6.0-STABLE #4 >Organization: Hibbing Community College >Environment: FreeBSD hcc.hibbing.edu 6.0-STABLE FreeBSD 6.0-STABLE #4: Thu Jan 5 16:01:00 CST 2006 root@hcc.hibbing.edu:/usr/src/sys/amd64/compile/HCC amd64 >Description: I have a Tyan Thunder S2895 (K8WE) motherboard in which I am trying to use an Adaptec 2400A ATA-RAID Card (AAR-2400A). I have dual Opteron 246 CPU's with 2GB of RAM. I am using a USB keyboard. The problem is that I cannot boot the box with the Adaptec Card installed with ACPI-enabled. When I have ACPI enabled, the card is detected and then the kernel panic's with: kernel trap 12: page fault in kernel mode, and then reboots. When I have ACPI disabled, the box boots up just fine but the Adaptec card is not detected. I am enabling/disabling ACPI through hint.acpi.0.disable in /boot/loader.conf and/or choosing option #1 or #2 in the boot menu. When I boot the box without the card, in ACPI mode, everything works fine. The problem persists in either SMP or non-SMP environments. The problem persists with multiple Adaptec 2400A cards. I've tried two others and both get errors. I've tried using different PCI slots, and that also did not correct the problem. >How-To-Repeat: Get a Tyan S2895 board and an Adaptec ATA-RAID 2400 card. Install 6.0-release and try to boot with ACPI-enabled. >Fix: None. You can boot the machine by disabling ACPI, but you will not be able to use the Adaptec card, so you may as well just remove the card and use ACPI. Please feel free to contact me for further details. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Fri Jan 6 18:33:09 2006 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 6F2E716A423 for ; Fri, 6 Jan 2006 18:33:09 +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 9A92143D5E for ; Fri, 6 Jan 2006 18:33:08 +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 k06IX7bG043313; Fri, 6 Jan 2006 19:33:07 +0100 (CET) (envelope-from cracauer@schlepper.zs64.net) Received: (from cracauer@localhost) by schlepper.zs64.net (8.13.3/8.12.9/Submit) id k06IX68Q043312; Fri, 6 Jan 2006 13:33:07 -0500 (EST) (envelope-from cracauer) Date: Fri, 6 Jan 2006 13:33:06 -0500 From: Martin Cracauer To: Scott Long Message-ID: <20060106133306.A43139@cons.org> References: <200512301245.57820.andrea@brancatelli.it> <20051230130529.GK52756@ip.net.ua> <200512300834.51959.jhb@freebsd.org> <20060103040049.GA54882@dragon.NUXI.org> <20060103130320.GA691@bsd.trippelsdorf.de> <43BA9E3F.50505@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <43BA9E3F.50505@samsco.org>; from scottl@samsco.org on Tue, Jan 03, 2006 at 08:54:39AM -0700 Cc: freebsd-amd64@freebsd.org, Markus Trippelsdorf Subject: Re: AMD64 boot floppies 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, 06 Jan 2006 18:33:09 -0000 Scott Long wrote on Tue, Jan 03, 2006 at 08:54:39AM -0700: > Markus Trippelsdorf wrote: > > > On Mon, Jan 02, 2006 at 08:00:49PM -0800, David O'Brien wrote: > > > >>On Fri, Dec 30, 2005 at 08:34:50AM -0500, John Baldwin wrote: > >> > >>>On Friday 30 December 2005 08:05 am, Ruslan Ermilov wrote: > >>> > >>>>On Fri, Dec 30, 2005 at 12:45:57PM +0100, Andrea Brancatelli wrote: > >>>> > >>>>>For i386 we have > >>>>>ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/6.0-RELEASE/floppies/ > >>>>>but for Amd64 there's no > >>>>>ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/6.0-RELEASE/floppies/ > >>>>> > >>>>>How can I get installation floppies for 6.0 / amd64? > >>>> > >>>>http://www.freebsd.org/releases/6.0R/installation-amd64.html#FLOPPIES > >>> > >>>FYI, it would be trivial to support with the splitfs stuff now. You'd > >>>basically just need to copy over the variables from i386 to set the > >>>sizes, etc. > >> > >>please, Please, PLEASE no... why add the pain of floppies to the release > >>mix when no one in their right mind as an AMD64 machine that has a floppy > >>drive AND doesn't have a CDROM (or DVD) drive. > > > > > > But I guess, the are many AMD64 machines that don't have a CDROM- or > > DVD- burner build in. For these machines a few floppy images to start a > > network installation would be helpful. > > > > My impression was the floppy drives are disappearing from servers faster > than CDROM drives are. For my new Supermicro board they only deliver BIOS updates in a floppy kit. At least SM seems to be committed to some floppability in the near future. For the rackmounts we have in the office there is neither floppy nor CD-ROM. Oh well. 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 Sat Jan 7 01:47:24 2006 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 273A216A41F for ; Sat, 7 Jan 2006 01:47:24 +0000 (GMT) (envelope-from dpz@ack.berkeley.edu) Received: from malcolm.berkeley.edu (malcolm.Berkeley.EDU [128.32.206.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id B987D43D45 for ; Sat, 7 Jan 2006 01:47:23 +0000 (GMT) (envelope-from dpz@ack.berkeley.edu) Received: from [166.172.128.50] (mobile-166-172-050-128.mycingular.net [166.172.128.50] (may be forged)) (authenticated bits=0) by malcolm.berkeley.edu (8.13.3/8.13.3) with ESMTP id k071l7RQ074237 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Fri, 6 Jan 2006 17:47:17 -0800 (PST) (envelope-from dpz@ack.berkeley.edu) Mime-Version: 1.0 (Apple Message framework v623) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-amd64@freebsd.org From: David Paul Zimmerman Date: Fri, 6 Jan 2006 17:46:56 -0800 X-Mailer: Apple Mail (2.623) X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (malcolm.berkeley.edu [128.32.206.239]); Fri, 06 Jan 2006 17:47:23 -0800 (PST) Subject: Sun X4100 LSI1064 support 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, 07 Jan 2006 01:47:24 -0000 Hi, all. We recently purchased a Sun X4100, which has the built-in LSI1064 SAS adapter. So far a lot of stuff seems to work: - autoboots the amd64 6.0-RELEASE disc1 CD - USB keyboard and VGA monitor connected to the back work great - gets all the way to the FreeBSD setup menu but it can't actually start the installation because it doesn't see either of the two Fujitsu 73GB SAS drives. I've got an external USB hard drive on order now, but that's just a temporary measure to mess around with the thing. Does anyone know of any efforts underway for LSI1064 support? If it's of any interest to anyone, here's a screenscrape of the device probing during boot. (Pardon the dust, the method of capturing this was kind of unnatural.) Note pci2. 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 ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 248 (2193.77-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20f51 Stepping = 1 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800,LM,3DNow+,3DNow> real memory = 1073676288 (1023 MB) evaavail memory = 1021034496 (973 MB)ris Operating Environment versions 8 and 9, and EMADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboardSun Java Enterprise System 2005Q1 Inioapic2 irqs 28-31 on motherboardct documentation. ioapic3 irqs 32-35 on motherboard ioapic4 irqs 36-39 on motherboard acpi0: on motherboard acpi0: Power Button (fixed)set /SYS (y/n)? yease wait. pci_link0: irq 11 on acpi0opped. pci_link1: irq 9 on acpi0 pci_link2: irq 10 on acpi0 pci_link3: irq 11 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 cpu0: on acpi0start /SP/console (y/n)? y acpi_throttle0: on cpu0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 em0: port 0x9c00-0x9c3f mem 0xfbfe0000-0xfbffffff irq 26 at device 1.0 on pci1 em0: Ethernet address: 00:14:4f:01:a4:94 em0: Speed:N/A Duplex:N/A em1: port 0x9800-0x983f mem 0xfbfc0000-0xfbfdffff irq 27 at device 1.1 on pci1 em1: Ethernet address: 00:14:4f:01:a4:95 em1: Speed:N/A Duplex:N/A em2: port 0x9400-0x943f mem 0xfbfa0000-0xfbfbffff irq 24 at device 2.0 on pci1 em2: Ethernet address: 00:14:4f:01:a4:96 em2: Speed:N/A Duplex:N/A em3: port 0x9000-0x903f mem 0xfbf80000-0xfbf9ffff irq 25 at device 2.1 on pci1 em3: Ethernet address: 00:14:4f:01:a4:97 em3: Speed:N/A Duplex:N/A pci0: at device 1.1 (no driver attached) pcib2: at device 2.0 on pci0 pci2: on pcib2 pci2: at device 3.0 (no driver attached) pci0: at device 2.1 (no driver attached) pcib3: at device 6.0 on pci0 pci3: on pcib3 ohci0: mem 0xfe3fe000-0xfe3fefff irq 19 at device 0.0 on pci3 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: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfe3fd000-0xfe3fdfff irq 19 at device 0.1 on pci3 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: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered pci3: at device 3.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 7.2 (no driver attached) pci0: at device 7.3 (no driver attached) pcib4: on acpi0 pci4: on pcib4 pcib5: at device 1.0 on pci4 pci5: on pcib5 pci4: at device 1.1 (no driver attached) pcib6: at device 2.0 on pci4 pci6: on pcib6 pci4: at device 2.1 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console orm0: at iomem 0xc0000-0xc9fff,0xca000-0xcafff,0xcb000-0xcbfff,0xcc000 -0xccfff,0xcd000-0xcdfff,0xce000-0xd27ff,0xd2800-0xd37ff on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ukbd0: American Megatrends Inc. Virtual Keyboard and Mouse, rev 1.10/1.00, addr 2, iclass 3/1 kbd0 at ukbd0 ums0: American Megatrends Inc. Virtual Keyboard and Mouse, rev 1.10/1.00, addr 2, iclass 3/1 ums0: X report 0x0002 not supported device_attach: ums0 attach returned 6 umass0: American Megatrends Inc. Virtual Cdrom Device, rev 1.10/1.00, addr 2 umass1: American Megatrends Inc. Virtual Floppy Device, rev 1.10/1.00, addr 3 Timecounter "TSC" frequency 2193768290 Hz quality 800 Timecounters tick every 1.000 msec md0: Preloaded image 4194304 bytes at 0xffffffff80970f68 acd0: DVDROM at ata0-master UDMA33 cd0 at umass-sim0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 1.000MB/s transfers cd0: Attempt to query device size failed: UNIT ATTENTION, Not ready to ready change, medium may have changed da0 at umass-sim1 bus 1 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: UNIT ATTENTION, Not ready to ready change, (da0:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim1:1:0:0): CAM Status: SCSI Status Error (da0:umass-sim1:1:0:0): SCSI Status: Check Condition (da0:umass-sim1:1:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim1:1:0:0): Not ready to ready change, medium may have changed (da0:umass-sim1:1:0:0): Retrying Command (per Sense Data) (da0:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim1:1:0:0): CAM Status: SCSI Status Error (da0:umass-sim1:1:0:0): SCSI Status: Check Condition (da0:umass-sim1:1:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim1:1:0:0): Not ready to ready change, medium may have changed (da0:umass-sim1:1:0:0): Retrying Command (per Sense Data) (da0:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim1:1:0:0): CAM Status: SCSI Status Error (da0:umass-sim1:1:0:0): SCSI Status: Check Condition (da0:umass-sim1:1:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim1:1:0:0): Not ready to ready change, medium may have changed (da0:umass-sim1:1:0:0): Retrying Command (per Sense Data) (da0:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim1:1:0:0): CAM Status: SCSI Status Error (da0:umass-sim1:1:0:0): SCSI Status: Check Condition (da0:umass-sim1:1:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim1:1:0:0): Not ready to ready change, medium may have changed (da0:umass-sim1:1:0:0): Retrying Command (per Sense Data) (da0:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim1:1:0:0): CAM Status: SCSI Status Error (da0:umass-sim1:1:0:0): SCSI Status: Check Condition (da0:umass-sim1:1:0:0): NOT READY asc:3a,0 (da0:umass-sim1:1:0:0): Medium not present (da0:umass-sim1:1:0:0): Unretryable error Opened disk da0 -> 6 (da0:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim1:1:0:0): CAM Status: SCSI Status Error (da0:umass-sim1:1:0:0): SCSI Status: Check Condition (da0:umass-sim1:1:0:0): NOT READY asc:3a,0 (da0:umass-sim1:1:0:0): Medium not present (da0:umass-sim1:1:0:0): Unretryable error Opened disk da0 -> 6 (da0:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim1:1:0:0): CAM Status: SCSI Status Error (da0:umass-sim1:1:0:0): SCSI Status: Check Condition (da0:umass-sim1:1:0:0): NOT READY asc:3a,0 (da0:umass-sim1:1:0:0): Medium not present (da0:umass-sim1:1:0:0): Unretryable error Opened disk da0 -> 6 Trying to mount root from ufs:/dev/md0 From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 7 03:40:10 2006 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 2F32B16A4A3; Sat, 7 Jan 2006 03:40:10 +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 93A0E43D46; Sat, 7 Jan 2006 03:40:09 +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 k073e7aD081614; Fri, 6 Jan 2006 22:40:07 -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 k073e8kt016184; Fri, 6 Jan 2006 22:40:08 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 19E0D7302F; Fri, 6 Jan 2006 22:40:08 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20060107034008.19E0D7302F@freebsd-current.sentex.ca> Date: Fri, 6 Jan 2006 22:40:08 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner4 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: Sat, 07 Jan 2006 03:40:10 -0000 TB --- 2006-01-07 01:53:06 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-01-07 01:53:06 - starting HEAD tinderbox run for amd64/amd64 TB --- 2006-01-07 01:53:06 - cleaning the object tree TB --- 2006-01-07 01:53:40 - checking out the source tree TB --- 2006-01-07 01:53:40 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2006-01-07 01:53:40 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-01-07 01:59:39 - building world (CFLAGS=-O2 -pipe) TB --- 2006-01-07 01:59:39 - cd /src TB --- 2006-01-07 01:59:39 - /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 --- 2006-01-07 03:31:16 - generating LINT kernel config TB --- 2006-01-07 03:31:16 - cd /src/sys/amd64/conf TB --- 2006-01-07 03:31:16 - /usr/bin/make -B LINT TB --- 2006-01-07 03:31:16 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2006-01-07 03:31:16 - cd /src TB --- 2006-01-07 03:31:16 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Jan 7 03:31:16 UTC 2006 >>> 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/kern/kern_malloc.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/kern/kern_mbuf.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/kern/kern_mib.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/kern/kern_module.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/kern/kern_mtxpool.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/kern/kern_mutex.c /src/sys/kern/kern_mutex.c: In function `mtx_destroy': /src/sys/kern/kern_mutex.c:887: error: structure has no member named `lo_class' *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-01-07 03:40:07 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-01-07 03:40:07 - ERROR: failed to build lint kernel TB --- 2006-01-07 03:40:07 - tinderbox aborted TB --- 1.29 user 6.80 system 6421.50 real From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 7 15:11:33 2006 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 E7BF116A41F for ; Sat, 7 Jan 2006 15:11:33 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (p65-147.acedsl.com [66.114.65.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B74943D45 for ; Sat, 7 Jan 2006 15:11:33 +0000 (GMT) (envelope-from lists@stringsutils.com) Received: from zoraida.natserv.net (zoraida.natserv.net [66.114.65.147]) by zoraida.natserv.net (Postfix) with ESMTP id B38BE7E86; Sat, 7 Jan 2006 10:11:32 -0500 (EST) References: <200512301245.57820.andrea@brancatelli.it> <20051230130529.GK52756@ip.net.ua> <200512300834.51959.jhb@freebsd.org> <20060103040049.GA54882@dragon.NUXI.org> <20060103130320.GA691@bsd.trippelsdorf.de> <43BA9E3F.50505@samsco.org> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: Scott Long Date: Sat, 07 Jan 2006 10:11:32 -0500 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org, Markus Trippelsdorf Subject: Re: AMD64 boot floppies 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, 07 Jan 2006 15:11:34 -0000 Scott Long writes: > My impression was the floppy drives are disappearing from servers faster > than CDROM drives are. I used to think floppies were no longer needed... and that all I needed was a CD ROM until I discovered sysinstall needs a floppy to install drivers (KLDs I think). Although the problem I had was with a i386 installation, the same would have happened if it had been the AMD64 CDs. It turns out the hardware, 3Ware 9550SX, is now supported in the tree.. but the code was put in the tree after release.. and after the latest snapshot at the FreeBSD site. And yes... I know that this is not directly related to... having boot floppies.. just trying to point out that floppies still are usefull in some cases... and that as long as the OS still FORCES you to use floppies in some cases, people will continue to have them. (unless I am totally missing a way to load KLDs from CDs/USB keys but sysinstall surely seems to only support floppies). From owner-freebsd-amd64@FreeBSD.ORG Sat Jan 7 16:20:13 2006 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 1295516A41F for ; Sat, 7 Jan 2006 16:20:13 +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 ECD0843D68 for ; Sat, 7 Jan 2006 16:20:06 +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 k07GK6Ju095053 for ; Sat, 7 Jan 2006 16:20:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k07GK6Ba095052; Sat, 7 Jan 2006 16:20:06 GMT (envelope-from gnats) Date: Sat, 7 Jan 2006 16:20:06 GMT Message-Id: <200601071620.k07GK6Ba095052@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Scott Long Cc: Subject: Re: amd64/91405: Kernel panic caused by asr on 6.0-amd64 box X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Scott Long List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 16:20:13 -0000 The following reply was made to PR amd64/91405; it has been noted by GNATS. From: Scott Long To: Don Brearley Cc: freebsd-gnats-submit@freebsd.org Subject: Re: amd64/91405: Kernel panic caused by asr on 6.0-amd64 box Date: Sat, 07 Jan 2006 09:14:57 -0700 Don Brearley wrote: >>Number: 91405 >>Category: amd64 >>Synopsis: Kernel panic caused by asr on 6.0-amd64 box >>Confidential: no >>Severity: serious >>Priority: high >>Responsible: freebsd-amd64 >>State: open >>Quarter: >>Keywords: >>Date-Required: >>Class: sw-bug >>Submitter-Id: current-users >>Arrival-Date: Fri Jan 06 17:20:02 GMT 2006 >>Closed-Date: >>Last-Modified: >>Originator: Don Brearley >>Release: 6.0-STABLE #4 >>Organization: > > Hibbing Community College > >>Environment: > > FreeBSD hcc.hibbing.edu 6.0-STABLE FreeBSD 6.0-STABLE #4: Thu Jan 5 16:01:00 CST > 2006 root@hcc.hibbing.edu:/usr/src/sys/amd64/compile/HCC amd64 > >>Description: > > I have a Tyan Thunder S2895 (K8WE) motherboard in which I am trying to use > an Adaptec 2400A ATA-RAID Card (AAR-2400A). I have dual Opteron 246 CPU's > with 2GB of RAM. I am using a USB keyboard. > > The problem is that I cannot boot the box with the Adaptec Card installed > with ACPI-enabled. > > When I have ACPI enabled, the card is detected and then the kernel panic's > with: kernel trap 12: page fault in kernel mode, and then reboots. > > When I have ACPI disabled, the box boots up just fine but the Adaptec card > is not detected. > > I am enabling/disabling ACPI through hint.acpi.0.disable in /boot/loader.conf > and/or choosing option #1 or #2 in the boot menu. > > When I boot the box without the card, in ACPI mode, everything works fine. > > The problem persists in either SMP or non-SMP environments. > > The problem persists with multiple Adaptec 2400A cards. I've tried two others > and both get errors. I've tried using different PCI slots, and that also > did not correct the problem. > > > > >>How-To-Repeat: > > > Get a Tyan S2895 board and an Adaptec ATA-RAID 2400 card. Install 6.0-release > and try to boot with ACPI-enabled. > > > >>Fix: > > > None. You can boot the machine by disabling ACPI, but you will not be able > to use the Adaptec card, so you may as well just remove the card and use ACPI. > > Please feel free to contact me for further details. > >>Release-Note: >>Audit-Trail: >>Unformatted: > The ASR driver will absolutely not work on amd64 due to not being 64bit clean. Fixing the driver requires a significant amount of work.