Jump to content

[pre-release] macOS Mojave

fantomas

By fantomas,
in New Releases and Updates

 Share
2,429 posts in this topic

Recommended Posts

Badruzeus
Badruzeus
Posted
Posted (edited)
56 minutes ago, fantomas1 said:

 

Unfortunately it didn't work. In fact my HD6770 is just a HD5770 rebranded so it does not even need more Device-ID injections that it needs (FakeID is plenty enough).  The same for my HD4830. Thanks anyway. ;)

Are AMD*.kext loaded? Uhmmmb, how if using IOAcceleratorFamily2.kext from 10.12/10.13?

 

#EDIT: Also IOGraphics* IOPCIFamily*.kext.

Edited by Badruzeus
Link to comment
Share on other sites
Cyberdevs
Cyberdevs
Posted
Posted
44 minutes ago, Badruzeus said:

Are AMD*.kext loaded? Uhmmmb, how if using IOAcceleratorFamily2.kext from 10.12/10.13?

 

#EDIT: Also IOGraphics* IOPCIFamily*.kext.

On my rig with those kext replacements the GPU is working but without acceleration.

These are the kext I have replaced so far and the results is the same (no acceleration)

Spoiler

 

AMD8000Controller.kext

AMDFramebuffer.kext

AMDLegacyFramebuffer.kext

AMDLegacySupport.kext

AMDRadeonX4000.kext

AMDRadeonX4000HWServices.kext

AMDSupport.kext

IOAccelerator2D.plugin

IOAcceleratorFamily2.kext

 

 

  • Thanks 1
Link to comment
Share on other sites
fantomas
fantomas
Posted
  • Author
Posted
1 hour ago, Badruzeus said:

Are AMD*.kext loaded? Uhmmmb, how if using IOAcceleratorFamily2.kext from 10.12/10.13?

 

#EDIT: Also IOGraphics* IOPCIFamily*.kext.

 

Yup, all kexts are loaded and already tried with IOAcceleratorFamily2.kext from 10.13, as I explained here and here

 

I even tried with my DSDT but still nothing. It shows the full RAM but no QE/CI enabled. The funny thing is that I'm able to use Lilu's plugin NightShiftUnlocker, while it is not feasible if I have no QE/CI. So I guess I'm having just QE (which allows me to use it) but no CI.

  • Like 2
Link to comment
Share on other sites
Badruzeus
Badruzeus
Posted
Posted
22 minutes ago, fusion71au said:

He's just posted a newer/simpler patched GeForceTesla.kext that also seems to work well (attached to post#2529 in macrumors thread :thumbsup_anim:)

I give up with my MacBook4,1.. got no succeeded Mojave install, C2D Penryn T8300, 64-bit not capable GMA X3100 graphics, and.. too big 2 x 1GB DDR2 RAM #LoL :hysterical: Now installing Win7 32-bit on real mac (boot with rEFInd), but Mojave on my Asus laptop.. what a funny!

  • Haha 3
Link to comment
Share on other sites
nmano
nmano
Posted
Posted

Without SSE4 and SSE4.1

This system only worked 10.11.4

Intel Xeon X5365

Any idea to work 10.14?:cry:

x86info v1.31pre
Found 8 identical CPUs
Family: 6 Model: 15 Stepping: 11
Type: 0 (Original OEM)
CPU Model (x86info's best guess): Core 2 Quad 
Processor name string (BIOS programmed): Intel(R) Xeon(R) CPU           X5365  @ 3.00GHz

eax in: 0x00000000, eax = 0000000a ebx = 756e6547 ecx = 6c65746e edx = 49656e69
eax in: 0x00000001, eax = 000006fb ebx = 01040800 ecx = 0004e3bd edx = bfebfbff
eax in: 0x00000002, eax = 05b0b101 ebx = 005657f0 ecx = 00000000 edx = 2cb43049
eax in: 0x00000003, eax = 00000000 ebx = 00000000 ecx = 00000000 edx = 00000000
eax in: 0x00000004, eax = 0c000121 ebx = 01c0003f ecx = 0000003f edx = 00000001
eax in: 0x00000005, eax = 00000040 ebx = 00000040 ecx = 00000003 edx = 00002220
eax in: 0x00000006, eax = 00000001 ebx = 00000002 ecx = 00000001 edx = 00000000
eax in: 0x00000007, eax = 00000000 ebx = 00000000 ecx = 00000000 edx = 00000000
eax in: 0x00000008, eax = 00000400 ebx = 00000000 ecx = 00000000 edx = 00000000
eax in: 0x00000009, eax = 00000000 ebx = 00000000 ecx = 00000000 edx = 00000000
eax in: 0x0000000a, eax = 07280202 ebx = 00000000 ecx = 00000000 edx = 00000503

eax in: 0x80000000, eax = 80000008 ebx = 00000000 ecx = 00000000 edx = 00000000
eax in: 0x80000001, eax = 00000000 ebx = 00000000 ecx = 00000001 edx = 20100000
eax in: 0x80000002, eax = 65746e49 ebx = 2952286c ecx = 6f655820 edx = 2952286e
eax in: 0x80000003, eax = 55504320 ebx = 20202020 ecx = 20202020 edx = 58202020
eax in: 0x80000004, eax = 35363335 ebx = 20402020 ecx = 30302e33 edx = 007a4847
eax in: 0x80000005, eax = 00000000 ebx = 00000000 ecx = 00000000 edx = 00000000
eax in: 0x80000006, eax = 00000000 ebx = 00000000 ecx = 10008040 edx = 00000000
eax in: 0x80000007, eax = 00000000 ebx = 00000000 ecx = 00000000 edx = 00000000
eax in: 0x80000008, eax = 00003026 ebx = 00000000 ecx = 00000000 edx = 00000000

Cache info
 L1 Instruction cache: 32KB, 8-way associative. 64 byte line size.
 L1 Data cache: 32KB, 8-way associative. 64 byte line size.
 L2 cache: 4MB, 16-way associative. 64 byte line size.
TLB info
 Instruction TLB: 4x 4MB page entries, or 8x 2MB pages entries, 4-way associative
 Instruction TLB: 4K pages, 4-way associative, 128 entries.
 Data TLB: 4MB pages, 4-way associative, 32 entries
 Data TLB0: 4KB pages, 4-way associative, 16 entries
 Data TLB0: 4MB pages, 4-way associative, 16 entries
 Data TLB1: 4KB pages, 4-way associative, 256 entries
 64 byte prefetching.
Feature flags:
 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflsh ds acpi mmx fxsr sse sse2 ss ht tm pbe sse3 dtes64 monitor ds-cpl vmx est tm2 ssse3 cx16 xTPR pdcm dca
Extended feature flags:
 xd em64t lahf_lm dts
Long NOPs supported: yes

Address sizes : 38 bits physical, 48 bits virtual
3.00GHz processor (estimate).

Total processor threads: 8
This system has 1 eight-core processor running at an estimated 3.00GHz

 

Screen Shot 2018-07-13 at 1.19.57 PM.png

Link to comment
Share on other sites
fantomas
fantomas
Posted
  • Author
Posted

@nmano

 

If your CPU does not boot on 10.12, then why you want to bother with 10.14?  :P

 

Anyway, you still can check on AMD Development Kernel patch forum, they already bypassed Sierra/HSierra SSE4/4,1 check, so you should be able to boot Sierra/HSierra with that patched kernel.

 

Or, check the 'Core2Duo/Quad on Mojave' method and see if you have such a file on ElCapitan and try to rollback it in Sierrra/HSierra/Mojave. No guarantee it will work or blow up your PC  :lol:but that's what we call a hackint0sh, right?   ;)

  • Like 1
Link to comment
Share on other sites
nmano
nmano
Posted
Posted
13 minutes ago, fantomas1 said:

@nmano

 

If your CPU does not boot on 10.12, then why you want to bother with 10.14?  :P

 

Anyway, you still can check on AMD Development Kernel patch forum, they already bypassed Sierra/HSierra SSE4/4,1 check, so you should be able to boot Sierra/HSierra with that patched kernel.

 

Or, check the 'Core2Duo/Quad on Mojave' method and see if you have such a file on ElCapitan and try to rollback it in Sierrra/HSierra/Mojave. No guarantee it will work or blow up your PC  :lol:but that's what we call a hackint0sh, right?   ;)

@fantomas1

Thank you 

I will try HSierra with pathed AMD kernel.

I test rollback 10.11.4 com.apple.telemetry.plugin  to 10.14 thats not work.

  • Like 1
Link to comment
Share on other sites
Badruzeus
Badruzeus
Posted
Posted
2 hours ago, macq said:

I have attempted the above method and my kext load but no graphics acceleration in Mojave .

Any help on this front my, specs are in sig. and I have a gt 320m.

I had accélération once but lost it at next boot and now I cannot get it at all.

Did you install it using Kext Utility.app or which method used?

Try running this after kexts are installed:

Spoiler 

sudo rm -f /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache && sudo touch /System/Library/Extensions && sudo kextcache -u / && sudo update_dyld_shared_cache -force

 

 

  • Like 2
Link to comment
Share on other sites
Pavo
Pavo
Posted
Posted

Anyone else having issues with full screen recording using the new capture/recording feature (CMD+Shift+5)? I can record sections of the screen no issues but it will not record when I select the entire screen.

Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted (edited)
5 minutes ago, Pavo said:

Anyone else having issues with full screen recording using the new capture/recording feature (CMD+Shift+5)? I can record sections of the screen no issues but it will not record when I select the entire screen.

You can try Capture.app

its Built in interactive toolbar in interactive mode

you wil see more option with the toolbar

Edited by chris1111
Link to comment
Share on other sites
Cyberdevs
Cyberdevs
Posted
Posted (edited)
37 minutes ago, Pavo said:

Anyone else having issues with full screen recording using the new capture/recording feature (CMD+Shift+5)? I can record sections of the screen no issues but it will not record when I select the entire screen.

No man it's all good here.

 

Edited by Cyberdevs
Link to comment
Share on other sites
Irish_Man
Irish_Man
Posted
Posted (edited)
2 hours ago, Pavo said:
Anyone else having issues with full screen recording using the new capture/recording feature (CMD+Shift+5)? I can record sections of the screen no issues but it will not record when I select the entire screen.

 


Not working for me. Full screen or not.

 


 

 

Edited by dzontra
Link to comment
Share on other sites
Cyberdevs
Cyberdevs
Posted
Posted (edited)
10 minutes ago, dzontra said:

Is there a way to check?

Yes you can use MacX Video Converter Pro to check and see if it's active not see this post 

 

Addition:

Here's the link to the official web site for MacX Video Converter Pro you can use it in demo mode just to see if the Hardware Encoding Support is on or off.

Edited by Cyberdevs
Link to comment
Share on other sites
Cyberdevs
Cyberdevs
Posted
Posted
1 minute ago, dzontra said:

O yeah, I forgot about that :)

 

It is active.

Are you using any kexts to activate the the iGPU and dGPU? (IntelGraphicsFixUp or WhateverGreen) or you just use clover's graphics related injections?

Link to comment
Share on other sites
Irish_Man
Irish_Man
Posted
Posted (edited)
14 minutes ago, Cyberdevs said:

Are you using any kexts to activate the the iGPU and dGPU? (IntelGraphicsFixUp or WhateverGreen) or you just use clover's graphics related injections?

 

Yeah, I'm using IntelGraphicsFixup.kext (v.1.2.7). Not sure that I need it.

Edited by dzontra
Link to comment
Share on other sites
Cyberdevs
Cyberdevs
Posted
Posted
Just now, dzontra said:

Yeah, I'm using IntelGraphicsFixUp

You can remove it and test without it, I don't inject anything related to my iGPU (and even if I do) it works without IntelGraphicsFixUp.kext anyway.

 

Please use a USB disk for these tests just in case :D copy the EFI folder on the EFI partition and remove the intelgraphicsfixup kext with any intel related injections and boot from the USB disk and see if that helps with the issue. ( I hope it does ;) )

  • Thanks 1
Link to comment
Share on other sites
Irish_Man
Irish_Man
Posted
Posted (edited)
11 minutes ago, Cyberdevs said:

You can remove it and test without it, I don't inject anything related to my iGPU (and even if I do) it works without IntelGraphicsFixUp.kext anyway.

 

Please use a USB disk for these tests just in case :D copy the EFI folder on the EFI partition and remove the intelgraphicsfixup kext with any intel related injections and boot from the USB disk and see if that helps with the issue. ( I hope it does ;) )

Removed the kext but same result.

Hardware Encoding still active. I've tried to disable igpu from BIOS but same thing.

Edited by dzontra
Link to comment
Share on other sites
Cyberdevs
Cyberdevs
Posted
Posted
5 minutes ago, dzontra said:

Removed the kext but same result.

Hardware Encoding still active. I've tried to disable igpu from BIOS but same thing.

Hardware Encoding Should be active if you disable it, it makes things worse so iGPU must be enabled for hardware encoding to work properly, but according to your last post regarding the issues with google maps I think there must be something wrong with the EFI folder or the config.plist that you are using. Are you using a Patched DSDT?

 

  • Thanks 1
Link to comment
Share on other sites
Irish_Man
Irish_Man
Posted
Posted
2 minutes ago, Cyberdevs said:

Hardware Encoding Should be active if you disable it, it makes things worse so iGPU must be enabled for hardware encoding to work properly, but according to your last post regarding the issues with google maps I think there must be something wrong with the EFI folder or the config.plist that you are using. Are you using a Patched DSDT?

 

 

Here is my EFI folder if you have time to check.

 

EFI.zip

  • Like 1
Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...