Strange PPP message

I recently compiled a 2.2.25 kernel and included
PPP into the kernel instead of as a module.
Now everytime I try to connect using the "ppp-on"
command, it keeps displaying this message:

modprobe: modprobe: can't locate module ppp0
registered device ppp0

Then the modem starts dialing and I connect to
my ISP and everything works fine with no further
problems.

Even though everytime works fine, I would like
to know why I am getting this message partly
out of annoyance and partly because I would like
to learn something from this.

I upgraded to pppd version 2.3.11 as the kernel
documentation told me to, so I can't see what's
wrong here.

I find it a bit strange because ppp is compiled
into the kernel already, so it shouldn't even be
looking for a module. Furthermore, why is it
complaining about a "ppp0" module? Isn't
the correct name of the module called "ppp"?

Can anybody explain this?

Web Spinner <(E-Mail Removed)> wrote:
> I recently compiled a 2.2.25 kernel and included
> PPP into the kernel instead of as a module.
> Now everytime I try to connect using the "ppp-on"
> command, it keeps displaying this message:

> modprobe: modprobe: can't locate module ppp0
> registered device ppp0

A wild guess would be that the PPP code in the new kernel has changed
to parallel the code in the 2.4.x kernels and that "ppp0" is defined
in /etc/modules.conf for the wrong module names.

....

Ha! After reading the rest of the post it looks like all the necessary
PPP code is compiled into the kernel and kmod (or kerneld) is trying to
find "ppp0" modules defined in modules.conf - which now don't exist.
Just remove the "ppp0" line(s).

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* Slogan appropriate for a certain well-known software company:
FAILURE IS NOT AN OPTION - it is built into the operating system
and comes bundled with the software. */

Web Spinner <(E-Mail Removed)> wrote in
news:Xns9469E0A33E825webspinnerhotpopcom@203.134.6 7.67:

> I recently compiled a 2.2.25 kernel and included
> PPP into the kernel instead of as a module.
> Now everytime I try to connect using the "ppp-on"
> command, it keeps displaying this message:
>
> I find it a bit strange because ppp is compiled
> into the kernel already, so it shouldn't even be
> looking for a module. Furthermore, why is it
> complaining about a "ppp0" module? Isn't
> the correct name of the module called "ppp"?
>

This is not strange at all.
When you execute ppp-on script, it does, i presume,
ifconfig ppp0 ... up

As the script does this, the kernel needs to know what ppp0 is
and as you have not specified what it is, the kernel
tries to load 'ppp0' module.

To resolve this problem consult `man modules.conf' and
add a correct entry to /etc/modules.conf
(alias ppp0 ppp)


P.Krumins

Clifford Kite <(E-Mail Removed)> wrote in
news:(E-Mail Removed):

> A wild guess would be that the PPP code in the new kernel has changed
> to parallel the code in the 2.4.x kernels and that "ppp0" is defined
> in /etc/modules.conf for the wrong module names.
>
> ...
>
> Ha! After reading the rest of the post it looks like all the necessary
> PPP code is compiled into the kernel and kmod (or kerneld) is trying to
> find "ppp0" modules defined in modules.conf - which now don't exist.
> Just remove the "ppp0" line(s).
>

The file modules.conf never had any lines with ppp0,
so this can't be the problem.

Peteris Krumins <(E-Mail Removed)> wrote in
news:Xns9469D843D3C60whitesuneapollolv@130.133.1.4 :

> This is not strange at all.
> When you execute ppp-on script, it does, i presume,
> ifconfig ppp0 ... up
>
> As the script does this, the kernel needs to know what ppp0 is
> and as you have not specified what it is, the kernel
> tries to load 'ppp0' module.
>
> To resolve this problem consult `man modules.conf' and
> add a correct entry to /etc/modules.conf
> (alias ppp0 ppp)
>
>
> P.Krumins
>

I can't seem to find any lines in the ppp-on script with
the command of "ifconfig ppp0 ... up". It does however make
use of pppd with chat to make a connection, so I am guessing
that pppd must internally execute that command.

I tried adding the line "alias ppp0 ppp" to the file /etc/modules.conf
as you suggested and it didn't make a difference. I still get
exactly the same symptoms as before.

Web Spinner <(E-Mail Removed)> wrote:
> Clifford Kite <(E-Mail Removed)> wrote in
> news:(E-Mail Removed):

>> Ha! After reading the rest of the post it looks like all the necessary
>> PPP code is compiled into the kernel and kmod (or kerneld) is trying to
>> find "ppp0" modules defined in modules.conf - which now don't exist.
>> Just remove the "ppp0" line(s).

> The file modules.conf never had any lines with ppp0,
> so this can't be the problem.

That was a surprise. But poking around I found that modprobe itself
(version 2.4.2 anyway) has ppp0 built in as an alias for ppp - also a
surprise. Executing "modprobe -c|less" is likely to show that to be the
case for you too. Adding the line "alias ppp off" to /etc/modules.conf
should eliminate the message. I've never gotten that message, but that's
likely because I don't compile PPP as modules or use module autoloading
for anything.

BTW, pppd brings up a PPP interface automagically so there should be no
"ifconfig ppp0 ... up" in any script.

Thanks for the follow-up and the opportunity for me to learn something
new.

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." Benjamin Franklin */

Web Spinner <(E-Mail Removed)> wrote in
news:Xns946C9D98A5D0Dwebspinnerhotpopcom@203.134.6 7.67:


>
> I can't seem to find any lines in the ppp-on script with
> the command of "ifconfig ppp0 ... up". It does however make
> use of pppd with chat to make a connection, so I am guessing
> that pppd must internally execute that command.
>
> I tried adding the line "alias ppp0 ppp" to the file /etc/modules.conf
> as you suggested and it didn't make a difference. I still get
> exactly the same symptoms as before.
>

Did you or any script update module dependencies via
`depmod -a'
after you had the line added in the file?


P.Krumins

Peteris Krumins <(E-Mail Removed)> wrote in
news:Xns946DF14FEEFEEwhitesuneapollolv@130.133.1.4 :

> Did you or any script update module dependencies via
> `depmod -a'
> after you had the line added in the file?
>
>
> P.Krumins

Yep, one of the initialization scripts does
that at boot up.