From: christophe barbe <christophe.barbe@online.fr>
To: linux-hotplug@vger.kernel.org
Subject: Re: Adaptec SlimSCSI 1480A
Date: Wed, 10 Oct 2001 21:28:22 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100274935400494@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100274739225720@msgid-missing>
After further investigation, it appears that :
. My card is sometimes detected.
it looks like a mechanical problem. After 20 insertion, the card is
finally datected and I see:
cs: cb_alloc(bus 20): vendor 0x9004, device 0x6075
PCI: Enabling device 14:00.0 (0000 -> 0003)
. The driver is not loaded automatically.
If I understand correctly it is because the aic7xxx is not define in the
/lib/modules/2.4.11/modules.pcimaps file.
Why AIC7xxx is not define in modules.pcimaps ?
Christophe
Le 2001.10.10 22:55:33 +0200, christophe barbe a écrit :
> Hi,
>
> I am trying the hotplug facilities. If I understand it correctly, the
> kernel call a user space tool which is then in charge of loading drivers
> for the just plugged device. Then kernel supporting the hotplug API are
> used (drivers providing standby/resume).
> Cardbus card are usable without pcmcia stuff.
>
> I've a kernel 2.4.11 with hotplug support enabled.
> I own a laptop Toshiba 2520cds with a pcmcia/cardbus slot and two cardbus
> cards : a 3com Megahertz 10/100 lan and an adaptec SlimSCCI 1480A.
>
> The first one is well managed by hotplug. The correct driver is loaded
> and
> the network interface is configured. But the second one is not detected.
>
> Nothing is written in /var/log/message and on the console when I insert
> my
> scsi card.
> Is there some debugging tools ?
>
> With pcmcia, the correct driver was apa1480 but if I have correctly
> understood the driver with hotplug is aic7xxx.
>
> My card works with pcmcia but only when inserted before booting.
>
> Christophe
>
>
>
>
> --
> Christophe Barbé <christophe.barbe@online.fr>
> GnuPG FingerPrint: E0F6 FADF 2A5C F072 6AF8 F67A 8F45 2F1E D72C B41E
>
> _______________________________________________
> Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
> Linux-hotplug-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
>
--
Christophe Barbé <christophe.barbe@online.fr>
GnuPG FingerPrint: E0F6 FADF 2A5C F072 6AF8 F67A 8F45 2F1E D72C B41E
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-10-10 21:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 20:55 Adaptec SlimSCSI 1480A christophe barbe
2001-10-10 21:28 ` christophe barbe [this message]
2001-10-11 0:00 ` Greg KH
2001-10-11 6:31 ` David Brownell
2001-10-11 19:55 ` christophe barbe
2001-10-11 21:32 ` Greg KH
2001-10-12 6:15 ` christophe barbe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-hotplug-100274935400494@msgid-missing \
--to=christophe.barbe@online.fr \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.