How To Compile the new 2.6.16 kernel from kernel.org

[haani]

does anyone know how to install drivers for intel ipw 3945 wireless in the new compiled kernel 2.6.17??

[PoisoN2003]

Is this supposed to be or something is wrong

find . -path './scripts/*' -prune -o -path './Documentation/*' -prune -o       \                -path './debian/*'  -prune -o -type f                          \                \( -name Makefile -o -name 'Kconfig*' \) -print |              \                  cpio -pd --preserve-modification-time debian/tmp-headers/usr/src/kernel-headers-2.6.16-ck12;
cpio: debian/tmp-headers/usr/src/kernel-headers-2.6.16-ck12/./Makefile not created: newer or same age version exists
cpio: debian/tmp-headers/usr/src/kernel-headers-2.6.16-ck12/./arch/i386/Makefile not created: newer or same age version exists
cpio: debian/tmp-headers/usr/src/kernel-headers-2.6.16-ck12/./include/asm-cris/arch-v32/hwregs/Makefile not created: newer or same age version exists
cpio: debian/tmp-headers/usr/src/kernel-headers-2.6.16-ck12/./include/asm-cris/arch-v32/hwregs/iop/Makefile not created: newer or same age version exists
5097 blocks
test ! -e arch/i386/kernel/asm-offsets.s ||             \
          install -p    -o root -g root -m 644 arch/i386/kernel/asm-offsets.s  \                debian/tmp-headers/usr/src/kernel-headers-2.6.16-ck12/arch/i386/kernel/asm-offsets.s
install -p    -o root -g root -m 644 .config            debian/tmp-headers/usr/src/kernel-headers-2.6.16-ck12/.config
echo k7                    > debian/tmp-headers/usr/src/kernel-headers-2.6.16-ck12/kernel-headers.revision
dpkg-gencontrol -DArchitecture=i386 -isp \
                        -pkernel-headers-2.6.16-ck12 -Pdebian/tmp-headers/
chown -R root:root debian/tmp-headers
chmod -R og=rX debian/tmp-headers
dpkg --build debian/tmp-headers ..
dpkg-deb: building package `kernel-headers-2.6.16-ck12' in `../kernel-headers-2.6.16-ck12_k7_i386.deb'.
rm -rf debian/tmp-headers
echo done >  stamp-headers
make[1]: Leaving directory `/usr/src/linux-2.6.16ck12'
for module in  ; do                       \
          if test -d  $module; then                                \
            (cd $module;                                          \
              if ./debian/rules KVERS="2.6.16-ck12" KSRC="/usr/src/linux" \
                             KMAINT="Unknown Kernel Package Maintainer" KEMAIL="unknown@unconfigured.in.etc.kernel-pkg.conf"      \
                             KPKG_DEST_DIR="/usr/src/linux/.."       \
                             KPKG_MAINTAINER="Unknown Kernel Package Maintainer"        \
                             KPKG_EXTRAV_ARG=""        \
                             ARCH="i386"                  \
                             KDREV="k7" kdist_image; then    \
                  echo "Module $module processed fine";            \
              else                                                  \
                   echo "Module $module failed.";                  \
                   if [ "X" != "X" ]; then      \
                      echo "Perhaps $module does not understand --rootcmd?";  \
                      echo "If you see messages that indicate that it is not"; \                      echo "in fact being built as root, please file a bug ";  \                      echo "against $module.";                     \
                   fi;                                              \
                   echo "Hit return to Continue";                   \
                 read ans;                                        \
              fi;                                                   \
             );                                                    \
          else                                                      \
               echo "Module $module does not exist";               \
               echo "Hit return to Continue?";                      \
          fi;                                                       \
        done
root@ubuntu:/usr/src/linux#

[ashrack]

which one do i install sincei get 2 deb files 1 image the other header?

Both of them!

well iget things like these from time to time while i compile is it bad?

fs/isofs/namei.c: In function ‘isofs_lookup’:
fs/isofs/namei.c:162: warning: ‘offset’ may be used uninitialized in this function
fs/isofs/namei.c:162: warning: ‘block’ may be used uninitialized in this function

its perfectly normal.

[xXx 0wn3d xXx]

Both of them!


its perfectly normal.

Yes, install both of them. It would be best to install the kernel_image first and then the kernel_headers second.

[PoisoN2003]

Yes, install both of them. It would be best to install the kernel_image first and then the kernel_headers second.

my last question i installed only 1 of them and when i launched the kernel teh xserver crashed so i reconfigured it but now when i try to reinstall the nvidia the next time i start the xserver crashes or sometimes it says its already installed
then when i do this
poison@ubuntu:~$ cat /proc/driver/nvidia/agp/status
cat: /proc/driver/nvidia/agp/status: No such file or directory

as u can see it hasnt found it
so any help i got nvidia 5600 fx ultra

oh and can i still install the header while im in teh kernel? or do i have to go back to my old one and install from there?

[OPaul]

Well it does. But in the UBUNTU kernels there are also a lot of custom patchs applied which are not in the VANILA kernel U are trying to compile. And its just possible that the support for TOSHIBA isnt in the default VANILA kernel.
U could verify this with the 'make oldconfig' command.

You need to copy the .config file to the folder containing the new source. From there you need to use the command I suggested

Well I don't understand, it's still not working for some reason. Now, ACPI_TOSHBIA, which handles the hotkeys, has a dot by it (being loaded as a module), so do I need to do something special perhaps to make the module load with the new kernel?

Also, I notice this when I run dmesg. On the original Ubuntu kernel, 2.6.15-25-686, (where the hotkeys work) I have the following.

[17179597.040000] toshiba_acpi: Toshiba Laptop ACPI Extras version 0.19a-dev
[17179597.040000] toshiba_acpi:     HCI method: \_SB_.VALD.GHCI
[17179597.044000] toshiba_acpi: Toshiba hotkeys are sent as ACPI events
[17179597.044000] toshiba_acpi: ktoshkeyd will check 2 times per second
[17179597.044000] toshiba_acpi: Dropped 0 keys from the queue on startup

But in 2.6.17.1 I only have this

[4294671.487000] toshiba_acpi: Toshiba Laptop ACPI Extras version 0.18
[4294671.487000] toshiba_acpi:     HCI method: \_SB_.VALD.GHCI

Also, the version numbers of acpi_toshiba are different. The older kernel has the newer copy.

[kakashi]

K well that completely drove me away from kernal compilation....

I dont know what I messed up but when I booted into the kernel it started in Failsafe. I logged in and when I went to start X it panicked. I booted my old kernel (2.6.12 ancient!) and THAT started in failsafe but X started at least. I uninstalled the package and now everything is back to normal. Think I'll wait till Dapper is released then do a fresh install of that so I have the latest kernel.

i suggest to everyone that you first try compiling the kernels a few times on a computer thats not your main one OR like i do in a vmwar. now that vmware server is freely available it is really easy to setup a nice test environment. once your comfortable with the process do it on your main system.

[tseliot]

Also, the version numbers of acpi_toshiba are different. The older kernel has the newer copy.

Ubuntu's kernels are heavily patched and I can't help you with that.

I have backported Edgy's 32bit kernels to Dapper (I haven't uploaded them anywhere yet). The only problem is making the restricted modules. After that problem is solved maybe I can upload everything.

[xpmaniac4ever]

Kernel 2.6.17 is out. Does this howto apply to this new version as well ? Or could someone please modify it to reflect the changes in the new version ?

[cfp999]

I was wondering about that too. My plan is to try and compile 2.6.17 + Con Kolivas' patch-2.6.17-ck1.bz2 although I have no idea what the latter does compared to Ubuntu's "native" patching. Will it be safe to assume, that I can boot a previous kernel in GRUB if something goes completely wrong?