Re: Lost front speakers with 2.6.13-1.1526_FC4 (SB Live 5.1 Gamer)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Patrick <fedora@xxxxxxxxxxxxxxxxx> writes:

> On Sun, 2005-10-02 at 08:19 -0500, Jeff Vian wrote:
> [snip]
>> > Since there are now more reports than one let me add my 2 cents. I use
>> > slmodemd on top of the snd-atiixp-modem module to activate the softmodem
>> > on my laptop. On kernel 2.6.12-1.1447 it works fine using modem:1,0 as
>> > the device. On kernel 2.6.13-1.1526 it fails. I'm reporting it because
>> > the snd-atiixp-modem module is part of the Alsa sound libs.
>> > 
>> did you recompile slmodemd on the new kernel?
>
> Yup and I also figured out that it was not caused by the kernel upgrade
> (doh!). It is caused by the /etc/alsa/cards/aliases.conf file. Here is
> the error message:
> ALSA lib conf.c:1578:(snd_config_load1) _toplevel_:51:23:No such file or
> directory
> ALSA lib conf.c:2823:(snd_config_hook_load) /etc/alsa/cards/aliases.conf
> may be old or corrupted: consider to remove or fix it
> ALSA lib conf.c:2686:(snd_config_hooks_call) function
> snd_config_hook_load returned error: No such file or directory
> ALSA lib pcm.c:1959:(snd_pcm_open_conf) Invalid type for PCM modem:1,0
> definition (id: modem, value: cards.pcm.modem)
> error: alsa setup: cannot open playback device 'modem:1,0': Invalid
> argument
> error: cannot setup device `modem:1,0'
>
> Now if I can figure out what's wrong with the file I can fix it. No luck
> so far so the search continues.

I ran into a similar problem last week. My laptop hung and when it
came back up, I had no sound, and got the same sort of messages from
esd. I don't know for sure if it was the crash or some update I did
before the hang.

I ran strace on esd, and found that a file was missing (just not
aliases.conf). I kind of fixed it my running ainit (as root), but the
permissions on the devices were messed up, so I had to run esd as
root. I also had permissions problems accessing /dev/scd0.

It's possible that some package update made some devices inaccessible
to normal users, and this is just part of the fallout.


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux