[ATrpms-users] nvidia problems after upgrading to FC4

[Axel Thimm]

On Sun, Jan 01, 2006 at 08:37:03PM +0100, Niels Dybdahl wrote:
> I have upgraded a MythTV 0.18.1 system from FC3 to FC4 with a 2.6.14-1.1653_FC4smp kernel.
> I then followed Jarod Wilsons instructions on installing nVidia drivers (V 7667), which seemed to install correctly.
> But on restart the system could not find the kernel module and there
> was no such thing as
> /lib/modules/2.6.14-1.1653_FC4smp/kernel/drivers/video/nvidia/nvidia.ko.
> There was however a
> /lib/modules/2.6.14-1.1644_FC4smp/kernel/drivers/video/nvidia/nvidia.ko,
> so I tried to copy that to
> /lib/modules/2.6.14-1.1653_FC4smp/kernel/drivers/video/nvidia/.
> After that the system could start but it is not stable when I start
> mythfrontend, which probably is not very surprising.
> 
> So now I would like to know a little more:
> - Should yum install nvidia-graphics7667-kmdl-$KVER create a
> nvidia.ko file under 2.6.14-1.1653_FC4smp ? And why did it not do
> that ?

KVER was probably not set to what you wanted.

> - Is there a better version that I should use instead ?

Just repeat the command with KVER=2.6.14-1.1653_FC4smp
There are also other nevidia driver versions at ATrpms (in fact all
since 1-2 years), the latest is nvidia-graphics8178, e.g.

yum install nvidia-graphics8178-kmdl-2.6.14-1.1653_FC4smp nvidia-graphics8178

Then use /etc/X11/xorg.conf.nvidia as a template for
/etc/X11/xorg.conf. E.g. copy it over after inspecting its contents.

> - Is it preferable to compile the driver from nvidias homepage
>   instead and is there a howto on doing that ?

The rpms are preferable, but if you want to build it yourself, there
is only one script you need to call in the upstream sources, so there
is no HOWTO needed.
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-users/attachments/20060102/0e818299/attachment.bin