Date: Mon, 08 Dec 2008 14:36:23 +0000 From: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk> To: "Conrad J. Sabatier" <conrads@cox.net> Cc: freebsd-current@freebsd.org, cpghost <cpghost@cordula.ws> Subject: Re: i give up Message-ID: <1228746983.27498.1.camel@buffy.york.ac.uk> In-Reply-To: <20081206190754.6c2bbd70@serene.no-ip.org> References: <20081128234155.0221e263@serene.no-ip.org> <4930D7CE.4080909@psg.com> <20081202220643.72eb52a3@serene.no-ip.org> <20081203151537.GA1045@phenom.cordula.ws> <20081206190754.6c2bbd70@serene.no-ip.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2008-12-06 at 19:07 -0600, Conrad J. Sabatier wrote: > I'm continuing to hold out hope that I can provide the missing bits of > the puzzle that will lead to a solution. But I've already passed along > everything I could get from Windows Vista's System Information tool, > Linux's lspci command, and FreeBSD's pciconf and dmesg. I don't know > what more iI can provide at this point. You could perhaps provide it again? I've still not seen it. > As another poster suggested, it's possible there's a bug/typo in the > patches Soren sent me, although they all apply quite cleanly to every > successive version of current I've tried them on. So...I'm at a loss > at this point. It really is frustrating. > > I'm no fan of either Windows or Linux, but at least they do recognize > my hardware. So I'm stuck for the time being. <sigh> > > If anyone's interested, I'll repost or mail directly to them all the > pertinent info I can gather. Just say the word and it shall be done. Please. Gavin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1228746983.27498.1.camel>