From owner-freebsd-stable Fri Oct 6 1:13:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from stjohn.stjohn.ac.th (stjohn.stjohn.ac.th [202.21.144.1]) by hub.freebsd.org (Postfix) with ESMTP id C93C437B502 for ; Fri, 6 Oct 2000 01:13:11 -0700 (PDT) Received: from granite ([203.151.134.100]) by stjohn.stjohn.ac.th (8.9.3/8.9.3) with SMTP id PAA25881; Fri, 6 Oct 2000 15:07:57 +0700 (GMT) Message-Id: <3.0.6.32.20001006151406.007d73c0@stjohn.stjohn.ac.th> X-Sender: mcrogerm@stjohn.stjohn.ac.th X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Fri, 06 Oct 2000 15:14:06 +0700 To: "Leonard C." From: Roger Merritt Subject: Re: CDROM support brokenness Cc: freebsd-stable@freebsd.org In-Reply-To: <4.3.2.7.2.20001006004836.028b9e58@yikes.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:53 AM 10/6/00 -0700, you wrote: >I recently upgraded from 4.0 RELEASE to 4.1.1-STABLE on a box with some >pretty old hardware. After the upgrade, my CDROM drive (slave on 2nd >channel) is no longer detected. > >Doing a quick search of the mailing list archive, this seems to be a pretty >common problem that other people have run into, but I couldn't find any >solutions to the problem. > >Does anybody know the status of this bug? Are there any workarounds? > >Thanks, > >Leonard > The workaround I found was to drop back to 4.1-RELEASE. I understand from postings to the list that the problem started around 22 August so I suppose you could update to any version prior to that. I've also read that the problem was fixed of 25 August and also that it was fixed on 2 September, but I cvsupped to 4-STABLE on 14 Sep and it still didn't work for me. Apparently it still hasn't been corrected. -- Roger An egotist is an annoying person who is more interested in himself than in me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message