Ubuntu
alsa-driver package

[HDA-Intel - HDA Creative, playback (Creative Recon3D PCIE)] No sound at all

Bug #1165889 reported by Michael Murphy on 2013-04-07

This bug report is a duplicate of: Bug #1166529: Creative Recon3d & Sound Blaster Z (CA0132), No sound at all. Edit Remove

This bug affects 1 person

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

Bug Description

Quite simply, no sound from a fresh install of Ubuntu 13.04 with a recon3D sound card.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
Uname: Linux 3.8.0-16-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Sun Apr 7 16:30:33 2013
InstallationDate: Installed on 2013-04-07 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
Symptom_Card: HDA Creative - HDA Creative
Symptom_Type: No sound at all
Title: [HDA-Intel - HDA Creative, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1102
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH 990FX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

Tags:

Revision history for this message

Michael Murphy (mmstick) wrote on 2013-04-07:

AlsaInfo.txt Edit (48.5 KiB, text/plain; charset="utf-8")
AudioDevicesInUse.txt Edit (299 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (70.5 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (15.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.9 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (22.6 KiB, text/plain; charset="utf-8")
Symptom_DevicesInUse.txt Edit (299 bytes, text/plain; charset="utf-8")

Revision history for this message

Marc Bourgoin (jagged-jimmy-j) wrote on 2013-06-05:

Heyyo,

I've experienced mixed success with getting the audio to work when it was static at first doing the fix_position 1 in the rc.local file... but I'm not sure if it was a recent System Update, but now I have no sound yet again. :(

running 13.04 as well on kernel 3.9.4. It worked for a while on 3.9 RC8 but after a few reboots and maybe disabling my onboard sound messed it up...

Revision history for this message

Marc Bourgoin (jagged-jimmy-j) wrote on 2013-06-15:

Heyyo,

I get sound with my SoundBlaster Recon 3d Fatal1ty Professional when I use any version of the 32bit kernel (3.8.x and 3.9.4 thoroughly tested)on any version of Linux (Ubuntu, Xubuntu, Kubuntu... can't install Fedora for some reason though... just hangs) where-as 64bit works only if I modify the rc.local file with the fix_position... and that's not even a guarantee. There's definitely a bug in the 64bit Kernel.