Hi!
Today my sound card stop to work, I'm not sure about the reason.
There is a error during boot, something like
timeout: killing '/sbin/modprobe -bv pci:v000010ECd0000816Csv00001734sd00001178bc0Csc07i01' [594]
The logs colected by alsa are accesible at
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.alsa-project.org/db/?f=f62fc41d83c2aecadb11e14b09241f872efe4949"
linktext was:"http://www.alsa-project.org/db/?f=f62fc ... 872efe4949"
====================================
Any ideas?
topic title: [SOLVED] No sound after update
8 posts
• Page 1 of 1
-
Posts: 74
- Joined: 21 Apr 2013
#1
Last edited by CGarces on 02 Sep 2013, 20:40, edited 1 time in total.
-
Posts: 630
- Joined: 12 Oct 2012
#2
Looks like the Kernel is not recognizing your card.
I would try a different kernel, to see if the sound card will get recognized.
I would try a different kernel, to see if the sound card will get recognized.
-
Posts: 74
- Joined: 21 Apr 2013
#3
Any other idea?
But was working fine yesterday... and I don't have changed the kernel...Eino wrote:Looks like the Kernel is not recognizing your card.
I would try a different kernel, to see if the sound card will get recognized.
Any other idea?
-
Posts: 4,164
- Joined: 20 Feb 2009
#4
See if auto mute is on in Alsa Mixer. My motorcycle Shop desktop started doing that after a upgrade. If alsa mixer won't open as user in terminal. Open it as root.
That is another glitch I live with on M11 Base. Yeah. My user name is part of the sound group also.
That is another glitch I live with on M11 Base. Yeah. My user name is part of the sound group also.
-
Posts: 74
- Joined: 21 Apr 2013
#5
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.alsa-project.org/db/?f=f62fc41d83c2aecadb11e14b09241f872efe4949"
linktext was:"see Alsa logs"
====================================
)
The element that fails at boot is the sound card...
snd_hda_intel NOT is loaded
But loading it manually works without problem !
1.-Why stop to work since 30-August? I don't have changed the kernel and I can't see anything related at /var/log/apt/
2.-Why modprobe snd-hda-intel works manually but not at boot? what it's doing during the boot process? I not see anything at dmesg
Nothing to do with alsa mixer becouse the card not is detected by Alsa (rokytnji wrote:See if auto mute is on in Alsa Mixer. My motorcycle Shop desktop started doing that after a upgrade. If alsa mixer won't open as user in terminal. Open it as root.
That is another glitch I live with on M11 Base. Yeah. My user name is part of the sound group also.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.alsa-project.org/db/?f=f62fc41d83c2aecadb11e14b09241f872efe4949"
linktext was:"see Alsa logs"
====================================
)
The element that fails at boot is the sound card...
Code: Select all
root@antiX1:/home/Carlos# modprobe -R 'pci:v00008086d0000284Bsv00001025sd00000136bc04sc03i00'
snd_hda_intel
snd_hda_intel
Code: Select all
root@antiX1:/home/Carlos# rmmod snd-hda-intel
Error: Module snd_hda_intel is not currently loaded
Code: Select all
root@antiX1:/home/Carlos# modprobe snd-hda-intel
2.-Why modprobe snd-hda-intel works manually but not at boot? what it's doing during the boot process? I not see anything at dmesg
-
Posts: 1,062
- Joined: 20 Jan 2010
#6
Maybe post the upgrade history when this happened. It seems to me that the driver either has a conflicting driver or the driver is blacklisted. The upgrade history should show if a conflicting package was installed and if you check /etc/modprobe.d/*.list for snd_hda_intel on one of the lines. If there is then comment out that line and. Restart to see if it is fixed.
-
Posts: 74
- Joined: 21 Apr 2013
#7
On Sep 1 13:07:27 was loaded during boot
On Sep 2 17:14:02 was loaded by hand.
First boot without sound was on
Something happens between Sep 1 13:07:27 and 17:09:44
During that time I do this:
Downgrade lxsession to fix one problem caused by dist-update
Reinstall ldxe stuff from stable instead of testing
And also install some stuff related with JSON
I have reverted the update of oss-compat without success
---EDIT---
Fixed!
The problem was caused by /etc/modprobe.d/oss-compat.conf
I'm not sure if is a
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://us.generation-nt.com/answer/bug-660803-oss-compat-3-problems-udev-breaks-audio-help-211726702.html"
linktext was:"debian bug"
====================================
I have removed the file and the library, I think that I don't need oss-compat
Code: Select all
root@antiX1:/home/Carlos# less /var/log/kern.log | grep snd_hda_intel
Sep 1 13:04:30 antiX1 kernel: [ 9.238361] snd_hda_intel 0000:00:1b.0: irq 46 for MSI/MSI-X
Sep 1 13:07:27 antiX1 kernel: [ 7.969088] snd_hda_intel 0000:00:1b.0: irq 45 for MSI/MSI-X
Sep 2 17:14:02 antiX1 kernel: [ 1465.338882] snd_hda_intel 0000:00:1b.0: irq 47 for MSI/MSI-X
On Sep 2 17:14:02 was loaded by hand.
First boot without sound was on
Code: Select all
Sep 1 17:09:44 antiX1 kernel: [ 0.000000] Command line: root=UUID=419ad2c2-a347-4b58-ad65-eee0c6e57bbe ro pcie_aspm=force quiet
During that time I do this:
Downgrade lxsession to fix one problem caused by dist-update
Code: Select all
Start-Date: 2013-09-01 13:13:32
Commandline: apt-get install --reinstall lxsession=0.4.6.1-4
Downgrade: lxsession:amd64 (0.4.9.2-1, 0.4.6.1-4)
Remove: lxde:amd64 (4+nmu1)
End-Date: 2013-09-01 13:13:49
Start-Date: 2013-09-01 13:14:16
Commandline: apt-get autoremove
Remove: libgee2:amd64 (0.6.8-1)
End-Date: 2013-09-01 13:14:18
Code: Select all
Start-Date: 2013-09-01 13:14:39
Commandline: apt-get remove lxde*
Remove: lxde-core:amd64 (4+nmu1), lxde-common:amd64 (0.5.5-6), lxde-icon-theme:amd64 (0.5.0-1)
End-Date: 2013-09-01 13:14:44
Start-Date: 2013-09-01 13:15:01
Commandline: apt-get install lxsession-edit
Install: lxsession-edit:amd64 (0.2.0-3)
End-Date: 2013-09-01 13:15:04
Start-Date: 2013-09-01 13:15:22
Commandline: apt-get install lxpolkit
Install: lxpolkit:amd64 (0.1.0-4)
End-Date: 2013-09-01 13:15:25
Start-Date: 2013-09-01 13:17:15
Commandline: apt-get install --yes lxde
Install: lxde-core:amd64 (4+nmu1), lxde-common:amd64 (0.5.5-6), lxde:amd64 (4+nmu1), lxde-icon-theme:amd64 (0.5.0-1)
End-Date: 2013-09-01 13:17:26
Code: Select all
Start-Date: 2013-09-01 13:58:42
Commandline: apt-get upgrade
Upgrade: oss-compat:amd64 (2, 4)
End-Date: 2013-09-01 13:58:44
Start-Date: 2013-09-01 14:07:49
Commandline: apt-get install php5-dev
Install: shtool:amd64 (2.0.8-6, automatic), php5-dev:amd64 (5.5.1+dfsg-2), libssl-dev:amd64 (1.0.1e-3, automatic)
End-Date: 2013-09-01 14:07:55
Start-Date: 2013-09-01 14:30:37
Commandline: apt-get install php5-json
Install: php5-json:amd64 (1.3.1+dfsg-3)
End-Date: 2013-09-01 14:30:40
Code: Select all
Start-Date: 2013-09-01 18:06:49
Commandline: apt-get install --reinstall oss-compat=2
Downgrade: oss-compat:amd64 (4, 2)
End-Date: 2013-09-01 18:07:00
---EDIT---
Fixed!
The problem was caused by /etc/modprobe.d/oss-compat.conf
Code: Select all
oftdep snd-pcm post: snd-pcm-oss
softdep snd-mixer post: snd-mixer-oss
softdep snd-seq post: snd-seq-midi snd-seq-oss
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://us.generation-nt.com/answer/bug-660803-oss-compat-3-problems-udev-breaks-audio-help-211726702.html"
linktext was:"debian bug"
====================================
I have removed the file and the library, I think that I don't need oss-compat
-
Posts: 1,062
- Joined: 20 Jan 2010
#8
Oh yes oss-compat.
It is safe to remove it.
I have had an issue with oss-compat before, I did not loose sound but I was recieving errors on bootup that did not apear to mean anything. (because the error was there,
but everything worked). I appologize, I am not sure why this did not click in my mind when seeing the very similar boot error in your first post.
Glad that you have it working now __{{emoticon}}__
Dave
It is safe to remove it.
I have had an issue with oss-compat before, I did not loose sound but I was recieving errors on bootup that did not apear to mean anything. (because the error was there,
but everything worked). I appologize, I am not sure why this did not click in my mind when seeing the very similar boot error in your first post.
Code: Select all
timeout: killing '/sbin/modprobe -bv pci:v000010ECd0000816Csv00001734sd00001178bc0Csc07i01' [594]
Dave