Re: compiling a new kernel

2002-12-24 Thread Shyamal Prasad
"Bruce" == Bruce Park <[EMAIL PROTECTED]> writes: Bruce> Hello debian users, I'm currently using the 2.4.18-bf2.4 Bruce> kernel and I would like to use a new kernel so that I can Bruce> have access to my ms sidewinder joystick. Bruce> Since I'm new to kernel compiling, I was w

Re: compiling a new kernel

2002-12-23 Thread Jeff
Bruce Park, 2002-Dec-23 21:33 -0500: > Hello debian users, > > I'm currently using the 2.4.18-bf2.4 kernel and I would like to use a new > kernel so that I can have access to my ms sidewinder joystick. > Since I'm new to kernel compiling, I was wondering if anyone can give me > some pointers on

Re: Compiling a new kernel

2002-11-04 Thread Hugh Saunders
04/11/2002 13:12:57, "Emanuele Boieri" <[EMAIL PROTECTED]> wrote: > then I copied the new image in the boot location of the old one /boot/ > bzImage.(I saved the old one). So I edit the lilo.conf if you copied the new image to the same place as the old one, you shouldnt need to edit lilo.conf >

Re: Compiling a new kernel

2002-11-04 Thread Gerald V. Livingston II
On Mon, 2002-11-04 at 07:12, Emanuele Boieri wrote: > Hi everybody I hope that somenone can help me. I just followed > precisely the instruction for compiling/installing a new kernel >(2.4.19). The previeous version was 2.2. > 1.. tar xvjf "the kernel source" > 2.. make menuconfig > 3.. make

Re: Compiling a new kernel

2002-11-04 Thread Michael Naumann
On Monday 04 November 2002 14:12, Emanuele Boieri wrote: > Hi everybody I hope that somenone can help me. I just followed precisely > the instruction for compiling/installing a new kernel (2.4.19). The > previeous version was 2.2. 1.. tar xvjf "the kernel source" > 2.. make menuconfig > 3.. ma

RE: Compiling a new kernel

2002-11-04 Thread Mikael Jirari
Title: Message * Maybe you didn't compile the 2.4.19 kernel check if you're compiling this one and not the 2.2 * Maybe you made a mistake in lilo.conf, check the process again -Original Message-From: Emanuele Boieri [mailto:[EMAIL PROTECTED]] Sent: 04 November 2002 13:13T

Re: Compiling a new kernel

2001-03-31 Thread Mathias
> bash-2.03# insmod ./es1371.o > ./es1371.o: kernel-module version mismatch > ./es1371.o was compiled for kernel version 2.2.18pre21 > while this kernel is version 2.2.17. Hi Kaloyan! I think you shold look whether your new kernel is booting. The new vmlinuz should be in /boot or if you made no c

Re: Compiling a new kernel

2001-03-31 Thread Robert Voigt
> bash-2.03# insmod ./es1371.o > ../es1371.o: kernel-module version mismatch > ./es1371.o was compiled for kernel version 2.2.18pre21 > while this kernel is version 2.2.17. Looks like you're not running the newly compiled kernel 2.2.18pre21, but your old 2.2.17. You can check what kernel you're

Re: Compiling a new kernel and dselect problems

2000-06-29 Thread Bob Nielsen
On Thu, Jun 29, 2000 at 10:28:12AM +0200, Luca De Giorgi wrote: > Hi, > I'm a new entry in the worderful Debian world. > Previously i'd used Red Hat 6.x ad Mandrake but i thought i' was time to > make a jump in the real Linux world and started using a potato release > Well, my problem arise when i

Re: Compiling a new kernel.

1999-02-10 Thread Martin Bialasinski
>> "JRL" == James R Lunsford <[EMAIL PROTECTED]> writes: JRL> /usr/src/linux is linked to the 2.0.34 directory. Am I correct JRL> in assuming that I have to relink /usr/src/linux to the 2.0.35 JRL> directory? Yes. JRL> Anyway, can someone give me a down and dirty way to do this? Also, what JR

Re: Compiling a new kernel

1997-07-01 Thread joost witteveen
> In the instructions that came with the kernel source package, Linus > recommends making symlinks in the include directory to directories in the > usr/src/linux/arch directory. > > I also remember reading that libc5-dev contains a set of headers. > > Someone on the list recommended that the dire