kernel-packages team mailing list archive

[Shaun Turnbull <993164@xxxxxxxxxxxxxxxxxx>]

This error is reproducable on my hardware  >=12.04.2 with EFI mode on.
Am posting this from 13.04 amd 64 desktop live session because of this
error and others possibly associated with it.  Using ga a75 ud4h mobo
with latest firmware which uses EFI 1.1 rev 2 specification firmware.
rEFInd sees this as ver UEFI 2.1.  Using msinfo32 and windows upgrade
assistant confirm this firmware/hardware is not Secure Boot capable.

Searching Ask Ubuntu this bug may have regressed/resurfaced since 12.04.2/12.10. (http://askubuntu.com/search?tab=votes&q=you%20need%20to%20load%20kernel%20first).
One similar question there http://askubuntu.com/q/206950/102029 links to this wiki http://web.dodds.net/~vorlon/wiki/blog/SecureBoot_in_Ubuntu_12.10/ which i have found helpful in getting confidence to post my first bug comment here.
The article talks of first stage and second stage boot loaders as well as shim.  Realise shim is Secure Boot related so is not the issue on this hardware but do not understand first stage and second stage boot loaders.
 Do know rEFInd sees BIOS/legacy bootloaders on media as "fallback loaders".  I am guessing this is second stage bootloader.  Which means if first stage loader is the signed.efi image then there is no usable .efi image to use on my hardware.
How to EFI install Ubuntu on a system that is EFI capable but is not Secure Boot capable? 
Understand 11.04 11.10 want to make 16bit EFI partition if installing to a completely unallocated space drive which would mean fixing before trying to boot to - source http://www.rodsbooks.com/gb-hybrid-efi/ which is a different story.  

I can not boot any Ubuntu installer using EFI mode on this hardware. I asked this  http://askubuntu.com/questions/208405/how-to-efi-install-ubuntu which links to thread over on Ubuntu Forums to try and find a working solution or a conclusion that explains why not!    
13.04 installed using legacy settings although EFI was on which indicates the expected sequence described in http://web.dodds.net/~vorlon/wiki/blog/SecureBoot_in_Ubuntu_12.10/ However i can not replicate this and have never booted any Ubuntu installer using EFI mode on this hardware.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/993164

Title:
  error file not found you need to load the kernel first failed to boot
  both default and fallback entries

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  after upgrading to this kernel, the VM under ESXi 5.0 fails to boot
  the new kernel

  You have to boot from a live cd and uninstall the kernel to fix.
  Reverting to 2.6.32-40 solves the issue so this is a regression
  2.6.32-41

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: linux-image-2.6.32-41-server (not installed)
  Regression: Yes
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.32-40.87-server 2.6.32.57+drm33.23
  Uname: Linux 2.6.32-40-server x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  Date: Wed May  2 10:59:35 2012
  InstallationMedia: Ubuntu-Server 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:
   
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-40-server root=UUID=715b5cff-4255-40e6-ae71-e5cd7c7dc913 ro
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux
  dmi.bios.date: 01/07/2011
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd01/07/2011:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/993164/+subscriptions