linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Drake <dan@reactivated.net>
To: gene.heskett@verizon.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: exiting X and rebooting
Date: Thu, 27 Nov 2003 13:14:15 +0000	[thread overview]
Message-ID: <3FC5F8A7.1000709@reactivated.net> (raw)
In-Reply-To: <200311270617.03654.gene.heskett@verizon.net>

Which display driver are you using for X? Using Xinerama/multi-displays or similar?
I noticed this behaviour once on a dual-monitor setup. After starting X then 
exiting it, I noticed the problems that you describe on the primary monitor. 
However the secondary monitor was showing the output as normal (including 
cursor) if I remember correctly.
Both displays were running from a single GeForce4 Ti card, using the nvidia 
binary driver under X. No framebuffer.

Never found the problem, but never really investigated either.

Gene Heskett wrote:
> Greetings;
> 
> I'm not sure what category this minor complaint falls under, but since 
> its evidenced by a 2.6 kernel and not a 2.4, this seems like the 
> place.
> 
> One of the things I've been meaning to mention is that if I'm running 
> a 2.6 kernel, and exit X to reboot, the shell that had a cursor when 
> I started X from it, no longer has a cursor when x has been stopped.  
> This occurs only for 2.6 kernels, but works as usual for 2.4 kernels 
> giving a big full character block for a cursor.
> 
> One can still type, and the keystrokes are echo'd properly.  But it is 
> a bit un-nerving at first.  Logging clear out and back in again to 
> re-init the shell doesn't help.  The cursor is gone.
> 


  parent reply	other threads:[~2003-11-27 13:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-27 11:17 exiting X and rebooting Gene Heskett
2003-11-27 12:16 ` Helge Hafting
2003-11-27 15:25   ` Gene Heskett
2003-11-27 13:14 ` Daniel Drake [this message]
2003-11-27 15:31   ` Gene Heskett

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3FC5F8A7.1000709@reactivated.net \
    --to=dan@reactivated.net \
    --cc=gene.heskett@verizon.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).