From owner-freebsd-hardware Sun Mar 24 11:03:22 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA18424 for hardware-outgoing; Sun, 24 Mar 1996 11:03:22 -0800 (PST) Received: from charlotte.spiders.com (charlotte.spiders.com [199.224.7.188]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA18402 Sun, 24 Mar 1996 11:03:16 -0800 (PST) Received: (from gwh@localhost) by charlotte.spiders.com (8.6.12/8.6.12) id OAA18062; Sun, 24 Mar 1996 14:05:50 -0500 Message-Id: <199603241905.OAA18062@charlotte.spiders.com> From: gwh@spiders.com (Gene W Homicki) Date: Sun, 24 Mar 1996 14:05:50 -0500 X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: freebsd-hardware@freebsd.org, freebsd-scsi@freebsd.org Subject: HP C1553A autochanger. Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey all, I have an HP C1553A DDS-2 6 Tape autolaoder/changer. In the docs for the drive, it specifies that that it can ork in changer mode, which "SCSI Medium Changer" commands can be sent. When the machine boots up, its recognized as a SCSI tape drive, but not as a changer device (I have the ch driver compiled into the kernel and I'm running 2.1R). The drive works just fine in "stacker" mode, but I'd be much much happier if I could randomly access cartridges. If anyone has experience with these drives and/or can give me a pointer to docs to get it working, I'd appreciate it. --Gene -- Gene W. Homicki gwh@spiders.com Objective Consulting, Inc. http://www.spiders.com/ Internet Presence Design voice: +1 914.353.3511 From owner-freebsd-hardware Sun Mar 24 12:03:42 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA21608 for hardware-outgoing; Sun, 24 Mar 1996 12:03:42 -0800 (PST) Received: from frig.mt.cs.keio.ac.jp (frig.mt.cs.keio.ac.jp [131.113.32.7]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA21593 Sun, 24 Mar 1996 12:03:37 -0800 (PST) Received: (from hosokawa@localhost) by frig.mt.cs.keio.ac.jp (8.6.12+2.4W/3.4Wbeta3) id FAA00665; Mon, 25 Mar 1996 05:03:31 +0900 Date: Mon, 25 Mar 1996 05:03:31 +0900 Message-Id: <199603242003.FAA00665@frig.mt.cs.keio.ac.jp> To: hackers@freebsd.org, hardware@freebsd.org, gbuchanan@shl.com Subject: [PCMCIA] Megahertz X-Jack Ethernet! From: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.18PL3] 1994-08/01(Mon) Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi! I wrote a pccard enabler for Megahertz X-Jack Ethenet tonight(based on BUCHANAN Gardner's if_sn driver, posted to -hackers a few days ago). It works very fine! (>6Mbps on my Digital Hinote Ultra CS433 via TCP) To drive this card, I forced to modify /sys/pccard and /usr/src/usr.sbin/pccard stuffs tens of lines, and of course I modified if_sn stuff so much. These modifications will be incorporated into the next release of our "pccard-test" package (based on 960323-SNAP). Hmm... I'm sleepy. It's 5:00 AM JST..... I go to bed now. Good night.... -- HOSOKAWA, Tatsumi E-mail: hosokawa@mt.cs.keio.ac.jp WWW homepage: http://www.mt.cs.keio.ac.jp/person/hosokawa.html Department of Computer Science, Keio University, Yokohama, Japan From owner-freebsd-hardware Mon Mar 25 02:21:12 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA11325 for hardware-outgoing; Mon, 25 Mar 1996 02:21:12 -0800 (PST) Received: from kanto.cc.jyu.fi (kallio@kanto.cc.jyu.fi [130.234.1.2]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA11286 Mon, 25 Mar 1996 02:21:01 -0800 (PST) Received: (from kallio@localhost) by kanto.cc.jyu.fi (8.7.2/8.7.2) id MAA22697; Mon, 25 Mar 1996 12:15:41 +0200 (EET) Date: Mon, 25 Mar 1996 12:15:40 +0200 (EET) From: Seppo Kallio To: Gene W Homicki cc: freebsd-hardware@FreeBSD.org, freebsd-scsi@FreeBSD.org Subject: Re: HP C1553A autochanger. In-Reply-To: <199603241905.OAA18062@charlotte.spiders.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 I am trying to use same device with amanda + 2.1R. I have one sh script from Peter Dufault . It is using the scsi-command. It can be used to change the tape randomly. It wokrs even with amanda in 2.2-960303 snap but not in 2.1R. In 2.1R mt -f /dev/nrst0 rewind command after scsi-slot selection command cause all next slot commands to fail. This can be solved by giving 1-2 extra slot selection commands selecting the same slot. #!/bin/sh #From dufault@hda.comThu Feb 29 10:04:36 1996 #Date: Fri, 26 Jan 1996 18:48:44 -0500 (EST) #From: Peter Dufault #To: Seppo Kallio #Cc: questions@freebsd.org, hardware@freebsd.org, # kallio@beeblebrox.pccc.jyu.fi #Subject: Re: HP C1553A Autoloading DDS-2 DAT tape drive control?# # #> #> #> Hi, we have HP C1553A Autoloading DDS2 DAT tape drives attached to #> a FreeBSD node. Is there a program available that would allow me to #> fully manipulate the drive? #> #> I have code for HPUX and Solaris, but it is so OS dependend I cannot #> compile it in FreeBSD.# # #You can use scsi(8) to send commands to the device. Something like #this (I didn't run this - this is a dramatization based on that C #code) saved as dds_changer and made executable. As a raw-device-name #you must use something that accepts the SCSI ioctl calls - the #control device for whatever it comes on line as will. # PATH="/sbin:/usr/sbin:/bin:/usr/bin"; export PATH usage() { echo "(/dev/rst0 for reading/writing, /dev/st0ctl.0 for command)" echo "Usage: dds_changer [123456ne] raw-device-name (/dev/st0ctl.0)" echo "1..6 = Select cartridge" echo "n = next cartridge" echo "e = eject magazine" exit 2 } if [ $# -ne 2 ] ; then usage fi cdb3=0 cdb4=0 cdb5=0 case $1 in [123456]) cdb3=$1 cdb4=1 ;; n) ;; e) cdb5=0x80 ;; ?) usage ;; esac scsi -f $2 -s 100 -c "1b 0 0 v v v" $cdb3 $cdb4 $cdb5 On Sun, 24 Mar 1996, Gene W Homicki wrote: > Hey all, > > I have an HP C1553A DDS-2 6 Tape autolaoder/changer. In the > docs for the drive, it specifies that that it can ork in changer mode, > which "SCSI Medium Changer" commands can be sent. > > When the machine boots up, its recognized as a SCSI tape drive, but > not as a changer device (I have the ch driver compiled into the kernel > and I'm running 2.1R). > > The drive works just fine in "stacker" mode, but I'd be much much > happier if I could randomly access cartridges. If anyone has > experience with these drives and/or can give me a pointer to docs to > get it working, I'd appreciate it. > > > --Gene > > -- > Gene W. Homicki gwh@spiders.com > Objective Consulting, Inc. http://www.spiders.com/ > Internet Presence Design voice: +1 914.353.3511 > From owner-freebsd-hardware Mon Mar 25 05:29:45 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA23702 for hardware-outgoing; Mon, 25 Mar 1996 05:29:45 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA23697 for ; Mon, 25 Mar 1996 05:29:43 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id AAA29950 for hardware@freebsd.org; Tue, 26 Mar 1996 00:17:36 +1030 From: Michael Smith Message-Id: <199603251347.AAA29950@genesis.atrad.adelaide.edu.au> Subject: Intel P-Overdrive and Opti chipsets? To: hardware@freebsd.org Date: Tue, 26 Mar 1996 00:17:35 +1030 (CST) 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 Just wondering if anyone out there is using an Intel PODP5V (83MHz P Overdrive) in a 486 board based on the Opti 82C895. I've got one here that won't work unless the internal cache is disabled, however that yields performance around 1/5 that achieved with a 486DX2/66. Any ideas? (Anyone got one of these bastards working at _all_?) -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Mon Mar 25 07:49:02 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA04530 for hardware-outgoing; Mon, 25 Mar 1996 07:49:02 -0800 (PST) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [199.93.252.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA04508 Mon, 25 Mar 1996 07:48:53 -0800 (PST) Received: (from owensc@localhost) by itsdsv1.enc.edu (8.6.11/8.6.9) id KAA02940; Mon, 25 Mar 1996 10:43:27 -0500 Date: Mon, 25 Mar 1996 10:43:27 -0500 (EST) From: Charles Owens To: Stefan Esser cc: freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: -stable and NCR problems? In-Reply-To: <199603222014.AA02130@Sisyphos> 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 Fri, 22 Mar 1996, Stefan Esser wrote: > That's the infamous handshake timeout ... > This feature seems to do more harm than good, > and I'll apply the following patch to -stable > (it has been in current for some time already): I'm giving the patch a try. >From time to time I also see the following. Is it related to the above problem? Mar 25 07:53:32 dingo /kernel: sd0(ncr0:0:0): M_DISCONNECT received, but datapointer not saved: Mar 25 07:53:32 dingo /kernel: data=2b9d78 save=2b9d78 goal=2b9e8c. Thanks, --- ------------------------------------------------------------------------- Charles Owens Email: owensc@enc.edu "I read somewhere to learn is to Information Technology Services remember... and I've learned that Eastern Nazarene College we've all forgot..." - King's X ------------------------------------------------------------------------- From owner-freebsd-hardware Mon Mar 25 09:24:00 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA13984 for hardware-outgoing; Mon, 25 Mar 1996 09:24:00 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA13975 for ; Mon, 25 Mar 1996 09:23:57 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id JAA04977; Mon, 25 Mar 1996 09:23:41 -0800 From: "Rodney W. Grimes" Message-Id: <199603251723.JAA04977@GndRsh.aac.dev.com> Subject: Re: Intel P-Overdrive and Opti chipsets? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Mon, 25 Mar 1996 09:23:41 -0800 (PST) Cc: hardware@FreeBSD.ORG In-Reply-To: <199603251347.AAA29950@genesis.atrad.adelaide.edu.au> from Michael Smith at "Mar 26, 96 00:17:35 am" X-Mailer: ELM [version 2.4ME+ PL11 (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 > > Just wondering if anyone out there is using an Intel PODP5V > (83MHz P Overdrive) in a 486 board based on the Opti 82C895. > > I've got one here that won't work unless the internal cache is > disabled, however that yields performance around 1/5 that > achieved with a 486DX2/66. > > Any ideas? (Anyone got one of these bastards working at _all_?) I have an idea, it is called WB cache coherency, and it probably was not implemented correctly on your motherboard. Does your bios only allow yot to disable the internal cache, or can you set it to write through mode (like the 486 was). Several motherboards have this as a jumper on the board. This is a common problem with the PODP processors :-( -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-hardware Mon Mar 25 11:14:19 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA26332 for hardware-outgoing; Mon, 25 Mar 1996 11:14:19 -0800 (PST) Received: from sub.Sonic.NET (root@sub.sonic.net [199.4.118.8]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA26319 for ; Mon, 25 Mar 1996 11:14:15 -0800 (PST) Received: from sonic.Sonic.NET (root@sonic.net [199.4.118.11]) by sub.Sonic.NET (8.7.4/8.7.3) with ESMTP id LAA04527 for ; Mon, 25 Mar 1996 11:18:22 -0800 Received: from sonic.net (root@sonic.net [199.4.118.11]) by sonic.Sonic.NET (8.7.4/8.6.10) with SMTP id LAA10439 for ; Mon, 25 Mar 1996 11:13:26 -0800 Received: from rose by sonic.net with uucp (Smail3.1.28.1 #100) id m0u1Hhl-000jTHC; Mon, 25 Mar 96 11:13 PST Received: by thirdeye.com (4.1/SMI-4.1) id AA07514; Mon, 25 Mar 96 10:51:27 PST Date: Mon, 25 Mar 96 10:51:27 PST From: peter@thirdeye.com (Peter Rowell) Message-Id: <9603251851.AA07514@thirdeye.com> To: freebsd-hardware@FreeBSD.ORG Subject: File corruption (Sun=>BSD w/3c590 + vx driver) Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I come seeking wisdom. The problem descibed involves file corruption when copying from a Sun to a BSD machine using NFS, a 3com 3c590 and the if_vx driver code. Please excuse the longish message, but I wanted to give enough specifics that a light might go on in someone's head. Possible culprits (in order of decreasing probability): BSD vx driver for the 3c590 3com 3c590 board BSD nfs server code Sun nfs client code Sun cp command Bad Karma Extremely Selective Cosmic Rays In an exchange with Eric Varsanyi , he mentioned a FIFO overrun problem with certain 3c590 boards. However, his observed pattern of corruption (every other 16-bit word (including the IP headers) 0's) differs markedly from what I am seeing. Suggestions/insights/enlightening ridicule/lunch offers are solicited. TIA, Peter Rowell peter@thirdeye.com ---------------------------------------------------------------------------- The BSD system is fully described below. It is on a network with a Sparc II running SunOS 4.1.3 and a DEC ALPHA running OSF1 V3.2. When I got my new system, I eagerly cross-mounted a bunch of file systems and, from the Sun, did: cp -r /SUN/big/honking/directory/tree /BSD/usr/home/someplace to put a goof-around copy of our product on the BSD machine. Everything seemed to go fine. I rlogin'd to the BSD machine, ran our configure script, and started a make. It immediately started throwing compile errors left and right. I looked at the files involved and noticed that they were all corrupted in a most peculiar way. I did a "diff -r" bewteen the Sun and BSD copies and saw that there were about 200 lines (out of about 130,000 lines) that were corrupted. The corruption was *always* the deletion of 2 characters or the repetition of 2 characters. Sometimes both would happen in the same file. E.g.: In the first case, the ",l" is repeated. In the second case, the "al" is deleted. diff BSD/node.c SUN/node.c 108c108 < {tkCmp, "<=>", asmiNil,l, PvFRelopNode}, --- ^^ 2 repeated characters > {tkCmp, "<=>", asmiNil, PvFRelopNode}, 112c112 < {tkEqu, "==", asmiNil, PvFRelopNode}, --- ^ "al" is missing > {tkEqual, "==", asmiNil, PvFRelopNode}, I tried a number of things and found that this problem manifests consistently (but not with the same files/lines!) when "pushing" from the Sun to the BSD machine using "cp -r". (i.e. I was ON the Sun and was writing TO an NFS mounted filesystem on the BSD machine.) It does NOT happen (apparently) when using FTP. It happened once (I think, have not been able to repeat) when ON the BSD machine I was pulling FROM the Sun. I have not gotten it to happen at all bewteen the Alpha and the BSD machine. I will continue to try combinations to see if there is any other pattern to what is going on. tar-pipe ::= tar cf - /Sun/dir | (cd /nfs/BSD/test ; tar xBf -) Command From Command Host Status ---------------- ---- ------------------------------------- cp -r /SUN /BSD Sun multiple files corrupted cp -r /SUN /BSD BSD OK cp -r /DEC /BSD DEC OK tar-pipe Sun multiple files corrupted tar-pipe BSD multiple files corrupted cp dir.tar Sun Corrupted, no complaints from tar! cp dir.tar BSD OK cp dir.tar DEC OK cp dir.tar.gz Sun OK !?!?!?! cp dir.tar.gz BSD OK cp dir.tar.gz DEC OK ======================================================================== The BSD system is composed of: Motherboard ASUS P55TP4N 512KB pipeline burst cache Pentium-S 150 MHz Memory 32MB, 60ns, no parity video Number Nine 9FX771 w/ 2MB controller ASUS PCI-SC200 (NCR 53c810 chip) disk1 (sd0) Seagate ST32550N, 2.1 GB Barracuda disk2 (sd1) Seagate ST15230N, 4.1 GB Hawk cdrom Plextor PX43CE, 4plex Plus tape HP 1536A 4mm DAT NIC 3Com 3c590 Combo audio Sound Blaster AWE/32 OS FreeBsd 2.1 (Walnut Creek CD-ROM) Using Fred Gray's if_vx driver for the 3c590 board. (Thanks, Fred!) Note that this is the copy from Fred's home page (~ 2/1/96), not the modified one in 2.1-current. From owner-freebsd-hardware Mon Mar 25 11:50:54 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA29869 for hardware-outgoing; Mon, 25 Mar 1996 11:50:54 -0800 (PST) Received: from smtp.munet.edu (smtp.munet.edu [198.109.72.32]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA29850 for ; Mon, 25 Mar 1996 11:50:43 -0800 (PST) Received: from MADONNA-Message_Server by smtp.munet.edu with Novell_GroupWise; Mon, 25 Mar 1996 14:52:43 -0500 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Mon, 25 Mar 1996 14:51:55 -0500 From: CAROL FOX To: freebsd-hardware@freebsd.org Subject: Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk help From owner-freebsd-hardware Mon Mar 25 12:08:42 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA01739 for hardware-outgoing; Mon, 25 Mar 1996 12:08:42 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA01733 for ; Mon, 25 Mar 1996 12:08:39 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id MAA06274; Mon, 25 Mar 1996 12:08:43 -0800 Message-Id: <199603252008.MAA06274@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol To: peter@thirdeye.com (Peter Rowell) cc: freebsd-hardware@FreeBSD.org Subject: Re: File corruption (Sun=>BSD w/3c590 + vx driver) In-reply-to: Your message of "Mon, 25 Mar 1996 10:51:27 PST." <9603251851.AA07514@thirdeye.com> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 25 Mar 1996 12:08:43 -0800 Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Suggestions/insights/enlightening ridicule/lunch offers are solicited. ... >I tried a number of things and found that this problem manifests >consistently (but not with the same files/lines!) when "pushing" from >the Sun to the BSD machine using "cp -r". (i.e. I was ON the Sun and >was writing TO an NFS mounted filesystem on the BSD machine.) It does >NOT happen (apparently) when using FTP. It happened once (I think, Sun, in an attempt to improve performance, violates the UDP RFC and doesn't calculate a checksum on UDP traffic. I suspect what is happening is that you're somehow getting corrupted data from your network (the interface card, the physical layer itself [unlikely - ethernet has a checksum], or whatever) and the data error isn't caught because of the lack of UDP checksum. I believe there is a fairly easy way to turn on the UDP checksumming on the Sun...it might even be documented somewhere. :-) -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hardware Mon Mar 25 13:24:24 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA06124 for hardware-outgoing; Mon, 25 Mar 1996 13:24:24 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA06083 Mon, 25 Mar 1996 13:24:12 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA10508; Mon, 25 Mar 1996 22:22:27 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id WAA12186; Mon, 25 Mar 1996 22:22:28 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id WAA10629; Mon, 25 Mar 1996 22:11:49 +0100 (MET) From: J Wunsch Message-Id: <199603252111.WAA10629@uriah.heep.sax.de> Subject: Re: HP C1553A autochanger. To: kallio@cc.jyu.fi (Seppo Kallio) Date: Mon, 25 Mar 1996 22:11:48 +0100 (MET) Cc: gwh@spiders.com, freebsd-hardware@freebsd.org, freebsd-scsi@freebsd.org In-Reply-To: from "Seppo Kallio" at Mar 25, 96 12:15:40 pm X-Phone: +49-351-2012 669 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 As Seppo Kallio wrote: > > > I am trying to use same device with amanda + 2.1R. I have one sh script from > Peter Dufault . It is using the scsi-command. Peter, any chance to commit this little script? -- 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 Mon Mar 25 13:52:24 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA09044 for hardware-outgoing; Mon, 25 Mar 1996 13:52:24 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA09038 for ; Mon, 25 Mar 1996 13:52:18 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id IAA01095; Tue, 26 Mar 1996 08:39:53 +1030 From: Michael Smith Message-Id: <199603252209.IAA01095@genesis.atrad.adelaide.edu.au> Subject: Re: Intel P-Overdrive and Opti chipsets? To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 26 Mar 1996 08:39:52 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, hardware@FreeBSD.ORG In-Reply-To: <199603251723.JAA04977@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Mar 25, 96 09:23:41 am 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 Rodney W. Grimes stands accused of saying: > > > > > Just wondering if anyone out there is using an Intel PODP5V > > (83MHz P Overdrive) in a 486 board based on the Opti 82C895. > > > > I've got one here that won't work unless the internal cache is > > disabled, however that yields performance around 1/5 that > > achieved with a 486DX2/66. > > > > Any ideas? (Anyone got one of these bastards working at _all_?) > > I have an idea, it is called WB cache coherency, and it probably > was not implemented correctly on your motherboard. Does your bios > only allow yot to disable the internal cache, or can you set it > to write through mode (like the 486 was). Several motherboards > have this as a jumper on the board. The board supports WB mode, and was previously running with it enabled. I'm fairly sure that the cache on the board works OK; it's been running FBSD for over 12mo. with a VLB busmaster SCSI controller. It wouldn't surprise me if the board is wrong, but I tried all of the possible combinations of internal and external cache and WB/WT modes, and the only significant factor was whether the PODP internal cache was on. > This is a common problem with the PODP processors :-( Think I'm resigned to hunting a new MB for this box. *sigh* Thanks for the suggestions. > Rod Grimes rgrimes@gndrsh.aac.dev.com -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Mon Mar 25 14:55:10 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA13419 for hardware-outgoing; Mon, 25 Mar 1996 14:55:10 -0800 (PST) Received: from psiint.com (vv.psiint.com [204.189.53.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA13410 Mon, 25 Mar 1996 14:54:59 -0800 (PST) Received: by psiint.com (8.6.12/4.03) id OAA51741; Mon, 25 Mar 1996 14:49:50 -0800 Date: Mon, 25 Mar 1996 14:49:49 -0800 (PST) From: Dave Walton To: "Andrew V. Stesin" cc: hardware@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: Strange lockup problem In-Reply-To: <199603212108.XAA03313@office.elvisti.kiev.ua> 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 Thu, 21 Mar 1996, Andrew V. Stesin wrote: > [... kbd lockup when switching consoles ...] > > # Any idea what the underlying problem is, and what the cure might be? > > Strange hardware. I remember the rumours this has something > to do with updating the state of kbd "status" LED indicators, > and some brand of kbd controller chips on the MB which has > problems with this. Another source of strange problems > often is hidden in a slightly misconfigured BIOS. > > Probably the author of the driver can tell you more detais, > I'm sending the copy to him. > > # > Sometimes re-plugging of kbd jack cures it (dangerous!) > # > or a command kbdcontrol -r fast < /dev/ttyv0 (issued > # > after coming into the box via telnet). For the sake of completeness, here's a brief recap of the problem: The first symptom appeared immediately after a fresh install of 2.1R, with GENERIC kernel. Switching between vtys would often lock up the keyboard. "kbdcontrol -r normal" reactivates the keyboard, so I set up cron to run that once per minute. The keyboard still locks, but for no more than a minute at a time. I compiled a new kernel, containing psm0, and rebooted. Probing psm0 locks the keyboard, but when cron hits a minute after bootup (see above), that is cleared up. Mouse and keyboard work properly in X. While in X, the keyboard occasionally locks up. Not as repeatably as when switching vtys, but with any key. I've seen it happen while using cursor keys, as well as with other keys. When the keyboard locks up, the mouse freezes as well. A minute later, cron (kbdcontrol) reactivates both mouse and keyboard. (The annoying part of all this is that we've never had a problem with FreeBSD before on any system. And then this happens when we set up a system to convince a client to go with FreeBSD instead of Interactive Unix, which is the worst excuse for a Unix I've ever seen.) > Sorry, David, I have no experience with bus mice and their > possible interaction with kbd controller, still no ideas. > I think that the _exact_ specs of your motherboard > (manufacturer, model name, chipset, output of dmesg(8) after > booting with '-v' switch to the loader) may give some > helpful hints. It's a Dell OptiPlex GXMT 5166 I'd love to give the chip number for the keyboard controller, but I have no idea which chip that is. dmesg output follows: FreeBSD 2.1.0-RELEASE #0: Wed Mar 20 10:19:39 PST 1996 root@myname.my.domain:/usr/src/sys/compile/PSI CPU: 166-MHz Pentium 735\\90 or 815\\100 (Pentium-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 16777216 (16384K bytes) avail memory = 14721024 (14376K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0: disabled, not probed. ed1: disabled, not probed. sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2: disabled, not probed. sio3: disabled, not probed. lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1: disabled, not probed. lpt2: disabled, not probed. mse0: disabled, not probed. psm0 at 0x60-0x63 irq 12 on motherboard fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 1039MB (2128896 sectors), 2112 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, accel, dma, iordis wcd0: 1033Kb/sec, 256Kb cache, audio play, 256 volume levels, ejectable tray wcd0: no disc inside, unlocked wdc1: disabled, not probed. bt0: disabled, not probed. uha0: disabled, not probed. ahc1: disabled, not probed. ahb0: disabled, not probed. aha0: disabled, not probed. aic0: disabled, not probed. nca0: disabled, not probed. nca1: disabled, not probed. sea0: disabled, not probed. wt0: disabled, not probed. mcd0: disabled, not probed. mcd1: disabled, not probed. matcdc0: disabled, not probed. scd0: disabled, not probed. ie0: disabled, not probed. ep0: disabled, not probed. ix0: disabled, not probed. le0: disabled, not probed. lnc0: disabled, not probed. lnc1: disabled, not probed. ze0: disabled, not probed. zp0: disabled, not probed. npx0 on motherboard npx0: INT 16 interface pcibus_setup(1): mode1res=0x80000000 (0x80000000), mode2res=0xff (0x0e) pcibus_setup(2): mode1res=0x80000000 (0x80000000) pcibus_check: device 0 is there (id=122d8086) Probing for devices on the PCI bus: configuration mode 1 allows 32 devices. chip0 rev 2 on pci0:0 chip1 rev 2 on pci0:7 vga0 rev 83 int a irq 9 on pci0:16 mapreg[10] type=0 addr=f8000000 size=4000000. pci0: uses 67108864 bytes of memory from f8000000 upto fbffffff. BIOS Geometries: 0:020e3f3f 0..526=527 cylinders, 0..63=64 heads, 1..63=63 sectors 1:01300311 0..304=305 cylinders, 0..3=4 heads, 1..17=17 sectors 0 accounted for wd0s1: type 0xa5, start 63, end = 2128895, size 2128833 : OK ========================================================================== David Walton Unix Programmer PSI INTERNATIONAL, Inc. email: dwalton@psiint.com 190 South Orchard #C200 Fax :(707)451-6484 Vacaville, CA 95688 Phone:(707)451-3503 ========================================================================== From owner-freebsd-hardware Tue Mar 26 05:54:40 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA05776 for hardware-outgoing; Tue, 26 Mar 1996 05:54:40 -0800 (PST) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [199.93.252.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA05758 for ; Tue, 26 Mar 1996 05:54:37 -0800 (PST) Received: (from owensc@localhost) by itsdsv1.enc.edu (8.6.11/8.6.9) id IAA19582; Tue, 26 Mar 1996 08:54:03 -0500 Date: Tue, 26 Mar 1996 08:54:03 -0500 (EST) From: Charles Owens To: freebsd-hardware@freebsd.org Subject: How to identify ASUS PB-cache modules? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Howdy, I recently bought several sytems containing ASUS P/I-P55TP4XE motherboards. When ordering, I asked for 512k pipline-burst cache. When picking up the systems, I thought to ask if they'd actually given me PB cache. I was told that 512k PB cache modules were not available, and that I'd been given async cache instead (grrrrrr). So, I get the systems back to the office, fire one up, and after all of the usual BIOS messages, I'm greeted with the message "Pipline Burst Cache"!! Can I trust this message? Do I in fact have PB cache? Are the guys who built the system really the yahoos that they seem to be? Taking a look at the module, I see that it bears the label: "CACHE MODULE CM1 REV 1.3". It has 4 Winbond W25P010AF-8 chips and one ISSI IS61C256AH-15J chip. Is this the right beastie? Thanks, --- ------------------------------------------------------------------------- Charles Owens Email: owensc@enc.edu "I read somewhere to learn is to Information Technology Services remember... and I've learned that Eastern Nazarene College we've all forgot..." - King's X ------------------------------------------------------------------------- From owner-freebsd-hardware Tue Mar 26 07:41:53 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA15350 for hardware-outgoing; Tue, 26 Mar 1996 07:41:53 -0800 (PST) Received: from psiint.com (vv.psiint.com [204.189.53.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA15329 Tue, 26 Mar 1996 07:41:45 -0800 (PST) Received: by psiint.com (8.6.12/4.03) id HAA47802; Tue, 26 Mar 1996 07:40:12 -0800 Date: Tue, 26 Mar 1996 07:40:11 -0800 (PST) From: Dave Walton To: Borja Marcos cc: freebsdelm@we.lc.ehu.es, freebsd-hardware@freebsd.org, freebsd-doc@freebsd.org Subject: Re: Magneto-optical disks In-Reply-To: <9603231844.AA15806@sol.we.lc.ehu.es> 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, 23 Mar 1996, Borja Marcos wrote: I think this should probably go into the FAQ or Handbook, and perhaps specifically list the DynaMO on the hardware compatibility list. > Does FreeBSD 2.1 (RELEASE) support Fujitsu DynaMO 230 drives? > If not... does it support any magneto-optical or WORM drive? Yes, it does. Dip switch 4 ("Device mode") has a factory setting of Closed ("Optical"). You need to set it to Open ("HDD"). That done, when you boot with -v, you will see something like: ahc0: target 6 synchronous at 5.0MB/s, offset = 0xf (ahc0:6:0): "FUJITSU M2512A 1314" type 0 removable SCSI 2 sd3(ahc0:6:0): Direct-Access sd3(ahc0:6:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB sks:c0,4 sd3 could not mode sense (4). Using ficticious geometry 217MB (446325 512 byte sectors) sd3(ahc0:6:0): with 217 cyls, 64 heads, and an average 32 sectors/track You can safely ignore the error message, and FreeBSD will treat it as a removable hard drive. On a side note, I've noticed that sysinstall scans all hard drives when it runs, whether or not they are mounted. Because of this, you will not be able to eject the MO while sysinstall is running, even if it is not mounted. Dave ========================================================================== David Walton Unix Programmer PSI INTERNATIONAL, Inc. email: dwalton@psiint.com 190 South Orchard #C200 Fax :(707)451-6484 Vacaville, CA 95688 Phone:(707)451-3503 ========================================================================== From owner-freebsd-hardware Tue Mar 26 09:31:48 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA01472 for hardware-outgoing; Tue, 26 Mar 1996 09:31:48 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA01451 for ; Tue, 26 Mar 1996 09:31:42 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id JAA06836; Tue, 26 Mar 1996 09:31:13 -0800 From: "Rodney W. Grimes" Message-Id: <199603261731.JAA06836@GndRsh.aac.dev.com> Subject: Re: How to identify ASUS PB-cache modules? To: owensc@enc.edu (Charles Owens) Date: Tue, 26 Mar 1996 09:31:12 -0800 (PST) Cc: freebsd-hardware@freebsd.org In-Reply-To: from Charles Owens at "Mar 26, 96 08:54:03 am" X-Mailer: ELM [version 2.4ME+ PL11 (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 > Howdy, > I recently bought several sytems containing ASUS P/I-P55TP4XE motherboards. > When ordering, I asked for 512k pipline-burst cache. When picking up the > systems, I thought to ask if they'd actually given me PB cache. I was > told that 512k PB cache modules were not available, and that I'd been > given async cache instead (grrrrrr). They have been telling you false stories, AAC has been shipping 512K PB modules for 8 months now. > So, I get the systems back to the office, fire one up, and after all of > the usual BIOS messages, I'm greeted with the message "Pipline Burst Cache"!! :-) > > Can I trust this message? Yes. > Do I in fact have PB cache? Yes. > Are the guys who built the system really the yahoos that they seem to be? Most likely. > Taking a look at the module, I see that it bears the label: "CACHE > MODULE CM1 REV 1.3". It has 4 Winbond W25P010AF-8 chips and one ISSI > IS61C256AH-15J chip. Is this the right beastie? Yes, and even the latest revision of the module :-) The W25P010AF-8 chips are 32Kx32 bit PBurst SRAM chips, for 128K bytes of cache each, times 4 of them makes 512K of cache. The IS61C256AH-15J is the tag ram. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-hardware Tue Mar 26 17:02:32 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA20881 for hardware-outgoing; Tue, 26 Mar 1996 17:02:32 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA20865 for ; Tue, 26 Mar 1996 17:02:22 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id KAA06293; Wed, 27 Mar 1996 10:39:28 +1030 From: Michael Smith Message-Id: <199603270009.KAA06293@genesis.atrad.adelaide.edu.au> Subject: Re: How to identify ASUS PB-cache modules? To: owensc@enc.edu (Charles Owens) Date: Wed, 27 Mar 1996 10:39:28 +1030 (CST) Cc: freebsd-hardware@FreeBSD.ORG In-Reply-To: from "Charles Owens" at Mar 26, 96 08:54:03 am 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 Charles Owens stands accused of saying: > > Taking a look at the module, I see that it bears the label: "CACHE > MODULE CM1 REV 1.3". It has 4 Winbond W25P010AF-8 chips and one ISSI > IS61C256AH-15J chip. Is this the right beastie? Sounds like all the PB modules I've seen so far... > Charles Owens Email: owensc@enc.edu -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Tue Mar 26 17:10:50 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA22002 for hardware-outgoing; Tue, 26 Mar 1996 17:10:50 -0800 (PST) Received: from saguaro.flyingfox.com (saguaro.flyingfox.com [204.188.109.253]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA21979 for ; Tue, 26 Mar 1996 17:10:45 -0800 (PST) Received: (from jas@localhost) by saguaro.flyingfox.com (8.6.12/8.6.10) id RAA19327 for hardware@freebsd.org; Tue, 26 Mar 1996 17:07:47 -0800 Date: Tue, 26 Mar 1996 17:07:47 -0800 From: Jim Shankland Message-Id: <199603270107.RAA19327@saguaro.flyingfox.com> To: hardware@freebsd.org Subject: motherboard and Ethernet card recommendations Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I hope this is not so frequently asked a question that I'm being annoying, but I would appreciate any words of wisdom regarding Pentium motherboard and Ethernet card selection for a FreeBSD machine. The criteria for the motherboard are: * rock solid stable; * no buggy chipsets or goofy cache coherency problems; * no weird hardware limitations. The criteria for the Ethernet card are: * rock solid stable; * excellent performance (should be able to keep up with basically a full-speed Ethernet packet stream); * excellent, very stable FreeBSD device driver. A secondary goal is to have a non-brain-damaged BIOS that can be configured so that the machine will boot without a keyboard, and ideally without a graphics card. Note that cost is *not* a primary concern, though of course I'm not intent on spending any money I don't need to. I'd be happy to take responses by email, and summarize to the list, if that's appropriate. Thanks in advance. Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-hardware Tue Mar 26 20:05:48 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA14234 for hardware-outgoing; Tue, 26 Mar 1996 20:05:48 -0800 (PST) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA14219 for ; Tue, 26 Mar 1996 20:05:45 -0800 (PST) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0u1mkT-000wqIC; Tue, 26 Mar 96 20:22 PST Received: from cc:Mail by ccgate.infoworld.com id AA827899497; Tue, 26 Mar 96 20:50:07 PST Date: Tue, 26 Mar 96 20:50:07 PST From: "Brett Glass" Message-Id: <9602268278.AA827899497@ccgate.infoworld.com> To: freebsd-hardware@freebsd.org Subject: Cannot boot after install Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've just installed FreeBSD three times on an EISA system with 20 MB of RAM, an UltraStor 24F SCSI host adapter, and a DEC DSP5200 2 GB hard disk. I can partition the drive and bring in the OS across the Internet, but when I try to reboot after the installation the system fails to bootstrap properly from the hard disk. I've tried swapping the SCSI host adapter with an Adaptec; same results. There do not appear to be any hardware conflicts. I've seen messages on the Net regarding problems with disks over 1 GB -- a problem I had assumed I'd avoided due to sector translation. (Both controllers translate the geometry to look as if it has less than 1024 cylinders.) I've tried installing the BootEasy boot manager and also committing the entire disk to BSD with no standard partition table. What is wrong? Insights from the developers would be especially useful, but ANY answers would be appreciated. --Brett Glass From owner-freebsd-hardware Tue Mar 26 21:04:55 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA19299 for hardware-outgoing; Tue, 26 Mar 1996 21:04:55 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA19294 for ; Tue, 26 Mar 1996 21:04:51 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id VAA07861; Tue, 26 Mar 1996 21:04:23 -0800 From: "Rodney W. Grimes" Message-Id: <199603270504.VAA07861@GndRsh.aac.dev.com> Subject: Re: motherboard and Ethernet card recommendations To: jas@flyingfox.COM (Jim Shankland) Date: Tue, 26 Mar 1996 21:04:22 -0800 (PST) Cc: hardware@freebsd.org In-Reply-To: <199603270107.RAA19327@saguaro.flyingfox.com> from Jim Shankland at "Mar 26, 96 05:07:47 pm" X-Mailer: ELM [version 2.4ME+ PL11 (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 hope this is not so frequently asked a question that I'm being > annoying, but I would appreciate any words of wisdom regarding > Pentium motherboard and Ethernet card selection for a FreeBSD machine. > > The criteria for the motherboard are: > > * rock solid stable; > * no buggy chipsets or goofy cache coherency problems; > * no weird hardware limitations. XX. ASI ASUS-PCI/I-P55TP4N Motherboard w/256K 8nS PBurst SRAM cache $ 210.00 > The criteria for the Ethernet card are: > > * rock solid stable; > * excellent performance (should be able to keep up with > basically a full-speed Ethernet packet stream); > * excellent, very stable FreeBSD device driver. XX. TMG EFA18215 EFA PCI Ethernet Card, 10BaseT & BNC, DC21040 $ 85.00 (Basically _most_ DEC DC21x4x based ethernet cards are okay, but watchout, some of them (Revision D2 and later Compex cards) have used some of the DEC stuff in ways that are very strange and cause you lots of problems, like not working with FreeBSD. > A secondary goal is to have a non-brain-damaged BIOS that can be > configured so that the machine will boot without a keyboard, and > ideally without a graphics card. The keyboard part is no problem, unfortanetly most BIOSes won't go without a video card :-(. > Note that cost is *not* a primary concern, though of course I'm not > intent on spending any money I don't need to. > > I'd be happy to take responses by email, and summarize to the list, > if that's appropriate. > > Thanks in advance. > > Jim Shankland > Flying Fox Computer Systems, Inc. > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-hardware Wed Mar 27 00:24:47 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA06108 for hardware-outgoing; Wed, 27 Mar 1996 00:24:47 -0800 (PST) Received: from pit.telkom.go.id (pit.telkom.go.id [167.205.136.6]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA06052 for ; Wed, 27 Mar 1996 00:23:00 -0800 (PST) Received: (from chandra@localhost) by pit.telkom.go.id (8.6.11/8.6.11) id PAA04098; Wed, 27 Mar 1996 15:27:28 GMT Date: Wed, 27 Mar 1996 15:27:28 +0000 () From: Rizkan Chandra To: hardware@freebsd.org Subject: Compaq Prosignia 300 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 would like to install 2.1.0 on my Compaq Prosignia with NCR 538x SCSI and AMD PCNet 3 Ethernet. The Prosignia has two hard disks on it: 2 Gbytes Compaq and 1 Gbytes Seagate plus one CDROM drive. It seems that 2.1.0 kernel has been failed to recognize both cards. Will the upcoming 2.2.0 correct the problem or does anyone have the drivers for those cards ? Rizkan Chandra Information Technology Research Division PT Telekomunikasi Indonesia Postal Address: Jl. Gegerkalong Hilir 47 Bandung 40152 - INDONESIA From owner-freebsd-hardware Wed Mar 27 01:59:09 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA13088 for hardware-outgoing; Wed, 27 Mar 1996 01:59:09 -0800 (PST) Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA13069 for ; Wed, 27 Mar 1996 01:58:59 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.13/8.6.12) with ESMTP id JAA05514 for ; Wed, 27 Mar 1996 09:56:44 GMT Received: from tees by snowdon with SMTP (PP); Wed, 27 Mar 1996 09:50:40 +0000 Received: (from dpr@localhost) by tees (SMI-8.6/8.6.12) id JAA11703; Wed, 27 Mar 1996 09:56:35 GMT From: Paul Richards Message-Id: <199603270956.JAA11703@tees> Subject: Re: Compaq Prosignia 300 To: chandra@telkom.go.id (Rizkan Chandra) Date: Wed, 27 Mar 1996 09:56:34 +0000 (GMT) Cc: hardware@FreeBSD.org In-Reply-To: from "Rizkan Chandra" at Mar 27, 96 03:27:28 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to Rizkan Chandra who said > > I would like to install 2.1.0 on my Compaq Prosignia with NCR 538x SCSI > and AMD PCNet 3 Ethernet. The Prosignia has two hard disks on it: 2 > Gbytes Compaq and 1 Gbytes Seagate plus one CDROM drive. It seems that > 2.1.0 kernel has been failed to recognize both cards. Will the upcoming > 2.2.0 correct the problem or does anyone have the drivers for those cards ? The PCNet card should work with a few patches that have been floating around. Does anyone know where I can get hold of a PCNet-PCI card? Can't find anyone who sells them around here. I've got hold of an old 4Mb 386 from work to set up a small LAN at home so I can get back to maintaining the Lance driver so if I can get hold of one of these PCI cards I'll finally look at fixing the problem. -- Paul Richards. Originative Solutions Ltd. (Netcraft Ltd. contractor) Elsevier Science TIS online journal project. Email: p.richards@elsevier.co.uk Phone: 0370 462071 (Mobile), +44 (0)1865 843155 From owner-freebsd-hardware Wed Mar 27 06:33:05 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA00770 for hardware-outgoing; Wed, 27 Mar 1996 06:33:05 -0800 (PST) Received: from fire.dkrz.de (fire.dkrz.de [136.172.110.250]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA00721 for ; Wed, 27 Mar 1996 06:32:15 -0800 (PST) Received: from racer.dkrz.de (racer.dkrz.de [136.172.110.55]) by fire.dkrz.de (8.7.4/8.7.3) with ESMTP id PAA16935; Wed, 27 Mar 1996 15:28:12 +0100 (MET) Received: (from gwk@localhost) by racer.dkrz.de (8.7.4/8.7.3) id PAA03923; Wed, 27 Mar 1996 15:25:57 +0100 (MET) Date: Wed, 27 Mar 1996 15:25:57 +0100 (MET) Message-Id: <199603271425.PAA03923@racer.dkrz.de> From: "Georg-W. Koltermann" To: rgrimes@GndRsh.aac.dev.com CC: jas@flyingfox.COM, hardware@FreeBSD.org In-reply-to: <199603270504.VAA07861@GndRsh.aac.dev.com> (rgrimes@GndRsh.aac.dev.com) Subject: Re: motherboard and Ethernet card recommendations Reply-to: gwk@cray.com Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > I hope this is not so frequently asked a question that I'm being > > annoying, but I would appreciate any words of wisdom regarding > > Pentium motherboard and Ethernet card selection for a FreeBSD machine. > > > > The criteria for the motherboard are: > > > > * rock solid stable; > > * no buggy chipsets or goofy cache coherency problems; > > * no weird hardware limitations. > > XX. ASI ASUS-PCI/I-P55TP4N Motherboard w/256K 8nS PBurst SRAM cache $ 210.00 > ... > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation Company Reliable computers for FreeBSD > Wasn't there some talking about buggy UMC chips on that board? Or does the ...TP4N board use different chips than the ...TP4XE? And, BTW, does anyone know if their just-to-be released Motherboards with the 430HX (aka Triton-2) use any buggy chips? I'm about to buy one of those when they've arrived the local dealers. I checked http://192.72.126.1/Products/spec.html and found nothing apparent. Nice pictures, though! Regards, Georg-W. Koltermann, gwk@cray.com > Date: Sat, 24 Feb 1996 08:01:17 +1100 > From: Bruce Evans > Cc: freebsd-bugs@FreeBSD.ORG > Sender: owner-bugs@FreeBSD.ORG > Precedence: bulk > > > >> I have problems with my serials ports. My hardware is an ASUS > > >> P/I-P55TP4XE(2.4 Rev) with an on-board 'Multi-I/O' using the > > >> UMC 8669F Super multi-I/O chip (16550 Fast UART compatible), > > >> and P120, 24Mo, NCR810. > > > >> When I'm using uucp, the chat connexion is well, but the > > >> transfert is very slow (200bps) and it fail. I try 2.0.5R, > > >> 2.1.0R, 2.2-960130-SNAP, it's the same thing. I try the second > > >> serial port at address COM2, COM4 without any more success > > > Bruce> I have the same motherboard and the same problems in > > Bruce> -current. The chat connection often fails too. This seems > > Bruce> to be a hardware bug. The bytes received in siointr1() > > Bruce> when /etc/rc is sent are: > > The bug is that the UART loses sync if it is in the middle of receiving > data when either the fifo enable bit is toggled or the divisor is written > (or perhaps if the divisor latch is toggled). The UART then delivers > garbage until data stops arriving or the UART is reprogrammed at a more > fortunate time. This happens even at 300 bps with the fifo disabled. > > I can almost work around the bug by attempting to only write to the > critical UART registers immediately after data has arrived. This works > best if data is arriving at a high rate. At 300 bps, it requires busy- > waiting with interrupts off for 33msec and if data isn't arriving then > it requires busy-waiting with interrupts off until data arrives :-(. > > While testing this, I found that the Startech (?) 16550's on my other > system are also buggy. If data is being transmitted and received at > full speed (even 300 bps), then some characters are received twice. > > I can work around this bug by delaying for 3.75 usec between reading > the line status register that says that data is available and reading > the data. A delay of 2.5 usec isn't quite enough :-(. Using a fifo > trigger level of 8 instead of 14 may work too. > > > >> I try 'ppp' and it works well. > > > Bruce> zmodem seems to work well too. This might be because the > > Bruce> receiver does less output for acks. > > > >> I try uucp with the same machine on Linux, it works well. > > Apparently ppp, zmodem and Linux don't stress the UART enough :-). `cat' > under Linux-1.2.13 doesn't work well for a stream of data transmitted by > a FreeBSD-current system. -current streams the data better than 2.1 > and maybe Linux. The problem may be more visible at low speeds since > it is easier for the transmitter to avoid dead spots that would allow > the receiver to resynchronize. > > >I got this message on news : > > >) From: peter@citylink.dinoex.sub.org (System Administration) > >) Subject: Taylor-UUCP not running with 16550 SIO (UMC Custom Chip) > > I saw it in news too. > > >) When i got angry about that, i started to change values in the uucp-source. > >) I succeded in libunix/serial.c by disactivating the "setmin" code (it > >) says: "if we can tell the terminal not to return after we have a certain > >) number of characters, do so."). uucico consumes some more CPU power now, > >) but runs with good performance. > >) > >) Explanations, anybody? > > >I comment lines in src/gnu/libexec/uucp/libunix/serial.c (lines 2163-2212) and I have compiled uucico. > >UUCP works well now with the on-board serials ports. > > >But I tell so do you have explanations... > > >I thinks this help anybody else. > > This might work be intoducing dead spots. > > The problem may be more noticeable with uucp because it may do more > TIOCSET* ioctls. (The driver only changes the settings for first-open, > TIOCSET* ioctls, and last-close.) > > Other news suggested fixing slave mode to set CRTSCTS. This also might > work by introducing dead spots. > > Bruce > From owner-freebsd-hardware Wed Mar 27 08:48:34 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA07996 for hardware-outgoing; Wed, 27 Mar 1996 08:48:34 -0800 (PST) Received: from persprog.com (persprog.com [204.215.255.203]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA07988 for ; Wed, 27 Mar 1996 08:48:31 -0800 (PST) Received: by persprog.com (8.7.3/4.10) id LAA15577; Wed, 27 Mar 1996 11:39:37 -0500 Received: from novell(192.2.2.201) by cerberus.ppi.com via smap (V1.3) id sma015575; Wed Mar 27 11:39:31 1996 Received: from NOVELL/SpoolDir by novell.persprog.com (Mercury 1.12); Wed, 27 Mar 96 11:38:34 +0500 Received: from SpoolDir by NOVELL (Mercury 1.12); Wed, 27 Mar 96 11:38:17 +0500 From: "David Alderman" Organization: Personalized Programming, Inc. To: "Rodney W. Grimes" , hardware@freebsd.org Date: Wed, 27 Mar 1996 11:38:16 EST Subject: Re: motherboard and Ethernet card recommendations Priority: normal X-mailer: Pegasus Mail for Windows (v2.23) Message-ID: <22AD11A2E@novell.persprog.com> Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Rodney Grimes recommended: > XX. ASI ASUS-PCI/I-P55TP4N Motherboard w/256K 8nS PBurst SRAM cache $ 210.00 > XX. TMG EFA18215 EFA PCI Ethernet Card, 10BaseT & BNC, DC21040 $ 85.00 Note: lots o' useful information omitted. This is a Triton board, isn't it? We have had a horrible time with an ASUS PCI/I-P55TP4XE and an SMC PCI network card that I think uses the DC21040 chipset. Unfortunately, for this apllication we are running (please, don't hit me!) SCO Open Server. A typical netstat -i shows: > netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll net1 1500 192.2.2 meddml 11852554 120 12836553 275265 138074 lo0 8232 loopback localhost 149531 0 149531 0 0 A machine on the same subnet with the ASUS Neptune board and an EISA network card has no such problem with Ierrs Oerrs or Collisions. I know this doesn't have much bearing on FreeBSD but I would appreciate any advice you could give. Would the TP4N work better? Would the TMG card be a better choice than SMC? If I could use FreeBSD on this machine I would (and I bet it would solve our problems ;) ). Thanks. ====================================== When philosophy conflicts with reality, choose reality. Dave Alderman -- dave@persprog.com ====================================== From owner-freebsd-hardware Wed Mar 27 09:20:00 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA10157 for hardware-outgoing; Wed, 27 Mar 1996 09:20:00 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA10141 for ; Wed, 27 Mar 1996 09:19:54 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id JAA08614; Wed, 27 Mar 1996 09:18:26 -0800 From: "Rodney W. Grimes" Message-Id: <199603271718.JAA08614@GndRsh.aac.dev.com> Subject: Re: motherboard and Ethernet card recommendations To: gwk@cray.com Date: Wed, 27 Mar 1996 09:18:25 -0800 (PST) Cc: jas@flyingfox.COM, hardware@FreeBSD.org In-Reply-To: <199603271425.PAA03923@racer.dkrz.de> from "Georg-W. Koltermann" at "Mar 27, 96 03:25:57 pm" X-Mailer: ELM [version 2.4ME+ PL11 (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 hope this is not so frequently asked a question that I'm being > > > annoying, but I would appreciate any words of wisdom regarding > > > Pentium motherboard and Ethernet card selection for a FreeBSD machine. > > > > > > The criteria for the motherboard are: > > > > > > * rock solid stable; > > > * no buggy chipsets or goofy cache coherency problems; > > > * no weird hardware limitations. > > > > XX. ASI ASUS-PCI/I-P55TP4N Motherboard w/256K 8nS PBurst SRAM cache $ 210.00 > > ... > > > > -- > > Rod Grimes rgrimes@gndrsh.aac.dev.com > > Accurate Automation Company Reliable computers for FreeBSD > > > > Wasn't there some talking about buggy UMC chips on that board? Or > does the ...TP4N board use different chips than the ...TP4XE? Some of the TP4XE's used UMC floppy/sio chips that had some annoying timeout problems, but I have not had a real problem with them. I see some stuff below from Bruce that indicates some problem, but not a clear solution. :-(. All the TP5N's that I have seen are using a winbond chip for this function. > And, BTW, does anyone know if their just-to-be released Motherboards > with the 430HX (aka Triton-2) use any buggy chips? I'm about to buy > one of those when they've arrived the local dealers. I checked > http://192.72.126.1/Products/spec.html and found nothing apparent. > Nice pictures, though! Yea, right, how can anyone possibly know if there are buggy chips on it before you can even get your hands on a board :-( :-(. > Regards, > > Georg-W. Koltermann, gwk@cray.com > > > Date: Sat, 24 Feb 1996 08:01:17 +1100 > > From: Bruce Evans > > Cc: freebsd-bugs@FreeBSD.ORG > > Sender: owner-bugs@FreeBSD.ORG > > Precedence: bulk > > > > > >> I have problems with my serials ports. My hardware is an ASUS > > > >> P/I-P55TP4XE(2.4 Rev) with an on-board 'Multi-I/O' using the > > > >> UMC 8669F Super multi-I/O chip (16550 Fast UART compatible), > > > >> and P120, 24Mo, NCR810. > > > > > >> When I'm using uucp, the chat connexion is well, but the > > > >> transfert is very slow (200bps) and it fail. I try 2.0.5R, > > > >> 2.1.0R, 2.2-960130-SNAP, it's the same thing. I try the second > > > >> serial port at address COM2, COM4 without any more success > > > > > Bruce> I have the same motherboard and the same problems in > > > Bruce> -current. The chat connection often fails too. This seems > > > Bruce> to be a hardware bug. The bytes received in siointr1() > > > Bruce> when /etc/rc is sent are: > > > > The bug is that the UART loses sync if it is in the middle of receiving > > data when either the fifo enable bit is toggled or the divisor is written > > (or perhaps if the divisor latch is toggled). The UART then delivers > > garbage until data stops arriving or the UART is reprogrammed at a more > > fortunate time. This happens even at 300 bps with the fifo disabled. > > > > I can almost work around the bug by attempting to only write to the > > critical UART registers immediately after data has arrived. This works > > best if data is arriving at a high rate. At 300 bps, it requires busy- > > waiting with interrupts off for 33msec and if data isn't arriving then > > it requires busy-waiting with interrupts off until data arrives :-(. > > > > While testing this, I found that the Startech (?) 16550's on my other > > system are also buggy. If data is being transmitted and received at > > full speed (even 300 bps), then some characters are received twice. > > > > I can work around this bug by delaying for 3.75 usec between reading > > the line status register that says that data is available and reading > > the data. A delay of 2.5 usec isn't quite enough :-(. Using a fifo > > trigger level of 8 instead of 14 may work too. > > > > > >> I try 'ppp' and it works well. > > > > > Bruce> zmodem seems to work well too. This might be because the > > > Bruce> receiver does less output for acks. > > > > > >> I try uucp with the same machine on Linux, it works well. > > > > Apparently ppp, zmodem and Linux don't stress the UART enough :-). `cat' > > under Linux-1.2.13 doesn't work well for a stream of data transmitted by > > a FreeBSD-current system. -current streams the data better than 2.1 > > and maybe Linux. The problem may be more visible at low speeds since > > it is easier for the transmitter to avoid dead spots that would allow > > the receiver to resynchronize. > > > > >I got this message on news : > > > > >) From: peter@citylink.dinoex.sub.org (System Administration) > > >) Subject: Taylor-UUCP not running with 16550 SIO (UMC Custom Chip) > > > > I saw it in news too. > > > > >) When i got angry about that, i started to change values in the uucp-source. > > >) I succeded in libunix/serial.c by disactivating the "setmin" code (it > > >) says: "if we can tell the terminal not to return after we have a certain > > >) number of characters, do so."). uucico consumes some more CPU power now, > > >) but runs with good performance. > > >) > > >) Explanations, anybody? > > > > >I comment lines in src/gnu/libexec/uucp/libunix/serial.c (lines 2163-2212) and I have compiled uucico. > > >UUCP works well now with the on-board serials ports. > > > > >But I tell so do you have explanations... > > > > >I thinks this help anybody else. > > > > This might work be intoducing dead spots. > > > > The problem may be more noticeable with uucp because it may do more > > TIOCSET* ioctls. (The driver only changes the settings for first-open, > > TIOCSET* ioctls, and last-close.) > > > > Other news suggested fixing slave mode to set CRTSCTS. This also might > > work by introducing dead spots. > > > > Bruce > > > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-hardware Wed Mar 27 09:26:42 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA11308 for hardware-outgoing; Wed, 27 Mar 1996 09:26:42 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA11303 for ; Wed, 27 Mar 1996 09:26:37 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id JAA08629; Wed, 27 Mar 1996 09:25:15 -0800 From: "Rodney W. Grimes" Message-Id: <199603271725.JAA08629@GndRsh.aac.dev.com> Subject: Re: motherboard and Ethernet card recommendations To: dave@persprog.com (David Alderman) Date: Wed, 27 Mar 1996 09:25:15 -0800 (PST) Cc: hardware@freebsd.org In-Reply-To: <22AD11A2E@novell.persprog.com> from David Alderman at "Mar 27, 96 11:38:16 am" X-Mailer: ELM [version 2.4ME+ PL11 (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 > Rodney Grimes recommended: > > > XX. ASI ASUS-PCI/I-P55TP4N Motherboard w/256K 8nS PBurst SRAM cache $ 210.00 > > XX. TMG EFA18215 EFA PCI Ethernet Card, 10BaseT & BNC, DC21040 $ 85.00 > Note: lots o' useful information omitted. > > This is a Triton board, isn't it? Yes, but not all Triton boards are equal, some folks design better artwork than others, some write better bios's than others, etc... > We have had a horrible time with > an ASUS PCI/I-P55TP4XE and an SMC PCI network card that I think uses > the DC21040 chipset. Unfortunately, for this apllication we are > running (please, don't hit me!) SCO Open Server. Your problem is most likely SCO open server, I just did a machine for someone and what a nightmare to get it working! God, they call that a ``commercial'' unix :-( :-(. > A typical netstat -i shows: > > netstat -i > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll > net1 1500 192.2.2 meddml 11852554 120 12836553 275265 138074 > lo0 8232 loopback localhost 149531 0 149531 0 0 > > A machine on the same subnet with the ASUS Neptune board and an EISA > network card has no such problem with Ierrs Oerrs or Collisions. Bad NIC, bad cable? Did you get the latest AHS update and the latest NIC driver from smc's ftp site? > I know this doesn't have much bearing on FreeBSD but I would > appreciate any advice you could give. Would the TP4N work better? There is very very little difference between a tp4xe and a tp4n, basically they took the async cache chips off the MB, added 2 PB cache chips and the tag ram. You upgrade to 512K cache buy installing a 256K _upgrade_ module in the COAST socket. [_upgrade_ is highlighted there, as this is not the same as a standard 256k module, as this special one has no tag ram, and if you try to use the ones that do you end up with 0K cache] > Would the TMG card be a better choice than SMC? Should be the same, and it is an EFA card card, TMG is my distributor code. Under SCO I actually run the EFA card usings SMC's driver, SCO isn't smart enough of a company to do things like the if_de driver, even when DEC gives them the source code to it :-(. > If I could use FreeBSD on this machine I would (and I bet it would > solve our problems ;) ). :-) -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-hardware Wed Mar 27 13:14:49 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA28294 for hardware-outgoing; Wed, 27 Mar 1996 13:14:49 -0800 (PST) Received: from ns.guate.net (NS.GUATE.NET [200.12.63.2]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA28264 for ; Wed, 27 Mar 1996 13:14:35 -0800 (PST) Received: from guate.net ([200.12.63.188]) by ns.guate.net (8.7.1/8.7.1) with SMTP id PAA08699 for ; Wed, 27 Mar 1996 15:27:54 -0600 Date: Wed, 27 Mar 1996 15:27:54 -0600 Message-Id: <199603272127.PAA08699@ns.guate.net> X-Sender: corpotel@guate.net X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: hardware@freebsd.org From: Jose Augusto Sanchez Subject: Unsubscribe!!!! Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I want to Unsubscribe to this list, but I forgot tha address to make this. Somebody could tell me that address? Thank You From owner-freebsd-hardware Wed Mar 27 14:47:20 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA08735 for hardware-outgoing; Wed, 27 Mar 1996 14:47:20 -0800 (PST) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA08648 Wed, 27 Mar 1996 14:46:57 -0800 (PST) Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id UAA01179; Sun, 24 Mar 1996 20:28:32 -0800 (PST) Message-Id: <199603250428.UAA01179@ref.tfs.com> Subject: Re: HP C1553A autochanger. To: gwh@spiders.com (Gene W Homicki) Date: Sun, 24 Mar 1996 20:28:31 -0800 (PST) From: "JULIAN Elischer" Cc: freebsd-hardware@freebsd.org, freebsd-scsi@freebsd.org In-Reply-To: <199603241905.OAA18062@charlotte.spiders.com> from "Gene W Homicki" at Mar 24, 96 02:05:50 pm X-Mailer: ELM [version 2.4 PL25 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 probably the 'changer device' is on a second LUN you will need to add an entry to scsiconf.c for the device (in the registration table, and add the flag SCSI_MORE_LUNS (or however it's spelled) to tell the scsi system to look for another LUN on the device.. then you will also need to configure in the 'ch' device which is the changer device. (see the LINT config file). (I see you've done that) The ioctls to control the changer wre defined in . there are no programs that presently do this so the driver hasn't been TESTED for a few generations, though it compiles fine.. it was last seen running correctly under OSF1 when the scsi system was shared between the two OS's but it has changed under FreeBSD a LOT (understatement) You may need to do debugging to get it going... sorry but i don't have such a changer to rest it on... > > > Hey all, > > I have an HP C1553A DDS-2 6 Tape autolaoder/changer. In the > docs for the drive, it specifies that that it can ork in changer mode, > which "SCSI Medium Changer" commands can be sent. > > When the machine boots up, its recognized as a SCSI tape drive, but > not as a changer device (I have the ch driver compiled into the kernel > and I'm running 2.1R). > > The drive works just fine in "stacker" mode, but I'd be much much > happier if I could randomly access cartridges. If anyone has > experience with these drives and/or can give me a pointer to docs to > get it working, I'd appreciate it. > > > --Gene > > -- > Gene W. Homicki gwh@spiders.com > Objective Consulting, Inc. http://www.spiders.com/ > Internet Presence Design voice: +1 914.353.3511 > From owner-freebsd-hardware Wed Mar 27 15:35:00 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA12299 for hardware-outgoing; Wed, 27 Mar 1996 15:35:00 -0800 (PST) Received: from cocoa.ops.neosoft.com (root@cocoa.ops.neosoft.com [206.109.5.227]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id PAA12276 for ; Wed, 27 Mar 1996 15:34:44 -0800 (PST) Received: (from dbaker@localhost) by cocoa.ops.neosoft.com (8.7.5/8.6.12) id RAA02309; Wed, 27 Mar 1996 17:34:13 -0600 (CST) Date: Wed, 27 Mar 1996 17:34:10 -0600 (CST) From: Daniel Baker X-Sender: dbaker@cocoa.ops.neosoft.com To: Jose Augusto Sanchez cc: hardware@FreeBSD.org Subject: Re: Unsubscribe!!!! In-Reply-To: <199603272127.PAA08699@ns.guate.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk send mail to majordomo@freebsd.org saying unsubcribe freebsd-hardware On Wed, 27 Mar 1996, Jose Augusto Sanchez wrote: > I want to Unsubscribe to this list, but I forgot tha address to make this. > > Somebody could tell me that address? > > Thank You > > Daniel Baker - Daniel@Cuckoo.COM "Uhhhhhhh, thank you, drive through please" From owner-freebsd-hardware Wed Mar 27 18:03:39 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA21053 for hardware-outgoing; Wed, 27 Mar 1996 18:03:39 -0800 (PST) Received: from cocoa.ops.neosoft.com (root@cocoa.ops.neosoft.com [206.109.5.227]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA21027 Wed, 27 Mar 1996 18:03:34 -0800 (PST) Received: (from dbaker@localhost) by cocoa.ops.neosoft.com (8.7.5/8.6.12) id UAA14400; Wed, 27 Mar 1996 20:03:27 -0600 (CST) Date: Wed, 27 Mar 1996 20:03:27 -0600 (CST) From: Daniel Baker X-Sender: dbaker@cocoa.ops.neosoft.com To: freebsd-current@freebsd.org, freebsd-hardware@freebsd.org Subject: qcamcontrol dumps core with brightness Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Running -CURRENT from about a week ago, qcamcontrol works, but if I try and adjust the brightness, it dumps core saying segmentation fault, any ideas? Daniel Daniel Baker - Daniel@Cuckoo.COM "Uhhhhhhh, thank you, drive through please" From owner-freebsd-hardware Wed Mar 27 18:43:42 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA23160 for hardware-outgoing; Wed, 27 Mar 1996 18:43:42 -0800 (PST) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [204.214.4.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA23155 for ; Wed, 27 Mar 1996 18:43:40 -0800 (PST) Received: from max7-173.HiWAAY.net by fly.HiWAAY.net; (5.65v3.0/1.1.8.2/21Sep95-1003PM) id AA07251; Wed, 27 Mar 1996 20:43:20 -0600 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 27 Mar 1996 20:43:31 -0600 To: jas@flyingfox.com From: dkelly@hiwaay.net (David Kelly) Subject: Re: motherboard and Ethernet card recommendations Cc: hardware@freebsd.org Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 8:25 AM 3/27/96, Georg-W. Koltermann wrote: >Wasn't there some talking about buggy UMC chips on that board? Or >does the ...TP4N board use different chips than the ...TP4XE? > >And, BTW, does anyone know if their just-to-be released Motherboards >with the 430HX (aka Triton-2) use any buggy chips? I'm about to buy >one of those when they've arrived the local dealers. I checked >http://192.72.126.1/Products/spec.html and found nothing apparent. >Nice pictures, though! I've been thinking about a 430HX too. My thinking is NOT to buy a Triton-I because the it doesn't support parity memory while the Triton-II one-ups the parity checkers by adding ECC. I'll do without EDO memory any day for parity check or ECC. Have never seen parity-EDO memory for sale. About 5 years ago I was running a 12 machine SGI installation. (9) 4D/320GTX, (1) 4D/340S, and (2) 4D/380S. All had either 64M or 128M of ECC memory (in 1M SIMMs). One lemon had a corrected single-bit parity error about twice per day. Never crashed claiming the problem was parity. Uptimes were the same as the other machines, typically months. Only one machine never had a parity error (that I know of). Today I have a memory failure phobia. :-) -- David Kelly N4HHE, n4hhe@amsat.org, dkelly@hiwaay.net ============================================================= To invent, you need a good imagination and a pile of junk. - Thomas Edison From owner-freebsd-hardware Wed Mar 27 18:53:55 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA23742 for hardware-outgoing; Wed, 27 Mar 1996 18:53:55 -0800 (PST) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA23737 Wed, 27 Mar 1996 18:53:53 -0800 (PST) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0u287Q-000wtyC; Wed, 27 Mar 96 19:11 PST Received: from cc:Mail by ccgate.infoworld.com id AA827981569; Wed, 27 Mar 96 19:49:38 PST Date: Wed, 27 Mar 96 19:49:38 PST From: "Brett Glass" Message-Id: <9602278279.AA827981569@ccgate.infoworld.com> To: freebsd-hardware@freebsd.org, jkh@freebsd.org Subject: Re: Cannot boot after install Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk After tweaking the translation settings on the controller, I was able to boot but still did not have a stable system. I was experiencing coredumps while running certain apps (e.g. mail), indicating that something was still wrong. Here's another clue to what might be going on. I partitioned the drive as "all FreeBSD" without a standard partition table, hoping that this would bypass problems with trying to stick to the MS-DOS standard. Using the "Novice" installation mode, step by step, I sliced up the disk into areas for root, swap, /var, /usr, and /home. I then turned on debugging messages and watched the second virtual TTY during installation. During newfs, error messages appeared as each file system was created, saying that the number of sectors per cylinder (4096) diagreed with that in the disk label (4032). The Ultrastor is a translating controller, and I had entered the geometry 969/64/63 in fdisk. The product of the last two numbers is (of course) 4032 -- the number of sectors per cylinder after translation. Why does the software think there are more? Does this message relate to the problem? If the message indicates an error in newfs, it might account for the disk errors and application coredumps I'm getting after installation. Authors: What do you think? Is this a bug? If so, is there a way to work around it (perhaps by specifying parameters to newfs)? --Brett Glass From owner-freebsd-hardware Wed Mar 27 19:48:59 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA26400 for hardware-outgoing; Wed, 27 Mar 1996 19:48:59 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA26387 Wed, 27 Mar 1996 19:48:39 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id OAA14159; Thu, 28 Mar 1996 14:36:52 +1030 From: Michael Smith Message-Id: <199603280406.OAA14159@genesis.atrad.adelaide.edu.au> Subject: Re: Cannot boot after install To: Brett_Glass@ccgate.infoworld.com (Brett Glass) Date: Thu, 28 Mar 1996 14:36:52 +1030 (CST) Cc: freebsd-hardware@FreeBSD.org, jkh@FreeBSD.org In-Reply-To: <9602278279.AA827981569@ccgate.infoworld.com> from "Brett Glass" at Mar 27, 96 07:49:38 pm 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 stands accused of saying: > > After tweaking the translation settings on the controller, I was able to > boot but still did not have a stable system. I was experiencing coredumps > while running certain apps (e.g. mail), indicating that something was still > wrong. Sounds like hardware, I have to say. > and watched the second virtual TTY during installation. During newfs, error > messages appeared as each file system was created, saying that the number > of sectors per cylinder (4096) diagreed with that in the disk label (4032). This message is harmless. > --Brett Glass -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Wed Mar 27 20:59:15 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA29646 for hardware-outgoing; Wed, 27 Mar 1996 20:59:15 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA29641 Wed, 27 Mar 1996 20:59:12 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id UAA03319; Wed, 27 Mar 1996 20:58:50 -0800 (PST) To: "Brett Glass" cc: freebsd-hardware@freebsd.org, jkh@freebsd.org Subject: Re: Cannot boot after install In-reply-to: Your message of "Wed, 27 Mar 1996 19:49:38 PST." <9602278279.AA827981569@ccgate.infoworld.com> Date: Wed, 27 Mar 1996 20:58:50 -0800 Message-ID: <3317.827989130@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > After tweaking the translation settings on the controller, I was able to > boot but still did not have a stable system. I was experiencing coredumps > while running certain apps (e.g. mail), indicating that something was still > wrong. Is it only mail that coredumps, or more than one app? > for root, swap, /var, /usr, and /home. I then turned on debugging messages > and watched the second virtual TTY during installation. During newfs, error > messages appeared as each file system was created, saying that the number > of sectors per cylinder (4096) diagreed with that in the disk label (4032). This is just a warning, and not actually an error - everyone gets that one. We should probably just remove the message. > The Ultrastor is a translating controller, and I had entered the geometry > 969/64/63 in fdisk. The product of the last two numbers is (of course) > 4032 -- the number of sectors per cylinder after translation. Why does the > software think there are more? Does this message relate to the > problem? I don't think so. Jordan From owner-freebsd-hardware Wed Mar 27 21:57:56 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA02472 for hardware-outgoing; Wed, 27 Mar 1996 21:57:56 -0800 (PST) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA02464 Wed, 27 Mar 1996 21:57:52 -0800 (PST) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0u2Azf-000wtxC; Wed, 27 Mar 96 22:15 PST Received: from cc:Mail by ccgate.infoworld.com id AA827992622; Wed, 27 Mar 96 22:52:41 PST Date: Wed, 27 Mar 96 22:52:41 PST From: "Brett Glass" Message-Id: <9602278279.AA827992622@ccgate.infoworld.com> To: jkh@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Cannot boot after install Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Is it only mail that coredumps, or more than one app? Many apps. Repeated the problem with an Adaptec controller; same results. (Details coming to you via private e-mail.) --Brett From owner-freebsd-hardware Wed Mar 27 22:46:45 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA04158 for hardware-outgoing; Wed, 27 Mar 1996 22:46:45 -0800 (PST) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA04153 Wed, 27 Mar 1996 22:46:43 -0800 (PST) Message-Id: <199603280646.WAA04153@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: "Brett Glass" cc: jkh@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Cannot boot after install In-reply-to: Your message of "Wed, 27 Mar 1996 22:52:41 PST." <9602278279.AA827992622@ccgate.infoworld.com> Date: Wed, 27 Mar 1996 22:46:43 -0800 From: "Justin T. Gibbs" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Is it only mail that coredumps, or more than one app? > >Many apps. > >Repeated the problem with an Adaptec controller; same results. (Details >coming to you via private e-mail.) With an Adaptec controller, I can tell you the proper geometry. I don't know about the Ultrastore. The Adaptec should be 64 heads, 32 sectors/track, #MB cylinders or in extended translation mode: 255,63,#MB/7 >--Brett -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-hardware Thu Mar 28 07:10:52 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA04781 for hardware-outgoing; Thu, 28 Mar 1996 07:10:52 -0800 (PST) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA04500 Thu, 28 Mar 1996 07:08:08 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id JAA28547; Thu, 28 Mar 1996 09:03:46 -0600 Received: from tserv.lodgenet.com(204.124.120.10) by bacall via smap (V1.3) id sma001066; Thu Mar 28 09:01:20 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by tserv.lodgenet.com (8.6.12/8.6.12) with ESMTP id IAA22747; Thu, 28 Mar 1996 08:26:10 -0600 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.7.5/8.6.12) with SMTP id IAA27093; Thu, 28 Mar 1996 08:38:26 -0600 (CST) Message-Id: <199603281438.IAA27093@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost [127.0.0.1] didn't use HELO protocol X-Mailer: exmh version 1.6.2 7/18/95 To: Joe Greco cc: erich@basenet.com (Eric Hester), freebsd-hardware@FreeBSD.org, freebsd-isp@FreeBSD.org Subject: Re: comtrol rocketports In-reply-to: Your message of "Sat, 16 Mar 1996 09:45:46 CST." <199603161545.JAA24201@brasil.moneng.mei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 Mar 1996 08:38:25 -0600 From: "Eric L. Hernes" Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk howdy, The salesman from Comtrol called again yesterday. I reminded him that I couldn't even seriously consider their card without a FBSD driver, he said he'd check on it... He called back and indicated that he'd gotten an engineer to look at porting (their?) BSDi driver. hope to know more in a few days... eric. -- erich@lodgenet.com erich@rrnet.com From owner-freebsd-hardware Thu Mar 28 09:41:43 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA22220 for hardware-outgoing; Thu, 28 Mar 1996 09:41:43 -0800 (PST) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA22207 Thu, 28 Mar 1996 09:41:41 -0800 (PST) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0u2LzH-000wurC; Thu, 28 Mar 96 09:59 PST Received: from cc:Mail by ccgate.infoworld.com id AA828034814; Thu, 28 Mar 96 10:30:56 PST Date: Thu, 28 Mar 96 10:30:56 PST From: "Brett Glass" Message-Id: <9602288280.AA828034814@ccgate.infoworld.com> To: "Justin T. Gibbs" Cc: jkh@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Cannot boot after install Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The Adaptec should be 64 heads, 32 sectors/track, #MB cylinders > or in extended translation mode: 255,63,#MB/7 Well, when I try to enter the parameters the controller sets in extended translation mode -- which are 243/255/63 -- FreeBSD's fdisk utlility bluntly tells me that these parameters are "wrong." Even though, when the kernel boots with the -v option, this is exactly what the reported BIOS geometry is. --Brett From owner-freebsd-hardware Thu Mar 28 13:09:40 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA05749 for hardware-outgoing; Thu, 28 Mar 1996 13:09:40 -0800 (PST) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA05738 Thu, 28 Mar 1996 13:09:35 -0800 (PST) Message-Id: <199603282109.NAA05738@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: "Brett Glass" cc: jkh@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Cannot boot after install In-reply-to: Your message of "Thu, 28 Mar 1996 10:30:56 PST." <9602288280.AA828034814@ccgate.infoworld.com> Date: Thu, 28 Mar 1996 13:09:35 -0800 From: "Justin T. Gibbs" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> The Adaptec should be 64 heads, 32 sectors/track, #MB cylinders >> or in extended translation mode: 255,63,#MB/7 > >Well, when I try to enter the parameters the controller sets in extended >translation mode -- which are 243/255/63 -- FreeBSD's fdisk utlility >bluntly tells me that these parameters are "wrong." Even though, when the >kernel boots with the -v option, this is exactly what the reported BIOS >geometry is. > >--Brett > Can you boot DOS, create a small DOS partition on the disk and try again? Looks like sysinstall is confused and having a valid partition table on the disk may help convince it that you are right. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-hardware Thu Mar 28 14:27:25 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA12346 for hardware-outgoing; Thu, 28 Mar 1996 14:27:25 -0800 (PST) Received: from arthur.cs.purdue.edu (root@arthur.cs.purdue.edu [128.10.2.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA12341 for ; Thu, 28 Mar 1996 14:27:16 -0800 (PST) Received: from moriarty.cs.purdue.edu (root@moriarty.cs.purdue.edu [128.10.2.69]) by arthur.cs.purdue.edu (8.7.3/PURDUE_CS-1.4) with ESMTP id RAA22751 for ; Thu, 28 Mar 1996 17:27:09 -0500 (EST) Received: from localhost (jha@localhost [127.0.0.1]) by moriarty.cs.purdue.edu (8.7.3/PURDUE_CS-1.4) with SMTP id RAA22564 for ; Thu, 28 Mar 1996 17:27:05 -0500 (EST) Message-Id: <199603282227.RAA22564@moriarty.cs.purdue.edu> To: hardware@freebsd.org Subject: NE2000 comatible PCMCIA Date: Thu, 28 Mar 1996 17:27:01 -0500 From: jha@cs.purdue.edu ("John H. Aughey") Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am looking for a PCMCIA Ethernet card to use with FreeBSD and I've found one created by Infotel. It says IEEE 802.3 compliant NE2000 compatible. However, it says nothing about the chipset. Will FreeBSD be able to work with this card? -John From owner-freebsd-hardware Thu Mar 28 15:07:48 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA16213 for hardware-outgoing; Thu, 28 Mar 1996 15:07:48 -0800 (PST) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA16207 Thu, 28 Mar 1996 15:07:35 -0800 (PST) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0u2R4u-000wr6C; Thu, 28 Mar 96 15:26 PST Received: from cc:Mail by ccgate.infoworld.com id AA828054376; Thu, 28 Mar 96 15:43:33 PST Date: Thu, 28 Mar 96 15:43:33 PST From: "Brett Glass" Message-Id: <9602288280.AA828054376@ccgate.infoworld.com> To: "Justin T. Gibbs" Cc: jkh@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Cannot boot after install Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Will give this a try. If it doesn't work, I will have to switch to another machine. This one will be around for testing, though. From owner-freebsd-hardware Thu Mar 28 17:51:59 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA27838 for hardware-outgoing; Thu, 28 Mar 1996 17:51:59 -0800 (PST) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA27823 Thu, 28 Mar 1996 17:51:55 -0800 (PST) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0u2Tdu-000wtoC; Thu, 28 Mar 96 18:10 PST Received: from cc:Mail by ccgate.infoworld.com id AA828064224; Thu, 28 Mar 96 18:27:44 PST Date: Thu, 28 Mar 96 18:27:44 PST From: "Brett Glass" Message-Id: <9602288280.AA828064224@ccgate.infoworld.com> To: "Brett Glass" , gibbs@freefall.freebsd.org Cc: jkh@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Cannot boot after install Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Partitioning with DOS does get rid of the geometry rejection problem. (Though, for some reason, fdisk sets the geometry to 1/1/1 as I partition and I have to reset it. This is apparently a bug.) However, I still had problems. This time, instead of freezing, the system brought up a dialogue box with the message: Write failure on transfer! (wrote -1 bytes of 1536 bytes) On VTY2, The system showed: pid 32: gunzip: uid 0: exited on signal 11 pid 31: cpio: uid 0: exited on signal 11 (I don't remember my UNIX signals that well, but I seem to recall that signal 11 is SIGTERM.) The last file copied (it varies from run to run) was kernel.GENERIC. Trying to continue the install returned additional "wrote -1 bytes of X bytes" messages. RAM tests good. About the only other thing I could try replacing is the disk drive. Unfortunately, I don't have another to replace it with.... --Brett From owner-freebsd-hardware Thu Mar 28 19:07:15 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA03109 for hardware-outgoing; Thu, 28 Mar 1996 19:07:15 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA03075 Thu, 28 Mar 1996 19:07:00 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id NAA19935; Fri, 29 Mar 1996 13:55:49 +1030 From: Michael Smith Message-Id: <199603290325.NAA19935@genesis.atrad.adelaide.edu.au> Subject: Re: Cannot boot after install To: Brett_Glass@ccgate.infoworld.com (Brett Glass) Date: Fri, 29 Mar 1996 13:55:49 +1030 (CST) Cc: Brett_Glass@ccgate.infoworld.com, gibbs@freefall.freebsd.org, jkh@freebsd.org, freebsd-hardware@freebsd.org In-Reply-To: <9602288280.AA828064224@ccgate.infoworld.com> from "Brett Glass" at Mar 28, 96 06:27:44 pm 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 stands accused of saying: > > Write failure on transfer! (wrote -1 bytes of 1536 bytes) > > On VTY2, The system showed: > > pid 32: gunzip: uid 0: exited on signal 11 > pid 31: cpio: uid 0: exited on signal 11 > > (I don't remember my UNIX signals that well, but I seem to recall that > signal 11 is SIGTERM.) SIGSEGV. In context, you have memory, cache or chipset problems. > RAM tests good. About the only other thing I could try replacing is the > disk drive. Unfortunately, I don't have another to replace it with.... RAM tests aren't worth spit. My first suggestion would be a RAM swap, but make sure you're using appropriately specified RAM to begin with. > --Brett -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Thu Mar 28 22:35:40 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA19094 for hardware-outgoing; Thu, 28 Mar 1996 22:35:40 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA19086 Thu, 28 Mar 1996 22:35:35 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id RAA07131; Fri, 29 Mar 1996 17:34:05 +1100 Date: Fri, 29 Mar 1996 17:34:05 +1100 From: Bruce Evans Message-Id: <199603290634.RAA07131@godzilla.zeta.org.au> To: Brett_Glass@ccgate.infoworld.com, gibbs@freefall.freebsd.org Subject: Re: Cannot boot after install Cc: freebsd-hardware@FreeBSD.org, jkh@FreeBSD.org Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Partitioning with DOS does get rid of the geometry rejection problem. >(Though, for some reason, fdisk sets the geometry to 1/1/1 as I partition >and I have to reset it. This is apparently a bug.) However, I still had I've seen this before (sysinstall or libdisk creates an invalid partition table with an ending C/H/S values of 1023/1/1 or something like that) but don't have any free disks to duplicate it on now. I tried sysinstall on a sliced floppy. This used to sort of work, but now sysinstall dumps core writing the partition table. Also, sysinstall no longer sort of works when run by non-root - keyboard input isn't recognised. Also, the libdisk tags got lost when libdisk was moved to /usr/src/lib. Bruce From owner-freebsd-hardware Fri Mar 29 01:43:35 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA28339 for hardware-outgoing; Fri, 29 Mar 1996 01:43:35 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id BAA28332 Fri, 29 Mar 1996 01:43:31 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id BAA28387; Fri, 29 Mar 1996 01:42:58 -0800 (PST) To: "Brett Glass" cc: gibbs@freefall.freebsd.org, jkh@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Cannot boot after install In-reply-to: Your message of "Thu, 28 Mar 1996 18:27:44 PST." <9602288280.AA828064224@ccgate.infoworld.com> Date: Fri, 29 Mar 1996 01:42:58 -0800 Message-ID: <28385.828092578@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hmmmmm. Now this smells like a cache problem! :-( Jordan > Partitioning with DOS does get rid of the geometry rejection problem. > (Though, for some reason, fdisk sets the geometry to 1/1/1 as I partition > and I have to reset it. This is apparently a bug.) However, I still had > problems. This time, instead of freezing, the system brought up a dialogue > box with the message: > > Write failure on transfer! (wrote -1 bytes of 1536 bytes) > > On VTY2, The system showed: > > pid 32: gunzip: uid 0: exited on signal 11 > pid 31: cpio: uid 0: exited on signal 11 > > (I don't remember my UNIX signals that well, but I seem to recall that > signal 11 is SIGTERM.) > > The last file copied (it varies from run to run) was kernel.GENERIC. > > Trying to continue the install returned additional "wrote -1 bytes of X > bytes" messages. > > RAM tests good. About the only other thing I could try replacing is the > disk drive. Unfortunately, I don't have another to replace it with.... > > --Brett > From owner-freebsd-hardware Fri Mar 29 07:11:36 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA23947 for hardware-outgoing; Fri, 29 Mar 1996 07:11:36 -0800 (PST) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA23926 Fri, 29 Mar 1996 07:11:31 -0800 (PST) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0u2g8S-000wyRC; Fri, 29 Mar 96 07:30 PST Received: from cc:Mail by ccgate.infoworld.com id AA828112246; Fri, 29 Mar 96 03:44:20 PST Date: Fri, 29 Mar 96 03:44:20 PST From: "Brett Glass" Message-Id: <9602298281.AA828112246@ccgate.infoworld.com> To: "Justin T. Gibbs" Cc: jkh@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Cannot boot after install Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk After giving up on getting the EISA/SCSI system to work with FreeBSD, I switched to a Zeos Pantera 486 DX4/100 with a Seagate ST5660A IDE hard disk. This is a "green" hard disk that shuts down after periods of inactivity, then spins up when it's needed again. It can be configured not to, but FreeBSD doesn't change the hard disk's default setting. Unfortunately, the spin-downs play hob with FreeBSD's IDE disk driver. As soon as the system was installed and seemed healthy, I brought up jove to edit a configuration file for a customized kernel. While I was editing, the drive shut down. When I tried to save, the console was splattered with messages indicating timeouts and "unwedge failures." The disk was corrupted, and the entire install was lost. Does anyone know of a way I can get THIS system stabilized? --Brett From owner-freebsd-hardware Fri Mar 29 07:28:05 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA25877 for hardware-outgoing; Fri, 29 Mar 1996 07:28:05 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA25853 Fri, 29 Mar 1996 07:27:56 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id HAA29330; Fri, 29 Mar 1996 07:27:07 -0800 (PST) To: Bruce Evans cc: Brett_Glass@ccgate.infoworld.com, gibbs@freefall.freebsd.org, freebsd-hardware@FreeBSD.org, jkh@FreeBSD.org Subject: Re: Cannot boot after install In-reply-to: Your message of "Fri, 29 Mar 1996 17:34:05 +1100." <199603290634.RAA07131@godzilla.zeta.org.au> Date: Fri, 29 Mar 1996 07:27:07 -0800 Message-ID: <29328.828113227@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I've seen this before (sysinstall or libdisk creates an invalid partition > table with an ending C/H/S values of 1023/1/1 or something like that) but > don't have any free disks to duplicate it on now. I tried sysinstall > on a sliced floppy. This used to sort of work, but now sysinstall dumps > core writing the partition table. Also, sysinstall no longer sort of works > when run by non-root - keyboard input isn't recognised. Also, the > libdisk tags got lost when libdisk was moved to /usr/src/lib. I'll look into all of this tomorrow, once I get back from a short trip. Jordan From owner-freebsd-hardware Fri Mar 29 08:48:43 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA01051 for hardware-outgoing; Fri, 29 Mar 1996 08:48:43 -0800 (PST) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA01042 Fri, 29 Mar 1996 08:48:41 -0800 (PST) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0u2heY-000wveC; Fri, 29 Mar 96 09:07 PST Received: from cc:Mail by ccgate.infoworld.com id AA828118056; Fri, 29 Mar 96 09:39:13 PST Date: Fri, 29 Mar 96 09:39:13 PST From: "Brett Glass" Message-Id: <9602298281.AA828118056@ccgate.infoworld.com> To: "Jordan K. Hubbard" Cc: gibbs@freefall.freebsd.org, jkh@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Cannot boot after install Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hmmmmm. Now this smells like a cache problem! :-( > > Jordan The OS's disk cache or the computer's RAM cache? The latter has been exercised heavily and seems to check out OK. Disk I/O problems would certainly lead to coredumps, so this may be related to the instability I was seeing. --Brett From owner-freebsd-hardware Fri Mar 29 10:40:52 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA09786 for hardware-outgoing; Fri, 29 Mar 1996 10:40:52 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA09772 Fri, 29 Mar 1996 10:40:47 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id KAA00286; Fri, 29 Mar 1996 10:40:11 -0800 (PST) To: "Brett Glass" cc: "Justin T. Gibbs" , jkh@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Cannot boot after install In-reply-to: Your message of "Fri, 29 Mar 1996 03:44:20 PST." <9602298281.AA828112246@ccgate.infoworld.com> Date: Fri, 29 Mar 1996 10:40:10 -0800 Message-ID: <284.828124810@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Does anyone know of a way I can get THIS system stabilized? Turn the green mode crap off! It's utterly unacceptable for pretty much any UNIX system you can name (including Linux) to have one of its drives suddently decide to take a vacation. This thing must have some BIOS option for disabling it. Jordan From owner-freebsd-hardware Fri Mar 29 11:29:04 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA14087 for hardware-outgoing; Fri, 29 Mar 1996 11:29:04 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA14082 for ; Fri, 29 Mar 1996 11:29:02 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id LAA02739; Fri, 29 Mar 1996 11:29:15 -0800 (PST) Message-Id: <199603291929.LAA02739@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol To: "Jordan K. Hubbard" cc: "Brett Glass" , freebsd-hardware@freebsd.org Subject: Re: Cannot boot after install In-reply-to: Your message of "Fri, 29 Mar 1996 10:40:10 PST." <284.828124810@time.cdrom.com> From: David Greenman Reply-To: davidg@Root.COM Date: Fri, 29 Mar 1996 11:29:15 -0800 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Does anyone know of a way I can get THIS system stabilized? > >Turn the green mode crap off! It's utterly unacceptable for pretty >much any UNIX system you can name (including Linux) to have one of its >drives suddently decide to take a vacation. This thing must have some >BIOS option for disabling it. Or perhaps a hardware jumper? -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hardware Fri Mar 29 13:02:07 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA19657 for hardware-outgoing; Fri, 29 Mar 1996 13:02:07 -0800 (PST) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA19644 Fri, 29 Mar 1996 13:02:03 -0800 (PST) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0u2lbs-000wvaC; Fri, 29 Mar 96 13:21 PST Received: from cc:Mail by ccgate.infoworld.com id AA828133263; Fri, 29 Mar 96 13:04:16 PST Date: Fri, 29 Mar 96 13:04:16 PST From: "Brett Glass" Message-Id: <9602298281.AA828133263@ccgate.infoworld.com> To: "Jordan K. Hubbard" Cc: gibbs@freefall.freebsd.org, jkh@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Cannot boot after install Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Turn the green mode crap off! It's utterly unacceptable for pretty > much any UNIX system you can name (including Linux) to have one of its > drives suddently decide to take a vacation. This thing must have some > BIOS option for disabling it. Unfortunately, the BIOS has no such option. I called Zeos, and they say that the OS's IDE driver should turn power management off if it does not want it on. This certainly seems like a good idea for any UNIX system. Incidentally, OS/2, for all its faults, DOES keep the drive running continuously. It must know how to keep it from spinning down. --Brett From owner-freebsd-hardware Fri Mar 29 13:02:08 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA19658 for hardware-outgoing; Fri, 29 Mar 1996 13:02:08 -0800 (PST) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA19647 for ; Fri, 29 Mar 1996 13:02:05 -0800 (PST) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0u2lbu-000wveC; Fri, 29 Mar 96 13:21 PST Received: from cc:Mail by ccgate.infoworld.com id AA828133271; Fri, 29 Mar 96 13:12:52 PST Date: Fri, 29 Mar 96 13:12:52 PST From: "Brett Glass" Message-Id: <9602298281.AA828133271@ccgate.infoworld.com> To: davidg@Root.COM, jkh@time.cdrom.com Cc: freebsd-hardware@freebsd.org Subject: Re: Cannot boot after install Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Or perhaps a hardware jumper? The drive spec in ftp://ftp.sdd.com/files/seagate/at/st5660a.txt Shows no jumper for this purpose. I wish it did. There *is* a jumper that forces 1024-cylinder translation. From owner-freebsd-hardware Fri Mar 29 17:30:31 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA05900 for hardware-outgoing; Fri, 29 Mar 1996 17:30:31 -0800 (PST) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA05891 Fri, 29 Mar 1996 17:30:28 -0800 (PST) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0u2pnt-000wvzC; Fri, 29 Mar 96 17:50 PST Received: from cc:Mail by ccgate.infoworld.com id AA828149379; Fri, 29 Mar 96 18:21:04 PST Date: Fri, 29 Mar 96 18:21:04 PST From: "Brett Glass" Message-Id: <9602298281.AA828149379@ccgate.infoworld.com> To: "Jordan K. Hubbard" Cc: gibbs@freefall.freebsd.org, jkh@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Cannot boot after install Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Here is the latest on the Zeos with the Seagate ST5660A drive. First, I found out why it wouldn't go above 1024/16/63. There's a jumper on the drive that limits it to that. When I removed the jumper, I was able to get 1057/16/63 in the BIOS. (Why Zeos did not remove the jumper, I do not know. When I called their tech support line, the tech was rude and insisted that the drive didn't have any more space on it.) I then installed Caldera Network Desktop, which is built on top of an enhanced version of Red Hat Linux. It *did* work and did not crash. One of the boot messages from the kernel seemed significant. It said something like: ide0: Buggy RZ1000 chip: Disabling read-ahead This could be related to the problem. If this *is* the problem, code to fix it ought to be available in the Red Hat Linux distribution, or so I would imagine. [Note: Caldera decided to treat the drive as 528/32/63. Not sure why it needs to do that under UNIX. But the translation is one of those listed by Seagate in the docs, and it works with only a slight loss of space.] In any event, if my intution is correct here, I can't get FreeBSD running until the read-aheads are disabled. (No, there's no jumper for this on the drive, just as there is no jumper to turn off "green" mode. It's got to be set via IDE.) --Brett P.S. -- I do like FreeBSD's configuration and installation routines much better than the ones that come with Caldera, by the way. That visual configuration editor saves a lot of pain. From owner-freebsd-hardware Fri Mar 29 19:11:47 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA08467 for hardware-outgoing; Fri, 29 Mar 1996 19:11:47 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA08461 Fri, 29 Mar 1996 19:11:35 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id NAA25554; Sat, 30 Mar 1996 13:59:27 +1030 From: Michael Smith Message-Id: <199603300329.NAA25554@genesis.atrad.adelaide.edu.au> Subject: Re: Cannot boot after install To: Brett_Glass@ccgate.infoworld.com (Brett Glass) Date: Sat, 30 Mar 1996 13:59:26 +1030 (CST) Cc: jkh@time.cdrom.com, gibbs@freefall.freebsd.org, jkh@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG In-Reply-To: <9602298281.AA828149379@ccgate.infoworld.com> from "Brett Glass" at Mar 29, 96 06:21:04 pm 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 stands accused of saying: > enhanced version of Red Hat Linux. It *did* work and did not crash. One of > the boot messages from the kernel seemed significant. It said something > like: > > ide0: Buggy RZ1000 chip: Disabling read-ahead > > This could be related to the problem. > > If this *is* the problem, code to fix it ought to be available in the Red > Hat Linux distribution, or so I would imagine. The problem can bite before the kernel has been loaded. Your BIOS should have an option to disable "IDE readhead" or similar, and this is the correct place to turn it off. > In any event, if my intution is correct here, I can't get FreeBSD running > until the read-aheads are disabled. (No, there's no jumper for this on > the drive, just as there is no jumper to turn off "green" mode. It's got > to be set via IDE.) If I recall correctly, the ATA-2 spec says that drives should not default to green mode; you're probably going to have to check with the spec and add some special code to the 'wd' driver to recognise your drive and disable 'green mode'. > --Brett > > P.S. -- I do like FreeBSD's configuration and installation routines much > better than the ones that come with Caldera, by the way. That visual > configuration editor saves a lot of pain. (*warm fuzzies*) -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Sat Mar 30 00:17:49 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA21782 for hardware-outgoing; Sat, 30 Mar 1996 00:17:49 -0800 (PST) Received: from rocoto.aug.com (aug.com [205.216.79.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA21774 for ; Sat, 30 Mar 1996 00:17:47 -0800 (PST) Received: (from heric@localhost) by rocoto.aug.com (8.6.12/8.6.6) id DAA14363 for freebsd-hardware@freebsd.org; Sat, 30 Mar 1996 03:17:16 -0500 From: Eric Hinson Message-Id: <199603300817.DAA14363@rocoto.aug.com> Subject: ASUS ncr scsi controller question To: freebsd-hardware@freebsd.org Date: Sat, 30 Mar 1996 03:17:16 -0500 (EST) X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I set up a drive with FreeBSD on an Adaptec 1542cf (on another system) and would like to put the drive in a system with the NCR PCI-SC200. I have done this before successfully with no difficulty. However, when I tried it with this new system, it works fine with an Adaptec 1542cf (even with 32 megs of ram), but gives me a 'missing operating system' message when I try to boot the same drive with the NCR based controller. I encountered this same error with the adaptec before I turned off the > 1gig translation option in the Adaptec 1542cf BIOS. After that, it came up without incident. I have moved drives from the Adaptec 1542cf based systems to the NCR PCI based systems in the past without problems. Any help you can provide would be greatly appreciated. Thanks. Eric From owner-freebsd-hardware Sat Mar 30 05:20:19 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA06183 for hardware-outgoing; Sat, 30 Mar 1996 05:20:19 -0800 (PST) Received: from hda.com (ip19-max1-fitch.zipnet.net [199.232.245.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA06178 for ; Sat, 30 Mar 1996 05:20:15 -0800 (PST) Received: (from dufault@localhost) by hda.com (8.6.11/8.6.9) id IAA09293; Sat, 30 Mar 1996 08:12:11 -0500 From: Peter Dufault Message-Id: <199603301312.IAA09293@hda.com> Subject: Re: Cannot boot after install To: davidg@Root.COM Date: Sat, 30 Mar 1996 08:12:10 -0500 (EST) Cc: hardware@freebsd.org In-Reply-To: <199603291929.LAA02739@Root.COM> from "David Greenman" at Mar 29, 96 11:29:15 am Reply-to: hdalog@zipnet.net X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> Does anyone know of a way I can get THIS system stabilized? > > > >Turn the green mode crap off! It's utterly unacceptable for pretty > >much any UNIX system you can name (including Linux) to have one of its > >drives suddently decide to take a vacation. This thing must have some > >BIOS option for disabling it. > > Or perhaps a hardware jumper? If all else fails a program that reads a block every 30s or so. -- Temporarily via "hdalog@zipnet.net"... Peter Dufault Real-Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-hardware Sat Mar 30 14:03:09 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA14539 for hardware-outgoing; Sat, 30 Mar 1996 14:03:09 -0800 (PST) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA14524 for ; Sat, 30 Mar 1996 14:03:06 -0800 (PST) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0u393f-000wynC; Sat, 30 Mar 96 14:23 PST Received: from cc:Mail by ccgate.infoworld.com id AA828223302; Sat, 30 Mar 96 00:51:48 PST Date: Sat, 30 Mar 96 00:51:48 PST From: "Brett Glass" Message-Id: <9602308282.AA828223302@ccgate.infoworld.com> To: "Jordan K. Hubbard" , hardware@freebsd.org Subject: Re: Cannot boot after install Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk By the way, while I'd *hope* that the author of the IDE driver would know how to turn off disk spindowns, there's an obvious shortcut. Simply make sure that the system does a seek at regular intervals. To prevent this from interfering with normal operation, the driver could do this only if there had been no disk activity for awhile. --Brett P.S. -- After the most recent install attempt, I got messages of the form: /kernel: arplookup failed for
; system not on local network. Why is the system trying to do an ARP on a system on the other side of the router? The address isn't that of our domain name server (though the domain name server is also on the other side of the router). From owner-freebsd-hardware Sat Mar 30 14:17:53 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA16206 for hardware-outgoing; Sat, 30 Mar 1996 14:17:53 -0800 (PST) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA16193 Sat, 30 Mar 1996 14:17:48 -0800 (PST) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0u39Hq-000wvxC; Sat, 30 Mar 96 14:38 PST Received: from cc:Mail by ccgate.infoworld.com id AA828224213; Sat, 30 Mar 96 12:31:07 PST Date: Sat, 30 Mar 96 12:31:07 PST From: "Brett Glass" Message-Id: <9602308282.AA828224213@ccgate.infoworld.com> To: Michael Smith Cc: jkh@time.cdrom.com, gibbs@freefall.freebsd.org, jkh@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Cannot boot after install Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > If I recall correctly, the ATA-2 spec says that drives should not default > to green mode; you're probably going to have to check with the spec and > add some special code to the 'wd' driver to recognise your drive and > disable 'green mode'. I have the kernel code, but am unfamiliar with ATA-2. Anyone here know where to get the spec? Also, it might be possible to add a driver flag for disabling read-ahead. --Brett P.S. -- A week from Monday, you'll see some comments on the FreeBSD kernel configuration program in InfoWorld. Check out http://www.infoworld.com/pageone/opinions/glass.htm From owner-freebsd-hardware Sat Mar 30 21:42:46 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA26978 for hardware-outgoing; Sat, 30 Mar 1996 21:42:46 -0800 (PST) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA26971 for ; Sat, 30 Mar 1996 21:42:44 -0800 (PST) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0u3GEo-000wqAC; Sat, 30 Mar 96 22:03 PST Received: from cc:Mail by ccgate.infoworld.com id AA828250915; Sat, 30 Mar 96 22:38:27 PST Date: Sat, 30 Mar 96 22:38:27 PST From: "Brett Glass" Message-Id: <9602308282.AA828250915@ccgate.infoworld.com> To: hdalog@zipnet.net, davidg@Root.COM Cc: hardware@FreeBSD.org Subject: Re: Cannot boot after install Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > If all else fails a program that reads a block every 30s or so. This is what I'm doing: I put a line consisting of all stars in /etc/crontab (so it executes every minute) and had it do a sync. FreeBSD's sync always hits the disk, so this keeps it spinning. The heads still retract, though. It'd be good to turn power management off, and turn off prefetches at the same time. If Linux can do it, surely FreeBSD can. --Brett P.S. -- Am still trying to diagnose that arplookup failure. Why might the system be attempting to do an ARP on a system that isn't even on the local net? And that isn't named anywhere in the network configuration files? From owner-freebsd-hardware Sat Mar 30 21:42:49 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA26995 for hardware-outgoing; Sat, 30 Mar 1996 21:42:49 -0800 (PST) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA26990 for ; Sat, 30 Mar 1996 21:42:48 -0800 (PST) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0u3GEn-000wq4C; Sat, 30 Mar 96 22:03 PST Received: from cc:Mail by ccgate.infoworld.com id AA828250911; Sat, 30 Mar 96 22:33:54 PST Date: Sat, 30 Mar 96 22:33:54 PST From: "Brett Glass" Message-Id: <9602308282.AA828250911@ccgate.infoworld.com> To: Eric Hinson , freebsd-hardware@freebsd.org Subject: ASUS ncr scsi controller question Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Different controllers do sector translation in different ways, and sometimes reserve sectors for themselves. They're not always compatible. You might not be able to read your disk after you've changed controllers.