Jump to content

Sony Vaio VGN-FZ21M - QE/CI


96 posts in this topic

Recommended Posts

After installation, make sure to:

  1. copy the Extra folder from your USB installer to your OS X installation.
  2. copy your add-on kexts to /L/E, to repair permissions and rebuild your cache. that way, you won't need KernelBooter_kexts=Yes (nor -f of course). 

If you play/experience with kexts, always do so in /L/E but always leave /E/E untouched (or only add kexts there once tested and proven). This way, you can always recover by booting with KernelBooter_kexts=Yes -f which injects kexts from /E/E but ignores /L/E.

After installation, make sure to:

  1. copy the Extra folder from your USB installer to your OS X installation.
  2. copy your add-on kexts to /L/E, to repair permissions and rebuild your cache. that way, you won't need KernelBooter_kexts=Yes (nor -f of course). 

If you play/experience with kexts, always do so in /L/E but always leave /E/E untouched (or only add kexts there once tested and proven). This way, you can always recover by booting with KernelBooter_kexts=Yes -f which injects kexts from /E/E but ignores /L/E.

 

Thank You, I have seen that I need to boot with GraphicsEnabler=Yes and the bad thing is that I don't have neither the keyboard nor the trackpkad working and I just have an external mouse.

Can I inject the proper kexts while booting or do I need to re-do the install process?

EDIT: LOL if I say to you guys the crazy thing I did you'll laugh a lot  :thumbsup_anim:

I've installed the app Typeeto on the MacBook Air I'm actually typing from (and making all the stuff) which let me share the keyboard of my Mac via Bluetooth and BT is one of the few things working natively on the VAIO  :D Practically I was able to finish the first setup! Just wow!

 

EDIT2: I still have to copy kexts/folders because I'm trying to see what works and not. Basically the good thing is that the Nvidia 8400M GT is fully recognised and working, also the Intel Core 2 Duo at 2.5Ghz and the 4gb of RAM, along with the Bluetooth and all of the other USB ports and the CD/DVD/BD reader/writer.

The other things like *mostly* the keyboard, ALPS touchpad, Sigmatel or IDT audio, Ricoh webcam, etc. are not working.

Hello again, I have to report a few more developments.

 

--> I've installed Enoch 2848 into the internal SSD so I got rid of the external USB boot;

--> I've copied all the necessary kexts into /Library/Extensions and rebuilt the cache (so now /Extra/Extensions is empty and KernelBooter_kexts=No);

--> Now all these things are working: Audio, Keyboard, Touchpad (just the mouse pointer works, without the single tap to click and scrolling).

 

So what, now?

 

--> Even though the Nvidia 8400M GT is fully recognised I think that QE/CI is not enabled at all and also the Monitor tab inside the Settings is not accessible (and is registered as a 14,9" monitor instead of 15,6"); but above all I can't change the screen brightness neither from settings nor from the keyboard shortcuts (where just the audio disabling works).

 

--> When booting, I always get this message from the bootloader after having chosen the disk:

header read size 200

 Incorrect image signature, expected version 10.7

What should I do? If I just press enter or any other key on the keyboard, it boots correctly.

 

--> From "About this Mac" I have seen that the Samsung 830 SSD is correctly recognised but TRIM is disabled;

--> Ethernet, Ricoh webcam, SD/MemoryStick reader,  are still not working. Not to mention the Intel WiFi 4965agn which will probably never work.

--> The bluetooth seems to work fine but I can't disable it from Settings (if I want to disable it, I just have to use the manual switch).

 

I'm really open to further suggestions from all of you to further improve this awesome setup.  B)

Thanks again for your help!

 

EDIT: I've also seen that the audio doesn't change automatically if, for example, I plug in the headphones. Always need to change the output source from the audio menu and/or from the Settings. Not a big deal, just reporting. I'm using the two kexts AppleHDADisabler and VoodooHDA.

Also I can't use the volume and play/pause buttons on the Apple headphones.

post-290784-0-62740800-1487847864_thumb.png

post-290784-0-14121700-1487847874_thumb.png

post-290784-0-26535200-1487847882_thumb.png

post-290784-0-22821500-1487847896_thumb.png

post-290784-0-38552400-1487847907_thumb.png

post-290784-0-99704000-1487847914_thumb.png

Hi,

The info of 14,9" monitor instead of 15,6" ,may be related to the smbios.plist you have used .... try another one

 

To verify if QE/Ci is enabled use VideoHardwareInfo

VideoHardwareInfo.zip

 

Yukon2.kext must have the right id in info.plist

Find it with DPCIManager

https://sourceforge.net/projects/dpcimanager/

 

To enable TRIM

run terminal and insert "sudo trimforce enable"

 

 

for SD/memory Stick reader

Try this

http://www.insanelymac.com/forum/topic/312536-voodoosdhc-sd-card-reader-for-el-capitan/

 

 

One Question:

Which is your Bios version ??

 

Seee Ya

To verify full graphics acceleration, you can simply launch DVDPlayer and go to Help->Show Supported Features. Everything (except possibly HD) is enabled with full QE/CI. Afaik, you'll have no brightness control on this nVidia GPU. What you need to get built-in LCD recognized as such is add the usual PNLF device to your DSDT.

 

To get rid of the message you get at startup, use Terminal to disable hibernation and delete the sleepimage:

sudo pmset -a hibernatemode 0
sudp pmset -a hibernatefile /dev/null
sudo rm -f /var/vm/sleepimage

If you want to disable/enable your BT module (for instance through the Finder's bar icon), you'll have to patch your relevant Bluetooth controller kext once you've identify it; this can be done through FakeSMC's Info.plist tuning, like AGPM tuning (to get GPU throttling). More details on these here and here.

 

NB: I advise you to keep a copy of all working kexts in /Extra/Extensions for recovery purposes. This way, if you mess with kexts placed in /L/E and screw up the cache, you'll be able to recover with KernelBooter_kexts=Yes -f. Now, I say this, I say nothing... 

Thanks to both of you for the answers.

 

I was trying to get some WiFi USBs to work but I just wasted time because I have 2 old dongles and the drivers aren't compatible. Fortunately I've done all the things correctly and removed all the unnecessary stuff to let me continue with the progress here.

 

Regarding the GPU, it's all enabled!  :yes: But how can I add PNLF to DSDT, I mean do you have some suggestions or a simple guide?

I can confirm that the error message while booting disappears after having used those terminal commands, thanks!

 

I've also enabled TRIM. I'm not so sure to try that Voodoo kext for SD card reader because of the "bad" reports from other users on El Capitan.

The Bluetooth device is a BCM2046. The BIOS version is the stock R1120J7 where in reality I had enabled VT-x (now disabled), AHCI, DEP (data execution prevention).

 

N.B. I've also experienced a completely messed screen (like with big squares green and red) after waking up from sleep. I was expecting a bad behaviour though...

Is the SD card reader Bluetooth or PCIe? If PCIe, you could try the DSDT patch to declare compatibility with Apple's own device 14e4,16bc though there is little success outside O2 Micro readers... VoodooSDHC might be your only solution despite the fact that it often break sleep (or wake).

 

Re: PNLF, I expect you're missing the following:

       Device (PNLF)
       {
            Name (_HID, EisaId ("APP0002"))  // _HID: Hardware ID
            Name (_CID, "backlight")  // _CID: Compatible ID
            Name (_UID, 0x0A)  // _UID: Unique ID
            Name (_STA, 0x0B)  // _STA: Status
            [...]
        }

Post the DSDT you use + a zipped copy of the saved output of IORegistryExplorer +  a zipped copy of a saved output of SysProfiler.

Well... the Sony has a "MemoryStick Duo + SD card" reader which is "internal" so it's not bluetooth --> it's a Texas Instruments (Vendor 104C, Device 803B).

BTW here's the zip, thank you again for your help.

Files.zip

Hi,

For Ethernet card, you can insert this info.plist  in Yukon2.Kext inside IONetworkFamily.kext.

Copy from /L/E to desktop, Patch it and Install back to /L/E with kext utility

 

This is for Marvell Yukon Ethernet card 88e8055

attachicon.gifInfo.zip

 

Thank you! I'm gonna try it, but don't we have the Marvell Yukon 88E8036 instead?

What about the webcam?

Try this for built-in LCD as a proper laptop (backlight) display.

DSDT_HD.aml.zip

 

Webcam is natively detected and reported as USB UVC VideoCamera in SysProfiler (ven/dev=0x05ca/0x183b, i.e. 1482/6203 in decimal). Basically, it's the Ricoh device reported in USB section of the SysProfiler. In IOReg, it's visible under port #2 or USB2.0 controller EH02. Since it's a USB-internal device, there are no patches and probably no kexts that can help get the camera working if it ain't already. I'm afraid it's either supported OOB or not at all... Once you have your LAN/Ethernet port working as en0 interface (or a fake Ethernet as en0), you'll be able to verify webcam behaviour with FaceTime.

 

LAN/Ethernet port is indeed Marvell Yukon GigaEthernet 88E8036 model (ven/dev=0x11ab/0x3451). Shown in IOReg as device PXSX under parent device RP05 @1c,4 (i.e. at address 0x001C0004). You can easily rename that PXSX device as "GLAN" in your DSDT".

 

Same for the wireless card (Intel 4965AG/AGN at the moment) which is registered as device PXSX under parent device RP03 @1C,2 (i.e. at address 0x001C0002). You could also rename that PXSX device to "ARPT" in the DSDT.

Thank you! I'm gonna try it, but don't we have the Marvell Yukon 88E8036 instead?

What about the webcam?

Yeah, you are right.

I re-upload the right info; look back to my prior post

For WebCam : It works under Windows10 ?

If Qe/Ci is enabled it should  work ...

Try this for built-in LCD as a proper laptop (backlight) display.

attachicon.gifDSDT_HD.aml.zip

 

Do I just need to replace the old one into /Extra folder?

Looking at it with MaciASL with iAsl 5.1, I can see there're at least 75 errors  :rofl: will it work fine?

EDIT: sorry, it was set to iAsl 4.1....... LOL switching to 5.1 gives no errors as it should be. Thanks!

 

@pippox0 : Yes, I've seen, thanks! I'm about to try both the new DSDT and the Yukon patch. Yes, it was working in Windows 10, but right now I have only MacOS installed!

Try this for built-in LCD as a proper laptop (backlight) display.

attachicon.gifDSDT_HD.aml.zip

 

Webcam is natively detected and reported as USB UVC VideoCamera in SysProfiler (dev/ven=0x05ca/0x183b, i.e. 1482/6203 in decimal). Basically, it's the Ricoh device reported in USB section of the SysProfiler. In IOReg, it's visible under port #2 or USB2.0 controller EH02. Since it's a USB-internal device, there are no patches and probably no kexts that can help get the camera working if it ain't working already. I'm afraid it's either supported OOB or not at all... Once you have your LAN/Ethernet port working as en0 interface (or a fake Ethernet as en0), you'll be able to verify webcam behaviour with FaceTime.

 

LAN/Ethernet port is indeed Marvell Yukon GigaEthernet 88E8036 model. Shown in IOReg as device PXSX under parent device RP05 @1c,4 (i.e. at address 0x001C0004). You can easily rename that PXSX device as "GLAN" in your DSDT".

 

Same for the wireless card (Intel 4965AG/AGN at the moment) which is registered as device PXSX under parent device @1C,2 (i.e. at address 0x001C0002). You could also rename that PXSX device to "ARPT" in the DSDT.

 

Mmm ok, with the new DSDT there's an actual MacBook Pro represented in the Monitor section, but I still can't access the Monitor panel inside the Settings which is weird... Really there's no way to adjust the screen brightness, even with Terminal (like in Linux if I remember correctly)?? I'm very "light-sensitive" and I couldn't stay in front of 100% light source for more than a few minutes  B)

 

Other than that, I've manually changed the .plist file inside the Yukon2.kext but if I make the changes you're saying also to the DSDT will it work anyway? And is there a remote chance to have also the Intel 4965agn to work!?

 

EDIT: it seems like I still have no Ethernet according to SystemInfo. I'm about to make those DSDT changes.

EDIT2: after changing 5 "PXSX" to "GLAN" the compiler says that I have 4 "syntax error, unexpected PARSEOP_INTEGER" (code 6126). I'm trying to figure out what to change.

Try the attached patched Yukon kext for your 88E8036 LAN card; basically it's a patched version of Sierra's Yukon2 kext where one of the existing 88E80xx entry has been copied/pasted and modified to reflect 88E8036 info (dev id 4351). The kext's version was then up'ed from 4.0.0 to 994.0.0 so that it loads instead of the vanilla PlugIn of /S/L/E/IONetworkingFamily kext.

 

Copy the patched kext to /L/E then repair permissions and rebuild your cache. On reboot, you'll hopefully have Ethernet working.

Patched_AppleYukon2.kext.zip


Revised DSDT to display LAN + Wireless info in PCI section of SysProfiler (RP05.PXSX renamed to RP05.GLAN and RP03.PXSX renamed to RP03.ARPT).

DSDT_HD2.aml.zip

Ethernet now successfully appears into SystemInfo!  :thumbsup_anim:

Webcam still shows a black screen both on PhotoBooth and FaceTime, even though as you said it seems to be recognised..

 

I need to say other two things:

1) after the new DSDT, I have a 0% battery reporting which is wrong cos it should be 100%.

2) should we try to implement this ACPI Backlight https://github.com/RehabMan/OS-X-ACPI-Backlight to have screen brightness working?

 

I would really like to know how you have saved those 2 new DSDTs with those 4 errors (6126)  :rolleyes:  :hysterical:

Another thing though, even if I can see that QE/CI and all the other things are supported, the overall graphics acceleration is extremely slow. I've tried for example to open the Chess game and it's lagging! Not to mention that every time you make a move the pc makes a "buzz" (sort of)..  :(

SDHC card reader 0x104c/0x803b @3,2 shows as sister device of Firewire controller 0x104C:0x803a @3,1 under parent device CARD @3, itself under PCIB@1E.

 

As a test, I've added a new device in DSDT under device CARD to declare the card reader as compatible with Apple's own device. This is similar to what works for O2 Micro card readers on Dell Latitude laptops, but may not work for this particular model, in which case just discard this DSDT version...

DSDT_HD3.aml.zip

 

I don't have any errors recompiling the DSDT files. I'm using Rehabman's macIASL v1.31 (252.2). Make sure to use a version downloaded off Rehabman's repository.

 

Don't hold much expectations on brightness control. I've never managed to obtain it on my Dell Latitude D630 and I've read many reports of other older nVidia-based systems that had the same problem.

NEW: I apologize for before. Anyway this is what I'm getting after the WiFi patch, seems interesting but there's no driver.

 

Aaaand I don't see anything new for the SD card reader after testing DSDT_HD3.

post-290784-0-11009600-1487889115_thumb.png

In case you still ignored it, there's never been any support for Intel wireless cards and never will be until Apple decided to use them. You'll have to replace your Intel 4965AGN by a compatible model. There's a non-exhaustive list here.

 

I've deliberately set wireless model to "To be defined" in your DSDT so that you replace this text with whatever card model you subsequently install.

                Device (ARPT)
                {
                    Name (_ADR, Zero)  // _ADR: Address
                    Name (_PRW, Package (0x02)  // _PRW: Power Resources for Wake
                    {
                        0x09, 
                        0x03
                    })
                    Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                    {
                        If (LEqual (Arg2, Zero))
                        {
                            Return (Buffer (One)
                            {
                                 0x03                                           
                            })
                        }
                        Return (Package (0x06)
                        {
                            "AAPL,slot-name", 
                            Buffer (0x05)
                            {
                                "WLAN"
                            }, 
                            "device_type", 
                            Buffer (0x08)
                            {
                                "Airport"
                            }, 
                            "model", 
                            Buffer ()
                            {
                                "To be defined"     // Adjust with appropriate model info
                            }
                        })
                    }
                }

`

I was not expecting much for the SD card reader, so it'll have to do with VoodooSDHC at best, probably to the detriment of Sleep...

Ok, nice to know! I did remember however of the non-Intel WiFi support on OSX, but yea defining the Full-size Mini PCIe card into DSDT makes sense  ^_^

I have tried the VoodooSDHC kext from a thread here stating that it was compatible with El Capitan, but even if I have changed the values the pc doesn't recognise the SD reader...

 

Anyway I don't have already a working sleep/wake function. I mean that the Vaio can go to sleep (not closing the lid though) but waking it makes the screen completely messed up with pixels to say the best. So, right now:

 

--> Sleep works BUT after wake the screen is completely dead and the system becomes unresponsive, forcing a shutdown.

--> SD card reader is still not working even with the patched VoodooSDHC. I'm looking into it.

--> Bluetooth works BUT not 100% because for example it can't connect to the internet shared from another device (with all the prerequisites) and it can't be stopped.

--> The battery percentage reports 0% after the new DSDTs with the monitor defined.

--> Still it's impossible to access the Monitor panel into Settings and display brightness is still a "who knows!?"

 

So yea, it's kinda working but I was expecting to have at least a useable machine with display/graphics fully working along with the integrated BT at least for now.

Hi iperzampem0,

--> Bluetooth starts/stops  only with fthe real switch

--> Battery percentage % -> revert back to the first DSDT

--> Monitor panel -> very strange  on my vaio ( up Yosemite ) it works

 

@ Hervé -> Thanks a lot for yours efforts to help us with this notebook.

 

Me too I can only say thank you to both of you, given that you're trying very hard to give me (and maybe others) a chance to have a working MacOS on a non-Apple machine.

 

@pippox0 : would you please say briefly which kexts, bootloader, smbios you have used for Yosemite? And the things not working there are just the wifi and the SD card reader? Thanks.

This is my Extra for Yosemite.

I have used imac9,1 for smbios, but Sierra needs imac12,1 

I use Enoch 2725 ,but works Enoch 2839 too.

The Kexts are Fakesmc, NullCPUPowerManagement, ACPIBacklight, ACPIBatteryManager

 

on /S/L/E i have VoodooHDA for audio.

 

Hints: the keys on keyboard controls Volume+ and Volume - , and NOVolume very well !!

 

And Yes what are not working --> SD Card reader and intel WIFI ( i have used a cheap RT2870USB Wifi dongle)

 

Extra.zip

Nice to know, thanks a lot ! I'm still learning a lot of new things about DSDT editing and I'm about to make some new changes for the actual Sierra setup on the VAIO.

Let's see if it will work  :rolleyes:

Do you also have brightness working on Yosemite? ACPIBacklight serves that purpose? BTW even in Sierra those Volume keys are working fine!

 

EDIT: I've successfully reverted back to the first (original) DSDT and I have the correct battery percentage reporting. I also have added the PNLF "device" injecting a code that should try to implement display brightness correctly, but I still need to manually install the right ACPIBacklight.kext and see.

 

EDIT2: Ok so I've tried the ACPIBacklight.kext from RehabMan (which is probably the same you, @pippox0, used for Yosemite) but I haven't seen any changes regarding brightness probably because there has to be something to direct the right keys on the keyboard, and for this I've used the latest VoodooPS2Controller with its daemon, obviously removing first the ApplePS2Nub and ApplePS2Controller kexts. Unfortunately, even though I like the fact that the keyboard now seriously has brightness controls built in (Fn+F13 & F15), the brightness doesn't change and the trackpad became totally unusable. The caps lock key works fine with Voodoo, otherwise it would act strangely on Sierra.

 

@pippox0 can you adjust the screen brightness (at least from the Monitor panel) in Yosemite for example? This is a big deal for me... I'm about to leave Sierra because of its different issues, and hopefully 10.10 is stable and usable enough. I need your confirm though. Have you also tried VoodooSDHC.kext for SDcard?

Hi iperzampem0,

Brightness can be tuned from color profile manager.

I nave no brightness controll under monitor preference panel. No way

Yosemite runs well , but with 2Gb of RAM i prefer OSX Mavericks because it runs better and i like "old style" desktop.

 

I never tried to fix SD card reader, because usually i don't need it

 

With 4GB you can run the OSX you like

See Ya

 

sent from my iPhone

×
×
  • Create New...