From owner-freebsd-hardware Sun May 3 16:58:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27178 for freebsd-hardware-outgoing; Sun, 3 May 1998 16:58:16 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from always.got.net (root@gotnet.znet.net [207.167.86.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27077; Sun, 3 May 1998 16:58:01 -0700 (PDT) (envelope-from dksprite@got.net) Received: from spriteboi (dksprite@SantaCruz-x2-3-94.got.net [209.66.100.94]) by always.got.net (8.8.8/8.8.7/Debian/GNU) with SMTP id QAA32285; Sun, 3 May 1998 16:57:47 -0700 Message-ID: <354D0537.526F@got.net> Date: Sun, 03 May 1998 17:00:55 -0700 From: kris zentner Reply-To: dksprite@got.net X-Mailer: Mozilla 3.04 (Win95; I) MIME-Version: 1.0 To: freebsd-questions@FreeBSD.ORG CC: hardware@FreeBSD.ORG Subject: 2.2.6 sysinstall probe problems with ST31621A Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org After weeks of effort trying to get FreeBSD 2.2.6 sysinstall to probe my Seagate (aka conner) drive I've found that there seems to be a problem with the sysinstall probing the drive (model number CFS1621A or ST31621A). The the system is as follows: Pentium 166 w/ 32mb ram, awe64 soundcard, hercules stingray 128, Adaptec AHA-1520 scsi controller (running a zip drive) 4.1gig Fujitsu MPA3043AT on primary master 1.6gig Seagate (formerly Conner) ST3121A on primary slave Sony CDU55E 2x CD-ROM on secondary master What seems to happen is that the sysinstall probe will seem to probe the disk(s) during the "probing devices, please wait..." screen and then after about 5 mins either hang (if that drive is connected) or continue. The 2.2.5 sysinstall has no problem and seems to spend less than a second on a the "probing devices, please wait..." screen finding any drive I attach. I've tried putting the drive in master, slave, and alone. Any configuration I've thought of and tried have had the same result. Win95/DOS seems to run fine on the drive. I'm wondering if there's any fix or solution for this and if the problem has been mentioned before. Please respond to kzentner@got.net. Thanks! -Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon May 4 10:08:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07272 for freebsd-hardware-outgoing; Mon, 4 May 1998 10:08:49 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from send1c.yahoomail.com (send1c.yahoomail.com [205.180.60.38]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA07244 for ; Mon, 4 May 1998 10:08:39 -0700 (PDT) (envelope-from rgireyev@yahoo.com) Message-ID: <19980504170957.25955.rocketmail@send1c.yahoomail.com> Received: from [208.141.52.226] by send1c; Mon, 04 May 1998 10:09:57 PDT Date: Mon, 4 May 1998 10:09:57 -0700 (PDT) From: Rudy Gireyev Subject: Re: [Target Mode] Was: Ooops - sorry To: Peter Dufault , Matthew Jacob Cc: hardware@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I thought Huyndai bought Symbios Logic. Peter Dufault wrote: > > > > as long as they are selling chips to Qlogic, > > > > Wrong. Qlogic is still it's own company. > > You misread me - I believe the "NCR" / Symbios chip company (NCR > sold their SCSI chips to Symbios two or so years ago) was just > bought by Adaptec. I mean as long as that group is selling chips > to small indepedendent companies such as Qlogic, Acculogic, Asus, > etc it should be possible to buy appropriate boards. > > I personally don't like Adaptec monopolizing the SCSI chip business. > > Peter > > -- > Peter Dufault (dufault@hda.com) Realtime development, Machine control, > HD Associates, Inc. Safety critical systems, Agency approval > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon May 4 13:41:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20035 for freebsd-hardware-outgoing; Mon, 4 May 1998 13:41:16 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from gw1.asacomputers.com (root@gw1.asacomputers.com [204.69.220.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20008 for ; Mon, 4 May 1998 13:41:02 -0700 (PDT) (envelope-from kedar@asacomputers.com) Received: by gw1.asacomputers.com id NAA21492; Mon, 4 May 1998 13:41:54 -0700 (PDT) Message-Id: <2.2.32.19980504203800.01385c30@gw1> X-Sender: rajadnya@gw1 X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 04 May 1998 13:38:00 -0700 To: Rudy Gireyev From: Kedar Rajadnya Subject: Re: [Target Mode] Was: Ooops - sorry Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org No, Adaptec is trying to. Kedar. At 10:09 AM 5/4/98 -0700, you wrote: >I thought Huyndai bought Symbios Logic. > > > >Peter Dufault wrote: >> >> > > as long as they are selling chips to Qlogic, >> > >> > Wrong. Qlogic is still it's own company. >> >> You misread me - I believe the "NCR" / Symbios chip company (NCR >> sold their SCSI chips to Symbios two or so years ago) was just >> bought by Adaptec. I mean as long as that group is selling chips >> to small indepedendent companies such as Qlogic, Acculogic, Asus, >> etc it should be possible to buy appropriate boards. >> >> I personally don't like Adaptec monopolizing the SCSI chip business. >> >> Peter >> >> -- >> Peter Dufault (dufault@hda.com) Realtime development, Machine >control, >> HD Associates, Inc. Safety critical systems, Agency >approval >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-hardware" in the body of the message >> > >_________________________________________________________ >DO YOU YAHOO!? >Get your free @yahoo.com address at http://mail.yahoo.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 Mon May 4 14:59:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08018 for freebsd-hardware-outgoing; Mon, 4 May 1998 14:59:50 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07878; Mon, 4 May 1998 14:59:13 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id OAA24132; Mon, 4 May 1998 14:58:54 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Mon, 4 May 1998 14:58:54 -0700 (PDT) From: Doug White Reply-To: Doug White To: kris zentner cc: freebsd-questions@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: 2.2.6 sysinstall probe problems with ST31621A In-Reply-To: <354D0537.526F@got.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 Sun, 3 May 1998, kris zentner wrote: > After weeks of effort trying to get FreeBSD 2.2.6 sysinstall to probe my > Seagate (aka conner) drive I've found that there seems to be a problem > with the sysinstall probing the drive (model number CFS1621A or > ST31621A). The the system is as follows: > > Pentium 166 w/ 32mb ram, awe64 soundcard, hercules stingray 128, Adaptec > AHA-1520 scsi controller (running a zip drive) > 4.1gig Fujitsu MPA3043AT on primary master > 1.6gig Seagate (formerly Conner) ST3121A on primary slave > Sony CDU55E 2x CD-ROM on secondary master > > What seems to happen is that the sysinstall probe will seem to probe the > disk(s) during the "probing devices, please wait..." screen and then > after about 5 mins either hang (if that drive is connected) or continue. Well, start pulling disks until it works. I'd start with the Zip drive; sysinstall does NOT like them. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon May 4 16:07:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23845 for freebsd-hardware-outgoing; Mon, 4 May 1998 16:07:20 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from gw1.asacomputers.com (root@gw1.asacomputers.com [204.69.220.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23797 for ; Mon, 4 May 1998 16:06:55 -0700 (PDT) (envelope-from nasir@asacomputers.com) Received: by gw1.asacomputers.com id QAA23671; Mon, 4 May 1998 16:07:36 -0700 (PDT) Message-Id: <2.2.32.19980504230607.006ef85c@gw1> X-Sender: nasir@gw1 X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 04 May 1998 16:06:07 -0700 To: freebsd-hardware@FreeBSD.ORG From: Nasir Ahmed Subject: Question about sccs. Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Please send me a private mail, as I am not subscribed to the list, yet. I would like to know if FreeBSD supports sccs. Thanks, Nasir. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon May 4 22:29:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA27667 for freebsd-hardware-outgoing; Mon, 4 May 1998 22:29:51 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from feral.com (mjacob@[209.54.254.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA27661 for ; Mon, 4 May 1998 22:29:45 -0700 (PDT) (envelope-from mjacob@feral.com) Received: (from mjacob@localhost) by feral.com (8.8.6/8.8.6) id WAA14939; Mon, 4 May 1998 22:28:43 -0700 Date: Mon, 4 May 1998 22:28:43 -0700 From: Matthew Jacob Message-Id: <199805050528.WAA14939@feral.com> To: dufault@hda.com, mjacob@feral.com, rgireyev@yahoo.com Subject: Re: [Target Mode] Was: Ooops - sorry Cc: hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >From rgireyev@yahoo.com Mon May 4 10:08:49 1998 >I thought Huyndai bought Symbios Logic. And now threatened to be bought by Adaptec. >Peter Dufault wrote: >> >> > > as long as they are selling chips to Qlogic, >> > >> > Wrong. Qlogic is still it's own company. >> >> You misread me - I believe the "NCR" / Symbios chip company (NCR >> sold their SCSI chips to Symbios two or so years ago) was just >> bought by Adaptec. I mean as long as that group is selling chips >> to small indepedendent companies such as Qlogic, Acculogic, Asus, >> etc it should be possible to buy appropriate boards. >> >> I personally don't like Adaptec monopolizing the SCSI chip business. >> No, you misread me. Qlogic has a separate architecture and makes their own chips. Orthogonal to NCR/Symbios and Adaptec. I was just mentioning it as a possible viable Target mode platform as opposed to trying to deduce target mode for Adaptec (or, rather, doing the right microengine foo for the undocumented AIC sequencer), or doing the whole NCR/Symbios SCRIPTS foo (which, as best as I can tell, works fitfully and somewhat unpredictably in the at least 20 different OS and target device implementations I've seen it in). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue May 5 08:27:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03821 for freebsd-hardware-outgoing; Tue, 5 May 1998 08:27:47 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mail1.sirius.com (mail1.sirius.com [205.134.253.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03792 for ; Tue, 5 May 1998 08:27:43 -0700 (PDT) (envelope-from parag@mail.codegen.com) Received: from [192.168.100.101] (ppp-asok07--141.sirius.net [205.134.245.141]) by mail1.sirius.com (8.8.7/Sirius-8.8.7-97.08.12) with SMTP id IAA07559 for ; Tue, 5 May 1998 08:27:42 -0700 (PDT) Message-Id: <199805051527.IAA07559@mail1.sirius.com> Subject: Re: [Target Mode] [short aside on NCR chips] Date: Tue, 5 May 1998 08:29:36 -0700 x-sender: parag@mail.codegen.com x-mailer: Claris Emailer 2.0v3, January 22, 1998 X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm From: Parag Patel cc: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 5/4/98 10:28 PM, Matthew Jacob (mjacob@feral.com) said: >[...] >or doing the whole NCR/Symbios SCRIPTS foo (which, as best as I >can tell, works fitfully and somewhat unpredictably in the at >least 20 different OS and target device implementations I've >seen it in) Funny you mention this - here's something we discovered about the NCR chips when debugging what we though was a PCI problem on an evaluation system. We ended up getting a PCI bus analyzer to watch every PCI transaction to debug the unrelated problem. While debugging, we noticed some interesting PCI bus cycles that the CPU was not initiating - nor was it the target. Turns out that when the NCR chip is running its SCRIPT, and that SCRIPT needs to access a PCI register on the NCR chip, then it actually performes PCI bus transactions to read/write those registers. Yes, that's right, it actually negotiates for control of the PCI bus then talks to itself over it! (These were *not* transactions to access SCRIPTS memory. It was easy to figure out what was going on when we realized the extra PCI transactions were doing exactly what we told the SCRIPTS engine to do and the accesses were to the NCR register mapped space.) It looks as if someone took a raw SCSI PCI engine, a completely separate SCRIPTS PCI engine, and slammed the two designs together using the PCI bus as an intermediary. -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue May 5 10:02:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22202 for freebsd-hardware-outgoing; Tue, 5 May 1998 10:02:08 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from george.arc.nasa.gov (george.arc.nasa.gov [128.102.194.142]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21914 for ; Tue, 5 May 1998 10:01:29 -0700 (PDT) (envelope-from lamaster@george.arc.nasa.gov) Received: (from lamaster@localhost) by george.arc.nasa.gov (8.8.7/8.8.7) id KAA14163; Tue, 5 May 1998 10:01:27 -0700 (PDT) Date: Tue, 5 May 1998 10:01:27 -0700 (PDT) From: Hugh LaMaster To: Matthew Jacob cc: hardware@FreeBSD.ORG Subject: Re: [Target Mode] Was: Ooops - sorry In-Reply-To: <199805050528.WAA14939@feral.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 On Mon, 4 May 1998, Matthew Jacob wrote: > No, you misread me. Qlogic has a separate architecture and makes > their own chips. Orthogonal to NCR/Symbios and Adaptec. I was > just mentioning it as a possible viable Target mode platform > as opposed to trying to deduce target mode for Adaptec (or, rather, > doing the right microengine foo for the undocumented AIC sequencer), > or doing the whole NCR/Symbios SCRIPTS foo (which, as best as I > can tell, works fitfully and somewhat unpredictably in the at > least 20 different OS and target device implementations I've > seen it in). NCR/Symbios may not be (have been?) perfect, but, performance is pretty good across the product line, and, at least the programming information was widely available, and, you could also buy driver-compatible controllers from multiple vendors, including inexpensive no-frills like the ASUS I own, to fancier, more heavily marketed Diamond controllers. With the acquisition of Symbios, is there *any* open chipset family available in multiple controller incarnations from different vendors? Does Qlogic sell its chips on the open market- and, if so, is anybody buying (what are the other sources?)? -- Hugh LaMaster, M/S 233-21, ASCII Email: hlamaster@mail.arc.nasa.gov NASA Ames Research Center Or: lamaster@george.arc.nasa.gov Moffett Field, CA 94035-1000 No Junkmail: USC 18 section 2701 Phone: 650/604-1056 Disclaimer: Unofficial, personal *opinion*. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue May 5 14:09:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10498 for freebsd-hardware-outgoing; Tue, 5 May 1998 14:09:57 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from persprog.com (root@persprog.com [204.215.255.203]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10424 for ; Tue, 5 May 1998 14:09:40 -0700 (PDT) (envelope-from dave@persprog.com) Received: by persprog.com (8.7.5/4.10) id QAA20363; Tue, 5 May 1998 16:00:43 -0500 Received: from dave.ppi.com(192.2.2.6) by cerberus.ppi.com via smap (V1.3) id sma020359; Tue May 5 17:00:37 1998 Message-ID: <354F7E09.58364F75@persprog.com> Date: Tue, 05 May 1998 17:00:57 -0400 From: "David W. Alderman" X-Mailer: Mozilla 4.04 [en] (WinNT; U) MIME-Version: 1.0 To: hardware@FreeBSD.ORG Subject: Re: [Target Mode] Was: Ooops - sorry References: X-Corel-MessageType: EMail Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hugh LaMaster wrote: > With the acquisition of Symbios, is there *any* open chipset > family available in multiple controller incarnations from > different vendors? Does Qlogic sell its chips on the open > market- and, if so, is anybody buying (what are the other > sources?)? > Who makes the chips on the Advansys controllers? They might be willing to publish their specs. They even make a controller that will boot in either a PC or a Mac!! I think it is still sold as the Iomega Jaz Jet PCI (after Iomega stopped shipping Adaptec PCI - possibly because someone figured out you could get the same controller from Iomega retail than you could from Adaptec anywhere). Dave Alderman "Where is Teddy Roosevelt when we need him?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue May 5 18:56:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02165 for freebsd-hardware-outgoing; Tue, 5 May 1998 18:56:38 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from antipodes.cdrom.com ([210.145.37.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02032; Tue, 5 May 1998 18:56:13 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA00535; Tue, 5 May 1998 14:57:15 -0700 (PDT) Message-Id: <199805052157.OAA00535@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Doug White cc: kris zentner , freebsd-questions@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: 2.2.6 sysinstall probe problems with ST31621A In-reply-to: Your message of "Mon, 04 May 1998 14:58:54 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 May 1998 14:57:13 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Sun, 3 May 1998, kris zentner wrote: > > > After weeks of effort trying to get FreeBSD 2.2.6 sysinstall to probe my > > Seagate (aka conner) drive I've found that there seems to be a problem > > with the sysinstall probing the drive (model number CFS1621A or > > ST31621A). The the system is as follows: Just to clarify, it's not Sysinstall probing the drive (as such). What happens is that sysinstall goes looking for stuff that the kernel has found. The only way it can do this is by trying to open everything that might exist and remembering which ones work. It's a pathetic "poor brother" to DEVFS. Is the drive itself locking up? Are you certain that the system is locked? Have you tried putting a disk in the Zip? It's possible that the Zip is just timing out very slowly. > > Pentium 166 w/ 32mb ram, awe64 soundcard, hercules stingray 128, Adaptec > > AHA-1520 scsi controller (running a zip drive) > > 4.1gig Fujitsu MPA3043AT on primary master > > 1.6gig Seagate (formerly Conner) ST3121A on primary slave > > Sony CDU55E 2x CD-ROM on secondary master > > > > What seems to happen is that the sysinstall probe will seem to probe the > > disk(s) during the "probing devices, please wait..." screen and then > > after about 5 mins either hang (if that drive is connected) or continue. > > Well, start pulling disks until it works. I'd start with the Zip drive; > sysinstall does NOT like them. Sysinstall doesn't care one way or the other. The ATAPI code in the FreeBSD kernel is a little grubby, and the ATAPI Zip shows up a few problems with it. SCSI Zip drives work just fine. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue May 5 18:59:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03090 for freebsd-hardware-outgoing; Tue, 5 May 1998 18:59:57 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from antipodes.cdrom.com ([210.145.37.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02939 for ; Tue, 5 May 1998 18:59:21 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA00275; Tue, 5 May 1998 17:55:51 -0700 (PDT) Message-Id: <199805060055.RAA00275@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "David W. Alderman" cc: hardware@FreeBSD.ORG Subject: Re: [Target Mode] Was: Ooops - sorry In-reply-to: Your message of "Tue, 05 May 1998 17:00:57 EDT." <354F7E09.58364F75@persprog.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 05 May 1998 17:55:50 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > With the acquisition of Symbios, is there *any* open chipset > > family available in multiple controller incarnations from > > different vendors? Does Qlogic sell its chips on the open > > market- and, if so, is anybody buying (what are the other > > sources?)? > > > > Who makes the chips on the Advansys controllers? They might be > willing to publish their specs. Advansys, surprisingly enough. They're willing to help serious developers, and their controllers are supported by the CAM code. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue May 5 20:57:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23881 for freebsd-hardware-outgoing; Tue, 5 May 1998 20:57:58 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23854 for ; Tue, 5 May 1998 20:57:44 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id UAA09861; Tue, 5 May 1998 20:57:22 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Tue, 5 May 1998 20:57:22 -0700 (PDT) From: Doug White Reply-To: Doug White To: Mike Smith cc: hardware@FreeBSD.ORG Subject: Re: 2.2.6 sysinstall probe problems with ST31621A In-Reply-To: <199805052157.OAA00535@antipodes.cdrom.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 limiting discussion to -hardware. > Just to clarify, it's not Sysinstall probing the drive (as such). What > happens is that sysinstall goes looking for stuff that the kernel has > found. The only way it can do this is by trying to open everything > that might exist and remembering which ones work. It's a pathetic > "poor brother" to DEVFS. indeed ... > Is the drive itself locking up? Are you certain that the system is > locked? Have you tried putting a disk in the Zip? It's possible that > the Zip is just timing out very slowly. > > Well, start pulling disks until it works. I'd start with the Zip drive; > > sysinstall does NOT like them. > > Sysinstall doesn't care one way or the other. The ATAPI code in the > FreeBSD kernel is a little grubby, and the ATAPI Zip shows up a few > problems with it. SCSI Zip drives work just fine. Well, then, I guess we know where to start. :-/ I know that the 'pull the Zip' advice has helped many people, so there is certainly a problem there. Why isn't wfd0 in the boot floppy kernel? Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed May 6 03:03:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27677 for freebsd-hardware-outgoing; Wed, 6 May 1998 03:03:04 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from maciek.gv.edu.pl (andrzej@netserv.gv.edu.pl [195.117.86.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27653 for ; Wed, 6 May 1998 03:02:56 -0700 (PDT) (envelope-from andrzej@maciek.gv.edu.pl) Received: from localhost (andrzej@localhost) by maciek.gv.edu.pl (8.8.5/8.8.2) with SMTP id MAA19868 for ; Wed, 6 May 1998 12:02:53 +0200 (CEST) Date: Wed, 6 May 1998 12:02:53 +0200 (CEST) From: Andrzej Szydlo To: freebsd-hardware@FreeBSD.ORG Subject: QIC-02 Archive 2150L Tape Drive 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 Hello, Are QIC-02 Tape Drives, Archive model 2150L in this case, supported? If so, is/was any one using them? Where to look for a driver? TIA Andrzej To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed May 6 10:50:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09168 for freebsd-hardware-outgoing; Wed, 6 May 1998 10:50:48 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from lugh.kerris.com (lugh.kerris.com [205.150.35.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA09128 for ; Wed, 6 May 1998 10:50:28 -0700 (PDT) (envelope-from mkerr@kerris.com) Received: from localhost (mkerr@localhost) by lugh.kerris.com (8.8.7/8.6.12) with SMTP id OAA12044 for ; Wed, 6 May 1998 14:08:38 -0400 (EDT) Date: Wed, 6 May 1998 14:08:37 -0400 (EDT) From: Mike Kerr To: freebsd-hardware@FreeBSD.ORG Subject: Stupid ATAPI Errors 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 keep getting these and have been getting them since 2.2.1. I am now running 2.2.6 and have gone through the intermediate revs as well: May 6 12:43:52 wraith /kernel: atapi1.0: invalid command phase, ireason=0xd0, status=d0, error=d0 It's driving me insane because it has the potential to hang the machine (console, anyway) 80% of the time. It typically happens when I use my CDROM to play music. I have two IDE ports on the motherboard, one connects to two 2G drives, the other connects to an NEC CDROM. Not sure the speed. Anybody seen this before? Mike. =-=-=-=-=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=-=-=-=-= Mike Kerr | Mailing Lists and other | Spiff Quote: mkerr@kerris.com | neat stuff... | http://www.kerris.com/ | majordomo@kerris.com | "Don Koharski sucks!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed May 6 18:51:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10172 for freebsd-hardware-outgoing; Wed, 6 May 1998 18:51:44 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09639 for ; Wed, 6 May 1998 18:49:57 -0700 (PDT) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id LAA27618; Thu, 7 May 1998 11:19:43 +0930 (CST) (envelope-from grog) Message-ID: <19980507111942.N396@freebie.lemis.com> Date: Thu, 7 May 1998 11:19:42 +0930 From: Greg Lehey To: Andrzej Szydlo , freebsd-hardware@FreeBSD.ORG Subject: Re: QIC-02 Archive 2150L Tape Drive References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Andrzej Szydlo on Wed, May 06, 1998 at 12:02:53PM +0200 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 6 May 1998 at 12:02:53 +0200, Andrzej Szydlo wrote: > Hello, > > Are QIC-02 Tape Drives, Archive model 2150L in this case, supported? Yes. > If so, is/was any one using them? Somebody else sent a question today with a problem with dump. Check your incoming -questions. I used to use one, but I can't recall whether it was with FreeBSD. > Where to look for a driver? As always, in /sys/i386/conf/LINT: # wt: Wangtek and Archive QIC-02/QIC-36 tape drives device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu May 7 06:01:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA09898 for freebsd-hardware-outgoing; Thu, 7 May 1998 06:01:41 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA09870 for ; Thu, 7 May 1998 06:01:19 -0700 (PDT) (envelope-from dateck@ludd.luth.se) Received: from father.ludd.luth.se (dateck@father.ludd.luth.se [130.240.16.18]) by zed.ludd.luth.se (8.8.5/8.8.5) with ESMTP id PAA24305; Thu, 7 May 1998 15:01:13 +0200 From: Tomas Klockar Received: (dateck@localhost) by father.ludd.luth.se (8.6.11/8.6.11) id PAA04436; Thu, 7 May 1998 15:01:11 +0200 Message-Id: <199805071301.PAA04436@father.ludd.luth.se> Subject: Re: Stupid ATAPI Errors To: mkerr@kerris.com (Mike Kerr) Date: Thu, 7 May 1998 15:01:10 +0200 (MET DST) Cc: freebsd-hardware@FreeBSD.ORG In-Reply-To: from Mike Kerr at "May 6, 98 02:08:37 pm" X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Mike Kerr: > > I keep getting these and have been getting them since 2.2.1. I am now > running 2.2.6 and have gone through the intermediate revs as well: > > May 6 12:43:52 wraith /kernel: atapi1.0: invalid command phase, > ireason=0xd0, status=d0, error=d0 > > It's driving me insane because it has the potential to hang the machine > (console, anyway) 80% of the time. > > It typically happens when I use my CDROM to play music. I have two IDE > ports on the motherboard, one connects to two 2G drives, the other > connects to an NEC CDROM. Not sure the speed. > > Anybody seen this before? > > Mike. > I see a simular problem and I am running 3.0-CURRENT I have my cdrom as slave on the second controler. I get 'wcd0: i/o error, status=51, error=30' When I play music. /Tomas -- Tomas Klockar can be found at the following adresses: Kårhusvägen 4:23 | Furuvägen 102 | dateck@ludd.luth.se 977 54 Luleå | 871 52 Härnösand | dateck@solace.mh.se Tel: +46-920-231335 | Tel: +46-611-13393 | d94-tkl@sm.luth.se Mob: +46-70-664 33 26 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu May 7 07:41:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22712 for freebsd-hardware-outgoing; Thu, 7 May 1998 07:41:12 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from skyserv.med.osd.mil (skyserv.med.osd.mil [199.209.8.144]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA22690 for ; Thu, 7 May 1998 07:40:54 -0700 (PDT) (envelope-from rpotts@med.osd.mil) Received: from 161.14.168.22 (ae1970.med.osd.mil [161.14.168.22]) by skyserv.med.osd.mil (8.6.8.1/SCA-6.6) with SMTP id KAA18435 for ; Thu, 7 May 1998 10:40:49 -0400 From: "Ross Potts, CON, EDS/D-SIDDOMS" Message-Id: <9805071038.ZM-81133@161.14.168.22> Date: Thu, 7 May 1998 10:38:26 -0700 X-Mailer: ZM-Win (3.2.1 11Sep94) To: freeBSD-hardware@FreeBSD.ORG Subject: Overclocking Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Boy, you do a simple thing like overclock a P133 to 187.93 MHZ and FreeBSD won't hardly boot up half the time! Where's the quality control!?!?!! I'm just joking folks! I just wanted to see how fast I could go. Nothing could be stable with a 41% gain. By the way I love all the little tools that are hidden, just waiting to be discovered(/usr/local/lib/lmbench/bin/bsd/mhz, for example)! I was impressed that FreeBSD would handle that at all! Winblows 95 wouldn't even boot. I was using regular EDO RAM, so maybe if I got the expensive stuff it would work out better. I went down to 166.99 mhz and so far everything seems to run fine. You guys are Da' Bomb! -- Potts, Ross A. Internet : Ross.Potts@med.osd.mil EDS-D/SIDDOMS Phone : (703) 824-7601 Skyline Two, Suite 1200 Beeper : (888) 687-2709 5113 Leesburg Pike, FAX : (703) 824-4155 Falls Church, VA 22041 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu May 7 11:48:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08382 for freebsd-hardware-outgoing; Thu, 7 May 1998 11:48:18 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from bogslab.ucdavis.edu (root@bogslab.ucdavis.edu [128.120.162.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08079 for ; Thu, 7 May 1998 11:47:46 -0700 (PDT) (envelope-from greg@bogslab.ucdavis.edu) Received: from myrtle1.bogs.org (root@myrtle1.bogs.org [198.137.203.39]) by bogslab.ucdavis.edu (8.7.4/8.7.3) with ESMTP id LAA09634 for ; Thu, 7 May 1998 11:47:43 -0700 (PDT) Received: from myrtle1.bogs.org (greg@localhost [127.0.0.1]) by myrtle1.bogs.org (8.6.12/8.6.12) with ESMTP id LAA11410 for ; Thu, 7 May 1998 11:45:59 -0700 Message-Id: <199805071845.LAA11410@myrtle1.bogs.org> To: hardware@FreeBSD.ORG Subject: Underclocking (Was: Overclocking) In-reply-to: Your message of "Thu, 07 May 1998 10:38:26 PDT." <9805071038.ZM-81133@161.14.168.22> Reply-To: gkshenaut@ucdavis.edu Date: Thu, 07 May 1998 11:45:37 -0700 From: Greg Shenaut Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm wondering if it might be possible to *underclock* a CPU chip in order to increase its reliability, especially under hot conditions. Has anyone tried this? I'm running out of 386-based motherboards to use as remote server/router boxes. -Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu May 7 13:01:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21079 for freebsd-hardware-outgoing; Thu, 7 May 1998 13:01:28 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dt050n33.san.rr.com (@dt053nd2.san.rr.com [204.210.34.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21024 for ; Thu, 7 May 1998 13:01:10 -0700 (PDT) (envelope-from Studded@san.rr.com) Received: from san.rr.com (Studded@localhost [127.0.0.1]) by dt050n33.san.rr.com (8.8.8/8.8.8) with ESMTP id NAA00478; Thu, 7 May 1998 13:01:01 -0700 (PDT) (envelope-from Studded@san.rr.com) Message-ID: <355212FC.39F4DB0D@san.rr.com> Date: Thu, 07 May 1998 13:01:00 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-STABLE-0507 i386) MIME-Version: 1.0 To: "Ross Potts, CON, EDS/D-SIDDOMS" CC: freeBSD-hardware@FreeBSD.ORG Subject: Re: Overclocking References: <9805071038.ZM-81133@161.14.168.22> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ross Potts, CON, EDS/D-SIDDOMS wrote: > > Boy, you do a simple thing like overclock a P133 to 187.93 MHZ and FreeBSD won't > hardly boot up half the time! Where's the quality control!?!?!! I know that you're just joking around, but did you try any of the clock calibration kernel options? I have a P150 overdrive chip that I (bus) overclock to 166 and the option to calibrate the cpu clock differently made a huge difference for me. Take a look in LINT, the specific options I use are: cpu "I586_CPU" options "CPU_FASTER_5X86_FPU" options "CLK_USE_I586_CALIBRATION" options "NO_F00F_HACK" Hope this helps you, Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud designer and maintainer of the world's largest Internet *** Relay Chat server with 5,328 simultaneous connections. *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu May 7 13:02:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21282 for freebsd-hardware-outgoing; Thu, 7 May 1998 13:02:14 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from george.lbl.gov (george-2.lbl.gov [131.243.2.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21013 for ; Thu, 7 May 1998 13:01:07 -0700 (PDT) (envelope-from jin@george.lbl.gov) Received: (from jin@localhost) by george.lbl.gov (8.8.8/LBL-ITG) id NAA02421; Thu, 7 May 1998 13:01:06 -0700 (PDT) Date: Thu, 7 May 1998 13:01:06 -0700 (PDT) From: Jin Guojun (ITG staff) Message-Id: <199805072001.NAA02421@george.lbl.gov> To: gkshenaut@ucdavis.edu, hardware@FreeBSD.ORG Subject: Re: Underclocking (Was: Overclocking) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm wondering if it might be possible to *underclock* > a CPU chip in order to increase its reliability, especially > under hot conditions. Has anyone tried this? ... Sure, reducing the CPU clock will lower the heat generated from CPU. Beware that not all CPUs can be overclocked/underclocked. Read the Intel CPU spec., some of the CPUs must run at specified clock rate. Typically those MMX CPUs. -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu May 7 13:03:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21465 for freebsd-hardware-outgoing; Thu, 7 May 1998 13:03:20 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21333 for ; Thu, 7 May 1998 13:02:32 -0700 (PDT) (envelope-from kpielorz@caladan.tdx.co.uk) Received: from localhost (kpielorz@localhost) by caladan.tdx.co.uk (8.8.8/8.8.8) with SMTP id VAA28500; Thu, 7 May 1998 21:02:27 +0100 (BST) (envelope-from kpielorz@caladan.tdx.co.uk) Date: Thu, 7 May 1998 21:02:27 +0100 (BST) From: Karl Pielorz To: Greg Shenaut cc: hardware@FreeBSD.ORG Subject: Re: Underclocking (Was: Overclocking) In-Reply-To: <199805071845.LAA11410@myrtle1.bogs.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You can underclock CPU's - and they do run cooler... I used to run a machine that was a 486DX4/100 with it's 'internal cache' disabled as I didn't have a heatsink... Just by disabling the internal cache the machine ran like a dog, but the chip would barely get warm... I guess the same would apply for underclocking - just be careful about busses that might derive their clock from the CPU's speed (especially on older machines). I guess it might make sense to some people - I always prefer to have 'more than adequate' cooling though... ;-) Regards, Karl Pielorz On Thu, 7 May 1998, Greg Shenaut wrote: > > I'm wondering if it might be possible to *underclock* > a CPU chip in order to increase its reliability, especially > under hot conditions. Has anyone tried this? I'm running > out of 386-based motherboards to use as remote server/router > boxes. > > -Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu May 7 14:17:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06810 for freebsd-hardware-outgoing; Thu, 7 May 1998 14:17:38 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from skyserv.med.osd.mil (skyserv.med.osd.mil [199.209.8.144]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA06755 for ; Thu, 7 May 1998 14:17:04 -0700 (PDT) (envelope-from rpotts@med.osd.mil) Received: from 161.14.168.22 (ae1970.med.osd.mil [161.14.168.22]) by skyserv.med.osd.mil (8.6.8.1/SCA-6.6) with SMTP id RAA15470; Thu, 7 May 1998 17:16:47 -0400 From: "Ross Potts, CON, EDS/D-SIDDOMS" Message-Id: <9805071714.ZM-81133@161.14.168.22> Date: Thu, 7 May 1998 17:14:27 -0700 In-Reply-To: Jin Guojun (ITG staff) "Re: Underclocking (Was: Overclocking)" (May 7, 1:01pm) References: <199805072001.NAA02421@george.lbl.gov> X-Mailer: ZM-Win (3.2.1 11Sep94) To: Jin Guojun (ITG staff) Subject: Re: Underclocking (Was: Overclocking) Cc: freeBSD-hardware@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Sure, reducing the CPU clock will lower the heat generated from CPU. >Beware that not all CPUs can be overclocked/underclocked. Read the Intel >CPU spec., some of the CPUs must run at specified clock rate. Typically >those MMX CPUs. Also take a look at the "lot codes"(I think that is the term) that are stamped on the CPU. If you see SY022 or SY033, chances are, you will only be able to overclock by one step. Right now, I am only dealing with Pentium classics and pros. Consult Tom's Hardware Guide(I don't have the URL today) on the web. It's well written. -- Potts, Ross A. Internet : Ross.Potts@med.osd.mil EDS-D/SIDDOMS Phone : (703) 824-7601 Skyline Two, Suite 1200 Beeper : (888) 687-2709 5113 Leesburg Pike, FAX : (703) 824-4155 Falls Church, VA 22041 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu May 7 14:29:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08948 for freebsd-hardware-outgoing; Thu, 7 May 1998 14:29:40 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from grayling.erg.sri.com (grayling.erg.sri.com [128.18.4.194]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA08883; Thu, 7 May 1998 14:29:11 -0700 (PDT) (envelope-from templin@erg.sri.com) Received: by grayling.erg.sri.com (SMI-8.6/2.7davy) id OAA11997; Thu, 7 May 1998 14:29:15 -0700 Message-Id: <199805072129.OAA11997@grayling.erg.sri.com> Date: Thu, 7 May 1998 14:29:15 -0700 From: "Fred L. Templin" To: hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Cc: mgorman@isi.edu, templin@erg.sri.com Subject: Missing Receive Data interrupts on a 16550 UART (sio driver)... Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, We're building a custom PC-CARD based on the Zilog Z80182 which "mimics" a 16550 UART at the host interface. We're using the sio.c driver via the SLIP line discipline to talk to the card, and we're able to both transmit and receive data bytes. Whenever the host writes a stream of data bytes to the 16550's Transmit Holding Register (and 16byte transmit FIFO) we get a "Transmit Holding Register Empty" interrupt after the Z182 has finished servicing the FIFO, which is as expected. But, we never get hardware interrupts when the Z182 writes the Receive Buffer Register and/or fills the receive FIFO beyond the trigger level. (I know the Z182 is writing data bytes, because when I enable the sio.c driver's timeout routine to do polling the received data is sitting there in the FIFO waiting for the host to grab it. Has anyone seen anything like this before? Any suggestions on debugging procedures? Thanks, Fred templin@erg.sri.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu May 7 17:28:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08475 for freebsd-hardware-outgoing; Thu, 7 May 1998 17:28:59 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from d183-205.uoregon.edu (d183-205.uoregon.edu [128.223.183.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08268 for ; Thu, 7 May 1998 17:27:33 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by d183-205.uoregon.edu (8.8.7/8.8.7) id RAA03267; Thu, 7 May 1998 17:27:29 -0700 (PDT) Message-ID: <19980507172729.47925@hydrogen.nike.efn.org> Date: Thu, 7 May 1998 17:27:29 -0700 From: John-Mark Gurney To: gkshenaut@ucdavis.edu Cc: hardware@FreeBSD.ORG Subject: Re: Underclocking (Was: Overclocking) References: <9805071038.ZM-81133@161.14.168.22> <199805071845.LAA11410@myrtle1.bogs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199805071845.LAA11410@myrtle1.bogs.org>; from Greg Shenaut on Thu, May 07, 1998 at 11:45:37AM -0700 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greg Shenaut scribbled this message on May 7: > I'm wondering if it might be possible to *underclock* > a CPU chip in order to increase its reliability, especially > under hot conditions. Has anyone tried this? I'm running > out of 386-based motherboards to use as remote server/router > boxes. also, becareful with overclocking a chip... I over clocked a 486/33dx to 40mhz for a LONG while... now the machine won't boot if you run it at 33mhz, you HAVE to run it at 40mhz... but it does work like a champ though... -- John-Mark Gurney Modem Rev/FAX: +1 541 346 9237 Cu Networking P.O. Box 5693, 97405 Live in Peace, destroy Micro$oft, support free software, run FreeBSD Don't trust anyone you don't have the source for To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri May 8 10:52:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02524 for freebsd-hardware-outgoing; Fri, 8 May 1998 10:52:44 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02472 for ; Fri, 8 May 1998 10:52:26 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id LAA15388; Fri, 8 May 1998 11:48:37 -0600 (MDT) Date: Fri, 8 May 1998 11:48:37 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199805081748.LAA15388@narnia.plutotech.com> To: Matthew Jacob cc: hardware@FreeBSD.ORG Subject: Re: [Target Mode] Was: Ooops - sorry Newsgroups: pluto.freebsd.hardware In-Reply-To: <199805050528.WAA14939@feral.com> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>> I personally don't like Adaptec monopolizing the SCSI chip business. > > No, you misread me. Qlogic has a separate architecture and makes > their own chips. Orthogonal to NCR/Symbios and Adaptec. I was > just mentioning it as a possible viable Target mode platform > as opposed to trying to deduce target mode for Adaptec (or, rather, > doing the right microengine foo for the undocumented AIC sequencer), This is one of the large misconceptions about the Adaptec parts. The parts are documented and anyone on this list can call the technical documents department and have Adaptec send you the manuals. What differentiates Adaptec and Symbios from vendors like Qlogic is that they do not release their firmware in an easy to use binary module nor do they release the exact interface to their firmware. All the information you need to write your own firmware is provided. I should say that they don't release firmware *yet*, as one of Adaptec's technical marketting people is working to make the Adaptec HIM (Hardware Interface Module) available for a "free" driver. Even if this does happen, they will never release source to their firmware which, for vendors like Pluto, would make a HIM based driver much less attractive than the current one. Most of the bugs I fix or features I add to the aic7xxx driver have a 1 day turn around time. We could never get this kind of response from the vendor. There are also features that we plan to implement that would never interest Adaptec (being able to release target DMA memory mid transfer by using the "bit bucket" feature of the chip so our cache can be reused more quickly, for instance) that require firmware level tweaking. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri May 8 10:54:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02881 for freebsd-hardware-outgoing; Fri, 8 May 1998 10:54:32 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from feral.com (root@[209.54.254.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02852 for ; Fri, 8 May 1998 10:54:23 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral-gw (mjacob@gw100.feral.com [192.67.166.129]) by feral.com (8.8.6/8.8.6) with SMTP id KAA28618; Fri, 8 May 1998 10:54:19 -0700 Message-ID: <355346CB.4C6B67B4@feral.com> Date: Fri, 08 May 1998 10:54:19 -0700 From: Matthew Jacob Organization: Feral Software X-Mailer: Mozilla 3.04 (X11; I; Linux 2.0.33 i586) MIME-Version: 1.0 To: "Justin T. Gibbs" CC: hardware@FreeBSD.ORG Subject: Re: [Target Mode] Was: Ooops - sorry References: <199805081748.LAA15388@narnia.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin- thanks for the clarification about Adaptec. I'll keep that in mind and won't bash them for this. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat May 9 02:34:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA20219 for freebsd-hardware-outgoing; Sat, 9 May 1998 02:34:02 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from itw.itworks.com.au (root@itw.itworks.com.au [203.32.61.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA20194 for ; Sat, 9 May 1998 02:33:52 -0700 (PDT) (envelope-from gavin@itworks.com.au) Received: from localhost (gavin@localhost) by itw.itworks.com.au (8.8.8/8.8.5) with SMTP id TAA20068 for ; Sat, 9 May 1998 19:30:50 +1000 (EST) Date: Sat, 9 May 1998 19:30:49 +1000 (EST) From: Gavin Cameron To: freebsd-hardware@FreeBSD.ORG Subject: Serial port problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I've just acquired 2 servers to run 2.2.6-RELEASE on. They are both using Iwill P55XUB motherboards. The book that came with the motherboard says that the onboard serial ports are NS16C550 compatible. The first serial port is setup as 3F8 and IRQ 4, and the second port is at 2F8 and IRQ3. Both machines will eventually have a serial console on them. If I boot the machine up using the video card as the console the kernel cannot find the serial ports. If I boot up using a serial console I get the boot messages coming through loud and clear (so the serial port was probed and is working), but the kernel panic as soon as is probes for the serial ports. The last message before the cu session closed is Probing for devices ocu: Got hangup signal which is the probing of the ISA bus message. If I cu again and enter cont into ddb I get Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01c37ee stack pointer = 0x10:0xefbfff80 frame pointer = 0x10:0xefbfff80 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 () interrupt mask = kernel: type 12 trap, code=0 Stopped at _cninit_finish+0x26: movl 0x4(%edx),%eax I've got the serial connection open and waiting in the debugger. If someone has an idea of where I should be looking to solve the problem, please email me. Thanks Gavin []------------------------------------+-------------------------------------[] | Gavin Cameron | ITworks Consulting | | Ph : 0418 390350 | Suite 100, 85 Grattan Street | | Fax : +61 3 9347 6544 | Carlton, Victoria | | Email : gavin@itworks.com.au | Australia, 3053 | []------------------------------------+-------------------------------------[] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat May 9 04:20:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA04624 for freebsd-hardware-outgoing; Sat, 9 May 1998 04:20:13 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA04619 for ; Sat, 9 May 1998 04:20:05 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA30393; Sat, 9 May 1998 21:15:56 +1000 Date: Sat, 9 May 1998 21:15:56 +1000 From: Bruce Evans Message-Id: <199805091115.VAA30393@godzilla.zeta.org.au> To: freebsd-hardware@FreeBSD.ORG, gavin@itworks.com.au Subject: Re: Serial port problems Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I've just acquired 2 servers to run 2.2.6-RELEASE on. They are both using >Iwill P55XUB motherboards. The book that came with the motherboard says >that the onboard serial ports are NS16C550 compatible. It apparently misspells `incompatible' :-). There have been several reports that serial ports on Iwills don't work under FreeBSD. >If I boot up using a serial console I get the boot messages coming through >loud and clear (so the serial port was probed and is working), but the This doesn't follow. The boot messages are printed by an independent part of the driver that doesn't probe the ports or use interrupts. >kernel panic as soon as is probes for the serial ports. The last message >before the cu session closed is > Probing for devices ocu: Got hangup signal > >which is the probing of the ISA bus message. > >If I cu again and enter cont into ddb I get > >Fatal trap 12: page fault while in kernel mode >fault virtual address = 0x4 >fault code = supervisor read, page not present >instruction pointer = 0x8:0xf01c37ee >stack pointer = 0x10:0xefbfff80 >frame pointer = 0x10:0xefbfff80 >code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 >processor eflags = interrupt enabled, resume, IOPL = 0 >current process = 0 () >interrupt mask = >kernel: type 12 trap, code=0 >Stopped at _cninit_finish+0x26: movl 0x4(%edx),%eax The panic is caused by a null pointer bug (cdevsw[SIO_MAJOR] = 0, and cninit_finish() doesn't check). It shows that all sio probes failed, but we already know that. The hangup is more interesting. The console output routines attempt to switch the h/w state so that you can debug sio probes using sio output, but switching the DTR state back off might cause avoidable hangups, so DTR is left on. To debug the probes, you have to start earlier. Boot with -d and put a breakpoint at sioprobe() and look around. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat May 9 04:32:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA06117 for freebsd-hardware-outgoing; Sat, 9 May 1998 04:32:23 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from itw.itworks.com.au (root@itw.itworks.com.au [203.32.61.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA06109 for ; Sat, 9 May 1998 04:32:19 -0700 (PDT) (envelope-from gavin@itworks.com.au) Received: from localhost (gavin@localhost) by itw.itworks.com.au (8.8.8/8.8.5) with SMTP id VAA20206; Sat, 9 May 1998 21:29:14 +1000 (EST) Date: Sat, 9 May 1998 21:29:13 +1000 (EST) From: Gavin Cameron To: Bruce Evans cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Serial port problems In-Reply-To: <199805091115.VAA30393@godzilla.zeta.org.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 Stoping in sioprobe() and single stepping give me the following Probing for devices on the ISA bus: Breakpoint at _sioprobe: pushl %ebp db> s Stopped at _sioprobe+0x1: movl %esp,%ebp db> Stopped at _sioprobe+0x3: subl $0x1c,%esp db> Stopped at _sioprobe+0x6: pushl %edi db> Stopped at _sioprobe+0x7: pushl %esi db> Stopped at _sioprobe+0x8: pushl %ebx db> Stopped at _sioprobe+0x9: cmpb $0,_already_init.114 db> Stopped at _sioprobe+0x10: jnz _sioprobe+0x48 db> Stopped at _sioprobe+0x12: movl $0xf0201870,%ecx db> Stopped at _sioprobe+0x17: cmpl $0,_isa_devtab_tty+0x4 db> Stopped at _sioprobe+0x1e: jz _sioprobe+0x41 db> Stopped at _sioprobe+0x20: cmpl $0xf02001f4,0x4(%ecx) db> Stopped at _sioprobe+0x27: jnz _sioprobe+0x38 db> Stopped at _sioprobe+0x29: cmpl $0,0x34(%ecx) db> Stopped at _sioprobe+0x2d: jz _sioprobe+0x38 db> Stopped at _sioprobe+0x2f: movl 0x8(%ecx),%edx db> Stopped at _sioprobe+0x32: addl $0x4,%edx db> Stopped at _sioprobe+0x35: xorb %al,%al db> Stopped at _sioprobe+0x37: outb %al,%dx db> cu: Got hangup signal Disconnected. gavin@ferret {143} : cu -l cuaa1 -s 9600 Connected. Stopped at _sioprobe+0x3b: cmpl $0,0x4(%ecx) db> s Stopped at _sioprobe+0x3f: jnz _sioprobe+0x20 db> Stopped at _sioprobe+0x20: cmpl $0xf02001f4,0x4(%ecx) db> Stopped at _sioprobe+0x27: jnz _sioprobe+0x38 db> Stopped at _sioprobe+0x29: cmpl $0,0x34(%ecx) db> Stopped at _sioprobe+0x2d: jz _sioprobe+0x38 db> Stopped at _sioprobe+0x2f: movl 0x8(%ecx),%edx db> Stopped at _sioprobe+0x32: addl $0x4,%edx db> Stopped at _sioprobe+0x35: xorb %al,%al db> Stopped at _sioprobe+0x37: outb %al,%dx db> Does this shed light for anyone? Thanks Gavin []------------------------------------+-------------------------------------[] | Gavin Cameron | ITworks Consulting | | Ph : 0418 390350 | Suite 100, 85 Grattan Street | | Fax : +61 3 9347 6544 | Carlton, Victoria | | Email : gavin@itworks.com.au | Australia, 3053 | []------------------------------------+-------------------------------------[] On Sat, 9 May 1998, Bruce Evans wrote: > >I've just acquired 2 servers to run 2.2.6-RELEASE on. They are both using > >Iwill P55XUB motherboards. The book that came with the motherboard says > >that the onboard serial ports are NS16C550 compatible. > > It apparently misspells `incompatible' :-). There have been several > reports that serial ports on Iwills don't work under FreeBSD. > > >If I boot up using a serial console I get the boot messages coming through > >loud and clear (so the serial port was probed and is working), but the > > This doesn't follow. The boot messages are printed by an independent part > of the driver that doesn't probe the ports or use interrupts. > > >kernel panic as soon as is probes for the serial ports. The last message > >before the cu session closed is > > Probing for devices ocu: Got hangup signal > > > >which is the probing of the ISA bus message. > > > >If I cu again and enter cont into ddb I get > > > >Fatal trap 12: page fault while in kernel mode > >fault virtual address = 0x4 > >fault code = supervisor read, page not present > >instruction pointer = 0x8:0xf01c37ee > >stack pointer = 0x10:0xefbfff80 > >frame pointer = 0x10:0xefbfff80 > >code segment = base 0x0, limit 0xfffff, type 0x1b > > = DPL 0, pres 1, def32 1, gran 1 > >processor eflags = interrupt enabled, resume, IOPL = 0 > >current process = 0 () > >interrupt mask = > >kernel: type 12 trap, code=0 > >Stopped at _cninit_finish+0x26: movl 0x4(%edx),%eax > > The panic is caused by a null pointer bug (cdevsw[SIO_MAJOR] = 0, and > cninit_finish() doesn't check). It shows that all sio probes failed, > but we already know that. > > The hangup is more interesting. The console output routines attempt to > switch the h/w state so that you can debug sio probes using sio output, > but switching the DTR state back off might cause avoidable hangups, so > DTR is left on. > > To debug the probes, you have to start earlier. Boot with -d and put > a breakpoint at sioprobe() and look around. > > Bruce > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat May 9 05:55:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA10605 for freebsd-hardware-outgoing; Sat, 9 May 1998 05:55:12 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA10596 for ; Sat, 9 May 1998 05:55:08 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id WAA00469; Sat, 9 May 1998 22:52:50 +1000 Date: Sat, 9 May 1998 22:52:50 +1000 From: Bruce Evans Message-Id: <199805091252.WAA00469@godzilla.zeta.org.au> To: bde@zeta.org.au, gavin@itworks.com.au Subject: Re: Serial port problems Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Stoping in sioprobe() and single stepping give me the following > >Probing for devices on the ISA bus: >Breakpoint at _sioprobe: pushl %ebp >db> s ... >Stopped at _sioprobe+0x35: xorb %al,%al >db> >Stopped at _sioprobe+0x37: outb %al,%dx This turns off DTR (among other things). >db> cu: Got hangup signal >Disconnected. DTR is normally connected to CD for a PC <-> PC connection, so turning off DTR drops CD and not-dumb-enough terminal programs disconnect. >gavin@ferret {143} : cu -l cuaa1 -s 9600 >Connected. >Stopped at _sioprobe+0x3b: cmpl $0,0x4(%ecx) >db> s >Stopped at _sioprobe+0x3f: jnz _sioprobe+0x20 >... >Does this shed light for anyone? It probably takes a few thousand instructions to get anywhere interesting. 0x80 in the device flags would show which parts of the probe fail. According to previous reports, IRQ4 doesn't go away properly when the device drives IRQ4 low. It would be interesting to know if IRQ4 ever has the correct value. Its value is given by bit 0x10 in port 0x20 (`call inb(0x20)' in ddb). Programming sio0 manually in ddb should make it go low: call outb(0x3f8+3,3) call outb(0x3f8+1,0) call outb(0x3f8+4,0xb) Disconnecting sio0 from IRQ4 should then make it float high: call outb(0x3f8+4,0x3) Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat May 9 07:01:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16562 for freebsd-hardware-outgoing; Sat, 9 May 1998 07:01:52 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from IBM.rhrz.uni-bonn.de (ibm.rhrz.uni-bonn.de [131.220.236.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA16553 for ; Sat, 9 May 1998 07:01:47 -0700 (PDT) (envelope-from uzsv2k@IBM.rhrz.uni-bonn.de) Received: from uni-bonn.de (131.220.225.110,1027) by IBM.rhrz.uni-bonn.de (IBM/VM SMTP V2R2) with TCP; Sat, 09 May 98 16:01:52 MEZ Message-ID: <3554570D.2552D445@uni-bonn.de> Date: Sat, 09 May 1998 15:15:57 +0200 From: Philipp Reichmuth X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: hardware@FreeBSD.ORG Subject: Re: Underclocking: 486 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > You can underclock CPU's - and they do run cooler... I used to run a > machine that was a 486DX4/100 with it's 'internal cache' disabled as I > didn't have a heatsink... If one can do without Pentium CPU power, I think a 486 is the best choice at the moment anyway because there are a lot of them available at very reasonable prices. You can get a 486 DX4/133 w/board fairly cheap and run the bus at 25 MHz, so the CPU runs at 100 internally and you don't lose the cache which is really a performance factor, esp. on the DX4/1xx ones because they're larger. It worked well without a fan for me, but the machine stood in a rather cool cellar. Installing a Pentium cooler ;-) should keep temperature at bay as well. Performance should be OK for router boxes, even though the PCI runs at 25 MHz there as well. Doesn't have much impact on network or SCSI performance, however. > I guess it might make sense to some people - I always prefer to have 'more > than adequate' cooling though... ;-) ;-) Philipp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat May 9 18:27:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26412 for freebsd-hardware-outgoing; Sat, 9 May 1998 18:27:45 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26407 for ; Sat, 9 May 1998 18:27:38 -0700 (PDT) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id KAA02533; Sun, 10 May 1998 10:57:33 +0930 (CST) (envelope-from grog) Message-ID: <19980510105733.C12200@freebie.lemis.com> Date: Sun, 10 May 1998 10:57:33 +0930 From: Greg Lehey To: Bruce Evans , freebsd-hardware@FreeBSD.ORG, gavin@itworks.com.au Subject: Re: Serial port problems References: <199805091115.VAA30393@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199805091115.VAA30393@godzilla.zeta.org.au>; from Bruce Evans on Sat, May 09, 1998 at 09:15:56PM +1000 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 9 May 1998 at 21:15:56 +1000, Bruce Evans wrote: >> I've just acquired 2 servers to run 2.2.6-RELEASE on. They are both using >> Iwill P55XUB motherboards. The book that came with the motherboard says >> that the onboard serial ports are NS16C550 compatible. > > It apparently misspells `incompatible' :-). There have been several > reports that serial ports on Iwills don't work under FreeBSD. This appears to be traceable to a specific Acer UART. Yuri Krichevsky has done a quick hack to fix it, and it works well (I'm using an Iwill board as well). Pick up the patches at http://www.lemis.com/serial-port-patch.html >> kernel panic as soon as is probes for the serial ports. The last message >> before the cu session closed is >> Probing for devices ocu: Got hangup signal This is different from what I've seen, however, but I'm not running 2.2.6. I wonder if this is the result of booting with a serial console. Anyway, grab the patch and tell me (and Yuri) if that helps. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message