From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: "Russell King" <rmk@arm.linux.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Trying to run 2.6.0-test3
Date: Mon, 18 Aug 2003 19:41:34 +0900 [thread overview]
Message-ID: <151901c36577$12b6f680$1aee4ca5@DIAMONDLX60> (raw)
In-Reply-To: 20030817143313.A22402@flint.arm.linux.org.uk
"Russell King" <rmk@arm.linux.org.uk> replied to me:
> > 2.6.0-test3 gets it wrong:
> > Aug 17 16:39:01 diamondpana cardmgr[540]: socket 1: KME KXLC005 CD-ROM
> > Aug 17 16:39:01 diamondpana cardmgr[540]: executing: 'modprobe -v ide_cs'
> > Aug 17 16:39:02 diamondpana cardmgr[540]: + insmod /lib/modules/2.6.0-test3/kernel/drivers/ide/legacy/ide-cs.ko
> > Aug 17 16:39:02 diamondpana cardmgr[540]: bind 'ide_cs' to socket 1 failed: Invalid argument
>
> Not quite. This is an old problem dating back several years to early 2.4
> times. Back in the dark old days, ide-cs used to use the name "ide_cs" to
> bind the driver to the device. It now uses "ide-cs" for binding.
Yes the problem is reminiscent of early 2.4 days, but how is it that 2.4.19
doesn't have the problem and 2.6.0-test3 does have the problem on the same
machine?
> Make sure that "ide_cs" isn't mentioned in /etc/pcmcia/config - if it
> is, change it to "ide-cs".
I will hope to have time to check this next weekend, but I'm sure the 2.4
name ide-cs is used. I was startled to see 2.6.0-test3 load a module named
ide_cs instead of ide-cs, but there it was. It was listed that way by
lsmod, but failing in the bind as shown above. Notice that modprobe used
the same name as lsmod showed.
next prev parent reply other threads:[~2003-08-18 10:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-17 7:59 Trying to run 2.6.0-test3 Norman Diamond
2003-08-17 13:33 ` Russell King
2003-08-18 10:41 ` Norman Diamond [this message]
2003-08-18 11:21 ` Russell King
-- strict thread matches above, loose matches on Subject: below --
2003-08-18 11:37 John Bradford
2003-08-17 9:57 Norman Diamond
2003-08-17 17:25 ` Alan Cox
2003-08-18 10:35 ` Norman Diamond
2003-08-18 11:00 ` Vojtech Pavlik
2003-08-23 12:29 ` Norman Diamond
2003-08-25 14:24 ` Vojtech Pavlik
2003-08-15 8:11 Norman Diamond
2003-08-15 8:53 ` Felipe Alfaro Solana
2003-08-15 10:00 ` Norman Diamond
2003-08-15 11:53 ` Felipe Alfaro Solana
2003-08-15 13:20 ` Norman Diamond
2003-08-15 15:02 ` Felipe Alfaro Solana
2003-08-16 13:21 ` Norman Diamond
2003-08-15 10:14 ` Russell King
2003-08-15 12:39 ` Norman Diamond
2003-08-15 13:04 ` Mikael Pettersson
2003-08-17 1:51 ` Norman Diamond
2003-08-15 16:43 ` Joshua Kwan
2003-08-15 17:06 ` Randy.Dunlap
2003-08-15 17:15 ` Russell King
2003-08-15 17:16 ` Greg KH
2003-08-16 13:20 ` Norman Diamond
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='151901c36577$12b6f680$1aee4ca5@DIAMONDLX60' \
--to=ndiamond@wta.att.ne.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).