View previous topic :: View next topic |
Author |
Message |
Joseph K. Guru
Joined: 07 Jun 2006 Posts: 436 Location: Sydney, Australia
|
Posted: Sat Jun 13, 2009 2:31 pm Post subject: gentoo-sources-2.6.30 and ALSA: no sound |
|
|
I'm not getting any sound after booting 2.6.30-r1. I can see some warning or error messages regarding alsa_ctl or something during the boot phase, but can't find those messages in /var/log. How do I make sure such messages are getting logged somewhere? Thanks, cheers. |
|
Back to top |
|
|
TheAbu Apprentice
Joined: 08 Jun 2008 Posts: 160 Location: Lyon, France
|
Posted: Sat Jun 13, 2009 3:00 pm Post subject: |
|
|
Did you try the dmesg command ?
As for the problem, maybe it has to do with the fact that now the modprobe scripts need to have the conf extension (not totally sure but I think I saw a warning in the latest 2.6.29 releases _________________ "Please, forgive my bad English"
Gentoo made me love using my computer again. Thank you to the Gentoo devs and more generally to all the people who makes GNU/Linux possible |
|
Back to top |
|
|
Joseph K. Guru
Joined: 07 Jun 2006 Posts: 436 Location: Sydney, Australia
|
Posted: Sat Jun 13, 2009 5:56 pm Post subject: |
|
|
Yeah, there was nothing interesting in the dmesg output, it lists the correct card: Intel ICH6 with AD1981B at irq 21.
Hmmm, OK, I renamed all my files in /etc/modprobe.d/ to have a .conf extension but to no avail. And on additional inspection, the error is something about "invalid hardware" and a syntax error in /etc/init.d/alsasound. Seems like something weird is going on.
If someone can explain to me how to make sure those errors go through syslog, I'd sure appreciate it. Thanks, cheers. |
|
Back to top |
|
|
Autie Guru
Joined: 25 Jul 2003 Posts: 309 Location: Ledegem - Belgium
|
Posted: Sat Jun 13, 2009 8:45 pm Post subject: |
|
|
re-run alsaconf can fix alot _________________ The capacity to learn is a gift; The ability to learn is a skill; The willingness to learn is a choice. |
|
Back to top |
|
|
Timbers2k Apprentice
Joined: 03 Oct 2003 Posts: 215
|
Posted: Sat Jun 13, 2009 10:43 pm Post subject: |
|
|
I have the same issue. 2.6.30-r1 has no sound. All the modules are loaded, mixer levels are up, but no sound at all. Same config with 2.6.29 works fine. I'm on amd64. |
|
Back to top |
|
|
Binkerton n00b
Joined: 13 Jun 2009 Posts: 12
|
Posted: Sun Jun 14, 2009 12:08 am Post subject: |
|
|
I too have the same problem, run amd64, I think it might be the audio chipset a nvidia hda 262 I think |
|
Back to top |
|
|
Timbers2k Apprentice
Joined: 03 Oct 2003 Posts: 215
|
Posted: Sun Jun 14, 2009 1:15 am Post subject: |
|
|
no, I'm on an old motherboard with the via82xx driver, so I think it is something other than the specific driver. I haven't noticed any warnings during the boot, and nothing shows up in dmesg or /var/log. All the modules are loading correctly as far as I can tell. |
|
Back to top |
|
|
Binkerton n00b
Joined: 13 Jun 2009 Posts: 12
|
Posted: Sun Jun 14, 2009 1:15 pm Post subject: |
|
|
could it have something to do with a symlink to the newer kernel? |
|
Back to top |
|
|
Jorgo n00b
Joined: 18 Jun 2004 Posts: 62 Location: Bochum, Germany
|
Posted: Sun Jun 14, 2009 3:36 pm Post subject: |
|
|
Same here. There ist only a crippled noise when playing some music or video.
Booting kernel 2.6.29 is working fine. Seems to be a specific kernel-2.6.30 problem. |
|
Back to top |
|
|
platojones Veteran
Joined: 23 Oct 2002 Posts: 1602 Location: Just over the horizon
|
Posted: Sun Jun 14, 2009 4:08 pm Post subject: |
|
|
Sounds like this could be a specific driver regression....I'm running the new kernel with the emu_10k1 drivers and no issues...amd64 platform. |
|
Back to top |
|
|
doctork Guru
Joined: 25 Apr 2004 Posts: 370 Location: Cleveland, OH
|
Posted: Sun Jun 14, 2009 4:18 pm Post subject: |
|
|
platojones wrote: | Sounds like this could be a specific driver regression....I'm running the new kernel with the emu_10k1 drivers and no issues...amd64 platform. |
Same for me. I have no problem with the HDA-Intel drivers or usbsound headphones on an amd64 platform.
--
doc |
|
Back to top |
|
|
Fest n00b
Joined: 06 Dec 2008 Posts: 3
|
Posted: Sun Jun 14, 2009 7:54 pm Post subject: |
|
|
I got same issue, after upgrade to 2.6.30 sound gone and all i heard was noise (i used hda-intel driver). But in my case answer was pretty simple - upgrade somehow turned off pcm output. So check alsamixer maybe it help. |
|
Back to top |
|
|
Timbers2k Apprentice
Joined: 03 Oct 2003 Posts: 215
|
Posted: Sun Jun 14, 2009 8:44 pm Post subject: |
|
|
I found my problem. In alsamixer are a few new controls, in mine they are called VIA DXS, VIA DXS 1, VIA DXS 2, and VIA DXS 3. These were all turned down all the way and turning them up brought up sound for different things. The DXS made my system sounds work and the DXS 2 made sound in Wine work. I have no idea what the DXS stands for, I'll need to look it up. |
|
Back to top |
|
|
Jorgo n00b
Joined: 18 Jun 2004 Posts: 62 Location: Bochum, Germany
|
Posted: Mon Jun 15, 2009 7:31 am Post subject: |
|
|
Solved for me. PCM was totally disabled and didn't show up in control panel. |
|
Back to top |
|
|
bastibasti Guru
Joined: 27 Nov 2006 Posts: 590
|
Posted: Mon Jun 15, 2009 8:54 am Post subject: |
|
|
Make sure you do not enable PCSPKR under generic alsa drivers, as it will be loaded as your first "soundcard" |
|
Back to top |
|
|
Joseph K. Guru
Joined: 07 Jun 2006 Posts: 436 Location: Sydney, Australia
|
Posted: Mon Jun 15, 2009 1:26 pm Post subject: |
|
|
Hmmm, after fixing the expected warning messages about ".conf" extension, sound worked on my desktop with Intel HDA without having to fiddle with any mixer settings. Now to see if I can magically get my laptop to work... |
|
Back to top |
|
|
Joseph K. Guru
Joined: 07 Jun 2006 Posts: 436 Location: Sydney, Australia
|
Posted: Sun Jun 21, 2009 7:53 am Post subject: |
|
|
Autie wrote: | re-run alsaconf can fix alot |
My feeling is that alsaconf works only if you compiled ALSA as modules, right? Because I just tried it on two machines and on both it reported
Quote: | ERROR: modinfo: could not find module snd |
and couldn't find the sound card.
The good news is that sound is working on my laptop; similar to Jorgo, the PCM volume was down at zero, which for me I presume is related to the errors that appear when alsasound loads at boot. Actually, I'm going to check that out... |
|
Back to top |
|
|
krinn Watchman
Joined: 02 May 2003 Posts: 7470
|
Posted: Sun Jun 21, 2009 9:23 am Post subject: Re: gentoo-sources-2.6.30 and ALSA: no sound |
|
|
Joseph K. wrote: | How do I make sure such messages are getting logged somewhere? |
despite the warning "you are stopping a boot service" "/etc/init.d/alsasound restart" will allow you to see the message without need to log them. |
|
Back to top |
|
|
Joseph K. Guru
Joined: 07 Jun 2006 Posts: 436 Location: Sydney, Australia
|
Posted: Sun Jun 21, 2009 9:55 am Post subject: Re: gentoo-sources-2.6.30 and ALSA: no sound |
|
|
krinn wrote: | Joseph K. wrote: | How do I make sure such messages are getting logged somewhere? |
despite the warning "you are stopping a boot service" "/etc/init.d/alsasound restart" will allow you to see the message without need to log them. |
That's what I thought! But strangely enough, the errors don't occur when I restart it afterwards. Puzzling. So I inserted a pause in the alsasound script to see the error. It's something about unrecognised "ICH4" hardware, which is clearly wrong, because it's an ICH6 chipset. So then it tries to guess the mixer settings via /usr/share/alsa/init/default and that causes CTL syntax errors, blah blah blah. |
|
Back to top |
|
|
dpaking n00b
Joined: 15 May 2006 Posts: 15
|
Posted: Sun Jun 21, 2009 3:41 pm Post subject: |
|
|
Had the same problem on 2.6.29-gentoo-r5. No errors on /etc/init.d/alsasound. aplay would play a file, but Banshee or Rhythmbox would not.
Solved by: rename /etc/modules.d/alsa /etc/modules.d/alsa.conf
I'm going to check if there is anything filed in bugs to change output of alsaconf to alsa.conf for versions >=2.6.29.
Thanks for the advice everyone. |
|
Back to top |
|
|
robak Apprentice
Joined: 14 Jan 2004 Posts: 209 Location: Germany
|
Posted: Sun Jun 21, 2009 6:57 pm Post subject: |
|
|
same problem here on i686 with 2.6.30-r1 kernel and hda-intel driver build into kernel.
sound works, all controlles show up in alsamixer but no microphones are working. i tried to recompile alsa-utils alsa-tools alsa-headers alsa-plugins alsa-oss alsa-lib without success. _________________ run this in your gentoo-bash:
"grep -R -i -A2 -B2 'on fire' /usr/src/linux/*" |
|
Back to top |
|
|
Joseph K. Guru
Joined: 07 Jun 2006 Posts: 436 Location: Sydney, Australia
|
Posted: Tue Aug 04, 2009 3:11 am Post subject: |
|
|
Here are the errors when alsasound starts at boot for 2.6.30*:
Code: | * Restoring Mixer Levels...
Unknown hardware: "ICH4" "Analog Devices AD1981B" "AC97a:41445374" "0x103c" "0x0934"
Hardware is initialized using a guess method
/usr/share/alsa/init/default:51: control element not found
/usr/share/alsa/init/default:52: missing close brace for format
/usr/share/alsa/init/default:52: error parsing CTL attribute
/usr/share/alsa/init/default:52: invalid rule
* Errors while restoring defaults, ignoring [ ok ]
|
As I mentioned earlier, it's actually an ICH6 chipset, so I'm not surprised that "ICH4" is causing a problem. But why is this happening in 2.6.30? And is there a separate bug in the guess method file? |
|
Back to top |
|
|
rahulthewall Veteran
Joined: 01 Nov 2007 Posts: 1264 Location: Zürich
|
Posted: Tue Aug 04, 2009 9:15 am Post subject: |
|
|
Joseph K. wrote: | Here are the errors when alsasound starts at boot for 2.6.30*:
Code: | * Restoring Mixer Levels...
Unknown hardware: "ICH4" "Analog Devices AD1981B" "AC97a:41445374" "0x103c" "0x0934"
Hardware is initialized using a guess method
/usr/share/alsa/init/default:51: control element not found
/usr/share/alsa/init/default:52: missing close brace for format
/usr/share/alsa/init/default:52: error parsing CTL attribute
/usr/share/alsa/init/default:52: invalid rule
* Errors while restoring defaults, ignoring [ ok ]
|
As I mentioned earlier, it's actually an ICH6 chipset, so I'm not surprised that "ICH4" is causing a problem. But why is this happening in 2.6.30? And is there a separate bug in the guess method file? |
These errors are due to the fact that your /var/lib/alsa/asound.state does not comply with your new settings.
First, check the file /etc/modprobe.d/alsa.conf and check the module settings for alsa.
Then, run update-modules, remove /var/lib/alsa/asound.state.
Then, reboot - you will still get errors.
Then, Configure sound settings with alsamixer or something similar - this is the setting that you will get at startup.
Then, run /etc/init.d/alsasound save and then reboot.
It should work now. _________________ Who shall guard the guards? |
|
Back to top |
|
|
mv Watchman
Joined: 20 Apr 2005 Posts: 6780
|
Posted: Tue Aug 04, 2009 9:20 am Post subject: |
|
|
Joseph K. wrote: | Here are the errors when alsasound starts at boot for 2.6.30*:
Code: | * Restoring Mixer Levels...
Unknown hardware: "ICH4" "Analog Devices AD1981B" "AC97a:41445374" "0x103c" "0x0934"
Hardware is initialized using a guess method
/usr/share/alsa/init/default:51: control element not found
/usr/share/alsa/init/default:52: missing close brace for format
/usr/share/alsa/init/default:52: error parsing CTL attribute
/usr/share/alsa/init/default:52: invalid rule
* Errors while restoring defaults, ignoring [ ok ]
|
As I mentioned earlier, it's actually an ICH6 chipset, so I'm not surprised that "ICH4" is causing a problem. But why is this happening in 2.6.30? And is there a separate bug in the guess method file? |
I have the same message, only with another hardware shown (in my case the correct one, but also "unknown hardware"). It seems that something in the hardware recognition part of snd-intel is broken in 2.6.30 (in 2.6.29 it worked smoothly). Of course, once falling back to the "guess method", I think things can only go wrong... |
|
Back to top |
|
|
imeridian n00b
Joined: 12 Nov 2003 Posts: 67
|
Posted: Tue Aug 04, 2009 9:37 am Post subject: |
|
|
Add me to the list of users with broken sound also, similar error messages on boot about unknown hardware and "guessing" wrongly, of course.
I tried rahulthewall's instructions, but unfortunately they did not help me regain sound. The error message is gone, and I now get an annoying "pop" from my speakers when it comes to loading the alsa settings, but still no sound in Gnome. |
|
Back to top |
|
|
|