Pi3b: ssh connection refused
SARPi Project - Slackware ARM on a Raspberry Pi, Notes for Pre-installation needs to be updated to note that, as the Raspberry documentation says:
Quote:
|
Hmm… I'm still getting
Code:
ssh: connect to host 192.168.1.118 port 22: Connection refused I think I might need to create userconf.txt. |
Even with that, I'm getting "connection refused". I've even tried static IP address, too.
It's not stuck at the rainbow screen; it shows the console on the monitor I connected to HDMI, but I still can't SSH to it. The ethernet lights flash, and the router DHCP is assigning it an IP address. I'm using a Raspberry Pi 3b with sarpi3_64-installer_slackcurrent_22Dec23_sp1.img.xz |
Quote:
I think the most helpful part of the SARPi installation tutorial for you right now might be: https://sarpi.penthux.net/index.php?p=preinstall Quote:
|
Quote:
|
Here's the debug output:
Code:
$ ssh -vvv root@192.168.1.118 |
Quote:
The error output mentions the system you’re connecting from with regards to: '~/.ssh/known_hosts' -> '/home/Geremia/.ssh/known_hosts && '~/.ssh/known_hosts2' -> '/home/Geremia/.ssh/known_hosts2 - I would delete those keys and try to login again. Code:
debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling Something on the system you're trying to connect from may be causing the issue. The type of authentication being used, for example. There has been quite a number of changes and updates to how OpenSSH works in recent times. The Release Notes offer further insight: Quote:
Code:
root@iana:~# slackpkg search openssh Code:
ssh -o IPQoS=none -vvv root@192.168.1.118 Have you tried connecting to the Pi using a different system, other than the one which produces this error? I'm clutching at straws with this one. Really don't know what could be causing your SSH issue(s). |
Quote:
One workaround is to access the console directly via your monitor and keyboard. From there, you can manually start Dropbear: Code:
/etc/rc.d/rc.dropbear start By default, the Installer doesn't have a root password (simply press ENTER when prompted by the SSH client). However, if you've set a root password as a Kernel parameter ('instrootpw=yourpassword'), that will be required instead. |
Quote:
Not had any issues with SSH login myself, and the dropbear method you've highlighted is included on https://sarpi.penthux.net/index.php?p=setupnic for those that might want to use it. Thanks for this info. Hope it helps Geremia locate whatever is causing the problem. [EDIT] on second thoughts if he's trying to install Slackware AArch64 users should be installing from the official documentation and software in any event. SARPi is just for playing around with. |
Pi3b: ssh connection refused
The raspberry pi 3 had difficulty loading the installer for Slackware Aarch64. With 1GB of RAM you will have a difficulty booting up to a shell. Not enough memory and the installer loads everything into memory.
My solution has been to use the mini rootfs and to unpack the filesystem to a formatted SD card. You will be able to boot if you unpack the kernel packages to a boot partition and the mini rootfs to a root partition. Definitely include a swap partition as well. You can easily put /boot on the SD card and the root (/) partition on a external usb hard drive or SSD. I always put a swap partition on my root disk rather than the SD card. I haven't tested this hardware model for several months, YMMV. Let us know if you successfully install on the Pi 3b. |
Pi3b: ssh connection refused
I forgot to mention that I was referring to the Slackware Aarch64 installer image.
I have no idea if sarpi has the same issue. Most likely sarpi uses less memory because it supports drivers in kernel or as modules just for the raspberry pi 3. |
Quote:
|
Quote:
I'm using a DD-WRT router. |
Quote:
|
Quote:
I don't know why that didn't auto-run. The execute bit is set: Code:
-rwxr-xr-x 1 root root 1776 Dec 22 2023 /etc/rc.d/rc.dropbear* Now the boot process hangs at SMSC95xx ethernet. ☹ |
All times are GMT -5. The time now is 11:55 AM. |