From owner-freebsd-hardware@FreeBSD.ORG Sun Dec 21 14:47:43 2003 Return-Path: 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 AF75A16A4CE for ; Sun, 21 Dec 2003 14:47:43 -0800 (PST) Received: from web14801.mail.yahoo.com (web14801.mail.yahoo.com [216.136.224.217]) by mx1.FreeBSD.org (Postfix) with SMTP id AC23743D55 for ; Sun, 21 Dec 2003 14:47:41 -0800 (PST) (envelope-from rosti_bsd@yahoo.com) Message-ID: <20031221224741.3821.qmail@web14801.mail.yahoo.com> Received: from [192.114.47.54] by web14801.mail.yahoo.com via HTTP; Sun, 21 Dec 2003 14:47:41 PST Date: Sun, 21 Dec 2003 14:47:41 -0800 (PST) From: Rostislav Krasny To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Fwd: ED(1) driver of FreeBSD 5.2-RC1 cannot work with ISA PnP NE2000 compatible NIC X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Dec 2003 22:47:43 -0000 Hello. I have a problem with ISA PnP network card and I asked a question about that in freebsd-current mailing list at Dec 19 17:33:14 PST 2003 but I didn't get any response from somebody. Maybe the freebsd-current mailing is a wrong place for such questions, so I'm forwarding my original email to freebsd-hardware mailing list. Please help me to resolve this problem. I have an ISA PnP NE-12 (NE2000 compatible) NIC based on UMC UM9008F chip. This is an output of 'pnpinfo' in this system: =======start of pnpinfo output======== Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID UMC9008 (0x0890a355), Serial Number 0x630f0000 PnP Version 1.0, Vendor Version 16 Device Description: ISA PLUG & PLAY Ethernet Card Logical Device ID: UMC9008 0x0890a355 #0 Device supports I/O Range Check Vendor register funcs 00 Compatible Device ID: PNP80d6 (d680d041) I/O Range 0x200 .. 0x3e0, alignment 0x20, len 0x20 [not 16-bit addr] IRQ: 2 3 4 5 10 11 12 15 IRQ: High true edge sensitive End Tag Successfully got 6 resources, 1 logical fdevs -- card select # 0x0001 CSN UMC9008 (0x0890a355), Serial Number 0x630f0000 Logical device #0 IO: 0x0200 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 2 0 DMA 4 4 IO range check 0x00 activate 0x01 =======end of pnpinfo output======== This card works well with FreeBSD 4.X but refuse to work with FreeBSD 5.X. Now I'm trying to make it work with FreeBSD 5.2-RC1. Following is a part of dmesg, right after I installed 5.2-RC1: ed1: at port 0x200-0x21f irq 2 on isa0 device_probe_and_attach: ed1 attach returned 22 When I saw it I thought that the problem is in PnP initialization because IRQ 2 looks wrong. I didn't programmed FreeBSD kernel and its device drivers in a past, so I made simple but ugly patch to the 'ed' driver: --- if_ed.c.orig Wed Dec 17 12:44:49 2003 +++ if_ed.c Fri Dec 19 16:34:32 2003 @@ -1655,7 +1655,7 @@ struct resource *res; res = bus_alloc_resource(dev, SYS_RES_IRQ, &rid, - 0ul, ~0ul, 1, (RF_ACTIVE | flags)); + 3ul, ~0ul, 1, (RF_ACTIVE | flags)); if (res) { sc->irq_rid = rid; sc->irq_res = res; After I recompiled the kernel I got following text in dmesg: ed1: at port 0x200-0x21f irq 5 on isa0 ed1: bpf attached ed1: address 00:00:21:82:25:03, type NE2000 (16 bit) And finally when I ran 'ifconfig -a' I saw this: ed1: flags=8843 mtu 1500 inet6 fe80::200:21ff:fe82:2503%ed1 prefixlen 64 scopeid 0x4 ether 00:00:21:82:25:03 Ok but ed1 still doesn't work! It can send packets but cannot receive any packet. This is how I found it. On the 5.2-RC1 box I ran ping with IP address of second host of my home LAN and in the second pseudo-terminal I ran tcpdump. On the destination host I ran ethereal. The tcpdump detected several outgoing packets with ARP requests but no incoming packet. The ethereal detected all these packets as incoming and also several outgoing packets with ARP responses. There was no problem to ping the same second host when I used 3Com NIC and the same Ethernet cable with this computer. Also there are many error messages in /var/log/messages when ed1 is UP: Dec 19 17:01:37 vega kernel: ed1: device timeout Dec 19 17:01:42 vega last message repeated 2 times Dec 19 17:03:05 vega last message repeated 5 times Do you have any idea why FreeBSD 5.x still can't work with ISA PnP NE2000 compatible NICs like the one I have? Thanks P.S. since I'm not subscribed to any freebsd mailing list could you please Cc you replies to me too? __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ From owner-freebsd-hardware@FreeBSD.ORG Sun Dec 21 14:50:06 2003 Return-Path: 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 866B616A4CE for ; Sun, 21 Dec 2003 14:50:06 -0800 (PST) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id B60A343D48 for ; Sun, 21 Dec 2003 14:50:05 -0800 (PST) (envelope-from RonDzierwa@comcast.net) Received: from comcast.net (esx132dhcp973.essex01.md.comcast.net[68.33.135.205]) by comcast.net (rwcrmhc13) with SMTP id <2003122122500501500k3vcde> (Authid: rondzierwa); Sun, 21 Dec 2003 22:50:05 +0000 Message-ID: <3FE623E8.448AD89E@comcast.net> Date: Sun, 21 Dec 2003 17:51:20 -0500 From: Ron Dzierwa Organization: Innovative Engineering, Inc. X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: athlon with 4.9 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Dec 2003 22:50:06 -0000 I'm looking for an Athlon motherboard that works with 4.9 and will support xp2600 or better and fast ddr (2700 or better) and usb 2.0. I have tried two Biostar boards M7NCG, M7NCD (both have nVidia nforce chipsets), and both have problems. The G boots till it gets to the disks and hangs. On the D, the kernel presents the copyright notice and dies. I tried the asus a7v333 and, although it seems to boot, it doesnt run with my raid (adaptec 2400). Does anybody have a rig that they are using that runs with no problems so that i can stop fooling around with trying this and that? thanks, ron. From owner-freebsd-hardware@FreeBSD.ORG Sun Dec 21 15:47:05 2003 Return-Path: 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 3145E16A4CE for ; Sun, 21 Dec 2003 15:47:05 -0800 (PST) Received: from ns.spirit.ee (ns.spirit.ee [82.131.120.70]) by mx1.FreeBSD.org (Postfix) with SMTP id 0D96F43D48 for ; Sun, 21 Dec 2003 15:47:03 -0800 (PST) (envelope-from joel@almic.ee) Received: (qmail 41217 invoked from network); 21 Dec 2003 23:49:54 -0000 Received: from unknown (HELO CHARON) (192.168.0.25) by 192.168.0.254 with SMTP; 21 Dec 2003 23:49:54 -0000 From: "Joel V." To: Date: Mon, 22 Dec 2003 01:46:26 +0200 Message-ID: <000b01c3c81c$ac600800$1900a8c0@CHARON> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Subject: FreeBSD 4.8 on WD1200JB - dissapointing access times X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Dec 2003 23:47:05 -0000 Hello! Now here's the case. I have this machine running FreeBSD 4.8: P4 2.4Ghz 512MB DDR333 Intel D845PESV motherboard Intel Pro/100 S nic WD 120GB hdd (8mb cache) 3COM officeconnect 100Mbit switch (About 7-8 people using the fileserver) The problem is that I'm experiencing rather dissapointing access times = when connecting with a winxp/win2k client to the FreeBSD box running samba. Sometimes it can take up to 5-6 seconds to display the content of a directory. However, during the day, when people are using it all the = time, such lag seems to occur not very often. Why I'm a bit suspicous is this = - I have another fileserver running in another firm, which serves more = people (about 10-15), yet has no such lag: Athlon XP 1900+ 512MB DDR266 Abit KR-133A motherboard (I think...) SMC nic with RTL chip (serious suckage) IBM 120GXP-series hdd, 80GB /w 2mb cache some el cheapo switch (trendnet? trendmicro? trendtrend? or something) Running FreeBSD 5.1 The average read access of the IBM drive is 8.5ms and of the WD drive = 8.9ms. (As far as I know, the average latency for both is about 4ms.) Can this = 0.4m really make that much of a difference? The 4.8 machine seems to be in a better position no matter how you look at it (cmon, RTL chip?!), but = still it does not experience this annoying lag. When I'm behind the the server physically, all is OK with both machines, no lag whatsoever behind the console. SSH connections are also OK. If you can help me with this one, please send mail directly to me, I'm = not in the list (however I try to read it as frequently as I can). Joel V. (joel@spirit.ee) From owner-freebsd-hardware@FreeBSD.ORG Sun Dec 21 20:19:51 2003 Return-Path: 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 E3CDB16A4CE for ; Sun, 21 Dec 2003 20:19:51 -0800 (PST) Received: from ns.dangbit.com (h-66-166-139-170.MCLNVA23.covad.net [66.166.139.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id B980843D1D for ; Sun, 21 Dec 2003 20:19:49 -0800 (PST) (envelope-from mhovan+freebsd@hovan.org) Received: from [192.168.1.10] (pcp03918452pcs.arlngt01.va.comcast.net [68.86.211.32]) (authenticated bits=0) by ns.dangbit.com (8.12.8/8.12.8) with ESMTP id hBM4JlCh041898 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Sun, 21 Dec 2003 23:19:48 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v609) Content-Transfer-Encoding: 7bit Message-Id: <99DB77EE-3436-11D8-941D-0030657E8346@hovan.org> Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-hardware@freebsd.org From: "Michael A. Hovan III" Date: Sun, 21 Dec 2003 23:23:32 -0500 X-Mailer: Apple Mail (2.609) Subject: ichsmb driver not loading on Intel SE7501CW2 motherboard X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Dec 2003 04:19:52 -0000 Hello, A colleague and I are currently having difficulty building a FreeBSD 4.9 kernel that loads the ichsmb driver on an Intel SE7501CW2 motherboard. There appears to be some sort of problem mapping an interrupt to the device, as illustrated by the following boot message: ichsmb0: port 0x1100-0x111f irq 0 at device 31.3 on pci0 pci_cfgintr_virgin: using routable interrupt 3 pci_cfgintr: ROUTE_INTERRUPT failed. smbus0: on ichsmb0 smb0: on smbus0 At some point near the end of the boot the console hangs, and the machine is in an unstable condition. When we do not load the ichsmb driver, the boot works fine, but the SMBus (obviously) does not work. As an experiment we built a 5.1 kernel which included the driver and it loaded fine, due to the addition of an ACPI/PCI bus driver in 5.x. We were then able to run utilities which interrogated devices on the system management bus. We are a little hesitant to put 5.x into service in a production environment at this time. So, we would really like to get this working on the 4.x series. The particular goal is to get the fan monitoring info from the Maxim MAX6651 chip that is on this motherboard, which appears to only support an SMBus interface. We have tried this with and without ACPI, with and without APM, and with and without an SMP kernel, and there is no difference. Further info that might be enlightening: When the boot hangs, we are able to ssh into the machine remotely, although the console remains frozen. When we try to run the monitoring utility we wrote, *it actually works* -- we get the correct fan information back from the max6651 chip, through the smbus interface. Even though the interrupt was unassigned, the smbus still worked. However, I did notice that any call to usleep() from a userland program will hang infinitely. Our guess is that this is the reason the boot hangs; one of the startup utilities calls usleep(). Still further info that might be enlightening to kernel folk: This is out of our depth, but on a lark, we found the line of code that printed the "ROUTE_INTERRUPT failed" message, which is in the pci_cfgintr() function in /usr/src/sys/i386/isa/pci_cfgreg.c . It returns 255 to indicate that the interrupt routing failed. If we comment out the "return(255);" line and rebuild the kernel, which causes the value 3 (the interrupt it was trying to route) to get returned, the boot will no longer hang -- but the SMBus now no longer works. Any suggestions on how to make this work, other things we could try, or other debugging information we should look at would be appreciated. Thanks, Mike & Carl From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 22 08:35:38 2003 Return-Path: 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 58FB216A4CE for ; Mon, 22 Dec 2003 08:35:38 -0800 (PST) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24D7543D1D for ; Mon, 22 Dec 2003 08:35:37 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 10675 invoked from network); 22 Dec 2003 16:35:36 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 22 Dec 2003 16:35:36 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.10/8.12.10) with ESMTP id hBMGZXM0045979; Mon, 22 Dec 2003 11:35:33 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <99DB77EE-3436-11D8-941D-0030657E8346@hovan.org> Date: Mon, 22 Dec 2003 11:35:34 -0500 (EST) From: John Baldwin To: "Michael A. Hovan III" X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: freebsd-hardware@freebsd.org Subject: RE: ichsmb driver not loading on Intel SE7501CW2 motherboard X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Dec 2003 16:35:38 -0000 On 22-Dec-2003 Michael A. Hovan III wrote: > Hello, > > A colleague and I are currently having difficulty building a FreeBSD > 4.9 kernel that loads the ichsmb driver on an Intel SE7501CW2 > motherboard. There appears to be some sort of problem mapping an > interrupt to the device, as illustrated by the following boot message: > > ichsmb0: port 0x1100-0x111f irq > 0 > at device 31.3 on pci0 > pci_cfgintr_virgin: using routable interrupt 3 > pci_cfgintr: ROUTE_INTERRUPT failed. > smbus0: on ichsmb0 > smb0: on smbus0 Well, the problem is that to get PCI interrupt routing to properly work on 4.x (which is what you need), you will need to do a lot of work. Esp. if you are trying to do this for an SMP kernel. Basically, only 5.x is going to properly do PCI interrupt routing. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 23 04:45:54 2003 Return-Path: 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 A5E5016A4CE; Tue, 23 Dec 2003 04:45:54 -0800 (PST) Received: from nsuncom.rz.hu-berlin.de (nsuncom.rz.hu-berlin.de [141.20.1.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id C51FB43D2F; Tue, 23 Dec 2003 04:45:52 -0800 (PST) (envelope-from h0444lp6@student.hu-berlin.de) Received: from localhost (localhost [127.0.0.1])hBNCjq0n027958; Tue, 23 Dec 2003 13:45:52 +0100 (MET) Received: from nsuncom.rz.hu-berlin.de ([127.0.0.1]) by localhost (nsuncom [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27764-01-4; Tue, 23 Dec 2003 13:45:51 +0100 (MET) Received: from kojo (x82.rewi.hu-berlin.de [141.20.121.82]) hBNChJcD026948; Tue, 23 Dec 2003 13:43:23 +0100 (MET) From: "h0444lp6" To: , , Date: Tue, 23 Dec 2003 20:43:54 +0800 Message-ID: <008301c3c952$7e5e5b00$5279148d@kojo> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-Virus-Scanned: by amavisd-new at hu-berlin.de Subject: WLAN card experiences wanted X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Dec 2003 12:45:54 -0000 Hi Does anyone have any experiences with one of the following cards? D-Link DWL-G520 (54MBit, PCI) Netgear WG311 (54MBit, PCI) Netgear MA111 (11MBit, USB) And which of these two is better Netgear MA311 D-Link DWL-520 Thanks From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 23 08:06:47 2003 Return-Path: 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 103A216A4CE; Tue, 23 Dec 2003 08:06:47 -0800 (PST) Received: from otter3.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B737243D2F; Tue, 23 Dec 2003 08:06:45 -0800 (PST) (envelope-from anderson@centtech.com) Received: from centtech.com (neutrino.centtech.com [10.177.171.220]) by otter3.centtech.com (8.12.3/8.12.3) with ESMTP id hBNG6j6T021029; Tue, 23 Dec 2003 10:06:45 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <3FE8680D.1020405@centtech.com> Date: Tue, 23 Dec 2003 10:06:37 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: h0444lp6 References: <008301c3c952$7e5e5b00$5279148d@kojo> In-Reply-To: <008301c3c952$7e5e5b00$5279148d@kojo> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: WLAN card experiences wanted X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Dec 2003 16:06:47 -0000 h0444lp6 wrote: >Hi > >Does anyone have any experiences with one of the following cards? > >D-Link DWL-G520 (54MBit, PCI) >Netgear WG311 (54MBit, PCI) >Netgear MA111 (11MBit, USB) > I've used cards with the same chipsets as those above, but not directly any of those cards. They work great (thanks Sam Leffler and everyone else!). I would not expect the full 54MBit however, but that's with any wireless networking. >And which of these two is better > >Netgear MA311 >D-Link DWL-520 > > Better for what? Eric -- ------------------------------------------------------------------ Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. ------------------------------------------------------------------ From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 25 04:20:45 2003 Return-Path: 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 4404716A4CE for ; Thu, 25 Dec 2003 04:20:45 -0800 (PST) Received: from hotmail.com (bay3-f22.bay3.hotmail.com [65.54.169.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DDE343D1F for ; Thu, 25 Dec 2003 04:20:44 -0800 (PST) (envelope-from abarbosazjose@msn.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 25 Dec 2003 04:20:44 -0800 Received: from 80.236.56.66 by by3fd.bay3.hotmail.msn.com with HTTP; Thu, 25 Dec 2003 12:20:44 GMT X-Originating-IP: [80.236.56.66] X-Originating-Email: [abarbosazjose@msn.com] X-Sender: abarbosazjose@msn.com From: "jose carlos barbosa" To: sam@errno.com, freebsd-hardware@freebsd.org Date: Thu, 25 Dec 2003 13:20:44 +0100 Message-ID: X-OriginalArrivalTime: 25 Dec 2003 12:20:44.0271 (UTC) FILETIME=[84E74FF0:01C3CAE1] MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Dec 2003 12:20:45 -0000 salu _________________________________________________________________ Dialoguez en direct et gratuitement avec vos amis sur [1]MSN Messenger ! References 1. http://g.msn.com/8HMAFRFR/2737??PS= From owner-freebsd-hardware@FreeBSD.ORG Sat Dec 27 17:11:15 2003 Return-Path: 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 9270A16A4CE for ; Sat, 27 Dec 2003 17:11:15 -0800 (PST) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NOSPAM.dyndns.dk (ip-212.223.103.150.admin4network.de [212.223.103.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id CECAF43D31 for ; Sat, 27 Dec 2003 17:11:09 -0800 (PST) (envelope-from bounce@NOSPAM.dyndns.dk) Received: from NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk (NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk [2002:d4df:6796:0:200:c0ff:fefc:19aa]) (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id hBS1ANg13223 verified NO) for ; Sun, 28 Dec 2003 02:10:31 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Received: (from beer@localhost)hBS1AGe08445; Sun, 28 Dec 2003 02:10:16 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Date: Sun, 28 Dec 2003 02:10:16 +0100 (CET) Message-Id: <200312280110.hBS1AGe08445@NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk> X-Authentication-Warning: NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk: beer set sender to bounce@NOSPAM.dyndns.dk using -f From: Barry Bouwsma References: <200311050441.hA54fhJ54978@NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk> <200311210043.hAL0hDu01322@NOSPAM.spam.NOSPAM.spam.NOSPAM.dyndns.dk> <20031121194845.GA87408@pit.databus.com> <20031202165949.GP81181@cicely12.cicely.de> To: FreeBSD Hardware Wizards MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit Subject: Re: USB camera compatibility question X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Dec 2003 01:11:15 -0000 [IPv6-only address etc etc; drop for replies, I read the archives periodically] Weeks ago, Bernd Walter wrote... > On Fri, Nov 21, 2003 at 02:48:46PM -0500, Barney Wolff wrote: > > On Fri, Nov 21, 2003 at 01:43:13AM +0100, Barry Bouwsma wrote: > > Yes, because so far the images snarfed with my hacks are okay for the > > first 4096 bytes, thereafter failing to match the perfect images I can > > > The "junk at byte 4097" symptom matches what I get with a Sony F707 > > on -current using the OHCI usb controller. I believe it's a bug in > > the ohci driver but don't know more than that. > You want ohci.c rev 1.139 I'll keep that in mind -- at present, I've had successful OHCI operation with a usb KLM with ohci.c rev 1.39.2.9, uhci.c rev 1.40.2.11, and umass.c either 1.11.2.21 or based on that patched from current -- my source is a mess, ugh. However, with the above kernel modules that worked fine with an OHCI card, when I connect the camera to a UHCI card, I confirm my earlier observation that data transfer rates from the camera are only ~60kB/sec -- more than 5 times slower than with the OHCI card. Enough for me to go and drink a Maß of coffee while I copy a good-sized detailed porn^H^H^Hicture, which previously was not necessary. The other kernel module(s) I have tried, perhaps when I experienced the corruption following byte 4096, have ohci.c rev 1.132, and uhci.c rev 1.145, but I can't remember what transfer rates I was seeing with that and UHCI. I'm quite sure I see no such limit to a conventional UHCI-connected disk -- in fact, at the moment I'm getting ten times the max rate the camera gave me (0,55 - 0,87MB/sec) with normal writes, not pushing any limits. Apart from the card in use, the setup of the camera (to hub to card) is identical between the UHCI 60kB/sec and OHCI 300-500kB/sec reads from the MSDOS filesystem. Just wondering if this difference in speed is a known issue (or was previously an issue). One of these days I'll get around to updating the kernel modules and seeing if the speed difference still is observed. One of these days... thanks Barry Bouwsma From owner-freebsd-hardware@FreeBSD.ORG Sat Dec 27 20:19:53 2003 Return-Path: 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 E7C2216A4CF for ; Sat, 27 Dec 2003 20:19:53 -0800 (PST) Received: from smtp.ya.com (smtp04.ya.com [62.151.11.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43CA843D31 for ; Sat, 27 Dec 2003 20:19:51 -0800 (PST) (envelope-from xxavi@ya.com) Received: from mta by smtp.ya.com with spam-scanned id 1AaSP6-0004wi-00 for freebsd-hardware@freebsd.org; Sun, 28 Dec 2003 05:19:49 +0100 Received: from [80.37.219.152] (helo=ya.com) by smtp.ya.com with smtp id 1AaSP6-0004wc-00 for freebsd-hardware@freebsd.org; Sun, 28 Dec 2003 05:19:48 +0100 From: xxavi To: freebsd-hardware@freebsd.org X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: Date: Sun, 28 Dec 2003 05:19:48 +0100 Subject: Problems with GeForce4 MX 440 AGP 8x, FreeBSD and GLX extension X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Dec 2003 04:19:54 -0000 Hi people! Info. of my system: I have a GeForce4 MX 440 AGP 8x video card. My OS is FreeBSD 4.9-STABLE #20: Wed Dec 10 13:39:46 CET 2003 My XFree86 is, This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to XFree86@XFree86.Org and patches submitted to fixes@XFree86.Org. Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs). XFree86 Version 4.3.99.12 Release Date: 10 September 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: FreeBSD 4.9 i386 [ELF] Current Operating System: FreeBSD localhost 4.9-STABLE FreeBSD 4.9-STABLE #20: Wed Dec i386 Build Date: 30 October 2003 Changelog Date: 10 September 2003 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present My motherboard is a Aopen AX6BC with R2.59 BIOS version. The problem: When I enable 'nvidia' driver into XF86Config and nvidia.ko module and after, I try any aplication's GLX extension, my system reboot automatically! Why it occur? How can I solvent this problem? Thanks. _____ xxavi "Be liberal in what you accept, and conservative in what you send" from RFC [Braden 1989a] From owner-freebsd-hardware@FreeBSD.ORG Sat Dec 27 21:17:34 2003 Return-Path: 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 7253D16A4CE for ; Sat, 27 Dec 2003 21:17:34 -0800 (PST) Received: from vp4.netgate.net (vp4.netgate.net [205.214.170.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3DA643D62 for ; Sat, 27 Dec 2003 21:16:37 -0800 (PST) (envelope-from admin@forkthepenguin.com) Received: from localhost (ibrew@localhost) by vp4.netgate.net (8.11.6/8.11.7) with ESMTP id hBS5Gb400654 for ; Sat, 27 Dec 2003 21:16:37 -0800 (PST) Date: Sat, 27 Dec 2003 21:16:37 -0800 (PST) From: admin@forkthepenguin.com X-X-Sender: ibrew@vp4.netgate.net To: freebsd-hardware@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Kernel Optimizations for Processors X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Dec 2003 05:17:34 -0000 Is there a method for determining what options can be incorporated for a specific processor? The unit in question is a VIA C3 Samuel2 processor running at 800 Mhz. I've found many clues that this uses Cyrix instructions although the chipset uses the Centaur core. This is supposed to be an i686, but I've seen some issues on a Linux system with the same processor that required the kernel to be built with i586. I see several options in LINT (below) that look like they might be applicable, my goal is to optimize this system as much as possible. I understand I can remove the following (in theory) from the kernel configuration for a gain in performance : cpu I386_CPU cpu I486_CPU cpu I586_CPU Below are some options selected from the LINT file. Can anyone provide any clues as to which of these are applicable to my processor, and how I might have been able to determine this myself? Or a more appropriate list to have posted this to? dmesg snippet provided below. Chris # CPU_BTB_EN enables branch target buffer on Cyrix 5x86 (NOTE 1). # # CPU_DIRECT_MAPPED_CACHE sets L1 cache of Cyrix 486DLC CPU in direct # mapped mode. Default is 2-way set associative mode. # # CPU_CYRIX_NO_LOCK enables weak locking for the entire address space # of Cyrix 6x86 and 6x86MX CPUs by setting the NO_LOCK bit of CCR1. # Otherwise, the NO_LOCK bit of CCR1 is cleared. (NOTE 3) # # CPU_DISABLE_5X86_LSSER disables load store serialize (i.e. enables # reorder). This option should not be used if you use memory mapped # I/O device(s). # # CPU_ENABLE_SSE enables SSE/MMX2 instructions support. # # CPU_IORT defines I/O clock delay time (NOTE 1). Default values of # I/O clock delay time on Cyrix 5x86 and 6x86 are 0 and 7,respectively # (no clock delay). # # CPU_RSTK_EN enables return stack on Cyrix 5x86 (NOTE 1). # # CPU_WT_ALLOC enables write allocation on Cyrix 6x86/6x86MX and AMD # K5/K6/K6-2 cpus. # # CYRIX_CACHE_WORKS enables CPU cache on Cyrix 486 CPUs with cache # flush at hold state. # # CYRIX_CACHE_REALLY_WORKS enables (1) CPU cache on Cyrix 486 CPUs # without cache flush at hold state, and (2) write-back CPU cache on # Cyrix 6x86 whose revision < 2.7 (NOTE 2). # # NO_F00F_HACK disables the hack that prevents Pentiums (and ONLY # Pentiums) from locking up when a LOCK CMPXCHG8B instruction is # executed. This option is only needed if I586_CPU is also defined, # and should be included for any non-Pentium CPU that defines it. Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.9-RELEASE #0: Mon Oct 27 17:51:09 GMT 2003 root@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: VIA C3 Samuel 2 (801.82-MHz 686-class CPU) Origin = "CentaurHauls" Id = 0x673 Stepping = 3 Features=0x803035