From owner-freebsd-hardware Mon Aug 28 1:55:12 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 8D61037B43E; Mon, 28 Aug 2000 01:55:06 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id CAA00739; Mon, 28 Aug 2000 02:09:02 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008280909.CAA00739@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Jin Guojun (DSD staff) Cc: hardware@freebsd.org, smp@freebsd.org Subject: Re: 370DLE motherboard In-reply-to: Your message of "Thu, 24 Aug 2000 16:01:45 PDT." <200008242301.e7ON1jX13791@portnoy.lbl.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 28 Aug 2000 02:09:02 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Just tested on Supermicro 370DLE motherboard and had problem with dual CPU. These aren't actually "problems" as such; they're fairly consistent with expected results. > The fxp0 is the primary network link, and the sk0 is a back-to-back connection > to the other 370DLE (both are identical). > > With one CPU installed, the sk0 throughput is 900 Mbps. > With two CPU installed, the sk0 throughput drops to 837 Mbps (non_SMP kernel). > With two CPU installed + SMP kernel, the sk0 throughput drops to 770 Mbps. > > Case 1 and 3 are expected, however, the case 2 is NOT expected (non_SMP kernel). Actually, it's not entirely unexpected. I'd accept that even if the second CPU is idle, there is extra latency somewhere in the chipset due to its presence. > The dmesg shows some information about timer (8254) interrupt issue. > > APIC_IO: Testing 8254 interrupt delivery > APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0 intpin 2 > APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 > Waiting 7 seconds for SCSI devices to settle > SMP: AP CPU #1 Launched! > > Both machines have the same message. I wonder if the 4.1 does not recognize > the board well, or there is something wrong with "ServerWork LE" chipset. No, this is a harmless bug. It's common for systems to lie about the 8254 interrupt routing, and we should probably complain less bitterly about it. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Aug 28 6:54:10 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id C5F3937B42C for ; Mon, 28 Aug 2000 06:54:07 -0700 (PDT) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JTIC5RW7OG000CYU@research.kpn.com> for freebsd-hardware@freebsd.org; Mon, 28 Aug 2000 15:54:02 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Mon, 28 Aug 2000 15:54:02 +0100 Content-return: allowed Date: Mon, 28 Aug 2000 15:54:00 +0100 From: "Koster, K.J." Subject: DE205 disfunctional To: 'FreeBSD Hardware mailing list' Cc: "Steehouder, R.J." Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D77DC@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear all, I have run into an DE205 card that our le driver was unable to drive. The mailing list archives suggest replacing the card, which we have done. Perhaps HARDWARE.TXT should be updated with something like "DE205 is known to be problematic". As a side note: if I compile the de driver for a 3c305 card into the kernel and I install the kernel, it does not show anything in dmesg. It shows up in the visual kernel boot config, but it does not say anything like "ed0: not found". Why is that? What am I missing? Kees Jan ================================================= TV is the worst of both worlds. It's not as good at words as radio is because the pictures are a distraction which demand attention, and it's not as good as cinema because the pictures are not nearly as good. [Douglas Adams] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Aug 28 12:27:57 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from wormhole.bluestar.net (wormhole.bluestar.net [208.53.1.61]) by hub.freebsd.org (Postfix) with ESMTP id 6B51137B422; Mon, 28 Aug 2000 12:27:53 -0700 (PDT) Received: from bsd.planetwe.com (bsd.planetwe.com [64.182.69.158]) by wormhole.bluestar.net (8.10.1/8.10.1) with ESMTP id e7SJRmN02662; Mon, 28 Aug 2000 14:27:48 -0500 (CDT) Received: (from steve@localhost) by bsd.planetwe.com (8.9.3/8.9.3) id OAA52362; Mon, 28 Aug 2000 14:27:48 -0500 (CDT) (envelope-from steve) Date: Mon, 28 Aug 2000 14:27:48 -0500 From: Steve Price To: freebsd-hardware@freebsd.org Cc: freebsd-isp@freebsd.org Subject: external storage questions Message-ID: <20000828142748.B47688@bsd.planetwe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm looking for external storage solutions ala the ones provided by EMC that allow multiple hosts to connect to a single external storage box. Any hints on workable solutions would be greatly appreciated? BTW, my pockets aren't real deep so I'm looking for cost-effective solutions. Otherwise I'd plunk down a $1MM for an EMC box. :) Thanks. -steve PS: Sorry for the crosspost. Please remove one (or both) of the mailing lists before replying. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Aug 28 15:40: 8 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from lariat.org (lariat.org [12.23.109.2]) by hub.freebsd.org (Postfix) with ESMTP id 4694F37B43C for ; Mon, 28 Aug 2000 15:40:01 -0700 (PDT) Received: from mustang.lariat.org (IDENT:ppp0.lariat.org@lariat.org [12.23.109.2]) by lariat.org (8.9.3/8.9.3) with ESMTP id QAA08969 for ; Mon, 28 Aug 2000 16:39:50 -0600 (MDT) Message-Id: <4.3.2.7.2.20000828160606.04ca9e90@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 28 Aug 2000 16:09:00 -0600 To: hardware@freebsd.org From: Brett Glass Subject: UDMA66 Controllers? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Which UDMA66 controllers, if any, are currently supported by FreeBSD's ATAPI drivers? Which should be avoided? A client has just bought a hot new UDMA66 drive, and would like to run it at full speed. His motherboard doesn't support UDMA66, so I'll need to add a controller card. All recommendations (other than going to SCSI -- the drive is already bought) would be appreciated! --Brett Glass To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Aug 28 16:21:24 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from defiant.quansoo.com (adsl-216-158-26-30.cust.oldcity.dca.net [216.158.26.30]) by hub.freebsd.org (Postfix) with ESMTP id 4628D37B424 for ; Mon, 28 Aug 2000 16:21:22 -0700 (PDT) Received: from localhost (cgriffiths@localhost) by defiant.quansoo.com (8.9.3/8.9.3) with ESMTP id TAA00580 for ; Mon, 28 Aug 2000 19:21:19 -0400 (EDT) (envelope-from cgriffiths@quansoo.com) X-Authentication-Warning: defiant.quansoo.com: cgriffiths owned process doing -bs Date: Mon, 28 Aug 2000 19:21:19 -0400 (EDT) From: "Christopher T. Griffiths" To: hardware@freebsd.org Subject: PCMCIA support for Symphony wireless networking? 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 running 4.1 -stable and it does not seem to have support under pccard for this card. I am looking for a pretty low cost solution for wireless lan connectivity and this looks pretty good. Is there any plan to support this network card under FreeBSD? Any help or direction would be great. Thanks Chris --- Christopher T. Griffiths Quansoo Group Inc. cgriffiths@quansoo.com Phone: (302) 777-4141 Fax: (302) 777-4142 Mobile: (302) 521-3436 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Aug 28 21:23:17 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from relay.infotel.ru (relay.infotel.ru [195.170.200.65]) by hub.freebsd.org (Postfix) with ESMTP id 26F7837B446; Mon, 28 Aug 2000 21:23:12 -0700 (PDT) Received: from krsk.infotel.ru ([195.161.20.246]) by relay.infotel.ru (8.8.7/8.8.7) with ESMTP id IAA21323; Tue, 29 Aug 2000 08:19:11 +0400 Received: from priem ([195.170.199.36]) by krsk.infotel.ru (8.9.3/8.9.3) with SMTP id MAA18718; Tue, 29 Aug 2000 12:08:50 +0700 Message-ID: <000b01c01178$ab68e560$0509a8c0@priem.nifti.krasnoyarsk.su> From: "nifti" To: Cc: Subject: Drivers for Promise UDMA-66 card ? Date: Tue, 29 Aug 2000 12:19:10 +0700 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear Sirs: Does anybody know how to make FreeBSD detect a Promise UDMA-66 card on P-III ? Is any driver for this card exist (and where)? On my server all two HDDs are connected to this card. I am using FreeBSD 2.2.8 Release. Oleg P.S. Please answer directly on this e-mail or write to olmi@home.krasnoyarsk.ru . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Aug 29 0:10:52 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mx7.port.ru (mx7.port.ru [194.67.23.44]) by hub.freebsd.org (Postfix) with ESMTP id E5CF237B422; Tue, 29 Aug 2000 00:10:46 -0700 (PDT) Received: from [212.96.98.34] (helo=[212.96.98.34]) by mx7.port.ru with esmtp (Exim 3.14 #6) id 13TfXb-0001Zp-00; Tue, 29 Aug 2000 11:10:45 +0400 Date: Tue, 29 Aug 2000 11:10:41 +0400 (MSD) From: Jaroshenko Serge X-Sender: jaroshenko@freebsd.merlin.ru To: nifti Cc: freebsd-questions@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Drivers for Promise UDMA-66 card ? In-Reply-To: <000b01c01178$ab68e560$0509a8c0@priem.nifti.krasnoyarsk.su> 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! You can see in /usr/src/sys/dev/ata/ata-dma.c . FreeBSD suport Promise Ultra33 Ultra66 Ultra100 . For add suport Promise IDE controller in your config kernel - see and read comment in /usr/src/sys/i386/conf/LINT. Best regards. Serge. On Tue, 29 Aug 2000, nifti wrote: > Dear Sirs: > > Does anybody know how to make FreeBSD detect > a Promise UDMA-66 card on P-III ? > Is any driver for this card exist (and where)? > > On my server all two HDDs are connected to this card. > > I am using FreeBSD 2.2.8 Release. > > Oleg > > P.S. Please answer directly on this e-mail or > write to olmi@home.krasnoyarsk.ru . > > > > 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 Aug 29 18:39:21 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from vista.athms.com (athms.bayarea.net [204.71.213.154]) by hub.freebsd.org (Postfix) with ESMTP id B041237B422 for ; Tue, 29 Aug 2000 18:39:17 -0700 (PDT) Received: from goofy.int.athms.com ([192.168.100.12] helo=athms.com) by vista.int.athms.com with esmtp (Exim 3.15) id 13TuGo-00005F-00 for ; Tue, 29 Aug 2000 15:54:18 -0700 Message-ID: <39AC3E08.A2666490@athms.com> Date: Tue, 29 Aug 2000 15:49:44 -0700 From: Tom Czarnik X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-hardware@FreeBSD.ORG" Subject: Cannot access files on IDE cdrom after 4.1-STABLE migration Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org After migrating (via cvsup) to 4.1-STABLE from 4.1-RC, I cannot access any files on an IDE CD-ROM. I can mount it, but there are no files. The only file that changed in /usr/src/sys/isofs/cd9660 between my 4.1-RC build on 2000-07-15 and 4.1-STABLE on 2000-08-24 was cd9660_mount.h. [4.1-RC built on 2000-07-15] ============================ Aug 29 14:40:51 vista /kernel.old: cd9660: RockRidge Extension root@vista:~$ df /cdrom Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/acd0c 648478 648478 0 100% /cdrom root@vista:~$ dir -d /cdrom drwxr-xr-x 2 root wheel 512 Aug 29 00:02 cdrom root@vista:~$ ls -l /cdrom total 5276 -r--r--r-- 1 root wheel 1462 Mar 8 09:21 00_TRANS.TBL -rw-r--r-- 1 root wheel 9706 Mar 7 10:14 ABOUT.TXT -rw-r--r-- 1 root wheel 981 Mar 7 10:14 ERRATA.TXT -rw-r--r-- 1 root wheel 28160 Mar 7 10:14 HARDWARE.TXT -rw-r--r-- 1 root wheel 49144 Mar 7 10:14 INSTALL.TXT -rw-r--r-- 1 root wheel 4722 Mar 7 10:14 LAYOUT.TXT -rw-r--r-- 1 root wheel 4317 Mar 7 10:14 README.TXT -rw-r--r-- 1 root wheel 58130 Mar 7 10:14 RELNOTES.TXT -rw-r--r-- 1 root wheel 17479 Mar 7 10:14 TROUBLE.TXT -rw-r--r-- 1 root wheel 8367 Mar 7 10:14 UPGRADE.TXT drwxr-xr-x 4 root wheel 6144 Mar 7 22:25 XF86336 drwxr-xr-x 2 root wheel 16384 Mar 7 12:25 bin drwxr-xr-x 2 root wheel 4096 Mar 7 12:25 catpages -rw-r--r-- 1 root wheel 34 Mar 7 10:14 cdrom.inf drwxr-xr-x 2 root wheel 2048 Mar 7 12:26 compat1x drwxr-xr-x 2 root wheel 2048 Mar 7 12:26 compat20 drwxr-xr-x 2 root wheel 2048 Mar 7 12:26 compat21 drwxr-xr-x 2 root wheel 2048 Mar 7 12:26 compat22 drwxr-xr-x 2 root wheel 2048 Mar 7 12:26 compat3x drwxr-xr-x 2 root wheel 8192 Mar 7 10:14 crypto drwxr-xr-x 2 root wheel 6144 Feb 8 2000 des drwxr-xr-x 2 root wheel 2048 Mar 7 12:26 dict drwxr-xr-x 2 root wheel 6144 Mar 7 12:26 doc -rw-r--r-- 1 root wheel 60267 Mar 8 09:21 filename.txt drwxr-xr-x 2 root wheel 2048 Mar 7 12:24 floppies drwxr-xr-x 2 root wheel 4096 Mar 7 12:26 games drwxr-xr-x 2 root wheel 2048 Mar 7 12:26 info -rw-r--r-- 1 root wheel 5042252 Mar 7 10:12 kernel drwxr-xr-x 2 root wheel 4096 Mar 7 12:25 manpages drwxr-xr-x 63 root wheel 8192 Jan 31 2000 packages drwxr-xr-x 2 root wheel 2048 Mar 7 12:28 ports drwxr-xr-x 2 root wheel 2048 Mar 7 12:26 proflibs drwxr-xr-x 2 root wheel 36864 Mar 7 12:28 src root@vista:~$ cdcontrol -f /dev/acd0c info Starting track = 1, ending track = 1, TOC size = 18 bytes track start duration block length type ------------------------------------------------- 1 0:02.00 72:05.16 0 324241 data 170 72:05.16 - 324241 - - [4.1-STABLE built on 200-08-24] =============================== Aug 29 14:47:28 vista /kernel: cd9660: RockRidge Extension Aug 29 14:47:30 vista /kernel: RRIP without PX field? root@vista:~$ df /cdrom Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/acd0c 648478 648478 0 100% /cdrom root@vista:~$ dir -d /cdrom -r-xr-xr-x 1 root wheel 0 Dec 31 1969 /cdrom root@vista:~$ cdcontrol -f /dev/acd0c info Starting track = 1, ending track = 1, TOC size = 18 bytes track start duration block length type ------------------------------------------------- 1 0:02.00 72:05.16 0 324241 data 170 72:05.16 - 324241 - - If I use 'mount_cd9660 -r /dev/acd0c /cdrom' everything is the same as above except /cdrom remains an directory and it is empty. After a mount, I cannot unmount. The sytem must be rebooted. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Aug 29 18:55:17 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 8EA6937B43C for ; Tue, 29 Aug 2000 18:55:15 -0700 (PDT) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id e7U1tEm23038; Tue, 29 Aug 2000 18:55:14 -0700 Date: Tue, 29 Aug 2000 18:55:14 -0700 From: Brooks Davis To: Tom Czarnik Cc: "freebsd-hardware@FreeBSD.ORG" Subject: Re: Cannot access files on IDE cdrom after 4.1-STABLE migration Message-ID: <20000829185514.A22968@Odin.AC.HMC.Edu> References: <39AC3E08.A2666490@athms.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <39AC3E08.A2666490@athms.com>; from tom@athms.com on Tue, Aug 29, 2000 at 03:49:44PM -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Aug 29, 2000 at 03:49:44PM -0700, Tom Czarnik wrote: > > After migrating (via cvsup) to 4.1-STABLE from 4.1-RC, I cannot access > any files on an IDE CD-ROM. I can mount it, but there are no files. The > only file that changed in /usr/src/sys/isofs/cd9660 between my 4.1-RC > build on 2000-07-15 and 4.1-STABLE on 2000-08-24 was cd9660_mount.h. This has been fixed, you need to upgrade again. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Aug 31 5:24:11 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from proton.hexanet.fr (proton.hexanet.fr [194.98.140.18]) by hub.freebsd.org (Postfix) with ESMTP id C05E237B422 for ; Thu, 31 Aug 2000 05:24:03 -0700 (PDT) Received: from proton.hexanet.fr (localhost [127.0.0.1]) by proton.hexanet.fr (8.9.3/8.9.3) with ESMTP id OAA02849 for ; Thu, 31 Aug 2000 14:23:59 +0200 (CEST) (envelope-from nighty@proton.hexanet.fr) Message-Id: <200008311223.OAA02849@proton.hexanet.fr> X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: chris@hexanet.fr From: "Christophe Prevotaux" To: freebsd-hardware@freebsd.org Subject: [HELP] USB , Gateway Solo 2150 and CURRENT Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 31 Aug 2000 14:23:58 +0200 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am running CURRENT on my Gateway Solo 2150 Laptop among the problems I have uhci0 keeps telling me this: uhci0: at device 7.2 on pci0 uhci0: Invalid irq 255 uhci0: Please switch on USB support and switch PNP-OS to 'No' in BIOS However I have no option to switch on or off USB support in my Laptop BIOS I can it seems set on or off the PNP thing even though it is not called that way in the PhoenixBios ( it is called Other/Win95/Win98-2000 i think :)) How can do to make my USB support work ? I also still have the problem of my PCMCIA-Cardbus DLINK DFE 660TX ethernet card that is not supported under FreeBSD , but it work very well under Linux I wonder if someone could not port the Linux driver under FreeBSD ? below is my full dmesg in the event it could help somebody answer my queries :) Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Mon Aug 28 19:25:26 CEST 2000 root@xxxx.hexanet.fr:/usr/obj/usr/src/sys/ZIPPY Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 167706624 (163776K bytes) avail memory = 159285248 (155552K bytes) Preloaded elf kernel "kernel" at 0xc0386000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc038609c. Pentium Pro MTRR support enabled md0: Malloc disk apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pci0: at 0.0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 9 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1050-0x105f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: at device 7.2 on pci0 uhci0: Invalid irq 255 uhci0: Please switch on USB support and switch PNP-OS to 'No' in BIOS device_probe_and_attach: uhci0 attach returned 6 pci0: at 7.3 pcic-pci0: irq 9 at device 8.0 on pci0 pcic-pci0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC pci int + CSC serial isa irq] pcic-pci1: irq 9 at device 8.1 on pci0 pcic-pci1: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC pci int + CSC serial isa irq] pci0: (vendor=0x1102, dev=0x8938) at 9.0 irq 5 <- unknown ? pci0: (vendor=0x11c1, dev=0x0448) at 10.0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 pcic0: at port 0x3e0 iomem 0xd0000 on isa0 pcic0: Polling mode pccard0: on pcic0 pccard1: on pcic0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources ad0: 11513MB [23392/16/63] at ata0-master using UDMA33 acd0: CDROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s1a pccard: card inserted, slot 0 logo_saver: no suitable graphics mode <-- here is another problem I have :) anyone ? module_register_init: MOD_LOAD (logo_saver, c11d7b3c, 0) error 19 ed1 at port 0x240-0x25f irq 3 slot 0 on pccard0 ed1: address 00:00:e8:7f:0f:34, type NE2000 (16 bit) -- -- =================================================================== Christophe Prevotaux Email: chris@hexanet.fr HEXANET SARL URL: http://www.hexanet.fr/ Z.A Farman Sud Tel: +33 (0)3 26 79 30 05 9 rue Roland Coffignot Direct: +33 (0)3 26 79 08 02 BP415 Fax: +33 (0)3 26 79 30 06 51689 Reims Cedex 2 FRANCE =================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Aug 31 13:22: 4 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from calcaphon.demon.co.uk (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id CC5D437B43E for ; Thu, 31 Aug 2000 13:19:40 -0700 (PDT) Received: from henny.webweaving.org (henny.qubesoft.com [192.168.1.5]) by calcaphon.demon.co.uk (8.9.3/8.9.1) with ESMTP id VAA63400; Thu, 31 Aug 2000 21:19:03 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id VAA32869; Thu, 31 Aug 2000 21:18:21 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Thu, 31 Aug 2000 21:18:21 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@henny.webweaving.org Reply-To: Nick Hibma To: Christophe Prevotaux Cc: freebsd-hardware@FreeBSD.org Subject: Re: [HELP] USB , Gateway Solo 2150 and CURRENT In-Reply-To: <200008311223.OAA02849@proton.hexanet.fr> 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 If there is no switch in your BIOS that makes the message go away, you are out of luck until FreeBSD has full PCI enumeration (or whatever it is called) support. Nick On Thu, 31 Aug 2000, Christophe Prevotaux wrote: > > I am running CURRENT on my Gateway Solo 2150 Laptop > > among the problems I have > > uhci0 keeps telling me this: > > uhci0: at device 7.2 on pci0 > uhci0: Invalid irq 255 > uhci0: Please switch on USB support and switch PNP-OS to 'No' in BIOS > > > However I have no option to switch on or off USB support in my Laptop BIOS > > I can it seems set on or off the PNP thing even though it is not called that > way > in the PhoenixBios ( it is called Other/Win95/Win98-2000 i think :)) > > > How can do to make my USB support work ? > > > I also still have the problem of my PCMCIA-Cardbus DLINK DFE 660TX ethernet > card > that is not supported under FreeBSD , but it work very well under Linux > I wonder if someone could not port the Linux driver under FreeBSD ? > > > below is my full dmesg in the event it could help somebody answer my queries :) > > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 5.0-CURRENT #0: Mon Aug 28 19:25:26 CEST 2000 > root@xxxx.hexanet.fr:/usr/obj/usr/src/sys/ZIPPY > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x683 Stepping = 3 > Features=0x383f9ff AT,PSE36,MMX,FXSR,XMM> > real memory = 167706624 (163776K bytes) > avail memory = 159285248 (155552K bytes) > Preloaded elf kernel "kernel" at 0xc0386000. > Preloaded userconfig_script "/boot/kernel.conf" at 0xc038609c. > Pentium Pro MTRR support enabled > md0: Malloc disk > apm0: on motherboard > apm0: found APM BIOS v1.2, connected at v1.2 > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pci0: at 0.0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pci1: at 0.0 irq 9 > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port 0x1050-0x105f at device 7.1 on > pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > uhci0: at device 7.2 on pci0 > uhci0: Invalid irq 255 > uhci0: Please switch on USB support and switch PNP-OS to 'No' in BIOS > device_probe_and_attach: uhci0 attach returned 6 > pci0: at 7.3 > pcic-pci0: irq 9 at device 8.0 on pci0 > pcic-pci0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC > pci int + CSC serial isa irq] > pcic-pci1: irq 9 at device 8.1 on pci0 > pcic-pci1: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC > pci int + CSC serial isa irq] > pci0: (vendor=0x1102, dev=0x8938) at 9.0 irq 5 <- unknown ? > pci0: (vendor=0x11c1, dev=0x0448) at 10.0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > psm0: irq 12 on atkbdc0 > psm0: model Generic PS/2 mouse, device ID 0 > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > pcic0: at port 0x3e0 iomem 0xd0000 on isa0 > pcic0: Polling mode > pccard0: on pcic0 > pccard1: on pcic0 > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > plip0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1: configured irq 3 not in bitmap of probed irqs 0 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > unknown: can't assign resources > unknown: can't assign resources > unknown: can't assign resources > unknown: can't assign resources > ad0: 11513MB [23392/16/63] at ata0-master using UDMA33 > acd0: CDROM at ata1-master using PIO4 > Mounting root from ufs:/dev/ad0s1a > pccard: card inserted, slot 0 > logo_saver: no suitable graphics mode <-- here is another problem I have :) > anyone ? > module_register_init: MOD_LOAD (logo_saver, c11d7b3c, 0) error 19 > ed1 at port 0x240-0x25f irq 3 slot 0 on pccard0 > ed1: address 00:00:e8:7f:0f:34, type NE2000 (16 bit) > > -- > -- > =================================================================== > Christophe Prevotaux Email: chris@hexanet.fr > HEXANET SARL URL: http://www.hexanet.fr/ > Z.A Farman Sud Tel: +33 (0)3 26 79 30 05 > 9 rue Roland Coffignot Direct: +33 (0)3 26 79 08 02 > BP415 Fax: +33 (0)3 26 79 30 06 > 51689 Reims Cedex 2 > FRANCE > =================================================================== > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@freebsd.org http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Sep 1 1:16:17 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id CD36937B424; Fri, 1 Sep 2000 01:16:14 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id BAA02219; Fri, 1 Sep 2000 01:30:39 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009010830.BAA02219@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Cc: hardware@freebsd.org Subject: DPT SmartRAID V, VI, Adaptec SCSI RAID driver committed Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 01 Sep 2000 01:30:39 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've just committed a driver for the abovementioned RAID adapter families provided by DPT/Adaptec and the long-suffering Mark Salyzyn. The driver will be maintained by Adaptec, with a little help from yours truly if really necessary. With any luck, we should see the complete set of management tools available from Adaptec shortly to complement this driver, and I'll be backporting to -stable once I'm certain I haven't broken anything with this commit, since the driver's already had a long shakedown period. Thanks to Adaptec, Mark Salyzyn and Justin Gibbs for again being the right person in the right place at the right time. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Sep 1 1:25: 0 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mtiwmhc24.worldnet.att.net (mtiwmhc24.worldnet.att.net [204.127.131.49]) by hub.freebsd.org (Postfix) with ESMTP id ABD8837B43C; Fri, 1 Sep 2000 01:24:54 -0700 (PDT) Received: from 216.neworleans-05-10rs16rt.la.dial-access.att.net ([12.73.250.216]) by mtiwmhc24.worldnet.att.net (InterMail vM.4.01.02.39 201-229-119-122) with SMTP id <20000901082447.JRGO13787.mtiwmhc24.worldnet.att.net@216.neworleans-05-10rs16rt.la.dial-access.att.net>; Fri, 1 Sep 2000 08:24:47 +0000 From: Thrumbar Pathfinder To: freebsd-hardware@FreeBSD.org Cc: arch@FreeBSD.ORG Subject: Auto-Mount/Dismount optional drivers development??? Date: Fri, 01 Sep 2000 03:18:03 -0500 Organization: OmniCorp Interstellar Message-ID: X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I propose the following enhancements to the drivers used in FreeBSD. Pleas do not confuse this with that Supermount (supermount) used in ManDrake Linux as this is different entirely... The ability for storage devices to auto-Mount/DisMount their media in the event that the eject button is pushed on the drive itself without executing the dismount command from terminal or by script.. This would help in the following ways : 1. Security : Drives can be linked to ones Login to allow access to only prescribed drives (Media) due to the drive that is not mounted cannot be accessed (drives units are ghost, assigned their ID's but not allowed to mount when the logged on user is not allowed access to it). The drive will appear on a manager to be hazed out to indicate that it is dismounted... This would be more secure than the current use of scripts or manual commands as the code would be securely in the in the driver code. The drive, if possible can also be set to prevent the insertion of media or the removal of said media (some drives can - at least in their Win doze version - when trying to eject and active disk prompt the user and the user select the ignore option thus preventing the ejection from taking place) if possible. Will have to contact drive suppliers to find out if possible... 2. Integrity : This prevents the mistaken removal of media without dismounting first in the event the manual eject is pressed. =09 This also allows for quick change of media for tape or cd jukeboxes with just a click of the drive icon or cd prompt change... 3. Access (see security) The driver would detect the eject command (from the button being pressed - much like current adaptec DirectCD does on my CD-RW drive) and triggers a detection to check it the media is active Active - either of the following a: cancels dismount b: waits for activity to end - dismounts c: halts activity - dismounts d: prompts for action non Active - dismounts media This is for media that does not use a mechanical ejection (Floppy (1.44) but uses and articulated ejection (electrical as in CD's, Zip, Jazz). Including hot-swapable HD's using swap trays (caddies). There is more ways this could be used, but my brain is falling off and I cannot think anymore so I will leave it with the above in hopes another can add their own.. I most likely will not be able to contribute much as I have trouble even spelling the word programming much less doing it (still learning at beginning level).. Any constructive comments?????? Thrumbar@Worldnet.att.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Sep 1 5:19:54 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from linum.cofc.edu (linum.cofc.edu [153.9.35.19]) by hub.freebsd.org (Postfix) with ESMTP id 13A0D37B422 for ; Fri, 1 Sep 2000 05:19:52 -0700 (PDT) Received: (from astrand@localhost) by linum.cofc.edu (8.11.0/8.9.3) id e81CJmA06967; Fri, 1 Sep 2000 08:19:48 -0400 (EDT) (envelope-from astrand) To: Allan Strand Subject: Re: Problems mounting ATAPI-CDROM under 4.1-stable Cc: freebsd-hardware@freebsd.org From: Allan Strand Date: 01 Sep 2000 08:19:48 -0400 In-Reply-To: Allan Strand's message of "Wed, 30 Aug 2000 09:43:18 -0400" Message-ID: <86r974cniz.fsf@linum.cofc.edu> Lines: 72 User-Agent: Gnus/5.070084 (Pterodactyl Gnus v0.84) XEmacs/20.4 (Emerald) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I apologize if this is inappropriate, but I posted this message to "questions" a couple of days ago and received no response. I'm flummoxed at the moment. Does anybody have a suggestion? Thanks, a. Allan Strand writes: > Hi, > > I am having problems mounting my ATAPI CD-RW as a filesystem. > > Previously, using the same hardware setup under FBSD 3.4, I was able > to get the CD-RW to work fine. > > Hardware: ASUS P5A > two IDE drives master and slave on the first IDE controller. > One CD-RW as master on the second controller. > > Here are the relevant lines from dmesg: > > ata1-slave: ata_command: timeout waiting for intr > ata1-slave: identify failed > ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable > ad0: 8056MB [16368/16/63] at ata0-master using UDMA33 > ad1: 9671MB [19650/16/63] at ata0-slave using UDMA33 > acd0: CD-RW at ata1-master using WDMA2 > > I have the BIOS set to no slave on IDE2 so I don't totally understand > the first two lines above. > > The CD drive does play and rip audio CDs and it also will burn data > disks. It just does not mount data disks as filesystems. > > I use the following command: mount -t cd9660 /dev/acd0a /cdrom > > when I execute this command I get the following errors sent to the > console log: > > acd0: READ_BIG command timeout - resetting > ata1: resetting devices .. ata1-master: Aladdin: two atapi devices on this channel, no DMA > ata1-master: timeout waiting for command=ef s=d0 e=60 > done > ata1-master: timeout waiting to give command=a0 s=d0 e=60 > acd0: failure to send ATAPI packet command > acd0: failure to execute ATAPI packet command > > > I'm clueless as to why I'm getting the two devices portion of the > error. Actually, I'm just generally clueless about this whole problem > (obvious). > > Can anyone give me any pointers? > > Cheers, > a. > -- > Allan Strand, Biology http://linum.cofc.edu > College of Charleston Ph. (843) 953-8085 > Charleston, SC 29424 Fax (843) 953-5453 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Allan Strand, Biology http://linum.cofc.edu College of Charleston Ph. (843) 953-8085 Charleston, SC 29424 Fax (843) 953-5453 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Sep 1 6: 5:14 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 8743437B422; Fri, 1 Sep 2000 06:05:09 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id JAA38677; Fri, 1 Sep 2000 09:05:07 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 1 Sep 2000 09:05:07 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Thrumbar Pathfinder Cc: freebsd-hardware@FreeBSD.org, arch@FreeBSD.org Subject: Re: Auto-Mount/Dismount optional drivers development??? 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 You can imagine the decisions and resulting activities, in the case of removable media, being made in a userland daemon listening for device events. I guess the pertinent question then is, what is the best way in which to deliver this sort of event information to userland processes? To what extent can this event stream be abstracted so as to not represent driver-specific events ("cdrom device (whatever) was ejected" in a cdrom schema as opposed to something acd-specific), and should it be extensible to allow the representing of driver-specific events. Polling for device availability in userland seems like a less pretty solution. Right now, devices in /devfs appear based on whether or not the drive is available, not media. I wonder if there would be an appropriate way for events to be notified via a combination of kqueue() and devfs nodes? Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Sep 1 11: 2:24 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.siscom.net (mail.siscom.net [209.251.2.99]) by hub.freebsd.org (Postfix) with SMTP id ACEA737B424 for ; Fri, 1 Sep 2000 11:02:22 -0700 (PDT) Received: (qmail 64251 invoked from network); 1 Sep 2000 18:02:12 -0000 Received: from mp.siscom.net (HELO jason) (209.251.2.49) by mail.siscom.net with SMTP; 1 Sep 2000 18:02:12 -0000 Message-ID: <057101c01440$2b5001e0$3102fbd1@siscom.net> From: "Robert J. Adams" To: Subject: mobo that will support 8 IDE? Date: Fri, 1 Sep 2000 13:21:29 -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 Hello all, Anyone happen to know of a motherboard that will support 8 IDE drives? -Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Sep 1 11:53:31 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.milw.twtelecom.net (ins1.milw.twtelecom.net [216.136.95.3]) by hub.freebsd.org (Postfix) with ESMTP id 8DF0137B43E for ; Fri, 1 Sep 2000 11:53:29 -0700 (PDT) Received: from inc.net (niki.pwke.twtelecom.net [207.250.66.46]) by mail.milw.twtelecom.net (Postfix) with ESMTP id 5712B3303F for ; Fri, 1 Sep 2000 13:53:24 -0500 (CDT) Message-ID: <39AFFA87.E86684D5@inc.net> Date: Fri, 01 Sep 2000 13:50:47 -0500 From: Steve Kaczkowski Organization: Time Warner Telecom - IDD X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: hardware@freebsd.org Subject: 3ware anyone ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hey all, Wondering if anyone out there is using a 3ware IDE RAID card (Specifically the Escalade 6400) in a fault-tolerant setup? Doing some searching through the list archives it seems that the drivers are pretty solid but I still have a couple questions. First off, is the array bootable without much messing around? Is it as simple as setting up the metadevice then going through the normal FBSD install and it's done or are there some gotchas I need to know about? Secondly, how well does the system's 'RAID-10' work? I realize it's not RAID-5, but from the info they have on their site it seems that it has the same kind of functionality. Does the auto rebuild and hot sparing work as expected, anything weird there? Lastly, how well does the entire system work, throughput OK, any data corruption and just generally would you recommend it? For $250 for the 4 port ATA/66 card and with 60 gig disks coming in around $200 it's REALLY hard to pass it up, I just hate being a beta tester.. :) Looking for any and all info.. Thanks in advance everyone! -- Steve Kaczkowski Time Warner Telecom IDD steve@inc.net (414)908-9012 http://www.inc.net (603)737-9209 Fax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Sep 1 13:44:26 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 5F4FE37B422 for ; Fri, 1 Sep 2000 13:44:23 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id NAA06031; Fri, 1 Sep 2000 13:58:44 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009012058.NAA06031@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Steve Kaczkowski Cc: hardware@freebsd.org Subject: Re: 3ware anyone ? In-reply-to: Your message of "Fri, 01 Sep 2000 13:50:47 CDT." <39AFFA87.E86684D5@inc.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 01 Sep 2000 13:58:44 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Wondering if anyone out there is using a 3ware IDE RAID card > (Specifically the Escalade 6400) in a fault-tolerant setup? Doing > some searching through the list archives it seems that the drivers > are pretty solid but I still have a couple questions. > > First off, is the array bootable without much messing around? Is it as > simple as setting up the metadevice then going through the normal FBSD > install and it's done or are there some gotchas I need to know about? I've had some reports of problems in RAID10 mode, where the array doesn't like being installed onto until it's finished building itself out. I'm working on that at the moment. > Secondly, how well does the system's 'RAID-10' work? I realize it's not > RAID-5, but from the info they have on their site it seems that it has > the same kind of functionality. Does the auto rebuild and hot sparing > work as expected, anything weird there? Obviously I've beaten up on it quite a bit, and it does behave pretty much "as expected". > Lastly, how well does the entire system work, throughput OK, any > data corruption and just generally would you recommend it? If you have a little time to spend familiarising yourself with the controller and how it "feels", I'd definitely recommend it. > For $250 for the 4 port ATA/66 card and with 60 gig disks coming > in around $200 it's REALLY hard to pass it up, I just hate being > a beta tester.. :) Well, the driver's pretty new, and the whole ATA RAID thing is a bit of a new concept in some ways, so there's still a little beta-tester pain going around. If you can deal with a small amount of that, and are willing to provide reasonable problem reports so that things can be fixed quickly, I'd say you'll be fine. And as you note, the cost issues are quite compelling. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Sep 1 23:42: 7 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from sanson.reyes.somos.net (freyes.static.inch.com [216.223.199.224]) by hub.freebsd.org (Postfix) with ESMTP id 546CC37B424; Fri, 1 Sep 2000 23:42:03 -0700 (PDT) Received: from tomasa (tomasa.reyes.somos.net [10.0.0.11]) by sanson.reyes.somos.net (8.9.3/8.9.3) with SMTP id CAA62757; Sat, 2 Sep 2000 02:33:51 -0400 (EDT) (envelope-from fran@reyes.somos.net) Message-Id: <200009020633.CAA62757@sanson.reyes.somos.net> From: "Francisco Reyes" To: "Mike Smith" , "Steve Kaczkowski" Cc: "hardware@FreeBSD.ORG" Date: Sat, 02 Sep 2000 02:40:15 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 98 (4.10.2222) In-Reply-To: <200009012058.NAA06031@mass.osd.bsdi.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: 3ware anyone ? Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 01 Sep 2000 13:58:44 -0700, Mike Smith wrote: >> Wondering if anyone out there is using a 3ware IDE RAID card >> (Specifically the Escalade 6400) in a fault-tolerant setup? Setting one up this Sunday. Will report back. >I've had some reports of problems in RAID10 mode, where the array doesn't >like being installed onto until it's finished building itself out. I'm >working on that at the moment. Mike can you expand on this? What do you mean by "until it's finished building itself out"? If I do the Alt+3 and do the partitions and wait until all is initialized and then try the FreeBSD install would I be ok? For the machine I am setting up Sunday I am doing Raid 0 (2 drives) and Raid 1 (another 2 drives) so this "issue" won't affect me yet, but I have a machine on order where I was planning on doing Raid 10. >willing to provide reasonable problem reports so that things can be fixed >quickly, I'd say you'll be fine. Mike anything you would like me to try? Any recommended benchmarks? I plan to do a bonnie on the machine before and after RAID, but I am wondering if there is any other good test(s). francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Sep 2 15:49: 0 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id 835BF37B42C for ; Sat, 2 Sep 2000 15:48:57 -0700 (PDT) Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by smtp1.sentex.ca (8.11.0/8.11.0) with ESMTP id e82MmuT24215; Sat, 2 Sep 2000 18:48:56 -0400 (EDT) Received: from chimp.simianscience.com (cage.simianscience.com [64.7.134.1]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id SAA17793; Sat, 2 Sep 2000 18:48:56 -0400 (EDT) From: mike@sentex.net (Mike Tancsa) To: fran@reyes.somos.net ("Francisco Reyes") Cc: hardware@FreeBSD.ORG Subject: Re: 3ware anyone ? Date: Sat, 02 Sep 2000 22:43:32 GMT Message-ID: <39b1821a.943974072@mail.sentex.net> References: <200009012058.NAA06031@mass.osd.bsdi.com> In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 2 Sep 2000 02:42:13 -0400, in sentex.lists.freebsd.hardware you wrote: What sorts of speeds are you getting with RAID 1 and 10 ? I gave up on the card for that configuration because it was incredibly slow. RAID 0 is great, but I was quite disappointed in the speed of the mirror. What sort of results do you get with bonnie ? ---Mike >On Fri, 01 Sep 2000 13:58:44 -0700, Mike Smith wrote: > >>> Wondering if anyone out there is using a 3ware IDE RAID card >>> (Specifically the Escalade 6400) in a fault-tolerant setup? > >Setting one up this Sunday. >Will report back. > > >>I've had some reports of problems in RAID10 mode, where the array doesn't >>like being installed onto until it's finished building itself out. I'm >>working on that at the moment. > >Mike can you expand on this? >What do you mean by "until it's finished building itself out"? >If I do the Alt+3 and do the partitions and wait until all is >initialized and then >try the FreeBSD install would I be ok? > >For the machine I am setting up Sunday I am doing Raid 0 (2 >drives) and Raid 1 (another 2 drives) >so this "issue" won't affect me yet, but I have a machine on >order where I was planning on doing Raid 10. > > >>willing to provide reasonable problem reports so that things can be fixed >>quickly, I'd say you'll be fine. > >Mike anything you would like me to try? >Any recommended benchmarks? >I plan to do a bonnie on the machine before and after RAID, but >I am wondering >if there is any other good test(s). Mike Tancsa (mdtancsa@sentex.net) Sentex Communications Corp, Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers could setup a national IP network." (KDW2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message