[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: wscons red color



On Sat, Apr 21, 2001 at 01:00:28PM -0400, Aaron Campbell wrote:
> On Sat, 21 Apr 2001, Peter Valchev wrote:
> 
> > The problem is that it works _before_ starting X.  After that, there is
> > no way to get it back.  I'd guess it's XFree86 problem.
> > That eliminates the chance for the cable to be loose, I think -- can you
> > try it after you've started X?
> 
> Still works for me with X running.
> 

There have been reports of various terminal problems after starting XF4
in -current/2.9-beta.  This is the only response I've seen so far that
isn't a "Me too", and this is a "I don't see that here".  Is this being
looked at a all?

Some things that may or may not be related to the problem:
1) My terminals are fine when I run xf86cfg.  If I start X any other way, 
terminals are extermely dark.  This seems odd, since xf86cfg starts X.
Perhaps something in the way X is started?  Could others who are having
similar problems see what happens starting xf86cfg from a good terminal?

2) After a cold boot, when X starts, I see neon fuzz for a split second,
Then X is all good.  When I reboot from an xterm, as X is starting, I see
my window manager as it was then I typed 'sudo reboot', for a split second,
the X is all good.  I don't remember this with 3.3.6.

<jakemsr@clipper.net>