From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.81]) by mx.groups.io with SMTP id smtpd.web11.2172.1589232434910708822 for ; Mon, 11 May 2020 14:27:15 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=hFrzMf2Y; spf=pass (domain: redhat.com, ip: 207.211.31.81, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1589232434; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=CRVW0pFxvM31pNKsC0Jy87axoi5OYS/1TGL7UN8HUOs=; b=hFrzMf2Y8zKcX8dnx7+2GHi1kuBIMbBAV0x5j1vArUOoxGowZa0FGmL7Djjp5AVR2+pAAE VExvB6J2zEj5CxI7cgbl3UsKXqBeHfWaXH/TI5NLRdkgB+GCBEUmw9T2DxJT8VL0KtN88i qnlWaM+H1u0p2GehihbNV1O5QjW2n6w= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-63-Vqj6VfFsMHe7IygYWI_MtA-1; Mon, 11 May 2020 17:27:07 -0400 X-MC-Unique: Vqj6VfFsMHe7IygYWI_MtA-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id F356F1054F8F; Mon, 11 May 2020 21:27:00 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-113-11.ams2.redhat.com [10.36.113.11]) by smtp.corp.redhat.com (Postfix) with ESMTP id 56FE37D8CD; Mon, 11 May 2020 21:27:00 +0000 (UTC) Subject: Re: [edk2-devel] Help with Logo Display Problems To: jim slaughter , devel@edk2.groups.io References: <160E089A62B6865C.18245@groups.io> From: "Laszlo Ersek" Message-ID: Date: Mon, 11 May 2020 23:26:59 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit On 05/11/20 20:04, jim slaughter wrote: > Hello, > > Yes BootLogoEnableLogo() appears in several files and is not commented out. > > Files: > PlatformBm.c > BdsPlatform.c > BootLogoLib.c > BootLogoLib.h > PlatformBm.c That doesn't answer my question. Does the PlatformBootManagerLib instance that is *specifically* linked into BdsDxe in *your* firmware platform call BootLogoEnableLogo()? Build your firmware with "--report-file=report.txt", and look up the following part: Module Name: BdsDxe [...] Module INF Path: MdeModulePkg/Universal/BdsDxe/BdsDxe.inf [...] Library [...] {PlatformBootManagerLib: Time = ...ms} The pathname just before the "PlatformBootManagerLib: Time" line gives you the INF file path that is relevant. Check the C files listed in that INF file, for a BootLogoEnableLogo() call. The call should be made in PlatformBootManagerAfterConsole(). Thanks Laszlo > > Jim Slaughter > ; > > On Mon, May 11, 2020 at 12:12 PM jim slaughter via groups.io sage-micro.com@groups.io> wrote: > >> Hello, >> >> I do not know. Will look into this. >> >> Is this call, BootLogoEnableLogo(), normally in the code? >> I have not added any code in this area. >> >> Jim S. >> ; >> >> On Mon, May 11, 2020 at 11:41 AM Laszlo Ersek wrote: >> >>> On 05/10/20 05:00, jim slaughter wrote: >>>> Hello, >>>> >>>> I have followed previous directions provided and the build works ok. I >>>> built an IA32 generic binary. >>>> I cannot tell if the logo code is working since I cannot see the logo >>> on my >>>> display. >>>> >>>> I do see a file in >>>> the ~/src/edk2-stable202002/Build/MdeModule/DEBUG_GCC5/IA32/$ directory, >>>> called LogoDxe.efi and another called LogoDxe. This leads me to >>>> believe that the Logo entry point is in the image. >>>> >>>> After the build I did find an empty map file? How do I get a map of the >>>> build? >>>> >>>> How do I debug this problem? I have no debugger. Can I freely use >>>> DEBUG((...........)); . >>>> >>>> Any help please. I am stuck. Thank you. >>>> >>> >>> Does your PlatformBootManagerLib instance call BootLogoEnableLogo() in >>> PlatformBootManagerAfterConsole()? >>> >>> Thanks, >>> Laszlo >>> >>> >> >> -- >> Jim Slaughter >> >> >> >