I have some problems with it. It compiled fine (didn't even take much more than a night on my 250 MHz R4K), and it detects the graphics chip. But the screen just turns black when I run 'startx'. I can change back to a virtual console, and 'top' shows that WindowMaker runs as well. So X11 works, but isn't usable. Also, I can start X11 clients like xmms and run remote to another computer with music coming from my SGI.

And to the developers: Thank you for your work. Gentoo is quite nice on the Indigo2. I've only discovered two problems yet: XFree86, and that hwclock doesn't work and hangs at start-up and shutdown (should submit a bug report? This was from a stage3-mips3-20040131.tar.bz2 install).

Hello, I think I talked to you in #gentoo-mips about this. Anyway, this is the exact XF86Config I use on my Indy for newport. You might take a look at it and see if anything major is obviously different.

One more thing...you are the only person I've ever talked to that had an I2 XL. On top of that, there aren't many of us that run X on our Indy even. You may try emailing Guido about it. He's the fellow that maintains the newport driver. You can find his contact information on the same page you got the XF86Config.

I've looked through it, grepped for warnings and errors. There seems to be nothing wrong. The Newport graphics chip is detected, and the server starts. It's even possible to zap it with ctrl-alt-backspace (or switch to virtual consoles with ctrl-alt-f*). The only problem is that there's no picture.

To the issue at hand -- the monitor is syncing, just black? Amazing. I have to say, this stalls my plans to get XL cards for my Indigos...

Yes, it doesn't change resolution or anything from what is used at the text console. It just turns black. Of course, it could be that it actually tries to change resolution and fails, but it doesn't lose sync.