Date: Sat, 16 Oct 2004 16:59:00 -0500 From: "Conrad J. Sabatier" <conrads@cox.net> To: freebsd-current@freebsd.org Subject: Re: no echo console Message-ID: <20041016165900.4a0446b0@dolphin.local.net> In-Reply-To: <41717BC8.3070205@gamersimpact.com> References: <16753.26886.433270.800049@ran.psg.com> <20041016142741.32cd5ae8@dolphin.local.net> <41717BC8.3070205@gamersimpact.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 16 Oct 2004 14:51:36 -0500, Ryan Sommers <ryans@gamersimpact.com> wrote: > Conrad J. Sabatier wrote: > > >On Sat, 16 Oct 2004 11:31:34 -0700, Randy Bush <randy@psg.com> wrote: > > > > > > > >>on -current as of an hour ago (and the last few days too), running > >>many progs leaves the console, whether serial or xterm from another > >>host, not echoing. a `reset` fixes it. shell is bash2. > >> > >>randy > >> > >> > > > >Yes, I'm still noticing this, too. The last commits from yesterday > >seem to have improved the situation somewhat, but it's still not > >100%. Echo will just randomly become disabled after certain commands. > > > >Wish I could provide more specifics. Sorry. > > > > > > > Are you both using the syscons "device sc" console driver or are you > using the pcvt "device vt" console driver? "device sc" It's very odd, and hard to tell what's causing this or when it's likely to occur. I've noticed it a few times after running portupgrade. -- Conrad J. Sabatier <conrads@cox.net> -- "In Unix veritas"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041016165900.4a0446b0>