From owner-freebsd-hardware@FreeBSD.ORG Sun Oct 12 07:06:35 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 ABFF216A4B3 for ; Sun, 12 Oct 2003 07:06:35 -0700 (PDT) Received: from maelstrom.waterspout.com (rrcs-ma-24-56-74-54.biz.rr.com [24.56.74.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7139343F93 for ; Sun, 12 Oct 2003 07:06:34 -0700 (PDT) (envelope-from csg@waterspout.com) Received: from maelstrom.waterspout.com (localhost [127.0.0.1]) h9CE6SPH085329; Sun, 12 Oct 2003 09:06:28 -0500 (CDT) (envelope-from csg@waterspout.com) Received: (from csg@localhost)h9CE6Rnj085328; Sun, 12 Oct 2003 09:06:27 -0500 (CDT) X-Authentication-Warning: maelstrom.waterspout.com: csg set sender to csg@waterspout.com using -f Date: Sun, 12 Oct 2003 09:06:27 -0500 From: "C. Stephen Gunn" To: Jamie Bowden Message-ID: <20031012140627.GA85255@waterspout.com> References: <20031011085624.C20891-100000@moo.sysabend.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031011085624.C20891-100000@moo.sysabend.org> User-Agent: Mutt/1.4.1i cc: hardware@FreeBSD.org Subject: Re: PCI-X Multiport Serial cards. 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, 12 Oct 2003 14:06:35 -0000 Jamie Bowden (ragnar@sysabend.org) likely uttered: > Does anyone have any experience with PCI-X multiport serial cards under > FreeBSD (4 or 5, either is fine)? I've got a 1u Dell machine that in 3 > weeks will lose it's current role in life, and I'd like to use it as a > console server for a bunch of headless SGI and Sun boxes. Its only > expansion slot is PCI-X. If anyone can recommend a known working card > with at least 8 ports, I'd appreciate it. Jamie -- First I think that PCI-X is just 133Mhz by 64-bit PCI. You should be bacward compatible. Regular PCI is perfect for nearly anything you might want to do. And this machine clearly has the muscle to be one heck of a nice conserver. You might check out the PCI boards from Cyclades. I've used both the Cyclom-Y and Cyclom-Z board successfully under FreeBSD. I did have some trouble with Cyclom-Y under 4.X and reverted to 2.2.8 to run it (It was 3 years ago so I can't be sure). You might also look into the 1-U rackmount products from Lantronix or Cyclades. A private Ethernet segment is nearly as good as a custom interconnect to the server. KS Braunsdorf's variant of conserver we run at work knows how to talk directly to a tcp/ip destination, you just spell the serial device differently in conserver.cf. I'm not sure about the ports, or comserver.com variants of conserver, but it wouldn't surprise me if they supported it too. The machine you have could easily handle 2-3 Muxes, so you have plenty of room to grow. Plus you can easily drop a second machine on the black network and not be dead if the conserver has a hardware issue, either. :) - Steve From owner-freebsd-hardware@FreeBSD.ORG Sun Oct 12 16:30: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 15FCB16A4B3 for ; Sun, 12 Oct 2003 16:30:45 -0700 (PDT) Received: from gaff.hhhr.ision.net (gaff.hhhr.ision.net [195.180.9.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id C50BD43FAF for ; Sun, 12 Oct 2003 16:30:43 -0700 (PDT) (envelope-from ohoyer@gaff.hhhr.ision.net) Received: from gaff.hhhr.ision.net (localhost [127.0.0.1]) by gaff.hhhr.ision.net (8.12.9/8.12.9) with ESMTP id h9CNUfJM026508 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Oct 2003 01:30:41 +0200 (CEST) (envelope-from ohoyer@gaff.hhhr.ision.net) Received: from localhost (ohoyer@localhost)h9CNUdPv026505; Mon, 13 Oct 2003 01:30:40 +0200 (CEST) Date: Mon, 13 Oct 2003 01:30:39 +0200 (CEST) From: Olaf Hoyer To: "C. Stephen Gunn" In-Reply-To: <20031012140627.GA85255@waterspout.com> Message-ID: <20031013012851.M26306@gaff.hhhr.ision.net> References: <20031011085624.C20891-100000@moo.sysabend.org> <20031012140627.GA85255@waterspout.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: hardware@freebsd.org Subject: Re: PCI-X Multiport Serial cards. 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, 12 Oct 2003 23:30:45 -0000 On Sun, 12 Oct 2003, C. Stephen Gunn wrote: > Jamie Bowden (ragnar@sysabend.org) likely uttered: > > > Does anyone have any experience with PCI-X multiport serial cards under > > FreeBSD (4 or 5, either is fine)? I've got a 1u Dell machine that in 3 > > weeks will lose it's current role in life, and I'd like to use it as a > > console server for a bunch of headless SGI and Sun boxes. Its only > > expansion slot is PCI-X. If anyone can recommend a known working card > > with at least 8 ports, I'd appreciate it. > > You might also look into the 1-U rackmount products from Lantronix > or Cyclades. A private Ethernet segment is nearly as good as > a custom interconnect to the server. > Hi! have a couple of Cyclades 1U TS1000 (16ports) and TS3000 (48port) sitting here as embedded solution running linux-ppc, and I am quite happy with them, even snmp on them for monitoring purposes (I am having nagios to monitor port status, link speed etc) runs out-of-the-box. Just my 0.02 EUR ;-) Olaf -- Olaf Hoyer ohoyer@gaff.hhhr.ision.net Fuerchterliche Erlebniss geben zu raten, ob der, welcher sie erlebt, nicht etwas Fuerchterliches ist. (Nietzsche, Jenseits von Gut und Boese) From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 13 06:44: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 E6A3D16A4B3 for ; Mon, 13 Oct 2003 06:44:43 -0700 (PDT) Received: from moo.sysabend.org (moo.sysabend.org [66.111.41.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6766043FCB for ; Mon, 13 Oct 2003 06:44:42 -0700 (PDT) (envelope-from ragnar@sysabend.org) Received: by moo.sysabend.org (Postfix, from userid 1004) id BA3717FC; Mon, 13 Oct 2003 06:44:41 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by moo.sysabend.org (Postfix) with ESMTP id B8C8F7FA; Mon, 13 Oct 2003 06:44:41 -0700 (PDT) Date: Mon, 13 Oct 2003 06:44:41 -0700 (PDT) From: Jamie Bowden To: "C. Stephen Gunn" In-Reply-To: <20031012140627.GA85255@waterspout.com> Message-ID: <20031013063509.E20891-100000@moo.sysabend.org> X-representing: Only myself. X-badge: We don't need no stinking badges. X-obligatory-profanity: Fuck X-moo: Moo. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: hardware@FreeBSD.org Subject: Re: PCI-X Multiport Serial cards. 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, 13 Oct 2003 13:44:44 -0000 On Sun, 12 Oct 2003, C. Stephen Gunn wrote: > Jamie Bowden (ragnar@sysabend.org) likely uttered: > > Does anyone have any experience with PCI-X multiport serial cards > > under FreeBSD (4 or 5, either is fine)? I've got a 1u Dell machine > > that in 3 weeks will lose it's current role in life, and I'd like to > > use it as a console server for a bunch of headless SGI and Sun boxes. > > Its only expansion slot is PCI-X. If anyone can recommend a known > > working card with at least 8 ports, I'd appreciate it. > First I think that PCI-X is just 133Mhz by 64-bit PCI. You should be > bacward compatible. Regular PCI is perfect for nearly anything you > might want to do. And this machine clearly has the muscle to be one > heck of a nice conserver. PCI-X is a different form, a standard PCI card will not fit and line up with the edge of the case (I found this out when I tried to add a parallel port to the machine, a plain jane PCI parallel card didn't fit). > You might check out the PCI boards from Cyclades. I've used both > the Cyclom-Y and Cyclom-Z board successfully under FreeBSD. I did > have some trouble with Cyclom-Y under 4.X and reverted to 2.2.8 > to run it (It was 3 years ago so I can't be sure). I'll have to check with Cyclades and see if they are selling PCI-X form cards yet. Has anyone tried any of the Cyclades cards under 5.x? This machine would be tracking RELENG_5_1 initially, and 5-S once it migrates from 4. > You might also look into the 1-U rackmount products from Lantronix > or Cyclades. A private Ethernet segment is nearly as good as > a custom interconnect to the server. I have network access to the machines in question now; the plan is to have their consoles available to me from my desk via ssh or a remote location (this machine will have a modem on it in case the network is down and I need to get in). I've considered using an old portmaster 2e, but it doesn't do ssh. Currently I just have an old Wyse term that I shuffle cables around on depending on which machine I need console access to. > KS Braunsdorf's variant of conserver we run at work knows how > to talk directly to a tcp/ip destination, you just spell the > serial device differently in conserver.cf. I'm not sure about > the ports, or comserver.com variants of conserver, but it wouldn't > surprise me if they supported it too. > > The machine you have could easily handle 2-3 Muxes, so you > have plenty of room to grow. Plus you can easily drop a second > machine on the black network and not be dead if the conserver > has a hardware issue, either. :) > > - Steve > Jamie Bowden -- "It was half way to Rivendell when the drugs began to take hold" Hunter S Tolkien "Fear and Loathing in Barad Dur" Iain Bowen From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 14 14:09:52 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 51E9416A4B3 for ; Tue, 14 Oct 2003 14:09:52 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52F7F43F3F for ; Tue, 14 Oct 2003 14:09:51 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id h9EL9orq013670 for ; Tue, 14 Oct 2003 17:09:50 -0400 (EDT) Date: Tue, 14 Oct 2003 17:09:50 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: hardware@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Network analyzers X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: deischen@freebsd.org List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Oct 2003 21:09:52 -0000 So what are all the cool folks now using for network analyzers. We'd like to be able to capture and analyze from all the common media: 10Base2/BNC, 10BaseT/UTP, 100BaseTX, 100BaseFX, 1000BaseTX (copper, SX, LX). Cost is not much of a concern (your U.S. tax dollars hard at work!) as capabilities and features. I was pointed at the Agilent J6800A series by someone here at work: http://we.home.agilent.com/cgi-bin/bvpub/agilent/Product/cp_Product.jsp?NAV_ID=-536889703.536882693.00&LANGUAGE_CODE=eng&COUNTRY_CODE=ZZ Any other recommendations? Thanks, -- Dan Eischen From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 14 20:00:58 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 673D916A4B3 for ; Tue, 14 Oct 2003 20:00:58 -0700 (PDT) Received: from ahab.dictos.com (adsl-67-125-129-106.dsl.frsn02.pacbell.net [67.125.129.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2192843F85 for ; Tue, 14 Oct 2003 20:00:57 -0700 (PDT) (envelope-from jason@ahab.dictos.com) Received: from ahab.dictos.com (localhost.dictos.com [127.0.0.1]) by ahab.dictos.com (8.12.9/8.12.9) with ESMTP id h9EF0LhS000873 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Tue, 14 Oct 2003 08:00:21 -0700 (PDT) (envelope-from jason@ahab.dictos.com) Received: from localhost (localhost [[UNIX: localhost]]) by ahab.dictos.com (8.12.9/8.12.9/Submit) id h9EF0GNf000872 for freebsd-hardware@freebsd.org; Tue, 14 Oct 2003 08:00:16 -0700 (PDT) (envelope-from jason) From: jason dictos To: freebsd-hardware@freebsd.org Date: Tue, 14 Oct 2003 08:00:16 -0700 User-Agent: KMail/1.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200310140800.16298.jason@dictos.com> Subject: Weird usb keyboard problem X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jason@dictos.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2003 03:00:58 -0000 Hi All, I have a logitech wireless keyboard, plugged into the onboard usb on my Tyan dual pIII motherboard running a Via chipset. Whenever I use the keyboard and type at a normal rate, it seems like the usb driver or whatever detects more ekeys then I've pressed. Here is san example of fwhat thappens when nI tytpe at ta normal r ate on nmy u sb k eybobard with hFreeBSD 5.1. How can I debug this?? When I use a PS/2 keyboard, the problem does not occur. Needless to say it is very annoying to type slowly constantly. Any help would be appreciated!! -Jason From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 14 23:48:13 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 6C6BF16A4B3 for ; Tue, 14 Oct 2003 23:48:13 -0700 (PDT) Received: from vusa.lt (ns.vusa.lt [193.219.44.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id A813043FAF for ; Tue, 14 Oct 2003 23:48:12 -0700 (PDT) (envelope-from molotov@vusa.lt) Received: by vusa.lt (Postfix, from userid 1005) id C25221049A; Wed, 15 Oct 2003 09:48:10 +0300 (EEST) Date: Wed, 15 Oct 2003 09:48:10 +0300 From: molotov To: freebsd-hardware@freebsd.org Message-ID: <20031015064810.GA76908@vusa.lt> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: the new IC7-MAX3 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: Wed, 15 Oct 2003 06:48:13 -0000 Hello, as most of you know,there is a recently released motherboard from ABIT, the IC7-MAX3. It seems, that it's features should satisfy anyone, but there is one problem. The motherboard has a SATA RAID controller, the SiI 3114, which is apparently not supported by FreeBSD-CURRENT. As I do not have much knowledge in FreeBSD kernel hacking, I just tried to modify the source in some way and added the PCI identifier of the 3114 controller to ata-chipset.c and ata-pci.h. After this, without any sata drives attached, the raid controller was identified correctly and I was quite happy, but after I've configured a raid0 array and booted FreeBSD again, it hanged and it hangs all the time with this "hacked" version of the FreeBSD kernel and disks attached. It doesn't depend on the type of RAID array or anything else. With an unpatched kernel I just receive this message: > pci3: at device 3.0 (no driver attached) Browsing through yesterday's logs I've found this: > Oct 14 18:35:26 b17 kernel: atapci0: port > 0x9000-0x900f,0x8c00-0x8c03,0x8800-0x8807,0x8400-0x8403,0x8000-0x8007 > mem 0xf7000000-0xf70003ff irq 11 at device 3.0 on pci3 You can find the diffs, the whole dmesg and the output of pciconf -vl at http://b17.vu.lt/diffs/ . You may wonder why the log says "SiI 311" and not "SiI 3114" - it's becouse I simply mistyped it's name :) I'm almost sure and I hope, that it isn't the couse. Oh, and the questions: 1. how soon could we expect the support of this controller in FreeBSD? 2. am I on the right way with the kernel hacking? ;) Your help will be appreciated. Thank you in advance. P.S. the files I've patched are in /usr/src/sys/dev/ata/ sincerely, Simonas Kareiva Sysadmin @ Vilnius University student's dormitories Lithuania From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 15 17:38: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 DDD7316A4DE; Wed, 15 Oct 2003 17:38:43 -0700 (PDT) Received: from mail005.syd.optusnet.com.au (mail005.syd.optusnet.com.au [211.29.132.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FB8F43FA3; Wed, 15 Oct 2003 17:38:39 -0700 (PDT) (envelope-from freebsd.org@carmoda.com) Received: from carmoda.com (c211-28-220-147.kelvn1.qld.optusnet.com.au [211.28.220.147])h9G0cbs00342; Thu, 16 Oct 2003 10:38:38 +1000 Message-ID: <3F8E7652.4000901@carmoda.com> Date: Thu, 16 Oct 2003 10:43:30 +0000 From: Anthony Carmody Organization: Anthony Carmody Consulting Pty Ltd User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4b) Gecko/20030524 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-i386@freebsd.org, freebsd-hardware@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: cannot view network servers, no sound, wheel mouse? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: anthony@carmoda.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2003 00:38:44 -0000 Hi, I am new to using FreeBSD as a Workstation, although i have used FreeBSD for servers for various reasons for years. I have come into a few problems now i have pissed off M$ completely. [can't teach an old dog new tricks] Running FreeBSD 5.1 on an Intel D45PESV mainboard. [onboard sound AC97 AC1981B] i have no sound and i cannot browse my network machines in gnome. Everything seems to work just fine, just that i get an error upon starting gnome [something about the mixer] and when i go to add a network server i get nothing. I have noticed that logged in as 'root' i can see them, just not connect. i have no idea about testing sound outside of a GUI so i dont know about it being Gnome related... on another note: does anyone know if a USB wheel mouse can work with 5.1? [im using it with a ps2 adapter with no wheel now] help! -- Regards, Anthony John Carmody Anthony Carmody Consulting Pty Ltd Adaptable Business Computing Solutions ====================================== Cellular/Mobile: +61 414417457 Fax: +617 38708040 Email: anthony@carmoda.com From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 16 20:38: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 0003F16A4B3 for ; Thu, 16 Oct 2003 20:38:53 -0700 (PDT) Received: from web10107.mail.yahoo.com (web10107.mail.yahoo.com [216.136.130.57]) by mx1.FreeBSD.org (Postfix) with SMTP id 6F8A743F85 for ; Thu, 16 Oct 2003 20:38:53 -0700 (PDT) (envelope-from twigles@yahoo.com) Message-ID: <20031017033853.41211.qmail@web10107.mail.yahoo.com> Received: from [68.5.49.41] by web10107.mail.yahoo.com via HTTP; Thu, 16 Oct 2003 20:38:53 PDT Date: Thu, 16 Oct 2003 20:38:53 -0700 (PDT) From: twig les To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Wireless PCI card support (pcmcia to a lesser degree) 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: Fri, 17 Oct 2003 03:38:54 -0000 OK, I'm a noob at wireless so I poked around Google and the lists and got a nice netgear 401 pcmcia card and accompanying AP; they work great. But having only one laptop I need a wireless PCI card to tinker with things like Kismet/BSD air tools and setting up my laptop as an AP with IPSec...ya know, all the fun stuff (I do NOT break into systems). To this end I have spent multiple hours online googling to find a PCI card that I know will work. I have also bought and returned a DLINK 520 (not the +) after reading that it worked, then trying it and finding out they pulled the old chipset switch-a-roo. I now have a nice new SMC 2602W, and from googling the lists I see that SMC changed it's chipset also. There is a point to this inane babbling...I was wondering if there is a central web page I'm missing that has somewhat current status on the state of wireless card support. Specifically: Which cards use which chipsets and how to find out before we buy them? Which companies actually increment/change their product numbers when they switch chipsets? What is the status of non-wi drivers in FreeBSD? Like the adm driver I think I now need for this $60 paperweight I bought. Maybe even the contact info for companies so we can send our gripes to them instead of to each other :). I'll start: http://www.smc.com/index.cfm?action=techsupport_contact They even have Linux in the dropdown menu in their little form (*BSD is expecting too much) which in this case probably covers us driver-support wise. ===== ----------------------------------------------------------- Get a taste of Religion ... eat a priest! ----------------------------------------------------------- __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 17 03:21:59 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 06AA116A4B3 for ; Fri, 17 Oct 2003 03:21:58 -0700 (PDT) Received: from mail.johnrshannon.com (mail.johnrshannon.com [69.20.155.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA95F43F93 for ; Fri, 17 Oct 2003 03:21:57 -0700 (PDT) (envelope-from john@johnrshannon.com) Received: by mail.johnrshannon.com (Postfix, from userid 1003) id 6CECE124A8; Fri, 17 Oct 2003 04:21:57 -0600 (MDT) Received: from pablo.internal.johnrshannon.com (pablo.internal.johnrshannon.com [192.168.1.34]) by mail.johnrshannon.com (Postfix) with ESMTP id 9970E12492 for ; Fri, 17 Oct 2003 04:21:56 -0600 (MDT) Received: by pablo.internal.johnrshannon.com (Postfix, from userid 1001) id 090A818D; Fri, 17 Oct 2003 04:21:56 -0600 (MDT) From: "John R. Shannon" To: freebsd-hardware@freebsd.org Date: Fri, 17 Oct 2003 04:21:49 -0600 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_9K8j/y7L7aACD7s" Message-Id: <200310170421.55829.john@johnrshannon.com> Subject: Repetitive filesystem corruption X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: john@johnrshannon.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2003 10:21:59 -0000 --Boundary-00=_9K8j/y7L7aACD7s Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Description: clearsigned data Content-Disposition: inline =46reeBSD 5.1-RELEASE-p10 CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.02-MHz 686-class CPU) I'm experiencing a problem on one computer with the filesystem corrupting=20 repetitively; another system here with the same software configuration but= =20 older hardware is working fine. When the system shuts down, I get the=20 message: syncing disks, buffers remaining... 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 giving up on 2 buffers If I reboot into single user mode and run fsck, it reports corruption most = of=20 the time. I have verified the media using the verify command in the SCSI=20 controllers BIOS. Any help would be appreciated. Dmesg output attached. =2D-=20 John R. Shannon john@johnrshannon.com --Boundary-00=_9K8j/y7L7aACD7s Content-Type: text/plain; charset="us-ascii"; name="dmesg.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="dmesg.txt" Waiting (max 60 seconds) for system process `vnlru' to stop...stopped Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped Waiting (max 60 seconds) for system process `syncer' to stop...timed out syncing disks, buffers remaining... 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 giving up on 2 buffers Uptime: 2m32s Terminate ACPI Rebooting... cpu_reset called on cpu#0 cpu_reset: Stopping other CPUs 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 5.1-RELEASE-p10 #0: Wed Oct 8 07:47:30 CDT 2003 root@venus.sed.redstone.army.mil:/usr/obj/usr/src/sys/KERNEL Preloaded elf kernel "/boot/kernel/kernel" at 0xc0789000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0789244. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 2793015636 Hz CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 1072889856 (1023 MB) avail memory = 1034244096 (986 MB) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00050014, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00178020, at 0xfec00000 Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pcibios: BIOS version 2.10 Using $PIR table, 11 entries at 0xc00f3310 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-safe" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_cpu0: port 0x530-0x537 on acpi0 acpi_cpu1: port 0x530-0x537 on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 IOAPIC #0 intpin 16 -> irq 2 IOAPIC #0 intpin 19 -> irq 16 IOAPIC #0 intpin 18 -> irq 17 IOAPIC #0 intpin 23 -> irq 18 IOAPIC #0 intpin 17 -> irq 19 agp0: mem 0xf8000000-0xfbffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pcib2: at device 3.0 on pci0 pci2: on pcib2 em0: port 0xac00-0xac1f mem 0xfe1e0000-0xfe1fffff irq 17 at device 1.0 on pci2 em0: Speed:100 Mbps Duplex:Full uhci0: port 0xe000-0xe01f irq 2 at device 29.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xe400-0xe41f irq 16 at device 29.1 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xe800-0xe81f irq 17 at device 29.2 on pci0 usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xec00-0xec1f irq 2 at device 29.3 on pci0 usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pci0: at device 29.7 (no driver attached) pcib3: at device 30.0 on pci0 pci3: on pcib3 IOAPIC #0 intpin 21 -> irq 20 IOAPIC #0 intpin 22 -> irq 21 mpt0: port 0xc800-0xc8ff mem 0xfeae0000-0xfeaeffff,0xfeaf0000-0xfeafffff irq 20 at device 0.0 on pci3 ahc0: port 0xc400-0xc4ff mem 0xfeadf000-0xfeadffff irq 21 at device 1.0 on pci3 aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs pcm0: port 0xcc00-0xcc3f irq 16 at device 3.0 on pci3 pcm0: fxp0: port 0xc000-0xc03f mem 0xfea80000-0xfea9ffff,0xfeade000-0xfeadefff irq 17 at device 4.0 on pci3 fxp0: Ethernet address 00:02:b3:d7:13:f4 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 31.0 on pci0 isa0: on isab0 ichsmb0: port 0xdc00-0xdc1f irq 19 at device 31.3 on pci0 acpi_button0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3,0x3f0-0x3f1 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A ppc0 port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: