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?
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'm replacing an Hp Officejet 4620 after print heads problems in 2 years of
I got tired with inkjet and their imitations and due to my sporadic needs
and only b/w, I would like to buy a black white laserjet with scanner
I see the product in object that seems quite good from an hw point of view
but it is not clear to me the status with Linux support, both with printing
Anyone using this product or similar one in the line?
Thanks in advance,
Fedora 28, x64
1) Is there a way to convert a Fedora hard drive that
is set up to boot off the old BIOS into a EUFI boot?
2) Is there a way to convert a Fedora hard drive that
is set up to boot off the old BIOS into a dual
BIOS and EUFI boot drive?
For some time now (i.e. multiple Fedora releases) I've noticed that on two
of my laptops that use EFI instead of BIOS booting, all of the startup
lines from SystemD are shown twice. No big issue but o a whim I decided to
google the problem and couldn't find much.
I can't be the only person that's seen this though... Any easy fix known?
I finally found a flash drive I like for installing
Fedora directly (not live). Flash drives break down
when a lot of small files go fly around and bog
the OS down and often corrupt. I have had issues
with both Kanguru and Kingston drives.
I also test a Patriot drive. They goof around with
parameters so that large file transfers give good
numbers at the expense of small file transfers
being so bad the stick almost unusable. Fedora on
a Patriot was a joke.
On a lark I tried a Samsung MUF-64BE3/AM and a
Samsung MUF-64DA1/WW. Both are USB 3.1.
And Wow. On two customer machines running USB 2,
they preformed flawlessly. Actually even faster than
the native Windows. And no corruptions and no ten
minutes to shutdown Firefox.
On my own USB 3.0 machine, they ran almost as 1/2 as
fast as native (I have an NVMe drive).
Both these guys ate Fedora 28 Xfce x64 alive, meaning
it handled multiple small file transfers with ease.
Anyone want to know the special tweaks to run
off a USB drive, drop me a line.
Computers are like air conditioners.
They malfunction when you open windows
One of our Fedora 28 machines now longer boots. Services fail to start, and there are a lot of errors like:
[ 3881.765993] systemd: dbus.service: Failed to execute command: Permission denied
[ 3881.766884] systemd: dbus.service: Failed at step EXEC spawning /usr/bin/dbus-daemon: Permission denied
for each service. gdm or a prompt on other terminals on the machine never come up, but I can ssh into the machine.
dnf doesn't work (it gives Error: Failed to synchronize cache for repo 'updates' )
any other system commands take forever (just doing `su` or querying systemctl takes a few minutes, and then usually fails).
Any thoughts on what might be causing this?