As I suspected, the modules aren't loaded so alsa isn't even running. Hence your original "open" error(s). How did you install alsa? Not that I think it is your issue, but it could be. If you boot with lilo, you need to re-install lilo after creating a new kernel. Even if it's technically the same version of your old kernel. Although most distros default to grub these days. So not likely. If you compiled from source at least for some modules, you'll need to reboot to use the new kernel and the new modules. Not really applicable to sound as you probably didn't change any PCIe or other internals to gain the functionality. In the old days if you compiled from source you could insmod (modprobe) the modules in alsa-driver-???/modules/ until you got the right order and all of the modules loaded. This is representative of the errors that you're seeing. You can't load a certain module because another module wasn't loaded before it. That has those symbols (functions) that it needs. Which brings things full circle to alsa isn't properly installed. $ sudo dpkg -l '*alsa*' Only pay attention to the ones that start alsa or alsa-. On my debian setup (similar to ubuntu) I have alsa, alsa-base, alsa-firmware-loaders, alsa-headers, alsa-source, alsa-tools, alsa-tools-gui, and alsa-utils. On my system all of those are installed, except alsa-firmware-loaders, alsa-headers (needed to compile other things from source against it), and alsa-tools-gui. IMO you are probably missing alsa-base. This should have entries in /etc/modprobe.d/alsa* for autoloading your modules (without concerning yourself about the order of insertion). It could also be that you haven't run depmod -a, or your distro didn't. Which updates a sort of list of what modules are related so they can also load when the other is loaded. IME, alsa is independent of this list and relies on other things (/etc/modprobe.d/). If you haven't solved your issue by now, I guess you're stuck with the old school ways. Meaning you'll likely have to create a /etc/modprobe.d/ entry for alsa so it can auto load at boot. Which might look something like: #--- START - /etc/modprobe.d/alsa_custom.conf ---# alias char-major-116 snd alias char-major-14 soundcore options snd major=116 cards_limit=3 # duplicate this following sequence for each soundcard you have # and bump (or omit) the index=# depending on the order / priority # that you desire. And adjust the first # in the sound- aliases to # match the index number. # your specific module NEXT LINE (and the next one) options snd-hda-intel index=0 alias snd-card-0 snd-hda-intel # this one assumes OSS emulation, you might need to # reference alsa-project.org to find a different one if you # opted out on that option. --with-oss=yes ? # (been a while) alias sound-slot-0 snd-card-0 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-oss #--- END ---# And 20 years after linux started, we're still configuring sound from the command line. Be sure to reboot OR try to use the soundcard to get the modules to auto magically load. They generally load at boot because your distro will likely try to restore mixer settings. And therefor try to use your soundcard. (which is or was failing for you) - James On 2/12/11, Marcin Szyniszewski <mszynisz@xxxxxxxxx> wrote: > Thank you all for the replies! Very appreciated! :) > >> $ sudo modprobe [module] > FATAL: Error inserting snd > (/lib/modules/2.6.35-25-generic/kernel/sound/acore/snd.ko): Unknown > symbol in module, or unknown parameter (see dmesg) > WARNING: Error running install command for snd > WARNING: Error inserting snd_pcm > (/lib/modules/2.6.35-25-generic/kernel/sound/acore/snd-pcm.ko): > Unknown symbol in module, or unknown parameter (see dmesg) > WARNING: Error inserting snd_hwdep > (/lib/modules/2.6.35-25-generic/kernel/sound/acore/snd-hwdep.ko): > Unknown symbol in module, or unknown parameter (see dmesg) > WARNING: Error inserting snd_hda_codec > (/lib/modules/2.6.35-25-generic/kernel/sound/pci/hda/snd-hda-codec.ko): > Unknown symbol in module, or unknown parameter (see dmesg) > FATAL: Error inserting snd_hda_intel > (/lib/modules/2.6.35-25-generic/kernel/sound/pci/hda/snd-hda-intel.ko): > Unknown symbol in module, or unknown parameter (see dmesg) > > This doesn't look good. What do you think is wrong?? > >> Note that * is a wildcard. So /dev/dsp* is any devices that start >> with /dev/dsp. > Yes, of course. I did "ll" in this folder and went through the whole > list. Nothing's there. > > # modprobe snd-hda-intel > Gives me permission errors. > > $ sudo modprobe snd-hda-intel > Gives the result above. > > $ sudo pavucontrol > sudo: pavucontrol: command not found > > $ lsmod | grep -i "snd" > snd_page_alloc 7120 0 > > $ cat /proc/asound/cards > cat: /proc/asound/cards: No such file or directory > >> /dev/dsp and /dev/audio are the oss sound drivers, not alsa. alsa has an >> oss >> emulation module, which will create those but they are NOT needed for >> using >> alsa. What you have under alsa is a buch of entry points under /dev/snd >> >> Now if your program uses the oss sound system, then you must load the >> alsa-oss >> emulators as well (snd_seq_oss, snd_pcm_oss snd_mixer_oss) >> This will generate the various /dev/dsp entry points. > > And how to load these emulators?? > > There is a folder /dev/snd. No other folders that begin with snd*. > /dev/snd$ ll > total 0 > drwxr-xr-x 2 root root 80 2011-02-12 12:11 ./ > drwxr-xr-x 18 root root 3900 2011-02-12 12:11 ../ > crw------- 1 root root 116, 1 2011-02-12 12:11 seq > crw------- 1 root root 116, 33 2011-02-12 12:11 timer > > $ ls -l /dev/* /dev/*/* | grep -i "audio" > ls: cannot access /dev/fd/255: No such file or directory > ls: cannot access /dev/fd/3: No such file or directory > lrwxrwxrwx 1 root root 9 2011-02-12 12:11 > usb-USB_Audio_Device_Acer_Crystal_Eye_webcam-event-if00 -> ../event6 > lrwxrwxrwx 1 root root 12 2011-02-12 12:11 > usb-USB_Audio_Device_Acer_Crystal_Eye_webcam-video-index0 -> > ../../video0 > > I also tried to run dmesg, but I won't post output here, as it's too > long. In short, I could see there many many many entries like that: > [ 1191.589110] snd: Unknown symbol unregister_sound_special (err 0) > [ 1191.589703] snd: Unknown symbol register_sound_special_device (err 0) > [ 1191.592939] snd_seq_device: Unknown symbol snd_info_register (err 0) > [ 1191.593097] snd_seq_device: Unknown symbol > snd_info_create_module_entry (err 0) > [ 1191.593254] snd_seq_device: Unknown symbol snd_info_free_entry (err 0) > [ 1191.593410] snd_seq_device: Unknown symbol snd_seq_root (err 0) > [ 1191.593584] snd_seq_device: Unknown symbol __snd_printk (err 0) > [ 1191.593741] snd_seq_device: Unknown symbol snd_iprintf (err 0) > [ 1191.593981] snd_seq_device: Unknown symbol snd_device_new (err 0) > > Do you see any solution to this problem? Please help me, as I'm > totally lost in this :( > > Best, > *mszynisz* > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Alsa-user mailing list > Alsa-user@xxxxxxxxxxxxxxxxxxxxx > https://lists.sourceforge.net/lists/listinfo/alsa-user > ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
