Date: 12 Aug 2002 11:25:17 +0000 From: Josh Paetzel <friar_josh@webwarrior.net> To: friar_josh@webwarrior.net Cc: Jacob Rhoden <jrhoden@unimelb.edu.au>, Seahawk <seahawk@isis.visi.com>, freebsd-questions@freebsd.org Subject: Re: MODE_SENSE_BIG - Any news on this being fixed? Message-ID: <1029151520.229.4.camel@heater.vladsempire.net> In-Reply-To: <1029145291.279.6.camel@heater.vladsempire.net> References: <Pine.GSO.4.10.10208112242080.12918-100000@isis.visi.com> <200208121352.03021.jrhoden@unimelb.edu.au> <1029145291.279.6.camel@heater.vladsempire.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2002-08-12 at 09:41, Josh Paetzel wrote: > On Mon, 2002-08-12 at 03:52, Jacob Rhoden wrote: > > Hi, > > > > On Mon, 12 Aug 2002 13:44, you wrote: > > > I have the same problem, I guess I'm waiting for 4.6.2 to be released > > > (couple weeks?). I've been told that the problem should be fixed in that > > > version. > > > > As I understand it though, changes are made in the 4.6-STABLE branch to test > > things, before it becomes a release. Since its not fixed yet in stable then I > > would assume no code has been submitted which could fixes it. (Or perhaps > > there has been but it doesnt fix it in this case?). > > > > Regards, > > Jacob > > > > > > Jacob Rhoden Phone: +61 3 9844 6102 > > ITS Division Email: jrhoden@unimelb.edu.au > > Melbourne University Mobile: +61 403 788 386 > > Someone can correct me if I'm wrong on this, but I've had CDROMS of > various types that have given me the read_big error ever since support > for IDE CDROMS became available. (2.1.5 was beta support iirc). I used > to submit prs and so forth to try and get them to work, through this > I've come to understand that the FreeBSD ad driver is written according > to the IDE "standard" and it's the drives themselves that have wrong > BIOS code. If you have a drive that just plain doesn't work correctly, > and never has worked correctly, I doubt 4.6.2 will fix it. If your > drive worked fine, and then updating to 4.6 broke it, then 4.6.2 will > probably fix it. > > As far as the code being in -STABLE, code freeze for 4.6.2 is a ways off > yet. My guess is the people working on it are still testing fixes and > so forth. > > Josh I guess reading questions before stable is a poor idea. Code freeze is not a ways off. :) Josh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1029151520.229.4.camel>