Funky frank Posted November 14, 2010 Share Posted November 14, 2010 I removed SNC device from the DSDT since it is not use by Mac OS X. Hm the SNC device is that thing "SNY5001"? But this is needed to get a working SNC.kext or not? The SNC.kext over here (sources) quite uses same structures. If I load it and press the "display off" button, at least the keyboard will not longer react SNC.zip Edit: Maybe the linux snc driver and also the kext do not implement all functionality of the snc device. If the snc is responisble for all extra sony buttons on the notebook, there must be a function enable/disable internal display. I cannot find this in the linux implementation. Link to comment Share on other sites More sharing options...
kizwan Posted November 14, 2010 Author Share Posted November 14, 2010 I think you should not emulate some specific OS when extracting ACPI code. The DSDT dump will always the same whether you extract it under windows, linux or OSX. There is no OS specific DSDT dump. For editing DSDT, I use this editor instead. Hm the SNC device is that thing "SNY5001"? But this is needed to get a working SNC.kext or not? The SNC.kext over here (sources) quite uses same structures. If I load it and press the "display off" button, at least the keyboard will not longer react Oh...Sorry, I didn't know you're using SNC.kext. If that is the case, just copy the SBUS device from the modified DSDT to your original DSDT. If the snc is responisble for all extra sony buttons on the notebook, there must be a function enable/disable internal display. No, there is no function to enable/disable internal display in the linux SNC driver. I already look into it. Also, I didn't found any function in SNC codes (in DSDT) that enable/disable internal LCD. Link to comment Share on other sites More sharing options...
Funky frank Posted November 14, 2010 Share Posted November 14, 2010 For editing DSDT, I use this editor instead. Wow this is cool stuff! Could we let the SNC device inside the dsl for now, because then I can do experiments with the snc.kext... Edit: What about the Scope _SB, Device ADP1? Is it the display1-device? "Notify (\_SB.ADP1, 0x81)" is called on _WAK. Hm, maybe I should first read more about ACPI structure... Link to comment Share on other sites More sharing options...
kizwan Posted November 14, 2010 Author Share Posted November 14, 2010 Could we let the SNC device inside the dsl for now, because then I can do experiments with the snc.kext... No problem. Please wait, I'll post new modified DSDT with SNC device in it. Link to comment Share on other sites More sharing options...
jlvaio Posted November 14, 2010 Share Posted November 14, 2010 @franck http://vaio-utils.org/power/ The device signature in the disassembled DSDT looks like the following: Device (SNC) { Name (_HID, EisaId ("SNY5001")) ... } and Device (SPIC) { Name (_HID, EisaId ("SNY6001")) ... } [1]↑ from kernel 2.6.21-rc1, when the driver has been merged mainline [2]↑ only from kernel 2.6.22-rc1, previous kernel handled this device with sonypi only Link to comment Share on other sites More sharing options...
kizwan Posted November 14, 2010 Author Share Posted November 14, 2010 Edit: What about the Scope _SB, Device ADP1? Is it the display1-device? "Notify (\_SB.ADP1, 0x81)" is called on _WAK. Hm, maybe I should first read more about ACPI structure... Yes, I think so. ADP1 is the AC adapter. Link to comment Share on other sites More sharing options...
Funky frank Posted November 14, 2010 Share Posted November 14, 2010 Yes, I think so. ADP1 is the AC adapter. Lol. How do get these information? Is there a general ACPI naming convention or what? Link to comment Share on other sites More sharing options...
kizwan Posted November 14, 2010 Author Share Posted November 14, 2010 @Frank, This is modified DSDT with SNC device. http://www.mediafire.com/?337l2s7m787cnsz It is good idea to play around SNC device. We should look into every possibility. I already look into SNC device & I didn't found any function that control internal LCD. SNC device is similar with AMW0 device which is for ON/OFF devices such as wlan, bluetooth, sound volume, brightness, etc. But you can look into it again if you want. Lol. How do get these information? Is there a general ACPI naming convention or what? You can download ACPI specification documentation at acpi.info website. Link to comment Share on other sites More sharing options...
jlvaio Posted November 14, 2010 Share Posted November 14, 2010 here some doc from suse: http://www.basyskom.org/~eva/log_installat...aio_z21vnx.html http://tjworld.net/snc/ http://tjworld.net/snc/sourcecode.html http://ubuntuforums.org/showthread.php?t=598551 http://vaioubuntu.wordpress.com/2009/07/20...or-fw4x-models/ http://www.mail-archive.com/git-commits-he...g/msg09721.html http://vaioubuntu.wordpress.com/2009/05/28...ide-for-jaunty/ http://vaioubuntu.wordpress.com/page/2/ Link to comment Share on other sites More sharing options...
Funky frank Posted November 14, 2010 Share Posted November 14, 2010 This is modified DSDT with SNC device.http://www.mediafire.com/?337l2s7m787cnsz Thank you! http://ubuntuforums.org/showthread.php?t=598551 What the {censored}. Is _SB Device the internal soundcard, so HDEF is the HDMI Sounddevice? Maybe that's the reason, even recent voodoohda 0.272 64bit will crash at the latest on second reboot (VoodooHDA_64bit_0272_with_alc275_inside.kext.zip - Don't forget to remove AppleHDA.kext from Sys/lib/ext first and rebuild kextcache with pfix).... ? I modified the plist inside for 2 soundcards, but freezes the system sooner or later. Link to comment Share on other sites More sharing options...
jlvaio Posted November 14, 2010 Share Posted November 14, 2010 Thank you! What the {censored}. Is _SB Device the internal soundcard, so HDEF is the HDMI Sounddevice? Maybe that's the reason, even recent voodoohda 0.272 64bit will crash at the latest on second reboot (VoodooHDA_64bit_0272_with_alc275_inside.kext.zip).... ? I modified the plist inside for 2 soundcards, but freezes the system sooner or later. i m not an expert but i think we should search on other system to find docs or dsdt patches for example i ve just find for sound: Top Re: THE DSDT SOLUTIONS THREAD. Postby Quackers on Thu Aug 12, 2010 11:02 pm You won't get the graphics card to work on a Vaio, but you will be able to get a display with vesa. Your sound vendor is 104d, your device id is 1c00 and the subsys is 0x8384766 For sound I extracted the dsdt of my vaio with DSDTSE (probably found in Library/Tools folder). This produces a file on screen with your dsdt.dsl After googling endlessly I found a thread that matched my sound card (not exactly the same as yours, but similar) and gave instructions. In the displayed dsdt.dsl (in DSDTSE screen) on the right side use the search or find function (or maybe look for) and enter HDEF and hit enter. The dsdtse screen will move to line 500+ (or thereabouts) and on the highlighted line will be "HDEF" - you need to delete that and type in AZAL in capitals. Then you need to do that for every HDEF entry (maybe 4 or 5 more times). When all entries are changed to AZAL click on "compile". If the compile runs ok it will say so. If there is an error read it. The most likely error will point to a line with HDEF still in it. Change that to AZAL and re-compile. When it runs ok you will have a DSDT.aml file to save. Then copy/paste that file in the Extra folder (which is hidden by default - you'll need to unhide it) NOT Extra/Extensions. Then run Kext Utility (in Library/Tools) to fix permissions. Then delete any sound kexts from the System/Library/Extensions folder and run Kext Utility again. When you've got that far send me a pm with your email address and I'll send you the kext I used. There are no guarantees that this will work. It worked for me, but may not work for your card. Sony Vaio AR51SU 2 x 250GB non-raid / Intel Core 2 Duo T7700 Intel Mobile PM965 Express chipset SATA RAID / SATA AHCI non-raid nVIDIA GeForce 8600M GT 256 Intel HD Audio / Realtek ALC262 Intel wifi link 4965 AGN User avatar Quackers osx86 expert Posts: 260 Joined: Sun Jun 13, 2010 1:51 pm Link to comment Share on other sites More sharing options...
Funky frank Posted November 14, 2010 Share Posted November 14, 2010 jlvaio: I thought about this too. I will try it to REPLACE HDEF with AZAL so the HDEF output of hdmi will be disabled...? Edit: Does not work. Btw maybe useless, could someone explain to me in short words what for are EDIDs needed, is this another way to PCI match or what. In the vaio dsl there are these EDIDs hardcoded: Name (EDI1, Buffer (0x80) { /* 0000 */ 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, /* 0008 */ 0x4D, 0xD9, 0xFA, 0x06, 0x00, 0x00, 0x00, 0x00, /* 0010 */ 0x2D, 0x0C, 0x01, 0x04, 0x90, 0x24, 0x14, 0x00, /* 0018 */ 0xEA, 0xA8, 0xE0, 0x99, 0x57, 0x4B, 0x92, 0x25, /* 0020 */ 0x1C, 0x50, 0x54, 0x00, 0x00, 0x00, 0x01, 0x01, /* 0028 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, /* 0030 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x28, 0x23, /* 0038 */ 0x40, 0x32, 0x60, 0x84, 0x0A, 0x30, 0x11, 0x11, /* 0040 */ 0x33, 0x00, 0x68, 0xC8, 0x10, 0x00, 0x00, 0x18, /* 0048 */ 0x28, 0x23, 0x40, 0x13, 0x61, 0x84, 0x3C, 0x30, /* 0050 */ 0x5B, 0x5B, 0x44, 0x00, 0x68, 0xC8, 0x10, 0x00, /* 0058 */ 0x00, 0x18, 0x00, 0x00, 0x00, 0xFC, 0x00, 0x4E, /* 0060 */ 0x76, 0x69, 0x64, 0x69, 0x61, 0x20, 0x44, 0x65, /* 0068 */ 0x66, 0x61, 0x75, 0x6C, 0x00, 0x00, 0x00, 0xFC, /* 0070 */ 0x00, 0x74, 0x20, 0x46, 0x6C, 0x61, 0x74, 0x20, /* 0078 */ 0x50, 0x61, 0x6E, 0x65, 0x6C, 0x00, 0x00, 0xEE }) Name (EDI2, Buffer (0x80) { /* 0000 */ 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, /* 0008 */ 0x4D, 0xD9, 0xFA, 0x06, 0x00, 0x00, 0x00, 0x00, /* 0010 */ 0x2D, 0x0C, 0x01, 0x04, 0x90, 0x24, 0x14, 0x00, /* 0018 */ 0xEA, 0xA8, 0xE0, 0x99, 0x57, 0x4B, 0x92, 0x25, /* 0020 */ 0x1C, 0x50, 0x54, 0x00, 0x00, 0x00, 0x01, 0x01, /* 0028 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, /* 0030 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x30, 0x2A, /* 0038 */ 0x40, 0x5E, 0x61, 0x84, 0x18, 0x30, 0x74, 0x74, /* 0040 */ 0x88, 0x00, 0x6A, 0xCC, 0x10, 0x00, 0x00, 0x18, /* 0048 */ 0x00, 0x00, 0x00, 0xFC, 0x00, 0x4E, 0x76, 0x69, /* 0050 */ 0x64, 0x69, 0x61, 0x20, 0x44, 0x65, 0x66, 0x61, /* 0058 */ 0x75, 0x6C, 0x00, 0x00, 0x00, 0xFC, 0x00, 0x74, /* 0060 */ 0x20, 0x46, 0x6C, 0x61, 0x74, 0x20, 0x50, 0x61, /* 0068 */ 0x6E, 0x65, 0x6C, 0x00, 0x00, 0x00, 0x00, 0xFD, /* 0070 */ 0x00, 0x00, 0x3D, 0x1D, 0x38, 0x0B, 0x00, 0x00, /* 0078 */ 0x20, 0x20, 0x20, 0x20, 0x20, 0x00, 0x00, 0x8A }) Name (EDI3, Buffer (0x80) { /* 0000 */ 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, /* 0008 */ 0x4D, 0xD9, 0xFA, 0x06, 0x00, 0x00, 0x00, 0x00, /* 0010 */ 0x2D, 0x0C, 0x01, 0x04, 0x90, 0x24, 0x14, 0x00, /* 0018 */ 0xEA, 0xA8, 0xE0, 0x99, 0x57, 0x4B, 0x92, 0x25, /* 0020 */ 0x1C, 0x50, 0x54, 0x00, 0x00, 0x00, 0x01, 0x01, /* 0028 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, /* 0030 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x30, 0x2A, /* 0038 */ 0x40, 0x5E, 0x61, 0x84, 0x18, 0x30, 0x74, 0x74, /* 0040 */ 0x88, 0x00, 0x68, 0xC8, 0x10, 0x00, 0x00, 0x18, /* 0048 */ 0x30, 0x2A, 0x40, 0x90, 0x61, 0x84, 0xB4, 0x30, /* 0050 */ 0x85, 0x85, 0xCC, 0x00, 0x68, 0xC8, 0x10, 0x00, /* 0058 */ 0x00, 0x18, 0x00, 0x00, 0x00, 0xFC, 0x00, 0x4E, /* 0060 */ 0x76, 0x69, 0x64, 0x69, 0x61, 0x20, 0x44, 0x65, /* 0068 */ 0x66, 0x61, 0x75, 0x6C, 0x00, 0x00, 0x00, 0xFC, /* 0070 */ 0x00, 0x74, 0x20, 0x46, 0x6C, 0x61, 0x74, 0x20, /* 0078 */ 0x50, 0x61, 0x6E, 0x65, 0x6C, 0x00, 0x00, 0xA9 }) Name (EDI4, Buffer (0x80) { /* 0000 */ 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, /* 0008 */ 0x36, 0x7F, 0x25, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0010 */ 0x2D, 0x0C, 0x01, 0x04, 0x90, 0x24, 0x14, 0x00, /* 0018 */ 0xEA, 0xA8, 0xE0, 0x99, 0x57, 0x4B, 0x92, 0x25, /* 0020 */ 0x1C, 0x50, 0x54, 0x00, 0x00, 0x00, 0x01, 0x01, /* 0028 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, /* 0030 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x40, 0x38, /* 0038 */ 0x80, 0xB4, 0x70, 0x38, 0x40, 0x40, 0x3C, 0x3C, /* 0040 */ 0x55, 0x00, 0x68, 0xC8, 0x10, 0x00, 0x00, 0x18, /* 0048 */ 0x40, 0x38, 0x80, 0x80, 0x71, 0x38, 0xAA, 0x40, /* 0050 */ 0x80, 0x80, 0x88, 0x00, 0x68, 0xC8, 0x10, 0x00, /* 0058 */ 0x00, 0x18, 0x00, 0x00, 0x00, 0xFC, 0x00, 0x4E, /* 0060 */ 0x76, 0x69, 0x64, 0x69, 0x61, 0x20, 0x44, 0x65, /* 0068 */ 0x66, 0x61, 0x75, 0x6C, 0x00, 0x00, 0x00, 0xFC, /* 0070 */ 0x00, 0x74, 0x20, 0x46, 0x6C, 0x61, 0x74, 0x20, /* 0078 */ 0x50, 0x61, 0x6E, 0x65, 0x6C, 0x00, 0x00, 0x1F }) Name (EDI5, Buffer (0x80) { /* 0000 */ 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, /* 0008 */ 0x36, 0x7F, 0x25, 0x00, 0x00, 0x00, 0x00, 0x00, /* 0010 */ 0x2D, 0x0C, 0x01, 0x04, 0x90, 0x24, 0x14, 0x00, /* 0018 */ 0xEA, 0xA8, 0xE0, 0x99, 0x57, 0x4B, 0x92, 0x25, /* 0020 */ 0x1C, 0x50, 0x54, 0x00, 0x00, 0x00, 0x01, 0x01, /* 0028 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, /* 0030 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x40, 0x38, /* 0038 */ 0x80, 0xB4, 0x70, 0x38, 0x40, 0x40, 0x3C, 0x3C, /* 0040 */ 0x55, 0x00, 0x68, 0xC8, 0x10, 0x00, 0x00, 0x18, /* 0048 */ 0x40, 0x38, 0x80, 0x80, 0x71, 0x38, 0xAA, 0x40, /* 0050 */ 0x80, 0x80, 0x88, 0x00, 0x68, 0xC8, 0x10, 0x00, /* 0058 */ 0x00, 0x18, 0x00, 0x00, 0x00, 0xFC, 0x00, 0x4E, /* 0060 */ 0x76, 0x69, 0x64, 0x69, 0x61, 0x20, 0x44, 0x65, /* 0068 */ 0x66, 0x61, 0x75, 0x6C, 0x00, 0x00, 0x00, 0xFC, /* 0070 */ 0x00, 0x74, 0x20, 0x46, 0x6C, 0x61, 0x74, 0x20, /* 0078 */ 0x50, 0x61, 0x6E, 0x65, 0x6C, 0x00, 0x00, 0x1F }) Link to comment Share on other sites More sharing options...
kizwan Posted November 14, 2010 Author Share Posted November 14, 2010 Btw maybe useless, could someone explain to me in short words what for are EDIDs needed, is this another way to PCI match or what. In the vaio dsl there are these EDIDs hardcoded: (source) Extended display identification data (EDID) is a data structure provided by a digital display to describe its capabilities to a video source (e.g. graphics card, Set-top box). It is what enables a modern personal computer to know what kind of monitor is connected. EDID is defined by a standard published by the Video Electronics Standards Association (VESA). The EDID includes manufacturer name and serial number, product type, phosphor or filter type, timings supported by the display, display size, luminance data and (for digital displays only) pixel mapping data. Link to comment Share on other sites More sharing options...
First Last Posted November 14, 2010 Share Posted November 14, 2010 some news about the linux nvidia driver for vaios: while the older ones (<256.53) needed EDID override and Output-Devices defined, the newer (256.53) had a fix and doesn't need the changes any more. But the newest (260.x) give me a black screen and system crash when loading the driver, but the backlight stays on. im now updating my osx to 10.6.5 and try my luck Link to comment Share on other sites More sharing options...
Funky frank Posted November 14, 2010 Share Posted November 14, 2010 cool please let us know your results with 10.6.5. kizwan: What about this idea: DD02 device seems to me the output device for LCD. The function DD02._DSS sets the state of it. Maybe we could change the calls in a way that the lcd / dd02 is alwas active. What do you think? Btw. why there are also DDXX-devices, it's not mentioned in the acpi docs. Link to comment Share on other sites More sharing options...
OoTLink Posted November 15, 2010 Share Posted November 15, 2010 http://www.insanelymac.com/forum/index.php...mp;#entry747500 Funkyfrank, try MacVidia_1.0.81.pkg.zip ( 151.86K ) Number of downloads: 264 and if that doesn't work, maybe the MacVidia_NVDriver107.zip ( 49.68K ) Number of downloads: 199 If those work, let me know ^^ thanks. What they SHOULD do (and what I've heard they do) is enable a software framebuffer (eg, no QE/CI) but with 1920x1080 support Link to comment Share on other sites More sharing options...
kizwan Posted November 15, 2010 Author Share Posted November 15, 2010 kizwan: What about this idea: DD02 device seems to me the output device for LCD. The function DD02._DSS sets the state of it. Maybe we could change the calls in a way that the lcd / dd02 is alwas active. What do you think? Btw. why there are also DDXX-devices, it's not mentioned in the acpi docs. Yeah, I don't see any reason why not. Go ahead. Study the EDID value will be good idea too. About the DDXX devices, it is manufacturer specific implementation. That is why you can't find it in ACPI docs. I believe it is display configurations. Link to comment Share on other sites More sharing options...
OoTLink Posted November 15, 2010 Share Posted November 15, 2010 One of the reasons I want to know about macvidia is to see if we can get a better glimpse at the info according to OS X when it works. Link to comment Share on other sites More sharing options...
JamesA27 Posted November 15, 2010 Share Posted November 15, 2010 Hello, I have a VAIO VPCF127FX and luckily I came across this forum. I don't know too much but I wanted to know more about this problem. So, I've gotten various errors booting up onto standard mode with both the retail 10.6.3 Retail Snow Leopard DVD and also the installed version. However, both do work when I boot up in Safe Mode and I do not know why this is... Anyway, I have tried various drivers and updates from in Safe Mode. But, I was wondering if this is the same problem as you guys have? When I boot up in standard mode, the monitor shuts off with no backlight or response, while safe mode boots up fine. Also, I have booted up in verbose mode and have gotten different errors, yet, unfortunately I do not know when I am making progress. I can try installing any .kexts or updates tomorrow if you need someone to test them. Thanks, James Link to comment Share on other sites More sharing options...
Funky frank Posted November 15, 2010 Share Posted November 15, 2010 kizwan: But where in the dsdt is the line of code that acually enables the internal LCD? Do you know this? Or is it hardcoded within the nvidia driver without any use of ACPI? In general is there any code in ACPI that actually enables some hardware? OoTLink: The provided MacVidia requires i386 kernel and then crashes at boot. I think it has to be recompiled for 10.6 and linked to recent system components. We need the sources of that! Can you get it here in the forum? Edit: Ok in the meanwhile maybe we should focus on not so difficult patches, like Audio and speed-stepping for the Core i7. CPU Stepping: Kizwan, do you know how to setup a good cpu stepping by using Chameleon PStates? CStates are for older cpus, right? The CPU is running quite hot here, so I guess the stepping could be better. Is there any tool the shows the current cpu speeds? My "about mac" crashes. Audio: If the audio device in ACPI is renamed from HDEF to AZAL, voodoohda will load and stay stable here. HDEF is the nvidia hdmi audio device or the internal Realtek one? Anybody? Bluetooth: Does it work for you? Not for me. With unpatched dsdt it shows up bluetooth devices but does not add it. Maybe bluetooth needs to be activated thru snc device first. LAN: Any ideas? Is there a similiar driver out there? Link to comment Share on other sites More sharing options...
OoTLink Posted November 16, 2010 Share Posted November 16, 2010 If you use VoodooHDA, it's possible to get the internal audio working, but I never did get beyond the initial sketchy state of it (it would start up the internal speakers when I manually started the driver, but after trying to configure it to start at boot, it crashed the machine lol). By default VoodooHDA really likes to work with the HDMI output. Go figure right? Link to comment Share on other sites More sharing options...
kizwan Posted November 16, 2010 Author Share Posted November 16, 2010 kizwan: But where in the dsdt is the line of code that acually enables the internal LCD? When did I said there is one in the DSDT? There is LID control method which is for LID operation (e.g. what to do when LID is close/open). There are control method in the DSDT to turn ON/OFF the usual stuff like bluetooth & wireless. CPU Stepping: Kizwan, do you know how to setup a good cpu stepping by using Chameleon PStates? CStates are for older cpus, right? The CPU is running quite hot here, so I guess the stepping could be better. Is there any tool the shows the current cpu speeds? My "about mac" crashes. Does AppleLPC.kext loaded? You need it loaded because it will help CPU run much cooler. I do not generate the C-State & P-State manually since my notebooks is supported by default by OSX. C-State is CPU power management while P-State is an operational state. Both state related with each other. Link to comment Share on other sites More sharing options...
OoTLink Posted November 16, 2010 Share Posted November 16, 2010 If Vaio Control Center is any indication, the F series' "lid' sensor only recognizes the laptop being closed, not opened. Just fyi :censored2: Link to comment Share on other sites More sharing options...
Funky frank Posted November 16, 2010 Share Posted November 16, 2010 Does AppleLPC.kext loaded? You need it loaded because it will help CPU run much cooler. I do not generate the C-State & P-State manually since my notebooks is supported by default by OSX. C-State is CPU power management while P-State is an operational state. Both state related with each other. No AppleLPC is not loaded. In the dsdt the is a LPCB device on PCI0. In IORegistry there is a LPCB with name "8086,3b03" and compatible "pci104d,9067". Edit: Added "8086,3b03" to AppleLPC.kext and now it's loaded. But the cpu is still very hot and the cooler runs all the time. How to enable proper power management now? Edit: Ok, with 1. adding devid to AppleLPC.kext, 2. the option ForeceHPET=Yes, 3. GeneratePStates=yes and 4. GenerateCStates=Yes the cpu is not so hot anymore, but still runs hotter than under win7. Edit: Hm, sleepmode does not work anymore.... Link to comment Share on other sites More sharing options...
Funky frank Posted November 16, 2010 Share Posted November 16, 2010 kizwan: Do you know what device is the ethernet device in the dsdt? Did you remove it in your DSDT? Vendor 11ab Devid 4380, Yukon 88e8057, should be loaded by Yukon2.kext if editing pcimatch... edit: I tried to patch the network device in dsdt like explained here. The strange thing is, in the VaioDST generated in OSX, there is only a P0PF device, in the Vaio DSDT generated in Windows (posted in this thread at beginning and dsdt_VAIO_windows.dsl.ziphere), there is only a P0P9 device. Also strange is Ethernet device is not listed in IOReg at all. So I tried to patch the device like this: /*Device (P0PF) { Name (_ADR, 0x001E0000) Method (_PRW, 0, NotSerialized) { Return (GPRW (0x0B, 0x04)) } }*/ // NETWORK patch Device (P0P9) { Name (_ADR, 0x001E0000) Method (_PRW, 0, NotSerialized) { Return (GPRW (0x0B, 0x04)) } Method (_PRT, 0, NotSerialized) { If (PICM) { Return (AR09) } Return (PR09) } Device (GIGE) { Name (_ADR, Zero) OperationRegion (GPIO, SystemIO, 0x0800, 0x06) Field (GPIO, ByteAcc, NoLock, Preserve) { GO01, 8, GO02, 8, GO03, 8, GO04, 8, GO05, 8, GP9, 1 } Name (_PRW, Package (0x02) { 0x09, 0x03 }) Method (EWOL, 1, NotSerialized) { If (LEqual (Arg0, One)) { Or (GP9, One, GP9) } Else { And (GP9, Zero, GP9) } If (LEqual (Arg0, GP9)) { Return (Zero) } Else { Return (One) } } } } The original patch in the thread needs addresses like AR09, GP09 and GP9 that do not exists neither in OSX dsdt nor in Windows dsdt. And why the dsdts are different? Because I have the recent BIOS update? Maybe there is something useful in the Windows DSDT. Link to comment Share on other sites More sharing options...
Recommended Posts