Jump to content

1,159 posts in this topic

Recommended Posts

Hi,

 

Any help with  kextd (240s) stalls:ACPICPU,

 

Iheve only lilu, virtualsmc, voodoops2 and realtekrl8111 kext in my kext folder.

Share this post


Link to post
Share on other sites
Advertisement
10 minutes ago, macq said:

Any help with  kextd (240s) stalls:ACPICPU,

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. :)

Share this post


Link to post
Share on other sites
5 hours ago, Sherlocks said:

 

thank you so much

here is log

  Reveal hidden contents

2019-06-06 10:03:00.970036+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) found com.apple.driver.AirPort.BrcmNIC
2019-06-06 10:03:00.971208+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) all patches are successfuly applied to com.apple.driver.AirPort.BrcmNIC
2019-06-06 10:03:00.971378+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) wowl disable patch is successfuly applied to com.apple.driver.AirPort.BrcmNIC
2019-06-06 10:03:00.971991+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) gIOCatalogue->startMatching(OSSymbol const*) successful
2019-06-06 10:03:00.972161+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) gIOCatalogue->startMatching(OSSymbol const*) successful
2019-06-06 10:03:00.972244+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) gIOCatalogue->startMatching(OSSymbol const*) successful
2019-06-06 10:03:00.976219+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) FakeBrcm::init(): FakeBrcm disabled
2019-06-06 10:03:00.976227+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) FakeBrcm::free()
2019-06-06 10:03:00.976262+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) probe is called, service name is AirPort_BrcmNIC, provider name is ARPT
2019-06-06 10:03:00.976268+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:   iokit @ (DBG) getOSData device-id has 43B1 value
2019-06-06 10:03:00.976272+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:   iokit @ (DBG) getOSData vendor-id has 14E4 value
2019-06-06 10:03:00.976329+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) PCIHookManager::hookProvider: hook is not required since vendor-id && device-id are the same
2019-06-06 10:03:00.976355+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) probe is finished with result success
2019-06-06 10:03:00.976392+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) probe is called, service name is AirPort_BrcmNIC, provider name is ARPT
2019-06-06 10:03:00.976397+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:   iokit @ (DBG) getOSData device-id has 43B1 value
2019-06-06 10:03:00.976401+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:   iokit @ (DBG) getOSData vendor-id has 14E4 value
2019-06-06 10:03:00.976467+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) PCIHookManager::hookProvider: hook is not required since vendor-id && device-id are the same
2019-06-06 10:03:00.976484+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) probe is finished with result success
2019-06-06 10:03:00.976498+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) start is called, service name is AirPort_BrcmNIC, provider name is ARPT
2019-06-06 10:03:00.976506+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) brcmfx-country in ioreg is set to #a
2019-06-06 10:03:00.976512+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:   iokit @ (DBG) getOSData device-id has 43B1 value
2019-06-06 10:03:00.976517+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:   iokit @ (DBG) getOSData vendor-id has 14E4 value
2019-06-06 10:03:00.976576+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) PCIHookManager::hookProvider: hook is not required since vendor-id && device-id are the same
2019-06-06 10:03:01.125032+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) siPmuFvcoPllreg2, original chip identificator = 4352
2019-06-06 10:03:01.125309+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) wlc_set_countrycode_rev2 is called, a3 = -1, country_code = US
2019-06-06 10:03:01.125314+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) country code is overrided in ioreg
2019-06-06 10:03:01.125432+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) country code is changed from US to #a, result = 0
2019-06-06 10:03:01.235185+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) newVendorString is called
2019-06-06 10:03:01.238621+0900  localhost kernel[0]: (kernel) AirportBrcmFixup:  BRCMFX @ (DBG) start is finished with result 1

 

Hi. How can I get that log? I already add -brcmfxdbg to boor-arg but don't how how to get it. Thanks!

Share this post


Link to post
Share on other sites
Posted (edited)
11 hours ago, lvs1974 said:

Can somebody test attached version of AirportBrcmFixup under 10.15?

Thank you in advance for any reports.

 

PS: to get logs please add -brcmfxdbg into boot-args

2.0.2 (DEBUG).zip

 DW-1560 works great with this version. Thank you @lvs1974

 

Bildschirmfoto 2019-06-06 um 07.58.04.png

2.0.2 (RELEASE).zip

Edited by anonymous writer

Share this post


Link to post
Share on other sites
57 minutes ago, PMheart said:

Hi, yes! I am extremely wondering if it works, thanks!

It’s working kernel lapic issue fixed. Tahnks :D

Share this post


Link to post
Share on other sites
8 minutes ago, kidooe said:

It’s working kernel lapic issue fixed. Tahnks :D

@kidooe

How did you make it work?

TIA

Share this post


Link to post
Share on other sites
8 hours ago, fusion71au said:

 

 

 

Just adding AirPortAtheros40.kext plugin kext from High Sierra doesn't work because it fails to link in the pre-linked kernel ---> need to also replace entire IO80211Family.kext with older version.

 

I used @parrotgeek1’s BCM4321fix ---> basically allows the IO80211Family.kext wifi driver from El Capitan to work in newer macOS eg High Sierra, Mojave, Catalina.  Therefore it supports all the deprecated wifi cards that lost support in newer macOS eg BCM94321, Atheros cards needing AirPortAtheros40.kext like AR9287, AR9285, AR9280 :thumbsup_anim:.

 

BCM4321fix.zip

 

Thanks for the solution. I will try it.

Best regards. :P:P

Share this post


Link to post
Share on other sites
6 hours ago, mnfesq said:

 

Whatevergreen has been updated to 1.3.0 and it avoids the problem you have (at least it did for me.). It has been posted several times already above (alone and as a part of the Lilu Plugins.)

I can confirm that it now no longer panics. I can enable `iGPU Multiple Monitor` in my bios and boot into macOS Catalina without issues. 

 

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.

 

I compiled latest Lilu, WhateverGreen, AppleALC and VirtualSMC in Mojave and they work great so far.

 

Image below is taken from the app called `VideoProc` (free trial is enough; Settings - Common - Hardware Acceleration Engine - Options - Press refresh buttons if needed)

 

2108053676_Decodingworks..png.28992fd4aa754e6f01e950b6cda31408.png

Share this post


Link to post
Share on other sites

Is it possible to run usb wifi adapters on Catalina? As far I know those apps are 32 bit... (the mediated and Ralink based ones)

Share this post


Link to post
Share on other sites
2 hours ago, macq said:

@kidooe

How did you make it work?

TIA

 

3 hours ago, kidooe said:

yes i check that option but still getting KP on boot when but boot fine with cpus=1 boot arg

 

now im trying this patch of your's

 

Please try this kernel patch for 10.15 Beta 1:

9E 00 00 74 0E 8B -> 9E 00 00 EB 22 8B

 

 

just apply this patch in your config.plist 

Share this post


Link to post
Share on other sites

Is it possible to run usb wifi adapters on Catalina? As far I know those apps are 32 bit... (the mediatek and Ralink based ones)

Share this post


Link to post
Share on other sites
7 hours ago, chris1111 said:

 

Working good here with BrcmBluethootInjector now only both kexts for Mojave and Catalina :)

Thanks a lot

Can you upload BrcmBluethootInjector please.

Share this post


Link to post
Share on other sites
3 hours ago, PMheart said:

Hi, yes! I am extremely wondering if it works, thanks!

@PMheart

Is there new patch for NVME (M2 device) to fix external icon (yellow icon) at 10.15 beta ?

previous one seems not working any more.

Share this post


Link to post
Share on other sites
36 minutes ago, jsl2000 said:

@PMheart

Is there new patch for NVME (M2 device) to fix external icon (yellow icon) at 10.15 beta ?

 previous one seems not working any more.

Hi,

 

If I remembered correctly, the binary patch stopped working as of certain release of 10.14, I guess the best way is to inject properties, details can be found at Pike's blog.

Share this post


Link to post
Share on other sites
45 minutes ago, SavageAUS said:

 Can you upload BrcmBluethootInjector please.

Here it is: 

 

Share this post


Link to post
Share on other sites
14 hours ago, WarDoc said:

new tv app wont play videos on a Hack but works on a real mac


Same:

 

<<<< VTVideoDecoderSelection >>>> VTSelectAndCreateVideoDecoderInstanceInternal: no video decoder found for 'qavc'

[12:52:45.431] VTSelectAndCreateVideoDecoderInstanceInternal signalled err=-12906 (err) (Video decoder not available) at 
/BuildRoot/Library/Caches/com.apple.xbs/Sources/CoreMedia_frameworks/CoreMedia-2469.2.4.4/Sources/VideoToolbox/VTVideoDecoderSelection.c:2752

[12:52:45.431] vtDecompressionDuctCreate signalled err=-12906 (err) (Could not select and open decoder instance) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/CoreMedia_frameworks/CoreMedia-2469.2.4.4/Sources/VideoToolbox/VTDecompressionSession.c:1653

[12:52:45.432] fpfs_createVideoRenderChain signalled err=-12167 (kFigCPEError_DecryptionNotAvailable) (Failed to build render pipeline when requiring hardware decoder for protected video track) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/CoreMedia/CoreMedia-2469.2.4.4/Prototypes/Player/FigPlayer_Stream.m:24518

<<<< FigStreamPlayer >>>> fpfs_StartTrackPlaying: [0x7fb554ff3a60|] <0x7fb55519b000|> Could not create render pipeline (-12167). Halting playback

 

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
Posted (edited)
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

Share this post


Link to post
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).

Share this post


Link to post
Share on other sites
Posted (edited)
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

Share this post


Link to post
Share on other sites
Posted (edited)

Clevo OK :thumbsup_anim:  mojave 10.14.6beta APFS --> Catalina 10.15.1beta :gathering:1724144506_Schermata2019-06-06alle17_06_17.thumb.png.3838e697cb1c47e5e632cef58ff454bc.png1497472224_Schermata2019-06-06alle17_12_18.png.a380c897edfbc6cef068a8eff79c8b9d.png

Edited by iCanaro

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By fantomas1
      This update:
      • Makes downloaded issues available in the My Magazines section of Apple News+, both online and offline
      • Adds all publications in Apple News+, including newspapers, to the catalog at the top of the News+ feed
      • Adds the ability to clear downloaded magazine issues in Apple News+ by selecting History > Clear > Clear All
      • Addresses an issue which prevents creation of a new Boot Camp partition on iMac and Mac mini with Fusion Drive
      • Resolves an issue that may cause a hang during a restart
      • Resolves a graphics issue that may occur when waking from sleep
      • Fixes an issue that may cause fullscreen video to appear black on Mac mini
      • Improves file sharing reliability over SMB
       
      macOS Mojave 10.14.6 (18G84)
       
      Update
      Combo

      View full article
    • By fantomas1
      This update:
      • Makes downloaded issues available in the My Magazines section of Apple News+, both online and offline
      • Adds all publications in Apple News+, including newspapers, to the catalog at the top of the News+ feed
      • Adds the ability to clear downloaded magazine issues in Apple News+ by selecting History > Clear > Clear All
      • Addresses an issue which prevents creation of a new Boot Camp partition on iMac and Mac mini with Fusion Drive
      • Resolves an issue that may cause a hang during a restart
      • Resolves a graphics issue that may occur when waking from sleep
      • Fixes an issue that may cause fullscreen video to appear black on Mac mini
      • Improves file sharing reliability over SMB
       
      macOS Mojave 10.14.6 (18G84)
       
      Update
      Combo
    • By fantomas1
      macOS Mojave 10.14.6 (18G84)
       
      Update
      Combo
    • By eliot6001
      I don't know whether my LAN device will work on MAC and Which version of mac but i still want to run MAC on my PC, Also i checked my CPU-GPU and it turned out that i can Run MAX High sierra but i realized that some people have trouble with Sound and Internet connection so Here's the NAME of my LAN device:
       
      PCI\VEN_10EC&DEV_8136&SUBSYS_012310EC&REV_05\4&45F2A70&0&00E1 as (LAN DEVICE took the name from device manager in  windows). 
      also from compatibleIds i got this:
      PCI\VEN_10EC&DEV_8136&REV_05
       
      Is it Supported on any version of macOS ?
    • By Aldaro
      I have been running macOS Mojave on my system for 3 months and everything was working pretty well.  After taking an update for clover, my entire system got wrecked, and I cannot even boot to an installation environment anymore (which I really need to do since I am starting back at square one).  I still have the old EFI folder backed up, but I know it'll only be a matter of time before Apple introduces an update that requires me to update Clover in order to work correctly.  I have tried all the available memory fixes, but none of them seem to work.  I was previously using the original osxaptiofix; so, I gave v2, and v3 a try, but to no success.  I read somewhere on the main discussion board for clover that AptioMemoryFix was no longer going to be supported and I therefor decided to skip over it (not to mention it isn't even available in newer clover installation packages).
       
      System specs:
      Motherboard: GIGABYTE Z390 M GAMING
      CPU Intel core i5 9600k @ stock 3.7GHz
      RAM 32GB DDR4 2667MHz
      GPU AMD Radeon RX 580 with 8GB of GDDR5
      SSD Intel 660p 512GB NVME
      NIC: Intel i210 10/100/1000 as it is natively supported in macOS
       
      I have been using the iMac 19,1 SMBIOs as I built this machine to match it as close as humanly possible.  As for my UEFI settings, I did the usual:
      Disabled Windows specific features and secure boot
      Enabled XHCI hand off
      Enabled Above 4G decoding
      Disabled onboard NIC since it is made irrelevant by my intel i210
       
      --INJECT KEXTS--
      FakeSMC
      Lilu
      WhateverGreen
      AppleALC
      USBInjectAll -- WITH PATCHED SSDT in /EFI/CLOVER/ACPI/patched
      Below are images of the errors I am receiving when trying to boot the macOS Mojave installer.
       
      with original osxaptiomemoryfix

       
      osxaptiofixv2

       
      osxaptiofixv3

       
      Anyway, if somebody can help me figure out what's going on, that'd be greatly appreciated.  My ultimate goal is to get an install with minimal clover patches as to be better prepared when the winds of change from Apple come roaring.
       
      p.s: I have also attached a copy of my EFI folder
       
       
      EFI.zip
×