From owner-freebsd-hackers Sun Jan 11 17:37:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA02463 for hackers-outgoing; Sun, 11 Jan 1998 17:37:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rvc1.informatik.ba-stuttgart.de (rvc1.informatik.ba-stuttgart.de [141.31.112.22]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA02192; Sun, 11 Jan 1998 17:36:00 -0800 (PST) (envelope-from helbig@Informatik.BA-Stuttgart.DE) Received: (from helbig@localhost) by rvc1.informatik.ba-stuttgart.de (8.8.8/8.8.5) id BAA00286; Mon, 12 Jan 1998 01:26:41 +0100 (MET) From: Wolfgang Helbig Message-Id: <199801120026.BAA00286@rvc1.informatik.ba-stuttgart.de> Subject: Re: Weird syscons errors In-Reply-To: <199801111815.SAA28880@awfulhak.demon.co.uk> from Brian Somers at "Jan 11, 98 06:15:03 pm" To: brian@awfulhak.org (Brian Somers) Date: Mon, 12 Jan 1998 01:26:39 +0100 (MET) Cc: karpen@ocean.campus.luth.se, hackers@FreeBSD.ORG, yokota@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (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? > > Yep. Go to /sys/net/i386/isa/syscons.c 1.242 and the problem will go > away. Did that, and the problem did not go away. So I speculate syscons.c dead keys are not the reason for syscons dead screens. Wolfgang > > > /Mikael > > -- > Brian , , > > Don't _EVER_ lose your sense of humour.... > > >