How to compile the 2.6.18 kernel from kernel.org

[linuxnewbie946]

This thread has been replaced by the master kernel thread.
The master kernel thread was written by me, under my new name.

[linuxnewbie946]

Feel free to ask any questions......

[linuxnewbie946]

PS This will be updated for each 2.6.17 kernel release through July 31.

[Brain Juice]

Im following your guide now Compling as I type.

I didn't see these options however:

Activate:

-Preemption Model
--Voluntary Kernel Preemption (Desktop)

-High Memory Support
--off -if you have less than 1 GB of RAM
--1GB Low Memory Support -if you have 1GB of RAM
--4GB -if you have more than 1GB of RAM

-Timer frequency
--1000 Hz

Hope it doesn't matter too much. I have an AMD 3800 and 2 GB of RAM.

[linuxnewbie946]

It shouldn't matter too much at all.... unless you're a freak who wants the fastest computer in the world

[Brain Juice]

Oh Noes!! I better start over.

[danderson3]

Feel free to ask any questions......

I patched 2.6.17 with beyond3 and did
make xconfig
make-kpkg clean
make-kpkg -initrd --revision=686 kernel_image kernel_headers modules_image

now when I dpkg -i kernel-headers-2.6.17.7_686_i386.deb

I get the error:

dpkg: error processing kernel-headers-2.6.17.7_686_i386.deb (--install):
cannot access archive: No such file or directory
Errors were encountered while processing:
kernel-headers-2.6.17.7_686_i386.deb

How can I debug this?

thanks,
David

[danderson3]

BTW, my source directory is linux-2.6.17. Do I have to
rename this?

David

[hfdragon]

now when I dpkg -i kernel-headers-2.6.17.7_686_i386.deb

I get the error:

dpkg: error processing kernel-headers-2.6.17.7_686_i386.deb (--install):
cannot access archive: No such file or directory
Errors were encountered while processing:
kernel-headers-2.6.17.7_686_i386.deb

How can I debug this?

I remember having this problem... I just forgot to "cd .." befor "dprkg -i ..."

When we make the .deb files, we are in /usr/src/linux, but the .deb files are in /usr/src !!

Hope this helps.

[danderson3]

thanks, but I get the same error. I would like dpkg to be
more verbose...

David