From owner-freebsd-questions@FreeBSD.ORG Thu Oct 21 12:33:50 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2756D106564A for ; Thu, 21 Oct 2010 12:33:50 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) by mx1.freebsd.org (Postfix) with ESMTP id D695C8FC20 for ; Thu, 21 Oct 2010 12:33:49 +0000 (UTC) Received: from r55.edvax.de (port-92-195-16-227.dynamic.qsc.de [92.195.16.227]) by mx02.qsc.de (Postfix) with ESMTP id 431931E631; Thu, 21 Oct 2010 14:33:47 +0200 (CEST) Received: from r55.edvax.de (localhost [127.0.0.1]) by r55.edvax.de (8.14.2/8.14.2) with SMTP id o9LCXknI001643; Thu, 21 Oct 2010 14:33:46 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Thu, 21 Oct 2010 14:33:46 +0200 From: Polytropon To: David Brodbeck Message-Id: <20101021143346.43940e3b.freebsd@edvax.de> In-Reply-To: References: <20101004195012.GA2023@tiny> <20101017143901.GA71132@current.Sisis.de> <20101019074615.GA2183@current.Sisis.de> <20101020022946.GA23035@thought.org> <4CBE8B86.9060608@uffe.org> <20101020173259.GD25310@thought.org> <20101020211546.GA26611@thought.org> <44y69s8rse.fsf@be-well.ilk.org> Organization: EDVAX X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Netbooks & BSD X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2010 12:33:50 -0000 On Wed, 20 Oct 2010 14:54:21 -0700, David Brodbeck wrote: > Fortunately, USB mass storage devices are highly standardized. One of > the things they got right. Highly, but not fully. In some cases, manufacturers "know better" and produce memory sticks that don't work on FreeBSD as they do require some "driver" (no idea what is meant) to be accessible. They seem to vialote the standards for USB direct access, so the system gets into trouble (because it has to work with an obviously defective storage media). Here's an example of a stick I returned to the shop the same day, said "It's broken, money back." with a dmesg + fdisk printout on tractor paper (always looks impressive). :-) umass0: on uhub2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: UNIT ATTENTION, Medium not present umass0: at uhub2 port 2 (addr 2) disconnected (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry umass0: detached I couldn't not format it (it was some FAT format on it) as it detached from the system by itself as soon as accessed. > Now, the USB keyboard protocol...ugh, they really dropped the ball on > that one. It's standardized, which is good, but it's a polling > interface and tends to occasionally lose events under high CPU load, > which is bad. Especially if it's a key-up event that gets lost. USB mice suffer from the same problem - the polling. In the past, I never had problems with interrupt-driven (serial and PS/2) equipment, even on lowest-end (!) hardware. Today, some load can render the system nearly inresponsive for several seconds (no keyboard input, mouse stopped). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...