On Sunday 07 March 2004 20:48, Charles Garcia-Tobin wrote:

Like the antisocial git that I am, I had to wait until I had a problem before my first post. Anyways the problem is this: On my Suse9.0 box whether I get 3D enabled when X starts up seems be a bit random. Sporadically, (more common on an X restart than the first X boot) 3D will be disabled. When this happens I get the following info on /var/log/XFree86.0.log

(II) MGA(0): [drm] drmSetBusid failed (9, PCI:1:0:0), Device or resource busy (EE) MGA(0): [drm] DRIScreenInit failed. Disabling DRI.

I'm running a matrox G400 card.

You could try playing with the IRQ assigned to VGA and the Plug and Play OS settings in your Bios, I had all sorts of random behaviour from my GForce before messing with these.

Another curious aspect of the 3D behaviour is that when it does work, on full screen mode it will change the monitor timings to the point that my monitor will complain their out of range. The monitor will still display, but there is this nasty on-screen-display right in the middle, complaining that the frequency is out of range. Annoyingly there doesn't seem to be way of getting rid of it, so playing a game is a bit tricky. So does anybody know if there is a way of settings the timings for full screen 3D display?

I thought that the monitor settings when in fullscreen 3D were handled by X and therefore taken from the XFconfig file. Sometimes what happens with LCD's (I've seen this more on laptops) is that the X configuration tools only set up the native resolution of the LCD panel, if your 3D app runs at a different resolution then it just goes with the defaults left in the X configuration for that particular resolution.

So the first step would be to get X running at the right refresh etc for each resolution your card supports. then whatever resolution the 3D app runs at will be correctly configured.

Anyway it's something else we can mess with when I come to see you tomorrow !

Wayne