Jump to content


  • Content Count

  • Joined

  • Last visited

About timp

  • Rank
    InsanelyMac Protégé

Recent Profile Visitors

3,865 profile views
  1. timp

    Screen Freeze with GTX 970 / X99 in Sierra

    Hay, Did you solve this? I have an Asus X99 and MSI GTX 1080 and it seems to have the same problems. Works fine in Windows 7 and Linux. Just 10.12.* + the webdriver seems problematic. I haven't tried early versions of OSX. Usually there's a NVidia DMA, PDE or MMU error or somthing about 'channel violation' which causes the WindowServer or loginwindow process to fail and the system hangs. Sometime it reboots, sometime I get the login prompt again with screen corruption, sometimes it reboots. It's most definately coming from the WebDriver. I hope the cards not failing!
  2. So a just enabling Optimus in the BIOS and changing the SMBIOS from MacPro5,1 to MacBook8,3 gets the 980m working on the display port. Having the connectors defined in the DSDT doesn't seem to make a difference. Like I added them, and it didn't work. Then I enabled Optimus and changed the SMBIOS and the 980m started working on the DP. I've now reverted to my old DSDT without the connectors and the 980m still works on the DP. Still can't get OSX to start up with Optimus disabled. If I can work out which ports the LVDS panel and HDMI are connected to I'll try patching the DSDT with the right connector types for the m6700 and see what happens. Thanks for your help. I would have given up without your suggestions.
  3. Thanks. I tried adding the DSDT mod under the GFX0 device. The connector definitions show up in IORegisteryExplorer so the patch is there, but unfortunately it doesn't fix it. I also tried with Opimus switched on and the web driver enable. While it still reboots on startup, the IGP connected display shows a panic in the NVDAResmanWeb kext, which I managed to get a photo of. Doesn't give much to go on. Do you have nvram working? If so, natively or with nvram clover extension?
  4. Okay, I'd already disabled all the Nvidia options in Clover with exception of enabling the Web Driver so it's probably not the config then. I have a patched DSDT, but I've be trying to reduce that and rely more on Clover to do it for me. What did you change with ACPI patching? I tried recording the verbose log messages using my smartphone, but it boots too quickly to be readable. I can see it's using the web driver in the verbose output, and that it uses the GM100 kext, but there's not much more than that. Since Apple changed the way logging works I haven't been able to find if the verbose boot logging is written to a log file somewhere. If I can find a better way to record the verbose boot I'll attach it. Thanks for the help.
  5. So the 980m is supported then. Wonder why mine crashes. Are you on 10.12.3? Would it be possible to attach or send me your Clover config file? The Dell m6700 has hardware video signal multiplexers. There is an option in the BIOS to disable Optimus. It seems this option disables the IGP and switches the multiplexers to use the outputs from the MXM slot to drive the internal LCD and one of the external ports. Maybe I should try OSX with Optimus enabled. Should behave the same as your setup then. Maybe if it's the LVDS internal LCD that is a problem for the driver... Thanks for your reply. Maybe I'll get this working after all.
  6. I have a Clevo 980m 8GB card installed in a Dell m6700(Optimus disabled) with 10.12.3(16D32). The 367.15.10.35f01 driver hangs or reboots the machine at about the time the desktop should appear. Like, after showing the verbose boot text the screen goes blank and the machine hangs or reboots. I assume I just need to check the Web Driver option in Clover? Nvidia injection, nvda_drv=1 and fake nvram aren't needed right? Anyone got a Maxwell mobile GPU working? The machine works well in Windows 7 and Ubuntu 16.04 with 378 and 375 version drivers respectively. Also not liking Sierra's new logging/console setup. Seems being able to see the boot log after a boot fails isn't a priority at Apple.
  7. Hi. I created a USB installer for Yosemite using Clover. I don't remember the details. Most things were fixed by changes to the Clover config and a custom DSDT. Sorry I can't be more help. I seem to remember some extra config to patch the kernel is needed for El Captain. Maybe newer version of Clover now have an option to do this. Did you get it installed? You'll need a USB keyboard and mouse. Or add the PS2 kexts to the installer. Not sure how to do that though as the installer has changed with newer versions of OSX.
  8. An update to getting the LP173WF1-TLB5 LCD panel working. Basically its EDID doesn't go down very well with the AMD drivers. While the above solution worked with sleep, if I connected or disconnected an external monitor the EDID override would get lost and the funky colours would come back. My new solution is to change the LVDS personality's sense ID to one that's not being used. This make it impossible for the AMD driver to get the really EDID from the panel. And then use Clover's EDID injection with a custom EDID. Without the really EDID getting in the way Clover's EDID injection seems to work well. So the solution is to remove any overrides that may match your panel's IDs from /System/Library/Displays/Overrides/ and put something like this in the Clover config.plist: <key>Graphics</key> <dict> <key>Inject</key> <dict> <key>ATI</key> <true/> <key>Intel</key> <false/> <key>NVidia</key> <false/> </dict> <key>FBName</key> <string>Buri</string> <key>DualLink</key> <integer>1</integer> <key>InjectEDID</key> <true/> <key>CustomEDID</key> <data>AP///////wAw5IMCAAAAAAASAQSQIhN4AsiVnldUkiYPUFQAAAABAQEBAQEBAQEBAQEBAQEBFDeAsnA4KEAYECQAWMEQAAAYuCSAsnA4KEAYECQAWMEQAAAYAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAMNfkPPIwaGDyTICAgAL0=</data> <key>LoadVBios</key> <false/> <key>PatchVBios</key> <false/> </dict> <key>KernelAndKextPatches</key> <dict> <key>ATIConnectorsController</key> <string>7000</string> <key>ATIConnectorsData</key> <string>02000000000100002905010010000505000400000403000000090200110201010004000004030000000903002103020200080000040200000001040012040303</string> <key>ATIConnectorsPatch</key> <string>02000000400000002901010010000500000400000403000000010200110201010004000004030000000103002103020200080000040200000001040012040303</string> Note the 5 is now a 0 in the first personality '02000000400000002901010010000500' Hope someone finds this useful.
  9. So after much farting about with MXM graphics cards I've installed an Dell/AMD Firepro m6000 and finally got the internal LCD working without gradients. Thanks to Amble and Deschutes for their posts here: http://www.insanelymac.com/forum/topic/277042-amd-radeon-hd-6650m-graphics-enabler-dsdt-hdmi-audio-acer-aspire-7750g-2674g50mnkk-gradients-fixed/page-38?do=findComment&comment=1977940 I had load hassle with wrong colours like in Amble's photo and gradients until I made an override for the panel's EDID using the AUO EDID Deschute's posted. The M6700 is configured with an LP173WF1-TLB5 panel. Both the LP and AUO panel are 1920x1080. Here are the relevant bits from Clovers config.plist: <key>Graphics</key> <dict> <key>DualLink</key> <integer>1</integer> <key>FBName</key> <string>Buri</string> <key>Inject</key> <dict> <key>ATI</key> <true/> <key>Intel</key> <false/> <key>NVidia</key> <false/> </dict> <key>LoadVBios</key> <true/> <key>PatchVBios</key> <true/> </dict> ... <key>KernelAndKextPatches</key> <dict> <key>ATIConnectorsController</key> <string>7000</string> <key>ATIConnectorsData</key> <string>02000000000100002905010010000505000400000403000000090200110201010004000004030000000903002103020200080000040200000001040012040303</string> <key>ATIConnectorsPatch</key> <string>02000000400000000901010010000005000400000403000000010200110201010004000004030000000103002103020200080000040200000001040012040303</string> And for the EDID override I created this file in /System/Library/Displays/Overrides/DisplayVendorID-30e4: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>DisplayProductID</key> <integer>643</integer> <key>DisplayVendorID</key> <integer>12516</integer> <key>IODisplayEDID</key> <data>AP///////wAGr+0TAAAAAAASAQSQIhN4AsiVnldUkiYPUFQAAAABAQEBAQEBAQEBAQEBAQEBFDeAsnA4KEAYECQAWMEQAAAYuCSAsnA4KEAYECQAWMEQAAAYAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAMNfkPPIwaGDyTICAgAKE=</data> </dict> </plist> Note that in the ATIConnectorsPatch the personality for the LVDS is 0200 0000 4000 0000 0901 0100 10 00 00 05. The encoder is 00 not 01. 01 gives an image, but with jittering, and sleep causes a black screen. Also the Hotplay IDs start at 00, didn't work starting at 01. Couldn't get the EDID override to work in Clover, don't know why.
  10. timp

    Seabios Clover HP Chromebook 14.

    Hi, Did you get Clover working with SeaBios? I'm also using a johnlewis.ie rom but on a Samsung Chromebox(Stumpy). 10.8 works okay with Chameleon(except for sleep). Would be nice to be able to update to Yosemite. Cheers, Tim.
  11. I was looking at about installing OSX on a cheapo Z3735F TV box. The first problem I foresee is that I doubt it'll be able to access the eMMC storage. Like I can't imagine there is a .kext for eMMC disks included in OSX by default. Please correct me if I'm wrong. It may be possible with a USB connected disk.
  12. Well thanks to John Lewis and his fantastic work on getting SeaBios working on the Samsung Chomebox, I've got OSX installed and booting on the Chromebox using a modified Mountain Lion install USB dongle. It's quite involved. Some hardware and hackintosh experience is required. Given the nature of what's involved don't blame John or me if you try this and brick/break your Chromebox. Unfortunately I don't have much time to respond to help requests although amendments and comments are welcome. If you like John's work on SeaBios, donate some money. He's clearly put a lot of time into it. Also, running OSX on non-Mac hardware is illegal, I'm doing this just to prove it can be done. So the process is something like this: 1. Make sure your Chromebox(Stumpy) has a HD3000 GPU and not the HD2000 that is in the Celeron version. You can quite easterly upgrade the CPU. I've tried an i7-2670qm that worked, but it got a bit hot. Now it's running an i5-2520m. I expect most core 'i' second gen CPU's will work although the CPU shouldn't be more than 35W TDP. 2. Enable developer mode and disable write protect. You'll have to remove the motherboard to do this as the write protect jumper is on the back. See http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/samsung-sandy-bridge At the bottom of the page there are some photos of the Stumpy. The write protect jumper is the lower of the two white connectors in the top left corner of the last two pictures. Next to the 8-pinned flash memory. 3. Create a Mountain Lion install USB dongle. I used Chameleon 2.1 and added the contents /Extra folder as follows.(I'll try and attach a tar file..) /Extra/Extensions/FakeSMC.kext /Extra/Extensions/NullCPUPowerManagement.kext /Extra/smbios.plist (From MacMini5,1) /Extra/org.chameleon.Boot.plist <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Kernel Flags</key> <string>-v</string> <key>GraphicsEnabler</key> <string>Yes</string> <key>Graphics Mode</key> <string>1920x1080x32</string> <key>Timeout</key> <string>2</string> <key>USBBusFix</key> <string>Yes</string> <key>Wait</key> <string>No</string> </dict> </plist> 4. Go to John Lewis's site: https://johnlewis.ie/custom-chromebook-firmware/rom-download/ and read about his work AND THE RISKS OF USING IT!! 5. Boot the Chromebox and download and run the flash script from John Lewis's site: https://johnlewis.ie/custom-chromebook-firmware/rom-download/ IF IT FAILS DON'T REBOOT!! Go to John Lewis's site for help. You need to re-flash the backup of the original rom the script made. I ran the script from Ubuntu 12 not ChromeOS and it worked great. 6. See if your Chromebox will still start. It only needs to get to the SeaBios text screen. Mine boot looped trying to boot from the SSD. I think because it can't boot from the odd ChromeOS boot setup. 6* (Optional) If you have OSX compatible Wifi card. Install it. 7. Insert your dongle, power up, press ESC and select the OSX Installer USB dongle. In the SeaBios boot menu you should get 3 options. HD, USB and some funky ROM based Linux that does't work with a USB Keyboard. If the you can't get Chameleon to start, it's probably the dongle. (FYI. I connected the dongle to one of the ports on the front of the Chromebox. Don't know this has any effect.) You can try the -x and -f Chameleon boot options if OSX hangs. 8. In the Installer open the DiskUtility and repartition the 16GB internal drive to contain one Mac file system. 9. Install OSX. 10. Stop the installer before it reboots or Reboot using the USB dongle again. 11. Install Chameleon. 12. Copy files from the USB dongles /Extra to the SSD. You can try adding the -allowAppleCPUPM option in org.chameleon.Boot.plist to enable power management. 13. Add the Lnx2Mac Realtek and VoodooHDA kexts to /System/Library/Extensions. What doesn't work: Sleep. Sleeps, but reboots on wake. The headphone socket. The mic works, but not audio out. Bluetooth. The hardware is detected but no devices show up when paring. Still a bit dodgy. Opening 'About this Mac' logs the user out!? Weird. smbios issue? HD3000 Artifacts.. I'll try and update this post with any further progress. Cheers and good luck. UPDATE: 15Sept14 I've found using Clover version 2890 and setting the ProductName to MacMini5,1 fixes sleep and the 'About this Mac' log outs. Seems Chameleon wasn't able to correctly set the memory parameters in the smBios. The down side is that there is now graphics tearing, although after a sleep cycle them seem to clear up. Still testing.. Another note. In SeaBios the keyboard only seems to work in the USB port on the back corner of the unit. UPDATE: 16Sept14 To get the audio output switching working between the internal speaker and the headphone jack add the following xml to Info.plist in VoodooHDA.kext next to 'MixerValues' <key>NodesToPatch</key> <array> <dict> <key>Codec</key> <integer>0</integer> <key>Node</key> <integer>5</integer> <key>Config</key> <string>0x0221201f</string> </dict> <dict> <key>Codec</key> <integer>0</integer> <key>Node</key> <integer>2</integer> <key>Conns</key> <array> <integer>5</integer> <integer>6</integer> </array> </dict> </array> This changes the headphone node config and tells the driver that node 2(the DAC) can switch between to nodes 5 & 6, The headphone jack and speaker. The Athreos AR3012 bluetooth chip will work with the 'Bluetooth Firmware Uploader' from osxlatitude.com but fails after sleep and is a bit glitchy. You need to add the correct ids(3315 & 12292) to the kexts Info.plist. There are still problems with the visual artifacts with the HD3000. Disabling Clover's Intel graphics fix seems to help. Seems to randomly occur on some boots but not others. UPDATE: 21Sept14 HD 3000 artifacts seem to improve with the code below added to the graphics section of the GFX0 device in the DSDT. This is the difference take from ioreg output between booting with Clover and Chameleon. Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x1C) { "AAPL00,DataJustify", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }, "AAPL00,Dither", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }, "AAPL00,DualLink", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }, "AAPL00,LinkFormat", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }, "AAPL00,LinkType", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }, "AAPL00,PixelFormat", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }, "AAPL00,T1", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }, "AAPL00,T2", Buffer (0x04) { 0x14, 0x00, 0x00, 0x00 }, "AAPL00,T3", Buffer (0x04) { 0xFA, 0x00, 0x00, 0x00 }, "AAPL00,T4", Buffer (0x04) { 0x2C, 0x01, 0x00, 0x00 }, "AAPL00,T5", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 }, "AAPL00,T6", Buffer (0x04) { 0x14, 0x00, 0x00, 0x00 }, "AAPL00,T7", Buffer (0x04) { 0xF4, 0x01, 0x00, 0x00 }, "model", Buffer (0x1E) { "Intel HD Graphics 3000 Mobile" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } UPDATE: 30Sept14 HD 3000 Still has problems with artifacts. Above DSDT doesn't fix it. Currently experimenting with EDID injection in Clover... Ethernet also has issues. On some boots the cable is detected but no data can be transferred. RealTek NICs seem to have problems generally. Given up on the Atheros Bluetooth firmware loader kexts.. ChomeboxFiles.zip
  13. For Andy. Here are my before and after DSDT .dsl files. Use iasl to compile them into .aml files. Sorry about all the iasl generated comments in one of the files but not the other. The newer version on iasl seems to decompile things slightly differently. I've included my modded AMD6000Controller kext binary too. It's from 10.8.4. The modded personality is Duckweed at byte offset 605008(decimal) Note my setup is an M6700 with a ATI/Dell 6970m 2GB card and Chimei N173HGE-L21 M6700.ati.dsdt.zip AMD6000Controller.zip
  14. Yeah. All works great with the M8900 although no VGA out and no HD4000 switching. The integrated GPU seems to be disabled with ATI cards. Would be good to know how the M6000 works. I also got the SD card reader working. I'll try and post a summary with once I've got things configured right. Did you get the brightness working with your NVidia card? Have you tried the PNLF DSDT mod: Device (PNLF) { Name (_HID, EisaId ("APP0002")) Name (_CID, "backlight") Name (_UID, 0x0A) Name (_STA, 0x0B) } Needs to be added at the same scope as the power button PWRB.
  15. timp

    Anyone mobile Kepler 6xxM working?

    I'd go with that theory too. I've given up trying to get a K3000m working with the 10.8.4 drivers. It's just not detecting the displays correctly no matter what DSDT injection you do. What's the version of the GeForce kexts shipping with 10.8.5? The latest drivers on NVidia's site are still at 313..