Date: Tue, 19 Jan 1999 23:20:13 -0500 (EST) From: Simon Shapiro <shimon@simon-shapiro.org> To: koziol@ncsa.uiuc.edu Cc: freebsd-scsi@FreeBSD.ORG Subject: RE: DPT problems Message-ID: <XFMail.990119232013.shimon@simon-shapiro.org> In-Reply-To: <199901192307.RAA00468@hawkwind.ncsa.uiuc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
koziol@ncsa.uiuc.edu, On 19-Jan-99 you wrote: > Howdy, > I'm running 3.0-release (and impatiently waiting for the 3.0-stable > release tomorrow.. :-) on an SMP box with an Adaptec 3940AUW on the Tyan > S1836DLUAN motherboard. I've installed a DPT PM2654U2-R with 16MB of > cache > RAM in the system also, but I can't get the kernel to recognize my hard > drive > when it is trying to mount root, near the end of the booting process. > It > gets as far as saying "changing root device to da0s1a" and then whines > about > not finding the drive to mount as root. This is weird to me, since it's > gotten > this far by reading the kernel from the drive.. :-? I've attached my > kernel > config file below, can anyone point out any obvious problems? Perhaps > this is > already fixed in the current->stable tree and I can just download the > stable > source tomorrow when it's released? (knock on wood :-) I'm currently > running > fine (but slower than I want) from the on-board Adaptec controller. > > Thanks for any help, > Quincey Koziol > koziol@ncsa.uiuc.edu Please help me out here. What exactly is a PM2654U2-R ? I it by any chance a SmartCace V? One of the i2o, i960 based cards? If so, I do not have the driver completed yet. If not, please give me some more hardware details... Simon BTW, it is very feasible for a DPT to allow you to boot, but not run; the boot code uses BIOS calls and the DPT card emulates IDE via the SCSI BIOS. The kernel, of course, does not use the BIOS, thus it sees but it does not... Simon > > > # > # SMP-GENERIC -- Smp machine with WD/AHx/NCR/BTx family disks > # > # For more information read the handbook part System Administration -> > # Configuring the FreeBSD Kernel -> The Configuration File. > # The handbook is available in /usr/share/doc/handbook or online as > # latest version from the FreeBSD World Wide Web server > # <URL:http://www.FreeBSD.ORG/>; > # > # An exhaustive list of options and more detailed explanations of the > # device lines is present in the ./LINT configuration file. If you are > # in doubt as to the purpose or necessity of a line, check first in LINT. > # > # $Id: SMP-GENERIC,v 1.17 1998/10/16 04:44:05 peter Exp $ > > machine "i386" > # SMP does NOT support 386/486 CPUs. > #cpu "I386_CPU" > #cpu "I486_CPU" > > #cpu "I586_CPU" > cpu "I686_CPU" > ident SMP-Hawkwind > maxusers 32 > > # Options for the VM subsystem > #options PQ_NOOPT # No coloring > options PQ_LARGECACHE # color for 512k/16k cache > #options PQ_HUGECACHE # color for 1024k/16k cache > > # > # Allow user-mode programs to manipulate their local descriptor tables. > # This option is required for the WINE Windows(tm) emulator, and is > # not used by anything else (that we know of). > # > options USER_LDT #allow user-level control of i386 ldt > > # > # This option includes a MD5 routine in the kernel, this is used for > # various authentication and privacy uses. > # > options "MD5" > > # > # Allow processes to switch to vm86 mode, as well as enabling direct > # user-mode access to the I/O port space. This option is necessary for > # the doscmd emulator to run. > # > options "VM86" > > # > # PERFMON causes the driver for Pentium/Pentium Pro performance counters > # to be compiled. See perfmon(4) for more information. > # > options PERFMON > > # Create a SMP capable kernel (mandatory options): > options SMP # Symmetric MultiProcessor Kernel > options APIC_IO # Symmetric (APIC) I/O > > # Optional, these are the defaults: > #options NCPU=2 # number of CPUs > options NBUS=5 # number of busses > #options NAPIC=1 # number of IO APICs > #options NINTR=24 # number of INTs > > # Lets always enable the kernel debugger for SMP. > #options DDB > > # SMP shouldn't need x87 emulation, disable by default. > #options MATH_EMULATE #Support for x87 emulation > > options INET #InterNETworking > options FFS #Berkeley Fast Filesystem > options FFS_ROOT #FFS usable as root device [keep this!] > options MFS #Memory Filesystem > options MFS_ROOT #MFS usable as root device, "MFS" req'ed > options NFS #Network Filesystem > options NFS_ROOT #NFS usable as root device, "NFS" req'ed > #options MSDOSFS #MSDOS Filesystem > options "CD9660" #ISO 9660 Filesystem > options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed > options PROCFS #Process filesystem > options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] > options SCSI_DELAY=5000 #Be pessimistic about Joe SCSI device > options UCONSOLE #Allow users to grab the console > #options FAILSAFE #Be conservative > options USERCONFIG #boot -c editor > options VISUAL_USERCONFIG #visual boot -c editor > > config kernel root on da0 > > controller isa0 > controller pci0 > > controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr > disk fd0 at fdc0 drive 0 > disk fd1 at fdc0 drive 1 > > # No IDE disks in hawkwind currently - QAK - 1/13/99 > #options "CMD640" # work around CMD640 chip deficiency > #controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr > #disk wd0 at wdc0 drive 0 > #disk wd1 at wdc0 drive 1 > > # A single entry for any of these controllers (ncr, ahb, ahc, amd) is > # sufficient for any number of installed devices. > controller ahc0 > > # The 'dpt' driver provides support for DPT controllers > # (http://www.dpt.com/). > # These have hardware RAID-{0,1,5} support, and do multi-initiator I/O. > # The DPT controllers are commonly re-licensed under other brand-names - > # some controllers by Olivetti, Dec, HP, AT&T, SNI, AST, Alphatronic, NEC > # and > # Compaq are actually DPT controllers. > # > # See sys/dev/dpt for debugging and other subtle options. > # DPT_VERIFY_HINTR Performs some strict hardware interrupts > # testing. > # Only use if you suspect PCI bus corruption > # problems > # DPT_RESTRICTED_FREELIST Normally, the freelisat used by the DPT for > # queue > # will grow to accomodate increased use. This > # growth > # will NOT shrink. To restrict the number of > # queue > # slots to exactly what the DPT can hold at one > # time, > # enable this option. > # DPT_MEASURE_PERFORMANCE Enables a set of (semi)invasive metrics. > # Various > # instruments are enabled. The tools in > # /usr/sbin/dpt_* assume these to be enabled. > # DPT_FREELIST_IS_STACK For optimal L{1,2} CPU cache utilization, > # enable > # this option. Otherwise, the transaction > # queue is > # a LIFO. I cannot measure the performance > # gain. > # DPT_HANDLE_TIMEOUTS Normally device timeouts are handled by the > # DPT. > # If you ant the driver to handle timeouts, > # enable > # this option. If your system is very busy, > # this > # option will create more trouble than solve. > # DPT_TIMEOUT_FACTOR Used to compute the excessive amount of time > # to > # wait when timing out with the above option. > # DPT_DEBUG_xxxx These are controllable from sys/dev/dpt/dpt.h > # DPT_LOST_IRQ When enabled, will try, once per second, to > # catch > # any interrupt that got lost. Seems to help > # in some > # DPT-firmware/Motherboard combinations. > # Minimal > # cost, great benefit. > # DPT_RESET_HBA Make "reset" actually reset the controller > # instead of fudging it. Only enable this if > # you > # are 100% certain you need it. > # DPT_SHUTDOWN_SLEEP Reset controller if a request take more than > # this number of seconds. Do NOT enable this > # unless you are really, really, really certain > # you need it. You are advised to call Simon (the > # driver author) before setting it, and NEVER, > # EVER set it to less than 300s (5 minutes). > controller dpt0 > > # DPT options > #options DPT_VERIFY_HINTR > options DPT_RESTRICTED_FREELIST > #!CAM# options DPT_MEASURE_PERFORMANCE > options DPT_FREELIST_IS_STACK > #!CAM# options DPT_HANDLE_TIMEOUTS > options DPT_TIMEOUT_FACTOR=4 > options DPT_INTR_DELAY=200 # Some motherboards need that > options DPT_LOST_IRQ > #options DPT_RESET_HBA > # Don't EVER set this without having talked to Simon Shapiro on the phone > # first. > #options DPT_SHUTDOWN_SLEEP=500 > > controller scbus2 at ahc0 bus 0 > controller scbus3 at ahc0 bus 1 > controller scbus0 at dpt0 bus 0 > controller scbus1 at dpt0 bus 1 > > device da0 #SCSI direct access devices (aka disks) > device pass0 #CAM passthrough driver > device cd0 #SCSI CD-ROMs > > # syscons is the default console driver, resembling an SCO console > device sc0 at isa? port "IO_KBD" conflicts tty irq 1 vector scintr > device npx0 at isa? port "IO_NPX" irq 13 vector npxintr > > # > # Other standard PC hardware: `lpt', `mse', `psm', `sio', etc. > # > # lpt: printer port > # lpt specials: > # port can be specified as ?, this will cause the driver to scan > # the BIOS port list; > # the irq and vector clauses may be omitted, this > # will force the port into polling mode. > # mse: Logitech and ATI InPort bus mouse ports > # psm: PS/2 mouse port [note: conflicts with sc0/vt0, thus "conflicts" > # keywd] > # sio: serial ports (see sio(4)) > > device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector siointr > device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr > > device lpt0 at isa? port? tty irq 7 vector lptintr > > device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr > > # Order is important here due to intrusive probes, do *not* alphabetize > # this list of network interfaces until the probes have been fixed. > # Right now it appears that the ie0 must be probed before ep0. See > # revision 1.20 of this file. > device fxp0 > > pseudo-device loop > pseudo-device ether > pseudo-device sl 1 > pseudo-device ppp 1 > pseudo-device tun 1 > options PPP_BSDCOMP #PPP BSD-compress support > options PPP_DEFLATE #PPP zlib/deflate/gzip support > options PPP_FILTER #enable bpf filtering (needs bpfilter) > > ##################################################################### > # MISCELLANEOUS DEVICES AND OPTIONS > > # The `pty' device usually turns out to be ``effectively mandatory'', > # as it is required for `telnetd', `rlogind', `screen', `emacs', and > # `xterm', among others. > > pseudo-device pty 16 > pseudo-device gzip # Exec gzipped a.out's > > # KTRACE enables the system-call tracing facility ktrace(2). > # This adds 4 KB bloat to your kernel, and slightly increases > # the costs of each syscall. > #options KTRACE #kernel tracing > > # This provides support for System V shared memory, semaphores & > # messages. > # > options SYSVSHM > options SYSVSEM > options SYSVMSG > > # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be > # aware of the legal and administrative consequences of enabling this > # option. The number of devices determines the maximum number of > # simultaneous BPF clients programs runnable. > pseudo-device bpfilter 4 #Berkeley packet filter > > # Enable PnP support in the kernel. This allows you to automaticly > # attach to PnP cards for drivers that support it and allows you to > # configure cards from USERCONFIG. See pnp(4) for more info. > controller pnp0 > > # Luigi's snd code (use INSTEAD of snd0 and all VOXWARE drivers!). > # You may also wish to enable the pnp controller with this, for pnp > # sound cards. > # > device pcm0 at isa? port ? tty irq 10 drq 1 flags 0x0 vector pcmintr > > # Not controlled by `snd' > device pca0 at isa? port IO_TIMER1 tty > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message Sincerely Yours, Shimon@Simon-Shapiro.ORG 770.265.7340 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.990119232013.shimon>