Sony VAIO VPCF115FM, preferably Mavericks?

Sony VAIO VPCF115FM, can do Mavericks!

Hello again! I'm so far unsuccessful in getting Mavericks onto my desktop (a Biostar-based box that previously Hackintoshed Snow Leopard), so I'd like to get it onto my laptop instead for now, a Sony VAIO VPCF115FM. Specs are as follows:

https://docs.sony.com/release/specs/VPCF115FMB_mksp.pdf said:

Intel Core i7-Q720 @ 1.60GHz w/TurboBoost up to 2.80GHz, apparently Core 2 Quad Yorkfield/Wolfdale
Intel PM55 Express
Intel 5 Series/3400 Series Chipset Family PCI Express Root
4GB+2GB DDR3/1333MHz RAM

Realtek HD Audio 6.0.1.6045
NVIDIA GeForce GT330M @ 1920*1080

Alps Pointing-device for VAIO
Atheros AR9285/AR9287
Marvell Yukon 88E8040 PCI-E Fast Ethernet

Blu-Ray+DVD/CD writer combo optical drive
Various other Sony bits-and-bobs

Click to expand...

The GT330M is discrete rather than switched.

I was able to get to a Mac that had Lion and convinced the owner to let me download the Mavericks installer to create the bootable USB with. I didn't enable "Laptop Support" in UniBeast because I was originally expecting to only try it with the desktop box.

I have two main issues with my current attempt to Hackintosh my VAIO. First is I get a black screen after the grey Apple screen with the throbber, even if I add the various usual boot switches; is the cause of this the same as this thread and therefore can I follow the same directions?

Second is what is the main difference between enabling Laptop Support through UniBeast versus not? Are there extra kexts and/or DSDTs that would target VAIOs specifically? If that's the case should I simply recreate the bootable USB and would that resolve the first issue?

I've read enough here to know that certain pieces of hardware are hit-or-miss (e.g. Alps Touchpad requires some extra effort, leading me to use my USB mouse, and I can apparently expect my Atheros wi-fi to not work afterwards, leading me to find a hardline or boot into Windows), but for this 2009 hardware are the essentials taken care of enough for me to install and run Mavericks with a reasonable level of performance?

Thanks in advance to anyone knowledgeable who can help resolve my issues!

neologix said:

Hello again! I'm so far unsuccessful in getting Mavericks onto my desktop (a Biostar-based box that previously Hackintoshed Snow Leopard), so I'd like to get it onto my laptop instead for now, a Sony VAIO VPCF115FM. Specs are as follows:



The GT330M is discrete rather than switched.

I was able to get to a Mac that had Lion and convinced the owner to let me download the Mavericks installer to create the bootable USB with. I didn't enable "Laptop Support" in UniBeast because I was originally expecting to only try it with the desktop box.

I have two main issues with my current attempt to Hackintosh my VAIO. First is I get a black screen after the grey Apple screen with the throbber, even if I add the various usual boot switches; is the cause of this the same as this thread and therefore can I follow the same directions?

Click to expand...

For your nvidia, you probably need GraphicsEnabler=Yes, and perhaps additional DSDT patches to make the nvidia recognize the internal display. Sorry, I don't have the details, as I don't have this hardware. Maybe someone else will chime in on the details...

Second is what is the main difference between enabling Laptop Support through UniBeast versus not? Are there extra kexts and/or DSDTs that would target VAIOs specifically? If that's the case should I simply recreate the bootable USB and would that resolve the first issue?

Click to expand...

Laptop support:
- MacBookPro8,1 instead of MacPro3,1
- PS2 kexts in /Extra/Extensions (AppleACPIPS2Nub.kext, ApplePS2Controller.kext)

I've made a bit of progress! Thanks to another thread that mentioned post-Apple black screen (which we should now refer to as PABS ) and external screens, I plugged my TV's HDMI into the laptop and lo and behold the TV displays the installer!

I didn't continue yet because my drive is MBR and Disk Utility didn't let me reformat the unformatted partition I freed for it. I'm going to put another drive, try again, and post later!

Update: more progress and an installation!

• I shrank one of my partitions to free ~110GB, then I ran diskpart to create an HFS partition on my MBR drive (diskpart, create partition primary id=af).
• I then downloaded the Mavericks MBR patch for 10.9.3 and untar'ed it into the installer USB via my old MacBook Pro.
• I booted the installer with GraphicsEnabler=Yes and my HDMI TV plugged in and used Disk Utility to Erase the HFS partition to allow it to become HFS+.
• I then continued the installation successfully!

The hitch comes when doing the post-install MultiBeast config. Choosing EasyDSDT or DSDT-Free in Quick Start results in kexts being installed that completely kill the built-in keyboard and touchpad, requiring me to plug in one of my USB keyboards (I have an old Apple one and a MacAlly one) and a USB mouse to actually do something. I haven't done the research yet to find out which specific kexts those two configs install to kill the built-in devices (EasyDSDT looks to be the same as DSDT-Free but with some extra kexts for legacy systems), but until I do I've been reinstalling Mavericks to restore the functionality of those two devices.

What do I have to uncheck in DSDT-Free to prevent losing built-in keyboard+touchpad support?

I'm also researching at InsanelyMac solutions for getting the internal display (NVidia GeForce GT330M) and audio (apparently Realtek ALC275) to work, so I'm not just sitting on my laurels. If I can at least get internal display working then I can start doing something in XCode and whatnot when I'm not around an external monitor/my TV.

neologix said:

Update: more progress and an installation!

• I shrank one of my partitions to free ~110GB, then I ran diskpart to create an HFS partition on my MBR drive (diskpart, create partition primary id=af).
• I then downloaded the Mavericks MBR patch for 10.9.3 and untar'ed it into the installer USB via my old MacBook Pro.
• I booted the installer with GraphicsEnabler=Yes and my HDMI TV plugged in and used Disk Utility to Erase the HFS partition to allow it to become HFS+.
• I then continued the installation successfully!

The hitch comes when doing the post-install MultiBeast config. Choosing EasyDSDT or DSDT-Free in Quick Start results in kexts being installed that completely kill the built-in keyboard and touchpad, requiring me to plug in one of my USB keyboards (I have an old Apple one and a MacAlly one) and a USB mouse to actually do something. I haven't done the research yet to find out which specific kexts those two configs install to kill the built-in devices (EasyDSDT looks to be the same as DSDT-Free but with some extra kexts for legacy systems), but until I do I've been reinstalling Mavericks to restore the functionality of those two devices.

What do I have to uncheck in DSDT-Free to prevent losing built-in keyboard+touchpad support?

I'm also researching at InsanelyMac solutions for getting the internal display (NVidia GeForce GT330M) and audio (apparently Realtek ALC275) to work, so I'm not just sitting on my laurels. If I can at least get internal display working then I can start doing something in XCode and whatnot when I'm not around an external monitor/my TV.

Click to expand...

Way to start with Multibeast on laptop: http://www.tonymacx86.com/mavericks...-sandy-bridge-ivy-bridge-haswell-laptops.html

It is not that Multibeast is killing your keyboard/trackpad. It is that you're likely not installing any drivers for them. There is no native support for PS2, so you need to add appropriate drivers for them.

RehabMan said:

Way to start with Multibeast on laptop: http://www.tonymacx86.com/mavericks...-sandy-bridge-ivy-bridge-haswell-laptops.html

Click to expand...

I didn't think that thread applied to me since my Core i7-Q720 (or i7-720QM, I don't care which way) is apparently Nehalem, but if you think it will help I'll look it over and give it a shot.

RehabMan said:

It is not that Multibeast is killing your keyboard/trackpad. It is that you're likely not installing any drivers for them. There is no native support for PS2, so you need to add appropriate drivers for them.

Click to expand...

I'm confused now. How is it that my built-in keyboard and trackpad work from installation through every reboot before running MultiBeast, then? I've rebooted up to 3 times after initial installation with keyboard+trackpad working each time, and it's only after installing custom configuration (likely a working kext being overwritten by a non-working kext) through MultiBeast that they're disabled. You've said yourself the Laptop Support option in UniBeast adds some PS2 kexts, and those are probably the working ones. You can see how I've arrived at the conclusion that a working kext is being overwritten, right?

I will continue to research which kext(s) are being overwritten and try out the power management stuff and report back.

neologix said:

I didn't think that thread applied to me since my Core i7-Q720 (or i7-720QM, I don't care which way) is apparently Nehalem, but if you think it will help I'll look it over and give it a shot.

Click to expand...

It is the same but no custom SSDT, GenerateCStates/PStates=Yes instead. And probably/maybe different smbios. Use everymac.com as your guide.

I'm confused now. How is it that my built-in keyboard and trackpad work from installation through every reboot before running MultiBeast, then? I've rebooted up to 3 times after initial installation with keyboard+trackpad working each time, and it's only after installing custom configuration (likely a working kext being overwritten by a non-working kext) through MultiBeast that they're disabled. You've said yourself the Laptop Support option in UniBeast adds some PS2 kexts, and those are probably the working ones. You can see how I've arrived at the conclusion that a working kext is being overwritten, right?

Click to expand...

The Unibeast USB receives PS2 drivers in /Extra/Extensions when you select "Laptop Support". Once you're not booting with the help of the Unibeast USB, those drivers are no longer loaded unless you install them.

RehabMan said:

The Unibeast USB receives PS2 drivers in /Extra/Extensions when you select "Laptop Support". Once you're not booting with the help of the Unibeast USB, those drivers are no longer loaded unless you install them.

Click to expand...

Ah, that makes sense. Just copy them into the install and I'm good, then?

neologix said:

Ah, that makes sense. Just copy them into the install and I'm good, then?

Click to expand...

You should install ps2 drivers appropriate for your hardware. What trackpad is in your laptop? Always use a kext installer (such as Kext Wizard) to install kexts to /S/L/E.

RehabMan said:

What trackpad is in your laptop?

Click to expand...

It's an Alps trackpad. Hardware ID in Win7 says it's attached to ACPI/SNY9011.