Jump to content

Callisto Technical Discussion

Swad

By Swad,
in ATi

 Share
826 posts in this topic

Recommended Posts

vince29
vince29
Posted
Posted

Sorry to be rude, but can't you search a little ? All your questions have been answeared several times in this thread and on Omni's site.

 

uninstall :

sudo rm -R /System/Library/Extensions/Callisto*

 

QE&CI : CallistoFB is used instead of IONDRVFramebuffer. Your ATIRadeonxxxGA.plugin refers to IONDRVFramebuffer. As it is no longer loaded, the GA plugin doesn't detect it and thus can't load.

To enable QE&CI with callisto, I strongly recommend that you read Omni's FAQ & troobleshoting.

mmk
mmk
Posted
Posted
It ahs been mentioned multiplpe times in this very thread how to enable QE and CI, just search for it. QE and CI will never be part of the callisto driver, because it's a different part of osx.

 

 

Sorry to be rude, but can't you search a little ? All your questions have been answeared several times in this thread and on Omni's site.

 

uninstall :

sudo rm -R /System/Library/Extensions/Callisto*

 

QE&CI : CallistoFB is used instead of IONDRVFramebuffer. Your ATIRadeonxxxGA.plugin refers to IONDRVFramebuffer. As it is no longer loaded, the GA plugin doesn't detect it and thus can't load.

To enable QE&CI with callisto, I strongly recommend that you read Omni's FAQ & troobleshoting.

 

 

As you could have seen from his post, he has a radeon 7000.

There is no QE/Ci for cards oldder than radeon 9550 (although QE is possible .....)

Try your best with opengl.

stmkjp
stmkjp
Posted
Posted

for People who have trouble getting QE&CI,

if you installed AppleI386PCI.kext for AGP, remove it.

that kext seems to have conflict with CallistoFB.

 

I can have QE&CI with no problem after removing the kext.

 

many people might know about this, but i hope this little tip can help people like me.

cyclonefr
cyclonefr
Posted
Posted

ok i ve tried removing the kext that wasnt loaded in safe mode but still same screen issue white + blue stripes when changing resolution, i guess safe mode uses also some frameworks etc...

 

Beside ive noticed that omni's driver remove the mouse scramble after exiting an OPENGL apps! that's a great news

TheManiacKY
TheManiacKY
Posted
Posted

I'm trying and trying over and over again but I never see omni's driver load or whatever at boot up with -v. I seen a debug list of where someone shown the driver loading and finding the hardware. What am I doing wrong? The only thing I'm seeing pop up everywhere is :

 

"VID: Family specific matching fails"

 

I'm running a Ati Mobility Radeon 9700 with 128meg. I've seven several other people get it working in the form. My hardware id is 0x4e50. I'm running OSX 10.4.6.

 

My info.plist for CallistoHal.kext is :

<string>CallistoHAL</string>

<key>IOMatchCategory</key>

<string>IOService</string>

<key>IOPCIMatch</key>

<string>0x4e50</string> <---- Should this be 0x4e50 or 0x4e501002&0xffffffff

<key>IOProbeScore</key>

<integer>60000</integer>

<key>IOProviderClass</key>

 

I apprecate any help I get! Thank you.

TheManiacKY
TheManiacKY
Posted
Posted
Folks, Radeon mobility 9600 AGP finally works in version 3.

 

Radeon Mobility 9600/9700 (M10/M11) NP:

 

Chipset Model: Radeon Mobility 9600/9700 (M10/M11) NP

Type: Display

Bus: PCI

VRAM (Total): 64 MB

Vendor: ATI (0x1002)

Device ID: 0x4e50

Revision ID: 0x0000

Displays:

Resolution: 1280 x 800 @ 60 Hz

Depth: 32-bit Color

Core Image: Not Supported

Main Display: Yes

Mirror: Off

Online: Yes

Quartz Extreme: Not Supported

I am so happy with it!!!

The first reboot gives me a noisy screen. Then it never shows in next several reboots.

I guess it's a quite robust version.

 

LOVE YA OMNI !!

ps. I remember someone is successful for an AGP bus, can sb gives me a hint of which thread I should read?

 

 

Is there any way you can give me your CallistoHAL.kext/Contents/Info.plist file? What did you call the IOPCIMatch key? The whole field please.

 

My info.plist for CallistoHal.kext is :

<string>CallistoHAL</string>

<key>IOMatchCategory</key>

<string>IOService</string>

<key>IOPCIMatch</key>

<string>0x4e50</string> <---- Should this be 0x4e50 or 0x4e501002&0xffffffff

<key>IOProbeScore</key>

<integer>60000</integer>

<key>IOProviderClass</key>

 

I apprecate any help I get! Thank you.

TheManiacKY
TheManiacKY
Posted
Posted
Is there any way you can give me your CallistoHAL.kext/Contents/Info.plist file? What did you call the IOPCIMatch key? The whole field please.

 

My info.plist for CallistoHal.kext is :

<string>CallistoHAL</string>

<key>IOMatchCategory</key>

<string>IOService</string>

<key>IOPCIMatch</key>

<string>0x4e50</string> <---- Should this be 0x4e50 or 0x4e501002&0xffffffff

<key>IOProbeScore</key>

<integer>60000</integer>

<key>IOProviderClass</key>

 

I apprecate any help I get! Thank you.

 

Never mind! I got it all working. I did need to use the 0x4e501002&0xffffffff and I had to put the kext files in the extension folderi instead of putting the Callisto_latest folder into extension.

BaselineAce
BaselineAce
Posted
Posted
Never mind! I got it all working. I did need to use the 0x4e501002&0xffffffff and I had to put the kext files in the extension folderi instead of putting the Callisto_latest folder into extension.

I was initially confused by this as well. Maybe Omni would like to update his insallation instructions?

TribesMan
TribesMan
Posted
Posted

I have an idea. Many users are reporting that after reboot the image is corrupted. And this can be solved if you try changeing resolution up and down a few times. So why not make a keybord shortcut to increase or decrease resolution. And so if your screen is corrupted, you only have to press a few keys and you are ready for work. What do you think?

 

Did anybody try this yet?

xtraa
xtraa
Posted
Posted
I have an idea. Many users are reporting that after reboot the image is corrupted. And this can be solved if you try changeing resolution up and down a few times. So why not make a keybord shortcut to increase or decrease resolution. And so if your screen is corrupted, you only have to press a few keys and you are ready for work. What do you think?

 

Did anybody try this yet?

 

Yes this is a good idea. i think you can easily make this with a script, autostart and a hotkey.

 

 

man the problem is the screen will be scrambled once more if u run an opengl app like an iphoto slideshow or a game...so that sux

this driver btw works under safe mode so there must be a workaround

 

I found a workaround.

 

You can install DisplayConfigX to create the data for your display (horizontal freq etc) and it will build you a

display file.

 

After that, there will be no more wrong display detection. Also you can lock the windowserver.plist.

 

Don't panic: If you enter the wrong settings for your display, it won't boot up to the gui. In that case you

have to simply remove the new created folder in /system/library/displays/overrides/ via the commandline.

The program itself also gives you a hint on that.

belgrano
belgrano
Posted
Posted
u must be using beta003 no? i said it worked using beta002

else boot -s

then type:

fsck -fy

mount -uw /

rm -R /System/Library/Extensions/Call*.*

rm -R /System/Library/Extensions.mkext

rm -R /System/Library/Extensions.kextcache

reboot

cyclonefr, thank you for that!

You saved me from a reinstall. :blink:

merak
merak
Posted
Posted

i read that there's no way to make qeci working wiv 10.4.6 is that true?

i'm not gonna use callisto if that's true..

any help?

cyclonefr
cyclonefr
Posted
Posted

no prob belgrano...Xtraa let me know, ur software freeze my loginwindow without callisto installed maybe it was working who know, dont have the courage to try callisto for the 10th time...let me know if it works with DisplayConfigX!

xtraa
xtraa
Posted
Posted
no prob belgrano...Xtraa let me know, ur software freeze my loginwindow without callisto installed maybe it was working who know, dont have the courage to try callisto for the 10th time...let me know if it works with DisplayConfigX!

 

Ok, maybe you can help me on this, forget about displayConfigX it seems to be even way more simple:

 

I started about 8 times now, and no reso probs. :D Could be luck...

 

The idea is, to simply write-protect the file with the actual proper display settings, so that the system can't

change it anymore. That does not mean that you are unable to change the resolution in osx, but after a

restart it will remember the locked resolution. (hopefully). So thats the plan. :D

 

Here is what I did so far:

 

1. In OSX I simply locked two files:

 

a) yourVolume/Library/Preferences/com.apple.windowserver.plist

 

You have to copy that to the desk, delete the original, copy it back and then rightclick>Info. At the very

bottom select: read only and also at the top check the: Lock checkbox.

 

bee) yourUsername/Library/Preferences/ByHost/com.apple.windowserver.YOURUSERNAME.local.plist

 

Rightclick on Info and do the same procedure again. No need to copy it this time because you can modify

it in place.

 

Press your thumbs that it will work with your setup, too. :blink::)

dbunder
dbunder
Posted
Posted

I've asked this before, but I didn't catch an answer to it. What's the absolute minimum ATI kexts you need to get CI/QE to work? With all the ATI drivers installed and running, my sound won't work under 10.4.6. Sounds odd but it's true. I am about to do a reinstall with 10.4.4 (myzar's, it has an update to 10.4.5), so hopefully that'll cure some of my ills.

 

edit: oh, what do i delete to clear ALL screen resolution settings? i've tried the stuff in omni's install instructions and xtraa's post, but my current system (JaS 10.4.6) is so garbled i can't even dream of changing resolutions. if this happens on my new install, i want to be able to fix it. any help?

VN Man
VN Man
Posted
Posted

For people who have problem with their x1xxx series try this method -

 

http://forum.osx86project.org/index.php?showtopic=14825

 

I tried on my Sapphire x1600xt PCIe and I've got both QE/CI supported and also something called "Rotation" now supported...

 

If only it would be this easy to get my RealTek ALC882 working in 7.1 mode :)

cyclonefr
cyclonefr
Posted
Posted

xtraa i dont how it will work, cause if u lock ur setup files (ie to 1280) the driver will still seek for 1280 and can grab this f***ing blue stripes...Secondary how can u think that changing resolution ie from 1280 to 1024 during game etc wont scramble the screen if u only change a config file? i dont get it...

Let me know if it works for u...but for philgeek it doesnt seem to do the trick..

Nice to see ur still trying to find a workaround, but i wish omni is already working on a workaround cause the driver is useless having this main issue

cyclonefr
cyclonefr
Posted
Posted

ok xtraa ive tested to read only all the apple's monitor configuration files and ive got almost the same result : seems to start up easier and grab the 1280 but when i launch ILIFE and play a slideshow in full screen i get f***ed lines on my screen and same for gaming...

I guess it may be a workaround for people trying to use in native 1600 and dont want to reboot ten times else ... im back in VESA mode 1280

Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...