Your message dated Fri, 09 Apr 2010 01:36:46 -0700
with message-id <[email protected]>
and subject line Re: nvidia module fails to load after kernel upgrade
has caused the Debian Bug report #288934,
regarding nvidia module fails to load after kernel upgrade
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
288934: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=288934
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nvidia-kernel-2.4.27-1-k7
Version: 1.0.6111+3
After kernel upgrade nvidia module failed to load. Transcript follows:
Script started on Thu Jan 6 00:21:34 2005
home:~# uname -a
Linux home 2.4.27-1-k7 #1 Wed Dec 1 20:12:01 JST 2004 i686 GNU/Linux
home:~# modprobe nvidia
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o:
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol irq_stat_R180940a9
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o:
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol
proc_root_driver_Ra36f876c
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o:
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol
devfs_register_chrdev_R703a15c9
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o:
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol
devfs_register_Re02370a4
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o:
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol
devfs_unregister_R29602a1c
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o:
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol
change_page_attr_R04098f96
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o:
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol __pollwait_R87156f10
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o:
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol mem_map_Rdb8be4fa
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o:
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol
create_proc_entry_Ra185990c
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o:
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol
remove_proc_entry_R4a81d799
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o:
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: unresolved symbol init_mm_R6257a2b2
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o:
Hint: You are trying to load a module without a GPL compatible license
and it has unresolved symbols. The module may be trying to access
GPLONLY symbols but the problem is more likely to be a coding or
user error. Contact the module supplier for assistance, only they
can help you.
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: insmod
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o failed
/lib/modules/2.4.27-1-k7/nvidia/nvidia.o: insmod nvidia failed
home:~# apt-cache policy nvidia-kernel-2.4.27-1-k7
nvidia-kernel-2.4.27-1-k7:
Installed: 1.0.6111+3
Candidate: 1.0.6111+3
Version Table:
*** 1.0.6111+3 0
500 ftp://debian.gala.net sarge/non-free Packages
100 /var/lib/dpkg/status
home:~# apt-cache policy kernel-image-2.4.27-1-k7
kernel-image-2.4.27-1-k7:
Installed: 2.4.27-6
Candidate: 2.4.27-6
Version Table:
*** 2.4.27-6 0
500 ftp://debian.gala.net sarge/main Packages
100 /var/lib/dpkg/status
home:~#
Script done on Thu Jan 6 00:22:29 2005
All packages in system from official repositories only, no third-party
ones.
I'm not sure -- should this bug be assigned to nvidia-kernel or
kernel-image packages? Recent upgrade changed kernel-image, but
nvidia-kernel was not changed. Probably it should be recompiled for new
kernel version? Or something wrong with the kernel?
--
WBR, Alexander A. Vlasov
Gala.Net System Administrator
+38(039)2476081
nic-hdl: ZULU-UANIC
--- End Message ---
--- Begin Message ---
This bug was reporting an incompatibility of symbols between the current
kernel and the current NVIDIA kernel module. Both the module and the
kernel against which this bug was originally reported are long-gone.
Closing this bug as it cannot exist with the current packages in its
originally reported form. Any similar bug today would be from some other
cause.
--
Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/>
--- End Message ---
