From owner-freebsd-current@FreeBSD.ORG Tue Dec 11 20:30:40 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D66C516A468 for ; Tue, 11 Dec 2007 20:30:40 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 109D213C4EA for ; Tue, 11 Dec 2007 20:30:39 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A4E2E.dip.t-dialin.net [84.154.78.46]) (authenticated bits=0) by tower.berklix.org (8.13.6/8.13.6) with ESMTP id lBBKUV0j013749; Tue, 11 Dec 2007 20:30:33 GMT (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by js.berklix.net (8.13.8/8.13.8) with ESMTP id lBBKUQJ6089770; Tue, 11 Dec 2007 21:30:26 +0100 (CET) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.13.8/8.13.8) with ESMTP id lBBKUeUO009646; Tue, 11 Dec 2007 21:30:40 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200712112030.lBBKUeUO009646@fire.js.berklix.net> To: current@freebsd.org, ghozzy@gmail.com In-reply-to: <30984.1197357342@critter.freebsd.dk> References: <30984.1197357342@critter.freebsd.dk> Comments: In-reply-to "Poul-Henning Kamp" message dated "Tue, 11 Dec 2007 07:15:42 +0000." Date: Tue, 11 Dec 2007 21:30:40 +0100 From: "Julian H. Stacey" Cc: Poul-Henning Kamp , Oliver Fromme Subject: Re: PLIP - Parallel IP - does it still work ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Dec 2007 20:30:40 -0000 Oliver Fromme wrote: > FWIW, I also noticed that PLIP seems to work best when > both machines are about the same speed. If you can't > get it to work between a very fast machine and a slow > one, then I suggest you try a different machine (if > possible) that is of similar speed as the other one. Thanks. I started with a similar slow server "lapl" which the 7.0BETA3 installer on install client "norb" failed to contact, then I switched to a fast server "fire" that also failed. Hosts "lapa" & "lapl" below work, so a reference to test PL-IP links with: HOST RELEASE PROCESSOR fire 6.2 AMD Athlon(tm) 64 Processor 3000+ (2010.06-MHz K8-class CPU) lapa 4.11 Pentium II/Pentium II Xeon/Celeron (267.27-MHz 686-class CPU) lapd 7.0-BETA3 Pentium/P55C (166-MHz 586 CPU) (no ppc yet, config prob) lapl 4.11 Pentium/P55C (120.27-MHz 586-class CPU) loft 6.2 Pentium II/Pentium II Xeon/Celeron (334.09-MHz 686-class CPU) norb 7.0-BETA3 Intel Pentium (P54C) (586-class), 133.65 MHz, id 0x52c Links: lapa-loft, & fire-lapl dont work. ( Host fire (X server) display same sticky mouse latency I've seen previously on a working FreeBSD plip/slip though, so some activity on that cable, it's trying even if not a working IP link. (No lpd of course, 3 PLIP cables, all tested OK on lapa-lapl) I think PLIP in much or all of FreeBSD-[5-7].* is defective. http://www.freebsd.org/cgi/query-pr.cgi?pr=113856 http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/src/gen/share/man/man4/lp.4.REL=ALL.diff http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/src/gen/share/man/man4/plip.4.send-pr.ignore http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/src/jhs/sys/dev/ppbus/if_plip.c.REL=ALL.diff Probably time `man plip` is marked as Dead, until fixed. "Poul-Henning Kamp" wrote: > PLIP is sensitive to cpu clock speeds, you may have to extend the > loops somewhat in order to give all the EMC/EMI protection time to > pass the signals. Thanks, Some time I'll hope to look in /usr/src/sys/ dev/ppc & modules/ppc if no one else does. -- Julian Stacey. Munich Computer Consultant, BSD Unix C Linux. http://berklix.com Ihr Rauch = mein allergischer Kopfschmerz. Dump cigs 4 snuff.