Date: Wed, 13 Nov 1996 13:29:59 +0100 From: Christoph Kukulies <kuku@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: aic0/ed0 problem Message-ID: <199611131229.NAA02642@gilberto.physik.rwth-aachen.de>
next in thread | raw e-mail | index | archive | help
I still have a strange interaction between a ed0 (WD8013EPC/16bit) and a board which calls AVA 1505 Total CD Kit (Adaptec Altra (tm) Line) The board is recognized a an aic0 and it recognizes the HP DAT drive I've attached to it even fine. But it somehow interacts badly with ed0 (I have ed0 and ed1 in that machine both being a WD8013EPC). This is my config: # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # $Id: GENERIC,v 1.46.2.6 1995/10/25 17:29:51 jkh Exp $ # machine "i386" cpu "I486_CPU" ident CGATE maxusers 64 options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 options "SCSI_DELAY=0" #Be pessimistic about Joe SCSI device options BOUNCE_BUFFERS #include support for DMA bounce buffers options UCONSOLE #Allow users to grab the console options MROUTING #Allow MCAST options USERCONFIG options SYSVSHM options SYSVSEM options SYSVMSG config kernel root on wd0 controller isa0 controller aic0 at isa? port 0x140 bio irq 11 vector aicintr controller scbus0 at aic0 disk sd0 device st0 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 controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device lpt0 at isa? port? tty irq 7 vector lptintr # 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. #ed0 at 0x300-0x31f irq 10 maddr 0xcc000 msize 16384 on isa #ed0: address 00:00:c0:50:8f:67, type WD8013EPC (16 bit) #ed1 at 0x280-0x29f irq 3 maddr 0xd8000 msize 16384 on isa #ed1: address 00:00:c0:12:3b:2e, type WD8013EPC (16 bit) device ed0 at isa? port 0x300 net irq 10 iomem 0xcc000 vector edintr device ed1 at isa? port 0x280 net irq 3 iomem 0xd8000 vector edintr pseudo-device loop pseudo-device ether pseudo-device log # ijppp uses tun instead of ppp device #pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 32 pseudo-device gzip # Exec gzipped a.out's MB is a ISA/VL board with only ISA devices attached. The Adaptec SCSI board doesn't have a BIOS ROM on it though there are PC board locations for this but the decoding logic isn't populated either so I don't think the cc000 range is decoded. The effect is that ed0 always sends 'ed0 timeout' messages while ed1 is still functioning. I cannot ping into the network, ed0 is attached to while the network on ed1 works fine. The Adaptec board is definitely strapped to IRQ 11. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611131229.NAA02642>