Date: Wed, 5 Sep 2001 21:59:16 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Jim Pirzyk <Jim.Pirzyk@disney.com> Cc: Wilko Bulte <wkb@freebie.xs4all.nl>, freebsd-alpha@FreeBSD.ORG Subject: Re: XFree86-4 and alpha DS10 Message-ID: <15254.55412.456276.744140@grasshopper.cs.duke.edu> In-Reply-To: <iss.57a5.3b96cba1.1fffb.1@mercury.fan.fa.disney.com> References: <iss.430a.3b90248d.64c9f.1@mercury.fan.fa.disney.com> <20010903211740.A1329@freebie.xs4all.nl> <iss.57a5.3b96cba1.1fffb.1@mercury.fan.fa.disney.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15254.55412.456276.744140>