I have a revB i-mac on which I installed Yellow Dog 4.0. The install went f=
ine. I decided to run the i-mac as a linux appliance so I did not need the =
monitor. I already have a spare monitor sitting around for other servers so=
I soldered together a 15pin macintosh video to VGA converter cable to use.=
After plugging in the monitor, it displayed fine during the BIOS start-up,=
and through the bootloader. and even the beginning of the kernel load. Ho=
wever, once tux appeared in the top left corner of the screen, the monitor =
displayed 4 columns, with succesive rows in successive columns.=0A=0AI play=
ed around with the XF86Config and was able to get X windows displaying perf=
ectly with the following stanza: =0A=0ASection "Monitor" =0A=0A# Disp=
laySize 270 200 =0A# HorizSync 60.0 - 60.0 =0A# Vert=
Refresh 75.0 - 117.0 =0A Identifier "Monitor0" =0A ModelNa=
me "Acer" =0A HorizSync 28.0 - 50.0 =0A VertRefresh 56=
.0 - 76.0 =0A Option "DPMS" =0AEndSection=0A=0Anow the only thi=
ng that does not display correctly is the console. Does anyone know where t=
he file is, or what must be done to tell the kernel or framebuffer how to i=
nteract with the monitor in the way that X uses the XF86Config file? I've =
posted this question to several message board with no response and can't fi=
nd anything on the web, so I'm going to the framebuffer experts now.=0A=0AT=
hanks, =0AKevin Nowaczyk=0A=0A=0A =0A______________________________________=
______________________________________________=0AHave a burning question? =
=0AGo to www.Answers.yahoo.com and get answers from real people who know.
|
