Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!news.mel.connect.com.au!news.mel.aone.net.au!news-out.internetmci.com!pull-feed.internetmci.com!www.facs.federated-fds.com!news.ececs.uc.edu!newsrelay.netins.net!newsfeed.dacom.co.kr!usenet.kornet.nm.kr!agate!howland.erols.net!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: Problems with uucico Date: 29 Oct 1996 21:04:18 GMT Organization: Private BSD site, Dresden Lines: 32 Message-ID: <555rgi$621@uriah.heep.sax.de> References: <Pine.LNX.3.91.961023224820.1769C-100000@speedy.ruhr.de> <54pvdd$897@uriah.heep.sax.de> <54thaa$8ue@hannibal.camelot.de> 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 os@hannibal.camelot.de (Oliver Scheel) wrote: > > . does your mainboard suffer from a broken UART implementation as it > > is e.g. known for the UMC8669F chip? (Btw., Daniel confirmed me in private mail that he's using the UMC part.) > I have got the same problem, but I tried everything to set handshake > correctly (with stty in rc.serial/manually, set hardflow true in the > uucp port file). PPP works, call ins/outs and zmodem receive work > fine. btw: UUCP over TCP works. UMC8669F? These chips are broken, period. You can find software workarounds (and there is one in the current driver), but the origin of the problems is a broken (by design) chip. They've botched the FDC, and they've botched the UARTs. (The FDC generates unexpected interrupts, the UARTs don't resynchronize when changing the divisor latch while data are flowing in -- even if you change it to the same value.) I suggest anybody who's suffering from such a chip to return the board as the first measure. Do only use software workarounds if you cannot return your hardware for some reason. -- 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. ;-)