Hi Frank, At 28 Jan 2002 07:08:09 +0100, Frank Schafer wrote: > > My devfsd contains: > LOOKUP snd MODLOAD ACTION snd > REGISTER sound/.* PERMISSIONS root.root 660 > REGISTER snd/.* PERMISSIONS root.root 660 This definition allows only root user to access sound devices. I believe this is the problem.
Try to change from root.root to root.audio (if audio group exists) or simply permit all 666 instead of 660. The other symptoms your wrote are normal. > # ls -l /proc/asound/card1 > -rw-r--r-- 1 root root 0 Jan 27 11:30 ak4531 > -rw-r--r-- 1 root root 0 Jan 27 11:30 audiopci > -r--r--r-- 1 root root 0 Jan 27 11:30 midiD0 > -rw-r--r-- 1 root root 0 Jan 27 11:30 mixerD0 > -rw-r--r-- 1 root root 0 Jan 27 11:55 pcmD0o > -rw-r--r-- 1 root root 0 Jan 27 11:55 pcmD1o > -r--r--r-- 1 root root 0 Jan 27 11:30 pcmloopD0S0c > -r--r--r-- 1 root root 0 Jan 27 11:30 pcmloopD0S0p > -r--r--r-- 1 root root 0 Jan 27 11:30 pcmloopD1S0p > > As you see I get a lot of empty files in `/proc/asound/cards'. It's OK. you don't know the size of proc files. > By the way: If I load soundcore before snd-card-ens1370 I get > soundcore 3344 0 [snd] > from lsmod; If I don't load soundcore, I get > soundcore 3344 2 [snd] > from `lsmod' after loading snd-card-ens1370. Hmm, this looks strange but I guess it's some mystery of modprobe :) > In this approach I included soundcore and ens1370 as modules in the > kernel config, and I've removed the ens1370.o after `make > modules_install'. > > So far, so good. I made a kernel recompile with sound support compiled > into the kernel without any soundcard as says the HOWTO. Then I rebuilt > the driver with full debug. > Here are the results: > > After the `modprobe snd-card-ens1370' I get from the syslog: > (none) kernel: PCI: Found IRQ 11 for device 00:08.0 > > ... that's all. From here on all is as described above. Yes, that implies that everything all right. > .. whooooo ... trying insmod ... > > # insmod snd-card-ens1370 > /lib/modules/2.4.16/misc/snd-card-ens1370.o: unresolved symbol > snd_card_unregist > er > ... insmod is different from modprobe. it doesn't load other required modules. > > Turning kmod on, and adding: > > # ALSA portion > alias char-major-116 snd > alias snd-card-0 snd-card-ens1370 > # > # (n)OSS - OSS/FREE portion > alias char-major-14 soundcore > 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 > > to modules.conf doesn't change anything. They are anyway necessary. > ./sndstat > Sound Driver:3.8.2-980706 (ALSA v0.5.12a emulation code) > Kernel: Linux (none) 2.4.16 #1 Sun Jan 27 12:22:42 CET 2002 i686 > Config options: 0 > > Installed drivers: > Type 10: ALSA emulation > > Card config: > Ensoniq AudioPCI ES1370 at 0xe400, irq 11 > > Audio devices: NOT ENABLED IN CONFIG > > Synth devices: NOT ENABLED IN CONFIG > > Midi devices: > 0: ES1370 > > Timers: > 7: system timer > > Mixers: NOT ENABLED IN CONFIG > > ( In which config and how can I enable the not enabled devices mentioned > here? ) The devices in sndstat are for OSS emulation. They appear only when snd-pcm-oss and snd-mixer-oss modules are loaded. (And "Synth" is never shown. It's a known feature :) > As we can't expect in any other kind `amixer' outputs: > > The ALSA sound driver was not detected in this system. > Most likely the devfs permission problem as described above. THT ciao, Takashi _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
