Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!solace!eru.mt.luth.se!www.nntp.primenet.com!nntp.primenet.com!howland.erols.net!sol.ctr.columbia.edu!startide.ctr.columbia.edu!wpaul From: wpaul@ctr.columbia.edu (Bill Paul) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: I must be a putz...no modem recognition. Date: 9 Dec 1996 17:54:41 GMT Organization: Columbia University Center for Telecommunications Research Lines: 83 Message-ID: <58hjp1$bb@sol.ctr.columbia.edu> References: <32AB6E90.1C63@nwlink.com> NNTP-Posting-Host: startide.ctr.columbia.edu X-Newsreader: TIN [version 1.2 PL2] Daring to challenge the will of the almighty Leviam00se, cjay (cjay@nwlink.com) had the courage to say: : Hello again. : I have one last question to ask of you all before I take the plunge into : UNIX land for the week. : Upon installing FreeBSD 2.1.6 with minimal files (bin, doc, manpages) I : tried to go and grab some additional packages like lynx, pdksh, etc. : However....I cannot talk to my modem (USR Sportster 33.6 at 3e8, irq4) : with the "ppp" program. I need to be able to so that I can access : online resources/help files. As you can imagine, it's a bit of a pain : to boot into FreeBSD, play around, find something thats not covered in : the man pages, boot into Win95, find the info, boot into FreeBSD, test : it out, play somemore, boot Win95, etc, etc, etc. <BG> : I have sio0 disabled (com1 has an external 14.4 that I use for : text-based systems [BBSes]) which I don't need while using FreeBSD. I : have a serial mouse on sio1 (configured for 2f8, IRQ3), and the : Sportster is on sio2 (configured for 3e8, IRQ4). No conflicts as far as : hardware goes. The GENERIC kernel expects serial ports to be configured as follows: device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? port "IO_COM3" tty irq 5 vector siointr device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr Here, COM1 == 0x3f8, COM2 == 0x2f8, COM3 = 0x3e8 and COM4 == 0x2e8. Note that each one is set to use a particular I/O address and IRQ. In order for your modem to be detected, its configuration and the kernel's configuration must agree, _and_ there must be no conflicts with other hardware. NOTE: in 2.1.6, you may also find that sio2 and sio3 are disabled by default. This is to avoid a conflict with certain graphics adapters. (Actually, it may just be sio3 that's disabled.) If this is the case, then you need to re-enable it by booting with -c and using the userconfig utility to turn it back on. You say your modem is at 0x3e8, IRQ 4: this is not a combination that the kernel knows to search for. You say you also have another modem on COM1 which you don't use in FreeBSD. But COM1 usually also uses IRQ 4. Now, this isn't MS-DOG or Lose95: you can't have two pieces of hardware installed in the machine using the same IRQ. Period. I don't care if you 'aren't using the modem on COM1.' It doesn't matter: all three of these devices must be on seperate I/O addresses with unique IRQs. There are a couple of ways to get your high speed modem to work: - The easiest: see if the fast modem allows you to choose an IRQ besides 3 or 4. If it allows another setting, like 5 or 9, then use that. If you can set it to 5, then it will match the entry for sio2 and, assuming it's enabled, the kernel should see it. If it allows a different IRQ, but not 5 or 9, then choose the new IRQ and use the userconfig utility (Boot: -c) to change the kernel configuration to match. - A slightly more complicated way is to turn off the serial port an COM1 using your machine's CMOS config. Some systems don't let you configure serial ports like this, forcing you instead to move jumpers on your motherboard or serial I/O card. Once you do this, then you can either change your high speed modem so that it uses COM1 (0x3f8, IRQ 4) or use the userconfig utility (Boot: -c) to change the configuration for sio2 so that it uses 0x3e8 IRQ4 instead of the default 0x3e8 IRQ5. (You can also recompile the kernel for this, but you'd need to download the kernel source code first. :) In all cases, watch for sio0, sio1 or sio2 to be probed by the kernel at boot time. If it doesn't see it the right serial port, then no amount of frobbing with the tty/cua devices will work. For the record, sio0 is /dev/cuaa0, sio1 is /dev/cuaa1 and sio2 is /dev/cuaa2. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "If you're ever in trouble, go to the CTR. Ask for Bill. He will help you." =============================================================================