[4521] in RedHat Linux List

home help back first fref pref prev next nref lref last post

RE: lost PPP kernel support

daemon@ATHENA.MIT.EDU (Al Longyear)
Fri Nov 15 10:23:06 1996

From: Al Longyear <longyear@sii.com>
To: "'redhat-list@redhat.com'" <redhat-list@redhat.com>,
        "'sestaats@cs.twsu.edu'" <sestaats@cs.twsu.edu>
Date: Fri, 15 Nov 1996 07:03:51 -0800
Resent-From: redhat-list@redhat.com
Reply-To: redhat-list@redhat.com

Make sure that you install the kernel and the modules from the root
account.

There are three overlapping questions which you must answer in the
affirmative to enable PPP support.

The first is "TCP/IP networking?". If you don't answer Y to this then
you will get nothing -- no loopback; no ethernet; no PPP; nothing.

The second is "Network devices?". Again, this is to enable the device
lists. If you answered "Y" to the first one but "N" to this then you
will only have the loopback support, but still include TCP/IP.

The third is the specific question for PPP. This is either "Y" or "M" to
enable its selection. This is only asked if you answered "Y" to the
"Network devices" which is only asked if you answered "Y" to the TCP/IP
networking.

Then if you are using modules, and haven't included support for CSLIP in
the kernel then you will need to load the slhc module before you may
load the ppp module.

A good idea is to include "old" into the /etc/lilo.conf file such that
you have:

name = old
	optional
	read-only
	boot = /dev/hda1
	root = /dev/hda1
	image = /vmlinuz.old

(Just take whatever you have for 'linux' or whatever your kernel is
called and duplicate it. Rename the image file to vmlinuz.old and add
the additional keyword 'optional' to the group. The 'optional' keyword
is just that; it makes the image optional and LILO will still work
without you having the optional kernels.)

This will permit you to enter "old" and have it boot the previously
working kernel when you build a new one. The kernel installation
procedure for zlilo will take your current kernel and rename it to
vmlinuz.old automatically. This will create the 'old' kernel.

You can be doubly-safe, as I am, and have a 'good' which you manually
copy as well. Sometimes, when I am working on the kernel I don't find a
problem until after I have built several ones which makes the 'old'
concept useless to me when it really comes time to do standard chores
such as backups.

>----------
>From: 	Sean Staats[SMTP:sestaats@cs.twsu.edu]
>Sent: 	Thursday, November 14, 1996 5:55 PM
>To: 	redhat-list@redhat.com
>Subject: 	lost PPP kernel support
>
>I reconfigured my RH 4.0 kernel 2.0.18 to include sound.  I made a 
>bakcup copy of zImage and vmlinuz before doing so.  To my horror, make 
>rproper wiped out the backup of zImage!  I compiled a new kernel...
>make zImage
>make modules
>make modules_install
>Now I don't have PPP support anymore(yes I included everything I 
>needed), and I still don't even have the sound.  Now when I boot linux, 
>I get a bunch of "can't find modules" type messages.
>Am I doing something wrong or did I miss another RH4.0 fix?
>


--
  PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
  ________________________________________________________________________
  http://www.redhat.com/RedHat-FAQ   http://www.redhat.com/RedHat-Errata
  http://www.redhat.com/RedHat-Tips  http://www.redhat.com/mailing-lists
  ------------------------------------------------------------------------
To unsubscribe: mail -s unsubscribe redhat-list-request@redhat.com < /dev/null


home help back first fref pref prev next nref lref last post