Linked by paolone on Fri 4th Jan 2013 20:56 UTC
Amiga & AROS Icaros Desktop, the popular distribution of the AROS Research Operating System, has recently released its version 1.5, a new milestone since it finally allows to run classic Amiga software and games on full screen or perfectly integrating them into the host AROS desktop.
Thread beginning with comment 547911
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[8]: Comment by lucas_maximus
by paolone on Wed 9th Jan 2013 10:43 UTC in reply to "RE[7]: Comment by lucas_maximus"
Member since:

No, it didn't change anything - but your suggestion made me compare all the boot config lines. Yes, when disabling DMA, I was able to run 3rd "mode" as well - still: the graphics remained as ugly, as in 4th one.

Well, the 1st mode runs the VESA driver and then native ones, looking for a supported card. If none is found, it fallbacks to VESA mode, which should at least run in a 800x600 or 1024x768, 16M colors screen. In some cases it may fall back to VGA mode, with its ugly 640x480, 16 color mode, which is, indeed the last boot line mode.

If you got the VGA mode even with the 3rd line, which does NOT include it, it means you may have a video card which does not support VESA standards (rare), or that you made some mistakes with the VESA= parameter in the boot lines, before continuing boot.

please notice some test cases

VESA=32bit --> tries to choose the best fitting resolution for your screen based in EDID values taken from monitor, with a 16 million color palette.

VESA=1024x768x16 --> opens a 1024x768, 65536 colors screen, independentely from EDID informations

VESA=1024x768@60 ---> opens a 1024x768 screen, with as much colors as it can, at a 60Hz frequency. Some monitors may need @70, @75 or @59 to avoid displaying the "unsupported frequency" error (which is Monitor one, nor AROS').

you can try combinations like VESA=32bit@60 AFAIK. Icaros manual also explains how to see what VESA resolutions your video card actually support, which is doable within GRUB itself.

Reply Parent Score: 1

Zbigniew Member since:

Well, if I'm correct, Icaros (or AROS) during boot time uses framebuffer for diplaying text boot messages.

I made a third attempt using older hardware - apart of the problems with the framebuffer (still "mode not supported") it booted just fine, and I could play a bit, when graphics appeared. It was much older mobo ASRock K7-Upgrade600, with Radeon 9600Pro.

The conclusions are:
- at the moment new AROS kernel has poor support for nForce chipset
- it would be much better idea to use - for displaying text boot messages - the modes e.g. "copied" from Linux (say: the ones LILO allows). Never had problems with these. It's simply not worthy to pack a few letters more into line at a cost of making most monitors unsuitable.

Reply Parent Score: 1