Hi, I'm new to SuSE Linux and I'm (actually was) a long time RedHat user. Something very weird is happening. I've succesfully installed Suse sometime ago and I currently need a new module and decided to compile a new kernel. What I did was to be sure that I have installed package called lx_sus24 and compile the kernel cd /usr/src/linux make menuconfig (just select the additional package and leave others as they are) make dep make clean make modules make bzImage make modules_install rename vmlinuz add an entry to lilo.conf and run lilo. When I boot the computer with the new kernel, I got an error saying that a module for the ethernet already exists and is newer. My ethernets do not work as you have guessed, and the kernel module I've decided to install has nothing to do with networking at all When I boot the computer with the old kernel, everything is ok. Question 1: What am I missing? Question 2: What difference there exists in compiling kernel in Suse? Thanks in advance Oyku Gencay
* Oyku Gencay
Hi,
I'm new to SuSE Linux and I'm (actually was) a long time RedHat user. Something very weird is happening. I've succesfully installed Suse sometime ago and I currently need a new module and decided to compile a new kernel. What I did was to be sure that I have installed package called lx_sus24 and compile the kernel cd /usr/src/linux
If you are running the precompiled SuSE kernel than make cloneconfig (to get the config of the SuSE kernel
make menuconfig (just select the additional package and leave others as they are) make dep make clean make modules make bzImage make modules_install make bzlilo (so vmlinuz and the system.map is copied to /boot
rename vmlinuz no need this
add an entry to lilo.conf and run lilo. Question 1: What am I missing? looks like not copying the vmlinuz
Question 2: What difference there exists in compiling kernel in Suse?
except for cloneconfig (specifig to SuSE nothing that I know) -- Togan Muftuoglu
* Oyku Gencay
[010531 17:29]: Hi,
I'm new to SuSE Linux and I'm (actually was) a long time RedHat user. Something very weird is happening. I've succesfully installed Suse sometime ago and I currently need a new module and decided to compile a new kernel. What I did was to be sure
have installed package called lx_sus24 and compile the kernel cd /usr/src/linux
If you are running the precompiled SuSE kernel than make cloneconfig (to get the config of the SuSE kernel
make menuconfig (just select the additional package and leave others as
OK, thanks a lot, seems like I'm missing the make cloneconfig part
----- Original Message -----
From: Togan Muftuoglu
are) make dep make clean make modules make bzImage make modules_install make bzlilo (so vmlinuz and the system.map is copied to /boot
rename vmlinuz no need this
add an entry to lilo.conf and run lilo. Question 1: What am I missing? looks like not copying the vmlinuz
Question 2: What difference there exists in compiling kernel in Suse?
except for cloneconfig (specifig to SuSE nothing that I know)
-- Togan Muftuoglu
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
participants (2)
-
Oyku Gencay
-
Togan Muftuoglu