MacBookPro11,1 (Late 2013 Haswell) has no sound

Bug #1255370 reported by Chun Li
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
alsa-driver (Ubuntu)
Invalid
Undecided
Unassigned
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

I installed Ubuntu 13.10 on a new MacBook Pro (Late 2013, 13-inch Haswell retina). The speakers did not work after installation, and after I fixed it, it would not work after suspend. It turns out some of the flags were not set correctly. I can fix these problems but it would be nice to have them fixed at installation.

The problem can be seen in the GPIO section in /proc/asound/card1/codec#0 (card0 is for HDMI). After boot, the GPIO flags for IO[0] were

GPIO: io=6, o=2, i=0, unsolicited=1, wake=1
  IO[0]: enable=1, dir=1, wake=0, sticky=0, data=0, unsol=0

If data were set to 1, sound would work! I fixed this by installing alsa-tools and adding to /etc/rc.local a line:

hda-verb /dev/snd/hwC1D0 0x1 set_gpio_data 1

After resuming from suspend, the GPIO flags for IO[0] became

GPIO: io=6, o=2, i=0, unsolicited=1, wake=1
  IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0

Here, three flags were set to 0. I fixed this by adding to /etc/pm/sleep.d/99_myfix a few lines:

#!/bin/sh
case "$1" in
 resume|thaw)
  hda-verb /dev/snd/hwC1D0 0x1 set_gpio_mask 1
  sleep 1
  hda-verb /dev/snd/hwC1D0 0x1 set_gpio_direction 1
  sleep 1
  hda-verb /dev/snd/hwC1D0 0x1 set_gpio_data 1
  ;;
esac
---
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: lic3 3717 F.... pulseaudio
 /dev/snd/controlC0: lic3 3717 F.... pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=a2156b27-f1e5-4408-9fb3-491e6f8229fb
InstallationDate: Installed on 2013-11-06 (21 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Apple Inc. MacBookPro11,1
MarkForUpload: True
NonfreeKernelModules: wl
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic.efi.signed root=UUID=b62d2699-f735-46a1-8e31-23146f2497a3 ro libata.force=noncq quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-13-generic N/A
 linux-backports-modules-3.11.0-13-generic N/A
 linux-firmware 1.116
Tags: saucy saucy
Uname: Linux 3.11.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 09/22/2013
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP111.88Z.0133.B00.1309220923
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-189A3D4F975D5FFC
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-189A3D4F975D5FFC
dmi.modalias: dmi:bvnAppleInc.:bvrMBP111.88Z.0133.B00.1309220923:bd09/22/2013:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
dmi.product.name: MacBookPro11,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1255370/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1255370

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Chun Li (lichun1668) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected saucy
description: updated
Revision history for this message
Chun Li (lichun1668) wrote : BootDmesg.txt

apport information

Revision history for this message
Chun Li (lichun1668) wrote : CRDA.txt

apport information

Revision history for this message
Chun Li (lichun1668) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Chun Li (lichun1668) wrote : IwConfig.txt

apport information

Revision history for this message
Chun Li (lichun1668) wrote : Lspci.txt

apport information

Revision history for this message
Chun Li (lichun1668) wrote : Lsusb.txt

apport information

Revision history for this message
Chun Li (lichun1668) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Chun Li (lichun1668) wrote : ProcEnviron.txt

apport information

Revision history for this message
Chun Li (lichun1668) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Chun Li (lichun1668) wrote : ProcModules.txt

apport information

Revision history for this message
Chun Li (lichun1668) wrote : PulseList.txt

apport information

Revision history for this message
Chun Li (lichun1668) wrote : RfKill.txt

apport information

Revision history for this message
Chun Li (lichun1668) wrote : UdevDb.txt

apport information

Revision history for this message
Chun Li (lichun1668) wrote : UdevLog.txt

apport information

Revision history for this message
Chun Li (lichun1668) wrote : WifiSyslog.txt

apport information

Revision history for this message
Chun Li (lichun1668) wrote :

I have run the command 'apport-collect 1255370'. I cannot found anywhere to change the status. Thanks.

Chun

Revision history for this message
Raymond (superquad-vortex2) wrote :

https://bugzilla.kernel.org/show_bug.cgi?id=60811

are you case similar to macbook air 6,2 or not ?

Revision history for this message
Chun Li (lichun1668) wrote :

I am not sure. My headphone works after installation and after resume. So there is no need to fix it. The internal mic seems to work fine, too. I do not have a mic to test external microphone.

I don't know if the patch code posted on that page would work or not on my Macbook Pro 11,1. I actually don't know how to apply the patch.

Revision history for this message
Raymond (superquad-vortex2) wrote :

seem you are not using alsa-driver since dB range of headphone is different from speakers

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/log/?qt=grep&q=cs4208

Revision history for this message
Raymond (superquad-vortex2) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in alsa-driver (Ubuntu):
status: New → Confirmed
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
Marcus Tomlinson (marcustomlinson) wrote :

This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you.

Changed in alsa-driver (Ubuntu):
status: Incomplete → Invalid
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.