From owner-freebsd-hackers Sun Jan 11 09:24:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA13844 for hackers-outgoing; Sun, 11 Jan 1998 09:24:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA13828 for ; Sun, 11 Jan 1998 09:23:47 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.8/8.8.8) id SAA05066 for hackers@freebsd.org; Sun, 11 Jan 1998 18:20:33 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199801111720.SAA05066@ocean.campus.luth.se> Subject: Weird syscons errors To: hackers@FreeBSD.ORG Date: Sun, 11 Jan 1998 18:20:32 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk Hi! After having built the world and kernel from something like midnight yesterday (CET) I have this weird problem that I didn't have with a kernel from late december. Anyone else seen this? I have noticed syscons changes lately, and I'm wondering if they screwed anything up. What happens is that after the probe messages have come up, I get no more output. The computer continues to boot to full multiuser mode, and I can log in, but I have to do it "blindly". There seems to be no way to the console into displaying anything except those frozen boot messages. If I log in and and vidconrol "VGA_80x50", for example, the mode _does_ change, but the text doesn't. And I can switch vtys, but without any real significant change. Only way I could tell that switching vtys worked was because I had one vty in VGA_80x50 mode. If I start X11, it will switch to graphic mode just fine, and run in X11. Then when I exit X11, I get the same crap again. So... What's wrong? Anyone else seen this? /Mikael