Announcement

**Qqmike** · Nov 29, 2015, 05:39 PM

Note:
After installing Kubuntu in UEFI mode, you can see the GRUB bootloader files for your Kubuntu in the ESP (EFI System Partition), which in your case is sda2. If you are in Kubuntu, the ESP will always be mounted at /boot/efi. Then you'd see /boot/efi/EFI/ubuntu (ubuntu is for Kubuntu, Mint, Lubuntu, Xubuntu, etc.--that's another story). And inside /boot/efi/EFI/ubuntu you will see the bootloader files for Kubuntu; mainly, to include the key one: grubx64.efi; and there may also be a shim, a MokMgr, a brief grub.cfg.
If you install the package called
tree
you can run from Konsole
tree /boot/efi
to see everything in the sda2 ESP. Or open /boot/efi/EFI in Dolphin and have a look. Or list using ls at the command line.

**vsreeser** · Nov 30, 2015, 02:41 AM

Have you tried reodering the boot menu in BIOS? I had to do this. There were two entries. one for win10 and one for kubuntu. Just moved kubuntu to #1 position and all was well.

**Qqmike** · Nov 30, 2015, 06:11 AM

That's what his
sudo efibootmgr -o xxxx,xxxx, ...
is also supposed to do.
Some "BIOS's" don't let you rearrange UEFI NVRAM variables from within, some (like ASUS) do.

But, more importantly, his boot order, shown in Post #13, is correct -- ubuntu (Kubuntu) appears as first, Windows as second. But it is not behaving as expected.

**Clayman1000x** · Nov 30, 2015, 06:41 AM

Originally posted by Qqmike View Post

That's what his
sudo efibootmgr -o xxxx,xxxx, ...
is also supposed to do.
Some "BIOS's" don't let you rearrange UEFI NVRAM variables from within, some (like ASUS) do.

But, more importantly, his boot order, shown in Post #13, is correct -- ubuntu (Kubuntu) appears as first, Windows as second. But it is not behaving as expected.

Right, mine does not allow this, already looked at trying that.

**Clayman1000x** · Nov 30, 2015, 09:43 AM

konsole monday.txt Gonna reboot again

**Clayman1000x** · Nov 30, 2015, 10:05 AM

Nope, booted into windows repair, look at this boot order after reboot, system doesn't hold settings it seems, I get the settings back after doing update grub, Boot0002 gave an error when I tried booting with that, something about a key.

Code:

rcw@rcw-HP2000:~$ sudo efibootmgr
[sudo] password for rcw: 
BootCurrent: 0000
Timeout: 0 seconds
[U][COLOR=#ff0000]BootOrder: 3001,3000,3002,3003,2001,2002,2003[/COLOR][/U]
Boot0000* ubuntu
Boot0001* Windows Boot Manager
Boot0002* rEFInd Boot Manager
Boot0003* Ubuntu
Boot2001* USB Drive (UEFI)
Boot2002* Internal CD/DVD ROM Drive (UEFI)
Boot3000* EFI Internal Hard Disk or Solid State Disk
Boot3001* EFI Internal Hard Disk or Solid State Disk
Boot3002* EFI Internal Hard Disk or Solid State Disk
Boot3003* EFI Internal Hard Disk or Solid State Disk
rcw@rcw-HP2000:~$ sudo grub-install
Installing for x86_64-efi platform.
Installation finished. No error reported.
rcw@rcw-HP2000:~$ sudo update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.13.0-68-generic
Found initrd image: /boot/initrd.img-3.13.0-68-generic
Found linux image: /boot/vmlinuz-3.13.0-32-generic
Found initrd image: /boot/initrd.img-3.13.0-32-generic
Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for EFI firmware configuration
done
rcw@rcw-HP2000:~$ sudo efibootmgr
BootCurrent: 0000
Timeout: 0 seconds[COLOR=#ff0000]BootOrder: 0000,3001,3000,3002,3003,2001,2002,2003     (after grub install update)[/COLOR]
Boot0000* ubuntu
Boot0001* Windows Boot Manager
Boot0002* rEFInd Boot Manager
Boot2001* USB Drive (UEFI)
Boot2002* Internal CD/DVD ROM Drive (UEFI)
Boot3000* EFI Internal Hard Disk or Solid State Disk
Boot3001* EFI Internal Hard Disk or Solid State Disk
Boot3002* EFI Internal Hard Disk or Solid State Disk
Boot3003* EFI Internal Hard Disk or Solid State Disk
rcw@rcw-HP2000:~$

I rebooted and again had to go through bios and ubuntu is gone from the boot order until I reinstall then update grub and it gets added again.

When I reinstalled Kubuntu this last time I was given a choice on where to put the loader, I chose sda2, the windows loader partition, was that the right place?

**Qqmike** · Nov 30, 2015, 11:15 AM

(1)
To edit as root:
kdesudo kate /etc/default/grub

Did you check that the Kubuntu /boot/grub/grub.cfg is NOT booting directly to Windows?

(2)
Your tree /boot/efi: OK, rEFInd and ubuntu are properly there. (I didn't recognize hardly any of the HP or Windows stuff -- much of it new to me, very complicated!, but that's Ok as I don't use HP or Windows.)

(3)

Nope, booted into windows repair, look at this boot order after reboot, system doesn't hold settings it seems,

I've heard of this happening. Touchy-buggy firmware, that's all. Not good, but that's how it can be, depending on the PC maker and UEFI firmware implementation.

In Post #21, I don't even see rEFInd listed in the BootOrder. Ouch! It must be there!?

(4)
Wondering now, if this is a bona fide buggy EFI/BIOS firmware? It looks--from here--like you are doing everything right.

Wild shot: The HP may need a "BIOS"/firmware update? I realize that's always iffy and risky and a possible crap shoot, but ...

(5)
Geez, I'm not sure now.

Except, possibly this:

As an experiment to see if anything makes sense, why not run rEFInd as a live CD and boot the PC from it, and boot from the menu rEFInd shows you and see if ubuntu/Kubuntu will boot that way. Or just see what rEFInd sees. When booting from the rEFInd, you have to enter the UEFI/BIOS firmware setup menus, and select the rEFInd EFI/UEFI CD to boot from.

Making the rEFInd CD:
https://www.kubuntuforums.net/showth...l=1#post376838

or a rEFInd USB:
https://www.kubuntuforums.net/showth...l=1#post379352

**Clayman1000x** · Dec 01, 2015, 08:50 AM

Code:

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT="Ubuntu"
#GRUB_HIDDEN_TIMEOUT="0"
GRUB_HIDDEN_TIMEOUT_QUIET="true"
GRUB_TIMEOUT="10"
GRUB_DISTRIBUTOR="`lsb_release -i -s 2> /dev/null || echo Debian`"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL="console"

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE="640x480"

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID="true"

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

GRUB_SAVEDEFAULT="false"
#GRUB_DISABLE_OS_PROBER="false"

**Clayman1000x** · Dec 01, 2015, 08:54 AM

Code:

$ sudo efibootmgr
BootCurrent: 0000
Timeout: 0 seconds[U][COLOR=#ff0000]
BootOrder: 3001,3000,3002,3003,2001,2002,2003[/COLOR][/U]                (oooo is gone again, I don't get this)[COLOR=#ff0000][/COLOR]
Boot0000* ubuntu
Boot0001* Windows Boot Manager
Boot0002* rEFInd Boot Manager
Boot0003* Ubuntu
Boot2001* USB Drive (UEFI)
Boot2002* Internal CD/DVD ROM Drive (UEFI)
Boot3000* EFI Internal Hard Disk or Solid State Disk
Boot3001* EFI Internal Hard Disk or Solid State Disk
Boot3002* EFI Internal Hard Disk or Solid State Disk
Boot3003* EFI Internal Hard Disk or Solid State Disk

**Clayman1000x** · Dec 01, 2015, 08:55 AM

It seems to me that the windows loader is not passing the boot to grub, how would I look at the windows loader?

**Qqmike** · Dec 01, 2015, 09:24 AM

This looks OK, maybe ... :

Code:

GRUB_DEFAULT="Ubuntu"
 #GRUB_HIDDEN_TIMEOUT="0"
 GRUB_HIDDEN_TIMEOUT_QUIET="true"
 GRUB_TIMEOUT="10"

Except:
Do you need quotes around the 10?; shouldn't it be GRUB_TIMEOUT=10; or does it work both ways? and this: GRUB_DEFAULT="Ubuntu" ... is that correct? or should it be simply GRUB_DEFAULT=0, where 0 is the position (= the first position in the menu entries) that ubuntu holds in your /boot/grub/grub.cfg menu. If this is not correct, it could cause unpredictable results, and so it should be checked now.

Code:

BootOrder: 3001,3000,3002,3003,2001,2002,2003      (oooo is gone again, I don't get this)

And, Windows Boot Manager 0001 and rEFInd 0002 are not listed.
However, it DOES say

Code:

BootCurrent: 0000

=> it is currently booting from ubuntu.

how would I look at the windows loader?

I don't know. But a google would produce the way. It is easy to do (as I see posters using various methods to get into the Windows bootloader, edit it, etc.).
But, the problem here is the failure of the UEFI firmware to place ubuntu as #1 in BootOrder and make it stick and work. Or, to place rEFInd as #1 in the BootOrder.

Btw, What are those 3xxx entries, 3000, 3001, 3002, 3003?

I'll mention Boot Repair, seems to be good, reliable, and can often save the day (although it will probably simply do what we have done manually, but who knows):
https://help.ubuntu.com/community/Boot-Repair

Did you happen to try a live rEFInd CD/USB to see if it would work?
Or, try this:
re-boot the PC, press the magic key to enter UEFI (BIOS) firmware setup, find a boot menu, select rEFInd from that boot menu, and boot the PC that way; then examine the boot menu presented to you by rEFInd, select ubuntu, see what happens.
(Btw, when rEFInd was installed, it also should have placed itself as #1 in the UEFI BootOredr; but, again, your firmware is not respecting these rules.)

**Qqmike** · Dec 01, 2015, 09:28 AM

Exs (I didn't read them):
http://superuser.com/questions/49215...s-in-windows-8
http://www.computerperformance.co.uk...s8-bcdedit.htm

**Qqmike** · Dec 01, 2015, 04:58 PM

To list all your drives and partitions, one nice way is
lsblk

**Clayman1000x** · Dec 03, 2015, 08:10 AM

Update, after spending at least a week trying to get the grub loader to work I decided just to delete windows and repartition the drive. All done and working, just don't get why I couldn't get windows to comply with me, but it was so slow I had to wait and wait for firefox to even open. But everything is good now. Thank you Qqmike for working with me and trying to help.

**Qqmike** · Dec 03, 2015, 08:14 AM

OK, good, not a bad decision. rEFInd, ime, seems to be able to boot about anything; very strange on this one, though. I do agree, something seemed to be amiss on Window's end of this deal.
Future ref.:
https://www.kubuntuforums.net/showth...l=1#post379977

Announcement

kubuntu not booting properly

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment