Post not yet marked as solved
Hi Apple,
I have a MacBook pro 2020 32GB ram. When I try to use a double monitor extension, the "kernel_task" process consumes %70 CPU. How can I solve it?
Post not yet marked as solved
Hi,
is there any hardware diffs between M1 & M2, without the performances?
As the title suggests, will i be able to create/test apps for both intel & arm(M1&M2) in my m1 mac with the same code in xcode?
And How can i make an universal dmg without having an intel mac? Also, correct me if i'm wrong: does 'the rosetta swaps' hamper ssd life?
Thanks in advance.
Post not yet marked as solved
Hi,
I have an iMac Retina 5k, 27" 2017 w 3.8GHZ process and 64gb of memory with a 2t hard drive and iCloud. Since the move to Big Sur (Big Slow) finder hangs and gets spinning beachballs if I try to move a file or folder. I can do this on my other iCloud devices that are on Catalina 10.15.7 without issue.
I've rebooted in safe mode. I've remove all start programs. I've reinstalled Big Sur 11.2.3, I've run 1st aid on all drives and they are good.
Anyone have this issue and try all these things? Anyone have a fix. I'm out of ideas and I even chatted with support to see if they could help no go there and I'm dead in the water now.
Post not yet marked as solved
I have had Touch ID Key heating issues lately. The key got really really hot. So, I deleted my fingerprint and deactivated all Touch ID login options. Now, if I try to add a fingerprint again, the Mac won't allow me.
It says (translating from Italian):
"Failed
Registration with Touch ID impossible to complete.
Go back and retry"
And this goes on an on.
It was working flawlessly on beta 1, until suddenly, after 3 days of the Mac being in a bag, unplugged, I noticed the Touch ID key was getting really really hot. I hoped upgrading to beta 2 would solve the problem, which it didn't.
I also noticed, on beta 1, that deleting the fingerprint and unchecking all login options from Touch ID brought the key back to the usual temperature.
But now, I cannot add a fingerprint again.
I wonder if it is a known issue on the beta or not. I filed two feedback reports at Apple, but haven't heard anything.
Lastly, for completeness, I am on:
Mac OS 12.5 public beta 2
MacBook Pro M1 Pro 2021
Internal keyboard
no peripherals attached
The issue started suddenly on beta 1, but the initial installation of the beta didn't cause it for some weeks.
The "add a fingerprint" issue was both in beta 1 and now in beta 2.
Post not yet marked as solved
I'm using M1pro and have successfully installed Numpy with Accelerate following, and it really speedup my programs. I also ran np.test() to check the correctness and every test passed.
However, I can't install Scipy with Accelerate, since the official document said Accelerate has a LAPACK of too old version. I can't even find a scipy that can pass scipy.test(). I tried the codes below:
conda install numpy 'libblas=*=*accelerate'
conda install scipy
np.test() as fails, sp.test() can't even finish
conda install numpy 'libblas=*=*openblas'
conda install scipy
Both np.test() and sp.test() can finish, but with many failures. I believe the bugs are due to Conda.
pip install --no-binary :all: --no-use-pep517 numpy
pip install scipy
np.test() has no failure and went fast, sp.test() uses OpenBLAS and has 3 failures. This is the best version I have found.
So my question is: can we find a reliable version of scipy on M1? Considering the popularity of scipy, I think it's not a high-living expectation.
And a question for Apple: is there really a plan to upgrade the LAPACK in Accelerate?
Post not yet marked as solved
Panic(cpu 2 caller 0xffffff8014f6799f): userspace watchdog timeout: no successful checkins from WindowServer in 120 seconds
service: logd, total successful checkins since wake (130 seconds ago): 14, last successful checkin: 0 seconds ago
service: WindowServer, total successful checkins since wake (130 seconds ago): 2, last successful checkin: 120 seconds ago
service: remoted, total successful checkins since wake (130 seconds ago): 14, last successful checkin: 0 seconds ago
service: opendirectoryd, total successful checkins since wake (130 seconds ago): 14, last successful checkin: 0 seconds ago
Panicked task 0xffffff8b6b7dd700: 3 threads: pid 116: watchdogd
Backtrace (CPU 2), panicked thread: 0xffffff869ef04000, Frame : Return Address
0xffffffe5b73b3690 : 0xffffff8011a81c8d
0xffffffe5b73b36e0 : 0xffffff8011be1596
0xffffffe5b73b3720 : 0xffffff8011bd0963
0xffffffe5b73b3770 : 0xffffff8011a21a70
0xffffffe5b73b3790 : 0xffffff8011a8205d
0xffffffe5b73b38b0 : 0xffffff8011a81816
0xffffffe5b73b3910 : 0xffffff8012315223
0xffffffe5b73b3a00 : 0xffffff8014f6799f
0xffffffe5b73b3a10 : 0xffffff8014f675f2
0xffffffe5b73b3a30 : 0xffffff8014f66971
0xffffffe5b73b3b60 : 0xffffff8012283a8c
0xffffffe5b73b3cc0 : 0xffffff8011b872e6
0xffffffe5b73b3dd0 : 0xffffff8011a5c9ab
0xffffffe5b73b3e60 : 0xffffff8011a731f9
0xffffffe5b73b3ef0 : 0xffffff8011bb35aa
0xffffffe5b73b3fa0 : 0xffffff8011a22256
Kernel Extensions in backtrace:
com.apple.driver.watchdog(1.0)[D6F8B92D-3418-34BA-B42B-F553E0C44C29]@0xffffff8014f65000->
Post not yet marked as solved
Installation of tested & trusted 3rd party software fails during the verification process. "PKInformSystemPolicyInstallOperation failed with error:An error occurred while registering installation with Gatekeeper."
Working with a M1 Macbook Air, macos 12.4.
Anytime I open a new terminal window or just a new tab, it takes a really long time till I can type.
I have commented out my entire ~/.zshrc and when run
for i in $(seq 1 10); do /usr/bin/time $SHELL -i -c exit; done
directly in an open terminal window it says it finished in 0.1s.
So it must be something macos is doing before zsh is even starting.
PS: In the activity monitor I can only see a spike in kernel_task cpu usage when opening a new terminal
Post not yet marked as solved
Hello! Help please, after updating the system to Big Sur, my MacBook Pro 13 began to slow down, previously there were no such problems.
MacBook Pro (Retina, 13-inch, Early 2015)
2,7 GHz 2‑core processor Intel Core i5
8 GB 1867 MHz DDR3
Intel Iris Graphics 6100 1536 MB
Post not yet marked as solved
I like to do most of my text processing in TextEdit, but since updating to Big Sur, it has become much more unstable, freezing unexpectedly (spinning beach ball of death). Some days it may happen only once, but some days (like today) it happens every half hour or so. It feels like Windows in the 1990s, when you were always working under a sword of Damocles, saving every few seconds and just waiting for the drop...
I don't think there's a single thing I'm doing when it happens, but I've often noticed it happening right when I accidentally zoom the TextEdit window by pinching (something I never mean to do in TextEdit and which is mostly annoying, btw). But it also happens when I'm doing nothing but typing on a keyboard (also external). I also do tend to use an external display connected by HDMI, which I suspect even more.
Running 11.2.3 on MacBook Pro 13-inch 2020. I saved a recent crash report, if it helps.
Any ideas? Thank you in advance.
Post not yet marked as solved
Please can I get some help!
I plugged in my new Logitech Mx series anywhere 3 mouse into my new MacBook air and now all of a sudden I cannot click into folders on Google drive and I cannot click into any cells in my airtable application to input data.
I removed the mouse from the MacBook and my trackpad on the MacBook is doing the same thing. What setting would this Mx series mouse changed that I cannot click properly anymore from my trackpad and I've added a friend's magic mouse and it's doing the same thing.
Post not yet marked as solved
I need to modify my security policy of Disk, from the startup security utility, but when I try so to modify the options such as: Allow user management of kernel extensions from identified developers
or
Allow remote management of kernel extensions and automatic software updates
Whenever I click on one of or both of these I get the following pop up after doing my credentials error:
”The operation couldn’t be completed.
(com.apple.BootPolicy.updateTagError error 11.)”
my computer:
MacBook Pro m1, 13 inch, 500Gb disk, 8Gb ram
I have disk encryption disabled.
I’m running MacOS 11.1
Post not yet marked as solved
my macbook pro 2015 it has a issue of coming crackling and popping sound from macbook pro from two speakers
it is very iritated and i apply all things from them but it is not fix my macbook pro update is 12.1 montery pleaase help and fix this issues
Post not yet marked as solved
I keep getting this message and can't access word any longer.
EXC_CRASH (SIGABRT)
Post not yet marked as solved
I need to run engineering applications (CFD Analyses) and thus I need to be able to have access to LINUX. I hear that Boot Camp will not be an option on Apple silicon. So be specific, how am I going to get my work done with a machine that has Apple Silicon in it.
Post not yet marked as solved
By using NSWindowCollectionBehaviorCanJoinAllSpaces, I can make NSWindow show up on every already opened space, however, it won't show up on spaces that were added after app launch. How can I display NSWindow on spaces which were added after app launch? For example SideNotes app it can be shown on all spaces, on already opened ones before app launch and ones which were created after app launch.
Post not yet marked as solved
The trackpad works with tapping but does not click after the update.
Post not yet marked as solved
How can I pair the SmartCard to the SafeNet eToken 5100 after signing using Adobe DCPro?
Post not yet marked as solved
How can I agree to the license of Xcode
Post not yet marked as solved
About a year ago, I bought a portable 4k external monitor that I am able to run off one USB-C cable to allow myself to have a highly efficient setup. It was working flawlessly with Big Sur for the past year, taking advantage of 2-way power delivery and DisplayPort over USB-C with a single USB 3.1 Type-C cable. Please note, this monitor is specifically DisplayPort over USB-C (see: https://www.displayport.org/displayport-over-usb-c/) and not Lightning or a USB-C to DisplayPort adapter.
After upgrading to Monterey, the monitor gets detected as an audio device, but no signal is displayed (black screen & not in Display settings), no sound is played and moreover the OS gets laggy. It's apparent that the Macbook Pro is still able to supply power, but something is wrong with the display signal that is being sent that is causing the macbook to freak. Moreover, the monitor still works perfect on any other device that I connect to it. I've heard in some other places that the fundamental problem is that the DisplayPort 1.4 protocol is not implemented properly in Monterey and that you could circumvent the issue by changing your monitor's settings to use DisplayPort 1.2, but my monitor does not have options to change the DisplayPort version.
I've already done an SMC, NVRAM and PRAM reset to no avail.
This is a hugeeeee hinderance to my workflow so I would really appreciate an update on Apple's end to acknowledge that this is a problem and if there is a proper solution.