tiny core linux tft display quotation

5. Copy all matching .ko entries from tmp/core to the same directory structure in tmp/tft/squashfs-root, deleting the matching .ko.gz entries - I used xfe for this

Those who are running TinyCore versions using the default fltk/flwm environment and find the supporting applications too small on modern high-res screens.

Keep track of which DISPLAY is set when issuing commands. FLWM will only work on one display (presumably the HDMI) and will not allow itself to have more than one instance running, so your app will need to need to handle the graphics on the others.

To answer your question about this option and where it goes: it must be on the boot prompt. Either typed ***without quotes*** or later added in the "extlinux.conf" file on the "append" line, inside the section you"re using to start TC. ( "append" line comes after "linux/kernel" and "initrd" lines).

I had to reinstall TC in the same laptop and having difficulty with getting the 1280x800 resolution, Before when was working correctly I didn"t need to setup .xsession file. My extlinux.conf file is below, this doesn"t work (doesn"t retain the resolution), although on exit to command line and 915resolution 50 1280 800 24 followed by startx DOES with display correct resolution. After backup and reboot the 1280x800 resolution is lost. Does the extlinux.conf file look OK?

Stuck the card in the display, powered it up, and it loaded.  Pulled the card out, verified all connections to the raduino were correct, and fired up the rig.  So far, everything seems to be working correctly.  I have not tested the QRT code backup yet, but band switching, tuning, etc. are all doing as expected.

I should have specified what OS I am on.  I have Win 10 on my main machines, and I do have an old laptop with XP I keep (completely offline) for legacy needs.  There are also a couple of Linux machines in the shop for CNC usage as well.

I can compile in the LTS version of the editor, and after formatting a card, transfer the .tft file.  When I put it in the display, it does the countdown to firmware load, then gives me the "File Version too low message," even with the LTS compiled version.

This evening, I am going to "back up and punt," by grabbing an Arduino Uno out of the stash and going through a simple tutorial on the display.  Hopefully, I"ll be able to isolate/eliminate the display as a potential source of my problem.  I realize the display is likely fine, given the demo Nextion preloads functioned fine, but at this point I don"t have anything to lose.

With the above, that still does not explain what is happening when you transfer the ubitx_28.tft to the microSD card.  I would reformat the microSD card with

I would verify that the device selected is the same as the device you are trying to transfer the file.  After you load the .HMI file there should be a gear with the tag Device ID.  Check it and then select the Nextion display that matches your device.