Linked by paolone on Fri 4th Jan 2013 20:56 UTC
Thread beginning with comment 547924
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2008-08-28
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.