• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How To Help ! Linux black screen

Markfw

Moderator Emeritus, Elite Member
OK, its been a while. So I had a perfectly working setup, but I kept hearing the fans start and stop. So I did the below:

sudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration

cd ~

gedit fancontrols

and add and then save (for 2 video cards)

nvidia-settings -a [gpu:0]/GPUFanControlState=1
nvidia-settings -a [fan:0]/GPUTargetFanSpeed=85
nvidia-settings -a [gpu:1]/GPUFanControlState=1
nvidia-settings -a [fan:1]/GPUTargetFanSpeed=75

============================================

Now I have a black screen (with a graphic mouse cursor) when I boot ! But my remote F@H says its running, and I assume BOINC is still running. Is there any easy way to fix this ?
 
I did that.68c just like I thought. Where is the file xconfig that I created ? I think maybe if I delete what I created it will fix it.

And it can't be the overheating as its worked perfectly for weeks, until I did the above, I created 2 files I think. I want the fancntrols, I think I want to undo the xconfig and empty config, etc.
 
Last edited:
ok I guessed at add sudo at the beginning of the line and it worked, and by that I mean, I renamed the file-rebooted, and the screen is back. Not sure if the fancontrols worked or not yet.
 
Last edited:
OK, its been a while. So I had a perfectly working setup, but I kept hearing the fans start and stop. So I did the below:

sudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration

cd ~

gedit fancontrols

and add and then save (for 2 video cards)

nvidia-settings -a [gpu:0]/GPUFanControlState=1
nvidia-settings -a [fan:0]/GPUTargetFanSpeed=85
nvidia-settings -a [gpu:1]/GPUFanControlState=1
nvidia-settings -a [fan:1]/GPUTargetFanSpeed=75

============================================

Now I have a black screen (with a graphic mouse cursor) when I boot ! But my remote F@H says its running, and I assume BOINC is still running. Is there any easy way to fix this ?

There's a couple of steps missing according to the Brony guide.

1) make the file, fancontrols, executable:
chmod +x fancontrols

2) Add the fancontrols executable to your startup applications.
go to start menu, then preferences or administration and look for "startup applications'. Once open choose add, then give it a name and 'browse' for your file fancontrols. Then choose save. You'll need to reboot.

To check fan speed and temps, run nivida-settings or nvidia-smi
 
I am probably wrong, lane42, but I think xserver doesn't know how to deal with EVGA's independent fan control system. But the cool-bits flag is able to over-ride both/all fans.
 
If you have xserver installed, I just copy and paste this,
sudo nvidia-xconfig --thermal-configuration-check --cool-bits=28 --enable-all-gpus
into terminal, enter, password, enter, then reboot computer.
Now nvidia xserver has fan control
 
If you have xserver installed, I just copy and paste this,
sudo nvidia-xconfig --thermal-configuration-check --cool-bits=28 --enable-all-gpus
into terminal, enter, password, enter, then reboot computer.
Now nvidia xserver has fan control

This works for you and me but MarkFW has a lot of machines. I think he wants to set the gpus at a certain fan speed automatically at each boot. I use nvidia-settings (gui) to set the fan speeds but I have to reset them after each boot.
 
This works for you and me but MarkFW has a lot of machines. I think he wants to set the gpus at a certain fan speed automatically at each boot. I use nvidia-settings (gui) to set the fan speeds but I have to reset them after each boot.

This may be a bit off-the-wall, but could we use something like, "Hey, Alexa! Set my fan speeds to default on PC Waldo."
 
Now that would be cool Rudy 🙂

I just do it this way because it's so easy to control fan speeds. it really only takes
seconds to adjust each gpu fan speed. I run seti. When I do F@H or Prime grid,
my gpu's run 10c warmer. just open xserver slider the slider over, done. it's
even fun to play with.
 
Now that would be cool Rudy 🙂

I just do it this way because it's so easy to control fan speeds. it really only takes
seconds to adjust each gpu fan speed. I run seti. When I do F@H or Prime grid,
my gpu's run 10c warmer. just open xserver slider the slider over, done. it's
even fun to play with.

I posted more detail in our stealth thread.
 
I always use... chmod -R 777/target folder

just don't do it to the entire drive (like root) or you could break a few things..


if in doubt. That gives permissions to Anyone... as long as your not a network administrator in a workplace, that command should be fine.
 
Last edited:
I islate most of my linux machines so.. there are no "others" lol. There is a way to make yourself the root and get rid of all others, but you need to really start off with this before installing other programs. It's probably the way I am going to go, when I install linux for my next build. I hate the sudo command. If someone telnetted into your system...They could just use the SUDO command all day long...so I don't see the point in having it.
 
Remote attackers usually break in by exploiting a buggy system service, or via a trojan. (And then they attempt to exploit privilege escalation bugs, because services or trojans generally run unprivileged.) IOW break-ins mostly happen without knowledge of username/password combos.

On my main home PC, I have a terminal open most of the time in which I am logged in as root. Thus I rarely use sudo on that machine.

On my boinc crunchers, the main user is member of group "boinc" for more convenient access to the boinc files. Or boinc is even running from that main user account.
 
Don't you need a password to run a SUDO command ?
Short answer: Yes, generally.

Long answer: This can be configured in different ways. By default, many Linux distributions configure sudo for the initial main user such that
  • the password of the invoking user must be entered when sudo is invoked (but it could also be configured to run without password, or with password of a certain other user),
  • the password is cached for a while, e.g. 5 minutes, such that the user isn't bothered with more password prompts when he issues a few sudo commands in a row (but it could also be configured not to cache the password, or more precisely, the authentication),
  • this password cache is only granted within the same login session/ pseudo terminal, such that the same user needs to enter the password again if logged in via a different pseudo terminal (but sudo could also be configured to have a single authentication cache for all pseudo terminals),
  • any user, e.g. root or boinc or fahclient or mail or..., is acceptable as target user (but it could also be set to accept only one or some specific target users),
  • any command is acceptable for execution with target user identity (but it could also be set to allow only specific commands).
 
Back
Top