[Asus SABERTOOTH 990FX R2.0] UEFI GRUB Fails After 13.10 Beta1 Installation

[Jesse Palser]

Hi, I installed Kubuntu 13.10 64Bit Beta1 from DVD. Installation successfully completes, but after I remove the DVD and reboot I get a GRUB prompt and no OS ? Seems like UEFI GRUB install did not work properly. My motherboard is an Asus Sabertooth 990FX Gen2.0 AMD with UEFI and Secure Boot. The Kubuntu UEFI hard drive is properly listed in the motherboard's BIOS. I don't know how to proceed, please instruct... JeZ+Lee

WORKAROUND: Turn off "UEFI" and "Secure Boot" in BIOS.

---
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kubuntu 6136 F.... pulseaudio
 /dev/snd/controlC1: kubuntu 6136 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
CasperVersion: 1.331
DistroRelease: Ubuntu 13.04
IwConfig:
 eth0 no wireless extensions.

 eth1 no wireless extensions.

 lo no wireless extensions.
LiveMediaBuild: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper maybe-ubiquity quiet splash --
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware 1.106
RfKill:

Tags: raring
Uname: Linux 3.8.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 01/11/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1503
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH 990FX R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd01/11/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1222017

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Jesse Palser (jessepalser)]

Hi, I can't run any commands in a terminal because I can't get the OS to boot...

[penalvch (penalvch)]

Jesse Palser, while in the Live environment, please run:
apport-collect 1222017

[penalvch (penalvch)]

ktech, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[Jesse Palser (jessepalser)]

Hi, tried to run "apport-collect 1222017" in terminal in a live environment but it crashes every time. Now what can I do?

[penalvch (penalvch)]

Jesse Palser, instead of Live Saucy, could you please try Live Raring?

[Jesse Palser (jessepalser)]

apport information

[Jesse Palser (jessepalser)]

apport information

[Jesse Palser (jessepalser)]

apport information

[Jesse Palser (jessepalser)]

apport information

[Jesse Palser (jessepalser)]

apport information

[Jesse Palser (jessepalser)]

apport information

[Jesse Palser (jessepalser)]

apport information

[Jesse Palser (jessepalser)]

apport information

[Jesse Palser (jessepalser)]

apport information

[Jesse Palser (jessepalser)]

apport information

[Jesse Palser (jessepalser)]

apport information

[Jesse Palser (jessepalser)]

apport information

[Jesse Palser (jessepalser)]

apport information

[Jesse Palser (jessepalser)]

apport information

[penalvch (penalvch)]

Jesse Palser, as per http://www.asus.com/Motherboards/SABERTOOTH_990FX_R20/#support_Download_8 an update is available for your BIOS (1903). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

Thank you for your understanding.

[Jesse Palser (jessepalser)]

Hi, updated my motherboard's BIOS and reinstalled Kubuntu 13.10 64Bit Beta1 but UEFI GRUB is still not working. ubuntu@kubuntu:~$ sudo dmidecode -s bios-version 1903 kubuntu@kubuntu:~$ sudo dmidecode -s bios-release-date
07/08/2013

[Jesse Palser (jessepalser)]

Hi, please visit this URL to see what I get when I boot my Kubuntu 13.10 64Bit Beta1 desktop: http://16bitsoft.com/V2/Images/Stuff/Kubuntu_13_10_64Bit_Beta1_GRUB_Error-01.png

[Jesse Palser (jessepalser)]

Hi, I disabled "Secure Boot" in my BIOS and reinstalled Kubuntu 13.10 64Bit Beta1 but still have a non-working UEFI GRUB. What is next? - JeZ+Lee

[penalvch (penalvch)]

Jesse Palser, would it allow it to install if set to Legacy mode in the BIOS?

[Jesse Palser (jessepalser)]

Yes, turning off "UEFI" and "Secure Boot" in BIOS allows Kubuntu 13.10 64Bit Beta1 GRUB to install properly.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-saucy/

[R2R (are-two-are)]

I had the same problem.

The sollution that worked for me was
- starting up with the usb,
- dowloading boot-repair
- starting boot repair, using advanced options -> it points efi out, and suggest to repair the system partition.

It may work as a workaround.

Proper check by expert user required for suitability

[Joseph Salisbury (jsalisbury)]

Given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We are approaching release and would like to confirm if this bug is still present. Please test again with the latest development kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

[Chris FIebelkorn (chris-fiebelkorn)]

Actually, not sure how this plays into everything exactly, but after reinstalling Ubuntu WITHOUT luks allowed me to UEFI Boot into Ubuntu perfectly even with LVM.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]