Date: Tue, 19 May 2009 19:55:01 +0200 From: Marius Strobl <marius@alchemy.franken.de> To: Steve Scally <steve@kcilink.com> Cc: freebsd-sparc64@freebsd.org Subject: Re: Serial Port Troubleshooting Message-ID: <20090519175501.GA65063@alchemy.franken.de> In-Reply-To: <43658782-451B-4B3E-9F59-6E04409AFAA1@kcilink.com> References: <43658782-451B-4B3E-9F59-6E04409AFAA1@kcilink.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 18, 2009 at 11:49:14AM -0400, Steve Scally wrote: > Hello, > > I currently have two machines one Ultra60 and one Dell GX400. Both > of these boxes have two serial ports. Currently port A on the Sun > goes to com2 on the Dell and com1 on the Dell goes to port B on the > Sun. I upgraded my Ultra60 to FreeBSD 7.2 from 7.0 last night using > the serial connection from the Dell box. However now when trying to > connect from the Sun to the Dell I only receive the "connected" string > and no prompt. I also tried connecting to the Dell from the Sun and > then rebooting the dell from another terminal. When the Dell box > reaches the multi-user prompt the terminal window with the serial > connection receives a question mark, "?." Does this imply that the low-level console works, i.e. you get the dmesg output of the kernel etc. but at the point getty(8) should take over things break? Does the other way work, i.e. can you login in to the Sun from the Dell machine? What happens if you connect each machine to itself and try to log in? Have you tried with something different than cu(1), f.e. minicom from ports? > My boot.config and ttys > files have not changed and I did test that it was working prior to > upgrading the Sun. I read through the freebsd docs however most of it > is just the setup and "it should work". When I initially set this up > it did work just as it was written. I was wondering if I missed any > changes in 7.2 for the serial ports or if there is any other > documentation to look at for troubleshooting serial port connections. > Is there is a script or more debugging I can turn on to see where > exactly the connection is failing? Not as far as I can tell. > I have included snips of my dmesg > and boot.config and ttys file. Let me know if you need more info or > the full listings. > I haven't troubleshooted serial port issues before and apologize if I > missed something obvious. > > Thank you for your help. > > I use the following commands to connect. > > Sun Terms > root 900 0.0 0.2 5880 1176 u1 Is+ 11:46PM 0:00.02 /usr/ > libexec/getty std.9600 ttyu1 > root 732 0.0 0.2 5880 1168 v1 Is+ 11:26PM 0:00.01 /usr/ > libexec/getty Pc ttyv1 > root 733 0.0 0.2 5880 1168 v2 Is+ 11:26PM 0:00.01 /usr/ > libexec/getty Pc ttyv2 > > Dell Terms > root 896 0.0 0.1 1352 948 d0 Is+ 8:51PM 0:00.01 /usr/ > libexec/getty std.9600 ttyd0 > root 762 0.0 0.1 1352 948 v1 Is+ 8:11PM 0:00.00 /usr/ > libexec/getty Pc ttyv1 > root 763 0.0 0.1 1352 948 v2 Is+ 8:11PM 0:00.00 /usr/ > libexec/getty Pc ttyv2 > > From the Sun to the Dell > > cu -l /dev/cuau0 > > From Dell to Sun > > cu -l /dev/cuad1 > > > Sun Files > > FreeBSD 7.2-RELEASE #1: Sun May 17 14:00:45 EDT 2009 > root@etch.helios.local:/usr/obj/usr/src/sys/GENERIC > cpu0: Sun Microsystems UltraSparc-II Processor (450.03 MHz CPU) > scc0: <Siemens SAB 82532 dual channel SCC> addr > 0x1400400000-0x140040007f irq 43 on ebus0 > scc0: [FILTER] > uart0: <SAB 82532 v3.2, channel A> on scc0 > uart0: [FILTER] > uart0: CTS oflow > uart1: <SAB 82532 v3.2, channel B> on scc0 > uart1: [FILTER] > uart1: CTS oflow > uart1: console (9600,n,8,1) > uart2: <16550 or compatible> addr 0x14003083f8-0x14003083ff irq 41 on > ebus0 > uart2: [FILTER] > uart2: keyboard (1200,n,8,1) > uart2: keyboard not present > uart3: <16550 or compatible> addr 0x14003062f8-0x14003062ff irq 42 on > ebus0 > uart3: [FILTER] > > boot.config > -Dh > > /etc/ttys > > # Serial terminals > # The 'dialup' keyword identifies dialin lines to login, fingerd etc. > # uart(4) > ttyu0 "/usr/libexec/getty std.9600" dialup off secure > ttyu1 "/usr/libexec/getty std.9600" vt100 on secure > ttyu2 "/usr/libexec/getty std.9600" vt100 off secure > ttyu3 "/usr/libexec/getty std.9600" vt100 off secure > > Dell Files > > FreeBSD 7.2-RELEASE #1: Sun May 17 22:22:58 EDT 2009 > sscally@buzz.helios.local:/usr/obj/usr/src/sys/GENERIC > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 > on acpi0 > sio0: type 16550A, console > sio0: [FILTER] > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > sio1: [FILTER] > > boot.config > -Dh > > /etc/ttys > > # Serial terminals > # The 'dialup' keyword identifies dialin lines to login, fingerd etc. > ttyd0 "/usr/libexec/getty std.9600" vt100 on secure > ttyd1 "/usr/libexec/getty std.9600" dialup off secure > ttyd2 "/usr/libexec/getty std.9600" dialup off secure > ttyd3 "/usr/libexec/getty std.9600" dialup off secure > > _______________________________________________ Marius
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090519175501.GA65063>