Keeping Brightness Settings (Dims after every Restart)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Keeping Brightness Settings (Dims after every Restart)
I got a new laptop that I freshly re-installed Slackware on, but the problem with this one is that every time I start my computer right before the Linux kernel tries to identify an eth0 internet connection (I'm on a wireless one so it won't ever find one), it goes dim.
I've changed this as root in hoping to keep the settings, but that didn't work either. I have to manually reset the brightness every time I turn on my computer.
I'm wondering if anybody knows how to permanently set a certain brightness level. I've tried:
...the Linux kernel tries to identify an eth0 internet connection (I'm on a wireless one so it won't ever find one) ...
First, it probably isn't the linux kernel that tries to set up eth0, it most likely is one of the init scripts.
Second, you can disable this by editing /etc/rc.d/rc.inet1.conf My entry for eth0 looks like this (it doesn't come up at boot time):
Code:
# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]=""
DHCP_HOSTNAME[0]=""
About the brightness thing: it seems that right before the networking, the init scripts start udev. I did a google search for "udev brightness", and it looks like a good start.
Do you see any usefull links when you google that?
I just got back from a 3 hour lab class. Normally the text goes by quickly so I can't read it, but I'll assume you are correct about that. Thank you for helping.
As for the google search, I'll start it now and report back to see if anything helps.
Unfortunately the Google searches did not help. I tried them and the terms that I googled were all for a different distro other than Slackware and when I did transfer the commands to what Slackware uses they failed.
dive:
Quote:
You could fix the brightness issue by finding the /proc/acpi file for brightness and put an echo command in rc.local.
That's what I tried to do with one of the Google searches, but for some reason there's no "brightness" under my /proc/acpi. These are the only files and directories there:
ac_adapter/ alarm battery/ button/ event wakeup
None of the directories had anything related to brightness, and the "event" file didn't contain anything brightness-related.
====================================================================
Also, I didn't want to make a new thread about this so I thought I would post it here, so hopefully this can also be helped even though it's not related to this issue.
My system clock keeps reverting back to a different time than the one I had set it as before logging off. I only realized this while I was doing this since it required me to constantly restart my computer to test if the effects had been permanent.
Does anybody know a way to keep my clock set at the time I put it on before logging off/shutting down? I also Googled this and none of the searches helped with this one either except one that said when I log off, to keep my settings, which I thought would work but did not.
Do you mean the clock runs too fast or too slow (e.g. it is 5 min off if you power down for 10 min, but 10 min off if you power down 20 min, ...)
Or does it reset to something like 1 januari 2010 00:00 ?
Do you mean the clock runs too fast or too slow (e.g. it is 5 min off if you power down for 10 min, but 10 min off if you power down 20 min, ...)
Or does it reset to something like 1 januari 2010 00:00 ?
Okay, I've semi-found the errors. Although I'm still unsure how to fix them. As I previously stated, my /proc/acpi did not come with the location to set the brightness, so I was unable to edit rc.local to use the 'echo' command and set the brightness. If I had done so, according to the Google searches it would have dimmed for a second during udev, started up rc.local and then set the brightness to what I put it as.
Unfortunately there's no /video section in /proc/acpi. I even tried to go into /lib/udev/keymaps and the HP (my laptop company) modules did not match the layout.
Fortunately, it was also because of many more restarts that I did find the problem. After some frustration I decided to watch some Hulu videos, but the sound was a bit low. I didn't clear anything recently, so I found out that my sound had reset to 75% while Hulu kept it's volume meter at maximum.
One of the Google solutions that didn't work for me was editing my power settings for my monitor, which I suspect to be the cause of the problem. There's an option titled "Monitor Power Control" which, I unchecked both as root and as my standard user. This did not work.
At first I thought it was just me again and my frustration kicking in, but because I recall putting my sound at 100% before (on my computer) I checked the power monitor, and it was again...checked.
This means that whatever is causing it, my computer reverts certain settings every time I start the computer. This includes the power manager (and therefore my monitor), my sound and my system clock.
=======SUMMARY OF THE ABOVE: My computer resets certain system settings.=======
Anyways, I guess the question now is...how do I keep these settings? Some of them I have tried as root to keep them but those failed. Does anybody think they know a way to keep these settings the way I had desired?
My first computer did not have these problems, which is why I'm confused as to why they're occurring on this one.
I was still wondering if anybody knew a quick solution to this? I think I could edit rc.local to put in everything I want uploaded at the time, but for me that's a lot of stuff to add.
Okay, I lied. I'm bumping this again because I tried setting everything the way I wanted it in rc.local, but none of it worked. ALL of it reset.
HOWEVER! All of it was fine in an older kernel version. I'm thinking I fudged something from the transition to 3.0.3 from 2.6.39.
Does anybody else have this problem, or a possible identification to my problem because after days and hours of trying, with college classes in between, I still haven't found it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.