From owner-freebsd-hardware Wed Jan 21 18:07:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26939 for hardware-outgoing; Wed, 21 Jan 1998 18:07:55 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26785 for ; Wed, 21 Jan 1998 18:05:48 -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 MAA00641; Thu, 22 Jan 1998 12:28:26 +1030 (CST) Message-Id: <199801220158.MAA00641@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Christian Fortin cc: freebsd-hardware@FreeBSD.ORG Subject: Re: 3M LS-120 support ? In-reply-to: Your message of "Wed, 21 Jan 1998 14:17:44 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Jan 1998 12:28:24 +1030 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Is FreeBSD support the 3M LS-120 drive ? -stable and -current have support for ATAPI removables, yes. > see it at: > > http://www.imation.com/dsp/ls120/ > > rw for regular 1.44M and 120M optical at an hard drive speed! IDE > street price ~250$ US They're cheaper, and slower, than that. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ From owner-freebsd-hardware Fri Jan 23 17:37:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08870 for hardware-outgoing; Fri, 23 Jan 1998 17:37:48 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from stcgate.statcan.ca (stcgate.statcan.ca [142.206.192.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA08864 for ; Fri, 23 Jan 1998 17:37:40 -0800 (PST) (envelope-from jeays@statcan.ca) Received: (from root@localhost) by stcgate.statcan.ca (8.6.11/8.6.9) id UAA05703 for ; Fri, 23 Jan 1998 20:40:54 -0500 Received: from stcinet.statcan.ca(142.206.128.146) by stcgate via smap (V1.3) id sma005692; Sat Jan 24 01:40:02 1998 Received: from statcan.ca by statcan.ca (SMI-8.6/SMI-SVR4) id UAA08226; Fri, 23 Jan 1998 20:38:41 -0500 Date: Fri, 23 Jan 1998 20:35:52 -0500 (EST) From: Mike Jeays X-Sender: jeays@austral To: freebsd-hardware@FreeBSD.ORG Subject: Iomega Zip drives (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have an IDE CD-ROM as the master and an Iomega 100MB ZIP IDE drive as the slave on my second controller. Before I installed the Zip drive, the CD-ROM functioned correctly. When I add the Zip drive, I cannot access either device; disklabel -r and mount both hang, and sometimes (well - usually) crash the OS. Here is the DMESG output, and two attempts at a kernel configuration file; neither work. OS version is 2.2.1. Can anyone advise me if these two devices can work on the same controller, and if so, how I can do it? I would appreciate parameters for disklabel and newfs if I can get that far. Will an upgrade to 2.2.5 or even 3.0 fix the problem? Both devices are seen correctly by Windows 95, which configured itself automatically to my annoyance! I can only use the Zip drive for backup by: a) Writing a tar file to the MS-DOS file system b) Opening the case and plugging in the Zip drive c) Booting Win95 and copying the file. Not a convenient or dignified procedure! --------------------------------------------------------------------- DMESG output wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 406MB (832608 sectors), 826 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): wd1: 1627MB (3332448 sectors), 3306 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, dma, iordis wcd0: 1378Kb/sec, 128Kb cache, audio play, 256 volume levels, ejectable tray wcd0: 120mm data disc loaded, unlocked wdc1: unit 1 (atapi): , removable, intr, iordis ie0 not found at 0x360 --------------------------------------------------------------------- First attempt: controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device wcd0 #IDE CD-ROM # device wcd1 #Iomega Zip drive --------------------------------------------------------------------- Second attempt: controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 option ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device wcd0 #IDE CD-ROM device wcd1 #Iomega Zip drive From owner-freebsd-hardware Fri Jan 23 17:41:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09191 for hardware-outgoing; Fri, 23 Jan 1998 17:41:23 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from doberman.cisco.com (doberman.cisco.com [171.69.1.178]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA09182 for ; Fri, 23 Jan 1998 17:41:11 -0800 (PST) (envelope-from brainey@cisco.com) Received: from brainey-ss20.cisco.com (brainey-ss20.cisco.com [171.69.193.41]) by doberman.cisco.com (8.6.12/8.6.5) with ESMTP id RAA29895; Fri, 23 Jan 1998 17:40:39 -0800 Received: (brainey@localhost) by brainey-ss20.cisco.com (8.6.12/CISCO.WS.1.1) id RAA18281; Fri, 23 Jan 1998 17:40:38 -0800 Date: Fri, 23 Jan 1998 17:40:38 -0800 Message-Id: <199801240140.RAA18281@brainey-ss20.cisco.com> From: Bill Rainey To: hardware@FreeBSD.ORG Subject: Intel Pro 100/B Ethernet card - PCI irq assignment Reply-to: brainey@cisco.com Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've installed a EtherExpress Pro 100/B card and the system seems to be running fine with it but I have a question about the way IRQs are assigned for PCI devices. I noticed after I config'd the kernel and installed the card that fxp0 was sharing IRQ 11 with the WinCast/TV and the Matrox Millenium cards. It this reasonable (a feature of the PCI bus) or should it really have its own IRQ ? How is IRQ assignment done for PCI cards ? As I said, it seems to work okay so far. Thanks, Bill Rainey ----------------------------------------------------------------------- FreeBSD 3.0-CURRENT #0: Fri Jan 23 03:36:15 PST 1998 brainey@avatar.cisco.com:/src/current/sys/compile/AVATAR CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x616 Stepping=6 Features=0xf9ff real memory = 134217728 (131072K bytes) avail memory = 127897600 (124900K bytes) Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.2.0 > bktr0: rev 0x11 int a irq 11 on pci0.6.0 Hauppauge WinCast/TV, Philips NTSC tuner, dbx stereo. > fxp0: rev 0x02 int a irq 11 on pci0 .10.0 fxp0: Ethernet address 00:a0:c9:8e:ed:19 > vga0: rev 0x01 int a irq 11 on pci0.1 2.0 ahc0: rev 0x00 int a irq 10 on pci0.14 .0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ----------------------------------------------------------------------- From owner-freebsd-hardware Fri Jan 23 18:04:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14386 for hardware-outgoing; Fri, 23 Jan 1998 18:04:54 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA14379 for ; Fri, 23 Jan 1998 18:04:45 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.73 #1) id 0xvuhq-00043l-00; Fri, 23 Jan 1998 17:48:22 -0800 Date: Fri, 23 Jan 1998 17:48:21 -0800 (PST) From: Tom To: Bill Rainey cc: hardware@FreeBSD.ORG Subject: Re: Intel Pro 100/B Ethernet card - PCI irq assignment In-Reply-To: <199801240140.RAA18281@brainey-ss20.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 23 Jan 1998, Bill Rainey wrote: > > I've installed a EtherExpress Pro 100/B card and the system seems to be > running fine with it but I have a question about the way IRQs are > assigned for PCI devices. > > I noticed after I config'd the kernel and installed the card that fxp0 > was sharing IRQ 11 with the WinCast/TV and the Matrox Millenium > cards. It this reasonable (a feature of the PCI bus) or should it > really have its own IRQ ? How is IRQ assignment done for PCI cards ? > As I said, it seems to work okay so far. IRQs are assigned by your motherboard. PCI supports IRQ sharing. > Thanks, > Bill Rainey > > ----------------------------------------------------------------------- > FreeBSD 3.0-CURRENT #0: Fri Jan 23 03:36:15 PST 1998 > brainey@avatar.cisco.com:/src/current/sys/compile/AVATAR > CPU: Pentium Pro (199.43-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x616 Stepping=6 > Features=0xf9ff > real memory = 134217728 (131072K bytes) > avail memory = 127897600 (124900K bytes) > Probing for devices on PCI bus 0: > chip0: rev 0x02 on pci0.2.0 > > bktr0: rev 0x11 int a irq 11 on pci0.6.0 > Hauppauge WinCast/TV, Philips NTSC tuner, dbx stereo. > > fxp0: rev 0x02 int a irq 11 on pci0 > .10.0 > fxp0: Ethernet address 00:a0:c9:8e:ed:19 > > vga0: rev 0x01 int a irq 11 on pci0.1 > 2.0 > ahc0: rev 0x00 int a irq 10 on pci0.14 > .0 > ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs > ----------------------------------------------------------------------- > > Tom From owner-freebsd-hardware Fri Jan 23 18:36:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17856 for hardware-outgoing; Fri, 23 Jan 1998 18:36:42 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from colossus.dyn.ml.org (dburr@199-170-160-85.la.inreach.net [199.107.160.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA17818 for ; Fri, 23 Jan 1998 18:36:25 -0800 (PST) (envelope-from dburr@colossus.dyn.ml.org) Received: (from dburr@localhost) by colossus.dyn.ml.org (8.8.7/8.8.7) id SAA12543; Fri, 23 Jan 1998 18:36:32 -0800 (PST) (envelope-from dburr) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 23 Jan 1998 18:35:18 -0800 (PST) Organization: Starfleet Command From: Donald Burr To: Mike Jeays Subject: RE: Iomega Zip drives (fwd) Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- My secret spy satellite informs me that on 24-Jan-98, Mike Jeays wrote: >Thanks for using NetForward! >http://www.netforward.com >v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v > > >I have an IDE CD-ROM as the master and an Iomega 100MB ZIP IDE drive >as the slave on my second controller. Before I installed the Zip >drive, the CD-ROM functioned correctly. When I add the Zip drive, >I cannot access either device; disklabel -r and mount both hang, and >sometimes (well - usually) crash the OS. Sometimes, when you have and an IDE CD-ROM drive on the same bus, the CD-ROM has to be the slave device. YOu could try setting the Zip as the master and the CD as the slave. Other than that, it is remotely possible that they are just incompatible together. I don't see that as often these days, but it is still possible I suppose... - --- Donald Burr - Ask me for my PGP key | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ #1347455 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNMlTsPjpixuAwagxAQHDzwP/Q7ct+GxZtVahbAHZp1YhA67QSX0mXy0G iQfPyeqsWiIxzXR8AAgcoYqi1YYoXWR8Mz56hhyVB8qhF0tXY8y8odXrbieupTcE PQymaiPjzoe5bfPHoUTvL/WQL5iPWHjqgUhpWS0QuOZQQQnMVpXPwVOUC3baDsG2 BQt733m55TE= =U38y -----END PGP SIGNATURE----- From owner-freebsd-hardware Fri Jan 23 19:35:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA23786 for hardware-outgoing; Fri, 23 Jan 1998 19:35:40 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from word.smith.net.au (ppp3.portal.net.au [202.12.71.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA23765 for ; Fri, 23 Jan 1998 19:35:25 -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 NAA00910; Sat, 24 Jan 1998 13:58:18 +1030 (CST) Message-Id: <199801240328.NAA00910@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mike Jeays cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Iomega Zip drives (fwd) In-reply-to: Your message of "Fri, 23 Jan 1998 20:35:52 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 24 Jan 1998 13:58:17 +1030 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I have an IDE CD-ROM as the master and an Iomega 100MB ZIP IDE drive > as the slave on my second controller. Before I installed the Zip > drive, the CD-ROM functioned correctly. When I add the Zip drive, > I cannot access either device; disklabel -r and mount both hang, and > sometimes (well - usually) crash the OS. The Zip is an ATAPI device, not an IDE device. (Big difference 8). > Here is the DMESG output, and two attempts at a kernel configuration > file; neither work. OS version is 2.2.1. There is no support for the ATAPI Zip in 2.2.1. You will need to upgrade to -stable (or 2.2.6 when it is released). At this point in time, the driver in -stable is *broken* for the Zip. Some clarification of the boot messages (you appear to have confused "the device is detected" with "the device is handled by a driver"). > wdc1 at 0x170-0x177 irq 15 on isa > wdc1: unit 0 (atapi): , removable, accel, dma, iordis The generic IDE code finds your second controller, and discovers an ATAPI device connected. (wdc*) > wcd0: 1378Kb/sec, 128Kb cache, audio play, 256 volume levels, ejectable tray > wcd0: 120mm data disc loaded, unlocked The ATAPI CDROM driver claims the CDROM. (wcd*) > wdc1: unit 1 (atapi): , removable, intr, > iordis The generic IDE code discovers your Zip. No drivers claim it though. During testing, I have observed that the presence of an ATAPI Zip as a secondary unit has caused problems. If W95 works correctly on your system, it would be fair to characterise this as a defect in the FreeBSD ATAPI driver. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\