From owner-freebsd-hardware Sun Apr 12 04:14:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA22755 for freebsd-hardware-outgoing; Sun, 12 Apr 1998 04:14:35 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dog.farm.org (gw-hssi-2.farm.org [209.66.103.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA22744 for ; Sun, 12 Apr 1998 04:14:32 -0700 (PDT) (envelope-from dog.farm.org!dk) Received: (from dk@localhost) by dog.farm.org (8.7.5/dk#3) id EAA13652; Sun, 12 Apr 1998 04:15:13 -0700 (PDT) Message-ID: <19980412041512.21011@dog.farm.org> Date: Sun, 12 Apr 1998 04:15:12 -0700 From: Dmitry Kohmanyuk =?KOI8-R?B?5M3J1NLJyiDrz8jNwc7Ayw==?= To: freebsd-hardware@FreeBSD.ORG Subject: dual-PII ATX motherboard with lots of slots?? Reply-To: dk+@ua.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e X-Class: Fast X-OS-Used: FreeBSD 2.2-960501-SNAP X-NIC-Handle: DK379 X-Pager-Email: dk@interpage.net Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hello everybody, is there any dual-PII motherboard made with ATX form factor and more than 5 PCI (or 4 PCI + 1 AGP) and 2 ISA slots (of which 1 slot is physically shared)? (In other words, I want something better than ASUS P2L97DS I have.) thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 13 20:04:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01089 for freebsd-hardware-outgoing; Mon, 13 Apr 1998 20:04:24 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from back1.hiper.net (back1.hiper.net [207.137.172.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA01078 for ; Tue, 14 Apr 1998 03:04:15 GMT (envelope-from randyk@ccsales.com) Received: from ntrkcasa (pool42.hiper.net [207.137.172.42]) by back1.hiper.net (8.8.7/8.8.7) with SMTP id UAA06516 for ; Mon, 13 Apr 1998 20:05:14 -0700 (PDT) (envelope-from randyk@ccsales.com) Message-Id: <3.0.5.32.19980413200252.02fdd100@ccsales.com> X-Sender: randyk@ccsales.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 13 Apr 1998 20:02:52 -0700 To: freebsd-hardware@FreeBSD.ORG From: "Randy A. Katz" Subject: 3Com 3C509B-TX In-Reply-To: <19980412041512.21011@dog.farm.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Are the 3Com 3C509B-TX's supported on RELEASE 2.2.6? Thanx, Randy Katz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 14 12:38:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25887 for freebsd-hardware-outgoing; Tue, 14 Apr 1998 12:38:55 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from monk.via.net (monk.via.net [209.81.9.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA25877 for ; Tue, 14 Apr 1998 19:38:48 GMT (envelope-from joe@via.net) Received: (from joe@localhost) by monk.via.net (8.6.11/8.6.12) id MAA06617 for hardware@freebsd.org; Tue, 14 Apr 1998 12:38:39 -0700 Date: Tue, 14 Apr 1998 12:38:39 -0700 From: Joe McGuckin Message-Id: <199804141938.MAA06617@monk.via.net> To: hardware@FreeBSD.ORG Subject: DEC Ultra HiNote 2000 laptop ? X-Sun-Charset: US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I was spammed with an offer to purchase these laptops for $3500. (4G disk, 32M ram, 233Mhz cpu, 14.1" XGA TFT LCD (1024x768)) Normally I would delete the msg, but I happen to think the Ultra 2000's are really nice. They are very thin and weight about 6 lbs. Has anyone had success running FreeBSD and X on one of these? Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 14 13:39:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09175 for freebsd-hardware-outgoing; Tue, 14 Apr 1998 13:39:28 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ns.mexcom.net (ver2-121.uninet.net.mx [200.38.135.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08847 for ; Tue, 14 Apr 1998 20:37:43 GMT (envelope-from eculp@ver1.telmex.net.mx) Received: from sunix (telmex@sunix.mexcom.net [206.103.64.3]) by ns.mexcom.net (8.8.8/8.8.7) with SMTP id PAA11968 for ; Tue, 14 Apr 1998 15:34:21 -0500 (CDT) Message-ID: <3533CA3B.397E52D5@ver1.telmex.net.mx> Date: Tue, 14 Apr 1998 15:42:36 -0500 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.14 i586) MIME-Version: 1.0 To: freebsd-hardware@FreeBSD.ORG Subject: Mitsubishi MCA-CDRW 226 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I bought a Mitsubishi MCA CDRW 226, thinking that it being SCSI everything would be routine:-) and my dmesg was what I expected: ahc0: rev 0x01 int a irq 10 on pci0.15.0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs scbus0 at ahc0 bus 0 ahc0:A:3: refuses WIDE negotiation. Using 8bit transfers cd0 at scbus0 target 3 lun 0 cd0: type 5 removable SCSI 2 cd0: CD-ROM can't get the size I mounted a cd on /tmp and worked perfectly so I decided to burn disk1 of Sunday's cvsup and make release. # cdrecord dev=0,3,0 test.raw Cdrecord release 1.6a12 Copyright (C) 1995-1998 Jvrg Schilling Bad system call (core dumped) I tried most of the drivers with the same results. I read "at" the manual and tried # cdrecord -scanbus Cdrecord release 1.6a12 Copyright (C) 1995-1998 Jvrg Schilling cdrecord: No target found. Does anyone know ir there is a problem with this drive? Thanks ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 14 15:44:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06351 for freebsd-hardware-outgoing; Tue, 14 Apr 1998 15:44:07 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06297 for ; Tue, 14 Apr 1998 22:43:57 GMT (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id PAA01195; Tue, 14 Apr 1998 15:40:17 -0700 (PDT) Message-Id: <199804142240.PAA01195@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Edwin Culp cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Mitsubishi MCA-CDRW 226 In-reply-to: Your message of "Tue, 14 Apr 1998 15:42:36 CDT." <3533CA3B.397E52D5@ver1.telmex.net.mx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Apr 1998 15:40:16 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I bought a Mitsubishi MCA CDRW 226, thinking that it being SCSI > everything would be routine:-) and my dmesg was what I expected: > > ahc0: rev 0x01 int a irq 10 on > pci0.15.0 > ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs > scbus0 at ahc0 bus 0 > ahc0:A:3: refuses WIDE negotiation. Using 8bit transfers > cd0 at scbus0 target 3 lun 0 > cd0: type 5 removable SCSI 2 > cd0: CD-ROM can't get the size > > I mounted a cd on /tmp and worked perfectly so I decided to > burn disk1 of Sunday's cvsup and make release. > > # cdrecord dev=0,3,0 test.raw > Cdrecord release 1.6a12 Copyright (C) 1995-1998 Jvrg Schilling > Bad system call (core dumped) > > I tried most of the drivers with the same results. > > I read "at" the manual and tried > > # cdrecord -scanbus > Cdrecord release 1.6a12 Copyright (C) 1995-1998 Jvrg Schilling > cdrecord: No target found. > > Does anyone know ir there is a problem with this drive? It doesn't sound like a problem with the drive, although the documentation doesn't indicate that the drive in question is supported. The 'bad system call' message is pretty ugly though; without knowing what the system call was it's hard to understand what's going on. You're not running CAM, I presume? Did you build cdrecord from source, or just install the package? If the latter, did you get the package from the 2.2 or -current collection? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 14 16:39:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA17279 for freebsd-hardware-outgoing; Tue, 14 Apr 1998 16:39:26 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ns.mexcom.net (ver2-121.uninet.net.mx [200.38.135.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA16871 for ; Tue, 14 Apr 1998 23:37:40 GMT (envelope-from eculp@ver1.telmex.net.mx) Received: from sunix (telmex@sunix.mexcom.net [206.103.64.3]) by ns.mexcom.net (8.8.8/8.8.7) with SMTP id SAA13818; Tue, 14 Apr 1998 18:34:25 -0500 (CDT) Message-ID: <3533F470.1B0807C2@ver1.telmex.net.mx> Date: Tue, 14 Apr 1998 18:42:40 -0500 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.14 i586) MIME-Version: 1.0 To: Mike Smith CC: freebsd-hardware@FreeBSD.ORG Subject: Re: Mitsubishi MCA-CDRW 226 References: <199804142240.PAA01195@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith wrote: > > > I bought a Mitsubishi MCA CDRW 226, thinking that it being SCSI > > everything would be routine:-) and my dmesg was what I expected: > > > > ahc0: rev 0x01 int a irq 10 on > > pci0.15.0 > > ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs > > scbus0 at ahc0 bus 0 > > ahc0:A:3: refuses WIDE negotiation. Using 8bit transfers > > cd0 at scbus0 target 3 lun 0 > > cd0: type 5 removable SCSI 2 > > cd0: CD-ROM can't get the size > > > > I mounted a cd on /tmp and worked perfectly so I decided to > > burn disk1 of Sunday's cvsup and make release. > > > > # cdrecord dev=0,3,0 test.raw > > Cdrecord release 1.6a12 Copyright (C) 1995-1998 Jvrg Schilling > > Bad system call (core dumped) > > > > I tried most of the drivers with the same results. > > > > I read "at" the manual and tried > > > > # cdrecord -scanbus > > Cdrecord release 1.6a12 Copyright (C) 1995-1998 Jvrg Schilling > > cdrecord: No target found. > > > > Does anyone know ir there is a problem with this drive? > > It doesn't sound like a problem with the drive, although the > documentation doesn't indicate that the drive in question is supported. > > The 'bad system call' message is pretty ugly though; without knowing > what the system call was it's hard to understand what's going on. > > You're not running CAM, I presume? Did you build cdrecord from source, > or just install the package? If the latter, did you get the package > from the 2.2 or -current collection? No not using CAM. Installed cdrecord from ports current version 1.6a12. Thanks ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 14 16:53:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20773 for freebsd-hardware-outgoing; Tue, 14 Apr 1998 16:53:02 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA20747 for ; Tue, 14 Apr 1998 23:52:51 GMT (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id QAA01470; Tue, 14 Apr 1998 16:48:50 -0700 (PDT) Message-Id: <199804142348.QAA01470@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Edwin Culp cc: Mike Smith , freebsd-hardware@FreeBSD.ORG Subject: Re: Mitsubishi MCA-CDRW 226 In-reply-to: Your message of "Tue, 14 Apr 1998 18:42:40 CDT." <3533F470.1B0807C2@ver1.telmex.net.mx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Apr 1998 16:48:50 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Mike Smith wrote: > > > > > I bought a Mitsubishi MCA CDRW 226, thinking that it being SCSI > > > everything would be routine:-) and my dmesg was what I expected: > > > > > > ahc0: rev 0x01 int a irq 10 on > > > pci0.15.0 > > > ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs > > > scbus0 at ahc0 bus 0 > > > ahc0:A:3: refuses WIDE negotiation. Using 8bit transfers > > > cd0 at scbus0 target 3 lun 0 > > > cd0: type 5 removable SCSI 2 > > > cd0: CD-ROM can't get the size > > > > > > I mounted a cd on /tmp and worked perfectly so I decided to > > > burn disk1 of Sunday's cvsup and make release. > > > > > > # cdrecord dev=0,3,0 test.raw > > > Cdrecord release 1.6a12 Copyright (C) 1995-1998 Jvrg Schilling > > > Bad system call (core dumped) > > > > > > I tried most of the drivers with the same results. > > > > > > I read "at" the manual and tried > > > > > > # cdrecord -scanbus > > > Cdrecord release 1.6a12 Copyright (C) 1995-1998 Jvrg Schilling > > > cdrecord: No target found. > > > > > > Does anyone know ir there is a problem with this drive? > > > > It doesn't sound like a problem with the drive, although the > > documentation doesn't indicate that the drive in question is supported. > > > > The 'bad system call' message is pretty ugly though; without knowing > > what the system call was it's hard to understand what's going on. > > > > You're not running CAM, I presume? Did you build cdrecord from source, > > or just install the package? If the latter, did you get the package > > from the 2.2 or -current collection? > > No not using CAM. Installed cdrecord from ports current version 1.6a12. "ports current"? You mean packages-current? Are you on -stable or -current? I ask simply because the only reasonable source of "bad system call" I can think of is running a binary built on a -current system on a -stable system. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 14 16:57:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22075 for freebsd-hardware-outgoing; Tue, 14 Apr 1998 16:57:47 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ns.mexcom.net (ver2-121.uninet.net.mx [200.38.135.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA21592 for ; Tue, 14 Apr 1998 23:55:49 GMT (envelope-from eculp@ver1.telmex.net.mx) Received: from sunix (telmex@sunix.mexcom.net [206.103.64.3]) by ns.mexcom.net (8.8.8/8.8.7) with SMTP id SAA14034; Tue, 14 Apr 1998 18:52:44 -0500 (CDT) Message-ID: <3533F8BA.6D8A6085@ver1.telmex.net.mx> Date: Tue, 14 Apr 1998 19:00:58 -0500 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.14 i586) MIME-Version: 1.0 To: Mike Smith CC: freebsd-hardware@FreeBSD.ORG Subject: Re: Mitsubishi MCA-CDRW 226 References: <199804142348.QAA01470@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith wrote: > > > Mike Smith wrote: > > > > > > > I bought a Mitsubishi MCA CDRW 226, thinking that it being SCSI > > > > everything would be routine:-) and my dmesg was what I expected: > > > > > > > > ahc0: rev 0x01 int a irq 10 on > > > > pci0.15.0 > > > > ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs > > > > scbus0 at ahc0 bus 0 > > > > ahc0:A:3: refuses WIDE negotiation. Using 8bit transfers > > > > cd0 at scbus0 target 3 lun 0 > > > > cd0: type 5 removable SCSI 2 > > > > cd0: CD-ROM can't get the size > > > > > > > > I mounted a cd on /tmp and worked perfectly so I decided to > > > > burn disk1 of Sunday's cvsup and make release. > > > > > > > > # cdrecord dev=0,3,0 test.raw > > > > Cdrecord release 1.6a12 Copyright (C) 1995-1998 Jvrg Schilling > > > > Bad system call (core dumped) > > > > > > > > I tried most of the drivers with the same results. > > > > > > > > I read "at" the manual and tried > > > > > > > > # cdrecord -scanbus > > > > Cdrecord release 1.6a12 Copyright (C) 1995-1998 Jvrg Schilling > > > > cdrecord: No target found. > > > > > > > > Does anyone know ir there is a problem with this drive? > > > > > > It doesn't sound like a problem with the drive, although the > > > documentation doesn't indicate that the drive in question is supported. > > > > > > The 'bad system call' message is pretty ugly though; without knowing > > > what the system call was it's hard to understand what's going on. > > > > > > You're not running CAM, I presume? Did you build cdrecord from source, > > > or just install the package? If the latter, did you get the package > > > from the 2.2 or -current collection? > > > > No not using CAM. Installed cdrecord from ports current version 1.6a12. > > "ports current"? You mean packages-current? Are you on -stable or > -current? I ask simply because the only reasonable source of "bad > system call" I can think of is running a binary built on a -current > system on a -stable system. Unfortunately it is current/current as of Sunday. New cvsup and Make world. Thanks ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 14 18:09:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05326 for freebsd-hardware-outgoing; Tue, 14 Apr 1998 18:09:15 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from soran.pacific.net.sg (soran.pacific.net.sg [203.120.90.76]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA05308; Wed, 15 Apr 1998 01:09:04 GMT (envelope-from accel@pacific.net.sg) Received: from pop2.pacific.net.sg (pop2.pacific.net.sg [203.120.90.86]) by soran.pacific.net.sg with ESMTP id JAA08837; Wed, 15 Apr 1998 09:04:18 +0800 (SGT) Received: from [210.24.118.47] (dyn118ppp47.pacific.net.sg [210.24.118.47]) by pop2.pacific.net.sg with ESMTP id JAA13094; Wed, 15 Apr 1998 09:08:59 +0800 (SGT) X-Sender: accel@pacific.net.sg (Unverified) Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 15 Apr 1998 09:05:44 +0800 To: hardware@FreeBSD.ORG, questions@FreeBSD.ORG From: Richard Goh Subject: FreeBSD on Solid-StateDisk Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I am running freebsd 2.2.5 on an industrial pc. Due to high temperature and vibration, would like to replace the harddisk with a solid state one. Can this be done? Anyone experienced with this? Thanks for any info. Rgds, Goh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 14 18:21:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08038 for freebsd-hardware-outgoing; Tue, 14 Apr 1998 18:21:50 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA08007; Wed, 15 Apr 1998 01:21:40 GMT (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id SAA01716; Tue, 14 Apr 1998 18:18:52 -0700 (PDT) Message-Id: <199804150118.SAA01716@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Richard Goh cc: hardware@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: FreeBSD on Solid-StateDisk In-reply-to: Your message of "Wed, 15 Apr 1998 09:05:44 +0800." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Apr 1998 18:18:52 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi, > I am running freebsd 2.2.5 on an industrial pc. > Due to high temperature and vibration, would like to replace the harddisk > with a solid state one. > Can this be done? Yes. > Anyone experienced with this? Yes. > Thanks for any info. If you're running a reasonably cut-down system, I suggest that you look at PicoBSD and one of the flash cards that emulate a floppy drive or harddisk at the BIOS level. You won't be able to read/write the disk once FreeBSD has booted though, but this is often OK for embedded applications. If you need rewritable storage, there are solid-state disks available both using flash and battery-backed DRAM. Owing to the behaviour of the BSD filesystem, you may find that flash disks have an unacceptably short lifetime (50-100,000 write cycles). See http://www.indcompsrc.com/products/drives/home.html for some examples (ICS are expensive, you will be able to do better elsewhere if you can find other suppliers). FreeBSD does not have flash filesystem support at this time. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 14 19:01:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16981 for freebsd-hardware-outgoing; Tue, 14 Apr 1998 19:01:01 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ns.mexcom.net (ver2-121.uninet.net.mx [200.38.135.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16144 for ; Wed, 15 Apr 1998 01:58:17 GMT (envelope-from eculp@ver1.telmex.net.mx) Received: from sunix (telmex@sunix.mexcom.net [206.103.64.3]) by ns.mexcom.net (8.8.8/8.8.7) with SMTP id UAA15313; Tue, 14 Apr 1998 20:55:19 -0500 (CDT) Message-ID: <35341576.55BF3975@ver1.telmex.net.mx> Date: Tue, 14 Apr 1998 21:03:34 -0500 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.14 i586) MIME-Version: 1.0 To: Mike Smith , freebsd-hardware@FreeBSD.ORG Subject: Re: Mitsubishi MCA-CDRW 226 References: <199804142348.QAA01470@dingo.cdrom.com> <3533F8BA.6D8A6085@ver1.telmex.net.mx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike, Thanks a lot. It works fine. There were two problems. 1. cdrecord 1.6a12 compiled with current would always give the bad system call. I changed it to one compiled with 2.2.6 and the bad system call went away. 2. You also have to do a s/link from /dev/cd0c to /dev/scgx and everything is beautiful. I burned and tested FreeBSD cdrom set with no problems. Thanks again. ed P.D. We can add the MCA-CDRW 226 from mitsubishi to the good list. Edwin Culp wrote: > > Mike Smith wrote: > > > > > Mike Smith wrote: > > > > > > > > > I bought a Mitsubishi MCA CDRW 226, thinking that it being SCSI > > > > > everything would be routine:-) and my dmesg was what I expected: > > > > > > > > > > ahc0: rev 0x01 int a irq 10 on > > > > > pci0.15.0 > > > > > ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs > > > > > scbus0 at ahc0 bus 0 > > > > > ahc0:A:3: refuses WIDE negotiation. Using 8bit transfers > > > > > cd0 at scbus0 target 3 lun 0 > > > > > cd0: type 5 removable SCSI 2 > > > > > cd0: CD-ROM can't get the size > > > > > > > > > > I mounted a cd on /tmp and worked perfectly so I decided to > > > > > burn disk1 of Sunday's cvsup and make release. > > > > > > > > > > # cdrecord dev=0,3,0 test.raw > > > > > Cdrecord release 1.6a12 Copyright (C) 1995-1998 Jvrg Schilling > > > > > Bad system call (core dumped) > > > > > > > > > > I tried most of the drivers with the same results. > > > > > > > > > > I read "at" the manual and tried > > > > > > > > > > # cdrecord -scanbus > > > > > Cdrecord release 1.6a12 Copyright (C) 1995-1998 Jvrg Schilling > > > > > cdrecord: No target found. > > > > > > > > > > Does anyone know ir there is a problem with this drive? > > > > > > > > It doesn't sound like a problem with the drive, although the > > > > documentation doesn't indicate that the drive in question is supported. > > > > > > > > The 'bad system call' message is pretty ugly though; without knowing > > > > what the system call was it's hard to understand what's going on. > > > > > > > > You're not running CAM, I presume? Did you build cdrecord from source, > > > > or just install the package? If the latter, did you get the package > > > > from the 2.2 or -current collection? > > > > > > No not using CAM. Installed cdrecord from ports current version 1.6a12. > > > > "ports current"? You mean packages-current? Are you on -stable or > > -current? I ask simply because the only reasonable source of "bad > > system call" I can think of is running a binary built on a -current > > system on a -stable system. > > Unfortunately it is current/current as of Sunday. New cvsup and Make > world. > > Thanks > > ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 14 21:05:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10019 for freebsd-hardware-outgoing; Tue, 14 Apr 1998 21:05:40 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [205.162.1.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA09860; Wed, 15 Apr 1998 04:05:25 GMT (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id VAA11981; Tue, 14 Apr 1998 21:04:42 -0700 (PDT) Date: Tue, 14 Apr 1998 21:04:42 -0700 (PDT) From: Jim Shankland Message-Id: <199804150404.VAA11981@biggusdiskus.flyingfox.com> To: accel@pacific.net.sg, mike@smith.net.au Subject: Re: FreeBSD on Solid-StateDisk Cc: hardware@FreeBSD.ORG, questions@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org See also http://www.adtron.com/sddaover.htm, and http://www.sandisk.com for the flash cards. Jim Shankland Flying Fox Computer Systems, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 14 21:22:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12644 for freebsd-hardware-outgoing; Tue, 14 Apr 1998 21:22:13 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from gatekeeper.alcatel.com.au (gatekeeper.alcatel.com.au [203.17.66.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA12614 for ; Wed, 15 Apr 1998 04:21:43 GMT (envelope-from Peter.Jeremy@alcatel.com.au) Received: from mfg1.cim.alcatel.com.au ([139.188.23.1]) by gatekeeper.alcatel.com.au (PMDF V5.1-7 #U2695) with ESMTP id <01IVWGIDLWIO000NVD@gatekeeper.alcatel.com.au> for freebsd-hardware@FreeBSD.ORG; Wed, 15 Apr 1998 14:20:14 +1000 Received: from cbd.alcatel.com.au by cim.alcatel.com.au (PMDF V5.1-10 #23324) with ESMTP id <01IVWGIAF5V4C2JOJS@cim.alcatel.com.au>; Wed, 15 Apr 1998 14:20:10 +1000 Received: from gsms01.alcatel.com.au by cbd.alcatel.com.au (PMDF V5.1-7 #U2695) with ESMTP id <01IVWGI7W69CAZTRET@cbd.alcatel.com.au>; Wed, 15 Apr 1998 14:20:06 +1100 Received: (from jeremyp@localhost) by gsms01.alcatel.com.au (8.8.8/8.7.3) id OAA24462; Wed, 15 Apr 1998 14:20:04 +1000 (EST) Date: Wed, 15 Apr 1998 14:20:04 +1000 (EST) From: Peter Jeremy Subject: Re: FreeBSD on Solid-StateDisk To: freebsd-hardware@FreeBSD.ORG Cc: accel@pacific.net.sg Message-id: <199804150420.OAA24462@gsms01.alcatel.com.au> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 15 Apr 1998 09:05:44 +0800, Richard Goh wrote: >Due to high temperature and vibration, would like to replace the harddisk >with a solid state one. >Can this be done? Yes. >Anyone experienced with this? I haven't used them personally, but Seagate make a range of solid state disks. Other drive vendors might as well. I thought they included SCSI ones, but I can only find IPI (or flashcard) interfaces. These just appear as a fast harddisk to the system. Since you mention temperature, you should be aware that the DRAM-based disks dissipate lots of power. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 14 23:27:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06694 for freebsd-hardware-outgoing; Tue, 14 Apr 1998 23:27:14 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from hermes.iaccess.com.au (hermes.iaccess.com.au [203.5.74.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA06672; Wed, 15 Apr 1998 06:26:59 GMT (envelope-from phil@iaccess.com.au) Received: from Quest (quest.iaccess.com.au [203.5.74.224]) by hermes.iaccess.com.au (8.8.5/8.8.5) with SMTP id QAA28045; Wed, 15 Apr 1998 16:26:54 +1000 (EST) Message-Id: <2.2.32.19980415062956.007691f0@iaccess.com.au> X-Sender: phil@iaccess.com.au X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 15 Apr 1998 16:29:56 +1000 To: freebsd-install@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG From: Phillip Krokidis Subject: Network Card problems Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, We are trying to install an SMC8216 [SMC9432TX] pci card on Freebsd2.2.5 but not having much luck. When the machine boots the message "no driver assigned" appears. There is a line in the kernel source that allows configuring ed0 for ISA but doesnt seem to work for PCI. We want to be able to connect this machine to a 100 mb ethernet port. We may need to connect it at times to a 10 mb port. We need a 10/100 mb network card supported by freebsd. Can anyone recommend a card. Even a 100 mb only card for now. Is it a config issue or a hardware issue. Thanks, Phil. ---------------------------------------------------------------- Phillip Krokidis Tel: +61 3 9686 6677 Network Manager Fax: +61 3 9686 6644 Internet Access Australia Email: phil@iaccess.com.au http://www.iaccess.com.au Melbourne,Sydney,Adelaide,Brisbane,Canberra,Perth,Geelong GoldCoast,Bendigo,Bridgewater,Harcourt,Goornong,Laanecoorie Axedale,Central Coast, Ballarat and surrounding areas: (Bacchus Marsh, Trentham, Myrnlong, Greendale, Rowsley and other areas through to Ballan. Clunes, Daylesford, Eganstown, Kingston Areas through to Creswick) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 15 04:01:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26959 for freebsd-hardware-outgoing; Wed, 15 Apr 1998 04:01:24 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from solaric.UkrCard.COM (ukrcard-gu.gu.net [194.93.170.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26839; Wed, 15 Apr 1998 11:00:56 GMT (envelope-from alex@UkrCard.COM) Received: from localhost (alex@localhost) by solaric.UkrCard.COM (8.8.8/8.8.8) with SMTP id NAA26566; Wed, 15 Apr 1998 13:58:54 +0300 (EEST) (envelope-from alex@solaric.UkrCard.COM) Date: Wed, 15 Apr 1998 13:58:53 +0300 (EEST) From: Alexander Tatmaniants To: Phillip Krokidis cc: freebsd-install@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Network Card problems In-Reply-To: <2.2.32.19980415062956.007691f0@iaccess.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 Wed, 15 Apr 1998, Phillip Krokidis wrote: > Hello, > > We are trying to install an SMC8216 [SMC9432TX] pci card on Freebsd2.2.5 AFAIK there is no driver for this card in 2.2.5, you have to upgrade to 2.2.6. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 16 09:16:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07749 for freebsd-hardware-outgoing; Thu, 16 Apr 1998 09:16:38 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from gorillanet.gorilla.net (gorillanet.gorilla.net [208.128.8.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA07730 for ; Thu, 16 Apr 1998 16:16:30 GMT (envelope-from tom@gorilla.net) Received: from [208.143.84.41] by gorillanet.gorilla.net (NTMail 3.03.0014/18.aaac) with ESMTP id ya068456 for ; Thu, 16 Apr 1998 11:15:41 -0500 Received: (from tom@localhost) by gorilla.net (8.8.8/8.8.8) id LAA06895; Thu, 16 Apr 1998 11:16:16 -0500 (CDT) (envelope-from tom) Message-ID: <19980416111616.39830@TOJ.org> Date: Thu, 16 Apr 1998 11:16:16 -0500 From: Tom Jackson To: freebsd-hardware@FreeBSD.ORG Subject: PAO Config for IC-Card+ Mail-Followup-To: freebsd-hardware@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anyone know the pccard.conf setting for this card? I was able to install FreeBSD over nfs to my Thinkpad 360Cs with this card but now when I try to initiate the driver for the card, I get a pccarddd message that the 'driver allocation failed for IC-Card (Device not configured). I have tried to decipher the CIS from 'pccardc dumpcis' but still don't have a clue. Anyone please. -- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 16 15:15:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24679 for freebsd-hardware-outgoing; Thu, 16 Apr 1998 15:15:58 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from gorillanet.gorilla.net (gorillanet.gorilla.net [208.128.8.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA24611 for ; Thu, 16 Apr 1998 22:15:41 GMT (envelope-from tom@gorilla.net) Received: from [208.143.84.66] by gorillanet.gorilla.net (NTMail 3.03.0014/18.aaac) with ESMTP id aa068744 for ; Thu, 16 Apr 1998 17:14:46 -0500 Received: (from tom@localhost) by gorilla.net (8.8.8/8.8.8) id RAA08467; Thu, 16 Apr 1998 17:15:21 -0500 (CDT) (envelope-from tom) Message-ID: <19980416171450.30958@TOJ.org> Date: Thu, 16 Apr 1998 17:14:50 -0500 From: Tom Jackson To: freebsd-hardware@FreeBSD.ORG Subject: Re: PAO Config for IC-Card+ Mail-Followup-To: freebsd-hardware@FreeBSD.ORG References: <19980416111616.39830@TOJ.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i rom: Tom Jackson In-Reply-To: <19980416111616.39830@TOJ.org>; from Tom Jackson on Thu, Apr 16, 1998 at 11:16:16AM -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Apr 16, 1998 at 11:16:16AM -0500, Tom Jackson wrote: > Does anyone know the pccard.conf setting for this card? > I was able to install FreeBSD over nfs to my Thinkpad > 360Cs with this card but now when I try to initiate the > driver for the card, I get a pccarddd message that the > 'driver allocation failed for IC-Card (Device not > configured). I have tried to decipher the CIS from > 'pccardc dumpcis' but still don't have a clue. > > Anyone please. > > -- > Tom > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message Never mind, got it! Had commented out ed0 driver like someone advised. BBad advise. -- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 17 03:32:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA24602 for freebsd-hardware-outgoing; Fri, 17 Apr 1998 03:32:50 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from luckssv.lucksnet.or.jp (luckssv.tsuyama.lucksnet.or.jp [202.235.120.17]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA24594 for ; Fri, 17 Apr 1998 10:32:43 GMT (envelope-from sada@lucksnet.or.jp) Received: from lucksnet.or.jp (as109.tsuyama.lucksnet.or.jp [202.235.121.202]) by luckssv.lucksnet.or.jp (8.6.12+2.4W/CF3.4W-LUCKSNET-V1.00/96020510) with ESMTP id TAA24746 for ; Fri, 17 Apr 1998 19:32:36 +0900 Message-ID: <35372F25.B33ED0AA@lucksnet.or.jp> Date: Fri, 17 Apr 1998 19:29:58 +0900 From: Makoto Sadakane X-Mailer: Mozilla 4.03 [ja] (Win95; I) MIME-Version: 1.0 To: FreeBSD-hardware@FreeBSD.ORG Subject: hardware Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org subscribe FreeBSD-hardware@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 17 03:49:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA26634 for freebsd-hardware-outgoing; Fri, 17 Apr 1998 03:49:49 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from luckssv.lucksnet.or.jp (luckssv.tsuyama.lucksnet.or.jp [202.235.120.17]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA26597 for ; Fri, 17 Apr 1998 10:49:37 GMT (envelope-from sada@lucksnet.or.jp) Received: from lucksnet.or.jp (as109.tsuyama.lucksnet.or.jp [202.235.121.202]) by luckssv.lucksnet.or.jp (8.6.12+2.4W/CF3.4W-LUCKSNET-V1.00/96020510) with ESMTP id TAA25457 for ; Fri, 17 Apr 1998 19:49:34 +0900 Message-ID: <3537303B.7A569879@lucksnet.or.jp> Date: Fri, 17 Apr 1998 19:34:35 +0900 From: Makoto Sadakane X-Mailer: Mozilla 4.03 [ja] (Win95; I) MIME-Version: 1.0 To: FreeBSD-hardware@FreeBSD.ORG Subject: hardware Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org subscribe FreeBSD-hardware@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 17 13:50:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24584 for freebsd-hardware-outgoing; Fri, 17 Apr 1998 13:50:37 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from cerberus.partsnow.com (gatekeeper.partsnow.com [207.155.26.98] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA24545 for ; Fri, 17 Apr 1998 20:50:26 GMT (envelope-from don@partsnow.com) Received: (from bin@localhost) by cerberus.partsnow.com (8.8.5/8.6.9) id NAA25414 for ; Fri, 17 Apr 1998 13:50:35 -0700 (PDT) X-Authentication-Warning: cerberus.partsnow.com: bin set sender to using -f Received: from wildeweb(192.168.100.10) by cerberus.partsnow.com via smap (V2.0) id xma025401; Fri, 17 Apr 98 13:50:12 -0700 Message-ID: <3537C046.3F8AE6B7@partsnow.com> Date: Fri, 17 Apr 1998 13:49:10 -0700 From: Don Wilde Reply-To: don@partsnow.com Organization: Soligen, Incorporated X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: freebsd-hardware@FreeBSD.ORG Subject: RAID system Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Guys - Please e-mail Frank Carta at Winchester Systems re: testing and inclusion of their RAID box on Vendor's list. He says his emails are bouncing. carta@winsys.com http://www.winsys.com -- oooOOO O O O o * * * * * * o ___ _________ _________ ________ _________ _________ ___==_ V_=_=_DW ===--- Don Wilde [don@PartsNow.com] [http://www.PartsNow.com ] /oo0000oo-oo--oo-ooo---ooo-ooo---ooo-ooo--ooo-ooo---ooo-ooo---ooo-oo--oo  To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 17 16:13:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02167 for freebsd-hardware-outgoing; Fri, 17 Apr 1998 16:13:03 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from fanfic.org (fanfic.org [205.150.35.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02018 for ; Fri, 17 Apr 1998 23:12:36 GMT (envelope-from dstenn@fanfic.org) Received: from fanfic.org (localhost.fanfic.org [127.0.0.1]) by fanfic.org (8.8.8/8.8.8) with SMTP id TAA02607 for ; Fri, 17 Apr 1998 19:11:57 -0400 (EDT) (envelope-from dstenn@fanfic.org) Posted-Date: Fri, 17 Apr 1998 19:11:57 -0400 (EDT) Date: Fri, 17 Apr 1998 19:11:56 -0400 (EDT) From: Dennis Tenn To: freebsd-hardware@FreeBSD.ORG Subject: S3 ViRGE/DX w/ 4Mb RAM, XFree86 3.3.2 and xdm 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 everyone. I've been experiencing a problem with the above combination on my computer and would like to know if I'm the only one and if there is a solution. I have a P166 w/ 128Mb RAM and the above hardware. When I start up my computer in xdm the initial screen comes up perfectly. I login and if I exit my X-window session I get a screen full of virtical red lines and my console locks up. This also happened to a friend who is running XFree86 3.3.2 with the same card using Linux while I'm using it with FreeBSD 3.0-current. We both are using the XF86_S3V accellerated driver. We both would like to use xdm but this problem doesn't let us. Is this a problem with the driver or the hardware, ie. the S3 ViRGE/DX video card? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Dennis Tenn * There will always come a time dstenn@fanfic.org * When your love will be tested ICQ# 1457509 * Stand tall and rise to the occasion * For only then will you grow strong. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 17 16:27:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06297 for freebsd-hardware-outgoing; Fri, 17 Apr 1998 16:27:18 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from fanfic.org (fanfic.org [205.150.35.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06204 for ; Fri, 17 Apr 1998 23:27:05 GMT (envelope-from dstenn@fanfic.org) Received: from fanfic.org (localhost.fanfic.org [127.0.0.1]) by fanfic.org (8.8.8/8.8.8) with SMTP id TAA02675 for ; Fri, 17 Apr 1998 19:27:02 -0400 (EDT) (envelope-from dstenn@fanfic.org) Posted-Date: Fri, 17 Apr 1998 19:27:02 -0400 (EDT) Date: Fri, 17 Apr 1998 19:27:02 -0400 (EDT) From: Dennis Tenn To: freebsd-hardware@FreeBSD.ORG Subject: Re: S3 ViRGE/DX w/ 4Mb RAM, XFree86 3.3.2 and xdm In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 17 Apr 1998, Dennis Tenn wrote: | I've been experiencing a problem with the above combination on my computer | and would like to know if I'm the only one and if there is a solution. | | I have a P166 w/ 128Mb RAM and the above hardware. When I start up my | computer in xdm the initial screen comes up perfectly. I login and if I | exit my X-window session I get a screen full of virtical red lines and my | console locks up. This also happened to a friend who is running XFree86 | 3.3.2 with the same card using Linux while I'm using it with FreeBSD | 3.0-current. We both are using the XF86_S3V accellerated driver. We both | would like to use xdm but this problem doesn't let us. Is this a problem | with the driver or the hardware, ie. the S3 ViRGE/DX video card? I should mention that if I don't start xdm but go to a console prompt and startx I can leave and startx without problems. It just happens with xdm. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Dennis Tenn * There will always come a time dstenn@fanfic.org * When your love will be tested ICQ# 1457509 * Stand tall and rise to the occasion * For only then will you grow strong. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 17 16:46:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12112 for freebsd-hardware-outgoing; Fri, 17 Apr 1998 16:46:24 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from symbion.srrc.usda.gov ([199.78.118.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12098 for ; Fri, 17 Apr 1998 23:46:07 GMT (envelope-from glenn@nola.srrc.usda.gov) Received: from nola.srrc.usda.gov (localhost.srrc.usda.gov [127.0.0.1]) by symbion.srrc.usda.gov (8.8.8/8.8.8) with ESMTP id SAA05374; Fri, 17 Apr 1998 18:45:14 -0500 (CDT) (envelope-from glenn@nola.srrc.usda.gov) Message-Id: <199804172345.SAA05374@symbion.srrc.usda.gov> X-Mailer: exmh version 2.0.2 2/24/98 To: Dennis Tenn cc: freebsd-hardware@FreeBSD.ORG From: Glenn Johnson Subject: Re: S3 ViRGE/DX w/ 4Mb RAM, XFree86 3.3.2 and xdm In-reply-to: Your message of "Fri, 17 Apr 1998 19:11:56 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 Apr 1998 18:45:14 -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Hi everyone. > > I've been experiencing a problem with the above combination on my computer > and would like to know if I'm the only one and if there is a solution. > > I have a P166 w/ 128Mb RAM and the above hardware. When I start up my > computer in xdm the initial screen comes up perfectly. I login and if I > exit my X-window session I get a screen full of virtical red lines and my > console locks up. This also happened to a friend who is running XFree86 > 3.3.2 with the same card using Linux while I'm using it with FreeBSD > 3.0-current. We both are using the XF86_S3V accellerated driver. We both > would like to use xdm but this problem doesn't let us. Is this a problem > with the driver or the hardware, ie. the S3 ViRGE/DX video card? It's the driver. Use the XF86_SVGA driver instead. -- Glenn Johnson Technician USDA-ARS-SRRC Phone: (504) 286-4252 1100 Robert E. Lee Boulevard FAX: (504) 286-4217 New Orleans, LA 70124 e-mail: gjohnson@nola.srrc.usda.gov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 17 18:15:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00145 for freebsd-hardware-outgoing; Fri, 17 Apr 1998 18:15:47 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00136 for ; Sat, 18 Apr 1998 01:15:37 GMT (envelope-from girgen@partitur.se) Received: from partitur.se (t4o29p75.telia.com [194.236.215.195]) by bastuba.partitur.se (8.8.5/8.8.5) with ESMTP id DAA10298; Sat, 18 Apr 1998 03:15:23 +0200 (CEST) Message-ID: <3537FE8E.27C886A6@partitur.se> Date: Sat, 18 Apr 1998 03:14:54 +0200 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-STABLE i386) MIME-Version: 1.0 To: Dennis Tenn CC: freebsd-hardware@FreeBSD.ORG, kudo@partitur.se Subject: Re: S3 ViRGE/DX w/ 4Mb RAM, XFree86 3.3.2 and xdm References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id BAA00137 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Dennis! My collegue has the same stuff you have. It works fine until trying to logout. Then the machine hangs completely, requiring a reset. I can kill X from another console OK, but not logout from X. Seems to be xdm related, but Iäm not sure. Happens with both 3.3.1 and 3.3.2. FreeBSD stable 2.2.6. /Palle Dennis Tenn wrote: > > Hi everyone. > > I've been experiencing a problem with the above combination on my computer > and would like to know if I'm the only one and if there is a solution. > > I have a P166 w/ 128Mb RAM and the above hardware. When I start up my > computer in xdm the initial screen comes up perfectly. I login and if I > exit my X-window session I get a screen full of virtical red lines and my > console locks up. This also happened to a friend who is running XFree86 > 3.3.2 with the same card using Linux while I'm using it with FreeBSD > 3.0-current. We both are using the XF86_S3V accellerated driver. We both > would like to use xdm but this problem doesn't let us. Is this a problem > with the driver or the hardware, ie. the S3 ViRGE/DX video card? > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Dennis Tenn * There will always come a time > dstenn@fanfic.org * When your love will be tested > ICQ# 1457509 * Stand tall and rise to the occasion > * For only then will you grow strong. > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 17 22:24:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04149 for freebsd-hardware-outgoing; Fri, 17 Apr 1998 22:24:52 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from fanfic.org (fanfic.org [205.150.35.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA04135 for ; Sat, 18 Apr 1998 05:24:46 GMT (envelope-from dstenn@fanfic.org) Received: from fanfic.org (localhost.fanfic.org [127.0.0.1]) by fanfic.org (8.8.8/8.8.8) with SMTP id BAA04311 for ; Sat, 18 Apr 1998 01:24:40 -0400 (EDT) (envelope-from dstenn@fanfic.org) Posted-Date: Sat, 18 Apr 1998 01:24:40 -0400 (EDT) Date: Sat, 18 Apr 1998 01:24:40 -0400 (EDT) From: Dennis Tenn To: freebsd-hardware@FreeBSD.ORG Subject: Re: S3 ViRGE/DX w/ 4Mb RAM, XFree86 3.3.2 and xdm In-Reply-To: <199804172345.SAA05374@symbion.srrc.usda.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 17 Apr 1998, Glenn Johnson wrote: | > I've been experiencing a problem with the above combination on my computer | > and would like to know if I'm the only one and if there is a solution. | > | > I have a P166 w/ 128Mb RAM and the above hardware. When I start up my | > computer in xdm the initial screen comes up perfectly. I login and if I | > exit my X-window session I get a screen full of virtical red lines and my | > console locks up. This also happened to a friend who is running XFree86 | > 3.3.2 with the same card using Linux while I'm using it with FreeBSD | > 3.0-current. We both are using the XF86_S3V accellerated driver. We both | > would like to use xdm but this problem doesn't let us. Is this a problem | > with the driver or the hardware, ie. the S3 ViRGE/DX video card? | | It's the driver. Use the XF86_SVGA driver instead. Ok.. I tried to do things the simple way. I deleted the symlink from X to XF86_S3V and created a new symlink to XF86_SVGA and tried to restart X. It failed immediately. If I put back the link to XF86_S3V it works fine. What am I doing wrong? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Dennis Tenn * There will always come a time dstenn@fanfic.org * When your love will be tested ICQ# 1457509 * Stand tall and rise to the occasion * For only then will you grow strong. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 17 23:32:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA11896 for freebsd-hardware-outgoing; Fri, 17 Apr 1998 23:32:03 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA11850; Sat, 18 Apr 1998 06:31:55 GMT (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id CAA03178; Sat, 18 Apr 1998 02:33:08 -0400 (EDT) (envelope-from mark) Message-ID: <19980418023307.34709@vmunix.com> Date: Sat, 18 Apr 1998 02:33:07 -0400 From: Mark Mayo To: stable@FreeBSD.ORG Cc: hardware@FreeBSD.ORG Subject: best wdc0 flags ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i X-Operating-System: FreeBSD 2.2.5-STABLE i386 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi. I just put a shiney new IDE (Ultra33) drive in a machine, and I'm wondering what the best flags to use for the drive are.. I realize that I can't get DMA on -STABLE (cvsupping right now), but with the default LINT flags of: controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x00ff8004 .. which turns on 32-bit transfers and multi-block-4 I'm gettting really crappy performance.. vnode:{76}~ % iozone 160 32000 ... IOZONE performance measurements: 2237052 bytes/second for writing the file 2264181 bytes/second for reading the file Now that is horrible. :-) Same results with block-size of 8K. I think I'll try without the flag option at all and see how it performs. Any recomendations appreciated, -Mark P.S. The drive is a Quantum Fireball SE 4.3GB, FWIW. -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ "The problem is how do you build tools that understand your programs at a deeper semantic level." - James Gosling To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Apr 18 01:09:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA21775 for freebsd-hardware-outgoing; Sat, 18 Apr 1998 01:09:49 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21766; Sat, 18 Apr 1998 08:09:45 GMT (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id KAA08148; Sat, 18 Apr 1998 10:09:36 +0200 (MEST) (envelope-from sos) Message-Id: <199804180809.KAA08148@sos.freebsd.dk> Subject: Re: best wdc0 flags ? In-Reply-To: <19980418023307.34709@vmunix.com> from Mark Mayo at "Apr 18, 98 02:33:07 am" To: mark@vmunix.com (Mark Mayo) Date: Sat, 18 Apr 1998 10:09:36 +0200 (MEST) Cc: stable@FreeBSD.ORG, hardware@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In reply to Mark Mayo who wrote: > Hi. I just put a shiney new IDE (Ultra33) drive in a machine, and > I'm wondering what the best flags to use for the drive are.. I realize > that I can't get DMA on -STABLE (cvsupping right now), but with the > default LINT flags of: > > controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x00ff8004 .. > which turns on 32-bit transfers and multi-block-4 > > I'm gettting really crappy performance.. > > vnode:{76}~ % iozone 160 32000 > ... > IOZONE performance measurements: > 2237052 bytes/second for writing the file > 2264181 bytes/second for reading the file > > Now that is horrible. :-) Same results with block-size of 8K. > I think I'll try without the flag option at all and see how it performs. Hmm, you should see about 9M/s from a drive like this.. I havn't run 2.2.x for ages but I've made two NFS servers with 4 of those exact disks using -current, and it gets ~9M/s, so the facts are there... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Apr 18 01:22:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23640 for freebsd-hardware-outgoing; Sat, 18 Apr 1998 01:22:27 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23633 for ; Sat, 18 Apr 1998 08:22:23 GMT (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id KAA08187; Sat, 18 Apr 1998 10:22:10 +0200 (MEST) (envelope-from sos) Message-Id: <199804180822.KAA08187@sos.freebsd.dk> Subject: Re: S3 ViRGE/DX w/ 4Mb RAM, XFree86 3.3.2 and xdm In-Reply-To: from Dennis Tenn at "Apr 17, 98 07:11:56 pm" To: dstenn@fanfic.org (Dennis Tenn) Date: Sat, 18 Apr 1998 10:22:09 +0200 (MEST) Cc: freebsd-hardware@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In reply to Dennis Tenn who wrote: > > I have a P166 w/ 128Mb RAM and the above hardware. When I start up my > computer in xdm the initial screen comes up perfectly. I login and if I > exit my X-window session I get a screen full of virtical red lines and my > console locks up. This also happened to a friend who is running XFree86 > 3.3.2 with the same card using Linux while I'm using it with FreeBSD > 3.0-current. We both are using the XF86_S3V accellerated driver. We both > would like to use xdm but this problem doesn't let us. Is this a problem > with the driver or the hardware, ie. the S3 ViRGE/DX video card? Hmm, I run a Dual P6/200 with a S3 ViRGE/DX 4MB on -current and the 3.3.2 XF86_S3V server. I see no problems, but I don't use xdm that often, but I have used it and it worked flawlessly.... If it matters my ViRGE card is an "ExpertColor" one with EDO RAM.... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Apr 18 03:19:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA04859 for freebsd-hardware-outgoing; Sat, 18 Apr 1998 03:19:19 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from fanfic.org (fanfic.org [205.150.35.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04842 for ; Sat, 18 Apr 1998 10:19:10 GMT (envelope-from dstenn@fanfic.org) Received: from fanfic.org (localhost.fanfic.org [127.0.0.1]) by fanfic.org (8.8.8/8.8.8) with SMTP id GAA19097 for ; Sat, 18 Apr 1998 06:19:07 -0400 (EDT) (envelope-from dstenn@fanfic.org) Posted-Date: Sat, 18 Apr 1998 06:19:07 -0400 (EDT) Date: Sat, 18 Apr 1998 06:19:07 -0400 (EDT) From: Dennis Tenn To: freebsd-hardware@FreeBSD.ORG Subject: Re: S3 ViRGE/DX w/ 4Mb RAM, XFree86 3.3.2 and xdm In-Reply-To: <199804180822.KAA08187@sos.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id KAA04845 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 18 Apr 1998, Søren Schmidt wrote: | > I have a P166 w/ 128Mb RAM and the above hardware. When I start up my | > computer in xdm the initial screen comes up perfectly. I login and if I | > exit my X-window session I get a screen full of virtical red lines and my | > console locks up. This also happened to a friend who is running XFree86 | > 3.3.2 with the same card using Linux while I'm using it with FreeBSD | > 3.0-current. We both are using the XF86_S3V accellerated driver. We both | > would like to use xdm but this problem doesn't let us. Is this a problem | > with the driver or the hardware, ie. the S3 ViRGE/DX video card? | | Hmm, I run a Dual P6/200 with a S3 ViRGE/DX 4MB on -current and the | 3.3.2 XF86_S3V server. I see no problems, but I don't use xdm that | often, but I have used it and it worked flawlessly.... | | If it matters my ViRGE card is an "ExpertColor" one with EDO RAM.... Actually that is also what I have. I have no problems if I'm not using xdm and only when using xdm do I get my system locked up. Could you try using xdm and just try logging in and out of X a few times? Maybe 5 to 10 times, just to see if it remains stable. If it does could you send me a list of your hardware specs? I'm not the only one experiencing this problem so I sincerely doubt I have done something wrong and must believe that it is either a hardware or a software problem. I'm hoping it's software but also looking for a replacement video card if this can't be resolved. My friend is using an ATI Expert@Play w/ 8Mb ram is having no problems. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Dennis Tenn * There will always come a time dstenn@fanfic.org * When your love will be tested ICQ# 1457509 * Stand tall and rise to the occasion * For only then will you grow strong. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Apr 18 06:56:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12668 for freebsd-hardware-outgoing; Sat, 18 Apr 1998 06:56:05 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from uk1.imdb.com (UK1.IMDb.COM [192.68.174.59]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA12621 for ; Sat, 18 Apr 1998 13:55:58 GMT (envelope-from robh@imdb.com) Received: from robh.imdb.com [194.222.68.23] by uk1.imdb.com with esmtp (Exim 1.62 #1) id 0yQXzP-0006QR-00; Sat, 18 Apr 1998 14:49:08 +0100 Date: Sat, 18 Apr 1998 14:42:37 +0100 (BST) From: Rob Hartill X-Sender: robh@localhost To: hardware@FreeBSD.ORG Subject: Dell Inspiron 3000/3200 portable 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 Anyone have any success/horror stories regarding FreeBSD on a Dell Inspiron 3000 or 3200 ? On a related topic, are there any specific gotchas to watch out for when buying a portable for use with FreeBSD ? thanks in advance. -- Rob Hartill Internet Movie Database (Ltd) http://www.moviedatabase.com/ .. a site for sore eyes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Apr 18 09:48:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15683 for freebsd-hardware-outgoing; Sat, 18 Apr 1998 09:48:34 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles306.castles.com [208.214.167.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15635; Sat, 18 Apr 1998 16:48:26 GMT (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id JAA04953; Sat, 18 Apr 1998 09:45:54 -0700 (PDT) Message-Id: <199804181645.JAA04953@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mark Mayo cc: stable@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: best wdc0 flags ? In-reply-to: Your message of "Sat, 18 Apr 1998 02:33:07 EDT." <19980418023307.34709@vmunix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Apr 1998 09:45:53 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi. I just put a shiney new IDE (Ultra33) drive in a machine, and > I'm wondering what the best flags to use for the drive are.. I realize > that I can't get DMA on -STABLE (cvsupping right now), but with the > default LINT flags of: > > controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x00ff8004 .. > which turns on 32-bit transfers and multi-block-4 I'd generally use 0x80ff80ff and let the autodetection code sort it out - in fact, I haven't run into a drive/controller combination yet that doesn't get that right. (Not saying they don't exist, just that the vast majority of hardware works as desired). > I'm gettting really crappy performance.. > > vnode:{76}~ % iozone 160 32000 > .... > IOZONE performance measurements: > 2237052 bytes/second for writing the file > 2264181 bytes/second for reading the file > > Now that is horrible. :-) Same results with block-size of 8K. > I think I'll try without the flag option at all and see how it performs. > > Any recomendations appreciated, > -Mark > > P.S. The drive is a Quantum Fireball SE 4.3GB, FWIW. We've been duplicating 3GB Western Digital disks the last few days under 2.2.6, flags 0x80ff80ff on 166MHz P5/430TX boards, and averaging about 5M/sec throughput. Try 'dd if=/dev/wd1 of=/dev/null bs=1m' to get an idea of your raw disk speed as opposed to filesystem throughput. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Apr 18 13:21:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21774 for freebsd-hardware-outgoing; Sat, 18 Apr 1998 13:21:39 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from localhost.ca (root@dial113.bc1.com [207.34.139.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA21717; Sat, 18 Apr 1998 20:21:30 GMT (envelope-from jake@localhost.ca.freebsd.org) Received: from localhost.ca (jake@localhost.ca [127.0.0.1]) by localhost.ca (8.8.8/8.8.8) with ESMTP id NAA00837; Sat, 18 Apr 1998 13:25:20 -0700 (PDT) (envelope-from jake@localhost.ca) Message-Id: <199804182025.NAA00837@localhost.ca> X-Mailer: exmh version 1.6.9 8/22/96 To: hardware@FreeBSD.ORG cc: stable@FreeBSD.ORG Subject: Re: best wdc0 flags ? In-reply-to: Your message of "Sat, 18 Apr 1998 09:45:53 PDT." <199804181645.JAA04953@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Apr 1998 13:25:19 -0700 From: Jake Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'd generally use 0x80ff80ff and let the autodetection code sort it out I get IOZONE performance measurements: 5144042 bytes/second for writing the file 5756362 bytes/second for reading the file with this flag on a Western Digital AC22500. It increased the dd if=/dev/wd0 of=/dev/null throughput from ~3 mb/s with no flags to ~4 mb/s. -- http://www.checker.org/~jake To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Apr 18 13:42:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25610 for freebsd-hardware-outgoing; Sat, 18 Apr 1998 13:42:45 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA25471; Sat, 18 Apr 1998 20:42:33 GMT (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id QAA00418; Sat, 18 Apr 1998 16:43:32 -0400 (EDT) (envelope-from mark) Message-ID: <19980418164331.08912@vmunix.com> Date: Sat, 18 Apr 1998 16:43:31 -0400 From: Mark Mayo To: Mike Smith Cc: stable@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: best wdc0 flags ? References: <19980418023307.34709@vmunix.com> <199804181645.JAA04953@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199804181645.JAA04953@antipodes.cdrom.com>; from Mike Smith on Sat, Apr 18, 1998 at 09:45:53AM -0700 X-Operating-System: FreeBSD 2.2.6-STABLE i386 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Apr 18, 1998 at 09:45:53AM -0700, Mike Smith wrote: > > Hi. I just put a shiney new IDE (Ultra33) drive in a machine, and > > I'm wondering what the best flags to use for the drive are.. I realize > > that I can't get DMA on -STABLE (cvsupping right now), but with the > > default LINT flags of: [SNIP] > We've been duplicating 3GB Western Digital disks the last few days under > 2.2.6, flags 0x80ff80ff on 166MHz P5/430TX boards, and averaging about > 5M/sec throughput. Try 'dd if=/dev/wd1 of=/dev/null bs=1m' to get an > idea of your raw disk speed as opposed to filesystem throughput. First, relavent dmesg output: FreeBSD 2.2.6-STABLE #0: Sat Apr 18 15:50:05 EDT 1998 CPU: Pentium (167.07-MHz 586-class CPU) real memory = 67108864 (65536K bytes) chip0 rev 1 on pci0:0:0 chip2 rev 1 on pci0:7:1 wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S Now the mega-crappy performance I'm still getting: vnode:{77}~ % dd if=/dev/wd0 of=/dev/null bs=1m ^C76+0 records in 76+0 records out 79691776 bytes transferred in 36.231349 secs (2199525 bytes/sec) vnode:{83}~ % iozone 165 17000 ... IOZONE performance measurements: 2438356 bytes/second for writing the file 3048197 bytes/second for reading the file Hmmrf. I'm sure the 3.0 read was just due to caching.. (64MB of pretty much unused RAM). vnode:{86}~ % bonnie -s 200 File './Bonnie.323', size: 209715200 Writing with putc()...done Rewriting...done Writing intelligently...done Reading with getc()...done Reading intelligently...done Seeker 1...Seeker 2...Seeker 3...start 'em...done...done...done... -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 200 1833 36.3 2384 17.4 1168 5.3 2097 31.4 2406 6.4 73.5 4.6 Man, either this drive really sucks, or something weird is going on! :-) The motherboard is the highly recomended Abit, DIMM RAM, etc.. STREAM is still showing memory throughput over 100MB/s, so that's working fine, and the old 1GB SCSI disk in the system is still pumping out about 4MB/s with the above tests.. If anyone has any ideas why the latest greatest IDE drive from Quantum is blowing chunks all over my I/O, give me a shout! :-) -Mark > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ "The problem is how do you build tools that understand your programs at a deeper semantic level." - James Gosling To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Apr 18 15:01:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10614 for freebsd-hardware-outgoing; Sat, 18 Apr 1998 15:01:04 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA10600; Sat, 18 Apr 1998 22:00:57 GMT (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id VAA10880; Sat, 18 Apr 1998 21:25:58 +0200 From: Luigi Rizzo Message-Id: <199804181925.VAA10880@labinfo.iet.unipi.it> Subject: Re: best wdc0 flags ? To: mark@vmunix.com (Mark Mayo) Date: Sat, 18 Apr 1998 21:25:57 +0200 (MET DST) Cc: mike@smith.net.au, stable@FreeBSD.ORG, hardware@FreeBSD.ORG In-Reply-To: <19980418164331.08912@vmunix.com> from "Mark Mayo" at Apr 18, 98 04:43:12 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > We've been duplicating 3GB Western Digital disks the last few days under > > 2.2.6, flags 0x80ff80ff on 166MHz P5/430TX boards, and averaging about > > 5M/sec throughput. Try 'dd if=/dev/wd1 of=/dev/null bs=1m' to get an > > idea of your raw disk speed as opposed to filesystem throughput. my experience with WD (caviar) is also good , speaking of speed. Cannot say the same about reliability, since last year we had about 10-15 units die within a few months (all replaced under warranty, and havent' crashed again since then). Also in my experience, maxtors are aslow (about 3MB/s) and I am interested in this thread on the QUANTUM FIREBALL since i am (was, given the poor results ?) thinking of buying one... cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Apr 18 17:03:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA02347 for freebsd-hardware-outgoing; Sat, 18 Apr 1998 17:03:06 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles324.castles.com [208.214.167.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02341; Sun, 19 Apr 1998 00:02:59 GMT (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id QAA05960; Sat, 18 Apr 1998 16:59:43 -0700 (PDT) Message-Id: <199804182359.QAA05960@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Luigi Rizzo cc: mark@vmunix.com (Mark Mayo), mike@smith.net.au, stable@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: best wdc0 flags ? In-reply-to: Your message of "Sat, 18 Apr 1998 21:25:57 +0200." <199804181925.VAA10880@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Apr 1998 16:59:42 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > We've been duplicating 3GB Western Digital disks the last few days under > > > 2.2.6, flags 0x80ff80ff on 166MHz P5/430TX boards, and averaging about > > > 5M/sec throughput. Try 'dd if=/dev/wd1 of=/dev/null bs=1m' to get an > > > idea of your raw disk speed as opposed to filesystem throughput. > > my experience with WD (caviar) is also good , speaking of speed. Cannot > say the same about reliability, since last year we had about 10-15 > units die within a few months (all replaced under warranty, and havent' > crashed again since then). Likewise here. They're also less than wonderful when it comes to withstanding physical abuse. > Also in my experience, maxtors are aslow (about 3MB/s) and I am > interested in this thread on the QUANTUM FIREBALL since i am (was, > given the poor results ?) thinking of buying one... I haven't seen too much to recommend the IDE Furballs when it comes to performance. I would personally recommend you look at the IBM Deskstar units if you want both performance and reliability. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Apr 18 18:34:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18216 for freebsd-hardware-outgoing; Sat, 18 Apr 1998 18:34:17 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from colossus.dyn.ml.org (dburr@206-18-112-191.la.inreach.net [206.18.112.191]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA18210 for ; Sun, 19 Apr 1998 01:34:06 GMT (envelope-from dburr@colossus.dyn.ml.org) Received: (from dburr@localhost) by colossus.dyn.ml.org (8.8.8/8.8.7) id SAA01098; Sat, 18 Apr 1998 18:28:33 -0700 (PDT) (envelope-from dburr) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 18 Apr 1998 18:28:27 -0700 (PDT) Organization: Computer Help From: Donald Burr To: Dennis Tenn Subject: Re: S3 ViRGE/DX w/ 4Mb RAM, XFree86 3.3.2 and xdm Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- My secret spy satellite informs me that on 18-Apr-98, Dennis Tenn wrote: > Ok.. I tried to do things the simple way. I deleted the symlink from X > to > XF86_S3V and created a new symlink to XF86_SVGA and tried to restart X. > It failed immediately. If I put back the link to XF86_S3V it works > fine. > What am I doing wrong? YOu will have to re-run XF86Setup/xf86config. The Accelerated servers (i.e. XF86-S3V) and SVGA use different blocks in the configuration file. Alternatively (this MAY work, I haven't tried it myself) you can just go in and find the "Screen" section, to the line "Driver "Accel"", change that to "Driver "SVGA"". Like I said, this may work or it may not, but I doubt it will screw up your system if you try it, so it's worth a shot. - --- Donald Burr - Ask me for my PGP key | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ #1347455 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNTlTOvjpixuAwagxAQGQPwP8CkvEpg2Qxf6r6KqyNWUL/ZaDXDSsPIf1 oBt0YmEYNXGZZV2W+gRioMQLZM7UFsjLng2j3RJ4GerCN/Ex7US67ZLeI9zlbFyY z4R/cHCiyalHO0CAItOZA86amZlVH46VOBPHQnr5dZLmMy6GvQZiaEK875oW+NWH yvdFjSeTZzk= =Il9Q -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Apr 18 18:40:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19080 for freebsd-hardware-outgoing; Sat, 18 Apr 1998 18:40:58 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from colossus.dyn.ml.org (dburr@206-18-112-191.la.inreach.net [206.18.112.191]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19044; Sun, 19 Apr 1998 01:40:49 GMT (envelope-from dburr@colossus.dyn.ml.org) Received: (from dburr@localhost) by colossus.dyn.ml.org (8.8.8/8.8.7) id SAA02024; Sat, 18 Apr 1998 18:35:36 -0700 (PDT) (envelope-from dburr) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19980418023307.34709@vmunix.com> Date: Sat, 18 Apr 1998 18:35:34 -0700 (PDT) Organization: Computer Help From: Donald Burr To: Mark Mayo Subject: RE: best wdc0 flags ? Cc: hardware@FreeBSD.ORG, stable@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- My secret spy satellite informs me that on 18-Apr-98, Mark Mayo wrote: > Hi. I just put a shiney new IDE (Ultra33) drive in a machine, and > I'm wondering what the best flags to use for the drive are.. I realize > that I can't get DMA on -STABLE (cvsupping right now), but with the > default LINT flags of: > controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x00ff8004 > which turns on 32-bit transfers and multi-block-4 The best combination of flags is 0x80ff, this will turn on 32-bit transfers and will do multi-block up to the maximum that is supported by the drive. > I'm gettting really crappy performance.. > > vnode:{76}~ % iozone 160 32000 > ... > IOZONE performance measurements: > 2237052 bytes/second for writing the file > 2264181 bytes/second for reading the file My results are: (using flags 0x80ff80ff): IOZONE performance measurements: 4828250 bytes/second for writing the file 5620741 bytes/second for reading the file This is on a Maxtor 4.3 GB UDMA33 (84320D4). - --- Donald Burr - Ask me for my PGP key | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ #1347455 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNTlU4fjpixuAwagxAQGBrwP+No/b/QpXLcD2hHxuo2OBNXwy2hPJCqLx VzrsURMgx94MPE0SMdDM5iTsvB0KNB1olzkAr9X7FU617BvsyQCoEdzkkgrRXN3k a7eH3xbc6Bql5FI1fF2suvV46W2RjQ717/1QOWfl8C3mN/s+U24oGQw1Bs1qLEox SQYUpr/hhPs= =OYZo -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Apr 18 19:15:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25446 for freebsd-hardware-outgoing; Sat, 18 Apr 1998 19:15:38 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA25428; Sun, 19 Apr 1998 02:15:30 GMT (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id MAA14356; Sun, 19 Apr 1998 12:12:21 +1000 Date: Sun, 19 Apr 1998 12:12:21 +1000 From: Bruce Evans Message-Id: <199804190212.MAA14356@godzilla.zeta.org.au> To: mark@vmunix.com, mike@smith.net.au Subject: Re: best wdc0 flags ? Cc: hardware@FreeBSD.ORG, stable@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >We've been duplicating 3GB Western Digital disks the last few days under >2.2.6, flags 0x80ff80ff on 166MHz P5/430TX boards, and averaging about >5M/sec throughput. Seems a bit slow. For a Fireball ST6.4 under -current, flags 0xa0ffa0ff (DMA...) on a K6/233/VIA2, I get 9-10M/sec for `dd if=/dev/rwd2 of=/dev/null bs=1m count=1280'. 5-6M/sec is normal for the previous generation of 5400 rpm IDE drives and for the outer tracks of this drive. >Try 'dd if=/dev/wd1 of=/dev/null bs=1m' to get an >idea of your raw disk speed as opposed to filesystem throughput. A bad idea. /dev/wd1 is not a raw disk. It is a buffered disk with a too-small block size of 2K. The effects of the buffer cache are difficult to analyze, and not very interesting because real file systems don't use a too-small block size, and clustering usually gives an effective block size of 64K or 128K for large sequential files. Read clustering seems to be unpessimizing the throughput for the 2K block size in -current, but at a huge cost: $ time dd if=/dev/rwd2 of=/dev/null bs=1m count=1280 # raw 1280+0 records in 1280+0 records out 1342177280 bytes transferred in 136.574105 secs (9827465 bytes/sec) 137.22 real 0.00 user 2.04 sys $ time dd if=/dev/wd2 of=/dev/null bs=1m count=1280 # buferred 1280+0 records in 1280+0 records out 1342177280 bytes transferred in 136.127378 secs (9859716 bytes/sec) 136.78 real 0.02 user 116.84 sys ^^^^^^^^^^ huge cost A slightly slower CPU would not be able to keep up with the disk. DMA only helps in this benchmark by freeing up some CPU cycles. PIO at 16.6M/sec would consume over half the CPU cycles, so the same CPU would not be able to keep up if the disk were in non-DMA mode. The cost for a too-small block size on the raw device is large but not huge: $ time dd if=/dev/wd2 of=/dev/null bs=2k count=1280 # raw, pessimized 655360+0 records in 655360+0 records out 1342177280 bytes transferred in 136.931865 secs (9801789 bytes/sec) 136.99 real 2.19 user 46.39 sys Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Apr 18 22:43:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17878 for freebsd-hardware-outgoing; Sat, 18 Apr 1998 22:43:51 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA17793 for ; Sun, 19 Apr 1998 05:43:44 GMT (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id BAA03292; Sun, 19 Apr 1998 01:44:48 -0400 (EDT) (envelope-from mark) Message-ID: <19980419014448.18673@vmunix.com> Date: Sun, 19 Apr 1998 01:44:48 -0400 From: Mark Mayo To: Bruce Evans , mike@smith.net.au Cc: hardware@FreeBSD.ORG Subject: Re: best wdc0 flags ? References: <199804190212.MAA14356@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199804190212.MAA14356@godzilla.zeta.org.au>; from Bruce Evans on Sun, Apr 19, 1998 at 12:12:21PM +1000 X-Operating-System: FreeBSD 2.2.6-STABLE i386 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Apr 19, 1998 at 12:12:21PM +1000, Bruce Evans wrote: > >We've been duplicating 3GB Western Digital disks the last few days under > >2.2.6, flags 0x80ff80ff on 166MHz P5/430TX boards, and averaging about > >5M/sec throughput. > > Seems a bit slow. For a Fireball ST6.4 under -current, flags 0xa0ffa0ff > (DMA...) on a K6/233/VIA2, I get 9-10M/sec for `dd if=/dev/rwd2 > of=/dev/null bs=1m count=1280'. 5-6M/sec is normal for the previous > generation of 5400 rpm IDE drives and for the outer tracks of this drive. Hmm.. As I previously posted, I'm only getting about 2MB/s... dd if=/dev/rwd0, dd if=/dev/wd0, iozone, bonnie all get the same 2MB/s.. (flags of 0x80ff80ff) > A bad idea. /dev/wd1 is not a raw disk. It is a buffered disk > $ time dd if=/dev/rwd2 of=/dev/null bs=1m count=1280 # raw > 1280+0 records in > 1280+0 records out > 1342177280 bytes transferred in 136.574105 secs (9827465 bytes/sec) > 137.22 real 0.00 user 2.04 sys Damn.. I just tried doing a dd if=/dev/rwd0 of=/dev/null bs=1m count=1280 My machine quite literaly came to a standstill while this transfer took place. I could not deliver a single keystroke to the thing, and a telnet attempt just hung on the "Connected" part without presenting an acualy login. Benchmark finished, machine came back to life like nothing happened. Load was over 20. It's like the dd monopolized all interupts or something? Note that a dd with if=/dev/wd0 behaved "normally".. only the rwd0 reading caused hell. I noticed that even on the "wd0" and iozone writes my load was at 1.00 or greater. I'm pretty sure that the FireBall SE should be just as fast (or faster) than the FireBall ST, and the P166 should be able to max it out at 9MB/s or so like you are seeing. I'm assuming something weird is happening with my interupts, but I don't know what exactly, or why.... Any ideas what's going wrong here? -Mark > Bruce -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ "The problem is how do you build tools that understand your programs at a deeper semantic level." - James Gosling To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Apr 18 23:55:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26542 for freebsd-hardware-outgoing; Sat, 18 Apr 1998 23:55:10 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA26532 for ; Sun, 19 Apr 1998 06:55:07 GMT (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA23558; Sun, 19 Apr 1998 16:52:34 +1000 Date: Sun, 19 Apr 1998 16:52:34 +1000 From: Bruce Evans Message-Id: <199804190652.QAA23558@godzilla.zeta.org.au> To: bde@zeta.org.au, mark@vmunix.com, mike@smith.net.au Subject: Re: best wdc0 flags ? Cc: hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Damn.. I just tried doing a > dd if=/dev/rwd0 of=/dev/null bs=1m count=1280 > >My machine quite literaly came to a standstill while this transfer >took place. I could not deliver a single keystroke to the thing, and >a telnet attempt just hung on the "Connected" part without presenting >an acualy login. Benchmark finished, machine came back to life >like nothing happened. Load was over 20. It's like the dd monopolized >all interupts or something? Note that a dd with if=/dev/wd0 behaved >"normally".. only the rwd0 reading caused hell. A fast wd drive in a slow PIO mode can consume almost all of the CPU cycles. The slowest mode is PIO 0 or 1 (3.3 MB/sec), but your drive wants to transfer almost 10MB/sec on the outer tracks. You apparently have the BIOS configured in this mode. /dev/wd0 probably only works better because copying the data from the buffer cache to user space gives the system time to breathe. First, non-wd interrupts can do something while the data is being copied. Second, the copying time is counted as system time instead of interrupt time, so scheduling works better and other applications may run. Transferring 1MB at a time at only 3MB/sec from a disk supplying 10MB/sec should take about 1/3 second, during which time timeout interrupts are blocked and any active tty and network interrupt handlers are suspended (nested tty and network interrupts will be processed but won't affect applications). >I'm pretty sure that the FireBall SE should be just as fast (or faster) >than the FireBall ST, and the P166 should be able to max it out at >9MB/s or so like you are seeing. It's too fast for most PIO modes. Use PIO mode 4 (16.6 MB/sec) if possible. >Any ideas what's going wrong here? Your BIOS is misconfigured or only supports slow PIO modes. I use AUTO mode and checked that this gave 16.6MB/sec by looking at `systat -vmstat' (interrupt overhead should be about 10/16.6 * 100% for a 10 MB/sec drive). My BIOS also supports PIO modes 0, 1, 2, 3 and 4. The 10MB firehose swamps at least PIO modes 0 and 1. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message