From owner-freebsd-hardware Thu Jan 1 02:26:10 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA04633 for hardware-outgoing; Thu, 1 Jan 1998 02:26:10 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from send1b.yahoomail.com (send1b.yahoomail.com [205.180.60.23]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA04628 for ; Thu, 1 Jan 1998 02:26:09 -0800 (PST) (envelope-from rgireyev@yahoo.com) Message-ID: <19980101102553.12506.rocketmail@send1b.yahoomail.com> Received: from [206.175.228.17] by send1b; Thu, 01 Jan 1998 02:25:53 PST Date: Thu, 1 Jan 1998 02:25:53 -0800 (PST) From: Rudy Gireyev Subject: Re: zip drive problems To: freebsd-hardware@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ---Mike Smith wrote: > > > My bad ... I wasn't saying that they are all the same, I was refering > > specifically to the parallel unit. But the emulation type thing was just > > what I heard from a friend, so I don't know if it's true or not. I > > originally told him something like what you just told me and he gave me > > the emulation story. > > Tell him to take some of them apart and look at the boards. Yeah, breaking stuff is cool !!! :-) > > > BTW, I don't suppose that anyone has any detailed white papers on the > > subject? > > What subject? Well my knoweledge is somewhat limited on this but I thought I'd share what I know. I apologize in advance if this is common knoweledge and I'm wasting bandwidth. >From what I know the way SCSI world works is you usually have a SCSI interface, which is also a SCSI bus (kinda like PCI), that controls multiple SCSI devices into this bus one can plug in HDs, CD-ROMS, scanners etc etc. Popular examples of SCSI buses are Adaptec AHA family and Symbios 8XX family What makes SCSI devices different from IDE is that they ship with an adapter/controller built into the device itself and that is what makes the SCSI unit intelligent (The hard disk itself may actually be the same as IDE). So SCSI Jaz drive only has a SCSI adapter. The SCSI Parallel has the adapter, the entire SCSI interface (or bus) to control a single unit. And on top of that a custom converter that allows a parallel port to talk to a SCSI interface (Wow that is a lot of hardware) So I guess the new plus drive with parallel and SCSI interface is extremely similar to the old parallel one with simply an external connector added directly into the adapter, bypassing SCSI interface and parallel port. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ Remember, the race is long, \\ msmith@freebsd.org > \\ and in the end it's only with yourself. \\ > > > _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com From owner-freebsd-hardware Thu Jan 1 04:50:22 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA09433 for hardware-outgoing; Thu, 1 Jan 1998 04:50:22 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from word.smith.net.au (ppp10.portal.net.au [202.12.71.110]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA09423 for ; Thu, 1 Jan 1998 04:50:11 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id XAA01771; Thu, 1 Jan 1998 23:14:16 +1030 (CST) Message-Id: <199801011244.XAA01771@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Rudy Gireyev cc: freebsd-hardware@FreeBSD.ORG Subject: Re: zip drive problems In-reply-to: Your message of "Thu, 01 Jan 1998 02:25:53 -0800." <19980101102553.12506.rocketmail@send1b.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jan 1998 23:14:15 +1030 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Tell him to take some of them apart and look at the boards. > > Yeah, breaking stuff is cool !!! :-) Breaking is for amateurs. I was referring to exploratory surgery. 8) > > > BTW, I don't suppose that anyone has any detailed white papers on > the > > > subject? > > > > What subject? > > Well my knoweledge is somewhat limited on this but I thought I'd share > what I know. I apologize in advance if this is common knoweledge and > I'm wasting bandwidth. I meant more "what subject for the white paper"? > From what I know the way SCSI world works is you usually have a SCSI > interface, which is also a SCSI bus (kinda like PCI), that controls > multiple SCSI devices into this bus one can plug in HDs, CD-ROMS, > scanners etc etc. Yecch. Stop here. You may be thinking straight, but your terminology is pretty broken. The bottom line here is that SCSI is a means for connecting devices together. You generally need a device to interface between a SCSI bus and the bus inside your system. > Popular examples of SCSI buses are Adaptec AHA > family and Symbios 8XX family These are interfaces; they provide translation services between the host bus (ISA for the 1542, PCI for the 8xx family) and a SCSI bus. > What makes SCSI devices different from IDE is that they ship with an > adapter/controller built into the device itself and that is what makes > the SCSI unit intelligent (The hard disk itself may actually be the > same as IDE). No. Both IDE and SCSI peripherals contain "intelligence" and interface logic; in this case the interface is between the IDE/SCSI bus and the local bus onboard the peripheral. Features of the SCSI interface make it possible for devices using that interface to do extra "clever" things that are only just becoming possible with ATA (nee IDE) devices. > So SCSI Jaz drive only has a SCSI adapter. > The SCSI Parallel has the adapter, the entire SCSI interface (or bus) > to control a single unit. And on top of that a custom converter that > allows a parallel port to talk to a SCSI interface (Wow that is a lot > of hardware) There is no parallel Jaz; you may mean the Zip. The only significant difference between the SCSI and Parallel Zip devices is the parallel-SCSI adapter (variously referred to as the ppa3, vp0, etc.) If you want to drive a Jaz off a parallel port, the Jaz Traveller should work with the vpo driver. As soon as I can lay my hands on one, I'll confirm that. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ Remember, the race is long, \\ msmith@freebsd.org \\ and in the end it's only with yourself. \\ From owner-freebsd-hardware Thu Jan 1 21:57:14 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA10393 for hardware-outgoing; Thu, 1 Jan 1998 21:57:14 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from m-net.arbornet.org (root@m-net.arbornet.org [209.142.209.161]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA10376 for ; Thu, 1 Jan 1998 21:57:06 -0800 (PST) (envelope-from kb8rjy@m-net.arbornet.org) Received: from localhost (kb8rjy@localhost) by m-net.arbornet.org (8.8.5/8.8.6) with SMTP id AAA00179 for ; Fri, 2 Jan 1998 00:50:06 -0500 (EST) Date: Fri, 2 Jan 1998 00:50:06 -0500 (EST) From: "Shaun Q." To: freebsd-hardware@freebsd.org Subject: re: zip drive problems (fixed.) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey - It's working! I received an email from Nicolas Souchu describing how someone had done it with the PPA driver instead of the ppbus. I installed it and initially had no success. However, I played with the flags a little and found out via trial and error that it can not be in EPP mode. I don't know if this is caused by my chipset, however, it's working now. I guess that the temporary solution until a fix for ppbus comes out would be to use ppa3 and if that doesn't work right away, to use that in any mode but EPP. Thanks for everyone's help. If anyone would like a copy of my MACHINE file, just write. TTYL! Shaun Qualheim From owner-freebsd-hardware Thu Jan 1 23:10:51 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA14588 for hardware-outgoing; Thu, 1 Jan 1998 23:10:51 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from al.imforei.apana.org.au (pjchilds@al.imforei.apana.org.au [202.12.89.41]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA14558 for ; Thu, 1 Jan 1998 23:10:28 -0800 (PST) (envelope-from pjchilds@al.imforei.apana.org.au) Received: (from pjchilds@localhost) by al.imforei.apana.org.au (beBop) id RAA10258; Fri, 2 Jan 1998 17:39:47 +1030 (CST) Date: Fri, 2 Jan 1998 17:39:47 +1030 (CST) From: Peter Childs Message-Id: <199801020709.RAA10258@al.imforei.apana.org.au> To: bryanb@walls-media.com (Bryan Bunch), freebsd-hardware@freebsd.org Subject: Re: Compaq Deskpro Intergrated Net Card In-Reply-To: <006501bd0bd3$0ba0e260$3471060c@ntwksbry.walls-media.com> User-Agent: tin/pre-1.4-971224 (UNIX) (FreeBSD/2.2-STABLE (i386)) Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <006501bd0bd3$0ba0e260$3471060c@ntwksbry.walls-media.com> you wrote: > Has anyone been able to get the integrated Network card that comes > installed in the Deskpro models to work under FreeBSD?? If its a 4000 or 6000 its probably got a netflex/3 in it which are based on a unsupported chipset. Search the archives for more info on this, but I've done it and its all a big _no_ peter -- Peter Childs --- http://www.imforei.apana.org.au/~pjchilds Finger pjchilds@al.imforei.apana.org.au for public PGP key From owner-freebsd-hardware Fri Jan 2 01:51:07 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA21438 for hardware-outgoing; Fri, 2 Jan 1998 01:51:07 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from shadows.aeon.net (shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA21433 for ; Fri, 2 Jan 1998 01:51:00 -0800 (PST) (envelope-from bsdhack@shadows.aeon.net) Received: (from bsdhack@localhost) by shadows.aeon.net (8.8.8/8.8.3) id LAA11223 for hardware@freebsd.org; Fri, 2 Jan 1998 11:54:59 +0200 (EET) From: mika ruohotie Message-Id: <199801020954.LAA11223@shadows.aeon.net> Subject: Re: I broke my mouse. In-Reply-To: from Atipa at "Dec 20, 97 10:16:54 pm" To: hardware@freebsd.org Date: Fri, 2 Jan 1998 11:54:59 +0200 (EET) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk i think this is more hardware thing... > Is the mouse plugged in when the system boots? The BIOS needs to hook > IRQ 12 at boot; if you try to plug in the mouse after boot, it won't be > properly recognized. Looks like the driver can't reset the device because it > can not physically locate it. > > You may have fried your mouse port on your motherboard. What type of > mouse and motherboard are you using? how about ps/2 keyboard? same danger with it? since, i have key tronic with ps/2, but i use it with an adapter, and i have hot plugged/unplugged it. it's a rare (and good) model of a keyboard, and i'd HATE to fry it, so, is there the same danger or not? logically, i would assume the danger exists. mickey