jardarab+news-200506@pvv.ntnu.no (Jardar Eggesbø Abrahamsen) writes:

> I artikkel <86fz06os3s.fsf@amidala.datadok.no>
> skreiv Peter N. M. Hansteen <peter@bgnett.no>:
>
> > so Something Horrible happened during the install.
>
> Obviously. I am not allowed to use vi ("Stopped (tty output)"), and I am
> also not allowed to log in with ssh.

The first could mean that your termcap is invalid. The second probably
that ssh was not enabled. Symptoms of an incomplete install, both of
them.

You could try to simply extract the file sets, ie tar zxvf *tgz, either
directly on top of your incompete install or to somewhere safer, copying
across such things as /etc/termcap if missing or damaged.

> But scp works (from the outside, not from the inside),

That's really weird. Try locating the part of the installer which comes
immediately after

"Start sshd(8) by default?"

and try running those steps by hand.

> so here is the output of dmesg. Does any of it make sense?

Lots of hardware getting recognized, but nothing truly obvious which
would cause your problem, which could of course mean simply that I'm
just not all that well informed about some of the devices. One of your
disks does not have a BSD disk label, but that may be intentional
(multibooting perhaps).

Anyway, bad memory chips or improperly seated ones is one possible
cause, as is heating problems, a damaged install medium and so on.

Did you install from an official CD set? Does network install of 3.6 or
even a -current snapshot fail in the same ways?

--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
"First, we kill all the spammers" The Usenet Bard, "Twice-forwarded tales"