Date: Fri, 7 Dec 2018 16:22:03 +0200 From: Aleksandr Rybalko <ray@ddteam.net> To: Eugene Grosbein <eugen@grosbein.net> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>, ed@freebsd.org, Ed Maste <emaste@freebsd.org> Subject: Re: vt(4)-related hang of 11.2 Message-ID: <CAJ1Oi8ELD4dwGC-Jr0FcoADvM%2BfRVSRQBkpZu3F2AteTMOWRLQ@mail.gmail.com> In-Reply-To: <5C092D4B.8050302@grosbein.net> References: <5C092989.6000007@grosbein.net> <CAJ1Oi8HgwXJMPz7hWJMXrAmzKUnAWfgitZ1fmgbFMV_hv8=B7g@mail.gmail.com> <5C092D4B.8050302@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Eugene! In the sys/dev/vt/hw/efifb/efifb.c, starting from line 115, set of initialized fields of "info" struct. Like "info->fb_height = efifb->fb_height;". "efifb" holds data passed by loader from UEFI firmware metadata. There is fb_height, fb_width, fb_mask_(red|green|blue|reserved), fb_stride and fb_addr fields. In most cases fb_stride is wrong. So you can temporarly hardcode some of that values to real info for your display to check what is wrong. чт, 6 груд. 2018 о 16:08 Eugene Grosbein <eugen@grosbein.net> пише: > On 06.12.2018 20:57, Aleksandr Rybalko wrote: > > Hi, Eugene! > > > > In most cases it's just wrong info passed from UEFI firmware about FB. > > try to hardcode FrameBuffer params into vt_efb driver, to know exatly. > > I'm not familiar with vt_efb code. Can you please elaborate what should I > do to debug this, exactly? > > > -- WBW ------- Rybalko Aleksandr <ray@ddteam.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ1Oi8ELD4dwGC-Jr0FcoADvM%2BfRVSRQBkpZu3F2AteTMOWRLQ>