Jump to content
3338 posts in this topic

Recommended Posts

19 hours ago, PoMpIs said:

solved the sleep problem in my Alder Lake by mapping the USBs, since then it works fine... (My b660 board has Asmedia 107x Hubs which MacOS doesn't like very much)

 

but in beta 2 it doesn't go to sleep on its own :(  .... it does if I put it to sleep manually...

End of quote

 

Thanks for the suggestion and I have mapped the Usb ports and that is working fine but did not solve the problem. The problem in my view is related to the Aquantia 113C. Whether you spoof it or use the quirk ForceAquantiaEthernet; this gives a problem with sleep. My system immediately wakes up again.

It has been solved by adding the AppleIntelI210Ethernet.kext to OpenCore and making the second Ethernet port on the ProArt Z690 Creator Wifi functional again. When I connect to the network with the Intel 2.5 G sleep is no longer interrupted. 

Edited by BarryBar
  • Like 2
11 hours ago, SavageAUS said:

Does anyone else experience strange behaviour with dark mode? Dark mode works great once logged in but my login screen is light mode.

I have tried to reset nvram, changed to light mode - reboot - dark mode - reboot to no avail.

 

You are right, the login screen is not 100% in dark mode 🙆‍♀️... I had not noticed because in beta two I can already have automatic login, but I have removed it and it is as you say 

  • Like 2
15 minutes ago, PoMpIs said:

@BarryBar and this only happens to you in beta2?

 

in my case in beta 2 I have the problem that it does not go to sleep automatically and I don't know how to solve it... if I manually go to sleep it works🤷‍♂️

Yes this is in beta 2. Beta 1 had better sleep function. Hope beta 3 will solve this.

  • Like 1
16 minutes ago, BarryBar said:

Yes this is in beta 2. Beta 1 had better sleep function. Hope beta 3 will solve this.

 

I just realized that updating to beta 2 changes my i225v network from "en0" to "en2😐 

 

SxMIxEu.png

 

I've cleared the network preferences and it's back to "en0"

 

/Library/Preferences/SystemConfiguration/coma.apple.network.identification.plist
/Library/Preferences/SystemConfiguration/NetworkInterfaces.plist
/Library/Preferences/SystemConfiguration/preferences.plist

 

AZ9QV7p.png


Maybe it will solve my automatic sleep problem 🤷‍♂️

Edited by PoMpIs
  • Like 1

Well, it turns out that in beta 2 my computer does not go to sleep because of this:

 

sleep                1 (sleep prevented by runningboardd, sharingd, powerd)

 

I have looked in sharing and indeed I had this activated:

 

s0fBPPj.png

 

I have deactivated it and now it does not go to sleep because of the following: :hysterical:

 

sleep                1 (sleep prevented by runningboardd) 

 

What is this?? 

 

 

  • Confused 1
8 minutes ago, Allan said:

WOW! 🤯

If you change it to sleep = 0, won't solve it?

 

 

I tried it, but I don't think it does anything...

 

It's that in beta 1 I don't have to do anything, it goes to sleep automatically without me intervening in any of this 🤷‍♂️

4 hours ago, PoMpIs said:

You are right, the login screen is not 100% in dark mode 🙆‍♀️... I had not noticed because in beta two I can already have automatic login, but I have removed it and it is as you say 

I don’t remember this issue in beta 1. Maybe future betas will resolve issue. 

  • Like 1
Guest ricoc90
9 minutes ago, SavageAUS said:

I don’t remember this issue in beta 1. Maybe future betas will resolve issue. 

I don’t remember this issue in beta 1. Maybe future betas will resolve issue. 

I don’t remember this issue in beta 1, maybe future releases will solve issue. 


I mean, you know what they say.... third time's a charm 😄

On 6/23/2022 at 12:06 PM, aben said:


I see. Well, the version of the kexts I provided above are specifically to address BT issues on macOS 13. They're not part of the master branch yet except Lilu. Please test and report if those replacements solves the BT issue. Thanks!

Aben, I have used your attached kexts and now my bluetooth is working. I can also see the iPhone in FaceTime, but unfortunately there's no video from the iPhone.

  • Like 3
4 hours ago, SavageAUS said:

I don’t remember this issue in beta 1. Maybe future betas will resolve issue. 

 

No, in beta 1 it's fine. 

 

they would have fixed a lot of things in beta 2, but along the way they have broken others 😔

@Allan  

 

The Apple people must have gone out for coffee... and I took the opportunity to fix the sleep 

 

p8rjAfl.png

 

😆 

 

It goes to sleep if I don't touch it in 4 minutes 

 

so I like it more 🥰 

 

The problem was "runningboardd" I don't know why but beta 2 on my computer has two "runningboardd" processes, one as root and another one without root user which is the one that doesn't let me automatically put the computer to sleep, I killed it and it works fine now

 

qXFmjhs.png

 

 

  • Like 3

@PoMpIs

I also have (sleep prevented by runningboardd) and ps -ax | grep runningboard shows the same output as yours but I doubt they are 2 processes, maybe is only 1 runningboardd and the second line is grep containing this word.

My system goes to sleep and wakes well. macOS 13 beta 2.

  • Like 1
10 minutes ago, miliuco said:

@PoMpIs

I also have (sleep prevented by runningboardd) and ps -ax | grep runningboard shows the same output as yours but I doubt they are 2 processes, maybe is only 1 runningboardd and the second line is grep containing this word.

My system goes to sleep and wakes well. macOS 13 beta 2.

 

No, in the capture I had already killed him, I did not capture before...

the strange thing is that once that duplicate process has been killed, when restarting it has no longer reappeared

 

bppssHR.png

 

[[[[para entendernos rápido tu y yo lo pongo en español, antes ya me salían dos procesos "runningboardd" en el monitor de actividad le di a forzar salida al que no era root, y nunca mas ha vuelto a aparecer, y ahora esto ya entra en reposo perfectamente... cosas raras de usar sistemas en fase beta 😥 ]]]] 

Edited by PoMpIs
3 hours ago, PoMpIs said:

The problem was "runningboardd" I don't know why but beta 2 on my computer has two "runningboardd" processes, one as root and another one without root user which is the one that doesn't let me automatically put the computer to sleep, I killed it and it works fine now

Nice!

 

After you kill the process it return back after a reboot/shutdown?

  • Like 1
3 hours ago, PoMpIs said:

@Allan  

 

The Apple people must have gone out for coffee... and I took the opportunity to fix the sleep 

 

p8rjAfl.png

 

😆

 

It goes to sleep if I don't touch it in 4 minutes 

 

so I like it more 🥰 

 

The problem was "runningboardd" I don't know why but beta 2 on my computer has two "runningboardd" processes, one as root and another one without root user which is the one that doesn't let me automatically put the computer to sleep, I killed it and it works fine now

 

qXFmjhs.png

 

 

How to delete this file?

  • Like 1
27 minutes ago, Allan said:

Nice!

 

After you kill the process it return back after a reboot/shutdown?

 

No, it hasn't come back anymore, now I only have one instance

 

2Zt4oVX.png

 

But what randomly gives me some other problem is "nsurlsessiond" if I don't kill the one that isn't loaded with my user, it doesn't go to sleep either and this one always comes back on every reboot

 

sDRjfaU.png

 

🤪 MacOS Ventura is going to drive me crazy 

 

3 minutes ago, bisdak4920 said:

How to delete this file?

 

I had two instances of runningboardd, one as root and another one that came out without a user... I killed the one that didn't have a user and it hasn't appeared again 🤷‍♂️

  • Like 1
  • Haha 1
3 minutes ago, PoMpIs said:

But what randomly gives me some other problem is "nsurlsessiond" if I don't kill the one that isn't loaded with my user, it doesn't go to sleep either and this one always comes back on every reboot

A loooong time ago, with Yosemite, I had the same problem. And was related to Safari, got fixed after updating it - Safari I mean

 

Now at Ventura, all of it is beta, so...😬

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