Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

Jief_Machak
Jief_Machak
Posted
Posted
7 minutes ago, iCanaro said:

@Jief_Machak 

i used this CloverX64-2021-03-31-18-47-00-a5494a8-dirty-jief.zip

you have device properties very populated in all the hacks, here for example the Z370

589437098_Schermata2021-03-31alle21_48_32.thumb.png.b0ba9de856f9edceb13f941cfe02d7cd.png

CloverX64-2021-03-31-18-47-00-a5494a8-dirty-jief.zip this one is good too.

Are they in Properties section ? Or Arbitrary section ? Or AddProperties section ?

iCanaro
iCanaro
Posted
Posted
2 minutes ago, Jief_Machak said:

CloverX64-2021-03-31-18-47-00-a5494a8-dirty-jief.zip this one is good too.

Are they in Properties section ? Or Arbitrary section ? Or AddProperties section ?

here

Devices --> Properties

659562438_Schermata2021-03-31alle22_01_41.thumb.png.e8b06069c4bd111ba581f9a2dcc0157d.png

eng_redaesm
eng_redaesm
Posted
Posted
1 hour ago, Jief_Machak said:

They exist under Device/Arbitrary and Devices/AppProperties. Maybe you just don't need it.

 

Probably an injection problem... That's the only thing I've touched.

@eng_redaesm Could you boot CloverX64-2021-03-31-21-48-49-a5494a8-dirty-jief.zip, check that HEVEC is enable and do "ioreg -lw0" > ioreg_ok.txt

Then boot : CloverX64-2021-03-31-21-50-04-a5494a8-dirty-jief.zip. Check that HEVEC in not enabled and do "ioreg -lw0 > ioreg_nok.txt

and send me the 2 files.

I'm afraid that'll be too much work for now, due to the way the Clover menu system works. But I guess one day I'll refactor that too :lol::lol::lol:

CloverX64-2021-03-31-21-48-49-a5494a8-dirty-jief.zip, works good there is HEVEC

but with  CloverX64-2021-03-31-21-50-04-a5494a8-dirty-jief.zip no HEVEC

here is the ioreg 

ioreg_nok_48.txt ioreg_nok_50.txt

  • Like 1
Matgen84
Matgen84
Posted
Posted
12 hours ago, Jief_Machak said:

I'm afraid that'll be too much work for now, due to the way the Clover menu system works. But I guess one day I'll refactor that too :lol::lol::lol:


@Jief_Machak I guess that'll be refactoring one day. TODO list is growing from day to day :D

Jief_Machak
Jief_Machak
Posted
Posted
11 hours ago, eng_redaesm said:

CloverX64-2021-03-31-21-48-49-a5494a8-dirty-jief.zip, works good there is HEVEC

but with  CloverX64-2021-03-31-21-50-04-a5494a8-dirty-jief.zip no HEVEC

here is the ioreg 

ioreg_nok_48.txt 1.8 MB · 0 downloads ioreg_nok_50.txt 1.8 MB · 0 downloads

 

10 hours ago, eng_redaesm said:

@Jief_Machak

very strange but test again now both commits has HEVEC  i don't know why or what happened  ioreg_nok50.txtioreg_nok49.txt

I have to say that I'm not sure which log correspond to what !

You both named them ioreg_nok_xx.txt. 'nok' stands for "Not OK'. But then, you said both boot were sucessful. You said "test again" soI guess it's a reboot.

 

So, did you generate ioreg_nok_48.txt with CloverX64-2021-03-31-21-48-49-a5494a8-dirty-jief.zip and you had HEVEC.

did you generate ioreg_nok_50.txt   with CloverX64-2021-03-31-21-50-04-a5494a8-dirty-jief.zip and had not HEVEC.

Then, you reboot CloverX64-2021-03-31-21-50-04-a5494a8-dirty-jief.zip one more time and you had HEVEC.

Am I correct on all 3 statements ?

@MifJpn Please stop apologizing ;). I don't even know what you apologize for. You're fine. You didn't waste time or annoyed anyone. Your contribution is much appreciated. Everything's ok.

  • Like 3
  • Thanks 1
matxpa
matxpa
Posted
Posted

@Jief_Machak

 

With your "CloverX64-2021-03-31-21-50-04-a5494a8-dirty-jief.efi" on  : 
    Laptop Asus X75VB (MBP11,3) IvyBridge (I5-3340M HD4000) and Desktop MSI Z270 SLI Plus (iMac18,3)  Kaby Lake (i5-7600K RX 570)
        - Big Sur 11.2.3 (20D91)                     PreBoot and Recovery--> boot OK
        - Big Sur beta6 11.3 (20E5224a)       PreBoot and Recovery--> boot OK

On Desktop only

        - Catalina 10.15.7 (19H524)                PreBoot and Recovery--> boot OK

 

Big Sur beta5 11.3 (20E5217a) to Big Sur beta6 11.3 (20E5224a) update was done on both Laptop and Desktop with that commit.

 

  • Like 3
eng_redaesm
eng_redaesm
Posted
Posted
5 hours ago, Jief_Machak said:

 

I have to say that I'm not sure which log correspond to what !

You both named them ioreg_nok_xx.txt. 'nok' stands for "Not OK'. But then, you said both boot were sucessful. You said "test again" soI guess it's a reboot.

 

So, did you generate ioreg_nok_48.txt with CloverX64-2021-03-31-21-48-49-a5494a8-dirty-jief.zip and you had HEVEC.

did you generate ioreg_nok_50.txt   with CloverX64-2021-03-31-21-50-04-a5494a8-dirty-jief.zip and had not HEVEC.

Then, you reboot CloverX64-2021-03-31-21-50-04-a5494a8-dirty-jief.zip one more time and you had HEVEC.

Am I correct on all 3 statements ?

@MifJpn Please stop apologizing ;). I don't even know what you apologize for. You're fine. You didn't waste time or annoyed anyone. Your contribution is much appreciated. Everything's ok.

yes you are correct 

Jief_Machak
Jief_Machak
Posted
Posted

Ok. So  that's probably not connected to my current refactoring because it seems to work with the others. That's why I've committed to github.

That said, if there is a Clover bug that causes intermittent failure of the codec loading, we'll track it !

Of course, the first thing to do is to know how to reproduce, because it's matter of luck, you never know for sure if this is fixed or not.

 

So I propose you stick to the last commit for a little time. You check if your codec is ok after each reboot. Have some cold boot too. Then after 10 or 20 boots, we'll see if the bug seems there, and if yes, how often.

You tell me then and will see...

last version is there : https://github.com/jief666/CloverCommits/blob/master/C-20210401110653-69a47c5.efi

  • Like 2
Slice
Slice
Posted
Posted

I don't know when it was happened but I see a problem

new Clover 

4:997  0:000  === [ GetMacAddress ] ===========================
4:997  0:000  === [ ScanSPD ] =================================

Old Clover rev 5130 

2:441  0:000  === [ GetMacAddress ] ===========================
2:441  0:000   get legacy LAN MAC, 1 card found
2:441  0:000  Legacy MAC address of LAN #0= 1C:1B:0D:66:5B:71:
2:441  0:000  === [ ScanSPD ] =================================

Why?

Slice
Slice
Posted
Posted

I made the bisection 

iMac2017:CloverBootloader sergey$ git bisect good
4a3bc612b85e61a77b8f760099a090b7bf2e9636 is the first bad commit
commit 4a3bc612b85e61a77b8f760099a090b7bf2e9636
Author: jief666 <github.com@jfa.knudsen.ovh>
Date:   Fri Mar 26 12:43:15 2021 +0300

    Create settings section Graphics, RtVariables.
    Mobe Turbo in GlobalConfig.

:040000 040000 2e1ae25009c9ebd84fd157d31061127a3b8ac1a5 ed70fa0b6dd4245c53409c9c924858f19923054b M	Include
:040000 040000 e3ddb98143e78428b9c483bc441727c4a663b478 a239dd5a7cd310a7e9ff972cbd38d32379165c31 M	Library
:040000 040000 0088f3300ecf989d50a1944e619e71ab45a181cc 2a7849860861a9145e3fcee454ef1cf8f9d2e8c0 M	Xcode
:040000 040000 9e0a346019e22a79f3ce62fcaa1c2b28339f51c9 9688c3002e6763c4f115f6640b7798d09cf9c9ff M	rEFIt_UEFI
iMac2017:CloverBootloader sergey$

 

eng_redaesm
eng_redaesm
Posted
Posted
16 hours ago, Jief_Machak said:

compare the debug.log when it’s working and not. Or send them to me.

@Jief_Machak here is the debug for not ok hevc and ok also ioreg not ok and ok

can you figure out what is the problem 

thanks

2021-4-2_10-8_CloverX64-RELEASE_GCC53-20210401110653-69a47c5.efi_nok_hevc.log 2021-4-2_10-29_CloverX64-RELEASE_GCC53-20210401110653-69a47c5.efi_ok_hevc.log ioreg_nok.txt ioreg_ok.txt

Jief_Machak
Jief_Machak
Posted
Posted
3 hours ago, eng_redaesm said:

@Jief_Machak here is the debug for not ok hevc and ok also ioreg not ok and ok

can you figure out what is the problem 

thanks

2021-4-2_10-8_CloverX64-RELEASE_GCC53-20210401110653-69a47c5.efi_nok_hevc.log 82.63 kB · 0 downloads 2021-4-2_10-29_CloverX64-RELEASE_GCC53-20210401110653-69a47c5.efi_ok_hevc.log 82.61 kB · 0 downloads ioreg_nok.txt 1.79 MB · 0 downloads ioreg_ok.txt 1.78 MB · 0 downloads

Unfortunately, I can't see anything different...

 

If you have reproduce this few times already, now you can use an old version, like 5130, and see if it does the same. If not, we know that it's because a commit in between. With dichotomy, we'll find it quite quick.

  • Like 1
Matgen84
Matgen84
Posted
Posted (edited)
52 minutes ago, Jief_Machak said:

Another refactoring. This time mainly on Smbios. Anyone who could check that there is no regression is welcome.

Use dmidecode before and after trying the last commit. Any change is a problem I'll fix.

Thanks.

dmidecode 120.89 kB · 1 download


@Jief_Machak I build new commit, and try with dmiecode :) How to use this tool ?

Edited by Matgen84
  • Like 1
LAbyOne
LAbyOne
Posted
Posted (edited)
39 minutes ago, Matgen84 said:


@Jief_Machak I build new commit, and try with dmiecode :) How to use this tool ?

just double click on it or eventually drag to terminal window and pipe to some editor if you want to keep the file.

i.e.

dmidecode > out.txt

 

your file will be in $HOME

 

or if you need somthing more specific its always a good idea to use --help

 

 

dmidecode --help

Usage: dmidecode [OPTIONS]

Options are:

 -i, --input-file       Decode DMI data from a binary file

 -d, --dev-mem FILE     Read memory from device FILE (default: I/O Registry)

 -h, --help             Display this help text and exit

 -q, --quiet            Less verbose output

 -s, --string KEYWORD   Only display the value of the given DMI string

 -t, --type TYPE        Only display the entries of given type

 -H, --handle HANDLE    Only display the entry of given handle

 -u, --dump             Do not decode the entries

     --dump-bin FILE    Dump the DMI data to a binary file

     --from-dump FILE   Read the DMI data from a binary file

     --no-sysfs         Do not attempt to read DMI data from sysfs files

     --oem-string N     Only display the value of the given OEM string

 -V, --version          Display the version and exit

Edited by LAbyOne
Matgen84
Matgen84
Posted
Posted
11 minutes ago, LAbyOne said:

just double click on it or eventually drag to terminal window and pipe to some editor if you want to keep the file.

i.e.

dmidecode > out.txt

 

your file will be in $HOME

 

@Jief_Machak Last commit not booting (Z390 Big Sur 11.3 Beta 6)

 

 

2021-4-3_16-11_CLOVERX64-2021-04-03-17-48-6ff5bab.efi.log

 Share
Go to topic listing
×
×
  • Create New...