From owner-freebsd-qa@FreeBSD.ORG Mon May 26 11:02:19 2003 Return-Path: Delivered-To: freebsd-qa@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9ECA37B40C for ; Mon, 26 May 2003 11:02:19 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CE5243F75 for ; Mon, 26 May 2003 11:02:19 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h4QI2JUp008853 for ; Mon, 26 May 2003 11:02:19 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h4QI2IKv008848 for qa@freebsd.org; Mon, 26 May 2003 11:02:18 -0700 (PDT) Date: Mon, 26 May 2003 11:02:18 -0700 (PDT) Message-Id: <200305261802.h4QI2IKv008848@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: qa@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-qa@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD Quality Assurance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 May 2003 18:02:20 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [2002/08/08] i386/41437 qa sysinstall 4.6 RELEASE - hang f [2002/08/21] i386/41860 qa sysinstall rel. 4.5 and 4.6 hangs o [2003/01/22] bin/47384 qa sysinstall ignores intended destination d o [2003/02/16] bin/48341 qa Sysinstall deletes mbr although it should 4 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/02/28] bin/25461 qa sysinstall's fdisk and disklabel don't wo f [2001/05/29] i386/27729 qa the ls120 device "afd" does not show up u o [2001/08/01] i386/29375 qa the disk editor used by /stand/sysinstall o [2001/09/26] bin/30837 qa Sysinstall doesn't set the schg flag on t o [2002/05/27] bin/38609 qa Sysinstall should know the size of the va o [2002/07/16] bin/40656 qa patch: sysinstall: scripted deletion of s o [2002/11/21] i386/45565 qa sysinstall: write error, filesystem full 7 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [1998/11/27] i386/8867 qa /stand/sysinstall core dumps (signal 11) o [1999/09/24] i386/13936 qa No clear indictaion of how much space to o [1999/10/13] bin/14318 qa sysinstall upon install has some counter- o [2000/03/22] bin/17546 qa Sysinstall does not let you configure NIS o [2000/08/28] bin/20908 qa /stand/sysinstall too limited in selectio o [2001/01/18] bin/24435 qa Changing slice type causes Auto-partition o [2001/04/28] bin/26919 qa sysinstall' fdisk can ONLY set bootable f o [2001/05/08] i386/27216 qa Can not get to shell prompt from serial c o [2001/05/20] bin/27483 qa make sysinstall ask for the keymap at ins o [2002/05/12] i386/37999 qa In /stand/sysinstall, 's' selects Options o [2002/05/13] i386/38055 qa In Install, Groups (creation) item should o [2002/05/27] bin/38610 qa Sysinstall should be able to mount ISO im o [2002/08/17] misc/41744 qa Cannot stop comat22 from being extracted o [2002/08/25] i386/42022 qa sysinstall in non-interactive mode prompt o [2002/08/29] i386/42162 qa Installation (sysinstall) crashes, md0c f o [2002/10/08] misc/43825 qa please remove object files in source (src o [2002/11/12] misc/45254 qa Sysinstall installs things it should not o [2002/11/22] conf/45608 qa Install should config all ether devices, 18 problems total. From owner-freebsd-qa@FreeBSD.ORG Wed May 28 01:30:15 2003 Return-Path: Delivered-To: freebsd-qa@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C540437B405 for ; Wed, 28 May 2003 01:30:15 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FBEC43F85 for ; Wed, 28 May 2003 01:30:15 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h4S8UFUp037394 for ; Wed, 28 May 2003 01:30:15 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h4S8UFEb037393; Wed, 28 May 2003 01:30:15 -0700 (PDT) Date: Wed, 28 May 2003 01:30:15 -0700 (PDT) Message-Id: <200305280830.h4S8UFEb037393@freefall.freebsd.org> To: qa@FreeBSD.org From: Thomas Zenker Subject: Re: bin/40656: patch: sysinstall: scripted deletion of slices X-BeenThere: freebsd-qa@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Thomas Zenker List-Id: FreeBSD Quality Assurance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 May 2003 08:30:16 -0000 The following reply was made to PR bin/40656; it has been noted by GNATS. From: Thomas Zenker To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: bin/40656: patch: sysinstall: scripted deletion of slices Date: Wed, 28 May 2003 10:26:02 +0200 Perhaps helps to get an ear explaining this a bit further: In automated installations (embedded devices in instruments) via sysinstall scripts, it is impossible to make a script which does a complete installation and works on hard disks which have fdisk partitions already. The most simple solution is to give sysinstall scripts the ability to delete all fdisk partitions, so we can do a new install. In embedded devices clobbering the fdisk partition manually is not an option. Thomas From owner-freebsd-qa@FreeBSD.ORG Wed May 28 04:34:01 2003 Return-Path: Delivered-To: freebsd-qa@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD6E237B401 for ; Wed, 28 May 2003 04:34:01 -0700 (PDT) Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.249.195.3]) by mx1.FreeBSD.org (Postfix) with SMTP id 14B1F43F93 for ; Wed, 28 May 2003 04:34:00 -0700 (PDT) (envelope-from paulo@nlink.com.br) Received: (qmail 89548 invoked by uid 85); 28 May 2003 11:33:58 -0000 Received: from paulo@nlink.com.br by mirage.nlink.com.br by uid 82 with qmail-scanner-1.16 (clamscan: 0.54. spamassassin: 2.55. Clear:. Processed in 0.175421 secs); 28 Mai 2003 11:33:58 -0000 Received: from sentry.nlink.com.br (HELO nlink.com.br) (200.249.197.84) by mirage.nlink.com.br with SMTP; 28 May 2003 11:33:58 -0000 Message-ID: <3ED49E98.1010702@nlink.com.br> Date: Wed, 28 May 2003 08:33:44 -0300 From: Paulo Fragoso User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030523 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug White References: <3ECD7DEE.2070604@nlink.com.br> <20030523154603.H38182@carver.gumbysoft.com> In-Reply-To: <20030523154603.H38182@carver.gumbysoft.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: FreeBSD-qa@FreeBSD.org Subject: Re: Problem with Toshiba Satelite X-BeenThere: freebsd-qa@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD Quality Assurance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 May 2003 11:34:02 -0000 There is another way to boot on Freebsd 5.1-BETA after used I had Window$, changing for boot sequence in setup from HDD->FDD to FDD->HDD without put any Floppy Disk. Paulo. Doug White wrote: > On Thu, 22 May 2003, Paulo Fragoso wrote: > > >>Hi, >> >>I'm using FreeBSD 5.1-BETA1 with Toshiba Satelite 1415-S173 and after I >>had logged out from Window$ XP and tryied boot into FreeBSD it is >>freezing after detected agp interface and I can't more use the FreeBSD. > > > What happens if you cold boot? > > windows could be whacking out the agp hardware and the reset isn't > resetting it fully. The chipset drivers on some systems are, shall we say, > unconventional. >