Getting the nvidia driver (version 6111) working under FC3T2 (with kernel-2.6.8-1.584) is proving to be rather bothersome.
First I encountered the 'no screen found problem'. After modprobing nvidia I encountered the 'unknown symbol VMALLOC_RESERVE' problem.
I have no idea what is happening. Can anybody suggest a quick (and dirty) fix?
Alexander
First thing I would do is lose the 2.6.8-1.584 kernel, it has been pulled from the update list, so I can only assume that is because it is buggy as hell.
the nVida driver works great with 2.6.8-1.541
I know this wasn't much help, but I had the same problem and that is what I ended up doing.
BaVinic
Alexander Volovics wrote:
Getting the nvidia driver (version 6111) working under FC3T2 (with kernel-2.6.8-1.584) is proving to be rather bothersome.
First I encountered the 'no screen found problem'. After modprobing nvidia I encountered the 'unknown symbol VMALLOC_RESERVE' problem.
I have no idea what is happening. Can anybody suggest a quick (and dirty) fix?
Alexander
On Fri, Sep 24, 2004 at 03:04:44PM -0400, Jim Martin wrote:
First I encountered the 'no screen found problem'. After modprobing nvidia I encountered the 'unknown symbol VMALLOC_RESERVE' problem.
First thing I would do is lose the 2.6.8-1.584 kernel, it has been pulled from the update list, so I can only assume that is because it is buggy as hell.
the nVida driver works great with 2.6.8-1.541
Thanks for the tip, I will give 2.6.8-1.541 a try.
Alexander
On Fri, Sep 24, 2004 at 03:04:44PM -0400, Jim Martin wrote:
First thing I would do is lose the 2.6.8-1.584 kernel, it has been pulled from the update list, so I can only assume that is because it is buggy as hell.
It was pulled due to SELinux bugs in particular.
the nVida driver works great with 2.6.8-1.541
I know this wasn't much help, but I had the same problem and that is what I ended up doing.
The VMALLOC_RESERVE problem is an NVidia driver problem, not a kernel bug. There was a one-line workaround for the nvidia driver posted to the linux-kernel mailing list (the problem happens with recent mm kernels too).
-Barry K. Nathan barryn@pobox.com
Jim Martin wrote:
First thing I would do is lose the 2.6.8-1.584 kernel, it has been pulled from the update list, so I can only assume that is because it is buggy as hell.
the nVida driver works great with 2.6.8-1.541
I know this wasn't much help, but I had the same problem and that is what I ended up doing.
I have noticed that I have to run the nvidia installer twice to get it working with udev. Running the installer only once cause screen not found with xorg. Running it twice does fix the problem.
Dwaine.