(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?
I have an up to date F28 server that boots to the grub prompt. This
started after a failed dnf update.
The computer will boot to an emergency mode command prompt if I set it up
properly from the grub prompt.
grub> set root=(lvm/fedora-root)
grub> linuxefi (hd0,gpt2)/vmlinuz-0-rescue... root=/dev/mapper/fedora-root
I can get networking working
#ls /sys/call/net <- find Ethernet device is enp3s0
# ifup enp3s0
# ping www.google.com
Now update it
# dnf update
Regenerate the grub2 config file
# shutdown -r now
It still boots to the grub prompt.
Why does it boot to the grub prompt and what do I need to do to fix it ?
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?
I've just noticed that at boot time that the FSTRIM service is
registering a failure. The failure seems to be because it is trying to
trim two windows mount points which are on the SSD, that are mounted as
RO because I can't mount them as RW due to Microsoft functionality.
Is there any way to configure the FSTRIM service to not attempt to
trim specific partitions?
I tried to upgrade a system to F29 this AM. The upgrade failed with
the following error:
Last metadata expiration check: 0:00:00 ago on Wed 31 Oct 2018 09:27:12
Problem: problem with installed package
requires libcryptopp.so.6()(64bit), but none of the providers can be
does not belong to a distupgrade repository
- cryptopp-6.1.0-2.fc28.x86_64 does not belong to a distupgrade
Any ideas on how to fix this?
Any assistance is appreciated.
I have f29 (ernel kernel-4.18.12-300.fc29 ) on machine, which is changing its place from time to
time - between two TVs. Old, and older:)
Both are connected by HDMI. Video output is fine, even acceleration is working, but sound work only
on newer of those two.
I don't know if this is regression, because this machine replaced 32b rapbery2 with kodi, which was
working without issues on both TVs (but was eaten by (not mine) dog)
I was following https://fedoraproject.org/wiki/How_to_debug_sound_problems but had not found much:
- with removed pulseaudio, the aplay -vv segfaults
- I really on pulseaudio anyway, as I need to transfer sound to this machine over network
- the diff of alsa-info.sh's is really minimal , only
for non working and
- when alsamixer is opened, then the default looks like working, and the job on old tv; but not do
nothing older tv.
- when alsamixer -c0 is opened, then the vc4-hdmi reports no control for selected device for
*both* tvs (which is same as f6 and selecting vc4-hdmi)
Does anybody have a clue what to try?
Thanx in advance form java world,
@@ -1,5 +1,5 @@
-cat: /tmp/alsa-info.TzPwpaQcKW/acpidevicestatus.tmp: No such file or directory
+cat: /tmp/alsa-info.GXybsmPDbN/acpidevicestatus.tmp: No such file or directory
cat: '/sys/module/(null)/parameters/*': No such file or directory
@@ -8,7 +8,7 @@
!!ALSA Information Script v 0.4.64
-!!Script ran on: Mon Oct 29 14:09:06 UTC 2018
+!!Script ran on: Mon Oct 29 14:15:02 UTC 2018
@@ -152,7 +152,7 @@
access 'read volatile'
Senior QE engineer, OpenJDK QE lead, Mgr.
Red Hat Czech
jvanek(a)redhat.com M: +420775390109
There's a big mail thread on fedora-devel about using a web forum
software called Discourse instead of mailing lists. The idea is that
it would invigorate the Fedora community by encouraging younger people
raised on social media and mobile platforms to contribute. One of the
targets they have mentioned is the user list, because of its nature of
short term question and answer topics. There has been push-back by
developers because they have their custom solutions all working great
around email lists for doing their work.
I'm wondering how the people who regularly use fedora-users mailing
list feel about that. Which would you prefer? Unfortunately, it's an
either / or proposal, because there is no interface in Discourse for
emails from an email list to be put in their forums, though they do
have email notification for new web messages. Would you willingly or
reluctantly migrate to the new platform?
Here are a few links from that thread.
In order to access discourse, because fedora is using the hosting
provided by discourse, you will have to grant js access to
My Nas Devices are failing to mount at boot time because the
Networkmanager Wait Online Service is failing at boot time. The
following is the output from systemctl that the boot process recommends
being run. Is there anything in that output that would indicate why the
service is failing even though the wifi adapter is indicating that it is
already active before the service fails? This issue happens every time I
bash-4.4$ systemctl status NetworkManager-wait-online.service
● NetworkManager-wait-online.service - Network Manager Wait Online
vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2018-10-23 07:38:50
AEDT; 19min ago
Process: 1656 ExecStart=/usr/bin/nm-online -s -q --timeout=30
Main PID: 1656 (code=exited, status=1/FAILURE)
Oct 23 07:38:20 localhost.localdomain systemd: Starting Network
Manager Wait Online...
Oct 23 07:38:50 localhost.localdomain systemd:
NetworkManager-wait-online.service: Main process exited, code=exited,
Oct 23 07:38:50 localhost.localdomain systemd:
NetworkManager-wait-online.service: Failed with result 'exit-code'.
Oct 23 07:38:50 localhost.localdomain systemd: Failed to start
Network Manager Wait Online.