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.
...which simply adds the command that you state fixes the problem to /etc/rc.d/rc.local and then ensures that /etc/rc.d/rc.local is executable. /etc/rc.d/rc.local is run after every boot by /etc/rc.d/rc.M if it is executable.
EDIT: Of course, your screen will be bright until near the end of the booting process.
I have no idea why that's not working -- you could just edit /etc/grub/grub/cfg directly if you find a kernel parameter that works better.
I misread your OP and I thought you were saying there was no content under /sys/class/backlight -- sorry (I was very tired).
If the `echo` command works then you probably already have all the functionality intact -- does this command work:
Code:
xbacklight -set 10
See man xbacklight
You can set up some manual keybinds based on this or the `echo` command.
However, the next time you update your kernel image dpkg will fail because it cannot run `update-grub` and you will no longer be able to update your Debian system -- you should start a new thread to troubleshoot this specific issue.
However, the next time you update your kernel image dpkg will fail because it cannot run `update-grub` and you will no longer be able to update your Debian system -- you should start a new thread to troubleshoot this specific issue.
My apologies -- the OP stated that his Debian system was "in charge" of GRUB and I was working on the assumption that this was all from that system (silly me). http://www.linuxquestions.org/questi...2/#post5323343
@OP: If this is all in Slackware then that's why there is no `update-grub` command...
FWIW you don't "update /etc/default/grub", that file is used as a template for the GRUB configuration file at /boot/grub/grub.cfg
Sorry for all this confusion -- I will try to pay more attention next time.
if no one helps ...then... i'm goin to need to talk with PAT... or QUIT the distro ...
Why not just do what you were advised by Richard Cranium in post n° 16???
I suggest you don't bother Pat with this kind of non-issue.
Feel free to move (again) to another distribution, then encounter another small issue then move (again) to another distribution then... Some people call that perpetual motion, others just distro-hopping. Nevertheless, as long as you have fun all is good
PS I saw ivandi's answer just after posting. Worth trying, I think.
Last edited by Didier Spaier; 02-26-2015 at 04:25 PM.
Typing blindly commands you find at random, not even trying to understand what they are supposed to do, won't lead you anywhere. The error message is right: there is no directory /mnt/sda6/dev as you didn't create one.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.