[EMAIL PROTECTED] wrote: > Ted Mittelstaedt writes: > >> You were given things to try and do to solve the problem. > > No, I was not. I encountered a few people throwing darts and trying > to pretend that they had a clue and/or working to divert any > suspicion from > FreeBSD towards unspecified, unverified hardware problems, but I got > no real answers. I don't think anybody has any idea, which doesn't > surprise me.
The problem is you just don't want it to be a hardware problem because you don't accept the possibility that the NT driver wrote around a hardware problem and the FreeBSD driver doesen't. Despite the fact that making up for hardware problems with writearounds in the software drivers is a common thing in the industry. So you won't do the testing to prove that it is or isn't a hardware bug, and thus you can continue pretending to yourself that it must be software, and thus not your responsibility. Ted _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
