Jump to content
Klumper

6990m QE/CI, but no LVDS; need help with personality

12 posts in this topic

Recommended Posts

I have DVI fully working, but LVDS is not recognized. I am almost positive that it is assigned to port 0, and the senseid is correct. I've tried changing the control flags, but any changes and none of the graphics work. This also happens when I change the last two entries.

 

This is what I am currently using:

 

02 00 00 00 00 01 00 00 09 01 00 00 12 04 05 05 <-- LVDS, not recognized

00 04 00 00 00 02 00 00 00 01 00 00 10 00 03 03 <-- HDMI, not working, but it doesn't matter to me

04 00 00 00 14 00 00 00 00 01 00 00 11 02 01 01 <-- DVI, fully working as far as I can tell

00 04 00 00 00 01 00 00 00 01 00 00 21 03 02 02 <-- Not used/not sure what it is

00 04 00 00 00 01 00 00 00 01 00 00 22 05 04 04 <-- Not used/not sure what it is

 

Is there anything I'm doing blatantly wrong?

 

ATOM BIOS Rom:

SubsystemVendorID: 0x1558 SubsystemID: 0x5104

IOBaseAddress: 0x0000

Filename: BR40793.004

BIOS Bootup Message:

Clevo P150HM Blackcomb XT Samsung 2GB

 

PCI ID: 1002:6720

Connector at index 0

Type [@offset 44696]: LVDS (7)

Encoder [@offset 44700]: INTERNAL_UNIPHY (0x1e)

i2cid [@offset 44780]: 0x94, OSX senseid: 0x5

Connector at index 1

Type [@offset 44706]: HDMI-A (11)

Encoder [@offset 44710]: INTERNAL_UNIPHY2 (0x21)

i2cid [@offset 44803]: 0x92, OSX senseid: 0x3

Connector at index 2

Type [@offset 44716]: DVI-I (2)

Encoder [@offset 44720]: INTERNAL_UNIPHY1 (0x20)

i2cid [@offset 44840]: 0x90, OSX senseid: 0x1

Connector at index 3

Type [@offset 44726]: DVI-I (2) <--- Not actually sure what this is, no other DVI port that I know of

Encoder [@offset 44730]: INTERNAL_KLDSCP_DAC1 (0x15)

i2cid [@offset 44840]: 0x90, OSX senseid: 0x1

 

 

 

IOService: (Only parts of LVDS & DVI shown)

 

LVDS (I believe)

| |   |   | +-o ATY,Elodea@0  <class AtiFbStub, id 0x1000002ef, registered,$
| |   |   | | | {
| |   |   | | |   "port-number" = 0
| |   |   | | |   "display-type" = "NONE"
| |   |   | | |   "connector-type" = 2
| |   |   | | |   "ATY,ActiveFlags" = 1
| |   |   | | |   "IOFBDependentIndex" = 0
| |   |   | | |   "IOFBDependentID" = 18446743524284400384
| |   |   | | |   "ATY,ControlFlags" = 256
| |   |   | | |   "AAPL,gray-page" = <01000000>
| |   |   | | |   "device_type" = "display"
| |   |   | | |   "av-signal-type" = 0
| |   |   | | |   "AAPL,iokit-ndrv" = <a06707817fffffff>
| |   |   | | |   "AAPL,gray-value" = <c38c6400>
| |   |   | | |   "display-connect-flags" = <00000000>
| |   |   | | |   "name" = "ATY,Elodea"
| |   |   | | |   "AAPL,boot-display" = <01000000>
| |   |   | | | }

DVI
(I know)
| |   |   | |	  
| |   |   | +-o ATY,Elodea@1  <class AtiFbStub, id 0x1000002f0, registered,$
| |   |   | | | {
| |   |   | | |   "display-type" = "LCD"
| |   |   | | |   "connector-type" = 4
| |   |   | | |   "ATY,ActiveFlags" = 4
| |   |   | | |   "IOFBDependentIndex" = 1
| |   |   | | |   "IOFBDependentID" = 18446743524284400384
| |   |   | | |   "ATY,ControlFlags" = 20
| |   |   | | |   "AAPL,gray-page" = <01000000>
| |   |   | | |   "device_type" = "display"
| |   |   | | |   "av-signal-type" = 2
| |   |   | | |   "AAPL,iokit-ndrv" = <a06707817fffffff>
| |   |   | | |   "AAPL,gray-value" = <c38c6400>
| |   |   | | |   "display-connect-flags" = <00000000>
| |   |   | | |   "name" = "ATY,Elodea"
| |   |   | | |   "port-number" = 2
| |   |   | | | }

post-220395-0-11040000-1332293484_thumb.png

Share this post


Link to post
Share on other sites
Advertisement

I forgot to mention, I had that, but the kext I was editing had them out of order and the ports matched the senseids so I thought maybe they had to match for this one. It is still recognized as being the correct port.

 

Since then, I've been working with Fanwort. LVDS is now recognized, but remains blank. av-signal-type is 0x0 if that means anything about the issue.

I've been messing with the transmitter and encoder, but so far no luck.

Share this post


Link to post
Share on other sites

Just one thing,can you use your laptop screen?

The offset in the first post is taken from Elodea?

The only thing that I know is that with theese offsets(one of theese) you can use hdmi:

0000030	00  08  00  00  04  02  00  00  00  01  04  00  12  04  03  03
0000000	00  04  00  00  04  03  00  00  00  01  00  00  12  04  03  03

Can you upload your Ati6000Controller.kext?

Thanks

Share this post


Link to post
Share on other sites

I'm now using:

 

02 00 00 00 40 00 00 00 29 05 00 00 10 00 00 05
00 08 00 00 04 02 00 00 00 01 04 00 12 04 01 03
04 00 00 00 14 00 00 00 00 01 00 00 11 02 02 01
00 04 00 00 04 03 00 00 00 01 00 00 21 13 03 02

 

DVI/HDMI working QE/CI but tearing occurs on both.

The LVDS does not work. It is recognized as a 17-inch spdisplays_display. Which is correct, but it stays blank.

Using Juncus Framebuffer & AtiPorts = 3

 

Edit:

I've looked at your other post now. I think our best bet is Osmunda. It seems to match quite closely what our cards are. Also where did you get the program that told you what the encoder, etc. was (the one you used before radeon_bios_decode)? Nevermind, I found it on a russian site. Unfortunately, it only confirms that what I had for the LVDS was actually correct so there must be some other issue. Maybe there just isn't any support until new framebuffers come out.

 

Chameleon does not seem to support Osmunda yet though. At least it doesn't appear in the source and I get an error when I set it.

ATI6000Controller.kext.zip

Share this post


Link to post
Share on other sites

I didn't understand one thing:can you use your laptop screen?

Probaly the transmitter value isn't correct,try with '51'

Share this post


Link to post
Share on other sites

Nope.

It is recognised, but stays blank. LVDS is the type of connection the internal screen uses.

Why 51?

 

According to this bios decoder, it should be 10. I'll try it once I boot Lion back up. I've been using Windows the past few days.

 

 

BR40793.004 :

 

Clevo P150HM Blackcomb XT Samsung 2GB

 

Subsystem Vendor ID: 1558

Subsystem ID: 5104

Object Header Structure Size: 237

Connector Object Table Offset: 3e

Router Object Table Offset: 0

Encoder Object Table Offset: b1

Display Path Table Offset: 12

Connector Object Id [14] which is [LVDS]

encoder obj id [0x1e] which is [iNTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false

Connector Object Id [12] which is [HDMI_TYPE_A]

encoder obj id [0x21] which is [iNTERNAL_UNIPHY2 (osx txmit 0x12 [duallink 0x2] enc 0x4)] linkb: false

Connector Object Id [1] which is [DVI_I]

encoder obj id [0x20] which is [iNTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false

Connector Object Id [1] which is [DVI_I]

encoder obj id [0x15] which is [iNTERNAL_KLDSCP_DAC1 (osx txmit 0x00 enc 0x10?)] linkb: false

Share this post


Link to post
Share on other sites

I used moninfo on windows and the LVDS id was 51...also all the combinations with 10 that I have tried didn't work...

Share this post


Link to post
Share on other sites

Hi,

 

I had the same issue with my LVDS. I solved it by installing dual link patch in my DSDT.

But you have to copy the code from GFX0 to PEGP and I had to set the decoder to 01 instead of 00.

 

This should work with all ATI 6XXX cards.

Share this post


Link to post
Share on other sites

Hi,

 

I had the same issue with my LVDS. I solved it by installing dual link patch in my DSDT.

But you have to copy the code from GFX0 to PEGP and I had to set the decoder to 01 instead of 00.

 

This should work with all ATI 6XXX cards.

 

 

hi,packo

can u give me more info about what u said

i wanna have a try

Share this post


Link to post
Share on other sites

hi,packo

can u give me more info about what u said

i wanna have a try

 

Please check your DSDT. search for PEGP and install the Duallink patch there.

should look like:

 

Scope (_SB.PCI0.PEG0.PEGP)

{

Method (_PRW, 0, NotSerialized)

{

Return (GPRW (0x09, 0x04))

}

Method (_DSM, 4, NotSerialized)

{

Store (Package (0x02)

{

"AAPL00,DualLink",

Buffer (0x04)

{

0x01, 0x00, 0x00, 0x00

}

}, Local0)

DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))

Return (Local0)

}

}

 

Then use your edited Kext and add the following to your Bootloader

 

GraphicsEnabler=Yes

AtiPorts=3

Aticonfig=%Your edited Framebuffer%

 

I Used Ipomoea

02000000 40000000 2901 0000 10 01 00 05 <-- LVDS

00080000 00020000 0001 0000 12 04 01 03 <-- HDMI

04000000 14020000 0001 0000 11 02 02 01 <-- DVI (not tested)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Slice
      As I see many novices in the forum ask "How to make my Radeon working? I have bad resolution, no QE/CI...." and so on. They come to the section and have no find an answer here because all Radeons are different and they don't know where else they read about this.
      I want to explain all steps needed for launching the Radeon family of videocards.
       
      Bootloader.
      I will speak about Clover because I maintain this bootloader to know recent hardware and modern OSX. Not sure if you will have the same result with other bootloaders. I am carefully checking the injecting of ATI card and correcting it times to times. I am also accessible for bug reports.
       
      OSX version.
      Older card require older system, newer cards require new system.
      ATIRadeon9000 is possible to launch under Tiger.
      ATIRadeonMobilityX1400 requires 10.5-10.6. See RadeonHD topic.
      As I see RadeonHD3xxx was successful only in 10.5
      For new AMDRadeonHD7xxx there must be 10.8.3+ system.
       
      DeviceID.
      This must be the first question before asking about the card.
      You may know the device-id from Windows->DeviceManger->VideoCard.properties->compatibleIDs
      You may boot into system in safe mode (key -x) and see system profiler
       
      And you may boot into Clover GUI, press F2 and get preboot.log. Find here something like
      2:709 0:000 PCI (00|01:00.00) : 1002 6758 class=030000 2:709 0:000 Found Radeon model=AMD Radeon HD 6670 Series It means my DeviceID=6758 (these are hex numbers)
      Then you must check that Apple's drivers support your DeviceID. If not then add it!
      For example HD7850 has DeviceID=6819. If we look into ATI7000Controller (AMD7000... in new systems) we find 6818 here but no 6819!
       
       
      I show you how to do this with terminal commands. Launch /Application/Utilities/Terminal.app. Type in opened window:
       
      cp /System/Library/Extensions/ATI7000Controller.kext/Contents/Info.plist ~/Desktop So you get a copy of the Info.plist on Desktop. Edit it with TextEdit. Change 68181002 -> 68191002.
      Don't edit this file directly in the system folder! 
      Then copy back by terminal. Don't use finder to copy kexts! They will have wrong permissions in this case.
      sudo cp ~/Desktop/Info.plist /System/Library/Extensions/ATI7000Controller.kext/Contents/ sudo rm -r -v /System/Library/Caches/com.apple.kext.caches/* Second command make sure next reboot the kext will use your edited info.plist.
      The same operation you must do with a kext AMDRadeonAccelerator or ATIRadeonX2000 or other one. Check all candidates if they contain such list of possible IDs and choose closest to you.
       
      FakeID
      Since Clover revision 1971+ you may just inject new DeviceID into DSDT instead of correcting kexts. See instruction here.
       
      GraphicsEnabler or Injector
      OSX needs to know some properties (Model name, Family, etc...) that must be somehow injected at boot time. Yes, also real Macs got DeviceProperties string from firmware.
      Alternatives:
      1. Set InjectATI=Yes in Clover (same as GE=y in Chameleon).
      2. Use custom string made with gfxutil. For whom who knows.
      3. Write _DSM into DSDT. You should know what to write.
      4. Use some kext like ATY_init.kext or Natit.kext. If you are sure that the kext is for your card namely.
      I want to say that all this methods make the same thing. Differencies in their tuning.
      The Clover do this automatically for most known cards at this moment.
       
      Connectors.
      As you may see to start HD5000-7000 some strange names used: Pithecia, Orangutan, Elodea... What are they?
      They are configs for framebuffer. Predefined configs how connectors are solded for cards used in real Macs. Strange but these configs rear coincide with PC card. Usually gurus make advice "choose a framebuffer that most appropriate for your card". The chances 1:10. In most cases you may find a FB name that gives you main monitor working. Or nothing at all.
      Great respect to bcc9 who gives us a method to correct one of config to be exactly for you. See here.
      My retelling for Clover is here
      Success example in the thread in posts 44-52
       
      Radeon Mobility
      I tested Clover's methods with two users having Mobility Radeon HD5470 and HD5650M. We found that full memory and QE/CI will be achieved if we set in Clover's config
      LoadVBios=Yes
      even thou no file with bios is provided. This is the key to make Radeon Mobility working!
      Other problem is bad gradients or artifacts. For this case Clover accept the key
      InjectEDID=Yes
      and sometimes you also need to inject CustomEDID.
      See Clover instructions for details.
       
      And my results.
      Gigabyte Radeon HD6670
      <key>Graphics</key> <dict> <key>GraphicsInjector</key> <true/> <key>InjectEDID</key> <true/> <key>FBName</key> <string>Ipomoea</string> <key>LoadVBios</key> <false/> <key>VideoPorts</key> <integer>3</integer> <key>PatchVBios</key> <true/> </dict> <key>KernelAndKextPatches</key> <dict> <key>KernelCpu</key> <false/> <key>ATIConnectorsController</key> <string>6000</string> <key>ATIConnectorsData</key> <string>000400000403000000010000120401050008000004020000000100001102040310000000100000000001000000000002</string> <key>ATIConnectorsPatch</key> <string>040000000403000000010000100001061000000010000000000100000000000100080000040200000001000012040403</string> VTX Radeon HD5570
      <key>Graphics</key> <dict> <key>PatchVBios</key> <false/> <key>FBName</key> <string>Baboon</string> <key>VideoPorts</key> <string>3</string> <key>GraphicsInjector</key> <string>Yes</string> <key>LoadVBios</key> <string>No</string> </dict> <key>KernelAndKextPatches</key> <dict> <key>Debug</key> <false/> <key>KernelCpu</key> <false/> <key>ATIConnectorsController</key> <string>5000</string> <key>ATIConnectorsData</key> <string>040000001400000000010000010201030008000000020000007100002205020110000000100000000001000000100002</string> <key>AppleRTC</key> <true/> <key>ATIConnectorsPatch</key> <string>040000001400000000010000010001040008000000020000007100002200020510000000100000000001000000000002</string> <key>AsusAICPUPM</key> <false/> <key>KextsToPatch</key> <array> <dict> <key>Name</key> <string>AppleAHCIPort</string> <key>Find</key> <data>RXh0ZXJuYWw=</data> <key>Replace</key> <data>SW50ZXJuYWw=</data> </dict> </array> </dict> See PatchVBios=No
      for this card "yes" leads to black screen. Use with precautions.
       
      A sample for Radeon R7 240
       
      UPDATE for ElCapitan.
      It seems has more problems. My HD6670 is not working in ElCapitan OOB unlike Mavericks.
      I had to set FakeID=0x67401002 as correspond to real iMac12,2 and set this model in SMBIOS section.
      It related to GraphicsPM or GraphicsControl.
      Look these kexts to decide what you can do for your configuration.
       
      HighSierra requires change these kexts by version from Sierra 10.12.6
      for Radeon HD6xxx
      AMDRadeonX3000.kext AMDRadeonX3000GLDriver.bundle IOAccelerator2D.plugin IOAcceleratorFamily2.kext .  for Radeon HD7xxx and up AMDRadeonX4000.kext AMDRadeonX4000GLDriver.bundle IOAccelerator2D.plugin IOAcceleratorFamily2.kext .    Black screen after wake problem resolved by follow method radeon_bios_decode.0.2.zip
      ati-personality.pl.0.15.zip
      ati-personality.pl.0.15a.zip
    • By DerNuntius
      Hi,
       
      Finally I finished the installation of 10.14.6 on my Dell E5440. Everything works just fine, but HDMI will not work. Every time I plug it in, it causes a grey screen on my laptop monitor. Also on boot up. I attached my EFI Folder, maybe someone can help me. I searched a bit and read something about Azul Framebuffer Kext.
       
      Thank you for helping.
      Greedings,
      Hugo
       
       
      CLOVER.zip
×