Cannot start sshd, no login screen, no gui

vecst

I recently switched from an AMD GPU to an nvidia. Upon boot I get a black screen. I tried running with nomodeset and I still get a black screen. I am able to get to a tty and type commands, but I can't see anything.
I ran an update and after a reboot I can now see an error message that sshd is failing to start.

If I'm not mistaken I believe it's sshd-keygen service for logging in. When I checked the status it shows that it cannot find ssh_host_rsa_key, ssh_host_ecdsa_key, and ssh_host_ed25519_key

Looking in /etc/ssh/ I can see the files and noticed that all the other files allowed group and others read access so I ran a chmod and that didn't seem to help anything.

I'm at a loss on where to go next. Any help would be greatly appreciated.

Staudey

vecst I recently switched from an AMD GPU to an nvidia. Upon boot I get a black screen.

So is this immediately after the GPU switch? Or was there a time when it worked?

Have you installed the proprietary Nvidia drivers? (if so, how exactly and list the output of eopkg li | grep nvidia)
I'd also try a sudo usysconf run -f to execute all usysconf triggers, which can be helpful after a hardware change.

vecst

Staudey
Immediately after the switch. I have not installed the drivers I planned on using doflicky. I was just surprised that nomodeset didn't allow me to see the display.

So right now I have one kernel version that boots me to the ssh failure, and another version that just takes me to a blank screen; I can access tty, but I'm typing blind.

I'll definitely try running that when I get back to my computer.
Oh I almost forgot to mention I tried to do eopkg check reinstall command and it failed because of some SHA1 sum in my node directory. I wasn't sure the best way to tell it to ignore that.

Staudey

I can access tty, but I'm typing blind.

Oh, you actually can't see anything even on TTY? I thought you just phrased it weirdly ^^

vecst Oh I almost forgot to mention I tried to do eopkg check reinstall command and it failed because of some SHA1 sum in my node directory.

Please elaborate. What do you mean "because of some SHA1 sum in my node directory"? What's the error message?

vecst

Staudey

The newer kernel I can see tty, the old one I can't, but the new kernel has the ssh error, and the old one doesn't.
I'll have to rerun the command when I get home. I'm pretty sure it said something like SHA1 sum error in /usr/share/lib64/node I'll get the correct wording, but I'm going to try to sudo usysconf run -f first. I'll report back as soon as I can

vecst

Staudey

alright big update. I've got my display working. I'm not sure how, but my sshd config file had a random 7 in it and the port was set to 92590. I've definitely not edited sshd on my local machine.
After I fixed that issue I was able to use nomodeset and it booted up normally.

The other error I was getting when checking for broken packages is Program terminated. Cannot calculate SHA1 hash of /usr/lib64/node_modules

Kuuchuu

Hey vecst ! Don't know if you ever resolved your node_modules SHA1 hash issue, but if not what fixed it for me is

Uninstall any installed npm packages.
Remove the node_modules directory (the sudo eopkg check command should complete now, but show nodejs as broken) sudo rm -rf /usr/lib64/node_modules
Reinstall nodejs sudo eopkg install --reinstall nodejs

You can possibly just reinstall nodejs, I'd try that first, those are just the steps I personally took while trying to resolve the problem. Wasn't much of an issue uninstalling my npm packages as I only had 2.

vecst

Kuuchuu
I have not resolved it yet, but it kinda became a nonissue when I got my system running again. Thanks for the heads up though. I'll give that a try