Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!fu-berlin.de!news.belwue.de!News.Uni-Marburg.DE!news.th-darmstadt.de!fauern!news.tu-chemnitz.de!irz401!uriah.heep!bonnie.heep!not-for-mail
From: j@bonnie.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: 2.0.5 screen problems after upgrade (no interactive response)
Date: 24 Jul 1995 11:41:43 +0200
Organization: Private U**x site, Dresden.
Lines: 22
Message-ID: <3uvpsn$aah@bonnie.tcd-dresden.de>
References: <3u7cuq$bb0@agate.berkeley.edu> <DC3II1.Drp@nemesis.lonestar.org>
Reply-To: joerg_wunsch@uriah.heep.sax.de
NNTP-Posting-Host: 192.109.108.139
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Frank Durda IV <uhclem@nemesis.lonestar.org> wrote:
>[0]I created a boot floppy and managed to boot up fine except when it
>[0]got to the point where the colourful initial configuration screen
>[0]was susp[osed to pop up I was simply faced with a blank screen. I
>Try disabling COM3 and COM4 detection. I have discovered several video
>systems (mostly on Intel MLBs) that use the I/O ports that other
>people use for COM3 and/or COM4. The COM3/COM4 probe could be scrambling
>the video chips brains. If you can't disable COM3/COM4 by themselves,
>try disabling all serial I/O and see if things improve.
Actually, maybe this is just COM4 (sio3) only?
I know of at least the S3 chips using 0x2e8 (plus a few derivatives
with higher bits set). I think this habit originated from IBM's 8514
register usage.
--
cheers, J"org private: joerg_wunsch@uriah.heep.sax.de
http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)