From owner-freebsd-hardware Sun Aug 24 14:57:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA24292 for hardware-outgoing; Sun, 24 Aug 1997 14:57:47 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA24287 for ; Sun, 24 Aug 1997 14:57:43 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id XAA01444 for ; Sun, 24 Aug 1997 23:57:58 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id XAA25602 for hardware@FreeBSD.ORG; Sun, 24 Aug 1997 23:57:18 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.6/keltia-uucp-2.9) id XAA13016; Sun, 24 Aug 1997 23:47:55 +0200 (CEST) Message-ID: <19970824234754.04458@keltia.freenix.fr> Date: Sun, 24 Aug 1997 23:47:54 +0200 From: Ollivier Robert To: hardware@FreeBSD.ORG Subject: Re: K6-200 Has anyone successfully done a 'make world' ? References: <199708222333.QAA14635@george.lbl.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <199708222333.QAA14635@george.lbl.gov>; from Jin Guojun[ITG] on Fri, Aug 22, 1997 at 04:33:40PM -0700 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3586 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Jin Guojun[ITG]: > Would you please tell what is the manufactory code on you CPU? Next time I open my machine, I'll get the fan out from the CPU and send the numbers. It was one of the first K6 shipped to France (if we believe my vendor). -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #24: Fri Aug 22 23:13:44 CEST 1997 From owner-freebsd-hardware Mon Aug 25 05:39:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA07579 for hardware-outgoing; Mon, 25 Aug 1997 05:39:08 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA07569 for ; Mon, 25 Aug 1997 05:39:04 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id HAA26821; Mon, 25 Aug 1997 07:51:32 -0400 (EDT) From: Peter Dufault Message-Id: <199708251151.HAA26821@hda.hda.com> Subject: Re: Fast a-d card In-Reply-To: <199708240221.LAA00737@word.smith.net.au> from Mike Smith at "Aug 24, 97 11:51:40 am" To: mike@smith.net.au (Mike Smith) Date: Mon, 25 Aug 1997 07:51:31 -0400 (EDT) Cc: hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk (Thanks...) > > PCI only - no ISA is available. > > At 40MHz? No shit 8) I scoped out the Gage engineering board level oscilloscopes but they are a two board PCI and ISA set. I meant there will be no ISA at all on the system. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval From owner-freebsd-hardware Mon Aug 25 08:34:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA18441 for hardware-outgoing; Mon, 25 Aug 1997 08:34:14 -0700 (PDT) Received: from passer.osg.gov.bc.ca (passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA18433 for ; Mon, 25 Aug 1997 08:34:12 -0700 (PDT) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.8.7/8.6.10) id IAA24412; Mon, 25 Aug 1997 08:34:02 -0700 (PDT) Message-Id: <199708251534.IAA24412@passer.osg.gov.bc.ca> Received: from localhost(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost, id smtpdaaxCxa; Mon Aug 25 08:33:53 1997 Reply-to: cschuber@uumail.gov.bc.ca X-Mailer: MH X-Sender: cschuber To: Tom Samplonius cc: cy@uumail.gov.bc.ca, freebsd-hardware@freebsd.org Subject: Re: 3C509B Card In-reply-to: Your message of "Sat, 23 Aug 1997 12:49:16 PDT." Date: Mon, 25 Aug 1997 08:33:52 -0700 From: Cy Schubert - ITSD Open Systems Group Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > On Sat, 23 Aug 1997, Cy Schubert wrote: > > > I think I got my answer from the 3Com website. > > > > Question: Can the EtherLink III family of adapters operate in promiscuous > > mode? > > > > Answer: All EtherLink III family adapters are certified for promiscuous > > mode. However, the parallel task feature of these adapters does not support > > the promiscuous mode since it drops the bad packets before it gets to the > > CPU. > > Not really. Most cards (all?) handle retransmits internally these days. > However, I don't belive the Etherlink driver is reading the count off the > card. Some of the other drivers use to report 0 for collisions as well, > until the driver was educated on where to read the collision count from. I had a chance to look at the driver and other drivers as well. You are indeed correct. The Linux driver does read the counts off the card whenever an interrupt from the card is generated. I think that this may be a bit of a waste of CPU, as the only time the count is needed is when it's displayed. I think that a system call could be used to get the information from the card instead of needlessly obtaining the information so that netstat could lseek() to a location in kmem to get it. After a little more thought, making the information available via the /proc filesystem might be a better idea. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 UNIX Support OV/VM: BCSC02(CSCHUBER) ITSD BITNET: CSCHUBER@BCSC02.BITNET Government of BC Internet: cschuber@uumail.gov.bc.ca cschuber@bcsc02.gov.bc.ca "Quit spooling around, JES do it." From owner-freebsd-hardware Mon Aug 25 14:01:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA09509 for hardware-outgoing; Mon, 25 Aug 1997 14:01:36 -0700 (PDT) Received: from TRUTH.WOFFORD.EDU (truth.wofford.edu [199.190.174.30]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA09491 for ; Mon, 25 Aug 1997 14:01:24 -0700 (PDT) Date: Mon, 25 Aug 1997 17:01:15 -0400 From: Dan Welch To: HARDWARE@FREEBSD.org CC: WELCHDW@wofford.edu Message-Id: <970825170115.24a254a3@wofford.edu> Subject: graphics terminals Sender: owner-freebsd-hardware@FREEBSD.org X-Loop: FreeBSD.org Precedence: bulk What's a good brand and model modest graphics terminal to use with FreeBSD? Something durable under heavy use and runs on a simple serial link. Monchrome is ok, color would be nice. Not critical. From owner-freebsd-hardware Mon Aug 25 14:46:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA12783 for hardware-outgoing; Mon, 25 Aug 1997 14:46:44 -0700 (PDT) Received: from runningman.rs.itd.umich.edu (0@runningman.rs.itd.umich.edu [141.211.144.15]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA12716 for ; Mon, 25 Aug 1997 14:45:37 -0700 (PDT) Received: from HG-BASIC1MAIL.HG.MED.UMICH.EDU by runningman.rs.itd.umich.edu (8.8.5/2.3) with ESMTP id QAA04887; Mon, 25 Aug 1997 16:58:08 -0400 (EDT) Received: from HG-BASIC1/SpoolDir by HG-BASIC1MAIL.HG.MED.UMICH.EDU (Mercury 1.31); 25 Aug 97 16:58:11 -0500 Received: from SpoolDir by HG-BASIC1 (Mercury 1.31); 25 Aug 97 16:57:54 -0500 Received: from biped by HG-BASIC1MAIL.HG.MED.UMICH.EDU (Mercury 1.31) with ESMTP; 25 Aug 97 16:57:48 -0500 Message-ID: <3401F1CD.AF4439B4@umich.edu> Date: Mon, 25 Aug 1997 16:57:49 -0400 From: Sasha Kacanski X-Mailer: Mozilla 4.01 [en] (WinNT; I) MIME-Version: 1.0 To: "hardware@FreeBSD.ORG" Subject: ISDN X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, I have a bit off question that you might be able to help me with. I want to hook up two Pentium computers to ISDN. Solution is an ISDN router which is around $600. Two reach for my blood. Now, if I get a TA with two serial ports I would be able to split 128k line and use both computers. It is cheaper and we will never have more than two computers in the house. Problem: Serial cable needs to be long to get to second machine. My question would be. Could I by a serial jack and hookup a RJ11 cable to it (connect the wires to the serial pins) and extend that way cable to second computer. Simple, how to avoid to by serial cable which is very expensive and how to connect second machine that is 50 feet away. Also maybe getting a old 10baseT hub and connecting it to a single TA would solve the problem. If anyone has any other idea please let me know. very grateful /s From owner-freebsd-hardware Mon Aug 25 15:31:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA16360 for hardware-outgoing; Mon, 25 Aug 1997 15:31:17 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA16354 for ; Mon, 25 Aug 1997 15:31:14 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA10754; Mon, 25 Aug 1997 15:21:03 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd010731; Mon Aug 25 22:20:54 1997 Message-ID: <3402053D.19A13460@whistle.com> Date: Mon, 25 Aug 1997 15:20:45 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Dan Welch CC: HARDWARE@FreeBSD.ORG Subject: Re: graphics terminals References: <970825170115.24a254a3@wofford.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Dan Welch wrote: > > What's a good brand and model modest graphics terminal to use with > FreeBSD? Something durable under heavy use and runs on a simple > serial link. Monchrome is ok, color would be nice. Not critical. another freeBSD PC running X11? what speed serial? there is of course the tek compatibility stuff i don't know if there is software to run that much any more.. From owner-freebsd-hardware Mon Aug 25 17:58:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA25665 for hardware-outgoing; Mon, 25 Aug 1997 17:58:47 -0700 (PDT) Received: from TRUTH.WOFFORD.EDU (truth.wofford.edu [199.190.174.30]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA25650 for ; Mon, 25 Aug 1997 17:58:32 -0700 (PDT) Date: Mon, 25 Aug 1997 20:58:04 -0400 From: Dan Welch To: julian@whistle.com CC: HARDWARE@FREEBSD.org, WELCHDW@wofford.edu Message-Id: <970825205804.24a234fb@wofford.edu> Subject: Re: graphics terminals Sender: owner-freebsd-hardware@FREEBSD.org X-Loop: FreeBSD.org Precedence: bulk >> What's a good brand and model modest graphics terminal to use with >> FreeBSD? Something durable under heavy use and runs on a simple >> serial link. Monchrome is ok, color would be nice. Not critical. > > another freeBSD PC running X11? > what speed serial? > there is of course the tek compatibility stuff > i don't know if there is software to run that much any more.. I have been recycling old PC's as serial terminals to FreeBSD by running Kermit on them. They run at 9600bps mostly, and Kermit's Tek emulation gives decent 720x348 graphics. I also run some old vt10[012]'s and so forth, even a few genuine Tektronix units. Having a bunch of serial terminals proves to be a useful adjunct to the workstation network. The terminals come up quickly and require little maintenance. For the more public areas, these simple terminals seem more secure because they have no disks and no direct network link. I'd like to get some more and newer, but with a bit of graphics support for basic data analysis so they could do at least as well as Kermit. Software is not a problem for us so long as adequate documentation for the terminal can be found. From owner-freebsd-hardware Mon Aug 25 18:55:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA27723 for hardware-outgoing; Mon, 25 Aug 1997 18:55:28 -0700 (PDT) Received: from MindBender.serv.net (mindbender.serv.net [205.153.153.98]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA27716 for ; Mon, 25 Aug 1997 18:55:24 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id SAA15589; Mon, 25 Aug 1997 18:54:43 -0700 (PDT) Message-Id: <199708260154.SAA15589@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Dan Welch cc: HARDWARE@freebsd.org Subject: Re: graphics terminals In-reply-to: Your message of Mon, 25 Aug 97 17:01:15 -0400. <970825170115.24a254a3@wofford.edu> Date: Mon, 25 Aug 1997 18:54:43 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >What's a good brand and model modest graphics terminal to use with >FreeBSD? Something durable under heavy use and runs on a simple >serial link. Monchrome is ok, color would be nice. Not critical. An old PC-XT or 286 running MS-DOS Kermit? ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-hardware Tue Aug 26 07:48:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA14496 for hardware-outgoing; Tue, 26 Aug 1997 07:48:19 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA14491; Tue, 26 Aug 1997 07:48:16 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id AAA04055; Wed, 27 Aug 1997 00:40:24 +1000 Date: Wed, 27 Aug 1997 00:40:24 +1000 From: Bruce Evans Message-Id: <199708261440.AAA04055@godzilla.zeta.org.au> To: bde@zeta.org.au, msmith@atrad.adelaide.edu.au Subject: Re: Parallel port developpements - ppbus Cc: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG, Nicolas.Souchu@prism.uvsq.fr, phk@critter.dk.tfs.com Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> >>[plip driver] >> ... >> >[in dev/ppbus/if_lp.c] >> >> It makes no sense to put it there either, since sys/dev is for >> bus-independent (parts of) drivers. > >Well, then I'd better move the ppbus stuff. It makes no sense to me >to have Yet Another toplevel directory for this though, and sys/dev >strikes me as being the ideal place for architecture-independent >device drivers. > >Any consensus on this? No :-). If /sys/de/ is ideal for arch-independent drivers, why put arch-dependent drivers in it? (ppbus/*.c is apparently arch-dependent because it includes files from i386/isa.) Bruce From owner-freebsd-hardware Tue Aug 26 09:22:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA18896 for hardware-outgoing; Tue, 26 Aug 1997 09:22:15 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA18848; Tue, 26 Aug 1997 09:22:00 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0x3ON3-0002uh-00; Tue, 26 Aug 1997 10:21:33 -0600 To: Bruce Evans Subject: Re: Parallel port developpements - ppbus Cc: msmith@atrad.adelaide.edu.au, freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org, Nicolas.Souchu@prism.uvsq.fr, phk@critter.dk.tfs.com In-reply-to: Your message of "Wed, 27 Aug 1997 00:40:24 +1000." <199708261440.AAA04055@godzilla.zeta.org.au> References: <199708261440.AAA04055@godzilla.zeta.org.au> Date: Tue, 26 Aug 1997 10:21:33 -0600 From: Warner Losh Message-Id: Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199708261440.AAA04055@godzilla.zeta.org.au> Bruce Evans writes: : If /sys/de/ is ideal for arch-independent drivers, why put arch-dependent : drivers in it? (ppbus/*.c is apparently arch-dependent because it includes : files from i386/isa.) But there is no arch-independent isa include files in the tree right now, so I wouldn't count that against the ppbus code just yet. I suspect that in the future there will be a-i versions of these files as the Alpha project gets rolling. Warner From owner-freebsd-hardware Tue Aug 26 09:51:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA21051 for hardware-outgoing; Tue, 26 Aug 1997 09:51:21 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA21037; Tue, 26 Aug 1997 09:51:17 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id CAA08250; Wed, 27 Aug 1997 02:50:15 +1000 Date: Wed, 27 Aug 1997 02:50:15 +1000 From: Bruce Evans Message-Id: <199708261650.CAA08250@godzilla.zeta.org.au> To: bde@zeta.org.au, imp@rover.village.org Subject: Re: Parallel port developpements - ppbus Cc: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG, msmith@atrad.adelaide.edu.au, Nicolas.Souchu@prism.uvsq.fr, phk@critter.dk.tfs.com Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >: If /sys/de/ is ideal for arch-independent drivers, why put arch-dependent >: drivers in it? (ppbus/*.c is apparently arch-dependent because it includes >: files from i386/isa.) I really meant (arch || bus)-dependent. >But there is no arch-independent isa include files in the tree right >now, so I wouldn't count that against the ppbus code just yet. I That's partly because isa is bus-dependent by definition, and partly the fault of the committer for not re-engineering the include files - if you want to put things in a new place then you get to implement the support for it. The old place (under isa) may be wrong, but its just as easy to move things from there as from a wrong new place (not easy). Bruce From owner-freebsd-hardware Tue Aug 26 11:27:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA27866 for hardware-outgoing; Tue, 26 Aug 1997 11:27:25 -0700 (PDT) Received: from DonaldBurr.DonaldBurr.dyn.ml.org (ppp10210.la.inreach.net [206.18.112.210]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA27847; Tue, 26 Aug 1997 11:27:17 -0700 (PDT) Received: from localhost (dburr@localhost) by DonaldBurr.DonaldBurr.dyn.ml.org (8.8.5/8.8.5) with SMTP id LAA03404; Tue, 26 Aug 1997 11:27:54 -0700 (PDT) X-Authentication-Warning: DonaldBurr.DonaldBurr.dyn.ml.org: dburr owned process doing -bs Date: Tue, 26 Aug 1997 11:27:53 -0700 (PDT) From: Donald Burr X-Sender: dburr@DonaldBurr.DonaldBurr.dyn.ml.org To: FreeBSD SCSI cc: FreeBSD Hardware , AIC7xxx List Subject: AHA-2940AU (aic7860) and weird error messages on SCSI hd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just installed a SCSI disk into my machine. It's an older Conner 540MB drive (CP3540), but this drive has been serving me well in another machine. I have it partitioned into a ~150MB /home partition, a ~32MB auxiliary swap partition, and two other partitions (one ~200MB and one ~150MB) that are currently not in use. Anyway, after I installed and partitioned this disk, I started to get these error messages both on my console (in bright white letters) and in my syslogs. These messages do not cause a kernel panic or something, and the system seems to run well despite them. Since seeing the first message I've been making hourly backups of my /home partition and comparing them, and all the data compares OK. Visually inspecting the files in /home shows no errors either. What could be going on here? Any ideas? I have already checked SCSI IDs and termination, and everything is A-OK. Please respond by e-mail if possible. Thanks! OS: FreeBSD 2.2.2-RELEASE running on a home-grown (i.e. clone) 486DX4/133 PCI motherboard. Other PCI devices: Cirrus Logic CL-GD5440 clone video board, and clone NE2000 Ethernet board (realtek 8029, I think). dmesg output: ============= ahc0 rev 1 int a irq 11 on pci0:13 ahc0: aic7860 Single Channel, SCSI Id=7, 3/8 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "CONNER CP3500-540MB-3.5 3231" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 518MB (1062516 512 byte sectors) (ahc0:1:0): "NEC CD-ROM DRIVE:462 1.16" type 5 removable SCSI 2 cd0(ahc0:1:0): CD-ROM cd present [328355 x 2048 byte records] ahc0: target 2 Tagged Queuing Device (ahc0:2:0): "iomega jaz 1GB H.72" type 0 removable SCSI 2 sd1(ahc0:2:0): Direct-Access sd1(ahc0:2:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd1 could not mode sense (4). Using ficticious geometry sd1(ahc0:2:0): NOT READY asc:3a,0 Medium not present sd1: could not get size 0MB (0 512 byte sectors) error messages: =============== Aug 26 11:09:27 DonaldBurr /kernel: sd0(ahc0:0:0): SCB 4 - Abort Completed. Aug 26 11:09:27 DonaldBurr /kernel: sd0(ahc0:0:0): no longer in timeout Aug 26 11:10:26 DonaldBurr /kernel: sd0(ahc0:0:0): SCB 0x2 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Aug 26 11:10:26 DonaldBurr /kernel: SEQADDR = 0x9 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Aug 26 11:10:26 DonaldBurr /kernel: sd0(ahc0:0:0): Queueing an Abort SCB Aug 26 11:10:27 DonaldBurr /kernel: sd0(ahc0:0:0): Abort Message Sent Aug 26 11:10:27 DonaldBurr /kernel: sd0(ahc0:0:0): SCB 2 - Abort Completed. Aug 26 11:10:27 DonaldBurr /kernel: sd0(ahc0:0:0): no longer in timeout Aug 26 11:16:27 DonaldBurr /kernel: sd0(ahc0:0:0): SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Aug 26 11:16:27 DonaldBurr /kernel: SEQADDR = 0x9 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Aug 26 11:16:27 DonaldBurr /kernel: sd0(ahc0:0:0): Queueing an Abort SCB Aug 26 11:16:27 DonaldBurr /kernel: sd0(ahc0:0:0): Abort Message Sent Aug 26 11:16:27 DonaldBurr /kernel: sd0(ahc0:0:0): SCB 3 - Abort Completed. Aug 26 11:16:27 DonaldBurr /kernel: sd0(ahc0:0:0): no longer in timeout Aug 26 11:17:07 DonaldBurr /kernel: sd0(ahc0:0:0): SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Aug 26 11:17:07 DonaldBurr /kernel: SEQADDR = 0x4 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Aug 26 11:17:07 DonaldBurr /kernel: sd0(ahc0:0:0): Queueing an Abort SCB Aug 26 11:17:07 DonaldBurr /kernel: sd0(ahc0:0:0): Abort Message Sent Aug 26 11:17:07 DonaldBurr /kernel: sd0(ahc0:0:0): SCB 3 - Abort Completed. Aug 26 11:17:07 DonaldBurr /kernel: sd0(ahc0:0:0): no longer in timeout 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. From owner-freebsd-hardware Tue Aug 26 12:24:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA01650 for hardware-outgoing; Tue, 26 Aug 1997 12:24:49 -0700 (PDT) Received: from fly.HiWAAY.net (dkelly@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA01591; Tue, 26 Aug 1997 12:23:54 -0700 (PDT) Received: (from dkelly@localhost) by fly.HiWAAY.net (8.8.6/8.8.6) id OAA05878; Tue, 26 Aug 1997 14:23:45 -0500 (CDT) Date: Tue, 26 Aug 1997 14:23:45 -0500 (CDT) From: David Kelly Message-Id: <199708261923.OAA05878@fly.HiWAAY.net> To: dburr@POBoxes.com, freebsd-scsi@FreeBSD.ORG Subject: Re: AHA-2940AU (aic7860) and weird error messages on SCSI hd Cc: , , AIC7xxx@POBoxes.com, FreeBSD@POBoxes.com, Hardware@POBoxes.com, List@POBoxes.com Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Donald Burr writes: > > I just installed a SCSI disk into my machine. It's an older Conner 540MB > drive (CP3540), but this drive has been serving me well in another > machine. I have it partitioned into a ~150MB /home partition, a ~32MB > auxiliary swap partition, and two other partitions (one ~200MB and one > ~150MB) that are currently not in use. > > Anyway, after I installed and partitioned this disk, I started to get > these error messages both on my console (in bright white letters) and in > my syslogs. These messages do not cause a kernel panic or something, and > the system seems to run well despite them. Since seeing the first message > I've been making hourly backups of my /home partition and comparing them, > and all the data compares OK. Visually inspecting the files in /home > shows no errors either. > > What could be going on here? Any ideas? I have already checked SCSI IDs > and termination, and everything is A-OK. [snip] I have a 5x86/133-P75 MB which also caused troubles with an Adaptec 2940 (a very old 2940). The failures were similar, altho mine were often fatal. The solution was to either 1) disable the external MB cache or 2) use write-thru mode on the cache rather than write-back. If the system would stay running, write back cache was a couple of % faster than write-thru. Write-thru was about 10% faster than nothing. Guess how its been running the past year? :-) Another system didn't like tagged queuing. You might disable that and see how it works. My tagged queuing problem system looks like: ahc0 rev 1 int a irq 11 on pci0:15 ahc0: aic7860 Single Channel, SCSI Id=7, 3/8 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "IBM DPES-31080 !t S31K" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 1034MB (2118144 512 byte sectors) (ahc0:3:0): "MAXTOR 7213-SCSI 0742" type 0 fixed SCSI 1 sd1(ahc0:3:0): Direct-Access 202MB (415600 512 byte sectors) Had no problem until I partitioned the Maxtor and started using it. Dmesg didn't indicate the kernel was going to use tagged queuing on the Maxtor. Kernel simply paniced and rebooted. But that's another story. -- David Kelly N4HHE, dkelly@hiwaay.net (hm) ====================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. From owner-freebsd-hardware Tue Aug 26 15:44:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA13981 for hardware-outgoing; Tue, 26 Aug 1997 15:44:38 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA13972; Tue, 26 Aug 1997 15:44:27 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id IAA01587; Wed, 27 Aug 1997 08:12:50 +0930 (CST) Message-Id: <199708262242.IAA01587@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Bruce Evans cc: msmith@atrad.adelaide.edu.au, freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG, Nicolas.Souchu@prism.uvsq.fr, phk@critter.dk.tfs.com Subject: Re: Parallel port developpements - ppbus In-reply-to: Your message of "Wed, 27 Aug 1997 00:40:24 +1000." <199708261440.AAA04055@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 Aug 1997 08:12:48 +0930 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >> > >> It makes no sense to put it there either, since sys/dev is for > >> bus-independent (parts of) drivers. > > > >Well, then I'd better move the ppbus stuff. It makes no sense to me > >to have Yet Another toplevel directory for this though, and sys/dev > >strikes me as being the ideal place for architecture-independent > >device drivers. > > > >Any consensus on this? > > No :-). > > If /sys/de/ is ideal for arch-independent drivers, why put arch-dependent > drivers in it? (ppbus/*.c is apparently arch-dependent because it includes > files from i386/isa.) This is a bug, and I am embarrassed to say that it has slipped down my list of must-fixes. None of the ppbus stuff *should* be arch-dependant in any way. mike From owner-freebsd-hardware Wed Aug 27 09:26:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA12674 for hardware-outgoing; Wed, 27 Aug 1997 09:26:00 -0700 (PDT) Received: from mail.calweb.com (mail.calweb.com [208.131.56.11]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA12669 for ; Wed, 27 Aug 1997 09:25:54 -0700 (PDT) Received: by mail.calweb.com (8.8.6/8.8.6) with ESMTP id JAA15343; Wed, 27 Aug 1997 09:25:52 -0700 (PDT) X-SMTP: hello admin3.calweb.com from cslye@calweb.com server cslye@admin3.calweb.com ip 208.131.56.111 ident=cslye Received: (from cslye@localhost) by admin3.calweb.com (8.8.5/8.8.5) id RAA12246; Wed, 27 Aug 1997 17:25:53 -0700 (PDT) Message-Id: <199708280025.RAA12246@admin3.calweb.com> Subject: Re: K6-200 Has anyone successfully done a 'make world' ? To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Wed, 27 Aug 1997 17:25:53 -0700 (PDT) From: "Cameron Slye" Cc: hardware@FreeBSD.ORG In-Reply-To: <19970823004520.28925@keltia.freenix.fr> from "Ollivier Robert" at Aug 23, 97 00:45:20 am X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I've only a 166 MHz but I've made several "make world" without problems. How much memory is in that box ? I have a asus p55t2p4 here, with a 166 in it. 25 make worlds finished with only 32mb in 2 slots, but with 64mb in 4 slots, it died in the first make world. (sig 11) From owner-freebsd-hardware Wed Aug 27 10:27:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA17016 for hardware-outgoing; Wed, 27 Aug 1997 10:27:07 -0700 (PDT) Received: from bmccane.uit.net (bmccane.uit.net [209.83.205.48]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA16961 for ; Wed, 27 Aug 1997 10:26:12 -0700 (PDT) Received: from bmccane.uit.net (localhost.mccane.com [127.0.0.1]) by bmccane.uit.net (8.8.7/8.8.5) with ESMTP id MAA26331; Wed, 27 Aug 1997 12:24:45 -0500 (CDT) Message-Id: <199708271724.MAA26331@bmccane.uit.net> X-Mailer: exmh version 2.0gamma 1/27/96 To: Tom Samplonius cc: hardware@FreeBSD.ORG Subject: Re: ISDN Modems In-reply-to: Your message of "Fri, 15 Aug 1997 09:30:20 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 Aug 1997 12:24:44 -0500 From: Wm Brian McCane Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > On Fri, 15 Aug 1997, Wm Brian McCane wrote: > > > Hello, > > I am looking for a list of ISDN modems that are supported by FreeBSD > > 2.1.5 or 3.0, but I hate to have to modify skip to work with 3.0 since the > > customer this is for won't absorb the cost. I would prefer a modem that has > > compression capabilities and would allow a greater than 128K feed to go to it, > > for example 512K to allow better compression. I have been looking at some of > > the Ascend equipment, but I think I could get by cheaper using a FreeBSD box > > as my router, and running skip in the kernel. > > > > brian > > The 3COM Impact II is nice. However, FreeBSD has poor support for the > high speed serial ports (230400 bps) that you need to drive these things > properly. > > You can get serial cards with a jumper that doubles the rate internally > on the card. So FreeBSD thinks the card is running at 115200, but it > really running at 230400. > > Tom > Sorry it has taken me so long to reply, my wife told me to "quit reading mail and earn some money!!!" Do you know which boards are capable of doing the doubled clock rate? Also, do they use a 16??? with a larger FIFO to reduce the interrupt overhead? I seem to remember seeing something in the sio driver about a newer 16550 chip with a large FIFO (is this right?) brian From owner-freebsd-hardware Wed Aug 27 10:41:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA18194 for hardware-outgoing; Wed, 27 Aug 1997 10:41:08 -0700 (PDT) Received: from hobbes.saturn-tech.com (drussell@[198.161.228.154]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA18184 for ; Wed, 27 Aug 1997 10:41:05 -0700 (PDT) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id LAA05270; Wed, 27 Aug 1997 11:40:26 -0600 (MDT) Date: Wed, 27 Aug 1997 11:40:25 -0600 (MDT) From: Doug Russell Reply-To: Doug Russell To: Cameron Slye cc: Ollivier Robert , hardware@FreeBSD.ORG Subject: Re: K6-200 Has anyone successfully done a 'make world' ? In-Reply-To: <199708280025.RAA12246@admin3.calweb.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 27 Aug 1997, Cameron Slye wrote: > How much memory is in that box ? I have a asus p55t2p4 here, with a 166 in > it. 25 make worlds finished with only 32mb in 2 slots, but with 64mb in 4 > slots, it died in the first make world. (sig 11) Did you try putting the extra 2 SIMMs in as the only set to see if the SIMMs were at fault? Later...... From owner-freebsd-hardware Wed Aug 27 14:26:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA08662 for hardware-outgoing; Wed, 27 Aug 1997 14:26:24 -0700 (PDT) Received: from lariat.lariat.org (ppp0.lariat.org@[129.72.251.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA08644 for ; Wed, 27 Aug 1997 14:26:19 -0700 (PDT) Received: from solo ([129.72.251.10] (may be forged)) by lariat.lariat.org (8.8.6/8.8.6) with SMTP id PAA04563 for ; Wed, 27 Aug 1997 15:23:18 -0600 (MDT) Message-Id: <3.0.3.32.19970827152511.00901750@mail.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 27 Aug 1997 15:25:11 -0600 To: hardware@freebsd.org From: Brett Glass Subject: Which PCMCIA Ethernet adapters are WELL-supported? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Am looking for a PCMCIA Ethernet adapter that's compatible with FreeBSD. I understand there are drivers for the 3Com 3C589, but I've had trouble with 3Com adapters in this machine and am looking for another brand. Will anything from Intel work? How about Xircom? Others? An adapter that can step up to 100BaseT would be useful, though it's not absolutely essential. --Brett Glass From owner-freebsd-hardware Wed Aug 27 14:34:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA10353 for hardware-outgoing; Wed, 27 Aug 1997 14:34:52 -0700 (PDT) Received: from cdf.computone.com (cdf.computone.com [160.77.62.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA10311; Wed, 27 Aug 1997 14:34:43 -0700 (PDT) From: c_fowler@hotmail.com Received: from cdf.computone.com (localhost [127.0.0.1]) by cdf.computone.com (8.8.5/8.8.5) with SMTP id RAA01582; Wed, 27 Aug 1997 17:32:35 -0400 Message-ID: X-Mailer: XFMail 1.1 [p0] on Linux Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 27 Aug 1997 17:28:00 -0400 (EDT) Organization: Computone.com To: freebsd-hardware@freebsd.org, freebsd-questions@freebsd.org Subject: Terminal Servers Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I'm not trying to spam your newsgroup, I just wanted to let everyone in the UNIX community know of a great deal on Computone Terminal Servers. Until Freiday, All 16 port PowerRacks are $1300 they were $2197. This deal is going on until this Friday our until our stock runs out. We just got a shipment from our distributor and need to sell them as fast as possible. After Friday t hey will go up to $2197. These will work under any unix flavor. each 16 port ex pansion cards are on sale for $445. Thanks, Christopher Fowler Computone Corporation 8002413946 x220 ---------------------------------- E-Mail: c_fowler@hotmail.com Date: 27-Aug-97 Time: 17:28:01 This message was sent by XFMail ---------------------------------- From owner-freebsd-hardware Wed Aug 27 17:16:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA20170 for hardware-outgoing; Wed, 27 Aug 1997 17:16:07 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA20100 for ; Wed, 27 Aug 1997 17:15:54 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id JAA02206; Thu, 28 Aug 1997 09:44:18 +0930 (CST) Message-Id: <199708280014.JAA02206@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brett Glass cc: hardware@freebsd.org Subject: Re: Which PCMCIA Ethernet adapters are WELL-supported? In-reply-to: Your message of "Wed, 27 Aug 1997 15:25:11 CST." <3.0.3.32.19970827152511.00901750@mail.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 Aug 1997 09:44:16 +0930 From: Mike Smith Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Am looking for a PCMCIA Ethernet adapter that's compatible with FreeBSD. I > understand there are drivers for the 3Com 3C589, but I've had trouble with > 3Com adapters in this machine and am looking for another brand. Will > anything from Intel work? How about Xircom? Others? An adapter that can > step up to 100BaseT would be useful, though it's not absolutely essential. I don't know of any 100bT adapters, I 'fess, however the Accton EN2216 is a non-3Com card that's known to work very well (NE2000 clone). mike From owner-freebsd-hardware Wed Aug 27 18:45:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA29057 for hardware-outgoing; Wed, 27 Aug 1997 18:45:56 -0700 (PDT) Received: from tok.qiv.com ([204.214.141.211]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA29050 for ; Wed, 27 Aug 1997 18:45:52 -0700 (PDT) Received: (from uucp@localhost) by tok.qiv.com (8.8.6/8.8.5) with UUCP id UAA19711; Wed, 27 Aug 1997 20:45:32 -0500 (CDT) Received: from localhost (jdn@localhost) by acp.qiv.com (8.8.6/8.8.5) with SMTP id UAA00667; Wed, 27 Aug 1997 20:37:22 -0500 (CDT) X-Authentication-Warning: acp.qiv.com: jdn owned process doing -bs Date: Wed, 27 Aug 1997 20:37:22 -0500 (CDT) From: "Jay D. Nelson" To: Cameron Slye cc: hardware@FreeBSD.ORG Subject: Re: K6-200 Has anyone successfully done a 'make world' ? In-Reply-To: <199708280025.RAA12246@admin3.calweb.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Did you upgrade the bios to support the chip? I just installed this board with a K5-166 -- clocked it at 66Mhz*2 because I wasn't sure. Works fine at 133Mhz though the bios thinks it's 100Mhz. I'm about to upgrade the bios but would rather not. Why wouldn't 66Mhz*2.5 work as well? My bios right now is *-0109. Is there anything peculiar about K5s above 133Mhz? -- Jay On Wed, 27 Aug 1997, Cameron Slye wrote: >> >> I've only a 166 MHz but I've made several "make world" without problems. > >How much memory is in that box ? I have a asus p55t2p4 here, with a 166 in >it. 25 make worlds finished with only 32mb in 2 slots, but with 64mb in 4 >slots, it died in the first make world. (sig 11) > From owner-freebsd-hardware Wed Aug 27 20:28:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA03761 for hardware-outgoing; Wed, 27 Aug 1997 20:28:43 -0700 (PDT) Received: from www2.shoppersnet.com (shoppersnet.com [204.156.152.112]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA03755 for ; Wed, 27 Aug 1997 20:28:32 -0700 (PDT) Received: (from hlew@localhost) by www2.shoppersnet.com (8.8.5/8.8.5) id UAA24145; Wed, 27 Aug 1997 20:35:32 -0700 (PDT) Date: Wed, 27 Aug 1997 20:35:32 -0700 (PDT) From: Howard Lew To: "Jay D. Nelson" cc: Cameron Slye , hardware@FreeBSD.ORG Subject: Re: K6-200 Has anyone successfully done a 'make world' ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 27 Aug 1997, Jay D. Nelson wrote: > Did you upgrade the bios to support the chip? I just installed this > board with a K5-166 -- clocked it at 66Mhz*2 because I wasn't sure. > Works fine at 133Mhz though the bios thinks it's 100Mhz. I'm about to > upgrade the bios but would rather not. Why wouldn't 66Mhz*2.5 work as > well? My bios right now is *-0109. Is there anything peculiar about > K5s above 133Mhz? > When you clock a K5-166 at 66x2 you are slowing it down to K5-133 speed because the K5-133 runs at 100MHz. The K5-166 should be jumpered for 166MHz like a Pentium (66 x 2.5). The circuits inside the chip will modify it to 1.75. The only way to overclock a K5 is to use a higher bus clock (i.e. 75MHz) because of the way the clock multiplier on the K5 works. 75MHz will generally work, but 83MHz will not. At 75MHz bus clock, the K5-166 will be probed and run at or almost at Pentium 200 speeds. Stability is questionable though and depending on whether your MB supports async PCI, 37.5MHz may be too high for some PCI SCSI cards. > -- Jay > > On Wed, 27 Aug 1997, Cameron Slye wrote: > > >> > >> I've only a 166 MHz but I've made several "make world" without problems. > > > >How much memory is in that box ? I have a asus p55t2p4 here, with a 166 in > >it. 25 make worlds finished with only 32mb in 2 slots, but with 64mb in 4 > >slots, it died in the first make world. (sig 11) > > > > From owner-freebsd-hardware Wed Aug 27 21:13:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA05560 for hardware-outgoing; Wed, 27 Aug 1997 21:13:22 -0700 (PDT) Received: from tok.qiv.com ([204.214.141.211]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA05553 for ; Wed, 27 Aug 1997 21:13:17 -0700 (PDT) Received: (from uucp@localhost) by tok.qiv.com (8.8.6/8.8.5) with UUCP id XAA19934; Wed, 27 Aug 1997 23:13:02 -0500 (CDT) Received: from localhost (jdn@localhost) by acp.qiv.com (8.8.6/8.8.5) with SMTP id XAA01054; Wed, 27 Aug 1997 23:07:13 -0500 (CDT) X-Authentication-Warning: acp.qiv.com: jdn owned process doing -bs Date: Wed, 27 Aug 1997 23:07:13 -0500 (CDT) From: "Jay D. Nelson" To: Howard Lew cc: hardware@FreeBSD.ORG Subject: Q: K5 clock speeds (Was: Re: K6-200 Has anyone ...) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thanks for the info. What you are suggesting is that the clock is the only thing that counts and moving the jumper to x2.5 is all that's necessary -- regardless of the bios. Why would ASUS issue a bios upgrade to support 150-166Mhz K5s? (Marketing?) -- Jay On Wed, 27 Aug 1997, Howard Lew wrote: >On Wed, 27 Aug 1997, Jay D. Nelson wrote: > >> Did you upgrade the bios to support the chip? I just installed this >> board with a K5-166 -- clocked it at 66Mhz*2 because I wasn't sure. >> Works fine at 133Mhz though the bios thinks it's 100Mhz. I'm about to >> upgrade the bios but would rather not. Why wouldn't 66Mhz*2.5 work as >> well? My bios right now is *-0109. Is there anything peculiar about >> K5s above 133Mhz? >> > >When you clock a K5-166 at 66x2 you are slowing it down to K5-133 speed >because the K5-133 runs at 100MHz. The K5-166 should be jumpered for >166MHz like a Pentium (66 x 2.5). The circuits inside the chip will >modify it to 1.75. > >The only way to overclock a K5 is to use a higher bus clock (i.e. 75MHz) >because of the way the clock multiplier on the K5 works. 75MHz will >generally work, but 83MHz will not. At 75MHz bus clock, the K5-166 will >be probed and run at or almost at Pentium 200 speeds. Stability is >questionable though and depending on whether your MB supports async PCI, >37.5MHz may be too high for some PCI SCSI cards. > > >> -- Jay >> >> On Wed, 27 Aug 1997, Cameron Slye wrote: >> >> >> >> >> I've only a 166 MHz but I've made several "make world" without problems. >> > >> >How much memory is in that box ? I have a asus p55t2p4 here, with a 166 in >> >it. 25 make worlds finished with only 32mb in 2 slots, but with 64mb in 4 >> >slots, it died in the first make world. (sig 11) >> > >> From owner-freebsd-hardware Wed Aug 27 22:54:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA09834 for hardware-outgoing; Wed, 27 Aug 1997 22:54:39 -0700 (PDT) Received: from MindBender.serv.net (root@mindbender.serv.net [205.153.153.98]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA09829 for ; Wed, 27 Aug 1997 22:54:34 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id WAA02625; Wed, 27 Aug 1997 22:54:02 -0700 (PDT) Message-Id: <199708280554.WAA02625@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Jay D. Nelson" cc: Howard Lew , hardware@freebsd.org Subject: Re: Q: K5 clock speeds (Was: Re: K6-200 Has anyone ...) In-reply-to: Your message of Wed, 27 Aug 97 23:07:13 -0500. Date: Wed, 27 Aug 1997 22:53:12 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Thanks for the info. What you are suggesting is that the clock is the >only thing that counts and moving the jumper to x2.5 is all that's >necessary -- regardless of the bios. Why would ASUS issue a bios >upgrade to support 150-166Mhz K5s? (Marketing?) How could it be marketing? They don't make money on BIOS upgrades. I suspect it has to do with tuning the chipsets correctly to work with the specific timing requirements of the K6. I have an Asus P55TP4N, the Triton-1 board just before Triton-2 came out. I bought it originally with a Pentium 100MHz CPU. It ran NetBSD just great for about a year. Later, I decided to put a Cyrix 6x86 P166+ in it. I plugged the chip in, and it booted, but it would get sig 11's constantly, and eventually panic. I wasn't sure if I had a bad chip, or a bad motherboard, or what. But verified it worked correctly with the Pentium. I was getting ready to send the Cyrix chip back when I checked the Asus web site, and found that a BIOS upgrade was recommended. I downloaded the BIOS, flashed it, and rebooted. The machine consequently proceeded to give my over 90 days solid uptime, before I accidently made my UPS shutdown while doing a reinstall of Win95 on my NT/95/Decsent box. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net Contract software development for Windows NT, Windows 95 and Unix. Windows NT and Unix server development in C++ and C. --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-hardware Thu Aug 28 00:50:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA15370 for hardware-outgoing; Thu, 28 Aug 1997 00:50:44 -0700 (PDT) Received: from hcshh.hcs.de (hcshh.hcs.de [194.49.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA15351; Thu, 28 Aug 1997 00:50:35 -0700 (PDT) Received: from hcswork.hcs.de(really [192.76.124.5]) by hcshh.hcs.de via sendmail with smtp id for ; Thu, 28 Aug 1997 09:50:29 +0200 (METDST) (Smail-3.2.0.91 1997-Jan-14 #3 built 1997-Apr-8) Received: by hcswork.hcs.de (Smail3.1.29.0 #12) id m0x3zLh-0000c4C; Thu, 28 Aug 97 09:50 METDST Message-Id: From: hm@hcs.de (Hellmuth Michaelis) Subject: Re: Terminal Servers To: c_fowler@hotmail.com Date: Thu, 28 Aug 1997 09:50:37 +0200 (METDST) Cc: freebsd-hardware@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG In-Reply-To: from "c_fowler@hotmail.com" at "Aug 27, 97 05:28:00 pm" Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL15 (25)] Content-Type: text Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >From the keyboard of c_fowler@hotmail.com: > I'm not trying to spam your newsgroup, I just wanted to let everyone in the > UNIX community know of a great deal on Computone Terminal Servers. I am not a murder. I just wear a knife and want to try it out. I never ever will even think about buying something from Computone. hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm@hcs.de 22457 Hamburg WWW http://www.hcs.de From owner-freebsd-hardware Thu Aug 28 03:58:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA21763 for hardware-outgoing; Thu, 28 Aug 1997 03:58:15 -0700 (PDT) Received: from MVS.OAC.UCLA.EDU (mvs.oac.ucla.edu [164.67.200.200]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id DAA21758 for ; Thu, 28 Aug 1997 03:58:11 -0700 (PDT) Message-Id: <199708281058.DAA21758@hub.freebsd.org> Received: from UCLAMVS.BITNET by MVS.OAC.UCLA.EDU (IBM MVS SMTP V2R2.1) with BSMTP id 0666; Thu, 28 Aug 97 03:59:09 PST Date: Thu, 28 Aug 97 03:59 PDT To: Mike Smith From: Denis DeLaRoca Subject: Re: Re: Which PCMCIA Ethernet adapters are WELL-supported? CC: hardware@FREEBSD.ORG Sender: owner-freebsd-hardware@FREEBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 28 Aug 1997 09:44:16 +0930, Mike Smith said: > > I don't know of any 100bT adapters, I 'fess, however the Accton EN2216 > is a non-3Com card that's known to work very well (NE2000 clone). Any idea what the Hitachi VisionBook notebooks have for their onboard ethernet support? -- Denis From owner-freebsd-hardware Thu Aug 28 04:06:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA21992 for hardware-outgoing; Thu, 28 Aug 1997 04:06:16 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA21984 for ; Thu, 28 Aug 1997 04:05:53 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id UAA05007; Thu, 28 Aug 1997 20:33:22 +0930 (CST) Message-Id: <199708281103.UAA05007@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Denis DeLaRoca cc: Mike Smith , hardware@FREEBSD.ORG Subject: Re: Which PCMCIA Ethernet adapters are WELL-supported? In-reply-to: Your message of "Thu, 28 Aug 1997 03:59:00 PDT." <199708281058.UAA27423@silver.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 Aug 1997 20:33:21 +0930 From: Mike Smith Sender: owner-freebsd-hardware@FREEBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I don't know of any 100bT adapters, I 'fess, however the Accton EN2216 > > is a non-3Com card that's known to work very well (NE2000 clone). > > Any idea what the Hitachi VisionBook notebooks have for their onboard > ethernet support? No; send me one and I'll tell you 8) mike From owner-freebsd-hardware Thu Aug 28 08:17:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA03640 for hardware-outgoing; Thu, 28 Aug 1997 08:17:05 -0700 (PDT) Received: from persprog.com (root@persprog.com [204.215.255.203]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA03617 for ; Thu, 28 Aug 1997 08:16:51 -0700 (PDT) Received: by persprog.com (8.7.5/4.10) id JAA09340; Thu, 28 Aug 1997 09:54:20 -0500 Received: from dave.ppi.com(192.2.2.6) by cerberus.ppi.com via smap (V1.3) id sma009326; Thu Aug 28 10:53:52 1997 Message-ID: <34059102.95F788BE@persprog.com> Date: Thu, 28 Aug 1997 10:53:54 -0400 From: Dave Alderman Reply-To: dave@persprog.com Organization: Personalized Programming, Inc X-Mailer: Mozilla 4.0 [en] (Win95; U) MIME-Version: 1.0 To: "Michael L. VanLoon -- HeadCandy.com" CC: "Jay D. Nelson" , Howard Lew , hardware@FreeBSD.ORG Subject: Re: Q: K5 clock speeds (Was: Re: K6-200 Has anyone ...) X-Priority: 3 (Normal) References: <199708280554.WAA02625@MindBender.serv.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Michael L. VanLoon -- HeadCandy.com wrote: > > I have an Asus P55TP4N, the Triton-1 board just before Triton-2 came > out. I bought it originally with a Pentium 100MHz CPU. It ran NetBSD > just great for about a year. > > Later, I decided to put a Cyrix 6x86 P166+ in it. I plugged the chip > in, and it booted, but it would get sig 11's constantly, and > eventually panic. I wasn't sure if I had a bad chip, or a bad > motherboard, or what. But verified it worked correctly with the > Pentium. > > I was getting ready to send the Cyrix chip back when I checked the > Asus web site, and found that a BIOS upgrade was recommended. I > downloaded the BIOS, flashed it, and rebooted. The machine > consequently proceeded to give my over 90 days solid uptime, before I > accidently made my UPS shutdown while doing a reinstall of Win95 on my > NT/95/Decsent box. > > Mr VanLoon Don't you know that only Intel can make processors that work? No one can ever match their expertise EVER. Likewise why are you bothering with these obviously inferior operating systems such as NetBSD and FreeBSD? Only Microsoft has the resources necessary to make a true robust and reliable OS. I hear this argument with microprocessors all the time. I thought I would extend it to OS'es and see how it sounded. To everyone: Why are some people afraid of flash upgrading their BIOS? I know most people on this group would not even blink at upgrading their kernel but BIOS'es are another matter. If a motherboard is not identifying your CPU properly it seems an upgrade is more than justified. Has anyone actually had a flash upgrade fail? -- David W. Alderman dave@persprog.com From owner-freebsd-hardware Thu Aug 28 09:26:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA07751 for hardware-outgoing; Thu, 28 Aug 1997 09:26:15 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA07744 for ; Thu, 28 Aug 1997 09:26:09 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id SAA21539; Thu, 28 Aug 1997 18:22:44 +0200 (MEST) From: Søren Schmidt Message-Id: <199708281622.SAA21539@sos.freebsd.dk> Subject: Re: Q: K5 clock speeds (Was: Re: K6-200 Has anyone ...) In-Reply-To: <34059102.95F788BE@persprog.com> from Dave Alderman at "Aug 28, 97 10:53:54 am" To: dave@persprog.com Date: Thu, 28 Aug 1997 18:22:44 +0200 (MEST) Cc: michaelv@MindBender.serv.net, jdn@qiv.com, hlew@www2.shoppersnet.com, hardware@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 X-Loop: FreeBSD.org Precedence: bulk In reply to Dave Alderman who wrote: > > To everyone: > Why are some people afraid of flash upgrading their BIOS? I know most > people on this group would not even blink at upgrading their kernel but > BIOS'es are another matter. If a motherboard is not identifying your > CPU properly it seems an upgrade is more than justified. Has anyone > actually had a flash upgrade fail? Yep!, glad I had a EPROM burner so I could do a new one :) which btw cant be flashed.... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hardware Thu Aug 28 10:01:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA09525 for hardware-outgoing; Thu, 28 Aug 1997 10:01:07 -0700 (PDT) Received: from dragon.awen.com (dragon.awen.com [207.33.155.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA09520 for ; Thu, 28 Aug 1997 10:01:00 -0700 (PDT) Received: from cmnsens (cmnsens.awen.com [207.33.155.2]) by dragon.awen.com (8.8.7/8.8.6) with SMTP id KAA16401 for ; Thu, 28 Aug 1997 10:00:40 -0700 (PDT) Message-Id: <199708281700.KAA16401@dragon.awen.com> From: "Mike Burgett" To: "hardware@freebsd.org" Date: Thu, 28 Aug 97 10:00:39 -0700 Reply-To: "Mike Burgett" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Fwd: K6 Linux Re-Compile Issue Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk FWIW, I just got the following from AMD tech support, regarding the problems I had reported with my initial K6 and running 'make world' ==================BEGIN FORWARDED MESSAGE================== >Date: Thu, 28 Aug 1997 08:47:35 -0700 >From: AMD Tech Support >Organization: AMD Tech Hotline >Subject: K6 Linux Re-Compile Issue Hello, AMD recently received reports from a limited number of users having intermittent problems while running core re-compiles of the Linux shareware operating system. Our systems engineering group has duplicated the observation and determined that it is related to a previously know erratum. Full technical details of this erratum are documented in section 2.6.2 of the AMD-K6 MMX Enhanced Processor Revision Guide posted on our website, www.amd.com. Users that feel they are being affected by this problem, should contact AMD s support line at (408) 749-3060 and ask for Dan Hingle or Glen Garcia. Regards, Technical Support ===================END FORWARDED MESSAGE=================== Here's the section of the errata that they apparently didn't feel like appending: 2.6.2 Re-execution of Instructions Due to Self-Modifying Code Products Affected. B stepping Normal Specified Operation. If the processor detects a potential self-modifying code condition, the processor performs specific internal actions to ensure that instruction execution occurs in the correct manner. Non-conformance. If: - The target of a transfer control instruction is fetched and loaded into the processor s Branch Target Cache (BTC) - This transfer control instruction is speculatively executed and hits in the BTC - An instruction (Instruction A ) is executed that causes the processor to detect a potential self-modifying code condition relative to the transfer control target that resides in the BTC - Instruction A is followed by a register-modifying instruction(s) in the form of: A long-decoded instruction, or; One or two short-decoded instructions - The transfer control instruction that was speculatively executed follows the register-modifying instruction(s) within approximately 1-9 instructions - Certain other relative internal pipeline timing conditions must occur then: the long-decoded instruction, or the short-decoded instruction(s), is executed twice. Potential Effect on System. If software is not affected by the re-execution of the register-modifying instruction(s) for instance, loading immediate data into a general purpose register then this erratum has no effect on the system. However, if any of the instructions that are re-executed change the state of the system from the state that would be achieved by the normal specified operation for instance, incrementing a register by one then this erratum can lead to unpredictable system behavior. Suggested Workaround. None. Resolution Status. This erratum will be corrected in a future stepping of the AMD-K6 processor. --Mike From owner-freebsd-hardware Thu Aug 28 10:26:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA10988 for hardware-outgoing; Thu, 28 Aug 1997 10:26:54 -0700 (PDT) Received: from www2.shoppersnet.com (shoppersnet.com [204.156.152.112]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA10981 for ; Thu, 28 Aug 1997 10:26:51 -0700 (PDT) Received: (from hlew@localhost) by www2.shoppersnet.com (8.8.5/8.8.5) id KAA24506; Thu, 28 Aug 1997 10:33:43 -0700 (PDT) Date: Thu, 28 Aug 1997 10:33:43 -0700 (PDT) From: Howard Lew To: "Jay D. Nelson" cc: hardware@FreeBSD.ORG Subject: Re: Q: K5 clock speeds (Was: Re: K6-200 Has anyone ...) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 27 Aug 1997, Jay D. Nelson wrote: > Thanks for the info. What you are suggesting is that the clock is the > only thing that counts and moving the jumper to x2.5 is all that's > necessary -- regardless of the bios. Why would ASUS issue a bios > upgrade to support 150-166Mhz K5s? (Marketing?) > > -- Jay I haven't seen the ASUS Bios bootup screen, but the K5-PR150 and K5-PR166 were supposed to be 60x1.75 and 66x1.75 respectively on the K5. The K5 was supposed to be an exact Pentium clone (even down to the clock multiplier and bus frequency so you can set the speed equal to its PR #). For example, the K5-PR133 can be jumpered at 66x1.5 (actual clock) or 66x2.0 (PR-clock). Either way, it will run at 100MHz. You can verify this with FreeBSD -- It will say 100MHz clock even with 66x2. Newer Award BIOSes will show the PR # under what used to be the clock frequency for the AMD K5 and Cyrix 6x86. > > On Wed, 27 Aug 1997, Howard Lew wrote: > > >On Wed, 27 Aug 1997, Jay D. Nelson wrote: > > > >> Did you upgrade the bios to support the chip? I just installed this > >> board with a K5-166 -- clocked it at 66Mhz*2 because I wasn't sure. > >> Works fine at 133Mhz though the bios thinks it's 100Mhz. I'm about to > >> upgrade the bios but would rather not. Why wouldn't 66Mhz*2.5 work as > >> well? My bios right now is *-0109. Is there anything peculiar about > >> K5s above 133Mhz? > >> > > > >When you clock a K5-166 at 66x2 you are slowing it down to K5-133 speed > >because the K5-133 runs at 100MHz. The K5-166 should be jumpered for > >166MHz like a Pentium (66 x 2.5). The circuits inside the chip will > >modify it to 1.75. > > > >The only way to overclock a K5 is to use a higher bus clock (i.e. 75MHz) > >because of the way the clock multiplier on the K5 works. 75MHz will > >generally work, but 83MHz will not. At 75MHz bus clock, the K5-166 will > >be probed and run at or almost at Pentium 200 speeds. Stability is > >questionable though and depending on whether your MB supports async PCI, > >37.5MHz may be too high for some PCI SCSI cards. > > > > > >> -- Jay > >> > >> On Wed, 27 Aug 1997, Cameron Slye wrote: > >> > >> >> > >> >> I've only a 166 MHz but I've made several "make world" without problems. > >> > > >> >How much memory is in that box ? I have a asus p55t2p4 here, with a 166 in > >> >it. 25 make worlds finished with only 32mb in 2 slots, but with 64mb in 4 > >> >slots, it died in the first make world. (sig 11) > >> > > >> > > > From owner-freebsd-hardware Thu Aug 28 10:41:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA11699 for hardware-outgoing; Thu, 28 Aug 1997 10:41:16 -0700 (PDT) Received: from dragon.awen.com (dragon.awen.com [207.33.155.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA11693 for ; Thu, 28 Aug 1997 10:41:12 -0700 (PDT) Received: from cmnsens (cmnsens.awen.com [207.33.155.2]) by dragon.awen.com (8.8.7/8.8.6) with SMTP id KAA16591 for ; Thu, 28 Aug 1997 10:41:09 -0700 (PDT) Message-Id: <199708281741.KAA16591@dragon.awen.com> From: "Mike Burgett" To: "hardware@freebsd.org" Date: Thu, 28 Aug 97 10:41:09 -0700 Reply-To: "Mike Burgett" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: K6 Info, phone call with Dan Hingle Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just got off the phone with Dan Hingle, who appears to be heading up the tech support folks that are dealing with this problem. AMD doesn't appear to have all the details worked out yet, and they are having their engineering check to be sure the Linux problem is the same one being seen on FreeBSD. He also said the engineers are "working to make sure the problem is resolved", but wasn't clear whether that meant they had already fixed the problem in silicon, or were preparing to. He expects it to take about 3 weeks to get everything set up to start the program. Once that's done, they do appear to be willing to swap out the defective chips, but will deal with users on a case by case basis (i.e., you call, talk to someone, and get a number or something to ship the chip back under... conditions of cross-shipping, if it will be available, are unknown at this time.) One thing, it appears that they will be doing this, *if* the problem has manifested on a AMD tested and approved listed motherboard, and the question of what motherboard you are using will undoubtedly come up while talking with them. A list of "approved" motherboards is at: http://www.amd.com/K6/k6mbl/mblist.html In case you're not sure if your motherboard is on the list or not. Thanks, Mike From owner-freebsd-hardware Thu Aug 28 10:59:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA12362 for hardware-outgoing; Thu, 28 Aug 1997 10:59:03 -0700 (PDT) Received: from dragon.awen.com (dragon.awen.com [207.33.155.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA12353 for ; Thu, 28 Aug 1997 10:58:57 -0700 (PDT) Received: from cmnsens (cmnsens.awen.com [207.33.155.2]) by dragon.awen.com (8.8.7/8.8.6) with SMTP id KAA16671; Thu, 28 Aug 1997 10:58:49 -0700 (PDT) Message-Id: <199708281758.KAA16671@dragon.awen.com> From: "Mike Burgett" To: "Sean Eric Fagan" Cc: "hardware@freebsd.org" Date: Thu, 28 Aug 97 10:58:47 -0700 Reply-To: "Mike Burgett" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Fwd: K6 Linux Re-Compile Issue Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 28 Aug 1997 10:54:21 -0700 (PDT), Sean Eric Fagan wrote: >>Here's the section of the errata that they apparently didn't feel like >>appending: > >It would have been nice if you'd specified a URL :). I can't find the >errata sheet. (Well, I found osmething in PDF, which does me no good >whatsoever.) > >Sean. > The URL is http://www.amd.com/K6/k6docs/revgd.html and it only seems to be available in PDF... I can convert that to at least a PS file, if that would be any help... --Mike From owner-freebsd-hardware Thu Aug 28 11:01:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA12557 for hardware-outgoing; Thu, 28 Aug 1997 11:01:04 -0700 (PDT) Received: from www2.shoppersnet.com (shoppersnet.com [204.156.152.112]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA12552 for ; Thu, 28 Aug 1997 11:01:01 -0700 (PDT) Received: (from hlew@localhost) by www2.shoppersnet.com (8.8.5/8.8.5) id KAA24639; Thu, 28 Aug 1997 10:37:15 -0700 (PDT) Date: Thu, 28 Aug 1997 10:37:15 -0700 (PDT) From: Howard Lew To: Dave Alderman cc: "Michael L. VanLoon -- HeadCandy.com" , "Jay D. Nelson" , hardware@FreeBSD.ORG Subject: Re: Q: K5 clock speeds (Was: Re: K6-200 Has anyone ...) In-Reply-To: <34059102.95F788BE@persprog.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 28 Aug 1997, Dave Alderman wrote: > Michael L. VanLoon -- HeadCandy.com wrote: > > > > I have an Asus P55TP4N, the Triton-1 board just before Triton-2 came > > out. I bought it originally with a Pentium 100MHz CPU. It ran NetBSD > > just great for about a year. > > > > Later, I decided to put a Cyrix 6x86 P166+ in it. I plugged the chip > > in, and it booted, but it would get sig 11's constantly, and > > eventually panic. I wasn't sure if I had a bad chip, or a bad > > motherboard, or what. But verified it worked correctly with the > > Pentium. > > > > I was getting ready to send the Cyrix chip back when I checked the > > Asus web site, and found that a BIOS upgrade was recommended. I > > downloaded the BIOS, flashed it, and rebooted. The machine > > consequently proceeded to give my over 90 days solid uptime, before I > > accidently made my UPS shutdown while doing a reinstall of Win95 on my > > NT/95/Decsent box. > > > > > Mr VanLoon > > Don't you know that only Intel can make processors that work? No one > can ever match their expertise EVER. Likewise why are you bothering > with these obviously inferior operating systems such as NetBSD and > FreeBSD? Only Microsoft has the resources necessary to make a true > robust and reliable OS. > > > > I hear this argument with microprocessors all the time. I thought I > would extend it to OS'es and see how it sounded. > > To everyone: > Why are some people afraid of flash upgrading their BIOS? I know most > people on this group would not even blink at upgrading their kernel but > BIOS'es are another matter. If a motherboard is not identifying your > CPU properly it seems an upgrade is more than justified. Has anyone > actually had a flash upgrade fail? Flash upgrades usually don't fail unless people flash it with the wrong version. Then the motherboard is hosed and they need a replacement chip. Even though Award BIOS supposedly still let's use reflash it with their flash bios boot block and an ISA video card, I have never seen that work before. > > -- > David W. Alderman dave@persprog.com > From owner-freebsd-hardware Thu Aug 28 11:21:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA13427 for hardware-outgoing; Thu, 28 Aug 1997 11:21:40 -0700 (PDT) Received: from dragon.awen.com (dragon.awen.com [207.33.155.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA13422 for ; Thu, 28 Aug 1997 11:21:37 -0700 (PDT) Received: from cmnsens (cmnsens.awen.com [207.33.155.2]) by dragon.awen.com (8.8.7/8.8.6) with SMTP id LAA16804; Thu, 28 Aug 1997 11:21:33 -0700 (PDT) Message-Id: <199708281821.LAA16804@dragon.awen.com> From: "Mike Burgett" To: "Sean Eric Fagan" Cc: "hardware@freebsd.org" Date: Thu, 28 Aug 97 11:21:32 -0700 Reply-To: "Mike Burgett" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Fwd: K6 Linux Re-Compile Issue Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 28 Aug 1997 11:00:50 -0700 (PDT), Sean Eric Fagan wrote: >>I can convert that to at least a PS file, if that would be any help... > >Yes, actually, that would, assuming it's not too large :). (If you >could mail it to me by gzip'ping and uuencoding it, that'd help. >Or put it up for ftp/http somewhere...) Ok. ftp://ftp.awen.com/pub/misc/k6errata.ps.gz -rw-r--r-- 1 nobody nobody 429959 Aug 28 11:10 k6errata.ps.gz Expands to ~3M when uncompressed. --Mike From owner-freebsd-hardware Thu Aug 28 12:27:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA16348 for hardware-outgoing; Thu, 28 Aug 1997 12:27:19 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA16338 for ; Thu, 28 Aug 1997 12:27:16 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id MAA08792; Thu, 28 Aug 1997 12:29:40 -0700 (PDT) Message-Id: <199708281929.MAA08792@implode.root.com> To: "Mike Burgett" cc: "hardware@freebsd.org" Subject: Re: Fwd: K6 Linux Re-Compile Issue In-reply-to: Your message of "Thu, 28 Aug 1997 10:00:39 PDT." <199708281700.KAA16401@dragon.awen.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 28 Aug 1997 12:29:40 -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >FWIW, I just got the following from AMD tech support, regarding the problems I >had reported with my initial K6 and running 'make world' If this was the problem then the failures would be deterministic and not random. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hardware Thu Aug 28 13:02:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA17919 for hardware-outgoing; Thu, 28 Aug 1997 13:02:30 -0700 (PDT) Received: from tok.qiv.com ([204.214.141.211]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA17914 for ; Thu, 28 Aug 1997 13:02:22 -0700 (PDT) Received: (from uucp@localhost) by tok.qiv.com (8.8.6/8.8.5) with UUCP id PAA01328; Thu, 28 Aug 1997 15:00:26 -0500 (CDT) Received: from localhost (jdn@localhost) by acp.qiv.com (8.8.6/8.8.5) with SMTP id OAA00841; Thu, 28 Aug 1997 14:42:55 -0500 (CDT) X-Authentication-Warning: acp.qiv.com: jdn owned process doing -bs Date: Thu, 28 Aug 1997 14:42:55 -0500 (CDT) From: "Jay D. Nelson" To: Dave Alderman cc: "Michael L. VanLoon -- HeadCandy.com" , Howard Lew , hardware@FreeBSD.ORG Subject: Re: Q: K5 clock speeds (Was: Re: K6-200 Has anyone ...) In-Reply-To: <34059102.95F788BE@persprog.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Well -- the upshot of all this is: I flashed the bios simply because ASUS said it was necessary. It did not fail. BTW -- it wasn't fear of flashing the bios -- it was a reluctance to disassemble the machine. At any rate - this T2P4 is jumpered at 66Mhz/2.5x and the chip is correctly recognized as a PR166. Kernel compile took about 4 minutes. -- Jay On Thu, 28 Aug 1997, Dave Alderman wrote: >Michael L. VanLoon -- HeadCandy.com wrote: >> >> I have an Asus P55TP4N, the Triton-1 board just before Triton-2 came >> out. I bought it originally with a Pentium 100MHz CPU. It ran NetBSD >> just great for about a year. >> >> Later, I decided to put a Cyrix 6x86 P166+ in it. I plugged the chip >> in, and it booted, but it would get sig 11's constantly, and >> eventually panic. I wasn't sure if I had a bad chip, or a bad >> motherboard, or what. But verified it worked correctly with the >> Pentium. >> >> I was getting ready to send the Cyrix chip back when I checked the >> Asus web site, and found that a BIOS upgrade was recommended. I >> downloaded the BIOS, flashed it, and rebooted. The machine >> consequently proceeded to give my over 90 days solid uptime, before I >> accidently made my UPS shutdown while doing a reinstall of Win95 on my >> NT/95/Decsent box. >> >> >Mr VanLoon > >Don't you know that only Intel can make processors that work? No one >can ever match their expertise EVER. Likewise why are you bothering >with these obviously inferior operating systems such as NetBSD and >FreeBSD? Only Microsoft has the resources necessary to make a true >robust and reliable OS. > > > >I hear this argument with microprocessors all the time. I thought I >would extend it to OS'es and see how it sounded. > >To everyone: >Why are some people afraid of flash upgrading their BIOS? I know most >people on this group would not even blink at upgrading their kernel but >BIOS'es are another matter. If a motherboard is not identifying your >CPU properly it seems an upgrade is more than justified. Has anyone >actually had a flash upgrade fail? > >-- >David W. Alderman dave@persprog.com > From owner-freebsd-hardware Thu Aug 28 13:06:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA18174 for hardware-outgoing; Thu, 28 Aug 1997 13:06:12 -0700 (PDT) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA18168 for ; Thu, 28 Aug 1997 13:06:10 -0700 (PDT) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id NAA26529; Thu, 28 Aug 1997 13:02:47 -0700 (PDT) Date: Thu, 28 Aug 1997 13:02:47 -0700 (PDT) From: Jim Shankland Message-Id: <199708282002.NAA26529@biggusdiskus.flyingfox.com> To: dg@root.com Subject: Re: Fwd: K6 Linux Re-Compile Issue Cc: freebsd-hardware@freebsd.org Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk (Re: K6 chip bug, I mean non-conformance) > If this was the problem then the failures would be deterministic and not > random. Note that AMD says that "Certain other relative internal pipeline timing conditions must occur"; that sure sounds as though it could be non-deterministic to me. Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-hardware Thu Aug 28 17:36:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA00140 for hardware-outgoing; Thu, 28 Aug 1997 17:36:31 -0700 (PDT) Received: from mail.san.rr.com (san.rr.com [204.210.0.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA00135 for ; Thu, 28 Aug 1997 17:36:29 -0700 (PDT) Received: (from uucp@localhost) by mail.san.rr.com (8.8.7/8.8.7) id RAA20625; Thu, 28 Aug 1997 17:35:57 -0700 (PDT) Message-Id: <199708290035.RAA20625@mail.san.rr.com> Received: from dt5h1n61.san.rr.com(204.210.31.97) by mail via smap (V2.0) id xma020540; Thu, 28 Aug 97 17:35:41 -0700 From: "Studded" To: "Howard Lew" Cc: "hardware@FreeBSD.ORG" Date: Thu, 28 Aug 97 17:35:39 -0700 Reply-To: "Studded" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Flashing BIOS (Was Q: K5 clock speeds) Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 28 Aug 1997 10:37:15 -0700 (PDT), Howard Lew wrote: >Flash upgrades usually don't fail unless people flash it with the wrong >version. Then the motherboard is hosed and they need a replacement chip. >Even though Award BIOS supposedly still let's use reflash it with their >flash bios boot block and an ISA video card, I have never seen that work >before. Even the wrong version is usually not fatal. I had this exact scenario happen (clueless techie on the phone told me to d/l the wrong thing, "Oh, I'm so glad you called back!" *grumble*) and there is a jumper on my mb (dell-tweaked intel of long ago) that clears everything out and gets you back to the factory defaults. I just built a new box for a good friend and the basically generic socket 7 mb had the same kind of jumper, so I can't help thinking this is a pretty standard feature? Doug Do thou amend they face, and I'll amend my life. -Shakespeare, "Henry V" From owner-freebsd-hardware Thu Aug 28 20:31:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA08010 for hardware-outgoing; Thu, 28 Aug 1997 20:31:36 -0700 (PDT) Received: from www2.shoppersnet.com (shoppersnet.com [204.156.152.112]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA08005 for ; Thu, 28 Aug 1997 20:31:31 -0700 (PDT) Received: (from hlew@localhost) by www2.shoppersnet.com (8.8.5/8.8.5) id UAA16602; Thu, 28 Aug 1997 20:38:48 -0700 (PDT) Date: Thu, 28 Aug 1997 20:38:48 -0700 (PDT) From: Howard Lew To: Studded cc: "hardware@FreeBSD.ORG" Subject: Re: Flashing BIOS (Was Q: K5 clock speeds) In-Reply-To: <199708290035.RAA20625@mail.san.rr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 28 Aug 1997, Studded wrote: > On Thu, 28 Aug 1997 10:37:15 -0700 (PDT), Howard Lew wrote: > > >Flash upgrades usually don't fail unless people flash it with the wrong > >version. Then the motherboard is hosed and they need a replacement chip. > >Even though Award BIOS supposedly still let's use reflash it with their > >flash bios boot block and an ISA video card, I have never seen that work > >before. > > Even the wrong version is usually not fatal. I had this exact > scenario happen (clueless techie on the phone told me to d/l the wrong > thing, "Oh, I'm so glad you called back!" *grumble*) and there is a > jumper on my mb (dell-tweaked intel of long ago) that clears everything > out and gets you back to the factory defaults. I just built a new box for > a good friend and the basically generic socket 7 mb had the same kind of > jumper, so I can't help thinking this is a pretty standard feature? > I maybe wrong, but I think you are referring to the CMOS settings right? Most motherboards have a jumper that you can short for a few seconds and it will get you back to factory defaults. However, when you flash a bios and it is wiped, it is gone for good unless you have some kind of motherboard with a backup bios eprom. Why they would go to the expense of having 2 flash eproms is beyond me because that kind of error rarely happens. Replacing a bios chip is very cheap unless you are getting it from Unicore, but I think putting a duplicate on each board is too costly. From owner-freebsd-hardware Thu Aug 28 20:45:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA08520 for hardware-outgoing; Thu, 28 Aug 1997 20:45:31 -0700 (PDT) Received: from mail.san.rr.com (san.rr.com [204.210.0.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA08515 for ; Thu, 28 Aug 1997 20:45:27 -0700 (PDT) Received: (from uucp@localhost) by mail.san.rr.com (8.8.7/8.8.7) id UAA29964; Thu, 28 Aug 1997 20:44:56 -0700 (PDT) Message-Id: <199708290344.UAA29964@mail.san.rr.com> Received: from dt5h1n61.san.rr.com(204.210.31.97) by mail via smap (V2.0) id xma029857; Thu, 28 Aug 97 20:44:41 -0700 From: "Studded" To: "Howard Lew" Cc: "hardware@FreeBSD.ORG" Date: Thu, 28 Aug 97 20:44:38 -0700 Reply-To: "Studded" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Flashing BIOS (Was Q: K5 clock speeds) Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 28 Aug 1997 20:38:48 -0700 (PDT), Howard Lew wrote: >I maybe wrong, but I think you are referring to the CMOS settings right? > >Most motherboards have a jumper that you can short for a few seconds and >it will get you back to factory defaults. However, when you flash a >bios and it is wiped, it is gone for good unless you have some kind of >motherboard with a backup bios eprom. Yeah, that's possible. I do know that I was flashing the bios when it died, and shorting that jumper fixed it. :) Maybe there is a safety feature built in so that it can't get any more screwed up than that jumper can fix. Sorry if I spoke out of turn. :) Doug Do thou amend they face, and I'll amend my life. -Shakespeare, "Henry V" From owner-freebsd-hardware Fri Aug 29 04:14:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA27384 for hardware-outgoing; Fri, 29 Aug 1997 04:14:51 -0700 (PDT) Received: from persprog.com (root@persprog.com [204.215.255.203]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA27375 for ; Fri, 29 Aug 1997 04:14:44 -0700 (PDT) Received: by persprog.com (8.7.5/4.10) id TAA22968; Thu, 28 Aug 1997 19:56:37 -0500 Received: from dave.ppi.com(192.2.2.6) by cerberus.ppi.com via smap (V1.3) id sma022966; Thu Aug 28 20:56:35 1997 Message-ID: <34061E45.3A5D3C0B@persprog.com> Date: Thu, 28 Aug 1997 20:56:37 -0400 From: Dave Alderman Reply-To: dave@persprog.com Organization: Personalized Programming, Inc X-Mailer: Mozilla 4.0 [en] (Win95; U) MIME-Version: 1.0 To: "Jay D. Nelson" CC: "Michael L. VanLoon -- HeadCandy.com" , Howard Lew , hardware@FreeBSD.ORG Subject: Re: Q: K5 clock speeds (Was: Re: K6-200 Has anyone ...) X-Priority: 3 (Normal) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jay D. Nelson wrote: > > Well -- the upshot of all this is: > > I flashed the bios simply because ASUS said it was necessary. It did > not fail. BTW -- it wasn't fear of flashing the bios -- it was a > reluctance to disassemble the machine. I realized after I wrote my original message that there was some implication that people "afraid" to flash their BIOS'es were timid. Actually, I was wondering if there was a good reason to be concerned that the procedure would fail. As long as you have the right BIOS and it is flashable then it is relatively safe. Of course if the vendor did not make clear which BIOS file to use then you could be in trouble. Actually I have toasted a BIOS once. This was a Micronics Neptune board in an old Micron box. I successfully flash-upgraded the board to support plug-n-play (yes, it was an old board) but the BusLogic controller that came with the machine stopped working. When I tried to restore the original BIOS it blew up supposedly because the original BIOS was smaller. To add insult to injury, this board had an emergency recovery procedure involving a pre-built floppy and a protected region of the BIOS that allowed you to restore the original BIOS after an unsuccessful flashing. Unfortunately, the BIOS upgrade needed so much space they overwrote the "protected" region. It was a good thing I had a friend who could blow me a new Intel Flash EEPROM. -- It's not my fault! It's some guy named "General Protection"! --Ratbert David W. Alderman dave@persprog.com From owner-freebsd-hardware Fri Aug 29 10:31:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA16467 for hardware-outgoing; Fri, 29 Aug 1997 10:31:57 -0700 (PDT) Received: from sparkie.gnofn.org (sparkie.gnofn.org [206.27.168.35]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA16459 for ; Fri, 29 Aug 1997 10:31:54 -0700 (PDT) Received: from sparkie.gnofn.org (sparkie.gnofn.org [206.27.168.35]) by sparkie.gnofn.org (8.7.Beta.10/8.7.Beta.10) with SMTP id MAA23129; Fri, 29 Aug 1997 12:00:04 -0500 (CDT) Date: Fri, 29 Aug 1997 12:00:04 -0500 (CDT) From: Craig Johnston To: Howard Lew cc: "Jay D. Nelson" , Cameron Slye , hardware@FreeBSD.ORG Subject: Re: K6-200 Has anyone successfully done a 'make world' ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 27 Aug 1997, Howard Lew wrote: > On Wed, 27 Aug 1997, Jay D. Nelson wrote: > > The only way to overclock a K5 is to use a higher bus clock (i.e. 75MHz) > because of the way the clock multiplier on the K5 works. 75MHz will > generally work, but 83MHz will not. At 75MHz bus clock, the K5-166 will 83 works great with my hardware. I do 83 * 1.5 and it beats out 75 * 1.75 for most of the stuff I do. (125 Mhz vs 132 Mhz, the win being on bus speed.) K5-166, ABIT IT5H, 50ns EDO, symbios 53c810 SCSI, ati mach32 pci. > be probed and run at or almost at Pentium 200 speeds. Stability is > questionable though and depending on whether your MB supports async PCI, > 37.5MHz may be too high for some PCI SCSI cards. I had stability probs at 1.75 * 75 until I upped the CPUs voltage a little bit, to 3.6 from 3.52. At 3.52 make world dies, 3.6 works fine. ta, Craig From owner-freebsd-hardware Fri Aug 29 13:28:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA26454 for hardware-outgoing; Fri, 29 Aug 1997 13:28:52 -0700 (PDT) Received: from DonaldBurr.dyn.ml.org (pm0-20.sba1.avtel.net [207.71.218.20]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA26435; Fri, 29 Aug 1997 13:28:47 -0700 (PDT) Received: from localhost (dburr@localhost) by DonaldBurr.dyn.ml.org (8.8.5/8.8.5) with SMTP id NAA21097; Fri, 29 Aug 1997 13:29:43 -0700 (PDT) X-Authentication-Warning: DonaldBurr.DonaldBurr.dyn.ml.org: dburr owned process doing -bs Date: Fri, 29 Aug 1997 13:29:42 -0700 (PDT) From: Donald Burr X-Sender: dburr@DonaldBurr.DonaldBurr.dyn.ml.org To: FreeBSD Hardware , FreeBSD SCSI Subject: Is this (SCSI) tape drive compatible with FreeBSD? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm about to acquire an Archive Viper 2150S, (a SCSI-1 tapedrive). Is this device compatible with FreeBSD's scsitape driver? (i.e. will I be able to use dump, tar, cpio, etc. to do backup/restores with it, or archive files, whatnot?) If it isn't compatible please let me know ASAP so that I can abort the forsale transaction. 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. From owner-freebsd-hardware Fri Aug 29 14:24:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA29167 for hardware-outgoing; Fri, 29 Aug 1997 14:24:15 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA29159 for ; Fri, 29 Aug 1997 14:24:06 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id XAA15965; Fri, 29 Aug 1997 23:23:53 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id XAA23604; Fri, 29 Aug 1997 23:23:38 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-uucp-2.9) id XAA01302; Fri, 29 Aug 1997 23:23:19 +0200 (CEST) Message-ID: <19970829232319.33757@keltia.freenix.fr> Date: Fri, 29 Aug 1997 23:23:19 +0200 From: Ollivier Robert To: Donald Burr Cc: FreeBSD Hardware Subject: Re: Is this (SCSI) tape drive compatible with FreeBSD? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: ; from Donald Burr on Fri, Aug 29, 1997 at 01:29:42PM -0700 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3592 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Donald Burr: > I'm about to acquire an Archive Viper 2150S, (a SCSI-1 tapedrive). Is > this device compatible with FreeBSD's scsitape driver? (i.e. will I be > able to use dump, tar, cpio, etc. to do backup/restores with it, or > archive files, whatnot?) You should have no problem at all with it. This is your average QIC-150 SCSI streamer; should work with 150 & 250 MB tapes. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #29: Tue Aug 26 21:05:09 CEST 1997 From owner-freebsd-hardware Fri Aug 29 19:38:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA13567 for hardware-outgoing; Fri, 29 Aug 1997 19:38:51 -0700 (PDT) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA13549; Fri, 29 Aug 1997 19:38:47 -0700 (PDT) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.5/8.8.5) with SMTP id VAA15336; Fri, 29 Aug 1997 21:38:34 -0500 (EST) Date: Fri, 29 Aug 1997 21:38:34 -0500 (EST) From: John Fieber To: Donald Burr cc: FreeBSD Hardware , FreeBSD SCSI Subject: Re: Is this (SCSI) tape drive compatible with FreeBSD? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 29 Aug 1997, Donald Burr wrote: > I'm about to acquire an Archive Viper 2150S, (a SCSI-1 tapedrive). Is > this device compatible with FreeBSD's scsitape driver? (i.e. will I be > able to use dump, tar, cpio, etc. to do backup/restores with it, or > archive files, whatnot?) Yes. No speed demon by today's standards (about 5MB/minute) but it works fine. -john From owner-freebsd-hardware Fri Aug 29 19:53:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA14085 for hardware-outgoing; Fri, 29 Aug 1997 19:53:58 -0700 (PDT) Received: from roguetrader.com (brandon@cold.org [206.81.134.103]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA14080 for ; Fri, 29 Aug 1997 19:53:55 -0700 (PDT) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id UAA01261 for ; Fri, 29 Aug 1997 20:57:19 -0600 (MDT) Date: Fri, 29 Aug 1997 20:57:19 -0600 (MDT) From: Brandon Gillespie To: freebsd-hardware@freebsd.org Subject: Odd problems with a Conner SCSI drive.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm trying to add a new drive to my system. The drive is a little unusual (its from a SUN workstation with a single integrated interface that has an adapter for the 50pin cables), but I seem to recall having one of the same drives on another FreeBSD system... The drive probes as: (ahc0:3:0): "CONNER CFP1060E SUN1.05 245C" type 0 fixed SCSI 2 sd1(ahc0:3:0): Direct-Access 1010MB (2070400 512 byte sectors) I've tried adding it with /stand/sysinstall, but all that does is when I try to 'W'rite the label it gives me a 'newfs: /usr3 Invalid Argument' or some such (going from memory). So, I go one step lower, I ran dd from /dev/zero to the drive with a 100 count (and later I did the whole drive, for the hell of it). Following this I did 'disklabel -Brw sd1 auto' and then simply 'disklabel -Brw sd1 auto'--per the Handbook Suggestions. ALL I change in the disklabel is I add a partition for the filesystem, using the label 'e'. However, when I try to save and quit it gives me the error: line 23: bad partition name (???) Following the man pages, 'e' is a perfectly valid partition name. I'm wondering if this has anything to do with the other disklabel information which say it only has 3 partitions--so I use 'd' instead, and it seems to work... Saving in disklabel gives the warning: Warning, unused partition d: size 2070400 offset 0 I'm also not sure if I'm supposed to change the 'type' to SCSI in disklabel, nor what should go in the 'disk', label and flags fields... -Brandon Gillespie --------------------------------------------- # /dev/rsd1c: type: unknown disk: label: flags: bytes/sector: 512 sectors/track: 93 tracks/cylinder: 8 sectors/cylinder: 744 cylinders: 2782 sectors/unit: 2070400 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 3 partitions: # size offset fstype [fsize bsize bps/cpg] c: 2070400 0 unused 0 0 # (Cyl. 0 -2782*) d: 2070400 0 4.4BSD 1024 8192 --------------------------------------------- From owner-freebsd-hardware Fri Aug 29 21:46:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA18357 for hardware-outgoing; Fri, 29 Aug 1997 21:46:39 -0700 (PDT) Received: from rfd1.oit.umass.edu (mailhub.oit.umass.edu [128.119.175.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA18352 for ; Fri, 29 Aug 1997 21:46:36 -0700 (PDT) Received: from emily.oit.umass.edu by rfd1.oit.umass.edu (PMDF V5.1-8 #20973) with ESMTP id <0EFPML7DR00EGQ@rfd1.oit.umass.edu> for freebsd-hardware@FreeBSD.ORG; Sat, 30 Aug 1997 00:46:19 -0400 (EDT) Received: from localhost (gp@localhost) by emily.oit.umass.edu (8.8.3/8.8.6) with SMTP id AAA09377 for ; Sat, 30 Aug 1997 00:46:14 -0400 (EDT) Date: Sat, 30 Aug 1997 00:46:14 -0400 (EDT) From: Greg Pavelcak Subject: Mixing DIMMS and SIMMS To: freebsd-hardware@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'm about to get a new motherboard, and I'd like to survey people about the possibility of mixing DIMMS and SIMMS. I know the Asus web-site advises against it, but the specs for the Gigabyte TX motherboard say it can be done. Although it says to be sure to follow the manual's instructions for the proper combinations. Opinions? Thanks. Greg From owner-freebsd-hardware Sat Aug 30 04:06:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA12061 for hardware-outgoing; Sat, 30 Aug 1997 04:06:33 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA12056 for ; Sat, 30 Aug 1997 04:06:26 -0700 (PDT) Received: from elwing.folklore.ee (elwing.folklore.ee [172.17.2.2]) by haldjas.folklore.ee (8.8.6/8.8.4) with SMTP id OAA16580; Sat, 30 Aug 1997 14:04:56 +0300 (EEST) Date: Sat, 30 Aug 1997 14:04:55 +0300 (EEST) From: Narvi X-Sender: narvi@elwing.folklore.ee To: Greg Pavelcak cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Mixing DIMMS and SIMMS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 30 Aug 1997, Greg Pavelcak wrote: > I'm about to get a new motherboard, and I'd like to survey people > about the possibility of mixing DIMMS and SIMMS. I know the Asus > web-site advises against it, but the specs for the Gigabyte TX Well, I have seen manuals say don't do it, you will burn your MB. > motherboard say it can be done. Although it says to be sure to follow > the manual's instructions for the proper combinations. > > Opinions? > I would say follow what the manual says. :-) > Thanks. > > Greg > > Sander There is no love, no good, no happiness and no future - all these are just illusions. From owner-freebsd-hardware Sat Aug 30 07:11:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA19040 for hardware-outgoing; Sat, 30 Aug 1997 07:11:04 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA19030 for ; Sat, 30 Aug 1997 07:11:00 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id QAA17325 for ; Sat, 30 Aug 1997 16:11:05 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id QAA19688 for freebsd-hardware@FreeBSD.ORG; Sat, 30 Aug 1997 16:10:47 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-uucp-2.9) id LAA02811; Sat, 30 Aug 1997 11:31:06 +0200 (CEST) Message-ID: <19970830113106.52616@keltia.freenix.fr> Date: Sat, 30 Aug 1997 11:31:06 +0200 From: Ollivier Robert To: freebsd-hardware@FreeBSD.ORG Subject: Re: Odd problems with a Conner SCSI drive.. References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: ; from Brandon Gillespie on Fri, Aug 29, 1997 at 08:57:19PM -0600 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3592 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Brandon Gillespie: > line 23: bad partition name Change the line that says "N partitions" to say at least "5 partitions". > which say it only has 3 partitions--so I use 'd' instead, and it seems to > work... Saving in disklabel gives the warning: You use 'd' so you should put at least "4 partitions" in the same line. > 3 partitions: > # size offset fstype [fsize bsize bps/cpg] > c: 2070400 0 unused 0 0 # (Cyl. 0 -2782*) > d: 2070400 0 4.4BSD 1024 8192 Change it to 4 partitions: ... -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #29: Tue Aug 26 21:05:09 CEST 1997 From owner-freebsd-hardware Sat Aug 30 07:41:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA20105 for hardware-outgoing; Sat, 30 Aug 1997 07:41:03 -0700 (PDT) Received: from roguetrader.com (brandon@cold.org [206.81.134.103]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA20098 for ; Sat, 30 Aug 1997 07:41:00 -0700 (PDT) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id IAA04539; Sat, 30 Aug 1997 08:44:13 -0600 (MDT) Date: Sat, 30 Aug 1997 08:44:12 -0600 (MDT) From: Brandon Gillespie To: Ollivier Robert cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Odd problems with a Conner SCSI drive.. In-Reply-To: <19970830113106.52616@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 30 Aug 1997, Ollivier Robert wrote: > > 3 partitions: > > # size offset fstype [fsize bsize bps/cpg] > > c: 2070400 0 unused 0 0 # (Cyl. 0 -2782*) > > d: 2070400 0 4.4BSD 1024 8192 > > Change it to > > 4 partitions: Ok, did that, now its being very weird... I changed the whole disklabel to be: ----------------------------------- # /dev/rsd1c: type: SCSI disk: sd1s1 label: flags: bytes/sector: 512 sectors/track: 93 tracks/cylinder: 8 sectors/cylinder: 744 cylinders: 2782 sectors/unit: 2070400 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 5 partitions: # size offset fstype [fsize bsize bps/cpg] c: 2070400 0 unused 0 0 # (Cyl. 0 -2782*) e: 2070400 0 4.4BSD 1024 8192 ----------------------------------- And then saved, it worked without warnings or errors this time, but when I fire disklabel back up, its changed the fstype on 'e' ?! It now looks like: e: 2070400 0 System V # (Cyl. 0 -2782*) Why on earth did it do this? -Brandon From owner-freebsd-hardware Sat Aug 30 11:42:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA27792 for hardware-outgoing; Sat, 30 Aug 1997 11:42:32 -0700 (PDT) Received: from iafnl.es.iaf.nl (root@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA27775; Sat, 30 Aug 1997 11:42:27 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA02548 (5.67b/IDA-1.5); Sat, 30 Aug 1997 20:18:54 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id XAA02721; Fri, 29 Aug 1997 23:52:30 +0200 (MET DST) From: Wilko Bulte Message-Id: <199708292152.XAA02721@yedi.iaf.nl> Subject: Re: Is this (SCSI) tape drive compatible with FreeBSD? To: dburr@POBoxes.com (Donald Burr) Date: Fri, 29 Aug 1997 23:52:30 +0200 (MET DST) Cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG In-Reply-To: from "Donald Burr" at Aug 29, 97 01:29:42 pm X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Donald Burr wrote... > I'm about to acquire an Archive Viper 2150S, (a SCSI-1 tapedrive). Is > this device compatible with FreeBSD's scsitape driver? (i.e. will I be > able to use dump, tar, cpio, etc. to do backup/restores with it, or > archive files, whatnot?) I use one with FreeBSD2.2.1R without problems. Has been working since 386BSD 0.1 or so ;-) _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' ----------------------------------------------------------------------Yoda From owner-freebsd-hardware Sat Aug 30 16:00:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA06675 for hardware-outgoing; Sat, 30 Aug 1997 16:00:23 -0700 (PDT) Received: from pegasus.com (pegasus.com [206.127.225.31]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id QAA06657; Sat, 30 Aug 1997 16:00:11 -0700 (PDT) Received: by pegasus.com (8.6.8/PEGASUS-2.2) id MAA11212; Sat, 30 Aug 1997 12:59:41 -1001 Date: Sat, 30 Aug 1997 12:59:41 -1001 From: richard@pegasus.com (Richard Foulk) Message-Id: <199708302300.MAA11212@pegasus.com> In-Reply-To: Wilko Bulte "Re: Is this (SCSI) tape drive compatible with FreeBSD?" (Aug 29, 11:52pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Is this (SCSI) tape drive compatible with FreeBSD? Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk } > I'm about to acquire an Archive Viper 2150S, (a SCSI-1 tapedrive). Is } > this device compatible with FreeBSD's scsitape driver? (i.e. will I be } > able to use dump, tar, cpio, etc. to do backup/restores with it, or } > archive files, whatnot?) } } I use one with FreeBSD2.2.1R without problems. Has been working since } 386BSD 0.1 or so ;-) Compatible perhaps, but not a very good deal -- even if it's free. A 250meg capacity is awfully small today, and the tapes are too expensive. They're also excruciatingly slow. Figure out how many tapes you might reasonably buy over the life of the drive and then see what the real cost is. DATs and Exabytes are usually a much better deal. I prefer Exabytes. Richard From owner-freebsd-hardware Sat Aug 30 17:20:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA09179 for hardware-outgoing; Sat, 30 Aug 1997 17:20:29 -0700 (PDT) Received: from ns.feral.com (root@feral.mauswerks.net [204.152.96.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA09162; Sat, 30 Aug 1997 17:20:23 -0700 (PDT) Received: from feral.feral.com.feral.COM (feral [192.67.166.5]) by ns.feral.com (8.8.6/8.8.6) with SMTP id RAA00360; Sat, 30 Aug 1997 17:15:39 -0700 Date: Sat, 30 Aug 1997 17:15:39 -0700 From: Matthew Jacob Message-Id: <199708310015.RAA00360@ns.feral.com> To: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, richard@pegasus.com Subject: Re: Is this (SCSI) tape drive compatible with FreeBSD? reply-to: mjacob@feral.com Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >A 250meg capacity is awfully small today, and the tapes are too expensive. >They're also excruciatingly slow. This isn't even 250Meg. It's QIC-120 (120Meg) or QIC-150. From owner-freebsd-hardware Sat Aug 30 18:21:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA11131 for hardware-outgoing; Sat, 30 Aug 1997 18:21:37 -0700 (PDT) Received: from shell.monmouth.com (root@shell.monmouth.com [205.164.220.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA11124 for ; Sat, 30 Aug 1997 18:21:31 -0700 (PDT) Received: from i4got.lakewood.com (fh-ppp9.monmouth.com [205.164.221.41]) by shell.monmouth.com (8.8.5/8.7.3) with ESMTP id VAA18151; Sat, 30 Aug 1997 21:18:26 -0400 (EDT) Received: (from pechter@localhost) by i4got.lakewood.com id VAA13486 (8.8.5/IDA-1.6); Sat, 30 Aug 1997 21:21:14 -0400 (EDT) From: Bill Pechter Message-ID: <199708310121.VAA13486@i4got.lakewood.com> Subject: Re: Is this (SCSI) tape drive compatible with FreeBSD? In-Reply-To: <199708310015.RAA00360@ns.feral.com> from Matthew Jacob at "Aug 30, 97 05:15:39 pm" To: mjacob@feral.com Date: Sat, 30 Aug 1997 21:21:14 -0400 (EDT) Cc: freebsd-hardware@freebsd.org Reply-to: pechter@lakewood.com X-Phone-Number: 908-389-3592 X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >A 250meg capacity is awfully small today, and the tapes are too expensive. > >They're also excruciatingly slow. Expensive... I've been buying new ones for $.25 per tape... They're NCR in the shrink wrap from a surplus house. Slow -- yes. Expensive -- not if you know where to look. I just picked up a 4 dat changer for $250 refurb... so the 150 is just going to be used for compatibility with boxes at work. Bill ------------------------------------------------------------------------------ Bill Pechter | 17 Meredith Drive Tinton Falls, NJ 07724 | 908-389-3592 pechter@lakewood.com | Save computing history, give an old geek old hardware. This msg brought to you by the letters PDP and the number 11. From owner-freebsd-hardware Sat Aug 30 19:14:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA12951 for hardware-outgoing; Sat, 30 Aug 1997 19:14:49 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA12934; Sat, 30 Aug 1997 19:14:41 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id LAA00788; Sun, 31 Aug 1997 11:43:14 +0930 (CST) Message-Id: <199708310213.LAA00788@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: mjacob@feral.com cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, richard@pegasus.com Subject: Re: Is this (SCSI) tape drive compatible with FreeBSD? In-reply-to: Your message of "Sat, 30 Aug 1997 17:15:39 MST." <199708310015.RAA00360@ns.feral.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 Aug 1997 11:43:12 +0930 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >A 250meg capacity is awfully small today, and the tapes are too expensive. > >They're also excruciatingly slow. > > This isn't even 250Meg. It's QIC-120 (120Meg) or QIC-150. > The Viper 150 will happily read and write the 250 and 525MB extended-length tapes. (Yes I have one, yes, I have used these tapes). Whilst the criticism that these drives are "slow" and the tapes "expensive" is not entirely without basis, it's worth bearing in mind that these drives are *robust*, and properly stored the media are very stable. You won't find this in any current drive or media except (perhaps) a DLT. mike From owner-freebsd-hardware Sat Aug 30 19:16:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA13083 for hardware-outgoing; Sat, 30 Aug 1997 19:16:45 -0700 (PDT) Received: from ns.feral.com (root@feral.mauswerks.net [204.152.96.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA13066; Sat, 30 Aug 1997 19:16:41 -0700 (PDT) Received: from feral.feral.com.feral.COM (feral [192.67.166.5]) by ns.feral.com (8.8.6/8.8.6) with SMTP id TAA00598; Sat, 30 Aug 1997 19:11:57 -0700 Date: Sat, 30 Aug 1997 19:11:57 -0700 From: Matthew Jacob Message-Id: <199708310211.TAA00598@ns.feral.com> To: mike@smith.net.au Subject: Re: Is this (SCSI) tape drive compatible with FreeBSD? Cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, richard@pegasus.com reply-to: mjacob@feral.com Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> >A 250meg capacity is awfully small today, and the tapes are too expensive. >> >They're also excruciatingly slow. >> >> This isn't even 250Meg. It's QIC-120 (120Meg) or QIC-150. >> > >The Viper 150 will happily read and write the 250 and 525MB >extended-length tapes. > Very interesting. This wasn't qualified by Sun, that I recall. I'd check to see whether it's a 2150S or a 2150. The drives aren't *that* robust- I'd say an old 9 track is more robust, mechanical, not vacuum. It's data density is very low though. From owner-freebsd-hardware Sat Aug 30 21:09:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA17261 for hardware-outgoing; Sat, 30 Aug 1997 21:09:26 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA17238; Sat, 30 Aug 1997 21:09:15 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id NAA01035; Sun, 31 Aug 1997 13:37:50 +0930 (CST) Message-Id: <199708310407.NAA01035@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: mjacob@feral.com cc: mike@smith.net.au, freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, richard@pegasus.com Subject: Re: Is this (SCSI) tape drive compatible with FreeBSD? In-reply-to: Your message of "Sat, 30 Aug 1997 19:11:57 MST." <199708310211.TAA00598@ns.feral.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 Aug 1997 13:37:47 +0930 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >>>A 250meg capacity is awfully small today, and the tapes are too expensive. > >>>They're also excruciatingly slow. > >> > >> This isn't even 250Meg. It's QIC-120 (120Meg) or QIC-150. > >> > > > >The Viper 150 will happily read and write the 250 and 525MB > >extended-length tapes. > > > > Very interesting. This wasn't qualified by Sun, that I recall. > I'd check to see whether it's a 2150S or a 2150. A/the Australian Archive (before they were bought) service agent (Peridata) qualified them on both the original head and the current replacement part. The wear characteristics are nonstandard, but appear to be within acceptable tolerances. It's possible that Sun either didn't bother to qualify the extended-length media, tried but decided the wear profile was "different" and therefore bad, or that the 2150 stopped being a mainstream product before it was worth the effort. > The drives aren't *that* robust- I'd say an old 9 track is > more robust, mechanical, not vacuum. It's data density is very low though. I wasn't comparing them to a 1/2" transport, but rather to a 4mm or 8mm mechanism. You will note that, in fact, I specifically mentioned that the only commercially active 1/2" transport currently on the market (DLT) was probably *more* robust. mike From owner-freebsd-hardware Sat Aug 30 21:33:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA18386 for hardware-outgoing; Sat, 30 Aug 1997 21:33:45 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id VAA18364; Sat, 30 Aug 1997 21:33:39 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id OAA27213; Sun, 31 Aug 1997 14:32:47 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id OAA22074; Sun, 31 Aug 1997 14:02:47 +0930 (CST) Message-ID: <19970831140246.12132@lemis.com> Date: Sun, 31 Aug 1997 14:02:46 +0930 From: Greg Lehey To: Mike Smith Cc: mjacob@feral.com, freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, richard@pegasus.com Subject: Re: Is this (SCSI) tape drive compatible with FreeBSD? References: <199708310211.TAA00598@ns.feral.com> <199708310407.NAA01035@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199708310407.NAA01035@word.smith.net.au>; from Mike Smith on Sun, Aug 31, 1997 at 01:37:47PM +0930 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Aug 31, 1997 at 01:37:47PM +0930, Mike Smith wrote: >> The drives aren't *that* robust- I'd say an old 9 track is >> more robust, mechanical, not vacuum. It's data density is very low though. > > I wasn't comparing them to a 1/2" transport, but rather to a 4mm or 8mm > mechanism. You will note that, in fact, I specifically mentioned that > the only commercially active 1/2" transport currently on the market > (DLT) was probably *more* robust. DLT is 1/2"? News to me. And certainly DLT isn't what people think of when you talk 1/2" tape. Greg From owner-freebsd-hardware Sat Aug 30 21:39:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA18665 for hardware-outgoing; Sat, 30 Aug 1997 21:39:15 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA18643; Sat, 30 Aug 1997 21:39:04 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id OAA01253; Sun, 31 Aug 1997 14:07:39 +0930 (CST) Message-Id: <199708310437.OAA01253@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Greg Lehey cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Is this (SCSI) tape drive compatible with FreeBSD? In-reply-to: Your message of "Sun, 31 Aug 1997 14:02:46 +0930." <19970831140246.12132@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 Aug 1997 14:07:37 +0930 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Sun, Aug 31, 1997 at 01:37:47PM +0930, Mike Smith wrote: > >> The drives aren't *that* robust- I'd say an old 9 track is > >> more robust, mechanical, not vacuum. It's data density is very low though. > > > > I wasn't comparing them to a 1/2" transport, but rather to a 4mm or 8mm > > mechanism. You will note that, in fact, I specifically mentioned that > > the only commercially active 1/2" transport currently on the market > > (DLT) was probably *more* robust. > > DLT is 1/2"? News to me. And certainly DLT isn't what people think > of when you talk 1/2" tape. *chuckle* DLT is a direct descendant of the venerable TK-50. Take a look at one sometime. 8) > Greg mike From owner-freebsd-hardware Sat Aug 30 22:01:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA19488 for hardware-outgoing; Sat, 30 Aug 1997 22:01:36 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA19482 for ; Sat, 30 Aug 1997 22:01:34 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id WAA02240; Sat, 30 Aug 1997 22:00:59 -0700 (PDT) To: Mike Smith cc: Greg Lehey , freebsd-hardware@FreeBSD.ORG Subject: Re: Is this (SCSI) tape drive compatible with FreeBSD? In-reply-to: Your message of "Sun, 31 Aug 1997 14:07:37 +0930." <199708310437.OAA01253@word.smith.net.au> Date: Sat, 30 Aug 1997 22:00:59 -0700 Message-ID: <2236.873003659@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [redirected to -hardware only; TK-50s hardly need to be discussed in multiple lists :)] > *chuckle* DLT is a direct descendant of the venerable TK-50. Take a > look at one sometime. 8) Cool! Does this mean that the tape followers also frequently become detached and stuck in the drive where they may only be removed by unit disassembly? :-) Jordan From owner-freebsd-hardware Sat Aug 30 22:11:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA20103 for hardware-outgoing; Sat, 30 Aug 1997 22:11:52 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA20093 for ; Sat, 30 Aug 1997 22:11:43 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id OAA01505; Sun, 31 Aug 1997 14:39:26 +0930 (CST) Message-Id: <199708310509.OAA01505@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jordan K. Hubbard" cc: Mike Smith , Greg Lehey , freebsd-hardware@FreeBSD.ORG Subject: Re: Is this (SCSI) tape drive compatible with FreeBSD? In-reply-to: Your message of "Sat, 30 Aug 1997 22:00:59 MST." <2236.873003659@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 Aug 1997 14:39:19 +0930 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > [redirected to -hardware only; TK-50s hardly need to be discussed in > multiple lists :)] > > > *chuckle* DLT is a direct descendant of the venerable TK-50. Take a > > look at one sometime. 8) > > Cool! Does this mean that the tape followers also frequently become > detached and stuck in the drive where they may only be removed by unit > disassembly? :-) I dunno; I only read up on DLTs recently when we were asked to quote on a direct-to-disk recording solution for the next Leonid(e?)s shower. (As an add-on to a new meteor radar we're developing). At a data rate of around 1MB/s and a 6-hour shower, we need about 25GB of storage that can keep up. The two candidates were a fast tape (AIT or DLT) and lots of disk. If/when someone ponies up the $5k or so that a decent DLT will cost me, I'll run it and tell you; certainly my experience with the TK-50 indicates that frotzing with the mechanism in either the tape or the unit is a recipe for certain disaster. I have some not-so-fond memories of being called over by a FOAF to "fix" his TK-50 after he "had a problem" with it. He'd been playing with the cart and misaligned something so that it wound about five metres of tangled tape onto the takeup spool before jamming tight, or at least that was the condition it was in when _I_ got to see it 8) mike > Jordan > From owner-freebsd-hardware Sat Aug 30 22:23:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA20457 for hardware-outgoing; Sat, 30 Aug 1997 22:23:17 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA20451 for ; Sat, 30 Aug 1997 22:23:13 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id WAA02302; Sat, 30 Aug 1997 22:19:16 -0700 (PDT) To: Mike Smith cc: Greg Lehey , freebsd-hardware@FreeBSD.ORG Subject: Re: Is this (SCSI) tape drive compatible with FreeBSD? In-reply-to: Your message of "Sun, 31 Aug 1997 14:39:19 +0930." <199708310509.OAA01505@word.smith.net.au> Date: Sat, 30 Aug 1997 22:19:16 -0700 Message-ID: <2298.873004756@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I have some not-so-fond memories of being called over by a FOAF to > "fix" his TK-50 after he "had a problem" with it. He'd been playing > with the cart and misaligned something so that it wound about five > metres of tangled tape onto the takeup spool before jamming tight, or > at least that was the condition it was in when _I_ got to see it 8) Heh. Well, back when I was in charge of 250 or so uVAX II's and Vaxstation 2000s at UCB, we had perfectly good TK50s and their cartridges misbehave so frequently with regard to the detached-follower problem that all of us carried around a little kit with us for disassembling the drives and removing tape followers (one of the techs even repaired the tapes, though I generally just binned them and said "sorry man, your data's toast" :-). For those who don't know how the TK-50s used to work, the tape cartridge has this little stiffened metal tab at the very end of the tape which the drive latches on to when it's feeding the tape in. Apparently the bond between tape and metal tab wasn't all that great back then and would frequently get separated from the tape, rendering the drive (which retained the tab) inoperable. Even more fun was when the tape came detached from the cartridge at the other end, after you'd read an entire tape into the drive. You had to take the drive apart and wind all that tape back off again. "The horror... the horror..." :-) Jordan From owner-freebsd-hardware Sat Aug 30 23:18:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA23070 for hardware-outgoing; Sat, 30 Aug 1997 23:18:44 -0700 (PDT) Received: from pegasus.com (pegasus.com [206.127.225.31]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA23051; Sat, 30 Aug 1997 23:18:38 -0700 (PDT) Received: by pegasus.com (8.6.8/PEGASUS-2.2) id UAA14714; Sat, 30 Aug 1997 20:11:32 -1000 Date: Sat, 30 Aug 1997 20:11:32 -1000 From: richard@pegasus.com (Richard Foulk) Message-Id: <199708310611.UAA14714@pegasus.com> In-Reply-To: Mike Smith "Re: Is this (SCSI) tape drive compatible with FreeBSD?" (Aug 31, 11:43am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Mike Smith , mjacob@feral.com Subject: Re: Is this (SCSI) tape drive compatible with FreeBSD? Cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk } > >A 250meg capacity is awfully small today, and the tapes are too expensive. } > >They're also excruciatingly slow. } > } > This isn't even 250Meg. It's QIC-120 (120Meg) or QIC-150. } > } } The Viper 150 will happily read and write the 250 and 525MB } extended-length tapes. } } (Yes I have one, yes, I have used these tapes). } } Whilst the criticism that these drives are "slow" and the tapes } "expensive" is not entirely without basis, it's worth bearing in mind } that these drives are *robust*, and properly stored the media are very } stable. I forgot to mention that they're fairly noisy too. } You won't find this in any current drive or media except (perhaps) a } DLT. } Considering the amount of data trasferred, the numbers show and certainly my experiences do; that the Exabyte drives are more robust than QIC. I suppose you could say that QIC was more robust back when they were more widely used and less data was being archived. In today's world they're not all that robust when compared to the alternatives. Richard