English Portuguese (Portugal)
Information for collecting logs is documented at the https://wayland.freedesktop.org/libinput/doc/latest/reporting-bugs.html[libinput website].
If you get no output at all from the kernel, booting with `earlyprintk=vga` can sometimes yield something of interest.
If the problem you've encountered isn't present in older versions of the kernel, it is very helpful to use `git-bisect` to find the commit that introduced the problem. For a general overview of `git-bisect`, see its https://git-scm.com/docs/git-bisect[documentation]. An outline on how to bisect the kernel is included in the https://www.kernel.org/doc/html/latest/admin-guide/bug-bisect.html[kernel documentation]. This guide contains Fedora-specific details.
If the new kernel works, mark it as good with `git bisect good`. Otherwise, mark it as bad with `git bisect bad`.
Hangs and freezes
Find the newest version you can that works. This will be the initial "good" version. The first version you find that doesn't work will be the initial "bad" version.
Checking whether or not the CapsLock key (or NumLock or ScrollLock) causes
Booting with vga=791 (or even just vga=1 if the video card won't support 791) will put the framebuffer into high resolution mode to get more lines of text on screen, allowing more context for bug analysis.
Boot failures
Bisecting the kernel
Bisecting is a time-consuming task, but it's very straightforward and is often the best way to find the cause of a problem. If you're really interested in getting the problem you're seeing fixed, bisecting will speed up the process considerably in most cases.
`alsa-info.sh` provides information about both kernel and userspace components. If you have a working and non-working kernel, you should provide `alsa-info.sh` for both cases.
Add `initcall_debug` parameter, which traces the initcalls as they are executed.