From owner-freebsd-questions Fri Aug 16 11:10:12 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8418937B400 for ; Fri, 16 Aug 2002 11:09:57 -0700 (PDT) Received: from flashmail.com (flash2.flashmail.com [207.173.216.241]) by mx1.FreeBSD.org (Postfix) with SMTP id 439DA43E42 for ; Fri, 16 Aug 2002 11:09:53 -0700 (PDT) (envelope-from dcswest@flashmail.com) Received: (qmail 22290 invoked from network); 16 Aug 2002 18:09:29 -0000 Received: from unknown (HELO ip68-7-179-245.sd.sd.cox.net) (68.7.179.245) by 0 with SMTP; 16 Aug 2002 18:09:29 -0000 Subject: RE: kernel PPP with external serial modem From: "Dennis B." To: barbish@a1poweruser.com Cc: FreeBSD-questions@FreeBSD.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 16 Aug 2002 11:09:46 -0700 Message-Id: <1029521392.241.7.camel@localhost> Mime-Version: 1.0 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 Thanks for your reply! Tried user PPP too, which I originally avoided because I thought I heard it was less efficient, but couldn't get it to work either with only a different error message about some "default already exists." Definitely not using a WinModem either, but rather the Zoom 3049 external modem that your article even seems to recommend... On Fri, 2002-08-16 at 05:36, JoeB wrote: > You are trying to use kernel ppp. > This is out dated and has been replaced with user ppp which is much easier > to debug. > You may also be trying to use a winmodem which does not work on FBSD. > > > > > Internal modems are manufactured for two target markets, MS/Windows and > every thing else. Winmodems are cheep because the hardware controller > function is handled by the software you have to install into windows. > This hardware controller function is contained in a chip on the modem > circuit board. Winmodems are missing this chip and have a replacement > chip that directs the modem to use driver software running in the > windows system to perform the controller function. The most common > replacement chip is manufactured by Lucent. There are many versions of > this Lucent chip each version needing a different software driver version. > > Up until version 4.4, FBSD did not have any solution to using > Winmodems, but with the release of 4.4 the ports collection contains > the "Linux Winmodem 'ltmdm' driver" which was ported to FBSD. > This port is very poorly documented, only works with a limited > number of Lucent chip version, and is unreliable. Your whole internet > connection is managed by your modem and trying to shoe horn a modem > specially manufactured for the MS/Windows operating system into FBSD > is not the way to achieve a satisfactory dialup connection. > > ISA expansion slot internal modem sales has dropped off and have been > replaced with PCI expansion slot internal modems. PCI modems are > causing there own problems with FBSD because they are designed to use > the generic irq number 9. This is the floating irq used by windows for > reassignment to unused com port irq's. FBSD does not work this way. > You can find your self with irq conflicts because your motherboard is > also specially designed for the MS/Windows market and the bios assigns > irqs based on how windows will use them and not FBSD. This is true for > all modems and Nic cards which do not have onboard jumpers to select > irq numbers and in the case of modems, com ports. Sure you can fight > your way through irq conflicts by playing with the motherboard bio > setup. The more PCI devices you have plugged into the motherboard the > harder it is to get all of them working, if at all. > > The newest entry into the modem market is the USB modem. > FBSD supports USB plug in devices. It is not known for it's ease of use. > > To summarize. > For the FBSD newbe or for that matter any FBSD user who lacks the > experience of making a custom kernel or does not know how to install a > port, should use an external serial modem for connecting their FBSD box > to the internet. This method works using the default generic kernel, > creates no irq conflicts with the motherboard bios, and will work right > out of the box so to say. All serial modems use the PC's serial ports' > controller built into the motherboard. This has been the standard since > PCs first came out > > Trying to use a PCI internal winmodem and the Linux Winmodem 'ltmdm' > driver port is not for the newbe. The 'ltmdm' driver port installations > instructions are so inadequate as to make it imposable to get the ltmdm > port working on your modem. > > Stay away from USB phone modems and cable modems. > You will be glad you did. > > If you have to use a internal modem in FBSD, you have to get one that has an > onboard controller, preferable one that uses the PCI bus and has onboard > jumpers to select irq number and com port setting. Even under Windows > it's better to use a modem that has a hardware controller. > These cost around $100.00. > > I recommend the Zoom model 3049L external modem, works right out > of the box. > > PPP. > There are two ppp methods in FBSD for supporting modem dialup to ISP. > The oldest and hardest to use and debug is kernel ppp. Kernel ppp was > rewritten to remove all it's limitations and short comings, it's now > called user ppp. User ppp is what most of the FBSD community is using > to dialup their ISPs using phone modems. Kernel ppp is a waist of time. > > To setup user ppp do > edit /etc/ppp/ppp.conf section papchap > adding your ISP's phone number, account name, and password. > Start user ppp by entering ppp -ddial papchap on the command line, > and killall ppp to stop. > > How to determine if FBSD found my modem at boot time? > The Boot log /var/run/boot.log is where you find out if FBSD found > your modem. If you are using a external serial modem, then in the boot > log you would see some messages about sio0 and sio1 having there irq > number assigned, these are your PCs com port 1 and 2. For ISA and > PCI modems, If you see PCI device unknown, this means FBSD found your > modem during the probe process but could not match it to known devices > in it's device table. This generally means your modem is a winmodem. > If FBSD knows your modem it will replace the (unknown) keyword with the > description of your modem. This does not mean you will have a working > modem, it just means FBSD found it during the probe and has it listed > in it's internal table. This is where you have to check out the irq > number assigned by the PCs bios. During the PC hardware boot process > the Bios summary screen should be displayed. You have to check this > display to verify that your modem is not sharing it's bios assigned irq > number with another device. Some times turning off the bio's > plug-n-play option will allow you to assign irq numbers to devices. > Setup bios have different options depending on the motherboard > manufacture. Best advice is to play a round with bio setting until the > summary screen shows the Nic and modem cards are not sharing irq's > with other devices. > They have to have exclusive use of the assigned irq number. > > The final test is to use the tip program to talk directly to the modem. > Enter tip com1 or com2 to connect to the external serial modem, > or tip com3 or com4 to connect to internal ISA or PCI modems. > If the tip command responds with the connected message then your > modem is functioning correctly. Try entering the Hayes at command, > the modem should answer with ok. > Use ~ followed by ctrl + d keys at same time to exit tip command. > > > If you are still having problems post your > /var/run/boot.log /etc/ppp/ppp.conf /var/log/ppp.log > and I will look then over to try to determine your problem. > > > > > > > -----Original Message----- > From: owner-freebsd-questions@FreeBSD.ORG > [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Dennis B. > Sent: Wednesday, August 14, 2002 1:41 PM > To: FreeBSD-questions@FreeBSD.org > Subject: kernel PPP with external serial modem > > Greetings; > > Trying to set up someone with internet access who's interested in trying > out FreeBSD, but only with dial-up access which I've never set up > through FreeBSD. > > Went with a Zoom 3049 V.92 on com A/com 1/irq 4 of a Pentium !!! 600 > system and configurations as follows: > > /etc/resolv.conf as follows: > > nameserver > nameserver > > /etc/ppp/options as follows: > > /dev/cuaa0 115200 > crtscts > modem > connect "/usr/bin/chat -f /etc/ppp/login.chat.script" > noipdefault > passive > domain > defaultroute > > /etc/ppp/login.chat.script as follows: > > ABORT BUSY ABORT 'NO CARRIER' "" AT+VCID=1 &F OK ATDT > CONNECT "" TIMEOUT 10 ogin:-\\r-ogin: TIMEOUT 5 sword: > > > Upon typing "pppd" through the root shell, the TD and RD light(s) on the > modem go out as the TR light on the modem comes on and after a few good > seconds of not hearing any sort of dial-up, the TD and RD light(s) come > back on as the TR light then stays on whereas the root shell then > returns the error message "connect script failed." It also creates a > file /etc/ppp/connect-errors with nothing in it and posts the same error > message to /var/log/messages > > Just not sure any more and hoping it looks familiar enough to someone, > > > 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