Bootloader Clover problems report & features request

[Pene]

10 minutes ago, Jief_Machak said:

I never used a nvram.plist. If I want to reproduce the bug in Qemu, where should I put it ? Have to add a driver ?

Put it in the root directory (/) of where clover is.

And add EmuVariableUefi.efi to (/EFI/CLOVER/drivers/UEFI/) 

 

I tried with Qemu, and yes, the bug still exists. And his nvram.plist doesn't contain invalid data, probably wasn't saved.

For example, his plist contains:

bluetoothActiveControllerInfo = 01 00 12 0a 00 00 00 00 16 1a 00 15 83 30 65 3c

and it is being parsed as (preboot.log):

7:881  0:000  === [ PutNvramPlistToRtVars ] ===================
...
7:882  0:000   Adding Key: bluetoothActiveControllerInfo: Size = 16, Data: 01 00 12 0A 00 00 00 00 16 1A 00 15 FFFFFF83 30 65 3C

 

Edited April 17, 2020 by Pene

[Jief_Machak]

Ok thanks. I'll do it soon.

[AndyYa]

In  the old  version  of  Clover  (for example  5096)  this  bug  not  present

bdmesg.log

[Matgen84]

Hi @Jief_Machak

 

Maybe I did a wrong things but on my Z390 config with 27" monitor: Shell.efi displays big caracters instead of usuals fonts (r5102 and previous versions). Can you tell me where I could have made a mistake.

 

Thanks

[Jief_Machak]

Pretty sure we introduced a bug, we're pretty good at that these times 

I'll commit in few minutes something about printf. Then try again with latest version and if it's still (it most likely will be), tell us (I hope @Slice will be able to have a look).

It'll be great if you can prepare a VMWare or Qemu virtual drive.

[Slice]

1 hour ago, Matgen84 said:

Hi @Jief_Machak

 

Maybe I did a wrong things but on my Z390 config with 27" monitor: Shell.efi displays big caracters instead of usuals fonts (r5102 and previous versions). Can you tell me where I could have made a mistake.

 

Thanks

Type 

>mode

in Shell interface and tell me what you see.

My example

[AndyYa]

5 hours ago, Jief_Machak said:

Ok thanks. I'll do it soon.

The  bug  is  gone  in  last  commit.    Thank you     :-)  

...

2:848  0:000   Adding Key: bluetoothActiveControllerInfo: Size = 16, Data: 01 00 12 0A 00 00 00 00 16 1A 00 15 83 30 65 3C
2:848  0:000   Adding Key: csr-active-config: Size = 4, Data: 67 00 00 00
2:848  0:000   Adding Key: efi-boot-device: Size = 216, Data: 3C 61 72 72 61 79 3E 3C 64 69 63 74 3E 3C 6B 65 79 3E 49 4F 4D 61 74 63 68 3C 2F 6B 65 79 3E 3C 64 69 63 74 3E 3C 6B 65 79 3E 49 4F 50 72 6F 76 69 64 65 72 43 6C 61 73 73 3C 2F 6B 65 79 3E 3C 73 74 72 69 6E 67 3E 49 4F 4D 65 64 69 61 3C 2F 73 74 72 69 6E 67 3E 3C 6B 65 79 3E 49 4F 50 72 6F 70 65 72 74 79 4D 61 74 63 68 3C 2F 6B 65 79 3E 3C 64 69 63 74 3E 3C 6B 65 79 3E 55 55 49 44 3C 2F 6B 65 79 3E 3C 73 74 72 69 6E 67 3E 42 41 41 41 44 34 38 34 2D 35 39 44 39 2D 34 39 44 35 2D 42 45 37 32 2D 31 33 43 31 36 39 39 32 41 37 45 36 3C 2F 73 74 72 69 6E 67 3E 3C 2F 64 69 63 74 3E 3C 2F 64 69 63 74 3E 3C 2F 64 69 63 74 3E 3C 2F 61 72 72 61 79 3E
2:848  0:000   Adding Key: efi-boot-device-data: Size = 85, Data: 02 01 0C 00 D0 41 08 0A 00 00 00 00 01 01 06 00 02 1F 01 04 15 00 C5 FA 31 CF 4E C2 D2 11 85 F3 00 A0 C9 3E C9 3B 80 04 01 2A 00 02 00 00 00 00 48 06 00 00 00 00 00 68 C1 CC 07 00 00 00 00 84 D4 AA BA D9 59 D5 49 BE 72 13 C1 69 92 A7 E6 02 02 7F FF 04 00

 

[Matgen84]

18 minutes ago, Slice said:

Type 

>mode

in Shell interface and tell me what you see.

 

It happen only my Z390 config (Gigabyte Aorus Master).

 

 

[Pene]

32 minutes ago, Matgen84 said:

 

It happen only my Z390 config (Gigabyte Aorus Master).

 

 

Try to set in your config.plist 

        <key>GUI</key>
        <dict>
                <key>ConsoleMode</key>
                <string>Max</string>

Maybe you already have it set to some wrong value?

If Max is too small, you can also set modes 1-5 that should corresponds to what is in the list you saw in shell.

Edited April 17, 2020 by Pene

[Matgen84]

30 minutes ago, Pene said:

Try to set in your config.plist 

        <key>GUI</key>
        <dict>
                <key>ConsoleMode</key>
                <string>Max</string>

Maybe you already have it set to some wrong value?

 

I try this value without success

 

 

[Pene]

 

12 minutes ago, Matgen84 said:

I try this value without success

Try to set it to 5.

 

EDIT: I committed a change to Clover that should fix your issue, it should choose the best mode in your case now also, no more need to set it.

Edited April 17, 2020 by Pene

[Matgen84]

6 minutes ago, Pene said:

 

Try to set it to 5.

 

Same problem. Fonts resolution!

[Pene]

1 minute ago, Matgen84 said:

Same problem. Fonts resolution!

You missed my edit.

[Matgen84]

31 minutes ago, Pene said:

You missed my edit.

 

I try latest commit: console mode always 80/25. 

In fact I have a problem rendering the text on the Z390 config. However, I have no problem with my IvyBridge config.

Edited April 17, 2020 by Matgen84

[Pene]

30 minutes ago, Matgen84 said:

 

I try latest commit: console mode always 80/25. 

In fact I have a problem rendering the text on the Z390 config. However, I have no problem with my IvyBridge config.

First, in your photo above, the selected console mode was not 80/25

Try again with consolemode=max with latest commit. Post config.plist, preboot.log and current output for the mode command from shell. And also a picture of the problem to better understand what you mean.

Edited April 17, 2020 by Pene

[Matgen84]

22 minutes ago, Pene said:

First, in your photo above, the selected console mode was not 80/25

Try again with consolemode=max with latest commit. Post config.plist, preboot.log and current output for the mode command from shell.

 

Thanks a lot: all works fine with console mode=max and new commit  Do you need config.plist, reboot.log!

 

 

[Pene]

Just now, Matgen84 said:

 

Thanks a lot: all works fine with console mode=max and new commit  Do you need config.plist, reboot.log!

 

 

Great.  No, if it works no need for anything.

[AndyYa]

In  boot.log  present  such  lines:

2:511  0:019  Slot: 0 Type 24 4096MB 1333MHz Vendor=Kingston PartNo=9905471-006.A01LF SerialNo=04080102050F0E00
2:530  0:019  Slot: 2 Type 24 4096MB 1333MHz Vendor=Kingston PartNo=9905471-009.A00LF SerialNo=0400020D0700060F

But Windows AIDA64 shows other values    SerialNo :  48125FE0h  and  402D706Fh

Is  that  a  bug  or  not ?

 

 

 

[joostiphone101]

So the following problem with Clover, I think, persists now for many builds (and I see many reports on the internet):

 

For Windows 10, I have the duplicate "Boot from EFI" showing, and this one does not boot. The one that does boot is 'Boot Microsoft EFI Boot from EFI'.  If I add this UUID to the hidden list, then both of them disappear. I have two separate SSD disks for Windows 10 and macOS.  This is Clover 5112.

 

I think I've tried a lot and I'm stuck now. Is this also something that Clover can better deal with in the future? 

 

 

 

 

[Slice]

24 minutes ago, crookedvult said:

So the following problem with Clover, I think, persists now for many builds (and I see many reports on the internet):

 

For Windows 10, I have the duplicate "Boot from EFI" showing, and this one does not boot. The one that does boot is 'Boot Microsoft EFI Boot from EFI'.  If I add this UUID to the hidden list, then both of them disappear. I have two separate SSD disks for Windows 10 and macOS.  This is Clover 5112.

 

I think I've tried a lot and I'm stuck now. Is this also something that Clover can better deal with in the future? 

 

 

 

 

 

 

Show list of files in your EFI folder.

You also can hide BOOTX64.EFI 

[joostiphone101]

 

 

 

1

7 hours ago, Slice said:

Show list of files in your EFI folder.

You also can hide BOOTX64.EFI 

 

See please here my EFI folder:

 

[Slice]

1 minute ago, crookedvult said:

 

See please here my EFI folder:

 

Sorry, what I have to see on this picture? It is standard.

[joostiphone101]

52 minutes ago, Slice said:

Sorry, what I have to see on this picture? It is standard.

Sorry, I thought you asked for my EFI folder. I thought you wanted to see something about my boot files. 

 

Anyway; I've hidden BOOTX64.EFI, but still I have the "Boot from EFI" showing up. 

[ameris_cyning]

I would like to request a Thunderbolt EFI driver

 

My mobo does not allow booting off a Thunderbolt HD. It can however do so if Grub is loaded from some other drive first. Unfortunately Clover doesn't see my Thunderbolt HD

[joostiphone101]

On 4/18/2020 at 6:59 PM, crookedvult said:

Sorry, I thought you asked for my EFI folder. I thought you wanted to see something about my boot files. 

 

Anyway; I've hidden BOOTX64.EFI, but still I have the "Boot from EFI" showing up. 

 

Wow, I'm happy; I finally solved this issue. 

 

Problem:

I had a duplicate Windows 10, "Boot from EFI" showing, and this one didn't boot. The one that did boot is 'Boot Microsoft EFI Boot from EFI'.  If I added this UUID to the hidden list, then both of them disappeared. I have two separate SSD disks for Windows 10 and macOS.

 

Solution:

It appears, that there was a little bug introduced in the config file. I thought that I had deselected 'Legacy' (that was what Clover Configurator was showing at least). So I Selected it in Clover Configurator, saved my EFI, then Deselected again and saved EFI again. Then it finally worked.  

 

Not sure of course if it was a bug in Clover.