From: Guest section DW <dwguest@win.tue.nl>
To: "Stephen C Burns" <sburns@farpointer.net>,
<linux-kernel@vger.kernel.org>
Subject: Re: LILO calling modprobe?
Date: Thu, 5 Jul 2001 22:42:45 +0200 [thread overview]
Message-ID: <20010705224245.A1789@win.tue.nl> (raw)
In-Reply-To: <003201c1058c$d9161d30$4201a8c0@lan.farpointer.net>
In-Reply-To: <003201c1058c$d9161d30$4201a8c0@lan.farpointer.net>; from Stephen C Burns on Thu, Jul 05, 2001 at 02:58:18PM -0500
On Thu, Jul 05, 2001 at 02:58:18PM -0500, Stephen C Burns wrote:
> Each time I run lilo, I receive the following message in syslog:
>
> modprobe: Can't locate module block-major-3
>
> This machine has no IDE devices. when I run lilo in verbose mode, I see
> that it is querying all possible hard disks in /dev (e.g. Caching device
> /dev/hda (0x0300, etc.). I am, in fact, running an older version of
> LILO (0.21) but upgrading when it is not necessary frightens me.
Well, why not look at the source, then?
void preload_dev_cache(void)
{
char tmp[10];
int i;
cache_add("/dev/hda",0x300);
for (i = 1; i <= 8; i++) {
sprintf(tmp,"/dev/hda%d",i);
cache_add(tmp,0x300+i);
}
cache_add("/dev/hdb",0x340);
for (i = 1; i <= 8; i++) {
sprintf(tmp,"/dev/hdb%d",i);
cache_add(tmp,0x340+i);
}
cache_add("/dev/sda",0x800);
for (i = 1; i <= 8; i++) {
sprintf(tmp,"/dev/sda%d",i);
cache_add(tmp,0x800+i);
}
cache_add("/dev/sdb",0x810);
for (i = 1; i <= 8; i++) {
sprintf(tmp,"/dev/sdb%d",i);
cache_add(tmp,0x810+i);
}
}
Before doing anything LILO v21 collects the hda, hdb, sda, sdb info.
There is no problem, certainly no kernel problem.
next prev parent reply other threads:[~2001-07-05 20:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-05 19:58 LILO calling modprobe? Stephen C Burns
2001-07-05 20:14 ` Aaron Lehmann
2001-07-05 20:42 ` Guest section DW [this message]
2001-07-05 21:03 ` [OT] " Aaron Lehmann
2001-07-05 22:03 ` Wakko Warner
2001-07-05 22:14 ` Albert D. Cahalan
2001-07-05 23:01 ` Guest section DW
2001-07-05 23:03 ` Aaron Lehmann
2001-07-05 23:08 ` Guest section DW
2001-07-05 23:29 ` Aaron Lehmann
2001-07-06 0:14 ` Wakko Warner
2001-07-05 20:57 ` Russell King
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=20010705224245.A1789@win.tue.nl \
--to=dwguest@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=sburns@farpointer.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;
as well as URLs for NNTP newsgroup(s).