Tiny Core Linux
Tiny Core Base => TCB Talk => Topic started by: fuegos on November 05, 2012, 11:14:45 AM
-
Hello,
I have successfully installed and configured 3.8.4 on HP t5520. It works much better than original windows ce. I only got one small issue with Caps Lock - I have to press button 3 times to switch it off. System runs Xvesa-7.1 (nozap) and uk.kmap... Can anyone please help?
Many thanks
-
I have noted that same behaviour since at least 2.x.
IIRC the other Xvesa extension may not produce such.
-
The only reason i went for Xorg's Xvesa is nozap working flawlessly. Ctrl+Alt+Del killing X is just gruesome for all users remoting to Windows (task manager funcionality is essential in their jobs). Where can i find other working Xvesa's or old version of Xorg? There is nothing i could find in the App Browser... I only need nozap and proper keyboard handling... Thanks.
-
Xvesa.tcz ?
-
The only reason i went for Xorg's Xvesa is nozap working flawlessly. Ctrl+Alt+Del killing X is just gruesome for all users remoting to Windows (task manager funcionality is essential in their jobs). Where can i find other working Xvesa's or old version of Xorg? There is nothing i could find in the App Browser... I only need nozap and proper keyboard handling... Thanks.
Sort of related, but I always thought ctrl+alt+backspace killed X, not ctrl+alt+delete?
-
Hi althalus
but I always thought ctrl+alt+backspace killed X
That is correct.
not ctrl+alt+delete?
If I read /etc/inittab correctly, that should execute /sbin/reboot
-
One way to find out... :P
-
Xvesa.tcz ?
I have tried Xvesa.tcz but used together with -nozap will not load X (cursor blinks for some time, then returns to shell). I found it working only with Xvesa-7.1.tcz but then again there is a Capslock problem...
Hi althalus
but I always thought ctrl+alt+backspace killed X
That is correct.
not ctrl+alt+delete?
If I read /etc/inittab correctly, that should execute /sbin/reboot
In my case both ctrl+alt+del and ctrl+alt+backspace kill X, although pressing ctrl+alt+del twice reboots the system.
-
really? that's interesting, so I just ran around several pc's running tc with Xorg-7.6.tcz. Seems as if ctrl+alt+del is functional up to text mode, however once X is running ctrl+alt+del is disabled ?? (grep reports an addition busybox key combination fwiw) Maybe it's the kernel, or busybox but so far (maybe X version dependent?) ctrl+alt+del has not initiated a reboot once fully booted to an X desktop.
ctrl+alt+backspace terminates X while
ctrl+alt+F1 returns to text mode and
ctrl+alt+F2 restores X (perhaps not technically the correct phrases)
AIUI you have the ability to set no zap in the xorg.conf file, you'll still have the magic Sysrq keys - REISUB, these apparently can also be disabled
Anyhow, the magic key combination " Alt+SysRq+B " will reboot the linux machine and according to the wiki so will " echo b > /proc/sysrq-trigger "
Isn't the Cap's Lock a BIOS issue ?
-
Did you try Xorg with nozap configured (in xorg.conf)?
-
An alternative approach would be to remap the capslock key out of reach ;)
-
I'm loading Xorg-7.5.tcz right now to test. Disk space available on thin client is limited to 64MB so i have to be very careful with the software i install. I'll post a follow up when tested. Cheers.
-
CapsLock and nozap works as it should now. Another issue is the screen resolution i can't change! I have followed all steps from http://wiki.tinycorelinux.net/wiki:using_xorg_over_xvesa (http://wiki.tinycorelinux.net/wiki:using_xorg_over_xvesa) but it seems to be stuck in 800x600. Also keyboard layout remains us when i set it to gb... Any clues guys?
-
it would make it easier to help if you could post the relevant part of your /etc/X11/xorg.conf
-
it would make it easier to help if you could post the relevant part of your /etc/X11/xorg.conf
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"
Option "XkbLayout" "gb"
Option "XkbModel" "pc105"
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 10
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1280x1024_60.00"
EndSubSection
EndSection
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?
-
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
-
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 (http://pastebin.com/mae7iuDa)
Any chance to find any walkaround for that?
-
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.
-
As far as i understand i create backup running command: filetool.sh -b ?
-
Yes.
-
/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?
-
Can't tell what it could be. Perhaps try with "fbdev" instead of vesa.
-
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.
-
Ref:
(--) 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?
-
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 (http://pastebin.com/aJ68RLA9)
xorg.conf file i have used for unichrome is here:
http://pastebin.com/5712vzd9 (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
-
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.
-
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.
-
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 (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?