From owner-freebsd-current Sun Jan 5 19:35:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA04345 for current-outgoing; Sun, 5 Jan 1997 19:35:21 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA04340 for ; Sun, 5 Jan 1997 19:35:19 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id UAA18789; Sun, 5 Jan 1997 20:35:11 -0700 (MST) Date: Sun, 5 Jan 1997 20:35:11 -0700 (MST) Message-Id: <199701060335.UAA18789@rocky.mt.sri.com> From: Nate Williams To: "Jordan K. Hubbard" Cc: regnauld@tetard.glou.eu.org (Philippe Regnauld), freebsd-current@freebsd.org Subject: Re: 2.2-BETA comments In-Reply-To: <11757.852517389@time.cdrom.com> References: <11757.852517389@time.cdrom.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > - during the installation process, in vty0 ("graphical" progression), when I > > scroll back with SCRL LOCK to look at kernel messages, if I return to > > normal mode and press SCRL LOCK again, the keyboard is frozen, only > > There appear to be a lot of problems with the 2.2 syscons. :-( We'll > work something out, even if it means ending up having to revert a > number of changes. Not that it makes any difference, but I'm mostly responsible for the syscons brokeness in 2.2. In my attempt to get PS/2 mice working I brought in some (very new) code that should have never been brought in. The worst part for the users stuck with broken hardware is that it seems to work 'mostly' fine on my system. I'm trying to get some hardware and software so that I can run -current on my main workstation (a PS/2 cable so I can run a PS/2 mouse and a version of XAceel that works under 2.2), so at least this should be fixed in the future. In the meantime, I *could* revert all of the kbdio and such changes from 2.2 if you think it would help. Whaddya think Jordan? Nate