Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
I do have a "Magic Mouse 2" and encountered no issues in Mojave with MB7,1 .

edit:
And it's automatically detected and bluetooth paired, I have only to turn on the mouse and nothing else.
All the Magic Mouse features are in Mouse PrefPane also with the "video Mouse examples" playing back.
Same here, I tested it with a magic mouse 1 - works like a charm. But still no luck with the magic trackpad!
Again: Am I the only one with that problem under Mojave?
[doublepost=1533294885][/doublepost]
just an aside. on this platform, there is a lot of love for the dark mode. am i alone in preferring the light mode? i'd like to think not.
I´d prefer to stick with light mode during daytime (for me personally, it´s kind of eye-stressing to have the dark screen compete with bright surroundings - a matter of eye adaption) and switch to dark mode in the evening. But at the moment, only dark mode seems acceptable with all the UI bugs currently. I fully understand that CAD/CAE/Photo/Film folks (and even lots of programmers) prefer to have minimum distraction from their focus on screen content and therefore "go dark"...
 
Last edited:
Is it possible to put the Kext drivers for the Newer AMD GPU From High Sierra or Sierra to allow the Drivers to load for The AMD Radeon 7xxx GPUs like the R9 270X. Since I can't afford a GTX 680.
 
  • Like
Reactions: TimothyR734
Is it possible to put the Kext drivers for the Newer AMD GPU From High Sierra or Sierra to allow the Drivers to load for The AMD Radeon 7xxx GPUs like the R9 270X. Since I can't afford a GTX 680.
newer AMD cards (GCN) don’t work on 3,1 because of the lack of CPU features (i think SSE4.2?)

EDIT: If you're going NVIDIA, avoid the 650 ti boost, 660 and 660 ti. Those dont work on high sierra and higher (it artifacts like crazy once its VRAM fills up)
 
Last edited:
newer AMD cards (GCN) don’t work on 3,1 because of the lack of CPU features (i think SSE4.2?)
Yeah that's right. The newer AMD drivers require SSE4.2, and will just crash on the Mac Pro 3,1 because it lacks that instruction set.
[doublepost=1533303991][/doublepost]
Is it possible to put the Kext drivers for the Newer AMD GPU From High Sierra or Sierra to allow the Drivers to load for The AMD Radeon 7xxx GPUs like the R9 270X. Since I can't afford a GTX 680.
You don't HAVE to get a GTX 680. Any GT(X) 6xx series card will work fine. Just get a GTX 650 or something, they're not very expensive. Also, I would never buy an AMD video card after the crap they pulled with the Radeon HD 6xxx series chipsets (and STILL haven't fixed TO THIS DAY!)
 
Yeah that's right. The newer AMD drivers require SSE4.2, and will just crash on the Mac Pro 3,1 because it lacks that instruction set.
[doublepost=1533303991][/doublepost]
You don't HAVE to get a GTX 680. Any GT(X) 6xx series card will work fine. Just get a GTX 650 or something, they're not very expensive. Also, I would never buy an AMD video card after the crap they pulled with the Radeon HD 6xxx series chipsets (and STILL haven't fixed TO THIS DAY!)
You can get the 6750 chips new apparently, I know that someone on eBay have sold new chips if you specifically asked for them. I don't know if they are revised or not, and I'm not sure if you can get them anymore. He was the only one that had new chips, besides getting them from the factory.

I know this because I have a 2011 macbook and was looking to find a new GPU chip for it to solder on. I bought one before I knew this so obviously I got a fake one, you could clearly see where the edge bonding had been glued to it in the microscope.
 
  • Like
Reactions: TimothyR734
You can get the 6750 chips new apparently, I know that someone on eBay have sold new chips if you specifically asked for them. I don't know if they are revised or not, and I'm not sure if you can get them anymore. He was the only one that had new chips, besides getting them from the factory.

I know this because I have a 2011 macbook and was looking to find a new GPU chip for it to solder on. I bought one before I knew this so obviously I got a fake one, you could clearly see where the edge bonding had been glued to it in the microscope.
I've gotten many of those, and yeah, they're "new", but are still defective, as AMD never revised the chips and fixed the defect they had. I've soldered many of these "new" chips, and a lot end up being DOA (wasting about 2 hours worth of work), or fail again like 2 weeks later. I will hate AMD forever because of this. Also, those brand new chips cost over $150 a piece.
 
I've gotten many of those, and yeah, they're "new", but are still defective, as AMD never revised the chips and fixed the defect they had. I've soldered many of these "new" chips, and a lot end up being DOA (wasting about 2 hours worth of work), or fail again like 2 weeks later. I will hate AMD forever because of this. Also, those brand new chips cost over $150 a piece.
could enough people come together that's have bought "new" amd chips and bring a lawsuit for the chips being defective
 
I've gotten many of those, and yeah, they're "new", but are still defective, as AMD never revised the chips and fixed the defect they had. I've soldered many of these "new" chips, and a lot end up being DOA (wasting about 2 hours worth of work), or fail again like 2 weeks later. I will hate AMD forever because of this. Also, those brand new chips cost over $150 a piece.
Sorry if I'm being too much but have you tried reballing the "new" chips with leaded balls ? also sometimes the GPU ram chips need to be reflowed, have you tried that too ? Im asking in case I decide to solder the fake chip on the board.
 
  • Like
Reactions: TimothyR734
Sorry if I'm being too much but have you tried reballing the "new" chips with leaded balls ? also sometimes the GPU ram chips need to be reflowed, have you tried that too ? Im asking in case I decide to solder the fake chip on the board.
Wait, are the "fake" chips a redesign of the original chips or something? Why would you want to put a fake chip on the board?
 
  • Like
Reactions: TimothyR734
Wait, are the "fake" chips a redesign of the original chips or something? Why would you want to put a fake chip on the board?
They remove the markings of a used chip that has been soldered to a board before, and laser or stamp in a new date code, to make the chip appear new, then sell it as new for more money.

I would use it because I have it already and if I would be lucky it could work for a while, only for reinstalling macOS and such, otherwise I'd keep it disabled. The current chip that's on the board is completely unusable so not much to lose.
 
They remove the markings of a used chip that has been soldered to a board before, and laser or stamp in a new date code, to make the chip appear new, then sell it as new for more money.

I would use it because I have it already and if I would be lucky it could work for a while, only for reinstalling macOS and such, otherwise I'd keep it disabled. The current chip that's on the board is completely unusable so not much to lose.
Ah, that makes more sense. I'm glad the Nvidia chips seem to be a bit more reliable at least, even if they aren't exactly "bulletproof."
 
  • Like
Reactions: TimothyR734
They remove the markings of a used chip that has been soldered to a board before, and laser or stamp in a new date code, to make the chip appear new, then sell it as new for more money.

I would use it because I have it already and if I would be lucky it could work for a while, only for reinstalling macOS and such, otherwise I'd keep it disabled. The current chip that's on the board is completely unusable so not much to lose.

I don't have any Mac with an AMD/ATI GPU, but if I'm not mistaken, unless you already have a partially working MacBook Pro 2011 only with the IntelHD3000, disabling the AMD/ATI through NVRAM command you could boot anyway.

Even if you succeed in replacing and soldering the new GPU CHIP, maybe could risk on the other side a kind of EFI CHIP Brick, I mean it couldn't pass the necessaries EFI (logic board components) CHECKS after chime sound, stucking on a black screen.

edit:
If you still can't neither power-on using the other IntelHD3000 GPU (because of faulted AMD/ATI GPU), then you have nothing to lose, and maybe your test could work being helpful for the others.

BUT seems exists also an "hardware way" to disable physically the AMD/ATI GPU on a dual GPUs MacBookPro, removing a resistor "R8911".
It seems also that in this way the machine EFI should be seen as having only the IntelHD3000, lets say as a MacBookPro 13" 2011.
 
Last edited:
I don't have any Mac with an AMD/ATI GPU, but if I'm not mistaken, unless you already have a partially working MacBook Pro 2011 only with the IntelHD3000, disabling the AMD/ATI through NVRAM command you could boot anyway.

Even if you succeed in replacing and soldering the new GPU CHIP, maybe could risk on the other side a kind of EFI CHIP Brick, I mean it couldn't pass the necessaries EFI (logic board components) CHECKS after chime sound, stucking on a black screen.

edit:
If you still can't neither power-on using the other IntelHD3000 GPU (because of faulted AMD/ATI GPU), then you have nothing to lose, and maybe your test could work being helpful for the others.

BUT seems exists also an "hardware way" to disable physically the AMD/ATI GPU on a dual GPUs MacBookPro, removing a resistor "R8911".
It seems also that in this way the machine EFI should be seen as having only the IntelHD3000, lets say as a MacBookPro 13" 2011.
I tried several methods, but found that this one worked the best, 1 setting the nvram variable, 2 moving the x3000 kext from extensions folder, 3 creating a login hook to load the x3000kext, 4 setting GPU sleep preferences to integrated. It works in high Sierra, brightness settings and everything, except the screen flickers sometimes.
I heated the GPU 2 times already to get it working temporarily, now If I need to use the dedicated GPU at all I can not see what I'm doing, Im sure it will soon be completely dead since sometimes it freezes now too.

I don't think I want to stay on high Sierra either, I much rather sell it then and use my 2010 macbook instead.

Edit
removing the resistor means no dedicated GPU option at all and I rather not have it that way.
 
The 1.1.1 version of you macOS Patcher worked great on my MacBook 5,2 is my iSight cam defective when you reinstall the iSight patch then use the kext utility un replace the 5 kexts from High Sierra as it says no video capture device found Thanks dosdude1
 
  • Like
Reactions: visberry
Has anyone tried the Graphics Set for translucency from older versions of macOS? Maybe Apple changed it up in High Sierra because of their focus on Metal 2. Maybe Sierra 10.13, El Capitan 10.11 or even Yosemite. We got other things working from older platforms. This could give us a good chance of getting some sort of translucency back in Light Mode, although I love Dark Mode, I am sort of missing the classic light mode when I am doing work in the day on my Mac.

Edit: Fixed typo
 
Last edited:
I had Mojave running on my MBP 5,5, but after booting off and back onto it it refused to boot. I had to rewrite Mojave to a flash drive, not realizing it was only 8 gb instead of my 16 gb drive. Anyways, the reinstallation failed and it corrupted the partition. I wiped the drive, rewrote Mojave to my 16 gb drive and did a clean install. After, I enrolled my mac into the beta program to update from the 4th build (18A336e) to the 5th build (18A347e). However, after enrolling, the software update still won't show in settings, saying my macOS is up to date. How can I get the update to show in settings?
 
  • Like
Reactions: TimothyR734
it is hit or miss with some machines upgrading to Mojave beta 5 version 1.1.1 is available (patcher) on the OP you can download macOS DP5 create a new patcher I am trying to see if installing DP5 over PB3 will work on my iMac 9,1 it didn't work on my MacBook installing DP5 over PB3 on my iMac 9,1 was successful :)
 
Last edited:
Finally got around to installing DP5, and man, these wallpapers are cool.

Kinda bummed that they took out everything pre-Yosemite tho.
 

Attachments

  • Screen Shot 2018-08-04 at 2.52.45 AM.png
    Screen Shot 2018-08-04 at 2.52.45 AM.png
    527.2 KB · Views: 247
I had Mojave running on my MBP 5,5, but after booting off and back onto it it refused to boot. I had to rewrite Mojave to a flash drive, not realizing it was only 8 gb instead of my 16 gb drive. Anyways, the reinstallation failed and it corrupted the partition. I wiped the drive, rewrote Mojave to my 16 gb drive and did a clean install. After, I enrolled my mac into the beta program to update from the 4th build (18A336e) to the 5th build (18A347e). However, after enrolling, the software update still won't show in settings, saying my macOS is up to date. How can I get the update to show in settings?
Which beta are you trying to get public 4 or dev 5? In my case (macpro 3,1 on Mojave dB4) , OTA system updates from b4 to b5 have at least consistently downloaded the full Mojave installer (5.8GB) after running the (developer) beta utility. Make sure you've installed dosdude1's software update patch (or manual equivalent) However, you'll end up with an installer that won't work until you either 1) create a patcher stick with it or 2) patch the distribution yourself (manually) then post-install (can be done manually too). There are posts here about the manual procedures - check out ASentientBot's instructions earlier in this thread if you're interested.
In my case b3 to b4 was the only automatic OTA system update (yay!) that ran smoothly and restarted (post-install still necessary)
There are many ways to skin this cat...Hopefully this will become more consistent after GM.
 
  • Like
Reactions: TimothyR734
Just noticed @dosdude1's new macOS Mojave Patcher version 1.1.1 is out. And that included more Utilities ~Startup Security utility, RAID utility, Disk Utility, Time Machine System Restore (this one I find really useful), Terminal, Network Utility and of course macOS Post Install.

Mahalo as always, @dosdude1.
Have anyone tried Raid 0 as boot drive with the patcher ? I read that someone did successfully create a raid 0 in terminal and install Mojave on it, but that was on a supported machine.
 
Has anyone tried the Graphics Set for translucency from older versions of macOS? Maybe Apple changed it up in High Sierra because of their focus on Metal 2. Maybe Sierra 10.13, El Capitan 10.11 or even Yosemite. We got other things working from older platforms. This could give us a good chance of getting some sort of translucency back in Light Mode, although I love Dark Mode, I am sort of missing the classic light mode when I am doing work in the day on my Mac.

Edit: Fixed typo

I've tried something going backward until Sierra 10.12.6, upon @Badruzeus suggestion, I've investigate a bit, and almost sure that the "light mode" transparency is rendered by the /S/L/PF/SkyLight.Framework

On Sierra the Skylight binary file is sized 7,4 MB , while on HS is 4,4 MB similar size as Mojave

Replacing with Sierra one you get a lot of WindowServer crashes, while a better behavior you get replacing with HS one BUT it stuck on black screen after the stage2 Apple logo, the keyboard is responsive, sometimes appears also the mouse cursor on black screen.

Anyway I guess this Mojave file is always mandatory, even if someone will succeed in patching:
/S/L/PF/SkyLight.Framework/Versions/A/Resources/WindowServer
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.