Search results

This worked. Could install Sierra. However, I 'forgot' to install the NVDAStartup kext with kextbeast - it could not boot from the install disk. No problem I thought; lets just boot from USB. Well, same NVDAStartup kernel panic. Edit: Disabling Nvidia inject allows me to boot. However, no...

Hahah oh well... So how now further? :P Trying the following, reporting in a sec -> https://www.tonymacx86.com/threads/solved-nvidia-geforce-gtx-260-sierra.202912/

Yeah, I noticed that but I am 100% sure I did not make a typo. If you look closely at other words in my kernel panic, they are messed up as well.

See attachment for the panic while booting with nv_disable=1. Edit: some info that might be useful: my hack does not detect my USB if I put it in one of the (USB 2.0) ports. However, if I connect the USB to my keyboard which is also a USB hub, it does. Edit2: somehow it does now.

Same result, unfortunately.

Sorry I am mistaken. I ment I could boot to the Clover screen just fine. This is something I couldn't when I tried to update clover at first, instead of making a USB instaler. Booting via my new USB to either the installer or my current El Capitan installation gives the kernel panic above...

So, this is what I tried. Booting from USB works - I get to the Clover boot loader screen. However if I try to boot the installer, I get the following error: (see attachment) Any suggestions?

Thank you. Will be trying that tomorrow. ;-)

That exactly is my problem. I can not boot with the new version of Clover. I can boot to the boot loader just fine, but booting into my El Capitan installation gives the kernel panic. To extract my EFI folder I attached above, I booted via USB using an older version of Clover which can boot...

Thank you. Attached EFI folder. EDIT: Will be trying the following: If it's a panic in a AppleUSBUHCIPCI.kext or AppleUSBXHCIPCI.kext: Try adding a DSDT.aml to EFI/CLOVER/ACPI/patched/ if you have one If it's an X58 chipset, try these settings in config.plist (the same may also work for P35...

Unfortunately, it does not. Quite stuck at the moment, can't seem to figure it out! EDIT: Also I want to point out that my system worked perfectly fine on the older Clover version. Would you like me to attach my EFI folder / config.plist?

I went through my whole BIOS twice, but I can not seem to find it... Asus P6T SE. It is quite an old MB.

Thank you for your reply. Booting with the new FakeSMC kext gives the following panic: Booting with the new FakeSMC kext and safe mode gives the following panic: Sorry for the images being rotated. If you click on them and go to the attachment page, it will be fine. I just removed the...

I recently updated my Clover version to the newest version available because I would like to update my current El Capitan installation to macOS Sierra. I downloaded Clover from source forge, ran the update program on my current SSD and tried to boot. I get the following error: (see attachment)...

Thanks for the answers. Will try and report back if I have any troubles. Cheers! Edit: I copied my EFI partition to my USB to use my USB as test drive for the update. Used MacMan's .PKG to update. It boots fine to the Clover bootscreen. However after I try to boot my MacOS partition, I get the...

Currently running Yosemite. Would like to update to Sierra, but Clover has to be updated. How can I properly update Clover to a newer version and keep my current settings?

I patched my DSDT with the Skyale 0x6D instant wake patch and rebooted with -gux_defer_usb2. Sleep still does not work. All assertions are '0'. Is there a way to disable ANY (internal) usb input while the laptop is asleep? So I can make sure the Wifi/BT card & the touchscreen aren't...

Setup: Lenovo Yoga 700 14isk. Intel HD520. Skylake Intel core i5 6200U. Problem: Sleep is not working. When manually putting the laptop to sleep (Apple -> Sleep) the display turns off and the fans keep spinning. Power led stays white.

I have patched my DSDT and all SSDTs with the GX0 to IGPU patch. Sleep however still does not work. I will probably do a new extract and patch my DSDT again because of the mistakes in my current one, and try a different SMBIOS.

And that exactly is what I have done wrong - thank you.