From owner-freebsd-hardware Sun Sep 20 03:09:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA22016 for freebsd-hardware-outgoing; Sun, 20 Sep 1998 03:09:37 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mauibuilt.com (mauibuilt.com [205.166.249.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA21990 for ; Sun, 20 Sep 1998 03:09:16 -0700 (PDT) (envelope-from freebsd@mauibuilt.com) Received: (from freebsd@localhost) by mauibuilt.com (8.8.8/8.8.7) id KAA11366 for freebsd-hardware@freebsd.org; Sun, 20 Sep 1998 10:50:44 GMT (envelope-from freebsd) From: FreeBSD MAIL Message-Id: <199809201050.KAA11366@mauibuilt.com> Subject: Please Help with Digiboard To: freebsd-isp@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Date: Sat, 19 Sep 1998 18:28:23 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am having problems with a Digiboard 16em. I have been searching the mailing lists and found little information about my problem, but it is mentioned and there may have been a fix. This is there error I get on boot. dgb0: PC/Xi 512K dgb0 at 0x224-0x227 maddr 0xfc0000 msize 524288 flags 0x2 on isa dgb0: 2nd reset failed I played with memory size between 8 and 16 megs as I had read that this might be the problem, as well as setting the flags in the kernel (0x01 0x02) to no avail.. I have built all the /dev/cuaD0X enteries as well /as /dev/ttyD0X and added them to /etc/ttys. I have the cable from the Digiboard pluged into EBI/in port on the breakout box and have a modem pluged into port 1. I try and talk to the modem using cu and this is what I get. /root 103% cu -s 9600 -l /dev/cuaD00 cu: open (/dev/cuaD00): Device not configured cu: /dev/cuaD00: Line in use Am I talking to the card in the correct manner? is there some patch to make the Xem cards work.. (ie the 16em). Any help is much apreciated. Thanks in advance Richard Puga puga@mauibuilt.com freebsd@mauibuilt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Sep 20 04:27:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA07695 for freebsd-hardware-outgoing; Sun, 20 Sep 1998 04:27:22 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from control.colossus.dyn.ml.org (206-18-115-80.la.inreach.net [206.18.115.80]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA07510 for ; Sun, 20 Sep 1998 04:25:48 -0700 (PDT) (envelope-from dburr@colossus.dyn.ml.org) Received: (from dburr@localhost) by control.colossus.dyn.ml.org (8.8.8/8.8.8) id EAA22093 for freebsd-hardware@freebsd.org; Sun, 20 Sep 1998 04:21:29 -0700 (PDT) (envelope-from dburr) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 20 Sep 1998 04:21:29 -0700 (PDT) Organization: Computer Help From: Donald Burr To: FreeBSD Hardware Subject: UNDER-clocking Cyrix 6x86MX-PR233 at 66x2.5 instead of 75x2.5? OK? Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just put together a new system (I bought it piecemeal: motherboard from Company A, CPU from company B, etc. and slapped it together myself) The motherboard uses the Intel i430TX chipset, and the processor I am using is an IBM/Cyrix 6x86MX-PR233. At first, I tried setting up the system the way the processor was marked, namely 75MHz bus speed, 2.5x clock multiplier, 2.9v. But I got random crashes, and the system was otherwise unstable. I have heard that some systems/boards/peripherals can't take the higher 75MHz bus speed, so I tried moving the bus speed down to 66 MHz, and left everything else as is (clock multiplier, etc.) Now the CPU is detected as a 6x86MX-PR200, and everything works perfectly. Since it seems to work OK now, I think I'll keep it set up this way. I just wanted to make sure if it's OK to "UNDER-clock" the CPU like this -- will doing this damage the CPU or motherboard or anything? Please reply by email &/or to the list. Thanks! --- Donald Burr *NEW EMAIL ADDRESS!* | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ#16997506 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Sep 20 06:40:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA26298 for freebsd-hardware-outgoing; Sun, 20 Sep 1998 06:40:36 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from clifford.inch.com (clifford.inch.com [207.240.140.163]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA26293 for ; Sun, 20 Sep 1998 06:40:34 -0700 (PDT) (envelope-from omar@clifford.inch.com) Received: (from omar@localhost) by clifford.inch.com (8.8.5/8.8.5) id JAA18677 for hardware@freebsd.org; Sun, 20 Sep 1998 09:34:42 -0400 Message-ID: <19980920093441.A18630@clifford.inch.com> Date: Sun, 20 Sep 1998 09:34:42 -0400 From: Omar Thameen To: hardware@FreeBSD.ORG Subject: SCSI card used at cdrom.com? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What SCSI controller is being used in the FreeBSD boxes at cdrom.com? We like to mirror what y'all use because if it performs there, we know it'll be great for us. We used to use Buslogic BT948's mostly (though we do have a news machine with Adaptec 2940's), but we want to get an ultra-wide controller and our vendor is telling us he can't locate Mylex's BT958's. Thanks for any info, Omar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Sep 20 08:32:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09131 for freebsd-hardware-outgoing; Sun, 20 Sep 1998 08:32:32 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from tasam.com (tasam.com [198.232.144.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09126 for ; Sun, 20 Sep 1998 08:32:29 -0700 (PDT) (envelope-from clash@tasam.com) Received: from bug (bug.tasam.com [198.232.144.254]) by tasam.com (8.9.1/8.9.1) with SMTP id LAA05788; Sun, 20 Sep 1998 11:31:28 -0400 (EDT) Message-ID: <004101bde4ab$bf17a3e0$f10408d1@bug.tasam.com> From: "Joe Gleason" To: Cc: Subject: Re: over 512 megs memory problems... Date: Sun, 20 Sep 1998 11:30:44 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2110.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org That makes sense, do you know of a motherboard that can cache more than 512mb? I just looked in my motherboard manual and it says that it is the L2 cache on the processor that does the caching so the board has none. So should I look for a board that has it's own L2 cache as well? We will be replacing that board anyways because it was doing other annoying things. Joe Gleason Tasam >> We have just bought a 256 meg dimm to boost our total ram up to 640 megs. >> There is a problem, the system goes reallly slow. We've tried just about >> everything, maxmem, iosiz, bouncebuffer, changing around the memory hole, >> and nothing works except not going over 512 megs in our system. The 256 >> dimm works fine, but if we go over 512 megs, it goes slow. Has anyone else >> experienced this before, or have any more ideas for us? > >Your motherboard/CPU combination is probably incapable of caching more >than 512MB of memory. > >-- >\\ Sometimes you're ahead, \\ Mike Smith >\\ sometimes you're behind. \\ mike@smith.net.au >\\ The race is long, and in the \\ msmith@freebsd.org >\\ end it's only with yourself. \\ msmith@cdrom.com > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Sep 20 11:47:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14292 for freebsd-hardware-outgoing; Sun, 20 Sep 1998 11:47:48 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from word.smith.net.au (castles359.castles.com [208.214.167.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14217 for ; Sun, 20 Sep 1998 11:47:15 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id LAA07584; Sun, 20 Sep 1998 11:52:11 -0700 (PDT) (envelope-from mike@word.smith.net.au) Message-Id: <199809201852.LAA07584@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Joe Gleason" cc: mike@smith.net.au, freebsd-hardware@FreeBSD.ORG Subject: Re: over 512 megs memory problems... In-reply-to: Your message of "Sun, 20 Sep 1998 11:30:44 EDT." <004101bde4ab$bf17a3e0$f10408d1@bug.tasam.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Sep 1998 11:52:10 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > That makes sense, do you know of a motherboard that can cache more than > 512mb? > > I just looked in my motherboard manual and it says that it is the L2 cache > on the processor that does the caching so the board has none. So should I > look for a board that has it's own L2 cache as well? It would have helped a *lot* if you had identified your processor/ chipset combination in your original post. I don't quite understand whether you expect us to magically read your mind or to work out where you're posting from, travel there, break in and examine your hardware for you while you sleep. With the miniscule crumbs of information that you've let slip so far, it seems that you're using a Pentium II of the < 350MHz variety, and yes, the 512MB cache limitation is a feature of the processor. > We will be replacing that board anyways because it was doing other > annoying things. Smoking in bed? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Sep 20 13:02:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27125 for freebsd-hardware-outgoing; Sun, 20 Sep 1998 13:02:48 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27120 for ; Sun, 20 Sep 1998 13:02:46 -0700 (PDT) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.8.7) with SMTP id PAA00826; Sun, 20 Sep 1998 15:02:05 -0500 (CDT) Message-Id: <199809202002.PAA00826@ns.tar.com> From: "Richard Seaman, Jr." To: "Mike Smith" Cc: "freebsd-hardware@FreeBSD.ORG" Date: Sun, 20 Sep 98 15:02:05 -0500 Reply-To: "Richard Seaman, Jr." 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: over 512 megs memory problems... Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 20 Sep 1998 11:52:10 -0700, Mike Smith wrote: >With the miniscule crumbs of information that you've let slip so far, >it seems that you're using a Pentium II of the < 350MHz variety, and >yes, the 512MB cache limitation is a feature of the processor. Actually. the very newest PII 66Mhz chips will cache 4GB if they're the Intel Boxed processors. S-Spec SL33D, SL2YK, SL2WY will all give you 4GB. There may be some unboxed 66Mhz processors that will cache 4GB also. Also, I understand that the newer 66Mhz chips are on the smaller .25m die size too. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Sep 20 15:01:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16585 for freebsd-hardware-outgoing; Sun, 20 Sep 1998 15:01:36 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from clifford.inch.com (clifford.inch.com [207.240.140.163]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16580 for ; Sun, 20 Sep 1998 15:01:34 -0700 (PDT) (envelope-from omar@clifford.inch.com) Received: (from omar@localhost) by clifford.inch.com (8.8.5/8.8.5) id RAA21591 for hardware@FreeBSD.ORG; Sun, 20 Sep 1998 17:55:38 -0400 Message-ID: <19980920175537.B21210@clifford.inch.com> Date: Sun, 20 Sep 1998 17:55:37 -0400 From: Omar Thameen To: hardware@FreeBSD.ORG Subject: Re: SCSI card used at cdrom.com? References: <19980920093441.A18630@clifford.inch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19980920093441.A18630@clifford.inch.com>; from Omar Thameen on Sun, Sep 20, 1998 at 09:34:42AM -0400 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Sep 20, 1998 at 09:34:42AM -0400, Omar Thameen wrote: > What SCSI controller is being used in the FreeBSD boxes at cdrom.com? > We like to mirror what y'all use because if it performs there, we > know it'll be great for us. I've just been made aware that the info is at ftp://ftp.cdrom.com/archive-info/configuration ...so here it is for the archives :-) Omar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Sep 20 15:04:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17245 for freebsd-hardware-outgoing; Sun, 20 Sep 1998 15:04:58 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA17240 for ; Sun, 20 Sep 1998 15:04:52 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id AAA09100 for hardware@FreeBSD.ORG; Mon, 21 Sep 1998 00:04:20 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id D69E11513; Sun, 20 Sep 1998 23:54:26 +0200 (CEST) Date: Sun, 20 Sep 1998 23:54:26 +0200 From: Ollivier Robert To: hardware@FreeBSD.ORG Subject: Re: SCSI card used at cdrom.com? Message-ID: <19980920235426.A10723@keltia.freenix.fr> Mail-Followup-To: hardware@FreeBSD.ORG References: <19980920093441.A18630@clifford.inch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.4i In-Reply-To: <19980920093441.A18630@clifford.inch.com>; from Omar Thameen on Sun, Sep 20, 1998 at 09:34:42AM -0400 X-Operating-System: FreeBSD 3.0-BETA/ELF ctm#4660 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Omar Thameen: > What SCSI controller is being used in the FreeBSD boxes at cdrom.com? > We like to mirror what y'all use because if it performs there, we > know it'll be great for us. Check with , there is a file named config that describe the configuration. I think there is 3 busses, two on a 3940 and one on a 2940. > machine with Adaptec 2940's), but we want to get an ultra-wide > controller and our vendor is telling us he can't locate Mylex's > BT958's. Either Adaptec 7880/7890-based or NCR/Symbios 875/6 cards should do fine. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-BETA #0: Sat Sep 19 23:38:25 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Sep 20 15:16:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20155 for freebsd-hardware-outgoing; Sun, 20 Sep 1998 15:16:17 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20144 for ; Sun, 20 Sep 1998 15:16:08 -0700 (PDT) (envelope-from dkelly@n4hhe.ampr.org) Received: from nospam.hiwaay.net (tnt1-155.HiWAAY.net [208.147.147.155]) by mail.HiWAAY.net (8.9.0/8.9.0) with ESMTP id RAA13122; Sun, 20 Sep 1998 17:15:38 -0500 (CDT) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.8) with ESMTP id QAA13708; Sun, 20 Sep 1998 16:45:47 -0500 (CDT) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199809202145.QAA13708@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: Donald Burr cc: FreeBSD Hardware From: David Kelly Subject: Re: UNDER-clocking Cyrix 6x86MX-PR233 at 66x2.5 instead of 75x2.5? OK? In-reply-to: Message from Donald Burr of "Sun, 20 Sep 1998 04:21:29 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Sep 1998 16:45:46 -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Donald Burr writes: > I have heard that some systems/boards/peripherals can't take the higher > 75MHz bus speed, so I tried moving the bus speed down to 66 MHz, and left > everything else as is (clock multiplier, etc.) Now the CPU is detected as > a 6x86MX-PR200, and everything works perfectly. > > Since it seems to work OK now, I think I'll keep it set up this way. I > just wanted to make sure if it's OK to "UNDER-clock" the CPU like this -- > will doing this damage the CPU or motherboard or anything? "Its a PC so if it works then just do it." It is *possible* the faster chip would not work right at a slower rate. While its being clocked slower, the silicon still switches at a rate that is supposed to be fast enough for a faster bus. If by some idiocy the chip latched onto data before a clock edge and before it was stable then it would do the wrong thing. I don't think this would be the case as the final decision as to a bus state should be at clock transition. Some CPU's have to run at some minimum clock rate in order to refresh internal dynamic memory. Don't worry about that until you drop to 1 MHz or so. Its a problem for the low power shutdown people and In-Circuit Emulator designers. With all that said, I'm running a PPro 166/512k. Supposed to be a 66 MHz bus. Chip runs real nice at 200/66 MHz too but I've decided either my ancient ATI Mach32 video card or my ancient non-ultra Adaptec 2940, or my new Asus SC875 (Symbios) SCSI card don't like a 66 MHz bus on an Asus P6NP5 MB. The NCR driver has reported some faults with PCI access. The system either a couple of times per day, or it would wait months. Always during heavy disk activity ("cvs -q update -P -d" was a favorite) combinded with something graphic intensive, always Netscape. A mouse click on Netscape which required disk activity (swap?) during the other disk activity often resulted in a freeze. There are BIOS parameters for the PCI bus I could mess with, I guess. Things like "PCI Latency" and such. Don't understand them. Can't reliably reproduce my problem. Ain't gonna touch them. Values are set by the "factory default" option on the BIOS. That's another long story where my floppy didn't work until a "factory default" altho I couldn't see any visible BIOS parameter changes. Dropped the bus divider down to 60 MHz, so now I run 180/60. Rock solid the past 2 months. So I'm overclocking my CPU, underclocking my bus. When I first played with overclocking, found the CPU ran at 233 without problem for the 30 minutes I tested it (running rc5des and "make kernel" several times.) 266 MHz wouldn't boot. Considering 233 ran well I used 200. Am thinking its time once again to see how 210 or 240 work. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Sep 20 18:00:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18451 for freebsd-hardware-outgoing; Sun, 20 Sep 1998 18:00:56 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from tasam.com (tasam.com [198.232.144.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18429 for ; Sun, 20 Sep 1998 18:00:47 -0700 (PDT) (envelope-from clash@tasam.com) Received: from bug (bug.tasam.com [198.232.144.254]) by tasam.com (8.9.1/8.9.1) with SMTP id UAA21235; Sun, 20 Sep 1998 20:59:34 -0400 (EDT) Message-ID: <001a01bde4fb$17dff780$f10408d1@bug.tasam.com> From: "Joe Gleason" To: "Mike Smith" Cc: Subject: Re: over 512 megs memory problems... Date: Sun, 20 Sep 1998 20:59:26 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2110.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry for not mentioning the details. It seems I get stupider the more frusterated with the problem. ;-) We are using a single PII 233 on a Tyan S1632DL (BX Chipset). Am I to understand that a newer processor (>333mhz) will solve this problem? Joe Gleason Tasam >> That makes sense, do you know of a motherboard that can cache more than >> 512mb? >> >> I just looked in my motherboard manual and it says that it is the L2 cache >> on the processor that does the caching so the board has none. So should I >> look for a board that has it's own L2 cache as well? > >It would have helped a *lot* if you had identified your processor/ >chipset combination in your original post. I don't quite understand >whether you expect us to magically read your mind or to work out where >you're posting from, travel there, break in and examine your hardware >for you while you sleep. > >With the miniscule crumbs of information that you've let slip so far, >it seems that you're using a Pentium II of the < 350MHz variety, and >yes, the 512MB cache limitation is a feature of the processor. > >> We will be replacing that board anyways because it was doing other >> annoying things. > >Smoking in bed? >-- >\\ Sometimes you're ahead, \\ Mike Smith >\\ sometimes you're behind. \\ mike@smith.net.au >\\ The race is long, and in the \\ msmith@freebsd.org >\\ end it's only with yourself. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Sep 20 19:12:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00774 for freebsd-hardware-outgoing; Sun, 20 Sep 1998 19:12:50 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from word.smith.net.au (castles236.castles.com [208.214.165.236]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00749 for ; Sun, 20 Sep 1998 19:12:30 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id TAA02260; Sun, 20 Sep 1998 19:17:31 -0700 (PDT) (envelope-from mike@word.smith.net.au) Message-Id: <199809210217.TAA02260@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Joe Gleason" cc: "Mike Smith" , freebsd-hardware@FreeBSD.ORG Subject: Re: over 512 megs memory problems... In-reply-to: Your message of "Sun, 20 Sep 1998 20:59:26 EDT." <001a01bde4fb$17dff780$f10408d1@bug.tasam.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Sep 1998 19:17:30 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Sorry for not mentioning the details. It seems I get stupider the more > frusterated with the problem. ;-) > > We are using a single PII 233 on a Tyan S1632DL (BX Chipset). > > Am I to understand that a newer processor (>333mhz) will solve this problem? Correct. Sounds like the very new 66MHz bus parts will also do this, but on a BX board you should look to a 100MHz CPU for best results. (And PC100 DIMMs, of course). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Sep 20 20:11:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09286 for freebsd-hardware-outgoing; Sun, 20 Sep 1998 20:11:27 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09264 for ; Sun, 20 Sep 1998 20:11:21 -0700 (PDT) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id XAA04589; Sun, 20 Sep 1998 23:10:14 -0400 (EDT) Date: Sun, 20 Sep 1998 23:10:14 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: Ollivier Robert cc: hardware@FreeBSD.ORG Subject: Re: SCSI card used at cdrom.com? In-Reply-To: <19980920235426.A10723@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Are there any known problems with the Adaptec cards with the new 100MHz chipsets? Thanks, Charles On Sun, 20 Sep 1998, Ollivier Robert wrote: > According to Omar Thameen: > > What SCSI controller is being used in the FreeBSD boxes at cdrom.com? > > We like to mirror what y'all use because if it performs there, we > > know it'll be great for us. > > Check with , there is a file named config that > describe the configuration. > > I think there is 3 busses, two on a 3940 and one on a 2940. > > > machine with Adaptec 2940's), but we want to get an ultra-wide > > controller and our vendor is telling us he can't locate Mylex's > > BT958's. > > Either Adaptec 7880/7890-based or NCR/Symbios 875/6 cards should do fine. > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-BETA #0: Sat Sep 19 23:38:25 CEST 1998 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Sep 20 20:55:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA16861 for freebsd-hardware-outgoing; Sun, 20 Sep 1998 20:55:17 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from cortes.cibnor.mx (cortes.cibnor.mx [200.23.161.225]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA16843 for ; Sun, 20 Sep 1998 20:55:10 -0700 (PDT) (envelope-from lmiller@cibnor.mx) Received: from cortes.cibnor.mx by cortes.cibnor.mx id aa16471; 20 Sep 98 21:55 MDT Date: Sun, 20 Sep 1998 21:55:04 -0600 (MDT) From: Larry Miller To: Mike Smith cc: freebsd-hardware@FreeBSD.ORG Subject: Re: over 512 megs memory problems... In-Reply-To: <199809210217.TAA02260@word.smith.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Correct. Sounds like the very new 66MHz bus parts will also do this, > but on a BX board you should look to a 100MHz CPU for best results. > (And PC100 DIMMs, of course). Related point; anybody know if there's a problem running PC100 DIMMS with a Pentium 233 on a BX board? We're short on budget right now and my thought is to get us running, with an easy upgrade path into the 100mhz world as CPU prices drop. Thanks-- Larry Larry Miller Administrador de Redes / Network Administrator Centro de Investigaciones Biologicas del Noroeste, La Paz, BCS Mexico lmiller@cibnor.mx http://www.cibnor.mx/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Sep 20 21:47:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25141 for freebsd-hardware-outgoing; Sun, 20 Sep 1998 21:47:11 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from word.smith.net.au (castles236.castles.com [208.214.165.236]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25101 for ; Sun, 20 Sep 1998 21:46:43 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id VAA03322; Sun, 20 Sep 1998 21:51:12 -0700 (PDT) (envelope-from mike@word.smith.net.au) Message-Id: <199809210451.VAA03322@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Larry Miller cc: Mike Smith , freebsd-hardware@FreeBSD.ORG Subject: Re: over 512 megs memory problems... In-reply-to: Your message of "Sun, 20 Sep 1998 21:55:04 MDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Sep 1998 21:51:11 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Correct. Sounds like the very new 66MHz bus parts will also do this, > > but on a BX board you should look to a 100MHz CPU for best results. > > (And PC100 DIMMs, of course). > > Related point; anybody know if there's a problem running PC100 DIMMS with > a Pentium 233 on a BX board? We're short on budget right now and my > thought is to get us running, with an easy upgrade path into the 100mhz > world as CPU prices drop. Shouldn't be any problems. Ignore any FUD. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Sep 20 22:10:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28129 for freebsd-hardware-outgoing; Sun, 20 Sep 1998 22:10:58 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from tasam.com (tasam.com [198.232.144.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA28121 for ; Sun, 20 Sep 1998 22:10:54 -0700 (PDT) (envelope-from clash@tasam.com) Received: from bug (bug.tasam.com [198.232.144.254]) by tasam.com (8.9.1/8.9.1) with SMTP id BAA09989; Mon, 21 Sep 1998 01:10:13 -0400 (EDT) Message-ID: <003101bde51e$1c6df630$f10408d1@bug.tasam.com> From: "Joe Gleason" To: "Larry Miller" Cc: Subject: Re: over 512 megs memory problems... Date: Mon, 21 Sep 1998 01:09:36 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2110.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org That is what we are doing now and we have no problems. (Untill this little 512mb issue) We are running a BX board with a 233 PII and have been buying PC100 ram for the exact same reasons you have. ;-) Joe Gleason Tasam > >Related point; anybody know if there's a problem running PC100 DIMMS with >a Pentium 233 on a BX board? We're short on budget right now and my >thought is to get us running, with an easy upgrade path into the 100mhz >world as CPU prices drop. > >Thanks-- Larry > >Larry Miller >Administrador de Redes / Network Administrator >Centro de Investigaciones Biologicas del Noroeste, La Paz, BCS Mexico >lmiller@cibnor.mx http://www.cibnor.mx/ > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Sep 20 22:15:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28734 for freebsd-hardware-outgoing; Sun, 20 Sep 1998 22:15:23 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from tasam.com (tasam.com [198.232.144.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA28721 for ; Sun, 20 Sep 1998 22:15:05 -0700 (PDT) (envelope-from clash@tasam.com) Received: from bug (bug.tasam.com [198.232.144.254]) by tasam.com (8.9.1/8.9.1) with SMTP id BAA10558; Mon, 21 Sep 1998 01:14:31 -0400 (EDT) Message-ID: <004101bde51e$b6313660$f10408d1@bug.tasam.com> From: "Joe Gleason" To: "spork" Cc: Subject: Re: SCSI card used at cdrom.com? Date: Mon, 21 Sep 1998 01:13:20 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2110.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wont the PCI bus still run at it's 33mhz regardless of what the system bus is and therefor the system bus speed would have no effect on PCI devices? Joe Gleason Tasam >Are there any known problems with the Adaptec cards with the new 100MHz >chipsets? > >Thanks, > >Charles > >On Sun, 20 Sep 1998, Ollivier Robert wrote: > >> According to Omar Thameen: >> > What SCSI controller is being used in the FreeBSD boxes at cdrom.com? >> > We like to mirror what y'all use because if it performs there, we >> > know it'll be great for us. >> >> Check with , there is a file named config that >> describe the configuration. >> >> I think there is 3 busses, two on a 3940 and one on a 2940. >> >> > machine with Adaptec 2940's), but we want to get an ultra-wide >> > controller and our vendor is telling us he can't locate Mylex's >> > BT958's. >> >> Either Adaptec 7880/7890-based or NCR/Symbios 875/6 cards should do fine. >> -- >> Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr >> FreeBSD keltia.freenix.fr 3.0-BETA #0: Sat Sep 19 23:38:25 CEST 1998 >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-hardware" in the body of the message >> > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Sep 20 23:12:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08106 for freebsd-hardware-outgoing; Sun, 20 Sep 1998 23:12:22 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from word.smith.net.au (castles236.castles.com [208.214.165.236]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08020 for ; Sun, 20 Sep 1998 23:12:02 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (LOCALHOST [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id XAA05524; Sun, 20 Sep 1998 23:16:55 -0700 (PDT) (envelope-from mike@word.smith.net.au) Message-Id: <199809210616.XAA05524@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Joe Gleason" cc: "spork" , hardware@FreeBSD.ORG Subject: Re: SCSI card used at cdrom.com? In-reply-to: Your message of "Mon, 21 Sep 1998 01:13:20 EDT." <004101bde51e$b6313660$f10408d1@bug.tasam.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Sep 1998 23:16:54 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Wont the PCI bus still run at it's 33mhz regardless of what the system bus > is and therefor the system bus speed would have no effect on PCI devices? Generally correct, yes. > >Are there any known problems with the Adaptec cards with the new 100MHz > >chipsets? > > > >Thanks, > > > >Charles > > > >On Sun, 20 Sep 1998, Ollivier Robert wrote: > > > >> According to Omar Thameen: > >> > What SCSI controller is being used in the FreeBSD boxes at cdrom.com? > >> > We like to mirror what y'all use because if it performs there, we > >> > know it'll be great for us. > >> > >> Check with , there is a file named config that > >> describe the configuration. > >> > >> I think there is 3 busses, two on a 3940 and one on a 2940. > >> > >> > machine with Adaptec 2940's), but we want to get an ultra-wide > >> > controller and our vendor is telling us he can't locate Mylex's > >> > BT958's. > >> > >> Either Adaptec 7880/7890-based or NCR/Symbios 875/6 cards should do fine. > >> -- > >> Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- > roberto@keltia.freenix.fr > >> FreeBSD keltia.freenix.fr 3.0-BETA #0: Sat Sep 19 23:38:25 CEST 1998 > >> > >> > >> To Unsubscribe: send mail to majordomo@FreeBSD.org > >> with "unsubscribe freebsd-hardware" in the body of the message > >> > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-hardware" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 21 02:10:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA03021 for freebsd-hardware-outgoing; Mon, 21 Sep 1998 02:10:22 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA02955 for ; Mon, 21 Sep 1998 02:10:11 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id CAA10650; Mon, 21 Sep 1998 02:04:20 -0700 (PDT) Message-Id: <199809210904.CAA10650@implode.root.com> To: Omar Thameen cc: hardware@FreeBSD.ORG Subject: Re: SCSI card used at cdrom.com? In-reply-to: Your message of "Sun, 20 Sep 1998 09:34:42 EDT." <19980920093441.A18630@clifford.inch.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 21 Sep 1998 02:04:20 -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >What SCSI controller is being used in the FreeBSD boxes at cdrom.com? >We like to mirror what y'all use because if it performs there, we >know it'll be great for us. > >We used to use Buslogic BT948's mostly (though we do have a news >machine with Adaptec 2940's), but we want to get an ultra-wide >controller and our vendor is telling us he can't locate Mylex's >BT958's. I saw your followup that you found my "configuration" file regarding the above. I should point out that the configuration will be changing soon when we move to RAID 5 for all of the disk space. The new config will be a Mylex DAC960SXI hanging off of a two channel AHA-3940AUW (which is aic-7895 based). The Mylex SCSI-SCSI RAID controller has six SCSI busses - two will be configured as host busses with the other four going to the disk drives. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 21 05:33:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28358 for freebsd-hardware-outgoing; Mon, 21 Sep 1998 05:33:56 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from laker.net (jet.laker.net [205.245.74.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA28352 for ; Mon, 21 Sep 1998 05:33:53 -0700 (PDT) (envelope-from sfriedri@laker.net) Received: from nt (digital-fll-150.laker.net [205.245.75.50]) by laker.net (8.9.0/8.9.LAKERNET.NO-SPAM.SPAMMERS.AND.RELAYS.WILL.BE.TRACKED.AND.PROSECUTED.) with SMTP id IAA27650; Mon, 21 Sep 1998 08:33:06 -0400 Message-Id: <199809211233.IAA27650@laker.net> From: "Steve Friedrich" To: "Joe Gleason" , "Mike Smith" Cc: "hardware@FreeBSD.ORG" , "spork" Date: Mon, 21 Sep 1998 08:32:54 -0400 Reply-To: "Steve Friedrich" X-Mailer: PMMail 98 Professional (2.01.1600) For Windows NT (4.0.1381;3) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: SCSI card used at cdrom.com? Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 20 Sep 1998 23:16:54 -0700, Mike Smith wrote: >> Wont the PCI bus still run at it's 33mhz regardless of what the system bus >> is and therefor the system bus speed would have no effect on PCI devices? > >Generally correct, yes. Actually, the correct answer is NO. With the exception of some newer motherboards, the PCI clock is derived from the system bus speed. Some newer moboards de-couple the PCI clock from the system bus. One place to do a little reading is http://www.tomshardware.com/ You'll want to research Front Side Bus. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 21 08:13:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25567 for freebsd-hardware-outgoing; Mon, 21 Sep 1998 08:13:51 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from cortes.cibnor.mx (cortes.cibnor.mx [200.23.161.225]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA25532 for ; Mon, 21 Sep 1998 08:13:31 -0700 (PDT) (envelope-from lmiller@cibnor.mx) Received: from cortes.cibnor.mx by cortes.cibnor.mx id aa22646; 21 Sep 98 9:12 MDT Date: Mon, 21 Sep 1998 09:12:31 -0600 (MDT) From: Larry Miller To: Joe Gleason cc: freebsd-hardware@FreeBSD.ORG Subject: Re: over 512 megs memory problems... In-Reply-To: <003101bde51e$1c6df630$f10408d1@bug.tasam.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Date: Mon, 21 Sep 1998 01:09:36 -0400 > From: Joe Gleason > To: Larry Miller > Cc: freebsd-hardware@FreeBSD.ORG > Subject: Re: over 512 megs memory problems... > > That is what we are doing now and we have no problems. (Untill this little > 512mb issue) > We are running a BX board with a 233 PII and have been buying PC100 ram for > the exact same reasons you have. ;-) Great, thanks. It's so nice to let other folks try things out. ;> Saludos-- Larry Larry Miller Administrador de Redes / Network Administrator Centro de Investigaciones Biologicas del Noroeste, La Paz, BCS Mexico lmiller@cibnor.mx http://www.cibnor.mx/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 21 11:52:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05995 for freebsd-hardware-outgoing; Mon, 21 Sep 1998 11:52:11 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05937 for ; Mon, 21 Sep 1998 11:51:51 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.9.1a/8.9.1) with ESMTP id UAA02800 for ; Mon, 21 Sep 1998 20:51:03 +0200 (MET DST) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by mail.siemens.de (8.9.1a/8.9.1) with ESMTP id UAA04137 for ; Mon, 21 Sep 1998 20:51:03 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id UAA06881 for ; Mon, 21 Sep 1998 20:51:04 +0200 (CEST) From: Andre Albsmeier Message-Id: <199809211850.UAA02011@internal> Subject: Re: SCSI card used at cdrom.com? In-Reply-To: <199809210904.CAA10650@implode.root.com> from David Greenman at "Sep 21, 98 02:04:20 am" To: dg@root.com Date: Mon, 21 Sep 1998 20:50:57 +0200 (CEST) Cc: hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >What SCSI controller is being used in the FreeBSD boxes at cdrom.com? > >We like to mirror what y'all use because if it performs there, we > >know it'll be great for us. > > > >We used to use Buslogic BT948's mostly (though we do have a news > >machine with Adaptec 2940's), but we want to get an ultra-wide > >controller and our vendor is telling us he can't locate Mylex's > >BT958's. > > I saw your followup that you found my "configuration" file regarding the > above. I should point out that the configuration will be changing soon when > we move to RAID 5 for all of the disk space. The new config will be a Mylex > DAC960SXI hanging off of a two channel AHA-3940AUW (which is aic-7895 based). So you are going to use CAM with the new configuration, right ? -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 21 12:56:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21948 for freebsd-hardware-outgoing; Mon, 21 Sep 1998 12:56:27 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21889 for ; Mon, 21 Sep 1998 12:56:15 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id JAA11282; Mon, 21 Sep 1998 09:48:38 -0700 (PDT) (envelope-from mike@word.smith.net.au) Message-Id: <199809211648.JAA11282@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Steve Friedrich" cc: "Joe Gleason" , "Mike Smith" , "hardware@FreeBSD.ORG" , "spork" Subject: Re: SCSI card used at cdrom.com? In-reply-to: Your message of "Mon, 21 Sep 1998 08:32:54 EDT." <199809211233.IAA27650@laker.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Sep 1998 09:48:37 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Sun, 20 Sep 1998 23:16:54 -0700, Mike Smith wrote: > > >> Wont the PCI bus still run at it's 33mhz regardless of what the system bus > >> is and therefor the system bus speed would have no effect on PCI devices? > > > >Generally correct, yes. > > Actually, the correct answer is NO. With the exception of some newer > motherboards, the PCI clock is derived from the system bus speed. Some > newer moboards de-couple the PCI clock from the system bus. One place > to do a little reading is http://www.tomshardware.com/ This place is Overclocker Heaven. If you configure your board correctly, you won't exceed the 33MHz PCI clock limit, and this includes running 100MHz slot 1 processors. > You'll want to research Front Side Bus. Thanks, I know more than I need or want to know about this already. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 21 13:47:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01715 for freebsd-hardware-outgoing; Mon, 21 Sep 1998 13:47:45 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from laker.net (jet.laker.net [205.245.74.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01687 for ; Mon, 21 Sep 1998 13:47:36 -0700 (PDT) (envelope-from sfriedri@laker.net) Received: from nt (digital-pbi-124.laker.net [208.0.233.24]) by laker.net (8.9.0/8.9.LAKERNET.NO-SPAM.SPAMMERS.AND.RELAYS.WILL.BE.TRACKED.AND.PROSECUTED.) with SMTP id QAA17455; Mon, 21 Sep 1998 16:46:37 -0400 Message-Id: <199809212046.QAA17455@laker.net> From: "Steve Friedrich" To: "Mike Smith" Cc: "hardware@FreeBSD.ORG" , "Joe Gleason" , "spork" Date: Mon, 21 Sep 1998 16:46:29 -0400 Reply-To: "Steve Friedrich" X-Mailer: PMMail 98 Professional (2.01.1600) For Windows NT (4.0.1381;3) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: SCSI card used at cdrom.com? Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 21 Sep 1998 09:48:37 -0700, Mike Smith wrote: >> On Sun, 20 Sep 1998 23:16:54 -0700, Mike Smith wrote: >> >> >> Wont the PCI bus still run at it's 33mhz regardless of what the system bus >> >> is and therefor the system bus speed would have no effect on PCI devices? >> > >> >Generally correct, yes. >> >> Actually, the correct answer is NO. With the exception of some newer >> motherboards, the PCI clock is derived from the system bus speed. Some >> newer moboards de-couple the PCI clock from the system bus. One place >> to do a little reading is http://www.tomshardware.com/ > >This place is Overclocker Heaven. If you configure your board >correctly, you won't exceed the 33MHz PCI clock limit, and this >includes running 100MHz slot 1 processors. > I think you missed my real point though. I was trying to tell everyone that on most older moboards, the system bus speed determines the PCI bus speed. So if you have a 60MHz bus speed, you have a 30MHz PCI speed. And a 66MHz bus speed gives you a 33MHz PCI bus. This doesn't pose a problem for correctly designed PCI boards. But some newer moboards allow higher bus speeds, like 87, etc., that will yield PCI bus speeds in excess of the spec, causing problems with some PCI boards. These newer moboards were "caused" by overclockers, but it is quite common to support bus speeds higher than 66, and if that moboard doesn't have separate jumpers for the "front side bus", you will have a PCI bus overspec if you use a bus speed higher than 66. So it really affects us all, thanks to the overclockers. I'm an old hardware guy and I do not condone overclocking. It's really only worthwhile to someone willing to sacrifice system stability for performance. That pretty much restricts it to people playing games, or experimenting. It's definitely not for production machines. >> You'll want to research Front Side Bus. > >Thanks, I know more than I need or want to know about this already. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 21 15:29:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28079 for freebsd-hardware-outgoing; Mon, 21 Sep 1998 15:29:23 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27979 for ; Mon, 21 Sep 1998 15:28:53 -0700 (PDT) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id SAA04038; Mon, 21 Sep 1998 18:27:42 -0400 (EDT) Date: Mon, 21 Sep 1998 18:27:42 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: David Greenman cc: Omar Thameen , hardware@FreeBSD.ORG Subject: Re: SCSI card used at cdrom.com? In-Reply-To: <199809210904.CAA10650@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'd like to throw my question out again, with a bit more of a general slant to it: Does everyone find the adaptec 2940xxx to be reliable and stable? Since we've used the Buslogic for soooo long I just want some reassurances. I recall there were some issues in the past of Adaptec changing things around that broke certain things. Those that do run them, do you enable all of the "options" in your kernel? I'm convinced these are faster than the Buslogic, I just want to make sure the stability is there. We will not be using CAM until 3.0 has been out for a while and we upgrade to that... Any input is welcome! And to David, may I ask a bit about how you came to choose the Mylex raid controller over the CMD? We have pretty much settled on the CMD after many recommendations, but I'd like to hear some of your reasons for going with the Mylex... Thanks, Charles --- Charles Sprickman spork@super-g.com On Mon, 21 Sep 1998, David Greenman wrote: > >What SCSI controller is being used in the FreeBSD boxes at cdrom.com? > >We like to mirror what y'all use because if it performs there, we > >know it'll be great for us. > > > >We used to use Buslogic BT948's mostly (though we do have a news > >machine with Adaptec 2940's), but we want to get an ultra-wide > >controller and our vendor is telling us he can't locate Mylex's > >BT958's. > > I saw your followup that you found my "configuration" file regarding the > above. I should point out that the configuration will be changing soon when > we move to RAID 5 for all of the disk space. The new config will be a Mylex > DAC960SXI hanging off of a two channel AHA-3940AUW (which is aic-7895 based). > The Mylex SCSI-SCSI RAID controller has six SCSI busses - two will be > configured as host busses with the other four going to the disk drives. > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 21 16:18:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09202 for freebsd-hardware-outgoing; Mon, 21 Sep 1998 16:18:58 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09039 for ; Mon, 21 Sep 1998 16:18:12 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id QAA18590; Mon, 21 Sep 1998 16:10:43 -0700 (PDT) Message-Id: <199809212310.QAA18590@implode.root.com> To: Andre Albsmeier cc: hardware@FreeBSD.ORG Subject: Re: SCSI card used at cdrom.com? In-reply-to: Your message of "Mon, 21 Sep 1998 20:50:57 +0200." <199809211850.UAA02011@internal> From: David Greenman Reply-To: dg@root.com Date: Mon, 21 Sep 1998 16:10:43 -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> >What SCSI controller is being used in the FreeBSD boxes at cdrom.com? >> >We like to mirror what y'all use because if it performs there, we >> >know it'll be great for us. >> > >> >We used to use Buslogic BT948's mostly (though we do have a news >> >machine with Adaptec 2940's), but we want to get an ultra-wide >> >controller and our vendor is telling us he can't locate Mylex's >> >BT958's. >> >> I saw your followup that you found my "configuration" file regarding the >> above. I should point out that the configuration will be changing soon when >> we move to RAID 5 for all of the disk space. The new config will be a Mylex >> DAC960SXI hanging off of a two channel AHA-3940AUW (which is aic-7895 based). > > >So you are going to use CAM with the new configuration, right ? > > -Andre I've been using CAM on wcarchive for nearly a year now. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 21 16:26:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11107 for freebsd-hardware-outgoing; Mon, 21 Sep 1998 16:26:44 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10981 for ; Mon, 21 Sep 1998 16:26:11 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id QAA18709; Mon, 21 Sep 1998 16:20:09 -0700 (PDT) Message-Id: <199809212320.QAA18709@implode.root.com> To: spork cc: Omar Thameen , hardware@FreeBSD.ORG Subject: Re: SCSI card used at cdrom.com? In-reply-to: Your message of "Mon, 21 Sep 1998 18:27:42 EDT." From: David Greenman Reply-To: dg@root.com Date: Mon, 21 Sep 1998 16:20:09 -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I'd like to throw my question out again, with a bit more of a general >slant to it: > >Does everyone find the adaptec 2940xxx to be reliable and stable? Yes, absolutely. >And to David, may I ask a bit about how you came to choose the Mylex raid >controller over the CMD? We have pretty much settled on the CMD after >many recommendations, but I'd like to hear some of your reasons for going >with the Mylex... I had, too, chosen the CMD until I found out that it only supports 32 tagged commands total. Maximally configured (45 drives), this means that not only would the CMD controller be unable to queue more than one command per disk, but in fact 1/3 of the disk drives would be completely idle at any given time. I was originally alerted that this may be a problem by looking at the product literature which indicated that 64 tagged commands was the limit. I called CMD and talked to a guy there about it and he told me that in more recent revs the tagged command limit had been further decreased to 32 commands due to a memory shortage on the controller. This problem forced me to look elsewhere, and the Mylex was what I found. The Mylex could be better in the transactions per second area (which I've benchmarked to be 1138/sec), but it's high enough for our purposes. I also looked at the Adaptec, but it doesn't support enough cache RAM - I considered 256MB a minimum, and I believe the Adaptec supported only 32MB. I think the Adaptec had only 3 SCSI busses, and I was looking for a minimum of 5. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 21 21:41:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13156 for freebsd-hardware-outgoing; Mon, 21 Sep 1998 21:41:06 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from jane.lfn.org (www.lfn.org [209.16.92.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA13145 for ; Mon, 21 Sep 1998 21:40:54 -0700 (PDT) (envelope-from caj@lfn.org) Received: (qmail 14108 invoked by uid 100); 22 Sep 1998 04:40:23 -0000 Date: Mon, 21 Sep 1998 23:40:23 -0500 (CDT) From: Craig Johnston To: freebsd-hardware@FreeBSD.ORG Subject: Cheap NCR/Symbios SCSI cards Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Who sells cheap 815-based cards these days? (815 = 810 + BIOS) Where and how much? thanks, Craig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 21 21:50:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14836 for freebsd-hardware-outgoing; Mon, 21 Sep 1998 21:50:27 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from calvin.saturn-tech.com ([207.229.19.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14722 for ; Mon, 21 Sep 1998 21:50:12 -0700 (PDT) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by calvin.saturn-tech.com (8.8.8/8.8.8) with SMTP id WAA06767; Mon, 21 Sep 1998 22:48:43 -0600 (MDT) (envelope-from drussell@saturn-tech.com) Date: Mon, 21 Sep 1998 22:48:42 -0600 (MDT) From: Doug Russell To: Steve Friedrich cc: Mike Smith , "hardware@FreeBSD.ORG" , Joe Gleason , spork Subject: Re: SCSI card used at cdrom.com? In-Reply-To: <199809212046.QAA17455@laker.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 21 Sep 1998, Steve Friedrich wrote: > So it really affects us all, thanks to the overclockers. I'm an old > hardware guy and I do not condone overclocking. It's really only It isn't always overclocking. The Cryix 6x86-PR200 chip required a 75 Mhz bus which was one of the reasons that > 66 MHz bus speeds became "official" on some motherboards (even if they supported it before.) Generally, of course, you are right. On the other hand, overclocking CAN be stable. My main dialin/mail/ftp/www/router box is a AM486/133 running with a 50Mhz bus (instead of 33) at 150 Mhz. It has *never* crashed itself since I built the box nearly 2 years ago. It has been down 4 times total since I finished the initial configuration: ~90 days uptime ~155 days uptime ~75 days uptime ~140 days uptime 10:42PM up 44 days, 45 mins, 8 users, load averages: 2.21, 2.24, 2.11 USER TTY FROM LOGIN@ IDLE WHAT drussell v0 - 08Aug98 9days -csh (csh) drussell v1 - 23Aug98 7days -su -m (csh) joy d1 :PPP 10:31PM 10 /usr/sbin/run.pppd auth login +pap tcc d2 - 14Sep98 6days pppd thor9 d3 :PPP 8:29PM 2:12 /usr/sbin/run.pppd auth login +pap drussell p0 calvin.saturn-te Wed09PM 5days -csh (csh) stever p1 den 10:26PM - (pine) drussell p2 calvin 10:41PM - w I Love FreeBSD! > worthwhile to someone willing to sacrifice system stability for > performance. That pretty much restricts it to people playing games, or > experimenting. It's definitely not for production machines. Under normal circumstances, I would agree, even though I don't always follow that rule with my own production machines. :) Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Sep 22 11:20:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26302 for freebsd-hardware-outgoing; Tue, 22 Sep 1998 11:20:21 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from jane.lfn.org (nocitycouncil.com [209.16.92.7]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA26200 for ; Tue, 22 Sep 1998 11:20:04 -0700 (PDT) (envelope-from caj@lfn.org) Received: (qmail 20184 invoked by uid 100); 22 Sep 1998 18:19:28 -0000 Date: Tue, 22 Sep 1998 13:19:28 -0500 (CDT) From: Craig Johnston To: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: diamond fireport 20, ok? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can someone confirm this works well with FreeBSD? I've seen reports on the 40 but not the 20. Which symbios chip does the 20 use -- is it an 875 or an 860? Diamond doesn't supply this info in the specs on their website. (typical) -- Craig Johnston, caj@lfn.org abort(); /* live fast, die young and leave a good-looking core file */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Sep 22 22:46:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08976 for freebsd-hardware-outgoing; Tue, 22 Sep 1998 22:46:47 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08910 for ; Tue, 22 Sep 1998 22:46:27 -0700 (PDT) (envelope-from dan@math.berkeley.edu) Received: (from dan@localhost) by math.berkeley.edu (8.8.7/8.8.7) id WAA25594; Tue, 22 Sep 1998 22:46:22 -0700 (PDT) Date: Tue, 22 Sep 1998 22:46:22 -0700 (PDT) From: dan@math.berkeley.edu (Dan Strick) Message-Id: <199809230546.WAA25594@math.berkeley.edu> To: freebsd-hardware@FreeBSD.ORG Subject: The "Creative Technology Ensoniq AudioPCI" card. Cc: dan@math.berkeley.edu Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am attempting to configure an "Ensoniq AudioPCI" to run under FreeBSD 3.0-xxx-BETA. As usual, actual technical information about the card is virtually nonexistant. The vendor said it was a "sound blaster 16 PCI" and that name was the closest he could come to a sound card that had worked for me in the past. Unfortunately, this seems to be very different. Nothing I try seems to work. The only kernel driver I can get to concede the existence of the card is "awe0" and (I believe) this is only for controlling "advanced wave effects" when using the real sound device. Can someone identify this species of sound card and suggest a driver? Also, can someone suggest a sound card that does work with FreeBSD? I am looking for a stable procuct line. Creative seems to plow its product line under every six months and I am getting sick and tired of discovering that the old drivers just don't work anymore. Thanks, Dan Strick dan@math.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 23 00:12:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24874 for freebsd-hardware-outgoing; Wed, 23 Sep 1998 00:12:29 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from control.colossus.dyn.ml.org (206-18-113-135.la.inreach.net [206.18.113.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24836 for ; Wed, 23 Sep 1998 00:12:17 -0700 (PDT) (envelope-from dburr@colossus.dyn.ml.org) Received: (from dburr@localhost) by control.colossus.dyn.ml.org (8.8.8/8.8.8) id AAA00806; Wed, 23 Sep 1998 00:08:21 -0700 (PDT) (envelope-from dburr) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199809230546.WAA25594@math.berkeley.edu> Date: Wed, 23 Sep 1998 00:08:16 -0700 (PDT) Organization: Computer Help From: Donald Burr To: (Dan Strick) Subject: RE: The "Creative Technology Ensoniq AudioPCI" card. Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My secret spy satellite informs me that on 23-Sep-98, Dan Strick wrote: > I am attempting to configure an "Ensoniq AudioPCI" to run under > FreeBSD 3.0-xxx-BETA. As usual, actual technical information > [...] > Can someone identify this species of sound card and suggest > a driver? FreeBSD does *not* support any PCI sound cards. However, the Open Sound System (OSS) driver supports this card, plus many more; it also has many other advanced features, and in general, seems to work at least as well as, if not somewhat better than, the FreeBSD default drivers. It's only $20, with free updates and tech support through the year 2002 (!!). To find more about it or to get your copy now, go to http://www.4front-tech.com/ > Also, can someone suggest a sound card that does work with > FreeBSD? I am looking for a stable procuct line. Creative > seems to plow its product line under every six months and > I am getting sick and tired of discovering that the old > drivers just don't work anymore. See the readme file for the "new" sound driver (Luigi's driver), at /sys/i386/isa/snd/README (also see /sys/i386/isa/snd/CARDS). This driver works quite well, and supports a large variety of ISA based sound cards, some of which can be had cheaply in "clone" versions. You really shouldn't be using the "old" sound drivers (i.e. VoxWare) any more. --- Donald Burr *NEW EMAIL ADDRESS!* | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ#16997506 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 23 13:28:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08724 for freebsd-hardware-outgoing; Wed, 23 Sep 1998 13:28:47 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA08635; Wed, 23 Sep 1998 13:28:06 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id QAA29223; Wed, 23 Sep 1998 16:33:16 -0400 From: Bill Paul Message-Id: <199809232033.QAA29223@skynet.ctr.columbia.edu> Subject: Call for testers for RealTek 8139 driver To: mturpin@shadow.spel.com, hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Date: Wed, 23 Sep 1998 16:33:14 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a call for testers for yet another PCI fast ethernet device driver, this time for the RealTek 8129 and 8139 chips. Note: I only have an 8139 adapter so I can't tell for sure if the 8129 support really works. The only major difference is that the 8129 uses an external PHY and needs MDIO support whereas the 8139 has a transceiver built in and the registers can be read directly. The source code is available from the following location: http://www.freebsd.org/~wpaul/RealTek/3.0 source for FreeBSD 3.0 http://www.freebsd.org/~wpaul/RealTek/2.2 source for FreeBSD 2.2.x To add the driver to an existing system, do the following: - Copy if_rl.c and if_rlreg.h to /sys/pci - Edit /sys/conf/files and add a line that says: pci/if_rl.c optional rl device-driver - Edit your kernel config file (e.g. /sys/i386/conf/GENERIC) and add a line that says: device rl0 - Compile a new kernel and reboot. You should get something like the following: rl0: rev 0x10 int a irq 14 on pci2.10.0 rl0: Ethernet address: 00:40:c7:79:18:1c rl0: autoneg complete, link status good (full-duplex, 100Mbps) My test machine is a PII 400Mhz system; on this system I can easily get 11MB/s transfer rates at 100Mbps full-duplex. Since the driver has to perform buffer copies, performance may not be quite as good on slower systems. Also, the autonegotiation on this chip seems a little flaky: you may have to force the proper mode using ifconfig in order to set it correctly for your network. As usual, report problems or success reports to wpaul@skynet.ctr.columbia.edu. For those who are wondering, no, this driver will not make it into FreeBSD 3.0-RELEASE: 3.0 is in a feature freeze and we have enough new code to whack into shape before the ship date. Next on the hit parade: the Winbond W89C840F chip. -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 23 14:11:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15825 for freebsd-hardware-outgoing; Wed, 23 Sep 1998 14:11:09 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from magpie.ece.arizona.edu (magpie.ece.arizona.edu [150.135.4.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15815 for ; Wed, 23 Sep 1998 14:10:57 -0700 (PDT) (envelope-from john@magpie.ece.arizona.edu) Received: (from john@localhost) by magpie.ece.arizona.edu (8.8.8/8.8.8) id OAA02303; Wed, 23 Sep 1998 14:11:04 -0700 (MST) (envelope-from john) Date: Wed, 23 Sep 1998 14:11:04 -0700 (MST) Message-Id: <199809232111.OAA02303@magpie.ece.arizona.edu> From: John Galbraith MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-hardware@FreeBSD.ORG Subject: new GPIB driver revision available CC: john@ece1.ece.arizona.edu X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs Lucid Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a new version of my GPIB driver available. Thomas Gellekum has made it available at the following URL: http://www.freebsd.org/~tg I am using it for real experiments now, so it is much more stable than it once was. It is still a development version, however. Mostly I just need other people to try it out and report bugs, problems, and successes. If you are interested in following this more closely, let me know and I will put you on a small mail alias that I have going of people using this driver, or who at least have some interest in it. Thanks, John -- John Galbraith email: john@ece.arizona.edu University of Arizona, home phone: (520) 327-6074 Los Alamos National Laboratory work phone: (520) 626-6277 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 23 20:47:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA17572 for freebsd-hardware-outgoing; Wed, 23 Sep 1998 20:47:35 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from asteroid.svib.ru (asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA17517 for ; Wed, 23 Sep 1998 20:47:09 -0700 (PDT) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (root@shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.8.8/8.8.8) with ESMTP id HAA02041 for ; Thu, 24 Sep 1998 07:46:55 +0400 (MSD) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (tarkhil@minas-tirith.pol.ru [127.0.0.1]) by minas-tirith.pol.ru (8.8.8/8.8.7) with ESMTP id HAA05503 for ; Thu, 24 Sep 1998 07:47:12 +0400 (MSD) (envelope-from tarkhil@minas-tirith.pol.ru) Message-Id: <199809240347.HAA05503@minas-tirith.pol.ru> X-Mailer: exmh version 2.0.2 2/24/98 To: hardware@FreeBSD.ORG Reply-To: tarkhil@asteroid.svib.ru Subject: PPP over LPT and EPP mode X-URL: http://freebsd.svib.ru Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Date: Thu, 24 Sep 1998 07:47:10 +0400 From: Alex Povolotsky Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello! Does PPP over LPT utilize byte-oriented exchange with FIFO, possible with parralel port in EPP mode? Alex. -- Alexander B. Povolotsky [2:5020/145] [http://freebsd.svib.ru] [tarkhil@asteroid.svib.ru] [Urgent messages: 234-9696 ΑΒ.#35442 or tarkhil@pager.express.ru] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 23 20:48:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA17656 for freebsd-hardware-outgoing; Wed, 23 Sep 1998 20:48:08 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from asteroid.svib.ru (asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA17616; Wed, 23 Sep 1998 20:47:51 -0700 (PDT) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (root@shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.8.8/8.8.8) with ESMTP id HAA02045; Thu, 24 Sep 1998 07:47:45 +0400 (MSD) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (tarkhil@minas-tirith.pol.ru [127.0.0.1]) by minas-tirith.pol.ru (8.8.8/8.8.7) with ESMTP id HAA05535; Thu, 24 Sep 1998 07:48:10 +0400 (MSD) (envelope-from tarkhil@minas-tirith.pol.ru) Message-Id: <199809240348.HAA05535@minas-tirith.pol.ru> X-Mailer: exmh version 2.0.2 2/24/98 To: hardware@FreeBSD.ORG cc: multimedia@FreeBSD.ORG Reply-To: tarkhil@asteroid.svib.ru Subject: Creative Infra X-URL: http://freebsd.svib.ru Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Date: Thu, 24 Sep 1998 07:48:10 +0400 From: Alex Povolotsky Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello! Does anyoune work (have finished work) on support of remote control unit of Creative Infra CD-ROM drive? Alex. -- Alexander B. Povolotsky [2:5020/145] [http://freebsd.svib.ru] [tarkhil@asteroid.svib.ru] [Urgent messages: 234-9696 ΑΒ.#35442 or tarkhil@pager.express.ru] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 23 22:55:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04415 for freebsd-hardware-outgoing; Wed, 23 Sep 1998 22:55:25 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04404 for ; Wed, 23 Sep 1998 22:55:18 -0700 (PDT) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40380>; Thu, 24 Sep 1998 15:54:39 +1000 Date: Thu, 24 Sep 1998 15:55:01 +1000 From: Peter Jeremy Subject: Re: PPP over LPT and EPP mode To: tarkhil@asteroid.svib.ru Cc: freebsd-hardware@FreeBSD.ORG Message-Id: <98Sep24.155439est.40380@border.alcanet.com.au> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alex Povolotsky wrote: >Does PPP over LPT utilize byte-oriented exchange with FIFO, possible with >parralel port in EPP mode? Definitely no in -stable. It uses nybble mode transfers with a laplink-style cable. I'm not sure if anyone has implemented it in the ppbus device in -current (last time I brought up the subject in -hackers, no-one seemed to be working on it). The major problem with byte-wide transfers is that the port becomes half-duplex (it can't simultaneously read and write). This means that you need to add appropriate hand-shaking to resolve (or prevent) contention. This probably means a changing the driver to master- slave. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 23 23:32:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08611 for freebsd-hardware-outgoing; Wed, 23 Sep 1998 23:32:14 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from word.smith.net.au (castles184.castles.com [208.214.165.184]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08536 for ; Wed, 23 Sep 1998 23:32:01 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id XAA00398; Wed, 23 Sep 1998 23:37:06 -0700 (PDT) (envelope-from mike@word.smith.net.au) Message-Id: <199809240637.XAA00398@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: tarkhil@asteroid.svib.ru cc: hardware@FreeBSD.ORG Subject: Re: PPP over LPT and EPP mode In-reply-to: Your message of "Thu, 24 Sep 1998 07:47:10 +0400." <199809240347.HAA05503@minas-tirith.pol.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Wed, 23 Sep 1998 23:37:05 -0700 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id XAA08570 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hello! G'day. > Does PPP over LPT utilize byte-oriented exchange with FIFO, possible with > parralel port in EPP mode? No; this would make it incompatible with the PLIP 'standard'. You're welcome to implement it as an optional feature controlled by an interface flag, of course. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Sep 24 08:43:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18051 for freebsd-hardware-outgoing; Thu, 24 Sep 1998 08:43:23 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18046 for ; Thu, 24 Sep 1998 08:43:22 -0700 (PDT) (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id LAA01938 for freebsd-hardware@freebsd.org; Thu, 24 Sep 1998 11:43:18 -0400 (EDT) (envelope-from mark) Message-ID: <19980924114317.A1903@vmunix.com> Date: Thu, 24 Sep 1998 11:43:17 -0400 From: Mark Mayo To: freebsd-hardware@FreeBSD.ORG Subject: hd error messages.. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i X-Operating-System: FreeBSD 2.2.6-STABLE i386 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org These just showed up in messages: > sd0(ahc0:0:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa > Ordered Tag queued > sd0(ahc0:0:0): SCB 0x3 timedout while recovery in progress > Ordered Tag sent > sd0(ahc0:0:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa > sd0(ahc0:0:0): Queueing an Abort SCB > sd0(ahc0:0:0): Abort Message Sent > sd0(ahc0:0:0): SCB 0 - Abort Tag Completed. > sd0(ahc0:0:0): no longer in timeout > sd0(ahc0:0:0): SCB 0x2 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR = 0x8 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa > Ordered Tag queued > sd0(ahc0:0:0): SCB 0x3 timedout while recovery in progress > sd0(ahc0:0:0): SCB 0x1 timedout while recovery in progress > sd0(ahc0:0:0): SCB 0x2 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR = 0x8 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa > sd0(ahc0:0:0): Queueing an Abort SCB > sd0(ahc0:0:0): SCB 0x0 timedout while recovery in progress > sd0(ahc0:0:0): Abort Message Sent > sd0(ahc0:0:0): SCB 2 - Abort Tag Completed. > sd0(ahc0:0:0): no longer in timeout > Ordered Tag sent > sd0(ahc0:0:0): SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR = 0x4 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa > Ordered Tag queued > sd0(ahc0:0:0): SCB 0x1 timedout while recovery in progress > sd0(ahc0:0:0): SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR = 0x7 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa > sd0(ahc0:0:0): Queueing an Abort SCB > sd0(ahc0:0:0): SCB 0x2 timedout while recovery in progress > sd0(ahc0:0:0): SCB 0x0 timedout while recovery in progress > sd0(ahc0:0:0): Abort Message Sent > sd0(ahc0:0:0): SCB 3 - Abort Tag Completed. > sd0(ahc0:0:0): no longer in timeout > Ordered Tag sent Nothing looks fatal, no panic or anything. I was doing a large untar at the time I believe (didn't notice anything wrong, picked up on this just now) which was likely working the disk a bit. Disk is a 1.2GB Seagate - SEAGATE ST51080N 0943 - the cheap medalist scsi drives they produced a while ago (or was it "hawk"? I dunno..). 5400RPM, SCSI2. Adaptec 2940UW controller. Should I be concerned about this, or was it just a "normal" correctable error. The disk is about 2 years old I think, +/- 6 months. I'd hate to have to replace a disk on that thing now, especially with 3.0 so close (i.e. I'd rather do the downtime all at once - upgrade + new disk!) TIA for any advice as to the fate of my drive! -Mark -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark ------------------------------------------------------------------------ "The problem is how do you build tools that understand your programs at a deeper semantic level." - James Gosling To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Sep 24 11:49:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18468 for freebsd-hardware-outgoing; Thu, 24 Sep 1998 11:49:46 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18462; Thu, 24 Sep 1998 11:49:44 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with SMTP id NAA16408; Thu, 24 Sep 1998 13:49:19 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 24 Sep 1998 13:49:18 -0500 (CDT) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: Bill Paul cc: mturpin@shadow.spel.com, hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Call for testers for RealTek 8139 driver In-Reply-To: <199809232033.QAA29223@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 23 Sep 1998, Bill Paul wrote: > This is a call for testers for yet another PCI fast ethernet device > driver, this time for the RealTek 8129 and 8139 chips. Note: I only I'm saving this message because I think I know where I can get my hand on some RealTek based Fast Ethernet cards. I have no idea just which RealTek chip I saw on them (quick glance), but more than likely it is one of the above. I'll let you know if/when I get ahold of a card and test it. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) (http://www.freebsd.org) */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Sep 24 11:55:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19840 for freebsd-hardware-outgoing; Thu, 24 Sep 1998 11:55:11 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19790; Thu, 24 Sep 1998 11:54:55 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with SMTP id NAA16433; Thu, 24 Sep 1998 13:54:48 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 24 Sep 1998 13:54:47 -0500 (CDT) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: Craig Johnston cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: diamond fireport 20, ok? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 22 Sep 1998, Craig Johnston wrote: > Can someone confirm this works well with FreeBSD? I've seen reports > on the 40 but not the 20. Which symbios chip does the 20 use -- is it > an 875 or an 860? Diamond doesn't supply this info in the specs on their > website. (typical) Should be the 810. If so, it will work fine. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) (http://www.freebsd.org) */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Sep 24 13:52:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11894 for freebsd-hardware-outgoing; Thu, 24 Sep 1998 13:52:09 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from jane.lfn.org (ops.lfn.org [209.16.92.6]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA11799 for ; Thu, 24 Sep 1998 13:51:54 -0700 (PDT) (envelope-from caj@lfn.org) Received: (qmail 950 invoked by uid 100); 24 Sep 1998 20:51:35 -0000 Date: Thu, 24 Sep 1998 15:51:35 -0500 (CDT) From: Craig Johnston To: Chris Dillon cc: freebsd-hardware@FreeBSD.ORG Subject: Re: diamond fireport 20, ok? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 24 Sep 1998, Chris Dillon wrote: > On Tue, 22 Sep 1998, Craig Johnston wrote: > > > Can someone confirm this works well with FreeBSD? I've seen reports > > on the 40 but not the 20. Which symbios chip does the 20 use -- is it > > an 875 or an 860? Diamond doesn't supply this info in the specs on their > > website. (typical) > > Should be the 810. If so, it will work fine. Actually the Fireport 20 is an ultra scsi card, if I am not mistaken. I was wondering if they were using the 860 (ultra narrow) or a crippled 875, or something else. At this point it is academic for me -- I decided I didn't trust diamond enough not to do something funny with the card, and ordered a Tekram 390U. (I wanted an external 50-pin connecter rather than a 68, hence the U over the W. I don't care much about wide anyway -- just seems like a good way to pay more for cables ;) ) 5'oclock computers (www.5oclock.com) has the U for $82, BTW. Can't comment on them as a vendor as I have not yet received my card. The F is a couple of bucks more. Thanks to all who replied. -- Craig Johnston, caj@lfn.org abort(); /* live fast, die young and leave a good-looking core file */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Sep 24 21:45:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25461 for freebsd-hardware-outgoing; Thu, 24 Sep 1998 21:45:18 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from iconmail.bellatlantic.net (iconmail.bellatlantic.net [199.173.162.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25456; Thu, 24 Sep 1998 21:45:14 -0700 (PDT) (envelope-from dmm125@bellatlantic.net) Received: from myname.my.domain (client201-122-77.bellatlantic.net [151.201.122.77]) by iconmail.bellatlantic.net (IConNet Sendmail) with SMTP id AAA16379; Fri, 25 Sep 1998 00:44:18 -0400 (EDT) Newsgroups: comp.unix.bsd.freebsd.misc Date: Fri, 25 Sep 1998 00:44:13 +0000 (GMT) From: Donn Miller X-Sender: dmm125@myname.my.domain To: questions@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: reading Sun-formatted diskettes Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to find out how to read floppies formatted in Sun filesystem format... supposedly, they're in UFS format, which FreeBSD uses. Maybe there's an option to `mount' to read older 4.3BSD filesystems? I couldn't find anything in the manpages about this. I know you can use the option to `newfs' to create 4.3BSD formats. I was trying to copy the Solaris install CD onto the first slice of HD #2, because Solaris panics while trying to boot the kernel off the CD for the first time. I just want to test to make sure it's not my CDROM Solaris is choking on. The tech-support guy at Sun Microsystems said that maybe my CDROM wasn't 100% ATAPI/IDE compliant. Now I'm wondering why Solaris is so picky that it has to have a CDROM that is 100% IDE compliant, even though FreeBSD/Linux/Win98 can use the CDROM perfectly well. It's a BTC 24X max CDROM. BTW, is there a diff between "24X max" and "24X" CDROMS? I went to BTC's website at http://www.btc.com.tw/ and it said my particular model is ATAPI/IDE and completely MPC level 3 compliant. BTW, what does MPC level 3 compliant mean? Does it mean that it's 100% ATAPI compliant? When FreeBSD boots up, it sort of "hangs" for about 25 seconds while probing the CDROM, but it still works great. Is this an indication that it's not 100% IDE complian? I think the bottom line is that Sun places a higher prio on supporting SPARC hardware than on supporting x86, and that's why it's so damn picky about HW. Sorry I spent so much time talking about Sun here, but I just want to be sure my computer's got compatible HW to run on many different OS's. Tbanks Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Sep 24 23:10:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04126 for freebsd-hardware-outgoing; Thu, 24 Sep 1998 23:10:23 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from word.smith.net.au (castles360.castles.com [208.214.167.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04081; Thu, 24 Sep 1998 23:10:19 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id XAA00472; Thu, 24 Sep 1998 23:14:28 -0700 (PDT) (envelope-from mike@word.smith.net.au) Message-Id: <199809250614.XAA00472@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Donn Miller cc: questions@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: reading Sun-formatted diskettes In-reply-to: Your message of "Fri, 25 Sep 1998 00:44:13 -0000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Sep 1998 23:14:27 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm trying to find out how to read floppies formatted in Sun filesystem > format... supposedly, they're in UFS format, which FreeBSD uses. Maybe > there's an option to `mount' to read older 4.3BSD filesystems? I couldn't > find anything in the manpages about this. I know you can use the option > to `newfs' to create 4.3BSD formats. Solaris uses a different word ordering; you can't mount Solaris filesystems under FreeBSD. > I was trying to copy the Solaris install CD onto the first slice of HD #2, > because Solaris panics while trying to boot the kernel off the CD for the > first time. I just want to test to make sure it's not my CDROM Solaris is > choking on. This is a FreeBSD support list; we can't help you with Solaris issues other than to point out that we dont suffer from them. > The tech-support guy at Sun Microsystems said that maybe my CDROM wasn't > 100% ATAPI/IDE compliant. Now I'm wondering why Solaris is so picky that > it has to have a CDROM that is 100% IDE compliant, even though > FreeBSD/Linux/Win98 can use the CDROM perfectly well. It's a BTC 24X max > CDROM. It's a convenient excuse for not fixing their driver. > BTW, is there a diff between "24X max" and "24X" CDROMS? I went to BTC's > website at http://www.btc.com.tw/ and it said my particular model is > ATAPI/IDE and completely MPC level 3 compliant. It means they have different ad copy writers. > BTW, what does MPC level 3 compliant mean? Does it mean that it's 100% > ATAPI compliant? When FreeBSD boots up, it sort of "hangs" for about 25 > seconds while probing the CDROM, but it still works great. Is this an > indication that it's not 100% IDE complian? No, this is just FreeBSD being very generous waiting for possibly extremely bogus IDE disks which can take up to that long to indicate their presence. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Sep 24 23:34:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06477 for freebsd-hardware-outgoing; Thu, 24 Sep 1998 23:34:32 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from iconmail.bellatlantic.net (iconmail.bellatlantic.net [199.173.162.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06466; Thu, 24 Sep 1998 23:34:28 -0700 (PDT) (envelope-from dmm125@bellatlantic.net) Received: from myname.my.domain (client201-122-14.bellatlantic.net [151.201.122.14]) by iconmail.bellatlantic.net (IConNet Sendmail) with SMTP id CAA21255; Fri, 25 Sep 1998 02:32:39 -0400 (EDT) Date: Fri, 25 Sep 1998 02:32:36 +0000 (GMT) From: Donn Miller X-Sender: dmm125@myname.my.domain To: Mike Smith cc: questions@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: reading Sun-formatted diskettes In-Reply-To: <199809250614.XAA00472@word.smith.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 24 Sep 1998, Mike Smith wrote: > > The tech-support guy at Sun Microsystems said that maybe my CDROM wasn't > > 100% ATAPI/IDE compliant. Now I'm wondering why Solaris is so picky that > > it has to have a CDROM that is 100% IDE compliant, even though > > FreeBSD/Linux/Win98 can use the CDROM perfectly well. It's a BTC 24X max > > CDROM. > > It's a convenient excuse for not fixing their driver. I figured as much... here I am thinking my hardware is inadaquate. That guy was trying to tell me to replace my CDROM drive. I just told him it works fine on FreeBSD and Linux... He said he was suspicious of that "$19.95 special" I was using for a CDROM drive. ( I don't know how much it cost really, but I know Soren used the same brand to test his CDRW driver so I figured it couldn't be that bad). I thought OH, a drive doesn't work with Sun software so that automatically makes it a cheap piece of crap. Sounds like their cdrom drivers need fixing. Thanks Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Sep 24 23:43:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07938 for freebsd-hardware-outgoing; Thu, 24 Sep 1998 23:43:37 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from word.smith.net.au (castles360.castles.com [208.214.167.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07915; Thu, 24 Sep 1998 23:43:28 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id XAA00720; Thu, 24 Sep 1998 23:47:24 -0700 (PDT) (envelope-from mike@word.smith.net.au) Message-Id: <199809250647.XAA00720@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Donn Miller cc: Mike Smith , questions@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: reading Sun-formatted diskettes In-reply-to: Your message of "Fri, 25 Sep 1998 02:32:36 -0000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Sep 1998 23:47:23 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > On Thu, 24 Sep 1998, Mike Smith wrote: > > > > The tech-support guy at Sun Microsystems said that maybe my CDROM wasn't > > > 100% ATAPI/IDE compliant. Now I'm wondering why Solaris is so picky that > > > it has to have a CDROM that is 100% IDE compliant, even though > > > FreeBSD/Linux/Win98 can use the CDROM perfectly well. It's a BTC 24X max > > > CDROM. > > > > It's a convenient excuse for not fixing their driver. > > I figured as much... here I am thinking my hardware is inadaquate. That > guy was trying to tell me to replace my CDROM drive. I just told him it > works fine on FreeBSD and Linux... He said he was suspicious of that > "$19.95 special" I was using for a CDROM drive. ( I don't know how much > it cost really, but I know Soren used the same brand to test his CDRW > driver so I figured it couldn't be that bad). They're a fairly typical Taiwanese unit. We actually bought the BTC CD-R for Soren because we were expecting it to represent something at the worse end of the spectrum, so that he'd have a better chance of covering some of the to-be-expected defects. As it turns out, it behaves better than the HP drive we also sent. > I thought OH, a drive doesn't work with Sun software so that automatically > makes it a cheap piece of crap. Sounds like their cdrom drivers need > fixing. To be fair, ATAPI is a disgusting hack and developing ATAPI drivers not an easy task. Sun aren't in the same position we are where we can honestly admit our faults without suffering terrible loss of face - they have to find some way to transfer the blame or be diminished. Under these circumstances, you can understand, if not forgive, their attitude. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Sep 24 23:57:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10379 for freebsd-hardware-outgoing; Thu, 24 Sep 1998 23:57:14 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from iconmail.bellatlantic.net (iconmail.bellatlantic.net [199.173.162.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10374; Thu, 24 Sep 1998 23:57:12 -0700 (PDT) (envelope-from dmm125@bellatlantic.net) Received: from myname.my.domain (client201-122-14.bellatlantic.net [151.201.122.14]) by iconmail.bellatlantic.net (IConNet Sendmail) with SMTP id CAA21948; Fri, 25 Sep 1998 02:56:01 -0400 (EDT) Date: Fri, 25 Sep 1998 02:56:01 +0000 (GMT) From: Donn Miller X-Sender: dmm125@myname.my.domain To: Mike Smith cc: questions@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: reading Sun-formatted diskettes In-Reply-To: <199809250647.XAA00720@word.smith.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 24 Sep 1998, Mike Smith wrote: > To be fair, ATAPI is a disgusting hack and developing ATAPI drivers not > an easy task. Sun aren't in the same position we are where we can > honestly admit our faults without suffering terrible loss of face - > they have to find some way to transfer the blame or be diminished. > > Under these circumstances, you can understand, if not forgive, their > attitude. I gather that you basically have to `cover all the bases' when writing the ATAPI drivers. Technically, there's probably a wide range of differing hardware that can be considered ATAPI compliant. It sounds like somewhat of a vague standard. The bigger companies like Sun, as you pointed out, can't conveniently admit their mistakes like the free software world without suffering the consequences... They'll probably come up with a fix in the future -- they're more than likely just buying time until they can fix it. It probably has one minor glitch that throws some drivers out of whack, which is understandable given the nature of the ATAPI standard. Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Sep 25 01:07:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA21936 for freebsd-hardware-outgoing; Fri, 25 Sep 1998 01:07:06 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.6.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA21920 for ; Fri, 25 Sep 1998 01:07:03 -0700 (PDT) (envelope-from schofiel@xs4all.nl) Received: from xs2.xs4all.nl (root@xs2.xs4all.nl [194.109.6.43]) by smtp1.xs4all.nl (8.8.8/8.8.8) with ESMTP id KAA24840 for ; Fri, 25 Sep 1998 10:06:58 +0200 (CEST) Received: from excelsior (enterprise.xs4all.nl [194.109.14.215]) by xs2.xs4all.nl (8.8.8/8.8.6) with SMTP id KAA06053 for ; Fri, 25 Sep 1998 10:06:57 +0200 (MET DST) Message-ID: <360B4F1D.6DAB@xs4all.nl> Date: Fri, 25 Sep 1998 10:06:53 +0200 From: Rob Schofield Reply-To: schofiel@xs4all.nl Organization: Knights of the Round Table Ltd. X-Mailer: Mozilla 3.04Gold (WinNT; I) MIME-Version: 1.0 To: Free BSD Hardware list Subject: Re: reading Sun-formatted diskettes References: <199809250614.XAA00472@word.smith.net.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith wrote: > > find anything in the manpages about this. I know you can use the option > > to `newfs' to create 4.3BSD formats. > > Solaris uses a different word ordering; you can't mount Solaris > filesystems under FreeBSD. Duh - so how come I can read OS-9 formatted floppies on FBSD? I would have thought byte ordering on the disk to be of little relevance so long as the correct device driver with an understanding of the layout of the disk is loaded...? Anyway, SPARC Solaris (which I guess you mean, Mike) wouldn't run on an Intel arch processor! It's obvious he's trying a dual boot setup on one machine, so it must be Solaris x86 => no byte ordering problem, merely a format problem. Did you get out of the wrong side of the bed this morning, Mike ;^) Rob -- The Ninety-Ninety Rule of Project Scheduling: The first ninety percent of the job takes ninety percent of the allotted time, the last ten percent takes the other ninety percent. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Sep 25 02:03:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA00652 for freebsd-hardware-outgoing; Fri, 25 Sep 1998 02:03:54 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from word.smith.net.au (castles360.castles.com [208.214.167.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA00637 for ; Fri, 25 Sep 1998 02:03:44 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id CAA01810; Fri, 25 Sep 1998 02:09:13 -0700 (PDT) (envelope-from mike@word.smith.net.au) Message-Id: <199809250909.CAA01810@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: schofiel@xs4all.nl cc: Free BSD Hardware list Subject: Re: reading Sun-formatted diskettes In-reply-to: Your message of "Fri, 25 Sep 1998 10:06:53 +0200." <360B4F1D.6DAB@xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 25 Sep 1998 02:09:12 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Mike Smith wrote: > > > > find anything in the manpages about this. I know you can use the option > > > to `newfs' to create 4.3BSD formats. > > > > Solaris uses a different word ordering; you can't mount Solaris > > filesystems under FreeBSD. > > Duh - so how come I can read OS-9 formatted floppies on FBSD? I would > have thought byte ordering on the disk to be of little relevance so long > as the correct device driver with an understanding of the layout of the > disk is loaded...? You totally fail to understand. Device drivers don't have anything to do with byte ordering. You will note that I specifically said "filesystems". > Anyway, SPARC Solaris (which I guess you mean, Mike) wouldn't run on an > Intel arch processor! It's obvious he's trying a dual boot setup on one > machine, so it must be Solaris x86 => no byte ordering problem, merely a > format problem. Solaris x86 uses the Sparc word ordering in on-disk filesystem data structures so that you can exchange disk media with Sparc systems. In addition to this, the Solaris "UFS" fileystem is not entirely compatible with the FreeBSD filesystem of the same name. See NetBSD/ Sparc, which can read SunOS/Solaris filesystems. Thus, you cannot mount a Solaris/X86 filesystem because: - The values in the on-disk data structures are formatted in a non-native fashion, and FreeBSD does not support this. - The on-disk data structures are not what the FreeBSD UFS/FFS is expecting. > Did you get out of the wrong side of the bed this morning, Mike ;^) I haven't gotten *into* bed this morning. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message