You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

I've been working on improving the Japan theme and I've been making good progress. However, along the way I noticed an amusing interaction between the backlight gadget and the caps lock key on my computer. I'm running Bodhi 5 32 bit on a Mac (OS X) using Virtual Box.

When I pull up the backlight slider to "increase" the screen brightness, the caps lock light comes on. And when I slide it down, it goes off. As you might imagine with a guest running under Virtual Box, the backlight itself isn't changed (it's under the control of the OS X host). I assume this is connected to a related issue that the caps lock light always turns on when I power up the Bodhi guest virtual machine.

@the_waiter, I am adding this to the Moksha Issues google Docs we maintain. As well as the following information for those interested:

Quote:

See files moksha/src/modules/conf_display/e_int_config_dpms.c
And moksha/src/bin/e_backlight.c

In the latter file note the comment:
/* FIXME: need to make this more precise so we don't set keyboard LEDs or something */

This and a few other things reminds me at some point sooner than later I need to go thru the list of known issues and start fixing stuff. At least fix all the easy stuff I can and examine more e22 backports to see if they are applicable.

Meanwhile on this specific issue, patches are of course accepted provided they work and don't break anything. lol. If anyway is brave enough to bite that bullet.

Quote:

Originally Posted by bobl01

... I assume this is connected to a related issue that the caps lock light always turns on when I power up the Bodhi guest virtual machine.

Anyone else noticed anything similar?

Now this issue of caps lock being on when I first boot Bodhi up is a longstanding irritation for me. Oddly enough most bodhi ISOs I have installed in Virtualbox have this issue. But not all I am unsure if this has to do with the Bodhi iso or the virtualbox version I was installing it on. I have running hardware installs of bodhi 2.4 to bodhi 5.0 and many of them have Virtualbox installed with several if not many VMs. (ok at some point i need to clean all this crap up on my multiple machines with multiple partitions and multiple OSes. too busy -- low priority)

Anyways back on topic: I have noted it just never really knew where to look for it. It seems that this also occurs in e22. But don't quote me on that I need to recheck that. Perhaps it is related. If so that would be fantastic because it would give a some place to start debugging the issue.

Yes, I checked the code and it is the same. I talked with okra (e-dev) and he claimed it must be a mapping issue in VBox. The real reason why the code is collecting the device info is uncertain for me but he told if there are some "insane" devices, they will be listed in the setting. And bobl01 is really right. The backlight slider has a real impact to capslock. I tried it in terminal. When I slide up to max, the first letter is capital. Any other letters are normal as, the slider goes down immediatelly. A real mystery, yes

I am uncertain why in a VM it picks up on stuff in /sys/devices/platform/i8042/serio0/input/input0/ but on my hardware it ignores stuff in /sys/devices/platform/i8042/serio0/input/input4/ To understand why I would prob have to run e thru dbg and set breakpoints at the relevant places and examine variables and function calls closely. Sounds like a good way to waste most of a day

But I would presume when the brightness module picks up on these key settings it is to increase the brightness of the led (turn on or turn off most likely) on the key, assuming you have a keyboard with leds on said keys.

I did not have a problem with the CAPS key light until I did an apt-get upgrade.

At the end the setup detected the correct keyboard (I think) but now after every login my CAPS key is illuminated but when I type I get lowercase. If I then hit the CAPS LOCK the light goes out and I still get lowercase. When I hit the CAPS LOCK key yet another time, the light is illuminated but I get uppercase. Any way to check this or just make it not illuminate the CAPS key indicator after login? I am not running VM. It's just a standard install on a hard drive.

I don't know if this is relevant at all, but if you go to the settings panel -> screen -> Backlight, then at the bottom of the dialog window that opens up, there are three (on my system) text lines, which end with "capslock", "numlock", and "scrolllock". I have no idea what they mean, and no idea how these lines are supposed to be used, but their very presence on a Backlight dialog window would hint that the backlight and the capslock light are linked in some way.

(Later) After some investigation, I discovered that the following Terminology commands will turn the capslock light on and off.
cd /sys/class/leds/input0::capslock
echo 1 | sudo tee brightness
echo 0 | sudo tee brightness

Whether it's possible to build these into a startup script is a question for another day, since I'm need some shuteye!

Yes I noticed the same thing. They are definitely linked but they shouldn't be. I can understand them being linked to KEYBOARD backlight but not DISPLAY backlight.

My temporary solution was to turn the slider for normal backlight down to < 50. When I adjust it to 50 that is the threshold where my capslock indicator lights up. I left the other sliders alone so the dim backlight still is on 30.

The path that appears at the bottom of the dialog box (in case anyone wants to cut and paste it) is:
/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:046D:C31C.0002/input/input6/input6::capslock

I will do some testing to see if I can comment something out or change a setting in one of the files but I'm no hacker or programmer and don't really know linux all that well but I'm learning.

I'm guessing it's something in the file in the above mentioned directory, named "trigger". I'm thinking there is an entry in there for capslock that can be commented out or the value changed. Maybe someone that knows more than me (shouldn't be hard) can give it a look.

Last edited by makarovnik; 01-23-2019 at 11:51 PM.
Reason: added more info