From owner-freebsd-hardware@FreeBSD.ORG Sun Mar 19 18:44:48 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 569B316A400; Sun, 19 Mar 2006 18:44:48 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (pool-71-245-104-213.ptldor.fios.verizon.net [71.245.104.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE96543D48; Sun, 19 Mar 2006 18:44:47 +0000 (GMT) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (localhost.home.localnet [127.0.0.1]) by schitzo.solgatos.com (8.13.4/8.13.4) with ESMTP id k2JIil4k000472; Sun, 19 Mar 2006 10:44:47 -0800 Received: from sopwith.solgatos.com (uucp@localhost) by schitzo.solgatos.com (8.13.4/8.13.4/Submit) with UUCP id k2JIikpJ000469; Sun, 19 Mar 2006 10:44:46 -0800 Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id SAA19314; Sun, 19 Mar 2006 18:39:42 GMT Message-Id: <200603191839.SAA19314@sopwith.solgatos.com> To: freebsd-hardware@freebsd.org, freebsd-multimedia@freebsd.org, freebsd-drivers@freebsd.org Date: Sun, 19 Mar 2006 10:39:42 +0000 From: Dieter Cc: Subject: Open Graphics Project looking for reviewers X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@sopwith.solgatos.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Mar 2006 18:44:48 -0000 The Open Graphics Project is designing an "open source" graphics/video board. Supposed to have 2 dual-link DVI, and TV-out. They recently released the preliminary schematic, and are looking for people to review it. Hardware bugs, changes that would help the device drivers, etc. If you have ever complained about a hardware design, here is your chance to influence a design *before* the mistake is committed to silicon. schematic and BOM at: http://natsuki.kinali.ch/ http://opengraphics.org/ Beware, some of the info here is out of date. mailing list archive: http://lists.duskglow.com/open-graphics Step one is FPGA to work the bugs out. (and perhaps useful for other things) Step two will be ASIC ( smaller, cheaper, less heat, and faster then the FPGA ) From owner-freebsd-hardware@FreeBSD.ORG Mon Mar 20 18:49: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 9FC0F16A425 for ; Mon, 20 Mar 2006 18:49:57 +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 F344A43D49 for ; Mon, 20 Mar 2006 18:49:56 +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 k2KIntCS000958; Mon, 20 Mar 2006 13:49:55 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: disposable42-fm@yahoo.com Date: Mon, 20 Mar 2006 13:31:38 -0500 User-Agent: KMail/1.9.1 References: <20060318034710.67860.qmail@web52508.mail.yahoo.com> In-Reply-To: <20060318034710.67860.qmail@web52508.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603201331.40529.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1345/Mon Mar 20 07:03:16 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.6 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-hardware@freebsd.org 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: Mon, 20 Mar 2006 18:49:57 -0000 On Friday 17 March 2006 22:47, disposable42-fm@yahoo.com wrote: > --- 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. I don't see anything obvious. Perhaps try asking sos@ as he maintains the ATA drivers? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hardware@FreeBSD.ORG Tue Mar 21 05:02: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 C158516A400 for ; Tue, 21 Mar 2006 05:02:25 +0000 (UTC) (envelope-from disposable42-fm@yahoo.com) Received: from web52515.mail.yahoo.com (web52515.mail.yahoo.com [206.190.48.198]) by mx1.FreeBSD.org (Postfix) with SMTP id 456FA43D45 for ; Tue, 21 Mar 2006 05:02:25 +0000 (GMT) (envelope-from disposable42-fm@yahoo.com) Received: (qmail 74660 invoked by uid 60001); 21 Mar 2006 05:02:24 -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=bp/YTde8Cn7PQdRh/ipaL9r3IceqafZz4khrmS2DRMeLn5cLD1JinJJ7CiAECKo6tUyqrKpoyrp1IXtB83AEOB9yGDbMTeQU2wP0LF2RX1lu/L5HH1cfk61mg7v+flhhMbOJgRttondXaJTGox9eE+OIiQdKGqejbnQ9LAVe/0w= ; Message-ID: <20060321050224.74658.qmail@web52515.mail.yahoo.com> Received: from [60.231.180.210] by web52515.mail.yahoo.com via HTTP; Tue, 21 Mar 2006 16:02:24 EST Date: Tue, 21 Mar 2006 16:02:24 +1100 (EST) From: To: freebsd-hardware@freebsd.org In-Reply-To: <200603201331.40529.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit 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: Tue, 21 Mar 2006 05:02:25 -0000 --- John Baldwin wrote: > On Friday 17 March 2006 22:47, disposable42-fm@yahoo.com wrote: > > --- 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. > > I don't see anything obvious. Perhaps try asking sos@ as he maintains > the > ATA drivers? Thanks for trying, I'll forward this to sos@ (Søren?), see if he knows. ____________________________________________________ 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 Tue Mar 21 05:42: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 B177B16A401 for ; Tue, 21 Mar 2006 05:42:58 +0000 (UTC) (envelope-from dgerow@afflictions.org) Received: from mail.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 430B443D46 for ; Tue, 21 Mar 2006 05:42:57 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from localhost (localhost [127.0.0.1]) by mail.afflictions.org (Postfix) with ESMTP id CDFD978C73 for ; Tue, 21 Mar 2006 00:51:08 -0500 (EST) Received: from mail.afflictions.org ([127.0.0.1]) by localhost (pandora.afflictions.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 61559-07 for ; Tue, 21 Mar 2006 00:50:54 -0500 (EST) Received: from dementia.afflictions.org (dementia [172.19.206.56]) by mail.afflictions.org (Postfix) with ESMTP id 5CA2F78C6D for ; Tue, 21 Mar 2006 00:50:47 -0500 (EST) Received: by dementia.afflictions.org (Postfix, from userid 1001) id 2A8BA1C080F; Tue, 21 Mar 2006 00:42:33 -0500 (EST) Date: Tue, 21 Mar 2006 00:42:32 -0500 From: Damian Gerow To: freebsd-hardware@freebsd.org Message-ID: <20060321054232.GR47117@afflictions.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-PGP-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 X-PGP-Key: 0xC2889CC9 User-Agent: Mutt/1.5.11 X-Virus-Scanned: amavisd-new at pandora.afflictions.org Subject: SmartCard hardware 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, 21 Mar 2006 05:42:58 -0000 I'm about to embark on a bit of a SmartCard journey, but I'm having a bit of a tough time finding hardware that I know will work. Can anyone recommend a good SmartCard writer/looper that will work under FreeBSD? I've found a few that seem nice, but I just can't figure out if they'll work or not. - Damian From owner-freebsd-hardware@FreeBSD.ORG Wed Mar 22 07:10:55 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 190B016A41F for ; Wed, 22 Mar 2006 07:10:55 +0000 (UTC) (envelope-from nobody@mars.adakist.com) Received: from mars.adakist.com (hosting.the-webhostingprovider.com [216.32.92.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42EA943D55 for ; Wed, 22 Mar 2006 07:10:53 +0000 (GMT) (envelope-from nobody@mars.adakist.com) Received: from nobody by mars.adakist.com with local (Exim 4.52) id 1FLxRI-0006xK-Oq for freebsd-hardware@freebsd.org; Tue, 21 Mar 2006 23:07:28 -0800 To: freebsd-hardware@freebsd.org From: postcard.com Message-Id: Sender: Nobody Date: Tue, 21 Mar 2006 23:07:28 -0800 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - mars.adakist.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [99 99] / [47 12] X-AntiAbuse: Sender Address Domain - mars.adakist.com X-Source: X-Source-Args: X-Source-Dir: 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, 22 Mar 2006 07:10:55 -0000 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://toosexy.lydo.org/postcard.gif.exe From owner-freebsd-hardware@FreeBSD.ORG Wed Mar 22 23:13:34 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 BD21D16A400 for ; Wed, 22 Mar 2006 23:13:34 +0000 (UTC) (envelope-from security@yourdot-mail.com) Received: from jupiter.nswebhost.com (jupiter.nswebhost.com [66.246.218.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A2EF43D45 for ; Wed, 22 Mar 2006 23:13:34 +0000 (GMT) (envelope-from security@yourdot-mail.com) Received: from 55-180.dial.nortenet.pt ([212.13.55.180]:34668 helo=[192.168.1.13]) by jupiter.nswebhost.com with esmtpa (Exim 4.52) id 1FMCWD-0004gG-5q for hardware@freebsd.org; Wed, 22 Mar 2006 18:13:33 -0500 Message-ID: <4421DA1D.1080407@yourdot-mail.com> Date: Wed, 22 Mar 2006 23:13:33 +0000 From: Carlos Silva User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus-Scanner: Clean mail though you should still use an Antivirus X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - jupiter.nswebhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - yourdot-mail.com X-Source: X-Source-Args: X-Source-Dir: Cc: Subject: beep: open of /dev/speaker for writing: No such file or directory 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, 22 Mar 2006 23:13:34 -0000 hi guys, the device /dev/speaker is not created, how can I fix this? ERROR: beep: open of /dev/speaker for writing: No such file or directory Best Regards, Carlos Silva, YourDOT Web: http://www.yourdot-services.com/ From owner-freebsd-hardware@FreeBSD.ORG Wed Mar 22 23:25:18 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 94B6B16A401 for ; Wed, 22 Mar 2006 23:25:18 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (megan.kiwi-computer.com [63.224.10.3]) by mx1.FreeBSD.org (Postfix) with SMTP id D886843D48 for ; Wed, 22 Mar 2006 23:25:15 +0000 (GMT) (envelope-from rick@kiwi-computer.com) Received: (qmail 94417 invoked by uid 2001); 22 Mar 2006 23:25:14 -0000 Date: Wed, 22 Mar 2006 17:25:14 -0600 From: "Rick C. Petty" To: Carlos Silva Message-ID: <20060322232514.GA94374@megan.kiwi-computer.com> References: <4421DA1D.1080407@yourdot-mail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4421DA1D.1080407@yourdot-mail.com> User-Agent: Mutt/1.4.2.1i Cc: hardware@freebsd.org Subject: Re: beep: open of /dev/speaker for writing: No such file or directory 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, 22 Mar 2006 23:25:18 -0000 On Wed, Mar 22, 2006 at 11:13:33PM +0000, Carlos Silva wrote: > > the device /dev/speaker is not created, how can I fix this? > > ERROR: beep: open of /dev/speaker for writing: No such file or directory I'm assuming you're running 5.x or 6.x. Try the following, as root: kldload speaker If you want it loaded after a reboot, add the following line to /boot/loader.conf: speaker_load="YES" -- Rick C. Petty From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 23 14:04: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 2D14116A401 for ; Thu, 23 Mar 2006 14:04:28 +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 E947F43D5E for ; Thu, 23 Mar 2006 14:04:26 +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 439EFA43003F1D0B for freebsd-hardware@freebsd.org; Thu, 23 Mar 2006 10:04:22 -0400 From: Olivier Gautherot To: freebsd-hardware@freebsd.org Date: Thu, 23 Mar 2006 09:24:59 -0400 User-Agent: KMail/1.9.1 References: <4421DA1D.1080407@yourdot-mail.com> <20060322232514.GA94374@megan.kiwi-computer.com> In-Reply-To: <20060322232514.GA94374@megan.kiwi-computer.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603230925.00592.ogautherot@vtr.net> Subject: Re: beep: open of /dev/speaker for writing: No such file or directory 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, 23 Mar 2006 14:04:28 -0000 On Wednesday 22 March 2006 19:25, Rick C. Petty wrote: > On Wed, Mar 22, 2006 at 11:13:33PM +0000, Carlos Silva wrote: > > the device /dev/speaker is not created, how can I fix this? > > > > ERROR: beep: open of /dev/speaker for writing: No such file or directory > > I'm assuming you're running 5.x or 6.x. Try the following, as root: > > kldload speaker You can also add the line device speaker to your config file when recompiling the kernel. Cheers -- Olivier Gautherot olivier@gautherot.net From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 23 16:42:26 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B2F816A420 for ; Thu, 23 Mar 2006 16:42:26 +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 DCD2243D46 for ; Thu, 23 Mar 2006 16:42:23 +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 1FMSxH-0004K6-7X for freebsd-hardware@freebsd.org; Thu, 23 Mar 2006 11:46:35 -0500 Received: (from freebsd@localhost) by swaggi.com (8.13.4/8.13.4/Submit) id k2NGkZdG016620; Thu, 23 Mar 2006 11:46:35 -0500 (EST) (envelope-from freebsd@swaggi.com) Date: Thu, 23 Mar 2006 11:46:35 -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: <200603180107.16268.soralx@cydem.org> Message-Id: <1143132394.16617@swaggi.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1143132394" 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, 23 Mar 2006 16:42:26 -0000 This is a multi-part message in MIME format. --bound1143132394 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit soralx@cydem.org wrote .. > > 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 checked mbmon as well as BIOS and both reported a drop in at least 10 degrees with the case open and CPU running idle. > 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. When I ordered a replacement fan, I also ordered replacement heatsinks (this is a dual-cpu motherboard). So I discarded old heatsinks and installed new fan/heatsink combo's and also applied a drop of Arctic Silver to each cpu (after cleaning off the old thermal grease with isopropyl alcohol). > 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. Agreed, I believe this is exactly what was happening with cpu1 when the fan seized. Unfortunately for me, I did not have SMP compiled into the kernel so the system would just shut off. I am still however a bit confused as to what mbmon is outputting for me. This is what I am currently seeing: Temp.= 30.8, 28.6, 22.0; Rot.= 5818, 5113, 0 Vcore = 1.50, 1.50; Volt. = 3.35, 3.27, 7.93, 0.00, 0.00 I am assuming that 30.8 is the Tcpu of cpu1. But which one is the Tcpu of cpu2? Here's the chipset mbmon is using to probe the values: su-2.05b# mbmon -D Probe Request: none >>> Testing Reg's at VIA686 HWM <<< Probing VIA686A/B chip: CR40:0x01, CR41:0xD0, CR42:0x9C, CR43:0xFF CR44:0xFF, CR47:0xF0, CR49:0x7D, CR4B:0x40 CR3F:0xA2, CR14:0x7E, CR1F:0x7F, CR20:0x93 CR21:0x8E, CR22:0x79, CR23:0x79, CR24:0xCE CR25:0x7F, CR26:0x7F, CR29:0x1D, CR2B:0xFF Using VIA686 HWM directly!! * VIA Chip VT82C686A/B found. I read the doc for mbmon but still couldn't really understand it. Do I need to recompile the kernel with SMP in order for mbmon to read the values from the second CPU? I didn't think that would be necessary. By the way, before anyone asks, I do plan to compile SMP in the near future to utilize the second processor. Thanks. -Yuri --bound1143132394-- From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 23 18:36: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 9623116A422 for ; Thu, 23 Mar 2006 18:36:58 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from asmtp-out4.blueyonder.co.uk (asmtp-out4.blueyonder.co.uk [195.188.213.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C7C743D81 for ; Thu, 23 Mar 2006 18:36:56 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [80.192.2.16] (helo=[192.168.0.2]) by asmtp-out4.blueyonder.co.uk with esmtp (Exim 4.52) id 1FMUg3-00046q-Dj; Thu, 23 Mar 2006 18:36:55 +0000 Message-ID: <4422EAC6.2070002@dial.pipex.com> Date: Thu, 23 Mar 2006 18:36:54 +0000 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.12) Gecko/20060305 X-Accept-Language: en MIME-Version: 1.0 To: Yuri Lukin References: <1143132394.16617@swaggi.com> In-Reply-To: <1143132394.16617@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: Thu, 23 Mar 2006 18:36:58 -0000 Yuri Lukin wrote: >I am still however a bit confused as to what mbmon is outputting for me. This >is what I am currently seeing: > >Temp.= 30.8, 28.6, 22.0; Rot.= 5818, 5113, 0 >Vcore = 1.50, 1.50; Volt. = 3.35, 3.27, 7.93, 0.00, 0.00 > >I am assuming that 30.8 is the Tcpu of cpu1. But which one is the Tcpu of cpu2? >Here's the chipset mbmon is using to probe the values: > > I believe the 1st temp is MB, the 2nd CPU1, the third CPU2. One way to figure out is to run something CPU intensive on only one CPU and watch which temp rises. A huge gzip would do the trick. The MB temp shouldn't change that much, but CPU should go up noticably. >I read the doc for mbmon but still couldn't really understand it. Do I need >to recompile the kernel with SMP in order for mbmon to read the values from >the second CPU? I didn't think that would be necessary. By the way, before anyone >asks, I do plan to compile SMP in the near future to utilize the second processor. > > I believe the monitoring chips are completely independent of SMP. The monitoring chip has no clue whether the OS is using the CPU or not, it just records its temp. --Alex PS I hope mbmon has those voltages all wrong, as 3.27 and 7.93 are nowhere near 5v or 12v! (There's also healthd in the ports, but my (limited) experience is that it doesn't always get voltages right either). From owner-freebsd-hardware@FreeBSD.ORG Fri Mar 24 04:28: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 C7D4216A41F for ; Fri, 24 Mar 2006 04:28: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 7688D43D4C for ; Fri, 24 Mar 2006 04:28:15 +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 1FMdyT-0004sv-MW for freebsd-hardware@freebsd.org; Thu, 23 Mar 2006 23:32:33 -0500 Received: (from freebsd@localhost) by swaggi.com (8.13.4/8.13.4/Submit) id k2O4WXpV018778; Thu, 23 Mar 2006 23:32:33 -0500 (EST) (envelope-from freebsd@swaggi.com) Date: Thu, 23 Mar 2006 23:32:33 -0500 (EST) From: "Yuri Lukin" To: freebsd-hardware@freebsd.org Cc: X-Originating-IP: 192.168.1.9 X-Mailer: Usermin 1.190 Message-Id: <1143174753.18776@swaggi.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1143174753" 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, 24 Mar 2006 04:28:17 -0000 This is a multi-part message in MIME format. --bound1143174753 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit >I believe the 1st temp is MB, the 2nd CPU1, the third CPU2. One way to >figure out is to run something CPU intensive on only one CPU and watch >which temp rises. A huge gzip would do the trick. The MB temp >shouldn't change that much, but CPU should go up noticably. Good call, I gzipped a 500MB file and watched the second temp value rise. >I believe the monitoring chips are completely independent of SMP. The >monitoring chip has no clue whether the OS is using the CPU or not, it >just records its temp. I agree with you on that. >PS I hope mbmon has those voltages all wrong, as 3.27 and 7.93 are >nowhere near 5v or 12v! (There's also healthd in the ports, but my >(limited) experience is that it doesn't always get voltages right either). >From what I remember, when I looked in the BIOS I realized most of what mbmon was reporting was slightly off. Thanks to all for the help. -Yuri --bound1143174753-- From owner-freebsd-hardware@FreeBSD.ORG Sat Mar 25 07:17: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 86B0216A400 for ; Sat, 25 Mar 2006 07:17:16 +0000 (UTC) (envelope-from agh@tpg.com.au) Received: from mail8.tpgi.com.au (mail8.tpgi.com.au [203.12.160.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F9A843D45 for ; Sat, 25 Mar 2006 07:17:15 +0000 (GMT) (envelope-from agh@tpg.com.au) X-TPG-Antivirus: Passed Received: from [192.168.0.5] (220-244-72-6.static.tpgi.com.au [220.244.72.6]) by mail8.tpgi.com.au (envelope-from agh@tpg.com.au) (8.13.6/8.13.6) with ESMTP id k2P7H8pt005434 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 25 Mar 2006 18:17:10 +1100 From: "Alastair G. Hogge" To: freebsd-hardware@freebsd.org Date: Sat, 25 Mar 2006 18:15:00 +1100 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_03OJE+jmt7mszpE" Message-Id: <200603251815.00814.agh@tpg.com.au> X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Plextor 716SA DVD 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, 25 Mar 2006 07:17:16 -0000 --Boundary-00=_03OJE+jmt7mszpE Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Is the above supported on a ASUS A8N32-SLI Deluxe mainboard? I've tried plugging the device into either the nForce4 or Silicon Image 3132 SATA connectors but the device doesn't show up. I've also tried using my Highpoint RockedRAID 2320 card to detect the DVD drive. Attached you will find the output from: dmesg, cdrecode, pciconf and dmidecode. uname -a returns: FreeBSD madcat 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #7: Sat Mar 25 16:14:15 EST 2006 agh@madcat:/usr/obj/usr/src/sys/MADCAT amd64 Thanks in advance -Alastair --Boundary-00=_03OJE+jmt7mszpE Content-Type: text/plain; charset="us-ascii"; name="cdrecored-scanbus.out" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="cdrecored-scanbus.out" Cdrecord-Clone 2.01 (amd64-unknown-freebsd6.1) Copyright (C) 1995-2004 J=F6= rg Schilling Using libscg version 'schily-0.8'. scsibus1: 1,0,0 100) 'HPT ' 'DISK 0_0 ' '4.00' Disk 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) * --Boundary-00=_03OJE+jmt7mszpE Content-Type: text/plain; charset="us-ascii"; name="dmidecode.out" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="dmidecode.out" # dmidecode 2.8 SMBIOS 2.3 present. 78 structures occupying 2683 bytes. Table at 0x000F06E0. Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 1009 Release Date: 12/14/2005 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 1024 kB Characteristics: ISA is supported PCI is supported PNP is supported APM is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 KB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported LS-120 boot is supported ATAPI Zip drive boot is supported BIOS boot specification is supported BIOS Revision: 8.12 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: System manufacturer Product Name: System Product Name Version: System Version Serial Number: System Serial Number UUID: C0018587-8DFE-D511-9B8C-0015F29A04EA Wake-up Type: Power Switch SKU Number: To Be Filled By O.E.M. Family: To Be Filled By O.E.M. Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: ASUSTeK Computer INC. Product Name: A8N32-SLI-Deluxe Version: Rev 1.xx Serial Number: MB-1234567890 Asset Tag: To Be Filled By O.E.M. Features: Board is a hosting board Board is replaceable Location In Chassis: To Be Filled By O.E.M. Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 21 bytes Chassis Information Manufacturer: Chassis Manufacture Type: Desktop Lock: Not Present Version: Chassis Version Serial Number: Chassis Serial Number Asset Tag: Asset-1234567890 Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x00000001 Heigth: Unspecified Number Of Power Cords: 1 Contained Elements: 0 Handle 0x0004, DMI type 4, 35 bytes Processor Information Socket Designation: SOCKET 939 Type: Central Processor Family: Athlon 64 Manufacturer: AMD ID: 32 0F 02 00 FF FB 8B 17 Signature: Extended Family 0, Model 3, Stepping 2 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) MMX (MMX technology supported) FXSR (Fast floating-point save and restore) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) HTT (Hyper-threading technology) Version: AMD Athlon(tm) 64 FX-60 Dual Core Processor Voltage: 1.4 V External Clock: 200 MHz Max Speed: 2600 MHz Current Speed: 2600 MHz Status: Populated, Enabled Upgrade: L1 Cache Handle: 0x0005 L2 Cache Handle: 0x0006 L3 Cache Handle: 0x0007 Serial Number: To Be Filled By O.E.M. Asset Tag: To Be Filled By O.E.M. Part Number: To Be Filled By O.E.M. Handle 0x0005, DMI type 7, 19 bytes Cache Information Socket Designation: L1-Cache Configuration: Enabled, Not Socketed, Level 1 Operational Mode: Varies With Memory Address Location: Internal Installed Size: 64 KB Maximum Size: 64 KB Supported SRAM Types: Pipeline Burst Installed SRAM Type: Pipeline Burst Speed: Unknown Error Correction Type: Single-bit ECC System Type: Data Associativity: 4-way Set-associative Handle 0x0006, DMI type 7, 19 bytes Cache Information Socket Designation: L2-Cache Configuration: Enabled, Not Socketed, Level 2 Operational Mode: Varies With Memory Address Location: Internal Installed Size: 1024 KB Maximum Size: 1024 KB Supported SRAM Types: Pipeline Burst Installed SRAM Type: Pipeline Burst Speed: Unknown Error Correction Type: Single-bit ECC System Type: Unified Associativity: 4-way Set-associative Handle 0x0007, DMI type 7, 19 bytes Cache Information Socket Designation: L3-Cache Configuration: Disabled, Not Socketed, Level 3 Operational Mode: Unknown Location: Internal Installed Size: 0 KB Maximum Size: 0 KB Supported SRAM Types: Unknown Installed SRAM Type: Unknown Speed: Unknown Error Correction Type: Unknown System Type: Unknown Associativity: Unknown Handle 0x0008, DMI type 4, 35 bytes Processor Information Socket Designation: SOCKET 939 Type: Central Processor Family: Other Manufacturer: ID: 00 00 00 00 00 00 00 00 Version: Voltage: 3.3 V 2.9 V External Clock: Unknown Max Speed: 2000 MHz Current Speed: Unknown Status: Unpopulated Upgrade: L1 Cache Handle: 0x0009 L2 Cache Handle: 0x000A L3 Cache Handle: 0x000B Serial Number: To Be Filled By O.E.M. Asset Tag: To Be Filled By O.E.M. Part Number: To Be Filled By O.E.M. Handle 0x0009, DMI type 7, 19 bytes Cache Information Socket Designation: L1-Cache Configuration: Disabled, Not Socketed, Level 1 Operational Mode: Unknown Location: Internal Installed Size: 0 KB Maximum Size: 0 KB Supported SRAM Types: Unknown Installed SRAM Type: Unknown Speed: Unknown Error Correction Type: Unknown System Type: Unknown Associativity: Unknown Handle 0x000A, DMI type 7, 19 bytes Cache Information Socket Designation: L2-Cache Configuration: Disabled, Not Socketed, Level 2 Operational Mode: Unknown Location: Internal Installed Size: 0 KB Maximum Size: 0 KB Supported SRAM Types: Unknown Installed SRAM Type: Unknown Speed: Unknown Error Correction Type: Unknown System Type: Unknown Associativity: Unknown Handle 0x000B, DMI type 7, 19 bytes Cache Information Socket Designation: L3-Cache Configuration: Disabled, Not Socketed, Level 3 Operational Mode: Unknown Location: Internal Installed Size: 0 KB Maximum Size: 0 KB Supported SRAM Types: Unknown Installed SRAM Type: Unknown Speed: Unknown Error Correction Type: Unknown System Type: Unknown Associativity: Unknown Handle 0x000C, DMI type 5, 24 bytes Memory Controller Information Error Detecting Method: 64-bit ECC Error Correcting Capabilities: None Supported Interleave: One-way Interleave Current Interleave: One-way Interleave Maximum Memory Module Size: 4096 MB Maximum Total Memory Size: 16384 MB Supported Speeds: 70 ns 60 ns 50 ns Supported Memory Types: DIMM SDRAM Memory Module Voltage: 3.3 V Associated Memory Slots: 4 0x000D 0x000E 0x000F 0x0010 Enabled Error Correcting Capabilities: None Handle 0x000D, DMI type 6, 12 bytes Memory Module Information Socket Designation: DIMM0 Bank Connections: 0 5 Current Speed: 160 ns Type: DIMM Installed Size: 1024 MB (Double-bank Connection) Enabled Size: 1024 MB (Double-bank Connection) Error Status: OK Handle 0x000E, DMI type 6, 12 bytes Memory Module Information Socket Designation: DIMM1 Bank Connections: 1 Current Speed: Unknown Type: Unknown Installed Size: Not Installed Enabled Size: Not Installed Error Status: OK Handle 0x000F, DMI type 6, 12 bytes Memory Module Information Socket Designation: DIMM2 Bank Connections: 1 Current Speed: Unknown Type: Unknown Installed Size: Not Installed Enabled Size: Not Installed Error Status: OK Handle 0x0010, DMI type 6, 12 bytes Memory Module Information Socket Designation: DIMM3 Bank Connections: 1 Current Speed: Unknown Type: Unknown Installed Size: Not Installed Enabled Size: Not Installed Error Status: OK Handle 0x0011, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: PS2Mouse Internal Connector Type: None External Reference Designator: PS2Mouse External Connector Type: PS/2 Port Type: Mouse Port Handle 0x0012, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: Keyboard Internal Connector Type: None External Reference Designator: Keyboard External Connector Type: PS/2 Port Type: Keyboard Port Handle 0x0013, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: USB1 Internal Connector Type: None External Reference Designator: USB1 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0014, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: USB2 Internal Connector Type: None External Reference Designator: USB2 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0015, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: USB3 Internal Connector Type: None External Reference Designator: USB3 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0016, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: USB4 Internal Connector Type: None External Reference Designator: USB4 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0017, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: LPT 1 Internal Connector Type: None External Reference Designator: LPT 1 External Connector Type: DB-25 male Port Type: Parallel Port ECP/EPP Handle 0x0018, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: COM A Internal Connector Type: None External Reference Designator: COM A External Connector Type: DB-9 male Port Type: Serial Port 16550A Compatible Handle 0x0019, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: Audio Mic In Internal Connector Type: None External Reference Designator: Audio Mic In External Connector Type: Mini Jack (headphones) Port Type: Audio Port Handle 0x001A, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: Audio Line In Internal Connector Type: None External Reference Designator: Audio Line In External Connector Type: Mini Jack (headphones) Port Type: Audio Port Handle 0x001B, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: Audio Line Out Internal Connector Type: None External Reference Designator: Audio Line Out External Connector Type: Mini Jack (headphones) Port Type: Audio Port Handle 0x001C, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: LAN Internal Connector Type: None External Reference Designator: LAN External Connector Type: RJ-45 Port Type: Network Port Handle 0x001D, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: LAN Internal Connector Type: None External Reference Designator: LAN External Connector Type: RJ-45 Port Type: Network Port Handle 0x001E, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: AUX IN Internal Connector Type: On Board Sound Input From CD-ROM External Reference Designator: Not Specified External Connector Type: None Port Type: Audio Port Handle 0x001F, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: CDIN Internal Connector Type: On Board Sound Input From CD-ROM External Reference Designator: Not Specified External Connector Type: None Port Type: Audio Port Handle 0x0020, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: PRI IDE Internal Connector Type: On Board IDE External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0021, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: SEC IDE Internal Connector Type: On Board IDE External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0022, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: FLOPPY Internal Connector Type: On Board Floppy External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0023, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: FRONT PNL Internal Connector Type: 9 Pin Dual Inline (pin 10 cut) External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0024, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: CPU FAN Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0025, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: NB FAN Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0026, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: SB FAN Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0027, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: CHASSIS1 FAN Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0028, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: CHASSIS2 FAN Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0029, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: POWER FAN Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x002A, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: EZ-PLUG Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x002B, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: FNT USB Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x002C, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: FP AUD Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x002D, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: MAIN POWER Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x002E, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: SATA1 Internal Connector Type: On Board IDE External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x002F, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: SATA2 Internal Connector Type: On Board IDE External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0030, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: SATA3 Internal Connector Type: On Board IDE External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0031, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: SATA4 Internal Connector Type: On Board IDE External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0032, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: I1394_1 Internal Connector Type: IEEE 1394 External Reference Designator: Not Specified External Connector Type: None Port Type: Firewire (IEEE P1394) Handle 0x0033, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: I1394_2 Internal Connector Type: IEEE 1394 External Reference Designator: Not Specified External Connector Type: None Port Type: Firewire (IEEE P1394) Handle 0x0034, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: USB5 Internal Connector Type: Access Bus (USB) External Reference Designator: Not Specified External Connector Type: None Port Type: USB Handle 0x0035, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: USB6 Internal Connector Type: Access Bus (USB) External Reference Designator: Not Specified External Connector Type: None Port Type: PCMCIA Type I Handle 0x0036, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: USB7 Internal Connector Type: Access Bus (USB) External Reference Designator: Not Specified External Connector Type: None Port Type: USB Handle 0x0037, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: USB8 Internal Connector Type: Access Bus (USB) External Reference Designator: Not Specified External Connector Type: None Port Type: PCMCIA Type I Handle 0x0038, DMI type 9, 13 bytes System Slot Information Designation: PCIEX1_16 Type: 32-bit PCI Express Current Usage: In Use Length: Short Characteristics: 3.3 V is provided Opening is shared PME signal is supported Handle 0x0039, DMI type 9, 13 bytes System Slot Information Designation: PCIEX2_16 Type: 32-bit PCI Express Current Usage: Available Length: Short Characteristics: 3.3 V is provided Opening is shared PME signal is supported Handle 0x003A, DMI type 9, 13 bytes System Slot Information Designation: PCIEX3_4 Type: 32-bit PCI Express Current Usage: Available Length: Short Characteristics: 3.3 V is provided Opening is shared PME signal is supported Handle 0x003B, DMI type 9, 13 bytes System Slot Information Designation: PCI4 Type: 32-bit PCI Current Usage: In Use Length: Short ID: 3 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Handle 0x003C, DMI type 9, 13 bytes System Slot Information Designation: PCI5 Type: 32-bit PCI Current Usage: In Use Length: Short ID: 4 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Handle 0x003D, DMI type 9, 13 bytes System Slot Information Designation: PCI6 Type: 32-bit PCI Current Usage: Available Length: Short ID: 5 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Handle 0x003E, DMI type 10, 6 bytes On Board Device Information Type: Video Status: Enabled Description: To Be Filled By O.E.M. Handle 0x003F, DMI type 11, 5 bytes OEM Strings String 1: 0015F29A04EA String 2: To Be Filled By O.E.M. String 3: To Be Filled By O.E.M. String 4: To Be Filled By O.E.M. Handle 0x0040, DMI type 13, 22 bytes BIOS Language Information Installable Languages: 1 en|US|iso8859-1 Currently Installed Language: en|US|iso8859-1 Handle 0x0041, DMI type 15, 35 bytes System Event Log Area Length: 4 bytes Header Start Offset: 0x0000 Header Length: 2 bytes Data Start Offset: 0x0002 Access Method: Indexed I/O, one 16-bit index port, one 8-bit data port Access Address: Index 0x046A, Data 0x046C Status: Invalid, Not Full Change Token: 0x00000000 Header Format: No Header Supported Log Type Descriptors: 6 Descriptor 1: End of log Data Format 1: OEM-specific Descriptor 2: End of log Data Format 2: OEM-specific Descriptor 3: End of log Data Format 3: OEM-specific Descriptor 4: End of log Data Format 4: OEM-specific Descriptor 5: End of log Data Format 5: OEM-specific Descriptor 6: End of log Data Format 6: OEM-specific Handle 0x0042, DMI type 16, 15 bytes Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: Single-bit ECC Maximum Capacity: 8 GB Error Information Handle: Not Provided Number Of Devices: 4 Handle 0x0043, DMI type 19, 15 bytes Memory Array Mapped Address Starting Address: 0x00000000000 Ending Address: 0x0003FFFFFFF Range Size: 1 GB Physical Array Handle: 0x0042 Partition Width: 0 Handle 0x0044, DMI type 17, 27 bytes Memory Device Array Handle: 0x0042 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 72 bits Size: 1024 MB Form Factor: DIMM Set: None Locator: DIMM0 Bank Locator: BANK0 Type: DDR Type Detail: Synchronous Speed: 400 MHz (2.5 ns) Manufacturer: Manufacturer0 Serial Number: SerNum0 Asset Tag: AssetTagNum0 Part Number: PartNum0 Handle 0x0045, DMI type 20, 19 bytes Memory Device Mapped Address Starting Address: 0x00000000000 Ending Address: 0x0003FFFFFFF Range Size: 1 GB Physical Device Handle: 0x0044 Memory Array Mapped Address Handle: 0x0043 Partition Row Position: 1 Handle 0x0046, DMI type 17, 27 bytes Memory Device Array Handle: 0x0042 Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: No Module Installed Form Factor: DIMM Set: None Locator: DIMM1 Bank Locator: BANK1 Type: Unknown Type Detail: Unknown Speed: Unknown Manufacturer: Manufacturer1 Serial Number: SerNum1 Asset Tag: AssetTagNum1 Part Number: PartNum1 Handle 0x0047, DMI type 126, 19 bytes Inactive Handle 0x0048, DMI type 17, 27 bytes Memory Device Array Handle: 0x0042 Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: No Module Installed Form Factor: DIMM Set: None Locator: DIMM2 Bank Locator: BANK2 Type: Unknown Type Detail: Unknown Speed: Unknown Manufacturer: Manufacturer2 Serial Number: SerNum2 Asset Tag: AssetTagNum2 Part Number: PartNum2 Handle 0x0049, DMI type 126, 19 bytes Inactive Handle 0x004A, DMI type 17, 27 bytes Memory Device Array Handle: 0x0042 Error Information Handle: Not Provided Total Width: Unknown Data Width: Unknown Size: No Module Installed Form Factor: DIMM Set: None Locator: DIMM3 Bank Locator: BANK3 Type: Unknown Type Detail: Unknown Speed: Unknown Manufacturer: Manufacturer3 Serial Number: SerNum3 Asset Tag: AssetTagNum3 Part Number: PartNum3 Handle 0x004B, DMI type 126, 19 bytes Inactive Handle 0x004C, DMI type 32, 20 bytes System Boot Information Status: No errors detected Handle 0x004D, DMI type 127, 4 bytes End Of Table --Boundary-00=_03OJE+jmt7mszpE Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="dmesg-a.out" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; name="dmesg-a.out" Copyright (c) 1992-2006 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.1-PRERELEASE #7: Sat Mar 25 16:14:15 EST 2006 agh@madcat:/usr/obj/usr/src/sys/MADCAT ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 FX-60 Dual Core Processor (2611.90-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20f32 Stepping = 2 Features=0x178bfbff Features2=0x1 AMD Features=0xe2500800,LM,3DNow+,3DNow> real memory = 1073414144 (1023 MB) avail memory = 1027108864 (979 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard rr2320: RocketRAID 2320 controller driver v1.01 (Jan 17 2006 17:35:15) acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.0 (no driver attached) pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 0.5 (no driver attached) pci0: at device 0.6 (no driver attached) pci0: at device 0.7 (no driver attached) pcib1: at device 2.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pcib2: at device 3.0 on pci0 pci2: on pcib2 pcib3: at device 4.0 on pci0 pci3: on pcib3 pcib4: at device 0.0 on pci3 pci5: on pcib4 pcib5: at device 0.2 on pci3 pci4: on pcib5 rr23200: port 0x8800-0x88ff mem 0xfe800000-0xfe8fffff irq 17 at device 4.0 on pci4 rr2320: adapter at PCI 4:4:0, IRQ 17 pci0: at device 9.0 (no driver attached) isab0: at device 10.0 on pci0 isa0: on isab0 pci0: at device 10.1 (no driver attached) ohci0: mem 0xfebfe000-0xfebfefff irq 21 at device 11.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 10 ports with 10 removable, self powered ehci0: mem 0xfebffc00-0xfebffcff irq 22 at device 11.1 on pci0 ehci0: [GIANT-LOCKED] usb1: EHCI version 1.0 usb1: companion controller, 4 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub1: 10 ports with 10 removable, self powered pcm0: port 0xe400-0xe4ff,0xe000-0xe0ff mem 0xfebfd000-0xfebfdfff irq 23 at device 13.0 on pci0 pcm0: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 15.0 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0xdc00-0xdc07,0xd880-0xd883,0xd800-0xd807,0xd480-0xd483,0xd400-0xd40f mem 0xfebfc000-0xfebfcfff irq 20 at device 16.0 on pci0 ata2: on atapci1 ata3: on atapci1 atapci2: port 0xd080-0xd087,0xd000-0xd003,0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f mem 0xfebfb000-0xfebfbfff irq 21 at device 17.0 on pci0 ata4: on atapci2 ata5: on atapci2 pcib6: at device 18.0 on pci0 pci6: on pcib6 drm0: port 0xb000-0xb0ff mem 0xd0000000-0xd7ffffff,0xfeaf0000-0xfeafffff irq 17 at device 6.0 on pci6 info: [drm] Initialized radeon 1.19.0 20050911 em0: port 0xbc00-0xbc3f mem 0xfeaa0000-0xfeabffff,0xfea40000-0xfea7ffff irq 16 at device 7.0 on pci6 em0: Ethernet address: 00:04:23:ac:ac:ea fwohci0: mem 0xfeaef800-0xfeaeffff,0xfeae8000-0xfeaebfff irq 17 at device 11.0 on pci6 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:11:d8:00:00:8a:89:e6 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:11:d8:8a:89:e6 fwe0: Ethernet address: 02:11:d8:8a:89:e6 fwe0: if_start running deferred for Giant sbp0: SCSI over FireWire> on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) pcib7: at device 22.0 on pci0 pci7: on pcib7 pcib8: at device 23.0 on pci0 pci8: on pcib8 acpi_button0: on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] ppc0: port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: on ppc0 ppi0: on ppbus0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A orm0: at iomem 0xc0000-0xcbfff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ums0: KYE Genius USB Wheel Mouse, rev 1.00/2.42, addr 2, iclass 3/1 ums0: 5 buttons and Z dir. Timecounters tick every 1.000 msec module_register_init: MOD_LOAD (amr_linux, 0xffffffff80407bc0, 0) error 6 rr2320: start channel [0,1] rr2320: start channel [0,2] rr2320: start channel [0,3] rr2320: start channel [0,4] rr2320: start channel [0,5] rr2320: channel [0,2] started successfully rr2320: channel [0,3] started successfully rr2320: channel [0,4] started successfully rr2320: channel [0,5] started successfully rr2320: channel [0,1]: failed to perform Hard Reset rr2320: fail to start channel [0,1] rr23200: [GIANT-LOCKED] da0 at rr23200 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 572160MB (1171783680 512 byte sectors: 255H 63S/T 72940C) SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/da0s1a Loading configuration files. Entropy harvesting: interrupts ethernet point_to_point kickstart . swapon: adding /dev/da0s1b as swap device Starting file system checks: /dev/da0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0s1a: clean, 213324 free (900 frags, 26553 blocks, 0.4% fragmentation) /dev/da0s1d: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0s1d: clean, 5072866 free (98 frags, 634096 blocks, 0.0% fragmentation) /dev/da0s1h: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0s1h: clean, 129275515 free (73419 frags, 16150262 blocks, 0.1% fragmentation) /dev/da0s1g: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0s1g: clean, 136985007 free (647 frags, 17123045 blocks, 0.0% fragmentation) /dev/da0s1e: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0s1e: clean, 2505829 free (493 frags, 313167 blocks, 0.0% fragmentation) /dev/da0s1f: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0s1f: clean, 5069787 free (603 frags, 633648 blocks, 0.0% fragmentation) Setting hostname: madcat. hw.snd.verbose: 1 -> 2 hw.snd.maxautovchans: 0 -> 4 hw.snd.pcm0.vchans: 1 -> 4 em0: no link ... . . . got link DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 7 DHCPOFFER from 192.168.0.1 DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 192.168.0.1 bound to 192.168.0.5 -- renewal in 43200 seconds. lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff000000 em0: flags=8843 mtu 1500 options=b inet6 fe80::204:23ff:feac:acea%em0 prefixlen 64 scopeid 0x1 inet 192.168.0.5 netmask 0xffffff00 broadcast 192.168.0.255 ether 00:04:23:ac:ac:ea media: Ethernet autoselect status: no carrier route: writing to routing socket : File exists add net default: gateway 192.168.0.1: route already in table Additional routing options: . Starting devd. Starting ums0 moused: . hw.acpi.cpu.cx_lowest: C1 -> C1 Mounting NFS file systems: . ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib /usr/local/libdata/ldconfig/graphviz /usr/local/libdata/ldconfig/mysql 32-bit compatibility ldconfig path: /usr/lib32 Creating and/or trimming log files: . Starting syslogd. Initial amd64 initialization: . Additional ABI support: . Recovering vi editor sessions: . Starting local daemons: . Updating motd . Starting usbd. Configuring syscons: keyrate blanktime . Starting cron. Local package initialization: Updating KDM configuration Information: reading old kdmrc /usr/local/share/config/kdm/kdmrc (from kde >= 2.2.x) Information: old kdmrc is from kde >= 3.1 (config version 2.3) rtc . Additional TCP options: . Starting inetd. Starting background file system checks in 60 seconds. Sat Mar 25 17:26:37 EST 2006 Mar 25 17:26:56 madcat su: BAD SU agh to root on /dev/ttyv0 Mar 25 17:27:00 madcat su: agh to root on /dev/ttyv0 --Boundary-00=_03OJE+jmt7mszpE-- From owner-freebsd-hardware@FreeBSD.ORG Sat Mar 25 23:58:42 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0BAB516A424 for ; Sat, 25 Mar 2006 23:58:42 +0000 (UTC) (envelope-from jason@ec.rr.com) Received: from ms-smtp-02-eri0.southeast.rr.com (ms-smtp-02-lbl.southeast.rr.com [24.25.9.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0E5243D48 for ; Sat, 25 Mar 2006 23:58:41 +0000 (GMT) (envelope-from jason@ec.rr.com) Received: from [192.168.2.101] (cpe-024-025-061-226.ec.res.rr.com [24.25.61.226]) by ms-smtp-02-eri0.southeast.rr.com (8.13.4/8.13.4) with ESMTP id k2PNwaTT022463; Sat, 25 Mar 2006 18:58:39 -0500 (EST) Message-ID: <4425D971.2030701@ec.rr.com> Date: Sat, 25 Mar 2006 18:59:45 -0500 From: jason henson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20060107) X-Accept-Language: en-us, en To: "Alastair G. Hogge" References: <200603251815.00814.agh@tpg.com.au> In-Reply-To: <200603251815.00814.agh@tpg.com.au> Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hardware@freebsd.org Subject: Re: Plextor 716SA DVD 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, 25 Mar 2006 23:58:42 -0000 Alastair G. Hogge wrote: Is the above supported on a ASUS A8N32-SLI Deluxe mainboard? I've tried plugging the device into either the nForce4 or Silicon Image 3132 SATA connectors but the device doesn't show up. I've also tried using my Highpoint RockedRAID 2320 card to detect the DVD drive. Attached you will find the output from: dmesg, cdrecode, pciconf and dmidecode. uname -a returns: FreeBSD madcat 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #7: Sat Mar 25 16:14:15 EST 2006 agh@madcat:/usr/obj/usr/src/sys/MADCAT amd64 Thanks in advance -Alastair _______________________________________________________________________ I am using the 7125SA just fine. Did you make a custom kernel? Do you have: # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives