Re: no longer sound on amd64 sid systems

2014-06-03 Thread Paul Pignon
Elimar Riesebieter  lxtec.de> writes:



I found a solution that worked here http://forums.debian.net/viewtopic.php?
f=6&t=114840&p=542584#p542584

/Paul





-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/loom.20140603t111315-...@post.gmane.org



Re: no longer sound on amd64 sid systems

2014-05-31 Thread Elimar Riesebieter
* Paul Pignon  [2014-05-30 11:59 +]:

> Andrei POPESCU  gmail.com> writes:
> 
> 
> > > > 
> > > > No, please do
> > > > 
> > > > # echo "options snd-hda-intel model=dell" >> /etc/modprobe.d/local.conf
> I did this, but modprobe snd-hda-intel still says "invalid argument" and I 
> have no idea why.

As mentioned before, a first step forward would be to post the
outpunt of:

# find /lib/modules -name '*snd-hda*'

to this list, though.

Elimar
-- 
 You cannot propel yourself forward by
  patting yourself on the back.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140531101103.gb3...@galadriel.home.lxtec.de



Re: no longer sound on amd64 sid systems

2014-05-30 Thread Paul Pignon
Andrei POPESCU  gmail.com> writes:


> > > 
> > > No, please do
> > > 
> > > # echo "options snd-hda-intel model=dell" >> /etc/modprobe.d/local.conf
I did this, but modprobe snd-hda-intel still says "invalid argument" and I 
have no idea why.
> > > 
> > > as alsa-base.conf will be purged in Jessie.
> > 
> > It's a bit hard to follow the broken threads, but I thought the OP is
> > running Wheezy *not* Jessie.
Yes, I am running Wheezy still.
> 
> 
> 
> Kind regards,
> Andrei





-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/loom.20140530t133423-...@post.gmane.org



Re: no longer sound on amd64 sid systems

2014-05-28 Thread Elimar Riesebieter
* Paul Pignon  [2014-05-28 14:53 +0300]:

[...]
> > please post the output of:
> > 
> > root@debianHP: find /lib/modules -name 'snd-hda*'

What gives this for an output?

[...]
> I still don't know what to put instead of dell.

Nothing!

[...]

> Yes, I can see that in future this would matter, but just now
> alsa-base.conf is still there so if it has the correct entry all
> should be well. Nonetheless, I did as you suggested and took away
> the conf lines from alsa-base.conf, put them in a new .conf file
> (/etc/balsa.conf), but that didn't change anything, still get the
> "invalid argument" error, and have no idea what argument is
> required.

You don't need to put any further phrases to files in
/etc/modprobe.d/

> So, any further suggestions would be greatly appreciated. I need
> sound, and it used to work fine!

Just be a bit more cooperative ;-)

Elimar
-- 
 The path to source is always uphill!
-unknown-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140528122425.gc19...@baumbart.home.lxtec.de



Re: no longer sound on amd64 sid systems

2014-05-28 Thread Paul Pignon


> To: debian-user@lists.debian.org
> Subject: Re: no longer sound on amd64 sid systems
> From: Elimar Riesebieter 
> Date: Fri, 23 May 2014 14:04:35 +0200
> Message-id: <20140523120435.ga32...@baumbart.home.lxtec.de>
> Mail-followup-to: debian-user@lists.debian.org
> In-reply-to: <537f2c5a.1020...@gmail.com>
> References: <537f2c5a.1020...@gmail.com>
> * Paul  [2014-05-23 13:09 +0200]:
> 
> [...]
> > /That just gets me
> > root@debianHP:/usr/lib/pd-extended/extra# modprobe -v snd-hda-intel
> > insmod /lib/modules/3.2.0-4-amd64/kernel/sound/pci/hda/snd-hda-codec.ko
> > ERROR: could not insert 'snd_hda_intel': Invalid argument

and I also get this
root@debianHP:/home/paul# modprobe -f snd-hda-intel
ERROR: could not insert 'snd_hda_intel': Exec format error

> 
> please post the output of:
> 
> root@debianHP: find /lib/modules -name 'snd-hda*'
> 
> > /
> > >>
> [...]
> > options snd_hda_intel model=laptop
> > #options snd_hda_intel index=0 model=auto
> 
> Remove those entries.

Did that

> 
> > //I recently made that change to model=laptop on the advice of someone else
> > on this forum AFAIR.
> > 
> > //
> > /
> > >
> > >No, please do
> > >
> > ># echo "options snd-hda-intel model=dell" >> /etc/modprobe.d/local.conf
> > /I don't want to put dell of course as this is and HP machine, what is the
> > recognized identifier in this case?

I still don't know what to put instead of dell.

> > And why would it make any difference just now if that line is in some other
> > .conf file?
> 
> Read this:
> > >
> > >as alsa-base.conf will be purged in Jessie. You can choose a filename
> > >as you want but with the extension .conf.

Yes, I can see that in future this would matter, but just now alsa-base.conf is 
still there so if it 
has the correct entry all should be well. Nonetheless, I did as you suggested 
and took away the conf 
lines from alsa-base.conf, put them in a new .conf file (/etc/balsa.conf), but 
that didn't change 
anything, still get the "invalid argument" error, and have no idea what 
argument is required.

So, any further suggestions would be greatly appreciated. I need sound, and it 
used to work fine!

/Paul
> 
> Elimar



-- 
Paul Pignon
The DP Works
S. Jordbrov. 177/II
13762 Jordbro
Sweden
Tel. +46 8 50026047
Mob. +46 729311141, +46 705508655
Skype: paulspignon


Re: no longer sound on amd64 sid systems

2014-05-23 Thread Elimar Riesebieter
* Paul  [2014-05-23 13:09 +0200]:

[...]
> /That just gets me
> root@debianHP:/usr/lib/pd-extended/extra# modprobe -v snd-hda-intel
> insmod /lib/modules/3.2.0-4-amd64/kernel/sound/pci/hda/snd-hda-codec.ko
> ERROR: could not insert 'snd_hda_intel': Invalid argument

please post the output of:

root@debianHP: find /lib/modules -name 'snd-hda*'

> /
> >>
[...]
> options snd_hda_intel model=laptop
> #options snd_hda_intel index=0 model=auto

Remove those entries.

> //I recently made that change to model=laptop on the advice of someone else
> on this forum AFAIR.
> 
> //
> /
> >
> >No, please do
> >
> ># echo "options snd-hda-intel model=dell" >> /etc/modprobe.d/local.conf
> /I don't want to put dell of course as this is and HP machine, what is the
> recognized identifier in this case?
> And why would it make any difference just now if that line is in some other
> .conf file?

Read this:
> >
> >as alsa-base.conf will be purged in Jessie. You can choose a filename
> >as you want but with the extension .conf.

Elimar
-- 
 >what IMHO then?
  IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
  --posting from alex in debian-user--


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140523120435.ga32...@baumbart.home.lxtec.de



Re: no longer sound on amd64 sid systems

2014-05-15 Thread Elimar Riesebieter
* Scott Ferguson  [2014-05-16 03:21 
+1000]:

> On 16/05/14 01:39, Elimar Riesebieter wrote:
> > * Scott Ferguson  [2014-05-16 00:49 
> > +1000]:
> > 
> >> On 16/05/14 00:15, Elimar Riesebieter wrote:
[...]
> >>> That is useless with the modules listet above. The sound driver for
> >>> your STA92xx is missing!
> >>>
> >>> Just try as root:
> >>> # modprobe -v snd-hda-intel
> >>
> >> after editing /etc/modprobe.d/alsa-base.conf and adding this line:
> >> options snd-hda-intel model=dell
> > 
> > No, please do
> > 
> > # echo "options snd-hda-intel model=dell" >> /etc/modprobe.d/local.conf
> > 
> > as alsa-base.conf will be purged in Jessie.
> 
> 
> It's a bit hard to follow the broken threads, but I thought the OP is
> running Wheezy *not* Jessie.

It is always not a good idea to edit configuration files installed
by packages in /etc. They will be purgedi/updated on each update. So
individual configs should be *marked* as such. Please notice, Jessie
is on the way ;-)

Elimar, who runs always sid
-- 
 >what IMHO then?
  IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
  --posting from alex in debian-user--


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140515202751.ga4...@galadriel.home.lxtec.de



Re: no longer sound on amd64 sid systems

2014-05-15 Thread Andrei POPESCU
On Vi, 16 mai 14, 03:21:46, Scott Ferguson wrote:
> On 16/05/14 01:39, Elimar Riesebieter wrote:
> > 
> > No, please do
> > 
> > # echo "options snd-hda-intel model=dell" >> /etc/modprobe.d/local.conf
> > 
> > as alsa-base.conf will be purged in Jessie.
> 
> It's a bit hard to follow the broken threads, but I thought the OP is
> running Wheezy *not* Jessie.

I understood that to mean "because you will avoid a problem when 
upgrading to Jessie". Even so, I made it a habit to stay as much as 
possible away from files "belonging" to a package.

This makes package upgrades smoother, though one still has to check the 
local config still applies to the upgraded package.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature


Re: no longer sound on amd64 sid systems

2014-05-15 Thread Scott Ferguson
On 16/05/14 01:39, Elimar Riesebieter wrote:
> * Scott Ferguson  [2014-05-16 00:49 
> +1000]:
> 
>> On 16/05/14 00:15, Elimar Riesebieter wrote:
>>> * Paul Pignon  [2014-05-15 12:09 +0100]:
>>>
>>> [...]> > ... 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: 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.*
>>> [...]
 *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.

>>>
>>> That is useless with the modules listet above. The sound driver for
>>> your STA92xx is missing!
>>>
>>> Just try as root:
>>> # modprobe -v snd-hda-intel
>>
>> after editing /etc/modprobe.d/alsa-base.conf and adding this line:
>> options snd-hda-intel model=dell
> 
> No, please do
> 
> # echo "options snd-hda-intel model=dell" >> /etc/modprobe.d/local.conf
> 
> as alsa-base.conf will be purged in Jessie.


It's a bit hard to follow the broken threads, but I thought the OP is
running Wheezy *not* Jessie.

Kind regards


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5374f7aa.9030...@gmail.com



Re: no longer sound on amd64 sid systems

2014-05-15 Thread Elimar Riesebieter
* Scott Ferguson  [2014-05-16 00:49 
+1000]:

> On 16/05/14 00:15, Elimar Riesebieter wrote:
> > * Paul Pignon  [2014-05-15 12:09 +0100]:
> > 
> > [...]> > ... 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: 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.*
> > [...]
> >> *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.
> >>
> > 
> > That is useless with the modules listet above. The sound driver for
> > your STA92xx is missing!
> > 
> > Just try as root:
> > # modprobe -v snd-hda-intel
> 
> after editing /etc/modprobe.d/alsa-base.conf and adding this line:
> options snd-hda-intel model=dell

No, please do

# echo "options snd-hda-intel model=dell" >> /etc/modprobe.d/local.conf

as alsa-base.conf will be purged in Jessie. You can choose a filename
as you want but with the extension .conf.

Elimar
-- 
 Never make anything simple and efficient when a way
  can be found to make it complex and wonderful ;-)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140515153939.gd21...@baumbart.home.lxtec.de



Re: no longer sound on amd64 sid systems

2014-05-15 Thread Scott Ferguson
On 16/05/14 00:15, Elimar Riesebieter wrote:
> * Paul Pignon  [2014-05-15 12:09 +0100]:
> 
> [...]> > ... 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: 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.*
> [...]
>> *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.
>>
> 
> That is useless with the modules listet above. The sound driver for
> your STA92xx is missing!
> 
> Just try as root:
> # modprobe -v snd-hda-intel

after editing /etc/modprobe.d/alsa-base.conf and adding this line:
options snd-hda-intel model=dell

> 
> Elimar
> 

Kind regards

-- 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5374d3ec.6030...@gmail.com



Re: no longer sound on amd64 sid systems

2014-05-15 Thread Elimar Riesebieter
* Paul Pignon  [2014-05-15 12:09 +0100]:

[...]> > ... 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: 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.*
[...]
> *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.
> 

That is useless with the modules listet above. The sound driver for
your STA92xx is missing!

Just try as root:
# modprobe -v snd-hda-intel

Elimar
-- 
 Obviously the human brain works like a computer.
  Since there are no stupid computers humans can't be stupid.
  There are just a few running with Windows or even CE ;-)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140515141521.gb21...@baumbart.home.lxtec.de



Re: Re: no longer sound on amd64 sid systems

2014-05-15 Thread Paul Pignon
[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread
Index]
Re: no longer sound on amd64 sid systems

To: debian-user@lists.debian.org
Subject: Re: no longer sound on amd64 sid systems
From: Elimar Riesebieter 
Date: Wed, 14 May 2014 18:18:41 +0200
Message-id: <20140514161841.ga3...@galadriel.home.lxtec.de>
Mail-followup-to: debian-user@lists.debian.org
In-reply-to: 
References: 
* Paul Pignon  [2014-05-14 16:08 +0100]:


*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
> Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc 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  *and *modprobe 

Elimar
--


Re: no longer sound on amd64 sid systems

2014-05-14 Thread Elimar Riesebieter
* Paul Pignon  [2014-05-14 16:08 +0100]:

[...]
> 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.
> 
> 
> 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.

> 
> __
> 
> 
> ... aplay -l
> 
> aplay: device_list:252: no soundcards found...

Because there is no sound driver loaded.

> 
> ... aplay -L
> 
> default
> 
> Playback/recording through the PulseAudio sound server
> 
> __

> ... dpkg -l |egrep alsa

Ok.

[...]

> ... dpkg -l |egrep asound

[...]
> ... cat /proc/version
> Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc 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.

> 
> KDE tells me this:
> 
> 
> [image: Inline images 1]

Not found. But not common to send to a mailing list anyway.

> 
> I tried removing and reinstating all the snd modules, to no avail.

How did you managed that?


Elimar
-- 
 Never make anything simple and efficient when a way
  can be found to make it complex and wonderful ;-)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140514161841.ga3...@galadriel.home.lxtec.de



Re: no longer sound on amd64 sid systems SOLVED

2014-05-13 Thread sp113438
On Tue, 13 May 2014 20:39:10 +0100
Robin  wrote:

> On 13 May 2014 20:05, sp113438  wrote:
> > On Tue, 13 May 2014 19:38:10 +0100
> > Robin  wrote:
> >
> >
> >>
> >>
> >> If you run alsamixer does it show the right audio interface?
> >
> > # alsamixer
> > cannot open mixer: No such file or directory
> >
> > Thanks,
> > Arne
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact
> > listmas...@lists.debian.org Archive:
> > https://lists.debian.org/20140513210500.48479b8f@fx4100
> >
> 
> reload modules?
> 
# rmmod snd_virtuoso
# modprobe snd_virtuoso

did the job

Later I will reboot

Thanks!
Arne


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140513214757.70645e4d@fx4100



Re: no longer sound on amd64 sid systems

2014-05-13 Thread Robin
On 13 May 2014 20:05, sp113438  wrote:
> On Tue, 13 May 2014 19:38:10 +0100
> Robin  wrote:
>
>
>>
>>
>> If you run alsamixer does it show the right audio interface?
>
> # alsamixer
> cannot open mixer: No such file or directory
>
> Thanks,
> Arne
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: https://lists.debian.org/20140513210500.48479b8f@fx4100
>

reload modules?

-- 
rob


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAOZWb-q6f3j02cZsG8t7MdXx9GEqwOJZrzgj=uqwg2bkjpp...@mail.gmail.com



Re: no longer sound on amd64 sid systems

2014-05-13 Thread sp113438
On Tue, 13 May 2014 19:38:10 +0100
Robin  wrote:


> 
> 
> If you run alsamixer does it show the right audio interface?

# alsamixer
cannot open mixer: No such file or directory

Thanks,
Arne


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140513210500.48479b8f@fx4100



Re: no longer sound on amd64 sid systems

2014-05-13 Thread sp113438
On Tue, 13 May 2014 20:13:12 +0200
Elimar Riesebieter  wrote:

> * sp113438  [2014-05-13 16:27 +0200]:
> 
> > On Tue, 13 May 2014 11:27:50 +0200
> > Elimar Riesebieter  wrote:
> > 
> > Hello,
> > > > hello,
> > > > 
> > > > I did the latest update on 2 systems amd64 Sid, and now sound
> > > > does not work any longer on both systems.
> > > > The program /usr/sbin/alsa dissapeared after installing the
> > > > latest alsa-base.
> > > 
> > > /usr/sbin/alsa was a relict from the obsolete alsa-driver package
> > > and is almost not usefull as the sound modules now handled by
> > > kmod.
> > > 
> > > > No mixers are found.
> 
> As you can see bei aplay -L there are mixers avaiable..
> 
> > > > Failed to open audio output
> > > > Yesterday sound did work on both systems.
> > > 
> > > Please post the output of:
> > > 
> > > $ lsmod | grep snd
> > > $ aplay -l
> > > $ aplay -L
> > > $ dpkg -l | egrep (alsa|asound)
> > > $ cat /proc/version
> > > 
> > # lsmod | grep snd
> 
> Seems to be correct
> 
> [...]
> > 
> > # aplay -l
> 
> Ok
> 
> [...]
> > 
> > # aplay -L
> > root@fx4100:/home/arne# aplay -L
> > null
> > Discard all samples (playback) or generate zero samples
> > (capture) pulse
> > PulseAudio Sound Server
> 
> Could you please start alasamixer, choose the Xonar via  (
> should be the second entry. and test sound again. I assume there is
> a prob with pulse.
> 
# alsamixer
cannot open mixer: No such file or directory

pulse is not installed.

# cat /proc/version
Linux version 3.14.2-arne-amd64 (root@fx4100) (gcc version 4.8.2
(Debian 4.8.2-21) ) #1 SMP Mon May 12 17:47:23 CEST 2014

Thanks,
Arne


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140513204202.5215ebd2@fx4100



Re: no longer sound on amd64 sid systems

2014-05-13 Thread Robin
On 13 May 2014 15:27, sp113438  wrote:
> On Tue, 13 May 2014 11:27:50 +0200
> Elimar Riesebieter  wrote:
>
> Hello,
>> > hello,
>> >
>> > I did the latest update on 2 systems amd64 Sid, and now sound does
>> > not work any longer on both systems.
>> > The program /usr/sbin/alsa dissapeared after installing the latest
>> > alsa-base.
>>
>> /usr/sbin/alsa was a relict from the obsolete alsa-driver package and
>> is almost not usefull as the sound modules now handled by kmod.
>>
>> > No mixers are found. Failed to open audio output
>> > Yesterday sound did work on both systems.
>>
>> Please post the output of:
>>
>> $ lsmod | grep snd
>> $ aplay -l
>> $ aplay -L
>> $ dpkg -l | egrep (alsa|asound)
>> $ cat /proc/version
>>
>> Elimar
>
> Hope this helps:
>
>>
> # lsmod | grep snd
> snd_hda_codec_hdmi 40908  0
> snd_virtuoso   34854  0
> snd_oxygen_lib 36709  1 snd_virtuoso
> snd_mpu401_uart13507  1 snd_oxygen_lib
> snd_rawmidi26805  1 snd_mpu401_uart
> snd_hda_codec 100159  1 snd_hda_codec_hdmi
> snd_seq_device 13132  1 snd_rawmidi
> snd_hwdep  13148  1 snd_hda_codec
> snd_pcm_oss44847  0
> snd_mixer_oss  22042  1 snd_pcm_oss
> snd_pcm84566  4
> snd_pcm_oss,snd_hda_codec_hdmi,snd_oxygen_lib,snd_hda_codec
> snd_timer  26614  1 snd_pcm snd61046
> 12
> snd_pcm_oss,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_rawmidi,snd_virtuoso,snd_oxygen_lib,snd_hda_codec,snd_mpu401_uart,snd_seq_device,snd_mixer_oss
> soundcore  13026  1 snd
>
> # aplay -l
>  List of PLAYBACK Hardware Devices 
> card 1: STX [Xonar STX], device 0: Multichannel [Multichannel]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 1: STX [Xonar STX], device 1: Digital [Digital]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
>
> # aplay -l
>  List of PLAYBACK Hardware Devices 
> card 1: STX [Xonar STX], device 0: Multichannel [Multichannel]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 1: STX [Xonar STX], device 1: Digital [Digital]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> root@fx4100:/home/arne# aplay -L
> null
> Discard all samples (playback) or generate zero samples (capture)
> pulse
> PulseAudio Sound Server
> default:CARD=STX
> Xonar STX, Multichannel
> Default Audio Device
> sysdefault:CARD=STX
> Xonar STX, Multichannel
> Default Audio Device
> front:CARD=STX,DEV=0
> Xonar STX, Multichannel
> Front speakers
> surround40:CARD=STX,DEV=0
> Xonar STX, Multichannel
> 4.0 Surround output to Front and Rear speakers
> surround41:CARD=STX,DEV=0
> Xonar STX, Multichannel
> 4.1 Surround output to Front, Rear and Subwoofer speakers
> surround50:CARD=STX,DEV=0
> Xonar STX, Multichannel
> 5.0 Surround output to Front, Center and Rear speakers
> surround51:CARD=STX,DEV=0
> Xonar STX, Multichannel
> 5.1 Surround output to Front, Center, Rear and Subwoofer speakers
> surround71:CARD=STX,DEV=0
> Xonar STX, Multichannel
> 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
> iec958:CARD=STX,DEV=0
> Xonar STX, Multichannel
> IEC958 (S/PDIF) Digital Audio Output
>
> dpkg -l | grep alsa
> ii  alsa-base
> 1.0.27+1   all  dummy package to ease
> purging of obsolete conffiles ii  alsa-oss
> 1.0.25-1   amd64ALSA wrapper for OSS
> applications ii  alsa-utils
> 1.0.27.2-1 amd64Utilities for
> configuring and using ALSA ii  alsamixergui
> 0.9.0rc2-1-9.1 amd64graphical soundcard
> mixer for ALSA soundcard driver ii
> liballegro4.4-plugin-alsa:amd64
> 2:4.4.2-4  amd64ALSA audio plugin for
> the Allegro library ii  libclalsadrv2
> 2.0.0-3amd64ALSA driver C++ access
> library ii  libsox-fmt-alsa:amd64
> 14.4.1-3   amd64SoX alsa format I/O
> library ii  libzita-alsa-pcmi0:amd64 0.2.0-2
> amd64C++ wrapper around the ALSA API
>
> # dpkg -l | grep asound
> ii  libasound2:amd64
> 1.0.27.2-3 amd64shared library for ALSA
> applications rc  libasound2:i386
> 1.0.27.2-3 i386 shared library for ALSA
> applications ii  libasound2-data
> 1.0.27.2-3 all  Configuration files and
> profiles for ALSA drivers ii  libasound2-plugins:amd64
> 1.0.27-2+b1amd64ALSA library additional
> plugins
>
>
> My soundcard is the Asus Xonar STX
>
> Thanks!
>
>
>
>
> --


If you run alsamixer does it show the right audio interface?
-- 
rob


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/caozwb-pbcwd0fcfin6fxfbjo1ftx2a8sp63ori4uv9e0-

Re: no longer sound on amd64 sid systems

2014-05-13 Thread Elimar Riesebieter
* sp113438  [2014-05-13 16:27 +0200]:

> On Tue, 13 May 2014 11:27:50 +0200
> Elimar Riesebieter  wrote:
> 
> Hello,
> > > hello,
> > > 
> > > I did the latest update on 2 systems amd64 Sid, and now sound does
> > > not work any longer on both systems.
> > > The program /usr/sbin/alsa dissapeared after installing the latest
> > > alsa-base.
> > 
> > /usr/sbin/alsa was a relict from the obsolete alsa-driver package and
> > is almost not usefull as the sound modules now handled by kmod.
> > 
> > > No mixers are found.

As you can see bei aplay -L there are mixers avaiable..

> > > Failed to open audio output
> > > Yesterday sound did work on both systems.
> > 
> > Please post the output of:
> > 
> > $ lsmod | grep snd
> > $ aplay -l
> > $ aplay -L
> > $ dpkg -l | egrep (alsa|asound)
> > $ cat /proc/version
> > 
> # lsmod | grep snd

Seems to be correct

[...]
> 
> # aplay -l

Ok

[...]
> 
> # aplay -L
> root@fx4100:/home/arne# aplay -L
> null
> Discard all samples (playback) or generate zero samples (capture)
> pulse
> PulseAudio Sound Server

Could you please start alasamixer, choose the Xonar via  (
should be the second entry. and test sound again. I assume there is
a prob with pulse.

[...] 
> dpkg -l | grep alsa

Sould be fine.

[...]
> 
> # dpkg -l | grep asound

Seems to be ok.

[...]
> 
> 
> My soundcard is the Asus Xonar STX

I noticed ;-)

Elimar

-- 
 Numeric stability is probably not all that
  important when you're guessing;-)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140513181312.ga3...@galadriel.home.lxtec.de



Re: no longer sound on amd64 sid systems

2014-05-13 Thread sp113438
On Tue, 13 May 2014 11:27:50 +0200
Elimar Riesebieter  wrote:

Hello,
> > hello,
> > 
> > I did the latest update on 2 systems amd64 Sid, and now sound does
> > not work any longer on both systems.
> > The program /usr/sbin/alsa dissapeared after installing the latest
> > alsa-base.
> 
> /usr/sbin/alsa was a relict from the obsolete alsa-driver package and
> is almost not usefull as the sound modules now handled by kmod.
> 
> > No mixers are found. Failed to open audio output
> > Yesterday sound did work on both systems.
> 
> Please post the output of:
> 
> $ lsmod | grep snd
> $ aplay -l
> $ aplay -L
> $ dpkg -l | egrep (alsa|asound)
> $ cat /proc/version
> 
> Elimar

Hope this helps:

> 
# lsmod | grep snd
snd_hda_codec_hdmi 40908  0 
snd_virtuoso   34854  0 
snd_oxygen_lib 36709  1 snd_virtuoso
snd_mpu401_uart13507  1 snd_oxygen_lib
snd_rawmidi26805  1 snd_mpu401_uart
snd_hda_codec 100159  1 snd_hda_codec_hdmi
snd_seq_device 13132  1 snd_rawmidi
snd_hwdep  13148  1 snd_hda_codec
snd_pcm_oss44847  0 
snd_mixer_oss  22042  1 snd_pcm_oss
snd_pcm84566  4
snd_pcm_oss,snd_hda_codec_hdmi,snd_oxygen_lib,snd_hda_codec
snd_timer  26614  1 snd_pcm snd61046
12
snd_pcm_oss,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_rawmidi,snd_virtuoso,snd_oxygen_lib,snd_hda_codec,snd_mpu401_uart,snd_seq_device,snd_mixer_oss
soundcore  13026  1 snd

# aplay -l
 List of PLAYBACK Hardware Devices 
card 1: STX [Xonar STX], device 0: Multichannel [Multichannel]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: STX [Xonar STX], device 1: Digital [Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

# aplay -l
 List of PLAYBACK Hardware Devices 
card 1: STX [Xonar STX], device 0: Multichannel [Multichannel]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: STX [Xonar STX], device 1: Digital [Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
root@fx4100:/home/arne# aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
pulse
PulseAudio Sound Server
default:CARD=STX
Xonar STX, Multichannel
Default Audio Device
sysdefault:CARD=STX
Xonar STX, Multichannel
Default Audio Device
front:CARD=STX,DEV=0
Xonar STX, Multichannel
Front speakers
surround40:CARD=STX,DEV=0
Xonar STX, Multichannel
4.0 Surround output to Front and Rear speakers
surround41:CARD=STX,DEV=0
Xonar STX, Multichannel
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=STX,DEV=0
Xonar STX, Multichannel
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=STX,DEV=0
Xonar STX, Multichannel
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=STX,DEV=0
Xonar STX, Multichannel
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=STX,DEV=0
Xonar STX, Multichannel
IEC958 (S/PDIF) Digital Audio Output

dpkg -l | grep alsa
ii  alsa-base
1.0.27+1   all  dummy package to ease
purging of obsolete conffiles ii  alsa-oss
1.0.25-1   amd64ALSA wrapper for OSS
applications ii  alsa-utils
1.0.27.2-1 amd64Utilities for
configuring and using ALSA ii  alsamixergui
0.9.0rc2-1-9.1 amd64graphical soundcard
mixer for ALSA soundcard driver ii
liballegro4.4-plugin-alsa:amd64
2:4.4.2-4  amd64ALSA audio plugin for
the Allegro library ii  libclalsadrv2
2.0.0-3amd64ALSA driver C++ access
library ii  libsox-fmt-alsa:amd64
14.4.1-3   amd64SoX alsa format I/O
library ii  libzita-alsa-pcmi0:amd64 0.2.0-2
amd64C++ wrapper around the ALSA API

# dpkg -l | grep asound
ii  libasound2:amd64
1.0.27.2-3 amd64shared library for ALSA
applications rc  libasound2:i386
1.0.27.2-3 i386 shared library for ALSA
applications ii  libasound2-data
1.0.27.2-3 all  Configuration files and
profiles for ALSA drivers ii  libasound2-plugins:amd64
1.0.27-2+b1amd64ALSA library additional
plugins


My soundcard is the Asus Xonar STX

Thanks!




-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140513162717.552c2fa4@fx4100



Re: no longer sound on amd64 sid systems

2014-05-13 Thread Elimar Riesebieter
* sp113438  [2014-05-12 22:05 +0200]:

> hello,
> 
> I did the latest update on 2 systems amd64 Sid, and now sound does not
> work any longer on both systems.
> The program /usr/sbin/alsa dissapeared after installing the latest
> alsa-base.

/usr/sbin/alsa was a relict from the obsolete alsa-driver package and
is almost not usefull as the sound modules now handled by kmod.

> No mixers are found. Failed to open audio output
> Yesterday sound did work on both systems.

Please post the output of:

$ lsmod | grep snd
$ aplay -l
$ aplay -L
$ dpkg -l | egrep (alsa|asound)
$ cat /proc/version

Elimar
-- 
 Obviously the human brain works like a computer.
  Since there are no stupid computers humans can't be stupid.
 There are just a few running with Windows or even CE ;-)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140513092750.ga21...@baumbart.home.lxtec.de