PCI/internal sound card not detected

Bug #989955 reported by Charlie Sager
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
alsa-utils (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Sound was working. After update, no sound card detected, and no sound.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: fglrx
AlsaDevices:
 total 0
 crw-rw---T 1 root audio 116, 1 Apr 27 03:25 seq
 crw-rw---T 1 root audio 116, 33 Apr 27 03:25 timer
AplayDevices: aplay: device_list:252: no soundcards found...
ApportVersion: 2.0.1-0ubuntu6
Architecture: amd64
ArecordDevices: arecord: device_list:252: no soundcards found...
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Fri Apr 27 10:30:51 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120325)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/21/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0803
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5E3 Premium
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 2.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd05/21/2009:svnSystemmanufacturer:pnP5E3Premium:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5E3Premium:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5E3 Premium
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Charlie Sager (charsager) wrote :
Revision history for this message
Daniel Letzeisen (dtl131) wrote :

Changing to alsa-utils since the issue in with alsa-restore init.

> From bootdmesg:
[ 29.478143] init: alsa-restore main process (1360) terminated with status 19

Try running sudo service alsa-restore restart manually and see if your card shows with aplay -l command. If it does, restart pulseaudio and sound should be working properly.

affects: alsa-driver (Ubuntu) → alsa-utils (Ubuntu)
Changed in alsa-utils (Ubuntu):
status: New → Confirmed
Revision history for this message
Charlie Sager (charsager) wrote : Re: [Bug 989955] Re: PCI/internal sound card not detected

On 04/27/2012 12:44 PM, Dave Lentz wrote:
> Changing to alsa-utils since the issue in with alsa-restore init.
>
>> From bootdmesg:
> [ 29.478143] init: alsa-restore main process (1360) terminated with status 19
>
> Try running sudo service alsa-restore restart manually and see if your
> card shows with aplay -l command. If it does, restart pulseaudio and
> sound should be working properly.
>
>
> ** Package changed: alsa-driver (Ubuntu) => alsa-utils (Ubuntu)
>
> ** Changed in: alsa-utils (Ubuntu)
> Status: New => Confirmed
>
Dave,

After about 8 hours of fiddling with this, I found out what my problem
is. I had added to update manager software sources,
ppa.launchpad.net/ubuntu-audio-dev/alsa-daily/ubuntu . This puts
alsa-hda-dkms as a package to update in update manager. One of the
drivers in there was causing my problem(that is, in system settings for
sound, output was "dummy-output", and I could not perform a speaker
test). When I restored from backup, and took the ppa out, the rest of
the updates were successful, and I still had my sound. I'm now on the
latest kernel, 3.2.0-24 .

I guess this bug #989955 can be forwarded to the alsa-dev team.
Wouldn't want this to show up on some future update. On another
computer, I still have another sound bug #980070 that has a work-around,
I just unplug/plug back in the HDMI cable, athough this is rather
annoying, as Ubuntu 11.10 worked just fine.
Thanks

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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