--doKZ0ri6bHmN2Q5y
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jun 28, 2004 at 06:31:11PM -0400, Steven M. Bellovin wrote:
> In message <20040628221600.GD21541@netbsd.org>, Bill Studenmund writes:
> >
> >Sorry I know so little about this as to be no more help..
> >
>=20
> Well, that's my problem, too -- I do *not* understand much of the X=20
> structure.  But I did look around before I posted.
>=20
> Grep tells me that the "read failed" message is coming from=20
> vbe/vbe.c.  It, in turn, is calling xf86ExecX86int10, which is calling=20
> the BIOS, I believe.  I *really* don't know how to put printfs there...
> (There is an option to disable int10 processing; selecting it produces=20
> "VBE Initialization failed".)

Sounds like our BIOS code is messed up, or you need some kernel option to=
=20
enable it..

Take care,

Bill

--doKZ0ri6bHmN2Q5y
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFA4J/MWz+3JHUci9cRAgZfAKCWOqcojWGgRXtOZVkYBB6Tlhoq/ACfZ+d7
12XhGwkNQ1WrZOKQzp/3/qM=
=UMvo
-----END PGP SIGNATURE-----

--doKZ0ri6bHmN2Q5y--