From owner-freebsd-hardware@FreeBSD.ORG Mon Jan 17 15:34:07 2005 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 2C31016A4CE for ; Mon, 17 Jan 2005 15:34:07 +0000 (GMT) Received: from mail.onlinefix.de (mail2-out.titan-networks.de [217.140.72.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3FA843D4C for ; Mon, 17 Jan 2005 15:34:05 +0000 (GMT) (envelope-from sw@gegenunendlich.de) Received: from kyuzo.dunkelkammer.void ([217.140.77.242]) (authenticated bits=0)j0HFY3Ti028736 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 17 Jan 2005 16:34:04 +0100 Received: by kyuzo.dunkelkammer.void (Postfix, from userid 1002) id 03B163EC8; Mon, 17 Jan 2005 16:34:02 +0100 (CET) Date: Mon, 17 Jan 2005 16:34:02 +0100 From: Stefan Walter To: freebsd-hardware@freebsd.org Message-ID: <20050117153402.GA875@kyuzo.dunkelkammer.void> References: <20050113140830.GA1953@kyuzo.dunkelkammer.void> <200501131729.JAA20704@mina.soco.agilent.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline In-Reply-To: <200501131729.JAA20704@mina.soco.agilent.com> X-PGP-key: http://www.gegenunendlich.de/swalter-rsa.asc X-PGP-fp: 85D8 6A49 22C7 6CD9 B011 5D6A 5691 111B 12B9 E0B3 Organization: Infinity Approximation Task Force X-PGP-key: http://www.gegenunendlich.de/swalter-rsa.asc X-PGP-fingerprint: 85D8 6A49 22C7 6CD9 B011 5D6A 5691 111B 12B9 E0B3 User-Agent: Mutt/1.5.6i Subject: Re: Athlon XP-M/PowerNow for desktop system? 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, 17 Jan 2005 15:34:07 -0000 --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Darryl Okahata in gmane.os.freebsd.devel.hardware: >> I considered an Athlon XP-M because it consumes less energy and should be >> cooler than the desktop variant. If you can't change the voltage of the >> CPU on an ATX board, that's OK, but I'm not sure if it's really worth >> buying it if I possibly can't throttle the frequency when it's idle. > > It may still be worthwhile, if you live in an area with expensive > electricity. I've forgotten the exact numbers, but the XP-M CPUs tend > to use significantly less power than the regular desktop CPUs (something > like 30-40+W less). A few months back, I built a 2200+ XP-M-based > system which only uses up around 80-90W, and this could have been even > lower, had I not also installed a power-hungry TV capture card > (Hauppauge PVR-250). Thanks for the info. I might give it a try, then. Stefan --=20 No reading beyond this point --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iQGVAwUBQeva6laRERsSueCzAQIsAAv/YR8RPsWLvcEHPV74TsH70Qb8xXlDbDgk ObZHlsCoFlLJEMIPlMuPZzugi+m6xCCjnth65hsbN+kQXpgSobLMxRsHblZ2xkmn eIbBx27WATe/JPwDoVVp4cNNq8Z2svcgctqj0s3hw2hjYtveIUr73PP+29k3OHMO y/7ivMISFA3XvgQvklvzrOVJswsljEibcAgl+ewDOMrVdfZq1nRotYQDRR6wegmU 8KaAmTGHnhqJmWF60jqzwQ68FQa5Cz+v+uux+0q3RZ/bdgfNxVKvOcZ+6n+SLXPY f4nu0FvnGsNIiWqe9UB6hqkGYQm9a3ARD9kFIfxn+FibZkG9cDd6mf1jh7Ko/5Tx t5ZP68DtKbAFr3BhZAMgU9zaBdjvme8ehVtZjb451F+9H3wA4lSF02VWkuXFGkh/ VOkW2dKP0032WW8lrngv0Smgn8+T/Kp8QmFhJnkPnfALEup3/De4GQg/8DdiANlI sTVTDXMGgizW3DEqMosI9VH+CySEVGyg =vuOG -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh-- From owner-freebsd-hardware@FreeBSD.ORG Tue Jan 18 02:48:06 2005 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 B101716A530 for ; Tue, 18 Jan 2005 02:48:01 +0000 (GMT) Received: from mail14.speakeasy.net (mail22.sea5.speakeasy.net [69.17.117.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4AAFD43D2F for ; Tue, 18 Jan 2005 02:48:01 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 6773 invoked from network); 18 Jan 2005 02:48:01 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 18 Jan 2005 02:48:00 -0000 Received: from slimer.baldwin.cx (slimer.baldwin.cx [192.168.0.16]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j0I2lqaH092340; Mon, 17 Jan 2005 21:47:55 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-hardware@FreeBSD.org Date: Mon, 17 Jan 2005 21:11:46 -0500 User-Agent: KMail/1.6.2 References: <1105725440.11715.33.camel@slappy> <200501141522.57653.jhb@FreeBSD.org> <1105738155.11715.52.camel@slappy> In-Reply-To: <1105738155.11715.52.camel@slappy> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501172111.46947.jhb@FreeBSD.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: Ross Kramer Subject: Re: em0 issues with 4.10 + SMP 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, 18 Jan 2005 02:48:07 -0000 On Friday 14 January 2005 04:29 pm, Ross Kramer wrote: > Actually, I did try it with 4.11-RC2. I was still getting the same > problem. If it's a driver issue, why does it work with SMP disabled? SMP in 4.x changes several things such as using the APIC for interrupts instead of the ATPIC, etc. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hardware@FreeBSD.ORG Tue Jan 18 11:29:22 2005 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 5F8AE16A4CE for ; Tue, 18 Jan 2005 11:29:22 +0000 (GMT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 223C043D1F for ; Tue, 18 Jan 2005 11:29:21 +0000 (GMT) (envelope-from andreas@klemm.apsfilter.org) Received: from srv1.cosmo-project.de (localhost [IPv6:::1]) j0IBTJHo019347 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 18 Jan 2005 12:29:20 +0100 (CET) (envelope-from andreas@klemm.apsfilter.org) Received: (from uucp@localhost)j0IBTJ8M019346 for freebsd-hardware@freebsd.org; Tue, 18 Jan 2005 12:29:19 +0100 (CET) (envelope-from andreas@klemm.apsfilter.org) Received: from titan.klemm.apsfilter.org (localhost.klemm.apsfilter.org [127.0.0.1]) by klemm.apsfilter.org (8.13.1/8.13.1) with ESMTP id j0IBT12c014622 for ; Tue, 18 Jan 2005 12:29:01 +0100 (CET) (envelope-from andreas@titan.klemm.apsfilter.org) Received: (from andreas@localhost) by titan.klemm.apsfilter.org (8.13.1/8.13.1/Submit) id j0IBT0dT014621 for freebsd-hardware@freebsd.org; Tue, 18 Jan 2005 12:29:00 +0100 (CET) (envelope-from andreas) Date: Tue, 18 Jan 2005 12:29:00 +0100 From: Andreas Klemm To: freebsd-hardware@freebsd.org Message-ID: <20050118112900.GA14342@titan.klemm.apsfilter.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 5.3-STABLE X-Disclaimer: A free society is one where it is safe to be unpopular User-Agent: Mutt/1.5.6i Subject: FreeBSD 5.3 SATA / RAID1 questions for migration from ATA 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, 18 Jan 2005 11:29:22 -0000 Hi, I bought a new socket 939 MSI mainboard (amd64, MSI K8N NEO2 Platinum, S.939 NVIDIA Nforce3 Ultra) and am planning now how I could best make use of it and its BIOS mirroring capabilities. In an ideal world I would dream of - creating a BIOS based mirror on 2 new SATA drives - then install XP and FreeBSD on these bios based mirrord disks. - finally move old data to new mirrored disks and thats it. After reading the mailinglists I have the feeling that - BIOS created mirrors are not useable for a FreeBSD 5.3 installation. But I also read - that its possible to create a mirror once you have a FreeBSD installed. Does this mean, that the BIOS based mirror as well as the FreeBSD based mirror solution are partition based ? Or is it mixed, that the BIOS based solution mirrors per disk and the FreeBSD one per partition ? Other questions involved: how well does Serial ATA in 5.3 ? Currently I see the following scenario. a) Buy 2 SATA disks, create BIOS mirror, install XP move data from ATA disks to new SATA disks b) keep the old ATA disks for FreeBSD only and dont mirror them from BIOS. Optionally mirror them from within FreeBSD. Installation would be done newly on one disk, then a magic ata command tells to do a mirror with 2nd disk or related. Does somebody make some experiences with scenarios like this so that I could ask questions or ideally could do a phonecall in english or german ? Thanks a lot for helping me Andreas /// -- Andreas Klemm - Powered by FreeBSD 5.1-CURRENT Need a magic printfilter today ? -> http://www.apsfilter.org/ From owner-freebsd-hardware@FreeBSD.ORG Tue Jan 18 17:58:03 2005 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 1DB1B16A4CE for ; Tue, 18 Jan 2005 17:58:03 +0000 (GMT) Received: from msgbas9x.lvld.agilent.com (msgbas9x.lvld.agilent.com [192.25.144.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id D88C543D48 for ; Tue, 18 Jan 2005 17:58:02 +0000 (GMT) (envelope-from darrylo@soco.agilent.com) Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas9x.lvld.agilent.com (Postfix) with ESMTP id 730163C54 for ; Tue, 18 Jan 2005 10:58:00 -0700 (MST) Received: from wcosvs02.cos.agilent.com (wcosvs02.cos.agilent.com [130.29.152.188]) by relcos2.cos.agilent.com (Postfix) with ESMTP id 615E887B for ; Tue, 18 Jan 2005 10:58:02 -0700 (MST) Received: from mina.soco.agilent.com ([141.121.54.157]) by wcosvs02.cos.agilent.com with InterScan Messaging Security Suite; Tue, 18 Jan 2005 10:58:01 -0700 Received: from mina.soco.agilent.com (localhost [127.0.0.1]) SMKit7.1.1_Agilent) with ESMTP id JAA28085 for ; Tue, 18 Jan 2005 09:58:01 -0800 (PST) Message-Id: <200501181758.JAA28085@mina.soco.agilent.com> To: freebsd-hardware@freebsd.org In-Reply-To: Your message of "Mon, 17 Jan 2005 16:34:02 +0100." <20050117153402.GA875@kyuzo.dunkelkammer.void> Mime-Version: 1.0 (generated by tm-edit 1.8) Content-Type: text/plain; charset=US-ASCII Date: Tue, 18 Jan 2005 09:58:01 -0800 From: Darryl Okahata Subject: Re: Athlon XP-M/PowerNow for desktop system? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Darryl Okahata List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 17:58:03 -0000 Stefan Walter wrote: > > It may still be worthwhile, if you live in an area with expensive > > electricity. I've forgotten the exact numbers, but the XP-M CPUs tend > > to use significantly less power than the regular desktop CPUs (something > > like 30-40+W less). A few months back, I built a 2200+ XP-M-based > > system which only uses up around 80-90W, and this could have been even > > lower, had I not also installed a power-hungry TV capture card > > (Hauppauge PVR-250). > > Thanks for the info. I might give it a try, then. Note that the power usage I gave (80-90W) does not include the power used by the monitor. It only lists the power used by the base system (CPU, motherboard, RAM, video card, TV capture card, hard disk, power supply, keyboard, etc. -- NO monitor). A monitor will increase the power usage significantly (70-120W++ for a CRT monitor, or 40-80W+ for an LCD monitor). [ Also, note that I'm not using a power-sucking 3D video graphics card (e.g., one that also needs one or more separate power connectors from the power supply), which can easily use up more power than the CPU. ] -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 19 03:50:31 2005 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 D6FA516A4D5 for ; Wed, 19 Jan 2005 03:50:30 +0000 (GMT) Received: from bak2.mail2000.com.tw (bak2.mail2000.com.tw [210.200.181.240]) by mx1.FreeBSD.org (Postfix) with SMTP id 507D943D5F for ; Wed, 19 Jan 2005 03:50:16 +0000 (GMT) (envelope-from semin@mail2000.com.tw) Received: from 210.200.181.214V3.20S(67659:0:AUTH_RELAY) (envelope-from ); Wed, 19 Jan 2005 11:50:15 +0800 (CST) Received: By OpenMail Mailer;Wed, 19 Jan 2005 11:50:13 +0800 (CST) From: "semin@NZ" Message-ID: <1106106613.36989.semin@mail2000.com.tw> To: freebsd-hardware@freebsd.org Date: Wed, 19 Jan 2005 11:50:13 +0800 (CST) MIME-Version: 1.0 Content-Type: text/plain Subject: Audio works... and then is dead? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: semin@mail2000.com.tw List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 03:50:32 -0000 Hi there, I've got a Laptop (Compaq Presario 2166) with Conxant audio chip. I used to activate the audio with sound.ko and snd_t4dwave.ko when I use FreeBSD 5.1 without any (I suppose so) problem. I downloaded 5.3 several days ago. What happened to me is when I loaded those sound modules (not add into kernel yet), it work. When I start X.org, the sound module didn't work suddenly. The sound disappered even the modules were loaded properly. I tried to add sound modules into my kernel then make, install and reboot, and found ...it still keep dumbness!! I'm definitely sure snd_ko and snd_t4dwave.ko are the correct ones. What on earth might go wrong? Sam From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 19 07:35:57 2005 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 2B7D916A4CE; Wed, 19 Jan 2005 07:35:57 +0000 (GMT) Received: from MXR-5.estpak.ee (mta2.mail.neti.ee [194.126.101.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1ED8A43D3F; Wed, 19 Jan 2005 07:35:56 +0000 (GMT) (envelope-from sven@orionis.net) Received: from [195.50.218.17] (unknown [195.50.218.17]) by MXR-5.estpak.ee (Postfix) with ESMTP id 57E35125A00; Wed, 19 Jan 2005 09:30:28 +0200 (EET) Message-ID: <41EE0C69.50107@orionis.net> Date: Wed, 19 Jan 2005 09:29:45 +0200 From: Sven Ahtama User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-2.2.1 (20041222) (Debian) at neti.ee cc: freebsd-hardware@freebsd.org Subject: nForce3 NIC on 5.3 (i386) 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, 19 Jan 2005 07:35:57 -0000 Hello folks, Anyone here who have managed to get the nForce3 MCP NIC to work with FreeBSD 5.3 on i386 platform? After several hours of retries and kernel configuration i managed to get the if_nv.ko successfully loaded. No complaints, no errors, but also, no nv0 device found. Just like it didn't exist. I also read that one of the common problems in such cases was the agp driver, however i'm not even using one. Even more, I tried a kernel run entirely without agp support. I got the if_nv loaded as module and tried compiled-in as well. I'd really appreciate any pointers, or a conclusive confirmation, that there is no success yet. Regards, chance. From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 19 07:57:59 2005 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 A7DD216A4CE for ; Wed, 19 Jan 2005 07:57:59 +0000 (GMT) Received: from eole2.univ-lyon2.fr (eole2.univ-lyon2.fr [159.84.44.37]) by mx1.FreeBSD.org (Postfix) with SMTP id BBCF943D1D for ; Wed, 19 Jan 2005 07:57:58 +0000 (GMT) (envelope-from patpro@patpro.net) Received: from 159.84.24.128 by eole2.univ-lyon2.fr (InterScan E-Mail VirusWall NT); Wed, 19 Jan 2005 08:52:56 +0100 Received: from [159.84.142.80] (patpro.univ-lyon2.fr [159.84.142.80]) by carex.univ-lyon2.fr (Postfix) with ESMTP id 74A0323AC20 for ; Wed, 19 Jan 2005 08:57:47 +0100 (MET) Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-hardware@freebsd.org From: Patrick Proniewski Date: Wed, 19 Jan 2005 08:57:47 +0100 X-Mailer: Apple Mail (2.619) Subject: FreeBSD on shuttle ST62K (zen) 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, 19 Jan 2005 07:57:59 -0000 Hi, I want to setup a FreeBSD internet gateway between my 8Mbps DSL and my LAN. I'm thinking about using a shuttle ST62K (ZEN), and I would like to known how well this hardware is supported by FreeBSD (4.10 or 5.3). specs are here: http://global.shuttle.com/Product/barebone/brb_OverView.asp?B_id=29 according to FreeBSD hardware notes : (?=info not available) --------------------------------------------5.3---4.10 chipset: ATI RS300 .................................. ? .. ? ATI IXP150 ................................. ? .. ? Audio: Realtek ALC650 six channel audio. .......... ? .. ? Ethernet: Realtek 8100C supports 10/100 LAN .......... ? .. ? IEEE 1394a: VIA VT6307 ................................. ? .. ? 1394 OHCI v1.0 compliant ................... OK . ? TV-out: unknown ? any help greatly appreciated. patpro From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 19 10:06:11 2005 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 B3EF016A4CE for ; Wed, 19 Jan 2005 10:06:11 +0000 (GMT) Received: from mail.vslash.com (gambetta-2-82-67-185-6.fbx.proxad.net [82.67.185.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 065FC43D53 for ; Wed, 19 Jan 2005 10:06:11 +0000 (GMT) (envelope-from valery@vslash.com) Received: from [192.168.0.22] (oxe [192.168.0.22]) by mail.vslash.com (Postfix) with ESMTP id 97E6C1D92A; Wed, 19 Jan 2005 11:09:37 +0100 (CET) Message-ID: <41EE310C.3080103@vslash.com> Date: Wed, 19 Jan 2005 11:06:04 +0100 From: =?ISO-8859-1?Q?Val=E9ry?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Patrick Proniewski References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD on shuttle ST62K (zen) 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, 19 Jan 2005 10:06:11 -0000 Hi, look here, all supported devices : http://www.freebsd.org/releases/5.3R/hardware-i386.html > ATI RS300 .................................. OK .. ? ATI 9100 IGP = RS300 My own work well (without 3D i think, no try) My advice : - don't buy a shuttle, mobo are too specific, and too integrated, specially sound and network. Video : NVidia is preferred for FBSD. Go on their website, there's some drivers specially designed for FBSD, ATI don't. Good luck, v. Patrick Proniewski wrote: > Hi, > > I want to setup a FreeBSD internet gateway between my 8Mbps DSL and my > LAN. I'm thinking about using a shuttle ST62K (ZEN), and I would like to > known how well this hardware is supported by FreeBSD (4.10 or 5.3). > specs are here: > http://global.shuttle.com/Product/barebone/brb_OverView.asp?B_id=29 > > according to FreeBSD hardware notes : (?=info not available) > --------------------------------------------5.3---4.10 > chipset: > ATI RS300 .................................. ? .. ? > ATI IXP150 ................................. ? .. ? > > Audio: > Realtek ALC650 six channel audio. .......... ? .. ? > > Ethernet: > Realtek 8100C supports 10/100 LAN .......... ? .. ? > > IEEE 1394a: > VIA VT6307 ................................. ? .. ? > 1394 OHCI v1.0 compliant ................... OK . ? > > TV-out: unknown ? > > > any help greatly appreciated. > > patpro > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 19 10:18:26 2005 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 136FA16A4CE for ; Wed, 19 Jan 2005 10:18:26 +0000 (GMT) Received: from eole2.univ-lyon2.fr (eole2.univ-lyon2.fr [159.84.44.37]) by mx1.FreeBSD.org (Postfix) with SMTP id 4F93A43D5D for ; Wed, 19 Jan 2005 10:18:25 +0000 (GMT) (envelope-from patpro@patpro.net) Received: from 159.84.24.128 by eole2.univ-lyon2.fr (InterScan E-Mail VirusWall NT); Wed, 19 Jan 2005 11:13:24 +0100 Received: from [159.84.142.80] (patpro.univ-lyon2.fr [159.84.142.80]) by carex.univ-lyon2.fr (Postfix) with ESMTP id 40C9D23ABC8; Wed, 19 Jan 2005 11:18:19 +0100 (MET) In-Reply-To: <41EE310C.3080103@vslash.com> References: <41EE310C.3080103@vslash.com> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <70A97505-6A03-11D9-A274-000A95D00720@patpro.net> Content-Transfer-Encoding: quoted-printable From: Patrick Proniewski Date: Wed, 19 Jan 2005 11:18:19 +0100 To: =?ISO-8859-1?Q?Val=E9ry?= X-Mailer: Apple Mail (2.619) cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD on shuttle ST62K (zen) 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, 19 Jan 2005 10:18:26 -0000 On 19 janv. 05, at 11:06, Val=E9ry wrote: > Hi, > look here, all supported devices : > http://www.freebsd.org/releases/5.3R/hardware-i386.html > > ATI RS300 .................................. OK .. ? > ATI 9100 IGP =3D RS300 I've already looked for these ref. in the freebsd hardware notes, and I=20= can't find these chipsets. > My own work well (without 3D i think, no try) > My advice : > - don't buy a shuttle, mobo are too specific, > and too integrated, specially sound and network. > Video : NVidia is preferred for FBSD. Go on their website, > there's some drivers specially designed for FBSD, > ATI don't. well :/ thats no good news, I really want something not-too-big,=20 *silent*, and quite powerfull (compared to my old celeron 333), and in=20= the 400-500 euros range. thanks, patpro From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 19 13:37:06 2005 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 E3DFD16A4CE for ; Wed, 19 Jan 2005 13:37:06 +0000 (GMT) Received: from hotmail.com (bay13-f12.bay13.hotmail.com [64.4.31.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id C575B43D2F for ; Wed, 19 Jan 2005 13:37:06 +0000 (GMT) (envelope-from yokean1@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 19 Jan 2005 05:36:03 -0800 Message-ID: Received: from 210.195.42.16 by by13fd.bay13.hotmail.msn.com with HTTP; Wed, 19 Jan 2005 13:35:04 GMT X-Originating-IP: [210.195.42.16] X-Originating-Email: [yokean1@hotmail.com] X-Sender: yokean1@hotmail.com From: "yoke an" To: freebsd-hardware@freebsd.org Date: Wed, 19 Jan 2005 21:35:04 +0800 X-Priority: 1 Importance: High X-OriginalArrivalTime: 19 Jan 2005 13:36:03.0033 (UTC) FILETIME=[D1CFEC90:01C4FE2B] MIME-Version: 1.0 Content-Type: text/plain; format="flowed" X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: ICH5 + SATA + Seagate ST380013AS + FreeBSD v4.8? 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, 19 Jan 2005 13:37:07 -0000 Hi , I'm in the process of installing freebsd v4.8 on Tyan Transport GX21 (B2735G21S2) with Tiger i7501R S2735-8M motherboard, with Seagate SATA disks (Model: ST380013AS). I have problem with FreeBSD v4.8-Release that cannot detect my HDD. Is ICH5 support SATA mode from FreeBSD v4.8-Release? Where can I download ICH5 that support FreeBSD v4.8-Release and how's the steps on installing this. BTW, I cannot change the installation to FreeBSD v5.3 coz my application only support 4.8-Release. Cheers Ann _________________________________________________________________ Find love online with [1]MSN Personals. References 1. http://g.msn.com/8HMBENMY/2743??PS=47575 From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 19 16:14:50 2005 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 D812B16A4CE for ; Wed, 19 Jan 2005 16:14:50 +0000 (GMT) Received: from relay.introweb.nl (relay.introweb.nl [80.65.96.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A71543D68 for ; Wed, 19 Jan 2005 16:14:50 +0000 (GMT) (envelope-from edwin@introweb.nl) Received: from brievenbus1.introweb.nl (frontend1 [192.168.4.31]) by relay.introweb.nl (Postfix) with ESMTP id 9A653866936 for ; Wed, 19 Jan 2005 17:14:43 +0100 (CET) Received: from piii-1 (mail.introcom.nl [80.65.97.195]) by brievenbus1.introweb.nl (Postfix) with ESMTP id 9057210710 for ; Wed, 19 Jan 2005 17:14:43 +0100 (CET) From: "Edwin Ringersma" To: freebsd-hardware@freebsd.org Date: Wed, 19 Jan 2005 17:14:42 +0100 MIME-Version: 1.0 Message-ID: <41EE9582.12042.C39D690@localhost> Priority: normal X-mailer: Pegasus Mail for Windows (4.21b) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Subject: QLA200 support 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, 19 Jan 2005 16:14:51 -0000 Hi all, Does anyone have support for the QLA200 of Qlogic ? It identifies itself as ISP23XX but the type is 0x6312 (instead of 0x2312) I've been trying to hack some support into the isp driver but no luck so far. It just recognises it, but not the disk. (it's an ax100 which has been initialized with windows through the same controller and virtual disk is created and 100%) There is sourcecode for linux available. But that didn't help a lot so far. I just noticed some offset being 6 instead of 0 for the other adapter. http://www.qlogic.com/support/oem_product_detail.asp?p_id=680&oemid=284&oemname=QLA200 Any suggestions will be appreciated. With regards, Edwin Ringersma System Administrator -------------------------------------------------------- IntroWeb Postbus 724 7550 AS Hengelo Tel: 074 - 243 01 05 Welbergweg 30 Fax: 074 - 242 98 95 7556 PE Hengelo http://www.introweb.nl Holland -------------------------------------------------------- Internet Access & Corporate Internet Solutions -------------------------------------------------------- From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 19 16:49:57 2005 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 F30F616A4CE; Wed, 19 Jan 2005 16:49:56 +0000 (GMT) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFA1D43D45; Wed, 19 Jan 2005 16:49:54 +0000 (GMT) (envelope-from lists@jnielsen.net) Received: from stealth.local (jn@c-24-2-72-123.client.comcast.net [24.2.72.123]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id j0JGnpXI024701; Wed, 19 Jan 2005 08:49:51 -0800 (PST) (envelope-from lists@jnielsen.net) From: John Nielsen To: freebsd-hackers@freebsd.org Date: Wed, 19 Jan 2005 09:50:46 -0700 User-Agent: KMail/1.7.2 References: <41EE0C69.50107@orionis.net> In-Reply-To: <41EE0C69.50107@orionis.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501190950.47174.lists@jnielsen.net> X-Virus-Scanned: ClamAV 0.80/627/Sun Dec 12 11:53:11 2004 clamav-milter version 0.80j on ns1.jnielsen.net X-Virus-Status: Clean cc: Sven Ahtama cc: freebsd-hardware@freebsd.org Subject: Re: nForce3 NIC on 5.3 (i386) 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, 19 Jan 2005 16:49:57 -0000 On Wednesday 19 January 2005 12:29 am, Sven Ahtama wrote: > Anyone here who have managed to get the nForce3 MCP NIC to work with > FreeBSD 5.3 on i386 platform? FWIW, I've had pretty much the same experience, although you were more thorough than I was. I installed 5.3-R on a new motherboard with an MCP chipset and installed the net/nvnet port. No complaints, no errors, no NIC. I'm using a PCI card for the time being but I would love to hear about a way to get the onboard NIC working if there is one. JN From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 19 20:28:38 2005 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 A9D9916A4CE for ; Wed, 19 Jan 2005 20:28:38 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 9EA2243D41 for ; Wed, 19 Jan 2005 20:28:37 +0000 (GMT) (envelope-from bsdfan@nurfuerspam.de) Received: (qmail invoked by alias); 19 Jan 2005 20:28:36 -0000 Received: from dsl-082-083-246-219.arcor-ip.net (EHLO [127.0.0.1]) (82.83.246.219) by mail.gmx.net (mp004) with SMTP; 19 Jan 2005 21:28:36 +0100 X-Authenticated: #931807 Message-ID: <41EEC2F3.8010502@nurfuerspam.de> Date: Wed, 19 Jan 2005 21:28:35 +0100 From: Markus Dolze User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, de-de, en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org X-Enigmail-Version: 0.89.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: Support of MO-Drives? 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, 19 Jan 2005 20:28:38 -0000 Hello, On http://www.freebsdforums.org/ there was a discussion about hardware for small backup use. I thought of MO-drives (magneto-optical). This week I got access to a new Fujitsu Dynamo 1.3 GB drive with ATAPI interface. After attaching it the drive didn't get a device assigned on startup. The drive is visible when I use "atacontrol list". I went through the example kernel config files and found the atapicam device. After building and installing a new kernel with it, the drive was detected and assigned an "ad*" device. Ejecting the media and starting the drive using "camcontrol" worked as well as reading and writing. Is this the intended way to use these kind of devices? Regards Markus Dolze From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 19 20:46:27 2005 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 C709816A4CE for ; Wed, 19 Jan 2005 20:46:27 +0000 (GMT) Received: from smtp6.arnet.com.ar (smtp6.arnet.com.ar [200.45.191.24]) by mx1.FreeBSD.org (Postfix) with SMTP id 0F7AF43D2D for ; Wed, 19 Jan 2005 20:46:26 +0000 (GMT) (envelope-from netbsd@contenidosonline.com.ar) Received: (qmail 15240 invoked from network); 19 Jan 2005 20:46:10 -0000 Received: from unknown (HELO host142.200-43-99.telecom.net.ar) (200.43.99.142) by smtp6.arnet.com.ar with SMTP; 19 Jan 2005 20:46:08 -0000 From: Roberto Pereyra To: freebsd-hardware@freebsd.org Date: Wed, 19 Jan 2005 14:49:13 -0300 User-Agent: KMail/1.7 MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200501191449.13646.netbsd@contenidosonline.com.ar> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: kernel: sioxx: silo overflow with 8 ports pci MOXA cards 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, 19 Jan 2005 20:46:27 -0000 Hi I have a 8 port pci Moxa C168U/PCI and use it like ppp server (with mgetty and radius support). The server not works well because I have many "sio overflow" errors. The modem drop the link or when the link is active (some minutes later) the link don't send packets and drop. Many times the modems not answer the call. Can anybody help me ? (excuse my english) My system is Freebsd 5.2 RELEASE My kernel is GENERIC plus this: # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports options COM_MULTIPORT device puc My dmesg show: ioapic0 irqs 0-23 on motherboard pcibios: BIOS version 2.10 usb0: USB revision 1.0 usb1: USB revision 1.0 usb2: USB revision 1.0 sio4: on puc0 sio4: type 16550A sio4: unable to activate interrupt in fast mode - using normal mode sio5: on puc0 sio5: type 16550A sio5: unable to activate interrupt in fast mode - using normal mode sio6: on puc0 sio6: type 16550A sio6: unable to activate interrupt in fast mode - using normal mode sio7: on puc0 sio7: type 16550A sio7: unable to activate interrupt in fast mode - using normal mode sio8: on puc0 sio8: type 16550A sio8: unable to activate interrupt in fast mode - using normal mode sio9: on puc0 sio9: type 16550A sio9: unable to activate interrupt in fast mode - using normal mode sio10: on puc0 sio10: type 16550A sio10: unable to activate interrupt in fast mode - using normal mode sio11: on puc0 sio11: type 16550A sio11: unable to activate interrupt in fast mode - using normal mode sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A And my /var/log/messages show: Jan 12 06:55:09 nas3 kernel: sio10: 2 more silo overflows (total 1609) Jan 12 06:56:09 nas3 kernel: sio10: 1 more silo overflow (total 1610) Jan 12 06:58:46 nas3 kernel: sio10: 1 more silo overflow (total 1611) Jan 12 06:59:39 nas3 kernel: sio10: 1 more silo overflow (total 1612) Jan 12 07:02:23 nas3 kernel: sio10: 1 more silo overflow (total 1613) Jan 12 07:04:27 nas3 kernel: sio10: 1 more silo overflow (total 1614) Jan 12 07:15:39 nas3 kernel: sio10: 1 more silo overflow (total 1615) Jan 12 07:26:09 nas3 kernel: sio10: 1 more silo overflow (total 1616) Jan 12 07:27:09 nas3 kernel: sio10: 1 more silo overflow (total 1617) Jan 12 07:46:00 nas3 kernel: sio10: 1 more silo overflow (total 1618) Jan 12 07:51:59 nas3 kernel: sio10: 1 more silo overflow (total 1619) Jan 12 07:54:03 nas3 kernel: sio10: 1 more silo overflow (total 1620) Jan 12 08:09:01 nas3 kernel: sio10: 2 more silo overflows (total 1622) Jan 12 08:45:09 nas3 kernel: sio10: 1 more silo overflow (total 1623) Jan 12 08:56:03 nas3 kernel: sio10: 1 more silo overflow (total 1624) Jan 12 09:12:04 nas3 kernel: sio10: 1 more silo overflow (total 1625) Jan 12 09:46:42 nas3 kernel: sio10: 1 more silo overflow (total 1626) Jan 12 09:49:32 nas3 kernel: sio10: 1 more silo overflow (total 1627) Jan 12 10:16:08 nas3 kernel: sio10: 1 more silo overflow (total 1628) Jan 12 10:31:09 nas3 kernel: sio10: 1 more silo overflow (total 1629) Jan 12 10:32:40 nas3 kernel: sio10: 1 more silo overflow (total 1630) Jan 12 10:50:45 nas3 kernel: sio10: 1 more silo overflow (total 1631) Jan 12 11:09:52 nas3 kernel: sio10: 1 more silo overflow (total 1632) Jan 12 11:10:09 nas3 kernel: sio10: 1 more silo overflow (total 1633) Jan 12 11:35:11 nas3 kernel: sio10: 1 more silo overflow (total 1634) Jan 12 11:49:23 nas3 kernel: sio10: 1 more silo overflow (total 1635) Jan 12 11:52:14 nas3 kernel: sio10: 1 more silo overflow (total 1636) Jan 12 11:53:39 nas3 kernel: sio10: 1 more silo overflow (total 1637) Jan 12 12:18:09 nas3 kernel: sio10: 1 more silo overflow (total 1638) Jan 12 12:25:10 nas3 kernel: sio10: 1 more silo overflow (total 1639) Jan 12 12:27:39 nas3 kernel: sio10: 1 more silo overflow (total 1640) Jan 12 12:57:22 nas3 kernel: sio10: 1 more silo overflow (total 1641) Jan 12 13:05:24 nas3 kernel: sio10: 1 more silo overflow (total 1642) Jan 12 13:05:55 nas3 kernel: sio10: 1 more silo overflow (total 1643) Jan 12 13:40:32 nas3 kernel: sio10: 1 more silo overflow (total 1644) Jan 12 13:48:17 nas3 kernel: sio10: 1 more silo overflow (total 1645) Jan 12 14:20:58 nas3 kernel: sio10: 1 more silo overflow (total 1646) Jan 12 14:22:23 nas3 kernel: sio10: 1 more silo overflow (total 1647) Jan 12 14:23:25 nas3 kernel: sio10: 1 more silo overflow (total 1648) Jan 12 14:23:39 nas3 kernel: sio10: 1 more silo overflow (total 1649) Jan 12 14:23:48 nas3 kernel: sio10: 1 more silo overflow (total 1650) Jan 12 14:23:56 nas3 kernel: sio10: 1 more silo overflow (total 1651) Jan 12 14:24:05 nas3 kernel: sio10: 1 more silo overflow (total 1652) Jan 12 14:24:09 nas3 kernel: sio10: 1 more silo overflow (total 1653) Jan 12 14:24:27 nas3 kernel: sio10: 1 more silo overflow (total 1654) Jan 12 15:05:09 nas3 kernel: sio10: 1 more silo overflow (total 1655) Jan 12 15:15:06 nas3 kernel: sio10: 1 more silo overflow (total 1656) Jan 12 15:19:14 nas3 kernel: sio10: 1 more silo overflow (total 1657) Jan 12 15:28:06 nas3 kernel: sio10: 1 more silo overflow (total 1658) Jan 12 15:39:53 nas3 kernel: sio10: 1 more silo overflow (total 1659) Jan 12 15:41:57 nas3 kernel: sio10: 1 more silo overflow (total 1660) Jan 12 15:49:38 nas3 kernel: sio10: 1 more silo overflow (total 1661) Jan 12 16:03:08 nas3 kernel: sio10: 1 more silo overflow (total 1662) Jan 12 16:18:08 nas3 kernel: sio10: 1 more silo overflow (total 1663) Jan 12 16:19:07 nas3 kernel: sio10: 1 more silo overflow (total 1664) Jan 12 16:39:09 nas3 kernel: sio10: 1 more silo overflow (total 1665) Jan 12 16:40:21 nas3 kernel: sio10: 1 more silo overflow (total 1666) Jan 12 16:48:05 nas3 kernel: sio10: 1 more silo overflow (total 1667) Jan 12 17:07:09 nas3 kernel: sio10: 1 more silo overflow (total 1668) Jan 12 17:36:11 nas3 kernel: sio10: 1 more silo overflow (total 1669) Jan 12 17:37:10 nas3 kernel: sio10: 1 more silo overflow (total 1670) Jan 12 17:49:04 nas3 kernel: sio10: 1 more silo overflow (total 1671) Jan 12 17:49:09 nas3 kernel: sio10: 1 more silo overflow (total 1672) Jan 12 17:55:40 nas3 kernel: sio10: 1 more silo overflow (total 1673) Jan 12 17:59:54 nas3 kernel: sio10: 1 more silo overflow (total 1674) Jan 12 18:29:10 nas3 kernel: sio10: 1 more silo overflow (total 1675) Jan 12 18:38:09 nas3 kernel: sio10: 1 more silo overflow (total 1676) Jan 12 18:45:10 nas3 kernel: sio10: 1 more silo overflow (total 1677) Jan 12 19:06:09 nas3 kernel: sio10: 1 more silo overflow (total 1678) Jan 12 19:17:03 nas3 kernel: sio10: 1 more silo overflow (total 1679) Jan 12 19:47:10 nas3 kernel: sio10: 1 more silo overflow (total 1680) Jan 12 19:51:10 nas3 kernel: sio10: 1 more silo overflow (total 1681) Jan 12 20:03:55 nas3 kernel: sio10: 1 more silo overflow (total 1682) Jan 12 20:23:01 nas3 kernel: sio10: 1 more silo overflow (total 1683) Jan 12 20:36:59 nas3 kernel: sio10: 1 more silo overflow (total 1684) Jan 12 21:26:04 nas3 kernel: sio10: 1 more silo overflow (total 1685) Jan 12 21:35:02 nas3 kernel: sio10: 1 more silo overflow (total 1686) Jan 12 22:11:10 nas3 kernel: sio10: 1 more silo overflow (total 1687) Jan 12 22:11:32 nas3 kernel: sio10: 1 more silo overflow (total 1688) Jan 12 22:12:02 nas3 kernel: sio10: 1 more silo overflow (total 1689) Jan 12 22:12:34 nas3 kernel: sio10: 1 more silo overflow (total 1690) Jan 12 22:12:40 nas3 kernel: sio10: 1 more silo overflow (total 1691) Jan 12 22:13:00 nas3 kernel: sio10: 1 more silo overflow (total 1692) Jan 12 22:24:03 nas3 kernel: sio10: 1 more silo overflow (total 1693) Jan 12 22:28:04 nas3 kernel: sio10: 1 more silo overflow (total 1694) Jan 12 23:02:40 nas3 kernel: sio10: 1 more silo overflow (total 1695) Jan 12 23:12:30 nas3 kernel: sio10: 1 more silo overflow (total 1696) Jan 12 23:15:05 nas3 kernel: sio10: 1 more silo overflow (total 1697) Jan 12 23:26:27 nas3 kernel: sio10: 1 more silo overflow (total 1698) Jan 12 23:30:03 nas3 kernel: sio10: 1 more silo overflow (total 1699) Jan 12 23:39:52 nas3 kernel: sio10: 1 more silo overflow (total 1700) Jan 13 00:05:42 nas3 kernel: sio10: 1 more silo overflow (total 1701) Jan 13 01:04:10 nas3 kernel: sio10: 1 more silo overflow (total 1702) Jan 13 01:17:32 nas3 kernel: sio10: 1 more silo overflow (total 1703) Jan 13 01:35:06 nas3 kernel: sio10: 1 more silo overflow (total 1704) Jan 13 01:37:10 nas3 kernel: sio10: 1 more silo overflow (total 1705) Jan 13 02:22:20 nas3 kernel: sio10: 1 more silo overflow (total 1706) Jan 13 02:34:10 nas3 kernel: sio10: 1 more silo overflow (total 1707) Jan 13 03:42:48 nas3 kernel: sio10: 1 more silo overflow (total 1708) Jan 13 03:58:10 nas3 kernel: sio10: 1 more silo overflow (total 1709) Jan 13 04:01:50 nas3 kernel: sio10: 1 more silo overflow (total 1710) Jan 13 04:04:55 nas3 kernel: sio10: 1 more silo overflow (total 1711) Jan 13 04:40:04 nas3 kernel: sio10: 1 more silo overflow (total 1712) Jan 13 04:49:53 nas3 kernel: sio10: 1 more silo overflow (total 1713) Jan 13 04:53:40 nas3 kernel: sio10: 1 more silo overflow (total 1714) Jan 13 04:59:42 nas3 kernel: sio10: 1 more silo overflow (total 1715) Jan 13 05:04:21 nas3 kernel: sio10: 1 more silo overflow (total 1716) Jan 13 05:05:32 nas3 kernel: sio10: 1 more silo overflow (total 1717) Jan 13 05:12:37 nas3 kernel: sio10: 1 more silo overflow (total 1718) Jan 13 09:37:28 nas3 kernel: sio10: 1 more silo overflow (total 1719) Jan 13 09:50:24 nas3 kernel: sio10: 1 more silo overflow (total 1720) Jan 13 10:58:04 nas3 kernel: sio10: 1 more silo overflow (total 1721) Jan 13 11:13:40 nas3 kernel: sio10: 1 more silo overflow (total 1722) Jan 13 11:43:10 nas3 kernel: sio10: 1 more silo overflow (total 1723) Jan 13 11:46:08 nas3 kernel: sio10: 1 more silo overflow (total 1724) Jan 13 11:49:10 nas3 kernel: sio10: 1 more silo overflow (total 1725) Jan 13 11:49:13 nas3 kernel: sio10: 1 more silo overflow (total 1726) Jan 13 11:52:10 nas3 kernel: sio10: 1 more silo overflow (total 1727) Jan 13 11:52:19 nas3 kernel: sio10: 1 more silo overflow (total 1728) Jan 13 11:53:22 nas3 kernel: sio10: 1 more silo overflow (total 1729) Jan 13 11:56:40 nas3 kernel: sio10: 1 more silo overflow (total 1730) Jan 13 11:56:58 nas3 kernel: sio10: 1 more silo overflow (total 1731) Jan 13 12:01:37 nas3 kernel: sio10: 1 more silo overflow (total 1732) Jan 13 12:05:15 nas3 kernel: sio10: 1 more silo overflow (total 1733) Jan 13 12:07:19 nas3 kernel: sio10: 1 more silo overflow (total 1734) Jan 13 12:10:33 nas3 kernel: sio10: 1 more silo overflow (total 1735) Jan 13 12:18:09 nas3 kernel: sio10: 1 more silo overflow (total 1736) Jan 13 12:18:40 nas3 kernel: sio10: 2 more silo overflows (total 1738) Jan 13 12:20:13 nas3 kernel: sio10: 1 more silo overflow (total 1739) Jan 13 12:22:18 nas3 kernel: sio10: 1 more silo overflow (total 1740) Jan 13 12:25:23 nas3 kernel: sio10: 1 more silo overflow (total 1741) Jan 13 12:29:00 nas3 kernel: sio10: 1 more silo overflow (total 1742) Jan 13 12:29:49 nas3 kernel: sio10: 1 more silo overflow (total 1743) Jan 13 12:30:02 nas3 kernel: sio10: 1 more silo overflow (total 1744) Jan 13 12:33:09 nas3 kernel: sio10: 1 more silo overflow (total 1745) Jan 13 12:35:10 nas3 kernel: sio10: 1 more silo overflow (total 1746) Jan 13 12:35:46 nas3 kernel: sio10: 1 more silo overflow (total 1747) Jan 13 12:36:11 nas3 kernel: sio10: 1 more silo overflow (total 1748) Jan 13 12:36:54 nas3 kernel: sio10: 1 more silo overflow (total 1749) Jan 13 12:43:28 nas3 kernel: sio10: 1 more silo overflow (total 1750) Jan 13 12:44:30 nas3 kernel: sio10: 1 more silo overflow (total 1751) Jan 13 12:47:37 nas3 kernel: sio10: 1 more silo overflow (total 1752) Jan 13 13:02:58 nas3 kernel: sio10: 1 more silo overflow (total 1753) Jan 13 13:04:11 nas3 kernel: sio10: 1 more silo overflow (total 1754) Jan 13 13:14:59 nas3 kernel: sio10: 1 more silo overflow (total 1755) Jan 13 13:41:20 nas3 kernel: sio10: 1 more silo overflow (total 1756) Jan 13 13:41:30 nas3 kernel: sio10: 1 more silo overflow (total 1757) Jan 13 13:41:41 nas3 kernel: sio10: 1 more silo overflow (total 1758) Jan 13 13:41:52 nas3 kernel: sio10: 1 more silo overflow (total 1759) Jan 13 13:42:04 nas3 kernel: sio10: 1 more silo overflow (total 1760) Jan 13 13:42:23 nas3 kernel: sio10: 1 more silo overflow (total 1761) Jan 13 13:42:54 nas3 kernel: sio10: 1 more silo overflow (total 1762) Jan 13 13:43:24 nas3 kernel: sio10: 1 more silo overflow (total 1763) Jan 13 13:46:31 nas3 kernel: sio10: 1 more silo overflow (total 1764) Jan 13 14:00:28 nas3 kernel: sio10: 1 more silo overflow (total 1765) Jan 13 14:00:41 nas3 kernel: sio10: 1 more silo overflow (total 1766) Jan 13 14:01:11 nas3 kernel: sio10: 1 more silo overflow (total 1767) Jan 13 14:01:30 nas3 kernel: sio10: 1 more silo overflow (total 1768) Jan 13 14:02:00 nas3 kernel: sio10: 1 more silo overflow (total 1769) Jan 13 14:02:11 nas3 kernel: sio10: 1 more silo overflow (total 1770) Jan 13 14:03:34 nas3 kernel: sio10: 1 more silo overflow (total 1771) Jan 13 14:04:35 nas3 kernel: sio10: 1 more silo overflow (total 1772) Jan 13 14:07:10 nas3 kernel: sio10: 1 more silo overflow (total 1773) Jan 13 14:12:21 nas3 kernel: sio10: 1 more silo overflow (total 1774) Jan 13 14:19:10 nas3 kernel: sio10: 1 more silo overflow (total 1775) Jan 13 14:36:45 nas3 kernel: sio10: 1 more silo overflow (total 1776) Jan 13 14:40:26 nas3 kernel: sio10: 1 more silo overflow (total 1777) Jan 13 15:05:11 nas3 kernel: sio10: 1 more silo overflow (total 1778) Jan 13 15:25:12 nas3 kernel: sio10: 1 more silo overflow (total 1779) Jan 13 15:36:34 nas3 kernel: sio10: 1 more silo overflow (total 1780) Jan 13 16:04:58 nas3 kernel: sio10: 1 more silo overflow (total 1781) Jan 13 16:23:04 nas3 kernel: sio10: 1 more silo overflow (total 1782) Jan 13 16:27:11 nas3 kernel: sio10: 1 more silo overflow (total 1783) Jan 13 16:35:58 nas3 kernel: sio10: 1 more silo overflow (total 1784) Jan 13 16:47:05 nas3 kernel: sio10: 1 more silo overflow (total 1785) Jan 13 16:57:10 nas3 kernel: sio10: 1 more silo overflow (total 1786) Jan 13 17:36:06 nas3 kernel: sio10: 1 more silo overflow (total 1787) Jan 13 17:47:17 nas3 kernel: sio10: 1 more silo overflow (total 1788) Jan 13 17:56:04 nas3 kernel: sio10: 1 more silo overflow (total 1789) Jan 13 17:58:11 nas3 kernel: sio10: 1 more silo overflow (total 1790) Jan 13 18:06:41 nas3 kernel: sio10: 1 more silo overflow (total 1791) Jan 13 18:28:06 nas3 kernel: sio10: 1 more silo overflow (total 1792) Jan 13 18:33:11 nas3 kernel: sio10: 1 more silo overflow (total 1793) Jan 13 18:34:49 nas3 kernel: sio10: 1 more silo overflow (total 1794) Jan 13 18:47:57 nas3 kernel: ioapic0 irqs 0-23 on motherboard Jan 13 18:47:57 nas3 kernel: pcibios: BIOS version 2.10 Jan 13 18:47:57 nas3 kernel: usb0: USB revision 1.0 Jan 13 18:47:57 nas3 kernel: usb1: USB revision 1.0 Jan 13 18:47:57 nas3 kernel: usb2: USB revision 1.0 Jan 13 18:47:57 nas3 kernel: sio4: on puc0 Jan 13 18:47:57 nas3 kernel: sio4: type 16550A Jan 13 18:47:57 nas3 kernel: sio4: unable to activate interrupt in fast mode - using normal mode Jan 13 18:47:57 nas3 kernel: sio5: on puc0 Jan 13 18:47:57 nas3 kernel: sio5: type 16550A Jan 13 18:47:57 nas3 kernel: sio5: unable to activate interrupt in fast mode - using normal mode Jan 13 18:47:57 nas3 kernel: sio6: on puc0 Jan 13 18:47:57 nas3 kernel: sio6: type 16550A Jan 13 18:47:57 nas3 kernel: sio6: unable to activate interrupt in fast mode - using normal mode Jan 13 18:47:57 nas3 kernel: sio7: on puc0 Jan 13 18:47:57 nas3 kernel: sio7: type 16550A Jan 13 18:47:57 nas3 kernel: sio7: unable to activate interrupt in fast mode - using normal mode Jan 13 18:47:57 nas3 kernel: sio8: on puc0 Jan 13 18:47:57 nas3 kernel: sio8: type 16550A Jan 13 18:47:57 nas3 kernel: sio8: unable to activate interrupt in fast mode - using normal mode Jan 13 18:47:57 nas3 kernel: sio9: on puc0 Jan 13 18:47:57 nas3 kernel: sio9: type 16550A Jan 13 18:47:57 nas3 kernel: sio9: unable to activate interrupt in fast mode - using normal mode Jan 13 18:47:57 nas3 kernel: sio10: on puc0 Jan 13 18:47:57 nas3 kernel: sio10: type 16550A Jan 13 18:47:57 nas3 kernel: sio10: unable to activate interrupt in fast mode - using normal mode Jan 13 18:47:57 nas3 kernel: sio11: on puc0 Jan 13 18:47:57 nas3 kernel: sio11: type 16550A Jan 13 18:47:57 nas3 kernel: sio11: unable to activate interrupt in fast mode - using normal mode Jan 13 18:47:57 nas3 kernel: sio0 port 0x3f8-0x3ff irq 4 on acpi0 Jan 13 18:47:57 nas3 kernel: sio0: type 16550A Jan 13 18:47:57 nas3 kernel: sio1 port 0x2f8-0x2ff irq 3 on acpi0 Jan 13 18:47:57 nas3 kernel: sio1: type 16550A Jan 13 19:29:19 nas3 kernel: sio5: 1 more silo overflow (total 1) Jan 13 19:29:56 nas3 kernel: sio5: 1 more silo overflow (total 2) Jan 13 19:39:07 nas3 kernel: sio10: 2 more silo overflows (total 2) Jan 13 19:53:56 nas3 kernel: sio10: 1 more silo overflow (total 3) Jan 19 17:00:27 nas3 kernel: ioapic0 irqs 0-23 on motherboard Jan 19 17:00:27 nas3 kernel: pcibios: BIOS version 2.10 Jan 19 17:00:27 nas3 kernel: usb0: USB revision 1.0 Jan 19 17:00:27 nas3 kernel: usb1: USB revision 1.0 Jan 19 17:00:27 nas3 kernel: usb2: USB revision 1.0 Jan 19 17:00:27 nas3 kernel: sio4: on puc0 Jan 19 17:00:27 nas3 kernel: sio4: type 16550A Jan 19 17:00:27 nas3 kernel: sio4: unable to activate interrupt in fast mode - using normal mode Jan 19 17:00:27 nas3 kernel: sio5: on puc0 Jan 19 17:00:27 nas3 kernel: sio5: type 16550A Jan 19 17:00:27 nas3 kernel: sio5: unable to activate interrupt in fast mode - using normal mode Jan 19 17:00:27 nas3 kernel: sio6: on puc0 Jan 19 17:00:27 nas3 kernel: sio6: type 16550A Jan 19 17:00:27 nas3 kernel: sio6: unable to activate interrupt in fast mode - using normal mode Jan 19 17:00:27 nas3 kernel: sio7: on puc0 Jan 19 17:00:27 nas3 kernel: sio7: type 16550A Jan 19 17:00:27 nas3 kernel: sio7: unable to activate interrupt in fast mode - using normal mode Jan 19 17:00:27 nas3 kernel: sio8: on puc0 Jan 19 17:00:27 nas3 kernel: sio8: type 16550A Jan 19 17:00:27 nas3 kernel: sio8: unable to activate interrupt in fast mode - using normal mode Jan 19 17:00:27 nas3 kernel: sio9: on puc0 Jan 19 17:00:27 nas3 kernel: sio9: type 16550A Jan 19 17:00:27 nas3 kernel: sio9: unable to activate interrupt in fast mode - using normal mode Jan 19 17:00:27 nas3 kernel: sio10: on puc0 Jan 19 17:00:27 nas3 kernel: sio10: type 16550A Jan 19 17:00:27 nas3 kernel: sio10: unable to activate interrupt in fast mode - using normal mode Jan 19 17:00:27 nas3 kernel: sio11: on puc0 Jan 19 17:00:27 nas3 kernel: sio11: type 16550A Jan 19 17:00:27 nas3 kernel: sio11: unable to activate interrupt in fast mode - using normal mode Jan 19 17:00:27 nas3 kernel: sio0 port 0x3f8-0x3ff irq 4 on acpi0 Jan 19 17:00:27 nas3 kernel: sio0: type 16550A Jan 19 17:00:27 nas3 kernel: sio1 port 0x2f8-0x2ff irq 3 on acpi0 Jan 19 17:00:27 nas3 kernel: sio1: type 16550A From owner-freebsd-hardware@FreeBSD.ORG Thu Jan 20 06:34:21 2005 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 651F216A4CE for ; Thu, 20 Jan 2005 06:34:21 +0000 (GMT) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCF9943D1F for ; Thu, 20 Jan 2005 06:34:20 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86])j0K6Y1A6020131; Thu, 20 Jan 2005 17:34:01 +1100 Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) j0K6Xwj9010487; Thu, 20 Jan 2005 17:33:59 +1100 Date: Thu, 20 Jan 2005 17:33:58 +1100 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Roberto Pereyra In-Reply-To: <200501191449.13646.netbsd@contenidosonline.com.ar> Message-ID: <20050120171850.Q33587@delplex.bde.org> References: <200501191449.13646.netbsd@contenidosonline.com.ar> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hardware@FreeBSD.org Subject: Re: kernel: sioxx: silo overflow with 8 ports pci MOXA cards 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: Thu, 20 Jan 2005 06:34:21 -0000 On Wed, 19 Jan 2005, Roberto Pereyra wrote: > I have a 8 port pci Moxa C168U/PCI and use it like ppp server (with mgetty and > radius support). > > The server not works well because I have many "sio overflow" errors. The modem > drop the link or when the link is active (some minutes later) the link don't > send packets and drop. Large numbers of ports might cause this problem under versions of FreeBSD newer than FreeBSD-4, due to poor interrupt latency in these versions. However, "large" is hopefully more than 8. > Many times the modems not answer the call. > > Can anybody help me ? (excuse my english) > > My system is Freebsd 5.2 RELEASE > > My kernel is GENERIC plus this: > > # Serial (COM) ports > device sio # 8250, 16[45]50 based serial ports > options COM_MULTIPORT > device puc COM_MULTIPORT is not needed for puc devices. Using it when it is not needed (for other devices) just increases interrupt latency and reduces efficiency. (The driver doesn't handle mixtures of devices (with only some devices needing it) very well.) > My dmesg show: > > ioapic0 irqs 0-23 on motherboard > pcibios: BIOS version 2.10 > usb0: USB revision 1.0 > usb1: USB revision 1.0 > usb2: USB revision 1.0 > sio4: on puc0 > sio4: type 16550A > sio4: unable to activate interrupt in fast mode - using normal mode > sio5: on puc0 > sio5: type 16550A > sio5: unable to activate interrupt in fast mode - using normal mode > sio6: on puc0 > sio6: type 16550A > sio6: unable to activate interrupt in fast mode - using normal mode > sio7: on puc0 > sio7: type 16550A > sio7: unable to activate interrupt in fast mode - using normal mode > sio8: on puc0 > sio8: type 16550A > sio8: unable to activate interrupt in fast mode - using normal mode > sio9: on puc0 > sio9: type 16550A > sio9: unable to activate interrupt in fast mode - using normal mode > sio10: on puc0 > sio10: type 16550A > sio10: unable to activate interrupt in fast mode - using normal mode > sio11: on puc0 > sio11: type 16550A > sio11: unable to activate interrupt in fast mode - using normal mode > sio0 port 0x3f8-0x3ff irq 4 on acpi0 > sio0: type 16550A > sio1 port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A Try using PUC_FASTINTR to reduce interrupt latency. This may require juggling irqs so that the puc interrupt is not shared (hopefully not since apic mode is used). This is not the default because if the interrupt ends up shared then it may do more than just fail to activate the interrupt in fast mode as above -- it may break other devices that want the interrupt in normal mode, depending on whether it is activated in fast mode first. Bryce From owner-freebsd-hardware@FreeBSD.ORG Thu Jan 20 13:25:53 2005 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 7D24616A4CE for ; Thu, 20 Jan 2005 13:25:53 +0000 (GMT) Received: from mail.intellstat.com (adsl-69-213-82-197.dsl.sfldmi.ameritech.net [69.213.82.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 517D843D55 for ; Thu, 20 Jan 2005 13:25:52 +0000 (GMT) (envelope-from gregs@intellstat.com) Date: Thu, 20 Jan 2005 08:25:50 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-ID: <59B6D51629A7D94DB850D903FAF46B3901234B@mario.home.local> Content-class: urn:content-classes:message X-MS-Has-Attach: X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 X-MS-TNEF-Correlator: Thread-Topic: Promise PDC20269 UDMA133 controller -- Hard drives not showing up Thread-Index: AcT+848s9DjiR6CNQfeGku/cXjFw+A== From: "Greg Smythe" To: Subject: Promise PDC20269 UDMA133 controller -- Hard drives not showing up 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: Thu, 20 Jan 2005 13:25:53 -0000 =20 Hello --=20 I installed 5.3, CVSUP'd stable and ports. I am unable to see the hard = drives on this controller with either the GENERIC kernel or my custom = one. I am also getting errors on kernel start up that I can't find = referenced anywhere. Anyone have any ideas? Thank you!=20 dmesg:=20 Copyright (c) 1992-2005 The FreeBSD Project.=20 Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 = The Regents of the University of California. All rights = reserved.=20 FreeBSD 5.3-STABLE #2: Tue Jan 18 16:00:26 EST 2005=20 root@www-alnm.tkcinc.com:/usr/obj/usr/src/sys/WWW-ALNM=20 Timecounter "i8254" frequency 1193182 Hz quality 0=20 CPU: AMD Athlon(tm) Processor (807.96-MHz 686-class CPU)=20 Origin =3D "AuthenticAMD" Id =3D 0x642 Stepping =3D 2=20 = Features=3D0x183f9ff=20 AMD Features=3D0xc0440000=20 real memory =3D 805240832 (767 MB)=20 avail memory =3D 782426112 (746 MB)=20 npx0: [FAST]=20 npx0: on motherboard=20 npx0: INT 16 interface=20 acpi0: on motherboard=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 acpi0: Power Button (fixed)=20 acpi0: Sleep Button (fixed)=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000=20 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0=20 cpu0: on acpi0=20 acpi_tz0: on acpi0=20 acpi_button0: on acpi0=20 pcib0: port 0xcf8-0xcff on acpi0=20 pci0: on pcib0=20 agp0: port 0xd200-0xd203 mem = 0xefdff000-0xefdfffff,0xec000000-0xedffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0=20 pci1: on pcib1=20 pci1: at device 5.0 (no driver attached)=20 isab0: at device 7.0 on pci0=20 isa0: on isab0=20 atapci0: port = 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0=20 ata0: channel #0 on atapci0=20 ata1: channel #1 on atapci0=20 pci0: at device 7.3 (no driver attached)=20 rl0: port 0xd400-0xd4ff mem = 0xefffbf00-0xefffbfff irq 11 at device 9.0 on pci0=20 miibus0: on rl0=20 rlphy0: on miibus0=20 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto=20 rl0: Ethernet address: 00:30:ab:00:8f:49=20 atapci1: port = 0xd600-0xd60f,0xd800-0xd803,0xda00-0xda07,0xdc00-0xdc03,0xde00-0xde07 = mem 0xefffc000-0xefffffff irq 10 at device 10.0 on pci0 ata2: channel #0 on atapci1=20 device_attach: ata2 attach returned 6=20 ata3: channel #1 on atapci1=20 atkbdc0: port 0x64,0x60 irq 1 on acpi0=20 atkbd0: irq 1 on atkbdc0=20 kbd0 at atkbd0=20 atkbd0: [GIANT-LOCKED]=20 fdc0: port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3 irq 6 = drq 2 on acpi0=20 fdc0: [FAST]=20 fd0: <1440-KB 3.5" drive> on fdc0 drive 0=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 pmtimer0 on isa0=20 orm0: at iomem 0xc8000-0xcbfff,0xc0000-0xc7fff on isa0 = sc0: at flags 0x100 on isa0=20 sc0: VGA <16 virtual consoles, flags=3D0x300>=20 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on = isa0=20 ppc0: parallel port not found.=20 sio0: configured irq 4 not in bitmap of probed irqs 0=20 sio0: port may not be enabled=20 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0=20 sio0: type 8250 or not responding=20 sio1: configured irq 3 not in bitmap of probed irqs 0=20 sio1: port may not be enabled=20 Timecounter "TSC" frequency 807958859 Hz quality 800=20 Timecounters tick every 10.000 msec=20 ad0: 19547MB [39714/16/63] at ata0-master = UDMA66=20 ad2: 114473MB [232581/16/63] at ata1-master UDMA66=20 ad3: 114473MB [232581/16/63] at ata1-slave UDMA66=20 Mounting root from ufs:/dev/ad0s1a=20 Kernel Config:=20 machine i386=20 cpu I686_CPU=20 ident WWW-ALNM=20 options SCHED_4BSD # 4BSD scheduler=20 options INET # InterNETworking=20 options INET6 # IPv6 communications protocols=20 options FFS # Berkeley Fast Filesystem=20 options SOFTUPDATES # Enable FFS soft updates = support=20 options UFS_ACL # Support for access control = lists=20 options UFS_DIRHASH # Improve performance on big = directoriesoptions MD_ROOT # MD is a potential = root device options NFSCLIENT # Network Filesystem Client=20 options NFSSERVER # Network Filesystem Server=20 options NFS_ROOT # NFS usable as /, requires = NFSCLIENT=20 options MSDOSFS # MSDOS Filesystem=20 options CD9660 # ISO 9660 Filesystem=20 options PROCFS # Process filesystem (requires = PSEUDOFS)options PSEUDOFS # Pseudo-filesystem = framework options GEOM_GPT # GUID Partition Tables.=20 options COMPAT_43 # Compatible with BSD 4.3 [KEEP = THIS!]=20 options COMPAT_FREEBSD4 # Compatible with FreeBSD4=20 options SCSI_DELAY=3D15000 # Delay (in ms) before probing = SCSI=20 options KTRACE # ktrace(1) support=20 options SYSVSHM # SYSV-style shared memory=20 options SYSVMSG # SYSV-style message queues=20 options SYSVSEM # SYSV-style semaphores=20 options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time = extensions=20 options KBD_INSTALL_CDEV # install a CDEV entry in /dev=20 # output. Adds ~215k to driver. = options ADAPTIVE_GIANT # Giant mutex is adaptive.=20 device apic # I/O APIC=20 # Bus support. Do not remove isa, even if you have no isa slots=20 device isa=20 device eisa=20 device pci=20 # Floppy drives=20 device fdc=20 # ATA and ATAPI devices=20 device ata=20 device atadisk # ATA disk drives=20 device ataraid # ATA RAID drives=20 device atapicd # ATAPI CDROM drives=20 device atapifd # ATAPI floppy drives=20 #device atapist # ATAPI tape drives=20 options ATA_STATIC_ID # Static device numbering=20 # atkbdc0 controls both the keyboard and the PS/2 mouse=20 device atkbdc # AT keyboard controller=20 device atkbd # AT keyboard=20 device psm # PS/2 mouse=20 device vga # VGA video card driver=20 #device splash # Splash screen and screen saver support = # syscons is the default console driver, resembling an SCO console=20 device sc=20 device agp # support several AGP chipsets=20 # Floating point support - do not disable.=20 device npx=20 # Power management support (see NOTES for more options)=20 #device apm=20 # Add suspend/resume support for the i8254.=20 device pmtimer=20 # Serial (COM) ports=20 device sio # 8250, 16[45]50 based serial ports=20 # Parallel port=20 device ppc=20 device ppbus # Parallel port bus (required)=20 device lpt # Printer=20 device plip # TCP/IP over parallel=20 device ppi # Parallel port interface device=20 #device vpo # Requires scbus and da=20 # PCI Ethernet NICs that use the common MII bus controller code.=20 # NOTE: Be sure to keep the 'device miibus' line in order to use these = NICs!=20 device miibus # MII bus support=20 device xl # 3Com 3c90x (``Boomerang'', = ``Cyclone'')=20 # Pseudo devices.=20 device loop # Network loopback=20 device mem # Memory and kernel memory devices=20 device io # I/O device=20 device random # Entropy device=20 device ether # Ethernet support=20 device sl # Kernel SLIP=20 device ppp # Kernel PPP=20 device tun # Packet tunnel.=20 device pty # Pseudo-ttys (telnet etc)=20 device md # Memory "disks"=20 device gif # IPv6 and IPv4 tunneling=20 device faith # IPv6-to-IPv4 relaying (translation)=20 device ccd =20 Thank you!=20 -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=20 Greg Smythe=20 Senior Technician=20 From owner-freebsd-hardware@FreeBSD.ORG Thu Jan 20 13:51:14 2005 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 3CDBC16A4CE for ; Thu, 20 Jan 2005 13:51:14 +0000 (GMT) Received: from mail.terralink.de (mail.tlink.de [217.9.16.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4969F43D55 for ; Thu, 20 Jan 2005 13:51:13 +0000 (GMT) (envelope-from me@daniel.stefan.haischt.name) Received: from smtp.abyssworld.de (daniel-s-haischt.biz [84.252.66.2]) by mail.terralink.de (Postfix) with ESMTP id E2D61BD6A4; Thu, 20 Jan 2005 14:51:05 +0100 (CET) Received: from abyssone.abyssworld.de (smtp.abyssworld.de [192.168.1.6]) by smtp.abyssworld.de (Postfix) with SMTP id DDD28190D1; Thu, 20 Jan 2005 14:51:07 +0100 (CET) Received: from (localhost) [192.168.1.6] by abyssone.abyssworld.de with smtp (geam 0.8.4) for ; Thu, 20 Jan 2005 14:51:07 +0100 Received: from smtp.abyssworld.de ([127.0.0.1])port 10024) with ESMTP id 01956-08; Thu, 20 Jan 2005 14:51:07 +0100 (CET) Received-SPF: none (smtp.abyssworld.de: 192.168.1.6 is neither permitted nor denied by domain of daniel.stefan.haischt.name) client-ip=192.168.1.6; envelope-from=me@daniel.stefan.haischt.name; helo=[192.168.120.239]; Received: from [192.168.120.239] (smtp.abyssworld.de [192.168.1.6]) by smtp.abyssworld.de (Postfix) with ESMTP id 4BB5A190A0; Thu, 20 Jan 2005 14:51:04 +0100 (CET) Message-ID: <41EFB745.3090009@daniel.stefan.haischt.name> Date: Thu, 20 Jan 2005 14:51:01 +0100 From: "Daniel S. Haischt" User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Greg Smythe References: <59B6D51629A7D94DB850D903FAF46B3901234B@mario.home.local> In-Reply-To: <59B6D51629A7D94DB850D903FAF46B3901234B@mario.home.local> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Processed-By: GNU Anubis v4.0 X-Virus-Scanned: amavisd-new at abyssworld.de cc: freebsd-hardware@freebsd.org Subject: Re: Promise PDC20269 UDMA133 controller -- Hard drives not showing up X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: me@daniel.stefan.haischt.name List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 13:51:14 -0000 Did you try to disable ACPI (just to get rid of the error messages)? You might also hava a look at the following page -> http://tinyurl.com/3rywq Search for the subject line 'Interrupt storm on FreeBSD 5.3'. It does not help to solve your problem, but it may be that there is a problem with the PDC20269 UDMA133 controller, at least in FreeBSD 5.3 because I did use this controller without any problems together with FreeBSD 5.2.1. Greg Smythe schrieb: > > > Hello -- > > I installed 5.3, CVSUP'd stable and ports. I am unable to see the hard drives on this controller with either the GENERIC kernel or my custom one. I am also getting errors on kernel start up that I can't find referenced anywhere. Anyone have any ideas? > > Thank you! > > dmesg: > Copyright (c) 1992-2005 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 5.3-STABLE #2: Tue Jan 18 16:00:26 EST 2005 > root@www-alnm.tkcinc.com:/usr/obj/usr/src/sys/WWW-ALNM > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Athlon(tm) Processor (807.96-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 > Features=0x183f9ff > AMD Features=0xc0440000 > real memory = 805240832 (767 MB) > avail memory = 782426112 (746 MB) > npx0: [FAST] > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > acpi0: Power Button (fixed) > acpi0: Sleep Button (fixed) > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 > cpu0: on acpi0 > acpi_tz0: on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > agp0: port 0xd200-0xd203 mem 0xefdff000-0xefdfffff,0xec000000-0xedffffff at device 0.0 on pci0 > > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pci1: at device 5.0 (no driver attached) > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 > ata0: channel #0 on atapci0 > ata1: channel #1 on atapci0 > pci0: at device 7.3 (no driver attached) > rl0: port 0xd400-0xd4ff mem 0xefffbf00-0xefffbfff irq 11 at device 9.0 on pci0 > miibus0: on rl0 > rlphy0: on miibus0 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > rl0: Ethernet address: 00:30:ab:00:8f:49 > atapci1: port 0xd600-0xd60f,0xd800-0xd803,0xda00-0xda07,0xdc00-0xdc03,0xde00-0xde07 mem 0xefffc000-0xefffffff irq 10 at device 10.0 on pci0 > > ata2: channel #0 on atapci1 > device_attach: ata2 attach returned 6 > ata3: channel #1 on atapci1 > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > fdc0: port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3 irq 6 drq 2 on acpi0 > fdc0: [FAST] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > pmtimer0 on isa0 > orm0: at iomem 0xc8000-0xcbfff,0xc0000-0xc7fff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > ppc0: parallel port not found. > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 8250 or not responding > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > Timecounter "TSC" frequency 807958859 Hz quality 800 > Timecounters tick every 10.000 msec > ad0: 19547MB [39714/16/63] at ata0-master UDMA66 > ad2: 114473MB [232581/16/63] at ata1-master UDMA66 > ad3: 114473MB [232581/16/63] at ata1-slave UDMA66 > Mounting root from ufs:/dev/ad0s1a > > > > Kernel Config: > > machine i386 > cpu I686_CPU > ident WWW-ALNM > > options SCHED_4BSD # 4BSD scheduler > options INET # InterNETworking > options INET6 # IPv6 communications protocols > options FFS # Berkeley Fast Filesystem > options SOFTUPDATES # Enable FFS soft updates support > options UFS_ACL # Support for access control lists > options UFS_DIRHASH # Improve performance on big directoriesoptions MD_ROOT # MD is a potential root device > > options NFSCLIENT # Network Filesystem Client > options NFSSERVER # Network Filesystem Server > options NFS_ROOT # NFS usable as /, requires NFSCLIENT > options MSDOSFS # MSDOS Filesystem > options CD9660 # ISO 9660 Filesystem > options PROCFS # Process filesystem (requires PSEUDOFS)options PSEUDOFS # Pseudo-filesystem framework > > options GEOM_GPT # GUID Partition Tables. > options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] > options COMPAT_FREEBSD4 # Compatible with FreeBSD4 > options SCSI_DELAY=15000 # Delay (in ms) before probing SCSI > options KTRACE # ktrace(1) support > options SYSVSHM # SYSV-style shared memory > options SYSVMSG # SYSV-style message queues > options SYSVSEM # SYSV-style semaphores > options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions > options KBD_INSTALL_CDEV # install a CDEV entry in /dev > # output. Adds ~215k to driver. > options ADAPTIVE_GIANT # Giant mutex is adaptive. > > device apic # I/O APIC > > # Bus support. Do not remove isa, even if you have no isa slots > device isa > device eisa > device pci > > # Floppy drives > device fdc > > # ATA and ATAPI devices > device ata > device atadisk # ATA disk drives > device ataraid # ATA RAID drives > device atapicd # ATAPI CDROM drives > device atapifd # ATAPI floppy drives > #device atapist # ATAPI tape drives > options ATA_STATIC_ID # Static device numbering > > # atkbdc0 controls both the keyboard and the PS/2 mouse > device atkbdc # AT keyboard controller > device atkbd # AT keyboard > device psm # PS/2 mouse > > device vga # VGA video card driver > > #device splash # Splash screen and screen saver support > > # syscons is the default console driver, resembling an SCO console > device sc > > device agp # support several AGP chipsets > > # Floating point support - do not disable. > device npx > > # Power management support (see NOTES for more options) > #device apm > # Add suspend/resume support for the i8254. > device pmtimer > > # Serial (COM) ports > device sio # 8250, 16[45]50 based serial ports > > # Parallel port > device ppc > device ppbus # Parallel port bus (required) > device lpt # Printer > device plip # TCP/IP over parallel > device ppi # Parallel port interface device > #device vpo # Requires scbus and da > > # PCI Ethernet NICs that use the common MII bus controller code. > # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! > device miibus # MII bus support > device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') > > # Pseudo devices. > device loop # Network loopback > device mem # Memory and kernel memory devices > device io # I/O device > device random # Entropy device > device ether # Ethernet support > device sl # Kernel SLIP > device ppp # Kernel PPP > device tun # Packet tunnel. > device pty # Pseudo-ttys (telnet etc) > device md # Memory "disks" > device gif # IPv6 and IPv4 tunneling > device faith # IPv6-to-IPv4 relaying (translation) > > device ccd > > Thank you! > > -=-=-=-=-=-=-=-=-=-=-=- > Greg Smythe > Senior Technician > > > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > > !DSPAM:41efb17c20713480789068! > > -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ > finger -l haischt@daniel.stefan.haischt.name From owner-freebsd-hardware@FreeBSD.ORG Thu Jan 20 13:53:49 2005 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 4B34D16A4CE for ; Thu, 20 Jan 2005 13:53:49 +0000 (GMT) Received: from mail.intellstat.com (adsl-69-213-82-197.dsl.sfldmi.ameritech.net [69.213.82.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79ED043D54 for ; Thu, 20 Jan 2005 13:53:48 +0000 (GMT) (envelope-from gregs@intellstat.com) Date: Thu, 20 Jan 2005 08:52:18 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-ID: <59B6D51629A7D94DB850D903FAF46B3901234C@mario.home.local> Content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Promise PDC20269 UDMA133 controller -- Hard drives not showing up Thread-Index: AcT+90GoS2MPiwBiSY6i1DyoGSB60g== From: "Greg Smythe" To: Subject: RE: Promise PDC20269 UDMA133 controller -- Hard drives not showing up 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: Thu, 20 Jan 2005 13:53:49 -0000 I just had a brainstorm and tried the controller in another (clean = installed) FBSD 5.3 box and it worked fine. So I am going to rebuild the = box that I'm having a problem with (it was a binary upgrade from 4.9). =20 I'll post back with my results.=20 =20 Thanks for the response! =20 =20 =20 Greg ________________________________ From: Daniel S. Haischt [mailto:me@stefan.haischt.name] Sent: Thu 1/20/2005 8:51 AM To: Greg Smythe Cc: freebsd-hardware@freebsd.org Subject: Re: Promise PDC20269 UDMA133 controller -- Hard drives not = showing up Did you try to disable ACPI (just to get rid of the error messages)? You might also hava a look at the following page -> http://tinyurl.com/3rywq Search for the subject line 'Interrupt storm on FreeBSD 5.3'. It does not help to solve your problem, but it may be that there is a problem with the PDC20269 UDMA133 controller, at least in FreeBSD 5.3 because I did use this controller without any problems together with FreeBSD 5.2.1. Greg Smythe schrieb: > =20 > > Hello -- > > I installed 5.3, CVSUP'd stable and ports. I am unable to see the hard = drives on this controller with either the GENERIC kernel or my custom = one. I am also getting errors on kernel start up that I can't find = referenced anywhere. Anyone have any ideas? > > Thank you! > > dmesg: > Copyright (c) 1992-2005 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, = 1994 > The Regents of the University of California. All rights = reserved. > FreeBSD 5.3-STABLE #2: Tue Jan 18 16:00:26 EST 2005 > root@www-alnm.tkcinc.com:/usr/obj/usr/src/sys/WWW-ALNM > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Athlon(tm) Processor (807.96-MHz 686-class CPU) > Origin =3D "AuthenticAMD" Id =3D 0x642 Stepping =3D 2 > = Features=3D0x183f9ff > AMD Features=3D0xc0440000 > real memory =3D 805240832 (767 MB) > avail memory =3D 782426112 (746 MB) > npx0: [FAST] > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > acpi0: Power Button (fixed) > acpi0: Sleep Button (fixed) > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 > cpu0: on acpi0 > acpi_tz0: on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > agp0: port 0xd200-0xd203 mem = 0xefdff000-0xefdfffff,0xec000000-0xedffffff at device 0.0 on pci0 > > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pci1: at device 5.0 (no driver attached) > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port = 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 > ata0: channel #0 on atapci0 > ata1: channel #1 on atapci0 > pci0: at device 7.3 (no driver attached) > rl0: port 0xd400-0xd4ff mem = 0xefffbf00-0xefffbfff irq 11 at device 9.0 on pci0 > miibus0: on rl0 > rlphy0: on miibus0 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > rl0: Ethernet address: 00:30:ab:00:8f:49 > atapci1: port = 0xd600-0xd60f,0xd800-0xd803,0xda00-0xda07,0xdc00-0xdc03,0xde00-0xde07 = mem 0xefffc000-0xefffffff irq 10 at device 10.0 on pci0 > > ata2: channel #0 on atapci1 > device_attach: ata2 attach returned 6 > ata3: channel #1 on atapci1 > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > fdc0: port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3 irq = 6 drq 2 on acpi0 > fdc0: [FAST] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from = [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > pmtimer0 on isa0 > orm0: at iomem 0xc8000-0xcbfff,0xc0000-0xc7fff on = isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=3D0x300> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on = isa0 > ppc0: parallel port not found. > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 8250 or not responding > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > Timecounter "TSC" frequency 807958859 Hz quality 800 > Timecounters tick every 10.000 msec > ad0: 19547MB [39714/16/63] at ata0-master = UDMA66 > ad2: 114473MB [232581/16/63] at ata1-master UDMA66 > ad3: 114473MB [232581/16/63] at ata1-slave UDMA66 > Mounting root from ufs:/dev/ad0s1a > > > > Kernel Config: > > machine i386 > cpu I686_CPU > ident WWW-ALNM > > options SCHED_4BSD # 4BSD scheduler > options INET # InterNETworking > options INET6 # IPv6 communications = protocols > options FFS # Berkeley Fast Filesystem > options SOFTUPDATES # Enable FFS soft updates = support > options UFS_ACL # Support for access control = lists > options UFS_DIRHASH # Improve performance on big = directoriesoptions MD_ROOT # MD is a potential = root device > > options NFSCLIENT # Network Filesystem Client > options NFSSERVER # Network Filesystem Server > options NFS_ROOT # NFS usable as /, requires = NFSCLIENT > options MSDOSFS # MSDOS Filesystem > options CD9660 # ISO 9660 Filesystem > options PROCFS # Process filesystem (requires = PSEUDOFS)options PSEUDOFS # Pseudo-filesystem = framework > > options GEOM_GPT # GUID Partition Tables. > options COMPAT_43 # Compatible with BSD 4.3 = [KEEP THIS!] > options COMPAT_FREEBSD4 # Compatible with FreeBSD4 > options SCSI_DELAY=3D15000 # Delay (in ms) before = probing SCSI > options KTRACE # ktrace(1) support > options SYSVSHM # SYSV-style shared memory > options SYSVMSG # SYSV-style message queues > options SYSVSEM # SYSV-style semaphores > options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time = extensions > options KBD_INSTALL_CDEV # install a CDEV entry in /dev > # output. Adds ~215k to = driver. > options ADAPTIVE_GIANT # Giant mutex is adaptive. > > device apic # I/O APIC > > # Bus support. Do not remove isa, even if you have no isa slots > device isa > device eisa > device pci > > # Floppy drives > device fdc > > # ATA and ATAPI devices > device ata > device atadisk # ATA disk drives > device ataraid # ATA RAID drives > device atapicd # ATAPI CDROM drives > device atapifd # ATAPI floppy drives > #device atapist # ATAPI tape drives > options ATA_STATIC_ID # Static device numbering > > # atkbdc0 controls both the keyboard and the PS/2 mouse > device atkbdc # AT keyboard controller > device atkbd # AT keyboard > device psm # PS/2 mouse > > device vga # VGA video card driver > > #device splash # Splash screen and screen saver = support > > # syscons is the default console driver, resembling an SCO console > device sc > > device agp # support several AGP chipsets > > # Floating point support - do not disable. > device npx > > # Power management support (see NOTES for more options) > #device apm > # Add suspend/resume support for the i8254. > device pmtimer > > # Serial (COM) ports > device sio # 8250, 16[45]50 based serial ports > > # Parallel port > device ppc > device ppbus # Parallel port bus (required) > device lpt # Printer > device plip # TCP/IP over parallel > device ppi # Parallel port interface device > #device vpo # Requires scbus and da > > # PCI Ethernet NICs that use the common MII bus controller code. > # NOTE: Be sure to keep the 'device miibus' line in order to use these = NICs! > device miibus # MII bus support > device xl # 3Com 3c90x (``Boomerang'', = ``Cyclone'') > > # Pseudo devices. > device loop # Network loopback > device mem # Memory and kernel memory devices > device io # I/O device > device random # Entropy device > device ether # Ethernet support > device sl # Kernel SLIP > device ppp # Kernel PPP > device tun # Packet tunnel. > device pty # Pseudo-ttys (telnet etc) > device md # Memory "disks" > device gif # IPv6 and IPv4 tunneling > device faith # IPv6-to-IPv4 relaying (translation) > > device ccd =20 > > Thank you! > > -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- > Greg Smythe > Senior Technician > > > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to = "freebsd-hardware-unsubscribe@freebsd.org" > > !DSPAM:41efb17c20713480789068! > > -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ > finger -l haischt@daniel.stefan.haischt.name From owner-freebsd-hardware@FreeBSD.ORG Thu Jan 20 13:59:13 2005 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 0AB9116A4CE for ; Thu, 20 Jan 2005 13:59:13 +0000 (GMT) Received: from mail.terralink.de (mail.tlink.de [217.9.16.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 247F543D4C for ; Thu, 20 Jan 2005 13:59:12 +0000 (GMT) (envelope-from me@daniel.stefan.haischt.name) Received: from smtp.abyssworld.de (daniel-s-haischt.biz [84.252.66.2]) by mail.terralink.de (Postfix) with ESMTP id 3BA7CBD7B8; Thu, 20 Jan 2005 14:59:09 +0100 (CET) Received: from abyssone.abyssworld.de (smtp.abyssworld.de [192.168.1.6]) by smtp.abyssworld.de (Postfix) with SMTP id B01DC190FC; Thu, 20 Jan 2005 14:59:08 +0100 (CET) Received: from (localhost) [192.168.1.6] by abyssone.abyssworld.de with smtp (geam 0.8.4) for ; Thu, 20 Jan 2005 14:59:08 +0100 Received: from smtp.abyssworld.de ([127.0.0.1])port 10024) with ESMTP id 02549-02; Thu, 20 Jan 2005 14:59:08 +0100 (CET) Received-SPF: none (smtp.abyssworld.de: 192.168.1.6 is neither permitted nor denied by domain of daniel.stefan.haischt.name) client-ip=192.168.1.6; envelope-from=me@daniel.stefan.haischt.name; helo=[192.168.120.239]; Received: from [192.168.120.239] (smtp.abyssworld.de [192.168.1.6]) by smtp.abyssworld.de (Postfix) with ESMTP id 40D1E190FA; Thu, 20 Jan 2005 14:59:08 +0100 (CET) Message-ID: <41EFB92A.1070703@daniel.stefan.haischt.name> Date: Thu, 20 Jan 2005 14:59:06 +0100 From: "Daniel S. Haischt" User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Greg Smythe References: <59B6D51629A7D94DB850D903FAF46B3901234C@mario.home.local> In-Reply-To: <59B6D51629A7D94DB850D903FAF46B3901234C@mario.home.local> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Processed-By: GNU Anubis v4.0 X-Virus-Scanned: amavisd-new at abyssworld.de cc: freebsd-hardware@freebsd.org Subject: Re: Promise PDC20269 UDMA133 controller -- Hard drives not showing up X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: me@daniel.stefan.haischt.name List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 13:59:13 -0000 BTW - Do you use both channels of the Promise controller? Greg Smythe schrieb: > I just had a brainstorm and tried the controller in another (clean installed) FBSD 5.3 box and it worked fine. So I am going to rebuild the box that I'm having a problem with (it was a binary upgrade from 4.9). > > I'll post back with my results. > > Thanks for the response! > > > > Greg > > ________________________________ > > From: Daniel S. Haischt [mailto:me@stefan.haischt.name] > Sent: Thu 1/20/2005 8:51 AM > To: Greg Smythe > Cc: freebsd-hardware@freebsd.org > Subject: Re: Promise PDC20269 UDMA133 controller -- Hard drives not showing up > > > > Did you try to disable ACPI (just to get rid of the > error messages)? > > You might also hava a look at the following page > > -> http://tinyurl.com/3rywq > > Search for the subject line 'Interrupt storm on FreeBSD 5.3'. > It does not help to solve your problem, but it may be that > there is a problem with the PDC20269 UDMA133 controller, > at least in FreeBSD 5.3 because I did use this controller > without any problems together with FreeBSD 5.2.1. > > Greg Smythe schrieb: > >> >> >>Hello -- >> >>I installed 5.3, CVSUP'd stable and ports. I am unable to see the hard drives on this controller with either the GENERIC kernel or my custom one. I am also getting errors on kernel start up that I can't find referenced anywhere. Anyone have any ideas? >> >>Thank you! >> >>dmesg: >>Copyright (c) 1992-2005 The FreeBSD Project. >>Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 >> The Regents of the University of California. All rights reserved. >>FreeBSD 5.3-STABLE #2: Tue Jan 18 16:00:26 EST 2005 >> root@www-alnm.tkcinc.com:/usr/obj/usr/src/sys/WWW-ALNM >>Timecounter "i8254" frequency 1193182 Hz quality 0 >>CPU: AMD Athlon(tm) Processor (807.96-MHz 686-class CPU) >> Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 >> Features=0x183f9ff >> AMD Features=0xc0440000 >>real memory = 805240832 (767 MB) >>avail memory = 782426112 (746 MB) >>npx0: [FAST] >>npx0: on motherboard >>npx0: INT 16 interface >>acpi0: on motherboard >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >>acpi0: Power Button (fixed) >>acpi0: Sleep Button (fixed) >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >>Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 >>acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 >>cpu0: on acpi0 >>acpi_tz0: on acpi0 >>acpi_button0: on acpi0 >>pcib0: port 0xcf8-0xcff on acpi0 >>pci0: on pcib0 >>agp0: port 0xd200-0xd203 mem 0xefdff000-0xefdfffff,0xec000000-0xedffffff at device 0.0 on pci0 >> >>pcib1: at device 1.0 on pci0 >>pci1: on pcib1 >>pci1: at device 5.0 (no driver attached) >>isab0: at device 7.0 on pci0 >>isa0: on isab0 >>atapci0: port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 >>ata0: channel #0 on atapci0 >>ata1: channel #1 on atapci0 >>pci0: at device 7.3 (no driver attached) >>rl0: port 0xd400-0xd4ff mem 0xefffbf00-0xefffbfff irq 11 at device 9.0 on pci0 >>miibus0: on rl0 >>rlphy0: on miibus0 >>rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >>rl0: Ethernet address: 00:30:ab:00:8f:49 >>atapci1: port 0xd600-0xd60f,0xd800-0xd803,0xda00-0xda07,0xdc00-0xdc03,0xde00-0xde07 mem 0xefffc000-0xefffffff irq 10 at device 10.0 on pci0 >> >>ata2: channel #0 on atapci1 >>device_attach: ata2 attach returned 6 >>ata3: channel #1 on atapci1 >>atkbdc0: port 0x64,0x60 irq 1 on acpi0 >>atkbd0: irq 1 on atkbdc0 >>kbd0 at atkbd0 >>atkbd0: [GIANT-LOCKED] >>fdc0: port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3 irq 6 drq 2 on acpi0 >>fdc0: [FAST] >>fd0: <1440-KB 3.5" drive> on fdc0 drive 0 >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >> ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST >>pmtimer0 on isa0 >>orm0: at iomem 0xc8000-0xcbfff,0xc0000-0xc7fff on isa0 >>sc0: at flags 0x100 on isa0 >>sc0: VGA <16 virtual consoles, flags=0x300> >>vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 >>ppc0: parallel port not found. >>sio0: configured irq 4 not in bitmap of probed irqs 0 >>sio0: port may not be enabled >>sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 >>sio0: type 8250 or not responding >>sio1: configured irq 3 not in bitmap of probed irqs 0 >>sio1: port may not be enabled >>Timecounter "TSC" frequency 807958859 Hz quality 800 >>Timecounters tick every 10.000 msec >>ad0: 19547MB [39714/16/63] at ata0-master UDMA66 >>ad2: 114473MB [232581/16/63] at ata1-master UDMA66 >>ad3: 114473MB [232581/16/63] at ata1-slave UDMA66 >>Mounting root from ufs:/dev/ad0s1a >> >> >> >>Kernel Config: >> >>machine i386 >>cpu I686_CPU >>ident WWW-ALNM >> >>options SCHED_4BSD # 4BSD scheduler >>options INET # InterNETworking >>options INET6 # IPv6 communications protocols >>options FFS # Berkeley Fast Filesystem >>options SOFTUPDATES # Enable FFS soft updates support >>options UFS_ACL # Support for access control lists >>options UFS_DIRHASH # Improve performance on big directoriesoptions MD_ROOT # MD is a potential root device >> >>options NFSCLIENT # Network Filesystem Client >>options NFSSERVER # Network Filesystem Server >>options NFS_ROOT # NFS usable as /, requires NFSCLIENT >>options MSDOSFS # MSDOS Filesystem >>options CD9660 # ISO 9660 Filesystem >>options PROCFS # Process filesystem (requires PSEUDOFS)options PSEUDOFS # Pseudo-filesystem framework >> >>options GEOM_GPT # GUID Partition Tables. >>options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] >>options COMPAT_FREEBSD4 # Compatible with FreeBSD4 >>options SCSI_DELAY=15000 # Delay (in ms) before probing SCSI >>options KTRACE # ktrace(1) support >>options SYSVSHM # SYSV-style shared memory >>options SYSVMSG # SYSV-style message queues >>options SYSVSEM # SYSV-style semaphores >>options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions >>options KBD_INSTALL_CDEV # install a CDEV entry in /dev >> # output. Adds ~215k to driver. >>options ADAPTIVE_GIANT # Giant mutex is adaptive. >> >>device apic # I/O APIC >> >># Bus support. Do not remove isa, even if you have no isa slots >>device isa >>device eisa >>device pci >> >># Floppy drives >>device fdc >> >># ATA and ATAPI devices >>device ata >>device atadisk # ATA disk drives >>device ataraid # ATA RAID drives >>device atapicd # ATAPI CDROM drives >>device atapifd # ATAPI floppy drives >>#device atapist # ATAPI tape drives >>options ATA_STATIC_ID # Static device numbering >> >># atkbdc0 controls both the keyboard and the PS/2 mouse >>device atkbdc # AT keyboard controller >>device atkbd # AT keyboard >>device psm # PS/2 mouse >> >>device vga # VGA video card driver >> >>#device splash # Splash screen and screen saver support >> >># syscons is the default console driver, resembling an SCO console >>device sc >> >>device agp # support several AGP chipsets >> >># Floating point support - do not disable. >>device npx >> >># Power management support (see NOTES for more options) >>#device apm >># Add suspend/resume support for the i8254. >>device pmtimer >> >># Serial (COM) ports >>device sio # 8250, 16[45]50 based serial ports >> >># Parallel port >>device ppc >>device ppbus # Parallel port bus (required) >>device lpt # Printer >>device plip # TCP/IP over parallel >>device ppi # Parallel port interface device >>#device vpo # Requires scbus and da >> >># PCI Ethernet NICs that use the common MII bus controller code. >># NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! >>device miibus # MII bus support >>device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') >> >># Pseudo devices. >>device loop # Network loopback >>device mem # Memory and kernel memory devices >>device io # I/O device >>device random # Entropy device >>device ether # Ethernet support >>device sl # Kernel SLIP >>device ppp # Kernel PPP >>device tun # Packet tunnel. >>device pty # Pseudo-ttys (telnet etc) >>device md # Memory "disks" >>device gif # IPv6 and IPv4 tunneling >>device faith # IPv6-to-IPv4 relaying (translation) >> >>device ccd >> >>Thank you! >> >>-=-=-=-=-=-=-=-=-=-=-=- >>Greg Smythe >>Senior Technician >> >> >> >> >>_______________________________________________ >>freebsd-hardware@freebsd.org mailing list >>http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >>To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" >> >> >> >> > > > -- > Mit freundlichen Gruessen / With kind regards > DAn.I.El S. Haischt > > Want a complete signature??? Type at a shell prompt: > $ > finger -l haischt@daniel.stefan.haischt.name > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > > !DSPAM:41efb81c24644141223431! > > -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ > finger -l haischt@daniel.stefan.haischt.name From owner-freebsd-hardware@FreeBSD.ORG Thu Jan 20 15:29:42 2005 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 21DA016A4CE for ; Thu, 20 Jan 2005 15:29:42 +0000 (GMT) Received: from mail.eecs.harvard.edu (bowser.eecs.harvard.edu [140.247.60.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2ECA43D31 for ; Thu, 20 Jan 2005 15:29:41 +0000 (GMT) (envelope-from ellard@eecs.harvard.edu) Received: from localhost (localhost.eecs.harvard.edu [127.0.0.1]) by mail.eecs.harvard.edu (Postfix) with ESMTP id E05BC54C849 for ; Thu, 20 Jan 2005 10:29:40 -0500 (EST) Received: from mail.eecs.harvard.edu ([127.0.0.1]) by localhost (bowser.eecs.harvard.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 70760-01 for ; Thu, 20 Jan 2005 10:29:40 -0500 (EST) Received: by mail.eecs.harvard.edu (Postfix, from userid 465) id B51E354C803; Thu, 20 Jan 2005 10:29:40 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by mail.eecs.harvard.edu (Postfix) with ESMTP id B2A8154C533 for ; Thu, 20 Jan 2005 10:29:40 -0500 (EST) Date: Thu, 20 Jan 2005 10:29:40 -0500 (EST) From: Daniel Ellard To: hardware@freebsd.org Message-ID: <20050120102730.T70307@bowser.eecs.harvard.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at eecs.harvard.edu Subject: anyone running FreeBSD on a Sun B200x blade? 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: Thu, 20 Jan 2005 15:29:42 -0000 Has anyone successfully installed FreeBSD 4.x or 5.x on a SUN B200x blade (the dual-Xeon blade that fits in a B1600 chassis)? If so, please let me know, and whether there were any major stumbling blocks along the way. Thanks, -Dan From owner-freebsd-hardware@FreeBSD.ORG Thu Jan 20 23:44:04 2005 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 7EEB416A4CE for ; Thu, 20 Jan 2005 23:44:04 +0000 (GMT) Received: from mx1.freebsdsystems.com (mx1.FreeBSDsystems.COM [69.90.68.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDA2743D1D for ; Thu, 20 Jan 2005 23:44:01 +0000 (GMT) (envelope-from lnb@freebsdsystems.com) Received: (qmail 54320 invoked by uid 89); 20 Jan 2005 23:43:59 -0000 Received: by simscan 1.0.8 ppid: 54307, pid: 54310, t: 5.5784s scanners: attach: 1.0.8 clamav: 0.80rc4/m:28/d:644 spam: 3.0.0 Received: from unknown (HELO ?192.168.0.5?) (lnb@216.235.9.82) by mx1.freebsdsystems.com with (DHE-RSA-AES256-SHA encrypted) SMTP; 20 Jan 2005 23:43:53 -0000 Message-ID: <41F04237.2050204@freebsdsystems.com> Date: Thu, 20 Jan 2005 18:43:51 -0500 From: Lanny Baron Organization: FreeBSD Systems User-Agent: Mozilla Thunderbird 0.9 (X11/20041124) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andreas Klemm References: <20050118112900.GA14342@titan.klemm.apsfilter.org> In-Reply-To: <20050118112900.GA14342@titan.klemm.apsfilter.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on mx1.freebsdsystems.com X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,COMPLETELY_FREE autolearn=ham version=3.0.0 cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD 5.3 SATA / RAID1 questions for migration from ATA 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: Thu, 20 Jan 2005 23:44:04 -0000 Hi, If you are speaking of Host-RAID that is, on-board RAID, it does not yet work. FreeBSD does not yet support it. Regards, =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= Lanny Baron Proud to be 100% FreeBSD http://www.FreeBSDsystems.COM Toll Free: 1.877.963.1900 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+= Andreas Klemm wrote: > Hi, > > I bought a new socket 939 MSI mainboard > (amd64, MSI K8N NEO2 Platinum, S.939 NVIDIA Nforce3 Ultra) > and am planning now how I could best make use of it and > its BIOS mirroring capabilities. > > In an ideal world I would dream of > - creating a BIOS based mirror on 2 new SATA drives > - then install XP and FreeBSD on these bios based mirrord disks. > - finally move old data to new mirrored disks and thats it. > > After reading the mailinglists I have the feeling that > - BIOS created mirrors are not useable for a FreeBSD 5.3 installation. > But I also read > - that its possible to create a mirror once you have a FreeBSD installed. > > Does this mean, that the BIOS based mirror as well as the > FreeBSD based mirror solution are partition based ? > Or is it mixed, that the BIOS based solution mirrors per > disk and the FreeBSD one per partition ? > > Other questions involved: how well does Serial ATA in 5.3 ? > > Currently I see the following scenario. > > a) Buy 2 SATA disks, create BIOS mirror, install XP > move data from ATA disks to new SATA disks > > b) keep the old ATA disks for FreeBSD only and dont mirror them > from BIOS. > Optionally mirror them from within FreeBSD. > Installation would be done newly on one disk, then a magic > ata command tells to do a mirror with 2nd disk or related. > > Does somebody make some experiences with scenarios like this > so that I could ask questions or ideally could do a > phonecall in english or german ? > > Thanks a lot for helping me > > Andreas /// > From owner-freebsd-hardware@FreeBSD.ORG Fri Jan 21 12:00:38 2005 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 26E5D16A4D1 for ; Fri, 21 Jan 2005 12:00:38 +0000 (GMT) Received: from main.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 776BF43D45 for ; Fri, 21 Jan 2005 12:00:37 +0000 (GMT) (envelope-from freebsd-hardware@m.gmane.org) Received: from root by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1CrxSu-0001Yn-00 for ; Fri, 21 Jan 2005 13:00:36 +0100 Received: from 49.64.142.82.ip.b26.cz ([82.142.64.49]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 21 Jan 2005 13:00:36 +0100 Received: from bati by 49.64.142.82.ip.b26.cz with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 21 Jan 2005 13:00:36 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hardware@freebsd.org From: Jiri Novak Date: Fri, 21 Jan 2005 12:45:11 +0100 Lines: 27 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 49.64.142.82.ip.b26.cz User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en Sender: news Subject: Server motherboard question 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: Fri, 21 Jan 2005 12:00:38 -0000 Hello, I have been assigned a task of choosing motherboard for our "next generation" server, and I need a little advice. After a week of surfing through hw compatibility list and mobo manufacturers websites I have came to conclusion that I don't know enough of current PC hardware :) This is what is required: CPU - AMD(64?) maybe dual Disk subsystem - SATA, HW RAID would be nice (0 is sufficient, 0+1 would be better), but I can easily replace that with (g)vinum Network adapter - definitely gigabit ethernet, dual would be nice Memory - about 2-4Gigs of RAM Can anybody recommend a motherboard which will not have any problems with FreeBSD 5.3 and have those outlined features? I came with some boards from MSI (MSI K8D Master3-133 and MSI K8N Neo4-Platinum), which have what I need, but I'm sceptical about chipset support in FreeBSD, anybody usess them? I generally also like Tyan motherboards (f.ex. Thunder K7X Pro, Tiger K8W(S)...), again, anybody using these boards with FreeBSD? I would like to make up about 4-5 solutions from single Athlon to dual Opteron and let our management choose the right one price-wise :) TIA! -- Jiri Novak From owner-freebsd-hardware@FreeBSD.ORG Fri Jan 21 17:24:35 2005 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 6DFC316A4CE for ; Fri, 21 Jan 2005 17:24:35 +0000 (GMT) Received: from direct.akers-online.co.uk (cpc1-nwrk1-5-0-cust1.nott.cable.ntl.com [81.111.104.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E80743D31 for ; Fri, 21 Jan 2005 17:24:34 +0000 (GMT) (envelope-from freebsd-hardware@akers-online.co.uk) Received: from localhost (unknown [127.0.0.1]) by direct.akers-online.co.uk (Postfix) with ESMTP id 590EB6D465 for ; Fri, 21 Jan 2005 17:24:33 +0000 (GMT) Received: from direct.akers-online.co.uk ([127.0.0.1]) by localhost (seven.qonos.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10909-03 for ; Fri, 21 Jan 2005 17:24:30 +0000 (GMT) Received: from gowron.qonos.com (gowron.qonos.com [192.168.123.251]) by direct.akers-online.co.uk (Postfix) with ESMTP id 2D4ED6D411 for ; Fri, 21 Jan 2005 17:24:30 +0000 (GMT) To: freebsd-hardware@freebsd.org MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.2 June 01, 2004 Message-ID: From: Sean Akers Date: Fri, 21 Jan 2005 17:24:30 +0000 X-MIMETrack: Serialize by Router on gowron/Qonos(Release 6.5.2|June 01, 2004) at 21/01/2005 17:24:30, Serialize complete at 21/01/2005 17:24:30 Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: by amavisd-new at akers-online.co.uk Subject: RE: FreeBSD on shuttle ST62K (zen) 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: Fri, 21 Jan 2005 17:24:35 -0000 Patrick Proniewski wrote: > Hi, > > I want to setup a FreeBSD internet gateway between my 8Mbps DSL and my > LAN. I'm thinking about using a shuttle ST62K (ZEN), and I would like to > known how well this hardware is supported by FreeBSD (4.10 or 5.3). > specs are here: > http://global.shuttle.com/Product/barebone/brb_OverView.asp?B_id=29 > > according to FreeBSD hardware notes : (?=info not available) > --------------------------------------------5.3---4.10 > chipset: > ATI RS300 .................................. ? .. ? > ATI IXP150 ................................. ? .. ? > > Audio: > Realtek ALC650 six channel audio. .......... ? .. ? > > Ethernet: > Realtek 8100C supports 10/100 LAN .......... ? .. ? > > IEEE 1394a: > VIA VT6307 ................................. ? .. ? > 1394 OHCI v1.0 compliant ................... OK . ? > > TV-out: unknown ? > > > any help greatly appreciated. > > patpro I don't know about the ST62K (I was going to buy one of these myself but couldn't verify FreeBSD would work OK with it.). However, instead, I bought a Shuttle SB52G2 instead. It uses a standard(ish) Intel chipset and contains onboard Intel graphics card. I'm using it as a firewall/router/mail server/news cache/VPN server/file server etc. It has 2 NICs 1x1Gb and 1x100Mb. I installed FreeBSD 5.3 on it and so far it is working perfectly for the tasks I'm using it for. I haven't used it for sound, I don't use USB or Firewire, only the NICs and X. X works fine, the only trouble I had was setting it up for use with an LCD monitor. It is really quite quiet which is one of the reasons I went for a Shuttle in the first place. Anyway, it might be worth checking out. Sean. ---------------------------------------------------------------------------- "Our enemies are innovative and resourceful - and so are we. They never stop thinking about new ways to harm our country and our people - and neither do we." George W Bush Aug 2004 From owner-freebsd-hardware@FreeBSD.ORG Fri Jan 21 23:24:06 2005 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 BA60716A4CE for ; Fri, 21 Jan 2005 23:24:06 +0000 (GMT) Received: from mail.intellstat.com (adsl-69-213-82-197.dsl.sfldmi.ameritech.net [69.213.82.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A78043D48 for ; Fri, 21 Jan 2005 23:24:05 +0000 (GMT) (envelope-from gregs@intellstat.com) Date: Fri, 21 Jan 2005 18:24:20 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Message-ID: <59B6D51629A7D94DB850D903FAF46B39032E2F@mario.home.local> X-MS-Has-Attach: Content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 X-MS-TNEF-Correlator: Thread-Topic: Promise PDC20269 UDMA133 controller -- Hard drives not showingup -- RESOLVED Thread-Index: AcT+90GoS2MPiwBiSY6i1DyoGSB60gBGPtcg From: "Greg Smythe" To: Subject: RE: Promise PDC20269 UDMA133 controller -- Hard drives not showingup -- RESOLVED 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: Fri, 21 Jan 2005 23:24:06 -0000 FYI I moved the hardware and hard drive to another machine and it works fine. I guess BSD is a bit finiky :)=20 -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- Greg Smythe -----Original Message----- From: owner-freebsd-hardware@freebsd.org [mailto:owner-freebsd-hardware@freebsd.org] On Behalf Of Greg Smythe Sent: Thursday, January 20, 2005 8:52 AM To: freebsd-hardware@freebsd.org Subject: RE: Promise PDC20269 UDMA133 controller -- Hard drives not showingup I just had a brainstorm and tried the controller in another (clean installed) FBSD 5.3 box and it worked fine. So I am going to rebuild the box that I'm having a problem with (it was a binary upgrade from 4.9). =20 I'll post back with my results.=20 =20 Thanks for the response! =20 =20 =20 Greg ________________________________ From: Daniel S. Haischt [mailto:me@stefan.haischt.name] Sent: Thu 1/20/2005 8:51 AM To: Greg Smythe Cc: freebsd-hardware@freebsd.org Subject: Re: Promise PDC20269 UDMA133 controller -- Hard drives not showing up Did you try to disable ACPI (just to get rid of the error messages)? You might also hava a look at the following page -> http://tinyurl.com/3rywq Search for the subject line 'Interrupt storm on FreeBSD 5.3'. It does not help to solve your problem, but it may be that there is a problem with the PDC20269 UDMA133 controller, at least in FreeBSD 5.3 because I did use this controller without any problems together with FreeBSD 5.2.1. Greg Smythe schrieb: > =20 > > Hello -- > > I installed 5.3, CVSUP'd stable and ports. I am unable to see the hard drives on this controller with either the GENERIC kernel or my custom one. I am also getting errors on kernel start up that I can't find referenced anywhere. Anyone have any ideas? > > Thank you! > > dmesg: > Copyright (c) 1992-2005 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 5.3-STABLE #2: Tue Jan 18 16:00:26 EST 2005 > root@www-alnm.tkcinc.com:/usr/obj/usr/src/sys/WWW-ALNM > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Athlon(tm) Processor (807.96-MHz 686-class CPU) > Origin =3D "AuthenticAMD" Id =3D 0x642 Stepping =3D 2 > Features=3D0x183f9ff > AMD Features=3D0xc0440000 > real memory =3D 805240832 (767 MB) > avail memory =3D 782426112 (746 MB) > npx0: [FAST] > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > ACPI-0252: *** Error: No object was returned from=20 > [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > acpi0: Power Button (fixed) > acpi0: Sleep Button (fixed) > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from=20 > [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST=20 > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 > cpu0: on acpi0 > acpi_tz0: on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > agp0: port 0xd200-0xd203 mem=20 > 0xefdff000-0xefdfffff,0xec000000-0xedffffff at device 0.0 on pci0 > > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pci1: at device 5.0 (no driver attached) > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port=20 > 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on=20 > pci0 > ata0: channel #0 on atapci0 > ata1: channel #1 on atapci0 > pci0: at device 7.3 (no driver attached) > rl0: port 0xd400-0xd4ff mem=20 > 0xefffbf00-0xefffbfff irq 11 at device 9.0 on pci0 > miibus0: on rl0 > rlphy0: on miibus0 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > rl0: Ethernet address: 00:30:ab:00:8f:49 > atapci1: port=20 > 0xd600-0xd60f,0xd800-0xd803,0xda00-0xda07,0xdc00-0xdc03,0xde00-0xde07=20 > mem 0xefffc000-0xefffffff irq 10 at device 10.0 on pci0 > > ata2: channel #0 on atapci1 > device_attach: ata2 attach returned 6 > ata3: channel #1 on atapci1 > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > fdc0: port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3 irq > 6 drq 2 on acpi0 > fdc0: [FAST] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST > ACPI-0252: *** Error: No object was returned from=20 > [\\_SB_.PCI0.SBRG.ECP_._STA] (Node 0xc1ab7d20), AE_NOT_EXIST pmtimer0=20 > on isa0 > orm0: at iomem 0xc8000-0xcbfff,0xc0000-0xc7fff on=20 > isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=3D0x300> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on=20 > isa0 > ppc0: parallel port not found. > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 8250 or not responding > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > Timecounter "TSC" frequency 807958859 Hz quality 800 Timecounters tick > every 10.000 msec > ad0: 19547MB [39714/16/63] at ata0-master > UDMA66 > ad2: 114473MB [232581/16/63] at ata1-master UDMA66 > ad3: 114473MB [232581/16/63] at ata1-slave UDMA66=20 > Mounting root from ufs:/dev/ad0s1a > > > > Kernel Config: > > machine i386 > cpu I686_CPU > ident WWW-ALNM > > options SCHED_4BSD # 4BSD scheduler > options INET # InterNETworking > options INET6 # IPv6 communications protocols > options FFS # Berkeley Fast Filesystem > options SOFTUPDATES # Enable FFS soft updates support > options UFS_ACL # Support for access control lists > options UFS_DIRHASH # Improve performance on big directoriesoptions MD_ROOT # MD is a potential root device > > options NFSCLIENT # Network Filesystem Client > options NFSSERVER # Network Filesystem Server > options NFS_ROOT # NFS usable as /, requires NFSCLIENT > options MSDOSFS # MSDOS Filesystem > options CD9660 # ISO 9660 Filesystem > options PROCFS # Process filesystem (requires PSEUDOFS)options PSEUDOFS # Pseudo-filesystem framework > > options GEOM_GPT # GUID Partition Tables. > options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] > options COMPAT_FREEBSD4 # Compatible with FreeBSD4 > options SCSI_DELAY=3D15000 # Delay (in ms) before = probing SCSI > options KTRACE # ktrace(1) support > options SYSVSHM # SYSV-style shared memory > options SYSVMSG # SYSV-style message queues > options SYSVSEM # SYSV-style semaphores > options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions > options KBD_INSTALL_CDEV # install a CDEV entry in /dev > # output. Adds ~215k to driver. > options ADAPTIVE_GIANT # Giant mutex is adaptive. > > device apic # I/O APIC > > # Bus support. Do not remove isa, even if you have no isa slots > device isa > device eisa > device pci > > # Floppy drives > device fdc > > # ATA and ATAPI devices > device ata > device atadisk # ATA disk drives > device ataraid # ATA RAID drives > device atapicd # ATAPI CDROM drives > device atapifd # ATAPI floppy drives > #device atapist # ATAPI tape drives > options ATA_STATIC_ID # Static device numbering > > # atkbdc0 controls both the keyboard and the PS/2 mouse > device atkbdc # AT keyboard controller > device atkbd # AT keyboard > device psm # PS/2 mouse > > device vga # VGA video card driver > > #device splash # Splash screen and screen saver support > > # syscons is the default console driver, resembling an SCO console > device sc > > device agp # support several AGP chipsets > > # Floating point support - do not disable. > device npx > > # Power management support (see NOTES for more options) > #device apm > # Add suspend/resume support for the i8254. > device pmtimer > > # Serial (COM) ports > device sio # 8250, 16[45]50 based serial ports > > # Parallel port > device ppc > device ppbus # Parallel port bus (required) > device lpt # Printer > device plip # TCP/IP over parallel > device ppi # Parallel port interface device > #device vpo # Requires scbus and da > > # PCI Ethernet NICs that use the common MII bus controller code. > # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! > device miibus # MII bus support > device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') > > # Pseudo devices. > device loop # Network loopback > device mem # Memory and kernel memory devices > device io # I/O device > device random # Entropy device > device ether # Ethernet support > device sl # Kernel SLIP > device ppp # Kernel PPP > device tun # Packet tunnel. > device pty # Pseudo-ttys (telnet etc) > device md # Memory "disks" > device gif # IPv6 and IPv4 tunneling > device faith # IPv6-to-IPv4 relaying (translation) > > device ccd =20 > > Thank you! > > -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- > Greg Smythe > Senior Technician > > > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list=20 > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > > !DSPAM:41efb17c20713480789068! > > -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ > finger -l haischt@daniel.stefan.haischt.name _______________________________________________ freebsd-hardware@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" From owner-freebsd-hardware@FreeBSD.ORG Sat Jan 22 13:26:33 2005 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 EC5D716A4CE for ; Sat, 22 Jan 2005 13:26:32 +0000 (GMT) Received: from smtp2.arnet.com.ar (smtp2.arnet.com.ar [200.45.191.5]) by mx1.FreeBSD.org (Postfix) with SMTP id 9B3F643D4C for ; Sat, 22 Jan 2005 13:26:31 +0000 (GMT) (envelope-from netbsd@contenidosonline.com.ar) Received: (qmail 9013 invoked from network); 22 Jan 2005 13:26:29 -0000 Received: from unknown (HELO host26.200-43-99.telecom.net.ar) (200.43.99.26) by smtp2.arnet.com.ar with SMTP; 22 Jan 2005 13:26:28 -0000 From: Roberto Pereyra To: freebsd-hardware@freebsd.org Date: Sat, 22 Jan 2005 07:29:18 -0300 User-Agent: KMail/1.7 References: <200501191449.13646.netbsd@contenidosonline.com.ar> <20050120171850.Q33587@delplex.bde.org> In-Reply-To: <20050120171850.Q33587@delplex.bde.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501220729.18577.netbsd@contenidosonline.com.ar> Subject: Re: kernel: sioxx: silo overflow with 8 ports pci MOXA cards 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: Sat, 22 Jan 2005 13:26:33 -0000 Thanks Bruce !! Another question: I have another server with a 2 port I must use PUC_FASTINTR and COM_MULTIPORT options with it ? I enable in the kernel the PUC_FASTINTR options but this dmesg continues: My dmesg is: sio4: on puc0 sio4: type 16550A sio4: unable to activate interrupt in fast mode - using normal mode sio5: on puc0 sio5: type 16550A sio5: unable to activate interrupt in fast mode - using normal mode sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A Thanks again roberto On Thursday 20 January 2005 03:33, Bruce Evans wrote: > On Wed, 19 Jan 2005, Roberto Pereyra wrote: > > I have a 8 port pci Moxa C168U/PCI and use it like ppp server (with > > mgetty and radius support). > > > > The server not works well because I have many "sio overflow" errors. The > > modem drop the link or when the link is active (some minutes later) the > > link don't send packets and drop. > > Large numbers of ports might cause this problem under versions of FreeBSD > newer than FreeBSD-4, due to poor interrupt latency in these versions. > However, "large" is hopefully more than 8. > > > Many times the modems not answer the call. > > > > Can anybody help me ? (excuse my english) > > > > My system is Freebsd 5.2 RELEASE > > > > My kernel is GENERIC plus this: > > > > # Serial (COM) ports > > device sio # 8250, 16[45]50 based serial ports > > options COM_MULTIPORT > > device puc > > COM_MULTIPORT is not needed for puc devices. Using it when it is not > needed (for other devices) just increases interrupt latency and reduces > efficiency. (The driver doesn't handle mixtures of devices (with only some > devices needing it) very well.) > > > My dmesg show: > > > > ioapic0 irqs 0-23 on motherboard > > pcibios: BIOS version 2.10 > > usb0: USB revision 1.0 > > usb1: USB revision 1.0 > > usb2: USB revision 1.0 > > sio4: on puc0 > > sio4: type 16550A > > sio4: unable to activate interrupt in fast mode - using normal mode > > sio5: on puc0 > > sio5: type 16550A > > sio5: unable to activate interrupt in fast mode - using normal mode > > sio6: on puc0 > > sio6: type 16550A > > sio6: unable to activate interrupt in fast mode - using normal mode > > sio7: on puc0 > > sio7: type 16550A > > sio7: unable to activate interrupt in fast mode - using normal mode > > sio8: on puc0 > > sio8: type 16550A > > sio8: unable to activate interrupt in fast mode - using normal mode > > sio9: on puc0 > > sio9: type 16550A > > sio9: unable to activate interrupt in fast mode - using normal mode > > sio10: on puc0 > > sio10: type 16550A > > sio10: unable to activate interrupt in fast mode - using normal mode > > sio11: on puc0 > > sio11: type 16550A > > sio11: unable to activate interrupt in fast mode - using normal mode > > sio0 port 0x3f8-0x3ff irq 4 on acpi0 > > sio0: type 16550A > > sio1 port 0x2f8-0x2ff irq 3 on acpi0 > > sio1: type 16550A > > Try using PUC_FASTINTR to reduce interrupt latency. This may require > juggling irqs so that the puc interrupt is not shared (hopefully not > since apic mode is used). This is not the default because if the > interrupt ends up shared then it may do more than just fail to activate > the interrupt in fast mode as above -- it may break other devices that > want the interrupt in normal mode, depending on whether it is activated > in fast mode first. > > Bryce > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" From owner-freebsd-hardware@FreeBSD.ORG Sat Jan 22 14:52:09 2005 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 EF29D16A4CE for ; Sat, 22 Jan 2005 14:52:09 +0000 (GMT) Received: from ns.yar.post.ru (ns.yar.post.ru [213.187.102.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3002143D31 for ; Sat, 22 Jan 2005 14:52:09 +0000 (GMT) (envelope-from liettneff@bk.ru) Received: from gate-corbina.km.vibrators.ru (km.yar.post.ru [213.187.105.186]) by ns.yar.post.ru (8.12.9p2/8.12.9) with ESMTP id j0MEq5ql050342 for ; Sat, 22 Jan 2005 17:52:06 +0300 (MSK) (envelope-from liettneff@bk.ru) Received: from [192.168.1.100] (reaper [192.168.1.100] (may be forged)) j0MEpxgU083677 for ; Sat, 22 Jan 2005 17:52:00 +0300 (MSK) (envelope-from liettneff@bk.ru) Date: Sat, 22 Jan 2005 17:52:00 +0300 From: Michael Lednev X-Mailer: The Bat! (v3.0.1.33) Professional Organization: none X-Priority: 3 (Normal) Message-ID: <55830518.20050122175200@bk.ru> To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: sata controllers X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: liettneff List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 14:52:10 -0000 Hello, freebsd-hardware. i'm going to buy new sata-controller for my freebsd box and don't know what to choose. as i seen in stable src there is support for silicon image, promise and via chipsets (i believe others are integrated in south bridges). what should i take to have no headache about my disks? ps: once i had experience with sii3112 based sata and it showed dma timeouts, have anything changed since august in ata driver about them? -- Best regards, Michael mailto:liettneff@bk.ru From owner-freebsd-hardware@FreeBSD.ORG Sat Jan 22 17:21:50 2005 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 2E6AF16A4CE for ; Sat, 22 Jan 2005 17:21:50 +0000 (GMT) Received: from mail.vslash.com (gambetta-2-82-67-185-6.fbx.proxad.net [82.67.185.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73E6743D45 for ; Sat, 22 Jan 2005 17:21:49 +0000 (GMT) (envelope-from valery@vslash.com) Received: from [192.168.0.22] (oxe [192.168.0.22]) by mail.vslash.com (Postfix) with ESMTP id 8D0BB1DA2C for ; Sat, 22 Jan 2005 18:25:44 +0100 (CET) Message-ID: <41F28B92.4070109@vslash.com> Date: Sat, 22 Jan 2005 18:21:22 +0100 From: =?ISO-8859-1?Q?Val=E9ry?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: ATI IXP150/AC97 Chipset not supported 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: Sat, 22 Jan 2005 17:21:50 -0000 Hi, is there a way to activate the AC97 embeded sound system designed in the ATI IXP150 Chipset ? What it is ? This chip is best know as Soundmax, Avance logic & some other name, and is mounted on a very large amount of Asus mother-board. There's no solution on the web, and snd_pcm doesn't work. And, just for fun, is there a way to port the Linux Alsa drivers solution on FBSD ? I know that these ones run under GPL licence, and i know that this question is very common and already exist, but it's a shame to see that there's no response for it ...! Thanks for your help, -- v/ From owner-freebsd-hardware@FreeBSD.ORG Sat Jan 22 19:43:13 2005 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 8F1F716A4CE for ; Sat, 22 Jan 2005 19:43:13 +0000 (GMT) Received: from drizzle.sasknow.net (drizzle.sasknow.net [204.83.220.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18A1243D1D for ; Sat, 22 Jan 2005 19:43:13 +0000 (GMT) (envelope-from ryan@sasknow.com) Received: from hsdbsk64-110-219-74.sasknet.sk.ca (hsdbsk64-110-219-74.sasknet.sk.ca [64.110.219.74]) by drizzle.sasknow.net (8.12.11/8.12.9) with ESMTP id j0MJhAp4013117 for ; Sat, 22 Jan 2005 13:43:10 -0600 (CST) (envelope-from ryan@sasknow.com) Date: Sat, 22 Jan 2005 13:43:10 -0600 (CST) From: Ryan Thompson To: freebsd-hardware@freebsd.org Message-ID: <20050122005608.H807@coyote.ry.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Virus-Status: Clean, ClamAV version devel-20041222, clamav-milter version 0.80aa on drizzle.sasknow.net X-Spam-Status: No, hits=-8.231 required=7 tests=MSGID_PINE=-2.1 HELO_DYNAMIC_IPADDR=4.4,BAYES_00=-4.9,RCVD_IN_SORBS_DUL=2.0 RCVD_IN_DSBL=3.8,RCVD_IN_NJABL_DUL=0.1 BAYES_LOW_AND_TZ_NEAR=-7.0,TIME_13_17_BAYES_LOW=-6.0,AWL=1.5 autolearn=ham version=3.000001- Subject: ASUS TV FM 7135 (Philips 7135) card supported by bktr(4)? 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: Sat, 22 Jan 2005 19:43:13 -0000 Hi all, I'm toying with a known-good ASUS TV FM 7135 card, which is using the Philips 7135 chipset (according to their web site, and the stamped chip on the board). Just for kicks, I've added the following to my kernel: device bktr device iicbus device iicbb device smbus device iic device ic device iicsmb device smb options BROOKTREE_SYSTEM_DEFAULT=BROOKTREE_NTSC Unfortunately, even though I've verified these devices are present in my kernel, none of them are probed (or appear in /dev). I'm running RELENG_5 from today on the machine in question. I originally tried this on RELENG_5 from a few weeks ago (before some wide-scale integer type changes were MFC'd in the sys/dev/bktr/ source). It shows up in the POST PCI device list as follows: Bus ID. Device ID. Func No. Vendor ID Device ID Device Type IRQ ------- ---------- -------- --------- --------- ------------------- --- 2 2 0 1131 7133 Multimedia Device 6 Nothing else shares IRQ6. Does anyone know how easily this card could be supported? The specific card is not listed in the "Known to work" section of bktr(4), but several Philips chipsets do appear to be supported, which, admittedly, could be nothing like this one. If not, I'll gladly accept recommendations for readily available TV tuner cards that work in FreeBSD. Thanks, - Ryan -- Ryan Thompson SaskNow Technologies - http://www.sasknow.com 901-1st Avenue North - Saskatoon, SK - S7K 1Y4 Tel: 306-664-3600 Fax: 306-244-7037 Saskatoon Toll-Free: 877-727-5669 (877-SASKNOW) North America From owner-freebsd-hardware@FreeBSD.ORG Sat Jan 22 20:42:05 2005 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 8B1C116A4CE for ; Sat, 22 Jan 2005 20:42:05 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46F6243D1D for ; Sat, 22 Jan 2005 20:42:05 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j0MKgLEo011269; Sat, 22 Jan 2005 12:42:21 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j0MKgLfP011268; Sat, 22 Jan 2005 12:42:21 -0800 Date: Sat, 22 Jan 2005 12:42:21 -0800 From: Brooks Davis To: Michael Lednev Message-ID: <20050122204221.GC4466@odin.ac.hmc.edu> References: <55830518.20050122175200@bk.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WplhKdTI2c8ulnbP" Content-Disposition: inline In-Reply-To: <55830518.20050122175200@bk.ru> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-hardware@freebsd.org Subject: Re: sata controllers 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: Sat, 22 Jan 2005 20:42:05 -0000 --WplhKdTI2c8ulnbP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 22, 2005 at 05:52:00PM +0300, Michael Lednev wrote: > Hello, freebsd-hardware. >=20 > i'm going to buy new sata-controller for my freebsd box and don't know > what to choose. as i seen in stable src there is support for silicon > image, promise and via chipsets (i believe others are integrated in > south bridges). what should i take to have no headache about my disks? >=20 > ps: once i had experience with sii3112 based sata and it showed dma > timeouts, have anything changed since august in ata driver about > them? The author of that ata driver reports good results with the promise chips. The 3112 remains a piece of junk. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --WplhKdTI2c8ulnbP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFB8rqtXY6L6fI4GtQRAh+sAJ995X5ArHOGaYcmLajhwK+zEpDfvwCgrO99 FQwPdea19u0Zy43BVaLWD74= =aWgW -----END PGP SIGNATURE----- --WplhKdTI2c8ulnbP-- From owner-freebsd-hardware@FreeBSD.ORG Sat Jan 22 21:19:21 2005 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 0F95B16A4CE for ; Sat, 22 Jan 2005 21:19:21 +0000 (GMT) Received: from beth.linkline.com (beth.linkline.com [64.30.215.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 922AF43D55 for ; Sat, 22 Jan 2005 21:19:20 +0000 (GMT) (envelope-from sclements@beth.linkline.com) Received: (qmail 48140 invoked by uid 1009); 22 Jan 2005 21:18:19 -0000 Message-ID: <20050122211819.48139.qmail@beth.linkline.com> References: <55830518.20050122175200@bk.ru> <20050122204221.GC4466@odin.ac.hmc.edu> In-Reply-To: <20050122204221.GC4466@odin.ac.hmc.edu> From: sclements@linkline.com Date: Sat, 22 Jan 2005 21:18:19 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1" Content-Transfer-Encoding: 7bit cc: Michael Lednev cc: freebsd-hardware@freebsd.org Subject: Re: sata controllers 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: Sat, 22 Jan 2005 21:19:21 -0000 Brooks Davis writes: > On Sat, Jan 22, 2005 at 05:52:00PM +0300, Michael Lednev wrote: >> Hello, freebsd-hardware. >> >> i'm going to buy new sata-controller for my freebsd box and don't know >> what to choose. as i seen in stable src there is support for silicon >> image, promise and via chipsets (i believe others are integrated in >> south bridges). what should i take to have no headache about my disks? >> >> ps: once i had experience with sii3112 based sata and it showed dma >> timeouts, have anything changed since august in ata driver about >> them? > > The author of that ata driver reports good results with the promise > chips. The 3112 remains a piece of junk. > > -- Brooks Also, The ICH5, 6300ESB, etc. SATA ports work very well. These tend to be integrated in all new Intel based boards. As long as you stay away from RAID mode and the Sil cards, you should be good to go! -Sam From owner-freebsd-hardware@FreeBSD.ORG Sat Jan 22 22:57:07 2005 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 41DFE16A4CE for ; Sat, 22 Jan 2005 22:57:07 +0000 (GMT) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FBF243D1D for ; Sat, 22 Jan 2005 22:57:06 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86])j0MMupA6026137; Sun, 23 Jan 2005 09:56:51 +1100 Received: from epsplex.bde.org (katana.zip.com.au [61.8.7.246]) j0MMumVU009935; Sun, 23 Jan 2005 09:56:50 +1100 Date: Sun, 23 Jan 2005 09:56:49 +1100 (EST) From: Bruce Evans X-X-Sender: bde@epsplex.bde.org To: Roberto Pereyra In-Reply-To: <200501220729.18577.netbsd@contenidosonline.com.ar> Message-ID: <20050123093746.V1118@epsplex.bde.org> References: <200501191449.13646.netbsd@contenidosonline.com.ar> <200501220729.18577.netbsd@contenidosonline.com.ar> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hardware@freebsd.org Subject: Re: kernel: sioxx: silo overflow with 8 ports pci MOXA cards 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: Sat, 22 Jan 2005 22:57:07 -0000 On Sat, 22 Jan 2005, Roberto Pereyra wrote: > Another question: > > I have another server with a 2 port > > I must use PUC_FASTINTR and COM_MULTIPORT options with it ? No. Using COM_MULTIPORT is an error unless you have an old isa multiport card or possibly a pci card not supported by puc. > I enable in the kernel the PUC_FASTINTR options but this dmesg continues: > > My dmesg is: > > sio4: on puc0 > sio4: type 16550A > sio4: unable to activate interrupt in fast mode - using normal mode > sio5: on puc0 > sio5: type 16550A > sio5: unable to activate interrupt in fast mode - using normal mode This means that PUC_FASTINTR didn't work. The interrupt for the puc device must not be shared for it to work. This can sometimes be arranged by moving pci cards to different slots. Without ACPI, there are typically 3-way possible sharings, with the irq for each slot shared with that of another slot and with 1 non-slot device or the AGP slot. The video interrupt is not used by FreeBSD so sharing with it doesn't matter and the best way to start moving pci cards is to put one that you want to have a non-shared interrupt in the slot that shares its interrupt with the AGP card. Then avoid using the other slot that shars the interrupt. With ACPI, the ACPI BIOS should allocate interrupts more sparsely and less juggling may work. > sio0 port 0x3f8-0x3ff irq 4 on acpi0 > sio0: type 16550A > sio1 port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A I hope you didn't lose the other 6 devices on the puc card. Bruce