Thank you all for the suggestions. There was definitely some problem here with GDM. Basically, on my initial install, GDM was crashing because X was configured to use the wrong video driver. I changed X to link to Xvfb (virtual frame buffer). Things started working at this point, but only with one DTU. To try to troubleshoot the problem, I removed GDM from inittab. I would start GDM manually.
After a long while, I restored the original inittab line (calling gdm directly WITH the -nodaemon option). I then did a 'telinit q', but things did not start working until AFTER I did a cold-restart of all SUNWut services. Then all but one (out of 7) client started working. The 7th is still hanging at the same place, and I suspect it somehow got fried. The latest version does solve quite a few headaches. I plan to do another 'clean room' install next week. Then I will be able to comment extensively on what went wrong. On 8/23/06, Bob Doolittle <[EMAIL PROTECTED]> wrote:
Dave Hwang wrote: > On Wed, 2006-08-23 at 14:03 +0200, Otheus (aka Timothy J. Shelling) > wrote: > >> I just downloaded the latest version of SRSS 3.1.1. The latest >> timestamp in this download set is the Release Notes, dated August 9, >> 2006. These notes indicate that RHEL 4AS U3 is now supported in this >> distribution of SRSS. Great! >> >> However, I have just installed it, and I am less than pleased with the >> results. While the SunRays connect, they all "hang" on the connected >> hourglass window (they have an IP address, contacted the >> authentication managers). That is, no X display appears. GDM does not >> seem to spawn any Xnewt processes. *On occasion* a single Xnewt >> process wil be displayed on *one* of the SunRays. At this point, one >> can login. But as soon as the user logs out, the SunRay "hangs" on the >> hourglass window as noted above. The hourglass looks like this: >> <-- 8 --> >> (where 8 represents an hourglass) >> > > I had a similar problem with srss-3.1.1 (Sunray Software 4 EA) and a > clean install of Fedora Core 5. Everything seemed to be working except > for getting GDM started on the DTU. However, my DTUs were hung at 26D > instead of the hourglass. 26D represents, in newer firmware, the same thing as the hourglass (I can't recall if it was with 2 or 3 dashes) in older firmware, sometimes accompanied by the "green newt" lizard cursor in really old firmware. We still refer to this sometimes as GNC (Green Newt Cursor) condition. It usually means that the Sun Ray has all of the network information, and has contacted utauthd on the server and is waiting for the X server to render something to it. On Linux most typically this occurs when gdm is misconfigured and can't start an X server/greeter using gdmdynamic, or if you have removed the SRSS RPM for gdm and are using the standard distro RPM (our changes are back into the main CVS root, but have not yet been picked up by all distros). Let us know if the solution below works for you. -Bob > I would get a single login window on my local > console, but no activity anywhere else. > > My problem: FC5 set up /etc/inittab to respawn GDM in nodaemon mode. > > My solution: configure inittab to start GDM once (in daemon mode): > > # Run xdm in runlevel 5 > # original FC5 config > #x:5:respawn:/etc/X11/prefdm -nodaemon > # for SRSS-3.1.1 - just start GDM once to respawn on its own. > x:5:once:/usr/sbin/gdm > > Hope this helps. > > Dave > > _______________________________________________ > SunRay-Users mailing list > [email protected] > http://www.filibeto.org/mailman/listinfo/sunray-users > _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
-- Otheus [EMAIL PROTECTED] +43.699.1049.7813 _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
