Caps Lock issue

[Juanito]

   SubSection "Display"
      Viewport   0 0
      Depth     16
      Modes "1280x1024_60.00"
   EndSubSection
EndSection

Modes "1280x1024_60" should probably be Modes "1280x1024"

I couldn't save that file in /etc/x11 as it was keep disappearing after reboot so i have placed it in /home/tc instead and changed the path in /opt/.filetool.lst respectively. Am i doing something wrong saving files in /etc folder?

You need root (admin) privileges to save files in /etc/X11, once saved you can add "etc/X11/xorg.conf" to filetool.lst

[fuegos]

I have tried that and X doesn't start at all now. After reboot /etc/x11/xorg.conf disappeared same as entry in /opt/.filetool.lst

This time i had a look at xorg log. I suspect video driver problem. Please follow the link to view log

http://pastebin.com/mae7iuDa

Any chance to find any walkaround for that?

[curaga]

It crashed in unichrome, and says it didn't find the config file.

Please make the file persistent first, sounds like you didn't make a backup before rebooting.

[fuegos]

As far as i understand i create backup running command: filetool.sh -b ?

[curaga]

Yes.

[fuegos]

/etc/X11/xorg.conf is now persistent and looks as follows (default setting):

Section "ServerLayout"
   Identifier     "X.org Configured"
   Screen      0  "Screen0" 0 0
   InputDevice    "Mouse0" "CorePointer"
   InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
   ModulePath   "/usr/local/lib/X11/modules"
   FontPath     "/usr/local/lib/X11/fonts/misc/"
   FontPath     "/usr/local/lib/X11/fonts/TTF/"
   FontPath     "/usr/local/lib/X11/fonts/OTF"
   FontPath     "/usr/local/lib/X11/fonts/Type1/"
   FontPath     "/usr/local/lib/X11/fonts/75dpi/"
EndSection

Section "Module"
   Load  "glx"
   Load  "dri"
   Load  "extmod"
   Load  "dbe"
   Load  "freetype"
EndSection

Section "InputDevice"
   Identifier  "Keyboard0"
   Driver      "kbd"
EndSection

Section "InputDevice"
   Identifier  "Mouse0"
   Driver      "mouse"
   Option       "Protocol" "auto"
   Option       "Device" "/dev/input/mice"
   Option       "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
   Identifier   "Monitor0"
   Option       "DPMS"
EndSection

Section "Device"
   Identifier  "Card0"
   Driver      "vesa"
EndSection

Section "Screen"
   Identifier "Screen0"
   Device     "Card0"
   Monitor    "Monitor0"
   DefaultDepth 24

   SubSection "Display"
      Viewport   0 0
      Depth     16
   EndSubSection
   SubSection "Display"
      Viewport   0 0
      Depth     24
   EndSubSection
EndSection

Startx causes monitor to go sleep and thin client crashes before Xorg log is created... It must be matter of configuration don't you think so?

[curaga]

Can't tell what it could be. Perhaps try with "fbdev" instead of vesa.

[tinypoodle]

You could try to symlink /var/log to a persistent storage medium and start syslogd before running startx in the hope to catch some info from both Xorg.log and syslog.

[Juanito]

Ref:

Code: [Select]

(--) UNICHROME(0): CRT: Attached!
(II) UNICHROME(0):
(II) UNICHROME(0): Listing CRTC to Output Mapping:
(II) UNICHROME(0):
(II) UNICHROME(0):   CRTC 1:
(II) UNICHROME(0):       Output CRT on Bus CRT.
(II) UNICHROME(0):
(II) UNICHROME(0):   CRTC 2: Disabled
Do you need to set the screen output device to CRTC or CRTC 1 in your xorg.conf maybe?

[fuegos]

Loading fbdev driver solved the problem. Now I got X in full res and screen is detected correctly i only can't change resolution to 1024x768 which is required by some 'blind' users. Help! That's not a big problem but i think you may know the aswer to it.

I have also managed to retrieve Xorg log file when unichrome driver is loaded:
http://pastebin.com/aJ68RLA9

xorg.conf file i have used for unichrome is here:
http://pastebin.com/5712vzd9

I thought you may want to look at them and suggest something...


Big thanks for Curaga for very accurate diagnosis  and all kind people who helped me trace the problem

As I'm new to Linux i will have more and more questions. More enough to hate me 

[tinypoodle]

An X server making use of framebuffer will always use the mode of preexisting framebuffer.

Your log does not seem to justify/explain a system crash.

[curaga]

The fbdev driver uses the existing resolution - the one you set with the vga=794 boot param. It can't change the resolution at runtime, unfortunately.

edit: Tinypoodle beat me.

[fuegos]

All tested and works as intended. Many thanks for all the help.

One more thing... I got few Wyse S30 terminals but internal flash memory is not visible once TC is loaded. Someone started similar topic here http://forum.tinycorelinux.net/index.php?topic=11622.0 but solution never been posted or explained... Anyone would like to take a challenge and clear this out?