Joan a 13:58, 3 feb 2009

2009-02-03T13:58:52Z

Pàgina nova

Tinc acabat d'instal.lar el Ubuntu Studio 8.04, que té el kernel 2.6.24-19-rt
<pre>
$ ls /usr/src
linux-headers-2.6.24-19 linux-headers-2.6.24-19-generic
$ ls /boot
config-2.6.24-19-rt initrd.img-2.6.24-19-rt memtest86+.bin vmlinuz-2.6.24-19-rt
grub initrd.img-2.6.24-19-rt.bak System.map-2.6.24-19-rt
</pre>

Miro la meva tarja de so internal
<pre>
$ cat /proc/asound/cards
0 [ICH6 ]: ICH4 - Intel ICH6
Intel ICH6 with STAC9752,53 at irq 16
</pre>

El primer mètode va funcionar aparentment bé, seguint pas a pas, i podia arrencar la màquina amb tres kernels: 2.6.24-19-rt, 2.6.24-21-rt i 2.6.24-22-rt

però en un dels kernels (ara no recordo quin) estava totalment desconfigurat tot el sistema de so (ls /proc/asound/cards) no existeix, i en el que funciona reconeix bé l'EDIROL UA-25EX en el mode normal, però no en el mode avançat (no s'ha aplicat bé el patch del kernel, recordem que l'objectiu es poder treballar amb la UA-25EX en mode avançat per tal que funcioni el MIDI).

Seguiré ara el howto del Sergi Tur [http://acacha.dyndns.org/mediawiki/index.php/Kernel_Linux._Compilaci%C3%B3], que respon a un mètode més clàssic i usual.

També segueixo la informació de [http://www.howtogeek.com/howto/ubuntu/how-to-customize-your-ubuntu-kernel/ http://www.howtogeek.com/howto/ubuntu/how-to-customize-your-ubuntu-kernel/]. Compte perquè aquest enllaç m'ha proporcionat dues o tres modificacions interessants respecte l'article original

Informació oficial: un cop m'hagi baixat el kernel source, disposaré del document /usr/share/doc/kernel-package/README.gz, que podré accedir fent: $ zless README.gz (ben explicat)

== Obtenció del kernel (les fonts) ==

<pre>
$ sudo apt-get install build-essential fakeroot kernel-package
$ sudo adduser joan src
$ su joan
$ groups
</pre>

Find the kernel source you want with
<pre>
$ apt-cache search source 2.6
...
linux-source-2.6.24 - Linux kernel source for version 2.6.24 with Ubuntu patches
</pre>

Download the kernel source using the following command.
<pre>
sudo apt-get install linux-source
</pre>
Són 47Mb. Les fonts les posa a /usr/src, i aquí trobem el fitxer '''linux-source-2.6.24.tar.bz2''', és a dir, disposem de la revisió 24

If you see a link called linux to an older kernel source remove it [No és el meu cas]

Desempaquetem:
<pre>
$ tar jxvf linux-source-2.6.24.tar.bz2
</pre>
es crea el directori linux-source-2.6.24 que pertany a joan i al grup src. Creem el link 'linux' que apunta a aquest directori
<pre>
ln -s linux-source-2.6.24 linux
</pre>

== Configuració del kernel ==

There are several ways to configure the kernel. You will probably use "xconfig". Perform the following steps prior to configuring the kernel:

Dins de /boot existeix el fitxer config-2.6.24-19-rt, que representa la configuració del meu kernel ajustat a les necessitats rt (real-time)
Partiré d'aquest fitxer config per fer la meva configuració particular (si calgués). Per fer-ho, s'ha de copiar a /usr/src/linux (compte perquè en el howto original no queda clar aquest pas)

<pre>
$ cd /boot
$ find .config -type f -print | xargs egrep -i RT | more -> vull mirar de quina manera el meu config file està adaptat a 'RT' (realtime). De totes maneres, m'és molt difícil veure-ho
$ uname --kernel-release
2.6.24-19-rt -> és el meu kernel, i el que he de fer és partir d'aquesta configuració
$ cd /usr/src/linux
$ cp /boot/config-`uname --kernel-release` ./.config -> copio el config original a /usr/src/linux
</pre>

There are two ways to configure the kernel - using an X-based menu or using an ncurses (command-line) menu. To use the X-based menu [d'entrada no funciona, probaré l'altra possibilitat]:

<pre>
$ sudo apt-get install qt3-dev-tools libqt3-mt-dev
$ /usr/src/linux$ make xconfig
</pre>

2a possibilitat. If you are not using X, or don't want to use your mouse:

<pre>
$ sudo apt-get install libncurses5-dev
$ /usr/src/linux$ make menuconfig
</pre>

En la pantalla del ncurses escollir a ''Load an Alternate Configuration File'' el fitxer .config que hem copiat (potser no caldria fer-ho, però per si de cas...)

Assegurar-me de què està activat el mòdul USB-Audio:

go to Device Driver->Sound->Alsa->USB and activate the module USB-Audio.

=== Aplico el patch ===

el fitxer '''usbquirks.h''', que és el que s'ha de modificar, està a /usr/src/linux/sound/usb

El fitxer.diff és:
<pre>
--- sound/usb/usbquirks.h.00 2007-11-28 02:15:11.000000000 -0700
+++ sound/usb/usbquirks.h 2007-11-28 02:17:51.000000000 -0700
@@ -1311,6 +1311,37 @@
}
},
/* TODO: add Edirol MD-P1 support */
+{ /*
+ * This quirk is for the "Advanced" modes of the Edirol UA-25EX.
+ * If the switch is not in an advanced setting, the UA-25EX has
+ * ID 0x0582/0x00a4 and is standard compliant (no quirks), but
+ * offers only 16-bit PCM at 44.1 kHz and no MIDI.
+ */
+ USB_DEVICE_VENDOR_SPEC(0x0582, 0x00e6),
+ .driver_info = (unsigned long) & (const struct snd_usb_audio_quirk) {
+ .vendor_name = "EDIROL",
+ .product_name = "UA-25EX",
+ .ifnum = QUIRK_ANY_INTERFACE,
+ .type = QUIRK_COMPOSITE,
+ .data = (const struct snd_usb_audio_quirk[]) {
+ {
+ .ifnum = 0,
+ .type = QUIRK_AUDIO_EDIROL_UA700_UA25
+ },
+ {
+ .ifnum = 1,
+ .type = QUIRK_AUDIO_EDIROL_UA700_UA25
+ },
+ {
+ .ifnum = 2,
+ .type = QUIRK_AUDIO_EDIROL_UA700_UA25
+ },
+ {
+ .ifnum = -1
+ }
+ }
+ }
+},
{
/* Roland SH-201 */
USB_DEVICE(0x0582, 0x00ad),
</pre>

<pre>
$ sudo apt-get install patch
$ patch < fitxer.diff
patching file usbquirks.h
</pre>

Visualitzem que s'han realitzat els canvis
<pre>
$ ls -la usbquirks.h
-rw-r--r-- 1 joan joan 46928 2008-10-24 13:56 usbquirks.h
$ find usbquirks.h -type f -print | xargs egrep -i UA-25EX
</pre>

== Compilació del kernel ==

L'objectiu és crear un paquet Debian (.deb) del tipus ''kernel-image-2.6.8.1.181004_10.00.Custom_i386.deb'', que més tard instal.larem

make-kpkg

To build the kernel you'll invoke "make-kpkg", a script which automates and replaces the sequence "make dep; make clean; make bzImage; make modules". Take a few minutes and read over the manual page for make-kpkg. The make-kpkg command line can be complex and at first intimidating. Its basic syntax is

<pre>
/usr/src/linux$ make-kpkg
</pre>

Your target will be "kernel_image". Let's examine two of the more important and common options, "--append-to-version" and "--revision".

'''--append-to-version'''

The first option lets you specify an addition to the kernel version, which then becomes part of the kernel's name. You may use alphanumeric characters, "+" and "." (period or full stop); do not use underscore "_".

Here's the kernel I'm running now:

<pre>/usr/src/linux$ /usr/src/$ uname -a</pre>
Linux ubuntu 2.6.24-21-rt #1 SMP PREEMPT RT Mon Aug 25 19:24:40 UTC 2008 i686 GNU/Linux

You should avoid using --append-to-version values such as "-686", "-K7", and "-sparc". They are commonly used for Debian pre-compiled kernels.

Kernel modules live in subdirectories of /lib/modules; each kernel has its own subdirectory. Every time you install a kernel image with a new name, the package installer creates a new subdirectory of /lib/modules to hold its modules.

This means that by using a new value for --append-to-version each time you build a kernel image, you can ensure that the new kernel will have a new name, and that its modules won't conflict with those of other kernels.

If you install a kernel with the same name (the same version and --append-to-version) as an already-installed kernel, installing the new kernel package will overwrite the old kernel and its modules. You will be warned and offered the chance to abort. Take it. Use another value for --append-to-version and rebuild.

'''--revision'''

Another make-kpkg option is "--revision", which affects the name of the Debian package itself but not the kernel name. As with --append-to-version, you may use only alphanumeric characters, "+" and ".". Do not use underscores "_". If you do not supply a value for --revision, make-kpkg will use "10.00.Custom".

Using different values of --revision will not prevent conflicts between kernels with the same name. They are just for you to see the difference, for example recompiling the same kernel with a very small change.

'''Kernel package names'''

Debian kernel-image file names have the form

<pre>kernel-image-(kernel-version)(--append-to-version)_(--revision)_(architecture).deb</pre>

The package name is everything before the first underscore.

per ex,

<pre>kernel-image-2.6.8.1.181004_10.00.Custom_i386.deb</pre>

Now you can see why underscores are not allowed in make-kpkg options — they separate the elements of package names.

I recommend using a different --append-to-version value for each kernel you compile, and letting make-kpkg assign the default revision. Date-based values work for me, but you are free to invent your own scheme.

Please read /usr/share/doc/kernel-package/README.gz if --append-to-version or --revision is unclear, or if you plan on using options different from the ones I suggest. (One way to do this is "zless README.gz".) Ignore the discussions of flavours and epochs until you are more familiar with make-kpkg and with Debian packages generally; they are not likely to be useful to you now.
[Compte amb això últim, perquè precisament el que jo vull fer és compilar un kernel amb el ''rt flavour'']

'''fakeroot'''

When you added yourself to the src group you made it possible to do most kernel-package work with normal user privilege. However the files that are part of a kernel package (like the kernel and kernel modules) will be owned by root and run with root privilege; they must be created with root privilege.

Using fakeroot you can start make-kpkg as a normal user, and most of the job will be run with normal permissions. Near the end of the job, fakeroot will simulate a root environment to create the kernel-image package.

The manual page for make-kpkg describes one way to use fakeroot; we will use the simpler method of putting "fakeroot" at the beginning of the make-kpkg command line, like this:

fakeroot make-kpkg <options> <target>

Making the kernel image

Finally! The time has arrived — you're ready to make the kernel image.

<pre>/usr/src/linux $ fakeroot make-kpkg clean</pre>

Then do:

<pre>/usr/src/linux $ fakeroot make-kpkg --append-to-version=.241008 kernel_image --initrd binary</pre>

Now all you can do is wait for the computer to finish. Take a few minutes off and enjoy yourself while the computer does its fair share of the work.

== Instal.lació del paquet del kernel-image (el .deb) ==

Once the kernel image is built you will install the kernel-image package, which includes the kernel and its modules. First check to make sure it was built successfully by changing to the /usr/src directory and listing its contents:

<pre>
/usr/src/linux$ cd ..
/usr/src$ ls
linux-image-2.6.24.3.181004_2.6.24.3.181004-10.00.Custom_i386.deb
linux-source-2.6.24/
linux-source-2.6.24.tar.bz2
</pre>

There it is! Notice how the --append-to-version value became part of the kernel name.

To install the kernel and all its modules:

<pre>
/usr/src$ sudo dpkg -i linux-image-2.6.24.3.181004_2.6.24.3.181004-10.00.Custom_i386.deb
</pre>

To install a kernel-image package from disk (as opposed to installing from a Debian archive) use the full file name. You can use tab for command-line-completion.

M'ha donat un error...
<pre>
Desempaquetando linux-image-2.6.24.3.181004 (de linux-image-2.6.24.3.181004_2.6.24.3.181004-10.00.Custom_i386.deb) ...
Done.
dpkg-deb: fin de fichero inesperado en entre números en linux-image-2.6.24.3.181004_2.6.24.3.181004-10.00.Custom_i386.deb
dpkg: error al procesar linux-image-2.6.24.3.181004_2.6.24.3.181004-10.00.Custom_i386.deb (--install):
el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2
</pre>

If everything went well, all you need to do now is reboot. If your new kernel doesn't boot, boot your previous kernel or insert your boot floppy and restart. Go back to Configuring the kernel, tweak your configuration, and try again. Wrapping it all up Hold that kernel!

If you used --append-to-version you shouldn't need to worry about apt-get trying to "upgrade" your kernel. If you're paranoid (it is out to get you) you can make sure by doing this:

<pre>
$ echo "kernel-image-2.6.8.1.181004 hold" | sudo dpkg --set-selections
</pre>

Of course substitute the real name of your kernel. To refer to a package that dpkg knows about (an installed package or one in an archive's list) use the package name rather than the full file name. Check that the package really is on hold; if it is you should see:

<pre>
$ dpkg --get-selections | grep kernel-image
kernel-image-2.6.8.1.181004_10.00.Custom_i386.deb hold
</pre>

Somebody should write about holding packages, what it does etc.

'''Removing the symlink'''

Next, you should get rid of the symlink you created in the /usr/src directory. There are several reasons for this:

1. The next time you download a kernel it might not be from a Debian archive. When you expand the source tarball it could overwrite your old source tree right through the old symlink. Bummer.
2. The next time you download the kernel source from the Debian archive, you might expand the source into its own tree without problems. But since you already have a symlink called "linux" in the src directory, you might go ahead and compile (forgetting of course that it's linked to your old source tree.)
3. When you download patches or other source code into a specific source tree, you don't want anything else messing with it. By removing the symlink you might prevent 1. 1 from happening.

To remove the link do this:

<pre>
$ rm /usr/src/linux
</pre>

Now reboot. Running "cat /proc/version" should tell you if you're running under your new kernel.

==Per acabar, més coses==

===Backing up your kernel===

While not required, it's a good idea to back up your custom kernel .deb. Copy it to a secure undisclosed location.

Once your kernel has been packaged with its modules, you can install it on any machine that has the hardware you specified in your kernel configuration. You could even reinstall it on your current machine after reinstalling your system. Making a new boot diskette

Create another boot diskette, this one for the kernel you just installed. Grab another floppy — it's not a good idea to overwrite your old boot disk; you haven't been using your new kernel long enough to be sure it works. A boot disk is only necessary if you messed up your system.

<pre>
/usr/src# cd /boot
/boot# mkboot /boot/vmlinuz-2.4.18.030320
</pre>

===Building your next kernel===

If you want to rebuild your kernel because you just bought a new sound card, or you want to enable a new feature you forgot to include the first time, all you need to do is reconfigure, do "fakeroot make-kpkg clean", and rebuild with a different value for --append-to-version. Your session should look something like this:

<pre>
$ cd /usr/src
bash:/usr/src$ ln -s linux-source-2.6.8.1 linux
bash:/usr/src$ cd linux
bash:/usr/src/linux$ make xconfig
(reconfigure your kernel)
bash:/usr/src/linux$ fakeroot make-kpkg clean
(lots of cleaning here)
bash:/usr/src/linux$ fakeroot make-kpkg --append-to-version=.181004 kernel_image --initrd binary
(screens and screens of stuff)
</pre>

===Using an existing configuration===

When you installed your custom kernel, its configuration was copied to /boot/config-x.y.z. You may want to squirrel it away in another location (or several other locations) for safekeeping or later re-use.

Suppose that just last week you picked your way through the maze of options, and settled on a configuration that supports all the hardware and features you want. Today a new stable kernel is released and of course you want to upgrade right away. Is it necessary to start from scratch configuring the new kernel? Not at all.

Download and expand the new source tarball and make a new symlink. Then change directory to /usr/src/linux, copy your existing configuration there and do "make oldconfig":

bash:/usr/src/linux$ cp /boot/config-2.4.18.030320 .config
bash:/usr/src/linux$ make oldconfig

You'll be asked questions about new kernel options. It's generally safe to answer "no" to all the questions; make notes of the new options that interest you.

After you finish oldconfig you can run xconfig or menuconfig to review your selections, change your answers, or investigate the options you noted.

Build the latest stable kernel with your own configuration.

fakeroot make-kpkg clean

Checklist

1. Make backup boot diskette.
2. Install required packages.
3. build-essential fakeroot kernel-package
4. Setup source tree.
5. Add yourself to src. Logout, login. Use groups to confirm.
6. Remove old symlink.
7. Expand source tarball.
8. Make and check new symlink.
9. Configure kernel.
10. Use old config file if available. cp /boot/config-x.y.z .config
11. make oldconfig or make xconfig or make menuconfig.
12. Save .config file somewhere else for later use.
13. Build kernel-image package.
14. fakeroot make-kpkg clean
15. fakeroot make-kpkg --append-to-version=alpha+numeric.but.no.underscore kernel_image --initrd binary
16. Install kernel-image package.
17. dpkg -i kernel-image-x.y.z.yy.mm.dd_10.00.Custom_i386.deb
18. Reboot.
19. What next?
20. Hold your package. echo "kernel-image-x.y.z.yymmdd hold" | dpkg --set-selections
21. Remove symlink.
22. Back up kernel image.
23. Remove old kernel image packages.
24. Make new boot diskette.

Outside Links

Here are some links to other ways of building the kernel.

*[WWW] Ben Edwards Article
*[WWW] Debian Kernel 2.6 How To
*{OK} [WWW] Creating custom kernels with Debian's kernel-package system

{{Autor}}, octubre 2008
[[Categoria: Kernel]]
[[Categoria: Ubuntu Studio]]
[[Categoria: Linux]]
[[Categoria: Llenguatge C]]

Compilació del Kernel amb Ubuntu Studio 2n mètode - Historial de revisió

Joan a 13:58, 3 feb 2009