Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!solace!eru.mt.luth.se!bloom-beacon.mit.edu!news.mathworks.com!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Weird Serial Port problem - Suggestions? Date: 14 Aug 1996 07:26:56 GMT Organization: Private BSD site, Dresden Lines: 21 Message-ID: <4urv40$891@uriah.heep.sax.de> References: <4uqjfa$bhs@nnrp1.news.primenet.com> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E p_s_i@primenet.com (Tony Rasa) wrote: > My question: is there a way to "force" freebsd to recognize com4? It's certainly not a com4 (aka sio3) problem, but rather the well- known problem many internal modems are suffering from, since they do emulate the UART and have timing problems. I think this is covered in the handbook. You could set the flag 0x80 for the sio3 port (after boot -c), in order to see which probe it fails, and by looking into the code in /sys/i386/isa/sio.c, you will see which it is. You might hack around the poor UART emulation by increasing some DELAY() in the probe code then. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)