kernel-packages team mailing list archive

[Shaun Turnbull <1072378@xxxxxxxxxxxxxxxxxx>]

This affects precise,quantal , and raring. Have not tried saucy yet.
Is there a way to confirm the  first stage installer are capable of running on an EFI system that is not secure boot capable?  Is shim required on non SecureBoot system?

I suspect if shim/ first stage installer are not able to run using .efi
image and are only looking for signed.efi criteria not finding either so
should drop to legacy/bios installer automatically but fall back
installer is not running either. is only speculation because do not know
the intended meaning of first and second stage installer-
ref:http://web.dodds.net/~vorlon/wiki/blog/SecureBoot_in_Ubuntu_12.10/

ga a75 ud4h mobo being used. When booting precise,quantal or raring with EFI on get to situation as described http://askubuntu.com/q/208405/102029 and several other related questions.  Searching ask ubuntu 
http://askubuntu.com/search?q=need+to+load+kernel+first+ confirms a recnt increase in these queries on differing hardware so this is almost a certain bug.

Doing ls -l  after dropping to command prompt when getting UEFI grub
screen ref
https://help.ubuntu.com/community/UEFI#Identifying_if_the_computer_boots_the_HDD_in_EFI_mode
confirms cd0,apple1 and cd0apple2 images are detected and might go some
way to explaining why they are not usable on an amd 64 platform.
running lsefisystab here also indicates EFI ver 1.1. rev 2 rEFInd sees
this firmware as UEFI 2.1 which goes to completely confirm this is not
Secure Boot capable system.

Confirm Christopher M. Penalver's workaround does work but i do not see
this as afull solution due to the lack of being to use efibootmgr when
booting live session- which has to be with EFI off due to installer bug.
No efi = no efibootmgr.  If dual booting with windows using this
workaround will mean having to simply create grub_bios partition,
install grub-efi and possibly rename windows bootfmgr to trick firmware
to booting grub-efi.  Using boot-repair seems to be the accepted and
easiest way of doing this but has hugely varying success rates.

-- 
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/1072378

Title:
  [Asus Eee PC 1015BXO] Ubuntu 12.10 EFI support is not ready

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  It crashes to the installation of grub (ASUS 1015BX, look screenshot)
  Here the hardware tested: http://kmuto.jp/debian/hcl/ASUS/1015BX+C-60

  ---
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu     3223 F.... pulseaudio
   /dev/snd/controlC0:  ubuntu     3223 F.... pulseaudio
  CasperVersion: 1.328
  DistroRelease: Ubuntu 12.10
  LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: ASUSTeK Computer INC. 1015BXO
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi.signed file=/cdrom/preseed/hostname.seed boot=casper quiet splash --
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/ubuntu not ours.
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware                            1.95
  Tags:  quantal
  Uname: Linux 3.5.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 04/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0610
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 1015BXO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x00000000
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0610:bd04/16/2012:svnASUSTeKComputerINC.:pn1015BXO:pvrx.x:rvnASUSTeKComputerINC.:rn1015BXO:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1015BXO
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.
  --- 
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu     2719 F.... pulseaudio
   /dev/snd/controlC0:  ubuntu     2719 F.... pulseaudio
  CasperVersion: 1.336
  DistroRelease: Ubuntu 13.10
  LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130814)
  MachineType: ASUSTeK Computer INC. 1015BXO
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/hostname.seed boot=casper quiet splash --
  ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-1-generic N/A
   linux-backports-modules-3.11.0-1-generic  N/A
   linux-firmware                            1.113
  Tags:  saucy
  Uname: Linux 3.11.0-1-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0610
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 1015BXO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x00000000
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0610:bd04/16/2012:svnASUSTeKComputerINC.:pn1015BXO:pvrx.x:rvnASUSTeKComputerINC.:rn1015BXO:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1015BXO
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

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