From owner-freebsd-hardware Sun May 26 15:31: 3 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from shell.reiteration.net (pc-62-31-233-54-se.blueyonder.co.uk [62.31.233.54]) by hub.freebsd.org (Postfix) with ESMTP id 3479B37B404 for ; Sun, 26 May 2002 15:31:00 -0700 (PDT) Received: from shell.reiteration.net (jfm@localhost [127.0.0.1]) by shell.reiteration.net (8.12.2/8.12.2) with ESMTP id g4QMUwqI030635 for ; Sun, 26 May 2002 23:30:58 +0100 (BST) (envelope-from jfm@shell.reiteration.net) Received: (from jfm@localhost) by shell.reiteration.net (8.12.2/8.12.2/Submit) id g4QMUwAN030634 for freebsd-hardware@freebsd.org; Sun, 26 May 2002 23:30:58 +0100 (BST) Date: Sun, 26 May 2002 23:30:58 +0100 From: John To: freebsd-hardware@freebsd.org Subject: usb webcam support Message-ID: <20020526233058.E29343@shell.reiteration.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i 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 list I was wondering what the status of usb webcam support is under (native freebsd), or (linux emulation) under freebsd. I can query my webcam but it doesn't report an alphabetical string, just a hexadecimal vendor ID. Is anyone working on software supporting usb webcams? cheers -- John - jfm@reiteration.net - http://www.reiteration.net/~jfm For PGP public key finger jfm@reiteration.net or see webpage To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun May 26 19:13:12 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.249.195.3]) by hub.freebsd.org (Postfix) with SMTP id AD57C37B404 for ; Sun, 26 May 2002 19:12:55 -0700 (PDT) Received: (qmail 91560 invoked by uid 501); 27 May 2002 02:12:53 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 27 May 2002 02:12:53 -0000 Date: Sun, 26 May 2002 23:12:53 -0300 (BRT) From: Paulo Fragoso To: "Jin Guojun [DSD]" Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Wireless Problems (wi) In-Reply-To: <3CEED543.75C213B4@lbl.gov> Message-ID: <20020526225503.W84607-100000@mirage.nlink.com.br> 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, On Fri, 24 May 2002, Jin Guojun [DSD] wrote: > I do not think this is related to 4.5 or later. I had similar problem on > 4.3-RELEASE. > I believe that this is trigged by losing the contact to the wireless server. > Somehow, > the dirver dies and left some recovering status in configuration register on the > card > (just guessing). > When wi driver sees this status after reboot or power cycle, it will not reset > the card regardless power on or reboot. This may leave the card in some unknown > status. > But there is a very important fact: when we remove the card from its adapter and after a little time we reintroduce again (there is one power cylce here) it can't work, only will work after a reboot, without a power cycle. We think could be some situation which the wi driver can't answer correctly. In our routers there ins't other OS and it is very difficult to test because this happen after some hours working fine. At weekend this problem rarely happen when our traffic is low. > MS Windows does not try to look such status, and just re-initializes the card. > So, > if BSD cannot recover the wi0, boot to window, then boot back to BSD, and wi0 > will work again. If this is the case, then above guessing will be true. > > -Jin > > Paulo Fragoso wrote: > > > Hi, > > > > Have you ever found a problem with Orinoco and Avaya wireless card like > > this: > > > > /kernel: wi0: xmit failed > > /kernel: wi0: watchdog timeout > > /kernel: wi0: init failed > > /kernel: wi0: failed to allocate 1594 bytes on NIC > > /kernel: wi0: tx buffer allocation failed > > /kernel: wi0: failed to allocate 1594 bytes on NIC > > /kernel: wi0: mgmt. buffer allocation failed > > /kernel: wi0: timeout in wi_seek to 0/0; last status 4000 > > /kernel: wi0: timeout in wi_seek to 0/44; last status 4044 > > > > It's happening after 1 or 2 hours working normally and only after reboot > > (without turn off, like M$ Windows) this card return to work. > > > > This is very strange, we have a lot of remote router with FreeBSD release > > older than 4.5 and it's happening only with 4.5-RELEASE, 4.5-RELESE-pX an > > 4.6RC. Is it a coincidence or there is a problem with wi code? > > > > How those cards are locking and all CPU speed down when it is happing? > > > > Whe really need some help. Can anyone help us? > > > > Many thanks, > > Paulo Fragoso. > > > > -- > > __O > > _-\<,_ Why drive when you can bike? > > (_)/ (_) > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hardware" in the body of the message > > -- > ------------ Jin Guojun ----------- v --- j_guojun@lbl.gov --- > Distributed Systems Department http://www.itg.lbl.gov/~jin > M/S 50B-2239 Ph#:(510) 486-7531 Fax: 486-6363 > Lawrence Berkeley National Laboratory, Berkeley, CA 94720 > > > -- __O _-\<,_ Why drive when you can bike? (_)/ (_) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun May 26 20:21: 9 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 9886A37B403 for ; Sun, 26 May 2002 20:21:03 -0700 (PDT) Received: from lbl.gov (localhost.pacbell.net [127.0.0.1]) by adsl-63-198-35-122.dsl.snfc21.pacbell.net (8.11.6/8.11.6) with ESMTP id g4R3LQ300352; Sun, 26 May 2002 20:21:27 -0700 (PDT) (envelope-from j_guojun@lbl.gov) Message-ID: <3CF1A636.4980D347@lbl.gov> Date: Sun, 26 May 2002 20:21:26 -0700 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: Paulo Fragoso Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Wireless Problems (wi) References: <20020526225503.W84607-100000@mirage.nlink.com.br> 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 Paulo Fragoso wrote: > > Hi, > > On Fri, 24 May 2002, Jin Guojun [DSD] wrote: > > > I do not think this is related to 4.5 or later. I had similar problem on > > 4.3-RELEASE. > > I believe that this is trigged by losing the contact to the wireless server. > > Somehow, > > the dirver dies and left some recovering status in configuration register on the > > card > > (just guessing). > > When wi driver sees this status after reboot or power cycle, it will not reset > > the card regardless power on or reboot. This may leave the card in some unknown > > status. > > > > But there is a very important fact: when we remove the card from its > adapter and after a little time we reintroduce again (there is one power > cylce here) it can't work, only will work after a reboot, without a power > cycle. We think could be some situation which the wi driver can't answer > correctly. Removing and reinserting card may have power cycle on the card, but not the system. So the driver may not reinitialize the card if there is a recovering status set. You had better case than I have. If card is removed from my system, the whole system will be frozen. > In our routers there ins't other OS and it is very difficult to test > because this happen after some hours working fine. At weekend this problem > rarely happen when our traffic is low. From the information you provided, I think it is caused by losing the connectivity, and there are some bugs inside driver to cause wireless system die. My experience is that the wi0 may die anytime just from boot-up to after worked a few hours. I know it is caused by losing the connectivity, but do not know if this is caused by traffic or weak signal. To me, it seems a driver bug. Since I did not use wireless so often, I cannot file a bug report because I do not have time to play with wi0. If you have a dedicated use use with wi0, then you should file a bug report once you can repoduce such problem by introducing some heavy traffic (not hard at all for creating 11 Mbps network traffic from any host). > > MS Windows does not try to look such status, and just re-initializes the card. > > So, > > if BSD cannot recover the wi0, boot to window, then boot back to BSD, and wi0 > > will work again. If this is the case, then above guessing will be true. > > > > -Jin > > > > Paulo Fragoso wrote: > > > > > Hi, > > > > > > Have you ever found a problem with Orinoco and Avaya wireless card like > > > this: > > > > > > /kernel: wi0: xmit failed > > > /kernel: wi0: watchdog timeout > > > /kernel: wi0: init failed > > > /kernel: wi0: failed to allocate 1594 bytes on NIC > > > /kernel: wi0: tx buffer allocation failed > > > /kernel: wi0: failed to allocate 1594 bytes on NIC > > > /kernel: wi0: mgmt. buffer allocation failed > > > /kernel: wi0: timeout in wi_seek to 0/0; last status 4000 > > > /kernel: wi0: timeout in wi_seek to 0/44; last status 4044 > > > > > > It's happening after 1 or 2 hours working normally and only after reboot > > > (without turn off, like M$ Windows) this card return to work. > > > > > > This is very strange, we have a lot of remote router with FreeBSD release > > > older than 4.5 and it's happening only with 4.5-RELEASE, 4.5-RELESE-pX an > > > 4.6RC. Is it a coincidence or there is a problem with wi code? > > > > > > How those cards are locking and all CPU speed down when it is happing? > > > > > > Whe really need some help. Can anyone help us? > > > > > > Many thanks, > > > Paulo Fragoso. > > > > > > -- > > > __O > > > _-\<,_ Why drive when you can bike? > > > (_)/ (_) > > > > > > 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 Sun May 26 21:18:13 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from blotto.phreak.net (blotto.phreak.net [207.250.188.230]) by hub.freebsd.org (Postfix) with ESMTP id F209E37B406 for ; Sun, 26 May 2002 21:18:09 -0700 (PDT) Received: from phreak.net (localhost.phreak.net [127.0.0.1]) by blotto.phreak.net (Postfix) with SMTP id D3993189519; Sun, 26 May 2002 23:18:04 -0500 (CDT) Received: from 207.250.188.242 (SquirrelMail authenticated user operator) by mail.phreak.net with HTTP; Sun, 26 May 2002 23:18:05 -0500 (CDT) Message-ID: <1164.207.250.188.242.1022473085.squirrel@mail.phreak.net> Date: Sun, 26 May 2002 23:18:05 -0500 (CDT) Subject: Re: 3ware card status From: "Steve Kaczkowski" To: In-Reply-To: <20020510105249.A68431@ecad.org> References: <20020510105249.A68431@ecad.org> X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal Cc: X-Mailer: SquirrelMail (version 1.2.5) 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 All, > > Slightly off topic; > > I read on this list that 3ware was discontinuing their Escalade rang, > and concentrating on some of their NAS products. Based on this > information I held off purchasing one of these units. > > What about the freebsd 3ware utilities, are these still being > maintained (Mike?) > 3Ware were going to stop making the Escalade cards, but then changed their minds. As for Mike, I'm not sure since he recently left the core team.. :( Mike? You still here? -- Steve Kaczkowski operator@phreak.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon May 27 10:52:28 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from earth.hub.org (earth.hub.org [64.49.215.11]) by hub.freebsd.org (Postfix) with ESMTP id 47E5037B405; Mon, 27 May 2002 10:52:22 -0700 (PDT) Received: from earth.hub.org (earth.hub.org [64.49.215.11]) by earth.hub.org (Postfix) with ESMTP id 60A84103BF6; Mon, 27 May 2002 14:52:21 -0300 (ADT) Date: Mon, 27 May 2002 14:52:21 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-hardware@freebsd.org Cc: freebsd-mobile@freebsd.org Subject: Surecom EP-428X \4B in Sony Vaio Z505S ... Message-ID: <20020527132301.H12810-100000@mail1.hub.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 Morning all .. Just picked up one of the above cards for my laptop, since it was substantially cheaper to do so then replace the cable for the onboard ... according to the box, she works under Linux, so it doesn't appear to be some "windows only' kinda card ... I have my kernel compiled with pccard support, and have pccardd enabled for boot ... when I insert/remove the card, the laptop hangs, so I've modified my pccard.conf file so that it has the following based on some information that I found on the web concerning this: io 0x240-0x360 irq 3 10 11 memory 0xd0000 96k debuglevel 4 Based on: http://www.daemonnews.org/199909/pccard.html I tried to run 'pccardc dumpcis' to get the info about the card, but it just returned: Configuration data for card in slot 0 Tuple #1, code = 0xff (Terminator), length = 0 1 slots found Pointers on how to debug this further? Thanks ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed May 29 2:53:59 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from cpe.atm0-0-0-1231187.0x50c47eb6.kd4nxx3.customer.tele.dk (cpe.atm0-0-0-1231187.0x50c47eb6.kd4nxx3.customer.tele.dk [80.196.126.182]) by hub.freebsd.org (Postfix) with ESMTP id 6A6CC37B401 for ; Wed, 29 May 2002 02:53:55 -0700 (PDT) Received: from odessa.eiffel.dk (localhost [127.0.0.1]) by cpe.atm0-0-0-1231187.0x50c47eb6.kd4nxx3.customer.tele.dk (8.12.3/8.11.6) with ESMTP id g4T9sdGQ000286 for ; Wed, 29 May 2002 11:55:05 +0200 (CEST) (envelope-from flemming@froekjaer.org) Received: (from www@localhost) by odessa.eiffel.dk (8.12.3/8.12.3/Submit) id g4T9s8j2000275 for freebsd-hardware@FreeBSD.ORG; Wed, 29 May 2002 11:54:08 +0200 (CEST) X-Authentication-Warning: odessa.eiffel.dk: www set sender to flemming@froekjaer.org using -f To: freebsd-hardware@FreeBSD.ORG Subject: E1 / T1 Nic Message-ID: <1022666048.3cf4a540a8eec@mail.froekjaer.org> Date: Wed, 29 May 2002 11:54:08 +0200 (CEST) From: =?ISO-8859-1?Q?Flemming_Fr=F8kj=E6r?= MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.7 X-Originating-IP: 62.242.20.27 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 I'm building a E1/T1 based wan, and I want to use FreeBSD as my router/firewall. I have been looking at www.sbei.net for a nic for the project. There "wanADAPT- 1T1E1" looks about right, but is there anyone here on the list that has any experiense with these cards? Do you have any other recomendations for a E1/T1 nic? \Flemming To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed May 29 5:22:22 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from imo-r04.mx.aol.com (imo-r04.mx.aol.com [152.163.225.100]) by hub.freebsd.org (Postfix) with ESMTP id BF7F037B400 for ; Wed, 29 May 2002 05:22:05 -0700 (PDT) Received: from Telford002@aol.com by imo-r04.mx.aol.com (mail_out_v32.5.) id j.63.c298bef (4328); Wed, 29 May 2002 08:21:22 -0400 (EDT) From: Telford002@aol.com Message-ID: <63.c298bef.2a2621c2@aol.com> Date: Wed, 29 May 2002 08:21:22 EDT Subject: Re: E1 / T1 Nic To: flemming@froekjaer.org, freebsd-hardware@FreeBSD.ORG MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="part1_63.c298bef.2a2621c2_boundary" X-Mailer: AOL 7.0 for Windows US sub 10504 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 --part1_63.c298bef.2a2621c2_boundary Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 5/29/2002 5:54:16 AM Eastern Daylight Time, flemming@froekjaer.org writes: > I'm building a E1/T1 based wan, and I want to use FreeBSD as my > router/firewall. > I have been looking at www.sbei.net for a nic for the project. There > "wanADAPT- > 1T1E1" looks about right, but is there anyone here on the list that has any > > experiense with these cards? > Do you have any other recomendations for a E1/T1 nic? > > This card apparently supplies only unchannelized E1/T1. If that is all you want, you could use any high speed serial adapter card that can achieve E1 data rates and connect it to an external channel unit. Joachim Martillo --part1_63.c298bef.2a2621c2_boundary Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 5/29/2002 5:54:16 AM Eastern Daylight Time, flemming@froekjaer.org writes:


I'm building a E1/T1 based wan, and I want to use FreeBSD as my router/firewall.
I have been looking at www.sbei.net for a nic for the project. There "wanADAPT-
1T1E1" looks about right, but is there anyone here on the list that has any
experiense with these cards?
Do you have any other recomendations for a E1/T1 nic?



This card apparently supplies only unchannelized E1/T1.  If that is all you
want, you could use any high speed serial adapter card that can achieve E1
data rates and connect it to an external channel unit.

Joachim Martillo
 --part1_63.c298bef.2a2621c2_boundary-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed May 29 9:15:22 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from homemail.bjt.net (homemail.bjt.net [209.237.6.18]) by hub.freebsd.org (Postfix) with ESMTP id 0B22237B40A for ; Wed, 29 May 2002 09:15:01 -0700 (PDT) Received: from foo.fake.primenet.com [209.237.31.190] by homemail.bjt.net with ESMTP (SMTPD32-7.07) id ACB7409028A; Wed, 29 May 2002 09:07:19 -0700 Received: from baz.fake.primenet.com (baz [10.0.0.3]) by foo.fake.primenet.com (8.9.3/8.8.8) with ESMTP id JAA26775; Wed, 29 May 2002 09:14:52 -0700 (PDT) (envelope-from bko@idiom.com) Received: from baz.fake.primenet.com (localhost [127.0.0.1]) by baz.fake.primenet.com (8.12.2/8.12.2) with ESMTP id g4TGEqFN050453; Wed, 29 May 2002 09:14:52 -0700 (PDT) (envelope-from bkogawa@baz.fake.primenet.com) Received: (from bkogawa@localhost) by baz.fake.primenet.com (8.12.2/8.12.2/Submit) id g4TGEpgo050450; Wed, 29 May 2002 09:14:51 -0700 (PDT) From: "Bryan K. Ogawa" Message-Id: <200205291614.g4TGEpgo050450@baz.fake.primenet.com> To: "Stephane D'Alu" , hardware@freebsd.org Subject: Re: ARCHOS Recorder 20 failes accesing da2:umas-sim device In-Reply-To: <20020510201917.C6694@loria.fr> References: <20020510201917.C6694@loria.fr> Date: Wed, 29 May 2002 09:14:51 -0700 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 1. You might get more help with the bsd-usb list, which is usb-bsd@eleetbsd.org . 2. it looks like the error which is indicative of the device not allowing 10-byte reads. daryl okahata wrote up a nice document on fixing this, here's a quote from that: Chances are, the above command will fail (assuming that you used the correct parameters), with messages like the following appearing in the syslog/console: (da0:umass-sim0:0:0:0): READ(06). CDB: 8 0 0 0 4 0 (da0:umass-sim0:0:0:0): ILLEGAL REQUEST asc:21,0 (da0:umass-sim0:0:0:0): Logical block address out of range If you see this, don't worry; it just means that you have to tweak the kernel sources. In the above, note that the failing command is, "READ(06)"; if you see anything else, stop now, as something else is going wrong, and the rest of these instructions will probably not help you. If, by some miracle, the above command actually succeeds, rejoice. It means that you do not have to tweak the kernel sources, and that the USB disk should already be fully functional under FreeBSD. You can skip the rest of these steps, and start using the disk normally (but see the cautions below on disconnecting the disk from the USB bus!). * If the above mount failed, it means that you probably need to apply some kernel tweaks. What's happening is that FreeBSD treats an IDE USB disk as a SCSI disk, and tries to send it 6-byte SCSI commands, but the USB disk probably understands only 10-byte SCSI commands, and gives errors when 6-byte commands are used. [ Yes, it may seem strange, treating an IDE USB disk as a SCSI one, but it's actually a pretty good idea. This simplifies driver writing, because the USB driver only has to worry about low-level details, and the higher-level SCSI driver can handle a lot of the upper-level details. ] Fortunately, FreeBSD allows you to mark certain SCSI devices as being incapable of understanding 6-byte SCSI commands, which is a passable workaround for this problem. Ideally, the driver should fall back to using 10-byte commands if 6-byte one fails, but this does not (yet?) exist in FreeBSD-STABLE (I believe it does exist in FreeBSD-CURRENT, though). This is where the drive identification string comes in (you did make a note of it, above, right?). Here's a tricky part: you have to break up this drive identification string into a manufacturer name, a model name, and a revision. Hopefully, you're familiar with disk drive manufacturers; if you're not, ask around. In the above example, the drive identification string is (and this will almost certainly be different for you): TOSHIBA MK2016GAP U0.3 Here, the manufacturer name is "TOSHIBA", and the model name is "MK2016GAP", and the revision is "U0.3". Note that this one's easy; other drive identification strings may have additional spaces. The two key parts you'll need are the manufacturer and model names. Make a note of them. * As root, go to /usr/src/sys/cam/scsi, and edit the file, "scsi_da.c". Search for the variable, "da_quirk_table"; you want to locate where it is defined. The variable, "da_quirk_table", contains a list of all SCSI devices that need to be specially handled, and it is here where we need to add an entry for our USB disk. Basically, to this variable, you want to add an entry like: { {T_DIRECT, SIP_MEDIA_FIXED, "TOSHIBA", "MK2016GAP", "*"}, /*quirks*/ DA_Q_NO_6_BYTE }, Replace "TOSHIBA" with the manufacturer name of your disk, and replace "MK2016GAP" with the model name. This will tell FreeBSD to specially handle your USB disk -- to not use 6-byte SCSI commands. Rebuild your kernel (don't forget to do a "make depend"), and reboot. The USB disk should be functional. >From here, you should be able to use the disk normally. However, before physically disconnecting the USB disk from the USB bus, do not forget to unmount any mounted filesystems that come off the USB disk. Bad Things Will Happen if you disconnect the disk before unmounting any such filesystems (you may lose data, or FreeBSD might crash). If part or all of the disk is going to be used for FreeBSD, just follow the instructions in the handbook. I hope this helps. In localhost.freebsd.hardware, you wrote: > Hello, > > I've bought a ARCHOS Recorder 20 (not the Studio, which used a > different chipset), and when plugged it is correctly > recognised by the USB subsystem as a umass device: >| umass0: ARCHOS ARCHOS USB2.0 (P4a), rev 2.00/11.01, addr 3 >| da2 at umass-sim0 bus 0 target 0 lun 0 >| da2: Fixed Direct Access SCSI-0 device >| da2: 650KB/s transfers >| da2: 19077MB (39070080 512 byte sectors: 64H 32S/T 19077C) > > now my problem is that when trying to access it, it failes: >| (da2:umass-sim0:0:0:0): READ(06). CDB: 8 0 0 0 1 0 >| (da2:umass-sim0:0:0:0): ILLEGAL REQUEST asc:21,0 >| (da2:umass-sim0:0:0:0): Logical block address out of range > > Does someone have an idea (and suggestions)? > > For information here is the result of 'usbdevs': > bash# usbdevs -v > Controller /dev/usb0: > addr 1: self powered, config 1, UHCI root hub(0x0000), VIA(0x0000), rev 0x0100 > port 1 addr 2: low speed, power 50 mA, config 1, USB Receiver(0xc501), Logitech(0x046d), rev 0x0910 > port 2 addr 3: self powered, config 2, ARCHOS USB2.0 (P4a)(0x0060), ARCHOS (0x05ab), rev 0x1101 > > > Thanks > > -- > Stephane D'Alu > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > -- bryan k ogawa http://www.idiom.com/~bko/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed May 29 23:20:54 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from roam.psg.com (uds159-58.dial.hccnet.nl [62.251.58.159]) by hub.freebsd.org (Postfix) with ESMTP id 4521637B405 for ; Wed, 29 May 2002 23:20:43 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=guest180.ripe.net.psg.com ident=randy) by roam.psg.com with esmtp (Exim 4.04) id 17DJIc-0003vt-00 for freebsd-hardware@freebsd.org; Wed, 29 May 2002 23:20:38 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Hardware Subject: d-link bluetooth Message-Id: Date: Wed, 29 May 2002 23:20:38 -0700 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 -stable of last week on a dell latitude c600 i have borrowed a d-link bluetooth dongle. i want it to appear as either ether or serial so i can get it through to win98 under vmware. any clues? search of archives did not avail. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu May 30 11:48:17 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from idefix.muenchen.de (idefix.muenchen.de [194.113.40.222]) by hub.freebsd.org (Postfix) with ESMTP id A581837B403 for ; Thu, 30 May 2002 11:48:10 -0700 (PDT) Received: from flaucher.muenchen.de (flaucher.muenchen.de [194.113.40.210]) by idefix.muenchen.de (8.10.1/8.10.1) with SMTP id g4UIm9807669 for ; Thu, 30 May 2002 20:48:09 +0200 (MET DST) Received: from ns01.muenchen.de by flaucher.muenchen.de via smtpd (for idefix.muenchen.de [194.113.40.222]) with SMTP; 30 May 2002 18:48:09 UT Received: from mail01.muenchen.de (mail01.muenchen.de [194.246.199.66]) by ns01.muenchen.de (8.11.3/8.11.3) with ESMTP id g4UIm8b29148 for ; Thu, 30 May 2002 20:48:08 +0200 (MET DST) Received: from muenchen.de (10.1.3.36) by mail01.muenchen.de (5.1.056) id 3CEE478A00012789 for freebsd-hardware@freebsd.org; Thu, 30 May 2002 20:48:08 +0200 Message-ID: <3CF673F7.E082A003@muenchen.de> Date: Thu, 30 May 2002 20:48:23 +0200 From: Florian Baier X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: USB and RS232 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 Hi, I'm searching for a USB to serialRS232 converter which is working with FreeBSD (4.5). Is the a supported converter (or chip)? Thanks in advance. Regards, Florian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu May 30 11:55:56 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id DE8D237B409 for ; Thu, 30 May 2002 11:55:52 -0700 (PDT) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.3/8.12.3) with ESMTP id g4UItpeE010022; Thu, 30 May 2002 11:55:51 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.3/8.12.3/Submit) id g4UItprj010021; Thu, 30 May 2002 11:55:51 -0700 Date: Thu, 30 May 2002 11:55:51 -0700 From: Brooks Davis To: Florian Baier Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: USB and RS232 Message-ID: <20020530115551.A9384@Odin.AC.HMC.Edu> References: <3CF673F7.E082A003@muenchen.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3CF673F7.E082A003@muenchen.de>; from Florian.Baier@muenchen.de on Thu, May 30, 2002 at 08:48:23PM +0200 X-Virus-Scanned: by amavisd-milter (http://amavis.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 --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 30, 2002 at 08:48:23PM +0200, Florian Baier wrote: > Hi, >=20 > I'm searching for a USB to serialRS232 converter which is working with > FreeBSD (4.5). > Is the a supported converter (or chip)? Not for 4.5. In current the uplcom driver supports the following ATEN UC-232A BAFO BF-800 BAFO BF-810 ELECOM UC-SGT IOGEAR UC-232A I/O DATA USB-RSAQ I/O DATA USB-RSAQ2 PLANEX USB-RS232 URS-03 I'm not 100% sure it's working at this point. I've got one of the IOGEAR ones and it hung my machine when I tried to use it, but it's entierly likely I was doing something wrong and that was right after the driver was imported (quite a while ago). -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --T4sUOijqQbZv57TR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE89nW2XY6L6fI4GtQRAqcTAKDV3rH3ZjTqlAOyQu0WiUVeCJNptgCbBQRZ JQvl0whg9jXrO8L3oJt9fCs= =dce3 -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu May 30 12:58:38 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by hub.freebsd.org (Postfix) with ESMTP id 242AB37B407 for ; Thu, 30 May 2002 12:58:35 -0700 (PDT) Received: from melange (melange.errno.com [66.127.85.82]) (authenticated bits=0) by ebb.errno.com (8.12.1/8.12.1) with ESMTP id g4UJwXKs032374 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Thu, 30 May 2002 12:58:34 -0700 (PDT)?g (envelope-from sam@errno.com)œ Message-ID: <005d01c20814$6146c030$52557f42@errno.com> From: "Sam Leffler" To: References: <3CF673F7.E082A003@muenchen.de> <20020530115551.A9384@Odin.AC.HMC.Edu> Subject: belkin omniview kvm switch lockup Date: Thu, 30 May 2002 12:58:33 -0700 Organization: Errno Consulting 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 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 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 I'm having problems with a belkin 2-port ps/2 omniview switch (F1DS102P). I have two machines connected; one running win2K the other freebsd-stable. I boot the win2k machine first and everything is ok--kbd and mouse work, the port switches on the front work, and the hotswap keys are accessible. I power on the freebsd system (an emachines box) and things work at the bios level but once -stable boots the kvm is stuck on the port where the freebsd machine is hooked. Front panel switches are inoperable and the hotswap keys are inaccessible. If I pull the keyboard and mouse cables for the freebsd box then I can switch to the port where the win2k machine is located but the keyboard is not usable (I can use the mouse to shutdown the machine). The only way to reset the kvm is to power everything down and yank cables (the kvm gets power from the ps/2 ports). Seems like the -stable atkdb driver is somehow confusing the kvm. Belkin "tech support" has no clues (the switch firmware is flash upgradable but no updates on the web site look worth trying). Has anyone used this switch w/ non-windows and/or non-mac systems w/ any success? I tried fiddling with the flags on atkbdc to reset/not-reset on boot w/ no effect. Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu May 30 15:10:26 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from damon.com (damon.com [199.98.84.130]) by hub.freebsd.org (Postfix) with ESMTP id 403E237B401 for ; Thu, 30 May 2002 15:10:19 -0700 (PDT) Received: from damon.com (localhost [127.0.0.1]) by damon.com (8.12.3/8.12.3) with ESMTP id g4UKlGxH019346; Thu, 30 May 2002 15:47:16 -0500 (CDT) (envelope-from dap@damon.com) Received: (from dap@localhost) by damon.com (8.12.3/8.12.3/Submit) id g4UKlGni019345; Thu, 30 May 2002 15:47:16 -0500 (CDT) (envelope-from dap) Date: Thu, 30 May 2002 15:47:16 -0500 From: Damon Anton Permezel To: Sam Leffler Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: belkin omniview kvm switch lockup Message-ID: <20020530154716.E15708@damon.com> References: <3CF673F7.E082A003@muenchen.de> <20020530115551.A9384@Odin.AC.HMC.Edu> <005d01c20814$6146c030$52557f42@errno.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: <005d01c20814$6146c030$52557f42@errno.com>; from sam@errno.com on Thu, May 30, 2002 at 12:58:33PM -0700 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 Sam, I have often been plagued by my KVM getting stuck. I have an ATen CS-106 Master View. Current failure mode is when the 4.6-RC kernel is stopped in the debugger over the serial port, if I switch to the look at the screen, I get stuck. I have seen this on other machines running loonix, with the same KVM. I have also noticed that if I reboot a machine, the BIOS has to get past a certain spot before the KVM will switch. I find that I can wait a while and it eventually switches. Sometimes. In combination with turning on and off the power on the KVM and hitting the switches from different angles and sacrificing small animals on the keyboard. I'd love to hear an explanation of what is causing this. On Thu, May 30, 2002 at 12:58:33PM -0700, Sam Leffler wrote: > I'm having problems with a belkin 2-port ps/2 omniview switch (F1DS102P). I > have two machines connected; one running win2K the other freebsd-stable. I > boot the win2k machine first and everything is ok--kbd and mouse work, the > port switches on the front work, and the hotswap keys are accessible. I > power on the freebsd system (an emachines box) and things work at the bios > level but once -stable boots the kvm is stuck on the port where the freebsd > machine is hooked. Front panel switches are inoperable and the hotswap keys > are inaccessible. If I pull the keyboard and mouse cables for the freebsd > box then I can switch to the port where the win2k machine is located but the > keyboard is not usable (I can use the mouse to shutdown the machine). The > only way to reset the kvm is to power everything down and yank cables (the > kvm gets power from the ps/2 ports). > > Seems like the -stable atkdb driver is somehow confusing the kvm. Belkin > "tech support" has no clues (the switch firmware is flash upgradable but no > updates on the web site look worth trying). > > Has anyone used this switch w/ non-windows and/or non-mac systems w/ any > success? I tried fiddling with the flags on atkbdc to reset/not-reset on > boot w/ no effect. > > Sam > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message -- -- Damon Permezel dap@damon.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri May 31 2: 0:40 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.wearix.com (lorien.wearix.com [193.197.4.2]) by hub.freebsd.org (Postfix) with ESMTP id 5CEDC37B408 for ; Fri, 31 May 2002 02:00:36 -0700 (PDT) Received: from hry.muc.wearix.com (ad96e1d2b.dsl.de.colt.net [217.110.29.43]) by mail.wearix.com (Postfix on SuSE Linux 7.3 (i386)) with ESMTP id 9CDBD3530; Fri, 31 May 2002 11:00:33 +0200 (CEST) Subject: Re: E1 / T1 Nic From: Harald Schmalzbauer To: Flemming =?ISO-8859-1?Q?Fr=F8kj=E6r?= Cc: freebsd-hardware@FreeBSD.ORG In-Reply-To: <1022666048.3cf4a540a8eec@mail.froekjaer.org> References: <1022666048.3cf4a540a8eec@mail.froekjaer.org> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution/1.0 (Preview Release) Date: 31 May 2002 12:01:19 +0300 Message-Id: <1022835680.7867.0.camel@hry.muc.wearix.com> Mime-Version: 1.0 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 Am Mi , 2002-05-29 um 12.54 schrieb Flemming Fr=F8kj=E6r: > I'm building a E1/T1 based wan, and I want to use FreeBSD as my router/fi= rewall. > I have been looking at www.sbei.net for a nic for the project. There "wan= ADAPT- > 1T1E1" looks about right, but is there anyone here on the list that has a= ny=20 > experiense with these cards? > Do you have any other recomendations for a E1/T1 nic? Hello, I built such a Cisco replacement box two years ago. It was a bit hard to get it working with unstructured E1 but the engineers at this time were very helpful and the extendet the driver for FreeBSD. At that time LMC support was in 5-current for netgraph but I don't know the status nowadays. In general I was very satisfied with that cards. -Harry >=20 > \Flemming >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message --=20 Wearix Software GmbH Harald Schmalzbauer, IT-Engineer Unterhachinger Strasse 75 81737 M=FCnchen +49 89 548828-802 http://www.wearix.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri May 31 2:53:59 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by hub.freebsd.org (Postfix) with SMTP id 4365137B407 for ; Fri, 31 May 2002 02:53:54 -0700 (PDT) Received: (qmail 22228 invoked by uid 0); 31 May 2002 09:53:48 -0000 Received: from unknown (HELO gmx.de) (193.158.3.118) by mail.gmx.net (mp015-rz3) with SMTP; 31 May 2002 09:53:48 -0000 Message-ID: <3CF74828.3CE8021B@gmx.de> Date: Fri, 31 May 2002 11:53:44 +0200 From: Christian Tanghe X-Mailer: Mozilla 4.72 [en]C-CCK-MCD QXW0323l (Windows NT 5.0; U) X-Accept-Language: de,en MIME-Version: 1.0 To: questions@freebsd.org Cc: hardware@freebsd.org Subject: Toshiba Equium 3000 with 5.0-DP1 FreeBSD doesn't boot, USB Keyboard problem? 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 Hello, I have installed a Toshiba Equium 3000 with 5.0-DP1 FreeBSD with Floppies and FTP. Therefore I had have to inactivate atkbd0 in Kerneldevice Configuration. So far so good, the System is on the machine, but ... Booting hangs after loading about 50 devices after the line: ad0: 5729MB [12416/15/63] at ata0-master UDMA33 Whats wrong, what have I to config? Thanks, Christian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri May 31 7:19:19 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from cavia.pp.ru (storm.demos.su [194.87.2.36]) by hub.freebsd.org (Postfix) with ESMTP id D54A737B400 for ; Fri, 31 May 2002 07:19:14 -0700 (PDT) Received: from cavia.pp.ru (localhost [127.0.0.1]) by cavia.pp.ru (8.12.2/8.12.2) with ESMTP id g4VEHowf006810 for ; Fri, 31 May 2002 18:17:50 +0400 (MSD) (envelope-from mitya@cavia.pp.ru) Received: (from mitya@localhost) by cavia.pp.ru (8.12.2/8.12.2/Submit) id g4VEHobl006809 for freebsd-hardware@freebsd.org; Fri, 31 May 2002 18:17:50 +0400 (MSD) Date: Fri, 31 May 2002 18:17:50 +0400 From: Dmitry Sivachenko To: freebsd-hardware@freebsd.org Subject: USB ThumbDrive (PenDrive) Message-ID: <20020531141750.GF5595@cavia.pp.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tKW2IUtsqtDRztdT" Content-Disposition: inline User-Agent: Mutt/1.3.99i WWW-Home-Page: http://mitya.pp.ru/ X-PGP-Key: http://mitya.pp.ru/mitya.asc 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 --tKW2IUtsqtDRztdT Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Hello! Whether any USB ThumbDrive (or PenDrive) is supported or not? Thank you in advance. --tKW2IUtsqtDRztdT 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 iD8DBQE894YOEZSZYxPV34ARAkeiAJ4oU354LBh1s79vYBzhRtGwEX2pNQCeKvGj ODilimGof30s02rv17D5OB0= =2wjh -----END PGP SIGNATURE----- --tKW2IUtsqtDRztdT-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jun 1 12:34: 0 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from smtp.comcast.net (smtp.comcast.net [24.153.64.2]) by hub.freebsd.org (Postfix) with ESMTP id AE00A37B401 for ; Sat, 1 Jun 2002 12:33:55 -0700 (PDT) Received: from pobox.com (pcp826719pcs.nrockv01.md.comcast.net [68.50.140.34]) by mtaout05.icomcast.net (iPlanet Messaging Server 5.1 HotFix 0.8 (built May 13 2002)) with ESMTP id <0GX100EKEL0IOI@mtaout05.icomcast.net> for freebsd-hardware@FreeBSD.ORG; Sat, 01 Jun 2002 15:33:55 -0400 (EDT) Date: Fri, 31 May 2002 15:43:34 -0400 From: Lee Nelson Subject: Re: belkin omniview kvm switch lockup To: Damon Anton Permezel Cc: Sam Leffler , freebsd-hardware@FreeBSD.ORG Message-id: <3CF7D266.2FC19C1D@pobox.com> MIME-version: 1.0 X-Mailer: Mozilla 4.77 [en] (Win98; U) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en References: <3CF673F7.E082A003@muenchen.de> <20020530115551.A9384@Odin.AC.HMC.Edu> <005d01c20814$6146c030$52557f42@errno.com> <20020530154716.E15708@damon.com> 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 I looked at the source for the FreeBSD mouse/keyboard drivers about a year ago when I was having the same problem. It turns out that they, along with everyone else, make unwarranted assumptions about the state of the keyboard/mouse. In the case of the mouse specifically, the FreeBSD driver doesn't make any attempt to notice odd data or try to resync on the data packets if it loses sync - it just happily sends "off by N" garbage data to apps, or ceases to function entirely. The FreeBSD drivers could be *much* better in this regard, but I don't think they could ever be perfect. The real answer is to use an expensive KVM that continuously emulates keyboard and mouse for each machine, or just live with the occasional reboots. For the record I use a 4 port Linksys KVM (rebadged Aten) which works well most of the time. When I lose keyboard, power cycling the KVM or switching to a different unit and hitting a key nearly always brings it back. If I lose mouse though, the only hope is a reboot. -Lee Damon Anton Permezel wrote: > > Sam, > I have often been plagued by my KVM getting stuck. > I have an ATen CS-106 Master View. > > Current failure mode is when the 4.6-RC kernel is stopped in the > debugger over the serial port, if I switch to the look at the screen, > I get stuck. > > I have seen this on other machines running loonix, with the same KVM. > > I have also noticed that if I reboot a machine, the BIOS has to get > past a certain spot before the KVM will switch. > > I find that I can wait a while and it eventually switches. Sometimes. > In combination with turning on and off the power on the KVM and hitting > the switches from different angles and sacrificing small animals on the > keyboard. > > I'd love to hear an explanation of what is causing this. > > On Thu, May 30, 2002 at 12:58:33PM -0700, Sam Leffler wrote: > > I'm having problems with a belkin 2-port ps/2 omniview switch (F1DS102P). I > > have two machines connected; one running win2K the other freebsd-stable. I > > boot the win2k machine first and everything is ok--kbd and mouse work, the > > port switches on the front work, and the hotswap keys are accessible. I > > power on the freebsd system (an emachines box) and things work at the bios > > level but once -stable boots the kvm is stuck on the port where the freebsd > > machine is hooked. Front panel switches are inoperable and the hotswap keys > > are inaccessible. If I pull the keyboard and mouse cables for the freebsd > > box then I can switch to the port where the win2k machine is located but the > > keyboard is not usable (I can use the mouse to shutdown the machine). The > > only way to reset the kvm is to power everything down and yank cables (the > > kvm gets power from the ps/2 ports). > > > > Seems like the -stable atkdb driver is somehow confusing the kvm. Belkin > > "tech support" has no clues (the switch firmware is flash upgradable but no > > updates on the web site look worth trying). > > > > Has anyone used this switch w/ non-windows and/or non-mac systems w/ any > > success? I tried fiddling with the flags on atkbdc to reset/not-reset on > > boot w/ no effect. > > > > Sam > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hardware" in the body of the message > > -- > -- > Damon Permezel > dap@damon.com > > 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