[SOLVED] Slackware 13.37 audio setup seems fine, no sound
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The system is Slackware 13.37, multilib. My problem is that I'm getting no sound from the speakers or headphones.
I'll just cut to the chase and (hopefully) give the relevant information.
lspci -k | grep -iA3 audio:
Code:
00:1b.0 Audio device: Intel Corporation 6 Series Chipset Family High Definition Audio Controller (rev 05)
Subsystem: ASUSTeK Computer Inc. Device 8410
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
--
01:00.1 Audio device: nVidia Corporation GF108 High Definition Audio Controller (rev a1)
Subsystem: eVga.com. Corp. Device 1430
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF version 1.0.24.2 ---
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
# --- END: Generated by ALSACONF, do not edit. ---
Alsaconf seems to go through without a hitch and alsamixer looks, well, it looks like it should. But I have no sound.
Any thoughts would be greatly appreciated. I'm truly stumped, but suspect the answer may be staring me in the face.
I saw the thread but didn't look into it since it seemed specific to flash sound.
Something else I noticed in my syslog that may or may not be related:
Code:
Jan 6 14:01:56 darkstar kernel: [ 92.912234] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
Jan 6 14:18:23 darkstar kernel: [ 1079.730061] irq 19: nobody cared (try booting with the "irqpoll" option)
Jan 6 14:18:23 darkstar kernel: [ 1079.730067] Pid: 0, comm: swapper Tainted: P 2.6.37.6 #3
Jan 6 14:18:23 darkstar kernel: [ 1079.730069] Call Trace:
Jan 6 14:18:23 darkstar kernel: [ 1079.730071] <IRQ> [<ffffffff810aac2b>] __report_bad_irq.clone.2+0x2b/0xa0
Jan 6 14:18:23 darkstar kernel: [ 1079.730083] [<ffffffff810aae2e>] note_interrupt+0x18e/0x1d0
Jan 6 14:18:23 darkstar kernel: [ 1079.730088] [<ffffffff81074125>] ? sched_clock_idle_wakeup_event+0x15/0x20
Jan 6 14:18:23 darkstar kernel: [ 1079.730092] [<ffffffff810abc85>] handle_fasteoi_irq+0xc5/0xf0
Jan 6 14:18:23 darkstar kernel: [ 1079.730104] [<ffffffff81005a32>] handle_irq+0x22/0x40
Jan 6 14:18:23 darkstar kernel: [ 1079.730107] [<ffffffff81aa57b8>] do_IRQ+0x68/0xf0
Jan 6 14:18:23 darkstar kernel: [ 1079.730110] [<ffffffff81aa52d3>] ret_from_intr+0x0/0xa
Jan 6 14:18:23 darkstar kernel: [ 1079.730111] <EOI> [<ffffffff8159094c>] ? intel_idle+0xec/0x180
Jan 6 14:18:23 darkstar kernel: [ 1079.730115] [<ffffffff8159092b>] ? intel_idle+0xcb/0x180
Jan 6 14:18:23 darkstar kernel: [ 1079.730118] [<ffffffff819891e1>] cpuidle_idle_call+0x91/0x130
Jan 6 14:18:23 darkstar kernel: [ 1079.730120] [<ffffffff81000d2c>] cpu_idle+0x9c/0x120
Jan 6 14:18:23 darkstar kernel: [ 1079.730123] [<ffffffff81a6e82d>] rest_init+0x6d/0x80
Jan 6 14:18:23 darkstar kernel: [ 1079.730124] [<ffffffff8210fc49>] start_kernel+0x3c4/0x3cf
Jan 6 14:18:23 darkstar kernel: [ 1079.730126] [<ffffffff8210f322>] x86_64_start_reservations+0x132/0x136
Jan 6 14:18:23 darkstar kernel: [ 1079.730128] [<ffffffff8210f417>] x86_64_start_kernel+0xf1/0xf8
Jan 6 14:18:23 darkstar kernel: [ 1079.730129] handlers:
Jan 6 14:18:23 darkstar kernel: [ 1079.730130] [<ffffffffa0249310>] (ath5k_intr+0x0/0x350 [ath5k])
Jan 6 14:18:23 darkstar kernel: [ 1079.730136] Disabling IRQ #19
Jan 6 15:17:35 darkstar kernel: [ 4629.033958] hda-intel: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj.
----------------------------------------------------------------------------------------------------
Jan 6 19:55:21 darkstar kernel: [ 10.342054] hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x100f0000
Jan 6 19:55:21 darkstar kernel: [ 11.342184] hda-intel: No response from codec, disabling MSI: last cmd=0x100f0000
Jan 6 19:55:21 darkstar kernel: [ 12.342324] hda-intel: Codec #1 probe error; disabling it...
Jan 6 19:55:21 darkstar kernel: [ 12.350328] hda-intel: no codecs initialized
Jan 6 19:55:21 darkstar kernel: [ 15.362724] hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x400f0000
Jan 6 19:55:21 darkstar kernel: [ 16.363870] hda-intel: Codec #4 probe error; disabling it...
Jan 6 19:55:21 darkstar kernel: [ 17.372995] hda-intel: Codec #5 probe error; disabling it...
Jan 6 19:55:21 darkstar kernel: [ 18.382109] hda-intel: Codec #6 probe error; disabling it...
Jan 6 19:55:21 darkstar kernel: [ 19.391236] hda-intel: Codec #7 probe error; disabling it...
----------------------------------------------------------------------------------------------------------
Jan 6 20:05:23 darkstar kernel: [ 233.316805] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
Jan 6 22:13:22 darkstar kernel: [ 7907.057929] irq 19: nobody cared (try booting with the "irqpoll" option)
Jan 6 22:13:22 darkstar kernel: [ 7907.057935] Pid: 0, comm: swapper Tainted: P 2.6.37.6 #3
Jan 6 22:13:22 darkstar kernel: [ 7907.057938] Call Trace:
Jan 6 22:13:22 darkstar kernel: [ 7907.057940] <IRQ> [<ffffffff810aac2b>] __report_bad_irq.clone.2+0x2b/0xa0
Jan 6 22:13:22 darkstar kernel: [ 7907.057952] [<ffffffff810aae2e>] note_interrupt+0x18e/0x1d0
Jan 6 22:13:22 darkstar kernel: [ 7907.057957] [<ffffffff81074125>] ? sched_clock_idle_wakeup_event+0x15/0x20
Jan 6 22:13:22 darkstar kernel: [ 7907.057962] [<ffffffff810abc85>] handle_fasteoi_irq+0xc5/0xf0
Jan 6 22:13:22 darkstar kernel: [ 7907.057973] [<ffffffff81005a32>] handle_irq+0x22/0x40
Jan 6 22:13:22 darkstar kernel: [ 7907.057976] [<ffffffff81aa57b8>] do_IRQ+0x68/0xf0
Jan 6 22:13:22 darkstar kernel: [ 7907.057979] [<ffffffff81aa52d3>] ret_from_intr+0x0/0xa
Jan 6 22:13:22 darkstar kernel: [ 7907.057980] <EOI> [<ffffffff8159094c>] ? intel_idle+0xec/0x180
Jan 6 22:13:22 darkstar kernel: [ 7907.057984] [<ffffffff8159092b>] ? intel_idle+0xcb/0x180
Jan 6 22:13:22 darkstar kernel: [ 7907.057987] [<ffffffff819891e1>] cpuidle_idle_call+0x91/0x130
Jan 6 22:13:22 darkstar kernel: [ 7907.057988] [<ffffffff81000d2c>] cpu_idle+0x9c/0x120
Jan 6 22:13:22 darkstar kernel: [ 7907.057991] [<ffffffff81a6e82d>] rest_init+0x6d/0x80
Jan 6 22:13:22 darkstar kernel: [ 7907.057993] [<ffffffff8210fc49>] start_kernel+0x3c4/0x3cf
Jan 6 22:13:22 darkstar kernel: [ 7907.057995] [<ffffffff8210f322>] x86_64_start_reservations+0x132/0x136
Jan 6 22:13:22 darkstar kernel: [ 7907.057997] [<ffffffff8210f417>] x86_64_start_kernel+0xf1/0xf8
Jan 6 22:13:22 darkstar kernel: [ 7907.057998] handlers:
Jan 6 22:13:22 darkstar kernel: [ 7907.057998] [<ffffffffa0178310>] (ath5k_intr+0x0/0x350 [ath5k])
Jan 6 22:13:22 darkstar kernel: [ 7907.058005] Disabling IRQ #19
Thanks for the heads up to the other thread. I'll take a closer look tomorrow.
To me, the syslog entries are reflecting that the snd-hda-intel module has been associated with your nVidia audio, which is obviously incorrect.
Editing /etc/modprobe.d/sound.conf seems to be required to get the appropriate kernel modules associated with each sound device together with appropriate module options.
I tried adding snd_hda_codec_hdmi to the blacklist, still no sound.
alsaconf resulted in this:
Code:
Found hardware: "HDA-Intel" "Nvidia ID 14" "HDA:10de0014,10de0101,00100100" "0x3842" "0x1430"
Hardware is initialized using a generic method
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #1 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #2 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #3 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #4 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #5 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #6 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #7 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #8 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #9 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #10 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #11 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #12 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #13 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #14 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #15 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #16 (No such file or directory)
Setting default volumes...
It seemed to think it worked, but again, no sound.
alsaconf (again rewriting sound.conf) gives me this at the end again:
Code:
Loading ALSA mixer settings: /usr/sbin/alsactl restore
Found hardware: "HDA-Intel" "Realtek ALC892" "HDA:10ec0892,10438410,00100302" "0x1043" "0x8410"
Hardware is initialized using a generic method
Found hardware: "HDA-Intel" "Nvidia ID 14" "HDA:10de0014,10de0101,00100100" "0x3842" "0x1430"
Hardware is initialized using a generic method
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #1 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #2 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #3 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #4 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #5 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #6 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #7 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #8 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #9 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #10 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #11 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #12 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #13 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #14 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #15 (No such file or directory)
/usr/sbin/alsactl: set_control:1267: failed to obtain info for control #16 (No such file or directory)
Setting default volumes...
No joy with any of these. This entry in syslog remains consistent: "hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj."
Thanks for the welcome allend, but I'm not entirely new here. I used to post under exluddite, but I no longer use the email that I registered with so couldn't reset my password.
I built the system myself. The motherboard is an Asus P8P67 rev. 3.0. I'm using (well, trying to!) the onboard audio, chipset is Realtek ALC892, 8 channel. The Nvidia that is coming up is an EVGA GT430 video card.
Ok, this seems to be the winner. I also added "irqpoll" to lilo due to what I've been seeing in my syslog. Quite honestly I'm not sure which was the solution since I did both. I did notice that when I ran alsaconf, it deleted "options snd-intel-hda model=auto,auto enable_msi=1,0 index=0,1 id=Intel,NVidia" that allend suggested I add to sound.conf. Maybe it passes those parameters and then rewrites the file?
Thanks to allend for all the help.
I have a pretty same issue , with the my on board sound (Intel).
The story is as follow :
I re-install my slackware 13.37 (x86) in my desktop . The /home partition didn't formatted, i keep the same user folder with the old user configuration files.
I didn't install the kde packages.
I have no sound with the new installation.
The alsaconf cannot see the on board sound card and the sound.conf is missing from /etc/modprobe.d
here are some help info
lspci -k|grep -iA3 audio
Quote:
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)
Subsystem: ASUSTeK Computer Inc. Device 829f
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
@mpregos - I have no experience with your device, but if it was working before the reinstall then I suggest try the advice from our BDFL. http://www.linuxquestions.org/questi...5/#post4289480
Your device used to require options for the snd-hda-intel kernel module, but it is my understanding that this is no longer necessary. The output you posted suggests that your device is being recognised and appropriate kernel modules are being loaded.
@mpregos - I have no experience with your device, but if it was working before the reinstall then I suggest try the advice from our BDFL. http://www.linuxquestions.org/questi...5/#post4289480
Your device used to require options for the snd-hda-intel kernel module, but it is my understanding that this is no longer necessary. The output you posted suggests that your device is being recognised and appropriate kernel modules are being loaded.
Thanks for the try Allend.....Not solved....
I still search in google similar problem , but i didn't find anything.....believe yet!!!!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.