opensuse 11: Asus MoBo p5be-plus sound problem

English Hardware
#1

Guys,

Please help, i’ve read FAQ about sound tshooting in suse10.3 and forums concerning HD INTEL sound and ALSA and Asus mobos… still cant get it working…my mobo is Asus p5b-e plus with ADI® AD1988A 8 -Channel High Definition Audio CODEC (as it says in specs) with 6 jacks and spdif on the back and 2 jacks in the front.

i have the following in messages log:
Jun 25 17:00:47 vnikiforov-suse11 kernel: ALSA /usr/src/packages/BUILD/alsa-driver-unstable/pci/hda/…/…/alsa-kernel/pci/hda/hda_intel.c:2091: hda-intel: no codecs found!

tried to modify
/etc/modprobe.d/sound
to set model=6stack or 6stack-dig
the same ****… just not working…
please advise…

HWinfo output:
80: udi = ‘/org/freedesktop/Hal/devices/pci_8086_284b’
pci.vendor_id = 32902 (0x8086)
linux.hotplug_type = 2 (0x2)
info.subsystem = ‘pci’
pci.subsys_product_id = 33260 (0x81ec)
info.product = ‘82801H (ICH8 Family) HD Audio Controller’
linux.subsystem = ‘pci’
pci.subsys_vendor_id = 4163 (0x1043)
info.udi = ‘/org/freedesktop/Hal/devices/pci_8086_284b’
pci.device_class = 4 (0x4)
pci.device_subclass = 3 (0x3)
pci.device_protocol = 0 (0x0)
pci.vendor = ‘Intel Corporation’
linux.sysfs_path = ‘/sys/devices/pci0000:00/0000:00:1b.0’
info.vendor = ‘Intel Corporation’
info.parent = ‘/org/freedesktop/Hal/devices/computer’
pci.product = ‘82801H (ICH8 Family) HD Audio Controller’
pci.linux.sysfs_path = ‘/sys/devices/pci0000:00/0000:00:1b.0’
pci.subsys_vendor = ‘ASUSTeK Computer Inc.’
pci.product_id = 10315 (0x284b)
pci.subsys_product = ‘P5B’

tshooting script output:
general pastebin - root - post number 1055662

versions:
rpm -qa | grep alsa
alsa-driver-kmp-pae-1.0.16.20080619_2.6.25.5_1.1-1.1
alsa-tools-1.0.16.91.git20080610-1.1
alsa-devel-1.0.16.92.git20080617-1.1
alsa-oss-1.0.15.git20080610-3.4
alsa-utils-1.0.16.92.git20080617-1.1
alsa-1.0.16.92.git20080617-1.1
alsa-driver-doc-1.0.16.20080619-1.1
alsa-plugins-1.0.16-57.1
alsa-plugins-pulse-1.0.16-57.1
alsa-firmware-1.0.16.92.git20080617-1.1
alsa-tools-gui-1.0.16.91.git20080610-1.1
alsa-plugins-maemo-1.0.16-57.1

rpm -qa | grep pulse
libpulse0-0.9.10-26.1
alsa-plugins-pulse-1.0.16-57.1

rpm -q libasound2
libasound2-1.0.16.92.git20080617-1.1

uname -a
2.6.25.5-1.1-pae #1 SMP 2008-06-07 01:55:22 +0200 i686 i686 i386 GNU/Linux

cat /etc/modprobe.d/sound
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel

#2

Please check that your sound is switched ON in your BIOS.

Also, please check to see if there is an update for your BIOS from the asus site.

#3

of cause it’s on! :slight_smile: i’ve checked that already… it’s in HD audio mode (any way i tried to switch it to AC97 mode - the same result)

also i have latest bios ver…

#4

When did you run the alsa-info.sh script? I ask, because it does not detect your sound card, which is unusual. Did you run it earlier, before you provided all the various alsa, libasound2, pulse, /etc/modprobe.d/sound info? If so, please run the script again.

Could you type:
dmesg > dmeg.txt
and copy the output of dmesg.txt to general pastebin - simplified internet collaboration and paste the URL here, so we can check out your dmesg for any errors.

#5

as far as i understand, ALSA doesn’t detect any snd cards cause card is not recognized by ALSA’s drivers. The card itself is present on PCI bus…

here’s my dmesg output:
dmesg 26_06_08 - nopaste.com (beta)

and tsalsa script output:
tsalsa.txt - nopaste.com (beta)

#6

Thanks. There is no difference in the tsalsa and the dmesg makes the problem abundantly clear:

ALSA /usr/src/packages/BUILD/alsa-driver-unstable/pci/hda/…/…/alsa-kernel/pci/hda/hda_intel.c:2091: hda-intel: no codecs found!
I have seen this sort of error when users do not have sound enabled in their BIOS, and also when their BIOS is not up to date. In your case you say this does not apply to you.

I suspect if you do a:
lsmod | grep snd
it will show no kernel sound modules loaded.

and if you try and force the load with:
modprobe snd-hda-intel
I suspect it will fail.

I also suspect if you run “rcalsasound restart” it will fail.

A search on the alsa web site for AD1988A yields this:
Search results - AlsaProject for AD1988A
suggesting that that codec should be identified. You are cetain this is an AD1988A?

In the ALSA-Configuration.txt file, I see no mention of an AD1988A, … only an AD1988:

939		AD1988
940		  6stack	6-jack
941		  6stack-dig	ditto with SPDIF
942		  3stack	3-jack
943		  3stack-dig	ditto with SPDIF
944		  laptop	3-jack with hp-jack automute
945		  laptop-dig	ditto with SPDIF
946		  auto		auto-config reading BIOS (default)

Linux Kernel Documentation :: sound : alsa : ALSA-Configuration.txt

You could try see if any of these AD1988 options work with the AD1988A, via changing your /etc/modprobe.d/sound file to:

alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
options snd-hda-intel model=auto

and reboot.

if that doesn’t work, try

alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
options snd-hda-intel model=6stack

and reboot.

… etc … for each of the model options. Its possible “rcalsasound restart” would also work (as opposed to a reboot), but normally when I have recommended an “rcalsasound restart” one’s alsa was loaded in the first place. Yours was not.

You could also remove any pulse audio applications before trying any of the above, so that it does not obscure the issue. Simply make note of what you remove, so you can put the applications back later.

#7

Thank you very much for your support.

I’ve already tried the same settings of modprobe.d/sound with different model= parameter. (auto,6stack,3stack)

“rcalsasound restart” works just great without any reboots.

I’ve checked the sound card bios settings (HD audio controller enabled). Also i’ve tried to reset CMOS settings to safe defaults…

BTW when im disabling HD audio controller in bios it’s just absent in linux logs like it’s just not exist. (and it’s not detected in yast control center in hardware->audio)
So it’s working but some problem with drivers…

BTW2 - it’s working perfectly clear in windows xp (on the same machine).

Maybe i should write to ALSA support forum? or what? i presume it’s not opensuse 11 prob?

mobo specs:
ASUSTeK Computer Inc.

audio codec specs:
Analog Devices: HD Audio CODEC, 10 Channels up to 95 dB Performance

#8

Please note the syntax I used in the /etc/modprobe.d/sound file for openSUSE-11.0. This is different from the syntax I would use in 10.3. I changed this because I have read of cases where the old 10.3 syntax did not work for 11.0 for some users.

What happens when you run “rcalsasound restart” and then run the diagnostic script? Does it still fail to recognize your sound card?

Did you try the “modprobe snd-hda-intel” and “lsmod | grep snd” commands?

This is looking like a bug. You could write it on either openSUSE, or on alsa, or on both. I believe Novell are one of (if the) main contributor to alsa, hence I suspect a bug report written on alsa in either location will garner openSUSE sound development team attention.

#9

I just realized there is an inconsistency between this (which states you have alsa-1.0.17RC2):

and this output of the rpm command, which states you have alsa-1.0.16.

I no longer have ANY confidence that you have the correct alsa installed. Since you changed your configuration in the middle of a thread, with no clear advisement of the change (that I can see) I have no confidence now that the recommendations I gave were good.

Your script output has all the makings of a failure to install alsa-driver-kmp-pae-somekernel.

Please, can you provide the current output of:
rpm -qa | grep alsa
so I can check your configuration.

#10

Please note the syntax I used in the /etc/modprobe.d/sound file for openSUSE-11.0. This is different from the syntax I would use in 10.3. I changed this because I have read of cases where the old 10.3 syntax did not work for 11.0 for some users.

yes i’ve tried you config anyway.

What happens when you run “rcalsasound restart” and then run the diagnostic script? Does it still fail to recognize your sound card?
Did you try the “modprobe snd-hda-intel” and “lsmod | grep snd” commands?

vnikiforov-suse11:~ # rcalsasound restart
Starting sound driver: hda-intel done
vnikiforov-suse11:~ # modprobe snd-hda-intel
vnikiforov-suse11:~ # lsmod | grep snd
snd_pcm_oss 65152 0
snd_mixer_oss 33536 1 snd_pcm_oss
snd_seq 74816 0
snd_seq_device 24972 1 snd_seq
snd_hda_intel 404892 0
snd_pcm 101636 2 snd_pcm_oss,snd_hda_intel
snd_timer 40584 2 snd_seq,snd_pcm
snd_page_alloc 27400 2 snd_hda_intel,snd_pcm
snd_hwdep 26372 1 snd_hda_intel
snd 83268 8 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_pcm,snd_timer,snd_hwdep
soundcore 24264 1 snd

This is looking like a bug. You could write it on either openSUSE, or on alsa, or on both. I believe Novell are one of (if the) main contributor to alsa, hence I suspect a bug report written on alsa in either location will garner openSUSE sound development team attention.

Please advice the bugreport location, i haven’t found ALSA’s support forum - they have wiki page only…

#11

A didnt change any ALSA version during our conversation
my current config is the same:
rpm -qa | grep alsa
alsa-driver-kmp-pae-1.0.16.20080619_2.6.25.5_1.1-1.1
alsa-tools-1.0.16.91.git20080610-1.1
alsa-devel-1.0.16.92.git20080617-1.1
alsa-oss-1.0.15.git20080610-3.4
alsa-utils-1.0.16.92.git20080617-1.1
alsa-1.0.16.92.git20080617-1.1
alsa-driver-doc-1.0.16.20080619-1.1
alsa-plugins-1.0.16-57.1
alsa-firmware-1.0.16.92.git20080617-1.1
alsa-tools-gui-1.0.16.91.git20080610-1.1
alsa-plugins-maemo-1.0.16-57.1

i have to idea why tsalsa tells us it’s 1.0.17rc2

#12

I just realized there is an inconsistency between this (which states you have alsa-1.0.17RC2) the list of installed alsa rpms you posted. Your script output has all the makings of a failure to install alsa-driver-kmp-pae-somekernel.

Please, can you provide the current output of:
rpm -qa | grep alsa
so I can check your configuration.

and? with proof of the sound modules loaded, did you then re-start alsa (with “rcalsasound restart”) and test your sound?

#13

OK, having checked that, I now suspect a naming convention change amongst the openSUSE developers/packagers who are posting those rpms. Even though the rpms state 1.0.16 in the file name, I suspect they really are 1.0.17RC2 (and hence then there is no inconsistency in what you posted).

#14

is it true? how can i confirm that there is module install failure?
as far as i know linux when modprobe tell us nothing and lsmod displays module than module is installed correctly and recognized by kernel.

but as us can see in lsmod the trailing 0 (zero) tell us that it’s not in use?!

and? with proof of the sound modules loaded, did you then re-start alsa (with “rcalsasound restart”) and test your sound?

yes rcalsasound restart working as ALSA is installed in the system but it stil failes to detect audio codec…

#15

you know what, i’m going to test it on linux mint5 live cd on saturday or on monday…
I just checked that at home: my home mobo asus p5kc with Realtek ALC 883, 8-channel High-Definition Audio CODEC is recognized and working just great in mint5. (it’s recognized as HDA Intel) also mint5 have the same version of alsa 1.0.16 so i’ll give it a try…

#16

alsa bug reporting: https://bugtrack.alsa-project.org/alsa-bug/login_page.php

openSUSE bug reporting: Submitting Bug Reports - openSUSE

#17

I was searching for information to help someone else, and I stumbled across this:
TroubleShooting - ALSA wiki - Asus P5E motherboards tidbit

hda-intel: no codecs found!

The error message “hda-intel: no codecs found!” can be experienced, when the snd-hda-intel module fails to find the codec chip of your sound device. This may for example happen if your PCIe 1x sound card is in the wrong slot. For example on ASUS P5E mainboards, the supplied sound card is supposed to be inserted in the top most PCIe 1x slot. This is the brown slot on the P5E.
… Is this relevant to your problem?

#18

not really… cause my AD1988a codec is integrated to motherboard… and i presume it’s not occupying any pci-e slots…

also russia lost to spain 3:0… that’s a major fault… :frowning:

#19

Are there any BIOS controls for a “virtual” slot location control for your integrated sound device?

#20

No, there is no such a thing in BIOS.

I’ve tried to boot from linux Mint5 live cd.

the result is the same it’s not working:

dpkg -p alsa-base:

Package: alsa-base
Version: 1.0.16-0ubuntu4
Provides: alsa
Depends: linux-sound-base, lsof (>= 4.64), module-init-tools (>= 3.2.1)

lsmod | grep snd:
snd_hda_intel 344728 0
snd_pcm_oss 42144 0
snd_mixer_oss 17920 1 snd_pcm_oss
snd_pcm 78596 2 snd_hda_intel,snd_pcm_oss
snd_page_alloc 11400 2 snd_hda_intel,snd_pcm
snd_hwdep 10500 1 snd_hda_intel
snd_seq_dummy 4868 0
snd_seq_oss 35584 0
snd_seq_midi 9376 0
snd_rawmidi 25760 1 snd_seq_midi
snd_seq_midi_event 8320 2 snd_seq_oss,snd_seq_midi
snd_seq 54224 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 24836 2 snd_pcm,snd_seq
snd_seq_device 9612 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd 56996 11 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_hwdep,snd_seq_dummy,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore 8800 1 snd

cat /var/logs/messages | grep HDA
Jun 27 11:54:40 mint kernel: 72.535331] HDA Intel: probe of 0000:00:1b.0 failed with error -16