Date: Mon, 28 Jul 2003 12:56:53 +0930 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-mobile@FreeBSD.org Subject: Re: Mapping Video BIOS? Message-ID: <20030728032653.GA37499@wantadilla.lemis.com> In-Reply-To: <20030726.221859.122847811.imp@bsdimp.com> References: <20030727010938.GF45069@wantadilla.lemis.com> <20030726.194750.28168388.imp@bsdimp.com> <20030727015903.GJ45069@wantadilla.lemis.com> <20030726.221859.122847811.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Saturday, 26 July 2003 at 22:18:59 -0600, M. Warner Losh wrote: > In message: <20030727015903.GJ45069@wantadilla.lemis.com> > "Greg 'groggy' Lehey" <grog@FreeBSD.org> writes: >> Presuming that it's the ROM driver, I get this in the dmesg I posted: >> pnpbios: Bad PnP BIOS data checksum > > That's likely the problem. However, PnP BIOS information isn't the > same thing that the orm[sic] driver probes for. They look related. I've now found the orm output: orm0: <Option ROMs> at iomem 0xe0000-0xe3fff,0xdf800-0xdffff,0xd0000-0xd17ff,0xc0000-0xcefff on isa0 The last one is the video BIOS. It's interesting to note that it doesn't report the 4 kB BIOS at 0xcf000, which suggests that at this point the 16 kB area is already unmapped. I've worked around the problem by compiling the video BIOS into the X server and not trying to access the BIOS in the machine. Obviously not a solution, but it works for the moment. I'd really like to track down the problem. Does anybody have an idea? Greg -- See complete headers for address and phone numbers [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE/JJf9IubykFB6QiMRApF3AJ9TjhIMp9EmoimeaZfsxHQroCB4kACfSBL1 qV+jC8b0T2wpEiuWi+XkQiI= =O/fs -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030728032653.GA37499>