Tweet
Hi,
I just wanted to upgrade the memtest86 free v6 beta I am using (I'm chainloading it via rEFInd).
However, it seems that while with v6 beta I get the full native 1920x1080 resolution, with v6.3 and v7 beta I just get something like 640x480.
The machine is an Alienware 17 with nVidia GPU (3D edition => nVidia GPU only, directly connected via DP to internal display) with newest available UEFI fw.
Here parts of the log when loading v6.3.0:
and continuing.
I don't see the pre-test screens at all, only afterwards I see the test-screen and when going back to config, I get something like 640x480.
With v6 beta, the log starts like this:
There is no mentioning of this "Console Control protocol workaround", the mentioned console-size is larger, I don't get any of the "GraphicsOutput Blt returned: Invalid Parameter" later on, and everything is working perfectly (all screens at native resolution).
Maybe this "Console Control protocol workaround" is not needed for my machine and just breaks things?
If you need more info, I can of course also provide full logs / test different versions.
Thanks for this nice product and cheers,
Oliver
I just wanted to upgrade the memtest86 free v6 beta I am using (I'm chainloading it via rEFInd).
However, it seems that while with v6 beta I get the full native 1920x1080 resolution, with v6.3 and v7 beta I just get something like 640x480.
The machine is an Alienware 17 with nVidia GPU (3D edition => nVidia GPU only, directly connected via DP to internal display) with newest available UEFI fw.
Here parts of the log when loading v6.3.0:
Code:
2016-05-19 18:20:11 - ============================================= 2016-05-19 18:20:11 - MemTest86 V6.3.0 Free Build: 1000 (64-bit) 2016-05-19 18:20:11 - ============================================= 2016-05-19 18:20:11 - SMBIOS: Found SMBIOS BaseboardInformation (pbLinAddr=0x9DE7C081, FormattedLen=16, iTotalLen=94) 2016-05-19 18:20:11 - Manufacturer: Alienware, Product: 04WT2G, Version: A00, S/N: XREMOVED_FOR_PRIVACYX, AssetTag: , LocationInChassis: Type2 - Board Chassis Location 2016-05-19 18:20:11 - Console Control protocol workaround required 2016-05-19 18:20:11 - Console size = 80 x 25 ... 2016-05-19 18:20:16 - Screen size = 1920 x 1080 2016-05-19 18:20:16 - Char width=8 height=19 2016-05-19 18:20:16 - Installing default tests 2016-05-19 18:20:16 - Loading images 2016-05-19 18:20:16 - GraphicsOutput Blt returned: Invalid Parameter (Text="Exit" XPos=726, YPos=698, Width=32, Height=19, Delta=7680) 2016-05-19 18:20:16 - GraphicsOutput Blt returned: Invalid Parameter (Text="Config" XPos=1154, YPos=698, Width=48, Height=19, Delta=7680) 2016-05-19 18:20:16 - GraphicsOutput Blt returned: Invalid Parameter (Text="Please select an icon to continue" XPos=828, YPos=26, Width=264, Height=19, Delta=7680) 2016-05-19 18:20:16 - GraphicsOutput Blt returned: Invalid Parameter (Text="Use the Left / Right arrow keys, or mouse" XPos=796, YPos=47, Width=328, Height=19, Delta=7680) 2016-05-19 18:20:16 - GraphicsOutput Blt returned: Invalid Parameter (Text="Memory tests will automatically start in 10.0 seconds" XPos=744, YPos=5, Width=432, Height=19, Delta=7680)
I don't see the pre-test screens at all, only afterwards I see the test-screen and when going back to config, I get something like 640x480.
With v6 beta, the log starts like this:
Code:
2016-05-19 18:28:38 - ============================================= 2016-05-19 18:28:38 - MemTest86 V6.0 Beta Build: 0001 (64-bit) 2016-05-19 18:28:38 - ============================================= 2016-05-19 18:28:38 - Console size = 240 x 56 2016-05-19 18:28:38 - Intializing screen for graphics
Maybe this "Console Control protocol workaround" is not needed for my machine and just breaks things?
If you need more info, I can of course also provide full logs / test different versions.
Thanks for this nice product and cheers,
Oliver
Comment