InsanelyMac Geek
What device ID ?
InsanelyMac Legend
Graphics Card's device ID, for example mine is 0x95531002. The people has started to report feedback using Lion's kext and seems that detect well the hdmi/dvi/vga ports, at least in mobility series. The only problem at the moment still being LVDS.
It'll be interesting if desktop users try the Lion's Framebuffer to check if the same happens and start to work with it.
InsanelyMac Protégé
What device ID ?
InsanelyMac Geek
68c1 and yes, it's missing in kabyl's ati.c
I've asked in some thread to add it but no one did...
InsanelyMac Protégé
It's so easy to do. Download Kabyl's branche, open the ati.c file and add your device ID. To compile it just type in the terminal "make clean" and "make embedtheme", check that you are in kabyl's folder.
InsanelyMac Sage
Sign In
Create Account
32
typedef struct {
UInt32 connectorType; //0
UInt32 supportedConnections; //4
UInt32 features; //8
UInt16 transmitterData; //C
UInt8 hotPlugId; //E
UInt8 ddcInfo; //F
} ConnectorInfo;
//connectorType
const char *CONNECTOR_TYPE_STRINGS[19] = {
"UNKNOWN",
"BUILT IN",
"DVI",
"ADC",
"VGA",
"MINI VGA",
"COMPOSITE",
"S VIDEO",
"AV TV JACK",
"DVI LOWER",
"DISPLAY PORT",
"HDMI",
"MINI DVI",
"DISPLAY PORT LOWER",
"MINI DISPLAY PORT",
};
//supportedConnections
const char *CONNECTION_STRINGS[11] = {
"NONE", "TV", "TMDS A", "LVTM A", "DAC A", "DAC B", "LVDS", "HDTV", "DP1", "DP2"
};
//features
enum {
kConnectorInternal = 1 << 0,
kConnectorRGBOnYUV = 1 << 2,
kConnectorBackLight = 1 << 3,
kConnectorInverted = 1 << 4,
kConnectorClamshell = 1 << 5,
kConnectorRGBOnMUX = 1 << 6,
kConnectorDACAutoCalibration = 1 << 7,
kConnectorUseHdcp = 1 << 8,
};
//transmitterData, hotPlugId and ddcInfo are the same as OP described in Post 1.
InsanelyMac Protégé
Before the ATIFramebuffer patch, all 4 kexts loaded (including ATI4600Controller) & no monitor is detected. Checked via VNC no QE/CI.
After the ATIFramebuffer patch, all 4 kexts loaded & monitors are detected but no output on the monitors. Checked via VNC, QE/CI working.
BTW, are you able to get your Radeon HD 4550 working? I believe on desktop it is much easier to get monitor to work with ATIFramebuffer patch.
InsanelyMac Protégé
Not even on external monitor (but didn't expect it for Nomascus).
InsanelyMac Legend
If you have problem with Kabyl's boot file, use the official Chameleon 2 RC5 boot file. I use combination of GraphicsEnabler=Yes & ATI injection in DSDT:-btw, i found out the hard way that kabyl's loader with optional AtiConfig switch behaves differently when the switch is on. (i tried AtiConfig=Peregrine and got a very different result from what usually happens without the switch - the default for my card is Peregrine)
Method (_DSM, 4, NotSerialized) { Store (Package (0x1E) { "@0,compatible", Buffer (0x0E) { "ATY,Vervet" }, "@0,device_type", Buffer (0x08) { "display" }, "@0,display-connect-flags", Buffer (0x04) { 0x04, 0x00, 0x00, 0x00 }, "@0,display-dual-link", Buffer (0x04) { 0x02, 0x00, 0x00, 0x00 }, "@0,VRAM,memsize", Buffer (0x04) { 0x00, 0x00, 0x00, 0x20 }, "@0,display-type", Buffer (0x04) { "LCD" }, "@0,name", Buffer (0x0E) { "ATY,Vervet" }, "@1,compatible", Buffer (0x0E) { "ATY,Vervet" }, "@1,device_type", Buffer (0x08) { "display" }, "@1,VRAM,memsize", Buffer (0x08) { 0x00, 0x00, 0x00, 0x20 }, "@1,name", Buffer (0x0E) { "ATY,Vervet" }, "device_type", Buffer (0x14) { "ATY,VervetParent" }, "hda-gfx", Buffer (0x0A) { "onboard-1" }, "VRAM,totalsize", Buffer (0x04) { 0x00, 0x00, 0x00, 0x20 }, "model", Buffer (0x23) { "ATI Mobility Radeon HD 4500 Series" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) }It's involved a bit of work because whenever you want to try another framebuffer, you'll need to edit your DSDT, change the framebuffer & compiled. However, this at least get the job done.
InsanelyMac Legend
Yes, tremendously.Hope it helps.
These we can probably tweek once we have output//features
enum {
kConnectorInternal = 1 << 0,
kConnectorRGBOnYUV = 1 << 2,
kConnectorBackLight = 1 << 3,
kConnectorInverted = 1 << 4,
kConnectorClamshell = 1 << 5,
kConnectorRGBOnMUX = 1 << 6,
kConnectorDACAutoCalibration = 1 << 7,
kConnectorUseHdcp = 1 << 8,
byte link_i2cid; /* Bits 0-3: i2cid
Bits 4-7: link transmitter link */
byte dac_digidx; /* Bits 0-3: link encoder number
Bits 4-7: link dac number */
byte hotplugid;
byte senseid; /* Sense line is bits 0-3
Use hw i2c flag is bit 4 */
/* i2cid = (senseid & 0xf-1)+0x90 */
/* senseid = (i2cid & 0xf) +1*/
InsanelyMac Protégé
BTW, I got my external monitor working with QE/CI enabled with Lion's ATI4600Controller.kext, ATIFramebuffer.kext & ATISupport.kext.
InsanelyMac Legend
You can get the Lion kexts from over here.would you please share the lion kexts by PM? 4500, 4600, framebuffer, support and x2000 kexts, if you have them. thanks in advance!
@everybody else: sorry for the spam! couldnt send PM to above user.
InsanelyMac Legend
First I'd like to point out that, no, I'm generally *not* guessing here. Most of the information in post #1 is grounded in actual observed use of the data in the tables by the code.One issue is there is tremendous variation in how mobility cards are connected to displays.
I am wondering if we could get more info by examining the atom bios, as we are really guessing how to set bits 2-14 right now.
I'll be pissed if all of this is obsolete in 10.7Seems that Lion's FB works different and auto detects the ports
Actually I'll be fine if the driver is smarter&simpler about handling hardware automatically.Figured out some more information on this... On the audio side (AppleHDA) there is code that checks against the connector-types and only allows HDMI & DP connector-types to connect between the audio&video drivers for HDMI/DP audio. (And thus the connector-type requirement is the same for Nvidia cards). Looks like the audio code also requires magic av-signal-type values, where 8=HDMI.There is code in ATISupport that explicitly checks the connector type against 0x800 before considering that the display is HDMI. (Failing that it also checks for an hdmi dongle to decide whether the port is usable as hdmi.
In practice I had working video with my hdmi display with the wrong connector type, but I couldn't get HDMI audio to hotplug without revising the ConnectorInfo entry to actually be for an HDMI port.
I haven't actually tried all combinations however.
Also I see no such test for displayport, so I suspect audio could work over displayport without the connector type mapping properly.
I see you located the problem function over in kabyl's thread:I didn't get the error ever. Sometimes stoped at first line. Are you booting on Verbose?
ATI card POSTed, reading VBIOS from legacy space Memory allocation error! Addr=0xdeadbeef, Size 0x0 File=ati.c, Line=668 This is anon recoverable error! System HALTED!The line changes in some boot's versions, but always are part of the same script.
InsanelyMac Protégé
You can get the Lion kexts from over here.
PM is disabled because I'm supposed to be retired from all of this. I come back here when I heard apple is releasing new macbook pro with ati graphic card.
InsanelyMac Legend
Connectortype does not index into the above array, even when first mapped from a type to a bit number. Note also that ATIFramebuffer::updateConnectorInfo() defines a funny mapping for connector types.//connectorType
const char *CONNECTOR_TYPE_STRINGS[19] = {
"UNKNOWN",
"BUILT IN",
"DVI",
"ADC",
"VGA",
"MINI VGA",
"COMPOSITE",
"S VIDEO",
"AV TV JACK",
"DVI LOWER",
"DISPLAY PORT",
"HDMI",
"MINI DVI",
"DISPLAY PORT LOWER",
"MINI DISPLAY PORT",
};
This field isn't an enumerated type it's a bitfield (multiple bits can and are set), but yes, that basically matches what I had://features
enum {
kConnectorInternal = 1 << 0,
kConnectorRGBOnYUV = 1 << 2,
kConnectorBackLight = 1 << 3,
kConnectorInverted = 1 << 4,
kConnectorClamshell = 1 << 5,
kConnectorRGBOnMUX = 1 << 6,
kConnectorDACAutoCalibration = 1 << 7,
kConnectorUseHdcp = 1 << 8,
};
/* Features byte 0 */ #define FEATURE_USE_INTERNAL 0x1 #define FEATURE_USE_RGB_ON_YUV 0x4 #define FEATURE_USE_BACKLIGHT 0x8 #define FEATURE_BACKLIGHT_INVERTED 0x10 #define FEATURE_USE_CLAMSHELL 0x20 /* Features byte 1 */ #define FEATURE_USE_HDCP 0x1Thanks for sharing.
InsanelyMac Legend
So in byte stream for use internal only this should be 01 00 00 00?Connectortype does not index into the above array, even when first mapped from a type to a bit number. Note also that ATIFramebuffer::updateConnectorInfo() defines a funny mapping for connector types.
This field isn't an enumerated type it's a bitfield (multiple bits can and are set), but yes, that basically matches what I had:/* Features byte 0 */ #define FEATURE_USE_INTERNAL 0x1 #define FEATURE_USE_RGB_ON_YUV 0x4 #define FEATURE_USE_BACKLIGHT 0x8 #define FEATURE_BACKLIGHT_INVERTED 0x10 #define FEATURE_USE_CLAMSHELL 0x20 /* Features byte 1 */ #define FEATURE_USE_HDCP 0x1Thanks for sharing.
InsanelyMac Geek
InsanelyMac Legend
Right, as represented as a byte stream.So in binary for use internal only this should be 01 00 00 00?
Those all look like the LVDS entries. So yes nomascus has use_internal, use_backlight, use_hdcp set. Notice all these LVDS connectors have use_internal set. I haven't tested these (I don't have an actual LVDS connection on any ATI cards so I probably can't really test use_internal at allWormy is 29 00 00 00
Iago, Hypoprion, is 09 00 00 00
Nomascus is 09 01 00 00
InsanelyMac Legend
Thanks that helpsRight, as represented as a byte stream.
Those all look like the LVDS entries. So yes nomascus has use_internal, use_backlight, use_hdcp set. Notice all these LVDS connectors have use_internal set. I haven't tested these (I don't have an actual LVDS connection on any ATI cards so I probably can't really test use_internal at all
byte link_i2cid; /* Bits 0-3: i2cid Bits 4-7: link transmitter link */ byte dac_digidx; /* Bits 0-3: link encoder number Bits 4-7: link dac number */ byte hotplugid; byte senseid; /* Sense line is bits 0-3 Use hw i2c flag is bit 4 */ /* i2cid = (senseid & 0xf-1)+0x90 */ /* senseid = (i2cid & 0xf) +1*/For instance, in earlier post you told me to use senseid 01
bash-3.2# kextload ./RadeonPCI.kext/ bash-3.2# ./RadeonDump -i Found a device of class RadeonPCI: IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/AGP@1/IOPCI2PCIBridge/VID@0/RadeonPCI it matched on name "display" Detected unknown Card (device id: 0x9552) It's not in known card list, treat as card with device id: 0x9511 Detect EDID may fail for this card. Start I2C dump ATOM BIOS detected ATOM BIOS Rom: SubsystemVendorID: 0x1028 SubsystemID: 0x02aa IOBaseAddress: 0xde00 Filename: BR31245C.001 BIOS Bootup Message: Dell_Roberts_M92S_GDDR3 M92 GDDR3 64bit 450e/600m object id 0005 01 src object id 2115 21 record type 1 rhdAtomParseI2CRecord: I2C Record: HW_Line 9 EngineID: 0 I2CAddr: 0 ddc_line from ATOMBIOS: 0x0 record type 4 object id 000e 01 src object id 2121 33 record type 1 rhdAtomParseI2CRecord: I2C Record: GPIO_ID 9 EngineID: 0 I2CAddr: 0 ddc_line from ATOMBIOS: 0x0 record type 4I am guessing:
byte link_i2cid; /* Bits 0-3: i2cid [?use I2CAddr = 0] Bits 4-7: link transmitter link */ [?use HW_Line = 9] byte dac_digidx; /* Bits 0-3: link encoder number [?use 0] Bits 4-7: link dac number */ [?use ddc_line = 0] byte hotplugid; [any clues here?]In byte stream:
We have a reasonable size group in the Mobility HD 4330 Thread, some are testing, others are now following with interest and have PM they will test. Some are posting results in that thread, some here. And there are a number of other mobility threads I don't follow.I don't have any ATI mobility hardware to test with so obviously someone else needs to drive any interests in that area.
InsanelyMac Geek
Hi, bcc9First I'd like to point out that, no, I'm generally *not* guessing here. Most of the information in post #1 is grounded in actual observed use of the data in the tables by the code.
Yes, when I did first find that modifying the senseid was necessary&sufficient to turn a non-working ConnectorInfo entry into a working one for my situation, it was thru some directed trial and error.
But I did follow up with a program and method to actually compute the value directly from one's own ATOM BIOS.
I believe I have about 60% of those 16 bytes mapped out actually, it's just that I've only effectively tested modifying the ConnectorType & senseid fields.
I don't have any ATI mobility hardware to test with so obviously someone else needs to drive any interests in that area.
I'll be pissed if all of this is obsolete in 10.7
Figured out some more information on this... On the audio side (AppleHDA) there is code that checks against the connector-types and only allows HDMI & DP connector-types to connect between the audio&video drivers for HDMI/DP audio. (And thus the connector-type requirement is the same for Nvidia cards). Looks like the audio code also requires magic av-signal-type values, where 8=HDMI.
I was able to finally get my nvidia 9400m to show HDMI audio by forcing av-signal-type=8. (Audio somehow still doesn't work but that's off topic).
I see you located the problem function over in kabyl's thread:
http://www.insanelym...p...t&p=1649581
If get_romrevision_val() was instead changed to protect against bad return values from that strlen() call, (and returning false when the strlen() result is bad), then this would avoid the crash without making that routine a no-op.
