Jump to content
InsanelyMac Forum

Bounc1ngbanker

Members
  • Content count

    25
  • Joined

  • Last visited

About Bounc1ngbanker

  • Rank
    InsanelyMac Protégé
  1. Changing default VESA modes on graphics card.

    I thought there might be a workaround using the clover patch VBIOS and inject EDID options but it definitely doesn't seem to be working for me. I suspect the graphics card VBIOS needs to be altered. Trying to work out how to do it. Clover boot log 0:247 0:000 VideoBiosPatchNativeFromEdid: 0:247 0:000 Bios: nVidia, nv_data_table_offset: 0x283, nv_data_table: 0xC0285, std_vesa: 0xC42E7, nv_mode_table: 0xC42EC, mode_table_size: 0x10 0:247 0:000 VideoBiosPatchInit(LegacyRegion = Success) = Success 0:247 0:000 VideoBiosUnlock: unlocked 0:255 0:007 Patching: BT_NVDA 0:255 0:000 Parse Edid: descriptor block 0 is timing descriptor (h_active: 3440, v_active: 1440, h_sync_offset: 48, h_sync_width: 32, h_blanking: 160, v_blanking: 34, pixel_clock: 26525, v_sync_offset: 3, v_sync_width: 10) 0:255 0:000 the patch is not ready for the desired resolution 0:255 0:000 VideoBiosLock: Success 0:468 0:213 CsmVideoDriverBindingStart 0:468 0:000 mixed support=40010 0:468 0:000 Controller is [030000] 0:468 0:000 Check for VBE 0:682 0:213 0 640x480 attr=3BF - ok, 640x480, working, highest, pref=0 0:684 0:002 1 800x600 attr=3BF - ok, 800x600, working, highest, pref=1 0:686 0:002 2 1024x768 attr=3BF - ok, 1024x768, working, highest, pref=2 0:688 0:002 3 1280x1024 attr=3BF - ok 0:697 0:009 CsmVideo: New mode: 2 1024x768 - set 0:863 0:165 - SetMode pref 2 (2) = Success 0:863 0:000 CsmVideoCheckForVbe - Success
  2. Changing default VESA modes on graphics card.

    I have an Asus NVIDIA GTX650 in my Dell T5610 machine. When not booking in -v mode, the apple looks squashed for the first half of the boot sequence because the card is showing a default non-widescreen VESA resolution. After the first half of the sequence, the resolution resets and the apple appears at normal aspect ratio. Fiddling with the clover settings for boot resolution is no use if the card doesn't support that resolution as a VESA mode. The monitor is an ultra wide LG 34UC87 you see that normally runs at a resolution of 3440x14440. I believe the way to fix this, is to fix the default VESA modes supported by the graphics card by changing the VBIOS so that it boots up at native resolution for the monitor. Does anyone have any experience of doing this?
  3. Making very slow progress. I currently have fully working USB2 ports, the USB3 ports kind of work sometimes if they have something in them on reboot, and sleep still isn't working properly. Everything else seems ok. Am investigating how I can modify the video card default VESA modes so that when booting up the apple doesn't look squashed for the first half of the boot sequence. Watch this space.
  4. Help on the Dell T5610 would be really appreciated.

    Just to follow up. The Audio codec on the motherboard is: RealTek ALC269Q . I have been having problems finding suitable kexts or drivers for it. I went back to using VoodooHDA for the time being to get the sound working - but I understand that it's not really a great solution and (perhaps) might cause some stability issues. I have no idea why the USB2 camera is working correctly now. Sleep still doesn't work correctly - with Darkwake=8 the video comes on and the mouse pointer works but the cursor isn't blinking so it looks to have crashed - I haven't had time this week to try and look at the logs and work out why. I was planning to take apart all the DSDT edits one-by-one and try and understand them because I don't follow why the USB2 camera now works at all. I removed the unused ports that were injected by USBInjectAll.kext leaving just the two internal hubs, which, since your edits now appear sometimes to have ports labelled PRxx and other times named HPxx. I don't follow why that is either. Can you tell me what controls the port names that appear in IOreg? Is this a function of the USBInjectAll.kext port injection or is a function of the port name in the DSDT? How does the system arrive at these port names? This really is a bit of a nightmare actually. I think so far I've spent more time trying to get the machine working than actually using it.
  5. Help on the Dell T5610 would be really appreciated.

    Hello. Sorry for delay replying. The usb2 camera has started working now and I'm just trying to narrow down why that is. Please bear with me for a few days. Thanks again for your help so far.
  6. Help on the Dell T5610 would be really appreciated.

    Thank you. Could you please explain what you were trying to achieve in the dsdt edits? Is it worth keeping them? Also. What is the point of the lilu and applehda kexts in your distribution because it seems to me that they do not work for audio? Should I revert to my original configuration?
  7. Help on the Dell T5610 would be really appreciated.

    Thanks. Unfortunately that DSDT did not work correctly. Although the machine booted to the logon screen correctly, all USB devices were not working (apple USB keyboard, internal port connected to bluetooth magic mouse, additional USB mouse I tried and USB memory sticks). I note that in the edited DSDT the original USBE and EUSB devices were present. When I had this before, and the USB ports did not work, I got them working by renaming those devices to EH01 and EH02 which presumably allowed USBInjectAllKext to inject the ports. It's worth noting that I have not managed to get the machine to boot with working USB for mouse or keyboard without using USBInjectAll.kex. I tried to use the original DSDT with USBE/EUSB devices AND my modified DSDT. Neither worked. The only edits that I performed in my DSDT were to rename: a ) The device that appeared to be the graphics device to GFX1 from NPE3. b ) the USB devices to EH01/EH02 (from EUSB and USBE) c ) I (later) renamed the hubs from HUBN to HUB1 and HUB2 but it made no difference. d ) I The Third party USB controller, device 14, I renamed from PEX0 to XHC. Again I'm not sure that really helped. e ) Added a 'darwin' in the IF statement in OSFL method as an alternative to windows 2009 If (LOr (OOSI ("Darwin"), OOSI ("Windows 2009"))) because I assumed that this was windows 7 and this the OS the machine shipped with when released. Update one --------------- I edited the DSDT that you provided to rename devices EUSB and USBE to EH01 and EH02. That allowed the USB2 ports to work and hence log on. The front panel USB3 port [uSB3FL] does not work when a USB2 device is inserted. The light flashes briefly and goes out. However, if a USB2 stick is inserted into one of the rear panel USB3 ports [uSB3STR] as before, that works. Once that has been inserted into that port, plugging it back into the front panel USB3 port (USB3FL) then works fine. (?!?) This is as before. The USB2 ports function as expected. The IOReg output is here: http://www76.zippyshare.com/v/9WGTdZNS/file.html for a USB2 stick in a USB2 port. And is here for a USB2 stick inserted into a rear working USB3 port: http://www76.zippyshare.com/v/YetSiHS2/file.html
  8. Help on the Dell T5610 would be really appreciated.

    Thank you for the note. It seems there are a lot of changes in the clover folder that you provided. It's hard for me to narrow down what's causing the problem. I noted that there were a lot of changes in the DSDT that looked interesting. I performed the following. 1. The original distribution that you provided does not show the 'apple' and boots to a black screen. 2. I then removed NVIDAGraphicsFixup.kext. It did not show the apple and booted to a black screen. 3. I then removed Lilu.kext and AppleALC.kext. It did not show the apple and booted to a black screen. 4. I then replaced the DSDT with my original. It did not show the apple and booted to a black screen. 5. I then copied my original clover folder and in it, I placed all the kexts from your copy (with the exception of NvidiaGraphicsFixup.kext) and I placed your patched DSDT in ACPI/Patched. That copy booted to a logon screen successfully. However, the Internal USB port (connected to to my Apple bluetooth card) did not work, and neither did any USB mouse or Keyboard, so I was not able to proceed. Conclusion. 1) Some other change in your distribution (drivers? clover configuration?) caused the black screen. 2) Something in the DSDT edits is not working and hence disabling the USB ports. Update 1 ------------ I also checked S/L/E and I noticed that I had put VoodooHDA.kext in there because I read that it only works correctly from that location. I had forgotten. I also noticed AppleIntelE1000e.kext in both /L/E and S/L/E . I didn't put it there. I did use a certain horrible cartoonish tool with a name akin to murderbeast when I first tried to get this working but stopped when I noticed that it was putting stuff in different places and I wasn't sure what it was doing. It was possible that this tool did it. I'll remove AppleIntelE1000e.kext from both those locations. Update 2. ----------- I removed voodooHDA.kext from S/L/E and both instances of AppleIntelE!000e.kext from S/L/E and /L/E. I can see no other nonstandard items in there. I also removed AppleIntelE1000e from my original clover/kexts directory. Right now. Sound does not work over HDMI or from the back panel - as I would expect. The onboard ethernet does not work without AppleEthernetE1000e.kext. It shows 'cable disconnected' all the time. However, this isn't really a problem because I am using the NEC card which works out of the box for wired ethernet. The bluetooth apple card which has wifi on it also continues to function as i would expect. Update three ---------------- OK. So I took my original clover folder. I left my original DSDT in there. I replaced all the kexts in it with the ones from your distribution. As mentioned, I removed everything nonstandard from S/L/E and /L/E (AppleIntelE1000e and VoodooHDA) The machine boots fine and I can log on. Sound over HDMI and onboard sound does not work. Onboard network does not work. USB3 ports are not recognised - just as before the light flashes briefly and goes out. Some USB2 ports no longer accept a memory stick. Some work. Some do not. Keyboard (plugged into USB port USB2VTR) works Camera (plugged into USB USB2VTL) still does not work. Bluetooth card (plugged into internal port) works. To avoid any confusion I have included the files again here: IOReg output http://www61.zippyshare.com/v/aNMoa9IO/file.html Clover folder as of current configuration http://www61.zippyshare.com/v/ygxm8eTQ/file.html Tables http://www61.zippyshare.com/v/yYHIwvcO/file.html Thanks so much for trying to help me. This has been a very frustrating journey because of the lack of clear information and documentation out there. Kind Rgds John
  9. Help on the Dell T5610 would be really appreciated.

    Thank you for the note and for the time you have spent on trying to solve my problem. Unfortunately the machine did not boot with that configuration. There were numerous errors along the lines of: AppleUSBHostPort::InterruptOccurred::Overcurrent Detected with port status: 0x4002 for two of the ports PR17 and PR18 I think. It was very slow booting. Then it went to a black screen. A few observations I have that I don't understand. 1. I note that in kexts/other in the alternative distribution you provided it has: IntelMausiEthernet.kext Lilu.kext NVidiaGraphicsFixup.kext. Not sure why that is. This machine has an Nvidia GTX650 card in it - which I believe is out of the box compatible with macOS-X? I am not sure why NvidaGraphicsFixup.kext / lily.kext are necessary? I am not experiencing any graphics issues or stuttering at all. I have tried IntelMausiEthernet.kext in the past. It did not work correctly. The existing kext for AppleEthernet100e worked just fine. It's worth noting that I currently have an additional PCIe card in there for ethernet that also works 'out of the box' just fine ( as well as the motherboard ethernet) This is an HP NC360T dual port adapter. Kind Rgds John After the above checks, I tried to use a modified SSDT-UIAC-ALL.aml to disable unwanted ports, and tried booting with a USB2 stick in the USB3 ports. The USB3 ports were recognised and the unwanted USB2 ports were indeed disabled. So it seems to me that my problems are: 1. The machine does not wake from sleep properly. 2. The machine won't recognise USB3 ports without booting with something plugged into the port. Will investigate further.
  10. Help on the Dell T5610 would be really appreciated.

    Thanks. http://www14.zippyshare.com/v/3aNkkSJD/file.html (clover directory) http://www14.zippyshare.com/v/lZVNY2Ve/file.html (Tables) http://www14.zippyshare.com/v/fBxwbC65/file.html (IOreg) Have also sent the same. It's worth noting that recognising the devices plugged into a USB3 port does not seem reliable. It seems to always recognise any USB2 or USB3 devices plugged into a USB3 port - as long as I reboot the machine with a USB2 stick in that particular USB3 port. There also seems to be some effect on the other USB3 ports. Investigation of effect of powering on with devices plugged in. Test one ---------- Reboot the machine with nothing in any USB3 ports. Plug a USB stick into USB3 front panel left. [uSB3FPL] Results. A USB2 stick with a light on it, flashes briefly and goes it. It is not recognised. No other devices plugged that same USB3 port works. Test Two ----------- I then rebooted the machine with nothing in any USB3 ports. I Placed the USB2 stick with light in the same USB3 port (front panel left) [uSB3FPL] Results: The light flashed briefly and went out. I left it plugged in for fifteen minutes. It was not recognised. Next steps: I plugged the same stick into another USB3 port (rear panel secondary block top right as mentioned in the mapping below) [uSB3STR] It was recognised. I then plugged it into the rear panel secondary block top left [uSB3STL] and it was not recognised. I then plugged it into the rear panel secondary block bottom left [uSB3SBL] and it was not recognised. I then re-plugged the same stick into the same port (front panel left) [uSB3FPL] that was not working before. and it worked and was recognised (!?!) I removed it and tried in the two rear ports again. It still did not work in rear panel secondary block top left [uSB3STL] or rear panel secondary bottom left [uSB3SBL]. Test Three ------------- I restarted the machine with the USB stick plugged into the rear secondary block top right port [uSB3STR] The light on it stayed lit all the way through boot and it was recognised. The stick plugged into rear secondary block top left [uSB3STL] was not recognised. I then moved the stick into front panel left ]USB3FPL] and that was recognised too. I then moved the stick back to the original socket that worked (rear secondary block top right) [uSB3STR] and it was no longer working (?!?) Test Four ------------- I restarted the machine with the USB2 stick in the front panel top left port [uSB3FPL] The light lit up and stayed on all the way through boot. It was recognised. I then plugged my USB3 device into that port [uSB3FPL] It was recognised and it appears under: XHC@1C / IOPP / PCI1912,14@0 / GenericUSBXHCI / G Drive with Thunderbolt USB3 @ 1C20 0000 That makes sense because the device ID in IOReg (and windows when I checked the controller) is given as 14 and the XHC device in my DSDT (which was renamed from PEX0) has an address of 0x001C 0000 I don't know if the IO reg file contains this information. But I uploaded it anyways here with that USB3 device showin under XHC as mentioned. http://www8.zippyshare.com/v/F0AcRFdN/file.html Conclusion 1. Any device plugged into a USB3 port at boot up, renders that device operational. 2. As a side-effect, it also seems to affect (some) other USB3 ports. There seems to be correlation in the hardware between the front panel top left port [uSB3FPL] and the rear panel secondary (top right) port [uSB3STR] There seems to be a correlation in the hardware between the rear panel secondary (top left) [uSB3STL] and the rear panel secondary (bottom left) port [uSB3SBL]. The USB3 ports appear to be linked somehow in pairs in the hardware. The above is reproduceable. I repeated it twice with the same results. I can see nothing in the BIOS to 'tune' to alleviate this. There are no relevant settings. There is nothing about XHCI handoff in the BIOS. This isn't necessarily big issue since I can keep a USB device plugged into a rear port all the time if I need to but it does point to an underlying problem that I don't understand. Machine Configuration The machine configuration as mentioned above, and as extracted, does not include the SSDT-UIAC-ALL.aml which didn't help matters, and it does not include an altered USBInjectAll.kext - because that didn't help either. The information I have discovered about the physical configuration of my ports is as follows: USB port configuration --------------------------- Machine has 4 external USB3 ports, 6 external USB2 ports, 3 internal USB2 ports according to the data sheet. http://i.dell.com/sites/doccontent/shared-content/data-sheets/en/Documents/CSG-EN-XX-ALL-Dell-Precision-T5610-Spec-Sheet.pdf I will refer to the ports by shorthand letters referring to their type and physical location: example: USB3FPL , USB2VTR , USB3STL and so on. Physical configuration of ports. Front Panel (4) - 1 USB3 ( far left ) [uSB3FPL] and 3 * USB2 [uSB2F1, USB2FP2 and USB2FP3] Back Panel (6): two ports next to PS/2 keyboard 2 USB2 (very top left and right) [uSB2VTL and USB2VTR] Four ports in a secondary block of four (a grid of two by two) configured as top left, top right, bottom left, bottom right. 2 USB3 (Secondary block of four. (Top Left and Top Right) [uSB3STL and USB3STR] 1 USB3 (Secondary block of four. Bottom Left) [uSB3SBL] 1 USB2 (secondary block of four. Bottom Right) [uSB2SBR] Internal (3) 3 x USB2 ports [uSB2i1. USB2i2 and USB2i3] Devices plugged into the ports: ------------------------------------ apple bluetooth card. Working. Plugged into one internal port [uSB2i1] apple keyboard with hub. Working. Plugged into back panel very top right [uSB2VTR] Camera. Not working. Plugged into back panel very top left [uSB2VTL] IOReg mapping information ---EH01 @1d00 0000---- EH01 / PR11 @ 1d10 0000- all devices appear under an internal port under this. I guess this is the hub. EH01 / PR12 @ 1d20 0000 No devices ever appear EH01 / PR13 @ 1d30 0000 No devices ever appear EH01 / PR14 @ 1d40 0000 No devices ever appear EH01 / PR15 @ 1d50 0000 No devices ever appear EH01 / PR16 @ 1d60 0000 No devices ever appear EH01 / PR17 @ 1d70 0000 No devices ever appear EH01 / PR18 @ 1d80 0000 No devices ever appear Internal hub addresses for EH01 seem to be: EH01 / PR30 @ 1d11 0000 USB2 Front Panel Second From Right [uSB2F2] EH01 / PR31 @ 1d12 0000 USB2 Front Panel Second From Left. [uSB2F1] EH01 / PR32 @ 1d13 0000 USB2 Front Panel Far Right [uSB2F3] EH01 / PR33 @ 1d14 0000 ?? (could be an internal USB I am not using) EH01 / PR34 @ 1d15 0000 USB2 Back Panel very top right (Apple Keyboard with internal hub) [uSB2VTR] EH01 / PR35 @ 1d160 0000 USB2 Back Panel very Top Left (Camera) [uSB2VTL] EH01 / PR36 @ 1d170 0000 No devices ever appear EH01 / PR37 @ 1d180 0000 No devices ever appear ---EH02 @ 1a00 0000 ---- EH02 / PR21 @ 1a10 0000 - all devices appear under an internal port under this. I guess this is the hub. EH02 / PR22 @ 1a20 0000 No devices ever appear EH02 / PR23 @ 1a30 0000 No devices ever appear EH02 / PR24 @ 1a40 0000 No devices ever appear EH02 / PR25 @ 1a50 0000 No devices ever appear EH02 / PR26 @ 1a60 0000 No devices ever appear Internal hub addresses for EH02 seem to be: EH02 / PR30 @ 1a11 0000 Internal USB (Apple bluetooth card) [uSB2i1] EH02 / PR31 1a120000 ?? (could be an internal USB I am not using) EH02 / PR32 1a130000 Bottom Right of the bottom set. Rear Panel. [uSB2SBR] EH02 / PR33 1a140000 No devices ever appear EH02 / PR34 1a150000 No devices ever appear EH02 / PR35 1a160000 No devices ever appear USB3 ports ——————— Items plugged into the FOUR USB3 ports (front panel left, rear panel secondary block Top right, secondary Top left and secondary bottom left() referred to as USB3FL , USB3STR, USB3STL and USB3SBL never appear in the above list. They all just appear under XHC with no specific ports visible that I could see.
  11. Hello. I have recently installed MacOS-X Sierra on a Dell T5610. This is a dual xeon C602 chipset motherboard. It has a renesas/NEC third party USB3 controller on the motherboard. . When I plug a USB3 hard drive into a USB3 port, it appears under the XHC device using GenericUSBXHCI.kext. It took about 18 seconds to transfer a 720MB file but that may be a function of the drive speed. Is it running at USB3 speed? I have no idea. All the USB ports recognise memory sticks. None of them will work with my webcam which does work on windows or on a real mac so clearly something isn't quite right. I am using a custom DSDT that contains a few renames for port names and a fix to recognise 'Darwin' OS type as an alternative to windows 7. I have written up the install here: http://www.insanelymac.com/forum/topic/331372-write-up-installing-os-x-1012-sierra-on-dell-t5610-dual-xeon-uefi/?p=2577542 I have some issues that I am having trouble resolving. The issue ----------- The main issue I want to resolve is that I can not get the machine to wake up properly from sleep. It goes to sleep just fine. When it wakes up, although the screen comes back on, either the pointer/keyboard don't work - (with some darkwake settings) or the mouse does work but the cursor isn't flashing in the password box and the machine looks to have hung. I have a feeling this might be helped by getting rid of some unused ports that are being injected by USBInjectAll.kext. So. I tried creating a custom SSDT-UIAC-ALL.aml file to remove unused ports. It did remove unused ports, but the USB3 ports all stopped working. I then tried to customise the USBInjectall.kext by editing the information in the .plist file inside the package. This had the same effect. So. Strangely enough, if I even remove a handful of unused ports on EH01/EH02 (which are the USB2 devices) for some reason all the USB3 ports just stop working. I don't know why that is. These ports (EH01 / PR11-PR18) and (EH02 / PR21-26) appear to be allocated with PR11/PR21 being internal hubs. The rest of the ports never have any devices under them in IORegExplorer. When a device is plugged into one of the USB2 ports, it will appear under what looks like an internal port which is numbered in the PR30+ range which itself comes under PR11 or PR21. So I assumed that it was probably ok to remove these unused ports. However, for reasons I can't explain, when I remove even one of them, the USB3 ports on the machine just stop working. I am unable to attach my IORegExplorer.ioreg file or my DSDT.dsl file - the site won't allow it. I don't know why that is. Does anyone please have any detailed information on what I'm doing wrong here? I've wasted a lot of time on this over the last few weeks. There seems to be little documentation about this aspect on the web apart from the ACPI spec and some postings on forums by a very few individuals.
  12. OK. Current situation with this machine. USB3 appears to work. At least, a USB3 G-drive connected to a USB3 port appears underneath port XHC, uses GenericUSBXHCI (using IORegistryexplorer) and transferred a 730MB file in 18 seconds. By my reckoning that's 324MB/s which I believe is still possible under USB2 but since that's the fastest device I have perhaps I had better be content with that. I can not get the machine to work properly from 'wake' whatever I do. It usually hangs OR doesn't recognise the mouse/keyboard. Various combinations of darkwake=0,1,2 and missing have been tried. I have a niggling feeling that I have a problem with the USB configuration on the machine because although it reads memory sticks OK, it will not work with my webcam - that does work on a real mac. I will ask in another thread for ideas. The final configuration at this time is: Kexts installed: AppleIntelE1000e.kext (onboard internet) GenericUSBXHCI.kext (needed to make it boot with USB3 turned on in the BIOS, otherwise it does not boot) USBInjectall.kext (currently injecting all ports - am trying to customise that but running into problems with it) VoodooTSCSync.kext - Required to make the machine run with all CPUs active. FakeSMC.kext - mandatory. FakeSMCACPISensors.kext FakeSMCCPUSensors.kext FakeSMC_GPUSensors.kext FakeSMC_I_PCSensors.kext }all four needed to make hwmonitor.app work and monitor temperature and so forth. Edited the DSDT. I tried to attach a copy but the site wouldn't allow it. The simple edits in the DSDT perform the following: a) Add 'Darwin' to the list of OS that is recognised as an alternative to windows 7. renames port EUSB and UESBE to EH01 and EH02 c) renames port PEX0 (which is the USB3 controller) to XHC d) renames port NPE4 (which was the graphics card) to GFX e) renames EH01 and EH02 internal hubs from HUBN to HUB1 and HUB2 Clover boot flags: dart =0 ; PICRootUID=1 ; npci=0x3000 Clover/ACPI - Generate P States - yes and Generate C States - yes (I need to check whether I actually do need these) I have attempted to customise the ports injected by USBInjectall.kext - first by using and editing SSDT-UIAC-ALL.aml and then, when that didn't work, I edited the plist file within the kext package. However this isn't working for me, when I even remove one unused port the USB3 ports just stop working and I can't work out why that is. More info to follow if I ever get this working properly.
  13. Update on USB3, bluetooth, sleep and wake ---------------------------------------- I have managed to get USB3 ports recognised at least, and it doesn't crash when it starts up. Sleep/wake is improving slowly. DSDT becoming clearer. Will post more information when I'm sure of my facts. Also installed an apple bluetooth/wifi b/g/ac card BCM94360CD with an appropriate PCI-express adapter that I sourced from amazon. The bluetooth and wifi on it worked right out of the box on the Mac. The bluetooth icon appeared in the control panel. The wifi symbol appeared in the top bar and it connected fine. Windows, however, required the drivers from the apple Bootcamp download site in order to recognise the bluetooth controller and hence pair to the apple magic mouse. Stop unexpected crash/exit from OS-X mouse preferences I did come across an interesting problem however when I started to use the magic mouse via bluetooth. This was, that the preferences for 'mouse' started to exit suddenly. I narrowed this down to the system being unable to play the little help video that appears. I'm not sure why that is, at this stage. However, you can work around it by renaming the offending video from the terminal. sudo mv /System/Library/Assets/com_apple_MobileAsset_prefpanes_TrackpadMouseVideos/8d8c589221217f59c640073a8a348ef41934be08.asset/AssetData/MagicMouse.mov /System/Library/Assets/com_apple_MobileAsset_prefpanes_TrackpadMouseVideos/8d8c589221217f59c640073a8a348ef41934be08.asset/AssetData/MagicMouse-fix.mov
  14. Screen stays black after wake-up from sleep

    Seriously. No replies? Bit disappointed that I've had hardly a single response to anything on this forum. Not what I expected...
  15. I recently managed to install OS-X 10.12 Sierra on a Dell T5610. I was unable to find any information on the web from anyone who did it, so I thought I would write it up as a useful guide. I have tried to write it in simple language. I know that I could have personally used this sort of simple information when I started this install.I'm an IT professional and this is my first mackintosh install and it's been an interesting experience - although not helped by the real lack of coherent and organised information on the web. Lots of rumours, guesses, smoke and mirrors. Please bear in mind that this guide was the order in which I did it. There might be a better way - because it was a learning process. So you could probably shorten this. But it will hopefully give hope to anyone trying to do it that it's possible. Things I tried first. --------------------- 1. I tried to install Sierra directly using a bootable USB and clover. Regardless of what I tried, I never managed to get past a white 'no entry' sign with an error 'still waiting for root device'. I gather this is because the machine lost connection to it's USB 2.0 ports half way through the procedure. Software I used Clover bootloader Clover configurator Plus some additional kext files (see below) that I downloaded from the Web. I did not use a certain bad, cartoonish post-install piece of software with a name similar to murderbeast. That's because I found that you wind up with all sorts of files all over the place that you don't want, and it's hard to work out what it's doing. What is a kext? Kext stands for 'kernel extension' and is similar to a Windows driver/Dll in the way it works. Kexts are found in a standard location on the mac os hard drive. Extensions usually go in /Library/extensionsand if they are there then that has the advantage that the mac hoots quicker because they are in the cache, but has the disadvantage that you can't easily get rid of them if it breaks. Some kexts need to be in that location tm work properly. l Kexts can also be injected into the os at boot time by clover and you make this happen by putting them in /efi/clover/kexts (which is in the efi partition of your mac or USB boot drive). This is convenient because you can easily enable and disable kexts from within clover and so it's not so big a tragedy if you accidentally mess up. Certain kexts such as FakeSMC.kext are mandatory to get the install working. Other users will require others according to requirements. For the Dell T5610 the kexts you will need to start with are: FakeSMC.kext USBInjectAll.kext VoodooTxtSync.kext (for your relevant CPU - 6 core/8 core etc) AppleIntelE1000e.kext BIOS on the machine Before I started, I installed the latest Dell BIOS (in my case it was version A14) from the Dell website: http://www.dell.com/support/home/us/en/04/product-support/product/precision-t5610-workstation/drivers I downloaded the BIOS onto a USB2 stick and then rebooted the machine. Then on reboot, hold down F12 and enter the 'one time only' boot menu. Select 'Flash BIOS' and then in the 'choose file' section at the top click on the (,,,) icon and select the BIOS that's on your USB stick. It's an executable (.exe) file that you downloaded earlier. If all goes well, it should be recognised and you should be able to flash your BIOS. Warning. Do not power off your machine whilst flashing the BIOS. It will render the machine unusable and you will have real problems recovering it. So ensure that your power cords are connected and you are not likely to have a power cut! I will not be responsible if you break your machine because you did something wrong. Steps that I followed I installed Yosemite 10.10.5 first. I did that because I gather Yosemite treats USB ports differently than Sierra does with far less reliance on correct ACPI information. Then, I upgraded the settings in clover using clover configurator and upgraded to Sierra 10.12 from within MacOS (i.e. - not using a USB at all). You will need a USB mouse and keyboard plugged into a USB2 port. A PS/2 Mouse/keyboard will not work. You will need an empty drive on your existing PC. I would suggest installing MacOS on an empty additional drive rather than going through the hassle of trying to dual-boot windows and OS-X from a single drive. You should use a 16gb USB 2.0 stick in a USB 2.0 port. There is a difference between USB3 and USB 2 sticks in terms of pinout. On the T5610 I know that the 2 rear (highest) ports next to the keyboard port are USB2 ports I suggest you plug the keyboard and mouse into those. The front panel (far right) port is a USB2 port. I suggest you put the USB stick in that. Stage 1 - Install Yosemite ----------------------------- Create bootable USB 1. Create a bootable UEFI USB of Yosemite on a real mac. 2. Install a clover boot loader to the USB. 3. Mount the EFI partition that was created in step (2) using clover configurator. 4. Ensure that the EFI / CLOVER / Kexts / Other area contains the kexts for: FakeSMC.kext USBInjectAll.kext VoodooTxtSync.kext (for your relevant CPU - 6 core/8 core etc) AppleIntelE1000e.kext Set up BIOS 1. Hold down F12 when machine is starting and then select 'BIOS setup' 2. Ensure that: USB3 is disabled Serial port is disabled Intel virtualisation technology and Intel virtualisation technology for IO is disabled. Set boot to UEFI and select USB stick to be highest in the list. Under POST settings ensure that 'boot speed' is not 'minimal' or 'auto' - it's the 'comprehensive' one you need. Boot into clover bootloader Save the BIOS and try and boot from the USB stick. If all goes well, the clover boot loader screen should appear. Go to 'options' in clover and ensure that: 1. Under 'CPU tuning' you have 'Generate P states' and 'Generate C states' 2. Under 'boot flags' you have nv_disable=1 dart=0 PCIRootUID=1 npci=ox3000 cpus=1 -v What do the flags do? -v (verbose) - turns logging on. cpus=1 (enables only one core. Useful for installing when we aren't sure if we will have issues). You can also use cpus=2, cpus=4 or whatever if you feel like you need to limit the number of cores in some way. nv_disable=1 disables nvida drivers. The machine boots up in a barebones video mode a bit like default VGA mode on a PC. Once you have the correct drivers you can get rid of that. PCIRootUID=1 and npci=0x3000 These are a bit of mystery but they appear to be related to PCI bus initialisation. These values work for the Dell T5610 at least. Attempt to run the installer 1. Go back to main menu and find and boot from the icon that corresponds to your USB stick. 2. If all goes well, you will get lots of lines of debug information and eventually the installer will start. Problems I encountered during my install All these messages are generated in the log you can see when you boot using the -v (verbose) option. 1. Installer hangs at appleFsCompressionTypeZlib Solution: Ensure USB 3 is disabled in BIOS. 2. Installer hangs at PCI configuration Begin Solution: Ensure npci=ox3000 and PCIRootUID=1 flags are set in clover. 3. Installer hangs randomly during boot Solution: Ensure that cpus=1 is set for the install. 4. Installer gives white 'no entry' sign and 'still waiting for root device' is visible in the log window during the install. The screen also gets corrupted but you can just read the text. Solution: Ensure you are using USB 2.0 key, in a USB 2.0 port. If this still doesn't work then you could try modifying the clover install on the USB using clover configurator to add the patches 'Change EUSBo EH01' and 'Change USBE to EH02' (under the ACPI area in clover configurator). 5. Screen goes black on login screen after the 'apple' progress bar. a ) Ensure that the BIOS is not using 'minimal' or 'auto' initialisation on POST but is fully initialising all the hardware. b ) Ensure your graphics drivers are correct if not using a native card like a GTX 6xx series card. Post Install - getting ready to move to sierra --------------------------------------------------- Make new Mac HD bootable and install clover boot loader. Once Yosemite was installed, I installed clover on the drive that I had just installed the OS to. It wasn't difficult and it creates the EFI partition and installs clover for you. I also downloaded 'clover configurator'. Then.in 'clover configurator' use the Mount EFI option to mount the EFI partition of your bootable USB key. Then copy the entire contents of the EFI folder from the efi partition on the bootable usb onto your machine in some convenient place in your documents folder. When copy the entire contents of the partition you should see a folder called EFI and inside that I see folders for 'BOOT' and 'CLOVER'. Next, after the copy, use clover configurator to 'unmount' the USB EFI partition (you shouldn't need it anymore) and then eject and take out the USB stick. Instead 'mount' the EFI partition from the newly installed MAC OS hard drive you just installed. Copy the entire contents of the EFI folder (that you just copied from USB onto your documents folder) into the EFI partition on the hard disk. The objective is for the EFI partition in the hard disk to look 'just the same' as the one on the USB stick. So. When you are done, the 'EFI' partition on the hard drive will contain a folder called 'EFI' which has some sub-folders in it. Download and install carbon copy cloner onto your mac. Use it to back up the 'new Mac hard disk' you just created to another drive. Use clover configurator to mount the EFI partition of the Mac hard drive just installed. Ensure that under /ACPI in clover configurator, the following patches were added: Change EUSB to EH01 Change USBE to EH02 (This is necessary so that the USB 2.0 ports will work in Sierra otherwise you will be unable to log in with no mouse and no keyboard) Ensure that under 'boot' you also have check marks next to: FixPIC FIxUSB AddDTGP USB Generate P States Generate C States Now go to 'Boot' and under there you can set the defaults for the clover boot to avoid typing the annoying flags in there every time you boot. For now, use: npci=0x3000 verbose(-v) nv_disable=1 cpus=1 and add a custom flag of PCIRootUID=1 Exit clover and it will automatically save the clover.plist file with the amendments in it. Test booting from the internal Hard drive. 1. Remove the USB key. 2. Restart the machine. Enter the BIOS. Ensure that the drive you just installed Yosemite to, is visible under UEFI boot options, and is top of the list. 3. Exit and try and boot into internal hard drive running yosemite. If all goes well, that should work and you should be able to boot into Mac OS-X without the USB key. Stage 3 - Upgrading to Sierra ---------------------------------- Download the install Sierra.app onto the 'applications' area of your yosemite install . Ensure the drive is backed up and that the above configuration is done. Remove the USB key - you won't be needing it. Run the installer. If all goes well, the installer will run correctly. The machine may well reboot/restart a few times during the process. I had a few times when it seemed to have crashed and all seemed lost but it worked in the end. So don't be too quick to reset it. Each time the machine restarts, just ensure that it reboots from the internal hard drive. Once Sierra is installed you can work on the post steps to make it better. Post Installation Steps -------------------------- This is a work in progress. So please forgive if this is not totally comprehensive. Graphics and getting rid of nv_disable=1 1. When using nv_disable=1 you are not really using the graphics card properly. It's just being used in 'basic' mode so you can install MacOS and actually see something on the screen. What I did was the easiest option - I went to Ebay and I bought a 100% compatible graphics card and stuck it in the machine in place of the one that was in there. The Nvidia Quadro NVS310 card I had in there I couldn't get to work properly. It wasn't a very expensive card. So I bought an Asus GTX650 on eBay for 25 pounds. I have read that the Nvidia GTX 5xx and 6xx series are 'out of the box compatible' with the Mac OS. I put a new graphics card in there and then once I was happy that it worked, I used clover configurator to remove that entry from the startup. You can temporarily remove it manually to see if it works of course. Note: The Machine is using a VGA monitor as part of a three monitor set and it works... It is possible to use three monitors at once (including a VGA monitor) with this cheap card. The Asus GTX650 works perfectly. In this machine with MacOS. It has three ports. One DVI-D , One HDMI and one VGA. I have three monitors connected to it. An LG 34uc88 QHD connected to DHMI, and two nondescript LCD panels connected to the other inputs, one using VGA and one using DVI-D. The mac recognises all of them and all three work just fine. I didn't expect that, because others in forums have maintained that a VGA monitor would not work 2. Get rid of cpus=1 so you can use all cores. My machine had 2 8 core xeon cpus. It wasn't ideal to be running on one core only. However, it would randomly crash when trying to boot without that flag. To fix it, I had to install the correct version of VoodooTSCSync.kext in CLOVER/Kexts/Other. I tried using a tool I found on this site to create a 'custom' VoodooTSCSync.kext (the tool was called VoodooTSCSyncConfigurator). It didn't work for me. I did, however find a .kext file that did work for me. If you google "common kexts and other downloads for Hackintosh Mark With Tech" you will find the place where I found the VoodooTSCSync.kext file that worked for me. Once installed, I was able to boot without cpus=1 3. Ensure that network works. I ensured that the clover patches (under ACPI in clover configurator) for 'Change EUSB to EH01' and 'Change USBE to EH02' were checked. This was because I used a tool called IORegistryExplorer.app to examine the machine, and I noticed that my USB ports appeared to be called things like 'EUSB' and so forth. Once that was done, network, USB and sound started working much better. I also ensured that the appleIntele1000e.kext file was installed. 4. Ensure that sound works. The HDMI sound works out of the box if you use a compatible graphics card. In order to get the sound working, I used the VoodooHDA.kext to get some sort of sound out of the rear headphone jack. That works, but I also understand that it's a bit of a hack and it's not the best solution. I feel that the machine would benefit from a complete custom DSDT file - but I haven't been able to do that yet. I'll have to read more about ACPI first. 5. Ensure that sleep works. Sleep has been a problem. And it's still a problem for me. I gather that you need graphics, USB and everything to be pretty perfect before the sleep will function OK. The best results that I have had (so far) are so use clover flags darkwake=1 and also ensure that the kext NullCPUPowerManagement.kext is NOT included anywhere. The computer seems to do just fine without that. What happens right now, is that the computer sleeps just fine, and even wakes up with a mouse movement, the monitors come on, but there is no USB mouse/keyboard anymore so it has to be restarted. This is therefore a work in progress. 6. Ensure that USB3 works I have not so far managed to get USB3 working. When it is enabled in the BIOS, it hangs just after AppleFSCompressionTypeZlib load succeeded. If I get further, I'll amend this guide. 7. Ensure that apple magic mouse and keyboard work correctly. To do this, I have ordered a bought an adapter from amazon which converts the Mac wifi-bluetooth card to a PCI card. Then you can buy a mac wifi-bluetooth card on eBay for about 25 pounds, plug it in, and have native bluetooth/wifi support with no issues, use an apple magic mouse and so on. Stage 4 - Dual booting with windows ten ----------------------------------------------- You may wish to dual-boot windows with your install. If you have an UEFI install of windows 10, then there's no problem. You can do that using clover and it will see it just fine. However, if you are running windows 10 and have it running in 'legacy' mode for whatever reason, then you will need to convert the windows install to UEFI before you can dual-boot it using clover (assuming you are using UEFI boot for your Mac install). Converting windows ten to UEFI. It's possible to do this 'in place' without re-installing windows. Steps. 1. Log onto windows 10 (using legacy boot in the BIOS) and make a recovery USB using the tool in windows. 2. Boot from that USB. 3. When the win10 recovery screen comes up, select 'troublehoot' / 'advanced' / 'command prompt' 4. try cd c: then dir.. if you don't see your windows system disk try cd d: then dir and so on... until you find it. 5. Navigate to windows/system32. 6. run mbr2gpt /convert 7. wait for it to finish. (It's quite quick) and then you can restart, go back into the BIOS, re-enable UEFI boot, and select your 'mac' drive with the clover bootloader at the 'top' of the list. Then, when you boot the machine, clover will load, and you will see your PC and Mac installs ready to be booted from. Hiding unnecessary partitions in clover. Once you've done that, you will probably have a bunch of partitions in clover that you don't want to see. You can hide those strange windows partitions in clover by using 'clover configurator' and selecting the 'GUI' tab and then unselecting 'legacy'. Choosing default boot and timeout in clover Whilst you have 'clover configurator' open, navigate to the 'boot' tab and you can select the default boot volume and the timeout before it auto-boots to that volume. Net result ----------- A serviceable dual Xeon 32 thread workstation that can dual boot MacOS and windows. With the above configuration, it's been 100% stable and problem-free. However, as mentioned, I have to live with the issue of not having USB3 and sleep working at the moment. Hope this is helpful. If anyone has any ideas about my 'sleep' problem or how to write a custom DSDT would be appreciated. Many thanks
×