From owner-freebsd-hardware@FreeBSD.ORG Tue Jul 18 11:25:08 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 124C716A4E0 for ; Tue, 18 Jul 2006 11:25:08 +0000 (UTC) (envelope-from om-lists-bsd@omx.ch) Received: from andromeda.insign.ch (andromeda.insign.ch [195.134.143.165]) by mx1.FreeBSD.org (Postfix) with SMTP id 3B91843D46 for ; Tue, 18 Jul 2006 11:25:06 +0000 (GMT) (envelope-from om-lists-bsd@omx.ch) Received: (qmail 31508 invoked by uid 508); 18 Jul 2006 11:25:03 -0000 Received: from om-lists-bsd@omx.ch by andromeda3 by uid 502 with qmail-scanner-1.21 (avp(2004-05-12). Clear:RC:1(80.254.166.203):. Processed in 0.027942 secs); 18 Jul 2006 11:25:03 -0000 Received: from zux166-203.adsl.green.ch (HELO olipc.insign) ([80.254.166.203]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 18 Jul 2006 11:25:03 -0000 From: Olivier Mueller To: freebsd-hardware@freebsd.org In-Reply-To: <1152697468.31818.15.camel@olipc.insign.local> References: <1152697468.31818.15.camel@olipc.insign.local> Content-Type: text/plain Date: Tue, 18 Jul 2006 13:25:04 +0200 Message-Id: <1153221904.23956.25.camel@olipc.insign.local> Mime-Version: 1.0 X-Mailer: Evolution 2.0.1 Content-Transfer-Encoding: 7bit Subject: Re: dell poweredge 1950 : not rebooting under 6.1 (sometimes) + bce0 issues X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jul 2006 11:25:08 -0000 On Wed, 2006-07-12 at 11:44 +0200, Olivier Mueller wrote: > Any guess about what I should try? I recompiled the kernel > with & without apci support or some different options, but it didn't > helped yet. Another problem: I wanted to transfer large amount of data (10GB) using rsync via the network, and just after 60MB, the network card won't answser anymore, and here is what is displayed in dmesg: bce0: /usr/src/sys/dev/bce/if_bce.c(4644): Error mapping mbuf into TX chain! bce0: /usr/src/sys/dev/bce/if_bce.c(4644): Error mapping mbuf into TX chain! bce0: /usr/src/sys/dev/bce/if_bce.c(4644): Error mapping mbuf into TX chain! [...] Then if I let it continue, the server simply "crashes" (keyboard not responding, and no network access). $ dmesg | grep bce bce0: mem 0xf4000000-0xf5ffffff irq 16 at device 0.0 on pci9 bce0: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz miibus0: on bce0 bce0: Ethernet address: 00:13:72:f8:6f:8c bce1: mem 0xf8000000-0xf9ffffff irq 16 at device 0.0 on pci5 bce1: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz miibus1: on bce1 bce1: Ethernet address: 00:13:72:f8:6f:8a To be continued, I'll continue to test, but it seems I will have to go back to linux for that PE 1950 server if it continues like that :/ regards, Olivier From owner-freebsd-hardware@FreeBSD.ORG Tue Jul 18 12:51:52 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64E7716A4DE for ; Tue, 18 Jul 2006 12:51:52 +0000 (UTC) (envelope-from jhs@flat.berklix.net) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAB2943D4C for ; Tue, 18 Jul 2006 12:51:51 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A5C6C.dip.t-dialin.net [84.154.92.108]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id k6ICpnDB016973; Tue, 18 Jul 2006 14:51:50 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id k6ICpmFv005287; Tue, 18 Jul 2006 14:51:49 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost.jhs.private [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id k6ICpmZW003636; Tue, 18 Jul 2006 14:51:48 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200607181251.k6ICpmZW003636@fire.jhs.private> To: Olivier Mueller In-Reply-To: Message from Olivier Mueller of "Tue, 18 Jul 2006 13:25:04 +0200." <1153221904.23956.25.camel@olipc.insign.local> Date: Tue, 18 Jul 2006 14:51:48 +0200 From: "Julian H. Stacey" Cc: freebsd-hardware@freebsd.org Subject: Re: dell poweredge 1950 : not rebooting under 6.1 (sometimes) + bce0 issues X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jul 2006 12:51:52 -0000 -------- Olivier Mueller wrote: > On Wed, 2006-07-12 at 11:44 +0200, Olivier Mueller wrote: > > Any guess about what I should try? I recompiled the kernel > > with & without apci support or some different options, but it didn't > > helped yet. > > Another problem: I wanted to transfer large amount of data (10GB) using > rsync via the network, and just after 60MB, the network card won't > answser anymore, and here is what is displayed in dmesg: > > bce0: /usr/src/sys/dev/bce/if_bce.c(4644): Error mapping mbuf into TX > To be continued, I'll continue to test, but it seems I will have to go > back to linux for that PE 1950 server if it continues like that :/ Maybe try eg /usr/ports/comms/ 44bsd-rdist rdist6 or other coms packs. to get you by for now, while you & others in parallel worry about what kernel prob. you'r tickling ? -- Julian Stacey. Consultant Unix Net & Sys. Eng., Munich. http://berklix.com Mail in Ascii, HTML=spam. Ihr Rauch = mein allergischer Kopfschmerz. From owner-freebsd-hardware@FreeBSD.ORG Tue Jul 18 19:00:37 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B701616A4DD for ; Tue, 18 Jul 2006 19:00:37 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3FE543D55 for ; Tue, 18 Jul 2006 19:00:36 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k6IJ0TOn055606; Tue, 18 Jul 2006 15:00:33 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Tue, 18 Jul 2006 15:00:21 -0400 User-Agent: KMail/1.9.1 References: <1152697468.31818.15.camel@olipc.insign.local> <1153221904.23956.25.camel@olipc.insign.local> In-Reply-To: <1153221904.23956.25.camel@olipc.insign.local> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607181500.21683.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Tue, 18 Jul 2006 15:00:35 -0400 (EDT) X-Virus-Scanned: ClamAV 0.87.1/1604/Tue Jul 18 11:41:03 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Olivier Mueller Subject: Re: dell poweredge 1950 : not rebooting under 6.1 (sometimes) + bce0 issues X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jul 2006 19:00:37 -0000 On Tuesday 18 July 2006 07:25, Olivier Mueller wrote: > On Wed, 2006-07-12 at 11:44 +0200, Olivier Mueller wrote: > > Any guess about what I should try? I recompiled the kernel > > with & without apci support or some different options, but it didn't > > helped yet. > > Another problem: I wanted to transfer large amount of data (10GB) using > rsync via the network, and just after 60MB, the network card won't > answser anymore, and here is what is displayed in dmesg: > > bce0: /usr/src/sys/dev/bce/if_bce.c(4644): Error mapping mbuf into TX > chain! > bce0: /usr/src/sys/dev/bce/if_bce.c(4644): Error mapping mbuf into TX > chain! > bce0: /usr/src/sys/dev/bce/if_bce.c(4644): Error mapping mbuf into TX > chain! > [...] This sounds like it is out of tx descriptors. Do you ever get a watchdog timeout message? If not, can you try this patch: Index: if_bce.c =================================================================== RCS file: /usr/cvs/src/sys/dev/bce/if_bce.c,v retrieving revision 1.5 diff -u -r1.5 if_bce.c --- if_bce.c 12 Jul 2006 23:13:09 -0000 1.5 +++ if_bce.c 18 Jul 2006 18:59:45 -0000 @@ -4391,6 +4391,9 @@ DBRUNIF(1, sc->tx_mbuf_alloc--); ifp->if_opackets++; + + /* Clear the TX timeout timer. */ + ifp->if_timer = 0; } sc->used_tx_bd--; @@ -4406,9 +4409,6 @@ BUS_SPACE_BARRIER_READ); } - /* Clear the TX timeout timer. */ - ifp->if_timer = 0; - /* Clear the tx hardware queue full flag. */ if ((sc->used_tx_bd + BCE_TX_SLACK_SPACE) < USABLE_TX_BD) { DBRUNIF((ifp->if_drv_flags & IFF_DRV_OACTIVE), @@ -5031,10 +5031,12 @@ /* DBRUN(BCE_FATAL, bce_breakpoint(sc)); */ + BCE_LOCK(sc); ifp->if_drv_flags &= ~IFF_DRV_RUNNING; - bce_init(sc); + bce_init_locked(sc); ifp->if_oerrors++; + BCE_UNLOCK(sc); } -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Tue Jul 18 22:05:21 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A564516A4DA for ; Tue, 18 Jul 2006 22:05:21 +0000 (UTC) (envelope-from ralphellis1@netscape.ca) Received: from smtp-2.vancouver.ipapp.com (smtp-2.vancouver.ipapp.com [216.152.192.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62EB043D45 for ; Tue, 18 Jul 2006 22:05:21 +0000 (GMT) (envelope-from ralphellis1@netscape.ca) Received: from [192.168.123.100] ([172.166.72.208]) by smtp-2.vancouver.ipapp.com ; Tue, 18 Jul 2006 15:04:52 -0700 From: Ralph Ellis To: freebsd-hardware@freebsd.org Date: Tue, 18 Jul 2006 18:04:49 -0400 User-Agent: KMail/1.9.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607181804.49339.ralphellis1@netscape.ca> X-Rcpt-To: X-Country: US Subject: USB Mouse X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jul 2006 22:05:21 -0000 I have a laptop with a touch pad and I would like to use my wireless USB mouse either at the same time as the touch pad or instead of the touch pad. I'm sure that this topic has been covered before but I have not been able to find clear information in the documentation about this. If anyone could point me to the appropriate documentation or mailing list archive, I would be happy to do a little reading. Thanks in advance from a BSD newbie Ralph Ellis From owner-freebsd-hardware@FreeBSD.ORG Tue Jul 18 22:29:08 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F94316A505 for ; Tue, 18 Jul 2006 22:29:08 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from sccmmhc91.asp.att.net (sccmmhc91.asp.att.net [204.127.203.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C02043D46 for ; Tue, 18 Jul 2006 22:29:08 +0000 (GMT) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net ([12.207.12.9]) by sccmmhc91.asp.att.net (sccmmhc91) with ESMTP id <20060718222905m910087avfe>; Tue, 18 Jul 2006 22:29:06 +0000 Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.13.6/8.13.6) with ESMTP id k6IMSvJX024149; Tue, 18 Jul 2006 17:28:58 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.13.6/8.13.6/Submit) id k6IMSuF4024148; Tue, 18 Jul 2006 17:28:56 -0500 (CDT) (envelope-from brooks) Date: Tue, 18 Jul 2006 17:28:56 -0500 From: Brooks Davis To: Ralph Ellis Message-ID: <20060718222856.GA24134@lor.one-eyed-alien.net> References: <200607181804.49339.ralphellis1@netscape.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="X1bOJ3K7DJ5YkBrT" Content-Disposition: inline In-Reply-To: <200607181804.49339.ralphellis1@netscape.ca> User-Agent: Mutt/1.5.11 Cc: freebsd-hardware@freebsd.org Subject: Re: USB Mouse X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jul 2006 22:29:08 -0000 --X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 18, 2006 at 06:04:49PM -0400, Ralph Ellis wrote: > I have a laptop with a touch pad and I would like to use my wireless USB = mouse=20 > either at the same time as the touch pad or instead of the touch pad. I'm= =20 > sure that this topic has been covered before but I have not been able to = find=20 > clear information in the documentation about this. If anyone could point = me=20 > to the appropriate documentation or mailing list archive, I would be hap= py=20 > to do a little reading. Just plug it in and they should both work as long as you are running moused. -- Brooks --X1bOJ3K7DJ5YkBrT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFEvWCmXY6L6fI4GtQRArPRAJ4/MJQQR/+RdEQT87t1TkhVzycFtwCgifTU lmXktoD+wL2w+NnYbkdW+Yg= =s1Jw -----END PGP SIGNATURE----- --X1bOJ3K7DJ5YkBrT-- From owner-freebsd-hardware@FreeBSD.ORG Tue Jul 18 22:37:30 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E99B16A4E0 for ; Tue, 18 Jul 2006 22:37:30 +0000 (UTC) (envelope-from baldur@foo.is) Received: from gremlin.foo.is (gremlin.foo.is [194.105.250.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id A312643D45 for ; Tue, 18 Jul 2006 22:37:29 +0000 (GMT) (envelope-from baldur@foo.is) Received: from 127.0.0.1 (localhost.foo.is [127.0.0.1]) by injector.foo.is (Postfix) with SMTP id 08390DA84A; Tue, 18 Jul 2006 22:37:28 +0000 (GMT) Received: by gremlin.foo.is (Postfix, from userid 1000) id 7A4D3DA847; Tue, 18 Jul 2006 22:37:25 +0000 (GMT) Date: Tue, 18 Jul 2006 22:37:25 +0000 From: Baldur Gislason To: Brooks Davis Message-ID: <20060718223725.GB36671@gremlin.foo.is> References: <200607181804.49339.ralphellis1@netscape.ca> <20060718222856.GA24134@lor.one-eyed-alien.net> In-Reply-To: <20060718222856.GA24134@lor.one-eyed-alien.net> User-Agent: Mutt/1.4.2.1i X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on gremlin.foo.is X-Spam-Level: X-Spam-Status: No, score=-5.9 required=6.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 X-Sanitizer: Foo MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline Cc: Ralph Ellis , freebsd-hardware@freebsd.org Subject: Re: USB Mouse X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jul 2006 22:37:30 -0000 And remember to configure X to use sysmouse and protocol "auto". Baldur On Tue, Jul 18, 2006 at 05:28:56PM -0500, Brooks Davis wrote: > On Tue, Jul 18, 2006 at 06:04:49PM -0400, Ralph Ellis wrote: > > I have a laptop with a touch pad and I would like to use my wireless USB mouse > > either at the same time as the touch pad or instead of the touch pad. I'm > > sure that this topic has been covered before but I have not been able to find > > clear information in the documentation about this. If anyone could point me > > to the appropriate documentation or mailing list archive, I would be happy > > to do a little reading. > > Just plug it in and they should both work as long as you are running > moused. > > -- Brooks From owner-freebsd-hardware@FreeBSD.ORG Wed Jul 19 01:13:20 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3159016A4DD for ; Wed, 19 Jul 2006 01:13:20 +0000 (UTC) (envelope-from landemaine@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9010D43D46 for ; Wed, 19 Jul 2006 01:13:19 +0000 (GMT) (envelope-from landemaine@gmail.com) Received: by ug-out-1314.google.com with SMTP id m2so83768uge for ; Tue, 18 Jul 2006 18:13:18 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=it1y4Om9/itcbhSLucUd7NaXVa3e5WSYTpQnfAnf+OXbBGDgd1xsPhu+Krjs/3Ld8vTh8FpBU2cB2W7CFGWgXuv4mh6mVMS3sx88GLSgEn1kxVZMdo+TtLWFqSw1NztTaUTwTVv26RW4dWTvwx6XNkyNC1swOZfVz9fMHYvQ7X4= Received: by 10.66.221.19 with SMTP id t19mr164675ugg; Tue, 18 Jul 2006 18:11:45 -0700 (PDT) Received: by 10.66.217.9 with HTTP; Tue, 18 Jul 2006 18:11:45 -0700 (PDT) Message-ID: Date: Tue, 18 Jul 2006 22:11:45 -0300 From: "Charles A. Landemaine" To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Improving FreeBSD's hardware compatibility X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jul 2006 01:13:20 -0000 I'm active on the PC-BSD forum, and there is not a single day without a hardware incompatibility issue. There are many mobos that don't even let people install PC-BSD (based on FreeBSD). Aside from the fact that some vendors don't cooperate to release hardware specifications, is there something we could do to revert this situation? How could the community act to change things? I'm sure a lot of people have free time to help, but how? Do you have any idea? This situation has been frustrating for a number of people who have left PC-BSD aside for now, not being able to install on their exotic hardware. Thanks in advance, -- Charles A. Landemaine. From owner-freebsd-hardware@FreeBSD.ORG Wed Jul 19 04:27:38 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81F3C16A4DA for ; Wed, 19 Jul 2006 04:27:38 +0000 (UTC) (envelope-from ralphellis1@netscape.ca) Received: from smtp-1.vancouver.ipapp.com (smtp-1.vancouver.ipapp.com [216.152.192.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4063043D45 for ; Wed, 19 Jul 2006 04:27:38 +0000 (GMT) (envelope-from ralphellis1@netscape.ca) Received: from [192.168.123.100] ([172.169.13.232]) by smtp-1.vancouver.ipapp.com ; Tue, 18 Jul 2006 21:27:35 -0700 From: Ralph Ellis To: freebsd-hardware@freebsd.org Date: Wed, 19 Jul 2006 00:27:25 -0400 User-Agent: KMail/1.9.3 References: <200607181804.49339.ralphellis1@netscape.ca> <20060718222856.GA24134@lor.one-eyed-alien.net> In-Reply-To: <20060718222856.GA24134@lor.one-eyed-alien.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607190027.26131.ralphellis1@netscape.ca> X-Rcpt-To: X-Country: US Subject: Re: USB Mouse X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jul 2006 04:27:38 -0000 On Tuesday 18 July 2006 18:28, you wrote: > On Tue, Jul 18, 2006 at 06:04:49PM -0400, Ralph Ellis wrote: > > I have a laptop with a touch pad and I would like to use my wireless USB > > mouse either at the same time as the touch pad or instead of the touch > > pad. I'm sure that this topic has been covered before but I have not been > > able to find clear information in the documentation about this. If anyone > > could point me to the appropriate documentation or mailing list archive, > > I would be happy to do a little reading. > > Just plug it in and they should both work as long as you are running > moused. > > -- Brooks As I get further into the documentation, I should be seeing a /dev/usm0 or other numbered device in my /dev folder. When my system boots up, it sees the mouse as /dev/uhid0 but moused will not recognize the mouse when I type moused -p /dev/uhid0 -t auto Do I need to create a usm0 device and link it somehow or is this just a case of faulty hardware detection? The touch pad mouse works just fine. Thanks Ralph Ellis From owner-freebsd-hardware@FreeBSD.ORG Wed Jul 19 06:25:29 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7917016A4DA; Wed, 19 Jul 2006 06:25:29 +0000 (UTC) (envelope-from ps@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AF8B43D4C; Wed, 19 Jul 2006 06:25:29 +0000 (GMT) (envelope-from ps@freebsd.org) Received: from [192.168.1.88] (64-142-76-135.dsl.static.sonic.net [64.142.76.135]) by elvis.mu.org (Postfix) with ESMTP id 0B25C1A3C1E; Tue, 18 Jul 2006 23:25:29 -0700 (PDT) Message-ID: <44BDD058.5030607@freebsd.org> Date: Tue, 18 Jul 2006 23:25:28 -0700 From: Paul Saab User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060530) MIME-Version: 1.0 To: John Baldwin References: <1152697468.31818.15.camel@olipc.insign.local> <1153221904.23956.25.camel@olipc.insign.local> <200607181500.21683.jhb@freebsd.org> In-Reply-To: <200607181500.21683.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: David Christensen , Olivier Mueller , freebsd-hardware@freebsd.org Subject: Re: dell poweredge 1950 : not rebooting under 6.1 (sometimes) + bce0 issues X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jul 2006 06:25:29 -0000 revision 1.4 needs to be MFC'd John Baldwin wrote: > On Tuesday 18 July 2006 07:25, Olivier Mueller wrote: > >> On Wed, 2006-07-12 at 11:44 +0200, Olivier Mueller wrote: >> >>> Any guess about what I should try? I recompiled the kernel >>> with & without apci support or some different options, but it didn't >>> helped yet. >>> >> Another problem: I wanted to transfer large amount of data (10GB) using >> rsync via the network, and just after 60MB, the network card won't >> answser anymore, and here is what is displayed in dmesg: >> >> bce0: /usr/src/sys/dev/bce/if_bce.c(4644): Error mapping mbuf into TX >> chain! >> bce0: /usr/src/sys/dev/bce/if_bce.c(4644): Error mapping mbuf into TX >> chain! >> bce0: /usr/src/sys/dev/bce/if_bce.c(4644): Error mapping mbuf into TX >> chain! >> [...] >> > > This sounds like it is out of tx descriptors. Do you ever get a watchdog > timeout message? If not, can you try this patch: > > Index: if_bce.c > =================================================================== > RCS file: /usr/cvs/src/sys/dev/bce/if_bce.c,v > retrieving revision 1.5 > diff -u -r1.5 if_bce.c > --- if_bce.c 12 Jul 2006 23:13:09 -0000 1.5 > +++ if_bce.c 18 Jul 2006 18:59:45 -0000 > @@ -4391,6 +4391,9 @@ > DBRUNIF(1, sc->tx_mbuf_alloc--); > > ifp->if_opackets++; > + > + /* Clear the TX timeout timer. */ > + ifp->if_timer = 0; > } > > sc->used_tx_bd--; > @@ -4406,9 +4409,6 @@ > BUS_SPACE_BARRIER_READ); > } > > - /* Clear the TX timeout timer. */ > - ifp->if_timer = 0; > - > /* Clear the tx hardware queue full flag. */ > if ((sc->used_tx_bd + BCE_TX_SLACK_SPACE) < USABLE_TX_BD) { > DBRUNIF((ifp->if_drv_flags & IFF_DRV_OACTIVE), > @@ -5031,10 +5031,12 @@ > > /* DBRUN(BCE_FATAL, bce_breakpoint(sc)); */ > > + BCE_LOCK(sc); > ifp->if_drv_flags &= ~IFF_DRV_RUNNING; > > - bce_init(sc); > + bce_init_locked(sc); > ifp->if_oerrors++; > + BCE_UNLOCK(sc); > > } > > > From owner-freebsd-hardware@FreeBSD.ORG Wed Jul 19 06:37:29 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02C3E16A4E0 for ; Wed, 19 Jul 2006 06:37:29 +0000 (UTC) (envelope-from om-lists-bsd@omx.ch) Received: from andromeda.insign.ch (andromeda.insign.ch [195.134.143.165]) by mx1.FreeBSD.org (Postfix) with SMTP id 820DE43D58 for ; Wed, 19 Jul 2006 06:37:27 +0000 (GMT) (envelope-from om-lists-bsd@omx.ch) Received: (qmail 12138 invoked by uid 508); 19 Jul 2006 06:37:25 -0000 Received: from om-lists-bsd@omx.ch by andromeda3 by uid 502 with qmail-scanner-1.21 (avp(2004-05-12). Clear:RC:1(80.254.166.203):. Processed in 0.016854 secs); 19 Jul 2006 06:37:25 -0000 Received: from zux166-203.adsl.green.ch (HELO olipc.insign) ([80.254.166.203]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 19 Jul 2006 06:37:25 -0000 From: Olivier Mueller To: John Baldwin In-Reply-To: <200607181500.21683.jhb@freebsd.org> References: <1152697468.31818.15.camel@olipc.insign.local> <1153221904.23956.25.camel@olipc.insign.local> <200607181500.21683.jhb@freebsd.org> Content-Type: text/plain Date: Wed, 19 Jul 2006 08:37:24 +0200 Message-Id: <1153291045.30250.5.camel@olipc.insign.local> Mime-Version: 1.0 X-Mailer: Evolution 2.0.1 Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@freebsd.org Subject: Re: dell poweredge 1950 : not rebooting under 6.1 (sometimes) + bce0 issues X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jul 2006 06:37:29 -0000 Hi John, and thanks for your feedback! On Tue, 2006-07-18 at 15:00 -0400, John Baldwin wrote: > > On Wed, 2006-07-12 at 11:44 +0200, Olivier Mueller wrote: > > Another problem: I wanted to transfer large amount of data (10GB) using > > rsync via the network, and just after 60MB, the network card won't > > answser anymore, and here is what is displayed in dmesg: > > > > bce0: /usr/src/sys/dev/bce/if_bce.c(4644): Error mapping mbuf into TX > > chain! > > This sounds like it is out of tx descriptors. Do you ever get a watchdog > timeout message? If not, can you try this patch: no watchdog timeout message. I tried your patch, but it doesn't seem to have an effect on the problem yet: Jul 19 08:22:28 dev2006 kernel: bce0: /usr/src/sys/dev/bce/if_bce.c(4644): Error mapping mbuf into TX chain! -patched20060719- Jul 19 08:22:59 dev2006 last message repeated 58 times Jul 19 08:23:34 dev2006 last message repeated 59 times and then the network is not responding anymore. Ready for the next suggestion... :) regards, Olivier From owner-freebsd-hardware@FreeBSD.ORG Wed Jul 19 06:56:10 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7F0816A4E9 for ; Wed, 19 Jul 2006 06:56:10 +0000 (UTC) (envelope-from om-lists-bsd@omx.ch) Received: from andromeda.insign.ch (andromeda.insign.ch [195.134.143.165]) by mx1.FreeBSD.org (Postfix) with SMTP id DA5E743D49 for ; Wed, 19 Jul 2006 06:56:07 +0000 (GMT) (envelope-from om-lists-bsd@omx.ch) Received: (qmail 29715 invoked by uid 508); 19 Jul 2006 06:56:05 -0000 Received: from om-lists-bsd@omx.ch by andromeda3 by uid 502 with qmail-scanner-1.21 (avp(2004-05-12). Clear:RC:1(80.254.166.203):. Processed in 0.022609 secs); 19 Jul 2006 06:56:05 -0000 Received: from zux166-203.adsl.green.ch (HELO olipc.insign) ([80.254.166.203]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 19 Jul 2006 06:56:05 -0000 From: Olivier Mueller To: "Julian H. Stacey" In-Reply-To: <200607181251.k6ICpmZW003636@fire.jhs.private> References: <200607181251.k6ICpmZW003636@fire.jhs.private> Content-Type: text/plain Date: Wed, 19 Jul 2006 08:56:05 +0200 Message-Id: <1153292165.30250.9.camel@olipc.insign.local> Mime-Version: 1.0 X-Mailer: Evolution 2.0.1 Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@freebsd.org Subject: Re: dell poweredge 1950 : not rebooting under 6.1 (sometimes) + bce0 issues X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jul 2006 06:56:10 -0000 On Tue, 2006-07-18 at 14:51 +0200, Julian H. Stacey wrote: > -------- > > On Wed, 2006-07-12 at 11:44 +0200, Olivier Mueller wrote: > > bce0: /usr/src/sys/dev/bce/if_bce.c(4644): Error mapping mbuf into TX > > Maybe try eg /usr/ports/comms/ 44bsd-rdist rdist6 or other coms > packs. to get you by for now, while you & others in parallel > worry about what kernel prob. you'r tickling ? So this could be a problem specific/related to rsync? I just made a quick check transfering 250 MB by ftp from the server, and it worked fine (just one large file), then a rsync of /usr/ports to another server -> crash after just 30MB transfered. Interesting... regards, Olivier From owner-freebsd-hardware@FreeBSD.ORG Wed Jul 19 07:13:07 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B827D16A4DA for ; Wed, 19 Jul 2006 07:13:07 +0000 (UTC) (envelope-from jhs@flat.berklix.net) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA0E043D79 for ; Wed, 19 Jul 2006 07:12:56 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A4F6D.dip.t-dialin.net [84.154.79.109]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id k6J7Cnq2018893; Wed, 19 Jul 2006 09:12:54 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id k6J7CknR007690; Wed, 19 Jul 2006 09:12:46 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost.jhs.private [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id k6J7Ckco042410; Wed, 19 Jul 2006 09:12:46 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200607190712.k6J7Ckco042410@fire.jhs.private> To: Olivier Mueller From: "Julian Stacey" Organization: http://berklix.com Munich Unix, BSD, Internet Consultancy User-agent: EXMH http://beedub.com/exmh/ on FreeBSD http://freebsd.org X-URL: http://berklix.com In-reply-to: Your message of "Wed, 19 Jul 2006 08:56:05 +0200." <1153292165.30250.9.camel@olipc.insign.local> Date: Wed, 19 Jul 2006 09:12:46 +0200 Sender: jhs@flat.berklix.net Cc: freebsd-hardware@freebsd.org Subject: Re: dell poweredge 1950 : not rebooting under 6.1 (sometimes) + bce0 issues X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jul 2006 07:13:07 -0000 > From: Olivier Mueller Olivier Mueller wrote: > On Tue, 2006-07-18 at 14:51 +0200, Julian H. Stacey wrote: > > -------- > > > On Wed, 2006-07-12 at 11:44 +0200, Olivier Mueller wrote: > > > bce0: /usr/src/sys/dev/bce/if_bce.c(4644): Error mapping mbuf into TX > > > > Maybe try eg /usr/ports/comms/ 44bsd-rdist rdist6 or other coms > > packs. to get you by for now, while you & others in parallel > > worry about what kernel prob. you'r tickling ? > > So this could be a problem specific/related to rsync? I just made a Don't know, just thought it might give more perspective to analyse, get job done, & avoid work of decamping to Linux ;-) > quick check transfering 250 MB by ftp from the server, and it worked > fine (just one large file), then a rsync of /usr/ports to another > server -> crash after just 30MB transfered. A kernel here was crashing under load. /usr/ports/sysutils/xmbmon showed high CPU temps. A bigger cooler solved it. Just a thought. -- Julian Stacey. Consultant Unix Net & Sys. Eng., Munich. http://berklix.com Mail in Ascii, HTML=spam. Ihr Rauch = mein allergischer Kopfschmerz. From owner-freebsd-hardware@FreeBSD.ORG Wed Jul 19 07:57:14 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 511A016A4DF for ; Wed, 19 Jul 2006 07:57:14 +0000 (UTC) (envelope-from om-lists-bsd@omx.ch) Received: from andromeda.insign.ch (andromeda.insign.ch [195.134.143.165]) by mx1.FreeBSD.org (Postfix) with SMTP id 6FCA243D45 for ; Wed, 19 Jul 2006 07:57:11 +0000 (GMT) (envelope-from om-lists-bsd@omx.ch) Received: (qmail 14753 invoked by uid 508); 19 Jul 2006 07:57:07 -0000 Received: from om-lists-bsd@omx.ch by andromeda3 by uid 502 with qmail-scanner-1.21 (avp(2004-05-12). Clear:RC:1(80.254.166.203):. Processed in 0.01874 secs); 19 Jul 2006 07:57:07 -0000 Received: from zux166-203.adsl.green.ch (HELO olipc.insign) ([80.254.166.203]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 19 Jul 2006 07:57:06 -0000 From: Olivier Mueller To: freebsd-hardware@freebsd.org In-Reply-To: <200607190712.k6J7Ckco042410@fire.jhs.private> References: <200607190712.k6J7Ckco042410@fire.jhs.private> Content-Type: text/plain Date: Wed, 19 Jul 2006 09:57:06 +0200 Message-Id: <1153295827.30250.30.camel@olipc.insign.local> Mime-Version: 1.0 X-Mailer: Evolution 2.0.1 Content-Transfer-Encoding: 7bit Subject: Re: dell poweredge 1950 : not rebooting under 6.1 (sometimes) + bce0 issues X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jul 2006 07:57:14 -0000 On Wed, 2006-07-19 at 09:12 +0200, Julian Stacey wrote: > > So this could be a problem specific/related to rsync? I just made a > > Don't know, just thought it might give more perspective to analyse, > get job done, & avoid work of decamping to Linux ;-) :-) well, I'm trying to move _from_ linux, so I won't give up so quickly, don't worry :). I know it's quite a new server (just came out a few weeks ago). I'd rather had a 1850 instead (network card = em0, never got problems here), but it's a server replacement case (an old 2550), so they prefered to give the newest model... So it seems the new network interfaces are not yet supported very well: bce0: bce1: (or that I have another problem...). Is there anyone else around running freebsd on a 1950? > A kernel here was crashing under load. /usr/ports/sysutils/xmbmon > showed high CPU temps. A bigger cooler solved it. Just a thought. quite difficult in my case, no more free space in the (1U) server for that (and the coolers are pretty big already) :) regards, Olivier From owner-freebsd-hardware@FreeBSD.ORG Wed Jul 19 08:02:58 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D8EF16A4DA for ; Wed, 19 Jul 2006 08:02:58 +0000 (UTC) (envelope-from om-lists-bsd@omx.ch) Received: from andromeda.insign.ch (andromeda.insign.ch [195.134.143.165]) by mx1.FreeBSD.org (Postfix) with SMTP id CED7443D6E for ; Wed, 19 Jul 2006 08:02:53 +0000 (GMT) (envelope-from om-lists-bsd@omx.ch) Received: (qmail 20967 invoked by uid 508); 19 Jul 2006 08:02:49 -0000 Received: from om-lists-bsd@omx.ch by andromeda3 by uid 502 with qmail-scanner-1.21 (avp(2004-05-12). Clear:RC:1(80.254.166.203):. Processed in 0.016618 secs); 19 Jul 2006 08:02:49 -0000 Received: from zux166-203.adsl.green.ch (HELO olipc.insign) ([80.254.166.203]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 19 Jul 2006 08:02:49 -0000 From: Olivier Mueller To: freebsd-hardware@freebsd.org In-Reply-To: <1153295827.30250.30.camel@olipc.insign.local> References: <200607190712.k6J7Ckco042410@fire.jhs.private> <1153295827.30250.30.camel@olipc.insign.local> Content-Type: text/plain Date: Wed, 19 Jul 2006 10:02:49 +0200 Message-Id: <1153296169.30250.32.camel@olipc.insign.local> Mime-Version: 1.0 X-Mailer: Evolution 2.0.1 Content-Transfer-Encoding: 7bit Subject: Re: dell poweredge 1950 : not rebooting under 6.1 (sometimes) + bce0 issues X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jul 2006 08:02:58 -0000 On Wed, 2006-07-19 at 09:57 +0200, Olivier Mueller wrote: > So it seems the new network interfaces are not yet supported very well: > bce0: > bce1: > (or that I have another problem...). Is there anyone else around > running freebsd on a 1950? PS: it seems to be a problem on the poweredge 2950 too: http://lists.freebsd.org/pipermail/freebsd-bugs/2006-July/019351.html "misc/100138: Unstable of Broadcom NetXtreme II (BCM5708) PCI/PCIe Gigabit Ethernet" & http://www.freebsd.org/cgi/query-pr.cgi?pr=100138 O. From owner-freebsd-hardware@FreeBSD.ORG Wed Jul 19 08:11:41 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E778616A4E0 for ; Wed, 19 Jul 2006 08:11:41 +0000 (UTC) (envelope-from ps@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A00443D73 for ; Wed, 19 Jul 2006 08:11:41 +0000 (GMT) (envelope-from ps@freebsd.org) Received: from [192.168.1.44] (64-142-76-135.dsl.static.sonic.net [64.142.76.135]) by elvis.mu.org (Postfix) with ESMTP id F05A21A3C1E; Wed, 19 Jul 2006 01:11:40 -0700 (PDT) Message-ID: <44BDE937.7070501@freebsd.org> Date: Wed, 19 Jul 2006 01:11:35 -0700 From: Paul Saab User-Agent: Mail/News 1.5.0.2 (Macintosh/20060324) MIME-Version: 1.0 To: Olivier Mueller References: <200607190712.k6J7Ckco042410@fire.jhs.private> <1153295827.30250.30.camel@olipc.insign.local> <1153296169.30250.32.camel@olipc.insign.local> In-Reply-To: <1153296169.30250.32.camel@olipc.insign.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@freebsd.org Subject: Re: dell poweredge 1950 : not rebooting under 6.1 (sometimes) + bce0 issues X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jul 2006 08:11:42 -0000 http://yogurt.org/FreeBSD/if_bce.c This is the version of bce I just merged into RELENG_6 to fix this problem. Olivier Mueller wrote: > On Wed, 2006-07-19 at 09:57 +0200, Olivier Mueller wrote: > >> So it seems the new network interfaces are not yet supported very well: >> bce0: >> bce1: >> (or that I have another problem...). Is there anyone else around >> running freebsd on a 1950? >> > > PS: it seems to be a problem on the poweredge 2950 too: > http://lists.freebsd.org/pipermail/freebsd-bugs/2006-July/019351.html > "misc/100138: Unstable of Broadcom NetXtreme II (BCM5708) PCI/PCIe > Gigabit Ethernet" > > & http://www.freebsd.org/cgi/query-pr.cgi?pr=100138 > > O. > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > > From owner-freebsd-hardware@FreeBSD.ORG Wed Jul 19 09:35:54 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FB4D16A4DA for ; Wed, 19 Jul 2006 09:35:54 +0000 (UTC) (envelope-from om-lists-bsd@omx.ch) Received: from andromeda.insign.ch (andromeda.insign.ch [195.134.143.165]) by mx1.FreeBSD.org (Postfix) with SMTP id 04D3543D45 for ; Wed, 19 Jul 2006 09:35:50 +0000 (GMT) (envelope-from om-lists-bsd@omx.ch) Received: (qmail 9164 invoked by uid 508); 19 Jul 2006 09:35:46 -0000 Received: from om-lists-bsd@omx.ch by andromeda3 by uid 502 with qmail-scanner-1.21 (avp(2004-05-12). Clear:RC:1(80.254.166.203):. Processed in 0.023465 secs); 19 Jul 2006 09:35:46 -0000 Received: from zux166-203.adsl.green.ch (HELO olipc.insign) ([80.254.166.203]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 19 Jul 2006 09:35:46 -0000 From: Olivier Mueller To: freebsd-hardware@freebsd.org In-Reply-To: <44BDE937.7070501@freebsd.org> References: <200607190712.k6J7Ckco042410@fire.jhs.private> <1153295827.30250.30.camel@olipc.insign.local> <1153296169.30250.32.camel@olipc.insign.local> <44BDE937.7070501@freebsd.org> Content-Type: text/plain Date: Wed, 19 Jul 2006 11:35:46 +0200 Message-Id: <1153301746.31113.10.camel@olipc.insign.local> Mime-Version: 1.0 X-Mailer: Evolution 2.0.1 Content-Transfer-Encoding: 7bit Subject: Re: dell poweredge 1950 : not rebooting under 6.1 (sometimes) + bce0 issues X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jul 2006 09:35:54 -0000 On Wed, 2006-07-19 at 01:11 -0700, Paul Saab wrote: > http://yogurt.org/FreeBSD/if_bce.c > This is the version of bce I just merged into RELENG_6 to fix this problem. great, it fixes this issue, thanks! What was the problem, if I may ask? New hardware not 100% compatible with the driver? Now the last (I hope) thing I would like to fix before bringing the server to its rack is the reboot problem (cf. initial post of this thread): on "shutdown -r now", it stops (crahes? kbd not responsive, ctrl-alt-del not working for example) here: http://omx.ch/om/stuff/freebsdPE1950.jpg . regards to California! Olivier From owner-freebsd-hardware@FreeBSD.ORG Wed Jul 19 15:04:26 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 863D116A530 for ; Wed, 19 Jul 2006 15:04:26 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from sccmmhc92.asp.att.net (sccmmhc92.asp.att.net [204.127.203.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC00F43D67 for ; Wed, 19 Jul 2006 15:04:18 +0000 (GMT) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net ([12.207.12.9]) by sccmmhc92.asp.att.net (sccmmhc92) with ESMTP id <20060719150417m92002skeee>; Wed, 19 Jul 2006 15:04:17 +0000 Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.13.6/8.13.6) with ESMTP id k6JF4B3c032733; Wed, 19 Jul 2006 10:04:12 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.13.6/8.13.6/Submit) id k6JF4A6b032727; Wed, 19 Jul 2006 10:04:10 -0500 (CDT) (envelope-from brooks) Date: Wed, 19 Jul 2006 10:04:10 -0500 From: Brooks Davis To: Ralph Ellis Message-ID: <20060719150410.GA32499@lor.one-eyed-alien.net> References: <200607181804.49339.ralphellis1@netscape.ca> <20060718222856.GA24134@lor.one-eyed-alien.net> <200607190027.26131.ralphellis1@netscape.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="45Z9DzgjV8m4Oswq" Content-Disposition: inline In-Reply-To: <200607190027.26131.ralphellis1@netscape.ca> User-Agent: Mutt/1.5.11 Cc: freebsd-hardware@freebsd.org Subject: Re: USB Mouse X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jul 2006 15:04:26 -0000 --45Z9DzgjV8m4Oswq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 19, 2006 at 12:27:25AM -0400, Ralph Ellis wrote: > On Tuesday 18 July 2006 18:28, you wrote: > > On Tue, Jul 18, 2006 at 06:04:49PM -0400, Ralph Ellis wrote: > > > I have a laptop with a touch pad and I would like to use my wireless = USB > > > mouse either at the same time as the touch pad or instead of the touch > > > pad. I'm sure that this topic has been covered before but I have not = been > > > able to find clear information in the documentation about this. If an= yone > > > could point me to the appropriate documentation or mailing list archi= ve,=20 > > > I would be happy to do a little reading. > > > > Just plug it in and they should both work as long as you are running > > moused. >=20 > As I get further into the documentation, I should be seeing a /dev/usm0 o= r=20 > other numbered device in my /dev folder. When my system boots up, it sees= the=20 > mouse as /dev/uhid0 but moused will not recognize the mouse when I type > moused -p /dev/uhid0 -t auto > Do I need to create a usm0 device and link it somehow or is this just a c= ase=20 > of faulty hardware detection? > The touch pad mouse works just fine. Ah, you have one of the uhid mice. Those don't just work quite yet. I believe there are patches to either moused or uhid to support them. -- Brooks --45Z9DzgjV8m4Oswq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFEvknpXY6L6fI4GtQRAqF+AJ4+60ES7/kbi1IzekhN9tSv9aJUQwCcCnx5 6RkafyBtgCefsswseiKt/d0= =eXoO -----END PGP SIGNATURE----- --45Z9DzgjV8m4Oswq-- From owner-freebsd-hardware@FreeBSD.ORG Thu Jul 20 10:32:31 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6F3216A4DF for ; Thu, 20 Jul 2006 10:32:31 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail01.syd.optusnet.com.au (mail01.syd.optusnet.com.au [211.29.132.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id F248A43D4C for ; Thu, 20 Jul 2006 10:32:30 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail01.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k6KAWS2S020810 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 20 Jul 2006 20:32:28 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k6KAWStu001541; Thu, 20 Jul 2006 20:32:28 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k6KAWS4v001540; Thu, 20 Jul 2006 20:32:28 +1000 (EST) (envelope-from peter) Date: Thu, 20 Jul 2006 20:32:28 +1000 From: Peter Jeremy To: "Charles A. Landemaine" Message-ID: <20060720103228.GA716@turion.vk2pj.dyndns.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MGYHOYXEY6WxJCY8" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-hardware@freebsd.org Subject: Re: Improving FreeBSD's hardware compatibility X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jul 2006 10:32:31 -0000 --MGYHOYXEY6WxJCY8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, 2006-Jul-18 22:11:45 -0300, Charles A. Landemaine wrote: >Aside from the fact that some vendors don't cooperate to release >hardware specifications, is there something we could do to revert this >situation? I suspect the major problems are lack of interface documentation for the various chips and non-compliance with standards on things like ACPI. I don't believe there's a general solution to the problem, rather work-arounds need to be developed on a case-by-case basis. > How could the community act to change things? Getting action from vendors has been unsuccessful in the past - the Free OS community (Linux + *BSD) is too small for vendors to be concerned about. I suspect the best solution is to publicise configurations that are known to work and what problems exist with other configurations. --=20 Peter Jeremy --MGYHOYXEY6WxJCY8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEv1TD/opHv/APuIcRAoAcAJ0a0yhI3Gr92ZLKplUP3Lf4akciuACdEOVF /5iN4sFDvO65dKSYo0FQKlA= =HGmn -----END PGP SIGNATURE----- --MGYHOYXEY6WxJCY8-- From owner-freebsd-hardware@FreeBSD.ORG Thu Jul 20 11:28:18 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDC8F16A4DF for ; Thu, 20 Jul 2006 11:28:18 +0000 (UTC) (envelope-from nitro@263.net) Received: from smtp.263.net (263.net.cn [211.150.96.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 206A143D82 for ; Thu, 20 Jul 2006 11:28:06 +0000 (GMT) (envelope-from nitro@263.net) Received: from origin.intron.ac (unknown [127.0.0.1]) by smtp.263.net (Postfix) with ESMTP id 8997FF1921 for ; Thu, 20 Jul 2006 19:28:06 +0800 (CST) X-KSVirus-check: 0 References: <20060720103228.GA716@turion.vk2pj.dyndns.org> In-Reply-To: <20060720103228.GA716@turion.vk2pj.dyndns.org> From: "Intron" To: Peter Jeremy Date: Thu, 20 Jul 2006 19:25:27 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312"; format=flowed Content-Transfer-Encoding: 7bit Message-Id: <1153394879.65957@origin.intron.ac> Cc: freebsd-hackers@freebsd.org, "Charles A. Landemaine" , freebsd-hardware@freebsd.org Subject: Re: Improving FreeBSD's hardware compatibility X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jul 2006 11:28:19 -0000 Peter Jeremy wrote: > On Tue, 2006-Jul-18 22:11:45 -0300, Charles A. Landemaine wrote: >>Aside from the fact that some vendors don't cooperate to release >>hardware specifications, is there something we could do to revert this >>situation? > > I suspect the major problems are lack of interface documentation for > the various chips and non-compliance with standards on things like > ACPI. I don't believe there's a general solution to the problem, > rather work-arounds need to be developed on a case-by-case basis. > >> How could the community act to change things? > > Getting action from vendors has been unsuccessful in the past - the > Free OS community (Linux + *BSD) is too small for vendors to be > concerned about. I cannot agree with you. Linux has achieved much more support from hardware vendors than FreeBSD. You may look in Linux source code. In linux-2.6.x/drivers/, there are so many hardware drivers. On the other hand, so many hardware vendors (especially some small enterprises, which are eager to obtain software support) have publicized data sheets of their integrated circuit products, but so few people would write hardware driver for FreeBSD. > > I suspect the best solution is to publicise configurations that are > known to work and what problems exist with other configurations. > > -- > Peter Jeremy FreeBSD must be more open than before. Otherwise, it will lose developping energy/vitality and fall behind the time. ------------------------------------------------------------------------ From Beijing, China From owner-freebsd-hardware@FreeBSD.ORG Thu Jul 20 13:18:32 2006 Return-Path: X-Original-To: freebsd-hardware@FreeBSD.ORG Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5184E16A4E2 for ; Thu, 20 Jul 2006 13:18:32 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A6F043D53 for ; Thu, 20 Jul 2006 13:18:31 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (slghcx@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k6KDIO5n092992 for ; Thu, 20 Jul 2006 15:18:30 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k6KDIOKH092991; Thu, 20 Jul 2006 15:18:24 +0200 (CEST) (envelope-from olli) Date: Thu, 20 Jul 2006 15:18:24 +0200 (CEST) Message-Id: <200607201318.k6KDIOKH092991@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hardware@FreeBSD.ORG In-Reply-To: <1153394879.65957@origin.intron.ac> X-Newsgroups: list.freebsd-hardware User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Thu, 20 Jul 2006 15:18:30 +0200 (CEST) Cc: Subject: Re: Improving FreeBSD's hardware compatibility X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hardware@FreeBSD.ORG List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jul 2006 13:18:32 -0000 Intron wrote: > Peter Jeremy wrote: > > Getting action from vendors has been unsuccessful in the past - the > > Free OS community (Linux + *BSD) is too small for vendors to be > > concerned about. > > I cannot agree with you. Linux has achieved much more support from > hardware vendors than FreeBSD. Interestingly, when I looked for a new laptop last year, it turned out that the number of laptops that ran FreeBSD was greater than those that ran Linux. (I finally chose a Samsung X20-XVM 1600-V, which works perfectly fine for me except for the built-in winmodem [which I don't need anyway]. A Linux live CD didn't even boot on it.) > You may look in Linux source code. > In linux-2.6.x/drivers/, there are so many hardware drivers. Yeah, most of which are crap. :-) The raw number of drivers says _nothing_ about hardware vendors' support. > > I suspect the best solution is to publicise configurations that are > > known to work and what problems exist with other configurations. I tend to agree with Peter here. By the way, a very good resource for hardware support information is the search facility at Rambler: http://freebsd.rambler.ru/ Best regards Oliver PS: I think this thread might be inappropriate for the -hackers list. How about moving it to either -hardware or -chat? (I watch them all, so either is fine with me.) -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "Documentation is like sex; when it's good, it's very, very good, and when it's bad, it's better than nothing." -- Dick Brandon From owner-freebsd-hardware@FreeBSD.ORG Thu Jul 20 18:12:30 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42E2B16A4E0; Thu, 20 Jul 2006 18:12:30 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 802A643D7E; Thu, 20 Jul 2006 18:12:18 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (u8flq0hzmiogvbs3@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id k6KICHRY061266; Thu, 20 Jul 2006 11:12:17 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id k6KICGJ8061263; Thu, 20 Jul 2006 11:12:16 -0700 (PDT) (envelope-from jmg) Date: Thu, 20 Jul 2006 11:12:16 -0700 From: John-Mark Gurney To: Intron Message-ID: <20060720181216.GJ96589@funkthat.com> Mail-Followup-To: Intron , Peter Jeremy , freebsd-hackers@freebsd.org, "Charles A. Landemaine" , freebsd-hardware@freebsd.org References: <20060720103228.GA716@turion.vk2pj.dyndns.org> <1153397244.66653@origin.intron.ac> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1153397244.66653@origin.intron.ac> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: Peter Jeremy , "Charles A. Landemaine" , freebsd-hardware@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Improving FreeBSD's hardware compatibility X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jul 2006 18:12:30 -0000 Intron wrote this message on Thu, Jul 20, 2006 at 19:25 +0800: > On the other hand, so many hardware vendors (especially some small > enterprises, which are eager to obtain software support) > have publicized data sheets of their integrated circuit products, > but so few people would write hardware driver for FreeBSD. I haven't seen this. The only case that I can think of is due to developers not having the hardware, or a need to use said hardware, so nothing happens... Do you have a list of hardware that has documntation available that needs device drivers to be written? -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hardware@FreeBSD.ORG Thu Jul 20 18:13:47 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4EC416A4DD for ; Thu, 20 Jul 2006 18:13:47 +0000 (UTC) (envelope-from j_guojun@lbl.gov) Received: from smtp114.sbc.mail.mud.yahoo.com (smtp114.sbc.mail.mud.yahoo.com [68.142.198.213]) by mx1.FreeBSD.org (Postfix) with SMTP id A4C8743D7C for ; Thu, 20 Jul 2006 18:13:28 +0000 (GMT) (envelope-from j_guojun@lbl.gov) Received: (qmail 52791 invoked from network); 20 Jul 2006 18:13:28 -0000 Received: from unknown (HELO ?192.168.2.10?) (jinmtb@sbcglobal.net@68.127.175.91 with plain) by smtp114.sbc.mail.mud.yahoo.com with SMTP; 20 Jul 2006 18:13:27 -0000 Message-ID: <44BFC80C.8040000@lbl.gov> Date: Thu, 20 Jul 2006 11:14:36 -0700 From: "Jin Guojun [VFFS]" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060317 X-Accept-Language: zh, zh-CN, en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <200607201318.k6KDIOKH092991@lurza.secnetix.de> In-Reply-To: <200607201318.k6KDIOKH092991@lurza.secnetix.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Improving FreeBSD's hardware compatibility X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jul 2006 18:13:47 -0000 Oliver Fromme wrote: >Intron wrote: > > Peter Jeremy wrote: > > > Getting action from vendors has been unsuccessful in the past - the > > > Free OS community (Linux + *BSD) is too small for vendors to be > > > concerned about. > > > > I cannot agree with you. Linux has achieved much more support from > > hardware vendors than FreeBSD. > >Interestingly, when I looked for a new laptop last year, >it turned out that the number of laptops that ran FreeBSD >was greater than those that ran Linux. (I finally chose >a Samsung X20-XVM 1600-V, which works perfectly fine for >me except for the built-in winmodem [which I don't need >anyway]. A Linux live CD didn't even boot on it.) > > Really depends on what environment you are in and things are case by case. Not long ago, I post some question to hardware list about booting FreeBSD on a Sony PCG-6J2L laptop, which cannot be even found/supported on Sony web site :-( , for my friend. I got no answer back. A couple of issues: (1) all FreeBSD releases can be installed on a USB drive, but none of these release can boot after FreeBSD installed. (2) I build a live FreeBSD CD (Freesbie), which can boot, but cannot configure the NIC (Yukon-FE). So, I tried different Linux. RedHat is the worst one to forget. Debian is ok and Suse Linux 10.1 seems to be the best for this laptop. Suse Linux detected the NIC as sky0. > > You may look in Linux source code. > > In linux-2.6.x/drivers/, there are so many hardware drivers. > >Yeah, most of which are crap. :-) The raw number of >drivers says _nothing_ about hardware vendors' support. > > FreeBSD has its merit and other OSs have their merits. If we want to make FreeBSD more stronger, we need to learn others advantages, alert all disadvantages, not just blame them. Blaming makes things going backward, and learning makes history moving forward. I agree with originator's idea although it is not easy because free OS community is small. -Jin From owner-freebsd-hardware@FreeBSD.ORG Fri Jul 21 00:00:20 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E4CB16A4DF for ; Fri, 21 Jul 2006 00:00:19 +0000 (UTC) (envelope-from jrhett@mail.meer.net) Received: from outbound0.sv.meer.net (outbound0.mx.meer.net [209.157.153.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id A292C43D4C for ; Fri, 21 Jul 2006 00:00:19 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id k6L00Jih065965 for ; Thu, 20 Jul 2006 17:00:19 -0700 (PDT) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id k6L00IO5001758 for ; Thu, 20 Jul 2006 17:00:18 -0700 (PDT) (envelope-from jrhett@mail.meer.net) Received: (from jrhett@localhost) by mail.meer.net (8.13.3/8.13.3) id k6L00IBI001757 for freebsd-hardware@freebsd.org; Thu, 20 Jul 2006 17:00:18 -0700 (PDT) (envelope-from jrhett) Date: Thu, 20 Jul 2006 17:00:18 -0700 From: Jo Rhett To: freebsd-hardware@freebsd.org Message-ID: <20060721000018.GA99237@svcolo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i Subject: device busy -- no locks? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jul 2006 00:00:20 -0000 root@scapa 45# tip com1 /dev/cuad0: Device busy link down Hm. Really? root@scapa 46# ls /var/spool/lock root@scapa 47# fstat /dev/ttyd0 USER CMD PID FD MOUNT INUM MODE SZ|DV R/W NAME root@scapa 48# ps -ajwx |grep d0 root 12 0 0 0 0 WL ?? 0:00.05 [irq1: atkbd0] root 372 0 0 0 0 DL ?? 0:00.24 [md0] No locks? No processes using it. Okay, this is uncool. And yet "ktrace tip com1" and "kdump -f ktrace.out" clearly show: 50461 tip CALL open(0x8059030,0x6,0) 50461 tip NAMI "/dev/cuad0" 50461 tip RET open -1 errno 16 Device busy Where is this lock hiding? What process has this device locked? NOTE: at this time I am suspecting that CD is being misread (it's not present - I have a break out box on the line) and that this problem is somehow tied to that. This problem appears at random after login has exerted itself on the system. I've disabled the getty on ttyd0 and login has timed out, but it continues to show "device busy". root@scapa 51# uname -a FreeBSD scapa.sv 6.0-RELEASE FreeBSD 6.0-RELEASE #4: Fri Nov 11 13:29:33 PST 2005 root@barrel.svcolo.com:/usr/obj/usr/src/sys/GENERIC i386 -- Jo Rhett senior geek SVcolo : Silicon Valley Colocation From owner-freebsd-hardware@FreeBSD.ORG Fri Jul 21 00:47:42 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1137316A4DE for ; Fri, 21 Jul 2006 00:47:42 +0000 (UTC) (envelope-from jrhett@mail.meer.net) Received: from outbound0.sv.meer.net (outbound0.mx.meer.net [209.157.153.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AB6543D49 for ; Fri, 21 Jul 2006 00:47:41 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id k6L0lfih068471; Thu, 20 Jul 2006 17:47:41 -0700 (PDT) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id k6L0lVQS014688; Thu, 20 Jul 2006 17:47:31 -0700 (PDT) (envelope-from jrhett@mail.meer.net) Received: (from jrhett@localhost) by mail.meer.net (8.13.3/8.13.3) id k6L0lVeO014687; Thu, 20 Jul 2006 17:47:31 -0700 (PDT) (envelope-from jrhett) Date: Thu, 20 Jul 2006 17:47:31 -0700 From: Jo Rhett To: "Rick C. Petty" Message-ID: <20060721004731.GC8868@svcolo.com> References: <20060721000018.GA99237@svcolo.com> <20060721001607.GA64376@megan.kiwi-computer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060721001607.GA64376@megan.kiwi-computer.com> Organization: svcolo.com User-Agent: Mutt/1.5.9i Cc: freebsd-hardware@freebsd.org Subject: Re: device busy -- no locks? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jul 2006 00:47:42 -0000 Thanks for the super-quick reply! Responses are inline... On Thu, Jul 20, 2006 at 07:16:07PM -0500, Rick C. Petty wrote: > > root@scapa 47# fstat /dev/ttyd0 > > USER CMD PID FD MOUNT INUM MODE SZ|DV R/W NAME > > What about "fstat /dev/cuad0" ? Anyway, I've found that fstat is useless, > try using sysutils/lsof instead. Sorry, yes. Same results. And if lsof shows things that fstat doesn't, then this is a bug in FreeBSD. But anyway, root@scapa 63# lsof /dev/cuad0 root@scapa 64# lsof /dev/ttyd0 Nada. Also note that this system is pretty bone stock. Standard install, plus mysql and apache. Nothing else would be using the port. It's something that left it locked, and really only "login" could be the culprit. > > root@scapa 48# ps -ajwx |grep d0 > > root 12 0 0 0 0 WL ?? 0:00.05 [irq1: atkbd0] > > root 372 0 0 0 0 DL ?? 0:00.24 [md0] > > try "-axww" instead.. I've noticed that processes with long command lines > don't match a regular grep. Same result. > > No locks? No processes using it. Okay, this is uncool. > > And yet "ktrace tip com1" and "kdump -f ktrace.out" clearly show: > > > > 50461 tip CALL open(0x8059030,0x6,0) > > 50461 tip NAMI "/dev/cuad0" > > 50461 tip RET open -1 errno 16 Device busy > > This isn't very useful. A ktrace on the process that's locking the file > would be. :-P See above. I can't find it. :-( > > NOTE: at this time I am suspecting that CD is being misread (it's not > > present - I have a break out box on the line) and that this problem is > > somehow tied to that. This problem appears at random after login has > > exerted itself on the system. I've disabled the getty on ttyd0 and login > > has timed out, but it continues to show "device busy". > > How did you disable the getty? Was this prior to or after a restart? It > sounds like /etc/ttys is maybe running a process on it. You need to > "killall -HUP init" after changing /etc/ttys. But you probably already > know that. Yes, I change "on" to "off" in /etc/ttys and "kill -1 1" :-) -- Jo Rhett senior geek SVcolo : Silicon Valley Colocation From owner-freebsd-hardware@FreeBSD.ORG Fri Jul 21 01:54:20 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 870FD16A4DD for ; Fri, 21 Jul 2006 01:54:20 +0000 (UTC) (envelope-from mag@intron.ac) Received: from mail.oreilly.com.cn (oreilly.com.cn [211.154.219.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4566A43D46 for ; Fri, 21 Jul 2006 01:54:18 +0000 (GMT) (envelope-from mag@intron.ac) Received: from origin.intron.ac ([210.51.165.237]) (AUTH: LOGIN intron) by mail.oreilly.com.cn with esmtp; Fri, 21 Jul 2006 09:54:11 +0800 id 000C9459.44C033C4.0000EE2B References: <200607201318.k6KDIOKH092991@lurza.secnetix.de> In-Reply-To: <200607201318.k6KDIOKH092991@lurza.secnetix.de> From: "Intron" To: Oliver Fromme Date: Fri, 21 Jul 2006 09:42:40 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312"; format=flowed Content-Transfer-Encoding: 7bit Message-Id: <1153446852.80350@origin.intron.ac> Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Improving FreeBSD's hardware compatibility X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jul 2006 01:54:20 -0000 Oliver Fromme wrote: > Intron wrote: > > Peter Jeremy wrote: > > > Getting action from vendors has been unsuccessful in the past - the > > > Free OS community (Linux + *BSD) is too small for vendors to be > > > concerned about. > > > > I cannot agree with you. Linux has achieved much more support from > > hardware vendors than FreeBSD. > > Interestingly, when I looked for a new laptop last year, > it turned out that the number of laptops that ran FreeBSD > was greater than those that ran Linux. (I finally chose > a Samsung X20-XVM 1600-V, which works perfectly fine for > me except for the built-in winmodem [which I don't need > anyway]. A Linux live CD didn't even boot on it.) Have a look at http://linmodems.org/ before your assertion. How many modems listed on that website are support by FreeBSD? Most of them are installed in laptops and nested on PCI bus. > > > You may look in Linux source code. > > In linux-2.6.x/drivers/, there are so many hardware drivers. > > Yeah, most of which are crap. :-) The raw number of > drivers says _nothing_ about hardware vendors' support. This is a problem of code quality. But at least Linux community has so many volunteers/vendors to write drivers. > > > > I suspect the best solution is to publicise configurations that are > > > known to work and what problems exist with other configurations. > > I tend to agree with Peter here. By the way, a very good > resource for hardware support information is the search > facility at Rambler: http://freebsd.rambler.ru/ > > Best regards > Oliver > > PS: I think this thread might be inappropriate for the > -hackers list. How about moving it to either -hardware > or -chat? (I watch them all, so either is fine with me.) > > -- > Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing > Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd > Any opinions expressed in this message may be personal to the author > and may not necessarily reflect the opinions of secnetix in any way. > > "Documentation is like sex; when it's good, it's very, very good, > and when it's bad, it's better than nothing." > -- Dick Brandon > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" ------------------------------------------------------------------------ From Beijing, China From owner-freebsd-hardware@FreeBSD.ORG Fri Jul 21 03:24:23 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D7C216A4DE for ; Fri, 21 Jul 2006 03:24:23 +0000 (UTC) (envelope-from mag@intron.ac) Received: from mail.oreilly.com.cn (oreilly.com.cn [211.154.219.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7678243D53 for ; Fri, 21 Jul 2006 03:24:17 +0000 (GMT) (envelope-from mag@intron.ac) Received: from origin.intron.ac ([210.51.165.237]) (AUTH: LOGIN intron) by mail.oreilly.com.cn with esmtp; Fri, 21 Jul 2006 11:24:15 +0800 id 000C9459.44C048DF.0000F4DC References: <20060720103228.GA716@turion.vk2pj.dyndns.org> <1153397244.66653@origin.intron.ac> <20060720181216.GJ96589@funkthat.com> In-Reply-To: <20060720181216.GJ96589@funkthat.com> From: "Intron" To: John-Mark Gurney Date: Fri, 21 Jul 2006 11:18:07 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312"; format=flowed Content-Transfer-Encoding: 7bit Message-Id: <1153452255.82099@origin.intron.ac> Cc: freebsd-hardware@freebsd.org Subject: Re: Improving FreeBSD's hardware compatibility X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jul 2006 03:24:23 -0000 John-Mark Gurney wrote: > Intron wrote this message on Thu, Jul 20, 2006 at 19:25 +0800: >> On the other hand, so many hardware vendors (especially some small >> enterprises, which are eager to obtain software support) >> have publicized data sheets of their integrated circuit products, >> but so few people would write hardware driver for FreeBSD. > > I haven't seen this. The only case that I can think of is due to > developers not having the hardware, or a need to use said hardware, > so nothing happens... > > Do you have a list of hardware that has documntation available that > needs device drivers to be written? > > -- > John-Mark Gurney Voice: +1 415 225 5579 > > "All that I will do, has been done, All that I have, has not." > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" Well, I list all hardware products whose data sheets I've seen and which haven't been supported by FreeBSD. 1. Cologne Chip - HFC-S PCI A ISDN Controller IC http://www.colognechip.com/isdn/controllers/main-datasheets.htm FreeBSD only supports ihfc(4), its ISA version, but doesn't support this PCI version. 2. Sigmatel - STIR 4200, USB 1.1 - IrDA 1.3 adapter The data sheet was once published on their website. Both Linux and NetBSD support this chip. 3. Philips SAA 7130/7134, TV decoder This is one of the most popular TV decoder chips on the market. The data sheet can be obtained from the vendor, just as what Linux community has done. 4. USB MIDI device class http://www.usb.org/developers/devclass_docs 5. USB IrDA device class http://www.usb.org/developers/devclass_docs Some new USB-IrDA chips conform to this specification. 6. TI 3410/5052 USB-RS232C adapter http://focus.ti.com/docs/prod/folders/print/tusb3410.html http://focus.ti.com/docs/prod/folders/print/tusb5052.html Please have a look at those Linux device drive websites and perceive the disparity that FreeBSD falls behind: Modem: http://linmodems.org/ Video: http://linux.bytesex.org/ Temperature sensor: http://www.lm-sensors.org/ USB PC Camera: http://mxhaard.free.fr/spca5xx.html Although not all data sheets have been publicized by vendors, but at least FreeBSDers can follow/keep up with Linux community, cannot we? ------------------------------------------------------------------------ From Beijing, China From owner-freebsd-hardware@FreeBSD.ORG Fri Jul 21 04:50:34 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0241916A4DE for ; Fri, 21 Jul 2006 04:50:34 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8068C43D46 for ; Fri, 21 Jul 2006 04:50:33 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (25os925fu7eb6ndx@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id k6L4oWtZ074243; Thu, 20 Jul 2006 21:50:32 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id k6L4oUab074242; Thu, 20 Jul 2006 21:50:30 -0700 (PDT) (envelope-from jmg) Date: Thu, 20 Jul 2006 21:50:30 -0700 From: John-Mark Gurney To: Intron Message-ID: <20060721045029.GL96589@funkthat.com> Mail-Followup-To: John-Mark Gurney , Intron , freebsd-hardware@freebsd.org References: <20060720103228.GA716@turion.vk2pj.dyndns.org> <1153397244.66653@origin.intron.ac> <20060720181216.GJ96589@funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-hardware@freebsd.org Subject: Re: Improving FreeBSD's hardware compatibility X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jul 2006 04:50:34 -0000 Intron wrote this message on Fri, Jul 21, 2006 at 11:18 +0800: > John-Mark Gurney wrote: > > >Intron wrote this message on Thu, Jul 20, 2006 at 19:25 +0800: > >>On the other hand, so many hardware vendors (especially some small > >>enterprises, which are eager to obtain software support) > >>have publicized data sheets of their integrated circuit products, > >>but so few people would write hardware driver for FreeBSD. > > > >I haven't seen this. The only case that I can think of is due to > >developers not having the hardware, or a need to use said hardware, > >so nothing happens... > > > >Do you have a list of hardware that has documntation available that > >needs device drivers to be written? > > Well, I list all hardware products whose data sheets I've seen and which > haven't been supported by FreeBSD. > > 1. Cologne Chip - HFC-S PCI A ISDN Controller IC > http://www.colognechip.com/isdn/controllers/main-datasheets.htm > > FreeBSD only supports ihfc(4), its ISA version, but doesn't > support this PCI version. If the programming interface is the same, then it should be a simple matter of writing a PCI front end, a good junior hacker project... > 2. Sigmatel - STIR 4200, USB 1.1 - IrDA 1.3 adapter > The data sheet was once published on their website. Both Linux and > NetBSD support this chip. FreeBSD's USB stack needs some tender loving from someone... There is an alternative stack I know exists but haven't looked at it yet... The current stack has many issues, and not being locked is a major issue... so, before more drivers are written, we should get a working USB stack first... > 3. Philips SAA 7130/7134, TV decoder > This is one of the most popular TV decoder chips on the market. > The data sheet can be obtained from the vendor, just as what Linux > community has done. analog TV? what's that? isn't everyone going digital? (yes, I know that analog TV will be with us for a long time due to security cams and other uses..) But a decoder isn't much use w/o the rest of the chip... This driver really should be in userland anyways, no point in putting items like this in the kernel... bktr should be broken out where it's just a DMA engine, and all the tuner chips are drivers in userland speaking over the iic device interface... > 4. USB MIDI device class > http://www.usb.org/developers/devclass_docs > > 5. USB IrDA device class > http://www.usb.org/developers/devclass_docs > > Some new USB-IrDA chips conform to this specification. > > 6. TI 3410/5052 USB-RS232C adapter > http://focus.ti.com/docs/prod/folders/print/tusb3410.html > http://focus.ti.com/docs/prod/folders/print/tusb5052.html > > Please have a look at those Linux device drive websites and perceive > the disparity that FreeBSD falls behind: > > Modem: http://linmodems.org/ > Video: http://linux.bytesex.org/ > Temperature sensor: http://www.lm-sensors.org/ > USB PC Camera: http://mxhaard.free.fr/spca5xx.html See above about USB... > Although not all data sheets have been publicized by vendors, but > at least FreeBSDers can follow/keep up with Linux community, cannot we? a) some drivers that aren't that high visibility don't get the demand/attention that they necessarily deserve... Mostly because there is only one or two people interested... There are a couple video capture drivers (saa and cxm) that both are apparently ready, but haven't yet been integrated... I did send mail asking about the cxm licensing issues (it has firmware necessary for operation), but never got a response... b) Many times the vendors ignore FreeBSD... DVIco has continued to fail to provide me w/ the necessary docs, but I think this is more because the person that is providing the docs is asleep at the wheel as others seem to want to give them out, but it's hard when it takes a lot more... Most of the stuff above are small little ones that the vendors don't really care about, but the ones that are really useful and not as easy to find alternatives are much harder... Get writing the drivers... It's a lot easier than people think... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hardware@FreeBSD.ORG Fri Jul 21 06:34:00 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D937116A4E2 for ; Fri, 21 Jul 2006 06:34:00 +0000 (UTC) (envelope-from mag@intron.ac) Received: from mail.oreilly.com.cn (oreilly.com.cn [211.154.219.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F82943D66 for ; Fri, 21 Jul 2006 06:33:50 +0000 (GMT) (envelope-from mag@intron.ac) Received: from origin.intron.ac ([210.51.165.237]) (AUTH: LOGIN intron) by mail.oreilly.com.cn with esmtp; Fri, 21 Jul 2006 14:33:44 +0800 id 000C9459.44C0754B.0000FF4B References: <20060720103228.GA716@turion.vk2pj.dyndns.org> <1153397244.66653@origin.intron.ac> <20060720181216.GJ96589@funkthat.com> <20060721045029.GL96589@funkthat.com> In-Reply-To: <20060721045029.GL96589@funkthat.com> From: "Intron" To: John-Mark Gurney Date: Fri, 21 Jul 2006 14:19:32 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312"; format=flowed Content-Transfer-Encoding: 7bit Message-Id: <1153463627.84529@origin.intron.ac> Cc: freebsd-hardware@freebsd.org Subject: Re: Improving FreeBSD's hardware compatibility X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jul 2006 06:34:00 -0000 John-Mark Gurney wrote: > Intron wrote this message on Fri, Jul 21, 2006 at 11:18 +0800: >> John-Mark Gurney wrote: >> >> >Intron wrote this message on Thu, Jul 20, 2006 at 19:25 +0800: >> >>On the other hand, so many hardware vendors (especially some small >> >>enterprises, which are eager to obtain software support) >> >>have publicized data sheets of their integrated circuit products, >> >>but so few people would write hardware driver for FreeBSD. >> > >> >I haven't seen this. The only case that I can think of is due to >> >developers not having the hardware, or a need to use said hardware, >> >so nothing happens... >> > >> >Do you have a list of hardware that has documntation available that >> >needs device drivers to be written? >> >> Well, I list all hardware products whose data sheets I've seen and which >> haven't been supported by FreeBSD. >> >> 1. Cologne Chip - HFC-S PCI A ISDN Controller IC >> http://www.colognechip.com/isdn/controllers/main-datasheets.htm >> >> FreeBSD only supports ihfc(4), its ISA version, but doesn't >> support this PCI version. > > If the programming interface is the same, then it should be a simple > matter of writing a PCI front end, a good junior hacker project... > >> 2. Sigmatel - STIR 4200, USB 1.1 - IrDA 1.3 adapter >> The data sheet was once published on their website. Both Linux and >> NetBSD support this chip. > > FreeBSD's USB stack needs some tender loving from someone... There > is an alternative stack I know exists but haven't looked at it yet... > The current stack has many issues, and not being locked is a major > issue... so, before more drivers are written, we should get a working > USB stack first... I agree with you. But USB stack is quite a little complicated. I have read USB specifications and bought a more understandable book. Would you like to co-operate with me? I would write USB stack in C++ so that base code can be easier to reuse. But on freebsd-hackers@, this idea encountered strong objection. > >> 3. Philips SAA 7130/7134, TV decoder >> This is one of the most popular TV decoder chips on the market. >> The data sheet can be obtained from the vendor, just as what Linux >> community has done. > > analog TV? what's that? isn't everyone going digital? (yes, I know > that analog TV will be with us for a long time due to security cams > and other uses..) Do you believe that current Intel Pentium 4 or AMD Athlon XP can process analog TV in full frame size and full frame rate (no larger than 767x575, 25 FPS, either of NTSC/PAL/SECAM) freely? Do you really believe that current Intel Pentium 4 or AMD Athlon XP can process much higher bitstream HDTV? > > But a decoder isn't much use w/o the rest of the chip... This driver > really should be in userland anyways, no point in putting items like > this in the kernel... bktr should be broken out where it's just a > DMA engine, and all the tuner chips are drivers in userland speaking > over the iic device interface... > >> 4. USB MIDI device class >> http://www.usb.org/developers/devclass_docs >> >> 5. USB IrDA device class >> http://www.usb.org/developers/devclass_docs >> >> Some new USB-IrDA chips conform to this specification. >> >> 6. TI 3410/5052 USB-RS232C adapter >> http://focus.ti.com/docs/prod/folders/print/tusb3410.html >> http://focus.ti.com/docs/prod/folders/print/tusb5052.html >> >> Please have a look at those Linux device drive websites and perceive >> the disparity that FreeBSD falls behind: >> >> Modem: http://linmodems.org/ >> Video: http://linux.bytesex.org/ >> Temperature sensor: http://www.lm-sensors.org/ >> USB PC Camera: http://mxhaard.free.fr/spca5xx.html > > See above about USB... > >> Although not all data sheets have been publicized by vendors, but >> at least FreeBSDers can follow/keep up with Linux community, cannot we? > > a) some drivers that aren't that high visibility don't get the > demand/attention that they necessarily deserve... Mostly because > there is only one or two people interested... There are a couple > video capture drivers (saa and cxm) that both are apparently ready, > but haven't yet been integrated... I did send mail asking about the > cxm licensing issues (it has firmware necessary for operation), but > never got a response... As a FreeBSD user, I must make enough psychological preparations before you try FreeBSD on new hardware. If I find FreeBSD doesn't support it, I will have not a bit amazement. Your being ignored is not out of a clear sky. Maybe your E-mail had been filtered as spam. Once I telephoned VIMICRO (www.vimicro.com, in Beijing, only a few kilometers far away from my dwelling), whose IC products have been installed in cheap USB PC cameras sold all over the world (USB PID 0x0ac8). The technical support staff kicked me to sales staff. But in the end, a salesman told me an "official" agreement is required for official data sheet. Only if you telephone or send registered paper mail to those vendors will you probably get a reply/answer. As a committer, you may try to get help from FreeBSD Foundation. > > b) Many times the vendors ignore FreeBSD... DVIco has continued to > fail to provide me w/ the necessary docs, but I think this is more > because the person that is providing the docs is asleep at the wheel > as others seem to want to give them out, but it's hard when it takes > a lot more... Most of the stuff above are small little ones that > the vendors don't really care about, but the ones that are really > useful and not as easy to find alternatives are much harder... > > Get writing the drivers... It's a lot easier than people think... > > -- > John-Mark Gurney Voice: +1 415 225 5579 > > "All that I will do, has been done, All that I have, has not." > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" ------------------------------------------------------------------------ From Beijing, China From owner-freebsd-hardware@FreeBSD.ORG Fri Jul 21 07:16:16 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA9EF16A4DF for ; Fri, 21 Jul 2006 07:16:16 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail06.syd.optusnet.com.au (mail06.syd.optusnet.com.au [211.29.132.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED85F43D45 for ; Fri, 21 Jul 2006 07:16:15 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail06.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k6L7G7vL021440 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 21 Jul 2006 17:16:08 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k6L7G7xI000974; Fri, 21 Jul 2006 17:16:07 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k6L7G710000973; Fri, 21 Jul 2006 17:16:07 +1000 (EST) (envelope-from peter) Date: Fri, 21 Jul 2006 17:16:07 +1000 From: Peter Jeremy To: Intron Message-ID: <20060721071607.GA728@turion.vk2pj.dyndns.org> References: <20060720103228.GA716@turion.vk2pj.dyndns.org> <1153397244.66653@origin.intron.ac> <20060720181216.GJ96589@funkthat.com> <1153452255.82099@origin.intron.ac> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xHFwDpU9dbj6ez1V" Content-Disposition: inline In-Reply-To: <1153452255.82099@origin.intron.ac> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-hardware@freebsd.org Subject: Re: Improving FreeBSD's hardware compatibility X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jul 2006 07:16:16 -0000 --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, 2006-Jul-21 09:42:40 +0800, Intron wrote: >Oliver Fromme wrote: >>Yeah, most of which are crap. :-) The raw number of >>drivers says _nothing_ about hardware vendors' support. > >This is a problem of code quality. A driver that is effectively unusable is no better than no driver at all. The FreeBSD prefers to expend developer resources on providing a smaller number of drivers but have them actually work. >But at least Linux community has so many volunteers/vendors to write >drivers. quantity !=3D quality On Fri, 2006-Jul-21 11:18:07 +0800, Intron wrote: >3. Philips SAA 7130/7134, TV decoder > This is one of the most popular TV decoder chips on the market. >The data sheet can be obtained from the vendor, just as what Linux >community has done. You are wrong in two respects here. a) The publicly available datasheet does not provide programming details. The programming details are only available under NDA. b) FreeBSD _does_ have a driver for this chipset, available from download.purpe.com - which I am successfully using. > Although not all data sheets have been publicized by vendors, but >at least FreeBSDers can follow/keep up with Linux community, cannot we? Feel free to contribute. --=20 Peter Jeremy --xHFwDpU9dbj6ez1V Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEwH81/opHv/APuIcRAs8dAJ9xbVEZEKHVA3kVJNjItKjIF6KDmwCgwb19 lmJwDIvtoEIEbiIErxfHH9Q= =Ld5O -----END PGP SIGNATURE----- --xHFwDpU9dbj6ez1V-- From owner-freebsd-hardware@FreeBSD.ORG Fri Jul 21 15:15:44 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DE7016A4DA for ; Fri, 21 Jul 2006 15:15:44 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (megan.kiwi-computer.com [63.224.10.3]) by mx1.FreeBSD.org (Postfix) with SMTP id 7C81643D49 for ; Fri, 21 Jul 2006 15:15:41 +0000 (GMT) (envelope-from rick@kiwi-computer.com) Received: (qmail 70119 invoked by uid 2001); 21 Jul 2006 15:15:39 -0000 Date: Fri, 21 Jul 2006 10:15:39 -0500 From: "Rick C. Petty" To: Jo Rhett Message-ID: <20060721151539.GA69956@megan.kiwi-computer.com> References: <20060721000018.GA99237@svcolo.com> <20060721001607.GA64376@megan.kiwi-computer.com> <20060721004731.GC8868@svcolo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060721004731.GC8868@svcolo.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hardware@freebsd.org Subject: Re: device busy -- no locks? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd@kiwi-computer.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jul 2006 15:15:44 -0000 On Thu, Jul 20, 2006 at 05:47:31PM -0700, Jo Rhett wrote: > > Sorry, yes. Same results. And if lsof shows things that fstat doesn't, > then this is a bug in FreeBSD. Not necessarily a bug, if you consider the ports tree as "enhancements". I know they show different stuff, e.g. lsof lists shared libraries which are open and IPC stuff. I'm not sure what other differences they have. The biggest troubles I've had with fstat in the past is when I was trying to find someone who held something like /dev/dsp0.2 open and I did a search for just /dev/dsp. I wish fstat was a bit more knowledgable about related devices. > Also note that this system is pretty bone stock. Standard install, plus > mysql and apache. Nothing else would be using the port. It's something > that left it locked, and really only "login" could be the culprit. By locked do you mean someone performed flock(2) or lockf(3) on the device or that someone held the device open? I was under the impression that all open file descriptors and file locks were cleaned up when a process terminates. So I'm not sure what you mean by "left it locked" if there's no current process using that device. > > How did you disable the getty? Was this prior to or after a restart? It > > sounds like /etc/ttys is maybe running a process on it. You need to > > "killall -HUP init" after changing /etc/ttys. But you probably already > > know that. > > Yes, I change "on" to "off" in /etc/ttys and "kill -1 1" :-) I was also asking if you tried rebooting after you disabled getty. There could be a bug in the sio driver or some hardware-related glitch which doesn't fully close the device even though the process is terminated. If the problem goes away after a reboot, this is likely the problem. If not, it still sounds like a device-related problem.. Although I can't find the use of EBUSY (errno 16) in the sio source code... -- Rick C. Petty From owner-freebsd-hardware@FreeBSD.ORG Fri Jul 21 17:14:21 2006 Return-Path: X-Original-To: freebsd-hardware@FreeBSD.ORG Delivered-To: freebsd-hardware@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E4E916A4DF for ; Fri, 21 Jul 2006 17:14:21 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 168C543EED for ; Fri, 21 Jul 2006 17:13:24 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (nunefe@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k6LHD7bp043629 for ; Fri, 21 Jul 2006 19:13:13 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k6LHD78t043628; Fri, 21 Jul 2006 19:13:07 +0200 (CEST) (envelope-from olli) Date: Fri, 21 Jul 2006 19:13:07 +0200 (CEST) Message-Id: <200607211713.k6LHD78t043628@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hardware@FreeBSD.ORG In-Reply-To: <1153446852.80350@origin.intron.ac> X-Newsgroups: list.freebsd-hardware User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Fri, 21 Jul 2006 19:13:13 +0200 (CEST) Cc: Subject: Re: Improving FreeBSD's hardware compatibility X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hardware@FreeBSD.ORG List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jul 2006 17:14:21 -0000 Intron wrote: > Oliver Fromme wrote: > > Intron wrote: > > > Peter Jeremy wrote: > > > > Getting action from vendors has been unsuccessful in the past - the > > > > Free OS community (Linux + *BSD) is too small for vendors to be > > > > concerned about. > > > > > > I cannot agree with you. Linux has achieved much more support from > > > hardware vendors than FreeBSD. > > > > Interestingly, when I looked for a new laptop last year, > > it turned out that the number of laptops that ran FreeBSD > > was greater than those that ran Linux. (I finally chose > > a Samsung X20-XVM 1600-V, which works perfectly fine for > > me except for the built-in winmodem [which I don't need > > anyway]. A Linux live CD didn't even boot on it.) > > Have a look at http://linmodems.org/ before your assertion. How useful is a Linux driver for the modem if Linux does not even _boot_ on your machine? And as I wrote, I don't even need the modem, because I've got Ethernet and WLAN. > How many modems listed on that website are support by FreeBSD? I have no idea (there are a few ports [e.g. ltmdm] which support a few). It's pretty much irrelevant. > > > You may look in Linux source code. > > > In linux-2.6.x/drivers/, there are so many hardware drivers. > > > > Yeah, most of which are crap. :-) The raw number of > > drivers says _nothing_ about hardware vendors' support. > > This is a problem of code quality. > But at least Linux community has so many volunteers/vendors to write > drivers. Yes, which is the cause of the code quality problem. Intron wrote: > I would write USB stack in C++ The existing USB stack is already quite heavy-weight and inefficient. There's no reason to make it even worse. > But on freebsd-hackers@, this idea encountered strong objection. If you look at the archives, you'll notice that you're not the first one suggesting to write (parts of) the kernel in C++. The reaction was always the same. > Do you believe that current Intel Pentium 4 or AMD Athlon XP can process > analog TV in full frame size and full frame rate (no larger than 767x575, > 25 FPS, either of NTSC/PAL/SECAM) freely? My 7-years old Pentium-II can do that. > Do you really believe that current Intel Pentium 4 or AMD Athlon XP > can process much higher bitstream HDTV? Yes, that's certainly possible. Maybe not if you write it in C++, though. :-) *duck* Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "I have stopped reading Stephen King novels. Now I just read C code instead." -- Richard A. O'Keefe From owner-freebsd-hardware@FreeBSD.ORG Sat Jul 22 01:02:13 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78B1616A4DA for ; Sat, 22 Jul 2006 01:02:13 +0000 (UTC) (envelope-from mag@intron.ac) Received: from mail.oreilly.com.cn (oreilly.com.cn [211.154.219.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FA2443D49 for ; Sat, 22 Jul 2006 01:02:08 +0000 (GMT) (envelope-from mag@intron.ac) Received: from origin.intron.ac ([210.51.165.237]) (AUTH: LOGIN intron) by mail.oreilly.com.cn with esmtp; Sat, 22 Jul 2006 09:02:06 +0800 id 000C9459.44C1790E.00013036 References: <200607211713.k6LHD78t043628@lurza.secnetix.de> In-Reply-To: <200607211713.k6LHD78t043628@lurza.secnetix.de> From: "Intron" To: Oliver Fromme Date: Sat, 22 Jul 2006 08:58:39 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312"; format=flowed Content-Transfer-Encoding: 7bit Message-Id: <1153530126.1977@origin.intron.ac> Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Improving FreeBSD's hardware compatibility X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jul 2006 01:02:13 -0000 Oliver Fromme wrote: > Intron wrote: > > Oliver Fromme wrote: > > > Intron wrote: > > > > Peter Jeremy wrote: > > > > > Getting action from vendors has been unsuccessful in the past - the > > > > > Free OS community (Linux + *BSD) is too small for vendors to be > > > > > concerned about. > > > > > > > > I cannot agree with you. Linux has achieved much more support from > > > > hardware vendors than FreeBSD. > > > > > > Interestingly, when I looked for a new laptop last year, > > > it turned out that the number of laptops that ran FreeBSD > > > was greater than those that ran Linux. (I finally chose > > > a Samsung X20-XVM 1600-V, which works perfectly fine for > > > me except for the built-in winmodem [which I don't need > > > anyway]. A Linux live CD didn't even boot on it.) > > > > Have a look at http://linmodems.org/ before your assertion. > > How useful is a Linux driver for the modem if Linux does > not even _boot_ on your machine? And as I wrote, I don't > even need the modem, because I've got Ethernet and WLAN. > > > How many modems listed on that website are support by FreeBSD? > > I have no idea (there are a few ports [e.g. ltmdm] which > support a few). It's pretty much irrelevant. > > > > > You may look in Linux source code. > > > > In linux-2.6.x/drivers/, there are so many hardware drivers. > > > > > > Yeah, most of which are crap. :-) The raw number of > > > drivers says _nothing_ about hardware vendors' support. > > > > This is a problem of code quality. > > But at least Linux community has so many volunteers/vendors to write > > drivers. > > Yes, which is the cause of the code quality problem. > > Intron wrote: > > I would write USB stack in C++ > > The existing USB stack is already quite heavy-weight and > inefficient. There's no reason to make it even worse. > > > But on freebsd-hackers@, this idea encountered strong objection. > > If you look at the archives, you'll notice that you're not > the first one suggesting to write (parts of) the kernel in > C++. The reaction was always the same. > > > Do you believe that current Intel Pentium 4 or AMD Athlon XP can process > > analog TV in full frame size and full frame rate (no larger than 767x575, > > 25 FPS, either of NTSC/PAL/SECAM) freely? > > My 7-years old Pentium-II can do that. Really? Y: 767x575 = 441025 (bytes) U: 767x575/4 = 110256 (bytes) V: 767x575/4 = 110256 (bytes) One frame: 661537 bytes One second: 661537*25 = 16538425 (bytes), 132 Mbps Please note that all popular video compressing algorithms (MPEG 1/2/4, Ogg Theora, RealVideo and Microsoft Windows Media Video) are not so simple as copying. My Intel Celeron 1.7GHz cannot compress in full size and full frame rate of PAL-D video into MPEG-2 format instantly. > > > Do you really believe that current Intel Pentium 4 or AMD Athlon XP > > can process much higher bitstream HDTV? > > Yes, that's certainly possible. Maybe not if you write it > in C++, though. :-) *duck* > > Best regards > Oliver > > -- > Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing > Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd > Any opinions expressed in this message may be personal to the author > and may not necessarily reflect the opinions of secnetix in any way. > > "I have stopped reading Stephen King novels. > Now I just read C code instead." > -- Richard A. O'Keefe > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" ------------------------------------------------------------------------ From Beijing, China