Jump to content

ATI Mobility RADEON HD 2600 HELP

andrean

By andrean,
in ATi

 Share
100 posts in this topic

Recommended Posts

Ichijoe
Ichijoe
Posted
Posted

Umm if you haven't trolled the Board enough yet to find the "Answer" that you are looking for. then...

You're still outaluck along with the rest of us.

It would seem that that the Mobility uses some non-compatible Framebuffer or connector (i.e. LVDS)

Because of this, it IS HIGHLY UNLIKELY that such Cards will ever be supported!!

hackmymac
hackmymac
Posted
Posted

Ichijoe, thats not totally correct.

 

I am currently working on this matter. I have had my 2600 Mobile work yesterday, and I'm currently working through a solution that I'm writing down, to share with others. I get back to you when I have more.

SunLizard
SunLizard
Posted
Posted

andrean,

 

There is no way to hope you if you don't give any information about your system.

 

For all we know you're having problems under Ubuntu....

 

Please list OSX version, what you're specs are, what you've done, what you're doing next, and what you've seen. No one can help you if you don't give us a baseline.

 

S_L

hackmymac
hackmymac
Posted
Posted

OK............

 

Here it is so far.

 

I've installed the latest Natit pkg and have a working display on an external screen. I'm working on an internal screen fix. this was loaded on Vanilla install, leo 10.5.7.

 

I have other issues as well, i.e. no working keypad, track pad or battery life display.

 

It was the simplest way atm.

 

UPDATE......

 

I have it running in logic after installing the 2600 pro pkg. Its a start I think. 1024x768 is the only res

 

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

 

I used the AGP drivers.

 

When i know more I'll post it

verma
verma
Posted
Posted
 I've installed the latest Natit pkg and have a working display on an external screen. 
Did you get QE/CI working on external screen?

 

 

 I can't get QE/CI on external display with this drivers http://www.insanelymac.com/forum/index.php?showtopic=107526 . Tried Kalyway 10.5.2, Ideneb 10.5.6 and 10.5.7. I have black or garbage screen on both displays. Laptop Gateway m-6862 with Mobility HD 2600.

 

  Maybe we can get mobility HD working this year if Apple will update macbook pro with Mobility 5000 series http://www.tomshardware.co.uk/forum/page-264649_10_0.html. At least we can hope :rolleyes:

hackmymac
hackmymac
Posted
Posted
Did you get QE/CI working on external screen?

 

 

 I can't get QE/CI on external display with this drivers http://www.insanelymac.com/forum/index.php?showtopic=107526 . Tried Kalyway 10.5.2, Ideneb 10.5.6 and 10.5.7. I have black or garbage screen on both displays. Laptop Gateway m-6862 with Mobility HD 2600.

 

  Maybe we can get mobility HD working this year if Apple will update macbook pro with Mobility 5000 series http://www.tomshardware.co.uk/forum/page-264649_10_0.html. At least we can hope :(

 

Hadn't got that far before I trashed the {censored} outta what I was doing:(:(

 

But I accidently got my M2600 running at full HD :D:unsure::D :D :D :D

 

I opened the ATIRaedon2000.kext/contents/info.plist and changed two values 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>CFBundleDevelopmentRegion</key>
<string>English</string>
<key>CFBundleExecutable</key>
<string>ATIRadeonX2000</string>
<key>CFBundleGetInfoString</key>
<string>ATIRadeonX2000 1.5.6.12 (4806)</string>
<key>CFBundleIdentifier</key>
<string>com.apple.ATIRadeonX2000</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundleName</key>
<string>ATIRadeonX2000 Kernel Extension</string>
<key>CFBundlePackageType</key>
<string>KEXT</string>
<key>CFBundleShortVersionString</key>
<string>1.5.6</string>
<key>CFBundleSignature</key>
<string>????</string>
<key>CFBundleVersion</key>
<string>5.0.6</string>
<key>IOKitPersonalities</key>
<dict>
	<key>ATIRadeonX2000</key>
	<dict>
		<key>ATIEnableWideBlitSupport</key>
		<true/>
		<key>ATIUseTearingWideBlit</key>
		<false/>
		<key>CFBundleIdentifier</key>
		<string>com.apple.ATIRadeonX2000</string>
		<key>IOCFPlugInTypes</key>
		<dict>
			<key>ACCF0000-0000-0000-0000-000a2789904e</key>
			<string>ATIRadeonX2000GA.plugin</string>
		</dict>
		<key>IOClass</key>
		<string>ATIRadeonX2000</string>
		<key>IODVDBundleName</key>
		<string>ATIRadeonX2000VADriver</string>
		<key>IOMatchCategory</key>
		<string>IOAccelerator</string>
		<key>IOPCIMatch</key>
		<string>0x94001002 0x94011002 0x94021002 0x94031002 0x95871002 0x95831002 0x95881002 0x94c41002 0x94c91002</string>
		<key>IOProviderClass</key>
		<string>IOPCIDevice</string>
		<key>IOSourceVersion</key>
		<string>1.5.6.12</string>
		<key>IOVARendererID</key>
		<integer>16908288</integer>
		<key>sensor-properties</key>
		<array>
			<dict>
				<key>device_type</key>
				<data>
				Z3B1LXNlbnNvcg==
				</data>
				<key>location</key>
				<string>GPU</string>
				<key>name</key>
				<string>gpu-sensor</string>
				<key>polling-period</key>
				<data>
				AAAAAQAAAAA=
				</data>
				<key>reg</key>
				<data>
				AAAAAg==
				</data>
				<key>sample-period</key>
				<data>
				AAAAAACYmAA=
				</data>
				<key>sensor-id</key>
				<data>
				AAAABg==
				</data>
				<key>version</key>
				<data>
				AAAAAg==
				</data>
				<key>zone</key>
				<data>
				AAAAAg==
				</data>
			</dict>
		</array>
	</dict>
</dict>
<key>OSBundleLibraries</key>
<dict>
	<key>com.apple.iokit.IOGraphicsFamily</key>
	<string>1.0.0b1</string>
	<key>com.apple.iokit.IONDRVSupport</key>
	<string>1.0.0b1</string>
	<key>com.apple.iokit.IOPCIFamily</key>
	<string>1.0.0b1</string>
	<key>com.apple.kernel.iokit</key>
	<string>1.0.0b1</string>
	<key>com.apple.kpi.bsd</key>
	<string>8.0.0</string>
	<key>com.apple.kpi.iokit</key>
	<string>8.0.0</string>
	<key>com.apple.kpi.libkern</key>
	<string>8.0.0</string>
	<key>com.apple.kpi.mach</key>
	<string>8.0.0</string>
	<key>com.apple.kpi.unsupported</key>
	<string>8.0.0</string>
</dict>
</dict>
</plist>

 

The line:

"<string>0x94001002 0x94011002 0x94021002 0x94031002 0x95871002 0x95831002 0x95881002 0x94c41002 0x94c91002</string>"

 

I change one value to 0x98571002 and another to 0x94c41002

 

both being id's for 2600 hd agp and the other is the 2600 mobility.

 

the attachment below shows this.

 

The only thing now is I'm lost to get it working on the laptop screen :wacko: :wacko:

post-422040-1254050555_thumb.jpg

Ichijoe
Ichijoe
Posted
Posted

The Mobility will work just fine with an External Display, with QE and CI (i.e. DVI or VGA out), that's not the problem, and never has been!!

 

The trick is to get it working ~under the "Laptop" Display~, and with the only possible exception of some Toshiba Laptops*, I've never seen / heard of anyone ever getting such ~Drivers~ to work under OSX.

 

I'll admit I'm not sure if it's the way the "Card" is physically connected LVDS instead of DVI or if it really is just a Framebuffer problem, or both.

 

Fact is this has been a problem for such users for over (or getting on), Two Years now!

 

I sincerely doubt that this "Issue" can be fixed outside of ATI or Apple, and neither have reason to do so.

 

*Toshiba has a different connection method then most other OEM's

In short unless you have a Toshi you can basically go ahead and give up now.

hackmymac
hackmymac
Posted
Posted

Update: Back to native 1024x768 res on internal LCD. I have to change course to look for keypad drivers.

 

I will return.

 

If you wondering how I got internal going, I used the AGP driver install set.

andrean
andrean
Posted
  • Author
Posted
Update: Back to native 1024x768 res on internal LCD. I have to change course to look for keypad drivers.

 

I will return.

 

If you wondering how I got internal going, I used the AGP driver install set.

 

 

а на русском тут ктото понимает?

Aidass
Aidass
Posted
Posted

My results:

http://www.insanelymac.com/forum/index.php...ry1069094\

You can read the whole thread, but that would be useless, you won't get it working, first of all you have to be some kind of programmer, not just a simple person. Just give up as all of us did, or maybe you're a donkey so you still can try getting it workin, anyways good luck!

smnhtkmpr
smnhtkmpr
Posted
Posted
The trick is to get it working ~under the "Laptop" Display~, and with the only possible exception of some Toshiba Laptops*, I've never seen / heard of anyone ever getting such ~Drivers~ to work under OSX.

 

 

*Toshiba has a different connection method then most other OEM's

In short unless you have a Toshi you can basically go ahead and give up now.

 

hey!

 

so, i have a toshiba satellite l500-153 with an ati mobility radeon hd 4570. what do you think, will it work properly?

 

thanks in advance...

hackmymac
hackmymac
Posted
Posted

Using the "ati radeon hd 2600 pro agp 10.5.6 - 10.5.x" package worked for me. I got the screen to work in one res only. Try it out. It may work.

 

I wont give up. I will try what I know. So far I'm looking at other Kext's within the driver package and also working on vanilla kext aswell to get a fix for it.

 

It may take some time, but I'd rather have a go than {censored} about it!! :(

 

sjoseph - the model of my toshi is the A200. I can see why they shouldnt work on other models. Most of the lappies that I've pulled apart from the year have nearly the same interface for the graphics area.

 

Andrean - what ever language that is, I cant read it mate. Any chance of an english version??

sjoseph
sjoseph
Posted
Posted

@hackmymack im using p200 so its pretty much the same mobo as yours. are you sure the kext you have did that? or did it just remove the mobility dev id (eg x****) from the kext. this means your display would only be working in 1024x768 and no qe ci.

 

Or have you done somthing different?

hackmymac
hackmymac
Posted
Posted

@sjoseph - yes mate I'm sure. I only installed that pkg. I did a wipe before starting again, cause it screwed up some coding, then installed it. I did not change any kext at all. didn't even repair the permission on any thing, just restarted and it worked.

 

I having a little trouble atm due the missus being in and outta hospital, but I'm sure i'll get there.

verma
verma
Posted
Posted

I was googling for mobility HD and find some info on russian board.Apple use mobility HD2600 on their imac,but there is some differense between pc mobility 2600 and Mac mobility chips. The differense is a voltage for laptop display. It comes permanent on Imac,but pc chip waiting a command for giving power to display.The kext for desktop hd2600 works fine with vga out (not for me though), but this driver cant power on the voltage for internal display what connected with lvds,so mobility chip can't read edid of internal display. 

 There is 2 way to fix it

1 Give a voltage manually on the laptop display (hardware mod)

 

2 Fix the driver for a power on the voltage

 

3 Inject EDID manually

 

 

 

 Internal display is a common problem for mobility HD and some Nvidia chips,and there was a good idea http://www.insanelymac.com/forum/index.php?showtopic=37630 ,but unfortunately it's never works. 

Any ideas?

 

 

а на русском тут ктото понимает?

 

 Тебе сюда http://www.applelife.ru/topic/8068-ati-hd-mobility/

hackmymac
hackmymac
Posted
Posted

yeah, and?? I never said I did anything special. Hence why I'm turning my attention to monitor type kexts, and having a play the atixxxxxx.kext aswell. Just letting others know so they can use laptop as a laptop without having to cart another monitor around.

hackmymac
hackmymac
Posted
Posted

I got the missus back from the hospital, and the laptop took a dump and wont work :D :D :censored2:

 

I'll be back on it after a couple of days......................

  • 3 weeks later...
Openminded
Openminded
Posted
Posted
The Mobility will work just fine with an External Display, with QE and CI (i.e. DVI or VGA out), that's not the problem, and never has been!!

 

The trick is to get it working ~under the "Laptop" Display~, and with the only possible exception of some Toshiba Laptops*, I've never seen / heard of anyone ever getting such ~Drivers~ to work under OSX.

 

I'll admit I'm not sure if it's the way the "Card" is physically connected LVDS instead of DVI or if it really is just a Framebuffer problem, or both.

 

Fact is this has been a problem for such users for over (or getting on), Two Years now!

 

I sincerely doubt that this "Issue" can be fixed outside of ATI or Apple, and neither have reason to do so.

 

*Toshiba has a different connection method then most other OEM's

In short unless you have a Toshi you can basically go ahead and give up now.

 

That's interesting!

Do you know which models might be working and how?

I'm looking for a solution for the A200 :)!

 Share
Go to topic listing
×
×
  • Create New...