I haven't used slackware for many years. There used to be a sticky thread with a great kernel compiling guide for slackware. It feels somewhat unnatural to me to use slackware without a shiny new kernel. Does that guide still exist? I'm working from memory right now.
I want to compile a kernel to add a few options that are not enabled in the huge-smp-2.6.29.6 that comes with slackware. specifically, i want to add TASK_DELAY_ACCT and TASK_IO_ACCOUNTING so that I can use iotop. I just want to add those 2 options to the new kernel, everything else I'd like to keep the way it is as the system has been running just fine. Will running 'make menuconfig' in /usr/src/linux default to the options that are used in the stock kernel?
I am currently having an issue installing the FGLRX driver in slackware 13.1. I use a customer kernel due to buggy acpi on my toshiba laptop. The steps i took to compile my kernel are as followed. hu
make mrproper in /usr/src/linux directory patch /usr/src/linux directory copy kernel config from /boot directory make menguconfig and load config the make all make modules install i have also tried make install as well then i mopy system.map the kernel file and config file into /boot directory edit lilo reboot ... everything works fine acpi works properly like before.. now the problem comes.. I try to install the fglrx drivers and i get the error message Code: Error: kernel includes at /lib/modules/2.6.33.4-smp/build/include do not match current kernel. they are versioned as "" instead of "2.6.33.4-smp". you might need to adjust your symlinks: - /usr/include - /usr/src/linux ERROR: I don't have make module Am I doing something wrong setting up my kernel. Issue on my gentoo box I have.
I compiled a kernel using a previous kernel config after I switched to the ext4 file system. Previously it was using ext3 and the kernel compiled and ran fine. I added support for ext4 to the config but when I went to boot I had a kernel panic. The error was "kernel can't mount vfs on (8,5)". Root is on sda5, I don't know what the 8 is. I started over, using mrproper and made a new config, but got the same error. I created an initrd with the ext4 file system but then the kernel said it couldn't mount root on ext3 because of unique options. (something along those lines) I booted back into the default kernel and saw that it had a similar error right after the bios check, but it loaded fine. I'm wondering why the kernel is saying that the ext4 file system is ext3.
Anyone able to compile kernel 2.6.38.6 on Slackware 13.37 successfully using the config from testing/2.6.38.4? I was able to get .4 and .5 to compile successfully, but with .6 I get the following after running "make modules".
Code: WARNING: modpost: Found 11 section mismatch(es). To see full details build your kernel with: 'make CONFIG_DEBUG_SECTION_MISMATCH=y' Running "make CONFIG_DEBUG_SECTION_MISMATCH=y 2>&1 > outfile" gives me a bunch of WARNINGS as follows:
Code: WARNING: vmlinux.o(.text+0xe656a): Section mismatch in reference from the function build_all_zonelists() to the function .meminit.text:setup_zone_pageset.clone.56() The function build_all_zonelists() references the function __meminit setup_zone_pageset.clone.56(). This is often because build_all_zonelists lacks a __meminit annotation or the annotation of setup_zone_pageset.clone.56 is wrong.....
WARNING: drivers/watchdog/nv_tco.o(.devinit.text+0x14): Section mismatch in reference from the function nv_tco_init() to the function .init.text:nv_tco_getdevice() The function __devinit nv_tco_init() references a function __init nv_tco_getdevice(). If nv_tco_getdevice is only used by nv_tco_init then annotate nv_tco_getdevice with a matching annotation.
i'm using this guide videos - howto: debian linux kernel compilation, part 1 and the author says i need kernel 2.6.26 this version of kernel doesnt longer exist in kernel.org website and the only 2.6.26 i found is a patch here. should i use the patch? or download another version of kernel?
so I am wanting to compile my own kernel to see if i can get my laptop to run a lill better. I found the how too's to do the compile, but what I want to know is.. what is the most complete way to find all the hardware and such that is in my laptop so i can build all the support into the kernel that i need and leave out EVERYTHING i dont need.
i figured lspci is a start but there has to be more info somewhere to find the exact needs of the laptop.
i want to compile and make kernel 1.0.0(the first kernel sources of linux) but its asking gas..... yup gnu assembler. i am using ubuntu 9.10 and if you ask why i am compiling this kernel.... because the truth is to study complete linux kernel.
I tried to compile an x86 linux kernel from amd64 machine. It is giving errors even after installing "gcc-multilib" But I wonder, it should be simply doable becuase "gcc -m32" creates 32 bit binary . I would prefer to compile it natively on x86_64 rather than creating an exclusive x86 chroot for that. Has anyone tried this on native x86_64?
I been trying all day to compile a kernel i downloaded from http://www.kernel.org/ (2.6.32.8 )Following this help thread viewtopic.php?t=4468.When i invoke make xconfig i'm just kinda lost at that point. Not really sure what to do, so i just save it as is and then compile/install.when i try to boot the kernel, a kernel panic happens saying it can't not mount the root partition.So i am sure i am missing a step with the xconfig part but not sure what.
I am trying to compile a vanilla kernel that I got from git in a VirtualBox VM running Fedora 12. With RHEL (albeit on real hardware, not a VM), I am able to do a make; make modules_install; make install and simply able to boot up the kernel. The make install step, in particular, creates the initrd using /sbin/installkernel, which also updates the grub configuration.
Under Fedora 12, my new kernel does not boot. I see no messages on the screen, not even if I change the boot command line to remove quiet bootup. I see disk usage on the VM and the CPU gets pegged at 100%. Strangely enough, if I change the initrd to refer to an existing, Fedora-provided kernel, I can boot my new kernel without any problems. I started with a Fedora kernel config and used it to generate the config for my new 2.6.33 kernel, so it couldn't be the case that I missed something in the config either.
Does anybody have an idea about what could be going on? Is there some specific patch that Fedora kernels use that are essential for booting up?
Also, the guest Fedora OS is 64-bit, if that is relevant.
I would like to try and optimize my kernel a bit. Since I am doing this on a fresh install, I don't really care if the os gets bricked in the process, and I am sure I can bring it back if I can boot into a recovery console from the old kernel. So, I followed thispost. I patched it and copied and edited a config file from /boot/, saved it as .config, I tried it several times with both removing and not removing /debian and /debian.master directories from the source, yet I always get the same error when I run "make oldconfig".
Code: $ make oldconfig scripts/kconfig/conf -o arch/x86/Kconfig *** Error during writing of the kernel configuration. make[1]: *** [oldconfig] Error 1
i downloaded the latest stable release of the linux kernel 2.6.39 and i did the following ran the command
Code:
make xconfig
and there were no errors so far so good
then i ran
Code:
make in the mix of all the command line and characters one of the lines said
Code:
stack protector enabled but no compiler support because of this the rest of the installation process is not going well i am unable to install the new linux kernel successfully. the kernel shows up on the grub boot menu but goes into a kernel panic when i try to boot it. how do i compile the new kernel in debian squeeze
I'm currently using Fedora 12 with kernel 2.6.31.9 and I was trying to upgrade to 2.6.32.2. These are the steps I followed. After rebooting and choosing this kernel from the Grub menu, I'm just greeted with a black screen with a blinking cursor and it won't proceed beyond that.
These are the commands I issued. I received an error on the first make modules about the mismatch. I then ran CONFIG_DEBUG_SECTION_MISMATCH=y and once finished I ran make modules again and it completed successfully.
Code: Downloaded kernel package 2.6.32.2 from www.kernel.org untar archive make menuconfig (no changes made, saved config file) make
I have been trying for few days on patching and compiling a Kernel, but got no success. I have been searching the web for pointers, but those I have found are very confusing. I did try them, yet same result. I am trying to patch and compile with the following:
I'm having problems to compile XIllybus kernel module. As this guide explains, [URL] ..... (on the top of page 8 of 25) I unpackaged the tar.gz file and compiled the kernel module by typing the make command in the proper path. When I compile the module with make command, I get the following error:
make -C /lib/modules/3.16.0-0.bpo.4-amd64/build SUBDIRS=/home/xillybus/module modules make: *** /lib/modules/3.16.0-0.bpo.4-amd64/build: No such file or directory. Stop. make: *** [default] Error 2
/lib/modules/3.16.0-0.bpo.4-amd64/build path does not exist. What does it mean? Should I have to install some kernel packet? www does not work for me.
I am completely new to compiling the kernel. Trying to compile on an old Dell C610 laptop that has Debian 6.01 installed and working. Here is what I have done so far:
Downloaded linux-3.0.tar.bz2 to home directory Also downloaded patch-3.0-git13 to home directory tar xjfv linux-3.0.tar.bz2 which uncompressed the tar ball in the created the linux-3.0 directory in my home directory
So I completely fail at making a kernel x86_64, used to make them fine for just x86 but I haven't a clue on how to make them specifically for 64-bit systems.
I am having some issues compiling kernel modules against the pre-built OpenSUSE kernel. Whenever I compile a module and try to load it, I get something like:
Code: insmod fs/smbfs/smbfs.ko insmod: error inserting 'fs/smbfs/smbfs.ko': -1 Invalid module format It doesn't actually matter what the module is, they all do the same thing. I have tried the above mentioned smbfs, I've also tried:vmware kernel module
I'm trying to compile a "faster", more optimized kernel. It compiles ok, but can't mount the root filesystem.Here is my kernel configuration for the 2.6.33.4 kernel. My boot partition is ext4 on a two-disk FakeRAID array totaling 1TB.When trying to boot in recovery mode, it says I could mount /dev/sdaX, etc. but can't recognize my dmraid array. BTW,
I'm trying to set it up so that I don't have to recompile the driver for my RAID card manually every time there is a kernel upgrade.I found a thread on it, here and a help page here, and it looks like it builds the module fine, but for some reason it's not being inserted into the new kernel, or something. It's like the new kernel doesn't know it exists, even tho modprobe -l shows the newly built module exists (and is in the correct place)Here's the script that I wrote up to get the drivers set up in DKMS:
this is my x-th attempt to compile the kernel on debian lenny. after solving the damn LGUEST issue, now i got an --append-to-version=-foobar issue?! damn... much time wasted, again. after make menuconfig and make-kpkg clean i start compiling with
EDIT: since this is debian specific and i used make -j5 etc. for # of jobs in other distros, is there an option on make-kpkg for that? && any chance for resuming?
I am in verse to compile a new kernel 2.6.34-rc5 on RHEL 6 Beta.I have been following [URL] for the same. how can i select all the options during :
Code: make menuconfig/make gconf/make xconfig
I just saved it under .config and when I ran : make modules it threw errro saying "modules not included". So i want to select complete options during make xconfig.
I update my last kernl to 2.6.38-rc7 but when I launch VirtualBox, on stdout.The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (2.6.38-rc7) or it failed to load. Please recompile the kernel module and install it by sudo /etc/init.d/vboxdrv setup.
It has been years since I have need to compile the kernel or its modules. Here goes: I recently upgraded to ubuntu 10.10 and needed the kernel source and its modules source. The relevant directories are in a mess. Several diff versions, broken links, the works. Is there a nice easy way, to remove all of the sources, there, and err "install" the ones for my latest kernel, in the correct places. Then I might have a chance at getting the two modules I need complied! Nvidia being one for the geforce 4 mx420 nv17