Jump to content

pippox0

pippox0

Member Since 11 Dec 2007
Offline Last Active Yesterday, 06:20 PM
*****

Posts I've Made

In Topic: Its possible install some OS X in this PC?

24 March 2017 - 05:27 AM

First of all you need a patched kernel for AMD CPU, then you can try Mavericks ...

sent from my iPhone

In Topic: Chameleon 2.4svn Official PKG Installer

07 March 2017 - 10:58 PM

Ok boot file attached.

kexts patcher
As I said the kext patcher can now patch prelinked kexts by adding the kext name you are intrested in to kexts.plist. Since last tests I modified the kexts.plist structure and now you have to put your custom patches under "KextsPatches":
attachicon.gifkexts1.pngattachicon.gifkexts2.png

kernel patches
As for kexts you can patch the kernel in kernel.plist under "KernelPatches":
attachicon.gifkernel.png

Remind you that MatchOS, MatchBuild and Comment are optional keys.

NVRAM
Embedded in the boot file, there is a modified version of FileNVRAM.kext, no module. To dump the nvram you have to use NVRAM Dumper Pro.app v1.3+ (attached):
attachicon.gifndp.pngattachicon.gifndp2.png
(making this app to be used in Clover the idea to add back the nvram support in Enoch :D )
Embedded kext is 64bit only and I have a fork of meklort's github repository where I'll add changes soon and make a pull request to Him. So please report back.
(I'm testing it also with real nvram in Clover.. and apparently works well, plus the driver add some missing stuff ;), but for that I've to check more)

Note
Olds FileNVRAM.dylib and KernelPatcher.dylib prevent the internal kernel patcher to do their things but still allow the kexts patcher.
FileNVRAM.dylib if loaded cause the internal nvram stuff in a off state.
Why? Just avoiding conflicts, so you can decide to use one or another, but for this tests mentioned modules shoud be removed.
FileNVRAM.kext if already present in Extra/Extensions, /S/L/E or /L/E should be removed.The one from the bootloader should win against it. Delete it anyway.

Now you can use the NVDIA Web Drivers by adding the relative arg when pressing the relative option in the NVIDIA Web Drivers Manager, or add it manually. Old patch I made is unnecessary and deprecated, deleted!

kernel.plist and kexts.plist attached as example to follow. Other old option are still there.

Please report back!

Very good job Micky1979 !!

sent from my iPhone

In Topic: 80 Core Hackintosh :)

06 March 2017 - 01:19 PM

Very interesting ! :)  Good Luck !

In Topic: Sony Vaio VGN-FZ21M - QE/CI

01 March 2017 - 07:07 AM

@ Iperzampem0,

i have checked the two EDID , they are different, but only in description, all technical stuffs are the same.

Your Edid

  Monitor
  Model name............... t Flat Panel
  Manufacturer............. NVD
  Plug and Play ID......... NVD0600
  Serial number............ n/a
  Manufacture date......... 2002, ISO week 45
  Filter driver............ None

 

Mine

Monitor
  Model name............... t Flat Panel
  Manufacturer............. NVD
  Plug and Play ID......... NVD0400
  Serial number............ n/a
  Manufacture date......... 2002, ISO week 45
  Filter driver............ None

The last byte (checksum) is normal that is different.

 

One interesting Thing i note is : Screen size is wrongly encoded in EDID  14,9" instead of 15,6" , but it is only a cosmetic thing.

 

EDID revision............ 1.3
  Input signal type........ Digital
  Color bit depth.......... Undefined
  Display type............. RGB color
  Screen size.............. 320 x 200 mm (14,9 in)
  Power management......... Standby, Suspend, Active off/sleep
  Extension blocs.......... None

In Topic: Sony Vaio VGN-FZ21M - QE/CI

28 February 2017 - 06:15 AM

Hi,
I re-check my EDID and is exactly the one i have posted in first page.
I have extracted from Windows a long time ago.

Try to extracted it with enTech utility and post the .bin file saved (128bytes)
http://www.entechtai...il/moninfo.shtm

It is very strange that Sony have changed Edid with the same notebook, but BTW it could be.

Yeah, our Edids are different for 3 bytes.

I have tried to fix brightness , (another time) with various methods, but with no success.

You should use color profile manager to create 3 profile with low, medium and high brightness level.

I Just create one and for me is enoght.

I have taken a look at my Bios : i have the same Bios version, but it is with very easy menu, and i can enable/disable only some things like boot from USB.
I have not advanced Bios menu to enable/disable Ahci,Vt+, etc.
Maybe this is Why i cannot boot El Capitan ..??

For Sd card reader, maybe in future we find out the right patch ...

© 2016 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy