A quick note about VNC and GLX

I’m doing some image processing heavy-lifting this weekend with DeVIDE ng1.phase1 (that’s the not-yet-released next generation). The Windows XP scheduler is quite crappy, so on my laptop (1.6GHz Banias, 1G ram, 5400 RPM HDD) this kind of work tends to slow everything else down. So, I upgraded my Linux server box’s RAM to 1G as well (it has an Athlon64 2800+ and is running Centos 4.2 Linux, 7200 RPM HDD) in order to use this for some of the heavy processing.

Because it’s a headless server (and has the ATI Radeon 7000/VE to show for it), I needed some graphical remote access software, such as VNC. Turns out that most VNCs (Real, Tight, Ultra) do not support GLX out of the box, so not even software-3D rendering is possible. Yes, I know that I could have used a more traditional X server based setup, but I like the idea of resuming my running session from everywhere.

After a brief stint with (Free)NX and discovering that its resume support (Linux server, Windows client, 1.5.0) is completely borked (after resume, your wallpaper is turned into the remote desktop, no interaction allowed), I came across xf4vnc. I took the Xvnc from this package and copied it over my existing realvnc Xvnc and now I have GLX. Yay!

(I’ve posted this so that others googling for “vnc glx” will find information more quickly than I did.)

One thought on “A quick note about VNC and GLX”

  1. Yo charl, net terug van athene lees ik dat je ook niet stil zit. Misschien kan ik nog wat voor je betekenen op een HP athlon 64 (3400+) met een ati radeon x1300 als test machine (1GB ram natuurlijk een 300 GB s-ata disk). We kunnen kijken of er met vnc wat te doen is voor test doeleinden voor je. Ik hoor het wel, Ant

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.