Re: hda-intel codec not being detected on ICH9 chipset

["Peter Westley" <alsa@xxxxxxxxxxxxx>]

Tobin,

On Sat, May 24, 2008 at 3:05 AM, Tobin Davis <tdavis@xxxxxxxxxxxx> wrote:

Before you go off and get rid of your board, there are a number of things to look at first.  According to an earlier post, it looked as though the audio may have been disabled in bios.

Checked that - all OK.

  Another possibility is that it worked before because the driver didn't even know about the codec (let alone the board).  When I looked at the tip source, the only motherboard that matched the subdevice id for your system was a 945 (ICH7/Sigmatel 9221).  Based on that, and the the way my board currently works (DP35DP - very similar), I am starting to think that it may be a problem with Ubuntu's alsa drivers (wouldn't be a first time, believe me).

I've tried building an Ubuntu 8.04  from scratch but that doesn't work. I'll also try it with the 7.10 desktop I think I originally had it working with. Haven't done that yet so can't report on it... standby for an update on that.

 

First thing to try, as suggested elsewhere, try removing your tuner card temporarily.  If audio comes up, then we have found the conflict.

 

Yes did that, same result.

  If not, try "acpi=off".

 

Also this, no luck
 

  Lastly, you can try downloading a daily snapshot from ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/ and building it with "./configure --with-cards=hda-intel --with-debug=detect".  Once you build and install it, type "lsmod|fgrep snd|awk '{print $1}'|xargs rmmod" to remove all sound modules, type "dmesg -c" to clear the dmesg log, then "modprobe snd_hda_intel" to load the new modules.  If you still don't get audio, type dmesg to see the latest output and email that info here.

 

OK built 20080524 from the above site (actually from ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/ because there's a 'README' there that says it's moved...)

Used:
./configure --with-cards=hda-intel --with-debug=detect
make
sudo make install

Then removed all the 'snd' modules with rmmod (couldn't use your above command - it required reverse dependency removal of the modules so I just did it manually - anyone written a script or is there an option to rmmod that ignores dependencies?)

and finally

dmesg -c
modprobe snd-hda-intel

No go.

Log contents folow

*************************
dmesg:
[14834.424775] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 23
[14834.424799] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[14834.495425] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-server/sound/alsa-driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1892: hda-intel: no codecs found!
[14834.495477] ACPI: PCI interrupt for device 0000:00:1b.0 disabled

*************************
tail /var/log/messages :
May 25 13:59:40 snoopy kernel: [14834.424775] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 23
May 25 13:59:40 snoopy kernel: [14834.495477] ACPI: PCI interrupt for device 0000:00:1b.0 disabled

Also tail /var/log/syslog is a little more telling (maybe!):
May 25 13:57:49 snoopy NetworkManager: <debug> [1211687869.615123] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/computer_oss_sequencer_0').
May 25 13:57:49 snoopy NetworkManager: <debug> [1211687869.618245] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/computer_oss_sequencer').
May 25 13:58:36 snoopy NetworkManager: <debug> [1211687916.647991] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/computer_alsa_sequencer').
May 25 13:58:50 snoopy NetworkManager: <debug> [1211687930.303908] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/computer_alsa_timer').
May 25 13:59:40 snoopy NetworkManager: <debug> [1211687980.458993] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/computer_alsa_timer').
May 25 13:59:40 snoopy NetworkManager: <debug> [1211687980.470466] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/computer_alsa_sequencer').
May 25 13:59:40 snoopy kernel: [14834.424775] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 23
May 25 13:59:40 snoopy kernel: [14834.424799] PCI: Setting latency timer of device 0000:00:1b.0 to 64
May 25 13:59:40 snoopy NetworkManager: <debug> [1211687980.486231] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/computer_oss_sequencer').
May 25 13:59:40 snoopy NetworkManager: <debug> [1211687980.495521] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/computer_oss_sequencer_0').
May 25 13:59:40 snoopy kernel: [14834.495425] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-server/sound/alsa-driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1892: hda-intel: no codecs found!
May 25 13:59:40 snoopy kernel: [14834.495477] ACPI: PCI interrupt for device 0000:00:1b.0 disabled

Curious to know why the hal is getting involved...
So that's where we are...
Peter

Tobin

On Fri, 2008-05-23 at 11:24 +1000, Peter Westley wrote:

On Fri, May 23, 2008 at 9:01 AM, Nigel Henry <cave.dnb2m97pp@xxxxxxxxxxxx> wrote:

On Friday 23 May 2008 00:27, Peter Westley wrote:
> Nigel,
>
> Thanks again for putting so much time into my problem! See comments inline.
>
> On Thu, May 22, 2008 at 5:15 AM, Nigel Henry <cave.dnb2m97pp@xxxxxxxxxxxx>
>
> wrote:
> > On Wednesday 21 May 2008 12:35, you wrote:
> > > Update:
> > >
> > > I removed the DVB-T card from the system and rebooted - same problem.
> > > System sees the card but the ALSA system doesn't recognise the codec
> > >
> > > <sigh> still looking.
> > >
> > > Peter
> >
> > Hi Peter. First of all it would be fair to say that there are horrible
> > problems with hda intel based cards, as they are setup differently on the
> > mobos of PC's/Laptops, depending on which machine you have. Laptops are
> > the worst, as your only alternative if you can't get the onboard hda
> > intel card to produce sounds, is to buy a USB, or pcmcia card. At least
> > with a PC, and aspare PCI slot you can buy a cheap, known Alsa supported
> > card, and get the sounds working.
> >
> > That said, you had sounds working when you had your Gutsy Gibbon
> > installed, so
> > at least you know the sounds worked with the hda intel card.
> >
> > You say that your not sure if the sounds stopped after installing the
> > server
> > version of Ubuntu GG, or after you'd installed HH 8.04. I spent a bit of
> > time
> > at the Ubuntu site looking at the server version, and the kernel. It did
> > say
> > the server kernel was somewhat different, but didn't say too much about
> > the differences. I don't know if there is some specific reason that you
> > need the
> > server kernel, but if not it may be worth installing the generic one, and
> > seeing if the sounds work ok with it.
> >
> > I'm a bit lost. Alsaconf is now deprecated, and no longer exists on GG.
> > You used to be able to run that command as root, and it would search for
> > soundcards, and if found set them up. I can't find anything on GG to
> > reconfigure the soundcard. All that running "asoundconf list " (no double
> > quotes)shows is soundcards that are already configured.
> >
> > There are a couple of things you could try to perhaps identify the
> > problem.
> >
> > First open konsole/terminal, and enter the following text.
> > sudo tail -f /var/log/messages
> > This should capture any problems when running the following stuff.
> >
> > Now open another instance of konsole/terminal, and run the following
> > command.
> > sudo /etc/init.d/alsa-utils stop
> > Followed by /etc/init.d/alsa-utils start
> > Any messages on the konsole running tail -f?
>
> I get:
> $ sudo /etc/init.d/alsa-utils stop
>  * Shutting down
> ALSA...                                                         * warning:
> 'alsactl store' failed with error message 'alsactl: save_state:1497: No
> soundcards found...'...                                              [fail]
>
> Which is to be expected I guess...
>
> Then:
> $ sudo /etc/init.d/alsa-utils start
>  * Setting up ALSA...                                                    [
> OK ]
>
> and in /var/log/messgaes:
> May 22 23:04:38 snoopy kernel: [97942.954373] ACPI: PCI Interrupt
> 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 23
> May 22 23:04:39 snoopy kernel: [97943.034189] ACPI: PCI interrupt for
> device 0000:00:1b.0 disabled
>
> Which is similar to what goes in dmesg when the system boots:
> >From demsg:
>
> [   40.254047] ALSA /build/buildd/linux-ubuntu
> -modules-2.6.24-2.6.24/debian/build/build-server/sound/alsa
> -driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1892:
> hda-intel: no codecs found!
> [   40.254089] ACPI: PCI interrupt for device 0000:00:1b.0 disabled
>
> > Also check out cat /proc/asound/cards, to see if any cards have appeared.
> > if
> > so we may be getting somewhere, but if not try the next suggestion, as
> > below.
>
> Nothing appeared
>
> Leaving the konsole running tail -f open, on the other konsole do.
>
> > rmmod snd-hda-intel
> > This may need to be run as.
> > modprobe -r snd-hda-intel, if the rmmod command fails.
> >
> > Now run.
> > modprobe snd-hda-intel
> >
> > Check again any output from the other konsole running tail -f, and also
> > run.
> > cat /proc/asound/cards, which may show detected cards.
>
> Nothing from those commands in /var/log/messages
>
> Whatever output you get on the konsole/terminal that is running tail
>
> > -f /var/log/messages, please post it to myself, and to the alsa-user
> > list.
> >
> > Personally, and if you have a spare PCI slot, I'd have a look on E-bay
> > for an
> > Audigy2 soundblaster card (emu10k1), which is the one I have. I think
> > they can be picked up quite cheaply, and I know that this card works.
> > Just a suggestion.
>
> That's exactly what I would have done ages ago but sadly my stupid
> motherboard has only one PCI slot  and that has the DVB-T card in it so
> sadly not an option.
>
> I will post to the alsa-dev  group and see what they have to say.
>
> Peter

Hi Peter. Sorry none of my suggestions produced any positive results.

As regards your mobo with only one PCI slot. That has to be quite pathetic.
You used to be able to get mobo's with 5 PCI slots, and I've been hunting for
a new atx mobo, to put in a case that I've had for some time. I have found an
atx one with 3 PCI slots, and a couple pf PCI express ones, and am waiting
for it to arrive (Asus M2N-X Plus). Not too expensive 52.50 euros. It too may
have a dodgy onboard soundcard. It will be interesting to see if the sound
works when it arrives.

Yes, do post to the alsa-development list. I hope someone there can help you
to get the sounds back up and running.

Nigel.

Nigel,

The mobo was was my own stupid fault - I bought it in a hurry and didn't research properly! It does have two PCIe slots but there's precious little in PCIe that Linux seems to support at all yet.

I will probably go the mobo replacement path eventually (then my 15yo son can have this one - he's been bugging me for one for ages!)

I am going to try one more thing and that is to install a fresh Ubuntu desktop onto an external drive and just check that the sound comes up there...

Peter

-------------------------------------------------------------------------

This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user