Jump to content
30960 posts in this topic

Recommended Posts

Maybe you were quick enough to boot in the same minute?

Because the log doesn't write seconds in the name, it simply overwrote it (or appended the new log to that one) because the name was the same.

Edited by kushwavez
  • Thanks 1
19 minutes ago, kushwavez said:

Maybe you were quick enough to boot in the same minute?

Because the log doesn't write seconds in the name, it simply overwrote it (or appended the new log to that one) because the name was the same.

 

Thanks. 
I think so: maybe too quick restart is the problem for the first test or something else. :) I could notice that the log doesn't overwrite the existing file, (1) is added at the name for quick restart.

Edited by Matgen84
Just now, MifJpn said:

⌘  Powered by Clover revision: 5132 (master, commit a5494a89f)

As a reminder, checking the System Information once booted is NOT enough !

Many of my compilation will have the same commit number.

 

I guess I will have to improve that !

  • Like 2
26 minutes ago, Jief_Machak said:

As a reminder, checking the System Information once booted is NOT enough !

Many of my compilation will have the same commit number.

 

I guess I will have to improve that !


@Jief_Machak You already do that in Clover  "About" section : see @eng_redaesm screenshot 

 

Spoiler

1.png.068b34b56612ef01132579326da1de5f.png

 

1 minute ago, LIMITANT said:

@Jief_Machak

Why I'm still seeing the old commit !!

20210330_132932.jpg

If you see the wrong one, it's because you used the wrong one :lol: !

Maybe you copied it the wrong place.

Use BootloaderChooser, you'll never have that problem anymore !

 

21 minutes ago, Matgen84 said:

@Jief_Machak You already do that in Clover  "About" section : see @eng_redaesm screenshot 

True, but if you forgot to do it, you have to reboot.

And it'll take me 2 minutes (really) to have my build id instead of commit number on my own compilations. (Normal release will stay the same).

  • Like 2
13 minutes ago, Slice said:

@MifJpn

It is automatic substitution. But I am not sure about japanese keyboard

  Reveal hidden contents

MifJpn.png

 

And about

The key "A".

 

On my keyboard image.png.0aba1be2e1aae64b1a56dbb08692c1c2.png      image.png.787a9dc21e0dd4e6a188c9868006ca95.png    AZERTY, I've to press "Q" key (not "A") to access "About screen".  

  

  • Thanks 1
9 hours ago, Jief_Machak said:

 

@Jief_Machak 

 

With your "CloverX64-2021-03-30-06-39-58-a5494a8-dirty-jief.efi" on  Laptop Asus X75VB (MBP11,3) IvyBridge (I5-3340M HD4000) 

- Big Sur 11.2.3 (20D91)                     PreBoot and Recovery--> boot OK
- Big Sur beta5 11.3 (20E5217a)        PreBoot and Recovery--> boot OK
 

  • Like 2
11 hours ago, Jief_Machak said:

this version works too. 

Now is 30.03.2021,  15:37:13 (GMT)

Starting Clover revision: 5132 (master, commit a5494a89f) on Lenovo EFI

Build id: 2021-03-30-06-39-58-a5494a8-dirty-jief

Build with: [jief]

Good !

Thanks you very much for all the tests.

Stay tuned : I'm now refactoring the properties settings structure and it's a hard one because they are mixed in struct where not all field are used...

When done, I wouldn't be surprised on some other glitches...

  • Thanks 4

Hi all,

I've finally refactor the Device properties management in Clover. That was a huge nightmare, mainly because they were all using the same data structure with some field used in some case and some other never used in some other cases. Finding if something is NOT used is always harder than something where and when something is used !

As usual, any tests are welcomed as I can't test a lot of configuration...

 

I also improved the menu. There is now 3 sub menu in Options->Pci devices :

- Properties

- Arbitrary Properties

- Add Properties

 

They, of course, correspond to the Config.plist section.

In these menu, you can enable/disable each property.

 

So please, confirm that your device properties seems to be well injected.

 

Here is the efi CloverX64-2021-03-31-18-47-00-a5494a8-dirty-jief.zip

It's not committed yet, so please use this file. Do not compile the last commit (it's not working).

You can now check you used the right file once booted in macOs by looking at the system information :

207039945_Screenshot2021-03-31at18_49_41.png.b069a4fe9866e6171d0755e09b671801.png

The name must be the same as the efi file name when I posted it.

 

 

  • Thanks 2
23 minutes ago, Jief_Machak said:

Hi all,

I've finally refactor the Device properties management in Clover. That was a huge nightmare, mainly because they were all using the same data structure with some field used in some case and some other never used in some other cases. Finding if something is NOT used is always harder than something where and when something is used !

As usual, any tests are welcomed as I can't test a lot of configuration...

 

I also improved the menu. There is now 3 sub menu in Options->Pci devices :

- Properties

- Arbitrary Properties

- Add Properties

 

They, of course, correspond to the Config.plist section.

In these menu, you can enable/disable each property.

 

So please, confirm that your device properties seems to be well injected.

 

Here is the efi CloverX64-2021-03-31-18-47-00-a5494a8-dirty-jief.zip

It's not committed yet, so please use this file. Do not compile the last commit (it's not working).

You can now check you used the right file once booted in macOs by looking at the system information :

207039945_Screenshot2021-03-31at18_49_41.png.b069a4fe9866e6171d0755e09b671801.png

The name must be the same as the efi file name when I posted it.

 

 


@Jief_Machak I confirm: Boot fine (Z390 Big Sur 11.3 Beta 5). Thanks for your great work.

I take a look to the submenu of Option/PCIdevices. I don't understand what 'Arbitrary Properties' and  'Add Properties' are ! Because I don't find these sections in Config-sample.plist
 

Properties submenu, I like the checkbox. Is It possible to have also a checkbox for <key>PciRoot(0x0)/Pci(0x1c,0x1)/Pci(0x0,0x0)</key>, for example. So we can enable or disable all sub-keys in one time

Sorry for my bad 
English.

 

 

 

  • Thanks 1
1 hour ago, Jief_Machak said:

Hi all,

I've finally refactor the Device properties management in Clover. That was a huge nightmare, mainly because they were all using the same data structure with some field used in some case and some other never used in some other cases. Finding if something is NOT used is always harder than something where and when something is used !

As usual, any tests are welcomed as I can't test a lot of configuration...

 

I also improved the menu. There is now 3 sub menu in Options->Pci devices :

- Properties

- Arbitrary Properties

- Add Properties

 

They, of course, correspond to the Config.plist section.

In these menu, you can enable/disable each property.

 

So please, confirm that your device properties seems to be well injected.

 

Here is the efi CloverX64-2021-03-31-18-47-00-a5494a8-dirty-jief.zip

It's not committed yet, so please use this file. Do not compile the last commit (it's not working).

You can now check you used the right file once booted in macOs by looking at the system information :

207039945_Screenshot2021-03-31at18_49_41.png.b069a4fe9866e6171d0755e09b671801.png

The name must be the same as the efi file name when I posted it.

 

 

confirm boots well

  • Thanks 1
1 hour ago, Jief_Machak said:

Hi all,

I've finally refactor the Device properties management in Clover. That was a huge nightmare, mainly because they were all using the same data structure with some field used in some case and some other never used in some other cases. Finding if something is NOT used is always harder than something where and when something is used !

As usual, any tests are welcomed as I can't test a lot of configuration...

 

I also improved the menu. There is now 3 sub menu in Options->Pci devices :

- Properties

- Arbitrary Properties

- Add Properties

 

They, of course, correspond to the Config.plist section.

In these menu, you can enable/disable each property.

 

So please, confirm that your device properties seems to be well injected.

 

Here is the efi CloverX64-2021-03-31-18-47-00-a5494a8-dirty-jief.zip

It's not committed yet, so please use this file. Do not compile the last commit (it's not working).

You can now check you used the right file once booted in macOs by looking at the system information :

207039945_Screenshot2021-03-31at18_49_41.png.b069a4fe9866e6171d0755e09b671801.png

The name must be the same as the efi file name when I posted it.

 

 

there is something strange i've noticed with this build  HEVEC CODEC is not enabled

 

but with this build  working good 

 

On 3/30/2021 at 6:42 AM, Jief_Machak said:

Screen Shot 2021-03-31 at 8.33.24 PM.png

  • Like 1
2 hours ago, Matgen84 said:

Because I don't find these sections in Config-sample.plist

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

 

57 minutes ago, eng_redaesm said:

but with this build  working good 

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.

2 hours ago, Matgen84 said:

Is It possible to have also a checkbox for <key>PciRoot(0x0)/Pci(0x1c,0x1)/Pci(0x0,0x0)</key>, for example

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:

  • Thanks 1

I see that Clover is still stuck at this commit,

https://github.com/CloverHackyColor/CloverBootloader/commit/a5494a89f69a6ba08f12e8d287b97ab100ca0539

if it has already been said, sorry, but I have not read all the posts, but with this the device properties section is not loaded

10 minutes ago, iCanaro said:

I see that Clover is still stuck at this commit,

https://github.com/CloverHackyColor/CloverBootloader/commit/a5494a89f69a6ba08f12e8d287b97ab100ca0539

if it has already been said, sorry, but I have not read all the posts, but with this the device properties section is not loaded

Yes, I forgot to commit the fix yesterday and I started this properties refactoring.

That's why you have to use the efi I've posted here.

If there is reasonable success, I'll commit everything.

  • Thanks 2
46 minutes 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:

with this version at first glance everything seems OK, even H264 and HEVC are OK

43 minutes ago, Slice said:

and all my Properties are injected as it should.

@Slice Glad it works. Do you have any Device Properties ? or Arbitrary ? or AddProperties ?

3 minutes ago, iCanaro said:

with this version at first glance everything seems OK, even H264 and HEVC are OK

@iCanaro Which one ? There is 2 efi files in the poste you quoted. One is WITHOUT the refactor and one is WITH it. So it's important to know which one do you test.

This one is the refactored one : CloverX64-2021-03-31-21-50-04-a5494a8-dirty-jief

×
×
  • Create New...