Date: Mon, 9 Aug 1999 08:33:18 +0200 (CEST) From: Soren Schmidt <sos@freebsd.dk> To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Cc: cejkar@dcse.fee.vutbr.cz, freebsd-current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: VESA module doesn't work with ATI Mach64 RagePro Message-ID: <199908090633.IAA51602@freebsd.dk> In-Reply-To: <199908090348.MAA25802@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Aug 9, 1999 12:48:15 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
It seems Kazutaka YOKOTA wrote: > > >I have switched graphics card from S3Virge to ATI Mach64 RagePro rev 92 > >with 8 MB RAM a I have noticed that VESA module doesn't work with this > >graphics card on my -current box - I can't use VESA_XXX console modes now. > >Command kldstat says there is loaded module vesa.ko. No errors are > >reported when I'm trying to unload/load vesa.ko module. Kernel reports > >during boot: > > > >VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc024f622 (1000022) > >VESA: ATI MACH64 > > > >Command "vidcontrol -i mode" reports lines below. It looks VESA module > >can't read mode table properly. But simple VESA utilities in DOS are capable > >to determine all VESA modes supported by ATI Mach64 card with VESA 2.0 BIOS. > >Is this known problem? Or should I invetigate this problem further? > > There is a good possibility that the VESA BIOS extension for this card > is provided in a DOS TSR program and the VESA BIOS entry in the ROM > BIOS is just a stub. Such implementation is allowed in the VESA spec. Actually its because the ATI chip reports the modes as non-VGA modes, which is correct (sortof), and our VESA code rejects those modeentries. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199908090633.IAA51602>