Re: Recompiling kernel broke my ppp
On Sat, 7 Dec 1996, Paul Christenson wrote: > There is something that I've been wondering.. Why is everyone so > fascinated with modules? I acknowledge that they have their uses, but > how many people really need to UNLOAD a module once it's loaded? > > If you need it, compile it into the kernel, where it belongs. You'll > find that there are a lot fewer problems if you do. edwalter already brought up two good reasons. here's a third: flexibility: you can compile a kernel with modules that you need plus modules that you MIGHT need in the future. e.g. you have an ne2000 ethernet card now but you're planning to upgrade to a 3c509 in a few weeks. compile a kernel with ne2000 and 3c509 modules and just use whichever one you need at the time. You'll still have to reboot but only because you cant swap the cards without powering down :-) a more common scenario is wanting to give yourself the flexibility of running samba or netatalk or ipx stuff later. You dont need it now but as soon as you have time you'll get it working. If it's a module, just load it and experiment without having to recompile the kernel and without having to reboot. and a fourth: finding out where hardware lives without rebooting 50,000,000 times: e.g. you have to convert an old 386 box with some sort of ethernet card in it into a linux box router. of course, there is no documentation for any of the hardware and the jumper settings on the card don't make any sense to you at all. If you compile the ethernet card into the kernel you have to edit /etc/lilo.conf, run lilo & reboot every time you try a new io port address and irq. With modules, you just keep on running modprobe or insmod commands from the shell prompt until the module loads successfully, make a note of the settings that worked, and edit /etc/modules or /etc/conf.modules to make those settings the defaults for that module. 5 minutes work rather than 1+ hours. this is particularly obvious when you are installing two or more ethernet cards in a machine (quite common for a router or firewall box). It's so much easier doing it with modules that i wouldn't even consider doing it any other way. BUT, no matter what hardware you've got and no matter how well the standard debian kernel works for you, it is a very good idea to compile your own kernel as soon as possible. Why waste memory on unneeded drivers? Also, many drivers add a couple of minutes to booting time while they probe for non-existant hardware. The standard debian kernel is a "one-size-fits-all" affair. Roll your own to suit your own hardware as soon as possible. craig -- This message was delayed because the list mail delivery agent was down.
Re: Recompiling kernel broke my ppp
On Sat, 7 Dec 1996, Paul Christenson wrote: > > There is something that I've been wondering.. Why is everyone so > fascinated with modules? I acknowledge that they have their uses, but how > many people really need to UNLOAD a module once it's loaded? > > If you need it, compile it into the kernel, where it belongs. You'll find > that there are a lot fewer problems if you do. > Well, I have two answers: 1. On a 386/sx with 4MB of RAM the ability to load modules (sound alone is 160K) only when you need them means a lot less swapping. Granted, the ideal solution would be to add more memory, but many of us are poor. A person with low memory can benfit a lot by making lightly used drivers into modules (ppp, floppy, sound, etc...). 2. Some drivers can't be used effectivly unless they are module. For example, on my system, I have 2 parallel ports. One I use for my printer. The other I use with plip. These 2 drivers (lp and plip) are mutually exclusive when compiled into the kernel. The first one that loads would requisition all of the printer ports. The second would then fail to find any ports. With modules, I can say, "lp use port 1, plip use port 2". Just my 2 cents... Erv ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ ==-- _ / / \ ---==---(_)__ __ __/ / /\ \ - [EMAIL PROTECTED] --==---/ / _ \/ // /\ \/ / / /_/\ \ \ - [EMAIL PROTECTED] -=/_/_//_/\_,_/ /_/\_\ /__\ \ \ - [EMAIL PROTECTED] http://www.linux.org \_\/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Recompiling kernel broke my ppp
On Fri, 6 Dec 1996, Bruce Perens wrote: > We had a report that adding PPP to /etc/modules rather than letting kerneld > load it made it work. I don't know why that would be, so if you can > corroborate it, that would help. This isn't directed to you, Bruce.. but your message brought up a point. There is something that I've been wondering.. Why is everyone so fascinated with modules? I acknowledge that they have their uses, but how many people really need to UNLOAD a module once it's loaded? If you need it, compile it into the kernel, where it belongs. You'll find that there are a lot fewer problems if you do. | This is OFFICIAL WRITTEN notification that I want to be REMOVED | | from ALL commercial mailing lists. EVERY message sent from this | | account has had this request posted. ALL UNSOLICITED ADVERTISEMENTS | | SENT TO THIS ACCOUNT ARE IN VIOLATION OF FEDERAL (U.S.) LAW.| -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Recompiling kernel broke my ppp
We had a report that adding PPP to /etc/modules rather than letting kerneld load it made it work. I don't know why that would be, so if you can corroborate it, that would help. Thanks Bruce -- Bruce Perens K6BP [EMAIL PROTECTED] Finger [EMAIL PROTECTED] for PGP public key. PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6 1F 89 6A 76 95 24 87 B3 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Recompiling kernel broke my ppp
Title says most of it. I have had this problem before, and now I can't figure out how to fix it, nor can I find the previous reference in the mailing list archives. So here it is: I have been running 2.0.6 kernel for some time now with no problems. I was experimenting around with trying to get my SB16 audio card and my AHA1542 to work at the same time (wanted to hear Biff bark ) but had no luck. So I moved my original kernel back to /vmlinuz, but now ppp doesn't work. I can start my chat script, the modem dials, I get connected. I see the remote IP in the routing tables. I see the IP I have been dynamically assigned. I can ping myself (ppp0), but if I ping the remote IP, I see the xmit light on the modem blink, but there is no answer from the remote site. I am using kerneld, so pppd goes away if I let the modem disconnect. Tried recompiling from the 2.0.6 kernel-source with and without kernel ppp support. Did the make modules and modules_install. I am stumped. What should I try to get this fixed? I am sure it is simple but it escapes me. Thanks! --- Ken Gaugler Systems Engineer, Hybrid Networks, Inc. (home: 'keng at aimnet dot com', URL:http://users.aimnet.com/~keng) "The life of a Repo Man is ALWAYS INTENSE..." --- Ken Gaugler Systems Engineer, Hybrid Networks, Inc. (home: 'keng at aimnet dot com', URL:http://users.aimnet.com/~keng) "The life of a Repo Man is ALWAYS INTENSE..." -- This message was delayed because the list mail delivery agent was down.
