106 replies to this topic

[Soaa]

Strange, OpenGL Extensions Viewer doesn't work properly on my computer. Sounds like we can use the same driver though, huh. I guess that's good news? (:

[Slice]

Soaa, on Mar 9 2008, 01:05 AM, said:

Strange, OpenGL Extensions Viewer doesn't work properly on my computer. Sounds like we can use the same driver though, huh. I guess that's good news? (:

Yes, glviewer for windows crashes for me too, but I can view settings.

[Soaa]

Ah, I see. It didn't give me my texture memory though.

Hmm... Any more suggestions on how I should configure the drivers? I have a feeling ATINDRV is the way to go. =P

[Soaa]

So, any news? ;p

I read in the AGPGart thread that something isn't working properly because of AGPGart? Or are there missing values? I'm lost as to what else I can test now, so I disabled ATILead.kext and went back to the good ol' framebuffer for the time being.

[Slice]

To test something new we need to create something new. But I have no information what to change.

[Soaa]

I see, we both have the same problem then... that of not knowing where to go! I tried adding some more values from the Mac's ioreg into ATILead's Info.plist, but I'm still getting a crazy fuzz like before.

[Slice]

Soaa, on Mar 13 2008, 09:40 PM, said:

I see, we both have the same problem then... that of not knowing where to go! I tried adding some more values from the Mac's ioreg into ATILead's Info.plist, but I'm still getting a crazy fuzz like before.

Digital photo or your screen?

[Soaa]

Fuzzy pics. Hope this helps?

[Slice]

Soaa, on Mar 16 2008, 03:05 AM, said:

Fuzzy pics. Hope this helps?

Yes! It is clear!
These pictures arisez when ATIRadeon8500.kext sets Display_Base_address to zero so you see RAM on the screen. Or AGP_BASE_ADDRESS=0 so AGP_transaction send data to zero.
Check once again all info.plists about memory bases, sizes and addressing.

AGPGart 265 permit you to change AGP_Base. Please, prepare detailed report, what is happen with different settings. Dmesg when possible.

[Soaa]

I've tried AGP_Base=0, 0xf0000000, 0xe0000000 before posting these pics. All had the same result, I'll post more test results as they come.

Edit: I tried fiddling with ATILead's IOSpaceOffset a bit, but no difference. I don't see any other settings to play with. Do you have any suggestions for me?

[Slice]

I made an attempt to patch 8500. But I can't promise you anything...
It is version from 10.4.8.

[Soaa]

Thanks! I'm at work now, so I can't test it right away. I'll test it once I get home.

May I ask, what did you patch, and how? I'm curious, and if this doesn't work, maybe I can do some patching of my own.

Also, I test this with ATILead and AGPGart, right? With what settings?

[Soaa]

Okay, tested your new driver.

Without AGPGart nor ATILead, it loads, and the bottom quarter of my screen goes fuzzy, then my computer reboots itself instantly.

With ATILead, with or without AGPGart, it does the same fuzzy lines as I've shown.

[Slice]

I make new patch for Radeon8500. (other version 1.4.40.4). I replaced commands from addresses 15ea8 to 15f1d and later.
Now I can boot to desktop with such settings
I have 1Gb total RAM = 0x40000000
VRAM 128Mb is shared with RAM so
VRAM_addr = 0x38000000 VRAM_size=0x08000000
I patch ATIRadeon8500.kext to make this addresses.
AGP_aperture set to 0x04000000 = 64Mb.
In AGPGart.info.plist I write

			<key>AGP_Base</key>
			<integer>0x3c000000</integer>

That is VRAM_addr+AGP_aper=0x38000000+0x04000000
Then in ATI1Slice I set F8,size=0x00300000. It is too bad. I have very slow system. But I can enter desktop!
With Callisto I can't enter desktop with any settings!!!!!!
So, ATILead require corrections, or Callisto don't work with AGP at all.
I think a good way is to launch ATINDRV. But how?
Real Mac with Radeon9000 uses AppleNDRV which is PowerPC only, so useless.
One more probable way is to revive RadeonFB project, but no one programmer is successful.
The most real way is to use IONDRVSupport without switch resolutions.

Attached Files

•  ATIRadeon8500.kext_3.zip   277.05K   21 downloads

[Soaa]

Slightly off-topic... I use JaS 10.4.7, should I use Software Update to update to 10.4.11 before testing?

[Slice]

Soaa, on Mar 17 2008, 05:10 PM, said:

Slightly off-topic... I use JaS 10.4.7, should I use Software Update to update to 10.4.11 before testing?

I am using JaS 10.4.6 so... at your will. The kext will work in any system.

[Soaa]

I see. I'll test it once I get home. I'd also like to upgrade to Leo, would you think that's a good idea or a bad one? =P

For testing purposes though, I'll stick to Tiger for now. I might jump to Leo once things work.

[Slice]

Soaa, on Mar 17 2008, 11:44 PM, said:

I see. I'll test it once I get home. I'd also like to upgrade to Leo, would you think that's a good idea or a bad one? =P

For testing purposes though, I'll stick to Tiger for now. I might jump to Leo once things work.

AFAIK drivers for Tiger work better then for Leo.

[Soaa]

I see. Tiger it is then.

I tried playing with AGPGart's and ATILead's values with your latest ATIRadeon8500 and I'm still getting a fuzzy screen. If you have anything for me to test in particular, please tell me.

Also, this might be useful to you: I have 768MB of system RAM and 32MB of dedicated VRAM, and I can't share. That probably affects some of the values.

[someguy429]

Hello, I've been trying some of your drivers with x200 mobility (dev id 5955), I can load the ATILead with Calisto and with 8500 kext. I can get to my desktop and I have two screens on the same screen, I can change my screen resolution (on both screens). Thou I have no QE/CI and I only have 8mb VRam. I just thought I'd tell you. Anything else you want to know?