Using Fedora 25 on my laptop I found out it supports 5ghz. Great, some
more speed, since the 2.4ghz band is a bit crowded in my
However, both NetworkManager an iwconfig report only a poor 6m...:
wlp3s0 IEEE 802.11 ESSID:"<very secret>"
Mode:Managed Frequency:5.26 GHz Access Point:
Bit Rate=6 Mb/s Tx-Power=20 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Link Quality=65/70 Signal level=-45 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Can't be that bad.... Luckily, my (Fritz) access point reports a
healthy 650 Mb. Also, downloading a large file goes easily 2x faster
from what you would expect from reported transfer rate.
I noticed this behaviour before, reporting only 1 MB on an older
What's happening here? I look a bit like large number (>100 Mb) is cut
of to only the first digit. Anyone seen this before? How to handle?
Some details about my wireless nic:
03:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
Network Adapter (rev 32)
Subsystem: Bigfoot Networks, Inc. Device 1535
Flags: bus master, fast devsel, latency 0, IRQ 129
Memory at df200000 (64-bit, non-prefetchable) [size=2M]
Capabilities:  Power Management version 3
Capabilities:  MSI: Enable+ Count=1/8 Maskable+ 64bit-
Capabilities:  Express Endpoint, MSI 00
Capabilities:  Advanced Error Reporting
Capabilities:  Virtual Channel
Capabilities:  Device Serial Number 00-00-00-00-00-00-00-
Capabilities:  Latency Tolerance Reporting
Capabilities:  L1 PM Substates
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci
> Date: Sat, 21 Jan 2017 14:10:43 -0700
> From: stan <stanl-fedorauser(a)vfemail.net>
> Subject: Re: Spectacular F24 to F25 dnf Upgrade Failure
> To: users(a)lists.fedoraproject.org
> Message-ID: <20170121141043.3a363873(a)vfemail.net>
> Content-Type: text/plain; charset=UTF-8
> What was the command you used to do the upgrade? Is there anything
> unusual about your installation?
I used 'dnf system-upgrade download --releasever=25' follow by 'dnf
system-upgrade reboot'. Nothing terribly unusual. Typical dual boot
Win10 & Fedora on a 3 year old HP Envy 15t laptop with two SSDs.
> Does windows still boot properly?
Yes, Win10 still running fine.
> You should open a bugzilla against dnf to document your experiences
> and allow the potential to get this fixed for the future.
Agreed. Unfortunately, I didn't save enough detail before moving on. I
will try to recreate and capture what I need.
> Whew, that's a bad experience.
> I'm not knowledgeable enough to help you, but there are some experts
> on the list, so maybe they'll be able to help you recover.
> It is because of potential experiences like yours that I always do my
> upgrades to new versions while leaving my old version intact. You
> could just create the new partitions, and rsync your old version to the
> new partitions before doing the upgrade. Then, if disaster strikes,
> you have a fallback position of a working system.
I usually use this laptop as my test machine. If it works here, then
I'll run it on my other Fedora machines. For my main workstation,
that's always done with a very cautious approach.
Maybe it's just me but I tend to have more issues with the odd numbered
releases. Call my superstitious.
Anyway, last night I did a full re-install over this mess with a F25 net
install USB image and that failed as well. With this latest attempt I
deleted and recreated all partitions except for the shared efi
partition. I used a basic ext4 partitioning scheme (/boot; /boot/efi;
/; swap). It seemed like the install was going well but on reboot it
failed. From the logs, it appears the new grub config written by the
installer is looking for a device UUID that doesn't exist.
Maybe I should clear out the /boot/efi/EFI/fedora directory before
This morning I ran one additional test. I did a fresh install from a
F25 XFCE Live USB. This was successful, but it leaves me with a ton of
reconfiguration and restoration work. Once I get everything up and
running again I will do some additional tests with the F25 net installer
to see if I can accurately document what happened.
I recall my last posts about this problem (complete shutdown impossible
In his hanswer, Chris Murphy suggested to use these tests :
First test: sync && reboot -f shows that it is not a kernel bug.
I went to the page listing the submitted bugs for systemd and I found
this answer to a similar problem:
<quote from Kay Sievers>
Systemd does not support "fake block devices". This needs to be provided by
the raid tools themselves and hook up into systemd.
Most of the things are done today by (mostly weird) shell scrips provided
by the distributions. Systemd has currently no plans to support MD or LVM
We provide minimal dis-assembly support for device-mapper volumes, something
similar could probably be done for MD, but someone needs to do it, and it
would need to be reasonable simple and not involve running daemons,
to command line tools or linking against uncommon libraries.
So, it seems that the bug is from Fedora and some "*mostly weird shell
by the distributions*".
Where do I report my problem (with tons of log provided by journalctl,
logwatch, and some other tests...)
It could be kind from fedora to say that Raid is not fully supported by
systemd and to provide an alternative if people want to have a RAID
system (with encryption).
For how many years now systemd has been adopted by Fedora?
Thank you for attention.
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 8394 5849
I downloaded & unpacked Neon Eclipse on my new installed Fedora 25 KDE desktop.I unzipped in my /opt directory. I did all operation using root use. Now I wanted to use as normal user but unable to run using CLI. I followed the instruction provided
tar -xvzf eclipse-java-mars-2-linux-gtk-x86_64.tar.gz -C /opt
chmod -R +r /opt/eclipse
chmod 755 /usr/bin/eclipse
## Create following file, with our favourite editor ##
## Add following content to file and save ##
But I am getting below error:
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. eclipse
Please help me on this.
I just installed fedora 25 workstation, 64 bit, and updated all
the packages. There are two things that don't work so far, and
*maybe* they are related, so here they go:
1) I have also installed KDE, OpenBox and other window managers.
But when I reboot and get the login screen, I see no menu to
select the window manager
2) I have english as default language, but italian keyboard selected.
it works... until another uses logs in. After that, when I switch
user to go back to my own session, I find the desktop using the
ENGLISH keyboard layout, and the keyboard switching widget in the
taskbar doesn't work.
How do I fix these things?
after upgrade to F25, panel locks randomly.
I have KDE and plasma5.
When it happens CTRL+ALT+F2 and back CTRL+ALT+F1 works for me.
I wonder if I can clear something inside .config, something that is recreated
fresh after logoff and login, to fix the issue
or should I ask on ked mlists?
Many thanx in advance
dnf update says:
Skipping packages with broken dependencies:
perl x86_64 4:5.22.3-366.fc24 updates 6.0 M
perl-Attribute-Handlers noarch 0.97-366.fc24 updates 76 k
perl-Devel-Peek x86_64 1.22-366.fc24 updates 79 k
perl-Devel-SelfStubber noarch 1.05-366.fc24 updates 62 k
perl-Errno x86_64 1.23-366.fc24 updates 63 k
perl-ExtUtils-Embed noarch 1.32-366.fc24 updates 66 k
perl-ExtUtils-Miniperl noarch 1.05-366.fc24 updates 63 k
perl-IO x86_64 1.35-366.fc24 updates 128 k
perl-IO-Zlib noarch 1:1.10-366.fc24 updates 67 k
perl-Locale-Maketext-Simple noarch 1:0.21-366.fc24 updates 66 k
perl-Math-BigInt-FastCalc x86_64 0.31-366.fc24 updates 68 k
perl-Math-BigRat noarch 0.2608-366.fc24 updates 77 k
perl-Math-Complex noarch 1.59-366.fc24 updates 95 k
perl-Memoize noarch 1.03-366.fc24 updates 105 k
perl-Module-Loaded noarch 1:0.08-366.fc24 updates 61 k
perl-Net-Ping noarch 2.43-366.fc24 updates 82 k
perl-Pod-Html noarch 1.22-366.fc24 updates 74 k
perl-SelfLoader noarch 1.22-366.fc24 updates 70 k
perl-Test noarch 1.26-366.fc24 updates 76 k
perl-Time-Piece x86_64 1.29-366.fc24 updates 84 k
perl-bignum noarch 0.39-366.fc24 updates 88 k
perl-core x86_64 5.22.3-366.fc24 updates 59 k
perl-devel x86_64 4:5.22.3-366.fc24 updates 553 k
perl-libs x86_64 4:5.22.3-366.fc24 updates 1.4 M
perl-macros x86_64 4:5.22.3-366.fc24 updates 59 k
perl-open noarch 1.10-366.fc24 updates 64 k
perl-tests x86_64 4:5.22.3-366.fc24 updates 1.1 M
perl-utils noarch 5.22.3-366.fc24 updates 132 k
To install the new packages, I need to remove the sagemath package !!
Actually, the issue may be due to Singular.
It looks like that there is an issue !
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
where does one find the mod_auth_tkt module for apache in current
fedora? or has it been subsumed into something else?
Robert P. J. Day Ottawa, Ontario, CANADA
One of my servers was a bit "unresponsive". After waiting about 20 seconds
for an ssh connection, the root shell seemed fine, but top showed this:
top - 06:31:36 up 3 days, 21:37, 2 users, load average: 6.00, 6.00, 6.00
Tasks: 294 total, 1 running, 277 sleeping, 0 stopped, 16 zombie
%Cpu(s): 0.1 us, 0.1 sy, 0.0 ni, 99.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0
KiB Mem : 4045896 total, 1200824 free, 346588 used, 2498484 buff/cache
KiB Swap: 2096112 total, 2093448 free, 2664 used. 3288268 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+
22031 root 20 0 156776 4092 3480 R 0.9 0.1 0:00.04
1 root 20 0 147032 7660 5616 D 0.0 0.2 0:14.18
2 root 20 0 0 0 0 S 0.0 0.0 0:00.05
3 root 20 0 0 0 0 S 0.0 0.0 0:00.01
The load average was 6. But nothing was burning CPU.
After poking around, all signs were pointing to systemd doing what systemd
# systemctl status
Failed to read server status: Connection timed out
And the 16 zombie processes were system daemons, that should've been reaped
"reboot" did nothing, of course. "reboot --force" did the trick.
Setting aside yet another systemd fiasco (on a mostly idle server that did
absolutely nothing for the last ten hours) I'm curious as to how
/proc/loadavg could end up reporting a load average of 6, without any
processes being seeming to be doing anything.