mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lathiat <lathiat@irc-desk.net>
To: Alan Chandler <alan@chandlerfamily.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How does ide-scsi get loaded?
Date: Sat, 12 Oct 2002 19:29:49 +0800	[thread overview]
Message-ID: <5.1.0.14.0.20021012192828.0183aa08@mail.bur.st> (raw)
In-Reply-To: <200210121106.58559.alan@chandlerfamily.org.uk>

well the standard places are
- /etc/modules
- initrd
or
/etc/modules.conf
if it is in modules something like alias char-major-blah ide-scsi, then 
change ide-scsi to 'off'

Else it may be compiled into the kernel, try passing ide-scsi=none or 
something similar to the kernel (check the docs)

At 11:06 AM 12/10/2002 +0100, you wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Please cc me on replies as I am not subscribed to the list.
>
>I am running a standard debian 2.4.19-k7 kernel on a configuration that 
>has an
>ide dvd rom drive and a scsi cd writer.
>
>Sometime during boot sequence (I can't find where in any log or dmesg - but
>looking at the text flying by - soon after the scsi adapter is found and the
>bus is being scanned for scsi devices) the module ide-scsi gets loaded.
>
>The problem is, I don't want it loaded because it prevents mplayer playing my
>dvds
>
>I initially assumed it was something in the debian start up that caused it but
>
>a) asking on the debian-user mailing list has not elicited any useful reponse
>b) grep -r ide-scsi /etc throws up nothing (ie there is not reference to
>ide-scsi in modules or modules.conf or any initialisation sequence doing a
>modprobe ide-scsi)
>c) scanning all through the initrd.img (loaded through the loop device) does
>not show any reference to ide-scsi either (although grep finds the sequence
>in bin/mount and then hangs locking my keyboard)
>d) modules.dep only shows ide-scsi needing other modules (ide-mod, scsi-mod)
>not the other way round.
>
>I am stuck, where can I look next?
>
>[and I know I could just do a rmmod at the end of the start up sequence but
>...]
>- --
>Alan Chandler
>alan@chandlerfamily.org.uk
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.2.0 (GNU/Linux)
>
>iD8DBQE9p/RCuFHxcV2FFoIRAiqmAJ4y7pWivbaNV/L4LKqLyBYpu+VsUgCgnSK2
>5YnCzrh6yVM+iwnBVk1BZQE=
>=N3vq
>-----END PGP SIGNATURE-----
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/


  reply	other threads:[~2002-10-12 11:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-12 10:06 Alan Chandler
2002-10-12 11:29 ` Lathiat [this message]
2002-10-12 14:33   ` Alan Chandler
2002-10-12 14:39     ` Michael Abshoff
2002-10-12 14:55       ` Alan Chandler
2002-10-12 16:01         ` Doug McNaught
2002-10-13  2:57           ` Keith Owens
2002-10-12 16:24         ` Thomas Molina
2002-10-12 18:06           ` Alan Chandler
2002-10-12 17:22         ` Nick Sanders

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=5.1.0.14.0.20021012192828.0183aa08@mail.bur.st \
    --to=lathiat@irc-desk.net \
    --cc=alan@chandlerfamily.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®