From owner-freebsd-questions Sat Feb 27 12:50:20 1999 Delivered-To: freebsd-questions@freebsd.org Received: from dorm-36314.rh.uh.edu (Dorm-36314.RH.UH.EDU [129.7.141.218]) by hub.freebsd.org (Postfix) with ESMTP id 848DA15174 for ; Sat, 27 Feb 1999 12:50:18 -0800 (PST) (envelope-from wotan@dorm-36314.rh.uh.edu) Received: from localhost (wotan@localhost) by dorm-36314.rh.uh.edu (8.9.2/8.9.2) with ESMTP id OAA07612 for ; Sat, 27 Feb 1999 14:49:31 -0600 (CST) (envelope-from wotan@dorm-36314.rh.uh.edu) Date: Sat, 27 Feb 1999 14:49:25 -0600 (CST) From: Jonathan Fosburgh Reply-To: jef53313@bayou.uh.edu To: questions@freebsd.org Subject: Modem ceased to work following 2.2.8 -> 3.1 upgrade Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This perhaps belongs on -stable since I didn't check it until after upgrading from 3.1-RELEASE to 3.1-STABLE, but I post it here in case this is of more general interest. My modem worked just fine all through the 2.2.x, and my upgrade from 2.2.6 -> 2.2.8 was accomplished by modem (due to lack of a working ethernet card.) Recently, I attempted to install hylafax and this is when I first noticed the problem. Running the setup utilities failed to communicate with the modem. I tried using ppp in term mode and could not send commands to the modem, and I also tried kermit's equivalent of term mode and had the same problem. My modem is on sio1 and my ppp is set up for /dev/cuaa1, which is where it has always worked. I also tried /dev/cuaa0 and had the same lack of success. Here is what my kernel config has (based on the man sio entry): device sio0 at isa? port "IO_COM1" tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 And here is dmesg sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio0 is where my serial mouse used to be until my MB was upgraded, and the modem has been used since the upgrade so I doubt it is a hardware/bios problem. Have I misconfigured the kernel or did I just pick up some bad sources? Jonathan Fosburgh Geotechnician Snyder Oil Corporation Houston, TX Home Page: http://www.geocities.com/vienna/1498 Manager, FreeBSD Webring: http://www.geocities.com/vienna/1498/computer/freebsdring.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message