From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 5 11:06:53 2007 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0EC3716A473 for ; Mon, 5 Nov 2007 11:06:53 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id F296A13C4BC for ; Mon, 5 Nov 2007 11:06:52 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id lA5B6q91026138 for ; Mon, 5 Nov 2007 11:06:52 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id lA5B6qtK026134 for freebsd-amd64@FreeBSD.org; Mon, 5 Nov 2007 11:06:52 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 5 Nov 2007 11:06:52 GMT Message-Id: <200711051106.lA5B6qtK026134@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org X-Mailman-Approved-At: Mon, 05 Nov 2007 12:40:09 +0000 Cc: Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org 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, 05 Nov 2007 11:06:53 -0000 Current FreeBSD problem reports Critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/112222 amd64 [libc] 32-bit libc incorrectly converts some FP number 1 problem total. Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdosfs locks up o amd64/74747 amd64 System panic on shutdown when process will not die o amd64/76136 amd64 system halts before reboot o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys o amd64/80691 amd64 amd64 kernel hangs on load o amd64/85451 amd64 [hang] 6.0-BETA3 lockups on AMD64 (PREEMPTION only) o amd64/86080 amd64 [radeon] [hang] radeon DRI causes system hang on amd64 o amd64/87258 amd64 [smp] [boot] cannot boot with SMP and Areca ARC-1160 r o amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in o amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6 o amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE o amd64/87977 amd64 [busdma] [panic] amd64 busdma dflt_lock called (by ata o amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not boot with usb o amd64/88790 amd64 kernel panic on first boot (after the FreeBSD installa o amd64/89501 amd64 System crashes on install using ftp on local subnet o amd64/89503 amd64 Cant Boot Installation Disk o amd64/89546 amd64 [geom] GEOM error o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 o amd64/91492 amd64 BTX halted o amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff o amd64/92889 amd64 [libc] xdr double buffer overflow o amd64/93961 amd64 [busdma] Problem in bounce buffer handling in sys/amd6 o amd64/94677 amd64 panic in amd64 install at non-root user creation o amd64/94989 amd64 BTX Halts on Sun Fire X2100 w/6.1-BETA4 (amd64) and 5. f amd64/95414 amd64 kernel crashes during install o amd64/95888 amd64 kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP DL140G o amd64/97075 amd64 Panic, Trap 12 o amd64/97337 amd64 [dri] xorg reboots system if dri module is enabled o amd64/102122 amd64 6.1-RELEASE amd64 Install Media panics on boot. s amd64/104311 amd64 ports/wine should be installable on amd64 f amd64/105514 amd64 FreeBSD/amd64 - Fails to boot on HP Pavilion dv8000 La o amd64/105531 amd64 [sata] gigabyte GA-M51GM-S2G / nVidia nForce 430 - doe o amd64/105629 amd64 [re] TrendNet TEG-BUSR 10/100/1000 disables itself on o amd64/106604 amd64 saslauthd crashes with signal 6 on FreeBSD 6.2-PREREL o amd64/106918 amd64 [re] Asus P5B with internal RealTek PCIe Ethernet gets o amd64/108861 amd64 [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work f amd64/109584 amd64 zdump doesn't work o amd64/110655 amd64 [threads] 32 bit threaded applications crash on amd64 o amd64/111955 amd64 [install] Install CD boot panic due to missing BIOS sm o amd64/111992 amd64 BTX failed - HP Laptop dv2315nr s gnu/112215 amd64 [patch] gcc(1): "gcc -m32" attempts to link against 64 o amd64/112677 amd64 [aac] Adaptec 4805SAS causes 6.2 (AMD64) to panic (amd f amd64/112828 amd64 Complete data loss after upgrade 6.1 -> 6.2 (Amd64) o amd64/113021 amd64 [re] ASUS M2A-VM onboard NIC does not work o amd64/114111 amd64 [nfs] System crashes while writing on NFS-mounted shar o amd64/115194 amd64 LCD screen remains blank after Dell XPS M1210 lid is c o amd64/115784 amd64 Compiling with -m32 breaks on FreeBSD/amd64 s amd64/115815 amd64 [sata] [request] Gigabyte GA-M61P-S3 Motherboard unsup o amd64/116159 amd64 Panic while debugging on CURRENT o amd64/116322 amd64 At start fsck on current, the system panics o amd64/116620 amd64 Ifconfig spins when creating carp(4) device on amd64/S o amd64/116977 amd64 FreeBSD/amd64 - Fails to boot on HP Pavilion dv9030ea o amd64/117296 amd64 [sata] I don`t see second SATA IDE on VIA VT8237A o amd64/117316 amd64 [acpi] ACPI lockups on SuperMicro motherboard o amd64/117418 amd64 FreeBSD 6.2 crash on amd64 4400+ 55 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/74608 amd64 [mpt] [hang] mpt hangs 5 minutes when booting s amd64/85273 amd64 FreeBSD (NetBSD or OpenBSD) not install on laptop Comp o amd64/88730 amd64 kernel panics during booting from the installation CD o amd64/91195 amd64 FreeBSD 6.0(amd64) and Asus A8R-MVP a amd64/93002 amd64 amd64 (6.0) coredumps at unpredictable times a amd64/93090 amd64 [nve] NIC on GA-K8NF-9 motherboard is recognized, but o amd64/97489 amd64 [ata] nForce 410 ATA controller dma time out (ASUS K8N o amd64/100326 amd64 [fdc] /dev/fd0 not created after installation FreeBSD o amd64/100838 amd64 [powerd] FreeBSD 6.0/6.1 kernel panics when booting wi f amd64/101132 amd64 [smp] Incorrect cpu idle and usage statistics in top a o amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV o amd64/103259 amd64 [ar] Cannot use ataraid on nvidia nForce4+amd64 o amd64/106186 amd64 [panic] panic in swap_pager_swap_init (amd64/smp/6.2-p f amd64/108345 amd64 6.2-* GENERIC will not boot Intel PD EMT64 w/ ACPI o amd64/110599 amd64 [geli] geli attach to gmirror device hangs and cannot o amd64/111096 amd64 motherboard ASRock AM2NF6G-VSTA not supported a amd64/113111 amd64 [Makefile] [patch] Potentially wrong instructions will o amd64/114270 amd64 [cpufreq] cpufreq doesnt work when compiled in to kern o amd64/115581 amd64 [patch] -mfancy-math-387 has no effect o amd64/116457 amd64 cant install freebsd on dv9420us o amd64/116514 amd64 freebsd6.2 can't detect GA-M61SME-S2's onboard lan car o amd64/116670 amd64 onboard SATA RAID1 controllers o amd64/116689 amd64 [request] support for MSI K9MM-V o amd64/116775 amd64 make distribution failed for sendmail o amd64/117186 amd64 kldload Unsupported file type on STABLE amd64 25 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 5 15:21:02 2007 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F10616A420 for ; Mon, 5 Nov 2007 15:21:02 +0000 (UTC) (envelope-from fbsdlists@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.241]) by mx1.freebsd.org (Postfix) with ESMTP id CAFDE13C480 for ; Mon, 5 Nov 2007 15:21:01 +0000 (UTC) (envelope-from fbsdlists@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so207825ana for ; Mon, 05 Nov 2007 07:20:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=z7n3+/JtRYVNmMJBNLvgtMA6lbr5aD2N6BYAYpSR2WY=; b=OpF8RYoe1oKzqyKSst9P3Aq93PVUfNQ1l09oKVljfsAUhoPhjV8ZqVWZj0ZTYnxaDitPr0D7K1w12FeA/6Q4z0NGftC/Dik0Rf1CrP3LGBEC6Q4ls8+qwbwCMX4gJFFb+oO6CSWPPRvO/4XS6YNdUsNJ8VNfpk1SX93Zd/wDNfU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JmFU05+3zT/fKDQU3vtgvmNK1tVUlRDtYyh9Voz1v4D8DFa3stz1Zzd8b1CXE1CAlmS7TIbm2PIsNQRDrTPgFCPfaxkFfuIvJXYa6erCMjjMVWh1qeQX0xB0WoVVFgJnMxOYpIelAZy5YqqAwH16f1CDwfedq2TAEa+fE+kOIM4= Received: by 10.142.242.8 with SMTP id p8mr978359wfh.1194274333584; Mon, 05 Nov 2007 06:52:13 -0800 (PST) Received: by 10.142.216.9 with HTTP; Mon, 5 Nov 2007 06:52:12 -0800 (PST) Message-ID: <54db43990711050652v1cf7a2e8ra1fcbdfe3e1a436e@mail.gmail.com> Date: Mon, 5 Nov 2007 09:52:12 -0500 From: "Bob Johnson" To: "John Baldwin" In-Reply-To: <200711011327.27953.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <6eb82e0711010634x5f70e974i78c505d8eda24223@mail.gmail.com> <200711011327.27953.jhb@freebsd.org> Cc: amd64@freebsd.org Subject: Re: panic: no BIOS SMAP info from loader 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, 05 Nov 2007 15:21:02 -0000 On 11/1/07, John Baldwin wrote: > On Thursday 01 November 2007 09:34:22 am Rong-en Fan wrote: > > I have a HP dc7000 box, booting with i386 is fine, but not > > amd64. It panics as soon as loader loads kernel. The console > > snapshot is at > > > > http://www.flickr.com/photos/rafan/1814155320/ > > > > under loader prompt, 'smap' shows nothing for both i386 > > and amd64. But i386 works well. I looked at archive, it > > seems there are several reports, but no solution. BTW, the boot > > cd I used is 7.0-BETA1.5. > > Does Linux find an SMAP? Right now FreeBSD/amd64 requires an SMAP. > My web searches on this indicated that when HP first introduced these systems, they had the same problem with Linux. HP provided a patch that allows recent Linux kernels to boot. Older i386 FreeBSDs also can not boot on my HP dc7700. So it appears someone has already fixed this for i386, but no one has moved it to AMD64. I don't remember which i386 versions work or don't work, but I can start booting install disks and find out. - Bob From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 5 16:48:19 2007 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE1AA16A481 for ; Mon, 5 Nov 2007 16:48:18 +0000 (UTC) (envelope-from fbsdlists@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.225]) by mx1.freebsd.org (Postfix) with ESMTP id 842BA13C481 for ; Mon, 5 Nov 2007 16:48:18 +0000 (UTC) (envelope-from fbsdlists@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so977547nzf for ; Mon, 05 Nov 2007 08:48:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=3ys5bvmanQUYuCdsWd4HknfRLvyiCXv/n4hS+oRs1ag=; b=VHEWqDpo6xC4A0I2L/JEDA3xmx0Ti6DTuCysVNsmoNRj7ThiN2y15UnOtZgdIcTcbhAi+UH8toycYqD6D8/1y+ktPTqAaictTeNSanpHJw/6t4bbw3aZ/cyiNu1cbmWCZd/Wt6vcFWVfptDZc4nykVQ6r3MfvLnnEAkqxB/dhV8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ATw+yLKsQ1ZaBGVcYeOmL7OXxvK0mFom275jndfe6TQPxuhi8ILWjwHzrpX4dUzuU0vOxMhkNK3eFLThGkkEV8m8scT6j9vyphXA8+rd2wHQOjRaRdCgBqCEBag+d8BnOLNyReh1b7SRYHCvIh/bXtmcFw+3K5OFSoh/M9ylAOQ= Received: by 10.143.8.10 with SMTP id l10mr1077657wfi.1194281287369; Mon, 05 Nov 2007 08:48:07 -0800 (PST) Received: by 10.142.216.9 with HTTP; Mon, 5 Nov 2007 08:48:07 -0800 (PST) Message-ID: <54db43990711050848i67b54bfbuc290414e6f4847f7@mail.gmail.com> Date: Mon, 5 Nov 2007 11:48:07 -0500 From: "Bob Johnson" To: "John Baldwin" In-Reply-To: <54db43990711050652v1cf7a2e8ra1fcbdfe3e1a436e@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <6eb82e0711010634x5f70e974i78c505d8eda24223@mail.gmail.com> <200711011327.27953.jhb@freebsd.org> <54db43990711050652v1cf7a2e8ra1fcbdfe3e1a436e@mail.gmail.com> Cc: amd64@freebsd.org Subject: Re: panic: no BIOS SMAP info from loader 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, 05 Nov 2007 16:48:19 -0000 On 11/5/07, Bob Johnson wrote: > My web searches on this indicated that when HP first introduced these > systems, they had the same problem with Linux. HP provided a patch > that allows recent Linux kernels to boot. Older i386 FreeBSDs also can > not boot on my HP dc7700. So it appears someone has already fixed this > for i386, but no one has moved it to AMD64. > > I don't remember which i386 versions work or don't work, but I can > start booting install disks and find out. Hmmm. Maybe I should retract that. I cannot find an i386 install CD that won't boot on it. I've tried 7.0-BETA1, 6.2-STABLEsnap200708, 6.2-RC1, 6.1-RELEASE, 6.0-BETA2, 6.0-BETA1, 5.3-RC1 (hangs probing ATA1), 4.5-RELEASE, and 4.3-RELEASE. But I thought I remembered being unable to boot some i386 install CDs in it. - Bob From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 5 20:02:35 2007 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED83D16A417 for ; Mon, 5 Nov 2007 20:02:35 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id 8EDFF13C48D for ; Mon, 5 Nov 2007 20:02:35 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8p) with ESMTP id 217859821-1834499 for multiple; Mon, 05 Nov 2007 15:02:15 -0500 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id lA5K1nwH063643; Mon, 5 Nov 2007 15:01:50 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Bob Johnson" Date: Mon, 5 Nov 2007 14:15:53 -0500 User-Agent: KMail/1.9.6 References: <6eb82e0711010634x5f70e974i78c505d8eda24223@mail.gmail.com> <54db43990711050652v1cf7a2e8ra1fcbdfe3e1a436e@mail.gmail.com> <54db43990711050848i67b54bfbuc290414e6f4847f7@mail.gmail.com> In-Reply-To: <54db43990711050848i67b54bfbuc290414e6f4847f7@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200711051415.53489.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Mon, 05 Nov 2007 15:01:50 -0500 (EST) X-Virus-Scanned: ClamAV 0.91.2/4675/Mon Nov 5 11:20:43 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: amd64@freebsd.org Subject: Re: panic: no BIOS SMAP info from loader 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, 05 Nov 2007 20:02:36 -0000 On Monday 05 November 2007 11:48:07 am Bob Johnson wrote: > On 11/5/07, Bob Johnson wrote: > > > My web searches on this indicated that when HP first introduced these > > systems, they had the same problem with Linux. HP provided a patch > > that allows recent Linux kernels to boot. Older i386 FreeBSDs also can > > not boot on my HP dc7700. So it appears someone has already fixed this > > for i386, but no one has moved it to AMD64. > > > > I don't remember which i386 versions work or don't work, but I can > > start booting install disks and find out. > > Hmmm. Maybe I should retract that. I cannot find an i386 install CD > that won't boot on it. I've tried 7.0-BETA1, 6.2-STABLEsnap200708, > 6.2-RC1, 6.1-RELEASE, 6.0-BETA2, 6.0-BETA1, 5.3-RC1 (hangs probing > ATA1), 4.5-RELEASE, and 4.3-RELEASE. But I thought I remembered being > unable to boot some i386 install CDs in it. Without an SMAP, FreeBSD/i386 is only going to find about 64M of RAM on the box though. Do you know what the patch was that HP provided for Linux? I wasn't able to find it. If you disable ACPI is FreeBSD/i386 able to see all of the RAM in the box? -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 5 20:26:04 2007 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2EBA116A421; Mon, 5 Nov 2007 20:26:04 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from angel.ticketswitch.com (angel.ticketswitch.com [IPv6:2002:57e0:1d4e::1]) by mx1.freebsd.org (Postfix) with ESMTP id DC47C13C4B6; Mon, 5 Nov 2007 20:26:03 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from smaug.rattatosk ([10.50.50.2]) by angel.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67 (FreeBSD)) (envelope-from ) id 1Ip8WJ-0001XJ-8e; Mon, 05 Nov 2007 20:26:03 +0000 Received: from dilbert.rattatosk ([10.50.50.6] helo=dilbert.ticketswitch.com) by smaug.rattatosk with esmtp (Exim 4.67 (FreeBSD)) (envelope-from ) id 1Ip8WJ-0009b2-6e; Mon, 05 Nov 2007 20:26:03 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Ip8WJ-0008M0-71; Mon, 05 Nov 2007 20:26:03 +0000 To: fbsdlists@gmail.com, jhb@freebsd.org In-Reply-To: <200711051415.53489.jhb@freebsd.org> Message-Id: From: Pete French Date: Mon, 05 Nov 2007 20:26:03 +0000 Cc: amd64@freebsd.org Subject: Re: panic: no BIOS SMAP info from loader 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, 05 Nov 2007 20:26:04 -0000 > Without an SMAP, FreeBSD/i386 is only going to find about 64M of RAM on the > box though. Do you know what the patch was that HP provided for Linux? I > wasn't able to find it. If you disable ACPI is FreeBSD/i386 able to see all > of the RAM in the box? I have an HP dc5750 which arrivd on my desk today and have spent the day wrestling with much the same problems as referred to here! Like you say, it only sees 64M of memory on boot, so you have to set hw.physmem in loader.conf to make it use the RAM. It will not boot with ACPI enabled at all either - has to boot ACPI disabled. Also it will noot boot amd64, not from the CD or from an install on the hard drive. That always fails with the error message described in the subject line. I am rather wishing I had waited before buying the machine and seen this thread, as the purpose was to have a test amd64 desktop :-( But... it here, and its running, and I have a lot of space to test various OS'es on it as required. Currently has 6.3-BETA for both i386 and amd64 installed (of which only one will bot obviously). cheers, -pete. From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 5 21:04:03 2007 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83D6A16A469 for ; Mon, 5 Nov 2007 21:04:03 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.freebsd.org (Postfix) with ESMTP id EFE8B13C49D for ; Mon, 5 Nov 2007 21:04:02 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1264539nfb for ; Mon, 05 Nov 2007 13:03:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=7AL60m+rv8Th3wjQJEr9lT4wwl+m/pg9/01s31Qdh5c=; b=haUGnaqFkQW/f5yL13Pj5cshKYhGXi4SiSdP1FKoMgcG24i/Zz0l+y8IKlyNpmsC/2WchSJ+TzgdDkzwuXM3GAya58wjsGwqBO4exorWgGfb9F7HjlPkVvFGrMBIjP5nLThlrWHMZ/W3PeGPX2cy0UgEaagC9VWHSLlFBXeKVjY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=HmHBTUJ1/5wuqo4fGn3K/n2t693qSohKDE2cSxJ/92LP/nxnlubAcoPsowOQgKpJiTFqpobFicpKJ0J60rgMyvxQdyh8Zq1wB/AEH+iX2qPWZ41SE2gYtAceWrtPyR7cZxJbk5skDcRAzkBOQh3At1RB/5bypmT0kRN7+jbmIzQ= Received: by 10.86.89.4 with SMTP id m4mr3720800fgb.1194295132152; Mon, 05 Nov 2007 12:38:52 -0800 (PST) Received: by 10.86.2.1 with HTTP; Mon, 5 Nov 2007 12:38:52 -0800 (PST) Message-ID: <499c70c0711051238o2463bbefx56856dfdb31f31cf@mail.gmail.com> Date: Mon, 5 Nov 2007 23:38:52 +0300 From: "Abdullah Ibn Hamad Al-Marri" To: "John Baldwin" In-Reply-To: <200711051415.53489.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <6eb82e0711010634x5f70e974i78c505d8eda24223@mail.gmail.com> <54db43990711050652v1cf7a2e8ra1fcbdfe3e1a436e@mail.gmail.com> <54db43990711050848i67b54bfbuc290414e6f4847f7@mail.gmail.com> <200711051415.53489.jhb@freebsd.org> Cc: amd64@freebsd.org Subject: Re: panic: no BIOS SMAP info from loader 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, 05 Nov 2007 21:04:03 -0000 On Nov 5, 2007 10:15 PM, John Baldwin wrote: > > On Monday 05 November 2007 11:48:07 am Bob Johnson wrote: > > On 11/5/07, Bob Johnson wrote: > > > > > My web searches on this indicated that when HP first introduced these > > > systems, they had the same problem with Linux. HP provided a patch > > > that allows recent Linux kernels to boot. Older i386 FreeBSDs also can > > > not boot on my HP dc7700. So it appears someone has already fixed this > > > for i386, but no one has moved it to AMD64. > > > > > > I don't remember which i386 versions work or don't work, but I can > > > start booting install disks and find out. > > > > Hmmm. Maybe I should retract that. I cannot find an i386 install CD > > that won't boot on it. I've tried 7.0-BETA1, 6.2-STABLEsnap200708, > > 6.2-RC1, 6.1-RELEASE, 6.0-BETA2, 6.0-BETA1, 5.3-RC1 (hangs probing > > ATA1), 4.5-RELEASE, and 4.3-RELEASE. But I thought I remembered being > > unable to boot some i386 install CDs in it. > > Without an SMAP, FreeBSD/i386 is only going to find about 64M of RAM on the > box though. Do you know what the patch was that HP provided for Linux? I > wasn't able to find it. If you disable ACPI is FreeBSD/i386 able to see all > of the RAM in the box? > > -- > John Baldwin John, This one? http://bugzilla.kernel.org/show_bug.cgi?id=8833 http://marc.info/?l=linux-kernel&m=118809338631160&w=2 -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 5 21:40:49 2007 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6680A16A41B for ; Mon, 5 Nov 2007 21:40:49 +0000 (UTC) (envelope-from fbsdlists@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.190]) by mx1.freebsd.org (Postfix) with ESMTP id 2B05B13C4A7 for ; Mon, 5 Nov 2007 21:40:48 +0000 (UTC) (envelope-from fbsdlists@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so1445069rvb for ; Mon, 05 Nov 2007 13:40:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=1YHZGyUhqJNr8XWfFcKHnBgQiRs7ADcJP+RM54Q42PA=; b=LYEiqUugOklnDKGZFMbPwHpYlmDl/pF5SabitzoXjDTjUV+ePWrqrOn810dzzBfI1LkjDtkIcHNXHdUIUmIzcDnPQmUwQgrWh5d8e9B5/aAZ6LbUTgT+vV8/yTv2BstafRU4Araox7+ntOyJdxZSxXthu7u4Shukd3wyZj8V+EY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Ws9yQt6WyTSABXIa/1tv1eeUjegYNRn4zfc2lJYcBBsfioPmp2iZo2Dm40ZxFQ7J2bIpxSuC4uqcuOvw7xdcchUZPS4VQ7j0Lzz8M6PKW+tPiHc7Fw82I4PC9BxX5k/oVutbuAZuImZX06LeVz0TrlIIHa0cdChMrMXiX19jhLg= Received: by 10.141.171.6 with SMTP id y6mr2645908rvo.1194298835293; Mon, 05 Nov 2007 13:40:35 -0800 (PST) Received: by 10.141.142.18 with HTTP; Mon, 5 Nov 2007 13:40:35 -0800 (PST) Message-ID: <54db43990711051340j727d43c6t6ee5aeb5a9342c8e@mail.gmail.com> Date: Mon, 5 Nov 2007 16:40:35 -0500 From: "Bob Johnson" To: "John Baldwin" In-Reply-To: <200711051415.53489.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <6eb82e0711010634x5f70e974i78c505d8eda24223@mail.gmail.com> <54db43990711050652v1cf7a2e8ra1fcbdfe3e1a436e@mail.gmail.com> <54db43990711050848i67b54bfbuc290414e6f4847f7@mail.gmail.com> <200711051415.53489.jhb@freebsd.org> Cc: amd64@freebsd.org Subject: Re: panic: no BIOS SMAP info from loader 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, 05 Nov 2007 21:40:49 -0000 On 11/5/07, John Baldwin wrote: > On Monday 05 November 2007 11:48:07 am Bob Johnson wrote: > > On 11/5/07, Bob Johnson wrote: > > > > > My web searches on this indicated that when HP first introduced these > > > systems, they had the same problem with Linux. HP provided a patch > > > that allows recent Linux kernels to boot. Older i386 FreeBSDs also can > > > not boot on my HP dc7700. So it appears someone has already fixed this > > > for i386, but no one has moved it to AMD64. > > > > > > I don't remember which i386 versions work or don't work, but I can > > > start booting install disks and find out. > > > > Hmmm. Maybe I should retract that. I cannot find an i386 install CD > > that won't boot on it. I've tried 7.0-BETA1, 6.2-STABLEsnap200708, > > 6.2-RC1, 6.1-RELEASE, 6.0-BETA2, 6.0-BETA1, 5.3-RC1 (hangs probing > > ATA1), 4.5-RELEASE, and 4.3-RELEASE. But I thought I remembered being > > unable to boot some i386 install CDs in it. > > Without an SMAP, FreeBSD/i386 is only going to find about 64M of RAM on the > box though. That's why I concluded that someone had fixed the problem in i386 but not moved it to amd64. This system has no problem with i386. The install disk boots without any special action on my part, the system installs, works great (except the x.org 7.3 ati driver doesn't support the video chipset, but VESA mode is adequate for now). > Do you know what the patch was that HP provided for Linux? I > wasn't able to find it. No, I only read some postings on Linux lists that said HP had supplied a patch that allowed HP 64-bit boxes to run Linux if your kernel was new enough. And the poster in that case may not have been entirely accurate! I think the dates were around 1st Q of this year. Of course, I can't find those postings now. > If you disable ACPI is FreeBSD/i386 able to see all of the RAM in the box? i386 can see it with ACPI enabled or disabled. Only amd64 has a problem in my case. Judging by various postings, different HP systems seem to have different details, though. At the moment I'm running i386 7.0-CURRENT-200708 snapshot on an HP dc7700 convertible (BIOS 1.10) with ACPI enabled. It reports real memory = 3757768704 (3583 MB) and ACPI APIC Table: . An amd64 install CD gets the SMAP panic with or without ACPI. I just read that HP has released a newer BIOS for this thing since I was trying to install amd64. So when I get time I will try updating the BIOS and see what happens. Before that I'll send you the files you asked for. And then maybe again after the BIOS update ;) - Bob From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 5 22:57:16 2007 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD06416A420 for ; Mon, 5 Nov 2007 22:57:16 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id 5CB7013C48D for ; Mon, 5 Nov 2007 22:57:16 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8p) with ESMTP id 217884076-1834499 for multiple; Mon, 05 Nov 2007 17:57:20 -0500 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id lA5MunWJ064856; Mon, 5 Nov 2007 17:56:51 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Abdullah Ibn Hamad Al-Marri" Date: Mon, 5 Nov 2007 16:34:32 -0500 User-Agent: KMail/1.9.6 References: <6eb82e0711010634x5f70e974i78c505d8eda24223@mail.gmail.com> <200711051415.53489.jhb@freebsd.org> <499c70c0711051238o2463bbefx56856dfdb31f31cf@mail.gmail.com> In-Reply-To: <499c70c0711051238o2463bbefx56856dfdb31f31cf@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200711051634.32518.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Mon, 05 Nov 2007 17:56:51 -0500 (EST) X-Virus-Scanned: ClamAV 0.91.2/4675/Mon Nov 5 11:20:43 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.7 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00, INFO_TLD autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: amd64@freebsd.org Subject: Re: panic: no BIOS SMAP info from loader 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, 05 Nov 2007 22:57:16 -0000 On Monday 05 November 2007 03:38:52 pm Abdullah Ibn Hamad Al-Marri wrote: > On Nov 5, 2007 10:15 PM, John Baldwin wrote: > > > > On Monday 05 November 2007 11:48:07 am Bob Johnson wrote: > > > On 11/5/07, Bob Johnson wrote: > > > > > > > My web searches on this indicated that when HP first introduced these > > > > systems, they had the same problem with Linux. HP provided a patch > > > > that allows recent Linux kernels to boot. Older i386 FreeBSDs also can > > > > not boot on my HP dc7700. So it appears someone has already fixed this > > > > for i386, but no one has moved it to AMD64. > > > > > > > > I don't remember which i386 versions work or don't work, but I can > > > > start booting install disks and find out. > > > > > > Hmmm. Maybe I should retract that. I cannot find an i386 install CD > > > that won't boot on it. I've tried 7.0-BETA1, 6.2-STABLEsnap200708, > > > 6.2-RC1, 6.1-RELEASE, 6.0-BETA2, 6.0-BETA1, 5.3-RC1 (hangs probing > > > ATA1), 4.5-RELEASE, and 4.3-RELEASE. But I thought I remembered being > > > unable to boot some i386 install CDs in it. > > > > Without an SMAP, FreeBSD/i386 is only going to find about 64M of RAM on the > > box though. Do you know what the patch was that HP provided for Linux? I > > wasn't able to find it. If you disable ACPI is FreeBSD/i386 able to see all > > of the RAM in the box? > > > > -- > > John Baldwin > > John, > > This one? > > http://bugzilla.kernel.org/show_bug.cgi?id=8833 > http://marc.info/?l=linux-kernel&m=118809338631160&w=2 That is interesting, but not related in this case. This is long, long after getting a copy of the SMAP. -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 6 01:24:04 2007 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5CF816A469 for ; Tue, 6 Nov 2007 01:24:04 +0000 (UTC) (envelope-from grafan@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.186]) by mx1.freebsd.org (Postfix) with ESMTP id 3BA2713C491 for ; Tue, 6 Nov 2007 01:24:03 +0000 (UTC) (envelope-from grafan@gmail.com) Received: by fk-out-0910.google.com with SMTP id b27so2080853fka for ; Mon, 05 Nov 2007 17:23:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Pct4OPq28+K1C5LMpbpmxGbAachpK3YFagz+KQzexCw=; b=MxOPOhQtjro5RD07yZQOj4aWOH6L/zM+EnXzmd9fsQ400fCK7PepwBP1t8y33HK4v0P3ZT9ruh+sycjyQvf5VdMSXH+lzGx3X6+USMRb/ZVqoXNIzq1SbePbKH1Jx7zWpwRvfNkDvaRoUOGx8MUMuD0WpW+IAQ/regMg9FE+n3w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Fh9fWrg9qP2Ks/J49mdTsh9KCwo8leIfF58pY4W32Glgo+UzK8j5HSv44xhDOuEVZGpS17cwF5iPAX+5KiVXAC2zv3Vu5mych3SQoqIXkV9WA6Nly8Nbg75gysOn2ulPzw17sAx7paD30JqAJ0FBl1NJyNMwffHOtwHn43mYB+w= Received: by 10.82.138.6 with SMTP id l6mr11120408bud.1194312235459; Mon, 05 Nov 2007 17:23:55 -0800 (PST) Received: by 10.82.115.11 with HTTP; Mon, 5 Nov 2007 17:23:55 -0800 (PST) Message-ID: <6eb82e0711051723g20ef2ee0qb8f030601542f8ad@mail.gmail.com> Date: Tue, 6 Nov 2007 09:23:55 +0800 From: "Rong-en Fan" To: amd64@freebsd.org In-Reply-To: <200711021403.04716.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <6eb82e0711010634x5f70e974i78c505d8eda24223@mail.gmail.com> <200711011327.27953.jhb@freebsd.org> <6eb82e0711011841q111fd701sa982c0e7a7f136df@mail.gmail.com> <200711021403.04716.jhb@freebsd.org> Cc: Subject: Re: panic: no BIOS SMAP info from loader 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, 06 Nov 2007 01:24:04 -0000 On Nov 3, 2007 2:03 AM, John Baldwin wrote: > > On Thursday 01 November 2007 09:41:09 pm Rong-en Fan wrote: > > On 11/2/07, John Baldwin wrote: > > > On Thursday 01 November 2007 09:34:22 am Rong-en Fan wrote: > > > > I have a HP dc7000 box, booting with i386 is fine, but not > > > > amd64. It panics as soon as loader loads kernel. The console > > > > snapshot is at > > > > > > > > http://www.flickr.com/photos/rafan/1814155320/ > > > > > > > > under loader prompt, 'smap' shows nothing for both i386 > > > > and amd64. But i386 works well. I looked at archive, it > > > > seems there are several reports, but no solution. BTW, the boot > > > > cd I used is 7.0-BETA1.5. > > > > > > Does Linux find an SMAP? Right now FreeBSD/amd64 requires an SMAP. > > > > I'm not sure if I get this right, on Linux it shows > > > > BIOS-provided physical RAM map: > > BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) > > BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) > > BIOS-e820: 00000000000e8000 - 0000000000100000 (reserved) > > BIOS-e820: 0000000000100000 - 00000000defafe00 (usable) > > BIOS-e820: 00000000defafe00 - 00000000defb1ea0 (ACPI NVS) > > BIOS-e820: 00000000defb1ea0 - 00000000e0000000 (reserved) > > BIOS-e820: 00000000f4000000 - 00000000f8000000 (reserved) > > BIOS-e820: 00000000fec00000 - 00000000fed40000 (reserved) > > BIOS-e820: 00000000fed45000 - 0000000100000000 (reserved) > > BIOS-e820: 0000000100000000 - 000000021c000000 (usable) > > Ok, so Linux finds it. They use the same algo the loader uses, so I don't see > why this isn't working. :( You can try adding some debug printfs into > sys/boot/i386/libi386/biossmap.c where it calls the BIOS to fetch the SMAP. > You can also try disassembling your BIOS to see how it handles int 0x15 > ax=0xe820 to see if it is expecting something odd. Right after v86int(), it shows efl 243 eax 8600 ecx 0 edx 534d4150 es 3fa7 edi 4 As eax != SMAPSIG, it just quits the loop... It's obtained from 200704 i386 current snap. BTW, netbsd 3.1 amd64 boots just fine on the same box. But I forget to check whether it can see all memory or not. Regards, Rong-En Fan From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 6 07:10:04 2007 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8EABF16A469 for ; Tue, 6 Nov 2007 07:10:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 638A113C481 for ; Tue, 6 Nov 2007 07:10:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id lA67A4D8096374 for ; Tue, 6 Nov 2007 07:10:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id lA67A4Ns096373; Tue, 6 Nov 2007 07:10:04 GMT (envelope-from gnats) Resent-Date: Tue, 6 Nov 2007 07:10:04 GMT Resent-Message-Id: <200711060710.lA67A4Ns096373@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, anonamoose Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D16216A417 for ; Tue, 6 Nov 2007 07:05:57 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id EC4EB13C4B2 for ; Tue, 6 Nov 2007 07:05:56 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.1/8.14.1) with ESMTP id lA675h6A018631 for ; Tue, 6 Nov 2007 07:05:43 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.1/8.14.1/Submit) id lA675hA7018630; Tue, 6 Nov 2007 07:05:43 GMT (envelope-from nobody) Message-Id: <200711060705.lA675hA7018630@www.freebsd.org> Date: Tue, 6 Nov 2007 07:05:43 GMT From: anonamoose To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Tue, 06 Nov 2007 13:10:31 +0000 Cc: Subject: amd64/117858: can not install / does not recognize network / no network connection 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, 06 Nov 2007 07:10:04 -0000 >Number: 117858 >Category: amd64 >Synopsis: can not install / does not recognize network / no network connection >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Nov 06 07:10:04 UTC 2007 >Closed-Date: >Last-Modified: >Originator: anonamoose >Release: 7.0-BETA2-amd64-bootonly >Organization: disorganized >Environment: n/a >Description: can not configure network possible clue: On the "Network Interface Information Required" menu, the option to select is displayed as: nfe0 = NVIDIA nForce MCP Ethernet There is no "nfe0" driver. The option should be: nve0 = NVIDIA nForce MCP Ethernet >How-To-Repeat: try installing it >Fix: maybe fix the typeo? "nfe0" should be "nve0" >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 6 16:33:59 2007 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6761516A41B; Tue, 6 Nov 2007 16:33:59 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id ECB2213C4B9; Tue, 6 Nov 2007 16:33:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8p) with ESMTP id 217995159-1834499 for multiple; Tue, 06 Nov 2007 11:34:13 -0500 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id lA6GXjlj073975; Tue, 6 Nov 2007 11:33:46 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org Date: Tue, 6 Nov 2007 11:33:38 -0500 User-Agent: KMail/1.9.6 References: <200711060705.lA675hA7018630@www.freebsd.org> In-Reply-To: <200711060705.lA675hA7018630@www.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200711061133.38912.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Tue, 06 Nov 2007 11:33:46 -0500 (EST) X-Virus-Scanned: ClamAV 0.91.2/4681/Tue Nov 6 07:52:41 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: anonamoose , freebsd-gnats-submit@freebsd.org Subject: Re: amd64/117858: can not install / does not recognize network / no network connection 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, 06 Nov 2007 16:33:59 -0000 On Tuesday 06 November 2007 02:05:43 am anonamoose wrote: > possible clue: > On the "Network Interface Information Required" menu, the option to select is displayed as: nfe0 = NVIDIA nForce MCP Ethernet > > There is no "nfe0" driver. The option should be: > nve0 = NVIDIA nForce MCP Ethernet There _is_ a nfe(4) driver and it supersedes nve(4) in 7.0. Did you try to use nfe0? -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 6 16:40:03 2007 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C52316A420 for ; Tue, 6 Nov 2007 16:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 48D6413C4BF for ; Tue, 6 Nov 2007 16:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id lA6Ge3K4046816 for ; Tue, 6 Nov 2007 16:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id lA6Ge3DL046813; Tue, 6 Nov 2007 16:40:03 GMT (envelope-from gnats) Date: Tue, 6 Nov 2007 16:40:03 GMT Message-Id: <200711061640.lA6Ge3DL046813@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: John Baldwin Cc: Subject: Re: amd64/117858: can not install / does not recognize network / no network connection X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Baldwin List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Nov 2007 16:40:03 -0000 The following reply was made to PR amd64/117858; it has been noted by GNATS. From: John Baldwin To: freebsd-amd64@freebsd.org Cc: anonamoose , freebsd-gnats-submit@freebsd.org Subject: Re: amd64/117858: can not install / does not recognize network / no network connection Date: Tue, 6 Nov 2007 11:33:38 -0500 On Tuesday 06 November 2007 02:05:43 am anonamoose wrote: > possible clue: > On the "Network Interface Information Required" menu, the option to select is displayed as: nfe0 = NVIDIA nForce MCP Ethernet > > There is no "nfe0" driver. The option should be: > nve0 = NVIDIA nForce MCP Ethernet There _is_ a nfe(4) driver and it supersedes nve(4) in 7.0. Did you try to use nfe0? -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 6 19:29:22 2007 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C80616A419; Tue, 6 Nov 2007 19:29:22 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from angel.ticketswitch.com (angel.ticketswitch.com [IPv6:2002:57e0:1d4e::1]) by mx1.freebsd.org (Postfix) with ESMTP id 089FE13C494; Tue, 6 Nov 2007 19:29:21 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from smaug.rattatosk ([10.50.50.2]) by angel.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67 (FreeBSD)) (envelope-from ) id 1IpU6x-000CHH-V2; Tue, 06 Nov 2007 19:29:19 +0000 Received: from dilbert.rattatosk ([10.50.50.6] helo=dilbert.ticketswitch.com) by smaug.rattatosk with esmtp (Exim 4.67 (FreeBSD)) (envelope-from ) id 1IpU6x-000Klh-SV; Tue, 06 Nov 2007 19:29:19 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IpU6x-000HVI-Qx; Tue, 06 Nov 2007 19:29:19 +0000 To: fbsdlists@gmail.com, jhb@freebsd.org In-Reply-To: <54db43990711051340j727d43c6t6ee5aeb5a9342c8e@mail.gmail.com> Message-Id: From: Pete French Date: Tue, 06 Nov 2007 19:29:19 +0000 Cc: amd64@freebsd.org Subject: Re: panic: no BIOS SMAP info from loader 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, 06 Nov 2007 19:29:22 -0000 Just to clarify, is this SMAP issue the same thing which means you have to boot these boxes with ACPI disabled (on either i386 or amd64) or are they separate problems ? [and what info can those of us with affected system provide to help?] cheers, -pete. From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 6 21:59:02 2007 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD1ED16A420 for ; Tue, 6 Nov 2007 21:59:02 +0000 (UTC) (envelope-from fbsdlists@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.229]) by mx1.freebsd.org (Postfix) with ESMTP id 8BC6813C4C5 for ; Tue, 6 Nov 2007 21:59:01 +0000 (UTC) (envelope-from fbsdlists@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so1337761nzf for ; Tue, 06 Nov 2007 13:59:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=ORgAAOU7aOVEe6iVMKIuwp7u0+DSYfmRuJXDaP0Rsh4=; b=fxqOPBchKejcg5mB2q/27Pba19OwIm3nn+J0JJJIaKRUUvyK5krQv6gCnoKM8i4KkenwC7NiiKC5fwQyOszn1Ts5dytYcgURNkSqh2ZBgYy/zJIa2RiMfcvM7A7Pv/NBTZ/1Okc9nwD+Zl0945/0NRzTVFzUQPnSF5k2UKRlj/0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Fx/5dvTrTfsl3Fn62zyhsKHFEK3ZOciId02GJC4FeZQd8EoMoOa/huTeb/ACFc/CJemp9TBvlbN8vqno37jXH332XrEae6f1bTZ4NVgTAVRkgoT72XiSCgR5tb766ndvMbO36MnHZtZy7cjqnTCyLq3N/vVl6Jx10g1VYU/P/es= Received: by 10.142.240.9 with SMTP id n9mr1878453wfh.1194386339956; Tue, 06 Nov 2007 13:58:59 -0800 (PST) Received: by 10.142.216.9 with HTTP; Tue, 6 Nov 2007 13:58:59 -0800 (PST) Message-ID: <54db43990711061358u7d626bf4pe02d4086b2de6715@mail.gmail.com> Date: Tue, 6 Nov 2007 16:58:59 -0500 From: "Bob Johnson" To: "Pete French" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <54db43990711051340j727d43c6t6ee5aeb5a9342c8e@mail.gmail.com> Cc: amd64@freebsd.org Subject: Re: panic: no BIOS SMAP info from loader 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, 06 Nov 2007 21:59:02 -0000 On 11/6/07, Pete French wrote: > Just to clarify, is this SMAP issue the same thing which means you > have to boot these boxes with ACPI disabled (on either i386 or amd64) or > are they separate problems ? > > [and what info can those of us with affected system provide to help?] In my case, the ACPI setting makes no difference. And I only have the problem with amd64. If you get the error message "No BIOS smap info from loader!" while booting, and the system locks up, then it is probably related. - Bob From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 8 22:06:36 2007 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9E3416A41A for ; Thu, 8 Nov 2007 22:06:36 +0000 (UTC) (envelope-from andrades@cisco.com) Received: from sj-iport-1.cisco.com (sj-iport-1-in.cisco.com [171.71.176.70]) by mx1.freebsd.org (Postfix) with ESMTP id 92D9F13C4BB for ; Thu, 8 Nov 2007 22:06:36 +0000 (UTC) (envelope-from andrades@cisco.com) X-IronPort-AV: E=Sophos;i="4.21,391,1188802800"; d="scan'208";a="31262274" Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-1.cisco.com with ESMTP; 08 Nov 2007 13:53:50 -0800 Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id lA8LrnCq020561 for ; Thu, 8 Nov 2007 13:53:49 -0800 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id lA8Lrgen019029 for ; Thu, 8 Nov 2007 21:53:49 GMT Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 8 Nov 2007 13:53:44 -0800 Received: from [10.33.235.12] ([10.33.235.12]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 8 Nov 2007 13:53:44 -0800 Message-ID: <47338559.8040302@cisco.com> Date: Thu, 08 Nov 2007 13:53:29 -0800 From: Richard Andrades Organization: GSBU sw User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: amd64@freebsd.org References: <54db43990711051340j727d43c6t6ee5aeb5a9342c8e@mail.gmail.com> <54db43990711061358u7d626bf4pe02d4086b2de6715@mail.gmail.com> In-Reply-To: <54db43990711061358u7d626bf4pe02d4086b2de6715@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 08 Nov 2007 21:53:44.0774 (UTC) FILETIME=[D5623E60:01C82251] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=139; t=1194558829; x=1195422829; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=andrades@cisco.com; z=From:=20Richard=20Andrades=20 |Subject:=20Using=204M=20pages=20in=20amd64=2064-bit=20mode |Sender:=20; bh=e0c1ARpKulb3H7viDnyTyeYantVJgBm0KiFtW7d/b+4=; b=Fb7lgeefm2zWaH2GRmf0jfPzeTPHz9upVK7m6+EQHUvdiNYmjfCXAXf/VvqYRemWn7jRcX6U NzSfKTBVHmzdbhCJz/ce7MRS/HpmZKihS6Z/gabASb1PX0J1upAPVm0t2HxdQQTq+JudJ0n3ud +b45KStnxg6UvMacbBpxjC3kY=; Authentication-Results: sj-dkim-1; header.From=andrades@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); Cc: Subject: Using 4M pages in amd64 64-bit mode X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: andrades@cisco.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2007 22:06:36 -0000 Hello, Does anyone know if there is support for using the large page sizes with the amd64 (Opteron or Barcelona)? Thanks, Richard From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 9 20:50:00 2007 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86C3016A478 for ; Fri, 9 Nov 2007 20:50:00 +0000 (UTC) (envelope-from ciscoaix@yahoo.com) Received: from web90613.mail.mud.yahoo.com (web90613.mail.mud.yahoo.com [216.252.100.196]) by mx1.freebsd.org (Postfix) with SMTP id 5F97A13C4A3 for ; Fri, 9 Nov 2007 20:50:00 +0000 (UTC) (envelope-from ciscoaix@yahoo.com) Received: (qmail 65196 invoked by uid 60001); 9 Nov 2007 20:22:57 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=SnU737E2LaeSkbbqLn7a5wuIdmbyg9pwgrjv4gCLBOWGwNl3tVckCno/+vyqdyslEqF4OHotMFMtMt2y13ePTBXI7KeX2L5BGyNlg7FjrOh3r/8DtHagfs+wyv/AkpxB7Urtyli5mKyZ6CUTFEWraQ78lWyJQAGo1xpk39oYjF8=; X-YMail-OSG: zCL6fIAVM1nc0hMPX3QTheSoKx.zEad9JsrdskQ4Ml9guY7ess_mc2wWh1AihbtNqhkXkVdHATXj9NrcZpxx7gXHLQZpr3DFgoxcqWXwM5aYqV71Vnc- Received: from [198.237.17.1] by web90613.mail.mud.yahoo.com via HTTP; Fri, 09 Nov 2007 12:22:57 PST Date: Fri, 9 Nov 2007 12:22:57 -0800 (PST) From: Kris Anderson To: amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <304158.64464.qm@web90613.mail.mud.yahoo.com> Cc: Subject: Upgrading to Xorg 7.2 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, 09 Nov 2007 20:50:00 -0000 Hi folks, I was looking at the UPDATING for xorg and I am currious about something. Why are those of us doing fresh downloads of the OS having to do the upgrade to 7.2? I see that 6.9 is installed, why not just make 7.2 the default? In UPDATING 20070519: AFFECTS: users of Xorg AUTHOR: kris@FreeBSD.org Welcome, fearless user! You are about to embark upon a mystical journey to the world of xorg 7.2. This upgrade procedure is for users of portupgrade. Users of other upgrade tools should contact the author for the corresponding upgrade method for that tool. It is recommended that you run the xorg 7.2 upgrade inside a script(1) session. This way, if something goes wrong, you will have hopefully saved enough information for the developers to debug the problem. Make sure you choose a filesystem with lots of space for the script output. # script xorg-upgrade You may wish to set BATCH=yes in the environment to avoid interactive dialogue boxes. In # script xorg-upgrade, why doesn't the file tell us where to get the script and what other files that might be needed, or where to go for additional guidance on this step? Please update the UPDATING to reflect where we're go to get this script. Thank you very much. If xorg 6.9 is removed (via pgk_delete /var/db/pkg/xorg-* along with any complaints about dependencies) do I still need to go through all the steps outlined in UPDATING or do I just go in to ports/x11/xorg (or where ever the meta gizmo is at these days) and do a make install? I would have tried pkg_add xorg but I happen to notice that it was then trying to fetch 6.2. But then perhaps an enviroment variable might needed to be set. #pkg_add -r xorg Fetching ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-6.2-release/Latest/xorg.tbz... Done. Is it really fetching 6.2 or is there just a typo someplace and it should have read 7.2? Well that's enough inquiring for now, hopefully I can get the thing going. I'm trying to use the GD library for PHP and it just wants to go get X stuff. *sigh* __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 10 16:56:31 2007 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 48A5416A420 for ; Sat, 10 Nov 2007 16:56:31 +0000 (UTC) (envelope-from dan@slightlystrange.org) Received: from catflap.slightlystrange.org (cpc5-cmbg1-0-0-cust497.cmbg.cable.ntl.com [86.6.1.242]) by mx1.freebsd.org (Postfix) with ESMTP id 87D9B13C4A7 for ; Sat, 10 Nov 2007 16:56:30 +0000 (UTC) (envelope-from dan@slightlystrange.org) Received: by catflap.slightlystrange.org (Postfix, from userid 106) id 0C818610C; Sat, 10 Nov 2007 16:38:26 +0000 (GMT) Received: from torus.slightlystrange.org (torus.slightlystrange.org [10.1.3.50]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by catflap.slightlystrange.org (Postfix) with ESMTP id 48AA160E2 for ; Sat, 10 Nov 2007 16:38:25 +0000 (GMT) Received: (from danielby@localhost) by torus.slightlystrange.org (8.14.1/8.13.4/Submit) id lAAGcNgT000773 for amd64@freebsd.org; Sat, 10 Nov 2007 16:38:23 GMT (envelope-from dan@slightlystrange.org) Date: Sat, 10 Nov 2007 16:38:23 +0000 From: Daniel Bye To: amd64@freebsd.org Message-ID: <20071110163823.GB4118@torus.slightlystrange.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZfOjI3PrQbgiZnxM" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-PGP-Fingerprint: D349 B109 0EB8 2554 4D75 B79A 8B17 F97C 1622 166A X-Mailman-Approved-At: Sat, 10 Nov 2007 17:04:17 +0000 Cc: Subject: Re: Upgrading to Xorg 7.2 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Bye List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2007 16:56:31 -0000 --ZfOjI3PrQbgiZnxM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 09, 2007 at 12:22:57PM -0800, Kris Anderson wrote: > Hi folks, > I was looking at the UPDATING for xorg > and I am currious about something. >=20 > Why are those of us doing fresh downloads of the OS > having to do the upgrade to 7.2? I see that 6.9 is > installed, why not just make 7.2 the default? When doing a fresh install, try to avoid installing any extra packages. It's better to wait and install from ports, to ensure you get the latest released versions. The packages bundled with each release are out of date pretty quickly - as the ports maintainers continue to upgrade and improve what's available, so the static snapshot of the ports tree that gets installed will be more and more obsolete. I usually don't even install ports any more from the install media - I prefer to use portsnap to get=20 the latest snapshot, and then crack on with installing whatever it is I need. >=20 > In UPDATING > 20070519: > AFFECTS: users of Xorg > AUTHOR: kris@FreeBSD.org >=20 > Welcome, fearless user! You are about to embark > upon a mystical > journey to the world of xorg 7.2. >=20 > This upgrade procedure is for users of portupgrade.=20 > Users of other > upgrade tools should contact the author for the > corresponding upgrade > method for that tool. >=20 > It is recommended that you run the xorg 7.2 upgrade > inside a script(1) > session. This way, if something goes wrong, you > will have hopefully > saved enough information for the developers to debug > the problem. > Make sure you choose a filesystem with lots of space > for the script > output. >=20 > # script xorg-upgrade >=20 > You may wish to set BATCH=3Dyes in the environment to > avoid interactive > dialogue boxes. >=20 >=20 > In # script xorg-upgrade, why doesn't the file tell us > where to get the script and what other files that > might be needed, or where to go for additional > guidance on this step? Please update the UPDATING to > reflect where we're go to get this script. Thank you > very much. script(1) in this instance refers to the Unix command script, which will save all subsequent terminal IO in the file named (in this example) xorg-upgrade. It is simply a way to record what happened next, in case something goes wrong, etc. man script for more details.=20 >=20 > If xorg 6.9 is removed (via pgk_delete > /var/db/pkg/xorg-* along with any complaints about > dependencies) do I still need to go through all the > steps outlined in UPDATING or do I just go in to > ports/x11/xorg (or where ever the meta gizmo is at > these days) and do a make install? If you have removed anything and everything to do with Xorg, then you are effectively going to be doing a clean install - so you should just be able to portinstall xorg. It worked this way for me on my laptop without any hitches. However, you must be certain you don't have any old X related ports still lurking, or it could blow up. >=20 > I would have tried pkg_add xorg but I happen to notice > that it was then trying to fetch 6.2. But then perhaps > an enviroment variable might needed to be set. > #pkg_add -r xorg > Fetching > ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-6.2-release/Latest= /xorg.tbz... > Done. >=20 > Is it really fetching 6.2 or is there just a typo > someplace and it should have read 7.2? No, it's downloading a prebuilt package suitable for FreeBSD 6.2 (I guess you're on 6.2?) >=20 > Well that's enough inquiring for now, hopefully I can > get the thing going. I'm trying to use the GD library > for PHP and it just wants to go get X stuff. *sigh* Yes, it is after all a graphics library! ;-) HTH Dan --=20 Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ ----- End forwarded message ----- --=20 Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ --ZfOjI3PrQbgiZnxM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHNd5/ixf5fBYiFmoRAkP4AJ9/9BffAbty+AWiwiwVGrvtw5mB3QCfeSMs 3kWX/QiSi0NWrcjTzPxk22Q= =b40A -----END PGP SIGNATURE----- --ZfOjI3PrQbgiZnxM--