Bronxteck

try formating the usb guid with hfs in diskutility then retrying.

i would suspect smbios and serial number. is there any way to pull what you had setup from time machine. also i am not sure if nvram might have anything to do with it since it also store certain keys.

sometimes there is an option in bios for usb legacy booting that allows to boot from usb thumb drives sometimes it's an option like pressing F12 during bios post to select boot medium.

have you tried to set hibernate mode to 0... in terminal ? sudo pmset hibernatemode 0 default apple value is 3

do you have the duallink=yes option enabled in chameleon?

you have to will have to repatch the kernel after every os update

try booting with the flag -xpcm at the chameleon prompt. if it reboots immediately after that then to test the -xcpm flag you will have to patch your mach_kernel. backup your original one first before patching.

glad you have it up and running.

hmm that is weird for GMA usually that happens on nvdia models. is there an EFI string in org. chameleon for some reason?link here what you are using directly if possible or zip and post it.

the app alone is not suffice without it's plugins.

i thought for disk it was ahcidisk=1 debug=8 flags. i am not sure if that still works on mavericks though.

look it the bios info to see if it has nvidia or GMA graphics. then download the appropriate boot pack also look at your screen resolution.

you might have to put the kexts back to see if the drm error goes away. and i think yes you need GraphicsEnables set to yes.

swap hard drives and find out.

well your IntelCapriFrameBuffer values might be different then the optiplex 9010 due to the amount of video ram being allocated to graphics by the hp bios. if it allows you to change the amount of ram or allows for the intel graphics to be set as primary try that. if not you need to play with the chameleon IntelCapriFrameBuffer values till you hit the right one. on the optiplex i think i used =9 that other error about DRM did you have myhack remove problematic kexts during install? if so it might be caused by that. and this is all assuming that your getting stuck at what you posted when booting regular without -x as i am not sure if that's what your trying to describe.

http://ark.intel.com/products/52224/Intel-Core-i5-2410M-Processor-3M-Cache-up-to-2_90-GHz According to Intel document your core has hyper threading. 2 physical cores 4 virtual, = two virtual cores per each physical core.

hmm i need to see if this works with an Sierra Wireless AirPrime MC8355 that came with my HP. i think it is also called a gobi 3000

yup... you probably need to inject your graphics into your DSDT.

run myhack again and choose install Extra folder option.

google maciasl app and extract the dsdt then patch it?

ahh chameleon options

you can try extracting your dsdt with maciasl app and applying this simple PNLF patch # Brightness control fix into device label PNLF remove_entry; into scope label \_SB insert begin Device (PNLF)\n {\n Name (_HID, EisaId ("APP0002"))\n Name (_CID, "backlight")\n Name (_UID, 10)\n Name (_STA, 0x0B)\n }\n end;

i think he is referring to the flag arch=i386

do you have more then 1 fakesmc installed like maybe in S/L/E?

no the new version of my hack should be fine if you used the manual image restore way. it only messes up if you use my hack to make the snow leopard installer directly.