Jump to content
8755 posts in this topic

Recommended Posts

On 4/10/2021 at 5:17 PM, miliuco said:

@eSaF  @antuneddu

 

Both of you are right, @tmbt has to empty and regenerate the Audio (Resources maybe) folder and check if there are files in EFI volume's bin. :thumbsup_anim:

 

Thanks,

i usually update my EFI with newer version of OpenCore and other kextss so this could be the case but my Trash is empty right now. How i can check if the trash's EFI partition is full of old files ?

 

Thanks

Mattia

 

29 minutes ago, tmbt said:

Thanks,

i usually update my EFI with newer version of OpenCore and other kextss so this could be the case but my Trash is empty right now. How i can check if the trash's EFI partition is full of old files ?

 

Thanks

Mattia

 

Mount EFI partition 

According to Dortania Guide, USBX is required for USB power properties as an OC post-install step.  If we have USB power properties in USBPorts.kext, is USBX required?

 

I've seen multiple discussions about this topic (maybe even earlier in this thread), but there seem to be as many opinions as there are posts.  My last two rigs have a custom USB port map (USBPorts.kext) that includes USB power properties.  I update USBPorts.kext/Contents/Info.plist with the matching USB power properties for my selected SMBIOS (extracted from a real Mac ACPI).  I don't inject Device (USBX) on these rigs and USB seems to work perfectly (with the correct power properties in IORegistry).

 

What's the latest recommended way to configure USB power properties: Device (USBX) or USBPorts.kext?

Edited by tonyx86
17 minutes ago, tonyx86 said:

According to Dortania Guide, USBX is required for USB power properties as an OC post-install step.  If we have USB power properties in USBPorts.kext, is USBX required?

 

I've seen multiple discussions about this topic (maybe even earlier in this thread), but there seem to be as many opinions as there are posts.  My last two rigs have a custom USB port map (USBPorts.kext) that includes USB power properties.  I update USBPorts.kext/Contents/Info.plist with the matching USB power properties for my selected SMBIOS (extracted from a real Mac ACPI).  I don't inject Device (USBX) on these rigs and USB seems to work perfectly (with the correct power properties in IORegistry).

 

What's the latest recommended way to configure USB power properties: Device (USBX) or USBPorts.kext?

Its up to you how you want to implement it, USBX ACPI way takes the same properties and applies it to all XHC controllers in the system, where as the injector kext requires the properties to be assigned to each XHC controller individually.

  • Like 2
  • Thanks 2
11 hours ago, tonyx86 said:

According to Dortania Guide, USBX is required for USB power properties as an OC post-install step.  If we have USB power properties in USBPorts.kext, is USBX required?

 

I've seen multiple discussions about this topic (maybe even earlier in this thread), but there seem to be as many opinions as there are posts.  My last two rigs have a custom USB port map (USBPorts.kext) that includes USB power properties.  I update USBPorts.kext/Contents/Info.plist with the matching USB power properties for my selected SMBIOS (extracted from a real Mac ACPI).  I don't inject Device (USBX) on these rigs and USB seems to work perfectly (with the correct power properties in IORegistry).

 

What's the latest recommended way to configure USB power properties: Device (USBX) or USBPorts.kext?

 

vit9696 replied in github about usb power properties.

It seems he's suggesting to use both USBX and kext injector, see point 3:

https://github.com/acidanthera/bugtracker/issues/1609#issuecomment-819087443

 

In my case USBX only didn't apply correctly power properties, I didn't try only the kext, I'm using both and it's working as it should.

  • Like 3
1 hour ago, ghost8282 said:

 

vit9696 replied in github about usb power properties.

It seems he's suggesting to use both USBX and kext injector, see point 3:

https://github.com/acidanthera/bugtracker/issues/1609#issuecomment-819087443

 

In my case USBX only didn't apply correctly power properties, I didn't try only the kext, I'm using both and it's working as it should.

I’m using both also but the kext has only port mapping, power properties are in the SSDT. 

  • Like 1

For completeness here is a link related to my previous issue:

 

If you look particularly at the image below "Moreover the usb properties here don't look correct...:", you will find that power properties for my xhci fresco were wrong with only USBX, and that was fixed only by injecting power properties within the usb map kext.

 

PS: I hope Hervé will not be too much angry, as this is slightly off topic..!

Edited by ghost8282
  • Like 1

@ghost8282 - Maybe this short discussion gets moved to the existing USB Problems thread where we spoke before; however, I think that as long as there are differences between OC documentation and reality, the discussion deserves a place in this thread.  If there's no harm in specifying identical USB Power Properties in both USBX (SSDT injection) and USBPorts.kext (and if in fact there are cases where only one or the other is appropriate), I'm leaning toward specifying the properties in both as a result of these latest comments.

Edited by tonyx86
  • Like 3
1 hour ago, miliuco said:

Strange. Most of us have around 200 mb. 

That would be because we used macOS to create it, it always does the 200mb, the 100mb is done by Windows.

Edited by MacUser2525
typo
  • Like 2
  • Thanks 1
3 hours ago, MacUser2525 said:

That would be because we used macOS to create it, it always does the 200mb, the 100mb is done by Windows.

I didn't know.

Of course, as @antuneddu says, even 100mb should be enough given the current size of the OpenCore EFI folders. My icon-themed versions 0.6.8 and 0.6.9 take about 10mb.

 

 

 

Edited by miliuco
  • Like 1
On 7/3/2020 at 12:49 AM, MacNB said:

 

Thanks boot-6d717c89b2bf90fc5378b652548d5e3c153396dc boots but the others fail.

Hello, I've similar problem with my old legacy server S5520HC, have U solved? Please let me know

Thanx in advance

21 minutes ago, mnfesq said:

Is there an entry that can be added to the config.plist to force the EFI folder to mount at boot?

Do you say to show EFI partition in OpenCore picker or to have EFI partition mounted in the desktop at boot?

5 hours ago, miliuco said:

I didn't know.

Of course, as @antuneddu says, even 100mb should be enough given the current size of the OpenCore EFI folders. My icon-themed versions 0.6.8 and 0.6.9 take about 10mb.

 

 

 

Yes it should be, but when they had the .wav files it was huge if you put the sounds in there too. I forget what the size was but trying to have couple of versions of the loader in it was near impossible without removing the excess languages.

4 hours ago, Check-IN said:

Hello, I've similar problem with my old legacy server S5520HC, have U solved? Please let me know

Thanx in advance

 

Yes it was fixed by the Devs and the fix is in the latest OpenDuet builds. Certainly works on my old Dell 530.

What chipset and SATA controller does your server motherboard use ?

Have use installed the latest Openduet (OpenCorePkg/Utilities/LegacyBoot/) ?

1 hour ago, miliuco said:

Do you say to show EFI partition in OpenCore picker or to have EFI partition mounted in the desktop at boot?

 

To have the EFI partition mounted at boot.  Clover has that function in the Clover prefpane.

11 hours ago, mnfesq said:

To have the EFI partition mounted at boot.  Clover has that function in the Clover prefpane.

It's off topic but you can do it by the /etc/fstab file. In Terminal

% > sudo pico /etc/fstab

Fstab can have entries relative to volumes so that they are mounted or not when starting macOS. Although it is a deprecated file, that by default in Big Sur is empty, it still works for this function.
Write in fstab:
LABEL=EFI none msdos rw, auto
Save it with Ctrl + O and exit with Ctrl + W.
Reboot.
When booting, the EFI partition should be on your desktop.
Disadvantage: if you have more than one EFI partition, they all will appear on the desktop. In this case, UUID must be used instead of Label.

 

Edited by miliuco
  • Like 1
  • Thanks 1
14 hours ago, mnfesq said:

Is there an entry that can be added to the config.plist to force the EFI folder to mount at boot?

1) No. Partitions are mounted by OS, not by bootloader

2) what for?

3) efi is hidden to prevent accidental changes and it is correct

Edited by Rodion2010
  • Confused 1
×
×
  • Create New...