omni's minimalistic web site

Troubleshooting

I thought to try another page with more detailed information. Naturally, read the F.A.Q. page first since it has general answers to problems you might be having. Other issues I will put into their own separate heading here...

This is the most important bit of all. I do NOT have any idea what you do to your system and how it is setup. If Callisto does not work for you it could be due to other reasons and not Callisto itself.
Any additional "patches" that you run that relate to graphics subsystem or any other subsystem could be causing instability, lack of functionality, etc. Run the clean system without any "mods" or "improvements" before writing to me about problems with Callisto. I cannot stress this enough, but it is ESSENTIAL

My monitor is a DFP and Callisto detects it as CRT

Current build supports "proper" monitor detection through I2C/DDC method and your DFP should get detected without any issues, unless there are some other problems elsewhere.
If you, if you are one of those people who uses DVI to SUB-D adapter to connect a DIGITAL output of ATI card to an analog DB-15 cable, then all I can say is "DUH!". Your DFP monitor will never be detected as DFP for as long as you use that dongle adapter. Either connect directly to DVI or live with CRT limitations.
I cannot stress this more, because I do not want to hear about "bugs" where your DFP is detected as CRT while not using the real digital cable. It is NOT a bug, you are the bug. Just because you have a DFP screen means nothing if you do not feed it digital signals via DVI. No DVI - NO DFP detection period

Kernel panic

No idea here, provide me with a kernel debug output from the boot screen and perhaps I can figure it out. I need all the lines that contain Callisto: in them as well as the actual kernel panic registers and values.

Black screen with mouse cursor instead of the Desktop

You must be using ATI KEXTs from 10.4.6. It seems Apple has changed something between 10.4.5 and 10.4.6 versions. Just go back to 10.4.5 ATI KEXTs and you should be fine

White screen with blue vertical lines on mode change

Try using the cursor up and down keys to try another resolution, just go cursor up once and then go back with cursor down to the same resolution, it should fix the white screen and display the selected resolution.

Black screen on boot or on mode change

The monitor has gone "Out of range" and that's what you get since the frequency range is not supported by your monitor. You can try using an alternative method of calculating and programming PLL. To enable this edit the Info.plist file of Callisto.kext and look for the key CallistoUseAltPLLMethod. Its value is by default false and you should set it to true to activate the alternative PLL method. If the above does not work, maybe you should start saving money for NVidia card? :)

No QE/CI support

For the last time, Callisto is not an IOAccelerator, it is a low-level driver and a frame buffer. If you want QE/CI support try the method from the F.A.Q.

Mouse tearing and other artifacts

Complain to Apple about this, has nothing to do with Callisto. If you don't like the artifacts, remove ATIRadeon* files from your /System/Library/Extensions folder.

Color banding (16-bit mode with DVI output)

It seems there are registers in both ATI and NVidia cards that control dithering, although I thought these registers relate to 2D/3D operations and not frame buffer. I am looking further into this.

Last update: 06-Jun-06