Hi Calvin, Sorry - I should have provided more specific links.
The missing file for the 4.2.0->4.2.1 patch isn't a problem - 4.2.1 patches some doc files which aren't included in the src-1 tarball, but in the second tarball. The second tarball isn't needed to build the server, so I didn't suggest you download it. The only instance we've ever seen of vnc.so causing hangs when loaded into the console X server was with a RedHat 7.3 test system with a particular model of graphics card for which the console X server's drivers were rather ropey. The current vnc.so has to grab the pixel data *back* from the graphics card, which is obviously not as well supported/tested as the more common task of putting pixels onto the graphics card. Our card did also display some weird behaviours even without vnc.so installed, though, so we couldn't be sure that that was the cause. One other thing to remember is that if you replace vnc.so while you have a console X server running, you must remember to move or rm the old one before copying the new one into place, otherwise you overwrite the library binary while it's still in use, which will either fail the copy, or cause the X server to hang. If the vnc.so module causes you too many problems then, once a user is logged on to the console X server, you can run the x0vncserver program instead of using the module. This shouldn't really be any more stable, but it's worth a try. Regards, Wez @ RealVNC Ltd. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Calvin Webster > Sent: 07 November 2006 19:49 > To: James Weatherall > Cc: 'VNC Mailing List' > Subject: RE: vnc-server-3.3.3r2-28.2: "connection refused" or > "end of stream" > > Thank you Wez, > > It all built and installed without errors, albeit with a lot of "elbow > grease". My first connection to the console display froze up > the system > within seconds, though. I had to power cycle the machine to > get it back. > To prevent angering the gathering lynch mob, I won't be making another > connection until late in the day. Besides, the software RAID > needs time > to rebuild parity. I'm hoping that the freeze was something that won't > repeat after the system restart. > > Since I'm not familiar with the layout of xfree86.org I still had to > search to find the tar-ball and patches you mentioned. They weren't > right there on the "downloads.html" page where I expected. > > I followed the instructions in > "vnc-4_1_2-unixsrc/unix/README" exactly. > The only unexpected event was a single missing patch file > (xc/doc/specs/Xaw/TextSource) which I skipped. > > The XFree86 build was long, but uneventful. I got this message when it > was done: > > "Full build of Release 6.6 of the X Window System complete." > > "./vncinstall /usr/bin /usr/share/man /usr/X11R6/lib/modules" put > everything where it should be. > > I added entries to /etc/X11/XF86Config-4 to support remote console > display and vnc password authentication. > > Section "Module" > ... > Load "vnc" > EndSection > > Section "Screen" > Identifier "Screen0" > ... > Option "SecurityTypes" "VncAuth" > Option "UserPasswdVerifier" "VncAuth" > Option "PasswordFile" "/root/.vnc/passwd" > EndSection > > I set vncpasswd for root, then restarted X with <Ctrl><Alt><Backspace> > from the physical console. > > >From an adjacent machine on the same network (with vnc-4.1.2-1 > installed) I ran "vncviewer winggear:0". > > Authentication worked. > Display came up with the appropriate XDMCP login prompt. > Within 15 seconds the system on which I'd just build vnc froze. > Power reset was required to recover. > > --Cal Webster > _______________________________________________ > VNC-List mailing list > VNC-List@realvnc.com > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list