Date: Sun, 27 Jul 2003 21:42:35 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: grog@FreeBSD.org Cc: freebsd-mobile@FreeBSD.org Subject: Re: Mapping Video BIOS? Message-ID: <20030727.214235.20045695.imp@bsdimp.com> In-Reply-To: <20030728032653.GA37499@wantadilla.lemis.com> References: <20030727015903.GJ45069@wantadilla.lemis.com> <20030726.221859.122847811.imp@bsdimp.com> <20030728032653.GA37499@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20030728032653.GA37499@wantadilla.lemis.com>
"Greg 'groggy' Lehey" <grog@FreeBSD.org> writes:
: 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.
Hmmmm, The list comes from scanning the "ISA HOLE" for certain memory
signatures. These signatures have a length in them that say "I'm a
rom that's X long". I don't think that it suggests that things are
'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?
I don't, I'm sorry.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030727.214235.20045695.imp>