Hi,
I was getting the same message but was unable to determine the module
it referred to. I solved it(not the way I wanted to) by removing the auto
load modules when I recompiled the kernel. Of course I had to compile
everything in rather than modularize :-(. Every thing seemed to work fine
for me too with the messages. My uneducated guess is that it has
something to do with the kerneld replacement? Maybe something in the
boot script sequence is pointing at a reference to pre 2.2.x. Any
thoughts?
Mike
On Tue, 9 Mar 1999, Germano Rizzo wrote:
>
> >When I boot 2.2.2 I get the following message:
> >modprobe: can't locate module char-major-4
> >How can I fix this?
> Me, too. the message repeats 30-40 times very quickly, and is followed
> by a green 'done'. However, it seems to work perfectly, so...
> Germano
>
> -
> To get out of this list, please send email to [EMAIL PROTECTED] with
> this text in its body: unsubscribe suse-linux-e
> Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
> archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
>
-
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
