My Fedora 40 experiences
by Stephen Morris
I used dnf to system-upgrade to F40, which downloaded all the relevant
packages, and then I rebooted through dnf.
The restart updated all the packages and automatically rebooted when it
was finished.
When the grub menu was displayed after the reboot it was obvious that
the upgrade did not update the grub config as there was no entry to boot
off the F40 installed kernel.
I booted to the display manager which I think is still gdm, and the
first thing I noticed there was the "plasma on xorg" selection had been
removed but the "Gnome on xorg" and "Gnome Classic on xorg" were still
there.
I selected the "Plasma" entry and booted into Plasma.
Having loaded Plasma I then went into the system entries menu and went
through all the options again, and it was obvious from this that the
display options I had configured with F39 had been wiped with F40. I
configured the display settings again and set the new HDR option as I
have a HDR monitor.
After the configuration changes I rebuilt the grub menus using
grub2-mkconfig to get a boot entry for the new kernel, and rebooted.
With the reboot from the new kernel, and for that matter any of the
older kernels, I got a message that the nvidia driver was not found and
it was falling back to the nouveau driver, I don't know how as the
nvidia driver was black listed in the grub menus.
From the display manager I loaded Plasma as I did after the first
upgrade boot, and Plasma displayed a black screen and never went any
further, irrespective of how long I left it for, and the only way I
could get out of that state was to use the physical reset button on the
computer.
On reboot, if I selected "Gnome" or "Gnome on Xorg", gnome would start
up quite happily, but logging out and starting Plasma would still hang
the computer.
So rebooting again to the display manager login screen, I used
ctrl+alt+F2 to switch to a terminal login process. Logging into the
terminal the first thing I did was use mokutil to check the uefi status
and it told me that uefi was disabled even though it was enabled in the
bios.
I checked whether the signing key was enrolled and it was, but the
system wasn't using the nvidia driver even though it was installed, and
a reinstall of kmod-nvidia and akmod-nvidia did nothing to alleviate the
issue.
So I uninstalled the kmod-nvidia module, and did a force re-enroll of
the uefi signed key (potentially with a new key), and then rebooted to
go through the mokutil enrolment required at boot. This did not resolve
the Plasm start issue, so I loaded Gnome.
Once in Gnome I started Firefox Nightly to do some net searches to see
if I could find a solution, and the one thing that did happen at this
point was the boot did not display the "falling back to nouveau"
message, but the start of firefox displayed a message that a gpu
couldn't be found on pci. Looking for a resolution to this I found an
entry about, as part of installed nvidia drivers, to ensure the gpu
firmware was also installed.
So I did a dnf install nvidia-gpu-firmware which was then installed as
it hadn't been already.
After installing the firmware I rebooted and started Plasma, which
successfully started without issues, and when I checked the video driver
it was finally using the nvidia driver.
This was a lot of work to resolve, and is the worst experience I've had
with any fedora system upgrade.
regards,
Steve
21 hours, 51 minutes
Any idea how to solve: upgrade to F40 results in Cisco VPN not
finding required libraries
by Ranjan Maitra
I have Cisco VPN version cisco-secure-client-linux64-5.0.05040 which is what is the current version released by our workplace.
The complete upgrade to Fedora 40 from Fedora 39 appears to have resulted in:
You are missing the required libraries for the authentication method you requested.
whenever I try to use the VPN and basically I can not connect.
Any suggestions as to how to get around this problem?
Many thanks in advance!
Best wishes,
Ranjan
1 day
nmcli -d ??
by ToddAndMargo
Hi All,
In CentOS 8, I have the following command:
# nmcli -d
example output:
DEVICE TYPE STATE CONNECTION
ens3 ethernet disconnected ens3
lo loopback unmanaged ---
But under Fedora 39, the same command gives me
# nmcli -d
Error: Option '-d' is unknown, try 'nmcli -help'.
I really like the output that CentOS gives. Is
there a way to get it back? Not finding anything
under --help or search.brave.com
Many thanks,
-T
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 day, 7 hours
What have I used too big a hammer on?
by Tom Horsley
Yesterday there were a couple of hours long xfinity cable outages and
I decided to try to connect over 5G via my phone's hotspot and the
built in wireless on my computer's motherboard.
It could connect, but I couldn't see anything on the internet, I suspect
because I beat NetworkManager into submission with too big a hammer
on my normal network setup where it kept not using my internal LAN
DNS, so my big hammer was to edit
/etc/NetworkManager/NetworkManager.conf
in in the mail section add
[main]
dns=none
Then remove the /etc/resolv.conf symlink and replace it with a fixed
content file with my local search and dns server so I can lookup
names for all my local stuff.
So, my question is: How to override DNS the same way, but only for
my hardwired ethernet connection, while allowing me to disable that
connection and use my hotspot in time of comcast outage?
Heck, it would be even better if I could use both at the same time,
the local ethernet to get to other computers in the house and the hotspot
to access the internet (but I have a feeling my brain might never
be able to wrap around that).
1 day, 8 hours
F40 Sendmail "Connection Refused"
by Tim Evans
I have sendmail (sendmail-8.18.1-1.fc40.x86_64) on my three home
systems, its purpose being handling of LOCAL-ONLY mail. That is, output
from cron jobs, local backup scripts, and the like. (I review these
messages using good-ole command-line 'mailx'.) External mail is handled
by my hosting provider's server, to which I connect with Thunderbird via
IMAP.
Two of the three systems are handling local mail correctly. One,
however, is failing with:
# mailq
/var/spool/mqueue (3 requests)
-----Q-ID----- --Size-- -----Q-Time-----
------------Sender/Recipient-----------
44HBtEsB003461 5910 Fri May 17 07:55 MAILER-DAEMON
(Deferred: Connection refused by
kestrel.mynetworksettings.co)
<root(a)kestrel.tkevans.com>
journalctl reports pretty much the same error message.
This began with the upgrade to F40 yesterday
Haven't dealt with sendmail.cf settings in many, many years, but don't
think there is misconfig there, as all three systems have identical
/etc/mail/sendmail.cf files.
What stands out here is the reference to "kestrel.mynetworksettings.co".
NOTE: ".co" not ".com". Where does this come from, and what do I need to
do to reset it to the actual local domain name?
Thanks.
1 day, 14 hours
postfix fails to start on boot
by Alex
Hi,
I have a fedora38 server with postfix-3.7.9 (although this problem has
existed for a long time) that fails to start because I believe the server
has multiple interfaces.
ifconfig shows just the primary ethernet interface, but "ip addr" shows the
rest. There are five total interfaces in this multi-instance postfix config.
Here are the related boot messages from journalctl -xb0:
postfix[1360]: egrep: warning: egrep is obsolescent; using grep -E
postfix[1371]: fatal: parameter inet_interfaces: no local interface found
for 130.250.NNN.197
postfix[1374]: fatal: parameter inet_interfaces: no local interface found
for 130.250.NNN.198
postfix[1375]: fatal: parameter inet_interfaces: no local interface found
for 130.250.NNN.199
postfix[1376]: fatal: parameter inet_interfaces: no local interface found
for 130.250.NNN.200
postfix[1379]: fatal: parameter inet_interfaces: no local interface found
for 130.250.NNN.201
Each of the IPs correspond to a different postfix instance.
After the system boots, I can start postfix successfully with just "service
postfix start".
Is it perhaps trying to start before networking is available? This would be
odd because the problem has persisted for quite a while, and I would have
thought something like that would have been fixed long ago.
Perhaps related to the difference between ifconfig and ip? Where is the
egrep coming from? I don't see it in the systemd file:
# ls -l /etc/systemd/system/multi-user.target.wants/postfix.service
lrwxrwxrwx 1 root root 39 Jan 24 2023
/etc/systemd/system/multi-user.target.wants/postfix.service ->
/usr/lib/systemd/system/postfix.service
1 day, 14 hours
boot fails to mount after fc39 upgrade
by Alex
Hi,
I just upgraded my fc38 desktop to fc39 using the regular "dnf upgrade"
method, as I've done forever. However, this time boot fails with messages
related to failed dependencies and it being unable to mount any partitions
other than boot and root.
I managed to get networking working so I can copy off some of the config.
Here's what's mounted when it fails:
Filesystem Size Used Avail Use% Mounted on
devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs 32G 0 32G 0% /dev/shm
tmpfs 13G 2.1M 13G 1% /run
efivarfs 192K 155K 33K 83% /sys/firmware/efi/efivars
/dev/sdc4 1.8T 40G 1.7T 3% /
/dev/loop1 6.9M 6.9M 0 100% /var/lib/snapd/snap/dalfox/227
/dev/loop0 104M 104M 0 100% /var/lib/snapd/snap/core/16928
tmpfs 32G 0 32G 0% /tmp
/dev/sdc2 974M 352M 555M 39% /boot
/dev/sdc1 599M 7.5M 592M 2% /boot/efi
I can mount my home directory manually, so it's not a problem with the
disk. I also tried replacing the UUID in /etc/fstab with the actual device
name and rebooting, but that didn't help either. I've also tried booting
into the previous fc38 kernel that I know booted properly.
I'm used to seeing the ext4 kernel module installed with lsmod, but it
seems that's not needed anymore?
There's also a message about selinux relabeling - I've also disabled
selinux on boot using security=0 so I don't think that's the problem.
Here are a few of the "fail" messages from "journalctl -xb 0"
May 15 15:31:23 fedora systemd[1]: Mounting home-alex.mount - /home/alex...
May 15 15:31:23 fedora mount[928]: mount: /home/alex: mount failed: Invalid
argument.
May 15 15:31:23 fedora systemd[1]: home-alex.mount: Mount process exited,
code=exited, status=1/FAILURE
May 15 15:31:23 fedora systemd[1]: Dependency failed for local-fs.target -
Local File Systems.
May 15 15:31:23 fedora systemd[1]: Dependency failed for
selinux-autorelabel-mark.service - Mark the need to relabel after reboot.
May 15 15:31:23 fedora systemd[1]: selinux-autorelabel-mark.service: Job
selinux-autorelabel-mark.service/start failed with result 'dependency'.
May 15 15:31:23 fedora systemd[1]: local-fs.target: Job
local-fs.target/start failed with result 'dependency'.
May 15 15:31:23 fedora systemd[1]: local-fs.target: Triggering OnFailure=
dependencies.
Here's my /etc/fstab. I've commented out all the secondary mount points
other than my home directory after they all failed too.
# cat /etc/fstab|grep -Ev '^$|#'
UUID=39b42604-3f56-4537-b738-b79656379920 / ext3
defaults 1 1
UUID=ca677379-15de-4b51-8728-e1c5591874fb /boot ext4
defaults 1 2
UUID=E6F8-57A9 /boot/efi vfat
umask=0077,shortname=winnt 0 2
UUID=e8add1bc-a807-4547-8177-52768f24bd25 none swap
defaults 0 0
UUID=e9be12f8-7d21-4992-9018-d5032124264d /home/alex ext4
defaults,group,user,exec 0 0
3 days, 8 hours
Fedora 39/40 hangs on boot after system update
by Meikel
Hi folks,
I have an ASUS N550JK laptop running Fedora XFCE. I didn't use it for
some months. It was running Fedora 39 XFCE. Today I did an update. After
the update it hangs on boot. Because I removed "rhgb quiet" from
GRUB_CMDLINE_LINUX I can see messages while the system boots. It seems
that it hangs after a message like
... nouveau ... Enabling HDA controller
As "nouveau" seems to be a driver for the graphic card and I can also
see that the update probably installed a newer kernel
6.8.9-200.fc39.x86_64 I did a reboot with choosing an older kernel
6.6.9-200.fc39.x86_64 from boot menu. With this older kernel the system
is able to boot without problems.
Then I did an upgrade to Fedora 40 XFCE because I hoped that this could
fix the problem. But with Fedora 40 I have the same problem. On starting
with the now very new kernel 6.8.9-300.fc40.x86_64 it hangs on boot with
the same message
... nouveau ... Enabling HDA controller
If I start Fedora 40 with the older kernel 6.6.9-200.fc39.x86_64 from
boot menu then the system boots without problems.
For providing you some information about the hardware, I did run
sudo dmidecode
but this gives very very much information. Here is only a short snippet
with some basic information:
System Information
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: N550JK
Version: 1.0
SKU Number: ASUS-NotebookSKU
Family: N
To find something about the graphic card I did run
dmesg | grep nouveau
and in the very first line I can see that it seems to be a NVIDIA GM107
(117110a2):
[ 2.426287] nouveau 0000:01:00.0: NVIDIA GM107 (117110a2)
[ 2.442106] nouveau 0000:01:00.0: bios: version 82.07.2a.00.02
[ 2.526832] nouveau 0000:01:00.0: fb: 2048 MiB DDR3
[ 2.526889] nouveau 0000:01:00.0: bus: MMIO read of 00000000
FAULT at 022554 [ PRIVRING ]
[ 3.197385] nouveau 0000:01:00.0: DRM: VRAM: 2048 MiB
[ 3.197387] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[ 3.197389] nouveau 0000:01:00.0: DRM: Pointer to TMDS table not
found
[ 3.197390] nouveau 0000:01:00.0: DRM: DCB version 4.0
[ 3.198239] nouveau 0000:01:00.0: DRM: MM: using COPY for buffer
copies
[ 3.198466] [drm] Initialized nouveau 1.4.0 20120801 for
0000:01:00.0 on minor 1
[ 3.198535] nouveau 0000:01:00.0: [drm] No compatible format found
[ 3.198537] nouveau 0000:01:00.0: [drm] Cannot find any crtc or
sizes
[ 52.988052] nouveau 0000:01:00.0: Enabling HDA controller
[ 59.107580] nouveau 0000:01:00.0: Enabling HDA controller
[ 59.227433] nouveau 0000:01:00.0: bus: MMIO read of 00000000
FAULT at 619444 [ PRIVRING ]
[ 97.171565] nouveau 0000:01:00.0: Enabling HDA controller
[ 97.288155] nouveau 0000:01:00.0: bus: MMIO read of 00000000
FAULT at 619444 [ PRIVRING ]
I do not want to manually choose the kernel each time when I boot the
computer. What can I do?
Regards,
Meikel
3 days, 12 hours
plocate?
by Geoffrey Leach
New install of Fedora 40. It is unclear what program should be run to
create plocate.db.
3 days, 16 hours
/boot too small
by Patrick Dupre
Hello,
During an update, I get
Error Summary
-------------
Disk Requirements:
At least 7MB more space needed on the /boot filesystem.
How can I fix it without currently resizing /boot?
Thank
drwx------. 5 root root 4096 May 14 08:36 grub2
lrwxrwxrwx. 1 root root 45 Mar 7 13:24 symvers-6.7.7-100.fc38.x86_64.xz -> /lib
/modules/6.7.7-100.fc38.x86_64/symvers.xz
-rw-------. 1 root root 81850041 Mar 7 13:24 initramfs-6.7.7-100.fc38.x86_64.img
-rw-r--r--. 1 root root 269378 Mar 1 01:00 config-6.7.7-100.fc38.x86_64
-rw-r--r--. 1 root root 8851783 Mar 1 01:00 System.map-6.7.7-100.fc38.x86_64
-rwxr-xr-x. 1 root root 14794568 Mar 1 01:00 vmlinuz-6.7.7-100.fc38.x86_64
lrwxrwxrwx. 1 root root 45 Feb 13 17:38 symvers-6.7.4-100.fc38.x86_64.xz -> /lib
/modules/6.7.4-100.fc38.x86_64/symvers.xz
-rw-------. 1 root root 81905180 Feb 13 17:37 initramfs-6.7.4-100.fc38.x86_64.img
-rw-r--r--. 1 root root 269327 Feb 5 01:00 config-6.7.4-100.fc38.x86_64
-rw-r--r--. 1 root root 8850577 Feb 5 01:00 System.map-6.7.4-100.fc38.x86_64
-rwxr-xr-x. 1 root root 14806856 Feb 5 01:00 vmlinuz-6.7.4-100.fc38.x86_64
lrwxrwxrwx. 1 root root 46 Jan 25 13:39 symvers-6.6.13-100.fc38.x86_64.xz -> /li
b/modules/6.6.13-100.fc38.x86_64/symvers.xz
-rw-------. 1 root root 42503616 Jan 25 13:39 initramfs-6.6.13-100.fc38.x86_64.img
-rw-r--r--. 1 root root 266375 Jan 20 01:00 config-6.6.13-100.fc38.x86_64
-rw-------. 1 root root 8786049 Jan 20 01:00 System.map-6.6.13-100.fc38.x86_64
-rwxr-xr-x. 1 root root 14676712 Jan 20 01:00 vmlinuz-6.6.13-100.fc38.x86_64
-rw-r--r--. 1 root root 147744 Jan 7 01:00 memtest86+x64.bin
drwx------. 4 root root 4096 Jun 20 2023 efi
drwxr-xr-x. 2 root root 4096 Jun 20 2023 extlinux
-rw-------. 1 root root 103940590 Jul 21 2022 initramfs-0-rescue-c60d54440c4d444a9eb5a084a65edf40.img
-rwxr-xr-x. 1 root root 11802352 Jul 21 2022 vmlinuz-0-rescue-c60d54440c4d444a9eb5a084a65edf40
drwxr-xr-x. 3 root root 4096 Jul 21 2022 loader
drwx------. 2 root root 16384 Jul 21 2022 lost+found
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
===========================================================================
3 days, 23 hours
