Miles Fidelman writes:
> well, it turns out that the installer, when accessed over a remote
> serial connection, forgets its kernel options when going into rescue
> mode
>
> i.e.:
> boot: CR #works just fine
> boot: rescue CR # fails miserably
> boot: rescue console=ttyS2,115200n8 #works just fin
Phillip,
Thanks! (more below, inline)
Philipp Kern wrote:
On Tue, Oct 02, 2012 at 03:10:48PM -0400, Miles Fidelman wrote:
The thing is, that the serial terminal is rather crippled - some
things seem to get recognized, others not (function keys are
particularly problematic, though that might be
On Tue, Oct 02, 2012 at 03:10:48PM -0400, Miles Fidelman wrote:
> The thing is, that the serial terminal is rather crippled - some
> things seem to get recognized, others not (function keys are
> particularly problematic, though that might be the Mac term
> program).
You might want to try xterm wi
well, it turns out that the installer, when accessed over a remote
serial connection, forgets its kernel options when going into rescue mode
i.e.:
boot: CR #works just fine
boot: rescue CR # fails miserably
boot: rescue console=ttyS2,115200n8 #works just fine
(now to wrestle with whatever it is
A little more info:
Miles Fidelman wrote:
Hi Folks,
Not getting a lot of help on debian-user, so thought I might raise
this here.
I've been trying to build a headless server, remotely, using the
netboot installer (PXEboot) and a serial-over-ip terminal provided by
the motherboard's (Superm
Hi Folks,
Not getting a lot of help on debian-user, so thought I might raise this
here.
I've been trying to build a headless server, remotely, using the netboot
installer (PXEboot) and a serial-over-ip terminal provided by the
motherboard's (Supermicro X8SIE-LN4F) on-board IPMI BMC.
The th
6 matches
Mail list logo
