From owner-freebsd-hackers Sat Nov 7 22:27:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA07631 for freebsd-hackers-outgoing; Sat, 7 Nov 1998 22:27:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07626; Sat, 7 Nov 1998 22:27:08 -0800 (PST) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id WAA09353; Sat, 7 Nov 1998 22:26:59 -0800 (PST) Message-ID: <19981107222659.L25743@Alameda.net> Date: Sat, 7 Nov 1998 22:26:59 -0800 From: Ulf Zimmermann To: the beavix , current@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: Re: Serial port oddnesses in -CURRENT Reply-To: ulf@Alameda.net References: <19981108060318.1627.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981108060318.1627.qmail@hotmail.com>; from the beavix on Sat, Nov 07, 1998 at 10:03:18PM -0800 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have an Intel DK440LX motherboard, there if I disable the serial ports, they get seen, but don't work when I try to use them. On Sat, Nov 07, 1998 at 10:03:18PM -0800, the beavix wrote: > Hi guys, > > I've got an Intel PR440FX dual-PPro motherboard, and am having some > problems regarding serial ports in -CURRENT (which I built 3 days ago). > > Nov 8 13:53:34 ether /kernel: sio1: 1 more silo overflow (total 121) > > That's the 121st message I've got so far, and pppd has only been running > for <10 minutes. I think I might have traced the problem, here's a quick > snippet from dmesg: > > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > sio0: type 8250 > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > > Now what puzzles me if that any serial port should complain, it should > be sio0, not sio1. What is similarly strange is that sio1 is not being > used, it's been disabled in the BIOS. > > All I am running is an external Banksia 56k modem (connecting at 33k6), > which hangs off of sio0 on the board. For one reason or another, BIOS > won't let me set sio0 to use COM1 (even though I have a PS/2 mouse), so > I'm stuck with COM2 for sio0. sio1 has been set to disabled in the BIOS, > and there's nothing hanging off of the connector. > > Here I am puzzled. You can't use an external modem on a serial port if > it's disabled, so why am I getting sio1 errors when the modem is using > sio0? > > I've tried disabling sio0 and using sio1 from the BIOS, but this hasn't > worked either. sio1 can take COM2 if sio0 is disabled; and when I try > this, cu just sits there with "Connected" but doesn't take input. The > modem doesn't seem to respond. > > Any ideas? Info would be greatly appreciated! > > -- > > beav. > > ______________________________________________________ > Get Your Private, Free Email at http://www.hotmail.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message