Jump to content

E6430 won't install


vclawson

Recommended Posts

  • Moderators

Have you tried toggling with Fn+F8 or bootup without the docking station? Do you get the same result?

I have seen it turned black after I log on sometimes, but hitting the escape key will get me onto the login screen and able to login into the gui.

Link to comment
Share on other sites

  • Replies 31
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

Yep, booting it undocked causes the dark screen on the native display. I'm going to double check the Extra contents and the DSDT. Something isn't just right. I'll post when I figure it out or end up at a dead end.

 

The Fn+F8 for some reason is not working when the machine is still in the preboot state so something isn't right with the Fn key. I'll make sure it's enabled in the BIOS.

Link to comment
Share on other sites

Yep, booting it undocked causes the dark screen on the native display. I'm going to double check the Extra contents and the DSDT. Something isn't just right. I'll post when I figure it out or end up at a dead end.

 

The Fn+F8 for some reason is not working when the machine is still in the preboot state so something isn't right with the Fn key. I'll make sure it's enabled in the BIOS.

Update: The display problem is definitely related to the DSDT I'm using.

No DSDT=Working built-in display (undocked); Working built-in display docked and ability to alternate from built-in to each external monitor 1 at a time via the Fn+F8 key; Mis-detected graphics card; Trackpad not working

 

DSDT=Proper graphics detection, fully functional external DVI and HDMI externals, trackpad and everything working; NO built-in display

 

The way I got the DSDT to work on my e6520 was by pasting and editing it using relevant information from other DSDTs including the one for the 6430 NVS 5200. I'm going to attempt to start with a vanilla and paste from the 6430 HD4000. TMB will be my friend. If I happen to get an alternate DSDT working on my system, I will upload it here in case others encounter a similar problem.

Link to comment
Share on other sites

The DSDT attached to the e6340HD4000 zip file has content referencing the NVS 5200 card. I'm not a DSDT expert and I'm still learning this so I am curious if the code in there is dormant and simply does not apply when no 5200 is present, or whether it can cause issues. The code starts on line 13359 and below is an excerpt from it. This DSDT almost works perfectly with my non-5200 e6430 except for the built-in display problem.

 

Snippet:

"device_type", 
                    Buffer (0x0C)
                    {
                        "NVDA,Parent"
                    }, 
                    "model", 
                    Buffer (0x11)
                    {
                        "nVidia NVS 5200M"
                    }, 
                    "rom-revision", 
                    Buffer (0x0E)
                    {
                        "NVS 5200M ROM"
                    }, 
                    "hda-gfx", 
                    Buffer (0x0A)
                    {
                        "onboard-2"
                    }
                }, Local0)
            DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
            Return (Local0)
Link to comment
Share on other sites

  • Moderators

I have the same on my DSDT and it's not causing any issue. What do you have under the device properties in boot.plist?

Try replacing with this to see if it makes any difference.

8800000001000000010000007c0000000200000002010c00d041030a000000000101060000027fff0400100000006d006f00640065006c0000001a000000496e74656c20484420477261706869637320343030302c0000004100410050004c002c00690067002d0070006c006100740066006f0072006d002d006900640000000800000003006601
Link to comment
Share on other sites

Jake Lo,

 

You just made my laptop work like a laptop. That device-properties string turned out to be the culprit the entire time. Adding it to org.chameleon along with GraphicsEnabler=No did the trick. Thank you for offering that solution. I hope others with similar configurations remember to add the string if their machines require it.  :)

Link to comment
Share on other sites

  • Moderators

Jake Lo,

 

You just made my laptop work like a laptop. That device-properties string turned out to be the culprit the entire time. Adding it to org.chameleon along with GraphicsEnabler=No did the trick. Thank you for offering that solution. I hope others with similar configurations remember to add the string if their machines require it.   :)

 

DraKuL71,

 

Glad we got this figured out. You could add this to the DSDT and disable the device properties to work as well.

 

Name (_ADR, 0x00020000)
            Method (_DSM, 4, NotSerialized)
            {
                Store (Package (0x08)
                    {
                        "AAPL,DualLink", 
                        Buffer (0x04)
                        {
                             0x01, 0x00, 0x00, 0x00
                        }, 


                        "AAPL,ig-platform-id", 
                        Buffer (0x04)
                        {
                             0x03, 0x00, 0x66, 0x01
                        }, 


                        "hda-gfx", 
                        Buffer (0x0A)
                        {
                            "onboard-1"
                        }, 


                        "model", 
                        Buffer (0x17)
                        {
                            "Intel HD Graphics 4000"
                        }
                    }, Local0)
                DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                Return (Local0)
            }
Link to comment
Share on other sites

Thanks so much for your efforts.
I get nothing but kernel panics with 10.8 and the HD4000 drivers and from anybody's extra folder I tried.
I tried 10.9 too but got a black screen and no hdmi output.
I have a i7 with nvidia card and 16gb memory.
C-states is enabled in BIOS, as is AHCI.

I keep having issues with powermanagement kexts.

it boots with -v -x DSDT=null.
Any clue how I can fix the issues?
I have a working 10.8.5 install now but can only boot with -v -x DSDT=null.
Otherwise it kernel panics.
Would be nice to get it working, especially with 10.9 :)

Link to comment
Share on other sites

  • Moderators

Thanks so much for your efforts.

I get nothing but kernel panics with 10.8 and the HD4000 drivers and from anybody's extra folder I tried.

I tried 10.9 too but got a black screen and no hdmi output.

I have a i7 with nvidia card and 16gb memory.

C-states is enabled in BIOS, as is AHCI.

I keep having issues with powermanagement kexts.

it boots with -v -x DSDT=null.

Any clue how I can fix the issues?

I have a working 10.8.5 install now but can only boot with -v -x DSDT=null.

Otherwise it kernel panics.

Would be nice to get it working, especially with 10.9 :)

Click on the link on my signature file below for your specific model. It includes instructions and bootpack too. I'm assuming E6430 with Optimus Nvidia nvs5200m?

Link to comment
Share on other sites

well, seems my bad: I had to disable optimus is bios, thought it was off. Now it boots properly.
Just no working sleep and webcam on 10.8.5.

Yes E6430 with dual graphics card.

thank you.

I think the webcam worked on the default install with DSDT=null.
Any clue how I can fix that?

Otherwise it looks good.
Too bad I cannot seem to boot Ubuntu properly with Optimus disabled, so I have to switch in bios.
Would be awesome if it works with optimus enabled :).

my macbook pro 15 retina has a similar hardware config.

thanks for the help anyway, it is usable, can't wait till it is working all.

Anyone has experience with 10.9?

Link to comment
Share on other sites


×
×
  • Create New...