You are not logged in.
Hi all,
After execute below command:
$ sudo mkinitcpio -p linuxBelow modules indicated, 'snd' and 'snd-rawmidi' modules are not found:
==> Building image from preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.6.11-1-ARCH
-> Running build hook: [base]
-> Running build hook: [usr]
-> Running build hook: [udev]
-> Running build hook: [block]
-> Running build hook: [resume]
-> Running build hook: [filesystems]
-> Running build hook: [usbinput]
==> ERROR: module not found: `snd'
==> ERROR: module not found: `snd-rawmidi'
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.6.11-1-ARCH
-> Running build hook: [base]
-> Running build hook: [usr]
-> Running build hook: [udev]
-> Running build hook: [block]
-> Running build hook: [resume]
-> Running build hook: [filesystems]
-> Running build hook: [usbinput]
==> ERROR: module not found: `snd'
==> ERROR: module not found: `snd-rawmidi'
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> WARNING: errors were encountered during the build. The image may not be completeLast edited by toni (2013-01-05 20:25:21)
Offline
In order to fix the problem, I have done:
sudo pacman -S linuxand then again, if I do:
$ sudo mkinitcpio -p linuxAll works again. No errors related to 'snd' and 'snd-rawmidi' modules are shown.
Hi all,
After execute below command:$ sudo mkinitcpio -p linuxBelow modules indicated, 'snd' and 'snd-rawmidi' modules are not found:
==> Building image from preset: 'default' -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img ==> Starting build: 3.6.11-1-ARCH -> Running build hook: [base] -> Running build hook: [usr] -> Running build hook: [udev] -> Running build hook: [block] -> Running build hook: [resume] -> Running build hook: [filesystems] -> Running build hook: [usbinput] ==> ERROR: module not found: `snd' ==> ERROR: module not found: `snd-rawmidi' ==> Generating module dependencies ==> Creating gzip initcpio image: /boot/initramfs-linux.img ==> WARNING: errors were encountered during the build. The image may not be complete. ==> Building image from preset: 'fallback' -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect ==> Starting build: 3.6.11-1-ARCH -> Running build hook: [base] -> Running build hook: [usr] -> Running build hook: [udev] -> Running build hook: [block] -> Running build hook: [resume] -> Running build hook: [filesystems] -> Running build hook: [usbinput] ==> ERROR: module not found: `snd' ==> ERROR: module not found: `snd-rawmidi' ==> Generating module dependencies ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img ==> WARNING: errors were encountered during the build. The image may not be complete
Offline
If you use OSS those mkinitcpio warnings will pop up. OSS replaces the alsa sound modules with its own, so they won't be missed. OSS tars up the entire /usr/lib/modules/`uname -r`/kernel/sound directory when it is installed and stores it in the file sound-preoss.tar.bz2. This is usually the only file left behind when a kernel is replaced. You can see what happens in the script /usr/lib/oss/scripts/remove_drv.sh.
Last edited by sonoran (2013-01-06 13:23:07)
Offline
Yes, I am using OSS. Many thanks for your information, so as I understand, each time a kernel is replaced, this file (sound-preoss.tar.bz2) is not taken into account, right? so is there any way to avoid those warnings to appear and get images to build correctly? I will try to analyse the script, thanks. Could you tell me if the fix that I have done is the correct in this case?
If you use OSS those mkinitcpio warnings will pop up. OSS replaces the alsa sound modules with its own, so they won't be missed. OSS tars up the entire /usr/lib/modules/`uname -r`/kernel/sound directory when it is installed and stores it in the file sound-preoss.tar.bz2. This is usually the only file left behind when a kernel is replaced. You can see what happens in the script /usr/lib/oss/scripts/remove_drv.sh.
Last edited by toni (2013-01-06 16:28:57)
Offline
I just ignore the warnings and have not, to my knowledge, suffered any consequences. On my system the warnings are sporadic - they don't occur on every kernel update.
There might be a setting in mkinitcpio.conf that would eliminate the warnings, but since the initramfs created has always worked despite the warnings, I haven't looked into it.
Blacklisting of the Alsa modules would be another area for investigation, if one had the time.
If your Arch has undergone several kernel updates you will find that the old kernel directories in /usr/lib/modules are not being deleted, because they still contain the sound-preoss.tar.bz2 archive where OSS stored the default kernel sound modules. At least that is what happens in my system. Every so often I just manually delete the directories for older kernels.
Offline