Re: no longer sound on amd64 sid systems

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



I found a solution that worked here http://forums.debian.net/viewtopic.php?
f=6t=114840p=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-30 Thread Paul Pignon
Andrei POPESCU andreimpopescu at 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 Paul Pignon


 To: debian-user@lists.debian.org
 Subject: Re: no longer sound on amd64 sid systems
 From: Elimar Riesebieter riese...@lxtec.de
 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 paulspig...@gmail.com [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: 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 riese...@lxtec.de
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: CAPMQhYS5h8=nD5xKaW5So=dfDDVCfGakkLoHfbPR--o0-T=+
2...@mail.gmail.com
References: CAPMQhYS5h8=nD5xKaW5So=dfDDVCfGakkLoHfbPR--o0-T=+
2...@mail.gmail.com
* Paul Pignon paulspig...@gmail.com [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 module *and *modprobe module

Elimar
--