Mark Benson | 12 Nov 2011 20:46
Picon

5.1 Restore - can't telnet?

Hi. I just did a NetBSD 5.1 Restore on my Qube2 (which I just built a new power supply and power plug for).

Restore went great - VERY smooth operation - really nice to be able to just 'do' it with no serial terminal etc.

I changed the IP, netmask, default route to match my LAN once I had it hooked up using the panel (I prefer a
fixed IP).

That went fine, I can now ping the Qube2 from another box.

$ ping 192.168.1.103
PING 192.168.1.103 (192.168.1.103): 56 data bytes
64 bytes from 192.168.1.103: icmp_seq=0 ttl=255 time=0.704 ms
64 bytes from 192.168.1.103: icmp_seq=1 ttl=255 time=0.472 ms
64 bytes from 192.168.1.103: icmp_seq=2 ttl=255 time=0.568 ms
^C
--- 192.168.1.103 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.472/0.581/0.704/0.095 ms

All good.

I can't telnet to the box to continue my setup/secure the box though?

$ telnet -l root 192.168.1.103
Trying 192.168.1.103...
Connected to 192.168.1.103.
Escape character is '^]'.
telnetd: Authorization failed.
Connection closed by foreign host.

(Continue reading)

Andy Ruhl | 13 Nov 2011 00:12
Picon

Re: 5.1 Restore - can't telnet?

On Sat, Nov 12, 2011 at 12:46 PM, Mark Benson <markbenson <at> mac.com> wrote:
> Hi. I just did a NetBSD 5.1 Restore on my Qube2 (which I just built a new power supply and power plug for).
>
> Restore went great - VERY smooth operation - really nice to be able to just 'do' it with no serial terminal etc.
>
> I changed the IP, netmask, default route to match my LAN once I had it hooked up using the panel (I prefer a
fixed IP).
>
> That went fine, I can now ping the Qube2 from another box.
>
> $ ping 192.168.1.103
> PING 192.168.1.103 (192.168.1.103): 56 data bytes
> 64 bytes from 192.168.1.103: icmp_seq=0 ttl=255 time=0.704 ms
> 64 bytes from 192.168.1.103: icmp_seq=1 ttl=255 time=0.472 ms
> 64 bytes from 192.168.1.103: icmp_seq=2 ttl=255 time=0.568 ms
> ^C
> --- 192.168.1.103 ping statistics ---
> 3 packets transmitted, 3 packets received, 0.0% packet loss
> round-trip min/avg/max/stddev = 0.472/0.581/0.704/0.095 ms
>
> All good.
>
> I can't telnet to the box to continue my setup/secure the box though?
>
> $ telnet -l root 192.168.1.103
> Trying 192.168.1.103...
> Connected to 192.168.1.103.
> Escape character is '^]'.
> telnetd: Authorization failed.
> Connection closed by foreign host.
(Continue reading)

Kieran Jacobsen | 13 Nov 2011 00:01

RE: 5.1 Restore - can't telnet?

Just performed a restore a few days ago myself. I ended up using rlogin to get in and start sshd.

-----Original Message-----
From: port-cobalt-owner <at> NetBSD.org [mailto:port-cobalt-owner <at> NetBSD.org] On Behalf Of Mark Benson
Sent: Sunday, 13 November 2011 5:47 AM
To: Cobalt MIPS NetBSD
Subject: 5.1 Restore - can't telnet?

Hi. I just did a NetBSD 5.1 Restore on my Qube2 (which I just built a new power supply and power plug for).

Restore went great - VERY smooth operation - really nice to be able to just 'do' it with no serial terminal etc.

I changed the IP, netmask, default route to match my LAN once I had it hooked up using the panel (I prefer a
fixed IP).

That went fine, I can now ping the Qube2 from another box.

$ ping 192.168.1.103
PING 192.168.1.103 (192.168.1.103): 56 data bytes
64 bytes from 192.168.1.103: icmp_seq=0 ttl=255 time=0.704 ms
64 bytes from 192.168.1.103: icmp_seq=1 ttl=255 time=0.472 ms
64 bytes from 192.168.1.103: icmp_seq=2 ttl=255 time=0.568 ms ^C
--- 192.168.1.103 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev =
0.472/0.581/0.704/0.095 ms

All good.

I can't telnet to the box to continue my setup/secure the box though?

(Continue reading)

Mark Benson | 1 Dec 2011 21:57
Picon

Qube2 Dead?

I know this is slightly OT but you folks are cobalt experts, and I need a second opinion...

I hooked up a IDE to SATA adapter to my Qube2 with a SATA SSD and did a 5.1 restore successfully.

I logged in as root after it rebooted fiorst time over and it was fine, I started SSHd and tested
that and it was a-ok. I shutdown the system and tied down some wires in side and secured the SSD with
a pad of insulating 2-sided silicon gel tape.

When it rebooted it locked up during the boot process hard. Nothing worked. No serial console
response.

I turned it off after 10 mins and on and it wouldn't even start up. All I get is a line of
black squares on the top row of the LCD.

I've stripped it right back to bare bones and it won't work. I even swapped the RAM (which had
been working 100% in service for years) but no dice.

I guess it's dead?

--

-- 
Mark Benson

My Blog:
<http://markbenson.org/blog>
Follow me on Twitter:
http://twitter.com/mdbenson

"Never send a human to do a machine's job..."

(Continue reading)

Byron Servies | 1 Dec 2011 22:05
Favicon

Re: Qube2 Dead?

On Thu, Dec 1, 2011 at 12:57 PM, Mark Benson <markbenson <at> mac.com> wrote:
> I've stripped it right back to bare bones and it won't work. I even swapped the RAM (which had
> been working 100% in service for years) but no dice.
>
> I guess it's dead?

Hi there!

I recommend checking the power supply and make sure it is not having
significant voltage dropouts in voltage and/or current.  The original
Qube2 supplies were always a bit fragile, in my opinion, and I have
had many fail.

I don't have a replacement option for you, either, but I believe there
were posts on that in this forum a few years ago.

HTH,

Byron

Andy Ruhl | 1 Dec 2011 23:17
Picon

Re: Qube2 Dead?

On Thu, Dec 1, 2011 at 2:05 PM, Byron Servies <bservies <at> pacang.com> wrote:
> On Thu, Dec 1, 2011 at 12:57 PM, Mark Benson <markbenson <at> mac.com> wrote:
>> I've stripped it right back to bare bones and it won't work. I even swapped the RAM (which had
>> been working 100% in service for years) but no dice.

I will agree about the power supplies. I changed about 4 of them. I
bought a cheap one on ebay that has an adapter cable for the funny
Qube power plug, so now I can use cheap laptop ones.

If you unplugged the fan, there was some specualtion that this changed
the power supply enough to make them unstable. Plug the fan back in
and try again? Although what you're describing sounds pretty bad.

Andy


Gmane