From owner-freebsd-questions Thu Dec 27 18:16: 7 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.mango-bay.com (mail.mango-bay.com [208.206.15.12]) by hub.freebsd.org (Postfix) with ESMTP id 9F0C237B419 for ; Thu, 27 Dec 2001 18:15:57 -0800 (PST) Received: from barbish ([63.70.155.123]) by mail.mango-bay.com (Post.Office MTA v3.5.3 release 223 ID# 0-52377U2500L250S0V35) with SMTP id com; Thu, 27 Dec 2001 21:18:11 -0500 From: "Joe & Fhe Barbish" To: "Robin Hall" Cc: "FBSD Questions" Subject: RE: Modem device not configured Date: Thu, 27 Dec 2001 21:15:53 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20011228013559.10608.qmail@web20509.mail.yahoo.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG You are the user who the 3.x setserial command was designed for. Your only option is to get a external modem and write a bug report to FBSD. http://www.freebsd.org/send-pr.html -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Robin Hall Sent: Thursday, December 27, 2001 8:36 PM To: Joe & Fhe Barbish Cc: FBSD Questions Subject: RE:Modem device not configured I am sorry I should have said earlier. This modem is not PNP. I can't find anything that is really pertinant on this page. I have an AOpen FM56-ITU/2 modem. Robin E. Hall --- Joe & Fhe Barbish wrote: > You are in a hole caused by very poor management of > FBSD change control. At > 4.0 a change was allowed in to stop a conflict > between isa and pci internal > modem hardware probing. This change for all purposes > closed the door for pci > internal modems. There used to be the pnp, > setserial, and pnpinfo commands > which allowed you to hack around the isa prob > results to get a pci internal > modem to work. Now all that is deactivated and pci > modems users are left out > in the cold. Maybe if enough people write problem > reports this will get > fixed. One would think that 2 years would have been > enough time to get this > fixed since 4.0 came out. If your modem is a isa > modem then you should be > able to get it working following the FAQ at this > url. > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#PNP-N > OT-FOUND > > > > -----Original Message----- > From: owner-freebsd-questions@FreeBSD.ORG > [mailto:owner-freebsd-questions@FreeBSD.ORG]On > Behalf Of Robin Hall > Sent: Thursday, December 27, 2001 7:46 PM > To: freebsd-questions@FreeBSD.org > Subject: Re: device not configured > > Ok I moved the jumpers on my modem to com 2 or cuaa1 > or sio1 whichever it is. > Now when I boot up to install freeBSD 4.4 stable it > gets to the point of > detecting hardware and just stays there. Does BSD > not > like modems? How am I > supposed to install this so that I can use it as a > router with a dialup > connection? Why would it freeze on detecting > hardware > if I have the modem set > to cuaa1? When I was getting it installed it > wouldn't > install kde or any > windowmanager. I did get it to startx with just the > bare bones x. I have 24 > MB of Ram is this enough to use a window manager? > > Robin E. Hall > > On Wed 26 Dec 01 12:10, Andrew C. Hornback wrote: > > > -----Original Message----- > > > From: owner-freebsd-questions@FreeBSD.ORG > > > [mailto:owner-freebsd-questions@FreeBSD.ORG]On > Behalf Of Robin Hall > > > Sent: Wednesday, December 26, 2001 6:36 AM > > > To: freebsd-questions@FreeBSD.org > > > Subject: RE: device not configured > > > > > > > > > I have an internal AOpen modem. This is a > hardware > > > modem. I have the jumpers set to com 3 in > windows > > > which is ttyS0 in linux and should be cuaa2 in > > > freeBSD. Why isn't this showing up on the > correct > > > port? > > > > > > Robin E. Hall > > > > If you're using the GENERIC kernel, it only > supports devices on classical > > COM 1 and COM 2. To support any other COM ports, > you need to compile a new > > kernel with support for those ports. A look at > the > GENERIC config file > > should of assistance. > > > > --- Andy > > > ===== > > Robin E. Hall > rob33_me@yahoo.com > > > __________________________________________________ > Do You Yahoo!? > Send your FREE holiday greetings online! > http://greetings.yahoo.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of > the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of > the message __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message