From owner-freebsd-questions Fri Feb 1 6:56:30 2002 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 6370C37B405 for ; Fri, 1 Feb 2002 06:56:24 -0800 (PST) Received: from barbish ([63.70.155.57]) by mail.mango-bay.com (Post.Office MTA v3.5.3 release 223 ID# 0-52377U2500L250S0V35) with SMTP id com; Fri, 1 Feb 2002 09:59:58 -0500 From: "Joe & Fhe Barbish" To: "Chris O'Brien" Cc: "FBSD" Subject: RE: Internal Modem on COM 4 Date: Fri, 1 Feb 2002 09:56:19 -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: <5.1.0.14.0.20020201135117.009f5980@jpowered.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 First thing first. If the modem is not found during the boot probe process then there is no way user ppp can work. FBSD does not work with pci or isa bus winmodems. If you bought this modem for a windows system you are SOL. A FBSD pci modem must have onboard controller and dsp module. Cost around $80-$100 dollars. The boot messages are very short. To get more meaning full boot msgs do this, when the boot process stops for 10 seconds with msg to hit enter to continue, hit space bar, enter boot -v then enter. This will give you verbose boot messages. Look for you modem as a . If it is in the boot log as unknown it's either a winmodem or it has irq conflict in the pc bios. One common problem to look for is a AGP video card and the first pci slot sharing a irq. Do not put your modem or nic card in slot1 if you have a video card in the AGP slot. If you still have problems remove other expansion cards one at a time from PC until you get it found in boot log. Play with pc bios. -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Chris O'Brien Sent: Friday, February 01, 2002 8:55 AM To: freebsd-questions@FreeBSD.org Subject: Internal Modem on COM 4 Hello, I can not get my internal modem on com 4 to work. I have set the devices to cuaa3 and I made sure I enabled cuaa2 and cuaa3 on the kernal configuration and there was no conflicts. When I run ppp and type dial dialup nothing happerns. In FreeBSD it says cuaa3 is a bad file desciptor. I noticed when FreeBSD is booting up it does not find the device sio3. I saw in the FreeBSD handbook in the kernal configuration file section (chapter 9.4) that if you need to change the modem's IRQ from 9 to 2. I have 2 computers with the same problem and both have an Internal modem on COM 4. Can you tell me how to change the Modems IRQ from 9 to 2. Do I have to change the Jumpers in the computer or is there another way of solving this problem. Thank you, Chris O'Brien 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