Search results

[DSDT/SSDT] syntax err: unexpected PARSEOP_NAMESEG I guess I fixed it. I applied the [gfx0] Cleanup/Fix Errors (SSDT) patch from Rehabman's laptop patch repository. Now there are no more errors.

Hello everybody, I'm currently patching a DSDT w/ corresponding SSDTs for an ASUS N750JK (it is not for myself). The system information is as follows: - Intel® Core™ i7 4700HQ Processor - Intel® HM86 Express Chipset - Intel® HD Graphics 4600 - Nvidia GeForce GTX 850M (switching technology) -...

I'm still a student (halfway second year), so I also need to learn (especially about how people create patches for Clover and how they discover them in the first place), but I am willing to learn it (may it take some time) and, some way or another, pass it on to others. I also want to thank you...

First and second paragraph: Sounds really promising! I'm already sometimes taking a peek inside your repository for new changes ;) Third paragraph: I fully understand that and I even did not miss my 'external' graphics card at all while driving 2 or 3 screens when developing (I do assume that...

I guess it will. I need to look at it first to decide whether I can do this time wise (also because of the support that will be needed). Anyway, I will also be shortly experimenting with Swift at University, so perhaps I can spice some things up later on as well. But that all needs to be seen...

Thanks. That hot patching seems interesting, but when I do it I will continue the 'legacy' way for a while, whilst researching this method :) I'll send nguyenmac a PM regarding this ;)

Hello, I would like to know with what program exactly the ProBook installer was written as I might (very maybe) consider to take it over and (maybe) even rewrite it so that all kexts / patches are fetched from online resources dynamically and even create an offline installer as well (for hacks...

Solved For everybody who has the same issue as me: All is resolved. The video chip needed a reball (very strange, as the laptop was always free of dust and never got that really hot). I replaced the heat-conducting pad with Ceramique 2 cooling paste just to be sure. I think that it is a very...

HP 4740s TPM Module... Hello, After setting up pre-boot authentication in HP ProtectTools on the Windows part it won't boot anymore. It freezes at the point where it should pick up the SSD and go into Clover. I also cannot get into the BIOS (F10) and the boot selection screen (F9), because it...

Thanks for that. Sorry for the late reply. --- So out of the blue I downloaded the installer from nguyenmac and installed it (Clover rev. 30xx) and it is working! I can boot like I can with my older revision! I did regenerated the config and put back my smbios and some other files, like...

Still not resolved the issue, but I do have a somewhat offtopic question (a quick one): Which name do I need to put by the OEM folder if I would like to create a multi-system EFI partition? From the log I posted earlier it looks like it should be HP ProBook 4740s, but I'm not 100% sure. You said...

Updated BIOS and re-patched DSDT & SSDT, but still the same. All other systems at home don't have issues running newer versions of Clover. Really weird :S Well, maybe I should contact Clover developers?

I followed the guide to the letter when I was installing Mavericks about 6 months ago and the problem was there then also. So I know a fresh install won't help. I also installed Yosemite from a fresh one (wiped whole SSD), but still the same. Could it be the BIOS version?

I always restore by booting from my USB pen drive with Clover on it and the Yosemite installation, after that you can go to Tools -> Restore from Time machine backup. You can find this in the menu. You connect your drive where the backup is located and this way you can restore your entire...

Unfortunately the lowmemfix driver doesn't work. Here is my current CLOVER folder zipped (in the attachment). EFI/Boot contains still the old BOOTX64.efi file of r2747 (not included), otherwise I won't be able to boot into Yosemite. If I choose CLOVERX64.efi via boot menu (boot with EFI file)...

Thanks for the info, but I was already aware of the instability issues :) Thanks again for sharing! Will report back with what I tried :)

Ah, thanks for the pointer. This doesn't install it in EFI I presume? This gives me a bit more flexibility. Thanks again, comes in handy with this kind of tasks :thumbup:

Mind to share your version of Aptiofix? :)

Ok, here's some more news. OSXAptioFix... driver works only on older revision. LowMemFix... driver doesn't work on both revisions (I only get the stuff to see what was in my first post). It also didn't matter whether I used slide=0 or not. So, seems that LowMemFix doesn't work for my system...

Thank you for the quick reply. I reset the BIOS settings 5 times and I checked DEP option and that was good (has a tick in it). I can now boot again with my normal settings for some strange reason, but only on 2747 or older revision again (pfew). At least it's bootable again lol :D Will try...