From owner-freebsd-hardware Sun Feb 17 9:16:34 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from telesp.net.br (200-207-48-86.dsl.telesp.net.br [200.207.48.86]) by hub.freebsd.org (Postfix) with ESMTP id 4EA8437B405 for ; Sun, 17 Feb 2002 09:16:31 -0800 (PST) Received: from BB3CE4.cee.com (bb3ce4 [10.249.60.228]) by telesp.net.br (8.11.6/8.9.3) with ESMTP id g1HHMZ101615 for ; Sun, 17 Feb 2002 14:22:36 -0300 (EST) (envelope-from capriotti@cee.com) Message-Id: <5.1.0.14.1.20020217151321.024eba20@pop.mpcnet.com.br> X-Sender: capriotti@pop.mpcnet.com.br X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sun, 17 Feb 2002 15:19:46 -0300 To: freebsd-hardware@freebsd.org From: Capriotti Subject: Redundant power supply Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello. It's been a couple of days now I am seeking for information regarding the support to red8undant power suopplies under FreeBSD. My goal is to set up a system that can, at least, tell me one of the X power supplies has gone had and execute some sort of script, allowing me to send mma an email or so. Additional syslog reporting like current power levels and so would also be desirable. I've seen something similar on Dell PowerEdge server running MS platforms and am lookig forward to doing the same with our dear Beast. Any ideas ? thank you To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Feb 17 14:19:53 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.dis.org (dhcp45-21.dis.org [216.240.45.21]) by hub.freebsd.org (Postfix) with ESMTP id 39F4A37B430 for ; Sun, 17 Feb 2002 14:19:37 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.6) with ESMTP id g1HMJQA01364; Sun, 17 Feb 2002 14:19:27 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200202172219.g1HMJQA01364@mass.dis.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Capriotti Cc: freebsd-hardware@freebsd.org Subject: Re: Redundant power supply In-reply-to: Your message of "Sun, 17 Feb 2002 15:19:46 -0300." <5.1.0.14.1.20020217151321.024eba20@pop.mpcnet.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Feb 2002 14:19:26 -0800 From: Michael Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Not possible until ACPI is integrated. And it may be difficult even then; on some platforms you will need IPMI as well. > It's been a couple of days now I am seeking for information regarding the > support to red8undant power suopplies under FreeBSD. > > My goal is to set up a system that can, at least, tell me one of the X > power supplies has gone had and execute some sort of script, allowing me to > send mma an email or so. > > Additional syslog reporting like current power levels and so would also be > desirable. > > I've seen something similar on Dell PowerEdge server running MS platforms > and am lookig forward to doing the same with our dear Beast. > > Any ideas ? > > thank you > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message -- To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Feb 17 16:45:58 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from telesp.net.br (200-207-48-86.dsl.telesp.net.br [200.207.48.86]) by hub.freebsd.org (Postfix) with ESMTP id B83C737B400 for ; Sun, 17 Feb 2002 16:45:51 -0800 (PST) Received: from BB3CE4.cee.com (bb3ce4 [10.249.60.228]) by telesp.net.br (8.11.6/8.9.3) with ESMTP id g1I0pu101962 for ; Sun, 17 Feb 2002 21:51:57 -0300 (EST) (envelope-from capriotti@cee.com) Message-Id: <5.1.0.14.1.20020217224850.02bfa1f0@pop.mpcnet.com.br> X-Sender: capriotti@pop.mpcnet.com.br X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sun, 17 Feb 2002 22:48:56 -0300 To: freebsd-hardware@freebsd.org From: Capriotti Subject: Re: Redundant power supply Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Thanks for the introduction. searching some more, I found this (ON fREEbsd 5.0-CURRENT): http://www.freebsd.org/relnotes/CURRENT/relnotes/i386/x18.html >2.1.9 Contributed Software > >The Forth Inspired Command Language (FICL) used in the boot loader has >been updated to 2.05. >Support for Advanced Configuration and Power Interface (ACPI), a >multi-vendor standard for configuration and power >management, has been added. This functionality has been provided by the >Intel ACPI Component Architecture project, >updated to the ACPI CA 20011120 snapshot. Some backward compatability for >applications using the older APM standard >has been provided. That looks verry promissing ! And it's not old as well... Any idea if this has started to be implemented ? or, maybe plans to make it work under 4.x ??? I found nothing on IPMI... Thank you. At 02:19 PM 2/17/02 -0800, you wrote: >Not possible until ACPI is integrated. And it may be difficult even >then; on some platforms you will need IPMI as well. > > > It's been a couple of days now I am seeking for information regarding the > > support to red8undant power suopplies under FreeBSD. > > > > My goal is to set up a system that can, at least, tell me one of the X > > power supplies has gone had and execute some sort of script, allowing > me to > > send mma an email or so. > > > > Additional syslog reporting like current power levels and so would also be > > desirable. > > > > I've seen something similar on Dell PowerEdge server running MS platforms > > and am lookig forward to doing the same with our dear Beast. > > > > Any ideas ? > > > > thank you > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hardware" in the body of the message > >-- >To announce that there must be no criticism of the president, >or that we are to stand by the president, right or wrong, is not >only unpatriotic and servile, but is morally treasonable to >the American public. - Theodore Roosevelt > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hardware" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Feb 17 22:54:16 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from curry.turban2000.net (rn-re145b08.uwaterloo.ca [129.97.236.183]) by hub.freebsd.org (Postfix) with ESMTP id F1AD937B421 for ; Sun, 17 Feb 2002 22:51:25 -0800 (PST) Received: (from jdhar@localhost) by curry.turban2000.net (8.11.6/8.11.6) id g1I1vJv24615 for freebsd-hardware@freebsd.org; Mon, 18 Feb 2002 01:57:20 GMT (envelope-from jdhar) Date: Mon, 18 Feb 2002 01:57:11 +0000 From: Jai Dhar To: freebsd-hardware@freebsd.org Subject: P4 L1 cache problem maybe??? Message-ID: <20020218015710.D24518@curry.turban2000.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I was wondering if anyone knew how I could possibly test if my L1 Cache on my P4 1.4 is faulty? The reason I ask is because while trying to make buildworld recently, I had errors. The actual problem is that out of 6 retries compiling, I got 6 different errors in 6 different places. I synced my tree with 4.5-STABLE, and am using 4.5-RC2 right now... after asking around, people said it could be my ram or my CPU cache, so I swapped my ram out, and problem still persists, so when trying to make buildworld with L1 cache disabled, I ended up waiting 12 hours , while it was still going. Is thee any way I can test to see if my cache is faulty without sitting through a build world that can take +24 hours??? Keep in mind that I'm not an expert C programmer, and don't know how to write programs that execute themselves in the achce and then instruct them to do a cache spill to see if the times vary ... (this was a suggestion made to me :p). Thank you, Jai To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Feb 19 2:16:42 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.eviltwins.org (ns1.eviltwins.org [66.210.190.47]) by hub.freebsd.org (Postfix) with SMTP id 1B2E437B484 for ; Tue, 19 Feb 2002 02:16:12 -0800 (PST) Received: (qmail 69477 invoked by uid 1001); 19 Feb 2002 10:17:17 -0000 Date: Tue, 19 Feb 2002 04:17:17 -0600 From: wiz To: freebsd-hardware@freebsd.org Subject: EPoX EP-DR02P3 IDE RAID controller Message-ID: <20020219101717.GC27269@wiz.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org hi, Is the EPoX EP-DR02P3 IDE RAID controller supported in FreeBSD? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Feb 20 23:53:37 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from smtp.sambolian.net.nz (203-79-83-205.cable.paradise.net.nz [203.79.83.205]) by hub.freebsd.org (Postfix) with ESMTP id 4793E37B405; Wed, 20 Feb 2002 23:53:31 -0800 (PST) Received: from sambo.sambolian.net.nz (sambo.sambolian.net.nz [192.168.0.81]) by smtp.sambolian.net.nz (Postfix) with ESMTP id 69DE1FE83; Thu, 21 Feb 2002 20:56:15 +1300 (NZDT) Subject: Sony CD Writer model CRX175M From: Andrew Thompson To: freebsd-hardware@freebsd.org, freebsd-hackers@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2 Date: 21 Feb 2002 21:54:22 +1400 Message-Id: <1014278062.254.31.camel@sambo.sambolian.net.nz> Mime-Version: 1.0 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I have recently purchased a Sony cd writer (model CRX175M) that has a memory stick drive built in. The device comes up as afd0 but I am unable to mount it. The snippet of my dmesg is... vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ad0: 19546MB [39714/16/63] at ata0-master UDMA66 acd0: CD-RW at ata1-master using PIO4 afd0: 0MB [0/4/16] at ata1-slave using PIO4 Mounting root from ufs:/dev/ad0s2a When I try to mount it I get # mount /dev/afd0 /mnt/sony/ mount: /dev/afd0 on /mnt/sony: incorrect super block or # mount -t msdos /dev/afd0 /mnt/sony/ msdos: /dev/afd0: Invalid argument And I get the a few lines of "afd0: PREVENT_ALLOW - ILLEGAL REQUEST asc=24 ascq=00 error=00" in my dmesg. I have reformatted the memory stick from the camera but that makes no difference. Has anyone else used this hardware device? or can anyone help? cheers Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 21 3:26:15 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from nmh.informatik.uni-bremen.de (nmh.informatik.uni-bremen.de [134.102.224.3]) by hub.freebsd.org (Postfix) with ESMTP id 091D037B404; Thu, 21 Feb 2002 03:26:04 -0800 (PST) Received: from s61.informatik.uni-bremen.de (s61.informatik.uni-bremen.de [134.102.201.21]) by nmh.informatik.uni-bremen.de (8.10.1/8.10.1) with ESMTP id g1LBQ1C02050; Thu, 21 Feb 2002 12:26:02 +0100 (MET) Received: (from jstocker@localhost) by s61.informatik.uni-bremen.de (8.8.8+Sun/8.8.7) id MAA08570; Thu, 21 Feb 2002 12:26:00 +0100 (MET) Date: Thu, 21 Feb 2002 12:26:00 +0100 (MET) From: Jan Stocker To: Andrew Thompson Cc: freebsd-hardware@FreeBSD.ORG, Subject: Re: Sony CD Writer model CRX175M In-Reply-To: <1014278062.254.31.camel@sambo.sambolian.net.nz> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The memory stick will also have partitions... so try $fdisk afd0 to show up the table.... maybe a mount -t msdos /dev/afd0s1 /mnt/sony does it.... Jan -- "Kneel and deliver!" -- Casanunda, the worlds smallest lover turns highwaydwarf (Terry Pratchett, Lords and Ladies) On 21 Feb 2002, Andrew Thompson wrote: > Hi, > > > I have recently purchased a Sony cd writer (model CRX175M) that has a > memory stick drive built in. The device comes up as afd0 but I am > unable to mount it. The snippet of my dmesg is... > > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on > isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ad0: 19546MB [39714/16/63] at ata0-master UDMA66 > acd0: CD-RW at ata1-master using PIO4 > afd0: 0MB [0/4/16] at ata1-slave using PIO4 > Mounting root from ufs:/dev/ad0s2a > > > > > When I try to mount it I get > > # mount /dev/afd0 /mnt/sony/ > mount: /dev/afd0 on /mnt/sony: incorrect super block > > or > > # mount -t msdos /dev/afd0 /mnt/sony/ > msdos: /dev/afd0: Invalid argument > > > And I get the a few lines of "afd0: PREVENT_ALLOW - ILLEGAL REQUEST > asc=24 ascq=00 error=00" in my dmesg. > > > I have reformatted the memory stick from the camera but that makes no > difference. Has anyone else used this hardware device? or can anyone > help? > > > > > cheers > > Andrew > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 21 10:39:21 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from smtp.sambolian.net.nz (203-79-83-205.cable.paradise.net.nz [203.79.83.205]) by hub.freebsd.org (Postfix) with ESMTP id 3FCFB37B402; Thu, 21 Feb 2002 10:39:01 -0800 (PST) Received: from sambo.sambolian.net.nz (sambo.sambolian.net.nz [192.168.0.81]) by smtp.sambolian.net.nz (Postfix) with ESMTP id 0E817FDF8; Fri, 22 Feb 2002 07:41:49 +1300 (NZDT) Subject: Re: Sony CD Writer model CRX175M From: Andrew Thompson To: Jan Stocker Cc: freebsd-hardware@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2 Date: 22 Feb 2002 08:39:58 +1400 Message-Id: <1014316798.254.37.camel@sambo.sambolian.net.nz> Mime-Version: 1.0 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I get.... # fdisk afd0 ******* Working on device /dev/afd0 ******* parameters extracted from in-core disklabel are: cylinders=0 heads=4 sectors/track=16 (64 blks/cyl) parameters to be used for BIOS calculations are: cylinders=0 heads=4 sectors/track=16 (64 blks/cyl) fdisk: invalid fdisk partition table found fdisk: /boot/mbr: length must be a multiple of sector size and # mount -t msdos /dev/afd0s1 /mnt/sony msdos: /dev/afd0s1: Device not configured I guess the filesystem on the memory stick may not be supported. oh well, I not too worried about it as I dual boot with Windows(ugh). As its a new model someone else may buy one and come up with a solution in the future. Thanks for your help Jan. cheers Andrew On Fri, 2002-02-22 at 01:26, Jan Stocker wrote: > The memory stick will also have partitions... so try > > $fdisk afd0 > > to show up the table.... > > maybe a > > mount -t msdos /dev/afd0s1 /mnt/sony > > does it.... > > Jan > > > -- > "Kneel and deliver!" > -- Casanunda, the worlds smallest lover turns highwaydwarf > (Terry Pratchett, Lords and Ladies) > > On 21 Feb 2002, Andrew Thompson wrote: > > > Hi, > > > > > > I have recently purchased a Sony cd writer (model CRX175M) that has a > > memory stick drive built in. The device comes up as afd0 but I am > > unable to mount it. The snippet of my dmesg is... > > > > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on > > isa0 > > sc0: at flags 0x100 on isa0 > > sc0: VGA <16 virtual consoles, flags=0x300> > > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > > sio0: type 16550A > > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > > sio1: type 16550A > > ad0: 19546MB [39714/16/63] at ata0-master UDMA66 > > acd0: CD-RW at ata1-master using PIO4 > > afd0: 0MB [0/4/16] at ata1-slave using PIO4 > > Mounting root from ufs:/dev/ad0s2a > > > > > > > > > > When I try to mount it I get > > > > # mount /dev/afd0 /mnt/sony/ > > mount: /dev/afd0 on /mnt/sony: incorrect super block > > > > or > > > > # mount -t msdos /dev/afd0 /mnt/sony/ > > msdos: /dev/afd0: Invalid argument > > > > > > And I get the a few lines of "afd0: PREVENT_ALLOW - ILLEGAL REQUEST > > asc=24 ascq=00 error=00" in my dmesg. > > > > > > I have reformatted the memory stick from the camera but that makes no > > difference. Has anyone else used this hardware device? or can anyone > > help? > > > > > > > > > > cheers > > > > Andrew > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hardware" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 21 16:14:44 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 62F8037B404; Thu, 21 Feb 2002 16:14:36 -0800 (PST) Received: from localhost (root@localhost [127.0.0.1]) by cain.gsoft.com.au (8.12.2/8.12.2) with ESMTP id g1M0EDZR007360; Fri, 22 Feb 2002 10:44:17 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Subject: Re: Sony CD Writer model CRX175M From: "Daniel O'Connor" To: Andrew Thompson Cc: Jan Stocker , freebsd-hardware@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: <1014316798.254.37.camel@sambo.sambolian.net.nz> References: <1014316798.254.37.camel@sambo.sambolian.net.nz> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2 Date: 22 Feb 2002 11:44:13 +1130 Message-Id: <1014336863.3564.30.camel@chowder.gsoft.com.au> Mime-Version: 1.0 X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 2002-02-22 at 06:09, Andrew Thompson wrote: > fdisk: invalid fdisk partition table found > fdisk: /boot/mbr: length must be a multiple of sector size > > > And I get the a few lines of "afd0: PREVENT_ALLOW - ILLEGAL REQUEST > > > asc=24 ascq=00 error=00" in my dmesg. Personally I'd say that is the problem. The ATA code is sending a request that the memory stick doesn't understand. Perhaps there are some resources online that may be able to point out what is necessary to talk to this device. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 21 17:14:49 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from orac.moffetimages.com (dsl3-63-249-88-4.cruzio.com [63.249.88.4]) by hub.freebsd.org (Postfix) with ESMTP id E19D837B402 for ; Thu, 21 Feb 2002 17:14:41 -0800 (PST) Received: from DIABLO.moffetimages.com (dhcp-64.moffetimages.com [192.168.20.64]) (authenticated bits=0) by orac.moffetimages.com (8.12.1/8.12.1) with ESMTP id g1M1EeHm018559 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 21 Feb 2002 17:14:41 -0800 (PST) Message-Id: <5.1.0.14.2.20020221170615.03751c38@orac.moffetimages.com> X-Sender: brianm@orac.moffetimages.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 21 Feb 2002 17:18:21 -0800 To: freebsd-hardware@freebsd.org From: "Brian D. Moffet" Subject: SAN Disk Flash ram Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I am using a Flash Ram, connected to a device that converts the PCM/CIA Flash ram to an IDE interface, it looks like a 30 Meg hard drive... It is currently hooked to the slave side of my second IDE controller (ASUS CUV4X-E motherboard with Pentium III 880 Mghz), and running FreeBSD 4.3. After doing the usual fdisk, disklabel, newfs, I mount it and start taring stuff to the flash ram. Someplace in the middle of this, the machine will lock up completely. Where it locks up is not consistent. The keyboard is inactive, as determined by no change in LEDs. The IDE light is on continuously. I let it sit for a few hours before I shut the machine down. I have put a 40pin/80 conductor IDE connector on both channels rather than the 40pin/40 conductor that was in there, but that didn't help. Is there a debug flag or something that I can turn on to help track state information in the driver, so that I can try to determine what is going on? I'm just looking for ways to start tracking this problem, though if anyone already knows of a solution, great. I am going to try it under LINUX (redhat 7.0) to see if I can reproduce the problem. Thanks much, Brian Moffet Brian D. Moffet brianm@moffetimages.com -- http://www.moffetimages.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Feb 21 19:11:57 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from alfred.oau.org (24.27.208.2.pinecastle-ubr-a.cfl.rr.com [24.27.208.2]) by hub.freebsd.org (Postfix) with ESMTP id 9BE7F37B400 for ; Thu, 21 Feb 2002 19:11:41 -0800 (PST) Received: (from elliot@localhost) by alfred.oau.org (8.11.6/8.11.6) id g1M3Bes75575 for freebsd-hardware@freebsd.org; Thu, 21 Feb 2002 22:11:40 -0500 (EST) (envelope-from elliot) From: Elliot Dierksen Message-Id: <200202220311.g1M3Bes75575@alfred.oau.org> Subject: Problems with Tyan 2466 MBD To: freebsd-hardware@freebsd.org Date: Thu, 21 Feb 2002 22:11:40 -0500 (EST) Reply-To: ebd@oau.org (Elliot Dierksen) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, I have a spiffy new Tyan 2466 760 MPX motherboard that is giving me a few problems. I can not get the psm device to find my mouse. I know the mouse is working because I put 2000 server in another partition, and it find the mouse just fine. See the following dmesg excerpts: psm0: current command byte:0047 psm0: failed to reset the aux device. I have tried several flags options such as no reset and ignore port error, but no success. Secondly, the xl device is having a problem with the on board 3C920 chipset. If I run the production BIOS [1.00 ;-)], I get endless "xl0: reset didn't complete" messages and the NIC is not usable. If I run the BETA BIOS, I still get one such message but I can use the NIC. I am running 4.5-STABLE as of about 4 days ago. I would be happy to provide any information I can to try and resolve the problem. Any suggestions appreciated! Thanx, EBD -----begin full dmesg------- Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.5-STABLE #4: Thu Feb 21 21:58:33 EST 2002 root@newalf.oau.org:/usr/src/sys/compile/AMD-MP Calibrating clock(s) ... TSC clock: 1533086052 Hz, i8254 clock: 1192947 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: AMD Athlon(tm) MP 1800+ (1533.39-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x662 Stepping = 2 Features=0x383fbff AMD Features=0xc0480000<,AMIE,DSP,3DNow!> Data TLB: 32 entries, fully associative Instruction TLB: 16 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 internal cache: 256 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative real memory = 536870912 (524288K bytes) Physical memory chunk(s): 0x00001000 - 0x0009cfff, 638976 bytes (156 pages) 0x00470000 - 0x1feeffff, 531103744 bytes (129664 pages) 0x1ff00000 - 0x1fff7fff, 1015808 bytes (248 pages) config> di pcic0 config> di sn0 config> di lnc0 config> di ie0 config> di fe0 config> di ed0 config> di cs0 config> di bt0 config> di ata1 config> di ata0 config> di aic0 config> di aha0 config> di adv0 config> en apm0 config> #flags psm0 0x1000 Invalid command or syntax. Type `?' for help. config> q avail memory = 517914624 (505776K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 SMP: CPU0 apic_initialize(): lint0: 0x00000700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040010, at 0xfee00000 io0 (APIC): apic id: 1, version: 0x00170011, at 0xfec00000 bios32: Found BIOS32 Service Directory header at 0xc00f7180 bios32: Entry = 0xfd670 (c00fd670) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x120 pnpbios: Found PnP BIOS data at 0xc00f71e0 pnpbios: Entry = f0000:989c Rev = 1.0 Other BIOS signatures found: ACPI: 000f71b0 Preloaded elf kernel "kernel" at 0xc0446000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc04460a8. Pentium Pro MTRR support enabled md0: Malloc disk Creating DISK md0 Math emulator present SMP: CPU0 bsp_apic_configure(): lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000010 SVR: 0x000001ff pci_open(1): mode 1 addr port (0x0cf8) is 0x80004108 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=700c1022) Using $PIR table, 11 entries at 0xc00fdf10 apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard found-> vendor=0x1022, dev=0x700c, revid=0x11 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base c0000000, size 29 map[14]: type 1, range 32, base b0400000, size 12 found-> vendor=0x1022, dev=0x700d, revid=0x00 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x1022, dev=0x7440, revid=0x04 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1022, dev=0x7441, revid=0x04 class=01-01-8a, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 0000f000, size 4 found-> vendor=0x1022, dev=0x7443, revid=0x03 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x1044, dev=0xa500, revid=0x01 class=06-04-00, hdrtype=0x01, mfdev=1 subordinatebus=2 secondarybus=2 found-> vendor=0x1044, dev=0xa501, revid=0x01 class=0e-00-01, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base e0000000, size 28 found-> vendor=0x1022, dev=0x7448, revid=0x04 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=3 secondarybus=3 pci0: on pcib0 pcib1: at device 1.0 on pci0 found-> vendor=0x5333, dev=0x8a22, revid=0x02 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base b0000000, size 19 map[14]: type 1, range 32, base b8000000, size 27 pci1: on pcib1 pci1: (vendor=0x5333, dev=0x8a22) at 5.0 irq 10 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xf000 ata0: mask=03 status0=50 status1=00 ata0: mask=03 ostat0=50 ostat2=00 ata0-master: ATAPI probe a=14 b=eb ata0-slave: ATAPI probe a=7f b=7f ata0: mask=03 status0=10 status1=00 ata0: devices=04 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xf008 ata1: mask=03 status0=20 status1=30 ata1: mask=03 ostat0=20 ostat2=30 ata1-master: ATAPI probe a=20 b=20 ata1-slave: ATAPI probe a=30 b=30 ata1: mask=03 status0=20 status1=30 ata1-master: ATA probe a=25 b=25 ata1-slave: ATA probe a=25 b=25 ata1: devices=00 ata1: at 0x170 irq 15 on atapci0 chip1: at device 7.3 on pci0 pcib2: at device 8.0 on pci0 pci2: on pcib2 asr0: mem 0xe0000000-0xefffffff irq 11 at device 8.1 on pci0 asr0: major=154 asr0: ADAPTEC 3210S FW Rev. 3607, 2 channel, 256 CCBs, Protocol I2O pcib3: at device 16.0 on pci0 found-> vendor=0x10b7, dev=0x9200, revid=0x78 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=5 map[10]: type 1, range 32, base 00002000, size 7 map[14]: type 1, range 32, base b0101000, size 7 pci3: on pcib3 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x2000-0x207f mem 0xb0101000-0xb010107f irq 5 at device 8.0 on pci3 xl0: reset didn't complete xl0: Ethernet address: 00:e0:81:20:3b:c8 xl0: media options word: a xl0: found MII/AUTO miibus0: on xl0 ukphy0: on miibus0 ukphy0: OUI 0x00105a, model 0x0000, rev. 0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bpf: xl0 attached ex_isa_identify() ata-: ata0 exists, using next available unit number ata-: ata1 exists, using next available unit number Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: