[1015PEM, Realtek ALC269VB, Green Headphone Out, Right] No sound at all. Sound does come out of speakers, as if headphones were not inserted.

Bug #779307 reported by Ralf Futselaar
40
This bug affects 6 people
Affects Status Importance Assigned to Milestone
alsa-driver (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Brand new eee pc 1015 pem, works all fine and dandy under Natty. However, headphone out is somehow not recognised. Even when a headphone is inserted, sound continues to come out of the built-in speakers. Headphones remain silent.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: alsa-base 1.0.24+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ralf 2223 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7cf8000 irq 46'
   Mixer name : 'Realtek ALC269VB'
   Components : 'HDA:10ec0269,104383ce,00100100'
   Controls : 12
   Simple ctrls : 7
Date: Sun May 8 10:40:35 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Internal Audio - HDA Intel
Symptom_DevicesInUse: 2223
Symptom_Jack: Green Headphone Out, Right
Symptom_Type: No sound at all
Title: [1015PEM, Realtek ALC269VB, Green Headphone Out, Right] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/18/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1101
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1015PE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd02/18/2011:svnASUSTeKComputerINC.:pn1015PEM:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1015PEM
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

Revision history for this message
Ralf Futselaar (ralf-futselaar) wrote :
Revision history for this message
Luke Yelavich (themuso) wrote :

Thanks for your bug report. I have an idea for a possible fix to this bug, however I need to prepare a package with the fix included for you to test. I will get back to you with more information as soon as I have a package ready.

Thanks again.

Changed in alsa-driver (Ubuntu):
assignee: nobody → Luke Yelavich (themuso)
status: New → Confirmed
Revision history for this message
blurry (brendan-robert) wrote :

Confirmed also happening on Toshiba Satellite M640 with the same sound chipset. Jack audio programs pointing to the ALSA driver do not work for headphones but will for analog speakers, but only if sound out is set to speakers and headphones are unplugged. If sound out is set to analog output (which should be for speakers or for headphones), sound does not come out of speakers with headphones unplugged.

Revision history for this message
Logan Weiler III (loganweileriii) wrote :

Also happening on Toshiba Satellite L655D.

Revision history for this message
Marciano (paulomarciano) wrote :

I can confirm it as happening on my desktop. Soundboard is onboard VIA

Revision history for this message
Mel (mellowiz) wrote :

Same here (ASUS X52D, ALC269VB Analog). What's weird is that I'm sure speakers were working while using the boot CD.
After installation the sound disappeared.

Revision history for this message
Mel (mellowiz) wrote :

Sound gets right back when resuming from standby (see #4 @ bug 697498).
#779307 and #697498 might be the same bug.

Revision history for this message
Logan Weiler III (loganweileriii) wrote :

Thanks for the heads up Mello. Unfortunately, resuming from standby or hibernation doesn't improve the audio problem on my Toshiba. Bug 697498 appears to be different issue.

Revision history for this message
blurry (brendan-robert) wrote :

@Logan: Me either. (Actually, in my case the rtl8192ce and rtlwifi drivers have to be reloaded sometimes to fix a wireless bug) I poked around some more and I don't have the issue with pulse audio, but I do have it with Jack (and possibly ALSA). Since the main apps I use (browser, banshee) are pulse audio friendly, it's usually OK. However, audio apps all tend to use Jack and simply just don't work with headphones.

For what it's worth, I set my local ~/.asoundrc to this:

pcm.!default {
   type pulse
}
## Not mandatory
ctl.!default {
   type pulse
}

in hopes of directing alsa apps to use the pulse audio server. Is this redundant?

Revision history for this message
Logan Weiler III (loganweileriii) wrote :

@blurry: Sounds like a great solution, but it's way over my head. I don't have a clue where to put any of that code in. I also had the wireless bug you mentioned, but upgrading to 11.04 fixed it. I traded one bug for another.

@Luke Yelavich: As Leslie Neilson said in Airplane, "Good luck. We're all counting on you."

Revision history for this message
blurry (brendan-robert) wrote :

@Logan: create a new file in your home folder and save it as ".asoundrc", then paste the stuff above into it. Save the file, and restart (or logout/login should probably also work). Test to see if sound works any differently in any program you may have had an issue with. Also, if applicable as it is in my case, if pulse works but other things like alsa do not, you can use the pulse audio wrapper (padsp) if the affected program can use OSS. This is EXTREMELY useful with Wine. more info here: http://linux.die.net/man/1/padsp

Revision history for this message
G Gajoch (gajoch) wrote :

Has anyone solved that?
I have 1015PEM too, and the same problem...
I tried to fix thast all day and nothing. I tried this script and also nothing...

But, on other instance of linux (on Debian) i had the same issue, but it solved automatically (after login to windows), but now it hasn't worked... I don't have any idea left.

Revision history for this message
blurry (brendan-robert) wrote :

Grrr... Thought that I was in the clear but I have the same problem with ReNoise using the ALSA driver. Somehow PulseAudio is more immune to this. Any leads on this folks?

Revision history for this message
Kay A.Serenade (wind-summoner) wrote :

Same thing under by Asus X23F notebook. It's using the same device:
aplay -l

**** List of PLAYBACK Hardware Devices ****
xcb_connection_has_error() returned true
card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
----------------------------------------------------------------------------
lspci | grep Audio
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
----------------------------------------------------------------------------

I get sound from the internal speaker, but no sound from headphones and both internal and external mic won't work. Tried installing driver from Realtek but no go. The list of supporting driver from Realtek indicates ALC269 but doesn't seem to support ALC269VB.

Revision history for this message
Martin Otten (martin-otten) wrote :

I believe I got a similar issue. Sound plays fine through the speakers, but when I plug in my headphones they do not work and the speakers stop playing sound too.

==> /proc/asound/card0/codec#0 <==
Codec: Realtek ALC269VB

==> /proc/asound/card0/codec#3 <==
Codec: Intel CougarPoint HDMI
head: cannot open `cat' for reading: No such file or directory

==> /proc/asound/cards <==
 0 [PCH ]: HDA-Intel - HDA Intel PCH

==> /proc/asound/card0/codec#0 <==
Codec: Realtek ALC269VB

Revision history for this message
Ralf Futselaar (ralf-futselaar) wrote :

Updating to Oneric does not solve the problem. (As expected, but perhaps worth pointing out nevertheless.)

Revision history for this message
Alexandre Miguel de Araújo Lopes (aalopes) wrote :

Had the same problem as Kay A.Serenade (wind-summoner) with the external and internal mic on a Realtek ALC269 on a Asus 1015PEM using Lucid. Fixed the external mic problem by writing

options snd-hda-intel model=basic

to the end of

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

Don't know if it works for the headphone's jack problem though, as I never had it, but it's probably worth a try.

Revision history for this message
Ralf Hersel (ralf.hersel) wrote :

Updating to Precise does not solve the problem.

==> /proc/asound/card0/codec#0 <==
Codec: Realtek ALC269VB

==> /proc/asound/card0/codec#3 <==
Codec: Intel CougarPoint HDMI

==> /proc/asound/cards <==
 0 [PCH ]: HDA-Intel - HDA Intel PCH

==> /proc/asound/card0/codec#0 <==
Codec: Realtek ALC269VB

Plug in a headphone switches speakers off but no sound from headphones. As soon as headphones are plugged in, the slide control for 'Speakers' in Alsamixer drops down to zero. (The 'Headphones' control in Alsamixer has no effect and cannot be used.) Raising the Speakers controll will give sound to headphones.

Tanz Smith (tanzasmith)
description: updated
Luke Yelavich (themuso)
Changed in alsa-driver (Ubuntu):
assignee: Luke Yelavich (themuso) → nobody
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

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: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in alsa-driver (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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