Bug 203376 - [uefi] 2014 apple macbook pro retina 15" does not use full screen on r287930 snapshot
Summary: [uefi] 2014 apple macbook pro retina 15" does not use full screen on r287930 ...
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: CURRENT
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on: 210382
Blocks:
  Show dependency treegraph
 
Reported: 2015-09-26 15:02 UTC by Dave Cottlehuber
Modified: 2017-11-14 05:44 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Cottlehuber freebsd_committer 2015-09-26 15:02:00 UTC
Booting off FreeBSD-11.0-CURRENT-amd64-20150917-r287930-memstick.img is now successful since fixes from #193745 & #202730, however the screen resolution is awry, filling ~3/4 of the screen only at a very low resolution, almost unreadable.

# uga info
UGA: Protocol not present (error=14)

# gop get
mode 0: 2880x1800x32
stride=2944
framebuffer: address = 90000000
size=1437000
color mask:
R 00ff0000
G 0000ff00
B 000000ff

# gop list
mode 0 as above
but, `mode 2` at loader prompt works fine, switches to a very readable resolution, and uses 100% of the screen. It would be perfect if it were possible to stay in this resolution. From within this mode, `gop list` and `gop get` return the same info as above.
Comment 1 Felix 2017-11-13 19:58:49 UTC
@dch is this fixed with #202288?
Comment 2 Felix 2017-11-13 19:59:33 UTC
sorry, I meant #210382.
Comment 3 Dave Cottlehuber freebsd_committer 2017-11-13 21:30:25 UTC
The macbook has been repurposed but I can at least confirm that the loader itself hasn't changed - still occupying the middle 3/4 of the screen, same debug info as noted earlier.

Given its got intel GPU inside I will see if I can try a recent 12.0-CURRENT and get different results
Comment 4 Felix 2017-11-14 05:44:35 UTC
(In reply to Dave Cottlehuber from comment #3)

So you mean this is in the loader itself - have you tried `mode 2' at the loader prompt? If not, what's the output of the `mode' command?