hank-test/quick-docs
1
0
Fork 0
mirror of https://pagure.io/fedora-docs/quick-docs.git synced 2024-12-01 07:39:48 +00:00
Code Issues 1 Projects Releases Packages Wiki Activity Actions

Merge #54 Add some polish to the kernel quick docs

Browse source
This commit is contained in:
Mirek Jahoda 2018-06-22 11:29:05 +00:00
commit bc8c04ddb4
2 changed files with 24 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
en-US/kernel/build-custom-kernel.adoc
View file

@ -37,6 +37,13 @@ cd kernel
sudo dnf builddep kernel.spec sudo dnf builddep kernel.spec
---- ----
If you want to use `make xconfig`, you'll need some additional packages:
[source,bash]
----
sudo dnf install qt3-devel libXi-devel gcc-c++
----
Make sure you add the user doing the build to `/etc/pesign/users` and run the Make sure you add the user doing the build to `/etc/pesign/users` and run the
authorize user script: authorize user script:
@ -205,13 +212,13 @@ look at the `Configuration targets` for the full list, but `make menuconfig`
is a good place to start. You can also just edit the `.config` file directly. is a good place to start. You can also just edit the `.config` file directly.
[NOTE] [NOTE]
====
If you plan to run `make xconfig`:
[source,bash] ====
----
sudo dnf install qt3-devel libXi-devel gcc-c++ One configuration option you may want to set is CONFIG_MODULE_COMPRESS, which
---- compresses the modules (with gzip by default) when installing them. Without
this setting, the modules can be very large.
==== ====
=== Building the kernel === Building the kernel

18
en-US/kernel/troubleshooting.adoc
View file

@ -22,8 +22,8 @@ boot process, there may or may not be any output. Some good first steps are:
* Add `initcall_debug` parameter, which traces the initcalls as they are * Add `initcall_debug` parameter, which traces the initcalls as they are
executed. executed.
* If you get no output at all from the kernel, sometimes booting with * If you get no output at all from the kernel, booting with `earlyprintk=vga`
`earlyprintk=vga` can sometimes yield something of interest. can sometimes yield something of interest.
== Hangs and freezes == Hangs and freezes
@ -68,7 +68,7 @@ version. The first version you find that doesn't work will be the initial "bad"
version. version.
. Install the <<build-custom-kernel.adoc#get-the-dependencies,dependencies>> . Install the <<build-custom-kernel.adoc#get-the-dependencies,dependencies>>
required to build the kernel required to build the kernel.
. Next, <<build-custom-kernel.adoc#getting-the-sources,get the source code>>. . Next, <<build-custom-kernel.adoc#getting-the-sources,get the source code>>.
@ -78,7 +78,13 @@ between major versions (e.g. `v4.16` and `v4.15`) new configuration options
will be added and removed as you bisect. It's _usually_ safe to select the will be added and removed as you bisect. It's _usually_ safe to select the
default.] default.]
. Start a new `git-bisect` with `git bisect start <bad> <good>`. . Start a new `git-bisect` with `git bisect start`.
. Mark the newest version that works as "good" with `git bisect good <tag>`.
For example: `git bisect good v4.16.8`.
. Mark the first version that does not work as "bad" with `git bisect bad
<tag>`. For example: `git bisect bad v4.17`.
. <<build-custom-kernel.adoc#building-the-kernel,Build the kernel>>. Sometimes . <<build-custom-kernel.adoc#building-the-kernel,Build the kernel>>. Sometimes
commits cannot be built. If this happens, skip the commit with `git bisect commits cannot be built. If this happens, skip the commit with `git bisect
@ -86,12 +92,10 @@ skip`.
. <<build-custom-kernel.adoc#installing-the-kernel,Install the kernel>>. . <<build-custom-kernel.adoc#installing-the-kernel,Install the kernel>>.
. Reboot into the new kernel and test to see if the it works. . Reboot into the new kernel and test to see if it works.
. If the new kernel works, mark it as good with `git bisect good`. Otherwise, . If the new kernel works, mark it as good with `git bisect good`. Otherwise,
mark it as bad with `git bisect bad`. mark it as bad with `git bisect bad`.
. Check out the next commit to test by running `git bisect next`.
. Repeat the previous five steps until you've found the commit that introduced . Repeat the previous five steps until you've found the commit that introduced
the problem. the problem.