[S.u.S.E. Linux] Two Issues after Kernel Compile
I have compiled a "customized" 2.0.33 kernel for myself, after checking the HOW-TOs and following threads in this list. I now have a 300k kernel that boots without a problem and works fine, as far as I can tell. Except... Issue 1: At boot time, dmesg shows nothing amiss. However, when I start pppd (compiled into the kernel), the message "localhost syslog: IPX support is not present in the kernel". OK, I _know_ that, I do not use Netware, am not on Ethernet, and so I excluded IPX from the kernel. I commented out the IPX lines from /etc/services, but no joy. What should I do to eliminate the message, or should I bother about it? Issue 2: I haven't upgraded the kernel, only recompiled it. My previous modules seem to work OK. Need I do a 'make modules_install' or am I headed for trouble if I don't? Howard Arons -- Powered by SuSE Linux 5.2 -- kernel 2.0.33 Communications by Mutt 0.89 - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, On Sat, Aug 08, 1998 at 15:51 -0400, Howard Arons wrote:
At boot time, dmesg shows nothing amiss. However, when I start pppd (compiled into the kernel), the message "localhost syslog: IPX support is not present in the kernel". OK, I _know_ that, I do not use Netware, am not on Ethernet, and so I excluded IPX from the kernel. I commented out the IPX lines from /etc/services, but no joy.
What should I do to eliminate the message, or should I bother about it?
Add `-ipx-protocol' to /etc/ppp/options. Ciao, Stefan - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, On Sat, 8 Aug 1998, Howard Arons wrote:
I have compiled a "customized" 2.0.33 kernel for myself, after checking the HOW-TOs and following threads in this list. I now have a 300k kernel that boots without a problem and works fine, as far as I can tell. Except...
Issue 1:
At boot time, dmesg shows nothing amiss. However, when I start pppd (compiled into the kernel), the message "localhost syslog: IPX support is not present in the kernel". OK, I _know_ that, I do not use Netware, am not on Ethernet, and so I excluded IPX from the kernel. I commented out the IPX lines from /etc/services, but no joy.
What should I do to eliminate the message, or should I bother about it?
Ignore it. Or "fix" ifconfig.
Issue 2:
I haven't upgraded the kernel, only recompiled it. My previous modules seem to work OK. Need I do a 'make modules_install' or am I headed for trouble if I don't?
No, you can leave them alone. There's only one thing to look for: If you enable module versioning (setting CONFIG_MODVERSIONS), you need to recompile the modules, as our precompiled kernels default to CONFIG_MODVERSIONS set to off.
Howard Arons -o) Hubert /\\ _\_v
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Howard Arons wrote:
I have compiled a "customized" 2.0.33 kernel for myself, after checking the HOW-TOs and following threads in this list. I now have a 300k kernel that boots without a problem and works fine, as far as I can tell. Except...
Issue 1:
At boot time, dmesg shows nothing amiss. However, when I start pppd (compiled into the kernel), the message "localhost syslog: IPX support is not present in the kernel". OK, I _know_ that, I do not use Netware, am not on Ethernet, and so I excluded IPX from the kernel. I commented out the IPX lines from /etc/services, but no joy.
What should I do to eliminate the message, or should I bother about it?
check /sbin/init.d/nwe, the start script for novell server emulation. I "older" SuSE versions, this script was run regardless the setting of a "stsrt" variable (rc.config) this has now changed. ("start_nwe" in rc.config) Set it in rc.config to no. You can ignore this message as well.
Issue 2:
I haven't upgraded the kernel, only recompiled it. My previous modules seem to work OK. Need I do a 'make modules_install' or am I headed for trouble if I don't?
if you made some changes to some modules (I think i.e. of sound) they need replacement, if you installed the package kernel-modules they all should be there, no need to replace them. I usually did a "make dep clean zImage modules modules_install", just to be save. Now, I started compiling only the obvious nessesary, successful sofar. One thing keep in mind: always keep a working kernel, just in case ;-))
Howard Arons --
Jürgen -- ========================================== __ _ Jürgen Braukmann e-mail: brauki@cww.de | / / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | / /__/ / _ \/ // /\ \/ / ========================================== /____/_/_//_/\_,_/ /_/\_\ - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On Aug 08, 1998, Howard Arons wrote:
I have compiled a "customized" 2.0.33 kernel for myself [...]
Two more questions about my "new" kernel. Q1. There has apparently been no info included in the zImage about _who_ compiled this kernel. Thus, 'uname -a' gives the following: "Linux BeagleDog 2.0.33 #1 Fri Aug 7 09:05:28 EDT 1998 i486 unknown" What should I have done to have such info included next time? I suppose there's something to edit in /usr/src/linux/Makefile. Q2. The compile gave an _un_compressed kernel /usr/src/linux/vmlinux as well as the zImage. I can see no reason to keep the vmlinux file now; what am I missing?
[...] when I start pppd the message "localhost syslog: IPX support is not present in the kernel".
Sincere thanks to Stefan Troeger for the '-ipx-protocol' option for pppd. Problem solved. Re Hubert Mantel's suggestion to 'fix ifconfig' as a solution to the IPX problem, sorry Hubert, but as far as I can tell there is no boot action that sets an ipx device with ifconfig. Or maybe I just haven't the faintest idea of what you meant :-) Howard Arons -- Powered by SuSE Linux 5.2 -- kernel 2.0.33 Communications by Mutt 0.89 - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, On Mon, 10 Aug 1998, Howard Arons wrote:
On Aug 08, 1998, Howard Arons wrote:
I have compiled a "customized" 2.0.33 kernel for myself [...]
Two more questions about my "new" kernel.
Q1. There has apparently been no info included in the zImage about _who_ compiled this kernel. Thus, 'uname -a' gives the following: "Linux BeagleDog 2.0.33 #1 Fri Aug 7 09:05:28 EDT 1998 i486 unknown" What should I have done to have such info included next time? I suppose there's something to edit in /usr/src/linux/Makefile.
This info only is printed on bootup. Use "dmesg" to see it.
Q2. The compile gave an _un_compressed kernel /usr/src/linux/vmlinux as well as the zImage. I can see no reason to keep the vmlinux file now; what am I missing?
It's an intermediate file (similar to the .o files laying around). You can delete it if you want.
[...] when I start pppd the message "localhost syslog: IPX support is not present in the kernel".
Sincere thanks to Stefan Troeger for the '-ipx-protocol' option for pppd. Problem solved.
Re Hubert Mantel's suggestion to 'fix ifconfig' as a solution to the IPX problem, sorry Hubert, but as far as I can tell there is no boot action that sets an ipx device with ifconfig. Or maybe I just haven't the faintest idea of what you meant :-)
Sorry, I was completely wrong here. I mixed it with another problem. Sorry for the confusion...
Howard Arons -o) Hubert /\\ _\_v
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (4)
-
brauki＠cityweb.de -
hlarons＠ComCAT.COM -
mantel＠suse.de -
stefan.troeger＠wirtschaft.tu-chemnitz.de