Tiny Core Base > TCB Q&A Forum
text font too small to see on AppBrowser and Aterm
rbacher:
Changing vga= didn't work. The boot code was set to vga=788. I changed it to 785 but the screen resolution stayed the same. I tried a couple of other numers. No change. I tried vga=text-mode which the faq says "can't run at all" but it ran fine. Something else is controlling my screen resolution. I suspect it is because I have an olpc XO computer. They are very different somehow. I don't run (because I can't) tinycore out of the box. I have some modified version specially adapted for the XO. It's a neat little computer, very sturdy and great for travelling, and I have everything humming on it except for these teensy size fonts on the tinycore utilities (cpanel, appbrowser, etc).
rbacher:
If it helps anyone understand my situation, so they can maybe help me to make my system fonts larger (or screen resolution smaller), the version of Tinycore (it's actually microcore) l run was specially created for the XO computer [removed, see rule/guideline 6]
When the XO boots, it gets the Tinycore boot codes (and other boot files) from a file unique to the XO named "olpc.fth". Without that file the XO won't boot. Other boot codes needed for Tinycore are there (such as tce=). Yet vga= seems to have no effect on my screen resolution.
tinypoodle:
And what happens if you boot with 'vga=ask' (see Reply #8!)?
moB:
rbacher,
yeah, I see...
It seems you might try starting TC in CLI (no GUI), then:
--- Code: ---sudo xfbdev -screen 800x600x24 && export DISPLAY=:0.0 || echo Failed
startx
--- End code ---
(nb. && means run second command if first one works, that is returns a zero.
|| means if not success... so don't say "startx".)
I found these links below:
Best results come with persistence.
moB
I protested my innocence of these things
--Melville, Moby Dick
[removed, see rule/guideline 6]
Do they all work the same way?
You are not the only one...
<snip>
You'll see that the fonts are pretty small in the apps. Should be some
way to increase them altogether adjusting the dpi but I could not find
anything easily. If you know the trick for tinycore running in Xfbdev,
please let us know.
</snip>
[removed 6]
<snip>
Try to see if from the console (press ctrl+alt+del) either of these
commands will execute w/o errors and get you to the desktop when you
enter it as sudo.
Code:
Xfbdev -dpi 200 -mouse /dev/input/mice,5 &
export DISPLAY=:0.0
# and/or
Xfbdev -screen 1200x900x16 -mouse /dev/input/mice,5 &
export DISPLAY=:0.0
startx
change the -dpi value to something smaller (150) and/or the -screen
option in the second case. See how it goes. I'm not sure that the
framebuffer can support different resolutions on the XO but try it just
the same.
</snip>
Xfbdev manual:
http://www.xfree86.org/current/Xfbdev.1.html
TinyX:
This incarnation of TinyX is colloquially known as kdrive.
Xfbdev [:display] [option...]
-screen widthxheight[xdepth[xfreq]][@rotation]
Use a screen of the specified width, height, screen depth,
frequency, and rotation (0, 90, 180 and 270 are legal values).
====
Edit:
--- Code: ---sudo xfbdev -screen 800x600x24 && sudo export DISPLAY=:0.0 && startx || echo Failed
--- End code ---
The manual says to make both screen commands as "sudo".
rbacher:
--- Quote from: tinypoodle on January 11, 2011, 09:21:41 PM ---And what happens if you boot with 'vga=ask' (see Reply #8!)?
--- End quote ---
Nothing different happens. I already tried it It is clear that vga= in the boot code on the system I have makes no difference. I just now took it out altogether. There's no vga= anything in my boot code and it makes no diference one way or the other. Something else is going on.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version