WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Caps Lock issue  (Read 5322 times)

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11068
Re: Caps Lock issue
« Reply #15 on: November 08, 2012, 05:44:43 AM »
   SubSection "Display"
      Viewport   0 0
      Depth     16
      Modes "1280x1024_60.00"
   EndSubSection
EndSection

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

Quote
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
« Last Edit: November 08, 2012, 05:47:36 AM by Juanito »

Offline fuegos

  • WikiUser
  • *
  • Posts: 24
Re: Caps Lock issue
« Reply #16 on: November 08, 2012, 06:49:28 AM »
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?

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10050
Re: Caps Lock issue
« Reply #17 on: November 08, 2012, 06:59:18 AM »
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.
The only barriers that can stop you are the ones you create yourself.

Offline fuegos

  • WikiUser
  • *
  • Posts: 24
Re: Caps Lock issue
« Reply #18 on: November 08, 2012, 07:12:46 AM »
As far as i understand i create backup running command: filetool.sh -b ?

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10050
Re: Caps Lock issue
« Reply #19 on: November 08, 2012, 07:25:42 AM »
Yes.
The only barriers that can stop you are the ones you create yourself.

Offline fuegos

  • WikiUser
  • *
  • Posts: 24
Re: Caps Lock issue
« Reply #20 on: November 08, 2012, 07:48:43 AM »
/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?

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10050
Re: Caps Lock issue
« Reply #21 on: November 08, 2012, 09:47:16 AM »
Can't tell what it could be. Perhaps try with "fbdev" instead of vesa.
The only barriers that can stop you are the ones you create yourself.

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: Caps Lock issue
« Reply #22 on: November 08, 2012, 12:17:47 PM »
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.
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11068
Re: Caps Lock issue
« Reply #23 on: November 08, 2012, 12:19:46 PM »
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?

Offline fuegos

  • WikiUser
  • *
  • Posts: 24
Re: Caps Lock issue
« Reply #24 on: November 09, 2012, 01:02:51 AM »
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  :P
« Last Edit: November 09, 2012, 04:19:44 AM by fuegos »

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: Caps Lock issue
« Reply #25 on: November 09, 2012, 05:34:26 AM »
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.
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10050
Re: Caps Lock issue
« Reply #26 on: November 09, 2012, 05:39:09 AM »
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.
The only barriers that can stop you are the ones you create yourself.

Offline fuegos

  • WikiUser
  • *
  • Posts: 24
Re: Caps Lock issue
« Reply #27 on: November 13, 2012, 12:46:09 AM »
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?
« Last Edit: November 13, 2012, 01:57:15 AM by fuegos »