On 2016-11-18 13:59, Bob Jones wrote:
Re: never reactivate the console unless you do it over ssh
Aah, well therein lies the twist, SSH never comes up, so I guess
you're right, its waiting for tty.
How do now I tell it to not use tty0 (and will doing so prevent me
from using the console port for diagnostics at a future date ?)
On 18 November 2016 at 18:08, <[email protected]> wrote:
On 2016-11-18 13:13, Bob Jones wrote:
I successfully installed OpenBSD 6 on a system that only has USB
console by broadly following the instructions here
http://unix.stackexchange.com/questions/292891/how-can-i-install-openbsd-using-the-serial-console-without-external-monitor-wi
When the console cable session is connected, the system boots up
fine,
no problems.
When the console cable is disconnected, the system seems to hang
somewhere, and then once I re-connect to the console the boot process
continues fine.
I'm obviously unable to tell at which point the boot hangs because of
the need to press the return key a few times to get the initial
console response.
(During the install process, OpenBSD prompted whether I wanted
default
console set to tty0 and I said yes).
The problem is that you've told the OS to use tty0 and when it boots
there
is no tty0 unless the cable is plugged in. If tty0 doesn't exist it's
going
to wait for it. There maybe be a timeout at which the OS continues
without
it, but in this case it will probably never reactivate the console
unless
you do it over ssh.
Have you tried waiting 10 minutes or so for tty0 to time out? I know it
times out on FreeBSD, but i have never had to test this on OpenBSD so i
am not sure.
If you tell it not to use tty0 then it wont use it at all unless you try
to start it manually over ssh at a later point in time. IMO the point of
the console is to be there is case you dont have ssh. The best solution
is to probably leave the cable plugged in. Or if this machine has PCI
ports get a serial card.
