From owner-freebsd-tokenring Tue Jun 22 15:12: 7 1999 Delivered-To: freebsd-tokenring@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 609C614FC2 for ; Tue, 22 Jun 1999 15:11:54 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id SAA15165 for ; Tue, 22 Jun 1999 18:11:53 -0400 (EDT) X-Received: from eowyn.zahle.dk (sps@eowyn.zahle.dk [193.162.230.138]) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id RAA14574 for ; Tue, 22 Jun 1999 17:36:27 -0400 (EDT) From: serces@mud.dk X-Received: from localhost (sps@localhost) by eowyn.zahle.dk (8.9.3/8.9.3) with ESMTP id XAA14537 for ; Tue, 22 Jun 1999 23:41:06 +0200 Date: Tue, 22 Jun 1999 23:41:06 +0200 (CEST) X-Sender: sps@eowyn.zahle.dk Reply-To: serces@mud.dk To: winter@jurai.net Subject: Tokenring Support for FreeBSD 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 there I'm having some slight troubles with FreeBSD kernel 3.1 and your Olicom tokenring driver, and they quite baffle me. I've patched the files mentioned on the website, and put the appropriate files the appropriate places. Compiled with device oltr0 at isa? pseudo-device token In, and everything went as planned, not even a single warning. :) After a reboot dmesg tells me that it has found the following oltr cards bash-2.02# dmesg | grep oltr oltr: oltr_pci_probe oltr: oltr_pci_probe oltr: oltr_pci_probe oltr1: rev 0x03 int a irq 9 on pci0.9.0 oltr1: mac address [00:00:83:2a:3a:75] oltr1: Adapter modes - TRLLD_MODE_PHYSICAL TRLLD_MODE_SHARE_INTERRUPT oltr0: oltr_probe oltr0: auto assigning card. oltr0: [00:00:83:78:f7:d6] oltr0 at 0xa20 irq 9 drq 1 on isa oltr0: Adapter modes - TRLLD_MODE_16M TRLLD_MODE_PHYSICAL oltr1: adapter status good. (close completed/self-test) oltr0: adapter status good. (close completed/self-test) Question 1: I have tried without the ISA card in, and the PCI card then becomes oltr1, instead of the expected oltr0, is that normal? on wit the installation, ifconfig tells me the following : oltr1: flags=8802 mtu 1500 lladdr 00:00:83:2a:3a:75 media: autoselect () supported media: UTP/16Mbit UTP/4Mbit autoselect fxp0: flags=8843 mtu 1500 inet 195.78.67.179 netmask 0xfffffff8 broadcast 195.78.67.183 inet 10.0.255.254 netmask 0xffff0000 broadcast 10.0.255.255 ether 00:90:27:4e:b4:0e media: autoselect supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP oltr0: flags=8802 mtu 1500 lladdr 00:00:83:78:f7:d6 media: autoselect () supported media: UTP/16Mbit UTP/4Mbit autoselect lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 Question #2: Why is the media unknown? As you note, I have a Intel FastEther card in as well, and that one works like a dream (One of the intentions with the machine was to have it as a kind of bridge between an Ethernet and a Tokennet). To enforce a UTP/4Mbit, since I'm not sure the MAU I'm sitting with, is in the best of conditions : # ifconfig oltr0 media UTP/4Mbit # ifconfig oltr1 media UTP/4Mbit No problems encountered here still, so I start configuring the cards, first the ISA card #ifconfig oltr0 inet 192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255 up KERNEL PANICS with the following: -- *SNIP* -- oltr0: Adapter initialization failed: Adapter cannot interrupt oltr0: closing adapter due to failure oltr0: otlr_stop Fatal trap 12: page fault while in kernel mode fault virtual address = 0xb8 fault code = supervisor read, page not present instruction pointer = 0x8:0xf014ca6b stack pointer = 0x10:0xf0251a7c frame pointer = 0x10:0xf0251a90 code segment = base 0x0, limit 0xffffff type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrrupt mask = net tty trap number = 12 panic: page fault -- *SNIP* -- Machine reboots, I try to get the PCI card working: #ifconfig oltr1 inet 192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255 up Kernel panics again, this time with : --*SNIP*-- oltr1: Adapter initialization failed: DMA data error oltr1: closing adapter due to failure oltr1: otlr_stop (... The rest is the same as with the ISA card) --*SNIP*-- And I'm back to square one. I've checked that I do not have any conflicts with hardware, I even tried to make a conflict, and during boot, it just mentioned that it didn't want to start that particular card. I've checked that cables are correct, and that it is possible for the card to open the port on the mau (Another machine standing next to the FreeBSD running Windows 95). Also that the cards themselves work (By putting them into the Win95 machine, and start). The machine is : CPU: Intel 166Mhz RAM: 32 Megabytes Controllers: IDE/SCSI (adaptech 1542) HD1: IDE, Might be A quantum HD2: SCSI, Quantum NIC1: Intel Fastether PCI NIC2: Olicom OC3137 PCI NIC3: Olicom OC3117 ISA Also, on the main webpage of http://www.jurai.net/~winter/tr/ it states that the Olicom driver and the tokenring support was submitted to FreeBSD 3.0-STABLE, I can't seem to locate it anywhere, and going in where the Olicom driver can be fetched, it says that the status is that it is in CURRENT. I hope you can shed some light over this situation, and hopefully enlighten me a lot. :) 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 Tue Jun 22 22:51: 0 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 162EB15510 for ; Tue, 22 Jun 1999 22:50:57 -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 HAA14148; Wed, 23 Jun 1999 07:52:02 +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 IAA65112; Wed, 23 Jun 1999 08:01:39 +0200 (CEST) Message-ID: <19990623080139.06759@ns.int.ftf.net> Date: Wed, 23 Jun 1999 08:01:39 +0200 From: Phil Regnauld To: serces@mud.dk Cc: winter@jurai.net, freebsd-tokenring@freebsd.org, lile@stdio.org Subject: Re: Tokenring Support for FreeBSD References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: ; from serces@mud.dk on Tue, Jun 22, 1999 at 11:41:06PM +0200 X-Operating-System: FreeBSD 3.1-RELEASE i386 Organization: FTFnet Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG serces@mud.dk writes: > Hi there > > I'm having some slight troubles with FreeBSD kernel 3.1 and your Olicom > tokenring driver, and they quite baffle me. I've patched the files > mentioned on the website, and put the appropriate files the appropriate > places. Compiled with I think the code on the web page + 3.1 don't mix. In fact, I never got anything to work properly other than 19990421-CURRENT (19990530-CURRENT doesn't work, for example, with packet loss + mbuf problems). Larry Lile is the person you want to talk to. I think he's busy working on it as we speak. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Tue Jun 22 22:55:46 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 394C815557 for ; Tue, 22 Jun 1999 22:55:42 -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 HAA14199; Wed, 23 Jun 1999 07:56: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 IAA65148; Wed, 23 Jun 1999 08:06:35 +0200 (CEST) Message-ID: <19990623080635.61064@ns.int.ftf.net> Date: Wed, 23 Jun 1999 08:06:35 +0200 From: Phil Regnauld To: serces@mud.dk Cc: winter@jurai.net, freebsd-tokenring@freebsd.org, lile@stdio.com Subject: Re: Tokenring Support for FreeBSD References: <19990623080139.06759@ns.int.ftf.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <19990623080139.06759@ns.int.ftf.net>; from Phil Regnauld on Wed, Jun 23, 1999 at 08:01:39AM +0200 X-Operating-System: FreeBSD 3.1-RELEASE i386 Organization: FTFnet Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Phil Regnauld writes: > > Larry Lile is the person you want to talk to. Woops, that would be stdio.COM, not .org. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message From owner-freebsd-tokenring Thu Jun 24 3: 0:10 1999 Delivered-To: freebsd-tokenring@freebsd.org Received: from bfc.dk (unknown [194.192.110.140]) by hub.freebsd.org (Postfix) with SMTP id A7ACD15373 for ; Thu, 24 Jun 1999 02:59:47 -0700 (PDT) (envelope-from npe@bfc.dk) Received: by bfc.dk(Lotus SMTP MTA SMTP v4.6 (462.2 9-3-1997)) id 4125679A.003BE325 ; Thu, 24 Jun 1999 11:54:07 +0100 X-Lotus-FromDomain: BFC-DATA@BFC From: npe@bfc.dk To: serces@mud.dk Cc: freebsd-tokenring@freebsd.org Message-ID: <4125679A.003A4D63.00@bfc.dk> Date: Thu, 24 Jun 1999 11:51:37 +0100 Subject: Re: Tokenring Support for FreeBSD Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-tokenring@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi there Hi. > I'm having some slight troubles with FreeBSD kernel 3.1 and > your Olicom tokenring driver, and they quite baffle me. > I've patched the files mentioned on the website, and put > the appropriate files the appropriate places. > Compiled with > > device oltr0 at isa? > pseudo-device token > > In, and everything went as planned, not even a single > warning. :) After a reboot dmesg tells me that it > has found the following oltr cards > bash-2.02# dmesg | grep oltr > oltr: oltr_pci_probe > oltr: oltr_pci_probe > oltr: oltr_pci_probe > oltr1: rev 0x03 int a irq 9 on pci0.9.0 > oltr1: mac address [00:00:83:2a:3a:75] > oltr1: Adapter modes - TRLLD_MODE_PHYSICAL TRLLD_MODE_SHARE_INTERRUPT > oltr0: oltr_probe > oltr0: auto assigning card. > oltr0: [00:00:83:78:f7:d6] > oltr0 at 0xa20 irq 9 drq 1 on isa > oltr0: Adapter modes - TRLLD_MODE_16M TRLLD_MODE_PHYSICAL > oltr1: adapter status good. (close completed/self-test) > oltr0: adapter status good. (close completed/self-test) > Question 1: I have tried without the ISA card in, and the PCI > card then becomes oltr1, instead of the expected oltr0, > is that normal? Yes.. Because of the structure of the driverinterface in FreeBSD. I't cannot know if there's a isa card or not when configuring the pci card. > on wit the installation, ifconfig tells me the following : > oltr1: flags=8802 mtu 1500 > lladdr 00:00:83:2a:3a:75 > media: autoselect () > supported media: UTP/16Mbit UTP/4Mbit autoselect > fxp0: flags=8843 mtu 1500 > inet 195.78.67.179 netmask 0xfffffff8 broadcast 195.78.67.183 > inet 10.0.255.254 netmask 0xffff0000 broadcast 10.0.255.255 > ether 00:90:27:4e:b4:0e > media: autoselect > supported media: autoselect 100baseTX 100baseTX > 10baseT/UTP 10baseT/UTP > oltr0: flags=8802 mtu 1500 > lladdr 00:00:83:78:f7:d6 > media: autoselect () > supported media: UTP/16Mbit UTP/4Mbit autoselect > lo0: flags=8049 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > > Question #2: Why is the media unknown? The driver does not open the TR interface until you configure the card with an IP-address. So it can't determine with media it is running on. > As you note, I have a Intel FastEther card in as well, and that > one works like a dream (One of the intentions with the machine was > to have it as a kind of bridge between an Ethernet and a Tokennet). > To enforce a UTP/4Mbit, since I'm not sure the MAU I'm sitting > with, is in the best of conditions : > # ifconfig oltr0 media UTP/4Mbit > # ifconfig oltr1 media UTP/4Mbit > No problems encountered here still, so I start configuring the > cards, first the ISA card > #ifconfig oltr0 inet 192.168.0.1 netmask 255.255.255.0 > broadcast 192.168.0.255 up KERNEL PANICS with the following: > -- *SNIP* -- > oltr0: Adapter initialization failed: Adapter cannot interrupt > oltr0: closing adapter due to failure > oltr0: otlr_stop > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xb8 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xf014ca6b > stack pointer = 0x10:0xf0251a7c > frame pointer = 0x10:0xf0251a90 > code segment = base 0x0, limit 0xffffff type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = Idle > interrrupt mask = net tty > trap number = 12 > panic: page fault > -- *SNIP* -- > Machine reboots, I try to get the PCI card working: Try using the configuration diskette for the ISA card.. Disable PnP and try assigning a different interrupt! > #ifconfig oltr1 inet 192.168.0.1 netmask 255.255.255.0 > broadcast 192.168.0.255 up > Kernel panics again, this time with : > --*SNIP*-- > oltr1: Adapter initialization failed: DMA data error > oltr1: closing adapter due to failure > oltr1: otlr_stop > (... The rest is the same as with the ISA card) > --*SNIP*-- Have you tried without the isa card in the machine ?? They are trying to share interrupts.. maybe that's the problem.. > And I'm back to square one. I've checked that I do not have > any conflicts with hardware, I even tried to make a conflict, > and during boot, it just mentioned that it didn't want to > start that particular card. > I've checked that cables are correct, and that it is possible > for the card to open the port on the mau (Another machine > standing next to the FreeBSD running Windows 95). Also that > the cards themselves work (By putting them into the Win95 machine, > and start). > Also, on the main webpage of http://www.jurai.net/~winter/tr/ > it states that the Olicom driver and the tokenring support > was submitted to FreeBSD 3.0-STABLE, I can't seem to locate > it anywhere, and going in where the Olicom driver can be fetched, > it says that the status is that it is in CURRENT. It's merge into the stable-tree.. after the release of the 3.2-RELEASE version. If you run a "cvsup" to the branch 3.0 branch then it will be added. (check the handbook on how to stay CURRENT(with STABLE)). > I hope you can shed some light over this situation, and > hopefully enlighten me a lot. :) Hopes this helps... It is my best shot.. ;-) > S. P. Skou --------- Nicolai Petri WM-data BFC Denmark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-tokenring" in the body of the message