Bruce Dubbs wrote:
Jeremy Utley wrote:
Having the Mesa 3d libs installed will break hardware 3D-rendering
always - whether it be DRI-based, NVIDIA drivers, or ATI's FireGL
drivers. People will be limited to software 3d rendering.
Thanks Jeremy. I can confirm that with the mesa
Jeremy Utley wrote:
Bruce Dubbs wrote:
Jeremy Utley wrote:
Having the Mesa 3d libs installed will break hardware 3D-rendering
always - whether it be DRI-based, NVIDIA drivers, or ATI's FireGL
drivers. People will be limited to software 3d rendering.
Thanks Jeremy. I can confirm that with
Bruce Dubbs wrote:
I figured out what happened. I installed the Nvidia binary drivers. It
overwrote:
Is it a good idea to add manual installation of those NVidia drivers (and
possibly fglrx, I can provide instructions) to the book, so that future
readers don't step onto this problem?
--
[I'm sorry if this comes as a duplicate message as I'm not sure about
the current status of the mail/news gateway and my posts don't seem to
appear on the mailing lists.]
Bruce Dubbs wrote:
Bruce Dubbs wrote:
OK. I can work with that. Right now the issue is whether to mention
mesa at all. I'm inclined to at least mention it. I don't know if the
mesa install breaks anything else. I don't know what to test it with
other than the kde screensavers.
-- Bruce
Having the Mesa
Jeremy Utley wrote:
Having the Mesa 3d libs installed will break hardware 3D-rendering
always - whether it be DRI-based, NVIDIA drivers, or ATI's FireGL
drivers. People will be limited to software 3d rendering.
Thanks Jeremy. I can confirm that with the mesa libraries installed I
get 635
