serial consoles
Hi I'd like to be able to login using a null modem cable to a freebsd server, from a freebsd laptop. It doesn't need to display boot messages, just allow me to login after the system has booted. I've got a null modem cable connected to my freebsd server, and on the other end is a USB serial port on my laptop. On the server I've got: uart0: 16550 or compatible port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: [FILTER] in /etc/ttys on the server: ttyu0 /usr/libexec/getty std.9600 vt100 on secure and there is a getty running on that: $ ps xa| grep getty 1825 ?? I 0:00.00 /usr/libexec/getty std.9600 ttyu0 On the laptop, I have: ugen1.2: FTDI at usbus1 uftdi0: USB to Serial Cable on usbus1 as well as cuaU0 and ttyU0 entries in /dev. However, when I use cu on the laptop: sudo cu -l /dev/cuaU0 -s 9600 I never get a login prompt. If I press enter, the cursor scrolls down. Likewise other characters echo back. I'm reasonably sure that I'm connected to the appropriate com port on the server because if I plug it into the other com port and press enter, nothing happens. It feels to me that I'm missing something basic. Can someone provide me with some clue? Note: I'm reasonably sure the null modem cable and USB device are fine, I've used them recently on an arm board (gateworks) running freebsd and it worked fine then. Matthew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: serial consoles
On 12/24/11 19:34, Matthew Luckie wrote: Hi I'd like to be able to login using a null modem cable to a freebsd server, from a freebsd laptop. It doesn't need to display boot messages, just allow me to login after the system has booted. I've got a null modem cable connected to my freebsd server, and on the other end is a USB serial port on my laptop. On the server I've got: uart0: 16550 or compatible port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: [FILTER] in /etc/ttys on the server: ttyu0 /usr/libexec/getty std.9600 vt100 on secure and there is a getty running on that: $ ps xa| grep getty 1825 ?? I 0:00.00 /usr/libexec/getty std.9600 ttyu0 On the laptop, I have: ugen1.2: FTDI at usbus1 uftdi0: USB to Serial Cable on usbus1 as well as cuaU0 and ttyU0 entries in /dev. However, when I use cu on the laptop: sudo cu -l /dev/cuaU0 -s 9600 I never get a login prompt. If I press enter, the cursor scrolls down. Likewise other characters echo back. I'm reasonably sure that I'm connected to the appropriate com port on the server because if I plug it into the other com port and press enter, nothing happens. It feels to me that I'm missing something basic. Can someone provide me with some clue? Note: I'm reasonably sure the null modem cable and USB device are fine, I've used them recently on an arm board (gateworks) running freebsd and it worked fine then. You sure its not easier to run a crossover UTP cable to the server? Then you can just ssh or similar to login to the server. From my understanding the null modem cable is used primarily for accessing the boot console - no login. Failing that, you'd probably need a RAS setup; probably mpd, but you may get away with the base pppd. Network is probably you're quickest and easiest bet. HTH ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: serial consoles
On Sat, 24 Dec 2011, Matthew Luckie wrote: However, when I use cu on the laptop: sudo cu -l /dev/cuaU0 -s 9600 I never get a login prompt. If I press enter, the cursor scrolls down. Likewise other characters echo back. I'm reasonably sure that I'm connected to the appropriate com port on the server because if I plug it into the other com port and press enter, nothing happens. Might there be something else on the server using/trying to use that com port at the same time, like apcupsd? Running cu on the server (after resetting the config) would allow manually typing characters to see if they come out of the right port. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: serial consoles
On 12/25/11 04:45, Warren Block wrote: On Sat, 24 Dec 2011, Matthew Luckie wrote: However, when I use cu on the laptop: sudo cu -l /dev/cuaU0 -s 9600 I never get a login prompt. If I press enter, the cursor scrolls down. Likewise other characters echo back. I'm reasonably sure that I'm connected to the appropriate com port on the server because if I plug it into the other com port and press enter, nothing happens. Might there be something else on the server using/trying to use that com port at the same time, like apcupsd? Running cu on the server (after resetting the config) would allow manually typing characters to see if they come out of the right port. Thanks for your reply, Warren. I do run apcupsd, though it uses a usb port for communications with the UPS and is configured to do so. I turned apcupsd off in rc.conf, as well as commented out the getty line for the port, and rebooted the system. Then, I used cu on the server and found characters were sent both ways over the serial cable. I then added the /etc/ttys entry back and rebooted. When I used cu on the laptop it behaved as before -- i.e. no login prompt. If I tried using cu on the server, it timed out after about 10 seconds and said link down. Any further tips? I've put the server's apcupsd.conf, /etc/rc.conf, and dmesg.boot at http://www.wand.net.nz/~mluckie/apcupsd.conf http://www.wand.net.nz/~mluckie/rc.conf http://www.wand.net.nz/~mluckie/dmesg.boot Matthew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: serial consoles
On 12/25/11 01:17, Mehmet Erol Sanliturk wrote: Perhaps the following pages will be helpful : http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serial.html#SERIAL-CABLES-PORTS http://www.freebsddiary.org/serial-console.php Thank you very much . I've read them while trying to get this going. Just a comment on the freebsd handbook pages: they seem to still talk about the sio driver which I understand is deprecated in freebsd8. One thing I have not done is touch /boot/loader.conf. I'm not worried about seeing the system boot messages, just the ability to login after the system has booted -- i.e. I did not do step 2 of 27.6.2. Should I have? Matthew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: serial consoles
On Sat, Dec 24, 2011 at 1:15 PM, Matthew Luckie m...@luckie.org.nz wrote: On 12/25/11 01:17, Mehmet Erol Sanliturk wrote: Perhaps the following pages will be helpful : http://www.freebsd.org/doc/en_**US.ISO8859-1/books/handbook/** serialconsole-setup.htmlhttp://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html http://www.freebsd.org/doc/en_**US.ISO8859-1/books/handbook/** serial.html#SERIAL-CABLES-**PORTShttp://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serial.html#SERIAL-CABLES-PORTS http://www.freebsddiary.org/**serial-console.phphttp://www.freebsddiary.org/serial-console.php Thank you very much . I've read them while trying to get this going. Just a comment on the freebsd handbook pages: they seem to still talk about the sio driver which I understand is deprecated in freebsd8. One thing I have not done is touch /boot/loader.conf. I'm not worried about seeing the system boot messages, just the ability to login after the system has booted -- i.e. I did not do step 2 of 27.6.2. Should I have? Matthew I think , YES , because this statement will direct the output to serial port , please , also study the part 2 7.6.5.1 Setting a Faster Serial Port Speed to see messages on the server screen . Since you are using a COMPUTER , and NOT a DUMP TERMINAL , I think you should apply steps in the page : http://www.freebsddiary.org/serial-console.php As you know , serial console is a special hardware to communicate headless computers ( without keyboard and video terminal ) . Therefore , communication with a serial console and a computer are different concepts ( which I do not know exactly , but with respect to specifications , it seems like that ) . This means that , in the client computer ( as simulator of serial console ) , it is necessary to have a program to receive output inserted into serial port by the server , and display it for you like a serial console . If you use a USB port in the client and a converter from serial-to-USB , obviously , you need that your program should be able to manage USB port for that reason . I think management of USB port and RS 232 port are very different concepts ( approximately ) . These actions are performed by the serial console by itself . Myself , I will use two computers to simulate a serial console , because I asked price of a serial console , which come out as more than 800 Euro ( in Turkey ) . Thank you very much . Mehmet Erol Sanliturk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: serial consoles
On 12/25/11 07:46, Mehmet Erol Sanliturk wrote: On Sat, Dec 24, 2011 at 1:15 PM, Matthew Luckie m...@luckie.org.nz mailto:m...@luckie.org.nz wrote: One thing I have not done is touch /boot/loader.conf. I'm not worried about seeing the system boot messages, just the ability to login after the system has booted -- i.e. I did not do step 2 of 27.6.2. Should I have? Matthew I think , YES , because this statement will direct the output to serial port , please , also study the part $ cat /boot.config -D This was sufficient to get the setup I wanted -- the ability to login over a serial port should I want to. Sorry for the noise, this was all in the handbook. Matthew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Question about Serial consoles.
If I have 1 null modem cable hooked up as follows: server1:sio0 -- server2:sio0 and setup sio0 on both server 1 2 to be serial consoles, will that work? Or do i have to have 2 null modem cables and connect them as follows: server1:sio0 -- server2:sio1 server1:sio1 -- server2:sio0 Daryl __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: monitoring serial consoles (was Re: erorrs from spec_getpages)
On Sat, 18 Oct 2003, Dan Langille wrote: DL Moving this thread over to -questions, please don't include DL [EMAIL PROTECTED] in the reply agrred [but the please don't drop me from CC list, as I do not read -question ;)] DL That's why I always try to set up logged serial console for any machine with DL more than marginal importance. BTW, comms/conserver-com port is of great use DL for this purpose! DL DL I have an 8 port serial Boca card here, which I have yet to get DL running. How does comms/conserver-com work? I couldn't determine DL that from the FAQ. Does it need any hardware? How does it monitor DL the serial console? Do you connect two boxes together via their DL serial ports? Box A reports on Box B, and vice versa? DL DL Or does it just monitor the serial console and report back to a DL central server? For two machines each capable of 2 serial ports (usually, but it's not that obvious with modern mobos and/or server/19/compact platforms), I'd connect each sio0/com1 to other's sio1/com2 with null-modem cable, enable serial console and getty at ttyd0. For servers cluster, one of machines should be elected as comserver and equipped with pultiport card, other's sio0's connected to its multiport, and its own sio0 -- to sio1 somewhere. each machine with remote console target then runs comserver. In the simplest case of thw machines each conserver.cf would be like -- 8 -- # name:path:baud:logfile:mark:break LOGDIR=/var/log com1:/dev/cuaa0:9600p::30ma # %% # Access part # trusted: localhost host.domain.tld #allow: localhost woozle.rinet.ru host.domain.tld refuse: 0.0.0.0/0 -- 8 -- conservers could also be cascaded, but that's another beast story ;-) DL I assumed here that usually you have more than one machine per physical DL location; otherwise, I'd set up remote logging, preferrably to two different DL machines via two different interfaces, but such ideal network design is DL *rarely* reqchable ;-) DL DL I have one location which has only one box. That box and the DL bandwidth is kindly donated by BCHosting.com, and hosts DL freebsddiary.org, freshports.org, etc. It does about 45GB a month DL (at last check). I'd like to have a serial console there. But if it DL could the console remotely, that would be good. well, there are devices which do real _remote_ console job; I suppose you can politely ask BCHosting if they can setup such remote console for you; it can greatly simplify remote upgrades, for example. However, not any (read: rare) non-rackmount mobo is able to redirect, say, BIOS output to com port, so that you can't remotely tweak ACPI and/or memory timings... Good colocation support is almost always great; if you have good hardware support _in_addition_ to that, you can sleep much better ;-P Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
monitoring serial consoles (was Re: erorrs from spec_getpages)
Moving this thread over to -questions, please don't include [EMAIL PROTECTED] in the reply On 18 Oct 2003 at 19:39, Dmitry Morozovsky wrote: On Sat, 18 Oct 2003, Dan Langille wrote: [snip] DL Well I was in impression you've swapped out the disk, not cable, hence my DL assumption. Sure it may be wrong cable; however, I suppose at least some ATA DL errors should be logged somewhere before spec_getpages... DL DL They may have been, but they were not in /var/log/messages. If they DL were on the console, they were scrolled off the top. I couldn't DL scroll up because the keyboard hadn't been attached at boot, and I DL had not modified the kernel to allow for that situation. That's why I always try to set up logged serial console for any machine with more than marginal importance. BTW, comms/conserver-com port is of great use for this purpose! I have an 8 port serial Boca card here, which I have yet to get running. How does comms/conserver-com work? I couldn't determine that from the FAQ. Does it need any hardware? How does it monitor the serial console? Do you connect two boxes together via their serial ports? Box A reports on Box B, and vice versa? Or does it just monitor the serial console and report back to a central server? I assumed here that usually you have more than one machine per physical location; otherwise, I'd set up remote logging, preferrably to two different machines via two different interfaces, but such ideal network design is *rarely* reqchable ;-) I have one location which has only one box. That box and the bandwidth is kindly donated by BCHosting.com, and hosts freebsddiary.org, freshports.org, etc. It does about 45GB a month (at last check). I'd like to have a serial console there. But if it could the console remotely, that would be good. Cheers -- Dan Langille : http://www.langille.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
