On Mon, 2010-08-16 at 20:01 -0700, john wendel wrote:
> I should just keep quiet, but anyhow ...
Yes, why tempt fate, when you can... ;-)
> I just installed the latest evil Nvidia driver, which works great on
> my F11 box, and nothing is broken. I just did 'ls -ltr' in all
> the /usr directories
On 08/16/2010 10:17 AM, Mikkel wrote:
> On 08/16/2010 07:38 AM, Marko Vojinovic wrote:
>> On Monday, August 16, 2010 05:03:54 Tim wrote:
>>> On Sun, 2010-08-15 at 17:12 -0700, Jonathan Ryshpan wrote:
I fear that there are technical reasons why Nvidia is releasing files
with conflicting na
On 08/16/2010 07:38 AM, Marko Vojinovic wrote:
> On Monday, August 16, 2010 05:03:54 Tim wrote:
>> On Sun, 2010-08-15 at 17:12 -0700, Jonathan Ryshpan wrote:
>>> I fear that there are technical reasons why Nvidia is releasing files
>>> with conflicting names.
>>
>> Considering that others have repa
Tim:
>> Considering that others have repackaged the same drivers, so they
>> install without stuffing up the original system files, the answer
>> would probably be that there is no good reason, just laziness on
>> their behalf.
>>
>> If they're making the drivers, they can make it ask for files wi
On Monday, August 16, 2010 05:03:54 Tim wrote:
> On Sun, 2010-08-15 at 17:12 -0700, Jonathan Ryshpan wrote:
> > I fear that there are technical reasons why Nvidia is releasing files
> > with conflicting names.
>
> Considering that others have repackaged the same drivers, so they
> install without
On Sun, 2010-08-15 at 17:12 -0700, Jonathan Ryshpan wrote:
> I fear that there are technical reasons why Nvidia is releasing files
> with conflicting names.
Considering that others have repackaged the same drivers, so they
install without stuffing up the original system files, the answer would
pro
On Sun, Aug 15, 2010 at 17:12:13 -0700,
Jonathan Ryshpan wrote:
>
> I used the kmod/akmod happily for some time, till google earth stopped
> working under the kmod/akmod driver. (The open source (nouveau) driver,
> which would have been preferable doesn't support the 3D hardware which
> google
On Sun, 2010-08-15 at 17:56 -0400, Todd Zullinger wrote:
> Jonathan Ryshpan wrote:
> > If you use the Nvidia proprietary drivers (as I do) be aware that
> > installing some of the xorg*.rpm packages can break these drivers in
> > subtle ways. In particular, xorg-x11-server-Xorg.*.rpm contains the
Jonathan Ryshpan wrote:
> If you use the Nvidia proprietary drivers (as I do) be aware that
> installing some of the xorg*.rpm packages can break these drivers in
> subtle ways. In particular, xorg-x11-server-Xorg.*.rpm contains the
> file /usr/lib64/xorg/modules/extensions/libglx.so, which confli
If you use the Nvidia proprietary drivers (as I do) be aware that
installing some of the xorg*.rpm packages can break these drivers in
subtle ways. In particular, xorg-x11-server-Xorg.*.rpm contains the
file /usr/lib64/xorg/modules/extensions/libglx.so, which conflicts with
a file with the same na
10 matches
Mail list logo
