From owner-freebsd-tokenring Mon Aug 30 22:17:28 1999 Delivered-To: freebsd-tokenring@freebsd.org Received: from ugrad.unbc.ca (ugrad.unbc.ca [142.207.112.20]) by hub.freebsd.org (Postfix) with ESMTP id F3F8C14FFF for ; Mon, 30 Aug 1999 22:17:11 -0700 (PDT) (envelope-from karlj000@unbc.ca) Received: from localhost (karlj000@localhost) by ugrad.unbc.ca (8.8.7/8.8.7) with SMTP id WAA29280 for ; Mon, 30 Aug 1999 22:16:56 -0700 X-Authentication-Warning: ugrad.unbc.ca: karlj000 owned process doing -bs Date: Mon, 30 Aug 1999 22:16:56 -0700 (PDT) From: Carpathia To: freebsd-tokenring@freebsd.org Subject: Curious about status Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey, I'm just curious about the status of this project... Has anyone got anywhere or done anything with this? This may be stupid, but I've never really looked into this mailing list, and I'm curious to see what's out there. Jeremy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Tue Aug 31 7:19:51 1999 Delivered-To: freebsd-tokenring@freebsd.org Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (Postfix) with ESMTP id DF5FA15961 for ; Tue, 31 Aug 1999 07:19:17 -0700 (PDT) (envelope-from lile@stdio.com) Received: from heathers.stdio.com (lile@heathers.stdio.com [199.89.192.5]) by heathers.stdio.com (8.8.8/8.8.8) with ESMTP id KAA07620 for ; Tue, 31 Aug 1999 10:17:00 -0400 (EDT) (envelope-from lile@stdio.com) Date: Tue, 31 Aug 1999 10:17:00 -0400 (EDT) From: Larry Lile To: tokenring@freebsd.org Subject: Newbus Olicom token-ring driver... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So has anyone tried out the "newbus" Olicom driver? I haven't heard back from anyone yet. The source is now tarballed and up on my web server: http://anarchy.stdio.com/oltr.html You will need to be running a very recent current, the last arp patch I committed is very important to proper function. You will need to build the driver as a kld module, I haven't included the files.i386 patch to make it static. Please let me know how the new version is working, my test network is very small and very clean. Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Wed Sep 1 2:18:15 1999 Delivered-To: freebsd-tokenring@freebsd.org Received: from eowyn.zahle.dk (eowyn.zahle.dk [193.162.230.138]) by hub.freebsd.org (Postfix) with ESMTP id 2BA9214D7C for ; Wed, 1 Sep 1999 02:18:05 -0700 (PDT) (envelope-from serces@mud.dk) Received: from localhost (sps@localhost) by eowyn.zahle.dk (8.9.3/8.9.3) with ESMTP id LAA25395 for ; Wed, 1 Sep 1999 11:25:14 +0200 Date: Wed, 1 Sep 1999 11:25:10 +0200 (CEST) From: serces@mud.dk X-Sender: sps@eowyn.zahle.dk Reply-To: serces@mud.dk To: FreeBSD Tokenring Mailinglist Subject: Strange Lockup Occurring Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all Sorry if this has been asked before or answered somewhere else, but I seemed unable to find anything about it in the Archives :). System is running 3.2-STABLE on a NetFinity 5000, with an Olicom 3117 ISA card. I have had the same NIC running in another machine, though only at 4Mbit, whereas in production it has to run 16Mbit not that I could see that being any problem. Though something goes haywire somewhere, and to me it's veryveryvery strange.. :) Here's what's going down: Machine boots, I login on the console no problem, then I start a connection to another machine, woohoo, no problem, happy I am :), then I try to connect from a remote station to the server, still no problem, everything should be happy in tokenland (or so I thought). I then decide to start configuring the machine, installing the things I need, so I switch to the apachedir in the ports-collection, and exclaim make install on command line, it fires up, and then stops responding, nothing happens, no transfer, nothing, and at the same time I start losing my connection to the machine (Connection closed by remote host). First time around, I go to the machine, login on the console, and reboot the machine. Everything starts working again, so I think, ah, I must have made a blunder somewhere. While still at the console I do the exact same manouver as before to install apache (or anything really :), same thing happens, NIC stops responding, and nothing happens. For some obscure reason I try to do an "ifconfig oltr0 down", that one gives: Aug 31 13:39:30 urd /kernel: oltr0: otlr_stop Aug 31 13:39:31 urd /kernel: oltr0: DriverTransmitFrameCompleted (frame 12 status 1) Aug 31 13:39:31 urd /kernel: oltr0: DriverTransmitFrameCompleted (frame 13 status 1) Aug 31 13:39:31 urd /kernel: oltr0: DriverTransmitFrameCompleted (frame 14 status 1) Aug 31 13:39:31 urd /kernel: oltr0: DriverTransmitFrameCompleted (frame 15 status 1) Aug 31 13:39:31 urd /kernel: oltr0: DriverTransmitFrameCompleted (frame 0 status 1) ... etc .. a ton of these followed by Aug 31 13:39:36 urd /kernel: oltr0: DriverCloseCompleted And then an "ifconfig oltr0 up", everything works perfectly again. Someone suggested setting the MAX_USERS to 256, which was tried, and even though I couldn't see any immediate result, it might have helped since I think it performed a bit better (But that again might simply be because of the increased buffer sizes :). Currently the machine is not in production, so every 15 minutes I reset the NIC by a small shellscript that takes it down and then up again, it works, At least if I then try to do something that will lockup the NIC I only have to wait max 15 mins to get it running again, and is thereby saved the trouble of running back and forth.. :) Any ideas of what might be wrong? I mean, connectivity to/from the machine seems to be no problem using ssh or telnet, but scp/rcp/ftp/http anything really that fetches more data, will stop the NIC from responding. hope someone can help.. :) S. P. Skou "The Law of Self Sacrifice" When you starve with a tiger, the tiger starves last. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Wed Sep 1 2:45:42 1999 Delivered-To: freebsd-tokenring@freebsd.org Received: from mail.ftf.dk (mail.ftf.net [129.142.64.2]) by hub.freebsd.org (Postfix) with ESMTP id 529A614D81 for ; Wed, 1 Sep 1999 02:45:38 -0700 (PDT) (envelope-from regnauld@ftf.net) Received: from ns.int.ftf.net (fw2.ftf.dk [192.168.1.2] (may be forged)) by mail.ftf.dk (8.9.3/8.9.3/gw-ftf-1.2) with ESMTP id LAA23339; Wed, 1 Sep 1999 11:43:58 +0200 (CEST) X-Authentication-Warning: mail.ftf.dk: Host fw2.ftf.dk [192.168.1.2] (may be forged) claimed to be ns.int.ftf.net Received: (from regnauld@localhost) by ns.int.ftf.net (8.9.2/8.9.3) id LAA41066; Wed, 1 Sep 1999 11:46:40 +0200 (CEST) Message-ID: <19990901114639.61033@ns.int.ftf.net> Date: Wed, 1 Sep 1999 11:46:39 +0200 From: Phil Regnauld To: Carpathia Cc: freebsd-tokenring@FreeBSD.ORG Subject: Re: Curious about status References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: ; from Carpathia on Mon, Aug 30, 1999 at 10:16:56PM -0700 X-Operating-System: FreeBSD 3.1-RELEASE i386 Organization: FTFnet Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Carpathia writes: > Hey, > > I'm just curious about the status of this project... Has anyone got > anywhere or done anything with this? > The Olicom drivers (the only ones really usable in the TR project) are under rewrite by Larry Lile. Stay tuned. -- Division by Zero error -- multiplying by zero to recover. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Wed Sep 1 2:46: 9 1999 Delivered-To: freebsd-tokenring@freebsd.org Received: from mail.ftf.dk (mail.ftf.net [129.142.64.2]) by hub.freebsd.org (Postfix) with ESMTP id 4C2D214D81 for ; Wed, 1 Sep 1999 02:46:06 -0700 (PDT) (envelope-from regnauld@ftf.net) Received: from ns.int.ftf.net (fw2.ftf.dk [192.168.1.2] (may be forged)) by mail.ftf.dk (8.9.3/8.9.3/gw-ftf-1.2) with ESMTP id LAA23350 for ; Wed, 1 Sep 1999 11:44:12 +0200 (CEST) X-Authentication-Warning: mail.ftf.dk: Host fw2.ftf.dk [192.168.1.2] (may be forged) claimed to be ns.int.ftf.net Received: (from regnauld@localhost) by ns.int.ftf.net (8.9.2/8.9.3) id LAA41074; Wed, 1 Sep 1999 11:46:55 +0200 (CEST) Message-ID: <19990901114654.62251@ns.int.ftf.net> Date: Wed, 1 Sep 1999 11:46:54 +0200 From: Phil Regnauld To: freebsd-tokenring@freebsd.org Subject: Olicom bought Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e X-Operating-System: FreeBSD 3.1-RELEASE i386 Organization: FTFnet Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... by Madge. -- Division by Zero error -- multiplying by zero to recover. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Wed Sep 1 8:29:45 1999 Delivered-To: freebsd-tokenring@freebsd.org Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (Postfix) with ESMTP id B950714E83 for ; Wed, 1 Sep 1999 08:29:31 -0700 (PDT) (envelope-from lile@stdio.com) Received: from heathers.stdio.com (lile@heathers.stdio.com [199.89.192.5]) by heathers.stdio.com (8.8.8/8.8.8) with ESMTP id LAA06452; Wed, 1 Sep 1999 11:28:17 -0400 (EDT) (envelope-from lile@stdio.com) Date: Wed, 1 Sep 1999 11:28:17 -0400 (EDT) From: Larry Lile To: serces@mud.dk Cc: FreeBSD Tokenring Mailinglist Subject: Re: Strange Lockup Occurring In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 1 Sep 1999 serces@mud.dk wrote: > Hi all > > Sorry if this has been asked before or answered somewhere else, but I > seemed unable to find anything about it in the Archives :). > > System is running 3.2-STABLE on a NetFinity 5000, with an Olicom 3117 ISA > card. I have had the same NIC running in another machine, though only at > 4Mbit, whereas in production it has to run 16Mbit not that I could see > that being any problem. I never managed to get ifmedia working correctly before I ran into other bigger problems. I can show you where in the code to force 16Mbit. > Though something goes haywire somewhere, and to me it's veryveryvery > strange.. :) Here's what's going down: > > Machine boots, I login on the console no problem, then I start a > connection to another machine, woohoo, no problem, happy I am :), then I > try to connect from a remote station to the server, still no problem, > everything should be happy in tokenland (or so I thought). > > I then decide to start configuring the machine, installing the things I > need, so I switch to the apachedir in the ports-collection, and exclaim > make install on command line, it fires up, and then stops responding, > nothing happens, no transfer, nothing, and at the same time I start losing > my connection to the machine (Connection closed by remote host). > > First time around, I go to the machine, login on the console, and reboot > the machine. Everything starts working again, so I think, ah, I must have > made a blunder somewhere. While still at the console I do the exact same > manouver as before to install apache (or anything really :), same thing > happens, NIC stops responding, and nothing happens. Okay, this might fix you - no promises though. Try this patch to if_ether.c. It was written for 4.x-current but it will probably work for 3.2. [appended] > For some obscure reason I try to do an "ifconfig oltr0 down", that one > gives: > Aug 31 13:39:30 urd /kernel: oltr0: otlr_stop > Aug 31 13:39:31 urd /kernel: oltr0: DriverTransmitFrameCompleted (frame 12 > status 1) > Aug 31 13:39:31 urd /kernel: oltr0: DriverTransmitFrameCompleted (frame 13 > status 1) > Aug 31 13:39:31 urd /kernel: oltr0: DriverTransmitFrameCompleted (frame 14 > status 1) > Aug 31 13:39:31 urd /kernel: oltr0: DriverTransmitFrameCompleted (frame 15 > status 1) > Aug 31 13:39:31 urd /kernel: oltr0: DriverTransmitFrameCompleted (frame 0 > status 1) > ... etc .. a ton of these followed by > Aug 31 13:39:36 urd /kernel: oltr0: DriverCloseCompleted > > And then an "ifconfig oltr0 up", everything works perfectly again. You can safely ignore those messages - they are only debug for my sanity. The adapter returns incompleted buffers on close 16 buffers, status 1 - not transmitted. > Someone suggested setting the MAX_USERS to 256, which was tried, and even > though I couldn't see any immediate result, it might have helped since I > think it performed a bit better (But that again might simply be because of > the increased buffer sizes :). > > Currently the machine is not in production, so every 15 minutes I reset > the NIC by a small shellscript that takes it down and then up again, it > works, At least if I then try to do something that will lockup the NIC I > only have to wait max 15 mins to get it running again, and is thereby > saved the trouble of running back and forth.. :) > > Any ideas of what might be wrong? I mean, connectivity to/from the machine > seems to be no problem using ssh or telnet, but scp/rcp/ftp/http anything > really that fetches more data, will stop the NIC from responding. > > hope someone can help.. :) If the arp patch doesn't help then you are likely being hit by the "dma" bug that we have never been able to pin down or even prove it is a "dma" bug. I have a new version of the driver but it is for PCI cards only so you will have to wait until I get the ISA code written. Larry Lile lile@stdio.com *** if_ether.c.orig Thu Aug 26 20:48:21 1999 --- if_ether.c Fri Aug 27 14:05:17 1999 *************** *** 566,588 **** * a token-ring nic then try to save the source * routing info. */ if (ac->ac_if.if_type == IFT_ISO88025) { th = (struct iso88025_header *)m->m_pkthdr.header; if ((th->iso88025_shost[0] & 0x80) && ! (((ntohs(th->rcf) & 0x1f00) >> 8) > 2)) { ! sdl->sdl_rcf = ntohs(th->rcf) & 0x0080 ? ! htons(ntohs(th->rcf) & 0xff7f) : ! htons(ntohs(th->rcf) | 0x0080); ! memcpy(sdl->sdl_route, th->rseg, ((ntohs(th->rcf) & 0x1f00) >> 8) - 2); ! sdl->sdl_rcf = htons(ntohs(sdl->sdl_rcf) & 0x1fff); /* Set up source routing information for reply packet (XXX)*/ ! m->m_data -= (((ntohs(th->rcf) & 0x1f00) >> 8) + 8); ! m->m_len += (((ntohs(th->rcf) & 0x1f00) >> 8) + 8); } else { th->iso88025_shost[0] &= 0x7f; - m->m_data -= 8; - m->m_len += 8; } th->rcf = sdl->sdl_rcf; } else { --- 566,593 ---- * a token-ring nic then try to save the source * routing info. */ + printf("arp: m_len %d\n", m->m_len); if (ac->ac_if.if_type == IFT_ISO88025) { th = (struct iso88025_header *)m->m_pkthdr.header; if ((th->iso88025_shost[0] & 0x80) && ! ((th->rcf & 0x001f) > 2)) { ! sdl->sdl_rcf = (th->rcf & 0x8000) ? (th->rcf & 0x7fff) : ! (th->rcf | 0x8000); ! memcpy(sdl->sdl_route, th->rseg, (th->rcf & 0x001f) - 2); ! sdl->sdl_rcf = sdl->sdl_rcf & 0xff1f; /* Set up source routing information for reply packet (XXX)*/ ! m->m_data -= (th->rcf & 0x001f); ! m->m_len += (th->rcf & 0x001f); ! m->m_pkthdr.len += (th->rcf & 0x001f); ! printf("arp: m_len %d\n", m->m_len); ! printf("arp: sr len %d\n", th->rcf & 0x001f); } else { th->iso88025_shost[0] &= 0x7f; } + m->m_data -= 8; + m->m_len += 8; + m->m_pkthdr.len += 8; + printf("arp: m_len %d\n", m->m_len); th->rcf = sdl->sdl_rcf; } else { *************** *** 664,670 **** /* Set the source routing bit if neccesary */ if (th->iso88025_dhost[0] & 0x80) { th->iso88025_dhost[0] &= 0x7f; ! if (((ntohs(th->rcf) & 0x1f00) >> 8) - 2) th->iso88025_shost[0] |= 0x80; } /* Copy the addresses, ac and fc into sa_data */ --- 669,675 ---- /* Set the source routing bit if neccesary */ if (th->iso88025_dhost[0] & 0x80) { th->iso88025_dhost[0] &= 0x7f; ! if ((th->rcf & 0x001f) - 2) th->iso88025_shost[0] |= 0x80; } /* Copy the addresses, ac and fc into sa_data */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Wed Sep 1 9: 1: 0 1999 Delivered-To: freebsd-tokenring@freebsd.org Received: from eowyn.zahle.dk (eowyn.zahle.dk [193.162.230.138]) by hub.freebsd.org (Postfix) with ESMTP id 7598A15372 for ; Wed, 1 Sep 1999 09:00:56 -0700 (PDT) (envelope-from serces@mud.dk) Received: from localhost (sps@localhost) by eowyn.zahle.dk (8.9.3/8.9.3) with ESMTP id SAA27787; Wed, 1 Sep 1999 18:07:24 +0200 Date: Wed, 1 Sep 1999 18:07:21 +0200 (CEST) From: serces@mud.dk X-Sender: sps@eowyn.zahle.dk Reply-To: serces@mud.dk To: Larry Lile Cc: FreeBSD Tokenring Mailinglist Subject: Re: Strange Lockup Occurring In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 1 Sep 1999, Larry Lile wrote: > I never managed to get ifmedia working correctly before I ran into > other bigger problems. I can show you where in the code to force > 16Mbit. I'd very much like that, provided that nothing else works, I've gotten the information that a PCI card is definately an option, I'd also prefer that instead of an ISA card, which simply was chosen for the sole reason that I never could get the PCI card to work, which I discarded as being a too old machine having problems with IRQ, 'IRQ15 not served' I think the correct error message was, and at that point the ISA card was allready spinning at 4Mbit.. :) > Okay, this might fix you - no promises though. Try this patch to > if_ether.c. It was written for 4.x-current but it will probably > work for 3.2. [appended] :) I'll get on that one right away, I'll let you know if it works or not.. thanks.. :) > I have a new version of the driver but it is for PCI cards only so you > will have to wait until I get the ISA code written. As stated, the PCI card will be no problem to put in the machine, I'd actually prefer to have a PCI card in the server :) Anything that works really.. :) Thanks for the quick response btw.. :) And do keep up the good work! :) S. P. Skou "The Law of Self Sacrifice" When you starve with a tiger, the tiger starves last. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Wed Sep 1 10:11:52 1999 Delivered-To: freebsd-tokenring@freebsd.org Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (Postfix) with ESMTP id C2C4114E3E for ; Wed, 1 Sep 1999 10:11:46 -0700 (PDT) (envelope-from lile@stdio.com) Received: from heathers.stdio.com (lile@heathers.stdio.com [199.89.192.5]) by heathers.stdio.com (8.8.8/8.8.8) with ESMTP id NAA10650; Wed, 1 Sep 1999 13:09:41 -0400 (EDT) (envelope-from lile@stdio.com) Date: Wed, 1 Sep 1999 13:09:40 -0400 (EDT) From: Larry Lile To: serces@mud.dk Cc: FreeBSD Tokenring Mailinglist Subject: Re: Strange Lockup Occurring In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 1 Sep 1999 serces@mud.dk wrote: > On Wed, 1 Sep 1999, Larry Lile wrote: > > > I never managed to get ifmedia working correctly before I ran into > > other bigger problems. I can show you where in the code to force > > 16Mbit. > I'd very much like that, provided that nothing else works, I've gotten the > information that a PCI card is definately an option, I'd also prefer that > instead of an ISA card, which simply was chosen for the sole reason that I > never could get the PCI card to work, which I discarded as being a too old > machine having problems with IRQ, 'IRQ15 not served' I think the correct > error message was, and at that point the ISA card was allready spinning at > 4Mbit.. :) About line 607 in if_oltr.c (/sys/contrib/dev/oltr) you should see: TRlldSetSpeed(sc->TRlldAdapter, TRLLD_SPEED_AUTO); Change that to TRlldSetSpeed(sc->TRlldAdapter, TRLLD_SPEED_16MBPS); Autonegotiation is only supported on "some" of the Olicom cards and definately not on the TMS380 based models :( This will force the card into 16Mb mode, you can also force it to 4Mb by changing the 16 to a 4. If you need "switched" mode I can tell you how to change that also. I will get the ifmedia stuff working once I get the driver stable again. Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Wed Sep 1 11:52:17 1999 Delivered-To: freebsd-tokenring@freebsd.org Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (Postfix) with ESMTP id 021F5155A9 for ; Wed, 1 Sep 1999 11:52:14 -0700 (PDT) (envelope-from martineg@ifi.uio.no) Received: from bolm.ifi.uio.no (3395@bolm.ifi.uio.no [129.240.64.88]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id UAA17688 for ; Wed, 1 Sep 1999 20:52:11 +0200 (MET DST) Received: (from martineg@localhost) by bolm.ifi.uio.no ; Wed, 1 Sep 1999 20:52:10 +0200 (MET DST) To: freebsd-tokenring@freebsd.org Subject: Madge drivers. X-URL: http://www.stud.ifi.uio.no/~martineg/ Organization: Unorganized, Inc. From: Martin Eggen Date: 01 Sep 1999 20:52:10 +0200 Message-ID: Lines: 7 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Madge released drivers for their Smartlink 16/4 series and some other cards some time ago. Does anyone know if there are any possibilites getting these drivers for FreeBSD too? Have anyone been in contact with Madge about this? -- Martin Eggen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Thu Sep 2 1:18:20 1999 Delivered-To: freebsd-tokenring@freebsd.org Received: from mailgate.hoechst.com (mailgate.hoechst.com [149.250.222.5]) by hub.freebsd.org (Postfix) with ESMTP id A6C2A14EC0 for ; Thu, 2 Sep 1999 01:18:16 -0700 (PDT) (envelope-from Ogrover@HRVet.COM) Received: from HRVet.COM (hrvet.mailhub.hiserv.com [149.250.18.50]) by mailgate.hoechst.com (8.9.1/8.9.1) with SMTP id KAA24853; Thu, 2 Sep 1999 10:15:24 +0200 (MET DST) From: Ogrover@HRVet.COM Received: by HRVet.COM(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id 412567E0.0032D05B ; Thu, 2 Sep 1999 10:15:01 +0100 X-Lotus-FromDomain: HOERU_AH To: Martin Eggen Cc: freebsd-tokenring@FreeBSD.ORG Message-ID: <412567E0.0032CEB6.00@HRVet.COM> Date: Thu, 2 Sep 1999 09:14:48 +0100 Subject: Re: Madge drivers. Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Martin The last time I asked Madge about FreeBSD drivers, there wasn't any available. As for their Linux driver, the source code they release is only the code required to make it work with Linux, not the driver code itself. The driver is supplied as a library. If you want the source code to that, Madge will want you to agree to a non disclosure agreement, although I'm not even sure they still do that. Owen Grover Martin Eggen on 01/09/99 19:52:10 To: freebsd-tokenring@FreeBSD.ORG cc: (bcc: Owen Grover/MKN/HUKAH/HoeRU_AH) Subject: Madge drivers. Madge released drivers for their Smartlink 16/4 series and some other cards some time ago. Does anyone know if there are any possibilites getting these drivers for FreeBSD too? Have anyone been in contact with Madge about this? -- Martin Eggen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Thu Sep 2 13:23:46 1999 Delivered-To: freebsd-tokenring@freebsd.org Received: from marvin.mud.dk (marvin.mud.dk [195.78.67.177]) by hub.freebsd.org (Postfix) with ESMTP id 5655214D3D for ; Thu, 2 Sep 1999 13:23:40 -0700 (PDT) (envelope-from serces@mud.dk) Received: from mud.dk (sps@localhost [127.0.0.1]) by marvin.mud.dk (8.9.3/8.9.3) with ESMTP id WAA00575; Thu, 2 Sep 1999 22:22:27 +0200 (CEST) (envelope-from serces@mud.dk) Message-ID: <37CEDC83.F806AD5C@mud.dk> Date: Thu, 02 Sep 1999 22:22:27 +0200 From: Lord of Chaos Organization: http://www.mud.dk/ X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Larry Lile , freebsd-tokenring@freebsd.org Subject: Re: Strange Lockup Occurring References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Larry Lile wrote: > Okay, this might fix you - no promises though. Try this patch to > if_ether.c. It was written for 4.x-current but it will probably > work for 3.2. [appended] Did work for 3.2, had to handpatch it though, not that it was much of a deal, It sadly didn't help the problem, but now I've dug even deeper into the problem, and found some more oddities that really doesn't make any sense. If I use Telnet to access the machine, I seldom experience any larger problems, a bit of lag here and there, but that might as well be the line, and not the card. SSH is installed on the machine, and as soon as I try to access it via ssh instead of telnet, the netcard simply freezes up, And I have to wait for my UP/Down script to kick in effect. ftp or scp from anything still locks up the machine, but Telnet works fine (That is, untill I start using ftp/rcp/scp).. Very Weird I'd have to say since the machine can actually accept connections, and also establish connections both ways (telnet to and from the machine works like a dream), but anything else kills the machine. > I have a new version of the driver but it is for PCI cards only so you > will have to wait until I get the ISA code written. I've noted it on the homepage, will it fit into a 3.2-STABLE? Because I've just claimed a PCI card for the machine, so if and so on, I will try to see if I can get that to work instead of the curent locking situation.. S. P. Skou To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Thu Sep 2 14: 8:52 1999 Delivered-To: freebsd-tokenring@freebsd.org Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (Postfix) with ESMTP id 9FE521567B for ; Thu, 2 Sep 1999 14:08:47 -0700 (PDT) (envelope-from lile@stdio.com) Received: from heathers.stdio.com (lile@heathers.stdio.com [199.89.192.5]) by heathers.stdio.com (8.8.8/8.8.8) with ESMTP id RAA14659; Thu, 2 Sep 1999 17:07:16 -0400 (EDT) (envelope-from lile@stdio.com) Date: Thu, 2 Sep 1999 17:07:16 -0400 (EDT) From: Larry Lile To: Lord of Chaos Cc: freebsd-tokenring@FreeBSD.ORG Subject: Re: Strange Lockup Occurring In-Reply-To: <37CEDC83.F806AD5C@mud.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If 3.2 has new-bus then the new driver should work, just compile it install and kldload it. You will of course need to remove the oltr driver from your kernel first. The new driver is "ol" not "oltr", I am not sure how permanent this is but it let me do development in paralell to the cvs tree. Give it a try :) On the other hand you could "downgrade" your 3.2 install with cvs to 4/20/99 and do a "make world". Add the arp patch back in and hopefully everything should just work. The very wee hours of 4/21 are the last known working conditions. Larry Lile lile@stdio.com On Thu, 2 Sep 1999, Lord of Chaos wrote: > Larry Lile wrote: > > > Okay, this might fix you - no promises though. Try this patch to > > if_ether.c. It was written for 4.x-current but it will probably > > work for 3.2. [appended] > Did work for 3.2, had to handpatch it though, not that it was much of a > deal, It sadly didn't help the problem, but now I've dug even deeper > into the problem, and found some more oddities that really doesn't make > any sense. > > If I use Telnet to access the machine, I seldom experience any larger > problems, a bit of lag here and there, but that might as well be the > line, and not the card. SSH is installed on the machine, and as soon as > I try to access it via ssh instead of telnet, the netcard simply freezes > up, And I have to wait for my UP/Down script to kick in effect. ftp or > scp from anything still locks up the machine, but Telnet works fine > (That is, untill I start using ftp/rcp/scp).. Very Weird I'd have to say > since the machine can actually accept connections, and also establish > connections both ways (telnet to and from the machine works like a > dream), but anything else kills the machine. > > > > I have a new version of the driver but it is for PCI cards only so you > > will have to wait until I get the ISA code written. > I've noted it on the homepage, will it fit into a 3.2-STABLE? Because > I've just claimed a PCI card for the machine, so if and so on, I will > try to see if I can get that to work instead of the curent locking > situation.. > > S. P. Skou > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-tokenring" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message