Contribute
Register

Yosemite installation on Sony Vaio SVE1511P1EW

Status
Not open for further replies.
Joined
Aug 16, 2014
Messages
3
Motherboard
Sony VAIO SVE1511P1EW
CPU
Intel i5-2450M/HM76
Graphics
Intel HD Graphics 3000, 1366x768
Mac
  1. 0
Classic Mac
  1. 0
Mobile Phone
  1. Android
hey guys,

I'm trying to install OS X Yosemite on my Sony Vaio SVE1511P1EW laptop (specs: http://www.sony.co.uk/support/en/content/cnt-specs/SVE1511P1E/list), but the installation always stops at [IOBluetoothHCIController][start]-- completed. I tried various boot flags, but it always stops there.
Is there anything I could do to install OS X? Thanks in advance!
 
hey guys,

I'm trying to install OS X Yosemite on my Sony Vaio SVE1511P1EW laptop (specs: http://www.sony.co.uk/support/en/content/cnt-specs/SVE1511P1E/list), but the installation always stops at [IOBluetoothHCIController][start]-- completed. I tried various boot flags, but it always stops there.
Is there anything I could do to install OS X? Thanks in advance!

Please provide complete details in your profile/signature
(Profile/Settings link in upper right corner of this site)

System: manufacturer/model
CPU: detailed CPU model + motherboard chipset
Graphics: all graphics devices + laptop internal screen resolution

For example, typical Ivy laptop:
System: HP ProBook 4540s
CPU: i5-3320m/HM76
Graphics: HD4000, 1366x768

Use CPU-Z on Windows to find CPU (Core iX-xxx) and motherboard chipset (HMxx), and graphics capabilities. For a laptop, these details are important and affect critical installation procedures.
 
okay, I updated everything that was available in the drop-down-menu, but because some things were missing, here they are:
System: Sony VAIO SVE1511P1EW
CPU: i5-2450M/HM76
Graphics: HD3000, 1366x768
 
okay, I updated everything that was available in the drop-down-menu, but because some things were missing, here they are:
System: Sony VAIO SVE1511P1EW
CPU: i5-2450M/HM76
Graphics: HD3000, 1366x768

In your profile, please... Look on each post under your user-id... that is your profile.
 
okay, I updated everything that was available in the drop-down-menu, but because some things were missing, here they are:
System: Sony VAIO SVE1511P1EW
CPU: i5-2450M/HM76
Graphics: HD3000, 1366x768

You have a mixed system.

Mixed Systems

If you have an Ivy CPU with a 6-series board (rare) or a Sandy CPU with a 7-series board (not as rare), you will probably have difficulty reaching the installer even if you provide the correct ig-platform-id. This is because the graphics drivers are dependent also on the driver for the Intel MEI device. The Apple has factored these drivers does not allow for a mixed system because the MEI driver for 6-series boards is in the same kext as for HD3000, and the MEI driver for 7-series baords is in the same kext as for HD4000. It is not possible to load the framebuffer for HD4000 to get the MEI for a 7-series board when you have HD3000 on a 7-series board. Similarly, it is not possible to load the framebuffer for HD3000 to get the MEI for a 6-series board when you have HD4000 on a 6-series board.

In order to account for this problem, the Info.plist files need to be modified so that the 6-series MEI loads when you have HD3000 on 7-series, and 7-series MEI loads when you have HD4000 on 6-series. If you're thinking this is a bit sketchy you'd be right. It should be obvious that the driver for 7-series MEI may not work properly with the 6-series MEI device, and similarly, that the driver for 6-series MEI may not work properly for the 7-series MEI device. Perhaps there is some instabilty caused by this, but it does seem to work.

Having a mismatch will cause the graphics drivers to hang (or is a very long delay). You will also see verbose logs about duplicate kexts and the inability to load HDCPCtrl because of these duplicates.

To work around this problem, we use DSDT patches to inject the device-id of the correct MEI device for the graphics driver that will be in use.

Extract native DSDT with Linux (/sys/firmware/acpi/tables/DSDT) or Windows (RW-Everything).

HD4000 on 6-series: https://github.com/RehabMan/Laptop-DSDT-Patch
Apply: "HD4000 on 6-series"

HD3000 on 7-series: https://github.com/RehabMan/Laptop-DSDT-Patch
Apply: "HD3000 on 7-series"

Note: Please read the README so you know how to use MaciASL and the laptop DSDT patch repository.

Place at /Extra/dsdt.aml after creating your USB. And for your final install.

Note that if you had HD3000 on 7-series with a high resolution display, you would need to do both the patch previously mentioned for "HD3000 High Resolution" and for "HD3000 on 7-series"
 
I have a Sony Vaio SVE17127CXB and it has an Ivy CPU (i7-3632QM) on a 6 Series board just as you said. I could not boot the installation directly, but I was able to install OS X using another Hackintosh that required very little DSDT edits. Once the installation was complete I put the drive back in the Vaio and was able to boot the system using Clover EFI in SafeMode with the npci=0x2000 Kernel Flag, InjectEDID, InjectATI, LoadVBIOS, DualLink=1, FBName=Pondweed, and VideoPorts=3. Nothing will work properly, but you should get to the desktop. (You'll also need the GenericUSBXHCI.kext to boot without DSDT hacking)

I took an extra step and practically rewrote the DSDT just to make it readable and get most of the devices to load properly; I have never seen so many Scopes in a DSDT before (Someone at Sony should be shot for such terrible coding). Moreover, Sony did a number locking out all the BIOS options which makes it harder to get the system to function the way you want it to. (I did find a blog that showed how to hack the BIOS, but after doing so I wasn't brave enough to flash the new UEFI BIOS without being able to restore the original) :S

Basically, the Intel HD 4000 graphics is locked out, or not present, leaving just the rebranded AMD Radeon HD 7650M graphics controller...

Decoding the VBIOS revealed:

ATOM BIOS Rom:
SubsystemVendorID: 0x104d SubsystemID: 0x908a
IOBaseAddress: 0x5000
Filename: BR41586.023
BIOS Bootup Message:

Sony/Wistron Z70CR ThamesPro DDR3

PCI ID: 1002:6841

Connector at index 0
Type [@offset 44962]: LVDS (7)
Encoder [@offset 44966]: INTERNAL_UNIPHY (0x1e)
i2cid [@offset 45036]: 0x96, OSX senseid: 0x7

Connector at index 1
Type [@offset 44972]: HDMI-A (11)
Encoder [@offset 44976]: INTERNAL_UNIPHY1 (0x20)
i2cid [@offset 45059]: 0x90, OSX senseid: 0x1

Connector at index 2
Type [@offset 44982]: VGA (1)
Encoder [@offset 44986]: INTERNAL_KLDSCP_DAC1 (0x15)
i2cid [@offset 45086]: 0x97, OSX senseid: 0x8


So, I patched the Pondweed Framebuffer in the AMD6000Controller.kext (I couldn't get Clover EFI to auto patch the kext for me, so I used HexEdit and patched the binary manually for lack of a better method)


Native Pondweed Framebuffer (3) @ 0x9ea30
LVDS, DP, DP
02000000000100000901010010000505
00040000040300000001020011020101
00040000040300000001030021030202

Patched Pondweed Framebuffer (3) @ 0x9ea30
LVDS, HDMI, VGA
02000000000100000901010010000507
00080000040200000001000011020401
10000000100000000001000000000008


Furthermore, I used this DSDT injection:


Method (_DSM, 4, NotSerialized)
{
Store (Package (0x0E)
{
"AAPL,slot-name",
Buffer (0x07)
{
"Slot-1"
},
"device-id",
Buffer (0x04)
{
0x40, 0x68, 0x00, 0x00
},
"@0,name",
Buffer (0x0D)
{
"ATY,kPondweed"
},
"@1,name",
Buffer (0x0D)
{
"ATY,kPondweed"
},
"@2,name",
Buffer (0x0D)
{
"ATY,kPondweed"
},
"model",
Buffer (0x13)
{
"AMD Radeon HD 7650M"
},
"hda-gfx",
Buffer (0x0A)
{
"onboard-1"
}
}, Local0)
DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
Return (Local0)
}

I have bootable graphics, no QE, but atleast the graphics controller loads showing the correct VRAM (was just shows 7MB befdore). Strange thing is now it shows different Framebuffers in IORegistryExplorer under the AMD6000Controller ("ATY,Gibba","ATY,Muskgrass", and "ATY,Lotus"). I am still trying to get the QE working, Atheros 9285 Wifi card, and a few other things. My ethernet works on boot with Realtek's AppleRTL8169Ethernet.kext, but it doesn't work when plugged in after boot. I haven't been able to resolve all the DSDT issues myself, but I have come a long way. The Synaptics trackpad works great with the VoodooPS2Controller... I think my sleep state is glitchy somehow because occasionally I have to click the left trackpad button one time to free the pointer; not sure what is going on there. Maybe someone smarter than myself can see what I have overlooked.
 

Attachments

  • SONY.aml
    42.4 KB · Views: 159
  • DSDT.aml
    42.6 KB · Views: 196
  • dmesg+kextstat.txt
    18.1 KB · Views: 184
I have a Sony Vaio SVE17127CXB and it has an Ivy CPU (i7-3632QM) on a 6 Series board just as you said.

Assuming you have both HD4000 and Radeon, you might want to read post #6.

The discrete graphics capability in a switched dual-GPU configuration is not supported with OS X on hacks. Best you can do is disable the discrete part with SSDT/DSDT patches.

You can do the IMEI fixing via Clover config.plist if you know how. I plan to write a similar article for Clover, but for now, I would suggest borrowing from the ProBook Guide a bit...

For using Clover, I suggest you read here: http://www.tonymacx86.com/hp-proboo...-install-yosemite-hp-laptops-clover-uefi.html. Filter appropriately as some information is HP ProBook specific (omit HPFanReset.efi, most of the stuff in the ProBook Installer, for example).

ally rewrote the DSDT just to make it readable and get most of the devices to load properly; I have never seen so many Scopes in a DSDT before (Someone at Sony should be shot for such terrible coding).

It is typical. And Sony isn't writing this code anyway. I would guess that DSDT is not hand coded, but computer generated from various config files, such that DSDT gets customized for each OEM by the BIOS provider.
 
Thanks for the advice, I will see if I can make it happen using that guide.
 
Status
Not open for further replies.
Back
Top