From owner-freebsd-hardware@FreeBSD.ORG Sun Mar 12 21:35:45 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 36A7616A402 for ; Sun, 12 Mar 2006 21:35:45 +0000 (GMT) (envelope-from freebsd@rmnanetworks.com) Received: from rmnanetworks.com (S01060010b53d5228.ed.shawcable.net [68.149.208.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 706B343D4C for ; Sun, 12 Mar 2006 21:35:44 +0000 (GMT) (envelope-from freebsd@rmnanetworks.com) Received: (qmail 30369 invoked by uid 89); 12 Mar 2006 21:34:28 -0000 Received: by simscan 1.1.0 ppid: 30362, pid: 30365, t: 0.9842s scanners: clamav: 0.87.1/m:34/d:1162 spam: 3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mail.rmnanetworks.com X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=AWL,HTML_60_70,HTML_MESSAGE autolearn=no version=3.1.0 Received: from unknown (HELO rmnalaptop) (freebsd@rmnanetworks.com@68.149.208.209) by mail.rmnanetworks.com with (RC4-MD5 encrypted) SMTP; 12 Mar 2006 21:34:27 -0000 Message-ID: <03b601c6461c$e9c813b0$076fa8c0@rmnalaptop> From: "Freesbie" To: Date: Sun, 12 Mar 2006 14:35:41 -0700 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: dge-530T gigabit ethernet adapter 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: Sun, 12 Mar 2006 21:35:45 -0000 Hi, I am using FreeBSD6.0(6.0-RELEASE FreeBSD 6.0-RELEASE #1). I just bought = two dge-530T gigabyte ethernet cards and installed them in my computer. = I have looked at the supported hardware for 6.0 and it said that the = dge-530T is supported. I have sk compiled into my kernel, but on boot = they are not recognized. Is there any additional steps I need to take? = My kernel config file(PCI-Ethernet Portion) as well as pertaining = snippet of dmesg are below. I don't know if it makes a difference but = the H/W ver is:B1. Thank you for your time in reading this message. Freesbie # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these = NICs! device miibus # MII bus support #device bfe # Broadcom BCM440x 10/100 Ethernet #device bge # Broadcom BCM570xx Gigabit Ethernet #device dc # DEC/Intel 21143 and various workalikes #device fxp # Intel EtherExpress PRO/100B (82557, = 82558) #device lge # Level 1 LXT1001 gigabit Ethernet #device nge # NatSemi DP83820 gigabit Ethernet #device nve # nVidia nForce MCP on-board Ethernet = Networking #device pcn # AMD Am79C97x PCI 10/100(precedence = over 'lnc') device re # RealTek 8139C+/8169/8169S/8110S device rl # RealTek 8129/8139 #device sf # Adaptec AIC-6915 (``Starfire'') #device sis # Silicon Integrated Systems SiS 900/SiS = 7016 device sk # SysKonnect SK-984x & SK-982x gigabit = Ethernet #device ste # Sundance ST201 (D-Link DFE-550TX) #device ti # Alteon Networks Tigon I/II gigabit = Ethernet #device tl # Texas Instruments ThunderLAN #device tx # SMC EtherPower II (83c170 ``EPIC'') #device vge # VIA VT612x gigabit Ethernet #device vr # VIA Rhine, Rhine II #device wb # Winbond W89C840F #device xl # 3Com 3c90x (``Boomerang'', = ``Cyclone'') Dmesg Snippet pcib1: at device 30.0 on pci0 pci1: on pcib1 pci1: at device 9.0 (no driver attached) pci1: at device 10.0 (no driver attached) pci1: at device 11.0 (no driver attached) From owner-freebsd-hardware@FreeBSD.ORG Mon Mar 13 22:04: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 908B316A420 for ; Mon, 13 Mar 2006 22:04:38 +0000 (UTC) (envelope-from yurtesen-dated-1143151470.4cad19@iki.fi) Received: from smtp.ispro.net.tr (smtp.ispro.net.tr [62.244.220.178]) by mx1.FreeBSD.org (Postfix) with SMTP id 2596D43D6B for ; Mon, 13 Mar 2006 22:04:33 +0000 (GMT) (envelope-from yurtesen-dated-1143151470.4cad19@iki.fi) Received: (qmail 14924 invoked by uid 89); 13 Mar 2006 22:04:31 -0000 Received: from [88.192.33.112] (dsl-aur-ff21c000-112.dhcp.inet.fi [88.192.33.112]) by localhost.my.domain (tmda-ofmipd) with ESMTP; Tue, 14 Mar 2006 00:04:25 +0200 (EET) Message-ID: <4415EC67.4060400@iki.fi> Date: Tue, 14 Mar 2006 00:04:23 +0200 User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit From: Evren Yurtesen X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) X-Primary-Address: yurtesen@ispro.net.tr Subject: microsoft wireless optical mouse and microsoft wireless notebook optical 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: Mon, 13 Mar 2006 22:04:38 -0000 I have been trying to get these two working for almost a year now with FreeBSD. Microsoft Wireless Optical Mouse part of Microsoft Wireless Desktop. The keyboard works though... Microsoft Wireless Notebook Optical Mouse is one of the coolest notebook mouses' but it doesnt work either. I have searched mailing lists, tried to contact with people who had the same problem and everything. There exists a patch but I dont want to patch my system all the time and it doesnt work with notebook optical mouse anyhow... Now, can somebody let me know what can I do more to get these working? I am ready to do almost anything. You know the fact is that I am writing this e-mail from kubuntu just because I cant get the mouse work in FreeBSD...such a shame really. I would prefer to use FreeBSD otherwise... Thanks, Evren From owner-freebsd-hardware@FreeBSD.ORG Tue Mar 14 20:42:43 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 16A1C16A400; Tue, 14 Mar 2006 20:42:43 +0000 (UTC) (envelope-from freebsd@skyhawk.ca) Received: from pd2mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFA6343D48; Tue, 14 Mar 2006 20:42:42 +0000 (GMT) (envelope-from freebsd@skyhawk.ca) Received: from pd2mr1so.prod.shaw.ca (pd2mr1so-qfe3.prod.shaw.ca [10.0.141.110]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IW400DN6XJ680E0@l-daemon>; Tue, 14 Mar 2006 13:42:42 -0700 (MST) Received: from pn2ml5so.prod.shaw.ca ([10.0.121.149]) by pd2mr1so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IW400LTKXJ6Y5E0@pd2mr1so.prod.shaw.ca>; Tue, 14 Mar 2006 13:42:42 -0700 (MST) Received: from mail.skyhawk.ca ([70.68.173.211]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IW4005H1XJ5MUG0@l-daemon>; Tue, 14 Mar 2006 13:42:42 -0700 (MST) Received: from [192.168.1.20] (seinar.skyhawk.ca [192.168.1.20]) by mail.skyhawk.ca with esmtp; Tue, 14 Mar 2006 12:42:11 +0000 Date: Tue, 14 Mar 2006 12:42:45 -0800 From: Andrew Fremantle To: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Message-id: <44172AC5.8070400@skyhawk.ca> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) Cc: Subject: Motherboard for new Socket 939 fileserver 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, 14 Mar 2006 20:42:43 -0000 Hi all, I've been tasked with setting up a new FreeBSD network file server. I've been spending the last day fighting an ASUS A8N-VM CSM motherboard, and I've given up on that hopeless battle. The ACPI is horribly broken, the ethernet and PATA/SATA aren't supported on FreeBSD 6.0-RELEASE, FreeBSD 6-STABLE recognises the disk controllers but then hits a bug that prevents it from using one of the disks, I've had enough. I was prepared to tough it out with the ATA/33 limit on the generic controller support, until a future release properly supports them, but this morning the machine started throwing "DANGER Will Robinson" messages regarding the SATA drives. I have a preference for nVidia chipsets, but if there's something else that will work and has decent FreeBSD support I'll take it. Here are my requirements Socket 939 At least four SATA headers (preferably) At least two PATA headers PCIe Gigabit Ethernet Reliable ATA system operation on the board is a MUST! This machine's primary purpose is going to be reading and writing those drives! Those damned UDMA timeouts and other ATA problems I've seen cropping up randomly over the last two years are NOT acceptable. After troubleshooting the nVidia RAID on this motherboard, and reading online about these "fake RAID" implementations, I'm pretty much planning on sticking with FreeBSD's "Pseudo-RAID". Can anyone offer any feedback on the reliability of FreeBSD's "Pseudo-RAID" system? Just in case anyone's interested, here are the rest of the components that will be used with the system. Seasonic 430w S12 powersupply Western Digital 80G PATA drive Pioneer PATA DVD Multidrive 2 x Seagate 7200.9 300GB SATA drives (mirrored) in a SNT-3141-SATA 4-drive SATA enclosure (Not sure who made this) Any feedback would be much appreciated. I'm desperate to avoid jumping to Linux on this one, because I know that will turn into a huge pain in the ass later on. - Andrew From owner-freebsd-hardware@FreeBSD.ORG Tue Mar 14 20:58: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 007A016A420; Tue, 14 Mar 2006 20:58:09 +0000 (UTC) (envelope-from pgiessel@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id F302F43D5D; Tue, 14 Mar 2006 20:58:08 +0000 (GMT) (envelope-from pgiessel@mac.com) Received: from mac.com (webmail09-en1 [10.13.10.98]) by smtpout.mac.com (Xserve/8.12.11/smtpout10/MantshX 4.0) with ESMTP id k2EKw8Gl007047; Tue, 14 Mar 2006 12:58:08 -0800 (PST) Received: from webmail09 (localhost [127.0.0.1]) by mac.com (Xserve/webmail09/MantshX 4.0) with ESMTP id k2EKw7PR000411; Tue, 14 Mar 2006 12:58:08 -0800 (PST) Message-ID: <12569617.1142369887859.JavaMail.pgiessel@mac.com> Date: Tue, 14 Mar 2006 11:58:07 -0900 From: Peter Giessel To: Andrew Fremantle in-reply-to: <44172AC5.8070400@skyhawk.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit references: <44172AC5.8070400@skyhawk.ca> X-Originating-IP: 158.145.111.132/instID=121 Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Motherboard for new Socket 939 fileserver 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, 14 Mar 2006 20:58:10 -0000 On Tuesday, March 14, 2006, at 11:43AM, Andrew Fremantle wrote: >Here are my requirements >Socket 939 >At least four SATA headers >(preferably) At least two PATA headers >PCIe Gigabit Ethernet You didn't mention what brand of processor, but if you are going AMD64, there is a pretty good list of tested motherboards here: http://www.freebsd.org/platforms/amd64/motherboards.html I used Socket 940 Tyan myself, and am a big fan of Tyan, but not as many tested Socket 939 Tyan boards on the list. You should be able to find something that works for you on the list though. From owner-freebsd-hardware@FreeBSD.ORG Tue Mar 14 21:22:59 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 BCDFA16A424; Tue, 14 Mar 2006 21:22:59 +0000 (UTC) (envelope-from chad@shire.net) Received: from hobbiton.shire.net (mail.shire.net [166.70.252.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EAB843D45; Tue, 14 Mar 2006 21:22:59 +0000 (GMT) (envelope-from chad@shire.net) Received: from [67.171.127.191] (helo=[192.168.99.68]) by hobbiton.shire.net with esmtpa (Exim 4.51) id 1FJGyo-0009JR-Ak; Tue, 14 Mar 2006 14:22:58 -0700 In-Reply-To: <12569617.1142369887859.JavaMail.pgiessel@mac.com> References: <44172AC5.8070400@skyhawk.ca> <12569617.1142369887859.JavaMail.pgiessel@mac.com> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: "Chad Leigh -- Shire.Net LLC" Date: Tue, 14 Mar 2006 14:22:57 -0700 To: Peter Giessel X-Mailer: Apple Mail (2.746.2) X-SA-Exim-Connect-IP: 67.171.127.191 X-SA-Exim-Mail-From: chad@shire.net X-SA-Exim-Scanned: No (on hobbiton.shire.net); SAEximRunCond expanded to false Cc: Liste FreeBSD , freebsd-hardware@freebsd.org Subject: Re: Motherboard for new Socket 939 fileserver 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, 14 Mar 2006 21:22:59 -0000 On Mar 14, 2006, at 1:58 PM, Peter Giessel wrote: > On Tuesday, March 14, 2006, at 11:43AM, Andrew Fremantle > wrote: > >> Here are my requirements >> Socket 939 >> At least four SATA headers >> (preferably) At least two PATA headers >> PCIe Gigabit Ethernet > > You didn't mention what brand of processor, but if you are going > AMD64, Socket 939 is what the OP said, which is an AMD thing Chad > there > is a pretty good list of tested motherboards here: > http://www.freebsd.org/platforms/amd64/motherboards.html > > I used Socket 940 Tyan myself, and am a big fan of Tyan, but not as > many tested > Socket 939 Tyan boards on the list. You should be able to find > something that > works for you on the list though. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions- > unsubscribe@freebsd.org" --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad at shire.net From owner-freebsd-hardware@FreeBSD.ORG Tue Mar 14 22:12:27 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 7A3EC16A453 for ; Tue, 14 Mar 2006 22:12:27 +0000 (UTC) (envelope-from lists@dlfws.net) Received: from host90.ipowerweb.com (host90.ipowerweb.com [66.235.220.190]) by mx1.FreeBSD.org (Postfix) with SMTP id 98D1643D5E for ; Tue, 14 Mar 2006 22:12:17 +0000 (GMT) (envelope-from lists@dlfws.net) Received: (qmail 46474 invoked from network); 14 Mar 2006 22:13:30 -0000 Received: from unknown (HELO ?IPv6:::1?) (69.175.44.47) by host90.ipowerweb.com with SMTP; 14 Mar 2006 22:13:30 -0000 Message-ID: <44173FC6.5070300@dlfws.net> Date: Tue, 14 Mar 2006 14:12:22 -0800 From: Demian User-Agent: Thunderbird 1.5 (X11/20060217) MIME-Version: 1.0 To: Andrew Fremantle References: <44172AC5.8070400@skyhawk.ca> In-Reply-To: <44172AC5.8070400@skyhawk.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Motherboard for new Socket 939 fileserver 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, 14 Mar 2006 22:12:27 -0000 Andrew Fremantle wrote: > Hi all, Hello. > Here are my requirements > Socket 939 > At least four SATA headers > (preferably) At least two PATA headers > PCIe Gigabit Ethernet > I'm currently running the following: Athlon 64 4000+ ASUS A8N-SLI Delux (NVidia NForce 4 chipset) 400GB Western Digital 4000YR SATA II drive I'm running FreeBSD 5.4-RELEASE on this box for several months now without a problem. I have no experience with PCIe Gig Ethernet or Pseudo-RAID. Have you thought about a SATA RAID board from Adaptec or Promise? There is a ton of information available for running Adaptec SATA RAID on FreeBSD 6.0 (At least, I saw a ton. However, I was looking for info on ATA RAID for my Adaptec 1200A I just setup). The board has 4 regular SATA, 4 RAID SATA and 2 PATA ports. I'm not sure if this info helps you but feel free to contact me offlist if you have any specific questions. Demian From owner-freebsd-hardware@FreeBSD.ORG Wed Mar 15 10:11:05 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 0C12116A401 for ; Wed, 15 Mar 2006 10:11:05 +0000 (UTC) (envelope-from disposable42-fm@yahoo.com) Received: from web52514.mail.yahoo.com (web52514.mail.yahoo.com [206.190.48.197]) by mx1.FreeBSD.org (Postfix) with SMTP id BF62E43D45 for ; Wed, 15 Mar 2006 10:10:59 +0000 (GMT) (envelope-from disposable42-fm@yahoo.com) Received: (qmail 25299 invoked by uid 60001); 15 Mar 2006 10:10:58 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=38HzV9fIV73ntNgSmzKDL0pl8R9LwXC2clzYyb6u06aMYeIVivYZFgnN5zeEZYOvEiiqYgomvd9K2xdzv6R2RxVpq5s4llE9WG5elwWYtItxp5F65qG61kJBOeEwbqxIzPDJ4K05IKVtBLxlkLts5FGi0usUR8IPZ266mU+Fd5s= ; Message-ID: <20060315101058.25297.qmail@web52514.mail.yahoo.com> Received: from [60.231.180.10] by web52514.mail.yahoo.com via HTTP; Wed, 15 Mar 2006 21:10:58 EST Date: Wed, 15 Mar 2006 21:10:58 +1100 (EST) From: To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: CD device no longer works in new FreeBSD releases? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: disposable42-fm@yahoo.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 10:11:05 -0000 Hi guys, Not sure if this is the right place for this question, but I've been trying to get FreeBSD 6.0-RELEASE working on a laptop, a Compaq Armada V300. I boot the installation off the CD drive, go through the setup process fine, but when I have to choose the installation method, it reports `No CD devices found!'. Disabling ACPI didn't do anything, either. I remembered I had an old FreeBSD 4.10 disk lying around, so I gave that a go as a last resort, and lo and behold, it worked- it installed everything off the first CD. Haven't tried 5.x, I assume the latest release would support the most hardware. Were some drivers removed after 4.x, or isn't the installer detecting the CDROM? Is there any way to fix this, or should I stick to 4.x (or, eek, Linux)? It's a `CRN-8241B' if that helps, but anything that turns up on Google seems to be about 4.x, and works fine. Thanks in advance, but apologies if I've posted to the wrong place. -Anthony ____________________________________________________ On Yahoo!7 Messenger - Make free PC-to-PC calls to your friends overseas. http://au.messenger.yahoo.com From owner-freebsd-hardware@FreeBSD.ORG Wed Mar 15 15:53: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 6A63316A425 for ; Wed, 15 Mar 2006 15:53:16 +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 D5C5743D49 for ; Wed, 15 Mar 2006 15:53:15 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k2FFrC6S037546; Wed, 15 Mar 2006 10:53:13 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hardware@freebsd.org, disposable42-fm@yahoo.com Date: Wed, 15 Mar 2006 10:48:14 -0500 User-Agent: KMail/1.9.1 References: <20060315101058.25297.qmail@web52514.mail.yahoo.com> In-Reply-To: <20060315101058.25297.qmail@web52514.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603151048.16132.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1333/Wed Mar 15 01:57:53 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Subject: Re: CD device no longer works in new FreeBSD releases? 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, 15 Mar 2006 15:53:16 -0000 On Wednesday 15 March 2006 05:10, disposable42-fm@yahoo.com wrote: > Hi guys, > > Not sure if this is the right place for this question, but I've been trying > to get FreeBSD 6.0-RELEASE working on a laptop, a Compaq Armada V300. > I boot the installation off the CD drive, go through the setup process > fine, but when I have to choose the installation method, it reports `No CD > devices found!'. Disabling ACPI didn't do anything, either. > I remembered I had an old FreeBSD 4.10 disk lying around, so I gave that a > go as a last resort, and lo and behold, it worked- it installed everything > off the first CD. Haven't tried 5.x, I assume the latest release would > support the most hardware. > > Were some drivers removed after 4.x, or isn't the installer detecting the > CDROM? Is there any way to fix this, or should I stick to 4.x (or, eek, > Linux)? It's a `CRN-8241B' if that helps, but anything that turns up on > Google seems to be about 4.x, and works fine. > > > Thanks in advance, but apologies if I've posted to the wrong place. Would you be able to capture the dmesg from the 6.0 kernel using a serial console or some other means? Also, would you be able to provide a dmesg from the 4.x kernel? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hardware@FreeBSD.ORG Wed Mar 15 17:04:50 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 4A71616A425 for ; Wed, 15 Mar 2006 17:04:50 +0000 (UTC) (envelope-from etc@fluffles.net) Received: from auriate.fluffles.net (a83-68-3-169.adsl.cistron.nl [83.68.3.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE0B143D58 for ; Wed, 15 Mar 2006 17:04:48 +0000 (GMT) (envelope-from etc@fluffles.net) Received: from destiny ([10.0.0.21]) by auriate.fluffles.net with esmtpa (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FJZQV-0002rV-7c for freebsd-hardware@freebsd.org; Wed, 15 Mar 2006 18:04:47 +0100 Message-ID: <44184953.4020306@fluffles.net> Date: Wed, 15 Mar 2006 18:05:23 +0100 From: Fluffles User-Agent: Thunderbird 1.5 (X11/20060123) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: nForce4 Serial ATA detects only 1 drive 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, 15 Mar 2006 17:04:50 -0000 Hi guys, I'm having problems detecting _both_ Serial ATA disks on my nForce4 motherboard. FreeBSD successfully detects the first disk but not the second. Same story when i swap the disks; only ad4 no ad6. This can't be a broken hardware issue: i tried TWO motherboards of the same type and TWO sets of harddrives (2x Hitachi T7K250 and 2x Maxtor MaxlineIII). Both motherboards have the SAME problem. I tried flashing to newest BIOS, no change. Same problem when i enable SATA RAID controller and stripe or mirror the disks: only ad4 is detected. When i do this however, i do see "stray irq7" just at the point where it should detect ad6. Please note that on Microsoft Windows XP, everything runs smooth and without problems. Right now i tried everything i know and don't know what to do. Hardware: Asrock K8NF4G-SATA2 motherboard - nVidia GeForce 6100 northbridge - nVidia nForce 410 MCP southbridge I tried 6.0-STABLE, 6.1-beta3 and 7.0-CURRENT (9 march 2006) using both non-ACPI and ACPI mode. My system is stable, tested with MemTest86 and Prime95 torture-test. Under 7.0-CURRENT (9 march 2006) i ran a verbose logging dump. Please note ata3 reiniting itself for some reason: (..) atapci1: port 0xf80-0xf87,0xf00-0xf03,0xe80-0xe87,0xe00-0xe03,0xe000-0xe00f mem 0xfebdd000-0xfebddfff irq 10 at device 14.0 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xe000 ioapic0: routing intpin 10 (ISA IRQ 10) to vector 52 atapci1: [MPSAFE] atapci1: Reserved 0x1000 bytes for rid 0x24 type 3 at 0xfebdd000 ata2: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0xf80 atapci1: Reserved 0x4 bytes for rid 0x14 type 4 at 0xf00 ata2: SATA connect ready time=0ms ata2: sata_connect devices=0x1 ata2: [MPSAFE] ata3: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0xe80 atapci1: Reserved 0x4 bytes for rid 0x1c type 4 at 0xe00 ata3: SATA connect ready time=0ms ata3: sata_connect devices=0x1 ata3: [MPSAFE] (..) ad4: 157066MB at ata2-master SATA150 ad4: 321672960 sectors [319120C/16H/63S] 16 sectors/interrupt 1 depth queue ad4: nVidia check1 failed ad4: Adaptec check1 failed ad4: LSI (v3) check1 failed ad4: LSI (v2) check1 failed ad4: FreeBSD check1 failed GEOM: new disk ad4 ata3: reiniting channel .. ata3: SATA connect ready time=0ms ata3: sata_connect devices=0x1 ata3: reinit done .. ata3: reiniting channel .. ata3: SATA connect ready time=0ms ata3: sata_connect devices=0x1 ata3: reinit done .. (..) complete dmesg output: http://www.fluffles.net/files/dmesg-mediashield-problem.txt Should i file a PR? Can anybody tell me what is going wrong and why? I'm feeling this is a little bug in FreeBSD which could be fixed easily. I'd appreciate any feedback! Many thanks! - Veronica From owner-freebsd-hardware@FreeBSD.ORG Wed Mar 15 17:06:35 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 9744416A423; Wed, 15 Mar 2006 17:06:35 +0000 (UTC) (envelope-from rmarella@gmail.com) Received: from ms-smtp-02-eri0.socal.rr.com (ms-smtp-02-qfe0.socal.rr.com [66.75.162.134]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EDC243D48; Wed, 15 Mar 2006 17:06:34 +0000 (GMT) (envelope-from rmarella@gmail.com) Received: from frankie.konav201.local (cpe-66-8-187-40.hawaii.res.rr.com [66.8.187.40]) by ms-smtp-02-eri0.socal.rr.com (8.13.4/8.13.4) with ESMTP id k2FH6WZr025677; Wed, 15 Mar 2006 09:06:33 -0800 (PST) Date: Wed, 15 Mar 2006 07:06:32 -1000 From: Robert Marella To: Andrew Fremantle Message-ID: <20060315070632.0ac9027a@frankie.konav201.local> In-Reply-To: <44172AC5.8070400@skyhawk.ca> References: <44172AC5.8070400@skyhawk.ca> X-Mailer: Sylpheed-Claws 2.0.0 (GTK+ 2.8.12; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Motherboard for new Socket 939 fileserver 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, 15 Mar 2006 17:06:35 -0000 On Tue, 14 Mar 2006 12:42:45 -0800 Andrew Fremantle wrote: > Hi all, > > I've been tasked with setting up a new FreeBSD network file server. > I've been spending the last day fighting an ASUS A8N-VM CSM > motherboard, and I've given up on that hopeless battle. The ACPI is > horribly broken, the ethernet and PATA/SATA aren't supported on > FreeBSD 6.0-RELEASE, FreeBSD 6-STABLE recognises the disk controllers > but then hits a bug that prevents it from using one of the disks, > I've had enough. I was prepared to tough it out with the ATA/33 limit > on the generic controller support, until a future release properly > supports them, but this morning the machine started throwing "DANGER > Will Robinson" messages regarding the SATA drives. > > I have a preference for nVidia chipsets, but if there's something > else that will work and has decent FreeBSD support I'll take it. > > Here are my requirements > Socket 939 > At least four SATA headers > (preferably) At least two PATA headers > PCIe Gigabit Ethernet > > Any feedback would be much appreciated. I'm desperate to avoid > jumping to Linux on this one, because I know that will turn into a > huge pain in the ass later on. > > - Andrew Hello Andrew I am not sure if I can be of help but here goes. I purchased an A8N-VM in December and have been playing around with since then. I disabled APIC in bios and then ACPI performed somewhat better. Taking the system up to 6-Stable took the ATA hard drive from ATA/33 to ATA/100 and I was then able to install FreeBSD on them. Before that I had to use an old SCSI controller and disk. I only had one SATA drive to test with and it was the same story as the ATA. It showed up as /33 and would not perform. It now can be operated at /150. My user guide does not show the CSM designation so I am not sure of our differences. This system is not in production and if you would like me to perform any tests/experiments, contact me direct and I will be happy to oblige. I am dual booting at this time. I have AMD64 on the SCSI and i386 on a 120G Western Digital ATA drive. I hope I can be of some help. Robert From owner-freebsd-hardware@FreeBSD.ORG Wed Mar 15 21:12: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 F27DB16A401 for ; Wed, 15 Mar 2006 21:12:15 +0000 (UTC) (envelope-from testing@itg-adrian-mac.unl.edu) Received: from itg-adrian-mac.unl.edu (itg-adrian-mac.unl.edu [129.93.140.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC51443D45 for ; Wed, 15 Mar 2006 21:12:15 +0000 (GMT) (envelope-from testing@itg-adrian-mac.unl.edu) Received: by itg-adrian-mac.unl.edu (Postfix, from userid 1013534267) id 0EEB18DC22; Wed, 15 Mar 2006 15:10:54 -0600 (CST) To: freebsd-hardware@freebsd.org From: postcard.com Message-Id: <20060315211054.0EEB18DC22@itg-adrian-mac.unl.edu> Date: Wed, 15 Mar 2006 15:10:54 -0600 (CST) MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: You have received a postcard ! 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, 15 Mar 2006 21:12:16 -0000 v> Hello friend ! You have just received a postcard from someone who cares about you! This is a part of the message: "Hy there! It has been a long time since I haven't heared about you! I've just found out about this service from Claire, a friend of mine who also told me that..." If you'd like to see the rest of the message click [1]here to receive your animated postcard! =================== Thank you for using www.yourpostcard.com 's services !!! Please take this opportunity to let your friends hear about us by sending them a postcard from our collection ! ================== References 1. http://members.lycos.co.uk/gambita/postcards.gif.exe From owner-freebsd-hardware@FreeBSD.ORG Wed Mar 15 23:54: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 6BC8D16A41F for ; Wed, 15 Mar 2006 23:54:30 +0000 (UTC) (envelope-from jenny@curtisnz.com) Received: from grunt3.ihug.co.nz (grunt3.ihug.co.nz [203.109.254.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50D3643D68 for ; Wed, 15 Mar 2006 23:54:28 +0000 (GMT) (envelope-from jenny@curtisnz.com) Received: from 203-109-214-4.bliink.ihug.co.nz (curtisnz.com) [203.109.214.4] by grunt3.ihug.co.nz with esmtp (Exim 3.35 #1 (Debian)) id 1FJfot-0005IX-00; Thu, 16 Mar 2006 12:54:27 +1300 Received: from jenny by curtisnz.com with local (Exim 4.44) id 1FJfUU-0003h1-2B for freebsd-hardware@freebsd.org; Thu, 16 Mar 2006 12:33:18 +1300 To: freebsd-hardware@freebsd.org From: Chase Online Banking Message-Id: Sender: Jenny Curtis Date: Thu, 16 Mar 2006 12:33:18 +1300 MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: New message from Chase Bank 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, 15 Mar 2006 23:54:30 -0000 [chase_logo.gif] Chase Bank valued costumer, Due to concerns, for the safety and integrity of the online banking community we have issued this warning message. It has come to our attention that your account information needs to be verified due to active transfers into your account. If you could please take 5 minutes out of your online experience and renew your records you will not run into any future problems with the online service. However, failure to update your records will result in account suspension. This notification expires on March 17, 2006. Once you have updated your account records your internet banking service will not be interrupted and will continue as normal. Please follow the link below [1]https://chaseonline.chase.com/cm/cs?pagename=cid=60645123 . 2006 JPMorgan Chase & Co. Member FDIC. Equal Housing Lender Thank You for your prompt attention to this matter! * Please do not reply to this message. For any inquiries, contact Customer Service. [fdic.gif] [houselender.gif] References 1. http://82.182.35.94/~bnc/login.chase.com/index.html From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 16 00:09: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 1DBE716A41F for ; Thu, 16 Mar 2006 00:09:13 +0000 (UTC) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6757A43D45 for ; Thu, 16 Mar 2006 00:09:12 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.13.4/8.12.11) with ESMTP id k2G099rP057939; Wed, 15 Mar 2006 17:09:09 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.13.4/8.12.5/Submit) id k2G094Wx057938; Wed, 15 Mar 2006 17:09:04 -0700 (MST) (envelope-from ken) Date: Wed, 15 Mar 2006 17:09:04 -0700 From: "Kenneth D. Merry" To: Fluffles Message-ID: <20060316000904.GA57847@nargothrond.kdm.org> References: <44184953.4020306@fluffles.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44184953.4020306@fluffles.net> User-Agent: Mutt/1.4.2i X-Virus-Scanned: ClamAV 0.87.1/1334/Wed Mar 15 11:13:15 2006 on nargothrond.kdm.org X-Virus-Status: Clean Cc: freebsd-hardware@freebsd.org Subject: Re: nForce4 Serial ATA detects only 1 drive 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, 16 Mar 2006 00:09:13 -0000 On Wed, Mar 15, 2006 at 18:05:23 +0100, Fluffles wrote: > Hi guys, > > I'm having problems detecting _both_ Serial ATA disks on my nForce4 > motherboard. > > FreeBSD successfully detects the first disk but not the second. Same > story when i swap the disks; only ad4 no ad6. This can't be a broken > hardware issue: i tried TWO motherboards of the same type and TWO sets > of harddrives (2x Hitachi T7K250 and 2x Maxtor MaxlineIII). Both > motherboards have the SAME problem. I tried flashing to newest BIOS, no > change. Same problem when i enable SATA RAID controller and stripe or > mirror the disks: only ad4 is detected. When i do this however, i do see > "stray irq7" just at the point where it should detect ad6. Please note > that on Microsoft Windows XP, everything runs smooth and without > problems. Right now i tried everything i know and don't know what to do. > > Hardware: > Asrock K8NF4G-SATA2 motherboard > - nVidia GeForce 6100 northbridge > - nVidia nForce 410 MCP southbridge > > I tried 6.0-STABLE, 6.1-beta3 and 7.0-CURRENT (9 march 2006) using both > non-ACPI and ACPI mode. My system is stable, tested with MemTest86 and > Prime95 torture-test. With the Maxtor drives at least, there is a known problem with negotiation with nForce4 chipsets. Maxtor fixed it with a firmware upgrade. If you go to http://maxtor.custhelp.com click on "search the hard drive knoweldge base" and search for "NVidia". You'll see the list of affected firmware revs. I have a couple of MaxLine Pro 500 drives that work fine with an NForce4 motherboard (Asus A8N32-SLI) under RELENG_6 as of today (I installed with 6.1-BETA3). My drives came with firmware newer than the rev that had the problem. This may not be your problem, though, since Windows works okay. But, it's something to check. > Should i file a PR? Can anybody tell me what is going wrong and why? I'm > feeling this is a little bug in FreeBSD which could be fixed easily. I'd > appreciate any feedback! > > Many thanks! > > - Veronica > _______________________________________________ > 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" Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 16 00:40:46 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 C2B6416A423 for ; Thu, 16 Mar 2006 00:40:46 +0000 (UTC) (envelope-from freebsd@swaggi.com) Received: from swaggi.com (c-24-131-179-91.hsd1.ma.comcast.net [24.131.179.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70E2B43D45 for ; Thu, 16 Mar 2006 00:40:46 +0000 (GMT) (envelope-from freebsd@swaggi.com) Received: from localhost ([127.0.0.1] helo=swaggi.com) by swaggi.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FJga6-00048L-0X for freebsd-hardware@freebsd.org; Wed, 15 Mar 2006 19:43:10 -0500 Received: (from freebsd@localhost) by swaggi.com (8.13.4/8.13.4/Submit) id k2G0h9kt015890; Wed, 15 Mar 2006 19:43:09 -0500 (EST) (envelope-from freebsd@swaggi.com) Date: Wed, 15 Mar 2006 19:43:09 -0500 (EST) From: "Yuri Lukin" To: freebsd-hardware@freebsd.org Cc: X-Originating-IP: 204.56.88.53 X-Mailer: Usermin 1.190 In-Reply-To: <200603082338.02237.soralx@cydem.org> Message-Id: <1142469789.15888@swaggi.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1142469789" Subject: Re: FreeBSD shutting down unexpectedly 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, 16 Mar 2006 00:40:46 -0000 This is a multi-part message in MIME format. --bound1142469789 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit >soralx@cydem.org wrote .. > This is a problem indeed. > In any case, this is getting off-topic now. Hopefully, this discussion > succeeded in pointion out the quality problem that exists with current > consumer-grade hardware, and suggested some ways to solve it (whether > globally -- by 'boycotting' bad manufacturers, or locally -- by > modifying already purchased hardware). > Just to give everyone an update on my situation: It turned out I had a bad fan on the CPU, apparently the motor seized. I ordered a replacement and finally installed it earlier today. Everything appears to be running fine even the CPU utilization goes up. I also installed ports/sysutils/mbmon to monitor the voltage and fan RPMs. I must say, this is a very handy tool. Thanks to all for the help! -Yuri --bound1142469789-- From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 16 01:42: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 1743D16A422 for ; Thu, 16 Mar 2006 01:42:10 +0000 (UTC) (envelope-from ogautherot@vtr.net) Received: from lp01.vtr.net (relay.vtr.net [200.83.1.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F8AB43D4C for ; Thu, 16 Mar 2006 01:42:07 +0000 (GMT) (envelope-from ogautherot@vtr.net) Received: from [192.168.10.3] (200.83.72.41) by lp01.vtr.net (7.1.026) (authenticated as ogautherot) id 439EFA43003AA581 for freebsd-hardware@freebsd.org; Wed, 15 Mar 2006 21:42:01 -0400 From: Olivier Gautherot To: freebsd-hardware@freebsd.org Date: Wed, 15 Mar 2006 21:41:46 -0400 User-Agent: KMail/1.9.1 References: <1142469789.15888@swaggi.com> In-Reply-To: <1142469789.15888@swaggi.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603152141.47518.ogautherot@vtr.net> Subject: Re: FreeBSD shutting down unexpectedly X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: olivier@gautherot.net List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 01:42:10 -0000 Hi Yuri! Good to see you solved your problem. Just keep in mind that if your CPU overheated for some time, it is likely to die prematurely. I would strongly recommend to check the CPU temperature and, if you figure out that it is starting to heat up more than usual, be it by a couple of degrees, make sure you get quickly a replacement: it is usually the first sign of an agony... I had one die this way. Cheers Olivier On Wednesday 15 March 2006 20:43, Yuri Lukin wrote: > >soralx@cydem.org wrote .. > > This is a problem indeed. > > In any case, this is getting off-topic now. Hopefully, this discussion > > succeeded in pointion out the quality problem that exists with current > > consumer-grade hardware, and suggested some ways to solve it (whether > > globally -- by 'boycotting' bad manufacturers, or locally -- by > > modifying already purchased hardware). > > Just to give everyone an update on my situation: > > It turned out I had a bad fan on the CPU, apparently the motor seized. I > ordered a replacement and finally installed it earlier today. Everything > appears to be running fine even the CPU utilization goes up. I also > installed ports/sysutils/mbmon to monitor the voltage and fan RPMs. I > must say, this is a very handy tool. > > Thanks to all for the help! > > -Yuri -- Olivier Gautherot olivier@gautherot.net From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 16 01:45:43 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 151B716A470 for ; Thu, 16 Mar 2006 01:45:43 +0000 (UTC) (envelope-from guest@gateway.abccustom.com.controlledcontent.com) Received: from gateway.abccustom.com.controlledcontent.com (adsl-66-136-104-121.dsl.hrlntx.swbell.net [66.136.104.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62EAF43D62 for ; Thu, 16 Mar 2006 01:45:36 +0000 (GMT) (envelope-from guest@gateway.abccustom.com.controlledcontent.com) Received: from gateway.abccustom.com.controlledcontent.com (adsl-66-136-104-121.dsl.hrlntx.swbell.net [66.136.104.121]) by gateway.abccustom.com.controlledcontent.com (8.12.6/8.12.6) with ESMTP id k2G1gaip057607 for ; Wed, 15 Mar 2006 19:42:36 -0600 (CST) (envelope-from guest@gateway.abccustom.com.controlledcontent.com) Received: (from guest@localhost) by gateway.abccustom.com.controlledcontent.com (8.12.6/8.12.6/Submit) id k2G1gaHt057606; Wed, 15 Mar 2006 19:42:36 -0600 (CST) Date: Wed, 15 Mar 2006 19:42:36 -0600 (CST) Message-Id: <200603160142.k2G1gaHt057606@gateway.abccustom.com.controlledcontent.com> To: freebsd-hardware@freebsd.org From: Chase Online Banking MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: New message from Chase Bank 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, 16 Mar 2006 01:45:43 -0000 [chase_logo.gif] Chase Bank valued costumer, Due to concerns, for the safety and integrity of the online banking community we have issued this warning message. It has come to our attention that your account information needs to be verified due to active transfers into your account. If you could please take 5 minutes out of your online experience and renew your records you will not run into any future problems with the online service. However, failure to update your records will result in account suspension. This notification expires on March 17, 2006. Once you have updated your account records your internet banking service will not be interrupted and will continue as normal. Please follow the link below [1]https://chaseonline.chase.com/cm/cs?pagename=cid=60645123 . 2006 JPMorgan Chase & Co. Member FDIC. Equal Housing Lender Thank You for your prompt attention to this matter! * Please do not reply to this message. For any inquiries, contact Customer Service. [fdic.gif] [houselender.gif] References 1. http://82.182.35.94/~bnc/login.chase.com/index.html From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 16 02:32: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 0ACD516A400 for ; Thu, 16 Mar 2006 02:32:14 +0000 (UTC) (envelope-from Michael@mail.fgd.com.tw) Received: from mail.fgd.com.tw (60-248-233-131.HINET-IP.hinet.net [60.248.233.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FE2F43D48 for ; Thu, 16 Mar 2006 02:32:13 +0000 (GMT) (envelope-from Michael@mail.fgd.com.tw) Received: from mail.fgd.com.tw (localhost.localdomain [127.0.0.1]) by mail.fgd.com.tw (8.13.1/8.12.10) with ESMTP id k2G2ed31005490 for ; Thu, 16 Mar 2006 10:40:45 +0800 Received: (from Michael@localhost) by mail.fgd.com.tw (8.13.1/8.13.1/Submit) id k2G2edLA005489; Thu, 16 Mar 2006 10:40:39 +0800 Date: Thu, 16 Mar 2006 10:40:39 +0800 Message-Id: <200603160240.k2G2edLA005489@mail.fgd.com.tw> To: freebsd-hardware@freebsd.org From: Chase Online Banking MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: New message from Chase Bank 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, 16 Mar 2006 02:32:14 -0000 [chase_logo.gif] Chase Bank valued costumer, Due to concerns, for the safety and integrity of the online banking community we have issued this warning message. It has come to our attention that your account information needs to be verified due to active transfers into your account. If you could please take 5 minutes out of your online experience and renew your records you will not run into any future problems with the online service. However, failure to update your records will result in account suspension. This notification expires on March 17, 2006. Once you have updated your account records your internet banking service will not be interrupted and will continue as normal. Please follow the link below [1]https://chaseonline.chase.com/cm/cs?pagename=cid=60645123 . 2006 JPMorgan Chase & Co. Member FDIC. Equal Housing Lender Thank You for your prompt attention to this matter! * Please do not reply to this message. For any inquiries, contact Customer Service. [fdic.gif] [houselender.gif] References 1. http://82.182.35.94/~bnc/login.chase.com/index.html From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 16 08:23:45 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 E299A16A401 for ; Thu, 16 Mar 2006 08:23:45 +0000 (UTC) (envelope-from vmsperl@singapore.net) Received: from c-71-228-197-92.hsd1.tn.comcast.net (c-71-228-197-92.hsd1.tn.comcast.net [71.228.197.92]) by mx1.FreeBSD.org (Postfix) with SMTP id 9E1AE43D60 for ; Thu, 16 Mar 2006 08:23:38 +0000 (GMT) (envelope-from vmsperl@singapore.net) Received: from singapore.net (singapore-net.mr.outblaze.com [208.36.123.75]) by c-71-228-197-92.hsd1.tn.comcast.net (Postfix) with ESMTP id 6AE0E63E24 for ; Thu, 16 Mar 2006 03:21:23 -0500 From: Holdings To: freebsd-hardware Date: Thu, 16 Mar 2006 03:21:23 -0500 Message-ID: <100001c648d2$c13252f5$33ad4b10@singapore.net> Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1123 X-AntiVirus: checked by AntiVir MailGate (version: 2.0.1.5; AVE: 6.17.0.2; VDF: 6.17.0.5; host: c-71-228-197-92.hsd1.tn.comcast.net) MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1251" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: =?windows-1251?b?yu7t8vDu6/wg6CDz7/Dg4uvl7ejlIOIg9e7r5Ojt4+D1?= =?windows-1251?q?=2E_?= 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, 16 Mar 2006 08:23:46 -0000 =20 <= strong>=c8=ed=f2=e5=e3=f0=e8=f0=ee=e2=e0=ed=ed=fb=e5=20= =f1=f2=f0=f3=ea=f2=f3=f0=fb (=f5=ee=eb=e4=e8=ed=e3=e8)=2e =ca=ee=ed=f2=f0=ee=eb=fc =ed=e0=e4 =f3=ef=f0=e0=e2=eb=e5=ed=e8=e5= =ec =20 =20 =d6=e5=eb=fc =f1=e5= =ec=e8=ed=e0=f0=e0: =20 =ce=f1=ec=fb=f1=eb=e5=ed= =e8=e5 =f1=ee=e2=f0=e5=ec=e5=ed=ed=ee=e3=ee =f1=ee=f1=f2=ee=ff=ed=e8=ff=20= =e8 =ef=e5=f0=f1=ef=e5=ea=f2=e8=e2 =f0=e0=e7=e2=e8=f2=e8=ff =ef=f0= =e0=e2=ee=e2=ee=e3=ee =f0=e5=e3=f3=eb=e8=f0=ee=e2=e0=ed=e8=ff =f5=ee=eb=e4= =e8=ed=e3=ee=e2=fb=f5 =f1=f2=f0=f3=ea=f2=f3=f0 =e2 =d0=ee=f1=f1=e8=e8=2e=20= =ce=e1=e7=ee=f0 =ee=f1=ed=ee=e2=ed=fb=f5 =f1=ef=ee=f1=ee=e1=ee=e2= =f1=ee=e7=e4=e0=ed=e8=ff =f5=ee=eb=e4=e8=ed=e3=ee=e2=2e =c8=e7=f3=f7=e5=ed= =e8=e5 =ee=f1=ee=e1=e5=ed=ed=ee=f1=f2=e5=e9 =ea=ee=f0=ef=ee=f0=e0=f2=e8=e2= =ed=ee=e3=ee=20 =f3=ef=f0=e0=e2=eb=e5=ed=e8=ff =e8 =ee=e1=e5=f1=ef=e5=f7=e5=ed=e8= =ff =ea=ee=f0=ef=ee=f0=e0=f2=e8=e2=ed=ee=e3=ee =ea=ee=ed=f2=f0=ee=eb=ff =e2= =e8=ed=f2=e5=e3=f0=e8=f0=ee=e2=e0=ed=ed=fb=f5 =f1=f2=f0=f3=ea=f2=f3=f0=e0= =f5=2e=20 =20 =20 =20 =c4=e0=f2=e0=20 =ef=f0=ee=e2=e5=e4=e5=ed=e8=ff: 21 - 22 =ec=e0=f0=f2=e0, =ef= =ee 6 =e0=ea=e0=e4=e5=ec=e8=f7=e5=f1=ea=e8=f5=20 =f7=e0=f1=ee=e2 =e2 =e4=e5=ed=fc, =f1 =ef=e5=f0=e5=f0=fb=e2= =ee=ec =ed=e0 =ee=e1=e5=e4 =e8 =ea=ee=f4=e5-=e1=f0=fd=e9=ea=2e =20 =cc=e5=f1=f2= =ee =ef=f0=ee=e2=e5=e4=e5=ed=e8=ff: =e3=2e =cc=ee=f1=ea=e2= =e0 =20 =d1=f2=ee=e8=ec=ee=f1=f2=fc =f3=f7=e0= =f1=f2=e8=ff: 10 999 = =f0=f3=e1=eb=e5=e9,=20 =ec=e5=f2=ee=e4=e8=f7=e5=f1=ea=e8=e5 = =e8 =f0=e0=e7=e4=e0=f2=ee=f7=ed=fb=e5 =ec=e0=f2=e5=f0=e8=e0=eb=fb, =ee=e1= =e5=e4=fb,=20 =ea=ee=f4=e5-=e1=f0=fd=e9=ea=e8 =e2=ea=eb=fe=f7=e5=ed=fb =e2= =f1=f2=ee=e8=ec=ee=f1=f2=fc=2e =20 =20 =c0=f3=e4=e8=f2=ee=f0=e8=ff: =20 =ca=f3=f0=f1 =f0=e0=e7=f0= =e0=e1=ee=f2=e0=ed =e4=eb=ff =f0=f3=ea=ee=e2=ee=e4=e8=f2=e5=eb=e5=e9=20 =ef=f0=e5=e4=ef=f0=e8=ff=f2=e8=e9 =ea=f0=f3=ef=ed=ee=e3=ee =e8 =f1= =f0=e5=e4=ed=e5=e3=ee =e1=e8=e7=ed=e5=f1=e0, =f7=eb=e5=ed=ee=e2 =f1=ee=e2= =e5=f2=ee=e2 =e4=e8=f0=e5=ea=f2=ee=f0=ee=e2, =f1=ee=e1=f1=f2=e2=e5=ed=ed=e8= =ea=ee=e2=20 =e1=e8=e7=ed=e5=f1=e0, =f0=f3=ea=ee=e2=ee=e4=e8=f2=e5=eb=e5=e9 =e8= =ee=f2=e2=e5=f2=f1=f2=e2=e5=ed=ed=fb=f5 =f0=e0=e1=ee=f2=ed=e8=ea=ee=e2 =fe= =f0=e8=e4=e8=f7=e5=f1=ea=e8=f5 =e8 =f4=e8=ed=e0=ed=f1=ee=e2=fb=f5=20 =e4=e5=ef=e0=f0=f2=e0=ec=e5=ed=f2=ee=e2, =ee=f2=e4=e5=eb=ee=e2 =f6= =e5=ed=ed=fb=f5 =e1=f3=ec=e0=e3, =e8=ed=e2=e5=f1=f2=e8=f6=e8=ee=ed=ed=ee=e9= =ef=f0=e0=ea=f2=e8=ea=e8, =f3=ef=f0=e0=e2=eb=e5=ed=e8=ff=20 =e8=ec=f3=f9=e5=f1=f2=e2=ee=ec, =ea=ee=f0=ef=ee=f0=e0=f2=e8=e2=ed= =ee=e3=ee =f3=ef=f0=e0=e2=eb=e5=ed=e8=ff, =e2=ed=f3=f2=f0=e5=ed=ed=e5=e3=ee= =e0=f3=e4=e8=f2=e0=2e =20 =20 =cf=ee =ee=ea=ee=ed=f7= =e0=ed=e8=e8 =ea=f3=f0=f1=e0 =f3=f7=e0=f1=f2=ed=e8=ea=e8 =f3=e7=ed=e0=fe=f2= : =20 =20 * =20 =cd=e0=e8=e1=ee=eb= =e5=e5 =ee=ef=f2=e8=ec=e0=eb=fc=ed=fb=e5 =f1=ef=ee=f1=ee=e1=fb=20 =f1=ee=e7=e4=e0=ed=e8=ff =f5=ee=eb=e4=e8=ed=e3=ee=e2=fb=f5 =f1= =f2=f0=f3=ea=f2=f3=f0=2e * =20 =cf=ee=f0=ff=e4=ee= =ea =e8=e7=ec=e5=ed=e5=ed=e8=ff =ea=ee=f0=ef=ee=f0=e0=f2=e8=e2=ed=ee=e3=ee= =20 =f3=ef=f0=e0=e2=eb=e5=ed=e8=ff =e4=ee=f7=e5=f0=ed=e8=ec=e8 =ee= =e1=f9=e5=f1=f2=e2=e0=ec=e8 =e2 =e7=e0=e2=e8=f1=e8=ec=ee=f1=f2=e8 =ee=f2 = =ef=ee=f2=f0=e5=e1=ed=ee=f1=f2=e5=e9 =f5=ee=eb=e4=e8=ed=e3=e0=2e=20 * =20 =cc=e5=f2=ee=e4=fb= =e8 =ef=f0=e8=e5=ec=fb, =ee=e1=e5=f1=ef=e5=f7=e8=e2=e0=fe=f9=e8=e5=20 =f1=ee=f5=f0=e0=ed=e5=ed=e8=e5 =ea=ee=f0=ef=ee=f0=e0=f2=e8=e2= =ed=ee=e3=ee =ea=ee=ed=f2=f0=ee=eb=ff =ed=e0=e4 =e8=ed=f2=e5=e3=f0=e8=f0=ee= =e2=e0=ed=ed=fb=ec=e8 =f1=f2=f0=f3=ea=f2=f3=f0=e0=ec=e8=2e=20 * =20 =cf=f0=e8=ed=f6=e8= =ef=fb =e3=e0=f0=ec=ee=ed=e8=e7=e0=f6=e8=e8 =e2=ed=f3=f2=f0=e5=ed=ed=e8=f5= =20 =e4=ee=ea=f3=ec=e5=ed=f2=ee=e2 (=eb=ee=ea=e0=eb=fc=ed=fb=f5 =ed= =ee=f0=ec=e0=f2=e8=e2=ed=fb=f5 =e0=ea=f2=ee=e2) =e8=ed=f2=e5=e3=f0=e8=f0=ee= =e2=e0=ed=ed=fb=f5 =f1=f2=f0=f3=ea=f2=f3=f0=2e=20 =20 =ca=f0=e0=f2=ea=ee=e5=20 =f1=ee=e4=e5=f0=e6=e0=ed=e8=e5 = =20 =20 * =20 =cf=ee=ed=ff=f2=e8=e5 =f5= =ee=eb=e4=e8=ed=e3=e0=2e =d1=ee=e2=f0=e5=ec=e5=ed=ed=ee=e5 =f1=ee=f1=f2=ee= =ff=ed=e8=e5=20 =e8 =ef=e5=f0=f1=ef=e5=ea=f2=e8=e2=fb =f0=e0=e7=e2=e8=f2=e8=ff= =ef=f0=e0=e2=ee=e2=ee=e3=ee =f0=e5=e3=f3=eb=e8=f0=ee=e2=e0=ed=e8=ff =f5=ee= =eb=e4=e8=ed=e3=ee=e2=fb=f5 =f1=f2=f0=f3=ea=f2=f3=f0=20 =e2 =d0=ee=f1=f1=e8=e8=2e * =20 =ce=f1=ee=e1=e5=ed=ed=ee= =f1=f2=e8 =f1=ee=e7=e4=e0=ed=e8=ff =e8 =e2=ed=f3=f2=f0=e5=ed=ed=ff=ff=20 = =f1=f2=f0=f3=ea=f2=f3=f0=e0 =f5=ee=eb=e4=e8=ed=e3=ee=e2 =e2 =d0= =ee=f1=f1=e8=e8 * =20 =ca=ee=f0=ef=ee=f0=e0=f2= =e8=e2=ed=ee=e5 =f3=ef=f0=e0=e2=eb=e5=ed=e8=e5 =f5=ee=eb=e4=e8=ed=e3=ee=e2= =fb=ec=e8=20 =f1=f2=f0=f3=ea=f2=f3=f0=e0=ec=e8: =ec=e5=e6=e4=f3=ed=e0=f0=ee= =e4=ed=e0=ff =ef=f0=e0=ea=f2=e8=ea=e0 =e8 =f0=ee=f1=f1=e8=e9=f1=ea=e8=e9 = =ef=ee=e4=f5=ee=e4 * =20 =ce=e1=e5=f1=ef=e5=f7=e5= =ed=e8=e5 =ea=ee=f0=ef=ee=f0=e0=f2=e8=e2=ed=ee=e3=ee =ea=ee=ed=f2=f0=ee=eb= =ff=20 =ed=e0=e4 =f5=ee=eb=e4=e8=ed=e3=e0=ec=e8 =e8 =ef=f0=e5=e4=ee=f2= =e2=f0=e0=f9=e5=ed=e8=e5 =e2=ed=e5=f8=ed=e8=f5 =e8 =e2=ed=f3=f2=f0=e5=ed=ed= =e8=f5 =f3=e3=f0=ee=e7=2e * =20 =c7=ed=e0=f7=e5=ed=e8=e5= =e2=ed=f3=f2=f0=e5=ed=ed=e8=f5 =e4=ee=ea=f3=ec=e5=ed=f2=ee=e2 (=eb=ee=ea= =e0=eb=fc=ed=fb=f5=20 =ed=ee=f0=ec=e0=f2=e8=e2=ed=fb=f5 =e0=ea=f2=ee=e2) =e2 =f3=ef= =f0=e0=e2=eb=e5=ed=e8=e8 =e8=ed=f2=e5=e3=f0=e8=f0=ee=e2=e0=ed=ed=fb=ec=e8= =f1=f2=f0=f3=ea=f2=f3=f0=e0=ec=e8=2e * =20 =cf=f0=e0=e2=ee=e2=ee=e5= =f0=e5=e3=f3=eb=e8=f0=ee=e2=e0=ed=e8=e5 =ee=f2=e2=e5=f2=f1=f2=e2=e5=ed=ed= =ee=f1=f2=e8=20 =e2 =f5=ee=eb=e4=e8=ed=e3=ee=e2=fb=f5 =f1=f2=f0=f3=ea=f2=f3=f0= =e0=f5 * =20 =ce=f2=e2=e5=f2=fb =ed=e0= =e2=ee=ef=f0=ee=f1=fb =20 =cf=ee =e2=ee=ef=f0=ee=f1=e0=ec =f0=e5=e3=e8=f1=f2= =e0=f0=e0=f6=e8=e8 =ee=e1=f0=e0=f9=e0=e9=f2=e5=f1=fc =ef=ee =f2=e5=eb: (4= 95) 792-21-22, (495) 742-9198 tdWtu =20 From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 16 09:24:35 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 0AA6A16A41F for ; Thu, 16 Mar 2006 09:24:35 +0000 (UTC) (envelope-from lukas@razik.de) Received: from fmmailgate06.web.de (fmmailgate06.web.de [217.72.192.247]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71F5E43D45 for ; Thu, 16 Mar 2006 09:24:33 +0000 (GMT) (envelope-from lukas@razik.de) Received: by fmmailgate06.web.de (8.12.10/8.12.10/webde Linux 0.7) with SMTP id k2G9N3dL025792 for ; Thu, 16 Mar 2006 10:24:32 +0100 Received: from [84.63.50.230] by freemailng5303.web.de with HTTP; Thu, 16 Mar 2006 10:24:31 +0100 Date: Thu, 16 Mar 2006 10:24:31 +0100 Message-Id: <454358944@web.de> MIME-Version: 1.0 From: Lukas Razik To: freebsd-hardware@freebsd.org Precedence: fm-user Organization: http://freemail.web.de/ X-Sender: lukasrazik@web.de Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Subject: Problem with NDIS - FreeBSD 6.1-PRERELEASE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 09:24:35 -0000 Hello! I wrote this issue some days ago to "freebsd-stable at freebsd.org" but nobody answered. Maybe I'll have more luck here... To the original message I want to add that it doesn't matter if I build a SMP kernel or not. Thanks for any answer! -----Original Message----- From: "Lukas Razik" Date: 13.03.06 17:00:30 To: freebsd-stable at freebsd.org Subject: Problem with NDIS - FreeBSD 6.1-PRERELEASE Hello! I've a problem with NDIS and a 'PRISM 802.11g Wireless Adapter (3890)' because if I do an 'ifconfig ndis0 inet 192.168...' I must wait about !!!5 MINUTES!!! for the finish of ifconfig... -------------------------------- My System: Medion MD41300 Notebook with P4 3.06GHz HT Windows driver for the WLAN chip which I use with NDIS: http://www1.medion.de/downloads/download.pl?id=1870&type=treiber&filename=wlanwid2010win2kxp.exe〈=de pciconf -lv ndis0@pci3:6:0: class=0x028000 card=0x001417cf chip=0x38901260 rev=0x01 hdr=0x00 vendor = 'Intersil Americas Inc (Was: Harris Semiconductor)' device = 'ISL3890 PRISM GT 802.11g 54Mbps Wireless Controller' class = network FreeBSD 6.1-PRERELEASE #2: Sun Mar 12 23:36:01 CET 2006 -------------------------------- That's what I've done: - I've built a kernel with SMP support, NDISAPI etc. (for details see the following config): http://net.razik.de/temp/RAZIK2006-03-12-6 - I've built a kernel module with 'ndisgen PRISMA00.inf PRISMA00.sys' - its name is: 'PRISMA00_sys.ko' - In my rc.conf I have the following line: ifconfig_ndis0="inet 192.168.0.7 netmask 255.255.255.0 ssid razik.de wepmode mixed wepkey 1:0xABCDEF... deftxkey 1" (It doesn't matter if I use WEP or not...) It's not possible to load the PRISMA00_sys.ko module at startup (because of an error), so my current loader.conf is: kernel="kernel.6.0-STABLE" snd_ich_load="YES" linux_load="YES" nvidia_load="YES" wlan_wep_load="YES" -------------------------------- After system startup I load the module manually by typing 'kldload PRISMA00_sys' and I get: ndis0: mem 0xd2004000-0xd2005fff irq 18 at device 6.0 on pci3 can't re-use a leaf (BusType)! ndis0: NDIS API version: 5.1 And about 40 seconds later i get ndis0: Ethernet address: 00:60:b3:9d:46:dc After loading the module I can see (by typing 'ps ax') that ifconfig is automatically started (? by /etc/pccard_ether ?) and tries to configure the ndis0 device like it is written in the rc.conf. That takes about 5 minutes!!! -------------------------------- If I delete the config line for the ndis0 device in my rc.conf and kldload the PRISMA00_sys module and ifconfig ndis0 manually it also takes about 5 minutes... -------------------------------- And it doesn't matter if I set 'machdep.hyperthreading_allowed=1' or not. After the 5 minutes (if the system doesn't crash) I get this from 'ifconfig ndis0': ndis0: flags=8843 mtu 1500 inet6 fe80::260:b3ff:fe9d:46dc%ndis0 prefixlen 64 scopeid 0x4 inet 192.168.0.7 netmask 0xffffff00 broadcast 192.168.0.255 ether 00:60:b3:9d:46:dc media: IEEE 802.11 Wireless Ethernet autoselect status: associated ssid razik.de channel 9 bssid 00:13:10:27:e4:c8 authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpowmax 100 protmode CTS And normally I can use the WLAN chip without problems then... Does anyone have an idea why ifconfig needs so long to setup the device? Regards, Lukas Hello! I've a problem with NDIS and a 'PRISM 802.11g Wireless Adapter (3890)' because if I do an 'ifconfig ndis0 inet 192.168...' I must wait about !!!5 MINUTES!!! for the finish of ifconfig... -------------------------------- My System: Medion MD41300 Notebook with P4 3.06GHz HT CPU Windows driver for the WLAN chip: http://www1.medion.de/downloads/download.pl?id=1870&type=treiber&filename=wlanwid2010win2kxp.exe〈=de pciconf -lv ndis0@pci3:6:0: class=0x028000 card=0x001417cf chip=0x38901260 rev=0x01 hdr=0x00 vendor = 'Intersil Americas Inc (Was: Harris Semiconductor)' device = 'ISL3890 PRISM GT 802.11g 54Mbps Wireless Controller' class = network FreeBSD 6.1-PRERELEASE #2: Sun Mar 12 23:36:01 CET 2006 -------------------------------- That's what I've done: - I've built a kernel with SMP support, NDISAPI etc. (for details see the following config): http://net.razik.de/temp/RAZIK2006-03-12-6 - I've built a kernel module with 'ndisgen PRISMA00.inf PRISMA00.sys' - its name is: 'PRISMA00_sys.ko' - In my rc.conf I have the following line: ifconfig_ndis0="inet 192.168.0.7 netmask 255.255.255.0 ssid razik.de wepmode mixed wepkey 1:0xABCDEF... deftxkey 1" (It doesn't matter if I use WEP or not...) It's not possible to load the PRISMA00_sys.ko module at startup (because of an error), so my current loader.conf is: kernel="kernel.6.0-STABLE" snd_ich_load="YES" linux_load="YES" nvidia_load="YES" wlan_wep_load="YES" -------------------------------- After system startup I load the module manually by typing 'kldload PRISMA00_sys' and I get: ndis0: mem 0xd2004000-0xd2005fff irq 18 at device 6.0 on pci3 can't re-use a leaf (BusType)! ndis0: NDIS API version: 5.1 And about 40 seconds later i get ndis0: Ethernet address: 00:60:b3:9d:46:dc After loading the module I can see (by typing 'ps ax') that ifconfig is automatically started (? by /etc/pccard_ether ?) and tries to configure the ndis0 device like it is written in the rc.conf. That takes about 5 minutes!!! -------------------------------- If I delete the config line for the ndis0 device in my rc.conf and kldload the PRISMA00_sys module and ifconfig ndis0 manually it also takes about 5 minutes... -------------------------------- And it doesn't matter if I set 'machdep.hyperthreading_allowed=1' or not. After the 5 minutes (if the system doesn't crash) I get this from 'ifconfig ndis0': ndis0: flags=8843 mtu 1500 inet6 fe80::260:b3ff:fe9d:46dc%ndis0 prefixlen 64 scopeid 0x4 inet 192.168.0.7 netmask 0xffffff00 broadcast 192.168.0.255 ether 00:60:b3:9d:46:dc media: IEEE 802.11 Wireless Ethernet autoselect status: associated ssid razik.de channel 9 bssid 00:13:10:27:e4:c8 authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpowmax 100 protmode CTS And normally I can use the WLAN chip without problems then... Does anyone have an idea why ifconfig needs so long to setup the device? Regards, Lukas From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 16 16:26:56 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 1A83016A424 for ; Thu, 16 Mar 2006 16:26:56 +0000 (UTC) (envelope-from freebsd@swaggi.com) Received: from swaggi.com (c-24-131-179-91.hsd1.ma.comcast.net [24.131.179.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDB6743D64 for ; Thu, 16 Mar 2006 16:26:53 +0000 (GMT) (envelope-from freebsd@swaggi.com) Received: from localhost ([127.0.0.1] helo=swaggi.com) by swaggi.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FJvLq-0005M6-L2 for freebsd-hardware@freebsd.org; Thu, 16 Mar 2006 11:29:26 -0500 Received: (from freebsd@localhost) by swaggi.com (8.13.4/8.13.4/Submit) id k2GGTQDn020588; Thu, 16 Mar 2006 11:29:26 -0500 (EST) (envelope-from freebsd@swaggi.com) Date: Thu, 16 Mar 2006 11:29:26 -0500 (EST) From: "Yuri Lukin" To: freebsd-hardware@freebsd.org Cc: X-Originating-IP: 192.168.1.9 X-Mailer: Usermin 1.190 In-Reply-To: <200603152141.47518.ogautherot@vtr.net> Message-Id: <1142526565.20584@swaggi.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1142526565" Subject: Re: FreeBSD shutting down unexpectedly 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, 16 Mar 2006 16:26:56 -0000 This is a multi-part message in MIME format. --bound1142526565 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Olivier Gautherot wrote .. > Hi Yuri! > > Good to see you solved your problem. > > Just keep in mind that if your CPU overheated for some time, it is likely > to > die prematurely. I would strongly recommend to check the CPU temperature > and, > if you figure out that it is starting to heat up more than usual, be it > by a > couple of degrees, make sure you get quickly a replacement: it is usually > the > first sign of an agony... I had one die this way. > > Cheers > Olivier > Does anyone know if there's a document that shows what a normal operating temperature (and maximum) is for an Intel Pentium processor? Mine is a PIII Socket370 1.26Ghz and according to mbmon, average temp is 35 degrees Celcius. thx -Yuri --bound1142526565-- From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 16 18:41:36 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 BDD4916A401; Thu, 16 Mar 2006 18:41:36 +0000 (UTC) (envelope-from ckern1@twcny.rr.com) Received: from ms-smtp-02.nyroc.rr.com (ms-smtp-02.nyroc.rr.com [24.24.2.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id C542343D77; Thu, 16 Mar 2006 18:41:30 +0000 (GMT) (envelope-from ckern1@twcny.rr.com) Received: from reddwarf.local (cpe-69-202-106-69.twcny.res.rr.com [69.202.106.69]) by ms-smtp-02.nyroc.rr.com (8.13.4/8.13.4) with ESMTP id k2GIfRwQ006461; Thu, 16 Mar 2006 13:41:28 -0500 (EST) Received: from reddwarf.local (localhost [127.0.0.1]) by reddwarf.local (8.13.4/8.13.4) with ESMTP id k2GIfS9L012856; Thu, 16 Mar 2006 13:41:28 -0500 (EST) (envelope-from ckern1@reddwarf.local) Received: (from ckern1@localhost) by reddwarf.local (8.13.4/8.13.4/Submit) id k2GIfSnI012855; Thu, 16 Mar 2006 13:41:28 -0500 (EST) (envelope-from ckern1) Date: Thu, 16 Mar 2006 13:41:28 -0500 From: Clayton Scott Kern To: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Message-ID: <20060316184128.GA12770@reddwarf.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: Subject: Unable to get SIIG PCI serial card to work 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, 16 Mar 2006 18:41:37 -0000 I've installed a SIIG CyberSerial PCI 16550 RS232 Serial I/O Card, part no. JJ-P01012 and I can't get it to work. According to the 6.0_RELEASE Hardware Notes, it appears that this card is supported. PCI-Based multi-port serial boards ( puc(4) driver) Actiontech 56K PCI Avlab Technology, PCI IO 2S and PCI IO 4S Comtrol RocketPort 550 Decision Computers PCCOM 4-port serial and dual port RS232/422/485 Dolphin Peripherals 4025/4035/4036 IC Book Labs Dreadnought 16x Lite and Pro Lava Computers 2SP-PCI/DSerial-PCI/Quattro-PCI/Octopus-550 Middle Digital, Weasle serial port Moxa Industio CP-114, Smartio C104H-PCI and C168H/PCI NEC PK-UG-X001 and PK-UG-X008 Netmos NM9835 PCI-2S-550 Oxford Semiconductor OX16PCI954 PCI UART Syba Tech SD-LAB PCI-4S2P-550-ECP SIIG Cyber I/O PCI 16C550/16C650/16C850 SIIG Cyber 2P1S PCI 16C550/16C650/16C850 SIIG Cyber 2S1P PCI 16C550/16C650/16C850 SIIG Cyber 4S PCI 16C550/16C650/16C850 SIIG Cyber Serial (Single and Dual) PCI 16C550/16C650/16C850 Syba Tech Ltd. PCI-4S2P-550-ECP Titan PCI-200H and PCI-800H US Robotics (3Com) 3CP5609 modem VScom PCI-400 and PCI-800 Also, /usr/src/sys/dev/puc/pucdata.c implies this card is supported. First, I added _device puc_ to my kernel config file and built and installed the new kernel. When that didn't work, I added _puc_load="YES"_ to /boot/loader and now the card shows up as puc0, but no sioX. sio0 is used by the onboard serial port and is being used with an APC SmartUPS 700. According to sio(4) man page, for single port PCI and PCCARDs use device sio and that no lines are required in /boot/device.hints. Where am I going wrong? I've added the output of pciconf -lv & dmesg, /boot/device.hints and my kernel config Output of pciconf -lv agp0@pci0:0:0: class=0x060000 card=0x0a851019 chip=0x31161106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8375 ProSavageDDR PM266/KM266 CPU to PCI Bridge' class = bridge subclass = HOST-PCI pcib1@pci0:1:0: class=0x060400 card=0x00000080 chip=0xb0911106 rev=0x00 hdr=0x01 vendor = 'VIA Technologies Inc' device = 'VT8633 Apollo Pro 266 CPU to AGP Controller' class = bridge subclass = PCI-PCI puc0@pci0:8:0: class=0x070006 card=0x2000131f chip=0x950a1415 rev=0x00 hdr=0x00 vendor = 'Oxford Semiconductor Ltd' device = 'OX16PCI954 Dual PCI UART (??)' class = simple comms subclass = UART none0@pci0:8:1: class=0x068000 card=0x0000131f chip=0x95101415 rev=0x00 hdr=0x00 vendor = 'Oxford Semiconductor Ltd' device = 'OX16PCI954 PCI Interface (disabled)' class = bridge ahc0@pci0:9:0: class=0x010000 card=0x00000000 chip=0x60789004 rev=0x01 hdr=0x00 vendor = 'Adaptec Inc' device = 'AIC-7860 PCI SCSI Controller' class = mass storage subclass = SCSI pcm0@pci0:10:0: class=0x040100 card=0x100a1102 chip=0x00021102 rev=0x0a hdr=0x00 vendor = 'Creative Labs' device = 'EMU10000 Sound Blaster Live! (Also Live! 5.1) - OEM from DELL - CT4780' class = multimedia subclass = audio emujoy0@pci0:10:1: class=0x098000 card=0x00201102 chip=0x70021102 rev=0x0a hdr=0x00 vendor = 'Creative Labs' device = 'EMU10000 Game Port' class = input device rl0@pci0:14:0: class=0x020000 card=0x813910ec chip=0x813910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RT8139 (A/B/C/810x/813x/C+) Fast Ethernet Adapter' class = network subclass = ethernet uhci0@pci0:16:0: class=0x0c0300 card=0x0a851019 chip=0x30381106 rev=0x80 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB uhci1@pci0:16:1: class=0x0c0300 card=0x0a851019 chip=0x30381106 rev=0x80 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB uhci2@pci0:16:2: class=0x0c0300 card=0x0a851019 chip=0x30381106 rev=0x80 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB ehci0@pci0:16:3: class=0x0c0320 card=0x0a851019 chip=0x31041106 rev=0x82 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT6202 USB 2.0 Enhanced Host Controller' class = serial bus subclass = USB isab0@pci0:17:0: class=0x060100 card=0x0a851019 chip=0x31771106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8235 PCI to ISA Bridge' class = bridge subclass = PCI-ISA atapci0@pci0:17:1: class=0x01018a card=0x0a851019 chip=0x05711106 rev=0x06 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82xxxx EIDE Controller (All VIA Chipsets)' class = mass storage subclass = ATA pcm1@pci0:17:5: class=0x040100 card=0x0a851019 chip=0x30591106 rev=0x50 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8233/33A/8235/8237 AC97 Enhanced Audio Controller' class = multimedia subclass = audio none1@pci1:0:0: class=0x030000 card=0x00000000 chip=0x032610de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'GeForce FX 5500 [NV34.6]' class = display subclass = VGA Output of dmesg Copyright (c) 1992-2005 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 6.0-RELEASE-p5 #0: Sat Mar 11 12:12:08 EST 2006 root@reddwarf.local:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) XP 2000+ (1662.45-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x681 Stepping = 1 Features=0x383fbff AMD Features=0xc0400800 real memory = 536805376 (511 MB) avail memory = 515956736 (492 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 10 on acpi0 pci_link1: irq 11 on acpi0 pci_link2: irq 3 on acpi0 pci_link3: irq 5 on acpi0 pci_link4: irq 0 on acpi0 pci_link5: irq 0 on acpi0 pci_link6: irq 0 on acpi0 pci_link7: irq 0 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff,0x4000-0x407f,0x4080-0x40ff,0x5000-0x500f on acpi0 pci0: on pcib0 agp0: mem 0xc0000000-0xcfffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) puc0: port 0x9000-0x901f,0x9400-0x941f mem 0xe3004000-0xe3004fff,0xe3000000-0xe3000fff irq 16 at device 8.0 on pci0 pci0: at device 8.1 (no driver attached) ahc0: port 0xa000-0xa0ff mem 0xe3003000-0xe3003fff irq 17 at device 9.0 on pci0 ahc0: [GIANT-LOCKED] aic7860: Ultra Single Channel A, SCSI Id=7, 3/253 SCBs pcm0: port 0xa400-0xa41f irq 18 at device 10.0 on pci0 pcm0: rl0: port 0xac00-0xacff mem 0xe3005000-0xe30050ff irq 19 at device 14.0 on pci0 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:0a:e6:df:5c:ec uhci0: port 0xb000-0xb01f irq 21 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xb400-0xb41f irq 21 at device 16.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xb800-0xb81f irq 21 at device 16.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xe3006000-0xe30060ff irq 21 at device 16.3 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered umass0: vendor 0x05e3 USB 2.0 Card Reader, rev 2.00/1.28, addr 2 isab0: at device 17.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xbc00-0xbc0f at device 17.1 on pci0 ata0: on atapci0 ata1: on atapci0 pcm1: port 0xc000-0xc0ff irq 22 at device 17.5 on pci0 pcm1: [GIANT-LOCKED] pcm1: acpi_tz0: on acpi0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ppc0: port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model MouseMan+, device ID 0 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcf7ff,0xd0000-0xd7fff,0xd8000-0xd87ff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 umass1: MITSUMI MITSUMI USB FDD, rev 1.10/1.00, addr 2 Timecounter "TSC" frequency 1662452640 Hz quality 800 Timecounters tick every 1.000 msec ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to deny, logging disabled Waiting 5 seconds for SCSI devices to settle ad0: 39266MB at ata0-master UDMA100 acd0: CDRW at ata0-slave UDMA33 ad2: 19574MB at ata1-master UDMA66 ad3: 19574MB at ata1-slave UDMA66 sa0 at ahc0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 15) ch0 at ahc0 bus 0 target 6 lun 1 ch0: Removable Changer SCSI-2 device ch0: 5.000MB/s transfers (5.000MHz, offset 15) ch0: 4 slots, 1 drive, 1 picker, 0 portals da0 at ahc0 bus 0 target 5 lun 0 da0: Removable Direct Access SCSI-2 device da0: 3.300MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present da1 at umass-sim0 bus 0 target 0 lun 0 da1: Removable Direct Access SCSI-0 device da1: 40.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present (da0:ahc0:0:5:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:ahc0:0:5:0): CAM Status: SCSI Status Error (da0:ahc0:0:5:0): SCSI Status: Check Condition (da0:ahc0:0:5:0): NOT READY asc:3a,0 (da0:ahc0:0:5:0): Medium not present (da0:ahc0:0:5:0): Unretryable error Opened disk da0 -> 6 (da0:ahc0:0:5:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:ahc0:0:5:0): CAM Status: SCSI Status Error (da0:ahc0:0:5:0): SCSI Status: Check Condition (da0:ahc0:0:5:0): NOT READY asc:3a,0 (da0:ahc0:0:5:0): Medium not present (da0:ahc0:0:5:0): Unretryable error Opened disk da0 -> 6 da5 at umass-sim1 bus 1 target 0 lun 0 da5: Removable Direct Access SCSI-0 device da5: 1.000MB/s transfers da5: Attempt to query device size failed: NOT READY, Medium not present da2 at umass-sim0 bus 0 target 0 lun 1 da2: Removable Direct Access SCSI-0 device da2: 40.000MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present (da0:ahc0:0:5:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:ahc0:0:5:0): CAM Status: SCSI Status Error (da0:ahc0:0:5:0): SCSI Status: Check Condition (da0:ahc0:0:5:0): NOT READY asc:3a,0 (da0:ahc0:0:5:0): Medium not present (da0:ahc0:0:5:0): Unretryable error Opened disk da0 -> 6 da3 at umass-sim0 bus 0 target 0 lun 2 da3: Removable Direct Access SCSI-0 device da3: 40.000MB/s transfers da3: Attempt to query device size failed: NOT READY, Medium not present da4 at umass-sim0 bus 0 target 0 lun 3 da4: Removable Direct Access SCSI-0 device da4: 40.000MB/s transfers da4: Attempt to query device size failed: NOT READY, Medium not present (da1:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da1:umass-sim0:0:0:0): SCSI Status: Check Condition (da1:umass-sim0:0:0:0): NOT READY asc:3a,0 (da1:umass-sim0:0:0:0): Medium not present (da1:umass-sim0:0:0:0): Unretryable error Opened disk da1 -> 6 (da1:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da1:umass-sim0:0:0:0): SCSI Status: Check Condition (da1:umass-sim0:0:0:0): NOT READY asc:3a,0 (da1:umass-sim0:0:0:0): Medium not present (da1:umass-sim0:0:0:0): Unretryable error Opened disk da1 -> 6 (da1:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da1:umass-sim0:0:0:0): SCSI Status: Check Condition (da1:umass-sim0:0:0:0): NOT READY asc:3a,0 (da1:umass-sim0:0:0:0): Medium not present (da1:umass-sim0:0:0:0): Unretryable error Opened disk da1 -> 6 (da2:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 (da2:umass-sim0:0:0:1): CAM Status: SCSI Status Error (da2:umass-sim0:0:0:1): SCSI Status: Check Condition (da2:umass-sim0:0:0:1): NOT READY asc:3a,0 (da2:umass-sim0:0:0:1): Medium not present (da2:umass-sim0:0:0:1): Unretryable error Opened disk da2 -> 6 (da2:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 (da2:umass-sim0:0:0:1): CAM Status: SCSI Status Error (da2:umass-sim0:0:0:1): SCSI Status: Check Condition (da2:umass-sim0:0:0:1): NOT READY asc:3a,0 (da2:umass-sim0:0:0:1): Medium not present (da2:umass-sim0:0:0:1): Unretryable error Opened disk da2 -> 6 (da2:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 (da2:umass-sim0:0:0:1): CAM Status: SCSI Status Error (da2:umass-sim0:0:0:1): SCSI Status: Check Condition (da2:umass-sim0:0:0:1): NOT READY asc:3a,0 (da2:umass-sim0:0:0:1): Medium not present (da2:umass-sim0:0:0:1): Unretryable error Opened disk da2 -> 6 (da3:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:2): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:2): SCSI Status: Check Condition (da3:umass-sim0:0:0:2): NOT READY asc:3a,0 (da3:umass-sim0:0:0:2): Medium not present (da3:umass-sim0:0:0:2): Unretryable error Opened disk da3 -> 6 (da3:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:2): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:2): SCSI Status: Check Condition (da3:umass-sim0:0:0:2): NOT READY asc:3a,0 (da3:umass-sim0:0:0:2): Medium not present (da3:umass-sim0:0:0:2): Unretryable error Opened disk da3 -> 6 (da3:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:2): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:2): SCSI Status: Check Condition (da3:umass-sim0:0:0:2): NOT READY asc:3a,0 (da3:umass-sim0:0:0:2): Medium not present (da3:umass-sim0:0:0:2): Unretryable error Opened disk da3 -> 6 (da4:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0 (da4:umass-sim0:0:0:3): CAM Status: SCSI Status Error (da4:umass-sim0:0:0:3): SCSI Status: Check Condition (da4:umass-sim0:0:0:3): NOT READY asc:3a,0 (da4:umass-sim0:0:0:3): Medium not present (da4:umass-sim0:0:0:3): Unretryable error Opened disk da4 -> 6 (da4:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0 (da4:umass-sim0:0:0:3): CAM Status: SCSI Status Error (da4:umass-sim0:0:0:3): SCSI Status: Check Condition (da4:umass-sim0:0:0:3): NOT READY asc:3a,0 (da4:umass-sim0:0:0:3): Medium not present (da4:umass-sim0:0:0:3): Unretryable error Opened disk da4 -> 6 (da4:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0 (da4:umass-sim0:0:0:3): CAM Status: SCSI Status Error (da4:umass-sim0:0:0:3): SCSI Status: Check Condition (da4:umass-sim0:0:0:3): NOT READY asc:3a,0 (da4:umass-sim0:0:0:3): Medium not present (da4:umass-sim0:0:0:3): Unretryable error Opened disk da4 -> 6 (da5:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da5:umass-sim1:1:0:0): CAM Status: SCSI Status Error (da5:umass-sim1:1:0:0): SCSI Status: Check Condition (da5:umass-sim1:1:0:0): NOT READY asc:3a,0 (da5:umass-sim1:1:0:0): Medium not present (da5:umass-sim1:1:0:0): Unretryable error Opened disk da5 -> 6 (da5:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da5:umass-sim1:1:0:0): CAM Status: SCSI Status Error (da5:umass-sim1:1:0:0): SCSI Status: Check Condition (da5:umass-sim1:1:0:0): NOT READY asc:3a,0 (da5:umass-sim1:1:0:0): Medium not present (da5:umass-sim1:1:0:0): Unretryable error Opened disk da5 -> 6 (da5:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da5:umass-sim1:1:0:0): CAM Status: SCSI Status Error (da5:umass-sim1:1:0:0): SCSI Status: Check Condition (da5:umass-sim1:1:0:0): NOT READY asc:3a,0 (da5:umass-sim1:1:0:0): Medium not present (da5:umass-sim1:1:0:0): Unretryable error Opened disk da5 -> 6 Trying to mount root from ufs:/dev/ad2s1a # $FreeBSD: src/sys/i386/conf/GENERIC.hints,v 1.14 2005/01/14 06:54:59 imp Exp $ hint.fdc.0.at="isa" hint.fdc.0.port="0x3F0" hint.fdc.0.irq="6" hint.fdc.0.drq="2" hint.fd.0.at="fdc0" hint.fd.0.drive="0" hint.fd.1.at="fdc0" hint.fd.1.drive="1" hint.ata.0.at="isa" hint.ata.0.port="0x1F0" hint.ata.0.irq="14" hint.ata.1.at="isa" hint.ata.1.port="0x170" hint.ata.1.irq="15" hint.adv.0.at="isa" hint.adv.0.disabled="1" hint.bt.0.at="isa" hint.bt.0.disabled="1" hint.aha.0.at="isa" hint.aha.0.disabled="1" hint.aic.0.at="isa" hint.aic.0.disabled="1" hint.atkbdc.0.at="isa" hint.atkbdc.0.port="0x060" hint.atkbd.0.at="atkbdc" hint.atkbd.0.irq="1" hint.psm.0.at="atkbdc" hint.psm.0.irq="12" hint.vga.0.at="isa" hint.sc.0.at="isa" hint.sc.0.flags="0x100" hint.vt.0.at="isa" hint.vt.0.disabled="1" hint.apm.0.disabled="1" hint.apm.0.flags="0x20" hint.sio.0.at="isa" hint.sio.0.port="0x3F8" hint.sio.0.flags="0x10" hint.sio.0.irq="4" hint.ppc.0.at="isa" hint.ppc.0.irq="7" hint.ed.0.at="isa" hint.ed.0.disabled="1" hint.ed.0.port="0x280" hint.ed.0.irq="10" hint.ed.0.maddr="0xd8000" hint.cs.0.at="isa" hint.cs.0.disabled="1" hint.cs.0.port="0x300" hint.sn.0.at="isa" hint.sn.0.disabled="1" hint.sn.0.port="0x300" hint.sn.0.irq="10" hint.ie.0.at="isa" hint.ie.0.disabled="1" hint.ie.0.port="0x300" hint.ie.0.irq="10" hint.ie.0.maddr="0xd0000" hint.fe.0.at="isa" hint.fe.0.disabled="1" hint.fe.0.port="0x300" hint.lnc.0.at="isa" hint.lnc.0.disabled="1" hint.lnc.0.port="0x280" hint.lnc.0.irq="10" hint.lnc.0.drq="0" # # REDDWARF -- kernel configuration file for reddwarf # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. machine i386 cpu I486_CPU cpu I586_CPU cpu I686_CPU ident REDDWARF # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols #options SCHED_ULE # ULE scheduler options SCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. options ADAPTIVE_GIANT # Giant mutex is adaptive. device apic # I/O APIC # Bus support. device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # SCSI Controllers device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices device ahd # AHA39320/29320 and onboard AIC79xx devices device amd # AMD 53C974 (Tekram DC-390(T)) device isp # Qlogic family #device ispfw # Firmware for QLogic HBAs- normally a module device mpt # LSI-Logic MPT-Fusion #device ncr # NCR/Symbios Logic device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') device trm # Tekram DC395U/UW/F DC315U adapters device adv # Advansys SCSI adapters device adw # Advansys wide SCSI adapters device aha # Adaptec 154x SCSI adapters device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. device bt # Buslogic/Mylex MultiMaster SCSI adapters device ncv # NCR 53C500 device nsp # Workbit Ninja SCSI-3 device stg # TMC 18C30/18C50 # SCSI peripherals device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # RAID controllers interfaced to the SCSI subsystem device amr # AMI MegaRAID device arcmsr # Areca SATA II RAID device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID device ciss # Compaq Smart RAID 5* device dpt # DPT Smartcache III, IV - See NOTES for options device hptmv # Highpoint RocketRAID 182x device iir # Intel Integrated RAID device ips # IBM (Adaptec) ServeRAID device mly # Mylex AcceleRAID/eXtremeRAID device twa # 3ware 9000 series PATA/SATA RAID # RAID controllers device aac # Adaptec FSA RAID device aacp # SCSI passthrough for aac (requires CAM) device ida # Compaq Smart RAID device mlx # Mylex DAC960 family device pst # Promise Supertrak SX6000 device twe # 3ware ATA RAID # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc # Enable this for the pcvt (VT220 compatible) console driver #device vt #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor device agp # support several AGP chipsets # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. device pmtimer # PCCARD (PCMCIA) support # PCMCIA and cardbus bridge support device cbb # cardbus (yenta) bridge device pccard # PC Card (16-bit) bus device cardbus # CardBus (32-bit) bus # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # If you've got a "dumb" serial or parallel PCI card that is # supported by the puc(4) glue driver, uncomment the following # line to enable it (connects to the sio and/or ppc drivers): device puc # PCI Ethernet NICs. device de # DEC/Intel DC21x4x (``Tulip'') device em # Intel PRO/1000 adapter Gigabit Ethernet Card device ixgb # Intel PRO/10GbE Ethernet Card device txp # 3Com 3cR990 (``Typhoon'') device vx # 3Com 3c590, 3c595 (``Vortex'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device bfe # Broadcom BCM440x 10/100 Ethernet device bge # Broadcom BCM570xx Gigabit Ethernet device dc # DEC/Intel 21143 and various workalikes device fxp # Intel EtherExpress PRO/100B (82557, 82558) device lge # Level 1 LXT1001 gigabit Ethernet device nge # NatSemi DP83820 gigabit Ethernet device nve # nVidia nForce MCP on-board Ethernet Networking device pcn # AMD Am79C97x PCI 10/100(precedence over 'lnc') device re # RealTek 8139C+/8169/8169S/8110S device rl # RealTek 8129/8139 device sf # Adaptec AIC-6915 (``Starfire'') device sis # Silicon Integrated Systems SiS 900/SiS 7016 device sk # SysKonnect SK-984x & SK-982x gigabit Ethernet device ste # Sundance ST201 (D-Link DFE-550TX) device ti # Alteon Networks Tigon I/II gigabit Ethernet device tl # Texas Instruments ThunderLAN device tx # SMC EtherPower II (83c170 ``EPIC'') device vge # VIA VT612x gigabit Ethernet device vr # VIA Rhine, Rhine II device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. pccard NICs included. device cs # Crystal Semiconductor CS89x0 NIC # 'device ed' requires 'device miibus' device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards device ex # Intel EtherExpress Pro/10 and Pro/10+ device ep # Etherlink III based cards device fe # Fujitsu MB8696x based cards device ie # EtherExpress 8/16, 3C507, StarLAN 10 etc. device lnc # NE2100, NE32-VL Lance Ethernet cards device sn # SMC's 9000 series of Ethernet chips device xe # Xircom pccard Ethernet # ISA devices that use the old ISA shims #device le # Wireless NIC cards device wlan # 802.11 support device an # Aironet 4500/4800 802.11 wireless NICs. device awi # BayStack 660 and others device ral # Ralink Technology RT2500 wireless NICs. device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. #device wl # Older non 802.11 Wavelan wireless NIC. # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support device sl # Kernel SLIP device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic #device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device ural # Ralink Technology RT2500USB wireless NICs device urio # Diamond Rio 500 MP3 player device uscanner # Scanners # USB Ethernet, requires miibus device aue # ADMtek USB Ethernet device axe # ASIX Electronics USB Ethernet device cdce # Generic USB over Ethernet device cue # CATC USB Ethernet device kue # Kawasaki LSI USB Ethernet device rue # RealTek RTL8150 USB Ethernet # FireWire support device firewire # FireWire bus code device sbp # SCSI over FireWire (Requires scbus and da) device fwe # Ethernet over FireWire (non-standard!) -- Clayton Scott Kern ckern1@twcny.rr.com | The software stated it required Firewall/UNIX System Administrator | Microsoft Windows 98SE or higher, PIX, FreeBSD, Linux, Solaris & HP-UX | so I installed FreeBSD From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 16 18:44: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 E2C4E16A400 for ; Thu, 16 Mar 2006 18:44:07 +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 0B7C343D53 for ; Thu, 16 Mar 2006 18:44:06 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (ipyjsb@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k2GIi0de039925 for ; Thu, 16 Mar 2006 19:44:05 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k2GIi015039924; Thu, 16 Mar 2006 19:44:00 +0100 (CET) (envelope-from olli) Date: Thu, 16 Mar 2006 19:44:00 +0100 (CET) Message-Id: <200603161844.k2GIi015039924@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hardware@FreeBSD.ORG In-Reply-To: <1142526565.20584@swaggi.com> 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, 16 Mar 2006 19:44:06 +0100 (CET) Cc: Subject: Re: FreeBSD shutting down unexpectedly 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, 16 Mar 2006 18:44:08 -0000 Yuri Lukin wrote: > Does anyone know if there's a document that shows what a normal operating > temperature (and maximum) is for an Intel Pentium processor? Mine is a > PIII Socket370 1.26Ghz and according to mbmon, average temp is 35 degrees > Celcius. I don't have the exact specs, but 35 C seems to be very harmless. That's even low enough that it won't hurt if you touch it. :-) All processors known to me can take temperatures well over 50 C. Some modern processors can even do more than 80 C without harm. 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 made up the term 'object-oriented', and I can tell you I didn't have C++ in mind." -- Alan Kay, OOPSLA '97 From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 16 19:31: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 6A23416A423; Thu, 16 Mar 2006 19:31:52 +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 E2D9843D5D; Thu, 16 Mar 2006 19:31:51 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k2GJVoNq047892; Thu, 16 Mar 2006 14:31:50 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Thu, 16 Mar 2006 14:27:26 -0500 User-Agent: KMail/1.9.1 References: <20060316184128.GA12770@reddwarf.local> In-Reply-To: <20060316184128.GA12770@reddwarf.local> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603161427.29180.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1335/Wed Mar 15 23:58:43 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.5 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: freebsd-questions@freebsd.org, Clayton Scott Kern Subject: Re: Unable to get SIIG PCI serial card to work 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, 16 Mar 2006 19:31:52 -0000 On Thursday 16 March 2006 13:41, Clayton Scott Kern wrote: > First, I added _device puc_ to my kernel config file and built and > installed the new kernel. That should have given you a puc0 device, did it not? > When that didn't work, I added _puc_load="YES"_ to /boot/loader and now > the card shows up as puc0, but no sioX. sio0 is used by the onboard > serial port and is being used with an APC SmartUPS 700. This won't work as the puc module doesn't include sio_puc (the version of the sio driver that attaches to puc devices). Yes, this is somewhat lame as it means the puc module is basically useless. I'm not sure if this has been made better since 6.0. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 16 20:33:25 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 6428A16A401; Thu, 16 Mar 2006 20:33:25 +0000 (UTC) (envelope-from ckern1@twcny.rr.com) Received: from ms-smtp-02.nyroc.rr.com (ms-smtp-02.nyroc.rr.com [24.24.2.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 530C943D66; Thu, 16 Mar 2006 20:33:16 +0000 (GMT) (envelope-from ckern1@twcny.rr.com) Received: from reddwarf.local (cpe-69-202-106-69.twcny.res.rr.com [69.202.106.69]) by ms-smtp-02.nyroc.rr.com (8.13.4/8.13.4) with ESMTP id k2GKXEbW013607; Thu, 16 Mar 2006 15:33:14 -0500 (EST) Received: from reddwarf.local (localhost [127.0.0.1]) by reddwarf.local (8.13.4/8.13.4) with ESMTP id k2GKXGIk013705; Thu, 16 Mar 2006 15:33:16 -0500 (EST) (envelope-from ckern1@reddwarf.local) Received: (from ckern1@localhost) by reddwarf.local (8.13.4/8.13.4/Submit) id k2GKXGKV013704; Thu, 16 Mar 2006 15:33:16 -0500 (EST) (envelope-from ckern1) Date: Thu, 16 Mar 2006 15:33:15 -0500 From: Clayton Scott Kern To: John Baldwin Message-ID: <20060316203315.GA13585@reddwarf.local> References: <20060316184128.GA12770@reddwarf.local> <200603161427.29180.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200603161427.29180.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Unable to get SIIG PCI serial card to work 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, 16 Mar 2006 20:33:25 -0000 on 03-16-2006, John Baldwin wrote: > On Thursday 16 March 2006 13:41, Clayton Scott Kern wrote: > > First, I added _device puc_ to my kernel config file and built and > > installed the new kernel. > > That should have given you a puc0 device, did it not? > No it didn't. > > When that didn't work, I added _puc_load="YES"_ to /boot/loader and now > > the card shows up as puc0, but no sioX. sio0 is used by the onboard > > serial port and is being used with an APC SmartUPS 700. > > This won't work as the puc module doesn't include sio_puc (the version > of the sio driver that attaches to puc devices). Yes, this is somewhat > lame as it means the puc module is basically useless. I'm not sure if > this has been made better since 6.0. > OK, I'll stop loading the module in /boot/loader.conf and work from there. -- Clayton Scott Kern ckern1@twcny.rr.com | The software stated it required Firewall/UNIX System Administrator | Microsoft Windows 98SE or higher, PIX, FreeBSD, Linux, Solaris & HP-UX | so I installed FreeBSD From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 16 20:45: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 B6E5616A400 for ; Thu, 16 Mar 2006 20:45:54 +0000 (UTC) (envelope-from cesar@fsonline.com.br) Received: from venom.itm.net.br (venom.itm.net.br [201.30.187.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 949D843D46 for ; Thu, 16 Mar 2006 20:45:52 +0000 (GMT) (envelope-from cesar@fsonline.com.br) Received: (qmail 13601 invoked by uid 89); 16 Mar 2006 20:45:18 -0000 Received: by simscan 1.2.0 ppid: 13593, pid: 13594, t: 2.4967s scanners: attach: 1.1.0 clamav: 0.88/m:36/d:1318 spam: 3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on venom.itm.net.br X-Spam-Level: X-Spam-Status: No, score=-4.3 required=6.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from ironman.fsonline.com.br (HELO ironman) (201.30.187.70) by venom.itm.net.br with SMTP; 16 Mar 2006 20:45:16 -0000 Message-ID: <037801c64939$fed3e160$0e4fdfc8@ironman> From: "Cesar Fazan" To: Date: Thu, 16 Mar 2006 17:41:26 -0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Antivirus: avast! (VPS 0611-1, 16/03/2006), Outbound message X-Antivirus-Status: Clean Subject: IC Plus IP1000A Gigabit Ethernet 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, 16 Mar 2006 20:45:54 -0000 Hi, Does anyone has the driver of this ethernet card for FreeBSD 6? The company who make these cards writed a driver for FreeBSD 5 (http://www.icplus.com.tw/Data/driver/IP1000A%20for%20FreeBSD%205%20Ver%20102.zip), but I have no luck trying to compile it on fbsd 6. Any help? Thanks. From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 16 20:55: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 6E5A716A401; Thu, 16 Mar 2006 20:55:13 +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 5866943D48; Thu, 16 Mar 2006 20:55:12 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k2GKt4ni048343; Thu, 16 Mar 2006 15:55:06 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Clayton Scott Kern Date: Thu, 16 Mar 2006 15:55:37 -0500 User-Agent: KMail/1.9.1 References: <20060316184128.GA12770@reddwarf.local> <200603161427.29180.jhb@freebsd.org> <20060316203315.GA13585@reddwarf.local> In-Reply-To: <20060316203315.GA13585@reddwarf.local> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603161555.41213.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1335/Wed Mar 15 23:58:43 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.5 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Unable to get SIIG PCI serial card to work 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, 16 Mar 2006 20:55:13 -0000 On Thursday 16 March 2006 15:33, Clayton Scott Kern wrote: > on 03-16-2006, John Baldwin wrote: > > On Thursday 16 March 2006 13:41, Clayton Scott Kern wrote: > > > First, I added _device puc_ to my kernel config file and built and > > > installed the new kernel. > > > > That should have given you a puc0 device, did it not? > > > No it didn't. Ok, can you get a dmesg from a boot with your custom kernel with puc in it and the output from kldstat -v with that kernel booted? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 16 22:07:19 2006 Return-Path: X-Original-To: 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 D0FAE16A401 for ; Thu, 16 Mar 2006 22:07:19 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from linda-4.paradise.net.nz (bm-4a.paradise.net.nz [203.96.152.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 404DD43D4C for ; Thu, 16 Mar 2006 22:07:18 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-1.paradise.net.nz (tclsnelb1-src-1.paradise.net.nz [203.96.152.172]) by linda-4.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IW800C3RQS3N3@linda-4.paradise.net.nz> for hardware@freebsd.org; Fri, 17 Mar 2006 11:07:17 +1300 (NZDT) Received: from [192.168.1.11] (218-101-28-185.dsl.clear.net.nz [218.101.28.185]) by smtp-1.paradise.net.nz (Postfix) with ESMTP id D965F8E2A89; Fri, 17 Mar 2006 11:07:14 +1300 (NZDT) Date: Fri, 17 Mar 2006 11:07:13 +1300 From: Mark Kirkwood In-reply-to: <44122B07.5070104@paradise.net.nz> To: Mark Kirkwood Message-id: <4419E191.3070004@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051106) References: <44122B07.5070104@paradise.net.nz> Cc: hardware@freebsd.org Subject: Re: 6.0-RELEASE /dev/pci still has config for uninstalled LAN card 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, 16 Mar 2006 22:07:19 -0000 Mark Kirkwood wrote: > I recently did a motherboard swap (removed VIA Apollo 133A board and > added VIA Apollo 266 based one). The new board has its own LAN (Intel > 82559), so I removed the PCI LAN card (VIA Rhine III based card). > > I noticed this in the boot up: > > vr0: port 0xc400-0xc4ff mem > 0xf7101000-0xf71010ff irq 11 at device 18.0 on pci0 > vr0: MII without any phy! > device_attach: vr0 attach returned 6 > > And pciconf shows: > > # pciconf -lv > .... > vr0@pci0:18:0: class=0x020000 card=0x01021106 chip=0x30651106 rev=0x62 > hdr=0x00 > vendor = 'VIA Technologies Inc' > device = 'VT6102 Rhine II PCI Fast Ethernet Controller' > class = network > subclass = ethernet > Figured this out - the new mobo has an optional stub for a second add on LAN card (the VIA Rhine VT6102 II) and the card I removed happened to be a VIA VT6105 Rhine III (close enough to confused me!). Disabling the optional stub in the BIOS has cleaned the various warnings. Sorry for the noise. Mark From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 16 22:22: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 70C1816A425 for ; Thu, 16 Mar 2006 22:22:44 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from linda-1.paradise.net.nz (bm-1a.paradise.net.nz [203.96.152.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0498643D46 for ; Thu, 16 Mar 2006 22:22:43 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-3.paradise.net.nz (tclsnelb1-src-1.paradise.net.nz [203.96.152.172]) by linda-1.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IW8008LWRHU2C@linda-1.paradise.net.nz> for freebsd-hardware@freebsd.org; Fri, 17 Mar 2006 11:22:42 +1300 (NZDT) Received: from [192.168.1.11] (218-101-28-185.dsl.clear.net.nz [218.101.28.185]) by smtp-3.paradise.net.nz (Postfix) with ESMTP id 3E838968F0B; Fri, 17 Mar 2006 11:22:42 +1300 (NZDT) Date: Fri, 17 Mar 2006 11:22:41 +1300 From: Mark Kirkwood In-reply-to: <1142526565.20584@swaggi.com> To: Yuri Lukin Message-id: <4419E531.7030105@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051106) References: <1142526565.20584@swaggi.com> Cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD shutting down unexpectedly 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, 16 Mar 2006 22:22:44 -0000 Yuri Lukin wrote: > Olivier Gautherot wrote .. > >>Hi Yuri! >> >>Good to see you solved your problem. >> >>Just keep in mind that if your CPU overheated for some time, it is likely >>to >>die prematurely. I would strongly recommend to check the CPU temperature >>and, >>if you figure out that it is starting to heat up more than usual, be it >>by a >>couple of degrees, make sure you get quickly a replacement: it is usually >>the >>first sign of an agony... I had one die this way. >> >>Cheers >> Olivier >> > > > Does anyone know if there's a document that shows what a normal operating > temperature (and maximum) is for an Intel Pentium processor? Mine is a > PIII Socket370 1.26Ghz and according to mbmon, average temp is 35 degrees > Celcius. Try the link below - you have to know your cpu sspec number (e.g. SL5LW) it shows voltage and temperature etc. http://processorfinder.intel.com/scripts/default.asp From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 16 22:24:11 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 1B45A16A400; Thu, 16 Mar 2006 22:24:11 +0000 (UTC) (envelope-from ckern1@twcny.rr.com) Received: from ms-smtp-02.nyroc.rr.com (ms-smtp-02.nyroc.rr.com [24.24.2.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91F7C43D46; Thu, 16 Mar 2006 22:24:10 +0000 (GMT) (envelope-from ckern1@twcny.rr.com) Received: from reddwarf.local (cpe-69-202-106-69.twcny.res.rr.com [69.202.106.69]) by ms-smtp-02.nyroc.rr.com (8.13.4/8.13.4) with ESMTP id k2GMO8eM017916; Thu, 16 Mar 2006 17:24:08 -0500 (EST) Received: from reddwarf.local (localhost [127.0.0.1]) by reddwarf.local (8.13.4/8.13.4) with ESMTP id k2GMO8F4001072; Thu, 16 Mar 2006 17:24:08 -0500 (EST) (envelope-from ckern1@reddwarf.local) Received: (from ckern1@localhost) by reddwarf.local (8.13.4/8.13.4/Submit) id k2GMO84B001071; Thu, 16 Mar 2006 17:24:08 -0500 (EST) (envelope-from ckern1) Date: Thu, 16 Mar 2006 17:24:08 -0500 From: Clayton Scott Kern To: John Baldwin Message-ID: <20060316222407.GA727@reddwarf.local> References: <20060316184128.GA12770@reddwarf.local> <200603161427.29180.jhb@freebsd.org> <20060316203315.GA13585@reddwarf.local> <200603161555.41213.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200603161555.41213.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Unable to get SIIG PCI serial card to work 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, 16 Mar 2006 22:24:11 -0000 on 03-16-2006, John Baldwin wrote: > > Ok, can you get a dmesg from a boot with your custom kernel with puc in it > and the output from kldstat -v with that kernel booted? > Here's the info you requested. When not loading the puc module in /boot/loader.conf, the puc device isn't found, though pciconf -lv shows the device. I added the output of pciconf -lv at the end. Output of dmesg Copyright (c) 1992-2005 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 6.0-RELEASE-p5 #0: Sat Mar 11 12:12:08 EST 2006 root@reddwarf.local:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) XP 2000+ (1662.46-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x681 Stepping = 1 Features=0x383fbff AMD Features=0xc0400800 real memory = 536805376 (511 MB) avail memory = 515956736 (492 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 10 on acpi0 pci_link1: irq 11 on acpi0 pci_link2: irq 3 on acpi0 pci_link3: irq 5 on acpi0 pci_link4: irq 0 on acpi0 pci_link5: irq 0 on acpi0 pci_link6: irq 0 on acpi0 pci_link7: irq 0 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff,0x4000-0x407f,0x4080-0x40ff,0x5000-0x500f on acpi0 pci0: on pcib0 agp0: mem 0xc0000000-0xcfffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pci0: at device 8.0 (no driver attached) pci0: at device 8.1 (no driver attached) ahc0: port 0xa000-0xa0ff mem 0xe3003000-0xe3003fff irq 17 at device 9.0 on pci0 ahc0: [GIANT-LOCKED] aic7860: Ultra Single Channel A, SCSI Id=7, 3/253 SCBs pcm0: port 0xa400-0xa41f irq 18 at device 10.0 on pci0 pcm0: rl0: port 0xac00-0xacff mem 0xe3005000-0xe30050ff irq 19 at device 14.0 on pci0 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:0a:e6:df:5c:ec uhci0: port 0xb000-0xb01f irq 21 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xb400-0xb41f irq 21 at device 16.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xb800-0xb81f irq 21 at device 16.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xe3006000-0xe30060ff irq 21 at device 16.3 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered umass0: vendor 0x05e3 USB 2.0 Card Reader, rev 2.00/1.28, addr 2 isab0: at device 17.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xbc00-0xbc0f at device 17.1 on pci0 ata0: on atapci0 ata1: on atapci0 pcm1: port 0xc000-0xc0ff irq 22 at device 17.5 on pci0 pcm1: [GIANT-LOCKED] pcm1: acpi_tz0: on acpi0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ppc0: port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model MouseMan+, device ID 0 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcf7ff,0xd0000-0xd7fff,0xd8000-0xd87ff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 umass1: MITSUMI MITSUMI USB FDD, rev 1.10/1.00, addr 2 Timecounter "TSC" frequency 1662456477 Hz quality 800 Timecounters tick every 1.000 msec ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to deny, logging disabled Waiting 5 seconds for SCSI devices to settle ad0: 39266MB at ata0-master UDMA100 acd0: CDRW at ata0-slave UDMA33 ad2: 19574MB at ata1-master UDMA66 ad3: 19574MB at ata1-slave UDMA66 sa0 at ahc0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 15) ch0 at ahc0 bus 0 target 6 lun 1 ch0: Removable Changer SCSI-2 device ch0: 5.000MB/s transfers (5.000MHz, offset 15) ch0: 4 slots, 1 drive, 1 picker, 0 portals da0 at ahc0 bus 0 target 5 lun 0 da0: Removable Direct Access SCSI-2 device da0: 3.300MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present (da0:ahc0:0:5:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:ahc0:0:5:0): CAM Status: SCSI Status Error (da0:ahc0:0:5:0): SCSI Status: Check Condition (da0:ahc0:0:5:0): NOT READY asc:3a,0 (da0:ahc0:0:5:0): Medium not present (da0:ahc0:0:5:0): Unretryable error Opened disk da0 -> 6 da1 at umass-sim0 bus 0 target 0 lun 0 da1: Removable Direct Access SCSI-0 device da1: 40.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present (da0:ahc0:0:5:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:ahc0:0:5:0): CAM Status: SCSI Status Error (da0:ahc0:0:5:0): SCSI Status: Check Condition (da0:ahc0:0:5:0): NOT READY asc:3a,0 (da0:ahc0:0:5:0): Medium not present (da0:ahc0:0:5:0): Unretryable error Opened disk da0 -> 6 (da0:ahc0:0:5:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:ahc0:0:5:0): CAM Status: SCSI Status Error (da0:ahc0:0:5:0): SCSI Status: Check Condition (da0:ahc0:0:5:0): NOT READY asc:3a,0 (da0:ahc0:0:5:0): Medium not present (da0:ahc0:0:5:0): Unretryable error Opened disk da0 -> 6 da2 at umass-sim0 bus 0 target 0 lun 1 da2: Removable Direct Access SCSI-0 device da2: 40.000MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present da5 at umass-sim1 bus 1 target 0 lun 0 da5: Removable Direct Access SCSI-0 device da5: 1.000MB/s transfers da5: Attempt to query device size failed: NOT READY, Medium not present da3 at umass-sim0 bus 0 target 0 lun 2 da3: Removable Direct Access SCSI-0 device da3: 40.000MB/s transfers da3: Attempt to query device size failed: NOT READY, Medium not present da4 at umass-sim0 bus 0 target 0 lun 3 da4: Removable Direct Access SCSI-0 device da4: 40.000MB/s transfers da4: Attempt to query device size failed: NOT READY, Medium not present (da1:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da1:umass-sim0:0:0:0): SCSI Status: Check Condition (da1:umass-sim0:0:0:0): NOT READY asc:3a,0 (da1:umass-sim0:0:0:0): Medium not present (da1:umass-sim0:0:0:0): Unretryable error Opened disk da1 -> 6 (da1:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da1:umass-sim0:0:0:0): SCSI Status: Check Condition (da1:umass-sim0:0:0:0): NOT READY asc:3a,0 (da1:umass-sim0:0:0:0): Medium not present (da1:umass-sim0:0:0:0): Unretryable error Opened disk da1 -> 6 (da1:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da1:umass-sim0:0:0:0): SCSI Status: Check Condition (da1:umass-sim0:0:0:0): NOT READY asc:3a,0 (da1:umass-sim0:0:0:0): Medium not present (da1:umass-sim0:0:0:0): Unretryable error Opened disk da1 -> 6 (da2:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 (da2:umass-sim0:0:0:1): CAM Status: SCSI Status Error (da2:umass-sim0:0:0:1): SCSI Status: Check Condition (da2:umass-sim0:0:0:1): NOT READY asc:3a,0 (da2:umass-sim0:0:0:1): Medium not present (da2:umass-sim0:0:0:1): Unretryable error Opened disk da2 -> 6 (da2:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 (da2:umass-sim0:0:0:1): CAM Status: SCSI Status Error (da2:umass-sim0:0:0:1): SCSI Status: Check Condition (da2:umass-sim0:0:0:1): NOT READY asc:3a,0 (da2:umass-sim0:0:0:1): Medium not present (da2:umass-sim0:0:0:1): Unretryable error Opened disk da2 -> 6 (da2:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 (da2:umass-sim0:0:0:1): CAM Status: SCSI Status Error (da2:umass-sim0:0:0:1): SCSI Status: Check Condition (da2:umass-sim0:0:0:1): NOT READY asc:3a,0 (da2:umass-sim0:0:0:1): Medium not present (da2:umass-sim0:0:0:1): Unretryable error Opened disk da2 -> 6 (da3:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:2): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:2): SCSI Status: Check Condition (da3:umass-sim0:0:0:2): NOT READY asc:3a,0 (da3:umass-sim0:0:0:2): Medium not present (da3:umass-sim0:0:0:2): Unretryable error Opened disk da3 -> 6 (da3:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:2): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:2): SCSI Status: Check Condition (da3:umass-sim0:0:0:2): NOT READY asc:3a,0 (da3:umass-sim0:0:0:2): Medium not present (da3:umass-sim0:0:0:2): Unretryable error Opened disk da3 -> 6 (da3:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:2): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:2): SCSI Status: Check Condition (da3:umass-sim0:0:0:2): NOT READY asc:3a,0 (da3:umass-sim0:0:0:2): Medium not present (da3:umass-sim0:0:0:2): Unretryable error Opened disk da3 -> 6 (da4:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0 (da4:umass-sim0:0:0:3): CAM Status: SCSI Status Error (da4:umass-sim0:0:0:3): SCSI Status: Check Condition (da4:umass-sim0:0:0:3): NOT READY asc:3a,0 (da4:umass-sim0:0:0:3): Medium not present (da4:umass-sim0:0:0:3): Unretryable error Opened disk da4 -> 6 (da4:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0 (da4:umass-sim0:0:0:3): CAM Status: SCSI Status Error (da4:umass-sim0:0:0:3): SCSI Status: Check Condition (da4:umass-sim0:0:0:3): NOT READY asc:3a,0 (da4:umass-sim0:0:0:3): Medium not present (da4:umass-sim0:0:0:3): Unretryable error Opened disk da4 -> 6 (da4:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0 (da4:umass-sim0:0:0:3): CAM Status: SCSI Status Error (da4:umass-sim0:0:0:3): SCSI Status: Check Condition (da4:umass-sim0:0:0:3): NOT READY asc:3a,0 (da4:umass-sim0:0:0:3): Medium not present (da4:umass-sim0:0:0:3): Unretryable error Opened disk da4 -> 6 (da5:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da5:umass-sim1:1:0:0): CAM Status: SCSI Status Error (da5:umass-sim1:1:0:0): SCSI Status: Check Condition (da5:umass-sim1:1:0:0): NOT READY asc:3a,0 (da5:umass-sim1:1:0:0): Medium not present (da5:umass-sim1:1:0:0): Unretryable error Opened disk da5 -> 6 (da5:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da5:umass-sim1:1:0:0): CAM Status: SCSI Status Error (da5:umass-sim1:1:0:0): SCSI Status: Check Condition (da5:umass-sim1:1:0:0): NOT READY asc:3a,0 (da5:umass-sim1:1:0:0): Medium not present (da5:umass-sim1:1:0:0): Unretryable error Opened disk da5 -> 6 (da5:umass-sim1:1:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da5:umass-sim1:1:0:0): CAM Status: SCSI Status Error (da5:umass-sim1:1:0:0): SCSI Status: Check Condition (da5:umass-sim1:1:0:0): NOT READY asc:3a,0 (da5:umass-sim1:1:0:0): Medium not present (da5:umass-sim1:1:0:0): Unretryable error Opened disk da5 -> 6 Trying to mount root from ufs:/dev/ad2s1a Output of kldstat -v Id Refs Address Size Name 1 11 0xc0400000 63072c kernel Contains modules: Id Name 26 xpt 27 probe 28 cam 29 cd 30 ch 31 da 32 scsi_low 33 pass 34 sa 35 ses 36 aac/aacp 37 aac/aacd 38 pci/aac 39 pci/aacch 40 eisa/adv 41 pci/adv 42 pci/adw 43 isa/aha 44 eisa/ahb 45 pccard/aic 46 eisa/ahc_eisa 47 isa/ahc_isa 48 pci/ahc_pci 49 cardbus/ahc_pci 50 pci/ahd 51 cardbus/ahd 52 ahd 53 ahc 54 pci/amd 55 amr/amrd 56 pci/amr 57 isa/an 58 pccard/an 59 pci/an 60 pci/asr 61 ata 62 pccard/ata 63 ata/ad 64 isa/ata 65 pci/atapci 66 atapci/ata 67 ad/subdisk 68 ataraid 69 ata/acd 70 ata/afd 71 ata/ast 72 pccard/awi 73 pci/bfe 74 bfe/miibus 75 pci/bge 76 bge/miibus 77 eisa/bt 78 isa/bt 79 pci/bt 80 cbb/cardbus 81 pci/ciss 82 isa/cs 83 pccard/cs 84 eisa/dpt 85 pci/dpt 86 pccard/ed 87 ed/miibus 88 pci/ed 89 eisa/mainboard 90 eisab/eisa 91 legacy/eisa 92 pci/em 93 eisa/ep 94 isa/ep 95 pccard/ep 96 isa/ex 97 exca 98 pccard/fe 99 fwohci/firewire 100 pci/fwohci 101 cardbus/fwohci 102 firewire/fwe 103 firewire/sbp 104 pci/fxp 105 cardbus/fxp 106 fxp/miibus 107 ida/idad 108 eisa/ida 109 pci/ida 110 isa/ie_3C507 111 isa/ie_EE16 112 isa/ie_SL 113 pci/iir 114 ips/ipsd 115 pci/ips 116 pci/isp 117 pci/if_ixgb 118 pci/lge 119 lge/miibus 120 pci/lnc 121 g_md 122 mem 123 miibus/acphy 124 miibus/amphy 125 miibus/bmtphy 126 miibus/brgphy 127 miibus/ciphy 128 miibus/dcphy 129 miibus/e1000phy 130 miibus/xlphy 131 miibus/inphy 132 miibus/lxtphy 133 miibus/mlphy 134 miibus/nsgphy 135 miibus/nsphy 136 miibus/pnaphy 137 miibus/pnphy 138 miibus/qsphy 139 miibus/rgephy 140 miibus/rlphy 141 miibus/ruephy 142 miibus/tdkphy 143 miibus/tlphy 144 miibus/ukphy 145 miibus/xmphy 146 mlx/mlxd 147 pci/mlx 148 pci/mly 149 mpt_core 150 mpt_cam 151 pci/mpt 152 mpt_raid 153 pccard/ncv 154 pci/nge 155 nge/miibus 156 pccard/nsp 157 null 158 pcic/pccard 159 cbb/pccard 160 isa/cbb 161 pci/cbb 162 pci/eisab 163 pci/fixup_pci 164 pci/ignore_pci 165 pci/isab 166 pcib/pci 167 pci/pcib 168 ppbus/plip 169 ppbus/lpt 170 ppc/ppbus 171 ppbus/ppi 172 pci/pstpci 173 pstpci/pst 174 pccard/ral 175 pci/ral 176 cardbus/ral 177 random 178 pci/re 179 cardbus/re 180 re/miibus 181 pccard/sio 182 pci/sio 183 cardbus/sio 184 isa/sn 185 pccard/sn 186 isa/stg 187 pccard/stg 188 pci/stg 189 pci/sym 190 pci/trm 191 pci/twa 192 pci/twe 193 twe/twed 194 pci/tx 195 tx/miibus 196 pci/txp 197 pci/ehci 198 cardbus/ehci 199 uhub/aue 200 aue/miibus 201 uhub/axe 202 axe/miibus 203 uhub/cdce 204 uhub/cue 205 uhub/kue 206 uhub/ural 207 uhub/rue 208 rue/miibus 209 pci/ohci 210 cardbus/ohci 211 uhub/ugen 212 pci/uhci 213 cardbus/uhci 214 uhub/uhid 215 usb/uhub 216 uhub/uhub 217 uhub/ukbd 218 uhub/ulpt 219 uhub/umass 220 uhub/ums 221 uhub/urio 222 ohci/usb 223 uhci/usb 224 ehci/usb 225 uhub/uscanner 226 pci/vge 227 cardbus/vge 228 vge/miibus 229 eisa/vx 230 pci/vx 231 watchdog 232 pccard/wi 233 pci/wi 234 pccard/xe 235 devfs 236 msdosfs 237 procfs 238 pseudofs 239 g_dev 240 g_disk 241 g_gpt 242 g_vfs 243 isab/isa 244 eisab/isa 245 isa/isahint 246 isa/orm 247 isa/pnp 248 cd9660 249 elf32 250 shell 251 cpu/cpufreq 252 rootbus 253 msgsys 254 msgctl 255 msgget 256 msgsnd 257 msgrcv 258 sysvmsg 259 semsys 260 __semctl 261 semget 262 semop 263 sysvsem 264 shmsys 265 shmat 266 shmctl 267 shmdt 268 shmget 269 sysvshm 270 ether 271 if_faith 272 if_gif 273 loop 274 if_ppp 275 if_sl 276 if_tun 277 wlan 278 nfs4 279 nfs 280 nfslock 281 nfsserver 282 cardbus/dc 283 pci/dc 284 dc/miibus 285 pci/de 286 pci/pcn 287 pcn/miibus 288 pci/rl 289 cardbus/rl 290 rl/miibus 291 pci/sf 292 sf/miibus 293 pci/sis 294 sis/miibus 295 pci/sk 296 skc/sk 297 sk/miibus 298 pci/ste 299 ste/miibus 300 pci/ti 301 pci/tl 302 tl/miibus 303 pci/vr 304 vr/miibus 305 pci/wb 306 wb/miibus 307 cardbus/xl 308 pci/xl 309 xl/miibus 310 ufs 311 g_class 312 isa/adv 313 isa/aic 314 pci/arcmsr 315 atkbdc/atkbd 316 isa/atkbdc 317 acpi/atkbdc 318 atkbdc/psm 319 isa/psmcpnp 320 acpi/psmcpnp 321 isa/ed 322 fdc/fd 323 acpi/fdc 324 isa/fdc 325 pccard/fdc 326 isa/fe 327 pci/hptmv 328 io 329 isa/lnc 330 pci/nve 331 nve/miibus 332 isa/ppc 333 acpi/ppc 334 isa/sio 335 acpi/sio 336 scterm-sc 337 scrndr-vga 338 g_bsd 339 g_mbr 340 g_mbrext 341 isa/pnpbios 342 nexus/legacy 343 legacy/cpu 344 legacy/mptable_pcib 345 pci/mptable_pcib 346 root/nexus 347 isa/sysresource 348 isa/atpic 349 acpi/atpic 350 isa/attimer 351 acpi/attimer 352 elink 353 legacy/isa 354 isa/atdma 355 acpi/atdma 356 nexus/npx 357 isa/npxisa 358 acpi/npxisa 359 isa/pmtimer 360 legacy/pcib 361 pci/hostb 362 isa/pcibus_pnp 363 pci/pcibios_pcib 364 legacy/pir 365 isa/sc 366 isa/vga 367 pci/agp_ali 368 pci/agp_amd 369 pci/agp_amd64 370 pci/agp_i810 371 pci/agp_intel 372 pci/agp_nvidia 373 pci/agp_sis 374 pci/agp_via 2 1 0xc0a31000 196c8 linux.ko Contains modules: Id Name 1 linuxelf 2 linuxaout 3 1 0xc0a4b000 d828 ipfw.ko Contains modules: Id Name 3 ipfw 4 1 0xc0a59000 7794 snd_emu10k1.ko Contains modules: Id Name 5 pci/emujoy 6 cardbus/snd_emu10k1 7 pci/snd_emu10k1 5 3 0xc0a61000 1d408 sound.ko Contains modules: Id Name 4 sound 6 1 0xc0a7f000 4758 snd_via8233.ko Contains modules: Id Name 8 pci/snd_via8233 7 16 0xc0a84000 568dc acpi.ko Contains modules: Id Name 9 nexus/acpi 10 acpi/acpi_button 11 acpi/acpi_isab 12 pcib/acpi_pci 13 acpi/acpi_pcib 14 pci/acpi_pcib 15 acpi/acpi_sysresource 16 acpi/acpi_timer 17 acpi/acpi_pci_link 18 acpi/acpi_tz 19 acpi/acpi_acad 20 acpi/acpi_cmbat 21 acpi/cpu 22 acpi/acpi_ec 23 acpi/acpi_lid 24 cpu/acpi_perf 25 cpu/acpi_throttle Output of pciconf -lv agp0@pci0:0:0: class=0x060000 card=0x0a851019 chip=0x31161106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8375 ProSavageDDR PM266/KM266 CPU to PCI Bridge' class = bridge subclass = HOST-PCI pcib1@pci0:1:0: class=0x060400 card=0x00000080 chip=0xb0911106 rev=0x00 hdr=0x01 vendor = 'VIA Technologies Inc' device = 'VT8633 Apollo Pro 266 CPU to AGP Controller' class = bridge subclass = PCI-PCI none0@pci0:8:0: class=0x070006 card=0x2000131f chip=0x950a1415 rev=0x00 hdr=0x00 vendor = 'Oxford Semiconductor Ltd' device = 'OX16PCI954 Dual PCI UART (??)' class = simple comms subclass = UART none1@pci0:8:1: class=0x068000 card=0x0000131f chip=0x95101415 rev=0x00 hdr=0x00 vendor = 'Oxford Semiconductor Ltd' device = 'OX16PCI954 PCI Interface (disabled)' class = bridge ahc0@pci0:9:0: class=0x010000 card=0x00000000 chip=0x60789004 rev=0x01 hdr=0x00 vendor = 'Adaptec Inc' device = 'AIC-7860 PCI SCSI Controller' class = mass storage subclass = SCSI pcm0@pci0:10:0: class=0x040100 card=0x100a1102 chip=0x00021102 rev=0x0a hdr=0x00 vendor = 'Creative Labs' device = 'EMU10000 Sound Blaster Live! (Also Live! 5.1) - OEM from DELL - CT4780' class = multimedia subclass = audio emujoy0@pci0:10:1: class=0x098000 card=0x00201102 chip=0x70021102 rev=0x0a hdr=0x00 vendor = 'Creative Labs' device = 'EMU10000 Game Port' class = input device rl0@pci0:14:0: class=0x020000 card=0x813910ec chip=0x813910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RT8139 (A/B/C/810x/813x/C+) Fast Ethernet Adapter' class = network subclass = ethernet uhci0@pci0:16:0: class=0x0c0300 card=0x0a851019 chip=0x30381106 rev=0x80 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB uhci1@pci0:16:1: class=0x0c0300 card=0x0a851019 chip=0x30381106 rev=0x80 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB uhci2@pci0:16:2: class=0x0c0300 card=0x0a851019 chip=0x30381106 rev=0x80 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82xxxxx UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB ehci0@pci0:16:3: class=0x0c0320 card=0x0a851019 chip=0x31041106 rev=0x82 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT6202 USB 2.0 Enhanced Host Controller' class = serial bus subclass = USB isab0@pci0:17:0: class=0x060100 card=0x0a851019 chip=0x31771106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8235 PCI to ISA Bridge' class = bridge subclass = PCI-ISA atapci0@pci0:17:1: class=0x01018a card=0x0a851019 chip=0x05711106 rev=0x06 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82xxxx EIDE Controller (All VIA Chipsets)' class = mass storage subclass = ATA pcm1@pci0:17:5: class=0x040100 card=0x0a851019 chip=0x30591106 rev=0x50 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8233/33A/8235/8237 AC97 Enhanced Audio Controller' class = multimedia subclass = audio none2@pci1:0:0: class=0x030000 card=0x00000000 chip=0x032610de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'GeForce FX 5500 [NV34.6]' class = display subclass = VGA -- Clayton Scott Kern ckern1@twcny.rr.com | The software stated it required Firewall/UNIX System Administrator | Microsoft Windows 98SE or higher, PIX, FreeBSD, Linux, Solaris & HP-UX | so I installed FreeBSD From owner-freebsd-hardware@FreeBSD.ORG Fri Mar 17 02:58: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 B2CB916A401 for ; Fri, 17 Mar 2006 02:58:58 +0000 (UTC) (envelope-from g_jin@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 3BC6943D45 for ; Fri, 17 Mar 2006 02:58:58 +0000 (GMT) (envelope-from g_jin@lbl.gov) Received: (qmail 50032 invoked from network); 17 Mar 2006 02:58:57 -0000 Received: from unknown (HELO ?192.168.2.10?) (jinmtb@sbcglobal.net@68.127.172.58 with plain) by smtp114.sbc.mail.mud.yahoo.com with SMTP; 17 Mar 2006 02:58:57 -0000 Message-ID: <441A263F.3060906@lbl.gov> Date: Thu, 16 Mar 2006 19:00:15 -0800 From: "Jin Guojun [VFFS]" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050108 X-Accept-Language: zh, zh-CN, en MIME-Version: 1.0 To: Yuri Lukin References: <1142526565.20584@swaggi.com> In-Reply-To: <1142526565.20584@swaggi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD shutting down unexpectedly 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, 17 Mar 2006 02:58:58 -0000 Yuri Lukin wrote: > Does anyone know if there's a document that shows what a normal operating > >temperature (and maximum) is for an Intel Pentium processor? Mine is a >PIII Socket370 1.26Ghz and according to mbmon, average temp is 35 degrees >Celcius. > >thx >-Yuri > > Technically, temperature below 39C is a super condition. From 55C to 60C is alerting zone, which is OK working condition. The maximum temperature depends on each CPU specification, which can be from 60C to 79C. Older CPUs may have a lower limit. Yours is OK, and the CPU seems your CPU has an auto shutdown mechanism on temperature. Newer CPUs more or less have similar mechanism to either slow down or shut down as temperature passing the altering zone. -Jin From owner-freebsd-hardware@FreeBSD.ORG Fri Mar 17 03:48: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 11C5016A400; Fri, 17 Mar 2006 03:48:54 +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 9D4AB43D5E; Fri, 17 Mar 2006 03:48:46 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k2H3miiH050391; Thu, 16 Mar 2006 22:48:45 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Clayton Scott Kern Date: Thu, 16 Mar 2006 21:58:01 -0500 User-Agent: KMail/1.8.3 References: <20060316184128.GA12770@reddwarf.local> <200603161555.41213.jhb@freebsd.org> <20060316222407.GA727@reddwarf.local> In-Reply-To: <20060316222407.GA727@reddwarf.local> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200603162158.02027.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1335/Wed Mar 15 23:58:43 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.5 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Unable to get SIIG PCI serial card to work 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, 17 Mar 2006 03:48:54 -0000 On Thursday 16 March 2006 05:24 pm, Clayton Scott Kern wrote: > on 03-16-2006, John Baldwin wrote: > > Ok, can you get a dmesg from a boot with your custom kernel with puc in > > it and the output from kldstat -v with that kernel booted? > > Here's the info you requested. When not loading the puc module in > /boot/loader.conf, the puc device isn't found, though pciconf -lv shows > the device. I added the output of pciconf -lv at the end. > > Output of dmesg > > Copyright (c) 1992-2005 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 6.0-RELEASE-p5 #0: Sat Mar 11 12:12:08 EST 2006 > root@reddwarf.local:/usr/obj/usr/src/sys/GENERIC This kernel doesn't have 'device puc' in it. If it did, it would have the= =20 'pci/puc' and 'puc/sio' modules listed in the kldstat -v output. Make sure= =20 you have built a custom kernel with 'device puc' enabled, installed it, and= =20 are booting from it. > Output of kldstat -v > > Id Refs Address Size Name > 1 11 0xc0400000 63072c kernel > Contains modules: > Id Name > 26 xpt > 27 probe > 28 cam > ... No puc this list tells me 'device puc' isn't in this kernel. :) =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-hardware@FreeBSD.ORG Fri Mar 17 08:40:28 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 C055A16A401; Fri, 17 Mar 2006 08:40:28 +0000 (UTC) (envelope-from ckern1@twcny.rr.com) Received: from ms-smtp-02.nyroc.rr.com (ms-smtp-02.nyroc.rr.com [24.24.2.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5E9943D5A; Fri, 17 Mar 2006 08:40:26 +0000 (GMT) (envelope-from ckern1@twcny.rr.com) Received: from reddwarf.local (cpe-69-202-106-69.twcny.res.rr.com [69.202.106.69]) by ms-smtp-02.nyroc.rr.com (8.13.4/8.13.4) with ESMTP id k2H8eOhK029188; Fri, 17 Mar 2006 03:40:24 -0500 (EST) Received: from reddwarf.local (localhost [127.0.0.1]) by reddwarf.local (8.13.4/8.13.4) with ESMTP id k2H8eOwb001190; Fri, 17 Mar 2006 03:40:24 -0500 (EST) (envelope-from ckern1@reddwarf.local) Received: (from ckern1@localhost) by reddwarf.local (8.13.4/8.13.4/Submit) id k2H8eNLf001189; Fri, 17 Mar 2006 03:40:23 -0500 (EST) (envelope-from ckern1) Date: Fri, 17 Mar 2006 03:40:23 -0500 From: Clayton Scott Kern To: John Baldwin Message-ID: <20060317084023.GA731@reddwarf.local> References: <20060316184128.GA12770@reddwarf.local> <200603161555.41213.jhb@freebsd.org> <20060316222407.GA727@reddwarf.local> <200603162158.02027.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200603162158.02027.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Unable to get SIIG PCI serial card to work 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, 17 Mar 2006 08:40:29 -0000 on 03-16-2006, John Baldwin wrote: > On Thursday 16 March 2006 05:24 pm, Clayton Scott Kern wrote: > > on 03-16-2006, John Baldwin wrote: > > > Ok, can you get a dmesg from a boot with your custom kernel with puc in > > > it and the output from kldstat -v with that kernel booted? > > > > Here's the info you requested. When not loading the puc module in > > /boot/loader.conf, the puc device isn't found, though pciconf -lv shows > > the device. I added the output of pciconf -lv at the end. > > > > Output of dmesg > > > > Copyright (c) 1992-2005 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 6.0-RELEASE-p5 #0: Sat Mar 11 12:12:08 EST 2006 > > root@reddwarf.local:/usr/obj/usr/src/sys/GENERIC > > This kernel doesn't have 'device puc' in it. If it did, it would have the > 'pci/puc' and 'puc/sio' modules listed in the kldstat -v output. Make sure > you have built a custom kernel with 'device puc' enabled, installed it, and > are booting from it. > > > Output of kldstat -v > > > > Id Refs Address Size Name > > 1 11 0xc0400000 63072c kernel > > Contains modules: > > Id Name > > 26 xpt > > 27 probe > > 28 cam > > ... > > No puc this list tells me 'device puc' isn't in this kernel. :) > Thank you for all your help. I thought I had built and installed the new kernel. This time I did both and now dmesg shows: puc0: port 0x9000-0x901f,0x9400-0x941f mem 0xe30 04000-0xe3004fff,0xe3000000-0xe3000fff irq 16 at device 8.0 on pci0 sio1: on puc0 sio1: type 16550A sio1: unable to activate interrupt in fast mode - using normal mode sio2: on puc0 sio2: type 16550A sio2: unable to activate interrupt in fast mode - using normal mode sio3: on puc0 sio3: type 16550A sio3: unable to activate interrupt in fast mode - using normal mode sio4: on puc0 sio4: type 16550A sio4: unable to activate interrupt in fast mode - using normal mode and kldstat -v | fgrep puc yields: 174 pccard/puc 175 pci/puc 176 cardbus/puc 187 puc/sio 337 puc/ppc Now when I run tip using sio1 - sio4 (aliases for /dev/cuad1-4), I get a message saying connected, but when I press enter, instead of getting my firewall's menu, I get nothing. I rebooted the system into Windoze and it works fine using TerraTerm Pro. -- Clayton Scott Kern ckern1@twcny.rr.com | The software stated it required Firewall/UNIX System Administrator | Microsoft Windows 98SE or higher, PIX, FreeBSD, Linux, Solaris & HP-UX | so I installed FreeBSD From owner-freebsd-hardware@FreeBSD.ORG Fri Mar 17 08:56:22 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 7FF8816A420 for ; Fri, 17 Mar 2006 08:56:22 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd5mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A1F743D45 for ; Fri, 17 Mar 2006 08:56:21 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd5mr5so.prod.shaw.ca (pd5mr5so-qfe3.prod.shaw.ca [10.0.141.181]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IW900H1UKTXYX40@l-daemon> for freebsd-hardware@freebsd.org; Fri, 17 Mar 2006 01:56:21 -0700 (MST) Received: from pn2ml3so.prod.shaw.ca ([10.0.121.147]) by pd5mr5so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IW900AQGKTXAWF0@pd5mr5so.prod.shaw.ca> for freebsd-hardware@freebsd.org; Fri, 17 Mar 2006 01:56:21 -0700 (MST) Received: from soralx.cydem.org ([24.87.27.3]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IW9007CHKTW1DU0@l-daemon> for freebsd-hardware@freebsd.org; Fri, 17 Mar 2006 01:56:21 -0700 (MST) Date: Fri, 17 Mar 2006 00:56:19 -0800 From: soralx@cydem.org In-reply-to: <441A263F.3060906@lbl.gov> To: freebsd-hardware@freebsd.org Message-id: <200603170056.19065.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <1142526565.20584@swaggi.com> <441A263F.3060906@lbl.gov> User-Agent: KMail/1.5.4 Cc: g_jin@lbl.gov Subject: Re: FreeBSD shutting down unexpectedly 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, 17 Mar 2006 08:56:22 -0000 Yuri Lukin wrote: > Does anyone know if there's a document that shows what a normal operating >temperature (and maximum) is for an Intel Pentium processor? Mine is a >PIII Socket370 1.26Ghz and according to mbmon, average temp is 35 degrees >Celcius. be sure to check Tcpu in BIOS before trusting mbmon (on my board, mbmon show CPU temperature ~20*C lower than BIOS; chipset temp & other data seem to be OK) see Intel's datasheets for power consumption, Tmax, etc. you can calculate approximate operating temperature by multiplying heat dissipation value (which is about equivalent to power consumption) by the cooler's thermal resistance (expressed in K/W or *C/W). Timestamp: 0x441A717B [SorAlx] http://cydem.org.ua/ ridin' VN1500-B2 From owner-freebsd-hardware@FreeBSD.ORG Fri Mar 17 13:13:57 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 F176316A400; Fri, 17 Mar 2006 13:13:56 +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 663BA43D46; Fri, 17 Mar 2006 13:13:56 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k2HDDshG053765; Fri, 17 Mar 2006 08:13:54 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Clayton Scott Kern Date: Fri, 17 Mar 2006 08:11:50 -0500 User-Agent: KMail/1.8.3 References: <20060316184128.GA12770@reddwarf.local> <200603162158.02027.jhb@freebsd.org> <20060317084023.GA731@reddwarf.local> In-Reply-To: <20060317084023.GA731@reddwarf.local> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200603170811.51962.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1335/Wed Mar 15 23:58:43 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.5 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Unable to get SIIG PCI serial card to work 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, 17 Mar 2006 13:13:57 -0000 On Friday 17 March 2006 03:40 am, Clayton Scott Kern wrote: > on 03-16-2006, John Baldwin wrote: > > On Thursday 16 March 2006 05:24 pm, Clayton Scott Kern wrote: > > > on 03-16-2006, John Baldwin wrote: > > > > Ok, can you get a dmesg from a boot with your custom kernel with puc > > > > in it and the output from kldstat -v with that kernel booted? > > > > > > Here's the info you requested. When not loading the puc module in > > > /boot/loader.conf, the puc device isn't found, though pciconf -lv sho= ws > > > the device. I added the output of pciconf -lv at the end. > > > > > > Output of dmesg > > > > > > Copyright (c) 1992-2005 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 6.0-RELEASE-p5 #0: Sat Mar 11 12:12:08 EST 2006 > > > root@reddwarf.local:/usr/obj/usr/src/sys/GENERIC > > > > This kernel doesn't have 'device puc' in it. If it did, it would have > > the 'pci/puc' and 'puc/sio' modules listed in the kldstat -v output.=20 > > Make sure you have built a custom kernel with 'device puc' enabled, > > installed it, and are booting from it. > > > > > Output of kldstat -v > > > > > > Id Refs Address Size Name > > > 1 11 0xc0400000 63072c kernel > > > Contains modules: > > > Id Name > > > 26 xpt > > > 27 probe > > > 28 cam > > > ... > > > > No puc this list tells me 'device puc' isn't in this kernel. :) > > Thank you for all your help. > > I thought I had built and installed the new kernel. This time I did > both and now dmesg shows: > > puc0: port > 0x9000-0x901f,0x9400-0x941f mem 0xe30 > 04000-0xe3004fff,0xe3000000-0xe3000fff irq 16 at device 8.0 on pci0 > sio1: on puc0 > sio1: type 16550A > sio1: unable to activate interrupt in fast mode - using normal mode > sio2: on puc0 > sio2: type 16550A > sio2: unable to activate interrupt in fast mode - using normal mode > sio3: on puc0 > sio3: type 16550A > sio3: unable to activate interrupt in fast mode - using normal mode > sio4: on puc0 > sio4: type 16550A > sio4: unable to activate interrupt in fast mode - using normal mode > > and kldstat -v | fgrep puc yields: > > 174 pccard/puc > 175 pci/puc > 176 cardbus/puc > 187 puc/sio > 337 puc/ppc > > Now when I run tip using sio1 - sio4 (aliases for /dev/cuad1-4), I get a > message saying connected, but when I press enter, instead of getting my > firewall's menu, I get nothing. > > I rebooted the system into Windoze and it works fine using TerraTerm Pro. You might need to play with stty to do things like -clocal or -crtscts to get it to work. stty -a < /dev/cuad1 will tell you what the current settings are (IIRC). Also, what speed are you using in TerraTerm? 9600? Note that with cu you can specify the speed directly (e.g. cu -l /dev/cuad1 -s 115200). =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-hardware@FreeBSD.ORG Fri Mar 17 14:39:09 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 1971116A400 for ; Fri, 17 Mar 2006 14:39:09 +0000 (UTC) (envelope-from nazim.aliyev@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id A514F43D48 for ; Fri, 17 Mar 2006 14:39:08 +0000 (GMT) (envelope-from nazim.aliyev@gmail.com) Received: by wproxy.gmail.com with SMTP id i30so546772wra for ; Fri, 17 Mar 2006 06:39:08 -0800 (PST) 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; b=iTUGyNmr4htjKKThQg37CYNqFGETh/dqO+TMcDeZ+MyQgIQ7FV+6xwA5DZGlETNCawqkUa+e2MXgbq+hQn4QTn7CrsjiHNpj2XsW/tgIQf1psdKjYQrI82pnOib0NQYNkSlaHS1cb1rB2G0xLdtXt3GBaIcOG2uXU+DxvXz/Bxo= Received: by 10.64.180.12 with SMTP id c12mr65029qbf; Fri, 17 Mar 2006 06:39:06 -0800 (PST) Received: by 10.65.197.9 with HTTP; Fri, 17 Mar 2006 06:39:06 -0800 (PST) Message-ID: Date: Fri, 17 Mar 2006 18:39:06 +0400 From: "Nazim Aliyev" To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Xeon 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, 17 Mar 2006 14:39:09 -0000 Hello everybody. I'm beginner and want to install FreeBSD on my PC. PC has Intel Xeon (64 bit) CPU. Which FreeBSD will run on it? -- Best regards, Nazim Aliyev From owner-freebsd-hardware@FreeBSD.ORG Fri Mar 17 16:36:17 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 7B6FB16A420 for ; Fri, 17 Mar 2006 16:36:17 +0000 (UTC) (envelope-from freebsd@swaggi.com) Received: from swaggi.com (c-24-131-179-91.hsd1.ma.comcast.net [24.131.179.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D34243D45 for ; Fri, 17 Mar 2006 16:36:17 +0000 (GMT) (envelope-from freebsd@swaggi.com) Received: from localhost ([127.0.0.1] helo=swaggi.com) by swaggi.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FKHyi-0007Sb-09 for freebsd-hardware@freebsd.org; Fri, 17 Mar 2006 11:39:04 -0500 Received: (from freebsd@localhost) by swaggi.com (8.13.4/8.13.4/Submit) id k2HGd33U028678; Fri, 17 Mar 2006 11:39:03 -0500 (EST) (envelope-from freebsd@swaggi.com) Date: Fri, 17 Mar 2006 11:39:03 -0500 (EST) From: "Yuri Lukin" To: freebsd-hardware@freebsd.org Cc: X-Originating-IP: 192.168.1.9 X-Mailer: Usermin 1.190 In-Reply-To: <200603170056.19065.soralx@cydem.org> Message-Id: <1142613543.28676@swaggi.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1142613543" Subject: Re: FreeBSD shutting down unexpectedly 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, 17 Mar 2006 16:36:17 -0000 This is a multi-part message in MIME format. --bound1142613543 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit soralx@cydem.org wrote .. > > be sure to check Tcpu in BIOS before trusting mbmon (on my board, mbmon > show CPU temperature ~20*C lower than BIOS; chipset temp & other data > seem to be OK) > > see Intel's datasheets for power consumption, Tmax, etc. > you can calculate approximate operating temperature by multiplying heat > dissipation value (which is about equivalent to power consumption) by the > cooler's thermal resistance (expressed in K/W or *C/W). > You were right, I checked the BIOS hardware monitor and found out that mbmon was reporting the temperature 20*C lower then the BIOS. This brings my avg Tcpu to around 55*C which seems somewhat high considering Intel's datasheet says my processor is rated for a max of 69*C. Should I be worried? -Yuri --bound1142613543-- From owner-freebsd-hardware@FreeBSD.ORG Fri Mar 17 17:27:01 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 5D8DC16A400 for ; Fri, 17 Mar 2006 17:27:01 +0000 (UTC) (envelope-from simon@optinet.com) Received: from cobra.acceleratedweb.net (cobra-gw.acceleratedweb.net [207.99.79.37]) by mx1.FreeBSD.org (Postfix) with SMTP id D9F3443D4C for ; Fri, 17 Mar 2006 17:27:00 +0000 (GMT) (envelope-from simon@optinet.com) Received: (qmail 13593 invoked by uid 110); 17 Mar 2006 17:26:59 -0000 Received: from ool-45701e98.dyn.optonline.net (HELO win2kpc1) (simon%optinet.com@69.112.30.152) by cobra.acceleratedweb.net with SMTP; 17 Mar 2006 17:26:59 -0000 From: "Simon" To: "freebsd-hardware@freebsd.org" , "Nazim Aliyev" Date: Fri, 17 Mar 2006 12:30:56 -0500 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2661) For Windows 2000 (5.0.2195;4) In-Reply-To: MIME-Version: 1.0 Message-Id: <20060317172700.D9F3443D4C@mx1.FreeBSD.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: Xeon 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, 17 Mar 2006 17:27:01 -0000 Yes, it will run, why don't you just try :-) Get 6.0-px version -Simon On Fri, 17 Mar 2006 18:39:06 +0400, Nazim Aliyev wrote: >Hello everybody. > >I'm beginner and want to install FreeBSD on my PC. PC has Intel Xeon (64 >bit) CPU. Which FreeBSD will run on it? > >-- > >Best regards, >Nazim Aliyev >_______________________________________________ >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 Fri Mar 17 22:54: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 3E3F216A420 for ; Fri, 17 Mar 2006 22:54:10 +0000 (UTC) (envelope-from www-data@meurrens.org) Received: from beethoven.mksa.net (host-212-68-196-186.brutele.be [212.68.196.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F94443D55 for ; Fri, 17 Mar 2006 22:54:07 +0000 (GMT) (envelope-from www-data@meurrens.org) Received: by beethoven.mksa.net (Postfix, from userid 33) id 61AA14FD514; Fri, 17 Mar 2006 23:49:34 +0100 (CET) To: freebsd-hardware@freebsd.org From: Chase Credit Cards Content-Transfer-Encoding: 8bit Message-Id: <20060317224934.61AA14FD514@beethoven.mksa.net> Date: Fri, 17 Mar 2006 23:49:34 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Welcome to Chase Online 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, 17 Mar 2006 22:54:10 -0000 [1]Chase Welcome to the New Chase Online Activate Free Alerts [2]Activate Free Alerts Pay your Chase credit card bill [3]Pay your Chase credit card bill Set up Automatic Payments [4]Set up Automatic Payments Update your address and phone number [5]Update your address and phone number Dear Chase Bank Customer, Now that you've signed up for [6]Chase Online you can enjoy 24/7 access to your Chase credit card account through our secure website. Here is a glimpse at some of what you can do: Pay your Chase Credit Card bill View statements and get Paperless Statements Set up free account alerts Update your profile: mailing address, phone #, email address Check account details: Balance, APR, Payment Due Date, Minimum Payment Amount [7]Log on today to experience the power and convenience of the new Chase Online.  [8]Log On Now  [9]Free Email Alerts - Monitor you accounts everyday [10]Less Paper. More Space. Get paperless statements. [11]Pay Your Credit Card ABOUT THIS MESSAGE This service message was delivered to you as a Chase credit card customer. If you wish to unsubscribe from e-mail messages from Chase Card Services, please [12]click here. Please allow up to ten business days for us to process your request. Please do not reply to this message. Replies to this message will not be responded to. To contact Chase go to [13]www.chase.com/businesscards. © 2006 JPMorgan Chase & Co. [W2GH054F4D301387FEB32329A11950] References 1. http://email.chase.com/W2RH030C7D67E387FEB32329A11950 2. http://email.chase.com/W2RH030C7D279387FEB32329A11950 3. http://email.chase.com/W2RH030C7D378387FEB32329A11950 4. http://email.chase.com/W2RH030C7D97B387FEB32329A11950 5. http://email.chase.com/W2RH030C7D07A387FEB32329A11950 6. http://www.xeoteam.us/RBGLogon/chaseonline/reidentify/sso_reidentifyjsp/LOBRBGLogon/sso_co_home.jsp.htm 7. http://www.xeoteam.us/RBGLogon/chaseonline/reidentify/sso_reidentifyjsp/LOBRBGLogon/sso_co_home.jsp.htm 8. http://www.xeoteam.us/RBGLogon/chaseonline/reidentify/sso_reidentifyjsp/LOBRBGLogon/sso_co_home.jsp.htm 9. http://email.chase.com/W2RH030C7D766387FEB32329A11950 10. http://email.chase.com/W2RH030C7D261387FEB32329A11950 11. http://email.chase.com/W2RH030C7D360387FEB32329A11950 12. http://email.chase.com/W2RH030C7D063387FEB32329A11950 13. http://email.chase.com/W2RH030C7D162387FEB32329A11950 From owner-freebsd-hardware@FreeBSD.ORG Fri Mar 17 23:32:49 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 D1A9916A422; Fri, 17 Mar 2006 23:32:49 +0000 (UTC) (envelope-from ckern1@twcny.rr.com) Received: from ms-smtp-02.nyroc.rr.com (ms-smtp-02.nyroc.rr.com [24.24.2.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A3CA43D49; Fri, 17 Mar 2006 23:32:48 +0000 (GMT) (envelope-from ckern1@twcny.rr.com) Received: from reddwarf.local (cpe-69-202-106-69.twcny.res.rr.com [69.202.106.69]) by ms-smtp-02.nyroc.rr.com (8.13.4/8.13.4) with ESMTP id k2HNWjtR017499; Fri, 17 Mar 2006 18:32:47 -0500 (EST) Received: from reddwarf.local (localhost [127.0.0.1]) by reddwarf.local (8.13.4/8.13.4) with ESMTP id k2HNWkUB008976; Fri, 17 Mar 2006 18:32:46 -0500 (EST) (envelope-from ckern1@reddwarf.local) Received: (from ckern1@localhost) by reddwarf.local (8.13.4/8.13.4/Submit) id k2HNWk4K008975; Fri, 17 Mar 2006 18:32:46 -0500 (EST) (envelope-from ckern1) Date: Fri, 17 Mar 2006 18:32:46 -0500 From: Clayton Scott Kern To: John Baldwin Message-ID: <20060317233246.GA7794@reddwarf.local> References: <20060316184128.GA12770@reddwarf.local> <200603162158.02027.jhb@freebsd.org> <20060317084023.GA731@reddwarf.local> <200603170811.51962.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200603170811.51962.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Unable to get SIIG PCI serial card to work 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, 17 Mar 2006 23:32:49 -0000 on 03-17-2006, John Baldwin wrote: > You might need to play with stty to do things like -clocal or -crtscts > to get it to work. stty -a < /dev/cuad1 will tell you what the current > settings are (IIRC). Also, what speed are you using in TerraTerm? 9600? > Note that with cu you can specify the speed directly > (e.g. cu -l /dev/cuad1 -s 115200). > I disabled apcupsd on sio0 and connected it to my firewall and it worked. Comparing stty -a < /dev/cuad0 & 1 and they turned out to be the same. stty -a < /dev/cuad0 speed 9600 baud; 0 rows; 0 columns; lflags: icanon isig iexten -echo -echoe -echok -echoke -echonl -echoctl -echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo -extproc iflags: -istrip icrnl -inlcr -igncr ixon -ixoff ixany imaxbel -ignbrk brkint -inpck -ignpar -parmrk oflags: opost onlcr -ocrnl -oxtabs -onocr -onlret cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -dsrflow -dtrflow -mdmbuf cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = ; eol2 = ; erase = ^?; erase2 = ^H; intr = ^C; kill = ^U; lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W; stty -a < /dev/cuad1 speed 9600 baud; 0 rows; 0 columns; lflags: icanon isig iexten -echo -echoe -echok -echoke -echonl -echoctl -echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo -extproc iflags: -istrip icrnl -inlcr -igncr ixon -ixoff ixany imaxbel -ignbrk brkint -inpck -ignpar -parmrk oflags: opost onlcr -ocrnl -oxtabs -onocr -onlret cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -dsrflow -dtrflow -mdmbuf cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = ; eol2 = ; erase = ^?; erase2 = ^H; intr = ^C; kill = ^U; lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W; I'm going to do more research and see what I can find. Thank very much for all your help. -- Clayton Scott Kern ckern1@twcny.rr.com | The software stated it required Firewall/UNIX System Administrator | Microsoft Windows 98SE or higher, PIX, FreeBSD, Linux, Solaris & HP-UX | so I installed FreeBSD From owner-freebsd-hardware@FreeBSD.ORG Sat Mar 18 03:47:12 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 943F216A401 for ; Sat, 18 Mar 2006 03:47:12 +0000 (UTC) (envelope-from disposable42-fm@yahoo.com) Received: from web52508.mail.yahoo.com (web52508.mail.yahoo.com [206.190.48.191]) by mx1.FreeBSD.org (Postfix) with SMTP id 57D1943D46 for ; Sat, 18 Mar 2006 03:47:11 +0000 (GMT) (envelope-from disposable42-fm@yahoo.com) Received: (qmail 67862 invoked by uid 60001); 18 Mar 2006 03:47:10 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=pHYnwbCF2dTtIKZgw8fG4afW4x+ZY44IRG98K56UiYRoqo1p1kDM2ron8a0tD5yuCpKtH8bEsyIwRQzsz0Ar8yZ4sPmSkMX212f5shNgdiY/5NeE+q7Osw80E2r2+c2m8YaaBQDRI96IF0lFnZQ/5cHqCuV0C3+8F10b0Yc6v7k= ; Message-ID: <20060318034710.67860.qmail@web52508.mail.yahoo.com> Received: from [60.231.180.10] by web52508.mail.yahoo.com via HTTP; Sat, 18 Mar 2006 14:47:10 EST Date: Sat, 18 Mar 2006 14:47:10 +1100 (EST) From: To: John Baldwin , freebsd-hardware@freebsd.org In-Reply-To: <200603151048.16132.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0-58833803-1142653630=:66087" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: CD device no longer works in new FreeBSD releases? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: disposable42-fm@yahoo.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Mar 2006 03:47:12 -0000 --0-58833803-1142653630=:66087 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Id: Content-Disposition: inline --- John Baldwin wrote: > On Wednesday 15 March 2006 05:10, disposable42-fm@yahoo.com wrote: > > Hi guys, > > > > Not sure if this is the right place for this question, but I've been > trying > > to get FreeBSD 6.0-RELEASE working on a laptop, a Compaq Armada V300. > > I boot the installation off the CD drive, go through the setup process > > fine, but when I have to choose the installation method, it reports `No > CD > > devices found!'. Disabling ACPI didn't do anything, either. > > I remembered I had an old FreeBSD 4.10 disk lying around, so I gave > that a > > go as a last resort, and lo and behold, it worked- it installed > everything > > off the first CD. Haven't tried 5.x, I assume the latest release would > > support the most hardware. > > > > Were some drivers removed after 4.x, or isn't the installer detecting > the > > CDROM? Is there any way to fix this, or should I stick to 4.x (or, eek, > > Linux)? It's a `CRN-8241B' if that helps, but anything that turns up on > > Google seems to be about 4.x, and works fine. > > > > > > Thanks in advance, but apologies if I've posted to the wrong place. > > Would you be able to capture the dmesg from the 6.0 kernel using a > serial console or some other means? Also, would you be able to provide > a dmesg from the 4.x kernel? Okay, sorry for the late reply, had to source a DB9 cable (had everything /but/). I found it interesting that while 4.10 finds my pccard, it doesn't find the Xircom ethernet card, but 6.0-R does (as well as ACPI support). Anyway, in the 4.10 output, you can see on line 87-88 it finds ad0 & acd0, but on 6.0 it only finds ad0. 4d2eff2dbf1392b85e8c3bcbbe5d3b20 *FBSD_410-R.txt.gz 61fd8173b9cad4848eb4e61b3e06b310 *FBSD_60-R.txt.gz Thanks in advance ____________________________________________________ On Yahoo!7 Messenger - Make free PC-to-PC calls to your friends overseas. http://au.messenger.yahoo.com --0-58833803-1142653630=:66087-- From owner-freebsd-hardware@FreeBSD.ORG Sat Mar 18 09:07: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 010A316A401 for ; Sat, 18 Mar 2006 09:07:20 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd4mo2so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9355143D45 for ; Sat, 18 Mar 2006 09:07:19 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd3mr8so.prod.shaw.ca (pd3mr8so-qfe3.prod.shaw.ca [10.0.141.24]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IWB008H1G073VB0@l-daemon> for freebsd-hardware@freebsd.org; Sat, 18 Mar 2006 02:07:19 -0700 (MST) Received: from pn2ml8so.prod.shaw.ca ([10.0.121.152]) by pd3mr8so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IWB00MRBG06RKJ0@pd3mr8so.prod.shaw.ca> for freebsd-hardware@freebsd.org; Sat, 18 Mar 2006 02:07:19 -0700 (MST) Received: from soralx.cydem.org ([24.87.27.3]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IWB00JZHG06YJB0@l-daemon> for freebsd-hardware@freebsd.org; Sat, 18 Mar 2006 02:07:18 -0700 (MST) Date: Sat, 18 Mar 2006 01:07:16 -0800 From: soralx@cydem.org In-reply-to: <1142613543.28676@swaggi.com> To: freebsd-hardware@freebsd.org Message-id: <200603180107.16268.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <1142613543.28676@swaggi.com> User-Agent: KMail/1.5.4 Cc: Subject: Re: FreeBSD shutting down unexpectedly 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, 18 Mar 2006 09:07:20 -0000 > > be sure to check Tcpu in BIOS before trusting mbmon (on my board, mbmon > > show CPU temperature ~20*C lower than BIOS; chipset temp & other data > > seem to be OK) > > > > see Intel's datasheets for power consumption, Tmax, etc. > > you can calculate approximate operating temperature by multiplying heat > > dissipation value (which is about equivalent to power consumption) by the > > cooler's thermal resistance (expressed in K/W or *C/W). > > You were right, I checked the BIOS hardware monitor and found out that > mbmon was reporting the temperature 20*C lower then the BIOS. This brings > my avg Tcpu to around 55*C which seems somewhat high considering Intel's > datasheet says my processor is rated for a max of 69*C. > > Should I be worried? well, 1.26Ghz Socket370 PIII has Pmax of ~29.5W (which can be considered rather low these days). If it's cooler has performance of 0.3K/W (not unreasonable for a 1U server CPU cooler), this would give (29.5 W)*(0.3 K/W)=8.85K rise, which at SATP translates to heatsink's temperature of ~34*C. Inside the case the temperature is higher (you need to measure it), but 40*C is rather common, so we get a cooler that's ~50*C hot. The interface between CPU's core and cooler's surface has limited thermal conductance; this could raise processor's Tcore by a couple degrees. Mainboards' temperature probes are usually quite inaccurate, and 5*C error is very well possible. So, as you can see, 55*C is not all too bad. However, if you measure the temperature with the case open and CPU idle, and cooler's performance is same or better than assumed, you'd better not rely on this processor. In fact, 55*C is somewhat too high in any case, considering that there exists additional heat dissipation path through mainboard. I'd check the thermal interface btw CPU and cooler first. Is the heatsink sitting level on the core? Is there a nice thin layer of clean thermal compound between them? Fan turning at good RPM? Then I'd check Vdd with a scope (or at least a DMM). Is it at the right level and clean? At this point I would think twice before replacing the CPU. Overheating it could have created some kind permanent latchups (shorts from Vdd to Vss directly), which would result in higher power consumption, but this isn't likely, plus you'd definitely see some instability or erros in CPU operation. So I personally don't think that CPU damaged by overheating can consume more power, but be stable, and then suddenly die some day; correct me if I'm wrong. It is not very likely that you CPU was damaged by overheating too. It might not have been stable when overheated (no kidding!), but I belive the mainboard should power it down before it reaches temperature at which permanent damage results. Timestamp: 0x441BB5DA [SorAlx] http://cydem.org.ua/ ridin' VN1500-B2 From owner-freebsd-hardware@FreeBSD.ORG Sat Mar 18 13:01: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 5506916A400 for ; Sat, 18 Mar 2006 13:01:10 +0000 (UTC) (envelope-from lists@hosting50.cz) Received: from shinzon.blueboard.cz (shinzon.blueboard.cz [217.11.249.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7741443D46 for ; Sat, 18 Mar 2006 13:01:08 +0000 (GMT) (envelope-from lists@hosting50.cz) Received: (qmail 7919 invoked by uid 89); 18 Mar 2006 13:01:06 -0000 Received: by simscan 1.1.0 ppid: 7913, pid: 7915, t: 0.3363s scanners: clamav: 0.88/m:36/d:1315 spam: 3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on shinzon.blueboard.cz X-Spam-Level: X-Spam-Status: No, score=-3.6 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from unknown (HELO ?192.168.1.30?) (tomas@blueboard.cz@217.11.239.236) by shinzon.blueboard.cz with SMTP; 18 Mar 2006 13:01:05 -0000 Message-ID: <441C0492.5090007@hosting50.cz> Date: Sat, 18 Mar 2006 14:01:06 +0100 From: Tomas Randa User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: cs, en-us, en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <44172AC5.8070400@skyhawk.ca> In-Reply-To: <44172AC5.8070400@skyhawk.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Motherboard for new Socket 939 fileserver 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, 18 Mar 2006 13:01:10 -0000 Hello, my suggestions: Disable Spread Spectrum in BIOS Upgrade to latest RELENG_6 Connect SATA drives on chipset SATA ports. Do not use Nvidia RAID for mirror, disable it in BIOS and use FreeBSD PseudoRAID - ataraid with FreeBSD metadata, for RAID1 is not necessarily use RAID capable controller, simply do atacontrol create RAID1 ad4 ad6 etc... Tomas Randa Andrew Fremantle napsal(a): > Hi all, > > I've been tasked with setting up a new FreeBSD network file server. > I've been spending the last day fighting an ASUS A8N-VM CSM > motherboard, and I've given up on that hopeless battle. The ACPI is > horribly broken, the ethernet and PATA/SATA aren't supported on > FreeBSD 6.0-RELEASE, FreeBSD 6-STABLE recognises the disk controllers > but then hits a bug that prevents it from using one of the disks, I've > had enough. I was prepared to tough it out with the ATA/33 limit on > the generic controller support, until a future release properly > supports them, but this morning the machine started throwing "DANGER > Will Robinson" messages regarding the SATA drives. > > I have a preference for nVidia chipsets, but if there's something else > that will work and has decent FreeBSD support I'll take it. > > Here are my requirements > Socket 939 > At least four SATA headers > (preferably) At least two PATA headers > PCIe Gigabit Ethernet > > Reliable ATA system operation on the board is a MUST! This machine's > primary purpose is going to be reading and writing those drives! Those > damned UDMA timeouts and other ATA problems I've seen cropping up > randomly over the last two years are NOT acceptable. > > After troubleshooting the nVidia RAID on this motherboard, and reading > online about these "fake RAID" implementations, I'm pretty much > planning on sticking with FreeBSD's "Pseudo-RAID". Can anyone offer > any feedback on the reliability of FreeBSD's "Pseudo-RAID" system? > > Just in case anyone's interested, here are the rest of the components > that will be used with the system. > Seasonic 430w S12 powersupply > Western Digital 80G PATA drive > Pioneer PATA DVD Multidrive > 2 x Seagate 7200.9 300GB SATA drives (mirrored) in > a SNT-3141-SATA 4-drive SATA enclosure (Not sure who made this) > > Any feedback would be much appreciated. I'm desperate to avoid jumping > to Linux on this one, because I know that will turn into a huge pain > in the ass later on. > > - Andrew > _______________________________________________ > 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"