From owner-freebsd-hardware Thu Apr 20 12:11:23 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from assurance.rstcorp.com (rstcorp2.daf.concentric.net [216.112.242.2]) by hub.freebsd.org (Postfix) with ESMTP id 7701A37B6AC for ; Thu, 20 Apr 2000 12:11:15 -0700 (PDT) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.9.3/8.9.3) id JAA26242; Thu, 20 Apr 2000 09:38:20 -0400 Received: from sandbox.rstcorp.com(10.1.30.2) by assurance.rstcorp.com via smap (V2.0) id xma026229; Thu, 20 Apr 00 13:37:29 GMT Received: from jabberwock.rstcorp.com (jabberwock.rstcorp.com [10.1.100.5]) by sandbox.rstcorp.com (8.9.3/8.9.3) with ESMTP id KAA19217; Thu, 20 Apr 2000 10:28:16 -0400 (EDT) Received: by jabberwock.rstcorp.com (Postfix, from userid 93) id A6A305B1C; Thu, 20 Apr 2000 10:34:53 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14591.5517.454232.897127@jabberwock.rstcorp.com> Date: Thu, 20 Apr 2000 10:34:53 -0400 (EDT) From: "Viren R.Shah" To: "Matthew N. Dodd" Cc: Jonathan Lemon , Ian Cartwright , freebsd-hardware@freebsd.org Subject: ida driver (Re: cvs commit: src/sys/dev/ida ida_eisa.c) In-Reply-To: References: <14584.47894.130306.880624@jabberwock.rstcorp.com> X-Mailer: VM 6.72 under 19.16 "Lille" XEmacs Lucid Reply-To: viren@rstcorp.com X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just a report on the ida driver: I installed a recent (0418) -current SNAP on my Compaq ProLiant box, and it worked just fine, except for 2 issues: 1. I did what I usually do, and customized the kernel to remove all the devices that were not present, and that new kernel would not boot -- paniced right after detecting ida0. I'm currently trying to resolve that issue by gradually removing devices and booting to find out which devices it needs that I thought it didn't. 2. The loader won't boot from the idad0s1a device. Here's the boot log: ida0: ignoring completion 1000 no devsw (majdev=0 bootdev=0xa0200000) Mounting root from ufs:/dev/idad0s1a no such device 'idad' setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0s1a ? List valid disk boot devices Abort manual input mountroot> ufs:/dev/id0s1a Mounting root from ufs:/dev/id0s1a The weird thing is that the id0s1a device isn't even present in the /dev directory. The ida devices present in /dev are (ls -la /dev/id* ): crw-r----- 1 root operator 109, 0x00010002 Apr 19 09:17 /dev/idad0 crw-r----- 1 root operator 109, 0 Apr 19 09:17 /dev/idad0a crw-r----- 1 root operator 109, 1 Apr 19 09:17 /dev/idad0b crw-r----- 1 root operator 109, 2 Apr 19 09:17 /dev/idad0c crw-r----- 1 root operator 109, 3 Apr 19 09:17 /dev/idad0d crw-r----- 1 root operator 109, 4 Apr 19 09:17 /dev/idad0e crw-r----- 1 root operator 109, 5 Apr 19 09:17 /dev/idad0f crw-r----- 1 root operator 109, 6 Apr 19 09:17 /dev/idad0g crw-r----- 1 root operator 109, 7 Apr 19 09:17 /dev/idad0h crw-r----- 1 root operator 109, 0x00020002 Apr 20 09:36 /dev/idad0s1 crw-r----- 1 root operator 109, 0x00020000 Apr 20 09:36 /dev/idad0s1a crw-r----- 1 root operator 109, 0x00020001 Apr 20 09:36 /dev/idad0s1b crw-r----- 1 root operator 109, 0x00020002 Apr 20 09:36 /dev/idad0s1c crw-r----- 1 root operator 109, 0x00020003 Apr 20 09:36 /dev/idad0s1d crw-r----- 1 root operator 109, 0x00020004 Apr 20 09:36 /dev/idad0s1e crw-r----- 1 root operator 109, 0x00020005 Apr 20 09:36 /dev/idad0s1f crw-r----- 1 root operator 109, 0x00020006 Apr 20 09:36 /dev/idad0s1g crw-r----- 1 root operator 109, 0x00020007 Apr 20 09:36 /dev/idad0s1h crw-r----- 1 root operator 109, 0x00030002 Apr 19 09:17 /dev/idad0s2 crw-r----- 1 root operator 109, 0x00030000 Apr 18 15:35 /dev/idad0s2a crw-r----- 1 root operator 109, 0x00030001 Apr 18 15:35 /dev/idad0s2b crw-r----- 1 root operator 109, 0x00030002 Apr 18 15:35 /dev/idad0s2c crw-r----- 1 root operator 109, 0x00030003 Apr 18 15:35 /dev/idad0s2d crw-r----- 1 root operator 109, 0x00030004 Apr 18 15:35 /dev/idad0s2e crw-r----- 1 root operator 109, 0x00030005 Apr 18 15:35 /dev/idad0s2f crw-r----- 1 root operator 109, 0x00030006 Apr 18 15:35 /dev/idad0s2g crw-r----- 1 root operator 109, 0x00030007 Apr 18 15:35 /dev/idad0s2h crw-r----- 1 root operator 109, 0x00040002 Apr 19 09:17 /dev/idad0s3 crw-r----- 1 root operator 109, 0x00050002 Apr 19 09:17 /dev/idad0s4 Viren -- Viren Shah | "Every time a file is committed, viren@rstcorp.com | a fairy gets its wings." viren@viren.org | -- TJ Walls To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message