Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 14 Oct 2001 00:32:03 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 14 Oct 2001 00:31:53 -0400 Received: from ppp-RAS1-2-181.dialup.eol.ca ([64.56.225.181]:10763 "EHLO node0.opengeometry.ca") by vger.kernel.org with ESMTP id ; Sun, 14 Oct 2001 00:31:43 -0400 Date: Sun, 14 Oct 2001 00:31:36 -0400 From: William Park To: pd Cc: linux-kernel@vger.kernel.org Subject: Re: PCI modem doesn't work after 2.4.2->2.4.10 upgrade Message-ID: <20011014003136.A2031@node0.opengeometry.ca> Mail-Followup-To: pd , linux-kernel@vger.kernel.org In-Reply-To: <01101319043002.01369@gabrielle.pdickson.newboston.nh.us> <20011013190658.A32535@hapablap.dyn.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from pdickson@att.net on Sat, Oct 13, 2001 at 11:21:58PM -0400 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Oct 13, 2001 at 11:21:58PM -0400, pd wrote: > >Unlike 2.4.2, 2.4.10 can automatically detect and configure PCI modems. > >That's why its already in use to setserial. The kernel has already > >found your modem, and assigned it ttyS4 (0-3 are reserved for the > >standard COM1-4). Theoretically, then, all you have to do is relink > >/dev/modem to /dev/ttyS4, and you should be set. > > That is exactly what it turned out to be. Tnx. Works fine now. Hi pd, Which PCI modem do you have? -- William Park, Open Geometry Consulting, 8 CPU cluster, Linux (Slackware), Python, LaTeX, Vim, Mutt, Tin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/