From owner-freebsd-questions Sat May 23 01:45:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22190 for freebsd-questions-outgoing; Sat, 23 May 1998 01:45:44 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from lucy.bedford.net (lucy.bedford.net [206.99.145.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22184 for ; Sat, 23 May 1998 01:45:39 -0700 (PDT) (envelope-from listread@lucy.bedford.net) Received: (from listread@localhost) by lucy.bedford.net (8.8.8/8.8.8) id EAA26278; Sat, 23 May 1998 04:33:33 -0400 (EDT) (envelope-from listread) Message-Id: <199805230833.EAA26278@lucy.bedford.net> Subject: Re: PnP modems, etc. In-Reply-To: <01BD8590.76474910@MANNY> from Dave Bender at "May 22, 98 02:46:51 pm" To: bendede@startribune.com (Dave Bender) Date: Sat, 23 May 1998 04:33:33 -0400 (EDT) Cc: questions@FreeBSD.ORG Reply-to: djv@bedford.net From: CyberPeasant X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dave Bender wrote: > With pointers and prodding from the fine folks on this mailing list, I learned to build a custom kernel configured to Plug and Play devices. Seems to work, and it wasn't too painful. But a question: > > In my dmesg, I get these lines: > > Probing for PnP devices: > CSN 1 Vendor ID: USR1004 [0x04107256] Serial 0x69612786 > CSN 2 Vendor ID: TCM5098 [0x98506d50] Serial 0x4b7455f9 > Probing for devices on the ISA bus: > ... > > What are those lines telling me? And what's my next step in communicating with my modem? How do I know which COM port/IRQ the PnP system put the modem on? > > It is a US Robotics (model 5683) "winmodem", so I'd guess the CSN1 line is the modem. What that other thing is on the second line, I don't know. Didn't think I had other PnP devices on this old box! Any way to find out? AAAAAAAAAArgh. It's a winmodem! Sorry, those don't work with any Unix, to my (incomplete) knowledge. If you can, exchange it for a "real" one. Or sell it to a Windows user. Winmodems use the CPU to do all their work, saving the manufacturer a few cents, and allowing the use of proprietary (mandatory) drivers and operating system. This CPU-abuse renders them unsuited to a multitasking OS. There seems to be no interest in writing a driver for them. Dave -- Is the true purpose of Unix its use, or its administration? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message