Bruce Hunter wrote:> I have setup a headless machine via a null modem cable. Instalation went > fine. The only problem now, is connecting to the machine after the > install. When I #cu -l /dev/cuaao/ > I see the boot process, but it gets to the date prompt but doesn't show > the login: > i did install ssh, but won't let me login with the password I set for > root. Any other methods for connecting? This system is connected in my > local network, with a firewall protecting my systems. > - i am not running xserver on this systemOf course you cannot login as root over the ssh connection; that's a default behaviour for security reasons. Haven't you installed a regular user on this PC, which is also member of the wheel group to allow using su for becoming root? Funny, that I'm struggling with opposite problem: I do not get the boot messages over the serial cable, but do get the login prompt, which I do not understand :(. For the login prompt, I have following in /etc/ttys on the headless PC: ttyd0 "/usr/libexec/getty std.9600" unknown on secure but be sure the serial port is enabled in the BIOS, and you have serial port support compiled into your kernel. Your cu command should then work, I suppose. Cheers, Rob.
Hi everybody! On (040507), Rob wrote:> Funny, that I'm struggling with opposite problem: I do not get the > boot messages over the serial cable, but do get the login prompt, > which I do not understand :(.To get your machine to display the boot messages on the serial console just do the following as root: echo -DP >/boot.config On boot the keyboard is probed and if no keyboard is present the serial console is selected. Best regards, Hank -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20040507/e27dbe09/attachment.bin
On Fri, 7 May 2004, Rob wrote:> Bruce Hunter wrote: > > I have setup a headless machine via a null modem cable. Instalation went > > fine. The only problem now, is connecting to the machine after the > > install. When I #cu -l /dev/cuaao/ > > I see the boot process, but it gets to the date prompt but doesn't show > > the login: > > i did install ssh, but won't let me login with the password I set for > > root. Any other methods for connecting? This system is connected in my > > local network, with a firewall protecting my systems. > > - i am not running xserver on this system...> Funny, that I'm struggling with opposite problem: I do not get the > boot messages over the serial cable, but do get the login prompt, > which I do not understand :(. > > For the login prompt, I have following in /etc/ttys on the headless PC: > > ttyd0 "/usr/libexec/getty std.9600" unknown on secure > > but be sure the serial port is enabled in the BIOS, and you have > serial port support compiled into your kernel. > Your cu command should then work, I suppose.You both have half of the solution, apparently, just different halves :-). To configure my boxes for serial console operation, I do two things: (1) Enable the ttyd0 entry in /etc/ttys by changing "off" to "on" (2) Add the following line to /boot/loader.conf: console="comconsole" This one can be done in a couple of ways, including flags in boot.config for the first stage loader. The first action above tells init to launch getty+login on the serial port. The second action above tells the kernel to direct /dev/console and low level console output to the serial port. Note that nothing prohibits you from leaving ttyv0 turned on when running with a serial console so you could still log in on the VGA/keyboard console if you wanted to. There are also some options in conscontrol(8) to send output to multiple console devices, but there are some limitations to multiple console operation. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research
> 1. Re: Connecting to a Headless machine, after install > (Robert Watson)> Message: 1 > Date: Sat, 8 May 2004 16:54:24 -0400 (EDT) > From: Robert Watson <rwatson@freebsd.org> > Subject: Re: Connecting to a Headless machine, after install > To: Rob <stopspam@users.sourceforge.net> > Cc: freebsd-stable@freebsd.org > Message-ID: > <Pine.NEB.3.96L.1040508165202.27309J-100000@fledge.watson.org> > Content-Type: TEXT/PLAIN; charset=US-ASCII >> On Fri, 7 May 2004, Rob wrote: > > > Bruce Hunter wrote: > > > I have setup a headless machine via a null modem cable. Instalation went > > > fine. The only problem now, is connecting to the machine after the > > > install. When I #cu -l /dev/cuaao/ > > > I see the boot process, but it gets to the date prompt but doesn't show > > > the login: > > > i did install ssh, but won't let me login with the password I set for > > > root. Any other methods for connecting? This system is connected in my > > > local network, with a firewall protecting my systems. > > > - i am not running xserver on this system > ... > > Funny, that I'm struggling with opposite problem: I do not get the > > boot messages over the serial cable, but do get the login prompt, > > which I do not understand :(.> > For the login prompt, I have following in /etc/ttys on the headless PC:> > ttyd0 "/usr/libexec/getty std.9600" unknown on secure> > but be sure the serial port is enabled in the BIOS, and you have > > serial port support compiled into your kernel. > > Your cu command should then work, I suppose.> You both have half of the solution, apparently, just different halves :-). > To configure my boxes for serial console operation, I do two things:> (1) Enable the ttyd0 entry in /etc/ttys by changing "off" to "on" > (2) Add the following line to /boot/loader.conf: > > console="comconsole" > > This one can be done in a couple of ways, including flags in > boot.config for the first stage loader.> The first action above tells init to launch getty+login on the serial > port. The second action above tells the kernel to direct /dev/console and > low level console output to the serial port. Note that nothing prohibits > you from leaving ttyv0 turned on when running with a serial console so you > could still log in on the VGA/keyboard console if you wanted to. There > are also some options in conscontrol(8) to send output to multiple console > devices, but there are some limitations to multiple console operation. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Senior Research Scientist, McAfee Research >I saw something similar on a headless Intel 1100R. The default serial port speed during the BIOS boot up did not match the port speed that was set on the port when the system booted. Resetting the BIOS speeds to match the speed set in /etc/ttys cured that problem.> End of freebsd-stable Digest, Vol 59, Issue 7Bill -- Bill Vermillion - bv @ wjv . com