Jump to content

[pre-release] macOS Catalina


1,679 posts in this topic

Recommended Posts

3 hours ago, Roboter said:

So for anyone of you who want SIDECAR to work on a CustoMac with a dGPU, your iGPU has to work headless to be able to provide decoding functionality or otherwise Sidecar will error out.

 

Not only Sidecar: AirPlay also relies on a working iGPU.

  • Thanks 1
Link to comment
Share on other sites

7 hours ago, Roboter said:

I can't tell you that for sure, but this is not necessarily an error. I installed Catalina the second time around using verbose flag and I've seen several of these messages, it just takes a looooong time to pass through. Try the installation without verbose boot and see if the remaining time changes or the progress bar moves.

 

For the protocol, there was a case where I hit an error and this message appeared while the logs showed some infinite looped logs of something else. Next time I'd say you should attach a screenshot of the error as well so we can better differentiate. :)

Hi,

Thanks, yes it waits there for a long time, around 9 minutes and then goes on to install.

@Roboter and others,

I am finally able to install and after finishing the install and rebooting I can reach to the apple logo boot screen with the progress bar, where the cursor can be moved around for a bit but it stays there and does not reach the desk top.

So close and yet so far!!!

Any advise on how to proceed?

TIA

Edited by macq
Link to comment
Share on other sites

13 minutes ago, macq said:

Hi,

Thanks, yes it waits there for a long time, around 9 minutes and then goes on to install.

@Roboter and others,

I am finally able to install and after finishing the install and rebooting I can reach to the apple logo boot screen with the progress bar, where the cursor can be moved around for a bit but it stays there and does not reach the desk top.

So close and yet so far!!!

Any advise on how to proceed?

TIA

I had this bug a well, the screen way grey with another grey screen on it. I have a multi monitor setup. I unplugged one and retried the installation, this time it went through and you'll get to the setup UI. Before trying the whole process again, just reboot your system and try it with a single monitor plugged in (if you have a multi monitor setup).

  • Thanks 1
Link to comment
Share on other sites

1 hour ago, macq said:

Hi,

Thanks, yes it waits there for a long time, around 9 minutes and then goes on to install.

 @Roboter and others,

 I am finally able to install and after finishing the install and rebooting I can reach to the apple logo boot screen with the progress bar, where the cursor can be moved around for a bit but it stays there and does not reach the desk top.

 So close and yet so far!!!

Any advise on how to proceed?

TIA

Unfortunately I don't know what goes wrong. But in another word, does my patch work?

Edited by PMheart
Link to comment
Share on other sites

1 hour ago, PMheart said:

Unfortunately I don't know what goes wrong. But in another word, does my patch work?

Yes, the kernel patch via config.plist works,

Simply booting with clover does not work and I don't know if that is due to incorrect boot parameters or failure of lapic patch in clover itself.

Regards

Link to comment
Share on other sites

6 minutes ago, Joshua60 said:

Yes it does, at least for me

 

Thank you so much PMheart

That's what I said, as I have not used virtual smc and its plugins before, may be the kernel panics were due to incorrect boot parameters or incomplete kext and plugins.

thanks and regards

 

 

Link to comment
Share on other sites

4 minutes ago, macq said:

That's what I said, as I have not used virtual smc and its plugins before, may be the kernel panics were due to incorrect boot parameters or incomplete kext and plugins.

thanks and regards

 

 

What is your setup?

 

I ran latest Clover (previously latest beta build, now the stable catched up with necessary patches).

 

Here are my kexts that I compiled. I did that today so they are more or less fresh. Those go into 10.15 folder in clover, so I can keep 10.14 which is working just fine separate. Catalina is installed on a separate partition so I don't have to deal with issues restoring my full system if I mess it up. I also do have multiple `config.plist` files so I can test them. The config for Catalina is almost empty without any patches except for USB and Audio.

 

Again if you run into problems because you may have multiple monitors, unplug one and retry. Sometimes this can be very glitchy.

 

I installed Catalina before trying to make my iGPU work together with the dGPU. In that process I messed up my BIOS setting so my whole system blacked out on boot. I had to reset CMOS and reset all BIOS changes again. Interestingly, after doing so I could pass some Catalina related errors. Here you can write down all your BIOS settings and reset it, then try booting into your main macOS. Try to find the minimal required BIOS settings to boot.

 

Best of luck. 

 

10.15.zip

Link to comment
Share on other sites

21 minutes ago, Roboter said:

What is your setup?

 

I ran latest Clover (previously latest beta build, now the stable catched up with necessary patches).

 

Here are my kexts that I compiled. I did that today so they are more or less fresh. Those go into 10.15 folder in clover, so I can keep 10.14 which is working just fine separate. Catalina is installed on a separate partition so I don't have to deal with issues restoring my full system if I mess it up. I also do have multiple `config.plist` files so I can test them. The config for Catalina is almost empty without any patches except for USB and Audio.

 

Again if you run into problems because you may have multiple monitors, unplug one and retry. Sometimes this can be very glitchy.

 

I installed Catalina before trying to make my iGPU work together with the dGPU. In that process I messed up my BIOS setting so my whole system blacked out on boot. I had to reset CMOS and reset all BIOS changes again. Interestingly, after doing so I could pass some Catalina related errors. Here you can write down all your BIOS settings and reset it, then try booting into your main macOS. Try to find the minimal required BIOS settings to boot.

 

Best of luck. 

 

10.15.zip

Thanks, I already have got it booting as I said earlier,.

Still will go through your folder

Thanks for all the help.

Link to comment
Share on other sites

5 minutes ago, Moviemakergr said:

Works both .. iMac pro smbios here..

 

what are ur config of gpu ? do u use both IGPU and Vega or only vega ? and if u use IGPU what device id do u use for igpu ? XD ah and btw which imac ? i'm on imac pro

Link to comment
Share on other sites

All of my hardware devices are now working but some better than others.  Bluetooth works but not great - lots of crackling in my headphones that sounds like a poor connection, not an audio glitch.  But the worst is my trackpad -- the sensitivity is set too high and two-finger scrolling is often interpreted as a two-finger click (i.e. right mouse click).  That makes scrolling through the posts in this thread difficult at best.  Is there a way to adjust the sensitivity of the trackpad?  I'm using RehabMan's most recent version of VoodooPS2Controller and the VoodooI2CSynaptics.kext.

 

Edited by mnfesq
Link to comment
Share on other sites

27 minutes ago, Moviemakergr said:

I use latest lilu and WG with -lilubetall

iGPU is disable from bios but i have HAcceleration from Vega 64.

iMac pro 1.1

after disabling IGPU from bios,  h264 became unavailable  and  i tried to play show from HBO first 30-35 secs was playing (Promo then it stuck and its not playing the actual show)

 

can u show me ur EFI ? :S

Link to comment
Share on other sites

Wrong SMBIOS and setup. Use Radeon VII without IGPU and iMacPro1,1. Otherwise encoding will be done on the IGPU. Alternatively you can also disable IGPU while staying on iMac19,2, put Whatevergreen in your Kexts folder and use the boot-args shikigva=32 and shiki-id=Mac-7BA5B2D9E42DDD94. Should also fix your video issues.

Link to comment
Share on other sites

4 hours ago, macq said:

Yes, the kernel patch via config.plist works,

Simply booting with clover does not work and I don't know if that is due to incorrect boot parameters or failure of lapic patch in clover itself.

 Regards

It's expected as I haven't updated the source code yet, I have claimed the reason at

Let's wait for several new releases, and see how it goes. :)

For now please just apply this manually patch.

  • Like 2
Link to comment
Share on other sites

On 6/5/2019 at 10:25 AM, fabiosun said:

Hi @Balamut

take a look here:


_ml_init_max_cpus:
ffffff800047c090	pushq	%rbp
ffffff800047c091	movq	%rsp, %rbp
ffffff800047c094	pushq	%r14
ffffff800047c096	pushq	%rbx
ffffff800047c097	subq	$0x10, %rsp
ffffff800047c09b	pushfq
ffffff800047c09c	popq	%rbx
ffffff800047c09d	testl	$0x200, %ebx
ffffff800047c0a3	je	0xffffff800047c0a6
ffffff800047c0a5	cli
ffffff800047c0a6	movl	0x9d832c(%rip), %eax
ffffff800047c0ac	cmpl	$0x1, %eax
ffffff800047c0af	je	0xffffff800047c107
ffffff800047c0b1	leaq	-0x1(%rdi), %rcx
ffffff800047c0b5	cmpq	$0x3f, %rcx
ffffff800047c0b9	ja	0xffffff800047c0cd
ffffff800047c0bb	movl	_max_ncpus(%rip), %ecx
ffffff800047c0c1	cmpq	%rdi, %rcx
ffffff800047c0c4	cmovbel	%ecx, %edi
ffffff800047c0c7	movl	%edi, 0x8241db(%rip)
ffffff800047c0cd	cmpl	$0x2, %eax
ffffff800047c0d0	jne	0xffffff800047c0fd
ffffff800047c0d2	leaq	0x9d82ff(%rip), %r14
ffffff800047c0d9	movq	%r14, -0x18(%rbp)
ffffff800047c0dd	leaq	-0x18(%rbp), %rdi
ffffff800047c0e1	movl	$0x8, %esi
ffffff800047c0e6	callq	__global_eventq
ffffff800047c0eb	movq	%rax, %rdi
ffffff800047c0ee	movq	%r14, %rsi
ffffff800047c0f1	xorl	%edx, %edx
ffffff800047c0f3	movl	$0xffffffff, %ecx
ffffff800047c0f8	callq	_waitq_wakeup64_all
ffffff800047c0fd	movl	$0x1, 0x9d82d1(%rip)
ffffff800047c107	pushfq
ffffff800047c108	popq	%rax
ffffff800047c109	testl	$0x200, %ebx
ffffff800047c10f	jne	0xffffff800047c11b
ffffff800047c111	testl	$0x200, %eax
ffffff800047c116	je	0xffffff800047c139
ffffff800047c118	cli
ffffff800047c119	jmp	0xffffff800047c139
ffffff800047c11b	sti
ffffff800047c11c	nop
ffffff800047c11d	cmpl	$0x0, %gs:0x18
ffffff800047c126	jne	0xffffff800047c139
ffffff800047c128	movq	%gs:0x0, %rax
ffffff800047c131	testb	$0x4, 0x4c(%rax)
ffffff800047c135	je	0xffffff800047c139
ffffff800047c137	int	$0xff
ffffff800047c139	addq	$0x10, %rsp
ffffff800047c13d	popq	%rbx
ffffff800047c13e	popq	%r14
ffffff800047c140	popq	%rbp
ffffff800047c141	retq
ffffff800047c142	nopw	%cs:(%rax,%rax)
ffffff800047c14c	nopl	(%rax)

ffffff800047c0b5 cmpq $0x3f, %rcx

 

no good news 

 

 

 

Well I guess no 56/112 core hacks for us.

 

  • Like 1
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...