From owner-freebsd-hardware@FreeBSD.ORG Sun Dec 28 22:03:24 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 830B716A4CE for ; Sun, 28 Dec 2003 22:03:24 -0800 (PST) Received: from iscan1.intra.oki.co.jp (okigate.oki.co.jp [202.226.91.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59A2943D2F for ; Sun, 28 Dec 2003 22:03:22 -0800 (PST) (envelope-from yamamoto436@oki.com) Received: from aoi.okilab.oki.co.jp (localhost.localdomain [127.0.0.1]) by iscan1.intra.oki.co.jp (8.9.3/8.9.3) with SMTP id PAA14190 for ; Mon, 29 Dec 2003 15:03:21 +0900 Received: (qmail 17182 invoked from network); 29 Dec 2003 15:03:20 +0900 Received: from tulip.okilab.oki.co.jp (172.24.23.187) by aoi.okilab.oki.co.jp with SMTP; 29 Dec 2003 15:03:20 +0900 Received: from localhost (tulip [172.24.23.187])hBT65hG5070423 for ; Mon, 29 Dec 2003 15:05:43 +0900 (JST) (envelope-from yamamoto436@oki.com) Date: Mon, 29 Dec 2003 15:05:42 +0900 (JST) Message-Id: <20031229.150542.41696894.yamamoto436@oki.com> To: freebsd-hardware@freebsd.org From: Hideki Yamamoto X-Mailer: Mew version 2.2 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Link up problem between 1000base-SX(bge) and SUN X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 06:03:24 -0000 Hello, I'm having a problem about link up between 1000base-SX(bge) and SUN. I tried yesterday's 4.9-stable on a FreeBSD box with two 3COM 3C996-SXs and two onboard BMC5703 chips. Two 3COM 3C996-SX board link went up, but the other side, a 1000base-SX I/F on SUN F280 did not go up. When doing ping command to SUN from FreeBSD box, LED on 3C996 were brinking but nothing happened to SUN board. I changed bge0 to bge2, but the situation was the same. Hardware diagram is as follows. bge0 can send or receive packates to the router or another PC with intel SX board. Is this related to AUTO negotiation? I cannot find any parameters about AUTO negotiation in 'bge' driver source. I checked Linux 2.4.22 kernel source and have found the several code about auto negotiation. I wonder if a linux box works well. I do not need full support of auto negotiation, but sample code that handles auto negotiation with Solaris machine. Any help would be greatly appreciated. Hideki Yamamoto +--------------+ | | | (bge0)3C996-SX+-----+[Router] | | | (bge2)3C996-SX+-----+[SUN F280] | | +--------------+ bge0: mem 0xf7ef0000-0xf7efffff irq 10 at device 1.0 on pci1 bge0: Ethernet address: 00:04:76:e1:06:cf bge1: mem 0xf7ee0000-0xf7eeffff irq 11 at device 2.0 on pci1 bge1: Ethernet address: 00:0b:cd:d2:b0:40 miibus0: on bge1 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto pcib2: on motherboard pci2: on pcib2 pcib3: on motherboard pci3: on pcib3 pcib4: on motherboard IOAPIC #1 intpin 10 -> irq 15 IOAPIC #1 intpin 13 -> irq 16 pci4: on pcib4 bge2: mem 0xf7ff0000-0xf7ffffff irq 15 at device 1.0 on pci4 bge2: Ethernet address: 00:0a:5e:1d:83:25 bge3: mem 0xf7fe0000-0xf7feffff irq 16 at device 2.0 on pci4 bge3: Ethernet address: 00:0b:cd:d2:b0:3b ----------------------------------------------------------------- Hideki YAMAMOTO Oki Electric Industry Co., Ltd. From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 29 01:18:21 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A44416A4CE for ; Mon, 29 Dec 2003 01:18:21 -0800 (PST) Received: from gaff.hhhr.ision.net (gaff.hhhr.ision.net [195.180.9.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36F0C43D2D for ; Mon, 29 Dec 2003 01:18:19 -0800 (PST) (envelope-from ohoyer@gaff.hhhr.ision.net) Received: from gaff.hhhr.ision.net (localhost [127.0.0.1]) by gaff.hhhr.ision.net (8.12.10/8.12.10) with ESMTP id hBT9IKVX065121; Mon, 29 Dec 2003 10:18:20 +0100 (CET) (envelope-from ohoyer@gaff.hhhr.ision.net) Received: from localhost (ohoyer@localhost)hBT9IJ7i065118; Mon, 29 Dec 2003 10:18:19 +0100 (CET) (envelope-from ohoyer@gaff.hhhr.ision.net) Date: Mon, 29 Dec 2003 10:18:18 +0100 (CET) From: Olaf Hoyer To: Hideki Yamamoto In-Reply-To: <20031229.150542.41696894.yamamoto436@oki.com> Message-ID: <20031229100720.X65076@gaff.hhhr.ision.net> References: <20031229.150542.41696894.yamamoto436@oki.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hardware@freebsd.org Subject: Re: Link up problem between 1000base-SX(bge) and SUN X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 09:18:21 -0000 On Mon, 29 Dec 2003, Hideki Yamamoto wrote: > > Hello, > > I'm having a problem about link up between 1000base-SX(bge) and SUN. > > I tried yesterday's 4.9-stable on a FreeBSD box with two 3COM > 3C996-SXs and two onboard BMC5703 chips. Two 3COM 3C996-SX board link > went up, but the other side, a 1000base-SX I/F on SUN F280 did not go > up. When doing ping command to SUN from FreeBSD box, LED on 3C996 > were brinking but nothing happened to SUN board. I changed bge0 to > bge2, but the situation was the same. Hardware diagram is as follows. > bge0 can send or receive packates to the router or another PC with > intel SX board. > > Is this related to AUTO negotiation? Hi! Sometimes SUN cards are a bit picky. But, lets start gathering additional data: I assume you have a ge-card in, or which card are you using in the 280? The man page says that autoneg is performed, but chooses : The GEM PCS is capable of performing auto-negotiation using the remote (or link partner) link end and receives the capabilities of the remote end. It selects the highest common demonina- tor mode of operation based on priorities. The ge driver also supports forced-mode operation under which the driver selects the mode of operation I assume that the interface is plumbed, and shows up in ifconfig as well, could you also post the snippet of the ifconfig entry? > I cannot find any parameters about AUTO negotiation in 'bge' driver > source. I checked Linux 2.4.22 kernel source and have found the > several code about auto negotiation. I wonder if a linux box works > well. I do not need full support of auto negotiation, but sample code > that handles auto negotiation with Solaris machine. in bge(4) it is stated, that the bge's also support autoneg over a cross-cable-config (which this basically is). But: have a look at the link0 option there (can be adjusted via ifconfig) normally, autoneg shall do, but over a cross-cable you need to designate one end being master, other end being slave. My suspicion is, that autoneg procedure somewhere fails, and you should try to set the bge to be link master. Just my 0.02 EUR -- Olaf Hoyer ohoyer@gaff.hhhr.ision.net Fuerchterliche Erlebniss geben zu raten, ob der, welcher sie erlebt, nicht etwas Fuerchterliches ist. (Nietzsche, Jenseits von Gut und Boese) From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 29 02:29:31 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB52E16A4CE for ; Mon, 29 Dec 2003 02:29:31 -0800 (PST) Received: from iscan1.intra.oki.co.jp (okigate.oki.co.jp [202.226.91.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF53D43D46 for ; Mon, 29 Dec 2003 02:29:28 -0800 (PST) (envelope-from yamamoto436@oki.com) Received: from aoi.okilab.oki.co.jp (localhost.localdomain [127.0.0.1]) by iscan1.intra.oki.co.jp (8.9.3/8.9.3) with SMTP id TAA10492 for ; Mon, 29 Dec 2003 19:29:27 +0900 Received: (qmail 25622 invoked from network); 29 Dec 2003 19:29:26 +0900 Received: from tulip.okilab.oki.co.jp (172.24.23.187) by aoi.okilab.oki.co.jp with SMTP; 29 Dec 2003 19:29:26 +0900 Received: from localhost (tulip [172.24.23.187])hBTAVqG5071086; Mon, 29 Dec 2003 19:31:52 +0900 (JST) (envelope-from yamamoto436@oki.com) Date: Mon, 29 Dec 2003 19:31:52 +0900 (JST) Message-Id: <20031229.193152.104097268.yamamoto436@oki.com> To: ohoyer@gaff.hhhr.ision.net From: Hideki Yamamoto In-Reply-To: <20031229100720.X65076@gaff.hhhr.ision.net> References: <20031229.150542.41696894.yamamoto436@oki.com> <20031229100720.X65076@gaff.hhhr.ision.net> X-Mailer: Mew version 2.2 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-hardware@freebsd.org Subject: Re: Link up problem between 1000base-SX(bge) and SUN X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 10:29:31 -0000 Hello again, Thank you for your reply. From: Olaf Hoyer Message-ID: <20031229100720.X65076@gaff.hhhr.ision.net> > On Mon, 29 Dec 2003, Hideki Yamamoto wrote: > > > > > Hello, > > > > I'm having a problem about link up between 1000base-SX(bge) and SUN. > > > > I tried yesterday's 4.9-stable on a FreeBSD box with two 3COM > > 3C996-SXs and two onboard BMC5703 chips. Two 3COM 3C996-SX board link > > went up, but the other side, a 1000base-SX I/F on SUN F280 did not go > > up. When doing ping command to SUN from FreeBSD box, LED on 3C996 > > were brinking but nothing happened to SUN board. I changed bge0 to > > bge2, but the situation was the same. Hardware diagram is as follows. > > bge0 can send or receive packates to the router or another PC with > > intel SX board. > > > > Is this related to AUTO negotiation? > > Hi! > > Sometimes SUN cards are a bit picky. > But, lets start gathering additional data: > > I assume you have a ge-card in, or which card are you using in the 280? > The man page says that autoneg is performed, but chooses : Yes, I have three 'ge' cards in one F280R. > > The GEM PCS is capable of performing auto-negotiation > using the remote (or link partner) link end and receives the > capabilities > of the remote end. It selects the highest common demonina- > tor mode of operation based on priorities. The ge driver > also supports forced-mode operation under which the driver > selects the mode of operation > > > > > I assume that the interface is plumbed, and shows up in ifconfig as > well, could you also post the snippet of the ifconfig entry? The machine is in a data center now. I cannot type ifconfig now. > > I cannot find any parameters about AUTO negotiation in 'bge' driver > > source. I checked Linux 2.4.22 kernel source and have found the > > several code about auto negotiation. I wonder if a linux box works > > well. I do not need full support of auto negotiation, but sample code > > that handles auto negotiation with Solaris machine. > > in bge(4) it is stated, that the bge's also support autoneg over a > cross-cable-config (which this basically is). > But: have a look at the link0 option there (can be adjusted via > ifconfig) normally, autoneg shall do, but over a cross-cable you need to > designate one end being master, other end being slave. > > My suspicion is, that autoneg procedure somewhere fails, and you should > try to set the bge to be link master. > Thank you for your advice. I am reading both FreeBSD and Linux driver. The following seems the definition of link master of Linux kernel source code in 'tg3.h'. -------------- |/* Tigon3 specific PHY MII registers. */ |#define TG3_BMCR_SPEED1000 0x0040 | |#define MII_TG3_CTRL 0x09 /* 1000-baseT control register */ |#define MII_TG3_CTRL_ADV_1000_HALF 0x0100 |#define MII_TG3_CTRL_ADV_1000_FULL 0x0200 |#define MII_TG3_CTRL_AS_MASTER 0x0800 |#define MII_TG3_CTRL_ENABLE_AS_MASTER 0x1000 -------------- In 'tg3.c', the following code seems to set the link master. ------------------------------------------ | if (tp->link_config.advertising & | (ADVERTISED_1000baseT_Half | ADVERTISED_1000baseT_Full)) { | new_adv = 0; | - | - | if (!(tp->tg3_flags & TG3_FLAG_10_100_ONLY) && | (tp->pci_chip_rev_id == CHIPREV_ID_5701_A0 || | tp->pci_chip_rev_id == CHIPREV_ID_5701_B0)) | new_adv |= (MII_TG3_CTRL_AS_MASTER | | MII_TG3_CTRL_ENABLE_AS_MASTER); | tg3_writephy(tp, MII_TG3_CTRL, new_adv); | - | - | } ------------------------------------------ In 'if_bge.c' in FreeBSD kernel, the following function seems problem, because it checks only IFM_1000_TX. I feel that IFM_1000_SX also have to be checked. I have another strange thing about 'dmesg' I showed in the original mail. Both bge0 and bge1 which specifiy SX cards did not have miibus or PHY in dmesg. Is this related to the link-up problem? ------------------------------------------ |static void |bge_miibus_statchg(dev) | device_t dev; |{ | struct bge_softc *sc; | struct mii_data *mii; | | sc = device_get_softc(dev); | mii = device_get_softc(sc->bge_miibus); | | BGE_CLRBIT(sc, BGE_MAC_MODE, BGE_MACMODE_PORTMODE); | if (IFM_SUBTYPE(mii->mii_media_active) == IFM_1000_TX) { | BGE_SETBIT(sc, BGE_MAC_MODE, BGE_PORTMODE_GMII); | } else { | BGE_SETBIT(sc, BGE_MAC_MODE, BGE_PORTMODE_MII); | } | | if ((mii->mii_media_active & IFM_GMASK) == IFM_FDX) { | BGE_CLRBIT(sc, BGE_MAC_MODE, BGE_MACMODE_HALF_DUPLEX); | } else { | BGE_SETBIT(sc, BGE_MAC_MODE, BGE_MACMODE_HALF_DUPLEX); | } | | return; |} ---------------------- > Just my 0.02 EUR > -- > Olaf Hoyer ohoyer@gaff.hhhr.ision.net > Fuerchterliche Erlebniss geben zu raten, > ob der, welcher sie erlebt, nicht etwas Fuerchterliches ist. > (Nietzsche, Jenseits von Gut und Boese) Regards, Hideki Yamammoto ----------------------------------------------------------------- Hideki YAMAMOTO | Broadband Media Solutions Department | E-mail: yamamoto436@oki.com Broadband Media Company | Tel: +81-3-3455-0870 Oki Electric Industry Co., Ltd. | FAX: +81-3-3798-7670 From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 29 07:26:06 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E822016A4CE for ; Mon, 29 Dec 2003 07:26:06 -0800 (PST) Received: from email05.aon.at (WARSL402PIP4.highway.telekom.at [195.3.96.79]) by mx1.FreeBSD.org (Postfix) with SMTP id 379E743D48 for ; Mon, 29 Dec 2003 07:26:05 -0800 (PST) (envelope-from m.hollmann@aon.at) Received: (qmail 269172 invoked from network); 29 Dec 2003 15:26:03 -0000 Received: from n471p029.adsl.highway.telekom.at (HELO aon.at) ([62.47.2.221]) (envelope-sender ) by qmail5rs.highway.telekom.at (qmail-ldap-1.03) with SMTP for ; 29 Dec 2003 15:26:03 -0000 Message-ID: <3FF04786.5070400@aon.at> Date: Mon, 29 Dec 2003 16:25:58 +0100 From: Michael Hollmann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030525 Thunderbird/0.1a X-Accept-Language: en-us, en MIME-Version: 1.0 To: hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: troubles with my nvidia card after update X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 15:26:07 -0000 my problem is (after upgrade kernel from 4.8.RC1 to 4.9.RELEASE): canīt shutdown my kde 3.1.xx: (EE) NVIDIA(0): Failed to destroy the primary surface i have allready insatlled and reinstalled the newest NVIDIA-Driver for FreeBSD. my graficcard is MSI GeForce4 Ti4200 64MB. i know, thatīs not the best choice for freebsd but i needed it for windows. please, could anybody help me? thanks, michael From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 29 08:28:02 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50AB716A4CE for ; Mon, 29 Dec 2003 08:28:02 -0800 (PST) Received: from smtpzilla1.xs4all.nl (smtpzilla1.xs4all.nl [194.109.127.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE9B343D69 for ; Mon, 29 Dec 2003 08:28:00 -0800 (PST) (envelope-from mcrosland@xs4all.nl) Received: from mojojojo (a80-126-82-35.adsl.xs4all.nl [80.126.82.35]) by smtpzilla1.xs4all.nl (8.12.9/8.12.9) with ESMTP id hBTGRxJ3040778 for ; Mon, 29 Dec 2003 17:27:59 +0100 (CET) Date: Mon, 29 Dec 2003 17:26:14 +0100 To: freebsd-hardware@freebsd.org From: Mike Crosland Content-Type: text/plain; format=flowed; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: User-Agent: Opera7.23/Win32 M2 build 3227 Subject: Terrattec DMX 6Fire X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 16:28:02 -0000 I already asked about this on multimedia, and had no response, so perhaps it was the wrong place to ask. Has anyone had success with the terratec DMX 6fire 24/96 audio card under 5.1? Mike -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 29 08:36:24 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C0F916A4CE; Mon, 29 Dec 2003 08:36:24 -0800 (PST) Received: from mv.milwaukeevalve.com (mail.milwaukeevalve.com [66.84.180.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0733F43D39; Mon, 29 Dec 2003 08:36:22 -0800 (PST) (envelope-from malexand@milwaukeevalve.com) Received: (from root@localhost) by mv.milwaukeevalve.com (8.11.6/8.11.6) id hBTGaLR31682; Mon, 29 Dec 2003 10:36:21 -0600 Received: from Pmjalex ([192.168.2.189]) (authenticated) by mv.milwaukeevalve.com (8.11.6/8.11.6) with ESMTP id hBTGaJe31626; Mon, 29 Dec 2003 10:36:19 -0600 From: "Michael Alexander" To: , Date: Mon, 29 Dec 2003 10:36:17 -0600 Message-ID: <01bc01c3ce29$e2b8aac0$bd02a8c0@Pmjalex> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-scanner: scanned by Inflex 1.0.12.7 Subject: Problems installing onto DAC960 (Mylex Acceleraid250) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 16:36:24 -0000 Hello, (Please excuse the cross post, I'm not sure if this is more a scsi or general hardware question, it can go eitherway) I had asked this question in freebsd-questions, but haven't been able = to receive a decent answer. A couple times I've gotten the answer that = FreeBSD may not install onto RAID at all, I can't believe that is correct. And = that RAID is just for user data, not the OS. Also working in the Netware = world, I know that RAID is important for the entire server, especially the OS. I am trying to install FreeBSD4.9 (or 5.1 even) on a system that uses = a Mylex Acceleraid250 (DAC960 driver) without success. The install CD = hangs when it attempts to spin up the drives on the raid, waiting 15 seconds = for scsi devices to settle is the last message on the screen. I found that there is a similar problem with RH9, but that they have a work around, = which involves recompiling the kernel and remaking the installation CDs. I = have the instructions for RH9, but I was hoping to be able to use FreeBSD. = If I can't get it installed though, I will have to go to RedHat instead. http://www.techonthenet.com/linux/rh9_update.htm is the instructions, it = is just a simple changing of two kernel options. Is this possibly the same reason that I cannot install FreeBSD? The two kernel options to be = changed are the following: # CONFIG_X86_UP_APIC is not set # CONFIG_X86_UP_IOAPIC is not set Change them to: CONFIG_X86_UP_APIC=3Dy CONFIG_X86_UP_IOAPIC=3Dy If so, are there instructions like the RH ones? I have never used = FreeBSD before, I have used RH7 and 8. Since RH is not really offering itself = free anymore, I thought I would give FreeBSD a try, and it also appears that FreeBSD is abit more current in its packages than RH has been. I do = have another machine I can install onto to make the changes. Since this = system is going to be a mail server for the company, we want to be able use = RAID for the entire system including boot. The system is fully up to date on bios and firmware for both MB and raid card. Thank you, Mike From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 29 09:14:30 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E971716A4CF for ; Mon, 29 Dec 2003 09:14:29 -0800 (PST) Received: from smtp.mho.com (smtp.mho.net [64.58.4.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 8566B43D39 for ; Mon, 29 Dec 2003 09:14:26 -0800 (PST) (envelope-from scottl@freebsd.org) Received: (qmail 9613 invoked by uid 1002); 29 Dec 2003 17:14:23 -0000 Received: from unknown (HELO freebsd.org) (64.58.1.252) by smtp.mho.net with SMTP; 29 Dec 2003 17:14:23 -0000 Message-ID: <3FF06091.4030307@freebsd.org> Date: Mon, 29 Dec 2003 10:12:49 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031103 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Alexander References: <01bc01c3ce29$e2b8aac0$bd02a8c0@Pmjalex> In-Reply-To: <01bc01c3ce29$e2b8aac0$bd02a8c0@Pmjalex> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-scsi@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: Problems installing onto DAC960 (Mylex Acceleraid250) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 17:14:30 -0000 Michael Alexander wrote: > Hello, > (Please excuse the cross post, I'm not sure if this is more a scsi or > general hardware question, it can go eitherway) > > I had asked this question in freebsd-questions, but haven't been able to > receive a decent answer. A couple times I've gotten the answer that FreeBSD > may not install onto RAID at all, I can't believe that is correct. And that > RAID is just for user data, not the OS. Also working in the Netware world, > I know that RAID is important for the entire server, especially the OS. You are correct, it is certainly possible to install the OS onto any RAID storage device that FreeBSD recognises. There is an issue with some low-end software raid controllers, but that does not apply here. > > I am trying to install FreeBSD4.9 (or 5.1 even) on a system that uses a > Mylex Acceleraid250 (DAC960 driver) without success. The install CD hangs > when it attempts to spin up the drives on the raid, waiting 15 seconds for > scsi devices to settle is the last message on the screen. I found that > there is a similar problem with RH9, but that they have a work around, which > involves recompiling the kernel and remaking the installation CDs. I have > the instructions for RH9, but I was hoping to be able to use FreeBSD. If I > can't get it installed though, I will have to go to RedHat instead. > http://www.techonthenet.com/linux/rh9_update.htm is the instructions, it is > just a simple changing of two kernel options. Is this possibly the same > reason that I cannot install FreeBSD? The two kernel options to be changed > are the following: > > > # CONFIG_X86_UP_APIC is not set > # CONFIG_X86_UP_IOAPIC is not set > > Change them to: > > CONFIG_X86_UP_APIC=y > CONFIG_X86_UP_IOAPIC=y > The hang at the 'Waiting 15 seconds...' is likely not related to SCSI. While the DAC960 card uses SCSI, it's FreeBSD driver does not attach through the SCSI subsystem at all. 99% os hangs that happen at this point are due to incorrect interrupt routing. The RedHat work-around appears to confirm this. There really is no fix for 5.1 and 4.9 unless you can experiment with moving the DAC960 to a different PCI slot. FreeBSD 5.2 has a much more comprehesive interrupt routing algorithm and will likely address your problem. If the 5.2 CD doesn't work, try booting it with ACPI disabled (either via the BIOS or the boot menu). > If so, are there instructions like the RH ones? I have never used FreeBSD > before, I have used RH7 and 8. Since RH is not really offering itself free > anymore, I thought I would give FreeBSD a try, and it also appears that > FreeBSD is abit more current in its packages than RH has been. I do have > another machine I can install onto to make the changes. Since this system > is going to be a mail server for the company, we want to be able use RAID > for the entire system including boot. The system is fully up to date on > bios and firmware for both MB and raid card. > Scott From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 29 09:43:17 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35EB216A4CE; Mon, 29 Dec 2003 09:43:17 -0800 (PST) Received: from mv.milwaukeevalve.com (mail.milwaukeevalve.com [66.84.180.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4392F43D70; Mon, 29 Dec 2003 09:42:57 -0800 (PST) (envelope-from linux@milwaukeevalve.com) Received: (from root@localhost) by mv.milwaukeevalve.com (8.11.6/8.11.6) id hBTHguF05649; Mon, 29 Dec 2003 11:42:56 -0600 Received: from Pmjalex ([192.168.2.189]) (authenticated) by mv.milwaukeevalve.com (8.11.6/8.11.6) with ESMTP id hBTHgqe05601; Mon, 29 Dec 2003 11:42:52 -0600 From: "michael Alexander" To: "'Scott Long'" , "'Michael Alexander'" Date: Mon, 29 Dec 2003 11:42:49 -0600 Message-ID: <01bd01c3ce33$2f96ece0$bd02a8c0@Pmjalex> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 In-Reply-To: <3FF06091.4030307@freebsd.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-scanner: scanned by Inflex 1.0.12.7 cc: freebsd-scsi@freebsd.org cc: freebsd-hardware@freebsd.org Subject: RE: Problems installing onto DAC960 (Mylex Acceleraid250) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 17:43:17 -0000 > The hang at the 'Waiting 15 seconds...' is likely not related to SCSI. > While the DAC960 card uses SCSI, it's FreeBSD driver does not attach > through the SCSI subsystem at all. 99% os hangs that happen at this > point are due to incorrect interrupt routing. The RedHat work-around > appears to confirm this. There really is no fix for 5.1 and > 4.9 unless > you can experiment with moving the DAC960 to a different PCI slot. > FreeBSD 5.2 has a much more comprehesive interrupt routing > algorithm and > will likely address your problem. If the 5.2 CD doesn't work, try > booting it with ACPI disabled (either via the BIOS or the boot menu). Will the miniinst be good enough to at least let me know if it is going to work or not? -Mike From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 29 10:33:28 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9BE916A4CE for ; Mon, 29 Dec 2003 10:33:28 -0800 (PST) Received: from smtp.mho.com (smtp.mho.net [64.58.4.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 4E53743D41 for ; Mon, 29 Dec 2003 10:33:25 -0800 (PST) (envelope-from scottl@freebsd.org) Received: (qmail 16331 invoked by uid 1002); 29 Dec 2003 18:33:22 -0000 Received: from unknown (HELO ?10.4.1.5?) (64.58.1.252) by smtp.mho.net with SMTP; 29 Dec 2003 18:33:22 -0000 Date: Mon, 29 Dec 2003 11:34:57 -0700 (MST) From: Scott Long X-X-Sender: scottl@pooker.samsco.home To: michael Alexander In-Reply-To: <01bd01c3ce33$2f96ece0$bd02a8c0@Pmjalex> Message-ID: <20031229113357.T93058@pooker.samsco.home> References: <01bd01c3ce33$2f96ece0$bd02a8c0@Pmjalex> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: 'Michael Alexander' cc: freebsd-scsi@freebsd.org cc: freebsd-hardware@freebsd.org Subject: RE: Problems installing onto DAC960 (Mylex Acceleraid250) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 18:33:28 -0000 On Mon, 29 Dec 2003, michael Alexander wrote: > > The hang at the 'Waiting 15 seconds...' is likely not related to SCSI. > > While the DAC960 card uses SCSI, it's FreeBSD driver does not attach > > through the SCSI subsystem at all. 99% os hangs that happen at this > > point are due to incorrect interrupt routing. The RedHat work-around > > appears to confirm this. There really is no fix for 5.1 and > > 4.9 unless > > you can experiment with moving the DAC960 to a different PCI slot. > > FreeBSD 5.2 has a much more comprehesive interrupt routing > > algorithm and > > will likely address your problem. If the 5.2 CD doesn't work, try > > booting it with ACPI disabled (either via the BIOS or the boot menu). > > Will the miniinst be good enough to at least let me know if it is going to > work or not? > > -Mike > > > Yes. In fact, the bootonly image can serve as a good smoke test for this. Scott From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 29 11:06:35 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3498416A4CE for ; Mon, 29 Dec 2003 11:06:35 -0800 (PST) Received: from smtp3.sentex.ca (smtp3.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1EA943D1F for ; Mon, 29 Dec 2003 11:03:22 -0800 (PST) (envelope-from damian@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smtp3.sentex.ca (8.12.10/8.12.10) with ESMTP id hBTJ1qHF043817; Mon, 29 Dec 2003 14:01:52 -0500 (EST) (envelope-from damian@sentex.net) Received: from pegmatite.sentex.ca (pegmatite.sentex.ca [192.168.42.92]) by lava.sentex.ca (8.12.9p2/8.12.9) with ESMTP id hBTJ1tXv033763; Mon, 29 Dec 2003 14:01:55 -0500 (EST) (envelope-from damian@sentex.net) Received: by pegmatite.sentex.ca (Postfix, from userid 1001) id 07209171CE; Mon, 29 Dec 2003 14:01:46 -0500 (EST) Date: Mon, 29 Dec 2003 14:01:46 -0500 From: Damian Gerow To: admin@forkthepenguin.com Message-ID: <20031229190146.GR883@sentex.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-GPG-Key-Id: 0xB841F142 X-GPG-Fingerprint: C7C1 E1D1 EC06 7C86 AF7C 57E6 173D 9CF6 B841 F142 X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-new cc: freebsd-hardware@freebsd.org Subject: Re: Kernel Optimizations for Processors X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 19:06:35 -0000 Thus spake admin@forkthepenguin.com (admin@forkthepenguin.com) [28/12/03 00:16]: > Is there a method for determining what options can be incorporated for a > specific processor? The unit in question is a VIA C3 Samuel2 processor > running at 800 Mhz. I've found many clues that this uses Cyrix > instructions although the chipset uses the Centaur core. This is supposed > to be an i686, but I've seen some issues on a Linux system with the same > processor that required the kernel to be built with i586. There's been a number of discussions about this over the past few months. Take a quick peak through the archives. In short: the GCC folk (at least for 2.95.x) assume that a 686-compatible chip understands CMOV. *Some* of the C3 cores understand it, others do not. I was under the impression that the Samuel2 /did/ understand it. Understanding CMOV is not a requirement for 686. I know for a fact that the Ezra and Ezra-T chips (what I'm using) do *not* understand CMOV. I think you get ever-so-slightly better performance if you set your ARCH to k6-2, though I use mine as i586/mmx. As for the kernel configuration, I left mine at I686_CPU, as the C3 /is/ a 686-class CPU. I think the history of the C3 is that VIA bought out Cyrix and Centaur, and brought both of them together. Technically, the chip is Cyrix at its core, I *believe*. Correct me if I'm wrong. The newer chips (Nehemiah and on) are probably different. > # CPU_BTB_EN enables branch target buffer on Cyrix 5x86 (NOTE 1). This is a 686-class CPU, not a 586-class CPU. > # CPU_DIRECT_MAPPED_CACHE sets L1 cache of Cyrix 486DLC CPU in direct > # mapped mode. Default is 2-way set associative mode. Again -- 486 vs. 686. > # CPU_CYRIX_NO_LOCK enables weak locking for the entire address space > # of Cyrix 6x86 and 6x86MX CPUs by setting the NO_LOCK bit of CCR1. > # Otherwise, the NO_LOCK bit of CCR1 is cleared. (NOTE 3) Never used it. > # CPU_DISABLE_5X86_LSSER disables load store serialize (i.e. enables > # reorder). This option should not be used if you use memory mapped > # I/O device(s). Never used it. > # CPU_IORT defines I/O clock delay time (NOTE 1). Default values of > # I/O clock delay time on Cyrix 5x86 and 6x86 are 0 and 7,respectively > # (no clock delay). Never used it. > # CPU_RSTK_EN enables return stack on Cyrix 5x86 (NOTE 1). 586 vs. 686. > # CPU_WT_ALLOC enables write allocation on Cyrix 6x86/6x86MX and AMD > # K5/K6/K6-2 cpus. Used it, never bothered to see if it made a difference. > # CYRIX_CACHE_WORKS enables CPU cache on Cyrix 486 CPUs with cache > # flush at hold state. Never used it -- 486 vs. 686. > # CYRIX_CACHE_REALLY_WORKS enables (1) CPU cache on Cyrix 486 CPUs > # without cache flush at hold state, and (2) write-back CPU cache on > # Cyrix 6x86 whose revision < 2.7 (NOTE 2). Used it, never bothered to see if it made a difference. > # NO_F00F_HACK disables the hack that prevents Pentiums (and ONLY > # Pentiums) from locking up when a LOCK CMPXCHG8B instruction is > # executed. This option is only needed if I586_CPU is also defined, > # and should be included for any non-Pentium CPU that defines it. 'and ONLY Pentiums' > Copyright (c) 1992-2003 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 4.9-RELEASE #0: Mon Oct 27 17:51:09 GMT 2003 > root@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/GENERIC > Timecounter "i8254" frequency 1193182 Hz > CPU: VIA C3 Samuel 2 (801.82-MHz 686-class CPU) > Origin = "CentaurHauls" Id = 0x673 Stepping = 3 > Features=0x803035 Well, I guess the Samuel2 doesn't understand CMOV either. Maybe it was the Samuel that did...? Dunno. The Nehemiah does, though. From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 29 12:20:35 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BF4916A4CE for ; Mon, 29 Dec 2003 12:20:35 -0800 (PST) Received: from vp4.netgate.net (vp4.netgate.net [205.214.170.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE8D843D2D for ; Mon, 29 Dec 2003 12:20:33 -0800 (PST) (envelope-from admin@forkthepenguin.com) Received: from localhost (ibrew@localhost) by vp4.netgate.net (8.11.6/8.11.7) with ESMTP id hBTKKW323095; Mon, 29 Dec 2003 12:20:32 -0800 (PST) Date: Mon, 29 Dec 2003 12:20:32 -0800 (PST) From: admin@forkthepenguin.com X-X-Sender: ibrew@vp4.netgate.net To: Damian Gerow In-Reply-To: <20031229190146.GR883@sentex.net> Message-ID: References: <20031229190146.GR883@sentex.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hardware@freebsd.org Subject: Re: Kernel Optimizations for Processors X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 20:20:35 -0000 Damian, thanks for the reply. > There's been a number of discussions about this over the past few months. > Take a quick peak through the archives. I looked through the archives using the search on the FreeBSD site, and Google (summaries are nice to have) and I didn't see a whole lot on this. Perhaps I'm just using the wrong search terms or getting too many false positives. > In short: the GCC folk (at least for 2.95.x) assume that a 686-compatible > chip understands CMOV. *Some* of the C3 cores understand it, others do not. > I was under the impression that the Samuel2 /did/ understand it. > Understanding CMOV is not a requirement for 686. OK, that clears things up a bit. I see now that this is listed in the "Features" in dmesg on a PentiumIII system. I found the following on the via site that discusses CMOV and is also related to the CMPXCHG8B code )see NO_F00F_HACK below). http://www.viaarena.com/?PageID=377 > I think you get ever-so-slightly better performance if you set your ARCH to > k6-2, though I use mine as i586/mmx. As for the kernel configuration, I > left mine at I686_CPU, as the C3 /is/ a 686-class CPU. What kernel option do you use for k6-2? I don't see anything in LINT or GENERIC. Also, what do you mean by "I use mine as i586/mmx"? Is this another kernel option? > > # CPU_WT_ALLOC enables write allocation on Cyrix 6x86/6x86MX and AMD > > # K5/K6/K6-2 cpus. > > Used it, never bothered to see if it made a difference. > > # CYRIX_CACHE_REALLY_WORKS enables (1) CPU cache on Cyrix 486 CPUs > > # without cache flush at hold state, and (2) write-back CPU cache on > > # Cyrix 6x86 whose revision < 2.7 (NOTE 2). > > Used it, never bothered to see if it made a difference. > > > # NO_F00F_HACK disables the hack that prevents Pentiums (and ONLY > > # Pentiums) from locking up when a LOCK CMPXCHG8B instruction is > > # executed. This option is only needed if I586_CPU is also defined, > > # and should be included for any non-Pentium CPU that defines it. > > 'and ONLY Pentiums' It also says "should be included for any non-Pentium CPU that defines it" but how do you know if the C# defines this? Is this another item that would show up in the "Features" list? I looked at a PI-133 I have and don't see it : CPU: Pentium/P54C (133.16-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x3bf I have a PII-300 running Fedora, but dmesg doesn't show the features. I did find it in proc : grep flags /proc/cpuinfo flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov mmx But again, I don't see anything like CMPXCHG8B (which apparently stands for "Compare and Exchange Eight Bytes". I did fint a thread on the OpenBSD list the eludes that the VIA Cyrix III supports this : http://www.monkey.org/openbsd/archive/bugs/0103/msg00127.html This feature is also reported in the C3 datasheet, it seems this is reported in the CPUID (Features) as CX8. http://www.viavpsd.com/product/6/13/%20VIA_C3_EBGA%20datasheet110.pdf So it seems like it "should be included for any non-Pentium CPU that defines it", but it sounds like it may not be an issue if this feature is implemented correctly... BTW, do you have problems with your system hanging on a reboot? I reported this as a bug (misc/60646) which I see has been reported at least twice before but nothing in the knats database shows it as being solved. Do you know of a fix for this? Thanks again, Chris From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 29 12:26:37 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E476B16A4CE for ; Mon, 29 Dec 2003 12:26:37 -0800 (PST) Received: from wrongcrowd.com (dsl231-036-178.sea1.dsl.speakeasy.net [216.231.36.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2E7D43D5F for ; Mon, 29 Dec 2003 12:26:36 -0800 (PST) (envelope-from matt@wrongcrowd.com) Received: from localhost ([::1] helo=wrongcrowd.com ident=nobody) by wrongcrowd.com with smtp (Exim 4.20) id 1Ab3xv-0002zc-7e for freebsd-hardware@freebsd.org; Mon, 29 Dec 2003 12:26:15 -0800 Received: from 207.46.125.17 (SquirrelMail authenticated user matt) by wrongcrowd.com with HTTP; Mon, 29 Dec 2003 12:26:15 -0800 (PST) Message-ID: <6412.207.46.125.17.1072729575.squirrel@wrongcrowd.com> In-Reply-To: <20031229200107.4D80916A4D9@hub.freebsd.org> References: <20031229200107.4D80916A4D9@hub.freebsd.org> Date: Mon, 29 Dec 2003 12:26:15 -0800 (PST) From: "Matt Staroscik" To: freebsd-hardware@freebsd.org User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/) *1Ab3xv-0002zc-7e*uXI9LCCJtPI* Subject: Re: Kernel Optimizations for Processors (Now AthlonXP Q) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: matt@wrongcrowd.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 20:26:38 -0000 > There's been a number of discussions about this over the past few months. > Take a quick peak through the archives. A while back I did a big Google session to try and find the best kernel and make flags for the AthlonXP proc (under FreeBSD 4.x). At the time, most of what I read said that the AthlonXP did best with (make.conf) CPUTYPE=i686, and the k7 flag just fell back to something like that anyway because there wasn't complete support for it yet in the compiler. Likewise my kernel is set to: cpu I686_CPU Is this advice still valid, if it ever was? Can anyone comment on the best make & kernel options for the AthlonXP CPU? -- matt@wrongcrowd.com From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 29 12:41:44 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE56A16A4CE for ; Mon, 29 Dec 2003 12:41:43 -0800 (PST) Received: from iscan1.intra.oki.co.jp (okigate.oki.co.jp [202.226.91.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CE7943D41 for ; Mon, 29 Dec 2003 12:41:39 -0800 (PST) (envelope-from yamamoto436@oki.com) Received: from aoi.okilab.oki.co.jp (localhost.localdomain [127.0.0.1]) by iscan1.intra.oki.co.jp (8.9.3/8.9.3) with SMTP id FAA24030 for ; Tue, 30 Dec 2003 05:41:37 +0900 Received: (qmail 4327 invoked from network); 30 Dec 2003 05:41:36 +0900 Received: from tulip.okilab.oki.co.jp (172.24.23.187) by aoi.okilab.oki.co.jp with SMTP; 30 Dec 2003 05:41:36 +0900 Received: from localhost (tulip [172.24.23.187])hBTKgO1f018567; Tue, 30 Dec 2003 05:42:24 +0900 (JST) (envelope-from yamamoto436@oki.com) Date: Tue, 30 Dec 2003 05:42:24 +0900 (JST) Message-Id: <20031230.054224.41627160.yamamoto436@oki.com> To: ohoyer@gaff.hhhr.ision.net From: Hideki Yamamoto In-Reply-To: <20031229.193152.104097268.yamamoto436@oki.com> References: <20031229.150542.41696894.yamamoto436@oki.com> <20031229100720.X65076@gaff.hhhr.ision.net> <20031229.193152.104097268.yamamoto436@oki.com> X-Mailer: Mew version 2.2 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-hardware@freebsd.org Subject: Re: Link up problem between 1000base-SX(bge) and SUN X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 20:41:44 -0000 Hi, I added code to recognize 3com 1000base-SX card as miibus module and compiled them, but I do not have time to test yet. I think this may solove my original problem that link of SUN SX card does not go up, though 3com card goes up well. I will start testing it from Jan.4,2004. I uploaded the fixed code on my web page, http://members.aol.com/hyama99/. I appreciate If someone gives me comments on the code before testing. Regards, Hideki Yamamoto From: Hideki Yamamoto Subject: Re: Link up problem between 1000base-SX(bge) and SUN Date: Mon, 29 Dec 2003 19:31:52 +0900 (JST) Message-ID: <20031229.193152.104097268.yamamoto436@oki.com> > > Hello again, > > Thank you for your reply. > > From: Olaf Hoyer > Message-ID: <20031229100720.X65076@gaff.hhhr.ision.net> > > > On Mon, 29 Dec 2003, Hideki Yamamoto wrote: > > > > > > > > Hello, > > > > > > I'm having a problem about link up between 1000base-SX(bge) and SUN. > > > > > > I tried yesterday's 4.9-stable on a FreeBSD box with two 3COM > > > 3C996-SXs and two onboard BMC5703 chips. Two 3COM 3C996-SX board link > > > went up, but the other side, a 1000base-SX I/F on SUN F280 did not go > > > up. When doing ping command to SUN from FreeBSD box, LED on 3C996 > > > were brinking but nothing happened to SUN board. I changed bge0 to > > > bge2, but the situation was the same. Hardware diagram is as follows. > > > bge0 can send or receive packates to the router or another PC with > > > intel SX board. > > > > > > Is this related to AUTO negotiation? > > > > Hi! > > > > Sometimes SUN cards are a bit picky. > > But, lets start gathering additional data: > > > > I assume you have a ge-card in, or which card are you using in the 280? > > The man page says that autoneg is performed, but chooses : > > Yes, I have three 'ge' cards in one F280R. > > > > > The GEM PCS is capable of performing auto-negotiation > > using the remote (or link partner) link end and receives the > > capabilities > > of the remote end. It selects the highest common demonina- > > tor mode of operation based on priorities. The ge driver > > also supports forced-mode operation under which the driver > > selects the mode of operation > > > > > > > > > > I assume that the interface is plumbed, and shows up in ifconfig as > > well, could you also post the snippet of the ifconfig entry? > > The machine is in a data center now. I cannot type ifconfig now. > > > > I cannot find any parameters about AUTO negotiation in 'bge' driver > > > source. I checked Linux 2.4.22 kernel source and have found the > > > several code about auto negotiation. I wonder if a linux box works > > > well. I do not need full support of auto negotiation, but sample code > > > that handles auto negotiation with Solaris machine. > > > > in bge(4) it is stated, that the bge's also support autoneg over a > > cross-cable-config (which this basically is). > > But: have a look at the link0 option there (can be adjusted via > > ifconfig) normally, autoneg shall do, but over a cross-cable you need to > > designate one end being master, other end being slave. > > > > My suspicion is, that autoneg procedure somewhere fails, and you should > > try to set the bge to be link master. > > > > Thank you for your advice. ----- From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 29 12:47:28 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4639216A4CE for ; Mon, 29 Dec 2003 12:47:28 -0800 (PST) Received: from smtp3.sentex.ca (smtp3.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00B5843D2D for ; Mon, 29 Dec 2003 12:47:26 -0800 (PST) (envelope-from damian@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smtp3.sentex.ca (8.12.10/8.12.10) with ESMTP id hBTKk5HF094049; Mon, 29 Dec 2003 15:46:05 -0500 (EST) (envelope-from damian@sentex.net) Received: from pegmatite.sentex.ca (pegmatite.sentex.ca [192.168.42.92]) by lava.sentex.ca (8.12.9p2/8.12.9) with ESMTP id hBTKk8Xv034180; Mon, 29 Dec 2003 15:46:08 -0500 (EST) (envelope-from damian@sentex.net) Received: by pegmatite.sentex.ca (Postfix, from userid 1001) id 31DDD171BA; Mon, 29 Dec 2003 15:46:08 -0500 (EST) Date: Mon, 29 Dec 2003 15:46:07 -0500 From: Damian Gerow To: admin@forkthepenguin.com Message-ID: <20031229204607.GA838@sentex.net> References: <20031229190146.GR883@sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-GPG-Key-Id: 0xB841F142 X-GPG-Fingerprint: C7C1 E1D1 EC06 7C86 AF7C 57E6 173D 9CF6 B841 F142 X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-new cc: freebsd-hardware@freebsd.org Subject: Re: Kernel Optimizations for Processors X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 20:47:28 -0000 Thus spake admin@forkthepenguin.com (admin@forkthepenguin.com) [29/12/03 15:20]: > > There's been a number of discussions about this over the past few months. > > Take a quick peak through the archives. > > I looked through the archives using the search on the FreeBSD site, and > Google (summaries are nice to have) and I didn't see a whole lot on this. > Perhaps I'm just using the wrong search terms or getting too many false > positives. Try looking for my e-mail address. > > In short: the GCC folk (at least for 2.95.x) assume that a 686-compatible > > chip understands CMOV. *Some* of the C3 cores understand it, others do not. > > I was under the impression that the Samuel2 /did/ understand it. > > Understanding CMOV is not a requirement for 686. > > OK, that clears things up a bit. I see now that this is listed in the > "Features" in dmesg on a PentiumIII system. I found the following on the > via site that discusses CMOV and is also related to the CMPXCHG8B code > )see NO_F00F_HACK below). > > http://www.viaarena.com/?PageID=377 > > > I think you get ever-so-slightly better performance if you set your ARCH to > > k6-2, though I use mine as i586/mmx. As for the kernel configuration, I > > left mine at I686_CPU, as the C3 /is/ a 686-class CPU. > > What kernel option do you use for k6-2? I don't see anything in LINT or > GENERIC. Also, what do you mean by "I use mine as i586/mmx"? Is this > another kernel option? Nope, I set that in /etc/make.conf. My kernel options I keep as I686_CPU. The C3 *is* a 686-class CPU. The problem lies in that GCC assumes that if a CPU is i686, it understands CMOV. But CMOV isn't part of the 686 spec. > It also says "should be included for any non-Pentium CPU that defines it" > but how do you know if the C# defines this? Is this another item that > would show up in the "Features" list? I looked at a PI-133 I have and > don't see it : Yeah, I read that over. The wording's a bit weird in that blurb, IMHO. I have *never* used the F00F workaround on any system I've used, and I've never had a problem with it. But I went from 486 straight to PIII. > CPU: Pentium/P54C (133.16-MHz 586-class CPU) > Origin = "GenuineIntel" Id = 0x52c Stepping = 12 > Features=0x3bf > > I have a PII-300 running Fedora, but dmesg doesn't show the features. I > did find it in proc : (Welcome to Linux.) > So it seems like it "should be included for any non-Pentium CPU that > defines it", but it sounds like it may not be an issue if this feature > is implemented correctly... Like I said, I've never used it anywhere. And I've never had problems with it, but I've never gone out of my way to test for it, either. > BTW, do you have problems with your system hanging on a reboot? I reported > this as a bug (misc/60646) which I see has been reported at least twice > before but nothing in the knats database shows it as being solved. Do you > know of a fix for this? Nope. I've had nothing but pure glee when dealing with the C3's, once I figured out the GCC assumption. I've been running 5.x on my C3s pretty much since the beginning -- which would mean the CMOV assumption carries over into 3.x for gcc -- and I've never had any CPU-related issues. From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 29 13:59:56 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7283B16A4CE for ; Mon, 29 Dec 2003 13:59:56 -0800 (PST) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42C1243D41 for ; Mon, 29 Dec 2003 13:59:55 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 19083 invoked from network); 29 Dec 2003 21:59:54 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 29 Dec 2003 21:59:54 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.10/8.12.10) with ESMTP id hBTLxpM0083040; Mon, 29 Dec 2003 16:59:51 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 29 Dec 2003 16:59:53 -0500 (EST) From: John Baldwin To: admin@forkthepenguin.com X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: Damian Gerow cc: freebsd-hardware@freebsd.org Subject: Re: Kernel Optimizations for Processors X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 21:59:56 -0000 On 29-Dec-2003 admin@forkthepenguin.com wrote: >> > # NO_F00F_HACK disables the hack that prevents Pentiums (and ONLY >> > # Pentiums) from locking up when a LOCK CMPXCHG8B instruction is >> > # executed. This option is only needed if I586_CPU is also defined, >> > # and should be included for any non-Pentium CPU that defines it. >> >> 'and ONLY Pentiums' > > It also says "should be included for any non-Pentium CPU that defines it" > but how do you know if the C# defines this? Is this another item that > would show up in the "Features" list? I looked at a PI-133 I have and > don't see it : It means that if you have 'cpu I586_CPU' in your kernel config and you aren't running a Pentium, then you can define this option. However, it won't really buy you much since we only install the F00F hack once during bootup and all adding this option will do is just not check for it at bootup. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 29 14:15:18 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1211416A4D0; Mon, 29 Dec 2003 14:15:18 -0800 (PST) Received: from vp4.netgate.net (vp4.netgate.net [205.214.170.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67A8043D2D; Mon, 29 Dec 2003 14:15:15 -0800 (PST) (envelope-from admin@forkthepenguin.com) Received: from localhost (ibrew@localhost) by vp4.netgate.net (8.11.6/8.11.7) with ESMTP id hBTMFF101620; Mon, 29 Dec 2003 14:15:15 -0800 (PST) Date: Mon, 29 Dec 2003 14:15:15 -0800 (PST) From: admin@forkthepenguin.com X-X-Sender: ibrew@vp4.netgate.net To: John Baldwin In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Damian Gerow cc: freebsd-hardware@FreeBSD.org Subject: Re: Kernel Optimizations for Processors X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 22:15:18 -0000 On Mon, 29 Dec 2003, John Baldwin wrote: > > On 29-Dec-2003 admin@forkthepenguin.com wrote: > >> > # NO_F00F_HACK disables the hack that prevents Pentiums (and ONLY > >> > # Pentiums) from locking up when a LOCK CMPXCHG8B instruction is > >> > # executed. This option is only needed if I586_CPU is also defined, > >> > # and should be included for any non-Pentium CPU that defines it. > >> > >> 'and ONLY Pentiums' > > > > It also says "should be included for any non-Pentium CPU that defines it" > > but how do you know if the C# defines this? Is this another item that > > would show up in the "Features" list? I looked at a PI-133 I have and > > don't see it : > > It means that if you have 'cpu I586_CPU' in your kernel config and > you aren't running a Pentium, then you can define this option. However, > it won't really buy you much since we only install the F00F hack once > during bootup and all adding this option will do is just not check for > it at bootup. Cool, thanks for the clarification. I do not have I586_CPU defined in my kernel conf (only I686_CPU) and had no problems building the kernel. Under Linux you have to define -march=i586 to build the kernel properly for the C3. I bring this up because you can specify CPUTYPE in the /etc/defaults/make.conf. According to the notes in that file, the following cpus can be defined : # Intel x86 architecture: # (AMD CPUs) k7 k6-2 k6 k5 # (Intel CPUs) p4 p3 p2 i686 i586/mmx i586 i486 i386 # Alpha/AXP architecture: ev6 pca56 ev56 ev5 ev45 ev4 Does CPUTYPE affect the -march flag? I ask because gnu apparently supports the VIA C3 using -march=c3. As a test I set CPUTYPE=c3 and had no problems building the kernel nor do I see any evidence that CPUTYPE was pulled from make.conf during the kernel build. Is CPUTYPE only used for application optimizations? I suspect that adding CPUTYPE=c3 was a misguided assumption based on the gnu docs (see below). http://gcc.gnu.org/onlinedocs/gcc-3.3.1/gcc/i386-and-x86-64-Options.html#i386%20and%20x86-64%20Options Chris From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 29 14:28:15 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6C0916A4CE; Mon, 29 Dec 2003 14:28:15 -0800 (PST) Received: from mv.milwaukeevalve.com (mail.milwaukeevalve.com [66.84.180.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A7D643D31; Mon, 29 Dec 2003 14:28:10 -0800 (PST) (envelope-from linux@milwaukeevalve.com) Received: (from root@localhost) by mv.milwaukeevalve.com (8.11.6/8.11.6) id hBTMS9831104; Mon, 29 Dec 2003 16:28:09 -0600 Received: from Pmjalex ([192.168.2.189]) (authenticated) by mv.milwaukeevalve.com (8.11.6/8.11.6) with ESMTP id hBTMS7e31055; Mon, 29 Dec 2003 16:28:07 -0600 From: "michael Alexander" To: "'Scott Long'" Date: Mon, 29 Dec 2003 16:28:04 -0600 Message-ID: <01d001c3ce5b$07593b20$bd02a8c0@Pmjalex> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 In-Reply-To: <20031229113357.T93058@pooker.samsco.home> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-scanner: scanned by Inflex 1.0.12.7 cc: freebsd-scsi@freebsd.org cc: freebsd-hardware@freebsd.org Subject: RE: Problems installing onto DAC960 (Mylex Acceleraid250) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 22:28:16 -0000 > On Mon, 29 Dec 2003, michael Alexander wrote: > > > The hang at the 'Waiting 15 seconds...' is likely not=20 > related to SCSI. > > > While the DAC960 card uses SCSI, it's FreeBSD driver does=20 > not attach > > > through the SCSI subsystem at all. 99% os hangs that=20 > happen at this > > > point are due to incorrect interrupt routing. The RedHat=20 > work-around > > > appears to confirm this. There really is no fix for 5.1 and > > > 4.9 unless > > > you can experiment with moving the DAC960 to a different PCI slot. > > > FreeBSD 5.2 has a much more comprehesive interrupt routing > > > algorithm and > > > will likely address your problem. If the 5.2 CD doesn't work, try > > > booting it with ACPI disabled (either via the BIOS or the=20 > boot menu). > > > > Will the miniinst be good enough to at least let me know if=20 > it is going to > > work or not? > > > > -Mike > > > > > > >=20 > Yes. In fact, the bootonly image can serve as a good smoke test for > this. >=20 > Scott Ok, downloaded the 5.2RC2-i386-miniinst.iso, no luck. BIOS has an option of "PCI IRQs to IO-APIC Mapping" (enabled/disabled) I didn't see anything else relating to APIC, or APCI(?) I set that to disabled. No luck, Then I left it disabled and tried = install w/o apic, still no luck. Then I ran with logging and have the following messages on screen after the Waiting 15 seconds.... ------------------------ (noperiph:sym0:0:-1:-1):SCSI BUS reset delivered (noperiph:sym0:0:-1:-1):SCSI BUS reset delivered [0] f:80 typ:6 s(CHS):0/1/1 e(CHS):749/127/32 s:32 l:3071968 [1] f:00 typ:101 s(CHS):750/0/1 e(CHS):1022/127/32 s:3072000 l:8212480 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM Configure mlxd0s1, start 16384 length 1572847616 end 1572863999 GEOM Configure mlxd0s2, start 1572864000 length 4204789760 end = 5777653759 ------------------------- I know the RAID works, I ran through enough of the Netware6 install for = it to be ready to partition the drives without any problem.=20 I can't really try the card in another slot, its being used as a zero channel raid card for the onboard scsi. I followed the instructions on = bios settings from intel's site (it's a NA440bx MB 512MB ram, dual P3-600s, = no other drive adapters, CD runs off built-in IDE) During the SCSI card = bootup it reports being at BUS 0, slot 12, irq 11 I'll be glad to provide any other information that might help figure = this out. Thanks, Mike From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 29 15:05:44 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0133616A4CF for ; Mon, 29 Dec 2003 15:05:44 -0800 (PST) Received: from smtp.mho.com (smtp.mho.net [64.58.4.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 2C40C43D45 for ; Mon, 29 Dec 2003 15:05:41 -0800 (PST) (envelope-from scottl@freebsd.org) Received: (qmail 39362 invoked by uid 1002); 29 Dec 2003 23:05:38 -0000 Received: from unknown (HELO ?10.4.1.5?) (64.58.1.252) by smtp.mho.net with SMTP; 29 Dec 2003 23:05:38 -0000 Date: Mon, 29 Dec 2003 16:07:09 -0700 (MST) From: Scott Long X-X-Sender: scottl@pooker.samsco.home To: michael Alexander In-Reply-To: <01d001c3ce5b$07593b20$bd02a8c0@Pmjalex> Message-ID: <20031229160108.P93734@pooker.samsco.home> References: <01d001c3ce5b$07593b20$bd02a8c0@Pmjalex> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org cc: freebsd-hardware@freebsd.org Subject: RE: Problems installing onto DAC960 (Mylex Acceleraid250) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 23:05:44 -0000 On Mon, 29 Dec 2003, michael Alexander wrote: > > Ok, downloaded the 5.2RC2-i386-miniinst.iso, no luck. > BIOS has an option of > "PCI IRQs to IO-APIC Mapping" (enabled/disabled) > I didn't see anything else relating to APIC, or APCI(?) > > I set that to disabled. No luck, Then I left it disabled and tried install > w/o apic, still no luck. Then I ran with logging and have the following > messages on screen after the Waiting 15 seconds.... Did you select the 'Boot with ACPI disabled' option from the boot menu on the CD? Sorry if this is a dumb question, but people often transpose 'apic' and 'acpi', so I want to make sure. I would try toggling both the BIOS 'IO_APIC Mapping' option and the ACPI option on the CD boot menu. If all four combinations fail to work, the only thing left to do is set up a serial console and capture the boot output and email it out. The boot serial console is enabled by escaping from the CD boot menu and typing 'boot -Dhv' Scott From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 29 15:14:34 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB15C16A4CE; Mon, 29 Dec 2003 15:14:34 -0800 (PST) Received: from just.puresimplicity.net (just.puresimplicity.net [140.177.207.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C535D43D4C; Mon, 29 Dec 2003 15:14:32 -0800 (PST) (envelope-from hemi@puresimplicity.net) Received: from just.puresimplicity.net (localhost.puresimplicity.net [127.0.0.1])hBTNEPcr033584 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Dec 2003 17:14:25 -0600 (CST) (envelope-from hemi@just.puresimplicity.net) Received: (from hemi@localhost) by just.puresimplicity.net (8.12.9p2/8.12.9/Submit) id hBTNEP0U033583; Mon, 29 Dec 2003 17:14:25 -0600 (CST) (envelope-from hemi) Date: Mon, 29 Dec 2003 17:14:25 -0600 From: Josh Tolbert To: admin@forkthepenguin.com Message-ID: <20031229231425.GA33560@just.puresimplicity.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: Damian Gerow cc: freebsd-hardware@freebsd.org Subject: Re: Kernel Optimizations for Processors X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 23:14:34 -0000 On Mon, Dec 29, 2003 at 02:15:15PM -0800, admin@forkthepenguin.com wrote: > > > On Mon, 29 Dec 2003, John Baldwin wrote: > > > > > On 29-Dec-2003 admin@forkthepenguin.com wrote: > > >> > # NO_F00F_HACK disables the hack that prevents Pentiums (and ONLY > > >> > # Pentiums) from locking up when a LOCK CMPXCHG8B instruction is > > >> > # executed. This option is only needed if I586_CPU is also defined, > > >> > # and should be included for any non-Pentium CPU that defines it. > > >> > > >> 'and ONLY Pentiums' > > > > > > It also says "should be included for any non-Pentium CPU that defines it" > > > but how do you know if the C# defines this? Is this another item that > > > would show up in the "Features" list? I looked at a PI-133 I have and > > > don't see it : > > > > It means that if you have 'cpu I586_CPU' in your kernel config and > > you aren't running a Pentium, then you can define this option. However, > > it won't really buy you much since we only install the F00F hack once > > during bootup and all adding this option will do is just not check for > > it at bootup. > > Cool, thanks for the clarification. I do not have I586_CPU defined in my > kernel conf (only I686_CPU) and had no problems building the kernel. Under > Linux you have to define -march=i586 to build the kernel properly for the > C3. I bring this up because you can specify CPUTYPE in the > /etc/defaults/make.conf. According to the notes in that file, the > following cpus can be defined : > > # Intel x86 architecture: > # (AMD CPUs) k7 k6-2 k6 k5 > # (Intel CPUs) p4 p3 p2 i686 i586/mmx i586 i486 i386 > # Alpha/AXP architecture: ev6 pca56 ev56 ev5 ev45 ev4 > > Does CPUTYPE affect the -march flag? I ask because gnu apparently supports > the VIA C3 using -march=c3. As a test I set CPUTYPE=c3 and had no problems > building the kernel nor do I see any evidence that CPUTYPE was pulled from > make.conf during the kernel build. Is CPUTYPE only used for application > optimizations? I suspect that adding CPUTYPE=c3 was a misguided assumption > based on the gnu docs (see below). > > http://gcc.gnu.org/onlinedocs/gcc-3.3.1/gcc/i386-and-x86-64-Options.html#i386%20and%20x86-64%20Options > > Chris Hi Chris, Take a look at /usr/share/mk/bsd.cpu.mk to see how CPUTYPE affects compiler flags. Thanks, Josh -- Josh Tolbert hemi@puresimplicity.net || http://www.puresimplicity.net/~hemi/ From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 29 15:29:28 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE04916A4CE for ; Mon, 29 Dec 2003 15:29:28 -0800 (PST) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A7AE43D45 for ; Mon, 29 Dec 2003 15:29:26 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 26490 invoked from network); 29 Dec 2003 23:29:23 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 29 Dec 2003 23:29:23 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.10/8.12.10) with ESMTP id hBTNTJM0083391; Mon, 29 Dec 2003 18:29:20 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 29 Dec 2003 18:29:22 -0500 (EST) From: John Baldwin To: admin@forkthepenguin.com X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: Damian Gerow cc: freebsd-hardware@FreeBSD.org Subject: Re: Kernel Optimizations for Processors X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 23:29:28 -0000 On 29-Dec-2003 admin@forkthepenguin.com wrote: > > > On Mon, 29 Dec 2003, John Baldwin wrote: > >> >> On 29-Dec-2003 admin@forkthepenguin.com wrote: >> >> > # NO_F00F_HACK disables the hack that prevents Pentiums (and ONLY >> >> > # Pentiums) from locking up when a LOCK CMPXCHG8B instruction is >> >> > # executed. This option is only needed if I586_CPU is also defined, >> >> > # and should be included for any non-Pentium CPU that defines it. >> >> >> >> 'and ONLY Pentiums' >> > >> > It also says "should be included for any non-Pentium CPU that defines it" >> > but how do you know if the C# defines this? Is this another item that >> > would show up in the "Features" list? I looked at a PI-133 I have and >> > don't see it : >> >> It means that if you have 'cpu I586_CPU' in your kernel config and >> you aren't running a Pentium, then you can define this option. However, >> it won't really buy you much since we only install the F00F hack once >> during bootup and all adding this option will do is just not check for >> it at bootup. > > Cool, thanks for the clarification. I do not have I586_CPU defined in my > kernel conf (only I686_CPU) and had no problems building the kernel. Under > Linux you have to define -march=i586 to build the kernel properly for the > C3. I bring this up because you can specify CPUTYPE in the > /etc/defaults/make.conf. According to the notes in that file, the > following cpus can be defined : > ># Intel x86 architecture: ># (AMD CPUs) k7 k6-2 k6 k5 ># (Intel CPUs) p4 p3 p2 i686 i586/mmx i586 i486 i386 ># Alpha/AXP architecture: ev6 pca56 ev56 ev5 ev45 ev4 > > Does CPUTYPE affect the -march flag? I ask because gnu apparently supports > the VIA C3 using -march=c3. As a test I set CPUTYPE=c3 and had no problems > building the kernel nor do I see any evidence that CPUTYPE was pulled from > make.conf during the kernel build. Is CPUTYPE only used for application > optimizations? I suspect that adding CPUTYPE=c3 was a misguided assumption > based on the gnu docs (see below). CPUTYPE does affect the -march flag, yes. However, /usr/share/mk/bsd.cpu.mk currently doesn't support the c3 CPU type for i386. If you want to add support for it and submit a patch in a PR, that would be great. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 29 21:42:29 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D80CE16A4CE for ; Mon, 29 Dec 2003 21:42:29 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADF5443D49 for ; Mon, 29 Dec 2003 21:42:26 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3p2/8.8.7) with ESMTP id QAA14289; Tue, 30 Dec 2003 16:42:17 +1100 Date: Tue, 30 Dec 2003 16:42:16 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Matt Staroscik In-Reply-To: <6412.207.46.125.17.1072729575.squirrel@wrongcrowd.com> Message-ID: <20031230155146.D6269@gamplex.bde.org> References: <20031229200107.4D80916A4D9@hub.freebsd.org> <6412.207.46.125.17.1072729575.squirrel@wrongcrowd.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hardware@freebsd.org Subject: Re: Kernel Optimizations for Processors (Now AthlonXP Q) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Dec 2003 05:42:30 -0000 On Mon, 29 Dec 2003, Matt Staroscik wrote: > A while back I did a big Google session to try and find the best kernel > and make flags for the AthlonXP proc (under FreeBSD 4.x). At the time, > most of what I read said that the AthlonXP did best with (make.conf) > CPUTYPE=i686, and the k7 flag just fell back to something like that anyway > because there wasn't complete support for it yet in the compiler. gcc-3.x in -current has direct support for AthlonXP. This may be worth a few percent in a few applications (the largest I saw was 11% for an integer-crunching application (searching a game tree)). CPUTYPE=i686 is about the worst possible for Athlons. It mostly gives extra instructions to avoid using some 386 instructions that PentiumPros handle poorly. Athlons handle these instructions well so CPUTYPE=i686 mainly just gives extra overheads for executing the extra instructions. The effects of this are quite small (something more like -0.1% than 11%). Setting CPUTYPE also affects things other than gcc (mainly a few applications that have special assembler support for to give very MD optimizations). I haven't benchmarked any of these. The best optimizations may involve using SSE, but RELENG_4 doesn't support this in userland for athlons (CPUTYPE=k7 gives only `MACHINE_CPU = k7 3dnow mmx k6 k5 i586 i486 i386', while CPUTYPE=athlon-xp in -current also gives athlon-xp and sse in MACHINE_CPU). RELENG_4 doesn't really support SSE in the kernel either (signals may trash the SSE state), so it mostly shouldn't be used. > Likewise > my kernel is set to: > > cpu I686_CPU > > Is this advice still valid, if it ever was? Can anyone comment on the best > make & kernel options for the AthlonXP CPU? Setting I686_CPU mainly prevents gratuitous refusing to boot i686 and later CPUs. The Ix86_CPU options are mostly bugs. This is mostly fixed for later CPUs by not using these options to determine features or break booting of old kernels on new CPUs. Things are handled better using the cpuid instruction to determine features. Anyway, these options only control a couple of performance-related features. Configuring I386_CPU forces use of i386-only instructions in a few not very important places in RELENG_4 (this is more harmful for real i686's). Configuring I386_CPU in -current forces use of i386-only instructions in a many important places, so it is much more harmful and not to default (but still costs only a few percent overall). I just always use I486_CPU, I586_CPU and I686_CPU (configuring them all costs epsilon), and make gcc optimize for 386's by not setting CPUTYPE and editing out the harmful default setting of -mcpu=pentiumpro in bsd.cpu.mk (this bug is only in -current). Bruce From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 30 13:07:46 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 82E9416A4CE for ; Tue, 30 Dec 2003 13:07:46 -0800 (PST) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0FE943D39 for ; Tue, 30 Dec 2003 13:07:44 -0800 (PST) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])hBUL7hoW050279 for ; Wed, 31 Dec 2003 08:07:43 +1100 (EST) (envelope-from jeremyp@cirb503493.alcatel.com.au) Received: (from jeremyp@localhost)hBUL7hjH050278 for freebsd-hardware@freebsd.org; Wed, 31 Dec 2003 08:07:43 +1100 (EST) (envelope-from jeremyp) Date: Wed, 31 Dec 2003 08:07:42 +1100 From: Peter Jeremy To: freebsd-hardware@freebsd.org Message-ID: <20031230210742.GA50195@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: Problem writing VCD with burncd X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Dec 2003 21:07:46 -0000 I have a -stable system from early December and recently tried to burn a VCD onto a CD-RW using burncd -v -s 4 blank vcd foo.bin fixate this fails after writing 6100KB with the kernel message acd0: WRITE_BIG - MEDIUM ERROR asc=0x0c ascq=0x10 error=0x04 I've tried two different CD-RW media - both of which work perfectly trying to burn audio or data. The CD writer is: acd0: CD-RW at ata1-master UDMA33 I've looked thru the mailing list archives but can't find anything that looks relevant. Does anyone have any suggestions? I've done some googling and can't find any useful ATAPI ASC/ASCQ tables and that ASC/ASCQ combination isn't listed in an SCSI ASC/ASCQ assignment list dated 12/05/03. Peter From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 30 13:10:32 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A89F16A4CE for ; Tue, 30 Dec 2003 13:10:32 -0800 (PST) Received: from abigail.blackend.org (blackend.org [212.11.35.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1836343D31 for ; Tue, 30 Dec 2003 13:10:29 -0800 (PST) (envelope-from marc@blackend.org) Received: from abigail.blackend.org (localhost [127.0.0.1]) by abigail.blackend.org (8.12.9/8.12.3) with ESMTP id hBULAQb1095062; Tue, 30 Dec 2003 22:10:26 +0100 (CET) (envelope-from marc@abigail.blackend.org) Received: (from marc@localhost) by abigail.blackend.org (8.12.9/8.12.3/Submit) id hBULAPiv095061; Tue, 30 Dec 2003 22:10:25 +0100 (CET) (envelope-from marc) Date: Tue, 30 Dec 2003 22:10:25 +0100 From: Marc Fonvieille To: Peter Jeremy Message-ID: <20031230221025.B93424@abigail.blackend.org> References: <20031230210742.GA50195@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20031230210742.GA50195@cirb503493.alcatel.com.au>; from PeterJeremy@optushome.com.au on Wed, Dec 31, 2003 at 08:07:42AM +1100 X-Useless-Header: blackend.org X-Operating-System: FreeBSD 4.8-STABLE cc: freebsd-hardware@freebsd.org Subject: Re: Problem writing VCD with burncd X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Dec 2003 21:10:32 -0000 On Wed, Dec 31, 2003 at 08:07:42AM +1100, Peter Jeremy wrote: > I have a -stable system from early December and recently tried to > burn a VCD onto a CD-RW using > burncd -v -s 4 blank vcd foo.bin fixate > this fails after writing 6100KB with the kernel message > acd0: WRITE_BIG - MEDIUM ERROR asc=0x0c ascq=0x10 error=0x04 > > I've tried two different CD-RW media - both of which work perfectly > trying to burn audio or data. The CD writer is: > acd0: CD-RW at ata1-master UDMA33 > > I've looked thru the mailing list archives but can't find anything > that looks relevant. Does anyone have any suggestions? I've done > some googling and can't find any useful ATAPI ASC/ASCQ tables and that > ASC/ASCQ combination isn't listed in an SCSI ASC/ASCQ assignment list > dated 12/05/03. > To burn VCD you should use cdrdao, it runs fine. You will find an example in this article: http://bsdnews.org/01/vcd.php Marc From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 30 14:40:17 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D1D7C16A4CE; Tue, 30 Dec 2003 14:40:17 -0800 (PST) Received: from server.vk2pj.dyndns.org (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44A3243D2F; Tue, 30 Dec 2003 14:40:16 -0800 (PST) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1])hBUMeAQU097217; Wed, 31 Dec 2003 09:40:10 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.12.10/8.12.10/Submit) id hBUMeAuA097216; Wed, 31 Dec 2003 09:40:10 +1100 (EST) (envelope-from peter) Date: Wed, 31 Dec 2003 09:40:10 +1100 From: Peter Jeremy To: Marc Fonvieille Message-ID: <20031230224010.GD84164@server.vk2pj.dyndns.org> References: <20031230210742.GA50195@cirb503493.alcatel.com.au> <20031230221025.B93424@abigail.blackend.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031230221025.B93424@abigail.blackend.org> User-Agent: Mutt/1.4.1i cc: freebsd-hardware@freebsd.org Subject: Re: Problem writing VCD with burncd X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Dec 2003 22:40:17 -0000 On Tue, Dec 30, 2003 at 10:10:25PM +0100, Marc Fonvieille wrote: >To burn VCD you should use cdrdao, it runs fine. >You will find an example in this article: >http://bsdnews.org/01/vcd.php The man page for burncd says it should work as well. cdrdao only supports SCSI CD-RW's and I don't currently have atapicam in my kernel - I'll give it a try when I can next reboot but that won't be for a day or two. (I recall seeing a reference to some patches to cdrdao to support ATAPI but don't seem to have kept the URL). Peter From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 30 20:19:58 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A62E16A4CF; Tue, 30 Dec 2003 20:19:58 -0800 (PST) Received: from monster.schulte.org (monster.schulte.org [209.134.156.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id D037C43D49; Tue, 30 Dec 2003 20:19:54 -0800 (PST) (envelope-from jay.liew@ml.freebsd.jaysern.org) Received: from localhost (localhost [127.0.0.1]) by monster.schulte.org (Postfix) with ESMTP id 563231FB2F; Tue, 30 Dec 2003 22:19:53 -0600 (CST) Received: from pinnacle.schulte.org (pinnacle.schulte.org [209.134.156.220]) by monster.schulte.org (Postfix) with ESMTP id 73A411FB24; Tue, 30 Dec 2003 22:19:52 -0600 (CST) Received: from localhost (dude@localhost)hBV4Jp44003149; Tue, 30 Dec 2003 22:19:52 -0600 (CST) (envelope-from jay.liew@ml.freebsd.jaysern.org) X-Authentication-Warning: pinnacle.schulte.org: dude owned process doing -bs Date: Tue, 30 Dec 2003 22:19:51 -0600 (CST) From: Jay Sern Liew X-X-Sender: dude@pinnacle.schulte.org To: undisclosed-recipients: ; Message-ID: <20031230221041.D3141@pinnacle.schulte.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS 0.3.12pre8 on monster.schulte.org X-Mailman-Approved-At: Tue, 30 Dec 2003 20:23:24 -0800 Subject: nVidia Quadro NVS 200 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Dec 2003 04:19:58 -0000 I couldn't find a comprehensive list of supported hardware in the handbook or in the release notes, hardware.txt file. I know nVidia provides FreeBSD drivers, but I can't seem to find anywhere on the FreeBSD WWW, mailinglist, freebsdforums.org, that says if the nVidia Quadro NVS 200 is supported. Anyone has got this dual head AGP card to work in FreeBSD? Thanks. ________________________________________________________________________ Jay Sern Liew jaysern@{acm,ieee}.org gpg --keyserver pgp.mit.edu --recv-keys 0xA115A33F From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 31 05:55:19 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18B9C16A4CE for ; Wed, 31 Dec 2003 05:55:19 -0800 (PST) Received: from ntx.netvision.net.il (ananas1.netvision.net.il [199.203.100.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5626F43D48 for ; Wed, 31 Dec 2003 05:55:13 -0800 (PST) (envelope-from cypher@netvision.net.il) Received: from Internal Mail-Server by ananas1 with SMTP; 31 Dec 2003 15:54:39 +0200 Received: from ntx2.forest.netvision.net.il ([172.20.30.33]) by ntx1.forest.netvision.net.il with Microsoft SMTPSVC(5.0.2195.6713); Wed, 31 Dec 2003 15:52:31 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Date: Wed, 31 Dec 2003 15:54:14 +0200 Message-ID: <560FC34DB0095B459060688A7818E04F037536@ntx2.forest.netvision.net.il> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: SCSI backup tape problem Thread-Index: AcPPpZiNA5yZyjq0TEu+oXWOLispSw== From: "Denis Prezhevalsky" To: X-OriginalArrivalTime: 31 Dec 2003 13:52:31.0332 (UTC) FILETIME=[55D8A240:01C3CFA5] Subject: SCSI backup tape problem X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Dec 2003 13:55:19 -0000 Hello, I hope this is the right list for my problem. I recently installed FreeBSD 5.1-RELEASE on HP DL380 G3. The problem is that that FreeBSD not probing/recognizing my external = Compaq AIT 35 SCSI tape connected to the SCSI port located on the back of the server (built-in = SCSI LVD).=20 When the computer starting up, I can see the BIOS message that the tape = is recognized, but when FreeBSD started - nothing. Running camcontrol : mail# camcontrol devlist -v scbus0 on ciss0 bus 0: at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 1 lun 0 (pass1,da1) scbus-1 on xpt0 bus 0: < > at scbus-1 target -1 lun -1 (xpt0) The same results even after running camcontrol rescan all. Changing SCSI id doesn't help. The tape is fine - running on another = machine without any problem. Any help? I'm attaching dmesg and kernel conf. Dec 31 14:57:56 mail kernel: Copyright (c) 1992-2003 The FreeBSD = Project. Dec 31 14:57:56 mail kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, = 1989, 1991, 1992, 1993, 1994 Dec 31 14:57:56 mail kernel: The Regents of the University of = California. All rights reserved. Dec 31 14:57:57 mail kernel: FreeBSD 5.1-RELEASE #0: Wed Dec 31 12:37:06 = IST 2003 Dec 31 14:57:57 mail kernel: = admin@mail.ort.org.il:/usr/src/sys/i386/compile/SMP31Dec2003 Dec 31 14:57:57 mail kernel: Preloaded elf kernel "/boot/kernel/kernel" = at 0xc0434000. Dec 31 14:57:57 mail kernel: Preloaded elf module "/boot/kernel/acpi.ko" = at 0xc0434244. Dec 31 14:57:57 mail kernel: Timecounter "i8254" frequency 1193182 Hz Dec 31 14:57:57 mail kernel: Timecounter "TSC" frequency 2784983072 Hz Dec 31 14:57:57 mail kernel: CPU: Intel(R) Xeon(TM) CPU 2.80GHz = (2784.98-MHz 686-class CPU) Dec 31 14:57:57 mail kernel: Origin =3D "GenuineIntel" Id =3D 0xf29 = Stepping =3D 9 Dec 31 14:57:57 mail kernel: = Features=3D0xbfebfbff Dec 31 14:57:57 mail kernel: Hyperthreading: 2 logical CPUs Dec 31 14:57:57 mail kernel: real memory =3D 2147459072 (2047 MB) Dec 31 14:57:57 mail kernel: avail memory =3D 2085732352 (1989 MB) Dec 31 14:57:57 mail kernel: Programming 16 pins in IOAPIC #0 Dec 31 14:57:57 mail kernel: IOAPIC #0 intpin 2 -> irq 0 Dec 31 14:57:57 mail kernel: Programming 16 pins in IOAPIC #1 Dec 31 14:57:57 mail kernel: Programming 16 pins in IOAPIC #2 Dec 31 14:57:57 mail kernel: Programming 16 pins in IOAPIC #3 Dec 31 14:57:57 mail kernel: FreeBSD/SMP: Multiprocessor System = Detected: 4 CPUs Dec 31 14:57:57 mail kernel: cpu0 (BSP): apic id: 0, version: = 0x00050014, at 0xfee00000 Dec 31 14:57:57 mail kernel: cpu1 (AP): apic id: 1, version: = 0x00050014, at 0xfee00000 Dec 31 14:57:57 mail kernel: cpu2 (AP): apic id: 6, version: = 0x00050014, at 0xfee00000 Dec 31 14:57:57 mail kernel: cpu3 (AP): apic id: 7, version: = 0x00050014, at 0xfee00000 Dec 31 14:57:57 mail kernel: io0 (APIC): apic id: 2, version: = 0x000f0011, at 0xfec00000 Dec 31 14:57:57 mail kernel: io1 (APIC): apic id: 3, version: = 0x000f0011, at 0xfec01000 Dec 31 14:57:57 mail kernel: io2 (APIC): apic id: 4, version: = 0x000f0011, at 0xfec02000 Dec 31 14:57:57 mail kernel: io3 (APIC): apic id: 5, version: = 0x000f0011, at 0xfec03000 Dec 31 14:57:57 mail kernel: Pentium Pro MTRR support enabled Dec 31 14:57:57 mail kernel: npx0: on motherboard Dec 31 14:57:57 mail kernel: npx0: INT 16 interface Dec 31 14:57:57 mail kernel: acpi0: on motherboard Dec 31 14:57:57 mail kernel: ACPI-0629: *** Info: There are no GPE = blocks defined in the FADT Dec 31 14:57:57 mail kernel: acpi0: power button is handled as a fixed = feature programming model. Dec 31 14:57:57 mail kernel: Timecounter "ACPI-safe" frequency 3579545 = Hz Dec 31 14:57:57 mail kernel: pcibios: BIOS version 2.10 Dec 31 14:57:57 mail kernel: acpi_timer0: <32-bit timer at 3.579545MHz> = port 0x920-0x923 on acpi0 Dec 31 14:57:57 mail kernel: acpi_cpu0: on acpi0 Dec 31 14:57:57 mail kernel: acpi_cpu1: on acpi0 Dec 31 14:57:57 mail kernel: acpi_cpu2: on acpi0 Dec 31 14:57:57 mail kernel: acpi_cpu3: on acpi0 Dec 31 14:57:57 mail kernel: acpi_cpu4: on acpi0 Dec 31 14:57:57 mail kernel: acpi_cpu5: on acpi0 Dec 31 14:57:57 mail kernel: acpi_cpu6: on acpi0 Dec 31 14:57:57 mail kernel: acpi_cpu7: on acpi0 Dec 31 14:57:57 mail kernel: acpi_tz0: on acpi0 Dec 31 14:57:57 mail kernel: pcib0: on acpi0 Dec 31 14:57:57 mail kernel: pci0: on pcib0 Dec 31 14:57:57 mail kernel: IOAPIC #1 intpin 0 -> irq 2 Dec 31 14:57:57 mail kernel: IOAPIC #1 intpin 1 -> irq 3 Dec 31 14:57:57 mail kernel: pci0: at device 3.0 (no = driver attached) Dec 31 14:57:57 mail kernel: pci0: at device 4.0 (no = driver attached) Dec 31 14:57:57 mail kernel: pci0: at device 4.2 (no = driver attached) Dec 31 14:57:57 mail kernel: isab0: at device 15.0 on = pci0 Dec 31 14:57:57 mail kernel: isa0: on isab0 Dec 31 14:57:57 mail kernel: atapci0: port = 0x2000-0x200f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device = 15.1 on pci0 Dec 31 14:57:57 mail kernel: ata0: at 0x1f0 irq 14 on atapci0 Dec 31 14:57:57 mail kernel: ata1: simplex device, DMA on primary only Dec 31 14:57:57 mail kernel: ata1: at 0x170 irq 15 on atapci0 Dec 31 14:57:57 mail kernel: pcib1: on acpi0 Dec 31 14:57:57 mail kernel: pci1: on pcib1 Dec 31 14:57:57 mail kernel: IOAPIC #1 intpin 14 -> irq 5 Dec 31 14:57:57 mail kernel: ciss0: port = 0x3000-0x30ff mem 0xf7cf0000-0xf7cf3fff,0xf7dc0000-0xf7dfffff irq 5 at = device 3.0 on pci1 Dec 31 14:57:57 mail kernel: ciss0: using 256 of 1024 available commands Dec 31 14:57:57 mail kernel: ciss0: 2 logical drives configured Dec 31 14:57:57 mail kernel: ciss0: firmware 2.36 Dec 31 14:57:57 mail kernel: ciss0: 2 SCSI channels Dec 31 14:57:57 mail kernel: ciss0: signature 'CISS' Dec 31 14:57:57 mail kernel: ciss0: valence 1 Dec 31 14:57:57 mail kernel: ciss0: supported I/O methods = 0xe Dec 31 14:57:57 mail kernel: ciss0: active I/O method 0x3 Dec 31 14:57:57 mail kernel: ciss0: 4G page base 0x00000000 Dec 31 14:57:57 mail kernel: ciss0: interrupt coalesce delay 1000us Dec 31 14:57:57 mail kernel: ciss0: interrupt coalesce count 16 Dec 31 14:57:57 mail kernel: ciss0: max outstanding commands 1024 Dec 31 14:57:57 mail kernel: ciss0: bus types 0x2 Dec 31 14:57:57 mail kernel: ciss0: server name '' Dec 31 14:57:57 mail kernel: ciss0: heartbeat 0x1000003a Dec 31 14:57:57 mail kernel: ciss0: 2 logical drives Dec 31 14:57:57 mail kernel: ciss0: logical drive 1: RAID 1, 34304MB = online Dec 31 14:57:57 mail kernel: ciss0: logical drive 1: RAID 5, 419840MB = online Dec 31 14:57:57 mail kernel: pcib2: on acpi0 Dec 31 14:57:57 mail kernel: pci2: on pcib2 Dec 31 14:57:57 mail kernel: IOAPIC #1 intpin 13 -> irq 7 Dec 31 14:57:58 mail kernel: IOAPIC #1 intpin 15 -> irq 10 Dec 31 14:57:58 mail kernel: bge0: mem 0xf7ef0000-0xf7efffff irq 7 at device 1.0 on pci2 Dec 31 14:57:58 mail kernel: bge0: Ethernet address: 00:0b:cd:dc:3a:53 Dec 31 14:57:58 mail kernel: miibus0: on bge0 Dec 31 14:57:58 mail kernel: brgphy0: on = miibus0 Dec 31 14:57:58 mail kernel: brgphy0: 10baseT, 10baseT-FDX, 100baseTX, = 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto Dec 31 14:57:58 mail kernel: bge1: mem 0xf7ee0000-0xf7eeffff irq 10 at device 2.0 on pci2 Dec 31 14:57:58 mail kernel: bge1: Ethernet address: 00:0b:cd:dc:3a:52 Dec 31 14:57:58 mail kernel: miibus1: on bge1 Dec 31 14:57:58 mail kernel: brgphy1: on = miibus1 Dec 31 14:57:58 mail kernel: brgphy1: 10baseT, 10baseT-FDX, 100baseTX, = 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto Dec 31 14:57:58 mail kernel: pcib3: on acpi0 Dec 31 14:57:58 mail kernel: pci3: on pcib3 Dec 31 14:57:58 mail kernel: pcib4: on acpi0 Dec 31 14:57:58 mail kernel: pci6: on pcib4 Dec 31 14:57:58 mail kernel: IOAPIC #1 intpin 2 -> irq 11 Dec 31 14:57:58 mail kernel: pci6: at device 30.0 (no = driver attached) Dec 31 14:57:58 mail kernel: atkbdc0: port = 0x64,0x60 irq 1 on acpi0 Dec 31 14:57:58 mail kernel: atkbd0: flags 0x1 irq 1 on = atkbdc0 Dec 31 14:57:58 mail kernel: kbd0 at atkbd0 Dec 31 14:57:58 mail kernel: sio0 port 0x3f8-0x3ff irq 4 on acpi0 Dec 31 14:57:58 mail kernel: sio0: type 16550A Dec 31 14:57:58 mail kernel: fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 Dec 31 14:57:58 mail kernel: fdc0: FIFO enabled, 8 bytes threshold Dec 31 14:57:58 mail kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Dec 31 14:57:58 mail kernel: orm0: