>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.
Please examine the manual of the video card for information.
Kazu
> mode# flags type size font window linear buffer
>------------------------------------------------------------------------------
> 0 (0x000) 0x00000001 T 40x25 8x8 0xb8000 32k 32k 0x00000000 32k
[...]
> 45 (0x02d) 0x00000000 T 90x43 8x8 0xb8000 32k 32k 0x00000000 32k
> 46 (0x02e) 0x00000001 T 90x50 8x8 0xb8000 32k 32k 0x00000000 32k
> 48 (0x030) 0x00000001 T 90x60 8x8 0xb8000 32k 32k 0x00000000 32k
>112 (0x070) 0x00000000 T 80x43 8x8 0xb8000 32k 32k 0x00000000 32k
>113 (0x071) 0x00000001 T 80x43 8x8 0xb8000 32k 32k 0x00000000 32k
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
