From owner-freebsd-questions Sat Jun 29 19:08:19 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA03108 for questions-outgoing; Sat, 29 Jun 1996 19:08:19 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA03086 for ; Sat, 29 Jun 1996 19:08:15 -0700 (PDT) Received: from mail.biddeford.com (root@mail.biddeford.com [204.120.68.142]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id OAA19039 for ; Sat, 29 Jun 1996 14:57:39 -0700 Received: from dtaylor (pld23.biddeford.com [204.120.68.86]) by mail.biddeford.com (8.7.4/8.7.3) with SMTP id RAA13510 for ; Sat, 29 Jun 1996 17:53:11 -0400 (EDT) Message-Id: <199606292153.RAA13510@mail.biddeford.com> X-Sender: dtaylor@mail.biddeford.com X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 29 Jun 1996 17:59:07 -0500 To: questions@FreeBSD.ORG From: dtaylor@eyemagic.com (Darrell Taylor) Subject: ATI Mach64 cards Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Though the compatibility list for FreeBSD includes ATI Mach64 cards, the FAQ says that to make these cards work, a whole stack of workarounds and rebuilds will be necessary. (Text below). Does this state of affairs still exist? Has the bug been squashed? Having barely survived lengthy attempts to configure Linux with a similarly problematic Stealth32 card some years ago, I am not inclined to add a card-incompatibility to the challenges of an FBSD install. (Unfortunately I found this paragraph after ordering the cdrom and starting the partitioning process.) Thanks, Darrell Taylor Is this still true?: " The problem is that the ATI Mach 64 uses address 2e8, and the fourth serial port does too. Due to a bug (feature?) in the sio.c driver it will touch this port even if you don't have the fourth serial port, and even if you disable sio3 (the fourth port) which normally uses this address. 7.9. What's the solution or workaround for this problem? Until the bug has been fixed, you can use this workaround: 1. Enter -c at the bootprompt. [ the kernel goes into configuration mode] 2. Disable sio0, sio1, sio2 and sio3 (all of them). This way the sio driver doesn't get activated -> no problems. 3. Type exit to continue booting. 7.10. The workaround works fine, but now I want to use my serial ports. You'll have to build a new kernel with the following modification: in /usr/src/sys/i386/isa/sio.c find the one occurrence of the string 0x2e8 and remove that string and the preceding comma (keep the trailing comma). Now follow the normal procedure of building a new kernel. 7.11. Now everything runs great, except for X Window: my screen goed black or X Window runs but with all kinds of problems. Some newer ATI Mach 64 video cards (notably ATI Mach Xpression) do not run with the current version of XFree86. You can get a beta-version of a new X-server that works better, by looking at the XFree86 site and following the links to the new beta release. Get the following files:..." Drop me a line, anytime! *********************** dtaylor@eyemagic.com (207) 874-2838 http://www.eyemagic.com ***********************