Arch & UEFI [Was: Bug on missing staging modules rpm]

Janina Sajka janina at
Wed Jul 20 16:01:02 EDT 2016

Hi Again,

A couple specific questions below ...

Alonzo Cuellar writes:
> ...
> After that I just configure /boot/loader/entries/arch.conf
> title   Arch Linux
> linux   /vmlinuz-linux
> initrd  /intel-ucode.img
I didn't have this entry, but I do see the file in the directory. So, I
added it as you have it. But, I'm curious. What does it do?

> initrd  /initramfs-linux.img
> options root=PARTUUID=d98f4878-0b54-4f26-b036-8c5eea7b581f rw
> PARTUUID is found with
> blkid -s PARTUUID -o value /dev/ where sdxx is your root partition (not your
> efi partition.)
This may be my problem, an incorrect identifier. I've seen this language
in the docs and was confused by it. At first I took "root" to mean /, as
in the root of the file system. But, I now think that's not what's meant.

If I google for "What is PARTUUID," I find guidance that says it's a GPT
value. So, I surmise maybe it's the same as what is listed by gdisk as
the GUID.

If I do "efibootmgr -v" I get an incorrect value in the output, if
indeed this should be listing the GUID:

BootCurrent: 0008
Timeout: 9 seconds
BootOrder: 0001,0008
Boot0001* Linux Boot Manager
Boot0008* UEFI: SMI USB DISK 1100

So, the value I had in my arch.conf on last boot was incorrect. I have
now corrected it. Should I now try rebooting? Is the above report a
reflection of what was ound on the last boot, and thus explains the
error I got from bootctl?

Seems it's worth a try, but I do so hate putting the chroot environs
together every time the boot fails. And, the USB stick has sometimes not
auto booted, as the above order suggests it would. I have also done some
other work to clear out some of the intervening, nonfunction
definitions, which is why the USB is listed as 0008. I presume that will
get renumbered on next boot as well?

PS: I was unable to get anything useful from the blkid syntax you
provided. Maybe I did it wrong?


> I hope this helps,
> Alonzo
> On 07/19/2016 04:37 PM, Janina Sajka wrote:
> > Hi, All:
> > 
> > I have had a bug filed against the lack of rpms for staging modules in
> > the rpmfusion Fedora repositories. I will not be updating this bug. In
> > fact, the lack of staging support in Fedora has caused me to move to
> > Arch Linux--assuming I'll figure out how to get Arch to boot on my
> > desktop--but that's another story.
> > 
> > I'm just letting you all know, as someone should keep after rpmfusion,
> > or maybe even offer to take over that package. I have not felt it
> > something I wanted to take on.
> > 
> > Janina
> > 
> > 
> > RPM Fusion Bugzilla writes:
> > >
> > > 
> > > --- Comment #2 from Emmanuel Seyman <emmanuel at> 2016-07-19 23:01:04 CEST ---
> > > Fedora 22 has been EOL-ed and RPMFusion will no longer be releasing updates for
> > > this version of Fedora. This bug will be set to RESOLVED:EXPIRED at the end of
> > > the week to reflect this.
> > > 
> > > If the problem persists after upgrading to the latest version of Fedora, please
> > > update the version field of this bug (and re-open it if it has been closed).
> > > 
> > > -- 
> > > Configure bugmail:
> > > ------- You are receiving this mail because: -------
> > > You are on the CC list for the bug.
> > > You reported the bug.
> _______________________________________________
> Speakup mailing list
> Speakup at


Janina Sajka,	Phone:	+1.443.300.2200
			sip:janina at
		Email:	janina at

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures

More information about the Speakup mailing list