Jump to content
533 posts in this topic

Recommended Posts

Posted (edited)
3 hours ago, iTTT said:

hello guys,

 

does AQC107 works on new beta?

 

thanks.

No, probably new patch is needed. Look appropriate topic https://www.insanelymac.com/forum/topic/330614-marvell-aquantia-10-gb-ethernet-support-thread/page/15/#elControls_2760169_menu

 

 

Update: This patch works https://www.insanelymac.com/forum/topic/330614-marvell-aquantia-10-gb-ethernet-support-thread/?do=findComment&comment=2760231

 

 

Edited by yapan4

Getting this kernel panic in the last phase of installation.  I used the latest kexts.  

 

IOPlatformPanicAction -> AppleSMC
panic(cpu 1 caller 0xffffff801087c9ad): userspace watchdog timeout: no successful checkins from opendirectoryd since load
service returned not alive with context : is_alive_func returned unhealthy : opendirectoryd initialization not completed, current stage: opening /Local/Default node (code: 0x6
service: logd, total successful checkins since load (120 seconds ago): 13, last successful checkin: 0 seconds ago
service: opendirectoryd, no successful checkins since load (120 seconds ago)

Panicked task 0xffffff8693776000: 4 threads: pid 44: watchdogd
Backtrace (CPU 1), panicked thread: 0xffffff86936df2c0, Frame : Return Address
0xffffffd084bcb6d0 : 0xffffff800d4b0dbd mach_kernel : _handle_debugger_trap + 0x41d
0xffffffd084bcb720 : 0xffffff800d6076f5 mach_kernel : _kdp_i386_trap + 0x145
0xffffffd084bcb760 : 0xffffff800d5f70e3 mach_kernel : _kernel_trap + 0x533
0xffffffd084bcb7b0 : 0xffffff800d450a7f mach_kernel : _return_from_trap + 0xff
0xffffffd084bcb7d0 : 0xffffff800d4b118d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffd084bcb8f0 : 0xffffff800d4b0946 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xffffffd084bcb950 : 0xffffff800dd1c0b6 mach_kernel : _panic_with_options + 0x5c
0xffffffd084bcb9c0 : 0xffffff801087c9ad com.apple.driver.watchdog : __ZN10IOWatchdog14userspacePanicEP8OSObjectPvP25IOExternalMethodArguments.cold.1 + 0x27
0xffffffd084bcb9d0 : 0xffffff801087c600 com.apple.driver.watchdog : __ZN10IOWatchdog35userspaceDisableUserspaceMonitoringEP8OSObjectPvP25IOExternalMethodArguments
0xffffffd084bcb9f0 : 0xffffff800dc938ce mach_kernel : __ZN12IOUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x1de
0xffffffd084bcba40 : 0xffffff801087b9bb com.apple.driver.watchdog : __ZN20IOWatchdogUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x7f
0xffffffd084bcbb70 : 0xffffff800dc9dcab mach_kernel : _is_io_connect_method + 0x3db
0xffffffd084bcbcd0 : 0xffffff800d5b1794 mach_kernel : _iokit_server_routine + 0x4e84
0xffffffd084bcbde0 : 0xffffff800d48c069 mach_kernel : _ipc_kmsg_send + 0x439
0xffffffd084bcbe70 : 0xffffff800d4a2f21 mach_kernel : _mach_msg_overwrite_trap + 0x221
0xffffffd084bcbef0 : 0xffffff800d5dc707 mach_kernel : _mach_call_munger64 + 0x267
0xffffffd084bcbfa0 : 0xffffff800d451266 mach_kernel : _hndl_mach_scall64 + 0x16
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[08806AC8-C0B9-3844-AE46-BC9CF76A9AA9]@0xffffff801087a000->0xffffff801087cfff

Process name corresponding to current thread (0xffffff86936df2c0): watchdogd
Boot args: -v -lilubetaall keepsyms=1 debug=0x100 alcid=12 vsmcgen=1

19 minutes ago, Hervé said:

HDMI audio works, yes.

 

Clover config is that of Big Sur and available here. Absolutely nothing differs. The only difference is that, since yesterday, I've updated Lilu, WEG and AppleALC kexts to those versions revised by PMHeart in order to avoid the beta boot args.

 

Where are these kexts, please?

Are them the ones from june 8th?

44 minutes ago, Donw35 said:

check your boot syntax, I had the same experience but -lilubetaall Brought it back. per @PMheart continue to use the boot flags for Lilu and WEG.

 

-v keepsyms=1 -lilubetaall -wegbeta

 

 

Is this answer for my post about sound? Thanks.

There is any solution for BrcmPatchRAM issues, I need BrcmBluetoothInjector and  BrcmFirmwareData kext, it currently isn't working. Temporarily I've solved deleting this kext from efi folder.

Monterey works surprisingly well in my hack considering it's a very early beta:

  • CPU and RX 580 scores are very similar to Big Sur
  • The system behaves very smoothly and with performance comparable to Big Sur
  • The apps i have tried so far work fine
  • As I have Fenvi T-919, Bluetooth and Wifi work fine.

A couple of things that don't work:

  • When choosing a desktop picture, we have to download it from the download icon but it will not download, only the Monterey-specific wallpapers (the colored ones) are enabled
  • System Preferences> Screens takes a few seconds to open, when it opens it works fine.

Note: I use BT speaker so I have not tried AppleALC which is giving problems to some users.

@chris1111

 

@Hervé says in an older post

"So, officially, it looks like it's Broadwell platforms minimum but Monterey would still support Haswell/Azul framebuffer for the moment. Very much like Ivy Bridge/HD4000 in Big Sur.

Edit: I stand corrected; Mac mini Late-2014 is full Haswell platform"

 

Your HP has Haswell right? What SMBIOS are you using?

This are the Macs Monterey capable:

iMac: Late 2015
Mac Pro: Late 2013
iMac Pro: 2017
Mac mini: Late 2014
MacBook Air: Early 2015
MacBook: Early 2016
MacBook Pro: Early 2015.

Posted (edited)
8 minutes ago, miliuco said:

@chris1111

 

@Hervé says in an older post

"So, officially, it looks like it's Broadwell platforms minimum but Monterey would still support Haswell/Azul framebuffer for the moment. Very much like Ivy Bridge/HD4000 in Big Sur.

Edit: I stand corrected; Mac mini Late-2014 is full Haswell platform"

 

Your HP has Haswell right? What SMBIOS are you using?

This are the Macs Monterey capable:

iMac: Late 2015
Mac Pro: Late 2013
iMac Pro: 2017
Mac mini: Late 2014
MacBook Air: Early 2015
MacBook: Early 2016
MacBook Pro: Early 2015.

Ok yea Mac mini Late-2014 is 4260U HD 5000 

I am not see any kext of HD 4600 on S/L/E of Monterey

My Prodesk 600 G1 Use a Geforce 710 capable, I have install Montery last night no issue

thanks

Edited by chris1111

Just installed Monterey on my Haswell/HD4400 Toshiba laptop. It's just as stated previously: all I had to do was changed SMBIOS to MBP11,4. The rest is just as per Big Sur's settings.

 

Tosh_R50B_Mon_12.0.jpg

 

NB: VGA output for HD4400 remains supported OOB! :-)

8 minutes ago, kushwavez said:

@chris1111 I have i5-4600U Haswell with HD 4400. MBP11,4 also Haswell and it is not dropped, still on support list. 

It is working natively without any issues.

Great thanks;)

6 hours ago, miliuco said:

I'm not sure but maybe FakePCIID.kext and FakePCIID_Intel_I225-V.kext should be adapted to Monterey as @PMheart has done with Acidanthera kexts.
The source code for FakePCIID.kext is found on @RehabMan 's Bitbucket but FakePCIID_Intel_I225-V.kext can't even find it as binary.

 

To send issues to Acidanthera I use the bugtracker. But I think this problem has nothing to do with them as it's not from OpenCore or related kexts.

https://github.com/acidanthera/bugtracker/issues

 

 

I want to send something to Dortania not acidanthera!

1 hour ago, Donw35 said:

Yes, hope it helps

 

Thanks.

I tried but no change.

And I always reset NVRAM after these changes to make effect.

 

My old flags were, and these works fine in Big Sur:

-v alcid=1 shikigva=128 watchdog=0 agdpmod=pikera -no_compat_check

The new one for the Monterrey is:

-v -alcbeta -lilubetaall -wegbeta shikigva=128 watchdog=0 agdpmod=pikera -no_compat_check

Also, as mentioned before, OC is 0.70 and the kexts are the ones from this post (June 8th).

39 minutes ago, 5T33Z0 said:

I want to send something to Dortania not acidanthera!

It can be a bit confusing.

Acidanthera is the group that makes OpenCore and related kexts that are considered Acidanthera projects.

Dortania is the central place for all information about OpenCore.

Both groups share many of their members.


For issues detected in OpenCore there is a bugtracker that is the one from Acidanthera whose link I put in my previous post.
https://github.com/acidanthera/bugtracker/issues


For issues detected in the Dortania guides there is another bugtracker.
https://github.com/dortania/bugtracker


I thought you wanted to send something related to OpenCore or kexts but if it is related to the guides then you can use the Dortania bugtracker.

Posted (edited)
13 minutes ago, miliuco said:

It can be a bit confusing.

Acidanthera is the group that makes OpenCore and related kexts that are considered Acidanthera projects.

Dortania is the central place for all information about OpenCore.

Both groups share many of their members.


For issues detected in OpenCore there is a bugtracker that is the one from Acidanthera whose link I put in my previous post.
https://github.com/acidanthera/bugtracker/issues


For issues detected in the Dortania guides there is another bugtracker.
https://github.com/dortania/bugtracker


I thought you wanted to send something related to OpenCore or kexts but if it is related to the guides then you can use the Dortania bugtracker.

 

I wanted to send soimething to Dortania since the Kernel Patch for Intel i225 Ethernet no longer works since BigSur 11.4. If it did work I wouldn't need the FakePCIID kexts to make it work. And maybe this would fix networking for 12.0 too, who knows. I've ssen the bugtracker site for Dortania before, but as I said, I don't know how it works, how to report something. Looks different from the usual way of reporting issues… that's why I asked.

Edited by 5T33Z0
7 minutes ago, 5T33Z0 said:

 

I wanted to send something to Dortania since the Kernel Patch for Intel i225 Ethernet no longer works since BigSur 11.4. If it did work I wouldn't need the FakePCIID kexts to make it work. And maybe this would fix networking for 12.0 too, who knows. I've ssen the bugtracker site for Dortania before, but as I said, I don't know how it works, how to report something. Looks different from the usual way of reporting issues… that's why I asked.

But Dortania maintains the guides and help texts and instructions. Acidanthera is the one who develops OpenCore and the kexts. I'm not sure what the kernel patch for Intel i225 Ethernet is made by them although the place where the patch is found is in the Dortania guide for Comet Lake so it is very likely that they are the creators.

They usually only respond to issues related to their projects.
I've posted some issues and the way to do it is this: create a GitHub account (if you don't already have one)> New issue> choose the appropriate forum (Bug in OpenCore or KEXTs, Bug in tools or applications, etc.)> you write title and content replacing the content that appears by default> Submit new issue.

 @miliuco I've cretaed an issue now since the guide is no longer correct anyways, since the patch doesn't work any more. He/they should know who's the author of this Kernel patch is and have him/them look into it to resolve it because I don't know how to write Kernel patches :D

Posted (edited)

Upgraded my 11.4 install without a hitch. I updated AppleALC, Lilu and VirtualSMC to the latest versions so I could boot without any additional beta flags.

 

One weird thing is that Monterey is now mounting all my NTFS partitions on the desktop. As if it's seeing them as external disks (turning off the option to show external disks on the desktop hides them). Yet Disk Utility shows them as all being internal. Right clicking on one and choosing Get Info shows the disk format as "Unknown (lifs)". Some have eject icons beside them in the Finder sidebar and some don't.

 

As for incompatibilities, some Audio Units are failing validation in Logic. I only have a few on this machine but Moog Model 15 is one of them.

Edited by Riley Freeman
31 minutes ago, mackyreddy said:

usb installer booted but showing images of mouse ? any help would be appreciated.

 

Your PS2 mouse/keyboard/trackpad are not likely being detected.  That may be a problem with kext injection or with your PS2 driver (I'm assuming VoodooPS2Controller.kext with the mouse, keyboard, trackpad and VoodooInput plugins.) It's probably somehow related to the prelinked kernel and kextcache.  Try using a USB mouse/keyboard for the easy workaround.

×
×
  • Create New...