Jump to content

wern

Members
  • Posts

    71
  • Joined

  • Last visited

  • Days Won

    6

Posts posted by wern

  1. I managed to boot from UEFI's HDD partition (it's formatted FAT32)... This HDD is a small one for test purposes....

     

    I finished my backup and will try to reproduce these results in my main larger HDD... but right now I can't get UEFI to read the EFI partition to create the UEFI boot entry... let's see what happen after Windows install...

     

    Thx

    On both of my drives the EFI partition is FAT32, if it freezes you can try to add the path manually, no issues here

    post-7507-0-22246700-1458233088_thumb.jpg

  2. The fact is, as I suspected, Intel 6 series chipsets UEFI support are buggy... I found a lot of posts with the same issue...´

    No issues here with UEFI, it runs flawlessly for more than a year on my SSD, also on a test drive with 10.9, 10.10, 10.11 and Windows, where i use legacy and UEFI.

  3. Strange, i've seen a few posts with low volume on headphones.
    For me the headphone volume was to loud, with this kext it should be loud enough, if not i can give you one with louder headphone volume.
    You have to set your layout-id to 0, i'm afraid it becomes a new challenge, but it can be simply changed @dsdt

  4. No issues here with clover UEFI while booting El Capitan, Yosemite, Mavericks, Win10, Ubuntu from one drive

     

    post-7507-0-23324400-1446756739_thumb.pn

     

    Nothing special only added "OsxAptioFix2Drv-64.efi", "NTFS.fi" @drivers64UEFI folder, i've unchecked nearly  all clover patches 

    <key>ACPI</key>
    	<dict>
    		<key>DSDT</key>
    		<dict>
    			<key>Debug</key>
    			<false/>
    			<key>DropOEM_DSM</key>
    			<false/>
    			<key>ReuseFFFF</key>
    			<false/>
    		</dict>
    		<key>DropTables</key>
    		<array>
    			<dict>
    				<key>Signature</key>
    				<string>MCFG</string>
    			</dict>
    		</array>
    		<key>SSDT</key>
    		<dict>
    			<key>DropOem</key>
    			<true/>
    			<key>EnableC6</key>
    			<true/>
    			<key>Generate</key>
    			<false/>
    		</dict>
    	</dict>
    

    post-7507-0-23324400-1446756739_thumb.png

  5. Thanks a million Dr. Hurt, with Release 4 you've made the biggest improvement, no pointer movement while tapping anymore.

     

    try disable BAT1 and BAT2 with

    method (_STA....)

    {

    //nothing

    }

    It's already done, else it dosen't work with the old driver, also compared the debug output from battery kext with both drivers, all the same instead of battery status
  6. @Jake Lo, i'm using clover without FixRegions, otherwise i've also no battery status with the old driver.

     

    @Dr. Hurt, i've installed this driver on my neighbors Toshiba and it works very well but the log file shows me this: 

     

    Found ALPS Device with ID E7=0x10 0x00 0x64, EC=0x10 0x00 0x64

    Unknown ALPS touchpad, does not match any known identifiers: E7=0x10 0x00 0x64, EC=0x10 0x00 0x64

×
×
  • Create New...