public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bristow <paul@paulbristow.net>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Cc: David Hinds <dhinds@sonic.net>
Subject: PCMCIA problem loading ide-floppy from ide_cs
Date: Wed, 17 Jan 2001 22:37:23 +0100	[thread overview]
Message-ID: <01011722372302.01013@zoltar.quantum.net> (raw)
In-Reply-To: <3A65FD84.129CA315@Hell.WH8.TU-Dresden.De>
In-Reply-To: <3A65FD84.129CA315@Hell.WH8.TU-Dresden.De>

Hi,

I am trying to understand the new PCMCIA configuration.  So far I am trying 
to use the kernel PCMCIA driver.  The yenta_socket driver is working fine. 

Using 2.4.0, and cardmgr 3.1.23

When I insert my Iomega Clik drive, cardmgr correctly identifies it as an ATA 
Fixed Disk and loads ide_cs.  ide_cs does the ide_probe and correctly assumes 
that the drive is an ide-floppy.  However at this point it doesn't seem to 
even try to load the module.  KMOD is set to y in .config

If I preload the ide-floppy module everything loads up fine and I can use the 
drive perfectly.  However, when I do a cardctl eject 0, everything screws up. 
The eject command says it works, unlinks ide_cs, but seems to leave 
ide-floppy working!  and yes, I have run depmod -a about a zillion times.

modprobe -nv finds the modules no problem.

Any pointers on where or what is wrong here?

Thanks

-- 

Paul Bristow
ide-floppy maintainer
http://paulbristow.net/linux/idefloppy.html

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-17 21:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-17 20:16 [OOPS] with 2.2.18 Udo A. Steinberg
2001-01-17 21:37 ` Paul Bristow [this message]
2001-01-18  8:59   ` PCMCIA problem loading ide-floppy from ide_cs Christian Gennerat

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=01011722372302.01013@zoltar.quantum.net \
    --to=paul@paulbristow.net \
    --cc=dhinds@sonic.net \
    --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