Date: Fri, 14 Sep 2018 11:53:45 +0300 From: Greg <greg@unrelenting.technology> To: Johannes Lundberg <johalun0@gmail.com> Cc: rebecca@bluestop.org, x11-list freebsd <freebsd-x11@freebsd.org> Subject: Re: Boot messages scroll off bottom of screen on ThinkPad T580 with drm-next-kmod-20180822 Message-ID: <20180914085345.xidsghn2knmdpxp7@unrelenting.technology> In-Reply-To: <CAECmPwsocZDNLJuGy9bHLnPac2t6yfTd%2BFwczVPwnas7ZuxECA@mail.gmail.com> References: <d33d4087-2bcc-9ea5-0b1c-196703f3e23a@bluestop.org> <3bfcafcb-337b-2e8c-08b2-f1d6d873dba8@bluestop.org> <CAECmPwsocZDNLJuGy9bHLnPac2t6yfTd%2BFwczVPwnas7ZuxECA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09/14, Johannes Lundberg wrote: >On Fri, Sep 14, 2018 at 2:59 AM Rebecca Cran via freebsd-x11 < >freebsd-x11@freebsd.org> wrote: > >> On 9/13/18 7:24 PM, Rebecca Cran via freebsd-x11 wrote: >> > I'm not sure when this started, but I've recently updated my kernel to >> > r338669 (12.0-ALPHA5) and am running drm-next-kmod-4.11-g20180822on a >> > ThinkPad T530. Now when I boot, after the i915kms.ko loads the boot >> > messages start scrolling off the bottom of the screen, and I can only >> > see them by hitting Enter lots of times. As suggested on gitter.im I >> > tried running drm-devel-kmod, but it caused the screen to blank and the >> > machine to apparently hang (as in >> > >> https://lists.freebsd.org/pipermail/freebsd-x11/2018-September/021588.html >> , >> > but the caps lock key on the built-in keyboard kept working). >> >> >> I've just realized that the built-in display shows the boot messages >> correctly, with the cursor remaining at the bottom of the screen: it's >> the external DisplayPort monitor that's having them scroll off the bottom. >> >> >> Hi Rebecca > >Yes, I have the same issue with my laptop with 1366x768 and external DP >display 3840x2160. I don't think it's possible to run console with two >separate resolutions so one resolution will dominate and the other display >won't show the content properly. It is odd that the larger one is picked though. On my desktop (amdgpu) when 1280x1024 and 3840x2160 monitors are connected, 1280x1024 is picked and the larger monitor has lots of blank space but everything is visible on both.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180914085345.xidsghn2knmdpxp7>