Date: Thu, 20 Apr 2000 15:01:24 -0400 From: Ian Cartwright <ICartwright@IT.RJF.com> To: "'viren@rstcorp.com'" <viren@rstcorp.com>, "Matthew N. Dodd" <winter@jurai.net> Cc: Jonathan Lemon <jlemon@flugsvamp.com>, Ian Cartwright <ICartwright@IT.RJF.com>, freebsd-hardware@freebsd.org Subject: RE: ida driver (Re: cvs commit: src/sys/dev/ida ida_eisa.c) Message-ID: <6D5097D4B56AD31190D50008C7B1579B670246@EXLAN5>
next in thread | raw e-mail | index | archive | help
I had both of those problem too. Matt Dodd's newest patch has fixed #2 for
me. And recompiling the kernel with 04/19 snapshot (or later) has solved
problem #1 for me. I think it was choking on finding the NCR 5c710 SCSI
controller... Not sure why though.
Ian Cartwright
Senior Engineer
Raymond James Associates
icartwright@it.rjf.com
-----Original Message-----
From: Viren R.Shah [mailto:viren@rstcorp.com]
Sent: Thursday, April 20, 2000 10:35 AM
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)
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:
<fstype>:<device> Mount <device> using filesystem <fstype>
eg. ufs:/dev/da0s1a
? List valid disk boot devices
<empty line> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6D5097D4B56AD31190D50008C7B1579B670246>