From owner-freebsd-hardware Sun Nov 24 09:54:18 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA00972 for hardware-outgoing; Sun, 24 Nov 1996 09:54:18 -0800 (PST) Received: from ki1.chemie.fu-berlin.de (ki1.Chemie.FU-Berlin.DE [160.45.24.21]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA00936 for ; Sun, 24 Nov 1996 09:53:54 -0800 (PST) Received: by ki1.chemie.fu-berlin.de (Smail3.1.28.1) from mail.hanse.de (193.174.9.9) with smtp id ; Sun, 24 Nov 96 18:53 MET Received: by mail.hanse.de with UUCP for hardware@freebsd.org id ; Sun, 24 Nov 96 18:53 MET Received: (from chris@localhost) by wolfhh.hanse.de (8.7.5/8.7.3) id RAA01611 for hardware@freebsd.org; Sun, 24 Nov 1996 17:47:09 +0100 (MET) From: Christian Wolf Message-Id: <199611241647.RAA01611@wolfhh.hanse.de> Subject: FreeBSD on Intel 386EX based embedded PC104 board? To: hardware@freebsd.org Date: Sun, 24 Nov 1996 17:47:08 +0100 (MET) Reply-To: chris@wolfhh.hanse.de X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello! The subject says it all. I would like to run FreeBSD on a Intel 386EX based PC104 embedded PC. The board also has a ``Crystal CS8900'' ethernet chip on board. Does onyone know this one? Chris -- Christian Wolf, Hamburg, Germany; +49 40 76750003; chris@wolfhh.hanse.de From owner-freebsd-hardware Sun Nov 24 12:04:27 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA09036 for hardware-outgoing; Sun, 24 Nov 1996 12:04:27 -0800 (PST) Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [131.155.210.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA08991; Sun, 24 Nov 1996 12:04:15 -0800 (PST) Received: (from guido@localhost) by gvr.win.tue.nl (8.8.2 with smtp patch/8.8.2) id VAA00708; Sun, 24 Nov 1996 21:03:48 +0100 (MET) From: Guido van Rooij Message-Id: <199611242003.VAA00708@gvr.win.tue.nl> Subject: Re: 3C900 - 3C590 - 3C595 - SMC and PCI ethernet cards ??? In-Reply-To: <199611221456.RAA23985@megillah.demos.su> from "Mikhail A. Sokolov" at "Nov 22, 96 05:56:56 pm" To: mishania@demos.su Date: Sun, 24 Nov 1996 21:03:48 +0100 (MET) Cc: mango@communique.net, freebsd-questions@freefall.freebsd.org, hardware@freefall.freebsd.org, bag@demos.su X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Mikhail A. Sokolov wrote: > > Raul Zighelboim wrote: > > > Questions: > > > What PCI Ethernet card is solid and has good support under FBSD? > > > Is it possible to get this 3C900 card working under 2.1.5 ? > There doesn't exist _good_ driver in 2.1.5r, 2.1.6r for 3c590/595, but there > is _good_ and even working driver in -current tree/2.2-ALPHA tree. > Not true. The one in 2.1.6 is the same as the on in -current. The one in 2.1.5 is indeed broken. Therefor I mentioned where to find a replacement,, -Guido From owner-freebsd-hardware Sun Nov 24 16:14:35 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA21938 for hardware-outgoing; Sun, 24 Nov 1996 16:14:35 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA21930 for ; Sun, 24 Nov 1996 16:14:26 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id KAA25985; Mon, 25 Nov 1996 10:44:07 +1030 (CST) From: Michael Smith Message-Id: <199611250014.KAA25985@genesis.atrad.adelaide.edu.au> Subject: Re: FreeBSD on Intel 386EX based embedded PC104 board? In-Reply-To: <199611241647.RAA01611@wolfhh.hanse.de> from Christian Wolf at "Nov 24, 96 05:47:08 pm" To: chris@wolfhh.hanse.de Date: Mon, 25 Nov 1996 10:44:06 +1030 (CST) Cc: hardware@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Christian Wolf stands accused of saying: > > The subject says it all. I would like to run FreeBSD on a Intel 386EX > based PC104 embedded PC. The board also has a ``Crystal CS8900'' ethernet > chip on board. Does onyone know this one? I don't know much about the EX, so I don't know if there are any catches there. There's no driver for the CS8900 at this time. I didn't have any trouble getting a datasheet for it from Crystal; I'd expect that you could do likewise easily. If you're not in a position to produce a driver, but would be willing to contract for same, let me know. > Chris -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Mon Nov 25 05:59:05 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA17982 for hardware-outgoing; Mon, 25 Nov 1996 05:59:05 -0800 (PST) Received: from cenotaph.snafu.de (root@gw-deadnet.snafu.de [194.121.229.33]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA17967 for ; Mon, 25 Nov 1996 05:58:54 -0800 (PST) Received: by cenotaph.snafu.de from deadline.snafu.de using smtp id m0vS1Yd-000ZjTC; Mon, 25 Nov 1996 14:58:47 +0100 (MET) (Smail-3.2 1996-Jul-4 #1) Received: by deadline.snafu.de id m0vS1Ya-00080FC; Mon, 25 Nov 1996 14:58:44 +0100 (MET) (Smail-3.2 1996-Jul-4 #1) Message-Id: From: mickey@deadline.snafu.de (Andreas S. Wetzel) Subject: NS16650 or NS16750 support for sio code ? To: hardware@freebsd.org Date: Mon, 25 Nov 1996 14:58:44 +0100 (MET) Organization: -D-E-A-D-L-I-N-E- Public access UN*X system, 13347 Berlin (WEST). X-Mailer: ELM [version 2.4ME+ PL13] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi! --- Does anybody out there know, if the NS 16650 and NS 16750 UARTS (32/64 byte FIFO) are currently supported by the FreeBSD sio code? Thanks in advance Mickey -- (__) (@@) Andreas S. Wetzel E-mail: mickey@deadline.snafu.de /-------\/ Utrechter Strasse 41 Web: http://deadline.snafu.de/ / | || 13347 Berlin Voice: <+4930> 456 81 68 * ||----|| Germany Fax/Data: <+4930> 455 19 57 ~~ ~~ From owner-freebsd-hardware Mon Nov 25 08:09:40 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA00437 for hardware-outgoing; Mon, 25 Nov 1996 08:09:40 -0800 (PST) Received: from Guard.PolyNet.Lviv.UA (Guard.PolyNet.Lviv.UA [194.44.138.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA29290 for ; Mon, 25 Nov 1996 08:02:52 -0800 (PST) Received: (from smap@localhost) by Guard.PolyNet.Lviv.UA (8.7.5/8.6.12) id SAA14258 for ; Mon, 25 Nov 1996 18:01:17 +0200 (EET) Received: from netsurfer.lp.lviv.ua(192.168.0.3) by Guard.Polynet.Lviv.UA via smap (V2.0beta) id xma014256; Mon, 25 Nov 96 18:00:53 +0200 Received: (from smap@localhost) by NetSurfer.lp.lviv.ua (8.6.12/8.6.12) id SAA08086 for ; Mon, 25 Nov 1996 18:00:52 +0200 Message-Id: <199611251600.SAA08086@NetSurfer.lp.lviv.ua> Received: from ws6.lp.lviv.ua(192.168.0.37) by NetSurfer.lp.lviv.ua via smap (V2.0beta) id xma008081; Mon, 25 Nov 96 18:00:44 +0200 Comments: Authenticated sender is From: "Slavik Terletsky" Organization: State University "Lvivska Polytechnika" To: FreeBSD-hardware@FreeBSD.org Date: Mon, 25 Nov 1996 18:01:49 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Help: Watchdog Problem Reply-to: ts@polynet.lviv.ua Priority: normal X-mailer: Pegasus Mail for Windows (v2.42a) Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi I have PC (PCA-6157) with WatchDog Feature. PC uses Pentium P54C type 75/90/100/120/133/150 MHz CPU and 82437FX "Triton" chipset,works with standard ISA and/or ISA/PCI bus. WatchDog works this way: The first time the watchdog-soft reads the ENABLE(0x443) port, it enables the watchdog timer. After that the soft must read the ENABLE port at time interval less then 1.6 sec, otherwise the watchdog timer will acvtivate and reset CPU. To disable watchdog timer the soft shoud read DISABLE(0x043) port. I'v written such soft (attached below) and seems it shoud work, but it don't. Question: can anyone say how can i find out why FreeBSD and WatchDog conflicts? Maybe FreeBSD has some codes which read DISABLE port? I'v checked kernel conf and there is no dev listed to read this port. P.S. WatchDog works under DOS. %%%%%%%%%%%%%%%%% CUT HERE %%%%%%%%%%%%%%%%%%% #include #include #include #include #include #define TIME 1 #define ENABLE 0x443 #define DISABLE 0x043 void disable(); extern int errno; int pd; FILE *fd; unsigned char c; int main(int argc, char *argv[]) { fd = fopen("/var/run/watchdog.pid","r"); if(fd) { fprintf(stderr,"watchdog: /var/run/watchdog.pid: File exists\n"); exit(1); } pd = open("/dev/io",O_RDONLY); /* allow i/o operations */ if(pd < 0) { perror("watchdog: can't open /dev/io"); exit(1); } fd = fopen("/var/run/watchdog.pid","w"); if(!fd) { perror("watchdog: /var/run/watchdog.pid"); exit(1); } switch(fork()) { case -1: /* fork() error */ perror("watchdog"); exit(1); case 0: /* child */ fprintf(fd,"%d\n",(int)getpid()); fclose(fd); (void)signal(SIGTERM,disable); while(1) { c = inbv(ENABLE); sleep(TIME); } default: /* parent */ fprintf(stdout,"WatchDog Enabled\n"); close(pd); fclose(fd); exit(0); } } void disable() { /* disable watchdog while exit */ c = inbv(DISABLE); fprintf(stdout,"WatchDog Disabled\n"); if(unlink("/var/run/watchdog.pid") < 0) { perror("watchdog: /var/run/watchdog.pid"); exit(1); } close(pd); exit(0); } %%%%%%%%%%%%%%%%% CUT HERE %%%%%%%%%%%%%%%%%%% # Slavik Terletsky # University "Lvivska Poytechnika" # # Network Administrator # mailto:ts@polynet.lviv.ua # From owner-freebsd-hardware Tue Nov 26 21:42:40 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA28434 for hardware-outgoing; Tue, 26 Nov 1996 21:42:40 -0800 (PST) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA28409 for ; Tue, 26 Nov 1996 21:42:02 -0800 (PST) Received: from easy.stallion.com by mail.crl.com with SMTP id AA28902 (5.65c/IDA-1.5 for ); Tue, 26 Nov 1996 20:32:29 -0800 Received: from cluster.stallion.oz.au by easy.stallion.com id aa17308; 26 Nov 96 20:29 PST Subject: Re: FreeBSD as Terminal Server To: hardware@freebsd.org Date: Wed, 27 Nov 1996 14:22:26 +1000 (est) From: Greg Ungerer Cc: alex@yahoo.com, sos@ravenock.cybercity.dk, bde@zeta.org.au, Greg Ungerer , sysseh@devetir.qld.gov.au X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <9611271422.aa01993@cluster.stallion.oz.au> Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hiya All, Sorry for the late response on this... (Hopefully the following attributions are correct, sorry if not :-) Bruce Evans writes: >>In reply to Alexander Winske who wrote: >>> Howdy, >>> I'm looking to set up a largish terminal server on >>> a FreeBSD box. (I want to log console output and allow >>> console sessions with approx. 75-100 hosts). >>> >>> Can anyone out there recommend a flavor of multiport >>> serial card that will allow me to have that many ports? >>> I would think that they wouldn't have to be doing more than >>> 2400 baud each, if that makes any difference... > >3 * 32-port Cyclades boards should work OK at such a low speed, >but are very expensive (list prices are US$1328 for a 32Ye (ISA) >and $1537 for a 32YeP (PCI). Discount prices seem to be slightly >more than half the list prices). > >>Look at some of the newer Stallion boards, I think they support >>upto 64 ports per card, so two of them should have you >>rolling. Yeah that is right. The EasyConnection 8/64 can do up to 64 ports per bus slot (ISA, EISA, and MCA buses supported). The EasyConnection 8/32 PCI board will also go up to 64 ports (don't you just love the names marketing comes up with ;-). The 8/64 is a real intelligent board with off-board CPU and large buffer memory so perforamce tends to be very good. It does not use interrupts to the host, so host overhead tends to be very low too. 64 ports at 2400 baud won't even start to work it hard. >You'd need to translate the istallion driver from the Linlish :-). Huh?? What do you mean? How mush more FreeBSDish can it be made? >The current version is too green to use. It disables interrupts >and calls tsleep() :-(. I would hardly call it green, people have been using them very happily for more than a year now... > >I did a quick check for drivers in isa/*.c that abuse disable_intr() >and found these: > >ctx.c: disables interrupts and calls uiomove(). Apart from disabling [driver list sniped] Did you let of the maintainers of these drivers know so they could "fix" up the problem? In any case this is very easy to "fix" for the Stallion drivers. If you look at a lot of the cases of the disabled interrupts they are turned off for no more than a couple of dozen instructions... Regards Greg --------------------------------------------------------------------------- Greg Ungerer EMAIL: gerg@stallion.com Stallion Technologies Pty Ltd PHONE: +61 7 3270 4271 33 Woodstock Rd, Toowong, QLD 4066, Australia FAX: +61 7 3270 4245 From owner-freebsd-hardware Wed Nov 27 13:42:24 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA14506 for hardware-outgoing; Wed, 27 Nov 1996 13:42:24 -0800 (PST) Received: from mailhost.yahoo.com (mailhost.yahoo.com [205.216.162.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA14498 for ; Wed, 27 Nov 1996 13:42:21 -0800 (PST) Received: from honker.yahoo.com (honker.yahoo.com [205.216.162.77]) by mailhost.yahoo.com (8.6.12/8.6.12) with ESMTP id NAA15782; Wed, 27 Nov 1996 13:42:20 -0800 Received: (from alex@localhost) by honker.yahoo.com (8.6.12/8.6.9) id NAA06470; Wed, 27 Nov 1996 13:41:48 -0800 Date: Wed, 27 Nov 1996 13:41:48 -0800 Message-Id: <199611272141.NAA06470@honker.yahoo.com> From: Alexander Winske To: gerg@stallion.oz.au CC: hardware@freebsd.org In-reply-to: <9611271422.aa01993@cluster.stallion.oz.au> (message from Greg Ungerer on Wed, 27 Nov 1996 14:22:26 +1000 (est)) Subject: Re: FreeBSD as Terminal Server Reply-To: alex@yahoo.com Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, I ended up getting the Cyclades boards, and when I get everything wired up I'll let you know if there are any big reasons *not* to use them.... Alex > > > Hiya All, > > Sorry for the late response on this... > (Hopefully the following attributions are correct, sorry if not :-) > > Bruce Evans writes: > >>In reply to Alexander Winske who wrote: > >>> Howdy, > >>> I'm looking to set up a largish terminal server on > >>> a FreeBSD box. (I want to log console output and allow > >>> console sessions with approx. 75-100 hosts). > >>> > >>> Can anyone out there recommend a flavor of multiport > >>> serial card that will allow me to have that many ports? > >>> I would think that they wouldn't have to be doing more than > >>> 2400 baud each, if that makes any difference... > > > >3 * 32-port Cyclades boards should work OK at such a low speed, > >but are very expensive (list prices are US$1328 for a 32Ye (ISA) > >and $1537 for a 32YeP (PCI). Discount prices seem to be slightly > >more than half the list prices). > > > >>Look at some of the newer Stallion boards, I think they support > >>upto 64 ports per card, so two of them should have you > >>rolling. > > Yeah that is right. The EasyConnection 8/64 can do up to 64 ports > per bus slot (ISA, EISA, and MCA buses supported). The EasyConnection > 8/32 PCI board will also go up to 64 ports (don't you just love > the names marketing comes up with ;-). > > The 8/64 is a real intelligent board with off-board CPU and large > buffer memory so perforamce tends to be very good. It does not use > interrupts to the host, so host overhead tends to be very low too. > 64 ports at 2400 baud won't even start to work it hard. > > > >You'd need to translate the istallion driver from the Linlish :-). > > Huh?? > What do you mean? > How mush more FreeBSDish can it be made? > > > >The current version is too green to use. It disables interrupts > >and calls tsleep() :-(. > > I would hardly call it green, people have been using them very happily > for more than a year now... > > > > > >I did a quick check for drivers in isa/*.c that abuse disable_intr() > >and found these: > > > >ctx.c: disables interrupts and calls uiomove(). Apart from disabling > [driver list sniped] > > Did you let of the maintainers of these drivers know so they could > "fix" up the problem? > > In any case this is very easy to "fix" for the Stallion drivers. If you > look at a lot of the cases of the disabled interrupts they are turned off > for no more than a couple of dozen instructions... > > Regards > Greg > > > --------------------------------------------------------------------------- > Greg Ungerer EMAIL: gerg@stallion.com > Stallion Technologies Pty Ltd PHONE: +61 7 3270 4271 > 33 Woodstock Rd, Toowong, QLD 4066, Australia FAX: +61 7 3270 4245 > From owner-freebsd-hardware Wed Nov 27 14:25:29 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA17029 for hardware-outgoing; Wed, 27 Nov 1996 14:25:29 -0800 (PST) Received: from tibet.stepnet.com ([206.14.120.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA17024 for ; Wed, 27 Nov 1996 14:25:26 -0800 (PST) Received: (from ping@localhost) by tibet.stepnet.com (8.7.6/8.7.3) id OAA03804 for freebsd-hardware@freebsd.org; Wed, 27 Nov 1996 14:24:42 -0800 (PST) From: Ping Mai Message-Id: <199611272224.OAA03804@tibet.stepnet.com> Subject: motherboard and case recommandation To: freebsd-hardware@freebsd.org Date: Wed, 27 Nov 1996 14:24:42 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi All, Please recommand a P5 motherboard and a good case for a fbsd system. I have been looking at the Asus p55t2p4d and the xp55t2p4, but I can not find any local shop that have them in stock. Please recommand a place where these boards can be found. Many Thanks in advance, ------------------------------------------------------------ Steps Network Solutions, Inc. Ping Mai ping@stepnet.com ------------------------------------------------------------ Work keeps away three great evils: boredom, vice, and need. - Voltaire From owner-freebsd-hardware Wed Nov 27 14:44:26 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA18643 for hardware-outgoing; Wed, 27 Nov 1996 14:44:26 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA18635 for ; Wed, 27 Nov 1996 14:44:21 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id JAA32072; Thu, 28 Nov 1996 09:36:12 +1100 Date: Thu, 28 Nov 1996 09:36:12 +1100 From: Bruce Evans Message-Id: <199611272236.JAA32072@godzilla.zeta.org.au> To: gerg@stallion.oz.au, hardware@FreeBSD.ORG Subject: Re: FreeBSD as Terminal Server Cc: alex@yahoo.com, bde@zeta.org.au, sos@ravenock.cybercity.dk, sysseh@devetir.qld.gov.au Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>You'd need to translate the istallion driver from the Linlish :-). > >Huh?? >What do you mean? >How mush more FreeBSDish can it be made? plainBSDish: use spltty() to disable tty interrupts. Never use disable_interrupt(), which doesn't exist exist in plainBSD. FreeBSDish: use only spltty() as in plainBSD, unless the driver uses a fast interrupt handler. Fast interrupt handlers are harder to program, so they should only be used if an interrupt latency of less than about 10 ms is required. E.g., for a serial driver at 115200 bps, a fast interrupt handler should be used if the receiver fifo size is smaller than about 128. There are several sources of huge interrupt latency in FreeBSD. E.g., tty interrupts are masked for 2-5 ms while the keyboard LEDs are being programmed. `bio' (disk) interrupts may preempt non-fast tty interrupt handlers and run for as long as 20 ms to transfer 64K of data to a slow MFM/IDE disk. >>The current version is too green to use. It disables interrupts >>and calls tsleep() :-(. > >I would hardly call it green, people have been using them very happily >for more than a year now... I think it works because tsleep() normally calls cpu_switch() and cpu_switch() happens to enable interrupts. >>I did a quick check for drivers in isa/*.c that abuse disable_intr() >>and found these: >> >>ctx.c: disables interrupts and calls uiomove(). Apart from disabling >[driver list sniped] > >Did you let of the maintainers of these drivers know so they could >"fix" up the problem? These drivers are mostly apparently unmaintained :=]. >In any case this is very easy to "fix" for the Stallion drivers. If you >look at a lot of the cases of the disabled interrupts they are turned off >for no more than a couple of dozen instructions... Yes, that is safe. To be sure that they are not turned off for longer, don't call any function outside the driver, since the implementation of foreign functions is unknown and may change. Foreign functions may execute thousands of instructions or reenable interrupts. Bruce From owner-freebsd-hardware Wed Nov 27 18:15:27 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA29385 for hardware-outgoing; Wed, 27 Nov 1996 18:15:27 -0800 (PST) Received: from george.lbl.gov (george-2.lbl.gov [131.243.2.12]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA29378 for ; Wed, 27 Nov 1996 18:15:25 -0800 (PST) Received: (jin@localhost) by george.lbl.gov (8.6.10/8.6.5) id SAA12838; Wed, 27 Nov 1996 18:15:19 -0800 Date: Wed, 27 Nov 1996 18:15:19 -0800 From: "Jin Guojun[ITG]" Message-Id: <199611280215.SAA12838@george.lbl.gov> To: freebsd-hardware@FreeBSD.org, ping@stepnet.com Subject: Re: motherboard and case recommandation Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Please recommand a P5 motherboard and a good case for a fbsd system. > > I have been looking at the Asus p55t2p4d and the xp55t2p4, but I can > not find any local shop that have them in stock. Please recommand > a place where these boards can be found. > > Many Thanks in advance, > > ------------------------------------------------------------ > Steps Network Solutions, Inc. Ping Mai > ping@stepnet.com > ------------------------------------------------------------ The problem is "where is your local?" From owner-freebsd-hardware Wed Nov 27 19:08:12 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA00877 for hardware-outgoing; Wed, 27 Nov 1996 19:08:12 -0800 (PST) Received: from superior.truenorth.org (ppp021-sm2.sirius.com [205.134.231.21]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA00871 for ; Wed, 27 Nov 1996 19:08:05 -0800 (PST) Received: (from jgrosch@localhost) by superior.truenorth.org (8.7.5/8.7.3) id TAA07336; Wed, 27 Nov 1996 19:06:53 -0800 (PST) From: Josef Grosch Message-Id: <199611280306.TAA07336@superior.truenorth.org> Subject: Re: motherboard and case recommandation To: ping@stepnet.com (Ping Mai) Date: Wed, 27 Nov 1996 19:06:52 -0800 (PST) Cc: freebsd-hardware@FreeBSD.org Reply-To: jgrosch@sirius.com In-Reply-To: <199611272224.OAA03804@tibet.stepnet.com> from Ping Mai at "Nov 27, 96 02:24:42 pm" X-Mailer: ELM [version 2.4ME+ PL13 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Hi All, > >Please recommand a P5 motherboard and a good case for a fbsd system. > >I have been looking at the Asus p55t2p4d and the xp55t2p4, but I can >not find any local shop that have them in stock. Please recommand >a place where these boards can be found. > >Many Thanks in advance, > >------------------------------------------------------------ >Steps Network Solutions, Inc. Ping Mai > ping@stepnet.com >------------------------------------------------------------ >Work keeps away three great evils: boredom, vice, and need. > - Voltaire > Since Whois tells me that stepnet.com is in the Bay Area, I assume you are also. I can recomend the Asus P55t2p4. Mine has given me no trouble since I installed it severl months ago. I have had good luck with Central Computer (http://www.centralcomputer.com). Their prices are reasonable and no BS unlike my favorite place to hate, Fry's. Josef -- Josef Grosch | Laugh while you can, monkey boy ! | FreeBSD 2.1.5 jgrosch@sirius.com | - John Warfin - | UNIX for the masses From owner-freebsd-hardware Fri Nov 29 20:30:42 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA22753 for hardware-outgoing; Fri, 29 Nov 1996 20:30:42 -0800 (PST) Received: from kaori.communique.net (kaori.Communique.Net [204.27.65.55]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA22729; Fri, 29 Nov 1996 20:30:35 -0800 (PST) Received: by kaori.communique.net with Microsoft Exchange (IMC 4.0.837.3) id <01BBDE44.9BB3E0E0@kaori.communique.net>; Fri, 29 Nov 1996 22:28:13 -0600 Message-ID: From: Raul Zighelboim To: "'hackers@freefall.freebsd.org'" Cc: "'hardware@freefall.freebsd.org'" Subject: Adaptec UW controller and Seagate Elite performance ? Date: Fri, 29 Nov 1996 22:28:12 -0600 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.837.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk .0 Hello there! My system is not performing as expected. Trying to find out were the bottleneck is, I run Bonnie and iozone benchmarks on the system while no i/o processes were running. I got the following results: # bonnie -s 40 (akira, http running) -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 40 3271 34.8 3085 13.0 1559 8.3 10330 97.1 44763 95.7 991.0 20.4 and IOZONE performance measurements: 2039008 bytes/second for writing the file 34861747 bytes/second for reading the file It bothered me that: 1- reading is 20 times faster than writing 2- 2Mbytes/s for writing seems slow, even if this was a scsi-2 and not an scsi fast and wide drive. Are this results the expected values for a UW scsi drive/controller ?, and if not, can someone point me in the correct direction to get this resolved ? Thanks. ------------------------ ------------------------ Raul Zighelboim Communique Inc. mailto:mango@communique.net http://www.communique.net From owner-freebsd-hardware Fri Nov 29 20:44:24 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA23290 for hardware-outgoing; Fri, 29 Nov 1996 20:44:24 -0800 (PST) Received: from dyson.iquest.net ([198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA23285; Fri, 29 Nov 1996 20:44:21 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id XAA09675; Fri, 29 Nov 1996 23:44:09 -0500 (EST) From: "John S. Dyson" Message-Id: <199611300444.XAA09675@dyson.iquest.net> Subject: Re: Adaptec UW controller and Seagate Elite performance ? To: mango@staff.communique.net (Raul Zighelboim) Date: Fri, 29 Nov 1996 23:44:08 -0500 (EST) Cc: hackers@freefall.freebsd.org, hardware@freefall.freebsd.org In-Reply-To: from "Raul Zighelboim" at Nov 29, 96 10:28:12 pm X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > # bonnie -s 40 (akira, http running) > -------Sequential Output-------- ---Sequential Input-- --Random-- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- > MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU > 40 3271 34.8 3085 13.0 1559 8.3 10330 97.1 44763 95.7 991.0 20.4 > > and > IOZONE performance measurements: > 2039008 bytes/second for writing the file > 34861747 bytes/second for reading the file > > It bothered me that: > 1- reading is 20 times faster than writing You are seeing the results of caching. The system remembers what is written so that it doesn't have to unnecessarily re-read the data. > > 2- 2Mbytes/s for writing seems slow, even if this was a scsi-2 and not > an > scsi fast and wide drive. > I don't know why your iozone write perf is so slow, unless you are writing 512 bytes at a time. Note also, that you might not have the write behind caching enabled on your drive. Try the following commands: # iozone auto and # iozone 40 8192 and # iozone 8192 and let me know the results. John dyson@freebsd.org From owner-freebsd-hardware Fri Nov 29 21:06:23 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA24037 for hardware-outgoing; Fri, 29 Nov 1996 21:06:23 -0800 (PST) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA24032 for ; Fri, 29 Nov 1996 21:06:21 -0800 (PST) From: BRETT_GLASS@infoworld.com Received: from ccgate.infoworld.com (ccgate.infoworld.com [192.216.49.101]) by lserver.infoworld.com (8.8.3/8.7.3/GNAC-GW-1.2) with SMTP id VAA24304 for ; Fri, 29 Nov 1996 21:06:20 -0800 (PST) Received: from ccMail by ccgate.infoworld.com (SMTPLINK V2.11) id AA849330036; Fri, 29 Nov 96 21:55:47 PST Date: Fri, 29 Nov 96 21:55:47 PST Message-Id: <9610298493.AA849330036@ccgate.infoworld.com> To: hardware@freebsd.org Subject: Support for Lucent WaveLAN (ISA, not mobile) cards? Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone developed FreeBSD support for the Lucent/AT&T/NCR WaveLAN cards? I'm currently working with wireless bridges built around these cards, and they work well for upscale projects. But on projects where cost is paramount, we may need to run the adapters right inside UNIX hosts. This should be easy.... Provided that drivers and setup utilities are available. Are there FreeBSD drivers for these cards -- either the 900 MHz or 2.4 GHz versions? Userland configuration and status utilities? --Brett From owner-freebsd-hardware Fri Nov 29 21:52:09 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA25473 for hardware-outgoing; Fri, 29 Nov 1996 21:52:09 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA25465 for ; Fri, 29 Nov 1996 21:52:06 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id QAA25244; Sat, 30 Nov 1996 16:21:55 +1030 (CST) From: Michael Smith Message-Id: <199611300551.QAA25244@genesis.atrad.adelaide.edu.au> Subject: Re: Support for Lucent WaveLAN (ISA, not mobile) cards? In-Reply-To: <9610298493.AA849330036@ccgate.infoworld.com> from "BRETT_GLASS@infoworld.com" at "Nov 29, 96 09:55:47 pm" To: BRETT_GLASS@infoworld.com Date: Sat, 30 Nov 1996 16:21:54 +1030 (CST) Cc: hardware@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk BRETT_GLASS@infoworld.com stands accused of saying: > Has anyone developed FreeBSD support for the Lucent/AT&T/NCR WaveLAN cards? > I'm currently working with wireless bridges built around these cards, and > they work well for upscale projects. But on projects where cost is > paramount, we may need to run the adapters right inside UNIX hosts. This > should be easy.... Provided that drivers and setup utilities are available. > > Are there FreeBSD drivers for these cards -- either the 900 MHz or 2.4 GHz > versions? Userland configuration and status utilities? There's a potential customer in Sydney that's considering trying to fund me to produce a decent driver for these cards. At this point in time, there are several BSD/OS drivers, a Linux driver, and (I believe) support in the PAO code for the PCCARD Wavelan cards. The customer was planning on supplying me with a couple of loaner cards; if you were interested in helping fund the exercise I can put the two of you in contact. (Note that I'm trying to work things out so that I can afford to spend time working on device drivers; the big struggle is finding people who understand that I have to eat while I'm doing this, and striking a balance with my employer.) > --Brett -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Sat Nov 30 02:09:39 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA03803 for hardware-outgoing; Sat, 30 Nov 1996 02:09:39 -0800 (PST) Received: from valis.worldgate.com (marcs@valis.worldgate.com [198.161.84.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA03796 for ; Sat, 30 Nov 1996 02:09:36 -0800 (PST) Received: from localhost (marcs@localhost) by valis.worldgate.com (8.6.12/8.6.12) with SMTP id DAA06178 for ; Sat, 30 Nov 1996 03:09:27 -0700 X-Authentication-Warning: valis.worldgate.com: marcs owned process doing -bs Date: Sat, 30 Nov 1996 03:09:01 -0700 (MST) From: Marc Slemko X-Sender: marcs@valis.worldgate.com To: hardware@freebsd.org Subject: Tekram 390U and Seagate hawk ST32151N Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Anyone have any trouble making a Tekram 390U SCSI controller work with certain disks? What we are seeing is that it hangs on probing the disks after the SCSI bios is installed, but if you go into the bios setup it can probe them, scan them, etc. with no problems. It works fine with tape drives and an old 300 meg drive we tried. Tried lowering the SCSI bus speed, disabling things that could cause problems, etc. See the same thing when we try it with a different type of Seagate. Yes, the bus is properly terminated and we have tried multiple cables. No, the question isn't really freebsd specific but there has been some discussion of the Tekram here a while back... From owner-freebsd-hardware Sat Nov 30 04:07:32 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA09542 for hardware-outgoing; Sat, 30 Nov 1996 04:07:32 -0800 (PST) Received: from cyclone.degnet.baynet.de (cyclone.degnet.baynet.de [194.95.214.129]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA09530; Sat, 30 Nov 1996 04:07:28 -0800 (PST) Received: from nada (ppp5 [194.95.214.135]) by cyclone.degnet.baynet.de (8.6.12/8.6.9) with SMTP id OAA14555; Sat, 30 Nov 1996 14:05:46 +0100 Message-ID: <32A03D57.6274@degnet.baynet.de> Date: Sat, 30 Nov 1996 12:57:43 -0100 From: Darius Moos Reply-To: moos@degnet.baynet.de X-Mailer: Mozilla 3.0Gold (Win95; I) MIME-Version: 1.0 To: "John S. Dyson" CC: mango@staff.communique.net, hackers@freefall.freebsd.org, hardware@freefall.freebsd.org Subject: Re: Adaptec UW controller and Seagate Elite performance ? References: <199611300444.XAA09675@dyson.iquest.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk One thing that stroke me some time ago was the termination of the SCSI-bus. After changing from passive to active termination, the speed of my disks doubled !!! Darius Moos. John S. Dyson wrote: > > > > > # bonnie -s 40 (akira, http running) > > -------Sequential Output-------- ---Sequential Input-- --Random-- > > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- > > MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU > > 40 3271 34.8 3085 13.0 1559 8.3 10330 97.1 44763 95.7 991.0 20.4 > > > > and > > IOZONE performance measurements: > > 2039008 bytes/second for writing the file > > 34861747 bytes/second for reading the file > > > > It bothered me that: > > 1- reading is 20 times faster than writing > > You are seeing the results of caching. The system remembers what > is written so that it doesn't have to unnecessarily re-read the > data. > > > > > 2- 2Mbytes/s for writing seems slow, even if this was a scsi-2 and not > > an > > scsi fast and wide drive. > > > I don't know why your iozone write perf is so slow, unless you are writing > 512 bytes at a time. Note also, that you might not have the write > behind caching enabled on your drive. > > Try the following commands: > > # iozone auto > and > # iozone 40 8192 > and > # iozone 8192 > > and let me know the results. > > John > dyson@freebsd.org From owner-freebsd-hardware Sat Nov 30 05:21:39 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA14483 for hardware-outgoing; Sat, 30 Nov 1996 05:21:39 -0800 (PST) Received: from gw.itfs.nsk.su (ns.itfs.nsk.su [193.124.36.33]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA14477 for ; Sat, 30 Nov 1996 05:21:33 -0800 (PST) Received: from itfs.UUCP (uucp@localhost) by gw.itfs.nsk.su (8.6.12/8.6.12) with UUCP id TAA14572 for hardware@freebsd.org; Sat, 30 Nov 1996 19:20:05 +0600 Received: by itfs.nsk.su; Sat, 30 Nov 96 20:30:44 +0600 (NSK) Received: (from daemon@localhost) by news.itfs.nsk.su (8.7.5/8.6.12) id TAA18368; Sat, 30 Nov 1996 19:19:37 +0600 (NSK) From: "Nickolay N. Dudorov" To: hardware@freebsd.org Subject: Re: Tekram 390U and Seagate hawk ST32151N Date: 30 Nov 1996 13:19:35 GMT Message-ID: <57pc97$hcm@news.itfs.nsk.su> References: Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Marc Slemko wrote: > Anyone have any trouble making a Tekram 390U SCSI controller work with > certain disks? What we are seeing is that it hangs on probing the disks > after the SCSI bios is installed, but if you go into the bios setup it can > probe them, scan them, etc. with no problems. It works fine with tape > drives and an old 300 meg drive we tried. > Tried lowering the SCSI bus speed, disabling things that could cause > problems, etc. See the same thing when we try it with a different type of > Seagate. Yes, the bus is properly terminated and we have tried multiple > cables. > No, the question isn't really freebsd specific but there has been some > discussion of the Tekram here a while back... Last week I also encounter a problem with Tekram DC-390F controller and CONNER CFP2105S disk (which also has some Seagate name on it ;). This disk was previously used with NCR 53c810-based controller AND was Dangerously Dedicated to FreeBSD. Tekram's BIOS hangs on identifing the disk, but successfully sees it when in it's setup. I solve my problem by re-fdisking disk to non-DD mode with old controller. This is definitely Tekram BIOS bug - if it does'nt like DD disk it can just skip it and not hung forever ;-). P.S. Are there any plans/shedules to support extened features of 53c875-based controllers in ncr-driver ? (It'll be very good ULTRA WIDE SCSI controller for ~150$ here in Siberia) N.Dudorov From owner-freebsd-hardware Sat Nov 30 10:12:10 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA28627 for hardware-outgoing; Sat, 30 Nov 1996 10:12:10 -0800 (PST) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA28619 for ; Sat, 30 Nov 1996 10:12:07 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr3-15.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA00313 (5.67b/IDA-1.5 for ); Sat, 30 Nov 1996 19:12:03 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.3/8.6.9) id SAA01423; Sat, 30 Nov 1996 18:01:37 +0100 (CET) Message-Id: Date: Sat, 30 Nov 1996 18:00:17 +0100 From: se@freebsd.org (Stefan Esser) To: marcs@znep.com (Marc Slemko) Cc: hardware@freebsd.org Subject: Re: Tekram 390U and Seagate hawk ST32151N References: X-Mailer: Mutt 0.52 Mime-Version: 1.0 In-Reply-To: ; from Marc Slemko on Nov 30, 1996 03:09:01 -0700 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Nov 30, marcs@znep.com (Marc Slemko) wrote: > Anyone have any trouble making a Tekram 390U SCSI controller work with > certain disks? What we are seeing is that it hangs on probing the disks > after the SCSI bios is installed, but if you go into the bios setup it can > probe them, scan them, etc. with no problems. It works fine with tape > drives and an old 300 meg drive we tried. I'm using an DC390F, and it seems to be a very nice card. But I also had some problems with boots hanging, recently. (It always works if I press the RESET button on my box, though. It may be a problem with the NCR driver setting controller registers to values that the warm boot code in the cards BIOS does not expect ...) Their Web-Server (www.tekram.com) doesn't seem to offer any SCSI BIOS upgrades. (My card got release 1.60). > Tried lowering the SCSI bus speed, disabling things that could cause > problems, etc. See the same thing when we try it with a different type of > Seagate. Yes, the bus is properly terminated and we have tried multiple > cables. When does it hang: 1) After showing the brand/model of the drive ? 2) After finding all devices on the SCSI bus ? 3) After loading the FreeBSD kernel ? I just wondered whether you have a WIDE drive connected to the Tekram. This could cause problems, since an 8bit cable is used to connect a WIDE capable SCSI chip (the 53c875) and a WIDE capable drive, then ... (Although the 390U offers only an 8bit SCSI bus, it does in fact use a WIDE SCSI chip. The 390F is identical, but comes with a WIDE and an 8bit internal connectors and a WIDE external connector ...) > No, the question isn't really freebsd specific but there has been some > discussion of the Tekram here a while back... Yes, I added support for the Tekram Ultra-SCSI cards to the NCR driver. (More to come soon ... :) And I still think they are the best SCSI cards, especially taking their price into account. I'd like to get this sorted out as soon as possible, to have a chance to get this fxixed for 2.2R ... Regards, STefan From owner-freebsd-hardware Sat Nov 30 10:50:35 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA00946 for hardware-outgoing; Sat, 30 Nov 1996 10:50:35 -0800 (PST) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA00940; Sat, 30 Nov 1996 10:50:33 -0800 (PST) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.7.5/8.7.3) with UUCP id LAA19494; Sat, 30 Nov 1996 11:50:27 -0700 (MST) Received: from localhost (marcs@localhost) by alive.ampr.ab.ca (8.7.5/8.7.3) with SMTP id LAA02353; Sat, 30 Nov 1996 11:43:40 -0700 (MST) Date: Sat, 30 Nov 1996 11:43:40 -0700 (MST) From: Marc Slemko X-Sender: marcs@alive.ampr.ab.ca To: Stefan Esser cc: hardware@freebsd.org Subject: Re: Tekram 390U and Seagate hawk ST32151N In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 30 Nov 1996, Stefan Esser wrote: > > Tried lowering the SCSI bus speed, disabling things that could cause > > problems, etc. See the same thing when we try it with a different type of > > Seagate. Yes, the bus is properly terminated and we have tried multiple > > cables. > > When does it hang: > > 1) After showing the brand/model of the drive ? > 2) After finding all devices on the SCSI bus ? > 3) After loading the FreeBSD kernel ? Right after the probe, when it shows the ID and LUD, ie.: ID-LUN: 0-0 It does not get to printing the identification of the drive and hangs right after it prints the above. Tried several IDs, it always hangs when it gets to the hard drive; right befere (1) I guess it would be. Someone else suggested that it could be due to the fact that it can't handle parsing a drive setup dedicated to FreeBSD, so I'll try re-fdisking it. > > I just wondered whether you have a WIDE drive connected > to the Tekram. This could cause problems, since an 8bit > cable is used to connect a WIDE capable SCSI chip (the > 53c875) and a WIDE capable drive, then ... Nope. [...] > > I'd like to get this sorted out as soon as possible, to > have a chance to get this fxixed for 2.2R ... Don't think it is a FreeBSD problem, but I'll let you know if I do encounter any FreeBSD problems once it is running. We are using -stable, but put the driver from -current in to make it work. I also encountered once machine where I simply could not make the Tekram install its BIOS; yanked everything else out, played with PCI bus settings, but the card would just detect drives and work find under FreeBSD but not install the BIOS and I couldn't change any settings. I'm inclined to write that off to the wonders of PCI or, more accurately, the wonders of the attempt to make PCI and PNP work by stupid motherboard and BIOS manufacturers. From owner-freebsd-hardware Sat Nov 30 13:13:54 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07531 for hardware-outgoing; Sat, 30 Nov 1996 13:13:54 -0800 (PST) Received: from po1.glue.umd.edu (po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA07526 for ; Sat, 30 Nov 1996 13:13:51 -0800 (PST) Received: from packet.eng.umd.edu (packet.eng.umd.edu [129.2.98.184]) by po1.glue.umd.edu (8.8.3/8.7.3) with ESMTP id QAA28452 for ; Sat, 30 Nov 1996 16:13:48 -0500 (EST) Received: from localhost (chuckr@localhost) by packet.eng.umd.edu (8.8.3/8.7.3) with SMTP id QAA10148 for ; Sat, 30 Nov 1996 16:13:47 -0500 (EST) X-Authentication-Warning: packet.eng.umd.edu: chuckr owned process doing -bs Date: Sat, 30 Nov 1996 16:13:46 -0500 (EST) From: Chuck Robey X-Sender: chuckr@packet.eng.umd.edu To: FreeBSD-Hardware@FreeBSD.org Subject: Fixed Frequency monitors Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I was wondering if anyone knew the V and H rates for this monitor that's dropped into my lap: A Sun (oem'ed Sony) GDM-1962B ? I haven't even really begun to read the XFree docs about how to go about setting the scan rates, so I'm not asking that yet, but I figure the place to start is with the basic specs. It's got this 13W3 connector, I've gone and bought a card that will push a fixed Frequency monitor, now I just have to figure out this thing's preferred diet. BTW, the card I got is what the previous owner was using, so I'm safe there, I think. I think this thing is kinda oldish, but it's 19", so I'm gonna try to get it working. Whatta X screen it'll make! Color! ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hardware Sat Nov 30 14:32:51 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA09994 for hardware-outgoing; Sat, 30 Nov 1996 14:32:51 -0800 (PST) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA09989 for ; Sat, 30 Nov 1996 14:32:50 -0800 (PST) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0vTxxK-0003vtC; Sat, 30 Nov 96 14:32 PST Received: from critter.tfs.com (localhost.dk.tfs.com [127.0.0.1]) by critter.tfs.com (8.8.2/8.8.2) with ESMTP id XAA06425 for ; Sat, 30 Nov 1996 23:33:50 +0100 (MET) To: hardware@freebsd.org Subject: the "debug" connector on a P6... Reply-to: phk@freebsd.org Date: Sat, 30 Nov 1996 23:33:50 +0100 Message-ID: <6423.849393230@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Most P6 motherboards seems to have the "debug" connector for each CPU. As far as I know you can get hold of the boundary-scan signals of the CPU this way, and poke around and debug the state of it. Now, are there anybody out there who knows what it would take to get something that plugs into that connector ? Preferably something that could be controlled from FreeBSD... -- 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. Future will arrive by its own means, progress not so. From owner-freebsd-hardware Sat Nov 30 14:50:51 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA11010 for hardware-outgoing; Sat, 30 Nov 1996 14:50:51 -0800 (PST) Received: from po1.glue.umd.edu (po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA11005; Sat, 30 Nov 1996 14:50:49 -0800 (PST) Received: from packet.eng.umd.edu (packet.eng.umd.edu [129.2.98.184]) by po1.glue.umd.edu (8.8.3/8.7.3) with ESMTP id RAA00016; Sat, 30 Nov 1996 17:50:46 -0500 (EST) Received: from localhost (chuckr@localhost) by packet.eng.umd.edu (8.8.3/8.7.3) with SMTP id RAA09613; Sat, 30 Nov 1996 17:50:45 -0500 (EST) X-Authentication-Warning: packet.eng.umd.edu: chuckr owned process doing -bs Date: Sat, 30 Nov 1996 17:50:45 -0500 (EST) From: Chuck Robey X-Sender: chuckr@packet.eng.umd.edu To: phk@freebsd.org cc: hardware@freebsd.org Subject: Re: the "debug" connector on a P6... In-Reply-To: <6423.849393230@critter.tfs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 30 Nov 1996, Poul-Henning Kamp wrote: > > Most P6 motherboards seems to have the "debug" connector for each CPU. > As far as I know you can get hold of the boundary-scan signals of the > CPU this way, and poke around and debug the state of it. > > Now, are there anybody out there who knows what it would take to get > something that plugs into that connector ? > > Preferably something that could be controlled from FreeBSD... Any kind of clue as to what such a connector looks like, like how many pins, or something? > > -- > 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. > Future will arrive by its own means, progress not so. > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hardware Sat Nov 30 14:59:23 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA12340 for hardware-outgoing; Sat, 30 Nov 1996 14:59:23 -0800 (PST) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA12333 for ; Sat, 30 Nov 1996 14:59:21 -0800 (PST) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0vTyMz-0003vyC; Sat, 30 Nov 96 14:58 PST Received: from critter.tfs.com (localhost.dk.tfs.com [127.0.0.1]) by critter.tfs.com (8.8.2/8.8.2) with ESMTP id AAA06586; Sun, 1 Dec 1996 00:00:21 +0100 (MET) To: Chuck Robey cc: hardware@freebsd.org Subject: Re: the "debug" connector on a P6... In-reply-to: Your message of "Sat, 30 Nov 1996 17:50:45 EST." Date: Sun, 01 Dec 1996 00:00:20 +0100 Message-ID: <6584.849394820@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message , Chuck Robey writes: >On Sat, 30 Nov 1996, Poul-Henning Kamp wrote: > >> >> Most P6 motherboards seems to have the "debug" connector for each CPU. >> As far as I know you can get hold of the boundary-scan signals of the >> CPU this way, and poke around and debug the state of it. >> >> Now, are there anybody out there who knows what it would take to get >> something that plugs into that connector ? >> >> Preferably something that could be controlled from FreeBSD... > >Any kind of clue as to what such a connector looks like, like how many >pins, or something? it's a 2x20 (or thereabout) berg connector, ie: somewhat like the two rows of pins for the floppy cable. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-hardware Sat Nov 30 15:06:41 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA13253 for hardware-outgoing; Sat, 30 Nov 1996 15:06:41 -0800 (PST) Received: from po2.glue.umd.edu (po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA13248 for ; Sat, 30 Nov 1996 15:06:39 -0800 (PST) Received: from packet.eng.umd.edu (packet.eng.umd.edu [129.2.98.184]) by po2.glue.umd.edu (8.8.3/8.7.3) with ESMTP id SAA07274; Sat, 30 Nov 1996 18:06:36 -0500 (EST) Received: from localhost (chuckr@localhost) by packet.eng.umd.edu (8.8.3/8.7.3) with SMTP id SAA10238; Sat, 30 Nov 1996 18:06:36 -0500 (EST) X-Authentication-Warning: packet.eng.umd.edu: chuckr owned process doing -bs Date: Sat, 30 Nov 1996 18:06:35 -0500 (EST) From: Chuck Robey X-Sender: chuckr@packet.eng.umd.edu To: Poul-Henning Kamp cc: hardware@freebsd.org Subject: Re: the "debug" connector on a P6... In-Reply-To: <6584.849394820@critter.tfs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 1 Dec 1996, Poul-Henning Kamp wrote: > In message , Chuck > Robey writes: > >On Sat, 30 Nov 1996, Poul-Henning Kamp wrote: > > > >> > >> Most P6 motherboards seems to have the "debug" connector for each CPU. > >> As far as I know you can get hold of the boundary-scan signals of the > >> CPU this way, and poke around and debug the state of it. > >> > >> Now, are there anybody out there who knows what it would take to get > >> something that plugs into that connector ? > >> > >> Preferably something that could be controlled from FreeBSD... > > > >Any kind of clue as to what such a connector looks like, like how many > >pins, or something? > > it's a 2x20 (or thereabout) berg connector, ie: somewhat like the two rows > of pins for the floppy cable. Hmm, yeah, I know what Berg pins are. Seems a Tyan Titan Pro doesn't have the connectors you are describing. Too bad. Maybe they left it out in the dual design, because the motherboard is somewhat cramped to begin with. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hardware Sat Nov 30 16:00:37 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA17507 for hardware-outgoing; Sat, 30 Nov 1996 16:00:37 -0800 (PST) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA17502 for ; Sat, 30 Nov 1996 16:00:33 -0800 (PST) Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id LAA12347; Sun, 1 Dec 1996 11:04:10 +1100 (EST) Date: Sun, 1 Dec 1996 11:04:09 +1100 (EST) From: "Daniel O'Callaghan" To: Michael Smith cc: BRETT_GLASS@infoworld.com, hardware@FreeBSD.org Subject: Re: Support for Lucent WaveLAN (ISA, not mobile) cards? In-Reply-To: <199611300551.QAA25244@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 30 Nov 1996, Michael Smith wrote: >> Brett Glass asks about Wavelan support. > There's a potential customer in Sydney that's considering trying to Hey! I'm in Melbourne!!! > fund me to produce a decent driver for these cards. At this point in > time, there are several BSD/OS drivers, a Linux driver, and (I > believe) support in the PAO code for the PCCARD Wavelan cards. > > The customer was planning on supplying me with a couple of loaner > cards; if you were interested in helping fund the exercise I can put > the two of you in contact. (Note that I'm trying to work things out > so that I can afford to spend time working on device drivers; the big > struggle is finding people who understand that I have to eat while I'm > doing this, and striking a balance with my employer.) I'd be really keen if Brett, or anyone else could chip in a little bit to help me fund Mike. I'll buy the cards and ship them to Mike (it's only 800km from Melbourne to Adelaide). As Mike says, there are already drivers written for BSD/OS, and FreeBSD for the PCCARD, so all that needs to be done is make the ISA code work. Danny From owner-freebsd-hardware Sat Nov 30 18:33:43 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA26729 for hardware-outgoing; Sat, 30 Nov 1996 18:33:43 -0800 (PST) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA26712; Sat, 30 Nov 1996 18:33:37 -0800 (PST) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.7.5/8.7.3) with UUCP id TAA03299; Sat, 30 Nov 1996 19:33:37 -0700 (MST) Received: from localhost (marcs@localhost) by alive.ampr.ab.ca (8.7.5/8.7.3) with SMTP id TAA05070; Sat, 30 Nov 1996 19:32:28 -0700 (MST) Date: Sat, 30 Nov 1996 19:32:28 -0700 (MST) From: Marc Slemko X-Sender: marcs@alive.ampr.ab.ca To: hardware@freebsd.org cc: scsi@freebsd.org, Greg Skafte Subject: Re: Tekram 390U and Seagate hawk ST32151N In-Reply-To: <57pc97$hcm@news.itfs.nsk.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [Sent to hardware and scsi; unless you have a reason, please followup to only one list. scsi is probably better, since it is dealing with freebsd drivers now.] Nickolay's suggestion worked, so now we can get past the BIOS probing stage. However, FreeBSD still won't boot. I am using -stable with the NCR driver (ncr.c and ncrregs.h) from -current dropped in. A 300 meg drive will work fine, but when it tries to probe the 2 gig hawk we get something like: sd0(ncr0:4:0): COMMAND failed (9 ff) @[address] sd0 could not get size error ncr0: aborting job ERROR (90:0) (0-21-15) (0/13) @ (418:43000060) script cmd = 878b0000 reg : [deleted] ncr0: restart failed That is not exact and doesn't include some of the important stuff for debugging it, but I don't have a copy of the full message right now. Booting with a 2.2-ALPHA disk works fine, so either I missed something from the NCR stuff between stable and current or there was another change that fixed this. Anyone have any ideas about what it could be? Nothing stood out in the CVS logs as being obvious. If all else fails, we just have to move to 2.2 which won't kill us, but we would prefer not to for this machine. On 30 Nov 1996, Nickolay N. Dudorov wrote: > Marc Slemko wrote: > > Anyone have any trouble making a Tekram 390U SCSI controller work with > > certain disks? What we are seeing is that it hangs on probing the disks > > after the SCSI bios is installed, but if you go into the bios setup it can > > probe them, scan them, etc. with no problems. It works fine with tape > > drives and an old 300 meg drive we tried. > > > Tried lowering the SCSI bus speed, disabling things that could cause > > problems, etc. See the same thing when we try it with a different type of > > Seagate. Yes, the bus is properly terminated and we have tried multiple > > cables. > > > No, the question isn't really freebsd specific but there has been some > > discussion of the Tekram here a while back.... > > Last week I also encounter a problem with Tekram DC-390F > controller and CONNER CFP2105S disk (which also has some Seagate > name on it ;). This disk was previously used with NCR 53c810-based > controller AND was Dangerously Dedicated to FreeBSD. Tekram's > BIOS hangs on identifing the disk, but successfully sees it when > in it's setup. I solve my problem by re-fdisking disk to non-DD > mode with old controller. > This is definitely Tekram BIOS bug - if it does'nt like > DD disk it can just skip it and not hung forever ;-). > > P.S. Are there any plans/shedules to support extened features > of 53c875-based controllers in ncr-driver ? > (It'll be very good ULTRA WIDE SCSI controller for ~150$ > here in Siberia) > > N.Dudorov >