trouble with Sync EFISTUB Kernel in UEFISYS partition using Systemd

otto88 · 2012-12-16 11:36:31

hi, everyone

I had install archlinux.

In the arch-wiki, "Sync EFISTUB Kernel in UEFISYS partition using Systemd"

when i done..

# systemctl enable efistub-update.path

then

# systenctl status efistub-update.path

return:

Loaded: loaded(percorso...;enabled)
Active: inactive(dead)

when i done

system start efistub-update.path

return:

"Job for efistub-update.path failed"

help please

srs5694 · 2012-12-16 19:34:34

Depending on your system configuration, this may no longer be necessary. There's now an ext4fs driver for EFI, so if your kernel is on an ext4fs partition, you may be able to load that driver and read your kernel directly from your kernel's "natural habitat," as it were. This works most smoothly with rEFInd, which supports loading drivers, but it might work with gummiboot if you use a boot-time shell script to load the driver and launch gummiboot, or if your firmware provides a user interface to load drivers before launching your boot loader.

Unfortunately, this won't help if you're using another filesystem (JFS, XFS, or Btrfs) or if your ext4fs root (or /boot) filesystem is in a RAID or LVM setup. Even in these cases, though, you could use a separate /boot partition with FAT, HFS+, ext2fs, ext3fs, or ReiserFS.

cfr · 2012-12-19 03:03:03

As far as I can tell, this driver is not yet available in Arch. (Maybe in testing.) At least, I have:

$ ls /usr/lib/refind/drivers_x64/
ext2_x64.efi  hfs_x64.efi  iso9660_x64.efi  reiserfs_x64.efi

which I guess means that my version doesn't yet feature this driver. (I installed refind-efi yesterday and did pacman -Syu today but I do not use testing.)

cfr · 2012-12-19 03:07:20

Please use [code ] [/code ] tags (w/o the spaces).

otto88 wrote:

system start efistub-update.path

First, it should be

systemctl start efistub-update.path

Second, did you create the files this needs? What does:

cat /etc/systemd/system/efistub-update.*

give?

Note: I set this up yesterday for both the standard and LTS kernels following the wiki. I then updated the LTS kernel and checked things got properly synced. So the instructions definitely should work. (The LTS kernel is not relevant unless you installed it. I just mention it as that's the one which was updated.)

Last edited by cfr (2012-12-19 03:10:01)

srs5694 · 2012-12-19 04:09:48

cfr wrote:

As far as I can tell, this driver is not yet available in Arch. (Maybe in testing.) At least, I have:
$ ls /usr/lib/refind/drivers_x64/
ext2_x64.efi  hfs_x64.efi  iso9660_x64.efi  reiserfs_x64.efi
which I guess means that my version doesn't yet feature this driver. (I installed refind-efi yesterday and did pacman -Syu today but I do not use testing.)

You can always grab it from the official rEFInd package. Even if you install the Arch package for rEFInd itself, dropping the driver file from my own rEFInd build onto your ESP should work fine. Alternatively, you could just wait; I'm sure the Arch package will be updated soon.

cfr · 2012-12-19 22:00:29

I can wait - I was just pointing out that the driver might not be in the current Arch installation.

the.ridikulus.rat · 2012-12-20 03:03:52

cfr wrote:

As far as I can tell, this driver is not yet available in Arch. (Maybe in testing.) At least, I have:
$ ls /usr/lib/refind/drivers_x64/
ext2_x64.efi  hfs_x64.efi  iso9660_x64.efi  reiserfs_x64.efi
which I guess means that my version doesn't yet feature this driver. (I installed refind-efi yesterday and did pacman -Syu today but I do not use testing.)

You can use aur/refind-efi-git pkg.

swordfish · 2012-12-20 11:10:04

cfr wrote:

As far as I can tell, this driver is not yet available in Arch. (Maybe in testing.)

The updated driver has arrived in testing: https://www.archlinux.org/packages/test … efind-efi/

Under "Package Contents" you will find:

usr/lib/refind/drivers_x64/ext2_x64.efi
usr/lib/refind/drivers_x64/ext4_x64.efi
usr/lib/refind/drivers_x64/hfs_x64.efi
usr/lib/refind/drivers_x64/iso9660_x64.efi
usr/lib/refind/drivers_x64/reiserfs_x64.efi

But I have to ask: Does that mean that I no longer need "efistub-update.path" and "efistub-update.service" to be managed by systemd? If so, how does it work then to tell rEFInd that a new kernel has arrived?

Last edited by swordfish (2012-12-20 11:11:35)

srs5694 · 2012-12-20 17:06:15

swordfish wrote:

But I have to ask: Does that mean that I no longer need "efistub-update.path" and "efistub-update.service" to be managed by systemd? If so, how does it work then to tell rEFInd that a new kernel has arrived?

Be aware that, although I'm rEFInd's maintainer, I only have "one toe in the pool" as far as Arch goes. (I've got an Arch installation in a virtual machine, but it's fairly new, and I'm not yet very familiar with the Arch kernel update process.)

If rEFInd can read your kernels where they naturally "live," and if a new kernel replaces an old one, then no reconfiguration is required; rEFInd simply detects the new kernel and uses it instead of the old one.

If a kernel update results in a new kernel file, so that you've got two (or more) kernels, then it gets tricky, since rEFInd then can't distinguish which initrd file should be associated with any given kernel. In that case, you'd need some way to separate the kernels into different directories or create a manual configuration of some sort.

cfr · 2012-12-20 22:13:34

But you could use a static configuration to distinguish the two kernels and avoid having to copy them to the EFI partition, right? So it should avoid the need for the update service even in that case.

(I always have 2 arch kernels installed - the regular one and the LTS one just in case.)

srs5694 · 2012-12-21 03:48:38

cfr wrote:

But you could use a static configuration to distinguish the two kernels and avoid having to copy them to the EFI partition, right? So it should avoid the need for the update service even in that case.

Yes. You can do just about anything with manual boot stanzas in refind.conf. Their main drawbacks are the need to set them up manually and the fact that they don't dynamically track anything that changes (new kernels under new names, for instance). If your kernels' filenames remain constant, even if their contents change, then manual boot stanzas make a lot of sense.

Arch Linux

#1 2012-12-16 11:36:31

trouble with Sync EFISTUB Kernel in UEFISYS partition using Systemd

#2 2012-12-16 19:34:34

Re: trouble with Sync EFISTUB Kernel in UEFISYS partition using Systemd

#3 2012-12-19 03:03:03

Re: trouble with Sync EFISTUB Kernel in UEFISYS partition using Systemd

#4 2012-12-19 03:07:20

Re: trouble with Sync EFISTUB Kernel in UEFISYS partition using Systemd

#5 2012-12-19 04:09:48

Re: trouble with Sync EFISTUB Kernel in UEFISYS partition using Systemd

#6 2012-12-19 22:00:29

Re: trouble with Sync EFISTUB Kernel in UEFISYS partition using Systemd

#7 2012-12-20 03:03:52

Re: trouble with Sync EFISTUB Kernel in UEFISYS partition using Systemd

#8 2012-12-20 11:10:04

Re: trouble with Sync EFISTUB Kernel in UEFISYS partition using Systemd

#9 2012-12-20 17:06:15

Re: trouble with Sync EFISTUB Kernel in UEFISYS partition using Systemd

#10 2012-12-20 22:13:34

Re: trouble with Sync EFISTUB Kernel in UEFISYS partition using Systemd

#11 2012-12-21 03:48:38

Re: trouble with Sync EFISTUB Kernel in UEFISYS partition using Systemd

Board footer