Unable to ssh to TonidoPlug with latest ArchLinuxARM

[starguy]

I installed the latest ArchLinuxARM to an external USB drive with my TonidoPlug using the directions at:
http://archlinuxarm.org/platforms/armv5/tonidoplug

When I booted the TonidoPlug (with the external USB drive) I could ping the device, but any attempt to ssh to it resulted in connection refused.

I then repeated the installation procedure, but instead of using the latest ARM image
(at: http://archlinuxarm.org/os/ArchLinuxARM ... est.tar.gz dated 14-Nov-2012)
I used an earlier version, dated 28-Aug-2012, found at:
http://os.archlinuxarm.org/os/armv5te/A ... tfs.tar.gz

When it booted I could ssh to it and it seems be fully operational, though it is a bit out of date, so I tried running:
pacman -Syu
to update the system, but it failed with a message about a conflict with /lib if I remember right.

Just in case I got bad data transfered I tried repeating the installation with the latest ArchLinuxARM again, but still got connection refused.

Has anyone else had trouble with the latest ArchLinuxARM on a TonidoPlug (v1)?
Or is there a reliable way to update an older install?

[honnoric]

I have the same problem.

I have copied ARM Linux onto two different USB drives.

In both cases my Tonidoplug boots from the USB - the indicator light is is Blue and I can ping the Plug successfully. Additionally I can see the Hostname (alarm) on my routers DHCP list - so it is definitely starting up.

But I cannot get an SSH connection.

I get "Failed to connect to 192.168.2.7: Network error: Connection refused" from PuTTy and the same from FireSSH."

Not sure if there is there any way I can mount the USB after it has been "running" and check out the log files - or if there is way to look at the relevant files to confirm that ssh is genuinely being started.

Any help much appreciated

[WarheadsSE]

Can you both please confirm you arcNumber & mainlineLinux settings from uboot? I don't have a TP/TP2 so I can't say if they left the serial port accessible.

[starguy]

> Can you both please confirm you arcNumber & mainlineLinux settings from uboot?
> I don't have a TP/TP2 so I can't say if they left the serial port accessible.

How do I do this? I can mount the USB drive on my desktop running LinuxMint and look around, but not sure what to look for. (I can also mount the USB drive on my Tonido (after booting it w/o the USB drive), but I still need my desktop computer to connect to the Tonido to look around.)

Where is uboot? arcNumber? mainlineLiux settings?

[WarheadsSE]

ssh into the stock tonido system, and run `fw_printenv`

[starguy]

I booted my TonidoPlug (v1) without a USB drive, ssh'd into it,
then ran:
fw_printenv
and got:
-bash: fw_printenv: command not found

If it helps, my TonidoPlug runs Jaunty Jackalope.
If I enter:
lsb_release -a
I get:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu jaunty (development branch)
Release: 9.04
Codename: jaunty

[starguy]

Just noticed that
http://archlinuxarm.org/os/ArchLinuxARM ... est.tar.gz
now points to a newer image that has a datestamp of January 16, so I tried it out. Unfortunately same result as November 14. The August 28 version is the last one I could ssh to.

[martinscharnke]

I have the same problem ... some time ago I was no longer able to ssh into my Tonidoplug ... possibly after a pacman update.
I was still able to access the shares and use webmin to do some things.
Having moved the main shared drive to another computer, I wanted to start with a clean up-to-date install.
Same installation process as a couple of years ago, but I used the new image ... and the same problem ... can't ssh in - "network error: connection refused."

I still have the image from a couple of years ago, and could probably install that, but would need to upgrade so many packages to install the ones I want to that - presumably - the same problem will re-occur.

What's going on? Is sshd even running? Since I can't ssh in, I can't tell.
I'll connect the drive to another machine and try to view the logs to work things out, but this has become a major pain in the proverbial.

[martinscharnke]

OK ... discovered that there are no logs recorded.
Digging deeper, there is no /etc/rc.conf on this clean install, so no logging daemon, and - significantly - no ssh daemon.
I composed a bare-bones rc.conf as per "archlinuxarm.org/support/guides/system/first-steps" but that doesn't seemed to have solved the problem. WIll keep trying.

[martinscharnke]

OK ... according to https://wiki.archlinux.org/index.php/In ... ts/rc.conf
rc.conf is mostly superseded ... the page states:

Note: Using the legacy configuration options in /etc/rc.conf for system configuring still works (for now) with the default init system, but the new configuration files take precedence and using them is recommended. The new files will also work for configuring systemd. See Systemd#Native_configuration

It sounds like the legacy configuration options no longer work ... and the new ones don't seem set up correctly in the install image.