Jump to content
30960 posts in this topic

Recommended Posts

Ok, the .VolumeLabel.txt was ignored for the bottom right message. Fixed.

Sorry @Matgen84.

 

If not .VolumeLabel.txt is present OR if contents start with #, no bottom right message anymore.

 

A clarification : I introduced .VolumeLabel.txt because, as a developer, you end up doing a lot of test, which usually makes you duplicate EFI folder to some USB sticks. The .VolumeLabel.txt, intentionally at the root of the volume, is not copied with the EFI folder. It made my life so easier to not have to remember to change my config.plist each time I copied my EFI folder.

54 minutes ago, Jief_Machak said:

Ok, the .VolumeLabel.txt was ignored for the bottom right message. Fixed.

Sorry @Matgen84.

 

If not .VolumeLabel.txt is present OR if contents start with #, no bottom right message anymore.

 

A clarification : I introduced .VolumeLabel.txt because, as a developer, you end up doing a lot of test, which usually makes you duplicate EFI folder to some USB sticks. The .VolumeLabel.txt, intentionally at the root of the volume, is not copied with the EFI folder. It made my life so easier to not have to remember to change my config.plist each time I copied my EFI folder.

 

Ok. If I understand well (english is not my current language), .VolumeLabel.txt is now fixed (at the root of the volume). The other day, I put at the root of EFI partition (not in EFI Folder). Now, It will be copied at the root of "Catalina" my volume for macOS. Right?

 

For your clarification: I understand the needs of developers. But users do not have the same requirements. This is why this option could be managed via themes.plist strings and only including by default in those embedded by Clover.  Just my opinion.

Edited by Matgen84

If you want to have this message, this should be managed by the theme.plist. Should have nothing to do with config.plist. Also, why not just put an menu label in one of the menus that says which device and name of the device booted from? Then it does not need any of this stuff...

 

EDIT: Why not use OEM folders for different configuration on different machines?

Edited by apianti
  • Like 1
49 minutes ago, apianti said:

If you want to have this message, this should be managed by the theme.plist. Should have nothing to do with config.plist. Also, why not just put an menu label in one of the menus that says which device and name of the device booted from? Then it does not need any of this stuff...

 

EDIT: Why not use OEM folders for different configuration on different machines?

 

Hi @apianti It's exactly what I try to explain to @Jief_Machak. Thanks.

 

Sorry for my bad english.

  • Like 1
2 minutes ago, Matgen84 said:

EDIT: Why not use OEM folders for different configuration on different machines?

I wasn't talking about different machine, but different "EFI" folder on different drive/partition for the same machine.

 

@Matgen84 and I agree about using theme.plist. Everyone is welcome to submit a pull request.

  • Like 1
  • Thanks 1
3 hours ago, Jief_Machak said:

I wasn't talking about different machine, but different "EFI" folder on different drive/partition for the same machine.

 

@Matgen84 and I agree about using theme.plist. Everyone is welcome to submit a pull request.

 

Thanks @Jief_Machak I vote for.

3 hours ago, pkdesign said:

Okay. I am still confused. Do I put it in root of EFI partition or in EFI folder? Do I use # in the front of the name or not? And it if fixed where? In the next distribution of Clover?

It fixed here

CLOVERX64.efi.zip

If you are using bootx64.efi then replace it with this file renamed to BOOTX64.EFI

  • Like 1

hi all

i have succes instal catalina on asus g750jx work 100% thank's to pcfr33k guid.

soory if i out of date but i'm stuk with a probleme with clover

1- the new version 5103 do not boot the machin i have black screen so i dowgrad to 4945 to boot

2-i can't hide unwonted partition "this bcs i have yosemite+catalina+win10 instaled and 3 other partition "

so i want some help if some one can help for this

thank's

 

clover always boot in verbose mode? I checked config.plist no -v boot-arg. While booting click to space and I am seeing verbose mode selected I disable it from there and click boot but still booting in -verbose? WHY and How can I fix that?

3 minutes ago, telepati said:

clover always boot in verbose mode? I checked config.plist no -v boot-arg. While booting click to space and I am seeing verbose mode selected I disable it from there and click boot but still booting in -verbose? WHY and How can I fix that?

clear NVRAM

  • Thanks 1
On 1/20/2020 at 11:40 PM, telepati said:

Finally, found time and tested it. Native NVRAM also working on Clover. I attached my files if anyone needs it you can look at it.

As far as I know, OcQuirks does not contain any fixes relevant to the problem with the newer Aptio used in Z390. Are you sure it was not already working natively with AptioMemoryFix?

 

 

8 minutes ago, Pene said:

As far as I know, OcQuirks does not contain any fixes relevant to the problem with the newer Aptio used in Z390. Are you sure it was not already working natively with AptioMemoryFix?

 

 

Yes, it wasnt work natively. It's work with adding PMC ACPI.

 

https://github.com/acidanthera/OpenCorePkg/commit/a825da4e566bba827f0c462d598eaa2b2f0b84f4

  • Like 1
  • Thanks 1
10 hours ago, telepati said:

Yes, it wasnt work natively. It's work with adding PMC ACPI.

 

https://github.com/acidanthera/OpenCorePkg/commit/a825da4e566bba827f0c462d598eaa2b2f0b84f4

 

Thanks @telepati I don't try SSDT-PMC. With OcQuircks+FwRuntime, Memoryallocation.efi do the job: no more "runtime error" with the bios used in Z390 Aorus Master

  • Like 2
21 hours ago, Pene said:

As far as I know, OcQuirks does not contain any fixes relevant to the problem with the newer Aptio used in Z390. Are you sure it was not already working natively with AptioMemoryFix?

 

I have a Z390, I could test it but I don't have time currently. It could possibly work, I believe the issue was the shims and they removed the shims and directly modified the ability to write to a memory region by a hook in runtime instead.

  • Like 1
23 hours ago, telepati said:

Yes, it wasnt work natively. It's work with adding PMC ACPI.

 

https://github.com/acidanthera/OpenCorePkg/commit/a825da4e566bba827f0c462d598eaa2b2f0b84f4

Thanks for the information. Does it work also with AptioMemoryFix and SSDT-PMC?

 

1 hour ago, apianti said:

 

I have a Z390, I could test it but I don't have time currently. It could possibly work, I believe the issue was the shims and they removed the shims and directly modified the ability to write to a memory region by a hook in runtime instead.

I actually wonder if OcQuirks is actually required for it to work, as if you look to the commit posted earlier by telepati, they refer to this PMC device as the cause. I cannot test currently either, only in a couple of days.

13 minutes ago, Pene said:

Thanks for the information. Does it work also with AptioMemoryFix and SSDT-PMC?

 

I actually wonder if OcQuirks is actually required for it to work, as if you look to the commit posted earlier by telepati, they refer to this PMC device as the cause. I cannot test currently either, only in a couple of days.

I didnt test with AptioMemoryFix cause this efi always giving an allocation error for me. I am using it with OcQuircks+FwRuntime.

  • Like 1
14 hours ago, Pene said:

Thanks for the information. Does it work also with AptioMemoryFix and SSDT-PMC?

 

I actually wonder if OcQuirks is actually required for it to work, as if you look to the commit posted earlier by telepati, they refer to this PMC device as the cause. I cannot test currently either, only in a couple of days.

 

Yeah, you need OcQuirks or some fix, because that is what adjusts everything for proper system configuration. Also why you need FwRuntimeServices, because that is what actually does all that stuff. Weirdly, I read that link and then inspected my ACPI tables real quick, the device with "PNP0C02" HID and "PCHRESV" UID is a temperature sensor.... The only devices I have under "PNP0C02" HID are temperature sensors. Strange.

 

EDIT: I have only one reservation for the memory range 0xFC800000 to 0xFE7FFFFF.

Edited by apianti
  • Like 2
8 hours ago, telepati said:

I am not using OpenCore just testing from USB Installer but when I look Hackintool it says current bootloader is OpenCore. I cleaned caches and NVRAM with Mac Optimizer.app but still the same. How can I fix that?

 

1972233482_ScreenShot2020-01-25at00_39_49.thumb.png.66fe9f0dd9ef9f5fe4204fd3d5b88ce3.png

 

Do you try to post your issue in Hackintool Topic? :)

  • Thanks 1
×
×
  • Create New...