[edk2-devel] Attempting to update to latest Repository Won't Build.
Hello, I was still on the SVN version (from 2019) and using VS2008. It would build fine. I created a new dir to use GIT now, I updated, ran: edksetup Reconfig Rebuild VS2019 So now, everything seems setup. I exit the command prompt, open it again, run my prep.bat script like I always did (setups up environment variables and calls edksetup). Then I try my build but it fails: -- Build environment: Windows-10-10.0.19045-SP0 Build start time: 22:30:34, Mar.27 2024 WORKSPACE= c:\edk PACKAGES_PATH= c:\edk\edk2-libc;c:\edk\edk2 EDK_TOOLS_PATH = c:\edk\edk2\basetools EDK_TOOLS_BIN= c:\edk\edk2\basetools\bin\win32 CONF_PATH= c:\edk\edk2\conf PYTHON_COMMAND = py -3 Processing meta-data . Architecture(s) = X64 Build target = RELEASE Toolchain= VS2019 Active Platform = c:\edk\edk2\Acme\Acme.dsc build.py... c:\edk\edk2\Acme\Acme.dsc(...): error 4000: Instance of library class [RegisterFilterLib] is not found in [c:\edk\edk2\MdePkg\Library\BaseLib\BaseLib.inf] [X64] consumed by module [c:\edk\edk2\Acme\myefiapp\myefiapp.inf] - Failed - -- Searching the edk2 I find the RegisterFilterLib pointing to the RegisterFilterLibNull which exists on in the directories: -- Volume in drive C is Windows 10 Directory of C:\edk\edk2\MdePkg\Include\Library 03/27/2024 06:18 PM 6,580 RegisterFilterLib.h 1 File(s) 6,580 bytes Directory of C:\edk\edk2\MdePkg\Library 03/27/2024 06:18 PM RegisterFilterLibNull 0 File(s) 0 bytes Directory of C:\edk\edk2\MdePkg\Library\RegisterFilterLibNull 03/27/2024 06:18 PM 6,410 RegisterFilterLibNull.c 03/27/2024 06:18 PM 627 RegisterFilterLibNull.inf 03/27/2024 06:18 PM 389 RegisterFilterLibNull.uni 3 File(s) 7,426 bytes -- What do I need to get this to automatically build like it did in the older versions? Thanks! -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#117215): https://edk2.groups.io/g/devel/message/117215 Mute This Topic: https://groups.io/mt/105203223/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[edk2-devel] test message - my messages aren't showing up?
I noticed the daily summary doesn't have my questions .. this is a test, can someone reply direct to confirm. Thanks. -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#117216): https://edk2.groups.io/g/devel/message/117216 Mute This Topic: https://groups.io/mt/105203224/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [edk2-devel] SIMPLE_TEXT_OUTPUT_PROTOCOL and Video Resolution
It would be nice to just update the specs to say, when a text mode is
chosen the resolution shall be set to the lowest resolution that
supports the cols and rows of the given text mode. Then over time all
the systems will handle it.
On Wed, Jun 23, 2021 at 3:24 AM Laszlo Ersek wrote:
>
> On 06/17/21 01:22, Andrew Fish via groups.io wrote:
> >
> >
> >> On Jun 16, 2021, at 2:45 PM, David F. wrote:
> >>
> >> Also, I found if there are 2 GOP handles and you change the mode of
> >> one, the other one doesn't reflect the change (but still doesn't solve
> >> anything with the original question), are you supposed to set the mode
> >> on every handle to keep that part in sync?
> >>
> >
> > A common implementation is to have the Conspliter [1] driver that produces
> > virtual handles that aggregate how many actual devices you have and manages
> > policy.
> >
> > You should grab the protocols on the gST->ConsoleOutHandle as these are the
> > Spec defined active console devices.
> >
> >
> > In terms on Simple Text Output Protocol on Graphics this is the default
> > driver in edk2 [2]. These are the config knobs you can set from your DSC
> > file to control defaults.
> >
> > [Pcd]
> > gEfiMdeModulePkgTokenSpaceGuid.PcdVideoHorizontalResolution ##
> > SOMETIMES_CONSUMES
> > gEfiMdeModulePkgTokenSpaceGuid.PcdVideoVerticalResolution ##
> > SOMETIMES_CONSUMES
> > gEfiMdeModulePkgTokenSpaceGuid.PcdConOutRow ##
> > SOMETIMES_CONSUMES
> > gEfiMdeModulePkgTokenSpaceGuid.PcdConOutColumn ##
> > SOMETIMES_CONSUMES
> > Note: If you have serial active that may mess with the Conspliter and force
> > it to pick a lower resolution since it has to find the best match between
> > the serial and graphics Simple Text In. So try the Graphics without the
> > serial terminal connect to see if it does different stuff.
>
> Regarding the serial terminal aspect, we discussed the following patch
> (maybe: workaround?) for that, many years ago, off-list:
>
> diff --git a/MdeModulePkg/Universal/Console/TerminalDxe/Terminal.c
> b/MdeModulePkg/Universal/Console/TerminalDxe/Terminal.c
> index a98b690c8b95..ded5513c74a7 100644
> --- a/MdeModulePkg/Universal/Console/TerminalDxe/Terminal.c
> +++ b/MdeModulePkg/Universal/Console/TerminalDxe/Terminal.c
> @@ -115,9 +115,44 @@ TERMINAL_DEV mTerminalDevTemplate = {
> };
>
> TERMINAL_CONSOLE_MODE_DATA mTerminalConsoleModeData[] = {
> - {80, 25},
> - {80, 50},
> - {100, 31},
> + { 80, 25 }, // from graphics resolution 640 x 480
> + { 80, 50 }, // from graphics resolution 640 x 960
> + { 100, 25 }, // from graphics resolution 800 x 480
> + { 100, 31 }, // from graphics resolution 800 x 600
> + { 104, 32 }, // from graphics resolution 832 x 624
> + { 120, 33 }, // from graphics resolution 960 x 640
> + { 128, 31 }, // from graphics resolution 1024 x 600
> + { 128, 40 }, // from graphics resolution 1024 x 768
> + { 144, 45 }, // from graphics resolution 1152 x 864
> + { 144, 45 }, // from graphics resolution 1152 x 870
> + { 160, 37 }, // from graphics resolution 1280 x 720
> + { 160, 40 }, // from graphics resolution 1280 x 760
> + { 160, 40 }, // from graphics resolution 1280 x 768
> + { 160, 42 }, // from graphics resolution 1280 x 800
> + { 160, 50 }, // from graphics resolution 1280 x 960
> + { 160, 53 }, // from graphics resolution 1280 x 1024
> + { 170, 40 }, // from graphics resolution 1360 x 768
> + { 170, 40 }, // from graphics resolution 1366 x 768
> + { 175, 55 }, // from graphics resolution 1400 x 1050
> + { 180, 47 }, // from graphics resolution 1440 x 900
> + { 200, 47 }, // from graphics resolution 1600 x 900
> + { 200, 63 }, // from graphics resolution 1600 x 1200
> + { 210, 55 }, // from graphics resolution 1680 x 1050
> + { 240, 56 }, // from graphics resolution 1920 x 1080
> + { 240, 63 }, // from graphics resolution 1920 x 1200
> + { 240, 75 }, // from graphics resolution 1920 x 1440
> + { 250, 105 }, // from graphics resolution 2000 x 2000
> + { 256, 80 }, // from graphics resolution 2048 x 1536
> + { 256, 107 }, // from graphics resolution 2048 x 2048
> + { 320, 75 }, // from graphics resolution 2560 x 1440
> + { 320, 84 }, // from graphics resolution 2560 x 1600
> + { 320, 107 }, // from graphics resolution 2560 x 2048
> + { 350, 110 }, // from graphics resolution 2800 x 2100
> + { 400, 126 }, // from graphics resolution 3200 x 2400
> + { 480, 113 }, // from graphics resolution 3840 x 2160
> +
Re: [edk2-devel] SIMPLE_TEXT_OUTPUT_PROTOCOL and Video Resolution
Also, I found if there are 2 GOP handles and you change the mode of one, the other one doesn't reflect the change (but still doesn't solve anything with the original question), are you supposed to set the mode on every handle to keep that part in sync? On Tue, Jun 15, 2021 at 11:33 PM David F. via groups.io wrote: > > Hello, > > I've found that most implementation of UEFI don't automatically change > the resolution when setting the mode with STOP (Simple Text Output > Protocol) . You can use GOP to change it after the mode but that > causes other problems. For example, using surface pro 7 in this case, > with 4K screen. The default text mode is 342x96 which puts it in > 2736x1824 mode which you'd expect and the text is tiny. But now you > set the mode to 0 which is 80x25 and it actually sets the mode to > 2736x1824 if not already in that resolution and uses a 80x25 area in > the center of the screen, still tiny text you can hardly read. If you > then say you want GOP in 640x480 mode (which is available as GOP mode > 1 on this system, it will make the font larger but you can't see > anything because it's still offset to the middle of the 2736x1824 area > and you're only seeing the 640x480 upper left of that area on the > screen. Likewise if you have it in 342x96 so it's fully in the upper > left corner of the screen and change the mode to say 800x600 > (available as GOP mode 2 on this system) it will make the text > readable but the text can go off the screen in both directions because > it's still 342x96 when the 100x31 STOP mode would be the correct one > (which happens to be mode 2 on this system). > > Shouldn't setting the STOP mode handle adjusting the resolution since > that's the main reason you want to change the mode so the size shown > on the screen changes to something you can read. > > Any tricks? I've tried a bunch of things, resetting the controller, > using the Reset() protocol function, and other things but nothing > works. As soon as you use STOP to set the mode, it is back to high > resolution and using an area centered in the screen and changing the > resolution after that leaves it in the area centered in the high res > screen and not in the upper left area. > > Thanks. > -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#76607): https://edk2.groups.io/g/devel/message/76607 Mute This Topic: https://groups.io/mt/83575008/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[edk2-devel] SIMPLE_TEXT_OUTPUT_PROTOCOL and Video Resolution
Hello, I've found that most implementation of UEFI don't automatically change the resolution when setting the mode with STOP (Simple Text Output Protocol) . You can use GOP to change it after the mode but that causes other problems. For example, using surface pro 7 in this case, with 4K screen. The default text mode is 342x96 which puts it in 2736x1824 mode which you'd expect and the text is tiny. But now you set the mode to 0 which is 80x25 and it actually sets the mode to 2736x1824 if not already in that resolution and uses a 80x25 area in the center of the screen, still tiny text you can hardly read. If you then say you want GOP in 640x480 mode (which is available as GOP mode 1 on this system, it will make the font larger but you can't see anything because it's still offset to the middle of the 2736x1824 area and you're only seeing the 640x480 upper left of that area on the screen. Likewise if you have it in 342x96 so it's fully in the upper left corner of the screen and change the mode to say 800x600 (available as GOP mode 2 on this system) it will make the text readable but the text can go off the screen in both directions because it's still 342x96 when the 100x31 STOP mode would be the correct one (which happens to be mode 2 on this system). Shouldn't setting the STOP mode handle adjusting the resolution since that's the main reason you want to change the mode so the size shown on the screen changes to something you can read. Any tricks? I've tried a bunch of things, resetting the controller, using the Reset() protocol function, and other things but nothing works. As soon as you use STOP to set the mode, it is back to high resolution and using an area centered in the screen and changing the resolution after that leaves it in the area centered in the high res screen and not in the upper left area. Thanks. -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#76576): https://edk2.groups.io/g/devel/message/76576 Mute This Topic: https://groups.io/mt/83575008/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[edk2-devel] Using debugger to debug UEFI application?
Hi, I just found the Intel UDK debugger and hopping to use it to debug my UEFI application. Basically, the function ippsEncodeLZ77DynamicHuff_8u in Intel IPP 7 (tried 7.1 as well) used in my application will hang if secure boot is enabled on most systems (disabled runs fine - someone with vmware workstation 15 sees same thing as physical system - I can't enable vmware secure boot because not running system in UEFI mode) - the source is shared with dos/linux/windows and all those work fine. I'm not sure why it hangs in that case, exception? stack? nothing I tried to do like force the stack size helped. So using this Lenovo laptop sitting next to me, can I use this Intel UDK debugger to connect via USB crossover cable and debug the application. I don't want to spend a bunch of time to only find out you can't do that and need special hardware. If not going to work then I'll have to spend time disassembling the application, injecting things in to the ippsEncodeLZ77DynamicHuff_8u to see what' up (a lot more work). Anyone feel free to chime in on what you think may be causing a problem when secure boot is enabled? TIA!! -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#60243): https://edk2.groups.io/g/devel/message/60243 Mute This Topic: https://groups.io/mt/74473343/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [edk2-devel] Updating to latest EDK2 and now get NMAKE: fatal error U1073: Don't know how to make.. on some items?
Let me start by what I did to get the build working with the old BaseTools. I renamed BaseTools and put back the prior BaseTools from Nov 29 2018 (build.exe date). It started building out of the gate, then hit nasm.inc not found, so digging around end up comparing old and new for things and brought over new NASM items from new GenMake.py to the old one. Tried again, same thing, ended up fixing by bringing over the new build_rule.txt. Now everything is building fine using VS2008 but the old BaseTools. I can try using VS2017, I though I was staying with VS2008 is VS2017 added more behind the scenes stuff that I have to add replacements for (already have what I need for VS2008). But I really don't remember. I'll do that when I get a chance once I catch up on things. Okay, now on to Guomin message, Those messages are saying it's not in the .inf, which looking in the .inf, they are not. Although the headers themselves exist. I got the edk2-libc repo from GIT. The edk2 repo I still use svn update to update it. Using tortoise tools on windows. Thanks. -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#60242): https://edk2.groups.io/g/devel/message/60242 Mute This Topic: https://groups.io/mt/74462877/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[edk2-devel] Updating to latest EDK2 and now get NMAKE: fatal error U1073: Don't know how to make.. on some items?
Hi, I haven't updated the edk2 in quite a while, I went ahead and did it tonight, stdlib was removed so I had to move stuff around. Where I used to have C:\EDK2, I now have C:\EDK\EDK2 and C:\EDK\EDK2-CLIB. My private directory is still under C:\EDK\EDK2\Acme. After figuring out how to get stdlib on its own repository by using the new directory, I then had to setup a batch file to do my edksetup in a different way. Now has: set WORKSPACE=%CD% set PACKAGES_PATH=%WORKSPACE%\edk2-libc;%WORKSPACE%\edk2 set EDK_TOOLS_PATH=%WORKSPACE%\edk2\BaseTools cd %WORKSPACE%\edk2 edksetup.bat It's all looking pretty good. I am using VS2008 for my EDK builds, I decided to stay with my old build_rule.txt, target.txt and tools_def.txt which has some older stuff in it that doesn't apply (I looked at the new stuff, but I have some custom switches and it wasn't much different). So I run my build switch to build my UEFI application and it starts and builds some items, but then dies with the NMAKE failure and I have no clue why. Here are some of the details after deleting c:\edk\build which is where it wants to go. Build environment: Windows-10-10.0.18362 Build start time: 00:33:37, May.25 2020 WORKSPACE = c:\edk PACKAGES_PATH = c:\edk\edk2-libc;c:\edk\edk2 EDK_TOOLS_PATH = c:\edk\edk2\basetools EDK_TOOLS_BIN = c:\edk\edk2\basetools\bin\win32 CONF_PATH = c:\edk\edk2\conf PYTHON_COMMAND = C:\python27-x64\python.exe Architecture(s) = X64 Build target = RELEASE Toolchain = VS2008x86 Active Platform = c:\edk\edk2\Acme\Acme.dsc build: : warning: Module MetaFile [Sources] is missing local header! Local Header: c:\edk\edk2-libc\stdlib\libc\gdtoa\gdtoaimp.h not found in c:\edk\edk2-libc\StdLib\LibC\gdtoa\gdtoa.inf build: : warning: Module MetaFile [Sources] is missing local header! Local Header: c:\edk\edk2-libc\stdlib\libc\gdtoa\gdtoa.h not found in c:\edk\edk2-libc\StdLib\LibC\gdtoa\gdtoa.inf build: : warning: Module MetaFile [Sources] is missing local header! Local Header: c:\edk\edk2-libc\stdlib\libc\time\tzfile.h not found in c:\edk\edk2-libc\StdLib\LibC\Time\Time.inf build: : warning: Module MetaFile [Sources] is missing local header! Several more like this from stdlib Building ... c:\edk\edk2\Acme\Library\ABLegacySpeakerLib\ABLegacySpeakerLib.inf [X64] Building ... c:\edk\edk2\Acme\Library\ABMemDumpLib\ABMemDumpLib.inf [X64] Building ... c:\edk\edk2\Acme\Library\ABVSSupportLib\ABVSSupportLib.inf [X64] "C:\Program Files (x86)\Microsoft Visual Studio 9.0\Vc\bin\x86_amd64\cl.exe" /Foc:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABLegacySpeakerLib\ABLegacySpeakerLib\OUTPUT\.\ /nologo /c /WX /GS- /X /W4 /Gs32768 /O1ib2s /GL- /Gy /FIAutoGen.h /EHs-c- /GR- /GF /X /Zc:wchar_t- /D UEFI_C_SOURCE /D MDEPKG_NDEBUG /D NDEBUG /Ic:\edk\edk2\Acme\Library\ABLegacySpeakerLib /Ic:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABLegacySpeakerLib\ABLegacySpeakerLib\DEBUG /Ic:\edk\edk2\MdePkg /Ic:\edk\edk2\MdePkg\Include /Ic:\edk\edk2\MdePkg\Include\X64 /Ic:\edk\edk2\Acme /Ic:\edk\edk2\Acme\Include /Ic:\edk\edk2\Acme\Include\AB\UEFI /Ic:\edk\edk2\Acme\Include\AB\fastgui /Ic:\edk\edk2\Acme\Include\AB /Ic:\edk\edk2\Acme\Include\IPP c:\edk\edk2\Acme\Library\ABLegacySpeakerLib\ABLegacySpeakerLib.c Building ... c:\edk\edk2\Acme\Library\ABMountedCPPEntryLib\ABMountedCPPEntryLib.inf [X64] Building ... c:\edk\edk2\Acme\Library\ABSafeOpenProtocolLib\ABSafeOpenProtocolLib.inf [X64] "C:\Program Files (x86)\Microsoft Visual Studio 9.0\Vc\bin\x86_amd64\cl.exe" /Foc:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABMemDumpLib\ABMemDumpLib\OUTPUT\.\ /nologo /c /WX /GS- /X /W4 /Gs32768 /O1ib2s /GL- /Gy /FIAutoGen.h /EHs-c- /GR- /GF /X /Zc:wchar_t- /D UEFI_C_SOURCE /D MDEPKG_NDEBUG /D NDEBUG /Ic:\edk\edk2\Acme\Library\ABMemDumpLib /Ic:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABMemDumpLib\ABMemDumpLib\DEBUG /Ic:\edk\edk2\MdePkg /Ic:\edk\edk2\MdePkg\Include /Ic:\edk\edk2\MdePkg\Include\X64 /Ic:\edk\edk2\Acme /Ic:\edk\edk2\Acme\Include /Ic:\edk\edk2\Acme\Include\AB\UEFI /Ic:\edk\edk2\Acme\Include\AB\fastgui /Ic:\edk\edk2\Acme\Include\AB /Ic:\edk\edk2\Acme\Include\IPP c:\edk\edk2\Acme\Library\ABMemDumpLib\ABMemDumpLib.c Building ... c:\edk\edk2\MdePkg\Library\UefiApplicationEntryPoint\UefiApplicationEntryPoint.inf [X64] ABLegacySpeakerLib.c Building ... c:\edk\edk2\MdePkg\Library\BaseIoLibIntrinsic\BaseIoLibIntrinsic.inf [X64] "C:\Program Files (x86)\Microsoft Visual Studio 9.0\Vc\bin\x86_amd64\cl.exe" /Foc:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABVSSupportLib\ABVSSupportLib\OUTPUT\.\ /nologo /c /WX /GS- /X /W4 /Gs32768 /O1ib2s /GL- /Gy /FIAutoGen.h /EHs-c- /GR- /GF /X /Zc:wchar_t- /D UEFI_C_SOURCE /D MDEPKG_NDEBUG /D NDEBUG /Ic:\edk\edk2\Acme\Library\ABVSSupportLib /Ic:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABVSSupportLib\ABVSSupportLib\DEBUG /Ic:\edk\edk2\MdePkg /Ic:\edk\edk2\MdePkg\Inc
[edk2-devel] BuildTools Broken
Last night through the forums I sent a problem with NMAKE U1073 trying to build. Some things built fine, but not others. I think my original message with all the details is still awaiting moderation. To follow up on that. I simply renamed BaseTools and restored the other one I had before updating back (which was older one where build.exe is Nov 29 2018), but now it starts building fine. Only breaks on some new items like longjump.nasm can't find nasm.inc which didn't exist back in the version I had. So I'll have to figure that out, but I guess I'll used the old BaseTools since the new one doesn't work either because I need to do something or it needs to be fixed. Building on Win10 but all that is in the other message. Using email now to see if it goes through faster. -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#60219): https://edk2.groups.io/g/devel/message/60219 Mute This Topic: https://groups.io/mt/74462867/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
