From owner-freebsd-stable Mon Oct 2 7:43:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id C325037B502 for ; Mon, 2 Oct 2000 07:43:51 -0700 (PDT) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 13g6oo-000DfH-00 for freebsd-stable@freebsd.org; Mon, 2 Oct 2000 15:43:50 +0100 Received: (from rasputin@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id PAA98464 for freebsd-stable@freebsd.org; Mon, 2 Oct 2000 15:43:50 +0100 (BST) (envelope-from rasputin) Date: Mon, 2 Oct 2000 15:43:50 +0100 From: Rasputin To: freebsd-stable@freebsd.org Subject: Re: 4.1.1 breakage: GUS, spash screen, CD writing Message-ID: <20001002154350.B98364@dogma.freebsd-uk.eu.org> References: <20000929130048.A62987@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from behanna@zbzoom.net on Fri, Sep 29, 2000 at 09:32:20AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 29, 2000 at 09:32:20AM -0400, Chris BeHanna wrote: > On Fri, 29 Sep 2000, Rasputin wrote: > > > Was tracking stable until the ata0 bus (pr20924) knocked out my CDROM drive. > > But my supfile is hardcoded to not update past the 21st of August > > because of the ata bug. > > If you're referring to the inability to mount a CD and the > subsequent inability to eject it, that was fixed quite some time ago. > No, I'm referring to PR 20924 , which is the inability of freeBSD-stable to detect ata0-slave on some intel kits. http://www.freebsd.org/cgi/query-pr.cgi?pr=20924 still shows it as open... Should I resubmit this PR, as my hardware is very different to the one listed? Maybe sos@frebsd.org thinkd it's only affecting 1 person? -- Rasputin Jack of All Trades :: Master of Nuns To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message