From owner-freebsd-hardware Mon Dec 11 3:28:31 2000 From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 11 03:28:29 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mail.kyx.net (unknown [216.232.16.187]) by hub.freebsd.org (Postfix) with ESMTP id 4450237B6B2 for ; Mon, 11 Dec 2000 03:28:19 -0800 (PST) Received: from smp.kyx.net (unknown [10.22.22.45]) by mail.kyx.net (Postfix) with SMTP id 536821DC08 for ; Mon, 11 Dec 2000 02:56:39 -0800 (PST) From: Dragos Ruiu Organization: kyx.net To: freebsd-hardware@freebsd.org Subject: Asus A7V and booting FreeBSD 4.2R from the onboard Promise ATA-100 controller Date: Mon, 11 Dec 2000 02:49:48 -0800 X-Mailer: KYX-CP/M [version core00-mail-92] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <0012110255191K.09615@smp.kyx.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anyone successfully done this? Can you enlighten me about the appropriate magic.... ??? I found the old PR about the ASUS A7V and it seems to have been fixed in 4.2R.... The install works fine... the drivers find the controller... the install seems to work on the new disks hanging of the ATA100. The boot loader finds the kernel on ad4 and then it craps out saying it can't load the root partition.... Any pointers? I'll try moving the root partition disk to the ordinary IDE tomorrow but this seems like a waste of a good fast disk... thanks, --dr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Dec 11 4:53:30 2000 From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 11 04:53:28 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mail0.bna.bellsouth.net (mail0.bna.bellsouth.net [205.152.150.12]) by hub.freebsd.org (Postfix) with ESMTP id E2B6137B400 for ; Mon, 11 Dec 2000 04:53:27 -0800 (PST) Received: from planetwe.com (adsl-20-108-74.bna.bellsouth.net [66.20.108.74]) by mail0.bna.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id HAA07383; Mon, 11 Dec 2000 07:49:55 -0500 (EST) Message-ID: <3A34CD75.8000502@planetwe.com> Date: Mon, 11 Dec 2000 06:49:57 -0600 From: Drew Sanford User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.12 i386; en-US; m18) Gecko/20001107 Netscape6/6.0 X-Accept-Language: en MIME-Version: 1.0 To: Dragos Ruiu Cc: freebsd-hardware@freebsd.org Subject: Re: Asus A7V and booting FreeBSD 4.2R from the onboard Promise ATA-100 controller References: <0012110255191K.09615@smp.kyx.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This didn't require any magic on my part - once I got my NIC and parralel port to stop fighting over the same IRQ. Before that it would hang right after the parralel port was detected. There was never an issue about loading the root partition. What sort of drive do you have? Dragos Ruiu wrote: > Has anyone successfully done this? Can you enlighten me > about the appropriate magic.... ??? > > I found the old PR about the ASUS A7V and it seems to have been fixed in > 4.2R.... The install works fine... the drivers find the controller... the > install seems to work on the new disks hanging of the ATA100. > The boot loader finds the kernel on ad4 and then it craps out saying it > can't load the root partition.... > > Any pointers? > > I'll try moving the root partition disk to the ordinary IDE tomorrow but this > seems like a waste of a good fast disk... > > thanks, > --dr > > > 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 Mon Dec 11 7:15:37 2000 From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 11 07:15:35 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from smtp.pandora.be (hercules.telenet-ops.be [195.130.132.33]) by hub.freebsd.org (Postfix) with SMTP id 26CDA37B400 for ; Mon, 11 Dec 2000 07:15:35 -0800 (PST) Received: (qmail 19443 invoked from network); 11 Dec 2000 15:15:33 -0000 Received: from unknown (HELO TOSH) ([213.224.184.208]) (envelope-sender ) by hercules.telenet-ops.be (qmail-ldap-1.03) with SMTP for ; 11 Dec 2000 15:15:33 -0000 Date: Mon, 11 Dec 2000 16:07:34 +0100 From: Tom Van de Wiele X-Mailer: The Bat! (v1.46d) Personal Reply-To: Tom Van de Wiele X-Priority: 3 (Normal) Message-ID: <169521849339.20001211160734@securax.org> To: freebsd-hardware@freebsd.org Subject: pcmcia ethernet card Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi I have a pcmcia ethernet card that I want to use to install freebsd on my laptop. The pcmcia card is recognized: pcic0 : Intel (i82365) port 0x3e0 iomem 0xd0000 When I try to install, the only installation media are ppp, paralell and serial, but no pcmcia. Also, everybody tells me I should have got a "would you like to activate/install ethernet devices" messages, which I didn't get... Any thoughts would be appreciated Thanks Tom Van de Wiele Ghent, Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Dec 11 8: 0:50 2000 From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 11 08:00:47 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from osiris.ipform.ru (osiris.ipform.ru [212.158.165.98]) by hub.freebsd.org (Postfix) with ESMTP id C541A37B404; Mon, 11 Dec 2000 08:00:44 -0800 (PST) Received: from wp2 (wp2 [192.168.0.12]) by osiris.ipform.ru (8.11.1/8.11.1) with SMTP id eBBG0bE20980; Mon, 11 Dec 2000 19:00:37 +0300 (MSK) (envelope-from matrix@ipform.ru) Message-ID: <000e01c0638b$8086dd60$0c00a8c0@ipform.ru> From: "Artem Koutchine" To: Cc: Subject: Power management control (programmatic) Date: Mon, 11 Dec 2000 19:00:32 +0300 Organization: IP Form MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is there any programmatic interface which allows to turn on/off devices (hdds any the whole PC)? I, i could probably access the device directly, however I don't know 1) How to do it right 2) The command I hope there is some c library or maybe utility with source code. Regards, Artem To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Dec 11 8: 0:54 2000 From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 11 08:00:50 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from osiris.ipform.ru (osiris.ipform.ru [212.158.165.98]) by hub.freebsd.org (Postfix) with ESMTP id B7EB037B400; Mon, 11 Dec 2000 08:00:44 -0800 (PST) Received: from wp2 (wp2 [192.168.0.12]) by osiris.ipform.ru (8.11.1/8.11.1) with SMTP id eBBG0YE20977; Mon, 11 Dec 2000 19:00:37 +0300 (MSK) (envelope-from matrix@ipform.ru) Message-ID: <000d01c0638b$80654ba0$0c00a8c0@ipform.ru> From: "Artem Koutchine" To: Cc: Subject: Software to contol LM7001 FM Radio card Date: Mon, 11 Dec 2000 18:58:08 +0300 Organization: IP Form MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello! Is there any software to control LM7001 bases FM radio card (i think i got the chip name right). It is usually Packard Bell OEM ISA card. Artem To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Dec 11 9:11: 4 2000 From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 11 09:11:01 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from bbnrel4.net.external.hp.com (bbnrel4.net.external.hp.com [155.208.254.68]) by hub.freebsd.org (Postfix) with ESMTP id B93D637B402; Mon, 11 Dec 2000 09:11:00 -0800 (PST) Received: from hpcpbla.bri.hp.com (hpcpbla.bri.hp.com [15.144.112.65]) by bbnrel4.net.external.hp.com (Postfix) with ESMTP id 8F7121ED40; Mon, 11 Dec 2000 18:10:58 +0100 (MET) Received: from sse0691.bri.hp.com (sse0691.bri.hp.com [15.144.0.53]) by hpcpbla.bri.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.0) with ESMTP id RAA11413; Mon, 11 Dec 2000 17:10:56 GMT Received: (from keithj@localhost) by sse0691.bri.hp.com (8.11.1/8.9.3) id eBBHFPR47775; Mon, 11 Dec 2000 17:15:25 GMT (envelope-from keithj) Date: Mon, 11 Dec 2000 17:15:24 +0000 From: Keith Jones To: Artem Koutchine Cc: questions@freebsd.org, hardware@freebsd.org Subject: Re: Power management control (programmatic) Message-ID: <20001211171524.A45253@moose.bri.hp.com> References: <000e01c0638b$8086dd60$0c00a8c0@ipform.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <000e01c0638b$8086dd60$0c00a8c0@ipform.ru>; from matrix@ipform.ru on Mon, Dec 11, 2000 at 07:00:32PM +0300 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The apm(4) manual page lists a bunch of ioctl's for power management, which could be used against /dev/apm or /dev/apmctl (I assume). I'd go take a look at the sources of apm/zzz(8) to see how they're actually implemented. Ta, Keith On Mon, Dec 11, 2000 at 07:00:32PM +0300, Artem Koutchine wrote: > Is there any programmatic interface which allows to turn on/off devices > (hdds any the whole PC)? I, i could probably access the device directly, > however > I don't know > 1) How to do it right > 2) The command > I hope there is some c library or maybe utility with source code. > > Regards, > Artem > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message -- Keith Jones E-Business Service Introduction, GBIT-EMEA (Bristol) E: keith_jones@non.hp.com T: [+44 117] 312-7602 I don't speak for Hewlett-Packard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Dec 11 9:34:19 2000 From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 11 09:34:12 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from osiris.ipform.ru (osiris.ipform.ru [212.158.165.98]) by hub.freebsd.org (Postfix) with ESMTP id 4AF0737B400; Mon, 11 Dec 2000 09:34:10 -0800 (PST) Received: from wp2 (wp2 [192.168.0.12]) by osiris.ipform.ru (8.11.1/8.11.1) with SMTP id eBBHVYE96285; Mon, 11 Dec 2000 20:31:35 +0300 (MSK) (envelope-from matrix@ipform.ru) Message-ID: <001d01c06398$36137ec0$0c00a8c0@ipform.ru> From: "Artem Koutchine" To: "Keith Jones" Cc: , References: <000e01c0638b$8086dd60$0c00a8c0@ipform.ru> <20001211171524.A45253@moose.bri.hp.com> Subject: Re: Power management control (programmatic) Date: Mon, 11 Dec 2000 20:31:32 +0300 Organization: IP Form MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks for the reply. Here is what man 4 apm states: Disk spin-down, LCD backlight control, and power on demand have not been supported on the current version. (I have FreeBSD 4.2-stable.) I guess that means that I CANNOT programmatically TURN OFF (PARK) HDDs? Regards, Artem ----- Original Message ----- From: "Keith Jones" To: "Artem Koutchine" Cc: ; Sent: Monday, December 11, 2000 8:15 PM Subject: Re: Power management control (programmatic) > The apm(4) manual page lists a bunch of ioctl's for power management, which > could be used against /dev/apm or /dev/apmctl (I assume). I'd go take a look > at the sources of apm/zzz(8) to see how they're actually implemented. > > Ta, > > Keith > > On Mon, Dec 11, 2000 at 07:00:32PM +0300, Artem Koutchine wrote: > > Is there any programmatic interface which allows to turn on/off devices > > (hdds any the whole PC)? I, i could probably access the device directly, > > however > > I don't know > > 1) How to do it right > > 2) The command > > I hope there is some c library or maybe utility with source code. > > > > Regards, > > Artem > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hardware" in the body of the message > > -- > Keith Jones > E-Business Service Introduction, GBIT-EMEA (Bristol) > E: keith_jones@non.hp.com > T: [+44 117] 312-7602 > > I don't speak for Hewlett-Packard. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Dec 11 10:19:43 2000 From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 11 10:19:37 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from bbnrel4.net.external.hp.com (bbnrel4.net.external.hp.com [155.208.254.68]) by hub.freebsd.org (Postfix) with ESMTP id DAB0E37B400; Mon, 11 Dec 2000 10:19:36 -0800 (PST) Received: from hpcpbla.bri.hp.com (hpcpbla.bri.hp.com [15.144.112.65]) by bbnrel4.net.external.hp.com (Postfix) with ESMTP id B37AF20DA1; Mon, 11 Dec 2000 19:19:34 +0100 (MET) Received: from sse0691.bri.hp.com (sse0691.bri.hp.com [15.144.0.53]) by hpcpbla.bri.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.0) with ESMTP id SAA16352; Mon, 11 Dec 2000 18:19:33 GMT Received: (from keithj@localhost) by sse0691.bri.hp.com (8.11.1/8.9.3) id eBBIO0w51846; Mon, 11 Dec 2000 18:24:00 GMT (envelope-from keithj) Date: Mon, 11 Dec 2000 18:24:00 +0000 From: Keith Jones To: Artem Koutchine Cc: questions@freebsd.org, hardware@freebsd.org Subject: Re: Power management control (programmatic) Message-ID: <20001211182400.B45253@moose.bri.hp.com> References: <000e01c0638b$8086dd60$0c00a8c0@ipform.ru> <20001211171524.A45253@moose.bri.hp.com> <001d01c06398$36137ec0$0c00a8c0@ipform.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <001d01c06398$36137ec0$0c00a8c0@ipform.ru>; from matrix@ipform.ru on Mon, Dec 11, 2000 at 08:31:32PM +0300 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It would appear that you are correct. On Mon, Dec 11, 2000 at 08:31:32PM +0300, Artem Koutchine wrote: > Thanks for the reply. > > Here is what man 4 apm states: > > Disk spin-down, LCD backlight control, and power on demand have not > been supported on the current version. > > (I have FreeBSD 4.2-stable.) > > I guess that means that I CANNOT programmatically TURN OFF (PARK) > HDDs? > > Regards, > Artem > > ----- Original Message ----- > From: "Keith Jones" > To: "Artem Koutchine" > Cc: ; > Sent: Monday, December 11, 2000 8:15 PM > Subject: Re: Power management control (programmatic) > > > > The apm(4) manual page lists a bunch of ioctl's for power management, > which > > could be used against /dev/apm or /dev/apmctl (I assume). I'd go take a > look > > at the sources of apm/zzz(8) to see how they're actually implemented. > > > > Ta, > > > > Keith > > > > On Mon, Dec 11, 2000 at 07:00:32PM +0300, Artem Koutchine wrote: > > > Is there any programmatic interface which allows to turn on/off devices > > > (hdds any the whole PC)? I, i could probably access the device directly, > > > however > > > I don't know > > > 1) How to do it right > > > 2) The command > > > I hope there is some c library or maybe utility with source code. > > > > > > Regards, > > > Artem > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-hardware" in the body of the message > > > > -- > > Keith Jones > > E-Business Service Introduction, GBIT-EMEA (Bristol) > > E: keith_jones@non.hp.com > > T: [+44 117] 312-7602 > > > > I don't speak for Hewlett-Packard. > > > -- Keith Jones E-Business Service Introduction, GBIT-EMEA (Bristol) E: keith_jones@non.hp.com T: [+44 117] 312-7602 I don't speak for Hewlett-Packard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Dec 11 13:51:48 2000 From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 11 13:51:45 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from ns2.globaldns.com (ns2.globaldns.com [206.253.214.12]) by hub.freebsd.org (Postfix) with ESMTP id E5B0437B400 for ; Mon, 11 Dec 2000 13:51:43 -0800 (PST) Received: from 39_NOC.nic.cc ([209.237.72.254]) by ns2.globaldns.com (8.8.7/8.8.7) with ESMTP id NAA08863 for ; Mon, 11 Dec 2000 13:49:48 -0800 (PST) (envelope-from peter@nic.cc) Message-Id: <4.3.2.7.0.20001211134909.00aa9500@wheresmymailserver.com> X-Sender: peter@ns2.globaldns.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 11 Dec 2000 13:53:55 -0800 To: freebsd-hardware@freebsd.org From: peter Subject: RAID 5 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Our company just purchased some Dell 2400s with on-mobo RAID 5 support....having a hell of a time with them. I am installing 4.2-Release from CD. Does this version of FreeBSD support the Dell controller? I've got 4 disks in there, I'd hate to have to give up the hardware RAID for a vinum stripe set. It looks like its made by Adaptec, a 7880 shows up at the beginning with my SCSI CDROM on it, but the RAID controller tells me its the 'Dell PowerEdge Expandable RAID Controller 2/si'.... Any ideas? Or do I just vinum the box? thanks, Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Dec 11 15:48:30 2000 From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 11 15:48:28 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id C59F137B400 for ; Mon, 11 Dec 2000 15:48:24 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBBNvp301012; Mon, 11 Dec 2000 15:57:52 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012112357.eBBNvp301012@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: peter Cc: freebsd-hardware@freebsd.org Subject: Re: RAID 5 In-reply-to: Your message of "Mon, 11 Dec 2000 13:53:55 PST." <4.3.2.7.0.20001211134909.00aa9500@wheresmymailserver.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Dec 2000 15:57:51 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Our company just purchased some Dell 2400s with on-mobo RAID 5 > support....having a hell of a time with them. I am installing 4.2-Release > from CD. Does this version of FreeBSD support the Dell controller? No, FreeBSD 4.2 doesn't support this controller. There is experimental support in 5.0, but we are having major issues with what we believe to be firmware bugs. Unfortunately, the reference hardware that we have access to doesn't exhibit these problems, and nobody has been able to supply us with a Dell box to work on. > It looks like its made by Adaptec, a 7880 shows up at the beginning with > my SCSI CDROM on it, but the RAID controller tells me its the 'Dell > PowerEdge Expandable RAID Controller 2/si'.... If FreeBSD is detecting the SCSI controller, something's not right. Either you don't have the RAID key installed, or you haven't set the array up properly. Either way, that won't help you yet. > Any ideas? Or do I just vinum the box? Well, a) you could send one of the boxes to scottl@freebsd.org for a month or so so that we can whack this bug for good and get support committed, or b) you could get some PERC 2/DC's from Dell. Meaning no offense to Greg, but I wouldn't be recommending Vinum for production use just yet. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Dec 11 16:56:41 2000 From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 11 16:56:38 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from ns2.globaldns.com (ns2.globaldns.com [206.253.214.12]) by hub.freebsd.org (Postfix) with ESMTP id 56EAC37B400; Mon, 11 Dec 2000 16:56:38 -0800 (PST) Received: from 39_NOC.nic.cc ([209.237.72.254]) by ns2.globaldns.com (8.8.7/8.8.7) with ESMTP id QAA28557; Mon, 11 Dec 2000 16:54:42 -0800 (PST) (envelope-from peter@nic.cc) Message-Id: <4.3.2.7.0.20001211163808.00acea40@ns2.globaldns.com> X-Sender: peter@ns2.globaldns.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 11 Dec 2000 16:58:52 -0800 To: Mike Smith From: peter Subject: Re: RAID 5 Cc: freebsd-hardware@freebsd.org In-Reply-To: <200012112357.eBBNvp301012@mass.osd.bsdi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks for the info, although I wish I could send you a box, I don't have anywhere near the kind of auth to do that... ;) We've played with vinum for a few months with no problems, is it reliable enough to take the abuse we are about to engage in? Would CCD be a better bet? Are there options I am not aware of. Basically there are five of these guys as Database servers behind ten PowerApp web100 boxes, which in turn are behind a Load-balancing smart switch (CISCO content switch)...we know our main bottleneck is drive access so we wanted some sort of RAID or striping. p. At 03:57 PM 12/11/00 -0800, you wrote: > > > > Our company just purchased some Dell 2400s with on-mobo RAID 5 > > support....having a hell of a time with them. I am installing 4.2-Release > > from CD. Does this version of FreeBSD support the Dell controller? > >No, FreeBSD 4.2 doesn't support this controller. There is experimental >support in 5.0, but we are having major issues with what we believe to be >firmware bugs. Unfortunately, the reference hardware that we have access >to doesn't exhibit these problems, and nobody has been able to supply us >with a Dell box to work on. > > > It looks like its made by Adaptec, a 7880 shows up at the beginning with > > my SCSI CDROM on it, but the RAID controller tells me its the 'Dell > > PowerEdge Expandable RAID Controller 2/si'.... > >If FreeBSD is detecting the SCSI controller, something's not right. >Either you don't have the RAID key installed, or you haven't set the >array up properly. Either way, that won't help you yet. > > > Any ideas? Or do I just vinum the box? > >Well, a) you could send one of the boxes to scottl@freebsd.org for a >month or so so that we can whack this bug for good and get support >committed, or b) you could get some PERC 2/DC's from Dell. Meaning no >offense to Greg, but I wouldn't be recommending Vinum for production use >just yet. > >-- >... every activity meets with opposition, everyone who acts has his >rivals and unfortunately opponents also. But not because people want >to be opponents, rather because the tasks and relationships force >people to take different points of view. [Dr. Fritz Todt] > V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Dec 11 17:20:17 2000 From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 11 17:20:14 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id 6B5A937B400 for ; Mon, 11 Dec 2000 17:20:14 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBC1U1301289; Mon, 11 Dec 2000 17:30:01 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012120130.eBC1U1301289@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: peter Cc: freebsd-hardware@freebsd.org Subject: Re: RAID 5 In-reply-to: Your message of "Mon, 11 Dec 2000 16:58:52 PST." <4.3.2.7.0.20001211163808.00acea40@ns2.globaldns.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Dec 2000 17:30:01 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Thanks for the info, although I wish I could send you a box, I don't have > anywhere near the kind of auth to do that... ;) *sigh* That's OK. 8) > We've played with vinum for a few months with no problems, is it reliable > enough to take the abuse we are about to engage in? > > Would CCD be a better bet? No, and no. > Are there options I am not aware of. Basically there are five of these > guys as Database servers behind ten PowerApp web100 boxes, which in turn > are behind a Load-balancing smart switch (CISCO content switch)...we know > our main bottleneck is drive access so we wanted some sort of RAID or > striping. Depends on how many disks you're planning to use. As I suggested, the Dell PERC 2/DC is probably a good alternative. I'm sorry we're not up to snuff with the onboard RAID yet; it's been a long haul. 8( Regards, Mike > p. > > At 03:57 PM 12/11/00 -0800, you wrote: > > > > > > Our company just purchased some Dell 2400s with on-mobo RAID 5 > > > support....having a hell of a time with them. I am installing 4.2-Release > > > from CD. Does this version of FreeBSD support the Dell controller? > > > >No, FreeBSD 4.2 doesn't support this controller. There is experimental > >support in 5.0, but we are having major issues with what we believe to be > >firmware bugs. Unfortunately, the reference hardware that we have access > >to doesn't exhibit these problems, and nobody has been able to supply us > >with a Dell box to work on. > > > > > It looks like its made by Adaptec, a 7880 shows up at the beginning with > > > my SCSI CDROM on it, but the RAID controller tells me its the 'Dell > > > PowerEdge Expandable RAID Controller 2/si'.... > > > >If FreeBSD is detecting the SCSI controller, something's not right. > >Either you don't have the RAID key installed, or you haven't set the > >array up properly. Either way, that won't help you yet. > > > > > Any ideas? Or do I just vinum the box? > > > >Well, a) you could send one of the boxes to scottl@freebsd.org for a > >month or so so that we can whack this bug for good and get support > >committed, or b) you could get some PERC 2/DC's from Dell. Meaning no > >offense to Greg, but I wouldn't be recommending Vinum for production use > >just yet. > > > >-- > >... every activity meets with opposition, everyone who acts has his > >rivals and unfortunately opponents also. But not because people want > >to be opponents, rather because the tasks and relationships force > >people to take different points of view. [Dr. Fritz Todt] > > V I C T O R Y N O T V E N G E A N C E > > -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Dec 11 17:31: 4 2000 From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 11 17:31:02 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from ecx1.edifecs.com (unknown [207.149.212.72]) by hub.freebsd.org (Postfix) with ESMTP id EE07A37B400; Mon, 11 Dec 2000 17:31:01 -0800 (PST) Received: by ecx1.edifecs.com with Internet Mail Service (5.5.2650.21) id ; Mon, 11 Dec 2000 17:27:35 -0800 Message-ID: From: Michael VanLoon To: 'Mike Smith' , peter Cc: freebsd-hardware@freebsd.org Subject: RE: RAID 5 Date: Mon, 11 Dec 2000 17:27:34 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've also had excellent results with the DPT SmartRaid V controllers, though I don't know how easy these are to find since they've been swallowed by Adaptec. > From: Mike Smith [mailto:msmith@freebsd.org] > Sent: Monday, December 11, 2000 5:30 PM > > > Thanks for the info, although I wish I could send you a > box, I don't have > > anywhere near the kind of auth to do that... ;) > > *sigh* That's OK. 8) > > > We've played with vinum for a few months with no problems, > is it reliable > > enough to take the abuse we are about to engage in? > > > > Would CCD be a better bet? > > No, and no. > > > Are there options I am not aware of. Basically there are > five of these > > guys as Database servers behind ten PowerApp web100 boxes, > which in turn > > are behind a Load-balancing smart switch (CISCO content > switch)...we know > > our main bottleneck is drive access so we wanted some sort > of RAID or > > striping. > > Depends on how many disks you're planning to use. As I > suggested, the > Dell PERC 2/DC is probably a good alternative. I'm sorry > we're not up to > snuff with the onboard RAID yet; it's been a long haul. 8( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Dec 11 18:22:47 2000 From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 11 18:22:45 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id 0357537B400 for ; Mon, 11 Dec 2000 18:22:41 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBC2WS301447; Mon, 11 Dec 2000 18:32:28 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012120232.eBC2WS301447@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Michael VanLoon Cc: freebsd-hardware@freebsd.org Subject: Re: RAID 5 In-reply-to: Your message of "Mon, 11 Dec 2000 17:27:34 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Dec 2000 18:32:28 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I've also had excellent results with the DPT SmartRaid V controllers, though > I don't know how easy these are to find since they've been swallowed by > Adaptec. They're now marketted as the "Adaptec SCSI RAID" controllers; the DPT VI family is very easy to come by (ASR2100, 3200, 3400 in the new nomenclature). Mark Salyzyn's driver seems to be working well for people; we support these out of the box, and Adaptec are also supporting their management tools. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Dec 12 1: 1:21 2000 From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 12 01:01:19 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mail.kyx.net (unknown [216.232.16.187]) by hub.freebsd.org (Postfix) with ESMTP id B7C3F37B400 for ; Tue, 12 Dec 2000 01:01:18 -0800 (PST) Received: from smp.kyx.net (unknown [10.22.22.45]) by mail.kyx.net (Postfix) with SMTP id 3A1AB1DC08; Tue, 12 Dec 2000 01:02:59 -0800 (PST) From: Dragos Ruiu Organization: kyx.net To: Drew Sanford Subject: Re: Asus A7V and booting FreeBSD 4.2R from the onboard Promise ATA-100 controller Date: Tue, 12 Dec 2000 01:00:17 -0800 X-Mailer: KYX-CP/M [version core00-mail-92] Content-Type: text/plain Cc: freebsd-hardware@freebsd.org References: <0012110255191K.09615@smp.kyx.net> <3A34CD75.8000502@planetwe.com> In-Reply-To: <3A34CD75.8000502@planetwe.com> MIME-Version: 1.0 Message-Id: <0012120101321S.09615@smp.kyx.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Uhm... it's a pretty newfangled maxtor 64Mb drive. Hmmm... never considered if that could be the issue.... I'll try swapping drives too... sigh. Cheers, --dr On Mon, 11 Dec 2000, Drew Sanford wrote: > This didn't require any magic on my part - once I got my NIC and > parralel port to stop fighting over the same IRQ. Before that it would > hang right after the parralel port was detected. There was never an > issue about loading the root partition. What sort of drive do you have? > > Dragos Ruiu wrote: > > > Has anyone successfully done this? Can you enlighten me > > about the appropriate magic.... ??? > > > > I found the old PR about the ASUS A7V and it seems to have been fixed in > > 4.2R.... The install works fine... the drivers find the controller... the > > install seems to work on the new disks hanging of the ATA100. > > The boot loader finds the kernel on ad4 and then it craps out saying it > > can't load the root partition.... > > > > Any pointers? > > > > I'll try moving the root partition disk to the ordinary IDE tomorrow but this > > seems like a waste of a good fast disk... > > > > thanks, > > --dr > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hardware" in the body of the message -- Dragos Ruiu dursec.com ltd. / kyx.net - we're from the future gpg/pgp key on file at wwwkeys.pgp.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Dec 12 3:39:49 2000 From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 12 03:39:48 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from nevermind.kiev.ua (unknown [212.109.53.33]) by hub.freebsd.org (Postfix) with ESMTP id 07C4737B400 for ; Tue, 12 Dec 2000 03:39:46 -0800 (PST) Received: (from never@localhost) by nevermind.kiev.ua (8.11.1/8.11.1) id eBCBdd100738 for freebsd-hardware@freebsd.org; Tue, 12 Dec 2000 13:39:39 +0200 (EET) (envelope-from never) Date: Tue, 12 Dec 2000 13:39:39 +0200 From: Nevermind To: freebsd-hardware@freebsd.org Subject: Iomega ZIP Message-ID: <20001212133938.A730@nevermind.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I have only one question: ata1-slave: floppy device - NO DRIVER! does it mean that it is not supported? -- Alexandr P. Kovalenko http://nevermind.kiev.ua/ NEVE-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Dec 12 3:49: 2 2000 From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 12 03:49:00 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id 0F65237B400 for ; Tue, 12 Dec 2000 03:49:00 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBCBwO303530; Tue, 12 Dec 2000 03:58:25 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012121158.eBCBwO303530@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nevermind Cc: freebsd-hardware@freebsd.org Subject: Re: Iomega ZIP In-reply-to: Your message of "Tue, 12 Dec 2000 13:39:39 +0200." <20001212133938.A730@nevermind.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Dec 2000 03:58:24 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hello, > > I have only one question: > ata1-slave: floppy device - NO DRIVER! > does it mean that it is not supported? No, it means you left the 'atapifd' driver out of your kernel. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Dec 12 11:52:55 2000 From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 12 11:52:54 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from portnoy.lbl.gov (portnoy.lbl.gov [131.243.2.11]) by hub.freebsd.org (Postfix) with ESMTP id C7D2A37B400 for ; Tue, 12 Dec 2000 11:52:53 -0800 (PST) Received: (from jin@localhost) by portnoy.lbl.gov (8.11.1/8.11.1) id eBCJqgu11343; Tue, 12 Dec 2000 11:52:42 -0800 (PST) Date: Tue, 12 Dec 2000 11:52:42 -0800 (PST) From: Jin Guojun (DSD staff) Message-Id: <200012121952.eBCJqgu11343@portnoy.lbl.gov> To: dr@kyx.net, drew@planetwe.com Subject: Re: Asus A7V and booting FreeBSD 4.2R from the onboard Promise ATA-100 controller Cc: freebsd-hardware@FreeBSD.ORG Sender: jin@portnoy.lbl.gov Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Both 4.1 and 4.2 works on A7V in my experience. There is a random hanging time during probing the ATA66/100 dirves. I just found some interesting issue for ATA-66/100 drives to cause such hang. I bought a bounch of ATA-66/100 WDC and Maxtor drives (10/20/40/45/60/80). Even with the same type of drives, say WDC450AA, each dirve has different response time the Tx rate (slightly different). If putting them on the same IDE bus, they cause trouble for the Tx rate. I do not have any detailed information on why this happens because I do not have time to analyse the singnal on the IDE bus. I guess there is confilct on the bus. About 8 years ago, when seagate Elite-2 came to the market, this dirve always try to grab at least two bus cycle before releasing the bus. It caused numbers of bus reset and reduced Tx rate to the half if more than one drives on the bus :-( (that was SCSI bus) I am not familiar with IDE signal. But I guess there is similar thing happened to these new drives that may not complaint with ATA-66/100 standard. Try to use one ATA-100 drive on each IDE bus to see if that work for you. -Jin On Mon, 11 Dec 2000, Drew Sanford wrote: > This didn't require any magic on my part - once I got my NIC and > parralel port to stop fighting over the same IRQ. Before that it would > hang right after the parralel port was detected. There was never an > issue about loading the root partition. What sort of drive do you have? > > Dragos Ruiu wrote: > > > Has anyone successfully done this? Can you enlighten me > > about the appropriate magic.... ??? > > > > I found the old PR about the ASUS A7V and it seems to have been fixed in > > 4.2R.... The install works fine... the drivers find the controller... the > > install seems to work on the new disks hanging of the ATA100. > > The boot loader finds the kernel on ad4 and then it craps out saying it > > can't load the root partition.... > > > > Any pointers? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Dec 13 3:11:25 2000 From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 13 03:11:19 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mail.monkeys.com (236.dsl9226.rcsis.com [63.92.26.236]) by hub.freebsd.org (Postfix) with ESMTP id 2765337B400; Wed, 13 Dec 2000 03:11:19 -0800 (PST) Received: from monkeys.com (236.dsl9226.rcsis.com [63.92.26.236]) by mail.monkeys.com (8.11.1/8.11.1) with ESMTP id eBDBB5w37687; Wed, 13 Dec 2000 03:11:05 -0800 (PST) To: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Help! "Fatal trap 1: privledged instruction trap" while installing Date: Wed, 13 Dec 2000 03:11:05 -0800 Message-ID: <37685.976705865@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Here's my situation: I wanted to cobble together a cheap system out of some components that I had scavenged from an older system, plus some new components. Fry's was having a special on the following pair of components: AMD K6-III 333 FIC VA-503+ motherboard So I purchased those, dropped them into an old case I had, added an old Adaptec 1542CP SCSI controller (ancient, but well-supported and reliable), a floppy disk, an ancient Toshiba SCSI CD-ROM drive, a couple of crusty old SCSI hard drives, some old 72-pin simms, and a nice new dirt cheap 10/100 generic ethernet card that I know works OK on other 4.1 systems I have. (It gets recognized by FreeBSD as an `rl0' thingy.) Then I fired the system up. Data point: The system seemed to work OK under MS-DOS 5.0 and I low-level and high-level formatted both SCSI drives. No problem. (I just provide this information for the sake of completness in describing my problem. Please DO NOT jump on me and tell me that I am denigrating FreeBSD. That is not my intent at all. I just want to proved as much data as possible to anyone and everyone who might help me to solcve this problem.) Anyway, then I tried to install FreeBSD 4.1.1. Now I have a problem. Con- sistantly, every time it tried to boot the kernel (the first time, during the install) it gets down to the point where it is trying to initialize the keyboard driver, and then it chokes, big time. Here's what I see on the console screen every time: ------------------------------------------------------------------------- ... isa0: blah blah blah atapci: blah blah blah pcib2: blah blah blah fdc0: blah blah blah fdc0: blah blah blah fd0: blah blah blah atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 Fatal trap 1: privledged instruction fault while in vm86 mode instruction pointer = 0xcc00:0x30d3 stack pointer = 0x0:0xff8 frame pointer = 0x0:0x0 code segment = base 0x0, limit 0x0, type 0x0 = DPL 0, pres 0, def32 0, gran 0 processor eflags = interrupt enabled, resume, vm86, IOPL = 0 current process = 0 (swapper) interrupt mask = net tty bio cam trap number = 1 panic: privledged instruction fault Uptime: 0s Automatic reboot in 15 seconds - press a key on the console to abort ------------------------------------------------------------------------- ... and then it sits there and waits for 15 seconds and then reboots. NOTE: There has been some suggestion elsewhere that the AMD K2-III processor is in some ways not compatible with either the FIC VA-503+ board or (perhaps) its BIOS (depending upon the REV number). NOTE HOWEVER that I also own an AMD K6-2/300 processor and so naturally, I tried that also. I swapped the K6-III/333 for my K6-II/300 and I still get _exactly_ the same failure at exactly the same place in the boot process with EITHER the K6-III or the K6-II installed. NOTE: Ssupecting a possible memory problem (even though I had run Memtest-86 on this memory overnight, with no errors), I yanked out ALL of the old 72-pin SIMMS and installed instead one fresh new 168-pin 64MB SDRAM DIMM, which is known good and pulled from a working system. (The FIC VA-503+ board is unusual in that it has slots for both 72-pin memory and 168-pin memory.) Anyway, even with totally different memory I still get the exact same failure at the exact same point in the install/boot process. NOTE: I even tried using a different keyboard. Still no go. I still got exactly the same failure (as shown above) at the exact same place in the install/boot process. I am at my wit's end now with this problem, and I don't know what else I can try swapping out. I've already swapped all of the usual suspects and none of that has helped. I've briefly scanned DejaNews looking for any signs of major incompatabilities between FreeBSD and K6-III's or between FreeBSD and FIC VA-503+ motherboards and I don't see anything major, but that doesn't mean that there isn't some problem that hasn't been reported (of course). I could speculate about what may be causing this problem, but I think I'm better off not showing my ignorance, and leaving the speculation to the experts instead. Experts? What say you? Is this a lost cause? I was really hoping to put FreeBSD on this system. But I can't even get past first base during the install process. P.S. For whatever it's worth, the BIOS rev on the board seems to be: Award rev: 4.60PGA FIC rev: JE439 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Dec 13 3:20:49 2000 From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 13 03:20:46 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id 6647437B400; Wed, 13 Dec 2000 03:20:45 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBDBUW308257; Wed, 13 Dec 2000 03:30:32 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012131130.eBDBUW308257@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Ronald F. Guilmette" Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Help! "Fatal trap 1: privledged instruction trap" while installing In-reply-to: Your message of "Wed, 13 Dec 2000 03:11:05 PST." <37685.976705865@monkeys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Dec 2000 03:30:32 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Fry's was having a special on the following pair of components: > > AMD K6-III 333 > FIC VA-503+ motherboard Make sure you have updated the BIOS on this board to the most recent version. > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > > Fatal trap 1: privledged instruction fault while in vm86 mode > instruction pointer = 0xcc00:0x30d3 Looks like you're in the VESA BIOS. Can you boot with -v and give us some more details? What video card are you using? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Dec 13 3:43:21 2000 From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 13 03:43:17 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mail.monkeys.com (236.dsl9226.rcsis.com [63.92.26.236]) by hub.freebsd.org (Postfix) with ESMTP id CD86637B400; Wed, 13 Dec 2000 03:43:16 -0800 (PST) Received: from monkeys.com (236.dsl9226.rcsis.com [63.92.26.236]) by mail.monkeys.com (8.11.1/8.11.1) with ESMTP id eBDBhGw38030; Wed, 13 Dec 2000 03:43:16 -0800 (PST) To: Mike Smith Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Help! "Fatal trap 1: privledged instruction trap" while installing In-reply-to: Your message of Wed, 13 Dec 2000 03:30:32 -0800. <200012131130.eBDBUW308257@mass.osd.bsdi.com> Date: Wed, 13 Dec 2000 03:43:16 -0800 Message-ID: <38028.976707796@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200012131130.eBDBUW308257@mass.osd.bsdi.com>, you wrote: >> >> Fry's was having a special on the following pair of components: >> >> AMD K6-III 333 >> FIC VA-503+ motherboard > >Make sure you have updated the BIOS on this board to the most recent >version. I do have. >> atkbdc0: at port 0x60,0x64 on isa0 >> atkbd0: flags 0x1 irq 1 on atkbdc0 >> >> Fatal trap 1: privledged instruction fault while in vm86 mode >> instruction pointer = 0xcc00:0x30d3 > >Looks like you're in the VESA BIOS. Can you boot with -v and give us >some more details? There isn't much more info, but here it is: ------------------------------------------------------------------------- ... atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0067 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa Fatal trap 1: privledged instruction fault while in vm86 mode instruction pointer = 0xcc00:0x30d3 stack pointer = 0x0:0xff8 frame pointer = 0x0:0x0 code segment = base 0x0, limit 0x0, type 0x0 = DPL 0, pres 0, def32 0, gran 0 processor eflags = interrupt enabled, resume, vm86, IOPL = 0 current process = 0 (swapper) interrupt mask = net tty bio cam trap number = 1 panic: privledged instruction fault Uptime: 0s Automatic reboot in 15 seconds - press a key on the console to abort ------------------------------------------------------------------------- So does that help any? What's going on here? > What video card are you using? A cheapie S3-based piece of junk. The brand is `Datona'. (I say ``junk'' because I tried using it with XFree86 before, and I could never get it to work 100% correctly. I mostly worked, but whenever I moved the mouse, or whenever there was any change in what appeared on the screen, many thin horizontal white lines would flash momentarily in seemingly random places all over the screen. I just chalked it up to crap/cheap electronics and used another card.) Should I try swapping the video card out? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Dec 13 3:57:25 2000 From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 13 03:57:20 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id 6382A37B400; Wed, 13 Dec 2000 03:57:20 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBDC78308428; Wed, 13 Dec 2000 04:07:08 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012131207.eBDC78308428@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Ronald F. Guilmette" Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Help! "Fatal trap 1: privledged instruction trap" while installing In-reply-to: Your message of "Wed, 13 Dec 2000 03:43:16 PST." <38028.976707796@monkeys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Dec 2000 04:07:08 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >> atkbdc0: at port 0x60,0x64 on isa0 > >> atkbd0: flags 0x1 irq 1 on atkbdc0 > >> > >> Fatal trap 1: privledged instruction fault while in vm86 mode > >> instruction pointer = 0xcc00:0x30d3 > > > >Looks like you're in the VESA BIOS. Can you boot with -v and give us > >some more details? > > There isn't much more info, but here it is: > > ------------------------------------------------------------------------- > ... > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > atkbd: the current kbd controller command byte 0067 > atkbd: keyboard ID 0x41ab (2) > kbdc: RESET_KBD return code:00fa > kbdc: RESET_KBD status:00aa > > > Fatal trap 1: privledged instruction fault while in vm86 mode > instruction pointer = 0xcc00:0x30d3 Ok; that doesn't really help a lot, unfortunately. However, I still think you're probably in the VESA BIOS. You might want to try a different (brand/type) of video card and see if that doesn't improve things. > So does that help any? What's going on here? What's going on is that we've called the BIOS in v86 mode, and it's done something stupid. It's probably not expecting to be called like this at all. > > What video card are you using? > > A cheapie S3-based piece of junk. The brand is `Datona'. (I say ``junk'' > because I tried using it with XFree86 before, and I could never get it to > work 100% correctly. I mostly worked, but whenever I moved the mouse, or > whenever there was any change in what appeared on the screen, many thin > horizontal white lines would flash momentarily in seemingly random places > all over the screen. I just chalked it up to crap/cheap electronics and > used another card.) I have a card like this made by Jaton; I never run it out of text mode. > Should I try swapping the video card out? Definitely. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Dec 13 4:11:27 2000 From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 13 04:11:23 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mail.monkeys.com (236.dsl9226.rcsis.com [63.92.26.236]) by hub.freebsd.org (Postfix) with ESMTP id EF84737B400; Wed, 13 Dec 2000 04:11:22 -0800 (PST) Received: from monkeys.com (236.dsl9226.rcsis.com [63.92.26.236]) by mail.monkeys.com (8.11.1/8.11.1) with ESMTP id eBDCBMw38166; Wed, 13 Dec 2000 04:11:22 -0800 (PST) To: Mike Smith Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Help! "Fatal trap 1: privledged instruction trap" while installing In-reply-to: Your message of Wed, 13 Dec 2000 04:07:08 -0800. <200012131207.eBDC78308428@mass.osd.bsdi.com> Date: Wed, 13 Dec 2000 04:11:22 -0800 Message-ID: <38164.976709482@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200012131207.eBDC78308428@mass.osd.bsdi.com>, you wrote: >> ------------------------------------------------------------------------- >> ... >> atkbdc0: at port 0x60,0x64 on isa0 >> atkbd0: flags 0x1 irq 1 on atkbdc0 >> atkbd: the current kbd controller command byte 0067 >> atkbd: keyboard ID 0x41ab (2) >> kbdc: RESET_KBD return code:00fa >> kbdc: RESET_KBD status:00aa >> >> >> Fatal trap 1: privledged instruction fault while in vm86 mode >> instruction pointer = 0xcc00:0x30d3 > >Ok; that doesn't really help a lot, unfortunately. However, I still >think you're probably in the VESA BIOS. You might want to try a >different (brand/type) of video card and see if that doesn't improve >things. > >> So does that help any? What's going on here? > >What's going on is that we've called the BIOS in v86 mode, and it's done >something stupid. It's probably not expecting to be called like this at >all. So who is really at fault here? The card, or FreeBSD? Is there some standard that says that VIDEO BIOSes aren't supposed to execute instructions that would be considered illegal in v86 mode? And anyway, how the heck did we get down into the Video Card BIOS before we have even finished doing keyboard initialization? Or have we finished that? (I can't quite tell.) >> Should I try swapping the video card out? > >Definitely. OK. Will do. First thing in the morning. But I've had enough fun for one day now, so I'm turning in for the nite. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Dec 13 4:31: 9 2000 From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 13 04:31:05 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id 33B8637B400; Wed, 13 Dec 2000 04:31:05 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBDCeq308534; Wed, 13 Dec 2000 04:40:52 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012131240.eBDCeq308534@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Ronald F. Guilmette" Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Help! "Fatal trap 1: privledged instruction trap" while installing In-reply-to: Your message of "Wed, 13 Dec 2000 04:11:22 PST." <38164.976709482@monkeys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Dec 2000 04:40:52 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >> So does that help any? What's going on here? > > > >What's going on is that we've called the BIOS in v86 mode, and it's done > >something stupid. It's probably not expecting to be called like this at > >all. > > So who is really at fault here? The card, or FreeBSD? That's hard to say. We expect the card's BIOS to work, and the exceedingly vast majority of them do. > Is there some standard that says that VIDEO BIOSes aren't supposed to > execute instructions that would be considered illegal in v86 mode? You're supposed to be able to call the BIOS in v86 mode, yes. A lot of DOS extenders (used for DOS-based games) do this. > And anyway, how the heck did we get down into the Video Card BIOS before > we have even finished doing keyboard initialization? Or have we finished > that? (I can't quite tell.) We've finished with the keyboard and have started on the VGA driver. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Dec 13 10:48:45 2000 From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 13 10:48:42 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id DA73C37B400; Wed, 13 Dec 2000 10:48:41 -0800 (PST) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eBDImYE34053; Wed, 13 Dec 2000 10:48:34 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.0) id eBDIlmh29517; Wed, 13 Dec 2000 10:47:48 -0800 (PST) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <38028.976707796@monkeys.com> Date: Wed, 13 Dec 2000 10:47:47 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: "Ronald F. Guilmette" Subject: Re: Help! "Fatal trap 1: privledged instruction trap" while inst Cc: freebsd-hardware@FreeBSD.ORG, Mike Smith Sender: jhb@foo.osd.bsdi.com Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 13-Dec-00 Ronald F. Guilmette wrote: > > In message <200012131130.eBDBUW308257@mass.osd.bsdi.com>, you wrote: > >>> >>> Fry's was having a special on the following pair of components: >>> >>> AMD K6-III 333 >>> FIC VA-503+ motherboard >> >>Make sure you have updated the BIOS on this board to the most recent >>version. > > I do have. > >>> atkbdc0: at port 0x60,0x64 on isa0 >>> atkbd0: flags 0x1 irq 1 on atkbdc0 >>> >>> Fatal trap 1: privledged instruction fault while in vm86 mode >>> instruction pointer = 0xcc00:0x30d3 >> >>Looks like you're in the VESA BIOS. Can you boot with -v and give us >>some more details? > > There isn't much more info, but here it is: > > ------------------------------------------------------------------------- > ... > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > atkbd: the current kbd controller command byte 0067 > atkbd: keyboard ID 0x41ab (2) > kbdc: RESET_KBD return code:00fa > kbdc: RESET_KBD status:00aa > > > Fatal trap 1: privledged instruction fault while in vm86 mode > instruction pointer = 0xcc00:0x30d3 > stack pointer = 0x0:0xff8 > frame pointer = 0x0:0x0 > code segment = base 0x0, limit 0x0, type 0x0 > = DPL 0, pres 0, def32 0, gran 0 > processor eflags = interrupt enabled, resume, vm86, IOPL = 0 > current process = 0 (swapper) > interrupt mask = net tty bio cam > trap number = 1 > panic: privledged instruction fault > Uptime: 0s > Automatic reboot in 15 seconds - press a key on the console to abort Mike, would this address be mapped to 0xc00cf0d3 in the kernel? (And thus in /dev/mem?) If so, Ronald, do this as root: - install nasm from ports/devel/nasm (or from sysinstall) # dd if=/dev/mem iseek=0xc00cf0d3 bs=1 count=16 | ndisasm Then mail back the resulting text you get. This will show us what instruction it died on. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Dec 13 10:57:36 2000 From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 13 10:57:31 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mail.monkeys.com (236.dsl9226.rcsis.com [63.92.26.236]) by hub.freebsd.org (Postfix) with ESMTP id A0F9137B6F4; Wed, 13 Dec 2000 10:57:29 -0800 (PST) Received: from monkeys.com (236.dsl9226.rcsis.com [63.92.26.236]) by mail.monkeys.com (8.11.1/8.11.1) with ESMTP id eBDIvTw39361; Wed, 13 Dec 2000 10:57:29 -0800 (PST) To: Mike Smith Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Help! "Fatal trap 1: privledged instruction trap" while installing In-reply-to: Your message of Wed, 13 Dec 2000 04:40:52 -0800. <200012131240.eBDCeq308534@mass.osd.bsdi.com> Date: Wed, 13 Dec 2000 10:57:29 -0800 Message-ID: <39359.976733849@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200012131240.eBDCeq308534@mass.osd.bsdi.com>, you wrote: >> >> So does that help any? What's going on here? >> > >> >What's going on is that we've called the BIOS in v86 mode, and it's done >> >something stupid. It's probably not expecting to be called like this at >> >all. >> >> So who is really at fault here? The card, or FreeBSD? > >That's hard to say. We expect the card's BIOS to work, and the >exceedingly vast majority of them do. You just answered the question. It's the card's fault. >> Is there some standard that says that VIDEO BIOSes aren't supposed to >> execute instructions that would be considered illegal in v86 mode? > >You're supposed to be able to call the BIOS in v86 mode, yes. A lot of >DOS extenders (used for DOS-based games) do this. Sounds to me like you have just confirmed your answer above... It really is the card's fault. (Grumble, grumble... last time I buy a video card whose brand I never heard of before!) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Dec 13 13: 7:52 2000 From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 13 13:07:50 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id E111637B402; Wed, 13 Dec 2000 13:07:49 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBDLHc310072; Wed, 13 Dec 2000 13:17:38 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012132117.eBDLHc310072@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Baldwin Cc: "Ronald F. Guilmette" , freebsd-hardware@FreeBSD.ORG, Mike Smith Subject: Re: Help! "Fatal trap 1: privledged instruction trap" while inst In-reply-to: Your message of "Wed, 13 Dec 2000 10:47:47 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Dec 2000 13:17:38 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Fatal trap 1: privledged instruction fault while in vm86 mode > > instruction pointer = 0xcc00:0x30d3 > > stack pointer = 0x0:0xff8 > > frame pointer = 0x0:0x0 > > code segment = base 0x0, limit 0x0, type 0x0 ... > Mike, would this address be mapped to 0xc00cf0d3 in the kernel? (And thus in > /dev/mem?) If so, Ronald, do this as root: > > - install nasm from ports/devel/nasm (or from sysinstall) > # dd if=/dev/mem iseek=0xc00cf0d3 bs=1 count=16 | ndisasm > > Then mail back the resulting text you get. This will show us what instruction > it died on. Actually, /dev/mem is a 1:1 mapping of physical memory. (You're thinking of /dev/kmem). But you're almost right; the code in question will be at 0xcf0d3 offset in /dev/mem, so: # dd if=/dev/mem iseek=0xcf0d3 bs=1 count=16 | ndisasm -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Dec 13 14:50:46 2000 From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 13 14:50:42 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mail.monkeys.com (236.dsl9226.rcsis.com [63.92.26.236]) by hub.freebsd.org (Postfix) with ESMTP id D113C37B699; Wed, 13 Dec 2000 14:50:41 -0800 (PST) Received: from monkeys.com (236.dsl9226.rcsis.com [63.92.26.236]) by mail.monkeys.com (8.11.1/8.11.1) with ESMTP id eBDMofw40357; Wed, 13 Dec 2000 14:50:41 -0800 (PST) To: Mike Smith Cc: John Baldwin , freebsd-questions@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Help! "Fatal trap 1: privledged instruction trap" while inst In-reply-to: Your message of Wed, 13 Dec 2000 13:20:53 -0800. <200012132120.eBDLKr310117@mass.osd.bsdi.com> Date: Wed, 13 Dec 2000 14:50:41 -0800 Message-ID: <40355.976747841@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200012132120.eBDLKr310117@mass.osd.bsdi.com>, Mike Smith wrote: >Also, the VESA code isn't in GENERIC, says he just looking. > >I'm sorry; I don't have any other great ideas. Try a new video card. 8) OK. I went today and bought a new ATI Xpert 98 video card. I installed it into the system in question. I tried to install FreeBSD again. Still no-go. I am getting EXACTLY the same error as before at EXACTLY the same point in the process. Another data point: I had an old FreeBSD 3.3 CD lying around, so I tried that, and sure enough it works! No problems and I get past the kernel initial boot. So OK chaps... What does it all mean? Based on the evidence, I am inclined to say that there is a definite bug in the FreeBSD 4.1.1 generic kernel. I mean hay! FreeBSD 3.3 boots up fine on the exact same hardware. I have now tried swapping just about everything... CPU, memory, keyboard, video card. The only other thing left for me to try is to try ripping out the SCSI card and associated drives. I guess that I will do that, just to be through, but really folks, this is looking a lot like a kernel bug. Assuming that it is one, where should I turn for further assistance? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Dec 13 15:22:50 2000 From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 13 15:22:46 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 1317937B404; Wed, 13 Dec 2000 15:22:46 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eBDNMWE46445; Wed, 13 Dec 2000 15:22:32 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <40355.976747841@monkeys.com> Date: Wed, 13 Dec 2000 15:22:41 -0800 (PST) From: John Baldwin To: "Ronald F. Guilmette" Subject: Re: Help! "Fatal trap 1: privledged instruction trap" while inst Cc: freebsd-hardware@FreeBSD.org, freebsd-questions@FreeBSD.org, Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 13-Dec-00 Ronald F. Guilmette wrote: > > In message <200012132120.eBDLKr310117@mass.osd.bsdi.com>, > Mike Smith wrote: > >>Also, the VESA code isn't in GENERIC, says he just looking. >> >>I'm sorry; I don't have any other great ideas. Try a new video card. 8) > > OK. I went today and bought a new ATI Xpert 98 video card. > > I installed it into the system in question. > > I tried to install FreeBSD again. > > Still no-go. I am getting EXACTLY the same error as before at EXACTLY > the same point in the process. > > Another data point: I had an old FreeBSD 3.3 CD lying around, so I tried > that, and sure enough it works! No problems and I get past the kernel > initial boot. > > So OK chaps... What does it all mean? Install nasm and do the dd pipe Mike Smith suggested (the one on /dev/mem) so we have a guess on how to work around this. > Based on the evidence, I am inclined to say that there is a definite bug > in the FreeBSD 4.1.1 generic kernel. I mean hay! FreeBSD 3.3 boots up > fine on the exact same hardware. 3.3 didn't have VM86 support in the kernel by default. Booting a 3.3 kernel with VM86 will probably crash as well. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Dec 13 15:35: 2 2000 From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 13 15:34:56 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mail.monkeys.com (236.dsl9226.rcsis.com [63.92.26.236]) by hub.freebsd.org (Postfix) with ESMTP id 6FA3737B402; Wed, 13 Dec 2000 15:34:56 -0800 (PST) Received: from monkeys.com (236.dsl9226.rcsis.com [63.92.26.236]) by mail.monkeys.com (8.11.1/8.11.1) with ESMTP id eBDNYtw40533; Wed, 13 Dec 2000 15:34:55 -0800 (PST) To: John Baldwin Cc: freebsd-hardware@FreeBSD.org, freebsd-questions@FreeBSD.org, Mike Smith Subject: Re: Help! "Fatal trap 1: privledged instruction trap" while inst In-reply-to: Your message of Wed, 13 Dec 2000 15:22:41 -0800. Date: Wed, 13 Dec 2000 15:34:55 -0800 Message-ID: <40531.976750495@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message , you wrote: > >On 13-Dec-00 Ronald F. Guilmette wrote: >> >> In message <200012132120.eBDLKr310117@mass.osd.bsdi.com>, >> Mike Smith wrote: >> >>>Also, the VESA code isn't in GENERIC, says he just looking. >>> >>>I'm sorry; I don't have any other great ideas. Try a new video card. 8) >> >> OK. I went today and bought a new ATI Xpert 98 video card. >> >> I installed it into the system in question. >> >> I tried to install FreeBSD again. >> >> Still no-go. I am getting EXACTLY the same error as before at EXACTLY >> the same point in the process. >> >> Another data point: I had an old FreeBSD 3.3 CD lying around, so I tried >> that, and sure enough it works! No problems and I get past the kernel >> initial boot. >> >> So OK chaps... What does it all mean? > >Install nasm and do the dd pipe Mike Smith suggested (the one on /dev/mem) so >we have a guess on how to work around this. As I pointed out to Mike Smith, I can't install _anything_ because I haven't even installed FreeBSD yet. As I noted earlier, I can't even get past the kernel boot up process that's being done at the beginning of the FreeBSD install. Thus I haven't even installed FreeBSD on this system yet. It has only blank/empty disk drives on it. >> Based on the evidence, I am inclined to say that there is a definite bug >> in the FreeBSD 4.1.1 generic kernel. I mean hay! FreeBSD 3.3 boots up >> fine on the exact same hardware. > >3.3 didn't have VM86 support in the kernel by default. Ah ha! So this is what has changed between 3.3 and 4.1.1. That vm86 stuff is obviously what is causing the problem. MORE DATA: Since I have already swapped just about every other component on this system (except the motherboard and the case) I tried yanking out the good old reliable Adaptech 1542CP (ISA) SCSI controller and then tried using a pair of FreeBSD 4.1 install floppies (kernel and mfsroot) to get to the kernel boot stage. I did that, and lo and behold if it didn't boot the kernel just fine. I just tried the exact same experiment, only this time with an Adaptech 2940AU (PCI) SCSI controller in the system in place of the 1542CP and THAT ALSO WORKED JUST FINE. CONCLUSION: Those good old reliable Adaptech 1542CP SCSI controllers seem to be incompatible with FreeBSD 4.1.1 and its vm86 mode. That's a real shame since these cards *did* formerly work with FreeBSD, and I really was counting on being able to use that card in this system. :-( >Booting a 3.3 kernel with VM86 will probably crash as well. I'm ignorant. Please tell me, very exactly, how I would test that theory. I will then be very happy to try it and report back my results. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Dec 13 16: 8:34 2000 From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 13 16:08:30 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 1DCD137B69C; Wed, 13 Dec 2000 16:08:27 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eBE08CE48360; Wed, 13 Dec 2000 16:08:12 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <40531.976750495@monkeys.com> Date: Wed, 13 Dec 2000 16:08:22 -0800 (PST) From: John Baldwin To: "Ronald F. Guilmette" Subject: Re: Help! "Fatal trap 1: privledged instruction trap" while inst Cc: Mike Smith , freebsd-questions@FreeBSD.org, freebsd-hardware@FreeBSD.org Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 13-Dec-00 Ronald F. Guilmette wrote: > In message , you wrote: >>Install nasm and do the dd pipe Mike Smith suggested (the one on /dev/mem) so >>we have a guess on how to work around this. > > As I pointed out to Mike Smith, I can't install _anything_ because I haven't > even installed FreeBSD yet. Install FreeBSD 3.3, then install nasm and run the dd command. :) >>Booting a 3.3 kernel with VM86 will probably crash as well. > > I'm ignorant. Please tell me, very exactly, how I would test that theory. > I will then be very happy to try it and report back my results. Compile a custom kernel with "options VM86" in the config file. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Dec 13 16:18:50 2000 From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 13 16:18:46 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mail.monkeys.com (236.dsl9226.rcsis.com [63.92.26.236]) by hub.freebsd.org (Postfix) with ESMTP id CE19737B698; Wed, 13 Dec 2000 16:18:45 -0800 (PST) Received: from monkeys.com (236.dsl9226.rcsis.com [63.92.26.236]) by mail.monkeys.com (8.11.1/8.11.1) with ESMTP id eBE0Ijw40807; Wed, 13 Dec 2000 16:18:45 -0800 (PST) To: John Baldwin Cc: Mike Smith , freebsd-questions@FreeBSD.org, freebsd-hardware@FreeBSD.org Subject: Re: Help! "Fatal trap 1: privledged instruction trap" while inst In-reply-to: Your message of Wed, 13 Dec 2000 16:08:22 -0800. Date: Wed, 13 Dec 2000 16:18:45 -0800 Message-ID: <40805.976753125@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message , you wrote: > >On 13-Dec-00 Ronald F. Guilmette wrote: >> In message , you wrote: >>>Install nasm and do the dd pipe Mike Smith suggested (the one on /dev/mem) s >o >>>we have a guess on how to work around this. >> >> As I pointed out to Mike Smith, I can't install _anything_ because I haven't >> even installed FreeBSD yet. > >Install FreeBSD 3.3, then install nasm and run the dd command. :) This is more work that I care to undertake at the moment. I'm just going to use my AHA-2940AU instead and throw the AHA-1542CP in the fireplace (to get burned up with the rest of the trash). >>>Booting a 3.3 kernel with VM86 will probably crash as well. >> >> I'm ignorant. Please tell me, very exactly, how I would test that theory. >> I will then be very happy to try it and report back my results. > >Compile a custom kernel with "options VM86" in the config file. See above. This is more work that I care to undertake right now. I'm just going to file a PR on all of this and then see if any of the kernel hackers give a darn about still supporting the crusty old AHA-154x cards. P.S. Anybody want to buy a video card? I seem to have some extras all of a sudden. :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Dec 13 17:29:15 2000 From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 13 17:29:14 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from web4502.mail.yahoo.com (web4502.mail.yahoo.com [216.115.105.63]) by hub.freebsd.org (Postfix) with SMTP id 2561237B698 for ; Wed, 13 Dec 2000 17:29:14 -0800 (PST) Message-ID: <20001214012914.6997.qmail@web4502.mail.yahoo.com> Received: from [63.171.147.12] by web4502.mail.yahoo.com; Wed, 13 Dec 2000 17:29:14 PST Date: Wed, 13 Dec 2000 17:29:14 -0800 (PST) From: Sean Blakey Subject: umass support for Iomega PocketZip/HipZip? To: freebsd-hardware@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anybody tried getting the USB Iomega PocketZip drives working under FreeBSD? Does it simply show up as a USB SCSI drive under the umass driver, like USB Zip drives? I ask because I am considering buying myself a HipZip player for Christmas. -Sean __________________________________________________ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Dec 14 3:14: 7 2000 From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 14 03:14:00 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (unknown [167.216.157.206]) by hub.freebsd.org (Postfix) with ESMTP id BDBF137B400; Thu, 14 Dec 2000 03:13:59 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBEBMr901509; Thu, 14 Dec 2000 03:22:53 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012141122.eBEBMr901509@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Ronald F. Guilmette" Cc: Mike Smith , John Baldwin , freebsd-questions@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Help! "Fatal trap 1: privledged instruction trap" while inst In-reply-to: Your message of "Wed, 13 Dec 2000 14:50:41 PST." <40355.976747841@monkeys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Dec 2000 03:22:53 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > >Also, the VESA code isn't in GENERIC, says he just looking. > > > >I'm sorry; I don't have any other great ideas. Try a new video card. 8) > > OK. I went today and bought a new ATI Xpert 98 video card. > > I installed it into the system in question. > > I tried to install FreeBSD again. > > Still no-go. I am getting EXACTLY the same error as before at EXACTLY > the same point in the process. Ok, so it's not the VESA BIOS. 8) I'm a little puzzled as to what the SCSI controller BIOS is doing being called at this point in time (the only other candidate). > Based on the evidence, I am inclined to say that there is a definite bug > in the FreeBSD 4.1.1 generic kernel. I mean hay! FreeBSD 3.3 boots up > fine on the exact same hardware. No, the bug is in the BIOS code. We're just tripping over it. > Assuming that it is one, where should I turn for further assistance? Get a BIOS update for the controller. I know that people are using 154x -family controllers with FreeBSD-4.x systems (because they get upset when things get broken elsewhere 8). -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Dec 14 3:36:46 2000 From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 14 03:36:41 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mail.monkeys.com (236.dsl9226.rcsis.com [63.92.26.236]) by hub.freebsd.org (Postfix) with ESMTP id 3014737B400; Thu, 14 Dec 2000 03:36:39 -0800 (PST) Received: from monkeys.com (236.dsl9226.rcsis.com [63.92.26.236]) by mail.monkeys.com (8.11.1/8.11.1) with ESMTP id eBEBacw43364; Thu, 14 Dec 2000 03:36:38 -0800 (PST) To: Mike Smith Cc: John Baldwin , freebsd-questions@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Help! "Fatal trap 1: privledged instruction trap" while inst In-reply-to: Your message of Thu, 14 Dec 2000 03:22:53 -0800. <200012141122.eBEBMr901509@mass.osd.bsdi.com> Date: Thu, 14 Dec 2000 03:36:38 -0800 Message-ID: <43362.976793798@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200012141122.eBEBMr901509@mass.osd.bsdi.com>, you wrote: >> >> >Also, the VESA code isn't in GENERIC, says he just looking. >> > >> >I'm sorry; I don't have any other great ideas. Try a new video card. 8) >> >> OK. I went today and bought a new ATI Xpert 98 video card. >> >> I installed it into the system in question. >> >> I tried to install FreeBSD again. >> >> Still no-go. I am getting EXACTLY the same error as before at EXACTLY >> the same point in the process. > >Ok, so it's not the VESA BIOS. 8) I'm a little puzzled as to what the >SCSI controller BIOS is doing being called at this point in time (the only >other candidate). > >> Based on the evidence, I am inclined to say that there is a definite bug >> in the FreeBSD 4.1.1 generic kernel. I mean hay! FreeBSD 3.3 boots up >> fine on the exact same hardware. > >No, the bug is in the BIOS code. We're just tripping over it. I don't think so. I filed a detailed PR on this whole problem, and someone responded to that already saying that he's pretty sure that the problem is fixed (again) in FreeBSD 4.2. The AHA-1542CP card is perfectly OK... It's just that FreeBSD 4.1 was expecting a little to much from it. I hope and believe that is rectified in 4.2. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Dec 14 8:45:56 2000 From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 14 08:45:54 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from sumamail.com (ono.sumamail.com [207.38.123.83]) by hub.freebsd.org (Postfix) with ESMTP id 9DD7337B404; Thu, 14 Dec 2000 08:45:53 -0800 (PST) Received: from [209.131.32.217] (HELO MRZcx904008a) by sumamail.com (CommuniGate Pro SMTP 3.4b7) with SMTP id 271116; Thu, 14 Dec 2000 08:45:52 -0800 Message-ID: <002b01c065ed$5a03b1e0$d92083d1@MRZcx904008a> From: "matthew zeier" To: , Subject: dell poweredge 2450 + raid Date: Thu, 14 Dec 2000 08:46:03 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anyone have any experience with the DELL PowerEdge 2450 with any of their hardware RAID solutions? Either the PERC2 or "motherboard RAID" whatever that is). I need to support booting off RAID like I can with a Mylex controller. Thanks. -- matthew zeier - "There ain't no rules around here. We're trying to accomplish something." - Thomas Edison To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Dec 14 9: 0:30 2000 From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 14 09:00:25 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mail.wlcg.com (mail.wlcg.com [207.226.17.4]) by hub.freebsd.org (Postfix) with ESMTP id F23B337B400; Thu, 14 Dec 2000 09:00:24 -0800 (PST) Received: from localhost (rsimmons@localhost) by mail.wlcg.com (8.11.1/8.11.1) with ESMTP id eBEH0Qx55190; Thu, 14 Dec 2000 12:00:27 -0500 (EST) (envelope-from rsimmons@wlcg.com) Date: Thu, 14 Dec 2000 12:00:26 -0500 (EST) From: Rob Simmons To: matthew zeier Cc: freebsd-questions@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: dell poweredge 2450 + raid In-Reply-To: <002b01c065ed$5a03b1e0$d92083d1@MRZcx904008a> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Unfortunately we purchased a set of the 2400's with the same RAID card that you are talking about. It's the PERC2/Si. It is not supported as of yet. The only drivers that are available for it are binary-only drivers for RedHat. Since the Dell rep that I talked to when I bought it misled me into thinking that drivers were available outside of RedHat, I was able to get Dell to send me replacement RAID cards made by American Megatrends, which have the same performance as the PERC2/Si and are supported by the amr driver in FreeBSD. Good luck! Robert Simmons Systems Administrator http://www.wlcg.com/ On Thu, 14 Dec 2000, matthew zeier wrote: > > Does anyone have any experience with the DELL PowerEdge 2450 with any of > their hardware RAID solutions? Either the PERC2 or "motherboard RAID" > whatever that is). > > I need to support booting off RAID like I can with a Mylex controller. > > Thanks. > > -- > matthew zeier - "There ain't no rules around here. We're trying to > accomplish something." - Thomas Edison > > > > 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 Fri Dec 15 8: 6:44 2000 From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 15 08:06:42 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from excalibur.dotcom.fr (ns.dotcom.fr [195.154.74.11]) by hub.freebsd.org (Postfix) with ESMTP id 4A0B437B400 for ; Fri, 15 Dec 2000 08:06:42 -0800 (PST) Received: from IPricot.com (pc181.fr.ipricot.com [192.168.31.181]) by excalibur.dotcom.fr (8.9.1/8.9.1) with ESMTP id QAA27470 for ; Fri, 15 Dec 2000 16:06:35 GMT X-To: Sender: roman@IPricot.com Message-ID: <3A3A418A.6CB4084F@IPricot.com> Date: Fri, 15 Dec 2000 17:06:34 +0100 From: Roman Le Houelleur Organization: dotcom X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-20000912-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: "hardware@FreeBSD.ORG" Subject: ether card for dummynet Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hello, I'm about to build a bridge that will use the dummynet system. I would like to known what are the recommended ethernet cards to use in this case. I've had a look at the Intel etherexpress, but this one is quite expensive, so if there are low cost cardsthat can do the job, please let me know. What about the realtek 8139 (rl driver) ? Thanks, Roman. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Dec 15 8:11: 3 2000 From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 15 08:11:00 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from gate.trident-uk.co.uk (mail.trident-uk.co.uk [195.166.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 1146F37B400; Fri, 15 Dec 2000 08:10:59 -0800 (PST) Received: from [194.207.93.139] by gate.trident-uk.co.uk for freebsd-hardware@freebsd.org id QAA07238; Fri Dec 15 16:08:04 2000 Organization: Psi-Domain Ltd. Subject: ESS Sound Driver Date: Fri, 15 Dec 2000 16:10:09 +0000 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00121516132000.04421@freefire.psi-domain.co.uk> Content-Transfer-Encoding: 8bit To: freebsd-hardware@freebsd.org From: Jamie Heckford Reply-To: heckfordj@psi-domain.co.uk Cc: freebsd-stable@freebsd.org Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Could anyone offer any guidance on getting the following sound card to work? It is in a Samsung GT8700 laptop - and I am using FreeBSD 4.2-RELEASE. Windows identifies the card as an ESS Maestro PCI Audio (WDM) - IRQ 5 I have tried the sbc and pcm sound drivers - but with no joy. Here is some info at boot if it is of any help: pci0: (vendor=0x125d, dev=0x199a) at 12.0 pci0: (vendor=0x11c1, dev=0x0444) at 13.1 Thanks in advance for your help -- Jamie Heckford Chief Network Engineer Psi-Domain - Innovative Linux Solutions. Ask Us How. ===================================== email: heckfordj@psi-domain.co.uk web: http://www.psi-domain.co.uk/ tel: +44 (0)1737 789 246 fax: +44 (0)1737 789 245 mobile: +44 (0)7779 646 529 ===================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Dec 15 8:53:56 2000 From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 15 08:53:52 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from unix.megared.net.mx (megamail.megared.com.mx [200.52.207.52]) by hub.freebsd.org (Postfix) with ESMTP id 262F937B400; Fri, 15 Dec 2000 08:53:52 -0800 (PST) Received: from localhost (lcroker@localhost) by unix.megared.net.mx (8.11.0/8.11.0) with ESMTP id eBFGrrc51704; Fri, 15 Dec 2000 10:53:53 -0600 (CST) (envelope-from lcroker@unix.megared.net.mx) Date: Fri, 15 Dec 2000 10:53:52 -0600 (CST) From: Lu!s Croker To: Jamie Heckford Cc: freebsd-hardware@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: ESS Sound Driver In-Reply-To: <00121516132000.04421@freefire.psi-domain.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi... I have that output in the dmesg too... I have a sound card ESS Allegro 1930S and I haven't can configure it.... I have tried whith every drivers ein the kernel... If you know later, please tell me.. On Fri, 15 Dec 2000, Jamie Heckford wrote: > Hi, > > Could anyone offer any guidance on getting the following sound card to work? > > It is in a Samsung GT8700 laptop - and I am using FreeBSD 4.2-RELEASE. > > Windows identifies the card as an ESS Maestro PCI Audio (WDM) - IRQ 5 > > I have tried the sbc and pcm sound drivers - but with no joy. > > Here is some info at boot if it is of any help: > > pci0: (vendor=0x125d, dev=0x199a) at 12.0 > pci0: (vendor=0x11c1, dev=0x0444) at 13.1 > > Thanks in advance for your help > > -- > Jamie Heckford > Chief Network Engineer > Psi-Domain - Innovative Linux Solutions. Ask Us How. > > ===================================== > email: heckfordj@psi-domain.co.uk > web: http://www.psi-domain.co.uk/ > > tel: +44 (0)1737 789 246 > fax: +44 (0)1737 789 245 > mobile: +44 (0)7779 646 529 > ===================================== > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" 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 Fri Dec 15 15:19:57 2000 From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 15 15:19:55 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mercury.gfit.net (unknown [209.246.145.154]) by hub.freebsd.org (Postfix) with ESMTP id 9FE6B37B400 for ; Fri, 15 Dec 2000 15:19:55 -0800 (PST) Received: from paranor (roc-24-169-192-168.rochester.rr.com [24.169.192.168]) by mercury.gfit.net (8.8.8/8.8.8) with SMTP id RAA28687; Fri, 15 Dec 2000 17:29:06 -0600 (CST) (envelope-from tom@embt.com) Message-Id: <3.0.3.32.20001215182132.015b0640@embt.com> X-Sender: tembt@embt.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 15 Dec 2000 18:21:32 -0500 To: Roman Le Houelleur , "hardware@FreeBSD.ORG" From: Tom Embt Subject: Re: ether card for dummynet In-Reply-To: <3A3A418A.6CB4084F@IPricot.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I haven't had experience with building bridges, but as far as general NICs suitable for FreeBSD, this question has been asked before. The Intel Etherexpress stuff is about the best 10/100 card you'll find. Several "good" cards are made from the PNIC 82c169 chipset, including the Kingston KNE-110TX and the NetGear FA-310TX. One bonus to the FA310TX is that it has _five_ status LEDs on the back, and the Kingston has four. Most cards have three, or even two. Just these little things that you notice... I personally would avoid the Realtek based stuff. Current prices on http://www.mwave.com (love that place) Intel PRO/100+ WOL $41.00 NetGear FA-310TX $19.00 ..plus shipping of course Tom At 05:06 PM 12/15/00 +0100, Roman Le Houelleur wrote: >hello, > > I'm about to build a bridge that will >use the dummynet system. > I would like to known what are the recommended >ethernet cards to use in this case. > > I've had a look at the Intel etherexpress, but >this one is quite expensive, so if there are low >cost cardsthat can do the job, please let me know. > > What about the realtek 8139 (rl driver) ? > > Thanks, > >Roman. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Dec 15 16: 1: 5 2000 From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 15 16:01:04 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from evilcode.com (evilcode.com [63.228.228.140]) by hub.freebsd.org (Postfix) with SMTP id A2D0E37B400 for ; Fri, 15 Dec 2000 16:01:03 -0800 (PST) Received: (qmail 85144 invoked by uid 1000); 16 Dec 2000 00:01:02 -0000 Date: Fri, 15 Dec 2000 16:01:02 -0800 From: James To: freebsd-hardware@freebsd.org Subject: Promise FASTtrak66/RAID1 working? Message-ID: <20001215160102.A84096@evilcode.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: daemus@evilcode.com Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I understand that FreeBSD 4.2 (and before) does not support the Promise FASTtrak66 in a RAID setup. But being one that likes to see things for himself, I tried it out. When I was doing the install, and I got to the disk partitioning part, it gave me 3 choices: ad4, ad6, and ar0. Remembering that I saw it mention the ar0 as the RAID card when it booted, I tried this device out.. and I saw 30GB of space when I was creating the slice; something that one would expect when the RAID1 setup works.. but my understanding about this card is that it only works as a regular IDE controller, and none of the RAID features are useable in FreeBSD. And I also looked in the LINT kernel config file to see what ar0 was supposed to be, and found that it's description is "Arnet SYNC/570i hdlc sync 2/4 port V.35/X.21 serial driver (requires sppp)". Now I'm really confused about this. Why is my RAID1 configuration working at all? And why was this device seen as "ar0"? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Dec 15 16:11:47 2000 From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 15 16:11:46 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-28.dsl.snfc21.pacbell.net [63.202.177.28]) by hub.freebsd.org (Postfix) with ESMTP id A9DCF37B400 for ; Fri, 15 Dec 2000 16:11:45 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBG0Lfo05581; Fri, 15 Dec 2000 16:21:45 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012160021.eBG0Lfo05581@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: James Cc: freebsd-hardware@freebsd.org Subject: Re: Promise FASTtrak66/RAID1 working? In-reply-to: Your message of "Fri, 15 Dec 2000 16:01:02 PST." <20001215160102.A84096@evilcode.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Dec 2000 16:21:41 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I understand that FreeBSD 4.2 (and before) does not support > the Promise FASTtrak66 in a RAID setup. But being one that > likes to see things for himself, I tried it out. Actually, FreeBSD does support these cards in 4.2. The choice of "ar" was an unfortunate mistake on the part of the driver author. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Dec 15 16:25:27 2000 From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 15 16:25:25 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from evilcode.com (evilcode.com [63.228.228.140]) by hub.freebsd.org (Postfix) with SMTP id AC74737B400 for ; Fri, 15 Dec 2000 16:25:24 -0800 (PST) Received: (qmail 86490 invoked by uid 1000); 16 Dec 2000 00:25:24 -0000 Date: Fri, 15 Dec 2000 16:25:24 -0800 From: James To: freebsd-hardware@freebsd.org Subject: Re: Promise FASTtrak66/RAID1 working? Message-ID: <20001215162523.A86352@evilcode.com> Mail-Followup-To: James , freebsd-hardware@freebsd.org References: <20001215160102.A84096@evilcode.com> <200012160021.eBG0Lfo05581@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200012160021.eBG0Lfo05581@mass.osd.bsdi.com>; from msmith@freebsd.org on Fri, Dec 15, 2000 at 04:21:41PM -0800 Sender: daemus@evilcode.com Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Dec 15, 2000 at 04:21:41PM -0800, Mike Smith wrote: > > I understand that FreeBSD 4.2 (and before) does not support > > the Promise FASTtrak66 in a RAID setup. But being one that > > likes to see things for himself, I tried it out. > > Actually, FreeBSD does support these cards in 4.2. Hmm, that is very strange.. I could almost swear that I saw 4.2 mentioned in one of the previous questions. So, should I have used the ar0 device as the drive? Or would using either of the ad devices have worked the same? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Dec 15 18:54:10 2000 From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 15 18:54:09 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from ifour.com.br (unknown [200.236.148.68]) by hub.freebsd.org (Postfix) with SMTP id 6262637B400 for ; Fri, 15 Dec 2000 18:54:03 -0800 (PST) Received: (qmail 86992 invoked from network); 16 Dec 2000 00:00:45 -0000 Received: from port23.tdnet.com.br (HELO ifour.com.br) (200.236.148.123) by midas.ifour.com.br with SMTP; 16 Dec 2000 00:00:45 -0000 Sender: grios@FreeBSD.ORG Message-ID: <3A3ABCAE.1CF1638F@ifour.com.br> Date: Sat, 16 Dec 2000 00:51:58 +0000 From: Gustavo Vieira Goncalves Coelho Rios X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hardware@freebsd.org Subject: Asus A7V motherboard Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am seeking a high quality motherboard to buy, my choice is: Asus A7V! (http://www.asus.com/products/Motherboard/socketa/a7v/spec.html) But some questions raised: 1. Does FreeBSD support Onboard Promise® PCI-ATA100 Controller? 2. This motherboard chipset supports 200MHZ FSB, does that mean any problem for freebsd? 3. Is anyone here running freebsd over it? How stable is it? And about performance? Thanks a lot for your time and cooperation. best regards, Gustavo Rios To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Dec 15 19:46:16 2000 From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 15 19:46:14 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 9A15437B402 for ; Fri, 15 Dec 2000 19:46:14 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id D0DEC5745B; Fri, 15 Dec 2000 21:46:35 -0600 (CST) Date: Fri, 15 Dec 2000 21:46:35 -0600 From: "Michael C . Wu" To: James Cc: freebsd-hardware@freebsd.org Subject: Re: Promise FASTtrak66/RAID1 working? Message-ID: <20001215214635.A43778@peorth.iteration.net> Reply-To: "Michael C . Wu" Mail-Followup-To: "Michael C . Wu" , James , freebsd-hardware@freebsd.org References: <20001215160102.A84096@evilcode.com> <200012160021.eBG0Lfo05581@mass.osd.bsdi.com> <20001215162523.A86352@evilcode.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001215162523.A86352@evilcode.com>; from j@evilcode.com on Fri, Dec 15, 2000 at 04:25:24PM -0800 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: keichii@peorth.iteration.net Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Dec 15, 2000 at 04:25:24PM -0800, James scribbled: | On Fri, Dec 15, 2000 at 04:21:41PM -0800, Mike Smith wrote: | > > I understand that FreeBSD 4.2 (and before) does not support | > > the Promise FASTtrak66 in a RAID setup. But being one that | > > likes to see things for himself, I tried it out. | > | > Actually, FreeBSD does support these cards in 4.2. | | Hmm, that is very strange.. I could almost swear that I saw | 4.2 mentioned in one of the previous questions. | | So, should I have used the ar0 device as the drive? Or would | using either of the ad devices have worked the same? Use the ar0 if you want the RAID to work, and setup your ar0 configuration in the Promise card's BIOS. -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Dec 15 19:48:49 2000 From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 15 19:48:47 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from portnoy.lbl.gov (portnoy.lbl.gov [131.243.2.11]) by hub.freebsd.org (Postfix) with ESMTP id 9D23E37B404 for ; Fri, 15 Dec 2000 19:48:47 -0800 (PST) Received: (from jin@localhost) by portnoy.lbl.gov (8.11.1/8.11.1) id eBG3mD715576; Fri, 15 Dec 2000 19:48:13 -0800 (PST) Date: Fri, 15 Dec 2000 19:48:13 -0800 (PST) From: Jin Guojun (DSD staff) Message-Id: <200012160348.eBG3mD715576@portnoy.lbl.gov> To: gustavo@ifour.com.br, hardware@FreeBSD.ORG Subject: Re: Asus A7V motherboard Sender: jin@portnoy.lbl.gov Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I am seeking a high quality motherboard to buy, my choice is: Asus A7V! > (http://www.asus.com/products/Motherboard/socketa/a7v/spec.html) > > But some questions raised: > > 1. Does FreeBSD support Onboard Promise® PCI-ATA100 Controller? > 2. This motherboard chipset supports 200MHZ FSB, does that mean any > problem for freebsd? > 3. Is anyone here running freebsd over it? How stable is it? And about > performance? Short answer is: Nothing different from ASUS K7V except having a second IDE controller, a Promise ATA-100. Do not know what performance you are looking for. Again it is similar to ASUS K7V on everything if you know K7V. ---- I do not know how other ATA-100 controller works. I haven't tried the burst rate on this controller yet. The overall stream is as bad as the ATA-66 controller. Below is the problem. Two (2) WDC 100AA on two ATA-66 bus ----> 22.5 X 2 = 45 MBps Four (4) WDC 100AA on two ATA-66 bus ----> 85 MBps (super) Note the single drive rate that affects the entire IDE and PCI performance: WDC ATA-66 drive One (1) WDC 450AA on one ATA-66 bus ----> 23.5 (selected drives) Two (2) WDC 450AA on two ATA-66 bus ----> 23 X 2 = 46 MBps Four (4) WDC 450AA on two ATA-66 bus ----> 66 MBps (OK) Four (4) WDC 450AA on two ATA-66 bus and two ATA-100 ----> 85 MBps (OK) One (1) WDC 450AA on one ATA-66 bus ----> 24.5 (selected drives) Two (2) WDC 450AA on two ATA-66 bus ----> 23 X 2 = 46 MBps Four (4) WDC 450AA on two ATA-66 bus ----> 10.8 * 4 = 43 MBps (???) Maxtor ATA-100 drive One (1) Maxtor 54089U8 on one IDE ATA-66 --> 29.5 MBps Two (2) Maxtor 54089U8 on two IDE ATA-66 --> 29.5 X 2 = 59 MBps (OK) Four (4) Maxtor 54089U8 on two IDE ATA-66 --> 9.5 X 4 = 38 MBps (bad) I do not believe that is disk drive problem because you may see the selected WDC drive will make the bus behave differently. I was luck that I had such WDC drives worked at 24 MBps boundary. When the drive stream speed is slower than 24 MBps, the bus works well. When the single drive stream rate higher than 24 MBps, the controller has problem to arbitrate the bus between master and slave. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Dec 15 19:51:25 2000 From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 15 19:51:24 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from satan.freebsdsystems.com (satan.freebsdsystems.com [24.69.168.5]) by hub.freebsd.org (Postfix) with ESMTP id 52C9937B402 for ; Fri, 15 Dec 2000 19:51:23 -0800 (PST) Received: from satan.freebsdsystems.com (satan.freebsdsystems.com [24.69.168.5]) by satan.freebsdsystems.com (8.11.1/8.11.0) with ESMTP id eBG3p9878161 for ; Fri, 15 Dec 2000 22:51:22 -0500 (EST) Date: Fri, 15 Dec 2000 22:51:09 -0500 (EST) From: Lanny Baron To: hardware@FreeBSD.ORG Subject: Raid card question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, Would anyone know if InforTrend Sentinal Raid (external) are supported? Thanks for the response. Lanny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Dec 15 20:55:42 2000 From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 15 20:55:41 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from blotto.phreak.net (blotto.phreak.net [207.250.188.230]) by hub.freebsd.org (Postfix) with ESMTP id E988037B400 for ; Fri, 15 Dec 2000 20:55:40 -0800 (PST) Received: from phreak.net (localhost.phreak.net [127.0.0.1]) by blotto.phreak.net (Postfix) with SMTP id F19A29EE01; Fri, 15 Dec 2000 22:54:56 -0600 (CST) Received: from 207.250.188.69 (SquirrelMail authenticated user operator) by mail.phreak.net with HTTP; Fri, 15 Dec 2000 22:54:57 -0600 (CST) Message-ID: <3954.207.250.188.69.976942497.squirrel@mail.phreak.net> Date: Fri, 15 Dec 2000 22:54:57 -0600 (CST) Subject: Re: Raid card question From: "Operator" To: lnb@FreeBSDsystems.COM In-Reply-To: References: Cc: hardware@FreeBSD.ORG X-Mailer: SquirrelMail (version 0.5) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hello, > Would anyone know if InforTrend Sentinal Raid (external) are supported? > > Thanks for the response. > > Lanny > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > External controllers are OS independant which means you do not need any driver support, they can be used on *any* system that has SCSI support.. I've found that external controllers are MUCH better to deal with overall and tend to offer many more features. The Infortrends in particular are VERY nice, I've got quite a few Sential 2000s in production and have no problems, I love em! :) Good luck! -- Operator operator@phreak.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Dec 16 7:10:46 2000 From owner-freebsd-hardware@FreeBSD.ORG Sat Dec 16 07:10:44 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from satan.freebsdsystems.com (satan.freebsdsystems.com [24.69.168.5]) by hub.freebsd.org (Postfix) with ESMTP id AC6F537B400 for ; Sat, 16 Dec 2000 07:10:43 -0800 (PST) Received: from satan.freebsdsystems.com (satan.freebsdsystems.com [24.69.168.5]) by satan.freebsdsystems.com (8.11.1/8.11.0) with ESMTP id eBGFAZ887641; Sat, 16 Dec 2000 10:10:35 -0500 (EST) Date: Sat, 16 Dec 2000 10:10:35 -0500 (EST) From: Lanny Baron To: Operator Cc: hardware@FreeBSD.ORG Subject: Re: Raid card question In-Reply-To: <3954.207.250.188.69.976942497.squirrel@mail.phreak.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello Operator, Thank you very much for your reply :-) Have a good day or night where ever you are! regards, Lanny Baron http://www.FreeBDSsystems.COM On Dec 15, 2000, Operator in our continuing battle wrote: >> Hello, >> Would anyone know if InforTrend Sentinal Raid (external) are supported? >> >> Thanks for the response. >> >> Lanny >> >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-hardware" in the body of the message >> > >External controllers are OS independant which means you do not need >any driver support, they can be used on *any* system that has SCSI >support.. > >I've found that external controllers are MUCH better to deal with overall >and tend to offer many more features. The Infortrends in particular are >VERY nice, I've got quite a few Sential 2000s in production and have >no problems, I love em! :) > >Good luck! > > >-- >Operator >operator@phreak.net > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Dec 16 7:44:24 2000 From owner-freebsd-hardware@FreeBSD.ORG Sat Dec 16 07:44:20 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from satan.freebsdsystems.com (satan.freebsdsystems.com [24.69.168.5]) by hub.freebsd.org (Postfix) with ESMTP id B667737B404; Sat, 16 Dec 2000 07:44:14 -0800 (PST) Received: from satan.freebsdsystems.com (satan.freebsdsystems.com [24.69.168.5]) by satan.freebsdsystems.com (8.11.1/8.11.0) with ESMTP id eBGFiC887999; Sat, 16 Dec 2000 10:44:13 -0500 (EST) Date: Sat, 16 Dec 2000 10:44:12 -0500 (EST) From: Lanny Baron To: hardware@FreeBSD.ORG, questions@FreeBSD.ORG Subject: GFS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, Would anyone know if Global File Systems will work with FreeBSD? Thanks in advance for your reply :-) Regards, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Dec 16 9:18:59 2000 From owner-freebsd-hardware@FreeBSD.ORG Sat Dec 16 09:18:55 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4036B37B400; Sat, 16 Dec 2000 09:18:55 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id JAA01629; Sat, 16 Dec 2000 09:18:50 -0800 Date: Sat, 16 Dec 2000 09:18:42 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Lanny Baron Cc: hardware@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: GFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Not yet. There are several people, including somebody at Sistina, who want to make it happen. On Sat, 16 Dec 2000, Lanny Baron wrote: > Hello, > Would anyone know if Global File Systems will work with FreeBSD? > > Thanks in advance for your reply :-) > > Regards, > > > > > > > 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 Sat Dec 16 9:27:53 2000 From owner-freebsd-hardware@FreeBSD.ORG Sat Dec 16 09:27:51 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mail1.bna.bellsouth.net (mail1.bna.bellsouth.net [205.152.150.13]) by hub.freebsd.org (Postfix) with ESMTP id F194937B400 for ; Sat, 16 Dec 2000 09:27:50 -0800 (PST) Received: from planetwe.com (adsl-20-109-209.bna.bellsouth.net [66.20.109.209]) by mail1.bna.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id MAA29773; Sat, 16 Dec 2000 12:26:44 -0500 (EST) Message-ID: <3A3BA5DD.6030809@planetwe.com> Date: Sat, 16 Dec 2000 11:26:53 -0600 From: Drew Sanford User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.12 i386; en-US; m18) Gecko/20001107 Netscape6/6.0 X-Accept-Language: en MIME-Version: 1.0 To: Gustavo Vieira Goncalves Coelho Rios Cc: hardware@freebsd.org Subject: Re: Asus A7V motherboard References: <3A3ABCAE.1CF1638F@ifour.com.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gustavo Vieira Goncalves Coelho Rios wrote: > I am seeking a high quality motherboard to buy, my choice is: Asus A7V! > (http://www.asus.com/products/Motherboard/socketa/a7v/spec.html) > > But some questions raised: > > 1. Does FreeBSD support Onboard Promise® PCI-ATA100 Controller? Yes. > 2. This motherboard chipset supports 200MHZ FSB, does that mean any > problem for freebsd? No. > 3. Is anyone here running freebsd over it? How stable is it? And about > performance? Yes. Rock solid. It flies. > > Thanks a lot for your time and cooperation. No problem. > best regards, > > Gustavo Rios > > > 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 Sat Dec 16 9:31: 8 2000 From owner-freebsd-hardware@FreeBSD.ORG Sat Dec 16 09:31:05 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from satan.freebsdsystems.com (satan.freebsdsystems.com [24.69.168.5]) by hub.freebsd.org (Postfix) with ESMTP id 54A7D37B400; Sat, 16 Dec 2000 09:31:04 -0800 (PST) Received: from satan.freebsdsystems.com (satan.freebsdsystems.com [24.69.168.5]) by satan.freebsdsystems.com (8.11.1/8.11.0) with ESMTP id eBGHUv809702; Sat, 16 Dec 2000 12:31:01 -0500 (EST) Date: Sat, 16 Dec 2000 12:30:57 -0500 (EST) From: Lanny Baron To: Matthew Jacob Cc: hardware@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: GFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Matthew, Damm, this puts us in a very precarious position :-( Thanks for the reply, Regards, On Dec 16, 2000, Matthew Jacob in our continuing battle wrote: >Not yet. There are several people, including somebody at Sistina, who want to >make it happen. > > >On Sat, 16 Dec 2000, Lanny Baron wrote: > >> Hello, >> Would anyone know if Global File Systems will work with FreeBSD? >> >> Thanks in advance for your reply :-) >> >> Regards, >> >> >> >> >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-hardware" in the body of the message >> > > ------------------------------------------------------- Lanny Baron 1-877-963-1900 FreeBSD Systems, Inc Freedom Technologies Corporation Proud to be 100% FreeBSD http://www.FreeBSDsystems.COM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Dec 16 9:32:18 2000 From owner-freebsd-hardware@FreeBSD.ORG Sat Dec 16 09:32:14 2000 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A08D837B400; Sat, 16 Dec 2000 09:32:13 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id JAA01690; Sat, 16 Dec 2000 09:32:15 -0800 Date: Sat, 16 Dec 2000 09:32:07 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Lanny Baron Cc: hardware@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: GFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Uh, why? It's not clear when anyone will actually get to it. If you were planning to do it, get on it, buddy! On Sat, 16 Dec 2000, Lanny Baron wrote: > Hi Matthew, > Damm, this puts us in a very precarious position :-( > > Thanks for the reply, > > Regards, > > On Dec 16, 2000, Matthew Jacob in our continuing battle wrote: > > >Not yet. There are several people, including somebody at Sistina, who want to > >make it happen. > > > > > >On Sat, 16 Dec 2000, Lanny Baron wrote: > > > >> Hello, > >> Would anyone know if Global File Systems will work with FreeBSD? > >> > >> Thanks in advance for your reply :-) > >> > >> Regards, > >> > >> > >> > >> > >> > >> > >> To Unsubscribe: send mail to majordomo@FreeBSD.org > >> with "unsubscribe freebsd-hardware" in the body of the message > >> > > > > > > ------------------------------------------------------- > Lanny Baron > 1-877-963-1900 > FreeBSD Systems, Inc > Freedom Technologies Corporation > Proud to be 100% FreeBSD > http://www.FreeBSDsystems.COM > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message