Jump to content

Mobility Radeon HD 4650:Full Resolution with QE & CI working on Internal LVDS screen


mucha
 Share

696 posts in this topic

Recommended Posts

RadeonHD.kext package come with RadeonDump file.You just need to put RadeonDump in, for example, home folder or desktop. Open terminal, change directory (cd) to the directory where RadeonDump is located & execute RadeonDump like this:-

(if RadeonDump is located in home folder)

cd /Users/dajerm119
./RadeonDump > encoder.txt

Link to comment
Share on other sites

hi dajerm119, according to this post it seems that your laptop uses my same card: 512mb ati mobile radeon hd4330 with only one internal lvds connector used by lcd display and only one external VGA port (no hdmi port at all).

If this is true, maybe will be helpful to jump directly to the ATIFramebuffer patch for 10.6.7.

Here you can find all the experiments I did until I reached a good solution to have both internal and external ports working (last case posted).

Remember you must use this bootloader (install any chamaleon 2 version before, then replace the boot file in your boot hd!!!), originally posted by crazybirdy if i'm not wrong.

Remember also to insert our device id in the other ati kext if not present and to set right permissions after any kext modifying:

 

sudo chmod -R 755 /System/Library/Extensions/

 

chown -R root:wheel /System/Library/Extensions/

touch /System/Library/Extensions

 

I'm now on lion and it was pretty simple to get it fully working on it. So I cannot help you better than this way for SL. Hope you'll figure out!

Let the community know! Good luck

 

[edit] I was forgetting I used graphicsenabler yes ;)

[edit 2] ...and at the end remove radeonhd kext when you're ready to try to avoid crash!

Edited by c0ke
Link to comment
Share on other sites

@kizwan: As far as I can tell, and with kextstat, it is loaded. I don't know why it keeps doing that. I think I am going to try and peruse this with the info provided by cOke. Thank you for your time and effort. I will let you know how this turns out.

Link to comment
Share on other sites

I must say I remember I had same issues getting RadeonDump detailed infos.

Maybe because of a different radeonHD version.

Thanks to the help by kizwan, wmarsh, crazybirdy, mucha, bcc9 and other people involved with similar connector configuration, I was able to try and try different personalities combos until I reached a good output without getting proper infos from my dump...

Anyway I had some little issue within the internal display output, showing I think some less color. I saw it on gradients being not perfectly linear. Maybe with the right data you'll obtain a better configuration...

Link to comment
Share on other sites

Haha, I've been trying for 2 whole weeks to get some kind of output on my internal display!

None of the information that is around makes any sense, I read the thing over and over I have my info but apparently its wrong as when I edit a personality it comes up with nothing...

 

Just from messing around my VGA works when the personality has a senseID of 03 in there which doesnt match anything in any of the info that I have gotten from my VBIOS. So I'm left to just randomly try different things... I'm not gonna give up but it seems like this is going to go on forever. I've tried pretty much every configuration I can think of so there must be something wrong going on here. Maybe the info that is in the first post doesn't work for all GPU's and that they vary because nothing works for me!!!!

Link to comment
Share on other sites

Well at least im not the only one. I was really beating myself up over that. I just couldn't figure out why i couldnt get the right info. I am sorry to hear about the trouble, but like i said at least im not the only one. And yes thank you kizwan, wmarsh, crazybirdy, mucha, bcc9,cOke and anyone else who has helped people such as myself.

Link to comment
Share on other sites

Man I'm lost, I can't seem to figure out how to find the right binary to edit. I know the file is in ATIFramebuffer.kext>contents>Macos file. I open with Hexedit but can't figure out exactly what I'm looking for. I typed in LVDS in the find and replace box it finds it but nothing called VGA. I also opened in another hex editor (0xed) i think. Same thing. I know I'm a total noob, but I googled and googled and can't seem to find anything all that useful. Thank you.

Link to comment
Share on other sites

Got to bcc9's thread:-

http://www.insanelymac.com/forum/index.php?showtopic=249642

 

download ati-personality.pl.0.8.zip. Extract the zip file & you'll get ati-personality.pl.

 

Open terminal, change directory to the directory where ati-personality.pl is located & run it like this:-

./ati-personality.pl > Personality_x86.txt
./ati-personality.pl -x > Personality_x64.txt

 

Both file contain personality for 32-bit & 64-bit support:-

32-bit: Personality_x86.txt

64-bit: Personality_x64.txt

 

For example, if you're going to use Shrike personality, just open the Personality_xXX.txt file & look for Shrike:-

Personality: Shrike
ConnectorInfo count in decimal: 3
Disk offset in decimal 225944
0000000    02  00  00  00  40  00  00  00  09  01  00  00  02  01  00  03
0000010    02  00  00  00  00  01  00  00  09  01  00  00  20  01  02  02
0000020    00  04  00  00  04  03  00  00  00  01  00  00  10  00  01  01

convert the connector info to one-line form:-

020000004000000009010000020100030200000000010000090100002001020200040000040300000001000010000101

copy the above connector info & search it in ATIFramebuffer file. This is the line you need to edit, replaced it with your own connector info.

Link to comment
Share on other sites

I've been messing around with my setup and I've got my VGA fully supported :)

However still nothing on the LVDS, sometimes I'll get the backlight on but I never get anything.

My senseID is 07, Transmitter is 10, my Encoder is 0 so this should be the info

020000-400000-09-01-0000-10-00-00-07

I've tried the above with different encoders and stuff but still nothing, my VGA still works O.o

Anyone know what's going on?

Link to comment
Share on other sites

Got to bcc9's thread:-

http://www.insanelym...howtopic=249642

 

download ati-personality.pl.0.8.zip. Extract the zip file & you'll get ati-personality.pl.

 

Open terminal, change directory to the directory where ati-personality.pl is located & run it like this:-

./ati-personality.pl > Personality_x86.txt
./ati-personality.pl -x > Personality_x64.txt

 

Both file contain personality for 32-bit & 64-bit support:-

32-bit: Personality_x86.txt

64-bit: Personality_x64.txt

 

For example, if you're going to use Shrike personality, just open the Personality_xXX.txt file & look for Shrike:-

Personality: Shrike
ConnectorInfo count in decimal: 3
Disk offset in decimal 225944
0000000	02  00  00  00  40  00  00  00  09  01  00  00  02  01  00  03
0000010	02  00  00  00  00  01  00  00  09  01  00  00  20  01  02  02
0000020	00  04  00  00  04  03  00  00  00  01  00  00  10  00  01  01

convert the connector info to one-line form:-

020000004000000009010000020100030200000000010000090100002001020200040000040300000001000010000101

copy the above connector info & search it in ATIFramebuffer file. This is the line you need to edit, replaced it with your own connector info.

 

 

When i do this both .txt files come out blank. I will keep trying but i think something else is going on. Maybe my system is corrupt? everything seems fine but i don't understand why this isnt working if it works for others.

Link to comment
Share on other sites

I know that our card needs Peregrine personality, so according to the link I provided to the collection and to the bootloader we're going to let the system use Peregrine for mobility hd4330 card.

Said that, i provided the offset to search with the hex editor (eg. mine 0x00010F60 and 0x00037278) for both 64bit and 32bit modes.

 

For example open ATIFramebuffer with 0xED, then search for "00010F60" offset in the up-right "go to offset" field.

It will highlight the first cipher of a couple. Starting from that you should replace 16 couples of cipher with the new ones for the LVDS connector, and then the next 16 for VGA.

And then again for offset "00037278" 32bit mode.

Be careful doing everything, and keep always an original backup version of every modified file.,,,

Link to comment
Share on other sites

I know that our card needs Peregrine personality, so according to the link I provided to the collection and to the bootloader we're going to let the system use Peregrine for mobility hd4330 card.

Said that, i provided the offset to search with the hex editor (eg. mine 0x00010F60 and 0x00037278) for both 64bit and 32bit modes.

 

For example open ATIFramebuffer with 0xED, then search for "00010F60" offset in the up-right "go to offset" field.

It will highlight the first cipher of a couple. Starting from that you should replace 16 couples of cipher with the new ones for the LVDS connector, and then the next 16 for VGA.

And then again for offset "00037278" 32bit mode.

Be careful doing everything, and keep always an original backup version of every modified file.,,,

 

Well that's the problem, I did this and OxED doesn't find either offset. Even searching manually I cannot find them. That is why I tried following those other directions as well. Maybe I will try redownloading the ATIFramebuffer.kext and search that one. Thank you.

 

 

You need to have XCode installed as ther Perl script uses otool which is part of XCode.

XCode is free in the App Store, it's a fairly big download but thats what you need!

 

Well I do have Xcode installed. The Perl script should call otool on its own correct? As in there is no need for me to open otool first.

Link to comment
Share on other sites

Ok so I downloaded a different ATIFramebuffer.kext file, installed, repaired permissions the rebooted. I tried searching of the offsets in OxED with no luck once again. I also went ahead and ran the ati-personality.pl with the new ATIFramebuffer installed and actually got the results this time. This does lead me to believe that cOke is more than likely correct in the fact that with this card we may need a different version of radeondump to accuire the correct info. I may try and find a different version and see if I can get the right dump. However I'm still no closer to QE/CI. Why can't I find the offsets? I put them in at the "go to offset" box in OxED and hit enter and it takes me to the closest on to it but the one I need is not there.

 

EDIT: I wonder if it's the version of RadeonHD or of radeondump. Maybe I'll try and get different versions of both.

Link to comment
Share on other sites

 Share

×
×
  • Create New...