Bug 134127

Summary: nvidia kernel modul could not build on kernel 2.6.8-1.590
Product: [Fedora] Fedora Reporter: Jochen Schmitt <jochen>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: rawhideCC: wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:06:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
The log file of the nvidia driver installation process none

Description Jochen Schmitt 2004-09-29 18:47:25 UTC
I am starting NVIDIA-Linux-x86-6111-pkg1.run.

After the new kernel modul should be created, I got a message which
says, that the module could not be loaded.

The file /var/log/nvidia-installer.log contains error messages from
the compile which try to create the kernel module.

Comment 1 Jochen Schmitt 2004-09-29 18:49:02 UTC
Created attachment 104537 [details]
The log file of the nvidia driver installation process

Comment 2 Arjan van de Ven 2004-09-29 18:51:50 UTC
Please report this problem to Nvidia via their customer
technical support, and they will likely address the issue in a
future driver update.  Nvidia might not officially support
Fedora Core 3 test2 at this juncture, however once Fedora Core 3
is officially released, they will probably release a new driver
which supports the final OS release.
                                                                     
                                                 
Thanks for reporting this problem to Nvidia.


*** This bug has been marked as a duplicate of 73733 ***

*** This bug has been marked as a duplicate of 73733 ***

Comment 3 Red Hat Bugzilla 2006-02-21 19:06:01 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.