[SOLVED] urgent major problem after f39 to f40 upgrade.

On 10/10/24 2:02 PM, home user via users wrote: (I'm doing this from a windows-7 box) This morning, I did my weekly patches for my f-39 stand-alone workstation.  No problems. Then I did the upgrade to f-40.  I did not sit there and watch it. During the automatic reboot, it booted using the no

Re: urgent major problem after f39 to f40 upgrade.

> On 15 Oct 2024, at 23:42, Patrick O'Callaghan wrote: > > Isn't DNF5 part of Fedora 41, which is not yet released? dnf5 is experimental in f40. If things break when you use dnf5 in f40 then use dnf (aka dnf4) that is reliable in f40. Barry -- ___

Re: urgent major problem after f39 to f40 upgrade.

On Tue, 2024-10-15 at 15:48 -0600, home user via users wrote: > Questions: I see in /var/log/ the log file > > -rw-r--r--. 1 root root   17955 Oct 10 11:07 /var/log/dnf5.log > > I've never directly run or even installed "dnf5".  What is this?  Am I > correct assuming this has nothing to do with

Re: urgent major problem after f39 to f40 upgrade.

On 10/14/24 10:47 PM, Samuel Sieb wrote: On 10/14/24 8:36 PM, Samuel Sieb wrote: On 10/14/24 4:36 PM, home user via users wrote: On 10/14/24 4:00 PM, Samuel Sieb wrote: On 10/14/24 2:43 PM, home user via users wrote: On 10/10/24 2:02 PM, home user via users wrote: I did send the long log

Re: urgent major problem after f39 to f40 upgrade.

On 10/14/24 8:36 PM, Samuel Sieb wrote: On 10/14/24 4:36 PM, home user via users wrote: On 10/14/24 4:00 PM, Samuel Sieb wrote: On 10/14/24 2:43 PM, home user via users wrote: On 10/10/24 2:02 PM, home user via users wrote: The first command that the tool owner suggested is "dnf history lis

Re: urgent major problem after f39 to f40 upgrade.

On 10/14/24 4:36 PM, home user via users wrote: On 10/14/24 4:00 PM, Samuel Sieb wrote: On 10/14/24 2:43 PM, home user via users wrote: On 10/10/24 2:02 PM, home user via users wrote: The first command that the tool owner suggested is "dnf history list". I did that and redirected output to t

Re: urgent major problem after f39 to f40 upgrade.

On 10/14/24 4:26 PM, Jonathan Billings wrote: On Oct 14, 2024, at 18:01, Samuel Sieb wrote: There are some serious issues in that list.  Removing "passwd"??  But also, look how many packages get removed by some of those. The “passwd” package is retired as part of the libuser deprecation. h

Re: urgent major problem after f39 to f40 upgrade.

On 10/14/24 5:26 PM, Jonathan Billings wrote: On Oct 14, 2024, at 18:01, Samuel Sieb wrote: There are some serious issues in that list. Removing "passwd"?? But also, look how many packages get removed by some of those. The “passwd” package is retired as part of the libuser deprecation. h

Re: urgent major problem after f39 to f40 upgrade.

On 10/14/24 4:00 PM, Samuel Sieb wrote: On 10/14/24 2:43 PM, home user via users wrote: On 10/10/24 2:02 PM, home user via users wrote: The first command that the tool owner suggested is "dnf history list". I did that and redirected output to the text file "dnfhist.txt".  It's attached.  Fro

Re: urgent major problem after f39 to f40 upgrade.

On Oct 14, 2024, at 18:01, Samuel Sieb wrote: > > There are some serious issues in that list. Removing "passwd"?? But also, > look how many packages get removed by some of those. The “passwd” package is retired as part of the libuser deprecation. https://fedoraproject.org/wiki/Changes/Libus

Re: urgent major problem after f39 to f40 upgrade.

On 10/14/24 2:43 PM, home user via users wrote: On 10/10/24 2:02 PM, home user via users wrote: (I'm doing this from a windows-7 box) This morning, I did my weekly patches for my f-39 stand-alone workstation.  No problems. Then I did the upgrade to f-40.  I did not sit there and watch it. D

Re: urgent major problem after f39 to f40 upgrade.

On 10/10/24 2:02 PM, home user via users wrote: (I'm doing this from a windows-7 box) This morning, I did my weekly patches for my f-39 stand-alone workstation.  No problems. Then I did the upgrade to f-40.  I did not sit there and watch it. During the automatic reboot, it booted using the no

Re: urgent major problem after f39 to f40 upgrade.

On 10/14/24 2:14 PM, home user via users wrote: On 10/12/24 10:06 PM, home user via users wrote: [snip] I hope to try some of the post-upgrade tasks Monday.  But I'll skip some altogether. The RPM database rebuild failed to delete 3 files; I don't know why. They are, all in /usr/lib/sysima

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 10:06 PM, home user via users wrote: [snip] I hope to try some of the post-upgrade tasks Monday.  But I'll skip some altogether. This morning, I did many of the parts of this. Of course, I skipped the remove-retired-packages. I remain very suspicious of it and uncomfortable wi

Re: urgent major problem after f39 to f40 upgrade.

On Sun, Oct 13, 2024 at 12:07 AM home user via users wrote: > > On 10/12/24 7:31 PM, Samuel Sieb wrote: > > On 10/12/24 6:13 PM, Jeffrey Walton wrote: > >> I would definitely consider some post-upgrade clean-ups as detailed in > >>

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 7:31 PM, Samuel Sieb wrote: On 10/12/24 6:13 PM, Jeffrey Walton wrote: I would definitely consider some post-upgrade clean-ups as detailed in . At minimum, there are some old

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 6:13 PM, Jeffrey Walton wrote: I would definitely consider some post-upgrade clean-ups as detailed in . At minimum, there are some old packages and a lot of dangling symlinks t

Re: urgent major problem after f39 to f40 upgrade.

On Sat, Oct 12, 2024 at 8:16 PM Samuel Sieb wrote: > On 10/12/24 5:07 PM, home user via users wrote: > > [...] > >> What does "systemctl status gdm" show now? I have no idea how it got > >> disabled, but if it still is, then try "systemctl enable --now gdm". > > > > It showed "disabled". I enter

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 5:07 PM, home user via users wrote: On 10/12/24 5:35 PM, Samuel Sieb wrote: On 10/11/24 9:36 PM, home user via users wrote: On 10/11/24 9:50 PM, Samuel Sieb wrote: On 10/11/24 8:03 PM, home user via users wrote: On 10/11/2024 7:50 PM, Samuel Sieb wrote: [snip] I assumed that fo

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 5:35 PM, Samuel Sieb wrote: On 10/11/24 9:36 PM, home user via users wrote: On 10/11/24 9:50 PM, Samuel Sieb wrote: On 10/11/24 8:03 PM, home user via users wrote: On 10/11/2024 7:50 PM, Samuel Sieb wrote: [snip] I assumed that force would make it compile again, but apparently n

Re: urgent major problem after f39 to f40 upgrade.

On 10/11/24 9:36 PM, home user via users wrote: On 10/11/24 9:50 PM, Samuel Sieb wrote: On 10/11/24 8:03 PM, home user via users wrote: On 10/11/2024 7:50 PM, Samuel Sieb wrote: [snip] I assumed that force would make it compile again, but apparently not. But anyway, the kernel modules shoul

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 5:05 PM, Samuel Sieb wrote: On 10/12/24 3:16 PM, home user via users wrote: On 10/12/24 3:58 PM, Samuel Sieb wrote: [snip] I might be treading on old ground here, but the above output is showing that you have nouveau blacklisted so it will not start. If you are booting to a consol

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 3:16 PM, home user via users wrote: On 10/12/24 3:58 PM, Samuel Sieb wrote: [snip] I might be treading on old ground here, but the above output is showing that you have nouveau blacklisted so it will not start. If you are booting to a console because your nvidia drivers aren't work

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 4:46 PM, Felix Miata wrote: [snip] Try showing us input/output from: systemd-analyze critical-chain -bash.2[~]: systemd-analyze critical-chain The time when unit became active or started is printed after the "@" character. The time the unit took to start is printed after th

Re: urgent major problem after f39 to f40 upgrade.

home user users composed on 2024-10-12 13:35 (UTC-0600): > Felix Miata wrote: >> I believe what is happening to you often happens on several of my faster >> machines. >> The following represents evidence of what happens here using KDM or TDM and >> Xorg/X11: >> # egrep 'dev/dr\|Xorg.0.' /var/lo

Re: urgent major problem after f39 to f40 upgrade.

On 10/11/24 10:36 PM, home user via users wrote: On 10/11/24 9:50 PM, Samuel Sieb wrote: On 10/11/24 8:03 PM, home user via users wrote: Entered it. The screen blanked. After about a minute, the graphical login screen appeared. I was able to log in as root via the graphical login screen. I s

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 3:58 PM, Samuel Sieb wrote: [snip] I might be treading on old ground here, but the above output is showing that you have nouveau blacklisted so it will not start. If you are booting to a console because your nvidia drivers aren't working yet allowing nouveau to be used may get you

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 2:42 PM, home user via users wrote: On 10/12/24 2:23 AM, Stephen Morris via users wrote: On 12/10/24 14:03, home user via users wrote: On 10/11/2024 7:50 PM, Samuel Sieb wrote: [snip] I assumed that force would make it compile again, but apparently not. But anyway, the kernel mo

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 5:46 AM, David King wrote: On 10/12/24 00:36, home user via users wrote: [snip] Earlier in this thread Jeffrey Walton suggested that you do "sudo systemctl set-default multi-user.target" to temporarily set your system to a plain console login while you troubleshoot.  Did you do thi

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 2:23 AM, Stephen Morris via users wrote: On 12/10/24 14:03, home user via users wrote: On 10/11/2024 7:50 PM, Samuel Sieb wrote: [snip] I assumed that force would make it compile again, but apparently not. But anyway, the kernel modules should be available. What do the following

Re: urgent major problem after f39 to f40 upgrade.

On 10/11/24 11:58 PM, Felix Miata wrote: home user composed on 2024-10-11 22:36 (UTC-0600): Samuel Sieb wrote: Everything looks good.  Try running "systemctl start gdm". Entered it. The screen blanked. After about a minute, the graphical login screen appeared. I was able to log in as roo

Re: urgent major problem after f39 to f40 upgrade.

On 10/11/24 11:06 PM, Tim wrote: On Fri, 2024-10-11 at 18:47 -0600, home user via users wrote: By the way, I let memtest go through 8 tests before stopping it due to the cpu getting hot. It passed. You might want to check your cooling is adequate, then. I've left memtest running for hours an

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 00:36, home user via users wrote: On 10/11/24 9:50 PM, Samuel Sieb wrote: On 10/11/24 8:03 PM, home user via users wrote: On 10/11/2024 7:50 PM, Samuel Sieb wrote: [snip] I assumed that force would make it compile again, but apparently not. But anyway, the kernel modules should

Re: urgent major problem after f39 to f40 upgrade.

On Oct 12, 2024, at 00:36, home user via users wrote: > > On 10/11/24 9:50 PM, Samuel Sieb wrote: >> >> Everything looks good. Try running "systemctl start gdm". > > Entered it. > The screen blanked. > After about a minute, the graphical login screen appeared. > I was able to log in as root

Re: urgent major problem after f39 to f40 upgrade.

On 10/12/24 1:23 AM, Stephen Morris via users wrote: On 12/10/24 14:03, home user via users wrote: On 10/11/2024 7:50 PM, Samuel Sieb wrote: [snip] I assumed that force would make it compile again, but apparently not. But anyway, the kernel modules should be available. What do the followin

Re: urgent major problem after f39 to f40 upgrade.

> On 12 Oct 2024, at 09:23, Stephen Morris via users > wrote: > > I might be treading on old ground here, but the above output is showing that > you have nouveau blacklisted so it will not start. That is the correct install when using the rpmfusion nvidia drivers. Without the black listing n

Re: urgent major problem after f39 to f40 upgrade.

On 12/10/24 14:03, home user via users wrote: On 10/11/2024 7:50 PM, Samuel Sieb wrote: [snip] I assumed that force would make it compile again, but apparently not. But anyway, the kernel modules should be available. What do the following commands show: cat /proc/cmdline grep -rn nouveau /e

Re: urgent major problem after f39 to f40 upgrade.

home user composed on 2024-10-11 22:36 (UTC-0600): > Samuel Sieb wrote: >> Everything looks good.  Try running "systemctl start gdm". > Entered it. > The screen blanked. > After about a minute, the graphical login screen appeared. > I was able to log in as root via the graphical login screen. >

Re: urgent major problem after f39 to f40 upgrade.

On Fri, 2024-10-11 at 18:47 -0600, home user via users wrote: > By the way, I let memtest go through 8 tests before stopping it due to > the cpu getting hot. It passed. You might want to check your cooling is adequate, then. I've left memtest running for hours and nothing was heat stressed. Ye

Re: urgent major problem after f39 to f40 upgrade.

On 10/11/24 9:50 PM, Samuel Sieb wrote: On 10/11/24 8:03 PM, home user via users wrote: On 10/11/2024 7:50 PM, Samuel Sieb wrote: [snip] I assumed that force would make it compile again, but apparently not. But anyway, the kernel modules should be available. What do the following commands s

Re: urgent major problem after f39 to f40 upgrade.

On 10/11/24 8:03 PM, home user via users wrote: On 10/11/2024 7:50 PM, Samuel Sieb wrote: [snip] I assumed that force would make it compile again, but apparently not. But anyway, the kernel modules should be available. What do the following commands show: cat /proc/cmdline grep -rn nouveau

Re: urgent major problem after f39 to f40 upgrade.

On 10/11/2024 7:50 PM, Samuel Sieb wrote: [snip] I assumed that force would make it compile again, but apparently not. But anyway, the kernel modules should be available. What do the following commands show: cat /proc/cmdline grep -rn nouveau /etc/modprobe.d/ lsmod | grep -i nouveau lsmod |

Re: urgent major problem after f39 to f40 upgrade.

On 10/11/24 5:47 PM, home user via users wrote: On 10/11/2024 5:59 PM, Samuel Sieb wrote: On 10/11/24 3:55 PM, home user via users wrote: On 10/11/2024 11:54 AM, home user via users wrote: It's been 11+ years since I last installed that.  I don't remember how to do it or where the instructio

Re: urgent major problem after f39 to f40 upgrade.

On 10/11/2024 5:59 PM, Samuel Sieb wrote: On 10/11/24 3:55 PM, home user via users wrote: On 10/11/2024 11:54 AM, home user via users wrote: It's been 11+ years since I last installed that.  I don't remember how to do it or where the instructions are.  Please give me or tell me where to find

Re: urgent major problem after f39 to f40 upgrade.

On 10/11/24 3:55 PM, home user via users wrote: On 10/11/2024 11:54 AM, home user via users wrote: It's been 11+ years since I last installed that.  I don't remember how to do it or where the instructions are.  Please give me or tell me where to find simple,clear, current,complete, correct ins

Re: urgent major problem after f39 to f40 upgrade.

On 10/11/2024 11:54 AM, home user via users wrote: It's been 11+ years since I last installed that.  I don't remember how to do it or where the instructions are.  Please give me or tell me where to find simple,clear, current,complete, correct instructions. I sort-of merged what Joe pointed to

Re: urgent major problem after f39 to f40 upgrade.

On 10/11/24 10:54 AM, home user via users wrote: On 10/10/2024 11:49 PM, Samuel Sieb wrote: That suggests that there are no akmods installed now.  Try following the installation instructions for nvidia again and see if you can get it running. It's been 11+ years since I last installed that.

Re: urgent major problem after f39 to f40 upgrade.

On 10/11/2024 11:54 AM, home user via users wrote: It's been 11+ years since I last installed that.  I don't remember how to do it or where the instructions are.  Please give me or tell me where to find simple,clear, current,complete, correct instructions. You can find one of many HOWTOs for

Re: urgent major problem after f39 to f40 upgrade.

On 10/10/2024 11:49 PM, Samuel Sieb wrote: On 10/10/24 9:14 PM, home user via users wrote: On 10/10/2024 9:30 PM, Samuel Sieb wrote: [snip] Were you using Gnome or something else? gnome Then I wonder why gdm was disabled.  Fix the nvidia drivers first, then try starting it. akmods "Chec

Re: urgent major problem after f39 to f40 upgrade.

On 10/10/24 9:14 PM, home user via users wrote: On 10/10/2024 9:30 PM, Samuel Sieb wrote: [snip] Were you using Gnome or something else? gnome Then I wonder why gdm was disabled. Fix the nvidia drivers first, then try starting it. akmods "Checking kmods exist for 6.10.12-200.fc40.x86_64

Re: urgent major problem after f39 to f40 upgrade.

On 10/10/2024 9:30 PM, Samuel Sieb wrote: [snip] Were you using Gnome or something else? gnome systemctl status (I'll try to attach the file that I redirected the output to) systemctl status --failed × sendmail.service - Sendmail Mail Transport Agent Loaded: loaded (/usr/lib/systemd

Re: urgent major problem after f39 to f40 upgrade.

On 10/10/24 8:21 PM, home user via users wrote: On 10/10/2024 8:51 PM, Samuel Sieb wrote: Can you login and sudo to root? If so, then try these commands: Well, I just log in as root. systemctl is-system-running "degraded" systemctl get-default "graphical.target" systemctl status gdm * gd

Re: urgent major problem after f39 to f40 upgrade.

On 10/10/2024 8:51 PM, Samuel Sieb wrote: On 10/10/24 6:48 PM, home user via users wrote: I had to dnf remove jgit for the system-upgrade to work.  That was true both this morning and this evening.  I assume this is not relevant. The system-upgrade seemed to run to completion, but I could not

Re: urgent major problem after f39 to f40 upgrade.

On 10/10/24 10:51 PM, Samuel Sieb wrote: On 10/10/24 6:48 PM, home user via users wrote: I had to dnf remove jgit for the system-upgrade to work.  That was true both this morning and this evening.  I assume this is not relevant. The system-upgrade seemed to run to completion, but I could not

Re: urgent major problem after f39 to f40 upgrade.

On 10/10/24 6:48 PM, home user via users wrote: I had to dnf remove jgit for the system-upgrade to work.  That was true both this morning and this evening.  I assume this is not relevant. The system-upgrade seemed to run to completion, but I could not sit with it and watch it the whole time. 

Re: urgent major problem after f39 to f40 upgrade.

(I'm back, but in windows-7) On 10/10/2024 5:28 PM, home user via users wrote: On 10/10/2024 5:20 PM, Samuel Sieb wrote: On 10/10/24 3:59 PM, Jeffrey Walton wrote: After you get your problems sorted out, perform some of the post-upgrade tasks at

Re: urgent major problem after f39 to f40 upgrade.

On 10/10/2024 5:20 PM, Samuel Sieb wrote: On 10/10/24 3:59 PM, Jeffrey Walton wrote: After you get your problems sorted out, perform some of the post-upgrade tasks at . Oh, that's where

Re: urgent major problem after f39 to f40 upgrade.

On 10/10/24 3:59 PM, Jeffrey Walton wrote: After you get your problems sorted out, perform some of the post-upgrade tasks at . Oh, that's where it is. That apparently is the step that mi

Re: urgent major problem after f39 to f40 upgrade.

On 10/10/24 4:15 PM, home user via users wrote: On 10/10/2024 4:52 PM, Samuel Sieb wrote: On 10/10/24 3:45 PM, home user via users wrote: [snip] Ok, the install didn't get very far then. Though I did not watch the whole system upgrade, my impression was that it was successful.  It was dur

Re: urgent major problem after f39 to f40 upgrade.

On 10/10/2024 4:52 PM, Samuel Sieb wrote: On 10/10/24 3:45 PM, home user via users wrote: [snip] Ok, the install didn't get very far then. Though I did not watch the whole system upgrade, my impression was that it was successful. It was during the post-upgrade tasks when the real trouble

Re: urgent major problem after f39 to f40 upgrade.

On Thu, Oct 10, 2024 at 6:46 PM home user via users wrote: > > (replying to multiple posts) > [...] > > (Samuel) > > If I boot from the f-39 entry, uname -a says I'm running f-39. > > If I boot from the f-40 entry, uname -a says I'm running f-40. > > Regardless of which grub line I use to boot, rp

Re: urgent major problem after f39 to f40 upgrade.

On 10/10/24 3:45 PM, home user via users wrote: (replying to multiple posts) On 10/10/2024 3:45 PM, home user via users wrote: On 10/10/2024 2:02 PM, home user via users wrote: (I'm doing this from a windows-7 box) This morning, I did my weekly patches for my f-39 stand-alone workstation. 

Re: urgent major problem after f39 to f40 upgrade.

(replying to multiple posts) On 10/10/2024 3:45 PM, home user via users wrote: On 10/10/2024 2:02 PM, home user via users wrote: (I'm doing this from a windows-7 box) This morning, I did my weekly patches for my f-39 stand-alone workstation.  No problems. Then I did the upgrade to f-40.  I

Re: urgent major problem after f39 to f40 upgrade.

On 10/10/24 2:41 PM, home user via users wrote: (sorry.  I meant to reply to the list) On 10/10/2024 3:18 PM, Samuel Sieb wrote: On 10/10/24 2:14 PM, home user via users wrote: On 10/10/2024 2:40 PM, Samuel Sieb wrote: Try running `dnf distro-sync` first.  If it says it will install F39 packa

Re: urgent major problem after f39 to f40 upgrade.

On 10/10/24 2:45 PM, home user via users wrote: On 10/10/2024 2:02 PM, home user via users wrote: (I'm doing this from a windows-7 box) This morning, I did my weekly patches for my f-39 stand-alone workstation.  No problems. Then I did the upgrade to f-40.  I did not sit there and watch it.

Re: urgent major problem after f39 to f40 upgrade.

On 10/10/2024 2:02 PM, home user via users wrote: (I'm doing this from a windows-7 box) This morning, I did my weekly patches for my f-39 stand-alone workstation.  No problems. Then I did the upgrade to f-40.  I did not sit there and watch it. During the automatic reboot, it booted using th

Re: urgent major problem after f39 to f40 upgrade.

(sorry.  I meant to reply to the list) On 10/10/2024 3:18 PM, Samuel Sieb wrote: On 10/10/24 2:14 PM, home user via users wrote: On 10/10/2024 2:40 PM, Samuel Sieb wrote: Try running `dnf distro-sync` first.  If it says it will install F39 packages, then don't continue. Tried it as root and

Re: urgent major problem after f39 to f40 upgrade.

On 10/10/24 2:14 PM, home user via users wrote: On 10/10/2024 2:40 PM, Samuel Sieb wrote: Try running `dnf distro-sync` first.  If it says it will install F39 packages, then don't continue. Tried it as root and re-directed to a text file.  It wants to upgrade packages to f-39, so I responded

Re: urgent major problem after f39 to f40 upgrade.

On 10/10/2024 2:40 PM, Samuel Sieb wrote: On 10/10/24 1:02 PM, home user via users wrote: (I'm doing this from a windows-7 box) This morning, I did my weekly patches for my f-39 stand-alone workstation.  No problems. Then I did the upgrade to f-40.  I did not sit there and watch it. During

Re: urgent major problem after f39 to f40 upgrade.

On 10/10/24 1:02 PM, home user via users wrote: (I'm doing this from a windows-7 box) This morning, I did my weekly patches for my f-39 stand-alone workstation.  No problems. Then I did the upgrade to f-40.  I did not sit there and watch it. During the automatic reboot, it booted using the n

urgent major problem after f39 to f40 upgrade.

(I'm doing this from a windows-7 box) This morning, I did my weekly patches for my f-39 stand-alone workstation. No problems. Then I did the upgrade to f-40. I did not sit there and watch it. During the automatic reboot, it booted using the nouveau driver rather than the kmod one from rpm