[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Re: sound blaster



On Wed, 26 Dec 2001 22:55:49 -0500, Brian Clark <brianj@fusionwerks.com> wrote:

> * Marcelo B. Bianchi (mbianc@pobox.com) [Dec 26. 2001 21:04]:
> 
> > After the reboot try load the module,
> 
> > modprobe emu10k1
> 
> I recentl;y had the same problem, but put it off for a while. This is
> what I get (the same card, same module - but the creative sources):
> 
> % modprobe emu10k1
> /lib/modules/2.2.19/misc/emu10k1.o: unresolved symbol mem_map_Rada6f066
> /lib/modules/2.2.19/misc/emu10k1.o: unresolved symbol
> __wake_up_R488028a0
> /lib/modules/2.2.19/misc/emu10k1.o: unresolved symbol
> interruptible_sleep_on_R0ca77f9d
> /lib/modules/2.2.19/misc/emu10k1.o: unresolved symbol
> register_sound_midi_Rfae787dd
> /lib/modules/2.2.19/misc/emu10k1.o: unresolved symbol
> register_sound_dsp_Rf393da98
> /lib/modules/2.2.19/misc/emu10k1.o: unresolved symbol
> __pollwait_R08b1d5fb
> /lib/modules/2.2.19/misc/emu10k1.o: unresolved symbol
> register_sound_mixer_Re7b6312f
> /lib/modules/2.2.19/misc/emu10k1.o: Note: modules without a GPL
> compatible license cannot use GPLONLY_ symbols
> /lib/modules/2.2.19/misc/emu10k1.o: insmod
> /lib/modules/2.2.19/misc/emu10k1.o failed
> /lib/modules/2.2.19/misc/emu10k1.o: insmod emu10k1 failed
> 
> And that business about the GPL -- good grief! :))
> 
> I'm starting to think I'll never have my sanity return. These headphones
> may get glued to my skull soon. ;)
> 
> Penny for your thoughts?

Well the module just isn't  'marked' as GPL but it is, just look into the source codes !! Not everything is perfect, YET :)) 

Well here i have a sblive card + debian testing + kernel 2.4.16 and i use the driver that comes with the kernel, i put sound support inside the kernel and configure the modules i want, in that case em10k1 and put SBlive MID support inside the module. 

And after booting i have no errors and when i see there are 3 modules loaded for the sound 

emu10k1                54592   0 (unused)
sound                     52332   0 [emu10k1]
ac97_codec              9504   0 [emu10k1]

maybe you can use the command nm to trace objects inside the modules,  for example, 
sparrow:/lib/modules# nm 2.4.16/kernel/drivers/sound/emu10k1/emu10k1.o  | grep register_sound 
         U register_sound_dsp
         U register_sound_midi
         U register_sound_mixer
         U unregister_sound_dsp
         U unregister_sound_midi
         U unregister_sound_mixer

note the U for unresolved !!  (man nm)

and then cause i compiled the sound inside the kernel these calls should be inside the kernel so i get my uncompressed image (/usr/src/linux/vmlinux) and then 

sparrow:/usr/src/linux# nm vmlinux | grep register_sound 
c0212914 ? __kstrtab_register_sound_dsp
c0212900 ? __kstrtab_register_sound_midi
c02128eb ? __kstrtab_register_sound_mixer
c02128d4 ? __kstrtab_register_sound_special
c0212927 ? __kstrtab_register_sound_synth
c0212982 ? __kstrtab_unregister_sound_dsp
c021296c ? __kstrtab_unregister_sound_midi
c0212955 ? __kstrtab_unregister_sound_mixer
c021293c ? __kstrtab_unregister_sound_special
c0212997 ? __kstrtab_unregister_sound_synth
c0217eb8 ? __ksymtab_register_sound_dsp
c0217eb0 ? __ksymtab_register_sound_midi
c0217ea8 ? __ksymtab_register_sound_mixer
c0217ea0 ? __ksymtab_register_sound_special
c0217ec0 ? __ksymtab_register_sound_synth
c0217ee0 ? __ksymtab_unregister_sound_dsp
c0217ed8 ? __ksymtab_unregister_sound_midi
c0217ed0 ? __ksymtab_unregister_sound_mixer
c0217ec8 ? __ksymtab_unregister_sound_special
c0217ee8 ? __ksymtab_unregister_sound_synth
c01a262c T register_sound_dsp
c01a2600 T register_sound_midi
c01a25d4 T register_sound_mixer
c01a251c T register_sound_special
c01a2658 T register_sound_synth
c01a26c8 T unregister_sound_dsp
c01a26b4 T unregister_sound_midi
c01a26a0 T unregister_sound_mixer
c01a2684 T unregister_sound_special
c01a26dc T unregister_sound_synth

so these unresolved symbol on em10k1 (register_sound_) is inside my kernel so no dependency problems
trying to load these module against my kernel.

marcelo~



Reply to: