From owner-freebsd-hackers Wed May 5 6:50:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 57A061573D for ; Wed, 5 May 1999 06:50:52 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id PAA25947; Wed, 5 May 1999 15:50:44 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199905051350.PAA25947@freebsd.dk> Subject: Re: Changes to console code? In-Reply-To: <000f01be96fc$ebafe210$8cbc2dc1@ibfs.com> from Joachim Isaksson at "May 5, 1999 3:41: 3 pm" To: Joachim.Isaksson@ibfs.com (Joachim Isaksson) Date: Wed, 5 May 1999 15:50:44 +0200 (CEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Joachim Isaksson wrote: > Hi, > > I was running current 4.0 990318 (as far as I can remember, can look that up > once I get home from work), and yesterday I decided to do an upgrade to 990504 > via a clean install from boot floppy. > > My console now decides to go blank when the probe for sc0 is attempted. As far > as I can see it never gets any further in the boot sequence. Luckily I got the > problem at floppy boot, not after killing my old system off :) Hmm, I've seen this a couble of times, but a reboot have succeded every time. The machine is locked solid when this happens, so I've kindof written it off as flaky HW, that might have been premature. I thought it was hanging in the VESA/VM86 code, but I dont think that is enabled on the boot floppy... Hmm... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message