No description
Find a file
Eugene Shatokhin 3e9fece6bd DKMS operations should be tied to kernel-<...>-devel packages
Before this commit, DKMS was called to build and install the external
kernel modules when kernel-<flavour> packages were installed, and
only if the development files were also available.

This is error-prone because there is no guarantee the -devel package
creates the necessary files before. As a result, some proprietary
drivers could not be built when the kernel is updated.

This is an attempt to fix the problem. Because kernel-<flavour>-devel
package is enough to build kernel modules with DKMS, I moved these build
and install operations to kernel-<flavour>-devel from kernel-<flavour>.
Some of the related code was simplified as well.
2015-04-21 15:35:28 +03:00
.abf.yml Updated to 3.14.39 2015-04-20 21:14:22 +03:00
cpupower-start.sh cpupower: Select the governor at start time rather than during install 2015-03-13 17:29:40 +03:00
cpupower.config cpupower: Select the governor at start time rather than during install 2015-03-13 17:29:40 +03:00
cpupower.path Make sure cpupower starts after the list of governors is available 2015-03-17 20:53:12 +03:00
cpupower.service Make sure cpupower starts after the list of governors is available 2015-03-17 20:53:12 +03:00
disable-mrproper-prepare-scripts-configs-in-devel-rpms.patch Updated to version 3.14.10 2014-07-11 16:00:31 +04:00
kernel.rpmlintrc Automatic import for version 3.10.19-1 2013-11-16 00:27:01 +04:00
kernel.spec DKMS operations should be tied to kernel-<...>-devel packages 2015-04-21 15:35:28 +03:00
linux-3.14.tar.sign Updated to version 3.14.10 2014-07-11 16:00:31 +04:00
patch-3.14.39.sign Updated to 3.14.39 2015-04-20 21:14:22 +03:00
README.kernel-sources Updated to version 3.14.10 2014-07-11 16:00:31 +04:00

Hello Mandriva, OpenMandriva, MagOS and Rosa Linux Users,

linux-userspace-headers contains the headers for the source code of
Linux kernel. All source code necessary to compile a new kernel is
included in two packages linux-userspace-headers, and kernel-source.
You will need to install both linux-userspace-headers (needed for
general Linux compilation), and kernel-source in order to compile
a new kernel.

The kernel is the central process of your Linux machine, the mediator
between the hardware and your programs. It is responsible for memory
allocations, process managing, device access...

Although modern kernels are very flexible thanks to dynamic modules, you
may need to compile your own kernel for various reasons: your found a
new module which need a more recent kernel, you need a feature of a new
kernel, etc...

Here is a short sum-up of what you can find in the Kernel-HOWTO. Consult
it in case of a problem or if the shortcut here provided does not meet
your needs. You should also consult the README of kernel-sources.



1. Configure your new kernel

You should never build a kernel as root, so as a normal user:
Copy the source in /usr/src/linux/ to ~/kernel/
Change to ~/kernel/ and clean-up previous compilations, by issuing 
"make mrproper",
In console mode, run "make menuconfig",
Under X11, run "make xconfig".

Then configure all sections of your kernel making each feature you need
available constantly or as a module. Note that you should compile most
features as a module, as it consume less memory, taking into account
that some of them cannot be modules as you may need them at boot time,
before dynamic modules be loaded...



2. Compile it

Just issue "make" to create a compressed kernel image and the modules you 
configured.



3. install your new kernel

Now you need root privilegies, so:
Issue "su" and enter root password.
Issue "make modules_install"

This will copy your modules and needed files to /lib/modules/

Issue "make install"

This will copy your new kernel and system.map to boot dir (/boot/) with
correct names including version, and change respective links.

It finally runs lilo to take into account your new kernel.



4. Modify Lilo to allow your booting on old kernel

* This step is optional, although recommended *
See lilo.conf man page.
Your are encouraged during this step to create a new section in your
lilo.conf file, in order to enable you to boot on your both kernels, the
old and the new one.
You need to run lilo then to take your changes into account.
You may also use linuxconf to do all that with a nice GUI.



5. Reboot your machine...

And pray.
Anyway if something goes wrong, you just need to reboot and choose your
old kernel with lilo.

Enjoy!


========================================================================
(c) 1999-2006 Mandriva, Camille B<>gnis <camille@mandriva.com>
(c) 2006 Thomas Backlund <tmb@mandriva.org> 
(c) 2011 Thomas Backlund <tmb@mageia.org> 
(c) 2011 Nicol<6F> Costanza <abitrules@yahoo.it>