Xorg and touchscreen

[maro]

I believe the X server configuration is controlled by '/usr/bin/xsetup.sh'. This contains the line XCOMMAND="$XSERVER -nolisten tcp &" (which controls the 'Xorg' parameters). Adding your option to that line should do the trick.

For the problem to ensure persistence I see two ways:

• via backup (e.g. echo 'usr/bin/xsetup.sh' >> /opt/.filetool.lst && /etc/init.d/tc-restore.sh backup), or
• via remastering of the initrd (see the Wiki)

Whether the first option will work depends on the timely restoration of the changed file from the backup. I believe that 'xsetup.sh' gets called "late" enough during start-up so that it should work. If my assumption is wrong you still have the second option, which is sure to succeed.

[asclepix]

I've modified xsetup.sh and it create a ~/.xsession with "/usr/local/bin/Xorg -retro -nolisten tcp &".
However if I launch startx I obtain a black screen and it is not possible to give more command (even CAPS LOCK doesn't turn on/off the relative keyboard led...)

Even if I launch only .xsession I obtain the black screen. On the other side, the only "/usr/local/bin/Xorg -retro -nolisten tcp &" from prompt works.

[asclepix]

I suppose the problem is that I run out of memory. Is it possible?

In fact if I launch manually Xorg, then flwm_topside, then wbar, when I try to set a background Linux kill Xorg because there is no free memory.

If I don't set a background, but use aterm, the system freezes itself.

[curaga]

How much ram is there? Any swap?

[asclepix]

I've got 128MB of RAM.
On boot 58MB is free. So I've decided for no swap.
After I install Xorg and its dependeces I've got only 9MB free 

How can I save RAM? Hybrid mode? If I understand correctly, this mode will not mount file in a loopback file and so I save RAM, is it right?

Other solutions?

[curaga]

If you're going with no swap, the 3.x series is better at that due to ramzswap. Otherwise, yeah PPI would help.

[asclepix]

I've tried to boot with local=hda2.
It seems great. When I load Xorg, TC put it on my disk, and I save RAM.

However, when I launch Xorg, it returns immediately, with no output neither a /var/log/Xorg.0.log file

[asclepix]

I suppose that not all the components of Xorg go in /usr/local.

Which is the right way to use PPI? where can I find documentation?

Thanks

[curaga]

Docs on PPI/hybrid mode are a bit scarce. Core Concepts is the main doc.

startx filters errors out, anything if you launch Xorg manually?

[asclepix]

There's no message if I launch Xorg manually

[asclepix]

As you can guess I've got low hardware resources. My HD is in fact a Disk OnModule of 64 MB. When I install Xorg with "tce-load -i Xorg-7.4" I have a "Xorg-7.4.tcz: OK".
If I do a ll of /usr/local/bin then I see that I have a lot of file with 0 byte length.

So, now I'll try to find a DOM of 256 MB.

[curaga]

I think it would be cheaper to use the normal tcz mode, and double the ram.

[asclepix]

I don't know, but I have problem to find RAM while we have some 256MB DOM.

Now I've rebuilt everything with such a DOM. I have not understood why, but I have more free memory.

I've installed input-2.6.29.1-tinycore and Xorg-7.4 manually (before input-2.6.29.1-tinycore was installed on boot).
I have enough memory for run Xorg -retro (manually, not with startx), flwm_topside, wbar and setting a little image as background.

Then I've seen I have more than 40MB of free RAM, so I've installed xvkbd and qt-3.3.8b, because my software need that library. I am now able to test my software with touchscreen 

Ok, When I poweroff the machine every go away, but I now know it can work. I'll make it working automatically.

Thank you for your support.

Do you know why I have so many more free memory changing only the DOM?

[curaga]

No, no idea