Date: Tue, 20 Nov 2001 15:51:24 -0500 From: "Andrew C. Hornback" <achornback@worldnet.att.net> To: "Toomas Aas" <toomas.aas@raad.tartu.ee>, <questions@FreeBSD.ORG> Subject: Bugfixes, Support, etc. (was: RE: home pc use) Message-ID: <004601c17205$1dc2e780$6600000a@ach.domain> In-Reply-To: <200111201428.fAKESdD28470@lv.raad.tartu.ee>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: owner-freebsd-questions@FreeBSD.ORG > [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Toomas Aas > Sent: Tuesday, November 20, 2001 9:28 AM > To: Anthony Atkielski; questions@FreeBSD.ORG > Subject: Re: home pc use > > On 20 Nov 01 at 11:19 you wrote: > > > Robert writes: > > > > > Perhaps this was due to your buggy VIA > > > Southbridge, mentioned in another > > > thread, IIRC? > > > > That same "buggy" hardware runs Windows flawlessly. > > VIA has released drivers for Windows that work around the hardware > bugs. That is why this buggy (sans quotes) hardware runs Windows > flawlessly. > > As they (VIA) don't want to release information of what is actually > wrong with the 686B southbridge, the people who make other > operating systems can't do much to write similar workarounds for > these systems. > > My information is some weeks old, maybe things have changed in > the meantime. Toomas, Greg Lehey told Anthony last week that he needed to speak with Soren about a fix for the ATA driver to make his VIA chipset work properly with FreeBSD. However, since then, Anthony has continued to discredit the idea that it could possibly be a hardware problem, and has instead placed the blame fully on the shoulders of FreeBSD. At this point, I believe it clear that Anthony does not want to correct the problem, but use it as a point of contention to continually bash FreeBSD with. I'm sorry, but I do not believe it is the fault of The FreeBSD Project (Core group or anyone else) that he has not seen fit to research the fix and apply it so that FreeBSD will work with his bug-laden chipset. From what I've seen, the Core group does not have every iteration of every piece of hardware in existance to test FreeBSD on. If I could remedy that situation, I would in a heart beat. Because they don't have EVERY knick-knack and geek-gaw in existance, there is no way to test the software for every possible situation. Thus, fixes are produced along the way (and I appreciate how hard the guys doing the fixes work, Warner Losh is one of the hardest working folks that I know trying to keep up on all of the various laptops out there with non-standard hardware implementations). When a user finds a piece of hardware that does not work properly under FreeBSD, they have to make one of three choices. 1) Either live with the problems, 2) Research the problem, see if a fix has been created, and apply the fix or 3) Find another OS that supports your hardware better. If I'm wrong, would someone please correct me. If you're not going to follow the information that you've been given by the experts on the list (Greg, Kris, and Crist this means you), then you shouldn't complain about having problems. Again, I'd like to reiterate that I appreciate the work that everyone is doing on The FreeBSD Project here. It's a lot of hard work, and having to deal with folks complaining about problems that don't even pursue solutions, that's gotta grate on your nerves. Thanks guys, and keep up the good work. --- Andy 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?004601c17205$1dc2e780$6600000a>