From owner-freebsd-alpha Tue Aug 29 21:31: 0 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 0069837B43E for ; Tue, 29 Aug 2000 21:30:58 -0700 (PDT) Received: from ganerc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 13TzWb-000384-00; Wed, 30 Aug 2000 06:30:57 +0200 Received: (from daemon@localhost) by ganerc.mips.inka.de (8.11.0/8.11.0) id e7U261E08855 for freebsd-alpha@freebsd.org; Wed, 30 Aug 2000 04:06:01 +0200 (CEST) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Bizarre syscons problem Date: 30 Aug 2000 04:06:01 +0200 Message-ID: <8ohq69$8k9$1@ganerc.mips.inka.de> To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org PC164, 5.0-CURRENT. For any other kernel than GENERIC, the syscons console will not quite work right. If I copy the GENERIC configuration file to another name, say TEST, and build that kernel, it suffers from the problem, too. Sic. Symptoms: - Immediately visible: when control passes from the boot loader to the kernel, SRM's blue background remains instead of changing to black. - A getty comes up on ttyv0 (console), but you can't login there. - ttyv0 (console) keeps a blue background forever. - When the system is up, and you switch from a different ttyvX back to ttyv0, the last output is "sc0: on isa0". New kernel and syslog messages can appear, but switching to another ttyvX and back will always restore the display to the final "sc0: ..." line. - When messages go to the console, fragments with blue background show up on the current ttyvX. /me scratches head -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message