Paul G. Allen wrote:
Until now I've not had any trouble with NVIDIA Linux drivers.
At some point when I had either FC5 or FC7 (I forget which), I had
issues with some OpenGL application. I thought maybe I needed to update
the video driver, which I hadn't done in a long time. I did, and X
didn't work. I had to revert to the stock X11.org, software emulated
OpenGL driver. So, I had no more OpenGL for anything.
So now I'm running FC8. I looked in the lvna repository for a NVIDIA
driver and thought I found one (this laptop has a GeForce 440 Go -
GeForce4 chip for mobile computing - and 1024x768 LCD + external SVGA
interface). I installed it with the dependencies - kernel module,
libraries, etc.
Are you sure your chipset is supported by the Nvidia driver you're
using. Normally, the driver won't compile if your chipset is not
supported, it and tells you to use the legacy driver instead. Check the
list of supported cards/chipsets.
Now I have a black screen when I start X. No errors in the X log file,
the driver seems to recognize the card, and in fact when I change screen
resolutions, I see in the log file the entry for each change.
I have similar problems on my laptop if I use the Nvidia driver - as do
many other people. The NV forum offers a few See-if-this-works solutions
from subscribers, but no official response from Nvidia.
My problem differs in that X runs fine with the Nvidia driver, but I
have a black screen on consoles during, and after quitting X. The
problem started some time ago for me, and using an earlier Nvidia driver
"fixed" the problem. However, that older driver will no longer compile
with the late Linux kernels.
So now I have to revert to the "stock" FC8 X driver (after I figure out
the name of the package(s) to install).
Of course, you mean the NV driver, which is not, as I understand, born
of Fedora.
Thanks NVIDIA and Fedora.
PGA
I really don't think it's Fedora created problem, and maybe not even an
Nvidia spawned problem. If anything, it's probably caused by multiple
changes between Nvidia, kernel, and ACPI.
I suspect it's related to recent changes to ACPI. You might do some
digging to find if your laptop is supported directly by ACPI or if there
is an ACPI driver specific you should be using.
--
Best Regards,
~DJA.
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
