karlos schreef: > hi > > I have tried the meterbridge and alsamixer settings but no input. > there are a few things I really don't why they happen, for example > does alsa not start off correctly during boot, no errors and modules > get loaded, but it when I want to start alsamixer after I log on, it > complains that there are no elements to display. Same with jack, it > cannot connect until alsa is restarted manually. no errors there > either. I have included all I can think of now, I hope that there is a > solution out there. > here is lsmod for example.. > > [EMAIL PROTECTED] ~ $ lsmod | grep snd > snd_pcm_oss 49312 0 > snd_mixer_oss 18432 1 snd_pcm_oss > snd_seq_midi 7840 0 > snd_virmidi 4288 0 > snd_seq_virmidi 7168 1 snd_virmidi > snd_seq_midi_event 6912 2 snd_seq_midi,snd_seq_virmidi > snd_seq 53264 3 > snd_seq_midi,snd_seq_virmidi,snd_seq_midi_event > snd_usb_audio 74944 0 > snd_usb_lib 15104 1 snd_usb_audio > snd_rawmidi 21920 3 snd_seq_midi,snd_seq_virmidi,snd_usb_lib > snd_seq_device 8332 3 snd_seq_midi,snd_seq,snd_rawmidi > snd_hwdep 8480 1 snd_usb_audio > snd_intel8x0 30784 0 > snd_ac97_codec 84220 1 snd_intel8x0 > snd_pcm 84100 4 > snd_pcm_oss,snd_usb_audio,snd_intel8x0,snd_ac97_codec > snd_timer 22916 2 snd_seq,snd_pcm > snd 48228 14 > snd_pcm_oss,snd_mixer_oss,snd_virmidi,snd_seq_virmidi,snd_seq,snd_usb_audio,snd_usb_lib,snd_rawmidi,snd_seq_device,snd_hwdep,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer > snd_page_alloc 8836 2 snd_intel8x0,snd_pcm > > could it be, these are all loaded as OSS?? I once heard underscores > mean OSS is beeing used. that would be very strange. > > here are alsa restart: > > posthuman karlos # /etc/init.d/alsasound restart > * WARNING: you are stopping a boot service. > * Storing ALSA Mixer Levels ... [ ok ] > * Unloading ALSA ... [ ok > ] > * Unloading ALSA modules ... [ ok ] > * Loading ALSA modules ... > * Loading: snd-card-0 ... [ ok ] > * Loading: snd-card-1 ... [ ok ] > * Loading: snd-card-2 ... [ ok ] > * Loading: snd-seq-midi ... [ ok ] > * Restoring Mixer Levels ... [ ok ] > > what could this possibly be??? > > thanks, > > > karsten
I have often found that alsasound is quite picky about the way it must all be set up in order for everything to load correctly. First thing is-- I know that the Handbook suggests to set it alsasound in the boot runlevel, but I find it works better when set in the default runlevel. Ime, alsasound vastly prefers modules rather than static compiles wherever possible, and in the boot runlevel, the modules are not loaded yet, as modules.autoload.d/kernel-2.x has not yet run. I suspect you may basically be asking alsasound to load modules before they are available, either statically, or certainly as modules. Besides, you don't need sound in the boot runlevel anyway-- what is there to hear? Hope this helps, Holly -- gentoo-user@gentoo.org mailing list
