Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Although you will not get any answers to questions here (eg why the keyboard does not work in Catalina)
you probably do not like hackintosh users like me, but I still want to report that on my hack-book,
an Intel Medion Akoya P8610, everything like WiFi , Sound, trackpad, keyboard, etc. works.
I found it out myself without help from here. Only the transparency is not yet, but I also solve the problem.
Nevertheless, many thanks for the useful hints from here to get Catalina on the device at all to get.
Some people need to have patience if you have Catalina installed then you are lot further than most of us first is getting it to install for the rest of us then we tackle other issues
 
I tried to clone it several ways, I just can't...

You may try: this method

Is a bit longer but has an advantage, that will clone only the occupied space, so if your drive is 128 gb with 40 gb used, it will clone only 40 gb.

It will create an image of your current APFS container and then you will restore that image to an empty partition.
 
  • Like
Reactions: TimothyR734
And that’s it, installed without any issue on a HFS+ disk, even if i thought apfs was required...
 

Attachments

  • image.jpg
    image.jpg
    3.1 MB · Views: 380
Could you post from your current Catalina Terminal the output of: diskutil list

Because you'd be the first to have installed Catalina working in HFS+.
I don’t understand, i only have one disk on my iMac but it appears like this, so i don’t know... maybe i just don’t remember...
 

Attachments

  • image.jpg
    image.jpg
    2.4 MB · Views: 370
  • Like
Reactions: TimothyR734
Hi - similar to a previous poster, I am getting the apfs_spec_read_wrapper error when trying to boot. Am on an Intel NUC with Clover, i5-8259u CPU with Iris 655 graphics. Any help would be appreciated. Thanks!
 

Attachments

  • IMG_20190615_000512.jpg
    IMG_20190615_000512.jpg
    1.6 MB · Views: 253
  • Like
Reactions: TimothyR734
Just a few small changes, this is coming from MacBook 4,1 though.

  • Obviously, I had to change AppleIntelGMAX3100 to use AppleVADriver instead of the AppleIntelGMAX3100VADriver, since it only had an i386 slice.
  • I would often compress the Dock icons so it would run smoother.
  • Disable Animations of course but I was working on trying to integrate cDock in my macOSE since it was the only known way to add some transparency back.
  • A few Quicktime plugins that I kept (which I don't know will work on Mojave and Catalina) gave me some success in video playback.
  • Used the NoSleep Extension to stop that annoying display issue. I was looking into changing the hibernate modes instead though.
  • Disable Beam Sync
Nothing special. Just a few little workarounds that I used in the Mavericks-El Capitan days since nobody could figure out get those beta frameworks to work.

These are some really good observations/actions. Could these suggestions be distilled down into a "VM Patcher" or "VM Performance Enhancer" script so as to make running macOS on a VM with lower resources more responsive?
[doublepost=1560557034][/doublepost]
After a significant effort, I've managed to get Catalina running (unstably) with Mojave's SkyLight.framework. And... still no acceleration. Unexpected.

I'll do some more tests. Not sure what's going on, since the GLDriver does load. I'm suspecting connection to changes in CoreDisplay and/or IOSurface... will report back.

Edit: I just got to a fully accelerated login screen you guys! It crashes 1-2 seconds later, but this is definitely doable. I'll be back soon (I hope)...

Your work is invaluable and frankly you're exactly the kind of person that would really be able to help the critically important Darling effort.
 
  • Like
Reactions: TimothyR734
[doublepost=1560558456][/doublepost]
Some people need to have patience if you have Catalina installed then you are lot further than most of us first is getting it to install for the rest of us then we tackle other issues


Nevertheless, you can sometimes answer my little question .... even after many hours my problem was not considered and answered .... when it comes to incidental sidecar, since the opinions almost overturn. Hackintosh is better than the old orig. Macs.
 
  • Like
Reactions: TimothyR734
Rastafabi's Catalina loader

READ THIS ENTIRE POST AND THE INCLUDED README FIRST!

It took me a while, but finally I managed to create a "Catalina loader", which enables you to install macOS 10.15 Catalina on unsupported Macs with compatible hardware. It's meant for Mac Pro 4,1 & 5,1 and iMac 2010/2011 systems, which have a Metal compatible GPU. A upgraded WiFi/Bluetooth card might be necessary to have OOB support. I have not yet looked into audio, though on my Mac Pro 4,1 it works OOB. The download includes an installation guide with additional details.
It is not meant for systems without a Metal GPU or with Core2 Duo (based) CPUs.

The loader is based on rEFInd and OpenCore, which spoofs the Mac to be a compatible model.
View attachment 842732

Download the Catalina loader.zip

————————————

Some might be reminded of my old Mavericks download enabler. ;)

————————————

Dual CPU Mac Pros also require to be running non x55xx CPUs to omit audio stuttering. Thanks @tsialex

————————————

Questions:

The Catalina Loader is confirmed to work with the first macOS Catalina developer beta installer (DP1).
No other installers have been tested and thus are not supported at the moment as those can potentially damage your hardware.

Properly not, as I think the installer will complain about not having a metal compatible GPU. Feel free to test and report.

Just about any should work. Find an old 512mb drive and you are good to go. Of course larger drives will work, too. BTW: You may also use SD-Cards, if your Mac can boot from those.

You can't. Just install it manually afterwards. There is now way to add anything, as this basically just enables you to run the legit unmodified Catalina installer.

I am very sorry. However there is nothing I can do. You have been warned (README) and proceeded at your own risk.

————————————

Updates:
  1. Fixed large file size (60mb), due to an oversight one may part.
  2. Removed experimental flag causing issues.

This is fantastic. One thing that the OpenCore devs have made clear is that graphics on boot (think Verbose Boot mode) are possible with OpenCore if we can either:

1) determine if there's any GOP protocol and if so, check if it's usable and Apple UI fails to show up (likely not the case since GPU is uninitialized, but worth a check). Or,

2) implement Option ROM loading driver based on EDK II, load it from OpenCore and then debug the use of EFI Boot Services/Runtime Services to see why it fails from the beginning. DumpUefiCalls drive for Clover can probably be extended/reused here. Or maybe

3) load CSM module (often called BIOSVideo). This could be a fair option.
 
[doublepost=1560558456][/doublepost]


Nevertheless, you can sometimes answer my little question .... even after many hours my problem was not considered and answered .... when it comes to incidental sidecar, since the opinions almost overturn. Hackintosh is better than the old orig. Macs.
I would f I could but I don't know what a Hackintosh is something new to me like clover never heard of it never heard of Dell,HP our Alienware I am a Mac person
 
  • Like
Reactions: Appleak
Anyone have any idea when the Public Beta will be coming out for Catalina?

I remember with High Sierra and Mojave, new beta updates we’re coming out every week.

And the public Beta ... if I remember correctly ... should be sometime in July if they’re sticking to the same schedule as Mojave.

Regardless, I’m still asking if anyone has any information
 
  • Like
Reactions: TimothyR734
Anyone have any idea when the Public Beta will be coming out for Catalina?

I remember with High Sierra and Mojave, new beta updates we’re coming out every week.

And the public Beta ... if I remember correctly ... should be sometime in July if they’re sticking to the same schedule as Mojave.

Regardless, I’m still asking if anyone has any information
its July the first public beta be out I'm guessing around the 4th of July :)
 
I never experienced these stalls on 3,1. Nor did I have to replace those kexts. Wondering what the difference is.

I noticed when there are stalls there are only three of them and it's acts like an array with

timeout[0] X number of seconds... does it three times always

For boot is

busy timeout[0] 240s 'IOUSBHostInterface' 'Device Manangement', 'Trackpad Boot', 'Actuator', 'Accelerometer'

so I get three of those.

Then on the next boot I get

busy timeout[0] 60s 'IOUSBHostInterface'

and sometimes I get after unplugging something my USB chain

busy timeout[0] 60s '...HIDDevice'

I should also point out I haven't been creating a prelinked Kernel. If I need to do it from Mojave, I can, I just got done doing new install of Mojave. I did a fresh installl for it on APFS.

I am also currently getting read to test the telemetry plugin from High Sierra. It seems not to barf on it, but I also want to see if there are any side affects.

A previous install my system clock was Locked into 3/26/1389 AP. Whatever that is!

None of the installs seem to know where you Mac is, this could be from WiFi and telemetry not working? I don't know. Just speculation.

So far I have everything working on my 3,1 except for the timeouts which is down to 3 minutes. I have had it skip them entirely before but it's not certain what is causing it to skip them.
 
I noticed when there are stalls there are only three of them and it's acts like an array with

timeout[0] X number of seconds... does it three times always

For boot is

busy timeout[0] 240s 'IOUSBHostInterface' 'Device Manangement', 'Trackpad Boot', 'Actuator', 'Accelerometer'

so I get three of those.

Then on the next boot I get

busy timeout[0] 60s 'IOUSBHostInterface'

and sometimes I get after unplugging something my USB chain

busy timeout[0] 60s '...HIDDevice'

I should also point out I haven't been creating a prelinked Kernel. If I need to do it from Mojave, I can, I just got done doing new install of Mojave. I did a fresh installl for it on APFS.

I am also currently getting read to test the telemetry plugin from High Sierra. It seems not to barf on it, but I also want to see if there are any side affects.

A previous install my system clock was Locked into 3/26/1389 AP. Whatever that is!

None of the installs seem to know where you Mac is, this could be from WiFi and telemetry not working? I don't know. Just speculation.

So far I have everything working on my 3,1 except for the timeouts which is down to 3 minutes. I have had it skip them entirely before but it's not certain what is causing it to skip them.
have you tried using the IOUSB kexts from HS
 
have you tried using the IOUSB kexts from HS
Not yet, mainly because USB is working. And this last install my Magic Track Pad 2 was recognized.

I am creating another clean install to test, taking baby steps to see its affects.

Yesterday, I have had things work smooth for 4 reboots then start kernel panicking and did not know what the deal was there after.

The USB Stall or Timeout error is a bugger as it can take anywhere from 3 x 60s to 3 x 240s to test. That time adds up to hours just on one issue. Luckily it always boots when it is done timing out three times.

I am running a little slow too.Not working at full speed. But this stuff does take my mind of my cold.
 
Last edited:
  • Like
Reactions: TimothyR734
I noticed when there are stalls there are only three of them and it's acts like an array with

timeout[0] X number of seconds... does it three times always

For boot is

busy timeout[0] 240s 'IOUSBHostInterface' 'Device Manangement', 'Trackpad Boot', 'Actuator', 'Accelerometer'

so I get three of those.

Then on the next boot I get

busy timeout[0] 60s 'IOUSBHostInterface'

and sometimes I get after unplugging something my USB chain

busy timeout[0] 60s '...HIDDevice'

I should also point out I haven't been creating a prelinked Kernel. If I need to do it from Mojave, I can, I just got done doing new install of Mojave. I did a fresh installl for it on APFS.

I am also currently getting read to test the telemetry plugin from High Sierra. It seems not to barf on it, but I also want to see if there are any side affects.

A previous install my system clock was Locked into 3/26/1389 AP. Whatever that is!

None of the installs seem to know where you Mac is, this could be from WiFi and telemetry not working? I don't know. Just speculation.

So far I have everything working on my 3,1 except for the timeouts which is down to 3 minutes. I have had it skip them entirely before but it's not certain what is causing it to skip them.
my image included a pre linked kernel built on a Catalina supported machine.
 
Thx for the updates, btw won't be a better solution to spoff the VMM flag?
I will look into it. Do not know if this functionality is currently available in OpenCore.

Right now the spoofed Mac is not fully complete on purpose. (Calling about this Mac wont show a difference apart from slightly off CPU clocks.) Right now I hope this will suffice to hinder firmware updates.
 
Your work is invaluable and frankly you're exactly the kind of person that would really be able to help the critically important Darling effort.
I don't have anywhere near the required coding skill for something like that, sorry. Perhaps ask @pkouame or @parrotgeek1.
[doublepost=1560569487][/doublepost]
my image included a pre linked kernel built on a Catalina supported machine.
The quote your message somehow attributed to me should be from @Starplayr.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.