Jump to content

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

6990m QE/CI ATI Framebuffer

  • Please log in to reply
11 replies to this topic

#1
Klumper

Klumper

    InsanelyMac Protégé

  • Members
  • Pip
  • 9 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
	| |   |   | | | }

Attached Files



#2
Toris

Toris

    InsanelyMac Protégé

  • Members
  • Pip
  • 24 posts
Maybe because your card has got 4 connectors and LVDS is set on pin 05?
Try to change with 04

#3
Klumper

Klumper

    InsanelyMac Protégé

  • Members
  • Pip
  • 9 posts
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.

#4
Toris

Toris

    InsanelyMac Protégé

  • Members
  • Pip
  • 24 posts
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

#5
Klumper

Klumper

    InsanelyMac Protégé

  • Members
  • Pip
  • 9 posts
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.

Attached Files



#6
Toris

Toris

    InsanelyMac Protégé

  • Members
  • Pip
  • 24 posts
I didn't understand one thing:can you use your laptop screen?
Probaly the transmitter value isn't correct,try with '51'

#7
Klumper

Klumper

    InsanelyMac Protégé

  • Members
  • Pip
  • 9 posts
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

#8
Toris

Toris

    InsanelyMac Protégé

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

#9
Packo1980

Packo1980

    InsanelyMac Protégé

  • Members
  • Pip
  • 2 posts
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.

#10
Klumper

Klumper

    InsanelyMac Protégé

  • Members
  • Pip
  • 9 posts
Thanks, Packo. I'll try that and report back on how it went.

#11
macsane123

macsane123

    InsanelyMac Protégé

  • Members
  • Pip
  • 13 posts

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

#12
Packo1980

Packo1980

    InsanelyMac Protégé

  • Members
  • Pip
  • 2 posts

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)






Also tagged with one or more of these keywords: 6990m, QE/CI, ATI, Framebuffer


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy