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),
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.
>>>
>>> Forgot to add importand detail: it boots and works with vt(4) using FreeBSD
>>> 11.1.
>>>
>>
>> r322258 is known working stable/11
On 06.12.2018 23:01, Eugene Grosbein wrote:
>>> 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.
>>
>> Forgot to add importand detail: it boots and works with vt(4) using FreeBSD
>> 11.1.
>>
>>
>
>
On 06.12.2018 22:52, Eugene Grosbein wrote:
> On 06.12.2018 20:57, Aleksandr Rybalko wrote:
>
>> 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.
>
> Forgot to add importand detail: it boots and works
On 06.12.2018 20:57, Aleksandr Rybalko wrote:
> 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.
Forgot to add importand detail: it boots and works with vt(4) using FreeBSD
11.1.
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
On 06.12.2018 20:52, Eugene Grosbein wrote:
> Hi!
>
> I ran across several systems based on AMI Aptio CRB CLBTM210 equiped with
> Intel J1900 processor
> that hang early at boot in the moment of kernel initialisation unless forced
> to use syscons(4) console driver
> instead of default vt(4).
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.
Thanks.
чт, 6 груд. 2018 о 15:52 Eugene Grosbein пише:
> Hi!
>
> I ran across several systems based on AMI Aptio CRB CLBTM210 equiped with
Hi!
I ran across several systems based on AMI Aptio CRB CLBTM210 equiped with Intel
J1900 processor
that hang early at boot in the moment of kernel initialisation unless forced to
use syscons(4) console driver
instead of default vt(4). Here is screen photo of one of such systems in such
dead
