RE: Connecting to serial port
From: Ted Mittelstaedt [EMAIL PROTECTED] To: Steve Douville [EMAIL PROTECTED], freebsd-questions@freebsd.org Subject: RE: Connecting to serial port Date: Sat, 11 Feb 2006 00:51:12 -0800 That happens, you can try a BIOS update, and also make sure your motherboard CMOS settings specify the port for serial0, and match port 0x3f8-0x3ff irq 4, and aren't set to auto. You can also try changing the setting for plug-and-play OS to off, (or on, if it was off before) You can ignore the message: configured irq 4 not in bitmap of probed irqs 0 as long as your serial port actually responds. A lot of motherboards will emit this message but the serial port still works. Unfortunately it looks like yours isn't one of these due to the not responding error message. Worst case, disble the motherboard serial ports and buy a pci serial port card. This seems to happen a lot on systems that use pci-express, probably because they are tying the serial port hardware to the pci bus rather than the isa bus. Ted Hi: I'm having this same problem with a new Abit AN8 MB, which has the pciexpress. I've tried changing the BIOS settings like suggested, PLUS, even trying a PCI card, but still the same no response. Does anyone have this MB and cured this problem? If so, please let me know as I really need that lost serial port for the UPS (no, USB won't drive it). Thanks. Best regards, Jack _ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Connecting to serial port
That happens, you can try a BIOS update, and also make sure your motherboard CMOS settings specify the port for serial0, and match port 0x3f8-0x3ff irq 4, and aren't set to auto. You can also try changing the setting for plug-and-play OS to off, (or on, if it was off before) You can ignore the message: configured irq 4 not in bitmap of probed irqs 0 as long as your serial port actually responds. A lot of motherboards will emit this message but the serial port still works. Unfortunately it looks like yours isn't one of these due to the not responding error message. Worst case, disble the motherboard serial ports and buy a pci serial port card. This seems to happen a lot on systems that use pci-express, probably because they are tying the serial port hardware to the pci bus rather than the isa bus. Ted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Steve Douville Sent: Friday, February 10, 2006 9:25 PM To: freebsd-questions@freebsd.org Subject: Connecting to serial port I'm trying to connect to the serial port of a Dell PowerConnect 3024. I've connected a null modem cable between them. During boot, this is what is happening: Feb 11 00:34:17 server2 kernel: sio0: configured irq 4 not in bitmap of probed irqs 0 Feb 11 00:34:17 server2 kernel: sio0: port may not be enabled Feb 11 00:34:17 server2 kernel: sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Feb 11 00:34:17 server2 kernel: sio0: type 8250 or not responding Can anyone shed some light on what I might have done wrong or where to continue looking? Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.15.5/256 - Release Date: 2/10/2006 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Connecting to serial port
I'm trying to connect to the serial port of a Dell PowerConnect 3024. I've connected a null modem cable between them. During boot, this is what is happening: Feb 11 00:34:17 server2 kernel: sio0: configured irq 4 not in bitmap of probed irqs 0 Feb 11 00:34:17 server2 kernel: sio0: port may not be enabled Feb 11 00:34:17 server2 kernel: sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Feb 11 00:34:17 server2 kernel: sio0: type 8250 or not responding Can anyone shed some light on what I might have done wrong or where to continue looking? Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Connecting to serial port using HyperTerminal
I see the Terminals docs in the handbook for connecting to the serial port. It looks as if maybe my FreeBSD 5.2 has getty up and running with several instances: 64553 v0 Is+0:00.00 /usr/libexec/getty Pc ttyv0 808 v1 Is+0:00.00 /usr/libexec/getty Pc ttyv1 809 v2 Is+0:00.00 /usr/libexec/getty Pc ttyv2 810 v3 Is+0:00.00 /usr/libexec/getty Pc ttyv3 811 v4 Is+0:00.00 /usr/libexec/getty Pc ttyv4 812 v5 Is+0:00.00 /usr/libexec/getty Pc ttyv5 813 v6 Is+0:00.00 /usr/libexec/getty Pc ttyv6 814 v7 Is+0:00.00 /usr/libexec/getty Pc ttyv7 What do I need to do more to allow the connection from my Windows machine in HyperTerminal? I've tried various settings, can someone suggest the correct settings? -- Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Connecting to serial port using HyperTerminal
On Oct 19, 2004, at 9:46 PM, Robert Fitzpatrick wrote: I see the Terminals docs in the handbook for connecting to the serial port. It looks as if maybe my FreeBSD 5.2 has getty up and running with several instances: 64553 v0 Is+0:00.00 /usr/libexec/getty Pc ttyv0 808 v1 Is+0:00.00 /usr/libexec/getty Pc ttyv1 809 v2 Is+0:00.00 /usr/libexec/getty Pc ttyv2 810 v3 Is+0:00.00 /usr/libexec/getty Pc ttyv3 811 v4 Is+0:00.00 /usr/libexec/getty Pc ttyv4 812 v5 Is+0:00.00 /usr/libexec/getty Pc ttyv5 813 v6 Is+0:00.00 /usr/libexec/getty Pc ttyv6 814 v7 Is+0:00.00 /usr/libexec/getty Pc ttyv7 What do I need to do more to allow the connection from my Windows machine in HyperTerminal? I've tried various settings, can someone suggest the correct settings? -- Robert The tty*v* means they're virtual terminals. You need to enable the serial console in /etc/ttys. The line you need (which needs to be uncommented) should look like this: ttyd0 /usr/libexec/getty std.9600 vt100 on secure Then you need to reHUP your getty process. HTH - Eric F Crist Secure Computing Networks PGP.sig Description: This is a digitally signed message part
Re: Connecting to serial port using HyperTerminal
ttyd0 /usr/libexec/getty std.9600 vt100 on secure I found an existing line for ttyd0 set for dailup and off, I replaced it with the one you suggested. Now, the ttyd0 shows up in the processes running, but still no luck connecting. I have things set to 9600 baud with 8|None|1|Hardware and VT100 emulation. But no response. -- Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Connecting to serial port using HyperTerminal
On Oct 19, 2004, at 10:08 PM, Robert Fitzpatrick wrote: ttyd0 /usr/libexec/getty std.9600 vt100 on secure I found an existing line for ttyd0 set for dailup and off, I replaced it with the one you suggested. Now, the ttyd0 shows up in the processes running, but still no luck connecting. I have things set to 9600 baud with 8|None|1|Hardware and VT100 emulation. But no response. -- Robert Maybe something trivial, but are you sure you're using a null modem cable? this is necessary... - Eric F Crist Secure Computing Networks PGP.sig Description: This is a digitally signed message part
Re: Connecting to serial port using HyperTerminal
ttyd0 /usr/libexec/getty std.9600 vt100 on secure I found an existing line for ttyd0 set for dailup and off, I replaced it with the one you suggested. Now, the ttyd0 shows up in the processes running, but still no luck connecting. I have things set to 9600 baud with 8|None|1|Hardware and VT100 emulation. But no response. -- Robert Maybe something trivial, but are you sure you're using a null modem cable? this is necessary... Yeah, the cable works connecting to a Linux box I have... -- Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Connecting to serial port using HyperTerminal
Robert Fitzpatrick wrote: ttyd0 /usr/libexec/getty std.9600 vt100 on secure I found an existing line for ttyd0 set for dailup and off, I replaced it with the one you suggested. Now, the ttyd0 shows up in the processes running, but still no luck connecting. I have things set to 9600 baud with 8|None|1|Hardware and VT100 emulation. But no response. -- Robert Maybe something trivial, but are you sure you're using a null modem cable? this is necessary... Yeah, the cable works connecting to a Linux box I have... Is the serial port enabled (BIOS kernel)? Do you get positive output when you do $ cat /var/run/dmesg.boot | grep sio[[:digit:]] f.ex: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A In /etc/ttys ttyd0 /usr/libexec/getty std.9600 dialup off secure means first serial port; cable is connected to that port? Rob. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
