Christoph Hellwig wrote:
> We don't support propritary modules.
The original report (#284356) was submitted by Joey Hess and made no
reference to proprietary modules. This affects modules shipped by
Debian too.
The problem is that a new Debian release of the "same" kernel (2.4.27-1)
has changed symbol version suffixes, thus breaking modules that were
compiled against earlier releases of this kernel.
Message-Id: <1102350007. 25052.98. camel@thanatos>
Date: Mon, 06 Dec 2004 17:20:08 +0100
From: Thomas Hood <email address hidden>
To: <email address hidden>
Cc: <email address hidden>,
<email address hidden>, <email address hidden>,
<email address hidden>
Subject: New release changed symbols thus rendering modules unloadable
reopen 284356 image-2. 4.27-i386 image-2. 4.27-i386 image-2. 4.27-i386 image-2. 4.27-i386
severity 284356 important
reassign 284356 kernel-
reassign 284371 kernel-
severity 284463 important
tags 284463 - pending
reassign 284463 kernel-
severity 284181 important
tags 284181 - pending
reassign 284181 kernel-
merge 284356 284371 284463 284181
thanks
Christoph Hellwig wrote:
> We don't support propritary modules.
The original report (#284356) was submitted by Joey Hess and made no
reference to proprietary modules. This affects modules shipped by
Debian too.
The problem is that a new Debian release of the "same" kernel (2.4.27-1)
has changed symbol version suffixes, thus breaking modules that were
compiled against earlier releases of this kernel.
--
Thomas Hood