Yes, you're ABSOLUTELY right. It's missing firmware. Thanks for your help, I truly do not understand how did you found out that, but that's not important. But, unfortunatelly, info you've mailed to me is not enough for me, because as I said: >... I have absolutely NO knowledge of linux administration and so on. I can download sources, configure them via ./configure, make them and then run make install. But what next? What's name of compiled module so I can call modprobe? Is it this the thing I should do? I do not know, can you help me with it? (Actually I do know ANYTHING about kernel, do not know what modprobe etc does, don't know ANYTHING about sound in linux, etc. etc ...) I'm using Kubuntu for work (java programming, some basic work), I'm not capable of playing with the system itself. I just want to play music through jack for music quality reasons. So what's the valid sequence of action I need to take? I've tried to find that info myself, but almost EVERY info/guide is written for REALLY experienced users, so I mostly do not understand what is article about... thanks for every hint. alfonz. 2009/5/3 Giuliano Pochini <pochini@xxxxxxxx>: > On Sat, 2 May 2009 20:31:11 +0200 > Martin Mucha <alfonz19@xxxxxxxxx> wrote: > >> Hi, >> >> I'm having REALLY bad times with alsa. But maybe it's just because I >> have absolutely NO knowledge with linux administration and so on. >> >> I've bought alsa compatible card. Here's installation guide >> http://www.alsa-project.org/main/index.php/Matrix:Module-echo3g > > Overly complicated document. Just do: > > ./configure --with-cards=echo3g ; make ; make install ; modprobe snd-echo3g > > >> I've finally managed to compile alsa-utils, alsa-lib and alsa-driver >> (not in that order), simply by following that guide. I have no idea >> what NB shortcut means but I have to run >> ./snddevices >> contrary to claim >> NB:If you are using drivers before 0.9.4 then you need to run ... >> since otherwise /dev/snd does not contain new devices. > > If you are using a distro which uses udev (I'm not aware of any recent one > that doesn't) you don't have to create device nodes in /dev because udev > automatically does it for you as soon as a new device appears. > > >> I've inserted modules to kernel with >> modprobe snd-echo3g ; modprobe snd-pcm-oss ; modprobe snd-mixer-oss ; >> modprobe snd-seq-oss >> and they are printed out with command >> lsmod >> so I think this is ok. > > Does "dmesg" show any error ? If it couldn't find the firmware, you forgot > to compile and install alsa-firmware. > > >> But when I run alsamixer (or amixer), which is >> in installation guide the next step, I'm getting message >> alsamixer: function snd_ctl_open failed for default: No such device > > Use aplay -l or arecord -l to get the list of available devices. > > >> What's wrong? > > It's likely you forgot the firmware. > > > -- > Giuliano. > ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
