Date: Thu, 21 Oct 2010 14:33:46 +0200 From: Polytropon <freebsd@edvax.de> To: David Brodbeck <gull@gull.us> Cc: freebsd-questions@freebsd.org Subject: Re: Netbooks & BSD Message-ID: <20101021143346.43940e3b.freebsd@edvax.de> In-Reply-To: <AANLkTin0e2bOM3Y_Z8pCeHU%2B_ZqMZmux=YpAXeHmDZDJ@mail.gmail.com> References: <20101004195012.GA2023@tiny> <op.vj5o9ixxhtl4zj@ack5833s2.ad.service.osu.edu> <20101017143901.GA71132@current.Sisis.de> <alpine.BSF.2.00.1010171215030.96626@wonkity.com> <20101019074615.GA2183@current.Sisis.de> <alpine.BSF.2.00.1010191448390.6689@wonkity.com> <20101020022946.GA23035@thought.org> <4CBE8B86.9060608@uffe.org> <20101020173259.GD25310@thought.org> <AANLkTi=EJdFYFdHRXhbcY-TGT4JuQMtK3zfxdSY7_PrE@mail.gmail.com> <20101020211546.GA26611@thought.org> <44y69s8rse.fsf@be-well.ilk.org> <AANLkTin0e2bOM3Y_Z8pCeHU%2B_ZqMZmux=YpAXeHmDZDJ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 20 Oct 2010 14:54:21 -0700, David Brodbeck <gull@gull.us> 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: <SanDisk Cruzer Micro, class 0/0, rev 2.00/2.00, addr 2> on uhub2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: <SanDisk Cruzer Micro 8.02> 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, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101021143346.43940e3b.freebsd>