- Joined
- Oct 24, 2015
- Messages
- 7
- Motherboard
- Dell
- CPU
- Intel
- Graphics
- nVidia
- Mac
- Classic Mac
- Mobile Phone
Beginner trying to get my feet wet. Thank you for the excellent guides and resources here. It's been an adventure-trying to get El Capitan on Dell XPS 8300 Core i7, 12 GB RAM, GeForce GTX560Ti (OEM)-trying first on external USB drive. Clover (first from here and then updated online on EFI partition -which I have to mount every time before I tinker with the config.plist)-Legacy mode. Unibeast USB thumbdrive will avoid infinite reboot only with 'nv_disable=1' flag but beyond that I was able to install and boot clover and then the OS on the 1 TB WD Passport (incl. getting an old Broadcom kext for the Ethernet) and all is good except that it reboots without any obvious KP message unless I use the "nv_disable=1" flag. Usually it comes to a line about 'Apple ACPM false' or something to that effect and then reboots. If I try any of the other boot flags or inject NVidia etc (SMBIOS got it set up as iMac 13,1), then it produces sometimes 'P state stepping errors', so I quit trying other flags. Also when I try to run the audioclover patch for my on board Realtek (0887), terminal gives message about "Inherently unstable" IOreg missing Apple HDA etc and terminates without doing anything. I read through several posts with folks who had similar boot issues, but not able to find a similar situation with El Cap (incl. trying PCIRootID=1 flag which I understand does not apply to Clover anyway). Incidentally, when I get into system properties, oftentimes the card is correctly identified but other times it is listed as NVidia chip 3 MB or something similar. So I think the OS's native drivers seem to recognize the card at times even though the monitor resolution is not set correctly. Very rarely I got it to boot with 'cpus=1' and then it looks gorgeous with the full 1080p resolution on my Dell UltraSharp monitor. But now the 'cpus=1' trick does not work after I updated clover although one good thing is that now the P state error messages have gone away...so close and yet I am afraid I'm slipping away...
Any thoughts and input would be greatly appreciated.
Dan
Any thoughts and input would be greatly appreciated.
Dan