Bug 188937 - nvidia driver needs symbol xen_tlb_flush
Summary: nvidia driver needs symbol xen_tlb_flush
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel-xen
Version: 5
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Xen Maintainance List
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-13 19:52 UTC by Sietse Visser
Modified: 2009-12-14 20:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-26 23:03:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Sietse Visser 2006-04-13 19:52:39 UTC
Description of problem: nvidia graphics driver fails to load on Xen kernel

Version-Release number of selected component (if applicable): nvidia 8756

How reproducible: every time. 
Works fine on non-xen kernel.

Steps to Reproduce:
1. modprobe nvidia
  
Actual results:
Apr 13 21:05:48 prefect kernel: nvidia: Unknown symbol xen_tlb_flush
FATAL: Error inserting nvidia_1_0_8756
(/lib/modules/2.6.16-1.2080_FC5xen0/updates/drivers/video/nvidia/nvidia-1_0-8756.ko):
Unknown symbol in module, or unknown parameter (see dmesg)

In /var/log/messages:
Apr 13 21:05:48 prefect kernel: nvidia: module license 'NVIDIA' taints kernel.
Apr 13 21:05:48 prefect kernel: nvidia: Unknown symbol xen_tlb_flush


Expected results: loaded module

Comment 1 Sietse Visser 2006-04-18 14:40:17 UTC
Someone got it working with some patches:
http://www.nvnews.net/vbulletin/showthread.php?t=68648

Hope this is helpful.

Sietse

Comment 2 Boleslaw Ciesielski 2006-10-10 21:20:42 UTC
See also discussion in http://bugzilla.atrpms.net/show_bug.cgi?id=784

Comment 3 Red Hat Bugzilla 2007-07-25 01:31:11 UTC
change QA contact

Comment 4 Chris Lalancette 2008-02-26 23:03:34 UTC
This report targets FC5, which is now end-of-life.

Please re-test against Fedora 7 or later, and if the issue persists, open a new bug.

Thanks


Note You need to log in before you can comment on or make changes to this bug.