No sound after reboot - how can I manage that without alsaconf?

[David Moerike-2]

After a reboot, on my system there often is no sound at all, or it is on
the first (onboard) soundcard. I normally use the second one.

Until now, I managed this by running - as root - alsaconf. However, this
is not good because:

- when kernel 2.6.30-1 is running, there always is no sound at all, and
alsaconf finds no soundcards. It only works with kernel 2.6.26-2

- alsaconf only is available when downgrading package alsa-utils from
testing to lenny.

How can I manage it without alsaconf?

lspci -vnn

...

00:1d.0 Audio device [0403]: ALi Corporation High Definition Audio/AC'97
Host Controller [10b9:5461]
    Subsystem: Acer Incorporated [ALI] Device [1025:0085]
    Flags: bus master, medium devsel, latency 64, IRQ 22
    Memory at ff6f8000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: <access denied>
    Kernel driver in use: HDA Intel
    Kernel modules: snd-hda-intel
...

07:11.0 Multimedia audio controller [0401]: C-Media Electronics Inc
CM8738 [13f6:0111] (rev 10)
    Subsystem: C-Media Electronics Inc CMI8738/C3DX PCI Audio Device
[13f6:0111]
    Flags: bus master, medium devsel, latency 64, IRQ 21
    I/O ports at c800 [size=256]
    Capabilities: <access denied>
    Kernel driver in use: C-Media PCI
    Kernel modules: snd-cmipci
...

System: Acer Power F5, Pentium 4, Squeeze.

David


--
To UNSUBSCRIBE, email to debian-testing-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[David Moerike-2]

jan peschke schrieb:

> Hi David, I solved this problem sorting my soundcards while loading the
> modules. I just put a file named something like "sound.conf" under
> /etc/modprobe.d/ with the following content:
>
> alias snd-card-0 snd-cmipci
> options snd-cmipci index=0
> options saa7134-alsa index=1
>
>
> The important thing is the index=<n> .
> regards
> Jan
>  

I found that making a correct file /etc/modprobe.d/sound.conf (the last
line is different because the Onboard soundcard is Intel) had no effect.

I found that instead of executing alsaconf I can - as root - execute

*alsa force-reload* but it does not work always.

The best thing is what follows: I made a completely new installation of
Squeeze, with the netinst CD

*Official Snapshot i386 NETINST Binary-1 20091006-17:02*

that is that from October 6th, and after only one time alsa
*force-reload* everything works fine, although a
/etc/modprobe.d/sound.conf file does not exist at all. Seems that the
new system is more intelligent!

Is, be default, the second soundcard used? Or need I simply choose it in
the Gnome mixer (that is what I did)?

Now my system always hangs when during boot, or during returning from
hibernation, the X Server starts (switching the screen to graphics
mode). However after downgrading the kernel to 2.6.26-2 this problem
disappeared, and I hope that in the future the system will also run with
the new kernel.

David


--
To UNSUBSCRIBE, email to debian-testing-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[David Moerike-2]

I found that sometimes again the sound is gone! However, I only need to
run alsa force-reload and that is much faster than before, when I ran
alsaconf.

David

David schrieb:
> I found that making a correct file /etc/modprobe.d/sound.conf (the last
> line is different because the Onboard soundcard is Intel) had no effect.
>
> I found that instead of executing alsaconf I can - as root - execute
>
> *alsa force-reload* but it does not work always ...


--
To UNSUBSCRIBE, email to debian-testing-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...