Codec + Mixer: IDT 92HD71B7X - STAC92xx Analog [STAC92xx Analog] Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) - no sound on HP Pavilion dv4-1220 US 64 Bit laptop in Ubuntu 9.04

     Do you have latest version of alsa? If so, check to see what your computer is using for a sound card and see it there are updated Linux drivers for it.

Hi,

In order to gather essential troubleshooting information about your sound card, please first follow this procedure:

Step 1: Open Terminal from "Applications->Accessories->
Terminal"

Step 2: Run the following 2 commands (copy/paste each command into the Terminal and then hit <enter> after each command)

wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh

bash alsa-info.sh

When the alsa-info.sh script asks "Do you want to run this script? [y/n]", press y and then hit <enter> to make sure the script actually runs. Please send us the full terminal output after the script has actually run.

Step 3: Run the following command. The command STARTS with the word cat and ENDS with the word snd. So please copy-paste the ENTIRE command below into a Terminal, press enter, then enter password when sudo asks for password, then press enter again.

cat /proc/asound/cards; sudo aptitude install gnome-alsamixer asoundconf-gtk alsa-utils flashplugin-nonfree-extrasound ; asoundconf list; aplay -l; sudo lshw -C sound; ls -lart /dev/snd; cat /dev/sndstat; lspci -nn ; lsmod | grep snd

Step 4: Please post results (copy/paste terminal output) on this thread

Step 5: Please also report on this thread if you cannot hear sound through the speakers, the headphones or cannot hear sound on both.

Step 6: Please also specify the exact model and make of your PC (if possible) on this thread

Step 7: If you are using a dual boot system (with Windows and Ubuntu installed on separate partitions),
then make sure to set the sound volume in Windows to a high level before booting into Ubuntu.
Also make sure to use the special function keys in Windows to make sure the loudspeakers are physically switched ON and working properly in Windows before installing and testing Ubuntu. This step is necessary with certain Toshiba Tecra laptops.

Step 8: Experiment with the audio settings in gnome-alsamixer and asoundconf-gtk until you get sound (hopefully)

Step 9: In System/Administration/Users and Groups , make sure that your user and the root user are members of the following 5 groups:

pulse

pulse-access

pulse-rt

audio

video

Step 10: Run the command gnome-volume-control and set the Sound Theme to "No sounds" (Sound Theme is also accessible via System > Preferences > Sound)

Step 11: Try connecting headphones to different audio jacks/ports on the backpanel of the sound card until you hopefully hear sound

Step 12: If you happen to have two soundcards installed in your pc, one integrated into the motherboard and one inserted into a PCI slot, then try removing the PCI audio card, reboot your pc and retest sound using only the motherboard's soundchip.

======================================================================================================

Please also read the following pages

http://www.ubuntugeek.com/sound-solutions-for-ubuntu-904-jaunty-users.html

http://doc.ubuntu-fr.org/audio_intel_hda (check for correct /etc/modprobe.d/alsa-base.conf options at bottom of this page)

https://help.ubuntu.com/community/SoundTroubleshooting

http://ubuntuforums.org/showthread.php?t=789578&highlight=audacity

for some initial suggestions.

You should add the following string to the /etc/modprobe.d/alsa-base.conf file

options snd-hda-intel model=YOUR_MODEL

Valid model names (that replace YOUR_MODEL) depending on the codec chip, can be found at

http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-jaunty.git;a=blob_plain;f=Documentation/sound/alsa/ALSA-Configuration.txt

If you do not know your codec chip name, you can execute the following Terminal command to find out:

cat /proc/asound/card*/codec* | grep Codec

Each combination of audio codec, audio mixer and audio device name requires a very specific configuration in the alsa-base.conf file, if the audio chipset does not work out-of-the-box.

Make sure to set all channels to high volume levels in gnome-alsamixer.

Make sure all the different speakers (including 'Front', 'Master', and 'PCM") are NOT muted and NOT set to low volume levels in gnome-alsamixer.

If sound still does not work, try upgrading ALSA to the newest version, reboot and retest sound.

ALSA upgrade procedure is here:

http://monespaceperso.org/blog-en/2009/05/09/upgrade-alsa-1020-on-ubuntu-jaunty-904/

Kind regards,

Mark

On Tue, Aug 11, 2009 at 2:27 AM, Mark Rijckenberg <
<email address hidden>> wrote:

> Your question #79688 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/79688
>
> Mark Rijckenberg requested for more information:
> Hi,
>
> In order to gather essential troubleshooting information about your
> sound card, please first follow this procedure:
>
> Step 1: Open Terminal from "Applications->Accessories->
> Terminal"
>
> Step 2: Run the following 2 commands (copy/paste each command into the
> Terminal and then hit <enter> after each command)
>
> wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh
>
> bash alsa-info.sh
>
> When the alsa-info.sh script asks "Do you want to run this script?
> [y/n]", press y and then hit <enter> to make sure the script actually
> runs. Please send us the full terminal output after the script has
> actually run.
>
> Step 3: Run the following command. The command STARTS with the word cat
> and ENDS with the word snd. So please copy-paste the ENTIRE command
> below into a Terminal, press enter, then enter password when sudo asks
> for password, then press enter again.
>
> cat /proc/asound/cards; sudo aptitude install gnome-alsamixer
> asoundconf-gtk alsa-utils flashplugin-nonfree-extrasound ; asoundconf
> list; aplay -l; sudo lshw -C sound; ls -lart /dev/snd; cat /dev/sndstat;
> lspci -nn ; lsmod | grep snd
>
> Step 4: Please post results (copy/paste terminal output) on this thread
>
> Step 5: Please also report on this thread if you cannot hear sound
> through the speakers, the headphones or cannot hear sound on both.
>
> Step 6: Please also specify the exact model and make of your PC (if
> possible) on this thread
>
> Step 7: If you are using a dual boot system (with Windows and Ubuntu
> installed on separate partitions),
> then make sure to set the sound volume in Windows to a high level before
> booting into Ubuntu.
> Also make sure to use the special function keys in Windows to make sure the
> loudspeakers are physically switched ON and working properly in Windows
> before installing and testing Ubuntu. This step is necessary with certain
> Toshiba Tecra laptops.
>
> Step 8: Experiment with the audio settings in gnome-alsamixer and
> asoundconf-gtk until you get sound (hopefully)
>
> Step 9: In System/Administration/Users and Groups , make sure that your
> user and the root user are members of the following 5 groups:
>
> pulse
>
> pulse-access
>
> pulse-rt
>
> audio
>
> video
>
> Step 10: Run the command gnome-volume-control and set the Sound Theme to
> "No sounds" (Sound Theme is also accessible via System > Preferences >
> Sound)
>
> Step 11: Try connecting headphones to different audio jacks/ports on the
> backpanel of the sound card until you hopefully hear sound
>
> Step 12: If you happen to have two soundcards installed in your pc, one
> integrated into the motherboard and one inserted into a PCI slot, then
> try removing the PCI audio card, reboot your pc and retest sound using
> only the motherboard's soundchip.
>
>
> ======================================================================================================
>
> Please also read the following pages
>
> http://www.ubuntugeek.com/sound-solutions-for-ubuntu-904-jaunty-
> users.html<http://www.ubuntugeek.com/sound-solutions-for-ubuntu-904-jaunty-%0Ausers.html>
>
> http://doc.ubuntu-fr.org/audio_intel_hda (check for correct
> /etc/modprobe.d/alsa-base.conf options at bottom of this page)
>
> https://help.ubuntu.com/community/SoundTroubleshooting
>
> http://ubuntuforums.org/showthread.php?t=789578&highlight=audacity
>
> for some initial suggestions.
>
> You should add the following string to the /etc/modprobe.d/alsa-
> base.conf file
>
> options snd-hda-intel model=YOUR_MODEL
>
> Valid model names (that replace YOUR_MODEL) depending on the codec chip,
> can be found at
>
> http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
> jaunty.git;a=blob_plain;f=Documentation/sound/alsa/ALSA-
> Configuration.txt
>
> If you do not know your codec chip name, you can execute the following
> Terminal command to find out:
>
> cat /proc/asound/card*/codec* | grep Codec
>
> Each combination of audio codec, audio mixer and audio device name
> requires a very specific configuration in the alsa-base.conf file, if
> the audio chipset does not work out-of-the-box.
>
> Make sure to set all channels to high volume levels in gnome-alsamixer.
>
> Make sure all the different speakers (including 'Front', 'Master', and
> 'PCM") are NOT muted and NOT set to low volume levels in gnome-
> alsamixer.
>
> If sound still does not work, try upgrading ALSA to the newest version,
> reboot and retest sound.
>
> ALSA upgrade procedure is here:
>
> http://monespaceperso.org/blog-en/2009/05/09/upgrade-alsa-1020-on-
> ubuntu-jaunty-904/<http://monespaceperso.org/blog-en/2009/05/09/upgrade-alsa-1020-on-%0Aubuntu-jaunty-904/>
>
> Kind regards,
>
> Mark
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+question/79688
>
> You received this question notification because you are a direct
> subscriber of the question.
>
ken@ubuntu:~$ wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh
--2009-08-11 12:25:37-- http://www.alsa-project.org/alsa-info.sh
Resolving www.alsa-project.org... 212.20.107.51
Connecting to www.alsa-project.org|212.20.107.51|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location:
http://git.alsa-project.org/?p=alsa-driver.git;a=blob_plain;f=utils/alsa-info.sh[following]
--2009-08-11 12:25:37--
http://git.alsa-project.org/?p=alsa-driver.git;a=blob_plain;f=utils/alsa-info.sh
Resolving git.alsa-project.org... 212.20.107.51
Reusing existing connection to www.alsa-project.org:80.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/plain]
Saving to: `alsa-info.sh'

    [ <=> ] 26,185 76.6K/s in
0.3s

2009-08-11 12:25:39 (76.6 KB/s) - `alsa-info.sh' saved [26185]

ken@ubuntu:~$ bash alsa-info.sh
ALSA Information Script v 0.4.57
--------------------------------

This script visits the following commands/files to collect diagnostic
information about your ALSA installation and sound related hardware.

  dmesg
  lspci
  lsmod
  aplay
  amixer
  alsactl
  /proc/asound/
  /sys/class/sound/
  ~/.asoundrc (etc.)

See 'alsa-info.sh --help' for command line options.

Automatically upload ALSA information to www.alsa-project.org? [y/N] : y
Uploading information to www.alsa-project.org ... Done!

Your ALSA information is located at
http://www.alsa-project.org/db/?f=a194d14deacae33c8c289f199cdf2488ecb51950

Please inform the person helping you.

ken@ubuntu:~$ cat /proc/asound/cards; sudo aptitude install gnome-alsamixer
 0 [SB ]: HDA-Intel - HDA ATI SB
                      HDA ATI SB at 0x92500000 irq 16
 1 [HDMI ]: HDA-Intel - HDA ATI HDMI
                      HDA ATI HDMI at 0x92410000 irq 19
Reading package lists... Done
Building dependency tree
Reading state information... Done
Initializing package states... Done
Writing extended state information... Done
The following NEW packages will be installed:
  gnome-alsamixer
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 56.6kB of archives. After unpacking 610kB will be used.
Writing extended state information... Done
Get:1 http://us.archive.ubuntu.com jaunty/universe gnome-alsamixer
0.9.7~cvs.20060916.ds.1-2 [56.6kB]
Fetched 56.6kB in 1s (44.0kB/s)
Selecting previously deselected package gnome-alsamixer.
(Reading database ... 105767 files and directories currently installed.)
Unpacking gnome-alsamixer (from
.../gnome-alsamixer_0.9.7~cvs.20060916.ds.1-2_amd64.deb) ...
Processing triggers for man-db ...
Processing triggers for menu ...
Setting up gnome-alsamixer (0.9.7~cvs.20060916.ds.1-2) ...

Processing triggers for menu ...
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Writing extended state information... Done

ken@ubuntu:~$

Hi,

Please try this procedure:

1. copy-paste the following command into the Terminal:

gksudo gedit /etc/modprobe.d/alsa-base.conf

2. and add these lines to the end of the file:

# Keep snd-pcsp from being loaded as first soundcard
options snd-pcsp index=-2
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
options snd-hda-intel model=hp-dv5
options snd-hda-intel enable_msi=1

3. Then navigate to System>Preferences>Sound and change everything to ALSA

4. reboot and retest sound

5. If sound still does not work, then replace hp-dv5 with one of the following 4 model options:

 STAC92HD71B*
   ref
   dell-m4-1
   dell-m4-2
   dell-m4-3

6. You will have to reboot and retest sound after every model option change to the alsa-base.conf file

See

https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/75353

for more info.

Regards,

Mark

On Tue, Aug 11, 2009 at 12:37 PM, Kenneth Boardman <email address hidden> wrote:

>
>
> On Tue, Aug 11, 2009 at 2:27 AM, Mark Rijckenberg <
> <email address hidden>> wrote:
>
>> Your question #79688 on Ubuntu changed:
>> https://answers.launchpad.net/ubuntu/+question/79688
>>
>> Mark Rijckenberg requested for more information:
>> Hi,
>>
>> In order to gather essential troubleshooting information about your
>> sound card, please first follow this procedure:
>>
>> Step 1: Open Terminal from "Applications->Accessories->
>> Terminal"
>>
>> Step 2: Run the following 2 commands (copy/paste each command into the
>> Terminal and then hit <enter> after each command)
>>
>> wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh
>>
>> bash alsa-info.sh
>>
>> When the alsa-info.sh script asks "Do you want to run this script?
>> [y/n]", press y and then hit <enter> to make sure the script actually
>> runs. Please send us the full terminal output after the script has
>> actually run.
>>
>> Step 3: Run the following command. The command STARTS with the word cat
>> and ENDS with the word snd. So please copy-paste the ENTIRE command
>> below into a Terminal, press enter, then enter password when sudo asks
>> for password, then press enter again.
>>
>> cat /proc/asound/cards; sudo aptitude install gnome-alsamixer
>> asoundconf-gtk alsa-utils flashplugin-nonfree-extrasound ; asoundconf
>> list; aplay -l; sudo lshw -C sound; ls -lart /dev/snd; cat /dev/sndstat;
>> lspci -nn ; lsmod | grep snd
>>
>> Step 4: Please post results (copy/paste terminal output) on this thread
>>
>> Step 5: Please also report on this thread if you cannot hear sound
>> through the speakers, the headphones or cannot hear sound on both.
>>
>> Step 6: Please also specify the exact model and make of your PC (if
>> possible) on this thread
>>
>> Step 7: If you are using a dual boot system (with Windows and Ubuntu
>> installed on separate partitions),
>> then make sure to set the sound volume in Windows to a high level before
>> booting into Ubuntu.
>> Also make sure to use the special function keys in Windows to make sure
>> the loudspeakers are physically switched ON and working properly in Windows
>> before installing and testing Ubuntu. This step is necessary with certain
>> Toshiba Tecra laptops.
>>
>> Step 8: Experiment with the audio settings in gnome-alsamixer and
>> asoundconf-gtk until you get sound (hopefully)
>>
>> Step 9: In System/Administration/Users and Groups , make sure that your
>> user and the root user are members of the following 5 groups:
>>
>> pulse
>>
>> pulse-access
>>
>> pulse-rt
>>
>> audio
>>
>> video
>>
>> Step 10: Run the command gnome-volume-control and set the Sound Theme to
>> "No sounds" (Sound Theme is also accessible via System > Preferences >
>> Sound)
>>
>> Step 11: Try connecting headphones to different audio jacks/ports on the
>> backpanel of the sound card until you hopefully hear sound
>>
>> Step 12: If you happen to have two soundcards installed in your pc, one
>> integrated into the motherboard and one inserted into a PCI slot, then
>> try removing the PCI audio card, reboot your pc and retest sound using
>> only the motherboard's soundchip.
>>
>>
>> ======================================================================================================
>>
>> Please also read the following pages
>>
>> http://www.ubuntugeek.com/sound-solutions-for-ubuntu-904-jaunty-
>> users.html<http://www.ubuntugeek.com/sound-solutions-for-ubuntu-904-jaunty-%0Ausers.html>
>>
>> http://doc.ubuntu-fr.org/audio_intel_hda (check for correct
>> /etc/modprobe.d/alsa-base.conf options at bottom of this page)
>>
>> https://help.ubuntu.com/community/SoundTroubleshooting
>>
>> http://ubuntuforums.org/showthread.php?t=789578&highlight=audacity
>>
>> for some initial suggestions.
>>
>> You should add the following string to the /etc/modprobe.d/alsa-
>> base.conf file
>>
>> options snd-hda-intel model=YOUR_MODEL
>>
>> Valid model names (that replace YOUR_MODEL) depending on the codec chip,
>> can be found at
>>
>> http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
>> jaunty.git;a=blob_plain;f=Documentation/sound/alsa/ALSA-
>> Configuration.txt
>>
>> If you do not know your codec chip name, you can execute the following
>> Terminal command to find out:
>>
>> cat /proc/asound/card*/codec* | grep Codec
>>
>> Each combination of audio codec, audio mixer and audio device name
>> requires a very specific configuration in the alsa-base.conf file, if
>> the audio chipset does not work out-of-the-box.
>>
>> Make sure to set all channels to high volume levels in gnome-alsamixer.
>>
>> Make sure all the different speakers (including 'Front', 'Master', and
>> 'PCM") are NOT muted and NOT set to low volume levels in gnome-
>> alsamixer.
>>
>> If sound still does not work, try upgrading ALSA to the newest version,
>> reboot and retest sound.
>>
>> ALSA upgrade procedure is here:
>>
>> http://monespaceperso.org/blog-en/2009/05/09/upgrade-alsa-1020-on-
>> ubuntu-jaunty-904/<http://monespaceperso.org/blog-en/2009/05/09/upgrade-alsa-1020-on-%0Aubuntu-jaunty-904/>
>>
>> Kind regards,
>>
>> Mark
>>
>> --
>> To answer this request for more information, you can either reply to
>> this email or enter your reply at the following page:
>> https://answers.launchpad.net/ubuntu/+question/79688
>>
>> You received this question notification because you are a direct
>> subscriber of the question.
>>
> ken@ubuntu:~$ wget -O alsa-info.sh
> http://www.alsa-project.org/alsa-info.sh
> --2009-08-11 12:25:37-- http://www.alsa-project.org/alsa-info.sh
> Resolving www.alsa-project.org... 212.20.107.51
> Connecting to www.alsa-project.org|212.20.107.51|:80... connected.
> HTTP request sent, awaiting response... 302 Found
> Location:
> http://git.alsa-project.org/?p=alsa-driver.git;a=blob_plain;f=utils/alsa-info.sh[following]
> --2009-08-11 12:25:37--
> http://git.alsa-project.org/?p=alsa-driver.git;a=blob_plain;f=utils/alsa-info.sh
> Resolving git.alsa-project.org... 212.20.107.51
> Reusing existing connection to www.alsa-project.org:80.
> HTTP request sent, awaiting response... 200 OK
> Length: unspecified [text/plain]
> Saving to: `alsa-info.sh'
>
> [ <=> ] 26,185 76.6K/s in
> 0.3s
>
> 2009-08-11 12:25:39 (76.6 KB/s) - `alsa-info.sh' saved [26185]
>
> ken@ubuntu:~$ bash alsa-info.sh
> ALSA Information Script v 0.4.57
> --------------------------------
>
> This script visits the following commands/files to collect diagnostic
> information about your ALSA installation and sound related hardware.
>
> dmesg
> lspci
> lsmod
> aplay
> amixer
> alsactl
> /proc/asound/
> /sys/class/sound/
> ~/.asoundrc (etc.)
>
> See 'alsa-info.sh --help' for command line options.
>
> Automatically upload ALSA information to www.alsa-project.org? [y/N] : y
> Uploading information to www.alsa-project.org ... Done!
>
> Your ALSA information is located at
> http://www.alsa-project.org/db/?f=a194d14deacae33c8c289f199cdf2488ecb51950
>
> Please inform the person helping you.
>
> ken@ubuntu:~$ cat /proc/asound/cards; sudo aptitude install
> gnome-alsamixer
> 0 [SB ]: HDA-Intel - HDA ATI SB
> HDA ATI SB at 0x92500000 irq 16
> 1 [HDMI ]: HDA-Intel - HDA ATI HDMI
> HDA ATI HDMI at 0x92410000 irq 19
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Initializing package states... Done
> Writing extended state information... Done
> The following NEW packages will be installed:
> gnome-alsamixer
> 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 56.6kB of archives. After unpacking 610kB will be used.
> Writing extended state information... Done
> Get:1 http://us.archive.ubuntu.com jaunty/universe gnome-alsamixer
> 0.9.7~cvs.20060916.ds.1-2 [56.6kB]
> Fetched 56.6kB in 1s (44.0kB/s)
> Selecting previously deselected package gnome-alsamixer.
> (Reading database ... 105767 files and directories currently installed.)
> Unpacking gnome-alsamixer (from
> .../gnome-alsamixer_0.9.7~cvs.20060916.ds.1-2_amd64.deb) ...
> Processing triggers for man-db ...
> Processing triggers for menu ...
> Setting up gnome-alsamixer (0.9.7~cvs.20060916.ds.1-2) ...
>
> Processing triggers for menu ...
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Reading extended state information
> Initializing package states... Done
> Writing extended state information... Done
>
> ken@ubuntu:~$
>
ken@ubuntu:~$ cat /proc/asound/cards; sudo aptitude install gnome-alsamixer
 0 [SB ]: HDA-Intel - HDA ATI SB
                      HDA ATI SB at 0x92500000 irq 16
 1 [HDMI ]: HDA-Intel - HDA ATI HDMI
                      HDA ATI HDMI at 0x92410000 irq 19
[sudo] password for ken:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Writing extended state information... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done

ken@ubuntu:~$

 Still no sound on HP DV4 1220 US Laptop Tried all Red light on laptop still
red. I've read in forums this model HP is very troublesome.
Thanks, Ken

>
>
>
>
>

Hi
 Tried all the fixes and none worked . Still have that accursed red lite on machine. What Alsa setting should I be using
in Systems>Preferences>Sound?
Thanks, Ken

You should set the Systems>Preferences>Sound settings to Intel HDA (ALSA) or something with ALSA in the name.

You can also try upgrading ALSA to the newest version, reboot and retest sound.

ALSA upgrade procedure is here:

http://monespaceperso.org/blog-en/2009/05/09/upgrade-alsa-1020-on-ubuntu-jaunty-904/

Did you make sure to reboot after every change you made to the /etc/modprobe.d/alsa-base.conf file?

For example, if you change the model option from dell-m4-1 to dell-m4-2, you need to reboot and retest sound.

It is very strange that my procedure did not solve your issue, because it helps everyone else who has a pc with the IDT 92HD71B7X codec. Your pc also uses the IDT 92HD71B7X audio codec.

See all the solved issues here:

https://answers.launchpad.net/~markrijckenberg/+questions?field.search_text=92HD71B7X&field.sort=NEWEST_FIRST&field.sort-empty-marker=1&field.actions.search=Search&field.language=en&field.language-empty-marker=1&field.status=OPEN&field.status=NEEDSINFO&field.status=ANSWERED&field.status=SOLVED&field.status-empty-marker=1

Maybe you should simply reinstall Ubuntu 9.04 32-bit desktop edition from scratch and then retry my procedure again.

On Tue, Aug 11, 2009 at 5:37 PM, Mark Rijckenberg <
<email address hidden>> wrote:

> Your question #79688 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/79688
>
> Status: Open => Answered
>
> Mark Rijckenberg proposed the following answer:
> You should set the Systems>Preferences>Sound settings to Intel HDA
> (ALSA) or something with ALSA in the name.
>
> You can also try upgrading ALSA to the newest version, reboot and retest
> sound.
>
> ALSA upgrade procedure is here:
>
> http://monespaceperso.org/blog-en/2009/05/09/upgrade-alsa-1020-on-
> ubuntu-jaunty-904/<http://monespaceperso.org/blog-en/2009/05/09/upgrade-alsa-1020-on-%0Aubuntu-jaunty-904/>
>
> Did you make sure to reboot after every change you made to the
> /etc/modprobe.d/alsa-base.conf file?
>
> For example, if you change the model option from dell-m4-1 to dell-m4-2,
> you need to reboot and retest sound.
>
> It is very strange that my procedure did not solve your issue, because
> it helps everyone else who has a pc with the IDT 92HD71B7X codec. Your
> pc also uses the IDT 92HD71B7X audio codec.
>
> See all the solved issues here:
>
>
> https://answers.launchpad.net/~markrijckenberg/+questions?field.search_text=92HD71B7X&field.sort=NEWEST_FIRST&field
> .sort-empty-marker=1&field.actions.search=Search&field.language=en&field
> .language-empty-
>
> marker=1&field.status=OPEN&field.status=NEEDSINFO&field.status=ANSWERED&field.status=SOLVED&field
> .status-empty-marker=1<https://answers.launchpad.net/%7Emarkrijckenberg/+questions?field.search_text=92HD71B7X&field.sort=NEWEST_FIRST&field%0A.sort-empty-marker=1&field.actions.search=Search&field.language=en&field%0A.language-empty-%0Amarker=1&field.status=OPEN&field.status=NEEDSINFO&field.status=ANSWERED&field.status=SOLVED&field%0A.status-empty-marker=1>
>
>
> Maybe you should simply reinstall Ubuntu 9.04 32-bit desktop edition from
> scratch and then retry my procedure again.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/ubuntu/+question/79688/+confirm?answer_id=6
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+question/79688
>
> You received this question notification because you are a direct
> subscriber of the question.
>
Hi
I did all those things the way you suggested re-booted each time and alsa
sttings were all correct. Nothing happened-probably did something wrong but
not sure what. Could the problem be the lap top itself?
Thanks for your help,
Ken

Hi again Mark,
Tried one more time and would like to know if this is what I should see in terminal for last command.
ken@ubuntu:~$ gksudo gedit /etc/modprobe.d/alsa-base.conf
ken@ubuntu:~$ # Keep snd-pcsp from being loaded as first soundcard
ken@ubuntu:~$ options snd-pcsp index=-2
bash: options: command not found
ken@ubuntu:~$ alias snd-card-0 snd-hda-intel
bash: alias: snd-card-0: not found
bash: alias: snd-hda-intel: not found
ken@ubuntu:~$ alias sound-slot-0 snd-hda-intel
bash: alias: sound-slot-0: not found
bash: alias: snd-hda-intel: not found
ken@ubuntu:~$ options snd-hda-intel model=dell-m4-1
bash: options: command not found
ken@ubuntu:~$ options snd-hda-intel enable_msi=1

I did other ones for dell too and re-booted and all sound were on alsa.Need to know if I made a mistake.
Thanks, Ken

No that is not correct.

When you run the command

gksudo gedit /etc/modprobe.d/alsa-base.conf

Ubuntu should be opening the file alsa-base.conf using the text editor called gedit

Using the gedit editor, you need to add the following lines at the end of the alsa-base.conf file (which you just opened using gedit):

# Keep snd-pcsp from being loaded as first soundcard
options snd-pcsp index=-2
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
options snd-hda-intel model=hp-dv5
options snd-hda-intel enable_msi=1

If that does not work, you need to replace the line

options snd-hda-intel model=hp-dv5

with

options snd-hda-intel model=dell-m4-1

and reboot and retest sound.

Same procedure for testing the other model options.

Hi Mark-sorry to be so much trouble. (Newbie)
I redid the procedure in alsa-base.conf and rebooted with everyone of the options (including dell).In preferences tried every Alsa setting.Sound lite on computer stays red. Question- just put the line changes in gedit and I just reboot without doing anything else? Sorry to be rambling.

# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7

# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-ioctl32 ; /sbin/modprobe --quiet --use-blacklist snd-seq ; }
#
# Workaround at bug #499695 (reverted in Ubuntu see LP #319505)
install snd-pcm /sbin/modprobe --ignore-install snd-pcm $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-pcm-oss ; : ; }
install snd-mixer /sbin/modprobe --ignore-install snd-mixer $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-mixer-oss ; : ; }
install snd-seq /sbin/modprobe --ignore-install snd-seq $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ; /sbin/modprobe --quiet --use-blacklist snd-seq-oss ; : ; }
#
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ; : ; }
# Cause optional modules to be loaded above sound card driver modules
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-emu10k1-synth ; }
install snd-via82xx /sbin/modprobe --ignore-install snd-via82xx $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq ; }

# Load saa7134-alsa instead of saa7134 (which gets dragged in by it anyway)
install saa7134 /sbin/modprobe --ignore-install saa7134 $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist saa7134-alsa ; : ; }
# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options saa7134-alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
options snd-usb-audio index=-2
options snd-usb-us122l index=-2
options snd-usb-usx2y index=-2
options snd-usb-caiaq index=-2
# Ubuntu #62691, enable MPU for snd-cmipci
options snd-cmipci mpu_port=0x330 fm_port=0x388
# Keep snd-pcsp from beeing loaded as first soundcard
options snd-pcsp index=-2
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
options snd-hda-intel model=hp-dv5
options snd-hda-intel enable_msi=1

If what I did was correct none worked.
Thanks for all your time and trouble, Ken

Hi Ken,

Did you make sure to first set all channels to high volume levels in gnome-alsamixer, before changing the settings in /etc/modprobe.d/alsa-base.conf ?

Did you make sure all the different speakers (including 'Front', 'Master', and 'PCM") are NOT muted and NOT set to low volume levels in gnome-alsamixer?

These are the first things I asked you to check, if you reread my very first remarks on this thread.

Did you do that first?

In particular, make sure the 'Master' volume is NOT muted in gnome-alsamixer

Check if you hear sound through both the speakers and headphones.

I cannot give you any more tips than that.

Good luck,

Regards,

Mark

On Wed, Aug 12, 2009 at 6:10 PM, Mark Rijckenberg <
<email address hidden>> wrote:

> Your question #79688 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/79688
>
> Status: Open => Needs information
>
> Mark Rijckenberg requested for more information:
> Hi Ken,
>
> Did you make sure to first set all channels to high volume levels in
> gnome-alsamixer, before changing the settings in /etc/modprobe.d/alsa-
> base.conf ?
>
> Did you make sure all the different speakers (including 'Front',
> 'Master', and 'PCM") are NOT muted and NOT set to low volume levels in
> gnome-alsamixer?
>
> These are the first things I asked you to check, if you reread my very
> first remarks on this thread.
>
> Did you do that first?
>
> In particular, make sure the 'Master' volume is NOT muted in gnome-
> alsamixer
>
> Check if you hear sound through both the speakers and headphones.
>
> I cannot give you any more tips than that.
>
> Good luck,
>
> Regards,
>
> Mark
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+question/79688
>
> You received this question notification because you are a direct
> subscriber of the question.
>
Hi Mark,
Installed 32 bit Ubuntu and fixes worked except only sound on external
speakers. Good enough.
Regards,
Ken

Hi Ken,

I am happy for you that my suggested solution from August 11 solves your sound issue.

If the sound issue is still resolved, can you please set this thread to status "solved"?

Regards,

Mark

Mark,
Problem solved.
Thanks, Ken

Solved
Thanks,
Ken

On Tue, Aug 18, 2009 at 4:18 PM, marcobra (Marco Braida) <
<email address hidden>> wrote:

> Your question #79688 on alsa-driver in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/79688
>
> Project: Ubuntu => alsa-driver in ubuntu
>
> --
> You received this question notification because you are a direct
> subscriber of the question.
>