Thus spake Brian Clark: > * 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? Just a thought - the soundblaster and soundblaster live! are different chipsets - the live! uses the emu10k1 and the others use the sb or any of a number of other modules. If you're unsure about which version of soundblaster, try lspci - it'll be pretty clear about which one you have. HTH, Steve -- I prefer the most unjust peace to the most righteous war. -- Cicero Even peace may be purchased at too high a price. -- Poor Richard
Attachment:
pgpL_CB3NRE_N.pgp
Description: PGP signature