Contribute
Register

Asus EP121 - Mountain Lion Install Help!

Status
Not open for further replies.
Thanks for the suggestion RehabMan. I've successfully gotten Mountain Lion 10.8.5 installed. Plugging in a Mini HDMI to DVI-D dongle helped. Doesn't actually need to be connected to a secondary monitor.

Will share the installation steps and the trouble shooting/thinking that got it to boot the installer. Once I have everything up and running to it's best ability.

Still need to update the Intel Graphics to the 3000 or 4000 (if I can) add the sound, wifi, and power management.

But again, I'll keep everyone posted.

Thanks.
 
iZac said:
Thanks for the suggestion RehabMan. I've successfully gotten Mountain Lion 10.8.5 installed. Plugging in a Mini HDMI to DVI-D dongle helped. Doesn't actually need to be connected to a secondary monitor.

Will share the installation steps and the trouble shooting/thinking that got it to boot the installer. Once I have everything up and running to it's best ability.

Still need to update the Intel Graphics to the 3000 or 4000 (if I can) add the sound, wifi, and power management.

But again, I'll keep everyone posted.

Thanks.
Click to expand...

HD3000 vs. HD4000 just depends on whether you have a Sandy Bridge or Ivy Bridge CPU. Don't forget to update your profile to include detailed specs for the system you're working on. What you do to make those work depends on which CPU you have and the resolution of your screen.
 
Hey all,

I'm almost there as far as a completed install of Mountain Lion 10.8.5 on my Asus EP121.

I've run into one snag that I hope someone can point me in the right direction for resolving.

The Asus EP121 Slate Computer has an i5-470UM, Arrandale. native resolution is 1280x800x32.

I've followed this guide for activating QE/CI
http://www.insanelymac.com/forum/topic/286092-guide-1st-generation-intel-hd-graphics-qeci/

I use the supplied kext files from the guide, and the Alternate Framebuffer kext supplied with the guide and am able to get QE/CI working, I'm also using Natit.kext as suggested in the guide to get it to actually load . . .

From the attachment though you can see I'm having an issue where the screen image is off set to the right (it also has a horizontal jitter).

Does anyone have a clue as to why this is happening? Can anyone point me in the direction for fixing? Thanks.
 

Attachments

  • IMG_6770.jpg
    IMG_6770.jpg
    522.9 KB · Views: 189
Thanks. Any thoughts then on why I'd get the off set image and jitter with my first attempts?
 
Can anyone tell me which Kext controls the EDID? Thanks. I'm wondering if I can edit it.
 
iZac said:
Can anyone tell me which Kext controls the EDID? Thanks. I'm wondering if I can edit it.
Click to expand...

I think you can inject EDID via DSDT. For example, from my patch repo (https://github.com/RehabMan/Laptop-DSDT-Patch):
Code: 
#Maintained by: RehabMan for: Laptop Patches
#graphics_EDID.txt

#
# Use this patch generic patch with EDID capability
# if your display seems to exhibit EDID problems.
#

#   Inject HDMI info and dual-link into GFX0/IGPU
into method label _DSM parent_adr 0x00020000 remove_entry;
into device name_adr 0x00020000 insert
begin
Method (_DSM, 4, NotSerialized)\n
{\n
    If (LEqual (Arg2, Zero)) { Return (Buffer() { 0x03 } ) }\n
    Return (Package()\n
    {\n
        //IMPORTANT: edit for actual snb-platform-id\n
        "AAPL,snb-platform-id", Buffer() { 0x00, 0x00, 0x01, 0x00 },\n

        //IMPORTANT: edit for actual ig-platform-id\n
        "AAPL,ig-platform-id", Buffer() { 0x04, 0x00, 0x66, 0x01 },\n

        //IMPORTANT: remove this line if not dual-link\n
        "AAPL00,DualLink", Buffer() { 0x01, 0x00, 0x00, 0x00 },\n

        //for HDMI-audio\n
        "hda-gfx", Buffer() { "onboard-1" },\n

        //EDID section: Fill in with your actual 128 bytes of EDID data\n
        "AAPL00,override-no-edid", Buffer (0x80)\n
        {\n
            0x00, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0x00, 0x06, 0xaf, 0xec, 0x23,\n
            0x00, 0x00, 0x00, 0x00, 0x0f, 0x15, 0x01, 0x04, 0x90, 0x22, 0x13, 0x78,\n
            0x02, 0xc8, 0x95, 0x9e, 0x57, 0x54, 0x92, 0x26, 0x0f, 0x50, 0x54, 0x00,\n
            0x00, 0x00, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01,\n
            0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0xce, 0x1d, 0x56, 0xe2, 0x50, 0x00,\n
            0x1e, 0x30, 0x26, 0x16, 0x36, 0x00, 0x58, 0xc1, 0x10, 0x00, 0x00, 0x18,\n
            0xdf, 0x13, 0x56, 0xe2, 0x50, 0x00, 0x1e, 0x30, 0x26, 0x16, 0x36, 0x00,\n
            0x58, 0xc1, 0x10, 0x00, 0x00, 0x18, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,\n
            0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,\n
            0x00, 0x00, 0x00, 0x02, 0x00, 0x0c, 0x3f, 0xff, 0x0a, 0x3c, 0x64, 0x11,\n
            0x19, 0x2f, 0x6e, 0x20, 0x20, 0x20, 0x00, 0xad\n
        },\n
  })\n
}\n
end;

I believe to get your 1st gen graphics you may have already done some injections via GFX0._DSM... so you would have to add the "AAPL00,override-no-edid" section. Don't use my EDID data (it is for my AUOv4 1080p display on my ProBook). Use MonInfo on Windows to gather your own EDID data.
 
Cool Thanks. I'll keep everyone posted.

Now that Maverick was announced to be free, I'm wondering if I'll go that route and have any success with it on this Tablet too.

Thanks again.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top