From owner-freebsd-alpha Thu Sep 6 9:37:15 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.disney.com (mail.disney.com [204.128.192.15]) by hub.freebsd.org (Postfix) with ESMTP id 68BE537B401 for ; Thu, 6 Sep 2001 09:37:11 -0700 (PDT) Received: from Hermes10.corp.disney.com (hermes10.corp.disney.com [153.7.110.102]) by mail.disney.com (Switch-2.0.1/Switch-2.0.1) with SMTP id f86Ga9e13751 for ; Thu, 6 Sep 2001 09:36:09 -0700 (PDT) Received: from [172.30.50.1] by hermes.corp.disney.com with ESMTP for freebsd-alpha@FreeBSD.ORG; Thu, 6 Sep 2001 09:36:06 -0700 Received: from plio.fan.fa.disney.com (plio.fan.fa.disney.com [153.7.118.2]) by pecos.fa.disney.com (8.11.3/8.11.3) with ESMTP id f86Gk5s13189 for ; Thu, 6 Sep 2001 09:46:05 -0700 (PDT) Received: from mercury.fan.fa.disney.com (mercury.fan.fa.disney.com [153.7.119.1]) by plio.fan.fa.disney.com (8.9.2/8.9.2) with ESMTP id JAA10682 for ; Thu, 6 Sep 2001 09:37:05 -0700 (PDT) (envelope-from Jim.Pirzyk@disney.com) Received: from [172.30.228.110] by mercury.fan.fa.disney.com; Thu, 6 Sep 2001 09:37:05 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Jim Pirzyk Organization: Walt Disney Feature Animation To: Andrew Gallatin Subject: Re: XFree86-4 and alpha DS10 Date: Thu, 6 Sep 2001 09:37:00 -0700 X-Mailer: KMail [version 1.3] Cc: Wilko Bulte , freebsd-alpha@FreeBSD.ORG References: <15254.55412.456276.744140@grasshopper.cs.duke.edu> In-Reply-To: <15254.55412.456276.744140@grasshopper.cs.duke.edu> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: 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 On Wednesday 05 September 2001 06:59 pm, Andrew Gallatin wrote: > 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. So I took a ELSA Gloria-8 card from a DS20e and put it into this DS10. The 'show bios' at the SRM prompt now shows this card, but I still do not get a PCI mem range on bootup, I still get both these messages: pci0: at device 17.0 (no driver attached) and in XFree86.0.log (--) PCI:*(0:17:0) Texas Instruments Permedia 2 rev 1, Mem @ 0x02080000/17, 0x01000000/23, 0x01800000/23, BIOS @ 0x020b0000/16 (WW) ****INVALID MEM ALLOCATION**** b: 0x2080000 e: 0x209ffff correcting^G - JimP -- --- @(#) $Id: dot.signature,v 1.10 2001/05/17 23:38:49 Jim.Pirzyk Exp $ __o Jim.Pirzyk@disney.com ------------- pirzyk@freebsd.org _'\<,_ Senior Systems Engineer, Walt Disney Feature Animation (*)/ (*) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message