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.