From owner-freebsd-hardware Sun Jul 11 2:32:36 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (Postfix) with ESMTP id 3889214C01 for ; Sun, 11 Jul 1999 02:32:32 -0700 (PDT) (envelope-from sanpei@sanpei.org) Received: from lavender.sanpei.org (u4161.seaple.icc.ne.jp [210.170.12.161]) by titanium.yy.ics.keio.ac.jp (8.8.8+3.0Wbeta13/3.7W) with ESMTP id SAA28749; Sun, 11 Jul 1999 18:32:24 +0900 (JST) Received: (from sanpei@localhost) by lavender.sanpei.org (8.9.3/3.7W) id SAA01963; Sun, 11 Jul 1999 18:32:19 +0900 (JST) Date: Sun, 11 Jul 1999 18:32:19 +0900 (JST) Message-Id: <199907110932.SAA01963@lavender.sanpei.org> To: gabriel@maquina.com Cc: repenting@hotmail.com, freebsd-hardware@FreeBSD.ORG Subject: Re: Would anyone like to start a FreeBSD irda project? In-Reply-To: Your message of "Thu, 8 Jul 1999 11:33:13 JST". From: sanpei@sanpei.org (MIHIRA Yoshiro) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org gabriel@maquina.com Wrote: >> > I have finally figured out where my IR device is located in my >> > Toshiba Satellite 315CDS and was wondering if anyone would like to >> > start a project to add support for IR devices? >> >> Yes, I'm very interested in a FreeBSD IrDA project. I've also met >> Daniel J. O'Connor at the linux-irda list who also >> seems very interested in doing things. <> >> Daniel is now gone for a two weeks holiday, however we will start work >> when he gets back. We're planning on a user lever implementation first. That's great!!! I can join alpha/beta test. I hope to announce some information about IrDA project to hackers or hardware mailing list. In Japan, some public telephone have IrDA port. I want to use IrCOMM with FreeBSD. (Windows and Linux support IrCOMM and I think they can use public telephone without PC-Card modem) Cheers MIHIRA Sanpei Yoshiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jul 11 5:44:55 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id B966E14D25 for ; Sun, 11 Jul 1999 05:44:52 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-153.skylink.it [194.185.55.153]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id OAA29153; Sun, 11 Jul 1999 14:44:20 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id OAA00312; Sun, 11 Jul 1999 14:36:33 +0200 (CEST) Date: Sun, 11 Jul 1999 14:36:33 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Francisco Reyes Cc: "freebsd-hardware@freebsd.org" Subject: Re: Solved (was SMC EZcard or Linksys ethernet?) In-Reply-To: <199907100406.AAA07723@arutam.inch.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 > >> ed0 not found at 0x280 > >> I made the cards 280H, IRQ 5 and made sure that FreeBSD was looking for > >> them. > > I didn't have DOS on the FreeBSD machine and was configuring the cards > in a separate computer. Someone suggested that I use a boot floopy and > configure the cards in the FreeBSD box. As soon as I ran the card > configuration it complained about a conflict at 280H and made the > address 220. I changed FreeBSD to look for the card there and it > worked. Did you manage to figure out what was on 280H? ComX? Sometimes the ComX ports are very possessive and claim the port even when they are not switched on. Nick -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jul 11 6: 9:52 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from hotmail.com (f124.law3.hotmail.com [209.185.241.124]) by hub.freebsd.org (Postfix) with SMTP id 419A614D98 for ; Sun, 11 Jul 1999 06:09:51 -0700 (PDT) (envelope-from repenting@hotmail.com) Received: (qmail 60341 invoked by uid 0); 11 Jul 1999 13:09:50 -0000 Message-ID: <19990711130950.60340.qmail@hotmail.com> Received: from 209.57.150.66 by www.hotmail.com with HTTP; Sun, 11 Jul 1999 06:09:50 PDT X-Originating-IP: [209.57.150.66] From: "Mike Del" To: sanpei@sanpei.org, gabriel@maquina.com Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Would anyone like to start a FreeBSD irda project? Date: Sun, 11 Jul 1999 13:09:50 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > That's great!!! I can join alpha/beta test. I hope to announce some >information about IrDA project to hackers or hardware mailing list. > > In Japan, some public telephone have IrDA port. I want to use >IrCOMM with FreeBSD. (Windows and Linux support IrCOMM and I think >they can use public telephone without PC-Card modem) > >Cheers >MIHIRA Sanpei Yoshiro GOOD! The more people we have the better chance we have of doing this project! But I need to send this message out because I really don't know anything about coding device drivers. And the Device Driver Tutorial on www.freebsd.org was not much help. I think a lot of IR devices in notebooks are on the PCI bus (that is where my IR device is located). But when the kernel finds it on boot, of course is cannot assign a driver to it because it doesn't exist. It does tell me that the (pci class = comms) how does one code a class=comms? is this anything like serial? In the /usr/src/sys/pci/ there is some code cy_* (sorry I forget right now) but this code is for handling some pci serial hardware? Would this be of any help, for example code? Please send all idea,etc. Thanks, Mike _______________________________________________________________ Get Free Email and Do More On The Web. Visit http://www.msn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jul 11 11:11:21 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.eclipse.net (mail.eclipse.net [207.207.192.13]) by hub.freebsd.org (Postfix) with ESMTP id 0CED914BD6; Sun, 11 Jul 1999 11:11:18 -0700 (PDT) (envelope-from johnc@geekopolis.com) Received: from ibe-cam (ibe-cam.ibetechgrp.com [207.207.207.75]) by mail.eclipse.net (8.9.1a/8.9.1) with SMTP id OAA15020; Sun, 11 Jul 1999 14:11:18 -0400 (EDT) From: "John T. Croteau" To: , Subject: I2O Date: Sun, 11 Jul 1999 14:06:55 -0400 Message-ID: <000401becbc8$28dbbe20$4bcfcfcf@ibe-cam.ibetechgrp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is anyone working on, or at least looking at, I2O (http://www.i2osig.com) support for FreeBSD? - JT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jul 11 14:37:39 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with SMTP id 3A1FB14CA7; Sun, 11 Jul 1999 14:37:34 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40323>; Mon, 12 Jul 1999 07:18:36 +1000 Date: Mon, 12 Jul 1999 07:36:33 +1000 From: Peter Jeremy Subject: Re: I2O In-reply-to: <000401becbc8$28dbbe20$4bcfcfcf@ibe-cam.ibetechgrp.com> To: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, johnc@geekopolis.com Message-Id: <99Jul12.071836est.40323@border.alcanet.com.au> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "John T. Croteau" wrote: >Is anyone working on, or at least looking at, I2O (http://www.i2osig.com) >support for FreeBSD? Last I heard, the I2O standard was not open - it was available only under NDA and/or in exchange for a bucketload of money. Unless this has changed recently, just cross any I2O motherboards off your shopping list. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jul 11 14:46:34 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5FC9F14F87; Sun, 11 Jul 1999 14:46:32 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id OAA31935; Sun, 11 Jul 1999 14:45:27 -0700 Date: Sun, 11 Jul 1999 14:45:26 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Peter Jeremy Cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, johnc@geekopolis.com Subject: Re: I2O In-Reply-To: <99Jul12.071836est.40323@border.alcanet.com.au> 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 > >Is anyone working on, or at least looking at, I2O (http://www.i2osig.com) > >support for FreeBSD? > > Last I heard, the I2O standard was not open - it was available only > under NDA and/or in exchange for a bucketload of money. > > Unless this has changed recently, just cross any I2O motherboards off > your shopping list. > NO need to be so draconian. I have several I2O motherboards running FreeBSD. It's just not entirely clear how to use the features. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jul 11 15:39: 1 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id AD4A314DD1; Sun, 11 Jul 1999 15:38:57 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40359>; Mon, 12 Jul 1999 08:20:54 +1000 Date: Mon, 12 Jul 1999 08:38:48 +1000 From: Peter Jeremy Subject: Re: I2O In-reply-to: To: mjacob@feral.com Cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Message-Id: <99Jul12.082054est.40359@border.alcanet.com.au> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote: >> Unless this has changed recently, just cross any I2O motherboards off >> your shopping list. > >NO need to be so draconian. I have several I2O motherboards running >FreeBSD. It's just not entirely clear how to use the features. My statement was derived from "don't support vendors who push proprietary solutions", rather than any technical issues. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jul 11 15:48:38 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8A74E14DD1; Sun, 11 Jul 1999 15:48:35 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id PAA32099; Sun, 11 Jul 1999 15:48:30 -0700 Date: Sun, 11 Jul 1999 15:48:29 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Peter Jeremy Cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: I2O In-Reply-To: <99Jul12.082054est.40359@border.alcanet.com.au> 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 > >> Unless this has changed recently, just cross any I2O motherboards off > >> your shopping list. > > > >NO need to be so draconian. I have several I2O motherboards running > >FreeBSD. It's just not entirely clear how to use the features. > > My statement was derived from "don't support vendors who push > proprietary solutions", rather than any technical issues. Then take the discussion to freebsd-advocacy. Not that I don't agree in some ways, but this isn't the forum for it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 12 0:56:32 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (Postfix) with ESMTP id 408F31531A for ; Mon, 12 Jul 1999 00:56:26 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.3/8.9.3/Kp) with ESMTP id HAA58271; Mon, 12 Jul 1999 07:56:12 GMT Message-ID: <37899F82.74969DBA@tdx.co.uk> Date: Mon, 12 Jul 1999 08:55:46 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Andrew MacIntyre Cc: Joey Garcia , hardware@FreeBSD.ORG Subject: Re: PCI and/or BIOS problems on Asus and FIC motherboards References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew MacIntyre wrote: > Make sure that the BIOS is configured for "non-PnP OS". My personal > experience is that Win95 (no experience with Win98 yet) PnP is itself > quirky, and is quite capable of screwing up a previously working config at > the drop of a hat. Setting the BIOS for "non-PnP OS" means that all PnP > settings are established by the BIOS, and those that can logically > controlled (ie ISA IRQs etc) can be hardwired in the BIOS. Tell me about it! - My machine (for no apparent reason) just decided to move _all_ the PCI cards to IRQ #10. Interrupt sharing doesn't work reliably on PCI across so many different cards (theres 5 in there + 1 AGP, which is also, you guessed! - on IRQ #10), and the machines running really slowly... Can anyone here point to any good reference docs that might help unravel the PCI 'mystery' as to how the BIOS assigns IRQ's, and the mappings between normal PC IRQ's and PCI 'INT A/B/C/D' IRQ's etc? Or even better - any utilities that might actually help pursuade the machine to move the cards to better IRQ'S? (like _different_ IRQ's?). The only way I can get this resolved is to remove the covers (not easy/nice) and play 'musical PCI cards' - i.e. slot swapping). Even then the results are less than predictable, and _extreemly_ annoying :( - In fact I spent the whole of yesterday doing it, only to find today that the stupid BIOS has moved everything back to IRQ #10 :( -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 12 1: 8:41 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id E27A714F6B; Mon, 12 Jul 1999 01:08:31 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA31650; Mon, 12 Jul 1999 09:09:11 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 12 Jul 1999 09:09:11 +0100 (BST) From: Doug Rabson To: Peter Jeremy Cc: freebsd-hardware@freebsd.org, freebsd-scsi@freebsd.org, johnc@geekopolis.com Subject: Re: I2O In-Reply-To: <99Jul12.071836est.40323@border.alcanet.com.au> 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 Jul 1999, Peter Jeremy wrote: > "John T. Croteau" wrote: > >Is anyone working on, or at least looking at, I2O (http://www.i2osig.com) > >support for FreeBSD? > > Last I heard, the I2O standard was not open - it was available only > under NDA and/or in exchange for a bucketload of money. > > Unless this has changed recently, just cross any I2O motherboards off > your shopping list. I thought the Linux folks were working on drivers. I seem to remember Alan Cox (the other one) working on I2O drivers fairly recently. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 12 1:35:15 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 56A0B14C35; Mon, 12 Jul 1999 01:35:11 -0700 (PDT) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id DAA10970; Mon, 12 Jul 1999 03:35:00 -0500 (CDT) Date: Mon, 12 Jul 1999 03:35:00 -0500 From: Tim Tsai To: Doug Rabson Cc: Peter Jeremy , freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, johnc@geekopolis.com Subject: Re: I2O Message-ID: <19990712033459.A10956@futuresouth.com> References: <99Jul12.071836est.40323@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Doug Rabson on Mon, Jul 12, 1999 at 09:09:11AM +0100 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I asked about this recently. I believe Simon Shapiro is working on I2O support for FreeBSD, in order to support DPT I2O drivers. Tim On Mon, Jul 12, 1999 at 09:09:11AM +0100, Doug Rabson wrote: > On Mon, 12 Jul 1999, Peter Jeremy wrote: > > > "John T. Croteau" wrote: > > >Is anyone working on, or at least looking at, I2O (http://www.i2osig.com) > > >support for FreeBSD? > > > > Last I heard, the I2O standard was not open - it was available only > > under NDA and/or in exchange for a bucketload of money. > > > > Unless this has changed recently, just cross any I2O motherboards off > > your shopping list. > > I thought the Linux folks were working on drivers. I seem to remember Alan > Cox (the other one) working on I2O drivers fairly recently. > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" 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 Mon Jul 12 1:54:33 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 624E714C25; Mon, 12 Jul 1999 01:54:19 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 4DDD281; Mon, 12 Jul 1999 16:52:59 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Tim Tsai Cc: Doug Rabson , Peter Jeremy , freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, johnc@geekopolis.com Subject: Re: I2O In-reply-to: Your message of "Mon, 12 Jul 1999 03:35:00 EST." <19990712033459.A10956@futuresouth.com> Date: Mon, 12 Jul 1999 16:52:59 +0800 From: Peter Wemm Message-Id: <19990712085259.4DDD281@overcee.netplex.com.au> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Tim Tsai wrote: > I asked about this recently. I believe Simon Shapiro is working on I2O > support for FreeBSD, in order to support DPT I2O drivers. > > Tim I was told that he was not only working on it, but had all but finished and had I2O disk support pretty much complete. The whole I2O concept doesn't fit within CAM as I understand it - all the scsi processing is offloaded. > On Mon, Jul 12, 1999 at 09:09:11AM +0100, Doug Rabson wrote: > > On Mon, 12 Jul 1999, Peter Jeremy wrote: > > > > > "John T. Croteau" wrote: > > > >Is anyone working on, or at least looking at, I2O (http://www.i2osig.com ) > > > >support for FreeBSD? > > > > > > Last I heard, the I2O standard was not open - it was available only > > > under NDA and/or in exchange for a bucketload of money. > > > > > > Unless this has changed recently, just cross any I2O motherboards off > > > your shopping list. > > > > I thought the Linux folks were working on drivers. I seem to remember Alan > > Cox (the other one) working on I2O drivers fairly recently. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 12 2:51:49 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from mauibuilt.com (mauibuilt.com [205.166.249.50]) by hub.freebsd.org (Postfix) with ESMTP id 47A7814C98; Mon, 12 Jul 1999 02:51:44 -0700 (PDT) (envelope-from puga@mauibuilt.com) Received: from mauibuilt.com (puga.mauibuilt.com [205.166.10.2]) by mauibuilt.com (8.8.8/8.8.7) with ESMTP id XAA06391; Sun, 11 Jul 1999 23:54:42 -1000 (HST) (envelope-from puga@mauibuilt.com) Message-ID: <378981EA.5CC31B1C@mauibuilt.com> Date: Sun, 11 Jul 1999 19:49:30 -1000 From: Richard Puga X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: WaveLAN problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a WaveLAN ISA adaptor. I am trying to run it in a machine equiped with an AMD K6-2 350 processor running at 66mhz bus speed. I am getting the following error while ifconfiging the card. ifconfig wl0 192.168.10.1 ifconfig: ioctl (SIOCAIFADDR): File exists cray100 /root 2% Jul 12 03:43:23 cray100 /kernel: wl0: diag() failed; status = 0, inw = 0, outw = e0a0 Jul 12 03:43:23 cray100 /kernel: wl0: diag() failed; status = 0, inw = 0, outw = e0a0 Jul 12 03:43:23 cray100 /kernel: scb_status a000 Jul 12 03:43:23 cray100 /kernel: scb_status a000 Jul 12 03:43:23 cray100 /kernel: scb_command 0 Jul 12 03:43:23 cray100 /kernel: scb_command 0 Jul 12 03:43:23 cray100 /kernel: scb_cbl ffc0 Jul 12 03:43:23 cray100 /kernel: scb_cbl ffc0 Jul 12 03:43:23 cray100 /kernel: cu_cmd 8007 Jul 12 03:43:23 cray100 /kernel: cu_cmd 8007 Jul 12 03:43:23 cray100 /kernel: wl0 init(): trouble resetting board. Jul 12 03:43:23 cray100 /kernel: wl0 init(): trouble resetting board. I belive the issure is some kind of timeing problem because the dos drivers and ptpdiag work and the card works with freebsd in other machines. I have tried about everything I can think of I have set machdep.wl_xmit_delay: up and down as well as played with clock speeds of the CPU and motherboard as well as bios wait states, pnp settings ect. and differant wavelan cards. I even reset the factory setting off 0x300 irq 10 to other ones just to be sure.. I have tried the drivers in 3.0 3.1 and 4.0 current they all do the same thing.. thease are the current dmesg settings wl0 at 0x390-0x39f irq 5 on isa wl0: address 08:00:6a:2b:e3:30, NWID 0x5262, Freq 2422 MHz and the wlconfig info... cray100 /root 6% wlconfig wl0 Board type : ISA Base address options : 0x300, 0x390, 0x3c0, 0x3e0 Waitstates : 0 Bus mode : ISA IRQ : 5 Default MAC address : 08:00:6a:2b:e3:30 Soft MAC address : 00:00:00:00:00:00 Current MAC address : Default Adapter compatability : PCCARD or 1/2 size AT, 915MHz or 2.4GHz Threshold preset : 1 Call code required : NO Subband : 915MHz/see WaveModem Quality threshold : 3 Hardware version : 1 (Rel3) Network ID enable : YES NWID : 0x5262 Datalink security : NO Databus width : 16 (variable) Configuration state : unconfigured CRC-16 : 0xaba1 CRC status : OK If anyone can help in any way or point me to someone who might I would greatly apreciate it. Thanks in advance Richard Puga puga@mauibuilt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 12 17:44:28 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id B4EF714FD2; Mon, 12 Jul 1999 17:44:24 -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.3/8.8.8) with ESMTP id RAA02765; Mon, 12 Jul 1999 17:39:01 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907130039.RAA02765@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Jeremy Cc: mjacob@feral.com, freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: I2O In-reply-to: Your message of "Mon, 12 Jul 1999 08:38:48 +1000." <99Jul12.082054est.40359@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Jul 1999 17:39:01 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Matthew Jacob wrote: > >> Unless this has changed recently, just cross any I2O motherboards off > >> your shopping list. > > > >NO need to be so draconian. I have several I2O motherboards running > >FreeBSD. It's just not entirely clear how to use the features. > > My statement was derived from "don't support vendors who push > proprietary solutions", rather than any technical issues. The I2O spec has been open for several months now. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jul 12 18:20: 7 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 519E114CB1; Mon, 12 Jul 1999 18:19:57 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40585>; Tue, 13 Jul 1999 11:00:37 +1000 Date: Tue, 13 Jul 1999 11:18:33 +1000 From: Peter Jeremy Subject: Re: I2O In-reply-to: <199907130039.RAA02765@dingo.cdrom.com> To: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Message-Id: <99Jul13.110037est.40585@border.alcanet.com.au> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith wrote: >The I2O spec has been open for several months now. Excellent. In that case, I withdraw my previous comments. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 13 5:56:42 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from matrix.42.org (matrix.42.org [194.246.250.200]) by hub.freebsd.org (Postfix) with ESMTP id 2877015219 for ; Tue, 13 Jul 1999 05:56:36 -0700 (PDT) (envelope-from sec@42.org) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.5) id OAA08297 for freebsd-hardware@freebsd.org (sender ); Tue, 13 Jul 1999 14:55:06 +0200 (CEST) Date: Tue, 13 Jul 1999 14:55:05 +0200 From: Stefan `Sec` Zehl To: freebsd-hardware@freebsd.org Subject: Re: Would anyone like to start a FreeBSD irda project? Message-ID: <19990713145505.A7398@matrix.42.org> References: <19990708012651.66717.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Jose Gabriel Marcelino on Thu, Jul 08, 1999 at 03:33:13AM +0100 I-love-doing-this: really Accept-Languages: de, en X-URL: http://sec.42.org/ Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jul 08, 1999 at 03:33:13AM +0100, Jose Gabriel Marcelino wrote: > Hi, > > > I have finally figured out where my IR device is located in my > > Toshiba Satellite 315CDS and was wondering if anyone would like to > > start a project to add support for IR devices? > > Yes, I'm very interested in a FreeBSD IrDA project. I've also met > Daniel J. O'Connor at the linux-irda list who also > seems very interested in doing things. Count me in. I was planning to check how hard a minimal IRComm or IRObex implementation would be. It looks like the IR is treated like a normal COM1 and can talk raw IR with BSD already. So it might be possible to implement the rest in userland which would make debugging far easier. Did somebody start a mailinglist for coordinating, or should I ? CU, Sec -- See above, IŽd vote now to remove TCP completely after seeing that results. -- on freebsd-ports, 2.Aug.1997 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 13 5:57:44 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id D9E44152D5 for ; Tue, 13 Jul 1999 05:57:39 -0700 (PDT) (envelope-from R.Schofield@pbc.be.philips.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id OAA23555 for ; Tue, 13 Jul 1999 14:57:33 +0200 (MEST) (envelope-from R.Schofield@pbc.be.philips.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma023547; Tue, 13 Jul 99 14:57:33 +0200 Received: from bcs11.pbc.be.philips.com (bcs11.bcs.cs.philips.com [130.139.40.111]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id OAA25843 for ; Tue, 13 Jul 1999 14:57:32 +0200 (MET DST) Received: from exchvs01.bcs.cs.philips.com (exchvs01.bcs.cs.philips.com [130.139.40.10]) by bcs11.pbc.be.philips.com (8.6.10/8.6.10-1.2.1a-961023) with ESMTP id OAA18284 for ; Tue, 13 Jul 1999 14:52:23 +0200 Received: by exchvs01.bcs.cs.philips.com with Internet Mail Service (5.0.1460.8) id <3PH9RG3W>; Tue, 13 Jul 1999 14:55:49 +0200 Message-ID: <29F16C82368FD111914F00805F858E4F029DCF0F@exchvs01.bcs.cs.philips.com> From: "Schofield, Robert " To: "'freebsd-hardware@freebsd.org'" Subject: Audio chipset support Date: Tue, 13 Jul 1999 14:55:47 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1460.8) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can anyone tell me (rapidly) if ESS1868 and Cyrix CX5530 audio chipsets are supported under *any* version of FBSD? Thanks, Rob Schofield M.Sc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 13 11:35:22 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 7F17314F28 for ; Tue, 13 Jul 1999 11:35:17 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id LAA79674; Tue, 13 Jul 1999 11:34:53 -0700 (PDT) Date: Tue, 13 Jul 1999 11:34:52 -0700 (PDT) From: Julian Elischer To: "Schofield, Robert " Cc: "'freebsd-hardware@freebsd.org'" Subject: Re: Audio chipset support In-Reply-To: <29F16C82368FD111914F00805F858E4F029DCF0F@exchvs01.bcs.cs.philips.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org the Cx5530 doesn;t HAVE an audio chipset. rather, it emulates the audio chipset in software and passes teh data to a separate CODEC that is on the motherboard using a built in serial codec interface.. ( the emulation is done in the SMI layer so it's available to other OSs thane W98 but I don't know how they do it exactly as we didn't implement SMI in our BIOS) On Tue, 13 Jul 1999, Schofield, Robert wrote: > Can anyone tell me (rapidly) if ESS1868 and Cyrix CX5530 audio chipsets are > supported under *any* version of FBSD? > > Thanks, > > Rob Schofield M.Sc. > > > 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 Tue Jul 13 12:43:55 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from server1.siscom.net (server1.siscom.net [209.251.2.89]) by hub.freebsd.org (Postfix) with SMTP id 8BC3D1503E for ; Tue, 13 Jul 1999 12:43:49 -0700 (PDT) (envelope-from radams@siscom.net) Received: (qmail 83163 invoked from network); 13 Jul 1999 19:42:53 -0000 Received: from mp.siscom.net (HELO jason) ([209.251.2.49]) (envelope-sender ) by server1.siscom.net (qmail-ldap-1.03) with SMTP for ; 13 Jul 1999 19:42:53 -0000 Message-ID: <121f01becd68$46c41120$3102fbd1@siscom.net> From: "Robert J. Adams" To: Cc: , References: Subject: Re: Fibre Channel Controller Date: Tue, 13 Jul 1999 15:45:33 -0400 Organization: SISCOM, Inc. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew, Have you used these? If so, how does the FC route compare to say U2W SCSI? Something about a little piece of fiber running my drives makes me feel all warm and fuzzy. -j --- Robert J. Adams radams@siscom.net http://www.siscom.net Looking to outsource news? http://www.newshosting.com SISCOM Network Administration - President, SISCOM Inc. Phone: 937-222-8150 FAX: 937-222-8153 ----- Original Message ----- From: Matthew Jacob To: Robert J. Adams Cc: ; Sent: Friday, July 09, 1999 9:20 PM Subject: Re: Fibre Channel Controller > > > > Hello all, > > > > Anyone know of a Fibre Channel Controller that is compatible with FBSD? > > Qlogic 2100/2200. It's part of 3.0 and later, but has been backported into > 2.2.X. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 13 19:43:16 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9D84914D13; Tue, 13 Jul 1999 19:43:02 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id TAA07743; Tue, 13 Jul 1999 19:41:01 -0700 Date: Tue, 13 Jul 1999 19:40:56 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Robert J. Adams" Cc: hardware@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Fibre Channel Controller [ LONG RESPONSE ] In-Reply-To: <121f01becd68$46c41120$3102fbd1@siscom.net> 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 Tue, 13 Jul 1999, Robert J. Adams wrote: > Have you used these? A lot. Not only for FreeBSD, but Solaris, Linux, OpenBSD, NetBSD, NT, etc.. > If so, how does the FC route compare to say U2W SCSI? > Something about a little piece of fiber running my drives makes me feel all > warm and fuzzy. I'd have to say it's a mixed experience at this time. The data rates for U2W SCSI busses (and U3W which I'm getting a sample card for in about a month), what with PCI latencies, are comparable to what you get for 1024Mbit Fibre Channel (the difference between 40 Mhz x 16 bits and 100MB is not a lot, really). The drives for U2W or Fibre Channel are the same (but with different interfaces), so if you're running a small setup, U2W is probably a better choice (see below). Now, that's data rates. What turns out to be somewhat significant (particularly for larger bus configurations) is that the non-data transfer phases stuff on SCSI is the same data rate as it's always been (async mode, varying between 2 && 8MB/s depending on bus length)- Additionally, Request Sense is a completely separate command. In Fibre Channel SCSI, command and device control functions go out as a single FC packet, data moves as multiple packets, and the response that includes status *and* sense data (as needed) goes as one packet, and they all go at the same rate. This gives more headroom that you don't get in parallel SCSI. A classic amusement to me about this is an arrangement at NASA/Ames where differential SCSI is carried to a fibre optic repeater and then over fibre optics to a building about a kilometer away to tape drives in a silo (for offsite secondaries)- the tape drives really do take the data bursts at a healthy 10Mhz, 16 bits wide, but because command, mesage and status bytes, and inter-burst times, all operate at async data rates, the effective data rate is about 5MB/s. Whuf. What you really get with Fibre Channel that you don't get with U2W is a very large address space that configures a little bit more sanely than parallel SCSI. With private loop (that's the best tested at this time), you get 126 loop addresses, so you can put a lot of devices on one loop. You can ask (as the FreeBSD driver does do) for a specific loop address, but you'll just get what's available after arbitration. No more of this "oops, two devices have the same ID, we're hosed!". Don't. Even. Think. About. Mentioning. SCAM. Thank you. On the other hand, the code that's currently in FreeBSD that trys to manage loop address rearbitration where it's possible to come back after a loop initialization ('coz joe bob rebooted his workstation) is not very well tested yet. The Fabric support (which allows you to have, in theory, an arbitrarily large disk address space, but in practice for the way the current fabric management is being done allows only another 127 disks, has a lot more wringing out to be done too). You also get a bit more tolerant interconnect technology (whether you're using FC Optical or FC copper) where cable distance pretty much becomes a non-issue. But you also pay for this. For U2W you can expect to pay a tad more for the disks && the controllers and LVD cabling, and whatever your normal SCSI disk case costs are, but for Fibre Channel you should expect to budget for FC hubs (at a minimum 2k$ for a ~10 port hub), beaucoup more if you get a switch (for fabrics). The FC adapters are also more expensive than SCSI, but FC disks are in fact often *cheaper* than LVD or Ultra disks (why? I dunno- probably because the FC connector is a 40 pin SCA rather than an 80 pin SCA or 68 pin high density.... and the actual bus interface technology basically only has to manage 4 twisted pairs plus grounds). The real killer here is that boxes to put your fibre channel disks in are not only expensive, they're harder than hell to find, particularly in unit 1 quantities. So, to get back to your question: I'd have to say that FC is cool, and will really be awesome over time, but it's just *barely* at the level you could put it together in your own shop with. Caveat Emptor. Man, it's painful to admit this, but it's true. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 13 22:30:28 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 3AB0614F5C for ; Tue, 13 Jul 1999 22:30:24 -0700 (PDT) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id AAA11042 for hardware@FreeBSD.ORG; Wed, 14 Jul 1999 00:30:06 -0500 (CDT) Date: Wed, 14 Jul 1999 00:30:06 -0500 From: Tim Tsai To: hardware@FreeBSD.ORG Subject: Re: Fibre Channel Controller [ LONG RESPONSE ] Message-ID: <19990714003006.A10871@futuresouth.com> References: <121f01becd68$46c41120$3102fbd1@siscom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Matthew Jacob on Tue, Jul 13, 1999 at 07:40:56PM -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jul 13, 1999 at 07:40:56PM -0700, Matthew Jacob wrote: > So, to get back to your question: I'd have to say that FC is cool, and > will really be awesome over time, but it's just *barely* at the level you > could put it together in your own shop with. Caveat Emptor. Man, it's > painful to admit this, but it's true. That is my experience while looking for FC gear. I'd love to replace the storage systems on our dozen or so servers with two FC storage servers and a FC switch. I couldn't find any reasonably priced solutions. BTW, can your driver handle that scenario with a switch? i.e. multiple hosts accessing one or two FC arrays (with independent RAID controller). Thanks, Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 13 22:49:57 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 430F614DFC for ; Tue, 13 Jul 1999 22:49:45 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id WAA08120; Tue, 13 Jul 1999 22:48:32 -0700 Date: Tue, 13 Jul 1999 22:48:27 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Tim Tsai Cc: hardware@FreeBSD.ORG Subject: Re: Fibre Channel Controller [ LONG RESPONSE ] In-Reply-To: <19990714003006.A10871@futuresouth.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 > > So, to get back to your question: I'd have to say that FC is cool, and > > will really be awesome over time, but it's just *barely* at the level you > > could put it together in your own shop with. Caveat Emptor. Man, it's > > painful to admit this, but it's true. > > That is my experience while looking for FC gear. I'd love to replace > the storage systems on our dozen or so servers with two FC storage servers > and a FC switch. I couldn't find any reasonably priced solutions. > > BTW, can your driver handle that scenario with a switch? i.e. multiple > hosts accessing one or two FC arrays (with independent RAID controller). This can be done without a switch. I've had the following private loop setup, e.g., work reasonably well for me: Vixel Hub FreeBSD i386 -> | Solaris 2.7 intel -> | FreeBSD Alpha -> | Solaris 2.7 sparc -> |-(initiator/target dev I cannot name) |-4 Disk JBOD Linux i386 -> |-Sun Photon (A5000) (up to 14 disks) |-Sun Photon (A5000) (up to 14 disks) As long as the loop isn't disturbed, it's quite stable. Reasonable 'white board' disk ownership management works. If the loop is disturbed, the 'loop id shifting' thing I referred to can occur, and like I said, that code isn't well tested. I've tried a SOCAL (Sun's SBus FC card) in this configuration with mixed results (sometimes the loop just crashes and nobody can see anybody). I've tried a JNI card in this configuration, also with some mixed results. I have also had, ha ha, this configuration: Vixel Hub Solaris 2.7 sparc-> | Solaris 2.7 sparc-> | Solaris 2.7 sparc-> | Solaris 2.7 sparc-> |- 8 Disk JBOD *not* work well (I mean, it does work well, but the drive f/w was such that too many multiple initiator accesses cause the f/w on the drive to crash requiring a power cycle to correct. Really. Very. Very. Bad. I now have a friend of mine not really speaking to me because of this. Sigh). I've not tried the Symbios FC Raid controllers for quite a while, so I can't say how well they work. I'm always *very* eager to hear what people find out- I'm mostly self-funded in a lot of this, so my h/w test matrix isn't nearly as large as I would like. The switch configuration *can* work (it's early days for the code I put in), but all that really does is join together multiple loops such that if I query the Fabric name server and get list of disks back, I can 'map' them to loop ID's such that the Qlogic knows they're not on the local loop. This picture looks like, e.g.: Brocade Switch | (initiator/target dev I cannnot name)- | Sun Photon (A5000) - | | <- FreeBSD i386 | <- FreeBSD alpha | <- Linux Alpha Vixel Hub-> | | 4 Disk JBOD -> | Sun Photon -> | -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jul 13 23: 5: 0 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id C781214DFC for ; Tue, 13 Jul 1999 23:04:47 -0700 (PDT) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id BAA12296; Wed, 14 Jul 1999 01:04:40 -0500 (CDT) Date: Wed, 14 Jul 1999 01:04:40 -0500 From: Tim Tsai To: Matthew Jacob Cc: hardware@FreeBSD.ORG Subject: Re: Fibre Channel Controller [ LONG RESPONSE ] Message-ID: <19990714010440.A11885@futuresouth.com> References: <19990714003006.A10871@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Matthew Jacob on Tue, Jul 13, 1999 at 10:48:27PM -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The switch configuration *can* work (it's early days for the code I put > in), but all that really does is join together multiple loops such that if > I query the Fabric name server and get list of disks back, I can 'map' > them to loop ID's such that the Qlogic knows they're not on the local > loop. This picture looks like, e.g.: Actually I mentioned the switch because as far as I know you can configure it in such a way that the host will never see disks that it's not intended for. That should isolate the hosts from each other even if FC id's go in and out? It is analogous to VLAN on ethernet. We will probably look into that again soon. We need [HW] RAID on a handful of machines and I would rather spend the money on a couple of good storage arrays instead of buying one for each machine. NFS is out for our environment. Would you happen to have a host-independent (stand-alone) FC RAID controller that you can recommend? Thanks! Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 14 0:44:30 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E0CF014CE3 for ; Wed, 14 Jul 1999 00:44:28 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id AAA08337; Wed, 14 Jul 1999 00:44:18 -0700 Date: Wed, 14 Jul 1999 00:44:13 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Tim Tsai Cc: hardware@FreeBSD.ORG Subject: Re: Fibre Channel Controller [ LONG RESPONSE ] In-Reply-To: <19990714010440.A11885@futuresouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > The switch configuration *can* work (it's early days for the code I put > > in), but all that really does is join together multiple loops such that if > > I query the Fabric name server and get list of disks back, I can 'map' > > them to loop ID's such that the Qlogic knows they're not on the local > > loop. This picture looks like, e.g.: > > Actually I mentioned the switch because as far as I know you can > configure it in such a way that the host will never see disks that it's > not intended for. That should isolate the hosts from each other even if > FC id's go in and out? It is analogous to VLAN on ethernet. I believe you're referring to a Brocade feature- zoning. It's possible that other switches have that feature too. > > We will probably look into that again soon. We need [HW] RAID on a > handful of machines and I would rather spend the money on a couple of good > storage arrays instead of buying one for each machine. NFS is out for > our environment. > > Would you happen to have a host-independent (stand-alone) FC RAID > controller that you can recommend? Not that I know well enough to swear by. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 14 6: 4:58 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from mail-smtp.socket.net (mail-smtp.socket.net [216.106.1.32]) by hub.freebsd.org (Postfix) with ESMTP id A0AE214F39 for ; Wed, 14 Jul 1999 06:04:53 -0700 (PDT) (envelope-from vaevictus@socket.net) Received: from mail.socket.net (mail.socket.net [216.106.1.7]) by mail-smtp.socket.net (8.9.3/8.9.3) with SMTP id VAA10924 for ; Wed, 14 Jul 1999 21:04:56 -0500 From: vaevictus@socket.net Received: from socket.net ([216.106.1.12]) by mail.socket.net ; Wed, 14 Jul 1999 08:04:23 -0600 Reply-To: vaevictus@socket.net To: hardware@FreeBSD.org Date: Wed, 14 Jul 99 08:04:21 -600 Subject: Mylex960 SCSI X-Mailer: DMailWeb Web to Mail Gateway 1.5af, http://netwinsite.com/top_mail.htm Message-id: <378c8ad5.17fd.0@socket.net> X-User-Info: 216.106.19.246 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org When i try to install BSD off the floppies, I got a nasty hex system dump. I pulled out my Mylex 960 SCSI controller and it'll boot off the same floppies, so i figure it's the problem. Does FreeBSD support the Mylex controllers? If it does, how am I supposed to install it? Nathan Mahon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 14 6:51:13 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from cgi.icon.co.za (cgi.icon.co.za [196.26.208.8]) by hub.freebsd.org (Postfix) with ESMTP id B871914D1C for ; Wed, 14 Jul 1999 06:51:07 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: from mail450.icon.co.za (smtp.icon.co.za [196.26.208.3]) by cgi.icon.co.za (Postfix) with ESMTP id ACD7E466EA; Wed, 14 Jul 1999 15:50:50 +0200 (SAST) Received: from ceia.nordier.com (m1-45-dbn.dial-up.net [196.34.155.45]) by mail450.icon.co.za (8.9.3/8.9.3) with ESMTP id PAA12047; Wed, 14 Jul 1999 15:50:44 +0200 (GMT) From: rnordier@nordier.com Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.8.7) id PAA20268; Wed, 14 Jul 1999 15:50:31 +0200 (SAST) (envelope-from rnordier@nordier.com) Message-Id: <199907141350.PAA20268@ceia.nordier.com> Subject: Re: Mylex960 SCSI In-Reply-To: <378c8ad5.17fd.0@socket.net> from "vaevictus@socket.net" at "Jul 14, 1999 08:04:21 am" To: vaevictus@socket.net Date: Wed, 14 Jul 1999 15:50:30 +0200 (SAST) Cc: hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 > When i try to install BSD off the floppies, I got a nasty hex system dump. I > pulled out my Mylex 960 SCSI controller and it'll boot off the same floppies, > so i figure it's the problem. > Does FreeBSD support the Mylex controllers? > If it does, how am I supposed to install it? If the hex dump is happening before the kernel gets control, the problem may be in the boot code. You'd best let us know at what stage this is happening, and preferably transcribe the dump info and send it along. What version of FreeBSD you're trying to install would also be a help. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 14 8: 3:15 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from gw-nl3.philips.com (gw-nl3.philips.com [192.68.44.35]) by hub.freebsd.org (Postfix) with ESMTP id E161D153E8 for ; Wed, 14 Jul 1999 08:03:04 -0700 (PDT) (envelope-from R.Schofield@pbc.be.philips.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl3.philips.com with ESMTP id RAA03597 for ; Wed, 14 Jul 1999 17:02:07 +0200 (MEST) (envelope-from R.Schofield@pbc.be.philips.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl3.philips.com via mwrap (4.0a) id xma003592; Wed, 14 Jul 99 17:02:08 +0200 Received: from bcs11.pbc.be.philips.com (bcs11.bcs.cs.philips.com [130.139.40.111]) by smtprelay-nl1.philips.com (8.9.3/8.8.5-1.2.2m-19990317) with ESMTP id RAA01584 for ; Wed, 14 Jul 1999 17:02:06 +0200 (MET DST) Received: from exchvs01.bcs.cs.philips.com (exchvs01.bcs.cs.philips.com [130.139.40.10]) by bcs11.pbc.be.philips.com (8.6.10/8.6.10-1.2.1a-961023) with ESMTP id QAA00514 for ; Wed, 14 Jul 1999 16:56:53 +0200 Received: by exchvs01.bcs.cs.philips.com with Internet Mail Service (5.0.1460.8) id <3PH9RJAB>; Wed, 14 Jul 1999 17:00:20 +0200 Message-ID: <29F16C82368FD111914F00805F858E4F029DCF1A@exchvs01.bcs.cs.philips.com> From: "Schofield, Robert " To: "'freebsd-hardware@freebsd.org'" Subject: CAN bus, PC/104 support Date: Wed, 14 Jul 1999 17:00:18 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1460.8) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi there. This may not be the appropriate forum to post, so my apologies if it isn't. If this is the case, maybe someone would be kind enough to tell me where to go (oops, which forum to use ;^) I am looking at implementing a system based on a Pentium SBC (not a PC) with various on-board devices. The most important aspect is PC/104 bus support; is there any bus support for this under any flavour of FBSD? Secondly, is there anyone working on CAN bus support? Rob Schofield M.Sc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 14 10:14:43 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from mail-smtp.socket.net (mail-smtp.socket.net [216.106.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 71DE615411 for ; Wed, 14 Jul 1999 10:14:40 -0700 (PDT) (envelope-from vaevictus@socket.net) Received: from mail.socket.net (mail.socket.net [216.106.1.7]) by mail-smtp.socket.net (8.9.3/8.9.3) with SMTP id BAA29470 for ; Thu, 15 Jul 1999 01:14:49 -0500 From: vaevictus@socket.net Received: from socket.net ([216.106.1.12]) by mail.socket.net ; Wed, 14 Jul 1999 12:14:19 -0600 Reply-To: vaevictus@socket.net To: rnordier@nordier.com Cc: hardware@FreeBSD.ORG Date: Wed, 14 Jul 99 12:14:18 -600 Subject: Re: Mylex960 SCSI X-Mailer: DMailWeb Web to Mail Gateway 1.5af, http://netwinsite.com/top_mail.htm Message-id: <378cc56a.33cf.0@socket.net> X-User-Info: 216.106.0.22 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> When i try to install BSD off the floppies, I got a nasty hex system dump. I >> pulled out my Mylex 960 SCSI controller and it'll boot off the same floppies, >> so i figure it's the problem. >> Does FreeBSD support the Mylex controllers? >> If it does, how am I supposed to install it? > >If the hex dump is happening before the kernel gets control, the >problem may be in the boot code. You'd best let us know at what >stage this is happening, and preferably transcribe the dump info >and send it along. What version of FreeBSD you're trying to install >would also be a help. > >-- >Robert Nordier > This is happening immediately after the first disk hit... before the kernel gets control. I'm trying to install FreeBSD 3.2. Here's my hand transcribed dump: int=0000000d err=00000000 efl=00030083 eip=00009013 eax=0000dfd0 ebx=00000000 ecx=00000001 edx=0009fa09 esi=00000270 edi=000000d1 ebp=0000ffff esp=000003dc cs=f000 ds=9f80 es=9f80 fs=0040 gs=0000 ss=9dfd cs:eip=2e 0f 01 1e 1f f1 0f 01-54 08 89 5c 26 c6 44 25 ss:esp=00 c8 80 9f d1 00 70 02-00 00 f0 03 00 00 a0 fa System Halted hope this is accurate... :) n8 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 14 11:37:29 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from cgi.icon.co.za (cgi.icon.co.za [196.26.208.8]) by hub.freebsd.org (Postfix) with ESMTP id 5BD9A15413 for ; Wed, 14 Jul 1999 11:37:22 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: from mail450.icon.co.za (smtp.icon.co.za [196.26.208.3]) by cgi.icon.co.za (Postfix) with ESMTP id B5365464F1; Wed, 14 Jul 1999 20:35:26 +0200 (SAST) Received: from ceia.nordier.com (m1-13-dbn.dial-up.net [196.34.155.13]) by mail450.icon.co.za (8.9.3/8.9.3) with ESMTP id UAA13367; Wed, 14 Jul 1999 20:35:25 +0200 (GMT) From: rnordier@nordier.com Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.8.7) id UAA21271; Wed, 14 Jul 1999 20:35:11 +0200 (SAST) (envelope-from rnordier@nordier.com) Message-Id: <199907141835.UAA21271@ceia.nordier.com> Subject: Re: Mylex960 SCSI In-Reply-To: <378cc56a.33cf.0@socket.net> from "vaevictus@socket.net" at "Jul 14, 1999 12:14:18 pm" To: vaevictus@socket.net Date: Wed, 14 Jul 1999 20:35:10 +0200 (SAST) Cc: hardware@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (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 > This is happening immediately after the first disk hit... > before the kernel gets control. > I'm trying to install FreeBSD 3.2. > Here's my hand transcribed dump: > > int=0000000d err=00000000 efl=00030083 eip=00009013 > eax=0000dfd0 ebx=00000000 ecx=00000001 edx=0009fa09 > esi=00000270 edi=000000d1 ebp=0000ffff esp=000003dc > cs=f000 ds=9f80 es=9f80 fs=0040 gs=0000 ss=9dfd > cs:eip=2e 0f 01 1e 1f f1 0f 01-54 08 89 5c 26 c6 44 25 > ss:esp=00 c8 80 9f d1 00 70 02-00 00 f0 03 00 00 a0 fa > System Halted > > hope this is accurate... :) Good enough. :) Your firmware (presumably the SCSI controller) isn't compatible with the boot code. It's trying to take over the whole machine at a really fundamental level, and the software that hosts the boot code isn't prepared to give up that much control. You could submit a problem report (PR) for this, though I doubt there's likely to be anything that can be done about it immediately. One workaround would be to install FreeBSD 3.0R (which uses older boot code) and then upgrade to 3.2 without doing a reinstall. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 14 12:27:10 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id EBD4314BCD for ; Wed, 14 Jul 1999 12:27:07 -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.3/8.8.8) with ESMTP id MAA01035; Wed, 14 Jul 1999 12:22:59 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907141922.MAA01035@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: vaevictus@socket.net Cc: hardware@FreeBSD.org Subject: Re: Mylex960 SCSI In-reply-to: Your message of "Wed, 14 Jul 1999 08:04:21." <378c8ad5.17fd.0@socket.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 14 Jul 1999 12:22:59 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > When i try to install BSD off the floppies, I got a nasty hex system dump. I > pulled out my Mylex 960 SCSI controller and it'll boot off the same floppies, > so i figure it's the problem. > Does FreeBSD support the Mylex controllers? No. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jul 14 12:32:51 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 3DE7915479 for ; Wed, 14 Jul 1999 12:32:48 -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.3/8.8.8) with ESMTP id MAA01076; Wed, 14 Jul 1999 12:28:45 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907141928.MAA01076@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Schofield, Robert " Cc: "'freebsd-hardware@freebsd.org'" Subject: Re: CAN bus, PC/104 support In-reply-to: Your message of "Wed, 14 Jul 1999 17:00:18 +0200." <29F16C82368FD111914F00805F858E4F029DCF1A@exchvs01.bcs.cs.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 14 Jul 1999 12:28:45 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I am looking at implementing a system based on a Pentium SBC (not a PC) with > various on-board devices. The most important aspect is PC/104 bus support; > is there any bus support for this under any flavour of FBSD? PC104 is just ISA with a different connector. > Secondly, is there anyone working on CAN bus support? I don't recall anything recently. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 15 3:53:22 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.iol.ie (mail1.mail.iol.ie [194.125.2.192]) by hub.freebsd.org (Postfix) with ESMTP id 7E84814E12; Thu, 15 Jul 1999 03:53:12 -0700 (PDT) (envelope-from nick@iol.ie) Received: from beckett.earlsfort.iol.ie (beckett.earlsfort.iol.ie [194.125.21.2]) by mail.iol.ie Sendmail (v8.9.3) with ESMTP id LAA57480; Thu, 15 Jul 1999 11:53:07 +0100 (IST) Received: (from nick@localhost) by beckett.earlsfort.iol.ie Sendmail (v8.8.8) id LAA19073; Thu, 15 Jul 1999 11:52:43 +0100 From: Nick Hilliard Message-Id: <199907151052.LAA19073@beckett.earlsfort.iol.ie> Subject: Re: Fibre Channel Controller To: radams@siscom.net Date: Thu, 15 Jul 1999 11:52:41 +0100 (IST) Cc: mjacob@feral.com, hardware@FreeBSD.ORG, stable@FreeBSD.ORG X-NCC-RegID: ie.iol Content-Type: text Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Have you used these? If so, how does the FC route compare to say U2W SCSI? > Something about a little piece of fiber running my drives makes me feel all > warm and fuzzy. A pal of mine who designs FC cards mailed me about this a few months ago. Nick -- | Nick Hilliard | nick@iol.ie | | Tel: +353 1 6046800 | Advanced Systems Architect | | Fax: +353 1 6046888 | Ireland On-Line System Operations | <...> but lets face it if you think 80MBytes/sec is nearly as good as 100Mbytes per second, you have to realise a few things 1) you don't get anything close to 80Mbytes/sec because SCSI doesn't share the bandwidth very well. Whereas with Fibrechannel 80MBytes per/second sustained to/from disk is achievable with anyone's adapter and up to 96 with the better ones. When you compare IOs/sec SCSI falls away much faster. HP have managed 33000 IOs from one FC loop. 2) Just you try to configure 30 drives on a SCSI system and then try the same on Fibrechannel. Then put all the drives in another room and see if you can make it work. 3) Multi-Initiator on SCSI? Don't make me laugh. Every FC drive has two ports as standard. Multi-Initiator is built in. [...] 5) Lost packets on Fibrechannel does not mean lost data. It is true that Class 3 is like IP, it doesn't have ACKs and this is a problem because it can cause timeouts. But compare that with SCSI where if you have cabling problems (and I know all about SCSI cabling problems) you just can't make it work at all. 6) Fibrechannel drives do not consume 50% more than SCSI drives unless you want to compare current SCSI drives with old FC ones. [...] 8) FC is bidirectional and is meant to be dual loop so really you have 400Mbytes per second if you want to compare numbers. By the time Ultra160 is stable 2Gb FC links will be available. Where has SCSI to go then? 80Mhz I don't think so. 2Gb transceivers are readily available and 4Gb transceivers are well on their way. So what would I buy for my PC, well UltraSCSI of course, unless gives me an FC cabinet. Then again if I was buying a couple of terabytes then I would go FC, mirroring (RAID1) not RAID5 because drives are cheap and write performance is better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 15 4:14: 6 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (Postfix) with ESMTP id EA47414E68 for ; Thu, 15 Jul 1999 04:13:57 -0700 (PDT) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (lavender.rad.cc.keio.ac.jp [131.113.16.115]) by titanium.yy.ics.keio.ac.jp (8.8.8+3.0Wbeta13/3.7W) with ESMTP id UAA04634; Thu, 15 Jul 1999 20:13:04 +0900 (JST) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.9.3/3.7W) id UAA99437; Thu, 15 Jul 1999 20:13:03 +0900 (JST) Date: Thu, 15 Jul 1999 20:13:03 +0900 (JST) Message-Id: <199907151113.UAA99437@lavender.yy.cs.keio.ac.jp> To: R.Schofield@pbc.be.philips.com Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Audio chipset support In-Reply-To: Your message of "Tue, 13 Jul 1999 21:55:47 JST". <29F16C82368FD111914F00805F858E4F029DCF0F@exchvs01.bcs.cs.philips.com> From: sanpei@sanpei.org (MIHIRA Yoshiro) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org R.Schofield@pbc.be.philips.com Wrote: >> Can anyone tell me (rapidly) if ESS1868 and Cyrix CX5530 audio chipsets are >> supported under *any* version of FBSD? Current pcm sound driver support ESS1868, but I think it has some noise problem with poor CPU. So we created new ESS18xx sound driver. http://home.jp.FreeBSD.org/~sanpei/ and 3.2-RELEASE CD-ROM, expermit directory. I hope to update ESS18xx sound driver with this. But Mr. Luigi is too busy to commit this. Does someone commit our ESS18xx sound driver.. MIHIRA Sanpei Yoshiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 15 9:15:43 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 96ECE1559D; Thu, 15 Jul 1999 09:15:28 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id JAA13652; Thu, 15 Jul 1999 09:14:44 -0700 Date: Thu, 15 Jul 1999 09:14:44 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Nick Hilliard Cc: radams@siscom.net, hardware@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Fibre Channel Controller In-Reply-To: <199907151052.LAA19073@beckett.earlsfort.iol.ie> 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 > 3) Multi-Initiator on SCSI? Don't make me laugh. Every FC drive has two > ports as standard. Multi-Initiator is built in. A word of caution about this- there is a lot of buggy driver f/w for the dual ports. > 6) Fibrechannel drives do not consume 50% more than SCSI drives unless you What does this mean? > want to compare current SCSI drives with old FC ones. > > [...] > > 8) FC is bidirectional and is meant to be dual loop so really you have > 400Mbytes per second if you want to compare numbers. By the time Ultra160 > is stable 2Gb FC links will be available. Where has SCSI to go then? 80Mhz > I don't think so. 2Gb transceivers are readily available and 4Gb > transceivers are well on their way. No, wrong thinking here. This is theory. In practice unless you use switches you don't have full duplex. I don't know of any FC card that has the number of connectors to make it true dual-loop (2x{send,receive}), so that argument is bogus. A better point to note that the 2GB FC links are coming. > So what would I buy for my PC, well UltraSCSI of course, unless > gives me an FC cabinet. Then again if I was buying a couple of terabytes > then I would go FC, mirroring (RAID1) not RAID5 because drives are cheap > and write performance is better. This is my conclusion too, but the figure of merit isn't a "couple of terabytes", it's "numbers of addressable units". - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 15 9:18:29 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.iol.ie (mail1.mail.iol.ie [194.125.2.192]) by hub.freebsd.org (Postfix) with ESMTP id D07E315591; Thu, 15 Jul 1999 09:18:21 -0700 (PDT) (envelope-from nick@iol.ie) Received: from beckett.earlsfort.iol.ie (beckett.earlsfort.iol.ie [194.125.21.2]) by mail.iol.ie Sendmail (v8.9.3) with ESMTP id RAA01940; Thu, 15 Jul 1999 17:17:46 +0100 (IST) Received: (from nick@localhost) by beckett.earlsfort.iol.ie Sendmail (v8.8.8) id RAA00121; Thu, 15 Jul 1999 17:17:45 +0100 From: Nick Hilliard Message-Id: <199907151617.RAA00121@beckett.earlsfort.iol.ie> Subject: Re: Fibre Channel Controller To: mjacob@feral.com Date: Thu, 15 Jul 1999 17:17:45 +0100 (IST) Cc: nick@iol.ie, radams@siscom.net, hardware@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: from "Matthew Jacob" at Jul 15, 99 09:14:44 am X-NCC-RegID: ie.iol Content-Type: text Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > 6) Fibrechannel drives do not consume 50% more than SCSI drives unless you > > What does this mean? Sorry, it was meant to be "50% more power". Nick -- | Nick Hilliard | nick@iol.ie | | Tel: +353 1 6046800 | Advanced Systems Architect | | Fax: +353 1 6046888 | Ireland On-Line System Operations | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 15 9:30:57 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8971D15591; Thu, 15 Jul 1999 09:30:54 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id JAA13716; Thu, 15 Jul 1999 09:30:24 -0700 Date: Thu, 15 Jul 1999 09:30:23 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Nick Hilliard Cc: radams@siscom.net, hardware@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Fibre Channel Controller In-Reply-To: <199907151617.RAA00121@beckett.earlsfort.iol.ie> 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 > > > 6) Fibrechannel drives do not consume 50% more than SCSI drives unless you > > > > What does this mean? > > Sorry, it was meant to be "50% more power". To be sure! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jul 15 9:36: 1 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.iol.ie (mail2.mail.iol.ie [194.125.2.193]) by hub.freebsd.org (Postfix) with ESMTP id 2E57315622; Thu, 15 Jul 1999 09:35:40 -0700 (PDT) (envelope-from nick@iol.ie) Received: from beckett.earlsfort.iol.ie (beckett.earlsfort.iol.ie [194.125.21.2]) by mail.iol.ie Sendmail (v8.9.3) with ESMTP id RAA68259; Thu, 15 Jul 1999 17:35:34 +0100 (IST) Received: (from nick@localhost) by beckett.earlsfort.iol.ie Sendmail (v8.8.8) id RAA01573; Thu, 15 Jul 1999 17:35:34 +0100 From: Nick Hilliard Message-Id: <199907151635.RAA01573@beckett.earlsfort.iol.ie> Subject: Re: Fibre Channel Controller To: mjacob@feral.com Date: Thu, 15 Jul 1999 17:35:33 +0100 (IST) Cc: nick@iol.ie, radams@siscom.net, hardware@FreeBSD.ORG, stable@FreeBSD.ORG In-Reply-To: from "Matthew Jacob" at Jul 15, 99 09:30:23 am X-NCC-RegID: ie.iol Content-Type: text Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > 6) Fibrechannel drives do not consume 50% more than SCSI drives unless you > > > > > > What does this mean? > > > > Sorry, it was meant to be "50% more power". > > To be sure! This was a comment which referred to some truly ancient large FC drives which ran really hot. The original mail was out of context, which is why it looks like a mildly dumb statement to make. Nick -- | Nick Hilliard | nick@iol.ie | | Tel: +353 1 6046800 | Advanced Systems Architect | | Fax: +353 1 6046888 | Ireland On-Line System Operations | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jul 16 21: 8:10 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from mercury.gfit.net (ns.gfit.net [209.41.124.90]) by hub.freebsd.org (Postfix) with ESMTP id 7C36114E4F for ; Fri, 16 Jul 1999 21:08:03 -0700 (PDT) (envelope-from tom@embt.com) Received: from paranor.embt.net (timembt.iinc.com [206.67.169.229]) by mercury.gfit.net (8.8.8/8.8.8) with SMTP id XAA28952 for ; Fri, 16 Jul 1999 23:06:59 -0500 (CDT) (envelope-from tom@embt.com) Message-Id: <3.0.3.32.19990717000615.006f2278@mail.embt.com> X-Sender: tembt@mail.embt.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sat, 17 Jul 1999 00:06:15 -0400 To: freebsd-hardware@freebsd.org From: Tom Embt Subject: HPT366 IDE/UDMA66 Support? (like on Abit BE6/BY6/BP6) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is there (or will there) be 3.x support for the HPT366 UDMA66 IDE controller that Abit is putting on some of their boards? I have a BP6 and would hope to someday use IDE3 and IDE4 in FreeBSD. Tom Embt tom@embt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jul 17 9:47:44 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from tasam.com (tasam.com [206.161.83.22]) by hub.freebsd.org (Postfix) with ESMTP id 0443914C47 for ; Sat, 17 Jul 1999 09:47:40 -0700 (PDT) (envelope-from freebsd.list@bug.tasam.com) Received: from bug (209-122-196-80.s80.tnt5.lnh.md.dialup.rcn.com [209.122.196.80]) by tasam.com (8.9.3/8.9.1) with SMTP id MAA26475; Sat, 17 Jul 1999 12:47:31 -0400 (EDT) Message-ID: <005801bed073$f94e3060$0286860a@tasam.com> From: "Joe Gleason" To: , "Tom Embt" References: <3.0.3.32.19990717000615.006f2278@mail.embt.com> Subject: Re: HPT366 IDE/UDMA66 Support? (like on Abit BE6/BY6/BP6) Date: Sat, 17 Jul 1999 12:46:48 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org If I was to venture a guess, IDE3 + 4 are not detected because FreeBSD does't look for more than 2 ide controlers. I certainly don't know, but you can try hacking the kernel and creating wdc2 and wdc3 in addition to wdc0 and wdc1. ----- Original Message ----- From: Tom Embt To: Sent: Saturday, July 17, 1999 00:06 Subject: HPT366 IDE/UDMA66 Support? (like on Abit BE6/BY6/BP6) > > Is there (or will there) be 3.x support for the HPT366 UDMA66 IDE > controller that Abit is putting on some of their boards? > > I have a BP6 and would hope to someday use IDE3 and IDE4 in FreeBSD. > > > > Tom Embt > tom@embt.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jul 17 14:43:52 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 9603C14C57 for ; Sat, 17 Jul 1999 14:43:34 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id RAA00568; Sat, 17 Jul 1999 17:43:26 -0400 (EDT) Message-ID: <19990717174325.A199@netmonger.net> Date: Sat, 17 Jul 1999 17:43:25 -0400 From: Christopher Masto To: freebsd-hardware@FreeBSD.ORG Subject: Re: Would anyone like to start a FreeBSD irda project? Mail-Followup-To: freebsd-hardware@FreeBSD.ORG References: <19990708012651.66717.qmail@hotmail.com> <19990713145505.A7398@matrix.42.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19990713145505.A7398@matrix.42.org>; from Stefan `Sec` Zehl on Tue, Jul 13, 1999 at 02:55:05PM +0200 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jul 13, 1999 at 02:55:05PM +0200, Stefan `Sec` Zehl wrote: > Count me in. I was planning to check how hard a minimal IRComm or IRObex > implementation would be. It looks like the IR is treated like a normal > COM1 and can talk raw IR with BSD already. So it might be possible to > implement the rest in userland which would make debugging far easier. I already started on something like that, partly as a joke.. but there are some timing issues. In the end, it does need to be a device driver, since IrCOMM at least should be providing "fake" serial ports. Anyway, I'm quite interested in this, though my free time keeps fluctuating wildly. The one good thing about it is that the standards are generally available. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message