From owner-freebsd-questions Mon Jun 24 10:47:46 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA11896 for questions-outgoing; Mon, 24 Jun 1996 10:47:46 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA11889 for ; Mon, 24 Jun 1996 10:47:44 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA28564; Mon, 24 Jun 1996 10:43:28 -0700 From: Terry Lambert Message-Id: <199606241743.KAA28564@phaeton.artisoft.com> Subject: Re: Intel Atlantis Motherboard To: morgan@odo.elan.af.mil (Jon P. Morgan) Date: Mon, 24 Jun 1996 10:43:28 -0700 (MST) Cc: questions@freebsd.org In-Reply-To: <31CEC34F.41C6@odo.elan.af.mil> from "Jon P. Morgan" at Jun 24, 96 09:33:19 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I have an Intel Atlantis Motherboard with a 133 MHZ CPU. > During boot, The console screen goes out during what appears > to be device probing. > I am able to get into device reconfiguration but the console > will screw up before going into the debuger. > I am running Freebsd 2.1 succesfully on my other P75. You have a MACH64 video card, which violates the standard for the IBM graphics card it is attempting to emulate by listening to port 0x3e8 when it has not been put in a specific mode that requires this. In other words, MACH64 cards are broken. You can work around the problem in two stages: 1) a) At the boot prompt, type "-c" and hit return b) At the next prompt, type "visual" and hit return c) Disable the SIO (serial port) driver. The conflict is with the SIo probe for COM3. d) Install normally. 2) a) Modify /sys/i386/isa/sio.c to remove 0x3e8 b) Rebuild and install a new kernel c) Reboot. Your serial ports, other than COM3, will once again be active. This is described in the handbook and in the 2.1R FAQ. It is fixed in more recent install snapshots by disabling com3 to start with. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.