Jump to content

Bronxteck

Administrators
  • Posts

    5778
  • Joined

  • Last visited

  • Days Won

    124

Everything posted by Bronxteck

  1. i really do not see anything wrong that would cause your issue... are you using a dsdt? maybe it needs a backlight fix? or what happens when the screen goes out? have you closed the lid let the machine sleep then open the lid to see if it comes back?
  2. -f loads all s/l/e and e/e kexts... why you have to use it if you have a kernel cache generating i am not sure. have you repaired your disk permissions with disk utility.
  3. use console app and see if cache generation is timing out. if so then you need to see what kext is causing it. many times it is caused if you have AppleACPIPlatform.kext in E/E and also still have the original one in S/L/E. you would need to backup the original to somewhere for safe keeping incase you need it ever and the remove it from S/L/E. after that run a myfix. the version of AppleACPIPlatform.kext that does not break cache generation in E/E needs to be Version 1.3.5
  4. well according to the log com.apple.driver.AirPortBrcm43224 caused the issue so remove it and run a my fix. our boot pack does not come with wifi kext.
  5. re run EDP and build for your model again. just incase something did not transfer well.
  6. repair your disk permissions with disk utility. bad permissions can cause weird problems.
  7. try reseating the ram.... it might have dust on the contacts or there not sitting correctly make sure the locking tabs are in the correct position.
  8. if it's x3100 gma graphics it also happens to real macs with that graphics card. you should also watch your temps the fans might be clogged or need new thermal paste on your cpu and or gpu
  9. if you see a sticker on the laptop that says centrino it most likely is an intel wifi unless it's been replaced. and as such is not supported in osx properly.
  10. AppleACPIPS2Nub is for the ps2 type kexts like for trackpad and ps2 keyboard. if your using usb keyboard and mouse you can remove the kext from e/e at least that might get you going.
  11. not really no. but the modules go in the modules folder in E/E. but the are in chameleon svn trunk.
  12. have you tried the chameleon modules like the acpipatcher dylib?
  13. i do not trust those bench mark apps... if it's truly for a definitive answer how is it you run it as many times as you want and you get a different score each time? i think there just to have a rough idea. why the variances. go by your gut feeling does it feel any better then before. also for the MBP5,1 smbios to give you the most if you have an Nvidia model you have to remove 3 kexts from e/e, Voodoopstate/nullcpu, and sleepenabler... make sure P and C states are enabled for generation in your org.chameleon.Boot.plist
  14. whenever you edit E/E or S/L/E you must run a myfix.
  15. if it's an intel wifi turn it off in bios or remove the card. but that error is usually common in the boot log. if you have a intel centrino sticker on the laptop then you most likely have intel wifi.
  16. i did some testing with Hervé today. Can you use an smbios for a MacBookPro 5,1 on either your d630 or d830 if they are nvidia models? It improved our graphics acceleration on the d630 nvidia. We were able to even remove the the emulated pstate kext and use native power management.
  17. try the boot flag dart=0 it might get you past. then you probably need file/Extra/Extensions/AppleACPIPlatform.kext version 1.3.5 you have to backup and relocate the one in S/L/E in other words remove it from that directory and run a myfix if you do not remove the native one from S/L/E it will not generate a kernel cache. the file should be in edp and or it's boot packs.
  18. if your already in the installed os then install edp and build
  19. maybe try different smbios files. like MacBookPro3,1 /4,1/or 5,1 and see if it helps.
  20. you can also try the D630 nvidia bootpack. as for usb try different usb ports. like bottom right one
  21. now you have to install edp app and build for your model? the first part requiring the bootpack is just to get the os installed.
  22. you should have tscsync.kext in extra or boot with cpus=1 flag i see you mention your bootpack but have you tried ours?
  23. you should be able to boot the original extra folder if needs be by booting with the chameleon flag Extra=orginal_extras -f -v or whatever you named it exactly... but yes when changing an Extra directory like that run a myfix
×
×
  • Create New...