[Realtek ALC268] ALSA test tone not correctly played back
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
alsa-driver (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I just updated my system and after reboot no sound running alsamixer from terminal gives
ALSA lib conf.c:
ALSA lib control.
cannot open mixer: No such file or directory
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
ALSA lib conf.c:
ALSA lib control.
aplay: device_list:232: control open (0): No such file or directory
**** List of PLAYBACK Hardware Devices ****
Architecture: i386
ArecordDevices:
ALSA lib conf.c:
ALSA lib control.
arecord: device_list:232: control open (0): No such file or directory
**** List of CAPTURE Hardware Devices ****
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
Card0.Amixer.info:
Error: command ['amixer', '-c', '0', 'info'] failed with exit code 1: ALSA lib conf.c:
ALSA lib control.
amixer: Control device hw:0 open error: No such file or directory
Card0.Amixer.
Error: command ['amixer', '-c', '0'] failed with exit code 1: ALSA lib conf.c:
ALSA lib control.
amixer: Mixer attach hw:0 error: No such file or directory
Date: Thu Feb 18 15:19:45 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Alpha i386 (20100210)
Package: alsa-base 1.0.22.
PackageArchitec
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SelectedCard: 0 Intel HDA-Intel - HDA Intel
SourcePackage: alsa-driver
SpeakerTestAlsa
A L S A l i b c o n f . c : 3 2 7 2 : ( s n d _ c o n f i g _ h o o k s _ c a l l ) C a n n o t o p e n s h a r e d l i b r a r y l i b a s o u n d _ m o d u l e _ c o n f _ p u l s e . s o
A L S A l i b p c m . c : 2 2 1 1 : ( s n d _ p c m _ o p e n _ n o u p d a t e ) U n k n o w n P C M p l u g h w : 0
Symptom: audio
Title: [Realtek ALC268] ALSA test tone not correctly played back
Uname: Linux 2.6.32-13-generic i686
amixerStderr:
A L S A l i b c o n f . c : 3 2 7 2 : ( s n d _ c o n f i g _ h o o k s _ c a l l ) C a n n o t o p e n s h a r e d l i b r a r y l i b a s o u n d _ m o d u l e _ c o n f _ p u l s e . s o
A L S A l i b c o n t r o l . c : 9 0 2 : ( s n d _ c t l _ o p e n _ n o u p d a t e ) I n v a l i d C T L h w : 0
a m i x e r : M i x e r a t t a c h h w : 0 e r r o r : N o s u c h f i l e o r d i r e c t o r y
Same issue here, using completely different audio hardware. This happened after this morning's PA upgrade push in Lucid,