From owner-freebsd-hardware Sun Jul 26 13:13:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01516 for freebsd-hardware-outgoing; Sun, 26 Jul 1998 13:13:37 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ConSys.COM (ConSys.COM [209.141.107.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01511 for ; Sun, 26 Jul 1998 13:13:32 -0700 (PDT) (envelope-from rcarter@psf.Pinyon.ORG) Received: from psf.Pinyon.ORG (ip-17-214.prc.primenet.com [207.218.17.214]) by ConSys.COM (8.8.6/8.8.6) with ESMTP id NAA04542 for ; Sun, 26 Jul 1998 13:13:01 -0700 (MST) Received: from psf.Pinyon.ORG (localhost [127.0.0.1]) by psf.Pinyon.ORG (8.8.8/8.8.7) with ESMTP id NAA03721 for ; Sun, 26 Jul 1998 13:10:53 -0700 (MST) Message-Id: <199807262010.NAA03721@psf.Pinyon.ORG> X-Mailer: exmh version 2.0.2 2/24/98 To: hardware@FreeBSD.ORG Subject: 53C810 + Micropolis 3243NT quarrel Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jul 1998 13:10:53 -0700 From: "Russell L. Carter" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi there (Stefan, probably... :-) I've been trying hard to get a make world through with the appended configuration, what appears to be the problem is something up with the 53c810 and a Micropolis 3243 NT. Under heavy disk load, like building the world or untarring src onto the same drive I get a hard hang, with the drive light solid on, and the console message: ncr0: timeout ccb=f0751c00 I see from the archives that the 3243 sucks big rocks! My problem looks entertaining because I see no mention of the "M_DISCONNECT" curiosity. So is there any voodoo I can do to civilize this drive? I've got my three fan case all ready to keep it cool... Cheers, Russell Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-980520-SNAP #0: Thu May 21 17:29:22 GMT 1998 jkh@bento.freebsd.org:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz cost 5300 ns CPU: Pentium (99.87-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x526 Stepping=6 Features=0x1bf real memory = 66060288 (64512K bytes) avail memory = 61370368 (59932K bytes) Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.1.0 ide_pci0: rev 0xd0 int a irq 11 on pci0.1.1 ncr0: rev 0x01 int a irq 12 on pci0.9.0 ncr0: waiting for scsi devices to settle scbus0 at ncr0 bus 0 sd0 at scbus0 target 2 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access sd0: 10.0 MB/s (100 ns, offset 8) sd0: M_DISCONNECT received, but datapointer not saved: data=4b4d94 save=4b56b0 goal=4b56d4. 4095MB (8388315 512 byte sectors) de0: rev 0x22 int a irq 10 on pci0.10.0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:40:05:50:5e:e6 vga0: rev 0x65 on pci0.19.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 fe0 not found at 0x300 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 at 0x378-0x37f on isa lpt1 not probed due to I/O address conflict with lpt0 at 0x378 mse0 not found at 0x23c psm0 not found at 0x60 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 not found at 0x1f0 wdc1 not found at 0x170 bt0 not found at 0x330 uha0 not found at 0x330 aha0 not found at 0x330 aic0 not found at 0x340 nca0 not found at 0x1f88 nca1 not found at 0x350 sea0 not found at 0xffff wt0 not found at 0x300 mcd0 not found at 0x300 matcdc0 not found at 0x230 scd0 not found at 0x230 ie0: unknown board_id: f000 ie0 not found at 0x300 ep0 not found at 0x300 ex0 not found le0 not found at 0x300 lnc0 not found at 0x280 ze0 not found at 0x300 zp0 not found at 0x300 npx0 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround struct nfsmount bloated (> 512bytes) Try reducing NFS_MUIDHASHSIZ changing root device to sd0s1a WARNING: / was not properly dismounted. de0: enabling 100baseTX port To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jul 26 19:06:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18545 for freebsd-hardware-outgoing; Sun, 26 Jul 1998 19:06:55 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from is2.net.ohio-state.edu (is2.net.ohio-state.edu [128.146.48.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA18534 for ; Sun, 26 Jul 1998 19:06:51 -0700 (PDT) (envelope-from maf@dev1.net.ohio-state.edu) Received: (qmail 10380 invoked from network); 27 Jul 1998 02:06:20 -0000 Received: from dev1.net.ohio-state.edu (128.146.222.3) by is2.net.ohio-state.edu with SMTP; 27 Jul 1998 02:06:20 -0000 Received: (qmail 5535 invoked by uid 4454); 27 Jul 1998 02:06:19 -0000 Message-ID: <19980726220619.A5410@net.ohio-state.edu> Date: Sun, 26 Jul 1998 22:06:19 -0400 From: Mark Fullmer To: Francois Jaccard , freebsd-hardware@FreeBSD.ORG Subject: Re: Support for Asus P2B-L? References: <199807251518.RAA28362@wwwsw.webshuttle.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i In-Reply-To: <199807251518.RAA28362@wwwsw.webshuttle.ch>; from Francois Jaccard on Sat, Jul 25, 1998 at 05:18:32PM +0200 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Jul 25, 1998 at 05:18:32PM +0200, Francois Jaccard wrote: > Hi, > I would like to know if the LAN chip (Intel 8255b) and the 440BX chip of the > Asus P2B-L motherboard are supported under 3.0-current. I searched the > archives but found nothing. This is a P2B-LS. The LAN and SCSI controllers work except for the "pci_map_mem failed: bad memory type=0xfffff004" message. Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.6-STABLE #0: Thu Jul 23 07:41:06 EDT 1998 maf@base.net.ohio-state.edu:/usr/src/sys/compile/BASE CPU: Pentium II (quarter-micron) (350.80-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping=1 Features=0x183f9ff,,MMX,> real memory = 268435456 (262144K bytes) avail memory = 261001216 (254884K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0: 0 chip1 rev 2 on pci0:1: 0 chip2 rev 2 on pci0:4:0 chip3 rev 1 on pci0:4:1 chip4 rev 1 int d irq 12 on pci0:4:2 chip5 rev 2 on pci0:4:3 ahc0 rev 0 int a irq 12 on pci0:6:0 pci_map_mem failed: bad memory type=0xfffff004 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 32/255 SCBs fxp0 rev 5 int a irq 10 on pci0:7:0 fxp0: Ethernet address 00:e0:18:90:28:6f Probing for devices on PCI bus 1: vga0 rev 16 int a irq 11 on pci1:0:0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface ccd0-3: Concatenated disk drivers (probe0:ahc0:0:0:0): Sending SDTR!! da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) -- mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jul 26 19:30:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21268 for freebsd-hardware-outgoing; Sun, 26 Jul 1998 19:30:24 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from a486n1.znh.org (dialup6.gaffaneys.com [208.155.161.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA21262 for ; Sun, 26 Jul 1998 19:30:19 -0700 (PDT) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by a486n1.znh.org (8.8.8/8.8.8) id CAA05508; Mon, 27 Jul 1998 02:35:27 GMT (envelope-from zach) Message-ID: <19980726213527.A5281@znh.org.> Date: Sun, 26 Jul 1998 21:35:27 -0500 From: Zach Heilig To: "Russell L. Carter" , hardware@FreeBSD.ORG Subject: Re: 53C810 + Micropolis 3243NT quarrel References: <199807262010.NAA03721@psf.Pinyon.ORG> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807262010.NAA03721@psf.Pinyon.ORG>; from Russell L. Carter on Sun, Jul 26, 1998 at 01:10:53PM -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Jul 26, 1998 at 01:10:53PM -0700, Russell L. Carter wrote: > what appears to be the problem is something up with the > 53c810 and a Micropolis 3243 NT. Under heavy disk load, > like building the world or untarring src onto the same > drive I get a hard hang, with the drive light solid on, > and the console message: > ncr0: timeout ccb=f0751c00 > I see from the archives that the 3243 sucks big rocks! > My problem looks entertaining because I see no mention > of the "M_DISCONNECT" curiosity. I think it is simply just a bad company. Your symptoms are exactly the same as mine were (except i had a 4743 NS). It seemed to have good speed, but it eventually just died. I think the board is on the way out -- it refuses to talk to FreeBSD (the 'timeout ccb=....' message), but it'll talk with the BIOS long enough to begin a boot). One thing to try (if it has anything important on it), is to run it at 5MB/sec. When I bumped the speed down on mine (20 MB/sec to 10 MB/sec), it appeared to be all right for awhile (4-5 months). > So is there any voodoo I can do to civilize this drive? > I've got my three fan case all ready to keep it cool... It isn't an issue of keeping it cool, I don't think. I had lots of good airflow over mine before it "died". > scbus0 at ncr0 bus 0 > sd0 at scbus0 target 2 lun 0 > sd0: type 0 fixed SCSI 2 > sd0: Direct-Access > sd0: 10.0 MB/s (100 ns, offset 8) > sd0: M_DISCONNECT received, but datapointer not saved: > data=4b4d94 save=4b56b0 goal=4b56d4. > 4095MB (8388315 512 byte sectors) the M_DISCONNECT seems to be a trademark of Micropolis. -- Zach Heilig -- zach@gaffaneys.com Real Programs don't use shared text. Otherwise, how can they use functions for scratch space after they are finished calling them? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jul 26 21:15:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA04312 for freebsd-hardware-outgoing; Sun, 26 Jul 1998 21:15:24 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from cynix.ecn.purdue.edu (cynix.ecn.purdue.edu [128.46.198.198]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA04276 for ; Sun, 26 Jul 1998 21:15:06 -0700 (PDT) (envelope-from splite@purdue.edu) Received: (from splite@localhost) by cynix.ecn.purdue.edu (8.8.8/8.8.8) id XAA26871; Sun, 26 Jul 1998 23:12:42 -0500 (EST) Message-ID: <19980726231242.A26777@cynix.ecn.purdue.edu> Date: Sun, 26 Jul 1998 23:12:42 -0500 From: Steven Plite To: Nicholas Lee Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Intel Providence deal at computer123 References: <35c3ebc4.14598707@smtp.ix.net.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <35c3ebc4.14598707@smtp.ix.net.nz>; from Nicholas Lee on Sat, Jul 25, 1998 at 02:30:52PM +0000 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Jul 25, 1998 at 02:30:52PM +0000, Nicholas Lee wrote: > Noticed your post in Dejanews dated 1998/07/08, Re: overclocking > PPro166-512kB. > > I was wondering if the 166MHz 512Kb ended up being better than the 180Mhz > with the deal computer123.com are offering at the moment. > > How was your business with Clifford Technology Inc as well? Were the CPUs > new or Pulls? I haven't been terribly impressed with Clifford Tech so far. Shipment packaging was sloppy, the rotor of one of the CPU fans had popped out and was floating around inside the board's static bag. I haven't called them yet to get it replaced. It also took them two weeks to ship my order. The motherboards are pulls (from Toshiba Equium 6200Ms probably, since the one I've installed has a Toshiba logo on boot up) and don't include the ATX IO shield to cover the ports. I have no idea where to get one to fit the PR440FX, since it's a bit odd in port layout. But at least the boards look clean, and they came with a photocopied jumper diagram, which is good as Intel's manual only gives settings for 180 and 200MHz. The CPUs are pulls as well, and look a bit worn. They did ship them with (cheap) fan/heatsinks, but without any thermal grease (which you can get at Radio Shack.) That said, the one board I've installed works so far, though all I've run on it is DOS and a -current boot floppy. I'll try loading a -current snap tonight. Bottom line is: you get what you pay for. Or rather, you don't get what you don't pay for. I don't know that I'd trust this gear to a production box, but they should be fine in test boxes, which is where mine's going. As for the 166/512 vs. 180/256 question, I haven't done any comparitive testing and am unlikely to have time to do so. But, if you can afford the cost delta, the 166/512 would be preferable. Twice the L2 cache and 10% faster memory bus are good, and they would probably overclock to 180MHz (or more) easily if the 14MHz delta in clock speed bothers you. :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 27 07:48:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28100 for freebsd-hardware-outgoing; Mon, 27 Jul 1998 07:48:15 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from shadow.spel.com (elevator.cablenet-va.com [208.206.84.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA28089 for ; Mon, 27 Jul 1998 07:48:06 -0700 (PDT) (envelope-from mturpin@shadow.spel.com) Received: from localhost (mturpin@localhost) by shadow.spel.com (8.8.5/8.8.5) with SMTP id KAA01262; Mon, 27 Jul 1998 10:47:51 -0400 (EDT) Date: Mon, 27 Jul 1998 10:47:51 -0400 (EDT) From: Mark turpin To: Steven Plite cc: Nicholas Lee , freebsd-hardware@FreeBSD.ORG Subject: Re: Intel Providence deal at computer123 In-Reply-To: <19980726231242.A26777@cynix.ecn.purdue.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 26 Jul 1998, Steven Plite wrote: > I haven't been terribly impressed with Clifford Tech so far. Shipment > packaging was sloppy, the rotor of one of the CPU fans had popped out > and was floating around inside the board's static bag. I haven't called > them yet to get it replaced. It also took them two weeks to ship my order. > > The motherboards are pulls (from Toshiba Equium 6200Ms probably, since > the one I've installed has a Toshiba logo on boot up) and don't include > the ATX IO shield to cover the ports. I have no idea where to get one > to fit the PR440FX, since it's a bit odd in port layout. But at least > the boards look clean, and they came with a photocopied jumper diagram, > which is good as Intel's manual only gives settings for 180 and 200MHz. > > The CPUs are pulls as well, and look a bit worn. They did ship them with > (cheap) fan/heatsinks, but without any thermal grease (which you can get > at Radio Shack.) > Mine shipped the same way.. Bad box, cheap fan, no thermal grease. The boards are pulls from a toshiba, probably last years model which didn't sell well. The boards were probably pulled at the factory and replaced with a pentium II board. Then sold at surplus. > That said, the one board I've installed works so far, though all I've run > on it is DOS and a -current boot floppy. I'll try loading a -current snap > tonight. > > Bottom line is: you get what you pay for. Or rather, you don't get what > you don't pay for. I don't know that I'd trust this gear to a production > box, but they should be fine in test boxes, which is where mine's going. > > As for the 166/512 vs. 180/256 question, I haven't done any comparitive > testing and am unlikely to have time to do so. But, if you can afford > the cost delta, the 166/512 would be preferable. Twice the L2 cache > and 10% faster memory bus are good, and they would probably overclock > to 180MHz (or more) easily if the 14MHz delta in clock speed bothers > you. :-) > I don't think that anything is WRONG with the boards. I would have no problem putting this in a production environment. I've already installed 2.1.6 with no problems. My department doesn't have a huge budget so sales like this are great for us. Mark Turpin - mturpin@spel.com Main Street Technology Centre Bedford, VA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 27 16:14:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03706 for freebsd-hardware-outgoing; Mon, 27 Jul 1998 16:14:25 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from pn.wagsky.com (root@wagsky.vip.best.com [206.86.71.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03563; Mon, 27 Jul 1998 16:13:52 -0700 (PDT) (envelope-from Jeff@Wagsky.com) Received: from [192.168.6.3] (mac.pn.wagsky.com [192.168.6.3]) by pn.wagsky.com (8.8.8/8.8.8) with ESMTP id QAA03778; Mon, 27 Jul 1998 16:12:53 -0700 (PDT) (envelope-from Jeff@Wagsky.com) X-Sender: mailman@mail.pn.wagsky.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 27 Jul 1998 16:11:23 -0700 To: freebsd-stable@FreeBSD.ORG From: Jeff Kletsky Subject: Support for V.90 PCI modems? Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have not been able to find evidence in the FAQs or sio source for the new V.90 PCI modems. Before buying one, I'd like to know the status on the STABLE branch, and/or stability of code in the CURRENT- branch for its support. TIA, Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 27 18:30:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03652 for freebsd-hardware-outgoing; Mon, 27 Jul 1998 18:30:30 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from lucy.bedford.net (lucy.bedford.net [206.99.145.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03600 for ; Mon, 27 Jul 1998 18:30:17 -0700 (PDT) (envelope-from listread@lucy.bedford.net) Received: (from listread@localhost) by lucy.bedford.net (8.8.8/8.8.8) id UAA06964; Mon, 27 Jul 1998 20:42:14 -0400 (EDT) (envelope-from listread) Message-Id: <199807280042.UAA06964@lucy.bedford.net> Subject: Re: Intel Providence deal at computer123 In-Reply-To: from Mark turpin at "Jul 27, 98 10:47:51 am" To: mturpin@shadow.spel.com (Mark turpin) Date: Mon, 27 Jul 1998 20:42:14 -0400 (EDT) Cc: freebsd-hardware@FreeBSD.ORG X-no-archive: yes Reply-to: djv@bedford.net From: CyberPeasant X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mark turpin wrote: > > > > On Sun, 26 Jul 1998, Steven Plite wrote: > > Mine shipped the same way.. Bad box, cheap fan, no thermal > grease. The boards are pulls from a toshiba, probably last years model > which didn't sell well. The boards were probably pulled at the factory > and replaced with a pentium II board. Then sold at surplus. I'd bet that Tosh. 6200M is right. I've got two of these with PPro 200/256K. I don't know if Toshiba ever shipped the 6200M (defunct around Dec 1997) with 166's PPro, so I'm betting the 200's were pulled for a different reason, and the 166's are from who-knows-where. I think there were 180MHz 6200M's, though. The 6200M User's Manual mentions 180 and 200, but not 166. This is a nice mobo -- nothing wrong with it AFAIK. A while ago, Insight remaindered 6200M's for US$895 with 32MB, an ATI Mach 64 video card, and a 4.3GB Micropolis scsi drive. (The last, of course, is a P.o.S. from a deservedly bankrupt manufacturer). Only one of the two Micropolis drives I bought still works. :-( Everything else is OK. Oh yeah... with kbd, rodent, CDROM and floppy. Oh yeah... with NT (*puke*). FreeBSD 2.2.6 runs without incident on this board. (So does Linux 2.0.33 and OpenBSD 2.2, fwiw). At the price the 6200M blows the doors off the "new" sub$1000 boxes. I /think/ these boards have some kind of net-booting BIOS in the on-board NIC. Hmm, Insight is now selling off the 6200M's replacement, the 62?0M?, which has a PII and an EIDE disk, at around $1000. I think ? = 3. On the 6200M, Toshiba says to use EDO-ECC /buffered/ DIMMs. They shipped with 32MB, so you dudes might want to see if you've gotten pulled DIMMs from elsewhere. My 6200M's 32MB DIMMs have Toshiba chips on them and the number 7AF585(2) screened on the pcb. The original Toshiba CPU fan/heatsink is a nicely-finished-looking unit with a red/white label on the rotor reading "Cpu Cooler" and "HPIC", made in Taiwan. The 'sink is gold-anodized aluminum. Email me if you need any other info re 6200M. > I don't think that anything is WRONG with the boards. I would > have no problem putting this in a production environment. Agree. haven't tried SMP, though. > Mark Turpin - mturpin@spel.com > > Main Street Technology Centre > Bedford, VA Dave Bedford, PA HEY, any other Bedfords out there? -- Sancho Panza: `Microsoft Windows NT Server is the most secure network operating system available.' Don Quixote: `You are mistaken, Sancho.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 27 18:38:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05114 for freebsd-hardware-outgoing; Mon, 27 Jul 1998 18:38:30 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05108; Mon, 27 Jul 1998 18:38:26 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id SAA02623; Mon, 27 Jul 1998 18:36:30 -0700 (PDT) Message-Id: <199807280136.SAA02623@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Jeff Kletsky cc: freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Support for V.90 PCI modems? In-reply-to: Your message of "Mon, 27 Jul 1998 16:11:23 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Jul 1998 18:36:30 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have not been able to find evidence in the FAQs or sio source for the new > V.90 PCI modems. Before buying one, I'd like to know the status on the > STABLE branch, and/or stability of code in the CURRENT- branch for its > support. There is no explicit support for these. If they look like a standard UART, you can tweak an sio to match the parameters the BIOS assigns to them. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 27 23:54:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA16119 for freebsd-hardware-outgoing; Mon, 27 Jul 1998 23:54:49 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from inet.chipweb.ml.org (qmailr@c1003518-a.plstn1.sfba.home.com [24.1.82.47]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA16105 for ; Mon, 27 Jul 1998 23:54:44 -0700 (PDT) (envelope-from ludwigp@bigfoot.com) Message-Id: <199807280654.XAA16105@hub.freebsd.org> Received: (qmail 18596 invoked from network); 28 Jul 1998 06:53:41 -0000 Received: from speedy.chipweb.ml.org (172.16.1.1) by inet.chipweb.ml.org with SMTP; 28 Jul 1998 06:53:41 -0000 X-Sender: ludwigp2@mail-r X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Mon, 27 Jul 1998 23:53:34 -0700 To: Mike Smith , Jeff Kletsky From: Ludwig Pummer Subject: Re: Support for V.90 PCI modems? Cc: freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG In-Reply-To: <199807280136.SAA02623@dingo.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 06:36 PM 7/27/98 -0700, Mike Smith wrote: >> I have not been able to find evidence in the FAQs or sio source for the new >> V.90 PCI modems. Before buying one, I'd like to know the status on the >> STABLE branch, and/or stability of code in the CURRENT- branch for its >> support. > >There is no explicit support for these. If they look like a standard >UART, you can tweak an sio to match the parameters the BIOS assigns to >them. > I don't think they look like a standard UART. They get an auto-assigned IRQ and a memory range. They only work in Win95 AFAIK (no NT support). Under Win95, they load a special driver to emulate a normal COM port (taking up the IO address for that COM port and usually another IRQ). --Ludwig Pummer ludwigp@bigfoot.com ludwigp@chipweb.ml.org ICQ UIN: 692441 http://chipweb.home.ml.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 28 07:59:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA23509 for freebsd-hardware-outgoing; Tue, 28 Jul 1998 07:59:33 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ether.ether.online.sh.cn ([202.96.211.193]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA23494 for ; Tue, 28 Jul 1998 07:59:22 -0700 (PDT) (envelope-from paulk@ether.online.sh.cn) Received: from king (202.120.100.126) by ether.ether.online.sh.cn (EMWAC SMTPRS 0.81) with SMTP id ; Tue, 28 Jul 1998 20:42:07 +0800 From: "Paul King" To: Subject: Xircom PCMCIA Card Date: Tue, 28 Jul 1998 20:44:20 +0800 Message-ID: <01bdba25$70eedae0$6f01a8c0@king.ether.online.sh.cn> MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is there any plan support Xircom PCMCIA ethernet and modem card. I found Linux has the driver now, where can i found it for FreeBSD. (I had chech www.jp.freebsd.org/PAO, but nothing help) Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 28 08:39:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02178 for freebsd-hardware-outgoing; Tue, 28 Jul 1998 08:39:29 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles227.castles.com [208.214.165.227]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02167; Tue, 28 Jul 1998 08:39:13 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id IAA03327; Tue, 28 Jul 1998 08:37:55 -0700 (PDT) Message-Id: <199807281537.IAA03327@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Ludwig Pummer cc: Mike Smith , Jeff Kletsky , freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Support for V.90 PCI modems? In-reply-to: Your message of "Mon, 27 Jul 1998 23:53:34 PDT." <199807280654.QAA02235@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Jul 1998 08:37:54 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > At 06:36 PM 7/27/98 -0700, Mike Smith wrote: > >> I have not been able to find evidence in the FAQs or sio source for the new > >> V.90 PCI modems. Before buying one, I'd like to know the status on the > >> STABLE branch, and/or stability of code in the CURRENT- branch for its > >> support. > > > >There is no explicit support for these. If they look like a standard > >UART, you can tweak an sio to match the parameters the BIOS assigns to > >them. > > > I don't think they look like a standard UART. They get an auto-assigned IRQ > and a memory range. They only work in Win95 AFAIK (no NT support). Under > Win95, they load a special driver to emulate a normal COM port (taking up > the IO address for that COM port and usually another IRQ). Yecch. This sounds more and more like a "Winmodem" all the time. Does anyone have any documentation on how they're supposed to work? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 28 08:52:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05035 for freebsd-hardware-outgoing; Tue, 28 Jul 1998 08:52:31 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from pandora.lovett.com (root@pandora.lovett.com [38.155.241.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04900; Tue, 28 Jul 1998 08:52:14 -0700 (PDT) (envelope-from ade@lovett.com) Received: from pandora.lovett.com ([38.155.241.3] ident=ade) by pandora.lovett.com with esmtp (Exim 2.01 #1) id 0z1C1V-0003Ad-00; Tue, 28 Jul 1998 10:50:45 -0500 To: Mike Smith cc: freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Support for V.90 PCI modems? Reply-To: ade@lovett.com In-reply-to: Your message of "Tue, 28 Jul 1998 08:37:54 PDT." <199807281537.IAA03327@antipodes.cdrom.com> Date: Tue, 28 Jul 1998 10:50:45 -0500 From: Ade Lovett Message-Id: Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith writes: > >> I don't think they look like a standard UART. They get an auto-assigned IRQ >> and a memory range. They only work in Win95 AFAIK (no NT support). Under >> Win95, they load a special driver to emulate a normal COM port (taking up >> the IO address for that COM port and usually another IRQ). > >Yecch. This sounds more and more like a "Winmodem" all the time. > >Does anyone have any documentation on how they're supposed to work? Sounds exactly like the DSVD PCI modem inside the Fujitsu Lifebook -- sadly Fujitsu have not exactly been forthcoming on information about how their Windows drivers work (though in this case there's support for both Win95/98 and NT). Under Windows, it appears as a pseudo-com port (it identifies itself as being on COM3, but probing around in the equivalent IO address reveals nothing obvious) -aDe -- Ade Lovett, Austin, TX. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 28 11:30:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10481 for freebsd-hardware-outgoing; Tue, 28 Jul 1998 11:30:46 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from socko.cdnow.com (socko.cdnow.com [209.83.166.75]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10190; Tue, 28 Jul 1998 11:29:58 -0700 (PDT) (envelope-from heller@daria.cdnow.com) Received: from daria.cdnow.com (daria.cdnow.com [209.83.166.60]) by socko.cdnow.com (8.9.0/8.9.0) with ESMTP id OAA02701; Tue, 28 Jul 1998 14:28:26 -0400 (EDT) Received: (from heller@localhost) by daria.cdnow.com (8.8.8/8.8.8) id OAA16891; Tue, 28 Jul 1998 14:25:37 -0400 (EDT) From: "A. Karl Heller" Message-Id: <199807281825.OAA16891@daria.cdnow.com> Subject: Re: Support for V.90 PCI modems? To: ade@lovett.com Date: Tue, 28 Jul 1998 14:25:37 -0400 (EDT) Cc: mike@smith.net.au, freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Reply-To: heller@cdnow.com In-Reply-To: from "Ade Lovett" at Jul 28, 98 10:50:45 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Do I dare ask how external V.90 modems work then? > Mike Smith writes: > > > >> I don't think they look like a standard UART. They get an auto-assigned IRQ > >> and a memory range. They only work in Win95 AFAIK (no NT support). Under > >> Win95, they load a special driver to emulate a normal COM port (taking up > >> the IO address for that COM port and usually another IRQ). > > > >Yecch. This sounds more and more like a "Winmodem" all the time. > > > >Does anyone have any documentation on how they're supposed to work? > Sounds exactly like the DSVD PCI modem inside the Fujitsu Lifebook -- > sadly Fujitsu have not exactly been forthcoming on information about > how their Windows drivers work (though in this case there's support > for both Win95/98 and NT). > Under Windows, it appears as a pseudo-com port (it identifies itself > as being on COM3, but probing around in the equivalent IO address > reveals nothing obvious) > -aDe > -- > Ade Lovett, Austin, TX. > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- A. Karl Heller - Senior Systems Engineer - heller@cdnow.com ----------------------------------------------------------------------------- An unbreakable toy is useful for breaking other toys. Do something unusual today. Accomplish work on the computer. >>>>> HTTP://CDNOW.COM - BIGGEST FASTEST BEST <<<<< To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 28 13:04:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01726 for freebsd-hardware-outgoing; Tue, 28 Jul 1998 13:04:19 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from persprog.com (root@persprog.com [204.215.255.203]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01584; Tue, 28 Jul 1998 13:03:46 -0700 (PDT) (envelope-from dave@mmrd.com) Received: by persprog.com (8.7.5/4.10) id OAA06837; Tue, 28 Jul 1998 14:55:16 -0500 Received: from dave.ppi.com(192.2.2.6) by cerberus.ppi.com via smap (V1.3) id sma006833; Tue Jul 28 15:54:50 1998 Message-ID: <35BE2C75.4440B92A@mmrd.com> Date: Tue, 28 Jul 1998 15:54:29 -0400 From: "David W. Alderman" X-Mailer: Mozilla 4.04 [en] (WinNT; U) MIME-Version: 1.0 To: heller@cdnow.com CC: ade@lovett.com, mike@smith.net.au, freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Support for V.90 PCI modems? References: <199807281825.OAA16891@daria.cdnow.com> X-Corel-MessageType: EMail Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org A. Karl Heller wrote: > Do I dare ask how external V.90 modems work then? > Like any other standard modem. There are three basic types of internal modem: 1-Modems that take the full AT command set through a serial chip (or hardware simulacrum thereof). 2-Modems that use the CPU to interpret the AT commands but all codec and compression functions are performed in hardware. 3-Modems that use the CPU to interpret AT commands and some of the codec and compression functions. I believe the original RPI modems were of class 3 above and therefore sucked. Most V.90 Winmodems are actually of class 2 and do not suck as badly as the RPI's. Many internal V.90 modems are class1 and therefore FreeBSD friendly. Most are PnP, though. WARNING: I am not a modem expert. The classes above are strictly my own and made up 3 minutes ago based on my observations of the current consumer modem "scene". YMMV. I do have an external V.90 modem that does not require special software drivers to work. Give it the appropriate AT string and it goes! -- Dave Alderman dave@persprog.com is changing to dave@mmrd.com dwa@atlantic.net -or- dwald@earthlink.net -or- dalderman@compuserve.com -or- dwa@hal.cen.ufl.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 28 22:33:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA13389 for freebsd-hardware-outgoing; Tue, 28 Jul 1998 22:33:29 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from obie.softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA13383; Tue, 28 Jul 1998 22:33:26 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id XAA15381; Tue, 28 Jul 1998 23:32:52 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <35BEB404.125BAAA7@softweyr.com> Date: Tue, 28 Jul 1998 23:32:52 -0600 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: Jeff Kletsky CC: freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Support for V.90 PCI modems? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jeff Kletsky wrote: > > I have not been able to find evidence in the FAQs or sio source for the new > V.90 PCI modems. Before buying one, I'd like to know the status on the > STABLE branch, and/or stability of code in the CURRENT- branch for its > support. I happened to have one of these lying around, a Diamond V.90 PCI internal. I stuck it in this machine and rebooted, running pretty much vanilla 2.2.6-RELEASE, and this is what dmesg tells me: pci0:12: vendor=0x127a, device=0x1002, class=comms, subclass=0x00 int a irq 9 [no driver assigned] Somebody mentioned a couple of weeks ago how to modify one of the system sources to wire this up to the sio driver. Can anyone throw some quick instructions at me? I'll give this a try in the morning, I'm off to bed. If I can't get this working fairly easily in the FreeBSD machine, it'll get banished to the void of the wife's Win95 machine, so it's not a total loss. For $40, it's pretty hard to lose much anyhow. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 28 23:50:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26342 for freebsd-hardware-outgoing; Tue, 28 Jul 1998 23:50:22 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles246.castles.com [208.214.165.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26254; Tue, 28 Jul 1998 23:50:11 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA00819; Tue, 28 Jul 1998 23:47:40 -0700 (PDT) Message-Id: <199807290647.XAA00819@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Wes Peters cc: Jeff Kletsky , freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Support for V.90 PCI modems? In-reply-to: Your message of "Tue, 28 Jul 1998 23:32:52 MDT." <35BEB404.125BAAA7@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Jul 1998 23:47:39 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Jeff Kletsky wrote: > > > > I have not been able to find evidence in the FAQs or sio source for the new > > V.90 PCI modems. Before buying one, I'd like to know the status on the > > STABLE branch, and/or stability of code in the CURRENT- branch for its > > support. > > I happened to have one of these lying around, a Diamond V.90 PCI internal. > I stuck it in this machine and rebooted, running pretty much vanilla > 2.2.6-RELEASE, and this is what dmesg tells me: > > pci0:12: vendor=0x127a, device=0x1002, class=comms, subclass=0x00 int a irq 9 > [no driver assigned] > > Somebody mentioned a couple of weeks ago how to modify one of the system > sources to wire this up to the sio driver. Can anyone throw some quick > instructions at me? Have a look at the way that if_ed_p.c does it. First, boot with -v and confirm that all it's asking for is an 8-byte I/O mapping; if it has anything else, then it's not going to be a UART clone. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 29 05:27:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA13166 for freebsd-hardware-outgoing; Wed, 29 Jul 1998 05:27:39 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from animaniacs.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA13150; Wed, 29 Jul 1998 05:27:33 -0700 (PDT) (envelope-from jamie@itribe.net) Received: from localhost (jamie@localhost) by animaniacs.itribe.net (950413.SGI.8.6.12/950213.SGI.AUTOCF) via SMTP id IAA22687; Wed, 29 Jul 1998 08:26:14 -0400 Date: Wed, 29 Jul 1998 08:26:14 -0400 (EDT) From: Jamie Bowden To: "A. Karl Heller" cc: ade@lovett.com, mike@smith.net.au, freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Support for V.90 PCI modems? In-Reply-To: <199807281825.OAA16891@daria.cdnow.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sure, they plug into a serial port. On Tue, 28 Jul 1998, A. Karl Heller wrote: > > > Do I dare ask how external V.90 modems work then? > > > Mike Smith writes: > > > > > >> I don't think they look like a standard UART. They get an auto-assigned IRQ > > >> and a memory range. They only work in Win95 AFAIK (no NT support). Under > > >> Win95, they load a special driver to emulate a normal COM port (taking up > > >> the IO address for that COM port and usually another IRQ). > > > > > >Yecch. This sounds more and more like a "Winmodem" all the time. > > > > > >Does anyone have any documentation on how they're supposed to work? > > > Sounds exactly like the DSVD PCI modem inside the Fujitsu Lifebook -- > > sadly Fujitsu have not exactly been forthcoming on information about > > how their Windows drivers work (though in this case there's support > > for both Win95/98 and NT). > > > Under Windows, it appears as a pseudo-com port (it identifies itself > > as being on COM3, but probing around in the equivalent IO address > > reveals nothing obvious) > > > -aDe > > > -- > > Ade Lovett, Austin, TX. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > -- > A. Karl Heller - Senior Systems Engineer - heller@cdnow.com > ----------------------------------------------------------------------------- > An unbreakable toy is useful for breaking other toys. > Do something unusual today. Accomplish work on the computer. > >>>>> HTTP://CDNOW.COM - BIGGEST FASTEST BEST <<<<< > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > -- Jamie Bowden Systems Administrator, iTRiBE.net If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 29 07:26:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04573 for freebsd-hardware-outgoing; Wed, 29 Jul 1998 07:26:20 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from racoon.riga.lv (racoon.riga.lv [194.8.12.142]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04561 for ; Wed, 29 Jul 1998 07:26:14 -0700 (PDT) (envelope-from nick@lv.net) Received: from racoon.riga.lv (racoon.riga.lv [194.8.12.142]) by racoon.riga.lv (8.8.4/8.7.3/OL.cf-2.3) with SMTP id RAA19340 for ; Wed, 29 Jul 1998 17:25:25 +0300 (EET DST) Date: Wed, 29 Jul 1998 17:25:25 +0300 (EET DST) From: Nikolai Matyushenko X-Sender: nick@racoon.riga.lv To: hardware@FreeBSD.ORG Subject: radio Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello ! Do we have support for RadioTrak radio FM card in FreeBSD or will we ever have ? Thanks ! Nick. ____________________________________________________________________ Nikolai Matyushenko Unix systems and networking Phone: +371-7551133 LvNet-Teleport SIA Fax: +371-7777701 Sun Distributor In Latvia Email: nick@lvnet.lv Postal address: 204 Brivibas gatve http://www.lvnet.lv/~nick Riga, LV-1039 Snow_Dog@irc LATVIA ____________________________________________________________________ --== She Mourns a Lengthening Shadow ==-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 29 07:47:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07653 for freebsd-hardware-outgoing; Wed, 29 Jul 1998 07:47:17 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA07634 for ; Wed, 29 Jul 1998 07:47:08 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id PAA14378 for ; Wed, 29 Jul 1998 15:46:35 +0100 (BST) Message-ID: <35BF35CB.988CAF6@tdx.co.uk> Date: Wed, 29 Jul 1998 15:46:35 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.5b1 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: hardware@FreeBSD.ORG Subject: Help needed with an unruly AST & Adaptec 2940 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi All, I've just started to set-up a 3rd FreeBSD machine - which is identical to 2 other boxes we have running as production servers... The machine is an AST Premmia G90 (P90, 64 Mb RAM, Onboard NE2100 compatible network card, Onboard NCR SCSI). We don't use the onboard SCSI (though the problem below persists with or without it enabled)... Instead we fit an Adaptec 2940UW, with a KGB Altas-II hard drive... This works fine for the other 2 machines, but this one can't even find the SCSI drive... The 2940 has an AIC7880p chip on it, and BIOS v1.32 - I've tried all the usual stuff in the BIOS (i.e. termination etc.) - NT finds the drive fine (It would, wouldn't' it?) - but booting FreeBSD 2.2.7 or 2.2.5 boot disks gives me: " eisa0 Probing for devices on the EISA bus DPT: EISA SCSI HBA Driver, version 1.4.3 Probing for devices on PCI bus 0: chip0 Rev 17 on pci0:0:0 ncr0 Rev 1 int a irq 15 on pci0:1:0 ncr0 waiting for SCSI devices to settle chip1 rev 4 on pci0:2:0 ahc0 Rev 1 int a on irq 11 on pci0:3:0 ahc0: aic7880 Wide channel, SCSI ID=7, 16 SCB's ahc0 waiting for SCSI devices to settle ahc0: board is not responding (ahc0:0:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x167 SCSIREQ = 0x12 SSTAT0=0x4 SSTAT1 = 0x8 (ahc0:0:0): Queing an abort ahc0: board is not responding " If I run with 'boot: -v' - I get basically the same, except it mentions 'uploading 387' (or similar) commands to the SCSI adapter... Unfortunately I can't down the other 2 boxes to swap bits (this box is meant to be a hot spare - how ironic? ) Looking at the DMESG's for the other boxes - they all appear identical up to the point where the board doesn't respond... The other boxes have much older 2940's in them (e.g. BIOS 1.24 etc) Can anyone suggest anything? Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 29 21:50:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27891 for freebsd-hardware-outgoing; Wed, 29 Jul 1998 21:50:33 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from obie.softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27870; Wed, 29 Jul 1998 21:50:25 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id WAA17443; Wed, 29 Jul 1998 22:49:29 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <35BFFB59.5E63DC4A@softweyr.com> Date: Wed, 29 Jul 1998 22:49:29 -0600 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: Mike Smith CC: freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Support for V.90 PCI modems? References: <199807290647.XAA00819@antipodes.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith wrote: > > > I happened to have one of these lying around, a Diamond V.90 PCI internal. > > I stuck it in this machine and rebooted, running pretty much vanilla > > 2.2.6-RELEASE, and this is what dmesg tells me: > > > > pci0:12: vendor=0x127a, device=0x1002, class=comms, subclass=0x00 int a irq 9 > > [no driver assigned] > > > Have a look at the way that if_ed_p.c does it. First, boot with -v and > confirm that all it's asking for is an 8-byte I/O mapping; if it has > anything else, then it's not going to be a UART clone. It reported: pci0:12: vendor=0x127a, device=0x1002, class=comms, subclass=0x00 int a irq 9 [no driver assigned] map(10): mem32(e4000000) I assume this means it wants 10 bytes of I/O, and may not be emulating a simple UART? I'll go plunge around the Diamond Multimedia pages and see if I can find any information. (Yeah, right). -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 29 23:22:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10944 for freebsd-hardware-outgoing; Wed, 29 Jul 1998 23:22:28 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles237.castles.com [208.214.165.237]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10937; Wed, 29 Jul 1998 23:22:25 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA00420; Wed, 29 Jul 1998 23:21:30 -0700 (PDT) Message-Id: <199807300621.XAA00420@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Wes Peters cc: Mike Smith , freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Support for V.90 PCI modems? In-reply-to: Your message of "Wed, 29 Jul 1998 22:49:29 MDT." <35BFFB59.5E63DC4A@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Jul 1998 23:21:29 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Mike Smith wrote: > > > > > I happened to have one of these lying around, a Diamond V.90 PCI internal. > > > I stuck it in this machine and rebooted, running pretty much vanilla > > > 2.2.6-RELEASE, and this is what dmesg tells me: > > > > > > pci0:12: vendor=0x127a, device=0x1002, class=comms, subclass=0x00 int a irq 9 > > > [no driver assigned] > > > > > Have a look at the way that if_ed_p.c does it. First, boot with -v and > > confirm that all it's asking for is an 8-byte I/O mapping; if it has > > anything else, then it's not going to be a UART clone. > > It reported: > > pci0:12: vendor=0x127a, device=0x1002, class=comms, subclass=0x00 int a irq 9 > [no driver assigned] > map(10): mem32(e4000000) > > I assume this means it wants 10 bytes of I/O, and may not be emulating a > simple UART? 10 is the configuration register address. It's asking for a 32-bit accessible memory region - I'd have to go look up the encoding of the field to tell you how big it is. It also wants an interrupt. It's certainly not emulating a UART. > I'll go plunge around the Diamond Multimedia pages and see if I can find > any information. (Yeah, right). More useful than that would be to tell us what the part(s) on the card are. Diamond just use off-the-shelf parts in most of their designs; they're too small to do anything really custom. Then go hunting for the datasheets for the parts in question; that's where you'll find what you're after. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 30 15:38:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10197 for freebsd-hardware-outgoing; Thu, 30 Jul 1998 15:38:08 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from athens.mea.com (acy1sun01.mea.com [208.145.189.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10144 for ; Thu, 30 Jul 1998 15:38:04 -0700 (PDT) (envelope-from Boris.Bliznukov@DLI.net) Received: from dliexc01.cpy.mea.com by athens.mea.com with ESMTP id PAA19274 for ; Thu, 30 Jul 1998 15:38:01 -0700 (PDT) Received: by DLIEXC01 with Internet Mail Service (5.5.1960.3) id ; Thu, 30 Jul 1998 15:37:43 -0700 Message-ID: From: "Bliznukov, Boris" To: freebsd-hardware@FreeBSD.ORG Subject: Support for ThunderLAN/Netelligent cards Date: Thu, 30 Jul 1998 15:37:42 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi All! Release notes for 2.2.7 says that TI ThunderLAN PCI NICs are supported. However I couldn't make it work. I check sys/pci directory there is nothing there that has anything to do with TLAN card. Is it supported? Boris Bliznukov. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 30 16:24:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20027 for freebsd-hardware-outgoing; Thu, 30 Jul 1998 16:24:38 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20012 for ; Thu, 30 Jul 1998 16:24:32 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id QAA01367; Thu, 30 Jul 1998 16:21:00 -0700 (PDT) Message-Id: <199807302321.QAA01367@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Bliznukov, Boris" cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Support for ThunderLAN/Netelligent cards In-reply-to: Your message of "Thu, 30 Jul 1998 15:37:42 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Jul 1998 16:21:00 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi All! > > Release notes for 2.2.7 says that TI ThunderLAN PCI NICs are supported. > However I couldn't make it work. I check sys/pci directory there is > nothing there that has anything to do with TLAN card. > > Is it supported? The release notes appear to be in error; the Thunderlan driver was not brought into the 2.2.7 release. This appears to have been an accidental omission. You may be able to bring the if_tl driver back from -current with a little effort, however I would suggest contacting the driver's author before doing this; Bill Paul . -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 30 17:52:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04750 for freebsd-hardware-outgoing; Thu, 30 Jul 1998 17:52:57 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from post.mail.demon.net (post-20.mail.demon.net [194.217.242.27]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA04709; Thu, 30 Jul 1998 17:52:49 -0700 (PDT) (envelope-from freebsd-root@i-zone.demon.co.uk) Received: from (i-zone.demon.co.uk) [158.152.227.78] by post.mail.demon.net with smtp (Exim 1.82 #2) id 0z23R4-0002m2-00; Fri, 31 Jul 1998 00:52:42 +0000 Message-ID: <3UKYkHANERw1Ew7y@i-zone.demon.co.uk> Date: Fri, 31 Jul 1998 01:34:21 +0100 To: freebsd-questions@FreeBSD.ORG Cc: freebsd-hardware@FreeBSD.ORG From: John Subject: S3 Trio 64V2/DX video card MIME-Version: 1.0 X-Mailer: Turnpike (32) Version 4.00 beta 9 <5jmCrxUbpyYdwGXid1yqlWD9$N> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello experts Has anyone here run the S3 Trio 64V2/DX video card (1 MB) at better than 640x480 resolution? I'm using the s3 server. Though the config script says it can run at 1024x768 resolution at 8bbp, on invoking xinit it always removes 1024x768 and 800x600 from the mode settings. Any ideas as to why? I'm running 2.2.5-release, the x11 that was shipped with that (3.2 I think...) thanks -- John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 30 20:50:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23888 for freebsd-hardware-outgoing; Thu, 30 Jul 1998 20:50:08 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from pyramid.interdomain.net.au (pyramid.interdomain.net.au [203.17.167.4]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA23825 for ; Thu, 30 Jul 1998 20:50:02 -0700 (PDT) (envelope-from rha@interdomain.net.au) Received: (qmail 10496 invoked from network); 31 Jul 1998 03:49:55 -0000 Received: from obnoxious.interdomain.net.au (HELO ?203.17.167.127?) (203.17.167.127) by pyramid.interdomain.net.au with SMTP; 31 Jul 1998 03:49:55 -0000 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 31 Jul 1998 13:51:24 +1000 To: freebsd-hardware@FreeBSD.ORG From: Richard Archer Subject: Support for passive backplane chassis? Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all! I am working on setting up Internet access to an office building with hundreds of ethernets. I want to isolate the individual ethernets as much as possible, and running a FreeBSD system to as a router/firewall seems to be a logical choice. The number of ethernet segments involved means building the routers out of normal four PCI slot motherboards would be unpleasant. Even with quad-port ethernet cards (like the ZNYX NetBlaster ZX346) each router would only be able to handle 15 segments. I'd finish up with 3 racks full of PCs to maintain! I am thinking of using a passive backplane system with 16 PCI slots. This would allow each router to handle up to 64 ethernet segments. But I can't find much information about how these interact with FreeBSD. I am concerned that either the multiple PCI buses would not be detected, or there would be lengthy delays introduced by transferring data across the bridge. Is the fact that the multiple-port ethernet cards each effectively contain a PCI-PCI bridge going to complicate matters? I've searched the mailing list archives, but any discussion on this topic dates back to 1996. Does anyone have experience with these devices they'd care to share? Also, the number of interrupts generated by 60 ethernet ports could get quite high. Each ethernet segment only has a few computers, but 60 networks averaging 100 packets per second each will still generate upwards of 6,000 int/sec. How many interrupts per second can FreeBSD handle in this situation? Would this be affected by delays passing data across the bridge? Yours sincerely, Richard Archer. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 30 22:51:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06060 for freebsd-hardware-outgoing; Thu, 30 Jul 1998 22:51:43 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from cyclone.wspout.com (cyclone.waterspout.com [206.230.5.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06055 for ; Thu, 30 Jul 1998 22:51:41 -0700 (PDT) (envelope-from csg@waterspout.com) Received: from tsunami.waterspout.com (tsunami.waterspout.com [199.233.104.138]) by cyclone.wspout.com (8.8.7/8.8.4) with ESMTP id AAA04139; Fri, 31 Jul 1998 00:51:37 -0500 (EST) Received: from tsunami.waterspout.com (localhost [127.0.0.1]) by tsunami.waterspout.com (8.9.1/8.9.1) with ESMTP id AAA13188; Fri, 31 Jul 1998 00:51:37 -0500 (EST) Message-Id: <199807310551.AAA13188@tsunami.waterspout.com> To: Richard Archer cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Support for passive backplane chassis? In-reply-to: Your message of "Fri, 31 Jul 1998 13:51:24 +1000." Date: Fri, 31 Jul 1998 00:51:37 -0500 From: "C. Stephen Gunn" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message , Richard Archer writes: >I am thinking of using a passive backplane system with 16 PCI slots. >This would allow each router to handle up to 64 ethernet segments. >But I can't find much information about how these interact with FreeBSD. Richard, This would scare the heck out of me. I use a FreeBSD box at my day job to route between 5 Ethernet Interfaces. While it's a fast box, and it all works fine, I don't want to think about the bandwidth aggregation problems you might have with 64 ethernet cards on one machine. At that level you're not looking for a CPU to make decisions on the packets. You want a Switch. I would check out Lucent's Cajun Switch, or some of the nicer Cisco 10/100 switches that can take a route processor. The Lucent one claims to be 10/100 on lots of ports (140 or so) and provide Layer-3 switching (basically routing) in hardware, at wire speed. While you're looking at $25K or so, racks of BSD machines aren't free either. Don't get me wrong here, FreeBSD is great, but PCI isn't going to handle what you want. At least not at high saturation levels for each subnet. Just wondering, how does this building hook to the rest of the universe? - Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 30 23:50:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12438 for freebsd-hardware-outgoing; Thu, 30 Jul 1998 23:50:42 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12426 for ; Thu, 30 Jul 1998 23:50:40 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id IAA01346; Fri, 31 Jul 1998 08:47:33 +0200 (CEST) To: "C. Stephen Gunn" cc: Richard Archer , freebsd-hardware@FreeBSD.ORG Subject: Re: Support for passive backplane chassis? In-reply-to: Your message of "Fri, 31 Jul 1998 00:51:37 CDT." <199807310551.AAA13188@tsunami.waterspout.com> Date: Fri, 31 Jul 1998 08:47:33 +0200 Message-ID: <1344.901867653@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199807310551.AAA13188@tsunami.waterspout.com>, "C. Stephen Gunn" wr ites: >In message , Richard Archer writes: > >>I am thinking of using a passive backplane system with 16 PCI slots. >>This would allow each router to handle up to 64 ethernet segments. >>But I can't find much information about how these interact with FreeBSD. > >Richard, > > This would scare the heck out of me. I use a FreeBSD box at my >day job to route between 5 Ethernet Interfaces. We have a couple with 12 10mbit (znyx 314) and one 100 mbit, and that works fine. 64 may be a tad many. Consider using less and let them share a 100mbit backbone. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 31 01:09:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19940 for freebsd-hardware-outgoing; Fri, 31 Jul 1998 01:09:29 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from pyramid.interdomain.net.au (pyramid.interdomain.net.au [203.17.167.4]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA19935 for ; Fri, 31 Jul 1998 01:09:26 -0700 (PDT) (envelope-from rha@interdomain.net.au) Received: (qmail 26540 invoked from network); 31 Jul 1998 08:09:22 -0000 Received: from obnoxious.interdomain.net.au (HELO ?203.17.167.127?) (203.17.167.127) by pyramid.interdomain.net.au with SMTP; 31 Jul 1998 08:09:22 -0000 Message-Id: In-Reply-To: <199807310551.AAA13188@tsunami.waterspout.com> References: Your message of "Fri, 31 Jul 1998 13:51:24 +1000." Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 31 Jul 1998 18:00:25 +1000 To: freebsd-hardware@FreeBSD.ORG From: Richard Archer Subject: Re: Support for passive backplane chassis? Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 15:51 +1000 31/7/1998, C. Stephen Gunn wrote: >In message , Richard Archer writes: > >>I am thinking of using a passive backplane system with 16 PCI slots. >>This would allow each router to handle up to 64 ethernet segments. >>But I can't find much information about how these interact with FreeBSD. > > This would scare the heck out of me. I use a FreeBSD box at my >day job to route between 5 Ethernet Interfaces. While it's a fast >box, and it all works fine, I don't want to think about the bandwidth >aggregation problems you might have with 64 ethernet cards on one >machine. At that level you're not looking for a CPU to make decisions >on the packets. You want a Switch. Hi Steve, Well, that's certainly a heads-up! The problem with the switches I've seen are that they don't offer the security of a router. I really want a solution that operates as a firewall between the LANs. From what I've seen, products like the Bay Networks Accelar 1200 finish up costing over $1000 per port (that's the price in local currency here in Australia). I've costed out a solution using FreeBSD boxes (either 4 16-slot backplane boxes or 16 4-slot motherboard solutions) and either way it works out to about $500 per port. But of course $500 per port works out being very expensive if the solution does not work! > I would check out Lucent's Cajun Switch, or some of the nicer Cisco >10/100 switches that can take a route processor. The Lucent one claims >to be 10/100 on lots of ports (140 or so) and provide Layer-3 switching >(basically routing) in hardware, at wire speed. While you're looking >at $25K or so, racks of BSD machines aren't free either. $25K (double that in Australia) would actually work out being a comparable price to the FreeBSD-based system. I'll certainly follow that up. Also the Cisco Catalyst 5000 series with the 48-port 10baseT ports might work out being a reasonable price. > Don't get me wrong here, FreeBSD is great, but PCI isn't going to >handle what you want. At least not at high saturation levels for >each subnet. Just wondering, how does this building hook to the rest >of the universe? At the moment the building is still a shell :) I was going to use a Cisco 3260 with a 2E2W card with each WAN port connecting to a different upstream. (Actually one upstream and one to a local peering point.) Thank you for the advice! ...Richard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 31 05:13:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16483 for freebsd-hardware-outgoing; Fri, 31 Jul 1998 05:13:58 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from animaniacs.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA16478 for ; Fri, 31 Jul 1998 05:13:57 -0700 (PDT) (envelope-from jamie@itribe.net) Received: from localhost (jamie@localhost) by animaniacs.itribe.net (950413.SGI.8.6.12/950213.SGI.AUTOCF) via SMTP id IAA03921; Fri, 31 Jul 1998 08:13:36 -0400 Date: Fri, 31 Jul 1998 08:13:36 -0400 (EDT) From: Jamie Bowden To: "C. Stephen Gunn" cc: Richard Archer , freebsd-hardware@FreeBSD.ORG Subject: Re: Support for passive backplane chassis? In-Reply-To: <199807310551.AAA13188@tsunami.waterspout.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 31 Jul 1998, C. Stephen Gunn wrote: > In message , Richard Archer writes: > > >I am thinking of using a passive backplane system with 16 PCI slots. > >This would allow each router to handle up to 64 ethernet segments. > >But I can't find much information about how these interact with FreeBSD. > > Richard, > > This would scare the heck out of me. I use a FreeBSD box at my > day job to route between 5 Ethernet Interfaces. While it's a fast > box, and it all works fine, I don't want to think about the bandwidth > aggregation problems you might have with 64 ethernet cards on one > machine. At that level you're not looking for a CPU to make decisions > on the packets. You want a Switch. > > I would check out Lucent's Cajun Switch, or some of the nicer Cisco > 10/100 switches that can take a route processor. The Lucent one claims > to be 10/100 on lots of ports (140 or so) and provide Layer-3 switching > (basically routing) in hardware, at wire speed. While you're looking > at $25K or so, racks of BSD machines aren't free either. > > Don't get me wrong here, FreeBSD is great, but PCI isn't going to > handle what you want. At least not at high saturation levels for > each subnet. Just wondering, how does this building hook to the rest > of the universe? I have a baynetworks accelar switch that was built just for this kind of nightmare...little pricey, but worth it. -- Jamie Bowden Systems Administrator, iTRiBE.net If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 31 08:35:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09641 for freebsd-hardware-outgoing; Fri, 31 Jul 1998 08:35:43 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.6.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09633 for ; Fri, 31 Jul 1998 08:35:40 -0700 (PDT) (envelope-from schofiel@xs4all.nl) Received: from xs1.xs4all.nl (root@xs1.xs4all.nl [194.109.6.42]) by smtp1.xs4all.nl (8.8.8/8.8.8) with ESMTP id RAA08122 for ; Fri, 31 Jul 1998 17:35:35 +0200 (CEST) Received: from excelsior (enterprise.xs4all.nl [194.109.14.215]) by xs1.xs4all.nl (8.8.8/8.8.6) with SMTP id RAA03457 for ; Fri, 31 Jul 1998 17:35:34 +0200 (MET DST) Message-ID: <35C1E3E8.2D6@xs4all.nl> Date: Fri, 31 Jul 1998 17:34:00 +0200 From: Rob Schofield Reply-To: schofiel@xs4all.nl Organization: Knights of the Round Table, Ltd. X-Mailer: Mozilla 3.04Gold (WinNT; I) MIME-Version: 1.0 To: Free BSD Hardware list Subject: 3C579-TP Ethernet card Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Anyone know off hand which driver should support the 3COM 579-TP EISA card? I am getting install problems and could do with a second, independent eye. Does this driver run in EISA's extended mode? Rob Schofield -- The Ninety-Ninety Rule of Project Scheduling: The first ninety percent of the job takes ninety percent of the alloted time, the last ten percent takes the other ninety percent. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 31 12:36:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11162 for freebsd-hardware-outgoing; Fri, 31 Jul 1998 12:36:05 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from stortek.stortek.com (stortek.stortek.com [129.80.22.249]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11111 for ; Fri, 31 Jul 1998 12:36:02 -0700 (PDT) (envelope-from RoberPS@LOUISVILLE.STORTEK.COM) Received: from lsv-bridge.stortek.com (lsv-bridge.stortek.com [129.80.5.131]) by stortek.stortek.com (8.9.0/8.9.0) with ESMTP id NAA24184; Fri, 31 Jul 1998 13:35:50 -0600 (MDT) Message-Id: <199807311935.NAA24184@stortek.stortek.com> Received: by lsv-bridge.stortek.com with Internet Mail Service (5.5.1960.3) id ; Fri, 31 Jul 1998 13:35:49 -0600 From: "Roberts, Patrick S" To: "'Richard Archer'" , freebsd-hardware@FreeBSD.ORG Subject: RE: Support for passive backplane chassis? Date: Fri, 31 Jul 1998 13:35:48 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Cisco Cat-5000 will work great in that capacity.... have used the a great deal and have found them to be exxellent in the areas of scalabilty.... as for your security problem, with a good switch, that has hardware routing capabilities, there is not much worries..... - -- Patrick S. Roberts StorageTek - Systems Engineer OpenSystemsSupport - -----Original Message----- From: Richard Archer [SMTP:rha@interdomain.net.au] Sent: Friday, July 31, 1998 2:00 AM To: freebsd-hardware@FreeBSD.ORG Subject: Re: Support for passive backplane chassis? At 15:51 +1000 31/7/1998, C. Stephen Gunn wrote: >In message , Richard Archer writes: > >>I am thinking of using a passive backplane system with 16 PCI slots. >>This would allow each router to handle up to 64 ethernet segments. >>But I can't find much information about how these interact with FreeBSD. > > This would scare the heck out of me. I use a FreeBSD box at my >day job to route between 5 Ethernet Interfaces. While it's a fast >box, and it all works fine, I don't want to think about the bandwidth >aggregation problems you might have with 64 ethernet cards on one >machine. At that level you're not looking for a CPU to make decisions >on the packets. You want a Switch. Hi Steve, Well, that's certainly a heads-up! The problem with the switches I've seen are that they don't offer the security of a router. I really want a solution that operates as a firewall between the LANs. From what I've seen, products like the Bay Networks Accelar 1200 finish up costing over $1000 per port (that's the price in local currency here in Australia). I've costed out a solution using FreeBSD boxes (either 4 16-slot backplane boxes or 16 4-slot motherboard solutions) and either way it works out to about $500 per port. But of course $500 per port works out being very expensive if the solution does not work! > I would check out Lucent's Cajun Switch, or some of the nicer Cisco >10/100 switches that can take a route processor. The Lucent one claims >to be 10/100 on lots of ports (140 or so) and provide Layer-3 switching >(basically routing) in hardware, at wire speed. While you're looking >at $25K or so, racks of BSD machines aren't free either. $25K (double that in Australia) would actually work out being a comparable price to the FreeBSD-based system. I'll certainly follow that up. Also the Cisco Catalyst 5000 series with the 48-port 10baseT ports might work out being a reasonable price. > Don't get me wrong here, FreeBSD is great, but PCI isn't going to >handle what you want. At least not at high saturation levels for >each subnet. Just wondering, how does this building hook to the rest >of the universe? At the moment the building is still a shell :) I was going to use a Cisco 3260 with a 2E2W card with each WAN port connecting to a different upstream. (Actually one upstream and one to a local peering point.) Thank you for the advice! ...Richard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.5.5 for non-commercial use Comment: Internet Security Consultant iQA/AwUBNcIcvro11bxpeVfFEQI4KwCg1Ig8Ffkia7Krz+XMdRxZs3YjM94AnRa8 d5+KE/zP5j9bVA7nodyPa42L =Wd1e -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 31 13:09:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16052 for freebsd-hardware-outgoing; Fri, 31 Jul 1998 13:09:33 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ece.arizona.edu (ece1.ece.arizona.edu [128.196.28.166]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA16041 for ; Fri, 31 Jul 1998 13:09:31 -0700 (PDT) (envelope-from john@ece.arizona.edu) Received: from burdell.ece.arizona.edu by ece.arizona.edu (SMI-8.6/SMI-SVR4) id NAA15546; Fri, 31 Jul 1998 13:09:11 -0700 Received: by burdell.ece.arizona.edu (SMI-8.6/SMI-SVR4) id NAA18443; Fri, 31 Jul 1998 13:10:07 -0700 Date: Fri, 31 Jul 1998 13:10:07 -0700 From: john@ece.arizona.edu (John Galbraith) Message-Id: <199807312010.NAA18443@burdell.ece.arizona.edu> To: mike@smith.net.au, fcawth@jjarray.umd.edufcawth@jjarray.umd.edu, randal@comtest.com, dufault@hda.com, mike@smith.net.au CC: FreeBSD-hardware@FreeBSD.ORG In-reply-to: <199807230013.RAA02438@dingo.cdrom.com> (message from Mike Smith on Wed, 22 Jul 1998 17:13:40 -0700) Subject: Re: new GPIB driver Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, I put the the first post of my code in ftp.freebsd.org/pub/FreeBSD/incoming/gpib-galbraith.Jul29-98.tar.gz. Randal says he is up to 600K/sec on with the modifications to the old driver. I am not up to that yet, but there are a thousand things that I still have to look at before I give up. Randal, what size of transfers are those, and how are you measuring your data rate? I measure my data rate by putting two GPIB cards in the same machine (I only have one machine to play with at a time 8-( ) and having one send data to the other. This means that the data has to get in AND out of the kernel on the same machine as I run my benchmark. There are a bunch of things that I don't know about this process. First of all, how do you get userland data into the kernel the fastest? Would this be with uiomove()? What block sizes are reasonable, and are there problems with very big or very small transfers? Right now, I am still using ioctl() to write data. I am not quite sure how the data gets into the kernel, other than the fact that it does. Does the operating system do this automatically with the ioctl() mechanism? Should I expect an improvement when I move this functionality to write() and read()? Second, I don't know if the bottleneck is the operating system or the GPIB bus itself. It could be that the data rate is limited by the bus and how I have the bus timing configured (which I haven't optimized at all yet). DMA - This seems to work on the send, but I sometimes get dmacheck errors and kernel panics which I haven't fixed yet. The read doesn't work, but I don't know if it is actually the DMA that is broken or the bus not syncronizing after the read. I sometimes have that problem with one of my cards even when I am not using DMA, but not the other. Finally, there is a #include problem when configuring this into the kernel which doesn't exist when doing it as an LKM. I just noticed this, and haven't had a chance to fix it. It is probably no big deal. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 31 14:04:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27327 for freebsd-hardware-outgoing; Fri, 31 Jul 1998 14:04:29 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27239 for ; Fri, 31 Jul 1998 14:04:15 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA00582; Fri, 31 Jul 1998 14:03:03 -0700 (PDT) Message-Id: <199807312103.OAA00582@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: schofiel@xs4all.nl cc: Free BSD Hardware list Subject: Re: 3C579-TP Ethernet card In-reply-to: Your message of "Fri, 31 Jul 1998 17:34:00 +0200." <35C1E3E8.2D6@xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 Jul 1998 14:03:03 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Anyone know off hand which driver should support the 3COM 579-TP EISA > card? I am getting install problems and could do with a second, > independent eye. This should be working with the 'ep' driver. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 31 14:05:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27618 for freebsd-hardware-outgoing; Fri, 31 Jul 1998 14:05:09 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27598 for ; Fri, 31 Jul 1998 14:05:05 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id NAA00537; Fri, 31 Jul 1998 13:59:57 -0700 (PDT) Message-Id: <199807312059.NAA00537@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: john@ece.arizona.edu (John Galbraith) cc: mike@smith.net.au, fcawth%jjarray.umd.edufcawth@jjarray.umd.edu, randal@comtest.com, dufault@hda.com, FreeBSD-hardware@FreeBSD.ORG Subject: Re: new GPIB driver In-reply-to: Your message of "Fri, 31 Jul 1998 13:10:07 PDT." <199807312010.NAA18443@burdell.ece.arizona.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 Jul 1998 13:59:57 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Well, I put the the first post of my code in > ftp.freebsd.org/pub/FreeBSD/incoming/gpib-galbraith.Jul29-98.tar.gz. > > Randal says he is up to 600K/sec on with the modifications to the old > driver. I am not up to that yet, but there are a thousand things that > I still have to look at before I give up. Randal, what size of > transfers are those, and how are you measuring your data rate? > > I measure my data rate by putting two GPIB cards in the same machine > (I only have one machine to play with at a time 8-( ) and having one > send data to the other. This means that the data has to get in AND > out of the kernel on the same machine as I run my benchmark. There > are a bunch of things that I don't know about this process. First of > all, how do you get userland data into the kernel the fastest? Would > this be with uiomove()? The fastest way is to map the user buffer into the kernel's address space, but that's expensive. uiomove is the next best way to go. > What block sizes are reasonable, and are > there problems with very big or very small transfers? When you say "block" I prefer you refer to the size of each individual transaction. Each read/write call requires a context switch into the kernel and back out again, and these cost. The larger the transaction, the lower the cost per unit data. > Right now, I am > still using ioctl() to write data. I am not quite sure how the data > gets into the kernel, other than the fact that it does. Does the > operating system do this automatically with the ioctl() mechanism? Yes; the data are copied in as part of the ioctl process. > Should I expect an improvement when I move this functionality to > write() and read()? This depends on where your overheads are. Note that the ISA bus bandwidth will ultimately become a bottleneck for you, as you're only using one bus for two cards. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 31 14:12:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29875 for freebsd-hardware-outgoing; Fri, 31 Jul 1998 14:12:55 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29870; Fri, 31 Jul 1998 14:12:53 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id OAA04092; Fri, 31 Jul 1998 14:12:30 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 31 Jul 1998 14:12:29 -0700 (PDT) From: Doug White To: John cc: freebsd-questions@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: S3 Trio 64V2/DX video card In-Reply-To: <3UKYkHANERw1Ew7y@i-zone.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 31 Jul 1998, John wrote: > Hello experts > > Has anyone here run the S3 Trio 64V2/DX video card (1 MB) at better than > 640x480 resolution? I'm using the s3 server. Though the config script > says it can run at 1024x768 resolution at 8bbp, on invoking xinit it > always removes 1024x768 and 800x600 from the mode settings. Any ideas as > to why? Use the SVGA server instead. (--) SVGA: PCI: S3 ViRGE/DX or /GX rev 1, Memory @ 0xf8000000 (--) SVGA: S3V: ViRGE/DXGX rev 1, Linear FB @ 0xf8000000 (--) SVGA: Detected S3 ViRGE/DXGX (--) SVGA: using driver for chipset "s3_virge" (--) SVGA: videoram: 2048k (--) SVGA: Ramdac speed: 170 MHz (--) SVGA: Detected current MCLK value of 57.273 MHz (--) SVGA: chipset: s3_virge (--) SVGA: videoram: 2048k (**) SVGA: Option "power_saver" (**) SVGA: Using 16 bpp, Depth 16, Color weight: 565 (--) SVGA: Maximum allowed dot-clock: 170.000 MHz (**) SVGA: Mode "1024x768": mode clock = 85.000 (**) SVGA: Mode "640x480": mode clock = 45.800 (**) SVGA: Mode "800x600": mode clock = 69.650 (--) SVGA: Virtual resolution set to 1024x768 Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 31 14:44:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05960 for freebsd-hardware-outgoing; Fri, 31 Jul 1998 14:44:00 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from oldyeller.comtest.com (comtest.hits.net [206.127.244.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05955 for ; Fri, 31 Jul 1998 14:43:56 -0700 (PDT) (envelope-from randal@comtest.com) Received: from graphics.comtest.com (graphics.comtest.com [206.127.245.194]) by oldyeller.comtest.com (8.8.8/8.8.8) with SMTP id LAA20872; Fri, 31 Jul 1998 11:41:50 -1000 (HST) (envelope-from randal@comtest.com) Message-Id: <199807312141.LAA20872@oldyeller.comtest.com> From: "Randal S. Masutani" Organization: ComTest Technologies, Inc. To: john@ece.arizona.edu (John Galbraith) Date: Fri, 31 Jul 1998 11:48:07 -1000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: new GPIB driver Reply-to: randal@comtest.com CC: FreeBSD-hardware@FreeBSD.ORG, Mike Smith , Peter Dufault In-reply-to: <199807312010.NAA18443@burdell.ece.arizona.edu> References: <199807230013.RAA02438@dingo.cdrom.com> (message from Mike Smith on Wed, 22 Jul 1998 17:13:40 -0700) X-mailer: Pegasus Mail for Windows (v3.01b) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 31 Jul 98, at 13:10, John Galbraith wrote: > Well, I put the the first post of my code in > ftp.freebsd.org/pub/FreeBSD/incoming/gpib-galbraith.Jul29-98.tar.gz. > > Randal says he is up to 600K/sec on with the modifications to the old > driver. I am not up to that yet, but there are a thousand things that > I still have to look at before I give up. Randal, what size of > transfers are those, and how are you measuring your data rate? As I mentioned it was raw throughput of 600KBytes/sec. I am sending 60 blocks of 64Kbyte size transfers. Using GPIB-Spy on the receiving station(Win95) to measure time for each block of 64K. Source computer: P166 FreeBSD 2.2.6, NI-GPIB/TNT ISA. Dest computer: P166 Win95, NI-GPIB/TNT ISA. Wrote a DOS program to just read 64Kbytes blocks of data. > I measure my data rate by putting two GPIB cards in the same machine > (I only have one machine to play with at a time 8-( ) and having one > send data to the other. This means that the data has to get in AND > out of the kernel on the same machine as I run my benchmark. There > are a bunch of things that I don't know about this process. First of > all, how do you get userland data into the kernel the fastest? Would > this be with uiomove()? What block sizes are reasonable, and are > there problems with very big or very small transfers? Right now, I am > still using ioctl() to write data. I am not quite sure how the data > gets into the kernel, other than the fact that it does. Does the > operating system do this automatically with the ioctl() mechanism? > Should I expect an improvement when I move this functionality to > write() and read()? Mike can best answer these questions. :) > Second, I don't know if the bottleneck is the operating system or the > GPIB bus itself. It could be that the data rate is limited by the bus > and how I have the bus timing configured (which I haven't optimized at > all yet). I have been playing with the T1 bus timing and it does make a difference from setting it to 350ns, 500ns, 2us. With the 2us timing the transfers slow down to about 300Kbyte/sec. > DMA - This seems to work on the send, but I sometimes get dmacheck > errors and kernel panics which I haven't fixed yet. The read doesn't > work, but I don't know if it is actually the DMA that is broken or the > bus not syncronizing after the read. I sometimes have that problem > with one of my cards even when I am not using DMA, but not the other. Well, I can get from Win95 to Win95, using demand DMA mode transfers about 1.3Mbytes/sec, again using GPIB-Spy on the receiving station to monitor timing. If we can get DMA to work on FreeBSD it should improve transfers very much I hope. > Finally, there is a #include problem when configuring this into the > kernel which doesn't exist when doing it as an LKM. I just noticed > this, and haven't had a chance to fix it. It is probably no big deal. > > John I will have the new NI-GPIB/TNT+ board in today. This will allow me to run the GPIB Analyzer software so I can see the timing on the bus much better and see also everything else going across that bus. Randal ------------------------------------------------------------------------- ComTest Technologies, Inc. 3049 Ualena St., Suite 1005 Honolulu, Hawaii 96819 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 31 18:42:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11126 for freebsd-hardware-outgoing; Fri, 31 Jul 1998 18:42:02 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from sho.97hongkong.com ([209.125.132.212]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11089 for ; Fri, 31 Jul 1998 18:41:58 -0700 (PDT) (envelope-from hho@97hongkong.com) Received: from localhost (hho@localhost) by sho.97hongkong.com (8.8.7/8.8.7) with SMTP id VAA08113 for ; Fri, 31 Jul 1998 21:41:02 -0400 Date: Fri, 31 Jul 1998 21:41:02 -0400 (EDT) From: Hiu Ho To: freebsd-hardware@FreeBSD.ORG Subject: FreeBSD doesn't see my hard drive. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I tried to install 2.2.6 but it couldn't see my hard drive. Can someone help me? Here's what I have: Motherboard: ASUS SP97-V Hard Drive: Seagate ST33220A (Primary IDE master) Thank you. Regards, Hiu Ho To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Aug 1 01:45:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA20127 for freebsd-hardware-outgoing; Sat, 1 Aug 1998 01:45:51 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA20121 for ; Sat, 1 Aug 1998 01:45:49 -0700 (PDT) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id EAA11814; Sat, 1 Aug 1998 04:45:29 -0400 (EDT) Date: Sat, 1 Aug 1998 04:45:29 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: "Roberts, Patrick S" cc: "'Richard Archer'" , freebsd-hardware@FreeBSD.ORG Subject: RE: Support for passive backplane chassis? In-Reply-To: <199807311935.NAA24184@stortek.stortek.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The problem with most of the switches is that it seems you lose some security. I mean they "route", but they don't quite route. The goal is to let no traffic of any sort pass from customer A to customer B. Does the RSM give you control over that? Is it just a VLAN issue? How about IP theft within the building? Charles On Fri, 31 Jul 1998, Roberts, Patrick S wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > The Cisco Cat-5000 will work great in that capacity.... have used the > a great deal and have found them to be exxellent in the areas of > scalabilty.... as for your security problem, with a good switch, that > has hardware routing capabilities, there is not much worries..... > > - -- > Patrick S. Roberts > StorageTek - Systems Engineer > OpenSystemsSupport > > - -----Original Message----- > From: Richard Archer [SMTP:rha@interdomain.net.au] > Sent: Friday, July 31, 1998 2:00 AM > To: freebsd-hardware@FreeBSD.ORG > Subject: Re: Support for passive backplane chassis? > > At 15:51 +1000 31/7/1998, C. Stephen Gunn wrote: > > >In message , Richard Archer > writes: > > > >>I am thinking of using a passive backplane system with 16 PCI slots. > >>This would allow each router to handle up to 64 ethernet segments. > >>But I can't find much information about how these interact with > FreeBSD. > > > > This would scare the heck out of me. I use a FreeBSD box at my > >day job to route between 5 Ethernet Interfaces. While it's a fast > >box, and it all works fine, I don't want to think about the bandwidth > >aggregation problems you might have with 64 ethernet cards on one > >machine. At that level you're not looking for a CPU to make > decisions > >on the packets. You want a Switch. > > Hi Steve, > > Well, that's certainly a heads-up! > > The problem with the switches I've seen are that they don't offer the > security of a router. I really want a solution that operates as a > firewall > between the LANs. From what I've seen, products like the Bay Networks > Accelar 1200 finish up costing over $1000 per port (that's the price > in > local currency here in Australia). > > I've costed out a solution using FreeBSD boxes (either 4 16-slot > backplane > boxes or 16 4-slot motherboard solutions) and either way it works out > to > about $500 per port. > > But of course $500 per port works out being very expensive if the > solution > does not work! > > > > I would check out Lucent's Cajun Switch, or some of the nicer > Cisco > >10/100 switches that can take a route processor. The Lucent one > claims > >to be 10/100 on lots of ports (140 or so) and provide Layer-3 > switching > >(basically routing) in hardware, at wire speed. While you're looking > >at $25K or so, racks of BSD machines aren't free either. > > $25K (double that in Australia) would actually work out being a > comparable > price to the FreeBSD-based system. I'll certainly follow that up. Also > the > Cisco Catalyst 5000 series with the 48-port 10baseT ports might work > out > being a reasonable price. > > > > Don't get me wrong here, FreeBSD is great, but PCI isn't going to > >handle what you want. At least not at high saturation levels for > >each subnet. Just wondering, how does this building hook to the rest > >of the universe? > > At the moment the building is still a shell :) > > I was going to use a Cisco 3260 with a 2E2W card with each WAN port > connecting to a different upstream. (Actually one upstream and one to > a local peering point.) > > > Thank you for the advice! > > ...Richard. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > > -----BEGIN PGP SIGNATURE----- > Version: PGPfreeware 5.5.5 for non-commercial use > Comment: Internet Security Consultant > > iQA/AwUBNcIcvro11bxpeVfFEQI4KwCg1Ig8Ffkia7Krz+XMdRxZs3YjM94AnRa8 > d5+KE/zP5j9bVA7nodyPa42L > =Wd1e > -----END PGP SIGNATURE----- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Aug 1 09:46:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26140 for freebsd-hardware-outgoing; Sat, 1 Aug 1998 09:46:17 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from is2.net.ohio-state.edu (is2.net.ohio-state.edu [128.146.48.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA26135 for ; Sat, 1 Aug 1998 09:46:15 -0700 (PDT) (envelope-from maf@dev1.net.ohio-state.edu) Received: (qmail 3289 invoked from network); 1 Aug 1998 16:46:05 -0000 Received: from dev1.net.ohio-state.edu (128.146.222.3) by is2.net.ohio-state.edu with SMTP; 1 Aug 1998 16:46:05 -0000 Received: (qmail 16742 invoked by uid 4454); 1 Aug 1998 16:46:05 -0000 Message-ID: <19980801124604.A16606@net.ohio-state.edu> Date: Sat, 1 Aug 1998 12:46:05 -0400 From: Mark Fullmer To: spork , "Roberts, Patrick S" Cc: "'Richard Archer'" , freebsd-hardware@FreeBSD.ORG Subject: Re: Support for passive backplane chassis? References: <199807311935.NAA24184@stortek.stortek.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i In-Reply-To: ; from spork on Sat, Aug 01, 1998 at 04:45:29AM -0400 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Aug 01, 1998 at 04:45:29AM -0400, spork wrote: > The problem with most of the switches is that it seems you lose some > security. I mean they "route", but they don't quite route. The goal is > to let no traffic of any sort pass from customer A to customer B. Does the > RSM give you control over that? Is it just a VLAN issue? How about IP > theft within the building? Yes. With an RSM Each VLAN looks like a virtual router port. If each port were a seperate VLAN, it would be just like having a high density ethernet router. To have decent performance you'll want to look at adding a nffc or an 8510. interface Vlan10 description TEST VLAN ip address 128.146.35.1 255.255.255.0 no ip directed-broadcast no ip proxy-arp no ip route-cache optimum ip route-cache flow If you're interested in accounting get a FreeBSD box to capture and process the netflow exports. -- mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Aug 1 16:41:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04706 for freebsd-hardware-outgoing; Sat, 1 Aug 1998 16:41:29 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04701 for ; Sat, 1 Aug 1998 16:41:27 -0700 (PDT) (envelope-from dkelly@n4hhe.ampr.org) Received: from nospam.hiwaay.net (tnt2-89.HiWAAY.net [208.147.148.89]) by mail.HiWAAY.net (8.9.0/8.9.0) with ESMTP id SAA04197 for ; Sat, 1 Aug 1998 18:41:19 -0500 (CDT) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.8) with ESMTP id SAA03810 for ; Sat, 1 Aug 1998 18:41:18 -0500 (CDT) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199808012341.SAA03810@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hardware@FreeBSD.ORG Subject: PCI and de0 From: David Kelly Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Aug 1998 18:41:18 -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org About a year or so ago the de driver broke for my early version 21040 card. Ended up putting an NE2000 clone on ISA to get by. Later installed an Adaptec 2742 or 2842 (I forget, the VL-bus one) and tried to get it working. And haven't paid much attention to either until recently. The VL Adaptec appears to work but won't boot my 4G IBM DCAS HD. Wonder if 4G was too much for it. Or "geometry" or something is wrong. Only mention this because the Adaptec was on IRQ 15. Noticed de0 was also getting IRQ 15. This is with 2.2.7-RELEASE. But couldn't ifconfig de0 because "interface does not exist". Yet it was listed in dmesg. So I got the great idea to move the Adaptec IRQ to 10. This time dmesg doesn't list the de0 at all. Removed the Adaptec and now the de0 is detected but looks like this: FreeBSD 2.2.7-STABLE #0: Fri Jul 31 09:22:28 CDT 1998 dkelly@Grumpy.tbe.com:/usr3/src/sys/compile/GRUMPY CPU: AMD Am5x86 Write-Back (486-class CPU) Origin = "AuthenticAMD" Id = 0x4f4 Stepping=4 Features=0x1 real memory = 33554432 (32768K bytes) avail memory = 30728192 (30008K bytes) Probing for devices on PCI bus 0: vga0 rev 211 int a irq 12 on pci0:12:0 ahc0 rev 0 int a irq 11 on pci0:13:0 ahc0: aic7870 Single Channel, SCSI Id=7, 16/255 SCBs ahc0 waiting for scsi devices to settle ahc0: target 0 Tagged Queuing Device (ahc0:0:0): "IBM DCAS-34330 S61A" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 4134MB (8467200 512 byte sectors) (ahc0:3:0): "ARCHIVE ANCDA 2750 28077 -003" type 1 removable SCSI 2 st0(ahc0:3:0): Sequential-Access density code 0x15, 512-byte blocks, write-enabled de0 rev 0 int a irq ?? on pci0:14:0 pci_map_port failed: not configured by bios. chip0 rev 4 on pci0:16:0 chip1 rev 14 on pci0:18:0 pci0:18:1: UMC, device=0x673a, class=storage (ide) [no driver assigned] 1996 AMI BIOS doesn't have provisions for assigning IRQ to the card the way the Award BIOS does on this Asus P6NP5. Other than The Real Solution: Go Buy New Intel Ethernet Card and Ditch This Cheap Junk MB Too, is there something I could/should do? There doesn't appear to be a way to assign an IRQ in the kernel config. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Aug 1 18:51:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15862 for freebsd-hardware-outgoing; Sat, 1 Aug 1998 18:51:59 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15856 for ; Sat, 1 Aug 1998 18:51:54 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id SAA05351; Sat, 1 Aug 1998 18:51:07 -0700 (PDT) Message-Id: <199808020151.SAA05351@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: David Kelly cc: freebsd-hardware@FreeBSD.ORG Subject: Re: PCI and de0 In-reply-to: Your message of "Sat, 01 Aug 1998 18:41:18 CDT." <199808012341.SAA03810@nospam.hiwaay.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Aug 1998 18:51:06 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > About a year or so ago the de driver broke for my early version 21040 > card. Ended up putting an NE2000 clone on ISA to get by. Later > installed an Adaptec 2742 or 2842 (I forget, the VL-bus one) and tried > to get it working. And haven't paid much attention to either until > recently. > > The VL Adaptec appears to work but won't boot my 4G IBM DCAS HD. Wonder > if 4G was too much for it. Or "geometry" or something is wrong. Only > mention this because the Adaptec was on IRQ 15. Noticed de0 was also > getting IRQ 15. This is with 2.2.7-RELEASE. But couldn't ifconfig de0 > because "interface does not exist". Yet it was listed in dmesg. Don't confuse the PCI probe enumerating the device with the device working OK. This sounds like simple misconfiguration on your part; you can't share an IRQ between an ISA and PCI device, and with the IRQ that you've configured the Adaptec for, it's not being routed correctly. (BIOS setup error). > So I got the great idea to move the Adaptec IRQ to 10. This time dmesg > doesn't list the de0 at all. > > Removed the Adaptec and now the de0 is detected but looks like this: ... > de0 rev 0 int a irq ?? on pci0:14:0 > pci_map_port failed: not configured by bios. ... This is your problem. Try turning the "PnP OS installed" option off. Interesting that the collection of boards that have this behaviour are just hitting the collection of users that have to ask about it. I'm sure there's something profound to be derived from this. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message