From: Markus Schaber <markus.schaber@student.uni-ulm.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: AHA-154X/1535 not recognized any more
Date: Wed, 18 Apr 2001 13:02:29 +0200 [thread overview]
Message-ID: <3ADD7445.6FD2068E@student.uni-ulm.de> (raw)
In-Reply-To: <E14pbdW-000368-00@the-village.bc.nu>
Alan Cox wrote:
>
> > Now I have the problem that kernels 2.4.2 and 2.4.3 don't recognize this
> > adapter any more, while all 2.2-kernels I used (I currently remember
> > 2.2.19, 2.2.18 and debian-2.2.17pre6) work with it without problems.
>
> Load the module with isapnp=1. It defaults to not scanning isapnp boards which
> strikes me as odd. Let me know if that fixes it if so I think I'll tweak the
> default
This gives me the following message:
lunix:/lib/modules/2.4.3# modprobe aha1542 isapnp=1
/lib/modules/2.4.3/kernel/drivers/scsi/aha1542.o: init_module: No such
device
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters
/lib/modules/2.4.3/kernel/drivers/scsi/aha1542.o: insmod
/lib/modules/2.4.3/kernel/drivers/scsi/aha1542.o failed
/lib/modules/2.4.3/kernel/drivers/scsi/aha1542.o: insmod aha1542 failed
markus
--
Markus Schaber -- http://www.schabi.de/ -- ICQ: 22042130
+-------------------------------------------------------------+
| Allgemeine Sig-Verletzung 0815/4711 <nicht OK> <Erbrechen> |
+-------------------------------------------------------------+
next prev parent reply other threads:[~2001-04-18 11:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 18:42 Markus Schaber
2001-04-17 19:59 ` Alan Cox
2001-04-18 11:02 ` Markus Schaber [this message]
2001-04-18 12:31 ` Alan Cox
2001-04-18 15:25 ` Markus Schaber
2001-04-18 15:45 ` Rafael E. Herrera
2001-04-20 12:28 ` Markus Schaber
2001-04-18 16:08 ` Alan Cox
2001-04-20 12:07 ` Markus Schaber
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=3ADD7445.6FD2068E@student.uni-ulm.de \
--to=markus.schaber@student.uni-ulm.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®