14894 – emu10k1 module reports unresolved symbols after installation

Bug 14894 - emu10k1 module reports unresolved symbols after installation

Summary: emu10k1 module reports unresolved symbols after installation

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	New packages (show other bugs)
Hardware:	x86 Linux

Importance:	High normal (vote)
Assignee:	SpanKY

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2003-01-31 23:58 UTC by Terry L. Triplett
Modified:	2003-02-04 19:42 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Terry L. Triplett 2003-01-31 23:58:28 UTC

After emerging the latest emu10k1 ebuild (emu10k1-0.20a-r1), the kernel reports "Unresolved 
symbols in /lib/modules/2.4.19-gentoo-r10/kernel/drivers/sound/emu10k1/emu10k1.o" when 
attempting to load the module. 
 
FIX: 
I located a description of the problem and a fix at: http://www.justlinux.com/nhf/Soundcards 
(at the bottom in the section titled "The Fix to the Hated unresolved symbols Errors").  The fix 
mentions that setting MODVERSIONS=y in the Makefile fixes the problem.  I tried adding ' echo 
"MODVERSIONS := y" > config ' to the src_compile() section of the ebuild and re-emerging.  
This seems to fix the problem for me - the module now loads fine. 

Reproducible: Always
Steps to Reproduce:
1. unmerge emu10k1 
2. (optional) reboot 
3. emerge emu10k1 
4. modprobe emu10k1 
Actual Results:  
See details. 

Expected Results:  
The module should have loaded with no problem.

Comment 1 SpanKY gentoo-dev

2003-02-01 00:04:59 UTC

whats the error msg you get ?

Comment 2 SpanKY gentoo-dev

2003-02-03 02:20:52 UTC

ok, i added your fix to cvs, thanks for the extended details :)

Comment 3 SpanKY gentoo-dev

2003-02-03 02:21:54 UTC

hmm, meant to close bug