Jump to content
11 posts in this topic

Recommended Posts

Hey i have an Elitebook 8540w with:

 

core i 720qm

quadro fx 1800

8 GB Ram

 

an habe problems with hackintoshing it:

 

when triying [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] + retail disc the display turns of during installation, in save mode i get a memory steal panic.

 

with iatkos s3 and the flags: busratio=12 cpus=1 maxmem=2048 the installation runs fine but after the reboot, mac os says there is no mouse and keyboard. It also doesnt recognize mice attached via usb.

 

Reinstalled iatkos s3 with usb patch. Now it askes not for the mouse but for the keyboard first, but still no mouse movement and no recognition of usb mouse, keyboard at all usb ports

 

Any hints?

 

Thanks,

 

Can

I have some problems posting in this forum, my older reply got lost, i'll try to reconstruct the content.

 

 

 

I first had nothing new to tell about, except that the same issues with the black display on the internal screen happened at Linux too.

 

The Linux Comunity said, that it could be an Nvidia driver issue causing problems detecting the internal screens EDID settings. But manual injections didnt solve the problem.

 

 

 

So i waited for my Displayport to DVI adapter to arrive to test the whole thing with an external display.

 

 

 

When it arrived, i attached it, reinstalled [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] to reactivate graphics support and after reboot, MacOS showed up nicely on the external screen with acceleration and native resolution. But the internal Screen stood empty, and wasnt recogniced by MacOS.

 

 

 

Exactly the same behaviour under Linux!

 

 

 

Then i got deeper into DSDT patching using this Tutorial http://www.projectosx.com/forum/index.php?showtopic=515

 

 

 

When Compiling i got the following 4 Errors and 1 Warning:

 

 

 

Intel ACPI Component Architecture

 

ASL Optimizing Compiler version 20080926 [Oct 4 2008]

 

Copyright © 2000 - 2008 Intel Corporation

 

Supports ACPI Specification Revision 3.0a

 

 

 

./dsdt_fixed.txt 18661: Store (VGDD, 0x01)

 

Error 4095 - ^ syntax error, unexpected PARSEOP_INTEGER

 

 

 

./dsdt_fixed.txt 18663: And (Local1, 0x1F, Local2)

 

Error 4050 - ^ Method local variable is not initialized (Local1)

 

 

 

./dsdt_fixed.txt 18664: If (And (Local1, 0xFFE0))

 

Error 4050 - ^ Method local variable is not initialized (Local1)

 

 

 

./dsdt_fixed.txt 18871: 0x00

 

Error 4095 - ^ syntax error, unexpected PARSEOP_INTEGER, expecting '('

 

 

 

./dsdt_fixed.txt 18908: Wait (\_SB.BEVT, 0x10)

 

Warning 1104 - Possible operator timeout is ignored ^

 

 

 

ASL Input: ./dsdt_fixed.txt - 20674 lines, 766795 bytes, 8061 keywords

 

Compilation complete. 4 Errors, 1 Warnings, 0 Remarks, 3543 Optimizations

 

The interesting part: all errors are within the following Method:

 

Method (WGDD, 0, NotSerialized)

{

Store ("GetDisplayDevices", Debug)

Store (Package (0x03)

{

0x00,

0x04,

Buffer (0x04) {}

}, Local0)

Store (VGDD, 0x01)

Local1

And (Local1, 0x1F, Local2)

If (And (Local1, 0xFFE0))

{

Or (Local2, 0x20, Local2)

}

Store (Local2, Index (DerefOf (Index (Local0, 0x02)), 0x00))

Store (0x01, Index (DerefOf (Index (Local0, 0x02)), 0x01))

Store (0x01, Index (DerefOf (Index (Local0, 0x02)), 0x02))

Return (Local0)

}

 

So i am a absolute newbie but there seems to be going on something unusual with the display recognition, doesn't it?

 

 

I would like to post my hole DSDTs with and without the patching, but everytime i try, my posts get completely lost, i'll try to find a workarround soon.

 

Edit: I attached the files now...

 

So i am not getting further at this point because my DSDT editing skills are to low to edit this method i rarely understand. But i think this could be the right way getting the 8540w's internal Display to work!

DSDTbeforepatching.txt

DSDTafterpatching.txt

  • 3 weeks later...

Hi,

 

Now my update:

today my DisplayPort to DVI Adapter arrived. So I plugged it in, booted MacOS, reinstalled [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] to reactivate Graphics support and after a Reboot MacOS was nicely running on the external Display with full acceleration and native Solution. The internal display is still absolutely off and not recognized in the System Settings.

 

It seems to be a nvidia driver issue because the behaviour is exactly the same under Linux: No picture on the internal display and without reconfiguring anything working perfect on the external display.

 

The Linux Comunity says, that it could have something to do with gaining the displays EDID information via the internal connector.

 

I am hoping so bad that somebody will find a solution soon, i have no ideas left...

 

- Can

So here are my DSDT files before and after aplying the patching routine as in the Tutorial in my post before.

 

Patching those errors is to much for my skills, perhaps someone you nows what to do?

it would be so great, having a working internal display!

DSDTbeforepatching.txt

DSDTafterpatching.txt

Maybe you should ask to DSDT expert people here.

I am sure they can help you.

By the way, what is working and what's not? (I mean, without DSDT, because you couldn't make it works).

You have a really good and interesting hardware, should be great to have a macbook pro killer, 'cause is much better in hardware... I you can get all working (except wireless, for sure, but you can change it...) through the DSDT, I think that the people will think twice if they want a real b*llsh*t macbook pro or your kick ass laptop.

 

Cheers.

Maybe you should ask to DSDT expert people here.

I am sure they can help you.

By the way, what is working and what's not? (I mean, without DSDT, because you couldn't make it works).

You have a really good and interesting hardware, should be great to have a macbook pro killer, 'cause is much better in hardware... I you can get all working (except wireless, for sure, but you can change it...) through the DSDT, I think that the people will think twice if they want a real b*llsh*t macbook pro or your kick ass laptop.

 

Cheers.

 

Well thats what i thought wenn I bought it. :-)

I have problems with sound and the USB 2 ports. But I found reports on the web, where people tell that they made that working. I still have not really worked on that, because my Screen problem ist more interesting ;-)

USB 3.0 ist working, Trackpad is working, Ethernet is working, Bluray drive ist working, Bluetooth seems to work (havent, attached a device yet) Also didn't test firewire yet.

 

I have to make my DSDT working soon. Would be great having everything (except wireless) working :-)

Well thats what i thought wenn I bought it. :-)

I have problems with sound and the USB 2 ports. But I found reports on the web, where people tell that they made that working. I still have not really worked on that, because my Screen problem ist more interesting ;-)

USB 3.0 ist working, Trackpad is working, Ethernet is working, Bluray drive ist working, Bluetooth seems to work (havent, attached a device yet) Also didn't test firewire yet.

 

I have to make my DSDT working soon. Would be great having everything (except wireless) working :-)

 

I think that the key to have almost working (except wireless), sound and graphic card stuff, is almost all in the DSDT, and in the booter, in order to enable nvidia graphic cards (I think talking with chameleon developers, they don't have any problem to add your card ID in order to get working, because is the same as a 330m/335m).

 

Using .kext, you always have problems with updates, etc... but with a good DSDT, maybe you don't need to include anything is /S/L/E, and should be completely Vanilla, that is the desirable situation.

 

So my advise is: try to do a good DSDT (if you have doubts or questions ask D00d, or FKA, but not posting in their threads, make a new one, and talk with them on private) and talk with chameleon developer to include your ID.

 

You need to do a thread similar like that. You can start one from scratch putting a name like 8540W DSDT. Choose a good location for that, I think that this thread is in a bad location. IMHO is better in OSx86 Project/Notebooks, maybe another laptops with the same or similar processor/chipsets/graphics could benefit both you and them.

 

There you should have all the sections you want to cover through the DSDT (like the thread I told you), like:

- Basic DSDT fixes (to avoid warnings/errors in the compilation, etc...).

- Power management support.

- CPU throttling, and cores support.

- CPU support...

- Mem support...

- Power button -> shutdown. Buttons in general...

- Shutdown/sleep.

- Audio.

- Video?

- Ethernet

- Battery/Energy issues.

- Whatever you need...

 

Always talking about what BIOS you are using and the required settings, and keeping update with the latest changes in the BIOS, and compare with older ones, to have the opportunity to keep older BIOS (like the thread I told you).

 

I am sure that some of people can help you, but you need to spend time, and research and communicate with them, and keep updated and clear the first post is the important part so the people can get updated shortly. If you keep active you'll get it. It's matter of patience. Read the DSDT official documentation, talk with people, and be patience.

 

All that I said is only an opinion and some advices, and of course you can avoid that. I am talking IMHO, without knowledge, but maybe could clarify you a little bit (or not, and you know all of that, and in that case, ignore me).

 

Sorry, for now I can't help you more, as I don't have enough knowledge for that.

 

Good luck and take care!!

Hey thanks for your detailed information.

 

I already started this thread: Link some time ago. But i am really stuck and didn't get an answer yet.

 

I will now ask D00d if he would like to have a look on my problem.

  • 2 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...