From owner-freebsd-bugs  Wed Nov  5 14:30:05 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id OAA14410
          for bugs-outgoing; Wed, 5 Nov 1997 14:30:05 -0800 (PST)
          (envelope-from owner-freebsd-bugs)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id OAA14389;
          Wed, 5 Nov 1997 14:30:03 -0800 (PST)
          (envelope-from gnats)
Date: Wed, 5 Nov 1997 14:30:03 -0800 (PST)
Message-Id: <199711052230.OAA14389@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: John Ioannidis <ji@research.att.com>
Subject: Re: kern/4945: continued failure to use the Adaptec 1460A PCMCIA SCSI host adaptor
Reply-To: John Ioannidis <ji@research.att.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/4945; it has been noted by GNATS.

From: John Ioannidis <ji@research.att.com>
To: nate@mt.sri.com
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: kern/4945: continued failure to use the Adaptec 1460A PCMCIA SCSI host adaptor
Date: Wed, 5 Nov 1997 17:19:47 -0500 (EST)

 > You haven't given me *any* useful information to go on.  What are the
 > results printed on the screen, or what the pccardd daemon said, etc..?
 > I can't help you unless you give me something to work with.
 
 I'll try to boot with the second serial port as the console (the first
 is an IRDA port) and capture the console messages. 
 
 In any case, I don't see a line in the PCCARD config file indicating
 that a driver for the 1460 is being configured; I would expect
 something like "controller foo0 on slot?" but all that's vaguely
 related to scsi in that config file is the "controller aic0 on isa0"
 (or something like that; I'm not near my FreeBSD machine right now),
 and then a "device sd0". Am I missing something here?
 
 What's the pccardd daemon? 
 
 To give you a bit more background: I'm trying to bring up FreeBSD on
 my notebook using a scsi jaz drive as the only disk; I assumed that
 something along the lines of what I described in the previous
 paragraph, combined with "config vmunix root on sd0" would do the
 trick. Apparently, this is not the case. 
 
 Am I totally wrong in assuming that this can be done? 
 
 Thanks,
 
 /ji