From owner-freebsd-amd64@FreeBSD.ORG Mon May 15 09:06: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 0C14316A72A for ; Mon, 15 May 2006 09:06:11 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6F7243D69 for ; Mon, 15 May 2006 09:06:06 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (rahsrq@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k4F95vtF038414 for ; Mon, 15 May 2006 11:06:02 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k4F95v44038413; Mon, 15 May 2006 11:05:57 +0200 (CEST) (envelope-from olli) Date: Mon, 15 May 2006 11:05:57 +0200 (CEST) Message-Id: <200605150905.k4F95v44038413@lurza.secnetix.de> From: Oliver Fromme To: freebsd-amd64@FreeBSD.ORG In-Reply-To: <20060513212555.GA23965@troutmask.apl.washington.edu> X-Newsgroups: list.freebsd-amd64 User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Mon, 15 May 2006 11:06:02 +0200 (CEST) Cc: Subject: Re: Installation from USB cdrom/dvd drive? 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: Mon, 15 May 2006 09:06:15 -0000 Steve Kargl wrote: > On Sat, May 13, 2006 at 09:08:45PM +0200, Oliver Fromme wrote: > > However, it might be more convenient to perform a > > networked installation via PXE (provided that your > > blade system supports PXE booting). > > Yes, it supports PXE. I suppose this is covered in > the Handbook. There's a separate article on PXE-based installation: http://www.freebsd.org/doc/en/articles/pxe/ Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "Life is short (You need Python)" -- Bruce Eckel, ANSI C++ Comitee member, author of "Thinking in C++" and "Thinking in Java" From owner-freebsd-amd64@FreeBSD.ORG Mon May 15 09:26: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 4053E16A868 for ; Mon, 15 May 2006 09:26:15 +0000 (UTC) (envelope-from jhs@flat.berklix.net) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94FF243D5E for ; Mon, 15 May 2006 09:26:12 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A6F50.dip.t-dialin.net [84.154.111.80]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id k4F9Q9Po055968; Mon, 15 May 2006 11:26:10 +0200 (CEST) (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 k4F9Q7Yi008170; Mon, 15 May 2006 11:26:07 +0200 (CEST) (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 k4F9Rsiq079025; Mon, 15 May 2006 11:27:54 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200605150927.k4F9Rsiq079025@fire.jhs.private> To: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= In-Reply-To: Message from =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= of "Fri, 12 May 2006 10:23:53 +0200." <44644619.70306@t-hosting.hu> Date: Mon, 15 May 2006 11:27:54 +0200 From: "Julian H. Stacey" Cc: freebsd-amd64@freebsd.org Subject: Re: Running i386 binaries on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 May 2006 09:26:15 -0000 jimprettyman@gmail.com wrote > I have just installed FreeBSD-6.1-R gabor.kovesdan@t-hosting.hu wrote: > either, you have to get the RELENG_6_1 RELENG_6_1 is for stable beyond, which jim might not want, to match release if uname -r == 6.1-RELEASE : RELENG_6_1_0_RELEASE > source with CVSup/Csup. Or even CTM + CVS, eg cvs -R export -r RELENG_6_1_0_RELEASE src -- Julian Stacey. Consultant Unix Net & Sys. Eng., Munich. http://berklix.com From owner-freebsd-amd64@FreeBSD.ORG Mon May 15 11:02:38 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 8283416A40D for ; Mon, 15 May 2006 11:02:38 +0000 (UTC) (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 EF76E43D55 for ; Mon, 15 May 2006 11:02:37 +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 k4FB2bhi075116 for ; Mon, 15 May 2006 11:02:37 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k4FB2aVF075110 for freebsd-amd64@freebsd.org; Mon, 15 May 2006 11:02:36 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 15 May 2006 11:02:36 GMT Message-Id: <200605151102.k4FB2aVF075110@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 May 2006 11:02:38 -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 o [2006/03/01] amd64/93961 amd64 Problem in bounce buffer handling in sys/ o [2006/05/09] amd64/97019 amd64 Cannot load the kernel after installation 4 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- 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/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/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/12/05] amd64/74747 amd64 System panic on shutdown when process wil 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/03/04] amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/p 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/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 [2006/01/06] amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr o [2006/01/08] amd64/91492 amd64 BTX halted o [2006/01/26] amd64/92337 amd64 FreeBsd 6.0 Release Intel Pro 1000 MT em1 o [2006/02/06] amd64/92889 amd64 xdr double buffer overflow o [2006/02/07] amd64/92991 amd64 FreeBSD(amd64) freezes when primary disk o [2006/02/08] amd64/93065 amd64 Running make depend on GENERIC kernel fai o [2006/02/14] amd64/93325 amd64 mount_ufs fails mounting Nero UFS DVD+RW o [2006/02/16] amd64/93413 amd64 lpd does not remove lock file from /var/s o [2006/02/17] amd64/93469 amd64 uninitialised struct stat in lpd prevents o [2006/03/19] amd64/94677 amd64 panic in amd64 install at non-root user c o [2006/03/24] amd64/94896 amd64 Where support VESA Modes for AMD64 kernel o [2006/03/27] amd64/94989 amd64 BTX Halts on Sun Fire X2100 w/6.1-BETA4 ( o [2006/03/28] amd64/95056 amd64 Nvidia Nforce ETH Driver -> Timeout Error o [2006/03/31] amd64/95167 amd64 driver for SuperMicro H8DAR-T (Adaptec AI o [2006/04/06] amd64/95414 amd64 kernel crashes during install o [2006/04/06] amd64/95418 amd64 pthread segmentation fault o [2006/04/09] amd64/95554 amd64 undetected sata drive on 6.1, detected on o [2006/04/16] amd64/95888 amd64 kernel: ad2: TIMEOUT - WRITE_DMA retrying o [2006/04/27] amd64/96400 amd64 FreeBSD 6.0 Bootin Conflict between Broad o [2006/05/10] amd64/97075 amd64 Panic, Trap 12 o [2006/05/11] amd64/97123 amd64 Vinum isn't in included in kernel o [2006/05/12] amd64/97184 amd64 Error compiling 6.1 zlib module (kernel) 69 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 [2005/03/17] amd64/78954 amd64 kerberos 5 failed to build 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 o [2006/01/30] amd64/92527 amd64 no driver for "CICADA VSC 8201 Gigabit LA o [2006/02/07] amd64/93002 amd64 amd64 (6.0) coredumps at unpredictable ti o [2006/02/09] amd64/93090 amd64 NIC on GA-K8NF-9 motherboard is recognize o [2006/02/28] amd64/93930 amd64 Page fault on `kldunload snd_driver` o [2006/04/03] amd64/95282 amd64 patch: fix ed for RELENG_5 amd64 so that o [2006/04/12] amd64/95651 amd64 CANT INSTALL o [2006/04/29] amd64/96516 amd64 FreeBSD/amd64 intermittent Network-Proble 21 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon May 15 11:17:20 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 079FF16A46B for ; Mon, 15 May 2006 11:17:20 +0000 (UTC) (envelope-from gabor.kovesdan@t-hosting.hu) Received: from server.t-hosting.hu (server.t-hosting.hu [217.20.133.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76C9143D45 for ; Mon, 15 May 2006 11:17:19 +0000 (GMT) (envelope-from gabor.kovesdan@t-hosting.hu) Received: from localhost (localhost [127.0.0.1]) by server.t-hosting.hu (Postfix) with ESMTP id F29D9998888; Mon, 15 May 2006 13:17:16 +0200 (CEST) X-Virus-Scanned: amavisd-new at t-hosting.hu Received: from server.t-hosting.hu ([127.0.0.1]) by localhost (server.t-hosting.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 38ZyQc+j3Mja; Mon, 15 May 2006 13:17:12 +0200 (CEST) Received: from [192.168.2.186] (catv-5062e7e3.catv.broadband.hu [80.98.231.227]) by server.t-hosting.hu (Postfix) with ESMTP id 54D29998876; Mon, 15 May 2006 13:17:12 +0200 (CEST) Message-ID: <44686330.2080506@t-hosting.hu> Date: Mon, 15 May 2006 13:17:04 +0200 From: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: "Julian H. Stacey" References: <200605150927.k4F9Rsiq079025@fire.jhs.private> In-Reply-To: <200605150927.k4F9Rsiq079025@fire.jhs.private> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: Running i386 binaries on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 May 2006 11:17:23 -0000 Julian H. Stacey wrote: > gabor.kovesdan@t-hosting.hu wrote: > >> either, you have to get the RELENG_6_1 >> > > RELENG_6_1 is for stable beyond, which jim might not want, > to match release if uname -r == 6.1-RELEASE : RELENG_6_1_0_RELEASE > RELENG_6_1 is *not* for stable, RELENG_6 is for stable. RELENG_6_1 is the security branch for 6.1-RELEASE, this should be used instead of RELENG_6_1_1_RELEASE. Currently, it doesn't make any sense, but later security fixes will go to RELENG_6_1 and it will be unwise to still use RELENG_6_1_0_RELEASE. Gabor Kovesdan From owner-freebsd-amd64@FreeBSD.ORG Mon May 15 13:06: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 8AEBC16A51A for ; Mon, 15 May 2006 13:06:58 +0000 (UTC) (envelope-from jhs@flat.berklix.net) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6CD543D73 for ; Mon, 15 May 2006 13:06:57 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A74E5.dip.t-dialin.net [84.154.116.229]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id k4FD6sXl056375; Mon, 15 May 2006 15:06:55 +0200 (CEST) (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 k4FD6naH009165; Mon, 15 May 2006 15:06:53 +0200 (CEST) (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 k4FCDcBm081238; Mon, 15 May 2006 14:13:38 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200605151213.k4FCDcBm081238@fire.jhs.private> To: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= In-Reply-To: Message from =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= of "Mon, 15 May 2006 13:17:04 +0200." <44686330.2080506@t-hosting.hu> Date: Mon, 15 May 2006 14:13:38 +0200 From: "Julian H. Stacey" Cc: freebsd-amd64@freebsd.org Subject: Re: Running i386 binaries on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 May 2006 13:07:05 -0000 =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= wrote: > Julian H. Stacey wrote: > > gabor.kovesdan@t-hosting.hu wrote: > > > >> either, you have to get the RELENG_6_1 > >> > > > > RELENG_6_1 is for stable beyond, which jim might not want, > > to match release if uname -r == 6.1-RELEASE : RELENG_6_1_0_RELEASE > > > RELENG_6_1 is *not* for stable, RELENG_6 is for stable. Yes. (Tricky word stable, I know what you mean, but I've also seen so called stable that was quite unstable on occasion way back, when one was ill advised to track beyond fixes for the specific release that was really `stable' in the real normal non BSD sense of the word, not some inter-release-hopefully-maybe-but-sometime-not-stable thing ;-) > RELENG_6_1 is > the security branch for 6.1-RELEASE, Yes. (& thus more stable (in the real sense of the word) & invariant than the inter-release progressive RELENG_6 that FreeBSD names as 'Stable') > this should be used instead of > RELENG_6_1_1_RELEASE. "Could" Yes, "Should" No. Not always. It's a matter of personal requirement that we are not qualified to dictate to others. Some few people may _really_ _want_ exactly the release for their own very good reasons eg QA stamped, part of embedded systems with expected & tested & timed repose, relied on to interact exactly as expected, or more bluntly, simply 'cos they've been told they'll be fired & or imprisoned (eg if in military or high rel. sytems), if they change an authorised code base without authority. > Currently, it doesn't make any sense, but later > security fixes will go to RELENG_6_1 Yes. >and it will be unwise to still use > RELENG_6_1_0_RELEASE. Often unwise, not always, depends on situation. Granted if a firewall or exposed to public access, generally good to have latest fixes. -- Julian Stacey. Consultant Unix Net & Sys. Eng., Munich. http://berklix.com Mail in Ascii, HTML=spam. Ihr Rauch = mein allergischer Kopfschmerz. From owner-freebsd-amd64@FreeBSD.ORG Mon May 15 13:20: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 3893F16A65F for ; Mon, 15 May 2006 13:20:51 +0000 (UTC) (envelope-from raf.ponsaerts@med.kuleuven.be) Received: from nibbel.kulnet.kuleuven.ac.be (nibbel.kulnet.kuleuven.ac.be [134.58.240.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38D1743D6A for ; Mon, 15 May 2006 13:20:47 +0000 (GMT) (envelope-from raf.ponsaerts@med.kuleuven.be) Received: from localhost (localhost [127.0.0.1]) by nibbel.kulnet.kuleuven.ac.be (Postfix) with ESMTP id F22384CDEE for ; Mon, 15 May 2006 15:20:46 +0200 (CEST) Received: from smtp03.kuleuven.be (antonius.kulnet.kuleuven.ac.be [134.58.240.73]) by nibbel.kulnet.kuleuven.ac.be (Postfix) with ESMTP id 5AD284CE22 for ; Mon, 15 May 2006 15:20:46 +0200 (CEST) Received: from smtp03.kuleuven.be (localhost.localdomain [127.0.0.1]) by smtp03.kuleuven.be (Postfix) with ESMTP id 391CA332778; Mon, 15 May 2006 15:20:46 +0200 (CEST) Received: from BSD-amd64.med.ad10.intern.kuleuven.be (pc-10-33-121-105.med.kuleuven.ac.be [10.33.121.105]) by smtp03.kuleuven.be (Postfix) with ESMTP id 33FA033275A for ; Mon, 15 May 2006 15:20:46 +0200 (CEST) From: raf ponsaerts To: freebsd-amd64@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-9PRPTUuZnwgHDxDZVCx8" Organization: KULeuven Date: Mon, 15 May 2006 15:20:46 +0200 Message-Id: <1147699246.49891.12.camel@BSD-amd64.med.ad10.intern.kuleuven.be> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port X-Virus-Scanned: by KULeuven Antivirus Cluster Subject: broadcom (bcm4319) wireless card on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: raf.ponsaerts@med.kuleuven.be List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 May 2006 13:20:53 -0000 --=-9PRPTUuZnwgHDxDZVCx8 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable I've already posted this message to "FreeBSD-Questions", about 2 days ago. I got no response ... maybe someone on this list has any idea... My appologies for posting twice and being impatient. > hi all, >=20 > I have a new laptop which runs on FreeBSD6.1beta-amd64 (Turion64 > ML-34). =20 >=20 > The only problem I have is getting the wireless interface up. >=20 > none3@pci6:2:0: class=3D0x028000 card=3D0x1359103c chip=3D0x431914e4 > rev=3D0x02 > hdr=3D0x00 =20 > vendor =3D 'Broadcom Corporation' > class =3D network >=20 > It seems to me I need a driver which supports bcm4319. > I read about the unwillingness of broadcom to support the development > of > a native FreeBSD-driver.=20 >=20 > I am aware of the "Evil project" and the "ndisgen" tool. So, I used > WinXP drivers=20 > (bcmwl5.inf, bcmwl5.sys) to build a module, which loads without any > comment. >=20 > However, ifconfig does not show the wireless interface ... >=20 > When I take a look at the ndiswrapper-list, I see that such cards work > on linux-amd64.=20 >=20 > Does anyone know a way to get past this problem? > Does bcmwl5.inf needs some tweaking? >=20 >=20 > raf=20 >=20 --=-9PRPTUuZnwgHDxDZVCx8 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBEaIAuwoS2GihjEx8RAjc/AJ9tgdGQK4zMZaOpcKMjbEqY4Oyh0ACbBIkE TiQuCriEjFw/YzXprX95MCE= =yib0 -----END PGP SIGNATURE----- --=-9PRPTUuZnwgHDxDZVCx8-- From owner-freebsd-amd64@FreeBSD.ORG Mon May 15 13:58:53 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 8413E16A558; Mon, 15 May 2006 13:58:53 +0000 (UTC) (envelope-from rodrigc@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37D3F43D48; Mon, 15 May 2006 13:58:53 +0000 (GMT) (envelope-from rodrigc@FreeBSD.org) Received: from freefall.freebsd.org (rodrigc@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k4FDwrTa090883; Mon, 15 May 2006 13:58:53 GMT (envelope-from rodrigc@freefall.freebsd.org) Received: (from rodrigc@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k4FDwqba090879; Mon, 15 May 2006 13:58:52 GMT (envelope-from rodrigc) Date: Mon, 15 May 2006 13:58:52 GMT From: Craig Rodrigues Message-Id: <200605151358.k4FDwqba090879@freefall.freebsd.org> To: alain@zwingelstein.org, rodrigc@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/84693: Keyboard not recognized during first step of install (Elite model ECS 755-A/A2) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 May 2006 13:58:54 -0000 Synopsis: Keyboard not recognized during first step of install (Elite model ECS 755-A/A2) State-Changed-From-To: open->feedback State-Changed-By: rodrigc State-Changed-When: Mon May 15 13:58:06 UTC 2006 State-Changed-Why: Are you using a USB keyboard? Can you try installing FreeBSD 6.1? USB keyboard support was improved in that release. http://www.freebsd.org/cgi/query-pr.cgi?pr=84693 From owner-freebsd-amd64@FreeBSD.ORG Mon May 15 13:33: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 B081F16A6F9 for ; Mon, 15 May 2006 13:33:58 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id A017743D6E for ; Mon, 15 May 2006 13:33:47 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wx-out-0102.google.com with SMTP id s19so87086wxc for ; Mon, 15 May 2006 06:33:47 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=nuhUEhE4rfUm91HjP58YXtGqC7WSLxeaVJRhPzChTU5QnGeJyyUcqA71ZuHKcVHWUSOpGIFCU9aaBZGZHOARIugdXtlaKi107pACHYOqRaEke/j1SIjYvYVecTXkKfO3acyeaaRfme29uRi3I//eTURtv31nYhq56tIS4fjUhww= Received: by 10.70.80.2 with SMTP id d2mr6947304wxb; Mon, 15 May 2006 06:33:47 -0700 (PDT) Received: by 10.70.53.10 with HTTP; Mon, 15 May 2006 06:33:46 -0700 (PDT) Message-ID: <790a9fff0605150633l4639d970q4bfe7545ed559ba@mail.gmail.com> Date: Mon, 15 May 2006 08:33:46 -0500 From: "Scot Hetzel" To: raf.ponsaerts@med.kuleuven.be In-Reply-To: <1147699246.49891.12.camel@BSD-amd64.med.ad10.intern.kuleuven.be> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_897_592540.1147700026801" References: <1147699246.49891.12.camel@BSD-amd64.med.ad10.intern.kuleuven.be> X-Mailman-Approved-At: Mon, 15 May 2006 14:09:07 +0000 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-amd64@freebsd.org Subject: Re: broadcom (bcm4319) wireless card on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 May 2006 13:33:59 -0000 ------=_Part_897_592540.1147700026801 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 5/15/06, raf ponsaerts wrote: > I've already posted this message to "FreeBSD-Questions", about 2 days > ago. I got no response ... maybe someone on this list has any idea... > My appologies for posting twice and being impatient. > > > hi all, > > > > I have a new laptop which runs on FreeBSD6.1beta-amd64 (Turion64 > > ML-34). > > > > The only problem I have is getting the wireless interface up. > > > > none3@pci6:2:0: class=3D0x028000 card=3D0x1359103c chip=3D0x431914e4 > > rev=3D0x02 > > hdr=3D0x00 > > vendor =3D 'Broadcom Corporation' > > class =3D network > > > > It seems to me I need a driver which supports bcm4319. > > I read about the unwillingness of broadcom to support the development > > of > > a native FreeBSD-driver. > > > > I am aware of the "Evil project" and the "ndisgen" tool. So, I used > > WinXP drivers > > (bcmwl5.inf, bcmwl5.sys) to build a module, which loads without any > > comment. > > > > However, ifconfig does not show the wireless interface ... > > > > When I take a look at the ndiswrapper-list, I see that such cards work > > on linux-amd64. > > > > Does anyone know a way to get past this problem? > > Does bcmwl5.inf needs some tweaking? > > You need the Broadcom ndis 64bit driver from Windows XP/64. The one you used was a 32bit driver. I have attached the 64bit ndis driver for the Broadcom Wireless. I don't remember where I originally obtained it from. Scot NOTE: 80211g.zp is actually a .zip file, renamed extension to get around gmail zip file protection. --=20 DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ------=_Part_897_592540.1147700026801-- From owner-freebsd-amd64@FreeBSD.ORG Mon May 15 15:16: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 2FD9316A7F6 for ; Mon, 15 May 2006 15:16:11 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B7C443D76 for ; Mon, 15 May 2006 15:16:05 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id BA941B826 for ; Mon, 15 May 2006 11:16:04 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v749.3) In-Reply-To: <200605151358.k4FDwqba090879@freefall.freebsd.org> References: <200605151358.k4FDwqba090879@freefall.freebsd.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <25BF62A8-4DBC-47F3-97A8-F3D67427AC9C@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Mon, 15 May 2006 11:16:03 -0400 To: FreeBSD AMD list X-Mailer: Apple Mail (2.749.3) Subject: Re: amd64/84693: Keyboard not recognized during first step of install (Elite model ECS 755-A/A2) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 May 2006 15:16:17 -0000 On May 15, 2006, at 1:58 PM, Craig Rodrigues wrote: > Synopsis: Keyboard not recognized during first step of install > (Elite model ECS 755-A/A2) > > State-Changed-From-To: open->feedback > State-Changed-By: rodrigc > State-Changed-When: Mon May 15 13:58:06 UTC 2006 > State-Changed-Why: > Are you using a USB keyboard? Can you try installing > FreeBSD 6.1? USB keyboard support was improved in that > release. I upgraded a box from 6.0 to 6.1 which only has a USB keyboard on it. However, for some idiotic reason Dell included an atkbdc controller even though there are no ports to connect to it. I cannot boot into single user mode and get a console keyboard on the screen. I tried the setting hint.atkbdc.0.disabled=1 and it made the kernel not find the atkdbc device but the USB keyboard is still unresponsive after BIOS and initial boot loader prompts. I double checked that the console's hints file entries tell it to probe for keyboard until it finds one (flags 0x100) but it doesn't. I also make sure ukbd module is pre-loaded by loader.conf. Not until devd runs does it connect the USB keyboard to the console, and I can then drop back to single user mode and complete the installworld, etc. I didn't notice this earlier since all systems I upgraded during the RC cycle had serial consoles which worked fine. From owner-freebsd-amd64@FreeBSD.ORG Mon May 15 15:40: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 9511C16A41A for ; Mon, 15 May 2006 15:40:06 +0000 (UTC) (envelope-from raf.ponsaerts@med.kuleuven.be) Received: from thumbler.kulnet.kuleuven.ac.be (thumbler.kulnet.kuleuven.ac.be [134.58.240.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC07443D48 for ; Mon, 15 May 2006 15:40:05 +0000 (GMT) (envelope-from raf.ponsaerts@med.kuleuven.be) Received: from localhost (localhost [127.0.0.1]) by thumbler.kulnet.kuleuven.ac.be (Postfix) with ESMTP id 9C7011381B1; Mon, 15 May 2006 17:40:04 +0200 (CEST) Received: from smtp03.kuleuven.be (antonius.kulnet.kuleuven.ac.be [134.58.240.73]) by thumbler.kulnet.kuleuven.ac.be (Postfix) with ESMTP id CFDFA13817C; Mon, 15 May 2006 17:40:00 +0200 (CEST) Received: from smtp03.kuleuven.be (localhost.localdomain [127.0.0.1]) by smtp03.kuleuven.be (Postfix) with ESMTP id 96C5B33278E; Mon, 15 May 2006 17:39:57 +0200 (CEST) Received: from BSD-amd64.med.ad10.intern.kuleuven.be (pc-10-33-121-105.med.kuleuven.ac.be [10.33.121.105]) by smtp03.kuleuven.be (Postfix) with ESMTP id 7DD51332792; Mon, 15 May 2006 17:39:57 +0200 (CEST) From: raf ponsaerts To: Scot Hetzel In-Reply-To: <790a9fff0605150633l4639d970q4bfe7545ed559ba@mail.gmail.com> References: <1147699246.49891.12.camel@BSD-amd64.med.ad10.intern.kuleuven.be> <790a9fff0605150633l4639d970q4bfe7545ed559ba@mail.gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-BLuIdtm25QPN+EN5rGEe" Organization: KULeuven Date: Mon, 15 May 2006 17:39:58 +0200 Message-Id: <1147707598.49891.32.camel@BSD-amd64.med.ad10.intern.kuleuven.be> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port X-Virus-Scanned: by KULeuven Antivirus Cluster Cc: freebsd-amd64@freebsd.org Subject: Re: broadcom (bcm4319) wireless card on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: raf.ponsaerts@med.kuleuven.be List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 May 2006 15:40:06 -0000 --=-BLuIdtm25QPN+EN5rGEe Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Thanks a lot for the info ! but I can't find any attachment (gmail might not have passed it through) another thing I like to share : Loading the 32-bit module apparently gave me a "fatal trap 12" kernel error. I already have tried a XP 64-bit driver and modified the .inf file (after converting it to ascii) and kept only the following line (I just removed the lines for other cards) : %BCM430M_DeviceDesc% =3D BCM43XM2, PCI\VEN_14E4&DEV_4319&SUBSYS_1359103C =3D>building the 64-bit module with ndiscvt in /sys/modules/if_ndis went flawless! (I cannot build it with ndisgen) =3D>loading the module was no problem =3D>However, I still can't see a wireless interface with ifconfig maybe your 64-bit drivers give me a better result ! So, can you please post me the .inf and .sys files. They might not be blocked via mail services. Thanks for your support !!! Raf On Mon, 2006-05-15 at 08:33 -0500, Scot Hetzel wrote: > On 5/15/06, raf ponsaerts wrote: > > I've already posted this message to "FreeBSD-Questions", about 2 days > > ago. I got no response ... maybe someone on this list has any idea... > > My appologies for posting twice and being impatient. > > > > > hi all, > > > > > > I have a new laptop which runs on FreeBSD6.1beta-amd64 (Turion64 > > > ML-34). > > > > > > The only problem I have is getting the wireless interface up. > > > > > > none3@pci6:2:0: class=3D0x028000 card=3D0x1359103c chip=3D0x431914e4 > > > rev=3D0x02 > > > hdr=3D0x00 > > > vendor =3D 'Broadcom Corporation' > > > class =3D network > > > > > > It seems to me I need a driver which supports bcm4319. > > > I read about the unwillingness of broadcom to support the development > > > of > > > a native FreeBSD-driver. > > > > > > I am aware of the "Evil project" and the "ndisgen" tool. So, I used > > > WinXP drivers > > > (bcmwl5.inf, bcmwl5.sys) to build a module, which loads without any > > > comment. > > > > > > However, ifconfig does not show the wireless interface ... > > > > > > When I take a look at the ndiswrapper-list, I see that such cards wor= k > > > on linux-amd64. > > > > > > Does anyone know a way to get past this problem? > > > Does bcmwl5.inf needs some tweaking? > > > > You need the Broadcom ndis 64bit driver from Windows XP/64. The one > you used was a 32bit driver. >=20 > I have attached the 64bit ndis driver for the Broadcom Wireless. I > don't remember where I originally obtained it from. >=20 > Scot >=20 > NOTE: 80211g.zp is actually a .zip file, renamed extension to get > around gmail zip file protection. >=20 > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" --=-BLuIdtm25QPN+EN5rGEe Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBEaKDOwoS2GihjEx8RAgdfAKC2F44cKAYNG5VaZIic/0E3+WqNbgCfbFD8 Bt0pmnpOlgLjG+2DcvSP1Uk= =Xtsl -----END PGP SIGNATURE----- --=-BLuIdtm25QPN+EN5rGEe-- From owner-freebsd-amd64@FreeBSD.ORG Mon May 15 21:37: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 EB3DD16BC1D for ; Mon, 15 May 2006 21:37:53 +0000 (UTC) (envelope-from gabor.kovesdan@t-hosting.hu) Received: from server.t-hosting.hu (server.t-hosting.hu [217.20.133.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2212043D49 for ; Mon, 15 May 2006 21:37:53 +0000 (GMT) (envelope-from gabor.kovesdan@t-hosting.hu) Received: from localhost (localhost [127.0.0.1]) by server.t-hosting.hu (Postfix) with ESMTP id B38E9998F2B; Mon, 15 May 2006 23:37:51 +0200 (CEST) X-Virus-Scanned: amavisd-new at t-hosting.hu Received: from server.t-hosting.hu ([127.0.0.1]) by localhost (server.t-hosting.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id TnNvS+wa-WHB; Mon, 15 May 2006 23:37:47 +0200 (CEST) Received: from [192.168.2.186] (catv-5062e7e3.catv.broadband.hu [80.98.231.227]) by server.t-hosting.hu (Postfix) with ESMTP id E23EF998F23; Mon, 15 May 2006 23:37:46 +0200 (CEST) Message-ID: <4468F4A7.9080205@t-hosting.hu> Date: Mon, 15 May 2006 23:37:43 +0200 From: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: "Julian H. Stacey" References: <200605151213.k4FCDcBm081238@fire.jhs.private> In-Reply-To: <200605151213.k4FCDcBm081238@fire.jhs.private> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: Running i386 binaries on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 May 2006 21:37:55 -0000 Julian H. Stacey wrote: > =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= wrote: > >> Julian H. Stacey wrote: >> >>> gabor.kovesdan@t-hosting.hu wrote: >>> >>> >>>> either, you have to get the RELENG_6_1 >>>> >>>> >>> RELENG_6_1 is for stable beyond, which jim might not want, >>> to match release if uname -r == 6.1-RELEASE : RELENG_6_1_0_RELEASE >>> >>> >> RELENG_6_1 is *not* for stable, RELENG_6 is for stable. >> > > Yes. > (Tricky word stable, I know what you mean, but I've also > seen so called stable that was quite unstable on occasion > way back, when one was ill advised to track beyond fixes > for the specific release that was really `stable' in the > real normal non BSD sense of the word, not some > inter-release-hopefully-maybe-but-sometime-not-stable thing ;-) > > >> RELENG_6_1 is >> the security branch for 6.1-RELEASE, >> > > Yes. > (& thus more stable (in the real sense of the word) & > invariant than the inter-release progressive RELENG_6 that > FreeBSD names as 'Stable') > > >> this should be used instead of >> RELENG_6_1_1_RELEASE. >> > > "Could" Yes, "Should" No. Not always. It's a matter of personal > requirement that we are not qualified to dictate to others. Some > few people may _really_ _want_ exactly the release for their own > very good reasons eg QA stamped, part of embedded systems with > expected & tested & timed repose, relied on to interact exactly as > expected, or more bluntly, simply 'cos they've been told they'll > be fired & or imprisoned (eg if in military or high rel. sytems), > if they change an authorised code base without authority. > > > IMHO, that's a very special case. Aside from these kinds of licensing hurdles you mentioned as a special example, I still think that the security branch should be used. Only very slight changes go to RELENG_6_1 that don't cause functional changes. Using RELENG_6_1_0_RELEASE anyway is like buying a two-day bread instead of the fresh one. The security branch offers the same functionality and *quality* that the original release, so imho the other points you listed make no sense. I really don't want to flame about this, but I'm curious what others think about this topic, because I'm very convinced that the use of the release tag is strongly discouraged after the release. If a security hole is recognized why one might not want to patch it? Gabor Kovesdan From owner-freebsd-amd64@FreeBSD.ORG Tue May 16 04:22:20 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 4B9A816A400 for ; Tue, 16 May 2006 04:22:20 +0000 (UTC) (envelope-from ukki@savot.org) Received: from netbox.wsoy.fi (netbox.wsoy.fi [193.208.165.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CE2743D45 for ; Tue, 16 May 2006 04:22:18 +0000 (GMT) (envelope-from ukki@savot.org) Received: from hki.wsoy.fi ([193.208.165.10]) by netbox.wsoy.fi with Microsoft SMTPSVC(6.0.3790.1830); Tue, 16 May 2006 07:22:15 +0300 Received: from savo.wsoy.fi (savo.wsoy.fi [192.89.52.130]) by hki.wsoy.fi (8.12.8/8.12.5) with ESMTP id k4G4MGiW021544; Tue, 16 May 2006 07:22:17 +0300 Received: from [192.89.52.134] ([192.89.52.134]) by savo.wsoy.fi (Lotus Domino Release 5.0.13a) with ESMTP id 2006051607244029:3524 ; Tue, 16 May 2006 07:24:40 +0300 From: Janne =?iso-8859-15?q?M=E4kinen?= To: raf.ponsaerts@med.kuleuven.be Date: Tue, 16 May 2006 07:23:20 +0300 User-Agent: KMail/1.9.1 References: <1147699246.49891.12.camel@BSD-amd64.med.ad10.intern.kuleuven.be> <790a9fff0605150633l4639d970q4bfe7545ed559ba@mail.gmail.com> <1147707598.49891.32.camel@BSD-amd64.med.ad10.intern.kuleuven.be> In-Reply-To: <1147707598.49891.32.camel@BSD-amd64.med.ad10.intern.kuleuven.be> MIME-Version: 1.0 Message-Id: <200605160723.20903.ukki@savot.org> X-MIMETrack: Itemize by SMTP Server on savo/WSOY/fi(Release 5.0.13a |April 8, 2004) at 16.05.2006 07:24:40, Serialize by Router on savo/WSOY/fi(Release 5.0.13a |April 8, 2004) at 16.05.2006 07:24:42, Serialize complete at 16.05.2006 07:24:42 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-6" Content-Disposition: inline X-OriginalArrivalTime: 16 May 2006 04:22:15.0616 (UTC) FILETIME=[4FD5F400:01C678A0] Cc: freebsd-amd64@freebsd.org Subject: Re: broadcom (bcm4319) wireless card on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 May 2006 04:22:20 -0000 On Monday 15 May 2006 18:39, raf ponsaerts wrote: > Thanks a lot for the info ! > > but I can't find any attachment (gmail might not have passed it through) > > another thing I like to share : > Loading the 32-bit module apparently gave me a "fatal trap 12" kernel > error. > > I already have tried a XP 64-bit driver and modified the .inf file > (after converting it to ascii) and kept only the following line (I just > removed the lines for other cards) : > %BCM430M_DeviceDesc% = BCM43XM2, PCI\VEN_14E4&DEV_4319&SUBSYS_1359103C > > > =>building the 64-bit module with ndiscvt in /sys/modules/if_ndis went > flawless! (I cannot build it with ndisgen) > =>loading the module was no problem > =>However, I still can't see a wireless interface with ifconfig > > maybe your 64-bit drivers give me a better result ! > > So, can you please post me the .inf and .sys files. They might not be > blocked via mail services. > > Thanks for your support !!! If I'm not mistaken, my laptop uses the same wireless, so this page might help you: http://savot.org/ukki/freebsd/ From owner-freebsd-amd64@FreeBSD.ORG Tue May 16 09:19: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 8710716A58A for ; Tue, 16 May 2006 09:19:31 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99D9D43D58 for ; Tue, 16 May 2006 09:19:30 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (naxydi@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k4G9JNXT097933 for ; Tue, 16 May 2006 11:19:28 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k4G9JNlR097932; Tue, 16 May 2006 11:19:23 +0200 (CEST) (envelope-from olli) Date: Tue, 16 May 2006 11:19:23 +0200 (CEST) Message-Id: <200605160919.k4G9JNlR097932@lurza.secnetix.de> From: Oliver Fromme To: freebsd-amd64@FreeBSD.ORG In-Reply-To: <4468F4A7.9080205@t-hosting.hu> X-Newsgroups: list.freebsd-amd64 User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) 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-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 16 May 2006 11:19:28 +0200 (CEST) Cc: Subject: Re: Running i386 binaries on 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, 16 May 2006 09:19:32 -0000 Kövesdán Gábor wrote: > I really don't want to flame about this, but I'm curious what others > think about this topic, because I'm very convinced that the use of the > release tag is strongly discouraged after the release. I tend to agree. The original poster wrote that he already has 6.1-Release installed, so "upgrading" with RELENG_6_1_0_RELEASE doen't make sense at all, because it won't change a bit. Staying with the release tag might be en highly dangerous. Look at the CERT advisories that have been published since 6.0 has been release. All of them have been addressed in RELENG_6_0. It is therefore a good thing to give the generic advice to follow RELENG_6_X (where X is now 1). Of course, there are always very special cases with very special requirements. But those are in the minority, and people having those requirements know very well themselves what tag they should use for upgrading (if upgrading is possible at all). Those should not prevent us from giving the general good advice of following the security branch, or even the RELENG_6 "stable" branch if critical fixes (not security-related) are an issue, too. (Personally I'm running RELENG_6 on my machine at home since it started to exist about one year ago, updating every few weeks, with zero problems.) By the way: There are also security holes which affect machines that are _not_ connected to the internet, for example the recently discovered FPU state bug on AMD processors, or the information leak on hyperthreading (intel) processors. Both of them can be exploited so that processes can obtain priviledged information, or even gain increased priviledges. Of course, there might be machines where it doesn't matter if every process can have root priviledges. But that's certainly not very common. If you run a UNIX system, you usually want to take advantage of having different users and groups, and maybe even advanced features such as the new MAC labels and policies. Just my 2 cents. Best regards Oliver PS: Uhm ... Shouldn't this be redirected to freebsd-chat? -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "Python is an experiment in how much freedom programmers need. Too much freedom and nobody can read another's code; too little and expressiveness is endangered." -- Guido van Rossum From owner-freebsd-amd64@FreeBSD.ORG Tue May 16 09:34:57 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 8C7EC16A417 for ; Tue, 16 May 2006 09:34:57 +0000 (UTC) (envelope-from raf.ponsaerts@med.kuleuven.be) Received: from nibbel.kulnet.kuleuven.ac.be (nibbel.kulnet.kuleuven.ac.be [134.58.240.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8957A43D58 for ; Tue, 16 May 2006 09:34:52 +0000 (GMT) (envelope-from raf.ponsaerts@med.kuleuven.be) Received: from localhost (localhost [127.0.0.1]) by nibbel.kulnet.kuleuven.ac.be (Postfix) with ESMTP id 5A3234D0BC; Tue, 16 May 2006 11:34:51 +0200 (CEST) Received: from smtp02.kuleuven.be (lepidus.kulnet.kuleuven.ac.be [134.58.240.72]) by nibbel.kulnet.kuleuven.ac.be (Postfix) with ESMTP id A2B604CE8E; Tue, 16 May 2006 11:34:50 +0200 (CEST) Received: from smtp02.kuleuven.be (localhost.localdomain [127.0.0.1]) by smtp02.kuleuven.be (Postfix) with ESMTP id 7AB822CAB10; Tue, 16 May 2006 11:34:50 +0200 (CEST) Received: from BSD-amd64.ad10.med.intern.kuleuven.be (pc-10-33-121-105.med.kuleuven.ac.be [10.33.121.105]) by smtp02.kuleuven.be (Postfix) with ESMTP id 5E4212CAB0E; Tue, 16 May 2006 11:34:50 +0200 (CEST) From: raf ponsaerts To: Janne =?ISO-8859-1?Q?M=E4kinen?= In-Reply-To: <200605160723.20903.ukki@savot.org> References: <1147699246.49891.12.camel@BSD-amd64.med.ad10.intern.kuleuven.be> <790a9fff0605150633l4639d970q4bfe7545ed559ba@mail.gmail.com> <1147707598.49891.32.camel@BSD-amd64.med.ad10.intern.kuleuven.be> <200605160723.20903.ukki@savot.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-ItKYil+ncNjtPCw9vKJ6" Organization: KULeuven Date: Tue, 16 May 2006 11:33:49 +0200 Message-Id: <1147772029.12060.10.camel@BSD-amd64.ad10.med.intern.kuleuven.be> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port X-Virus-Scanned: by KULeuven Antivirus Cluster Cc: freebsd-amd64@freebsd.org Subject: Re: broadcom (bcm4319) wireless card on amd64 : SOLVED X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: raf.ponsaerts@med.kuleuven.be List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 May 2006 09:34:59 -0000 --=-ItKYil+ncNjtPCw9vKJ6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, apparently I haven't posted the message 'problem solved' to the list. I did not try the driver which is linked to your page (@savot.org). The .inf file is an older version and the file does not contain specifications for my hardware. I'm not saying it might not work (with a little tweaking). Indeed, a lot of hardware on the HP zv6000 seems to match. I'm using a HP dv5075EA (I just wanted a 64-bit notebook). Anyway, I thank you for your commitment and I'm happy the driver provided by Scot works correctly ! Greetzzz Raf > YES !!! >=20 > Your 64-bit driver works !!! (I changed 4318 to 4319 in the ascii > conversion, but I don't know if that was really required) >=20 > and yes, I only read the copy you have sent to the mailing list. > So, In fact the direct mail towards me did contain the attachment ! >=20 > Thanks a lot, Scot ! You made my day. >=20 > You 'mailing-list' guys rule supreme=20 >=20 > Raf On Tue, 2006-05-16 at 07:23 +0300, Janne M=E4kinen wrote: > On Monday 15 May 2006 18:39, raf ponsaerts wrote: > > Thanks a lot for the info ! > > > > but I can't find any attachment (gmail might not have passed it through= ) > > > > another thing I like to share : > > Loading the 32-bit module apparently gave me a "fatal trap 12" kernel > > error. > > > > I already have tried a XP 64-bit driver and modified the .inf file > > (after converting it to ascii) and kept only the following line (I just > > removed the lines for other cards) : > > %BCM430M_DeviceDesc% =3D BCM43XM2, PCI\VEN_14E4&DEV_4319&SUBSYS_1359103= C > > > > > > =3D>building the 64-bit module with ndiscvt in /sys/modules/if_ndis wen= t > > flawless! (I cannot build it with ndisgen) > > =3D>loading the module was no problem > > =3D>However, I still can't see a wireless interface with ifconfig > > > > maybe your 64-bit drivers give me a better result ! > > > > So, can you please post me the .inf and .sys files. They might not be > > blocked via mail services. > > > > Thanks for your support !!! >=20 > If I'm not mistaken, my laptop uses the same wireless, so this page might= help=20 > you: http://savot.org/ukki/freebsd/ >=20 --=-ItKYil+ncNjtPCw9vKJ6 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBEaZx9woS2GihjEx8RAqUeAJ0cr0s/Jj/AyfCFDxL2aYQ/74OwlQCgvSz1 cPWJLOBpJuXzj9b9LCsXugA= =SFiQ -----END PGP SIGNATURE----- --=-ItKYil+ncNjtPCw9vKJ6-- From owner-freebsd-amd64@FreeBSD.ORG Tue May 16 09:50:28 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 EACF016A413 for ; Tue, 16 May 2006 09:50:28 +0000 (UTC) (envelope-from andrej@antiszoc.hu) Received: from andrej.mine.nu (catv-d5debe68.catv.broadband.hu [213.222.190.104]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66E1B43D5C for ; Tue, 16 May 2006 09:50:27 +0000 (GMT) (envelope-from andrej@antiszoc.hu) Message-ID: <4469A10D.20003@antiszoc.hu> Date: Tue, 16 May 2006 11:53:17 +0200 From: Andras Got User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.2) Gecko/20060404 SeaMonkey/1.0.1 MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: possible tcp problem X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 May 2006 09:50:29 -0000 Hi, I'm using freebsd 6.1 and _sometimes_ (one for every ~30-40 minutes) I get mysql connect errors with permission denied. The mysql_connect returns error code 1, which is permission denied. The same happed to me when i tried to open a tcp connection between jails and it wasn't mysql related. The same happened sometimes this dawn with a sendmail host lookup. On the console I got the permission denied. I don't really know what could cause this, but it's like a buffer gets full. I use pf for filtering and nat. I checked pfctl -si which says there are ~800-1000 states, so it's well below the max 10000. The question is that what could cause this thing and what should we try. Errors: sendmail[37085]: gethostbyaddr(IP) failed: 1 Can't connect to MySQL server on 'IP' (1) netstat -m 298/812/1110 mbufs in use (current/cache/total) 286/396/682/25600 mbuf clusters in use (current/cache/total/max) 286/322 mbuf+clusters out of packet secondary zone in use (current/cache) 0/0/0/0 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/0 9k jumbo clusters in use (current/cache/total/max) 0/0/0/0 16k jumbo clusters in use (current/cache/total/max) 646K/995K/1641K bytes allocated to network (current/cache/total) 65610/107271/98848 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/0/0 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 45726 requests for I/O initiated by sendfile 118 calls to protocol drain routines Regards, Andras From owner-freebsd-amd64@FreeBSD.ORG Tue May 16 10:38:18 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 2044D16A40A for ; Tue, 16 May 2006 10:38:18 +0000 (UTC) (envelope-from jhs@flat.berklix.net) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70DB943D49 for ; Tue, 16 May 2006 10:38:17 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A63B9.dip.t-dialin.net [84.154.99.185]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id k4GAcE7V059072; Tue, 16 May 2006 12:38:15 +0200 (CEST) (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 k4GAcClV013314; Tue, 16 May 2006 12:38:13 +0200 (CEST) (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 k4GAe5An093400; Tue, 16 May 2006 12:40:05 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200605161040.k4GAe5An093400@fire.jhs.private> To: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= In-Reply-To: Message from =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= of "Mon, 15 May 2006 23:37:43 +0200." <4468F4A7.9080205@t-hosting.hu> Date: Tue, 16 May 2006 12:40:05 +0200 From: "Julian H. Stacey" Cc: freebsd-amd64@freebsd.org Subject: Re: Running i386 binaries on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 May 2006 10:38:18 -0000 > IMHO, that's a very special case. Aside from these kinds of licensing Not licensing. > hurdles you mentioned as a special example, I still think that the > security branch should be used. Only very slight changes go to > RELENG_6_1 that don't cause functional changes. Using > RELENG_6_1_0_RELEASE anyway is like buying a two-day bread instead of > the fresh one. The security branch offers the same functionality and > *quality* that the original release, so imho the other points you listed > make no sense. > > I really don't want to flame about this, but I'm curious what others > think about this topic, because I'm very convinced that the use of the > release tag is strongly discouraged after the release. If a security > hole is recognized why one might not want to patch it? NO ! The original questioner has read what we're agreed the tags will deliver. He's informed, We're Done - Finished ! Expounding what tags all should use, would be arrogance in ignorance: Not all systems are trivial, some have Strict code control authorisation procedures: eg a warship system that embeds DOS, Win-XP & Linux - Shudder!, BSD systems that get used in other `interesting' places. Firewall manufacturers integrating BSD. Less stringent applications like banking will also have managers who must sign off before _Any_ code change is allowed. Which CVS tags you urge is Not amd64 specific, so to discuss it, please on an all architectures list, eg chat@ -- Julian Stacey. Consultant Unix Net & Sys. Eng., Munich. http://berklix.com From owner-freebsd-amd64@FreeBSD.ORG Tue May 16 10:50:16 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 D875516A405 for ; Tue, 16 May 2006 10:50:16 +0000 (UTC) (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 3007943D48 for ; Tue, 16 May 2006 10:50:16 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k4GAoGaN080924 for ; Tue, 16 May 2006 10:50:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k4GAoFBJ080920; Tue, 16 May 2006 10:50:15 GMT (envelope-from gnats) Resent-Date: Tue, 16 May 2006 10:50:15 GMT Resent-Message-Id: <200605161050.k4GAoFBJ080920@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, Jonatan Cerri Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A03B16A402 for ; Tue, 16 May 2006 10:43:20 +0000 (UTC) (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 3534F43D48 for ; Tue, 16 May 2006 10:43: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 k4GAhKnf030933 for ; Tue, 16 May 2006 10:43:20 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id k4GAhJAA030932; Tue, 16 May 2006 10:43:19 GMT (envelope-from nobody) Message-Id: <200605161043.k4GAhJAA030932@www.freebsd.org> Date: Tue, 16 May 2006 10:43:19 GMT From: Jonatan Cerri To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/97337: xorg reboots system if dri module is enabled X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 May 2006 10:50:17 -0000 >Number: 97337 >Category: amd64 >Synopsis: xorg reboots system if dri module is enabled >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue May 16 10:50:15 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Jonatan Cerri >Release: 6.1-RELENG/amd64 >Organization: student >Environment: FreeBSD 6.1-RELEASE FreeBSD 6.1-RELEASE #2: Mon May 15 17:54:15 CEST 2006 root@:/usr/src/sys/amd64/compile/MINE amd64 >Description: Using supported VGA-Card (ATI Radeon 9250 PCI), which is recognized at boot time, starting Xorg reboots the machine ungracefully, if the dri-module is uncommented in xorg.conf. This is the case in the default xorg configuration file generated with Xorg -configure. Commenting the line 'load "dri"' in the section "Module" of xorg.conf makes the problem go away. The card worked with dri hardware acceleration in a previous FreeBSD/i386 installation on a different mainboard/cpu. The Problem started when changing the mainboard and CPU. Current CPU is Pentium D 805, current Board is Asrock 775Dual-880Pro with VIA PT880Pro Chipset and 1GB DDRII Ram in dualchannel configuration. Output of dmesg |grep drm: drm0: port 0xe000-0xe0ff mem 0xd8000000-0xdfffffff,0xff6f0000-0xff6fffff irq 17 at device 9.0 on pci0 info: [drm] Initialized radeon 1.19.0 20050911 drm0: port 0xe000-0xe0ff mem 0xd8000000-0xdfffffff,0xff6f0000-0xff6fffff irq 17 at device 9.0 on pci0 info: [drm] Initialized radeon 1.19.0 20050911 'device agp' was removed from the kernel. the kernel runs with the new scheduler, but the problem persists when running with the old 4BSD scheduler. >How-To-Repeat: Install 6.1-RELEASE with bundled Xorg. Execute startx using xorg.conf with line 'load "dri"' in the section "Module". >Fix: Comment line 'load "dri"' in the section "Module" in xorg.conf. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Tue May 16 15:20: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 6AD1016A696 for ; Tue, 16 May 2006 15:20:33 +0000 (UTC) (envelope-from m0rf@mail.cz) Received: from pecka.reflektor.cz (pecka.reflektor.cz [82.208.4.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BB0443D48 for ; Tue, 16 May 2006 15:20:19 +0000 (GMT) (envelope-from m0rf@mail.cz) Received: from localhost (localhost [127.0.0.1]) by pecka.reflektor.cz (Postfix) with ESMTP id ADE87D0451; Tue, 16 May 2006 17:20:48 +0200 (CEST) Received: from pecka.reflektor.cz ([127.0.0.1]) by localhost (pecka.reflektor.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20203-07; Tue, 16 May 2006 17:20:48 +0200 (CEST) Received: from [192.168.1.1] (jezibaba.ariga.cz [194.213.62.10]) by pecka.reflektor.cz (Postfix) with ESMTP id 53CFFCF3DA for ; Tue, 16 May 2006 17:20:48 +0200 (CEST) Message-ID: <4469EDB4.70008@mail.cz> Date: Tue, 16 May 2006 17:20:20 +0200 From: m0rf User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at mail.cz Subject: Re: amd64/95554: undetected sata drive on 6.1, detected on 6.0 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 May 2006 15:20:37 -0000 I have same problem on FreeBSD (6.0, 6.1, 7.0) with 3 SATA disks Seagate Barracuda ST3120813AS on mother board Gigabyte K8N51PVMT-9 - GF6150. While booting system don't recognize one disk which is in or out of SATA array. I tried boot DragonFlyBSD which have FreeBSD 5.4 kernel and all disks was detected successfully... dmesg (dragon fly founded once more disk with device name ad10): Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 7.0-CURRENT #0: Sat Apr 29 06:45:21 CEST 2006 root@:/usr/obj/usr/src/sys/GENERIC WARNING: WITNESS option enabled, expect reduced performance. ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3700+ (2210.08-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20f71 Stepping = 1 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800 AMD Features2=0x1 usable memory = 994975744 (948 MB) avail memory = 958840832 (914 MB) ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 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_bus_number: can't get _ADR acpi_bus_number: can't get _ADR cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.0 (no driver attached) pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 0.5 (no driver attached) pci0: at device 0.6 (no driver attached) pci0: at device 0.7 (no driver attached) vgapci0: mem 0xf2000000-0xf2ffffff,0xe0000000-0xefffffff,0xf3000000-0xf3ffffff irq 16 at device 5.0 on pci0 pci0: at device 9.0 (no driver attached) isab0: at device 10.0 on pci0 isa0: on isab0 pci0: at device 10.1 (no driver attached) pci0: at device 10.2 (no driver attached) ohci0: mem 0xf5108000-0xf5108fff irq 21 at device 11.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 8 ports with 8 removable, self powered ehci0: mem 0xf5104000-0xf51040ff irq 22 at device 11.1 on pci0 ehci0: [GIANT-LOCKED] usb1: EHCI version 1.0 usb1: companion controller, 8 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: on usb1 uhub1: 8 ports with 8 removable, self powered atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 13.0 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd800-0xd80f mem 0xf5107000-0xf5107fff irq 23 at device 14.0 on pci0 ata2: on atapci1 ata3: on atapci1 atapci2: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xc400-0xc40f mem 0xf5106000-0xf5106fff irq 20 at device 15.0 on pci0 ata4: on atapci2 ata5: on atapci2 pcib1: at device 16.0 on pci0 pci1: on pcib1 fwohci0: port 0xa000-0xa07f mem 0xf5000000-0xf50007ff irq 18 at device 14.0 on pci1 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:00:14:85:00:3b:53:a5 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:00:14:3b:53:a5 fwe0: Ethernet address: 02:00:14:3b:53:a5 fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) pci0: at device 16.1 (no driver attached) nve0: port 0xb000-0xb007 mem 0xf5105000-0xf5105fff irq 22 at device 20.0 on pci0 nve0: Ethernet address 00:14:85:3f:14:e3 miibus0: on nve0 ciphy0: on miibus0 ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto nve0: Ethernet address: 00:14:85:3f:14:e3 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 sio0: [FAST] ppc0: port 0x378-0x37f,0x778-0x77b irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 orm0: at iomem 0xd0000-0xd3fff pnpid ORM0000 on isa0 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 Timecounter "TSC" frequency 2210075853 Hz quality 800 Timecounters tick every 1.000 msec module_register_init: MOD_LOAD (amr_linux, 0xffffffff8061f040, 0) error 6 acd0: DVDR at ata0-master UDMA33 ad4: 114472MB at ata2-master SATA150 ad8: 114472MB at ata4-master SATA150 Trying to mount root from ufs:/dev/ad4s2a atacontrol: ATA channel 0: Master: acd0 ATA/ATAPI revision 5 Slave: no device present ATA channel 1: no devices ATA channel 2: Master: ad4 Serial ATA v1.0 Slave: no device present ATA channel 3: no devices ATA channel 4: Master: ad8 Serial ATA v1.0 Slave: no device present ATA channel 5: no devices From owner-freebsd-amd64@FreeBSD.ORG Tue May 16 17:52: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 171F816A786 for ; Tue, 16 May 2006 17:52:31 +0000 (UTC) (envelope-from andriy@whitebox.color-pro.com) Received: from whitebox.color-pro.com (ip.82.144.202.13.stat-3.volia.net [82.144.202.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C62A43D7B for ; Tue, 16 May 2006 17:52:29 +0000 (GMT) (envelope-from andriy@whitebox.color-pro.com) Received: from krimsonbox.color-pro.in ([192.168.1.98]) by whitebox.color-pro.com (8.11.1/8.11.1) with ESMTP id k4GHqIn67444; Tue, 16 May 2006 20:52:18 +0300 (EEST) (envelope-from andriy@whitebox.color-pro.com) Date: Tue, 16 May 2006 20:52:12 +0300 To: m0rf , freebsd-amd64@freebsd.org From: "Andriy Podanenko" Organization: Color Pro Prepress Studio Content-Type: text/plain; format=flowed; delsp=yes; charset=koi8-u MIME-Version: 1.0 References: <4469EDB4.70008@mail.cz> Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <4469EDB4.70008@mail.cz> User-Agent: Opera Mail(BETA2)/9.00 (Win32) Cc: Subject: Re: amd64/95554: undetected sata drive on 6.1, detected on 6.0 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: andriy@whitebox.color-pro.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 May 2006 17:52:32 -0000 Tue, 16 May 2006 18:20:20 +0300, m0rf ÐÉÓÁ×: > I have same problem on FreeBSD (6.0, 6.1, 7.0) with 3 SATA disks Seagate > Barracuda ST3120813AS on mother board Gigabyte K8N51PVMT-9 - GF6150. > While booting system don't recognize one disk which is in or out of SATA > array. I tried boot DragonFlyBSD which have FreeBSD 5.4 kernel and all > disks was detected successfully... I have the same problem but Asus A8N-E Motherboard 3 Seagate 120GB 7200.9 SATA drives and one of them sometimes lost by system mount command with system panic.. savecore - lost system mount atacontrol (init detach rescan) can`t help/// only reboot (with power off) -- ---------------- Andriy Podanenko -podarok- PAK-UANIC ICQ 125123884 YahooIM podarok_ua MSN podarok_ Jabber podarok@jabber.org AIM podarokua From owner-freebsd-amd64@FreeBSD.ORG Wed May 17 23:17:28 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 D290116AA76 for ; Wed, 17 May 2006 23:17:28 +0000 (UTC) (envelope-from igorr@speechpro.com) Received: from speechpro.ru (speech-tech-2.ip.PeterStar.net [81.3.190.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62C2643D45 for ; Wed, 17 May 2006 23:17:28 +0000 (GMT) (envelope-from igorr@speechpro.com) Received: from [192.168.2.26] (helo=sysadm.stc) by s1.stc with esmtp (Exim 4.53 (FreeBSD)) id 1FgVGg-000HfK-6A for freebsd-amd64@freebsd.org; Thu, 18 May 2006 03:17:26 +0400 Received: from localhost.stc ([127.0.0.1] helo=sysadm.stc) by sysadm.stc with esmtp (Exim 4.62 (FreeBSD)) (envelope-from ) id 1FgV1t-000IAj-Uk for freebsd-amd64@freebsd.org; Thu, 18 May 2006 03:02:10 +0400 Received: (from igorr@localhost) by sysadm.stc (8.13.6/8.13.6/Submit) id k4GAZTHq047963 for freebsd-amd64@freebsd.org; Tue, 16 May 2006 14:35:29 +0400 (MSD) (envelope-from igorr) Date: Tue, 16 May 2006 14:35:29 +0400 From: Igor Robul To: freebsd-amd64@freebsd.org Message-ID: <20060516103529.GD383@sysadm.stc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 X-Archived: Yes Subject: Success report of 6.1 on Tyan S2865 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 May 2006 23:17:28 -0000 Hello, normaly I dont write success reports :-) But I wish to say big "Thank You" to all FreeBSD developers, and to developers o AMD64 port, because this was my first installation of FreeBSD to AMD64 (even more, this is my first AMD64 based PC). All devices of Tyan S2865 was recognized by installer, NVidia RAID "just works", nve network card "just works", and even PCI-E ATI X1300 works with "vesa" driver, without 3D :-) but I dont generaly need it. Ports builds are much faster than on P-IV 2.8GHz, some sites, on which firefox 1.5.3 was crashing on i386 now "just work". Firewire and USB are recognized, I have not used them still, sound recognized (but I dont use it at work :-) ) Of course, I have done some research while selecting motherboard, and because it was not for home PC, I was not too limited in cash :-) And now question, can I expect same results on much cheaper motherboard from ASUS? From owner-freebsd-amd64@FreeBSD.ORG Thu May 18 15:02:02 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 403B416A416 for ; Thu, 18 May 2006 15:02:02 +0000 (UTC) (envelope-from michael@apfel.de) Received: from mail.apfel.de (mail.apfel.de [212.12.33.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9657C43D48 for ; Thu, 18 May 2006 15:02:00 +0000 (GMT) (envelope-from michael@apfel.de) Received: from IBM-LAPTOP (kunde-luise.work.de [212.12.35.106] (may be forged)) (authenticated bits=0) by mail.apfel.de (8.13.4/8.12.9) with ESMTP id k4IF1wfB015359 for ; Thu, 18 May 2006 17:01:59 +0200 (CEST) (envelope-from michael@apfel.de) Date: Thu, 18 May 2006 17:01:57 +0200 From: Michael Beckmann To: freebsd-amd64@freebsd.org Message-ID: <7FED3A7BF24B00412A1F91F2@IBM-LAPTOP> X-Mailer: Mulberry/4.0.4 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Asus K8N-DRE motherboard X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 May 2006 15:02:02 -0000 Greetings! Has anyone tried the Asus K8N-DRE motherboard yet? It has NVIDIA nforce Professional 2200 chipset with SATA-II RAID support 2x Broadcom BCM5721 Gigabit PCI-E LAN controllers I wonder if any of that is supported. Searching the mailing list archive led to no results. Thanks, Michael From owner-freebsd-amd64@FreeBSD.ORG Thu May 18 17:05: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 C4D0916A62E for ; Thu, 18 May 2006 17:05:00 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp100.rog.mail.re2.yahoo.com (smtp100.rog.mail.re2.yahoo.com [206.190.36.78]) by mx1.FreeBSD.org (Postfix) with SMTP id 5C96A43D7C for ; Thu, 18 May 2006 17:04:52 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 69591 invoked from network); 18 May 2006 17:04:52 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=rF29suVXDSFSWyCIJAo2p4/IsMOLfH2Sm/gKqFqAIFdh4rTxe0xi7eoscXNQJr1iG+QVEJOLSU0AsgsZX3LH5bGgRPu9mTnayUB0ssQRf+nmj6hdw7MioCwAlchgEKPdLGFGFBtMe/hE86QEZ+YOEhnT+tqR41BgbMoJKH5Gkvs= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp100.rog.mail.re2.yahoo.com with SMTP; 18 May 2006 17:04:52 -0000 Message-ID: <446CA944.9070704@rogers.com> Date: Thu, 18 May 2006 13:05:08 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Michael Beckmann References: <7FED3A7BF24B00412A1F91F2@IBM-LAPTOP> In-Reply-To: <7FED3A7BF24B00412A1F91F2@IBM-LAPTOP> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org Subject: Re: Asus K8N-DRE motherboard X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 May 2006 17:05:02 -0000 Michael Beckmann wrote: > Greetings! > > Has anyone tried the Asus K8N-DRE motherboard yet? It has > > NVIDIA nforce Professional 2200 chipset with SATA-II RAID support > 2x Broadcom BCM5721 Gigabit PCI-E LAN controllers > > I wonder if any of that is supported. Searching the mailing list > archive led to no results. Yes, should work fine. man ata and man bge. From owner-freebsd-amd64@FreeBSD.ORG Thu May 18 17:19: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 A2DB216A88D for ; Thu, 18 May 2006 17:19:51 +0000 (UTC) (envelope-from michael@apfel.de) Received: from mail.apfel.de (mail.apfel.de [212.12.33.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7F2443D53 for ; Thu, 18 May 2006 17:19:50 +0000 (GMT) (envelope-from michael@apfel.de) Received: from IBM-LAPTOP (kunde-luise.work.de [212.12.35.106] (may be forged)) (authenticated bits=0) by mail.apfel.de (8.13.6/8.12.9) with ESMTP id k4IHJlNi002053; Thu, 18 May 2006 19:19:47 +0200 (CEST) (envelope-from michael@apfel.de) Date: Thu, 18 May 2006 19:19:46 +0200 From: Michael Beckmann To: Mike Jakubik Message-ID: <60FF5C35083C87F64C0569B7@IBM-LAPTOP> In-Reply-To: <446CA944.9070704@rogers.com> References: <7FED3A7BF24B00412A1F91F2@IBM-LAPTOP> <446CA944.9070704@rogers.com> X-Mailer: Mulberry/4.0.4 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: freebsd-amd64@freebsd.org Subject: Re: Asus K8N-DRE motherboard X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 May 2006 17:19:55 -0000 Thanks. I will try it then. That should be a screamer with two dual core Opterons 265 or 270. Michael -- Mike Jakubik wrote: > Michael Beckmann wrote: >> Greetings! >> >> Has anyone tried the Asus K8N-DRE motherboard yet? It has >> >> NVIDIA nforce Professional 2200 chipset with SATA-II RAID support >> 2x Broadcom BCM5721 Gigabit PCI-E LAN controllers >> >> I wonder if any of that is supported. Searching the mailing list >> archive led to no results. > > Yes, should work fine. man ata and man bge. From owner-freebsd-amd64@FreeBSD.ORG Fri May 19 00:14:27 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 4AE2516A494 for ; Fri, 19 May 2006 00:14:27 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0853B43D46 for ; Fri, 19 May 2006 00:14:27 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.13.6/8.13.6) with ESMTP id k4J0EQQl068460 for ; Thu, 18 May 2006 17:14:26 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.6/8.13.6/Submit) id k4J0EQtE068459 for freebsd-amd64@freebsd.org; Thu, 18 May 2006 17:14:26 -0700 (PDT) (envelope-from sgk) Date: Thu, 18 May 2006 17:14:26 -0700 From: Steve Kargl To: freebsd-amd64@freebsd.org Message-ID: <20060519001426.GA68381@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: dead keyboard in Xorg X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 May 2006 00:14:28 -0000 I've installed FreeBSD 6.1 release on a Tyan K8SR motherboard and then updated to RELENG_6. I've installed the Xorg 6.9.0 port and fired up the server where the graphics are from the builtin ATI Rage chip. Everything comes up as expected and the ps/2 mouse works. However, the keyboard is dead. I can get an xterm up, give it focus, but typing yields nothing. Killing X reveals a bunch of gibberish on the console (ie., extended ascii characters). I have tried 2 different ps/2 keyboards and two different ps/2 mice. I've enable/disabled the kbdmux and I've set atkbd flags in /boot/device.hints. Nothing has given me a working keyboard. I've also played with numerous xorg.conf files trying to isolate the problem. I'm stuck. Anyone seen this type of problem? -- Steve From owner-freebsd-amd64@FreeBSD.ORG Fri May 19 02:50:19 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 E3FB916A421 for ; Fri, 19 May 2006 02:50:19 +0000 (UTC) (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 53BAF43D49 for ; Fri, 19 May 2006 02:50:19 +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 k4J2oJd3031987 for ; Fri, 19 May 2006 02:50:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k4J2oJP9031986; Fri, 19 May 2006 02:50:19 GMT (envelope-from gnats) Date: Fri, 19 May 2006 02:50:19 GMT Message-Id: <200605190250.k4J2oJP9031986@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "Greg Hamen" Cc: Subject: Re:amd64/97019 : Cannot load the kernel after installation on Supermicro H8DAR-T X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Greg Hamen List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 May 2006 02:50:20 -0000 The following reply was made to PR amd64/97019; it has been noted by GNATS. From: "Greg Hamen" To: bug-followup@FreeBSD.org, haxor777@gmail.com Cc: Subject: Re:amd64/97019 : Cannot load the kernel after installation on Supermicro H8DAR-T Date: Thu, 18 May 2006 19:46:25 -0700 To whom it may concern: Going through some troubleshooting steps with i j hart (ICT Technician) from the Cardinal Newman Catholic School & Community College, I was informed to submit a Followup letting you know that the above problem also applies to the i386 architecture. -=3D-Thanks in Advance -=3D-Greg From owner-freebsd-amd64@FreeBSD.ORG Fri May 19 06:54:52 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 D5E6016A422 for ; Fri, 19 May 2006 06:54:52 +0000 (UTC) (envelope-from Lennart.Sorth@uni-c.dk) Received: from mail.ssi.uni-c.dk (mail.ssi.uni-c.dk [130.228.9.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CF4A43D45 for ; Fri, 19 May 2006 06:54:52 +0000 (GMT) (envelope-from Lennart.Sorth@uni-c.dk) Received: from [172.16.121.2] (ls.ssi.uni-c.dk [172.16.121.2]) by mail.ssi.uni-c.dk (Postfix) with ESMTP id 0C882B864; Fri, 19 May 2006 08:54:51 +0200 (CEST) Message-ID: <446D6B92.5020201@uni-c.dk> Date: Fri, 19 May 2006 08:54:10 +0200 From: Lennart Sorth User-Agent: Thunderbird 1.5 (X11/20060207) MIME-Version: 1.0 To: Steve Kargl , freebsd-amd64@freebsd.org References: <20060519001426.GA68381@troutmask.apl.washington.edu> In-Reply-To: <20060519001426.GA68381@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: dead keyboard in Xorg X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 May 2006 06:54:52 -0000 Steve Kargl wrote: > Anyone seen this type of problem? yes, on my Sony Vaio Z1 6.1-STABLE laptop (i386) On (quite rare) occations - when booting on batteries where the CPU is wrongly detected - I end up with XDM running, and no keyboard. If I don't start xdm during the bootprocess, but let it boot all the way, THEN login as root and starts xdm manually, then it always works fine. You could try this. When booting on batteries, the sys/i386/cpufreq/est.c cannot determine the speed, and my 1700Mhz Centrino becomes a 596Mhz, with speedstepping down to 74Mhz. Maybe this affects timing somewhere, which causes the keyboardproblem. -- Hilsen Lennart.Sorth@uni-c.dk From owner-freebsd-amd64@FreeBSD.ORG Fri May 19 09:40:12 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 A35E016A427 for ; Fri, 19 May 2006 09:40:12 +0000 (UTC) (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 5C7FA43D55 for ; Fri, 19 May 2006 09:40: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 k4J9e9Z2059089 for ; Fri, 19 May 2006 09:40:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k4J9e901059088; Fri, 19 May 2006 09:40:09 GMT (envelope-from gnats) Resent-Date: Fri, 19 May 2006 09:40:09 GMT Resent-Message-Id: <200605190940.k4J9e901059088@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, Luke Jee Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2130D16A41F for ; Fri, 19 May 2006 09:36:50 +0000 (UTC) (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 B5D9A43D46 for ; Fri, 19 May 2006 09:36:49 +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 k4J9andS028458 for ; Fri, 19 May 2006 09:36:49 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id k4J9anLn028453; Fri, 19 May 2006 09:36:49 GMT (envelope-from nobody) Message-Id: <200605190936.k4J9anLn028453@www.freebsd.org> Date: Fri, 19 May 2006 09:36:49 GMT From: Luke Jee To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/97489: nForce 410 ATA controller dma time out X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 May 2006 09:40:12 -0000 >Number: 97489 >Category: amd64 >Synopsis: nForce 410 ATA controller dma time out >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: Fri May 19 09:40:08 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Luke Jee >Release: 6.0 release >Organization: Prevantage Corporation >Environment: FreeBSD safari.prevantage.com 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Wed Nov 2 19:07:38 UTC 2005 root@rat.samsco.home:/usr/obj/usr/src/sys/GENERIC amd64 >Description: My Mainboard is ASUS K8N-VM nVidia nForce 410 / Socket 754 after install 6.0 release i get this error messages and ATA controller is marked as generic and works at ATA33 highest. ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=786975 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=52612783 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53412279 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=27027535 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13482191 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53741551 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53365295 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=39128559 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=39134127 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53744495 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=39068239 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=54119055 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=39149199 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=262495 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=39068271 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=262495 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13482191 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=39156347 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=39162447 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=39067567 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=27027535 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53741551 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53802935 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=262463 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=2726799 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=39068079 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=39168527 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53368367 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=54901307 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=3483311 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=2726799 my dmesg is: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-RELEASE #0: Wed Nov 2 19:07:38 UTC 2005 root@rat.samsco.home:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Sempron(tm) Processor 2500+ (1406.41-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20fc2 Stepping = 2 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800,LM,3DNow+,3DNow> real memory = 251396096 (239 MB) avail memory = 226975744 (216 MB) cpu0 on motherboard pcib0: pcibus 0 on motherboard pci0: on pcib0 pci0: at device 0.0 (no driver attached) pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 0.5 (no driver attached) pci0: at device 0.6 (no driver attached) pci0: at device 0.7 (no driver attached) pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 3.0 on pci0 pci2: on pcib2 pcib3: at device 4.0 on pci0 pci3: on pcib3 pci0: at device 5.0 (no driver attached) pci0: at device 9.0 (no driver attached) isab0: at device 10.0 on pci0 isa0: on isab0 pci0: at device 10.1 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 13.0 on pc i0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0xe800-0xe807,0xe480-0xe483,0xe400-0xe407,0xe080-0xe083,0xe000-0xe00f mem 0xfebdf000-0xfebdffff irq 5 at device 14.0 on pci0 ata2: on atapci1 ata3: on atapci1 pcib4: at device 16.0 on pci0 pci4: on pcib4 fxp0: port 0xdc00-0xdc1f mem 0xbfeff000-0xbfefffff,0xfaa00000-0xfaafffff irq 7 at device 7.0 on pci4 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:00:4c:b3:59:12 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: [FAST] device_attach: fdc0 attach returned 12 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding 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 Timecounter "TSC" frequency 1406408424 Hz quality 800 Timecounters tick every 1.000 msec md0: Preloaded image 4194304 bytes at 0xffffffff80970f68 ad0: 38166MB at ata0-master UDMA33 acd0: DVDROM at ata1-master UDMA33 ad4: 190782MB at ata2-master UDMA33 Trying to mount root from ufs:/dev/md0 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=61266639 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=66157967 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=77069391 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=3855503 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=536991 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53758511 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53759055 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53759151 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53759607 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53761195 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53757543 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53763015 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53766383 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53766831 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53768975 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53775375 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53775503 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53776079 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53776335 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53776367 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=53778131 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13882927 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13883055 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13874351 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13881519 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13887023 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13898703 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=62784815 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=62786031 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13900015 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=62787951 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=62788591 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=62791663 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=62793455 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=62798063 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=62800495 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=62800623 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=62810223 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=62814479 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=62814991 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=62815119 ad0: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=62814991 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=62816399 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=62817551 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=62821391 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13506191 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13506447 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13482063 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13518863 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13520495 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13522319 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13512399 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13523279 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13527471 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13531407 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13536207 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13543055 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13543759 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13545679 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13549167 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=13542063 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=57147479 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=57153603 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=57128143 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=57172015 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=27040975 ad0: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=27040975 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=27049007 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=27050799 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=27051247 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=27051375 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=27052591 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=27058799 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=27059567 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=27064111 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=27066223 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=27069167 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=27076143 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=27077423 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=27075247 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=27075503 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=27093167 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=27077231 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=9535 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=795071 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=800959 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=272991 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=11647 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=11775 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=31487 ad0: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=31487 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=39327 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=52639 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=58367 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=42111 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=44319 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=48255 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=50783 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=51583 ad0: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=51583 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=55807 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=60639 ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=68831 ad0: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=68831 Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...10 10 4 0 0 done All buffers synced. Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-RELEASE #0: Wed Nov 2 19:07:38 UTC 2005 root@rat.samsco.home:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Sempron(tm) Processor 2500+ (1406.41-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20fc2 Stepping = 2 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800,LM,3DNow+,3DNow> real memory = 251396096 (239 MB) avail memory = 231149568 (220 MB) cpu0 on motherboard pcib0: pcibus 0 on motherboard pci0: on pcib0 pci0: at device 0.0 (no driver attached) pci0: at device 0.1 (no driver attached pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 0.5 (no driver attached) pci0: at device 0.6 (no driver attached) pci0: at device 0.7 (no driver attached) pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 3.0 on pci0 pci2: on pcib2 pcib3: at device 4.0 on pci0 pci3: on pcib3 pci0: at device 5.0 (no driver attached) pci0: at device 9.0 (no driver attached) isab0: at device 10.0 on pci0 isa0: on isab0 pci0: at device 10.1 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 13.0 on pc i0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0xe800-0xe807,0xe480-0xe483,0xe400-0xe407,0xe080-0xe083,0xe000-0xe00f mem 0xfebdf000-0xfebdffff irq 5 at device 14.0 on pci0 ata2: on atapci1 ata3: on atapci1 pcib4: at device 16.0 on pci0 pci4: on pcib4 fxp0: port 0xdc00-0xdc1f mem 0xbfeff000-0xbfefffff,0xfaa00000-0xfaafffff irq 7 at device 7.0 on pci4 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:00:4c:b3:59:12 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: [FAST] ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding 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 Timecounter "TSC" frequency 1406409628 Hz quality 800 Timecounters tick every 1.000 msec ad0: 38166MB at ata0-master UDMA33 acd0: DVDROM at ata1-master UDMA33 ad4: 190782MB at ata2-master UDMA33 Trying to mount root from ufs:/dev/ad0s1a >How-To-Repeat: new install freebsd 6.0 release on ASUS K8N-VM >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Fri May 19 20:25:38 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 8ED0916A421 for ; Fri, 19 May 2006 20:25:38 +0000 (UTC) (envelope-from garyj@jennejohn.org) Received: from mail08b.verio.de (mail08b.verio.de [213.198.55.74]) by mx1.FreeBSD.org (Postfix) with SMTP id A132F43D45 for ; Fri, 19 May 2006 20:25:37 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from mx14.stngva01.us.mxservers.net (204.202.242.37) by mail08b.verio.de (RS ver 1.0.95vs) with SMTP id 3-092504333; Fri, 19 May 2006 22:25:35 +0200 (CEST) Received: from www.jennejohn.org [213.198.5.174] (EHLO peedub.jennejohn.org) by mx14.stngva01.us.mxservers.net (mxl_mta-1.3.8-10p4) with ESMTP id eb92e644.6514.360.mx14.stngva01.us.mxservers.net; Fri, 19 May 2006 16:25:34 -0400 (EDT) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.4/8.11.6) with ESMTP id k4JKPU98003793; Fri, 19 May 2006 22:25:30 +0200 (CEST) (envelope-from garyj@jennejohn.org) Message-Id: <200605192025.k4JKPU98003793@peedub.jennejohn.org> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 To: Igor Robul In-Reply-To: Message from Igor Robul of "Tue, 16 May 2006 14:35:29 +0400." <20060516103529.GD383@sysadm.stc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 May 2006 22:25:30 +0200 From: Gary Jennejohn X-Spam: [F=0.4021140231; heur=0.500(-19800); stat=0.402; spamtraq-heur=0.500(2006051905)] X-MAIL-FROM: X-SOURCE-IP: [213.198.5.174] X-Loop-Detect: 1 X-DistLoop-Detect: 1 Cc: freebsd-amd64@freebsd.org Subject: Re: Success report of 6.1 on Tyan S2865 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 May 2006 20:25:38 -0000 Igor Robul writes: > And now question, can I expect same results on much cheaper motherboard > from ASUS? > It works very well on my ASUS A8V Deluxe, but I don't know whether that MB is still available. --- Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTde From owner-freebsd-amd64@FreeBSD.ORG Fri May 19 21:40: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 406F116A422 for ; Fri, 19 May 2006 21:40:13 +0000 (UTC) (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 BA67E43D49 for ; Fri, 19 May 2006 21:40:12 +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 k4JLeCf7099787 for ; Fri, 19 May 2006 21:40:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k4JLeCHS099786; Fri, 19 May 2006 21:40:12 GMT (envelope-from gnats) Resent-Date: Fri, 19 May 2006 21:40:12 GMT Resent-Message-Id: <200605192140.k4JLeCHS099786@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, Marcelo Machado Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A02C116A422 for ; Fri, 19 May 2006 21:34:19 +0000 (UTC) (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 615A743D46 for ; Fri, 19 May 2006 21:34:19 +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 k4JLYJsB018701 for ; Fri, 19 May 2006 21:34:19 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id k4JLYJAE018700; Fri, 19 May 2006 21:34:19 GMT (envelope-from nobody) Message-Id: <200605192134.k4JLYJAE018700@www.freebsd.org> Date: Fri, 19 May 2006 21:34:19 GMT From: Marcelo Machado To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: amd64/97504: IPFW Rules bug X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 May 2006 21:40:13 -0000 >Number: 97504 >Category: amd64 >Synopsis: IPFW Rules bug >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri May 19 21:40:12 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Marcelo Machado >Release: 6.0 >Organization: Profit-ti >Environment: >Description: I've added the following rules to the ipfw.rules: ipfw add 100 allow all from 192.168.100.3 to 192.168.100.4 ipfw add 110 allow all from 192.168.100.4 to 192.168.100.3 ipfw add 65535 deny all from any to any With these rules the 192.168.100.3 should ping or interact with 192.168.100.4 normally, but don't. But if I add this line: ipfw add 1 allow all from any to any they talk each other normally, but the most problem comes next, if I: ipfw delete 1 Everything begins to work as they should, only these IP's can talk with each other on the net. Thanks >How-To-Repeat: >Fix: if I add this line: ipfw add 1 allow all from any to any they talk each other normally, but the most problem comes next, if I: ipfw delete 1 Everything begins to work as they should, only these IP's can talk with each other on the net. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Sat May 20 11:30:35 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 32E3516A429 for ; Sat, 20 May 2006 11:30:35 +0000 (UTC) (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 8B03043D4C for ; Sat, 20 May 2006 11:30:34 +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 k4KBUYBn058279 for ; Sat, 20 May 2006 11:30:34 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k4KBUYmN058277; Sat, 20 May 2006 11:30:34 GMT (envelope-from gnats) Date: Sat, 20 May 2006 11:30:34 GMT Message-Id: <200605201130.k4KBUYmN058277@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Oliver Fromme Cc: Subject: Re: amd64/97504: IPFW Rules bug X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Oliver Fromme List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 May 2006 11:30:35 -0000 The following reply was made to PR amd64/97504; it has been noted by GNATS. From: Oliver Fromme To: bug-followup@FreeBSD.org, marcelo_vt@hotmail.com Cc: Subject: Re: amd64/97504: IPFW Rules bug Date: Sat, 20 May 2006 13:28:29 +0200 (CEST) Marcelo Machado wrote: > > Number: 97504 > > Synopsis: IPFW Rules bug > > [...] > I've added the following rules to the ipfw.rules: > > ipfw add 100 allow all from 192.168.100.3 to 192.168.100.4 > ipfw add 110 allow all from 192.168.100.4 to 192.168.100.3 > ipfw add 65535 deny all from any to any > > With these rules the 192.168.100.3 should ping or interact with > 192.168.100.4 normally, but don't. But if I add this line: > > ipfw add 1 allow all from any to any > > they talk each other normally, but the most problem comes next, > if I: > > ipfw delete 1 > > Everything begins to work as they should, only these IP's can talk > with each other on the net. You probably forgot to allow access to/from your DNS server, or something similar. The rule #1 will shortly allow that access, and when you delete that rule again, it still works because the DNS results are cached. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "I made up the term 'object-oriented', and I can tell you I didn't have C++ in mind." -- Alan Kay, OOPSLA '97 From owner-freebsd-amd64@FreeBSD.ORG Sat May 20 13:20:21 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 A821916A42D for ; Sat, 20 May 2006 13:20:21 +0000 (UTC) (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 25CE043D45 for ; Sat, 20 May 2006 13:20:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k4KDKLbV064254 for ; Sat, 20 May 2006 13:20:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k4KDKKuk064253; Sat, 20 May 2006 13:20:20 GMT (envelope-from gnats) Date: Sat, 20 May 2006 13:20:20 GMT Message-Id: <200605201320.k4KDKKuk064253@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "Marcelo Machado" Cc: Subject: RE: Re: amd64/97504: IPFW Rules bug X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marcelo Machado List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 May 2006 13:20:21 -0000 The following reply was made to PR amd64/97504; it has been noted by GNATS. From: "Marcelo Machado" To: Cc: Subject: RE: Re: amd64/97504: IPFW Rules bug Date: Sat, 20 May 2006 13:12:54 +0000 --_d6bc2cbb-35e5-41b5-9720-9114e24f7867_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thanks for the assistance Oliver! =20 =20 But, I have a question, I'm only using IP's and not names, still they look = for the DNS? =20 How can I fix it? My firewall is Freebsd 6 and the Dataserver and most of W= ebservers are Windows and one Linux. =20 Thanks a Lot!! =20 Best Regards, Marcelo > Date: Sat, 20 May 2006 13:28:29 +0200> From: olli@lurza.secnetix.de> To: = bug-followup@FreeBSD.org; marcelo_vt@hotmail.com> Subject: Re: amd64/97504:= IPFW Rules bug> > Marcelo Machado wrote:> > > Nu= mber: 97504> > > Synopsis: IPFW Rules bug> > > [...]> > I'= ve added the following rules to the ipfw.rules:> > > > ipfw add 100 allow= all from 192.168.100.3 to 192.168.100.4> > ipfw add 110 allow all from 19= 2.168.100.4 to 192.168.100.3> > ipfw add 65535 deny all from any to any > = > > > With these rules the 192.168.100.3 should ping or interact with> >= 192.168.100.4 normally, but don't. But if I add this line:> > > > ipfw a= dd 1 allow all from any to any> > > > they talk each other normally, but = the most problem comes next,> > if I:> > > > ipfw delete 1> > > > Ever= ything begins to work as they should, only these IP's can talk> > with eac= h other on the net.> > You probably forgot to allow access to/from your DNS= server,> or something similar. The rule #1 will shortly allow that> acces= s, and when you delete that rule again, it still works> because the DNS res= ults are cached.> > Best regards> Oliver> > -- > Oliver Fromme, secneti= x GmbH & Co. KG, Marktplatz 29, 85567 Grafing> Dienstleistungen mit Schwerp= unkt FreeBSD: http://www.secnetix.de/bsd> Any opinions expressed in this me= ssage may be personal to the author> and may not necessarily reflect the op= inions of secnetix in any way.> > "I made up the term 'object-oriented', an= d I can tell you> I didn't have C++ in mind."> -- Alan Kay, OOPSLA = '97 _________________________________________________________________ MSN Busca: f=E1cil, r=E1pido, direto ao ponto.=20 http://search.msn.com.br= --_d6bc2cbb-35e5-41b5-9720-9114e24f7867_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =0A= =0A= =0A= =0A=

Thanks for the assistance Oliver!

 

 

But, I have a question, I'm only using IP's and not names, still they lo= ok for the DNS?

 

How can I fix it? My firewall is Freebsd 6 and the Dataserver and most o= f Webservers are Windows and one Linux.

 

Thanks a Lot!!

 

Best Regards,

Marcelo

> Date: Sat, 20 May 2006 13:28:29 +0200
> From: olli@lurza.secn= etix.de
> To: bug-followup@FreeBSD.org; marcelo_vt@hotmail.com
>= ; Subject: Re: amd64/97504: IPFW Rules bug
>
> Marcelo Ma= chado <marcelo_vt@hotmail.com> wrote:
>  >&nb= sp;> Number:         9= 7504
>  > > Synopsis:    &nb= sp;  IPFW Rules bug
>  > > [= ...]
>  > I've added the following r= ules to the ipfw.rules:
>  > 
> &nb= sp;> ipfw add 100 allow all from 192.= 168.100.3 to 192.168.100.4
>  > ipfw add&= nbsp;110 allow all from 192.168.100.4 to 192.= 168.100.3
>  > ipfw add 65535 deny a= ll from any to any 
>  > 
&g= t;  > With these rules the 192.168.100.3&n= bsp;should ping or interact with
>  >&nbs= p;192.168.100.4 normally, but don't. But if I=  add this line:
>  > 
>  >&= nbsp;ipfw add 1 allow all from any to&nb= sp;any
>  > 
>  > they talk = ;each other normally, but the most problem&nb= sp;comes next,
>  > if I:
>  >&n= bsp;
>  > ipfw delete 1
>  >&nbs= p;
>  > Everything begins to work as=  they should, only these IP's can talk>  > with each other on the net.=
>
> You probably forgot to allow acc= ess to/from your DNS server,
> or something&= nbsp;similar.  The rule #1 will shortly = allow that
> access, and when you delete&nbs= p;that rule again, it still works
> because&= nbsp;the DNS results are cached.
>
> Best&= nbsp;regards
>    Oliver
>
> -- 
= > Oliver Fromme,  secnetix GmbH & Co.&= nbsp;KG, Marktplatz 29, 85567 Grafing
> Dienstlei= stungen mit Schwerpunkt FreeBSD: http://www.secnetix.de= /bsd
> Any opinions expressed in this messag= e may be personal to the author
> and&n= bsp;may not necessarily reflect the opinions = of secnetix in any way.
>
> "I made&n= bsp;up the term 'object-oriented', and I can&= nbsp;tell you
> I didn't have C++ in mi= nd."
>         -- Alan&n= bsp;Kay, OOPSLA '97


MSN Busca: f=E1cil, r=E1pi= do, direto ao ponto. = Encontre o que voc=EA quiser. Clique aqui.=0A= = --_d6bc2cbb-35e5-41b5-9720-9114e24f7867_-- From owner-freebsd-amd64@FreeBSD.ORG Sat May 20 16:15:48 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 69B1916A45A for ; Sat, 20 May 2006 16:15:48 +0000 (UTC) (envelope-from astrodog@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F6A743D48 for ; Sat, 20 May 2006 16:15:46 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by nf-out-0910.google.com with SMTP id c29so387850nfb for ; Sat, 20 May 2006 09:15:45 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Q8awFZCdORANmbAum4o2/ohpKMFIaOd/0QeJL+2EZrcNK9Ixknts/BFP1ldL5BEoyNePzCBWqUkRwTsSZqGdDKURwwt9heUauI7FJXhZPWiQ40ZzCB6uXNm6ueTdIKAhI2iVEyWp5syv3vIdqVXWLeeJxLnwLOvsWiafafzoayE= Received: by 10.49.80.10 with SMTP id h10mr2315754nfl; Sat, 20 May 2006 08:11:11 -0700 (PDT) Received: by 10.49.85.3 with HTTP; Sat, 20 May 2006 08:11:11 -0700 (PDT) Message-ID: <2fd864e0605200811j78c969eqfd8d9df820e06f14@mail.gmail.com> Date: Sat, 20 May 2006 10:11:11 -0500 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <2fd864e0605200810y3ce502f9nf6b8528e509df336@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200605192134.k4JLYJAE018700@www.freebsd.org> <2fd864e0605200810y3ce502f9nf6b8528e509df336@mail.gmail.com> Subject: Fwd: amd64/97504: IPFW Rules bug X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 May 2006 16:15:48 -0000 ---------- Forwarded message ---------- From: Astrodog Date: May 20, 2006 10:10 AM Subject: Re: amd64/97504: IPFW Rules bug To: Marcelo Machado On 5/19/06, Marcelo Machado wrote: > > >Number: 97504 > >Category: amd64 > >Synopsis: IPFW Rules bug > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible: freebsd-amd64 > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Fri May 19 21:40:12 GMT 2006 > >Closed-Date: > >Last-Modified: > >Originator: Marcelo Machado > >Release: 6.0 > >Organization: > Profit-ti > >Environment: > >Description: > I've added the following rules to the ipfw.rules: > > > ipfw add 100 allow all from 192.168.100.3 to 192.168.100.4 > ipfw add 110 allow all from 192.168.100.4 to 192.168.100.3 > ipfw add 65535 deny all from any to any > > With these rules the 192.168.100.3 should ping or interact with 192.168.1= 00.4 normally, but don't. But if I add this line: > > ipfw add 1 allow all from any to any > > they talk each other normally, but the most problem comes next, if I: > > ipfw delete 1 > > Everything begins to work as they should, only these IP's can talk with e= ach other on the net. > > Thanks > >How-To-Repeat: > > >Fix: > if I add this line: > > ipfw add 1 allow all from any to any > > they talk each other normally, but the most problem comes next, if I: > > ipfw delete 1 > > Everything begins to work as they should, only these IP's can talk with e= ach other on the net. > >Release-Note: > >Audit-Trail: > >Unformatted: > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > There's a bit more to the two systems talking to each other, than the point to point communication. ARP lookups, etc. If you allow all from anip to anotherip, and allow all from anotherip to anip, you're still denying everything to broadcast, for example. As a side note, this isn't AMD64 related. :\