You are not logged in.

#1 2013-10-25 13:44:00

hrod
Member
Registered: 2013-10-24
Posts: 57

Macbook Pro Late 2013 Retina

MacBook Pro11,2 (intel iris pro HD5200 igpu only) october 2013

moved to: https://wiki.archlinux.org/index.php/MacBookPro11,x

edit:
acpi -V now shows correct design capacity

Last edited by hrod (2015-04-14 09:06:29)

Offline

#2 2013-10-26 00:26:17

hrod
Member
Registered: 2013-10-24
Posts: 57

Re: Macbook Pro Late 2013 Retina

moved to above post

Last edited by hrod (2013-10-27 22:15:21)

Offline

#3 2013-10-27 00:19:33

afiestas
Member
Registered: 2008-12-28
Posts: 18

Re: Macbook Pro Late 2013 Retina

Have you reported a bug about the Intel issue?

Offline

#4 2013-10-27 22:35:07

hrod
Member
Registered: 2013-10-24
Posts: 57

Re: Macbook Pro Late 2013 Retina

thanks, i'll submit a report to intel today.

Last edited by hrod (2013-10-31 01:26:55)

Offline

#5 2013-10-28 10:05:51

afiestas
Member
Registered: 2008-12-28
Posts: 18

Re: Macbook Pro Late 2013 Retina

Offline

#6 2013-11-01 18:41:32

alexh
Member
Registered: 2013-10-25
Posts: 3

Re: Macbook Pro Late 2013 Retina

Hi,

have you reported the bug yet? You can report it here: https://bugzilla.kernel.org/buglist.cgi … 20Intel%29

I'm quite interested in getting a macbook pro 2013 retina (13") myself, but that video bug is obviously a showstopper, so it'd be quite helpful, not just for me, if you reported it upstream. It'd also be good if you could update the "Macbook Pro Retina" wiki: https://wiki.archlinux.org/index.php/MacBookPro_Retina

EDIT: on digging a bit more I found this bug report on freedesktop: https://bugs.freedesktop.org/show_bug.cgi?id=71049 which seems to be about the same issue.

EDIT2: it seems only the Macbook Pro 15" is affected by the screen garbling from reading several posts on other forums. Probably because it has the 5200 graphics, vs 5100 in the 13".

Thanks,
Alex

Last edited by alexh (2013-11-01 21:22:20)

Offline

#7 2013-11-01 21:03:59

baronmog
Member
Registered: 2013-11-01
Posts: 58

Re: Macbook Pro Late 2013 Retina

hrod wrote:

MacBook Pro11,2 (intel iris pro HD5200 igpu only) october 2013

working:
installation using nomodeset
x using xf86-video-fbdev
sound headphones
wireless using broadcom-wl
keyboard backlight
multitouch enabled in touchpad synaptics

not working:
screen backlight control
resume gives black screen on open
sound speakers
unable to turn off optical audio
xf86-video-intel gives screen corruption

concern:
acpi -V shows an incorrect design capacity(6800mAh to 7100mAh), and the number fluctuates. why does it not just use the figure from /sys/class/power_supply/BAT0/energy_full_design (or uevent) of 8440mAh?

How did you even get that far, with the console as messed up as it is? I installed rEFInd and resized the MacOS partition (from OS X) easily enough. After booting from a usb stick with Arch ISO on it, the console is so garbled that I can't be certain that I'm reading things cgdisk correctly.

Offline

#8 2013-11-01 21:23:57

alexh
Member
Registered: 2013-10-25
Posts: 3

Re: Macbook Pro Late 2013 Retina

baronmog wrote:

How did you even get that far, with the console as messed up as it is? I installed rEFInd and resized the MacOS partition (from OS X) easily enough. After booting from a usb stick with Arch ISO on it, the console is so garbled that I can't be certain that I'm reading things cgdisk correctly.

Have you tried 'nomodeset' on the kernel command line?

Offline

#9 2013-11-01 21:42:10

streamer45
Member
Registered: 2013-10-31
Posts: 3

Re: Macbook Pro Late 2013 Retina

No problems except speakers sound on my Macbook Pro Retina 13.

Offline

#10 2013-11-01 22:34:21

baronmog
Member
Registered: 2013-11-01
Posts: 58

Re: Macbook Pro Late 2013 Retina

alexh wrote:

Have you tried 'nomodeset' on the kernel command line?

Yeah, that was the detail. Just had to add it to the options line in loader/entries/archiso-x86_64.conf .

Offline

#11 2013-11-03 01:19:31

afiestas
Member
Registered: 2008-12-28
Posts: 18

Re: Macbook Pro Late 2013 Retina

Not working:
-Webcam (not even listed on lspci/usb)
-Speakers
-Thunderbolt hotplug (this won't get fixed)

Not working perfect:
-Wireless with broadcom-wl, it is not as stable and fast as it is on osx (not by far).

Offline

#12 2013-11-03 03:55:16

hrod
Member
Registered: 2013-10-24
Posts: 57

Re: Macbook Pro Late 2013 Retina

afiestas wrote:

Not working perfect:
-Thunderbolt hotplug (this won't get fixed)

hotplug does not work on windows either, so yeah

afiestas wrote:

Not working perfect:
-Wireless with broadcom-wl, it is not as stable and fast as it is on osx (not by far).

performance isn't great for me either, but i've gotten no drop outs at home or uni.
91Mbits/s performance at desk on 2.4Ghz
98Mbits/s performance at airport on 2.4Ghz
(sometiems it changes to 5Ghz and gets 'Bitrate: 450Mbit/s', but it didn't do it when i made those images)

it also says 802.11abg in wavemon, however the airport is broadcasting 2.4Ghz n only, and 5Ghz n only

Last edited by hrod (2013-11-03 03:57:11)

Offline

#13 2013-11-03 19:25:18

baronmog
Member
Registered: 2013-11-01
Posts: 58

Re: Macbook Pro Late 2013 Retina

I get occasional hangs that last anywhere from 20s to a minute or so. There's always an accompanying set of logs from dmesg like the below:

[   68.369215] ata1.00: exception Emask 0x0 SAct 0x7ffe3fff SErr 0x0 action 0x6 frozen
[   68.369334] ata1.00: failed command: READ FPDMA QUEUED
[   68.369411] ata1.00: cmd 60/88:00:d8:41:d3/00:00:0d:00:00/40 tag 0 ncq 69632 in
         res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.369612] ata1.00: status: { DRDY }
[   68.369664] ata1.00: failed command: READ FPDMA QUEUED
[   68.369739] ata1.00: cmd 60/00:08:a8:05:e3/04:00:0d:00:00/40 tag 1 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.369940] ata1.00: status: { DRDY }
[   68.369993] ata1.00: failed command: READ FPDMA QUEUED
[   68.370066] ata1.00: cmd 60/00:10:a8:25:e3/04:00:0d:00:00/40 tag 2 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.370270] ata1.00: status: { DRDY }
[   68.370321] ata1.00: failed command: READ FPDMA QUEUED
[   68.370391] ata1.00: cmd 60/00:18:a8:2d:e3/04:00:0d:00:00/40 tag 3 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.370583] ata1.00: status: { DRDY }
[   68.370632] ata1.00: failed command: READ FPDMA QUEUED
[   68.370703] ata1.00: cmd 60/00:20:a8:31:e3/04:00:0d:00:00/40 tag 4 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.370895] ata1.00: status: { DRDY }
[   68.370945] ata1.00: failed command: READ FPDMA QUEUED
[   68.371015] ata1.00: cmd 60/00:28:a8:35:e3/04:00:0d:00:00/40 tag 5 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.371206] ata1.00: status: { DRDY }
[   68.371256] ata1.00: failed command: READ FPDMA QUEUED
[   68.371327] ata1.00: cmd 60/00:30:a8:39:e3/04:00:0d:00:00/40 tag 6 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.371518] ata1.00: status: { DRDY }
[   68.371568] ata1.00: failed command: READ FPDMA QUEUED
[   68.371638] ata1.00: cmd 60/00:38:a8:3d:e3/04:00:0d:00:00/40 tag 7 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.371830] ata1.00: status: { DRDY }
[   68.371880] ata1.00: failed command: READ FPDMA QUEUED
[   68.371950] ata1.00: cmd 60/00:40:a8:41:e3/04:00:0d:00:00/40 tag 8 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.372141] ata1.00: status: { DRDY }
[   68.372191] ata1.00: failed command: READ FPDMA QUEUED
[   68.372262] ata1.00: cmd 60/00:48:a8:45:e3/04:00:0d:00:00/40 tag 9 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.372464] ata1.00: status: { DRDY }
[   68.372514] ata1.00: failed command: READ FPDMA QUEUED
[   68.372585] ata1.00: cmd 60/40:50:68:b2:77/00:00:31:00:00/40 tag 10 ncq 32768 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.372777] ata1.00: status: { DRDY }
[   68.372827] ata1.00: failed command: WRITE FPDMA QUEUED
[   68.372899] ata1.00: cmd 61/a8:58:d8:b3:37/00:00:11:00:00/40 tag 11 ncq 86016 out
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.373091] ata1.00: status: { DRDY }
[   68.373141] ata1.00: failed command: WRITE FPDMA QUEUED
[   68.373213] ata1.00: cmd 61/78:60:b8:b3:77/00:00:27:00:00/40 tag 12 ncq 61440 out
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.373406] ata1.00: status: { DRDY }
[   68.377217] ata1.00: failed command: READ FPDMA QUEUED
[   68.381029] ata1.00: cmd 60/08:68:e0:d1:f7/00:00:0e:00:00/40 tag 13 ncq 4096 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.388335] ata1.00: status: { DRDY }
[   68.391932] ata1.00: failed command: READ FPDMA QUEUED
[   68.395355] ata1.00: cmd 60/08:88:a8:b4:33/01:00:14:00:00/40 tag 17 ncq 135168 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.402358] ata1.00: status: { DRDY }
[   68.405696] ata1.00: failed command: READ FPDMA QUEUED
[   68.409009] ata1.00: cmd 60/00:90:a8:f1:e2/04:00:0d:00:00/40 tag 18 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.415754] ata1.00: status: { DRDY }
[   68.418938] ata1.00: failed command: READ FPDMA QUEUED
[   68.422133] ata1.00: cmd 60/00:98:a8:f5:e2/04:00:0d:00:00/40 tag 19 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.428597] ata1.00: status: { DRDY }
[   68.431680] ata1.00: failed command: READ FPDMA QUEUED
[   68.434751] ata1.00: cmd 60/00:a0:a8:f9:e2/04:00:0d:00:00/40 tag 20 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.440945] ata1.00: status: { DRDY }
[   68.443932] ata1.00: failed command: READ FPDMA QUEUED
[   68.446894] ata1.00: cmd 60/00:a8:a8:fd:e2/04:00:0d:00:00/40 tag 21 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.452878] ata1.00: status: { DRDY }
[   68.455756] ata1.00: failed command: READ FPDMA QUEUED
[   68.458618] ata1.00: cmd 60/00:b0:a8:01:e3/04:00:0d:00:00/40 tag 22 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.464391] ata1.00: status: { DRDY }
[   68.467182] ata1.00: failed command: READ FPDMA QUEUED
[   68.469951] ata1.00: cmd 60/00:b8:a8:09:e3/04:00:0d:00:00/40 tag 23 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.475547] ata1.00: status: { DRDY }
[   68.478245] ata1.00: failed command: READ FPDMA QUEUED
[   68.480929] ata1.00: cmd 60/00:c0:a8:0d:e3/04:00:0d:00:00/40 tag 24 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.486342] ata1.00: status: { DRDY }
[   68.488964] ata1.00: failed command: READ FPDMA QUEUED
[   68.491567] ata1.00: cmd 60/00:c8:a8:11:e3/04:00:0d:00:00/40 tag 25 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.496827] ata1.00: status: { DRDY }
[   68.499365] ata1.00: failed command: READ FPDMA QUEUED
[   68.501892] ata1.00: cmd 60/00:d0:a8:15:e3/04:00:0d:00:00/40 tag 26 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.506991] ata1.00: status: { DRDY }
[   68.509539] ata1.00: failed command: READ FPDMA QUEUED
[   68.512072] ata1.00: cmd 60/00:d8:a8:19:e3/04:00:0d:00:00/40 tag 27 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.517194] ata1.00: status: { DRDY }
[   68.519738] ata1.00: failed command: READ FPDMA QUEUED
[   68.522278] ata1.00: cmd 60/00:e0:a8:1d:e3/04:00:0d:00:00/40 tag 28 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.527430] ata1.00: status: { DRDY }
[   68.529980] ata1.00: failed command: READ FPDMA QUEUED
[   68.532558] ata1.00: cmd 60/00:e8:a8:21:e3/04:00:0d:00:00/40 tag 29 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.537699] ata1.00: status: { DRDY }
[   68.540273] ata1.00: failed command: READ FPDMA QUEUED
[   68.542825] ata1.00: cmd 60/00:f0:a8:29:e3/04:00:0d:00:00/40 tag 30 ncq 524288 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   68.547961] ata1.00: status: { DRDY }
[   68.550517] ata1: hard resetting link
[   68.935620] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   68.935981] ata1.00: unexpected _GTF length (8)
[   68.936372] ata1.00: unexpected _GTF length (8)
[   68.936441] ata1.00: configured for UDMA/133
[   68.936445] ata1.00: device reported invalid CHS sector 0
[   68.936447] ata1.00: device reported invalid CHS sector 0
[   68.936449] ata1.00: device reported invalid CHS sector 0
[   68.936451] ata1.00: device reported invalid CHS sector 0
[   68.936452] ata1.00: device reported invalid CHS sector 0
[   68.936453] ata1.00: device reported invalid CHS sector 0
[   68.936455] ata1.00: device reported invalid CHS sector 0
[   68.936456] ata1.00: device reported invalid CHS sector 0
[   68.936458] ata1.00: device reported invalid CHS sector 0
[   68.936459] ata1.00: device reported invalid CHS sector 0
[   68.936461] ata1.00: device reported invalid CHS sector 0
[   68.936462] ata1.00: device reported invalid CHS sector 0
[   68.936464] ata1.00: device reported invalid CHS sector 0
[   68.936465] ata1.00: device reported invalid CHS sector 0
[   68.936467] ata1.00: device reported invalid CHS sector 0
[   68.936469] ata1.00: device reported invalid CHS sector 0
[   68.936470] ata1.00: device reported invalid CHS sector 0
[   68.936472] ata1.00: device reported invalid CHS sector 0
[   68.936473] ata1.00: device reported invalid CHS sector 0
[   68.936474] ata1.00: device reported invalid CHS sector 0
[   68.936476] ata1.00: device reported invalid CHS sector 0
[   68.936477] ata1.00: device reported invalid CHS sector 0
[   68.936479] ata1.00: device reported invalid CHS sector 0
[   68.936480] ata1.00: device reported invalid CHS sector 0
[   68.936482] ata1.00: device reported invalid CHS sector 0
[   68.936483] ata1.00: device reported invalid CHS sector 0
[   68.936485] ata1.00: device reported invalid CHS sector 0
[   68.936486] ata1.00: device reported invalid CHS sector 0
[   68.936510] sd 0:0:0:0: [sda]  
[   68.936512] Result: hostbyte=0x00 driverbyte=0x08
[   68.936513] sd 0:0:0:0: [sda]  
[   68.936515] Sense Key : 0xb [current] [descriptor]
[   68.936517] Descriptor sense data with sense descriptors (in hex):
[   68.936518]         72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 
[   68.936525]         00 00 00 00 
[   68.936528] sd 0:0:0:0: [sda]  
[   68.936528] ASC=0x0 ASCQ=0x0
[   68.936530] sd 0:0:0:0: [sda] CDB: 
[   68.936531] cdb[0]=0x28: 28 00 14 33 b4 a8 00 01 08 00
[   68.936537] end_request: I/O error, dev sda, sector 338932904
[   68.940271] ata1: EH complete

Offline

#14 2013-11-03 22:27:47

baronmog
Member
Registered: 2013-11-01
Posts: 58

Re: Macbook Pro Late 2013 Retina

hrod wrote:

MacBook Pro11,2 (intel iris pro HD5200 igpu only) october 2013
speaker sound
unable to turn off optical audio

This is probably tied into the on-keyboard volume controls not working. If you press any of the three buttons (Mute, Lower Volume, Raise Volume), the on-screen display always shows a volume of 0%.

Offline

#15 2013-11-04 01:53:01

baronmog
Member
Registered: 2013-11-01
Posts: 58

Re: Macbook Pro Late 2013 Retina

Adding to the list of things that don't work:

Thunderbolt  to DVI adapter.

Have verified that the adapter works under OS X, but does not work under Arch Linux. Tried the following scenarios:
- attach adapter after booting Linux
- attach adapter before booting Linux
- boot OS X, attach adapter (verify display works), reboot into Linux (without power cycle)

The 2nd display never shows up in KDE's display control or lspci/lshw output.

Offline

#16 2013-11-04 06:27:43

alexh
Member
Registered: 2013-10-25
Posts: 3

Re: Macbook Pro Late 2013 Retina

baronmog wrote:

I get occasional hangs that last anywhere from 20s to a minute or so. There's always an accompanying set of logs from dmesg like the below:

libata.force=noncq on the kernel command line might help.

Offline

#17 2013-11-04 22:33:30

afiestas
Member
Registered: 2008-12-28
Posts: 18

Re: Macbook Pro Late 2013 Retina

Speakers are fixed with Kernel 3.12 and https://bugzilla.kernel.org/show_bug.cgi?id=64401

One less thing to go! let's fix the webcam now.

Offline

#18 2013-11-04 22:34:50

afiestas
Member
Registered: 2008-12-28
Posts: 18

Re: Macbook Pro Late 2013 Retina

baronmog wrote:

Adding to the list of things that don't work:

Thunderbolt  to DVI adapter.

Have verified that the adapter works under OS X, but does not work under Arch Linux. Tried the following scenarios:
- attach adapter after booting Linux
- attach adapter before booting Linux
- boot OS X, attach adapter (verify display works), reboot into Linux (without power cycle)

The 2nd display never shows up in KDE's display control or lspci/lshw output.

VGA adaptor works fine.

Can you attach the output of xrandr and kscreen-console bug ?

Offline

#19 2013-11-04 23:29:50

baronmog
Member
Registered: 2013-11-01
Posts: 58

Re: Macbook Pro Late 2013 Retina

afiestas wrote:

Speakers are fixed with Kernel 3.12 and https://bugzilla.kernel.org/show_bug.cgi?id=64401

One less thing to go! let's fix the webcam now.

The diff in the bug entry adds "MacBookPro11,1". lshw reports mine has a product of "MacBookPro11,2" so that will need to be added as well.

Offline

#20 2013-11-05 15:23:12

afiestas
Member
Registered: 2008-12-28
Posts: 18

Re: Macbook Pro Late 2013 Retina

baronmog wrote:
afiestas wrote:

Speakers are fixed with Kernel 3.12 and https://bugzilla.kernel.org/show_bug.cgi?id=64401

One less thing to go! let's fix the webcam now.

The diff in the bug entry adds "MacBookPro11,1". lshw reports mine has a product of "MacBookPro11,2" so that will need to be added as well.

The maintainer came out with a better patch which includes all Apples with that chip I think.

Offline

#21 2013-11-06 05:01:29

baronmog
Member
Registered: 2013-11-01
Posts: 58

Re: Macbook Pro Late 2013 Retina

afiestas wrote:
baronmog wrote:

Adding to the list of things that don't work:

Thunderbolt  to DVI adapter.

Have verified that the adapter works under OS X, but does not work under Arch Linux. Tried the following scenarios:
- attach adapter after booting Linux
- attach adapter before booting Linux
- boot OS X, attach adapter (verify display works), reboot into Linux (without power cycle)

The 2nd display never shows up in KDE's display control or lspci/lshw output.

VGA adaptor works fine.

Can you attach the output of xrandr and kscreen-console bug ?

After posting that, it struck me that it might be related to using the xf86-video-fbdev driver, instead of the Intel driver. When I specify the driver from xf86-video-intel in the X config, I just get a blank screen with a blinking cursor in the upper left corner. The `kscreen-console bug` output below is, of course, while using the fbdev X driver.

START 
Config::current() took 1 milliseconds 

========================xrandr --verbose========================== 

xrandr: Failed to get size of gamma for output default
Screen 0: minimum 2880 x 1800, current 2880 x 1800, maximum 2880 x 1800
default connected primary 2880x1800+0+0 (0x17d) normal (normal) 0mm x 0mm
        Identifier: 0x17c
        Timestamp:  180075
        Subpixel:   unknown
        Clones:    
        CRTC:       0
        CRTCs:      0
        Transform:  1.000000 0.000000 0.000000
                    0.000000 1.000000 0.000000
                    0.000000 0.000000 1.000000
                   filter: 
  2880x1800 (0x17d)  471.7MHz *current
        h: width  2880 start    0 end    0 total 2880 skew    0 clock  163.8KHz
        v: height 1800 start    0 end    0 total 1800           clock   91.0Hz
 

========================Outputs=================================== 

KScreen version:  1.0.1 
Screen: 
        maxSize: QSize(2880, 1800) 
        minSize: QSize(2880, 1800) 
        currentSize: QSize(2880, 1800) 

-----------------------------------------------------
 
Id:  380 
Name:  "default" 
Type:  "Unknown" 
Connected:  true 
Enabled:  true 
Primary:  true 
Rotation:  1 
Pos:  QPoint(0,0) 
Size:  QSize(2880, 1800) 
Clones:  None 
Mode:  "381" 
Preferred Mode:  "381" 
Preferred modes:  () 
Modes:  
         "381"    "2880x1800"   QSize(2880, 1800)   91 
EDID Info:  
        Unavailable 

========================Configurations============================ 

Configs in:  "/home/klevin/.kde4/share/apps/kscreen/" 
Number of files:  1 

"c21f969b5f03d33d43e04f8f136e7682" 
"[
 {
  "enabled" : true,
  "id" : "default",
  "metadata" :   {
   "name" : "default"
  },
  "mode" :   {
   "refresh" : 91.0,
   "size" :    {
    "height" : 1800,
    "width" : 2880
   }
  },
  "pos" :   {
   "x" : 0,
   "y" : 0
  },
  "primary" : true,
  "rotation" : 1
 }
]"

Offline

#22 2013-11-06 17:09:52

jsmith
Member
Registered: 2013-11-06
Posts: 4

Re: Macbook Pro Late 2013 Retina

First post here, just reporting my findings so far. I upgraded from a 2012 Macbook Pro Retina to the Late 2013 Macbook Pro Retina (NVidia 750m graphics). I'm an ubuntu user (not by choice, third party software for works requires Ubuntu), running 13.04

Working:
NVidia drivers (Follow instructions on http://cberner.com/2013/03/01/installin … o-retina/). Both 319.60 and 331.17 drivers
Hibernate to disk
Screen backlight control (but only after hibernating at least once) Worked only once
External screens using DP -> HDMI cable (http://www.monoprice.com/Product?c_id=1 … 1&format=2)

Regressions from 2012 MBPr:
webcam not working
speakers (should be fixed in newest kernel tip, but that breaks NVidia drivers)
Suspend
Screen backlight control only worked on the 2012 after at least one suspend action.

Improvements:
Disk write speed (dd if=/dev/zero of=test bs=8k count=10M) increased from ~220MB/s to ~995MB/s)

Same:
Wireless still not as stable as it ought to be

Hibernating is about as fast as suspend on the 2012, so I don't mind loosing suspend

Last edited by jsmith (2013-11-06 18:40:42)

Offline

#23 2013-11-07 15:11:22

brunsgaard
Member
Registered: 2013-11-07
Posts: 1

Re: Macbook Pro Late 2013 Retina

Feel free to start sharing your findings in a more structured way on the wiki

https://wiki.archlinux.org/index.php/MacBookPro11,x

Offline

#24 2013-11-08 21:13:03

eyl
Member
Registered: 2013-11-08
Posts: 2

Re: Macbook Pro Late 2013 Retina

Note: I have a MacBookPro11,1, I don't know if it affects the 15" inch models as well.

I discovered an issue with kernel panics caused by what seems like power management controlling the SSD (both kernel 3.11.6 and 3.12). If I have powertop open and attempt to access any file system on the SSD (such as using ls) it'll panic with a null pointer dereference in skip_spaces saying "kernel panic not syncing: Fatal exception in interrupt".

Booting from a live USB drive I can mount the filesystem and keep powertop open as long as I want, it's only when I try to "ls" it immediately panics. It doesn't matter what the filesystem type is (I tried btrfs and fat, not like it should matter).  If I add "acpi=off" to the kernel parameters it won't panic, but of course modules like i915 will refuse to load without acpi. So, it appears to be something with the power management of the SSD.

Last edited by eyl (2013-11-09 04:07:44)

Offline

#25 2013-11-09 12:16:29

afiestas
Member
Registered: 2008-12-28
Posts: 18

Re: Macbook Pro Late 2013 Retina

eyl wrote:

Note: I have a MacBookPro11,1, I don't know if it affects the 15" inch models as well.

I discovered an issue with kernel panics caused by what seems like power management controlling the SSD (both kernel 3.11.6 and 3.12). If I have powertop open and attempt to access any file system on the SSD (such as using ls) it'll panic with a null pointer dereference in skip_spaces saying "kernel panic not syncing: Fatal exception in interrupt".

Booting from a live USB drive I can mount the filesystem and keep powertop open as long as I want, it's only when I try to "ls" it immediately panics. It doesn't matter what the filesystem type is (I tried btrfs and fat, not like it should matter).  If I add "acpi=off" to the kernel parameters it won't panic, but of course modules like i915 will refuse to load without acpi. So, it appears to be something with the power management of the SSD.

Report a bug at http://bugzilla.kernel.org pls.

Offline

Board footer

Powered by FluxBB