new boot error message
by Jon LaBadie
I'm on a Fedora 38 workstation.
On reboots, say after a dnf update, I've started
getting an error message I'd not seen before.
I don't recall the exact syntax but it basically
says "/efi/Fedora" doesn't exist.
System still boots normally.
I have an "efi" partition, 1st partition on the
system disk. After boot it is mounted under /boot.
The efi partition contains a subdirectory "EFI"
and EFI contains a subdirectory "fedora". So after
boot I can see "/boot/efi/EFI/fedora".
Any explanation for the error message?
tnx
--
Jon H. LaBadie jonfu(a)jgcomp.com
4 weeks
Stuck at grub prompt after reordering partitions
by Klaus-Peter Schrage
After many years of maintaing dual boot setups (Fedora/Windows) my
harddisk layout got a bit confusing: Linux and Windows partition were
scattered on mainly two harddisks (all gpt). I was able to free a third
harddisk (ssd) and copied the linux partitions boot, root and home over
to the new disk, where they now reside as /dev/sda1, /dev/sda2
and /dev/sda3.
I left the efi-partition on the disk /dev/sdc together with Windows 11.
As in /etc/fstab all partitions are identified by their UUID, I didn't
feel a need to adjust that file.
Trying to boot brought me to the grub command line prompt. After some
trial and error, the appropriate sequence of grub commands (set
root=..., linux ..., initrd ...) made the system boot into a fully
working Fedora 39 installation.
From there I tried to repair GRUB2, following the guidelines at
https://fedoraproject.org/wiki/GRUB_2?rd=Grub2#Updating_GRUB_2_configurat...
namely those three steps:
# rm /boot/efi/EFI/fedora/grub.cfg
# rm /boot/grub2/grub.cfg
# dnf reinstall shim-* grub2-efi-* grub2-common
But rebooting still gets me to the dreaded grub>.
So what am I missing?
BTW, I did NOT use the grub2-install command which shoud not be used on
UEFI systems.
4 weeks
pulseaudio misbehaviour on remote
by Neal Becker
I'm running a connection to a remote server via x2go. The remote desktop
is xfce.
When I leave this unattended for some time, I come back to find that
pulseaudio is sucking 64GB of VM. Needless to say, I don't really need PA
running on it, but I haven't seen how to disable it. Also this seems like
a bug, PA has no business using 64GB of VM.
I've just been killing it when I notice, but I'd rather fix the problem.
Any thoughts?
4 weeks, 1 day
What's up with debuginfod?
by Sam Varshavchik
Can anyone vouch for having a reliable, established, experience with
debuginfod?
My 'make check' runs valgrind a bunch of times. Right now, each invocation
is sitting and doing nothing for about ten minutes, before it apparently
times out downloading something from debuginfod.fedoraproject.org:
poll([{fd=9, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND}], 1, 0) = 0 (Timeout)
poll([{fd=9, events=POLLIN}], 1, 1000) = 0 (Timeout)
poll([{fd=9, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND}], 1, 0) = 0 (Timeout)
poll([{fd=9, events=POLLIN}], 1, 1000) = 0 (Timeout)
poll([{fd=9, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAN
Whether using valgrind or gdb, I find that debuginfod gets stuck more often
than not, and this is getting old. I don't know what it's beef is. I can
reach debuginfod.fedoraproject.org on port 443 without any issues.
After perusing the man page I set DEBUGINFOD_MAXTIME=10, and things are
slowly, slowly moving forward. But I'm wondering if anyone found debuginfod
to be reliable.
1 month
a tool like xte(1) but for Wayland?
by Don Marti
I have some old shell functions that use xte to fake some keyboard
input. For example, this is a function to run its argument(s) in a new
gnome-terminal tab.
run_in_tab ()
{
xte 'keydown Control_L' 'keydown Shift_L' 'key t' 'keyup Control_L'
'keyup Shift_L' 'sleep 1' "str exec $*" 'key Return'
}
Is there a tool packaged in new Fedora versions that's like xte, but for
Wayland?
1 month
Which keys did I hit?
by Sam Varshavchik
My fingers had a mind of their own and apparently hit some combination of
keys that had a very weird result.
I'm using an XFCE desktop. And, apparently, it became, maybe, fourty or so
virtual pixels wider. Of course, the monitor still has the same number of
pixels, so what was happening is that moving the mouse pointer to one of the
edges scrolled the entire desktop slightly to reveal the extra virtual space
on that side. Moving the mouse pointer to the other edge scrolled the
virtual window on the desktop in the other direction, to the other side of
the now-larger virtual desktop.
It was a pretty cool effect, so after I had my fun I logged out and back in,
and things were back to normal. But I'm wondering what keys did I hit, I
looked through settings and didn't find anything relevant…
1 month
systemd-networkd-wait-online times out
by Sam Varshavchik
I've been made aware that it takes two minutes for systemd-networkd-wait-
online.service to spin its wheels, before giving up with a squeal:
Apr 09 22:03:30 shorty.email-scan.com systemd[1]: Starting systemd-networkd-wait-online.service - Wait for Network to be Configured…
Apr 09 22:05:30 shorty.email-scan.com systemd-networkd-wait-online[1282]: Timeout occurred while waiting for network connectivity.
Apr 09 22:05:30 shorty.email-scan.com systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE
Everything comes up normally. Network connectivity on this box is normal.
Originally I was looking into why it took a long time for keepalived to come
up on this box and grab its virtual IP address, and I determined that
keepalived simply started after quite a bit of time elapsed before systemd
deemed it necessary to start keepalived. And when I tried to figure out
why's that, I discovered this to be the culprit.
I did not find the man pages to be illumanating, just a bunch of systemd man
pages referring to each other, with no clear indication as to what the issue
is.
At the time I obtained the above logs I was ssh-ed into the box in question,
which was fully up. But systemd-networkd-wait-online was under the
impression that it wasn't, apparently, and decided to croak after two
minutes elapsed.
So, how do I troubleshoot this?
1 month, 1 week
Failed to find a suitable stage1 device
by Michael Hennebry
While trying to install from Fedora-Workstation-Live-x86_64-39-1.5.iso ,
I got the following:
Failed to find a suitable stage1 device:
EFI System Partition must be mounted on one of /boot/efi.;
EFI System Partition cannot be of type None;
EFI System Partition cannot be of type NTFS;
EFI System Partition must be mounted on one of /boot/efi.;
EFI System Partition cannot be of type ext4.;
EFI System partition must be mounted on one of /boot/efi.;
... repetition
I am not happy.
The target is an HP EliteBook (not EliteDesk).
The partition editing was done with Windows 10,
which is still present.
According to Anaconda:
sda1 partition efi 100 MiB
sda2 partition 16 MiB
sda3 partition ntfs 220.83 GiB
sda4 partition ext4 97.66 GiB slash /
sda5 partition ext4 97.66 GiB home /home
sda6 partition ext4 19.53 GiB var /var
free space free space 517.58 GiB
sda7 partition ntfs 509 MiB
sda3, sda5 and sda6 exist because I used the Windows 10 tool.
I left formating up to anaconda.
Anaconda has not yet formatted them.
What is going on?
How do I do the installation?
I do not rmember my last pain-free install.
--
Michael hennebry(a)mail.cs.ndsu.NoDak.edu
"SCSI is NOT magic. There are *fundamental technical
reasons* why it is necessary to sacrifice a young
goat to your SCSI chain now and then." -- John Woods
1 month, 1 week
[Now Playing] Intel Open CL Test Day
by Sumantro Mukherjee
Hey All,
We're hosting an Intel OpenCL Test Day[0] and we need your expertise!
Join us on 2024-04-09 to put Intel's OpenCL through its paces. Your
feedback will be invaluable in shaping the future of this technology.
Together, let's push the boundaries of performance and innovation.
Intel's OpenCL (Open Computing Language) is a powerful framework for
parallel computing across CPUs, GPUs, and FPGAs. It enables developers
to harness the full potential of Intel's hardware, optimizing
performance for a wide range of applications from AI and machine
learning to high-performance computing. By participating in our test
day, you'll gain hands-on experience and contribute directly to the
enhancement of Intel's OpenCL platform for Fedora 40.
[0] http://fedoraproject.org/wiki/Test_Day:2024-04-09_Intel_Open_CL
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
1 month, 1 week
