You are not logged in.
Hello!
It seems, that systemd complains since the last release about a missing modules.devname during bootup:
Warning: /lib/modules/3.11.2-CUSTOM/modules.devname not found - ignoring
The message is not logged to journactl or dmesg. So keep your eyes open during booting!
I'm using a vanilla kernel from kernel.org, which I compile myself. The mentioned file is existing. My kernel installation process is pretty simple and has nevern been showing any problems:
1. tar -xf kernel.tar
2. cd linux-3.11.2
2. copy config
3. make oldconfig
4. make -j5
5. su
6. make modules_install
7. cp arch/x86_64/boot/bzImage /boot/vmlinuz-custom
8. mkinitcpio 3.11.2-CUSTOM -g /boot/initramfs-custom.img
9. reboot
I wonder if their is anybody else with this bug? How can I fix that?
Other Sources:
http://www.spinics.net/lists/linux-modu … 01079.html # log message, search for "warning"
http://lists.freedesktop.org/archives/s … 10470.html
http://lists.freedesktop.org/archives/s … 10470.html
https://lwn.net/Articles/564385/
// edit
Solution:
https://bbs.archlinux.org/viewtopic.php … 5#p1330705
Last edited by hoschi (2013-09-28 19:21:59)
Offline
Not sure about that but I would highly recommend that you build your kernel package with makepkg/pacman rather than by hand. Just edit the distro provided PKGBUILD (via ABS or whatever) and customize it.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Online
http://git.kernel.org/cgit/utils/kernel … des.c#n214 # responsible source
Offline
http://git.kernel.org/cgit/utils/kernel … des.c#n214 # responsible source
Glad you found the source of the message, but my recommendation is still true
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Online
Thanks for your recommondation, but I want stay with the traditional way:
https://wiki.archlinux.org/index.php/Ke … raditional
Offline
modules.devname is a file generated by depmod. If depmod doesn't generate one, it just means there were no devname aliases declared in the modules built with the kernel. Doesn't really matter how it was compiled.
systemd won't complain about this next release:
Offline
Thanks falconindy!
I solved it in meantime. I changed my mkinitcpio-commando to:
mkinitcpio -k 3.11.2-CUSTOM -g /boot/initramfs-custom.img -S autodetect # sets kernelversion instead of running kernel, skips hook autodetect
Rationale:
I was always to lazy to create a modified /etc/mkinitcpio.conf for my custom-kernel! This is my fault!
Skipping the hook autodetect fixed it. Using autodetect doesn't make any sense with a custom-kernel. Also I didn't used the -k option during some (if not all) of the last builds, depending on the current running kernel not using this option could lead to invalid results. By the way, both pages on the wiki for traditional and abs compilation didn't mention the modification of the mkinitcpio.conf. Maybe I should add some lines?
-k, --kernel kernelversion
Use kernelversion, instead of the current running kernel. This may be a path to a
kernel image or a specific kernel version.
-S, --skiphooks hooks
Skip hooks when generating the image. Multiple hooks should be comma-separated. This
option can be specified multiple times.
This should also prevent mkinitcpio to print this warning:
==> WARNING: No modules were added to the image. This is probably not what you want.
Last edited by hoschi (2013-09-28 19:26:25)
Offline