From myke at ees.com Fri Jun 18 22:18:10 2004 From: myke at ees.com (Mike Holling) Date: Fri Jun 18 22:18:13 2004 Subject: is this list still alive? Message-ID: <20040618161629.B28794@claw.ees.com> not much in the archives the past two years. i'll be getting some assorted olicom pci cards next week, will they work in 4.10 with the olicom driver on the freebsd token ring web site? - Mike From david at madole.net Fri Jun 18 22:20:51 2004 From: david at madole.net (David S. Madole) Date: Fri Jun 18 22:20:53 2004 Subject: is this list still alive? References: <20040618161629.B28794@claw.ees.com> Message-ID: <15b401c45582$80236810$e3e7a8c0@david> It's alive. Just no traffic. Almost all of the Olicom PCI cards will work with the driver that's included in stock FreeBSD. See /usr/src/sys/i386/conf/LINT and /usr/src/sys/contrib/dev/oltr Dave ----- Original Message ----- From: "Mike Holling" To: Sent: Friday, June 18, 2004 6:17 PM Subject: is this list still alive? > not much in the archives the past two years. i'll be getting some > assorted olicom pci cards next week, will they work in 4.10 with the > olicom driver on the freebsd token ring web site? > > - Mike > > _______________________________________________ > freebsd-tokenring@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-tokenring > To unsubscribe, send any mail to "freebsd-tokenring-unsubscribe@freebsd.org" > ____________________________________________________________________________ This message is spam and virus free. Filtering solutions by http://omd3.com Expert computer system support and development by http://baysidenetworks.com From myke at ees.com Mon Jun 21 04:34:28 2004 From: myke at ees.com (Mike Holling) Date: Mon Jun 21 04:34:31 2004 Subject: lanstreamer on 4.10? Message-ID: <20040620221723.C28794@claw.ees.com> i'm trying to revive the beta lanstreamer driver. i unpacked the beta driver in /usr/src/sys and tried to compile it. to get it to compile i added the following to if_lns_var.h: #ifndef __packed #define __packed __attribute__ ((packed)) #endif this seems to be necessary to make the struct definitions in the rest of that header work. i put device token in the kernel, rebooted, and loaded the module. it seems to work so far: russianthistle# kldload if_lns russianthistle# ifconfig lns0 ; ifconfig lns1 ; ifconfig lns2 lns0: flags=8002 mtu 17960 lladdr 8.0.5a.fd.95.69 media: Token ring UTP/16Mbit (autoselect) status: no ring lns1: flags=8002 mtu 1500 lladdr 8.0.5a.fd.95.6a media: Token ring autoselect status: no ring lns2: flags=8002 mtu 17960 lladdr 8.0.5a.fd.95.6b media: Token ring UTP/16Mbit (autoselect) status: no ring lns0 should be plugged into a CAU, which has two linux boxes with working tokenring setup (the box is some 2500 miles away for extra fun). dmesg shows lns0 as being connected to rj45: lns0: port 0xa000-0xa0ff mem 0xef100000-0xef1000ff irq 5 at device 1.0 on pci2 lns0: RJ-45 cable, Last insert: 16Mbps, No FDX lns0: MAC address: 08.00.5a.fd.95.69 lns1: port 0xa400-0xa4ff mem 0xef101000-0xef1010ff irq 5 at device 2.0 on pci2 lns1: LANStreamer Configuration Not Valid. lns1: No cable, No saved ring speed, No FDX lns1: MAC address: 08.00.5a.fd.95.6a lns2: port 0xa800-0xa8ff mem 0xef102000-0xef1020ff irq 11 at device 3.0 on pci2 lns2: LANStreamer Configuration Not Valid. lns2: No cable, Last insert: 16Mbps, No FDX lns2: MAC address: 08.00.5a.fd.95.6b unfortunately trying to do russianthistle# ifconfig lns0 10.1.1.10 causes the box to reboot, presumably from a kernel panic. unfortunately i don't have a serial console setup, only ssh, so i can't tell exactly what happens before it reboots. any help is appreciated! it looks like it's fairly close to working. i've never laid eyes on any of this hardware, yet, we're trying to get it working for a demonstration setup at a convention in a few weeks. i'm pretty sure this card will work under linux but it'd be much nicer for us if we could get it running under freebsd, although not essential. - Mike