[MacBookAir5,1] Mini dp-2-VGA Adapter not recogonized

Bug #1222734 reported by Guillaume Mandil
66
This bug affects 13 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Since I update from 12.10 to 13.04 my mini dp to vga adapter is not recognized :

With VGA adapter connected to macbook air
mandilg@Horace:~$ xrandr
Screen 0: minimum 320 x 200, current 1366 x 768, maximum 8192 x 8192
eDP1 connected 1366x768+0+0 (normal left inverted right x axis y axis) 256mm x 144mm
   1366x768 60.0*+
   1360x768 59.8 60.0
   1024x768 60.0
   800x600 60.3 56.2
   640x480 59.9
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)
   1280x1024_60.00 60.0
HDMI2 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)

With mini dp to DVI adapter conneted to macbook air.
mandilg@Horace:~$ xrandr
Screen 0: minimum 320 x 200, current 3286 x 1200, maximum 8192 x 8192
eDP1 connected 1366x768+1920+203 (normal left inverted right x axis y axis) 256mm x 144mm
   1366x768 60.0*+
   1360x768 59.8 60.0
   1024x768 60.0
   800x600 60.3 56.2
   640x480 59.9
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
   1920x1200 60.0*+
   1600x1200 60.0
   1680x1050 59.9
   1280x1024 60.0
   1280x960 60.0
   1024x768 60.0
   800x600 60.3
   640x480 60.0
   720x400 70.1
DP1 disconnected (normal left inverted right x axis y axis)
   1280x1024_60.00 60.0
HDMI2 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)

it seems to be a bug on 3.8 kernel : see https://bbs.archlinux.org/viewtopic.php?pid=1270495

regards

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-25-generic 3.8.0-25.37
ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
Uname: Linux 3.8.0-25-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mandilg 2626 F.... pulseaudio
CRDA:
 country FR:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (N/A, 20)
  (5250 - 5330 @ 40), (N/A, 20), DFS
  (5490 - 5710 @ 40), (N/A, 27), DFS
Date: Mon Sep 9 11:58:38 2013
HibernationDevice: RESUME=UUID=82626092-cf02-414e-9ed6-924147b9b035
InstallationDate: Installed on 2012-12-19 (263 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: Apple Inc. MacBookAir5,1
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=e9a0f640-b834-45cb-9dd3-373676e1c3d2 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-25-generic N/A
 linux-backports-modules-3.8.0-25-generic N/A
 linux-firmware 1.106
SourcePackage: linux
UpgradeStatus: Upgraded to raring on 2013-06-09 (91 days ago)
dmi.bios.date: 07/27/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBA51.88Z.00EF.B01.1207271122
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-66F35F19FE2A0D05
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir5,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-66F35F19FE2A0D05
dmi.modalias: dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B01.1207271122:bd07/27/2012:svnAppleInc.:pnMacBookAir5,1:pvr1.0:rvnAppleInc.:rnMac-66F35F19FE2A0D05:rvrMacBookAir5,1:cvnAppleInc.:ct10:cvrMac-66F35F19FE2A0D05:
dmi.product.name: MacBookAir5,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

Revision history for this message
Guillaume Mandil (gmandil-x) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: Vga Adapter not recogonized with Macbook air

Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.8 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8.13.7-raring/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: regression-update
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
description: updated
Revision history for this message
Guillaume Mandil (gmandil-x) wrote :

tested with http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8.13.7-raring/ and the bug still exists with this kernel.

description: updated
penalvch (penalvch)
summary: - Vga Adapter not recogonized with Macbook air
+ [MacBookAir5,1] Vga Adapter not recogonized
penalvch (penalvch)
summary: - [MacBookAir5,1] Vga Adapter not recogonized
+ [MacBookAir5,1] Mini dp-2-VGA Adapter not recogonized
tags: added: kernel-bug-exists-upstream-v3.8.13.7
removed: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Guillaume Mandil (gmandil-x) wrote :

Here is the result of the command
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date after upgrading the bios :
[sudo] password for mandilg:
MBA51.88Z.00EF.B02.1211271028
11/27/2012

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Guillaume Mandil (gmandil-x) wrote :

The bios version didn't changed anything.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Guillaume Mandil, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, please only make a comment to this.

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: regression-release
removed: regression-update
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Guillaume Mandil (gmandil-x) wrote :

I tested the v3.9-rc8-raring kernel and the issue is still there with absolutely no changes.

otherwise, i'm anable to obtain a bootable usb stick with today daily-live iso image of latest developement release of ubuntu 13.10 (http://cdimage.ubuntu.com/daily-live/current/saucy-desktop-amd64+mac.iso)

tags: added: kernel-bug-exists-upstream-v3.9-rc8-raring
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Guillaume Mandil (gmandil-x) wrote :

I finally had a sucessful boot with the classical iso image (http://cdimage.ubuntu.com/daily-live/current/saucy-desktop-amd64.iso). But under this environement, the mini dp-to-vga adapter is still not recogonized.

Revision history for this message
penalvch (penalvch) wrote :

Guillaume Mandil, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc1-saucy/ and advise on the results?

tags: added: kernel-bug-exists-upstream-v3.9-rc8 saucy
removed: kernel-bug-exists-upstream-v3.8.13.7 kernel-bug-exists-upstream-v3.9-rc8-raring
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Guillaume Mandil (gmandil-x) wrote :

I'm unable to have a usefull system with this kernel but it seems that with this version the adapter is detected as I'm able to recive kernel error messages on my external screen during boot up.

Revision history for this message
penalvch (penalvch) wrote :

Guillaume Mandil, the next step is to bisect from Quantal to Raring, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

tags: added: needs-bisect
Revision history for this message
Guillaume Mandil (gmandil-x) wrote :

I already did this bisect...
The adapter was working with the last ubuntu 12.10 stable realese.
It stoped working with 13.04 stable release.
My differents testing showed that it's not working with all kernels included this one : http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.1-saucy/
It seems to work again with http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc1-saucy/.

Revision history for this message
Fredrik Wendt (fredrik-wendt) wrote :

I have a MacBook Air 5,2 and was too hit by this unpleasant surprise infront of a class. (I usually use DP/HDMI but occasionally run into organisations with VGA only.)

I'll boot up a daily build of Sausy and see how it behaves. Should I report back here or in a separate bug (because of different MacBook hardware)?

Revision history for this message
Fredrik Wendt (fredrik-wendt) wrote :

I just ran a daily build of Sausy on my MacBook 5,2 and the VGA adapter did not work - xrandr gives the same output with and without the adapter plugged in. HDMI-adapter on the other hand worked perfectly.

Revision history for this message
penalvch (penalvch) wrote :

Fredrik Wendt, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

tags: added: kernel-bug-exists-upstream-v3.11.1 kernel-fixed-upstream-v3.12-rc1
removed: kernel-bug-exists-upstream-v3.9-rc8
Revision history for this message
penalvch (penalvch) wrote :

Guillaume Mandil regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222734/comments/15 :
>"I already did this bisect..."

No, you did not. You bisected it to two different releases. Doing a commit bisect between those releases, as noted in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222734/comments/14 , is what was requested.

>"My differents testing showed that it's not working with all kernels included this one : http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.1-saucy/ It seems to work again with http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc1-saucy/."

If it's fixed in upstream v3.12-rc1 then it may end up landing in Saucy.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Vishnu (vishnuholmes) wrote :

I still have this problem in ubuntu 14.10

Changed in linux (Ubuntu):
status: Expired → Incomplete
Revision history for this message
penalvch (penalvch) wrote :

Vishnu, thank you for your comment. So your issue may be dealt with as soon as possible, and so your hardware may be tracked by having necessary debugging information automatically attached, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu repository kernel via:
ubuntu-bug linux

For more on why this is most helpful, please read the official Ubuntu documentation from the respective Ubuntu developer groups, and triage teams:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.