There shoudln’t be nothing to change there, unless you have a GMA chip onboard, and then you can add some graphical memory with the tooltype GMA_MEM. The description of the devices, allowing IcAROS to handle them are in sys:Devs/Monitors If you are in Native mode, just simply use Prefs / Screenmode : To switch from native to vesa / vesa to native, use the prefs/boot interface. I personnally get more “memory access violation” errors with native mode. You can get some weird behaviors (icons that disapear…), if you have your graphic card recognized but not in the compatibility list. If your card is recognized and handled by AROS, it is the best choice.īut it is also more complex for the system to handle, so, it is also more unstable. You can change the graphical mode without having to reboot the machine. To know the list of VESA modes supported by the graphic card, on the grub screen type “c” to get into the “grub command line”, then type : vbeinfo NATIVE : For more informations about VESA : īut it is slow, and Warp 3D is badly supported.Īlso, you can have problems changing graphical modes (need to restart the comp’), or even finding a mode that fits your needs and your screen (for me, I had issues with my wide 22′ monitor)
VESA is perfect for compatibility with ALL the gfx cards.
0 kommentar(er)
