From owner-freebsd-hardware Sun Feb 3 9:16:55 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from nikita.theblinis.net (nikita.theblinis.net [62.212.96.132]) by hub.freebsd.org (Postfix) with ESMTP id D72E237B419 for ; Sun, 3 Feb 2002 09:16:42 -0800 (PST) Received: from vaio (vaio [192.168.0.16]) by nikita.theblinis.net (8.11.6/8.11.3) with SMTP id g13HGmb12973 for ; Sun, 3 Feb 2002 18:16:48 +0100 (CET) (envelope-from admin@optogone.com) Message-ID: <004b01c1acd6$8ac74ae0$1000a8c0@vaio> From: "Michel Gravey" To: Subject: OnStream DI30 tape Date: Sun, 3 Feb 2002 18:16:39 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I have problem using the adr di30 tape. Freebsd recognizes it as ast0: TAPE at ata1-master using PIO4 Any write/erase command give messages like this ast0: WARNING: CTL exceeded 65536>32768 ast0: SPACE - ILLEGAL REQUEST asc=20 ascq=00 error=04 ast0: WRITE - ILLEGAL REQUEST asc=24 ascq=00 error=04 ast0: SPACE - ILLEGAL REQUEST asc=20 ascq=00 error=04 ast0: WRITE - ILLEGAL REQUEST asc=24 ascq=00 error=04 ast0: ERASE - ILLEGAL REQUEST asc=20 ascq=00 error=04 I use flexbakup and I'm running FreeBSD 4.5 stable. mt -f /dev/nrast0 erase mt: /dev/nrast0: erase: Input/output error optogone# Feb 3 15:02:34 optogone /kernel: ast0: ERASE - ILLEGAL REQUEST asc=20 ascq=00 error=04 Thanks in advance, Michel Gravey mailto: admin@optogone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Feb 4 1:14:50 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from Mail6.nc.rr.com (fe6.southeast.rr.com [24.93.67.53]) by hub.freebsd.org (Postfix) with ESMTP id 546D637B400; Mon, 4 Feb 2002 01:14:41 -0800 (PST) Received: from i8k.babbleon.org ([66.57.85.154]) by Mail6.nc.rr.com with Microsoft SMTPSVC(5.5.1877.687.68); Sun, 3 Feb 2002 22:37:22 -0500 Received: by i8k.babbleon.org (Postfix, from userid 111) id 9A71E4074; Sun, 3 Feb 2002 09:20:29 -0500 (EST) Content-Type: text/plain; charset="iso-8859-1" From: Brian T.Schellenberger To: freebsd-question@freebsd.org, freebsd-hardware@freebsd.org Subject: USB drive -- problems Date: Sun, 3 Feb 2002 09:20:28 -0500 X-Mailer: KMail [version 1.3] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020203142029.9A71E4074@i8k.babbleon.org> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Ok, with little confidence it would work, since I could find no very good info on USB & FreeBSD, and there was no response to my query on the subject, I decided in a "what the hell" moment to get a USB drive and see what happened. I have a LaCie 80G drive. It was $250 for 80, USB 2, and if it works it should be pretty darn cool. It is recognized by the kernel, so I thought I was doing pretty well, but when I try to actually do anything with it, I run into trouble. Here are some messages from /var/log messages, first hte successful boot stuff and then the failure messages: Feb 3 04:31:21 i8k /kernel: uhci0: port 0xbce0-0xbcff irq 11 at device 31.2 on pci0 Feb 3 04:31:21 i8k /kernel: usb0: on uhci0 Feb 3 04:31:21 i8k /kernel: usb0: USB revision 1.0 Feb 3 04:31:21 i8k /kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Feb 3 04:31:21 i8k /kernel: uhub0: 2 ports with 2 removable, self powered Feb 3 04:31:21 i8k /kernel: umass0: LaCie LaCie StudioDrive USB2 , rev 2.00/10.06, addr 2 : : Feb 3 04:31:21 i8k /kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Feb 3 04:31:22 i8k /kernel: da0: Fixed Direct Access SCSI-0 device Feb 3 04:31:22 i8k /kernel: da0: 650KB/s transfers Feb 3 04:31:22 i8k /kernel: da0: 78167MB (160086528 512 byte sectors: 64H 32S/T 12631C) : : Feb 3 05:08:48 i8k /kernel: (da0:umass-sim0:0:0:0): READ(06). CDB: 8 0 0 0 1 0 Feb 3 05:08:48 i8k /kernel: (da0:umass-sim0:0:0:0): ILLEGAL REQUEST asc:21,0 Feb 3 05:08:48 i8k /kernel: (da0:umass-sim0:0:0:0): Logical block address out of range Feb 3 05:08:57 i8k /kernel: (da0:umass-sim0:0:0:0): READ(06). CDB: 8 0 0 0 1 0 Feb 3 05:08:57 i8k /kernel: (da0:umass-sim0:0:0:0): ILLEGAL REQUEST asc:21,0 Feb 3 05:08:57 i8k /kernel: (da0:umass-sim0:0:0:0): Logical block address out of range The set of error messages above were returned when I did a simple dd if=/dev/da0 PS: I might not recieve mail for a couple days so don't be surprised if responses are a little slow. Based on previous response to USB queries on the questions list I doubt that excessive responses will be a big problem. I'm including the questions list here more as an "FYI" sort of thing. PPS: Why, oh why is there a /dev/ad0 and a /dev/da0? What do they stand for? It's darn confusing and it makes me nervous as heck doing "dangerous" operations where I am one swapped letter pair away from wiping out my primary drive! -- Brian T. Schellenberger . . . . . . . bts@wnt.sas.com (work) Brian, the man from Babble-On . . . . bts@babbleon.org (personal) ME --> http://www.babbleon.org http://www.eff.org <-- GOOD GUYS --> http://www.programming-freedom.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Feb 4 5: 1:28 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mailout09.sul.t-online.com (mailout09.sul.t-online.com [194.25.134.84]) by hub.freebsd.org (Postfix) with ESMTP id 85C2937B420 for ; Mon, 4 Feb 2002 05:01:20 -0800 (PST) Received: from fwd06.sul.t-online.de by mailout09.sul.t-online.com with smtp id 16XikF-00006W-0A; Mon, 04 Feb 2002 14:01:15 +0100 Received: from twoflower (320072111332-0001@[217.80.121.179]) by fmrl06.sul.t-online.com with smtp id 16XikB-0ebSkKC; Mon, 4 Feb 2002 14:01:11 +0100 Reply-To: From: "Jan Stocker" To: "Brian T.Schellenberger" , Subject: RE: USB drive -- problems Date: Mon, 4 Feb 2002 14:00:20 +0100 Message-ID: <000701c1ad7b$e6982d80$fe02010a@twoflower.liebende.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 In-Reply-To: <20020203142029.9A71E4074@i8k.babbleon.org> X-Sender: 320072111332-0001@t-dialin.net Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org A maybe better discussion group will be freebsd-scsi. Maybe you need to turn off 6-byte commands with a quirk... Jan > PPS: Why, oh why is there a /dev/ad0 and a /dev/da0? What do > they stand for? Okay... da is for the DirectAccess drives on USB/SCSI ad represent the ATA-Drives. So ad0 is the primary-master ATA-IDE drive. > -----Original Message----- > From: owner-freebsd-hardware@FreeBSD.ORG > [mailto:owner-freebsd-hardware@FreeBSD.ORG]On Behalf Of Brian > T.Schellenberger > Sent: Sunday, February 03, 2002 3:20 PM > To: freebsd-question@FreeBSD.ORG; freebsd-hardware@FreeBSD.ORG > Subject: USB drive -- problems > > > > Ok, with little confidence it would work, since I could find no very good > info on USB & FreeBSD, and there was no response to my query on > the subject, > I decided in a "what the hell" moment to get a USB drive and see what > happened. > > I have a LaCie 80G drive. It was $250 for 80, USB 2, and if it works it > should be pretty darn cool. > > It is recognized by the kernel, so I thought I was doing pretty well, but > when I try to actually do anything with it, I run into trouble. Here are > some messages from /var/log messages, first hte successful boot stuff and > then the failure messages: > > Feb 3 04:31:21 i8k /kernel: uhci0: controller > USB-A> port 0xbce0-0xbcff irq 11 at device 31.2 on pci0 > Feb 3 04:31:21 i8k /kernel: usb0: controller > USB-A> on uhci0 > Feb 3 04:31:21 i8k /kernel: usb0: USB revision 1.0 > Feb 3 04:31:21 i8k /kernel: uhub0: Intel UHCI root hub, class 9/0, rev > 1.00/1.00, addr 1 > Feb 3 04:31:21 i8k /kernel: uhub0: 2 ports with 2 removable, self powered > Feb 3 04:31:21 i8k /kernel: umass0: LaCie LaCie StudioDrive USB2 > , > rev 2.00/10.06, addr 2 > : > : > Feb 3 04:31:21 i8k /kernel: da0 at umass-sim0 bus 0 target 0 lun 0 > Feb 3 04:31:22 i8k /kernel: da0: Fixed > Direct Access > SCSI-0 device > Feb 3 04:31:22 i8k /kernel: da0: 650KB/s transfers > Feb 3 04:31:22 i8k /kernel: da0: 78167MB (160086528 512 byte > sectors: 64H > 32S/T 12631C) > : > : > Feb 3 05:08:48 i8k /kernel: (da0:umass-sim0:0:0:0): READ(06). > CDB: 8 0 0 0 1 > 0 > Feb 3 05:08:48 i8k /kernel: (da0:umass-sim0:0:0:0): ILLEGAL > REQUEST asc:21,0 > Feb 3 05:08:48 i8k /kernel: (da0:umass-sim0:0:0:0): Logical > block address > out of range > Feb 3 05:08:57 i8k /kernel: (da0:umass-sim0:0:0:0): READ(06). > CDB: 8 0 0 0 1 > 0 > Feb 3 05:08:57 i8k /kernel: (da0:umass-sim0:0:0:0): ILLEGAL > REQUEST asc:21,0 > Feb 3 05:08:57 i8k /kernel: (da0:umass-sim0:0:0:0): Logical > block address > out of range > > The set of error messages above were returned when I did a simple > > dd if=/dev/da0 > > > PS: I might not recieve mail for a couple days so don't be surprised if > responses are a little slow. Based on previous response to USB > queries on > the questions list I doubt that excessive responses will be a big > problem. > I'm including the questions list here more as an "FYI" sort of thing. > > It's darn confusing and it makes me nervous as heck doing "dangerous" > operations where I am one swapped letter pair away from wiping > out my primary > drive! > > > > > > -- > Brian T. Schellenberger . . . . . . . bts@wnt.sas.com (work) > Brian, the man from Babble-On . . . . bts@babbleon.org (personal) > ME --> http://www.babbleon.org > http://www.eff.org <-- GOOD GUYS --> > http://www.programming-freedom.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Feb 5 12:26:34 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from Thanatos.Shenton.Org (a3.ebbed1.client.atlantech.net [209.190.235.163]) by hub.freebsd.org (Postfix) with SMTP id 3DB2137B48A for ; Tue, 5 Feb 2002 12:26:22 -0800 (PST) Received: (qmail 30765 invoked by uid 1000); 5 Feb 2002 20:26:20 -0000 To: hardware@freebsd.org Subject: Anyone using FalconStor virtual NAS/SAN? From: Chris Shenton Date: 05 Feb 2002 15:26:20 -0500 Message-ID: <873d0fd6ab.fsf@thanatos.shenton.org> Lines: 18 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Talked to a vendor recently who's building something NetApp like based on FalconStor's product. (The NetApp won't do what he needs for distributed database storage). I hadn't heard of it but it looks pretty interesting. See http://www.falconstor.com/. It appears to collect IP- or FC-connected back-end storage, then offer it as a virtualized service to client machines over IP or FC. The online product description indicate it runs on a few variants of Lunix, and has client machine drivers for DOS, Lunix, and Solaris. No BSD for either the server platform nor client drivers. Bummer. Seems like an ideal system in a decent-sized ISP environment or good sized server shop. And I expect BSD's superior networking wouldn't slow it down as much as the Lunix stack. Just curious if any BSDers have played with it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Feb 6 14:50:50 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from db.nexgen.com (db.nexgen.com [66.92.98.149]) by hub.freebsd.org (Postfix) with SMTP id 7381537B434 for ; Wed, 6 Feb 2002 14:50:46 -0800 (PST) Received: (qmail 89872 invoked from network); 6 Feb 2002 22:50:39 -0000 Received: from oxyetb.com (HELO alexus) (@66.92.98.145) by secure.nexgen.com with SMTP; 6 Feb 2002 22:50:39 -0000 Message-ID: <004301c1af60$b6761e00$0d00a8c0@alexus> From: "alexus" To: Cc: Subject: teaming/failover Date: Wed, 6 Feb 2002 17:50:45 -0500 Organization: NexGen MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello First of all I'd like to appologize for cross posting, but I wasn't quite sure which list should i start with, this question basically can relate to both lists. here is my question: I was wondering if there is a way to do a teaming/failover in Freebsd with network cards, if it's not available now or it's being in development is there any dates on beta versions of it? I'm using Intel(R) PRO/100 S Desktop Adapter and I also have Intel card server version and i was able to do that on Windows platform, but now i'm looking to do same thing with FreeBSD machines Thank you in advance Your Trully alexus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 7 12:46:46 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id 52D1437B41A; Thu, 7 Feb 2002 12:46:36 -0800 (PST) Received: (from olli@localhost) by lurza.secnetix.de (8.11.6/8.11.6) id g17KkSM05459; Thu, 7 Feb 2002 21:46:28 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Date: Thu, 7 Feb 2002 21:46:28 +0100 (CET) Message-Id: <200202072046.g17KkSM05459@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hardware@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: USB "Memorybird" quirks User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.5-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I've got a small problem with a nice little thing called "USB Memorybird" (Fujitsu-Siemens) ... It is bascially a 64 MB Flash chip in a small plastic pen that you can carry with your keys. It doesn't need any battery and you can plug it directly into a USB socket. Very neat. Works without any drivers on WinME and Win2k, so I assume it should be some standard USB mass storage device. FreeBSD 4.5 recognizes it out of the box and attaches it as a SCSI disk, but I cannot access it. This is what happens: From the boot log: uhci0: port 0xd400-0xd41f irq 10 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered This appears when I connect the Memorybird: umass0: Fujitsu Memorybird, rev 1.00/1.00, addr 2 da2 at umass-sim0 bus 0 target 0 lun 0 da2: Removable Direct Access SCSI-0 device da2: 650KB/s transfers da2: 62MB (128000 512 byte sectors: 64H 32S/T 62C) This is the output from "usbdevs -v" (note that there is a ~10 seconds delay!): Controller /dev/usb0: addr 1: self powered, config 1, UHCI root hub(0x0000), VIA(0x0000), rev 0x0100 port 1 powered < ~10 seconds delay > port 2 addr 2: power 100 mA, config 1, product 0x0100(0x0100), vendor 0x0d7d(0x0d7d), rev 0x0100 When I type "fdisk da2", it hangs for a while, then prints: fdisk: can't open device /dev/da2 fdisk: cannot open disk /dev/da2: Input/output error At the same time, the kernel logs this: Feb 7 20:00:31 lurza /kernel: umass0: BBB reset failed, TIMEOUT Feb 7 20:00:36 lurza /kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT Feb 7 20:00:41 lurza /kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT Feb 7 20:00:51 lurza /kernel: umass0: BBB reset failed, TIMEOUT Feb 7 20:00:56 lurza /kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT Feb 7 20:01:01 lurza /kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT The same happens when I try to dd some block from the device to /dev/null. During my experiments I also got these messages (I don't know if they're important): Feb 7 19:54:46 lurza /kernel: da2: reading primary partition table: error reading fsbn 0 Feb 7 19:54:56 lurza /kernel: umass0: BBB reset failed, TIMEOUT Feb 7 19:55:01 lurza /kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT Feb 7 19:55:06 lurza /kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT Feb 7 19:55:06 lurza /kernel: (da2:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 Is there a chance to get this to run? Clearly the umass driver recognizes it and attaches it as a SCSI disk, so I assume that it can't be _that_ hard to convince it to work with FreeBSD. :) Are there any quirks that I should try? I'm not extremely familiar with that kind of stuff, but I'm willing to experiment. Thanks in advance for any help! I would _really_ love to get this thing working. Regards Oliver BTW: More information on the Memorybird: http://www.fujitsu-siemens.com/rl/peripherals/homeperipherals/memorybird.html -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 7 12:55:16 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from alicia.nttmcl.com (alicia.nttmcl.com [216.69.69.10]) by hub.freebsd.org (Postfix) with ESMTP id BDE6737B405; Thu, 7 Feb 2002 12:54:54 -0800 (PST) Received: (from gene@localhost) by alicia.nttmcl.com (8.10.1/8.10.1) id g17KsnO09885; Thu, 7 Feb 2002 12:54:49 -0800 (PST) Date: Thu, 7 Feb 2002 12:54:49 -0800 From: "Eugene M. Kim" To: Oliver Fromme Cc: FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks Message-ID: <20020207125449.A9620@alicia.nttmcl.com> References: <200202072046.g17KkSM05459@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2i In-Reply-To: <200202072046.g17KkSM05459@lurza.secnetix.de>; from olli@secnetix.de on Thu, Feb 07, 2002 at 09:46:28PM +0100 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This is a common problem of most umass devices that implements BBB protocol, and arises from the fact that those devices don't understand the 6-byte SCSI READ command. You can add a quirk entry to src/sys/cam/scsi_da.c (refer to quirk entries that have DA_Q_NO_6_BYTE). IIRC this problem is being addressed at a more fundamental level on -current, by adding a 6-byte-to-10-byte READ command translator somewhere in the abstraction layer. Eugene On Thu, Feb 07, 2002 at 09:46:28PM +0100, Oliver Fromme wrote: > > > Hi, > > I've got a small problem with a nice little thing called > "USB Memorybird" (Fujitsu-Siemens) ... > > It is bascially a 64 MB Flash chip in a small plastic pen > that you can carry with your keys. It doesn't need any > battery and you can plug it directly into a USB socket. > Very neat. > > Works without any drivers on WinME and Win2k, so I assume > it should be some standard USB mass storage device. > > FreeBSD 4.5 recognizes it out of the box and attaches it as > a SCSI disk, but I cannot access it. This is what happens: > > >From the boot log: > > uhci0: port 0xd400-0xd41f irq 10 at device 7.2 on pci0 > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > > This appears when I connect the Memorybird: > > umass0: Fujitsu Memorybird, rev 1.00/1.00, addr 2 > da2 at umass-sim0 bus 0 target 0 lun 0 > da2: Removable Direct Access SCSI-0 device > da2: 650KB/s transfers > da2: 62MB (128000 512 byte sectors: 64H 32S/T 62C) > > This is the output from "usbdevs -v" (note that there is a > ~10 seconds delay!): > > Controller /dev/usb0: > addr 1: self powered, config 1, UHCI root hub(0x0000), VIA(0x0000), rev 0x0100 > port 1 powered > < ~10 seconds delay > > port 2 addr 2: power 100 mA, config 1, product 0x0100(0x0100), vendor 0x0d7d(0x0d7d), rev 0x0100 > > When I type "fdisk da2", it hangs for a while, then prints: > > fdisk: can't open device /dev/da2 > fdisk: cannot open disk /dev/da2: Input/output error > > At the same time, the kernel logs this: > > Feb 7 20:00:31 lurza /kernel: umass0: BBB reset failed, TIMEOUT > Feb 7 20:00:36 lurza /kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT > Feb 7 20:00:41 lurza /kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT > Feb 7 20:00:51 lurza /kernel: umass0: BBB reset failed, TIMEOUT > Feb 7 20:00:56 lurza /kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT > Feb 7 20:01:01 lurza /kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT > > The same happens when I try to dd some block from the > device to /dev/null. During my experiments I also got > these messages (I don't know if they're important): > > Feb 7 19:54:46 lurza /kernel: da2: reading primary partition table: error reading fsbn 0 > Feb 7 19:54:56 lurza /kernel: umass0: BBB reset failed, TIMEOUT > Feb 7 19:55:01 lurza /kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT > Feb 7 19:55:06 lurza /kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT > Feb 7 19:55:06 lurza /kernel: (da2:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 > > Is there a chance to get this to run? Clearly the umass > driver recognizes it and attaches it as a SCSI disk, so > I assume that it can't be _that_ hard to convince it to > work with FreeBSD. :) > > Are there any quirks that I should try? I'm not extremely > familiar with that kind of stuff, but I'm willing to > experiment. > > Thanks in advance for any help! I would _really_ love to > get this thing working. > > Regards > Oliver > > BTW: More information on the Memorybird: > http://www.fujitsu-siemens.com/rl/peripherals/homeperipherals/memorybird.html > > -- > Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München > Any opinions expressed in this message may be personal to the author > and may not necessarily reflect the opinions of secnetix in any way. > > "All that we see or seem is just a dream within a dream" (E. A. Poe) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 7 13:44:13 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id DB98E37B425; Thu, 7 Feb 2002 13:42:50 -0800 (PST) Received: (from olli@localhost) by lurza.secnetix.de (8.11.6/8.11.6) id g17LgjV01787; Thu, 7 Feb 2002 22:42:45 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) From: Oliver Fromme Message-Id: <200202072142.g17LgjV01787@lurza.secnetix.de> Subject: kern/34712 (was: USB "Memorybird" quirks) To: gene@nttmcl.com (Eugene M. Kim) Date: Thu, 7 Feb 2002 22:42:45 +0100 (CET) Cc: hardware@freebsd.org (FreeBSD Hardware Mailing List), hackers@freebsd.org (FreeBSD Hackers Mailing List) In-Reply-To: <20020207125449.A9620@alicia.nttmcl.com> from "Eugene M. Kim" at Feb 07, 2002 12:54:49 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Eugene M. Kim wrote: > This is a common problem of most umass devices that implements BBB > protocol, and arises from the fact that those devices don't understand > the 6-byte SCSI READ command. You can add a quirk entry to > src/sys/cam/scsi_da.c (refer to quirk entries that have DA_Q_NO_6_BYTE). Thankyou very much! It works. Very cool indeed. # mount -t msdos /dev/da2s1 /mnt # df -k /mnt Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da2s1 63718 4 63714 0% /mnt This is with the following patch applied to 4.5-RELEASE: --- src/sys/cam/scsi/scsi_da.c.orig Mon Jan 14 10:25:43 2002 +++ src/sys/cam/scsi/scsi_da.c Thu Feb 7 22:07:33 2002 @@ -345,6 +345,14 @@ */ {T_DIRECT, SIP_MEDIA_REMOVABLE, "DIVA USB", "Media Reader","*"}, /*quirks*/ DA_Q_NO_6_BYTE + }, + { + /* + * Fujitsu-Siemens Memorybird. + * Doesn't work correctly with 6 byte reads/writes. + */ + {T_DIRECT, SIP_MEDIA_REMOVABLE, "Fujitsu", "Memorybird", "*"}, + /*quirks*/ DA_Q_NO_6_BYTE } }; I've submitted a PR accordingly, it's kern/34712. Can someone please commit it? Thanks! Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 7 15:54:39 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id 5D1C437B41A; Thu, 7 Feb 2002 15:54:32 -0800 (PST) Received: from pool0339.cvx22-bradley.dialup.earthlink.net ([209.179.199.84] helo=mindspring.com) by albatross.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16YyMw-00059O-00; Thu, 07 Feb 2002 15:54:23 -0800 Message-ID: <3C63133A.CF411A74@mindspring.com> Date: Thu, 07 Feb 2002 15:52:26 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Eugene M. Kim" Cc: Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks References: <200202072046.g17KkSM05459@lurza.secnetix.de> <20020207125449.A9620@alicia.nttmcl.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org "Eugene M. Kim" wrote: > > This is a common problem of most umass devices that implements BBB > protocol, and arises from the fact that those devices don't understand > the 6-byte SCSI READ command. You can add a quirk entry to > src/sys/cam/scsi_da.c (refer to quirk entries that have DA_Q_NO_6_BYTE). > > IIRC this problem is being addressed at a more fundamental level on > -current, by adding a 6-byte-to-10-byte READ command translator > somewhere in the abstraction layer. Could this be "auto-quirked"? It seems to me that you should be able to add the quirk flag to the device instance after the first failure... Unfortunately, I don't have one of these toys, so he'll have to do the code himself. 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 7 15:57:52 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id BBBA037B405; Thu, 7 Feb 2002 15:57:47 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id C2CA9410; Thu, 7 Feb 2002 23:57:46 +0000 (GMT) Date: Thu, 7 Feb 2002 23:57:46 +0000 From: Josef Karthauser To: Terry Lambert Cc: "Eugene M. Kim" , Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks Message-ID: <20020207235746.E46984@genius.tao.org.uk> References: <200202072046.g17KkSM05459@lurza.secnetix.de> <20020207125449.A9620@alicia.nttmcl.com> <3C63133A.CF411A74@mindspring.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="UnaWdueM1EBWVRzC" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C63133A.CF411A74@mindspring.com>; from tlambert2@mindspring.com on Thu, Feb 07, 2002 at 03:52:26PM -0800 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --UnaWdueM1EBWVRzC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 07, 2002 at 03:52:26PM -0800, Terry Lambert wrote: > >=20 > > IIRC this problem is being addressed at a more fundamental level on > > -current, by adding a 6-byte-to-10-byte READ command translator > > somewhere in the abstraction layer. >=20 > Could this be "auto-quirked"? >=20 As in, try a 6 byte command, and if that fails try a 10 byte command instead? Unfortunately although I'm maintaining USB in -current, I don't have a complete in depth understanding of the code yet. :( I'm mainly trying to fix my problems by taking from NetBSD. Joe --UnaWdueM1EBWVRzC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjxjFHoACgkQXVIcjOaxUBYRcgCgtwLd0OsXPbxbwBQYKblFEWVD Db4AoIjORl8hdZuOF6YKiX0SwvThVwXC =9+QE -----END PGP SIGNATURE----- --UnaWdueM1EBWVRzC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 7 15:59:11 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from www2.att.ne.jp (www2.att.ne.jp [165.76.0.163]) by hub.freebsd.org (Postfix) with ESMTP id 9658337B405 for ; Thu, 7 Feb 2002 15:59:04 -0800 (PST) Received: (from www@localhost) by www2.att.ne.jp (8.8.8+Spin/3.6W-JENS-stand2(09/27/01)) id IAA05741; Fri, 8 Feb 2002 08:59:03 +0900 (JST) Date: Fri, 8 Feb 2002 08:59:03 +0900 (JST) From: hiroyu-y@tkc.att.ne.jp Message-Id: <200202072359.IAA05741@www2.att.ne.jp> X-Authentication-Warning: www2.att.ne.jp: www set sender to hiroyu-y@tkc.att.ne.jp using -f To: hardware@freebsd.org Reply-To: hiroyu-y@tkc.att.ne.jp Content-Type: text/plain; charset="iso-2022-jp" Subject: 4.5 release, problem with K6 cpus ? Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi all. I happen to own machine with K-6II & K6-III both on ASUS SP-98N. When I was runnig 4.4 RELEASE on both machine rock stable, but after I've CVSup to 4.5 RELEASE, it became unstable. Worst was on K6-III.sshd will not execute given me bus error. ssh client will also not connect to remote sshd given me buserror. On K6-II machine, I couldn't compile the kernel, given me kernel panic. Has anybody out there had luck running stable K-6II & K6-III cpu with 4.5 RELEASE? #I've been using them as router and couldn't be offline for long time #so they've rolled back to 4.4 and been fine again. Regards. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 7 16: 1:11 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from pr93.lublin.sdi.tpnet.pl (pr93.lublin.sdi.tpnet.pl [217.97.36.93]) by hub.freebsd.org (Postfix) with ESMTP id 5886737B41A for ; Thu, 7 Feb 2002 16:01:06 -0800 (PST) Received: (from doc@localhost) by pr93.lublin.sdi.tpnet.pl (8.11.6/8.11.6) id g180Ajd09710; Fri, 8 Feb 2002 01:10:45 +0100 (CET) (envelope-from doc@lublin.t1.pl) Date: Fri, 8 Feb 2002 01:10:45 +0100 From: =?iso-8859-2?Q?Micha=B3?= Pasternak To: hiroyu-y@tkc.att.ne.jp Cc: hardware@freebsd.org Subject: Re: 4.5 release, problem with K6 cpus ? Message-ID: <20020208001045.GA9684@lublin.t1.pl> Reply-To: =?iso-8859-2?Q?Micha=B3?= Pasternak References: <200202072359.IAA05741@www2.att.ne.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <200202072359.IAA05741@www2.att.ne.jp> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org hiroyu-y@tkc.att.ne.jp [Fri, Feb 08, 2002 at 08:59:03AM +0900]: > Hi all. > I happen to own machine with K-6II & K6-III both on ASUS SP-98N. > > When I was runnig 4.4 RELEASE on both machine rock stable, but after > I've CVSup to 4.5 RELEASE, it became unstable. What CFLAGS you have in /etc/make.conf? -- ::( Micha³ Pasternak ::( http://lublin.t1.pl ::( +48606570000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 7 16: 3: 5 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from alicia.nttmcl.com (alicia.nttmcl.com [216.69.69.10]) by hub.freebsd.org (Postfix) with ESMTP id 95D6637B400; Thu, 7 Feb 2002 16:03:00 -0800 (PST) Received: (from gene@localhost) by alicia.nttmcl.com (8.10.1/8.10.1) id g1802uV19724; Thu, 7 Feb 2002 16:02:56 -0800 (PST) Date: Thu, 7 Feb 2002 16:02:56 -0800 From: "Eugene M. Kim" To: Terry Lambert Cc: Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks Message-ID: <20020207160256.A19270@alicia.nttmcl.com> References: <200202072046.g17KkSM05459@lurza.secnetix.de> <20020207125449.A9620@alicia.nttmcl.com> <3C63133A.CF411A74@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3C63133A.CF411A74@mindspring.com>; from tlambert2@mindspring.com on Thu, Feb 07, 2002 at 03:52:26PM -0800 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Feb 07, 2002 at 03:52:26PM -0800, Terry Lambert wrote: > > > "Eugene M. Kim" wrote: > > > > This is a common problem of most umass devices that implements BBB > > protocol, and arises from the fact that those devices don't understand > > the 6-byte SCSI READ command. You can add a quirk entry to > > src/sys/cam/scsi_da.c (refer to quirk entries that have DA_Q_NO_6_BYTE). > > > > IIRC this problem is being addressed at a more fundamental level on > > -current, by adding a 6-byte-to-10-byte READ command translator > > somewhere in the abstraction layer. > > Could this be "auto-quirked"? > > It seems to me that you should be able to add the quirk flag > to the device instance after the first failure... > > Unfortunately, I don't have one of these toys, so he'll have > to do the code himself. 8-). The USB development team seems to have something similar to your idea in their mind; see the comment for rev 1.47 of: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/umass.c?f=u&only_with_tag=MAIN&logsort=date It mentions about `da(4) becoming more intelligent about this.' Regards, Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 7 16:17:21 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from www2.att.ne.jp (www2.att.ne.jp [165.76.0.163]) by hub.freebsd.org (Postfix) with ESMTP id CFBF237B41B for ; Thu, 7 Feb 2002 16:17:17 -0800 (PST) Received: (from www@localhost) by www2.att.ne.jp (8.8.8+Spin/3.6W-JENS-stand2(09/27/01)) id JAA10207; Fri, 8 Feb 2002 09:17:17 +0900 (JST) Date: Fri, 8 Feb 2002 09:17:17 +0900 (JST) From: hiroyu-y@tkc.att.ne.jp Message-Id: <200202080017.JAA10207@www2.att.ne.jp> X-Authentication-Warning: www2.att.ne.jp: www set sender to hiroyu-y@tkc.att.ne.jp using -f To: hardware@freebsd.org Reply-To: hiroyu-y@tkc.att.ne.jp Content-Type: text/plain; charset="iso-2022-jp" Subject: Re: 4.5 release, problem with K6 cpus ? Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, =?iso-8859-2?Q?Micha=B3?= Pasternak wrote > What CFLAGS you have in /etc/make.conf? No CFLAGS set on /etc/make.conf & also no CFLAGS eviroment value set. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 7 16:42: 9 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from harrier.prod.itd.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by hub.freebsd.org (Postfix) with ESMTP id 9202137B41A; Thu, 7 Feb 2002 16:42:02 -0800 (PST) Received: from pool0339.cvx22-bradley.dialup.earthlink.net ([209.179.199.84] helo=mindspring.com) by harrier.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Yz6u-00055G-00; Thu, 07 Feb 2002 16:41:53 -0800 Message-ID: <3C631E45.2EAAA4CF@mindspring.com> Date: Thu, 07 Feb 2002 16:39:33 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Josef Karthauser Cc: "Eugene M. Kim" , Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks References: <200202072046.g17KkSM05459@lurza.secnetix.de> <20020207125449.A9620@alicia.nttmcl.com> <3C63133A.CF411A74@mindspring.com> <20020207235746.E46984@genius.tao.org.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Josef Karthauser wrote: > On Thu, Feb 07, 2002 at 03:52:26PM -0800, Terry Lambert wrote: > > > IIRC this problem is being addressed at a more fundamental level on > > > -current, by adding a 6-byte-to-10-byte READ command translator > > > somewhere in the abstraction layer. > > > > Could this be "auto-quirked"? > > As in, try a 6 byte command, and if that fails try a 10 byte command > instead? As in, if it fails to reset, then sc->softc->minimum_cmd_size = 10; printf( "auto-quirking mumble foo\n"); It would let most of the existing quirks table go away, but would require additional retries. The cool thing is that it would all happen in the error path, so, other than increasing the number of retries to cause it to engage by itself without having to try the disklabel 3 times, which is also failure mode stuff, it adds no overhead to working devices, and makes non-working ones work with the overhead they have to have anyway. > Unfortunately although I'm maintaining USB in -current, I don't have a > complete in depth understanding of the code yet. :( I'm mainly trying > to fix my problems by taking from NetBSD. I took a look at the code. I have to say it's opaque. It makes a better door than a window. ;-). I haven't figured out how to turn a struct umass_softc * into a struct da_softc *, or I would have given you an ugly little patch against an older version of FreeBSD to try. 8-p. I think someone with one of these things, or with a quirky one with the DA_Q_NO_6_BYTE removed from the quirks table, is going to have to set CAM_DEBUG on big-time, and then see where the reset error falls out, add a static fail counter to that place in the code, and then if it fails and the fail counter >= 3 (for example), reset the minimum command size to 10. That should "just work". If the reset is retried enough times, you could get rid of the quirks entries that existed solely for this quirk; I think that a 6 byte commands not supported: changing to 10 byte commands message on the console is probably acceptable "noise" in trade for getting rid of it, and supporting future devices with the same problem, without needing to "quirk" them. I think DA_Q_NO_SYNC_CACHE might be handleable the same way, which would get rid of all the quirk entries, and maybe the need for a quirk table at all (it looks like the daclose/dadump/dashutdown sync code could be static'ed and shared, as well). Maybe this is a CAM-specific thing, and shouldn't be handled in the USB code at all (you won't know until you see a quirked device failure with the CAM debug, or you write the CAM code to tape and run it through your dental fillings or otherwise load it into your head). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 7 16:48:45 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from harrier.prod.itd.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by hub.freebsd.org (Postfix) with ESMTP id 24EFF37B41E; Thu, 7 Feb 2002 16:48:36 -0800 (PST) Received: from pool0339.cvx22-bradley.dialup.earthlink.net ([209.179.199.84] helo=mindspring.com) by harrier.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16YzDE-0006Ng-00; Thu, 07 Feb 2002 16:48:26 -0800 Message-ID: <3C631FD9.AABA00B4@mindspring.com> Date: Thu, 07 Feb 2002 16:46:17 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Eugene M. Kim" Cc: Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks References: <200202072046.g17KkSM05459@lurza.secnetix.de> <20020207125449.A9620@alicia.nttmcl.com> <3C63133A.CF411A74@mindspring.com> <20020207160256.A19270@alicia.nttmcl.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org "Eugene M. Kim" wrote: > The USB development team seems to have something similar to your idea in > their mind; see the comment for rev 1.47 of: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/umass.c?f=u&only_with_tag=MAIN&logsort=date > > It mentions about `da(4) becoming more intelligent about this.' See my other posting. It's definitely a CAM thing, not a USB thing, and the handling should be automatic, with no quirks table at all. The USB code, though, then has a responsibility to retry more times, so that the failure triggers the workaround, and the with the workaround in place, the operation then succeeds transparently. I don't think this is universal, though, since I can't see this approach working for a CD burner failure which might render something unrecoverable, but I have yet to see a place it would fail. I think the person with the problem needs to turn on the CAM debugging, or a CAM-head needs to become involved. The workaround works, for now, but it's frustrating, knowing that the next time anyone OEMs the same hardware and changes the ID, it will have to grow another quirk. 8-(. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 7 18:46: 6 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id 7E57637B427; Thu, 7 Feb 2002 18:45:42 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id B903B314; Fri, 8 Feb 2002 02:45:40 +0000 (GMT) Date: Fri, 8 Feb 2002 02:45:40 +0000 From: Josef Karthauser To: Terry Lambert Cc: "Eugene M. Kim" , Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks Message-ID: <20020208024540.B50352@genius.tao.org.uk> References: <200202072046.g17KkSM05459@lurza.secnetix.de> <20020207125449.A9620@alicia.nttmcl.com> <3C63133A.CF411A74@mindspring.com> <20020207160256.A19270@alicia.nttmcl.com> <3C631FD9.AABA00B4@mindspring.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="CdrF4e02JqNVZeln" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C631FD9.AABA00B4@mindspring.com>; from tlambert2@mindspring.com on Thu, Feb 07, 2002 at 04:46:17PM -0800 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --CdrF4e02JqNVZeln Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Feb 07, 2002 at 04:46:17PM -0800, Terry Lambert wrote: > I think the person with the problem needs to turn on the > CAM debugging, or a CAM-head needs to become involved. The > workaround works, for now, but it's frustrating, knowing > that the next time anyone OEMs the same hardware and changes > the ID, it will have to grow another quirk. 8-(. It's also a pain to maintain. Joe --CdrF4e02JqNVZeln Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjxjO9QACgkQXVIcjOaxUBZgMACfUM8XSVF94Q3IzlNc/fYVLuZD cVYAnj4FQXsfICv3CY3tB3Dd3QHWjmE2 =tShr -----END PGP SIGNATURE----- --CdrF4e02JqNVZeln-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 8 6:37:49 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from web13604.mail.yahoo.com (web13604.mail.yahoo.com [216.136.175.115]) by hub.freebsd.org (Postfix) with SMTP id 1E65E37B417 for ; Fri, 8 Feb 2002 06:37:37 -0800 (PST) Message-ID: <20020208143736.35672.qmail@web13604.mail.yahoo.com> Received: from [193.110.209.122] by web13604.mail.yahoo.com via HTTP; Fri, 08 Feb 2002 06:37:36 PST Date: Fri, 8 Feb 2002 06:37:36 -0800 (PST) From: Veysel Koybasi Subject: USB Keyboard... To: freebsd-hardware@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi. I have a problem with my USB keyboard. When I tried to install FreeBSD 4.4 it stops loading when choises about kernel configuration are come. I tried to install it using another computer with ps2 keyboard an I installed it to my hdd and when I connect my hdd to my computer and try to boot freebsd 4.4 it boots but my keyboard does not work again althoug usbd is started. When I disconnect my keyboard and again reconnect it realizes that the keyboard is disconnected and attached again but it seems something is wrong because again I cant write anything. How can I manage with this problem is there any ideas. Thanks for all replys from now on. __________________________________________________ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 8 8:29: 8 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from deckard.addix.net (deckard.addix.net [194.64.167.10]) by hub.freebsd.org (Postfix) with ESMTP id 3625937B488 for ; Fri, 8 Feb 2002 08:28:42 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by deckard.addix.net (8.11.6/8.11.6) with ESMTP id g18GPai81307; Fri, 8 Feb 2002 17:25:36 +0100 (CET) (envelope-from olaf@nightfire.de) Date: Fri, 8 Feb 2002 17:25:36 +0100 (CET) From: Olaf Hoyer To: Cc: Subject: Re: 4.5 release, problem with K6 cpus ? In-Reply-To: <200202072359.IAA05741@www2.att.ne.jp> Message-ID: <20020208171428.I81293-100000@deckard.addix.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 8 Feb 2002 hiroyu-y@tkc.att.ne.jp wrote: > > > Hi all. > I happen to own machine with K-6II & K6-III both on ASUS SP-98N. > > When I was runnig 4.4 RELEASE on both machine rock stable, but after > I've CVSup to 4.5 RELEASE, it became unstable. > > Worst was on K6-III.sshd will not execute given me bus error. > ssh client will also not connect to remote sshd given me buserror. > On K6-II machine, I couldn't compile the kernel, given me kernel panic. > > Has anybody out there had luck running stable K-6II & K6-III cpu with > 4.5 RELEASE? Hi! Well, just played with an old machine here in my offic, that is intended to be used as a mp3-server for internal use. ASUS P5A (ALI chip), 64 MB PC66, PCI ATI vid card (el cheapo) Intel EEPro 10/100 (82557) Adaptec 2940UW: narrow channel: Teac CDR58 as CDrom, on the wide channel a 9 gig barracuda, originally LVD. Hmm, the system came up, but within installing I had lots of probs with the controller, which reset some times and finally hung with the big transfers whilst installin ports collection... Ok, took a 68-50 pin adapter, and connected the drive to the narrow chain. Also told the 2940UW to only use narrow negotiation... after that, I discovered that the CPU was clocked to 100MHz FSB, whilst a colleague told me that it should have been a 333->66MHz FSB. So clocked down the CPU to 66*3,5=233 MHz, and it is running fine I installed 4.5-R from CD, and since then I only had the box transferring some 5 GB data via ftp in one big swoop, and the system remained stable. I only had the box running for a few hours, and it performed well, but to me my other (ok, Intel based with HX/BX chipsets) seemed more happy with 4.3 and 4.4, but this also might be due to different mainboards. HTH Olaf Hoyer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 8 9:25:11 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id D2F4237B41F; Fri, 8 Feb 2002 09:24:57 -0800 (PST) Received: (from olli@localhost) by lurza.secnetix.de (8.11.6/8.11.6) id g18HOlZ40937; Fri, 8 Feb 2002 18:24:47 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) From: Oliver Fromme Message-Id: <200202081724.g18HOlZ40937@lurza.secnetix.de> Subject: Re: USB "Memorybird" quirks To: tlambert2@mindspring.com (Terry Lambert) Date: Fri, 8 Feb 2002 18:24:47 +0100 (CET) Cc: gene@nttmcl.com (Eugene M. Kim), olli@secnetix.de (Oliver Fromme), hardware@freebsd.org (FreeBSD Hardware Mailing List), hackers@freebsd.org (FreeBSD Hackers Mailing List) In-Reply-To: <3C63133A.CF411A74@mindspring.com> from "Terry Lambert" at Feb 07, 2002 03:52:26 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Terry Lambert wrote: > "Eugene M. Kim" wrote: > > This is a common problem of most umass devices that implements BBB > > protocol, and arises from the fact that those devices don't understand > > the 6-byte SCSI READ command. You can add a quirk entry to > > src/sys/cam/scsi_da.c (refer to quirk entries that have DA_Q_NO_6_BYTE). > > > > IIRC this problem is being addressed at a more fundamental level on > > -current, by adding a 6-byte-to-10-byte READ command translator > > somewhere in the abstraction layer. > > Could this be "auto-quirked"? > > It seems to me that you should be able to add the quirk flag > to the device instance after the first failure... That's what I thought, too. It seems to me that umass_scsi_transform() in umass.c is the place intended for this kind of things. After the first failure (which is detected in umass_bbb_state()), a flag (quirk) should be set in the softc, and afterwards umass_scsi_transform should translate 6-byte commands to 10-byte commands. Doesn't sound too complicated to me. Or am I totally wrong? Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 8 9:32:11 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from ra.upan.org (ra.upan.org [204.107.76.19]) by hub.freebsd.org (Postfix) with ESMTP id 685FA37B41C for ; Fri, 8 Feb 2002 09:32:08 -0800 (PST) Received: from ocsinternet.com ([10.0.0.102]) by ra.upan.org (8.11.6/8.11.6) with ESMTP id g18HVv190035 for ; Fri, 8 Feb 2002 12:32:01 -0500 (EST) (envelope-from mikel@ocsinternet.com) Message-ID: <3C640B6E.6090302@ocsinternet.com> Date: Fri, 08 Feb 2002 12:31:26 -0500 From: Mikel King User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 X-Accept-Language: en-us MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: adaptec 29160 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi all, I am researching a storage project that will use an external raid like the Flashdisk OpenRaid and found that the 29160 card is recommended. has anyone used this card. Are there any know pitfalls? Cheers, Mikel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 8 9:48:49 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id DF8F137B41A for ; Fri, 8 Feb 2002 09:48:46 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g18HmiR22311; Fri, 8 Feb 2002 10:48:44 -0700 (MST) (envelope-from ken) Date: Fri, 8 Feb 2002 10:48:43 -0700 From: "Kenneth D. Merry" To: Mikel King Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: adaptec 29160 Message-ID: <20020208104843.A22249@panzer.kdm.org> References: <3C640B6E.6090302@ocsinternet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3C640B6E.6090302@ocsinternet.com>; from mikel@ocsinternet.com on Fri, Feb 08, 2002 at 12:31:26PM -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, Feb 08, 2002 at 12:31:26 -0500, Mikel King wrote: > Hi all, > > I am researching a storage project that will use an external raid > like the Flashdisk OpenRaid and found that the 29160 card is > recommended. has anyone used this card. Are there any know pitfalls? It work fine, and is well supported. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 8 10: 1:23 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by hub.freebsd.org (Postfix) with ESMTP id 3812437B41A; Fri, 8 Feb 2002 10:00:45 -0800 (PST) Received: from [192.168.1.129] (212.129.11.210) by mail.libertysurf.net (5.1.053) id 3C633FD40002C6AB; Fri, 8 Feb 2002 19:00:20 +0100 Date: Thu, 7 Feb 2002 20:00:24 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: To: Josef Karthauser Cc: Terry Lambert , "Eugene M. Kim" , Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks In-Reply-To: <20020207235746.E46984@genius.tao.org.uk> Message-ID: <20020207193911.U1513-100000@gerard> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 7 Feb 2002, Josef Karthauser wrote: > On Thu, Feb 07, 2002 at 03:52:26PM -0800, Terry Lambert wrote: > > > > > > IIRC this problem is being addressed at a more fundamental level on > > > -current, by adding a 6-byte-to-10-byte READ command translator > > > somewhere in the abstraction layer. > > > > Could this be "auto-quirked"? > > > > As in, try a 6 byte command, and if that fails try a 10 byte command > instead? > > Unfortunately although I'm maintaining USB in -current, I don't have a > complete in depth understanding of the code yet. :( I'm mainly trying > to fix my problems by taking from NetBSD. A couple of READ/WRITE 6 byte commands are still mandatory for SCSI block devices in order to accomodate softwares as boot software for example that may not be upgradable on systems still in use. Softwares that are maintained should no longer use 6 byte commands, but use the 10 byte commands replacement (for years...). So, unless we want to accomodate applications that still may send 6 byte commands through passthrough driver, no translator should be needed. Just make class drivers use 10 byte commands instead. I donnot know about USB in details. But since USB is a recent technology USB devices should not be required to support READ/WRITE 6 byte commands. OTOH, using 6 byte READ/WRITE commands is very restrictive if we ever want to implemement kind of trustable disk write caching support since they do not allow to selectively force media access (this is achieved by the FUA bit in >=3D 10 byte READ/WRITE command). As a result, no device should be quirked nowadays as failing READ/WRITE 6 byte commands. Just maintained softwares should get rid of those commands asap. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 8 10:11:51 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id 9647437B404; Fri, 8 Feb 2002 10:11:39 -0800 (PST) Received: from pool0031.cvx22-bradley.dialup.earthlink.net ([209.179.198.31] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16ZFUb-0002PY-00; Fri, 08 Feb 2002 10:11:28 -0800 Message-ID: <3C641347.ADE06FAD@mindspring.com> Date: Fri, 08 Feb 2002 10:04:55 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Oliver Fromme Cc: "Eugene M. Kim" , Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks References: <200202081724.g18HOlZ40937@lurza.secnetix.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Oliver Fromme wrote: > > Could this be "auto-quirked"? [ ... ] > It seems to me that umass_scsi_transform() in umass.c is > the place intended for this kind of things. After the > first failure (which is detected in umass_bbb_state()), > a flag (quirk) should be set in the softc, and afterwards > umass_scsi_transform should translate 6-byte commands to > 10-byte commands. Doesn't sound too complicated to me. After looking at the code in more detail, then puzzling and puzzling 'til mu puzzler was sore, then sitting back down, and puzzling some more... It very obviously needs to be generic in the CAM layer in the da handler, since it's applicable to all devices in the quirks table, not just the USB devices. It still needs a failuter trace from the CAM_DEBUG stuff. Strange as it may seem, I look through quirks lists before I buy hardware, and if it has a quirk, I don't buy it. So I'm not in a position to run the test, or test a fix. The USB stuff still needs to retry more than it does, though, if those logs were an accurate retry count, or the fix of automatically moving from 6->10 byte commands won't work transparently, and you'll end up having to do the disklabel a couple of times before it sticks. This is pretty unacceptable behaviour (it violates POLA all to heck). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 8 10:38:13 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id 1489637B419; Fri, 8 Feb 2002 10:38:05 -0800 (PST) Received: from pool0031.cvx22-bradley.dialup.earthlink.net ([209.179.198.31] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16ZFu6-0005UD-00; Fri, 08 Feb 2002 10:37:48 -0800 Message-ID: <3C64196C.CC0318FD@mindspring.com> Date: Fri, 08 Feb 2002 10:31:08 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: =?iso-8859-1?Q?G=E9rard?= Roudier Cc: Josef Karthauser , "Eugene M. Kim" , Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks References: <20020207193911.U1513-100000@gerard> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org G=E9rard Roudier wrote: > A couple of READ/WRITE 6 byte commands are still mandatory for SCSI blo= ck > devices in order to accomodate softwares as boot software for example t= hat > may not be upgradable on systems still in use. Not a real problem, since if the device doesn't support the 5 byte commands, it's not booting with the legacy system software anyway, since you can't boot legacy stuff on it. > Softwares that are > maintained should no longer use 6 byte commands, but use the 10 byte > commands replacement (for years...). This I don't understand. FreeBSD appears to have a preference for the 6 byte commands in the drivers, which are only used after boot. Further, it makes sense that you'd prefer 6 byte if you could, since it makes your commands 60% smaller, which should make them faster. > So, unless we want to accomodate applications that still may send 6 byt= e > commands through passthrough driver, no translator should be needed. Ju= st > make class drivers use 10 byte commands instead. There has to be a reason that FreeBSD has a preference for 6 bytes in the CAM code... ?!? > OTOH, using 6 byte READ/WRITE commands is very restrictive if we ever w= ant > to implemement kind of trustable disk write caching support since they = do > not allow to selectively force media access (this is achieved by the FU= A > bit in >=3D 10 byte READ/WRITE command). > = > As a result, no device should be quirked nowadays as failing READ/WRITE= 6 > byte commands. Just maintained softwares should get rid of those comman= ds > asap. It sounds like devices that only support 6 byte commands are the ones that need quirked? In other words, you're just reversing the default and the fallback positions. I think auto-detecting the quirk is still a good bet, even in the 6 byte only case, just as it would have been in the 10 byte only case. Thanks for the info on what's supposed to be done going forward, though. If there's no performance issue with 10 byte commands, inverting the default and the quirk handling in the failure case seems to be the right thing to do. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 8 10:59:48 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from alicia.nttmcl.com (alicia.nttmcl.com [216.69.69.10]) by hub.freebsd.org (Postfix) with ESMTP id 6000E37B400; Fri, 8 Feb 2002 10:59:40 -0800 (PST) Received: (from gene@localhost) by alicia.nttmcl.com (8.10.1/8.10.1) id g18Ix7M07563; Fri, 8 Feb 2002 10:59:07 -0800 (PST) Date: Fri, 8 Feb 2002 10:59:07 -0800 From: "Eugene M. Kim" To: Terry Lambert Cc: G?rard Roudier , Josef Karthauser , Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks Message-ID: <20020208105907.A20197@alicia.nttmcl.com> References: <20020207193911.U1513-100000@gerard> <3C64196C.CC0318FD@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2i In-Reply-To: <3C64196C.CC0318FD@mindspring.com>; from tlambert2@mindspring.com on Fri, Feb 08, 2002 at 10:31:08AM -0800 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org There is hardly a performance issue about 10-byte READ, considering the size of a whole transaction (command + transfer) is at least as large as a disk sector (512 bytes on most modern drives); a four-byte difference is almost nothing here. IMHO the best way is to `try a 10-byte READ first, and if it fails then fallback to a 6-byte READ.' Eugene On Fri, Feb 08, 2002 at 10:31:08AM -0800, Terry Lambert wrote: > > > Gérard Roudier wrote: > > A couple of READ/WRITE 6 byte commands are still mandatory for SCSI block > > devices in order to accomodate softwares as boot software for example that > > may not be upgradable on systems still in use. > > Not a real problem, since if the device doesn't support > the 5 byte commands, it's not booting with the legacy > system software anyway, since you can't boot legacy stuff > on it. > > > > Softwares that are > > maintained should no longer use 6 byte commands, but use the 10 byte > > commands replacement (for years...). > > This I don't understand. FreeBSD appears to have a > preference for the 6 byte commands in the drivers, > which are only used after boot. > > Further, it makes sense that you'd prefer 6 byte if > you could, since it makes your commands 60% smaller, > which should make them faster. > > > > So, unless we want to accomodate applications that still may send 6 byte > > commands through passthrough driver, no translator should be needed. Just > > make class drivers use 10 byte commands instead. > > There has to be a reason that FreeBSD has a preference > for 6 bytes in the CAM code... ?!? > > > > OTOH, using 6 byte READ/WRITE commands is very restrictive if we ever want > > to implemement kind of trustable disk write caching support since they do > > not allow to selectively force media access (this is achieved by the FUA > > bit in >= 10 byte READ/WRITE command). > > > > As a result, no device should be quirked nowadays as failing READ/WRITE 6 > > byte commands. Just maintained softwares should get rid of those commands > > asap. > > It sounds like devices that only support 6 byte commands > are the ones that need quirked? > > In other words, you're just reversing the default and > the fallback positions. > > I think auto-detecting the quirk is still a good bet, > even in the 6 byte only case, just as it would have > been in the 10 byte only case. > > Thanks for the info on what's supposed to be done going > forward, though. If there's no performance issue with > 10 byte commands, inverting the default and the quirk > handling in the failure case seems to be the right thing > to do. > > -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 8 11:36:38 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by hub.freebsd.org (Postfix) with ESMTP id 730EC37B41C; Fri, 8 Feb 2002 11:36:30 -0800 (PST) Received: from [192.168.1.129] (212.129.11.210) by mail.libertysurf.net (5.1.053) id 3C633EE70002F95C; Fri, 8 Feb 2002 20:36:07 +0100 Date: Thu, 7 Feb 2002 21:36:11 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: To: Terry Lambert Cc: Josef Karthauser , "Eugene M. Kim" , Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks In-Reply-To: <3C64196C.CC0318FD@mindspring.com> Message-ID: <20020207205736.W1763-100000@gerard> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 8 Feb 2002, Terry Lambert wrote: > G=E9rard Roudier wrote: > > A couple of READ/WRITE 6 byte commands are still mandatory for SCSI blo= ck > > devices in order to accomodate softwares as boot software for example t= hat > > may not be upgradable on systems still in use. > > Not a real problem, since if the device doesn't support > the 5 byte commands, it's not booting with the legacy > system software anyway, since you can't boot legacy stuff > on it. > > > > Softwares that are > > maintained should no longer use 6 byte commands, but use the 10 byte > > commands replacement (for years...). > > This I don't understand. FreeBSD appears to have a > preference for the 6 byte commands in the drivers, > which are only used after boot. > > Further, it makes sense that you'd prefer 6 byte if > you could, since it makes your commands 60% smaller, > which should make them faster. The gain is probably no more that 1 microsecond and only applies to the first GB of hard disks (Logical Block Address is 21 bits). There are tons of other places where optimizations are more relevant than sticking with such a questionnable 6 byte commands preference in my humble opinion. Note that not only FreeBSD seems to want not to change this. > > So, unless we want to accomodate applications that still may send 6 byt= e > > commands through passthrough driver, no translator should be needed. Ju= st > > make class drivers use 10 byte commands instead. > > There has to be a reason that FreeBSD has a preference > for 6 bytes in the CAM code... ?!? The main reason could well be that I'm not the maintainer of this code. :-) > > OTOH, using 6 byte READ/WRITE commands is very restrictive if we ever w= ant > > to implemement kind of trustable disk write caching support since they = do > > not allow to selectively force media access (this is achieved by the FU= A > > bit in >=3D 10 byte READ/WRITE command). > > > > As a result, no device should be quirked nowadays as failing READ/WRITE= 6 > > byte commands. Just maintained softwares should get rid of those comman= ds > > asap. > > It sounds like devices that only support 6 byte commands > are the ones that need quirked? Speaking about direct access devices, may-be none has to be so or just a few number of them: - SCSI-1 devices only knew about READ(6)/WRITE(6) commands. - SCSI-2 made READ(10) mandatory, WRITE(10) being optional but just because read-only devices exist. Supporting READ(10) but only WRITE(6) for a read/write device looking like a great strangeness to me. This should be checked for other device types... > In other words, you're just reversing the default and > the fallback positions. > > I think auto-detecting the quirk is still a good bet, > even in the 6 byte only case, just as it would have > been in the 10 byte only case. May-be just applying simple rules based on [SCSI version | SCSI plagiarism (ex: USDB, ATAPI,...)] + Device type should avoid autodetection in most situations. > Thanks for the info on what's supposed to be done going > forward, though. If there's no performance issue with > 10 byte commands, inverting the default and the quirk > handling in the failure case seems to be the right thing > to do. The performance issue is certainly negligible (~ 1 micro-second), and as I wrote above it only applies to the first GB of disks. (Additionnaly, the tranfer length is limited to 256 sectors) So, unless we want to advertise about best support for 1 GB hard disks, better not to mix disk performance issue with 6 byte command preference, in my humble opinion. :-) G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 8 17:59: 0 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from neo.spbnit.ru (mail.spbnit.ru [212.48.192.115]) by hub.freebsd.org (Postfix) with ESMTP id 8382837B416 for ; Fri, 8 Feb 2002 17:58:56 -0800 (PST) Received: from default (ppp-18.pool-121.spbnit.ru [212.48.199.18]) by neo.spbnit.ru (8.9.3+mPOP/8.9.3) with ESMTP id EAA65187 for ; Sat, 9 Feb 2002 04:58:36 +0300 (MSK) Message-Id: <200202090158.EAA65187@neo.spbnit.ru> From: "Vladislav V. Anikiev" To: Subject: Re: Re: MAC address Date: Sat, 9 Feb 2002 05:19:25 +0300 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1157 MIME-Version: 1.0 Content-Type: text/plain; charset=Default Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Everyone OK, I've understood everything, which were written before. Thank you very much. Vladislav >Network Interface Card >On Sat, 9 Feb 2002, Vladislav V. Anikiev wrote: >> >> Hello Brian, >> >> The MAC address - I meen The Media Access Control address (i.e., >ethernet >> hardware address, not IP address). I want to use the default hardware >(not >> current physical ) address in my license management software. >> >> Why did you write: "Depending on the NIC". The NIC means Network >> Information Center. Doesn't it ? >> >> Vladislav >> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 8 19: 3:50 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from snipe.prod.itd.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id CDC7437B405; Fri, 8 Feb 2002 19:03:43 -0800 (PST) Received: from pool0053.cvx21-bradley.dialup.earthlink.net ([209.179.192.53] helo=mindspring.com) by snipe.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16ZNnC-00078N-00; Fri, 08 Feb 2002 19:03:15 -0800 Message-ID: <3C648F73.1663C5E9@mindspring.com> Date: Fri, 08 Feb 2002 18:54:43 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: =?iso-8859-1?Q?G=E9rard?= Roudier Cc: Josef Karthauser , "Eugene M. Kim" , Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks References: <20020207205736.W1763-100000@gerard> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org G=E9rard Roudier wrote: > The performance issue is certainly negligible (~ 1 micro-second), and a= s I > wrote above it only applies to the first GB of disks. (Additionnaly, th= e > tranfer length is limited to 256 sectors) > = > So, unless we want to advertise about best support for 1 GB hard disks,= > better not to mix disk performance issue with 6 byte command preference= , > in my humble opinion. :-) You want to create some patches? I'm not really a CAM-head. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 8 19:25:32 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from adsl-63-198-35-122.dsl.snfc21.pacbell.net (adsl-63-198-35-122.dsl.snfc21.pacbell.net [63.198.35.122]) by hub.freebsd.org (Postfix) with ESMTP id 812D537B421 for ; Fri, 8 Feb 2002 19:25:20 -0800 (PST) Received: from lbl.gov (localhost.pacbell.net [127.0.0.1]) by spode.pacbell.net (8.11.6/8.11.6) with ESMTP id g180wLd00630; Thu, 7 Feb 2002 16:58:22 -0800 (PST) (envelope-from j_guojun@lbl.gov) Message-ID: <3C6322AD.B981EEB2@lbl.gov> Date: Thu, 07 Feb 2002 16:58:21 -0800 From: "Jin Guojun[ITG]" X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.5-RELEASE i386) X-Accept-Language: zh, zh-CN, en MIME-Version: 1.0 To: hiroyu-y@tkc.att.ne.jp Cc: hardware@FreeBSD.ORG Subject: Re: 4.5 release, problem with K6 cpus ? References: <200202072359.IAA05741@www2.att.ne.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org hiroyu-y@tkc.att.ne.jp wrote: > > Hi all. > I happen to own machine with K-6II & K6-III both on ASUS SP-98N. > > When I was runnig 4.4 RELEASE on both machine rock stable, but after > I've CVSup to 4.5 RELEASE, it became unstable. > > Worst was on K6-III.sshd will not execute given me bus error. > ssh client will also not connect to remote sshd given me buserror. > On K6-II machine, I couldn't compile the kernel, given me kernel panic. > > Has anybody out there had luck running stable K-6II & K6-III cpu with > 4.5 RELEASE? > > #I've been using them as router and couldn't be offline for long time > #so they've rolled back to 4.4 and been fine again. I just installed 4.5 on K6-III with ASUS P5A-B, and below is the boot information: FreeBSD 4.5-RELEASE #0: Thu Feb 7 16:33:35 PST 2002 root@vff.pacbell.net:/usr/src/sys/compile/Custom Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D+ Processor (420.00-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x591 Stepping = 1 Features=0x8021bf -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 8 19:49: 6 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with ESMTP id 50AC637B402 for ; Fri, 8 Feb 2002 19:49:00 -0800 (PST) Received: (qmail 14689 invoked from network); 9 Feb 2002 03:48:58 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.90.117.49]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 9 Feb 2002 03:48:58 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020208143736.35672.qmail@web13604.mail.yahoo.com> Date: Fri, 08 Feb 2002 22:48:25 -0500 (EST) From: John Baldwin To: Veysel Koybasi Subject: RE: USB Keyboard... Cc: freebsd-hardware@FreeBSD.org Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 08-Feb-02 Veysel Koybasi wrote: > > > Hi. I have a problem with my USB keyboard. When I > tried to install FreeBSD 4.4 it stops loading when > choises about kernel configuration are come. I tried > to install it using another computer with ps2 keyboard > an I installed it to my hdd and when I connect my hdd > to my computer and try to boot freebsd 4.4 it boots > but my keyboard does not work again althoug usbd is > started. When I disconnect my keyboard and again > reconnect it realizes that the keyboard is > disconnected and attached again but it seems something > is wrong because again I cant write anything. How can > I manage with this problem is there any ideas. Thanks > for all replys from now on. Use kbdcontrol to change the console keyboard to /dev/kbd1. You can create a script that runs at startup time in /usr/local/etc/rc.d to automate this. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 8 19:49:28 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with ESMTP id 598CF37B404 for ; Fri, 8 Feb 2002 19:49:14 -0800 (PST) Received: (qmail 14889 invoked from network); 9 Feb 2002 03:49:13 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.90.117.49]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 9 Feb 2002 03:49:13 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020207193911.U1513-100000@gerard> Date: Fri, 08 Feb 2002 22:49:08 -0500 (EST) From: John Baldwin To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Subject: Re: USB "Memorybird" quirks Cc: FreeBSD Hackers Mailing List , Cc: FreeBSD Hackers Mailing List , FreeBSD Hardware Mailing List , Oliver Fromme , "Eugene M. Kim" , Terry Lambert , Josef Karthauser Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 07-Feb-02 Gérard Roudier wrote: > > On Thu, 7 Feb 2002, Josef Karthauser wrote: > >> On Thu, Feb 07, 2002 at 03:52:26PM -0800, Terry Lambert wrote: >> > > >> > > IIRC this problem is being addressed at a more fundamental level on >> > > -current, by adding a 6-byte-to-10-byte READ command translator >> > > somewhere in the abstraction layer. >> > >> > Could this be "auto-quirked"? >> > >> >> As in, try a 6 byte command, and if that fails try a 10 byte command >> instead? >> >> Unfortunately although I'm maintaining USB in -current, I don't have a >> complete in depth understanding of the code yet. :( I'm mainly trying >> to fix my problems by taking from NetBSD. > > A couple of READ/WRITE 6 byte commands are still mandatory for SCSI block > devices in order to accomodate softwares as boot software for example that > may not be upgradable on systems still in use. Softwares that are > maintained should no longer use 6 byte commands, but use the 10 byte > commands replacement (for years...). Just so you know, I made the umass driver for UFI and ATA translate SCSI 6 byte commands to 10 byte commands. There is a simple function call to do the change if you wish to do this in for the SCSI transforms as well. As far as axeing 6 byte commands all together, I will plead ignorance and defer to the scsi@ list and CAM folks. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Feb 8 22:24: 8 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from swan.prod.itd.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 162E037B41A for ; Fri, 8 Feb 2002 22:24:07 -0800 (PST) Received: from lsanca1-ar3-108-172.elnk.dsl.gtei.net ([4.33.108.172] helo=rne) by swan.prod.itd.earthlink.net with smtp (Exim 3.33 #1) id 16ZQve-0007dl-00 for freebsd-hardware@FreeBSD.ORG; Fri, 08 Feb 2002 22:24:06 -0800 From: "Ronald R. Perez" To: Subject: Date: Fri, 8 Feb 2002 22:24:17 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org auth 5017de9d unsubscribe freebsd-hardware ronaldp76@earthlink.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Feb 9 4:16:55 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id E978537B402; Sat, 9 Feb 2002 04:16:49 -0800 (PST) Received: (from olli@localhost) by lurza.secnetix.de (8.11.6/8.11.6) id g19CGk874726; Sat, 9 Feb 2002 13:16:46 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) From: Oliver Fromme Message-Id: <200202091216.g19CGk874726@lurza.secnetix.de> Subject: Re: USB "Memorybird" quirks To: jhb@FreeBSD.org (John Baldwin) Date: Sat, 9 Feb 2002 13:16:46 +0100 (CET) Cc: groudier@free.fr (=?ISO-8859-1?Q?G=E9rard_Roudier?=), hackers@FreeBSD.org (FreeBSD Hackers Mailing List), hardware@FreeBSD.org (FreeBSD Hardware Mailing List), olli@secnetix.de (Oliver Fromme), gene@nttmcl.com (Eugene M. Kim), tlambert2@mindspring.com (Terry Lambert), joe@tao.org.uk (Josef Karthauser) In-Reply-To: from "John Baldwin" at Feb 08, 2002 10:49:08 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org John Baldwin wrote: > On 07-Feb-02 Gérard Roudier wrote: > > A couple of READ/WRITE 6 byte commands are still mandatory for SCSI block > > devices in order to accomodate softwares as boot software for example that > > may not be upgradable on systems still in use. Softwares that are > > maintained should no longer use 6 byte commands, but use the 10 byte > > commands replacement (for years...). > > Just so you know, I made the umass driver for UFI and ATA translate SCSI > 6 byte commands to 10 byte commands. There is a simple function call to do the > change if you wish to do this in for the SCSI transforms as well. I think that would be a very good idea. The boot software issue is negligible, because there aren't any USB devices you can boot from. Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Feb 9 4:36: 4 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id B263237B421; Sat, 9 Feb 2002 04:35:59 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 651E92F6; Sat, 9 Feb 2002 12:35:58 +0000 (GMT) Date: Sat, 9 Feb 2002 12:35:58 +0000 From: Josef Karthauser To: Oliver Fromme Cc: John Baldwin , =?iso-8859-1?Q?G=E9rard_Roudier?= , FreeBSD Hackers Mailing List , FreeBSD Hardware Mailing List , Oliver Fromme , "Eugene M. Kim" , Terry Lambert Subject: Re: USB "Memorybird" quirks Message-ID: <20020209123558.A81896@genius.tao.org.uk> References: <200202091216.g19CGk874726@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="PNTmBPCT7hxwcZjr" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200202091216.g19CGk874726@lurza.secnetix.de>; from oliver.fromme@secnetix.de on Sat, Feb 09, 2002 at 01:16:46PM +0100 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Feb 09, 2002 at 01:16:46PM +0100, Oliver Fromme wrote: > John Baldwin wrote: > > On 07-Feb-02 G=E9rard Roudier wrote: > > > A couple of READ/WRITE 6 byte commands are still mandatory for SCSI = block > > > devices in order to accomodate softwares as boot software for exampl= e that > > > may not be upgradable on systems still in use. Softwares that are > > > maintained should no longer use 6 byte commands, but use the 10 byte > > > commands replacement (for years...). > >=20 > > Just so you know, I made the umass driver for UFI and ATA translate SC= SI > > 6 byte commands to 10 byte commands. There is a simple function call = to do the > > change if you wish to do this in for the SCSI transforms as well. I'd love the patches if you've got them to hand. Joe --PNTmBPCT7hxwcZjr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjxlF60ACgkQXVIcjOaxUBaBPQCgh4aTu64MnnqXQpK45BCDKRA9 WA4An02hKJBC2vEMQE7xyUex15kH6SO+ =mu+I -----END PGP SIGNATURE----- --PNTmBPCT7hxwcZjr-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Feb 9 7:51:25 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id 4239337B420 for ; Sat, 9 Feb 2002 07:50:52 -0800 (PST) Received: (qmail 16271 invoked from network); 9 Feb 2002 15:50:50 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.91.153.195]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 9 Feb 2002 15:50:50 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020209123558.A81896@genius.tao.org.uk> Date: Sat, 09 Feb 2002 10:50:48 -0500 (EST) From: John Baldwin To: Josef Karthauser Subject: Re: USB "Memorybird" quirks Cc: Terry Lambert , "Eugene M. Kim" , Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List , =?iso-8859-1?Q?G=E9rard_Roudier?= , Oliver Fromme Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 09-Feb-02 Josef Karthauser wrote: > On Sat, Feb 09, 2002 at 01:16:46PM +0100, Oliver Fromme wrote: > >> John Baldwin wrote: >> > On 07-Feb-02 Gérard Roudier wrote: >> > > A couple of READ/WRITE 6 byte commands are still mandatory for SCSI >> > > block >> > > devices in order to accomodate softwares as boot software for example >> > > that >> > > may not be upgradable on systems still in use. Softwares that are >> > > maintained should no longer use 6 byte commands, but use the 10 byte >> > > commands replacement (for years...). >> > >> > Just so you know, I made the umass driver for UFI and ATA translate SCSI >> > 6 byte commands to 10 byte commands. There is a simple function call to >> > do the >> > change if you wish to do this in for the SCSI transforms as well. > > I'd love the patches if you've got them to hand. Unless you've spammed the commits I made to umass.c they've been in the tree for a month or so. :-P Look at the UFI transform for example: umass_ufi_transform(struct umass_softc *sc, unsigned char *cmd, int cmdlen, unsigned char **rcmd, int *rcmdlen) { ... if (umass_scsi_6_to_10(cmd, cmdlen, rcmd, rcmdlen)) return (1); ... } Same code is in the atapi_transform function as well. Just add those two lines before the big switch() on the command to the scsi_transform function. > Joe -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Feb 9 11:51:49 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 4D0CB37B41E; Sat, 9 Feb 2002 11:51:42 -0800 (PST) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id NAA69074; Sat, 9 Feb 2002 13:51:32 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Sat, 9 Feb 2002 13:51:32 -0600 (CST) From: Chris Dillon To: Oliver Fromme Cc: John Baldwin , =?ISO-8859-1?Q?G=E9rard_Roudier?= , FreeBSD Hackers Mailing List , FreeBSD Hardware Mailing List , Oliver Fromme , "Eugene M. Kim" , Terry Lambert , Josef Karthauser Subject: Re: USB "Memorybird" quirks In-Reply-To: <200202091216.g19CGk874726@lurza.secnetix.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, 9 Feb 2002, Oliver Fromme wrote: > I think that would be a very good idea. The boot software issue > is negligible, because there aren't any USB devices you can boot > from. You mean can't boot from USB devices in just FreeBSD, or anywhere? I've not actually tried it yet, but many motherboard vendors have added the ability to boot from USB ZIP drives and probably other USB mass storage devices to their BIOSes, so it at least should be possible. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet - Available for IA32 (Intel x86) and Alpha architectures - IA64, PowerPC, UltraSPARC, and ARM architectures under development - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message