| 1 |
karlos schreef: |
| 2 |
> hi |
| 3 |
> |
| 4 |
> I have tried the meterbridge and alsamixer settings but no input. |
| 5 |
> there are a few things I really don't why they happen, for example |
| 6 |
> does alsa not start off correctly during boot, no errors and modules |
| 7 |
> get loaded, but it when I want to start alsamixer after I log on, it |
| 8 |
> complains that there are no elements to display. Same with jack, it |
| 9 |
> cannot connect until alsa is restarted manually. no errors there |
| 10 |
> either. I have included all I can think of now, I hope that there is a |
| 11 |
> solution out there. |
| 12 |
> here is lsmod for example.. |
| 13 |
> |
| 14 |
> karlos@posthuman ~ $ lsmod | grep snd |
| 15 |
> snd_pcm_oss 49312 0 |
| 16 |
> snd_mixer_oss 18432 1 snd_pcm_oss |
| 17 |
> snd_seq_midi 7840 0 |
| 18 |
> snd_virmidi 4288 0 |
| 19 |
> snd_seq_virmidi 7168 1 snd_virmidi |
| 20 |
> snd_seq_midi_event 6912 2 snd_seq_midi,snd_seq_virmidi |
| 21 |
> snd_seq 53264 3 snd_seq_midi,snd_seq_virmidi,snd_seq_midi_event |
| 22 |
> snd_usb_audio 74944 0 |
| 23 |
> snd_usb_lib 15104 1 snd_usb_audio |
| 24 |
> snd_rawmidi 21920 3 snd_seq_midi,snd_seq_virmidi,snd_usb_lib |
| 25 |
> snd_seq_device 8332 3 snd_seq_midi,snd_seq,snd_rawmidi |
| 26 |
> snd_hwdep 8480 1 snd_usb_audio |
| 27 |
> snd_intel8x0 30784 0 |
| 28 |
> snd_ac97_codec 84220 1 snd_intel8x0 |
| 29 |
> snd_pcm 84100 4 |
| 30 |
> snd_pcm_oss,snd_usb_audio,snd_intel8x0,snd_ac97_codec |
| 31 |
> snd_timer 22916 2 snd_seq,snd_pcm |
| 32 |
> snd 48228 14 |
| 33 |
> 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 |
| 34 |
> snd_page_alloc 8836 2 snd_intel8x0,snd_pcm |
| 35 |
> |
| 36 |
> could it be, these are all loaded as OSS?? I once heard underscores |
| 37 |
> mean OSS is beeing used. that would be very strange. |
| 38 |
> |
| 39 |
> here are alsa restart: |
| 40 |
> |
| 41 |
> posthuman karlos # /etc/init.d/alsasound restart |
| 42 |
> * WARNING: you are stopping a boot service. |
| 43 |
> * Storing ALSA Mixer Levels ... [ ok ] |
| 44 |
> * Unloading ALSA ... [ ok ] |
| 45 |
> * Unloading ALSA modules ... [ ok ] |
| 46 |
> * Loading ALSA modules ... |
| 47 |
> * Loading: snd-card-0 ... [ ok ] |
| 48 |
> * Loading: snd-card-1 ... [ ok ] |
| 49 |
> * Loading: snd-card-2 ... [ ok ] |
| 50 |
> * Loading: snd-seq-midi ... [ ok ] |
| 51 |
> * Restoring Mixer Levels ... [ ok ] |
| 52 |
> |
| 53 |
> what could this possibly be??? |
| 54 |
> |
| 55 |
> thanks, |
| 56 |
> |
| 57 |
> |
| 58 |
> karsten |
| 59 |
|
| 60 |
I have often found that alsasound is quite picky about the way it must |
| 61 |
all be set up in order for everything to load correctly. |
| 62 |
|
| 63 |
First thing is-- I know that the Handbook suggests to set it alsasound |
| 64 |
in the boot runlevel, but I find it works better when set in the default |
| 65 |
runlevel. Ime, alsasound vastly prefers modules rather than static |
| 66 |
compiles wherever possible, and in the boot runlevel, the modules are |
| 67 |
not loaded yet, as modules.autoload.d/kernel-2.x has not yet run. |
| 68 |
|
| 69 |
I suspect you may basically be asking alsasound to load modules before |
| 70 |
they are available, either statically, or certainly as modules. Besides, |
| 71 |
you don't need sound in the boot runlevel anyway-- what is there to hear? |
| 72 |
|
| 73 |
Hope this helps, |
| 74 |
Holly |
| 75 |
|
| 76 |
-- |
| 77 |
gentoo-user@g.o mailing list |
Archives