Jump to content

[pre-release] macOS Mojave


2,429 posts in this topic

Recommended Posts

9 minutes ago, corint1 said:

all I found about mojave ... many versions ... none work for me ... no video accelaration( use driver for hs 13.5)  ... no sound ...something missing but I dont know what ...

 

As I said... Post your Clover folder so we can see where you're at. :)

Sound is a common problem and considering your motherboard, you MIGHT be able to get sound from it using AppleALC & Lilu kexts (we'll talk about that when the time comes).

 

Video acceleration is also common issue and known issue, since there is no Nvidia driver for Mojave yet.

 

Your motherboard is fantastic. Which is to say you're gonna love making a hackintosh out of it. And when I say "love", I mean pull your hair not knowing what the hell to do to get it to work. :) But otherwise, it's a pretty damn awesome motherboard.

 

It's gonna be a challenge to make it work.

Send me a PM, if you want. So we don't spam everyone on the forum.

Edited by arsradu
  • Like 1
Link to comment
Share on other sites

15 minutes ago, Cyberdevs said:

Well I guess apple is going to completely ditch the OpenCL and replace it with Metal and that's why all the AMD GPU generations prior to 7000 series are not supported anymore

 

I have no problem with that - But they could keep the support for old GPU/CPU and ONLY allow new features for NEW GPU/CPU.

 

But truly speaking... in the current Mojave state, could you really agree that it needs CPU SSE 4,2 or GPU > 7000 series as minimum recommendation??? Naaaaah.  :thumbsdown_anim:

  • Like 1
Link to comment
Share on other sites

23 minutes ago, arsradu said:

Guys, the ones of you having issues opening certain photos with the first Beta, do you still have that issue? Cause I do. I was hoping Apple would fix it. But...well, they didn't seem to. And it's kind of annoying.

 

Apparently it doesn't occur with HEIC files (live photos) and screenshots taken on the Mac. It does with screenshots received on iMessage for example and regular camera photos. Cannot be opened either with Quick Look (endless loop) or Preview app (app becomes unresponsive).

Guys, the ones of you having issues opening certain photos with the first Beta, do you still have that issue? Cause I do. I was hoping Apple would fix it. But...well, they didn't seem to. And it's kind of annoying.

 

Apparently it doesn't occur with HEIC files (live photos) and screenshots taken on the Mac. It does with screenshots received on iMessage for example and regular camera photos. I have no idea why... The photos cannot be opened either with Quick Look (endless loop) or Preview app (app becomes unresponsive).

I don't seem to have that issue. I need to double check some of my old photos to make sure.

  • Like 1
Link to comment
Share on other sites

1 minute ago, Cyberdevs said:

I don't seem to have that issue. I need to double check some of my old photos to make sure.

 

Thanks! Did you have this issue before? Cause it's important that we test the same photos, before and after the update. Otherwise, results might differ. Especially since this is a weird issue, and seems to be dependent on the file itself...

Link to comment
Share on other sites

14 minutes ago, fantomas1 said:

 

I have no problem with that - But they could keep the support for old GPU/CPU and ONLY allow new features for NEW GPU/CPU.

 

But truly speaking... in the current Mojave state, could you really agree that it needs CPU SSE 4,2 or GPU > 7000 series as minimum recommendation??? Naaaaah.  :thumbsdown_anim:

 

You are correct and I totally agree with you about supporting older Macs. BUT we are talking about Apple! They do whatever they want whenever they want! they don't really care about the end-user they just care about the sales. I know for a fact that all the discontinued (or better to say unsupported) Macs are still capable for professional use. But "Hey! who cares we are building a "Campus" and we neeeeeeed money, a lot of it so let's force people to buy new Macs so we can make more profit! " :dev:

 

11 minutes ago, arsradu said:

 

Thanks! Did you have this issue before? Cause it's important that we test the same photos, before and after the update. Otherwise, results might differ. Especially since this is a weird issue, and seems to be dependent on the file itself...

If I remember correctly I came across this issue on one of the High Sierra beta's but I don't remember which version was it and it got fixed in the next release.

 

About testing the same photos how you propose we do that?

Edited by Cyberdevs
Link to comment
Share on other sites

15 minutes ago, fantomas1 said:

 

I have no problem with that - But they could keep the support for old GPU/CPU and ONLY allow new features for NEW GPU/CPU.

 

But truly speaking... in the current Mojave state, could you really agree that it needs CPU SSE 4,2 or GPU > 7000 series as minimum recommendation??? Naaaaah.  :thumbsdown_anim:

No. At some point people need to suck it up and upgrade. AMD 7000 series is almost 7 years old.

Link to comment
Share on other sites

7 minutes ago, Cyberdevs said:

 

You are correct and I totally agree with you about supporting older Macs. BUT we are talking about Apple! They do whatever they want whenever they want! they don't really care about the end-user they just care about the sales. I know for a fact that all the discontinued (or better to say unsupported) Macs are still capable for professional use. But "Hey! who cares we are building a "Campus" and we neeeeeeed money, a lot of it so let's force people to buy new Macs so we can make more profit! " :dev:

 

If I remember correctly I came across this issue on one of the High Sierra beta's but I don't remember which version was it and it got fixed in the next release.

 

About testing the same photos how you propose we do that?

 

I mean...we test each one of us individually, the same photos. :)) Not...sharing photos. Although that could work, too, I guess, with non private photos.

 

For example the wallpaper below cannot be opened on my hack.

0f85fc483dd5e85460ee4d685a86edbb.jpg

  • Haha 2
Link to comment
Share on other sites

3 minutes ago, arsradu said:

 

I mean...we test each one of us individually, the same photos. :)) Not...sharing photos. Although that could work, too, I guess, with non private photos.

 

For example the wallpaper below cannot be opened on my hack.

it opens normally on mine in QuickLook and the PreviewTry this photo 

Spoiler


Screen Shot 2018-06-20 at 12.16.39 AM.png

Screen Shot 2018-06-14 at 6.05.12 AM.png

 

 

7 minutes ago, zxv said:

No. At some point people need to suck it up and upgrade. AMD 7000 series is almost 7 years old.

IMHO there is a big difference between forcing someone to do something or they doing it by choice.

However technology almost forces people to upgrade but still I'd rather to have a choice rather than being forced to do it.

Edited by Cyberdevs
  • Like 1
Link to comment
Share on other sites

4 minutes ago, Cyberdevs said:

IMHO there is a big difference between forcing someone to do something or they doing it by choice.

However technology almost forces people to upgrade but still I'd rather to have a choice rather than being forced to do it.

It burns through more development resources than people realize to try and continually support legacy hardware, and delays rollouts of newer features.

 

It's nice to not have to upgrade every couple years (like we used to). But nowadays people get lazy and self-entitled thinking they deserve to be able to run modern software on antiques.

Link to comment
Share on other sites

12 minutes ago, zxv said:

But nowadays people get lazy and self-entitled thinking they deserve to be able to run modern software on antiques.

 

:thumbsdown_anim:

 

What being lazy has to do with running a modern software on an old material??? You really didn't understand what the purpose of hackintosh is. And what's meaning a modern software? Mojave??? C'mon dude, just be serious more than 5sec.

 

Like I said above, my old Core2Duo config works perfectly well under 10.13.6, but no longer under 10.14. How in the hell Mojave could be more 'modern software' than HS???  :hammer: 

 

Because of Dark Mode???  :hysterical:   Ok, I got it.

  • Like 2
  • Haha 4
Link to comment
Share on other sites

On 6/5/2018 at 1:43 PM, PMheart said:

Seemingly there has not been a proper USB port limit patch? Here you go. :)

 


kext: com.apple.driver.usb.AppleUSBXHCI
find: 83 FB 0F 0F 83 09 05 00 00
repl: 83 FB 0F 90 90 90 90 90 90

 

 

new find 83 FB 0F 0F 83 03 05 00 00

 

Fred

Edited by FredWst
  • Like 5
  • Thanks 4
Link to comment
Share on other sites

38 minutes ago, Cyberdevs said:

it opens normally on mine in QuickLook and the PreviewTry this photo 

  Reveal hidden contents

 

 

 

Well...this is really weird...

 

Initially, your screenshots didn't work.

Rebooted. Cleared kernelcache (though, if I'm thinking about it right now, that part might not have been necessary).

After the reboot, the screenshots you provided above, worked!

I then tried to open the initial wallpaper that I posted above. And that one STILL didn't work.

So I went back to your screenshots. And now, those don't work either!

WHAT THE...FORK!?

 

Update: yep, the issue is fixed after a reboot... I mean, the one with the screenshots. The initial wallpaper still doesn't work.

Edited by arsradu
Link to comment
Share on other sites

6 minutes ago, fabiosun said:

hi Fred

not working here

 

find <83fb0f0f 83030500>

replace <83fbXX0f 83030500> in my case XX = 1A. (XX number of port OC)

 

Works fine

 

Fred

Edited by FredWst
  • Like 3
  • Thanks 1
Link to comment
Share on other sites

27 minutes ago, fantomas1 said:

It's new find, not new replace!!!  :P

Yup I know but still didn't work. I'm double checking my configs to see where did I go wrong :D

 

I guess I edited the wrong config. Now it's working :D I had three EFI partitions mounted and I must have edited the wrong config. :hysterical:

Edited by Cyberdevs
  • Haha 2
Link to comment
Share on other sites

5 minutes ago, FredWst said:

 

find <83fb0f0f 83030500>

replace <83fbXX0f 83030500> in my case XX = 1A. (XX number of port OC)

 

Works fine

 

Fred

Ok

it is working :)

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...