Compilied 2.2.17 with ppp support in Slack. But ppp dont work. Please Help!

[gmoreno]

I compilied kernel 2.2.17. I KNOW that i included ppp support. I am 100% sure. I compilied it once and it didnt work so I compilied it again with ppp just to make sure I had it. But it dosent work. WHenever I try to connect to the net it tells me no ppp support in kernel. I get this message from pppd. WHen I try to dailup via script and kppp. PLEASE HELP ME!!!

[treatment]

a well-known KPPP bug.

Ignore it.

[gmoreno]

treatment...I know about the kppp bug. Its happened to me before. But I click on connect and when it connects I get a message in eterm saying ppp0 not found. If I connect with ppp-go(script) it tells me I don't have ppp compilied.

ITS MORE THAN THE BUG

[PLBlaze]

How did you compile ppp into kernel? if you made modules then make sure you modprobe for ppp,bsd_comp,shlc...If ppp is build right into kernel do you see a reference to it when doing dmesg | less or more?

I'd advise to get lastest stable pppd (2.4.0) package,search on freshmeat.net for pppd to get it.Hope this helps.

[gmoreno]

Yeah I compilied it once as a module and another time as modules. AND they do apeear in dmesg.

I am download 2.2.18 now and I will look for pppd

[gmoreno]

Ok I think pppd or 2.2.17 is not the problem. I installed the slackpack of the cdrom with the sources for 2.2.16 I compilied it and it starts but I dont got ppp support still. Believe me I know I added ppp support. But it seems that other stuff dosent work like I can not access my win partion or or any vfat disks. So some how kernel is not able or has problems. I looked at dmesg and it showed ppp support. PLEASE PLEASE HELP ME!

Ok let me tell you what else happened and maybe you can help me.

The other night I downloaded apmd. But it said I had no support in kernel so I recompilied but ppp didnt work. BUT I was able to boot in to my old kernel.

But then I tried to recompile it did it like this:

make menuconfig
make dep
make modules
make modules install

Then I notice that it installed it in my root directory and did everthing with lilo. I booted it up, no luck. Tried to go to my old kernel, but that didn't work although I told lilo to boot up the old kernel I still boots up 2.2.17.

I think make install did this. So know I cant boot in to my Original 2.2.16 only my newly created kernels which have limited support.. No ppp no vfat ..

ARRRRRGGGGGGGGG!!!!!1

[ovf]

I'd try building 2.2.17 again without modules. Be sure to do a "make clean" before the "make menuconfig". The PPP module may not be loading due to a version mismatch with modules built with the earlier kernel. Also, your last post didn't show the kernel being rebuilt. Maybe that's why Lilo didn't load 2.2.16?

It migh help if you posted the output from dmesg.

[btberch]

well my slack 7.1 install tells me everytime i open kppp that it is not in the kernal, but i continue with connect and it connects.

probably not relevant, but my 2 cents

btberch

[treatment]

You checked your /etc/lilo.conf and made sure that lilo is loading the correct kernels, correct?

Did you run lilo -v afterwards?

Is your computer connected to a network at all? Did you run netconfig? Did your slackware detect your modem at all?

[gmoreno]

I figured out my problem. THANK YOU VERY MUCH.

I had /lib/modules/2.2.17 & 2.2.16
They were there from previous (when 2.2.17 first came out) attempts at compiling the kernel. They were old modules.

What I did is erase /usr/src/linux-2.2.17 and 2.2.16 and erased /lib/modules/*.*

Then I got the source for the kernel compilied it. WHen I was finished I noticed that there was NOTHING in /lib/modules/2.2.17 although I did make modules install.

I remembering seeing somewhere something about make modules_install.

I tried it and voila my modules appeared. Booted up and now ppp works fine.

THANKS BE TO GOD I dont have to be in windows to surf the net. OH THANKS BE TO GOD.

WIndows is so dam slow. Never realized that

[ovf]

Congratulations. I went back and re-read your earlier post and noticed you had typed modules install instead modules_install. Wish I had noticed that yesterday.