From owner-freebsd-scsi Mon May 15 7:23:23 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from exmta2.rjf.com (exmta2.rjf.com [170.12.31.84]) by hub.freebsd.org (Postfix) with ESMTP id E5B4137B740 for ; Mon, 15 May 2000 07:23:16 -0700 (PDT) (envelope-from ICartwright@IT.RJF.com) Received: by exmta2.rjf.com with Internet Mail Service (5.5.2448.0) id ; Mon, 15 May 2000 10:23:16 -0400 Message-ID: <6D5097D4B56AD31190D50008C7B1579B91204C@EXLAN5> From: Ian Cartwright To: "'freebsd-scsi@freebsd.org'" Subject: SCSI Speeds? Date: Mon, 15 May 2000 10:23:14 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, all. I have a question regarding the relative speeds of devices on a SCSI bus. I have two machines currently running FreeBSD. One is a P-200 with IDE and one is a PII-360 with both IDE and SCSI drives. I boot off the the SCSI bus on this machine. The IDE drives on both machines are UDMA-33. My SCSI drives are as follows (reported by FreeBSD on boot up): ID0: Fast SCSI2 HDD 10.00 MB Xfer (Synchronous), ID1: Ultra SCSI2 HDD 40.00 MB Xfer (Synchronous), ID2: SCSI2 CD-ROM 10.00 MB Xfer (Async), ID4: SCSI CD-Writer 3.300 MB Xfer (Async), ID5: SCSI2 Tape (Xfer not reported, Asynch). My question is this: why does it seem that the slower machine does disk access much faster? When I was installing these machines newfs wrote superblocks to the IDE drives much faster than to the SCSI drives, even though the Ultra SCSI drive (my FreeBSD drive) should theoretically be much faster... Many disk intensive operations seem to be faster on the IDE drives. Any ideas as to why this should be? Thanks! Ian Cartwright Senior Engineer Raymond James Associates icartwright@it.rjf.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 15 8:41: 1 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.quantum.com (mx1.quantum.com [204.212.103.34]) by hub.freebsd.org (Postfix) with ESMTP id 4D1E337B9D4 for ; Mon, 15 May 2000 08:40:58 -0700 (PDT) (envelope-from Stephen.Byan@quantum.com) Received: from milcmima.qntm.com (milcmima.qntm.com [146.174.18.61]) by mx1.quantum.com (8.9.3 (PHNE_18979)/8.9.3) with ESMTP id IAA26015; Mon, 15 May 2000 08:40:51 -0700 (PDT) Received: by milcmima.qntm.com with Internet Mail Service (5.5.2650.10) id ; Mon, 15 May 2000 08:40:50 -0700 Message-ID: <8133266FE373D11190CD00805FA768BF02EE9FA8@shrcmsg1.tdh.qntm.com> From: Stephen Byan To: "'Ian Cartwright'" , "'freebsd-scsi@freebsd.org'" Subject: RE: SCSI Speeds? Date: Mon, 15 May 2000 08:40:46 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.10) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just guessing, but I suspect it's because the IDE drives are caching writes, while the SCSI drives are not. Try enabling write-caching on the SCSI drives. Unfortunately, this will expose a data integrity risk in the event of a power failure (you are already exposed to this risk on your IDE drives). fsck may not be able to unscramble the file system, since some of the synchronous writes of UFS meta-data may not have made it to the disk media before the power fail. I don't recommend enabling write-caching for drives holding UFS file systems unless you have an uninterruptible power supply on the system and the drives. Perhaps the I/O subsystem will someday be educated to selectively disable write-caching on UFS metadata writes, but until then, beware of enabling write-caching. Regards, -Steve Byan - not speaking for Quantum Corp. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 15 18:50:35 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id D18DF37B534 for ; Mon, 15 May 2000 18:50:24 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA10632; Tue, 16 May 2000 11:20:57 +0930 (CST) Date: Tue, 16 May 2000 11:20:57 +0930 From: Greg Lehey To: Ian Cartwright Cc: freebsd-scsi@freebsd.org Subject: Re: SCSI Speeds? Message-ID: <20000516112057.A10269@freebie.lemis.com> References: <6D5097D4B56AD31190D50008C7B1579B91204C@EXLAN5> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <6D5097D4B56AD31190D50008C7B1579B91204C@EXLAN5> Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Monday, 15 May 2000 at 10:23:14 -0400, Ian Cartwright wrote: > Hello, all. > > I have a question regarding the relative speeds of devices on a SCSI bus. I > have two machines currently running FreeBSD. One is a P-200 with IDE and one > is a PII-360 with both IDE and SCSI drives. I boot off the the SCSI bus on > this machine. The IDE drives on both machines are UDMA-33. My SCSI drives > are as follows (reported by FreeBSD on boot up): ID0: Fast SCSI2 HDD 10.00 > MB Xfer (Synchronous), ID1: Ultra SCSI2 HDD 40.00 MB Xfer (Synchronous), > ID2: SCSI2 CD-ROM 10.00 MB Xfer (Async), ID4: SCSI CD-Writer 3.300 MB Xfer > (Async), ID5: SCSI2 Tape (Xfer not reported, Asynch). > > My question is this: why does it seem that the slower machine does disk > access much faster? When I was installing these machines newfs wrote > superblocks to the IDE drives much faster than to the SCSI drives, even > though the Ultra SCSI drive (my FreeBSD drive) should theoretically be much > faster... Many disk intensive operations seem to be faster on the IDE > drives. Any ideas as to why this should be? The IDE disks are probably just simply faster. Don't confuse the transfer rate with the disk speed. No drives I know of can currently hit 33 MB/s, so that's not the issue, and some recent IDE drives are blindingly fast. If you want to check, run rawio (/usr/ports/benchmarks/rawio) against the drives and see what speeds it comes up with. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 15 19:15:14 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id B8E9C37B5E4 for ; Mon, 15 May 2000 19:15:06 -0700 (PDT) (envelope-from dkelly@hiwaay.net) Received: from nospam.hiwaay.net (tnt6-216-180-5-68.dialup.HiWAAY.net [216.180.5.68]) by mail.hiwaay.net (8.10.1/8.10.1) with ESMTP id e4G2F1311393; Mon, 15 May 2000 21:15:01 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id UAA38353; Mon, 15 May 2000 20:38:06 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <200005160138.UAA38353@nospam.hiwaay.net> X-Mailer: exmh version 2.1.1 10/15/1999 To: Ian Cartwright Cc: "'freebsd-scsi@freebsd.org'" Subject: Re: SCSI Speeds? In-Reply-To: Message from Ian Cartwright of "Mon, 15 May 2000 10:23:14 EDT." <6D5097D4B56AD31190D50008C7B1579B91204C@EXLAN5> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 May 2000 20:38:05 -0500 From: David Kelly Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ian Cartwright writes: > My question is this: why does it seem that the slower machine does disk > access much faster? You didn't say how you measured. Others before you have observed IDE drives performing simple tasks faster than SCSI drives. Most notably when running simple operating systems from Microsoft. The consensus is the IDE read/write head is closer to the CPU than with SCSI. That it takes less time to set up an IDE transfer. The downside of IDE is that a drive can only do one thing at a time. And when one drive on the IDE cable is busy the other can not be accessed. Have heard that one day ATA/IDE drives may have SCSI-like multitasking. Its common for IDE drives to cache reads and writes to mask their single tasking nature. Its uncommon to be given any control over this caching, or over bad block management. It *is* common to have this control over SCSI devices. It is also common (but not mandatory) to be able to send multiple commands to a SCSI device before the first command has completed. Just as its common (but not mandatory) for a device to accept a command then step off the bus and allow others to use it while its processing its command(s). Scanners with SCSI interfaces are well known for barely implementing SCSI. If you have a SCSI scanner its best to dedicate a SCSI controller/bus to it. For a single user desktop SCSI is likely not to be the fastest disk solution. But IMHO SCSI devices are more robust because those who choose SCSI are usually more willing to pay for quality, while those who choose ATA/IDE are buying by price. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 16 3:16:30 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mercury.gfit.net (ns.gfit.net [209.41.124.90]) by hub.freebsd.org (Postfix) with ESMTP id E04EC37B55E for ; Tue, 16 May 2000 03:16:27 -0700 (PDT) (envelope-from tom@embt.com) Received: from paranor (tmp1-868d.rochester.rr.com [24.161.86.141]) by mercury.gfit.net (8.8.8/8.8.8) with SMTP id FAA03041; Tue, 16 May 2000 05:16:59 -0500 (CDT) (envelope-from tom@embt.com) Message-Id: <3.0.3.32.20000516061507.00de28b0@mail.gfit.com> X-Sender: tembt@mail.gfit.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Tue, 16 May 2000 06:15:07 -0400 To: Greg Lehey , Ian Cartwright From: Tom Embt Subject: Re: SCSI Speeds? Cc: freebsd-scsi@FreeBSD.ORG In-Reply-To: <20000516112057.A10269@freebie.lemis.com> References: <6D5097D4B56AD31190D50008C7B1579B91204C@EXLAN5> <6D5097D4B56AD31190D50008C7B1579B91204C@EXLAN5> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 11:20 5/16/2000 +0930, Greg Lehey wrote: >On Monday, 15 May 2000 at 10:23:14 -0400, Ian Cartwright wrote: >> Hello, all. >> >> I have a question regarding the relative speeds of devices on a SCSI bus. I >> have two machines currently running FreeBSD. One is a P-200 with IDE and one >> is a PII-360 with both IDE and SCSI drives. I boot off the the SCSI bus on >> this machine. The IDE drives on both machines are UDMA-33. My SCSI drives >> are as follows (reported by FreeBSD on boot up): ID0: Fast SCSI2 HDD 10.00 >> MB Xfer (Synchronous), ID1: Ultra SCSI2 HDD 40.00 MB Xfer (Synchronous), >> ID2: SCSI2 CD-ROM 10.00 MB Xfer (Async), ID4: SCSI CD-Writer 3.300 MB Xfer >> (Async), ID5: SCSI2 Tape (Xfer not reported, Asynch). >> >> My question is this: why does it seem that the slower machine does disk >> access much faster? When I was installing these machines newfs wrote >> superblocks to the IDE drives much faster than to the SCSI drives, even >> though the Ultra SCSI drive (my FreeBSD drive) should theoretically be much >> faster... Many disk intensive operations seem to be faster on the IDE >> drives. Any ideas as to why this should be? > >The IDE disks are probably just simply faster. > >Don't confuse the transfer rate with the disk speed. No drives I know >of can currently hit 33 MB/s, so that's not the issue, and some recent >IDE drives are blindingly fast. If you want to check, run rawio >(/usr/ports/benchmarks/rawio) against the drives and see what speeds >it comes up with. > >Greg Just as a datapoint: http://www.storage.ibm.com/hardsoft/diskdrdl/prod/ds75gxp40gv.htm I want one. No, actually I want two. Tom Embt tom@embt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 17 8:10: 0 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from pan.salford.ac.uk (pan.salford.ac.uk [146.87.255.104]) by hub.freebsd.org (Postfix) with SMTP id 5C1E437B696 for ; Wed, 17 May 2000 08:09:42 -0700 (PDT) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 375 invoked by alias); 17 May 2000 15:09:40 -0000 Received: (qmail 369 invoked from network); 17 May 2000 15:09:40 -0000 Received: from unknown (HELO plato.salford.ac.uk) (146.87.255.76) by pan.salford.ac.uk with SMTP; 17 May 2000 15:09:40 -0000 Received: (qmail 33897 invoked by uid 141); 17 May 2000 15:09:40 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 17 May 2000 15:09:40 -0000 Date: Wed, 17 May 2000 16:09:40 +0100 (BST) From: Mark Powell To: freebsd-scsi@freebsd.org Subject: Anyone successfully made a RAID 10 array on a DPT? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We have a machine with a DPT SmartRAID IV, with two channels, each with 3x18GB disks. I wanted to stripe the 3 disks across one channel and then mirror the whole lot on to the other channel, thus giving me ~54GB of storage in a RAID 10 array. I could the partition this to root, swap and the rest for data. I hit the old problem where you have to fiddle with the OS type in the DPTMGR. I've done this in the past when I've made RAID 0 arrays, to enable FBSD to see the array as one logical drive rather than individual disks. This was something DPT let me on to. However, this time I had to set the OS to something that would allow striped RAID 1 arrays. Most OS settings complain "the driver for this OS doesn't support software striped RAID 1 arrays." Setting to Windows NT or Dos, would allow the setup of the three RAID 1 arrays that appeared, under DPTMGR at least, as one ~54GB logical unit. Booting into FBSD showed three seperate drives. More worryingly, at bootup the DPT BIOS displays garbage characters when it would normally display the drives NAME, i.e. without the array it's ------ DPT SCSI BIOS v003.EN (1998/03/31) ... Controller: PM334UW v07M.0 Port:B010h IRQ:11 Drive: 0 (0,00,0) ..... Drive: 1 (0,01,0) ..... Drive: 2 (0,02,0) ..... CDROM: (0,06,0) ..... Drive: 3 (1,03,0) ..... Drive: 4 (1,04,0) ..... Drive: 5 (1,05,0) ..... ------ (I'm getting the (x,yy,x) from memory) However, after the array is configured it shows: ------ DPT SCSI BIOS v003.EN (1998/03/31) ... Controller: PM334UW v07M.0 Port:B010h IRQ:11 CDROM: (0,06,0) TEAC CD-ROM CD-532S Controller: CD-ROM CD-532S v1.0.A Port:0000h IRQ:00 Drive: 0 (0,00,0) ------ This looks like the controller is getting itself into some, for want of a better word, crappy state. Anyone actually made a RAID10 array successfully? Any ideas if this is possible? Cheers. Mark Powell - UNIX System Administrator - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key M.S.Powell@salfrd.ac.uk (spell salford correctly to reply to me) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 17 9: 2: 1 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id 871CA37B5AC for ; Wed, 17 May 2000 09:01:54 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 12s5zW-0006ea-00; Wed, 17 May 2000 08:44:10 -0700 Date: Wed, 17 May 2000 08:44:08 -0700 (PDT) From: Tom To: Mark Powell Cc: freebsd-scsi@freebsd.org Subject: Re: Anyone successfully made a RAID 10 array on a DPT? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 17 May 2000, Mark Powell wrote: > settings complain "the driver for this OS doesn't support software striped > RAID 1 arrays." Setting to Windows NT or Dos, would allow the setup of the NEither does the FreeBSD driver. The PM334 can only do only do one layer of RAID in hardware. So if you want to do a RAID 5+0 config, the RAID0 part must be done in the software driver or in the OS. The DPT DOS/Windows driver can do RAID0 and RAID1 internally. On FreeBSD, you'll have to use vinum to do this. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 17 11:26:54 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from spike.porcupine.org (umbilical.porcupine.org [168.100.189.1]) by hub.freebsd.org (Postfix) with ESMTP id 23F4137BE01; Wed, 17 May 2000 11:26:32 -0700 (PDT) (envelope-from wietse@porcupine.org) Received: by spike.porcupine.org (Postfix, from userid 100) id 143E945659; Wed, 17 May 2000 14:26:20 -0400 (EDT) Subject: Need FreeBSD 4.0 removable SCSI support In-Reply-To: <20000517185649.A35355@gvr.gvr.org> from Guido van Rooij at "May 17, 0 06:56:49 pm" To: freebsd-mobile@freebsd.org Cc: freebsd-scsi@freebsd.org X-Time-Zone: USA EST, 6 hours behind central European time MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 4908 Message-Id: <20000517182620.143E945659@spike.porcupine.org> Date: Wed, 17 May 2000 14:26:20 -0400 (EDT) From: wietse@porcupine.org (Wietse Venema) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Note: I am not in the freebsd mailing lists. I am just a user. I am stuck on FreeBSD 2.2.8 because I need support for removable SCSI controllers, which is absent in FreeBSD 3.x. I had set my hopes on FreeBSD 4.0 but am running into a problem. Hardware is ThinkPad 600 and Adaptec SlimSCSI 1460B. Works like a champ with FreeBSD 2.2.8. Not so with FreeBSD 4.0. Complete dmesg output is attached at the end of this mail. I need to get away from 2.2.8 because its Linux emulation cannot handle Star Office. But I cannot give up removable SCSI support. The option I see now is to give up FreeBSD in favor of Linux. I have the following removable devices: - Removable ethernet. Works on IRQ 3 and IRQ 9. - Removable modem. Works on IRQ 3 and IRQ 9. - Removable SCSI controller. Recognized but unusable on IRQ 3 and 9. With FreeBSD 2.2.8, the removable SCSI controller and the external JAZ disk are recognized immediately. With FreeBSD 4.0, no SCSI device is recognized, and the machine locks up after "camcontrol rescan 0" or "camcontrol rescan scbus". # camcontrol rescan 0 ((with aic1 on irq 9) (probe0:aic1:0:0:0): ccb 0xc0addc00 - timed out, phase 0xa6, state 1 Here's another attempt: (probe0:aic1:0:0:0): ccb 0xc0aeb800 - timed out, phase 0xa6, state 1 and the machine locks up again. I have been a devoted FreeBSD user from the 386bsd days. I like running a real operating system. I really need to upgrade because 2.2.8's Linux emulation is not good enough for Star Office. I also need removable SCSI support. I know all this works with Linux. There's a box sitting on my desk, ready to blow away FreeBSD forever. That would be a shame. Wietse Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-RELEASE #0: Mon Mar 20 22:50:22 GMT 2000 root@monster.cdrom.com:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (298.42-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 134021120 (130880K bytes) avail memory = 126054400 (123100K bytes) Preloaded elf kernel "kernel" at 0xc03c0000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcic-pci0: mem 0x20301000-0x20301fff at device 2.0 on pci0 pcic-pci1: mem 0x20300000-0x20300fff at device 2.1 on pci0 pci0: at 3.0 irq 11 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfcf0-0xfcff at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 irq 11 chip1: port 0xefa0-0xefaf at device 7.3 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 pcic0: management irq 10 pccard0: on pcic0 pccard1: on pcic0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: cannot reserve I/O port range isa_compat: didn't get irq for lnc ad0: 6149MB [13328/15/63] at ata0-master using UDMA33 acd0: CDROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted pccard: card inserted, slot 0 pccard: card inserted, slot 1 ed1 at port 0x240-0x25f irq 3 slot 0 on pccard0 ed1: supplying EUI64: 00:04:ac:ff:fe:25:da:dd ed1: address 00:04:ac:25:da:dd, type NE2000 (16 bit) ed1: starting DAD for fe80:000a::0204:acff:fe25:dadd ed1: DAD complete for fe80:000a::0204:acff:fe25:dadd - no duplicates found sio4 at port 0x2f8-0x2ff irq 9 slot 1 on pccard1 sio4: type 16550A sio4: unloaded pccard: card removed, slot 1 pccard: card inserted, slot 1 aic1: at port 0x340-0x35f irq 9 slot 1 on pc card1 aic1: aic6360, dma, disconnection, parity check To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 17 22:11:56 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from socrates.nmia.com (socrates.nmia.com [198.59.166.170]) by hub.freebsd.org (Postfix) with SMTP id 24F6637B786 for ; Wed, 17 May 2000 22:11:52 -0700 (PDT) (envelope-from drobbins@gentoo.org) Received: from freebox.gentoo.org(really [207.66.80.126]) by socrates.nmia.com via sendmail with smtp id for ; Wed, 17 May 2000 23:11:50 -0600 (MDT) (Smail-3.2.0.106 1999-Mar-31 #3 built 1999-Apr-19) Received: by freebox.gentoo.org (Postfix, from userid 1001) id 47AD61C83; Wed, 17 May 2000 23:06:05 -0600 (MDT) Date: Wed, 17 May 2000 23:06:05 -0600 From: Daniel Robbins To: freebsd-scsi@freebsd.org Subject: VXA-1 tape drive not probed in 4.0-STABLE Message-ID: <20000517230604.A636@gentoo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Mailer: Mutt 1.0.1i Organization: Gentoo Technologies, Inc. Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm having a good amount of trouble getting my favorite OS to recognize my new Ecrix VXA-1 tape drive. I'm running FreeBSD 4.0-STABLE (updated 1 day ago). I'm fairly certain it's a FreeBSD issue rather than a hardware issue, since the tape drive, cabling, termination and SCSI ID and BIOS settings appear to be adequate for Windows NT 4.0. The basic problem I'm having is that my VXA-1 is simply not being probed. Period. I've tried "hard-wiring" the settings in my kernel config, and many other things. Here's additional info: Host Adapter: Buslogic BT-958 UW firmware 5.06J It has a narrow internal 50-pin connector, to which my Plextor CDR is attached. It also has a wide internal 68-pin connector, to which my Quantum Atlas II and my VXA-1 are connected. *MY ATLAS II IS FOUND*, the VXA-1 is not. They are on the same cable. Interesting, no? Here's more information. My VXA-1 is at SCSI ID 5. When I type: # camcontrol rescan 0:5:0 I see the VXA-1 light flash. So FreeBSD and the VXA-1 are able to talk, something is just breaking down somewhere. And here's even more information -- output from a camcontrol debug session I had a few minutes ago (note -- at this point, I have removed my Atlas II drive to simplify my SCSI setup. My VXA-1 is recognized by AutoSCSI BIOS on boot but *still* not by FreeBSD): Script started on Wed May 17 23:01:50 2000 # camcontrol debug -Ic 0:5:0=0D Debugging enabled for 0:5:0=0D # camcontrol s=08 =08rescan 0:5:0=0D Re-scan of 0:5:0 was successful=0D # camcontrol devlist=0D at scbus0 target 4 lun 0 (pass0,cd0)=0D # argh!=0D bash: argh!: command not found=0D # camcontrol -=08 =08debug -Ic 0=0D Debugging enabled for 0:-1:-1=0D # camcontrol rescan 0:4=08 =085=08 =08=08 =08=0D Re-scan of bus 0 was successful=0D # camcontrol devlist=0D at scbus0 target 4 lun 0 (pass0,cd0)=0D # camcontrol reset 0=0D Reset of bus 0 was successful=0D # cam c=08 =08=08 =08control rescan 0=0D Re-scan of bus 0 was successful=0D # camcontrol devlist=0D at scbus0 target 4 lun 0 (pass0,cd0)=0D # eek!=0D bash: eek!: command not found=0D # exit=0D Script done on Wed May 17 23:03:21 2000 Please help me get this wonderful tape drive working under FreeBSD. Anyone who helps me to get my VXA-1 working will receive an official favor IOU from me. Best Regards, --=20 Daniel Robbins President/CEO http://www.gentoo.org=20 Gentoo Technologies, Inc. =09 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 17 22:25: 0 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 7203337B85B for ; Wed, 17 May 2000 22:24:53 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA23932; Wed, 17 May 2000 23:24:36 -0600 (MDT) (envelope-from ken) Date: Wed, 17 May 2000 23:24:36 -0600 From: "Kenneth D. Merry" To: Daniel Robbins Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: VXA-1 tape drive not probed in 4.0-STABLE Message-ID: <20000517232436.A23897@panzer.kdm.org> References: <20000517230604.A636@gentoo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.2i In-Reply-To: <20000517230604.A636@gentoo.org>; from drobbins@gentoo.org on Wed, May 17, 2000 at 11:06:05PM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, May 17, 2000 at 23:06:05 -0600, Daniel Robbins wrote: > Hi, >=20 > I'm having a good amount of trouble getting my favorite OS to > recognize my new Ecrix VXA-1 tape drive. I'm running FreeBSD > 4.0-STABLE (updated 1 day ago). I'm fairly certain it's a FreeBSD > issue rather than a hardware issue, since the tape drive, cabling, > termination and SCSI ID and BIOS settings appear to be adequate for > Windows NT 4.0. The basic problem I'm having is that my VXA-1 is > simply not being probed. Period. I've tried "hard-wiring" the > settings in my kernel config, and many other things. Here's > additional info: >=20 > Host Adapter: Buslogic BT-958 UW firmware 5.06J > It has a narrow internal 50-pin connector, to which my Plextor CDR is > attached. > It also has a wide internal 68-pin connector, to which my Quantum > Atlas II and my VXA-1 are connected. *MY ATLAS II IS FOUND*, the > VXA-1 is not. They are on the same cable. Interesting, no? I would suggest re-checking your termination. Make sure you don't have termination enabled on your hard disk, and that you do have termination enabled on the Ecrix drive. Also, make sure low byte termination is not enabled on the adapter. > Here's more information. My VXA-1 is at SCSI ID 5. When I type: >=20 > # camcontrol rescan 0:5:0 >=20 > I see the VXA-1 light flash. So FreeBSD and the VXA-1 are able to > talk, something is just breaking down somewhere. And here's even more > information -- output from a camcontrol debug session I had a few > minutes ago (note -- at this point, I have removed my Atlas II drive > to simplify my SCSI setup. My VXA-1 is recognized by AutoSCSI BIOS on > boot but *still* not by FreeBSD): Was the drive recognized by the BusLogic BIOS when the Atlas II was on the chain? > Script started on Wed May 17 23:01:50 2000 > # camcontrol debug -Ic 0:5:0 > Debugging enabled for 0:5:0 > # camcontrol s=08 =08rescan 0:5:0 > Re-scan of 0:5:0 was successful > # camcontrol devlist > at scbus0 target 4 lun 0 (pass0,cd0) > # argh! > bash: argh!: command not found > # camcontrol -=08 =08debug -Ic 0 > Debugging enabled for 0:-1:-1 Turning on debugging may help somewhat, but all of the output goes to the console. (It isn't printed out by camcontrol.) Ken --=20 Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 18 4: 1:35 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id EB4AE37BD75; Thu, 18 May 2000 04:01:27 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p09-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.10]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id UAA21075; Thu, 18 May 2000 20:00:55 +0900 (JST) Message-ID: <3923CDBC.242F8237@newsguy.com> Date: Thu, 18 May 2000 20:02:20 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Wietse Venema Cc: freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Need FreeBSD 4.0 removable SCSI support References: <20000517182620.143E945659@spike.porcupine.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wietse Venema wrote: > > I am stuck on FreeBSD 2.2.8 because I need support for removable > SCSI controllers, which is absent in FreeBSD 3.x. I had set my > hopes on FreeBSD 4.0 but am running into a problem. > > Hardware is ThinkPad 600 and Adaptec SlimSCSI 1460B. Works like > a champ with FreeBSD 2.2.8. Not so with FreeBSD 4.0. Complete > dmesg output is attached at the end of this mail. I have been using that very same SlimSCSI without a problem. I have one suggestion: > pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 > pcic0: management irq 10 IRQ for pcic is only necessary when you insert and remove cards, and, then, only if you do not want to run the detachment/attachment commands by hand. You might, then, change the pcic0 to polling by adding the following line to your /boot/loader.conf (create one if needed): machdep.pccard.pcic_irq="0" This will free irq 10 for other use. You then change pccard.conf accordingly, to give that irq preference. > sio4 at port 0x2f8-0x2ff irq 9 slot 1 on pccard1 ^^^^^ > sio4: type 16550A > sio4: unloaded > pccard: card removed, slot 1 > pccard: card inserted, slot 1 > aic1: at port 0x340-0x35f irq 9 slot 1 on pc ^^^^^ > card1 > aic1: aic6360, dma, disconnection, parity check These are not sharable. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@another.bsdconspiracy.org "Sentience hurts." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 18 4:20:58 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from ntua.gr (achilles.noc.ntua.gr [147.102.222.210]) by hub.freebsd.org (Postfix) with ESMTP id 695E437B5CD; Thu, 18 May 2000 04:20:41 -0700 (PDT) (envelope-from past@netmode.ece.ntua.gr) Received: from netmode.ece.ntua.gr (dolly.netmode.ece.ntua.gr [147.102.13.10]) by ntua.gr (8.9.3/8.9.3) with ESMTP id OAA27399; Thu, 18 May 2000 14:20:23 +0300 (EET DST) Received: by netmode.ece.ntua.gr (Postfix, from userid 410) id 5977C85C3; Thu, 18 May 2000 14:10:13 +0300 (EET DST) Date: Thu, 18 May 2000 14:10:12 +0300 From: Panagiotis Astithas To: "Daniel C. Sobral" Cc: Wietse Venema , freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Need FreeBSD 4.0 removable SCSI support Message-ID: <20000518141012.B12479@netmode.ece.ntua.gr> Reply-To: past@netmode.ntua.gr Mail-Followup-To: "Daniel C. Sobral" , Wietse Venema , freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG References: <20000517182620.143E945659@spike.porcupine.org> <3923CDBC.242F8237@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3923CDBC.242F8237@newsguy.com>; from dcs@newsguy.com on Thu, May 18, 2000 at 08:02:20PM +0900 X-Organizational-Unit: Network Management and Optimal Design Laboratory X-Organization: National Technical University of Athens, GREECE X-Work-Phone: +30-1-772-1-450 X-Work-FAX: +30-1-772-1-452 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, May 18, 2000 at 08:02:20PM +0900, Daniel C. Sobral wrote: > IRQ for pcic is only necessary when you insert and remove cards, and, > then, only if you do not want to run the detachment/attachment commands > by hand. You might, then, change the pcic0 to polling by adding the > following line to your /boot/loader.conf (create one if needed): > > machdep.pccard.pcic_irq="0" > > This will free irq 10 for other use. You then change pccard.conf > accordingly, to give that irq preference. I believe you get the same effect by specifying irq 0 in the kernel config for the pcic device. -past To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 18 8:33:38 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from spike.porcupine.org (umbilical.porcupine.org [168.100.189.1]) by hub.freebsd.org (Postfix) with ESMTP id 3FA2237B6E3; Thu, 18 May 2000 08:33:26 -0700 (PDT) (envelope-from wietse@porcupine.org) Received: by spike.porcupine.org (Postfix, from userid 100) id C01FC4563D; Thu, 18 May 2000 11:33:23 -0400 (EDT) Subject: Re: Need FreeBSD 4.0 removable SCSI support In-Reply-To: <20000518170300.A6979@lpthe.jussieu.fr> from Michel Talon at "May 18, 0 05:03:00 pm" To: freebsd-mobile@freebsd.org Cc: freebsd-scsi@freebsd.org X-Time-Zone: USA EST, 6 hours behind central European time MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 4280 Message-Id: <20000518153323.C01FC4563D@spike.porcupine.org> Date: Thu, 18 May 2000 11:33:23 -0400 (EDT) From: wietse@porcupine.org (Wietse Venema) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Summary: I'm stuck at FreeBSD 2.2.8 because removable SCSI devices are not supported in FreeBSD 3.4. Meanwhile, I need up-to-date Linux emulation for Star Office, which does not run on FreeBSD 2.2.8. At the suggestion of several respondents I installed FreeBSD 4.0-STABLE on my Thinkpad 600. I downloaded 4.0-20000518-STABLE and installed the bin/* files including pre-compiled kernel. I use IRQ 3+9 for pccard devices which works fine with the removable modem and ethernet cards. See dmesg messages below. When I insert the Adaptec 1460B SCSI controller, the machine locks up after "camcontrol rescan 0", exactly like it did with FreeBSD 4.0-RELEASE yesterday. On the other hand, SUSE Linux recognizes the controller and the attached JAZ disk even before it has installed Linux. Star Office runs on Linux, and I can use VMware to run Crap if I need to. I can no longer afford to be stuck on FreeBSD 2.2.8. My best bet is to migrate to 3.4 for just one month without SCSI, and then kiss FreeBSD goodbye forever. Too bad, I liked running a real operating system. Wietse Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-20000518-STABLE #0: Thu May 18 11:32:01 GMT 2000 root@usw3.freebsd.org:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (298.42-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 134021120 (130880K bytes) avail memory = 126484480 (123520K bytes) Preloaded elf kernel "kernel" at 0xc03c9000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcic-pci0: mem 0x20301000-0x20301fff at device 2.0 on pci0 pcic-pci1: mem 0x20300000-0x20300fff at device 2.1 on pci0 pci0: at 3.0 irq 11 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfcf0-0xfcff at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 irq 11 chip1: port 0xefa0-0xefaf at device 7.3 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 pcic0: management irq 10 pccard0: on pcic0 pccard1: on pcic0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: cannot reserve I/O port range isa_compat: didn't get irq for lnc ad0: 6149MB [13328/15/63] at ata0-master using UDMA33 acd0: CDROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted pccard: card inserted, slot 0 pccard: card inserted, slot 1 aic1: at port 0x340-0x35f irq 3 slot 0 on pccard0 aic1: aic6360, dma, disconnection, parity check ed1 at port 0x240-0x25f iomem 0xd4000-0xd7fff irq 9 slot 1 on pccard1 ed1: supplying EUI64: 00:04:ac:ff:fe:25:da:dd ed1: address 00:04:ac:25:da:dd, type NE2000 (16 bit) ed1: starting DAD for fe80:000a::0204:acff:fe25:dadd ed1: DAD complete for fe80:000a::0204:acff:fe25:dadd - no duplicates found (probe0:aic1:0:0:0): ccb 0xc0b3c000 - timed out, phase 0xa6, state 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 18 10:44:21 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from kris.huntsvilleal.com (kris.huntsvilleal.com [63.147.8.46]) by hub.freebsd.org (Postfix) with ESMTP id 5B74837B8A1; Thu, 18 May 2000 10:44:14 -0700 (PDT) (envelope-from kris@hiwaay.net) Received: from localhost (localhost [127.0.0.1]) by kris.huntsvilleal.com (8.9.3/8.9.3) with ESMTP id LAA40305; Thu, 18 May 2000 11:46:35 -0500 (CDT) (envelope-from kris@hiwaay.net) Date: Thu, 18 May 2000 11:46:35 -0500 (CDT) From: Kris Kirby To: Wietse Venema Cc: freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Need FreeBSD 4.0 removable SCSI support In-Reply-To: <20000518153323.C01FC4563D@spike.porcupine.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > When I insert the Adaptec 1460B SCSI controller, the machine locks > up after "camcontrol rescan 0", exactly like it did with FreeBSD > 4.0-RELEASE yesterday. Perhaps then the solution would be to keep the SCSI card in the slot at all times, and "camcontrol rescan 0" whenever you connect and disconnect the Jaz drive. I've got a machine with a 1540B in it which I never turn off, but instead I disconnect drives and reconnect them as necessary. Nifty SCSI test box, slow as molasses... ----- Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. | ------------------------------------------------------- "Fate, it seems, is not without a sense of irony." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 18 10:51:14 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from spike.porcupine.org (umbilical.porcupine.org [168.100.189.1]) by hub.freebsd.org (Postfix) with ESMTP id E02F337B8A1; Thu, 18 May 2000 10:51:08 -0700 (PDT) (envelope-from wietse@porcupine.org) Received: by spike.porcupine.org (Postfix, from userid 100) id 11AFE4563D; Thu, 18 May 2000 13:51:06 -0400 (EDT) Subject: Re: Need FreeBSD 4.0 removable SCSI support In-Reply-To: from Kris Kirby at "May 18, 0 11:46:35 am" To: kris@hiwaay.net (Kris Kirby) Cc: wietse@porcupine.org, freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG X-Time-Zone: USA EST, 6 hours behind central European time MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 848 Message-Id: <20000518175106.11AFE4563D@spike.porcupine.org> Date: Thu, 18 May 2000 13:51:06 -0400 (EDT) From: wietse@porcupine.org (Wietse Venema) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kris Kirby: > > When I insert the Adaptec 1460B SCSI controller, the machine locks > > up after "camcontrol rescan 0", exactly like it did with FreeBSD > > 4.0-RELEASE yesterday. > > Perhaps then the solution would be to keep the SCSI card in the slot > at all times, and "camcontrol rescan 0" whenever you connect and > disconnect the Jaz drive. It's not like I scream to the mailing list upon the first problem. I have rebooted the machine dozens of times with the card already in the machine and it makes no difference. Please do not add to the noise level in my mailbox. > I've got a machine with a 1540B in it which I never turn off, but instead > I disconnect drives and reconnect them as necessary. Nifty SCSI test box, > slow as molasses... The Adaptect 1460 is a pig as well, but it's a whole lot better than having nothing. Wietse To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 18 10:55:21 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from moek.pir.net (moek.pir.net [209.192.237.190]) by hub.freebsd.org (Postfix) with ESMTP id ABEDE37BB23; Thu, 18 May 2000 10:54:11 -0700 (PDT) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 12sUUs-0002zN-00 ; Thu, 18 May 2000 13:54:10 -0400 Date: Thu, 18 May 2000 13:54:09 -0400 From: Peter Radcliffe To: freebsd-mobile@freebsd.org Cc: wietse@porcupine.org, freebsd-scsi@freebsd.org Subject: Re: Need FreeBSD 4.0 removable SCSI support Message-ID: <20000518135409.B10677@pir.net> Mail-Followup-To: freebsd-mobile@freebsd.org, wietse@porcupine.org, freebsd-scsi@freebsd.org References: <20000518170300.A6979@lpthe.jussieu.fr> <20000518153323.C01FC4563D@spike.porcupine.org> <20000518131010.D8913@pir.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000518131010.D8913@pir.net>; from pir@pir.net on Thu, May 18, 2000 at 01:10:10PM -0400 X-fish: < Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Radcliffe probably said: > You do know that the latest 3.4-PAO supports the adaptec slimscsi ? I > was using that for some time before I went up to 4.0-S. I also just dug out my slimscsi 1460B and tried it on my 4.0-S Sony 5050TR. Seems to work perfectly. I cvsuped last on May 13th, which is before the time you're having trouble with. Looks like a local problem. Sorry I can't offer more advice as to exactly _what_ ... P. --- kernel ---- device aic device scbus # SCSI bus (required) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) device pcic0 at isa? --------------- --- pccard.conf --- # Adaptec SlimSCSI (also included with Sony CD-ROM players) card "Adaptec, Inc." "APA-1460 SCSI Host Adapter" config 0x9 "aic0" ? insert logger -t pccard:$device -s Adaptec Slim SCSI inserted remove logger -t pccard:$device -s Adaptec Slim SCSI removed ------------------- --- rc.conf --- pccard_enable="YES" pccardd_flags="-z" pccard_conf="/etc/pccard.conf" pccard_mem="0xd8000" --------------- ------------------------------------------------------------------------ pccard: card inserted, slot 0 May 18 13:18:11 disapp pccardd[121]: Card "Adaptec, Inc."("APA-1460 SCSI Host Adapter") matched "Adaptec, Inc." ("APA-1460 SCSI Host Adapter") aic0: at port 0x340-0x35f irq 7 slot 0 on pccard0 aic0: aic6360, dma, disconnection, parity check pir@disapp# camcontrol rescan 0 Re-scan of bus 0 was successful da0 at aic0 bus 0 target 3 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 5.000MB/s transfers (5.000MHz, offset 8), Tagged Queueing Enabled da0: 1006MB (2061108 512 byte sectors: 64H 32S/T 1006C) /dev/da0s1e 998367 700337 218161 76% /mnt (da0:aic0:0:3:0): lost device (da0:aic0:0:3:0): removing device entry pccard: card removed, slot 0 ------------------------------------------------------------------------ -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 18 11:17:36 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from spike.porcupine.org (umbilical.porcupine.org [168.100.189.1]) by hub.freebsd.org (Postfix) with ESMTP id E628C37B858; Thu, 18 May 2000 11:17:28 -0700 (PDT) (envelope-from wietse@porcupine.org) Received: by spike.porcupine.org (Postfix, from userid 100) id 3D1084563D; Thu, 18 May 2000 14:17:27 -0400 (EDT) Subject: Re: Need FreeBSD 4.0 removable SCSI support In-Reply-To: <20000518135409.B10677@pir.net> from Peter Radcliffe at "May 18, 0 01:54:09 pm" To: pir@pir.net (Peter Radcliffe) Cc: freebsd-mobile@freebsd.org, wietse@porcupine.org, freebsd-scsi@freebsd.org X-Time-Zone: USA EST, 6 hours behind central European time MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2789 Message-Id: <20000518181727.3D1084563D@spike.porcupine.org> Date: Thu, 18 May 2000 14:17:27 -0400 (EDT) From: wietse@porcupine.org (Wietse Venema) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Radcliffe: > Peter Radcliffe probably said: > > You do know that the latest 3.4-PAO supports the adaptec slimscsi ? I > > was using that for some time before I went up to 4.0-S. > > I also just dug out my slimscsi 1460B and tried it on my 4.0-S Sony > 5050TR. Seems to work perfectly. I cvsuped last on May 13th, which is > before the time you're having trouble with. > > Looks like a local problem. > Sorry I can't offer more advice as to exactly _what_ ... With my Thinkpad 600 machine, the SlimSCSI 1460B+Jaz 2GB works with FreeBSD 2.2.8 and with SUSE Linux 6.4. So it would appear that the hardware is not too broken. What is 3.4-PAO? Is it a patch to the 3.4-RELEASE that I already have on CD, or does this involve yet another download and install? What hardware were you using? Perhaps the Thinkpad 600 is a bit finnicky about things. Wietse > P. > > --- kernel ---- > device aic > device scbus # SCSI bus (required) > device da # Direct Access (disks) > device sa # Sequential Access (tape etc) > device cd # CD > device pass # Passthrough device (direct SCSI access) > > device pcic0 at isa? > --------------- > > --- pccard.conf --- > # Adaptec SlimSCSI (also included with Sony CD-ROM players) > card "Adaptec, Inc." "APA-1460 SCSI Host Adapter" > config 0x9 "aic0" ? > insert logger -t pccard:$device -s Adaptec Slim SCSI inserted > remove logger -t pccard:$device -s Adaptec Slim SCSI removed > ------------------- > > --- rc.conf --- > pccard_enable="YES" > pccardd_flags="-z" > pccard_conf="/etc/pccard.conf" > pccard_mem="0xd8000" > --------------- > > ------------------------------------------------------------------------ > pccard: card inserted, slot 0 > May 18 13:18:11 disapp pccardd[121]: Card "Adaptec, Inc."("APA-1460 SCSI > Host Adapter") matched "Adaptec, Inc." ("APA-1460 SCSI Host Adapter") > aic0: at port 0x340-0x35f irq 7 slot > 0 on pccard0 > aic0: aic6360, dma, disconnection, parity check > > pir@disapp# camcontrol rescan 0 > Re-scan of bus 0 was successful > > da0 at aic0 bus 0 target 3 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 5.000MB/s transfers (5.000MHz, offset 8), Tagged Queueing Enabled > da0: 1006MB (2061108 512 byte sectors: 64H 32S/T 1006C) > > /dev/da0s1e 998367 700337 218161 76% /mnt > > (da0:aic0:0:3:0): lost device > (da0:aic0:0:3:0): removing device entry > pccard: card removed, slot 0 > ------------------------------------------------------------------------ > > -- > pir pir@pir.net pir@net.tufts.edu > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 18 11:23:35 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from ptldpop1.ptld.uswest.net (ptldpop1.ptld.uswest.net [198.36.160.1]) by hub.freebsd.org (Postfix) with SMTP id 8A3E537B967 for ; Thu, 18 May 2000 11:23:31 -0700 (PDT) (envelope-from bwoods2@uswest.net) Received: (qmail 20797 invoked by alias); 18 May 2000 18:23:25 -0000 Delivered-To: fixup-freebsd-scsi@FreeBSD.ORG@fixme Received: (qmail 20772 invoked by uid 0); 18 May 2000 18:23:24 -0000 Received: from alpha.uswest.net (63.227.213.92) by ptldpop1.ptld.uswest.net with SMTP; 18 May 2000 18:23:24 -0000 Date: Thu, 18 May 2000 11:25:08 -0700 (PDT) From: William Woods Reply-To: bwoods2@uswest.net To: Wietse Venema Cc: Kris Kirby , freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Need FreeBSD 4.0 removable SCSI support In-Reply-To: <20000518175106.11AFE4563D@spike.porcupine.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > The Adaptect 1460 is a pig as well, but it's a whole lot better than > having nothing. > > Wietse I use this card in mine and like it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 18 11:40:18 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from moek.pir.net (moek.pir.net [209.192.237.190]) by hub.freebsd.org (Postfix) with ESMTP id 9B6AC37B5C6; Thu, 18 May 2000 11:40:05 -0700 (PDT) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 12sVDD-0003HW-00 ; Thu, 18 May 2000 14:39:59 -0400 Date: Thu, 18 May 2000 14:39:59 -0400 From: Peter Radcliffe To: Wietse Venema Cc: freebsd-mobile@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: Need FreeBSD 4.0 removable SCSI support Message-ID: <20000518143959.D10677@pir.net> Mail-Followup-To: Wietse Venema , freebsd-mobile@freebsd.org, freebsd-scsi@freebsd.org References: <20000518135409.B10677@pir.net> <20000518181727.3D1084563D@spike.porcupine.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000518181727.3D1084563D@spike.porcupine.org>; from wietse@porcupine.org on Thu, May 18, 2000 at 02:17:27PM -0400 X-fish: < Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wietse Venema probably said: > With my Thinkpad 600 machine, the SlimSCSI 1460B+Jaz 2GB works with > FreeBSD 2.2.8 and with SUSE Linux 6.4. So it would appear that the > hardware is not too broken. The only thing that occurs to me is 4.0 uses a configuration that conflicts with something else in the machine, which seems odd given that another Thinkpad 600 owner has said it is ok. Did they send you their configuration details ? > What is 3.4-PAO? Is it a patch to the 3.4-RELEASE that I already > have on CD, or does this involve yet another download and install? http://www.jp.FreeBSD.org/PAO/ New kernel ans a few userland utilities for 3.4. If you can install 3.4 then you can just do a binary install of PAO over the top. > What hardware were you using? Perhaps the Thinkpad 600 is a bit > finnicky about things. The laptop is a Sony 505TR, the disk a random Seagate 1Gb disk I had kicking around in an external case. Do you have any other scsi devices to test with ? P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 18 12: 2:59 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from spike.porcupine.org (umbilical.porcupine.org [168.100.189.1]) by hub.freebsd.org (Postfix) with ESMTP id CB92C37B721; Thu, 18 May 2000 12:02:43 -0700 (PDT) (envelope-from wietse@porcupine.org) Received: by spike.porcupine.org (Postfix, from userid 100) id 88D9C4563D; Thu, 18 May 2000 15:02:40 -0400 (EDT) Subject: Re: Need FreeBSD 4.0 removable SCSI support In-Reply-To: <20000518143959.D10677@pir.net> from Peter Radcliffe at "May 18, 0 02:39:59 pm" To: pir@pir.net (Peter Radcliffe) Cc: wietse@porcupine.org, freebsd-mobile@freebsd.org, freebsd-scsi@freebsd.org X-Time-Zone: USA EST, 6 hours behind central European time MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1537 Message-Id: <20000518190240.88D9C4563D@spike.porcupine.org> Date: Thu, 18 May 2000 15:02:40 -0400 (EDT) From: wietse@porcupine.org (Wietse Venema) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Radcliffe: > Wietse Venema probably said: > > With my Thinkpad 600 machine, the SlimSCSI 1460B+Jaz 2GB works with > > FreeBSD 2.2.8 and with SUSE Linux 6.4. So it would appear that the > > hardware is not too broken. > > The only thing that occurs to me is 4.0 uses a configuration that > conflicts with something else in the machine, which seems odd given > that another Thinkpad 600 owner has said it is ok. > > Did they send you their configuration details ? Who was that TP600 owner? We might be able to make a very close comparison between our systems. I have not seen that email as I am not on the freebsd list (I receive too much mail). > > What is 3.4-PAO? Is it a patch to the 3.4-RELEASE that I already > > have on CD, or does this involve yet another download and install? > > http://www.jp.FreeBSD.org/PAO/ > > New kernel ans a few userland utilities for 3.4. If you can install > 3.4 then you can just do a binary install of PAO over the top. That sounds interesting. There still is a little free space on the spare disk that I use for testing. Of course that web server is dead right now. > > What hardware were you using? Perhaps the Thinkpad 600 is a bit > > finnicky about things. > > The laptop is a Sony 505TR, the disk a random Seagate 1Gb disk I > had kicking around in an external case. > > Do you have any other scsi devices to test with ? All I want is to use this sucker with the JAZ drive. Carrying a couple external disk drives in my suitcase is not practical. Wietse To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 18 13: 2: 8 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from moek.pir.net (moek.pir.net [209.192.237.190]) by hub.freebsd.org (Postfix) with ESMTP id 62EDE37B6CE; Thu, 18 May 2000 13:01:33 -0700 (PDT) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 12sWU2-0003mZ-00 ; Thu, 18 May 2000 16:01:26 -0400 Date: Thu, 18 May 2000 16:01:26 -0400 From: Peter Radcliffe To: Wietse Venema , Martin Dieringer Cc: freebsd-mobile@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: Need FreeBSD 4.0 removable SCSI support Message-ID: <20000518160126.F10677@pir.net> Mail-Followup-To: Wietse Venema , Martin Dieringer , freebsd-mobile@freebsd.org, freebsd-scsi@freebsd.org References: <20000518143959.D10677@pir.net> <20000518190240.88D9C4563D@spike.porcupine.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000518190240.88D9C4563D@spike.porcupine.org>; from wietse@porcupine.org on Thu, May 18, 2000 at 03:02:40PM -0400 X-fish: < Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wietse Venema probably said: > > The only thing that occurs to me is 4.0 uses a configuration that > > conflicts with something else in the machine, which seems odd given > > that another Thinkpad 600 owner has said it is ok. > > > > Did they send you their configuration details ? > > Who was that TP600 owner? We might be able to make a very close > comparison between our systems. I have not seen that email as Martin Dieringer > > http://www.jp.FreeBSD.org/PAO/ > That sounds interesting. There still is a little free space > on the spare disk that I use for testing. Of course that web > server is dead right now. It's quite a small install. pccardd, pccardc, apm (a couple of other binaries) and the kernel, plus the kernel source and include file patches. I was using PAO exclusively on my laptops until 4.0-S. > All I want is to use this sucker with the JAZ drive. Carrying > a couple external disk drives in my suitcase is not practical. Just wondering if you had another test device ... Martin Dieringer probably said: > I have no problem with 4.0-STABLE and the 1460 on a thinkpad 600. > > card "Adaptec, Inc." "APA-1460 SCSI Host Adapter" > config 0x9 "aic0" ? > insert logger -t pccard:$device -s Adaptec Slim SCSI inserted > remove logger -t pccard:$device -s Adaptec Slim SCSI removed > > > my dmesg looks like yours. > May 8 22:19:27 ThinkPad /kernel: aic1: controller> at port 0x340-0x35f irq 3 slot 0 on pccard0 > May 8 22:19:27 ThinkPad /kernel: aic1: aic6360, dma, disconnection, > parity check > > and an hp scanjet 2cx: after camcontrol rescan 0 > > May 8 22:20:22 ThinkPad /kernel: pt0 at aic1 bus 0 target 5 lun 0 > May 8 22:20:22 ThinkPad /kernel: pt0: Fixed Processor > SCSI-2 d > evice > May 8 22:20:22 ThinkPad /kernel: pt0: 3.300MB/s transfers > > > are you shure you have the necessary options and devices in the kernel? > > m. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 18 13:24: 4 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id A36B437B914; Thu, 18 May 2000 13:23:56 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:KUWmOqZik0F4SCCNPyzsVH2nyBELTdvC2MLAyYTgxyNc8Q6ikh2xtQHbPfip3sA/@localhost [::1]) by peace.mahoroba.org (8.10.1/3.7W-peace) with ESMTP id e4IKIqF08014; Fri, 19 May 2000 05:18:52 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Fri, 19 May 2000 05:18:52 +0900 (JST) Message-Id: <200005182018.e4IKIqF08014@peace.mahoroba.org> To: wietse@porcupine.org Cc: pir@pir.net, freebsd-mobile@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: Need FreeBSD 4.0 removable SCSI support In-Reply-To: <20000518190240.88D9C4563D@spike.porcupine.org> References: <20000518143959.D10677@pir.net> <20000518190240.88D9C4563D@spike.porcupine.org> X-Mailer: xcite1.20> Mew version 1.94.2 on Emacs 20.6 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Hajimu UMEMOTO (=?ISO-2022-JP?B?GyRCR19LXBsoQiA=?= =?ISO-2022-JP?B?GyRCSCUbKEI=?=) X-Dispatcher: imput version 20000228(IM140) Lines: 20 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> On Thu, 18 May 2000 15:02:40 -0400 (EDT) >>>>> Wietse Venema said: > http://www.jp.FreeBSD.org/PAO/ > > New kernel ans a few userland utilities for 3.4. If you can install > 3.4 then you can just do a binary install of PAO over the top. wietse> That sounds interesting. There still is a little free space wietse> on the spare disk that I use for testing. Of course that web wietse> server is dead right now. Sorry. I sent notify to maintainer of www.jp.freebsd.org. Please refer to http://updraft2.jp.freebsd.org/PAO/ for a while. It is backup server of www.jp. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 18 14:40:38 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from axp5.physik.fu-berlin.de (axp5.physik.fu-berlin.de [160.45.34.3]) by hub.freebsd.org (Postfix) with ESMTP id A61A837B923; Thu, 18 May 2000 14:40:33 -0700 (PDT) (envelope-from dieringe@sirius.physik.fu-berlin.de) Received: from sirius.physik.fu-berlin.de (sirius.physik.fu-berlin.de [160.45.34.162]) by axp5.physik.fu-berlin.de (8.9.1a/8.9.1) with ESMTP id XAA05330; Thu, 18 May 2000 23:40:31 +0200 (MET DST) Received: from localhost (dieringe@localhost) by sirius.physik.fu-berlin.de (8.9.1a/8.9.1) with ESMTP id XAA22108; Thu, 18 May 2000 23:40:30 +0200 (MET DST) Date: Thu, 18 May 2000 23:40:30 +0200 (MET DST) From: Martin Dieringer To: Peter Radcliffe Cc: Wietse Venema , freebsd-mobile@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: Need FreeBSD 4.0 removable SCSI support In-Reply-To: <20000518160126.F10677@pir.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We exchanged 3 or 4 emails and I sent him my kernel config, rc.conf and dmesg output. so he should probably be able to try it out. I don't know anything about jaz drives, so I can't help any more here. martin On Thu, 18 May 2000, Peter Radcliffe wrote: > Wietse Venema probably said: > > > The only thing that occurs to me is 4.0 uses a configuration that > > > conflicts with something else in the machine, which seems odd given > > > that another Thinkpad 600 owner has said it is ok. > > > > > > Did they send you their configuration details ? > > > > Who was that TP600 owner? We might be able to make a very close > > comparison between our systems. I have not seen that email as > > Martin Dieringer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 18 14:43:23 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from spike.porcupine.org (umbilical.porcupine.org [168.100.189.1]) by hub.freebsd.org (Postfix) with ESMTP id 0655337B923; Thu, 18 May 2000 14:43:18 -0700 (PDT) (envelope-from wietse@porcupine.org) Received: by spike.porcupine.org (Postfix, from userid 100) id 0DAC34563D; Thu, 18 May 2000 17:43:11 -0400 (EDT) Subject: Re: Need FreeBSD 4.0 removable SCSI support In-Reply-To: from Martin Dieringer at "May 18, 0 11:40:30 pm" To: dieringe@physik.fu-berlin.de (Martin Dieringer) Cc: pir@pir.net, wietse@porcupine.org, freebsd-mobile@freebsd.org, freebsd-scsi@freebsd.org X-Time-Zone: USA EST, 6 hours behind central European time MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 363 Message-Id: <20000518214311.0DAC34563D@spike.porcupine.org> Date: Thu, 18 May 2000 17:43:11 -0400 (EDT) From: wietse@porcupine.org (Wietse Venema) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Martin Dieringer: > We exchanged 3 or 4 emails and I sent him my kernel config, rc.conf > and dmesg output. so he should probably be able to try it out. > I don't know anything about jaz drives, so I can't help any more here. Your help is appreciated. I had hoped that upgrade to 4.0-STABLE would make the difference. I will try your config files next. Wietse To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 18 16:16:34 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from spike.porcupine.org (umbilical.porcupine.org [168.100.189.1]) by hub.freebsd.org (Postfix) with ESMTP id B836E37BCB7; Thu, 18 May 2000 16:16:13 -0700 (PDT) (envelope-from wietse@porcupine.org) Received: by spike.porcupine.org (Postfix, from userid 100) id 5AE974563D; Thu, 18 May 2000 19:16:06 -0400 (EDT) Subject: Re: Need FreeBSD 4.0 removable SCSI support In-Reply-To: from Martin Dieringer at "May 18, 0 11:40:30 pm" To: dieringe@physik.fu-berlin.de (Martin Dieringer) Cc: pir@pir.net, wietse@porcupine.org, freebsd-mobile@freebsd.org, freebsd-scsi@freebsd.org X-Time-Zone: USA EST, 6 hours behind central European time MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 7449 Message-Id: <20000518231606.5AE974563D@spike.porcupine.org> Date: Thu, 18 May 2000 19:16:06 -0400 (EDT) From: wietse@porcupine.org (Wietse Venema) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Martin Dieringer: > We exchanged 3 or 4 emails and I sent him my kernel config, rc.conf > and dmesg output. so he should probably be able to try it out. Summary: Generic FreeBSD 4.0-RELEASE + Thinkpad 600 + SlimSCSI 1460B + Jaz 2GB locks up the machine. Summary: I built a machine according to Martin Dieringer's specs and it still locks up. For details, see below. All this works OK with FreeBSD 2.2.8. And SUSE Linux can talk to the Jaz drive even before Linux is installed. I conclude that FreeBSD 4.0 cannot work with my hardware. Perhaps it gets upset by garbage from the Jaz disk. I do not care anymore. I could try if FreeBSD 3.4+PAO is up to the task, but then I would again be stuck one major release behind the times. That is not a good long-term solution. It looks like Linux will have to be my long-term solution. It was nice knowing you people. Wietse - I upgraded from FreeBSD 4.0-RELEASE to FreeBSD 4.0-20000518 STABLE. - I built Martin Dieringer's kernel configuration, with two changes: no MAXMEM (I removed all but the last 64MB memory) and no soft updates (undefined symbols). - I installed Martin Dieringer's rc.conf file, unmodified. And here are the results: - The SlimSCSI 1460B card is recognized. - After "camcontrol rescan 0" the machine locks up. Below is dmesg output from my machine, and diffs against Martin Dieringer's dmesg output. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-20000518-STABLE #0: Thu May 18 22:13:38 EDT 2000 wietse@bristle.watson.ibm.com:/usr/src/sys/compile/THINKPAD Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (298.42-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 66912256 (65344K bytes) avail memory = 61505536 (60064K bytes) Preloaded elf kernel "kernel" at 0xc0387000. ccd0-3: Concatenated disk drivers Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: on motherboard pci0: on pcib0 pcic-pci0: mem 0x20301000-0x20301fff at device 2.0 on pci0 pcic-pci1: mem 0x20300000-0x20300fff at device 2.1 on pci0 pci0: at 3.0 irq 11 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfcf0-0xfcff at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x8400-0x841f irq 11 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered chip1: port 0xefa0-0xefaf at device 7.3 on pci0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 pcic0: at port 0x3e0-0x3e1 on isa0 pcic0: Polling mode pccard0: on pcic0 pccard1: on pcic0 ppc0: cannot reserve I/O port range unknown: can't assign resources unknown0: at port 0-0xf,0x80-0x8f,0xc0-0xdf drq 4 on isa0 unknown1: at port 0x40-0x43 irq 0 on isa0 unknown2: at port 0x70-0x73 irq 8 on isa0 unknown3: at port 0x61 on isa0 unknown: can't assign resources unknown: can't assign resources unknown4: at port 0xf0-0xff irq 13 on isa0 unknown: can't assign resources unknown5: at port 0xcf8-0xcff on isa0 unknown6: at port 0x22,0x2e-0x2f,0x92,0xb2-0xb3,0x4d0-0x4d1,0x15e0-0x15ef,0xef00-0xefaf iomem 0-0x9ffff,0xf0000-0xfffff,0x100000-0x3ffffff,0xffff0000-0xffffffff on isa0 unknown: can't assign resources unknown: can't assign resources pcm0: at port 0x530-0x537,0x388-0x38b,0x220-0x233 irq 5 drq 1,0 on isa0 unknown7: at port 0x538-0x53f on isa0 unknown8: at port 0x10 on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown9: at iomem 0xca000-0xcbfff on isa0 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging lim ited to 100 packets/entry by default IP Filter: initialized. Default = pass all, Logging = enabled IP Filter: v3.3.8 ad0: 6149MB [13328/15/63] at ata0-master using UDMA33 acd0: CDROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s1a 4,5c4,5 < FreeBSD 4.0-STABLE #0: Sun May 14 16:37:24 CEST 2000 < root@pc.nowhere.local:/usr/src/sys/compile/THINKPAD --- > FreeBSD 4.0-20000518-STABLE #0: Thu May 18 22:13:38 EDT 2000 > wietse@bristle.watson.ibm.com:/usr/src/sys/compile/THINKPAD 7,8c7,8 < CPU: Pentium II/Pentium II Xeon/Celeron (232.11-MHz 686-class CPU) < Origin = "GenuineIntel" Id = 0x650 Stepping = 0 --- > CPU: Pentium II/Pentium II Xeon/Celeron (298.42-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x652 Stepping = 2 10,12c10,12 < real memory = 100073472 (97728K bytes) < avail memory = 93618176 (91424K bytes) < Preloaded elf kernel "kernel" at 0xc0390000. --- > real memory = 66912256 (65344K bytes) > avail memory = 61505536 (60064K bytes) > Preloaded elf kernel "kernel" at 0xc0387000. 52,57c52 < ppc0: at port 0x378-0x37f irq 7 on isa0 < ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode 52,57c52 < ppc0: at port 0x378-0x37f irq 7 on isa0 < ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode < ppi0: on ppbus0 < lpt0: on ppbus0 < lpt0: Interrupt-driven port < plip0: on ppbus0 --- > ppc0: cannot reserve I/O port range 68c63 < unknown6: at port 0x22,0x2e-0x2f,0x92,0xb2-0xb3,0x4d0-0x4d1,0x15e0-0x15ef,0xef00-0xefaf iomem 0-0x9ffff,0xf0000-0xfffff,0x100000-0x5ffffff,0xffff0000-0xffffffff on isa0 --- > unknown6: at port 0x22,0x2e-0x2f,0x92,0xb2-0xb3,0x4d0-0x4d1,0x15e0-0x15ef,0xef00-0xefaf iomem 0-0x9ffff,0xf0000-0xfffff,0x100000-0x3ffffff,0xffff0000-0xffffffff on isa0 84c79 < ad0: 11513MB [23392/16/63] at ata0-master using UDMA33 --- > ad0: 6149MB [13328/15/63] at ata0-master using UDMA33 86c81 < Mounting root from ufs:/dev/ad0s2a --- > Mounting root from ufs:/dev/ad0s1a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 19 3: 3:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from internal.mail.demon.net (internal.mail.demon.net [193.195.224.3]) by hub.freebsd.org (Postfix) with ESMTP id 0238D37BD9E for ; Fri, 19 May 2000 03:03:27 -0700 (PDT) (envelope-from jguard@demon.net) Received: from gti.noc.demon.net (gti.noc.demon.net [195.11.55.101]) by internal.mail.demon.net with ESMTP id LAA13046; Fri, 19 May 2000 11:03:24 +0100 (BST) Received: (from jguard@localhost) by gti.noc.demon.net (8.8.8/8.8.8) id LAA26999 for freebsd-scsi@freebsd.org; Fri, 19 May 2000 11:03:23 +0100 (BST) Date: Fri, 19 May 2000 11:03:23 +0100 From: James Guard To: freebsd-scsi@freebsd.org Subject: Compaq Proliant DL380 Array Controller Message-ID: <20000519110322.A6122@demon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I am trying to install FreeBSD on a Compaq Proliant DL380 with "Integrated Smart Array Controller" Could someone please confirm if this should be supported by FreeBSD. I have tried 3.4 with ida support compiled into the floppy set and this almost finds the controller - it detects with errors and doesn't work. I have tried 4.0-20000518-Stable which appears to have ida support in the GENERIC kernel, but this does not recognise it at all Do I need to compile ida support into the floppy set for 4.0 Stable as well? Thanks in advance, James -- James Guard System Administrator Interactive Services Demon Internet, Demon@THUS http://www.games.demon.net/ http://www.demon.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 19 8: 4:52 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from p2.acadia.net (p2.acadia.net [205.217.210.2]) by hub.freebsd.org (Postfix) with ESMTP id 7D19237BDB8; Fri, 19 May 2000 08:04:37 -0700 (PDT) (envelope-from tbuswell@acadia.net) Received: from smpbox (ip142167010111.acadia.net [142.167.10.111]) by p2.acadia.net (8.9.3/8.9.3) with ESMTP id LAA02204; Fri, 19 May 2000 11:13:17 -0400 (EDT) Received: (from tbuswell@localhost) by smpbox (8.9.3/8.9.3) id LAA00499; Fri, 19 May 2000 11:09:27 -0400 (EDT) (envelope-from tbuswell) From: Ted Buswell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 19 May 2000 11:08:27 -0400 (EDT) To: wietse@porcupine.org (Wietse Venema) Cc: freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Need FreeBSD 4.0 removable SCSI support In-Reply-To: <20000518231606.5AE974563D@spike.porcupine.org> References: <20000518231606.5AE974563D@spike.porcupine.org> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14629.21138.578322.41745@smpbox> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wietse Venema writes: > Summary: Generic FreeBSD 4.0-RELEASE + Thinkpad 600 + SlimSCSI > 1460B + Jaz 2GB locks up the machine. > > I conclude that FreeBSD 4.0 cannot work with my hardware. Perhaps > it gets upset by garbage from the Jaz disk. I do not care anymore. > Even though you don't care anymore, whether or not the Jaz is upsetting the card or driver by spewing garbage is easy to determine: with nothing plugged into your bus adapter, does the rescan still lockup your machine? And while we're talking about it, is the lockup a real lockup, or is it simply that the camcontrol process hangs and you have it in your startup sequence in such a way that the boot is not able to continue? Also, did you do the obvious things like trying the aic on different interrupts [well, at least both of the interrupts that you stated you use with other devices successfully]? In your second(? third?) message to the -scsi list, you sent the following (snippets from) dmesg: >aic1: at port 0x340-0x35f irq 3 slot 0 on pccard0 >aic1: aic6360, dma, disconnection, parity check >(probe0:aic1:0:0:0): ccb 0xc0b3c000 - timed out, phase 0xa6, state 1 I'm not sure about yours, but my 1460B does not list irq 3 as one of the valid IRQ's that it can generate. Check "pccardc dumpcis" and search for IRQ. While "timed out" messages could also be cable/device related, on my setup they indicated an IRQ conflict. For what it's worth, 5.0-CURRENT + SMP 2xPII + SlimSCSI 1460B (irq 9) + Iomega Zip works. > It looks like Linux will have to be my long-term solution. It was > nice knowing you people. > > Wietse Apologies in advance if this was meant to convey that you are no longer interested in resolving this problem. -Ted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 19 8:39:12 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from spike.porcupine.org (umbilical.porcupine.org [168.100.189.1]) by hub.freebsd.org (Postfix) with ESMTP id 0320837BF02; Fri, 19 May 2000 08:38:57 -0700 (PDT) (envelope-from wietse@porcupine.org) Received: by spike.porcupine.org (Postfix, from userid 100) id 8F53C4563D; Fri, 19 May 2000 11:38:50 -0400 (EDT) Subject: Thanks! In-Reply-To: <20000518214311.0DAC34563D@spike.porcupine.org> from Wietse Venema at "May 18, 0 05:43:11 pm" To: freebsd-mobile@freebsd.org Cc: freebsd-scsi@freebsd.org X-Time-Zone: USA EST, 6 hours behind central European time MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1800 Message-Id: <20000519153850.8F53C4563D@spike.porcupine.org> Date: Fri, 19 May 2000 11:38:50 -0400 (EDT) From: wietse@porcupine.org (Wietse Venema) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks to the PAO project I can keep using FreeBSD on my primary machine that goes where I go, and where things are tried first. I've been a loyal FreeBSD user since day 386bsd. It would have been a traumatic experience to switch primary environment to Linux. There is still one problem: after zzz or closing the lid, the machine wakes up a few seconds after it suspends, even when it was turned on from battery power. Details below the signature. Suggestions for fixes appreciated. Wietse Hardware is Thinkpad 600. apm output follows: APM version: 1.2 APM Managment: Enabled AC Line status: off-line Battery status: high Remaining battery life: 85% Remaining battery time: 5:38:00 Number of batteries: 1 Resume timer: disabled Resume on ring indicator: enabled APM Capacities: global standby state global suspend state resume timer from suspend This is FreeBSD 3.4 and PAO3 out of the box - the only kernel config change being (I do run NTP when plugged into ethernet): 62c62 < #options SCSI_DETACH --- > options SCSI_DETACH 213c213 < #options "APM_NO_CLOCK_ADJUST" --- > options "APM_NO_CLOCK_ADJUST" Changes to rc.conf: < hostname="" # Set this! --- > hostname=bristle.watson.ibm.com 74,75c78,79 < #ifconfig_common="inet 192.168.1.100 netmask 255.255.255.0" < ifconfig_common="DHCP" # Use dhcp --- > ifconfig_common="inet 9.2.84.17 netmask 255.255.255.128" > #ifconfig_common="DHCP" # Use dhcp 156c160 < defaultrouter="NO" # Set to default gateway (or NO). --- > defaultrouter="9.2.84.2" # Set to default gateway (or NO). No changes to pccard.conf (except adding entry for ZOOM modem). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 19 8:45:55 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 4D7C637BF21; Fri, 19 May 2000 08:45:49 -0700 (PDT) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 7FEE63E43; Fri, 19 May 2000 17:45:37 +0200 (CEST) Date: Fri, 19 May 2000 17:45:37 +0200 From: Jesper Skriver To: Wietse Venema Cc: freebsd-mobile@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: Thanks! Message-ID: <20000519174537.B31814@skriver.dk> References: <20000518214311.0DAC34563D@spike.porcupine.org> <20000519153850.8F53C4563D@spike.porcupine.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000519153850.8F53C4563D@spike.porcupine.org>; from wietse@porcupine.org on Fri, May 19, 2000 at 11:38:50AM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, May 19, 2000 at 11:38:50AM -0400, Wietse Venema wrote: > Thanks to the PAO project I can keep using FreeBSD on my primary > machine that goes where I go, and where things are tried first. > > I've been a loyal FreeBSD user since day 386bsd. It would have been > a traumatic experience to switch primary environment to Linux. > > There is still one problem: after zzz or closing the lid, the > machine wakes up a few seconds after it suspends, even when it was > turned on from battery power. I had the exact same problem on my Thinkpad 600E - got it fixed by booting windows and using the APM utility supplied there, I don't think I did anything - apart from rewriting the configuration. Quite strange - but it might solve your problem too. /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 19 8:47: 4 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from spike.porcupine.org (umbilical.porcupine.org [168.100.189.1]) by hub.freebsd.org (Postfix) with ESMTP id F0E3F37BDBC; Fri, 19 May 2000 08:46:52 -0700 (PDT) (envelope-from wietse@porcupine.org) Received: by spike.porcupine.org (Postfix, from userid 100) id 2816B4563D; Fri, 19 May 2000 11:46:50 -0400 (EDT) Subject: Re: Need FreeBSD 4.0 removable SCSI support In-Reply-To: <14629.21138.578322.41745@smpbox> from Ted Buswell at "May 19, 0 11:08:27 am" To: tbuswell@acadia.net (Ted Buswell) Cc: wietse@porcupine.org, freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG X-Time-Zone: USA EST, 6 hours behind central European time MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2183 Message-Id: <20000519154650.2816B4563D@spike.porcupine.org> Date: Fri, 19 May 2000 11:46:50 -0400 (EDT) From: wietse@porcupine.org (Wietse Venema) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ted Buswell: > Even though you don't care anymore, whether or not the Jaz is upsetting > the card or driver by spewing garbage is easy to determine: with nothing > plugged into your bus adapter, does the rescan still lockup your > machine? Hmm, I didn't try that. I'll see if I can fire up 4.0. > And while we're talking about it, is the lockup a real > lockup, or is it simply that the camcontrol process hangs and you have > it in your startup sequence in such a way that the boot is not able to > continue? The machine is dead, as in not responding to keyboard events. It still responds to the power switch so I can avoid a hardware reset. > Also, did you do the obvious things like trying the aic on different > interrupts [well, at least both of the interrupts that you stated you > use with other devices successfully]? In your second(? third?) > message to the -scsi list, you sent the following (snippets from) dmesg: > > >aic1: at port 0x340-0x35f irq 3 slot 0 on pccard0 > >aic1: aic6360, dma, disconnection, parity check > >(probe0:aic1:0:0:0): ccb 0xc0b3c000 - timed out, phase 0xa6, state 1 > > I'm not sure about yours, but my 1460B does not list irq 3 as one of > the valid IRQ's that it can generate. Check "pccardc dumpcis" and > search for IRQ. While "timed out" messages could also be cable/device > related, on my setup they indicated an IRQ conflict. I've tested with IRQ3 and IRQ 9, with identical results. > For what it's worth, 5.0-CURRENT + SMP 2xPII + SlimSCSI 1460B (irq 9) + Iomega > Zip works. I figure the Jaz disk is causing the trouble. I'll see if I can get the 4.0 to work again. The 2.2.8 kernel complains when it recognizes the Jaz disk so I suppose its SCSI is not quite kosher. > > It looks like Linux will have to be my long-term solution. It was > > nice knowing you people. > > > > Wietse > > Apologies in advance if this was meant to convey that you are no > longer interested in resolving this problem. I would love to keep using FreeBSD. It is my primary environment. I really dislike Linux. Having to switch to Linux for my primary environment would not be fun at all. Wietse To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 19 8:57: 4 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from student.rug.ac.be (student.rug.ac.be [157.193.88.45]) by hub.freebsd.org (Postfix) with ESMTP id 326DF37BF11; Fri, 19 May 2000 08:56:57 -0700 (PDT) (envelope-from frank@student.rug.ac.be) Received: (from frank@localhost) by student.rug.ac.be (8.9.3/8.9.3/DSA/1.0) id RAA16318Fri, 19 May 2000 17:56:32 +0200 Date: Fri, 19 May 2000 17:56:32 +0200 From: Frank Louwers To: Wietse Venema Cc: freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Thanks! Message-ID: <20000519175632.A16294@student.rug.ac.be> References: <20000518214311.0DAC34563D@spike.porcupine.org> <20000519153850.8F53C4563D@spike.porcupine.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000519153850.8F53C4563D@spike.porcupine.org>; from wietse@porcupine.org on Fri, May 19, 2000 at 11:38:50AM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, May 19, 2000 at 11:38:50AM -0400, Wietse Venema wrote: > There is still one problem: after zzz or closing the lid, the > machine wakes up a few seconds after it suspends, even when it was > turned on from battery power. Hi Wietse, It feels great to try to help a person like your :) Anyway, here are my .02$. I have a TP760, so not exactly the same. However: try these: a) remove your pcmcia cards before going into suspend/standby b) boot into dos, and check the 'presentation' status with the 'ps2.exe ? presen' command. Make sure it is disabled! Frank -- Frank Louwers Unix System Administrator PGP: 1024D/3F6A7EDD D597 566A BDF5 BBFB C308 447A 5E81 1188 3F6A 7EDD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 19 9:56:26 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from spike.porcupine.org (umbilical.porcupine.org [168.100.189.1]) by hub.freebsd.org (Postfix) with ESMTP id DEE1637B56E; Fri, 19 May 2000 09:56:21 -0700 (PDT) (envelope-from wietse@porcupine.org) Received: by spike.porcupine.org (Postfix, from userid 100) id 3AC404563D; Fri, 19 May 2000 12:56:19 -0400 (EDT) Subject: Re: Need FreeBSD 4.0 removable SCSI support In-Reply-To: <14629.21138.578322.41745@smpbox> from Ted Buswell at "May 19, 0 11:08:27 am" To: tbuswell@acadia.net (Ted Buswell) Cc: wietse@porcupine.org, freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG X-Time-Zone: USA EST, 6 hours behind central European time MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 798 Message-Id: <20000519165619.3AC404563D@spike.porcupine.org> Date: Fri, 19 May 2000 12:56:19 -0400 (EDT) From: wietse@porcupine.org (Wietse Venema) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ted Buswell: > I'm not sure about yours, but my 1460B does not list irq 3 as one of > the valid IRQ's that it can generate. Check "pccardc dumpcis" and > search for IRQ. While "timed out" messages could also be cable/device > related, on my setup they indicated an IRQ conflict. Here's one data point with FreeBSD 3.4+PAO, same machine: card0: assign aic0 iobase 0x340 irq 3 aic0: aic6360, dma, disconnection, parity check (da0:aic0:0:0:0): ccb 0xc07c3800 - timed out, phase 0x0, state 0 da0 at aic0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 5.000MB/s transfers (5.000MHz, offset 8) da0: 1911MB (3915600 512 byte sectors: 64H 32S/T 1911C) So the driver does gripe, but it survives, and that's what I need. Wietse To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 19 10:30:37 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from p2.acadia.net (p2.acadia.net [205.217.210.2]) by hub.freebsd.org (Postfix) with ESMTP id 8114437B669; Fri, 19 May 2000 10:30:32 -0700 (PDT) (envelope-from tbuswell@acadia.net) Received: from smpbox (ip142167010111.acadia.net [142.167.10.111]) by p2.acadia.net (8.9.3/8.9.3) with ESMTP id NAA04521; Fri, 19 May 2000 13:39:10 -0400 (EDT) Received: (from tbuswell@localhost) by smpbox (8.9.3/8.9.3) id NAA00932; Fri, 19 May 2000 13:35:23 -0400 (EDT) (envelope-from tbuswell) From: Ted Buswell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 19 May 2000 13:34:22 -0400 (EDT) To: wietse@porcupine.org (Wietse Venema) Cc: freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Need FreeBSD 4.0 removable SCSI support In-Reply-To: <20000519165619.3AC404563D@spike.porcupine.org> References: <14629.21138.578322.41745@smpbox> <20000519165619.3AC404563D@spike.porcupine.org> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14629.31234.408264.179584@smpbox> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wietse Venema writes: > Ted Buswell: > > I'm not sure about yours, but my 1460B does not list irq 3 as one of > > the valid IRQ's that it can generate. Check "pccardc dumpcis" and > > search for IRQ. While "timed out" messages could also be cable/device > > related, on my setup they indicated an IRQ conflict. > > Here's one data point with FreeBSD 3.4+PAO, same machine: > > card0: assign aic0 iobase 0x340 irq 3 > aic0: aic6360, dma, disconnection, parity check > (da0:aic0:0:0:0): ccb 0xc07c3800 - timed out, phase 0x0, state 0 > da0 at aic0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-2 device > da0: 5.000MB/s transfers (5.000MHz, offset 8) > da0: 1911MB (3915600 512 byte sectors: 64H 32S/T 1911C) > > So the driver does gripe, but it survives, and that's what I need. > > Wietse Are you getting any errors other than during the rescan (i.e. while actually using the disk) ? -Ted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 19 10:32:51 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from moek.pir.net (moek.pir.net [209.192.237.190]) by hub.freebsd.org (Postfix) with ESMTP id 9B0F437BF51; Fri, 19 May 2000 10:32:39 -0700 (PDT) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 12sqdR-0005pO-00 ; Fri, 19 May 2000 13:32:29 -0400 Date: Fri, 19 May 2000 13:32:28 -0400 From: Peter Radcliffe To: Wietse Venema Cc: freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Need FreeBSD 4.0 removable SCSI support Message-ID: <20000519133228.A22178@pir.net> Mail-Followup-To: Wietse Venema , freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG References: <14629.21138.578322.41745@smpbox> <20000519154650.2816B4563D@spike.porcupine.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000519154650.2816B4563D@spike.porcupine.org>; from wietse@porcupine.org on Fri, May 19, 2000 at 11:46:50AM -0400 X-fish: < Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Note: I'm on -mobile but not -scsi. Wietse Venema probably said: > Ted Buswell: > > Even though you don't care anymore, whether or not the Jaz is upsetting > > the card or driver by spewing garbage is easy to determine: with nothing > > plugged into your bus adapter, does the rescan still lockup your > > machine? > > Hmm, I didn't try that. I'll see if I can fire up 4.0. I pulled a 1Gb Jaz drive from another machine (I don't have any 2Gb jaz drives) and tested that with my adaptec 1460. I could scan the bus ok, but running /stand/sysinstall crashed the machine. I got a crashdump; panicstr: page fault but I can't get any real information from this, no real stack trace :/ just late shutdown stuff; (kgdb) where #0 boot (howto=Cannot access memory at address 0xc8fe7c08. ) at ../../kern/kern_shutdown.c:304 (kgdb) list 299 EVENTHANDLER_INVOKE(shutdown_post_sync, howto); 300 splhigh(); 301 if ((howto & (RB_HALT|RB_DUMP)) == RB_DUMP && !cold) { 302 savectx(&dumppcb); 303 #ifdef __i386__ 304 dumppcb.pcb_cr3 = rcr3(); 305 #endif 306 dumpsys(); 307 } 308 Trying again after the reboot I can use the Jaz drive fine, sysinstall works ok, I can mount the dos partition ... no scsi errors. Unfortunately I don't have a 2Gb drive that WV said he was having trouble with to test. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 19 10:40:15 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from spike.porcupine.org (umbilical.porcupine.org [168.100.189.1]) by hub.freebsd.org (Postfix) with ESMTP id 41D5937B5D0; Fri, 19 May 2000 10:40:10 -0700 (PDT) (envelope-from wietse@porcupine.org) Received: by spike.porcupine.org (Postfix, from userid 100) id E03D54563D; Fri, 19 May 2000 13:40:05 -0400 (EDT) Subject: Re: Need FreeBSD 4.0 removable SCSI support In-Reply-To: <14629.31234.408264.179584@smpbox> from Ted Buswell at "May 19, 0 01:34:22 pm" To: tbuswell@acadia.net (Ted Buswell) Cc: wietse@porcupine.org, freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG X-Time-Zone: USA EST, 6 hours behind central European time MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1237 Message-Id: <20000519174005.E03D54563D@spike.porcupine.org> Date: Fri, 19 May 2000 13:40:05 -0400 (EDT) From: wietse@porcupine.org (Wietse Venema) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ted Buswell: > > Wietse Venema writes: > > Ted Buswell: > > > I'm not sure about yours, but my 1460B does not list irq 3 as one of > > > the valid IRQ's that it can generate. Check "pccardc dumpcis" and > > > search for IRQ. While "timed out" messages could also be cable/device > > > related, on my setup they indicated an IRQ conflict. > > > > Here's one data point with FreeBSD 3.4+PAO, same machine: > > > > card0: assign aic0 iobase 0x340 irq 3 > > aic0: aic6360, dma, disconnection, parity check > > (da0:aic0:0:0:0): ccb 0xc07c3800 - timed out, phase 0x0, state 0 > > da0 at aic0 bus 0 target 0 lun 0 > > da0: Removable Direct Access SCSI-2 device > > da0: 5.000MB/s transfers (5.000MHz, offset 8) > > da0: 1911MB (3915600 512 byte sectors: 64H 32S/T 1911C) > > > > So the driver does gripe, but it survives, and that's what I need. > > Are you getting any errors other than during the rescan (i.e. while > actually using the disk) ? It is quite happy when I fsck the file system (one large partition with a complete backup of my 2.2.8 environment) which takes a considerable amount of time. I have similar results when aic0 is assigned IRQ 9. Wietse To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 19 11:12:48 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 8371C37B532; Fri, 19 May 2000 11:12:44 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e4JICZr65256; Fri, 19 May 2000 11:12:35 -0700 (PDT) Date: Fri, 19 May 2000 11:12:35 -0700 (PDT) From: Doug White To: Wietse Venema Cc: freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Thanks! In-Reply-To: <20000519153850.8F53C4563D@spike.porcupine.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 19 May 2000, Wietse Venema wrote: > Thanks to the PAO project I can keep using FreeBSD on my primary > machine that goes where I go, and where things are tried first. > > I've been a loyal FreeBSD user since day 386bsd. It would have been > a traumatic experience to switch primary environment to Linux. > > There is still one problem: after zzz or closing the lid, the > machine wakes up a few seconds after it suspends, even when it was > turned on from battery power. There's also the sleep 1; zzz command since sometimes the machine will pick up the from the command as a keystroke and say alive. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 19 16:58:44 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from zirizui.lotbiniere.net (HSE-Toronto-ppp129882.sympatico.ca [64.228.64.239]) by hub.freebsd.org (Postfix) with ESMTP id 912EF37B61C for ; Fri, 19 May 2000 16:58:38 -0700 (PDT) (envelope-from Michel@Lotbiniere.Net) Received: from Spooler by zirizui.lotbiniere.net (Mercury/32 v3.01a) ID MO000016; 19 May 00 19:58:41 -0400 Received: from spooler by zirizui.lotbiniere.net (Mercury/32 v3.01a); 19 May 00 19:58:33 -0400 Received: from zirizui (192.168.1.100) by lotbiniere.net (Mercury/32 v3.01a) ID MG000015; 19 May 00 19:58:26 -0400 From: "Michel Joly de Lotbiniere" To: Subject: Q: Sony AIT-2 SDX-500C tape drive supported? Date: Fri, 19 May 2000 19:58:25 -0400 Message-ID: <000001bfc1ee$1f366920$6401a8c0@lotbiniere.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-Mimeole: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear Gurus, I'm debating the use of FreeBSD 4.0 (RELEASE version); due to the fact that my machine's disk space is entirely occupied by Windows 2K, testing FBSD is an all-or-nothing proposition, hence I'd like to be fairly certain that this hardware will work with the usual dump/restore utilities. This Sony drive is an AIT-2 Internal Tape Drive, OEM Model with Single Ended, Ultra SCSI, LVDS Interface (see http://ccpgprod.sel.sony.com/ccpg/ccpg_eusub_modelsub?model_id=SDX-500C). In the tech ref manual (http://ccpgprod.sel.sony.com/pdf/sdx500cpsm.pdf), p. 173, Sony says "In default configuration, the Sony SDX-500C emulates DDS drives. In this mode, it supports up to two partitions, logically numbered 0 and 1, where the logical Partition 1 is the first physical partition on the tape. The physical partition numbering is the same in either the DDS emulation or the native AIT mode: the first partition on tape is given the physical partition number of 0. In the DDS emulation mode, the drive translates the physical partition numbering scheme into the logical scheme that is communicated to the host. In the AIT mode, the logical partition numbers correspond directly to the physical partition numbers. SDX-500C manages DDS Emulation transparently, and it can be used as a large capacity and a high transfer rate DDS drive." And p. 181 goes on: "Consequently, SDX-500C can be used with DDS applications without requiring configuration adjustments via special commands or hardware switches. [...] (1) Cassette has its own Mode, of which there are two: (a) DDS mode and (b) AIT mode. The default mode for the drive is also the DDS mode, therefore a MIC cassette will be initialised as DDS mode cassette. You can initialise MIC in the AIT mode by using Mode Select Page 31h before Mode Select Page 11h. (2) The Mode is assigned for the cassette when it is initialised by using Mode Select Page 11h. If the AIT bit is set to ONE with Mode Select Page 31h before Mode Select Page 11h, then the cassette will be initialised in the AIT mode. (3) The power up default mode for SDX-500C is the DDS mode. SDX-500C automatically changes its mode to the same mode as with the cassette; it also automatically returns to the default (DDS) mode after ejecting the AIT mode cassette." Would this mean /unequivocally/ that the tape drivers in FBSD-4.0-RELEASE will work happily with this (wonderfully fast) device? The tech manual is a very detailed description of exactly how the SCSI interface works, but unfortunately I don't have the required SCSI guru knowledge to deduce the answer. Any help much appreciated and will be acknowledged. // Michel Joly de Lotbinière To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 20 7:39:58 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from spike.porcupine.org (umbilical.porcupine.org [168.100.189.1]) by hub.freebsd.org (Postfix) with ESMTP id E590737B6B4; Sat, 20 May 2000 07:39:51 -0700 (PDT) (envelope-from wietse@porcupine.org) Received: by spike.porcupine.org (Postfix, from userid 100) id 0D9664563D; Sat, 20 May 2000 10:39:50 -0400 (EDT) Subject: Data point: FreeBSD 4.0 + removable SCSI support In-Reply-To: <20000519154650.2816B4563D@spike.porcupine.org> from Wietse Venema at "May 19, 0 11:46:50 am" To: wietse@porcupine.org (Wietse Venema) Cc: tbuswell@acadia.net, wietse@porcupine.org, freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG X-Time-Zone: USA EST, 6 hours behind central European time MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2095 Message-Id: <20000520143950.0D9664563D@spike.porcupine.org> Date: Sat, 20 May 2000 10:39:50 -0400 (EDT) From: wietse@porcupine.org (Wietse Venema) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ted Buswell: > Even though you don't care anymore, whether or not the Jaz is upsetting > the card or driver by spewing garbage is easy to determine: with nothing > plugged into your bus adapter, does the rescan still lockup your > machine? Without devices attached to the SlimSCSI 1460B, "camcontrol rescan 0" reports success. With random hardware connected to the SlimSCSI 1460B, "camcontrol rescan 0" reports success, and the kernel says: May 20 14:04:01 bristle /kernel: sa0 at aic1 bus 0 target 5 lun 0 May 20 14:04:01 bristle /kernel: sa0: Removable Sequential Access SCSI-CCS device May 20 14:04:01 bristle /kernel: sa0: 3.300MB/s transfers For the sake of completeness, this is what the kernel logs when the SlimSCSI 1460B itself is installed: May 20 13:56:31 bristle /kernel: aic1: at port 0x340-0x35f irq 3 slot 0 on pccard0 May 20 13:56:31 bristle /kernel: aic1: aic6360, dma, disconnection, parity check With the same IRQ setting and the same I/O port setting on the same machine, FreeBSD3.4+PAO3 is able to access the same JAZ 2GB drive successfully, just like the much older FreeBSD 2.2.8. However, FreeBSD3.4+PAO3 occasionally drops me into the kernel debugger after I execute /usr/bin/halt. That is not supposed to happen. > And while we're talking about it, is the lockup a real > lockup, or is it simply that the camcontrol process hangs and you have > it in your startup sequence in such a way that the boot is not able to > continue? The machine does not respond to keyboard events or network events. The reset and power buttons still have effect, though. Conclusion: the aic device driver has a problem with an unexpected (lack of) response from the JAZ 2GB drive. FreeBSD3.4+PAO3 gripes, too, but it does recover (except for sometimes dropping me into a kernel debugger). If you need to know more, there is a few more days before I have to return the test disk. After that, I will not be able to do further experiments with 4.0 on that laptop until July or so. Wietse To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message