Jump to content

Editing custom personalities for ATI Radeon HD[45]xx


bcc9
 Share

775 posts in this topic

Recommended Posts

If the FB has swapped from ATiFramebuffer to ATI5000Controller then why does ATI5000Controller load and ATIFramebuffer doesn't when the kernal is loading card in slot 1, gets to desktop. No changes.

Obviously one of the kexts finds card ID 68C1 in slot one.

 

I will go install xcode and investigate 5000 controller binary.

Link to comment
Share on other sites

If the FB has swapped from ATiFramebuffer to ATI5000Controller then
I only said that the createInfo() routines, which initialize the personality specific tables, have moved from ATIFramebuffer to the individual controller kexts instead. Helps us see which personalities are intended for which controllers :D
Link to comment
Share on other sites

I only said that the createInfo() routines, which initialize the personality specific tables, have moved from ATIFramebuffer to the individual controller kexts instead. Helps us see which personalities are intended for which controllers :D

 

otool -arch i386 -vt ATI5000Controller | c++filt | grep createInfo

DoucInfo::createInfo(unsigned char, PlatformParameters&):

LangurInfo::createInfo(unsigned char, PlatformParameters&):

UakariInfo::createInfo(unsigned char, PlatformParameters&):

ZonalisInfo::createInfo(unsigned char, PlatformParameters&):

AlouattaInfo::createInfo(unsigned char, PlatformParameters&):

HoolockInfo::createInfo(unsigned char, PlatformParameters&):

VervetInfo::createInfo(unsigned char, PlatformParameters&):

BaboonInfo::createInfo(unsigned char, PlatformParameters&):

EulemurInfo::createInfo(unsigned char, PlatformParameters&):

GalagoInfo::createInfo(unsigned char, PlatformParameters&):

ColobusInfo::createInfo(unsigned char, PlatformParameters&):

MangabeyInfo::createInfo(unsigned char, PlatformParameters&):

NomascusInfo::createInfo(unsigned char, PlatformParameters&):

OrangutanInfo::createInfo(unsigned char, PlatformParameters&):

 

Now only 14 :(

 

I only said that the createInfo() routines, which initialize the personality specific tables, have moved from ATIFramebuffer to the individual controller kexts instead. Helps us see which personalities are intended for which controllers :)

 

Personality: Douc
ConnectorInfo count in decimal: 2
Effective address for ConnectorInfo table in hex: 10
Personality: Langur
ConnectorInfo count in decimal: 3
Effective address for ConnectorInfo table in hex: 10
Personality: Uakari
ConnectorInfo count in decimal: 4
Effective address for ConnectorInfo table in hex: 10
Personality: Zonalis
ConnectorInfo count in decimal: 6
Effective address for ConnectorInfo table in hex: 10
Personality: Alouatta
ConnectorInfo count in decimal: 4
Effective address for ConnectorInfo table in hex: 10
Personality: Hoolock
ConnectorInfo count in decimal: 3
Effective address for ConnectorInfo table in hex: 10
Personality: Vervet
ConnectorInfo count in decimal: 4
Effective address for ConnectorInfo table in hex: 10
Personality: Baboon
ConnectorInfo count in decimal: 3
Effective address for ConnectorInfo table in hex: 10
Personality: Eulemur
ConnectorInfo count in decimal: 3
Effective address for ConnectorInfo table in hex: 10
Personality: Galago
ConnectorInfo count in decimal: 2
Effective address for ConnectorInfo table in hex: 10
Personality: Colobus
ConnectorInfo count in decimal: 2
Effective address for ConnectorInfo table in hex: 10
Personality: Mangabey
ConnectorInfo count in decimal: 2
Effective address for ConnectorInfo table in hex: 10
Personality: Nomascus
ConnectorInfo count in decimal: 4
Effective address for ConnectorInfo table in hex: 10
Personality: Orangutan
ConnectorInfo count in decimal: 2
Effective address for ConnectorInfo table in hex: 10

 

So i will have to patch ATI5000Controller in my situation yes? So in the above their is 4 personalities with 3 connectors, My laptop has VGA/HDMI/LVDS.

Personality: Eulemur

Personality: Langur

Personality: Hoolock

Personality: Baboon

 

First before I get into any of this I have to find out how I can even enable graphics without injectors or DSDT's as Lion doesn't have any bootloaders yet?

Link to comment
Share on other sites

Now only 14 :D
Only 14 for that 1 controller, but now 40 total across all controllers, so more than in 10.6.6.

Effective address for ConnectorInfo table in hex: 10
Obviously those addresses are wrong; my perl script needs adjusting for 10.7 apparently.

So i will have to patch ATI5000Controller in my situation yes? So in the above their is 4 personalities with 3 connectors, My laptop has VGA/HDMI/LVDS.
Still can't get 10.7 installed over here so I can't say what is necessary&sufficient at this point.

First before I get into any of this I have to find out how I can even enable graphics without injectors or DSDT's as Lion doesn't have any bootloaders yet?
Netkas has claimed you don't need to inject, but without seeing for myself I don't know if he was just referring to one particular ATI model or what.
Link to comment
Share on other sites

Netkas did claim this however the system picks up i have a card in slot 1 but nothing is effected after this, my ID is in both ATI5000Controller and ATIRadeonX3000 kexts but for some reason my card doesnt do anything. it show's like this in sys profiler.

 

Display: Type: GPU Bus: PCIe PCIe Lane Width: x16 VRAM (Total): 4 MB Vendor: ATI (0x1002) Device ID: 0x68c1 Revision ID: 0x0000 Displays:Display: Resolution: 1366 x 768 Pixel Depth: 32-Bit Color (ARGB8888) Main Display: Yes Mirror: Off Online: Yes

 

Imagine having a 4MB video card and trying to acellerate Lion haha :D

Link to comment
Share on other sites

Imagine having a 4MB video card and trying to acellerate Lion haha :(
I think I used to have a 4MB video card back in 1995 :D

So why not take all your formerly working injection strings and move them to your dsdt.

Link to comment
Share on other sites

I did further test with 10.6.6 kexts & I found bytes which set the ATY,ControlFlags.

 

Based on the success report I read, I found ATY,ControlFlags for LVDS is 0x40 & HDMI is 0x204.

 

LVDS: 02 00 00 00 40 00 00 00 09 01 00 00 02 01 00 01

HDMI: 00 08 00 00 04 02 00 00 00 01 00 00 22 05 05 02

 

I test this with Peregrine framebuffer & now I have output on the internal display for the first time!!! :thumbsup_anim:

 

However, if the external monitor connected to HDMI port, both screen blank/black.

Link to comment
Share on other sites

I think I used to have a 4MB video card back in 1995 :thumbsup_anim:

So why not take all your formerly working injection strings and move them to your dsdt.

 

I remember 1995 days and computers very clearly :) 95 prob was my intel 120mhz pentium it hooned in games, frame rate pausing changing res from 640 to 800. 16mb upped it to 32mb ram :) ultra gaming machine.

 

 

I would use a DSDT but [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] has a dsdt folder and if I place dsdt in there i cannot boot, loading of kernel pauses, Also kext folder if i place kexts, pauses lol

Link to comment
Share on other sites

@Checcco I won't give up, i will use all the information here and figure something out, I can get my card to work using Eulemur in 10.6.6 using 10.7 kexts so there must be a way to get something working in 10.7. Lion would be lovely accelerated.

 

Atlee, bcc9 guide never worked for us... Changing senseid to Nomascus didn't make our 5650m to work... We got our internal display to work with 10.7 kexts, but never recognized. We got our display working but don't know why. Like I said some post earlier, probably we need to tweak something else...You claimed Eulemur is the right fb, but a lot of people (included me) got the same result with uakari, vervet, baboon and langur... Before digging in 10.7 kexts (that may be incomplete) we should continue to try and understand why bcc9 guide ain't working for us on 10.6.6, why we can't have any 0x2 connector-type to work...

 

Luckily this new guy mucha seems to have found how to tweak the other bits of a personality... This like I said could be a solution... :thumbsup_anim:

 

Little tip for everybody:

Analyzing every perosnality I found out that for arch=i386 in 10.6.6 ATIFramebuffer start_offset_for_architecture + offset_for_segment - start_address_for_segment is ALWAYS 0x26338 so you can get the offsite in file this way:

 

offset_in_file = virtual_address + 0x26338

Link to comment
Share on other sites

Atlee, bcc9 guide never worked for us... Changing senseid to Nomascus didn't make our 5650m to work... We got our internal display to work with 10.7 kexts, but never recognized. We got our display working but don't know why. Like I said some post earlier, probably we need to tweak something else...You claimed Eulemur is the right fb, but a lot of people (included me) got the same result with uakari, vervet, baboon and langur... Before digging in 10.7 kexts (that may be incomplete) we should continue to try and understand why bcc9 guide ain't working for us on 10.6.6.

 

Eulemur gave me proper 3D acceleration.

 

Hoolock works but no 3D, Vervet works no 3D, same with Uakari, same with Baboon, and alot of others. But I found only one Personality that gave me 100% 3D and it was Eulemur.

 

@checcco in 10.6.6 click on DVD Player using all other FB's, for me DVD Player gave me error, Frontrow gave me blank screen. Eulemur didn't give me any errors or blank screen.

 

However PCI0 --> POP2@3 same as GFX1 i think. --> VGA0 tells me that VGA port worked and setting a higher resolution then VGA can handle made the Internal screen pop on. This would tell me that the ports are no initiating properly.

 

I dont really wish to go back to 10.6.6 that means reinstall everything lol :thumbsup_anim: I will probably go back to 10.6.6 and we'll figure this out together maybe. only takes me about 1hour or so complete reinstall.

 

@bcc9 empty your inbox please have a new flavour of usb to try.

Link to comment
Share on other sites

k540kkk contacted me via PM and asked me to post this info he extracted from ATI6000Controller.kext from MBP2011

 

Personality: Pithecia 
ConnectorInfo count in decimal: 3 
Effective address for ConnectorInfo table in dec: 159584 (0x26f60) 
Location in dec: 500444 (0x7a2dc) 
0000000: 0004 0000 0403 0000 0001 0000 2103 0204 ............!... 
0000010: 0400 0000 1402 0000 0001 0000 0000 0403 ................ 
0000020: 1000 0000 1000 0000 0001 0000 0000 0001 ................ 

Personality: Bulrushes 
ConnectorInfo count in decimal: 6 
Effective address for ConnectorInfo table in dec: 159648 (0x26fa0) 
Location in dec: 500508 (0x7a31c) 
0000000: 0004 0000 0403 0000 0001 0000 1102 0101 ................ 
0000010: 0004 0000 0403 0000 0001 0000 2103 0202 ............!... 
0000020: 0004 0000 0403 0000 0001 0000 1204 0303 ................ 
0000030: 0004 0000 0403 0000 0001 0000 2205 0404 ............"... 
0000040: 0004 0000 0403 0000 0001 0000 1000 0505 ................ 
0000050: 0004 0000 0403 0000 0001 0000 2001 0606 ............ ... 

Personality: Cattail 
ConnectorInfo count in decimal: 4 
Effective address for ConnectorInfo table in dec: 159744 (0x27000) 
Location in dec: 500604 (0x7a37c) 
0000000: 0200 0000 4000 0000 2905 0000 0000 0005 ....@...)....... 
0000010: 0004 0000 0403 0000 0001 0000 1102 0101 ................ 
0000020: 0004 0000 0001 0000 0001 0000 2103 0202 ............!... 
0000030: 0004 0000 0001 0000 0001 0000 1204 0303 ................ 

Personality: Hydrilla 
ConnectorInfo count in decimal: 5 
Effective address for ConnectorInfo table in dec: 159808 (0x27040) 
Location in dec: 500668 (0x7a3bc) 
0000000: 0200 0000 0001 0000 0901 0000 1204 0303 ................ 
0000010: 0004 0000 0403 0000 0001 0000 1102 0101 ................ 
0000020: 0004 0000 0403 0000 0001 0000 2103 0202 ............!... 
0000030: 0004 0000 0403 0000 0001 0000 2205 0504 ............"... 
0000040: 0004 0000 0403 0000 0001 0000 1000 0405 ................ 

Personality: Duckweed 
ConnectorInfo count in decimal: 4 
Effective address for ConnectorInfo table in dec: 159904 (0x270a0) 
Location in dec: 500764 (0x7a41c) 
0000000: 0004 0000 0403 0000 0001 0000 1204 0401 ................ 
0000010: 0004 0000 0403 0000 0001 0000 2205 0502 ............"... 
0000020: 0008 0000 0402 0000 0001 0000 1102 0304 ................ 
0000030: 0002 0000 0402 0000 0001 0000 0000 0605 ................ 

Personality: Fanwort 
ConnectorInfo count in decimal: 4 
Effective address for ConnectorInfo table in dec: 159968 (0x270e0) 
Location in dec: 500828 (0x7a45c) 
0000000: 0200 0000 4000 0000 2905 0000 0000 0004 ....@...)....... 
0000010: 0004 0000 0403 0000 0001 0000 1102 0101 ................ 
0000020: 0004 0000 0001 0000 0001 0000 2103 0202 ............!... 
0000030: 0004 0000 0001 0000 0001 0000 1204 0303 ................ 

Personality: Elodea 
ConnectorInfo count in decimal: 5 
Effective address for ConnectorInfo table in dec: 160032 (0x27120) 
Location in dec: 500892 (0x7a49c) 
0000000: 0200 0000 0001 0000 0901 0000 1204 0303 ................ 
0000010: 0004 0000 0403 0000 0001 0000 1102 0101 ................ 
0000020: 0004 0000 0403 0000 0001 0000 2103 0202 ............!... 
0000030: 0004 0000 0403 0000 0001 0000 2205 0404 ............"... 
0000040: 0004 0000 0403 0000 0001 0000 1000 0505 ................ 

Personality: Kudzu 
ConnectorInfo count in decimal: 2 
Effective address for ConnectorInfo table in dec: 160128 (0x27180) 
Location in dec: 500988 (0x7a4fc) 
0000000: 0004 0000 0403 0000 0001 0000 1204 0303 ................ 
0000010: 0008 0000 0402 0000 0001 0000 1102 0101 ................ 

Personality: Gibba 
ConnectorInfo count in decimal: 5 
Effective address for ConnectorInfo table in dec: 160160 (0x271a0) 
Location in dec: 501020 (0x7a51c) 
0000000: 0004 0000 0403 0000 0001 0000 1204 0501 ................ 
0000010: 0004 0000 0403 0000 0001 0000 2205 0402 ............"... 
0000020: 0008 0000 0402 0000 0001 0000 1102 0604 ................ 
0000030: 0002 0000 0402 0000 0001 0000 0000 0305 ................ 
0000040: 0400 0000 0402 0000 0001 0000 1102 0103 ................ 

Personality: Lotus 
ConnectorInfo count in decimal: 3 
Effective address for ConnectorInfo table in dec: 160256 (0x27200) 
Location in dec: 501116 (0x7a57c) 
0000000: 0004 0000 0403 0000 0001 0000 1102 0101 ................ 
0000010: 0004 0000 0001 0000 0001 0000 2103 0202 ............!... 
0000020: 0008 0000 0402 0000 0001 0000 2205 0404 ............"... 

Personality: Ipomoea 
ConnectorInfo count in decimal: 3 
Effective address for ConnectorInfo table in dec: 160320 (0x27240) 
Location in dec: 501180 (0x7a5bc) 
0000000: 0004 0000 0403 0000 0001 0000 1204 0105 ................ 
0000010: 0008 0000 0402 0000 0001 0000 1102 0403 ................ 
0000020: 1000 0000 1000 0000 0001 0000 0000 0002 ................

Link to comment
Share on other sites

I did further test with 10.6.6 kexts & I found bytes which set the ATY,ControlFlags.

 

Based on the success report I read, I found ATY,ControlFlags for LVDS is 0x40 & HDMI is 0x204.

 

LVDS: 02 00 00 00 40 00 00 00 09 01 00 00 02 01 00 01

HDMI: 00 08 00 00 04 02 00 00 00 01 00 00 22 05 05 02

 

I test this with Peregrine framebuffer & now I have output on the internal display for the first time!!! :D

 

However, if the external monitor connected to HDMI port, both screen blank/black.

According to my working HDMI audio in Asus EAH 5850, EAH 5770 and MSI Hawk 5770 using Uakari, Vervet, Baboon, Zonalis, Flicker & Hoolock FBs:

The working HDMI for desktop ATI 5xxx cards should be 00 08 00 00 00 02 00 00 00 01 00 00 22 05 05 xx (xx=04 or 05).

 

However, I am NOT sure whether there is big difference between desktop ATI 5xxx cards and laptop ATI 5xxx M series.

Link to comment
Share on other sites

According to my working HDMI audio in Asus EAH 5850, EAH 5770 and MSI Hawk 5770:

all should be 00 08 00 00 00 02 00 00 00 01 00 00 22 05 05 xx (xx=04 or 05).

Please try these for your card.

Thank you but I already tried it. The external display just blank if connected to HDMI port. However, I'm successfully enabled dual-screen with external monitor connected to VGA port. :D

 

Peregrine framebuffer:-

0000000	02 00 00 00 40 00 00 00 09 01 00 00 02 01 00 01		(LVDS)
0000010	10 00 00 00 10 00 00 00 00 01 00 00 00 10 00 06		(VGA)

 

post-125711-1300189352_thumb.jpg

post-125711-1300189393_thumb.jpg

Link to comment
Share on other sites

Hi bcc9,

can you make a tool like your radeondump thats provide usefull information about Encoder & Transmitter routing for each output (like does the Dong's RadeonHD.kext Debug info), such a tools in combination with radeondump info will make every ATI card Working

Link to comment
Share on other sites

Finally, all three connections are working. :wacko:

ATOM BIOS Rom: 
SubsystemVendorID: 0x1028 SubsystemID: 0x02bd
IOBaseAddress: 0x0000
Filename: BR034783.006
BIOS Bootup Message: 
BR034783-006 M92 DDR3 64bit 500e/800m									   

Connector at index 0 type: VGA (1)
Connector's i2cid: 95
Connector at index 1 type: HDMI-A (11)
Connector's i2cid: 91
Connector at index 2 type: LVDS (7)
Connector's i2cid: 90

 

senseid = (i2cid & 0xf) + 1

VGA: (95 And 0xf) + 1 = 6

HDMI: (91 And 0xf) + 1 = 2

LVDS: (90 And 0xf) + 1 = 1

 

Patched connection table (Shrike framebuffer):-

--> 00000000	 02  00  00  00  40  00  00  00  09  01  00  00  12  00  00  01 	(LVDS)
--> 00000010	 10  00  00  00  10  00  00  00  00  01  00  00  00  10  01  06 	(VGA)
--> 00000020	 00  08  00  00  00  02  00  00  00  01  00  00  20  01  02  02 	(HDMI)

post-125711-1300211521_thumb.jpg

post-125711-1300211557_thumb.jpg

 

Thank you bcc9 & mucha for the excellent guides! ;)

Link to comment
Share on other sites

So the quest is pretty much complete, I guess :wacko: Congratulations to all of you!

 

It looks like a black magic to me though. I have no experience with OSX86 at all (although I'm fine with linux) but I'm giving it a shot tomorrow.

I just wish there was a more straightforward guide for newbies on getting OSX work on ATi Mobility - equipped notebooks. (such as dell studio 15 series)

Link to comment
Share on other sites

Hi bcc9,

can you make a tool like your radeondump thats provide usefull information about Encoder & Transmitter routing for each output (like does the Dong's RadeonHD.kext Debug info), such a tools in combination with radeondump info will make every ATI card Working

Such a tool would be very useful.

I get a garbled screen, both internal and external, with Dong's tool in debug mode, which makes getting this info difficult.

Link to comment
Share on other sites

Such a tool would be very useful.

I get a garbled screen, both internal and external, with Dong's tool in debug mode, which makes getting this info difficult.

Me too i was getting grabled screen, RadeonHD.kext never worked for me i was using chameleon with autoresolution before, but to overcome this and after having installed RadeonHD you should wait until you are sure your desktop is fully loaded then:

 

1- press "alt+shift+u" (to select utility folder)

2- press "t" (to select terminal)

3- press "alt+o" (to open the already selected terminal)

4- type "sudo -s" press enter and wait

5- type your password press enter and wait

6- type "dmesg > encoder.txt" and press enter

7- press the powerbutton to reboot with boot flag -s -f Delete radeonHD.kext and type exit to continue the normal boot process

8- Go to your home folder you will find your dumped log in encoder.txt

Link to comment
Share on other sites

Me too i was getting grabled screen, RadeonHD.kext never worked for me i was using chameleon with autoresolution before, but to overcome this and after having installed RadeonHD you should wait until you are sure your desktop is fully loaded then:

 

1- press "alt+shift+u" (to select utility folder)

2- press "t" (to select terminal)

3- press "alt+o" (to open the already selected terminal)

4- type "sudo -s" press enter and wait

5- type your password press enter and wait

6- type "dmesg > encoder.txt" and press enter

7- press the powerbutton to reboot with boot flag -s -f Delete radeonHD.kext and type exit to continue the normal boot process

8- Go to your home folder you will find your dumped log in encoder.txt

Found a simpler solution:

 

Put terminal in dock

Set options to open on logon

Then move patched RadeonHD.kext to /S/L/E

reboot

 

When loaded (typing blind):

sudo bash
<enter your password>
dsemg > Encoder.txt
shutdown -r now

 

Reboot with -s, but unpatched RadeonHD.kext back, etc

 

And an even simpler solution is I found all the info I needed with dsemg without debug actually.

 

I still don't have mine up yet; may be an issue with graphics enabler. I think some of us may have to inject under AGP or PEGP with a dsdt patch, like the Nvidia and Intel laptops do.

Link to comment
Share on other sites

Finally, all three connections are working. :(

ATOM BIOS Rom: 
SubsystemVendorID: 0x1028 SubsystemID: 0x02bd
IOBaseAddress: 0x0000
Filename: BR034783.006
BIOS Bootup Message: 
BR034783-006 M92 DDR3 64bit 500e/800m									   

Connector at index 0 type: VGA (1)
Connector's i2cid: 95
Connector at index 1 type: HDMI-A (11)
Connector's i2cid: 91
Connector at index 2 type: LVDS (7)
Connector's i2cid: 90

 

senseid = (i2cid & 0xf) + 1

VGA: (95 And 0xf) + 1 = 6

HDMI: (91 And 0xf) + 1 = 2

LVDS: (90 And 0xf) + 1 = 1

 

Patched connection table (Shrike framebuffer):-

--> 00000000	 02  00  00  00  40  00  00  00  09  01  00  00  12  00  00  01 	(LVDS)
--> 00000010	 10  00  00  00  10  00  00  00  00  01  00  00  00  10  01  06 	(VGA)
--> 00000020	 00  08  00  00  00  02  00  00  00  01  00  00  20  01  02  02 	(HDMI)

post-125711-1300211521_thumb.jpg

post-125711-1300211557_thumb.jpg

 

Thank you bcc9 & mucha for the excellent guides! :D

Congratulations Kizwan !

Just as I predicted before that the working HDMI should be 00 08 00 00 00 02 00 ........................

no matter it's desktop or laptop ATI HD cards (Connector-type:0x800, ATY-ControlFlag:0x200).

Link to comment
Share on other sites

Congratulations Kizwan !

Just as I predicted before that the working HDMI should be 00 08 00 00 00 02 00 ........................

no matter it's desktop or laptop ATI HD cards (Connector-type:0x800, ATY-ControlFlag:0x200).

Thanks. :(

 

It doesn't work earlier with ATY,ControlFlags 0x200 is because it use the same link as LVDS used (same UNIPHY2). So, it conflicted with each other:-

LVDS: 02 00 00 00 40 00 00 00 09 01 00 00 02 01 00 01 > DIG2>UNIPHY2>DUAL_LINK (A+B )>LVDS

HDMI: 00 08 00 00 04 02 00 00 00 01 00 00 22 05 05 02 > DIG6>UNIPHY2>LINK_B>HDMI

 

LVDS was using UNIPHY2>LINK_B and HDMI was using the same link which cause the interference.

 

With correct link, it works:-

02 00 00 00 40 00 00 00 09 01 00 00 12 00 00 01 (LVDS)

10 00 00 00 10 00 00 00 00 01 00 00 00 10 01 06 (VGA)

00 08 00 00 00 02 00 00 00 01 00 00 20 01 02 02 (HDMI)

Link to comment
Share on other sites

Hi bcc9,

can you make a tool like your radeondump thats provide usefull information about Encoder & Transmitter routing for each output (like does the Dong's RadeonHD.kext Debug info), such a tools in combination with radeondump info will make every ATI card Working

Hey, congrats for figuring out more about the hotplugid, transmitter, encoder, controlflags. Way cool!

 

I'll have to see whether those additional values can be derived from the atom bios (I think it'd be a lot cleaner to get them that way rather than probing the hardware if possible).

I've actually never used Dong's kext before (never knew about it before rolling my own dump code).

 

When loaded (typing blind):

Boot without the framebuffer kext, configure system preferences->sharing->remote login, then whenever your system boots to a black/garbled/corrupt screen you can ssh login to it once it's fully booted and type whatever commands you want. No flying blind required.

Link to comment
Share on other sites

Finally, all three connections are working. :unsure:

 

Patched connection table (Shrike framebuffer):-

--> 00000000	 02  00  00  00  40  00  00  00  09  01  00  00  12  00  00  01 	(LVDS)
--> 00000010	 10  00  00  00  10  00  00  00  00  01  00  00  00  10  01  06 	(VGA)
--> 00000020	 00  08  00  00  00  02  00  00  00  01  00  00  20  01  02  02 	(HDMI)

post-125711-1300211521_thumb.jpg

post-125711-1300211557_thumb.jpg

 

Thank you bcc9 & mucha for the excellent guides! :thumbsup_anim:

 

Hi Kizwan is every mobility cards sense ID's different? Would this method be something I could do?

Link to comment
Share on other sites

 Share

×
×
  • Create New...