From owner-freebsd-hackers Wed May 5 7:58:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id A23B0158D7 for ; Wed, 5 May 1999 07:58:13 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id JAA18024; Wed, 5 May 1999 09:56:30 -0500 (CDT) From: Kevin Day Message-Id: <199905051456.JAA18024@home.dragondata.com> Subject: Re: Changes to console code? In-Reply-To: <199905051350.PAA25947@freebsd.dk> from Soren Schmidt at "May 5, 1999 3:50:44 pm" To: sos@freebsd.dk (Soren Schmidt) Date: Wed, 5 May 1999 09:56:29 -0500 (CDT) Cc: Joachim.Isaksson@ibfs.com, 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 > I'm seeing something similar.... very current code makes my system essentially throw the cursor all over a blank screen (like it's printing spaces or tabs very fast)... Going back to Mar 15th's kernel, it went away. I haven't had time to track this down any further, but i blamed it on weird hardware too. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message