[solved] errors were encountered during the build. The image may not b

karol · 2014-07-28 22:49:22

(the title is cut off, which is a nice pun on the warning message ;P)
Updated my system, got brand new linux 3.15.7-1 and also got

==> WARNING: errors were encountered during the build. The image may not be complete.

when creating the initcpio. I did reboot anyway, seems to work fine.
I'm using [testing] and the new mkinitcpio 18-1.

Is it a bug or a feature? Does anyone else has this issue?

$ sudo mkinitcpio -p linux
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.15.7-1-ARCH
  -> Running build hook: [systemd]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [consolefont]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.15.7-1-ARCH
  -> Running build hook: [systemd]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: smsmdtv
  -> Running build hook: [filesystems]
  -> Running build hook: [consolefont]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.

BTW, does every new release of the kernel have to go through [testing] repo?

Last edited by karol (2014-08-03 11:05:12)

jasonwryan · 2014-07-28 22:57:13

Moving to [testing]...

karol · 2014-07-28 23:30:15

I did downgrade linux to 3.15.6-1 and got the same warning. Downgraded mkinitcpio to 17-1 and got no warning on either kernel.

anatolik · 2014-07-29 00:35:47

I wonder if it is related to the lzo2->lzo rename that is baking in [testing] right now. Could you please run 'pacman -Sy lzo' and then rerun mkinitcpio again?

karol · 2014-07-29 00:58:21

I've already installed lzo 2.08-2 48 hours ago. 'pacman -Sy lzo' simply reinstalled it. I did remove it from cache, downloaded and installed again.
Using both the stock Arch kernel presets and the -ck one results in the warnings with mkinitcpio to 18-1.

anatolik · 2014-07-29 01:17:56

Ok, it is not lzo problem. Could you please run mkinitcpio with '-v' flag (verbose output) and share it with us?

karol · 2014-07-29 01:33:25

$ sudo mkinitcpio -v -p linux 2&> m.log

The log: http://sprunge.us/MXgd

tomk · 2014-07-29 07:13:18

karol wrote:

does every new release of the kernel have to go through [testing] repo?

Yes - this applies to all packages in the core repo. For other repos, it is at the devs' discretion.

karol · 2014-07-29 14:17:01

I didn't see 3.15.7-1 in [testing], it must have been a very short stay.
Anyway, this issue seems to be with mkinitcpio, not with the kernel, although https://bbs.archlinux.org/viewtopic.php … 4#p1441064

Scimmia wrote:

Seems 3.15.7 is a binary module breaker and the modules haven't been rebuilt for it.

Last edited by karol (2014-07-29 14:18:46)

tomk · 2014-07-29 14:23:09

Scimmia is referring to out-of-tree modules only e.g. nvidia, virtualbox, etc.

karol · 2014-07-29 14:38:41

They should have been updated too, IMHO.
I'm not using any, but stuff breaking or not shouldn't be based on luck.

karol · 2014-08-03 11:02:13

Now using lzo 2.08-3 and the warnings are gone.
Marking as solved.

Arch Linux

#1 2014-07-28 22:49:22

[solved] errors were encountered during the build. The image may not b

#2 2014-07-28 22:57:13

Re: [solved] errors were encountered during the build. The image may not b

#3 2014-07-28 23:30:15

Re: [solved] errors were encountered during the build. The image may not b

#4 2014-07-29 00:35:47

Re: [solved] errors were encountered during the build. The image may not b

#5 2014-07-29 00:58:21

Re: [solved] errors were encountered during the build. The image may not b

#6 2014-07-29 01:17:56

Re: [solved] errors were encountered during the build. The image may not b

#7 2014-07-29 01:33:25

Re: [solved] errors were encountered during the build. The image may not b

#8 2014-07-29 07:13:18

Re: [solved] errors were encountered during the build. The image may not b

#9 2014-07-29 14:17:01

Re: [solved] errors were encountered during the build. The image may not b

#10 2014-07-29 14:23:09

Re: [solved] errors were encountered during the build. The image may not b

#11 2014-07-29 14:38:41

Re: [solved] errors were encountered during the build. The image may not b

#12 2014-08-03 11:02:13

Re: [solved] errors were encountered during the build. The image may not b

Board footer