Bug on missing staging modules rpm

Discussion:

Janina Sajka

2016-07-19 21:37:39 UTC

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

https://bugzilla.rpmfusion.org/show_bug.cgi?id=3807
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: https://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You reported the bug.

--
Janina Sajka, Phone: +1.443.300.2200
sip:***@asterisk.rednote.net
Email: ***@rednote.net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup: http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures http://www.w3.org/wai/apa

Alonzo Cuellar

2016-07-20 01:57:00 UTC

Permalink

Hello Janina,

I think I saw your postings related to UEFI in irc. If you need help let
me know.

My setup is the following.

partitions = /boot, swap, / and home

systemd boot, or bootctl looks for your efi partition mounted at /boot
by default.

With my partitions made I do bootctl install.

After that I just configure /boot/loader/entries/arch.conf

title Arch Linux
linux /vmlinuz-linux
initrd /intel-ucode.img
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.)

I hope this helps,

Alonzo

Post by Janina Sajka
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

Janina Sajka

2016-07-20 20:01:02 UTC

Permalink

Hi Again,

A couple specific questions below ...

Post by Alonzo Cuellar
...
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?

Post by Alonzo Cuellar
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
HD(1,GPT,a95c2ac4-a6b7-4191-9c2a-34b694a39d08,0x800,0x64000)/File(\EFI\systemd\systemd-bootx64.efi)
Boot0008* UEFI: SMI USB DISK 1100
PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/HD(1,MBR,0x82,0xac,0x14000)AMBO

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?

Janina

Post by Alonzo Cuellar
I hope this helps,
Alonzo

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

Jason White

2016-07-20 22:09:50 UTC

Permalink

Post by Janina Sajka
A couple specific questions below ...

Post by Alonzo Cuellar
...
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?

According to the bootctl manual page:
"A copy of systemd-boot will be stored as the EFI default/fallback loader at
/EFI/Boot/boot*.efi. A systemd-boot entry in the EFI boot variables is created
and added to the top of the boot order list."

I strongly suspect the configuration file, as above, then enables the boot
loader to find the kernel and the initrd. Thus the start-up order is:

EFI firmware -> boot loader -> kernel.

and the kernel is not booted directly by the EFI firmware in this
configuration, but by the *.efi boot loader executable specified in the EFI
boot variable.

Alonzo Cuellar

2016-07-22 22:51:57 UTC

Permalink

Hi
Yes that is what it does. Sorry for the long response. I've been on the
road.

Post by Jason White

Post by Janina Sajka
A couple specific questions below ...

Post by Alonzo Cuellar
...
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?

"A copy of systemd-boot will be stored as the EFI default/fallback loader at
/EFI/Boot/boot*.efi. A systemd-boot entry in the EFI boot variables is created
and added to the top of the boot order list."
I strongly suspect the configuration file, as above, then enables the boot
EFI firmware -> boot loader -> kernel.
and the kernel is not booted directly by the EFI firmware in this
configuration, but by the *.efi boot loader executable specified in the EFI
boot variable.
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

Janina Sajka

2016-07-23 14:27:46 UTC

Permalink

Hi,

Just last night I finally got my system booting successfully. It turns
out that swapping usb sticks on this particular board could cause the
UEFI boot order settings to get shuffled. One of these shuffles appears
to have put me back in legacy mode, so I took advantage of that to have
gdisk return me to mbr. A quick install of grub, and I'm booting just
fine.

Further searching turns up people with similar boards having issues with
UEFI as well--so clearly not something Arch related. I may try again
after, and if I get my firmware fully updated. Unfortunately, Asrock's
support pages aren't very friendly to work with, so that will have to
await sighted assistance.

Thanks for your help. I feel I've a pretty good handle on efistub and
systemd booting. I just can't do it on this machine. But, I'm at least
up and running, which is what really matters!

Janina

Post by Alonzo Cuellar
Hi
Yes that is what it does. Sorry for the long response. I've been on the
road.

Post by Jason White

Post by Janina Sajka
A couple specific questions below ...

Post by Alonzo Cuellar
...
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?

"A copy of systemd-boot will be stored as the EFI default/fallback loader

Post by Jason White
/EFI/Boot/boot*.efi. A systemd-boot entry in the EFI boot variables is

created

Post by Jason White
and added to the top of the boot order list."
I strongly suspect the configuration file, as above, then enables the boot
EFI firmware -> boot loader -> kernel.
and the kernel is not booted directly by the EFI firmware in this
configuration, but by the *.efi boot loader executable specified in the

EFI

Post by Jason White
boot variable.
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

Chris Brannon

2016-07-23 15:08:02 UTC

Permalink

Post by Janina Sajka
Just last night I finally got my system booting successfully. It turns
out that swapping usb sticks on this particular board could cause the
UEFI boot order settings to get shuffled.

Just out of curiosity, what kind of mobo do you have?
Mine is an Asus F1A55-M.
I had a similar problem a while back, and I posted to the list
about it. At some point, my UEFI boot settings got shuffled, and the
board now always boots all of my rescue media in legacy mode.
efibootmgr won't work, and none of the EFI variables are available.
I didn't mention it earlier in this thread, because it looked like
efibootmgr and friends were working for you.
I suspect if I ever need to do anything with EFI while rescuing a
system, I'm going to have to get a sighted person over here with a
monitor to fix my settings.
EFI has been a bit of a source of pain and frustration for me.
It's really too bad that the computer makers went off and did their own
thing here, rather than adopting something open like Coreboot. I
suspect that Coreboot could actually be made to talk, and we could
have had accessibility at the firmware level. Oh well, whatever.
Another day, another disappointment.

-- Chris

Janina Sajka

2016-07-23 22:18:47 UTC

Permalink

Hi, Chris:

Mine is an Asrock Z77Pro4 mobo. This machine is vintage 2013. My
requirements at the time included 3 PCI slots, and a mobo with that many
wasn't easy to find. Nowadays I only use two! <sigh>

I'm going to be more careful with the next mobo. I'm not going to assume
just because they have UEFI, they've done a good implementation. But
then, I should also upgrade my firmware, as it's stock as shipped, and
quite out of date.

In most respects it's been a good board. It was Bill Acker's favorite
build machine.

Janina

Post by Chris Brannon

Alonzo Cuellar

2016-07-23 11:36:48 UTC

Permalink

Hello Janina,

Sorry for the long responce again.

Doing

bootctl install coppies the needed files in /boot/loader and /boot/EFI.
It also adds an entry in the efi menu to boot the kernel.

the file

/boot/loader/entries/arch.conf tells the system to simply boot the
kernel as you described previously in one of your messages.

blkid -s PARTUUID -o value/dev/sdxx will get your PARTUUID. This should be the PARTUUID of your
root partition which for me is /dev/sda2. /dev/sda1 = EFI and is mounted
on /boot /dev/sda2 = my root partition and is the partition you want to
get the PARTUUID value /dev/sda3 = home The partition table has to be in
gpt. The ESP (EFI system Partition) is in fat32 I've not used
"efibootmgr" so I can not currently comment on that. It took me a while
to get an EFI system working a few years ago. Now that it works... Its
probably the easiest way of booting the system. For me anyways. Note-
You will need to have secure boot turned off for Arch Linux. You can
have the system installed successfully. However, if you have secure boot
enabled Arch will not boot. I hope this clears up most things. Alonzo

Post by Janina Sajka
Hi Again,
A couple specific questions below ...

Post by Alonzo Cuellar
...
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?

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
BootCurrent: 0008
Timeout: 9 seconds
BootOrder: 0001,0008
Boot0001* Linux Boot Manager
HD(1,GPT,a95c2ac4-a6b7-4191-9c2a-34b694a39d08,0x800,0x64000)/File(\EFI\systemd\systemd-bootx64.efi)
Boot0008* UEFI: SMI USB DISK 1100
PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/HD(1,MBR,0x82,0xac,0x14000)AMBO
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?
Janina

Post by Alonzo Cuellar
I hope this helps,
Alonzo

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

Alonzo Cuellar

2016-07-20 02:06:12 UTC

Permalink

oh and one more thing

configure /boot/loader/loader/conf

default arch
timeout 4

editor 0

Janina Sajka

2016-07-20 17:55:12 UTC

Permalink

Hi, Alonzo:

Thank you for this offer. I accept!

I see a few discrepencies between what I have and what you show--more
about them soon in another email.

I had no errors running bootctl, but I wasn't able to boot from that.
I've also tried using efistub boot, also without success.

Meanwhile, if I run bootctl by itself, I come up with the following
error up top:

Failed to read EFI variable LoaderDevicePartUUID

Running efibootmgr shows no errors.

More soon--I have a telecon to go to just now.

Janina

Everything else looks OK in the output.

It seems there's a recent bug that might be related?
https://bugs.archlinux.org/task/49314

Janina

Post by Alonzo Cuellar
oh and one more thing
configure /boot/loader/loader/conf
default arch
timeout 4
editor 0

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

Jude DaShiell

2016-07-20 17:59:16 UTC

Permalink

Janina,

Have you done sudo updatedb then locate efi*.service yet? You need the
mlocate package installed first if that wasn't done yet. There may be
some services you can enable.

Date: Wed, 20 Jul 2016 13:55:12
Reply-To: Speakup is a screen review system for Linux.
Subject: Arch & UEFI [Was: Bug on missing staging modules rpm]
Thank you for this offer. I accept!
I see a few discrepencies between what I have and what you show--more
about them soon in another email.
I had no errors running bootctl, but I wasn't able to boot from that.
I've also tried using efistub boot, also without success.
Meanwhile, if I run bootctl by itself, I come up with the following
Failed to read EFI variable LoaderDevicePartUUID
Running efibootmgr shows no errors.
More soon--I have a telecon to go to just now.
Janina
Everything else looks OK in the output.
It seems there's a recent bug that might be related?
https://bugs.archlinux.org/task/49314
Janina

Post by Alonzo Cuellar
oh and one more thing
configure /boot/loader/loader/conf
default arch
timeout 4
editor 0

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

--
Janina Sajka, Phone: +1.443.300.2200
Linux Foundation Fellow
Executive Chair, Accessibility Workgroup: http://a11y.org
The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures http://www.w3.org/wai/apa
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

Janina Sajka

2016-07-20 19:47:29 UTC

Permalink

Post by Alonzo Cuellar
Janina,
Have you done sudo updatedb then locate efi*.service yet? You need the
mlocate package installed first if that wasn't done yet. There may be some
services you can enable.

I have mlocate installed -- can't live without my locate command! <grin>

However, locate efi*.service returns nothing.

Post by Alonzo Cuellar

Post by Alonzo Cuellar
oh and one more thing
configure /boot/loader/loader/conf
default arch
timeout 4
editor 0

Post by Janina Sajka

Post by Janina Sajka
I have had a bug filed against the lack of rpms for staging

modules in

Post by Janina Sajka
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.

Post by Janina Sajka
I'm just letting you all know, as someone should keep after

rpmfusion,

Post by Janina Sajka
or maybe even offer to take over that package. I have not felt it
something I wanted to take on.

Post by Janina Sajka
Janina
https://bugzilla.rpmfusion.org/show_bug.cgi?id=3807

2016-07-19 23:01:04 CEST ---

Post by Janina Sajka

Post by Janina Sajka
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

Post by Janina Sajka

Post by Janina Sajka
update the version field of this bug (and re-open it if it has been closed).

https://bugzilla.rpmfusion.org/userprefs.cgi?tab=email

Post by Janina Sajka

Post by Janina Sajka
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You reported the bug.

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

--
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup