Mailinglist Archive: opensuse-kernel (148 mails)

< Previous Next >
Re: [opensuse-kernel] bug in kernel-source-2.6.27.13-2.1 from http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_Factory/
  • From: Markus Koßmann <mkossmann_ml1@xxxxxx>
  • Date: Mon, 26 Jan 2009 18:22:51 +0100
  • Message-id: <200901261822.51513.mkossmann_ml1@xxxxxx>
Am Montag, 26. Januar 2009 schrieb Rainer Klier:
hi list,

i think, there is a bug in the latest factory-kernel 2.6.27.13-2 from
http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_Factory/.

at least the kernel source has a bug, i think.

i tried to install latest nvidia-driver 180.22 on an opensuse11.1 x86_64
system. former kernel 2.6.27.12-1 had no problems with this.
but this time, it was not possible to load nvidia kernel module.

the installation-script stopped, and told me that the built kernel module
can't be loaded.

there were also warnings about missing symbols at compile time.

this is the relevant part of dmesg-output when loading the driver:
nvidia: Unknown symbol pv_mmu_ops
nvidia: Unknown symbol pv_cpu_ops
nvidia: Unknown symbol pv_irq_ops
nvidia: Unknown symbol pv_lock_ops

it seems, the above symbols are missing.

this was not the case with 2.6.27.12-1.

i had to downgrade kernel to latest available 2.6.27.7-9 from oss-repo.
with this version building the nvidia driver also was no problem.
right now i am writing this mail with this setup.

there must have been some changes between 2.6.27.12-1 and 2.6.27.13-2 which
have something to do with these missing symbols.
Hmm , I'am running 2.6.27.13-HEAD_20090125010735_8d0b1ab5-default x86_64 from
http://ftp.suse.com/pub/projects/kernel/kotd/HEAD/x86_64/ and I had no
problems to build 180.22.
However I didn't clone the configuration from the previous version , but used
the SUSE default configuration from linux-2.6.27.13-
HEAD_20090125010735_8d0b1ab5-obj/x86_64/default/.config



--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kernel+help@xxxxxxxxxxxx

< Previous Next >
References