I get *Failed to start Load Kernel Modules* during the boot.
Everytime Kernel is updated VirtualBox modules fail I have to reboot into
the new Kernel, run the following commands and then it starts working.
$ sudo akmods --force
$ sudo dracut -v -f
$ sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
Then everything starts working again and the boot error goes away. You can
found the background of the issue in the link below.
My question is how can I automate this task.
(after a looong time not using Fedora, just back to it!)
I've tried installing Fedora on a Zotac Zbox CI327 (Intel Celeron
N3450 inside) but this happens to fail. I've tried F25 but it has
not the right kernel to make it (I've read about 4.10 minimum), then
tried F26-Alpha-1.7 Live and Rawhide-20170518 Live but none could
reach the graphical login. They both boot, some steps take a lot of
time and I end up in a state I don't understand but which is not
Here's a link to a rdsosreport.txt file generated using Rawhide, I must
admit that I don't know what to do now..
BTW, I could install and run a Ubuntu 17.10 daily
(artful-desktop-amd64-20170519.iso) - wow it starts up pretty quickly -
and that gave me hope!
Any hint or experience w/ such hardware?
After the last system update in F28 Network Manager is not
retaining the wifi password entered into its security tab. When I enter
the password and select apply then 'OK' to exit network manager, when I
get back in the password is gone. Is anyone else seeing this issue or
have any tips on how to rectify this issue?
So... I did a "sudo dnf upgrade" and things seemed to do well.
However, when I rebooted, it hangs on bootup with the statment "Holding
until bootup processes complete" or something like that -- I'm doing
this from memory. I tried with a couple of older kernels, but they also
I assume that this is some transient thing associated with the upgrade.
Over the years, I've had glitches appear on an upgrade and disappear on
the next upgrade. Accordingly, I'd like to boot into rescue mode and
see if I can upgrade again.
However, I've forgotten how to turn on wifi networking from rescue mode.
Can anybody point me to a tutorial?
Ever since Fedora(27) released a 4.17.x kernel, my MacBook Air (7,1)
is no longer able to boot at all. It hangs when trying to use the
NVMe disk controller:
nvme nvme0: controller is down; will reset: CSTS=0x3, PCI_STATUS=0x810
and the entire boot process eventually times out completely. If I
return to using the last 4.16.x kernel (4.16.14-200.fc27.x86_64), then
the problem does *not* reproduce, and everything boots normally.
i opened a bug for this problem:
however, I'm surprised that no one else has run into this issue. Any
ideas or suggestions?
I have two drives mounted on a F28 system. Both are identical 4TB drives. The second one is empty. I am concerned about the first one failing so would like to copy the contents (which are around 3.7 TB) to the second.
What is the fastest way to copy the contents of the first drive to the second? I was using rsync, but is there a better way?
Many thanks in advance for any advice,
Important Notice: This mailbox is ignored: e-mails are set to be deleted on receipt. Please respond to the mailing list if appropriate. For those needing to send personal or professional e-mail, please use appropriate addresses.
It seems Tiger-vncserver is broken WRT polkit for any spin other than
gnome. Definitely not Xfce that I use. The work around is nasty:
Connect via SSH and run vncserver from the command line. But probably
can do it better via SCREEN and just forget about that screen session...
So it is time to look at the alternatives. I know they are out there
and have been talked about on this list, but my search foo is weak (as
always). So can I have a bit of help in figuring out what to replace my
decades-old connection to VNC?
I just upgraded one of my machines to FC29 Beta. Looks
pretty. Haven't had a chance to play with it yet.
Here are my upgrade notes;
FC 28 -->> FC 29:
# rpm --rebuilddb
# rpm -Va --nofiles --nodigest
if anything is too new, do a
# dnf downgrade offender(s)
# dnf --enablerepo=* update --refresh
# dnf install python3-dnf-plugin-system-upgrade
# dnf system-upgrade download --refresh --releasever=29 --allowerasing
# dnf clean packages <-- optional
# dnf system-upgrade reboot
I'm using f28 cloud on AWS as a compute farm. It seems that instances
randomly shutdown within hours of starting. An example log:
Fedora 28 (Cloud Edition)
Kernel 4.16.3-301.fc28.x86_64 on an x86_64 (ttyS0)
Stopping Restore /run/initramfs on shutdown...
[[0;32m OK [0m] Removed slice system-sshd\x2dkeygen.slice.
Stopping User Manager for UID 1000...
In this case after about 4 hours it seems to have spontaneously shutdown.
This happens with high probability - maybe 2/10 instances I start
Any ideas what's going on? I'm just wondering if this is something specific
to fedora cloud edition, because it doesn't seem to be a common complaint on
AWS (most of which is ubuntu).