🚀 go-pugleaf

 
"Mark Vandersteen" <mvanders@merlin.net.au> writes:
 
> I posted here a few weeks ago about problems with pppd

> I have recompiled the kernel many many times using ppp in modules and in
> the kernel itself with no luck but never got it going and then presumed
> that it was the pppd program as i could get the ppp module to load but pppd
> would just do nothing except display a message of:     PPPD - Is
> unavailable on this system.

You will get a similar message to this if the ppp module is unable to be 
loaded. First check that the ppp.o module is available in 
/lib/modules/.../net/
You might want to see if you can load it manually with modprobe (you can
see the modules currently loaded with /sbin/lsmod).

You probably should check that module dependencies have been updated
by running /sbin/depmod -a .
This is typically done at boot time with this code in rc.sysinit 
(or similar) 

if [ -x /sbin/depmod ]; then
    depmod -a
fi

Example:(from my system)

[root@picu-sgh /root]# /sbin/modprobe ppp.o
[root@picu-sgh /root]# /sbin/lsmod
Module:        #pages:  Used by:
ppp                5		0
slhc               2	[ppp]	0
sr_mod             4		1 (autoclean)
isofs              5		1 (autoclean)
msbusmouse         1		1 (autoclean)
misc               1	[msbusmouse]	1 (autoclean)
ncpfs              6		1 (autoclean)
3c509              2		1 (autoclean)
ipx                4		4 (autoclean)
st                 6		0
hpfs               3		3 (autoclean)
[root@picu-sgh /root]# /sbin/modprobe -r ppp.o
[root@picu-sgh /root]# /sbin/lsmod
Module:        #pages:  Used by:
sr_mod             4		1 (autoclean)
isofs              5		1 (autoclean)
msbusmouse         1		1 (autoclean)
misc               1	[msbusmouse]	1 (autoclean)
ncpfs              6		1 (autoclean)
3c509              2		1 (autoclean)
ipx                4		4 (autoclean)
st                 6		0
hpfs               3		3 (autoclean)

If it loads and unloads OK, you could try using ppp with the module
loaded. If that works the problem is in autoloading the module as 
required. This is done with /sbin/kerneld.
Have you checked to see if kerneld is running? 

[root@picu-sgh /root]# ps -aux |grep kerneld |grep -v grep
root        17  0.0  0.3   872    48  ?  S   12:30   0:00 /sbin/kerneld 

On my system it is started at boot time with the following code in
/etc/rc.d/rc.sysinit

if [ -x /sbin/kerneld ]; then
    /sbin/kerneld
fi

Once this is all running I suspect your problems will disappear.
The kernel module code seems to work *very* nicely now.

Hope this helps,
Peter Rye

-- 
Peter Rye  <prye@picu-sgh.demon.co.uk>
Consultant in Paediatric Intensive Care,  St. George's Hospital, London, UK
Ph: +44 (0)181 725 1932                            Fax: +44 (0)181 725 0089
** Smoking areas in restaurants are like peeing areas in swimming pools. **