WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: text font too small to see on AppBrowser and Aterm  (Read 8769 times)

Offline rbacher

  • Newbie
  • *
  • Posts: 23
Re: text font too small to see on AppBrowser and Aterm
« Reply #15 on: January 11, 2011, 10:45:11 PM »
[removed 6]

Yes, indeed. I have several posts there. Mavrothal was great helping me to solve other issues with installing a minimalistic microcore onto an olpc XO computer. I previously installed the Tinycore versions he has there, but I wanted (and I now have) an even more minimalistic OS. Quite possibly Tinycore has some way to make the fonts bigger, however I am running Quozl's microcore for the XO. Boot time from a cold boot is 24 sec (on a dinky powered XO)!  I will try the other ideas you wrote. There has to be a way to do this. I have succeeded in making all of the other fonts larger and perfectly readable. It's just the "system" fonts (cpanel, appbrowser, etc) that remain microscopically small
« Last Edit: January 12, 2011, 01:09:43 AM by ^thehatsrule^ »

Offline maro

  • Hero Member
  • *****
  • Posts: 1228
Re: text font too small to see on AppBrowser and Aterm
« Reply #16 on: January 12, 2011, 01:32:00 AM »
So it appears that some "special" boot loader has some influence on the outcome, I just wonder what the result of cat /proc/cmdline might be.

Offline rbacher

  • Newbie
  • *
  • Posts: 23
Re: text font too small to see on AppBrowser and Aterm
« Reply #17 on: January 12, 2011, 09:47:18 PM »
So it appears that some "special" boot loader has some influence on the outcome, I just wonder what the result of cat /proc/cmdline might be.

no_console_suspend selinux=0 fbcon=font:SUN12x22 quiet norestore tz=EST+5 home=LABEL=sd tce=LABEL=sd opt=LABEL=sd

Does this help any in figuring out how to make the system fonts bigger or the resolution smaller?

Offline rbacher

  • Newbie
  • *
  • Posts: 23
Re: text font too small to see on AppBrowser and Aterm
« Reply #18 on: January 12, 2011, 10:16:07 PM »
I tried:

sudo xfbdev -screen 800x600x24 && export DISPLAY=:0.0 || echo Failed
startx

The result was the same as when I do $ Xfbdev.
What I get is a gray and black cross hatching with an X instead of a mouse arrow. When I go back to the CLI by pressing alt-cntrl-del, I see the following line:

$ Could not init font path element /usr/lib/X11/fonts/100dpi, removing from list!

Under /usr/lib/X11/fonts/ I have 75dpi and misc but not 100dpi.

Offline maro

  • Hero Member
  • *****
  • Posts: 1228
Re: text font too small to see on AppBrowser and Aterm
« Reply #19 on: January 13, 2011, 03:40:09 AM »
no_console_suspend selinux=0 fbcon=font:SUN12x22 quiet norestore tz=EST+5 home=LABEL=sd tce=LABEL=sd opt=LABEL=sd

Does this help any in figuring out how to make the system fonts bigger or the resolution smaller?

Maybe not directly, I just wanted to be sure what boot codes are getting passed to the kernel. I assume all the ones after 'quiet' are your own. But where is the 'vga=...', and are the first three also specified by yourself? This must be a rather "special" setup ...

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: text font too small to see on AppBrowser and Aterm
« Reply #20 on: January 13, 2011, 03:47:10 AM »
FWIW, you can find the boot options for fbcon here:

http://www.mjmwired.net/kernel/Documentation/fb/fbcon.txt
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: text font too small to see on AppBrowser and Aterm
« Reply #21 on: January 13, 2011, 03:52:03 AM »
Maybe not directly, I just wanted to be sure what boot codes are getting passed to the kernel. I assume all the ones after 'quiet' are your own. But where is the 'vga=...', and are the first three also specified by yourself? This must be a rather "special" setup ...

What puzzles me most is the 'selinux=0' part...   ::)
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: text font too small to see on AppBrowser and Aterm
« Reply #22 on: January 13, 2011, 04:01:10 AM »
Under /usr/lib/X11/fonts/ I have 75dpi and misc but not 100dpi.

FWIW, same here   ;)
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline rbacher

  • Newbie
  • *
  • Posts: 23
Re: text font too small to see on AppBrowser and Aterm
« Reply #23 on: January 13, 2011, 10:09:40 AM »

Maybe not directly, I just wanted to be sure what boot codes are getting passed to the kernel. I assume all the ones after 'quiet' are your own. But where is the 'vga=...', and are the first three also specified by yourself? This must be a rather "special" setup ...

Yes, it's a special set up. Not sure what I am allowed to write about it. Some previous text I wrote was deleted per Rule 6 (which I then looked up, it says "6. No specific remasters/remixes releases or discussion"). Not sure why that's a rule but I am not here to make any trouble, only to look for help.

I have an olpc XO computer. It comes with a child like OS named Sugar. You can't just replace it with another OS like you can on a "normal" computer, there's something different in the hardware. There are a few OS's out there specially written for the XO by people who know how to do it. A popular one is Ubuntu adapted for the XO. I ran that for awhile however I wanted a smaller OS. That's because the XO computer is very low powered, small ram, slow processing speed, etc. So my novice wanderings led me to Tinycore, and then to Microcore. Microcore is a perfect fit for the XO computer. But you can't just put microcore "as is" onto an XO computer. It has to be modified in ways beyond my ability. Fortunately there is such a modified version out there written by someone named Quozl. I installed it and it runs perfectly. My only problem is the tiny system fonts.

The boot codes after "quiet" are required by the XO computer. There is currently no "vga=" because it does nothing. Originally it came as "vga=788".  At the suggestion of a message I received (I think in this thread) I changed it to "vga=785" and I tried some other numbers. This idea was based on the fact that I run Xfbdev and, it was explained to me, the frame buffer is made bigger or smaller by the "vga=" setting. But that's not what happens on an XO with the OS that I have. The "vga=" does nothing. It's just not there now because I made 5 or 6 changes to it, to see what would happen, and the last change was simply to take it out altogether.

Finally, sorry for the long post, and thanks to those who have tried (are trying) to help me. This may be an unsolvable condition due to installing a modified microcore onto a computer that has unusual hardware.

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: text font too small to see on AppBrowser and Aterm
« Reply #24 on: January 13, 2011, 11:12:36 AM »
If vga=ask doesn't bring up any prompt with a choice, it is unlikely that setting any other value would do anything.

it does not make much sense to speculate about a kernel which is obviously very different from the TC stock kernel without seeing its config, but as you seem to use a fbcon kernel parameter, perhaps you might do trial and error with other fbcon parameters, as per the manual.
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline rbacher

  • Newbie
  • *
  • Posts: 23
Re: text font too small to see on AppBrowser and Aterm
« Reply #25 on: January 13, 2011, 04:00:01 PM »
I tried vga=ask along with several other combinations (vga=785, vga=text-mode, and others) just trying by hit and miss to get the screen to show up different in some respect. The vga=ask did not bring up a prompt, and no combination did anything different. I can only conclude that "vga=" does nothing in my set up

I agree that it makes no sense to speculate about this. I don't want to waste anyone's time. In other situations I have gotten excellent answers on forums like this one. It's hard for me to know when I will get an answer that works and when I won't. I grew up with Windows and only recently tried to do things with Linux. It can be incredibly frustrating, I feel like I am stumbling around in the dark much of the time.

I will try some different combinations with the fbcon parameter tonight. As always, thanks for trying to help me.