From owner-freebsd-questions Sat Nov 20 21:58: 5 1999 Delivered-To: freebsd-questions@freebsd.org Received: from smtppop3.gte.net (smtppop3.gte.net [207.115.153.22]) by hub.freebsd.org (Postfix) with ESMTP id 5AA8D14C1B for ; Sat, 20 Nov 1999 21:58:02 -0800 (PST) (envelope-from chris.dahler@gte.net) Received: from laptop.my.domain (1Cust156.tnt1.denton.tx.da.uu.net [63.27.85.156]) by smtppop3.gte.net with SMTP ; id XAA4201205 Sat, 20 Nov 1999 23:57:15 -0600 (CST) From: Chris Dahler To: Marc Dodsworth Subject: Re: Serial Ports Problem Date: Sat, 20 Nov 1999 23:45:17 -0600 X-Mailer: KMail [version 1.0.20] Content-Type: text/plain Cc: freebsd-questions@FreeBSD.ORG References: <99112115054100.00382@zen.dodsworth.org> MIME-Version: 1.0 Message-Id: <99112023595400.02697@laptop.my.domain> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A lot of of the time with PCCARD modems and winmodems, they are recognised > by the software as comports rather than being physical com ports (i,e ones > built on the motherboard or through and external card) > Have you tried booting with a PCCARD enabled kernel to see what that comes > back with in relation to your PCCARD modem? Yes, I have compiled my kernel with pccard support. Your comment about software-recognized com ports (rather than physical ports) makes sense given the problems I am having. When FreeBSD is unable to detect anything other than sio0 (which is actually the physical port on the back of the computer), pccardd cannot detect the card modem (which is not a winmodem). When FreeBSD does detect sio2, pccardd correctly detects the card, but then it says it cannot allocate resources for the card - a whole other problem I was going to tackle next. What can I do to resolve this serial port problem, or is this another instance of a computer being designed for windows and nothing else? Chris Dahler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message