Tiny Core Linux
Tiny Core Base => TCB Bugs => Topic started by: ibug on February 03, 2012, 10:44:11 PM
-
in TC-4.2.1 with vga=786 kernel option
do not start in 640x480x24
it startx 1024x768 exactly like without vga=786
and xsetup kernel option works ok
-
The vga=option sets the vesa mode used by console.
-
You'll need to use the 'Xfbdev' X server from the 'Xfbdev.tcz' extension to make use of any 'vga=...' boot code. If said X server is installed at the time of the 'startx' execution it will replace the default X server (i.e. 'Xvesa') and use the resolution and colour depth you specified via the 'vga=...' boot code. As you found out, the 'vga=...' boot code has no influence on the 'Xvesa' X server.
IMHO using the 'Xfbdev' X server makes only sense if your hardware does not work at all with 'Xvesa'. If OTOH your system is fine with 'Xvesa' but you want it to start with a resolution other than the default (which is 1024x768x32), then you should use a boot code like 'xvesa=640x480x24' instead.
Of course you should first check that 'Xvesa' supports your target resolution, which you could do by running Xvesa -listmodes
-
xvesa=640x480x**
and it is on blank TC-4.2.1
without Xfbdev.tcz
-
For proper Xvesa setup use, from text mode use xsetup or from control panel Xvesa button.
-
yes xsetup works
but why both kernel option
xvesa=640x480x**
vga=786
do not work
and xsetup force mouse config
take time if mistake
-
I already told you why vga= does not work.
What made you think xvesa=640x480x** would work?