Jump to content

Zprood

Members
  • Content Count

    248
  • Joined

  • Last visited


Reputation Activity

  1. Like
    Zprood got a reaction from litaocomet in USB Card Reader Apple Optimized Legacy Driver (10.6.5/10.6.6/10.6.7/10.6.8)   
    Thanks ,works perfectly.









  2. Like
    Zprood reacted to TimeWalker75a in OSX on DELL Vostro 3450 / Inspiron N4110 / XPS L702x UEFI Clover   
    In the bar at the bottom of the manager there's a thingy to set nvram theme - this is what you need to set.
  3. Like
    Zprood reacted to TimeWalker75a in OSX on DELL Vostro 3450 / Inspiron N4110 / XPS L702x UEFI Clover   
    Hello.
    Clover is undergoing some serious rewamp right now, until it's finished I'm not touching the configs (also, why would I, anyway?). The only kext that hasn't been updated for Yosemite (just generally updated, really) is the voodoo kext, to reduce touchpad sensivity when scrolling. Other than that, all the kexts have been updated with rev 1.1.1 of SCT package. Though true, ACPIBattery driver hasn't been updated, but the update functionality is irrelevant to our line-up of laptops, like I said earlier, I will push these with a next major update. 
  4. Like
    Zprood reacted to TimeWalker75a in OSX on DELL Vostro 3450 / Inspiron N4110 / XPS L702x UEFI Clover   
    For multitouch gestures to work you have to assign F3 and F6 keys to whichever action you fancy. I have them set to Expose and Show Desktop. Command+X is assigned to toggle notification center and Dell Support Center is configured to show Launchpad. The touchpad speeds is indeed to high and has been corrected, but I haven't uploaded a changed config yet - not too many changes to roll out a new revision. 
  5. Like
    Zprood reacted to TimeWalker75a in OSX on DELL Vostro 3450 / Inspiron N4110 / XPS L702x UEFI Clover   
    I do believe you - it's not a problem with Mac, it's a problem with DELL drivers. At least ones that come bundled in my recovery Windows 7 Professional image ... since there are no newer drivers from Realtek that would enable SRS sound I'm forced to used these ones which have the bug. When I had Windows 8.1 Update 1 installed this never happened .. but for for some peculiar reasons I was forced to go back to Windows 7 and now we are back to square one.
  6. Like
    Zprood got a reaction from pcnewpinky in AppleACPIBatteryManager/AppleSmartBatteryManager For Lion   
    First Of All, Thanks these people for the battery driver:Chun-Nan, zenglg1977, gsly, bcc9, VIVXIX, weizh126. Cause without what they do can't get it work.Now start the topic.
     
    Since apple changes some things on lion, the Appleacpibatterymanager does't work any more under the Lion, so people use roll backed next to get is work, but this has shortage. At the first, bcc9 found that lion reads battery info from EC by 8bit, and most laptop's EC region use 16bit to store battery information, so the legacy driver doesn't work include voodoo battery. This information is important for next.
     
    The guy zenglg1977 takes some time to rewrite the sources code of Appleacpibatterymanager to make it work for lion. It is needed to edit the code of battery in the dsdt, so divide 16bit register into two 8bit can make sense. Like:

    Before // Field (RAM, ByteAcc, Lock, Preserve) { Offset (0xE0), BSDC, 16, BSDV, 16, BSSN, 16 } // Later // Field (RAM, ByteAcc, Lock, Preserve) { Offset (0xE0), SDC0, 8, SDC1, 8, SDV0, 8, SDV1, 8, SSN0, 8, SSN1, 8 } //
    then, the transmit part can be done like this:
    For example:
     

    Before: Multiply (BSDC, 0x0A, Local1) Later: Multiply (SDC1, 0x100, Local1) Add (SDC0, Local1, Local1) Multiply (Local1, 0x0A, Local1) Before: Store (BSDC, Local1) Later: Multiply (SDC1, 0x100, Local1) Add (SDC0, Local1, Local1)
     
    This way created by zenglg1977, after done with this can make it work.
    But when compare VIVXIX with others method, i found his method is simple and easy to reach, it named "B1B2".
    Here is his method:
    1, create the "Method (B1B2, 2, NotSerialized)" as global:

    Method (B1B2, 2, NotSerialized) { Or (ShiftLeft(Arg1,0x08), Arg0, Local0) Return (Local0) } //for 16bit Method (B1B4, 4, NotSerialized) { Or (ShiftLeft(Arg1,0x08), Arg0, Local0) Or (ShiftLeft(Arg2,0x10), Local0, Local0) Or (ShiftLeft(Arg3,0x18), Local0, Local0) Return (Local0) } //for 32bit Method (L1L4, 4, NotSerialized)//32*4=128 { Or (ShiftLeft(Arg1,0x20), Arg0, Local0) Or (ShiftLeft(Arg2,0x40), Local0, Local0) Or (ShiftLeft(Arg3,0x60), Local0, Local0) Return (Local0) }//for 128bit
     
    2, change the 16bit register into two 8bit register, like:

    //BPV0, SPV0, 8, SPV1, 8,
    3, here is some collections of example editing work he finished before.
    A:

    //Store (^^EC0.BAC0, Local5) Store (B1B2(^^EC0.SAC0,^^EC0.SAC1), Local5)
     
    B:

    //Store (^^EC0.BDC0, Index (STAT, One)) Store (B1B2(^^EC0.SDC0,^^EC0.SDC1), Index (STAT, One))
     
    C:

    //Multiply (BGU1, BFC1 ,Local2) Multiply (BGU1, B1B2 (BFC0, BFC1), Local2)
     
    Some special parts as below:
    D:

    //If (^^EC0.BDC0 ) If (B1B2(^^EC0.SDC0,^^EC0.SDC1))
     
    E:

    //If (LGreater (^^EC0.BAC0, 0xFB00)) If (LGreater (B1B2(^^EC0.SAC0,^^EC0.SAC1), 0xFB00)
     
    F:

    //Store (^^EC0.BDC0, BFC1) Store (^^EC0.SDC1, BFC1) Sleep (0x14) Store (^^EC0.SDC0, BFC0)
     
    More about the sources code, zenglg1977 combines gsly's AppleSmartBatteryManger code into whole project, then people get two choice. And weizh126 plays a trick about battery cycle count in the _BIF method part, the _BIF just contains 13 items in the package and he adds "Zero" to it become 14, and store the cycle count register info in it, it sounds illegal, but it works.
     
    Last, here is the sources code and attachments.
     
    AppleBatteryManager_src.zip
    AppleACPIBatteryManager.kext.zip
    AppleSmartBatteryManager.kext.zip
     
    Update for 10.7.3
    AppleBatteryManager_src.zip
    AppleSmartBatteryManager.kext.zip
    AppleACPIBatteryManager.kext.zip
     
    Also screenshots:


     
    Original link address:
    http://bbs.pcbeta.co...935509-1-1.html
    http://bbs.pcbeta.co...935582-1-1.html
  7. Like
    Zprood got a reaction from Mieze in Driver for Realtek's RTL810x Fast Ethernet Series   
    Good job, my chip is RTL8136, mavericks 10.9.2, test works well. 
    Mail/DHCP/sleep&wakeup/AppStore/plug&unplug, WoL haven't test. But all play good. 


  8. Like
    Zprood reacted to TimeWalker75a in OSX on DELL Vostro 3450 / Inspiron N4110 / XPS L702x UEFI Clover   
    When I first started deciphering registers Aida used direct Dell ec access which lagged, only when I posted some info about sensors Aida switched to monitoring through acpi. I'm not implying they used the knowledge I have collected, but its just a weird coincidence. Good find none the less!
     
  9. Like
    Zprood got a reaction from TimeWalker75a in OSX on DELL Vostro 3450 / Inspiron N4110 / XPS L702x UEFI Clover   
    I think i find a easy way to find the registers under windows. 
    First, install windows then install AIDA64, then run it, like below:

    you can see the sensors like the screen then right click from bottom bar, choose sensors dump--Embedded xxxx. then you can have this:

    so, scroll down to bottom, you can see all the registers from you sensors, fan and other temps sensors. For fan, u can see the last two registers name( it can be found in the DSDT), other temps registers name, you just need to compare the value of them, basically it's a simple way to do that, also you can use RW, the find the Offset to match different register function. 
  10. Like
    Zprood reacted to RehabMan in OSX on DELL Vostro 3450 / Inspiron N4110 / XPS L702x UEFI Clover   
    0 step as black is 'by design'. It is the way Macs work. My Apple MacBookAir is the same.
  11. Like
    Zprood reacted to TimeWalker75a in OSX on DELL Vostro 3450 / Inspiron N4110 / XPS L702x UEFI Clover   
    There you go .. the behavior coded in is the same as "Audible" profile under Windows.
    I will update the "Passive" profile's analog and push this to git when I have time. 
    HWMonitor application has been patched to include monitoring for fan control mode. As expected - it's either auto or steady.
     

     
    osx-fan-control.zip
    mirror: https://www.dropbox.com/s/t69jtriziymbtih/osx-fan-control.zip
  12. Like
    Zprood reacted to TimeWalker75a in OSX on DELL Vostro 3450 / Inspiron N4110 / XPS L702x UEFI Clover   
    Taking 2 PIOs is completely normal, it will require a 2nd PIO sooner or later.. So its better when it happens right at wake, rather than in a distant unpredictable future.
  13. Like
    Zprood reacted to TimeWalker75a in OSX on DELL Vostro 3450 / Inspiron N4110 / XPS L702x UEFI Clover   
    Sure, here you go. I've tossed in the latest CC revision from git that works best for me right now (requires single PIO and jack sense works too).
     
    I'm experimenting with defining custom output numbers though config, but even though it appear to end up with the same path, behavior changes to the way it was before .. when I had badly patched kext.. So I'm debating if I should settle at how it works right now or tinker some more and allow customization through plist.. its open source anyway, so anyone capable of changing 1 digit and pushing CMD+B would be able to change that.
     
    But let us see how the current CC build works for you .. if it will also require just a single PIO for EAPD bit to stick .. then we are definitely settling on this hardcoded approach.
     
    C48-HDA-CC.zip
  14. Like
    Zprood got a reaction from badman0_8 in OSX on DELL Vostro 3450 / Inspiron N4110 / XPS L702x UEFI Clover   
    here it is one which edit default value, you can install without modification. What change:
    1. enable Fn+F3 to diable trackpad.
    2. three fingers assign gesture like: swipe down > mission control(F3), swipe up > show desktop(F5), swipe left and right > back & forward(CMD+[&])
    3. Context Key (App windows) > Launchpad
    4, double finger click > right mouse click.
     
    VoodooPS2Controller.kext.zip
     
  15. Like
    Zprood reacted to axel99092 in Edit plist inside a kext   
    I have added it.
     

  16. Like
    Zprood reacted to TimeWalker75a in OSX on DELL Vostro 3450 / Inspiron N4110 / XPS L702x UEFI Clover   
    So, you are running Clover-EFI and not UEFI, because PBR is only meant for Clover-EFI. I kinda knew that Clover-EFI can boot legacy installations of Windows, but UEFI Clover is not capable of doing this, sadly. 
     
     
    Then you are obviously missing some pieces of the puzzle. Ensure that:
    1. Your AppleHDA has layout-28.aml.zlib and Platforms.aml.zlib in Resources folder
    2. You have CustomPeripheral kext that is properly loaded and has Hardware Config data in info.plist
    3. You have kext patches defined for AppleHDA patching inside the config file of Clover
    4. You have either my CodecCommander or EAPDFix kext installed in your system
    5. You have antipop installed along the plist file provided in the OP of this thread.
    6. Your Clover config.plist also contains kext patch for SNB Framebuffer connectors
    If you are missing at leased one of these things mentioned above your sound is bound to be broken.
  17. Like
    Zprood reacted to TimeWalker75a in [Guide] Dell XPS 15 L502X (Early 2011) Snow Leopard Install (possibly L702x too)   
    @jkbuha, just look at the files from my guide .. you don't need anything extra. I've same ACL269VB chip as sits in your 15z so don't go all *I'm stuck now* when everything has been posted. 
    I haven't touched a thing in this setup (in terms of getting the audio codec working) since 10.7.5 hit.
  18. Like
    Zprood got a reaction from sky-lo-fi in OSX on DELL Vostro 3450 / Inspiron N4110 / XPS L702x UEFI Clover   
    as i suggest that you can make it install successfully, then apply this patches to you. because you have much things to learn and understand. 
    about GUI, TW set text only mod, so you won't see it. And you have a different CPU compare with TW, i need delete SSDT-2.aml from patched folder, and i modify a config.plist to you, replace it. config.plist.zip
  19. Like
    Zprood got a reaction from Mohamed Khairy in OSX on DELL Vostro 3450 / Inspiron N4110 / XPS L702x UEFI Clover   
    about iMessage, if you use clover you should add two options  under "RtVariables"
    one more thing, if your account doesn't activated in iso device or real mac, you should add a credit card to it, then change your password of account, then problem solved. 
  20. Like
    Zprood reacted to Alex009988 in How to get rid of any Sound Assertions on AppleHDA   
    Hello. I had fully-working codec for ALC670, but there was only two issues.
    The first, endless assertions
    03/10/13 20:56:34,000 kernel[0]: Sound assertion in AppleHDAWidget at line 2181 03/10/13 20:57:24,000 kernel[0]: Sound assertion in AppleHDAWidget at line 2181 03/10/13 20:58:14,000 kernel[0]: Sound assertion in AppleHDAWidget at line 2181 03/10/13 20:59:24,000 kernel[0]: Sound assertion in AppleHDAWidget at line 2181 03/10/13 21:00:25,000 kernel[0]: Sound assertion in AppleHDAWidget at line 2181 The second, two pops when computer goes to sleep and wakes up.(Only for Mavericks)
    I decided to solve the problem with Assertions.
    I tried to do much on my own, but it was unsuccessful. 
    After I asked TimeWalker for any help, he guessed that the problem was with SPDIF  as AppleHDA was looking for special type of node, namely 0x04.
    pinconfig for SPDIF
    01e71c60 - Association Nr/ Sequence Nr 0
    01e71d11 - Black / Reserved
    01e71e4b - SPDIF / Combo
    01e71f01 - Port is connected to a Jack / External on primary chassis / Rear
    pin-default for this node is 0x014b1160, and driver want to have 04 at one specific place(but it was only a supposition)
    Of course, I tried all possible variants. But it was unsecesfful either.
    First Variant - the error didn't disappeared 01B71C40 01B71D10 01B71E2B 01B71F01 01571C30 01571D01 01571E13 01571F90 01271C10 01271D01 01271EA0 01271F90 01A71C50 01A71D31 01A71E81 01A71F01 01971C20 01971D90 01971E81 01971F01 01E71C04 01E71D11 01E71E4B 01E71F01 01171CF0 01171D00 01171E00 01171F40 01371CF0 01371D00 01371E00 01371F40 01471CF0 01471D00 01471E00 01471F40 01671CF0 01671D00 01671E00 01671F40 01771CF0 01771D00 01771E00 01771F40 01871CF0 01871D00 01871E00 01871F40 01D71CF0 01D71D00 01D71E00 01D71F40 02171CF0 02171D00 02171E00 02171F40 Second Variant - the error didn't disappeared 01B71C40 01B71D10 01B71E2B 01B71F01 01571C30 01571D01 01571E13 01571F90 01271C10 01271D01 01271EA0 01271F90 01A71C50 01A71D31 01A71E81 01A71F01 01971C20 01971D90 01971E81 01971F01 01E71C60 01E71D04 01E71E4B 01E71F01 01171CF0 01171D00 01171E00 01171F40 01371CF0 01371D00 01371E00 01371F40 01471CF0 01471D00 01471E00 01471F40 01671CF0 01671D00 01671E00 01671F40 01771CF0 01771D00 01771E00 01771F40 01871CF0 01871D00 01871E00 01871F40 01D71CF0 01D71D00 01D71E00 01D71F40 02171CF0 02171D00 02171E00 02171F40 Third Variant - the error disappeared but it had broken down the sound completely 01B71C40 01B71D10 01B71E2B 01B71F01 01571C30 01571D01 01571E13 01571F90 01271C10 01271D01 01271EA0 01271F90 01A71C50 01A71D31 01A71E81 01A71F01 01971C20 01971D90 01971E81 01971F01 01E71C60 01E71D11 01E71E04 01E71F01 01171CF0 01171D00 01171E00 01171F40 01371CF0 01371D00 01371E00 01371F40 01471CF0 01471D00 01471E00 01471F40 01671CF0 01671D00 01671E00 01671F40 01771CF0 01771D00 01771E00 01771F40 01871CF0 01871D00 01871E00 01871F40 01D71CF0 01D71D00 01D71E00 01D71F40 02171CF0 02171D00 02171E00 02171F40 Forth Variant - the error didn't disappeared 01B71C40 01B71D10 01B71E2B 01B71F01 01571C30 01571D01 01571E13 01571F90 01271C10 01271D01 01271EA0 01271F90 01A71C50 01A71D31 01A71E81 01A71F01 01971C20 01971D90 01971E81 01971F01 01E71C60 01E71D11 01E71E4B 01E71F04 01171CF0 01171D00 01171E00 01171F40 01371CF0 01371D00 01371E00 01371F40 01471CF0 01471D00 01471E00 01471F40 01671CF0 01671D00 01671E00 01671F40 01771CF0 01771D00 01771E00 01771F40 01871CF0 01871D00 01871E00 01871F40 01D71CF0 01D71D00 01D71E00 01D71F40 02171CF0 02171D00 02171E00 02171F40 After, a user called vladlenas saw my desperate attempts. And told me that he didn't solve it as well by using a similar method.
    And show me his the solution of the problem.
    He had that error
    Sound assertion "kTypePinComplex != fType" failed in AppleHDAWidget at line 2043 goto Exit ascii to hex
    536F756E6420617373657274696F6E20226B5479706550696E436F6D706C657820213D20665479706522206661696C656420696E204170706C65484441576964676574206174206C696E65203230343320676F746F20457869740A And replaced it by this in AppleHDA
    00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 In my opinion, it looks too large. Moreover, I couldn't find it   for my mistake(another long patch for 2181) at the kext
    So I decided  to make the universal patch against any assertion.
    536F756E 64206173 73657274 696F6E20 to
    00000000 00000000 00000000 00000000 And what do you think? All of the assertions have disappeared. Now I have clean Console.
    I check sleep, ports. Everything works as it was before.
    The solution for Clover-bootloader, you know, Clover can patch any kexts
    <dict> <key>Comment</key> <string>Patch_against_assertions</string> <key>Find</key> <data> U291bmQgYXNzZXJ0aW9uIA== </data> <key>Name</key> <string>AppleHDA</string> <key>Replace</key> <data> AAAAAAAAAAAAAAAAAAAAAA== </data> </dict> Solution for XPC-bootloader
    <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>XpcPatcher</key> <dict> ............................. <key>MachOPatch3</key> <dict> <key>Apply</key> <integer>1</integer> <key>SystemVersion</key> <string>0x000</string> <key>Description</key> <string>Patch against assertions for AppleHDA</string> <key>FileName</key> <string>AppleHDA</string> <key>Search</key> <string>536F756E6420617373657274696F6E20</string> <key>Replace</key> <string>00000000000000000000000000000000 </string> </dict> </dict> </dict> </plist>  Please, give a feedback if it works for you too.
  21. Like
    Zprood got a reaction from robin_hood in OSX on DELL Vostro 3450 / Inspiron N4110 / XPS L702x UEFI Clover   
    you should take a look about rehabman's voodoops2controller github guide. i give some advice about it. if you use TW's kext, add your board-id under Dell's alias, or you take stock one from rehabman.
    1. for brightness key work, install TW's IOWMIController from his guide. then mod dsdt like this( DO IT BOTH _Q80 method and _Q81):
    before:
    If (LEqual (OSYS, 0x07D6)) { //......// If (PWRS) { Store (Local0, BRGA) } Else { Store (Local0, BRGD) } Store (0x03, ^^^^AMW0.INF0) Store (Zero, ^^^^AMW0.INF1) Store (0xE006, ^^^^AMW0.INF2) Store (Local0, ^^^^AMW0.INF3) If (LEqual (DMFG, Zero)) { Notify (AMW0, 0xD0) } //....// } after:
    If (LEqual (OSYS, 0x07D6)) { //......// } If (PWRS) { Store (Local0, BRGA) } Else { Store (Local0, BRGD) } Store (0x03, ^^^^AMW0.INF0) Store (Zero, ^^^^AMW0.INF1) Store (0xE006, ^^^^AMW0.INF2) Store (Local0, ^^^^AMW0.INF3) If (LEqual (DMFG, Zero)) { Notify (AMW0, 0xD0) } 2. for disable touchpad from TW's voodoops2controller, you can use PrintScr key to do that, because his remap fn+f3 to PrintScr key. one more thing, you can have it back to Fn+F3, just remap it twice in the custom ps2 map, like:
    e01e=e037 e037=e01e   e01e is scan code of Fn+F3, e037 is PrintScr.

    @TW, i think i should say great work this time.   
  22. Like
    Zprood reacted to TimeWalker75a in [Guide] Dell XPS 15 L502X (Early 2011) Snow Leopard Install (possibly L702x too)   
    Inspiron 14R (N4110) post install and Clover UEFI files posted, same guide applies.
    Thanks to @Zprood for collaboration.
  23. Like
    Zprood reacted to TimeWalker75a in OSX on DELL Vostro 3450 / Inspiron N4110 / XPS L702x UEFI Clover   
    This guide will discuss the process of getting OS X Mavericks or Yosemite to run on Vostro 3450 / Inspiron N4110 / XPS L702x using UEFI Clover, no other discussions please.
    I should start by saying that I'm not responsible for any bricks that may happen if you follow this guide and I'm not saying I will be updating this with every bit of changes I do to my personal system after every minor OSX upgrade. Though, with this kind of setup you shouldn't have to lift a finger after installing OSX updates... Also, don't mirror my files!
     
    This is your goal:

    I'm sure if you ended up here you probably know the majority of limitation that Phoenix SecureCore Tiano firmware applies to this system, but I'll mention them none the less:
    - Can't boot GPT formatted disk with legacy bootloader such as XPC, Chameleon, Chi*mera
    - Can't boot UEFI OS or bootloader as UEFI is locked down from the factory
    - Cardreader is not bootable
    - Secondary disk installed in place of DVD drive is not bootable either
    - BIOS doesn't let you disabled Turbo Boost or Hyper Threading

    So, let's get to the point, shall we?

    1. Flashing a UEFI-capable modified BIOS

    BIOS images are meant only for Dell Vostro 3450, Inspiron N4110 and XPS L702x (both Intel model and AMD/nVidia models) and no other! Vostro 3350 and 3550 use AMI Aptio BIOS, not SecureCore Tiano!

    Modified BIOS images includes the following changes:
    - Unlocked write access to MSR 0xE2 - credits to RevoGirl;
    - Unlocked Advanced Setup options (includes UEFI Boot option) - credits to jkbuha, HairyCube and myself;
    - CPUID 206A7h microcode updated to V28 - credits to jkbuka (again) and Florin9doi;
    - Video BIOS for Intel updated from 2098 to 2170 with GOP protocol support (bring 1366x768 resolution to GUI) - credits to Ash;
    - BIOS DSDT modified to fix Dell's ACPI syntax screw-up while checking for MBT (media buttons) - credits for PhoenixTool fix in 2.14 to AndyP.

    In order to flash the modified BIOS image you have to obtain it first. Make sure to read the enclosed readme.
    - Vostro 3450 A13-C4: LINK
    - Inspiron N4110 A12-C4: LINK
    - XPS 17 L702x A19-C4: LINK
     
    Use WinFlash method if you are on stock DELL BIOS.
    If you already have UEFI capable BIOS I recommend using PFlash method to prevent BIOS settings from being reset.

    When you are done flashing go to your BIOS Setup and navigate to Advanced tab, go to Boot Configuration section and enable UEFI Boot.

    2. How to install OSX

    In case you want to boot Legacy Windows from primary HDD (because let's face it, Dell made it pretty hard to use UEFI Windows with all the freezing issues caused by their proprietary software while having a UEFI installation) and you have a caddy in place of your DVD drive with a disk you want to dedicate to booting OSX simply put you can't do that by default BIOS means as caddy is not bootable. You can only make it bootable as a UEFI medium and there is why this guide was even put together. Also I should mention that booting Legacy Windows from UEFI Clover is a big no go with Tiano firmware, so don't expect that. The only way to access Legacy Windows is to either use F12 and choosing Hard Disk or exiting Clover.

    Now go ahead and download Clover bootloader that you will need for this guide :
    Required Pre Installation files: LINK
     
    2.1. You have to have a flash drive prepped with UEFI Clover (no need to prepare it in some weird way, just copy the files to it). Just format the flashdrive to FAT32 and put the contents of "UEFI Clover USB" onto it. 
     
    N.B. Make sure to rename EFI/CLOVER/config-17 or config-14 (depending on the computer model) to just config.plist, EFI/CLOVER/ACPI/patched-17 and patched-14 to just patched respectively!

    2.2. You need a second flash drive as well as an access to a genuine Apple computer (or a VM) that is capable of accessing Mac AppStore in order to download the free Mavericks installation app. Then, using DiskMakerX application you have to make a bootable OSX drive.
     
    2.3. When that's done use UEFI Clover USB drive to boot your OSX medium and partition your HDD in the DVD caddy as you desire, but make sure partition map is GPT. You can then install OSX to that target disk while you are at it. The installation process is usually subdivided into 2 stages.
     
    3. Post installation
     
    I've put together a convenient installer that allows you to put some needed finishing touched to your OSX installation on your supported DELL laptop. 

    Go ahead and download the installer (only OSX 10.9 & 10.10 is supported):
     
    DELL SCT OSX Support Package v1.1.3 - HERE | - PREV -
     
    When you run the installer you will need to select the destination disk you are installing it to. Please note, the files will be copied to EFI System Partition of active boot disk. 
    - Select laptop model
    - Select motherboard type 
    - Select daughterboard type
    - Select wireless module (limited support available)
    - Select "About This Mac" customizations for either Vostro, Inspiron, XPS
    - Select applications to install 
     
    If you are installing Support Package for the first time new serial numbers for MBP8,1 model identifier will be generated automatically, if you are reinstalling and already have your config in EFI partition serial numbers will be retained. The installer will put CLOVER onto your system partition and install all the necessary kernel extensions (preconfigured) to support your hardware.
     
     
    4. Adding Clover to your F12 Boot Manager
     
    When you have installed the Dell SCT OSX Support Package package remove your Clover USB drive, reboot your laptop and boot into Clover GUI, press F3 and start the Shell entry that has appeared. While in shell you first need to determine what is the number of file system of the EFI System Partition on your DVD caddy drive. Perform the command:
    map fs* The ESP on the GPT disk will be marked as GPT,1 and is usually either fs2 or fs3. Let's assume fs3 is ESP. We don't want the BOOT folder as it won't ever be bootable with HDD sitting in DVD caddy, so we get rid of that:
    fs3: cd \EFI rm -r BOOT Then, to add custom Clover Boot Manager entry you need to do the following:
    bcfg boot add 3 fs3:\EFI\CLOVER\CLOVERX64.efi "Clover" We used 3 here as by default in BIOS 0 is diagnostics, 1 is Bios Setup and 2 is Boot Manager. Now, go to your BIOS Setup and just for emergency set the boot order as follows:
    - USB - CD/DVD Drive - Clover - Hard Disk - eSata - Network - Removable Disk Having this boot order configuration first off will be as a precaution if something ever happens and you can't start the laptop normally, so USB as the first device will allow you to boot a crisis bios recovery PFlash.efi with a BIOS capsule. Also, this kind of boot order will allow you to boot legacy Windows installed on your primary HDD by just exitting Clover, so there won't be a need to go to boot menu (F12) to select HDD when you need to boot Windows.
    You can add Shell binary to boot menu the same way, you just have to point it to the other EFI application:
    bcfg boot add 9 fs3:\EFI\CLOVER\tools\Shell64U.efi "Shell" That's it. If you followed the guide at this point you should have a fully working OS X Mavericks installation.
     
    5. Known issues
     
    If anyone has any insights on fixing these remaining problems on this range of machines I would be very grateful. So far the problems are as follows:
     
    1. Wireless interface toggle hotkey (Fn+F2) doesn't work in UEFI mode and causes system to freeze, hence it was disabled in OSX ACPI using a custom patch. This is caused by a buggy UEFI implementation by DELL, which is the reason they originally locked it down from the factory. Use software toggles to control status of Bluetooth and Wi-Fi.
    2. HD3000 still has the ability to utilize VGA port with some minor annoyances, namely - no hotplug support. You have to connect the monitor before you start OSX and when you unplug the monitor in running system, OSX will still think it's connected until you reboot. 
    3. No support for docking mode for HDMI connector (works ok with VGA), meaning if you close the LID when HDMI screen or projector is connected laptop will enter sleep. 
    4. Having HDMI screen connected during shutdown and restart will cause the system to stall. Turn of the screen and unplug from laptop before shutting down or restarting. 
    5. On XPS L702x HDMI connector is physically linked to NVIDIA chip and therefore will not work in OSX due to Optimus being unsupported. DisplayPort connector is linked with Intel graphics and is known to work.
    6. Soft rebooting from Windows into OSX will leave the headphone socket non-operational until you cold boot OSX. 
     
    Credits to @Dokterdok  for providing detailed research and solution for Handoff & Continuity support. Tested with BCM943225HMB card. 
     
     

    Table design courtesy of OSX Latitude. I hope they are ok with me borrowing the canvas.
     
    Updated - 14th Jun 2015:
    - DELL SCT OSX Support package updated to v1.1.3
     
    Updated - 14th Feb 2015:
    - DELL SCT OSX Support package updated to v1.1.2
     
    Updated - 28th Sep 2014:
    - DELL SCT OSX Support package updated to v1.1.1
    - No reports from L702x Optimus users to this day... 
     
    Updated - 5 Sep 2014:
     
    - DELL XPS 17 L702X Optimus support added 
    - Major update to SCT OSX Support package bringing it's version to 1.1.0 (active testing needed!!)
     
    Update - 26 Jul 2014:
     
    - DELL SCT OSX Support Package updated to v1.0.4, includes Yosemite Beta support
     
    Update - 1 Jul 2014:
     
    - DELL SCT OSX Support Package updated to v1.0.3
     
    Update - 8 Mar 2014:
     
    - Mandatory BIOS updates have been posted. See enclosed readme for changes and installation information.
    - DELL SCT OSX Support Package updated to v1.0.2
     
    Update - 3 Mar 2014:
     
    - Clover updated to 2638
    - Post installation files packaged into .pkg installer v1.0.1 for convenience
    - Guide partially rewritten to be less confusing
     
    Update - 25 Feb 2014:
     
    - Clover updated to 2608
    - Updated grand majority of kernel extensions
    - Added fully remapped keyboard profile, all the keys can now be toggled to either use Fn or not .. straight from OSX (kudos RehabMan)
    - Added memory compartment temperature monitoring sensor
    - Added subtle brightness control using ACPIBacklight, levels adjust gradually and not in rough steps (kudos RehabMan, again)
    - Added fan control profiles - choose between automatic, audible (~3000 rpm) or passive modes from HWMonitor menu
    - Got rid of IOWMIFamily for display backlight control, now VoodooPS2 handles these too (1.8.11 and later)
  24. Like
    Zprood reacted to TimeWalker75a in [Guide] Dell XPS 15 L502X (Early 2011) Snow Leopard Install (possibly L702x too)   
    I had zero issue migrating to Mavericks. Finally posted my guide, but I don't feel like it will get any attention as this model is not really widely spread. 
  25. Like
    Zprood reacted to Dr. Hurt in [How To] Share files between OS X 10.7+ and Android over WiFi without SAMBA   
    **I'm not sure if this topic goes here so mods feel free to move it to the appropriate section.
     
    Ever since updating from 10.6.8 to 10.8.2, I've had a nasty problem with file sharing between my Android (ES File Explorer) and Mac OS.
    I could no longer authenticate into my Mac using SMB to access different "volumes". The only way was to add the entire volume I need as a public folder which in my case is totally unacceptable.
    I needed password protected access to the volumes.
     
     
    How I got around it?
    Easy. Using SFTP:
     
    I went into System Preferences -> Sharing -> marked "allow remote login".
     
    Next on my android tablet, I opened es file explorer, selected SFTP, typed my IP, user name and password and BOOM. I have full access to all mounted volumes again. And I believe its even faster than SMB.
     
    What happend between Snow Leopard and Lion/Mountain Lion?
    Well, I believe that Apple ran into a licensing issue with SAMBA so they had to trim down support for SMB and replace it with AFP. Only AFP can authenticate and access password protected volumes.
    This problem appears to be plaguing OS X Lion/ML users everywhere. Most people suggest reinstalling the old SAMBA which can be a pain in the @ss. I believe this solution is much more elegant.
     
    I hope this comes in handy to someone like me who depended on SAMBA to share files between android and Mac OS.
×