Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8755 posts in this topic

Recommended Posts

markl18
markl18
Posted
Posted
39 minutes ago, hardcorehenry said:

Some desktop have devices(H_EC,EC0) that require only rename to EC, unless I should already know it(without your DSDT). Try this SSDT-EC-USBX.aml

Rehabman has all those edits automated and if you get those ae_already done they are innocuous all it means that those search and replace commands in the info file could not be executed you could put oc in debug mode and see live all those edits happening as it goes about building it’s tables anyway you could go both ways maybe one way will save some extra waisted cpu time but again. It’s only couple of micro seconds who cares

MacNB
MacNB
Posted
Posted
13 hours ago, startergo said:

Not very well with EC and Clover. It looses LCD output on login. I can VNC to it and it is accelerated, but I cannot output to the LCD with acceleration. I think the biggest issue is that I cannot get the EDID out of it for injection

 

Let's try another way to ask the question.

What are you doing to try and get Arrandale graphics to work ?

I.e. what patches ?

What kexts ?

etc ?

 

As far I can remember Arrandale is not supported at all since the graphics drivers have been removed.

People were taking drivers from Lion and Mountain Lion (I believe to get it to work).

There's a whole Topic on this site.

ajacocks
ajacocks
Posted
Posted
6 hours ago, hardcorehenry said:

@ajacocks I think smbios iMac17,1 would be better choice.

 

Edit:Did you try SSDTTime. It’s possible you only need rename for your “EC”

Yep! That’s what generated my existing .aml files. I ran it on Windows 10, on the machine, itself.

 

Thanks!

- Alex

hardcorehenry
hardcorehenry
Posted
Posted
35 minutes ago, ajacocks said:

Yep! That’s what generated my existing .aml files. I ran it on Windows 10, on the machine, itself.

 

Thanks!

- Alex

I run your DSDT through SSDTTime and I'm a bit surprised it didn't returned SSDT-EC-USBX.aml. Just in case:SSDT-EC-USBX.aml

apianti
apianti
Posted
Posted (edited)
4 hours ago, ajacocks said:

Thanks, I did indeed follow the procedures to the best of my knowledge.

 

1) This is a desktop, a Dell Optiplex 7050

2) There is no “EC” device, in the DSDT.dsl, it’s called “H_EC”

3) I did the editing to rename it, but I’m not sure that I did it correctly, as I get that duplication error that I mentioned

 

Would someone be willing to check over my edits, if I post my DSDT.dsl and my SSDT-EC-USBX.dsl, that I already linked?

 

Here’s the definition of “H_EC” from the DSDT.dsl:

  


Scope (_SB.PCI0.LPCB)
    {
        Device (H_EC)
        {
            Name (_HID, EisaId ("PNP0C09") /* Embedded Controller Device */)  // _HID: Hardware ID
            Name (_UID, One)  // _UID: Unique ID
            Method (_STA, 0, NotSerialized)  // _STA: Status
            {
                ^^^GFX0.CLID = 0x03
                Return (Zero)
            }

 

I uncommented and modified this section, in SSDT-EC-USBX.dsl: 


    External (_SB_.PCI0.LPCB.H_EC, DeviceObj)
    Scope (\_SB.PCI0.LPCB.H_EC)
    {
        Method (_STA, 0, NotSerialized)  // _STA: Status
        {
            If (_OSI ("Darwin"))
            {
                Return (0)
            }
            Else
            {
                Return (0x0F)
            }
        }
    }

Does that look right?

 

Thanks!

- Alex

 

Are you modifying your DSDT? If you are just add that OS specific stuff to your original device. One thing though, your controller is disabled, it's already returning zero status (see the embedded controller _STA edge case, that's yours). Looks like you may have a scope problem in your SSDT as well. And the device should be EC in the SSDT not H_EC. That's why it is giving you the already exists.

 

EDIT: Sorry, looking at the wrong part of SSDT. You did name it EC, remove the H_EC part.

 

EDIT2: Fix your scope in the SSDT.

Edited by apianti
startergo
startergo
Posted
Posted
2 hours ago, MacNB said:

 

Let's try another way to ask the question.

What are you doing to try and get Arrandale graphics to work ?

I.e. what patches ?

What kexts ?

etc ?

 

As far I can remember Arrandale is not supported at all since the graphics drivers have been removed.

People were taking drivers from Lion and Mountain Lion (I believe to get it to work).

There's a whole Topic on this site.

I used this guide:

 

apianti
apianti
Posted
Posted (edited)
6 hours ago, startergo said:

Just before login. I can't see the login screen on the LCD only through VNC. How can I adjust the connectors? If I spoof graphics the screen is connected but then acceleration does not work.

 

There are patches specific to devices. You'd have to look for them, I imagine that they are probably in that topic you used already. I imagine you need to change the connector type for the internal screen, have you tried connecting an external screen?

 

EDIT: The patches will probably need applied to whatever kext you added to get working graphics.

 

EDIT2: You can try using Lilu+WEG but I don't think those will help you because I don't think they support those graphics either but I am not sure...

Edited by apianti
apianti
apianti
Posted
Posted
9 hours ago, Download-Fritz said:

Posts save within 2 to 3 seconds, then the site eats glue for another 30 to 60, just refresh...

 

This works for you? I just end up right back and the editor says it has restored my previous content...

6 hours ago, SavageAUS said:


No I meant True / Enable.
What works for one will not always for another.

 

Oh, well.... S h i t. Maybe he does need it enabled.... :frantics:

9 hours ago, markl18 said:

I get about 12 of those for all kinds of reasons anyway in order to the gpu device to work correctly you have to have those changes to coincide with ssdt-gpu.aml file that has to be present in order for things to happen 

 

What you talking about? The ACPI dump? You should probably have anywhere from five to thirty tables depending on your firmware, chipset, cpu, and feature set of the mobo.

ajacocks
ajacocks
Posted
Posted
12 minutes ago, hardcorehenry said:

I run your DSDT through SSDTTime and I'm a bit surprised it didn't returned SSDT-EC-USBX.aml. Just in case:SSDT-EC-USBX.aml

Yeah, when I ran it through, it just provided SSDT-EC.dsl/aml. I tried that, and the SSDT-EC-USBX.aml that you linked.

 

Neither got us to the graphical screen, unfortunately.

 

- Alex

15 minutes ago, apianti said:

 

This works for you? I just end up right back and the editor says it has restored my previous content...

 

Oh, well.... S h i t. Maybe he does need it enabled.... :frantics:

 

What you talking about? The ACPI dump? You should probably have anywhere from five to thirty tables depending on your firmware, chipset, cpu, and feature set of the mobo. 

 

The ACPI dump just generates DSDT.aml, and SSDT-EC.aml and SSDT-Plug.aml. There are indeed a bunch of tables in the DSDT.dsl, when I look at it.

 

- Alex

apianti
apianti
Posted
Posted (edited)
6 minutes ago, ajacocks said:

Yeah, when I ran it through, it just provided SSDT-EC.dsl/aml. I tried that, and the SSDT-EC-USBX.aml that you linked.

 

Neither got us to the graphical screen, unfortunately.

 

- Alex

 

The ACPI dump just generates DSDT.aml, and SSDT-EC.aml and SSDT-Plug.aml. There are indeed a bunch of tables in the DSDT.dsl, when I look at it.

 

- Alex

 

Look at my previous response before this to you. That should get you working, you have a few problems, you don't need to disable your original controller, it's fine. You only need to add the new fake device but you may have a scope problem.

 

EDIT: Also I was referring to dumping all ACPI tables, not running that auto patcher thingy.

Edited by apianti
startergo
startergo
Posted
Posted
52 minutes ago, apianti said:

 

There are patches specific to devices. You'd have to look for them, I imagine that they are probably in that topic you used already. I imagine you need to change the connector type for the internal screen, have you tried connecting an external screen?

 

EDIT: The patches will probably need applied to whatever kext you added to get working graphics.

 

EDIT2: You can try using Lilu+WEG but I don't think those will help you because I don't think they support those graphics either but I am not sure...

I always use them. Like I said my guts are telling me I need to inject EDID but this bios does not have any or it is so protected that it won't give me anything. It is a Panasonic toughbook.  I tried Linux and Windows. 

apianti
apianti
Posted
Posted (edited)
33 minutes ago, startergo said:

I always use them. Like I said my guts are telling me I need to inject EDID but this bios does not have any or it is so protected that it won't give me anything. It is a Panasonic toughbook.  I tried Linux and Windows. 

 

You mean Lilu+WEG or the connector patches? Did you try an external monitor? I'm pretty sure you need the connectors patch. The EDID is in the monitor itself, if the screen is embedded it may not have an EDID. Thing is it MUST support certain modes by default to be certified as the specific type of display it is, so it would just try to work at the one of these resolutions if the EDID was not available (since it is extended information, not vital). This does not mean it is the native (or best) resolution of the display. I guess macOS could be trying to use a resolution that it doesn't support because the smbios model you chose does support it. How have you tried to extract it? You can always try to build your own from scratch as well with a hex editor and the wikipedia page for EDID.

 

EDIT: When you remote in, can you check and see what it says the resolution is in any way?

 

EDIT2: I'm assuming yes, since you said you could check for acceleration.

Edited by apianti
hardcorehenry
hardcorehenry
Posted
Posted
50 minutes ago, ajacocks said:

Yeah, when I ran it through, it just provided SSDT-EC.dsl/aml. I tried that, and the SSDT-EC-USBX.aml that you linked.

 

Neither got us to the graphical screen, unfortunately.

 

- Alex

 

Did you changed everything in config.plist PlatformInfo>Generic, because iMac18,3 is bad idea.

MacNB
MacNB
Posted
Posted (edited)
2 hours ago, startergo said:

I used this guide:

 

 

Well then, really you should be seeking help on that thread as it is relevant to your issue.

You more likely to meet like-minded people with the experience with Arrandale there that can help.

It's not related to OpenCore.

If most of those folks are using Clover, then they'll get you working.

Then there are ways to migrate to OpenCore.

 

Edited by MacNB
duplicate post...this site has a lot of problems at the moment
apianti
apianti
Posted
Posted (edited)
18 minutes ago, MacNB said:

 

Well then, really you should be seeking help on that thread as it is relevant to your issue.

You more likely to meet like-minded people with the experience with Arrandale there that can help.

It's not related to OpenCore.

If most of those folks are using Clover, then they'll get you working.

Then there are ways to migrate to OpenCore.

 

Agreed. I think that they will be able to help you better. I don't think this is an issue of OC but of your configuration for devices.

18 minutes ago, MacNB said:

duplicate post...this site has a lot of problems at the moment

 

This is not even a post anymore because it was merged but it edited the last one, but says it edited the first. So the quoting doesn't work, I had to copy and paste. I double post constantly and the site is like a good minute per post or edit currently.

 

EDIT: The edit time line is above your text for the post, lol.

Edited by apianti
kiu777
kiu777
Posted
Posted
On 5/8/2020 at 11:34 PM, gorans said:

Hi Kiu,

did You manage to solve this problem? I also have USB flash drives listed as "USB Internal Physical Disk" but they have external icons and I can unmount them.

Sorry but was not able to solve that until now.

lanzaozijun
lanzaozijun
Posted
Posted (edited)

Lenovo-Air13-IWL

Upgrade to macos catalina 10.15.5 (19F96) hdmi external display black screen!
In macos catalina 10.15.4, boot-args enable igfxonln = 1 igfxagdc = 0 method is invalid.
Is there any other solutions for my friends?

 

2020-05-27.png

Edited by lanzaozijun
startergo
startergo
Posted
Posted (edited)
9 hours ago, MacNB said:

 

Well then, really you should be seeking help on that thread as it is relevant to your issue.

You more likely to meet like-minded people with the experience with Arrandale there that can help.

It's not related to OpenCore.

If most of those folks are using Clover, then they'll get you working.

Then there are ways to migrate to OpenCore.

 

I wanted to migrate to OC. I just don't know if it even supports Arrandale. I asked questions in that thread. But nobody answered.

Edited by startergo
SavageAUS
SavageAUS
Posted
Posted

Im trying to boot Arch Linux with OC, OC sees my EFI partition for Arch but it just boots to a black screen.

What config do i need to generate a boot log for OC so i can get my PCIRoot address so i can hopefully add an entry in OC.

If this can be done does anyone have a method for this?

MacNB
MacNB
Posted
Posted
5 hours ago, startergo said:

I wanted to migrate to OC. I just don't know if it even supports Arrandale. I asked questions in that thread. But nobody answered.

 

Support of Arrandale is a macOS issue and nothing to do with the boot loader (Clover, OC, etc).

kecinzer
kecinzer
Posted
Posted

I have weird minor issue with OpenCore (my files). After I wake up screen and login into macOS, I see for a while booting screen and then normal login screen into macOS. It seems to some buffered thing. This occuring every time. Sleep and wake from sleep solves it, so after sleep it work normally.

I'm attaching video of this issue.
https://drive.google.com/open?id=1_8a8YukSJjiXuySTFPdWWgUdoo2S-PPl
May be it can be solved simply by some option in OpenCore or WEG?

MacNB
MacNB
Posted
Posted (edited)
3 hours ago, kecinzer said:

I have weird minor issue with OpenCore (my files). After I wake up screen and login into macOS, I see for a while booting screen and then normal login screen into macOS. It seems to some buffered thing. This occuring every time. Sleep and wake from sleep solves it, so after sleep it work normally.

I'm attaching video of this issue.
https://drive.google.com/open?id=1_8a8YukSJjiXuySTFPdWWgUdoo2S-PPl
May be it can be solved simply by some option in OpenCore or WEG?

 

I get that on my real MacBook Pro.

It's normal with FileVault.

 

Looks like you turned ON File Vault.

Edited by MacNB
spelling
 Share
Go to topic listing
×
×
  • Create New...