You are not logged in.
I installed bunsen labs alongside my archlinux but skipped the mbr boot loader setup because I have a UEFI mobo.Can someone point me in the right direction here? How do I get it to boot?
Offline
Welcome to the forums
Step one: Search the forum for all the UEFI posts
Step two: Try Convert your BunsenLabs system to UEFI booting
There is also a recent HowTo to chroot into your system from a Live session, and carry out repairs that way.
Hopefully @Head_on_a_Stick, the resident go-to UEFI guy, will be along sometime
Last edited by damo (2016-02-02 02:11:59)
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
Hello!
By which method are you booting your Arch system?
Which boot{loader,manager} are you using?
Offline
Perhaps it is necessary to add packages from the Arch.
This is to let the GRUB is either BunsenLabs or Arch:
https://wiki.archlinux.org/index.php/GR … m_other_OS
Last edited by balloon (2016-02-02 11:15:12)
BALLOON | FU-SEN - English balloon.gdn - 日本語 balloon.asia - GitHub fu-sen
Offline
I think I'm on gummiboot. It was so long ago that I set it up.
I have already made that EFI boot partition.
I am not sure how to follow the linked guide further as it is written with the expectation that I'm already running Bunsen.
Offline
I think I'm on gummiboot
OK we can make this work but it will take some fiddling.
First, let's make sure we know how everything is set up so I don't b0rk your system.
From your Arch system, please post the output of:
# parted -l
# efibootmgr -v
lsblk -f
The first two commands should be run as root (this is what the "#" symbol means)
EDIT: Just to note, I am currently booting my BunsenLabs system with gummiboot so I know this can be done.
Last edited by Head_on_a_Stick (2016-02-02 19:18:55)
Offline
I ended up reformatting everything.
Here is where I'm at now.
user@debian:~$ sudo parted -l
Model: ATA OCZ-VERTEX3 (scsi)
Disk /dev/sda: 240GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 538MB 537MB fat32 boot, esp
2 538MB 135GB 135GB ext4
3 135GB 240GB 105GB ext4
From the live BL LiveUSB I installed grub-efi and ran grub-install...targeting sda1 @ /mnt/esp
user@debian:~$ sudo grub-install --target=x86_64-efi --efi-directory=/mnt/esp --recheck
Installing for x86_64-efi platform.
grub-install: error: failed to get canonical path of `aufs'.
I tried to chroot into the install but with other errors...
root@debian:/# apt-get install grub-efi
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package grub-efi is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
grub-common grub2-common
E: Package 'grub-efi' has no installation candidate
I tried to install it anyways...
root@debian:/# grub-install --target=x86_64-efi --efi-directory=/boot/efi/ --recheck
grub-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist. Please specify --target or --directory.
Offline
I ended up reformatting everything.
Do you mean that you removed your Arch system?
If you still have Arch installed, all we have to do is copy the BunsenLabs kernel image and initramfs to the EFI system partition (/dev/sda1) and make a gummiboot menu entry -- this will allow BL to bot in UEFI mode using your Arch gummiboot menu.
A kernel postinstall script is needed to ensure that updated kernels are copied back to the ESP but this is very simple.
If you have removed your Arch system then it's probably best to simply re-install BunsenLabs and make sure that your EFI sytem partition (/dev/sda1) is mounted to /boot/efi -- you can enter this manually in the partitioning section of the installer.
Once this is done, you can let the installer place the (non-UEFI) GRUB bootloader in the MBR of your drive and boot your system in non-UEFI mode then follow the steps outlined in the "Convert your BunsenLabs system to UEFI Booting" link in my signature.
If you do not wish to re-install, I can give you the exact commands needed to chroot successfully with a working internet connection and the ability to install grub-efi & run the `grub-install` command.
The reason why the grub-efi package was "not found" when you tried to install it is probably because you have no APT database set up (run `apt update` to generate this) or no internet connection (or no nameservers).
As you can see from the link, the package most certainly does exist and is in the repositories.
Please *do not* try to do things unless I specifically tell you to or thing will get very confusing very quickly.
Offline
Removed Arch completely as the end goal is to replace it with BL.
I didn't realize booting from GRUB on the MBR was an option at all.
Will rerun the installer with that in mind and try following the guide.
I don't understand why the ESP needs an fstab entry to mount at /boot/efi.
Offline
I don't understand why the ESP needs an fstab entry to mount at /boot/efi
Because your UEFI motherboard will only start .efi loaders that are on the EFI system partition.
The Debian GRUB package will place it's .efi loader under /boot/efi
It is not possible to mount /boot to the ESP in Debian because dpkg will refuse to unpack a kernel image to a non-POSIX filesystem (the ESP must be FAT-formatted).
Offline
I get an error when installing grub.
The grub-pc package failed to install to /target/.
This is using the graphical installer.
Offline
Ah bugger, sorry.
You need a BIOS boot partition (type EF02) to install non-UEFI GRUB to a GPT disk such as yours.
I like to use:
# gdisk /dev/sda
Then use "n" to generate a new partition and press enter twice to accept the default start and end sectors (34 & 2047, respectively) and make it type "ef02" then use "w" to write the changes to disk.
Alternatively, use gparted to make a small (1MiB is enough) new partition -- the partition flag you need is called "bios_grub"
Most importantly: *do not* attempt to format this new partition, it should *not* have any filesystem at all.
Offline
I reran the installer but didn't include a mountpoint for the ESP and grub installed fine.
System boots and seems usable except;
Now I'm getting GPG errors from apt-get.
koopdi@funroll:~$ sudo apt-get update
Get:1 http://www.deb-multimedia.org jessie InRelease [22.3 kB]
Hit http://pkg.bunsenlabs.org bunsen-hydrogen InRelease
Hit http://pkg.bunsenlabs.org bunsen-hydrogen/main amd64 Packages
Ign http://www.deb-multimedia.org jessie InRelease
Ign http://www.deb-multimedia.org jessie/main amd64 Packages/DiffIndex
Ign http://www.deb-multimedia.org jessie/non-free amd64 Packages/DiffIndex
Hit http://www.deb-multimedia.org jessie/main amd64 Packages
Hit http://www.deb-multimedia.org jessie/non-free amd64 Packages
Ign http://pkg.bunsenlabs.org bunsen-hydrogen/main Translation-en_US
Ign http://pkg.bunsenlabs.org bunsen-hydrogen/main Translation-en
Ign http://www.deb-multimedia.org jessie/main Translation-en_US
Ign http://www.deb-multimedia.org jessie/main Translation-en
Ign http://www.deb-multimedia.org jessie/non-free Translation-en_US
Ign http://www.deb-multimedia.org jessie/non-free Translation-en
Fetched 22.3 kB in 7s (2,901 B/s)
Reading package lists... Done
W: GPG error: http://www.deb-multimedia.org jessie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5C808C2B65558117
and the same error finding grub-efi
koopdi@funroll:~$ sudo apt-get install grub-efi
[sudo] password for koopdi:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package grub-efi is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
grub-common grub2-common
E: Package 'grub-efi' has no installation candidate
Offline
Here is my fstab post install
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda2 during installation
UUID=09b560bd-4b91-4a76-8675-41833b99b0cc / ext4 errors=remount-ro 0 1
# /home was on /dev/sda3 during installation
UUID=02eb6700-1fd2-4b77-b89e-a385eaecf88b /home ext4 defaults 0 2
and now with an entry for the esp added manually plus noatime options because SSD.
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda2 during installation
UUID=09b560bd-4b91-4a76-8675-41833b99b0cc / ext4 noatime, errors=remount-ro 0 1
# /home was on /dev/sda3 during installation
UUID=02eb6700-1fd2-4b77-b89e-a385eaecf88b /home ext4 noatime 0 2
#/dev/sda1: LABEL="ssd_esp" UUID="15D8-BA02" TYPE="vfat" PARTLABEL="ssd_esp" PARTUUID="39e7566a-575b-4e9b-b398-74d81fcc50fd"
UUID=39e7566a-575b-4e9b-b398-74d81fcc50fd /boot/efi vfat noatime 0 2
Offline
okay UUID fo ESP was wrong, corrected.
Here is how it looks.
koopdi@funroll:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 223.6G 0 disk
├─sda1 8:1 0 512M 0 part /boot/efi
├─sda2 8:2 0 125.4G 0 part /
└─sda3 8:3 0 97.7G 0 part /home
Offline
Still trying to overcome GPG errors.
Tried;
sudo apt-key adv --recv-keys --keyserver http://www.deb-multimedia.org 5C808C2B65558117
...
gpg: requesting key 65558117 from http server www.deb-multimedia.org
gpgkeys: no key data found for http://www.deb-multimedia.org/
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
Offline
Comment out the deb-multimedia lines then `apt update` and install away.
I don't know why deb-multimedia is doing that
Offline
This worked;
sudo apt-get install deb-multimedia-keyring
apt-get update works but still I have the same error for grub-efi;
koopdi@funroll:~$ sudo apt-get install grub-efi
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package grub-efi is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
grub-common grub2-common
E: Package 'grub-efi' has no installation candidate
Offline
Is the `deb-multimedia-keyring` package installed?
EDIT ninja'd by the OP
Last edited by damo (2016-02-03 22:11:56)
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
^^
It is now
My wireless has issues and tends to disconnect approx every 2 to 20min...leads to strange errors.
Offline