From owner-freebsd-hardware Sun Oct 8 07:47:08 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA02578 for hardware-outgoing; Sun, 8 Oct 1995 07:47:08 -0700 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA02565 for ; Sun, 8 Oct 1995 07:47:02 -0700 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id PAA16412 ; Sun, 8 Oct 1995 15:46:58 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id PAA00604 ; Sun, 8 Oct 1995 15:46:58 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.1/keltia-uucp-2.6) id NAA20546; Sun, 8 Oct 1995 13:00:29 +0100 (MET) From: Ollivier Robert Message-Id: <199510081200.NAA20546@keltia.freenix.fr> Subject: Re: PCI DE21040 based cards. To: pete@puffin.pelican.com (Pete Carah) Date: Sun, 8 Oct 1995 13:00:29 +0100 (MET) Cc: hardware@freebsd.org In-Reply-To: from "Pete Carah" at Oct 7, 95 04:31:00 pm X-Operating-System: FreeBSD 2.2-CURRENT ctm#1190 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org Precedence: bulk It seems that Pete Carah said: > And be careful for a while - current shipments from SMC are all 21041 and > our driver doesn't probe them (unless DG has released the new driver). Matt did: /sys/pci/if_de.c: ---------------------------- revision 1.31 date: 1995/09/29 19:52:10; author: davidg; state: Exp; lines: +891 -232 Latest version from Matt Thomas. This version works with the newer DC21041 NICs and with ZNYX cards. Submitted by: Matt Thomas ---------------------------- -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #1: Tue Oct 3 02:08:00 MET 1995 From owner-freebsd-hardware Sun Oct 8 12:26:05 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA09546 for hardware-outgoing; Sun, 8 Oct 1995 12:26:05 -0700 Received: from fgate.flevel.co.uk (fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA09541 for ; Sun, 8 Oct 1995 12:26:02 -0700 Received: (from freebsd@localhost) by fgate.flevel.co.uk (8.6.11/8.6.9) id UAA03003; Sun, 8 Oct 1995 20:28:20 +0100 Date: Sun, 8 Oct 1995 20:28:20 +0100 (BST) From: freebsd To: freebsd-hardware@freebsd.org Subject: DASS2 Cards Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org Precedence: bulk Does anyone have any inormation about support for DASS2 cards? I have the details of a card marketed under the brand name of Aculab for primary rate ISDN with DASS2 compatibility. The card is a 16bit PC/AT and has BABT approval. The signalling processor is two 16MHz 80188s with a control Interface which is stated to be 32k tri-port RAM. The card is in 75ohm and 120ohm versions each of which can be supplied to support 60 lines or 30 lines. The brochure states that it is DIALOGIC open developer product and that the card has also connection approval in Germany. We would be interested in receiving any information from anyone who has succesfully installed a DASS2 comnpatible card on a freebsd system. david S. From owner-freebsd-hardware Sun Oct 8 18:16:31 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA17059 for hardware-outgoing; Sun, 8 Oct 1995 18:16:31 -0700 Received: from husc.harvard.edu (root@scunix5.harvard.edu [140.247.30.45]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA17049 for ; Sun, 8 Oct 1995 18:16:29 -0700 Received: from scws26.harvard.edu by husc.harvard.edu with ESMTP; Sun, 8 Oct 1995 21:16:28 -0400 Received: by scws26.harvard.edu id VAA09258; Sun, 8 Oct 1995 21:27:33 -0400 Date: Sun, 8 Oct 1995 21:27:31 -0400 (EDT) From: Sir Ilya Tsymbal Subject: problem booting w/ati m64 To: hardware@freebsd.org, questions@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org Precedence: bulk I am having a problem booting from a floppy with ATI PCI Mach64. Kernel loads, but when it checks for peripherals and such, the monitor goes blanc or (with another monitor) white lines appear for the rest of peripherals testing, and when the blue install screen is supposed to come up, the screen turns green and funny line patterns run through it. I tried booting with -c flag, but I am not sure of which device is the monitor - in case i need to change IRQ and memory address. Dos and Windows work fine with the same card; Windows claims the card has IRQ 10 and the ATI's install disk claims the card has memory address 2ECh. I booted with -c and set sc0 device to irq 10 and address 2ec - it wouldn't accept 2ech. Is there a way to know these things for sure? The system boots fine with a different card - all the way to the install screen. I tried experimenting with different BIOS settings, and also card settings through the card's install program. Anyway, If you have any idea, please tell me. Thank you in advance, Ilya. Ilya Tsymbal '96 Harvard U, Quincy House. itsymbal@husc.harvard.edu http://itsymbal.student.harvard.edu/ilya/ From owner-freebsd-hardware Mon Oct 9 07:38:37 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA12023 for hardware-outgoing; Mon, 9 Oct 1995 07:38:37 -0700 Received: from gemsgw.med.ge.com (gemsgw.med.ge.com [192.88.230.10]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id HAA12018 for ; Mon, 9 Oct 1995 07:38:33 -0700 Received: from gemed.med.ge.com by gemsgw.med.ge.com (4.1/GEMS-1.1) id AA27266; Mon, 9 Oct 95 09:40:33 CDT Received: from sol.sol.med.ge.com (sol-gw [3.28.124.2]) by gemed.med.ge.com (8.6.12/8.6.12) with SMTP id JAA07197 for ; Mon, 9 Oct 1995 09:36:59 -0500 Received: from merak.med.ge.com by sol.sol.med.ge.com (4.1/SMI-4.1) id AA02306; Mon, 9 Oct 95 09:38:42 CDT From: laufen@sol.med.ge.com (Derek Laufenberg x7-4534) Received: by merak.med.ge.com (4.1/client-1.3) id AA24795; Mon, 9 Oct 95 09:38:41 CDT Date: Mon, 9 Oct 95 09:38:41 CDT Message-Id: <9510091438.AA24795@merak.med.ge.com> To: freebsd-hardware@freebsd.org Subject: xircom cards - any experience? Sender: owner-hardware@freebsd.org Precedence: bulk I was wondering if anyone here has had any experience with Xircom? I'm trying to get some tech info about one of their cards I own. I'd like to modify the if_zp driver to support this card. Does anyone have any contacts at Xircom - or know where to find the required docs to workup a driver for the card? This is a longshot I realize. :) All I got from them is that there are some SCO drivers and I should contact Sales. Derek Laufenberg From owner-freebsd-hardware Mon Oct 9 09:21:52 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA15186 for hardware-outgoing; Mon, 9 Oct 1995 09:21:52 -0700 Received: from gemsgw.med.ge.com (gemsgw.med.ge.com [192.88.230.10]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id JAA15181 for ; Mon, 9 Oct 1995 09:21:50 -0700 Received: from gemed.med.ge.com by gemsgw.med.ge.com (4.1/GEMS-1.1) id AA04462; Mon, 9 Oct 95 11:23:45 CDT Received: from sol.sol.med.ge.com (sol-gw [3.28.124.2]) by gemed.med.ge.com (8.6.12/8.6.12) with SMTP id LAA10848 for ; Mon, 9 Oct 1995 11:20:10 -0500 Received: from merak.med.ge.com by sol.sol.med.ge.com (4.1/SMI-4.1) id AA03501; Mon, 9 Oct 95 11:21:53 CDT From: laufen@sol.med.ge.com (Derek Laufenberg x7-4534) Received: by merak.med.ge.com (4.1/client-1.3) id AA25750; Mon, 9 Oct 95 11:21:53 CDT Date: Mon, 9 Oct 95 11:21:53 CDT Message-Id: <9510091621.AA25750@merak.med.ge.com> To: freebsd-hardware@freebsd.org Subject: PCMCIA - any good books, tech notes? Sender: owner-hardware@freebsd.org Precedence: bulk Are there any books or tech notes that I should read to learn how this interface works? What about code examples - which would be best to study? Derek From owner-freebsd-hardware Mon Oct 9 14:01:56 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA22767 for hardware-outgoing; Mon, 9 Oct 1995 14:01:56 -0700 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id OAA22736 ; Mon, 9 Oct 1995 14:01:50 -0700 X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com didn't use HELO protocol To: hackers, hardware Subject: PCMCIA MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <22729.813272508.1@freefall.freebsd.org> Date: Mon, 09 Oct 1995 14:01:49 -0700 Message-ID: <22733.813272509@freefall.freebsd.org> From: Poul-Henning Kamp Sender: owner-hardware@FreeBSD.org Precedence: bulk I have just a second ago managed to plug first my ether, then my modem, then my ether again and finally my modem again into my pcmcia slot, and actually get it to work every single time. :-> The code still needs some cleanup, but I hope to commit some of it already tomorrow. The architecture is there, now we just need to clean up the code, and add more drivers (only sio & if_ed at this time). For instance there are a lot of DELAY() calls we need to loose, and power management still needs to be folded in too. People interested in working on pcmcia should make sure they are subscribed to hardware@freebsd.org (send email to majordomo!). Before you start working on a driver, send an email to hardware@freebsd.org, maybe somebody else has some help to offer... You can start to look at the current code today in: src/usr.sbin/pccard src/sys/pccard src/sys/i386/sio.c Most of the honour goes to Andrew McRae, I'm just debugging this :-) Poul-Henning Kamp From owner-freebsd-hardware Mon Oct 9 15:06:34 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA25642 for hardware-outgoing; Mon, 9 Oct 1995 15:06:34 -0700 Received: from gemsgw.med.ge.com (gemsgw.med.ge.com [192.88.230.10]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id PAA25628 for ; Mon, 9 Oct 1995 15:06:29 -0700 Received: from gemed.med.ge.com by gemsgw.med.ge.com (4.1/GEMS-1.1) id AA01104; Mon, 9 Oct 95 17:08:31 CDT Received: from sol.sol.med.ge.com (sol-gw [3.28.124.2]) by gemed.med.ge.com (8.6.12/8.6.12) with SMTP id RAA20481; Mon, 9 Oct 1995 17:04:55 -0500 Received: from merak.med.ge.com by sol.sol.med.ge.com (4.1/SMI-4.1) id AA06159; Mon, 9 Oct 95 17:06:39 CDT From: laufen@sol.med.ge.com (Derek Laufenberg x7-4534) Received: by merak.med.ge.com (4.1/client-1.3) id AA00920; Mon, 9 Oct 95 17:06:38 CDT Date: Mon, 9 Oct 95 17:06:38 CDT Message-Id: <9510092206.AA00920@merak.med.ge.com> To: phk@freefall.freebsd.org Subject: Re: PCMCIA Cc: hardware@freebsd.org Sender: owner-hardware@freebsd.org Precedence: bulk Congrats. One quick question - which modem and ethernet cards? Derek > > I have just a second ago managed to plug first my ether, then my modem, > then my ether again and finally my modem again into my pcmcia slot, > and actually get it to work every single time. :-> > > The code still needs some cleanup, but I hope to commit some of it > already tomorrow. > > The architecture is there, now we just need to clean up the code, and > add more drivers (only sio & if_ed at this time). For instance there > are a lot of DELAY() calls we need to loose, and power management still > needs to be folded in too. > > People interested in working on pcmcia should make sure they are > subscribed to hardware@freebsd.org (send email to majordomo!). > > Before you start working on a driver, send an email to hardware@freebsd.org, > maybe somebody else has some help to offer... > > You can start to look at the current code today in: > src/usr.sbin/pccard > src/sys/pccard > src/sys/i386/sio.c > > Most of the honour goes to Andrew McRae, I'm just debugging this :-) > > Poul-Henning Kamp > From owner-freebsd-hardware Mon Oct 9 23:13:25 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA12646 for hardware-outgoing; Mon, 9 Oct 1995 23:13:25 -0700 Received: from husc.harvard.edu (root@scunix5.harvard.edu [140.247.30.45]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA12631 for ; Mon, 9 Oct 1995 23:13:22 -0700 Received: from itsymbal-2.student.harvard.edu by husc.harvard.edu with SMTP; Tue, 10 Oct 1995 02:13:15 -0400 Date: Tue, 10 Oct 1995 02:13:15 -0400 Message-Id: <199510100613.CAA00580@husc.harvard.edu> To: questions@freebsd.org, hardware@freebsd.org Newsgroups: comp.unix.bsd.freebsd.misc Subject: FreeBSD & ATI Mach64 install problem (follow-up) From: itsymbal@husc.harvard.edu (Sir Ilya Tsymbal) Organization: Harvard University Reply-To: Ilya Tsymbal X-Newsreader: WinVN 0.93.14 MIME-Version: 1.0 Sender: owner-hardware@freebsd.org Precedence: bulk I have been having a problem installing FreeBSD with Mach64 card. During the start-up phase when hardware is probed, the screen either goes blank or (depending on the monitor) shows lines. A different cideo card (Diamond SpeedStar) works fine. I have found that if I start with -c flag during boot and disable ALL com ports - sio0-3 then the card behaves appropriately. I do need to use a mouse ( at least) and preferably a modem. The ATI install disk claims the card is using Base I/O address 0x2ECh; however, with all com ports disabled it works fine if sc0 is set to either 0x2ec (card's setting) or 0x60. I have found no sure way to tell which IRQ the card is using; it seems to work fine with sc0's irq set to 1. If I leave any one com port enabled, the card will mess up. Wether or not the particular com port is actually present does not seem to make a difference. That's all the information I have; I would appreciate any input. Thank you, Ilya Tsymbal From owner-freebsd-hardware Mon Oct 9 23:55:00 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA15892 for hardware-outgoing; Mon, 9 Oct 1995 23:55:00 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA15884 ; Mon, 9 Oct 1995 23:54:54 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id QAA11243; Tue, 10 Oct 1995 16:53:18 +0930 From: Michael Smith Message-Id: <199510100723.QAA11243@genesis.atrad.adelaide.edu.au> Subject: Re: FreeBSD & ATI Mach64 install problem (follow-up) To: itsymbal@husc.harvard.edu Date: Tue, 10 Oct 1995 16:53:17 +0930 (CST) Cc: questions@freebsd.org, hardware@freebsd.org In-Reply-To: <199510100613.CAA00580@husc.harvard.edu> from "Sir Ilya Tsymbal" at Oct 10, 95 02:13:15 am Content-Type: text Content-Length: 1858 Sender: owner-hardware@freebsd.org Precedence: bulk Sir Ilya Tsymbal stands accused of saying: > > I have been having a problem installing FreeBSD with Mach64 card. > During the start-up phase when hardware is probed, the screen either goes > blank or (depending on the monitor) shows lines. > > A different cideo card (Diamond SpeedStar) works fine. > > I have found that if I start with -c flag during boot and disable ALL com > ports - sio0-3 then the card behaves appropriately. I do need to use a > mouse ( at least) and preferably a modem. It would appear that the Mach64 in your configuration conflicts with your serial ports. > The ATI install disk claims the card is using Base I/O address 0x2ECh; > however, with all com ports disabled it works fine if sc0 is set to either > 0x2ec (card's setting) or 0x60. Leave sc0 at 0x60. It's not trying to talk to the special registers on the Mach64. > I have found no sure way to tell which IRQ the card is using; it seems to > work fine with sc0's irq set to 1. IRQ 1 is the keyboard. If the Mach64 generates any interrupts, they'll be on IRQ 9. > If I leave any one com port enabled, the card will mess up. Wether or not > the particular com port is actually present does not seem to make a > difference. Are you certain about this? 0x2ec will conflict with sio3, which is at 0x2e8. I would expect this to cause some problems. Note that most/all S3 based video boards occupy this address, and thus conflict to some degree with com4. > Ilya Tsymbal -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[ From owner-freebsd-hardware Mon Oct 9 23:57:57 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA16207 for hardware-outgoing; Mon, 9 Oct 1995 23:57:57 -0700 Received: from fgate.flevel.co.uk (fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA16179 ; Mon, 9 Oct 1995 23:57:49 -0700 Received: (from freebsd@localhost) by fgate.flevel.co.uk (8.6.11/8.6.9) id IAA07449; Tue, 10 Oct 1995 08:00:39 +0100 Date: Tue, 10 Oct 1995 08:00:39 +0100 (BST) From: freebsd To: hardware@freebsd.org cc: hackers@freebsd.org Subject: DASS2 Cards (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org Precedence: bulk I am uncertain whether this got posted correctly as I am new to this mailing list. Has anyone an DASS2 experience with freebsd? Here is a repost - apolgies if you have altready received it. ---------- Forwarded message ---------- Date: Sun, 8 Oct 1995 20:28:20 +0100 (BST) From: freebsd To: freebsd-hardware@freebsd.org Subject: DASS2 Cards Does anyone have any information about support for DASS2 cards? I have the details of a card marketed under the brand name of Aculab for primary rate ISDN with DASS2 compatibility. The card is a 16bit PC/AT and has BABT approval. The signalling processor is two 16MHz 80188s with a control Interface which is stated to be 32k tri-port RAM. The card is in 75ohm and 120ohm versions each of which can be supplied to support 60 lines or 30 lines. The brochure states that it is DIALOGIC open developer product and that the card has also connection approval in Germany. We would be interested in receiving any information from anyone who has succesfully installed a DASS2 comnpatible card on a freebsd system. david S. From owner-freebsd-hardware Tue Oct 10 01:10:07 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA22019 for hardware-outgoing; Tue, 10 Oct 1995 01:10:07 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA21992 ; Tue, 10 Oct 1995 01:09:50 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id SAA11883; Tue, 10 Oct 1995 18:02:33 +1000 Date: Tue, 10 Oct 1995 18:02:33 +1000 From: Bruce Evans Message-Id: <199510100802.SAA11883@godzilla.zeta.org.au> To: itsymbal@husc.harvard.edu, msmith@atrad.adelaide.edu.au Subject: Re: FreeBSD & ATI Mach64 install problem (follow-up) Cc: hardware@freebsd.org, questions@freebsd.org Sender: owner-hardware@freebsd.org Precedence: bulk >> I have found that if I start with -c flag during boot and disable ALL com >> ports - sio0-3 then the card behaves appropriately. I do need to use a >> mouse ( at least) and preferably a modem. >It would appear that the Mach64 in your configuration conflicts with your >serial ports. Probably only sio3. >> The ATI install disk claims the card is using Base I/O address 0x2ECh; >> however, with all com ports disabled it works fine if sc0 is set to either >> 0x2ec (card's setting) or 0x60. >Leave sc0 at 0x60. It's not trying to talk to the special registers on the >Mach64. Setting it to 0x2EC is harmless because sc0 ignores the setting. This setting may even help by confusing the conflict checking code into thinking that sc0 uses ports 0x2EC-0x2FB (actually only X uses it). These addresses overlap with the normal ones for sio1 and sio3, and sc0 is probed first, so sio1 and sio3 may be skipped due to the conflict. >> If I leave any one com port enabled, the card will mess up. Wether or not >> the particular com port is actually present does not seem to make a >> difference. >Are you certain about this? 0x2ec will conflict with sio3, which is at 0x2e8. >I would expect this to cause some problems. Note that most/all S3 based >video boards occupy this address, and thus conflict to some degree with >com4. sio does an outb(0x2EC, 0) if _any_ com port is enabled :-(. It does this to handle braindamage involving edge triggered interrupts (all ports sharing an IRQ must have their IRQ enable disabled although it is only possible to use one such port so it would be natural not to configure the other ones). Bruce From owner-freebsd-hardware Tue Oct 10 01:33:14 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA23070 for hardware-outgoing; Tue, 10 Oct 1995 01:33:14 -0700 Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id BAA23056 for ; Tue, 10 Oct 1995 01:33:09 -0700 Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0t2a7X-0003wnC; Tue, 10 Oct 95 01:33 PDT Received: from localhost (localhost [127.0.0.1]) by critter.tfs.com (8.6.11/8.6.9) with SMTP id JAA00809; Tue, 10 Oct 1995 09:33:04 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost didn't use HELO protocol To: laufen@sol.med.ge.com (Derek Laufenberg x7-4534) cc: phk@freefall.freebsd.org, hardware@freebsd.org Subject: Re: PCMCIA In-reply-to: Your message of "Mon, 09 Oct 1995 17:06:38 CDT." <9510092206.AA00920@merak.med.ge.com> Date: Tue, 10 Oct 1995 09:33:04 +0100 Message-ID: <807.813313984@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hardware@freebsd.org Precedence: bulk > Congrats. > > One quick question - which modem and ethernet cards? IBM/National "Infomover" and a MEGAHERTZ 14.4 modem. but almost any modem card should work now, if you can find the right magic for it... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. It will be some time yet before progress goes too far... (Poul Henningsen) From owner-freebsd-hardware Tue Oct 10 06:51:22 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA03170 for hardware-outgoing; Tue, 10 Oct 1995 06:51:22 -0700 Received: from gemsgw.med.ge.com (gemsgw.med.ge.com [192.88.230.10]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id GAA03163 for ; Tue, 10 Oct 1995 06:51:18 -0700 Received: from gemed.med.ge.com by gemsgw.med.ge.com (4.1/GEMS-1.1) id AA27609; Tue, 10 Oct 95 08:53:20 CDT Received: from sol.sol.med.ge.com (sol-gw [3.28.124.2]) by gemed.med.ge.com (8.6.12/8.6.12) with SMTP id IAA08665; Tue, 10 Oct 1995 08:49:44 -0500 Received: from merak.med.ge.com by sol.sol.med.ge.com (4.1/SMI-4.1) id AA09554; Tue, 10 Oct 95 08:51:27 CDT From: laufen@sol.med.ge.com (Derek Laufenberg x7-4534) Received: by merak.med.ge.com (4.1/client-1.3) id AA08558; Tue, 10 Oct 95 08:51:26 CDT Date: Tue, 10 Oct 95 08:51:26 CDT Message-Id: <9510101351.AA08558@merak.med.ge.com> To: ds9@xircom.com, CS@xircom.com Subject: xircom cards - was: Re: Re[2]: Unix Drivers? FH/176695/COMP Cc: freebsd-hardware@freebsd.org Sender: owner-hardware@freebsd.org Precedence: bulk Dear Sirs at Xircom, No problem. I've returned your card to the store I purchased it from. They gladly sold be one of your competitors cards. It was less expensive so I thank you for the cost savings. :) Derek Laufenberg PS: I've CC'd this to a few of the Free OS mailing lists to warn others interested in open systems about your products. > From ds9@xircom.com Mon Oct 9 21:36:12 1995 > Return-Path: > Received: from gemed.med.ge.com by sol.sol.med.ge.com (4.1/SMI-4.1) > id AA07181; Mon, 9 Oct 95 21:36:11 CDT > Received: from gemsgw.med.ge.com (gemsgw [3.28.88.26]) by gemed.med.ge.com (8.6.12/8.6.12) with SMTP id VAA23855 for ; Mon, 9 Oct 1995 21:32:55 -0500 > Received: from phydeax.xircom.com by gemsgw.med.ge.com (4.1/GEMS-1.1) > id AA08373; Mon, 9 Oct 95 21:34:55 CDT > Received: from smtpgate.xircom.com (smtpgate.xircom.com [199.107.130.15]) by phydeax.xircom.com (8.6.12/8.6.12) with SMTP id TAA18009 for ; Mon, 9 Oct 1995 19:26:51 -0700 > Received: from ccMail by smtpgate.xircom.com > (IMA Internet Exchange 1.04b) id 079db640; Mon, 9 Oct 95 19:33:08 -0700 > Mime-Version: 1.0 > Date: Mon, 9 Oct 1995 19:30:14 -0700 > Message-Id: <079db640@xircom.com> > From: ds9@xircom.com (DS9) > Subject: Re[2]: Unix Drivers? FH/176695/COMP > To: laufen@sol.med.ge.com (Derek Laufenberg x7-4534) > Content-Type> : > text/plain> ; > charset=US-ASCII> > Content-Transfer-Encoding: 7bit > Content-Description: cc:Mail note part > Content-Length: 2955 > X-Lines: 94 > Status: RO > > > Derek, > > Tracking # 176695 > > Unfortunately our drivers are proprietary but a software developers > kit can be purchased through our Sales Department. > > Should you have any further questions, Please don't hesitate to > contact us again. > > Please send all correspondences to CS@XIRCOM.COM, all others will be > forwarded resulting in a longer reply time! > > > Regards, > Frank Henderson > Xircom Technical Support > CS@XIRCOM.COM > > > > ______________________________ Reply Separator _________________________________ > Subject: Re: Unix Drivers? TN 176695 CoMp DLH > Author: laufen@sol.med.ge.com (Derek Laufenberg x7-4534) at internet > Date: 10/9/95 8:58 AM > > > Dear Mr. Hentsch, > > OK, so no unix drivers exist. I'll write one - No big deal. Where can I > get the CEM2's memory map and register layout. If this is proprietary info > please say so. I can return this card and get one which is already supported > by FreeBSD or Linux. I know the 3Com ether net card is supported because > that is the driver code I'm using to build a driver for the CEM2 product. > > I've looked at your BBS and Faxline. There is no detailed technical > information for this card (or any others) located there. > > Could you please forward this to someone in software engineering? It > is most likely they will be able to help me. Sending me to "sales" will > only result in you loosing a customer. > > Thankyou, > > Derek Laufenberg > > > > > Derek; > > > > To my knowledge there are no unix drivers available for the COMBO > > cards. I know that the CE2 and PE3 have SCO drivers available for > > them. To verify this contact Xircom Sales at 1-800-438-4526. > > > > If you have any questions or require further assistance reply to > > cs@xircom.com and reference the Track Number listed on the subject > > line above. > > > > Regards > > David Hentsch > > Xircom Technical Support > > cs@xircom.com > > > > > > ______________________________ Reply Separator > ________________________________ _ > > Subject: Unix Drivers? > > Author: laufen@sol.med.ge.com (Derek Laufenberg x7-4534) at internet > > Date: 10/6/95 5:07 PM > > > > > > > > Hello Xircom Engineering, > > > > I just picked up one of your Credit Card II combo cards for use > > on my laptop. After a bit of trouble with old drivers and > > bad flash re-programming I got everything running with your > > drivers under MSDOS/Windows. > > > > The laptop I use is a dual use machine which I run DOS and FREEBSD. > > I'm looking for either technical specs on the card or a set of > > driver source code I can port to the unix BSD environment. > > > > Can you help? I'd hate to waste a bunch of time reverse engineering > > the interface software. > > > > > > Thankyou, > > > > Derek Laufenberg > > laufen@sol.med.ge.com > > > > > From owner-freebsd-hardware Tue Oct 10 07:03:11 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA03461 for hardware-outgoing; Tue, 10 Oct 1995 07:03:11 -0700 Received: from persprog.com (root@persprog.com [204.215.255.203]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA03455 for ; Tue, 10 Oct 1995 07:03:02 -0700 Received: from novell.persprog.com by persprog.com (8.6.9/4.10) id JAA06202; Tue, 10 Oct 1995 09:55:53 -0400 Received: from NOVELL/SpoolDir by novell.persprog.com (Mercury 1.12); Tue, 10 Oct 95 9:56:02 +0500 Received: from SpoolDir by NOVELL (Mercury 1.12); Tue, 10 Oct 95 9:55:58 +0500 From: "David Alderman" Organization: Personalized Programming, Inc. To: laufen@sol.med.ge.com (Derek Laufenberg x7-4534), freebsd-hardware@freebsd.org Date: Tue, 10 Oct 1995 09:55:49 EST Subject: Re: xircom cards - any experience? X-Confirm-Reading-To: "David Alderman" X-pmrqc: 1 Priority: normal X-mailer: Pegasus Mail/Windows (v1.21) Message-ID: <206E12B27B9@novell.persprog.com> Sender: owner-hardware@freebsd.org Precedence: bulk > I was wondering if anyone here has had any experience with > Xircom? I'm trying to get some tech info about one of their cards > I own. I'd like to modify the if_zp driver to support this > card. > > Does anyone have any contacts at Xircom - or know where to find > the required docs to workup a driver for the card? > This is a longshot I realize. :) All I got from them is that there > are some SCO drivers and I should contact Sales. > > > Derek Laufenberg > Last I heard, Xircom has a policy that the interface specs for the network adapters are totally proprietary and you must sign a NDA to get any information from them. One of the BSD FAQ's has a scathing disclaimer concerning the company. If I remember correctly, Xircom claims you are violating their rights by reverse engineering their interface specs. Maybe their policy has changed or perhaps you can convince them that this policy is not in their best interests since it reduces the market for their product. Good Luck. ====================================== When philosophy conflicts with reality, choose reality. Dave Alderman -- dave@persprog.com ====================================== From owner-freebsd-hardware Tue Oct 10 07:09:27 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA03604 for hardware-outgoing; Tue, 10 Oct 1995 07:09:27 -0700 Received: from gemsgw.med.ge.com (gemsgw.med.ge.com [192.88.230.10]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id HAA03594 for ; Tue, 10 Oct 1995 07:09:23 -0700 Received: from gemed.med.ge.com by gemsgw.med.ge.com (4.1/GEMS-1.1) id AA29013; Tue, 10 Oct 95 09:11:25 CDT Received: from sol.sol.med.ge.com (sol-gw [3.28.124.2]) by gemed.med.ge.com (8.6.12/8.6.12) with SMTP id JAA09352; Tue, 10 Oct 1995 09:07:49 -0500 Received: from merak.med.ge.com by sol.sol.med.ge.com (4.1/SMI-4.1) id AA09700; Tue, 10 Oct 95 09:09:33 CDT From: laufen@sol.med.ge.com (Derek Laufenberg x7-4534) Received: by merak.med.ge.com (4.1/client-1.3) id AA08712; Tue, 10 Oct 95 09:09:32 CDT Date: Tue, 10 Oct 95 09:09:32 CDT Message-Id: <9510101409.AA08712@merak.med.ge.com> To: phk@critter.tfs.com Subject: Re: Has the Linux PCMCIA tools been ported? Cc: hardware@freebsd.org Sender: owner-hardware@freebsd.org Precedence: bulk > > > Anyone know about the Linux PCMCIA card service tools? > > Have they been ported to freebsd yet? > > No, and they wont be. > OK -why? No need with the code you just got working? derek From owner-freebsd-hardware Tue Oct 10 07:16:08 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA03864 for hardware-outgoing; Tue, 10 Oct 1995 07:16:08 -0700 Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id HAA03851 for ; Tue, 10 Oct 1995 07:16:03 -0700 Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0t2fTN-0003wpC; Tue, 10 Oct 95 07:16 PDT Received: from localhost (localhost [127.0.0.1]) by critter.tfs.com (8.6.11/8.6.9) with SMTP id PAA01664; Tue, 10 Oct 1995 15:02:28 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost didn't use HELO protocol To: laufen@sol.med.ge.com (Derek Laufenberg x7-4534) cc: hardware@freebsd.org Subject: Re: Has the Linux PCMCIA tools been ported? In-reply-to: Your message of "Tue, 10 Oct 1995 09:09:32 CDT." <9510101409.AA08712@merak.med.ge.com> Date: Tue, 10 Oct 1995 15:02:28 +0100 Message-ID: <1662.813333748@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hardware@freebsd.org Precedence: bulk > > > > > > Anyone know about the Linux PCMCIA card service tools? > > > Have they been ported to freebsd yet? > > > > No, and they wont be. > > > > OK -why? No need with the code you just got working? The code we have fits the unix-model better. The linux stuff, at least last time I looked, was a 1-1 mapping of the rather bogus MSDOS implementation. Did I see you voluteer to help write drivers ? -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. It will be some time yet before progress goes too far... (Poul Henningsen) From owner-freebsd-hardware Tue Oct 10 07:22:00 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA04161 for hardware-outgoing; Tue, 10 Oct 1995 07:22:00 -0700 Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id HAA04156 for ; Tue, 10 Oct 1995 07:21:54 -0700 Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0t2fZ2-0003wBC; Tue, 10 Oct 95 07:21 PDT Received: from localhost (localhost [127.0.0.1]) by critter.tfs.com (8.6.11/8.6.9) with SMTP id PAA01697; Tue, 10 Oct 1995 15:08:20 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost didn't use HELO protocol To: "David Alderman" cc: laufen@sol.med.ge.com (Derek Laufenberg x7-4534), freebsd-hardware@freebsd.org Subject: Re: xircom cards - any experience? In-reply-to: Your message of "Tue, 10 Oct 1995 09:55:49 EST." <206E12B27B9@novell.persprog.com> Date: Tue, 10 Oct 1995 15:08:20 +0100 Message-ID: <1695.813334100@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hardware@freebsd.org Precedence: bulk > [...] If I remember correctly, Xircom > claims you are violating their rights by reverse engineering their > interface specs. [...] At least for people inside the EU this is not the case, the EU has a directive that explicitly allows reverse engineering of "interfaces" in case a spec or description isn't available. :-) Xircom has been on my blacklist ever since they misused the Crynwr source. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. It will be some time yet before progress goes too far... (Poul Henningsen) From owner-freebsd-hardware Tue Oct 10 09:11:32 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA24111 for hardware-outgoing; Tue, 10 Oct 1995 09:11:32 -0700 Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id JAA24105 for ; Tue, 10 Oct 1995 09:11:29 -0700 Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0t2hH5-0003w8C; Tue, 10 Oct 95 09:11 PDT Received: from localhost (localhost [127.0.0.1]) by critter.tfs.com (8.6.11/8.6.9) with SMTP id QAA01930 for ; Tue, 10 Oct 1995 16:50:33 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost didn't use HELO protocol To: hardware@freebsd.org Subject: How to get pccard, pcmcia working: Date: Tue, 10 Oct 1995 16:50:32 +0100 Message-ID: <1928.813340232@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hardware@freebsd.org Precedence: bulk Here is the steps you need to do to get moving with the PCMCIA stuff: This may take some PCMCIA knowledge on your part, but give it a shot: 1) add "controller crd0" and recompile your kernel, reboot. 2) cd /usr/src/lkm/pcic (make obj) make all install modload -e lkm_pcic /lkm/pcic_mod.o 3) cp /usr/src/etc/pccard.conf /etc vi /etc/pccard.conf # insert descriptions of your card in the file. (*) 4) cd /usr/src/usr.sbin/pccard/pccardd (make obj) make sleep 4 ./pccardd -d 5) insert your card. At this time you have to stop and restart pccardd if you unplug your ether-card, since it takes a wrong address next time you plug it in, and shutdown/resume is generally hosed too I think. This will be looked at next. (*) I realize this is a bit non-specific, and that is really too bad. If you don't do it, pccardd will not recognize your card, unless it matches my card. Uncomment the "dumpcis(sp->cis) in line 286 in cardd.c, recompile and run again. Save the stdout&stderr from pccardd and email it to phk@freebsd.org, and I will try to find the right magic for your pccard.conf. If you find it yourself, please email it too, so it can go into our source-tree. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Just that: dried leaves in boiling water ? From owner-freebsd-hardware Thu Oct 12 00:49:29 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA13467 for hardware-outgoing; Thu, 12 Oct 1995 00:49:29 -0700 Received: from smokey.ee.washington.edu (smokey.ee.washington.edu [128.95.75.8]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA13447 ; Thu, 12 Oct 1995 00:49:26 -0700 Received: (from olsenc@localhost) by smokey.ee.washington.edu (8.6.11/8.6.9) id AAA00197; Thu, 12 Oct 1995 00:49:25 -0700 Date: Thu, 12 Oct 1995 00:49:25 -0700 From: Clint Olsen Message-Id: <199510120749.AAA00197@smokey.ee.washington.edu> To: hardware@freebsd.org, questions@freebsd.org Subject: SCSI_DELAY Sender: owner-hardware@freebsd.org Precedence: bulk It was suggested that I increase SCSI_DELAY. As I suspected, it didn't have any effect. I changed it from 10 to 20 seconds. I doubt an eon would have any difference: aic0 at 0x340-0x35f irq 11 on isa aic0 waiting for scsi devices to settle (aic0:1:0): "CDC 94171-9 0045" type 0 fixed SCSI 1 sd0(aic0:1:0): Direct-Access 312MB (640584 512 byte sectors) (aic0:2:0): "unknown unknown ????" type 0 fixed SCSI 0 However, using scsi(8) commands does properly identify the second disk. Could the aic driver be at fault? Thanks, -Clint From owner-freebsd-hardware Thu Oct 12 01:37:48 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA16864 for hardware-outgoing; Thu, 12 Oct 1995 01:37:48 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA16833 ; Thu, 12 Oct 1995 01:37:40 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id SAA16401; Thu, 12 Oct 1995 18:37:28 +0930 From: Michael Smith Message-Id: <199510120907.SAA16401@genesis.atrad.adelaide.edu.au> Subject: Re: SCSI_DELAY To: olsenc@smokey.ee.washington.edu (Clint Olsen) Date: Thu, 12 Oct 1995 18:37:27 +0930 (CST) Cc: hardware@freebsd.org, questions@freebsd.org In-Reply-To: <199510120749.AAA00197@smokey.ee.washington.edu> from "Clint Olsen" at Oct 12, 95 00:49:25 am Content-Type: text Content-Length: 1549 Sender: owner-hardware@freebsd.org Precedence: bulk Clint Olsen stands accused of saying: > > It was suggested that I increase SCSI_DELAY. As I suspected, it > didn't have any effect. I changed it from 10 to 20 seconds. I > doubt an eon would have any difference: > > aic0 at 0x340-0x35f irq 11 on isa > aic0 waiting for scsi devices to settle > (aic0:1:0): "CDC 94171-9 0045" type 0 fixed SCSI 1 > sd0(aic0:1:0): Direct-Access 312MB (640584 512 byte sectors) > (aic0:2:0): "unknown unknown ????" type 0 fixed SCSI 0 > > However, using scsi(8) commands does properly identify the second > disk. Could the aic driver be at fault? No, as the scsi(8) command just uses the aic driver. It's more likely that either : a) if you check the response back during the initial enquiry it's slightly incorrect (I don't have the spec handy, so I can't be sure) or b) the MD21 normally returns the drive type of the ESDI disk attached to it. It's possible that the disk you're using doesn't return its type, and the MD21 is behaving strangely because of this. Either way, I wouldn't sweat it. The MD21 has enough other quirks that a slight bogosity in an inquiry command shouldn't lose you any sleep. > -Clint -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[ From owner-freebsd-hardware Thu Oct 12 02:11:37 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id CAA19956 for hardware-outgoing; Thu, 12 Oct 1995 02:11:37 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id CAA19924 ; Thu, 12 Oct 1995 02:11:30 -0700 Received: (from julian@localhost) by ref.tfs.com (8.6.11/8.6.9) id CAA04673; Thu, 12 Oct 1995 02:11:23 -0700 From: Julian Elischer Message-Id: <199510120911.CAA04673@ref.tfs.com> Subject: Re: SCSI_DELAY To: olsenc@smokey.ee.washington.edu (Clint Olsen) Date: Thu, 12 Oct 1995 02:11:23 -0700 (PDT) Cc: hardware@freebsd.org, questions@freebsd.org In-Reply-To: <199510120749.AAA00197@smokey.ee.washington.edu> from "Clint Olsen" at Oct 12, 95 00:49:25 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 826 Sender: owner-hardware@freebsd.org Precedence: bulk > > It was suggested that I increase SCSI_DELAY. As I suspected, it > didn't have any effect. I changed it from 10 to 20 seconds. I > doubt an eon would have any difference: > > aic0 at 0x340-0x35f irq 11 on isa > aic0 waiting for scsi devices to settle > (aic0:1:0): "CDC 94171-9 0045" type 0 fixed SCSI 1 > sd0(aic0:1:0): Direct-Access 312MB (640584 512 byte sectors) > (aic0:2:0): "unknown unknown ????" type 0 fixed SCSI 0 Well it's seeing the device.. but the resulting data isn't standard... so it doesn't know the type is this a REALLY OLD device? (like maybe SASI not even SCSI?) can you show that identify data again? I'll look at it better next time.. i promise.. > > However, using scsi(8) commands does properly identify the second > disk. Could the aic driver be at fault? > > Thanks, > > -Clint > From owner-freebsd-hardware Thu Oct 12 05:56:15 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA07951 for hardware-outgoing; Thu, 12 Oct 1995 05:56:15 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id FAA07933 for ; Thu, 12 Oct 1995 05:56:10 -0700 Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id FAA21598; Thu, 12 Oct 1995 05:56:07 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id FAA00163; Thu, 12 Oct 1995 05:56:07 -0700 Message-Id: <199510121256.FAA00163@corbin.Root.COM> To: hardware@freebsd.org cc: dyson@root.com, batie@agora.rdrop.com Subject: benchmark results From: David Greenman Reply-To: davidg@root.com Date: Thu, 12 Oct 1995 05:56:06 -0700 Sender: owner-hardware@freebsd.org Precedence: bulk Attached are the results of some benchmark comparisons between similar systems. All of the machines have Triton chipset based motherboards, so the only significant difference is async/pipeline-burst cache and the CPU speed. -DG 90Mhz-async: ASUS PCI/I-P54TP4, 32MB RAM, 256k async cache, Pentium 90Mhz FreeBSD-2.1-stable (Oct. 9th) 90Mhz: ASUS P/I-P55TP4XE, 64MB RAM, 256K pipeline-burst cache, Pentium 90Mhz FreeBSD-current (Oct. 10th) 133Mhz: ASUS P/I-P55TP4XE, 64MB RAM, 256K pipeline-burst cache, Pentium 133Mhz FreeBSD-2.0.5-RELEASE Note that on the 90Mhz machine, the source being compiled is 2.1-stable, which should be very similar (in time) to the source in 2.0.5-RELEASE. -pipe was used in all cases. All tests done twice (and the second time was used) to make sure that everything was cached. "CORBIN" kernel make depend: 46.100u 18.674s 1:05.98 98.1% 105+657k 7+51io 0pf+0w (90Mhz-async) 44.291u 11.232s 0:56.38 98.4% 101+535k 7+49io 0pf+0w (90Mhz) 29.265u 9.772s 0:39.94 97.7% 104+659k 3+41io 0pf+0w (133Mhz) "CORBIN" kernel make: 432.518u 53.907s 8:14.79 98.3% 1046+1271k 13+505io 0pf+0w (90Mhz-async) 347.405u 28.275s 6:23.66 97.9% 1006+1293k 14+497io 0pf+0w (90Mhz) 260.303u 27.605s 5:00.20 95.9% 1043+1264k 52+480io 0pf+0w (133Mhz) For the following, the same (-static) binary was used within each test set. dry: (-O -finline-functions -fomit-frame-pointer) Dhrystone(1.1) time for 500000 passes = 3 (90Mhz-async) This machine benchmarks at 157248 dhrystones/second 3.184u 0.015s 0:03.31 96.3% 48+213k 0+0io 0pf+0w Dhrystone(1.1) time for 500000 passes = 3 (90Mhz) This machine benchmarks at 159203 dhrystones/second 3.159u 0.007s 0:03.16 99.6% 46+206k 0+0io 0pf+0w Dhrystone(1.1) time for 500000 passes = 2 (133Mhz) This machine benchmarks at 230215 dhrystones/second 2.175u 0.007s 0:02.18 99.5% 47+207k 0+0io 0pf+0w ttcp: [implode:davidg] ttcp -p9 -n16384 -t localhost (90Mhz-async) ttcp-t: buflen=8192, nbuf=16384, align=16384/+0, port=9 tcp -> localhost ttcp-t: socket ttcp-t: connect ttcp-t: 134217728 bytes in 16.76 real seconds = 7822.28 KB/sec +++ ttcp-t: 16384 I/O calls, msec/call = 1.05, calls/sec = 977.79 ttcp-t: 0.1user 7.0sys 0:16real 42% 40i+247d 68maxrss 0+2pf 7244+1594csw 0.120u 7.045s 0:16.77 42.6% 40+247k 0+0io 0pf+0w [corbin:davidg] ttcp -p9 -n16384 -t localhost (90Mhz) ttcp-t: buflen=8192, nbuf=16384, align=16384/+0, port=9 tcp -> localhost ttcp-t: socket ttcp-t: connect ttcp-t: 134217728 bytes in 12.49 real seconds = 10495.37 KB/sec +++ ttcp-t: 16384 I/O calls, msec/call = 0.78, calls/sec = 1311.92 ttcp-t: 0.1user 5.6sys 0:12real 46% 42i+275d 98maxrss 0+2pf 5443+4471csw 0.175u 5.693s 0:12.50 46.8% 42+275k 0+0io 0pf+0w [pyrex:davidg] ttcp -p9 -n16384 -t localhost (133Mhz) ttcp-t: buflen=8192, nbuf=16384, align=16384/+0, port=9 tcp -> localhost ttcp-t: socket ttcp-t: connect ttcp-t: 134217728 bytes in 9.31 real seconds = 14071.71 KB/sec +++ ttcp-t: 16384 I/O calls, msec/call = 0.58, calls/sec = 1758.96 ttcp-t: 0.0user 4.4sys 0:09real 49% 41i+267d 46maxrss 0+2pf 4445+6338csw iozone: (We're only interested in the cache read performance) MB reclen bytes/sec written bytes/sec read (90Mhz-async) 4 512 2085319 12761286 4 8192 2127731 24353765 MB reclen bytes/sec written bytes/sec read (90Mhz) 4 512 2235863 15093178 4 8192 2455878 31840138 MB reclen bytes/sec written bytes/sec read (133Mhz) 4 512 1635305 19576771 4 8192 1656868 34723076 From owner-freebsd-hardware Thu Oct 12 08:44:24 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA19893 for hardware-outgoing; Thu, 12 Oct 1995 08:44:24 -0700 Received: from smokey.ee.washington.edu (smokey.ee.washington.edu [128.95.75.8]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA19877 ; Thu, 12 Oct 1995 08:44:17 -0700 Received: (from root@localhost) by smokey.ee.washington.edu (8.6.11/8.6.9) id IAA00754; Thu, 12 Oct 1995 08:44:15 -0700 Date: Thu, 12 Oct 1995 08:44:15 -0700 From: Clint Olsen Message-Id: <199510121544.IAA00754@smokey.ee.washington.edu> To: hardware@freebsd.org, questions@freebsd.org Subject: scsi(8) requested output here Sender: owner-hardware@freebsd.org Precedence: bulk Hello: # scsi -f /dev/rsd0c -c "12 0 0 0 64 0" -i 64 "s8 z8 z16 z4" SCIOCCOMMAND ioctl: Command accepted. host adapter status 2 Command out (6 of 6): 12 00 00 00 64 00 Data in (64 of 64): 00 00 01 01 27 12 00 00 43 44 43 20 20 20 20 20 # ....'...CDC 39 34 31 37 31 2d 39 20 20 20 20 20 20 20 20 20 # 94171-9 30 30 34 35 30 30 31 32 30 33 33 37 00 00 00 00 # 004500120337.... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 # ................ No sense sent. CDC 94171-9 0045 # scsi -f /dev/rsd1c -c "12 0 0 0 64 0" -i 64 "s8 z8 z16 z4" SCIOCCOMMAND ioctl: Command accepted. host adapter status 2 Command out (6 of 6): 12 00 00 00 64 00 Data in (64 of 64): 00 00 00 01 1f 12 00 00 45 4d 55 4c 45 58 20 20 # ........EMULEX 4d 44 32 31 2f 53 32 20 20 20 20 20 45 53 44 49 # MD21/S2 ESDI 41 30 30 20 00 00 00 00 00 00 00 00 00 00 00 00 # A00 ............ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 # ................ No sense sent. EMULEX MD21/S2 ESDI A00 Compare this to the resulting boot message from dmesg: aic0 at 0x340-0x35f irq 11 on isa aic0 waiting for scsi devices to settle (aic0:1:0): "CDC 94171-9 0045" type 0 fixed SCSI 1 sd0(aic0:1:0): Direct-Access 312MB (640584 512 byte sectors) (aic0:2:0): "unknown unknown ????" type 0 fixed SCSI 0 sd1(aic0:2:0): Direct-Access 312MB (640500 512 byte sectors) Note: o The ESDI disk has a SCSI translator on it (of sorts). Anyway, I looked at the driver source briefly, and it mentions some inherited ideas from Linux. Linux IS able to detect and speak/partition/newfs both drives. I'm concerned that these issues are keeping me from getting disklabel to work. I don't know what in the hell is going on. The commands to operate on the disk are not working for me. ******* Working on device /dev/rsd0 ******* parameters extracted from in-core disklabel are: cylinders=1549 heads=51 sectors/track=8 (408 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1549 heads=51 sectors/track=8 (408 blks/cyl) Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 0 is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 0, size 640584 (312 Meg), flag 80 beg: cyl 0/ sector 1/ head 0; end: cyl 311/ sector 8/ head 50 Running disklabel -e -r sd0 gives me this: Bad pack magic number (label is damaged, or pack is unlabeled) I'm running out of ideas. -Clint From owner-freebsd-hardware Thu Oct 12 11:05:47 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA23729 for hardware-outgoing; Thu, 12 Oct 1995 11:05:47 -0700 Received: (from hsu@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA23715 ; Thu, 12 Oct 1995 11:05:44 -0700 Date: Thu, 12 Oct 1995 11:05:44 -0700 From: Jeffrey Hsu Message-Id: <199510121805.LAA23715@freefall.freebsd.org> To: davidg Subject: Re: benchmark results Cc: batie@agora.rdrop.com, dyson@Root.COM, hardware@freebsd.org Sender: owner-hardware@freebsd.org Precedence: bulk > "CORBIN" kernel make: > 432.518u 53.907s 8:14.79 98.3% 1046+1271k 13+505io 0pf+0w (90Mhz-async) > 347.405u 28.275s 6:23.66 97.9% 1006+1293k 14+497io 0pf+0w (90Mhz) > 260.303u 27.605s 5:00.20 95.9% 1043+1264k 52+480io 0pf+0w (133Mhz) ^^ I don't supposed there's not much that can be done about blocked reads other than to run multiple compiles in parallel to keep the processor busy while it would otherwise be read blocked? From owner-freebsd-hardware Fri Oct 13 01:26:00 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA20337 for hardware-outgoing; Fri, 13 Oct 1995 01:26:00 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA20317 ; Fri, 13 Oct 1995 01:25:49 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id SAA18626; Fri, 13 Oct 1995 18:26:32 +0930 From: Michael Smith Message-Id: <199510130856.SAA18626@genesis.atrad.adelaide.edu.au> Subject: Re: scsi(8) requested output here To: olsenc@smokey.ee.washington.edu (Clint Olsen) Date: Fri, 13 Oct 1995 18:26:31 +0930 (CST) Cc: hardware@FreeBSD.ORG, questions@FreeBSD.ORG In-Reply-To: <199510121544.IAA00754@smokey.ee.washington.edu> from "Clint Olsen" at Oct 12, 95 08:44:15 am Content-Type: text Content-Length: 788 Sender: owner-hardware@FreeBSD.ORG Precedence: bulk Clint Olsen stands accused of saying: > Running disklabel -e -r sd0 gives me this: > > Bad pack magic number (label is damaged, or pack is unlabeled) This has nothing to do with the MD21; you can't edit a disklabel if there isn't one there yet. You'll have to write one out first. disklabel -w -r sd0 Pick a label at random from /etc/disktab, and then use disklabel -e to correct it. > -Clint -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[ From owner-freebsd-hardware Fri Oct 13 03:56:32 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA25649 for hardware-outgoing; Fri, 13 Oct 1995 03:56:32 -0700 Received: from pancake.remcomp.fr (pancake.remcomp.fr [194.51.30.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id DAA25636 for ; Fri, 13 Oct 1995 03:54:59 -0700 Received: from zapata.omnix.fr.org (zapata.omnix.fr.org [128.127.10.1]) by zapata.omnix.fr.org (8.6.9/8.6.9) with SMTP id MAA03115; Fri, 13 Oct 1995 12:26:05 +0100 Date: Fri, 13 Oct 1995 12:26:05 +0100 (MET) From: Didier Derny To: David Greenman cc: hardware@FreeBSD.org, dyson@root.com, batie@agora.rdrop.com Subject: Re: benchmark results In-Reply-To: <199510121256.FAA00163@corbin.Root.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@FreeBSD.org Precedence: bulk is it possible to find the programs used to make these benchmarks. I've recently tested the AMD 486DX4-120 with dhrystone 1.1 and I get 141000 dhrystones / secondes. +---------------------+ | Didier Derny | | didier@omnix.fr.org | +---------------------+ On Thu, 12 Oct 1995, David Greenman wrote: > Attached are the results of some benchmark comparisons between similar > systems. All of the machines have Triton chipset based motherboards, so the > only significant difference is async/pipeline-burst cache and the CPU speed. > > -DG > > 90Mhz-async: > ASUS PCI/I-P54TP4, 32MB RAM, 256k async cache, Pentium 90Mhz > FreeBSD-2.1-stable (Oct. 9th) > > 90Mhz: > ASUS P/I-P55TP4XE, 64MB RAM, 256K pipeline-burst cache, Pentium 90Mhz > FreeBSD-current (Oct. 10th) > > 133Mhz: > ASUS P/I-P55TP4XE, 64MB RAM, 256K pipeline-burst cache, Pentium 133Mhz > FreeBSD-2.0.5-RELEASE > > Note that on the 90Mhz machine, the source being compiled is 2.1-stable, > which should be very similar (in time) to the source in 2.0.5-RELEASE. > -pipe was used in all cases. All tests done twice (and the second time > was used) to make sure that everything was cached. > > "CORBIN" kernel make depend: > 46.100u 18.674s 1:05.98 98.1% 105+657k 7+51io 0pf+0w (90Mhz-async) > 44.291u 11.232s 0:56.38 98.4% 101+535k 7+49io 0pf+0w (90Mhz) > 29.265u 9.772s 0:39.94 97.7% 104+659k 3+41io 0pf+0w (133Mhz) > > "CORBIN" kernel make: > 432.518u 53.907s 8:14.79 98.3% 1046+1271k 13+505io 0pf+0w (90Mhz-async) > 347.405u 28.275s 6:23.66 97.9% 1006+1293k 14+497io 0pf+0w (90Mhz) > 260.303u 27.605s 5:00.20 95.9% 1043+1264k 52+480io 0pf+0w (133Mhz) > > For the following, the same (-static) binary was used within each test set. > > dry: > (-O -finline-functions -fomit-frame-pointer) > Dhrystone(1.1) time for 500000 passes = 3 (90Mhz-async) > This machine benchmarks at 157248 dhrystones/second > 3.184u 0.015s 0:03.31 96.3% 48+213k 0+0io 0pf+0w > > Dhrystone(1.1) time for 500000 passes = 3 (90Mhz) > This machine benchmarks at 159203 dhrystones/second > 3.159u 0.007s 0:03.16 99.6% 46+206k 0+0io 0pf+0w > > Dhrystone(1.1) time for 500000 passes = 2 (133Mhz) > This machine benchmarks at 230215 dhrystones/second > 2.175u 0.007s 0:02.18 99.5% 47+207k 0+0io 0pf+0w > > ttcp: > [implode:davidg] ttcp -p9 -n16384 -t localhost (90Mhz-async) > ttcp-t: buflen=8192, nbuf=16384, align=16384/+0, port=9 tcp -> localhost > ttcp-t: socket > ttcp-t: connect > ttcp-t: 134217728 bytes in 16.76 real seconds = 7822.28 KB/sec +++ > ttcp-t: 16384 I/O calls, msec/call = 1.05, calls/sec = 977.79 > ttcp-t: 0.1user 7.0sys 0:16real 42% 40i+247d 68maxrss 0+2pf 7244+1594csw > 0.120u 7.045s 0:16.77 42.6% 40+247k 0+0io 0pf+0w > > [corbin:davidg] ttcp -p9 -n16384 -t localhost (90Mhz) > ttcp-t: buflen=8192, nbuf=16384, align=16384/+0, port=9 tcp -> localhost > ttcp-t: socket > ttcp-t: connect > ttcp-t: 134217728 bytes in 12.49 real seconds = 10495.37 KB/sec +++ > ttcp-t: 16384 I/O calls, msec/call = 0.78, calls/sec = 1311.92 > ttcp-t: 0.1user 5.6sys 0:12real 46% 42i+275d 98maxrss 0+2pf 5443+4471csw > 0.175u 5.693s 0:12.50 46.8% 42+275k 0+0io 0pf+0w > > [pyrex:davidg] ttcp -p9 -n16384 -t localhost (133Mhz) > ttcp-t: buflen=8192, nbuf=16384, align=16384/+0, port=9 tcp -> localhost > ttcp-t: socket > ttcp-t: connect > ttcp-t: 134217728 bytes in 9.31 real seconds = 14071.71 KB/sec +++ > ttcp-t: 16384 I/O calls, msec/call = 0.58, calls/sec = 1758.96 > ttcp-t: 0.0user 4.4sys 0:09real 49% 41i+267d 46maxrss 0+2pf 4445+6338csw > > iozone: > (We're only interested in the cache read performance) > MB reclen bytes/sec written bytes/sec read (90Mhz-async) > 4 512 2085319 12761286 > 4 8192 2127731 24353765 > > MB reclen bytes/sec written bytes/sec read (90Mhz) > 4 512 2235863 15093178 > 4 8192 2455878 31840138 > > MB reclen bytes/sec written bytes/sec read (133Mhz) > 4 512 1635305 19576771 > 4 8192 1656868 34723076 > From owner-freebsd-hardware Sat Oct 14 11:39:37 1995 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA14709 for hardware-outgoing; Sat, 14 Oct 1995 11:39:37 -0700 Received: from dsw.com (root@gate.dsw.com [206.43.0.254]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA14699 for ; Sat, 14 Oct 1995 11:39:34 -0700 Received: from dsw.dsw.com by dsw.com (8.6.12) id MAA17545; Sat, 14 Oct 1995 12:39:32 -0600 Date: Sat, 14 Oct 1995 12:39:31 -0600 (MDT) From: Pete Kruckenberg To: hardware@freebsd.org, hackers@freefall.freebsd.org Subject: Memory upgrade problems w/ 2.0.5R Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org Precedence: bulk Last night, I attempted to upgrade my FreeBSD 2.0.5R news/Web server from 64 to 96MB. It ended in slight disaster. I wanted to find out if I missed something critical, or if one or both of my SIMMs might have been bad. Here's what I did: modified my conf file with 'options MEMMAX="98304"', then rebuilt the kernel when building the kernel, I use optimizations (gcc 2.6.3): -O2 -m486 -fomit-frame-pointer -pipe The system is a Pentium 75 (AMI BIOS, I think) with an Adaptec 2940 PCI controller, VGA controller, 2 SCSI (Barracuda) 4GB drives. After I installed the new kernel, things came up just fine, but after maybe 10-20 minutes, the machine would crash and reboot, with a message like: /kernel: Fatal trap 12: page fault while in kernel mode /kernel: fault virtual address = 0xf1a6a814 /kernel: fault code = supervisor read, page not present /kernel: instruction pointer = 0x8:0xf019e735 /kernel: code segment = base 0x0, limit 0xfffff, type 0x1b /kernel: = DPL 0, pres 1, def32 1, gran 1 /kernel: processor eflags = interrupt enabled, resume, IOPL = 0 /kernel: current process = 670 (innd) /kernel: interrupt mask = /kernel: panic: page fault /kernel: /kernel: syncing disks... 53 53 48 39 27 10 done /kernel: Automatic reboot in 15 seconds - press a key on the console to abort /kernel: Rebooting... This happened a couple other times with the current process = Idle, but those times, the disks didn't sync (I just got timeouts), so there was no record in /var/log/messages. So, would this indicate a hardware problem, or a software problem, or what? I'm a little hesitant to try this again until I know how to avoid it. As soon as 2.1 comes out, I'll probably upgrade the OS, but I would like to bump it up to 96MB now, if possible. Thanks for your input. Pete Kruckenberg pete@dsw.com