Jump to content
178 posts in this topic

Recommended Posts

Relating to the posts by @cankiulascmnfye and @Anto65 I thought I'd do a test disk fresh install using the pre-loaded OCLP Mac installer USB.

This was done using the same type of external disk connection to a USB port I do with all my Test installs.

 

My thoughts on this type of installation are, whilst this nicely ties up the WIFI connection with the install, Man Oh Man it is mind numbing slow compared to the other way.

I did not time the install but I would hazard a guess, it took about one hour and a half to complete.

 

This could be just my rig and the type of connection but I am comparing it to the previous usual way I do my test installs.

During the first stage install it stays at 13 minutes left for about 20 or so minutes. If not for the activity light flickering on the cable connected to the drive, I would swear the install was in a loop.

 

Another part that was frustrating, after each reboot, at the boot menu it would always default to the first install of the process from the USB instead of the files on the disk.

In essence, it is not a process that can be set running without interaction like the conventional way.

 

In saying all this, it could be the findings are local to my setup and will not necessarily be like this for all.

In the end the installation was done albeit painfully slow.

  • Like 5

@eSaF, I did a test setup in this way and didn't notice any increase in time. Only time for installation of PKG and patch OCLP has been added.

The entire installation was completely automatic with the correct partition selection after each reboot. (Huananzhi PC)

Edited by verdazil
  • Like 8
  • Thanks 1

And since yesterday my hands are itching and the USB sticks come out of the drawer by themselves 😆
but at the moment I have nothing to patch the DW1820a I put it on my nephew's laptop
... it makes no sense for me at the moment to try that method  🤷 to give an evaluation

Edited by Anto65
  • Like 3
  • Haha 5
1 hour ago, verdazil said:

@eSaF, I did a test setup in this way and didn't notice any increase in time. Only time for installation of PKG and patch OCLP has been added.

The entire installation was completely automatic with the correct partition selection after each reboot. (Huananzhi PC)

Thanks, in my report I did say that maybe it could be how I do my test installs on an external connected drive via a USB Port

which by any standard won't be as fast as an internal connected drive. The comparison between this method and non pre-loaded OCLP was vast time wise.

 

I will bear in mind your findings if I ever do a clean install in the future and try it on an internal connected drive and note the difference in install time.

I did find it strange that the install did not choose the correct partition after each reboot during the install. I will also take note of your findings on that score.

Cheers.

 

PS. When you did your install using the pre-loaded OCLP method, in building the USB drive did you have the required kexts in the kext folder i.e 1080211FamilyLegacy.kext, IOSkywalkFamily.kext etc?

Query open to anyone who used this method.

Edited by eSaF
Add a query
  • Like 1
4 hours ago, eSaF said:

Relating to the posts by @cankiulascmnfye and @Anto65 I thought I'd do a test disk fresh install using the pre-loaded OCLP Mac installer USB.

This was done using the same type of external disk connection to a USB port I do with all my Test installs.

 

My thoughts on this type of installation are, whilst this nicely ties up the WIFI connection with the install, Man Oh Man it is mind numbing slow compared to the other way.

I did not time the install but I would hazard a guess, it took about one hour and a half to complete.

 

This could be just my rig and the type of connection but I am comparing it to the previous usual way I do my test installs.

During the first stage install it stays at 13 minutes left for about 20 or so minutes. If not for the activity light flickering on the cable connected to the drive, I would swear the install was in a loop.

 

Another part that was frustrating, after each reboot, at the boot menu it would always default to the first install of the process from the USB instead of the files on the disk.

In essence, it is not a process that can be set running without interaction like the conventional way.

 

In saying all this, it could be the findings are local to my setup and will not necessarily be like this for all.

In the end the installation was done albeit painfully slow.

 

After some research I found out that this package install feature is an undocumented feature of macOS. I guess you probably can also throw other apps in .pkg format into this "Packages" folder to have them installed unattendedly alongside macOS.

 

And: the AutoPkg-Assets.pkg.file will be added to the installer automatically if you create the USB installer with OCLP. If you install macOS via the app in the programs folder only then you have to add the AutoPkg-Assets.pkg to the installer manually, as described earlier.

 

I've tested the USB method last night on a fresh apfs volume on my Ivy Bridge notebook with Sequoia 15.2 and my experience was really good. I didn't have any of the problems you mentioned: installation took a bit longer, but once the setup-assistant was visible, everything was working immediately: WiF, BT, iGPU Acceleration, external display. But I had to run the patcher again in 15.2 since OCLP needed to download the latest metallib package in order to get transparency working properly. And this is only possible once the GUI can be displayed. Once you hit the button to apply root patches it will checks for the metallib thingy online. That's why it's a good idead to use LAN when working with OCLP if Wi-Fi requires patching first in order to work).

 

BTW: I probably will create a seperate repo for all the OCLP Wintel guides on the OC-Little repo soon. It's about time to bridge the gap to the OpenCore install guide (which just stops at 10th gen Intel Core and BigSur/Monterey) and the OpenCore Legacy Patcher guide which is for real Macs only…

 

 

 

 

 

Edited by cankiulascmnfye
  • Like 2
  • Thanks 1
20 minutes ago, cankiulascmnfye said:

 

I've tested the USB method last night on a fresh apfs volume on my Ivy Bridge notebook with Sequoia 15.2 and my experience was really good. I didn't have any of the problems you mentioned:

Thanks again. Now that I've read two success posts, I will have a play and do another clean install but this time I will try an internal connected drive and try and create the USB with the OCLP app.

Will report results on completion.

  • Like 3

OK as promised, I did another clean install but this time I used the OCLP app to build the installer USB drive.

After building on the USB, had to add the EFI Folder, plus the AutoPkgInstaller.kext to the kext folder and config.plist.

The USB installer took 40 minutes to build, the installation to the internal drive took one hour and 20 minutes from start to completion to reach the Desktop.

 

I am still somewhat skeptical at that length of time but did noticed the verbose readouts were more fluid and the reboots unlike before, did go to the correct volumes. So the installation is completely automated and yes WIFI is connected automatically. All in all, the process is an all in one procedure.

Just wish I could cut down the time it took.

 

I also noticed it not only put AutoPkg-Assets.pkg on the hidden volume on the installer but KDK.pkg, KDKInfo.plist and MetallibSupportPkg.pkg as well.

I don't know if I should have deleted these before starting the installation. I just left them in place.

Maybe someone can advise me about those so I will know the next time I do an install this way. 

  • Like 2

I lost bluetooth functionality with 15.3 beta 1.  Resetting bluetooth with "sudo killall -9 BlueTool bluetoothd" multiple times did not help.  I'll keep tinkering and report back.

 

EDIT:  I put the laptop to sleep for about 2-3 minutes.  After waking it up, bluetooth worked.  Go figure.  I remember back in the day there was a sleep/wake trick to getting video to work on some laptops.  Sometimes, the old solutions still work.

Edited by mnfesq
  • Like 1
2 minutes ago, mnfesq said:

I lost bluetooth functionality with 15.3 beta 1.  Resetting bluetooth with "sudo killall -9 BlueTool bluetoothd" multiple times did not help.  I'll keep tinkering and report back.

 

For me, Resetting NVRAM, forgeting the device and then recoupling it helps on Broadcom.

1 hour ago, eSaF said:

OK as promised, I did another clean install but this time I used the OCLP app to build the installer USB drive.

After building on the USB, had to add the EFI Folder, plus the AutoPkgInstaller.kext to the kext folder and config.plist.

The USB installer took 40 minutes to build, the installation to the internal drive took one hour and 20 minutes from start to completion to reach the Desktop.

 

I am still somewhat skeptical at that length of time but did noticed the verbose readouts were more fluid and the reboots unlike before, did go to the correct volumes. So the installation is completely automated and yes WIFI is connected automatically. All in all, the process is an all in one procedure.

Just wish I could cut down the time it took.

 

I also noticed it not only put AutoPkg-Assets.pkg on the hidden volume on the installer but KDK.pkg, KDKInfo.plist and MetallibSupportPkg.pkg as well.

I don't know if I should have deleted these before starting the installation. I just left them in place.

Maybe someone can advise me about those so I will know the next time I do an install this way. 

 

Sounds to me that either your USB flash drive is performing really badly or is not working at USB 3.0 speeds or that you are using an HDD. It doesn't even take that long on my 2011 imac (Sandy Bridge) – and that only supports USB 2.0! What system are you installing macOS on again?

  • Like 1
1 hour ago, cankiulascmnfye said:

 

Sounds to me that either your USB flash drive is performing really badly or is not working at USB 3.0 speeds or that you are using an HDD. It doesn't even take that long on my 2011 imac (Sandy Bridge) – and that only supports USB 2.0! What system are you installing macOS on again?

On my Z490, actually the USB Drive is so over used for multiple installs that it could be on it's way out after so many formats and deletions.

I think I will have to get a few more and discard these now as they are definitely past their sell by date. :lol:

Edited by eSaF
Typo
  • Like 2

Very smooth upgrade from Sequoia 15.2 -> 15.3 Beta ((24D5034f)).  Booting with OC 1.0.3.  Not using OCLP.  

 

A couple of noteworthy observations:

  • MS Remote Desktop and VNC Client are both able to connect to remote systems without toggling Ethernet.  Ethernet issues have come and gone with various Sequoia versions, so let's see if Apple has nailed the fix this time.
  • Intel Bluetooth is able to pair with my speaker and earbuds without issues

Screenshot2024-12-18at8_14_29AM.png.0ae0f4d95958f4cd3107672dc534fa37.png

  • Like 9
17 hours ago, eSaF said:

On my Z490, actually the USB Drive is so over used for multiple installs that it could be on it's way out after so many formats and deletions.

I think I will have to get a few more and discard these now as they are definitely past their sell by date. :lol:

 

What do you need root patches for on a Z490 system? WiFi and BT?

 

There's absolutely no point of using the auto-root-patching mechanism unless iGPU/GPU acceleration is affected, which is not the case on your system.

 

  • Like 3
39 minutes ago, cankiulascmnfye said:

 

What do you need root patches for on a Z490 system? WiFi and BT?

 

There's absolutely no point of using the auto-root-patching mechanism unless iGPU/GPU acceleration is affected, which is not the case on your system.

 

You're quite right I don't, it was just an experiment as I had nothing better to occupy my time.

I use OCLP the conventional hack way for my Fenvi Card.

  • Like 3
  • Haha 2

All this talk about OCLP stimulated me to ask a question.  I use File Vault on all my Macs.

 

I know that I can't have File Vault enabled, at least currently, if I want to install OCLP.  I just tried with 2.2 and it stopped and would not install if File Vault was enabled.

 

Has there been any discusion around somehow making OCLP and File Vault work together? I can't find any.  So, the OCLP root patching and process just can't work with File Vault, and that's it?  Sounds like if you want File Vault, you just have to live without OCLP...

  • Like 1
9 hours ago, Anto65 said:

Here I am in the 'Nothing Better to Do' mode, decided to do a test clean install of macOS Sequoia 15.3  (24D5034f) and it won't let me??!!

Thinking the USB drive is suspect, tried with different ones, still the same result.

 

It takes me up to formatting the recipient drive and then nothing. I did look at the installation log errors and it said something along the line of no previous version.

If that is the case, why the Full Installer unless my interpretation of such is flawed (No surprises there).

 

I will now try a Released version and see how that goes. This is the kind of thing when one has too much time on hand but I like to call it 'Tinkering'.

Or as the saying goes......'The devil makes light work for idle hands'.:lol:

  • Like 2
  • Haha 1
3 hours ago, eSaF said:

Here I am in the 'Nothing Better to Do' mode, decided to do a test clean install of macOS Sequoia 15.3  (24D5034f) and it won't let me??!!

Thinking the USB drive is suspect, tried with different ones, still the same result.

 

It takes me up to formatting the recipient drive and then nothing. I did look at the installation log errors and it said something along the line of no previous version.

If that is the case, why the Full Installer unless my interpretation of such is flawed (No surprises there).

 

I will now try a Released version and see how that goes. This is the kind of thing when one has too much time on hand but I like to call it 'Tinkering'.

Or as the saying goes......'The devil makes light work for idle hands'.:lol:

Hi dear, I'm sorry to tell you but there is some problem with your drones 😂 

... oops I meant USB
Just downloaded the installer from the link I provided, compared it with the Mist one and it's the same ... everything went well, no problem
Maybe you used some app for creating the USB?
Let this know-it-all know, who make nonsense statements without first having experienced it first hand
It happened in the past that problems occurred on Apple's part but (this is not the case) it has nothing to do with Full installer!? or PKG

 

Spoiler

Screenshot2024-12-19alle09_55_17.png.102360bfe71416238165914c3e5bd7bb.png

 

Screenshot2024-12-19alle09_44_30.thumb.png.e07776dcac960eb2e07d701527525329.png

 

 

Screenshot2024-12-19alle10_10_30.png.585c8d97092253788f9fa1e955c1f190.png

 

 

:thumbsup_anim:

Screenshot2024-12-19alle10_22_37.thumb.png.78c98c6e400f0a6e7253ddcd11686f5c.png

19092448.thumb.png.cd451561e6dd5e47398296315fbabe16.png

 

 

It seems to work too 😄...if I have time I'll try to install it

 

IMG_20241219_102641.thumb.png.aea4a28c1d4a769335d84c7c82652aee.png

 


 

 

Edited by Anto65
  • Like 3
  • Haha 1
4 hours ago, verdazil said:

aF, use the full installer, not PKG.

That worked!!

Would you believe it? I am about to do another test to find out what went wrong

with the one @Anto65 posted using that one again. The one that worked, I used the TINU app.

 

This time I will use the link again and build the USB Apple's way.

Fingers crossed, hoping for good result. Seriously far too much time on my hands.

I need another indoor hobby, this is getting ridiculous. :fiery:

Edited by eSaF
  • Like 6
25 minutes ago, Anto65 said:

... I never use the apps for creating the USB , use terminal ... I'm sure it works for you too

Yea I will use terminal this time.

Are you mad? get rid of my drones!!!! You sound just like the wife.........CRAZY!!!!! :hysterical:

  • Like 4
  • Haha 2
Guest
This topic is now closed to further replies.
×
×
  • Create New...