On Fri, 27 Jul 2018 at 19:44:28 +0200, Mark Kettenis wrote:
> > Date: Thu, 26 Jul 2018 17:56:03 -0500
> > From: joshua stein
> >
> > On Thu, 26 Jul 2018 at 22:26:51 +0200, Mark Kettenis wrote:
> > > I'm hesitant to change this code. How does Linux behave on tese
> > > machines? Does it use the
> Date: Thu, 26 Jul 2018 17:56:03 -0500
> From: joshua stein
>
> On Thu, 26 Jul 2018 at 22:26:51 +0200, Mark Kettenis wrote:
> > I'm hesitant to change this code. How does Linux behave on tese
> > machines? Does it use the invisible part of the framebuffer? Or have
> > they done away with
On Thu, 26 Jul 2018 at 22:26:51 +0200, Mark Kettenis wrote:
> I'm hesitant to change this code. How does Linux behave on tese
> machines? Does it use the invisible part of the framebuffer? Or have
> they done away with actually using the kernel framebuffer completely
> like some developers
> Date: Mon, 23 Jul 2018 13:28:40 -0500
> From: joshua stein
>
> On the 2015 MacBook Pro and the 12" MacBook, the firmware reports a
> framebuffer size of 2880x1800 but the screens are 2560x1600 and
> 2304x1440. Our console ends up drawing text off screen and the
> latest few lines can't be
On Wed, Jul 25, 2018 at 08:51:53AM +0100, Stuart Henderson wrote:
> On 2018/07/24 13:25, Bryan Vyhmeister wrote:
> > (Obviously clock was wrong and I did not realize it. Looks like ntpd is
> > not setting the clock with -s for some reason so rdate did the trick.)
>
> If the clock is already more
On 2018/07/25 06:10, Bryan Vyhmeister wrote:
> On Wed, Jul 25, 2018 at 08:51:53AM +0100, Stuart Henderson wrote:
> > On 2018/07/24 13:25, Bryan Vyhmeister wrote:
> > > (Obviously clock was wrong and I did not realize it. Looks like ntpd is
> > > not setting the clock with -s for some reason so
On 2018/07/24 13:25, Bryan Vyhmeister wrote:
> (Obviously clock was wrong and I did not realize it. Looks like ntpd is
> not setting the clock with -s for some reason so rdate did the trick.)
If the clock is already more than a little bit wrong and you have
"constraints" in ntpd.conf, ntpd (even
On Mon, Jul 23, 2018 at 01:28:40PM -0500, joshua stein wrote:
> On the 2015 MacBook Pro and the 12" MacBook, the firmware reports a
> framebuffer size of 2880x1800 but the screens are 2560x1600 and
> 2304x1440. Our console ends up drawing text off screen and the
> latest few lines can't be
On the 2015 MacBook Pro and the 12" MacBook, the firmware reports a
framebuffer size of 2880x1800 but the screens are 2560x1600 and
2304x1440. Our console ends up drawing text off screen and the
latest few lines can't be read.
Once X loads, it probes the outputs again and uses the proper
