From owner-freebsd-hardware Tue Mar 4 11:42:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA10940 for hardware-outgoing; Tue, 4 Mar 1997 11:42:46 -0800 (PST) Received: from trogon.kiwi.net (trogon.kiwi.net [207.155.64.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA10934; Tue, 4 Mar 1997 11:42:44 -0800 (PST) Received: from localhost (freebsd@localhost) by trogon.kiwi.net (8.8.5/8.8.5) with SMTP id LAA02156; Tue, 4 Mar 1997 11:42:42 -0800 (PST) Date: Tue, 4 Mar 1997 11:42:42 -0800 (PST) From: Christopher Taylor To: freebsd-hackers@freebsd.org cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Squid 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 am trying to get Squid to work on my FreeBSD 2.2-ALPHA system. It gives me an error at compile time re: res_init undefined: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Making all in lib... Making all in scripts... Making all in src... gcc -o dnsserver -g dnsserver.o -L../lib -lmiscutil -lm -lresolv -lgnumalloc dnsserver.c:267: Undefined symbol `___res_init' referenced from text segment /usr/lib/libresolv.so.2.0: Undefined symbol `___res_init' referenced *** Error code 1 Stop. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - I can get around it by commenting out res_init in dnsserver.c. I have also played around with the -l libs in Makefile, etc. Everything compiles ok, but when I try to run squid, it gives this message in the cache.log file: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 97/03/04 11:36:23| Starting Squid Cache version 1.1.8 for i386-unknown-freebsd2.2... 97/03/04 11:36:23| With 256 file descriptors available 97/03/04 11:36:23| Performing DNS Tests... FATAL: ipcache_init: DNS name lookup tests failed. Squid Cache (Version 1.1.8): Terminated abnormally. CPU Usage: user 0 sys 0 Maximum Resident Size: 1040 KB Page faults with physical i/o: 3 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - I get the same results on a FreeBSD 3.0, 2.1.6, 2.1.7 system. If anyone can give me any insight, it would be greatly appreciated! -------- Christopher Taylor Kiwi Internet Services Best Rates Around! ctaylor@kiwi.net Phone: 909-274-7800! $12.95/mo FLAT PPP! BBS: SUCCESSBBS.COM Visit: Http://Www.Kiwi.Net Web Services! PGP Fingerprint: 0D 47 98 16 74 DC 3D 7E 1E 6E 6C 2B D9 A5 C7 1B Finger 'ctaylor@kiwi.net' for Public Keyring! From owner-freebsd-hardware Tue Mar 4 14:59:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA21945 for hardware-outgoing; Tue, 4 Mar 1997 14:59:34 -0800 (PST) Received: from mail2.uunet.ca (mail2.uunet.ca [142.77.1.15]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA21917 for ; Tue, 4 Mar 1997 14:59:26 -0800 (PST) Received: from wraith ([142.77.1.23]) by mail2.uunet.ca with SMTP id <122991-18384>; Tue, 4 Mar 1997 17:59:18 -0500 Message-ID: <331CA8C4.5058@kerris.com> Date: Tue, 4 Mar 1997 17:57:08 -0500 From: Mike Kerr Organization: Kerr Information Systems X-Mailer: Mozilla 3.0 (WinNT; I) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: Problems with 2.1 Probe? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've had, on occasion, difficulty with my system probing my modem. I've gone through the following progression: 14.4K No problems detecting it. (100%) 28.8K Occasional problems detecting it. (60%) 33.6K Seems to refuse to detect it. (10%) The percentages is an estimate of how often it will work. Each time the modem has been configured to COM3 (sio2) on IRQ 4, with the standard 3e8 base address. It's getting *really* frustrating. I've even tried changing the IRQ on this latest attempt to IRQ 3, but it still won't detect it. The machine I'm running is a 386DX-40 with 8M RAM. Is anybody aware of any incompatibilities with 386 motherboards and fast COM ports, or if the probe has problems, or if there is a way I can bypass the probe to get the thing to work? Oddly enough, if I boot into my DOS partition and use something like Telemate, it works fine. Mike. From owner-freebsd-hardware Tue Mar 4 16:20:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA26646 for hardware-outgoing; Tue, 4 Mar 1997 16:20:44 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA26575 for ; Tue, 4 Mar 1997 16:20:37 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id KAA18729; Wed, 5 Mar 1997 10:49:34 +1030 (CST) From: Michael Smith Message-Id: <199703050019.KAA18729@genesis.atrad.adelaide.edu.au> Subject: Re: Problems with 2.1 Probe? In-Reply-To: <331CA8C4.5058@kerris.com> from Mike Kerr at "Mar 4, 97 05:57:08 pm" To: mkerr@kerris.com (Mike Kerr) Date: Wed, 5 Mar 1997 10:49:34 +1030 (CST) Cc: freebsd-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 Mike Kerr stands accused of saying: > I've had, on occasion, difficulty with my system probing my modem. I've > gone through the following progression: > > 14.4K No problems detecting it. (100%) > 28.8K Occasional problems detecting it. (60%) > 33.6K Seems to refuse to detect it. (10%) > > The percentages is an estimate of how often it will work. Each time the > modem has been configured to COM3 (sio2) on IRQ 4, with the standard 3e8 > base address. > > It's getting *really* frustrating. I've even tried changing the IRQ on > this latest attempt to IRQ 3, but it still won't detect it. The machine > I'm running is a 386DX-40 with 8M RAM. Neither IRQ 3 nor 4 are available if you have sio0 or sio1 respectively configured; you will have to use a different interrupt in that case. > Is anybody aware of any incompatibilities with 386 motherboards and fast > COM ports, or if the probe has problems, or if there is a way I can > bypass the probe to get the thing to work? If your modem is an internal unit, and it does not have a _real_ UART on the board, it's likely that it is too _slow_, and the 2.1 sio probe is giving up on it. You could try booting a 2.2 installation disk to see if it finds it, once you have fixed your interrupt problem. > Oddly enough, if I boot into my DOS partition and use something like > Telemate, it works fine. DOS communications programs have very low expectations of serial hardware. You could probably jam a digestive biscuit into an ISA slot and log on to your favorite BBS with it, but that won't work too well with the BSD sio driver. > Mike. -- ]] 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 Wed Mar 5 00:58:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA03060 for hardware-outgoing; Wed, 5 Mar 1997 00:58:46 -0800 (PST) Received: from dfw-ix2.ix.netcom.com (dfw-ix2.ix.netcom.com [206.214.98.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA03055; Wed, 5 Mar 1997 00:58:44 -0800 (PST) Received: (from smap@localhost) by dfw-ix2.ix.netcom.com (8.8.4/8.8.4) id CAA07292; Wed, 5 Mar 1997 02:58:07 -0600 (CST) Received: from wck-ca14-39.ix.netcom.com(207.92.174.103) by dfw-ix2.ix.netcom.com via smap (V1.3) id sma007288; Wed Mar 5 02:57:46 1997 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id AAA24992; Wed, 5 Mar 1997 00:57:42 -0800 (PST) Date: Wed, 5 Mar 1997 00:57:42 -0800 (PST) Message-Id: <199703050857.AAA24992@silvia.HIP.Berkeley.EDU> To: freebsd@trogon.kiwi.net CC: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG In-reply-to: (message from Christopher Taylor on Tue, 4 Mar 1997 11:42:42 -0800 (PST)) Subject: Re: Squid From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * cc: freebsd-questions@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG * * I am trying to get Squid to work on my FreeBSD 2.2-ALPHA system. It gives Two advices: (1) Use the port (2) Don't post to more than one mailing list (especially when none of them are appropriate ;) Satoshi From owner-freebsd-hardware Wed Mar 5 04:45:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA15059 for hardware-outgoing; Wed, 5 Mar 1997 04:45:36 -0800 (PST) Received: from os.inf.tu-dresden.de (os.inf.tu-dresden.de [141.76.1.46]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA15048; Wed, 5 Mar 1997 04:45:32 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by os.inf.tu-dresden.de (8.8.5/8.8.5) with ESMTP id NAA27354; Wed, 5 Mar 1997 13:20:44 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA19293; Wed, 5 Mar 1997 09:40:09 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA15427; Wed, 5 Mar 1997 09:02:28 +0100 (MET) Message-ID: Date: Wed, 5 Mar 1997 09:02:28 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd@trogon.kiwi.net (Christopher Taylor) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Squid References: X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Christopher Taylor on Mar 4, 1997 11:42:42 -0800 Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Christopher Taylor wrote: > Making all in src... > gcc -o dnsserver -g dnsserver.o -L../lib -lmiscutil -lm -lresolv -lgnumalloc > dnsserver.c:267: Undefined symbol `___res_init' referenced from text segment > /usr/lib/libresolv.so.2.0: Undefined symbol `___res_init' referenced mv /usr/lib/libresolv.so.2.0 /usr/lib/compat/ ldconfig -m /usr/lib/compat rm /usr/lib/libresolv* FreeBSD 2.2 is not supposed to have one at all. Remove -lresolv, you don't need it. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hardware Wed Mar 5 08:03:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA24650 for hardware-outgoing; Wed, 5 Mar 1997 08:03:18 -0800 (PST) Received: from dn800e0.fingerhut.com (dn800e0-ext.fingerhut.com [204.221.45.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA24641; Wed, 5 Mar 1997 08:03:10 -0800 (PST) Received: from dn800e0.fingerhut.com (root@localhost) by dn800e0.fingerhut.com (8.7.5/8.7.3) with ESMTP id KAA10853; Wed, 5 Mar 1997 10:04:15 -0600 (CST) Received: from seag.fingerhut.com (GF007E0.SEAG.fingerhut.com [151.210.140.7]) by dn800e0.fingerhut.com (8.7.5/8.7.3) with SMTP id KAA10849; Wed, 5 Mar 1997 10:04:14 -0600 (CST) Received: from gf006e0.fingerhut.com. by seag.fingerhut.com (SMI-8.6/SMI-SVR4) id KAA06579; Wed, 5 Mar 1997 10:03:05 -0600 Received: by gf006e0.fingerhut.com. (5.x/SMI-SVR4) id AA28215; Wed, 5 Mar 1997 10:03:02 -0600 Date: Wed, 5 Mar 1997 10:03:02 -0600 Message-Id: <9703051603.AA28215@gf006e0.fingerhut.com.> From: Bruce Albrecht To: freebsd-smp@freebsd.org, freebsd-hardware@freebsd.org Subject: P6 MB recommendations Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm planning to purchase a dual P6 system in the next 3 weeks, and I'm looking for opinions about various mothboards and/or systems. I'm only planning on buying one P6-200 CPU now, and a second one in about 6 months. I'm only planning on using SCSI peripherals, mainly because I intend to liberate a bunch of drives from my Amiga. I'm looking at: Micron Millenia Pro2 with an AH2940UW controller Custom Tyan Titan Pro ATX (Award BIOS), ASUS AS200 SCSI + either Tyan 875 or ASUS 875 UW controller, Matrox Millenium Custom ASUS P65UP5/CP6ND, ASUS AS200 + ASYS 875 controller, Matrox Millenium GigaByte 686DX, ASUS AS200 + ASYS 875 controller, Matrox Millenium I'm leaning towards the custom Tyan system, probably from RC Systems. If you've got one (or purchased from RC Systems), I'd like to hear from you. Should I stay away from the Tyan 875 controller, since they've discontinued it, or should that not really matter, since it's just another Symbios 875 chipset controller? Thanks. From owner-freebsd-hardware Wed Mar 5 08:50:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA27149 for hardware-outgoing; Wed, 5 Mar 1997 08:50:27 -0800 (PST) Received: from gw.rinet.ru (gw.rinet.ru [194.87.171.65]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id IAA27138; Wed, 5 Mar 1997 08:50:11 -0800 (PST) Received: by gw.rinet.ru id TAA29903; (8.6.11/vak/1.9) Wed, 5 Mar 1997 19:49:34 +0300 From: marck@gw.rinet.ru (Dmitry Morozovsky) Message-Id: <199703051649.TAA29903@gw.rinet.ru> Subject: NCR 510 troubles To: freebsd-scsi@freebsd.org Date: Wed, 5 Mar 1997 19:49:33 +0300 (MSK) Cc: freebsd-hardware@freebsd.org X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello there. We've got news server (2.1.5, partially upgraded to .7 -- at least, kernel sources upgraded fully) with onboard ahc & additional ncr 510, which holds 3 disks with a ccd on it. ncr configured for 2 tags on bootup. After upgrading newsserver from cnews to inn, regularly, there are very sad things such as: Mar 5 16:38:50 gw2 /kernel: ncr0: restart (ncr dead ?). Mar 5 16:38:51 gw2 /kernel: sd5(ncr0:4:0): UNIT ATTENTION asc:29,0 Mar 5 16:38:51 gw2 /kernel: sd5(ncr0:4:0): Power on, reset, or bus device reset occurred Mar 5 16:38:51 gw2 /kernel: , retries:3 Mar 5 16:38:51 gw2 /kernel: sd3(ncr0:0:0): UNIT ATTENTION asc:29,0 Mar 5 16:38:51 gw2 /kernel: sd3(ncr0:0:0): Power on, reset, or bus device reset occurred field replaceable unit: 14 Mar 5 16:38:51 gw2 /kernel: , retries:3 Mar 5 16:38:51 gw2 /kernel: sd5(ncr0:4:0): FAST SCSI-2 125ns (8 Mb/sec) offset 8. Mar 5 16:38:57 gw2 /kernel: ncr0: restart (ncr dead ?). Mar 5 16:38:58 gw2 /kernel: sd3(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. Mar 5 16:38:58 gw2 /kernel: sd5(ncr0:4:0): FAST SCSI-2 125ns (8 Mb/sec) offset 8. Mar 5 16:38:58 gw2 /kernel: sd4(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. Mar 5 16:38:58 gw2 /kernel: sd4(ncr0:1:0): UNIT ATTENTION asc:29,0 Mar 5 16:38:58 gw2 /kernel: sd4(ncr0:1:0): Power on, reset, or bus device reset occurred field replaceable unit: 14 Mar 5 16:38:58 gw2 /kernel: , retries:4 then system either crashes or one of ncr disks become missing. dmesg: FreeBSD 2.1.5-RELEASE #0: Mon Feb 17 22:56:23 MSK 1997 marck@gw2.rinet.ru:/usr/src/sys/compile/newsx CPU: 133-MHz Pentium 735\\90 or 815\\100 (Pentium-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 30789632 (30068K bytes) Probing for devices on PCI bus 0: chip0 rev 1 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 ahc0 rev 0 int a irq 11 on pci0:9 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "CONNER CFP1060S 1.05GB 2135" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 1013MB (2074880 512 byte sectors) (ahc0:1:0): "CONNER CFP2105S 2.14GB 2B4B" type 0 fixed SCSI 2 sd1(ahc0:1:0): Direct-Access 2048MB (4194304 512 byte sectors) (ahc0:2:0): "Quantum XP34300 81HB" type 0 fixed SCSI 2 sd2(ahc0:2:0): Direct-Access 4101MB (8399520 512 byte sectors) ncr0 rev 18 int a irq 15 on pci0:11 ncr0 waiting for scsi devices to settle (ncr0:0:0): "CONNER CFP1060S 1.05GB 245F" type 0 fixed SCSI 2 sd3(ncr0:0:0): Direct-Access sd3(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1010MB (2070400 512 byte sectors) (ncr0:1:0): "CONNER CFP1060S 1.05GB 2035" type 0 fixed SCSI 2 sd4(ncr0:1:0): Direct-Access sd4(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1013MB (2074880 512 byte sectors) (ncr0:4:0): "QUANTUM EMPIRE_1080S 1101" type 0 fixed SCSI 2 sd5(ncr0:4:0): Direct-Access sd5(ncr0:4:0): FAST SCSI-2 125ns (8 Mb/sec) offset 8. 1029MB (2109376 512 byte sectors) Probing for devices on the ISA bus: scprobe: keyboard won't accept RESET command sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 5 on isa ed0: address 00:80:48:a9:42:ee, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface ccd0-3: Concatenated disk drivers Any proposals? Sincerely, D.Marck ======================================================================== === D.Marck --- Dmitry Morozovsky --- marck@rinet.ru --- Wild Woozle === ======================================================================== From owner-freebsd-hardware Wed Mar 5 09:27:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA28362 for hardware-outgoing; Wed, 5 Mar 1997 09:27:49 -0800 (PST) Received: from tarpon.exis.net (stefan@tarpon.exis.net [205.252.72.108]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA28290; Wed, 5 Mar 1997 09:26:34 -0800 (PST) Received: (from stefan@localhost) by tarpon.exis.net (8.7.4/8.7.3) id MAA05407; Wed, 5 Mar 1997 12:29:38 -0500 Date: Wed, 5 Mar 1997 12:29:37 -0500 (EST) From: Stefan Molnar To: Bruce Albrecht cc: freebsd-smp@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: P6 MB recommendations In-Reply-To: <9703051603.AA28215@gf006e0.fingerhut.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 > Custom Tyan Titan Pro ATX (Award BIOS), ASUS AS200 SCSI + either Tyan 875 or > ASUS 875 UW controller, Matrox Millenium > I'm leaning towards the custom Tyan system, probably from RC Systems. If > you've got one (or purchased from RC Systems), I'd like to hear from you. > Should I stay away from the Tyan 875 controller, since they've discontinued > it, or should that not really matter, since it's just another Symbios 875 > chipset controller? Thanks. The Tyan one we have rocks. But we are using 3 ultra wide buslogic controlers. I find that tyan w/ buslogic makes a very strong system. Stefan -------------------------------------------- Stefan Molnar Team Exis.Net stefan@exis.net Member EFF Slightly Silly Team OS/2 east-coast-ambassador@soda.CSUA.Berkeley.EDU "She turned me into a Newt! A Newt? I got better." -Monty Python -------------------------------------------- From owner-freebsd-hardware Wed Mar 5 11:06:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA05292 for hardware-outgoing; Wed, 5 Mar 1997 11:06:36 -0800 (PST) Received: from r74h25.res.gatech.edu (ken@r74h25.res.gatech.edu [128.61.74.25]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA05287; Wed, 5 Mar 1997 11:06:32 -0800 (PST) Received: (from ken@localhost) by r74h25.res.gatech.edu (8.8.5/8.8.5) id OAA23756; Wed, 5 Mar 1997 14:06:04 -0500 (EST) From: "Kenneth D. Merry" Message-Id: <199703051906.OAA23756@r74h25.res.gatech.edu> Subject: Re: P6 MB recommendations In-Reply-To: <9703051603.AA28215@gf006e0.fingerhut.com.> from Bruce Albrecht at "Mar 5, 97 10:03:02 am" To: Bruce.Albrecht@seag.fingerhut.com (Bruce Albrecht) Date: Wed, 5 Mar 1997 14:06:03 -0500 (EST) Cc: freebsd-smp@freebsd.org, freebsd-hardware@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'm planning to purchase a dual P6 system in the next 3 weeks, and I'm > looking for opinions about various mothboards and/or systems. I'm > only planning on buying one P6-200 CPU now, and a second one in about > 6 months. I'm only planning on using SCSI peripherals, mainly because > I intend to liberate a bunch of drives from my Amiga. > > I'm looking at: > > Micron Millenia Pro2 with an AH2940UW controller > > Custom Tyan Titan Pro ATX (Award BIOS), ASUS AS200 SCSI + either Tyan 875 or > ASUS 875 UW controller, Matrox Millenium > > Custom ASUS P65UP5/CP6ND, ASUS AS200 + ASYS 875 controller, Matrox Millenium > > GigaByte 686DX, ASUS AS200 + ASYS 875 controller, Matrox Millenium > > I'm leaning towards the custom Tyan system, probably from RC Systems. If > you've got one (or purchased from RC Systems), I'd like to hear from you. > Should I stay away from the Tyan 875 controller, since they've discontinued > it, or should that not really matter, since it's just another Symbios 875 > chipset controller? Thanks. I've been running the ASUS P/I-P65UP5 with the C-P6ND cpu card for a couple of months now. It runs pretty well with FreeBSD-SMP. I've got an Adaptec 3940UW and Matrox Millenium, and haven't seen much trouble from it. I've also got 3 DEC 21140-based network cards in it, and a GUS PnP pro. The motherboard has 8 SIMM slots, for a maximum of 512MB, and 5 PCI slots. I assume that it will work with just one CPU. I'd check the ASUS web sites to make sure. (http://www.asus.com.tw, http://www.asus.com) Hope this helps, Ken -- Kenneth Merry ken@r74h25.res.gatech.edu Disclaimer: I don't speak for GTRI, GT, or Elvis. From owner-freebsd-hardware Wed Mar 5 11:37:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA06973 for hardware-outgoing; Wed, 5 Mar 1997 11:37:37 -0800 (PST) Received: from tarkin.qualcomm.com (tarkin.qualcomm.com [129.46.111.16]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA06968; Wed, 5 Mar 1997 11:37:35 -0800 (PST) Received: (from rmallory@localhost) by tarkin.qualcomm.com (8.8.5/1.4/8.7.2/1.12) id LAA06203; Wed, 5 Mar 1997 11:36:38 -0800 (PST) From: Rob Mallory Message-Id: <199703051936.LAA06203@tarkin.qualcomm.com> Subject: Re: P6 MB recommendations To: Bruce.Albrecht@seag.fingerhut.com (Bruce Albrecht) Date: Wed, 5 Mar 1997 11:36:38 -0800 (PST) Cc: freebsd-smp@freebsd.org, freebsd-hardware@freebsd.org In-Reply-To: <9703051603.AA28215@gf006e0.fingerhut.com.> from "Bruce Albrecht" at Mar 5, 97 10:03:02 am X-Mailer: ELM [version 2.4 PL24 ME8b] 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 > > I'm planning to purchase a dual P6 system in the next 3 weeks, and I'm > looking for opinions about various mothboards and/or systems. I'm > only planning on buying one P6-200 CPU now, and a second one in about > 6 months. I'm only planning on using SCSI peripherals, mainly because > I intend to liberate a bunch of drives from my Amiga. > I recently purchased the Tyan dual-pro from www.env.com for $850 inc tax. (motherboard alone was $320) including 2 150MHz cpus (which I overclocked to 166MHz). Call (or email) them and see if you can get the "swap meet price". I chose it because of its 5 pci slots and 8 simm slots. 2 weeks ago the P6-200/512k cpu was just over $1k at the swap meet. they should drop to ~$750 when the klamath is released.(in may/june) Rob From owner-freebsd-hardware Wed Mar 5 11:49:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA08241 for hardware-outgoing; Wed, 5 Mar 1997 11:49:48 -0800 (PST) Received: from mpress.com (qmailr@mpress.com [208.138.29.130]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA08234 for ; Wed, 5 Mar 1997 11:49:46 -0800 (PST) Received: (qmail 23548 invoked by uid 100); 5 Mar 1997 19:49:39 -0000 Message-ID: <19970305114938.25472@mpress.mpress.com> Date: Wed, 5 Mar 1997 11:49:38 -0800 From: Brian Litzinger To: "Kenneth D. Merry" Cc: Bruce Albrecht , freebsd-smp@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: P6 MB recommendations References: <9703051603.AA28215@gf006e0.fingerhut.com.> <199703051906.OAA23756@r74h25.res.gatech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.64 In-Reply-To: <199703051906.OAA23756@r74h25.res.gatech.edu>; from Kenneth D. Merry on Wed, Mar 05, 1997 at 02:06:03PM -0500 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mar 5, "Kenneth D. Merry" wrote: > > I'm planning to purchase a dual P6 system in the next 3 weeks, and I'm > > looking for opinions about various mothboards and/or systems. I'm > > only planning on buying one P6-200 CPU now, and a second one in about > > 6 months. I'm only planning on using SCSI peripherals, mainly because > > I intend to liberate a bunch of drives from my Amiga. > > I've have an ASUS P/I-P65UP5 with the the C-P6ND card. It has 256MB ram (expandable to 512) and 2 PP200 CPUs. I'm running a Dec 21140 card, and Adaptec 2940W SCSI controller. It has uptimes of weeks. Generally I'm the one rebooting it. It runs as an http and ftp server. -- Brian Litzinger brian@mediacity.com From owner-freebsd-hardware Wed Mar 5 12:23:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA09940 for hardware-outgoing; Wed, 5 Mar 1997 12:23:18 -0800 (PST) Received: from persprog.com (persprog.com [204.215.255.203]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA09925 for ; Wed, 5 Mar 1997 12:23:11 -0800 (PST) Received: by persprog.com (8.7.5/4.10) id PAA32564; Wed, 5 Mar 1997 15:15:40 -0500 Received: from dave(192.2.2.6) by cerberus.ppi.com via smap (V1.3) id sma032559; Wed Mar 5 15:15:26 1997 Message-ID: <331DD461.5279@persprog.com> Date: Wed, 05 Mar 1997 15:15:29 -0500 From: Dave Alderman Reply-To: dave@persprog.com Organization: Personalized Programming, Inc X-Mailer: Mozilla 4.0b2 (Win95; I) MIME-Version: 1.0 To: Dmitry Morozovsky , hardware@freebsd.org Subject: Re: NCR 510 troubles X-Priority: 3 (Normal) References: <199703051649.TAA29903@gw.rinet.ru> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dmitry Morozovsky wrote: > FreeBSD 2.1.5-RELEASE #0: Mon Feb 17 22:56:23 MSK 1997 > marck@gw2.rinet.ru:/usr/src/sys/compile/newsx > CPU: 133-MHz Pentium 735\\90 or 815\\100 (Pentium-class CPU) > Origin = "GenuineIntel" Id = 0x52c Stepping=12 > Features=0x1bf > real memory = 33554432 (32768K bytes) > avail memory = 30789632 (30068K bytes) > Probing for devices on PCI bus 0: > chip0 rev 1 on pci0:0 > chip1 rev 1 on pci0:7:0 > chip2 rev 0 on pci0:7:1 > ahc0 rev 0 int a irq 11 on pci0:9 > ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs > ahc0 waiting for scsi devices to settle > (ahc0:0:0): "CONNER CFP1060S 1.05GB 2135" type 0 fixed SCSI 2 > sd0(ahc0:0:0): Direct-Access 1013MB (2074880 512 byte sectors) > (ahc0:1:0): "CONNER CFP2105S 2.14GB 2B4B" type 0 fixed SCSI 2 > sd1(ahc0:1:0): Direct-Access 2048MB (4194304 512 byte sectors) > (ahc0:2:0): "Quantum XP34300 81HB" type 0 fixed SCSI 2 > sd2(ahc0:2:0): Direct-Access 4101MB (8399520 512 byte sectors) > ncr0 rev 18 int a irq 15 on pci0:11 > ncr0 waiting for scsi devices to settle > (ncr0:0:0): "CONNER CFP1060S 1.05GB 245F" type 0 fixed SCSI 2 > sd3(ncr0:0:0): Direct-Access > sd3(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. > 1010MB (2070400 512 byte sectors) > (ncr0:1:0): "CONNER CFP1060S 1.05GB 2035" type 0 fixed SCSI 2 > sd4(ncr0:1:0): Direct-Access > sd4(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. > 1013MB (2074880 512 byte sectors) > (ncr0:4:0): "QUANTUM EMPIRE_1080S 1101" type 0 fixed SCSI 2 > sd5(ncr0:4:0): Direct-Access > sd5(ncr0:4:0): FAST SCSI-2 125ns (8 Mb/sec) offset 8. > 1029MB (2109376 512 byte sectors) > Probing for devices on the ISA bus: > scprobe: keyboard won't accept RESET command > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA color <16 virtual consoles, flags=0x0> > ed0 at 0x280-0x29f irq 5 on isa > ed0: address 00:80:48:a9:42:ee, type NE2000 (16 bit) > sio0 at 0x3f8-0x3ff irq 4 on isa > sio0: type 16550A > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: NEC 72065B > fd0: 1.44MB 3.5in > npx0 on motherboard > npx0: INT 16 interface > ccd0-3: Concatenated disk drivers > What is a 510? The lowest number NCR/Symbios Logic chip I've dealt with is the 53C810. Is this an old ISA based card? If so, it's probably not very good for hard disks. ----------------------------------------- The only constant in computers is change. David W. Alderman dave@persprog.com ----------------------------------------- From owner-freebsd-hardware Wed Mar 5 15:28:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA19310 for hardware-outgoing; Wed, 5 Mar 1997 15:28:39 -0800 (PST) Received: from os.inf.tu-dresden.de (os.inf.tu-dresden.de [141.76.1.46]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA19301; Wed, 5 Mar 1997 15:28:29 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by os.inf.tu-dresden.de (8.8.5/8.8.5) with ESMTP id AAA14076; Thu, 6 Mar 1997 00:20:54 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA23655; Thu, 6 Mar 1997 00:20:54 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id XAA02175; Wed, 5 Mar 1997 23:57:15 +0100 (MET) Message-ID: Date: Wed, 5 Mar 1997 23:57:15 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: marck@gw.rinet.ru (Dmitry Morozovsky) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: NCR 510 troubles References: <199703051649.TAA29903@gw.rinet.ru> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199703051649.TAA29903@gw.rinet.ru>; from Dmitry Morozovsky on Mar 5, 1997 19:49:33 +0300 Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Dmitry Morozovsky wrote: > After upgrading newsserver from cnews to inn, > regularly, there are very sad things such as: > > Mar 5 16:38:50 gw2 /kernel: ncr0: restart (ncr dead ?). > Mar 5 16:38:51 gw2 /kernel: sd5(ncr0:4:0): UNIT ATTENTION asc:29,0 > Mar 5 16:38:51 gw2 /kernel: sd5(ncr0:4:0): Power on, reset, or bus device reset occurred > Mar 5 16:38:51 gw2 /kernel: , retries:3 > Mar 5 16:38:51 gw2 /kernel: sd3(ncr0:0:0): UNIT ATTENTION asc:29,0 > Mar 5 16:38:51 gw2 /kernel: sd3(ncr0:0:0): Power on, reset, or bus device reset occurred field replaceable unit: 14 Normally, this wouldn't even lead to a crash. I've got a flakey disk that i can often ``cure'' by powering it off... after which i also see the unit attention, where the next retry will get everything back online. If it crashes for you, and the unit attentions appear all of a sudden, i suspect you've got a broken (or overloaded) power supply. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hardware Wed Mar 5 16:25:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA24513 for hardware-outgoing; Wed, 5 Mar 1997 16:25:12 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA24485; Wed, 5 Mar 1997 16:25:05 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id KAA07675; Thu, 6 Mar 1997 10:54:45 +1030 (CST) From: Michael Smith Message-Id: <199703060024.KAA07675@genesis.atrad.adelaide.edu.au> Subject: Re: NCR 510 troubles In-Reply-To: <199703051649.TAA29903@gw.rinet.ru> from Dmitry Morozovsky at "Mar 5, 97 07:49:33 pm" To: marck@gw.rinet.ru (Dmitry Morozovsky) Date: Thu, 6 Mar 1997 10:54:45 +1030 (CST) Cc: freebsd-scsi@freebsd.org, freebsd-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 Dmitry Morozovsky stands accused of saying: > > After upgrading newsserver from cnews to inn, > regularly, there are very sad things such as: > > Mar 5 16:38:50 gw2 /kernel: ncr0: restart (ncr dead ?). > Mar 5 16:38:51 gw2 /kernel: sd5(ncr0:4:0): UNIT ATTENTION asc:29,0 > Mar 5 16:38:51 gw2 /kernel: sd5(ncr0:4:0): Power on, reset, or bus device reset occurred > Mar 5 16:38:51 gw2 /kernel: , retries:3 > Mar 5 16:38:51 gw2 /kernel: sd3(ncr0:0:0): UNIT ATTENTION asc:29,0 > Mar 5 16:38:51 gw2 /kernel: sd3(ncr0:0:0): Power on, reset, or bus device reset occurred field replaceable unit: 14 > Mar 5 16:38:51 gw2 /kernel: , retries:3 > Mar 5 16:38:51 gw2 /kernel: sd5(ncr0:4:0): FAST SCSI-2 125ns (8 Mb/sec) offset 8. > Mar 5 16:38:57 gw2 /kernel: ncr0: restart (ncr dead ?). > Mar 5 16:38:58 gw2 /kernel: sd3(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. > Mar 5 16:38:58 gw2 /kernel: sd5(ncr0:4:0): FAST SCSI-2 125ns (8 Mb/sec) offset 8. > Mar 5 16:38:58 gw2 /kernel: sd4(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. > Mar 5 16:38:58 gw2 /kernel: sd4(ncr0:1:0): UNIT ATTENTION asc:29,0 > Mar 5 16:38:58 gw2 /kernel: sd4(ncr0:1:0): Power on, reset, or bus device reset occurred field replaceable unit: 14 > Mar 5 16:38:58 gw2 /kernel: , retries:4 > > then system either crashes or one of ncr disks become missing. You don't say anything about your hardware setup (case, PSU, fans etc.), but I'd start by checking that your disks aren't overheating, that the PSU is holding up OK (with that many disks a 'normal' PC PSU just won't cut it). INN has much higher expectations of your disks than C-news does, and the extra work may be more than your farm can handle. Another item worth checking is your power supply connections, although with so many disks failing, unless you are using a mess of Y-splitter power cables I don't think that'd be the cause. -- ]] 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 Wed Mar 5 16:28:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA24838 for hardware-outgoing; Wed, 5 Mar 1997 16:28:02 -0800 (PST) Received: from gw.rinet.ru (gw.rinet.ru [194.87.171.65]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA24771 for ; Wed, 5 Mar 1997 16:27:46 -0800 (PST) Received: from marck.rinet.ru by gw.rinet.ru with SMTP id DAA06042; (8.6.11/vak/1.9) Thu, 6 Mar 1997 03:24:12 +0300 Message-ID: <331E0E96.42F9@rinet.ru> Date: Thu, 06 Mar 1997 03:23:50 +0300 From: Dmitry Morozovsky Organization: Cronyx Ltd. X-Mailer: Mozilla 3.01Gold (Win95; I) MIME-Version: 1.0 To: Joerg Wunsch CC: freebsd-hardware@freebsd.org Subject: Re: NCR 810 troubles References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > > As Dmitry Morozovsky wrote: > > > After upgrading newsserver from cnews to inn, > > regularly, there are very sad things such as: > > > > Mar 5 16:38:50 gw2 /kernel: ncr0: restart (ncr dead ?). > > Mar 5 16:38:51 gw2 /kernel: sd5(ncr0:4:0): UNIT ATTENTION asc:29,0 > > Mar 5 16:38:51 gw2 /kernel: sd5(ncr0:4:0): Power on, reset, or bus device reset occurred > > Mar 5 16:38:51 gw2 /kernel: , retries:3 > > Mar 5 16:38:51 gw2 /kernel: sd3(ncr0:0:0): UNIT ATTENTION asc:29,0 > > Mar 5 16:38:51 gw2 /kernel: sd3(ncr0:0:0): Power on, reset, or bus device reset occurred field replaceable unit: 14 > > Normally, this wouldn't even lead to a crash. I've got a flakey disk > that i can often ``cure'' by powering it off... after which i also see > the unit attention, where the next retry will get everything back > online. > > If it crashes for you, and the unit attentions appear all of a sudden, > i suspect you've got a broken (or overloaded) power supply. First, there was mistype with model name. Second, power supply is definitely *not* overloaded, because it is separated in external SCSI box and used only for these 3 disks. Maybe, however, there's one of 3 disks partially broken with power connector; however, it was used for long time previously at other place and never fails. I'll check whether single disk disappears... Sincerely, D.Marck From owner-freebsd-hardware Wed Mar 5 22:07:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA16872 for hardware-outgoing; Wed, 5 Mar 1997 22:07:39 -0800 (PST) Received: from lugh.kerris.com (lugh.kerris.com [205.150.35.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id WAA16845 for ; Wed, 5 Mar 1997 22:07:34 -0800 (PST) Received: from localhost (mkerr@localhost) by lugh.kerris.com (8.6.12/8.6.12) with SMTP id BAA00323; Thu, 6 Mar 1997 01:08:39 -0500 Date: Thu, 6 Mar 1997 01:08:38 -0500 (EST) From: Mike Kerr To: Michael Smith cc: freebsd-hardware@freebsd.org Subject: Re: Problems with 2.1 Probe? In-Reply-To: <199703050019.KAA18729@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 Tue, 4 Mar 1997, Michael Smith wrote: > Mike Kerr stands accused of saying: > > I've had, on occasion, difficulty with my system probing my modem. I've > > > > modem has been configured to COM3 (sio2) on IRQ 4, with the standard 3e8 > > base address. > > > > It's getting *really* frustrating. I've even tried changing the IRQ on > > this latest attempt to IRQ 3, but it still won't detect it. The machine > > I'm running is a 386DX-40 with 8M RAM. > > Neither IRQ 3 nor 4 are available if you have sio0 or sio1 respectively > configured; you will have to use a different interrupt in that case. I have disabled sio0 and sio1 in every configuration because I don't use them. I've tried booting with my normal kernel, with the kernel.old, and with the generic kernel. > > Is anybody aware of any incompatibilities with 386 motherboards and fast > > COM ports, or if the probe has problems, or if there is a way I can > > bypass the probe to get the thing to work? > > If your modem is an internal unit, and it does not have a _real_ UART > on the board, it's likely that it is too _slow_, and the 2.1 sio > probe is giving up on it. You could try booting a 2.2 installation > disk to see if it finds it, once you have fixed your interrupt problem. I'll try that. The modem is a 33,600 modem, one of the new ones, although a noname. The 28.8 I used was a Boca, though exhibited similar problems. Interestingly though, I am able to get it to detect fine if I a) boot with kernel.GENERIC and b) remove the ethernet card. Ethernet card IRQ: 10 Base: 0x280 Modem IRQ: 5 Base: 0x3E8 There should be no conflict here, yet if I boot with the generic kernel and not have the ethernet card plugged in, it works. If I plug the card it, it doesn't. Similar config does not work on subsequent kernel builds other than generic. If it would help, I could email you my kernel config file. Perhaps I've done something nutsy in it that I've overlooked, but I don't think so. > > Oddly enough, if I boot into my DOS partition and use something like > > Telemate, it works fine. > > DOS communications programs have very low expectations of serial hardware. > You could probably jam a digestive biscuit into an ISA slot and log on > to your favorite BBS with it, but that won't work too well with the > BSD sio driver. You've got a point. :) I've seen DOS terms that completely ignore the IRQ... Thanks! Mike. =-=-=-=-=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=-=-=-=-= Mike Kerr | http://www.net/~mkerr Kerr Information Systems | http://www.kerris.com/ mkerr@kerris.com | Web Guy, etc. From owner-freebsd-hardware Wed Mar 5 22:12:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA18021 for hardware-outgoing; Wed, 5 Mar 1997 22:12:53 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA17988 for ; Wed, 5 Mar 1997 22:12:46 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id QAA10999; Thu, 6 Mar 1997 16:42:22 +1030 (CST) From: Michael Smith Message-Id: <199703060612.QAA10999@genesis.atrad.adelaide.edu.au> Subject: Re: Problems with 2.1 Probe? In-Reply-To: from Mike Kerr at "Mar 6, 97 01:08:38 am" To: mkerr@kerris.com (Mike Kerr) Date: Thu, 6 Mar 1997 16:42:22 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, freebsd-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 Mike Kerr stands accused of saying: > > > It's getting *really* frustrating. I've even tried changing the IRQ on > > > this latest attempt to IRQ 3, but it still won't detect it. The machine > > > I'm running is a 386DX-40 with 8M RAM. > > > > Neither IRQ 3 nor 4 are available if you have sio0 or sio1 respectively > > configured; you will have to use a different interrupt in that case. > > I have disabled sio0 and sio1 in every configuration because I don't use > them. I've tried booting with my normal kernel, with the kernel.old, and > with the generic kernel. I should have been more accurate; if you have physical sio0 or sio1 hardware installed, you generally _cannot_ use IRQ 3 or 4. > I'll try that. The modem is a 33,600 modem, one of the new ones, although > a noname. The 28.8 I used was a Boca, though exhibited similar problems. > Interestingly though, I am able to get it to detect fine if I a) boot with > kernel.GENERIC and b) remove the ethernet card. > > Ethernet card IRQ: 10 Base: 0x280 > Modem IRQ: 5 Base: 0x3E8 > > There should be no conflict here, yet if I boot with the generic kernel > and not have the ethernet card plugged in, it works. If I plug the card > it, it doesn't. Similar config does not work on subsequent kernel builds > other than generic. Weird. What sort of ethernet card? > If it would help, I could email you my kernel config file. Perhaps I've > done something nutsy in it that I've overlooked, but I don't think so. I'd be happy to have a look at it, sure. -- ]] 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 Thu Mar 6 00:06:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA03032 for hardware-outgoing; Thu, 6 Mar 1997 00:06:02 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA03026 for ; Thu, 6 Mar 1997 00:05:58 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id TAA27421; Thu, 6 Mar 1997 19:03:51 +1100 Date: Thu, 6 Mar 1997 19:03:51 +1100 From: Bruce Evans Message-Id: <199703060803.TAA27421@godzilla.zeta.org.au> To: mkerr@kerris.com, msmith@atrad.adelaide.edu.au Subject: Re: Problems with 2.1 Probe? Cc: freebsd-hardware@freebsd.org Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> I have disabled sio0 and sio1 in every configuration because I don't use >> them. I've tried booting with my normal kernel, with the kernel.old, and >> with the generic kernel. > >I should have been more accurate; if you have physical sio0 or sio1 hardware >installed, you generally _cannot_ use IRQ 3 or 4. Wrong. sio provides full support for using sio0 and sio1 in polled mode and sio2 and sio3 in interrupt mode, and vice versa, when they have the usual IRQ4 and IRQ3 interrupt conflict (configure a null irq to get polled mode). Just disabling the ones that you don't want to use usually works too (it depends how the BIOS and/or the previously running OS left them). >> I'll try that. The modem is a 33,600 modem, one of the new ones, although >> a noname. The 28.8 I used was a Boca, though exhibited similar problems. >> Interestingly though, I am able to get it to detect fine if I a) boot with >> kernel.GENERIC and b) remove the ethernet card. >> >> Ethernet card IRQ: 10 Base: 0x280 >> Modem IRQ: 5 Base: 0x3E8 >> >> There should be no conflict here, yet if I boot with the generic kernel >> and not have the ethernet card plugged in, it works. If I plug the card >> it, it doesn't. Similar config does not work on subsequent kernel builds >> other than generic. Someone reported serious serial data loss caused by some non-obvious conflict with an old ethernet card. Unfortunately :-) the probe worked. Bruce From owner-freebsd-hardware Thu Mar 6 08:17:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA26374 for hardware-outgoing; Thu, 6 Mar 1997 08:17:29 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA26369 for ; Thu, 6 Mar 1997 08:17:26 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA14501; Thu, 6 Mar 1997 09:17:18 -0700 (MST) Date: Thu, 6 Mar 1997 09:17:18 -0700 (MST) Message-Id: <199703061617.JAA14501@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Bruce Evans Cc: freebsd-hardware@freebsd.org Subject: Re: Problems with 2.1 Probe? In-Reply-To: <199703060803.TAA27421@godzilla.zeta.org.au> References: <199703060803.TAA27421@godzilla.zeta.org.au> Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > sio provides full support for using sio0 and sio1 in polled mode > and sio2 and sio3 in interrupt mode ... > (configure a null irq to get polled mode) How does one configure a null IRQ? In the kernel config? In the boot config? Nate From owner-freebsd-hardware Thu Mar 6 08:38:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA27708 for hardware-outgoing; Thu, 6 Mar 1997 08:38:21 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA27697 for ; Thu, 6 Mar 1997 08:38:17 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id DAA09437; Fri, 7 Mar 1997 03:33:17 +1100 Date: Fri, 7 Mar 1997 03:33:17 +1100 From: Bruce Evans Message-Id: <199703061633.DAA09437@godzilla.zeta.org.au> To: bde@zeta.org.au, nate@mt.sri.com Subject: Re: Problems with 2.1 Probe? Cc: freebsd-hardware@freebsd.org Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> (configure a null irq to get polled mode) > >How does one configure a null IRQ? In the kernel config? In the boot >config? Like this: "". Bruce From owner-freebsd-hardware Thu Mar 6 12:00:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA07907 for hardware-outgoing; Thu, 6 Mar 1997 12:00:05 -0800 (PST) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA07841; Thu, 6 Mar 1997 11:59:45 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr2-41.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA20411 (5.67b/IDA-1.5); Thu, 6 Mar 1997 20:59:39 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id UAA04017; Thu, 6 Mar 1997 20:58:56 +0100 (CET) Message-Id: <19970306205735.TD54148@x14.mi.uni-koeln.de> Date: Thu, 6 Mar 1997 20:57:35 +0100 From: se@freebsd.org (Stefan Esser) To: marck@gw.rinet.ru (Dmitry Morozovsky) Cc: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: NCR 510 troubles References: <199703051649.TAA29903@gw.rinet.ru> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 In-Reply-To: <199703051649.TAA29903@gw.rinet.ru>; from Dmitry Morozovsky on Mar 5, 1997 19:49:33 +0300 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mar 5, marck@gw.rinet.ru (Dmitry Morozovsky) wrote: > Hello there. > > We've got news server (2.1.5, partially upgraded to .7 -- at least, kernel > sources upgraded fully) with onboard ahc & additional ncr 510, which holds 3 > disks with a ccd on it. ncr configured for 2 tags on bootup. > > After upgrading newsserver from cnews to inn, > regularly, there are very sad things such as: > > Mar 5 16:38:50 gw2 /kernel: ncr0: restart (ncr dead ?). > Mar 5 16:38:51 gw2 /kernel: sd5(ncr0:4:0): UNIT ATTENTION asc:29,0 > Mar 5 16:38:51 gw2 /kernel: sd5(ncr0:4:0): Power on, reset, or bus device reset occurred > then system either crashes or one of ncr disks become missing. > (ahc0:0:0): "CONNER CFP1060S 1.05GB 2135" type 0 fixed SCSI 2 > (ahc0:1:0): "CONNER CFP2105S 2.14GB 2B4B" type 0 fixed SCSI 2 > (ahc0:2:0): "Quantum XP34300 81HB" type 0 fixed SCSI 2 > (ncr0:0:0): "CONNER CFP1060S 1.05GB 245F" type 0 fixed SCSI 2 > (ncr0:1:0): "CONNER CFP1060S 1.05GB 2035" type 0 fixed SCSI 2 > (ncr0:4:0): "QUANTUM EMPIRE_1080S 1101" type 0 fixed SCSI 2 > Any proposals? Hmmm, this is quite a number of disk drives ... Are they all mounted in the same case and connected to the same power supply ? Are you sure, your power supply is capable of delivering sufficient 12V current, if all drives are seeking at a time ? I guess that your seek rate increased when switching from c-news to inn, and since you are using ccd, there is a very high probability, that all drives are seeking at the same instance of time. This may lead to current spikes, which possibly overload your power supply ... I have ordered a new play-ground system for NCR driver tests and development, which hopefully will be delivered soon (finally). Improving the recovery from error situations is on top of my ToDo list, actually. But my current job does in part depend on the fact, that my (currently only) system is working reliably and without disruption, and as you can imagine, this prevents me from doing any driver tests :) BTW: You should upgrade from 2.1.5, for various reasons, and you'll find, that the NCR driver has become more reliable in case of a transient hardware failure, than it used to be. This is in part due to changes in the generic SCSI code, and I'm not sure, whether those made it into 2.1.7, but at least under 2.2, many more error situations should not be fatal. Regards, STefan From owner-freebsd-hardware Thu Mar 6 13:19:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA12265 for hardware-outgoing; Thu, 6 Mar 1997 13:19:46 -0800 (PST) Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA12255 for ; Thu, 6 Mar 1997 13:19:38 -0800 (PST) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by pahtoh.cwu.edu (8.6.13/8.6.9) with ESMTP id NAA01504 for ; Thu, 6 Mar 1997 13:19:35 -0800 Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.5/8.8.5) with SMTP id NAA20006 for ; Thu, 6 Mar 1997 13:19:35 -0800 (PST) Date: Thu, 6 Mar 1997 13:19:35 -0800 (PST) From: Chris Timmons To: freebsd-hardware@freebsd.org Subject: p5 mb supporting 36 chip 16x36 simms - tyan? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We've been using a particular model of 16x36 64MB simm (implemented with 36 chips) on the p6np5 natoma motherboards very successfully. Unfortunately, the p55t2p4 boards require no more than 24 chips per module. Do any of the tyan boards support modules with > 24 chips, or is this a triton-ii issue which natoma is immune from? I was hoping to be able to get 256MB into a p55t2p4 :( -Chris From owner-freebsd-hardware Thu Mar 6 16:53:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA26127 for hardware-outgoing; Thu, 6 Mar 1997 16:53:23 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA26116 for ; Thu, 6 Mar 1997 16:53:16 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA15526; Fri, 7 Mar 1997 11:20:46 +1030 (CST) From: Michael Smith Message-Id: <199703070050.LAA15526@genesis.atrad.adelaide.edu.au> Subject: Re: Problems with 2.1 Probe? In-Reply-To: <199703061617.JAA14501@rocky.mt.sri.com> from Nate Williams at "Mar 6, 97 09:17:18 am" To: nate@mt.sri.com (Nate Williams) Date: Fri, 7 Mar 1997 11:20:45 +1030 (CST) Cc: bde@zeta.org.au, freebsd-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 Nate Williams stands accused of saying: > > sio provides full support for using sio0 and sio1 in polled mode > > and sio2 and sio3 in interrupt mode > ... > > (configure a null irq to get polled mode) > > How does one configure a null IRQ? In the kernel config? In the boot > config? You don't specify one in the kernel config. In normal userconfig, set the IRQ to zero. In visual userconfig hit 'x' to get the 'auto' mode. (Did that get committed to 2.2? I can't remember.) > Nate -- ]] 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 Fri Mar 7 02:40:01 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA02399 for hardware-outgoing; Fri, 7 Mar 1997 02:40:01 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA02394 for ; Fri, 7 Mar 1997 02:39:55 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id VAA11380; Fri, 7 Mar 1997 21:29:30 +1100 Date: Fri, 7 Mar 1997 21:29:30 +1100 From: Bruce Evans Message-Id: <199703071029.VAA11380@godzilla.zeta.org.au> To: msmith@atrad.adelaide.edu.au, nate@mt.sri.com Subject: Re: Problems with 2.1 Probe? Cc: bde@zeta.org.au, freebsd-hardware@freebsd.org Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> How does one configure a null IRQ? In the kernel config? In the boot >> config? > >You don't specify one in the kernel config. In normal userconfig, set >the IRQ to zero. In visual userconfig hit 'x' to get the 'auto' mode. >(Did that get committed to 2.2? I can't remember.) Actually, in normal userconfig, you type ls to get some examples and then follow one of the examples and set the irq to -1 (irq 0 is for the clock). In visual userconfig you give up and send mail to Mike, since the changes for auto mode haven't been committed to -current. Bruce From owner-freebsd-hardware Fri Mar 7 19:47:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA14421 for hardware-outgoing; Fri, 7 Mar 1997 19:47:25 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA14414 for ; Fri, 7 Mar 1997 19:47:23 -0800 (PST) Received: from starbase.globalpc.net ([207.211.100.102]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id SAA02302 for ; Fri, 7 Mar 1997 18:07:56 -0800 (PST) Received: (from agonzalez@localhost) by starbase.globalpc.net (8.8.3/8.8.3) id UAA27417; Fri, 7 Mar 1997 20:16:50 -0600 (CST) Date: Fri, 7 Mar 1997 20:16:49 -0600 (CST) From: Adrian Gonzalez To: freebsd-hardware@freebsd.org Subject: Finding the IRQ# for an NE2000 ethernet card Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello everybody I have a bunch of NE-2000 compatible jumperless ethernet cards, but I have no software or manuals for them. They get detected at port 0300h just fine, but I believe I'm not getting the irq # right, as I keep getting "ed0: device timeout" when I try to configure them (with ifconfig). I have tried irq 5 and irq 3 so far, and keep getting the same timeouts. Is there any easy way to check which irq they're set to? Even if it means using some DOS utility program, it would be better than recompiling kernels for several irq's. The card itself doesn't give much insight as to who makes it, etc. I doubt anybody will be able to tell from this, but I'll include the relevant stuff written on the card: 2000JA VER 1.1 307A A 'YES Netware Tested and Approved' logo two UMC chips three Fil-Mag "chips" And some other misc text such as: this equipment complies with fcc class a made in taiwan R.O.C. :-) Any help would be greatly appreciated, as I have like 8 of these cards lying around unused. thanks -Adrian From owner-freebsd-hardware Fri Mar 7 19:52:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA15847 for hardware-outgoing; Fri, 7 Mar 1997 19:52:53 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA15827 for ; Fri, 7 Mar 1997 19:52:48 -0800 (PST) Received: from atlantis.ping.at (a013.static.Vienna.AT.EU.net [193.154.186.13]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id OAA01316 for ; Fri, 7 Mar 1997 14:58:30 -0800 (PST) Received: from atlantis (localhost.ping.at [127.0.0.1]) by atlantis.ping.at (8.7.6/8.6.12) with SMTP id XAA00266; Fri, 7 Mar 1997 23:54:31 +0100 (MET) Message-ID: <33209CA7.41C67EA6@ping.at> Date: Fri, 07 Mar 1997 23:54:31 +0100 From: "Helmut F. Wirth" X-Mailer: Mozilla 3.0 (X11; I; FreeBSD 2.1.7-RELEASE i386) MIME-Version: 1.0 To: jkh@time.cdrom.com CC: freebsd-hardware@freebsd.org Subject: Updates for Quantum ATLAS, a question Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I have a problem with a new Quantum ATLAS XP32150W (2GB, Wide). Since there was some talk about firmware upgrades I thought to ask about my problem. The problem is *not* a FreeBSD problem, but see below: My SCSI configuration: AHA 2940U (Not wide!), BIOS 1.23, 7880 chipset Quantum ATLAS XP31250 (An older 2GB model, NOT wide), works fine IBM OEM 1GB (Older disk), works fine Quantum ATLAS XP31250W has a problem, see below Plextor 12x CDROM works fine HP 6020 CD Writer, works fine IOMEGA JAZ drive, works fine Archive Viper Tape (SCSI I) works fine. The XP31250W has an adapter attached, so I can use it on an 8 bit SCSI bus. The problem: Adaptec BIOS identifies the ATLAS wide, no error messages. But when I try to access it under DOS or Win95, the communication seems to be bad. The ASPI8DOS-driver reports an INT13 routing failure. If I use programs like EZSCSI to look at the mode pages or at the inquiry response I only get nonsense. The second inquiry made by the ASPI8DOS- Driver does not work too, there is nonsense in the response string. It seems the communication between disk and hostadapter is not correct. (Termination is NOT a problem, I checked this. I used a new short cable with the disk as the only device, terminated, and the problem was exactly the same. The rest of the devices on the bus works fine, the Plextor CDROM is normally the last device on the cable and it has an active termination.) BUT: Under FreeBSD-2.1.7 the disk works fine !!! With my old NCR810 adapter, the disk works under DOS and Win95, as expected. With an older Adaptec AHA 2940, BIOS Version 1.21 the disk works too. I think the problem lies with the Adaptec BIOS. I wrote to them, but they were not helpful. Support only said to try a new cable (I did this), try out different BIOS settings, etc. Since FreeBSD uses its own script, the problem does not occur there and this hints strongly at the BIOS. Has anybody seen this problem, or heard of it ? Any solutions or hints ? Do I need a firmware upgrade for my Quantum ATLAS ? I fetched all the files and the tools from ftp.qtnm.com, but there is no information which disks (serial numbers, revisions) are to upgrade. Since I am aware that I easily can render my disk unusable I am very unsure about what to do. Has somebody more information ? Thanks for any help! -- Helmut F. Wirth Email: hfwirth@ping.at From owner-freebsd-hardware Sat Mar 8 01:38:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA03334 for hardware-outgoing; Sat, 8 Mar 1997 01:38:54 -0800 (PST) Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA03325 for ; Sat, 8 Mar 1997 01:38:47 -0800 (PST) Received: from father.ludd.luth.se (dateck@father.ludd.luth.se [130.240.16.18]) by zed.ludd.luth.se (8.8.5/8.8.5) with ESMTP id KAA21962; Sat, 8 Mar 1997 10:38:18 +0100 From: Tomas Klockar Received: (dateck@localhost) by father.ludd.luth.se (8.6.11/8.6.11) id KAA19671; Sat, 8 Mar 1997 10:38:21 +0100 Message-Id: <199703080938.KAA19671@father.ludd.luth.se> Subject: Re: Finding the IRQ# for an NE2000 ethernet card To: agonzalez@starbase.globalpc.net (Adrian Gonzalez) Date: Sat, 8 Mar 1997 10:38:21 +0100 (MET) Cc: freebsd-hardware@freebsd.org In-Reply-To: from Adrian Gonzalez at "Mar 7, 97 08:16:49 pm" X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Adrian Gonzalez: > > Hello everybody > > I have a bunch of NE-2000 compatible jumperless ethernet cards, but I > have no software or manuals for them. They get detected at port 0300h > just fine, but I believe I'm not getting the irq # right, as I keep getting > "ed0: device timeout" when I try to configure them (with ifconfig). I > have tried irq 5 and irq 3 so far, and keep getting the same timeouts. My experience is that people often use 10 as irq for ethernet. Since 3 is the serialport and 5 mostly used for soundcard. > Is there any easy way to check which irq they're set to? Even if it > means using some DOS utility program, it would be better than recompiling > kernels for several irq's. Why recompile your kernel. enter -c at the boot prompt and type visual later Then you can configure your kernel att boot time instead. > The card itself doesn't give much insight as to who makes it, etc. I > doubt anybody will be able to tell from this, but I'll include the > relevant stuff written on the card: > > 2000JA VER 1.1 > 307A > A 'YES Netware Tested and Approved' logo > two UMC chips > three Fil-Mag "chips" > > And some other misc text such as: > this equipment complies with fcc class a > made in taiwan R.O.C. :-) > > Any help would be greatly appreciated, as I have like 8 of these cards > lying around unused. > > thanks > > -Adrian > > Doesn't tell me anything. /Tomas -- Tomas Klockar can be found at the following adresses: Kårhusvägen 4:23 | Furuvägen 102 | dateck@ludd.luth.se 977 54 Luleå | 871 52 Härnösand | dateck@solace.mh.se Tel: +46-920-231335 | Tel: +46-611-13393 | d94-tkl@sm.luth.se From owner-freebsd-hardware Sat Mar 8 11:06:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA26860 for hardware-outgoing; Sat, 8 Mar 1997 11:06:13 -0800 (PST) Received: from tarkhil.dialup.aha.ru (p249-n66.dip.aha.ru [195.2.66.249]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA26844; Sat, 8 Mar 1997 11:06:02 -0800 (PST) Received: from localhost (tarkhil@localhost) by tarkhil.dialup.aha.ru (8.8.5/8.6.9) with SMTP id WAA02963; Sat, 8 Mar 1997 22:02:53 +0300 (MSK) Message-Id: <199703081902.WAA02963@tarkhil.dialup.aha.ru> X-Authentication-Warning: tarkhil.dialup.aha.ru: tarkhil@localhost didn't use HELO protocol To: freebsd-questions@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Tar and Archive FT-60 trouble Reply-To: tarkhil@aha.ru Date: Sat, 08 Mar 1997 22:02:52 +0300 From: Alex Povolotsky Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello! I've suddenly run into trouble: my Archive FT-60 often cannot read good archives from good tapes. With v flag added, it works much better. The thing appeared quite suddenly (most likely after CMOS failure). All my attempts to tune CMOS properly failed. I just have no idea from where to begin digging... Alex.