Ubuntu
alsa-driver package

[ALC888 - HDA Intel] ALSA test tone not correctly played back

Bug #667590 reported by Brad Gulliford on 2010-10-28

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	alsa-driver (Ubuntu)	Expired	Undecided	Unassigned

Bug Description

System has been totally mute since running upgrade manager (to 10,04 LTR Lucid), except for initial beep from BIOS (if I open that after booting). Have run system checks. Speakers plugged in & turned on, volume (in software) set well above 0. No alert/warning beeps, startup theme, sound from movie player Totem 2.30.2. Have tried various upgrades & tests suggested here on Launchpad. Also did a fresh reinstall. Anything else I should check?

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic i686
AlsaVersion:
Advanced Linux Sound Architecture Driver Version 1.0.23.
Compiled on Sep 27 2010 for kernel 2.6.32-25-generic (SMP).
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: helen 1182 F.... pulseaudio
                      helen 1891 F.... alsamixer
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfdff4000 irq 28'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,1028020d,00100001'
   Controls : 40
   Simple ctrls : 22
Date: Wed Oct 27 22:11:29 2010
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SelectedCard: 0 Intel HDA-Intel - HDA Intel
SourcePackage: alsa-driver
Symptom: audio
Title: [HDA-Intel - HDA Intel] ALSA test tone not correctly played back
dmi.bios.date: 03/20/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.13
dmi.board.name: 0RY007
dmi.board.vendor: Dell Inc.
dmi.board.version: ��
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: OEM
dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd03/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0RY007:rvr:cvnDellInc.:ct3:cvrOEM:
dmi.product.name: Inspiron 530
dmi.sys.vendor: Dell Inc.

Tags:

Revision history for this message

Brad Gulliford (bxg) wrote on 2010-10-28:

AlsaDevices.txt Edit (587 bytes, text/plain; charset="utf-8")
AplayDevices.txt Edit (273 bytes, text/plain; charset="utf-8")
ArecordDevices.txt Edit (386 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (41.2 KiB, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (4.4 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.2.txt Edit (13.2 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (975 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
PciMultimedia.txt Edit (586 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")

David Henningsson (diwic) on 2010-10-28

summary:

- [HDA-Intel - HDA Intel] ALSA test tone not correctly played back
+ [ALC888 - HDA Intel] ALSA test tone not correctly played back

Revision history for this message

David Henningsson (diwic) wrote on 2010-10-28:

Hi Brad,
In what version was sound working for you?
Also, the first thing to try here is the latest snapshot according to https://wiki.ubuntu.com/Audio/InstallingLinuxAlsaDriverModules
- can you do that and report back? Thanks!

Revision history for this message

Brad Gulliford (bxg) wrote on 2010-10-29: Re: [Bug 667590] Re: [ALC888 - HDA Intel] ALSA test tone not correctly played back

> In what version was sound working for you?
>
Sorry, after the fresh reinstall I developed a case of amnesia. :-{)}
It would have been whatever came with the Hardy LTR (which, come to
think of it, was an in-place upgrade from Gutsy).

> Also, the first thing to try here is the latest snapshot according to https://wiki.ubuntu.com/Audio/InstallingLinuxAlsaDriverModules
> - can you do that and report back? Thanks!
>

The add-apt-repository ppa resulted in:

Executing: gpg --ignore-time-conflict --no-options --no-default-keyring
--secret-keyring /etc/apt/secring.gpg --trustdb-name
/etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring
/etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv
4E9F485BF943EF0EABA10B5BD225991A72B194E5
gpg: requesting key 72B194E5 from hkp server keyserver.ubuntu.com
gpg: key 72B194E5: "Launchpad Ubuntu Audio Dev team PPA" not changed
gpg: Total number processed: 1
gpg: unchanged: 1

I went ahead anyway and tried the apt-get install and got:

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
   linux-backports-modules-alsa-2.6.32-25-generic
   linux-backports-modules-alsa-lucid-generic
The following NEW packages will be installed:
   linux-alsa-driver-modules-2.6.32-25-generic
0 upgraded, 1 newly installed, 2 to remove and 0 not upgraded.
Need to get 2,126kB of archives.

I agreed to getting those archives, and things seemed to run their course.

Rebooted and still had no sound.

Then I proceeded to install again using the package manager, figuring
the package manager would be intelligent enough to overwrite and not
install a second instance. Synaptic went about its task without
objection; I rebooted; still no sound.

So could I have done something to result in a successful PPA change? I
hope I'm not interfering with anything by attempting to do stuff more
than once.

I do appreciate your help, and look forward to your response.

--Brad

> In what version was sound working for you?
>    
Sorry, after the fresh reinstall I developed a case of amnesia.  :-{)}  
It would have been whatever came with the Hardy LTR (which, come to 
think of it, was an in-place upgrade from Gutsy).

> Also, the first thing to try here is the latest snapshot according to https://wiki.ubuntu.com/Audio/InstallingLinuxAlsaDriverModules
> - can you do that and report back? Thanks!
>

The add-apt-repository ppa resulted in:

Executing: gpg --ignore-time-conflict --no-options --no-default-keyring 
--secret-keyring /etc/apt/secring.gpg --trustdb-name 
/etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring 
/etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv 
4E9F485BF943EF0EABA10B5BD225991A72B194E5
gpg: requesting key 72B194E5 from hkp server keyserver.ubuntu.com
gpg: key 72B194E5: "Launchpad Ubuntu Audio Dev team PPA" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

I went ahead anyway and tried the apt-get install and got:

I agreed to getting those archives, and things seemed to run their course.

Rebooted and still had no sound.

Then I proceeded to install again using the package manager, figuring 
the package manager would be intelligent enough to overwrite and not 
install a second instance.  Synaptic went about its task without 
objection; I rebooted; still no sound.

So could I have done something to result in a successful PPA change?  I 
hope I'm not interfering with anything by attempting to do stuff more 
than once.

I do appreciate your help, and look forward to your response.

--Brad

Revision history for this message

Daniel T Chen (crimsun) wrote on 2010-10-29:

Please use `apport-collect 667590' while using the ppa sound drivers.

Revision history for this message

Brad Gulliford (bxg) wrote on 2010-10-29:

Sorry, I've never used apport-collect before. I'm getting a > prompt
and nothing happening when I enter commands.

Could you please type out exactly what I should enter at the regular
shell prompt (i.e., what I get when I open a terminal session).

> Please use `apport-collect 667590' while using the ppa sound drivers.
>
>

Revision history for this message

Daniel T Chen (crimsun) wrote on 2010-10-29:

The backtick and quotation mark are used to denote a command, so just
enter what's between them.

Revision history for this message

Brad Gulliford (bxg) wrote on 2010-11-03:

[Sorry it's been a while; I've been busy with other stuff.]

On 10/28/2010 10:58 PM, Daniel T Chen wrote:
> Please use `apport-collect 667590' while using the ppa sound drivers.
>
>
Activated apport-collect 667590; got the following (helen is my home
login/computer's name):

helen@helen-desktop:~$ sudo add-apt-repository ppa:ubuntu-audio-dev/ppa
[sudo] password for helen:
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring
--secret-keyring /etc/apt/secring.gpg --trustdb-name
/etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring
/etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv
4E9F485BF943EF0EABA10B5BD225991A72B194E5
gpg: requesting key 72B194E5 from hkp server keyserver.ubuntu.com
gpg: key 72B194E5: "Launchpad Ubuntu Audio Dev team PPA" not changed
gpg: Total number processed: 1
gpg: unchanged: 1

------------
So if I've neglected a setting or something (computer has been without
sound since in-place upgrade), TIA & I look forward to hearing from you.

--Brad

Revision history for this message

Brad Gulliford (bxg) wrote on 2010-11-12:

Hi, sorry to bother, but was wondering if there's anything else I can
do. I'm still stuck out here. Thanks.

On 11/02/2010 10:46 PM, Brad Gulliford wrote:
> [Sorry it's been a while; I've been busy with other stuff.]
>
> On 10/28/2010 10:58 PM, Daniel T Chen wrote:
>
>> Please use `apport-collect 667590' while using the ppa sound drivers.
>>
>>
>>
> Activated apport-collect 667590; got the following (helen is my home
> login/computer's name):
>
> helen@helen-desktop:~$ sudo add-apt-repository ppa:ubuntu-audio-dev/ppa
> [sudo] password for helen:
> Executing: gpg --ignore-time-conflict --no-options --no-default-keyring
> --secret-keyring /etc/apt/secring.gpg --trustdb-name
> /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring
> /etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv
> 4E9F485BF943EF0EABA10B5BD225991A72B194E5
> gpg: requesting key 72B194E5 from hkp server keyserver.ubuntu.com
> gpg: key 72B194E5: "Launchpad Ubuntu Audio Dev team PPA" not changed
> gpg: Total number processed: 1
> gpg: unchanged: 1
>
> ------------
> So if I've neglected a setting or something (computer has been without
> sound since in-place upgrade), TIA& I look forward to hearing from you.
>
> --Brad
>
>

Revision history for this message

David Henningsson (diwic) wrote on 2010-11-12:

To make sure we analyze the right thing, please attach an alsa-info according to: https://wiki.ubuntu.com/Audio/AlsaInfo - and to that while the https://wiki.ubuntu.com/Audio/InstallingLinuxAlsaDriverModules are installed. Thanks!

Revision history for this message

Brad Gulliford (bxg) wrote on 2010-11-13:

#10

alsa-info.txt.7bqiqCJjA1 Edit (74.0 KiB, text/plain; name="alsa-info.txt.7bqiqCJjA1")

OK, installed alsa-driver-modules, then ran AlsaInfo and that file is
attached.

If I misunderstood the sequence, let me know. Even after reinstalling
(there were some already there of course; I let Synaptic package manager
sort it out) alsa, still get no sound after BIOS beep, FYI.

Looking forward to next step. :-{)}

--Brad

On 11/12/2010 06:32 AM, David Henningsson wrote:
> To make sure we analyze the right thing, please attach an alsa-info
> according to: https://wiki.ubuntu.com/Audio/AlsaInfo - and to that while
> the https://wiki.ubuntu.com/Audio/InstallingLinuxAlsaDriverModules are
> installed. Thanks!
>
>

Revision history for this message

David Henningsson (diwic) wrote on 2010-11-15:

#11

Ok, I have two ideas:

1) Keep alsa-driver-modules installed, then try model=auto by inserting the line
options snd-hda-intel model=auto
...into /etc/modprobe.d/alsa-base.conf
Reboot and try.

2) An invalid SKU, try by uninstalling alsa-driver-modules, then install http://people.canonical.com/~diwic/temp/alsa-hda-realtek-ignore-sku-dkms_1.0.23.diwic_all.deb and reboot.

Revision history for this message

David Henningsson (diwic) wrote on 2010-11-15:

#12

Could you also specify whether you have a problem with headphones, line-out, or both? (I assume this is a desktop machine and you don't expect the internal speakers, if any, to be working.)

Revision history for this message

Brad Gulliford (bxg) wrote on 2010-11-16:

#13

Tried both (in order; uninstalled alsa-driver-modules with Synaptic,
then clicked on the .deb URL to install); still nothing.

Yes, this is a Dell desktop; problem is with both line-out and
headphones. My sound was fine until the upgrade; hadn't changed a thing
in my cables/jacks/connections.

> Ok, I have two ideas:
>
> 1) Keep alsa-driver-modules installed, then try model=auto by inserting the line
> options snd-hda-intel model=auto
> ...into /etc/modprobe.d/alsa-base.conf
> Reboot and try.
>
> 2) An invalid SKU, try by uninstalling alsa-driver-modules, then install
> http://people.canonical.com/~diwic/temp/alsa-hda-realtek-ignore-sku-
> dkms_1.0.23.diwic_all.deb and reboot.
>
>

Revision history for this message

David Henningsson (diwic) wrote on 2010-11-16:

#14

Ok, seems like we have tried the easy paths then...would it possible for you to do the following:
* Start your system from a Karmic live-CD and verify that sound is working (or the latest version that it was working on)
and from that system, attach an alsa-info: https://wiki.ubuntu.com/Audio/AlsaInfo

The idea is to compare that alsa-info to the current codec and see if there's any difference.

Revision history for this message

Brad Gulliford (bxg) wrote on 2010-11-17:

#15

<groan> OK, it'll take a few days while I do some real-world stuff
(unrelated to the computer). I appreciate your staying with this & I'll
get back to you as soon as I can download & burn a disk (maybe as late
as next week).

> Ok, seems like we have tried the easy paths then...would it possible for you to do the following:
> * Start your system from a Karmic live-CD and verify that sound is working (or the latest version that it was working on)
> and from that system, attach an alsa-info: https://wiki.ubuntu.com/Audio/AlsaInfo
>
> The idea is to compare that alsa-info to the current codec and see if
> there's any difference.
>
>

Revision history for this message

Brad Gulliford (bxg) wrote on 2010-11-23:

#16

alsa-info.txt.bHgTtz9137 Edit (27.4 KiB, text/plain; name="alsa-info.txt.bHgTtz9137")

(Back again from last week--thank you for your patience.) Last time
sound worked was with Hardy 8.04 LTR. I just LiveCD'd Hardy again (am
currently running Lucid 10.04 LTS), BUT sound didn't work with the
LiveCD of 8.04 either. Movie Player said it lacked MP3 & DivX
decoders. (It does not say that in Movie Player from my Lucid, just the
LiveCD.) Am attaching the alsa-info from that LiveCD session.

> Ok, seems like we have tried the easy paths then...would it possible for you to do the following:
> * Start your system from a Karmic live-CD and verify that sound is working (or the latest version that it was working on)
> and from that system, attach an alsa-info:https://wiki.ubuntu.com/Audio/AlsaInfo
>
> The idea is to compare that alsa-info to the current codec and see if
> there's any difference.
>
>

Revision history for this message

Daniel T Chen (crimsun) wrote on 2010-11-23:

#17

Note how the following mixer controls are muted and zeroed:

Simple mixer control 'Surround',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 0 [0%] [-46.50dB] [off] <---
  Front Right: Playback 0 [0%] [-46.50dB] [off] <---
Simple mixer control 'Center',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback 0 - 31
  Mono: Playback 0 [0%] [-46.50dB] [off] <---
Simple mixer control 'LFE',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback 0 - 31
  Mono: Playback 0 [0%] [-46.50dB] [off] <---
Simple mixer control 'Side',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 0 [0%] [-46.50dB] [off] <---
  Front Right: Playback 0 [0%] [-46.50dB] [off] <---
Simple mixer control 'Line',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 0 [0%] [-34.50dB] [off] <---
  Front Right: Playback 0 [0%] [-34.50dB] [off] <---

Revision history for this message

Brad Gulliford (bxg) wrote on 2010-11-23:

#18

alsa-info.txt.GERqolldlV Edit (62.3 KiB, text/plain; name="alsa-info.txt.GERqolldlV")

OK, went into alsa-mixer and (think I) changed the settings. Attached
is new alsa-info. Still no sound. Used a help file within Ubuntu or
alsa. Did I not make the changes correctly, or forget to save it, or
something?

> Note how the following mixer controls are muted and zeroed:
>
> Simple mixer control 'Surround',0
> Capabilities: pvolume pswitch
> Playback channels: Front Left - Front Right
> Limits: Playback 0 - 31
> Mono:
> Front Left: Playback 0 [0%] [-46.50dB] [off]<---
> Front Right: Playback 0 [0%] [-46.50dB] [off]<---
> Simple mixer control 'Center',0
> Capabilities: pvolume pvolume-joined pswitch pswitch-joined
> Playback channels: Mono
> Limits: Playback 0 - 31
> Mono: Playback 0 [0%] [-46.50dB] [off]<---
> Simple mixer control 'LFE',0
> Capabilities: pvolume pvolume-joined pswitch pswitch-joined
> Playback channels: Mono
> Limits: Playback 0 - 31
> Mono: Playback 0 [0%] [-46.50dB] [off]<---
> Simple mixer control 'Side',0
> Capabilities: pvolume pswitch
> Playback channels: Front Left - Front Right
> Limits: Playback 0 - 31
> Mono:
> Front Left: Playback 0 [0%] [-46.50dB] [off]<---
> Front Right: Playback 0 [0%] [-46.50dB] [off]<---
> Simple mixer control 'Line',0
> Capabilities: pvolume pswitch
> Playback channels: Front Left - Front Right
> Limits: Playback 0 - 31
> Mono:
> Front Left: Playback 0 [0%] [-34.50dB] [off]<---
> Front Right: Playback 0 [0%] [-34.50dB] [off]<---
>
>

Revision history for this message

Marcus Tomlinson (marcustomlinson) wrote on 2020-03-05:

#19

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in alsa-driver (Ubuntu):
status:	New → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2020-05-05:

#20

[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.]

Changed in alsa-driver (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntualsa-driver package

[ALC888 - HDA Intel] ALSA test tone not correctly played back

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
alsa-driver package