From: Randy Dunlap <randy.dunlap@oracle.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Dominik Brodowski <linux@dominikbrodowski.net>,
LKML <linux-kernel@vger.kernel.org>,
linux-pcmcia@lists.infradead.org
Subject: Re: Strange behavior since commit 5fef0e5c
Date: Mon, 17 Nov 2008 08:10:59 -0800 [thread overview]
Message-ID: <20081117081059.e008ff46.randy.dunlap@oracle.com> (raw)
In-Reply-To: <491DECF9.6020707@lwfinger.net>
On Fri, 14 Nov 2008 15:26:17 -0600 Larry Finger wrote:
> Bartlomiej Zolnierkiewicz wrote:
> > On Friday 14 November 2008, Larry Finger wrote:
> >> In testing kernel version 2.6.28-rc4 on my server that was running kernel
> >> 2.6.27, an external IDE disk system connected via a PCCard interface failed to
> >> start because module ide_disk would not load. The console output is as follows:
> >>
> >> finger@sonylap:~> sudo modprobe -v ide-disk
> >> WARNING: module 'ide_gd_mod' is unsupported
> >> FATAL: Module ide_disk not found.
> >
> > Please verify that your system uses a recent module-init-tools version
> > and then repeat 'make modules' + 'make modules_install' (it could be that
> > something went wrong previously during installing modules) as it works
> > just fine for me with 2.6.28-rc3 and module-init-tools 3.4.
>
> That was the problem. I had 3.3 pre11, which was installed by openSUSE 10.3.
> Updating to version 3.4 fixed the problem. Thanks.
>
> Should the requirement in Documentation/Changes be modified, or is that info no
> longer used?
IMO it should be updated (or deleted if it's really useless).
---
~Randy
prev parent reply other threads:[~2008-11-17 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 15:02 Strange behavior since commit 5fef0e5c Larry Finger
2008-11-14 19:53 ` Bartlomiej Zolnierkiewicz
2008-11-14 21:26 ` Larry Finger
2008-11-17 16:10 ` Randy Dunlap [this message]
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=20081117081059.e008ff46.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=Larry.Finger@lwfinger.net \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux@dominikbrodowski.net \
/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