[Bug 1084106] Re: highbank installer broken

[Colin Watson]

Hello Rob, or anyone else affected,

Accepted flash-kernel into quantal-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/flash-
kernel/3.0~rc.4ubuntu27.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from
verification-needed to verification-done.  If it does not, change the
tag to verification-failed.  In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: flash-kernel (Ubuntu Quantal)
       Status: Confirmed => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to flash-kernel in Ubuntu.
https://bugs.launchpad.net/bugs/1084106

Title:
  highbank installer broken

Status in The Eilt project:
  Triaged
Status in “flash-kernel” package in Ubuntu:
  Fix Released
Status in “flash-kernel” source package in Quantal:
  Fix Committed
Status in “flash-kernel” source package in Raring:
  Fix Released

Bug description:
  [Impact]

  It is possible to install neither highbank nor armadaxp on Quantal.
  This is a regression in Quantal, since this worked at release.

  [Test Case]

  Run the installer using the instructions at
  https://wiki.ubuntu.com/ARM/Server/Install, except use 12.10 images
  instead of 12.04.

  If successful, the installation should succeed. If this bug still
  exists, then the installer will fail with the following in
  /var/log/syslog:

  Dec 10 16:46:03 in-target: Setting up u-boot-tools (2012.04.01-2) ...
  Dec 10 16:46:04 in-target: update-initramfs: Generating /boot/initrd.img-3.5.0-17-highbank
  Dec 10 16:46:04 in-target: grep: /boot/config-3.5.0-17-highbank
  Dec 10 16:46:04 in-target: : No such file or directory
  Dec 10 16:46:04 in-target: WARNING: missing /lib/modules/3.5.0-17-highbank
  Dec 10 16:46:04 in-target: Device driver support needs thus be built-in linux image!
  Dec 10 16:46:04 in-target: WARNING: Couldn't open directory /lib/modules/3.5.0-17-highbank: No such file or directory
  Dec 10 16:46:04 in-target: FATAL: Could not open /lib/modules/3.5.0-17-highbank/modules.dep.temp for writing: No such file or directory
  Dec 10 16:46:04 in-target: FATAL: Could not load /lib/modules/3.5.0-17-highbank/modules.dep: No such file or directory
  Dec 10 16:46:04 in-target: FATAL: Could not load /lib/modules/3.5.0-17-highbank/modules.dep: No such file or directory
  Dec 10 16:46:05 in-target: FATAL: Could not load /lib/modules/3.5.0-17-highbank/modules.dep: No such file or directory
  Dec 10 16:46:06 in-target: FATAL: Could not load /lib/modules/3.5.0-17-highbank/modules.dep: No such file or directory
  Dec 10 16:46:08 in-target: Can't find /boot/vmlinuz-3.5.0-19-highbank or /boot/initrd.img-3.5.0-19-highbank
  Dec 10 16:46:09 flash-kernel-installer: error: flash-kernel failed
  Dec 10 16:46:09 main-menu[329]: WARNING **: Configuring 'flash-kernel-installer' failed with error code 1
  Dec 10 16:46:09 main-menu[329]: WARNING **: Menu item 'flash-kernel-installer' failed.

  [Regression Potential]

  This change affects flash-kernel-installer only, so can only affect
  d-i. d-i is completely broken for both highbank and armadaxp, so I
  don't see how it could get worse for these machines. For other
  machines, a regression would manifest itself as an installer failure
  only. We have verified that the new linux-version call works as
  expected in Quantal using network-console, so think that this is
  unlikely.

  Original description:

  It appears the installer for highbank is broken because 3.5.0-17 kernel
  is running and 3.5.0-18 is the current kernel version which is installed:

  Nov 13 16:14:43 in-target: Unpacking u-boot-tools (from .../u-boot-tools_2012.04.01-2_armhf.deb) ...
  Nov 13 16:14:44 in-target: Processing triggers for man-db ...
  Nov 13 16:14:46 in-target: Setting up u-boot-tools (2012.04.01-2) ...
  Nov 13 16:14:48 in-target: update-initramfs: Generating /boot/initrd.img-3.5.0-17-highbank
  Nov 13 16:14:48 in-target: grep: /boot/config-3.5.0-17-highbank
  Nov 13 16:14:48 in-target: : No such file or directory
  Nov 13 16:14:48 in-target: WARNING: missing /lib/modules/3.5.0-17-highbank
  Nov 13 16:14:48 in-target: Device driver support needs thus be built-in linux image!
  Nov 13 16:14:48 in-target: WARNING: Couldn't open directory /lib/modules/3.5.0-17-highbank: No such file or directory
  Nov 13 16:14:48 in-target: FATAL: Could not open /lib/modules/3.5.0-17-highbank/modules.dep.temp for writing: No such file or directory
  Nov 13 16:14:48 in-target: FATAL: Could not load /lib/modules/3.5.0-17-highbank/modules.dep: No such file or directory
  Nov 13 16:14:48 in-target: FATAL: Could not load /lib/modules/3.5.0-17-highbank/modules.dep: No such file or directory
  Nov 13 16:14:49 in-target: FATAL: Could not load /lib/modules/3.5.0-17-highbank/modules.dep: No such file or directory
  Nov 13 16:14:51 in-target: FATAL: Could not load /lib/modules/3.5.0-17-highbank/modules.dep: No such file or directory
  Nov 13 16:14:53 in-target: Can't find /boot/vmlinuz-3.5.0-18-highbank or /boot/initrd.img-3.5.0-18-highbank
  Nov 13 16:14:53 flash-kernel-installer: error: flash-kernel failed
  Nov 13 16:14:53 main-menu[328]: WARNING **: Configuring 'flash-kernel-installer' failed with error code 1
  Nov 13 16:14:53 main-menu[328]: WARNING **: Menu item 'flash-kernel-installer' failed.
  Nov 13 16:14:53 main-menu[328]: INFO: Modifying debconf priority limit from 'critical' to 'high'

To manage notifications about this bug go to:
https://bugs.launchpad.net/eilt/+bug/1084106/+subscriptions