[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]
Re: no longer sound on amd64 sid systems
Subject: Re: no longer sound on amd64 sid systems
Date: Wed, 14 May 2014 18:18:41 +0200
Thanks for your prompt response Elimar. I've made some replies in-line below. In my ignorance I do not know how to respond so that an > is added at the beginning of quoted lines so I have just made all my new remarks italic; happy if you can enlighten me how it should be done.
Any further tips you have I'd be most grateful for.
Best,
/Paul
[...]
> Hi,
>
>
> First, apologies if I'm not posting this request the way one should, I
> don't think I ever tried to ask a question on this forum before, so if I
> should have done it differently please advise me.
And now I am not sure whether this is the right way to reply, I just copied everything and pasted it into a mail client (don't use the default Kmail for the moment).
>
>
> I'm having exactly the same grief as Arne, since the latest update of
> wheezy on my HP Pavilion dm1. I'm a musician and use pd-extended live on
> stage, not to mention the fact that I cannot play or record anything
> anymore, so I'd be hugely grateful for any help.
>
> As a last resort I could roll back the latest updates from Debian but I
> don't at present know how so that would also be a lot of time-consuming
> work I imagine.
>
>
> Here's the output on my machine as requested of Arne:
>
>
>
> ... lsmod | grep snd
>
> snd_pcm 76785 0
>
> snd_hwdep 13189 0
>
> snd_page_alloc 13052 1 snd_pcm
>
> snd_seq 53391 0
>
> snd_seq_device 13132 1 snd_seq
>
> snd_timer 22767 2 snd_seq,snd_pcm
>
> snd 61901 5 snd_timer,snd_seq_device,snd_seq,snd_hwdep,snd_pcm
>
> soundcore 13065 1 snd
There is now card specific sound driver loaded. You have to find out
which soundchip you are running and load the respective driver,
though. But this should be done automagic by udev so there is
something wrong with your kernel, half configured packages or
something like that.
I reverted to the previous kernel, no joy, then re-installed the new one (KDE prompted me to do this when it discovered I was running an old kernel), so I cannot see how there could be anything wrong with the package or configuration, all handled automagically. Have browsed udev rules superficially but don't get much at this point.
>
> __________
>
>
> ... aplay -l
>
> aplay: device_list:252: no soundcards found...
Because there is no sound driver loaded.
OK, even though I unloaded and reloaded all the snd modules, obviously I have not understood something.
>
> ... aplay -L
>
> default
>
> Playback/recording through the PulseAudio sound server
>
> __________________________________________________________
> ... dpkg -l |egrep alsa
Ok.
[...]
> ... dpkg -l |egrep asound
[...]
> ... cat /proc/version
> 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.57-3+deb7u1
Ok, looks not customized.
> alsamixer says there are no sound cards.
Because there is no sound driver loaded.
I'm not sure why, the snd modules were all there, but I will try to find and load a new driver package.
>
> KDE tells me this:
>
>
> [image: Inline images 1]
Not found. But not common to send to a mailing list anyway.
It was a warning from KDE saying
This is the list of devices KDE thinks can be removed:
Capture: HDA ATI SB (STAC92xx Analog)
Capture: HDA ATI SB, STAC92xx Analog (Default Audio Device)
Output: HD-Audio Generic (HDMI 0)
Output: HD-Audio Generic, HDMI 0 (HDMI Audio Output)
Output: HDA ATI SB (STAC92xx Analog)
Output: HDA ATI SB, STAC92xx Analog (Default Audio Device)
>
> I tried removing and reinstating all the snd modules, to no avail.
How did you managed that?
I just used modprobe -r <module> and modprobe <module>
Elimar
--