Talk:Apple Macbook Pro Retina (early 2013)

Note
Before creating a discussion or leaving a comment, please read about using talk pages. To create a new discussion, click here. Comments on an existing discussion should be signed using ~~~~:

A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC)
: A reply [[User:Sally|Sally]] 12:39, 5 November 2024 (UTC)
:: Your reply ~~~~

Display backlight

Talk status

This discussion is done as of 30 July 2020.

The article says, that it is not possible to change that, if you use the nvidia driver. if you add

FILE /etc/local.d/nvidia.start

setpci -v -H1 -s 00:01.00 BRIDGE_CONTROL=0

(or just execute it in a shell) you can change the backlight within "/sys/class/backlight/gmux_backlight/brightness".

Thank you. --Davidbryant (talk) 17:31, 30 July 2020 (UTC)

Merged 2 pages

Talk status

This discussion is done as of 30 July 2020.

There were 2 pages for this same MacBook model. All the content from the other page Apple_Macbook_Pro_Retina_2013 was already included in this page, except for this somewhat older hint about some SATA issues. I'll put it here for reference, not sure if it's still necessary (can't test, have a new MacBook). This was added by User:Lu_zero

The System Rescue CD 4 works fine, pending a caveat due the SSD triggering a strange behaviour with SATA.

CODE

[  126.963413] ata1.00: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x6 frozen
[  126.963418] ata1.00: failed command: READ FPDMA QUEUED
[  126.963422] ata1.00: cmd 60/08:00:a0:59:7b/00:00:69:00:00/40 tag 0 ncq 4096 in
[  126.963422]          res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[  126.963423] ata1.00: status: { DRDY }
[  126.963425] ata1.00: failed command: WRITE FPDMA QUEUED
[  126.963427] ata1.00: cmd 61/08:08:e8:27:15/00:00:39:00:00/40 tag 1 ncq 4096 out
[  126.963427]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[  126.963429] ata1.00: status: { DRDY }
[  126.963430] ata1.00: failed command: WRITE FPDMA QUEUED
[  126.963432] ata1.00: cmd 61/88:10:e8:68:3e/00:00:56:00:00/40 tag 2 ncq 69632 out
[  126.963432]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[  126.963433] ata1.00: status: { DRDY }
[  126.963434] ata1.00: failed command: READ FPDMA QUEUED
[  126.963437] ata1.00: cmd 60/88:18:c8:3a:6e/00:00:38:00:00/40 tag 3 ncq 69632 in
[  126.963437]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[  126.963438] ata1.00: status: { DRDY }
[  126.963441] ata1: hard resetting link
[  127.291561] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  127.291930] ata1.00: unexpected _GTF length (8)
[  127.292627] ata1.00: unexpected _GTF length (8)
[  127.292837] ata1.00: configured for UDMA/133
[  127.292842] ata1.00: device reported invalid CHS sector 0
[  127.292844] ata1.00: device reported invalid CHS sector 0
[  127.292845] ata1.00: device reported invalid CHS sector 0
[  127.292847] ata1.00: device reported invalid CHS sector 0
[  127.292853] ata1: EH complete

Setting the queue_size to 1 workarounds it:

user $echo 1 > /sys/block/sda/device/queue_depth

Simonvanderveldt (talk) 10:54, 28 January 2016 (UTC)

Thank you for the information. --Davidbryant (talk) 17:34, 30 July 2020 (UTC)