X86 systems have both Xorg and Xsun installed, as they both provide a different hardware driver set. I'm using Xorg 6.9 (almost the final release) on my laptop, as that's what rolled into the last OpenSolaris release.
But on SPARC there's no need for Xorg, as all of Sun's supported graphics cards are supported best by the Xsun server. I checked, and no Xorg stuff exists there. And of course I'm building earlier versions with no problems on the same box. I'm working from home today, but will try out .18 tomorrow. Ta, Mark. On Wed, 2005-12-21 at 20:04, Nathan Ingersoll wrote: > IIRC, SunRay's require using Xsun still. So he wouldn't have the > composite extension available, but Xorg is often installed so it may > be compiled with support for composite. > > On 12/21/05, Kim Woelders <[EMAIL PROTECTED]> wrote: > Mark R. Bowyer wrote: > > On Tue, 2005-12-20 at 21:26, Kim Woelders wrote: > > > >>>On Solaris Nevada on my x64 laptop, it works fine. On a > SunRay running > >>>off a SPARC-based server running the same Solaris release, > with both > >>>0.20 and now this pre1, on starting I'd get the split > screen, the 2 > >>>progress meters at the top would go, and then it would just > freeze that > >>>way. Truss shows it reading and writing forever on fd 4, > with the > >>>occasional "Err#11 EAGAIN" message on a read. If I clear > away my ~/.e16 > >>>and start that way, I see the extra progress meter as it > looks for > >>>backgrounds, but then the same long wait. It happens > whether or not I > >>>use the -p argument. I've left it over 5 minutes and it's > not helped. > >>>Version 0.17 worked fine, as did all the ones before? > > > > > > OK, further testing later: > > > > > >>Not sure what goes on here. If there is a session manager > I'd expect > >>that connection on fd 4. Is there a session manager > involved? I don't > >>recall having made changes to that in ages though. If not, > can you find > >>out what is on fd 4? > > > > > > Well, all my tests now it was fd 3, which according to > pfiles is an > > AF_UNIX socket at /tmp/.X11-unix/X3 - I've been getting :3.0 > as my > > display on this SunRay server. So it's the local talking to > the X > > server that's going on, which is expected? > > > Yes, the X-server connection will normally be on fd 3. > > > > >>Could you find out in which version (.18/.19/.20) the > problem first appears? > > > > > > .18 no longer exists on the sourceforge site. > > It can still be found here: > http://prdownloads.sourceforge.net/e/en/enlightenment > Could you please try that as well? > > > I built .19, and it > > happens there. I installed it, and logged out and in as a > "Failsafe" > > session - X and one dtterm. Started e16 from .19 and see > the closed > > doors for a long time. Did the truss and pfiles from my > Linux box next > > to the SunRay. Same thing. Killed e16, logged back in to > Gnome > > (gnome-session is starting "e16 -p e_config") and same thing > for fd 3. > > Go back into my .17 build directory, "gmake install", and > the problem > > has gone away again. Note I've tried without the -p - that > isn't it. > > > > So, go back to .19, and try starting it with --fast as > well. And we get > > in to a windowing environment, and all seems well. But no > dialogues > > will come up (menus will) and windows wont raise, and a > number of other > > issues show up. I can *move* windows, but it's not fully > functional. > > Back to .17, and everything's back again, including the > "About" box. > > All a bit trippy, really. It's like a central part of E > isn't working > > any more... The only thing I've not tried is rebuilding .17 > in case > > it's something about how I built it. I'm going to make sure > I have a > > safe backup of the working code first, and will then try > that. > > > > Does this give you any clues? > > > Not really. There are quite a few changes between .17 and .19. > Results > for .18 will narrow down the possibilities considerably. > > It sounds like some OS/X-server dependent issue. Which > X-server are you > using? If xorg, is e16 built with composite support? > > If running with/whithout --fast makes a difference the problem > may > somehow be related to the startup windows ("split screen"). In > .19 could > you try changing in src/startup.c > #define TEST_STARTUP_USING_TIMER 1 > to > #define TEST_STARTUP_USING_TIMER 0 > and see if that changes anything? > > /Kim > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep > through log files > for problems? Stop! Download the new AJAX search engine that > makes > searching your log files as easy as surfing > the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- o o mailto:[EMAIL PROTECTED] /v\ark R. Bowyer http://mark.thebowyers.me.uk [EMAIL PROTECTED] `-' --------------------------------------- /"\ ...fingerprint = 7924 9E9E 7B91 225E B065 \ / ASCII Ribbon Campaign 1024D/15140DC1 39D0 551D ABE6 1514 0DC1 X Against HTML Mail -------------------------------------------- / \ My grandma says she has eyes in the back of her head... I hope it's not hereditary. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
