Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!darwin.sura.net!howland.reston.ans.net!sol.ctr.columbia.edu!usenet.ucs.indiana.edu!bigbang.astro.indiana.edu!pitts From: pitts@bigbang.astro.indiana.edu (Jim Pitts) Subject: Re: Modem not work under FreeBSD :-( Message-ID: <CE12z2.2on@usenet.ucs.indiana.edu> Sender: news@usenet.ucs.indiana.edu (USENET News System) Nntp-Posting-Host: bigbang.astro.indiana.edu Organization: Indiana University Astrophysics, Bloomington, IN References: <1993Sep27.155651.21828@uxmail.ust.hk> Date: Mon, 27 Sep 1993 19:47:23 GMT Lines: 80 In article <1993Sep27.155651.21828@uxmail.ust.hk> cs089613@uxmail.ust.hk (Lam Ho Ming (BACS3 Class A)) writes: >Hi Guys, >D > I just upgrade from 386bsd 0.1 to FreeBSD, every thing is nice except >with my modem, can anybody tell me what device (com or sio, or cua) should I >use? and can anybody tell me the step in getting the modem to work under Free- >BSD. When I was using 386BSD, I used com1 (com2 in DOS) and every thing works >well, however, under FreeBSD, when I look at the /etc/remote file, the last >two lines start with "com00.......; com01........" something like this, I >change these to sio00, sio01, and use the "cu" command using sio01 (com2 in >DOS) and the connect message appeared. However, when I start typing, "Input/ >Output error" appear and then disconnected. > The sio device drivers are one of the great things about FreeBSD. The com devices are never used now (that I know of). sio is really cool. I too had the same problems as you. I would suggest: # cd /dev # sh MAKEDEV sio00 # sh MAKEDEV sio01 # stty -f /dev/sio01 19200 clocal # tip modem (I assume that in /etc/remote you have defined host 'modem' and the modem is on com2 which is sio01 ... com1 is sio00.) The /etc/remote file that is distributed is incorrect as it sets up com1 and com2, neither of which are used in the distributed kernel. Your serial ports in the distributed kernel are sio01 and sio02. If for some sick reason you must have com1 and com2 you can get them by editing your kernel config and changing the devices from sio to com ports. You must recompile your kernel and replace the exsisting one. If you want to do this and do not have the disk space (many people don't), I would be glad to compile one for you and mail it to you. Just let me know and send the kernel config file you want to use. Every time I go to use the modem I have to do: # stty -f /dev/sio01 clocal To get tip to work correctly with the modem. It is a pain but it works. The plus here is that once it works, ppp and slip work witout a hitch, you will never see (I hope) a silo overflow, and zmodem runs without a hitch. I run ftp, telnet, run remote X applications and yes play netrek without any problems. These would not work with slip and the brain dead serial drivers on BSD386 or NetBSD. > > I know there is some news in this group have already discussed this >aspect, but they are not so detailed, (please forgive my ignorance) can >anybody please kindly tell me the solutions about this? I prefer FreeBSD than >386BSD but I really need to use my modem under it, please help. > I prefer FreeBSD as well by a long shot. Perhaps the others will improve with time, but FreeBSD-1.0-GAMMA seems to be the most mature of the 3 at the present time. I think NetBSD is a close second. BSD386 should be scrapped as FreeBSD has everything it as plus lots more and many fixes beyond the patch kit. Everyone handles this subject with gloves as to which one is better, but I really don't think it is necessary. FreeBSD seems to come out on top as far as I am concerned ... no contest. I am sure that comment will generate lots of noise. As if I don't get enough mail as it is ... ;) > > Looking forwards to hearing good news from you and thank you very much >for your kindly attention. Thanks in advance. > Feel free to E-Mail me for help: pitts@bigbang.astro.indiana.edu Best regards. Jim Pitts