From owner-freebsd-alpha Wed Sep 5 19: 0: 0 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id DCA4037B403 for ; Wed, 5 Sep 2001 18:59:57 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA17032; Wed, 5 Sep 2001 21:59:45 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f861xGW32790; Wed, 5 Sep 2001 21:59:16 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15254.55412.456276.744140@grasshopper.cs.duke.edu> Date: Wed, 5 Sep 2001 21:59:16 -0400 (EDT) To: Jim Pirzyk Cc: Wilko Bulte , freebsd-alpha@FreeBSD.ORG Subject: Re: XFree86-4 and alpha DS10 In-Reply-To: References: <20010903211740.A1329@freebie.xs4all.nl> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Jim Pirzyk writes: > > (WW) ****INVALID MEM ALLOCATION**** b: 0x18a0000 e: 0x18a3fff correcting^G > > So I am thinking the problem has to due with the 'no driver attached' > message from the kernel. No, the kernel has nothing to do with allocating pci memory ranges; that is done by the 'bios" -- srm console in this case. The problem is that the X server always screws up when it "corrects" the memory range. Keep it from correcting anything, and you may be OK. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message