From owner-freebsd-hardware Sun Jan 7 01:10:14 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA28499 for hardware-outgoing; Sun, 7 Jan 1996 01:10:14 -0800 (PST) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA28487 for ; Sun, 7 Jan 1996 01:10:08 -0800 (PST) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id KAA06734; Sun, 7 Jan 1996 10:08:03 +0100 Message-Id: <199601070908.KAA06734@ra.dkuug.dk> Subject: Re: PS/2 AUX mouse problems with 2.1 To: brett@selgus.com (Brett Bourbin) Date: Sun, 7 Jan 1996 10:08:03 +0100 (MET) Cc: freebsd-hardware@FreeBSD.org In-Reply-To: <30EF5A63.20E@selgus.com> from "Brett Bourbin" at Jan 6, 96 09:30:11 pm From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hardware@FreeBSD.org Precedence: bulk In reply to Brett Bourbin who wrote: > > Are there any other issues with the 2.1 psm PS/2 AUX mouse driver, than > those listed in the FAQ? > > I have added a psm0 line (exactly the way it was in the LINT config) > along with the PSM_NO_RESET option and made the device, but the kernel > still does not think the mouse is there. > > It is, since I am writing this mail from the same box under Win95. > > I have looked at psm.c and inserted some debugging printf's and the > probe read (the inb() call) is returning 0x55. The check it seems to > be doing is if bit 2 is set, the mouse is not there. Is this correct? > It also assumes that it is at port 0x60, and IRQ 12. I know the > interrupt is correct, and I assume the port it right. Hmm I use it here, and it works fine for me, my config is something like: device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr that works on a ASUS p55tp4xeg motherboard with an IBM mouse.. There is work underways in this area as the way its done now is not optimal -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-hardware Sun Jan 7 11:23:28 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA04407 for hardware-outgoing; Sun, 7 Jan 1996 11:23:28 -0800 (PST) Received: from dreamlabs.dreaming.org (dreamlabs.dreaming.org [198.96.119.129]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA04383 for ; Sun, 7 Jan 1996 11:23:22 -0800 (PST) Received: (from mitayai@localhost) by dreamlabs.dreaming.org (8.6.12/8.6.12) id OAA13713; Sun, 7 Jan 1996 14:22:34 -0500 Date: Sun, 7 Jan 1996 14:22:32 -0500 (EST) From: Will Mitayai Keeso Rowe To: "Garrett A. Wollman" cc: James FitzGibbon , hardware@FreeBSD.org Subject: Re: Support for a Cabletron E20xx adapter? In-Reply-To: <9601011902.AA12485@halloran-eldar.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@FreeBSD.org Precedence: bulk On Mon, 1 Jan 1996, Garrett A. Wollman wrote: > Date: Mon, 1 Jan 1996 14:02:57 -0500 > From: Garrett A. Wollman > To: James FitzGibbon > Cc: hardware@FreeBSD.org > Subject: Support for a Cabletron E20xx adapter? > > [BTW: PLEASE don't post to multiple mailing-lists. It irritates those > people who read more than one.] > > < said: > > > Has anyone got support for a Cabletron E20xx adapter working under 2.1? > > Last I touched these things, they were based on the National 83C90 > chip, but used a proprietary bus interface that Cabletron would not > explain to anyone. That was three years ago; things may have gotten > better now. > > -GAWollman > > -- I kinda got it working as a NE2000 under Linux with a few twists... might want to find Linux Docs on it to look at what they say. Oh, and James: if that is my old Cabletron card i accidentally left at IO, i burned it out long ago and you'll never get it to work. :) -Mit ------------------------------------------------------------------------ Will Mitayai Keeso Rowe at DreamLabs Community Information Network Toronto/Peterborough/Oshawa, Ontario, Canada Web: http://www.dreaming.org/~mitayai IRC: Mitayai Email: mitayai@dreaming.org From owner-freebsd-hardware Sun Jan 7 20:28:24 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA10566 for hardware-outgoing; Sun, 7 Jan 1996 20:28:24 -0800 (PST) Received: from mailx.best.com (mailx.best.com [204.156.128.56]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA10560 Sun, 7 Jan 1996 20:28:16 -0800 (PST) Received: from shellx.best.com (shellx.best.com [206.86.0.11]) by mailx.best.com (950911.SGI.8.6.12.PATCH825/8.6.5) with ESMTP id EAA13635; Mon, 8 Jan 1996 04:30:19 GMT Received: from othello.selgus.com (brett.vip.best.com [205.149.181.145]) by shellx.best.com (950911.SGI.8.6.12.PATCH825/8.6.5) with SMTP id UAA29703; Sun, 7 Jan 1996 20:28:11 -0800 Message-ID: <30F09D41.2E90@selgus.com> Date: Sun, 07 Jan 1996 20:27:45 -0800 From: Brett Bourbin Organization: Selgus Limited X-Mailer: Mozilla 2.0b4 (Win95; I) MIME-Version: 1.0 To: sos@FreeBSD.org CC: freebsd-hardware@FreeBSD.org Subject: Re: PS/2 AUX mouse problems with 2.1 References: <199601070908.KAA06734@ra.dkuug.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hardware@FreeBSD.org Precedence: bulk sos@FreeBSD.org wrote: > Hmm I use it here, and it works fine for me, my config is something like: > > device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr > > that works on a ASUS p55tp4xeg motherboard with an IBM mouse.. > > There is work underways in this area as the way its done now is > not optimal Well, I have that same line and the probe failed for me. I have a Pentium 133 SCSI motherboard with a PS/2 AUX port onboard. Just to see if it was just Windows 95 doing some magic to find the mouse port, I used my Linux boot disk from another machine I have (which also has a PS/2 AUX mouse port), and it detected and installed the PS/2 mouse driver. So it was the FreeBSD PSM probe code-- so I commented out the actual test after the read of the DATA port in psmprobe(), and booted with my new kernel, and it loaded the driver and it worked fine with XFree86. This seems to say the probe code is wrong (maybe it just happens to work on some machines or maybe mine is slightly different). Since Linux got it correct, I check how they detected the PS/2 mouse, and they use an INT 11 to read the configuration and then check bit 2 (0x04) from the INT return value. FreeBSD seems to be trying to do some kind of handshake on the CNTRL port and then reading the DATA port. > Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team-- Brett Bourbin, President SELGUS LIMITED brett@selgus.com 555 Bryant Street, Suite 221 Palo Alto, CA 94301 From owner-freebsd-hardware Sun Jan 7 23:05:19 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA18004 for hardware-outgoing; Sun, 7 Jan 1996 23:05:19 -0800 (PST) Received: from wgrobez1.remote.louisville.edu (wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA17996 for ; Sun, 7 Jan 1996 23:05:13 -0800 (PST) Received: (from wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.3/8.6.12) id CAA00616; Sun, 7 Jan 1996 02:03:34 -0500 (EST) Date: Sun, 7 Jan 1996 02:03:33 -0500 (EST) From: Wicked Angel To: freebsd-hardware@FreeBSD.org Subject: ATAPI Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@FreeBSD.org Precedence: bulk HELP! :) I have an ATAPI cdrom(Don't stop reading yet) and for some reason FreeBSD can't detect it. I've tried everything, and I think the problem is that I have my secondary IDE controller on my SoundBlaster 32. My primary is built into the MB, and I have 2 hd's on it. The Cdrom is the MASTER device on the Soundblaster 32 device. FreeBSD will find the device, and while the kernel is booting it will probe for about 30seconds and won't find my cdrom! :( Any suggestions I'd apperciate it!!! Thanks again Gary From owner-freebsd-hardware Mon Jan 8 00:16:02 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA21196 for hardware-outgoing; Mon, 8 Jan 1996 00:16:02 -0800 (PST) Received: from ip2.uplift.fr (af@ip2.uplift.fr [194.51.20.70]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA21143 for ; Mon, 8 Jan 1996 00:15:54 -0800 (PST) Received: (from af@localhost) by ip2.uplift.fr (8.6.12/8.6.9) id JAA05113; Mon, 8 Jan 1996 09:16:53 +0100 Date: Mon, 8 Jan 1996 09:16:53 +0100 Message-Id: <199601080816.JAA05113@ip2.uplift.fr> From: Alain Forcioli To: freebsd-hardware@freebsd.org Sender: owner-hardware@freebsd.org Precedence: bulk unsubscribe freebsd-hardware From owner-freebsd-hardware Mon Jan 8 09:13:52 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA21820 for hardware-outgoing; Mon, 8 Jan 1996 09:13:52 -0800 (PST) Received: from ki1.chemie.fu-berlin.de (ki1.Chemie.FU-Berlin.DE [160.45.24.21]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA21814 for ; Mon, 8 Jan 1996 09:13:48 -0800 (PST) Received: by ki1.chemie.fu-berlin.de (Smail3.1.28.1) from mordillo (130.133.3.126) with smtp id ; Mon, 8 Jan 96 18:08 MET Received: (from graichen@localhost) by mordillo (8.6.12/8.6.12) id PAA01832; Mon, 8 Jan 1996 15:23:32 +0100 From: Thomas Graichen Message-Id: <199601081423.PAA01832@mordillo> Subject: Re: ATAPI To: wangel@wgrobez1.remote.louisville.edu (Wicked Angel) Date: Mon, 8 Jan 1996 15:23:32 +0100 (MET) Cc: freebsd-hardware@freebsd.org In-Reply-To: from "Wicked Angel" at Jan 7, 96 02:03:33 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hardware@freebsd.org Precedence: bulk hasn't Wicked Angel said ? ... > > HELP! :) > > I have an ATAPI cdrom(Don't stop reading yet) and for some reason FreeBSD > can't detect it. > > I've tried everything, and I think the problem is that I have my > secondary IDE controller on my SoundBlaster 32. My primary is built into > the MB, and I have 2 hd's on it. The Cdrom is the MASTER device on the > Soundblaster 32 device. > > FreeBSD will find the device, and while the kernel is booting it will > probe for about 30seconds and won't find my cdrom! :( > > Any suggestions I'd apperciate it!!! > i think a test if the second ide controller i ok would be to hang a disk onto it and see if it works - on the other side i also got a 4x ide cdrom only working as slave on the first controller - not as master (and only drive at the second one) - maybe you should put the slave disk from the first controller as master to the second and the cdrom as slave to the first t _______________________________________________________||___________________ __|| Perfection is reached, not when there is no __|| thomas graichen longer anything to add, but when there __|| freie universitaet berlin is no longer anything to take away __|| fachbereich physik __|| - Antoine de Saint-Exupery - __|| graichen@mail.physik.fu-berlin.de ___________________________||__________________graichen@FreeBSD.org_________ From owner-freebsd-hardware Mon Jan 8 09:19:42 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA22166 for hardware-outgoing; Mon, 8 Jan 1996 09:19:42 -0800 (PST) Received: from wgrobez1.remote.louisville.edu (wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA22161 for ; Mon, 8 Jan 1996 09:19:39 -0800 (PST) Received: (from wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.3/8.6.12) id MAA04650; Sun, 7 Jan 1996 12:17:53 -0500 (EST) Date: Sun, 7 Jan 1996 12:17:51 -0500 (EST) From: Wicked Angel To: Thomas Graichen cc: freebsd-hardware@freebsd.org Subject: Re: ATAPI In-Reply-To: <199601081423.PAA01832@mordillo> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org Precedence: bulk On Mon, 8 Jan 1996, Thomas Graichen wrote: > hasn't Wicked Angel said ? ... > i think a test if the second ide controller i ok would be to hang a > disk onto it and see if it works - on the other side i also got a 4x > ide cdrom only working as slave on the first controller - not as > master (and only drive at the second one) - maybe you should put the > slave disk from the first controller as master to the second and the > cdrom as slave to the first > > t > _______________________________________________________||___________________ > __|| > Perfection is reached, not when there is no __|| thomas graichen > longer anything to add, but when there __|| freie universitaet berlin > is no longer anything to take away __|| fachbereich physik > __|| > - Antoine de Saint-Exupery - __|| graichen@mail.physik.fu-berlin.de > ___________________________||__________________graichen@FreeBSD.org_________ > I didn't think about that, put my CDROM as a slave on my primary controller and my second hd as a master on my secondary device ;) I'll try that, thanks From owner-freebsd-hardware Mon Jan 8 16:26:08 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA21348 for hardware-outgoing; Mon, 8 Jan 1996 16:26:08 -0800 (PST) Received: from wgrobez1.remote.louisville.edu (wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA21332 for ; Mon, 8 Jan 1996 16:25:53 -0800 (PST) Received: (from wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.3/8.6.12) id TAA00218; Sun, 7 Jan 1996 19:24:04 -0500 (EST) Date: Sun, 7 Jan 1996 19:24:01 -0500 (EST) From: Wicked Angel To: Thomas Graichen , freebsd-hardware@freebsd.org Subject: Re: ATAPI In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org Precedence: bulk On Sun, 7 Jan 1996, Wicked Angel wrote: > > > On Mon, 8 Jan 1996, Thomas Graichen wrote: > > > hasn't Wicked Angel said ? ... > > i think a test if the second ide controller i ok would be to hang a > > disk onto it and see if it works - on the other side i also got a 4x > > ide cdrom only working as slave on the first controller - not as > > master (and only drive at the second one) - maybe you should put the > > slave disk from the first controller as master to the second and the > > cdrom as slave to the first > > > > t > > _______________________________________________________||___________________ > > __|| > > Perfection is reached, not when there is no __|| thomas graichen > > longer anything to add, but when there __|| freie universitaet berlin > > is no longer anything to take away __|| fachbereich physik > > __|| > > - Antoine de Saint-Exupery - __|| graichen@mail.physik.fu-berlin.de > > ___________________________||__________________graichen@FreeBSD.org_________ > > > I didn't think about that, put my CDROM as a slave on my primary > controller and my second hd as a master on my secondary device ;) > > I'll try that, thanks > > BTW: I just attempted that, no such luck, my computer couldn't find the second HD on the secondary controller, and yes, I have an AST bios ;) From owner-freebsd-hardware Mon Jan 8 22:08:12 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA11444 for hardware-outgoing; Mon, 8 Jan 1996 22:08:12 -0800 (PST) Received: from lonnie.tamarcom.com.au (lonnie.tamarcom.com.au [203.15.240.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA11415 for ; Mon, 8 Jan 1996 22:08:06 -0800 (PST) Received: (from cknight@localhost) by lonnie.tamarcom.com.au (8.6.12/8.6.12) id RAA05618 for freebsd-hardware@freebsd.org; Tue, 9 Jan 1996 17:08:07 +1100 From: Chris Knight Message-Id: <199601090608.RAA05618@lonnie.tamarcom.com.au> Subject: Acers & Fujitsus To: freebsd-hardware@freebsd.org Date: Tue, 9 Jan 1996 17:08:07 +1100 (EST) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org Precedence: bulk Howdy, I was wondering if anyone knew if FreeBSD will run on the AcerAltos 7000 series and/or the Intel Series of Fujitsu TeamServers. Any feedback will be greatly appreciated. Regards, -- Chris Knight Work: +61 03 347 866 Systems Administrator Home: +61 03 301 270 Tamar Communications http: http://www.tamarcom.com.au/~stryqx From owner-freebsd-hardware Mon Jan 8 22:44:52 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA16069 for hardware-outgoing; Mon, 8 Jan 1996 22:44:52 -0800 (PST) Received: from bunyip.cc.uq.oz.au (pp@bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA16056 for ; Mon, 8 Jan 1996 22:44:48 -0800 (PST) Received: from cc.uq.oz.au by bunyip.cc.uq.oz.au id <25357-0@bunyip.cc.uq.oz.au>; Tue, 9 Jan 1996 16:43:33 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id QAA29314; Tue, 9 Jan 1996 16:49:28 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id GAA06976; Tue, 9 Jan 1996 06:47:00 GMT Message-Id: <199601090647.GAA06976@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6.4 10/10/95 To: Chris Knight cc: freebsd-hardware@freebsd.org Subject: Re: Acers & Fujitsus In-reply-to: Your message of "Tue, 09 Jan 1996 17:08:07 +1100." <199601090608.RAA05618@lonnie.tamarcom.com.au> X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 09 Jan 1996 16:46:51 +1000 From: Stephen Hocking Sender: owner-hardware@freebsd.org Precedence: bulk > Howdy, > I was wondering if anyone knew if FreeBSD will run on the > AcerAltos 7000 series and/or the Intel Series of Fujitsu TeamServers. > Any feedback will be greatly appreciated. > Last time I stuck a boot floppy into a TeamServer (with EISA Adaptec controller, it was one of the AIC 7770 based ones) it recognised everything bar the ICL/FAL ethernet card fine. Unfortunately it had to have ICL's DRS/NX installed on it, so I never tried it further than that. Stephen -- I do not speak for the Worker's Compensation Board of Queensland - They don't pay me enough for that! From owner-freebsd-hardware Tue Jan 9 06:06:18 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA11420 for hardware-outgoing; Tue, 9 Jan 1996 06:06:18 -0800 (PST) Received: from cc.jyu.fi (root@cc.jyu.fi [130.234.1.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA11407 for ; Tue, 9 Jan 1996 06:06:08 -0800 (PST) Received: from [130.234.41.39] (zaphod.maccc.jyu.fi [130.234.41.39]) by cc.jyu.fi (8.7.2/8.7.2) with SMTP id QAA23633; Tue, 9 Jan 1996 16:05:23 +0200 (EET) X-Sender: kallio@pop.jyu.fi Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 9 Jan 1996 16:05:47 +0300 To: truesdel@nas.nasa.gov, shovey@buffnet.net From: kallio@cc.jyu.fi (Seppo Kallio) Subject: Linux Connectix QuickCam app Cc: hardware@freebsd.org Sender: owner-hardware@freebsd.org Precedence: bulk Found this ... Seppo ---------------------------------------------------------------- Subject: Connectix QuickCam (parallel-port) supported in Linux X-URL: ftp://ftp.nas.com/laird/README-0.2 ftp://ftp.nas.com/laird/README-0.2 README for qcam 0.2 This is the third alpha-test release of my control program for the Connectix QuickCam parallel port video camera. It enables you to take pictures with the camera at 320x240, 160x120, or 80x60 using 4 or 6 bits per pixel. This program may not work with your camera, and could possibly damage your system if used improperly. Use at your own risk. New Features since 0.1: ----------------------- I've included Paul Chinn's X frontend as 'xqcam', and enhanced it a bit. It supports the same command-line options as the original, plus a -C flag for using a private colormap and a -v flag for verbose operation. Right now, verbose mode only adds a running frame rate display. Added a TK front end to qcam to make it easier to experiment with brightness, contrast, and white balance settings. Added a new program ("probeqcam") to automatically probe for the QuickCam. Note: This may fail if an old version of "qcam" has accessed the camera recently. It wouldn't detect my QuickCam until I unplugged it and then replugged it. I added a qc_reset at the end of qc_scan, and that seems to have fixed the problem for now. Please test this on your system and report problems ASAP -- I want to add autoprobing to libqcam if the port isn't specified otherwise. Added support for SUID operation. Added code to library to automatically set the scan mode from resolution, bit depth. Added locking to qc_open/qc_close -- hopefully this will prevent multiple programs from trying to use the same camera at the same time. Usage: ------ qcam [options] [filename] Options: -x width Set width -y height Set height -p port Set port -B bpp Set bits per pixel -c val Set contrast -w val Set white balance -b val Set brightness -V Print version The program returns one image from the camera on standard output in PGM format. The default resolution is 160x120, and the default port is 0x378 (LPT1). There are command-line arguments to change these as well as a configuration file. If your camera is on your first parallel port (0x378 or /dev/lp1), then your should be able to run the program with no options and get a picture. If you are unsure which port your QuickCam is on, run probeqcam as root, and it should tell you. This program *must* run as root to allow access to the parallel port. This program can be run suid root, and should not pose a security problem. The makefile's install target installs qcam and xqcam into /usr/local/bin, suid root by default. Credits: -------- Several people have contributed to this, including Paul Chinn, Thomas Davis, Russell Nelson, and Simon Janes. Copyright: ---------- I've placed this program under the same copyright the X Consortium uses. Basically, it's free for any use whatsoever. If this manages to cause great problems for anyone (?) let me know and I suspect we can arrange something. Here's the notice: Copyright (C) 1996 by Scott Laird Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL SCOTT LAIRD BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Bugs: ----- This program has bugs. The known ones should be listed in the BUGS file that comes with this program. Please send bug reports/fixes to me at scott@laird.com, and I'll try to get the bug fixed for the next version. FTP Site: --------- The latest version of this program can be found in ftp://ftp.nas.com/laird Mailing List: ------------- There is a mailing list for discussing the QuickCam and Linux at linux-connectix@crynwr.com. Send mail to linux-connect-request@crynwr.com to be added to the list. Scott Laird scott@laird.com January 3, 1996. -- +-- Seppo Kallio ----- kallio@jyu.fi ---+ ! Computing Center ! Fax +358-41-603611 Phone +358-41-603606 ! ! University of Jyvaskyla ! http://www.jyu.fi/~kallio ! +-- Finland --+-- 62.14N 25.44E -- + From owner-freebsd-hardware Wed Jan 10 08:10:20 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA13112 for hardware-outgoing; Wed, 10 Jan 1996 08:10:20 -0800 (PST) Received: from acs3.bu.edu (root@ACS3.BU.EDU [128.197.153.30]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA13107 for ; Wed, 10 Jan 1996 08:10:16 -0800 (PST) From: rdmurphy@acs.bu.edu Received: by acs3.bu.edu (8.6.11/BU_SmartClient-1.0) id LAA84577; Wed, 10 Jan 1996 11:06:43 -0500 Date: Wed, 10 Jan 1996 11:06:43 -0500 Message-Id: <199601101606.LAA84577@acs3.bu.edu> To: freebsd-hardware@freebsd.org Subject: Req: Purchase recommendations Sender: owner-hardware@freebsd.org Precedence: bulk I hope this is the proper venue for this request; please correct me if it isn't. I am at last (after a long holdout) going to replace my home PC (an XT with 20MB hard drive and 1MB of RAM running PC-DOS 2.1 - don't laugh too much). I plan to run FreeBSD and do not have much need to run Windows or DOS applications. I don't need sound. I anticipate using the CD-ROM drive mostly to load new software; therefore I don't think I need anything particularly fast here. I'm looking for system, component, or vendor recommendations - both positive and negative. My budget is likely to be roughly $2400. Looking at various ads, it seems one can get a nice (?) EIDE Pentium system with 16MB RAM, 1 GB hard drive, and CD-ROM for this kind of money from places such as Dell and Micron. Questions: 1) Would these systems work with FreeBSD? 2) Assuming they would, what kind of arguments would anyone offer to push me away from EIDE and toward SCSI? 3) What other recommendations would you have? 4) Much less pressing: is there any possibility that I could take my old 20MB drive, install it in the new machine and mount it as a DOS drive to be used for whatever DOS stuff I do need to do? I have been trying to read as much of the hardware related information in various FAQs and at www.freebsd.org, but it's not yet entirely clear. For what it's worth, I think I am fairly knowledgable, but not at all expert. I have a couple years of experience with IBM's AIX, DEC's OSF/1 (now DIGITAL Unix), and a bunch of other non-Unix operating systems. I am not a hardware guy. Thanks much for any guidance you can offer. Russ Murphy From owner-freebsd-hardware Wed Jan 10 12:49:09 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA00817 for hardware-outgoing; Wed, 10 Jan 1996 12:49:09 -0800 (PST) Received: from relay5.UU.NET (relay5.UU.NET [192.48.96.15]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA00785 for ; Wed, 10 Jan 1996 12:48:46 -0800 (PST) Received: from uucp5.UU.NET by relay5.UU.NET with SMTP id QQzxyp18942; Wed, 10 Jan 1996 15:48:44 -0500 (EST) Received: from uanet.UUCP by uucp5.UU.NET with UUCP/RMAIL ; Wed, 10 Jan 1996 15:48:45 -0500 Received: by crocodil.monolit.kiev.ua; Wed, 10 Jan 96 22:47:02 +0200 Received: (from dk@localhost) by dog.farm.org (8.6.11/dk#3) id UAA18539 for freebsd-hardware@freebsd.org; Wed, 10 Jan 1996 20:31:29 +0200 From: Dmitry Kohmanyuk Message-Id: <199601101831.UAA18539@dog.farm.org> Subject: anyone there using AMD's 133MHz chips? To: freebsd-hardware@freebsd.org Date: Wed, 10 Jan 1996 18:31:29 +0000 () Reply-To: dk+@ua.net X-Class: Fast X-OS-Of-Choice: FreeBSD 2.0.5-RELEASE X-NIC-Handle: DK379 X-Mailer: ELM [version 2.4 PL22 dk9] Content-Type: text Sender: owner-hardware@freebsd.org Precedence: bulk are there any problems/opinions on them? It is worth to choose them over 120MHz ones? (i.e., time make world on both) From owner-freebsd-hardware Wed Jan 10 14:54:18 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA09310 for hardware-outgoing; Wed, 10 Jan 1996 14:54:18 -0800 (PST) Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA09302 for ; Wed, 10 Jan 1996 14:54:10 -0800 (PST) Received: by Sysiphos id AA13484 (5.67b/IDA-1.5 for freebsd-hardware@freebsd.org); Wed, 10 Jan 1996 23:53:01 +0100 Message-Id: <199601102253.AA13484@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Wed, 10 Jan 1996 23:53:00 +0100 In-Reply-To: Dmitry Kohmanyuk "anyone there using AMD's 133MHz chips?" (Jan 10, 18:31) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: dk+@ua.net Subject: Re: anyone there using AMD's 133MHz chips? Cc: freebsd-hardware@freebsd.org Sender: owner-hardware@freebsd.org Precedence: bulk On Jan 10, 18:31, Dmitry Kohmanyuk wrote: } Subject: anyone there using AMD's 133MHz chips? } are there any problems/opinions on them? It is worth to choose them } over 120MHz ones? (i.e., time make world on both) Well, I just rebooted my ASUS SP3G after doing a close examination of its internals, with the goal to find out whether the AMD 486/133 (also known as AMD 5x86) will work. Guess it will do! AMD seems to have gone back to Intel conventions regarding the positions of CLKMUL and WB/WT pins. Only difference is, that the 2x/3x jumper becomes a 4x/2x jumper now :) According to some reports I read, the 5x86 is not significantly faster than the 486DX4/120, but it has the advantage to work well on PCI only mother boards, which prefer a 33MHz bus clock (and don't like a 40MHz clock at all :-) The 5x86 seems to be available at some $129 single quantity. Didn't ask for a DX4/120 price, since that chip can't be used in my system ... Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-hardware Wed Jan 10 18:54:49 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA23856 for hardware-outgoing; Wed, 10 Jan 1996 18:54:49 -0800 (PST) Received: from gw3.pacbell.com (gw3.PacBell.COM [129.245.2.24]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA23847 Wed, 10 Jan 1996 18:54:45 -0800 (PST) Received: from popper.PacBell.COM by gw3.pacbell.com (5.x/PacBell-10/18/95) id AA16008; Wed, 10 Jan 1996 18:54:32 -0800 Received: from ipms_pc (15iddz102158.scrm3600.PacBell.COM) by popper.PacBell.COM (5.0/SMI-SVR4) id AA13450; Wed, 10 Jan 1996 18:54:26 -0800 Message-Id: <9601110254.AA13450@popper.PacBell.COM> X-Sender: dlhodge@192.100.81.136 X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 10 Jan 1996 18:53:53 -0800 To: se@freebsd.org From: dlhodge@netcom.com (Dave Hodge) Subject: Please Help. Attempting to load freebsd v2.1 on DeskPro XL 575 Cc: hardware@freebsd.org Sender: owner-hardware@freebsd.org Precedence: bulk Stefan, I received your address from Gary at of the Freebsd Project Team in Walnut Creek. Gary said that you may be able to help me via either a installation method that you had developed or kernal/bootdisk that will allow me to install Freebsd v2.1 to my Compaq DeskPro XL 575. I have tried using the instruction that are available at the WEB site "http://tci00.uibk.ac.at:80/xl/", but I was unsuccessful. It was like a "Catch 22" situation. The WEB instructions were all base on LINUX Slackware distributions and not FreeBSD. I was required to obtain a kernel and place it on a DOS bootable disk that contain some file that were capable of re-addressing the memory location of the PCI driver. Unfortuately you had to have the kernel first, which meant that your system had to be working: frustrating! Any help will be appreciated. Thank You Very Much .. David Hodge dlhodge@netcom.com From owner-freebsd-hardware Wed Jan 10 19:38:47 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA25784 for hardware-outgoing; Wed, 10 Jan 1996 19:38:47 -0800 (PST) Received: from gw3.pacbell.com (gw3.PacBell.COM [129.245.2.24]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA25773 Wed, 10 Jan 1996 19:38:41 -0800 (PST) Received: from popper.PacBell.COM by gw3.pacbell.com (5.x/PacBell-10/18/95) id AA17659; Wed, 10 Jan 1996 19:38:41 -0800 Received: from ipms_pc (15iddz102158.scrm3600.PacBell.COM) by popper.PacBell.COM (5.0/SMI-SVR4) id AA14310; Wed, 10 Jan 1996 19:38:40 -0800 Message-Id: <9601110338.AA14310@popper.PacBell.COM> X-Sender: dlhodge@192.100.81.136 X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 10 Jan 1996 19:38:01 -0800 To: se@freebsd.org From: dlhodge@netcom.com (Dave Hodge) Subject: More information on the DeskPro XL 575 trouble. Thanks! Cc: hardware@freebsd.org Sender: owner-hardware@freebsd.org Precedence: bulk Hi Stefan, Here is some information that I recovered during the boot attempt. pcibus_setup(1): mode1res=0x8000000c (0x80000000), mode2res=0x0c (0x0e) Gary said this may be of some importance. Thank you. David Hodge dlhodge@netcom.com From owner-freebsd-hardware Thu Jan 11 03:38:24 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA27967 for hardware-outgoing; Thu, 11 Jan 1996 03:38:24 -0800 (PST) Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA27906 for ; Thu, 11 Jan 1996 03:38:10 -0800 (PST) Received: by Sysiphos id AA26065 (5.67b/IDA-1.5 for hardware@freebsd.org); Thu, 11 Jan 1996 12:37:10 +0100 Message-Id: <199601111137.AA26065@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Thu, 11 Jan 1996 12:37:09 +0100 In-Reply-To: dlhodge@netcom.com (Dave Hodge) "Please Help. Attempting to load freebsd v2.1 on DeskPro XL 575" (Jan 10, 18:53) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: dlhodge@netcom.com (Dave Hodge) Subject: Re: Please Help. Attempting to load freebsd v2.1 on DeskPro XL 575 Cc: hardware@freebsd.org Sender: owner-hardware@freebsd.org Precedence: bulk On Jan 10, 18:53, Dave Hodge wrote: } Subject: Please Help. Attempting to load freebsd v2.1 on DeskPro XL 575 } Stefan, } } I received your address from Gary at of the Freebsd Project Team in Walnut } Creek. Gary said that you may be able to help me via either a installation } method that you had developed or kernal/bootdisk that will allow me to } install Freebsd v2.1 to my Compaq DeskPro XL 575. Ok. I will try to get you going ... } I have tried using the instruction that are available at the WEB site } "http://tci00.uibk.ac.at:80/xl/", but I was unsuccessful. It was like a } "Catch 22" situation. The WEB instructions were all base on LINUX Slackware } distributions and not FreeBSD. I was required to obtain a kernel and place } it on a DOS bootable disk that contain some file that were capable of } re-addressing the memory location of the PCI driver. Unfortuately you had to } have the kernel first, which meant that your system had to be working: } frustrating! Hmmm, please give some information on what you tried so far, to get FreeBSD installed. The problem Linux has with that Compaq does in no way affect FreeBSD. But Compaq has a long tradition of doing things just slightly different, and to break the rules. I've had a lot of problems to get their non-compliant PCI chip sets probed correctly by the kernel. Please try to boot from the FreeBSD boot floppy and enter "-v" at the "Boot: " prompt. I'm interested in all numbers from the lines starting with "pcibus_*" and "pci0*". Then I'd like to know how it fails in the end. The Compaq seems to use the AMD Combo Ethernet and SCSI chip. This is a variant of the NCR 5380 (not the 53c810 !), and there is no direct driver support, currently. I'll have to check, whether anybody had success making it work under FreeBSD. This chip will not be automatically probed, but you may have success if you enter its port address into the FreeBSD boot config menu. The Ethernet part of that chip is said to work with the Lance driver (lnc0), and you will have to enter some port and irq value (which can be found by repeated reboots with -v, a little inconvenient, I know). Please send VERBOSE boot messages (write down ALL numbers, if you have no other means of saving the message log), and I'll tell you how to proceed. Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-hardware Thu Jan 11 03:50:36 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA29951 for hardware-outgoing; Thu, 11 Jan 1996 03:50:36 -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 DAA29927 for ; Thu, 11 Jan 1996 03:50:29 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id LAA13469 for ; Thu, 11 Jan 1996 11:48:42 GMT Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Thu, 11 Jan 1996 11:48:59 +0000 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id LAA12479; Thu, 11 Jan 1996 11:48:58 GMT From: Paul Richards Message-Id: <199601111148.LAA12479@cadair.elsevier.co.uk> Subject: Re: Please Help. Attempting to load freebsd v2.1 on DeskPro XL 575 To: se@zpr.uni-koeln.de (Stefan Esser) Date: Thu, 11 Jan 1996 11:48:57 +0000 (GMT) Cc: dlhodge@netcom.com, hardware@FreeBSD.org In-Reply-To: <199601111137.AA26065@Sysiphos> from "Stefan Esser" at Jan 11, 96 12:37:09 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hardware@FreeBSD.org Precedence: bulk In reply to Stefan Esser who said > > The Ethernet part of that chip is said to > work with the Lance driver (lnc0), and you > will have to enter some port and irq value > (which can be found by repeated reboots > with -v, a little inconvenient, I know). > It should do. The chip is basically two chips in one that are completely independant of each other and the lnc0 driver should just see it as a plain PCnet-PCI chip. It'll probably probe as a PCnet-VL chip though because of a known problem in the lance probe code for PCI (yes, I'll look at this soon :-) I'd be interested to see the probe output too and to hear if the lnc0 driver does work properly with this chip. The few reports I've had suggests it does. -- Paul Richards. Originative Solutions Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-hardware Thu Jan 11 04:16:20 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA05419 for hardware-outgoing; Thu, 11 Jan 1996 04:16:20 -0800 (PST) Received: from nwpeople.demon.co.uk (nwpeople.demon.co.uk [158.152.27.96]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA05361 for ; Thu, 11 Jan 1996 04:16:08 -0800 (PST) Date: Thu, 11 Jan 1996 11:32:28 GMT From: iain@nwpeople.demon.co.uk (Iain Baird) Reply-To: iain@nwpeople.demon.co.uk Message-Id: <16105@nwpeople.demon.co.uk> To: freebsd-hardware@freebsd.org (Stefan Esser) Cc: se@zpr.uni-koeln.de (Stefan Esser) Subject: Re: anyone there using AMD's 133MHz chips? X-Mailer: PCElm 1.10 Lines: 26 Sender: owner-hardware@freebsd.org Precedence: bulk Stefan Esser writes: > On Jan 10, 18:31, Dmitry Kohmanyuk wrote: > } Subject: anyone there using AMD's 133MHz chips? > } are there any problems/opinions on them? It is worth to choose them > } over 120MHz ones? (i.e., time make world on both) > > According to some reports I read, the 5x86 is not > significantly faster than the 486DX4/120, but it > has the advantage to work well on PCI only mother > boards, which prefer a 33MHz bus clock (and don't > like a 40MHz clock at all :-) I'm running a DX4-120 on a GA-486AMS PCI-only motherboard. This can clock PCI at CPU/2. By default, with CPU at 40MHz, PCI runs at 20MHz. However: I have tried setting CPU:PCI to 1:1, so PCI is clocked at 40MHz, and everything seems to work fine. So far at least. I have an AHA-2940 and a Diamond Stealth 64 (S3 968). I haven't done any benchmarking to compare the performance. Any comments on the wisdom of this? -- Iain Baird Network People International Tel: +44 (0)1732 743591 From owner-freebsd-hardware Thu Jan 11 04:26:30 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA07986 for hardware-outgoing; Thu, 11 Jan 1996 04:26:30 -0800 (PST) Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA07812 Thu, 11 Jan 1996 04:25:41 -0800 (PST) Received: by Sysiphos id AA27117 (5.67b/IDA-1.5); Thu, 11 Jan 1996 13:24:34 +0100 Message-Id: <199601111224.AA27117@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Thu, 11 Jan 1996 13:24:33 +0100 In-Reply-To: dlhodge@netcom.com (Dave Hodge) "More information on the DeskPro XL 575 trouble. Thanks!" (Jan 10, 19:38) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: dlhodge@netcom.com (Dave Hodge) Subject: Re: More information on the DeskPro XL 575 trouble. Thanks! Cc: hardware@freebsd.org, jkh@freebsd.org Sender: owner-hardware@freebsd.org Precedence: bulk On Jan 10, 19:38, Dave Hodge wrote: } Subject: More information on the DeskPro XL 575 trouble. Thanks! } Hi Stefan, } } Here is some information that I recovered during the boot attempt. } } } pcibus_setup(1): mode1res=0x8000000c (0x80000000), mode2res=0x0c (0x0e) o, well. THAT Compaq chip set ... The next FreeBSD SNAP will use the PCI probe code from FreeBSD-current, which should work a lot better on your system ... Perhaps we can get Jordan to release a pre-SNAP boot floppy, which would help somebody else, too ... (Hi Jordan, how about it ???) } Gary said this may be of some importance. Well, yes, and he was right :-) But it won't help you, sorry ... :( The problem is that Compaq has a long history of chip sets which break the (PCI) rules. I received mail from a Compaq engineer who told me, they did compensate for that in software (BIOS and drivers) and saw no need to make their hardware behave according to the PCI spec. requirements! This means it is not possible to make a save distinction between PCI and some EISA chip sets, and since I could not risk loosing EISA support in FreeBSD-2.1, it was impossible to correctly deal with all those Compaq chip sets :( Your best bet is either installing to that SCSI drive connected to another computer (you'll have to weaken a test, or just compile in a file from -current). Then you still have to make sure, that the "nca0" driver can be made to work with the AMD SCSI+Ethernet Combo chip. Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-hardware Thu Jan 11 04:46:51 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA12062 for hardware-outgoing; Thu, 11 Jan 1996 04:46:51 -0800 (PST) Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA12044 for ; Thu, 11 Jan 1996 04:46:46 -0800 (PST) Received: by Sysiphos id AA27510 (5.67b/IDA-1.5 for freebsd-hardware@freebsd.org); Thu, 11 Jan 1996 13:39:15 +0100 Message-Id: <199601111239.AA27510@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Thu, 11 Jan 1996 13:39:15 +0100 In-Reply-To: iain@nwpeople.demon.co.uk (Iain Baird) "Re: anyone there using AMD's 133MHz chips?" (Jan 11, 11:32) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: iain@nwpeople.demon.co.uk Subject: Re: anyone there using AMD's 133MHz chips? Cc: freebsd-hardware@freebsd.org Sender: owner-hardware@freebsd.org Precedence: bulk On Jan 11, 11:32, Iain Baird wrote: } Subject: Re: anyone there using AMD's 133MHz chips? } Stefan Esser writes: } > On Jan 10, 18:31, Dmitry Kohmanyuk wrote: } > } Subject: anyone there using AMD's 133MHz chips? } > } are there any problems/opinions on them? It is worth to choose them } > } over 120MHz ones? (i.e., time make world on both) } > } > According to some reports I read, the 5x86 is not } > significantly faster than the 486DX4/120, but it } > has the advantage to work well on PCI only mother } > boards, which prefer a 33MHz bus clock (and don't } > like a 40MHz clock at all :-) } } I'm running a DX4-120 on a GA-486AMS PCI-only motherboard. } This can clock PCI at CPU/2. By default, with CPU at 40MHz, } PCI runs at 20MHz. } } However: I have tried setting CPU:PCI to 1:1, so PCI is clocked } at 40MHz, and everything seems to work fine. So far at least. } I have an AHA-2940 and a Diamond Stealth 64 (S3 968). I haven't } done any benchmarking to compare the performance. } } Any comments on the wisdom of this? Well, this has got nothing at all to do with wisdom. But a lot with luck ;-) PCI chip sets are designed for a 33MHz upper limit, and I'd be afraid of overheating the expensive S3 or AIC chips, and the mainboard PCI chip set as well (eek, all soldered in :) I'd rather spend a few $ on the 133MHz variant, even if it is no faster than the DX4/120. But that is a matter of personal taste ... Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-hardware Thu Jan 11 05:16:11 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA17813 for hardware-outgoing; Thu, 11 Jan 1996 05:16:11 -0800 (PST) Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA17278 for ; Thu, 11 Jan 1996 05:14:02 -0800 (PST) Received: by Sysiphos id AA29433 (5.67b/IDA-1.5 for hardware@FreeBSD.org); Thu, 11 Jan 1996 14:07:54 +0100 Message-Id: <199601111307.AA29433@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Thu, 11 Jan 1996 14:07:53 +0100 In-Reply-To: Paul Richards "Re: Please Help. Attempting to load freebsd v2.1 on DeskPro XL 575" (Jan 11, 11:48) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: Paul Richards Subject: Re: Please Help. Attempting to load freebsd v2.1 on DeskPro XL 575 Cc: dlhodge@netcom.com, hardware@freebsd.org Sender: owner-hardware@freebsd.org Precedence: bulk On Jan 11, 11:48, Paul Richards wrote: } Subject: Re: Please Help. Attempting to load freebsd v2.1 on DeskPro XL 57 } In reply to Stefan Esser who said } > } > The Ethernet part of that chip is said to } > work with the Lance driver (lnc0), and you } > will have to enter some port and irq value } > (which can be found by repeated reboots } > with -v, a little inconvenient, I know). } > } } It should do. The chip is basically two chips in one that are } completely independant of each other and the lnc0 driver should just } see it as a plain PCnet-PCI chip. It'll probably probe as a PCnet-VL } chip though because of a known problem in the lance probe code for } PCI (yes, I'll look at this soon :-) This would be fine. It has become a FAQ ... I've looked into the Lance driver, and found that there are MANY references to the isa device data structure. But then, you can easily malloc one from the PCI probe code ... :) } I'd be interested to see the probe output too and to hear if the lnc0 } driver does work properly with this chip. The few reports I've had } suggests it does. Yes, there have been some success reports. The situation is not that bad, as all that is required is to enter the port address and irq into the boot config tool. But the bad thing is, that the IRQ will not be printed in the PCI probe message for an "unknown" device. Have considered to change this... Hmmm, guess I will do it! Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-hardware Thu Jan 11 05:57:37 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA24357 for hardware-outgoing; Thu, 11 Jan 1996 05:57:37 -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 FAA24352 for ; Thu, 11 Jan 1996 05:57:34 -0800 (PST) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id NAA14093 for ; Thu, 11 Jan 1996 13:55:38 GMT Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Thu, 11 Jan 1996 13:55:48 +0000 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id NAA13907; Thu, 11 Jan 1996 13:55:46 GMT From: Paul Richards Message-Id: <199601111355.NAA13907@cadair.elsevier.co.uk> Subject: Re: Please Help. Attempting to load freebsd v2.1 on DeskPro XL 575 To: se@zpr.uni-koeln.de (Stefan Esser) Date: Thu, 11 Jan 1996 13:55:46 +0000 (GMT) Cc: dlhodge@netcom.com, hardware@FreeBSD.org In-Reply-To: <199601111307.AA29433@Sysiphos> from "Stefan Esser" at Jan 11, 96 02:07:53 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hardware@FreeBSD.org Precedence: bulk In reply to Stefan Esser who said > > } see it as a plain PCnet-PCI chip. It'll probably probe as a PCnet-VL > } chip though because of a known problem in the lance probe code for > } PCI (yes, I'll look at this soon :-) > > This would be fine. It has become a FAQ ... > I've looked into the Lance driver, and found that there > are MANY references to the isa device data structure. > But then, you can easily malloc one from the PCI probe > code ... :) Not surprising, it's an ISA driver :-) > Yes, there have been some success reports. The situation > is not that bad, as all that is required is to enter the > port address and irq into the boot config tool. But the > bad thing is, that the IRQ will not be printed in the PCI > probe message for an "unknown" device. Have considered to > change this... Hmmm, guess I will do it! All that's needed is to get the IRQ and port from the PCI code but I've been delaying fixing this because I don't really want to hack a specific fix into lnc0 for what is a generic problem i.e. many devices have a core set of code that works across a chipset family and needs different glue code to hook it into different buses (or even different architectures when we go down that road since the core lance code would be the same on a Sun platform). It needs some re-architecting though all through the device driver sub-system. -- Paul Richards. Originative Solutions Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-hardware Thu Jan 11 06:48:11 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA26080 for hardware-outgoing; Thu, 11 Jan 1996 06:48:11 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA26073 Thu, 11 Jan 1996 06:48:08 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id GAA11948; Thu, 11 Jan 1996 06:46:37 -0800 To: se@zpr.uni-koeln.de (Stefan Esser) cc: dlhodge@netcom.com (Dave Hodge), hardware@freebsd.org, jkh@freebsd.org Subject: Re: More information on the DeskPro XL 575 trouble. Thanks! In-reply-to: Your message of "Thu, 11 Jan 1996 13:24:33 +0100." <199601111224.AA27117@Sysiphos> Date: Thu, 11 Jan 1996 06:46:37 -0800 Message-ID: <11946.821371597@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hardware@freebsd.org Precedence: bulk > Perhaps we can get Jordan to release > a pre-SNAP boot floppy, which would > help somebody else, too ... > (Hi Jordan, how about it ???) Could you please be more specific? A snap of... 2.1? 2.2? What do you also mean by `pre-snap'? :) Jordan From owner-freebsd-hardware Thu Jan 11 08:43:32 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA03016 for hardware-outgoing; Thu, 11 Jan 1996 08:43:32 -0800 (PST) Received: from pancake.remcomp.fr (root@pancake.remcomp.fr [194.51.30.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA03007 for ; Thu, 11 Jan 1996 08:43:18 -0800 (PST) Received: (from didier@localhost) by zapata.omnix.fr.org (8.6.12/8.6.9) id TAA17954; Thu, 11 Jan 1996 19:40:46 +0100 Date: Thu, 11 Jan 1996 19:40:46 +0100 (MET) From: didier@omnix.fr.org To: Stefan Esser cc: iain@nwpeople.demon.co.uk, freebsd-hardware@FreeBSD.org Subject: Re: anyone there using AMD's 133MHz chips? In-Reply-To: <199601111239.AA27510@Sysiphos> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@FreeBSD.org Precedence: bulk On Thu, 11 Jan 1996, Stefan Esser wrote: > On Jan 11, 11:32, Iain Baird wrote: > } Subject: Re: anyone there using AMD's 133MHz chips? > } Stefan Esser writes: > } > On Jan 10, 18:31, Dmitry Kohmanyuk wrote: > } > } Subject: anyone there using AMD's 133MHz chips? > } > } are there any problems/opinions on them? It is worth to choose them > } > } over 120MHz ones? (i.e., time make world on both) > } > > } > According to some reports I read, the 5x86 is not > } > significantly faster than the 486DX4/120, but it > } > has the advantage to work well on PCI only mother > } > boards, which prefer a 33MHz bus clock (and don't > } > like a 40MHz clock at all :-) > } > } I'm running a DX4-120 on a GA-486AMS PCI-only motherboard. > } This can clock PCI at CPU/2. By default, with CPU at 40MHz, > } PCI runs at 20MHz. > } > } However: I have tried setting CPU:PCI to 1:1, so PCI is clocked > } at 40MHz, and everything seems to work fine. So far at least. > } I have an AHA-2940 and a Diamond Stealth 64 (S3 968). I haven't > } done any benchmarking to compare the performance. > } > } Any comments on the wisdom of this? > > Well, this has got nothing at all to do with wisdom. > But a lot with luck ;-) > > PCI chip sets are designed for a 33MHz upper limit, > and I'd be afraid of overheating the expensive S3 > or AIC chips, and the mainboard PCI chip set as well > (eek, all soldered in :) > > I'd rather spend a few $ on the 133MHz variant, even > if it is no faster than the DX4/120. > > But that is a matter of personal taste ... > > Regards, STefan > > -- > Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 > Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 > ============================================================================== > http://www.zpr.uni-koeln.de/~se > I have been using a 486DX4-120 on my AL3 mother board (chipset acer labs) without any problems for nearly 3 months. When I replaced the 486DX4-100 by a 486DX4-120 the speed was dramaticly improved (37%) . I've never had any problems with the PCI boards. (AHA2940 and Miro Crystal 20SV) -- Didier Derny | My computer is Microsoft Free... didier@aida.org | Private FreeBSD 2.1-STABLE site From owner-freebsd-hardware Thu Jan 11 11:20:50 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA12546 for hardware-outgoing; Thu, 11 Jan 1996 11:20:50 -0800 (PST) Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA12530 for ; Thu, 11 Jan 1996 11:20:28 -0800 (PST) Received: by Sysiphos id AA10314 (5.67b/IDA-1.5 for hardware@freebsd.org); Thu, 11 Jan 1996 20:17:47 +0100 Message-Id: <199601111917.AA10314@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Thu, 11 Jan 1996 20:17:47 +0100 In-Reply-To: "Jordan K. Hubbard" "Re: More information on the DeskPro XL 575 trouble. Thanks!" (Jan 11, 6:46) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: "Jordan K. Hubbard" Subject: Re: More information on the DeskPro XL 575 trouble. Thanks! Cc: dlhodge@netcom.com (Dave Hodge), hardware@freebsd.org Sender: owner-hardware@freebsd.org Precedence: bulk On Jan 11, 6:46, "Jordan K. Hubbard" wrote: } Subject: Re: More information on the DeskPro XL 575 trouble. Thanks! } > Perhaps we can get Jordan to release } > a pre-SNAP boot floppy, which would } > help somebody else, too ... } > (Hi Jordan, how about it ???) } } Could you please be more specific? A snap of... 2.1? 2.2? } What do you also mean by `pre-snap'? :) 1) I'd like it to be for 2.2-SNAP. 2) pre-snap was meant to mean, that just the kernel and the sysinstall++ binary have to be there. Since building a boot floppy requires a "make release", it would take too long on my small system. Now, if you manage to build a SNAP boot floppy, (even if the full SNAP isn't complete at that time), I'd like to have access to the boot floppy with the -current PCI probe code compiled into the kernel. I'd really like to have verbose PCI probe output from the -current pcibus.c. This would let me know, whether there are further changes required to make the 2.2 PCI probe support the Compaq ... Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-hardware Thu Jan 11 12:37:10 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA18089 for hardware-outgoing; Thu, 11 Jan 1996 12:37:10 -0800 (PST) Received: from gw3.pacbell.com (gw3.PacBell.COM [129.245.2.24]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA18083 Thu, 11 Jan 1996 12:37:06 -0800 (PST) Received: from popper.PacBell.COM by gw3.pacbell.com (5.x/PacBell-10/18/95) id AA06343; Thu, 11 Jan 1996 12:36:59 -0800 Received: from ipms_pc (15iddz102158.scrm3600.PacBell.COM) by popper.PacBell.COM (5.0/SMI-SVR4) id AA09707; Thu, 11 Jan 1996 12:36:57 -0800 Message-Id: <9601112036.AA09707@popper.PacBell.COM> X-Sender: dlhodge@192.100.81.136 X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 11 Jan 1996 12:36:20 -0800 To: se@freebsd.org From: dlhodge@netcom.com (Dave Hodge) Subject: Here is all the information from "Boot -v" on my Compaq DeskPro XL 575 Cc: hardware@freebsd.org Sender: owner-hardware@freebsd.org Precedence: bulk Hello Stefan, I hope this is all the information that you've requested. I am willing to help where ever possible. The only caveat is that I am a bit of NOVICE. Here is the information: ------------------------------------------------------------------------------ Boot: -v Booting fd (0,a) /Kernel at 0x20c000 text=0xfc000 data=0x0 loss=0xa00 symbols=[+0x600+0x4+0x27c+0x4+0x1fb] total=0x30947f entry point=0x20c000 Uncompressing kernel ... done Booting Kernel BIOS basemem (639K) !=RTC basemem (640K) Copyright (c) 1982, 1986, 1989, 1991, 1993 The Reqents of the University of California FreeBSD 2.1.0-RELEASE #0: Sat Nove 18 10:21:19 1995 jkh@werhill.cdrom.com:/usr/src/sys/compile/BOOTMFS CPU: 75-MHZ Pentium 734\90 or 815\100 (Pentium-class CPU) Origin="GenuineIntel" Id=0x524 Stepping=4 Features=0x1bf real memory= 16777216 (16384K bytes) avail memory= 13770752 (13448K bytes) Probing for devices on the ISA bus: sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 ed1 not found at 0x300 sio0 at 0x3f8-0x3ff irq 4 on isa sio0 type 16550A sio1 not found at 0x2f8 sio2 not found at 0x3e8 sio3 not found at 0x2e8 lpt0 at 0x378-0x37f irq 7 on isa lpt0 Interrupt-driven port lp0: TCP/IP Capable interface lpt1 not found at 0xffffffff lpt2 not found at 0xffffffff mse0: wrong signature ff mse0: not found at 0x23c fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: 1.44 MB 3.5 in wdc0 not found at 0x1f0 wdc1 not found at 0x170 bt0 not found at 0x330 uha0 not found at 0x330 ahc1 not found ahb0 not found aha0 not found at 0x330 aic0 not found at 0x340 nca0 not found at 0x1f88 nca1 not found at 0x350 sea0 not found wt0 not found at 0x300 mcd0: timeout getting status mcd0 not found at 0x340 mcd1: timeout getting status mcd1 not found at 0x340 matcdc0 not found at 0x230 scd0 not found at 0x230 le0 not found at 0x360 ep0 not found at 0x300 lx0 not found at 0x300 le0 no board found at 0x300 lnc0 not found at 0x300 lnc1 not found at 0x280 ze0 not found at 0x300 zp0 not found at 0x300 npx0 on mother board npx0:INT 16 interface pcibus_setup(1): mode1res=0x8000000c (0x80000000), mode2res=0x0c (0x0e) rootfs is 1000 Kbyte compiled in MFS BIOS Gemometries: 0:01fe3f20 0..510=511 cylinders, 0..63=64 heads, 1..32=32 sectors 1:00000000 0..=1 cylinders, 0..0=1 heads, 1..0=0 sectors 2:00000000 0..=1 cylinders, 0..0=1 heads, 1..0=0 sectors 3:00000000 0..=1 cylinders, 0..0=1 heads, 1..0=0 sectors 4:00000000 0..=1 cylinders, 0..0=1 heads, 1..0=0 sectors 5:00000000 0..=1 cylinders, 0..0=1 heads, 1..0=0 sectors 6:00000000 0..=1 cylinders, 0..0=1 heads, 1..0=0 sectors 7:00000000 0..=1 cylinders, 0..0=1 heads, 1..0=0 sectors 0: accounted for ------------------------------------------------------------------------------ Thanks again .. David Hodge dlhodge@netcom.com From owner-freebsd-hardware Thu Jan 11 19:13:17 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA18786 for hardware-outgoing; Thu, 11 Jan 1996 19:13:17 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA18769 for ; Thu, 11 Jan 1996 19:13:04 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id TAA00381; Thu, 11 Jan 1996 19:12:00 -0800 To: se@zpr.uni-koeln.de (Stefan Esser) cc: dlhodge@netcom.com (Dave Hodge), hardware@freebsd.org Subject: Re: More information on the DeskPro XL 575 trouble. Thanks! In-reply-to: Your message of "Thu, 11 Jan 1996 20:17:47 +0100." <199601111917.AA10314@Sysiphos> Date: Thu, 11 Jan 1996 19:11:59 -0800 Message-ID: <379.821416319@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hardware@freebsd.org Precedence: bulk I still have some trouble with the bin distribution in -current, but I'm working on it. I should have a 2.2 SNAP shortly! Jordan > On Jan 11, 6:46, "Jordan K. Hubbard" wrote: > } Subject: Re: More information on the DeskPro XL 575 trouble. Thanks! > } > Perhaps we can get Jordan to release > } > a pre-SNAP boot floppy, which would > } > help somebody else, too ... > } > (Hi Jordan, how about it ???) > } > } Could you please be more specific? A snap of... 2.1? 2.2? > } What do you also mean by `pre-snap'? :) > > 1) I'd like it to be for 2.2-SNAP. > 2) pre-snap was meant to mean, that just the kernel and > the sysinstall++ binary have to be there. > > Since building a boot floppy requires a "make release", it > would take too long on my small system. > > Now, if you manage to build a SNAP boot floppy, (even if > the full SNAP isn't complete at that time), I'd like to > have access to the boot floppy with the -current PCI probe > code compiled into the kernel. > > I'd really like to have verbose PCI probe output from the > -current pcibus.c. This would let me know, whether there > are further changes required to make the 2.2 PCI probe > support the Compaq ... > > Regards, STefan > > -- > Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 > Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 > ============================================================================ == > http://www.zpr.uni-koeln.de/~se From owner-freebsd-hardware Fri Jan 12 06:33:09 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA12911 for hardware-outgoing; Fri, 12 Jan 1996 06:33:09 -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 GAA12906 Fri, 12 Jan 1996 06:33:04 -0800 (PST) Received: (from owensc@localhost) by itsdsv1.enc.edu (8.6.11/8.6.9) id JAA13587; Fri, 12 Jan 1996 09:32:33 -0500 Date: Fri, 12 Jan 1996 09:32:33 -0500 (EST) From: Charles Owens To: questions list FreeBSD cc: freebsd-hardware@freebsd.org Subject: Should I buy an Exabyte 8205XLE 8mm tape drive? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org Precedence: bulk Hi, I'm thinking about buying an Exabyte 8205XLE 8mm SCSI tape drive. Should I? I've dug through the freebsd list archives and have seen mixed reviews. Some folks seem to swear by them and others seem to have plenty of trouble. Could some kind soul provide something of an authoritative answer as to whether or not these drives work well with FreeBSD (2.1-stable and up)? Is there anything special I need to do to get them to work? Thanks much, --- ------------------------------------------------------------------------- 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 Fri Jan 12 08:02:19 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA18128 for hardware-outgoing; Fri, 12 Jan 1996 08:02:19 -0800 (PST) Received: from ponder (ponder.csci.unt.edu [129.120.3.16]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA18104 Fri, 12 Jan 1996 08:02:11 -0800 (PST) Received: from poseidon.csci.unt.edu by ponder (5.61/1.36) id AA18308; Fri, 12 Jan 96 10:02:40 -0600 Date: Fri, 12 Jan 1996 10:02:49 -0700 (MST) From: Dongil Shin X-Sender: dshin@poseidon.csci.unt.edu To: freebsd-hardware@freebsd.org, freebsd-questions@freebsd.org Subject: Anyone using 3Com 3c589 (PCMCIA)? Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org Precedence: bulk I've got a lap-top with 3c589. I set up the card for IRQ 10 and I/O 300h. After I recompiled the kernel, it still does not recognize it. The following line is in my kernel configuration file. device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zpintr If you know a clue or answer, please let me know. p.s. I am using FreeBSD 2.0.5. --------------------------------------------------------------------- PO BOX 13886 (Dongil Shin) INTERNET: dshin@cs.unt.edu Dept. of Comp. Sci. WWW : http://poseidon.csci.unt.edu/shin.html Univ. of North Texas VOICE : 817-565-2088 (Office) FAX: 817-565-2799 Denton, TX 76203-3886 OFFICE : GAB 542A From owner-freebsd-hardware Fri Jan 12 08:38:50 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA20294 for hardware-outgoing; Fri, 12 Jan 1996 08:38:50 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA20289 Fri, 12 Jan 1996 08:38:37 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id JAA24693; Fri, 12 Jan 1996 09:41:09 -0700 Date: Fri, 12 Jan 1996 09:41:09 -0700 From: Nate Williams Message-Id: <199601121641.JAA24693@rocky.sri.MT.net> To: Dongil Shin Cc: freebsd-hardware@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Anyone using 3Com 3c589 (PCMCIA)? In-Reply-To: References: Sender: owner-hardware@freebsd.org Precedence: bulk > I've got a lap-top with 3c589. I set up the card for IRQ 10 and > I/O 300h. After I recompiled the kernel, it still does not recognize > it. Are you using 'card-services' under DOS to configure it, or are you using the 3COM configuration utility (w/out card-services loaded) to save the settings on the card? You must do the latter until the PCCARD support is better integrated. I've used the 3C589[BC] cards under FreeBSD w/out problems on 4 different laptops, so it *should* work. Also, did you note that IOMEM. Under DOS it's not mentioned, but in the 3COM utility you can see it by looking at the 'card stats' or something like that. If you need more help, send me private email. Nate From owner-freebsd-hardware Fri Jan 12 08:46:03 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA20875 for hardware-outgoing; Fri, 12 Jan 1996 08:46:03 -0800 (PST) Received: from atlas.com (gw.atlas.com [205.139.124.67]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA20870 for ; Fri, 12 Jan 1996 08:45:55 -0800 (PST) Received: from billthecat.atlas.com. (billthecat.atlas.com [97.12.13.38]) by atlas.com (8.7.1/8.7.1) with SMTP id IAA01452 for ; Fri, 12 Jan 1996 08:44:07 -0800 (PST) Received: by billthecat.atlas.com. (4.1/SMI-4.1) id AA08287; Fri, 12 Jan 96 08:47:53 PST Message-Id: <9601121647.AA08287@billthecat.atlas.com.> Subject: NEC 2Xc CD changer supported? To: hardware@freebsd.org Date: Fri, 12 Jan 1996 08:47:53 -0800 (PST) From: "Brant Katkansky" X-Mailer: ELM [version 2.4 PL25] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org Precedence: bulk I'm in the market for a CD changer, and have found a good deal on a NEC 2Xc 7 disk (SCSI-2) model. Has anyone used this under FreeBSD, particularily with an NCR PCI SCSI host adapter? -- Brant Katkansky (brantk@atlas.com) Systems Test Engineer, ADC From owner-freebsd-hardware Fri Jan 12 09:20:04 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA22819 for hardware-outgoing; Fri, 12 Jan 1996 09:20:04 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA22757 Fri, 12 Jan 1996 09:19:57 -0800 (PST) Received: from mail.zrz.TU-Berlin.DE (mail.zrz.TU-Berlin.DE [130.149.4.15]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id JAA08717 ; Fri, 12 Jan 1996 09:18:40 -0800 Received: from itrsp2.fb10.tu-berlin.de by mail.zrz.TU-Berlin.DE with SMTP (PP); Fri, 12 Jan 1996 17:00:30 +0100 Date: Fri, 12 Jan 1996 17:03:12 +0100 (MET) From: Goetz Fischer To: hackers@FreeBSD.ORG Cc: hardware@FreeBSD.ORG Subject: HELP pci mach64 blanks screen (fwd) Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@FreeBSD.ORG Precedence: bulk Hi ! I have a problem with Gigabyte GA-586ATE PB Cache Mainboard and Asus PCI-V264CT (ATI OEM mach64 Xpession 2MB Dram). If I enable sio0 and/or sio1 the screen blanks while probing devices and never come back. Without probing sio's it's ok but no mouse and modem. I know that mach64 uses adress off sio3 (com4) but I have no sio2/3. I build a new kernel with only probing sio0 and sio1, but no fun :-( What to do?? Hope for help. By Goetz From owner-freebsd-hardware Fri Jan 12 10:09:59 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA25160 for hardware-outgoing; Fri, 12 Jan 1996 10:09:59 -0800 (PST) Received: from Aspen.Woc.Atinc.COM (aspen.woc.atinc.com [198.138.38.205]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA25150 for ; Fri, 12 Jan 1996 10:09:48 -0800 (PST) Received: (from jmb@localhost) by Aspen.Woc.Atinc.COM (8.6.12/8.6.9) id NAA03089; Fri, 12 Jan 1996 13:09:47 -0500 Date: Fri, 12 Jan 1996 13:09:45 -0500 (EST) From: "Jonathan M. Bresler" X-Sender: jmb@Aspen.Woc.Atinc.COM To: Brant Katkansky cc: hardware@freebsd.org Subject: Re: NEC 2Xc CD changer supported? In-Reply-To: <9601121647.AA08287@billthecat.atlas.com.> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org Precedence: bulk On Fri, 12 Jan 1996, Brant Katkansky wrote: > I'm in the market for a CD changer, and have found a good deal on a > NEC 2Xc 7 disk (SCSI-2) model. > > Has anyone used this under FreeBSD, particularily with an NCR PCI SCSI > host adapter? yesterday i got the nakamichi "NRC MBR-7 110". scsi-ii, 2x speed, 7 cdrom, model. $139.50 including fedex ground shipping. 1 yr warranty. applied the cd.c, scsiconf.c and ncr.c patches. (the patches are small, cd.c and ncr.c are both one-liners.) works like a champ. i number of developers and core team members have this drive, so you will be well supported :) corporate systems center http://www.corpsys.com/ 408-734-disk (expect to wait on the phone). their part number is CD7. now i have online source 1.1, 2.0, 2.0.5, and 2.1. shame 1.1.5.1 was never on cd ;(( i have the tarballs, etc, anyone want to burn a cd for me? jmb Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG play go. ride bike. hack FreeBSD.--ah the good life i am moving to a new job. PLEASE USE: jmb@FreeBSD.ORG From owner-freebsd-hardware Fri Jan 12 10:45:29 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA28155 for hardware-outgoing; Fri, 12 Jan 1996 10:45:29 -0800 (PST) Received: from atlas.com (gw.atlas.com [205.139.124.67]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA28149 Fri, 12 Jan 1996 10:45:21 -0800 (PST) Received: from billthecat.atlas.com. (billthecat.atlas.com [97.12.13.38]) by atlas.com (8.7.1/8.7.1) with SMTP id KAA00896; Fri, 12 Jan 1996 10:44:09 -0800 (PST) Received: by billthecat.atlas.com. (4.1/SMI-4.1) id AA08665; Fri, 12 Jan 96 10:47:55 PST Message-Id: <9601121847.AA08665@billthecat.atlas.com.> Subject: Re: NEC 2Xc CD changer supported? To: jmb@freebsd.org (Jonathan M. Bresler) Date: Fri, 12 Jan 1996 10:47:54 -0800 (PST) From: "Brant Katkansky" Cc: brantk@gatekeeper.atlas.com, hardware@freebsd.org In-Reply-To: from "Jonathan M. Bresler" at Jan 12, 96 01:09:45 pm X-Mailer: ELM [version 2.4 PL25] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org Precedence: bulk > > On Fri, 12 Jan 1996, Brant Katkansky wrote: > > > I'm in the market for a CD changer, and have found a good deal on a > > NEC 2Xc 7 disk (SCSI-2) model. > > > > Has anyone used this under FreeBSD, particularily with an NCR PCI SCSI > > host adapter? > > yesterday i got the nakamichi "NRC MBR-7 110". scsi-ii, 2x speed, > 7 cdrom, model. $139.50 including fedex ground shipping. 1 yr warranty. > applied the cd.c, scsiconf.c and ncr.c patches. (the patches are small, > cd.c and ncr.c are both one-liners.) works like a champ. i number of > developers and core team members have this drive, so you will be well > supported :) Good price. The NEC is available from Tiger Direct (+1-800-888-4437) for ten bucks more, with a longer warranty (quantities are probably limited). Fedex overnight is 6.99. I've had good luck with NEC products, so that's what I'm gonna get. Are the patches in question applicable to 2.1-RELEASE? If so, where might I find them? I'm net-impaired for a few days (the net weenies broke our firewall) so I'd appreciate it if someone could mail me the patches. > now i have online source 1.1, 2.0, 2.0.5, and 2.1. shame 1.1.5.1 > was never on cd ;(( i have the tarballs, etc, anyone want to burn a cd for > me? Hey, disk space is cheap, and 1.1.5.1 isn't _that_ big. :) -- Brant Katkansky (brantk@atlas.com) Systems Test Engineer, ADC From owner-freebsd-hardware Fri Jan 12 12:01:04 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA01944 for hardware-outgoing; Fri, 12 Jan 1996 12:01:04 -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 MAA01935 Fri, 12 Jan 1996 12:00:57 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id GAA21300; Sat, 13 Jan 1996 06:57:06 +1100 Date: Sat, 13 Jan 1996 06:57:06 +1100 From: Bruce Evans Message-Id: <199601121957.GAA21300@godzilla.zeta.org.au> To: gofi1033@itrsp2.fb10.tu-berlin.de, hackers@freebsd.org Subject: Re: HELP pci mach64 blanks screen (fwd) Cc: hardware@freebsd.org Sender: owner-hardware@freebsd.org Precedence: bulk >I have a problem with Gigabyte GA-586ATE PB Cache Mainboard and >Asus PCI-V264CT (ATI OEM mach64 Xpession 2MB Dram). If I enable sio0 >and/or sio1 the screen blanks while probing devices and never come back. >Without probing sio's it's ok but no mouse and modem. >I know that mach64 uses adress off sio3 (com4) but I have no sio2/3. >I build a new kernel with only probing sio0 and sio1, but no fun :-( >What to do?? Delete the hard-coded sio3 address in sio.c, or run -current. Bruce From owner-freebsd-hardware Fri Jan 12 20:19:19 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA04170 for hardware-outgoing; Fri, 12 Jan 1996 20:19:19 -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 UAA04157 for ; Fri, 12 Jan 1996 20:18:40 -0800 (PST) Received: (from hosokawa@localhost) by frig.mt.cs.keio.ac.jp (8.6.12+2.4W/3.4Wbeta3) id NAA01377; Sat, 13 Jan 1996 13:16:56 +0900 Date: Sat, 13 Jan 1996 13:16:56 +0900 Message-Id: <199601130416.NAA01377@frig.mt.cs.keio.ac.jp> To: dshin@ponder.csci.unt.edu Cc: freebsd-hardware@freebsd.org, hosokawa@mt.cs.keio.ac.jp Subject: Re: Anyone using 3Com 3c589 (PCMCIA)? In-Reply-To: Your message of Fri, 12 Jan 1996 10:02:49 -0700 (MST). From: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.18PL3] 1994-08/01(Mon) Sender: owner-hardware@freebsd.org Precedence: bulk In article dshin@ponder.csci.unt.edu writes: >> I've got a lap-top with 3c589. I set up the card for IRQ 10 and >> I/O 300h. After I recompiled the kernel, it still does not recognize it. >> The following line is in my kernel configuration file. >> >> device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zpintr >> >> If you know a clue or answer, please let me know. If you're using 3C589C, comment out the following lines (about 530th line of if_zp.c). POKE(isa_dev->id_maddr, 0x80); /* reset the card (how long?) */ DELAY(40000); or can you test our PC-card package I announced yesterday. -- 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