From owner-freebsd-hardware Mon Oct 12 11:50:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12060 for freebsd-hardware-outgoing; Mon, 12 Oct 1998 11:50:23 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [205.162.1.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12052 for ; Mon, 12 Oct 1998 11:50:21 -0700 (PDT) (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.8/8.8.5) id MAA15990 for hardware@freebsd.org; Mon, 12 Oct 1998 12:50:03 -0700 (PDT) Date: Mon, 12 Oct 1998 12:50:03 -0700 (PDT) From: Jim Shankland Message-Id: <199810121950.MAA15990@biggusdiskus.flyingfox.com> To: hardware@FreeBSD.ORG Subject: ATX boards and restart after power failure Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I know this has come up before, but I haven't found the discussion in the archives. We have been building systems based on the Tyan S1572 motherboard (ATX form factor, TX chipset). It turns out that when there's a power failure, these systems stay down when power returns until a human or other mammal presses the soft power-on button on the front. Furthermore, *this "feature" cannot be disabled*. (On the equivalent Asus board, the TX97-X, there's a BIOS option -- "AC Pwr Loss Restart" -- to disable the "feature".) Now, I'm as much of a fan of power management as the next person, but the mind-numbing stupidity of deliberately building a system that can't be restarted without human intervention after a power failure has me speechless (well, nearly). Maybe FreeBSD and Linux are barely blips on these people's radar screens; but have they ever heard of Windows NT? Or even Windows 95 users who want their machines to pick up FAX calls around the clock? Anyway, enough ranting. My questions are: * Is this likely to be a BIOS configuration item that, for whatever reason, was deliberately omitted from the configuration screen? I.e., is there a software-only solution to this problem (either we poke the CMOS by hand, or look for a BIOS update)? * Somebody (I think on this list) actually made a hardware mod to their boxes to simulate "mammal pushed soft-power-on button" when power came up. If that person or anyone else has any thoughts on how to go about this, I'd like to hear them. * I'd love to hear more about which ATX Socket 7 boards are similarly damaged. So far, the data points I have are: -- Asus TX97-X: OK -- Tyan S1572: BROKEN -- Asus P5A: BROKEN? (was told, haven't seen this myself) The P5A is particularly disturbing, as it's the successor to the TX97-X, with the Aladdin chipset. If this is true, then Asus is making negative progress. Thanks in advance for any information. Jim Shankland Flying Fox Computer Systems, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 12 13:08:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29428 for freebsd-hardware-outgoing; Mon, 12 Oct 1998 13:08:39 -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 NAA29418 for ; Mon, 12 Oct 1998 13:08:36 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from localhost (kpielorz@localhost) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id VAA15291; Mon, 12 Oct 1998 21:08:18 +0100 (BST) Date: Mon, 12 Oct 1998 21:08:18 +0100 (BST) From: Karl Pielorz To: Jim Shankland cc: hardware@FreeBSD.ORG Subject: Re: ATX boards and restart after power failure In-Reply-To: <199810121950.MAA15990@biggusdiskus.flyingfox.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 Mon, 12 Oct 1998, Jim Shankland wrote: > We have been building systems based on the Tyan S1572 motherboard > (ATX form factor, TX chipset). It turns out that when there's a > power failure, these systems stay down when power returns until > a human or other mammal presses the soft power-on button on the > front. ;-) Mammal... Why don't you get your FreeBSD daemon to do it? (Here Chuck... Chuck? ) > * Somebody (I think on this list) actually made a hardware mod > to their boxes to simulate "mammal pushed soft-power-on button" > when power came up. If that person or anyone else has any thoughts > on how to go about this, I'd like to hear them. You should be able to build a simple RC (i.e. resistor/capictor) switch to bring the machine up when mains returns (similar to the one that provides the RESET signal for CPU's in systems until the PSU has stabalised... If no other helpful soul dives in and sends you ASCII art of an RC network let me know, I'll dig/draw one up... 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 Mon Oct 12 15:40:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00657 for freebsd-hardware-outgoing; Mon, 12 Oct 1998 15:40:52 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from otto.oss.uswest.net (otto.oss.uswest.net [204.147.85.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00622 for ; Mon, 12 Oct 1998 15:40:45 -0700 (PDT) (envelope-from pmckenna@otto.oss.uswest.net) Received: (from pmckenna@localhost) by otto.oss.uswest.net (8.8.8/8.8.7) id RAA23554; Mon, 12 Oct 1998 17:39:18 -0500 (CDT) (envelope-from pmckenna) From: "Pete McKenna" Message-Id: <9810122239.ZM23552@otto.oss.uswest.net> Date: Mon, 12 Oct 1998 22:39:18 +0000 In-Reply-To: Jim Shankland "ATX boards and restart after power failure" (Oct 12, 12:50pm) References: <199810121950.MAA15990@biggusdiskus.flyingfox.com> X-Mailer: Z-Mail (3.2.1 10apr95) To: Jim Shankland , hardware@FreeBSD.ORG Subject: Re: ATX boards and restart after power failure Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've commented on this before and I may be who your refering to. We use Tyan Tahoe S1648S boards and they don't have a bios setting but do have a MB jumper right between the IDE headers that disables this "feature". Don't know if the same holds true for yours. I believe some did make a ciruit to temporarily pull the soft switch to ground for a Tyan board as well, but don't recall who. Pete On Oct 12, 12:50pm, Jim Shankland wrote: > Subject: ATX boards and restart after power failure > I know this has come up before, but I haven't found the discussion > in the archives. > > We have been building systems based on the Tyan S1572 motherboard > (ATX form factor, TX chipset). It turns out that when there's a > power failure, these systems stay down when power returns until > a human or other mammal presses the soft power-on button on the > front. Furthermore, *this "feature" cannot be disabled*. (On > the equivalent Asus board, the TX97-X, there's a BIOS option -- > "AC Pwr Loss Restart" -- to disable the "feature".) > > Now, I'm as much of a fan of power management as the next person, but > the mind-numbing stupidity of deliberately building a system that > can't be restarted without human intervention after a power failure > has me speechless (well, nearly). Maybe FreeBSD and Linux are barely > blips on these people's radar screens; but have they ever heard of > Windows NT? Or even Windows 95 users who want their machines to pick > up FAX calls around the clock? > > Anyway, enough ranting. My questions are: > > * Is this likely to be a BIOS configuration item that, for whatever > reason, was deliberately omitted from the configuration screen? > I.e., is there a software-only solution to this problem (either we > poke the CMOS by hand, or look for a BIOS update)? > > * Somebody (I think on this list) actually made a hardware mod > to their boxes to simulate "mammal pushed soft-power-on button" > when power came up. If that person or anyone else has any thoughts > on how to go about this, I'd like to hear them. > > * I'd love to hear more about which ATX Socket 7 boards are > similarly damaged. So far, the data points I have are: > > -- Asus TX97-X: OK > -- Tyan S1572: BROKEN > -- Asus P5A: BROKEN? (was told, haven't seen this myself) > > The P5A is particularly disturbing, as it's the successor to the TX97-X, > with the Aladdin chipset. If this is true, then Asus is making > negative progress. > > Thanks in advance for any information. > > Jim Shankland > Flying Fox Computer Systems, Inc. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message >-- End of excerpt from Jim Shankland -- Pete McKenna Systems Engineer US WEST - !NTERACT Internet Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 12 18:26:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27865 for freebsd-hardware-outgoing; Mon, 12 Oct 1998 18:26:08 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27855 for ; Mon, 12 Oct 1998 18:26:02 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA21131; Tue, 13 Oct 1998 10:55:42 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id KAA03655; Tue, 13 Oct 1998 10:55:41 +0930 (CST) Message-ID: <19981013105541.U21983@freebie.lemis.com> Date: Tue, 13 Oct 1998 10:55:41 +0930 From: Greg Lehey To: Jim Shankland , hardware@FreeBSD.ORG Subject: Re: ATX boards and restart after power failure References: <199810121950.MAA15990@biggusdiskus.flyingfox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810121950.MAA15990@biggusdiskus.flyingfox.com>; from Jim Shankland on Mon, Oct 12, 1998 at 12:50:03PM -0700 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Monday, 12 October 1998 at 12:50:03 -0700, Jim Shankland wrote: > I know this has come up before, but I haven't found the discussion > in the archives. > > We have been building systems based on the Tyan S1572 motherboard > (ATX form factor, TX chipset). It turns out that when there's a > power failure, these systems stay down when power returns until > a human or other mammal presses the soft power-on button on the > front. Furthermore, *this "feature" cannot be disabled*. (On > the equivalent Asus board, the TX97-X, there's a BIOS option -- > "AC Pwr Loss Restart" -- to disable the "feature".) > > Now, I'm as much of a fan of power management as the next person, but > the mind-numbing stupidity of deliberately building a system that > can't be restarted without human intervention after a power failure > has me speechless (well, nearly). Maybe FreeBSD and Linux are barely > blips on these people's radar screens; but have they ever heard of > Windows NT? Or even Windows 95 users who want their machines to pick > up FAX calls around the clock? Assuming Pete McKenna's solution doesn't hold, have you thought of informing Tyan of your displeasure? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 12 21:47:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26767 for freebsd-hardware-outgoing; Mon, 12 Oct 1998 21:47:12 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [205.162.1.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26760 for ; Mon, 12 Oct 1998 21:47:11 -0700 (PDT) (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.8/8.8.5) id WAA17506; Mon, 12 Oct 1998 22:46:24 -0700 (PDT) Date: Mon, 12 Oct 1998 22:46:24 -0700 (PDT) From: Jim Shankland Message-Id: <199810130546.WAA17506@biggusdiskus.flyingfox.com> To: grog@lemis.com, hardware@FreeBSD.ORG Subject: Re: ATX boards and restart after power failure In-Reply-To: <19981013105541.U21983@freebie.lemis.com> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [Re: ATX m/boards that can't be made to power up without human intervention after a power failure:] Greg Lehey writes: > Assuming Pete McKenna's solution doesn't hold, have you thought of > informing Tyan of your displeasure? Already have. They apparently hear this complaint often enough that they have a ready-made letter apologizing for the inconvenience; nonetheless, the suggested remedy is to switch to a Pentium II m/b and CPU. The subtext here seems to be that as far as Intel is concerned, Socket 7 is dead, and AMD is positioning the K6 as a desktop/gaming chip. Maybe the m/b makers are even deliberately trying to migrate servers to the more expensive (and higher margin?) Pentium II boards. Or maybe they're just being dense. It's a shame, because I'm not crazy about Intel patenting Slot 1, and I'd like to support AMD just to prevent Intel hegemony, and the Socket 7/K6 combo is *plenty* powerful enough for my current purposes; and cost is an issue. Sigh. We'll definitely be trying Pete McKenna's solution; I'll drop a brief note saying how it worked out for us. Jim Shankland Flying Fox Computer Systems, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 13 07:32:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28957 for freebsd-hardware-outgoing; Tue, 13 Oct 1998 07:32:04 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from laker.net (jet.laker.net [205.245.74.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA28923 for ; Tue, 13 Oct 1998 07:31:58 -0700 (PDT) (envelope-from sfriedri@laker.net) Received: from nt (digital-pbi-135.laker.net [208.0.233.35]) by laker.net (8.9.0/8.9.LAKERNET.NO-SPAM.SPAMMERS.AND.RELAYS.WILL.BE.TRACKED.AND.PROSECUTED.) with SMTP id KAA25174; Tue, 13 Oct 1998 10:31:29 -0400 Message-Id: <199810131431.KAA25174@laker.net> From: "Steve Friedrich" To: "grog@lemis.com" , "hardware@FreeBSD.ORG" , "Jim Shankland" Date: Tue, 13 Oct 1998 10:30:41 -0400 Reply-To: "Steve Friedrich" X-Mailer: PMMail 98 Professional (2.01.1600) For Windows NT (4.0.1381;3) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: ATX boards and restart after power failure Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 12 Oct 1998 22:46:24 -0700 (PDT), Jim Shankland wrote: >[Re: ATX m/boards that can't be made to power up without human >intervention after a power failure:] > >Greg Lehey writes: > >> Assuming Pete McKenna's solution doesn't hold, have you thought of >> informing Tyan of your displeasure? > >Already have. They apparently hear this complaint often enough that >they have a ready-made letter apologizing for the inconvenience; >nonetheless, the suggested remedy is to switch to a Pentium II m/b >and CPU. But this is merely a feature of ATX. Switch to an AT (baby AT, etc.) m/b and you should be free of this feature... I have an ASUS TX97 which is also available as an ATX m/b. It doesn't have this feature, because it's not an ATX m/b. >The subtext here seems to be that as far as Intel is concerned, >Socket 7 is dead, and AMD is positioning the K6 as a desktop/gaming >chip. Maybe the m/b makers are even deliberately trying to migrate >servers to the more expensive (and higher margin?) Pentium II boards. >Or maybe they're just being dense. Intel's been wrong before... >It's a shame, because I'm not crazy about Intel patenting Slot 1, and >I'd like to support AMD just to prevent Intel hegemony, and the >Socket 7/K6 combo is *plenty* powerful enough for my current >purposes; and cost is an issue. Sigh. You are not alone... >We'll definitely be trying Pete McKenna's solution; I'll drop a >brief note saying how it worked out for us. Cool beans... Unix systems measure "uptime" in years, Winblows measures it in minutes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 13 07:45:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00374 for freebsd-hardware-outgoing; Tue, 13 Oct 1998 07:45:53 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from acc0.visti.net (acc0.visti.net [195.64.225.233]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00364 for ; Tue, 13 Oct 1998 07:45:47 -0700 (PDT) (envelope-from vit@visti.net) Received: from office.visti.net (office.visti.net [195.64.225.183]) by acc0.visti.net (8.8.8/8.8.8) with ESMTP id RAA25604 for ; Tue, 13 Oct 1998 17:45:24 +0300 (EEST) Received: from visti.net (post.visti.net [195.64.225.174]) by office.visti.net (8.6.12/8.ElVisti) with ESMTP id RAA03148 for ; Tue, 13 Oct 1998 17:43:40 +0300 Message-ID: <362368A9.7374E573@visti.net> Date: Tue, 13 Oct 1998 17:50:17 +0300 From: Vitaly Zubok X-Mailer: Mozilla 4.5b2 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hardware@FreeBSD.ORG Subject: Cyclom 16Ye problem (rev. 2.03) Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We use a number of Cyclom 16Ye cards rev. 1.02, these ISA cards work pretty nice in all our freebsd boxes. Recently we bought another Cyclom 16Ye, rev. 2.03. We can't find the reason why it works only in ancient i486 boxes and does'not work in any Pentium (chipsets VX, HX, LX tested). How it looks: it depends. On HX (P54TPI, Airwebs), cy driver can't find device after power-on. However, after testing with vendor's DOS diskette and soft reboot, everything is Ok until power switched off. On VX (Airwebs) and LX (Soltek, SL-66A) Cyclom card is always detected but does not work correctly: we can't talk to modem (no response on AT command), and after leaving the port DTE LED does not go off. The same story was described by Gediminas Vilutis 6 months ago (you'll find that msg at freebsd-questions archive). Definitely, there are some changes in this "new" rev. 2.03, is anyone going to do something with driver? We'll appreciate any answer, even ``yes'' or ``no'' :) -- Vitaly Y. Zubok (380 44) 2473940, 2440122 I.S.P. Administrator Kyiv, Ukraine ElVisti Information Center http://www.visti.net/~vit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 13 07:46:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00500 for freebsd-hardware-outgoing; Tue, 13 Oct 1998 07:46:17 -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 HAA00494 for ; Tue, 13 Oct 1998 07:46:16 -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 JAA11832; Tue, 13 Oct 1998 09:45:47 -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 JAA22661; Tue, 13 Oct 1998 09:45:46 -0500 (EST) Message-Id: <199810131445.JAA22661@tsunami.waterspout.com> To: "Jos M Alcaide" cc: freebsd-hardware@FreeBSD.ORG Subject: Re: 3.0R on Iwill DBL100 or Asus P2B-DS ? In-reply-to: Your message of "Fri, 09 Oct 1998 15:52:24 +0200." <361E1518.9BC322C@we.lc.ehu.es> Date: Tue, 13 Oct 1998 09:45:46 -0500 From: "C. Stephen Gunn" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <361E1518.9BC322C@we.lc.ehu.es>, "Jos M Alcaide" writes: Jose, >Then, our main options are the Iwill DBL100 and the Asus P2B-DS >(we want the SCSI bus). I work days for the Physics Department at Purdue University. We have a couple of ASUS machines in production. In particular, we have a Dual Pentium II 450, on an ASUS P2B-DS. It just works. Its current configuration is: ASUS P2B-DS, Dual Pentium II 450, 512M PC-100 Memory A single 4.5Gb Ultra2W SCSI Drive 2 x 3Com 3c905b cards using the xl driver It's an a rackmount case from APPRO, which we have been _VERY_ pleased with. Especially for the cost.. under $400 with the rails. Amazing. It's currently running one of the ELF beta installs, and gets upgraded nearly daily. (It's not in production yet, we were waiting on 3.0 to go final) We've also been running ASUS P5A's with K6-2 300's under FreeBSD and they just ROCK AND ROLL. - Steve -- WaterSpout Communications, Inc. Email: csg@waterspout.com 1291 Cumberland Ave, Suite C Phone: (765) 775-4512 West Lafayette, IN 47906 Fax: (765) 463-7004 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 13 08:10:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03001 for freebsd-hardware-outgoing; Tue, 13 Oct 1998 08:10:20 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02993 for ; Tue, 13 Oct 1998 08:10:16 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id BAA24392; Wed, 14 Oct 1998 01:09:59 +1000 Date: Wed, 14 Oct 1998 01:09:59 +1000 From: Bruce Evans Message-Id: <199810131509.BAA24392@godzilla.zeta.org.au> To: freebsd-hardware@FreeBSD.ORG, vit@visti.net Subject: Re: Cyclom 16Ye problem (rev. 2.03) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Recently we bought another Cyclom 16Ye, rev. 2.03. >We can't find the reason why it works only in ancient >i486 boxes and does'not work in any Pentium (chipsets >VX, HX, LX tested). The hardware changed. Recent versions shouldn't work even in ancient i486 boxes under any released version of FreeBSD. You need a modified version from www.cyclades.com for FreeBSD-2.2.[5-7]. FreeBSD-current has native support. FreeBSD-2.2.8 should have native support. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 13 11:44:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29516 for freebsd-hardware-outgoing; Tue, 13 Oct 1998 11:44:45 -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 LAA29504 for ; Tue, 13 Oct 1998 11:44: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 OAA02359 for ; Tue, 13 Oct 1998 14:44:13 -0400 Date: Tue, 13 Oct 1998 14:44:12 -0400 (EDT) From: Jamie Bowden To: hardware@FreeBSD.ORG Subject: Motherboards. 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 am looking for a motherboard with as many pci slots as I can get. A full 8 would be nice. It's really annoying that no one would have been able to sell a 486 or 386 board without 8 isa slots, but it's hard to find a decent pci MB with 5, much less more. SuperMicro has an 11 slot with 8 pci and 3 isa, but it's I2O, and I refuse to go there. I am going to be doing a processor upgrade in the near future, and while I would like to buy a K6/2, I will probably go P2 just because the Slot 1 boards I've seen tend to have more pci slots than the Super 7 boards. 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 Tue Oct 13 12:26:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05134 for freebsd-hardware-outgoing; Tue, 13 Oct 1998 12:26:07 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mail.intercom.com ([207.51.55.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05129 for ; Tue, 13 Oct 1998 12:26:05 -0700 (PDT) (envelope-from jason@intercom.com) Received: from localhost (jason@localhost) by mail.intercom.com (8.9.0/8.9.0) with SMTP id PAA26686; Tue, 13 Oct 1998 15:25:46 -0400 (EDT) Date: Tue, 13 Oct 1998 15:25:46 -0400 (EDT) From: jason To: Jamie Bowden cc: hardware@FreeBSD.ORG Subject: Re: Motherboards. In-Reply-To: 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 Go rackmount... alot of 19" rackmount cases support up to 20 slots in a passive backplane form factor. Interlogic makes custom backplanes, might be able to talk them into making a 19 slot PCI system (19 PCI slots, one motherboard slot). This is the option if you have some extra bucks to spend. http://www.infoview.com/ -J To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 13 13:30:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17495 for freebsd-hardware-outgoing; Tue, 13 Oct 1998 13:30:14 -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 NAA17470 for ; Tue, 13 Oct 1998 13:30:06 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA01142; Tue, 13 Oct 1998 13:33:33 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810132033.NAA01142@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jamie Bowden cc: hardware@FreeBSD.ORG Subject: Re: Motherboards. In-reply-to: Your message of "Tue, 13 Oct 1998 14:44:12 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Oct 1998 13:33:33 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I am looking for a motherboard with as many pci slots as I can get. A > full 8 would be nice. It's really annoying that no one would have been > able to sell a 486 or 386 board without 8 isa slots, but it's hard to > find a decent pci MB with 5, much less more. SuperMicro has an 11 slot > with 8 pci and 3 isa, but it's I2O, and I refuse to go there. I am > going to be doing a processor upgrade in the near future, and while I > would like to buy a K6/2, I will probably go P2 just because the Slot 1 > boards I've seen tend to have more pci slots than the Super 7 boards. To get more than 4 or 5 slots you need to put a bridge on the board; this tends to drive the cost a long way up. You might want to look at a passive backplane solution; boards with 8 or 12 slots are common, though they usually take PICMG (sp?) processor cards, and you're looking at a lot more money here. -- \\ 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 Oct 13 18:48:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13570 for freebsd-hardware-outgoing; Tue, 13 Oct 1998 18:48:41 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from rovis.com (tony1.mpinet.net [208.6.199.201] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13548; Tue, 13 Oct 1998 18:48:37 -0700 (PDT) (envelope-from adchen@skatefaq.com) Received: from [138.210.141.219] ([138.210.141.219]) by rovis.com (8.9.1/8.9.1) with ESMTP id VAA06171; Tue, 13 Oct 1998 21:47:59 -0400 (EDT) X-Sender: adchen@skatefaq.com (Unverified) Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 13 Oct 1998 21:50:22 -0400 To: freebsd-hardware@FreeBSD.ORG, freebsd-net@FreeBSD.ORG From: Tony Chen Subject: ethernet card weirdness Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, Have an odd problem, not sure if a hardware problem or a network/OS problem. System: VA-502 motherboard 32 MB 6x86 PR200+ FreeBSD 2.2.7-stable SMC EtherPower PCI card, (SMC8432T) 10-baseT Part 1: ------- Originally this machine was using 2.2.2-stable. The PCI Ethernet card is on de0 and has about 16 ip aliased on it. Every few days (sometimes several times a day) the interface will stop working. No packets out, no packets in - link light on the ethernet card shows link (green) but no traffic. There *were* only two ways to wake it back up: 1) reboot, 2) do "ifconfig de0 down" followed by "ifconfig de0 up". We had a script do #2 whenever it could ping out. Crude, but it worked. Part 2: ------- A while later, we upgraded to 2.2.7-stable. The network card still goes silent but now the ifconfig down/up trick no longer wakes the interface back up. Now only a reboot will make it work again. Not good. The included DOS diagnostic programs show the card appears to be fine hardware-wise. We even swapped in another ethernet card, exact same model, brand-new, and the problem still occurs. We tried different PCI slots on the motherboard with each card. Still happens. So is this a hardware compatibility problem or an OS problem? Thanks for any help. -Tony Chen adchen@skatefaq.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 13 19:28:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA19557 for freebsd-hardware-outgoing; Tue, 13 Oct 1998 19:28:46 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA19546 for ; Tue, 13 Oct 1998 19:28:41 -0700 (PDT) (envelope-from girgen@partitur.se) Received: from partitur.se (solist.partitur.se [193.219.246.204]) by bastuba.partitur.se (8.8.8/8.8.8) with ESMTP id EAA20935 for ; Wed, 14 Oct 1998 04:28:25 +0200 (CEST) (envelope-from girgen@partitur.se) Message-ID: <36240C47.ED276B4B@partitur.se> Date: Wed, 14 Oct 1998 04:28:23 +0200 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.5b2 [en] (X11; I; SunOS 5.6 sun4u) X-Accept-Language: sv,en MIME-Version: 1.0 To: freebsd-hardware@FreeBSD.ORG Subject: pax killing scsi w/ 2940UW (ahc) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! Yesterday I wanted to move a directory structure to a different disk on one of our servers. Suddenly, the scsi bus was reset, and reset again and again. The system did hardly accept input. After about a minute or so, with the taper going nuts (from all the resets), the system rebooted??!! Nothing similar has ever happened before, not to me! Since this was midday, with people working, it was not good. :) No problem getting it up again, though. This evening, I though I'd take antoher shot at it. Same thing happens, only this time i hit ctrl-C, and pax stops fine. I'm using an adaptec 2940UW on a pentium Pro with four disks and a taper unit. The last disk is pretty newly installed. I have compiled the kernel with these options: options AHC_SCBPAGING_ENABLE options AHC_ALLOW_MEMIO options AHC_TAGENABLE This has been working fine for more than a year, but maybe this was too much for it? Don't remember moving large quantities with pax before; I probably used tar. uname -a: FreeBSD trumpet.partitur.se 2.2.7-STABLE FreeBSD 2.2.7-STABLE #0: Mon Sep 28 16:07:19 CEST 1998 girgen@trumpet.partitur.se:/disk1/src/sys/compile/TRUMPET i386 Here's a demsg starting from the problem time: sd3(ahc0:3:0): SCB 0xa - timed out in dataout phase, SCSISIGI == 0x4 SEQADDR = 0x127 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x2 Ordered Tag queued sd3(ahc0:3:0): SCB 0xf timedout while recovery in progress sd3(ahc0:3:0): SCB 0x7 timedout while recovery in progress sd0(ahc0:0:0): SCB 0x1 timedout while recovery in progress sd3(ahc0:3:0): SCB 0x5 timedout while recovery in progress sd3(ahc0:3:0): SCB 0xa - timed out in dataout phase, SCSISIGI == 0x4 SEQADDR = 0x127 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x2 sd3(ahc0:3:0): abort message in message buffer sd3(ahc0:3:0): SCB 0x7 - timed out in dataout phase, SCSISIGI == 0x14 SEQADDR = 0x127 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x2 sd3(ahc0:3:0): no longer in timeout sd3(ahc0:3:0): no longer in timeout ahc0: Issued Channel A Bus Reset. 6 SCBs aborted sd3(ahc0:3:0): UNIT ATTENTION asc:29,0 sd3(ahc0:3:0): Power on, reset, or bus device reset occurred , retries:3 sd2(ahc0:2:0): UNIT ATTENTION asc:29,0 sd2(ahc0:2:0): Power on, reset, or bus device reset occurred , retries:4 sd0(ahc0:0:0): UNIT ATTENTION asc:29,0 sd0(ahc0:0:0): Power on, reset, or bus device reset occurred field replaceable unit: 1 , retries:3 sd1(ahc0:1:0): UNIT ATTENTION asc:29,0 sd1(ahc0:1:0): Power on, reset, or bus device reset occurred , retries:4 sd2(ahc0:2:0): SCB 0xa - timed out in dataout phase, SCSISIGI == 0x4 SEQADDR = 0x127 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x2 Ordered Tag queued sd2(ahc0:2:0): SCB 0x2 timedout while recovery in progress sd3(ahc0:3:0): SCB 0xf timedout while recovery in progress sd2(ahc0:2:0): SCB 0xa - timed out in dataout phase, SCSISIGI == 0x4 SEQADDR = 0x126 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x2 sd3(ahc0:3:0): abort message in message buffer sd3(ahc0:3:0): SCB 0xf - timed out in dataout phase, SCSISIGI == 0x14 SEQADDR = 0x126 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x2 sd2(ahc0:2:0): no longer in timeout sd3(ahc0:3:0): no longer in timeout ahc0: Issued Channel A Bus Reset. 4 SCBs aborted sd2(ahc0:2:0): UNIT ATTENTION asc:29,0 sd2(ahc0:2:0): Power on, reset, or bus device reset occurred , retries:3 sd3(ahc0:3:0): UNIT ATTENTION asc:29,0 sd3(ahc0:3:0): Power on, reset, or bus device reset occurred , retries:3 sd0(ahc0:0:0): UNIT ATTENTION asc:29,0 sd0(ahc0:0:0): Power on, reset, or bus device reset occurred field replaceable unit: 1 , retries:3 sd2(ahc0:2:0): SCB 0x4 - timed out in dataout phase, SCSISIGI == 0x4 SEQADDR = 0x127 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x2 Ordered Tag queued sd2(ahc0:2:0): SCB 0xa timedout while recovery in progress sd3(ahc0:3:0): SCB 0x7 timedout while recovery in progress sd2(ahc0:2:0): SCB 0x1 timedout while recovery in progress sd0(ahc0:0:0): SCB 0xe timedout while recovery in progress sd2(ahc0:2:0): SCB 0x4 - timed out in dataout phase, SCSISIGI == 0x4 SEQADDR = 0x127 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x2 sd3(ahc0:3:0): abort message in message buffer sd2(ahc0:2:0): SCB 0xc timedout while recovery in progress sd0(ahc0:0:0): SCB 0x8 timedout while recovery in progress sd0(ahc0:0:0): SCB 0x5 timedout while recovery in progress sd3(ahc0:3:0): SCB 0xf timedout while recovery in progress sd3(ahc0:3:0): SCB 0xd timedout while recovery in progress sd3(ahc0:3:0): SCB 0x2 timedout while recovery in progress sd0(ahc0:0:0): SCB 0x9 timedout while recovery in progress sd3(ahc0:3:0): SCB 0x7 - timed out in dataout phase, SCSISIGI == 0x14 SEQADDR = 0x126 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x2 sd2(ahc0:2:0): no longer in timeout sd3(ahc0:3:0): no longer in timeout ahc0: Issued Channel A Bus Reset. 12 SCBs aborted sd2(ahc0:2:0): UNIT ATTENTION asc:29,0 sd2(ahc0:2:0): Power on, reset, or bus device reset occurred , retries:3 sd3(ahc0:3:0): UNIT ATTENTION asc:29,0 sd3(ahc0:3:0): Power on, reset, or bus device reset occurred , retries:3 sd0(ahc0:0:0): UNIT ATTENTION asc:29,0 sd0(ahc0:0:0): Power on, reset, or bus device reset occurred field replaceable unit: 1 , retries:3 sd1(ahc0:1:0): UNIT ATTENTION asc:29,0 I will try removing the tagenable option. Wonder if it'll help? What else can be the cause? /Palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 13 20:38:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA27607 for freebsd-hardware-outgoing; Tue, 13 Oct 1998 20:38:47 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA27568 for ; Tue, 13 Oct 1998 20:37:57 -0700 (PDT) (envelope-from girgen@partitur.se) Received: from partitur.se (solist.partitur.se [193.219.246.204]) by bastuba.partitur.se (8.8.8/8.8.8) with ESMTP id FAA21326 for ; Wed, 14 Oct 1998 05:37:36 +0200 (CEST) (envelope-from girgen@partitur.se) Message-ID: <36241C7F.95DE0CC3@partitur.se> Date: Wed, 14 Oct 1998 05:37:35 +0200 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.5b2 [en] (X11; I; SunOS 5.6 sun4u) X-Accept-Language: sv,en MIME-Version: 1.0 To: freebsd-hardware@FreeBSD.ORG Subject: Re: pax killing scsi w/ 2940UW (ahc) References: <36240C47.ED276B4B@partitur.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hello again! I tried removing the TAGENABLE, same thing happens. Tried tar instead of pax, same thing happens. :( I enclose a dmesg of the system startup. This is with TAGENABLE back on. The failing copy is from sd2 to sd3. As you can see, the disks' types are the same. Can anybody shed some light on this, please? TIA Palle FreeBSD 2.2.7-STABLE #0: Wed Oct 14 05:15:25 CEST 1998 root@trumpet.partitur.se:/disk3/src/sys/compile/TRUMPET CPU: Pentium Pro (198.95-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x617 Stepping=7 Features=0xfbff real memory = 201326592 (196608K bytes) avail memory = 194760704 (190196K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0:0 chip1 rev 0 on pci0:7:0 chip2 rev 0 on pci0:7:1 de0 rev 32 int a irq 9 on pci0:11:0 de0: SMC 9332BDT 21140A [10-100Mb/s] pass 2.0 de0: address 00:00:c0:27:eb:e9 vga0 rev 84 int a irq 10 on pci0:12:0 ahc0 rev 0 int a irq 11 on pci0:13:0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs ahc0 waiting for scsi devices to settle ahc0: target 0 Tagged Queuing Device (ahc0:0:0): "SEAGATE ST32155W 0528" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 2049MB (4197405 512 byte sectors) ahc0: target 1 Tagged Queuing Device (ahc0:1:0): "IBM DCAS-34330W S65A" type 0 fixed SCSI 2 sd1(ahc0:1:0): Direct-Access 4134MB (8467200 512 byte sectors) ahc0: target 2 Tagged Queuing Device (ahc0:2:0): "IBM DCAS-34330W S65A" type 0 fixed SCSI 2 sd2(ahc0:2:0): Direct-Access 4134MB (8467200 512 byte sectors) ahc0: target 3 Tagged Queuing Device (ahc0:3:0): "IBM DCAS-34330W S65A" type 0 fixed SCSI 2 sd3(ahc0:3:0): Direct-Access 4134MB (8467200 512 byte sectors) (ahc0:5:0): "CONNER CTT8000-S 1.07" type 1 removable SCSI 2 st0(ahc0:5:0): Sequential-Access density code 0x45, drive empty Probing for PnP devices: No Plug-n-Play devices were found Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <7 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 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 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (atapi): , removable, dma, iordy wcd0: 687Kb/sec, 240Kb cache, audio play, 2 volume levels, ejectable tray wcd0: 120mm data disc loaded, unlocked npx0 flags 0x1 on motherboard npx0: INT 16 interface 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 Tue Oct 13 21:04:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA00812 for freebsd-hardware-outgoing; Tue, 13 Oct 1998 21:04:53 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA00795 for ; Tue, 13 Oct 1998 21:04:49 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id WAA07215; Tue, 13 Oct 1998 22:04:25 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810140404.WAA07215@panzer.plutotech.com> Subject: Re: pax killing scsi w/ 2940UW (ahc) In-Reply-To: <36240C47.ED276B4B@partitur.se> from Palle Girgensohn at "Oct 14, 98 04:28:23 am" To: girgen@partitur.se (Palle Girgensohn) Date: Tue, 13 Oct 1998 22:04:25 -0600 (MDT) Cc: freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Palle Girgensohn wrote... > Hi! > > Yesterday I wanted to move a directory structure to a different disk on > one of our servers. Suddenly, the scsi bus was reset, and reset again > and again. The system did hardly accept input. After about a minute or > so, with the taper going nuts (from all the resets), the system > rebooted??!! > > Nothing similar has ever happened before, not to me! > Since this was midday, with people working, it was not good. :) No > problem getting it up again, though. > > This evening, I though I'd take antoher shot at it. Same thing happens, > only this time i hit ctrl-C, and pax stops fine. > > I'm using an adaptec 2940UW on a pentium Pro with four disks and a taper > unit. The last disk is pretty newly installed. I have compiled the ^^^^^^^^^^^^^^^^^^^^^^ > kernel with these options: > > options AHC_SCBPAGING_ENABLE > options AHC_ALLOW_MEMIO > options AHC_TAGENABLE > > This has been working fine for more than a year, but maybe this was too > much for it? Don't remember moving large quantities with pax before; I > probably used tar. > > uname -a: > > FreeBSD trumpet.partitur.se 2.2.7-STABLE FreeBSD 2.2.7-STABLE #0: Mon > Sep 28 16:07:19 CEST 1998 > girgen@trumpet.partitur.se:/disk1/src/sys/compile/TRUMPET i386 > > Here's a demsg starting from the problem time: > > sd3(ahc0:3:0): SCB 0xa - timed out in dataout phase, SCSISIGI == 0x4 > SEQADDR = 0x127 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0x2 > Ordered Tag queued This looks like it might be a cabling or termination problem. Make sure your cable isn't kinked, too near a power supply, etc. Make sure your SCSI chain is terminated in the proper places, etc. It could be something else of course, but the "timed out in dataout phase" messages (or "timed out in datain phase") are often indicative of lost signals on the SCSI bus, Since your disk is newly installed, I would suspect that the change in your setup has triggered the problem. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 14 04:04:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA11180 for freebsd-hardware-outgoing; Wed, 14 Oct 1998 04:04:28 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from post.mail.demon.net (post-11.mail.demon.net [194.217.242.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA11161; Wed, 14 Oct 1998 04:04:26 -0700 (PDT) (envelope-from freebsd-root@i-zone.demon.co.uk) Received: from [158.152.227.78] (helo=i-zone.demon.co.uk) by post.mail.demon.net with smtp (Exim 2.05 #1) id 0zTOiu-0002nQ-00; Wed, 14 Oct 1998 11:04:09 +0000 Message-ID: Date: Wed, 14 Oct 1998 10:14:10 +0100 To: freebsd-questions@FreeBSD.ORG Cc: freebsd-hardware@FreeBSD.ORG From: John Subject: FreeBSD, maximum memory and 440TX chipset MIME-Version: 1.0 X-Mailer: Turnpike (32) Version 4.00 <5jmCrxUbpyYdwGXid1yqlWD9$N> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello experts (cc'd to freebsd-hardware where it is also relevant) I have an Abit PX5 (440TX) motherboard. I have been advised that, as a win98 machine at least, adding more RAM than 64MB will see a performance hit in the order of 10% as the chipset cannot cache more than 64MB. The cpu is an Intel P166MMX The board can take up to 256MB My questions: Will I see this performance hit in FreeBSD? i.e. is this issue solely chipset specific? Does anyone else here run more than 64MB on a 440tx chipset? Thanks -- John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 14 08:50:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09607 for freebsd-hardware-outgoing; Wed, 14 Oct 1998 08:50:44 -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 IAA09585; Wed, 14 Oct 1998 08:50:40 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA01000; Wed, 14 Oct 1998 08:55:18 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810141555.IAA01000@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John cc: freebsd-questions@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: FreeBSD, maximum memory and 440TX chipset In-reply-to: Your message of "Wed, 14 Oct 1998 10:14:10 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 14 Oct 1998 08:55:18 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hello experts > > (cc'd to freebsd-hardware where it is also relevant) > > I have an Abit PX5 (440TX) motherboard. I have been advised that, as a > win98 machine at least, adding more RAM than 64MB will see a performance > hit in the order of 10% as the chipset cannot cache more than 64MB. > > The cpu is an Intel P166MMX > > The board can take up to 256MB > > My questions: > > Will I see this performance hit in FreeBSD? i.e. is this issue solely > chipset specific? Does anyone else here run more than 64MB on a 440tx > chipset? It's a feature of the 430TX and 430VX chipsets, and yes, once you start using memory over the 64M mark you will find it hurts FreeBSD too. -- \\ 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 Oct 14 12:30:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12806 for freebsd-hardware-outgoing; Wed, 14 Oct 1998 12:30:14 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from post.mail.demon.net (post-11.mail.demon.net [194.217.242.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12719; Wed, 14 Oct 1998 12:30:05 -0700 (PDT) (envelope-from freebsd-root@i-zone.demon.co.uk) Received: from [158.152.227.78] (helo=i-zone.demon.co.uk) by post.mail.demon.net with smtp (Exim 2.05 #1) id 0zTWc9-00037q-00; Wed, 14 Oct 1998 19:29:42 +0000 Message-ID: Date: Wed, 14 Oct 1998 19:05:24 +0100 To: freebsd-questions@FreeBSD.ORG Cc: freebsd-hardware@FreeBSD.ORG From: John Subject: Re: FreeBSD, maximum memory and 440TX chipset References: <199810141555.IAA01000@dingo.cdrom.com> In-Reply-To: <199810141555.IAA01000@dingo.cdrom.com> MIME-Version: 1.0 X-Mailer: Turnpike (32) Version 4.00 <5jmCrxUbpyYdwGXid1yqlWD9$N> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199810141555.IAA01000@dingo.cdrom.com>, Mike Smith writes >> Hello experts >> >> (cc'd to freebsd-hardware where it is also relevant) >> >> I have an Abit PX5 (440TX) motherboard. I have been advised that, as a >> win98 machine at least, adding more RAM than 64MB will see a performance >> hit in the order of 10% as the chipset cannot cache more than 64MB. >> >> The cpu is an Intel P166MMX >> >> The board can take up to 256MB >> >> My questions: >> >> Will I see this performance hit in FreeBSD? i.e. is this issue solely >> chipset specific? Does anyone else here run more than 64MB on a 440tx >> chipset? > >It's a feature of the 430TX and 430VX chipsets, and yes, once you start >using memory over the 64M mark you will find it hurts FreeBSD too. > Argh. Thanks for clarifying. Can you tell me what other boards are out there that don't exhibit this (cough) feature, or if they do, at what RAM capacity do they exhibit it? (just wanting to avoid the same sort of mistake again). Thanks -- John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 14 14:28:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28543 for freebsd-hardware-outgoing; Wed, 14 Oct 1998 14:28:39 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from laker.net (jet.laker.net [205.245.74.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28538; Wed, 14 Oct 1998 14:28:36 -0700 (PDT) (envelope-from sfriedri@laker.net) Received: from nt (digital-pbi-145.laker.net [208.0.233.45]) by laker.net (8.9.0/8.9.LAKERNET.NO-SPAM.SPAMMERS.AND.RELAYS.WILL.BE.TRACKED.AND.PROSECUTED.) with SMTP id RAA04870; Wed, 14 Oct 1998 17:28:07 -0400 Message-Id: <199810142128.RAA04870@laker.net> From: "Steve Friedrich" To: "freebsd-questions@FreeBSD.ORG" , "John" Cc: "freebsd-hardware@FreeBSD.ORG" Date: Wed, 14 Oct 1998 17:26:51 -0400 Reply-To: "Steve Friedrich" X-Mailer: PMMail 98 Professional (2.01.1600) For Windows NT (4.0.1381;3) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD, maximum memory and 440TX chipset Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 14 Oct 1998 19:05:24 +0100, John wrote: >In article <199810141555.IAA01000@dingo.cdrom.com>, Mike Smith > writes >>> Hello experts >>> >>> (cc'd to freebsd-hardware where it is also relevant) >>> >>> I have an Abit PX5 (440TX) motherboard. I have been advised that, as a >>> win98 machine at least, adding more RAM than 64MB will see a performance >>> hit in the order of 10% as the chipset cannot cache more than 64MB. >>> >>> The cpu is an Intel P166MMX >>> >>> The board can take up to 256MB >>> >>> My questions: >>> >>> Will I see this performance hit in FreeBSD? i.e. is this issue solely >>> chipset specific? Does anyone else here run more than 64MB on a 440tx >>> chipset? >> >>It's a feature of the 430TX and 430VX chipsets, and yes, once you start >>using memory over the 64M mark you will find it hurts FreeBSD too. >> > >Argh. Thanks for clarifying. Can you tell me what other boards are out >there that don't exhibit this (cough) feature, or if they do, at what >RAM capacity do they exhibit it? (just wanting to avoid the same sort of >mistake again). You have to check each board you're looking at to see which "glue" chipset it uses. Intel makes several, as well as a few other manufacturers. Take a look at: http://www.anandtech.com/chipset.html Unix systems measure "uptime" in years, Winblows measures it in minutes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Oct 15 16:57:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29691 for freebsd-hardware-outgoing; Thu, 15 Oct 1998 16:57:57 -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 QAA29686 for ; Thu, 15 Oct 1998 16:57:55 -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 TAA22213 for ; Thu, 15 Oct 1998 19:57:00 -0400 (EDT) Date: Thu, 15 Oct 1998 19:57:00 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: freebsd-hardware@FreeBSD.ORG Subject: IBM DDRS-39130 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 Hi, Just a quick check on everyone's opinion of the IBM DDRS-39130 4G U/W drive. The specs look good, they are quiet, and pretty cheap compared to the Barracudas we've been buying. Has anyone had a bad experience with these? Anyone used them with a CMD Raid controller? (they aren't listed in the "approved drives" section of the cmd website) Thanks, Charles --- Charles Sprickman spork@super-g.com --- "...there's no idea that's so good you can't ruin it with a few well-placed idiots." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Oct 15 20:23:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA27019 for freebsd-hardware-outgoing; Thu, 15 Oct 1998 20:23:24 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA27009 for ; Thu, 15 Oct 1998 20:23:19 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA08488; Fri, 16 Oct 1998 12:52:46 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA18408; Fri, 16 Oct 1998 12:52:24 +0930 (CST) Message-ID: <19981016125224.X468@freebie.lemis.com> Date: Fri, 16 Oct 1998 12:52:24 +0930 From: Greg Lehey To: spork , freebsd-hardware@FreeBSD.ORG Subject: Re: IBM DDRS-39130 drive References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from spork on Thu, Oct 15, 1998 at 07:57:00PM -0400 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thursday, 15 October 1998 at 19:57:00 -0400, spork wrote: > Hi, > > Just a quick check on everyone's opinion of the IBM DDRS-39130 4G U/W > drive. The specs look good, they are quiet, and pretty cheap compared to > the Barracudas we've been buying. I've had pretty good experiences with IBM disks generally, but I don't have any experience of this particular drive. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Oct 15 21:33:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06657 for freebsd-hardware-outgoing; Thu, 15 Oct 1998 21:33:35 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06614 for ; Thu, 15 Oct 1998 21:33:18 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id VAA09147; Thu, 15 Oct 1998 21:32:50 -0700 (PDT) (envelope-from jdp) Message-Id: <199810160432.VAA09147@austin.polstra.com> To: spork@super-g.com Subject: Re: IBM DDRS-39130 drive In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: hardware@FreeBSD.ORG Date: Thu, 15 Oct 1998 21:32:49 -0700 From: John Polstra Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article , spork wrote: > Hi, > > Just a quick check on everyone's opinion of the IBM DDRS-39130 4G U/W > drive. I believe that model number is for the 9.1 GB drive. The 4.5 GB drive is DDRS-34560W. I have three of the 34560W drives in a machine here, and they're dynamite. Check it out: vashon$ dd if=/dev/rda2 of=/dev/null bs=64k count=1000 1000+0 records in 1000+0 records out 65536000 bytes transferred in 4.927831 secs (13299157 bytes/sec) The drives are reasonably quiet and run cool. When I received the drives, one of them had zillions of bad blocks. I had to exchange it under warranty. However, I'm convinced that it had gotten damaged during shipment. (The vendor said he tested the system before shipping it, and it was fine at that point.) Since getting the replacement drive, I haven't seen any anomalies with these drives at all. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 16 01:22:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28009 for freebsd-hardware-outgoing; Fri, 16 Oct 1998 01:22:45 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ns.new-mediacom.co.uk (ns.new-mediacom.co.uk [193.192.221.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28004 for ; Fri, 16 Oct 1998 01:22:41 -0700 (PDT) (envelope-from alex@targeting.co.uk) Received: by ns.new-mediacom.co.uk with Internet Mail Service (5.0.1459.74) id ; Fri, 16 Oct 1998 09:16:56 +0100 Message-ID: <615CAC0140CED111AF1500805FEDDB8A094A4E@ns.new-mediacom.co.uk> From: Alex Knowles To: "'Freebsd-Hardware (E-mail)" Subject: newbie setup Date: Fri, 16 Oct 1998 09:16:55 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1459.74) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi first post etc etc I hope this is to the right place! I'm about to set a new server system for the company i work for and was planning to set a bsd box to run the web server/internal file server/print server. At the moment a nt box handles (ish!) all this, and i want to keep this as an outlook server for mail etc. Can anyone forsee any problems with this plan? the office uses nt and mac. I have previously used redhat (this is probably a dangerous admission to make on this group!!) and I know that it can only see fat16 on internal partitions, but it would be ok to use smb to see nt folders (i hope this is ok!). so acouple of questions: will Nt be able to read files stored on the bsd box and vice versa will macs be able to do the same (particularly g3's) will an nt outlook server be able to run in parallel we also want to have an automatic dat backup, can anyone forsee any problems/software we need etc. or is it easier for an nt box to do this ? and then hardware compatibility: I shall probably have the following spec: PII 350 or 450 (if some spare cash is lying around!!!) adaptec 2940 UW SCSI controller 9 Gig Fast wide SCSI Hard drive 100 Mb/s 3com network card S3 Virge Graphics card Connected to an optic line via a 3com router I'm really sorry this post is so long. and thanks alot in advance. alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" 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 Fri Oct 16 01:36:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29122 for freebsd-hardware-outgoing; Fri, 16 Oct 1998 01:36:48 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (castles312.castles.com [208.214.167.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29113 for ; Fri, 16 Oct 1998 01:36:45 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id BAA01817; Fri, 16 Oct 1998 01:41:16 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810160841.BAA01817@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alex Knowles cc: "'Freebsd-Hardware (E-mail)" Subject: Re: newbie setup In-reply-to: Your message of "Fri, 16 Oct 1998 09:16:55 BST." <615CAC0140CED111AF1500805FEDDB8A094A4E@ns.new-mediacom.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 16 Oct 1998 01:41:15 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > so acouple of questions: > will Nt be able to read files stored on the bsd box and vice versa Yes, and yes if you use the Sharity product (available in a free 'light' version or the full commercial version) > will macs be able to do the same (particularly g3's) You can support Appletalk filesharing with the BSD system, or you can use Samba and the "Dave" product for MacOS. > will an nt outlook server be able to run in parallel Yes. > we also want to have an automatic dat backup, can anyone forsee any > problems/software we need etc. or is it easier for an nt box to do this ? You almost certainly want two backups, one on each server. > and then hardware compatibility: > I shall probably have the following spec: > > PII 350 or 450 (if some spare cash is lying around!!!) > adaptec 2940 UW SCSI controller > 9 Gig Fast wide SCSI Hard drive > 100 Mb/s 3com network card > S3 Virge Graphics card > Connected to an optic line via a 3com router This is probably gross overkill; unless you have > 50 workstations you could probably swing it with a P166 and an IDE disk. A server like this doesn't need much CPU; if a slow PII would give you more cash for RAM or disk space, it's better spent there than on wasted cycles. For a good example doing basic file service: ftp.cdrom.com supports > 3000 simultaneous users at 400GB+/day throughput on a P6/200 with 1GB of RAM. You don't need lots of CPU; you want disk and RAM (for disk cache). If you're going to use a 3C905, make sure you're installing 2.2.7-stable on the system (ie. go to releng22.freebsd.org to do your install), as support for these cards was not in 2.2.7-RELEASE. Alternatively, use an Intel EtherExpress Pro/100B. -- \\ 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 Oct 16 01:43:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29661 for freebsd-hardware-outgoing; Fri, 16 Oct 1998 01:43:14 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29640; Fri, 16 Oct 1998 01:43:09 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id SAA09448; Fri, 16 Oct 1998 18:12:49 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id SAA00699; Fri, 16 Oct 1998 18:12:43 +0930 (CST) Message-ID: <19981016181243.G514@freebie.lemis.com> Date: Fri, 16 Oct 1998 18:12:43 +0930 From: Greg Lehey To: Alex Knowles , FreeBSD Questions Subject: Re: newbie setup References: <615CAC0140CED111AF1500805FEDDB8A094A4E@ns.new-mediacom.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <615CAC0140CED111AF1500805FEDDB8A094A4E@ns.new-mediacom.co.uk>; from Alex Knowles on Fri, Oct 16, 1998 at 09:16:55AM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Friday, 16 October 1998 at 9:16:55 +0100, Alex Knowles wrote: > Hi first post etc etc I hope this is to the right place! Well, no, this is for discussing hardware. I've replied to FreeBSD-questions, which is the correct address. > I'm about to set a new server system for the company i work for and was > planning to set a bsd box to run the web server/internal file server/print > server. > > At the moment a nt box handles (ish!) all this, and i want to keep this as > an outlook server for mail etc. > > Can anyone forsee any problems with this plan? Yes. Outlook is one of the most obscene programs I have ever seen. Most messages I receive from Outlook are mutilated in some way or another. > the office uses nt and mac. I have previously used redhat (this is > probably a dangerous admission to make on this group!!) and I know > that it can only see fat16 on internal partitions, but it would be > ok to use smb to see nt folders (i hope this is ok!). Should be. If you're running a server, you should only have one OS on the system, so you won't have any local Microsoft partitions. > so acouple of questions: > will Nt be able to read files stored on the bsd box and vice versa If you use Samba, yes. > will macs be able to do the same (particularly g3's) I don't know. You'd presumably need Appletalk, about which I know nothing. > will an nt outlook server be able to run in parallel I don't know. I don't do Microsoft. It seems unlikely that you could have any two machines running in parallel and receiving the same mail. But you could get the FreeBSD box to forward the messages to the Microsoft box and also deliver mail locally. > we also want to have an automatic dat backup, can anyone > forsee any problems/software we need etc. No. You don't need any special software, though I'm sure lots of people will recommend things like Amanda (Ports Collection). > or is it easier for an nt box to do this ? It's definitely not easier for an NT box to handle tapes. They seem to have implemented tape handling as an afterthought. > and then hardware compatibility: > I shall probably have the following spec: > > PII 350 or 450 (if some spare cash is lying around!!!) > adaptec 2940 UW SCSI controller > 9 Gig Fast wide SCSI Hard drive > 100 Mb/s 3com network card > S3 Virge Graphics card > Connected to an optic line via a 3com router Looks fine. > I'm really sorry this post is so long. Well, not really. It's less than one page. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 16 05:15:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA18445 for freebsd-hardware-outgoing; Fri, 16 Oct 1998 05:15:49 -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 FAA18439 for ; Fri, 16 Oct 1998 05:15:46 -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 IAA05507; Fri, 16 Oct 1998 08:15:09 -0400 Date: Fri, 16 Oct 1998 08:15:09 -0400 (EDT) From: Jamie Bowden To: John Polstra cc: spork@super-g.com, hardware@FreeBSD.ORG Subject: Re: IBM DDRS-39130 drive In-Reply-To: <199810160432.VAA09147@austin.polstra.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 Thu, 15 Oct 1998, John Polstra wrote: > I have three of the 34560W drives in a machine here, and they're > dynamite. Check it out: > > vashon$ dd if=/dev/rda2 of=/dev/null bs=64k count=1000 > 1000+0 records in > 1000+0 records out > 65536000 bytes transferred in 4.927831 secs (13299157 bytes/sec) > > The drives are reasonably quiet and run cool. I have one of these as well. Beautiful drive. Runs quieter and cooler than either of my Western Digital IDE drives. John, just out of curiousity, what are yours plugged in to? I have an Adaptec 2940UW, and bonnie is only reporting about 4MB/s throughput for me. I do have scb paging and tagenable in the kernel. 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 Oct 16 07:47:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06464 for freebsd-hardware-outgoing; Fri, 16 Oct 1998 07:47:32 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from datacompusa.com (grand-rapids-252-235.iserv.net [208.224.11.235]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06457 for ; Fri, 16 Oct 1998 07:47:24 -0700 (PDT) (envelope-from msb@datacompusa.com) Received: from [192.168.1.100] (msb.datacompusa.com [192.168.1.100]) by datacompusa.com (8.8.7/8.8.7) with SMTP id KAA12216; Fri, 16 Oct 1998 10:47:32 -0400 (EDT) (envelope-from msb@datacompusa.com) Message-Id: <199810161447.KAA12216@datacompusa.com> Subject: Problem with Cyclades Cyclom-8Yep Date: Fri, 16 Oct 98 10:47:45 -0400 x-sender: msb@datacompusa.com. x-mailer: Claris Emailer 1.1 From: Michael Scott Boers To: cc: "Cyclades Support" Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am having trouble getting a Cyclades Cyclom-8YeP (PCI, 8 port) multiport serial card to work with my FreeBSD 2.2.7 machine. I would appreciate any help anyone can give me towards solving this problem. If anyone out there is using a Cyclom-8YeP card with 2.2.7, please let me know. Should I just give up and get the isa version instead? PROBLEM SUMMARY: During bootup, the kernel finds the card but reports no ports found. (Exerpt from boot sequence with the -v added) cy0 rev 1 int a irq 10 on pci0:9:0 mapreg[10] type=0 addr=ffadff80 size=0080. mapreg[14] type=1 addr=00007c80 size=0080. mapreg[18] type=1 addr=000dc000 size=3f80. cy_pci.c cy_attach config_id.cfg1 = 80004800 /*Added to peak at the values*/ cy_pci.c cy_attach unit = 0 /*Added to peak at the values*/ cy_pci.c cy_attach ioport = 7c80 /*Added to peak at the values*/ cy_pci.c cy_attach paddr = dc000 /*Added to peak at the values*/ cy_pci.c cy_attach vaddr = f4d3b000 /*Added to peak at the values*/ cy0: no ports found! So as you can see, the pci probe finds the card, but the attach sequence fails. I have already updated the i386/isa/cy.c and i386/isa/cyreg.h with the new version (1.41.3.1) from Cyclades. This has not helped. WHAT I HAVE TRIED: CYCTEST.EXE (from Cyclades) reports everything is fine. Output from CYCTEST: Device: 64 BusNumber: 0 Vendor ID: 120Eh Device ID: 0100h Class Code: 078000h Revision ID: 01h Interrupt Line: 9 Runtime Regs Addr: 00007C81h Base Address Reg: 000DC002h Firmware ID: 13 FirmWare Rev: 3 Number of Ports:8 ID Number: 9DA74502 EEPROM Version: 3 CD1400 #0: 48h CD1400 #1: 48h CD1400 #2: 00h CD1400 #3: 00h CD1400 #4: 00h CD1400 #5: 00h CD1400 #6: 00h CD1400 #7: 00h Changing the base address with CYCTEST (from Y < 1MB to Y > 1MB) doesn't help. Swaping the card with my Intel Pro 100 (which changes the assign IRQ) doesn't help. WHAT I HAVE LEARNED: First, I have learned that I my OS class in college didn't spend enough time on driver issues. Second, I thing that the problem is in cy_attach (from pci/cy_pci.c) and cyattach_common (i386/isa/cy.c). cy_attach retrieves the ioport and physical address from the pci datastructure. It then maps the physical address to a virtual address with the call pmap_mapdev(paddr, 0x4000). After this call, all 0x4000 bytes at 0xf4d3b000 are 0xff. I have looked at them with ddb during boot and with gdb -k afterword. They never change. So cy_attach passes the virtual address to cyattach_common which tries to get version numbers and stuff. Every query comes back 0xff and it finally gives up. Any suggestions, advice, or commiseration is very welcome. -- Michael Boers Datacomp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 16 08:53:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14721 for freebsd-hardware-outgoing; Fri, 16 Oct 1998 08:53:57 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14716 for ; Fri, 16 Oct 1998 08:53:55 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id IAA12745; Fri, 16 Oct 1998 08:53:12 -0700 (PDT) (envelope-from jdp) Message-Id: <199810161553.IAA12745@austin.polstra.com> To: Jamie Bowden cc: spork@super-g.com, hardware@FreeBSD.ORG Subject: Re: IBM DDRS-39130 drive In-reply-to: Your message of "Fri, 16 Oct 1998 08:15:09 EDT." Date: Fri, 16 Oct 1998 08:53:12 -0700 From: John Polstra Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > John, just out of curiousity, what are yours plugged in to? I > have an Adaptec 2940UW, and bonnie is only reporting about 4MB/s > throughput for me. I do have scb paging and tagenable in the > kernel. ahc0: rev 0x04 int a irq 10 on pci0.18.0 ahc0: Using left over BIOS settings ahc0: aic7895 Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: rev 0x04 int b irq 10 on pci0.18.1 ahc1: Using left over BIOS settings ahc1: aic7895 Wide Channel B, SCSI Id=7, 32/255 SCBs John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 16 09:59:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23277 for freebsd-hardware-outgoing; Fri, 16 Oct 1998 09:59:30 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23272 for ; Fri, 16 Oct 1998 09:59:28 -0700 (PDT) (envelope-from dglynn@vaview5.vavu.vt.edu) Received: from vaview5.vavu.vt.edu (vaview5.vavu.vt.edu [198.82.158.16]) by vaview5.vavu.vt.edu (8.8.8/8.8.7) with SMTP id MAA06196 for ; Fri, 16 Oct 1998 12:59:08 -0400 (EDT) (envelope-from dglynn@vaview5.vavu.vt.edu) Date: Fri, 16 Oct 1998 12:59:08 -0400 (EDT) From: Greg Lynn To: freebsd-hardware@FreeBSD.ORG Subject: Iomega JAZ 1G Tape... 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 Does anyone out there know what it takes to enable a Jaz tape drive on 2.2.7? Is it simply a matter of specifying the type in mount and/or should the kernel have a line of info. Kernel output goes like this: (ahc0:5:0): "iomega jaz 1GB J.83" type 0 removable SCSI 2 sd2(ahc0:5:0): Direct-Access sd2(ahc0:5:0): NOT READY asc:3a,0 Medium not present sd2: could not get size sd2(ahc0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd2 could not mode sense (4). Using fictitious geometry But that's WITHOUT a cartridge in the drive. Can you mount this puppy after boot? -Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 16 11:34:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12679 for freebsd-hardware-outgoing; Fri, 16 Oct 1998 11:34:27 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12674 for ; Fri, 16 Oct 1998 11:34:23 -0700 (PDT) (envelope-from patl@phoenix.volant.org) From: patl@phoenix.volant.org Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with smtp (Exim 1.92 #8) id 0zUEhM-00072Y-00; Fri, 16 Oct 1998 11:34:00 -0700 Received: from localhost by asimov.phoenix.volant.org (SMI-8.6/SMI-SVR4) id LAA00930; Fri, 16 Oct 1998 11:33:52 -0700 Date: Fri, 16 Oct 1998 11:33:52 -0700 (PDT) Reply-To: patl@phoenix.volant.org Subject: Re: Iomega JAZ 1G Tape... To: Greg Lynn cc: freebsd-hardware@FreeBSD.ORG In-Reply-To: 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 > Does anyone out there know what it takes to enable a Jaz > tape drive on 2.2.7? Is it simply a matter of specifying the > type in mount and/or should the kernel have a line of info. It's not a tape, it's a disk. It mounts like any other disk. > Kernel output goes like this: > > (ahc0:5:0): "iomega jaz 1GB J.83" type 0 removable SCSI 2 > sd2(ahc0:5:0): Direct-Access > sd2(ahc0:5:0): NOT READY asc:3a,0 Medium not present > sd2: could not get size > sd2(ahc0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB > sd2 could not mode sense (4). Using fictitious geometry > > But that's WITHOUT a cartridge in the drive. Can you mount this > puppy after boot? Yep. If you have a cartridge in at boot time, it will be able to get the geometry info from it; which is convienient if you haven't partitioned, labeled, and newfsed it yet. -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 16 12:18:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19662 for freebsd-hardware-outgoing; Fri, 16 Oct 1998 12:18:13 -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 MAA19566 for ; Fri, 16 Oct 1998 12:18:07 -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 PAA24120; Fri, 16 Oct 1998 15:16:00 -0400 (EDT) Date: Fri, 16 Oct 1998 15:16:00 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: John Polstra cc: hardware@FreeBSD.ORG Subject: Re: IBM DDRS-39130 drive In-Reply-To: <199810160432.VAA09147@austin.polstra.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 Thanks for all the input, folks... Searching dejanews I've yet to find any negative comments on this or other IBM drives, so I think I'll go ahead and take the plunge... Hopefully they get along with the CMD controller. Thanks, Charles --- Charles Sprickman spork@super-g.com On Thu, 15 Oct 1998, John Polstra wrote: > In article , > spork wrote: > > Hi, > > > > Just a quick check on everyone's opinion of the IBM DDRS-39130 4G U/W > > drive. > > I believe that model number is for the 9.1 GB drive. The 4.5 GB drive > is DDRS-34560W. > > I have three of the 34560W drives in a machine here, and they're > dynamite. Check it out: > > vashon$ dd if=/dev/rda2 of=/dev/null bs=64k count=1000 > 1000+0 records in > 1000+0 records out > 65536000 bytes transferred in 4.927831 secs (13299157 bytes/sec) > > The drives are reasonably quiet and run cool. > > When I received the drives, one of them had zillions of bad blocks. I > had to exchange it under warranty. However, I'm convinced that it had > gotten damaged during shipment. (The vendor said he tested the system > before shipping it, and it was fine at that point.) Since getting the > replacement drive, I haven't seen any anomalies with these drives at > all. > > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-knowledge is always bad news." -- John Barth > > 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 Fri Oct 16 12:27:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21940 for freebsd-hardware-outgoing; Fri, 16 Oct 1998 12:27:52 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from azazel.async.org (hun-al1-02.ix.netcom.com [205.184.6.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21924 for ; Fri, 16 Oct 1998 12:27:47 -0700 (PDT) (envelope-from ysyi@async.org) Received: from localhost (ysyi@localhost) by azazel.async.org (8.9.1a/8.9.1a) with SMTP id OAA26403; Fri, 16 Oct 1998 14:26:21 -0500 Date: Fri, 16 Oct 1998 14:26:21 -0500 (CDT) From: "Yong S. Yi" To: Greg Lynn cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Iomega JAZ 1G Tape... In-Reply-To: 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, 16 Oct 1998, Greg Lynn wrote: >Date: Fri, 16 Oct 1998 12:59:08 -0400 (EDT) >From: Greg Lynn >To: freebsd-hardware@FreeBSD.ORG >Subject: Iomega JAZ 1G Tape... > >Does anyone out there know what it takes to enable a Jaz >tape drive on 2.2.7? Is it simply a matter of specifying the Well, I don't know if this was just a simple mistake, or what, but the Jaz is *not* a tape -- it is a disk. (Unless Iomega labeled one of their tape drives as 'Jaz' lately...) >type in mount and/or should the kernel have a line of info. Yes, it should work like any SCSI disk. >But that's WITHOUT a cartridge in the drive. Can you mount this >puppy after boot? Yup, but make sure to insert a cartridge, though :) > >-Greg -- Yong S. Yi Email: ysyi@async.org Phone: 1.256.881.8821 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Oct 17 01:29:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA14378 for freebsd-hardware-outgoing; Sat, 17 Oct 1998 01:29:05 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA14373 for ; Sat, 17 Oct 1998 01:29:01 -0700 (PDT) (envelope-from ab@paert.tse-online.de) Received: (qmail 24801 invoked by uid 1000); 17 Oct 1998 08:37:34 -0000 Message-ID: <19981017103734.L10960@paert.tse-online.de> Date: Sat, 17 Oct 1998 10:37:34 +0200 From: Andreas Braukmann To: hardware@FreeBSD.ORG Subject: Re: IBM DDRS-39130 drive Mail-Followup-To: hardware@FreeBSD.ORG References: <199810160432.VAA09147@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: ; from spork on Fri, Oct 16, 1998 at 03:16:00PM -0400 Organization: TSE TeleService GmbH Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, On Fri, Oct 16, 1998 at 03:16:00PM -0400, spork wrote: > Searching dejanews I've yet to find any negative comments on this > or other IBM drives, I'm hoping you won't find any, because our boxes are completely stuffed with IBM drives. (mainly DCAS 4.3 GB and this exactly DDRS 9 GB drive) > Hopefully they get along with the CMD controller. They do so far with our CMD 5440. I don't have really valuable results wether regarding 'real RAID'- benchmarks nor real stresstests. But nonetheless: The machine: Dual PPro 166/512, Intel-Board PR440FX, 256 MB RAM running 3.0-pretty-current-with-cam SCSI-Host: onboard Adaptec 7880 UW RAID: CMD 5440 with 64 MB Cache (4 SCSI-Channels) 5 x IBM DDRS-39130W S92A across 2 drive-channels as an RAID-5 raid-set. The set is divided into two redundancy sets (each ca. 17 GB) (two ca. 9GB filesystems on each) The bonnies: First, a single bonnie on the first red.-set's first filesystem: >haendel# bonnie -s 1024 -d . >File './Bonnie.360', size: 1073741824 >Seeker 1...Seeker 2...Seeker 3...start 'em...done...done...done... > -------Sequential Output-------- ---Sequential Input-- --Random-- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- >Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU > 1024 10397 97.9 9172 39.1 3857 20.3 5243 57.0 6025 20.1 147.7 6.0 Then, three bonnies (one GByte each) in parallel; two of them on the same filesystem as the first test and the third on the first filesystem of the second redundancy-set. (hmm, they're ponding on the same drives anyways, but I suppose that the drives have to seek a heck more ...) The three runs are overlapping a little bit (easy to recognize by a look at the seek-results), because I just startet them by hitting return in three shell-windows. > -------Sequential Output-------- ---Sequential Input-- --Random-- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- >Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU >1-of-3 1024 5510 59.2 6099 29.8 1606 11.3 1731 20.4 2562 9.9 76.2 3.3 >2-of-3 1024 5451 58.5 5887 28.2 1380 9.8 2219 26.0 2581 10.0 74.7 3.4 >3-of-3 1024 6672 69.2 5538 23.4 1506 10.9 2449 28.3 2923 10.6 150.3 6.2 >'sum' 17633 17524 4492 6449 8066 Ahh. The stripe-size is 128 kByte (from memory). The server provides file- and compute-services for our web-developers. A definately backdraw of the CMD-controllers is, that they only accept as few as 32 (sic!) tagged commands. That was really bad news for me, I wasn't able to extract this from the technical docs or any sales- / tech- representive. After switching to CAM, I noted the cam-console-message > (da2:ahc0:0:14:0): tagged openings now 32 Shortly after that David Greenman stated in a discussion regarding the selection of an RAID-controller for ftp.cdrom.com: DG> I had, too, chosen the CMD until I found out that it only supports 32 DB> tagged commands total. Maximally configured (45 drives), this means that DB> not only would the CMD controller be unable to queue more than one command DB> per disk, but in fact 1/3 of the disk drives would be completely idle at DB> any given time. hmmm. Since the load on our server will surely be not in class of 'ftp.cdrom.com' I currently suppose, that I can live with that. -ab -- /// TSE TeleService GmbH | Gsf: Arne Reuter | /// Hovestrasse 14 | Andreas Braukmann | We do it with /// D-48351 Everswinkel | HRB: 1430, AG WAF | FreeBSD/SMP /// ------------------------------------------------------------------- /// PGP-Key: http://www.tse-online.de/~ab/public-key /// Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Oct 17 08:33:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23367 for freebsd-hardware-outgoing; Sat, 17 Oct 1998 08:33:43 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23346; Sat, 17 Oct 1998 08:33:39 -0700 (PDT) (envelope-from roger@cs.strath.ac.uk) Received: from cs.strath.ac.uk (posh.dmem.strath.ac.uk [130.159.202.3]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with ESMTP id QAA01410 Sat, 17 Oct 1998 16:33:16 +0100 (BST) Message-ID: <3628B8B8.BDAA6939@cs.strath.ac.uk> Date: Sat, 17 Oct 1998 16:33:12 +0100 From: Roger Hardiman Organization: Strathclyde Uni X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-980520-SNAP i386) MIME-Version: 1.0 To: hardware@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Realtek 8029 goes slow. 200k/second. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Recently I posted this problem. I have a solution which I am posting for future reference. > I have a couple of PCI network cards with the Realtek 8029 chip. > (a no-name and a Genuis) > > Both these cards give 1000k / sec on all of my FreeBSD machines except > my new one. > > My new PII400 (BX chipset) gives just 200k / second on our lab network. > Perfect test conditions - no other network traffic. The test I was performing was to FTP a gzipped file from our server to my new PC. The Realtek 8029 is a PCI card and I am using an IDE hard drive (just the BX chipset's controller) In my kernerl config settings I changed the IDE controller to enable 32bit transfers with maximum sector transfers So, I changed controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr to this controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x80ff80ff vector wdintr And now I can FTP files from our server at 1000k/second. I connected an ethernet load monitor (on a 3com hub) and noticed the PC was downloading a burst of data and then waiting before downloading the next burst. The PC was downloading data and then spending a long time writing to the disk and then fetching more data. Bye Roger Hardiman Strathclyde University Telepresence Research Group To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Oct 17 09:11:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27569 for freebsd-hardware-outgoing; Sat, 17 Oct 1998 09:11:20 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA27563; Sat, 17 Oct 1998 09:11:12 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id MAA20232; Sat, 17 Oct 1998 12:16:06 -0400 From: Bill Paul Message-Id: <199810171616.MAA20232@skynet.ctr.columbia.edu> Subject: 2nd call for testers for PNIC driver To: hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Date: Sat, 17 Oct 1998 12:16:04 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a second call for testers for the Lite-On PNIC driver (if_pn). My first call resulted in a couple of respondes, most of which were in the form of "I'll have one of these boards to try soon and I'll get back to you" and only one of which was of the form "I tried it and here's what happened." (And special thanks to Mark Tinguely for being that one.) Here's what's changed since the first announcement: - Fixed the programming of the multicast filter in the 2.2.x version of if_pn.c. When I converted the 3.0 driver to 2.2.x, I left out a few things from pn_ioctl(). - Rearranged the interrupt handling and transmission a bit to avoid some possible infinite loop conditions where the interrupt handlers would do the wrong thing and retrigger interrupts over and over again. - Turned off store and forward mode and instead set the tx threshold to 72 bytes. This improves performance quite a bit at 100Mbps. I still don't have my regular test machines back (hopefully I will on Monday) but in the meantime I've kludged together another testbed. Transmit performance with the PNIC seems a little slow: with other NICs like the ThunderLAN and the 3Com 3c905/3c905B, I could get data rates of 11.3MB/sec to 11.4MB/sec using ttcp. Heck, even the RealTek would do 11MB/sec. The PNIC seems to be barely able to reach 10MB/sec if you push it really hard on a fast machine. The main test machine I'm using now is a Dell PowerEdge 2300/400 SMP system with dual PII 400Mhz CPUs and 256MB RAM (with a CAM binary snapshot release from a couple months ago). Using Lose NT Server with service pack 1 and the LinkSys drivers that came with my test card, I can get about 8.5MB/sec over FTP. My driver with an SMP kernel achieves pretty much the same performance. One thing that's a little strange is that if I run a uniprocessor kernel on the same hardware, transmit performance increases a bit from 8.5MB/sec to 10MB/sec. As an aside, I spoke with Greg LaPolla from LinkSys on the phone earlier this week and learned that when LinkSys first approached Lite-On about using their PNIC chips on LinkSys adapters, LinkSys insisted that they would only deal with Lite-On if the PNIC were made available without NDA for the benefit of free OS programmers/users or else they would get up and walk right out the door. He implied that the PNIC engineers were opposed to this but Lite-On eventually gave in. Greg has also told me there will be an official link from the LinkSys web server to www.freebsd.org pointing to the FreeBSD driver once it's ready for prime time, so everybody get your acts in gear and help me test this sucker. There is already an unannounced FreeBSD page at http://www.linksys.com/support/solution/nos/freebsd.htm. So anyway, go to http://www.freebsd.org/~wpaul/PNIC and read the instructions about how to install the PNIC driver. The source is at: http://www.freebsd.org/~wpaul/PNIC/3.0 source for FreeBSD 3.0 http://www.freebsd.org/~wpaul/PNIC/2.2 source for FreeBSD 2.2.x So far, I've learned from Mark that he has one pathological P90 system with a Neptune chipset and a NetGear FA310TX D1 card which locks up periodically, however I have been unable to reproduce his problems on my machines and he says the card and driver seem to work okay on other systems that he's tried. I've also received one problem report that was resolved by putting the card in a different PCI slot: please make sure that you put the LinkSys adapter in a bus master PCI slot when you install it. Note that this driver still does not support the PNIC's internal transceiver since I don't have a card that uses the internal transceiver for testing. The LinkSys, NetGear, Matrox and I think D-Link adapters that use the PNIC all use external PHYs through the MII bus, so for current cards this is not a problem. I did some more testing with the transmit list base address register (CSR4) and am convinced that the chip is broken in that after setting CSR4 the first time after a software reset, trying to change it later doesn't work. The driver still uses the 'kludge descriptor' workaround for this problem. I spoke with Lite-On engineers about this at the same time I spoke with Greg, however I haven't gotten a conclusive answer back yet as to whether this is really a chip errata or stupidity on my part. Never having programmed a real tulip chip before, it may very well be that this is intended behavior. (Though if it is intended behavior, it's really stupid intended behavior.) On a separate note, I am still looking for a vendor for cards that use the Winbond WB89C840F chip so that I can complete my Winbond driver. If anybody knows where I can order a board with one of these chips, please e-mail me. Note: that's _840_ not _940_. The 940 is a 10Mbps-only NE2000 clone. The 840 is a dumbed-down 10/100Mbps tulip clone. On another separate note, I'm planning to import the RealTek driver into FreeBSD-current soon now that 3.0 is going out the door. So far I've only gotten a couple of reports about this driver but they've been positive. I've learned of quite a few cheap cards that use the RealTek 8139 chip. Go to http://www.freebsd.org/~wpaul/RealTek if you have one of these and want to be a tester. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Oct 17 09:30:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29113 for freebsd-hardware-outgoing; Sat, 17 Oct 1998 09:30:19 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29079; Sat, 17 Oct 1998 09:30:07 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id CAA32472; Sun, 18 Oct 1998 02:29:44 +1000 Date: Sun, 18 Oct 1998 02:29:44 +1000 From: Bruce Evans Message-Id: <199810171629.CAA32472@godzilla.zeta.org.au> To: hardware@FreeBSD.ORG, questions@FreeBSD.ORG, roger@cs.strath.ac.uk Subject: Re: Realtek 8029 goes slow. 200k/second. Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >In my kernerl config settings I changed the IDE controller to enable >32bit transfers >with maximum sector transfers > >So, I changed > controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr > >to this > controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x80ff80ff >vector wdintr > > >And now I can FTP files from our server at 1000k/second. Try using DMA mode (flags 0x20002000). The best case for PIO mode (16MB/sec) can barely keep up with a current fast IDE disk (14MB/sec?), and since the CPU is doing the tranfer, this matters more than when a busmastering SCSI controller can't keep up. With 16-bit transfers, the best case for PIO mode is 8MB/sec, so it couldn't even keep up with yesterday's fast IDE disk (10MB/sec). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Oct 17 10:29:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05088 for freebsd-hardware-outgoing; Sat, 17 Oct 1998 10:29:59 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA05061 for ; Sat, 17 Oct 1998 10:29:47 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 19377 invoked by uid 1001); 17 Oct 1998 17:29:25 +0000 (GMT) To: wpaul@skynet.ctr.columbia.edu Cc: hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: 2nd call for testers for PNIC driver In-Reply-To: Your message of "Sat, 17 Oct 1998 12:16:04 -0400 (EDT)" References: <199810171616.MAA20232@skynet.ctr.columbia.edu> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 17 Oct 1998 19:29:25 +0200 Message-ID: <19375.908645365@verdi.nethelp.no> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I still don't have my regular test machines back (hopefully I will on > Monday) but in the meantime I've kludged together another testbed. > Transmit performance with the PNIC seems a little slow: with other > NICs like the ThunderLAN and the 3Com 3c905/3c905B, I could get > data rates of 11.3MB/sec to 11.4MB/sec using ttcp. Unrelated to testing of the PNIC driver, but: A *big* thanks to Bill Paul for the Thunderlan driver. We're using it with 2.2.7 on a big Compaq server here, and it's been rock solid so far, handling large volumes of traffic. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Oct 17 12:22:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13289 for freebsd-hardware-outgoing; Sat, 17 Oct 1998 12:22:12 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from seagull.rtd.com (seagull.rtd.com [198.102.68.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13224 for ; Sat, 17 Oct 1998 12:22:04 -0700 (PDT) (envelope-from tony@rtd.com) Received: (from tony@localhost) by seagull.rtd.com (8.8.5/8.8.5) id MAA02566 for freebsd-hardware@freebsd.org; Sat, 17 Oct 1998 12:21:42 -0700 (MST) Date: Sat, 17 Oct 1998 12:21:42 -0700 (MST) From: Tony Jones Message-Id: <199810171921.MAA02566@seagull.rtd.com> To: freebsd-hardware@FreeBSD.ORG Subject: FreeBSD system advice (overclocked Celeron?) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi It's been a few years since I last put together a FreeBSD system (P90 with 32MB ($1000+) of RAM). A bunch of my coworkers all have home NT systems using Celeron's overclocked to 450/500mhz, most are using the Abit BX6 and BH6. I'll be doing some NT work at home, but will also still want it to run FreeBSD. What are peoples views on the following: Abit BH6 motherboard Intel Celeron 300A overclocked to 450mhz 128MB of RAM Matrox G200 AGP video (seems to have provisional XFree86 support) Adaptec AHA-2940UW SCSI Card My current system uses an ASUS motherboard, and I've been very happy with them, but from what I've read the Abit (with it's software selectable bus speed and voltages) will be a lot easier to work with ? Also, what are peoples recommendations in the 19/21" monitor front ? Thanks Tony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message