Jump to content

Pablo Iglesias

Members
  • Content Count

    15
  • Joined

  • Last visited

  • Days Won

    1

Pablo Iglesias last won the day on November 30 2013

Pablo Iglesias had the most liked content!

Community Reputation

3 Neutral

About Pablo Iglesias

  • Rank
    Private First Class
  1. Hi FrostyTheSnowman, First of all, thanks for your patience and help! Sorry for the delay on answering you, but I still haven't the time to check the procedures you informed. I will try this weekend and let you know how it worked. Best regards, Pablo Iglesias
  2. Hi Hervé, Jake, FrostyTheSnowman, I really appreciate your very quick response, clarifying my doubts. Hervé, will try the approach of declaring an external method, as it's the easiest. But at the same time, I agree with copying SSDT content inside to DSDT so it will be compatible with future version of BIOS. As my display is 1366x768, I'm not planning to update my BIOS, keeping with the first option. Jake, I got the bootpack you referenced and it worked perfectly. Thanks! I did all the changes in the config.plist and it's booting perfectly with external monitor and much better performance! It seems that the sleep is not working, then I disabled for a while. About the SMBIOS MBA 6.2, this is a Haswell cpu and e6430 has an Ivy Bridge. Does it matter when creating the SSDT.aml via ssdtPRGen.sh script? FrostyTheSnowman, I really appreciate your kindness on helping me. May I ask you (and the others too) few more questions? 1. I didn't find the PNLF method to insert in the DSDT. Is it the '[igpu] Brightness fix (HD300/HD4000)' patch that I need to apply? 2. I was looking around, but I could not find the 'backlight code for Nvidia' to replace the content of the _DSM method in the SSDT-7.dsl. Could you help me to find it? I will continue reading related posts. 3. I could find the _DSM method in SSDT-7.dsl and inside the DSDT.dsl. Should I clean only in the SSDT-7.dsl file, or both including DSDL.dsl. 4. About the _OSI to XOSI, I did inside the config.plist via Clover patch. If I create the SSDT with XOSI method to set 'Windows 2009', should I saved in /EFI/CLOVER/ACPI/patched? Which name should I use SSDT-n.aml (where n is a number from 0 to 9)? Does it matter to use any that doesn't exist? Thank you all for the help! Best regards, Pablo Iglesias
  3. Hi FrostyTheSnowman, Great job on this topic! I'm trying to activate the Nvidia 5200M in order to use an external monitor through a docking station using the Display Port connector. I already have this working on Yosemite and I'm trying to enable on El Capitan. Have plans to install Sierra, but not now due to software compatibilities. I'm facing some issues during the compilation of the DSDT and I'm not sure if I'm doing something wrong. I can understand most of the topics about Hackintosh, but DSDT/SSDT is something very unclear to me. I read lot's of posts related, but the problem is with me and I can't understand clearly. I'm getting a compilation error below because (I suspect) I didn't imported the Nvidia SSDT-7.dsl into DSDT.dsl. In fact, I don't know how to do it. Just merge the files? Is there any specific place in DSDT.dsl to insert the SSDT-7.dsl content? Should I copy part or full SSDT-7 content? DSDT.dsl 6839: \_SB.PCI0.PEG0.VID._OFF() Error 6084 - Object does not exist ^ (\_SB.PCI0.PEG0.VID._OFF) DSDT.dsl 6898: \_SB.PCI0.PEG0.VID._ON () Error 6084 - Object does not exist ^ (\_SB.PCI0.PEG0.VID._ON) I'm using the RehabMan iasl command with ACPI 6.1 in the terminal to compile. Another doubt that I have is about the _OSI to XOSI. I could insert in the Clover DSDT patch, but I didn't understand how to apply into DSDT. Is just a matter of renaming _OSI to XOSI inside DSDT? This USB3 step is a little bit confusing for me. Another part that I'm in doubt is the "added backlight properties to Nvidia _DSM (not needed for Intel)". And in the other part you mention "- Nvidia _DSM cleared and replaced with injection of backlight properties". Should I remove the _DSM methods via '[syn] Remove _DSM methods' or only remove the method content? Where is the content backlight properties? One thing that I'm curious, you mentioned to extract DSDT with Optimus activated. But I will use it deactivated to use the Nvidia card, is not a problem? Shouldn't extract the DSDT with Optimus unmarked on BIOS? I'm sorry to have all these questions, but I'm failing to enable the Nvidia card. Best regards, Pablo Iglesias
  4. Hi voidRunner, Yes, this is normal! I have the same output from the kext in the /var/log/system.log file. Please, let us know the output of the following commands: 1. Inside the /System/Library/Extensions directory, execute: kextlibs -undef-symbols VoodooSDHC.kext 2. Inside the /System/Library/Extensions directory, execute: grep -A3 IONameMatch VoodooSDHC.kext/Contents/Info.plist 3. Grab the Vendor and Device IDs: lspci -nn | grep SD 4. Start the machine without the SD card inserted, wait for the desktop to load completely, then open a terminal and execute: tail -f /var/log/system.log 4.1. Insert the SD card in the card reader: 4.2. Collect and send the output of the /var/log/system.log after the insertion of the SD card. Let's start with this information and see what we have. Cheers!
  5. Hi voidRunner, Try to insert the sd card after the boot process completes, when you have desktop available. But before you insert, check if the kext is loaded. You can check it following instructions in the Troubleshooting session of the main guide. Let me know what you had. Cheers!
  6. Thanks Shiecldk! There is no source but the kext (VoodooSDHC.kext). Just login and download the zip file. Let me know if you got it. Cheers!
  7. Hi RobertB, Good to know that worked for you with Patel4Prez updates!
  8. Thanks Jake Lo for your contribution to Npjohnson. Npjohnson, That's why I tried to explain the most generic as possible. It's possible to extend to different number of SD Card controller. I really don't know which ones will work. It's good to know replying to this topic if your controller works! We can create a compatibility list of SD Card readers with this version of VoodooSDHC.kext. Just let us know the output of the command "lspci -nn". Thanks!
  9. Hi Bigman, Maybe it's possible to create a package, but not totally automatic. You need to have a minimum of knowledge of Vendor ID and Device ID of your SD card controller. That's why I showed you how to collect this info. It's possible that the kext could cover a range of SD card controllers, but unfortunately I don't know how to do it. Maybe someone wants to adventure in this field. Feel free to ask if you don't know how to do it. I'll be happy to help you. Cheers!
  10. Hi Patel4Prez, The VoodooSDHC.kext that I posted was already modified to my machine. I mentioned in the post how to change if necessary. I'm glad to know that worked on all your machines! Thanks for the feedback! Pablo Iglesias
  11. Hi Patel4Prez, I wrote a new topic about the SD Card reader in Latitude E6410. See the link below. https://osxlatitude.com/index.php?/topic/5859-sd-card-reader-on-latitude-e6410/ Hope it helps!
  12. Hello all, This topic will cover how to enable the SD Card reader in the Latitude E6410. The information below try to describe my Latitude E6410 configuration: 2.4GHz Intel Core i5 4GB 1067 Ghz DDR3 NVS 3100M 512 MB (1440x900) BIOS version A13 This information worked for me in Mavericks and Mountain Lion. PLEASE, BACKUP YOUR MEMORY CARD BEFORE TRYING THIS PROCEDURE. I CAN'T GUARANTEE IF THE DATA WILL BE SAFE AFTER YOU TEST WITH THE INFORMATION DESCRIBED BELOW. First, you need to find out the "Vendor ID" and the "Device ID" of your SD card controller. I used the "System Info" tool from El Coniglio and Oldnapalm. Another way to get this info is using the "lspci" command in the terminal: (you need to have the "lspcidrv.kext" in S/L/E) localhost:/ piglesias$ lspci -nn | grep SD pcilib: 0000:01:00.0 64-bit device address ignored. pcilib: 0000:01:00.0 64-bit device address ignored. 04:00.0 SD Host controller [0805]: Ricoh Co Ltd MMC/SD Host Controller [1180:e822] (rev 03) In my case, the SD card reader has the Vendor ID = 1180 and the Device ID = e822, as you can see in red above. With this information in hands, you can edit the "Info.plist" file from VoodooSDHC.kext (version 1.1.2b1). VoodooSDHC.kext.zip - Edit the file "VoodooSDHC.kext/Contents/Info.plist": In order to edit the Info.plist file, you can use any text editor. In my case, I used "vim". Inside the "Info.plist" file, search for the string "IONameMatch". You will find something like this: <key>IONameMatch</key> <array> <string>pciVVVV,DDDD</string> </array> Replace the "VVVV" by the Vendor ID and the "DDDD" by the Device ID you got from your hardware. Copy the VoodooSDHC.kext to /System/Library/Extensions and then repair the permissions and rebuild the S/L/E cache with your preferred tool. I used Kext Wizard. Reboot the machine in order to load the VoodooSDHC.kext. After the reboot, insert the SD card and check inside the Finder. Let me know if it works for you. Troubleshooting: Check if the VoodooSDHC.kext loaded. Type in the command line: localhost:~ piglesias$ kextstat | grep VoodooSDHC 53 0 0xffffff7f80b1e000 0x4000 0x4000 org.voodoo.VoodooSDHC (1.1.2b1) <15 11 5 4 3 1> If not loaded, check the /var/log/system.log file and try to find the reasons why the "VoodooSDHC.kext" didn't load. Check the session "OSBundleLibraries" in the bottom of "VoodooSDHC.kext/Contents/Info.plist". There you will see the dependencies of the kext. Verify if you satisfy all the dependency versions with your installed kexts. Another way to check if your kexts are satisfying the "VoodooSDHC.kext" dependencies, you can try in the command line: localhost:~ piglesias$ kextlibs -undef-symbols /System/Library/Extensions/VoodooSDHC.kext For x86_64: com.apple.iokit.IOStorageFamily = 1.9 com.apple.kpi.iokit = 13.0 com.apple.kpi.libkern = 13.0 com.apple.kpi.mach = 13.0 2 symbols not found in any library kext: __ZN9IOService19_RESERVEDIOService0Ev __ZN9IOService19_RESERVEDIOService1Ev In my case, these last two symbols not found, don't disturb the kext to be loaded.
  13. Hi Patel4Prez, First of all, just to congratulate you for the great guide to install Mavericks! I would like to give you some suggestions about your guide, but I'm not sure if it's the right topic. Let me know where is the best place to do so. Not sure if you already have the SD card reader working, but mine is working fine so far. I haven't tested extensively, and it's impossible to cover all the scenarios. Just reading and writing on my E6410. Let me know if you want to cover on a new topic. Thanks, Pablo Iglesias
  14. Hi Brainlobe, In order to have the shutdown working properly, you will need to patch the DSDT. At least worked for me. You can find a patched DSDT.aml for Latitude E6410 in the topic of Patel4Prez to install the Mountain Lion. The link is below: https://osxlatitude.com/index.php?/topic/1695-e6410-mountain-lion-guide/ Search for the file "E6410 ML 10.8.4.zip", extract the DSDT.aml file and save it in /Extra of your Mavericks installation. After this, you need to edit the "/Extra/org.chameleon.Boot.plist" and insert the lines below: <key>DSDT</key> <string>/Extra/DSDT.aml</string> You can use the Chameleon Wizard that's easier to edit the "/Extra/org.chameleon.Boot.plist" file. After, just reboot to read the DSDT.aml configs. Try to shutdown and check if it works for you. Hope it helps! Thanks, Pablo Iglesias
×
×
  • Create New...